﻿ticket,summary,host,guest,version,modified,_changetime,_description,_reporter
15967,VM guest freezes,Linux,Windows,VirtualBox 5.1.6,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"I think it is the same as this one #15529

I'm Running Linux Mint 18, and Windows 10 (x64) in the virtual box.

The guest freezes, sometimes in the startup, sometimes after 3 hours, sometimes NOT...
",Anders Dvinge
20592,Version 6.1.26 r145957 (Qt5.6.2) GUI crashes quite a times after start,Windows,all,VirtualBox 6.1.26,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"I am using Windows 10 Pro (Version	10.0.19042 Build 19042)and many a times, immediately after starting the application the GUI crashes. Virtualbox Version 6.1.26 r145957 (Qt5.6.2)

It was happening in an older version also. Mostly second time it starts just fine. 

None of my other apps crash, my system is an i7 with 32GB RAM. Attaching crash dumps.

Crash dump size is larger, unable to attach, copied in this folder on Google Drive : https://drive.google.com/drive/folders/13Wbp5wuq1thK2RzXxJZP6rxEtb9JYO1D?usp=sharing

",Ravi R
20901,not letting me create a user name,other,other,VirtualBox 6.1.32,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
21039,Guest Windows firewall disable does disable internet on Windows Host,Windows,Windows,VirtualBox 6.1.16,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"* Host/Guest: Windows 7 x64

I am trying to use shared MAC address on both Host and Guest, because ISP does block internet access by the MAC.

In that case if set Bridged network mode and try to disable the Windows 7 x64 firewall on the Guest, then the internet would be disabled on the Windows 7 x64 Host.",andry81
21116,VirtualBox 6.1.38 keeps crashing,Linux,Windows,VirtualBox 6.1.38,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"I frequently get my VirtualBox instance to crash. The OS the virtualbox guest is running is Windows 10. The host VirtualBox is running on is Fedora 35.

I've attached my logs like the gui pop-up requests.",Brad Walker
18925,"Virtualbox freeze all guest system (32, 64 bit, linux, windows, other)",Windows,all,VirtualBox 6.0.12,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"The Virtualbox freeze after running guest operating system.
",agostonl119
13572,GUI to remember whether Details or Snapshots were showing,Windows,all,VirtualBox 4.3.18,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"Could the VirtualBox Manager GUI (VirtualBox.exe on a Windows host) please remember between runs whether I had the Details or the Snapshots view in the right pane. 

I create, delete, restore snapshots a lot, but don't look at or modify (once the VM is set up) the VM details much. So almost every time I run the VirtualBox Manager GUI I click the Snapshots button (top right corner), because the GUI always starts showing Details. It would be very handy if the GUI would simply preserve the current view between runs, as it preserves many other GUI state details.",m6477
12050,Customizable keybindings needed,all,all,,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"Since Win8.x now has a dependency on the Win-Key, and there are keyboards that do not have the ""Windows Keys"", there needs to be a utility for creating custom keybindings for VirtualBox VMs.   I'm considering custom keybindings rather than hard-coding some combination for the WinKey, since that allows the flexibility for a user to re-map keys which the Host OS may want to use for different purpose.",jelabarre59
767,[documentation] Explain to users how-to run VirtualBox on Windows in background/as a service on PC boot,other,other,VirtualBox 1.5.0,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
1888,"Option to configure a VirtualBox VM to automatically ""save the machine state"" upon exciting - and do this minimized.",other,other,VirtualBox 1.6.2,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
1526,Virtualbox 'Native' Menu of the Virtual Machine,other,other,VirtualBox 1.6.0,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
1415,using keyboard shortcuts to switch virtual desktops on the host while in full-screen mode,other,other,VirtualBox 1.5.6,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
2098,MaxGuestResolution per machine,Windows,Windows,VirtualBox 2.0.0,2008-09-08T07:28:43Z,2008-09-08T07:28:43Z,"Feature request: ""VBoxManage setextradata global GUI/MaxGuestResolution ..."" shall be a per-machine setting.
",A20_user
2736,It is impossible to set a user's font table for text output in a graphics mode,Linux,other,VirtualBox 2.0.6,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
2906,Defining a keyboard filter,other,other,VirtualBox 2.1.0,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
3010,VM control on powerdown/reboot,other,other,VirtualBox 2.0.4,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
2389,mount.vboxfs does not allow context= option,Windows,Linux,VirtualBox 2.0.2,2009-01-21T09:07:47Z,2009-01-21T09:07:47Z,"Mounting a shared folder in a Fedora 9 linux guest, I receive SELinux denials when I try to copy files into the shared folder.  I received advice to attempt the mount using a ''context= option''.

According to the mount manpage, the ''context='' option should be supported on all filesystems...  So I guess this ticket is an RFE.

Cheers,
 Christian",Christian Iseli
2107,Feature request: Predefined absolute time for Guest,Windows,Windows,VirtualBox 2.0.0,2009-02-10T23:08:26Z,2009-02-10T23:08:26Z,Please add an option to set Guest time to a fixed value at startup. This is a feature for repeatable software tests.,A20_user
3451,files with national characters not shown via \vboxsvr,Linux,Windows,VirtualBox 2.1.4,2009-02-27T10:13:55Z,2009-02-27T10:13:55Z,"I am running VB 2.1.4_OSE with GA 2.1.4r42893. Guest is WinXPSP2, host is Debian 5.0 (smbd 3.2.5). When accesing host shares via standard \10.0.2.2\ I get full list of all files on that share (files with national characters have them converted to '_'s). When accessing shares via GA - Shared Folders, only files without national characters are shown.
",wolcano
3484,"Using shared folders, if the underlying shared resource becomes unavailable, you cannot remove it from its previously assigned VBOXSVR mapping.",Windows,Windows,VirtualBox 2.1.4,2009-03-03T12:33:36Z,2009-03-03T12:33:36Z,"Share a resource permanently, read-only, say E:\mp3 -> mp3.  This will show up in the guest OS as \VBOXSVR\mp3.  Then change the drive letter or make the resource generally unavailable (e.g. no E: drive).  Then try to go in to shared folders and remove it - this will appear to work successfully.  But if you go into the guest OS and browse, \VBOXSVR\mp3 will still be there!  Nothing you do within Vbox will make that change - rebooting, logging out as different user, etc.

I've attached virtual machine config files as well.

WORKAROUND:
* Shut down the guest OS
* Go to MachineDisks and find the guest OS's .xml file.
* Find section SharedFolders/SharedFolder which corresponds to share you're trying to remove.
* Change or remove the entry to be correct.
* Restart guest OS virtual machine.
* Vbox appears to just remove the entry you modified in the .xml file regardless of whether you set it to a valid value or not.
* Re-add the changed resource path (if you want to change it).

",cboyd
3493,Pass the Tablet PC Pen Flicks from the host to the guest,Windows,Windows,VirtualBox 2.1.4,2009-03-04T12:59:25Z,2009-03-04T12:59:25Z,"Pass the Tablet PC Pen Flicks from the host to the guest

1- Install the Virtual Box on Windows Vista 32 or 64 bit
2- Connect a wacom babmo tablet with pen and install the drivers
3- Open the vista control panel, and enable all pen flicks.
4- Install Windows Xp or Vista on a virtual machine, and install the additions.
5- Do (Copy) or (Paste) or (Undo) with the pen on the virtual machine

Results:
Vista will report that the pen flick is successful, but nothing will happen in the virtual machine

Expected Results:
Please just pass the flick command to the guest OS, I am not asking for full pen support, the current mode is very good, just pass the pen flicks to the guest.
",GT
3422,USB Filter does not distinguish two or more identical USB devices,Mac OS X,Windows,VirtualBox 2.1.4,2009-03-25T19:28:13Z,2009-03-25T19:28:13Z,"Actually I want to overcome the problem described in ticket #373. It is really problematic not able to enter backslash and other chars on a German keyboard layout.

I use the Microsoft Natural Ergonomic Keyboard 4000 with a Mac Mini. Host is Mac OS X Leopard. 

My idea was the following: I tried to use two identical USB keyboards. One should be connected to the host. The other should be connected to the guest. However, when I enter the USB filter dialog, the virtualbox lists two devices with identical name ""Microsoft Natural Ergonomic Keyboard 4000 [0173]"". I selected one of both to be used with the guest.

Then, I started the guest Windows XP. However, instead of connecting only one device of both to the guest, the virtualbox connects both USB devices (Not okay). It should be possible to distinguish between identical devices in case of multiplicity.


Then, I tried to use this with Windows Vista x64 as guest. Forget it, it starts to toggling and never starts up.

",Harald Stuebinger
3645,files in guest shared folders seems not to reflect changes done in host,Linux,Linux,VirtualBox 2.1.4,2009-04-15T08:44:17Z,2009-04-15T08:44:17Z,"I have a guest OS (Ubuntu Hardy Heron) with shares a folder (in read/write) with the host OS (Ubuntu Hardy Heron). I use a web editor to edit the files in this folder in the host OS so the modifications should be seen in the guest OS (the shared folder, mounted in the guest, is the root directory of an apache web server installed just in the guest).
The problem is that, when I modify a file in the host side, these changes seem not reflected correctly in guest side. Via a simple cat or less or vi the modified files seem correct but with apache the modifications aren't reflected (I can test this via ""telnet server 80""). In fact often the modifications are seen as strange characters or other times other strange behaviours happen.
I can solve this either:
- umount and then re-mount the shared folder (but I have to do this after every file change)
or
- simply edit the file via vi (guest side) and, with no modifications, save the file",Marco 
3800,global alt-tabbing?,other,other,VirtualBox 2.2.0,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
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,other,VirtualBox 2.2.0,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
3821,Estimate required and available disk space when discarding snapshots,Linux,Windows,VirtualBox 2.2.0,2009-04-23T12:21:10Z,2009-04-23T12:21:10Z,"When discarding snapshots in the Virtual Media Manager, it would be good to estimate the required and available disk space before the operation starts and refuse it if there is not enough disk space.

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

Happily, I have had a backup copy of that file.",Vladimir
3887,"Feature request: make VirtualBox compatible with Virtual PC guest additions, since that supports MS-DOS, Windows 3.1/95/98",other,Windows,VirtualBox 2.2.2,2009-04-30T00:32:20Z,2009-04-30T00:32:20Z,"It would be a great idea if guest additions could be provided for MS-DOS, Windows 3.1, 95 and 98. If the VirtualBox developers need to obtain the Windows 3.1 or 95 DDKs, let me know.

Of course, developing guest additions for those older OSes would take a lot of development time. As an alternative, would it be possible to implement compatibility with guest additions used by Microsoft Virtual PC (2004/2007)? Then MS-DOS and Windows 3.1/95/98 could have guest additions support without much extra work; The user would just need to install the additions from Virtual PC. Also, image files created with Virtual PC would then be completely usable with VirtualBox without needing to uninstall/install additions.
",Donuts
2439,"Need ""are you sure"" power off option",Linux,Windows,VirtualBox 2.0.2,2009-05-04T01:54:45Z,2009-05-04T01:54:45Z,"Hi All,

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

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

Many thanks,
-T


",ToddAndMargo
2570,Seamless mode with Vista host doesn't work correctly with Sidebar turned on,Windows,Windows,VirtualBox 2.0.4,2009-05-04T16:34:53Z,2009-05-04T16:34:53Z,"Using a Vista host with the Sidebar enabled, a Windows XP guest in seamless mode isn't cropped properly.  All window cropping is shifted to the left 2 pixels, such that a windows shows 2 pixels of the background on the left and is missing 2 pixels of the border on the right.

The problem disappears when the Sidebar is closed.",Chris Thompson
4004,Access favorite Windows or Linux programs straight from Mac Dock,Mac OS X,Windows,VirtualBox 2.2.2,2009-05-12T22:21:41Z,2009-05-12T22:21:41Z,"It would be great to be able to access Windows or Linux applications directly from Mac OS X Finder by double-clicking an application icon, just like Mac OS X integration offered by VMWare and Parellels offers.
Also to display them in the dock when they are launched just like a normal Mac OS X application.

Here in Parallels : http://www.parallels.com/products/desktop/features/new/ Favorite Applications

http://www.parallels.com/files/img/pdfm40/screenshots/coherence_start.png
http://www.parallels.com/files/img/pdfm40/screenshots/coherence_vm1.png

",M-Rick
4003,"Impossible to hide USB devices, specifically the host system disk",Linux,Windows,VirtualBox 2.2.2,2009-05-13T09:13:16Z,2009-05-13T09:13:16Z,"
My host system (Ubuntu Jaunty 9.04) boots from an external USB disk that is selectable in the USB selection menu as any other connected usb device.

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

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

Perhaps a feature like filters but whith a blacklist logic...",Mico
2957,[Suggestion] ISZ Compressed ISO Support,other,other,VirtualBox 2.1.0,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
4057,ER: Simpler way of accessing Windows host printer from Ubuntu guest,Windows,Linux,VirtualBox 2.2.2,2009-05-20T09:05:57Z,2009-05-20T09:05:57Z,"
I am a non-technical user of VirtualBox 2.2.2 so I can run Linux programs on a Ubuntu guest for purposes of writing third-party user guides in FrameMaker on Windows XP SP3. I would like to remain a non-technical user and therefore propose that Guest Additions for all guest OSes incorporates a virtual printer that can access one or more real network/local/usb/parallel/serial printers on the host OS.

This could be a configuration option in the xVM VirtualBox GUI that allows the user to map guest printers to real printers, however then may be attached to the host.

I am trying to access my Epson CX6900F on Windows XP SP3 from an Ubuntu 9.04 Jaunty Jackalope using CUPS and Samba but without success. (I told you I was non-technical.)

I have shared a folder on Windows to try and access it from Samba but although it scans for shared folders can't find it.  Same for shared printer with CUPS.",Hedley Finger
3064,Wanted pre-start post-stop scripts,other,other,VirtualBox 2.1.0,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
4189,Need ot be able to chunk large VMDK files when exporting an appliance,Linux,Solaris,VirtualBox 2.2.4,2009-06-05T16:44:35Z,2009-06-05T16:44:35Z,"We need an easy way to split up the files that comprise a virtual appliance so that they are easily distributed to our end users on media like DVDs and CDs. My preference would be a check box in the Export Appliance dialog box with an option like ""Split large files into 2 GB chunks."" Import Appliance should be smart enough to recognize that is importing a chunked vmdk and rebuild it as part of the import. (If that is too difficult to do, it would be acceptable if the user had to select an option in the Import Appliance dialog to tell VirtualBox to rejoin the vmdk.)

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

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

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

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

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

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

Thanks and regards,

David",David Goldsmith
4229,Allow specification of the configuration directory (VBOX_USER_HOME) from the command line.,other,other,VirtualBox 2.2.4,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
4367,Better folder sharing ideas,other,other,VirtualBox 3.0.0,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
4338,enable/disable features of guest additions,other,other,VirtualBox 3.0.0,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
3368,vlan interface support in os x version,Mac OS X,Windows,VirtualBox 2.1.4,2009-07-16T20:54:48Z,2009-07-16T20:54:48Z,"In os x leopard (10.5) it is possible to add vlan interfaces as follows:

-Click on system preferences----->network
-Click on the ""cog"" icon at the botom of the interfaces list and select ""manage virtual interfaces.
-Add additional tagged interface as per needed ;)

Once created, these interfaces show up to OS X as if they were additional physical interfaces, but do not show up as usable host interfaces in virtualbox.  If it could be possible to use these interfaces in virtualbox it would make an enormous different to my ability to use virtualbox on an OS X host as a server virtualization solution in my production environment.  Without it I am limited to only being able to have virtual machines on as many subnets as I have physical NICs.  

From reading through other posts etc, it seems as if this functionality may already be present in the windows version?

Thanks for all you hard work!  virtualbox is fantastic!

-Neil",Neil Broadbent
4635,Allow remapping of parallel port addresses,Linux,other,VirtualBox 3.0.2,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
3813,Discarding a Snapshot should not decrease space left on the device before increasing it,other,other,VirtualBox 2.1.2,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
4661,VirtualBox creates folder in /Volumes/ directory when disk with virtual machines is not present,Mac OS X,other,VirtualBox 3.0.2,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
4673,please add a machine configuration option to always show the boot device menu,other,other,VirtualBox 3.0.2,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
4678,Linux host running on MacBook Hardware: Default release key should be left-winkey,Linux,other,VirtualBox 3.0.4,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
4804,creating directories with umlauts in a shared folder fail with error 0x80070057 on Windows Host,Linux,other,VirtualBox 3.0.2,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
4828,Usability issue when deleting multiple hard disks using Virtual Media Manager,Mac OS X,other,VirtualBox 3.0.4,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
4728,using host share for my documents in windows is slow but mapped drive isn't,Linux,Windows,VirtualBox 3.0.4,2009-08-23T21:24:11Z,2009-08-23T21:24:11Z,"Weird issue found.

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

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

told you it was weird!",Richard
5053,options that are unavailable should be deselected in addition to being grayed out,other,other,VirtualBox 3.0.6,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
5064,"Mouse I-pointer and crosshair pointer disappears when using Guest Additions (Vista host, WinXP guest)",Windows,Windows,VirtualBox 3.0.6,2009-09-23T13:48:47Z,2009-09-23T13:48:47Z,"I'm using Windows Vista as my host and Windows XP as my guest. When I'm using VirtualBox Guest Additions and mouse pointer integration is enabled, the regular mouse pointer appears ok, but when I move my mouse within the guest to a textbox, or to a window which is supposed to change into a crosshair pointer, the mouse pointer disappears on those areas. When I move out of the affected areas, the regular mouse pointer appears. The other mouse pointers, like the hand pointer when selecting a hyperlink, and the hourglass pointers appear fine.

When I disable the mouse pointer integration, all pointers are working perfectly. However, I'd like to have the mouse pointer integration enabled as I would have difficulty moving from an application in my host and an application running in the guest (I have to hit Right-Ctrl every time.)

Using the same VirtualBox version on a Linux (Ubuntu Jaunty) host and the same Windows XP guest, I did not experience this problem.

",Jake Catayoc
5076,Keyboard go crazy (miss map) after screen turn off and come back,Windows,Linux,VirtualBox 3.0.6,2009-09-25T08:20:58Z,2009-09-25T08:20:58Z,"I just install the latest Virtualbox yesterday and i observed a very strange behavior. Below is the details description:

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

- Basically the problem is causing the host keyboard catching to go crazy. 
- Seem like the window key (special key) is lock up, so no matter what key i pressed, even is a single key (such as ""y"") but in the host window it seem like (window key + y).
- I try using VMware unity, it did not seem to have this problem. So i guess it is a bug. Has this bug being reported?",ntyonline
5122,Can't access shared folder without login on Windows 2003,Windows,Windows,VirtualBox 3.0.6,2009-10-05T12:47:20Z,2009-10-05T12:47:20Z,"Try to access shared folder from autorun service (not with !LocalSystem account but a User account) using net command or UNC but doesn't work until someone login and must maintain login for the access to work.

Issue mentioned in thread:
http://forums.virtualbox.org/viewtopic.php?f=2&t=22032
",Cplaisstw
4961,Mouse wheel scrolling broken in Ubuntu 32 bit guest / Windows 7 host since 3.06,Windows,Linux,VirtualBox 3.0.6,2009-10-06T21:50:56Z,2009-10-06T21:50:56Z,"Subject says it all really - since upgrading to 3.06 I can no longer use the mouse wheel to scroll in an Ubuntu guest.

Ceri",carlill
5172,Improve RDP audio latency,other,other,VirtualBox 3.0.8,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
1944,VirtualBox Amazon EC2 Integration,other,other,VirtualBox 1.6.4,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
3045,Feature Request: Control HOST os resolution in fullscreen mode (for res switching),Windows,Windows,VirtualBox 2.1.0,2009-10-29T19:35:02Z,2009-10-29T19:35:02Z,"Id like to see a feature that allows virtual box to control the physical monitor on resolution switching 

for example
  you launch gameA.exe and it needs to run in fullscreen 800x600 on the GUEST os but the HOST os is 1600x1600 (right now it just shows as a little square in the middle of the screen with big borders), it would be really nice if VirtualBox could change the HOST display to the required resolution the guest os is at. (this would probably be needed for windows only and when in fullscreen mode, i think X11 doesn't change res's as much) 

so far other software such as microsoft virtual pc 2007 (in their options it has a pulldown that says ""use guest os resolution"", ""use host's resolution"" ..etc)

vmware , and parallels has a option, VirtualBox is such great software this feature missing is a giant let down for me, it has speed, hardware support, lightweight, it just cant control the host's resolution. :\

dont confuse this with ctrl+g (since that just ups the virtualbox to the host's current resolution (what i need is the host's resolution to match the currnet guest os resolution so basically its reversed ;) ) 

",hyakki
5335,"When running a VM, Hard Disks should be opened ShareMode=0 to prevent other processes writing to them",other,other,VirtualBox 3.0.8,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
5344,Add Haiku to the list of supported OS,other,other,VirtualBox 3.0.10,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
5349,traffic get answered on the wrong VLAN,Windows,Linux,VirtualBox 3.0.10,2009-10-30T18:44:54Z,2009-10-30T18:44:54Z,"debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

second debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

you will notice on the tcpdump trace that requests are received in VLAN 400/VLAN4 (this is QinQ) but the response is sent on VLAN 4 which is not even configured on the box.

tcpdump [[BR]]

tcpdump -i eth2[[BR]]

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode[[BR]]

listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes[[BR]]

15:33:47.584076 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:47.614299 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:48.566620 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:48.566983 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:49.549445 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]
[[BR]]
[[BR]]


setup:[[BR]]

apt-get install vlan[[BR]]

modprobe 8021q[[BR]]

vconfig add eth3 400[[BR]]

ifconfig eth3.400 up[[BR]]

vconfig add eth3.400 4[[BR]]

ifconfig eth3.400.4 up[[BR]]


",erik
5392,VRDP Multiconn looses track of connection details,other,other,VirtualBox 3.0.10,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
5428,Mac OS X: Deleting Virtual Hard Disks Should Move to Trash,Mac OS X,other,,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
3163,Can't create snapshots when ~/Library/VirtualBox is a symlink,Mac OS X,other,VirtualBox 2.1.2,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
5452,Auto detect active network interface,other,other,VirtualBox 3.0.10,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
171,More GUI commands,other,other,VirtualBox 1.3.6,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
2578,Update sections 3.4.3 and 3.4.4 to reflect current functionality,other,other,VirtualBox 2.0.4,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
3128,Fix PCI ID vendor,other,other,VirtualBox 2.1.2,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
2158,MacOS: Expose support,Mac OS X,Windows,VirtualBox 2.0.0,2009-11-16T08:56:40Z,2009-11-16T08:56:40Z,"Parallels and Vmware both support a feature called Expose with Windows guest systems.[[BR]]
When clicking the Expose key, MacOs shows all the open windows in a miniaturized form and the user is able to click the right window he wants to ""flip to"". Parallels and Vmware integrate Windows guest windows into expose, which is extremly usefull.[[BR]]
[[BR]]
it would be very nice, if virtualbox would introduce this feature (in the coherence mode) in a later version, too.",virtualbox
5547,[feature-request] Log all loaded drivers currently running on host,other,other,VirtualBox 3.0.12,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
5555,Mac OS X: Time Machine-friendly storage,Mac OS X,other,,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
5557,"Allow user to specify network card option ROM image, and ship default PXE images for boot.kernel.org",other,other,VirtualBox 3.0.12,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
715,[feature-request] Make virtual monitor (screen/display) customizable,other,other,VirtualBox 1.5.0,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
5574,In Seamless mode clicking on window titles bring guest windows to top,Linux,Windows,VirtualBox 3.0.12,2009-11-27T11:24:49Z,2009-11-27T11:24:49Z,"I have VirtualBox installed on Ubuntu 9.04(actually Linux Mint 7),using KDE 4.3.2
Guest is Windows XP SP3, themes are disabled.

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

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

",roozbeh
286,make console screen available when vm is powered off & addevirtual power buttons,other,other,VirtualBox 1.3.8,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
5594,Keyboard mapping problems using SSH tunneling,Mac OS X,Linux,VirtualBox 3.0.12,2009-12-01T09:13:33Z,2009-12-01T09:13:33Z,"While using OpenSSH 5.3 to SSH into my Debian 5.3 GNU/Linux and Ubuntu 9.10, I encounter keyboard mapping problems whenever I run X11 applications from the SSH terminal. When I type into any X11 program (such as leafpad, xterm, etc.), the keyboard output is completely jumbled. When I type ""QWERTY"", I get ""-=[reverse tab][forward tab]w"", also caps lock acts as a space and the back space as a comma. 

I'm running all this on Mac OS X Snow Leopard (v 10.6.2)",sm_news
5628,"Suggestion: Add a ""minimise writes"" option to Windows Guest Additions",other,other,VirtualBox 3.0.12,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
5308,vrdp with resistive touchscreen tablet pc,Windows,Windows,VirtualBox 3.0.8,2009-12-01T17:59:01Z,2009-12-01T17:59:01Z,"Hello,
I just dug this out of the forums, realizing that after all this time; I've had it in the wrong spot.

I just bought a tablet (slate) WinCE pc with a 10"" resistive touch screen. I can connect to virtualbox with vrdp and it looks great, and the response times are great, but I have one issue. With the touchscreen, I have to touch twice to click (once to move the mouse to the desired location, again to click) or hold it for like a second. This makes double clicking impossible. Although, I can use the hard navigation buttons just fine. Using the Microsoft's RDP on the guest works perfect, so I am believed to it bieng virtualbox.

I am hoping to use the tablet for interacting with MS PowerPoint that is being displayed fullscreen on a projector simultaneously. It doesn't matter if mouse integration is enabled or not.

I have:
Host: win7 x64
--CPU: i7 920
--Memory: 6 Gb 
Network: Host - ethernet - wireless router - wifi (802.11g w/ excellent signal) - tablet
Guest: Win XP Pro Sp 2 tablet edition
--VB version: 3.0.8; additions: installed
--mouse integration: on and off
tablet: viewsonic v210 WinCE 4.2
--RDC v5.1 settings:
----Display: 256 color (lowered to see if it would help, didnt)
----Local resources: Sound: leave at remote; local dev: none checked
----Experience: Performance: Custom (none clicked, to test, didnt help)


there is no crash, so i dont believe a log file is needed.",silverhawk_184
5624,PXE does not work with virtio,Linux,other,VirtualBox 3.1.0,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
976,Feature request: automatic snapshots with merge,other,other,VirtualBox 1.5.2,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
2104,"Better management of VMs, Disks and Snapshots in GUI",other,other,VirtualBox 2.0.0,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
3061,Add Virtual Disk Tasks to Virtual Media Manager,other,other,VirtualBox 2.1.0,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
5148,integration between host/guest panels and menus,Linux,Windows,VirtualBox 3.0.8,2009-12-01T20:17:43Z,2009-12-01T20:17:43Z,"It would be nice if the applications and icons normally shown on the Windows taskbar were instead shown on the GNOME panel window list.

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

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

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

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

I'm using Debian GNU/Linux with the GNOME desktop as a host and Windows XP and Windows 7 as guests. It would also be useful to have similar things for other Linux desktops.",Paul Wise
5652,Bridge network driver breaks host network DHCP,Windows,other,VirtualBox 3.1.0,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
5489,high-bandwidth multicast traffic,Linux,Linux,VirtualBox 3.0.10,2009-12-04T11:00:18Z,2009-12-04T11:00:18Z,"Hi!

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

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

I will attach the kernel ring buffer log. ",Stefaan
5806,Dialog should not include whole status because it doesn't fit,Mac OS X,Linux,VirtualBox 3.1.2,2009-12-20T09:45:33Z,2009-12-20T09:45:33Z,"Resuming and Suspending on OS X stick the entire progress message into the dialog title.

This results in:

{{{
.________________________________.
| ( ) ( ) ( ) Mer: Spawning s... |
|--------------------------------|
|       Spawning session...      |
|[=================             ]|
|                                |
|________________________________|

.________________________________.
| ( ) ( ) ( ) Windows 7: Rest... |
|--------------------------------|
|  Restoring virtual machine...  |
|[=================             ]|
|21 seconds remaining            |
|________________________________|
}}}

Expected results:
  Don't show the primary text in the dialog title
or
  Make the dialog wide enough such that the title text can be read...",timeless
5808,Session information should prefer to wrap at word breaks and punctuation,Mac OS X,Windows,VirtualBox 3.1.2,2009-12-20T11:03:57Z,2009-12-20T11:03:57Z,"The session information dialog wraps text in a fairly annoying way. I understand that someone felt wrapping was important, but it'd be great if a word wrapping/sentence wrapping algorithm was employed instead of merely treating all characters as equal.

Steps:
 1. setup Windows 7 with a fairly typically setup
 2. install guest additions
 3. start Windows 7
 4. open the session information dialog

Actual results:
{{{
￼ General
   Name:                 Windows 7
   OS Type:              Windows 7 (64 bit)
 
￼ System
   Base Memory:          1024 MB
   Processor(s):         1
   Boot Order:           CD/DVD-ROM, Hard
                         Disk
   VT-x/AMD-V:           Enabled
   Nested Paging:        Enabled
 
￼ Display
   Video Memory:         32 MB
   3D Acceleration:      Enabled
   2D Video Acceleratio  Enabled
   n:
   Remote Display Serv   3389
   er Port:
 
￼ Storage
   IDE Controller
    IDE Primary Master:  Windows 7 rc.vdi
                         (Normal, 60.00 GB)
    IDE Secondary Mast   VBoxGuestAdditions.is
   er (CD/DVD):          o (31.79 MB)
   SATA Controller
   Floppy Controller
    Floppy Device 0:     Empty
 
￼ Audio
   Host Driver:          CoreAudio
   Controller:           ICH AC97
 
￼ Network
   Adapter 1:            Intel PRO/1000 MT
                         Desktop (NAT)
   Adapter 2:            Intel PRO/1000 MT
                         Desktop (Bridged
                         adapter, en0:
                         Ethernet)
   Adapter 3:            Intel PRO/1000 MT
                         Desktop (Bridged
                         adapter, en1: AirPort)
 
￼ Serial Ports
   Disabled
 
￼ USB
   Device Filters:       7 (7 active)
 
￼ Shared Folders
   Shared Folders:       3
}}}

Expected results:
{{{
...
￼ System
...
   Boot Order:           CD/DVD-ROM,
                         Hard Disk
... 
￼ Display
...
   2D Video
   Acceleration:         Enabled
   Remote Display
   Server Port:          3389
 
￼ Storage
   IDE Controller
...
    IDE Secondary
    Master (CD/DVD):     VBoxGuestAdditions
                         .iso (31.79 MB)
...
}}}",timeless
5856,Can not write to VBox shared folders until someone logs in,Linux,Windows,VirtualBox 3.1.2,2009-12-27T21:36:34Z,2009-12-27T21:36:34Z,"Vbox 3.1.2
Host: CentOS 5.4
Guest: Windows Server 2003 as a Terminal Server
Guest Additions: 3.1.2

Hi All,

Would you please fix this for me?

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

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

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

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

Many thanks,
-T",ToddAndMargo
5878,Virtual Media Manager drag and drop support,other,other,VirtualBox 3.1.2,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
4167,Mac OSX Host: Enable CD/DVD Eject Key in Guest,Mac OS X,other,VirtualBox 2.2.4,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
5943,LeftCommand+H cannot be passed to guest on Mac OS X,Mac OS X,Linux,VirtualBox 3.1.2,2010-01-08T19:43:02Z,2010-01-08T19:43:02Z,"See also #5684.

I have redefined the host key to !RightCommand because I use !LeftCommand in the guest.

In 3.1.0 !LeftCommand+H was passed to the guest.

In 3.1.2 !LeftCommand+H is intercepted by the GUI and causes the guest to be hidden.

Consequently !LeftCommand+H cannot be passed to the guest.

Please either:
 * bind ""hide guest"" to !HostKey+H rather than hard coding !LeftCommand+H, or
 * provide an option to disable interception of !LeftCommand+H

Many thanks!",Tom Payne
5959,[feature-request] GUI: Show 3D Acceleration in status bar,other,other,VirtualBox 3.1.2,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
4949,Need to be able to re-assign keys for Mac,Mac OS X,other,VirtualBox 3.0.6,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
6036,[Docs] Please document major dropped features,other,other,VirtualBox 3.1.2,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
6093,Deleting a snapshot when the underlying vdi files are readonly,Windows,Windows,VirtualBox 3.1.2,2010-01-29T14:55:37Z,2010-01-29T14:55:37Z,"If you make a VDI file for a snapshot on disk read only to protect it against unexpected modification and then try and delete a snapshot which results in merging on the read only VDI, the snapshot dissapears from the UI but it fails to complete since the file is read only. You can't try again though since the snapshot has gone from the UI.

I.e.

A  <--Read only
|-B  <-- Read only
  |-C

Then delete snapshot B, when it tries to merge to give you A->C it'll fail, however the UI shows B missing now and you end up having to delete all snapshots and reverting back to the base disk.

If the merge operation fails then the snapshots in the UI should be left untouched.",Robert Garfoot
5768,[feature-request] Allow VM to run faster or slower than normal time,other,other,VirtualBox 3.1.0,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
6132,VBoxManage confuses VM names starting with dash character (-) with command line option names,Linux,Linux,VirtualBox 3.1.2,2010-02-04T14:22:48Z,2010-02-04T14:22:48Z,"When playing with VBoxManage I created a VM with name ""--ostype"" (by mistake - there was an error in my shell script that invoked VBoxManage)

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

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

Apparently, VBoxManage confuses VM names starting with dash character (-) with command line option names. !VirtualBox GUI does not have such problem.",xlogger
6148,international characters cannot be created on mounted linux guest shared folder,Linux,Linux,VirtualBox 3.1.2,2010-02-09T14:16:21Z,2010-02-09T14:16:21Z,"Im using linux ubuntu as guest running on linux host ubuntu. shared folder mount perfectly and I can copy move and delete any files on it, but files with caracters with acentos gives me ""protocol error"" see the command:

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

the above creates the file test.txt

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

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

thanks.",Marcus Leandro
6178,[feature-request] Installer: Please introduce internal checksum,Windows,other,VirtualBox 3.1.4,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
5862,integrate host and guest keyboard window switching (ALT+TAB),Linux,Windows,VirtualBox 3.1.2,2010-02-23T13:53:25Z,2010-02-23T13:53:25Z,"I feel the same as the reporter of Ticket #778, about the VM instantly passing keyboard focus to the guest being very annoying for people such as myself who use the keyboard to switch between windows in the host system.

However, instead of disabling this focus-passing, I propose another interesting feature that will solve this problem: Just like the mouse focus is seamlessly shared between the host and guest (with guest additions), maybe the ALT+TAB window switching inside the guest could be integrated with that of the host. So that you can somehow switch through both host and guest windows without needing other keyboard shortcuts / mouse clicks inbetween.",uetsah
5816,Reserve the guest OS taskbar space on the host OS desktop in seamless mode,Windows,Windows,,2010-02-23T13:58:13Z,2010-02-23T13:58:13Z,"I think this will be useful for those who want the guest to work seamless with the host OS.

In the seamless mode, When a host application is maximized, it will cover the guest OS taskbar. If I want to use guest application, I have to minimize the host application to make the guest taskbar show up. So there will be a lot of unnecessary mouse clicks and movement, if I have to do much copy/paste work between guest and host.

Now, I walk around this problem using the HSI(Hawkeye ShellInit), a small tool that can create any number of margins on the screen that maximized windows won't cover.

I think this can be easily implimented in the Virtualbox. The guest additions gets the guest's taskbar position and width, then sends this imformation to the vboxmanager. The vboxmanager performs the same function in seamless mode like what the HSI will do. ",kidault
543,confirm before doing dangerous commands or allow to disable those commands,other,other,VirtualBox 1.4.0,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
4924,Change mount behaviour in suse guests (vboxadd),Linux,Linux,VirtualBox 3.0.4,2010-03-12T04:06:17Z,2010-03-12T04:06:17Z,"Having vboxsf in the fstab with opensuse is not that good, as suse cannot umount volumes correctly (did not track down this one), however I think the way devices get unmounted is not the best way to do so.

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

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

For all described the attached patch is working.",Michael Kromer
6307,Partitions larger than 2T are not supported with Raw disks,other,other,VirtualBox 3.1.4,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
6418,Microsoft NetworkLoadBalance unicast mode can't work on VirtualBox3.1.4(Linux version),Linux,Windows,VirtualBox 3.1.4,2010-03-26T02:25:15Z,2010-03-26T02:25:15Z,"I use VB-3.1.4 to test the WIN2003 Network Load Balance, but I find it can't work on unicast mode, while the multi-cast mode can work fine. I tested the WIN2003 with the same configuration for unicast mode on vmware, and it works. I search the bug report for it, but there is no help. Is there some bugs on VB?

BTW: I use virtual box with non-root account.
",dwei
4939,alt-tab back out of guest doesn't work,Linux,Linux,VirtualBox 3.0.6,2010-04-04T02:11:47Z,2010-04-04T02:11:47Z,"Host: Centos 5.3, GNOME 2.16.0
Guest: Ubuntu 9.04, GNOME 2.26.1, guest additions installed

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

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

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

It would be really, really useful to be able to define some hotkeys which are *not* passed through like this... Please! :-)",Andrew Clegg
6500,Virtualbox BIOS should implement USB legancy support,other,other,VirtualBox 3.1.6,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
3072,Seamless mode prevents drag to host desktop,Solaris,other,VirtualBox 2.1.0,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
6514,Host only interfaces and DHCP servers show strange behavior,Linux,other,VirtualBox 3.1.6,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
4763,Cross-PC Clipboard Data Exposure Using Remote Desktop into Guest,Windows,Windows,VirtualBox 3.0.4,2010-04-13T12:51:35Z,2010-04-13T12:51:35Z,"I discovered what I would consider a data security exposure (at worst) or (at best) an undesirable function of clipboard copy/paste. I have an XP guest (running on a Vista host, but I don't think the host platform matters). Let's call the XP guest GUEST1 and the Vista host HOST1. Often, using another plain standalone XP PC (not running VirtualBox) -- a separate physical PC on the same network that we'll call PC1 -- I will use Windows Remote Desktop from PC1 to access GUEST1 remotely. If I copy text in the Remote Desktop session from PC1, the next paste operation on HOST1 results in pasting the data that was copied from the Remote Desktop session on PC1 (obviously by way of GUEST1).

The data copied to the clipboard should have remained only on the physical PC on which is was copied, in this case PC1 which isn't even running VirtualBox.

This becomes a problem when a separate user on another computer is remotely accessing a guest. This is actually how I discovered the problem as undesirable data was appearing in my host clipboard while someone else was remotely accessing my guest. They could be copying sensitive data, which should not appear on the host clipboard.

This is an easy scenario to recreate on demand. I have verified that this scenario happens in 3.0.4 and as far back as 3.0.0, possibly earlier as I have been having unexpected data appear in my host clipboard for some time.",Christopher Makris
6547,"Cancelling ""Add host-only network"" causes ""Unknown device"" to be created.",Windows,other,VirtualBox 3.1.6,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
5668,[Feature-request] Global Shared Folders,other,other,VirtualBox 3.1.0,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
3990,VLAN support,other,other,VirtualBox 2.2.2,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
6602,runtime change remembered through First Run Wizard,other,other,VirtualBox 3.1.6,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
3236,hostif networking doesn't work when link is down,Linux,other,VirtualBox 2.1.2,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
418,Sharing a single VM on multiuser accounts (Ubuntu),other,other,VirtualBox 1.4.0,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
1929,"[feature-request] Allow Custom, per-VM BIOS",other,other,VirtualBox 1.6.4,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
6576,Suggestion for improving the usermanual: Hostonly connection  should mention routing.,Linux,Linux,VirtualBox 3.1.6,2010-05-04T14:14:20Z,2010-05-04T14:14:20Z,"I used virtualbox before version 2.0, and now I need it in a production case.

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

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

I tried a random few, and ended up with ""host only"", which I think should mention the option of using routing from the guest to the outside world. This would've made my experience with the new version a lot easier: I could've selected the right option right away. ",Roger Wolff
6645,"Option to configure USB devices out of the Devices->""USB Devices"" menu",other,other,VirtualBox 3.1.6,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
6752,Option to ask for password when leaving virtual machine,other,other,VirtualBox 3.2.0,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
893,[feature-request] Revolutionary CLI for mass-management of Virtual Linux Servers,other,other,VirtualBox 1.5.2,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
3853,[feature-request] List which guest additions are ready to be installed,other,Windows,VirtualBox 2.2.0,2010-05-23T15:35:19Z,2010-05-23T15:35:19Z,"Going over an old predecessor, Connectix VirtualPC 5.1, I found many niceties.

One of them is that when Guest Additions for Windows setup is launched it shows exactly which features it will enhance.

Minor nice-to-have.

-Technologov, 27.4.2009.",Technologov
4934,Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running,Windows,other,VirtualBox 3.0.4,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
1751,Allow SMBIOS information to be copied from host,other,other,VirtualBox 1.6.2,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
6815,Dual Monitors in full screen doesn't focus when dropping windows into other screen,Windows,Windows,VirtualBox 3.2.0,2010-05-26T14:24:41Z,2010-05-26T14:24:41Z,"When in Full Screen mode and Guest OS having 2 Virtual Monitors, moving 1 window to another screen requires an additional click to have the focus on what should already have a focus (i.e. to drag the window back to the other monitor, I'd need another click to focus the ""window/screen/monitor"" then I can click+drag. For completeness, I think this is a ""minor"" fault.  Fixing this will make it as seamless as a real dual monitor setup!",danf84
6829,"Network Adapter dialog allows to select Bridged Adapter, that is not installed, but actually doesn't set this setting",Windows,Linux,VirtualBox 3.2.0,2010-05-28T14:18:53Z,2010-05-28T14:18:53Z,"I have VirtualBox already installed. But it was installed without VirtualBox Networking. I tried to change network settings of the virtual machine by clicking on the icon in the bottom of the window. The next dialog offed me to select Bridged Adapter (though it is not installed). Then I press Enter and it allows me to select this adapter. But when I press the icon once again, adapter is not attached.",r75a7
4744,Windows host and guest drives should be WHQL certified (Windows logo testing),Windows,Windows,VirtualBox 3.0.4,2010-05-28T20:25:00Z,2010-05-28T20:25:00Z,"Just upgraded VB from 3.0.2 to 3.0.4 on Windows XP. Upgrading the guest additions failed with the error that the driver for the VirtualBox Graphics Adapter has not passed Windows Logo testing to verify its compatibility with Windows XP. I've tried uninstalling the previous guest additions and get the same error.

The host is also XP.

The guest is configured with 16MB of video RAM with 3D Acceleration disabled.",John Clayton
6692,go to fullscreen mode when maximizing the guess window,other,other,VirtualBox 3.1.8,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
4134,Host Only Networking: Route Connections,Linux,other,VirtualBox 2.2.4,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
1735,feature-request: Hardware Virtualization GUI Info Utility,other,other,VirtualBox 1.6.2,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
6888,Automatic Name Wizard GUI issues,other,other,VirtualBox 3.2.0,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
6893,32-bit Windows OpenGL applications are not 3D-accelerated in a 64-bit Windows guest,other,Windows,VirtualBox 3.2.2,2010-06-04T07:44:20Z,2010-06-04T07:44:20Z,"With VBox 3.2.2, 64-bit Windows OpenGL applications are now 3D-accelerated with 64-bit Windows guests, but 32-bit OpenGL applications still use the software renderer.

The 3.2.2 Guest Additions for Windows appear to install 32-bit versions of the VBoxOGL DLL's in c:\windows\syswow64, but the necessary registry information to enable these is not present in:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\VBoxOGL

If I copy this key over from the 64-bit location

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\VBoxOGL

then I can make the 32-bit version of VBoxOGL.dll load, but it subsequently prints several copies of the following error message:

OpenGL Warning: Host doesn't accept our version 7.1. Make sure you have appropriate additions installed!

and the 32-bit OpenGL application is not 3D-accelerated.
",DRC
6917,Feature request: Prevent guest resolution auto adjust,Windows,other,VirtualBox 3.2.2,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
1435,extremely slow vector graphic performance,other,Windows,VirtualBox 2.0.6,2010-06-07T15:33:49Z,2010-06-07T15:33:49Z,"System configuration:
Virtualbox 1.5.6, 64-bit binary packages on Ubuntu 7.10 host system.
Guest system: either Windows2000 or WindowsXP with guest additions installed.
Remote desktop connection via rdesktop-vrdp from a linux client connected via 1Gb Ethernet to server.

Problem description:
Running some applications that use vector graphics, like CAD systems, is extremely slow. Sometimes it takes several minutes (!!!) to refresh a screen which otherwise would take a split-second to redraw on a ""real"" PC. On WindowsXP the problem is so severe that sometimes VirtualBox just crashes. During redrawing of the screen the guest system seems totally stalled and unresponsive.
I've experienced this problem with ""Zuken CadStar express"" and running a simulation in Octave with FEMM (The simulation is blazing fast, but redrawing the mesh on screen can take up to 3 minutes!).

Additional information:
Running VirtualBox as X-windows client instead of using VRDP, doen't make much of a difference, it is still horribly slow. Doing the test on VMWare-player, it is fast, sometimes about 20-100 times faster that in VirtualBox.
Ethernet network load also doesn't make any difference.
The speed (or slowliness) varies widely for no apparent reason. Sometimes it is just slow, and sometimes it is very slow. It seems as if drawing time increases exponentially with the complexity of the object that is being drawn, that means that simple drawings most of the time render quickly, whereas more complex drawings go in ""bursts"", slowing to a crawl somewhere in the middle. It becomes so slow, that you can count the indivitual lines being drawn on screen.
All other applications (that do no intense vector drawing on screen) run fine at normal speed, interaction is snappy and even transition effects on menus are quite workable.
",yope
2928,Make time sync time function of the Guest Additions optional,Windows,Windows,VirtualBox 3.1.2,2010-06-11T08:26:34Z,2010-06-11T08:26:34Z,"I don't want the time of the guest OS auto-synced by the Guest Additions, but still wish to use other features of it.

Could this function be made OPTIONAL?",helehele
6990,"AIOMgr documentation, transparency needed",Mac OS X,Windows,VirtualBox 3.2.4,2010-06-14T11:06:37Z,2010-06-14T11:06:37Z,"There's nothing much available in terms of AIOMgr documentation. Some of the things I'd like:

 1. recommended system settings to enable AIO (e.g. kern.aioprocmac sysctl on OS X)
 2. several settings are referenced in the logs (cache commit interval, cache commit threshold), but it's not clear where these settings are made and where it might be appropriate to change them
 3. it's not clear where to get metrics to determine whether tunings are working as expected or where problems may crop up in the I/O path

In terms of metrics and debug, I've got a number of cases where CPU utilisation on Windows guests maxes out in the middle of disk I/O, and I can't really tell at what level the problem occurs. I noticed that SAS controllers don't produce metrics at all. Perhaps more importantly, the primary metrics interfaces don't appear to show disk I/O (I can only find this through the session information dialog in the GUI) or allow me to understand how the queuing looks to the guest or how it's being passed on to the host. I can't really understand whether there's some synchronisation problem in the drivers in the guest that are causing the problem or whether the guest is queuing I/O faster than the host is dispatching it, leading Windows to throw a tantrum because I/Os are appearing to time out or some such. As this is an issue where the guest hangs without giving me much in the way of data about whatever it was that caused it to hang (and this is in the middle of things like running Windows Update, so it's not the kind of case where a hang would be expected), it would be extremely useful to be able to observe the guest behaviour as it interacts with the virtualisation layer to get some idea of what's going on in there.",Bayard Bell
6992,Add protections again DHCP rogue activity,other,other,VirtualBox 3.2.4,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
6995,Permit names to be specified for Host-Only adapters,other,other,VirtualBox 3.2.4,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
6985,"""Configuring the BIOS DMI information"" documentation needs improvement",Solaris,Windows,VirtualBox 3.2.4,2010-06-14T12:44:22Z,2010-06-14T12:44:22Z,"I am trying to use the ""VBoxManage setextradata"" feature described in that section of the manual to set up the DMI data so that my VM looks like my actual system, in this case an Acer Ferrari 3400 laptop, so that the version of Windows XP that came with it will install.

However the example given in the documentation does not show which DMI information from dmidecode to use for which parameters.  Several that are shown as being something you can change, like the Release and BIOS Major/Minor values, do not show up in the dmidecode output I see.

I would be very helpful to show example output of dmidecode from a specific system and then show how you use it to set the various values, and what to do if no such value is present.

I have included the full output of dmidecode for my laptop for you to see what it looks like as an attachment to this report.
",Mike Riley
6994,Raise maximum number of Host-Only networks,other,other,VirtualBox 3.2.4,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
7042,retain window geometry after full screen,Linux,Windows,VirtualBox 3.2.4,2010-06-22T09:25:19Z,2010-06-22T09:25:19Z,"The following is a regression since (I think) VBox 3.2.

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

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

Retaining the window geometry (and scroll position) set by the user is very useful when having several guest VMs running side-by-side on one screen for overview, and easily being able to go into Full Screen when a guest needs attention.",Mike Wilson
7083,character encoding munged in CLI on Windows,Windows,other,VirtualBox 3.2.6,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
4789,"""vboxvideo does not export required DRI extension""",Mac OS X,Linux,VirtualBox 3.0.4,2010-07-06T10:28:46Z,2010-07-06T10:28:46Z,"KDE4.3 is unable to enable its effects because Composite is not accessible in X. In X logs, these errors occured:

{{{
(EE) AIGLX error: vboxvideo does not export required DRI extension
(EE) AIGLX: reverting to software rendering
}}}

I will attach complete logs of my (still running) virtual machine, which is running on PUEL 3.0.4, with matching PUEL Guest Additions.",Jacob Godserv
3461,Settings saved in wrong place (WinXP),Windows,other,VirtualBox 2.1.4,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
4238,Option to define shortcuts to be passed to host os,Mac OS X,other,VirtualBox 2.2.4,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
7246,VLAN support for virtual adapters,other,other,VirtualBox 3.2.6,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
682,Binary prefixes,other,other,VirtualBox 1.5.0,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
6632,Virtualbox should warn if you aren't in vboxusers group,other,other,VirtualBox 3.1.6,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
7340,Please make 3D Video card name consistent across APIs,other,other,VirtualBox 3.2.8,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
2152,"Feature Request: allow ""move"" option when changing Snapshots Folder",Windows,Windows,VirtualBox 2.0.0,2010-08-17T09:45:43Z,2010-08-17T09:45:43Z,"I would like the VirtualBox GUI to offer to *move* any existing snapshots, if I change the Snapshots Folder (in the ""Advanced"" tab of the General settings).  Currently, I get the following error message instead:

""The snapshot folder of a machine with snapshots cannot be changed (please discard all snapshots first).""
",Kevin Roth
4754,Suggest a new function to install the VDI file to a real physical hardrive,Windows,Linux,VirtualBox 3.0.0,2010-08-19T20:00:45Z,2010-08-19T20:00:45Z,"Hi, all VBox developers,
I am a 1-year VBox user, fanny about this application.
Thank you all for the masterpiece.

Currently, I have been running Ubuntu(a kind of Linux, as guest OS here) on VBox on Windows(as host OS here) for 1 year and love the Ubuntu OS very much. 
However, how could I put the Ubuntu to a physical hardisk?
That means, how could I write the VDI file to a real phycial hardisk, in which way Ubuntu is on a real and physical machine? 
Is there such a functionality in VBox of next version?

Thanks and waiting. ",jack
7361,Windows XP UNC Benutzername und Passwort läst sich nicht über Ordner suchen hinzufügen,Windows,Windows,VirtualBox 3.2.8,2010-08-21T14:38:55Z,2010-08-21T14:38:55Z,"Auf einem Windows XP Host, kann man bei einem ""Durchuschen""(Ordner suchen)-Dialog(Fenster) auch einen Netzwerkort angeben. Das ist UNC. Normalerweise dann, bei einem Datenzugrif auf diesen Ort, fordert dann Windows XP die Zugangsdaten per Fenster auf, ein zu geben. Jedoch wird bei dem ""Durchsuchen""-Dialog bei Virtual Box nur der Path-String ausgelesen und als lokale Adresse behandelt. Somit erkennt Windows nicht, dass es nötig ist, ein Fenster zu erstellen um die Zugangsdaten (Benutzername, passwort) eingeben zu können.

Jedoch könnte man die Funktion von Virtual Box umschreiben. So dass man da bei dem Fenster ""Gemeinsame Ordner"" gleich die Zugangsdaten mit angeben kann und diese dann entsprechend der Paramter-Syntax mit einer UNC-Connection Funktion übernommen werden.

So mit würde folgender Leistungs-Belastener Schritt nicht mehr nötig:

1. Netzlaufwerk zur Netzwerkquelle auf dem Host erstellen (net use).

2. Erstelltes Netzlaufwerk von Punkt 1, als Quelle bei den Gemeinsamen Ordnern (Virtual Box) eintragen.

3. Netzlaufwerk im Gast-Betriebsystem (Virtual Box Computer) erstellen (net use).",Ines
7407,feature request - double-click action in main window customizable (i.e. open settings instead of starting vm),Linux,other,VirtualBox 3.1.8,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
7419,SSH tunnel headless mode,Linux,other,VirtualBox 3.1.8,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
3340,"Shared folder file creation/deletion not permitted on sub-folders, WinXP SP3 Guest",Linux,Windows,VirtualBox 2.1.2,2010-09-07T04:11:34Z,2010-09-07T04:11:34Z,"Shared folder issues with Virtualbox 2.1.2 running in a ubuntu 8.10 box, with a WinXP SP3 guest.

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

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

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

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

or if I attempt to delete a file I get:

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

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

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

/media/sda6/MYFOLDER: drwxrwx---

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

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

I believe this started happening with VBox 2.0",Ari
7441,"Expose ""--vrdpaddress 127.0.0.1"" in the GUI",other,other,VirtualBox 3.2.8,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
7476,2D Video Acceleration Error Message Should detect platform first,Windows,Linux,VirtualBox 3.2.8,2010-09-15T06:53:51Z,2010-09-15T06:53:51Z,"'''Host:''' Windows XP SP3.[[BR]]
'''Guest:''' Debian Linux

'''Problem:'''  When selecting 2D Video Acceleration, the error message presentation priority is non-helpful.

'''Steps To Reproduce'''
 1.  Start !VirtualBox.
 2.  For your Debian Linux image, click Settings.
 3.  Click Display.
 4.  Set the amount of video memory to 16MB.[[BR]]
 ->  No message is displayed in the lower information pane.
 5.  Click Enable 2D Video Acceleration.[[BR]]
 ->  A message in the lower information pane appears stating that ""On the Display page, you have assigned less than 20MB of video memory which is the minimum amount required for HD Video to be played efficiently.""
 6.  Increase the amount of video memory to 20MB.[[BR]]
 ->  A message appears in the lower information pane stating that ""On the Display page, you have 2D Video Acceleration enabled.  As 2D Video Acceleration is supported for Windows guests only, this feature will be disabled.""

'''Expected behavior:'''  I would expect the system to warn me about how the option is only valid for certain guest operating systems first in priority, and then warn me about the HD video problem.  Thus, I would expect the Windows support for guests only message to appear instead of the HD Video warning.

'''Actual behavior:'''  One has to adjust video memory before discovering that the 2D Video Acceleration option isn't supported for non-Windows hosts.",Jon Polfer
7288,"Shared Folders: on windows guest, linux host. case-sensitive directoryes, but not files.",Linux,Windows,VirtualBox 3.2.6,2010-09-22T12:28:31Z,2010-09-22T12:28:31Z,"
example of bug:

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


shared folder placed on XFS partition of host.

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

Why are the directory names are case-sensitive, but filenames not? How to fix?",Jury
1752,Software Installation not passed Windows Logo testing,Windows,other,VirtualBox 1.6.2,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
7546,Print Screen does not work on Windows XP if Virtual Box has Focus,Windows,other,VirtualBox 3.2.8,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
721,Feature request: ieee1394 (Firewire) UHCI/OHCI pass-through support,other,other,VirtualBox 1.5.0,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
7036,"""Check for update"" turned on, automatic vm start, when update available, access blocked",Windows,Windows,VirtualBox 3.2.2,2010-10-17T23:27:46Z,2010-10-17T23:27:46Z,"Hi,

a very strange ""error"". Situation: 

- automatic checking for updates once a week is turned on
- vm is started automatically from batch with vboxmanage StartVM
- vm was restoring from Saved State, vm restored correctly
- VirtualBox update occurred

All started well, and there was a modal dialog notifying that there is an update, but wherever I tried to click, on OK button in dialog or inside the vm, Windows produce a sound ""you can't click there"". The vm was also not visible in Alt+Tab list.

The only way to was to force Save State with ControlVM.

",vlatko
7570,VNC shows password in commandline,other,other,VirtualBox 3.2.10,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
7646,Keyboard and mouseclick disabled at windows host with 'view login sceen at resume',Windows,other,VirtualBox 3.2.10,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
1194,Request for seamless VRDP feature,other,other,VirtualBox 1.5.4,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
7681,extended keyboard layout support under the builtin vnc server (OSE),other,other,VirtualBox 3.2.10,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
7694,Add SCSI device passthrough support,other,other,VirtualBox 3.2.10,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
7727,Keyboard should be released to host when mouse moves outside of Vbox window,Linux,Windows,VirtualBox 3.2.10,2010-11-17T08:50:27Z,2010-11-17T08:50:27Z,"Currently, it takes two user actions to release the keyboard:
  a) move mouse off the vbox window
  b) click the mouse

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

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

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

As a point of reference, a Large Commercial Virtualization package works this way.  It does not require the extra mouse click.",mtnbiker
7749,Vboxsf has no read caching on linux,Mac OS X,Linux,VirtualBox 3.2.10,2010-11-21T15:20:48Z,2010-11-21T15:20:48Z,"There is no read caching implemented on volumes mounted via vboxsf on linux guest.
Read cache may improve vboxfs performance dramatically.

For testing try executing 
{{{
time cat any_long_file > /dev/null
}}}
on mounted host fs multiple times. Time to read file does not change. That means there is no caching done on that file.
Dong the same i.e. on vmware fusion shares makes subsequent reading almost instant.",Slava Nadvorny
7761,additions install on Xen kernel,Windows,Linux,VirtualBox 3.2.10,2010-11-24T21:35:36Z,2010-11-24T21:35:36Z,"Apparently, Linux Guest Additions are not working on Xen kernels. Unfortunately, I did not know about this limitation, because the Additions installer appeared to install OK. Sure, it installed OK, but should it even try to install?",Luci S
7763,configure needs to check for glib2,Mac OS X,other,VirtualBox 3.2.10,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
7773,USB does not work with NIS or LDAP login,Linux,other,VirtualBox 3.2.10,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
6600,VBoxService.exe does not terminate in os/2 guest,Linux,other,VirtualBox 3.1.6,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
7791,"If disk images are on a shared storage(eg. samba), clients crashes if there is networking error.",Windows,other,VirtualBox 3.2.12,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
7804,"When mounting shared host files with vboxsf, softlinks fail to be copied.",Linux,Linux,VirtualBox 3.2.12,2010-12-07T20:23:47Z,2010-12-07T20:23:47Z,"Description:

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

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

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

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

",V
7816,"CPU Idle load hi with ""divider=10""",Mac OS X,Linux,VirtualBox 3.2.12,2010-12-10T02:57:43Z,2010-12-10T02:57:43Z,"Idle load with CentOs 5.5 client on OSX 10.6.5 host is ~ 75%. I added ""divider=10"" to grub.conf post additions, and have rebooted the client and the application; still idle load is high.

",Dale Douglas
7820,[feature-request] Scale Mode: OpenGL 3D Accelerated graphics should scale,other,other,VirtualBox 3.2.12,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
7824,[feature-request] Scale Mode: should optionally produce window w/ menus,other,other,VirtualBox 3.2.12,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
7825,"[feature-request] Scale Mode: please make it work with ""Mouse integration""",other,other,VirtualBox 3.2.12,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
7836,[feature-request] Floppy: Create Virtual FAT images from host's filesystem,other,other,VirtualBox 3.2.12,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
7843,"VBox host-only network is reported as ""Unidentified Network"" and Public on Windows7 hosts",Windows,other,VirtualBox 3.2.12,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
7828,[feature-request] Voodoo 3DFX emulation,other,Windows,VirtualBox 3.2.12,2010-12-16T21:19:14Z,2010-12-16T21:19:14Z,"Add Voodoo 3DFX emulation for legacy gaming and other uses in DOS and Windows 9x. The emulation already exits in MAME and is being ported to DOSBox. I feel this would be a good addition to VirtualBox and probably simpler than some other ideas proposed for legacy gaming.

http://mamedev.org/",Zombiedeth
7896,VB creates wrong .vmdk on Mac OSX,other,other,VirtualBox 4.0.0,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
7897,Only one IP of multi-homed guest is visible,Linux,Windows,VirtualBox 3.2.12,2010-12-24T08:03:51Z,2010-12-24T08:03:51Z,"I have a Windows guest that is multihomed (multiple IPs to single NIC).  The host's NIC is bridged so traffic should be passed for both IPs.  However, from the outside network, I can only ping the first IP address assigned to the guest NIC.  Inside the guest, I can ping the first and second IP addresses assigned to the guest NIC.  This is why I believe this is a bug in the host interface bridging code.

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

The vbox.log is attached.",Ken Yee
7965,Remove confusing geeky-internal VirtualBox snapshot language from GUI,other,other,VirtualBox 3.2.12,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
7954,Different VBox question text deleting snapshots w/o merging,other,other,VirtualBox 4.0.0,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
8011,VBoxManage/GUI does not detect VMs started by another user,Windows,Windows,VirtualBox 4.0.0,2011-01-06T15:58:46Z,2011-01-06T15:58:46Z,"If a VM is started by the Windows Local System account (for example, if started by ""VBoxVMService""), then neither VBoxManage nor the GUI when executed by a regular user or administrator will show the VM as running. The status of a VM should be machine global and visible to all users.
",DavidN
8020,Add appropriate comments for strings that are used in other strings (in translation *.ts files),other,other,VirtualBox 4.0.0,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
375,Integrating VirtualBox Linux additions upstream (X.org),other,Linux,VirtualBox 1.3.8,2011-01-08T07:25:05Z,2011-01-08T07:25:05Z,"hi all !

I believe that there is a sense in pushing VBox Linux additions into upstream X.org: namely the VBox graphics driver and VBox Mouse driver.

By doing so, we will eventually have VBox supported out-of-the-box even on LiveCDs, and during install stage !

Additionally, by going this way, we can receive support for BSD and Solaris guest additions from open-source community for free. (Solaris and BSD UNIX uses X.org too)

The downside:

Inability to change the VBox graphics and mouse drivers interface between host and guest. This means that future versions of VBox must stay compatible with 1.3.x in this regard in API level.

What do you think about it? Do you want me contacting X.org ?

The same topic exists in forum:
http://forums.virtualbox.org/viewtopic.php?t=239

-Alexey ""Technologov""",Technologov
5811,Feature-request: New Storage GUI: VM/Storage Settings,other,other,VirtualBox 3.1.2,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
2120,Exposé shortcuts don't work,Mac OS X,Windows,VirtualBox 2.0.0,2011-01-09T16:39:25Z,2011-01-09T16:39:25Z,On OS X 10.5.4 (locale FR-fr) the Exposé shortcuts (screen edges) are not aviable when the focus is on a VirtualBox window.,Simon Delalay
6495,VBox DHCP Server does not respect client identifier,other,other,VirtualBox 3.1.6,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
7837,Feature Request: Option to hide Additions mismatch warning,other,other,VirtualBox 3.2.12,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."
8099,Email address trac@virtualbox.org not found,other,other,,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
33,"Better icon for ""Guest Additions"" entry in ""Add/Remove Programs""",other,Windows,VirtualBox 1.3.4,2011-01-18T20:05:41Z,2011-01-18T20:05:41Z,"After installing GuestAdditions for Windows, I see that there is no specific icon exists in Windows 2000/XP in Add/Remove programs on Guest VMs.

Recommendation:

make some kind of icon. MS Virtual PC 2004 uses ""puzzle"" icon for it's guest additions.",Technologov
7952,gues key mapping problem while host is using XkbOptions,Linux,Linux,VirtualBox 4.0.0,2011-01-19T02:02:53Z,2011-01-19T02:02:53Z,"My host is archlinux with xorg 7.6, and i am using XkbOption for some key mapping workaround, like blow:


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


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

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

It seems that virtualbox has ignored the XkbOptions and accesses the keyboard as is.",Zer4tul
8144,Dock does not show up anymore after switching between applications,Mac OS X,Linux,VirtualBox 4.0.2,2011-01-21T16:51:00Z,2011-01-21T16:51:00Z,"Steps to reproduce:
 * Enable the option ""show dock and menu bar in full screen mode automatically""
 * Switch VM to full screen mode
 * When I move the mouse to the top border, the menu bar shows up. When I move mouse to the left border, the dock shows up. (I have my dock configured to the left side of the screen.) This is the expected behavior.
 * I click on the icon of some other application in the dock. The windows of this application show up.
 * I click on the icon of the VM in the dock or (makes no difference) click in the VM desktop in the background. The windows of the other application and the dock disappear.
 * When I move the mouse now to the left border, nothing happens. The dock does not show up anymore. However the menu bar on the top border still shows up if I move the mouse there.
 
Hiding the VM and the reentering the VM does not change anything, the dock still does not work anymore. What helps is switching off and then on again the full screen mode. Then the dock works again, until the next time.",cmr
8147,Adding devices to virtual SCSI controller will use reserved port 7,Windows,Linux,VirtualBox 4.0.2,2011-01-22T15:26:00Z,2011-01-22T15:26:00Z,"Hi! Fantastic work on VBox, thank you so much! I think the V4 is better than VMware :)

If this guy is right - http://forums.virtualbox.org/viewtopic.php?f=1&t=38319&start=0 - i.e. that the SCSI port 7 is reserved for the host adapter ID (or something more accurate, not a SCSI-savvy guy myself), then there's a bug in the interface when adding devices to the virtual SCSI controller. It will automatically assign the new device to port 7 when ports 0 thru 6 are already occupied, and you end up with missing devices in your OS (at least in my Ubuntu OS ;)",Daniel Smedegaard Buus
8148,Guest pre-boot check cycle of .vmdks with raw disks does not detect mismatch in drive geometry,Windows,other,VirtualBox 4.0.2,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
5130,"Bridging eth0 needs ""link"" in order to work",Linux,Linux,VirtualBox 3.0.6,2011-01-26T12:41:31Z,2011-01-26T12:41:31Z,"Ran into problem when trying to bridge virtual Ubuntu 9.10 with host Fedora 11 using the distributions VBox-packages. Using NIC eth0 (Thinkpad T61)

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

kernel: 2.6.30.8-64-fc11.i586
VBox 3.0.6

I don't have a problem with the issue as there is a easy workaround, but one have to be aware of it.",Niklas Andersson
6323,Can't get IP Forwarding to work with Host-only adapter,Linux,Linux,VirtualBox 3.0.6,2011-01-26T12:41:53Z,2011-01-26T12:41:53Z,"Hello, 

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

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

[*]1 bridge br0

[*]2 tun/tap interfaces tap0 and tap1


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

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

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

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

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

Thank you, 

Laurent Sebag",grattemedi
8192,seamless mode problems when moving/minimizing guest's windows,Linux,Windows,VirtualBox 4.0.2,2011-01-26T23:29:38Z,2011-01-26T23:29:38Z,"Host: Ubuntu 11.04
Guest: Windows XP SP3

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

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

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

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

In order to recover, I usually have to switch out of seamless mode and back in. Sometimes moving around other guest windows or clicking in another guest window will fix it.
",Chuck Cox
8048,Restless Guest window's preview,Windows,other,VirtualBox 4.0.0,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
8203,GUI highlighting of running VMs,other,other,VirtualBox 4.0.0,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
7143,Please expose the IgnoreFlush option to the GUI,other,other,VirtualBox 3.2.6,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
8282,Mini Toolbar/Quickbar unavailable if fullscreen changed to other host screen,Windows,Linux,VirtualBox 4.0.2,2011-02-05T22:51:59Z,2011-02-05T22:51:59Z,"I am using 4.0.2 on Windows Vista host. (guest should be irrelevant, but is linux in case)

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

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

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

Switching temporarily to window mode, and back to fullscreen fixes the issue (as a work around) until the next host-monitor switch",Martin
8302,Avoid showing VirtualBox GUI when starting in seamless mode,other,other,VirtualBox 4.0.2,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
6519,Network bridge does not work with multiple mac addresses on the guest side,Linux,Linux,VirtualBox 3.1.6,2011-02-19T18:34:59Z,2011-02-19T18:34:59Z,"The Bridged network mode seems to be unable to deal with multiple MAC addresses being used to send packets from a guest. This situation occurs when a network bridge is configured inside a guest system.

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

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

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

A reasonable alternative to accepting *all* packets would be to enlarge the MAC address buffer, but this would require a far more complex network switch implementation.",Ivo Smits
4876,A duplicate name exists on the network - Windows Error,Windows,Windows,VirtualBox 3.0.4,2011-02-20T22:58:44Z,2011-02-20T22:58:44Z,"VirtualBox Guest has problems with DHCP leases managed by ASUS Wireless Router RT-N11 (host connected by cable).

Guest does the DHCP has grabs an IP address although it is not accessible by the network name, only by IP address.

See images attached.",XoK
8393,A way to define key-combinations which always are passed to the Host OS,Windows,Windows,VirtualBox 4.0.4,2011-02-21T18:37:36Z,2011-02-21T18:37:36Z,"I commonly run certain utilities in my host OS which are useful whether I'm in the guest OS or not. I would like to be able to set up ""pass through shortcuts"" which always get passed to the Host.

For example the NextAction task list manager always activates with Windows+Z but I run it on my host machine. I would like to be able to set up virtual box so the guest machine does not capture Windows+Z.",George Mauer
8404,"window backup (wbadmin) restore error ""Cannot enumerate files"" if guestadditions installed.",Windows,Windows,VirtualBox 4.0.4,2011-02-22T20:00:27Z,2011-02-22T20:00:27Z,"Guest Windows 2008 Server (32bit) as DC role. Guest edition 4.0.2 installed, 4.0.4 running. 

Perform windows full vss backup, with windows backup to attached disk.

Boot into DSRM and attempt a system state restore.

wbadmin start systemstaterecovery -version:xxxx -backuptarget:E: -authsysvol

Errors with ""cannot enumerate file""

If the guest edition is removed, a restore can be made.

Comments on the net suggest that this might be due to the path names of the vboxservice in the registry. However a brief examination of the service keys did not show anything unusual to my eye.



",John Huttley
8426,Unable to lock down VBOX COM using DCOMCNFG,Windows,Linux,VirtualBox 4.0.4,2011-02-24T19:59:23Z,2011-02-24T19:59:23Z,"I need to install VirtualBox in an environment that permits only a special user (vboxuser) to control virtual box.[[BR]]
[[BR]]
The problem is that on Windows XP, locking down VirtualBox is not working (could be a windows bug), any user can launch with VBOXSVC and then have complete control over VirtualBox (if the set VBOX_USER_HOME properly). Windows 7 works fine (UAC on and off).[[BR]]
[[BR]]
[[BR]]
Here are the steps to lock down the COM service:[[BR]]
1- Install virtualbox under any admin user[[BR]]
2- Create a new user (vboxuser), make it an admin.[[BR]]
3- Login to vboxuser and start DCOMCNFG as admin[[BR]]
4- Select Component Services --> Computers --> My Computer --> DCOM Config[[BR]]
5- Locate VirtualBox then right click on open Properties[[BR]]
6- Select Security Tab[[BR]]
7- Change Launch/Activation to SYSTEM and vboxuser (local launch and activation)[[BR]]
8- Change Access to SELF,SYSTEM and vboxuser (local access)[[BR]]
9- Change Configuration to SYSTEM, vboxuser (full control)[[BR]]
10- Click OK and make sure that virtualbox.exe can start under vboxuser[[BR]]
11- logoff from vboxuser and then log back in to your user.[[BR]]
12- Start virtual box, and it starts! That is the problem.[[BR]]
[[BR]]
On Windows 7 you would get an error (Access Denied) and it would only work if I use runas /user:vboxuser virtualbox.exe.[[BR]]
[[BR]]
The problem happens only on Windows XP SP3 x86 (I haven't tested any x64 versions)[[BR]]
[[BR]]
I tested another COM service, and the permissions seem to work on Windows XP.[[BR]]
Please let me know if you have any questions[[BR]]
[[BR]]
I was able to reproduce this problem using VBOX 4.0.4 and VBOX-OSE 3.2.18 (self compiled/installed)",rbhkamal
3593,Fixes for UserManual.pdf,other,Windows,VirtualBox 2.1.4,2011-02-24T21:15:21Z,2011-02-24T21:15:21Z,"I've read portions of UserManual.pdf and have some suggested corrections...

page 66
{{{
4  The VirtualBox Guest Additions 
• Linux or Solaris/OpenSolaris guests with an X.org server version 1.3 or higher, 
except Fedora 9, due to a bug in it’s X server1 (support added with VirtualBox 
1.6). 
}}}
""it's"" should be ""its""

page 67
{{{
4.9 Guest properties 
...
These predefined properties are all preﬁxed with “/VirtualBox/“ and organized into a hierarchical tree of keys. 
}}}
the trailing quote is actually an open quote...

page 71
{{{
VirtualBox will always present at least the IDE controller device to the guest. Even 
if your guest operating system does not support SATA (AHCI), it will always see this 
IDE controller and the virtual disks attached to it. 
}}}
""even if ... does not ... SATA ... see IDE"" doesn't make sense, the ""not"" should probably be elided.

page 80
{{{
6.4.3 NAT limitations 
...
As a consequence, NetBios name resolution based on broadcasts is not always working (but WINS always works). 
}}}
""is not always working"" sounds odd, ""does not always work"" ?

page 81
{{{
1 
For Mac OS X and Solaris hosts, net ﬁlter drivers were added already with VirtualBox 2.0
}}}
were already added in ...
{{{
With VirtualBox 2.1, net ﬁlter drivers were 
also added for the Windows and Linux hosts, replacing the mechanisms previously present in VirtualBox 
for these platforms;
}}}
these => those ?

{{{
None of this is necessary any more. 
}}}
anymore

page 82
{{{
– A VNIC cannot be shared between multiple guest network interfaces, i.e. 
each guest network interface must have it’s own, exclusive VNIC. 
}}}
its own

page 85
{{{
First, VBoxManage must always be used with a speciﬁc “subcommand”, such as “list vms” or “createvm” or “startvm”. All the subcommands that VBoxManage supports are 
}}}
""list vms"" isn't a subcommand, ""list"" is.

page 87
{{{
7.4 Remote virtual machines (VRDP support)
}}}
should mention Remote Desktop for OS X

page 122
{{{
Keep in mind that on Windows hosts a named pipe must always start with \.\pipe\“. 
}}}
opening quotes at the end of a string w/o matching open quotes....

page 128
{{{
9.16 Enabling SCSI controllers in the guest 
As said in chapter 5.1
}}}
As mentioned in ...",timeless
8460,Mouse events don't come to the guest while snapshot deletion is in progress,Mac OS X,Linux,VirtualBox 4.0.4,2011-02-28T18:36:42Z,2011-02-28T18:36:42Z,"Ubuntu guest doesn't get any mouse events while snapshot deletion is running when launched from the main vbox window. Progress dialog is active.

This is unreasonable to affect guest this way since past snapshot deletion has nothing to do with the guest's current state.",yurivict
4682,"Remove ""Create Quick Launch Icon"" from installer on Windows 7 and above",Windows,other,VirtualBox 3.0.4,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
8141,Clipboard sharing between 3 machines / security issue?,Linux,Windows,VirtualBox 4.0.2,2011-03-01T16:04:51Z,2011-03-01T16:04:51Z,"I've recently run into a scenario that is a bit troubling. I have two desktop Ubuntu Lucid machines, let's call them D1 and D2, and two users working on them, U1 on D1 and U2 on D2. U1 has VirtualBox running a Windows VM (V1) with D1 as a host. User U2 has a RDP connection opened to V1. 

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

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

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

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

",Adrian Roman
8477,Cannot use Windows clipboard when connected to host and guest via RDP,Windows,Windows,VirtualBox 4.0.2,2011-03-02T16:54:48Z,2011-03-02T16:54:48Z,"Configuration:

Laptop:  Windows XP
Virtualbox Host: Windows 2003 Standard
Virtualbox Guest: Windows 2003 Standard

If I am connected to both the Virtualbox Host and Virtualbox Guest via RDP the clipboard fails to work.  Also it looks like it locks up the local application that I am copying from. 

For example If I copy something from either Excel or notepad and I want to past it into notepad on the VirtualBox host or any Windows Virtualbox Guest, the paste will not work and the source app will be locked until I either disconnect either the RDP connection to the VirtualBox Host or VirtualBox Guest.

If a RDP connection is open to only the VBOX Guest or VBOX Host it works fine.
",Shawn McCloskey
8481,Failure when non-existing uppercase and underscore directory,Linux,Windows,VirtualBox 4.0.4,2011-03-03T09:18:43Z,2011-03-03T09:18:43Z,"1. Ubuntu 10.10 Host
2. Windows XP Guest
3. VirtualBox-Guest-Tools 4.0.4
4. Shared Folder called ""Share"" pointing to ~/Share

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

6. Try to access \VBOXSVR\Share:

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

Falscher Parameter."" 

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

Wrong parameter.""


If you try the same with ""hello_world"" or ""HELLO"" or ""HELLO_WORLd"", there will be no error.",garfield
8485,Differencing disk created from multiattach base disk is marked as auto-reset,Windows,Windows,VirtualBox 4.0.4,2011-03-03T19:08:39Z,2011-03-03T19:08:39Z,"According to the [http://www.virtualbox.org/manual/ch05.html#hdimagewrites VirtualBox] docs:
  ''Technically, a ""multiattach"" image behaves identically to an ""immutable"" image '''except the differencing image is not reset every time the machine starts'''.''

This doesn't appear to be the case.

I created a VM with a dynamically sized disk, installed Win7, sysprepped the VM and shut it down. I released the HDD and used '''VBOXMANAGE MODIFYHD ... -TYPE MULTIATTACH''' to mark this HDD as immutable and that children should not auto-reset.

I then created a new VM, using the base HD which created a differencing disk for its own data.

Using '''VBOXMANAGE SHOWHDINFO ...''', I examined the new VM's differencing disk and saw that it claims auto-reset is on.

I booted the new machine, completed the OOBE (Out Of Box Experience) and modified the desktop wallpaper. I shut down the VM and then rebooted it and was sent straight back to the OOBE again.

VirtualBox is a great product, but its poor handling of differencing disks, requiring users to delve around in the command-line tools to configure even the most rudumentary differencing scenarios, is, in my opinion, VirtualBox' biggest weakness, especially when compared to Hyper-V and VMWare.

PLEASE fix this bug and consider improving VirtualBox' GUI for handling differencing disks.",bitcrazed
8551,DOS applications dosn't work with VBox Guest Additions shared folders,Windows,Windows,VirtualBox 4.0.4,2011-03-13T00:38:18Z,2011-03-13T00:38:18Z,"Hello,

There is a problem with DOS applications working on folders shared through VBox Guest Additions.

The test configuration is:
  Host:  Win XP, 32-bit /problem also confirmed on Win7 64-bit host/

  Guest: Win XP, 32-bit

  Shared folder: 'D:\' on host shared as 'D'; Drive F: on the guest is mapped to \vboxsvr\D;
  
Problem: A DOS application running on the guest cannot find any file residing on a shared folder. The standard DOS FindFirst function call (INT 21/AH=4E) always fails despite there is files matching to the search criteria. For example FindFirst(""F:\Temp\*.*"") always got error is 0x12 (NO MORE FILES), but there are files in F:\Temp. Furthermore if you call GetExtendedError (INT 21/AH=59h) afterwards it reports error 0xEA which looks meaningless and unrelated to the error returned by FindFirst.

The problem occurs only if you are searching for files on a shares through VirtualBox Guest Additions. It's working correctly with classic SMB network shares.

I tested FindFirst for files on a network drive (e.g. drive 'G:' mapped to a network share) and it works. But if you map G: to \vboxsvr\some-shared-folder then you always got error as described above.

Another test by running 4DOS command shell on the guest shows similar behaviour (4DOS is a popular 16-bit DOS shell like COMMAND.COM). If you type ""dir F:\*.*"", where F: is mapped to \vboxsvr\some-shared-folder you see empty directory listing.

Described problem also appears also on a different machine with Windows 7, 64-bit host.",Dimitar Nanev
8597,"When connect to windows server guest by use Terminal Services, the VBoxTray.exe use half of my CPU",Windows,Windows,VirtualBox 4.0.4,2011-03-20T15:34:24Z,2011-03-20T15:34:24Z,"Hi

I think I find a bug here:

I was try Windows Server 2003 SP2 on VirtualBox 4.0.4, and install the Terminal Services, and set the network to be Bridged.

Now when I connect the Windows Server by use Remote Desktop Connection, VBoxTray.exe will use half of my CPU.",vibbow
3473,alt+printscreen and windows-logo+E  used to work but now do not,Solaris,Windows,VirtualBox 2.1.2,2011-03-21T16:26:07Z,2011-03-21T16:26:07Z,"Hi,

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

   ( in all cases below guest additions were installed )

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

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

In 2.1.2 I no longer can.

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

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

If I can be of help to a developer I'm happy to try things out.
",cj
8625,Shared Floppy Images cannot be accessed from several VMs,other,other,VirtualBox 4.0.4,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
6271,"During Clonezilla Live CD Process, Text Only display shifts down so bottom lines appear off screen",other,other,VirtualBox 3.1.4,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
8637,Inappropriate Runlevel for openSUSE 11.4,Linux,other,VirtualBox 4.0.4,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
8664,vboxsf causing kernel panic with mounted loopback file system after restore from suspend,other,other,VirtualBox 4.0.4,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
8704,[feature-request] Mini-toolbar: allow to switch between VMs,other,other,VirtualBox 4.0.4,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
8360,"when using existing ubuntu as a guest, vbox replaces xorg.conf",Windows,Linux,VirtualBox 4.0.4,2011-04-13T13:39:34Z,2011-04-13T13:39:34Z,"I have a win7/ubuntu10.10 dual-boot. I installed virtualbox on win7 (host)
I followed these instructions http://chaits.accosted.net/?p=54 and created an instance out of an existing linux partition.
after I installed vb additions and extension, everything worked great in virtualbox. when i tried to boot into linux, the windows manager didn't lunch. xorg.conf was overwritten. 

Currently I have to sitch xorg.conf file manually if i want a graphical interface. 
i documented my experience [http://kirilligum.wordpress.com/2011/02/17/run-existing-linux-ubuntu-10-10-partition-in-virtualbox-under-host-windows-7-system-on-thinkpad-x201t/ here].",kirill
8719,Mouse pointer calibration issue in seamless mode,Mac OS X,Linux,VirtualBox 4.0.4,2011-04-14T08:23:36Z,2011-04-14T08:23:36Z,"When using seamless mode, the mouse becomes decalibrated, pointing around 50px directly above the cursor.

The only way that I have found to fix it is cycle the guest, but it happens again very quickly.",Mashi
8730,Portability: please allow to move VMs with Bridged NIC attached,other,other,VirtualBox 4.0.4,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
8764,Regression: VirtualBox and VM configuration broken if VM folder exists,Linux,other,VirtualBox 4.0.6,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
7642,[feature-request] Reverse Shared Folders,other,other,VirtualBox 3.2.10,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
8808,Add option to stop machine on error warning,other,other,VirtualBox 4.0.6,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
8828,Back button in program installer doesn't work,Windows,other,VirtualBox 4.0.6,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
8819,Keyboard layout 'Programmer Dvorak',Linux,other,VirtualBox 4.0.6,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
8847,Feature Request: Multiple Tabbed Interface,other,other,VirtualBox 4.0.6,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
8848,Feature Request: Ability to map VDI to Windows and use them as a harddrive,Windows,Windows,VirtualBox 4.0.6,2011-05-04T22:40:54Z,2011-05-04T22:40:54Z,"Ability to map vdi to windows and use them as a harddrive storage directly. Windows doesn't have easy way loop-mount facility. This will require writing Windows-host SCSI driver to make it work. Possible, but hard.",DNS
8849,Feature Request: Snapshot Immutable Images and Enhanced Branching,Windows,Windows,VirtualBox 4.0.6,2011-05-05T06:39:38Z,2011-05-05T06:39:38Z,"Snapshots:
Snapshots in VMware 7 have a number of advantages: 
They have automatic snapshots every few days + ability to create new VM from snapshots (aka differencing-immutable images).

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

It would be very useful. Thanks for considering.",DNS
8862,launchd recipe for vboxwebsrv doesn't work,Mac OS X,other,VirtualBox 4.0.6,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
4562,[feature-request] 'Default Gateway' parameter in DHCP server for host-only networks,other,other,VirtualBox 3.0.2,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
8789,Shared Folders doesn't honor guest OS DAC settings,Solaris,Windows,VirtualBox 4.0.2,2011-05-09T19:33:13Z,2011-05-09T19:33:13Z,"When using VBoxHeadless vrdp -off and set a mount point on the NFS shared (/export/home/COMMON_SHARE) we noticed that the files that are copied to NFS share from the guest OS show DAC root:root instead of the user DAC settings from the guest OS. The user account exists on both Host and Guest (same UID/GID) example testuser1/staff.

Guest OS: Windows Server 2003 STD R2
Host OS: Solaris 10 v10/09
Extension pack for 4.0.2 installed",Ronald MacDonald
8855,"Windows XP netcard doesnt work with ""VirtualBox Bridged network driver"" enabled",Windows,other,VirtualBox 4.0.6,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
8877,Ethernet frame larger than 1500 do no pass through bridged ethernet connection,other,other,VirtualBox 4.0.6,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
8686,Change process directory to / before forking,other,other,VirtualBox 4.0.4,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
8904,Missing license information in About Virtualbox window,other,other,VirtualBox 4.0.8,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
8606,Files remain installed and locked by Windows after uninstall or upgrade,Windows,other,VirtualBox 4.0.4,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
8731,Cannot use bond0 on Mac OS X 10.6.7 and some other errors...,Mac OS X,Linux,VirtualBox 4.0.4,2011-05-17T18:45:46Z,2011-05-17T18:45:46Z,"When I created a LACP link on a Mac OS X server 10.6.7 , I can't use it as an interface with VirtualBox. It would complain something about 

My guest is Ubuntu 10.04 64-bit. I also noticed that I saw what seemed like disk errors during the bootup of the guest..

attached are the log files.",John Huong
8929,undoc'd Windows XP  trick does not work in virtualbox (active partitons),other,Windows,VirtualBox 3.1.2,2011-05-21T02:43:10Z,2011-05-21T02:43:10Z,"do this on a real computer:
run UBCD and mark the sole partition of your computer active using MMC. reboot without disk, and you should receive error: NTLDR missing. Press Ctrl+Alt+Del to reboot.

then i copy contents of windows drive to the disk and it runs because NTLDR is copied.


do the same in virtualbox and i get FATAL: No bootable medium found! system halted.
obviously a virtualbox error, not seeing the active partition on the virtual drive.

This virtual drive was created using version 1.62 as i was using a win2k host at the time, but the copying was done using the 3.1.2 (and failed to boot), and tried running it on 4.0.8 and not going.

UBCD mmc still reports there is a single partition on the drive, and is active. 160GB drive, 48GB partition.

currently vista host 4.0.8
and not yet a XP sp1 guest.

cb.",Charlie
6074,Permission denied to access shared folders on Windows when folder contains broken symbolic link,Linux,Windows,VirtualBox 3.1.2,2011-05-25T12:52:29Z,2011-05-25T12:52:29Z,"Host: Ubuntu 9.10 AMD64 Guest: Windows XP 32bits

For some reason, Windows prevented me to access a shared folder by telling me I need administraor privileges to access it (while I have them).
I noticed that I have some broken symbolic links on the ext4 filesystem of that folder. After removing them, access to the folder was granted by Windows guest os.",Ankhterus
8960,Virtualbox Unity Launcher Integration,Linux,Linux,VirtualBox 4.0.4,2011-05-26T15:48:30Z,2011-05-26T15:48:30Z,"Hello,

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

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

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

It's registered under the MIT license.",Daniel
8974,--bootable=off doesn't apply to IDE controller,other,other,VirtualBox 4.0.8,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
8969,"Mouse clicks move mouse pointer, and mouse not properly captured",Linux,Windows,VirtualBox 4.0.8,2011-05-27T20:39:30Z,2011-05-27T20:39:30Z,"Running VirtualBox 4.0.8 (32 bit) on Fedora 14 (32 bit) with guest Windows XP SP3 (32 bit, 1024x768). The host has a single display (1280x1024), PS/2 mouse, window manager is fvwm2. Everything was fine about 3 months ago (IIRC that was with VBox 4.0.4).

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

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

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

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

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

Same problem with different screen resolutions within the guest system.

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

I'll append a VBox.log but there are not errors in it.
",Andreas M. Kirchwitz
8982,CoDeSys on windows xp work with time delays,Linux,Windows,VirtualBox 4.0.8,2011-05-28T16:37:12Z,2011-05-28T16:37:12Z,"I´am using CoDeSys(a SoftSPS)on windows xp.
The guest get delays from 2sec up to 10 sec when I switch between CoDeSys and envince(pdf-viewer) until the switch finished which make working time expensive.
There are also delays between the call of the functions/views within CoDeSys.
Also the whole guest seems to be slowed down when I call services/widgets/programms.

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

3D support is enabled.

For getting the program(not a one stop shop):
http://www.3s-software.com/index.shtml?de_contact",maninred2
3458,Shared Folders failing on access,Linux,Windows,VirtualBox 2.1.4,2011-05-28T16:46:15Z,2011-05-28T16:46:15Z,"Ubuntu 8.10 64-Bit host, Windows XP SP3 32-Bit guest.

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

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

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

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

",Robert
8991,Virtualbox breaks virtual machines if the host dies unexpectedly,Windows,Linux,VirtualBox 3.0.8,2011-05-30T19:50:14Z,2011-05-30T19:50:14Z,"If a virtual machine is running and the host shuts down unexpectedly from processor overheating, BSoD or power failure, about 50% of the time, it breaks the VM.
It breaks the actual settings file and not the HD image.
Sometimes it shows
----------------------------------------------------------------------------
Could not load the settings file 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml'.
Premature end of data in tag VirtualBox line 3.
Location: 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml', line 77 (3), column 5.
Result Code: 
VBOX_E_XML_ERROR (0x80BB000A)
Component: 
VirtualBox
Interface: 
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
---------------------------------------------------------------------------
And sometimes it hangs for no apparent reason when trying to start of modify the VM.
I can create a new VM with similar settings and reattach the disk image and it works fine but this is an annoyance. The VMs seem excessively fragile.
BTW I just realized I am using a very old version.

",smeezekitty
9006,Guest Additions: Fails to detect multiple IP addresses on the same NIC,other,Windows,VirtualBox 4.0.8,2011-06-01T13:50:49Z,2011-06-01T13:50:49Z,"Host: Win 7 x64 + VBox 4.0.8
Guest: Windows XP + GA 4.0.8

As part of GNS3 Network Simulator tests, it became clear that VBox GA give incomplete information regarding multiple IP addresses.

Specifically, if I configure several IP addresses on single NIC, Guest Additions must show the MAC address of all logical interfaces. Currently MAC address is omitted for secondary IP addresses.

-Technologov, 1.Jun.2011.",Technologov
9031,Add option to handle URLs in guest on host,Windows,Windows,VirtualBox 4.0.8,2011-06-06T14:33:33Z,2011-06-06T14:33:33Z,"It would be really useful if Guest Additions could (optionally?) add a handler for URLs that would pass them through to the host.

My use case is Outlook running on a Win7 Guest.  I'd prefer if links in Outlook opened on my Host instead of in the Guest. Others at my work have a similar use case, as well as [http://superuser.com/questions/140234/is-there-a-way-to-redirect-a-click-on-a-url-in-a-virtualbox-guest-to-open-in-th others] outside my work.

Ciao!",Christian Höltje
9038,VNC Screen Repaint Delay,Linux,Linux,VirtualBox 4.0.8,2011-06-07T00:28:00Z,2011-06-07T00:28:00Z,"If I reconnect to a system that has been online for a few hours, the screen is usually completely black. Clicking around on the screen slowly causes it to invalidate regions and cause paint updates. The host and guest systems are recent releases of ubuntu. This behavior occurs regardless of the VNC client used. It was not a problem in 3.2.12. The guest system has Guest additions 4.0.8 installed, but I have seen this behavior occur with guest additions 3.2.10 even on a 4.0.8 system.

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

Also, the display is configured to never go to sleep in ubuntu.",kihjin
9041,The example python script src/VBox/Frontends/VBoxShell/vboxshell.py,Linux,other,VirtualBox 4.0.4,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
9052,Have Virtual Machines create .desktop icons for Gnome 3,Linux,other,VirtualBox 4.0.8,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
9026,Keyboard problem on guest systems in w7 host,Windows,Linux,VirtualBox 4.0.8,2011-06-10T04:53:11Z,2011-06-10T04:53:11Z,"I'm running VirtualBox 4.0.8 on 64-bit Windows 7 Home Premium with the latest updates.

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

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

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

I notice that there are other reports of this problem this week in the forum for Windows-hosted VirtualBox users, but no solutions. ",davidsmith
9072,implement copy-on-read for disk images,other,other,VirtualBox 4.0.8,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
9076,After canceling Cmd-Q confirmation dialog keyboard settings are screwed up,Mac OS X,Linux,VirtualBox 4.0.8,2011-06-15T05:52:54Z,2011-06-15T05:52:54Z,"I'm using a debian squeeze 64bit guest on my MacOSX 10.6.7 host.

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

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

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

  TIA, Wolfgang",Wolfgang Glas
9077,VBoxManage showhdinfo fails on hdd with same uuid as different existing hdd,other,other,VirtualBox 4.0.8,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
9087,"Linux: Please optimize output of VBoxHeadless in ""top""",Linux,other,VirtualBox 4.0.8,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
3351,Normalise or repair the XML data models,Windows,other,VirtualBox 2.1.2,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
9092,Linux host Windows XP guest virtual drive gets corrupted when installing service pack,Linux,Windows,VirtualBox 4.0.8,2011-06-29T19:00:50Z,2011-06-29T19:00:50Z,"I am using Ubuntu 11.04 as the host and I am trying to install Windows XP as the guest and then using windows update to install all the updates. I have 2 Win XP CDs, one does not include any service pack the other includes service pack 2.  

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

I have tried this many times now with the same result. I have tried installing and not installing the 4.0.8 extensions before using the Windows update.  The virtual drive is defined as IDE master. I have even managed to corrupt the virtual drives of Windows XP that were created under VirtualBox version 3.",Mark Myers
6089,Inactive/non-functioning keyboard and mouse in fullscreen (Ubuntu 9.10 guest),other,other,VirtualBox 3.1.2,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
8888,Unabled to pass Command-Q (Super-Q/Win-Q) to guest machine from OSX host,Mac OS X,Linux,VirtualBox 4.0.6,2011-07-10T14:57:06Z,2011-07-10T14:57:06Z,"First of all, Command-Q is assigned to Quit, so I had to change that shortcut key assignment by doing:

`defaults write org.virtualbox.app.VirtualBoxVM NSUserKeyEquivalents '{""Quit VirtualBox VM""=""@^q""; ""Hide VirtualBox VM"" = ""@^h"";}'`

However, even after the shortcut key has been changed, Command-Q is not passed to the guest machine. Virtualbox silently absorbs the shortcut and doesn't do anything with it.",dlee
9182,Pause dock menu item on OS X does not work while Virtual Machine is not front,Mac OS X,other,VirtualBox 4.0.10,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
7823,[feature-request] Scale Mode: performance should improve,other,other,VirtualBox 3.2.12,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
8555,Wrong resolution in full screen mode.,Linux,Windows,VirtualBox 4.0.4,2011-07-12T09:21:04Z,2011-07-12T09:21:04Z,"I use external monitor connected to my notebook. This monitor has bigger resolution than notebook's screen. When I start virtualbox on this monitor and switch to full screen mode guest os takes height of notebook's screen and width of extarnal monitor (see screenshot). Turn off/turn on option ""Auto-resize Guiest Display"" in fullscreen mode nothing changes. To get correct resolution I shoud come back from fullscreen mode, turn off ""Auto-resize Guiest Display"", switch to fullscreen mode and turn on ""Auto-resize Guiest Display"" (see screenshot). Seamless mode also takes wrong display size (see screenshot). In normal mode I can't resize virtualbox window more then notebook's resolution. Maximize button normal in mode works fine.",Oksenchuk Dmitry
9195,"In machine list details view, show actual size of attached VDIs",other,other,VirtualBox 4.0.10,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
9147,"After upgrading to 4.0.10 from 4.0.8 on windows 7 host network connection is permenantly lost, icon replaced by vurtualbox adapter icon",Windows,Linux,VirtualBox 4.0.10,2011-07-15T11:50:15Z,2011-07-15T11:50:15Z,Running Windows 7 on a Toshiba L755D latop with 6GB of RAM.  Upgraded from 4.0.8 to 4.0.10.  After the install could not connect to the internet from windows (via wireless).  The standard wireless network icon in the systems tray was replaced by an icon which was reported as virtualbox adapter.  Opened networking settings to try and connect manually to the wireless but the virtualbox adapter could not be removed or disabled and the normal wireless connection was disabled and would not re-enable.  Uninstalled 4.0.10 and regressed to 4.0.8.,setheridge
9211,Mouse pointer not correctly showed on guest when using multiple displays.,Windows,Windows,VirtualBox 4.0.12,2011-07-16T02:18:34Z,2011-07-16T02:18:34Z,"When using multiple displays on host system - in this case, Windows 7 Professional - on a guest system running Windows XP the mouse pointer is not correctly mapped. In other words, you can't reach all window with one ""normal"" mouse pass: sometimes, multiple mouse passes have to be done with some speed to get the other side of the guest window.

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

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

I'm available to provide more information on this issue.",haZard0us
9212,"in seamless mode with Linux KDE host, sliding open a KDE auto-hidden panel causes temporary screen corruption",Linux,Windows,VirtualBox 4.0.12,2011-07-16T04:01:54Z,2011-07-16T04:01:54Z,"Host: Ubuntu 10.10 with KDE desktop

Guest: Windows XP Pro SP3

VirtualBox 3.2.8_OSE r64453


Steps to reproduce:

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

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

Workaround: uncheck the KDE 'Sliding popups' option mentioned above.
",David-Sarah Hopwood
9219,Shared Folder Enhancement,Linux,other,VirtualBox 4.0.12,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
9271,Mouse pointer Issues in graphics applications,Linux,Windows,VirtualBox 4.1.0,2011-07-22T07:42:56Z,2011-07-22T07:42:56Z,"I have tested on three systems running Ubuntu 11.04 with unity.  P4 with Nvidia, Core 2 with Intel graphics and AMD with ATI graphics.  Problem is the same regardless of host 32bit or 64bit OS.  Virtualbox is 4.1.0

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

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

I have tried disabling both 2d and 3d acceleration but this did not resolve the problem.  I expect this bug will cause problems in other applications too where manipulation of graphics is needed.
",Mark
4358,Break signal on serial port is not delivered to the port in vm,Windows,Windows,VirtualBox 2.2.4,2011-07-25T14:25:03Z,2011-07-25T14:25:03Z,"On the host machine, I run an application that listens to COM port and reacts when the port sends Break signal. To the port I connect a device capable of sending Break signal, and the application reacts as programmed.

In Windows v.m. I specify COM port mapped to the real port on the host machine. Then I run the same application in the virtual machine and have the device send break signal. But the application in v.m. does not see it.

Break signal is described at 
http://support.microsoft.com/kb/119506

its implementation in Visual Basic at 
http://msdn.microsoft.com/en-us/library/aa259405(VS.60).aspx

I can provide the sample program demonstrating this, if needed.


",vadimrapp
9306,Black screen after finishing an application run in full screen in DOS prompt,Mac OS X,Windows,VirtualBox 4.1.0,2011-07-25T20:58:26Z,2011-07-25T20:58:26Z,"Hello,

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

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

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

I attach the last log associated with the issue described.

Thank you.",edu
9316,Hardware presets - the next killer feature?,other,other,VirtualBox 4.1.0,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
9337,VM defaults for a new windows 95/98 image seem off,other,other,VirtualBox 4.1.0,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
9341,Strange wizard help on cloning - no help on really needed info,other,other,VirtualBox 4.1.0,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
9344,Snaphot deletion status window,Windows,other,VirtualBox 4.0.12,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
9307,VBox 4.1.0 GA --  shared folder fails manual mount with sf_read_super_aux err=-22,other,Linux,VirtualBox 4.1.0,2011-07-29T23:43:31Z,2011-07-29T23:43:31Z,"'''VBox 4.1.0 GA gets this error when mounting manually.'''

{{{
mount -t vboxsf vm-shared /mnt/shared
mount: wrong fs type, bad option, bad superblock on vm-shared,
            missing codepage or helper program, or other error
...
}}}

dmesg|tail shows:

{{{
sf_read_super_aux error=-22
}}}

Host: MacOSX 10.6.8
Guest: Oracle Linux 6

'''The following changes work:[[BR]]'''
1. Do not install 4.1.0 GA.  I upgraded VBox from 4.0.12 to 4.1.0.  My Oracle Linux 6.1 guest was using VBox GA 4.0.8 and shared folders were working fine.  After upgrading GA from 4.0.8 to 4.1.0, they now do not work when manually trying to mount shared folders.  This is all against the 2.6.32-100.34.1.el6uek.x86_64 kernel.[[BR]]

2. If I boot the same system into the Redhat kernel 2.6.32-131.0.15.el6.x86_64, and rebuild the 4.1.0 GA, then manual mounting works.[[BR]]


'''Also note:[[BR]]'''

A. Oracle Linux 5, with kernel 2.6.32-100.0.19.el5 and 4.1.0 GA gets: ""mount: Protocol error"" and dmesg says ""sf_read_super_aux err=-71"".  But if I set the VBox GUI setting ""Auto-mount"" for the shared folder, then the shared folder mounts fine at /media/sf_vm-shared.  Meanwhile, ""Auto-mount"" does not work on the OL 6.1 uek kernel (listed in 1. above).[[BR]]

B. If I use Debian guest with kernel 2.6.32-5, then 4.1.0 GA works fine.[[BR]]

C. I created a new VM from scratch (in case there were some issue with the other VMs having been created in an earlier version), did a fresh install of Oracle Linux 6.1, and built the 4.1.0 GA.  Manual mounting of shared folder fails.  '''I will upload the log for this guest''' since it is fresh with basically nothing else done to it.[[BR]]


",jguerrero
9353,Seamless mode is broken on Linux host with Openbox and composite manager,Linux,other,VirtualBox 4.1.0,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
7895,multimon fullscreen mode is broken in 4.x,Windows,Windows,VirtualBox 4.0.0,2011-07-31T11:15:48Z,2011-07-31T11:15:48Z,"Hello. Im using virtualbox 3.x without this problem at all.
I have 2 monitors running in dualview mode (so i have two separated desktops). First desktop is primary.

Virtualbox Manager GUI running on first monitor and guest VM running on second monitor.
now if i press <host>+F combination (goto fullscreen) my guest VM is switched to primary monitor! if i press <host>+F again, it will go away to second monitor.

I expect to see fullscreen mode on second monitor (that is working flawless in 3.x builds)
",ddn
9345,Personalized Settings in Windows NT / XP can not be stored in the shared folder via Junction,other,Windows,VirtualBox 4.1.0,2011-08-02T19:15:03Z,2011-08-02T19:15:03Z,"Hello,

if you use Windows XP in a VM and shut down after loading the snapshot, you want to retain settings (folders and files) from the Windows profile. There are the shared folder. Problem but if its Windows software in the Windows user settings constant user settings stores. With Linux, you could now create a symbolic link (ln-s newLink Target) but in Windows NT / XP, there is no symbolic links by default. It can also create tools using junctions but it does not work with network sources. ""vboxsvr"" is but an emulated network adapter. Symbolic links with a common goal in order Windows NT / XP do not work also. This is a critical problem. For Windows <NT / XP would be necessary to integrate different shared folder in Windows (mount).




Original text:

Hallo,

wenn man Windows XP in einer vM benutzt und es nach dem starten/beenden immer wieder auf einen Snapshot zurück setzten lässt, möchte man Einstellungen (Ordner und Dateien) aus dem Windows Profil beibehalten. Dafür gibt es den Gemeinsamen Ordner. Problem ist aber wenn Windows Software ihre Benutzereinstellungen konstant im Windows Profil abspeichert. Bei Linux könnte man nun einen symbolischen Link erstellen (ln -s neuerLink Ziel) aber bei Windows NT/XP gibt es standartmäßig keine symbolischen Links. Es lassen sich aber mittels Tools Junctions erstellen aber es funktioniert nicht mit Netzwerkquellen. ""vboxsvr"" ist aber ein emulierter Netzwerkadapter. Symbolische Verknüpfungen mit Ziel in einem Gemeinsamen Order in Windows NT/XP funktionieren also nicht. Das ist ein kritisches Problem. Für Windows < NT/XP müsste man die Gemeinsamen Ordner anders in Windows einbinden (mounten).",Codename
9381,Lost keyboard control,Mac OS X,Windows,VirtualBox 4.1.0,2011-08-05T10:19:18Z,2011-08-05T10:19:18Z,"With my external monitor plugged in and my external keyboard plugged into the USB hub in the monitor, I started a Windows 7 VM.  Everything worked great. Then I put the laptop to sleep, closed the screen, unplugged everything and took the laptop away.  opened it up again and the VM wouldn't respond to input from the built-in keyboard.",David Abrahams
9385,"""Create a snapshot of the current state"" is not remembered when restoring snapshots",Windows,other,VirtualBox 4.1.0,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
9358,Mouse pointer offset when shown as arrow. Position ok if line-pointer (text-mode),Windows,Windows,VirtualBox 4.1.0,2011-08-11T05:09:41Z,2011-08-11T05:09:41Z,"A display in Vbox shows Text and buttons in the top and a table with several lines and columns below.
As soon as the mousepointer crosses the border from the screen-top to the table it offsets by 1.5 lines of the table vertically and about the same amount horizontal.
If the mouse pointer goes across a field of the table which has text-contents, i.e. the mouse pointer changes to a line pointer to select text it adjusts perfectly to the text.
This problem has shown up after installing Vbox 4.1 with extension pack 4.1 and guest additions 4.1. Everything was working fine with 4.0.12",Ulrich
9418,Mac Arabic Line Endings,Mac OS X,Windows,VirtualBox 4.1.0,2011-08-11T15:12:21Z,2011-08-11T15:12:21Z,"When copying a paragraph of right-to-left text (arabic in our case) from Word on the Windows guest to the Mac host the line-endings are lost

It seems as though the hidden paragraph marks are being lost",Trident
9419,Sorting controller in the storage device menu,other,other,VirtualBox 4.1.0,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
9420,Selection for optical drives in the boot menu,other,other,VirtualBox 4.1.0,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
8893,FATAL: Int13_diskette_function: read error,Windows,other,VirtualBox 4.0.6,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
9430,Fedora15 does not hook into my wireless connection,Linux,other,VirtualBox 4.1.0,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
9438,Provide a mechinism to set a guest OS's process priority to idle,other,other,VirtualBox 4.1.0,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
9389,Feature Request: Shutdown host if guest is shut down,other,other,VirtualBox 4.1.0,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
9448,Don't show mouse pointer in fullscreen,Windows,Windows,VirtualBox 4.1.2,2011-08-17T07:52:18Z,2011-08-17T07:52:18Z,"Don't show mouse pointer in fullscreen for windows host.
Thanks Gabee.",Gabee
9450,Restore snapshot improvements,Windows,Windows,VirtualBox 4.1.2,2011-08-17T10:13:57Z,2011-08-17T10:13:57Z,"1. When double clicking a snapshot, this should mean: Restore this snapshot.
Similar to (but easier than) clicking on the snapshot and select the restore button.

2. When current state hasn't changed and you restore the nearest snapshot, there's no need to display the confirmation dialog. Nothing gets deleted and the operation is totally reversible (simply by restoring the previous snapshot again).

3. The message that comes up, when you restore a snapshot and current has changed only asks if you want to create a snapshot of current state, but not why I would want that/what happens if I do.
The text should clarify that I can create a branched snapshot tree, something like:
'...... by checking the checkbox below to create a branched snapshot tree; if you don't....'

4. That checkbox should be OFF by default! Normally when restoring a snapshot, you really want to delete the current state.

5. Documentation shows an image with branched snapshots, but not a word about how you create a branched snapshot tree. Please add some text about that.",Poul Bak
5477,Mini toolbar option in GUI is confusing and inconsistent with Shared Clipboard option,Windows,other,VirtualBox 3.0.10,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
9472,"Minor regression in past several versions - ""Help...About Virtualbox..."" flashes off-screen before it can be read",Windows,Linux,VirtualBox 4.1.2,2011-08-20T07:18:49Z,2011-08-20T07:18:49Z,"Windows 7 x64 SP1 host:

Help...About Virtualbox...

Version box materializes momentarily, then vanishes before it is possible to read it.

Since this may include your copyrights, you should be more concerned about this than I am.",Bob Kosch
7821,[feature-request] Scale Mode: Should work with Full-screen,other,other,VirtualBox 3.2.12,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
9541,VirtualBox GUI does not support Windows 7 Jump Lists for recent machines.,Windows,other,VirtualBox 4.1.2,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
9339,[feature request] Enable remote management with GUI,other,other,VirtualBox 4.1.0,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
8070,Less reliance on absolute paths in VirtualBox,Linux,other,VirtualBox 4.0.0,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
5589,GUI options for dock icon/live preview,Mac OS X,Windows,VirtualBox 3.0.12,2011-09-16T11:18:54Z,2011-09-16T11:18:54Z,"There should be a GUI option for toggling between the Live Preview dock icon, and a static icon for the VM's OS. If the user has very small dock icons, the live preview has minimal benefit, so a static OS icon would allow quicker identification of the relevant VM.

Also, the Live Preview icon should allow the user to turn off the 'iMac-like' bezel surrounding the preview. This is a subjective design choice that some (I think many) users would like to remove. Dock icons are usually something that are very easy to modify in OS X so being locked into a set style is quite frustrating.",Kieran
9060,Ideas to improve the list of VMs (GUI),other,other,VirtualBox 4.0.8,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
9202,"Ommit selection dialog on close, when only one close action is possible",other,other,VirtualBox 4.0.10,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
9634,programatically wiring binary data to a file on a VBoxSharedFolderFS disk fails,Mac OS X,Windows,VirtualBox 4.1.2,2011-09-22T07:09:28Z,2011-09-22T07:09:28Z,"I made a python program to write binary data to a file on my shared disk. It has the filesystem VBoxSharedFolderFS. '''When the data became over a certain size only 0s was written.''' 
I used the numpy.tofile() method and also used a more direct way writing the data.
f = open('z:\some_file.bin', 'wb')
f.write(data.tostring())
which also failed on the shared disk, but there was no problem on the local disk. 


",exoer
9668,"more facts, figures, and statistics",other,other,VirtualBox 4.1.2,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
9004,"Neo-layout keyboard in host is not supported, regression from Bug #2595?",Linux,Windows,VirtualBox 4.0.8,2011-09-30T21:22:07Z,2011-09-30T21:22:07Z,"I am using Virtualbox 4.0.8 on Linux Debian Host (Debian SID) with a NEO2 Keyboard layout (see http://www.neo-layout.org). If I use this keyboard while starting Virtualbox, several keys don’t work: for example [CAPS]+[l] for “-” etc. If I overwrite VBoxKeyboard.so with the version of VBoxKeyboard.so attached to Bug #2595, everything works fine.",Johannes Fichtinger
4703,VBoxManage creterawvmdk on osx only allows first 4 partitions.,Mac OS X,other,VirtualBox 3.0.4,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
9035,"[feature-request] GuestControl execute must automatically handle extensions, like shell does",other,other,VirtualBox 4.0.8,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
9692,OSX: Mini Toolbar is not visible in Full Screen mode,Mac OS X,other,VirtualBox 4.1.2,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
9706,Big minimizing machine in Full Screen dual monitor mode,Windows,Linux,VirtualBox 4.1.4,2011-10-06T19:28:34Z,2011-10-06T19:28:34Z,"I'm running Windows 7 Professional 64 bit as the host and Ubuntu 11.04 as the guest.

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

When in full screen mode running dual monitors, if I click the minimize button on the VM tab with the VirtualBox controls for the machine, it only minimizes the primary monitor window and leaves the secondary monitor window maximized.  This should be fixed since the auto-resize feature in dual monitor mode in running an Ubuntu guest OS is still a little fragile.  Both windows should minimize when clicking the minimize button from the VirtualBox menu bar.",josiah
9715,Change GUI to ask for merge or snapshot when gracefully shutting down a guest,Windows,Windows,VirtualBox 4.1.4,2011-10-07T11:44:15Z,2011-10-07T11:44:15Z,"One nice feature of Virtual PC 2007 is that when you gracefully shut down a guest (only Windows), it displays a pop up box asking if you want to merge changes or discard them.

This feature would be nice in Virtual Box as it's a (slight) pain to shutdown the machine, then go to the console and delete a snapshot to merge the images.  Virtual Box, on gracefully shutdown of a guest, could display a pop up box asking if you want to 1) Snapshot 2) Discard Changes (Revert to last snapshot), or 3) Merge changes into last snapshot.  Note:  This would be for shutdown of the guest, not a restart of the guest.",Chris
9723,"same disk boots with fullDevice, but not with partitionedDevice",Linux,Linux,VirtualBox 4.1.2,2011-10-08T20:53:59Z,2011-10-08T20:53:59Z,"i've recently started to use vbox with debian stable, don't remember which version, and then switched to debian unstabe because of unsupported hw. with that vbox got upgraded to 4.1.2_Debian r38459

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

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

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

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

one unusual thing is that my partitions in the partition table are not in disk layout order.",attila.lendvai
9733,Cannot set defaultMachineFolder globally,other,other,VirtualBox 4.0.4,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.
8694,java client access via vboxjws.jar is not using https,other,other,VirtualBox 4.0.4,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
9734,Guest OS goes blank and then reboots when opening mounted shared folder.,Mac OS X,Windows,VirtualBox 4.1.4,2011-10-11T00:51:45Z,2011-10-11T00:51:45Z,"Hi, when i set up and then mount a folder share, my guest os seems to fail. Upon opening the mapped drive the system stalls for a second or two and then goes blank. The system then restarts itself. It is not shutting down, simply going completely blank instantly. My host OS is OS X Lion and my guest OS is Windows 7 Professional. Full details of everything tried so far can be seen on the forum thread: https://forums.virtualbox.org/viewtopic.php?f=2&t=45264 

I have guest additions installed as well as the extension pack. The problem is continuing to persist and the forums have not solved it. I am attaching my log file. Please help.",Tom Rogers
9744,Cancelling out of VM creation deletes entire mount point / junction,Windows,other,VirtualBox 4.1.4,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
9757,"MacOS 10.6.8 host, Fedora14-x86-64 guest, Gnome WM, window moves=artifacts",Mac OS X,Linux,VirtualBox 4.1.4,2011-10-14T17:20:15Z,2011-10-14T17:20:15Z,"Using VirtualBox 4.1.4 r74291, but also previous versions for as long as I can remember, dragging windows causes horrible artifacts inside the dragged window.  Dragging another window over the affected window will fix the parts that the other window covers and reveals, but the other window develops its own artifacts as a consequence of moving it.  Hiding and unhiding a window clears the artifacts.  This happens on every window, all the time.  Firefox windows will refresh themselves after the mouse is released.  I'm using the Fedora default desktop, GDM.  The 4.1.4 guest additions have been installed.  Windowed mode still has artifacts. Seamless mode is better, but artifacts still occur.  Scaled mode has artifacts.  Switching between modes clears currently visible artifacts, but this is because the screen size changes, and the window manager redraws all windows.",Penelope Fudd
9774,2.The preview in the VirtualBox main window shows a black screen when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu,Windows,Linux,VirtualBox 4.1.4,2011-10-17T13:05:24Z,2011-10-17T13:05:24Z,"The preview in the VirtualBox main window shows a black screen 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
9777,"The display panel in Ubuntu only shows the current resolution and 800x600, 640-480 - need better way to set specific resolutions",Windows,Linux,VirtualBox 4.1.4,2011-10-17T17:02:53Z,2011-10-17T17:02:53Z,"The display panel in Ubuntu only shows the current resolution and 800x600, 640-480, there is no way to set a specific resolution other than that.
Maybe adding a dialog to set a specific resolution using the resizing ability of the guest additions will offer a simple solution for this. (there needs to be a GUI for this not only VBOXManage display hints)",temp4746
9036,"kernel WARNING ""sysfs: cannot create duplicate filename /devices/virtual/bdi/vboxsf-$SHARENAME""",Windows,Linux,VirtualBox 4.0.8,2011-10-19T18:15:16Z,2011-10-19T18:15:16Z,"The following kernel messages are regularly logged since upgrading to 4.0. They appear harmless.

{{{
Jun  6 20:00:41 wintermute kernel: [   18.074041] ------------[ cut here ]------------
Jun  6 20:00:41 wintermute kernel: [   18.074048] WARNING: at /build/buildd-linux-2.6_2.6.39-1+b1-amd64-h9EWBu
/linux-2.6-2.6.39/debian/build/source_amd64_none/fs/sysfs/dir.c:455 sysfs_add_one+0x86/0x98()
Jun  6 20:00:41 wintermute kernel: [   18.074051] Hardware name: VirtualBox
Jun  6 20:00:41 wintermute kernel: [   18.074052] sysfs: cannot create duplicate filename 
'/devices/virtual/bdi/vboxsf-vmshare'
Jun  6 20:00:41 wintermute kernel: [   18.074054] Modules linked in: bridge stp bnep rfcomm bluetooth rfkill binfmt_misc 
ppdev lp sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod joydev snd_intel8x0 snd_ac97_codec ac97_bus 
snd_pcm snd_seq snd_timer snd_seq_device pcspkr snd processor soundcore psmouse ac thermal_sys power_supply button 
serio_raw parport_pc parport snd_page_alloc evdev fuse vboxsf(O) vboxguest(O) loop autofs4 ext4 mbcache jbd2 crc16 
nbd usbhid hid sg sd_mod sr_mod cdrom crc_t10dif ohci_hcd ahci libahci libata ehci_hcd virtio_net scsi_mod usbcore 
virtio_pci virtio_ring virtio [last unloaded: scsi_wait_scan]
Jun  6 20:00:41 wintermute kernel: [   18.074089] Pid: 1226, comm: mount.vboxsf Tainted: G           O 2.6.39-1-amd64 #1
Jun  6 20:00:41 wintermute kernel: [   18.074091] Call Trace:
Jun  6 20:00:41 wintermute kernel: [   18.074097]  [<ffffffff810458b4>] ? warn_slowpath_common+0x78/0x8c
Jun  6 20:00:41 wintermute kernel: [   18.074100]  [<ffffffff81045966>] ? warn_slowpath_fmt+0x45/0x4a
Jun  6 20:00:41 wintermute kernel: [   18.074102]  [<ffffffff8114f8aa>] ? sysfs_add_one+0x86/0x98
Jun  6 20:00:41 wintermute kernel: [   18.074105]  [<ffffffff811500cd>] ? create_dir+0x67/0x9f
Jun  6 20:00:41 wintermute kernel: [   18.074108]  [<ffffffff81150196>] ? sysfs_create_dir+0x91/0xa5
Jun  6 20:00:41 wintermute kernel: [   18.074112]  [<ffffffff811a34fc>] ? kobject_add_internal+0xc8/0x181
Jun  6 20:00:41 wintermute kernel: [   18.074114]  [<ffffffff811a3745>] ? kobject_add+0x66/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074118]  [<ffffffff81331dc0>] ? mutex_lock+0xd/0x33
Jun  6 20:00:41 wintermute kernel: [   18.074120]  [<ffffffff811a3376>] ? kobject_get+0x12/0x17
Jun  6 20:00:41 wintermute kernel: [   18.074124]  [<ffffffff81242cfa>] ? device_add+0xcf/0x5d7
Jun  6 20:00:41 wintermute kernel: [   18.074127]  [<ffffffff8124329f>] ? device_create_vargs+0x8b/0xbc
Jun  6 20:00:41 wintermute kernel: [   18.074131]  [<ffffffff810cbb0f>] ? bdi_register+0x5a/0x183
Jun  6 20:00:41 wintermute kernel: [   18.074133]  [<ffffffff810cb794>] ? bdi_init+0x12b/0x157
Jun  6 20:00:41 wintermute kernel: [   18.074137]  [<ffffffff8110d9c1>] ? inode_sb_list_add+0x10/0x4b
Jun  6 20:00:41 wintermute kernel: [   18.074141]  [<ffffffffa01914fc>] ? sf_read_super_26+0x44f/0x514 [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074144]  [<ffffffff811a2788>] ? ida_get_new_above+0x196/0x1b7
Jun  6 20:00:41 wintermute kernel: [   18.074147]  [<ffffffff811a2bb3>] ? idr_pre_get+0x57/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074151]  [<ffffffff810fd06a>] ? unlock_super+0x21/0x21
Jun  6 20:00:41 wintermute kernel: [   18.074154]  [<ffffffff810fd0b8>] ? set_anon_super+0x4e/0xe1
Jun  6 20:00:41 wintermute kernel: [   18.074157]  [<ffffffff810fdf6a>] ? sget+0x35d/0x372
Jun  6 20:00:41 wintermute kernel: [   18.074160]  [<ffffffffa01910ad>] ? sf_glob_free+0x2a/0x2a [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074163]  [<ffffffff810fe05c>] ? mount_nodev+0x45/0x79
Jun  6 20:00:41 wintermute kernel: [   18.074165]  [<ffffffff810fdb2f>] ? mount_fs+0x6c/0x14a
Jun  6 20:00:41 wintermute kernel: [   18.074168]  [<ffffffff81112ce9>] ? vfs_kern_mount+0x61/0x97
Jun  6 20:00:41 wintermute kernel: [   18.074171]  [<ffffffff81112d7e>] ? do_kern_mount+0x49/0xd6
Jun  6 20:00:41 wintermute kernel: [   18.074173]  [<ffffffff81113533>] ? do_mount+0x728/0x792
Jun  6 20:00:41 wintermute kernel: [   18.074176]  [<ffffffff810e6260>] ? alloc_pages_current+0xa7/0xca
Jun  6 20:00:41 wintermute kernel: [   18.074179]  [<ffffffff81113625>] ? sys_mount+0x88/0xc3
Jun  6 20:00:41 wintermute kernel: [   18.074182]  [<ffffffff81338c12>] ? system_call_fastpath+0x16/0x1b
Jun  6 20:00:41 wintermute kernel: [   18.074184] ---[ end trace 8683823577cfa94a ]---
Jun  6 20:00:41 wintermute kernel: [   18.074186] kobject_add_internal failed for vboxsf-vmshare with -EEXIST, don't try to 
register things with the same name in the same directory.
}}}

This may be a duplicate of #8056, but for me the shared folders work fine, whereas in that bug the user cannot mount them.

Guest is Linux 2.6.32 through 2.6.39.",Sam Morris
9791,Improved support for Ubuntu Unity,Linux,other,VirtualBox 4.1.4,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
9792,Parent VM Still reports being parent of deleted VMs,Windows,other,VirtualBox 4.1.4,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
4753,ost-only network adapters settings change after reinstall,Windows,other,VirtualBox 4.1.4,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
9806,VirtualBox Manager does not update Machine status when the VM is started in a different desktop (sysinternals),Windows,Windows,VirtualBox 4.1.4,2011-10-25T02:21:01Z,2011-10-25T02:21:01Z,"I use SysInternals desktops on Windows 7 64, which gives Windows four desktops.  I nominally run VMM on desktop 1 and VMs on each of the other three desktops.  All works fine, except for the VM status does not get updated on the VMM running in desktop 1.  

This has led to corrupted VM Linux filesystems due to executing a VM management task while the VM was in a state that normally would not allow the task to be executed.  

If the VMM is run in the same desktop as the VM, then the status gets updated.

WORKAROUND: verify that the VM is shutdown before performing any management tasks in the VMM.
",george lawton
6957,More network adapters in VirtualBox,other,other,VirtualBox 3.2.4,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
9815,Mark virtual machines as excluded from backups,Mac OS X,other,VirtualBox 4.1.4,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
302,wrong path for settings under mac os x,Mac OS X,other,,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
9846,Virtualbox 4.1.4r74291 - shared folders disappear and reappear randomly between reboots,Windows,Windows,VirtualBox 4.1.4,2011-11-02T17:22:48Z,2011-11-02T17:22:48Z,"Virtualbox 4.1.4r74291 - shared folder to drive letter mappings disappear and reappear randomly between reboots.
They always show up in the VM's Settings --> Shared Folders section, no problem displaying or editing them.   But, when you start the VM, sometimes they show in Windows Explorer as mapped drive letters, sometimes they don't.   They are always accesible when referenced as UNC paths, i.e. \vboxsrv\sharedfolder, but they are not always accesible as drive letters.",Pedro Serrano
9842,virtualbox doesn't list USB device with zero vendor and product ID,other,other,VirtualBox 4.1.4,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
8649,[feature-request] VBox Windows Installer should check for python version,Windows,other,VirtualBox 4.0.4,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
8926,Extra window pops up after unfocusing open CD Image dialog,Mac OS X,Windows,VirtualBox 4.0.8,2011-11-11T15:31:42Z,2011-11-11T15:31:42Z,"Once you open the ""Choose a virtual CD/DVD disk file..."", unfocus the VirtualBox window, then switch focus back to VirtualBox window and a Linux-like dialog box appears. You are unable to interact with it, but a ESC or Cmd+. will get you out of the box.",jeremyttu
8830,Lock screen removes all clipboard data,Linux,Windows,VirtualBox 4.0.6,2011-11-13T18:49:37Z,2011-11-13T18:49:37Z,Lock screen removes all clipboard data.,386sky
9913,Windows XP Guest application causes hang of VirtualBox Guest & Windows 7 Host,Windows,Windows,VirtualBox 4.1.6,2011-11-17T15:27:55Z,2011-11-17T15:27:55Z,"I am running Virtualbox 4.0.10 successfully with a Window 7 host and a Windows XP guest.

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

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

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

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

I have held off logging a bug until now as I was hoping newer versions may resolve the issue but the fault is still present.",starfire
9934,Suspend 3D Desktop Composition when entering Seamless Mode,other,other,VirtualBox 4.1.6,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
9234,GNU/kFreeBSD support: gnukfreebsd checks in the build system,other,other,VirtualBox 4.0.12,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
9964,cloned(full) openSUSE12.1 is not able to find it´s harddrive,Linux,Linux,VirtualBox 4.1.6,2011-11-28T16:56:50Z,2011-11-28T16:56:50Z,"I´ve made two clones of a working openSUSE12.1 64bit vm(on a openSUSE12.1 64 bit host).

Both have problems to start up correctly.

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

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

I attach a screenshot for the exact error message and the logs.",maninred2
9970,DHCP gateway option,other,other,VirtualBox 4.1.6,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
9971,Persistent DHCP database,other,other,VirtualBox 4.1.6,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
9979,[feature-request] Please allow clones from running VMs,other,other,VirtualBox 4.1.6,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
9992,"Close button for ""already latest version"" window does not work",Windows,other,VirtualBox 4.1.6,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
10001,Short file names missing from \vboxsvr\share,Windows,Windows,VirtualBox 4.1.6,2011-12-07T08:16:23Z,2011-12-07T08:16:23Z,"short file names are missing via shared folders whether the drive is mapped or the unc is used.  for example: 

dir \vboxsvr\share /x 

should list short file names along with the name, but the short file names are missing.  this is causing problems with 16 bit utilities including source code builds that have to use the short name.
",dfatvb
10007,Drag and Drop ISO on to CD/DVD Icon,Windows,Windows,VirtualBox 4.1.6,2011-12-07T18:46:51Z,2011-12-07T18:46:51Z,"You should be able to drag/drop an .ISO file on to the icon in the statusbar.  I couldn't do that with the release as of today Dec 7, 2011 Using Win7 x64.",dfatvb
9808,Cannot delete snapshot due to hidden differencing image,Windows,other,VirtualBox 4.1.4,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
3852,"vboxusers group should be added as a system group, not as an ordinary group",other,other,VirtualBox 2.2.0,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
10009,Switching to dimensioned mode (Host+C) hangs Windows 7,other,Windows,VirtualBox 4.1.6,2011-12-08T17:54:01Z,2011-12-08T17:54:01Z,"Windows 7 guest / VB 4.1.6 / Mac OSX Lion

When in the VM I inadvertently press host+C (Copy in mac world), Virtual Box VM switches to 'dimensioned mode'
When getting back to 'integrated desktop' mode (host+L), user interface is just freezed, no action possible unless I restart the virtual machine.

I've experienced this problem since VB version 4.1.4, and before upgrading Mac OSX to Lion.",n
9972,Connection sharing for host-only networking,Mac OS X,other,VirtualBox 4.1.6,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
10098,Wrong manual entries for setting up VRDP authentication in the VBox end-user documentation,other,other,VirtualBox 3.2.14,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
10123,Allow using raw host disks for guests via VirtualBox VM Manager (GUI),other,other,VirtualBox 4.1.8,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
10101,"VBoxLinuxAdditions should check for make, perl",other,Linux,VirtualBox 4.1.2,2012-01-04T15:28:32Z,2012-01-04T15:28:32Z,"Just finished installing guest additions on a CentOS 6.2 system (x86_64, in case it matters... don't think it does, though.)

In addition to the usual kernel-devel and gcc requirements, make and perl were also not installed as part of the default textmode install, yet were required for the guest additions module to be built.

It was not difficult to find out these were missing--it was very obvious from vboxadd-install.log, actually--but the installer should probably explicitly check anyway.

I can write a patch for this myself if someone would be kind enough to point out where the relevant source is located in the tree.",Matt Behrens
8693,Consider pushing the java  vboxjws.jar client API jar in a Maven repository,other,other,VirtualBox 4.0.4,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
7891,VBox doens't handle the user account correctly on Windows Hosts,Windows,other,VirtualBox 3.2.12,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
10156,Windows Guest Additions lacks silent reboot option,other,Windows,VirtualBox 4.1.8,2012-01-11T03:59:00Z,2012-01-11T03:59:00Z,"VBox: 4.1.8

Guest: Windows XP

VBoxWindowsAdditions.exe has ""/S"" flag for silent install, but lacks a flag for silent reboot, which is a problem for unattended install.

This problem prevents wish #5810 from finishing.

-Technologov, 11.Jan.2012.",Technologov
10175,auto mount shared folders immediately and not just after reboot,Windows,Linux,VirtualBox 4.1.8,2012-01-16T21:27:12Z,2012-01-16T21:27:12Z,"When creating a shared folder and setting auto mount it will be mounted after reboot.
It will be helpful if the folder will be mounted immediately without requiring a reboot as well.

Tested on ubuntu 11.10 guest under win7 host.

Thanks",pablop
10182,Auto capture keyboard shortcut host key not displayed in warning info,Windows,Linux,VirtualBox 4.1.8,2012-01-19T16:21:46Z,2012-01-19T16:21:46Z,"When I start VirtualBox I get 'auto capture keyboard' warning where it should be displayed keyboard shortcut, but in my case there is no key displayed.

I use Windows-menu key as host key, key is between right <Atlt> and right <Ctrl> key.",grof
9480,VirtualBox + VirtualPC2007 = crash,other,other,VirtualBox 4.1.2,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
10212,Problem with DNS lookups (NAT),other,other,VirtualBox 4.1.8,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
10241,Display the Current State node as the first child of its parent,Windows,Windows,VirtualBox 4.1.8,2012-02-10T15:17:20Z,2012-02-10T15:17:20Z,"In the GUI's display of snapshots for a machine, the Current State node is often lost within the tree of snapshots. I would like to more easily see which snapshot is its parent. Making it the first child would be one way (whether by a preference setting or otherwise). 

Yes, it could be argued that once the current state has changed (thereby begun serving its purpose), it is the youngest state and therefore should be the last child of the snapshot parent. However, the fact that it has snapshots as siblings is irrelevant to its relationship to its parent and the ultimate purpose of restoring to that snapshot in the first place.",TomB
10242,Need a way to prune snapshot tree,Windows,Windows,VirtualBox 4.1.8,2012-02-10T20:02:44Z,2012-02-10T20:02:44Z,"Note: This is ''not'' another complaint about ""Delete Snapshot"". I propose a new feature, regardless of what the snapshot operations are named.

When I have a tree of snapshots, I sometimes want to remove a branch, abandoning the snapshot states, deleting their differencing images and other new disks. I just want part of the machine's state zapped, just as if I had never created it in first place.

Other than hacking XML files, the only way to do this is documented here: 
[http://srackham.wordpress.com/2010/06/18/deleting-virtualbox-snapshots/ Convoluted Pruning Method] (Warning: contains an irrelevant gripe about the name of ""Delete Snapshot"".)


There are some design issues that I've thought of:

- Should the operation be on the parent snapshot (i.e, prune all children)? Or, should it be on the topmost snapshot to be removed?

- What if Current State is one of the decendents? Disallow or offer to restore to one of the snapshots that will remaing?

- There can be only one root snapshot. It necessarily has Current State as a decendent. And with all the snapshots being removed, it would seem appropriate to make the Current State the same as the the root snapshot and then remove all the snapshot. Again, just as if I had never created the root snapshot.

- I'm not looking for a one-click ""nuke it"" operation. As with the other snapshot operations, careful, informative UI design will help users be sure that they are doing the right thing and offer appropriate options or followup actions (e.g., delete disks or keep).
",TomB
9776,When using pause the gray out effect isn' working when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu,Windows,other,VirtualBox 4.1.4,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
10252,Switch to fullscreen with VBoxManage,Windows,Linux,VirtualBox 4.1.8,2012-02-14T16:52:49Z,2012-02-14T16:52:49Z,"It would be of great value to us to be able to use VBoxManage controlvm to switch the VM window between the different display modes, such as scale, fullscreen and so on via VBoxManage. This would be a very important and valuable feature. Also, it would be valuable to as well allow auto resize to be turned on and off via VBoxManage. These would be extremely valuable and important features to us. Thank you very much, it is greatly appreciated.",David
10272,Allow storing virtual machine settings in a directory thus multiple virtual box installation could share,other,other,VirtualBox 4.0.16,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
10222,Please implement readPhysicalMemory or a raw memory dumper,Linux,other,VirtualBox 4.1.8,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
6358,Add official support for running as a service,Windows,other,VirtualBox 3.1.4,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
8279,Use FreeRDP instead of rdesktop,Linux,other,VirtualBox 4.0.2,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
6525,Develop a Gallium3D Driver for Linux (and Other) Guests,other,Linux,VirtualBox 3.1.6,2012-03-18T18:03:26Z,2012-03-18T18:03:26Z,"Traditionally, Mesa drivers each have to have their own OpenGL implementations written for them.  This creates a lot of duplicate code.  Gallium3D solves this problem by separating the API (known as a state tracker) from the core driver.  This allows driver developers to focus mainly on hardware interaction, not on graphics APIs.

Gallium3D has already been adopted by:
1. VMware (for Linux guests)
2. Nouveau project (open source NVIDIA drivers)
3. ATI (R300 driver nearly complete, R600 in the works)",William Swartzendruber
10351,Host-Q and Host-H do not follow host key remapping,Mac OS X,Linux,VirtualBox 4.1.10,2012-03-19T20:15:25Z,2012-03-19T20:15:25Z,"Steps to reproduce:

1. Change host key from default (command) to left control + left option.
2. Start a guest (I have a Debian Linux guest).
3. Type Command-Q.

Expected behavior:

* Keystroke is passed through to guest.

Actual behavior:

* Keystroke is intercepted by VirtualBox (which offers to quit).
* After cancelling the quit dialog, the Command key is stuck down until it's pressed again.

Misc:

* Basically, this is a user interface bug. Following the principle of least surprise, all host key combinations should be remapped if the host key is changed. Also, these keystrokes are needed in the guest OS (Emacs in particular uses them frequently).
* This forum thread may be relevant: https://forums.virtualbox.org/viewtopic.php?f=6&t=29695

Thanks for your hard work on VirtualBox! It makes my work dramatically easier.",reidpr
10383,Enable mouse integration to be disabled in the guest config,Linux,Windows,VirtualBox 4.1.8,2012-03-26T19:44:41Z,2012-03-26T19:44:41Z,"When using a VirtualBox guest in full-screen mode as root, the mouse integration can cause issues with programs like Synergy <http://synergy-foss.org/>. Because this is for school computer labs and the local user does not own the guest (for security reasons), I would like to be able to permanently disable mouse integration in the guest config.

Host is RHEL 5.6 x86_64. Guest is Windows XP.

BTW, I have the host key disabled for security reasons, which is why this is a pain.",jwedgeco
10343,"Provide emulated hardware devices for video camera, scanners and video capture",Windows,Linux,VirtualBox 4.1.8,2012-04-04T21:02:27Z,2012-04-04T21:02:27Z,"Virtualbox should add a virtual emulated device that a guest OS can use inside the VM to access video input and output devices and imaging devices such as scanners and video cameras, and capture cards, virtualbox would use the  application API of the host OSs to access the hardware through the Host OS driver, the application API for accessing the hardware drivers used by the  host OS as the backend for emulated devices provided to the guest OS. 

This is already what virtualbox does for sound cards, video cards, and network interfaces.

This in many cases is better than attempting to use the USB pass through. USB pass through does not work well when multiple OSs including many VMs need to share the device. Very rarely does pass through work right. It is just asking for trouble to occur to have many different drivers trying to directly cntrol the device. 

This is why it is best to only have one driver directly talk to the device, the Host OS driver, and then provide emulated devices inside the VMs that use the Host OS driver as a backend. The guest Os then only needs to load the driver for the device that virtualbox emulates. Virtualbox should choose to emulate a brand and model of each type of hardware that is particularly common and widely supported by many OSs.

What I suggest is have virtualbox emulate some hardware devices, like a scanner, USB web cam and a happauge video capture card. The emulation would then use the Host OSs application driver APIs as a backend and provide a virtual device in the VM for every real device accessible via the application driver APIs. Guest OSs would load the driver for the scanner, video capture card and camera device that would talk to the emulated hardware device. 

This would provide much smoother operation than  the horrid and buggy USB pass through. This is already done with video cards, network adapters and so on. ",David
10504,Missing case-insensitivity for certain filenames for Windows 7 guests,Linux,Windows,VirtualBox 4.1.12,2012-05-02T13:16:10Z,2012-05-02T13:16:10Z,"Use a Windows 7 64-bit guest on VirtualBox 4.1.2 on Linux 64-bit hosts.
Mount a VirtualBox-Filesystem share.
Open a ""cmd"" box and change the current directory into a directory in this share.
Execute following script:

{{{
mkdir test
mkdir test\Client
mkdir test\Client\a
mkdir test\Client\a\b
dir test\client\a
dir test\Client\a
}}}

What is expected that ""test\client\a"" should be accessible. What is actually observed is that ""test\client\a"" is not accessible. However, ""test\Client\a"" is accessible.

Running apps which access VirtualBox-shares is therefore quite restricted.


",xbaldauf
10261,Shared Folder symlnks now broken with Windows Host<-> Linux Guest,other,Linux,VirtualBox 4.1.8,2012-05-03T08:01:19Z,2012-05-03T08:01:19Z,"One of the most annoying things over the holidays was when I upgraded to the Virtual Box 4.1.8 release and it broke the ability to create symlinks inside shared folders on a Windows 7 host.  Normally prior, I would run Virtual Box as administrator and symlinks were creatable and would function properly.  We use symlinks to link our django project settings files to be a source file checked into our code repots.  Now I have to copy the file direct and use a differ tool.

Unfortunately I did try down grading to the previous version but the xml structure of the machine file definitions changed and there was no documentation or inisight on how to correct it so my machines could now only run in the current version that has this broken functionality.  I consider this defect major because it is functionality that is useful to developers, does not pose a security risk, and is now completely broken in the latest point release.

I love VirtualBox and I will be truly satisfied if this issue can be fixed.  Now to file a different report with the PyCharm people ...",Matteius
10557,Need an option to save a machine's state somewhere else,Linux,all,VirtualBox 4.1.14,2012-05-12T17:08:26Z,2012-05-12T17:08:26Z,"Suppose you incurr into a DISK FULL error while a VM is running (it actually happened to me). The machine is automatically paused, and you are prompted to free some space on disk.
Suppose you cannot free up any space because the vdi and snapshots are alone on a disk partition and they have filled it up.

- You cannot save the machine
- You cannot clone it because when you clone it, you are not asked where to store the files for the new machine
- you cannot export it because it is not turned off

- you have other disks with plenty of space where you could save the current space and copy all the vdi's so as to later resume the machine with enough disk space, but there's no way you can do that because you can't save it anywhere else than in the disk that is full.


So, an option should exist (or at least should be provided as a backup mechanism whenever a disk full error is encountered) to save the current machine state somewhere other than the default location.

",matteo sisti sette
5252,Intel vt-d/AMD IOMMU support,Windows,other,VirtualBox 3.0.8,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
10598,--timesync-set-on-restore syncs time up to 10 seconds after snapshot restore,Windows,Linux,VirtualBox 4.0.16,2012-05-25T13:35:49Z,2012-05-25T13:35:49Z,"I have a Linux guest(additions 4.0.16) and a Windows host(vbox 4.0.16). The guest service is started via:
{{{
/usr/sbin/vboxguest-service -f -vvvvv --disable-vminfo --disable-cpuhotplug --disable-vmstats --disable-automount --disable-memballoon --timesync-set-threshold 1000 --timesync-set-on-restore 1
}}}

If I restore a snapshot of this machine, even one that is 7 days old, the time is not synced on restore.
~10 seconds (timesync-interval?) after resuming the VM, the vboxguest-service outputs ""The VM session ID changed, forcing resync."" and time is actually synced.

This causes trouble when working with certificates that are generated after taking the snapshot, so for some use cases this is really annoying.",insecure
10802,Host only interfaces should be down when not in use,Mac OS X,all,VirtualBox 4.1.18,2012-08-05T01:42:25Z,2012-08-05T01:42:25Z,"I noticed that host side interface (i.e. vboxnet*) stay ""UP"" even when VMs referring to the interfaces. They even stay ""UP"" when the virtual box manager is not present. It is nice, and probably semantically correct that vboxnet* interfaces are brought down when they are not referenced, or at least when the virtual box manager is not running.
",shinoda
8038,Symbolic links in shared folders,Windows,Linux,VirtualBox 4.0.0,2012-08-21T09:45:45Z,2012-08-21T09:45:45Z,"
Hi all !

Virtualbox 4.0.0
windows host, linux guest.

If I made with windows a simlink from folder c:\Documents to d:\shared_folder\documents... under linux this symlink doesn't works... is not accessible ( red color 0 byte )... linux can't access to c:\Documents.
In the past releases this kind of symlink worked.

For testing windows simlinks I used mklink from cmd line and a specific ( awesome ) program like Link Shell Extension (http://schinagl.priv.at/nt/hardlinkshel ... ml#contact ) that allow making different kinds of links... but nothing working...",Quaid
10838,Horizontal wheel-scroll becomes alt-vertical-wheel-scroll,Linux,Windows,VirtualBox 4.1.18,2012-08-25T06:39:31Z,2012-08-25T06:39:31Z,"I have a Windows 7 guest on Virtualbox 4.1.18 r78361 on 64-bit Ubuntu 12.04 host (Unity 2D/3D), and when in the Windows guest, a horizontal mouse wheel-scroll becomes the alt-vertical-scroll event (with effect similar to page-up/down). This is very annoying as whenever I accidentally touch horizontal scroll wheel the whole page jumps up or down a full page or more. This happens both of my bluetooth mouses (Apple and Logitech). I have the latest guest addition installed on the guest Windows 7 OS. I've tried both PS2 mode and absolute position mode (e.g. tablet mode) HID mouse emulation in virtualbox setup, with same result. I can't find any mention of this problem after an hour of search.

BTW, the same Virtualbox with an Ubuntu guest works fine, e.g. horizontal and vertical mouse wheel-scroll work as they normally should.

What can I do? If it can't be fixed, e.g. horizontal scroll-wheel to scroll horizontally, then I don't mind if there is a way to disable horizontal scroll-wheel events from Virtualbox's .vbox guest-machine configuration...",powerstrip2
9054,Add Host CPU/System info to About or other dialog.,Linux,Linux,VirtualBox 4.0.4,2012-09-12T09:38:47Z,2012-09-12T09:38:47Z,"Hello, thanks for an awesome project.  I use it for a pre-made LAMP development environment:  http://drupal.org/project/quickstart.

My users are asking me whether they should install the i386 or amd64 version.  

Could you please add a ""System info"" dialog to the Virtualbox host UI?

Basically, CPU info, host OS info, AMD-V/VT-X extensions enabled, etc.  For a  big bonus, ""This system can/can't run a 64-bit guest.""  Other things could be added (3d support, USB, etc) but for now just the 32/64 bit info would be great.

This might seem trivial, but would greatly simplify supporting my users, saving them alot of trouble choosing which guest to download, and helping me help them.

Thanks again for a great project,

Mike
",MIchael Cole
10957,"website: add link to ""vboxsvc"" project (enhanced SMF management of VMs on Solaris-based hosts)",Solaris,all,VirtualBox 4.2.0,2012-09-18T08:59:16Z,2012-09-18T08:59:16Z,"The http://www.virtualbox.org site lists some useful open-source projects that can be used along with VirtualBox. I suggest adding there a link to the ""vboxsvc"" project, which is hosted on SourceForge at http://sourceforge.net/projects/vboxsvc/ and its discussion is in VirtualBox forum, thread ""[Free as in beer] SMF service for VirtualBox VM's"" http://forums.virtualbox.org/viewtopic.php?f=11&t=33249.

This project provides an SMF method script and manifest to wrap execution/hibernation/shutdown of each VM as a separate SMF service instance, and lifetime monitoring (i.e. a frozen VM can be forced to reboot), as well as optional automated ZFS snapshot creation upon VM startup/shutdown, and many other administrative features. An SVR4 package of the project deliverables is also available.

In comparison with VirtualBox 4.2.0 automated VM startup support there are a few differences which may be important in more advanced setups - but available only for solutions built on Solaris 10, OpenSolaris and its relatives (using SMF and ZFS):
* With vboxsvc, each VM is an SMF instance, which allows to enable-disable them independently, and to build SMF dependency graphs between VMs and/or other system services and resources for automatic startup and shutdown/savestate of VMs.
* You can monitor the VM's functionality (i.e. test that it is ""pingable"" or that a webserver inside it responds), and accordingly restart the SMF service or put it into maintenance; you can also delay the exit is start-method until the VM actually works (needed for dependencies to start at a right moment in time and not after a delay randomly selected by admins).
* You can automate taking snapshots of ZFS-backed VM filesystem resources (including those on remote storage hosts available to VBox host via NFS or perhaps CIFS) before start/after stop to keep track of relatively stable points in time.
* There are some other differences, such as getting X11 control of a VM and then passing its execution back to headless SMF controller and various other ""nifty features"", all with configurable SMF attributes.",Jim Klimov
7214,[PATCH] Add BeOS and Haiku to the (Other) guest OS list,other,other,VirtualBox 3.2.6,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
7111,[feature-request] Please allow to loop mount VBox HDD images on host,other,other,VirtualBox 3.2.6,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
10986,Wrong mtime on shared folders,Windows,Linux,VirtualBox 4.2.0,2012-09-24T12:07:45Z,2012-09-24T12:07:45Z,"Linux ""vboxsf"" shared folder system does not set correct modification time. It only happens then file is written with some data.
attachment contains repro code (gcc testts.c ; ./a.out)
",ajax16384
10996,Parallel port interrupts can not be used,Windows,other,VirtualBox 4.2.0,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
11000,Performance and statistics for host and guests,all,all,VirtualBox 4.2.0,2012-09-28T13:34:43Z,2012-09-28T13:34:43Z,"Hello,

it would be very nice to see kind of performance & utilization statistics for each guest in Virtualbox console.

With some graphs for

 - cpu usage
 - memory usage
 - disk i/o
 - network usage
 - etc.

Does this features is alredy in your roadmap ?

Thanks for your feedback.

Davide",dfranco
11006,Creating a cloned or linked virtual machine does not allow to select destination folder,other,other,VirtualBox 4.2.0,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
11029,/etc/init.d/vboxautostart-service stop has no effect,Linux,other,VirtualBox 4.2.0,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
11077,Allow drag-and-drop of disks between controllers,all,all,VirtualBox 4.2.0,2012-10-18T06:58:27Z,2012-10-18T06:58:27Z,"VirtualBox GUI allows to define several disk controllers for a VM (such as SATA, IDE and SCSI controllers). 
While testing different boot modes (bootloader development) it is needed to switch a single HDD image between controllers, however it is not convenient onw, because a disk image must be removed from the old controller and added to new controller with several mouse clicks and a file selection window.
This RFE suggests to allow drag-and-drop of already-attached virtual storage devices between available VM storage controllers, easing this operation to one click-and-drag.",Jim Klimov
10993,Using cmd+<key> in Mac OS X host executes the command but also the <key> to the guest,Mac OS X,Windows,VirtualBox 4.2.0,2012-10-20T10:16:45Z,2012-10-20T10:16:45Z,"With the latest hotfix 4.2.1 when I do cmd+e (to start Explorer in a Windows XP guest) it starts Explorer but also inputs the character 'e' in the current focused application (ex: Notepad). 

This also is true for any other cmd+<key> combination.",kimus
11096,No Host-Only Network Adapter after upgrading from 4.2.0 to 4.2.2,Windows,all,VirtualBox 4.2.2,2012-10-21T03:25:17Z,2012-10-21T03:25:17Z,"
There appears to be a flaw in the Windows installer script, probably custom actions.

Upgrading from 4.2.0 to 4.2.2 on a Windows 7 x64 SP1 host produces the following:

""--Error Renaming Connection-- Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.""

The msi logs indicate the installation was 'sucessful'. However in addition to the 'Proxy' issue already reported, the Host-only Networks section of VirtualBox Settings is completely blank.
",Bob Kosch
2652,Gentoo hardened (grsecurity) hosts not supported,Linux,Linux,VirtualBox 4.2.2,2012-10-22T08:45:10Z,2012-10-22T08:45:10Z,"Hello,


I am running VirtualBox 2.0.6 on a Gentoo Hardened Host (2.6.23-r7).

Running normal linux systems as guest works fine, however when I try to boot a Gentoo Hardened _Guest_ system, VirtualBox reports a Guru Mediation Error and the VM freezes on kernel bootup. I tried with various hardened Guest kernels (2.6.23-r7, 2.6.24-r3 and 2.6.25-r9, all hardened-sources from Gentoo) but the error remains. Grsecurity/PAX presetting in the kernel is set to ""high"". The produced log is attached.


I will try to narrow down the search on why the kernel crashes by disabling some of the hardened options but so far I didn't have much success.

Best regards,


Christian Holler",Christian Holler
11105,Better support for clustered environments,all,all,VirtualBox 4.2.2,2012-10-22T12:56:50Z,2012-10-22T12:56:50Z,"We would like to see better support for clustered environments.

We run a cluster environment using VirtualBox and glusterFS. All VM's and their virtual disks are stored on mirrored glusterFS volumes via storage nodes (dedicated storage servers). We have several compute nodes (Linux x64 host servers) running the the guest VM's. All compute nodes share the same VirtualBox.xml (stored on a mirrored glusterFS volume) so that any guest VM can be serviced by any compute node. We use phpVirtualBox to manage our VM cluster.

This cluster configuration presents several problems:

1) Updates to guest VMs (i.e. to VirtualBox.xml via vboxmanage) on any server in the cluster is never propogated to the other servers in the cluster unless a complete restart occurrs;

2) Compute node B (or C, D, E, etc) does not know that Compute Node A is currently servicing (running) guest VM '1234'.

Proposed Enhancments:

1) A new file called '{compute node}.state.xml' (or any other name).

This file is created in the guest VM's home VirtualBox folder and updated to reflect the current state of the guest VM. The '{compute name}' is used in the filename to designate which compute node (host server) the state file is for. This file is updated accordingly by the compute node to provide read-only information via vboxmanage and web services.

VirtualBox.xml is modified to better separate configuration information versus 'current running state' information so that the 'current running state' information is by compute node. This will allow for 'teleporation' within a cluster. You cannot use teleportation in a cluster sharing the same VirtualBox.xml.

2) Updates to VirtualBox.xml are propogated to other compute nodes sharing the same VirtualBox.xml.

Perhaps add a new vboxmanag command called ""refresh config"". This command will cause VirtualBox to re-scan the VirtualBox.xml and update it's memory configuration.
This command should also be available in web services.
",Van Stokes Jr
11032,VBox 4.2 on Solaris 11/11 with bonding locks up network adapter,Solaris,all,VirtualBox 4.2.0,2012-10-22T17:20:54Z,2012-10-22T17:20:54Z,"I am running Solaris 11/11 SRU 11.

I have two onboard network adapters which I had bonded.  Both e1000e drivers.

I understood that virtualbox would not work properly with bond0 without vnics created.  So I created a vnic for each Guest with the guests mac.  After aprox 2 days of operation, the entire host machine will no longer be network accessible.  There are no system log messages about any issues and VBoxSvr does not have any information. This of course crashes any VBox that is using iSCSI harddrives.

I was able to reproduce this issue twice. Each time taking 2 to 3 days for the problem to manifest.

I have since unbonded the adapters and set net0 as the primary bridgeadapter for all VMs and let the vbox network driver create its own vnics over net0.  This has been running stable for 2 weeks now.

I have an identical hardware box also running Solaris 11/11 SRU 11 with bonding turned on. This box ONLY serves up iSCSI targets and has not exhibited the same behavior.

Hopefully I can get a third box where I can try reproducing it on that without disrupting production.",norchem
3640,Additional Preference to swap Control (CTRL) and Command (CMD) keys per virtual machine,Mac OS X,other,VirtualBox 2.1.4,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
11104,Ubuntu Quantal package: migrate from libpython2.7 to libpython3,Linux,other,VirtualBox 4.2.2,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
11205,snapshot management on toolbar,all,all,VirtualBox 4.2.4,2012-11-18T14:05:22Z,2012-11-18T14:05:22Z,"tried searching, didn't find anything similar.  VMWare's ability to revert to snapshots from the menubar+utility bar (the tab bar providing quick options w/in the guest session) is very handy.  Best way I've found to revert to snapshots in VBox is to power down the machine and then revert to the snapshot, or click all over the VBox Manager window to get to the snapshot pane. Neither of which are at all convenient.  Would be nice to have fewer-click shopping for snapshots.",dorklord
11246,Display VM Name in Dock,Mac OS X,all,VirtualBox 4.2.4,2012-11-27T16:16:30Z,2012-11-27T16:16:30Z,"When multiple virtual machines are running on Mac OS X and some are minimized to the OS X Dock it can be annoying to find the one you are looking for without maximizing each, as the title of the instances of the machines in the dock is just ""VirtualBoxVM"".",t0biasvogel
1668,Mac version needs option to pass system keyboard shortcuts through to OS X,Mac OS X,other,VirtualBox 1.6.2,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
7142,SHUTDOWN=acpibutton fails to wait for shutdown of headless/vrdp guest with parrallel boot activated on host,Linux,other,VirtualBox 3.2.6,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
11296,entropy quality,other,all,VirtualBox 4.2.4,2012-12-17T09:17:54Z,2012-12-17T09:17:54Z,"Many cryptographic operations depend on good entropy. Bad entropy results in weak keys and poor security.

There is no information about entropy quality available on virtualbox.org.

What sources of entropy are available to virtual machines? How good are those sources? Does the virtual CPU have an accurate TSC or does it provide entropy? Does the --synthcpu option change anything?

Does Virtual Box implement any measures to provide good entropy to virtual machines?

None of these questions is answered on virtualbox.org.",Tsso
11313,Can't assign guest audio to dedicated sound device on Host,Windows,all,VirtualBox 4.2.6,2012-12-20T22:40:02Z,2012-12-20T22:40:02Z,"I would like to assign all audio from a Guest into a specific audio device so that my kids can listen to audio on the Guest while I work on the host or other guests. I am using Windows 7 64-bit as Host.

The simplest solution would be to allow the guest audio to be directed to a specific audio device. This is possible using windows APIs, but in absence of choosing a device, VirtualBox sends all audio to ""Default Device"", which is then the same as all other Guests, as well as the Host. Therefore, all audio is mixed into 1 stream, which prevents isolation.",random_luser
11330,SDK - IGuestSession - enhance guest process management functions,Windows,Windows,VirtualBox 4.2.6,2012-12-25T01:52:08Z,2012-12-25T01:52:08Z,"Hi,

I'm working on a custom-made test automation framework and I was having high hopes with VirtualBox for my VM-based automation needs.
I'd like to see IGuestSession interface augmented with methods such as:

-Get list of ALL guess processes, not only those explicitly created through IGuestSession::CreateProcess()

-Bind/attach to an EXISTING guest process (not previously created via IGuestSession) and get an IProcess object wrapper around it, in order to be able to sync on it (i.e. wait for termination)

Considering how powerful the level of VirtualBox automation is currently (at least for windows guests - i.e. things like auto-logon, process execution, file injection/copying), tt would be a real pity not to have a 1st-class, built-in solution for more complete process management.

By having such support, we wouldn't have to rely on activating network support on the windows guest OS and mess with Microsoft Process/Debug diagnostics API and SMB/RPC calls (i.e. see Process.GetProcesses(string machineAddress) method in .NET Framework).",smihaila
10768,RFE: Restore snapshot default to not save current state,Mac OS X,all,VirtualBox 4.1.18,2012-12-29T15:09:39Z,2012-12-29T15:09:39Z,"Until fairly recently, the default on restoring a snapshot was to not save the current state. This has changed relatively recently to by default store the current state. 

The new default causes me (and doubtless others) many problems: I have inadvertently clicked 'OK' on a number of occasions, and thereby constructed a forked snapshot structure. Unfortunately this seems to be fairly buggy (at least on osx and linux hosts) and I have ended up with difficult restorations on a number of occasions.

Ideally, I'd like to see the default set back to what it was originally (i.e. don't save the current state). However I can see there are arguments on the both sides if some hosts (I'm guessing windows) support more complex snapshot structures reliably. So if changing the default back isn't possible, please can you consider providing a user option to change the default behaviour. 

I'm marking this as OSX, but the same issue also applies to linux (unfortunately marking all would include windows, where it may not apply).",Bob
9769,Blue screen during install of Windows XP with slipstreamed SATA driver,other,other,VirtualBox 4.1.4,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
11358,VBoxManage cannot resize fixed size disks,all,other,VirtualBox 4.2.6,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
950,Autostart a vm on startup,other,other,VirtualBox 1.5.2,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
11389,Create new disk in Virtual Media Manager,all,all,VirtualBox 4.2.6,2013-01-14T13:32:04Z,2013-01-14T13:32:04Z,"If possible, please, consider to add a button in the Virtual Media Manager to add a new Hard Disk, Optical Disk or Floppy Disk, without associate it to a virtual machine.

Thank you.",Dudytz
8769,VLAN tagged packets mangled on bridged adapter,Linux,other,VirtualBox 4.0.6,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
11397,Clipboard stops working,Windows,Linux,VirtualBox 4.2.6,2013-01-16T18:17:25Z,2013-01-16T18:17:25Z,"The clipboard stops working completely (not just host<->guest, but on the guest itself) when a remote desktop session is established with the guest.

The clipboard on the guest can be brought back to life if the 'Shared Clipboard' is 'disabled' on the 'Devices' menu.

I am also remote-desktop'ed into the host when this problem occurs.",cruvis
990,[feature-request] parallel port,other,other,VirtualBox 1.5.2,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
10094,Valgrind's memcheck hard to use with VirtualBox OpenGL drivers,other,Linux,VirtualBox 4.1.8,2013-01-21T10:34:22Z,2013-01-21T10:34:22Z,"'''Host:''' Windows 7 64 bit with nvidia GPU.[[BR]]
'''Guest:''' Ubuntu with VirtualBox OpenGL driver.

=== Test case ===
{{{
/* gcc test.c `sdl-config --libs --cflags` */
#include <SDL.h>

int main( int argc, char** argv )
{
	SDL_Init( SDL_INIT_VIDEO );
	SDL_SetVideoMode( 16, 16, 32, SDL_OPENGL );
	return 0;
}
}}}

=== Steps to reproduce ===
 1. Compile the test case.
 1. Run the compiled program through valgrind's memcheck tool (run {{{valgrind ./a.out}}}).

=== Results ===
Valgrind reports a significant amount of errors originating in VirtualBox OpenGL driver. Example:
{{{
==3028== Conditional jump or move depends on uninitialised value(s)
==3028==    at 0x51193B9: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x50D588B: crNetDispatchMessage (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DF2EB: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DEBCE: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DEF64: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50D517B: crNetSend (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x511962D: packspuFlush (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x51178A8: packspu_CreateContext (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x57B42D2: feedbackspu_CreateContext (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLfeedbackspu.so)
==3028==    by 0x501984C: stubMakeCurrent (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGL.so)
==3028==    by 0x502EC53: vboxstub_glXMakeCurrent (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGL.so)
==3028==    by 0x5031E49: vbox_glXMakeCurrent (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGL.so)
==3028== 
==3028== Use of uninitialised value of size 4
==3028==    at 0x5119338: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x51193FC: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x50D588B: crNetDispatchMessage (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DF2EB: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DEBCE: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50DEF64: ??? (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x50D517B: crNetSend (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLcrutil.so)
==3028==    by 0x511962D: packspuFlush (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x51178A8: packspu_CreateContext (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLpackspu.so)
==3028==    by 0x57B42D2: feedbackspu_CreateContext (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGLfeedbackspu.so)
==3028==    by 0x501984C: stubMakeCurrent (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGL.so)
==3028==    by 0x502EC53: vboxstub_glXMakeCurrent (in /opt/VBoxGuestAdditions-4.1.8/lib/VBoxOGL.so)
}}}
The amount of reported errors increases with each single OpenGL instruction used in code. Such behavior makes looking for real application errors very hard, if not impossible to do.

Note that, despite all the errors reported, VirtualBox OpenGL drivers do NOT misbehave in any way (whether running under valgrind or not).

=== Expected result ===
Valgrind reports no errors, or the errors number is very limited and they originate from SDL or X. This happens when the test case is run on a non-virtualized Linux machine with nvidia drivers.

=== Additional info ===
Other people also have reported this issue:[[BR]]
https://forums.virtualbox.org/viewtopic.php?f=6&t=32378 [[BR]]
https://forums.virtualbox.org/viewtopic.php?f=3&t=45319",wolf42
11417,User Manual controlvm options,other,other,VirtualBox 4.2.6,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
11333,configure script rejects --prefix,Linux,other,VirtualBox 4.2.6,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
11476,build time dependences not documentend in debian control file,Linux,all,VirtualBox 4.2.6,2013-02-09T05:11:26Z,2013-02-09T05:11:26Z,"building from a svn copy (4.2.51~svn-1) in a debian wheezy with vanilla 3.6.7 stable kernel.

packages that are needed to build virtualbox but are not indicated at build environment check time, so dpkg-buildpackage does not complain while they are not installed and build ends up failing later:

libdevmapper-dev
makeself 

also, linux-headers-generic is obsoleted and uninstallable in wheezy so I have benn forced to build vbox with 
dpkg-buildpakage -d",AlejandroAmo
11491,VirtualBox GUI unnecessary dynamic and complex.,Mac OS X,other,VirtualBox 4.2.6,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
11493,Showing device UUID in Virtual Media Manager,Mac OS X,all,VirtualBox 4.2.6,2013-02-15T09:10:06Z,2013-02-15T09:10:06Z,"Hello,

The list of hard drives in the Virtual Media Manager currently shows name, location, format, storage details and attached to, but not the device UUID. It seems there is currently no option to obtain the device UUID using the GUI interface.

For instance, when setting up Oracle Linux with several hard disks attached to the virtual machine, the installer can list the device name, but it cannot determine the disk image name. 

To be able to obtain the UUID of a disk image file would help as it corresponds to a device's serial number, which is shown in the OS installation dialog.

Kind regards.",Dude
11497,"When starting on user login in windows in fullscreen mode, vb loses focus",Windows,Linux,VirtualBox 4.2.6,2013-02-16T15:00:00Z,2013-02-16T15:00:00Z,"I have set up virtualbox to start up when the Windows user logins, By setting up the virtualbox command line tool to be run in a script on Windows user login, to start virtualbox on start up from a script when the windows user logs in. I wish for it to be started in fullscreen mode so the Windows UI is not visible at all, including the Windows taskbar covered up.

The problem is, after virtualbox starts when the user logs in, the Windows taskbar appears at the top of the screen even though virtualbox is in fullscreeen mode, and virtualbox loses focus. Virtualbox needs to add a stayontop option for use from the virtualbox command line tool to tell virtualbox to stay on top and regain focus if virtualbox happens to lose focus and make sure the windows taskbar stays covered up.

I also request a ""screenmode"" vboxclient option for specifying display mode to use, such as ""fullscreen"", when the vboxclient virtualbox command line program is used, to assure that virtualbox is started in fullscreen mode, by supplying this fullscreen option to vboxclient, when started from with vboxclient from my startup script. ",David
11508,No detection of screen size change in fullscreen when using xubuntu/xfce4 as host,Linux,Windows,VirtualBox 4.2.6,2013-02-20T17:10:36Z,2013-02-20T17:10:36Z,"With Ubuntu (Unity/metacity or compiz), no problem.
With xfce4, I can resize the screen with xrandr or the xfce4 tools, vbox does not detect it. If I go windowed then fullscreen again (host + f), the vbox screen is resized correctly (and I see Display::handleDisplayResize() in logs).
In case it's xfce's fault, is there a way to send the Display::handleDisplayResize() event manually?",acathla
9527,'Shared Folders' returning incorrect file order to Win API,Linux,Windows,VirtualBox 4.1.2,2013-02-20T20:06:36Z,2013-02-20T20:06:36Z,"I am using some proprietary software on Windows XP guest under Linux host. This software (Magpie from MEA in Australia) extracts certain data from certain binary files output from a datalogger and collates it in a database. When run in WinXP under VirtualBox with the data stored in a VirtualBox 'shared folder' mounted as a Windows network drive it loses data.  When the data is stored within the VirtualBox 'disk' it works fine and it also works fine when the data is on a real Windows network share.

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

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

Unfortunately, I am not a developer and have no idea how linux chooses to present it's files or anything further about these API calls...",solanum
11509,Host CD passthrough not consistant,all,all,VirtualBox 4.2.6,2013-02-21T16:59:29Z,2013-02-21T16:59:29Z,"When choosing the host CD as the attached media device to be able to view video or use as a writeable CD/DVD, I need to set this with the guest stopped.  After you change from the Host CD to an ISO, like the guest additions and then go back to the Host CD the passthrough is no longer enabled, requiring a complete shut-down of the guest to select and enable passthrough again.

I wonder if there is a way to make this default or at least add the CD/DVD passthrough as a VBoxManage controlvm function?",Perry G
11462,Problem font with VirtualBox from a terminal in Red Hat 6.2,Linux,Linux,VirtualBox 4.2.6,2013-02-22T14:11:53Z,2013-02-22T14:11:53Z,"Hi, 
When we launched !VirtualBox, we had only ""squares"" on the GUI.
{{{
[root# VirtualBox 
Xlib:  extension ""SYNC"" missing on display ""10.102.130.2:32.0"".
}}}
And firstable, we had a failed installation with vboxpci 
{{{
[root@opisidb1 log]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modulesWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Trying to register the VirtualBox kernel modules using DKMSWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxpci failed. Please use 'dmesg' to find out why)

root#dmesg
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x51c offMax=0x28308
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x62c offMax=0x2a7f8
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x664 offMax=0x2a8d0
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x4fc offMax=0x27658
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
}}}",fornesi
11489,vboxmanage showhdinfo does not work with relative pathes,Linux,all,VirtualBox 4.2.4,2013-02-22T14:32:50Z,2013-02-22T14:32:50Z,"vboxmanage showhdinfo seems to be broken in 4.2.4 & 4.2.6[[BR]]

Some of my VDI disk :
{{{
virtualbox@gateway:~$ vboxmanage list hdds | grep vSRV001
Location:    /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
Usage:       vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)

}}}

This works :

{{{
virtualbox@gateway:~$ vboxmanage showhdinfo ""/home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi""
UUID:                 f6c75dcf-682b-4396-9e49-54202f465afe
Accessible:           yes
Logical size:         20480 MBytes
Current size on disk: 14461 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
In use by VMs:        vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)
Location:             /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
}}}

If I try using a . to refer from the current directory:
{{{
virtualbox@gateway:~$ pwd
/home/virtualbox
virtualbox@gateway:~$ vboxmanage showhdinfo ""./VirtualBox VMs/vSRV001/vSRV001-001.vdi""
VBoxManage: error: Cannot register the hard disk '/home/virtualbox/./VirtualBox VMs/vSRV001/vSRV001-001.vdi' {f6c75dcf-682b-4396-9e49-54202f465afe} because a hard disk '/home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi' with UUID {f6c75dcf-682b-4396-9e49-54202f465afe} already exists
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBox, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())"" at line 178 of file VBoxManageDisk.cpp
}}}

But this would work:
{{{
virtualbox@gateway:~$ pwd
/home/virtualbox
virtualbox@gateway:~$ vboxmanage showhdinfo ""VirtualBox VMs/vSRV001/vSRV001-001.vdi""
UUID:                 f6c75dcf-682b-4396-9e49-54202f465afe
Accessible:           yes
Logical size:         20480 MBytes
Current size on disk: 14461 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
In use by VMs:        vSRV001 (UUID: 30740f89-b026-466f-9b78-9cd8000e0f0d)
Location:             /home/virtualbox/VirtualBox VMs/vSRV001/vSRV001-001.vdi
}}}

I understand the check to find if the disk has a corresponding UUID but the path check seems off to me.",Max D
11514,Time sync: incorrect host time,Windows,Linux,VirtualBox 4.2.6,2013-02-26T15:01:24Z,2013-02-26T15:01:24Z,"I have noticed that I do not get the time set correctly on my virtuals machines. They do sync but are always behind the host's time (which is set per ntp correctly) and funnily the times between several VMs running on the same host vary.

When I started to dig for the reason I started VBoxService with -vvv and saw that the Host time displayed there was not the actual time of the host (i.e. the windows machine on which the VMs are running).

I expected the time shown in the log as ""Host:"" would be the host time, e.g:
{{{
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z
}}}
Unfortunately it differs from the hosts time. Even more suspicious: it differs differently on various VMs of the same host.
Could this be the reason why time sync does not work correctly?

Below more debug output.

{{{
root@orpdm-03:~#  /usr/sbin/VBoxService -f -vvv --enable-timesync --timesync-interval 1000
VBoxService 4.2.4 r81684 (verbosity: 3) linux.amd64 (Oct 26 2012 19:49:17) release log
00:00:00.002083 main     Log opened 2013-02-22T13:37:48.290070000Z
00:00:00.002159 main     OS Product: Linux
00:00:00.002180 main     OS Release: 3.2.0-37-generic
00:00:00.002199 main     OS Version: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002388 main     OS Service Pack: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002412 main     Executable: /opt/VBoxGuestAdditions-4.2.4/sbin/VBoxService
00:00:00.002415 main     Process ID: 31071
00:00:00.002418 main     Package type: LINUX_64BITS_GENERIC
00:00:00.002608 main     4.2.4 r81684 started. Verbose level = 3
00:00:00.002766 main     Initializing services ...
00:00:00.003517 main     Service client ID: 0x24
00:00:00.003767 main     VMInfo: Property Service Client ID: 0x25
00:00:00.003810 main     VBoxServiceBalloonInit
00:00:00.003847 main     MemBalloon: VbglR3MemBalloonRefresh failed with VERR_PERMISSION_DENIED
00:00:00.003942 main     Service 'memballoon' was disabled because of missing functionality
00:00:00.003965 main     VBoxServiceVMStatsInit
00:00:00.004058 main     VBoxStatsInit: New statistics interval 0 seconds
00:00:00.004102 main     VBoxServiceAutoMountInit
00:00:00.004353 main     VBoxServiceAutoMountInit: Service Client ID: 0x26
00:00:00.004393 main     Starting services ...
00:00:00.004414 main     Starting service     'control' ...
00:00:00.004706 control  Waiting for host msg ...
00:00:00.004831 main     Starting service     'timesync' ...
00:00:00.005097 main     Starting service     'vminfo' ...
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z    (MinAdjust: 100 ms)
00:00:00.005341 vminfo   Writing guest property ""/VirtualBox/GuestInfo/OS/Product"" = ""Linux""
00:00:00.005413 timesync VBoxServiceTimeSyncWorker: Guest: - 2013-02-22T13:37:48.293063000Z => 119 171 937 000 ns drift
00:00:00.005509 timesync VBoxServiceTimeSyncAdjust: adjtime by 119 171 937 000 ns
}}}",Markus
11562,VirtualBox does not honour regular/shareable disks while cloning.,Linux,Linux,VirtualBox 4.2.6,2013-03-05T07:35:57Z,2013-03-05T07:35:57Z,"Linked copy doesn't clone any disks. Full copy clones all disks, even when they are shareable. It would be cool to have third clone option, that clones all regular disks and uses shareable disks with the same properties and from the same location, like the source VM.
For example, it would be convenient for Oracle RAC emulation setup.",sknaumov
11570,NPIV Support Request,all,other,VirtualBox 4.2.8,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
7822,"[feature-request] Scale Mode: option to ""keep original aspect ratio""",other,other,VirtualBox 3.2.12,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
11640,"vboxsf does not support noatime,nodiratime,discard options",Windows,Linux,VirtualBox 4.2.10,2013-03-25T01:30:53Z,2013-03-25T01:30:53Z,"When using a mount (/etc/fstab), for example as follows:

ssd /ssd vboxsf noatime,nodiratime,discard 0 0

And trying to mount, you get:

[roel@localhost /]$ sudo mount -a
unknown mount option `noatime'

Removing the options one by one shows it does not support any:

unknown mount option `nodiratime'
unknown mount option `discard'

Yet, using 'defaults', i.e.:

ssd /ssd vboxsf defaults 0 0

Works fine.

This is very significant, as it does not allow for mounting a SSD with SSD recommended options (noatime,nodiratime,discard).",RoelV
11338,OS/2 VBOXSERVICE.EXE 4.2.6 not working,Windows,other,VirtualBox 4.2.6,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
6049,JACK audio support for Virtualbox (Linux host),Linux,other,VirtualBox 3.1.2,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
9926,No virtual system boot with grub2 on mbr for raw disk access to specific partitions,Windows,Linux,VirtualBox 4.1.6,2013-04-04T06:48:32Z,2013-04-04T06:48:32Z,"Recent Linux systems, such as Fedora 16, use the newer grub2 boot loader.  The usual grub2 setup places the boot code on the mbr and on the unpartitioned sectors immediately follow the mbr partition.  If a virtual guest Linux system is made using raw parition access to Linux code on a partition(s) separate from the host system partition(s), the grub2 boot code is not accessible unless the whole disk is attached rather than just the partitions containing the guest system.

For example, with a Windows 7 64bit host on partition 3 of disk 0 and Fedora 16 on partitions 5 and 6, and with grub2 installed on the mbr of disk0, VirtualBox will not boot a Fedora 16 x86_64 guest unless the vmdk is created with whole disk access to disk0.  If the vmdk is created with access to only partitions 5 and 6, Fedora does not boot and hangs after the boot code in the mbr is executed.  The code in the sectors following the mbr sector is not reached.  Given that it is dangerous for the virtual system to have direct access to the host operating system code, the grub2 boot code should be accessible when only individual partitions are attached.  For Windows hosts, the -relative option is not available for createrawvmdk so this option cannot be tested as a solution with Windows hosts.
",Leo Pilachowski
8401,[feature-request] Direct Linux Boot,other,Linux,VirtualBox 4.0.4,2013-04-07T20:50:43Z,2013-04-07T20:50:43Z,"Direct Linux Boot means that the user can specify guest kernel and initrd and boot Linux guest directly, either from CD/DVD, or from HDD, bypassing guest's bootloader.

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

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

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

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

-Technologov, 22.02.2011.",Technologov
2251,cannot specify disk geometry,Mac OS X,other,VirtualBox 2.0.2,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
11687,Please add support for Guests to control Host Audio Volume (+/-),Linux,all,VirtualBox 4.2.10,2013-04-19T19:37:36Z,2013-04-19T19:37:36Z,"Please add support for Guests to control Audio Volume (+/-). Probably best to add a check box in the Audio Section of the Settings GUI (where it says Enable Audo; Host Audio Driver = ALSA; Audio Controller = Intel HD Audio).

Right now if I watch a video in Guest OS in Full Screen, and I need to increase or lower the volume I have to 
1. Pause the Video
2. Exit full screen mode
3. Go to the Host OS to increase or lower the volume
4. Then go back to the Guest OS and change it to full screen mode.
5. Resume Video and hope it is the correct volume or go back to Step 1.",Quickbooks Office
11516,Please consider adopting the phpvirtualbox project,other,other,VirtualBox 4.2.6,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
6102,VirtualBox cannot load split VHD files.,other,other,VirtualBox 3.1.2,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
11017,Outdated SMBIOS version,other,other,VirtualBox 4.2.0,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
11846,Setting the medium description not implemented,Windows,all,VirtualBox 4.2.12,2013-06-07T13:56:08Z,2013-06-07T13:56:08Z,"Setup
Host: Core i5 3gen (quad core), 16GB RAM, Windows 8 Pro 64 bits.
Guest: 4 cores, 4GB RAM, 2 alread, no OS installed.

I created a disk and attached to a VM with vboxmanage. While the attaching was successful, it gave me some errors:

C:\Users\luka\Desktop>vboxmanage createhd --filename ""E:\asm\asm-vol00.vdi"" --size 20480 --variant Fixed
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Disk image created. UUID: 706f7563-882f-4da2-91c5-3a593dcd957a

C:\Users\luka\Desktop>vboxmanage storageattach ""RAC n1"" --storagectl SATA --port 2 --type hdd --medium ""E:\asm\asm-vol00.vdi"" --mtype shareable --comment ""Disco para ASM""
VBoxManage.exe: error: Method Medium::put_Description is not implemented
VBoxManage.exe: error: Details: code E_NOTIMPL (0x80004001), component Medium, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Description)(bstrComment.raw())"" at line 685 of file VBoxManageStorageController.cpp",chesterman
11856,Quick shutdown of all vms wanted,Linux,all,VirtualBox 4.2.12,2013-06-12T08:36:25Z,2013-06-12T08:36:25Z,"This is not a bug, but an enhancement-question


I'm running Debian 7.0.
When i'm shutting down the system 
(This can manual or automatic or by powerloss and other causes..)
Init sends the SIGTERM signal and 5 sec later the SIGKILL.

In the /etc/rcx.d  the vbox-services are executed for shutdown/reboot at the beginning of the shutdown/reboot.
K02vboxautostart-service
K02vboxballoonctrl-services
K02vboxweb-services
K03vboxdrv
(after this unmouting nfs takes place)

Because of the shutdown order, i cannot move the proces more to the back. I can only try to shutdown the vm's before vboxservices are going down. This means a K01 for my script.

I did make a script to put the vm's in savestate one by one. (because a powerdown will not work for some machines.)
Saving a machine takes a few seconds.
I want to save 5 or more vm's.

By default i can save one vm.
With some tuning i can save 4 vm's before the host go's down.

The problem is, that the other vm's are just stopped. And could lose data, because the proces is killed, without the change to save the state off the machine.


I have a question.

Is it possible to make a command likje this:

vboxmanage controlvm all savestate

And that this command brings all machines down '''at once'''.
Not one after an other but alltogether. So it go's quicker and can be done in 5-10 sec.

Or an other sollution would be, the possibility to run commands on the background. So i can call all vm's one by one and don't have to wait for finishing before i can call the next one.

something like this:

vboxmanage controlvm <vm> savestate &

Thanks





",ED
11860,error starting VM in batch when the path to VM have Unicode characters,Windows,all,VirtualBox 4.2.12,2013-06-13T07:02:18Z,2013-06-13T07:02:18Z,"When I start <<VirtualBox.exe --startvm ""path_to_VM"">> it works only if path_to_VM doesn't have some Unicode characters (specific to a language, like the u with 2 dots above from Munchen).
It shows an error message saying that the VM was not found and it displays the path with those Unicode characters doubled into some strange ones.
If I start <<VBoxManage.exe  --startvm ""path_to_VM""/UUID>> or <<VirtualBox.exe --startvm UUID>> it works with any combination.
But I prefer using <<VirtualBox.exe --startvm ""path_to_VM"">> so could you please fix it...?
Thank you.

Regards, Cosmin",Cosmin
11876,should change char to wide character in VBoxStub.cpp,Windows,all,VirtualBox 4.2.12,2013-06-18T07:54:47Z,2013-06-18T07:54:47Z,"
If a user name is not english(such as East Asia Lang.-Korean, Japanese..), current stub code can not extracts msi and cab file.

or one of way is

do not use user's temp folder. (like C:\TEMP_VIRTUALBOX) but it is not good way.

",Woof
11885,Automatically detect SSD status of a virtual disk,other,other,VirtualBox 4.2.12,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
11922,Document on creating CD/DVD (and installing Guest Additions) do not mention VM must be shut down,Linux,Linux,VirtualBox 4.2.14,2013-07-04T19:52:51Z,2013-07-04T19:52:51Z,"I'm running a CentOS 6 VM guest on an XUbuntu 13.04 host using virtualbox 4.2.10_Ubuntu r84101

Under Machine -> Settings -> Storage, the menu item to ""Add a CD/DVD Device"" is disabled for both the IDE and SATA controllers.

Neither https://www.virtualbox.org/manual/ch04.html#idp14782496 
nor https://www.virtualbox.org/manual/ch03.html#settings-storage say anything about shutting down in order to use Device -> Storage -> Add CD/DVD Device.

The latter says ""You can modify these media attachments freely.""

Please add text to these manual pages to make it clear how to add a CD or DVD device.
",David Biesack
6057,[feature-request] Installer: warn users for incompatible drivers on Windows host,Windows,other,VirtualBox 3.1.2,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
12045,Cannot attach new vm via multiattach when another vm is running,other,other,VirtualBox 4.2.14,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
12071,OpenGL 4.2 not supported,all,all,VirtualBox 4.2.16,2013-09-04T19:16:38Z,2013-09-04T19:16:38Z,"Hello

Opengl in Guest machine VirtualBOX work good !
But opengl 4.2 is not supported by VirtualBOX on guest machines.
OpenGL 4.2 Function is not available.

Thank.



",yann458
12084,extension pack,all,all,VirtualBox 4.2.18,2013-09-08T17:53:03Z,2013-09-08T17:53:03Z,"Would be nice to see what extension pack is installed for a vM in the ""General"" box of the virtualbox manager field, besides the name and OS.  Have many vm's and some need updating and some dont, always a pain to have to startup the vm to see what the currently installed extension pack version is.

thanks,
art",ArtZ
12106,Include Quiet Mode in VBOXGUEST.SYS,all,other,VirtualBox 4.2.18,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
4184,Allow network drive mapping too all shared folders,other,Windows,VirtualBox 2.2.4,2013-09-18T16:57:43Z,2013-09-18T16:57:43Z,"When I used VMware I could map a network drive (under Windows XP guest) to all shared folders within the host (Windows Vista). This was easy because when I went to:
My Network Places » Entire Network » VMware Shared Folders

There was a ""folder"" holding all shared folders and I could just map that folder to a network drive.

This doesn't seem to be possible with VirtualBox. When I go to ""VirtualBox Shared Folders"" in the network, I see one entry by shared folder and I have to map each folder to a network drive, which sucks if I have a bunch of shared folders.

Is it possible to do the same as VMware does in a future release?
",Nazgulled
11297,poor entropy performance,all,other,VirtualBox 4.2.4,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
12120,Cannot create snapshot with ampersand in the title,other,other,VirtualBox 4.2.18,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
11778,Version names and error messages are not translatable.,other,other,VirtualBox 4.2.12,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
12174,Configure internal DHCP server to pass arbitrary domains,other,other,VirtualBox 4.2.18,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
2282,Blue screen during install of Windows XP with slipstreamed SATA driver,other,Windows,VirtualBox 2.0.2,2013-10-21T06:20:57Z,2013-10-21T06:20:57Z,Attempt to install Windows XP SP3 (slipstreamed) with slipstreamed driver Intel Matrix 7.0.0.1020 results in blue screen ,vadimrapp
12294,"small VM icon inconsistency, suggest using '2000' not 'w2k'",other,other,VirtualBox 4.3.2,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
12331,The documentation is not entirely up to date regarding the NAT service,other,other,VirtualBox 4.3.2,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
12352,Request: Option to store differencing image on same host device as base image,Linux,all,VirtualBox 4.2.18,2013-11-12T20:33:09Z,2013-11-12T20:33:09Z,"I have a host with two drives, one SSD and one HD.
I have a guest with two .vdi's. The guest os (/) is on the host SSD and file storage .vdi (/home) is on the larger host HD.
However when snapshots are used, the differencing image is always stored in the default VM location. This makes snapshots unusable with multiple host storage locations.
whatever folder structure you would like is fine, (i.e. subfolder called snapshots) I would just like to see an option to store the differencing images on the same host media.

I have read through the forums, about the closest thing I've found was a request for a custom differencing folder (ramdisk)",ImEdwardo
12361,Autostart config doesn't allow for shared storage of VM files,all,all,VirtualBox 4.3.2,2013-11-14T05:12:53Z,2013-11-14T05:12:53Z,"As others have done I have several virtualbox servers which store the VM definitions on a common NFS share to facilitate rebalancing loads, maintenance, and teleportation.  The current implementation of autostart uses a config entry in the VM definition .vbox file to determine whether the machine should autostart, but that won't work in the case where the machine definition has been registered on multiple machines, it'd try to autostart on all of them.

I believe the autostart config should not be stored in the machine config file, but in the ~/.VirtualBox directory which can still be specific to the server machine even though the VM definition is shared across servers.",Steve Prior
12362,Add possibility to update snapshots,all,all,VirtualBox 4.3.2,2013-11-14T09:51:50Z,2013-11-14T09:51:50Z,"Sometimes I want to start a VM with a specific snapshot, do some work and then create a snapshot with the current state that replaces the old one.

At the moment, I would have to create the new snapshot and afterwards manually delete the old one.

It would be more convenient, if I could simply update the old snapshot so it contained the current state.


Lars
",larsen0815
12287,VBox 4.3.2 Video Capture without cursor,Mac OS X,Linux,VirtualBox 4.3.2,2013-11-18T14:49:39Z,2013-11-18T14:49:39Z,The VBox 4.3.2 Video Capture cannot capture the cursor as well.,Samiux
11997,Switching virtual machines (feature request),all,all,VirtualBox 4.2.16,2013-11-18T15:15:10Z,2013-11-18T15:15:10Z,"How about to add a hotkey to switch between running virtual machines and the pop-up menu to select and run existing virtual machines.

[[Image(http://img199.imageshack.us/img199/6382/7c0.png)]]

Sorry for my bad English.",Octane
11081,"Using Bridged Adapter, Allow Option for Host Cable/Connection State to Passthrough to Guest",all,all,VirtualBox 4.2.2,2013-11-25T17:28:31Z,2013-11-25T17:28:31Z,"While the ability to set the cable connection state is helpful for testing, I find (especially on a laptop with wired and wireless adapters) that most often I want the host cable state (or equivalent wireless connection state) to pass through to the guest, such as going for home to work and back to home networks, a typical daily example. Currently, I run a batch file on the new network to issue VBoxManage command to do this manually. For guests that obtain their own address from the physical network, it would be a convenient option to have the guest detect the host's connection state and pick-up a new address config on the connection to a new network.",CM7
12403,Feature Request - Mount VDI as Windows Drive,Windows,other,VirtualBox 4.3.2,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
12440,"Option to capture USB for whole VB run, or even globally",Windows,all,VirtualBox 4.3.4,2013-12-04T18:45:18Z,2013-12-04T18:45:18Z,"Running on Windows, it seems USB capturing works on a per-VM invocation basis. You start the VM, insert the USB device, and it's captured until the VM exits. This means that multiple runs of the VM require removing and reinserting the USB device every time.

It would be useful to have an option to capture USB for the whole VirtualBox session, rather than a single VM run. 

Possibly, even a system-global capture would be useful, where the USB filter parameters would be stored by the host USB capture driver and acted upon even before VB runs. In such a case, the VB GUI (or maybe a property sheet for the USB capture driver) could have a ""release capture"" option. 

A system-global capture would prove useful in scenarios where a USB device is there exclusively for VM usage. A system-global capture would mean no removal/reinsertion at all.
",emu1
12487,Disable ICH9 Chipset for NetWare Guests,Windows,other,VirtualBox 4.3.4,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
12535,Notification dialogs should move when Mini ToolBar position is changed,other,other,VirtualBox 4.3.6,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
12540,Link to VirtualBox Manager for Android from website,all,all,VirtualBox 4.3.6,2013-12-25T03:11:27Z,2013-12-25T03:11:27Z,"There is a link to phpVirtualBox (not an offical Oracle application) from www.virtualbox.org which is a webservice client UI.  I created a similar app called VirtualBox Manager for Android which is now a robust and open source application which has almost all the same functionality.  I was hoping to see a link to it from the virtualbox.org website.  It is available on the Google Play Store and source is available on github.

[https://play.google.com/store/apps/details?id=com.kedzie.vbox]
[http://www.github.com/kedzie/VBoxManager]",Mark Kedzierski
12549,async I/O bug,all,all,VirtualBox 4.3.6,2013-12-28T19:31:18Z,2013-12-28T19:31:18Z,"Hello,[[BR]]
I had some problems with async I/Os so I looked at the implementation in more details. VirtualBox is not able to handle multiple requests, when e.g. VD.cpp!vdIOIntWriteMeta is called several times and crash.

Repro steps:
1. Assume VD.cpp!vdIOIntWriteMeta is called (pMetaXfer block is allocated, pfnWriteAsync is called, pMetaXfer is insterted into pTreeMetaXfers).
2. Another vdIOIntWriteMeta call is invoked, let's say for the same block. The first request has not been completed yet so pMetaXfer is received (line 4428) from the tree. Assert on line 4443 is invalid, because pMetaXfer->fFlags is set to VDMETAXFER_TXDIR_WRITE. Now, vdMetaXferCompleted is invoked for the first request - pMetaXfer context is removed from the tree (line 3784) and freed (line 3786). When the second request is completed, this request works with already freed pMetaXfer context.

The same problem is also for vdIOIntReadMeta + vdIOIntFlush functions.

I fixed this by referencing volatile VDMETAXFER.cRefs (ASMAtomicDecU32/ASMAtomicIncU32) before I call pfnReadAsync (line 4336)/pfnWriteAsync/pfnFlushAsync functions. 

Thanks,[[BR]]
Petr Kurtin",Petr Kurtin
12560,[Feature request] Anonymous virtual machines.,all,all,VirtualBox 4.3.6,2014-01-01T18:34:35Z,2014-01-01T18:34:35Z,"Hi. I have a feature request. Sometimes, we need to create from scratch, start and stop some virtual machines from a linux bash script. I have this through the VBoxManage command: register a new virtual machine, configure the disk adapter, attach the disk to it, and so on. Because this machines run in headless mode, the name are created by the bash script with a pseudorandom name.

In qemu, is much more simpler to start a virtual machine. Simply call the qemu executable with all the params need. But, in VirtualBox, we need to register the virtual machine, modify it to configure, start, stop, deregister it. And if I have duplicated one disk (with the same UUID) for two virtual machines, the second refuse to configures by the duplicated UUID. If the virtual machine crash, we need to test if they are registered before to restart it.

It is possible add a new mode like qemu without a virtual machine registration?. With this mode, a new executable can be created (for example vboxanonymous or something) which accept all params in the same command line (disks, ram memory, network cards, sound card, etc).

Thanks.

",marianito1234
6510,Timed Default Option When Close Is Detected,Windows,Windows,VirtualBox 3.1.6,2014-01-02T22:22:20Z,2014-01-02T22:22:20Z,"Currently, when VirtualBox detects a close request (i.e. the system sends one or the the clicks on the close button) it brings up the Close Virtual Machine dialog box and waits for a response.  It would be useful to have the ability to select one of the three options as a timed default.  IOW, if the user didn't respond within n seconds VirtualBox would execute the default selection.

This would provide a way to gracefully close a VM when the host initiated a logoff or a shutdown while the user was not at the machine.
",Stewart Berman
12590,Add Run from last snapshot workflow option,other,other,VirtualBox 4.3.6,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
1461,Virtualizing physical partition with createrawvmdk fails on Mac OS X Leopard,Mac OS X,other,VirtualBox 3.0.4,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
12614,New rpm packaging convention of 4.3 and autoupgrade in OpenSuse 13.1,other,all,VirtualBox 4.3.6,2014-01-15T22:37:10Z,2014-01-15T22:37:10Z,"OpenSuse 13.1 (and maybe other releases) contains VirtualBox 4.2.* divided in several 
rpm (sub)packages as virtualbox, python-virtualbox, virtualbox-guest-kmp-desktop,
virtualbox-host-kmp-desktop, virtualbox-qt ...

if one have installed the 4.2.* release from the original distribution (4.2.18) or
from the community distro (http://download.opensuse.org/repositories/Virtualizatio/openSUSE_13.1/, 4.2.20) and then tries to upgrade to 4.3.*  everything seams to work
as aspected. but this is not a supported upgrade in rpm sense.
no provides oder obsolets entries in the all-in-one 4.3 packade gives the installer a hint to
delete the old installation or inform the user about conflicts.

the trouble begins when some uncontrolled or automatic upgrade see the
existing old entry and simple overwrites the new installation with old stuff.
as a result /dev/vboxdru disappiers and so on.

suse 13.1 is actally heavely under development, its rather a .0 oder a beta version.
i simple foregot one of the 4.2 packages to delete and than i spend a long time to underestand
what was going on.

my suggestion is to place additional Provides: statements with the old naming conventions
to the rpm or corresponding Obsoletes: statements. then the user will be informed and can decide what should happen.

regards
i.b.

(see also http://www.virtualbox.org/ticket/5884)






 
  ",iber
12635,Can't import to different basedir,Linux,other,VirtualBox 4.3.6,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
12669,Mac OSX  VBoxManage: error: Cannot read the partition information from '/dev/disk0',Mac OS X,all,VirtualBox 4.3.6,2014-02-06T03:58:51Z,2014-02-06T03:58:51Z,"I am trying to get !VirtualBox to boot up my Bootcamp Partition. Does anyone know why I'm getting the error ""VBoxManage: error: Cannot read the partition information from '/dev/disk0'""?

What I typed into terminal
{{{
WinXPmbp manila$ chmod 777 /dev/disk0 /dev/disk0s4
WinXPmbp manila$ sudo VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename ""/Users/home/VirtualBox/WinXPMBP/bootcamp.vmdk"" -partitions 4
Password:
VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
}}}",DonyorM
8985,Use 'addgroup' instead of 'groupadd' in installer,Linux,other,VirtualBox 4.0.8,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
32,"[feature-reques] Ability to suppress all stupid messages in ""File->Global Settings""",other,other,VirtualBox 1.3.4,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
12794,Icon-indication for Cloned-VMs (VirtualBox UI),all,all,VirtualBox 4.3.8,2014-03-07T07:21:44Z,2014-03-07T07:21:44Z,"While clone-parents show their cloned children in the description, the cloned VMs are not easily recognized (and hence not easily differentiated from VMs without children.)
I propose that the icons used for the VMs are modified for VMs which are based on cloned disks - they might f.e. have a little C in the corner.",BmyGuest
12812,*.start and *.stop scripts are not created by VBoxManage modifyvm myvm --autostart-enabled on,Linux,Linux,VirtualBox 4.3.8,2014-03-12T06:54:47Z,2014-03-12T06:54:47Z,"I have followed the steps in this tutorial: [http://www.vionblog.com/virtualbox-4-3-autostart-debian-wheezy/]

The problem is no *.start or *.stop files are created in /etc/vbox/ (and no errors are shown) after running the command:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled on
}}}

In case it helps, trying to disable auto start for the same VM does give an error:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled off
VBoxManage: error: Removing machine 'myvm' to the autostart database failed with VERR_FILE_NOT_FOUND
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(AutostartEnabled)(ValueUnion.f)"" at line 2616 of file VBoxManageModifyVM.cpp
}}}

Host os: Ubuntu Server 12.04-4 (amd64)

VirtualBox: 4.3.8

This issue was reported on the forum a few weeks ago, but there has been no reply:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=60425&p=282223#p282223]

Thanks!


For reference, here's user/group involved:

{{{
$ whoami 
dan
$ groups
dan adm cdrom sudo dip plugdev lpadmin sambashare vboxusers
}}}
 

The contents of /etc/vbox

{{{
$ ls -al /etc/vbox/
total 12
drwxrwxr-t   2 root vboxusers 4096 Mar 12 00:55 .
drwxr-xr-x 101 root root      4096 Mar 12 02:11 ..
-rw-r--r--   1 root root       239 Mar 12 00:55 autostart.conf
}}}

content of autostart.conf:

{{{
# Default policy is to deny starting a VM, the other option is ""allow"".
default_policy = deny

# user dan is allowed to start virtual machines but starting them
# will be delayed for 10 seconds
dan = {
 allow = true
 startup_delay = 10
}
}}}

uname:

{{{
$ uname -a
Linux ubu-host64 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
}}}",Dan Rollo
10190,"MS Flight beta report ""no Shader 3 support"" and close",Linux,Windows,VirtualBox 4.1.8,2014-03-17T03:53:44Z,2014-03-17T03:53:44Z,"I tried to install the new MS Flight beta on WinXP in VB4.1.8
I keep 3D acceleration activated with 128 MB dedicated to VideoRAM.
My Host is Linux Ubuntu 11.10, and the card is a NVidia G104M
The installation work, but on Flight start it detect ""no Shader 3 support"" and close.",Valerio Messina
12816,Scale Mode reworked into Zoom function,other,other,VirtualBox 4.3.6,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
12866,VBoxManage clonehd should fail early if not enough disk space,other,other,VirtualBox 4.3.8,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
11137,BIOS call int13h cannot access more than 4 HDDs on the SATA or SCSI controller.,Windows,all,VirtualBox 4.2.4,2014-04-06T21:32:35Z,2014-04-06T21:32:35Z,"When I set up 6 HDDs on SATA controller, BIOS in VirtualBox does not recognize last 2 HDDs. If the last 2 HDDs are connected to SCSI controller, i.e. 4 HDDs on SATA and 2 HDDs on SCSI, all the 6 HDDs can be accessed via int13h.

Similarly, more than 4 HDDs on SCSI and SAS controller cannot be accessed by int13.

This causes boot failure problem of linux in software RAID5 partition with 6 HDDs.

The ""User Manual"" says VirtualBox supports 4 HDDs to IDE, 30 HDDs to SATA, 15 HDDs to SCSI and 8 HDDs to SAS controller. Since real PC BIOS can access all the HDDs connected to SCSI controller as usual, this is a bug of VirtualBox BIOS, I believe.

This problem is also in version 4.2.2 and 4.2.0, and maybe older version.
",Yano
1871,Keyboard Mapping,Mac OS X,Windows,VirtualBox 1.6.2,2014-04-17T10:45:11Z,2014-04-17T10:45:11Z,"bonjour,

I use a MacBook Pro to virtualise Windows XP Pro OS.
My request is the possibility to use the Mac OS X 10.5 Keyboard Driver For Windows XP ""in the DVD"" or a VB driver that Map the unusual Mac keybord for a Canadian french configuration.
The work around is to use a external USB keybord with te conventionnal layout
It is the only way I have found to type the useful ""@"" key entry.
Not a very pratical solution when your on the go.
Denis.",Denis
12958,Virtualbox fails to start in headless mode with 3d acceleration enabled.,Mac OS X,Linux,VirtualBox 4.3.10,2014-04-18T00:47:53Z,2014-04-18T00:47:53Z,Virtualbox fails with uninformative message when 3d acceleration is enabled and guest OS is started in headless mode using shift+Start.,berkovskyy
11900,Windows host cannot see / follow symlinks in shared folder from Linux guest,Windows,Linux,VirtualBox 4.2.12,2014-04-24T11:14:35Z,2014-04-24T11:14:35Z,"I'm running an ubuntu guest on a windows 7 host. I have shared folders setup and working via a Vagrant file. My shared folder has a bunch of development files in it created using the Ubuntu guest, nearly all of which I can access from the windows host. 

{{{
$ ls -lah                              
total 13                                                                                  
drwxrwxrwx 1 vagrant vagrant 4096 Jun 25 14:06 ./                                         
drwxrwxrwx 1 vagrant vagrant 8192 Jun 24 19:49 ../                                        
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:51 brunch -> ../brunch/bin/brunch*            
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 cake -> ../coffee-script/bin/cake*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 cleancss -> ../clean-css/bin/cleancss*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 coffee -> ../coffee-script/bin/coffee*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 express -> ../express/bin/express*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 grunt -> ../grunt-cli/bin/grunt*           
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 jade -> ../jade/bin/jade*                  
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 nodemailer -> ../nodemailer/bin/nodemailer*
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 stylus -> ../stylus/bin/stylus*            
-rwxrwxrwx 1 vagrant vagrant   20 Jun 25 14:04 test*                                      
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:02 test2 -> test*                             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:05 test3 -> ../brunch/bin/brunch*             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 uglifyjs -> ../uglify-js/bin/uglifyjs*     
vagrant@mwalters:~/development/clp-web/node_modules/.bin$                                                                                                 
}}}

What's shown above (ls -lah run on Ubuntu guest) - 

1. 'test' file, created on Ubuntu guest is visible on Windows 7 host
2. 'test2' symlink to 'test', created on Ubuntu guest is visible on Windows 7 host
3. 'test3' symlink to file in another directory, created on Ubuntu guest is *not* visible on Windows 7 host (nor are any of the others which follow the same pattern). 

{{{
$ ls -lah                                                                  
ls: brunch: No such file or directory                                      
ls: cake: No such file or directory                                        
ls: cleancss: No such file or directory                                    
ls: coffee: No such file or directory                                      
ls: express: No such file or directory                                     
ls: grunt: No such file or directory                                       
ls: jade: No such file or directory                                        
ls: nodemailer: No such file or directory                                  
ls: stylus: No such file or directory                                      
ls: test3: No such file or directory                                       
ls: uglifyjs: No such file or directory                                    
total 7.0k                                                                 
drwxr-xr-x   15 mwalters Administ     4.0k Jun 25 10:06 ./                 
drwxr-xr-x   37 mwalters Administ     8.0k Jun 24 15:50 ../                
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test*              
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test2*                                                                             
}}}

What's shown above (ls -lah run on Windows 7 host) - 

Notice none of the files are recognized as symlinks. test2 is a symlink to test and all of the other files, including test3, are symlinks to files in other directories. None of them are registering or followable from the Windows host. 

Here is a copy of my Vagrant file: 

{{{
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(""2"") do |config|
  config.vm.box = ""precise32""
  config.vm.box_url = ""removed to allow me to post""

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  config.vm.network :forwarded_port, guest: 9983, host: 9983

  config.vm.hostname = ""#{ENV['USERNAME']}.dev""

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network :private_network, ip: ""192.168.33.10""

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  config.vm.synced_folder ""../../"", ""/home/vagrant/development""


  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
    vb.customize [""modifyvm"", :id, ""--cpus"", ""8""]
    vb.customize [""modifyvm"", :id, ""--memory"", ""12288"", ""--ioapic"", ""on""]
    vb.customize ['storagectl', :id, '--name', 'SATA Controller', '--hostiocache', 'on' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development/*', '1' ]
    vb.customize [""modifyvm"", :id, ""--natdnshostresolver1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--natdnsproxy1"", ""on""]
  end

config.vm.provision :puppet do |puppet|
    puppet.manifests_path = ""manifests""
    puppet.manifest_file  = ""init.pp""
  end
end
}}}

Additional info here: https://forums.virtualbox.org/viewtopic.php?f=6&t=56097&p=259861#p259861",mateodelnorte
12989,guest display size indicator,other,other,VirtualBox 4.3.10,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
3438,Feature Request:  Pass guest hyperlinks to host OS,Linux,Windows,VirtualBox 2.1.4,2014-04-30T08:26:37Z,2014-04-30T08:26:37Z,"It would be nice if there was a way through the VirtualBox guest addition drivers to permit hyperlinks clicked in the guest OS to be passed directly to the host OS operating system.  I forsee this being a selectable option, possibly through the ""shared folders"" option.  There should also be a modifiable key to bypass the option (such as cntrl-shift-click, which would leave the link in the guest OS).  URLs should probably be selectable (such as http:// and ftp:// links).  

My specific instance is that I only use my Windows virtual machine for Outlook.  I would prefer that most links I access would open in Firefox in Linux.  Thanks!",blamerson
13028,Vertical scrollbar scrolls very slow with mouse-wheel,Windows,Windows,VirtualBox 4.3.10,2014-05-15T12:34:56Z,2014-05-15T12:34:56Z,The 'Auto-resize guest display' is disabled. The guest screen size is set to 1280*1024 while the host screen size is 1366*768. At this time the vertical scrollbar displays but it scrolls very slow with mouse-wheel. It will be better if the scroll speed can be adjusted and mouse-wheel work outside the vertical scrollbar a bit.,abelli
13042,Support for Spice,other,other,,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
13054,metric enhancement - autostart,all,all,VirtualBox 4.3.12,2014-05-22T11:04:11Z,2014-05-22T11:04:11Z,"The ability to allow metric collection to '''auto start''' when the VM is started.  The metric will have to be predefined.

I use metrics to determine how busy the VM is so I can take/kill snapshots for backup purposes.

Also use metrics to monitor and alert if guests are running hot, out of resources, etc.

For the above and more reasons, it would benefit to have a predefined, auto-starting metric.",Senthil Nathan
13055,archive/save metric data,all,all,VirtualBox 4.3.12,2014-05-22T11:09:25Z,2014-05-22T11:09:25Z,"Requesting the ability to '''store / archive''' metrics.

Besides setting up a metric, for purposes of long-term data analysis, I will have to rely on a 3rd party tool (such as pnp4nagios) to keep track of resource requirement changes for VM over time.

It would be beneficial to have an local data collection / data archive of the collected metrics that can be directly queried.


",Senthil Nathan
13059,Guest Processor Affinity,all,all,VirtualBox 4.3.12,2014-05-22T23:34:22Z,2014-05-22T23:34:22Z,"Requesting a feature that specifies a guest should run with processor affinity. This can be even better if there is a way to specify if specific processes inside the guest need to run with processor affinity.

I have some single threaded long running process that perform well in the native machine as they are not thrown around different CPUs unlike the processes in the guest machine.",Senthil Nathan
13079,clonevm makes immutable hard disks normal in clone,Linux,Linux,VirtualBox 4.3.12,2014-05-31T12:22:05Z,2014-05-31T12:22:05Z,"When cloning a VM, '''ALL''' the cloned new VM's hard disks are of type '''normal''' whereas some of the source VM's hard disks are of type '''immutable'''.  Cloning is not preserving hard disk type and is resetting immutable hard disks to normal.

Both host and guest are Ubuntu Trusty Server.",Senthil Nathan
13141,Host+Tab support to switch between running VMs,all,all,VirtualBox 4.3.12,2014-06-24T20:15:34Z,2014-06-24T20:15:34Z,Can you support Host+Tab support to switch between running VMs?  (i.e. right Control+Tab)  This would be similar to the Alt+Tab feature used by many operating systems.,Seann
12780,VBoxSVC.exe crashes on Windows with VBox 4.3.8 when setting VBOX_USER_HOME,Windows,other,VirtualBox 4.3.8,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
13169,[feature-request] Network: Promiscuous mode for NAT,all,all,VirtualBox 4.3.12,2014-07-16T13:52:52Z,2014-07-16T13:52:52Z,"Hi,

I have 2 VMs with SSH servers on my host. I use user-space NAT. Host has IP: 192.168.4.82

I would like to be able to make a NAT route from a different host IP, like 192.168.4.201 and x.x.4.202 for those 2 VMs. I would be nice if VirtualBox NAT router could enter into ""promiscuous mode"" and allow the host listening on custom addresses (similar to what WinPCAP/libpcap and Wireshark do).

Today I have to use non-standard ports for this. Like:  

VM1:

Rule 1 | TCP | [blank host IP] | host port = 1001 | [blank guest IP] | Guest Port = 22

VM2:

Rule 1 | TCP | [blank host IP] | host port = 1002 | [blank guest IP] | Guest Port = 22

I would like to achieve this:

VM1:

Rule 1 | TCP | 192.168.4.201 | host port = 22 | [blank guest IP] | Guest Port = 22

VM2:

Rule 1 | TCP | 192.168.4.202 | host port = 22 | [blank guest IP] | Guest Port = 22

-Alexey Eromenko ""Technologov"", 6.July.2014",Technologov
11433,NAT port forwarding warning or overwrite,Mac OS X,all,VirtualBox 4.2.6,2014-07-16T14:54:07Z,2014-07-16T14:54:07Z,"What behavior should I expect if I run more than 1 virtual machines with the same port forwarding rule, e.g. TCP 2222 -> TCP 22?

Obviously port 2222 on the host system can only be forwarded to one particular virtual machine behind the NAT interface.

There is currently no error or warning when attempting such a setup. In practice, any subsequently started virtual machine that employs the same port forwarding rule is ignored:

09:01:55.697789 NAT: set redirect TCP host port 2222 => guest port 22 @ 10.0.3.15
09:01:55.697852 NAT: failed to redirect TCP 2222 => 22

I think the default behavior should be that the NAT router overwrites the previous rule. To update the ARP table regardless of existing devices is standard with router or server TCP/IP implementations. VirtualBox could perhaps print a warning, referring to which virtual machine currently uses the offending port forwarding rule, or deny startup.",Dude
13222,Add a config and an icon for Mageia,all,all,VirtualBox 4.3.14,2014-07-20T21:37:22Z,2014-07-20T21:37:22Z,Mageia Linux should be supported by Virtualbox since Mageia actively supports Virtualbox.,TinSmith
13233,Please enable fPIC for libraries,other,other,VirtualBox 4.3.14,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
13249,A requested new spin on Ticket#11176 Mouse integration and snap to default button in a guest OS,all,Windows,VirtualBox 4.3.14,2014-07-29T17:00:21Z,2014-07-29T17:00:21Z,"Please consider adding an option that could be enabled on trusted Windows guests that would allow guest-initiated mouse pointer movements to occur.

Many professionals use the ""Snap to default button"" on Windows hosts, and would like this option available on Windows guests.

If an optional checkbox is addded to VirtualBox Manager:
Settings \ General \ Advanced \ [X] Allow Mouse Pointer Snap
It would help to improve VirtualBox popularity for Windows Guests.

And by making this feature optional, it will not interfere with justifications for not allowing this level of control for all Guests by default.

Thank you for considering.

Original ticket#11176 text follows:

Mouse integration is a great feature, but misses one piece: guest OS can not control position of mouse pointer. This can be easily verified in the Windows XP guest OS. Go to the Control Panel/Mouse, select 'Pointer Parameters' tab and check the 'Snap to default button' checkbox. After this, with mouse integration disabled mouse cursor will jump to the default dialog button (eg, the OK button). It will not however, with mouse integration enabled. This will also cause problems with programs which move mouse cursor programmatically and expect it to actually move. 

Thank you again for considering.
",LanceLance
12089,Option to show host-side mouse pointer with mouse integration,other,other,VirtualBox 4.2.18,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
13263,RTPathUserHome lookup fails when using API in a windows service,Windows,all,VirtualBox 4.3.14,2014-08-06T11:16:18Z,2014-08-06T11:16:18Z,"RTPathUserHome uses environment variables to determine the user home directory. When accessing the API from a windows service the lookup for the user home directory fails.

Probably a solution would be to use SHGetFolderPathW for the lookup.

http://stackoverflow.com/questions/9542611/how-to-get-the-current-users-home-directory-in-windows",hakito
13267,more video ram please,Windows,Windows,VirtualBox 4.3.14,2014-08-07T02:13:23Z,2014-08-07T02:13:23Z,"some games need more vram to load texture, please change vram setting options to unlimited by host can uses free ram, thanks",CML
8564,WiFi network adapter,Windows,Windows,VirtualBox 4.0.4,2014-08-15T23:28:14Z,2014-08-15T23:28:14Z,"Currently there are only wired network adapters available. A wireless adapter should be available too.

Some WiFi networks need a certificate to gain access. This certificate may (sometimes) only be installed IF a WiFi network is present and active on the (guest) server.

To allow for the VM guest to gain full access to a certificate controlled WiFi network, even thou the VM host does not, the VM guests need a network adapter of type WiFi.

",dum
13298,Custom snapshot location for each virtual disk,all,all,VirtualBox 4.3.14,2014-08-18T15:41:39Z,2014-08-18T15:41:39Z,"I was hoping to set up a mirrored disk set up with zfs having two vdi'a stored on two different physical disks.  In theory then if one physical disk was lost I would still have my mirrored data.  However, due to the fact that I have snapshots the data is actually be written to the same physical disk despite the real vdi's being on two separate physical disks.

I request a feature to be able to define the location of snapshot files for each virtual disk.",jeremywj
10592,"Documentation for ""Restoring d3d8.dll and d3d9.dll"" is incomplete",all,Windows,VirtualBox 4.1.16,2014-08-25T11:50:47Z,2014-08-25T11:50:47Z,"A recent version of the Guest Additions installer on Windows implemented a check for ""corrupted"" versions of d3d8.dll and d3d9.dll. When the installer discovers an incorrect version of one of these files, it opens the following URL in the user's web browser:

http://www.virtualbox.org/manual/ch12.html#ts_d3d8-d3d9-restore

The instructions for Windows 7 are to replace the following files from the original Windows media:

{{{
C:\Windows\System32\d3d9.dll
C:\Windows\SYSWOW64\d3d8.dll
C:\Windows\SYSWOW64\d3d9.dll
}}}

The instructions are incomplete, however, as the guest additions installer also checks for incorrect versions of the following files, and fails if they are found:

{{{
C:\Windows\system32\dllcache\d3d9.dll
C:\Windows\SysWOW64\dllcache\d3d8.dll
C:\Windows\system32\msd3d9.dll
}}}

I believe the first two files can simply be deleted as they are merely cached copies. The third, msd3d9.dll, was not present on the Windows media I was using, and I suspect it can be deleted as well. 

The documentation should be updated to include instructions about deleting these files manually. Alternately, the installer could delete these files itself.",Ryan Steele
13323,Stop pre-populating a DHCP server on fresh installs?,all,all,VirtualBox 4.3.14,2014-08-26T21:30:41Z,2014-08-26T21:30:41Z,"Hello there good VBoxers! :)

Vagrant core maintainer here. Working on an issue that comes up pretty regularly for folks in Vagrant-land:

https://github.com/mitchellh/vagrant/issues/3083

A fresh install of VirtualBox adds a default dhcpserver into its config.

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/xml/Settings.cpp?rev=52312#L1520

This dhcpserver ends up messing up Vagrant's interface <-> dhcpserver accounting and causes any first-time user with a DHCP-using interface in their Vagrantfile to get a cryptic error message.

We've considered writing code to detect and remove this default config, but it seems the simplest solution would just be to have VirtualBox avoid the default config and leave dhcpservers blank for fresh installs. Since there's no vboxnet0 by default it seems like this is less surprising behavior than having a dhcpserver that references a nonexistent interface in its name.

Looking forward to your thoughts - thanks for your time!

Paul / phinze",phinze
8332,Video controller VirtualBox guest additions 4.0.2 don't work with windows 2003 /3GB switch enable,Mac OS X,Windows,VirtualBox 4.0.2,2014-09-03T14:41:26Z,2014-09-03T14:41:26Z,"Windows 2003 SP2 32bits work fine with VirtualBox guest additions, but when enable /3GB switch video only supports lowest color profile (4 bits) and 640x480 resolution.

Unistall VirtualBox additions and video works again with /3GB switch enable",Sistemas
13351,names of saved virtual machine's cannot be changed,other,other,VirtualBox 4.3.14,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
13303,"Allow to rename or add a comment to the ""Current State"" ""snapshot""",all,all,VirtualBox 4.3.14,2014-09-10T14:03:07Z,2014-09-10T14:03:07Z,"Atm, it is possible to add a name and description for a snapshot. This is not yet possible for the ""Current State"".

I often work with a VM, install software for testing purposes and then forget about it when other things need attention. Two weeks later I will be wondering what the purpose or last state is.

It would be very helpful if I could add a description and/or name, so instead of ""Current State"" the title would be ""Current State (testing Gitlab)"".

I could easily change the title or update it. With snapshots, I would have to create multiple to achieve this.
",larsen0815
13409,VirtualBox does not allow releasing media when a snapshot references it,all,all,VirtualBox 4.3.16,2014-09-16T15:20:02Z,2014-09-16T15:20:02Z,"I have created a snapshot of a VM a while ago while it had the guest additions attached to it. Now I cannot get the old ISO virtual media removed. It should be possible for snapshots only reference certain VM settings and ""release"" others (such as unneeded virtual media).
",rbu
13416,Add option to allow VM to swap,Linux,Linux,VirtualBox 4.3.16,2014-09-18T09:08:41Z,2014-09-18T09:08:41Z,"Test setup is the following:

 * Host machine: Linux, 16GB RAM, 16GB swap.
 * Guest 1: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 2: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 3: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 4: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk

Steps to reproduce:
1. Start all 4 VMs.
2. Start growing ramdisk.

When host free RAM is close to zero - VirtualBox will abort one of the VMs. Swap usage on host is still very low.

Please add the option to allow VM to swap, so all of those 4 VMs will be able to work together, even if slower (swap based on SSD disk makes it not so bad).",indifferent
13408,VirtualBox does not warn that Extension Pack is out of date,all,all,VirtualBox 4.3.16,2014-09-18T12:37:46Z,2014-09-18T12:37:46Z,"VirtualBox is upgraded by my system's package management, while the extension pack needs to be downloaded manually. While that makes perfect sense, VirtualBox should really check that versions for these packages are the same if it needs this constraint to work flawlessly.

I only noticed I had an outdated extension pack since I was getting random machine aborts and found several forum entries with this solution.
",rbu
13458,Prevent VM paging on host and zero memory on power off,all,all,VirtualBox 4.3.16,2014-10-01T21:32:24Z,2014-10-01T21:32:24Z,"I run some VMs that I use for anonymity. I would like to make sure that nothing from these VMs appears on disk and I don't know if VirtualBox does that or has an option for that. I asked in the [https://forums.virtualbox.org/viewtopic.php?f=1&t=63606 forum] two weeks ago but did not receive a reply.

Currently I have the VMs on a portable USB drive. In my Windows 7 host I copy them to a RAM disk that does not page out (awealloc). I cannot run them from the USB drive directly as it's too slow. I have to be sure not to hibernate or sleep during this time because that would write the physical RAM to the hard drive. When I am done I wipe the drive.

I have some requests that could make my life easier and possibly anyone else who's doing the same thing.

I would like an option to zero memory on the host that was allocated by VirtualBox for the guest, after the guest is powered off or suspended. This could be done using ZeroMemory in Windows, for example.

I would like an option to prevent VM paging. In VMWare Workstation, which I am transitioning from, there is a separate level of paging. There's the level VMWare does itself and the level done by the OS (Windows in my case). Does VirtualBox have its own paging routine? In any case an option to prevent all paging would be helpful. 

In Windows it's likely that fully preventing paging out won't be possible without administrator privileges, because the only way to make sure allocated memory absolutely stays in RAM is by passing a special flag that that can only be done by a process that has special permissions. There are very good reasons for this, as if any application could allocate all RAM etc.

Also, related to the no paging suggestion, an option to prevent host sleep/hibernate while a VM is running. Thanks
",quiettime
13468,Typo in FR and LT critical error titles,all,all,VirtualBox 4.3.16,2014-10-03T13:40:52Z,2014-10-03T13:40:52Z,"There is a typo in VirtualBox 4.3.16 in the critical error titles in the FR and LT translation files.

I attached a patch fixing the typo. It is released under MIT license [https://www.virtualbox.org/wiki/MIT%20license].

It replaces: ""Virt'''i'''alBox - Erreur Critique"" by ""Virt'''u'''alBox - Erreur Critique"".
Same for the LT translation file.

Hope it helps somehow. If I did anything wrong, please let me know.",depierre
13433,For pyTivo with Python 2.7.8 the network traffic is being modified somehow on the Host,Windows,Windows,VirtualBox 4.3.16,2014-10-11T19:01:30Z,2014-10-11T19:01:30Z,"I've been using pyTivo and VirtualBox on the same host for a long time. It worked fine until I upgraded from 4.3.12 to 4.3.16. There were no errors produced, but my TiVo could not access pyTivo. I downgraded back to 4.3.12 and pyTivo started working again. Not really sure what log files I could produce to demonstrate the problem. I do not see any errors in any of the Windows log files and pyTivo shows no problems. I can only surmise that it is some sort of networking issue. However I can still access the web address for the program, http://pytivohost:9032, from another computer. Only my TiVo cannot access it.

I'm running Windows 7 Home Premium 64-bit with 16GB of RAM. Not particularly relevant, but my guests are also Windows 7 64-bit. The problem exists whether any guests are running or not.",Steven Wilson
13443,Tooltips in VBox window (not in the guest) make it crash.,Windows,all,VirtualBox 4.3.16,2014-10-13T20:56:06Z,2014-10-13T20:56:06Z,"Hi there,

This is the second time I'm encountering problems / crashes with VBox.

First time was with... 4.3.14 ! Now this is with 4.3.16...

Bugs encountered in 4.3.14 have been solved so I could update from 4.3.12, but this time, I'm encountering a new one (not blocking but disturbing).

VM started, in the VBox window or on the Mini Toolbar (depending on if I'm in fullscreen or not), I just can't make tooltips appear : when I put the cursor on a button, after the tooltip delay (1s), the guest windows crashes (and make it ""Aborted"" in the VMs list). I'm getting a 0x0000000 crash with ""memory can't be written"" (see attached files)

This happens on all my VMs (Linux / Windows guests)

Thanks for your help",marebul
13507,Overwrite the MAC address of other virtual miniport adapter after wake up from sleep,Windows,all,VirtualBox 4.3.16,2014-10-14T07:29:28Z,2014-10-14T07:29:28Z,"I have installed VirtualBox and an IPsec client SW on Windows7 host system. The client uses its own virtual miniport adapter. On this adapter is enabled the ""VirtualBox Bridged Networking Driver"" service.

The MAC address of client adapter:
 
before going sleep: 02:00:00:00:01:00 
after wake up:      08:00:27:00:70:1D

VirtualBox does overwrite the MAC address of foreign adapters!",Beat O
13509,Mouse does not work in full screen mode (HOST+F),Linux,Windows,VirtualBox 4.3.18,2014-10-14T14:06:13Z,2014-10-14T14:06:13Z,"When going to full screen mode (HOST+F) on Linux, using Windows, the mouse is unusable (mouse moves around, but you cannot click on anything... keyboard still works).  When leaving full screen mode (HOST+F) part of the Linux UI is covered by something left over by Virtual Box (force closing Virtual box seems to be the only way to get Linux Desktop usable again).

For more on this, view the forum message:
https://forums.virtualbox.org/viewtopic.php?f=2&t=63740&p=301543#p301543

My System
Host: Ubuntu 14.04 64bit
Guest: Windows 8.1 64bit",darthjdc
13417,Shortcut doesn't start VM window in the foreground,Windows,Windows,VirtualBox 4.3.16,2014-10-14T19:38:21Z,2014-10-14T19:38:21Z,"I'm running Windows XP SP3 as guest OS in a Windows 7 Ultimate 64-bit host. I've created a shortcut to the VM using the feature in VirtualBox Manager.

When starting the VM using the shortcut, the VM window is not brought to the foreground. Although it will appear on top of the desktop (if the shortcut is on the desktop), it will not have focus until you click in it or switch to it using Alt-Tab.

However, the VM window is brought to the foreground when started from VirtualBox Manager.

This seems to be a side effect of the recent Windows hardening changes, but I'm not sure.",bogdan
13513,vBox USB redirection not working for remotefx redirected USB devices,Windows,all,VirtualBox 4.3.18,2014-10-14T22:35:19Z,2014-10-14T22:35:19Z,"Environment:  VirtualBox on Windows 7 x64 (The Windows Host is actually a Guest on a Hyper-V, Server 2012 R2)

The Windows 7 is connected via Remote Desktop while being attached with some USB devices via RemoteFx USB redirection. VirtualBox is unable to detect these USBs, thus the Nested guests are not able to use USB attached to their Host. It is possible that VirtualBox could support such ""uncommon"" configuration? 

Blow shows a snapshot (devicemanager.jpg) from the ""Device Manager"" to illustrate the hardware topology while RemoteFx USB redirection is in effect.",ganboing
8057,First mouse click in virtual screen interpreted as drag,Mac OS X,Linux,VirtualBox 4.0.0,2014-10-16T13:57:02Z,2014-10-16T13:57:02Z,"With an OSX host and Linux (Fedora 14) guest with guest additions installed, a mouse click into the guest that also transfers focus to the running VirtualBox host window causes an undesired drag from the previous mouse position within the guest (before host focus moved).
This can have a number of undesirable effects on the guest depending on what exactly is on screen at the time.

Steps to reproduce:

1. Install Fedora 14 and guest additions on an OSX host, and run in single-window mode with mouse integration enabled

2. With a clean F14 desktop (no windows open), focus another host (OSX) window

3. Left-click and hold at any position on the F14 desktop. A selection rectangle should be visible from the last position of the mouse within the guest before host focus was lost (the bug occurs even without holding, but the desktop selection rectangle shows what is happening clearly)

Expected behaviour: The click (or drag) should be experienced by the guest as starting from the position of the click into the guest desktop, not the position of the mouse prior to loss of host focus
",Matthew Francis
13523,After snapshot VM won't start.,Windows,Windows,VirtualBox 4.3.16,2014-10-17T15:53:31Z,2014-10-17T15:53:31Z,"I made a snapshot of the virtual machine it would not start anymore the result I get is:
No error info:

Result Code: 
E_FAIL (0x80004005)
Component: 
ProgressProxy
Interface: 
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
",ditproz
13275,VBoxManage does not set hostonly adapter name,Linux,Linux,VirtualBox 4.3.14,2014-10-18T09:07:02Z,2014-10-18T09:07:02Z,"I've got a script that creates VM's for me and one of the lines is this one:
VBoxManage modifyvm ""$VM"" --nic2 hostonly --hostonlyadapter1 'vboxnet0'

I can see the adapter in the network section in the GUI, however the name is blank. To populate the name I need to use the GUI and enter Settings, Network, applicable adapter and press Ok. I.e. I do not need to change anything, just press Ok for the hostonly adapter to have the name set.",Onkelringnes
13531,"VBoxManage ""c:\"" argument handling",Windows,all,VirtualBox 4.3.18,2014-10-20T14:04:36Z,2014-10-20T14:04:36Z,"on the Microsoft Windows host I run 'cmd' and enter:[[BR]]
cd %programfiles%[[BR]]
cd Oracle[[BR]]
cd VirtualBox[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
[[BR]]
The quotes are straight. In[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
this is displayed as:[[BR]]
c:\[[BR]]
in the textbox. There is no icon to the left side of the text.[[BR]]
[[BR]]
[[BR]]
In the file[[BR]]
%userprofile%\.VirtualBox\VirtualBox.xml[[BR]]
it is stored as:[[BR]]
<SystemProperties defaultMachineFolder=""c:&quot;"" ...[[BR]]
[[BR]]
[[BR]]
[[BR]]
This will lead to:[[BR]]
a) wrong folders being used.[[BR]]
New virtual machines created with VirtualBox.exe will be stored in[[BR]]
""%userprofile%\%VBOXNAME%\""[[BR]]
instead of[[BR]]
""c:\%VBOXNAME%\""[[BR]]
[[BR]]
The snapshot folder of the virtual machine is wrong as well.[[BR]]
[[BR]]
[[BR]]
b) errors if you programmatically create a virtual machine.[[BR]]
If you set the machinefolder:[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
The VM creation/registration command :[[BR]]
VBoxManage createvm --name ""%VBOXNAME%"" --ostype Windows7 --register[[BR]]
[[BR]]
will fail with the error message:[[BR]]
VBoxManage.exe: error: Invalid machine settings file name 'C:\Users\user\""\VB-USER\VB-USER.vbox' (VERR_INVALID_NAME)[[BR]]
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine, callee IUnknown[[BR]]
VBoxManage.exe: error: Context: ""CreateMachine(bstrSettingsFile.raw(), bstrName.raw(), ComSafeArrayAsInParam(groups), bstrOsTypeId.raw(), createFlags.raw(), machine.asOutParam())"" at line 275 of file VBoxManageMisc.cpp[[BR]]
[[BR]]
[[BR]]
Note: the problem applies to the following parameters as well:[[BR]]
VBoxManage createvm --basefolder[[BR]]
VBoxManage modifyvm --snapshotfolder[[BR]]
[[BR]]
[[BR]]
For example, if you run[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
and[[BR]]
VBoxManage createvm --basefolder ""c:\""[[BR]]
The settings file will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%.vbox[[BR]]
The Snapshot folder will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%\Snapshots[[BR]]
[[BR]]
I leave out the example of the snapshotfolder.[[BR]]
[[BR]]
[[BR]]
The workaround I found is instead of[[BR]]
""c:\""[[BR]]
use[[BR]]
{{{
""c:\\""
}}}
OR[[BR]]
{{{
c:\
}}}
as argument to machinefolder/basefolder/snapshotfolder parameter.[[BR]]
[[BR]]
In ""%userprofile%\.VirtualBox\VirtualBox.xml""[[BR]]
{{{
""c:\\""
}}}
is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
c:\ is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
Either workaround will display a folder icon in[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
Note:[[BR]]
on Fedora 20 x86_64 you can use ""/"" as a machine folder without problem.[[BR]]
I had to start VirtualBox with root-permissions to work with this, though.[[BR]]",Sobek
13528,Windows 10 Tech preview - Reboot at Guest Additions installation with 3D disabled,Windows,Windows,VirtualBox 4.3.18,2014-10-20T16:51:39Z,2014-10-20T16:51:39Z,"Instead of showing a specific error, the Virtual machine crash/reboot if  I try to install guest addition 4.3.18.r96516 .  I just activated 2D+3D graphic options of the vm and now the installation complete successfully

",FrankBT
13539,Can't Resize guest to span monitors,Windows,all,VirtualBox 4.3.18,2014-10-21T16:55:35Z,2014-10-21T16:55:35Z,"Running Windows 7 amd64 
Previously in version 4.3.12 and earlier, I could move a guest so it spanned monitors I have 4 of them. And the guest would resize the desktop.

Now since 4.3.14 (or) 4.3.16.. I can move a windowed guest so it crosses multiple monitors. But when I try to resize it. It snaps to one monitor window and fits itself inside the monitor still in windowed mode.

Since my monitors are pretty low res 1440x900 being able to expand my guests makes it much more useful.

I see this using Ubuntu 14.4 as a guest as well as Win XP as a guest.

I did upgrade everything to 4.3.18 and added the additions to the host and the guests.

",Remowylliams
13440,can't share folders after yum update,Windows,Linux,VirtualBox 4.3.16,2014-10-22T16:51:21Z,2014-10-22T16:51:21Z,"Running windows 7 host w/fedora 20 guest.  Setup shared folders and they worked fine for a long time, then they stopped working recently.  When trying to mount the folders, get the error ""/sbin/mount.vboxsf: mounting failed with the error: No such device""  Tried all online suggestions and no luck.  

Eventually narrowed it down to working with fresh Fedora 20 install but the error occurs after a ""yum update"".  

So if I have a VM that's been updated and boot from ""Fedora with Linux 3.11.10-301.fc20.x86_64"", it works fine.  But if booting with the latest, ""Fedora 3.16.3-200.fc20.x86_64) 20 (Heisenbug)"" the shared folders don't work",virtualsomething
13556,Unable to get out of scaled mode in Mac OS X,other,other,VirtualBox 4.3.18,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
11231,Recursive copyto does not create folders and fall if it not exists on destination VM,Windows,Windows,VirtualBox 4.2.4,2014-10-27T18:54:22Z,2014-10-27T18:54:22Z,"I want to recursively copy files to a VM. But when copying occurs directory, an error occurs.
In version 4.1.18 ""--recursive"" worked. But there were unexpected interruption when transferring files.

{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" guestcontrol ""VM"" copyto ""c:\\AutoTest\\"" ""c:\\Test\\"" --username ""Administrator"" --password ""***"" --verbose --recursive

Copying from host to guest ...
Directory ""c:\\Test\"" already exists
Source: C:\\AutoTest\
Processing host directory: C:\\AutoTest
File: Exchange.exe
Directory ""c:\\Test\"" already exists
Copying ""C:\\AutoTest/Exchange.exe"" to ""c:\\Test\Exchange.exe"" ...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
File: ExchangeConfiguration.exe
Copying ""C:\\AutoTest/ExchangeConfiguration.exe"" to ""c:\\Test\ExchangeConfiguration.exe"" ...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Directory: icons
Processing host directory: C:\\AutoTest/icons
File: about.png
VBoxManage.exe: error: Unable to retrieve requested information.
VBoxManage.exe: error: Error processing ""C:\\AutoTest"", rc=VERR_GENERAL_FAILURE
}}}

{{{
01:07:04.784606 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={57eb82a8-822b-42c1-9d1c-5c54bc3d3250} aComponent={GuestSession} aText={Unable to retrieve requested information}, preserve=false
}}}",angelx
13561,Window Lock on regular guests,all,all,VirtualBox 4.3.18,2014-10-28T13:53:37Z,2014-10-28T13:53:37Z,"When I have a host with running guests launched in regular windows (not headless), a spurious mouse click on the Close box without thinking can kill a ""office-mission-critical"" guest (like our SBS domain controller) - embarrassing. Others who have access to that host might also not take good care with the running guests and pause or kill them. Sometimes guests need to run with a logged in user, and the guest needs to have the desktop showing so the status of the guest can be seen, but having folks click around in the guest might not be desired.

It would be useful to have a lockdown function on the guest window (active in windowed mode, I'd think, not full-screen or seamless) that would not allow any interaction with the window menus or the Close box (minimize and restore/maximize might be OK to leave unlocked) and no interaction in the guest desktop itself, until the lock is removed. It may also be possible to block Vboxmanage activity to such a locked guest, too, and have a Vboxmanage command to unlock the guest so other Vboxmanage commands could be run.

Summarizing:
Ability to place a lock on Virtualbox commands and input for a guest running in a regular window, not full-screen or seamless.
When the guest window is locked: 
  - the Virtualbox menus are unusable
  - the Close Window box is unusable
  - the minimize and restore window buttons are optionally still usable
  - the guest desktop receives no mouse or keyboard input
  - the guest desktop is still visible (perhaps an optional overlay showing the guest is locked, if desired)
  - option to block Vboxmanage commands, including or excluding the VboxManage unlock command, if desired
  - option to block Virtualbox RDP if the guest is locked
  - a new button or menu to unlock the guest window with a password
  - the guest is still completely active and running behind the lock

Please consider adding these to Virtualbox:
  - the locking function, with the optional settings in the GUI
  - a new Vboxmanage command to lock & unlock the guest, and set the optional settings
  - a Lock Status icon in the bar at the bottom of the guest window.",scottgus1bug
13568,"mount vboxsf won't accept option ""user""",Linux,Linux,VirtualBox 4.3.18,2014-11-02T20:32:51Z,2014-11-02T20:32:51Z,"Even though the vbox shared folders can be mounted through mount(8) and a usual /etc/fstab entry can be created, some options accepted by mount won't work for vboxsf, e.g. ""user"" and ""group"".

{{{
juanlu@minted ~ $ tail /etc/fstab
# mint shared folder
mint /media/sf_mint vboxsf defaults,user,uid=1000,gid=999 0 0
juanlu@minted ~ $ mount mint
Only root can mount shared folders from the host.
juanlu@minted ~ $ sudo !!
sudo mount mint
unknown mount option `user'
valid options:
  rw         mount read write (default)
  ro         mount read only
  uid       =<arg> default file owner user id
  gid       =<arg> default file owner group id
  ttl       =<arg> time to live for dentry
  iocharset =<arg> i/o charset (default utf8)
  convertcp =<arg> convert share name from given charset to utf8
  dmode     =<arg> mode of all directories
  fmode     =<arg> mode of all regular files
  umask     =<arg> umask of directories and regular files
  dmask     =<arg> umask of directories
  fmask     =<arg> umask of regular files
}}}

This might be just a non-implemented feature in mount.vboxsf.c. If it's not, then probably a clarification is needed in the user manual that not all mount(8) options are allowed for vboxsf, and in that case it would be nice to have a rationale of why is that.
 ",juanlu001
13571,64bit guest on 64bit Windows 8.1 running bootcamp on a macbook air,Windows,Windows,VirtualBox 4.3.18,2014-11-03T14:43:00Z,2014-11-03T14:43:00Z,"I have just installed Virtual Box 4.3.18r96516, on a Macbook Air running Windows 8.1 in bootcamp. Right after the installation completed, I installed Windows Server 2012R2 64bit on a new virtual machine - this worked perfectly and I also installed an SQL server 2012 afterwards. Now a few hours later after sleeping the computer I get this error: ""VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."". I tried rebooting into OS X and back again, but that didn't work either (same error).
In task manager->performance it says Virtualization Enabled, and from a bit of research I can gather that virtualization should be enabled as default on all macs.",Skovby
13516,VBoxManage stucks on long operations,Linux,Linux,VirtualBox 4.3.18,2014-11-06T16:27:08Z,2014-11-06T16:27:08Z,"Host OS: openSUSE 13.1 or Fedora 20 or RHEL7
Guest OS: any linux I've tried so far.

Steps to reproduce:

1. Import provided OVA file at least 3 times, avoid spaces in VM name. Provided OVA is simple Fedora-20 install, cleaned from garbage, installed openjdk build dependencies and VBox guest additions, nothing special.

2. Change shared folder path to existing writable folder, but leave ""shared"" as name of share.

3. Install mercurial, run following command:
{{{ hg clone 'http://hg.openjdk.java.net/jdk8u/jdk8u/' && cd 'jdk8u' && bash get_source.sh }}}

4. Download jdk-7u67-linux-i586.tar.gz from http://java.sun.com

5. Start all imported VMs, does not matter headless or not.

6. Open number of terminals and run following command in each one of them, change path to jdk8u source, path to jdk-7u67 and name of VM:
{{{
while true; do bash vm-build.sh \
--with-major=8 \
--with-src=/home/user/src/jdk8u \
--with-tag=jdk8u20-b26 \
--with-boot-jdk=/home/user/jdk-7u67-linux-i586.tar.gz \
--with-vm=""Fedora-20-i586-test1"" ; done
}}}
7. Watch the output from time to time, it usually stucks during make pretty soon on at least 1 of the running VMs, usually during first or second iteration.


OVA file and 2 scripts:
https://drive.google.com/folderview?id=0B5Kp-cB1sXJrRDd6RlRwOGxLTTg&usp=sharing",indifferent
13599,Windows 7 guest renders Linux host unresponsive; uncompleted fence warnings,other,other,VirtualBox 4.3.18,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)
13601,multiple keyboard related issues,all,other,VirtualBox 4.3.18,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
13598,Error al iniciar máquina,Windows,Windows,VirtualBox 4.3.18,2014-11-10T14:16:25Z,2014-11-10T14:16:25Z,"Fallo al abrir una sesión para la máquina virtual PC_WindowsXPSP3.

The virtual machine 'PC_WindowsXPSP3' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'N:\EquiposVM\PC_WindowsXPSP3\Logs\VBoxStartup.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: Machine
Interfaz: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}",seterymco
13613,Update vboxadd and vboxadd-service startup scripts for LFS 7.6,Linux,Linux,VirtualBox 4.3.18,2014-11-13T06:29:27Z,2014-11-13T06:29:27Z,"Since /etc/rc.d/init.d/functions is removed in LFS 7.6, the existing vboxadd and vboxadd-service startup scripts will not work.
That means those scripts have to be updated.",hykwok
13557,Virtualbox 4.3.18 disable logging,Windows,Linux,VirtualBox 4.3.18,2014-11-14T11:41:47Z,2014-11-14T11:41:47Z,"I have set system user variables:
{{{
VBOX_RELEASE_LOG_DEST=nofile
VBOXSVC_RELEASE_LOG_DEST=nofile
VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile
}}}

But one file still appears. ""VBoxStartup.log"" under `\VirtualBox VMs\(Machine name)\Logs`. How can I disable all log files?",karlsson
13611,Cannot get rid of 2nd monitor window,Windows,Windows,VirtualBox 4.3.18,2014-11-14T13:31:57Z,2014-11-14T13:31:57Z,"Never set VB to use 2 monitors for a VM, but somehow after a Windows update occurred in the VM, guessing this was the point at which it first appeared. I have 2 VB displays coming up for a VM.  I have tried to set VB to use only 1 display, however, the Win OS still comes up on the 2nd display thus never allowing me to sign in to the OS.  I have also tried changing the monitor under windows settings to show the desktop on the primary display 1, vs the second but the OS will not allow me to make the change. I did not initiated the change on the OS or through VB and cannot get ride of it.  Also, VB shows the primary display as being corrupted in the preview window.

Please see attached screen shots.  Need to get the VM back and Win OS to using only 1 display.

Thank you
Art",ArtZ
13299,Clipboard stops working after few hours,Mac OS X,Windows,VirtualBox 4.3.14,2014-11-19T12:10:44Z,2014-11-19T12:10:44Z,"Hi guys,
After a few hours the Windows 7 guest  stops copying content to the Mac host - I can copy from Mac to Windows but not on the opposite way - I have to kill the VBoxTray.exe and open it again to force it to work.
I'm using the last version of VIrtualBox (4.3.14 r95030) and the guest Windows (Win7 SP1) is using the last version of the Guest Addition software and the host is a OS X 10.9.4.

",MaaT
13625,Can't start virtualBox,Windows,Linux,VirtualBox 4.2.18,2014-11-20T16:25:38Z,2014-11-20T16:25:38Z,"Échec de l'ouverture de session pour la machine virtuelle Linux Mint 17.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Code d'erreur : E_FAIL (0x80004005)
Composant : Console
Interface : IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

",EricG
13629,VM SUP startup log creation,Windows,all,VirtualBox 4.3.18,2014-11-20T16:30:45Z,2014-11-20T16:30:45Z,"VirtualBox creates VM shortcuts without adding the --sup-startup-log command line parameter. A VM receives the --sup-startup-log parameter only when it is started from the VirtualBox Manager. Most users will not be aware of this and they will provide whatever log resides in the VM folder. Maybe it should be better to use a per VM property, that defaults to enabled. An example of such a situation can be found [[https://www.virtualbox.org/ticket/13295#comment:20|here]].",Mihai Hanor
13633,Unable to delete snapshot - Hard disk 'Disk location' has more than one child hard disk (3),Windows,Windows,VirtualBox 4.3.20,2014-11-21T20:45:49Z,2014-11-21T20:45:49Z,"Hi,

I am trying to delete snapshot on VM but getting error message - Hard disk 'Disk location' has more than one child hard disk (3)

VM Version - 4.3.20 r96996
OS - Windows 7
OS on VM- windows server2003

Details about the error:
Failed to delete the snapshot Snapshot 1 of the virtual machine XXXXXXXXXXXXX.

Hard disk 'H:\infor.vdi' has more than one child hard disk (3).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Please take a look.
",Mahi
13637,Second screen not working with 4.3.20 in Yosemite,Mac OS X,Windows,VirtualBox 4.3.20,2014-11-22T19:31:01Z,2014-11-22T19:31:01Z,"The second screen is black. We use dual monitors and they have worked fine for years. Even with 4.3.18 it was fine. Now, I extend to the second screen in Windows and says it did but it's black. The mouse moves over there. but nothing actually works. 
The Mac side still seems fine. I thought maybe it was just that computer so I tried a second one and it's the same way.

I'm running Yosemeite 10.10.1 and Virtualbox 4.3.20 with a Windows XP SP3 Guest. The computer is a 27"" iMac with i7 and 16GB ram the second screen is an IBM 19"" lcd through a thunderbolt port.
",BryceSteiner
13341,Chipset and problems,Windows,Linux,VirtualBox 4.3.14,2014-11-24T12:30:55Z,2014-11-24T12:30:55Z,"Host  - Windows 2003 Std (32 bit)
Guest - Oracle Linux 6.5 (64 bit)

VirtualBox-4.3.14-95030-Win and VirtualBox-4.3.15-95713

If Chipset set to '''PIIX3''':[[br]]

The network is working properly.

# cat /proc/cpuinfo 
> processor	: 0[[br]]
> vendor_id	: GenuineIntel[[br]]
> cpu family	: 6[[br]]
> model		: 23[[br]]
> model name	: Intel(R) Xeon(R) CPU L5420  @ 2.50GHz[[br]]
> stepping	: 6[[br]]
> microcode	: 0x60b[[br]]
>> cpu MHz	: 0.000[[br]]
> cache size	: 6144 KB[[br]]
> physical id	: 0[[br]]
> siblings	: 4[[br]]
> core id		: 0[[br]]
> cpu cores	: 4[[br]]
> apicid		: 0[[br]]
> initial apicid	: 0[[br]]
> fpu		: yes[[br]]
> fpu_exception	: yes[[br]]
> cpuid level	: 5[[br]]
> wp		: yes[[br]]
> flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl pni ssse3 lahf_lm[[br]]
> bogomips	: 4571.13[[br]]
> clflush size	: 64[[br]]
> cache_alignment	: 64[[br]]
> address sizes	: 38 bits physical, 48 bits virtual[[br]]
> power management:[[br]]

[[br]]
[[br]]
If Chipset set to '''ICH9''':[[br]]

# cat /proc/cpuinfo[[br]]
...[[br]]
cpu MHz  : '''2394.048'''[[br]]
...[[br]]

Network interface not work (on guest network interface is up, but there is no network traffic)[[br]]
eth0 - RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)",PepeN
13605,Guest OS Window Disappears after Sleep in MacOS X Yosemite,Mac OS X,Windows,VirtualBox 4.3.18,2014-11-24T17:57:19Z,2014-11-24T17:57:19Z,"The guest OS Window Disappears on Sleep in MacOS X Yosemite.  The sleeping behavior of the new Yosemite release may be causing this problem.

Steps to reproduce:

1) Open a Windows 7 guest OS.
2) Put the window on a second monitor.
3) Close the Macbook lid to cause the MacOS to sleep.
4) Open the Macbook lid.
5) For a moment you will see no windows from any application, then most of them will pop back up.
6) VirtualBox Guest OS Window never reappears.
7) Clicking ""Show"" button in VirtualBox Manager does nothing.

Workaround: Use Remote Desktop to shutdown the OS and restart.

Please note that the length of time in sleep should be a long time.  Merely closing and opening the MacBook lid for a few seconds will probably not trigger this behavior.

Guest OS is Windows 7 with all patches applied to the date of this writing.

Thank you.


",Kriston
13047,Windows guest on linux host is very slow with guest additions,Linux,Windows,VirtualBox 4.3.12,2014-11-25T17:20:26Z,2014-11-25T17:20:26Z,"I have installed VBox on an Archlinux x64 host (Manjaro).
The guest is Win 8.1 Update 1 x64. I use a Core2Duo 9500M having hardware virtualisation enabled.
With guest additions installed the guest becomes very slow oftentimes even unresponsive (often taking several seconds to draw a Window.) In the guest's task manager the CPU load is already 20-50% usage when system is shold be idle. It shows the system interrups process with 10-20% usage.
And just having Skype running without conversation for example, causes overall CPU usage of nearly 100%.

Without installing the guest additions the guest seems to be much faster and system interrups cause < 3% usage.",albion
13432,Frequent BSOD's on Windows guests since 4.3.x,Windows,Windows,VirtualBox 4.3.16,2014-11-25T22:46:21Z,2014-11-25T22:46:21Z,"I've been running everything from 4.3.10 to 4.3.15 and I'm getting constant bluescreens in Windows 7 guests. They are fresh instals as well as older guests. The timing seems to be random, but always within a few minutes. When I can catch the BSOD information, it's regarding ""REFERENCE_BY_POINTER"". The bugcheck is 0x00000018.

At first I thought it was a memory issue, but it occurs even when there is very little memory load on the host.  Host is XP SP3, Intel Core2Duo, 2.93Ghz, 3GB Ram.  I ran a full memory diagnostic which found no problems.

I've done some experimenting, and I can recreate this issue even with barely any memory load on the host. I rolled back to one of the earlier versions that I knew had worked, 4.2.6, and I cannot recreate a single crash, even with an intentionally heavy memory load on the host. I tried several other 4.2.x builds and stopped at 4.2.16. (Newer builds lead to the well-known security issues that also affect the latest 4.3.x branch).  On all of these 4.2.x builds, I just can't get a crash to happen, no matter how hard I try.

Because this didn't happen at all until I upgrade to 4.3.x, I tend to think there's a regression of some kind in 4.3.x.  If anyone is so kind as to take a look at this, I am more than happy to provide additional logs, testing, or information.  

Thanks for reading!",mjdbb1
13304,"Generic GL Renderer used, leading to crash when accessing 3D functionality.",Windows,Linux,VirtualBox 4.3.14,2014-11-26T14:40:11Z,2014-11-26T14:40:11Z,"Host : Windows 8.1pro 64, i7 Haswell with integrated 4600HD Graphics. Latest Intel HD driver 10.18.10.3621.

Guest : Ubuntu 14.04 LTS 64bit, guest additions 4.3.14

Virtual Box 4.3.14r95030 does not recognize Intels OpenGL driver, but falls back to Microsoft generic GDI. 
Linux is booting, when trying to login, crashes with Exception 0xc000094 at 0x2370aeff (unknown software exception). 
Working when disabling 3D support in VBox.

Logfile shows generic MS GDI driver
00:00:30.456612 OpenGL Info: Render SPU: GL_VENDOR:   Microsoft Corporation
00:00:30.456629 OpenGL Info: Render SPU: GL_RENDERER: GDI Generic
00:00:30.456633 OpenGL Info: Render SPU: GL_VERSION:  1.1.0

Using VBox 4.3.12, OpenGL from Intel is being recognized and system is working :
00:00:27.446361 OpenGL Info: Render SPU: GL_VENDOR: Intel
00:00:27.446378 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 4600
00:00:27.446381 OpenGL Info: Render SPU: GL_VERSION: 4.2.0 - Build 10.18.10.3621

(I am not using RDP oder two graphics adapters or similar). ",Bueffel
12605,Slow accesses for XP guest shared folders,all,Windows,VirtualBox 4.2.20,2014-11-27T14:30:31Z,2014-11-27T14:30:31Z,"This problem appears to have a long history (see ""Archaeology"" below).  

'''The symptom:''' XP guest accesses to shared folders at !\\vboxsvr are intermittently stalled, apparently for name resolution.  This happens on both Win7 and CentOS hosts.

'''To replicate:'''
* Fresh install of XP SP3 guest.
* Install Guest Additions
* Add a shared folder - a temp directory with a folder tree (e.g. directories a, b, and c, each with subdirectories 1, 2, and 3) will be convenient.
* In Start -> Run, open a !\\vboxsvr explorer window.  Initial access will stall for 5-10 seconds, after which response is speedy (browse down the folder tree to a/1, b/2, c/3, etc.)
* Doing something else (open a My Computer window) and returning to !\\vboxsvr explorer window will usually result in the next action (e.g. browsing back to directory a/1) being delayed.

'''Affected systems:'''
* VBox 4.1.18 Host: Win 7 64bit Guest: WinXP SP3
* VBox 4.2.20 Host: CentOS 6 64bit Guest: WinXP SP3

'''Unaffected systems:'''
* VBox 4.1.18 Host: Win 7 64bit Guest: Win2K
* VBox 4.2.20 Host: CentOS 6 64bit Guest: Win2K

'''Observations:'''

I have tried each of the following workarounds (both separately and in various combinations).
* Added 255.255.255.255 vboxsvr #PRE to lmhosts; rebooted; '''problem still occurs'''
* Added 127.0.0.1 vboxsvr to hosts; rebooted; '''problem still occurs'''
* Turned off NetBIOS and Windows file sharing (Network Connection -> Properties -> uncheck Client, File Sharing) ; '''problem resolves''' (no stalls, but no Samba access either, of course).
* Turned off all networking (Network Connection -> disable connection) ; '''problem resolves'''
* Disconnected (virtual) network cable via VBox network adapter menu ; '''problem resolves'''
* ipconfig /all shows Node Type is ""Unknown"".  Forced to ""Broadcast"" to match Win2K configuration by setting HLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\NodeType = 1.  '''Problem still occurs'''.
* Verified HLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order lists VBoxSF.  Although VBoxSF is listed first, netbios broadcasts for vboxsvr still go out when lmhosts is not ""patched"".  Broadcasts do not occur if lmhosts is patched, but access stalls still occur.  Note that Win2K apparently caches the name lookup - Win2K will broadcast on initial access attempt, but never again.  I think XP is retrying the name lookups, leading to the periodic delays.
* My local network does not have any name servers (DNS/WINS).

'''Archaeology:'''

Most of the tickets below have been closed as duplicates of ticket 1728, and relate to speed of file transfers.  Arguably *this* ticket is probably a duplicate of 1728.  I figured I'd try a new ticket since it's been 2 years since 1728 showed any activity, and I have a simpler reproduction method - delays can be observed merely navigating the shared folder's directory tree.

http://www.virtualbox.org/ticket/1728

http://www.virtualbox.org/ticket/2256

http://www.virtualbox.org/ticket/5353

http://www.virtualbox.org/ticket/5599

http://www.virtualbox.org/ticket/6146

http://forums.virtualbox.org/viewtopic.php?f=6&t=56768

http://forums.virtualbox.org/viewtopic.php?p=33519
",shuttlefan
9570,MacOSX Menubar appearing in Fullscreen Client,Mac OS X,Linux,VirtualBox 4.1.2,2014-11-27T23:30:38Z,2014-11-27T23:30:38Z,"After the Host Screen is locked with the screensaver or the host goes to sleep, and is subsequently woken up, the MacOSX Menubar for VirtualBox appears in a full screen client, when the cursor moves to the very top of the screen. 

A workaround to keep the menubar from appearing again is to switch the guest out of fullscreen, minimize the guest to the dock, have the guest window come back up and switch back to fullscreen. Then the menubar does not reappear, until the next time the host display is locked. 

Host is MacOS X SnowLeopard, Guest is Ubuntu 11.04.
This also happened with VirtualBox 4.0.x.",srd
13657,Virtual Box 4.3.20 Linux Guest Addition slow a Win64 guest down,Linux,Windows,VirtualBox 4.3.20,2014-11-29T05:19:34Z,2014-11-29T05:19:34Z,"I follow my post about the problems of the graphic driver on Windows guest to advise that finally the new VirtualBox 4.3.20 Linux Guest Addition is buggy. Installed on a Windows 7 64bit guest the system
slow completely down becoming hardly usable.

My configuration:

Laptop i74500U, 8gb + external monitor 1920x1080
Host: Fedora 20
Guest: Windows 7 64bit SP1 and recents updates

At the moment I downgraded to version 4.3.18, and all is magically back running.",par7133
12063,Using Windows 8.1 RTM and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems,Windows,Windows,VirtualBox 4.2.16,2014-11-29T22:11:23Z,2014-11-29T22:11:23Z,"Using Windows 8.1 RTM single language (English, activated with serial provided with PC) and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems. The display becomes dim and HDD spins down (on notebook) but the power led is on and coolers continue to work.
Changing drivers for network cards, video, motherboard, etc doesn't help.
Reinstalling Virtualbox with bridge networking switched off (NAT is on) helps to completely resolve the issue.
Devices used: HP envy 4 touchsmart, Acer iconia tab w700.",Immunologist
13658,"Win7 64bit guest changing color scheme, nothing happens",Linux,Windows,VirtualBox 4.3.18,2014-12-02T10:57:04Z,2014-12-02T10:57:04Z,"My configuration:

Laptop i74500U, 8gb + external monitor 1920x1080
Host: Fedora 20
Guest: Windows 7 64bit SP1 and recents updates",par7133
12369,NAT Network -  DHCP problem: no DNS,Windows,Windows,VirtualBox 4.3.2,2014-12-02T12:33:10Z,2014-12-02T12:33:10Z,"Postby petardo » 17. Nov 2013, 03:20
I am using the ""NAT NETWORK"" Network Adapter.
I have found a DHCP SERVER problem:
IF
- DHCP SERVER is enabled in the file / preferences / network / nat network section,
- and NAT NETWORK is selected as natwork adapter for the guest
==> NO DNS values get forwarded to the guest",petardo
3883,Moving VM window status bar to the top of the window would save space,Linux,other,VirtualBox 2.2.2,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
13664,Guest additions failed after upgrading to 4.3.20 on ubuntu 14.04.1 LTS guest / W7 host,Windows,Linux,VirtualBox 4.3.20,2014-12-05T11:58:22Z,2014-12-05T11:58:22Z,"I upgraded my host to 4.3.20 and also the additions into all my existing and running 4.3.18 VM's.
I didn't see anything special during the upgrade.
I noticed the cut/paste with the host not working on a desktop install.
I got to the boot.log and noticed the additions failed (modprobe vboxguest failed).
I noticed stange characters in voboxadd-install.log at the end of the make statement.
Seem to me something went wrong here !
",micwic
13675,Crash due to windowed screen spanning monitors,Windows,Windows,VirtualBox 4.3.20,2014-12-07T09:48:09Z,2014-12-07T09:48:09Z,"4.3.2 I can stretch the display across multiple monitors with no issues. The display shrinks back to the main display when the system hibernates but can just be resized on wake-up.
All releases after this do not function this way, resulting in BSOD crash.
4.3.20 I can't even stretch the window beyond the main display.

There is a memory.dmp of 350mb created before I rolled back but it may not be complete as I usually just close the VM down and start over.
LMK if a full dump is of any use and I'll reinstall an interim release and replicate the crash.",akaAlso
13678,Networking Still Works After Not Installing,other,other,VirtualBox 4.3.20,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
13679,GUI for guestproperty,all,all,,2014-12-10T13:06:55Z,2014-12-10T13:06:55Z,"Enhancement request: Please put another tab in the Virtualbox GUI, perhaps next to Details and Snapshots, where the guest's ""guestproperty"" settings can be viewed and set. 
The view might be a table, like an Excel spreadsheet, or an expandable tree with group branches and textboxes for the name and value of the property. (certain cells or branches would be read-only if necessary)",scottgus1bug
7779,Dock issue causing log pollution when using Spaces,Mac OS X,other,VirtualBox 3.2.10,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
13455,Windows 8.1 guest - black screen,Windows,Windows,VirtualBox 4.3.16,2014-12-12T16:03:24Z,2014-12-12T16:03:24Z,"On host with Windows 7 64bit and Intel 4600 HD video, guest with  windows 8.1 32bit has black screen after enabling 3d support.

3d Support enabled
last video driver from intel is installed

In log is see that GL_Vendor is recognised as Microsoft GDI Generic",RMarauder
13692,Vboxmanage Guestproperty Get command - 'laconic' output,all,all,VirtualBox 4.3.20,2014-12-15T15:41:39Z,2014-12-15T15:41:39Z,"There are presently two modes for the command-line output of ""Vboxmanage guestproperty get"", the default 


{{{
""Value: ____""
}}}
 

and a --verbose, giving this:


{{{
Value: ______
Timestamp: ###################
Flags: ______
}}}

When using ""Vboxmanage guestproperty get"" in a script, the output of the command has to be put through a filter to act on just the contents of the desired property, without acting on the title preceding the property contents. Especially is this so if one want's the timestamp or the flags, and has to hunt through the verbose output to find the desired data.

It would be useful to have a ""laconic"" output mode, giving just the contents of the requested item itself, with no explanatory name in front of the value, so the command output could be inserted into a variable without any filtering needed later in the script.

Suggested switches:

''--justvalue''  only the value without the preceding ""value: ""

''--justtimestamp''   only the timestamp number without the ""timestamp: ""

''--justflags''    only the flags, without the ""flags: """,scottgus1bug
13574,VirtualBox keeps resizing the guest to 1 screen,Windows,Linux,VirtualBox 4.3.18,2014-12-18T19:39:20Z,2014-12-18T19:39:20Z,"Since updating to VB 4.3.16 and 4.3.18 from 4.3.12 it is impossible to resize the guest operating system to more than 1 screen.

I run Windows 7 and I have 3 screens and I have enabled Auto-Resize Guest Display.

It is possible to drag the bottom right corner of the guest window, but as soon as it is released there are some flickering and the window is resized to be as width as 1 screen.
The guest OS display is internally of the size I resized to, but there is a horizontal scrollbar.

The guest OS is Fedora 19 fully updated.

Guest OS additions are installed.

As soon as I downgradeto 4.3.12 the problem goes away and it is 100% reproducible with 4.3.16 and 4.3.18. I have never tried 4.3.14.

I have a NVIDIA NVS 310 card.

Some other users have reported it here

https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",mariolino
10955,APC UPS Driver and VirtualBox issue,Windows,Linux,VirtualBox 4.2.0,2014-12-19T16:51:46Z,2014-12-19T16:51:46Z,"Hi,

My host is Windows 7 64 bits Ultimate Edition with latest service pack and hotfixes. My processor is an Intel i7 950 4 cores @ 3.07 Ghz. My board is the GigaByte X58A-UD3R. While two days, I had a big problem : VirtualBox GUI was no longer starting. After investigation, I discovered that it was due to my recent installation of PowerChute Personnal Edition v. 3.0.2. It contains a driver named ""APC UPS"". After I disabled it, VirtualBox was working. But I need this driver because Microsoft's default ""HID UPS Battery"" driver makes my computer sleep has soon as it is on the battery. I have review every power options, even made a reset, nothing can explain why Windows goes to sleep immediatly. But when using PowerChute, evering is fine, but VirtualBox is not working. I have tried to reactivate the driver after starting VirtualBox, but it hangs like VirtualBox when the driver is enabled. I hope I give you enough details.",sickle
13703,"VBox generates constant ""psynch_cvwait"" #316 errors on OSX",Mac OS X,all,VirtualBox 4.3.20,2014-12-20T00:34:58Z,2014-12-20T00:34:58Z,"Tonight I noticed that when I have a VM running (Ubuntu, Windows, or TinyCoreLinux),  `errinfo` on OSX (the host machine) returns constantly flowing errors like so:

{{{
$ sudo errinfo -n VBox
            EXEC          SYSCALL  ERR  DESC
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless    psynch_cvwait  316 
    VBoxHeadless __semwait_signal   60  Operation timed out 
...
}}}

And when no VMs are running, having the VirtualBox GUI open returns constant stream of these errors (which go away when I exit it):

{{{
...
         VBoxSVC    psynch_cvwait  316 
         VBoxSVC    psynch_cvwait  316 
         VBoxSVC    psynch_cvwait  316 
...
}}}

I first noticed this when I was profiling an intensive ~8 second task in a VirtualBox VM. I used `dtruss` to trace system calls during the task, and found that about 25% of the time was spent in these `psynch_cvwait` calls, which was output like this (where 13035 is the VBoxHeadless PID):

{{{
sudo dtruss -f -a -p 13035
PID/THRD  RELATIVE  ELAPSD    CPU SYSCALL(args) 		 = return
...
13035/0x41f17:  10017630    1170     45 psynch_cvwait(0x100118610, 0x3D22A0103D22B00, 0x0)     = -1 Err#316
...
}}}

I can't find much info about Err # 316 on OSX. The XNU repo has a definition for it, but no info that I can find about this specific error:

https://github.com/opensource-apple/xnu

OSX Version: 10.10.1 (4-core Macbook Pro -- all 4 cores enabled for the VMs)
VBox Version: 4.3.20r96996
Guest OS's: Windows8, TinyCoreLinux, Ubuntu

Lmk if I can provide any more info! Thanks for your time.
",tzaharia
13707,Unable to delete snapshot with 2 child snapshots,all,Windows,VirtualBox 4.3.20,2014-12-21T04:07:09Z,2014-12-21T04:07:09Z,"When I tried to delete a snapshot I got this error:

Failed to delete the snapshot 1 of the virtual machine Windows XP chs.

Snapshot '1' of the machine 'Windows XP chs' cannot be deleted, because it has 2 child snapshots, which is more than the one snapshot allowed for deletion.

Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
Component: SessionMachine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
",Edward Yang
13710,Error code 5 with install windows 7,Windows,Windows,VirtualBox 4.3.20,2014-12-23T07:54:44Z,2014-12-23T07:54:44Z,"Hi,

When I want install Windows 7 on VM, I have ""code error 5"".

This probleme come from the BIOS (old BIOS make this with Windows 7 CD bootable).
It's possible to update BIOS of VM in Virtual Box? 
Or propose a choice

Best regards",Olivier69
13718,Write same error when using SAS controller with Arch Linux guest,Mac OS X,Linux,VirtualBox 4.3.20,2014-12-27T01:23:00Z,2014-12-27T01:23:00Z,"I'm installing an Arch Linux guest using the 2014.12.01 ISO image. I've taken the defaults for VM provisioning except for changing the default storage controller to SAS. The ISO is able to boot and the /dev/sda disk is able to be successfully partitioned using cgdisk. Creating an ext4 file system is also successful. However, when the new sda1 is mounted, errors begin appearing on the console:
sda1: WRITE SAME failed. Manually zeroing.

I've changed the controller to SATA, and the problem is gone.

I'm not sure if this is a problem with the drivers in Arch, or with the SAS device in VirtualBox. I'm opening a bug with Arch as well, in case its not a vbox problem.",rj45
13721,Machine Shared Folders and Repeatable Serial Numbers (Win),Windows,Linux,VirtualBox 4.3.20,2014-12-28T22:47:15Z,2014-12-28T22:47:15Z,"Ubuntu 14.04.01 LTS With VBox 4.3.20

A windows Guest program (MediaMonkey) makes use of the ""Serial Number"" scheme assigned to drives in windows to build the database of files.  After reboot, the Serial Number reported to the Guest changes, causing issues for the Guest program to link up the mapped drive to it's database representing it.

This seems to be new behaviour when I upgraded to 4.3.20, prior to this the serial numbers would not change.  May I suggest that the serial number reported to the Guest OS be calculated from the host's Path so that it remains constant as long as the host's path configuration is constant?",longj
13723,Gnome 3 window decoration issue on Debian guest with 3D acceleration enabled,Windows,Linux,VirtualBox 4.3.20,2015-01-01T07:13:31Z,2015-01-01T07:13:31Z,"I searched for an already opened ticket: I found
ticket:12320
ticket:12746
ticket:12941
that seem similar, but in my case there is no guest crash, actually just some X server problems.

Host:
{{{
Windows 8.1
16GB RAM
NVIDIA GTX 860M (dedicated GPU)
Intel HD 4600 (integrated GPU)
VirtualBox 4.3.20r96997
}}}
Guest:
{{{
Debian 8 (testing) quite fresh installation
3D acceleration enabled
}}}

Issue:
It looks everything work fine....but after some using of Totem video player, window decoration crashes (see the attached screenshot): for example

1. If I select menu->properties during video playback, its window is not visible because video rectangle remain ""on top"", while the properties window lies correctly above the title bar.
2. If I open and close several video files, suddenly window decoration crashes. Buttons are not drawn (even the date and the clock) and there are white or gray rectangles in their place. If I restart gnome 3 (alt+F2 then ""r""), some buttons are still not clickable, i.e. poweroff button, some other are missing (I suppose it is a gnome 3 behaviour after video capabilities have been switched from 3D to 2D). I have to reboot from a terminal (TTY).

Xorg logs are clean, while virtualbox guest logs show GuestAdditions errors: (full log is attached)
{{{
00:07:49.644926 Guest Additions capability report: (0x5 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:07:50.050200 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
00:07:50.050224 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
00:07:50.050288 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400
00:07:50.050301 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid..
00:08:00.952341 Guest Additions capability report: (0x1 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:08:00.956122 Guest Log: VBoxGuestCommonIOCtl: HGCM_CALL: Invalid handle. u32Client=13
00:08:00.956161 Guest Log: VBoxGuestCommonIOCtl: HGCM_CALL: Invalid handle. u32Client=13
}}}",debianized
13725,[patch] make VNC listen on same port for IPv6 and IPv4,all,all,VirtualBox 4.3.20,2015-01-02T11:25:52Z,2015-01-02T11:25:52Z,"Currently, VirtualBox always assigns port 5900 when listening for VNC connections via IPv6, as opposed to IPv4, where the port to use can be set using the property TCP/Ports.

The attached patch changes this behavior so that TCP/Ports also applies when listening via IPv6, thereby using the same port number for both IPv4 and IPv6.

It should be applied in /usr/ports and will create a file emulators/virtualbox-ose/files/patch-src-VBox-ExtPacks-VNC-VBoxVNC.cpp.

See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193778

-- Martin",wonko1953
13727,can't run a program with Transient Folders with Windows 10 Technical Preview Build 9841,Linux,Windows,VirtualBox 4.3.20,2015-01-03T01:03:45Z,2015-01-03T01:03:45Z,"I am using the modern.IE Windows 10 with Internet Explorer 11 VirtualBox download.

I am using VirtualBox 4.3.20 r96996 on Fedora 20 x86_64.

I updated Windows 10 with the available Windows Updates.

I installed the VirtualBox Guest Additions for 4.3.20.

I changed a few of the settings as they come from Microsoft (modern.IE):

1) Chipset -> ICH9
2) Enable I/O APIC
3) IDE -> ICH6
4) switch the HD to the SATA controller
  a) SATA is set to AHCI
  b) enable Use Host I/O Cache

Once the guest is booted, I go to Devices -> Shared Folders Settings...

I add a Transient Folders that maps to my local (ext4) Linux filesystem. A ""Downloads"" directory in my home directory.

I then ""browse"" to \\VBOXSVR\Downloads in Windows Explorer.

I get the file listing.

I doulbe-click on an installer program for a PDF Viewer.

I get an error:
""ShellExecuteEX failed; code 1.
Incorrect function.""

If I copy the file from \\VBOXSVR\Downloads to a local guest directory, it runs fine.

But I have ran this same installer the same way with all of the other modern.IE VirtualBox images, i.e. running the installer from the \\VBOXSVR\Downloads share works on all the other modern.IE images but Windows 10 w/IE 11.",allenatdecisiv
13731,High CPU load when smooth-scrolling,Windows,Linux,VirtualBox 4.3.20,2015-01-04T02:26:32Z,2015-01-04T02:26:32Z,"I have noticed that when smooth-scrolling in either Firefox or Chrome, either by continuously running the mouse wheel, or by mid-click to activate auto-scroll and then moving the cursor slightly to slowly start scrolling, I get very high CPU load. At usual reading pace I can often get 70-80% CPU, slightly less when I scroll slower. This surprises me, since scrolling really shouldn't be a CPU intensive task! Under the Windows host, smooth scrolling never takes any CPU at all. Also, the Linux guest feels a bit more sluggish when scrolling compared to the Windows host. I am running Compiz, and 3D is generally working well (if using the 3D-box desktop, and it rotates nicely).

It is a bit of a bother, since this significantly reduces battery time: When just browsing the web, I scroll while reading, and this usually loads the CPU high enough to spin up the fan. Obviously, all that heat is a battery drain!

I am using a dual-boot Windows 8.1 and Windows 7 host with an Ubuntu 14.04 LTS guest on an ASUS 550JV laptop (Core I7-4700HQ, 16GB RAM and nVidia GT-750M). I have seen this on Virtualbox 4.3.12 (with guest additions 4.3.14) and on 4.3.20 (with guest additions 4.3.20). Virtualbox has one core and 6GB RAM. 3D in general is working well, as mentioned.",00prometheus
13732,Direct3D on Intel GMA X3000 hangs VM and manager GUI,Windows,Windows,VirtualBox 4.3.20,2015-01-05T03:51:50Z,2015-01-05T03:51:50Z,"Guest: XPSP3 32-bit[[br]]
Host:  XPSP3 32-bit[[br]]
Video core: Intel GMA X3000 (G965 Express Chipset Family)

Easiest way to repro is run DxDiag in guest (obviously install and enable 3D acceleration first). VM and manager GUI hang and have to be killed but host seems unscathed.

VBox log and DxDiag.txt from host attached. The log is possibly truncated by my having to kill the process (or maybe it flushes after each line, I don't know).",hugh2
13736,Function Keys in VirtualBox are inactive,Windows,Windows,VirtualBox 4.3.20,2015-01-05T14:09:20Z,2015-01-05T14:09:20Z,"Hallo
My PC is ASUS ZenBook with OS:Win7 Prof (Host).
I have Installed  WM VirtualBox 4.3.20 with Extension package.
My Guest OS is Win98.
In my Application I need the function keys F1 to F12.
I have try all possible, I also search in the community FAQ but without
success. The proposition I have found there are without success. activate
What I have to do for activating the F1 to F12 ??
Thank You in advance
Anton
",akurka
242,No image with USB 2.0 webcams,other,other,VirtualBox 2.2.2,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
13743,NAT: port forwarding issues / collision,other,other,VirtualBox 4.3.18,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
7736,SATA disks not found after reboot into linux (ICH9 only),Windows,Linux,VirtualBox 3.2.10,2015-01-07T22:26:38Z,2015-01-07T22:26:38Z,"Situation:
 * I have a IDE hdd with a linux installation on it, as well as grub.
 * I have a IDE cdrom with an image of windows XP on it.
 * I have a SATA hdd with windows XP on it, or nothing

I want to boot the linux OS, which will determine if the windows XP partition is available and has booted correctly. If this is the case, a grub-reboot is issued to boot into windows XP once, otherwise the image is restored onto the HDD.
If I reboot from windows XP, the linux OS should do the above again.

On an actual machine, the procedure works without a hitch.

However after a reboot from windows XP to linux (Start | Shut Down... | Restart) the linux suddenly can't find the SATA disks.
dmesg has the following lines:
{{{
[    6.166426] ata1.00: qc timeout (cmd 0xec)
[    6.166426] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.516437] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   16.517619] ata1.00: qc timeout (cmd 0xec)
[   16.517619] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   16.517619] ata1: limiting SATA link speed to 1.5 Gbps
[   16.866406] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   46.866424] ata1.00: qc timeout (cmd 0xec)
[   46.866424] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   47.216399] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   47.566424] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   52.566425] ata2.00: qc timeout (cmd 0xec)
[   52.566425] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   52.916425] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   62.916398] ata2.00: qc timeout (cmd 0xec)
[   62.916398] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   62.916398] ata2: limiting SATA link speed to 1.5 Gbps
[   63.266424] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   93.266437] ata2.00: qc timeout (cmd 0xec)
[   93.266437] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   93.616439] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
}}}
Attached is the full vbox.log and the full dmesg as I have it.",Mike Musterd
13754,Export Appliance Dialog does not export selected machine if machine state is changed,Mac OS X,all,VirtualBox 4.3.14,2015-01-12T11:55:49Z,2015-01-12T11:55:49Z,"This is a behaviour report that might be used to correct the usabillity. 
I ran into the following scenario:

1. I started (accidently) my centos host
2. I open the dialog export appliance
3. I see that i cant export a running machine (its ok). The running machine is disabled in the select box. So far so good. '''I left this export selection dialog open! '''
4. I shutdown the running host
5. The formerly running machine is now selectable. So i select it.
6. I press export. The default export filename is right. Then the strange thing happend. The Appliance export starts to export the machine next to the one i want

Long story made short:
Start a host from a list with at least 2 hosts.
Open the export dialog
Stop the host and select it at the exporter dialog
Export the host. It will export the wrong host


I have 4 host machines (3 x centos, 1 x windows)
",jami
13720,Virtualbox Crashes in r600_dri.so Mesa Graphics Driver When Running Ubuntu Guest With Guest Additions Installed,Linux,Linux,VirtualBox 4.3.20,2015-01-12T22:47:14Z,2015-01-12T22:47:14Z,"On installing guest additions on a Ubuntu 14.10 guest and rebooting, the guest and virtualbox crash immediately _after_ the _login_ screen (i.e. after entering the password and Unity starts setting itself up). Subsequently, every reboot crashes at the same point and only un-installation of the guest additions can work around the problem.

The crash is always reproducible. Debugging details including a coredump, stack trace and register information will be found attached to this bug report.

The system in question is running the 64 bit version of Virtualbox 4.3.20 (4.3.20-96996~Ubuntu~raring) on a 64 bit Ubuntu 14.04 system running kernel 3.8.1.

The system runs the free Radeon drivers. The card is an AMD Radeon Evergreen (REDWOOD) PCI ID: 1002:68c1 (Dell Mobility Radeon HD 5650).

I am using this PPA for the MESA drivers: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers but the crash is reproducible with the stock Ubuntu 14.04 MESA drivers and has been for a while (see the next paragraph).

I have been seeing this problem over the last several (I'd say 3 or 4) iterations of Virtualbox as well as the last 2 iterations of the OS (Currently Ubuntu 14.04 but previously 12.04), and across a wide range of kernels.

Further debugging information (including a Stack Trace e.t.c.) is attached but here are the basics:

- The crash occurs due to Signal 11 in r600_dri.so
- Summary Segv Analysis:
{{{ 
Segfault happened at: 0x7f3ef00ed1bd <_mesa_MultiModeDrawArraysIBM+93>:        
mov    (%r15,%rbx,1),%esi
 PC (0x7f3ef00ed1bd) ok
 source ""(%r15,%rbx,1)"" (0x00000030) not located in a known VMA region (needed r
eadable region)!
 destination ""%esi"" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
}}}
- The kernel has the following traps message in its log after the crash:
{{{
ShCrOpenGL[24186]: segfault at 30 ip 00007ff0902eb1bd sp 00007ff0918afa80 error 4 in r600_dri.so[7ff09016e000+7b8000]
}}}

Exactly the same crash occurs with the most recent Guest Additions ""test build"" (Guest Additions, revision 97191), but with the same (un-updated) version of Virtualbox.

See attached files for further debugging information.",marete
13704,No Window Decorations in Zorin 9 after Guest Additions - VirtualBox 4.3.20,Windows,Linux,VirtualBox 4.3.20,2015-01-13T02:43:15Z,2015-01-13T02:43:15Z,"After Installing Zorin 9 32 bit core (3D Acceleration Enabled) I installed VirtualBox Guest Addtions as follows:

In Termainal ran:

sudo apt-get install build-essential linux-headers-$(uname -r) dkms

Then from VirtualBox Menu selected Devices - Insert Guest Additions CD image... And ran it.
After I rebooted all Window Decorations were missing (Minimize Maximize/Restore and Close buttons) I tried everything in Zorin but found that it happened after I installed Guest Additions from VirtualBox.

The only fix was to install Guest Additions from terminal in Zorin using the following:

sudo apt-get update

sudo apt-get install virtualbox-guest-x11

and choose Y to overwrite

I rebooted and my Window Decorations Were Back.

I think the problem is with 4.3.20 Guest Addtions CD image",FutureAlex
13024,Support for physical multiCPU,all,all,VirtualBox 4.3.10,2015-01-14T09:37:04Z,2015-01-14T09:37:04Z,"Hi.

The summary is somewhat missleading, sorry about that, but i was just not sure how to ""commpress"" it to something meaningfull.

As up to 4.3.10 version, VirtualBox engine only support multiCPU configurations, where guest sees multiple CPU's as '''one''' physical CPU, with more cores and siblings.

For majority of use-cases this is sufficiant to emulate multi-cpu environment. But, it seems that it have more than one performance penalty.

I have HP580 G5 machine, which was running ESXi package, and there was number of guest machines (mostly linuxes). All of them, when displaying cpuinfo, did show CPU's as separate physical packages. In example - this is from guest running on another similar host with VMWare:


{{{
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 46
model name      : Intel(R) Xeon(R) CPU           X7542  @ 2.67GHz
stepping        : 6
cpu MHz         : 2663.778
cache size      : 18432 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf pni ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm ida epb dts
bogomips        : 5327.55
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 46
model name      : Intel(R) Xeon(R) CPU           X7542  @ 2.67GHz
stepping        : 6
cpu MHz         : 2663.778
cache size      : 18432 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf pni ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm ida epb dts
bogomips        : 5327.55
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:
}}}

When i did migrate those to VirtualBox, now CPU's are shown as ""cores"":

{{{
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU           X7350  @ 2.93GHz
stepping	: 11
cpu MHz		: 2904.312
cache size	: 6144 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good pni ssse3 lahf_lm
bogomips	: 5783.55
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU           X7350  @ 2.93GHz
stepping	: 11
cpu MHz		: 2904.312
cache size	: 6144 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good pni ssse3 lahf_lm
bogomips	: 5783.55
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:
}}}

(note how physical id does not change).

It seems, that this is having some performance penalty, as guests seems to be running slower than before. Host is installed using CentOS 6.5, as do guests.

Also, HP580 G5 have 4 CPU's with 2x2 cores. Increasing vCPU (guest CPU count) to anything above 2 causes huge performance degradation, and instability (frequent oopses). On VMWare this was working flawlesly - you can go to VMWare knowelege base, and search for article 2030577.

I did not manage to find anywhere any reference on how to make VirtualBox present CPU's as physical ones, so i do assume that this is something that needs to be done.

I do also assume that this could be connected to other reports about suboptimal performance with more than one CPU. I say connected, because it seems that only affects older host CPU's - running VM's on HP380 G7 (i7), with lagrer number of CPU on guest does not influence performance in a major way.

If needed, i can provide logs from host, and guests.

Regards,

H.

",Hrvoje
13758,Win7-64 install fro SCCM image,Windows,Windows,VirtualBox 4.3.20,2015-01-14T14:35:23Z,2015-01-14T14:35:23Z,"new VM WIn7Ent64. install always fails after loading boot image from SCCM.
pls. see attached log.",Papika
10953,Slow Guest Desktop,Mac OS X,Windows,VirtualBox 4.2.0,2015-01-15T23:04:04Z,2015-01-15T23:04:04Z,"After upgrading to 4.2.0 by first uninstalling 4.1.22 guest tools, rebooting and installing 4.2.0 and rebooting clean, I see very slow desktop. Dragging any guest windows (Win7 x32) are lagging behind mouse. I know this is not a good measurement but on 4.1.x is was much much faster. Also dragging window around leaves dirty lines (from dragged window) on desktop all over. At some point it desktop will get refreshed. I try to get screenshot but whenever I try to get screenshot desktop is refreshed.
When I mean drag window in circle motion mouse stops and window still is in motion following circle.
I did try to uninstall guest tools. Reboot Guest and Host and nothing works.
Host is Mt Lion 10.8.1",oxoocoffee
13765,clonevm faster: make use of --reflink,Linux,all,VirtualBox 4.3.20,2015-01-16T12:43:06Z,2015-01-16T12:43:06Z,"I'm running vbox machines off a btrfs partition with CoW. When combined with bcache (SSD-backed cache) the fragmentation penalty of fragmented images doesn't hurt much - i.e. I get adequate perfomance of 3-8 VMs on my Lenovo T540p notebook. 

When I clone the vm (separate copy), virtualbox does a full copy of the image - taking considerable time (4 hours for 100GB image) and space. I suggest to utilize the ""cp --reflink=auto"" instead. The copy is made instantly (if possible and falls back to traditional copy) and no additional space is taken until there are changed blocks in the image file.  ",rugubara
7067,"VERR_INTERNAL_ERROR: Inexistent host networking interface, named 'vboxnet0'",other,other,VirtualBox 3.2.6,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
13778,Alt+Tab breaks keyboard input,Linux,Windows,VirtualBox 4.3.20,2015-01-22T20:57:46Z,2015-01-22T20:57:46Z,"My computer is a Lenovo thinkpad x230. 
Host OS is Fedora 20. 
Guest OS is 64bit Windows 7 Enterprise SP1. 

I can reproduce this bug in 4.3.20_96996_fedora18-1 from the virtualbox yum repo, and the test build 97569. 

Attached is the latest log from the last time I reproduced the bug, these are also the events I describe in this report. 

1. Start guest VM.
2. Open notepad or any input field to test keyboard
3. Type some words. 
4. Press right Ctrl to release keyboard from guest
5. Press alt+tab to switch host OS program, do not release alt
6. Switch back to guest VM with alt+shift+tab
7. Type some words in notepad

Expected result:
Letters from a-z and numbers from 0-9 typed out on screen. 

Result:
The menus activate randomly in notepad, no words are typed. In other programs like Putty I see strange characters being input, sometimes spaces, sometimes returns, never the expected character. In the Windows desktop random functions might be activated, or nothing will happen at all depending on what keys I press from a-z and 0-9 on the keyboard. 

Workaround:
Press left ctrl+alt once and typing is restored. ",stemid
13779,vobxsf breaks on long paths (> 260) with Windows host,Windows,Linux,VirtualBox 4.3.20,2015-01-22T21:00:44Z,2015-01-22T21:00:44Z,"Linux guest (Ubuntu 14.10), Windows (8.1) host.

When using shared folders, if the path length of a file is greater than 260, the file doesn't appear correctly in the guest. Note that the problem appears to be related to the path length in the host (Windows), rather than the path length in the mounted filesystem in the guest.

Here is an example of the problem:

{{{

$ ls -l
ls: cannot access 22-20131023143021.zip: No such file or directory
ls: cannot access properties.xml: No such file or directory
total 4
?????????? ? ?   ?      ?            ? 22-20131023143021.zip
-rwxr-xr-x 1 abc abc 3819 Jan 20 10:26 content.txt
?????????? ? ?   ?      ?            ? properties.xml

}}}

In the host, the length of the path (in the host fs) of context.txt is 258. It is readable in the guest (Linux). The other two files have a path length > 260 and are not accessible
",__cc__
13787,Incorrect usage of size units,all,all,VirtualBox 4.3.20,2015-01-25T19:06:41Z,2015-01-25T19:06:41Z,"See this screenshot: http://i.imgur.com/Rh8smv7.png

The size of the disk is 197 GiB or 211.5 GB. But VirtualBox reports 197 GB, which isn't correct.",joco
12819,Host fails to read NTFS folder which is mounted to some partition,Windows,Linux,VirtualBox 4.3.8,2015-01-27T08:14:56Z,2015-01-27T08:14:56Z,"Steps to reproduce:
* On Windows host, mount some partition (USB drive in my case) to NTFS folder, (say, to `C:\shared\usb`)
* Create new shared folder, ""shared"" = ""C:\shared"".
* Mount the folder in Linux guest.

Result:
* When listing the directory, ""usb"" is shown as symlink.
* When trying to `cd /mnt/shared/usb` the following error occurs:
{{{
-bash: cd: /mnt/shared/usb: Protocol error
}}}
",dmak
13798,Junctions to host,Windows,Windows,VirtualBox 4.3.20,2015-01-29T09:42:36Z,2015-01-29T09:42:36Z,"Hello

I don't know if it is a bug or a technical restriction.
I tried to make a link (junction) to a folder from win 8.1 (guest) to my windows 7 (host).
My idea was, instead to add a drive to an UNC Path (\\vboxsrv\hostshare), I make a link to this folder.
But when I access to this folder (double click in explorer), folling message appears (see attachment).

What do you this?
Should this work or isn't possible to do this?

Thanks",Michael
11329,SDK - IGuestSession - (conceptual) bug with CopyTo/From(),Windows,Windows,VirtualBox 4.2.4,2015-02-03T17:14:39Z,2015-02-03T17:14:39Z,"There seems to be a (conceptual) bug with the IGuestSession::CopyTo() and CopyFrom(). The internal code is relying on a 30 seconds timeout for the whole copy operation to finish (because it's counting on some vbox_cat internal process spawn within the Guest). Obviously that fixed timeout is not realistic for large files such as 500MB-1GB long. Not to mention that the host file may not be really on the physical host itself, but located somewhere on the network.

I get into the same issue when I'm using the equivalent VBoxManage command.",smihaila
13808,VM window should stay maximized when moving to a screen with a different resolution,Windows,Windows,VirtualBox 4.3.20,2015-02-04T13:51:56Z,2015-02-04T13:51:56Z,"VirtualBox: 4.3.20 r96997

Host: Windows 8.1 Enterprise 64-bit

Guest: Windows 7 Enterprise 64-bit

Problem:  I am running VirtualBox on a laptop with a secondary monitor connected via a display-port to VGA adapter coming out of the laptop and VGA in on the monitor.  The resolution of the laptop is 3200x1800 and the resolution of the secondary monitor is 1680x1050.  When I move the guest machine from the laptop screen to the secondary monitor I expect the VirtualBox window to resize to the new resolution but it does not. All other applications do this.  This is a bit confusing to explain but bear with me here...

Example:
I start Virtualbox and start my guest machine.  These windows are on my laptop screen and maximized, so running at 3200x1800.  I move the guest machine window over to my secondary monitor but the window does not resize.  I believe the window is still running at 3200X1800 instead of resizing to 1680x1050 when moved.  This is causing issues because the guest machine is pretty much unusable as everything is at a very high resolution but running on a monitor that does not have that resolution.  I can adjust the window or the resolution of the guest machine, but nothing changes.  The window still is running at 3200x1800 thus causing the guest machine to appear very tiny.",gregv
13774,"OpenGL, Direct3d screenshot making error",Windows,Windows,VirtualBox 4.3.20,2015-02-05T09:00:05Z,2015-02-05T09:00:05Z,"Like it is listed here:
https://www.virtualbox.org/ticket/10794
and here:
https://www.virtualbox.org/ticket/10800

In both cases the screenshot making is not working in the inteded way, I can see through the active window which have the 3d application in the screenshot.
The 3d content is completely transparent.
Integrated Intel HD video card on a T520 notebook, with only 3D DirectX enabled on the guest. (Win7 Enterprise X64 host, Win7 Ultimate X64 guest) Latest patch on everything: drivers, OS, VBox on both machines.
On guest VBoxWindowsAdditions-amd64.exe was also installed from this: http://download.virtualbox.org/virtualbox/4.3.20/VBoxGuestAdditions_4.3.20.iso

Host 8GB RAM, 2 display

Guest RAM 2048MB, VRAM 256MB, 1 display, I/O APIC enabled, PIIX3, 1 core, VT-x enabled, memory virtualization enabled, 2-way shared clipboard enabled

Please do not mark it obsolete, since it is a live bug in the latest version.
I will gladly give more info if needed.",xzvf
13698,Rotating the host window,all,all,VirtualBox 4.3.20,2015-02-05T09:02:54Z,2015-02-05T09:02:54Z,"It would be great if VirtualBox can rotate the host window.
This is needed because of Android guests.
The guest content can rotate, but the host window does not.

There should by a menu entry to rotate the host window 90°:
Independing of the guest system.",E88
13821,mouse cursor changes to guest even when not capturing mouse,Mac OS X,Windows,VirtualBox 4.3.20,2015-02-10T22:21:11Z,2015-02-10T22:21:11Z,"I've used vboxmanage to set...

VBoxManage setextradata ""win7-32bit"" GUI/MouseCapturePolicy Disabled

I've tried seamless and windowed and though the mouse is not ""captured"" in the window, the mouse cursor still changes to the guest cursor when I click on a guest window.  I've seen it where the cursor did NOT change (it happened once, so I'm not sure if this is as designed or what) but the behavior seems to be inconsistent, and it's now changing again.  I would prefer that it doesn't change because I'm using a ""resized"" (accessibility settings) cursor in my macOS host, which distorts the guest cursor to a grotesque pixelated monstrosity.  I have the extensions installed, and behavior described in the user manual says that the cursor is not supposed to change, but it does anyway. :(",apocalysque
11995,Saving Ubuntu guest in full-screen mode causes guest X session hang when resuming. Windows 8 host.,Windows,Linux,VirtualBox 4.2.16,2015-02-11T23:24:07Z,2015-02-11T23:24:07Z,"Host is Windows 8 64-bit, guest is Ubuntu 13.04 64 bit.

Everything works fine including saving state & restoring when the guest is in a normal window.  But if the guest is saved while in full-screen mode, then when the guest is restored it is unresponsive, cursors do not flash, etc.

However the ""hung"" guest does respond to Host-F1 and switches to a VT where you can log and kill the X server, after which normal operation resumes.

So saving or restoring in full-screen-mode breaks something related to sending events to the guest X server.

HOW TO REPRODUCE:


{{{
Start Ubuntu guest
Go to full screen (Host-F)
Put cursor at bottom of screen to get vbox menu, then
Machine->Close-Save Machine State
}}}


Restart the saved VM.  It hangs.

(to recover: Host-F1, log in as root and kill the X server process)

I'll attach two log files (one from the session which ended with a save while in full-screen mode), the other from the restarted VM with the hung X server.",Jim Avera
13369,Bottom toolbar is displayed incorrectly,Linux,Windows,VirtualBox 4.3.16,2015-02-13T12:39:42Z,2015-02-13T12:39:42Z,"After updating VB to version 4.3.16, bottom toolbar on my guest Windows is displayed incorrectly (see attachement).
Toolbar appear in wrong place (above the Windows toolbar and above my system toolbar). It also exist even when I minimize the VB window.

To trigger the toolbar, I need to place mouse pointer in the edge of the system toolbar what is wrong also.

I'm working on full screen with two monitors. In previous version the toolbar was displayed correctly.

Host system:
Linux mateusz 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux

Guest system:
Windows 7 Professional x64 with all updates",mmaj
13832,VirtualBox 4.3.22 Breaks Physical Network Card Config,Windows,Linux,VirtualBox 4.3.22,2015-02-13T18:11:52Z,2015-02-13T18:11:52Z,"

I'm having the same problem with VirtualBox 4.3.22 for Windows on Windows 7 Pro 64 Bit patched as of today. After virtual box install it disabled eth0 (first NIC) and I have no networking at all. From the command line it looks like the bridged network is being assigned to the physcial interface and that breaks connectivity.

I had to log in as Admin and disable and reenable both interfaces for it to sort of work. Not it keeps putting the card off line and online. Not sure how this bug reared its ugly head so often but it has.
",evit
8275,3D accelerated OpenGL 1.5 occlusion query support missing,Windows,Windows,VirtualBox 4.0.2,2015-02-14T07:36:26Z,2015-02-14T07:36:26Z,"Host: Windows 7 Ultimate 64-bit
Guest: Windows XP Professional SP3 32-bit
3D acceleration: Enabled

The Windows XP guest reports the OpenGL version as ""2.1 Chromium 1.9"".
However not all OpenGL features up until OpenGL 2.1 are supported.
The following OpenGL 1.5 functions are missing: glBeginQuery, glDeleteQueries, glEndQuery, glGenQueries, glGetQueryObjectiv, glGetQueryObjectuiv, glGetQueryiv, glIsQuery. This means that OpenGL programs that expect full OpenGL 2.1 support may crash if it uses the OpenGL version string to determine whether or not it can use OpenGL 1.5 occlusion queries.

Attached is output from glewinfo which lists extensions that are present/missing.",Jonathan Liu
13834,linked clone - uuid already exists,Linux,Linux,VirtualBox 4.3.22,2015-02-14T09:48:11Z,2015-02-14T09:48:11Z,"goodmorning, I have this problem, and I think that all versions from 4.3 are affected, because the problem doesn't .
I created 1 virtualmachine, started, SO installed, closed, everything fine.
I want a (one or more) clone of this machine, type linked-clone, so I use the procedure to create a linked-clone.
If I remove 1 of the 2 machine (remove only) and than I re-add there is the error about ""uuid already exists"" and I can't re-add the machine.
I think the problem is that each machine load all the structure of snapshots for both the machine, so if I re-add the one removed, it sais that already exists.
I have this problem with host Linux and Windows",sigfrido.barb
13836,Not rendering the window properly when in fullscreen,other,other,VirtualBox 4.3.22,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
13840,Trailing spaces in VM names are not handled consistently when grouping,Windows,all,VirtualBox 4.3.22,2015-02-16T01:56:59Z,2015-02-16T01:56:59Z,"1. Create 3 new VMs ""test1"", ""test2"", ""test3 "". The VM names do not include the quotation marks, but test 3 has a trailing space in its name.
2. Select all three new VMs and create a new group for them.

The VMs all appear in the group in the Virtual Box Manager GUI, but when I look at the directories where the data is stored, I see that test1 and test2 have been moved into a subdirectory named ""new group"", but test3_ (directory name has underscore instead of space) has not been moved into the subdirectory - it remains in its original parent directory
",m6477
5683,Configurable actions on signals,Mac OS X,other,VirtualBox 3.1.0,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
13663,Repeat installation without reboots in between does not work.,Windows,Windows,VirtualBox 4.3.12,2015-02-16T10:54:38Z,2015-02-16T10:54:38Z,"*Steps to reproduce*
1. Download VBox 4.3.12 (x64 in my case). 
2. Install the setup. 
3. Uninstall the setup. A dialog prompts for reboot. Select 'No'.
4. Again install the same setup. 
5. Upon complete installation, a reboot prompt appears. Select 'Yes' this time. 
6. Upon reboot, try to start a VM (simple windows 7 installation .vdi)

*Observation*
VM does not start. 
Kernel driver missing error is shown. ",praseo
13844,Ubuntu guest on Mac OS X stops tracking battery status after full charge,Mac OS X,Linux,VirtualBox 4.3.22,2015-02-16T16:49:36Z,2015-02-16T16:49:36Z,"As the subject says, an Ubuntu guest tracks the battery status of the Mac host but stops if the host is charged to 100% of the battery. After that point, the Ubuntu guest reports a 100% charged battery regardless of the status of the host (plugged or unplugged).

This issue '''is not present''' with a Windows 7 guest, for example. The Windows client continues to track battery status without problems after a full charge.

Some details about my setup:[[BR]]

'''Guest'''[[BR]]
Ubuntu 14.04 LTS
4 Processors 2GB of memory

'''Host'''[[BR]]
MacBookPro Intel Core i7 4GB of Memory
Mac OS X 10.10.3 (14D72i), but the problem was observed with 10.10.2 public release version as well.",SototaSoft
13843,MSCOM Java Binding - Breakage,Windows,all,VirtualBox 4.3.22,2015-02-17T21:09:03Z,2015-02-17T21:09:03Z,"MSCOM Java bindings are currently unusable as they fail on any method not returning a String.[[BR]]
[[BR]]
Test code[[BR]]

{{{
public class MsComTest {
   
   public static void main(String[] args) {
      VirtualBoxManager mgr = VirtualBoxManager.createInstance(null);
      try {
         mgr.getVBox().getRevision();
      } finally {
         mgr.cleanup();
      }
   }
   
}
}}}
",Max D
13851,Linked clone not created in group subdirectory,Windows,other,VirtualBox 4.3.20,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
10558,Console Mode Mouse Position not moving in Guest,all,Linux,VirtualBox 4.1.14,2015-02-18T09:06:12Z,2015-02-18T09:06:12Z,"The square mouse cursor for the console mode of a Linux guest does not move.  When the mouse is moved, the console cursor remains in the center of the text display.  Double-clicking the mouse causes the line at the cursor position to be selected. Apparently the mouse clicks are being seen, but not the mouse position updates.

I tested using VirtualBox 4.1.14, 4.1.12 and 4.1.10 on the host.  Those versions all behaved the same way.  Only the version of Guest Additions seems have an effect on the problem.

I am using the generic Linux version of the Guest Additions, since there is no version specifically for Slackware Linux.

Guest Additions version 3.1.6 and 4.1.2 work in console mode, and the square text mouse cursor moves as expected.  Guest Additions versions 4.1.4 through 4.1.14  all have this problem and the console mouse cursor is frozen.  My testing for all versions of the Guest Additions was done using VirtualBox 4.1.14 on the host.

I tested both a 64-bit Slackware Linux guest and a 32-bit Slackware Linux guest.  I also tested the v2.6 Linux kernel (32-bit) and kernel v3.2.13 (32/64-bit).  They all behaved the same way, and the problem occurs (or not) depending on the version of Guest Additions.

My host OS is Windows 7 64-bit. I also tested using a Slackware Linux host with kernel v3.2.13.  The host OS does not have any effect on the problem.  The console text mouse cursor works in earlier versions of the Guest Additions and does not work in later versions of the Guest Additions.",ErikW
13853,SDK: Java via webservice: IMachine.setGroups causes IMachine.deleteConfig to work wrongly,Windows,all,VirtualBox 4.3.22,2015-02-18T09:30:44Z,2015-02-18T09:30:44Z,"Setting:
Using a java application to access webservice from SDK to control virtual box.

Problem: IMachine.deleteConf does not delete files when machine is in a group other than ""/""

Use case:
- Create clones
- Add clones to group ""/Clones"" (and only this group)
- Verify: Files of clone were created in subfolder ""/Clones/Name_of_clone
- Delete clones using 'deleteConf' does NOT delete files and does not fail! Documentation does not mention anything related to that

Workaround
- Before deleting, change group back to ""/"". delteConf works as expected

",andresluzern
13861,Feature Suggestion: usb and other devices controlling of connections admin permissions,Windows,Windows,VirtualBox 4.3.22,2015-02-19T22:51:48Z,2015-02-19T22:51:48Z,"There should be a way to at least hide (as in VMware player)
or preferably disable the usb connections or restrict for 
non admin users, 
the connecting and disconnecting of specific usb and other devices
shared with the host so kids/non admin users can't randomly connect
and disconnect devices. 
One example is the mouse/keyboard -if disconnected instability in host also.
Or if loading a VDI for virtualbox off the external usb
hard drive you don't want this accidentally disconnected from the host, 
as you may have data loss and crash VM.

I am new to using virtual box and have yet to use the usb filters -not sure how this works.",Astrogirl
13865,Make text from label in the overview of details of the machine copyable,other,other,VirtualBox 4.3.22,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
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,other,VirtualBox 4.3.22,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
12910,respect host-only settings on update / upgrade,Windows,Linux,VirtualBox 4.3.10,2015-02-20T12:51:47Z,2015-02-20T12:51:47Z,"Every time I updated / upgraded my VBox installation my Host-only Adapter settings are changed. I have to reconfigure my settings all the time. This is very annoying, because the problem exists for years.",kirsche40
13875,Uninstaller doesnt remove all drivers,Windows,other,VirtualBox 4.3.22,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
13877,USB microscope camera on windows guest : bandwidth error,Linux,Windows,VirtualBox 4.3.18,2015-02-21T16:22:03Z,2015-02-21T16:22:03Z,"Guest : Windows XP
Host : Ubuntu 14.04 64 bits
VirtualBox 4.3.10 with extension and additions

I use a professionnal camera (Toupcam) on a microscope connected to USB port of the host. It works on the host.
On the windows guest, with a specific application (Toupview) the camera is detected but when I ask a preview I get an error : the USB bandwidth is not sufficient...
USB 2.0 is activated in VBox and other USB devices work.

An idea ? Thanks.",arverne73
13879,Seamless mode tri-head hosts,Windows,Linux,VirtualBox 4.3.22,2015-02-22T11:32:48Z,2015-02-22T11:32:48Z,"Hi,

When using seamless mode with 3 monitors, only 2 monitors are displayed. The main monitor does not display guest windows (and taskbar); but we see them on the preview and we can drag them over the ""not displayed monitor"".

Screenshot attached

All is working fine on dual-screen and in normal mode

Test with 4.3.22 and build 98406",MPoil
13880,"OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')",other,other,VirtualBox 4.3.22,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
13881,Login screen not full screen on Oracle Linux 5,Mac OS X,Linux,VirtualBox 4.3.22,2015-02-22T22:12:22Z,2015-02-22T22:12:22Z,"Since upgrading to 4.3.22 the login screen on Oracle Linux 5
fails to go into full screen. However, when logging-in to user
accounts, the screen does go full.

I went back one version to 4.3.20 and all screens are in full.

Forum discussion with log file.
https://forums.virtualbox.org/viewtopic.php?f=8&t=66245
",ASGR
11183,Nonexistent host networking interface,Windows,Windows,VirtualBox 4.2.4,2015-02-23T08:06:03Z,2015-02-23T08:06:03Z,"The following error message is displayed when restoring a VM from a Saved state:


{{{
Failed to open a session for the virtual machine [VM NAME].

Nonexistent host networking interface, name 'Atheros AR8131 PCI-E Gigabit Ethernet Controller (NDIS 6.20) #2' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
}}}


This occurs when the following is performed:

1. VM is running fine, and in Bridged networking mode connected to the LAN network interface. This interface is connected to a wireless router
2. The VM state is saved
3. Host is put to sleep
4. Wireless router is unplugged
5. Host is woken up
6. A different network device, in this case a network hub is plugged into the LAN
7. The VM is started again, and the error appears

The workaround is to delete the savestate and start the VM again.

For interest, the VM is Windows 2012 with 8GB RAM, 2 CPUs and apart from Shared Folders there is nothing fancy configured.

This behaviour does occur for all OSs and configurations.

I would assume this has something to do with when a network interface is disabled and enabled again, it adds ""#2"", ""#3"" next to it. Note, though that no setting in the Host (in Windows 7) shows that the network interface has been renamed, this appears to be the internal NIC name.",georgeby
13870,Video driver for Windows 10 is turned off,other,other,VirtualBox 4.3.22,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
13896,virtualbox installing rolling back in the end of the install,other,other,VirtualBox 4.3.22,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
13891,VNC output scrambled during Ubuntu installation,other,Linux,VirtualBox 4.3.22,2015-02-26T09:18:36Z,2015-02-26T09:18:36Z,"I ran VirtualBox headless on a FreeBSD 10.1 server (host) and tried to install Ubuntu 14.10 as a guest from the live iso image. I connect to the VirtualBox VNC server to get the VM output. The Ubuntu VM boots up, my VNC client shows the Ubuntu splash screen but as soon as the Ubuntu desktop gets started I get a scrambled image.
I can confirm the problem on FreeBSD 9.3 / VirtualBox 4.2.16 and FreeBSD 10.1 / VirtualBox 4.2.16 & VirtualBox 4.2.22. I have tried different VNC viewer @ Ubuntu (ssvncviewer) and Windows (RealVNC), no difference.

VM VNC output

[[Image(http://www.directupload.net/file/d/3908/adgfi9ld_png.htm)]]


Steps to create the VM:
- set VM='Ubuntu_14.10'
- VBoxManage createvm --name $VM --ostype ""Ubuntu_64"" --register
- VBoxManage storagectl $VM --name ""SATA Controller"" --add sata --controller IntelAHCI
- VBoxManage storageattach $VM --storagectl ""SATA Controller"" --port 1 --type dvddrive --medium ~/ubuntu-14.10-desktop-amd64.iso
- VBoxManage modifyvm $VM --memory 2048 --vram 128
- VBoxManage modifyvm $VM --vrdeproperty VNCPassword=password
- VBoxHeadless -s $VM


Output from VBoxHeadless
{{{
Oracle VM VirtualBox Headless Interface 4.3.22_OSE
(C) 2008-2015 Oracle Corporation
All rights reserved.

24/02/2015 22:28:30 Listening for VNC connections on TCP port 3389
24/02/2015 22:28:30 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3389.
24/02/2015 22:28:34   other clients:
24/02/2015 22:28:34 Client Protocol Version 3.8
24/02/2015 22:28:34 Protocol version sent 3.8, using 3.8
24/02/2015 22:28:34 rfbProcessClientSecurityType: executing handler for type 2
24/02/2015 22:28:34 Pixel format for client 192.168.0.109:
24/02/2015 22:28:34   32 bpp, depth 24, little endian
24/02/2015 22:28:34   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
24/02/2015 22:28:34 Enabling X-style cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling full-color cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling cursor position updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling KeyboardLedState protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling NewFBSize protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedMessages protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedEncodings protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling ServerIdentity protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling Xvp protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Using hextile encoding for client 192.168.0.109
24/02/2015 22:28:38 Sending rfbEncodingNewFBSize for resize to (720x400)
24/02/2015 22:29:04 Sending rfbEncodingNewFBSize for resize to (1024x768)
24/02/2015 22:29:06 Sending rfbEncodingNewFBSize for resize to (1152x400)
}}}


Output from ssvncviewer (VNC client)
{{{
Proto: RFB 003.008

Connected to RFB server, using protocol version 3.8

SelectSecurityType:
  sec-type[0]    2  (rfbSecTypeVncAuth)
Security-Type:   2  (rfbSecTypeVncAuth)  Latency: 3.01 ms

Performing standard VNC authentication
VNC Password: 
VNC authentication succeeded

Desktop name ""VBoxVNC""

VNC server default format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 0 green 8 blue 16
Warning: Cannot convert string ""-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*"" to type FontStruct
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
geometry: 720x400+358+238 ycrop: 0
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 720x400
try_create_image: image->bytes_per_line: 2880

guessed: -compresslevel 1
guessed: -qualitylevel  9
enabling 'delay_sync' mode for faster local drawing,
disable via env SSVNC_DELAY_SYNC=0 if there are painting errors.
New Size: 1024x768 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1024x768
try_create_image: image->bytes_per_line: 4096
New Size: 1152x400 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1152x400
try_create_image: image->bytes_per_line: 4608
}}}
",MrSmith
12860,"Linux guest aborts in VRDP, OpenGL mural warning",Windows,Linux,VirtualBox 4.3.8,2015-02-26T11:51:28Z,2015-02-26T11:51:28Z,As of 4.3.8 my Fedora 20 guest (Windows 8.1 host) is aborting when I launch Komodo IDE within the VRDP connection. If I launch Komodo with the VM running directly it does not abort. VBox.log attached.,Citryphus
13792,Bidirectional clipboard not working host->guest under certain circumstances (see text),Linux,Windows,VirtualBox 4.3.20,2015-02-27T11:18:21Z,2015-02-27T11:18:21Z,"Host: Debian jessie, VirtualBox 4.3.20
Guest: Windows 7, with guest additions 4.3.20, bidirectional clipboard activated

When host has text in clipboard, then VM is started and trying to paste the text in VM, it will not work.
If text is copied to clipboard on host *after* VM start, it will work.

Step-by-step instructions:

*** NOT working ***
1. HOST: Copy text 'abc' to clipboard (using mousepad and CTRL-C or right-click menu)
2. HOST: Start VM
3. VM: Start Notepad
4. VM: Press CTRL-V or choose Edit->Paste from menu (which is *not* greyed out, i.e. there should be sth. in clipboard)
4a. VM: *DOES NOT WORK* (nothing pasted)
5. HOST: Paste in mousepad
5a. HOST: *DOES NOT WORK* (nothing pasted)
REMARK: Obviously, the clipboard seems to be cleared when the VM started
6. HOST: Copy text 'abc' to clipboard {again, as in 1.}
7. HOST: Paste in mousepad
7a. HOST: => *WORKS*
8. VM: Paste in Notepad
8a. VM: *DOES NOT WORK* (nothing pasted)
9. VM: Copy text 'xyz' to clipboard
10. VM: Paste in Notepad
10a. VM: => *WORKS*
11. HOST: Paste in mousepad
11a. HOST: => *WORKS*
12. Shutdown Guest OS


*** working ***
1. HOST: Start VM
2. VM: Start Notepad
3. HOST: Copy text 'abc' to clipboard
4. VM: Paste in Notepad
4a. VM: *WORKS*
5. VM: Copy text 'xyz' to clipboard
6. HOST: Paste in mousepad
6a. HOST: *WORKS*
7. Shutdown Guest OS
",hmickler
13733,VBoxNetFlt.sys v4.3.20 BSOD “DRIVER_POWER_STATE_FAILURE” when hibernate/shutdown WIN7,Windows,all,VirtualBox 4.3.20,2015-03-01T11:01:59Z,2015-03-01T11:01:59Z,"I randomly (but often) get a BSOD ({{{DRIVER_POWER_STATE_FAILURE}}}) when I hibernate or shutdown my laptop (Windows 7 Home Premium).

I first get a black screen during about 10 minutes then I get the following BSOD.

I already got this issue randomly with previous versions of VirtualBox and I thought it was fixed when reinstalling a new version…

analyze -v output:
{{{
*******************************************************************************
*                                                                             *
*                        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: fffffa8005572700, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800feaa0a0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88010200000 VBoxNetFlt

IRP_ADDRESS: fffffa800feaa0a0

DEVICE_OBJECT: fffffa8007771050

DRIVER_OBJECT: fffffa8007756e70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0354c8d2 : 00000000`0000009f 00000000`00000003 fffffa80`05572700 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034e785c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`034e76f6 : fffffa80`0e88fc58 fffffa80`0e88fc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034e75de : 000001b6`a883467f fffff800`00b9cc58 00000000`00b847c0 fffff800`0365ba88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034e73c7 : 00000060`dc5662c2 00000060`00b847c0 00000060`dc56620f 00000000`000000c0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d48ca : fffff800`03657e80 fffff800`03665cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 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 VBoxNetFlt
start             end                 module name
fffff880`10200000 fffff880`1022b000   VBoxNetFlt T (no symbols)           
    Loaded symbol image file: VBoxNetFlt.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
    Image name: VBoxNetFlt.sys
    Timestamp:        Mon Nov 24 12:06:09 2014 (54731121)
    CheckSum:         000271EA
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
}}}
",lorcan
13913,Start a VM at boot time on a Windows host,Windows,all,VirtualBox 4.3.24,2015-03-03T15:36:38Z,2015-03-03T15:36:38Z,"Can a VM be started at boot time on a Windows host? 
Documentation (see page https://www.virtualbox.org/manual/ch09.html#autostart ) 
say it is possibile on other hosts (Linux, Solaris, ...).
Does it mean it is not possible on Windows hosts?
If so, can this limitation be inserted in documentation?
If not, can the documentation include instructions to start a guest VM at boot time?

  ",Marius Roma
13917,USB configuration GUI inconsistent between OS X hosts compared to GNU/Linux and Windows hosts,Mac OS X,all,VirtualBox 4.3.24,2015-03-04T03:57:02Z,2015-03-04T03:57:02Z,"On GNU/Linux and Windows hosts, to configure USB for a virtual machine, users go to the ""USB"" option on the left of the configuration window. On OS X, there is no ""USB"" option immediately visible on the virtual machine configuration window. Instea, users go to ""Ports"" then select the ""USB"" tab on OS X.",Be
13920,Starting guest with multiple monitors on a different workspace causes virtual screens to disappear,other,other,VirtualBox 4.3.24,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
13921,"Missing values from configuration validation function, Acpi",all,all,VirtualBox 4.3.24,2015-03-04T19:00:16Z,2015-03-04T19:00:16Z,"Hi,

The configuration validation function: ""CFGMR3AreValuesValid"" does not include the following two ACPI extradata settings. The core functionality is available, but users are unable to set these via the extradata settings, as 3 out of 5 values are available to be configured. It is most likely a bug/oversight:

- Missing from the check:
AcpiOemTabId
AcpiOemRevision


- Included:
AcpiOemId
AcpiCreatorId
AcpiCreatorRev


Regards
Mikael   ",nsmfoo
13916,Altium on VirtualBox,other,other,VirtualBox 4.3.24,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
13912,Windows 10(host) and virtual box,Windows,all,VirtualBox 4.3.24,2015-03-04T22:41:18Z,2015-03-04T22:41:18Z,Host pc-surface pro (i5) causing black screen after install of virtual box.,Bluwolf024
13925,file timestamp not preserved on tar-extracted files in shared folders on linux guest windows host,Windows,Linux,VirtualBox 4.3.24,2015-03-05T17:36:29Z,2015-03-05T17:36:29Z,"There is a strange behavior, that files extracted from TAR package within shared folders on Linux guest/Windows host, does not preserve file timestamp stored in a tarball. The files' timestamp get converted to the extraction time.

I've searched through Virtualbox issues, and saw another ticket regarding timestamp in shared folders, #6473, but that was solved years ago, and does not apply to this particular issue.

Issue is easily reproducable:
- configuration: Windows 7 Host, Linux (Debian, no GUI) Guest
- using tar command from a Linux Guest shell, create a TAR of an older ""test file"", so the timestamp would be evident,
- delete the ""test file""
- extract the ""test file"" from a tar archive
- the timestamp will be wrong, as tar preserves timestamp by default
- to confirm we can do the same procedure within another Linux Guest folder, other than the shared folder, and the timestamp will be preserved.

Here's code sample, presuming we have a file.pdf test file, within /var/www/shared folder, which is a shared folder, both Linux guest and Windows 7 host can see:

{{{
cd /var/www/shared
ls -la
> -rwxrwxrwx 1 root root 11654 Jan 23 08:16 file.pdf
tar -c -f test.tar file.pdf
rm file.pdf
tar -x -f test.tar
ls -la
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 file.pdf
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 test.tar
}}}

I would kindly ask anyone to answer if there is a solution to this problem, or is there anything we can do to preserve original timestamps at tar extraction process within shared folders, so we don't need to extract files in a separate folders and move the files back, as we need those timestamps.

We have both, current Virtualbox and current Guest Additions installed.",sargac
13928,Change of behavior of Host Only Network,Windows,Linux,VirtualBox 4.3.24,2015-03-06T10:52:19Z,2015-03-06T10:52:19Z,From version 4.3.22 you have added a value for *NdisDeviceType register entry. A value for that entry as NDIS_DEVICE_TYPE_ENDPOINT implies that Windows ignores the endpoint device when it identifies networks. I was using a virtual linux firewall connected to the bridged interface to create a network with different OS including the access to internet from the host. After this change in 4.3.22 Windows does not detect the virtual network and there is no connection from most windows applications.,luisds
13930,"Shared folders: ""umount -f"" required",Linux,Linux,VirtualBox 4.3.24,2015-03-06T12:53:56Z,2015-03-06T12:53:56Z,"Host: openSUSE 13.1 (64bit)
Guest: openSUSE 13.2 (64bit)",robert spitzenpfeil
13862,"Sound not working 4.3.22 windows xp guest, windows 8.1 host",Windows,Windows,VirtualBox 4.3.22,2015-03-09T05:49:43Z,2015-03-09T05:49:43Z,"HI many others also reported on forum that sound that was working has stopped in newer version.  I tried reinstalling drivers, installing downloaded driver, reinstalling guest additions, installing K-lite codec pack, checking all volume controls not muted.  Also uninstalled, rebooted and reinstalled host sound drivers. 
In meantime will be downgrading to older 4.3.20 where was working sound. Host sound works well through speakers. Please fix soon as prefer to use current version.",Astrogirl
13931,Excessive processor use,Windows,Linux,VirtualBox 4.3.24,2015-03-10T09:47:37Z,2015-03-10T09:47:37Z,"Since 4.3.22 or so I noticed that after a while VBox is starting to use a lot of processor power. Everything is OK when it starts but after few hours its 90-100% of one thread and some minor-medium use on other threads (35%-40% of total processor time, i7 4770K, 4 cores 8 threads).

Host is Windows 8.1
Guest is 64bit Ubuntu 14.04

It was initially installed under 4.3.20 and there was no problem. It only appeared recently.",randomwhitetrash
13948,Host only interfaces in linux host are being deleted after system reboot.,all,Linux,VirtualBox 4.2.24,2015-03-11T09:00:11Z,2015-03-11T09:00:11Z,"I am using virtualbox verion 4.2.26. I create some hostonly interfaces(vboxnetxx) to communicate from host to guest. When the system is rebooted all these hostonly interfaces are being removed (even though the virtual machines exist) and I am not able to communicate with my machines.
I observed that all the info in virtualbox.xml file is being removed.
Please let me know if it is a desired functionality or a bug.",PRANEETH MANNEM
13932,VBoxManage returns success even thow it failes,all,Linux,VirtualBox 4.3.24,2015-03-11T13:38:58Z,2015-03-11T13:38:58Z,"vboxmanage metrics enable --list ""Android 5""
echo $?
0
vboxmanage --version
4.3.24r98716
",Kappen
8405,Problem with the graphical abilities of a windows xp guest running unity3d,Linux,Windows,VirtualBox 4.0.4,2015-03-12T10:26:24Z,2015-03-12T10:26:24Z,"The programm unity3d( a game editor) is verry unhappy in a Virtualbox enviroment.
It is exrtreme in a manner, that the program is not able to run more than some minutes and with heavy visual impairements(it is stable in a native windows installation).

You can find the program under:

http://unity3d.com/unity/download/

I think here is the posebility to improve the graphical abilities of virtualbox.


Greetings
",anonymous
13947,bridged networking broken for Windows 8.1 guest,Linux,Windows,VirtualBox 4.3.24,2015-03-12T14:13:44Z,2015-03-12T14:13:44Z,"The windows 8.1 guest diagnostics don't see a problem with the bridged connection, but web browsers are unable to connect to any URL. If the adapter (Intel Pro 1000 desktop) is set to NAT in the Linux host then the connection is ok (browsers are able to connect). This problem also existed for version 4.3.18. Windows 7 guests do not have this problem.",nbi
13949,All guests fail to start,Windows,Linux,VirtualBox 4.3.24,2015-03-16T08:24:39Z,2015-03-16T08:24:39Z,"All guests fail to start at virtualbox 4.3.24


The virtual machine 'bioLinux' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\libindo\VirtualBox VMs\bioLinux\Logs\VBoxStartup.log'.

Code erorr: E_FAIL (0x80004005)
Компонент: Machine
Интерфейс: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

",buratin
13958,GUI does not indicate corrupt/missing save file in an obvious way,Windows,all,VirtualBox 4.3.24,2015-03-16T14:20:14Z,2015-03-16T14:20:14Z,"I have a windows 8.1 x64 host running 4.3.24 which cannot start a Windows 7 Enterprise x64 guest with saved state after rebooting the host OS. Something appears to have removed or corrupted the save-state file, but the GUI does not indicate this in an obvious way (it does appear in the log, however).

More desirable behavior would be a ""Save file is missing or corrupt. Restart VM?"" dialog. Instead, I get this, which is also symptomatic of a large number of other (more complex) failures:

{{{
Failed to open a session for the virtual machine CDW Win7.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
}}}

The Log:

{{{
VirtualBox VM 4.3.24 r98716 win.amd64 (Mar  2 2015 14:18:45) release log
00:00:03.174146 Log opened 2015-03-16T13:53:05.920532400Z
00:00:03.174149 Build Type: release
00:00:03.174155 OS Product: Windows 8.1
00:00:03.174157 OS Release: 6.3.9600
00:00:03.174158 OS Service Pack: 
00:00:03.258341 DMI Product Name: 20246
00:00:03.262022 DMI Product Version: Lenovo IdeaPad Yoga 11S
00:00:03.262030 Host RAM: 8071MB total, 5351MB available
00:00:03.262033 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:03.262034 Process ID: 4556
00:00:03.262035 Package type: WINDOWS_64BITS_GENERIC
00:00:03.262679 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={VM cannot start because the saved state file 'C:\Users\P\VirtualBox VMs\CDW Win7\Snapshots\2015-03-14T16-48-25-963707000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false
00:00:03.263825 UIMediumEnumerator: Medium-enumeration finished!
00:00:03.264472 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 640x480
00:00:03.268691 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 1 as 640x480
}}}
",kc0tfb
13970,Switch desktop defect,Linux,Linux,VirtualBox 4.3.26,2015-03-20T09:46:09Z,2015-03-20T09:46:09Z,"On Linux Mint Mate, I have a two-monitor linux VM, and when I boot up, it starts with just one window. The second window is launched a few second later.
If in the meantime, I change desktop (using ctrl-alt right or left, for example), the first window stays in the starting desktop, but the second one is opened in the second desktop.

Would be great if they were opened both in the same desktop.

Thank you.",malarittu
544,Full Screen shown behind kicker,Linux,other,VirtualBox 1.4.0,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
13578,Option to disable the USB device filters,Linux,other,VirtualBox 4.3.18,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
13953,WinXP guest machines do not start after the update to version 4.3.24 & host system reboott,Windows,Windows,VirtualBox 4.3.24,2015-03-22T12:52:20Z,2015-03-22T12:52:20Z,"After the update to version 4.3.24 from 4.2.18 I was able to run a win XP guest machine but after the host (Win 7 Home Premium x64, AMD, Acer Aspire) reboot it has been possible no longer. I tried to turn off PC Tools 7 firewall, antivirus AVG 2015 and Iobit Advanced Care 8.1 but without a success. I am enclosing screenshots and the VM guest machine logs. Could you look at the issue?

The error messages are:
""Error relaunching VirtualBox VM process: 5
Command line: '...--starttvm...--no-starttvm-errormsgbox...""

""The virtual machine '...' has terminated unexpectedly during startup with exit code 1(0x1)...
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {...}""
",Kola Wisarionowicz
13942,Failed to start the virtual machine when seemingly unreachable,Windows,Windows,VirtualBox 4.3.24,2015-03-23T11:28:17Z,2015-03-23T11:28:17Z,"I as a system connected to the virtual media used images located on a network drive.
In the case where the network drive is not available, the virtual system can not start.
  It would be better to just give a message about the unavailability of the resource, not to block the program.",and_kors
13491,HostAudioNotResponding,Windows,Windows,VirtualBox 4.3.16,2015-03-24T15:19:02Z,2015-03-24T15:19:02Z,"The warning message appears at Vm's start/restore. 
Audio not transmitted from Guest to Host. Guest does not report any issue.
I've never had such a problem before (since 4.1 at least). 
!!! Reverted back to 4.3.12 works OK again !!!.

",BugRep0rt3r
13713,VirtualBox fails to create bridged or host-only network adapter on some Win7 desktops - Error FAIL (0x80004005),Windows,all,VirtualBox 4.3.20,2015-03-25T14:34:59Z,2015-03-25T14:34:59Z,"Detected in:  VirtualBox-4.3.20-96997-Win.exe

On some of our Win7 desktops with Broadcomm gigabit 57xx ethernet adapter, When installing or configuring VirtualBox, it returns error FAIL x8004005 and fails to create the virtual ""host-only"" and/or bridged network adapter.  Switching to NAT also fails with a similar network-related error (cannot find network adapter for PXE boot or similar). 

This error is occurring only on some (~10%) of our Qa desktops, but all have identical hardware and configurations running similar recent Win 7 builds. 

Note that this error was also occurring also under Vbox 3.18 and VBox 3.16, for these same desktops, and is similar to many open defects already logged with oracle. 

We have tried install/uninstall numerous versions of Virtual Box, as local and domain Admin, with AVG antivirus disabled, as well as uninstall + manual registry and driver-file cleaning as per FAQs, + system restores, and nothing fixes it. For these affected desktops, Vbox is unable to work.

Note that this error is very similar to open issue logged with Oracle, on which there is no resolution, but it seems very suspicious that it's working for most of QA and RnD, except for those recent windows builds.

Scenario 1: 
------------------
On install, or subsequently from :
 ==> Vbox/File/Preferences/Network/Host-Only/ ==> try to create a new ""host-only"" adapter:
Result Code: E_FAIL (0x80004005)
- In Device manager, every time this is attempted, we get a new ""unknown"" network device.
- Manual device driver update fails (see attached screenshot)
 
Scenario 2:
-----------------
On any guest image
==> Settingas/Network==> select ""Bridged"" network adapter ==> save and start guest VM:
Result Code:  E_FAIL (0x80004005)
Component: 
Console
Interface: 
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}


Similar issues logged @ Virtual Box:
--------------------------------------------
   * https://www.virtualbox.org/ticket/13690
   * https://www.virtualbox.org/ticket/13681
   * https://www.virtualbox.org/ticket/13654
   * https://www.virtualbox.org/ticket/13481

See attached vbox ""setupapi"" log files and screenshots
--------------------------------------------",mkorning
13986,Shared folder accessible after removed from list of shared folders,Linux,all,VirtualBox 4.3.26,2015-03-25T16:00:08Z,2015-03-25T16:00:08Z,"When removing a 'permanent' shared folder while it is mounted, it is removed from the list of shared folders but it's still fully accessible in the VM. There is a pop up warning that this will result in 'broken shared folder', which only offers to click 'OK'. The folder is even accessible after rebooting the guest system and host system. Tested this with Linux and Windows guest systems.

Steps to reproduce:
1. Add shared folder in shared folder settings, check 'Make Permanent'
2. Mount shared folder in guest system
3. Remove shared folder in shared folder settings",A_Dombeck
13991,NUL character with a value of 0 ^@ Shown In Linux Console,Linux,Linux,VirtualBox 4.3.24,2015-03-26T11:12:54Z,2015-03-26T11:12:54Z,"Hi,

My Specs;

Slackware 14.1 x86_64 - Host
screen size 1920x1080
Virtualbox 4.3.24 - (compiled from source)


Slackware 14.1 x86_64 - Guest
screen size 1920x965
Virtualbox 4.3.24 - (Guest Additions installed)

I noticed when I restart or shutdown Slackware, in the console, I am seeing the NUL character with a value of 0 that is represented as `^@` appear next to text on the screen.

I thought at first something in the Slackware system was causing this.

I was running the Guest with the default of 'Auto-resize Guest Display', this causes the console to have a small size, and it seems for some reason Virtualbox doesn't like it and creates the Nul Character, because if I change the Guest to 'Scaled Mode' it never appears.

I tested this several times changing back and forth with the 'Auto-resize Guest Dispaly' and 'Scaled Mode', and everytime it was on 'Auto-resize Guest Display' it appeared, and everytime it was on 'Scaled Mode' it did not appear.

I'm attaching a screen shot, called vb_character.jpg, notice the line with the red dot I marked, to the far left the word; `^@Sending`...",VBoxGrl
13978,USB filter with empty name gets deleted,all,all,VirtualBox 4.3.26,2015-03-27T16:50:45Z,2015-03-27T16:50:45Z,"If on a virtual machine an USB filter is created but the ""Name:"" field is let being empty the filter will only be saved temporary and deleted as soon as the USB filter menu closes.",Sworddragon
13973,Win 10 x64 guest with Guest Additions crashed host xserver,Linux,Windows,VirtualBox 4.3.26,2015-03-29T09:02:57Z,2015-03-29T09:02:57Z,"Host:
Linux Mint 17.1 x64.
X.Org v1:7.7+1ubuntu8.

Guest:
Windows 10 x64 Technical Preview 9926.

What I did:
1) Installed Win 10x64 English.
2) Installed Guest additions and asked to restart.
3) Tried to login to windows after the restart. Host froze and after ~1 min, X crashed. Attached pic shows what I see on tty7 (X tty after crash).

I'm guessing that something is wrong with the guest additions.",Tharbad
13763,Problem with setextradata GUI/Seamless on,Windows,Windows,VirtualBox 4.3.20,2015-03-30T16:09:06Z,2015-03-30T16:09:06Z,"Hello.
I develop on c#.
I'm trying to start VirtualBox VM to SeamlessMode via VBoxManage.exe in command line under Windows 7/8/8.1 host. The problem is that it works, but not all the time. If the host computer is powerful then the success rate of starting VM in seamless mode is about 90%. If the host machine is slow then the success rate drops to 50%.
Please see the attached snippet (VM starting in seamless mode) 
	restoreSnapshot();[[BR]]setSeamlessMode();[[BR]]runVM(); 

	public static void restoreSnapshot()
	{
			Process VBoxManage = new Process();
    			VBoxManage.StartInfo.CreateNoWindow = true;
	    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    			VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    			VBoxManage.StartInfo.Arguments = ""snapshot VM restore Snap1"";
	    		VBoxManage.StartInfo.UseShellExecute = false;
	    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    			VBoxManage.Start();[[BR]]String line = """";
		        while (!VBoxManage.StandardOutput.EndOfStream)
		        {	        
		            line = VBoxManage.StandardOutput.ReadToEnd();	            
		        }
	        	VBoxManage.Dispose();
	}

	public static void setSeamlessMode()
	{
		
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    		VBoxManage.StartInfo.Arguments = ""setextradata VM GUI/Seamless on"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    		VBoxManage.Start();[[BR]]String line = """";
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
	        VBoxManage.Dispose();
	        
	}

	public static void runVM()
	{            
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
            	VBoxManage.StartInfo.Arguments = ""--nologo startvm VM -type GUI"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;
    		VBoxManage.Start();            
	        String line = """";[[BR]]
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
                VBoxManage.Dispose();            
        }",batyr
13968,Can't drag to select text in Google Chrome on Linux Guest,Windows,Linux,VirtualBox 4.3.26,2015-03-30T23:33:32Z,2015-03-30T23:33:32Z,"I am unable to drag to select text in Google Chrome on a Linux Guest.

There is currently a thread on chromium at code.google.com for this.  A common factor is when running in VirtualBox - https://code.google.com/p/chromium/issues/detail?id=456222 .  Note: Their title for the bug is missleading and they are lumping the above description into that same bug report.

By drag to select text I mean: mouse down on some text, drag mouse to highlight some text, then mouse up.

I can drag to select text in Firefox with no problems.

My setup:
Host OS: Windows 8.1 Pro,
VirtualBox:  4.3.26 r98988 with Guest additions installed,
Virtual Machine OS: XUbuntu 14.04 last updated 3/17/2015,
Chrome: 41.0.2272.89 (64-bit)

On the code.google.com report, people have seen the issue with host OS of Mac OS X.  One report mentioned downgrading chrome fixed it.  Another mentioned uninstalling Guest Additions fixed it.",Scott H
14018,Shared Clipboard stops working,Windows,Windows,VirtualBox 4.3.20,2015-04-02T00:16:04Z,2015-04-02T00:16:04Z,"Host: Windows 7 x64

Step 1: Start guest with guest additions, bi-directional clipboard (in my case, linux mint)

clipboard works both ways, as it should.

Step 2: Start another guest without guest additions, clipboard sharing disabled (in my case, windows 10 preview)

clipboard does not share in 2nd guest, as intended; however, clipboard no longer is shared in the 1st guest now, either direction.",whoami
13937,Windows 10 TP network bridge causes major fault,Windows,all,VirtualBox 4.3.24,2015-04-02T09:32:55Z,2015-04-02T09:32:55Z,"This is similar to ticket number 13912. When VB is installed in the latest beta of Windows 10 technical preview, the host machine halts upon restart. The only thing working is the mouse, nothing else works.

The computer works fine if the network cards are disabled in Windows, but this leaves end users unable to access any network.",dhrida
14023,Modifier keys from the virtual keyboard don't get passed through,Mac OS X,Linux,VirtualBox 4.3.26,2015-04-02T23:53:33Z,2015-04-02T23:53:33Z,"I'm using autopy to generate low-level Quartz keyboard events on my host machine. Most keys get passed through just fine. But for some reason the modifier keys do not. That's command, shift, Option and Control.

https://github.com/msanders/autopy/

The relevant code looks very straightforward:

void toggleKeyCode(MMKeyCode code, const bool down, MMKeyFlags flags)
{
#if defined(IS_MACOSX)
	CGEventRef keyEvent = CGEventCreateKeyboardEvent(NULL,
	                                                 (CGKeyCode)code, down);
	assert(keyEvent != NULL);

	CGEventSetType(keyEvent, down ? kCGEventKeyDown : kCGEventKeyUp);
	CGEventSetFlags(keyEvent, flags);
	CGEventPost(kCGSessionEventTap, keyEvent);
	CFRelease(keyEvent);
#elif defined(IS_WINDOWS)
	const DWORD dwFlags = down ? 0 : KEYEVENTF_KEYUP;

	/* Parse modifier keys. */
	if (flags & MOD_META) WIN32_KEY_EVENT_WAIT(K_META, dwFlags);
	if (flags & MOD_ALT) WIN32_KEY_EVENT_WAIT(K_ALT, dwFlags);
	if (flags & MOD_CONTROL) WIN32_KEY_EVENT_WAIT(K_CONTROL, dwFlags);
	if (flags & MOD_SHIFT) WIN32_KEY_EVENT_WAIT(K_SHIFT, dwFlags);

	WIN32_KEY_EVENT(code, dwFlags);
#elif defined(USE_X11)
	Display *display = XGetMainDisplay();
	const Bool is_press = down ? True : False; /* Just to be safe. */

	/* Parse modifier keys. */
	if (flags & MOD_META) X_KEY_EVENT_WAIT(display, K_META, is_press);
	if (flags & MOD_ALT) X_KEY_EVENT_WAIT(display, K_ALT, is_press);
	if (flags & MOD_CONTROL) X_KEY_EVENT_WAIT(display, K_CONTROL, is_press);
	if (flags & MOD_SHIFT) X_KEY_EVENT_WAIT(display, K_SHIFT, is_press);

	X_KEY_EVENT(display, code, is_press);
#endif
}",michael fox
11133,On a Windows 8 host VM microphone does not work in an XP guest,Windows,Windows,VirtualBox 4.2.4,2015-04-03T06:00:37Z,2015-04-03T06:00:37Z,"Host: Windows 8 64, MB ASUS M2N68 AM-PLUS integrated audio
Guest: Windows XP, ICH AC97

The guest sees the microphone, but does not react when I am speaking into it.

The same VM works on Windows 7 host.",Andrey Gerasimenko
14025,The Exception unkown software exception (0xc06d007e),other,other,VirtualBox 4.3.26,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
12261,Error Enable 3D Acceleration in Virtualbox.,Linux,all,VirtualBox 4.3.0,2015-04-06T23:40:17Z,2015-04-06T23:40:17Z,"When I try to Enable 3D Acceleration enabled in the VMs, I get the following message:

""
This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

Código Resultado: NS_ERROR_FAILURE (0x80004005)
Componente: Console
Interfaz: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}""

My graphics card is ATI / AMD Integrated ATI Raedon 3300 and I have installed the proprietary drivers 13.1 Legacy. My OS is Linux Mint 13 64 bits based on Ubuntu 12.04.1 LTS.

I think I have correctly installed the proprietary drivers and I have also installed Video Hardware Acceleration...

[[Image(http://imageshack.us/a/img812/7149/aqer.png)]]

'''Note :''' In the version 4.2.18 this did not happen, working properly ..

Thanks ..
",Malus
14036,Win 8.1 guest vm machine hangs with VBoxGuestAdditions,Linux,Windows,VirtualBox 4.3.26,2015-04-09T07:16:18Z,2015-04-09T07:16:18Z,"I submitted a ticket #14030 few days ago, and get resolved when i applied diff_smap_4. 

But a new problem comes,I installed VBoxGuestAdditions to my Win 8.1 guest machine, reboot system. When i input the password and login to Win8.1,The VM Machine hangs.I killed the process and restart the win8.1 guest to safe mode,uninstall VBoxGuestAdditions and restart again, Guest is up and running.

I have tried this for several times, Guest machine will hang on logn as long as VBoxGuestAdditions installed.

",fedvb
14037,Error starting virtual machine after upgrading to 4.3.26 The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  E_FAIL (0x80004005),Windows,all,VirtualBox 4.3.26,2015-04-09T07:23:28Z,2015-04-09T07:23:28Z,"Hello, since I upgraded to 4.3.26 (but I tried even using 4.3.27), when I start a VM I got the following error:

Apertura di una sessione per la Macchina Virtuale Vista non riuscita.

The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Daniela\VirtualBox VMs\Vista\Logs\VBoxStartup.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: Machine
Interfaccia: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

This is the host machine:
Microsoft Windows 7 Professional 
6.1.7601 Service Pack 1 build 7601
SAMSUNG ELECTRONICS CO., LTD.
X86-based PC
x64 Family 6 Model 58 Stepping 9 GenuineIntel ~2400 Mhz

Please, see the attached file for startup log

Best regards",shinnai
14027,VMs with bridged network do not start,other,other,VirtualBox 4.3.26,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
11712,Install Makes Windows 8 Host Boot Fail,Windows,other,VirtualBox 4.2.12,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
14033,VM Losing time guest running network backups,all,all,VirtualBox 4.3.26,2015-04-10T12:24:41Z,2015-04-10T12:24:41Z,"One of my VMs is seeing major loss of time when it runs backups.

It does not have this issue at any other time.

I did not see this behavior until I upgraded from the last pre-packaged version of VirtualBox for Fedora 17 to built-from-sources 4.3.(the one before 26).

The host:

`Linux hagrid.sb.litts.net 2.6.43.8-1.fc15.x86_64 #1 SMP Mon Jun 4 20:33:44 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux`

The guest:

`Linux overkill.sb.litts.net 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 15:12:59 EST 2007 i686 i686 i386 GNU/Linux`

''VirtualBox:''
`4.3.26_OSE r98988 built from sources`

I do not see this on other VMs, but this one has the most data.  The other VMs also run Fedora, but not this exact version.

Disk being backed-up:

`/dev/hda3              415G    79G   316G  20% /`

Resulting backup (on an NFS-mounted NAS):

`-rw-rw---- 1 root root 58G Apr  8 05:18 /mnt/backup/overkill/Wed.tar.z`

The host and the NAS both have Gb ethernet connections to the same (switched) physical LAN.

The virtual adapter is ""Bridged"", Intel PRO/1000 MT Desktop (8254OEM).

The virtual disk is a normal VDI 400GB (170.94 actual) dynamic disk on an (emulated) IDE controller.  It is the only disk configured on this VM (except for an empty CDROM).

The VM runs headless.

The tar command:

{{{
tar --totals --exclude var/www/servers/PhotoGallery/FileCache --anchored --wildcards --wildcards-match-slash --exclude proc --exclude sys --exclude dev/pts --exclude dev/shm --exclude var/lib/nfs/rpc_pipefs --exclude proc/fs/nfsd --exclude proc/sys/fs/binfmt_misc --exclude mnt/castaway --exclude mnt/hagrid --exclude mnt/CindyTV --exclude mnt/nas148001 --exclude mnt/backup --exclude etc/lvm --exclude etc/mtab --exclude dev --exclude proc --exclude run --exclude sys --exclude mnt --exclude tmp --exclude var/cache -czpf /mnt/backup/overkill/Wed.tar.z bin boot dev etc home lib lost+found media misc mnt net opt proc root sbin selinux srv sys tftpboot tmp usr var
}}}

The backup runs for several hours.  In today's case, from about 0100 to about 0515.  Accumulated drift is about 40 minutes:

{{{
date
Wed Apr  8 04:43:05 EDT 2015
 Stop/restart NTP (to get correct time from network)
date
Wed Apr  8 05:23:13 EDT 2015
}}}

The VM runs NTP, but the time drift is too large for NTP to compensate.

NTP ends up locking to the local time-of-year clock, which is also slow.

VBox.log (attached) contains lines showing the drift accumulating of the form:

{{{
124:38:08.239525 TM: Giving up catch-up attempt at a 60 001 255 770 ns lag; new total: 60 001 255 770 ns

124:44:06.724982 TM: Giving up catch-up attempt at a 60 001 273 374 ns lag; new total: 120 002 529 144 ns
}}}



",Timothe Litt
14045,full screen mode not ok with 2 sceens  under Ubuntu 14.04  64Bit,Linux,Linux,VirtualBox 4.3.26,2015-04-13T05:54:53Z,2015-04-13T05:54:53Z,"on full screen mode - the guest appears only half (screen_shot attach to this ticket)

One Screen is Belinea, other one Fujitsu Siemens (different sizes)

On Fujitsu Siemens screen: in full screen mode - onle half display (see screen-shot)

On Belinea (smaler one): display is cut on the right side

",Yupi
14042,VBoxNetFlt crashing windows 7 on resume,Windows,Linux,VirtualBox 4.3.26,2015-04-13T09:36:10Z,2015-04-13T09:36:10Z,"My system started bugchecking after I installed virtualbox 4.3.26 r98988 on my Windows 7 SP1 Enterprise system (64 bit).  The first one happened when I awoke the machine after putting it into sleep mode with my vm running.  After that, I made sure to shut down the vm before going into sleep mode but that doesn't prevent the crash.

Please find the crash dump analysis below.  Note that while the analyzer is blaming the multi-process NT kernel, the faulting module is VBoxNetFlt.  That indicates the filter driver is not handling the power state change correctly.
{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22948.amd64fre.win7sp1_ldr.150202-1521
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a3890
Debug session time: Thu Apr  9 16:19:23.133 2015 (UTC - 6:00)
System Uptime: 2 days 7:16:36.599
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800d99d980, fffff800047063d8, fffffa80134bee10}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxNetFlt.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: fffffa800d99d980, Physical Device Object of the stack
Arg3: fffff800047063d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80134bee10, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88000dc6000 VBoxNetFlt

IRP_ADDRESS: fffffa80134bee10

DEVICE_OBJECT: fffffa8011208050

DRIVER_OBJECT: fffffa8013c3c5d0

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:  FFFFF8000470CFB0

STACK_TEXT:  
fffff800`04706388 fffff800`02f448e2 : 00000000`0000009f 00000000`00000003 fffffa80`0d99d980 fffff800`047063d8 : nt!KeBugCheckEx
fffff800`04706390 fffff800`02edeb3c : fffff800`047064c0 fffff800`047064c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x336b0
fffff800`04706430 fffff800`02ede9d6 : fffff800`03086140 00000000`00c2a48e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`047064a0 fffff800`02ede8be : 000001cf`53374f3b fffff800`04706b18 00000000`00c2a48e fffff800`03054448 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04706af0 fffff800`02ede6a7 : 00000079`dd9484c1 00000079`00c2a48e 00000079`dd9484d7 00000000`0000008e : nt!KiTimerExpiration+0x1be
fffff800`04706b90 fffff800`02ecbb8a : fffff800`03050e80 fffff800`0305ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04706c40 00000000`00000000 : fffff800`04707000 fffff800`04701000 fffff800`04706c00 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
---------
}}}",microwheels
14048,Error Starting Virtual Machine (was Previously Working),Linux,Windows,VirtualBox 4.3.26,2015-04-14T08:04:19Z,2015-04-14T08:04:19Z,"Hi,

I initially installed the VirtualBox-4.3.20-96997-Win in January this year. It was working fine for about a month, the period I was using it.

However, today, after a gap of about 2 months when I again wanted to use it, it refused to open and flashed the error message mentioned below. I read somewhere that reinstalling helps in solving this problem and so I did exactly that by first using the same version and when that didn't work I downloaded the recent version (VirtualBox-4.3.26-98988-Win) and installed it. However it too is displaying the same message now.

Can someone help me in solving this problem?

'''System OS''': Windows Vista SP1[[BR]]
'''Firewall/Antivirus''': Yes (Windows/Avira respectively)[[BR]]
'''OS to run in VM''': Ubuntu[[BR]]

[[BR]]

'''Error Message'''


{{{
    Failed to open a session for the virtual machine CS50 Appliance 2014.

    The virtual machine 'CS50 Appliance 2014' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Viper\VirtualBox VMs\CS50 Appliance 2014\Logs\VBoxStartup.log'.

    Result Code: E_FAIL (0x80004005)
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


}}}


Log files attached in zip format.
",freeman00in
14049,VirtualBox NAT implementation tcp keep-alive problem,Windows,Linux,VirtualBox 4.3.10,2015-04-15T13:25:24Z,2015-04-15T13:25:24Z,"Guests behind VirtualBox NAT have problem using TCP keepalive.
When connection with remote is lost (i.e. even host OS reports no connection), VirtualBox NAT implementation continues to reply to guest OS keepalive requests, hence guest cannot detect TCP connection loss.[[BR]]

Encountered on:
Host OS: Windows 7 Professional 64
VirtualBox 4.3.10
Guest OS: Ubuntu 12.04 32

The same problem was reported by two users on the forum: https://forums.virtualbox.org/viewtopic.php?f=7&t=52384
",Aegis
14050,Bugcheck (BSOD) 0x0000009f (0x00000003) on wakeup with InstantGo,Windows,Windows,VirtualBox 4.3.26,2015-04-15T19:43:46Z,2015-04-15T19:43:46Z,"Hi, 
After installing the latest stable x86 version on a Z3735 tablet with Windows 8.1,
I experience recurring bluescreens/reboots when the machine is trying to wake up. Since this Atom class CPU is setup with InstantGo/Connected standby, I suspect that this may be the root cause.

The bugcheck and event log entries point to a problem reinitializing the virtual network adapter on wakeup.

I tried uninstalling Virtualbox and after that,the crashes did not appear anymore.

Device: Pipo W5
CPU: Intel Z3735
RAM: 2 GB
OS: Windows 8.1 x86

",andersl
13676,Guest windows is squeezed to small size if user32.dll has been altered on a host,Windows,all,VirtualBox 4.3.20,2015-04-18T09:30:31Z,2015-04-18T09:30:31Z,"If user32.dll has been altered on a host (some software installation) and is not signed anymore, since 4.3.16 (or 4.3.14) all guests start with a window squeezed to a smallest possible size. VMs start and run normally, just the window always auto-resize to a smallest size. Not happening with 4.3.12 version.

related error in the logs:
00:00:01.122572 supR3HardenedErrorV: supR3HardenedScreenImage/Imports: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=32 \Device\HarddiskVolume7\Windows\System32\user32.dll

discussion on the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",wroot
14057,CPU spikes when concurrently using an XP VM and its complete clone on Debian,Linux,Windows,VirtualBox 4.3.26,2015-04-18T11:11:53Z,2015-04-18T11:11:53Z,"Host Linux sandy 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux
Virtualbox 4.3.26-98988 (happened also with 4.2.28-97679)

I have an XP virtual machine with a test installation of oracle rdbms. To do some speed optimizations on some plsql code and compare results, I cloned it (complete) and changed name, mac and ip.

When one vm is running and idling and I launch the other one, both the machines go to 200% cpu consumption (quad core host). After a (long) while the second machine boot completes, and they both go back to idling.

When I log in on the second vm, the first starts spinning again. After a while the login is completed and both go back to idle.

Whatever I try to do on one of the two, the other one immediately starts using all the available cpu, 50/50 with the first one.

Both the original vm and the clone run perfectly on their own, if the other one is shut down or even paused. If I run another unrelated XP guest with one of the two, the issue does not appear.

I'm using vboxheadless and connecting with Remote Display, but this can be triggered also when not connected to the desktop, e.g. launching a plsql cpu consuming loop via sqldeveloper (not i/o bound operations).

Typical output of top when the issue is occurring

top - 12:59:39 up 7 days, 15:02,  1 user,  load average: 3,34, 5,32, 5,05
Tasks: 192 total,   2 running, 190 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1,5 us, 98,4 sy,  0,0 ni,  0,1 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem:  12280376 total, 12063944 used,   216432 free,    68776 buffers
KiB Swap:  7771064 total,        0 used,  7771064 free,  2834160 cache

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
14613 vbox      20   0 4003m 3,6g 3,6g S 198,0 30,9  36:11.00 VBoxHeadless                
 9930 vbox      20   0 3981m 3,6g 3,6g S 196,0 30,9  40:37.10 VBoxHeadless

",ctrl
13620,Inconsistent screen redraw when scrolling in Chromium,Windows,Linux,VirtualBox 4.3.18,2015-04-20T08:57:20Z,2015-04-20T08:57:20Z,"When I scroll in Chromium, I get inconsistent screen redraws.

Attached is a PNG that demonstrates the problem. In that case, I scrolled up some. Notice how the banner image shows three times.

Occasionally, when I switch between tabs, portions of both tabs will be interleaved in horizontal stripes.

I can usually fix an inconsistent screen redraw if I take the Chromium window and move it around.

This seems to have started with a 14.04 guest when I upgraded VirtualBox and the guest extensions in September or October. I cannot remember the exact timeline. I installed a fresh copy of 14.10 yesterday (that's where the PNG comes from), and the same problem is happening.

I have 3D acceleration enabled and 128MB video memory. Host is Windows 8.1 x64.

I've also attached console warnings that appear when starting Chromium from the terminal window.",Aren Cambre
14060,Mouse disappears when over active window when typing in WinXP Guest,Windows,Windows,VirtualBox 4.3.26,2015-04-20T15:44:58Z,2015-04-20T15:44:58Z,"Using a windows 7 pro host running virtualbox 4.3.26 running a windows xp guest os in fullscreen mode. Due to an antiquated management system, resolution on the monitor being used for virtualbox is 800x600, though I don't think this matters. To replicate the problem, open notepad (or any program really), position the mouse over the notepad window and start typing. the mouse dissapears until you move it. Now move the mouse outside the notepad window and type - the mouse remains visible the entire time. I've reproduced on multiple computers, hosts, guests, and monitors. To me this is trivial, but to several users this is major as they ""lose"" the mouse and have to ""refind"" it all day long.",Keebs
14061,VBoxManage CLI Support for configuring DNS server settings of the VirtualBox Host-Only Network adapters,all,Linux,VirtualBox 4.3.26,2015-04-20T16:51:28Z,2015-04-20T16:51:28Z,"Currently, when I create a VirtualBox Host-Only Network adapter, the DNS settings are essentially empty. (See {{{VirtualBox Host-Only Network #3}}} below). For Windows hosts, one would have to manually follow the steps [http://windows.microsoft.com/en-us/windows/change-tcp-ip-settings#1TC=windows-7 described here] in order to configure this adapter to point to a DNS server (See {{{VirtualBox Host-Only Network #2}}}).

Functionality should be added to the network provisioning portion of the VBoxManage CLI which facilitates creating a network adapter with a DNS server. Without this functionality, the automatic provisioning of nameservers inside VirtualBox guest machines is not possible.

{{{
Ethernet adapter VirtualBox Host-Only Network #2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
   Physical Address. . . . . . . . . : 08-00-27-00-98-93
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.99.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.99.103
   NetBIOS over Tcpip. . . . . . . . : Enabled
}}}

{{{
Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #3
   Physical Address. . . . . . . . . : 08-00-27-00-68-27
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.86.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled
}}}",PhilG
13104,Network issues on OS X 10.10 Yosemite,Mac OS X,Linux,VirtualBox 4.3.12,2015-04-21T05:39:58Z,2015-04-21T05:39:58Z,"I'm having trouble with guest network connectivity with Virtualbox 4.3.12r93733 running on OS X 10.10 Yosemite build 14A238x. There seem to be two issues with a Ubuntu Trusty VM i created using vagrant:

- Network connections (e.g. ssh sessions) to the VM keep hanging for 1-2min. When typing in ssh sometimes the shell is unresponsive for a couple of minutes.
- Network connections from the VM to the internet fail often (~50% ping drop), also this problem happens: http://stackoverflow.com/questions/24060099/docker-failed-to-pull-images-from-registry

I've tried: Restarting host / guest, recreating the VM, playing around with network settings (although I don't know much about that).

Let me know if you need any more details, I'm happy to help anyway I can.",lclemente
14063,"Guest VM hangs if ""Exit full screen"" is clicked while saving state",other,Windows,VirtualBox 4.3.26,2015-04-21T12:17:21Z,2015-04-21T12:17:21Z,"Steps to reproduce:  

* Have a running Windows guest (I couldn't reproduce it with Linux)  
* Press Close -> choose to save state  
* While saving state mini-window is up, press ""Exit full screen""

Result is that guest VM is stuck in ""Saving"" state indefinitely and with unresponsive GUI, the only way I could abort it is kill -9, after which it goes to ""Aborted"" state. I can alt-tab out of VM to my host WM (openbox on ArchLinux).",Alex110101
14066,CopyTo subcommand complains Source Folder does not exist,Windows,Windows,VirtualBox 4.3.26,2015-04-21T14:44:09Z,2015-04-21T14:44:09Z,"VirtualBox Version : 4.3.26 r98988
Host Machine : Windows7 x64 Bit
Guest Machine : Windows7 x64 Bit

Expected Result
=================
valid source Folder from Host gets copied to valid Guest Host recursively

Command
=========
VBoxManage.exe guestcontrol  ""PerfTest_Windows7x64_1-"" copyto F:\VMBOX-Stuff\d\  D:\  --username admin --password  pass, --recursive --verbose


Actual Result
=============
Opening guest session as user 'admin' ...
Waiting for guest session to start ...
Guest session (ID 1) has been started
Copying from host to guest ...
Directory ""D:\"" already exists
Source: F:\VMBOX-Stuff\dummyFolder
Closing guest session ...
VBoxManage.exe: error: Warning: Source ""F:\VMBOX-Stuff\dummyFolder"" does not exist, skipping!

However for a File from the same folder gets successfulyl copied

arg : [VBoxManage.exe, guestcontrol, ""PerfTest_Windows7x64_1-"", copyto, F:\VMBOX-Stuff\dummyFolder\abc.txt, D:\abc.txt, --username, admin, --password, pass, --recursive, --verbose]

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Opening guest session as user 'xpadmin' ...
Waiting for guest session to start ...
Guest session (ID 1) has been started
Copying from host to guest ...
Directory ""D:\"" already exists
Source: F:\VMBOX-Stuff\dummyFolder\abc.txt
Copying ""F:\VMBOX-Stuff\dummyFolder\abc.txt"" to ""D:\abc.txt"" ...
Closing guest session ...

",vazudew
14044,Crash Virtualbox on Windows 8.1,Windows,all,VirtualBox 4.3.26,2015-04-21T18:43:49Z,2015-04-21T18:43:49Z,"Hello. 

Virtualbox Crash when i use file explore (in import application, import vdi...). 

Virtualbox end to tun. I use virtualbox 4.3..26.

Regards",bernalau
14064,Virtual Machine fails to start from a saved state or restored snapshot at 97% progress,Mac OS X,Windows,VirtualBox 4.3.26,2015-04-21T19:06:53Z,2015-04-21T19:06:53Z,"Cannot start a VM from a saved state or from a restored snapshot with the same error:
----------------------------------------------------------------------------------------------------------------------
Failed to open a session for the virtual machine Windows8.1.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
------------------------------------------------------------------------------------------------------------------------
Host OS: Linux Ubuntu 14.10
Virtual box version: 4.3.26r98988
Guest OS: Windows 8.1 64 bit
Laptop: System 76
-----------------------------------------------------------------------
Configuration file to be renamed to Windows8.1.vbox and the log file are attached.
-----------------------------------------------------------------------

Export to .vmdk and import back both work. I can start the imported VM. 
But cannot started it from a saved state or a snapshot as well: so both VMs 
1. Original .vbox + .vdi
2. Exported to and imported back from a .vmdk
can't be started from a saved state or restored snapshot.
",mduberstein
14068,Getting an error code when I try to start virtual machines.,other,Windows,VirtualBox 4.3.26,2015-04-22T06:16:05Z,2015-04-22T06:16:05Z,"Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE)

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Console
Interface: 
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

Is there anything that can be done or anything additional I need to install for this? I'm using Linux Mint.",Heidi Hecht
14072,Win 8 host.  Cannot change Linux guest priority using Windows taskmgr.exe,Windows,Linux,VirtualBox 4.3.26,2015-04-22T19:11:30Z,2015-04-22T19:11:30Z,"I am running Windows 8.1 using VBox 4.3.26 and a couple of Fedora 21 based Linux guests on a 4 core i7 computer with 16 GB of memory.  I would like to be able to set priority or change affinities of the Linux guests but I receive a message from Windows that access is denied.
I tried running taskmgr from an administrative command prompt without success.  Note that I am a Windows administrator as well.
I am able to set priorities or change affinities for other Windows processes but not for the Linux guests.  I even ran Tails, an ISO based TOR Linux implementation, guest as well and could not change its priorities or affinities either. 
To be clear I want to change the Windows priorities for the Linux guests and not priorities inside the Linux guest.  Likewise I want to limit a 2 core guest to certain cores on my i7.
",TKVbox
14073,vbox doesn't know how to use my kernel signature to sign its modules,other,other,VirtualBox 4.3.26,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
14079,The Application failed to initialize properly (0xc000007b),Windows,Windows,VirtualBox 4.3.26,2015-04-27T07:35:35Z,2015-04-27T07:35:35Z,"i recently updated the virtualbox from 4.3.18 to 4.3.26
and suddenly i cannot start the virtualbox, error show the application failed to initialized properly (0xc000007b)
how can i repair this, i already use the sfc /scannow on command prompt, uninstall the .net framework (2.0, 3.0, 3.5)
fyi my OS was windows xp SP3 and before the update my virtualbox was running smoothly.
",Handi
12312,Rendering in Civilization IV is broken on Windows 8 guests,Linux,Windows,VirtualBox 4.3.2,2015-04-27T19:02:14Z,2015-04-27T19:02:14Z,"Hi,

I've noticed that rendering within game Civilization IV (or its spin-off Colonization) is fully broken, with a black screen instead of anything else.

Steps to reproduce :
DO : start a Civ IV game
EXPECT : the map is properly displayed
ACTUAL : rendering is broken (almost everything black). Playing with details does not change anything.

My hardware
Ubuntu Saucy AMD64
AMD Phenom x4 9850
8 GB RAM
NVidia GeForce 660Ti w/ 2 GB RAM

VM : Windows 8 32 bits",gojul
9166,vboxnet0 doesn't count traffic correctly (Linux host),Linux,Windows,VirtualBox 4.0.10,2015-04-28T04:17:29Z,2015-04-28T04:17:29Z,"On a Linux box with VirtualBox 4.0.10 installed and with a Windows XP virtual machine with default settings.

'''ifconfig vboxnet0''' does not show the reality :

{{{
[root@fedora15 ~]# ifconfig vboxnet0
vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00
          inet adr:192.168.56.1  Bcast:192.168.56.255  Masque:255.255.255.0
          adr inet6: fe80::800:27ff:fe00:0/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:0 (0.0 b)  TX bytes:274935 (268.4 KiB)
}}}

I've transferred much more than 268.4 KiB and obviously received some data.

Problem can also be seen with ""tcpdump"" which shows traffic only in one direction and ""bwm-ng"" which doesn't show any traffic at all.

This ticket is related to this post http://forums.virtualbox.org/viewtopic.php?f=7&t=38499 and to a conversation I've had on IRC where I've been told to fill in a bug report.

The Linux host is a Fedora 15 up to date (07/07/2011).
Windows VM is also up to date.
",a_i_
13744,Windows 7 guest can't connect to the Internet - host Wifi/guest bridged network adapter,Linux,Windows,VirtualBox 4.3.20,2015-04-28T05:00:39Z,2015-04-28T05:00:39Z,"Virtualbox: 4.3.20
Hosts: Ubuntu 14.04, 14.10, 15.04
Guest: Windows 7 Pro; network adapter: Tested all, including Virtio
VM Network connection: Bridged

I have a Windows 7 guest (VM) installed in VirtualBox host running Ubuntu 14.04. Other users have experienced this in hosts running Ubuntu 14.10 and 15.04 too. 

This is on a laptop so I have two networking adapters. 

The VM's internet access works fine if I activate the ethernet adapter on the host, regardless of the VM's NAT or Bridged connection type. 

When the host's active Internet connection is Wireless then the VM's internet access only works in NAT mode.  In bridged mode, the guest obtains an IP address, but can’t connect to the Internet.

I need to use the Bridged connection type in order to participate in the LAN's native IP network, not a host's NAT network. Thanks for any help in advance.

Similar bug tickets:
#12408
#11254
",Pedro Serrano
13785,OS X Guest with Bridged Networking cannot obtain DHCP lease - guest actively DHCPDECLINEs due to host activity,other,Linux,VirtualBox 4.3.20,2015-04-28T05:04:29Z,2015-04-28T05:04:29Z,"Host: OS X Yosemite 10.10.1
VirtualBox: 4.3.20
Guest: CentOS 6.4

I have configured an OS X VirtualBox guest with a primary interface as NAT, a private network secondary, and a tertiary interface as Bridge Networking with DHCP. I have bridged to my Airport Wi-Fi adapter.

When the machine boots it nearly always fails to obtain an IP address for the bridged interface. In rare cases it will actually succeed. Retrying it will eventually work though rarely (run it 100 times in a loop maybe.)

Running dhclient -v eth2 shows the guest is declining the IP offer when it fails:
{{{
[root@localhost ~]# dhclient -v eth2
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5 (xid=0x2bc89bf5)
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
DHCPACK from 192.168.0.1 (xid=0x2bc89bf5)
DHCPDECLINE on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
}}}
This seems to be because it sees the IP as already existing - though it doesn't. I modified /sbin/dhclient-script to show the arping output like this:
{{{
        arping -D -c2 -I ${interface} ${new_ip_address}
        RC=$?
        echo ""Exit: $RC""
        [ $RC -ne 0 ] && exit_with_hooks 1
}}}
Interestingly, if I didn't exit and let it run its own arping afterwards - it would always succeed. More on that shortly.

Output is below:
{{{
[root@localhost ~]# dhclient -v eth2
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5 (xid=0x2bc89bf5)
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
DHCPACK from 192.168.0.1 (xid=0x2bc89bf5)
ARPING 192.168.0.149 from 0.0.0.0 eth2
Broadcast request from 192.168.0.149 [HI:DD:EN:HI:DD:EN] for 192.168.0.1 [00:00:00:00:00:00] 1.163ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s) (1 request(s), 1 broadcast(s))
Exit: 1
DHCPDECLINE on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
}}}
Arping detects a broadcast request coming from the IP it just allocated... the Mac address there is the HOST's MAC address. So something on the host sends this request from the allocated IP, and arping here catches it and fails duplicate address detection, meaning dhclient declines the address.

Weirdly, if I precede the dhclient-script arp check with a sleep 2 instead of the debug lines above - it never works. Replace it with just a single arping command, it works every time. Seems something is happening on the host in response to the FIRST arp check. So the first fails, and the second arp check succeeds (though normally there is only one check - it's just in my debugging I stumbled on it.)

Any ideas what is causing this request from the host? Is it a VirtualBox thing or a OS X thing? Any possible fix?",Jason Woods
14092,Ufter upgrade from 4.1.12 to 4.3.26 stops to run VM from PhysicalDrive,Windows,all,VirtualBox 4.3.26,2015-05-02T08:38:16Z,2015-05-02T08:38:16Z,"subj

I had working system, ufter upgrade that stopping to work. No config is changed. Logs and configurations attached",KES
14084,Sketch feature.,all,all,VirtualBox 4.3.26,2015-05-04T07:51:02Z,2015-05-04T07:51:02Z,"I would like to propose a group of new features. I would have ability to create a new machine simply and fast from created earlier sketch. In my opinion the best solution is give ability to create compete scratch with disk image. Afterwards we can create new machine from scratch with checkbox ""use blank disk"" to give user ability to create blank machines with same settings. ",xearo
9586,Seamless Mode cuts out Drop-Down boxes where options are not inside Window/Dialog,Windows,Windows,VirtualBox 4.1.2,2015-05-05T18:22:42Z,2015-05-05T18:22:42Z,"If you drop-down a combo boc and the list of options full-out of the active window in Seamless Mode, you cannot see them. I have upgraded from 3.1.8 to 4.1.2 and never saw this issue in 3.1.8. The guest PC is a clean build of Windows XP with 4.1.2 tools installed.

See picture which shows the issue.",stewaj03
14097,I can not connect the drive to Virtualbox.,Windows,Windows,VirtualBox 4.3.26,2015-05-06T13:08:09Z,2015-05-06T13:08:09Z,"Не удалось открыть файл виртуального жёсткого диска E:\arut-minimal.vdi.

After transferring from one resource to another error occurred.

Could not get the storage format of the medium 'E:\arut-minimal.vdi' (VERR_NOT_SUPPORTED).
{{{
Код ошибки: VBOX_E_IPRT_ERROR (0x80BB0005)
Компонент: Medium
Интерфейс: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Вызванный интерфейс: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Код ошибки метода: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}
I tried using vboxmanage for repair.
{{{
c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -dry-run -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbo
x\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)

c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbox\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)
}}}",Speltor
14098,Automated kernel modules recompilation,Linux,Windows,VirtualBox 4.3.26,2015-05-07T11:33:06Z,2015-05-07T11:33:06Z,"Whenever the host OS is updated (in my case Ubuntu), VirtualBox is not able to start my VM and brings up a weird error. A popup then appears prompting me to do `sudo /etc/init.d/vboxdrv setup`

If VirtualBox knows that this is needed, why doesn't it just do it itself? Maybe just showing a prompt with a more user-friendly message saying 'VirtualBox needs to recompile its kernel modules, probably due to a recent OS system update. Confirm?' and the user just presses OK and its done automatically?

At the moment this process is really annoying:
1. You have to copy the command to run from the message box.
2. You have to open a terminal window and paste it but NOT press enter, since Virtual Box is still running. If on the other hand you close Virtual Box before pasting the clipboard info is lost.
3. Close VirtualBox
4. Press enter, wait for Kernel module recompilation.
5. Start VirtualBox.

This could immensely be simplified from a user point of view if when the message is shown and the user confirms, VirtualBox automatically closes, recompiles the kernel modules and restarts.



",jbx
14077,Crash with RDR_FILE_SYSTEM in Windows 7,Linux,Windows,VirtualBox 4.3.26,2015-05-10T07:46:01Z,2015-05-10T07:46:01Z,"I already read:

* https://www.virtualbox.org/ticket/57
* https://www.virtualbox.org/ticket/1683
* https://www.virtualbox.org/ticket/991

and all those tickets were created 7 years ago or even sooner, they are all closed as FIXED, and yet, for 2-3 months I see my guest Windows 7 crashes with RDR_FILE_SYSTEM constantly. The uptime can be around 2-3 days max.

I saw this with 4.3.22, after upgrade to 4.3.26 I still see this crash.

Host: openSUSE 13.2 64-bit, Windows 7 64-bit, using shared folders which are mapped as network drive in guest. Activity in guest: Visual Studio, Free Commander, Notepad++, Cygwin. Crashes occurs during user activity (for example when I am saving a file) or on idle (during night for example).",thxOracle
14106,vboxdrv initscript $SHUTDOWN fix,Linux,all,VirtualBox 4.3.26,2015-05-11T12:23:28Z,2015-05-11T12:23:28Z,"I experienced issues when shutting down VM's with the provided init scripts especially if they are not subject to the autostart service when setting the variable $SHUTDOWN_USERS as documented in /etc/init.d/vboxdrv:
Either VboxXPCOMIPCD is not running any more and gives me error messages or the kernel modules cannot be unloaded properly because VboxXPCOMIPCD is still running when using
{{{
 service vboxdrv stop
}}}
.

So I've done the following to /etc/init.d/vboxdrv:
* checking whether VboxXPIPCD ist still alive before trying to determine the status of running vms or trying to unload the kernel modules in stop_vms() and dmnstatus()
* enhancing the way the script waits for an ACPI shutdown with a configurable $SHUTDOWN_ACPI_TIMEOUT in stop_vms()
* provide a failover method $SHUTDOWN_ACPI_ACTION_FAILURE if ACPI shutdown is not successful (poweroff or savestate) in stop_vms()



{{{
254a255,278
> # the following is optional:
> #   SHUTDOWN_ACPI_TIMEOUT
> #     how long to wait for acpi shutdown of all vms
> #   SHUTDOWN_ACPI_ACTION_FAILURE=poweroff
> #   SHUTDOWN_ACPI_ACTION_FAILURE=savestate
> #     select failure action rather than terminating,
> #     defaults to poweroff
> 
> poweroff_vms() {
>     begin_msg ""Powering off remaining VMs""
>     for v in $1; do
>         $VBOXMANAGE --nologo controlvm $v poweroff
>     done
>     succ_msg
> }
> 
> savestate_vms() {
>     begin_msg ""Powering off remaining VMs""
>     for v in $1; do
>         $VBOXMANAGE --nologo controlvm $v savestate
>     done
>     succ_msg
> }
> 
258,282c282,323
<     for i in $SHUTDOWN_USERS; do
<         # don't create the ipcd directory with wrong permissions!
<         if [ -d /tmp/.vbox-$i-ipc ]; then
<             export VBOX_IPC_SOCKETID=""$i""
<             VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
<             if [ -n ""$VMS"" ]; then
<                 if [ ""$SHUTDOWN"" = ""poweroff"" ]; then
<                     begin_msg ""Powering off remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v poweroff
<                     done
<                     succ_msg
<                 elif [ ""$SHUTDOWN"" = ""acpibutton"" ]; then
<                     begin_msg ""Sending ACPI power button event to remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v acpipowerbutton
<                         wait=30
<                     done
<                     succ_msg
<                 elif [ ""$SHUTDOWN"" = ""savestate"" ]; then
<                     begin_msg ""Saving state of remaining VMs""
<                     for v in $VMS; do
<                         $VBOXMANAGE --nologo controlvm $v savestate
<                     done
<                     succ_msg
---
>     #see whether we can contact ipcd to avoid error message
>     if pgrep VBoxXPCOMIPCD>/dev/null; then
>         for i in $SHUTDOWN_USERS; do
>             # don't create the ipcd directory with wrong permissions!
>             if [ -d /tmp/.vbox-$i-ipc ]; then
>                 export VBOX_IPC_SOCKETID=""$i""
>                 VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                 if [ -n ""$VMS"" ]; then
>                     if [ ""$SHUTDOWN"" = ""poweroff"" ]; then
>                         poweroff_vms $VMS
>                     elif [ ""$SHUTDOWN"" = ""acpibutton"" ]; then
>                         begin_msg ""Sending ACPI power button event to remaining VMs""
>                         for v in $VMS; do
>                             $VBOXMANAGE --nologo controlvm $v acpipowerbutton
>                         done
>                         succ_msg
>                         if [ -n ""$SHUTDOWN_ACPI_TIMEOUT"" ];then
>                             wait=$SHUTDOWN_ACPI_TIMEOUT
>                         else
>                             wait=30
>                         fi
>                         begin_msg ""Waiting for $wait seconds for VM shutdown""
>                         c=0
>                         while [ -n ""`$VBOXMANAGE --nologo list runningvms`"" ] && [ $c -le $wait ]; do
>                             echo -n '.'
>                             sleep 1
>                             c=$(($c+1))
>                         done
>                         VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                         if [ -n ""$VMS"" ];then
>                             fail_msg
>                             if [ -z ""$SHUTDOWN_ACPI_ACTION_FAILURE"" ] || [ ""$SHUTDOWN_ACPI_ACTION_FAILURE"" = ""poweroff"" ] ;then
>                                 poweroff_vms $VMS
>                             elif [ ""$SHUTDOWN_ACPI_ACTION_FAILURE"" = ""savestate"" ]; then
>                                 savestate $VMS
>                             fi
>                         else
>                             succ_msg
>                         fi
>                     elif [ ""$SHUTDOWN"" = ""savestate"" ]; then
>                         savestate_vms $VMS
>                     fi
284a326,338
>         done
>         begin_msg 'waiting for XPCOMIPCD to stop '
>         timeout=20
>         c=0
>         while pgrep VBoxXPCOMIPCD>/dev/null && [ $c -le $timeout ] ; do
>             echo -n '.'
>             sleep 1
>             c=$(($c+1))
>         done
>         if pgrep VBoxXPCOMIPCD>/dev/null;then
>             fail_msg
>         else
>             succ_msg
286,291d339
<     done
<     # wait for some seconds when doing ACPI shutdown
<     if [ ""$wait"" -ne 0 ]; then
<         begin_msg ""Waiting for $wait seconds for VM shutdown""
<         sleep $wait
<         succ_msg
378,387c426,437
<         for i in $SHUTDOWN_USERS; do
<             # don't create the ipcd directory with wrong permissions!
<             if [ -d /tmp/.vbox-$i-ipc ]; then
<                 export VBOX_IPC_SOCKETID=""$i""
<                 VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
<                 if [ -n ""$VMS"" ]; then
<                     echo ""The following VMs are currently running:""
<                     for v in $VMS; do
<                        echo ""  $v""
<                     done
---
>         if pgrep VBoxXPCOMIPCD>/dev/null; then
>             for i in $SHUTDOWN_USERS; do
>                 # don't create the ipcd directory with wrong permissions!
>                 if [ -d /tmp/.vbox-$i-ipc ]; then
>                     export VBOX_IPC_SOCKETID=""$i""
>                     VMS=`$VBOXMANAGE --nologo list runningvms | sed -e 's/^"".*"".*{\(.*\)}/\1/' 2>/dev/null`
>                     if [ -n ""$VMS"" ]; then
>                         echo ""The following VMs are currently running:""
>                         for v in $VMS; do
>                             echo ""  $v""
>                         done
>                     fi
389,390c439,440
<             fi
<         done
---
>             done
>         fi
}}}

See also https://forums.virtualbox.org/viewtopic.php?f=9&t=67546 for a better formatted diff.",old_man
14110,GUI anomalies on VHD display Windows 8.1,Windows,other,VirtualBox 4.3.26,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
14111,Using SaveState is corrupting disk image when VirtualBox has been opened more than once (by multiple users),other,other,VirtualBox 4.3.26,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
14117,One Linux guest crashes on OS X (10.10.3) host in AioMgr0 or Port0 thread,Mac OS X,Linux,VirtualBox 4.3.26,2015-05-15T09:23:34Z,2015-05-15T09:23:34Z,"Having two VM on same machine with very similar (but not cloned) setup. 

One crashes frequently. Other one just keep going. 

I am seeing two different crashes. Both are attached. I have seem them both with headless and GUI guests-

",Dennis Schafroth
14093,AltGr issue on Windows 8.1 and Windows 7 with Czech keyboard layout,Windows,Linux,VirtualBox 4.3.26,2015-05-15T13:18:34Z,2015-05-15T13:18:34Z,"This is weird issue, as I am not able to reproduce it alltime, but I know, after several hours of running guest it results in this weird issue.

Host: MS Windows 8.1 (64 bit) or Windows 7 (64 bit).
Guest: Debian Wheezy (64 bit) or Debian Jessie (64 bit).
Guests addons installed from Debian's contrib repository.

AltGr-a (~) is not working, when host keyboard layout is Czech, but works if keyboard layout is English USA. All other AltGr combinations (I use) work fine.

I have already investigated it using {{{xev}}}, I can see keystroke {{{ISO_Level3_Shift}}}, but no {{{a}}} keystroke, but for example AltGr-q (\) I can see both keystrokes.

Auto capture is disabled. When auto capture is enabled it works as expected, but it is not handy for me.

I see similar fixed issue #13216.

Offtopic: Is it possible to create Extension Pack, that will not capture several key combinations, so for example ctrl-alt-(anything) will not be captured even if auto capture feature is enabled?",xdml
14120,unable to startvm with high priority on windows,Windows,Linux,VirtualBox 4.3.26,2015-05-15T14:39:58Z,2015-05-15T14:39:58Z,"Reference forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=67715#p320669

I recently upgraded to 4.3.26 and now I'm unable to run my batch file that launched my VM with high priority because it seems that there are now 3 different processes that end up getting run. The parent process has the high priority but the actual VM does not which makes it slow. Here is the batch file, not much to it. Anyone found a workaround for this, or should I report it as a bug? 

Batch File contents:
start ""name"" /high ""C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"" --comment name --startvm 1941c965-3dc5-4326-85ae-4400ea58b90d

Things that I've tried without any success:
- running the batch file as admin
- setting VirtualBox.exe to always run as Admin",p1234
14121,VirtualBox 4.3.28 auf Windows Server 2012 Datacenter - kein VM-Start mehr nach Windows-Updates,Windows,Windows,VirtualBox 4.3.28,2015-05-15T15:27:10Z,2015-05-15T15:27:10Z,"I have updated VirtualBox from 4.3.20 to 4.3.26 and later to 4.3.28.
The operating system is Windows Server 2012 Datacenter (German).
When I install all current Windows updates, my
VM (Windows Server 2008 R2 German with all Windows updates) does
not start.

The error after installing VirtualBox 4.3.28 is:
Die Anweisung in 0xe3ff0ab1 verweist auf Speicher 0x041af0bd. Der
Vorgang read konnte nicht im Speicher durchgeführt werden.
Klicken Sie auf ""OK"", um das Programm zu beenden.

",clearth
14119,3d graphics window closes the program menu.,Linux,Windows,VirtualBox 4.3.28,2015-05-15T16:08:20Z,2015-05-15T16:08:20Z,The three-dimensional programs running in windowed mode menu under the window are 3D graphics. Attached a screenshot. This is evident when the mode switches on 3D acceleration in VirtualBoх.,3DRaven
10852,Automatic integer-factor scaling under full-screen mode,other,other,VirtualBox 4.1.20,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
14127,No bridged network adapter is currently selected,Windows,other,VirtualBox 4.3.26,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
14129,No Internet Connection under Host Only / NAT: DHCP,Mac OS X,Linux,VirtualBox 4.3.28,2015-05-17T18:08:32Z,2015-05-17T18:08:32Z,"Hello Guys,

I am currently using VirtualBox 4.3.28 r100309 on Mac OS X Yosemite 10.10.3. My guest OS is Ubuntu Server 14.04.2.

I setup two network interfaces: Adapter 1 ""NAT"" and Adapter 2 ""Host-only"". Thus, the machine should have access to the internet (NAT) and I should have access to the virtual machine from my Mac without port forwarding (Host-only).

In the previous versions of VirtualBox I had not that problem, but right now I cannot access to internet through my guest machine. If I set just one network interface using the Bridged Adapter I can access to internet in my guest machine, but I want to use an static ip due to I do not want my ip address changes everytime I change my network in the host machine, like when I change the wifi for example.

Can someone help me please?",vihuvac
14130,Creating a VB on Windows 7-32bit for Windows 8-32bit,Windows,Windows,VirtualBox 4.3.28,2015-05-18T06:33:45Z,2015-05-18T06:33:45Z,"Tried to run a VB Windows 8.1 (32 bit) on my Windows 7.  

Encountered the following errors:

1.  Failed to create the VirtualBox COM object.
    The application will now terminate.
    Callee RC: E_INVALIDARG (0x80070057)

2.  Failed to open a session for the virtual machine Windows 8.
    The virtual machine 'Windows 8' has terminated unexpectedly during 
    startup with exit code 1 (0x1).  More details may be available in   
    'C:\Users\c3p0i\VirtualBox VMs\Windows 8\Logs\VBoxStartup.log'.

    Result Code: E_FAIL (0x80004005)
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I have attached the *.log with this ticket.

Thanks and Regards.",c3p0i
14123,X11 additions: no EDID detection any more,Windows,X11,VirtualBox 4.3.28,2015-05-18T12:54:34Z,2015-05-18T12:54:34Z,"With release 4.3.28 the X11 additions have rendered EDID detection dysfunctional. As a result, Xorg comes up with the default resolution of 1024x768 instead of sizing according to the (virtual) screen size.

Attached is a unified diff of Xorg.0.log, comparing 4.3.26 and 4.3.28 guest additions. xorg.conf is identical.",hmo
13939,Errort when pressing right mouse buttion in CD/DVD device selection dialog,Windows,all,VirtualBox 4.3.24,2015-05-18T13:11:02Z,2015-05-18T13:11:02Z,"When the CD/DVD Device selection dialog is shown and you press the right mouse button to bring up a popup menu the guest aborts with a C++ runtime error.

Host Windows Server 2003 x64 / Windows XP64

Also occurs with latest test build. 

Other than the termination dialog window no error in event log or elsewhere can be found.

FRG",frg
14133,"After update, the windows taskbar icon is wrong",other,other,VirtualBox 4.3.28,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
13962,"VBoxClient: Failed to set graphics capability, rc=VERR_NOT_SUPPORTED",Windows,Linux,VirtualBox 4.3.26,2015-05-19T09:30:15Z,2015-05-19T09:30:15Z,"Host is Windows 7 Pro 64-bit; guest is openSUSE 13.2 32-bit. Previously functioning correctly with this host and this VM. VM display is no longer using custom dimensions, but preset 4:3-aspect dimensions seem to work. Upon logging in to account in guest OS, I receive the following two errors:

* vBoxClient: Failed to set graphics capability, rc=VERR_NOT_SUPPORTED
* vBoxClient: Initialising service: VERR_NOT_SUPPORTED

The background on this is that I was running VirtualBox 4.3.20 (I think) until this morning. After being prompted about a new version (4.3.24) I decided to upgrade, including updating the Guest Additions. (Oops.) If I remember right, this problem appeared on the first boot after the Guest Additions upgrade. I then tried 4.3.25 (not seeing that .26 was already available), with the matching(?) Guest Additions, and the behavior was the same. I then installed 4.3.26 and the matching Guest Additions, and the behavior is still the same.

While I can use preset sizes, they are all 4:3 and are either significantly smaller than what I want to use or are too large vertically, imposing scrolling (not ideal).

I'm assuming the 'component' is 'guest additions' but I'm not sure that's correct.",Crenel
10908,vboxnet host side MAC address should be configurable,Mac OS X,all,VirtualBox 4.1.22,2015-05-19T16:45:30Z,2015-05-19T16:45:30Z,"Host side MAC address  of hostonlyifs, vboxnetX, are statically assigned 0a:00:27:00:00:X, where 0 <= X <= 127, which is good for the what it was designed for.

However, in certain applications of the virtualbox, these MAC addresses are announced to the external network as station behind L2 bridges. IEEE802.11s mesh networking protocol is an example of such application. In such cases, likelihood of MAC address collision is extremely large under the current assignment scheme. It should be fixed so that lower 3 octets could be configurable (just like the guest side of the interface).",shinoda
7040,"Windows 7 host, VBox 3.2.4 cannot do bridged networking",Windows,Windows,VirtualBox 3.2.4,2015-05-19T17:18:58Z,2015-05-19T17:18:58Z,"Upgraded from 3.1.4 to 3.2.4 on a Windows 7 Ultimate 64-bit host

Existing VMs would not start (E_FAIL). Checking the settings highlighted a problem with the network adapter.

The VMs all use bridged networking. The dropdown for the host network adapter to bridge was empty, and nothing could be selected.

Tried creating a new VM in 3.2.4, same problem - can't set network adapter to bridged networking, because I can't select a host adapter to bridge.

Downgrade to 3.1.8 - everything works as before.
",Mike Benson
2760,Feature request: direct tun/tap support not available since 2.1.0,Linux,other,VirtualBox 2.1.0,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
6947,"VBoxSharedClipBoardClass blocks when copying from host.  (XP guest, CentOS host)",Linux,Windows,VirtualBox 3.2.4,2015-05-20T13:56:50Z,2015-05-20T13:56:50Z,"Since several versions ago, I have been experiencing clipboard blocking problems.

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

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

The problem happens at some time, I still cannot reproduce it at will.",afante
14115,4.3.28 installation failed,Windows,other,VirtualBox 4.3.28,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
14141,vb guest additions corrupts win 10 guest,Windows,Windows,VirtualBox 4.3.28,2015-05-22T10:06:54Z,2015-05-22T10:06:54Z,"when attempting to load vb guest additions on a windows 10 64 bit guest with a windows 8.1 64 bit host vitalization enabled guest initially loads fine insert guest additions CD within guest then attempt to run CD clicking through with default settings guest additions will start to load drivers until it gets to the WDDM video driver can take up to a minute to Begin to load this driver then the screen will began to pixalate and artifact and then the screen will go blank and show a black screen with a white or grey box in the middle then VM will freeze the only way to exit is by red X attempts to restart will show widows loading screen then show blank screen again you are forced to force close only fix is to restore to previous snap shot a use VM without guest additions installed
this problem has existed in all versions of virtual box since window 10 tech preview was initially released",bugger
3866,Host-only interface interferes with the current adapter,Windows,other,VirtualBox 2.2.2,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
14146,Windows 7 grant privileges dialoges mess up seamless mode,Linux,Windows,VirtualBox 4.3.18,2015-05-22T19:50:45Z,2015-05-22T19:50:45Z,"On my Debian Jessie Gnome host with Windows 7 as guest it happens quite often that Windows ""grant privileges"" / ""admin permission"" fullscreen dialogs mess up the seamless mode.

When that happens host and guest desktops are kind of frozen and both partially visible. It is not possible to perform mouse clicks on both host and guest then. The only way to come back to a normal state is using the host shutdown key and waiting for the guest to close.

",conceptdeluxe
14152,restoring my snapshot made web pages cannot connect to mysql,Windows,Linux,VirtualBox 4.3.28,2015-05-26T12:52:01Z,2015-05-26T12:52:01Z,"Restoring snapshot made my webpages connection to Ubuntu guest cannot connect to Ubuntu guest mysql anymore

",virtualguys
14157,Removing snapshot fails and leave VM in unbootable state,Windows,Linux,VirtualBox 4.3.28,2015-05-28T11:24:14Z,2015-05-28T11:24:14Z,"The VM had 2 snapshots and was running. I started the removal of the
first snapshot from the GUI.  This removal aborted with an error, and the running VM was somehow stopped (or killed).
Unfortunately, I don't have the error message any longer.

The bigger problem is that the VM was not bootable any longer; I think this is the error message in VBox.log.2:
{{{
00:00:04.189066 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false
}}}

The next attempt to start the VM resulted in an error messag that a required snapshot file was missing (in VBox.1.log):
{{{
00:00:02.948345 AIOMgr: Endpoint for file 'C:\Users\voelkerb\VirtualBox VMs\opensuse13.2\os13.2.vdi' (flags 000c0781) created successfully
00:00:02.983231 VMSetError: F:\tinderbox\win-4.3\src\VBox\Storage\VD.cpp(6370) int __cdecl VDOpen(struct VBOXHDD *,const char *,const char *,unsigned int,struct VDINTERFACE *); rc=VERR_FILE_NOT_FOUND
}}}

Creating a new snapshot in order to preserve the current state failed
with the same message.

The only way out was to revert to the last snapshot - without taking
a snapshot of the current state and thus loosing the work until that
last snapshot. ;-(

After that, the machine was still not bootable, but the media manager
complained about 2 missing differencing images.
After removing that, the VM could be started again, yet some work was
lost.

I experienced the same already 2-3 times in the past.

Host: Windows 7, guest: openSUSE-13.2",berny
13534,Seamless mode on secondary monitor mimics resolution of primary monitor since 4.3.18,Linux,Windows,VirtualBox 4.3.18,2015-05-28T11:52:52Z,2015-05-28T11:52:52Z,"After upgrading from 4.3.16-95972 to 4.3.18 r96516 I'm facing a (for me) severe usage problem with seamless mode in combination with my multi-monitor setup.

=== MY SETUP ===
A laptop (15"" 1600x900) with a large monitor (24"" 1920x1200) as secondary monitor. I would run a Win guest on the large, secondary screen in seamless mode, so my Cinnamon taskbars & menus are on my laptop screen, my Win7 bar is on the bottom of my 2nd monitor.

=== THE PROBLEM ===
As of 4.3.18 the seamless mode mimics the height of the primary monitor (900px) though taking the whole width. Fullscreen mode still works as expected and takes up the whole secondary screen. 

More oddly, in seamless mode the 900px frame is positioned somewhere in the middle of the screen giving my a flying taskbar and VBox Toolbar.

I always faced a problem that the VBox Toolbar menues appears with a vertical offset to the actual toolbar hover (something like 300px below). But I think this is rather a Gtk issue which I can tackle.

Downgrading restored the seamless mode for me.",vBen
14149,Trivial macro bug in SDK in bindings/c/include/VBoxCAPI_v4_3.h,Linux,all,VirtualBox 4.3.28,2015-05-29T15:56:53Z,2015-05-29T15:56:53Z,"The definition for the IVirtualBox_CreateMachine macro is missing the GroupSize parameter. It needs to have the parameter added, and then needs to forward it to CreateMachine.

Without this change, code that uses the macro won't compile.

Here's a diff, in case it helps.

{{{
diff a/bindings/c/include/VBoxCAPI_v4_3.h b/bindings/c/include/VBoxCAPI_v4_3.h
--- a/third_party/VirtualBoxSDK/sdk/bindings/c/include/VBoxCAPI_v4_3.h
+++ b/third_party/VirtualBoxSDK/sdk/bindings/c/include/VBoxCAPI_v4_3.h
@@ -4266,7 +4266,7 @@ struct IVirtualBoxVtbl
 #define IVirtualBox_get_GenericNetworkDrivers(p, aGenericNetworkDrivers) ((p)->lpVtbl->GetGenericNetworkDrivers(p, aGenericNetworkDrivers))
 #define IVirtualBox_GetGenericNetworkDrivers(p, aGenericNetworkDrivers) ((p)->lpVtbl->GetGenericNetworkDrivers(p, aGenericNetworkDrivers))
 #define IVirtualBox_ComposeMachineFilename(p, aName, aGroup, aCreateFlags, aBaseFolder, aFile) ((p)->lpVtbl->ComposeMachineFilename(p, aName, aGroup, aCreateFlags, aBaseFolder, aFile))
-#define IVirtualBox_CreateMachine(p, aSettingsFile, aName, aGroups, aOsTypeId, aFlags, aMachine) ((p)->lpVtbl->CreateMachine(p, aSettingsFile, aName, aGroups, aOsTypeId, aFlags, aMachine))
+#define IVirtualBox_CreateMachine(p, aSettingsFile, aName, aGroupSize, aGroups, aOsTypeId, aFlags, aMachine) ((p)->lpVtbl->CreateMachine(p, aSettingsFile, aName, aGroupSize, aGroups, aOsTypeId, aFlags, aMachine))
 #define IVirtualBox_OpenMachine(p, aSettingsFile, aMachine) ((p)->lpVtbl->OpenMachine(p, aSettingsFile, aMachine))
 #define IVirtualBox_RegisterMachine(p, aMachine) ((p)->lpVtbl->RegisterMachine(p, aMachine))
 #define IVirtualBox_FindMachine(p, aNameOrId, aMachine) ((p)->lpVtbl->FindMachine(p, aNameOrId, aMachine))
}}}",pwnall
10092,Error message when using a normal command which should not give this message,Linux,Linux,VirtualBox 4.1.8,2015-05-29T16:01:19Z,2015-05-29T16:01:19Z,"After giving the command (as root):
{{{
su - vboxuser -c ""/usr/bin/VBoxManage controlvm ""vmname"" acpipowerbutton""
}}}
the following command is given in a loop each second
{{{
su - vboxuser -c ""/usr/bin/VBoxManage -nologo showvminfo ""vmname"" -machinereadable"" | grep -q 'VMState=""poweroff""'
}}}
until this command returns 0 and the loop is ended.
Apparently at the moment the command returns VMState=""poweroff"" the command VBoxManage also gives the following error message:
{{{
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee nsISupports
Context: ""COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))"" at line 1698 of file VBoxManageInfo.cpp
}}}",Freek de Kruijf
14158,Memory Leak on Windows 7 Host VBox  4.3.28 r100309. Host Mem 45%-90% in 3 Hrs.,Windows,Linux,VirtualBox 4.3.28,2015-05-29T17:47:50Z,2015-05-29T17:47:50Z,"Vbox Details
 Version 4.3.28
 Guest Additions 4.3.28.iso
 Operating System: Ubuntu 14.04
 System:
  Base Memory: 3GB
  Processors: 4
  Execution Cap: 95%
  Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX
 Display:
  Video Memory 64 MB
  Screens: 2
  Acceleration: 3D

Host Details:
 Operating System: Windows 7
 RAM: 8GB
 Processors: 8
 
After starting the Virtual Machine VirtualBox.exe Memory(Private Working Set) rises to about 416,416 K. Within 3 hours of working inside the VM It will rise to roughly 2,000,000 K at which point the host alerts me to low memory. If I don't restart the VM eventually it will completely freeze and crash.

Typical Programs running in VM
Firefox
Sublime-Text-2
Terminal
Libre Office Writer/Spreadsheet
File Manager

In the host VirtualBox is typically the only program I'm running. I was wondering if maybe not having Admin permissions on the account I'm using is causing a problem? Although I did give VirtualBox all the rights an admin account has. 
",dduke22
13137,Parent UUID ... of the medium ... does not match UUID... of its parent medium stored in the media registry ...,Linux,Windows,VirtualBox 4.3.10,2015-06-01T07:53:10Z,2015-06-01T07:53:10Z,"I have a virtual hd which reports the following:


{{{
$ VBoxManage showhdinfo b4938314-1204-43f0-8752-767515f71b39
UUID:           b4938314-1204-43f0-8752-767515f71b39
Parent UUID:    9c1d4675-e810-45d6-941d-ba0ced1037ea
State:          inaccessible
Access Error:   Parent UUID {b43a1680-4e28-45a7-80d4-7f43520f54df} of the medium '/u/martin/VirtualBox VMs/Windows XP Professional/Snapshots/{b4938314-1204-43f0-8752-767515f71b39}.vmdk' does not match UUID {9c1d4675-e810-45d6-941d-ba0ced1037ea} of its parent medium stored in the media registry ('/u/martin/.VirtualBox/VirtualBox.xml')
Type:           normal (differencing)
Auto-Reset:     off
Location:       /u/martin/VirtualBox VMs/Windows XP Professional/Snapshots/{b4938314-1204-43f0-8752-767515f71b39}.vmdk
Storage format: VMDK
Format variant: differencing default
Capacity:       0 MBytes
Size on disk:   0 MBytes
In use by VMs:  Windows XP Professional (UUID: ed45ab68-3ae8-4c86-bb30-54b728ade86c) [Snapshot 1 (UUID: 3c90fa44-287d-4e66-8c7c-91d65ad7c340)]
}}}

I suspect something went wrong in the past while deleting a snapshot.

I've attached the VM's logs and .vbox files.
",mslw
14164,Problem with installing VirtualBox on Windows 7,Windows,other,VirtualBox 4.3.28,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
14165,Virtual machine loses hard drive when settings are changed.,Windows,Windows,VirtualBox 4.3.28,2015-06-02T15:35:30Z,2015-06-02T15:35:30Z,"This problem is described at length in the forum at this link:
http://forums.virtualbox.org/viewtopic.php?f=6&t=68147&p=323314&e=323314

After shutting down the guest OS and changing its settings using VirtualBox Manager the virtual machine loses its DVD and/or HDD configuration.
The message: FATAL: Could not read from the boot medium! System halted.

is displayed and it not possible to recover the disk. (Things tried restoring the original .vbox and .vbox-prev files, running VBoxManage internalcommands sethduuid etc. )

This problem is not present in VirtualBox 4.3.20.",eqh
14169,vboxsf: files with illegal (:) characters truncated on host's NTFS shared folder / results in data loss,Windows,Linux,VirtualBox 4.3.28,2015-06-03T06:50:04Z,2015-06-03T06:50:04Z,"Moving a file from a Linux guest filesystem that is tolerant of e.g. the colon character (:) in a filename, to a Windows-hosted NTFS filesystem using vboxsf results in truncation ('''DATA LOSS''') and odd naming behavior.

== Steps to reproduce: ==

1. Create a file on a Linux filesystem in a guest; e.g.
{{{
# dd if=/dev/random of='/tmp/1mega:byte' bs=1M count=1
}}}

2. Mount NTFS shared folder:
{{{
# mount -t vboxsf SHARE /mnt
}}}

3. Move file to vboxsf shared filesystem
{{{
# mv '/tmp/1mega:byte' /mnt
}}}

== RESULT: ==
a file in /mnt of zero size and truncated filename

{{{
# du /mnt/1mega
0       /mnt/1mega

# du '/tmp/1mega:byte'
du: cannot access '/tmp/1mega:byte': no such file or directory
}}}

== EXPECTED RESULT: ==
An error that does not result in the truncation of the /tmp/1mega:byte file in the above example OR a renaming of the file in /mnt, along with preservation of the contents of the file.",baitisj
14172,Virturalbox doesn't start,other,other,VirtualBox 4.3.28,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
14173,Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state,Windows,Windows,VirtualBox 4.3.22,2015-06-03T23:29:33Z,2015-06-03T23:29:33Z,"== Symptom ==
Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes.

== Details ==
Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state.

However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. 

Also another workaround is to have the Virtual Box GUI interface open and running and the VM will seem to start.

Is this a permissions issue?

== Steps to be able to duplicate the bug ==
1. Have an instance of Jenkins running on the host machine.
2. Create a freestyle Job that will allow you to execute Windows batch scripts
3. Then create a batch script as such 

{{{
cd ""C:\Program Files\Oracle\VirtualBox""
VBoxManage.exe ""Name_OF_VM""
}}}

4. save and build the job
5. Observer that it starts up but then immediately crashes and goes to the abort state.

== Versions Affected ==

 * Windows 8.1 64-bit (Host and Guest)
 * Version 4.3.22

== Workaround ==
Please see Details for any workarounds at the moment.

",MTaylor
7443,Guest Addition brakes mouse: instant scrolling instead of pointer movement,Windows,Windows,VirtualBox 3.2.8,2015-06-04T19:15:50Z,2015-06-04T19:15:50Z,"Host OS: Win7HomeBasic

Guest OS: WinXP SP3

VBox version: 3.2.8

PC(Notebook): Samsung R519

After installation of the Guest Additions touchpad (and usb-mouse too) does not work properly in guest OS: any application that have scrollbars (tested on notepad, MS Office 2007, MS Paint) do constant scrolling down to the bottom of the document when touchpad is used or mouse is moved. The direction of the mouse's movement does not influence on the applications behaviour. It just scrolls down. Installation of the official touchpad drivers into guest OS does not help. The pointer does not react on any movement after the driver installation.
The mouse (and touchpad) worked fine before Guest Additons installation. Uninstallation makes mouse work back as well.
",zolotov
4956,Installer fails with error 1603,Windows,Windows,VirtualBox 3.0.6,2015-06-05T09:14:31Z,2015-06-05T09:14:31Z,"Trying to install version 3.0.6 on Windows Vista.
After all the confirmation the installer starts. But after seconds the scrollbare runs back and an error is showed:

Virtual Box Installer
Installation of MSI failed
Error: 1603

",Nagi
13149,VirtualBox installation on Windows 8.1 with InstantGo issues,Windows,all,VirtualBox 4.3.12,2015-06-05T19:31:52Z,2015-06-05T19:31:52Z,"When you install Oracle VirtualBox x64 (latest version) on a Surface Pro 3 that supports InstantGo, when the computer goes to sleep, most of the time when the computer awakes, the base Surface wireless device won't load on the host system. I've been able to reproduce the problem by doing a factory reset on my Surface Pro 3 and installing it. The problem manifests itself immediately after the VirtualBox installation. This is a major problem, because without the wireless driver, the computer can no longer connect to the Internet or access network resources on both the host system and guest OS.",JHumenik
14177,Very slow command line operations on long uptime,Linux,all,VirtualBox 4.3.28,2015-06-06T18:16:06Z,2015-06-06T18:16:06Z,"I've a server where I'm trying to run a lot of virtual machines (25-30), with somewhat long uptime (some weeks) and what I see is a constant increase of the slowness of VBoxManage operations.

For example, on a fresh start the command ""VBoxManage list runningvms"" employs only 0.2 seconds but day after day the execution time rises and after some weeks the same command can employ even 60 seconds to complete.

This in turn gives problem with applications like phpvirtualbox that is unable to even reach the main screen (supposedly) due to various timeouts.

The only way to solve the problem is to shutdown all the machines, stop the vbox service, and restart it.",Alex
14178,Host Crash reproducible,Windows,all,VirtualBox 4.3.28,2015-06-08T12:40:51Z,2015-06-08T12:40:51Z,"Hi, i finally add it as a BUG here AFTER following all advices ( IRC, testing, reproducing failure, compaing results, check forums, etc. );

[ Sorry for sounding washy, im a bit tired now of all that crap, hopefully you are not and can take a deep look in it ]

Definition of the Bug as far as i can describe:

[HOST-SYSTEM]

[Soft-Ware:OS]

The Host Operating Systems i can reproduce these bugs on ( so far )are:

a) Windows NT 6.3.1 x86 U1 [ Windows 8.1 ( Embedded / Enterprise )Update 1 32-Bit ] NVHD

b) Windows NT 6.1.2 x86 [ Windows 7 ( Embedded Standard / Enterprise ) ] Service Pack 2 32-Bit ] NVHD

[Soft-Ware:VBOX]

VirtualBox 4.3.28 r100309 with ext-pack same version

[same effect/other symptoms in]

VirtualBox 4.3.29 r100811 with ext-pack from released version r100309 AND extpack for testing version [r100811]

HINT: Any version before is running ( not fine, but running )!


[Hard-Ware]

[A:AMD]
- Dell Optiplex 740
- CPU: AMD-Athlon X2 2.7GHz ( AMD-VX )
- NIC:
- onboard lan Marvell yukon GBit
- Wifi 54g D-link (PCI) originally; was exchanged with a firewire-pci
- 100mbit lan(pci with pxe-bios)

SND:
- onboard realtek ac 97

VGA:
- onboard nvidia ? ( unused)
- Ati v5700 Fire-GL (pci-express 16x)

HDD:
- 4x Seagate Barracuda ES 750GB 15k (non-raid use on onboard SATA AHCI )

ODD:
- external LG DVD+-RW whatever USB2
USB:
- 4 RootHubs ( 3 in use ) USB 2

[B:Intel]
- FS Esprimo

CPU:
- Pentium D 945 Presler ( VT-X)

HDD:
- 1x Samsung 160GB ( internal SATA AHCI )
- 1x IDE changeable rack
- 1x ide smart card/Compactflash-boot/SDHC/MS

VGA:
- Intel 945G (EE)

SND:
- onboard intel HD

ODD:
- none

HINT: These machines are in amounts up to 50 available, were in seldom use and bought from local energy provider as sorted-out and should be used in future for kindergarten-network as experimental stations; they are already checked and stress-tested and i interchanged systems with the given setup just to ensure it is not a single-machine that is faulty. Btw.: all these machines ran in energy efficient lowest modes all their lifetime just used for some bureaucracy, so even if cpu-ram-gpu-stresstest weren't reliable, they function normally in any other case ( before and after reproducing the given failure of vbox )


What is the problem ?


In my webchat IRC with MichalN in the #vbox channel i had kind brainstorm of possibilities, because i wouldn't report a bug without further investigations. Whatever, the problem to report a bug is, i can get NO MINIDUMP at all, independent of settings, because due to bugs in the given version, from a given OS in native VHD-Boot there are issues which in most cases, do not lead to a dump. believe me i tried all options. That is why i asked at vbox-channel for possible workarounds, like special logging-modes for vbox or possibilities to sandbox vbox, so the host-system can't crush and can be investigated. Nonen option so far given.

The problem in its symptomatic:

When running 64-Bit guests the host system crushes almost immediately!
Linux live systems run. ( at least in the release version ) in the testing-version they crush also immediately and with a bsod clock_watchdog_timeout for some millisecs of the host - followed by immediate restart and no dump at all ); at least in testing version vbox comes so far to log the usual vm-init inside. in the release version it never got so far.

Tested systems:
- 64-bit guest on 32-bit host is the problem;
- i counterchecked 32-bit ones also

- Fedora
- 17
- 19
- 21
( Workstation, Server, Live, DVD , CD, Netinstall )

- Ubuntu
- all LTS versions plus vivid (15.04) and winy (15.10)

- Windows
- any you can think of

- Debian
- Jessie ( 8 )
- Wheezy ( 7.1 and 7.6 )
- did i forget some, maybe ...

okay to get some more specific things:


side-problem NIC

as MichalN mentioned, due to change from wifi to onboard lan i checked that ones too, it makes a difference in time it takes until crash, but nevertheless changes nothing at all; so forget about it; right now in this moment i am running the stable-version 4.2.30 r100415 with winy werewolf (15.10) besides this ticket-creation without a problem with full install and stress-test inside 64 bit vm on the A-Host, the AMD-one, with all options given and any hardware acceleration and all hardware on the host enabled, soi can say -- It is NOT a HW-problem and not even a host-problem i would say.

I know it is problematic without a dump at all; however let me go on with that:

i tested any old version i could find in my libraries and which i regularly used on all my machines, especially on the given ones.
Btw. i just checked if it is dependent of the generation/featuresets by checking on m HP Elitebooks, too and on a panasonic toughbook; It is not; That ones were Core-duo Core2-Duo Turion X2 i5; Where was I, ah yes: Old versions

Old versions of VBOX tested so far:

- 3.2.8
- 4.0.8-71778
- 4.1.12
- 4.1.14-77440
- 4.1.22-80657
- 4.2.0-80737
- 4.2 ( 4.2.16 + 4.2.4[r81684] )
- 4.3 ( 4.3.6[r91406] + 4.3.8[92456] )
... these ones are counterchecked on linux hosts as well, which have not at all any problem with the 64guests on 32hosts (whereas the mentioned systems above that were used as guests i have also available as hosts )
plus the actual

release:

- 4.3.28-100309

testing:
- 4.3.29-100811

and the actual stable:

- 4.2.30-100415


Here is what i came to as a definitive reproducable point:

When using the actual release or testing:

-ONLY Linux-live systems based on debian run at all;
- UNTIL fully installed, the CRASH follows right after logging in the created user-account first-time.

- Windows-64-Guests ( Setup OR OVA OR prepared vhd's dism/firadisk/grub4dos) crash immediately.

- Linux-64-Guests crash right in the moment a user account is logged in in a graphical system

- Fedora-based linuxes are critically slow

- debian-based run acceptable up to perfect

- ovas with virtualization features in it are crushing in the same manner, comparable to Fedora 21 Workstation, which is the fastest crusher of all tested systems(IMMEDIATE-RIGHT-NOW-TOTAL-RESTART-OF-HOST)

Okay that was long enough - i am tired and have no concentration anymore, please see this as a possibility to make something of it; i am available for further test-scenarios, BUT DO NOT FORGET: the given HOST-OSs can not produce a dump.

I saved the chat-log of my chat with MichalN if it helps and am willed to help out. added also 2 screenshots just for a prove of stable is running ubuntu winy and a short device overview.

Give me reproducable test-case and i follow to my best; If necessary i can make a video of the crash and the none existance of the dump if you wish to. In case you do not believe.
I have visual studio available if it helps and am able to install a set of progs to help narrow the problem, because these ones are not really production systems at the moment. Only thing is you have to explain what it is for if i dont know and i might double check for resulting contents, because i run some more networks chained where these machines are appended to.

To be precise: i am willed to spend my time to check on the HOST-A ( the AMD ) as the Intel-Machines go out for setup and deliverance for a while for other projects.

The other systems are my personal ones and i am not willed to make crucial tests on them anymore as long as crazy shutdowns are not handled.

So whatever: I hope you have an idea of an idea of an idea of what might could eventually maybe happen here and feel able to give some straight questions.

Thanks for your interest.

PAETH CLAUDIUSRAPHAEL
S466531257BOSS

P.s.:

By the way, if you think that it is not necessary to give compatibility to these OLD machines then i need you to tell that clearly and unmisleading and ALSO clarify the tech-specs of your products for the given case. If instead you accept that these kind of machines are right now even in industry-leading nations like germany still in use by MANY private AND business users and organizations, especially those who teach and take care of our children then PLEASE do me and maybe others the chance to make it usable. Your decision. I just ask to be precise about this issue.",PAETH CLAUDIUSRAPHAEL
14180,when trying to open sagemath in oracle vm virtual box in windows 8.1 64 bit Blue screen of death happening,Windows,Linux,VirtualBox 4.3.28,2015-06-08T14:12:35Z,2015-06-08T14:12:35Z,"Installation of Oracle VM Virtual Box and importing the sage ova file in it was not a problem. But when I started the sage machine Blue Screen of Death (DRIVER_VERIFIER_DETECTED_VIOLATION) happened. Otherwise my machine works fine. I was using Sage-6.7 ova file and Virtual Box 4.3.28.100309-win in a windows 8.1 64 bit machine. The problem persists for 4.3.12.93733-Win version also. For my machine OS, drivers BIOS everything is up to date. Hard disk health is good. No issue of Virus or malware. I have not installed the guest additions.More than 100 GB space is available in machine. Any help will be appreciated.",amritendu
14189,Port forwarding silently fails when source ports are privileged,Linux,Linux,VirtualBox 4.3.28,2015-06-09T23:38:27Z,2015-06-09T23:38:27Z,"I just spent a really unproductive hour or so trying to work out why I was getting ""Connection refused"" from a test LDAP server in a VM.

Then I resorted to trying to forward the port using SSH. The SSH client reminded me that privileged ports cannot be forwarded unless you're root. (Oh yeah, Unix. Privileged ports. I remember now.)

So my suggestion is:

 - The VirtualBox GUI should warn the user about this.

 - There should be an error displayed if port forwarding fails because the port is privileged.

The documentation at https://www.virtualbox.org/manual/ch06.html mentions the limitation, but it states that the VM will refuse to start in such a situation. That doesn't appear to be true -- I tried restarting the VM and didn't get a useful error message.",meta
3654,Bridged Networking does not find any adapters,Windows,other,VirtualBox 2.2.0,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
13945,Yosemite 10.10.2 and Virtualbox 4.3.X Crash System,Mac OS X,Windows,VirtualBox 4.3.24,2015-06-12T02:25:39Z,2015-06-12T02:25:39Z,"After migration from 4.2.28 to any version of 4.3.X the Yosemite OS crash with memory fault error.
This event is just with this version and Guest Windows 7.
",tekmanforce
14194,VBoxManage VM with same name in different groups,all,all,VirtualBox 4.3.28,2015-06-14T13:58:28Z,2015-06-14T13:58:28Z,"In VBox GUI I can easily view and manage two different guests with the same name but are located in different groups:

Project-A -> DC

Project-B -> DC

However, when using 'VBoxManage list runningvms' for example, I just have two VMs called 'DC'.  The only way to manage them is to use the UUIDs which is really awkward to use.  In fact, I have to use 'showvminfo' just to work out which group each guest belongs to.


It would be easier if the group could be used as part of the VMNAME so that they can be referred to as follows in command line tools such as VBoxManage:

Project-A/DC

Project-B/DC

I know I could rename the guests to ProjA-DC and ProjB-DC or similar, but that defeats the object somewhat.
",garethwilliams
14134,"WDDM driver exposes only 384 MB VRAM, at least 512 MB needed (and 12 GB available!)",other,other,VirtualBox 4.3.28,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
14195,Linked clone does not keep saved state,all,all,VirtualBox 4.3.28,2015-06-15T17:49:57Z,2015-06-15T17:49:57Z,"When trying to create a link clone of a VM which has live snapshot and has been restored to one of them, the saved state is not carried accross to the cloned VM.

Simple steps to reproduce:

Create, register & start an empty VM. Wait until the boot failure screen.
{{{
vboxmanage createvm --name test --register
vboxmanage startvm test --type gui
}}}
Take a live snapshot, power off the VM, restore the snapshot, check the state.
{{{
vboxmanage snapshot test take base
vboxmanage controlvm test poweroff
vboxmanage snapshot test restorecurrent
vboxmanage showvminfo test | grep State
}}}
State is now ""Saved""
Create a linked clone and check its state:
{{{
vboxmanage clonevm test --name test-clone --snapshot base --mode machine --options link --register
vboxmanage showvminfo test-clone | grep State
}}}
Reported state if ""powered off"" instead of ""Saved"".
Starting the linked clone brings us to the initial VBox boot and not to the failed boot screen of the parent VM.",Max D
14196,Install fails with fatal error but no other message,Windows,all,VirtualBox 4.3.28,2015-06-16T17:31:04Z,2015-06-16T17:31:04Z,"It gets most of the way through the install then it rolls back and says there was a fatal error. But, it never says what the error was. I've collected an msiexe /lx install log that I'm attaching. It's the only info I have right now. I'm running Windows 7 as the host.",Gungwald
14191,"VBoxSVC crashing, VirtualBox broken in several ways",Mac OS X,Linux,VirtualBox 4.3.28,2015-06-17T01:39:10Z,2015-06-17T01:39:10Z,"It's tough to explain what's going on, but here's a post I made on the forum which has screenshots and explanations:

https://forums.virtualbox.org/viewtopic.php?f=8&t=68309

Basically everything is broken. I'm unable to add new guests, and the ones I load up act oddly. It would be great if someone could walk me through some debugging/troubleshooting steps. Something is badly broken here, even after a complete uninstall and fresh install.",CaptSaltyJack
14205,Win guests on Dell laptops have black display for integrated webcam via passthrough,Linux,Windows,VirtualBox 4.3.28,2015-06-17T01:45:32Z,2015-06-17T01:45:32Z,"As the original bug reported, #13728, was limited to different hardware and software, I created a new bug report.

Using Fedora 22 64bit host, and Win 8.1 guest, passthrough webcam produces a black screen/display on Dell Inspiron 15 5000 series.  

This is despite using the latest Virtualbox and Guest Additions.  No suggested fix has worked.",H0wdy
14206,"glPixelStorei(GL_UNPACK_ALIGNMENT,1) does not work",Windows,Windows,VirtualBox 4.3.28,2015-06-17T03:07:02Z,2015-06-17T03:07:02Z,"This following code:

glPixelStorei(GL_UNPACK_ALIGNMENT,1);
glTexImage2D(GL_TEXTURE_2D,0,GL_ALPHA8,width,height,0,GL_ALPHA,GL_UNSIGNED_BYTE,pixels);

Will work properly with a packed texture only if width is a multiple of 4. If for example width is 41 and the texture is packed (so each row is 41 bytes wide with 0 empty bytes between rows) then diagonal lines will appear in the texture. However the same code works properly outside of virtualbox on every machine/driver combination tested.",sarladudu
14207,VBoxManage unregistervm --delete performs only a partial deletion if media file is locked by other process,Windows,Linux,VirtualBox 4.3.28,2015-06-17T09:12:07Z,2015-06-17T09:12:07Z,"Trying to produce an automatic provisioning script to build VM's on demand and encountering this issue when the machine get above a few GB in size.

Process calls the vboxmanage export command and then immediately calls the unregistervm --delete command to remove the VM leaving just the export file.

However if the VM is above a few GB in size the lock is not released on the media in time resulting in:

{{{
BoxManage.exe: error: Medium 'C:\Users\scobarn\VirtualBox VMs\My_VM\My_VM.vdi' is locked for reading by another task
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium
VBoxManage.exe: error: Context: ""int __cdecl handleUnregisterVM(struct HandlerArg *)"" at line 166 of file VBoxManageMisc.cpp
}}}

Subsequent delete commands fail due to the vboxmanage unregister command executing just the unregistration part but leaves all files and directories behind requiring manual cleanup.

{{{
VBoxManage.exe: error: Could not find a registered machine named 'My_VM'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: ""FindMachine(Bstr(VMName).raw(), machine.asOutParam())"" at line 154 of file VBoxManageMisc.cpp
}}}

Shouldn't vboxmanage unregister --delete be an all or nothing command and if an error occurs perform none of the steps instead of just removing the registration and leaving all files behind to cause issues without manual cleanup?",sbarnden
13564,Allow sorting of the VM snapshots,other,other,VirtualBox 4.3.18,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
12180,running slow,other,other,VirtualBox 4.3.0,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
8179,Dreamweaver ftp errors because of uppercase directories on mapped drives,Linux,Windows,VirtualBox 4.0.2,2015-06-17T17:48:25Z,2015-06-17T17:48:25Z,"My setup:

Virtualbox 4.0.2
Host OS: Ubuntu 10.10
Guest OS: Windows 7
Dreamweaver version: CS5

I keep getting errors when trying to put files onto my server. An example error would be:
------------------------------------------------------------
Started: 1/24/2011 6:23 PM

DOMAIN.COM\index.html - error occurred - An FTP error occurred - cannot put index.html.  Access denied.  The file may not exist, or there could be a permission problem. 

File activity incomplete. 1 file(s) or folder(s) were not completed.

Files with errors: 1
DOMAIN.COM\index.html

Finished: 1/24/2011 6:23 PM
----------------------------------------------------

The error is occurring because the directory DOMAIN.COM does not exist on the server. However, I didn't put it from a local file system with an uppercase directory of DOMAIN.COM. On my system the directory in question is lowercase, domain.com.

This only seems to happen when the local location is on a mapped network drive.",V_RocKs
14204,VM screen flickers,Linux,Linux,VirtualBox 4.3.28,2015-06-17T23:11:02Z,2015-06-17T23:11:02Z,"Virtual machine is constantly flickering and when I log in grey base coloured squares appear until I press in the higher left corner where dash is. But flickering is making working with VM impossible.

I am using Virtualbox 4.3.26. My host is Ubuntu 15.04 with custom NVIDIA driver (version 346.72) for Geforce GTX 960M. My guest is Ubuntu 14.04.02 LTS.

All details about this annoying regression are described and available here: https://forums.virtualbox.org/viewtopic.php?f=3&t=67823",SamH
13806,Video capture in Linux does not work (small file with empty green .webm video),Linux,Linux,VirtualBox 4.3.20,2015-06-18T12:53:37Z,2015-06-18T12:53:37Z,"I know similar bug reports are made but problem still exist and is not solved like I noticed on some bug report comments.

Host: 64-bit Ubuntu 14.04.1 LTS with 3.18.5 generic kernel.

Using ATI-AMD graphics card HD 7770 series on host:
    $ lspci -vnn | grep VGA
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller])

Also guest additions are installed in guests and 3D acceleration enabled from settings. Did not help. Still I get small .webm file with empty green video.

I tried also classic Gnome fallback - I mean I turned Unity off but still no help. I tried with or without guest additions - no help. Certainly also from settings I turned 3D acceleration on and off.
I am running 64-bit Ubuntu 14.04.1 LTS and guest systems are Kubuntu 14.04.1 LTS, Lubuntu 14.04.1 LTS, Xubuntu 14.04.1 LTS Ubuntu Mate 14.04.1 LTS. I tried both 32-bit and 64-bit guests - same problem.
I also tried different video players - VLC, SMPlayer, Totem, Xine - always blank green video and that's it",Edmund Laugasson
14138,Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf',Windows,all,VirtualBox 4.3.28,2015-06-18T18:24:59Z,2015-06-18T18:24:59Z,"I get this error installing on Windows 8.1:


{{{
DIFXAPP: INFO:   VBoxUSBMon.inf: checking signature with catalog 'C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.cat' ...
DIFXAPP: ERROR:  Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf'). (Error code 0x800B0003: The form specified for the subject is not one supported or known by the specified trust provider.)

}}}

",Mark Richman
14213,NAT networking stops responding blocks all I/O on that interface for Ubuntu/Debian x64 guests,Windows,Linux,VirtualBox 4.3.28,2015-06-19T23:06:42Z,2015-06-19T23:06:42Z,"= Summary =
I can reproduce almost 100% this fault, which seems to affect Virtualbox versions 4.3.x in both Windows 8.1 and Windows 10 using ubuntu 14.04.2 or debian Jessie guests.

I attached a script, which pings a well known site once a second that you can run to show the precise moment at which networking stops responding. You may use this script or any tool you like for this. For the purposes of the bug description I will assume you are using the embedded script.

= Repro steps to detect fault =

1. Make sure you have a standard NAT based single interface ubuntu guest running.
2. Log-in to guest.
3. Install either google chrome (triggers fault immediately) or chromium-browser (ubuntu) or chromium (debian jessie) which trigger very often but not 100% of the time. Install google-chrome using the following snippet:

{{{
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - 
echo ""deb http://dl.google.com/linux/chrome/deb/ stable main"" | sudo tee /etc/apt/sources.list.d/google-chrome.list
sudo apt-get -yqq update
sudo apt-get install -yqq google-chrome-stable
}}}


4. Start embedded script to monitor network, access.
{{{
Expected result: It should be possible to ping well known address, the
 result should be something along these lines:
...
1 packets transmitted, 1 received, 0% packet loss, time 0ms
...
}}}

5. Start chromium browser from UI and try to access google.com or any address.

{{{
Result: Scripts start showing that network access is broken. Lines like
the following one show in script after a small delay where everything is
frozen:
...
1 packets transmitted, 0 received, 100% packet loss, time 0ms
...

Result 2: Virtualbox process in Windows becomes unresponsive and unstable,
cannot be easily stopped, may turn windows blank as hung processes show.

}}}
 
{{{
Expected result: Network access should work normally, no disruptions.
}}}

= Script to trigger fault =

For repro steps I used:
{{{
./net_tester.sh -x
}}}

{{{
$ cat net_tester.sh 
#!/bin/bash

function usage()
{

  cat <<eof

Usage: $(basename $0) [-x] [-h] [output log file]

The purpose of this script is to check network reliability of Virtualbox

Options:

-x, --external  Uses the google DNS to ping instead of NAT gateway address.
-h, --help      This message.

eof
  exit 1
}

#
# Change the following line to the address of the NAT gateway.
#
ping_address=10.0.0.2
out_file=out.log

while [ ""$1"" != """" ]
do
  case ""$1"" in
  -h|--help) usage ;;
  -x|--external) ping_address=8.8.8.8 ;;
  *) out_file=$1 ;;
  esac
  shift
done

while :
do
  date
  ping -c 1 ${ping_address}
  sleep 1
done | tee ${out_file}

}}}

",Coffee_fan
13526,Memory leak with 3D acceleration with Ubuntu lens,Windows,Linux,VirtualBox 4.3.18,2015-06-20T00:47:09Z,2015-06-20T00:47:09Z,"I have a Windows 7 host and Ubuntu 14.04 guest. If I enable 3D acceleration, there is a huge memory leak (about 100 MB per second) when the Ubuntu main system menu (Unity lens) is open. It is apparently related to the blurring effect, since there is no leak if I disable 3D acceleration and Ubuntu just shows a plain colour background. 

The strangest thing is that I can see the memory being eaten away in my host's performance monitor, but the guest's performance monitor doesn't show any problem and the memory use is stable there. I hope this can be a clue as to where the problem lies.

I can work with 3D disabled but the system is totally unusable with it enabled, since the memory leak is so severe.

I attach a log file",rgargente
14200,USB not detected when VBox running,Windows,all,VirtualBox 4.3.28,2015-06-22T18:49:08Z,2015-06-22T18:49:08Z,I have a Canon IX8000 series USB printer connected directly to my PC. If I run VBox the printer is reported offline and cannot be accessed. As soon as I close VB the printer starts working again,MarkT
13866,Provide useful output when host interface for bridge is no longer available,other,other,VirtualBox 4.3.22,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
14109,VBoxSVC lingering after VBoxWebSrv,Windows,all,VirtualBox 4.3.26,2015-06-23T13:51:58Z,2015-06-23T13:51:58Z,"'''Context'''[[BR]]
Windows 8.1 64 bits
VirtualBox 4.3.26

'''Scenario'''[[BR]]
Without any VirtualBox process already running, start VBoxWebSrv in a prompt in verbose mode, wait for it to start, wait another 2 sec, then press Ctrl+C to quit.
In the Task Manager or via cygwin ps -W, check how long VBoxSVC will remain running before auto shutdown.

'''Issue'''[[BR]]
VBoxSVC remains running for about 6 min then auto exit

'''Expected behaviour'''[[BR]]
VBoxSVC remains running 5-10 sec then auto exit, like when VirtualBox.exe or VBoxManage are run.

'''Detection command in cygwin'''

{{{
while true; do sleep 1; isStarted=1; isFinished=0; while [ $isStarted -ne 0 ]; do sleep 0.5; ps -W | grep -qi vboxsvc; isStarted=$?; done; echo ""VBoxSVC started""; startTime=$(date ""+%s""); while [ $isFinished -eq 0 ]; do sleep 0.5; ps -W | grep -iq vboxsvc; isFinished=$?; done; echo ""VBoxSVC finished""; endTime=$(date ""+%s""); runTime=$(($endTime-$startTime)); echo ""VBoxSVC ran for $runTime seconds""; done;
}}}


'''VBoxSVC average runtime as per the command above'''[[BR]]
367 sec

'''Extra info'''[[BR]]
Behaviour is also visible on Win 7.[[BR]]
Logs & memory dump of lingering VBoxSVC can be found at https://kamax.io/vbox/vboxsvc-lingering_with_vboxwebsrv.zip",Max D
14220,Resized differential drives causes guest crash,other,other,VirtualBox 4.3.28,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
13622,BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) on host machine immediately after powering on guest machine,Windows,Windows,VirtualBox 4.3.18,2015-06-25T13:51:57Z,2015-06-25T13:51:57Z,"Hello.

I get BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) immediately on host machine after powering on guest machine. 

I have searched the forums and did not find anything corresponding to my problem.

Host: Windows 7 SP1 x64
Guest: Windows 2012",Anton Lisnenko
14222,VM window should not be brought to front when it becomes active in full-screen mode,Linux,Windows,VirtualBox 4.3.28,2015-06-25T19:43:32Z,2015-06-25T19:43:32Z,"Using VirtualBox 4.3.28 on Lubuntu 14.10 x86-64 host.

I have the window manager (Openbox) configured so the window under the mouse pointer is automatically activated, but not brought to the front, when the pointer moves over it. (Clicking in a window does bring it to the front.)

That works fine with a VirtualBox VM which isn't in full-screen mode. However when a VM is in full-screen mode, the VM window is brought to the front as soon as it becomes active, even though it has not been clicked in.

That's quite annoying if I have Alt-Tabbed out of the VM and am using other programs, with the VM window appearing behind the other program windows. As I move the mouse pointer from one other program window to another, as it passes over part of the VM window, the VM window is brought to the front, obscuring the other program windows.

I think a better behaviour would be to only bring the VM window to the front when the user clicks in it.",Donuts
14223,Please change the Mandriva name on the rpm page to OpenMandriva,Linux,all,VirtualBox 4.3.28,2015-06-26T08:07:08Z,2015-06-26T08:07:08Z,"Hi, I am the president of the OpenMandriva Association, this body was formed from users and developers of Mandriva prior to their final bankcruptcy. It was formed with the purpose of legally passing on the source code of the OpenMandriva distribution into the hands of the OpenSource community. 
The OpenMandriva association creates and distributes it's own OpenMandriva OS created from this sourcecode. We want very much to keep the name of Mandriva alive under the auspices of the OpenMandriva Association and one of the ways we can do this is to ask you whether you would change your current web pages to show OpenMandriva rpm packages rather than Mandriva and to change the name part of the rpm filename from mdv to omdv. We are more than happy to support you with updated rpm spec files for the builds. Since sadly Mandriva is no more and the web pages should be changed anyway to reflect this point in history it is felt that this might be the best time to ask for your help and cooperation.

I was advised on the admin/moderation forum that here would be the best place to make the request

This web page from the founder of Mnadrake/Mandriva may be of interest.
http://www.indidea.org/gael/blog/

Regards,

Colin Close
President 
OpenMandriva Association",itchka
10121,Guru Meditation (HostMemoryLow) when low memory,Windows,Windows,VirtualBox 4.1.8,2015-06-26T14:10:12Z,2015-06-26T14:10:12Z,"I've resumed a virtual machine, but memory low. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation. 
(First occurence was founded in unofficial test build 4.1.7, see comment #9 of ticket #7929
",wacher
14197,can not install bridged interfaces on W7-64 Pro,Windows,other,VirtualBox 4.3.28,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
13841,Oracle Vbox crashes on full screen,Windows,Linux,VirtualBox 4.3.22,2015-06-29T05:41:28Z,2015-06-29T05:41:28Z,"While trying to view in full screen Vbox crashes with error ""the instruction at 0x000000000 referenced memory at 0x000000000. The memory could not be written."" ",ddfedora21
14230,VirtualBox ISession get_Console returns S_OK but IConsole ptr is NULL,Windows,Linux,VirtualBox 4.3.28,2015-06-29T15:52:54Z,2015-06-29T15:52:54Z,"Hi,

I am running into a strange thing here. My (pseudo) code (see below) works fine on Windows 7 SP1 / 64bit with 64bit VirtualBox and 64bit app binary.
But when I compile the stuff not as x64 but Win32 (32bit binary on SysWOW64), the app crashes because get_Session returns S_OK but the delivered pointer IConsole * is NULL !!!
Is this a bug or is it not possible to run a Win32 binary on Win7/64 with VirtualBox/64? I thought that it should be completely transparent using Microsoft COM?
Here is the pseudo code:

{{{
BSTR machineName = SysAllocString(L""VMName"");
IMachine *pMachine = NULL;
if (FAILED(pVBOX->FindMachine(machineName,&pMachine)))
{//do error stuff}
if (FAILED(pMachine->LockMachine(pVBOXSession,LockType_Write)))
{//do error stuff}
pMachine->Release, pMachine = NULL;
if (FAILED(pVBOXSession->get_Machine(&pMachine))) // get mutable one
{// do error stuff}
IConsole *pConsole = NULL;
if (FAILED(pVBOXSession->get_Console(&pConsole)))
{// do error stuff }
}}}

[...]
At this position, pConsole is NULL on Win32 (SysWOW64) and not NULL on Win64 (x64).
Any ideas?

Thank you.




",vboxcomapijunkie
14112,BSoD in VBoxNetAdp6.sys with STOP 0x9F,Windows,other,,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
10860,Full resolution not exposed to Linux guest,Mac OS X,Linux,VirtualBox 4.1.20,2015-07-02T15:31:46Z,2015-07-02T15:31:46Z,"When using VirtualBox on a MacBook Pro Retina, only half the resolution is exposed to, at least, Linux guests. This causes the fonts to be blurry in the guest OS. 

To verify this, install Linux, and go to fullscreen, type xrandr and notice the resolution is set to 1440x900.

To compare with VMWare, full Retina mode is supported: http://www.vmware.com/products/fusion/features.html#approved

This exposes the current full resolution to the guest, which in the default host retina mode would mean the guest sees 2880x1800 resolution and has to deal with it on its own accordingly.",dsvensson
11451,no keyboard and mouse after sleep with Win7,Mac OS X,Windows,VirtualBox 4.2.6,2015-07-03T15:41:35Z,2015-07-03T15:41:35Z,"After opening the lid on my Macbook Air (13"" mid 2012, 1.8GHz, 8GB, running OSX 10.8.2) and waking up from sleep mode, keyboard and mouse input doesn't work any more. But the system itself is not frozen, it updates emails etc. The only way is to hard reboot. This happens only when the lid is closed for more than maybe 30min (can't tell exactly). 

The issue happens when the guest system Win7 Pro 32 Bit is running, even with no running application. deactivated sleep mode in Win 7 without any improvement. 
Virtualbox and extensions are Version 4.2.6. 

[https://forums.virtualbox.org/viewtopic.php?f=8&t=53947]",maerz001
14241,Brackets in group name of VirtualBox Manager causes erratic behavior.,Windows,Windows,VirtualBox 4.3.12,2015-07-04T19:44:06Z,2015-07-04T19:44:06Z,"This is to report that including brackets ""("" and "")"" in group names causes erratic behavior; 

When creating groups named ""Base Machines (Stage 0)"" or ""Base Machines (Stage 1)"" cause the groups to show up collapsed and moved to the bottom when the VirtualBox Manager is (re)started (Windows).

Taking out the brackets immediately solved the problem. The VirtualBox Manager seems to have a problem with brackets in group names. Possibly other characters cause similary issues.

I am currently stuck at v4.3.12 due to issue (#13841), but I've seen this behavior up to v4.3.28 (inclusive).",Hans Vledder
14242,3D Accelerate Grayed Out (Can't disable after moving VM),Windows,Linux,VirtualBox 4.3.18,2015-07-04T23:28:40Z,2015-07-04T23:28:40Z,"I recently set up a new system and decided to migrate my VM to the new host. The new host doesn't support 3D acceleration so I was unable to start the VM.

Unfortunately, because VirtualBox detected that my host doesn't support 3D acceleration, it disabled the ""3D Acceleration"" checkbox in the VM's settings. It was disabled, yet still checked.

The workaround is just to use the commandline:
vboxmanage modifyvm MY_VM_NAME --accelerate3d off

If VBox is taking the time to check for host capabilities and updating the UI appropriately, it should also remove the 3D acceleration checkbox and notify the user about the incompatibility.

I'll also note that this was in 4.3.18 since that's what's in the Debian package repository. I migrated the VM from a Windows host using 4.3.28 that supports 3D virtualization so I wasn't able to verify whether this is an issue in the latest release.",sraboy
14243,"Mini toolbar is 'Always on top' for all windows, even when VM does not have focus",other,other,VirtualBox 4.3.28,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
14215,(Windows 7) Guru Meditation -226 (VERR_INTERNAL_ERROR_2),Windows,Windows,VirtualBox 4.3.28,2015-07-06T00:56:59Z,2015-07-06T00:56:59Z,I was trying to install Visual Studio Community 2015 RC on Win7 x64 guest and during component selection got Guru Meditation. No Guru Meditation on the second try.,tico-tico
12558,dock and menubar: auto-show in fullscreen doesn't work on OS X Mavericks,Mac OS X,Windows,VirtualBox 4.3.6,2015-07-06T19:00:45Z,2015-07-06T19:00:45Z,"The option under ""Virtual Box->Preferences"" (dock and menubar: auto-show in fullscreen doesn't work on OS X Mavericks), seems not working on OS X Mavericks with Windows 8.1 guest. After I unchecked this option, when I pull the mouse to the top, the menubar still shows up.",Hong Xu
12064,Suddenly no VM's will start - all give a RPC_S_SERVER_UNAVAILABLE error at 0%,Windows,all,VirtualBox 4.2.16,2015-07-06T19:51:53Z,2015-07-06T19:51:53Z,"I was in the process of creating a new machine, and it wouldn't start (more in a bit) - I then tried to start up a few old, reliable machines, and got the same behavior.  The only change was that on startup a new version was mentioned; I installed it and saw this behavior.  After some web research I went back to version 4.2.12, and still see the same problem - but this may have to do with having installed the 4.2.16 version and then, perhaps, and incomplete removal.  I suppose technically this applies to both versions, as the problem shows up in both.

When I try to start any machine, I see a small popup, ""Starting virtual machine..."" and ""0%"" - that never changes.  My host OS is Windows 7 Ultimate; I have to kill the process for that machine manually.  When I do, I get a popup from Virtualbox; the detailed error message is:
Result Code: 
  RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
  Component: 
  ProgressProxy
  Interface: 
  IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Web searching shows this, or something like it, was a problem years ago, but apparently fixed.  I found current ticket #10747 that looks similar.

The VM I was trying to start as the main test case is a Windows 98 machine, fairly vanilla.  I certainly haven't changed any of its attributes (e.g., hardware acceleration options) since it last ran.

I have 17 VM's, all of some level of importance; it would not be a minor effort to recreate them, even if that helped.  I tried to create a new Windows 2000 machine from scratch and had the same problem, that is the exact same hang and detailed error message.

I'm willing to invest some time to help fix it, if any testing I can do on this end might help.",Bryan Bentz
13686,VirtualBox + Actual Windows Manager = crash,Windows,Windows,VirtualBox 4.3.20,2015-07-07T12:02:14Z,2015-07-07T12:02:14Z,"Hello,

I recently installed the Actual Windows Manager application (demo available here: http://www.actualtools.com/windowmanager/) to manage my multiple screens.

I noticed that, when this application is installed, all my virtual machines crashes when I try to open them. After 5 seconds, the virtual machine window freezes, and it's not possible to make any action. I noticed that the virtual machine continues to work on the application main interface (the virtual machine is still updated inside the screenshot control), but the virtual machine display window stops to work, and I have no alternative but to kill it.

When this happens, my machines take the Aborted status, and I cannot do nothing to resolve that. If I try to start my machine again, it restarts normally, but after 5 seconds, the problem returns. All my virtual machines are affected by this issue. If I uninstall the Active Windows Manager, all becomes normal.

I'm working on Windows 7 professional 64bit.

Regards",jeanmilost
13234,Key repeating does not work in OS/2 guest,Windows,other,VirtualBox 4.3.14,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
14210,VERR_INTERNAL_ERROR_3 when loading custom device plugin,Windows,Windows,VirtualBox 4.3.28,2015-07-13T11:15:57Z,2015-07-13T11:15:57Z,"Hi folks, I use a custom virtual PCI device plugin. Unfortunately, even though I've signed it with a code-signing key from GoDaddy, VirtualBox 4.3.28 refuses to load my DLL. It gives the following error..

{{{
00:00:03.302562 VMSetError: F:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDMLdr.cpp(307) int __cdecl pdmR3LoadR3U(struct UVM *,const char *,const char *); rc=VERR_INTERNAL_ERROR_3
00:00:03.302569 VMSetError: Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll
00:00:03.429194 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll (VERR_INTERNAL_ERROR_3)}, preserve=false
00:00:03.475155 Power up failed (vrc=VERR_INTERNAL_ERROR_3, rc=E_FAIL (0X80004005))
}}}

I've had a look at the source code for VBox and unfortunately this error is returned in many different situations. To make matters worse the pdmR3LoadR3U function obliterates the original error string which makes it impossible to discover the root cause. All you get is ""Unable to load R3 module"", which is about as useful as a chocolate teapot.

Given that the same DLL works with older versions of VBox (prior to the hardening update) and that the DllMain is never called, I have to assume that this error is related to signature verification issues. However, every tool I've tried tells me that my DLL is signed correctly and that the certificate chain is OK.",Kaloth
13022,I/O errors reported by kernel for device backed by VDI,Mac OS X,Linux,VirtualBox 4.3.10,2015-07-14T12:15:31Z,2015-07-14T12:15:31Z,"/dev/sda backed by a VDI

/dev/sdb backed by a vmdk, created with the command:
sudo VBoxManage internalcommands createrawvmdk -filename /Users/chris/VirtualBox\ VMs/Fedora\ Rawhide/320g.vmdk -rawdisk /dev/disk2

/media/sf_chris/ is a Shared Folder whose source is HFS+

During sustained copying from /media/sf_chris and writing to /dev/sdb, the kernel reports spurius read and write errors from /dev/sda which is essentially inactive in this process. Long file copies (10 minutes) eventually result in segfaults, the system will no longer respond to commands and I can't even get kernel messages out of the VM to see what's gone wrong other than it looks like the I/O errors are effectively corrupting the OS as it's running.

[  222.202808] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  222.203003] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  222.203287] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  222.203407] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  222.203528] rawhide.localdomain kernel: Write(10): 2a 00 00 58 a1 c8 00 02 00 00
[  222.203644] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 5808584
[  222.203746] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[  273.598086] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  273.598179] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  273.598255] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  273.598341] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  273.598437] rawhide.localdomain kernel: Read(10): 28 00 01 17 73 40 00 00 20 00
[  273.598533] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 18314048
[  273.598618] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0

The host kernel messages report no IO related errors. But does report other things related to VirtualBox at the time the problem occurs:

May  8 23:04:16 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:44 ming kernel[0]: VirtualBox (map: 0xffffff8050dfec18) triggered DYLD shared region unnest for map: 0xffffff8050dfec18, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VirtualBoxVM (map: 0xffffff803cc1b138) triggered DYLD shared region unnest for map: 0xffffff803cc1b138, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:13:46 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0

The vboxlog reports a lot of issues related to AHCI:

00:43:34.854982 AHCI#0P0: Cancelled task 7
00:43:34.855589 AHCI#0: Port 0 reset
00:43:50.165909 AHCI#0P0: Cancelled task 31
00:43:50.165928 AHCI#0: Port 0 reset
00:44:05.474666 AHCI#0P0: Cancelled task 31
00:44:05.474685 AHCI#0: Port 0 reset
00:44:35.781838 AHCI#0P0: Cancelled task 31
00:44:35.782117 AHCI#0: Port 0 reset
00:44:43.107712 AsyncCompletion: Task 0x00000131801a40 completed after 98 seconds
00:44:43.107728 AsyncCompletion: Task 0x00000131801ac0 completed after 98 seconds
00:44:43.107734 AsyncCompletion: Task 0x00000131801a80 completed after 98 seconds
00:44:43.108556 AsyncCompletion: Task 0x00000131801b40 completed after 98 seconds
00:44:43.108572 AsyncCompletion: Task 0x00000131801b00 completed after 98 seconds
00:44:43.108605 AsyncCompletion: Task 0x00000131801b80 completed after 98 seconds
00:44:43.148090 AHCI#0P0: Flush request was active for 98 seconds
00:44:43.148101 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:43.148108 AsyncCompletion: Task 0x00000131801bc0 completed after 98 seconds
00:44:43.473168 AHCI#0P0: Flush request was active for 68 seconds
00:44:43.473183 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688476 AHCI#0P0: Flush request was active for 54 seconds
00:44:44.688495 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688838 AHCI#0P0: Flush request was active for 38 seconds
00:44:44.688850 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS

Since this is reporting the problem is with sda and not sdb, I don't think it's the physical external drive causing the problem, it's either a guest additions bug or how AHCI is implemented in VBox and interacting with Linux.

kernel-3.15.0-0.rc4.git0.1.fc21.x86_64",Chris Murphy
13235,Shutdown hangs in OS/2 guest,Windows,other,VirtualBox 4.3.14,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
14280,VirtualBox 5.0 regression: full screen mode with composite manager works incorrectly,Linux,Windows,VirtualBox 5.0.0,2015-07-15T12:35:15Z,2015-07-15T12:35:15Z,"Just upgraded to VirtualBox 5.0 (host: Ubuntu 14.04 amd64, guest: Windows).
Relevant extension pack and guest additions installed.

PROBLEM:
When switching to full screen mode, the VM screen resizes all right to fill the screen,
but the screen is dimmed (brightess is reduced). Looks similar to the effect when you
pause the VM, but not quite.

INVESTIGATION:
I narrowed down the problem to compton, a compositor for X11.
When compton is killed, the fullscreen mode works fine.

Previously, with VirtualBox 4.3.30 (and many versions before that), fullscreen mode used to work
correctly with compton.",coriolan
14212,(ipv6) multicast NS are not delivered to the guest,Windows,Linux,VirtualBox 4.3.28,2015-07-16T13:48:05Z,2015-07-16T13:48:05Z,"It seems that the guest doesn't receive (ipv6) multicast neighbor
solicitations from the router.",Maarten Hoes
14240,Oracle Linux 6.6 wont start on init 5 after install guest additions,Windows,Linux,VirtualBox 4.3.28,2015-07-20T18:41:04Z,2015-07-20T18:41:04Z,"Recently we upgrade our Oracle Linux 6.4 to Oracle Linux 6.6. Upgrade was fine. We were able to connect with no issues on Linux guest.

Then we try to upgrade the guest additions, in order to use mouse integration. Guest additions was installed successfully. Then we reboot the Linux guest. After this, we are not able anymore to use GUI to start the Linux. We are able to change the init to 3 and start the Linux, but when we use init 5, the Linux just hangs. If we deinstall the guest addition, then we can install Linux in GUI mode.

We are using Windows7 as host, and Oracle Linux 6.6 as guest. Running latest Virtual Box version, 4.3.28 r 100389. We did not find nothing in messages and dmesg output.",Antonio Cesar Rosa
14299,GUI should disable snapshot delete on running VM,Windows,Linux,VirtualBox 5.0.0,2015-07-20T21:12:01Z,2015-07-20T21:12:01Z,"This has happened a couple of times to me. I go to delete a snapshot, not realizing the VM is already running. I get an error. Thereafter, even with the VM stopped, I cannot delete any of its snapshots. Simplest fix I would recommend: disable GUI controls for deleting snapshots on running VMs.",Dale Visser
11879,USB microphone unusable in Windows 8 guest,Mac OS X,Windows,VirtualBox 4.2.12,2015-07-21T04:29:48Z,2015-07-21T04:29:48Z,"With the latest OS X host on a mid 2011 MacMini and Windows 8 32 bit guest, the guest microphone hears loud noise whenever a USB input device (camera or earphones) is selected in host. The only way to get rid of the noise is to set the guest microphone sensitivity to zero. When the line input is selected in the host, the microphone properly hears nothing.

This resembles #5869, but I cannot find the problem in the known issues, so this may be a new bug.",Andrey Gerasimenko
14313,Windows resizes to the smallest size,Windows,Windows,VirtualBox 5.0.0,2015-07-21T18:42:40Z,2015-07-21T18:42:40Z,"Virtual machine starts in the tiny winndow (smallest possible size). With guest additions installed and without them.

If the auto adjust option is on and trying to resize with the mouse the window is blinking and right after the mouse buttom is up the window resizes to the smallest size again.

But with fully expanded window and in the full screen everything works correct.

As I suppose VirtualBox fails o detect curent guest screen size and sets the smallest windows size every time exept full screen and expanded cases.

Tested with:[[BR]]
VirtualBox 5.0 (4.3.38, 4.3.30) tested with (and without) guest addition of corresponding versions[[BR]] 
Host Windows 7 (latest updates) fresh install [[BR]]
Guest Windows 7 (latest updates)[[BR]]
Intel hd graphics 4600 drivers 10.18.14.4222[[BR]]",Lester
14314,Allow copying & pasting files between host and guest,all,all,VirtualBox 5.0.0,2015-07-21T19:04:22Z,2015-07-21T19:04:22Z,"Now that drag-and-drop of files is supported between host and guest, it would be nice if in addition to that you could copy the files (by selecting, right-clicking and choosing Copy from the context menu) on the host/in the VM, and then paste them in the VM/on the host.",Jernej Simončič
10686,Kernel Panic: MONITOR/MWAIT,Linux,Linux,VirtualBox 4.1.14,2015-07-25T03:44:42Z,2015-07-25T03:44:42Z,"I'm running Slackware 13.37 x86 host and guest on VirtualBox 4.1.14, this is on a Sony Vaio with a Intel Core i3, and when I try to boot the Slack guest it kernel panics and gives me this message;

kernel panic not syncing: Attempted to kill the idle task!
atkbd serio0: Spurious ACK on isa0060/serio0. Some program may be trying 
to access hardware directly

I'm attaching a screen shot to this bug report you can also see.

I have a desktop running an AMD and the guest will boot and run just fine, it's only on my Vaio with the i3 that it won't boot, so I recompiled the kernel 3.4.3 hoping this would help with no luck.

I've also attached the VB log....

I also noticed that if I try to boot the Slackware 13.37 CD it too won't boot on the Sony and kernel panics and locks up as well.

I read there seems to be an issue here with Slack and i3/i5/i7 cpus?

I hope someone might know a fix for VB OSE 4.1.14 I can apply to get this to bootup?

THANKS

P.S. Since I'm running Slackware and I compiled the OSE version into a slackware package, this is the build script I used;

http://slackbuilds.org/repository/13.37/system/virtualbox/

Until this gets updated, I'm not able to use 4.1.16....

",DasFox
13546,Support virtual Wi-Fi adapters with at least UDP tunneling,all,all,VirtualBox 4.3.18,2015-07-25T12:05:57Z,2015-07-25T12:05:57Z,"I know requests for a virtual Wi-Fi adapter have been made before
(see[https://www.virtualbox.org/ticket/8564 #8564]),
but my reasons for wanting one are very different from that ticket.

Rather than bridge mode,
I'm asking for a virtual Wi-Fi adapter that can use at least UDP tunneling. Just that mode. No bridging necessary.

This mode alone will allow tools like [http://www.gns3.com/ GNS3]
to emulate Wi-Fi networks, which would in turn
revolutionize network professionals' training.

Ideally, whether an adapter is Wi-Fi or not should be readable by APIs,
since there are slight differences in the rules for them that GNS3
would need to apply (namely,
that multiple devices can connect to one Wi-Fi adapter,
whereas there can be only one ""cable"" for each Ethernet adapter).",boen_robot
14330,Guest OS still show black sreen when it startup,Windows,Windows,VirtualBox 5.0.0,2015-07-27T02:15:37Z,2015-07-27T02:15:37Z,"Guest OS is windows 8.1 x64 or windows 10 x64.
When guest os startup ,after windows splash screen,it is still show a black screen when 3D acceleration is enabled.I have to force to close the guest OS.When 3D acceleration disabled it works fine.

",binary
14331,PXE boot fails on NAT network,all,Linux,VirtualBox 5.0.0,2015-07-27T15:26:39Z,2015-07-27T15:26:39Z,"Hello,
I created guest(Linux/Red Hat 64-bit). Set NAT network for this guest.
I set external tftp server and file:
{{{
alexey@rualty-mac:~$ VBoxManage modifyvm ""test4"" --nattftpserver1 192.168.2.2
alexey@rualty-mac:~$ VBoxManage modifyvm ""test4"" --nattftpfile1 pxelinux.0
}}}
According to tcpdump guest successfully download pxelinux.0 form server, but couldn't get  config file.
Server several times retried to send file to the guest (see attach pxe-nat-doesnot-work.txt).
While PXE boot through bridged network works fine (see attach pxe-bridged-works.txt) 
",Alexey Tyapkin
14289,Drag and drop failing from vm to host,Windows,Windows,VirtualBox 5.0.0,2015-07-28T09:31:39Z,2015-07-28T09:31:39Z,"With latest Virtualbox 5.0 r101573 and updated guest additions, Host Win7, Guest XP, I'm able to drop files from host to vm but not the opposite.

I get a ""Drag and drop error from guest (VERR_INVALID_PARAMETER)."" followed by VBOX_E_IPRT_ERROR (0x80BB0005), component GuestWrap, interface IGuest {13a11514-402e-022e-6180-c3944de3f9c8}
",ctrl
14344,Strange characters appended to clipboard 10.10.4 to Win 7,Mac OS X,Windows,VirtualBox 5.0.0,2015-07-29T14:24:53Z,2015-07-29T14:24:53Z,"This happened multiple times when pasting from both a Chrome and Safari window in OS X 10.10.4 (host) into Windows 7 Ultimate N (guest) on both 4.x and 5.x versions of Virtualbox.

Strangely it seemed to happen less often with Safari but that could just be a coincidence because sometimes it would not happen at all, however each time I was copying the exact same text, a C# class from a github raw file view.

Another note is that if I did not copy a second time, the paste would always be the same and contain the same extra/strange characters on the end, however it would never be in the clipboard on the mac/host side, only on the windows/guest side.

I tried posting this before by including the strange text and I received errors that my post was not long enough (and then lost my entire post  :oops: ) so I am including these as images now to hopefully prevent this issue...

[[Image(http://i.imgur.com/FNNdLWR.png)]]

[[Image(http://i.imgur.com/HFWHfX3.png)]]

[[Image(http://i.imgur.com/q6TRolM.png)]]

[[Image(http://i.imgur.com/c88JA9m.png)]]

[[Image(http://i.imgur.com/YSFEuRU.png)]]

[[Image(http://i.imgur.com/25XBw6l.png)]]

[[Image(http://i.imgur.com/RiWYHtn.png)]]

[[Image(http://i.imgur.com/n8Y6Odw.png)]]

[[Image(http://i.imgur.com/FNNdLWR.png)]]",virtualrox
14352,Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057),Windows,Windows,VirtualBox 4.3.30,2015-07-30T21:43:49Z,2015-07-30T21:43:49Z,"After an upgrde from 4.3.12 to 4.3.30, I get the 'Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057)' error. this error has prevented me from upgrading from 4.3.12 to any later version.",dinsdale
14354,"Simple Feature request: Please Change the ""Input"" Menue",Windows,other,VirtualBox 5.0.0,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
13582,3D fails in Ubuntu 14.10 Guest,Windows,Linux,VirtualBox 4.3.18,2015-07-31T09:27:01Z,2015-07-31T09:27:01Z,"This may be related to bug [https://www.virtualbox.org/ticket/12941 ] but is with the newer release of ubuntu and verified on the latest virtualbox 4.3.18 release and a variety of guest additions (including latest 4.3.19 test).

vboxvideo fails to load either via compiz or in tests using `/usr/lib/nux/unity_support_test`, giving the following error:

{{{
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

This means that ubuntu falls back to llvmpipe rendering, so uses 100%+ CPU continuously. 
This is with a Window 8.1 host, ubuntu 14.10 guest (clean install from latest ubuntu ISO)",markh
14267,Guest windows 7 x64  crashes in BSOD after upgrading to VB v5.0 unless nested paging left OFF,Linux,Windows,VirtualBox 5.0.0,2015-07-31T11:07:36Z,2015-07-31T11:07:36Z,Recently I upgraded to VB 5.0 on Linux Mint host machine. When I try to start my Windows 7 x64 guest machine it enters BSOD with 0x0000007E exception unless I switch nested paging feature OFF. Under VB 4.3 it was on and ok. Attaching VBox.log for more details.,dvb15
14274,BSoD in VBoxNetLwf with d1,Windows,other,VirtualBox 5.0.0,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
14345,Windows 10 crash with 3D acceleration,other,Windows,VirtualBox 5.0.0,2015-08-01T11:30:35Z,2015-08-01T11:30:35Z,"I found a different ticket about it, but for a previous version and marked as resolved.  I can't find that now.
I am using the latest Virtualbox.

When 3D acceleration is enabled, various programs (such as Visual Studio 2015) crash.  Also, the screen is flickery.

I am using Virtualbox 5.0.0-101573 on Linux.  My GPU is a GeForce GT 740 with NVIDIA drivers.  I will be attaching the log file",Mikemk
14245,Guest Additions are broken when built with new versions of system Mesa,Linux,Linux,VirtualBox 4.3.28,2015-08-01T20:20:57Z,2015-08-01T20:20:57Z,"Most Linux distributions use system versions of Mesa instead of the bundled Mesa 7.2. But with new versions of Mesa Guest Additions are broken. For example, glxinfo reports (null) for ""OpenGL renderer string"" and other glGetString() requests.

This patch from Fedora is used for new Mesa support by various distributions:

http://cvs.rpmfusion.org/viewvc/rpms/VirtualBox/devel/VirtualBox-4.3.10-mesa_guest.patch?revision=1.1&root=free&view=markup

Likely it's incomplete.

Perhaps Virtual Box 5.0+ should support Mesa 10+ because Mesa 7.2 is really old.",Pulfer
14375,VM apparently becomes inaccessible after shutdown,Linux,Windows,VirtualBox 5.0.0,2015-08-02T19:25:40Z,2015-08-02T19:25:40Z,"Steps:[[BR]]

1) Start VM[[BR]]
2) Do some work[[BR]]
3) Shutdown[[BR]]
After that some VMs always show the state ""inaccessible"". It is possible to remove it. Later on it is not possible to add this VM due to an error:[[BR]]
VBoxManage registervm /u00/HDD/W764.2015/W764.2015.vbox
VBoxManage: error: Could not find an open hard disk with UUID {9d2e777b-dc39-40fc-b1b8-8661dd13bd84}[[BR]]
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports[[BR]]
VBoxManage: error: Context: ""OpenMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())"" at line 85 of file VBoxManageMisc.cpp[[BR]]
[[BR]]

Workaround (not always working):[[BR]]
4) Use VBoxManage showhdinfo <virtualdisk vdi name>. (This command may produce no output, in this case registering VM is not possible.)[[BR]]
5) Add VM back if the previous command provided the information about vdi disk.[[BR]]
[[BR]]
After repeating steps 1-3 VM becomes inaccessible again.
",zoman
13407,VirtualBox Extension pack fails to install due to missing privileges,Linux,Windows,VirtualBox 4.3.16,2015-08-03T03:15:45Z,2015-08-03T03:15:45Z,"I have tried upgrading the VirtualBox Extension Pack, but both removing the existing extension as well as adding a new one failed with my user privileges. The UI reported an error related to the SHELL variable instead of missing privileges and did not attempt to raise privileges (by asking for the password) to write to a directory.

See log for details:

{{{
00:03:16.930642 ExtPackInst ExtPack: Executing '/usr/lib64/virtualbox/VBoxExtPackHelperApp''install' '--base-dir' '/usr/lib64/virtualbox/ExtensionPacks' '--cert-dir' '/usr/lib64/virtualbox/ExtPackCertificates' '--name' 'Oracle VM VirtualBox Extension Pack' '--tarball' '/home/rbu/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.3.16-95972.vbox-extpack' '--sha-256' '93b01ac2c575388ea6ae994450907c24e30a788c271ae9ff18512a06f28d9abd'
00:03:16.955177 ExtPackInst ExtPack: enmReason=1 iStatus=127 stderr='The value for the SHELL variable was not found the /etc/shells file
00:03:16.955191 ExtPackInst 
00:03:16.955192 ExtPackInst This incident has been reported.
00:03:16.955194 ExtPackInst '
00:03:16.955231 ExtPackInst ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={The installer failed with exit code 127: The value for the SHELL variable was not found the /etc/shells file
00:03:16.955246 ExtPackInst 
00:03:16.955248 ExtPackInst This incident has been reported.}, preserve=false

}}}
",rbu
14387,Application Error when Plugging/Unplugging HDMI for second display,Windows,Linux,VirtualBox 5.0.0,2015-08-04T13:10:09Z,2015-08-04T13:10:09Z,"When unplugging/plugging in HDMI cable for second display on my laptop, I receive dialog ""VirtualBox.exe - Application Error"", ""The instruction at 0x80165d4a referenced memory at 0x00000018.  The memory could not be read.""

I am running a Windows 8.1 host, with Ubuntu 14.04 as the guest.",cmo
14399,Background VMs are halted when Host is shuting down,Windows,all,VirtualBox 5.0.0,2015-08-05T20:30:19Z,2015-08-05T20:30:19Z,"I see the great feature in VirtualBox 5!!! Its posibility to run virtual machines in background. Its very cool and must have feature.
But!! When i shutdown my windows host machine it halts all background virtual machines. It is not funny. Why halt it? It is better to susspend it by default. Isn't it?

So great tool. Great new features. But fix this ""little bug"" please.",artkor
2097,Minimize to task bar on key,Windows,Windows,VirtualBox 2.0.0,2015-08-06T20:26:22Z,2015-08-06T20:26:22Z,"Feature Request: Add key to go from Full Screen to minimized (hidden in task bar). Switching back to V.B. shall enter Full Screen again.
",A20_user
10105,Implement a keyboard shortcut key to minimize a fullscreen VirtualBox VM guest window,other,other,VirtualBox 4.1.8,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
14395,"vbox 5 host firewall blocks bridged networking, used to work in 4.3.20",Windows,Windows,VirtualBox 5.0.0,2015-08-09T06:33:20Z,2015-08-09T06:33:20Z,"I migrated from vbox 4.3.20 on a w7/64 host to vbox 5 & later to 5.01

I run Bitdefender Internet security on my host

VM's (w7) that used to work with bridged networking under vbox 4.3.20 no longer can access internet. Disabling the Bitdefender host firewall solves the issue. accessing local web resources on the intranet such as a NAS management webpage does work. So it looks like the new network adapter of 5.x is causing the issue

NAT does work with the host firewall enabled.",Frank Bevers
14422,"Video playback in Windows guest badly compromised, as seen in Chrome and Firefox (but not VLC Video player!)",Linux,Windows,VirtualBox 5.0.0,2015-08-10T11:13:56Z,2015-08-10T11:13:56Z,"Environment is:

Machine: Thinkpad Yoga laptop with I7-4600U processor and Intel HD Graphics 4400.

Host: Debian 8.0 AMD64 latest (XFCE4 window manager, though should have no effect)

Guest: Windows 8.1 64bit pro , with 2D and 3D acceleration enabled in VirtualBox.

VirtualBox: 5.0

Installed the ""guest additions"" in the guest.

Problem description:


(A)

Playing any YouTube video (e.g. https://www.youtube.com/watch?v=1Y0kX7dfGKU ), in any resolution (even 144px!),

 * lags so bad that viewing is unbearable,

 * very clear vertical sync problem (i.e. half new frame on upper part of screen, half old frame on lower part of screen), and

 * the audio output is stuttering (indicating CPU overuse).

So it looks like video presentation is unaccelerated!


(B)
Installing VLC player and making it use the ""Direct2D video output"" rendering backend, produces *excellent* video playback though!

If I only knew how to switch the web browsers into this video output mode!

(There is a slight vertical sync but that's fine.)


(B.2)
In VLC, using the ""DirectX"" backend shows a black window though!

(B.3)
In VLC, using the ""Direct3D"" or ""OpenGL"" backend crashes VLC though - it just exits and there's no crash report dialog box or alike!

(B.4)
In VLC, using the ""Windows GDI"" backend produces the same video display experience as in (A), i.e. stuttering video and audio - this indicates that (A) is made completely without acceleration?

(B.5)
In VLC, using the ""OpenGL (experimental)"" backend gives no output.

(C)
The video in (A) was HTML5 video playback. Also trying Flash video playback on http://www.adobe.com/devnet/flash/articles/vidtemplate-engage-with-flash.html gives some kind of stuttering in the video and audio playback, while not nearly as bad as in (A), it's still very laggy.


",mik_
14147,XPCOM init failure when using CAPI from go on OSX,Mac OS X,all,VirtualBox 4.3.28,2015-08-13T01:08:23Z,2015-08-13T01:08:23Z,"I'm writing a VirtualBox client in go that uses the XPCOM API. It seems like the XPCOM initialization code in pfnClientInitialize fails under go's runtime environment in OSX. The same code works fine in Linux (Fedora 22 x64).

Go is gaining popularity as a systems configuration tool, so I think you should take a look.

GitHub repository with full information on reproducing the bug:
https://github.com/pwnall/vbox_bug",pwnall
9860,VirtualBox Bridged Networking Service Is not installed with Virtual Box 4.1.6,Windows,Windows,VirtualBox 4.1.6,2015-08-13T16:29:31Z,2015-08-13T16:29:31Z,"I installed VB 4.1.6. Apparently it install fine. I then created a new virtual machine. I changed the networking settings to use ""Bridged Adapter"" in the Attached To list. However the Name list is empty. The dialog would not save the configuration because ""Invalid settings detected"". Same thing with earlier version of Virtual Box. The ""VirtualBox Host-Only Network"" is fine, but the bridged network adapter was not installed.",Fernando Quintero
11663,Host-only adapter slows down DNS resolution tremendously,Windows,other,VirtualBox 4.2.10,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
8866,Guest network not able to reach beyond host's network when host bridged adaptor is using LACP (bonding),Mac OS X,Linux,VirtualBox 4.0.6,2015-08-13T17:06:13Z,2015-08-13T17:06:13Z,"We have a Mac OSX host using Snow Leapord. We've bonded two of its network card to create bond0 and it uses LACP.

When the guest uses bond0 as a bridged adaptor it is only able to reach other guests on the same machine and the host itself but can't go beyond that. 
The guest I'm using is Ubuntu 10.04 64-bit.
 ",John Huong
4214,VirtualBox 2.2.4 and bonded host interface with guest bridge networking,Linux,other,VirtualBox 2.2.4,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
11005,Unable to ping guest from host in host-only network; ping6 works,Mac OS X,Linux,VirtualBox 4.2.0,2015-08-13T17:29:28Z,2015-08-13T17:29:28Z,"An environment with a VM that has 2 types of networks: 1 NAT, 1 Host-Only [[BR]]
NAT works fine for world access but for internal access to the host, the IPv4 is not working even though IPv6 works fine [[BR]]

The host is running MacOSX 10.7.5 [[BR]]
The Guest is an Ubuntu 11.10 [[BR]]

Host virtual switches
{{{
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 0a:00:27:00:00:00
vboxnet1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 
	ether 0a:00:27:00:00:01
	inet 10.100.100.1 netmask 0xffffff00 broadcast 10.100.100.255
	inet6 fe80::800:27ff:fe00:1%vboxnet1 prefixlen 64 scopeid 0x9  
	inet6 2000:aaaa::1 prefixlen 64
}}}
Ping6 test from host to guest
{{{
nightwatch:~ ricky$ ping6 2000:aaaa::2
PING6(56=40+8+8 bytes) 2000:aaaa::1 --> 2000:aaaa::2
16 bytes from 2000:aaaa::2, icmp_seq=0 hlim=64 time=155.398 ms
16 bytes from 2000:aaaa::2, icmp_seq=1 hlim=64 time=0.715 ms
16 bytes from 2000:aaaa::2, icmp_seq=2 hlim=64 time=1.023 ms
16 bytes from 2000:aaaa::2, icmp_seq=3 hlim=64 time=0.840 ms
16 bytes from 2000:aaaa::2, icmp_seq=4 hlim=64 time=0.929 ms
16 bytes from 2000:aaaa::2, icmp_seq=5 hlim=64 time=0.875 ms 
16 bytes from 2000:aaaa::2, icmp_seq=6 hlim=255 time=0.909 ms
16 bytes from 2000:aaaa::2, icmp_seq=7 hlim=255 time=0.873 ms
16 bytes from 2000:aaaa::2, icmp_seq=8 hlim=255 time=0.864 ms
16 bytes from 2000:aaaa::2, icmp_seq=9 hlim=255 time=0.739 ms
16 bytes from 2000:aaaa::2, icmp_seq=10 hlim=255 time=0.756 ms
16 bytes from 2000:aaaa::2, icmp_seq=11 hlim=255 time=1.067 ms
^C
--- 2000:aaaa::2 ping6 statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.715/13.749/155.398/42.709 ms
}}}
Ping Test from Host to Guest
{{{
nightwatch:~ ricky$ ping 10.100.100.2
PING 10.100.100.2 (10.100.100.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 10.100.100.2 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
nightwatch:~ ricky$ 
}}}
Guest Network Configuration
{{{
ricky@bunker:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:41:4f:1b
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe41:4f1b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1180 (1.1 KB)  TX bytes:2240 (2.2 KB)
eth1      Link encap:Ethernet  HWaddr 08:00:27:9d:08:1d
          inet addr:10.100.100.2  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe9d:81d/64 Scope:Link
          inet6 addr: 2000:aaaa::2/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:168 errors:0 dropped:0 overruns:0 frame:0
          TX packets:238 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20887 (20.8 KB)  TX bytes:23841 (23.8 KB)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
pimreg    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:1472  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
}}}
Ping6 Test from guest to Host
{{{
ricky@bunker:~$ ping6 2000:aaaa::1
PING 2000:aaaa::1(2000:aaaa::1) 56 data bytes
64 bytes from 2000:aaaa::1: icmp_seq=1 ttl=64 time=0.317 ms
64 bytes from 2000:aaaa::1: icmp_seq=2 ttl=64 time=0.518 ms
^C
 2000:aaaa::1 ping statistics
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.317/0.417/0.518/0.102 ms
ricky@bunker:~$ ^C
}}}",Rick
7405,When RDP to VM is terminated badly - VM still holds RDP session open,Linux,Windows,VirtualBox 3.2.8,2015-08-13T17:32:44Z,2015-08-13T17:32:44Z,"Now my Vista machine is a piece on junk and likes to lock up. So it needs cold rebooting. The problem is that the vrdp tcp connection stays established on the Linux machine even after rebooting the vista machine. So I cannot reconnect back to my running VM and also have not been able to force it to disconnect. I've tried below with no success.
{{{
VBoxMange controlvm winxp_work vrdp  off
VBoxMange controlvm winxp_work vrdp  on
}}}

I see from netstat that the VM still thinks there is a RDP session established. Even when the keepalive timer times out - it just resets rather then closing the connection. Occasionally if I wait long enough - I can reconnect - but we are talking 15min plus.


Some details:
 1. Virtual Box installed (3.2.8r64453) on 64bit Linux host (amd64 all distro version).
 2. Win XP 32 bit guest installed with latest Virtual Box tools.
 3. VM started with ""VBoxHeadless -s winxp_work &""
 4. VBoxHeadless disown'ed from bash to stop it killing it if I close shell
 5. Access VM from Vista 64 via remote desktop
 6. Linux iceweasel 2.6.30.4-2 !#7 SMP Tue Aug 11 17:12:39 MDT 2009 x86_64 x86_64 x86_64 GNU/Linux
 7. Using a bridged interface

Does anyone have any ideas how I can convince the VM that the RDP session is over - or maybe I need to change some global tcp settings somewhere?
{{{
iceweasel:~ # netstat -ntap | grep VB
tcp        0      0 0.0.0.0:3389            0.0.0.0:*               LISTEN      26054/VBoxHeadless
tcp        0  49850 192.168.124.7:3389      192.168.124.3:1116      ESTABLISHED 26054/VBoxHeadless
iceweasel:~ # netstat -ntap --timer
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    Timer
...
tcp        0  49850 192.168.124.7:3389      192.168.124.3:1116      ESTABLISHED 26054/VBoxHeadless  on (95.16/9/0)
}}}",Adrian
4370,Guest fails to start w/VLAN Interface in OSX,Mac OS X,other,VirtualBox 3.0.2,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
14385,Guest  Ubuntu 15.04 (64 bit) crashes on Host Windows 7 AND 10 (each 64bit) after upgrading to VB v5.0 unless nested paging left OFF,Windows,Linux,VirtualBox 5.0.0,2015-08-14T09:17:52Z,2015-08-14T09:17:52Z,"I upgraded to VirtualBox 5.0.0-101573 three weeks ago, from VirtualBox v4.3.30.
Today I also tried Testbuild 5.0.1-101908.

With the new versions 5.0.X I cannot use my Ubuntu 15.04 (64 bit) VM anymore, unless I turn nested paging off. When it is turned on Ubuntu crashes and restarts when I try to access the VM.
I tried it on both Windows 7 and Windows 10 Host (each 64 bit).

For now, I reverted to VirtualBox v4.3.30 which runs it fine.

It looks like it is the same error as #14262 and #14263, although Guest/Host are the opposite.",Aweman
14423,2nd screen window - Fail to open,other,other,VirtualBox 4.3.30,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
14440,Guest program runing with wrong account,Windows,Windows,VirtualBox 5.0.2,2015-08-14T14:21:55Z,2015-08-14T14:21:55Z,"When you start or run any programs on guest it's will run under system account, not specified by ''--username'' one.[[BR]]
This bug occurred by Guest Additions 5.x only.

Thanks. ",EAX
14442,Detachable GUI - Seamless mode not implemented,all,all,VirtualBox 5.0.2,2015-08-14T16:28:52Z,2015-08-14T16:28:52Z,"This is a placeholder for implementing the Seamless mode with the detachable GUI mode. Goal would be equivalent behaviour compared to 4.3.30.[[BR]]
[[BR]]
Currently nothing will be displayed when switching to Seamless mode after starting the VM headless and attaching the GUI to it.",Max D
14261,Bridge network,Windows,Linux,VirtualBox 5.0.0,2015-08-15T01:28:49Z,2015-08-15T01:28:49Z,"Since my upgrade to Virtual Box 5, I have 2 issues :

1/ My Bridged Network does not work anymore, I had to switch to NAT",daredevil
14443,Regression: cannot execute Windows Performance Index,Mac OS X,Windows,VirtualBox 5.0.2,2015-08-15T09:39:39Z,2015-08-15T09:39:39Z,"With latest version 5.0.2 Windows Performance Index fails to be updated with an error generated from the OS, the driver or other components and also Aero effects are disabled. This issue was absent on previous 5.0.0 version.

OS guest is Windows 7 Ultimate 32 bit
OS host is MacOS X Yosemite (latest version available)
Guest additions where updated.

Note: the VM was suspended when I've updated from version 5.0 to 5.0.2 and it crashes when I attempted to start the first time. I had to trash saved state to use it.",Kirirur
14377,No Network-Adapters found after Windows 10 Installation,Windows,Windows,VirtualBox 5.0.0,2015-08-15T10:06:52Z,2015-08-15T10:06:52Z,After Installation of Windows 10 pro upgrade from Windows 7 pro no networkadapters are selectable under the VMs properties Network->Networkbridge and also under Network->Host-only Adapter. The same bug was found after new installation of VirtualBox. ,arcor.de
14449,"VirtualBox replaces the ""\"" to ""/"" in file names of disks on Linux",Linux,all,VirtualBox 4.3.30,2015-08-15T18:18:07Z,2015-08-15T18:18:07Z,"VirtualBox saves invalid filenames of disks in the virtual machine configuration file (.vbox): backslashes is replaced with slashes. The file attribute is in vbox /VirtualBox/Machine/MediaRegistry/HardDisks/HardDisk/location saved the wrong disk names.
In linux backslashes common names disks, for example, in the directory /dev/disk/by-partlabel/.",empty is reserved
14455,Error writing to a file froma SMB share - shared through VirtualBox,Linux,Windows,VirtualBox 5.0.2,2015-08-16T13:00:39Z,2015-08-16T13:00:39Z,"Summary:  This problem is similar to ticket # 14252.  Have upgraded to 5.0.2r102096, however, problem still exists.  Did not have problem with version 4.3.28.  Can create a file, delete the file, but cannot modify the file that is an SMB share, shared via VirtualBox to guest systems.

Issue:  Connect a SMB share to Linux host and share it via VirtualBox to guest VMs.  In Linux Guest VM access shared folder via mount /media/sf_Shared.  Can create file, however, cannot modify file.  Receive the following error:  ""The document cannot be saved, as it was not possible to write to /media/sf_Shared/lin.txt.  Check that you have write access to this file or that enough disk space is available.""  In Linux guest delete file works.  With a Windows 8.1 Guest VM access shared folder via G: drive (\\vboxsvr\Shared).  Can create file, however cannot modify file lin.txt.  Receive error:  ""An unexpected error occurred while writing G:\lin.txt.""  In Windows guest delete file works.  Also,  created file from both Linux and Windows guest systems and then accessed the file from the host.  Confirmed permissions set on the file were correct.  Can modify the file via the host.

Temporary Workaround:  In both Linux and Windows guest systems connect to SMB server directly (\\mestor\Shared).  Can modify files.

Host System:
HP envy15t with 16GB RAM, Intel i7-4700MQ, Sandisk SSD 120GB drive
Xubuntu - 15.04 - Vivid
VirtualBox version 5.0.2 r102096

Linux Guest System:
Kubuntu - 14.10 - utopic
Guest Additions version 5.0.2r102096

Windows Guest System:
Windows 8.1 - 6.3 build 9600
Guest Additions version 5.0.2r102096

Sincerely,

Charles",GrizzlyWullf
13748,Java8 GUI Apps not working in Linux guest,Windows,Linux,VirtualBox 4.3.20,2015-08-17T11:24:07Z,2015-08-17T11:24:07Z,"My Host is Windows 7 Enterprise Build 7601 SP1
My Guest is Suse Enterprise Linux Server 11 SP3 with GuestAdditions.

I installed jdk8u25 and eclipse STS Version 3.6.3.RELEASE Build 201411281415 Platform Eclipse Luna SR1 (4.4.1)
and when i try to start eclipse i get following error message:

{{{
ES2 Prism: Error – reported GLX version = 1.2
GLX version 1.3 or higher is required
}}}

This seems to be caused by the eclipse internal webbrowser.

And the problem seems to be that the glx version provided by the virtual box's graphic card driver is just too old.

The only way i was able to solve the issue was to downgrade java to jdk7u71.",mmoossen
14460,Error starting VM - E_FAIL 0x80004005 SessionMachine,Windows,Windows,VirtualBox 5.0.2,2015-08-17T17:30:54Z,2015-08-17T17:30:54Z,"I am getting virtualbox error ""Failed to open a session for the virtual
machine xxxxx.""  The VM session was aborted. See screenshot attachment
for complete error. 

This happens when I start any virtual machine just after launching the
virtualbox manager.  I try the start a second and sometimes third time
and the machine will launch and function normally.  When it shuts down,
I also get an error but everything is being saved inside the machine.

I am running Windows 10 Pro (64-bit) on an HP desktop (I7 processor
with 32gb of memory).  This only started after upgrading to version 5
of virtualbox.  I have tried the original 5.0 version, the 5.01 test
version and am now on 5.02 r102096.  The guest machine doesn't seem
to matter - they all receive the error.  Guests include Windows 10
Enterprise, Windows 2008 R2 server, Windows 7, and Windows 2003 R2
server.

Attached is the screenshot of the error and a clean log (cleared before
starting virtualbox and getting error).",_Dale_
14414,No DNS server information on DHCP enabled NATNetworks,Linux,Linux,VirtualBox 5.0.0,2015-08-17T19:28:16Z,2015-08-17T19:28:16Z,"I've configured a NATNetwork with DHCP enabled:

{{{
NetworkName:    NatNetwork
IP:             10.0.3.1
Network:        10.0.3.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
loopback mappings (ipv4)
        127.0.0.1=2
}}}

It created a DHCP server configuration like this:
{{{
NetworkName:    NatNetwork
IP:             10.0.3.3
NetworkMask:    255.255.255.0
lowerIPAddress: 10.0.3.4
upperIPAddress: 10.0.3.254
Enabled:        Yes
}}}

When the VM is started it requests the IP address to DHCP server. On the DHCP response (DHCP ACK package) there is no DNS information, but there is the Domain Name (DNS suffix).

If I manually configure the DNS in the virtual machine to 10.0.3.1 the name resolution works.
",jacksonfoz
14464,dwFileAttributes Incorrectly Reports FILE_ATTRIBUTE_REPARSE_POINT,Windows,Windows,VirtualBox 5.0.2,2015-08-17T19:54:27Z,2015-08-17T19:54:27Z,"With a Windows guest running within a Windows host, executing the FindFirstFile Win32 API function on the guest returns the incorrect dwFileAttributes with FILE_ATTRIBUTE_REPARSE_POINT for symlinks on the vboxsf.

With symlinks on Linux & Mac hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to false.

With symlinks on Windows hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to true.

FILE_ATTRIBUTE_REPARSE_POINT should be set to false for all vboxsf files/folders, because being a symlink should only be relevant to the host, and the information should be hidden to the guest.

This is causing us some issues doing PHP development involving symlinked folders, because PHP likes to try and follow the reparse points to convert relative paths to canonical paths.  It attempts to retrieve the reparse point info to conver to the canonical path, then fails.


To reproduce the issue:

On the Windows host, create a folder at c:\test

Create a subdirectory at c:\test\myDir

Create a symlink:

{{{
mklink /D c:\test\myLink c:\test\myDir
}}}

Create a VirtualBox shared folder pointing to c:\test , and mount it to X: within the guest.

Run the attached Python script:

{{{
python find_data.py X:\myLink
}}}

On the Windows host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 1024
Attributes: 1040
}}}

On a Linux/Max host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 0
Attributes: 16
}}}",Matt Hopkins
14470,NAT Network failing to provision gateway,Windows,Linux,VirtualBox 5.0.2,2015-08-18T21:01:03Z,2015-08-18T21:01:03Z,"Creating a new NAT Network using the GUI WITHOUT DHCP server results in a network with the gateway address at x.y.z.1 however gateway fails to respond to ping and fails to forward traffic upstream.  Stopping and restarting VirtualBox does not resolve gateway non-functionality.

NAT Network created WITH DHCP server responds to ping and forwards traffic upstream.  Removing/disabling the DHCP server does not cause loss of gateway functionality.  Functionality maintained across restart of VirtualBox.",VirtualBryan
14473,"No emails from answers to my tickets, adding address to the CC field impossible",other,other,,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
14281,Mac OS X Installer can't install because VirtualBox is running,Mac OS X,all,VirtualBox 4.3.30,2015-08-19T15:19:45Z,2015-08-19T15:19:45Z,"In trying to upgrade Boot2Docker this morning, I ran into an issue where the installer would not proceed as it claimed VirtualBox was still running. I then tried to install VirtualBox 4.3.30, upgrading from 4.3.28, and the VirtualBox installer was gated on the same issue asking me to stop all VMs and processes. A quick process check showed the following:

{{{
mbp:~ me$ ps aux | grep VB
me             1135   0.2  0.0  2451240   7088   ??  S     7:10AM   0:00.05 /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD
me             1137   0.2  0.1  2532164  11260   ??  S     7:10AM   0:00.13 /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC --auto-shutdown
me             1147   0.0  0.0  2450180    684 s000  S+    7:10AM   0:00.00 grep VB
}}}

If I kill the processes using kill -9, the installer then works. I am running on Mac OS X 10.10.4. I am not sure if this is an issue with the 4.3.30 installer or if it's an issue with 4.3.28 with lingering processes?",damnhandy
14463,Symlinks in shared folders don't work after upgrading to 5.0.2,Windows,Linux,VirtualBox 5.0.2,2015-08-20T20:35:47Z,2015-08-20T20:35:47Z,"I'm running CentOS 7 as a guest on a Windows 10 host machine. When using 5.0.0 or the test build, 5.0.1, symlinks work fine but once I upgraded to 5.0.2, they stopped working.

The symlink is relative to 2 directories up and was created in Windows 10 as follows:
mklink /D rpclib ..\..\node-rpclib

I tried downgrading the Guest Additions from 5.0.2 to 5.0.0 and that didn't fix the problem so it seems related to the VirtualBox 5.0.2 program itself since after downgrading to 5.0.0 it went back to working

Here's the VBox.log from 5.0.0: http://gobin.io/mTII
Here's the VBox.log from 5.0.2: http://gobin.io/ZJuK

Let me know if you need any more information.",fastest963
13771,Crash When Entering Seamless/Fullscreen Mode,Windows,all,VirtualBox 4.3.20,2015-08-21T02:31:11Z,2015-08-21T02:31:11Z,"VirtualBox v4.3.20/4.3.21 crashes when I enter Fullscreen or Seamless mode. The guest OS will run perfectly in a regular window, but once you try to switch to one of those two modes it crashes after about a second or two. It doesn't matter what the guest is (Windows or Linux) and I have the guest add-ons installed in both of them. I'm running Windows 7 64 as my host OS. I have 20 GB of RAM and an Intel Core i7, so power isn't a problem. The crash is repeatable, even across versions and clean installs. I wiped out my VMs and my settings, then booted a LiveCD and the same error happened.

Here's the actual error: '''The Instruction at 0x00000000 referenced memory at 0x00000000. The memory couldn't be written. Click OK to terminate the program.'''
",BrandonGolway
14483,Option to allocate memory dynamically,all,all,VirtualBox 5.0.2,2015-08-21T22:51:41Z,2015-08-21T22:51:41Z,Similar to the ability to allocate disk space dynamically maybe this can be also implemented for the memory to make on average more of it available to the host while having the ability that the guest can still use it if needed.,Sworddragon
14489,My Windows 7 cannot surf the Internet after I upgrade Virtualbox,Windows,all,VirtualBox 5.0.2,2015-08-24T05:42:11Z,2015-08-24T05:42:11Z,"I used virtualbox 4.3.30 before. And then I upgrade Virtualbox from 4.3.30 to 5.0.2 and 5.0.0. After I upgrade Virtualbox to those newer versions. I cannot connect any website. Finally, I uninstall newer versions and load back 4.3.30 version. It can connect website successfully.",jackzzkao
13002,Slow DNS resolving with enabled natdnsproxy,other,other,VirtualBox 4.3.10,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
14498,4k resolution on Linux + GNOME/gtk host extremely buggy,Linux,all,VirtualBox 5.0.2,2015-08-25T18:17:18Z,2015-08-25T18:17:18Z,UI components are extremely buggy wih overlaps and placement on a host with Ubuntu GNOME 3.16+ 4k resolution display.,sgnn7
14403,Symlinks are created incorrectly on shared directories,Windows,Linux,VirtualBox 5.0.0,2015-08-26T08:04:54Z,2015-08-26T08:04:54Z,"I have a trusted environment for development and I have activated symlink support for shared folders as desribed here: https://www.virtualbox.org/ticket/10085

This solution worked great so far, however since VirtualBox 5 (in combination with Win 10 host), the creation is incorrect.

If I create a symlink on a shared folder with the command

{{{
ln -s /media/sf_data/file.js /media/sf_data/test.js
}}}

The symlink is created but using readlink, I can see that the created path is incorrect:

{{{
\media\sf_data\test.js
}}}

The backslash should be replaced by a slash.

If I create a symlink outside the shared folder, everything is correct. Also if I create a symlink pointing to a file in a shared folder. However if I create a symlink within a shared folder to a file outside the shared folder, the bug exists.",MathiasB
14504,VM VirtualBox crashes on Windows Server 2008 r2,Windows,other,VirtualBox 5.0.2,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
14505,VM desktop migrate to current desktop after wake up,Linux,Windows,VirtualBox 5.0.2,2015-08-27T08:45:35Z,2015-08-27T08:45:35Z,"1. I have three virtual desktops (""workspaces"" in xfce terminology)
2. Usually I run VM's windows on ""VBOX"" desktop
3. When I switch to other ""workplace"" , hibernate computer an then wake it up, VM's desktop show at current workplace which is annoing ",Kamil Jońca
14495,Guest crash when drag and drop file into it on Linux host,Linux,all,VirtualBox 5.0.2,2015-08-27T09:14:29Z,2015-08-27T09:14:29Z,"When I drag a file to a Windows XP guest, the virtual machine crash and state change to ""Aborted"". 
Tried Linux Mint guest, same problem. 
",FiveYellowMice
14485,PCI IDE controller (PIIX4) has incorrect programming interface,all,all,VirtualBox 5.0.2,2015-08-27T09:36:07Z,2015-08-27T09:36:07Z,"The programming interface field of the PCI configuration space for the PCI IDE controller (PIIX4) as configured in http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/Storage/DevATA.cpp is incorrectly specified as 0x8a.  The PIIX4 datasheet (e.g. http://www.microbe.cz/docs/82371AB%20PCI-TO-ISA_IDE%20XCELERATOR%20(PIIX4).pdf) page 91 states it should be 0x80 instead.

The current value 0x8a is invalid because it incorrectly informs drivers that the device supports switching to PCI native mode when by writing 0x8f back to the programming interface field when it does not (specifically, the emulated device does not honour writes to pci configuration space addresses 0x8 through 0xb).

The fix is to either change the current value to 0x80 (line 7446 of DevATA.cpp) or fully implement mode switching in the driver.  The former is probably better as it better emulates the PIIX4.",jncronin
7211,Captured mouse pointer is not released with Right-Control keypress on Windows when Canadian Multilingual Standard keyboard layout is active,Windows,other,VirtualBox 3.2.6,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
14513,OpenGL error with 3D acceleration enable with black screen,Windows,Linux,VirtualBox 4.3.30,2015-08-27T20:58:30Z,2015-08-27T20:58:30Z,"Hi,

I'm running Ubuntu 14.04 lts trusty 64 bit on 4.3.30 r101610 on Win 7 host 64 bit.
I'm getting too many OpenGL warning and my rendering screen is going black. I'm
running gazebo robotic simulator. However if I do not use hardware acceleration then everything work fine and there are no warning. But then by simulation run very slow.
I've done almost everything regarding this issue as this is not new. I've installed the VBoxGuestAddition_4.3.30.iso. Before installing the guest addition the 3d hardware acceleration work fine and I do not get openGL warning. However I'm not able to go to fullscreen.
I've also installed latest virtual box extension pack.

Please share any suggestion.",AmitUbu
14514,VM freezes during installation of guest,Windows,Linux,VirtualBox 5.0.2,2015-08-28T07:09:02Z,2015-08-28T07:09:02Z,"I am trying to install openSUSE 13.2 and in the middle of the installation everything just stalls. I am able to move the mouse around and operate dialog boxes/buttons inside openSUSE but the installation itself completely froze.
Process Explorer confirms it where I/O activity completely stops in the middle of loading files. It never stops in the same spot always. Once it got as far as installing half the applications that come with the OS, most of the time it doesn't even make it to the first one.

On average it's about 10 minutes into the session that this happens. Once it stalls, there is no possible way to terminate the VM. If I manage to close the window, the process will remain in memory (and I cant start the VM again). I cannot even normally restart my host PC. I have to press the button on the computer to force restart. If I try to terminate the VM after the freeze, it interferes with the functioning of my host OS. Some programs I can't open at all such as CMD, other operations will be extremely slow and so on.",Inds
13828,Drag-and-drop not working in either direction,Windows,Linux,VirtualBox 4.3.22,2015-08-28T07:26:12Z,2015-08-28T07:26:12Z,"Host: Windows 7, all latest updates
Guest: XUbuntu 14.04.1, all latest updates

Drag-and-drop does not work in either direction.  I have tried changing the menu option to enable it only in one direction, as well as bidirectional, but nothing works.

I've checked the manual, and it says drag-and-drop should work for a Windows host and Linux guest.  But in this case it doesn't.

Shared folders do work, so that's my workaround for the moment.  (Although there's another bug for shared folders to report separately.)

The clipboard does work for copying text in both directions.  It does not let me copy files in either direction.  It's not clear from the manual whether it should, but I have to assume it's text-only.  (This is a shame, when VMware Player does it fairly seamlessly.)",gbartlett
14517,Menubar disappears in fullscreen mode when 3D acceleration is activated in VM settings,Windows,Windows,VirtualBox 5.0.0,2015-08-29T13:32:13Z,2015-08-29T13:32:13Z,"Hello,[[BR]]

I think that I found a bug:[[BR]]

I have a VM running with guest OS Windows 8.1 on a Windows 10 host (both 64bit). The problem that occurs is that the menubar disappears in fullscreen mode when I click into the VM (e.g. on the desktop or a window of the VM). If I click on the host desktop on my second screen after this, the menubar will appear again. However, if I click into the guest again the menubar will disappear again. The problem only occurs when I have activated 3D acceleration in the VM settings. 2D acceleration doesn't cause that problem.[[BR]]

If you need more information you can feel free to contact me.",JKLs
14522,Unity 3D supported: no,Mac OS X,Linux,VirtualBox 5.0.2,2015-08-30T21:39:57Z,2015-08-30T21:39:57Z,"I'm trying to get OpenGL (3d) working in a Ubuntu 15.04 guest. 

I've installed VBOXADDITIONS_5.0.2_102096 but `/usr/lib/nux/unity_support_test -p` says:

{{{
pci id for fd 4: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string:   VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits)
OpenGL version string:  3.0 Mesa 10.5.2

Not software rendered:    no
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+:       yes

Unity 3D supported:       no
}}}

I also get a message about ""vboxvideo: module verification failed"":

{{{
$ cat /var/log/syslog|grep vbox
Aug 30 23:14:09 udev vboxadd[8667]: Starting the VirtualBox Guest Additions ...done.
Aug 30 23:14:10 udev vboxadd-service[8754]: Starting VirtualBox Guest Addition service  ...done.
Aug 30 23:14:10 udev systemd[1]: vboxadd-service.service: control process exited, code=exited status=1
Aug 30 23:14:10 udev systemd[1]: Unit vboxadd-service.service entered failed state.
Aug 30 23:14:10 udev systemd[1]: vboxadd-service.service failed.
Aug 30 23:14:42 udev kernel: [14302.735185] vboxvideo: module verification failed: signature and/or  required key missing - tainting kernel
Aug 30 23:14:42 udev kernel: [14302.736192] [drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0
Aug 30 23:14:42 udev kernel: [14302.942282] vboxguest: misc device minor 56, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
Aug 30 23:14:42 udev kernel: [14302.942283] vboxguest: Successfully loaded version 5.0.2 (interface 0x00010004)
Aug 30 23:14:42 udev kernel: [14306.524633] vboxsf: Successfully loaded version 5.0.2 (interface 0x00010004)
Aug 30 23:14:42 udev systemd-modules-load[188]: Inserted module 'vboxvideo'
Aug 30 23:14:43 udev vboxadd[634]: Starting the VirtualBox Guest Additions ...done.
Aug 30 23:14:43 udev vboxadd-service[896]: Starting VirtualBox Guest Addition service  ...done.
Aug 30 23:14:43 udev systemd[1]: vboxadd-service.service: control process exited, code=exited status=1
Aug 30 23:14:43 udev systemd[1]: Unit vboxadd-service.service entered failed state.
Aug 30 23:14:43 udev systemd[1]: vboxadd-service.service failed.
}}}

",motomo
13847,vpnc no response from target after upgrade to 4.3.20 and 4.3.22,Windows,Linux,VirtualBox 4.3.22,2015-08-30T23:54:57Z,2015-08-30T23:54:57Z,"Host is Win7, Guest is OEL6.  Have been using vpnc to connect to Cisco VPN for several years.  After upgrade of VirtualBox from 4.3.12 to 4.3.20 it stopped working with ""vpnc: no response from target"". Restarting guest and host did not help. Downgrading to VirtualBox 4.3.12 resolved the issue. Tried upgrading to VirtualBox 4.3.20 again, just in case a driver got hosed during first attempt, but it did not work.  Reverted back to 4.3.12 and having been running that for months now.

Today I tried upgrading to VirtualBox 4.3.22, hoping the issue would be fixed, but it still doesn't work.  I tried the same reboot guest and host after upgrade but no luck.  Reverted back to 4.3.12 and it works fine now.",Dave Musci
13752,VM freezes after leaving Haiku operating system running for several hours,Linux,other,VirtualBox 4.3.18,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
14525,Mini toolbar does not show up in fullscreen mode,Solaris,all,VirtualBox 5.0.2,2015-08-31T21:14:08Z,2015-08-31T21:14:08Z,"When the guest VM is set to full screen mini-tool bar disappears.
It appears for a while when I switch between application (Alt+Tab) but disappears when VM gets focus.
Looks like the mini-tool bar is not a part of VM window but runs in a separate window.

The problem not fixed in development build VirtualBox-5.0.3-SunOS-amd64-r102322.

Host: OpenIndiana 151a9 x86_64 (pkgadd says 'Detected Solaris 11 Version 151'),
VirtualBox 5.0.2-SunOS-amd64-r10209, Extension Pack: 5.0.2-102096

Guests: Linux 32 and 64 bits, Windows 32 and 64-bit.",virtit
14518,Can't install Guest Additions in Windows 10 guest under Windows 8.1,Windows,Windows,VirtualBox 5.0.2,2015-09-01T12:50:37Z,2015-09-01T12:50:37Z,"I have never been able to install the Guest Additions ever since I first tried the Technical Preview of Windows 10 and VirtualBox 4.28 or 4.30.  It has always failed when installing the WDDM driver.

This is the case with the current VirtualBox test build 5.0.3r102322 and its Guest Additions 5.0.3.102316.

I attach the machine log and a screen shot of the Guest Additions installation.  As the machine is unusable after the Guest Additions intended installation, I was only able to get its installation log by attaching the virtual disk to another Windows 7 VM.  However, it doesn't show any errors.

I did a machine reset but, on reboot, I still had a blank screen and had to ""power it off"".  I restored the machine to a saved VBox snapshot in order to be able to use it.
",c273
14263,Unable to start Windows 10 64 build 10162 (preview) guest under i686 Linux host: The digital signature for this file couldn't be verified,Linux,Windows,VirtualBox 5.0.0,2015-09-02T09:02:00Z,2015-09-02T09:02:00Z,"I have troubles trying to run the preview of Windows 10 64 build 10162 (Windows10_InsiderPreview_x64_EN-US_10162.iso) under Linux (i686 PAE) using VirtualBox 5.0.

When I try to boot my Windows 10 64 guest I see this error message:

Recovery

Your PC/Device needs to be repaired

The digital signature for this file couldn't be verified.

Error code: 0xc0000428

My ISO file is correct (verified using SHA1 hash: 31346458255afeac1afeed5c4c61f15d57708b9b)

My host is: Linux 4.1.0 i686 PAE, 16GB of RAM
My guest is: Windows 10 64

People with a totally different HW configuration also have this problem.

This is a cross post from here: https://forums.virtualbox.org/viewtopic.php?f=2&t=68840",Artem S. Tashkinov
14322,BSOD on Windows 7 upon hibernating while VirtualBox is open,Windows,Linux,VirtualBox 4.3.30,2015-09-02T21:52:59Z,2015-09-02T21:52:59Z,"I have a recurring problem where I get a blue screen of death when I hibernate my computer while I have VirtualBox open. I'm running Windows 7 64-bit with a xubuntu on Ubuntu 14.04 (trusty) guest. I'm also using version 4.3.30 of virtualbox and version 4.3.24 of the guest additions. My BSOD provided the following information: the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL, and was attributed to VBoxNetFlt.sys. I ran WinDbg on the MEMORY.DMP (full dump, not minidump) and got the following info:

{{{
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03253890
    Debug session time: Fri Apr 10 15:50:18.376 2015 (UTC - 4:00)
    System Uptime: 3 days 14:35:58.020
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    
    Loading unloaded module list
    ................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {112337, 2, 0, fffff80003076615}
    
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+10634 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000112337, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003076615, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  0000000000112337 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertQueueApc+69
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800bffb710 -- (.trap 0xfffff8800bffb710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80003341a58 rbx=0000000000000000 rcx=000000000011232f
    rdx=fffffa800a6373e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003076615 rsp=fffff8800bffb8a0 rbp=fffff880009e8180
     r8=0000000000000001  r9=000000000011231f r10=fffff880009e8c01
    r11=fffffa800fd26b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KiInsertQueueApc+0x69:
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8] ds:00000000`00112337=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003083469 to fffff80003083ec0
    
    STACK_TEXT:  
    fffff880`0bffb5c8 fffff800`03083469 : 00000000`0000000a 00000000`00112337 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0bffb5d0 fffff800`030820e0 : fffff880`0bffb738 fffff800`03083153 ffffffff`8000297c fffffa80`105c1060 : nt!KiBugCheckDispatch+0x69
    fffff880`0bffb710 fffff800`03076615 : fffff880`00000001 fffffa80`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0bffb8a0 fffff800`030656b0 : fffffa80`105c1060 00000000`00000000 00000000`00000078 fffffa80`0a6373d0 : nt!KiInsertQueueApc+0x69
    fffff880`0bffb8d0 fffff880`04c10634 : 00000000`00000000 00000000`778e7ac0 00000000`00000078 00000000`000007ff : nt!KeInsertQueueApc+0x80
    fffff880`0bffb930 fffff880`04c107b4 : 00000000`0000ed04 fffff880`04c3cf50 ffffffff`8000397c fffffa80`1769b6c0 : avgidsdrivera+0x10634
    fffff880`0bffba10 fffff880`04c10866 : ffffffff`8000397c fffffa80`1769b6c0 fffffa80`168f6520 00000000`000007ff : avgidsdrivera+0x107b4
    fffff880`0bffbac0 fffff880`04c2925c : 00000000`00000001 fffff880`0bffbba8 fffffa80`0fd26b50 fffff880`0bffbba8 : avgidsdrivera+0x10866
    fffff880`0bffbb10 fffff800`0337cb43 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`0fd26b50 : avgidsdrivera+0x2925c
    fffff880`0bffbb40 fffff800`0308da95 : fffff800`03338b00 fffff800`0322b201 fffffa80`0fd26b00 fffffa80`00000000 : nt!IopProcessWorkItem+0x23
    fffff880`0bffbb70 fffff800`03322b8a : fffffa80`105029d0 fffffa80`0fd26b50 00000000`00000080 fffffa80`0698eb30 : nt!ExpWorkerThread+0x111
    fffff880`0bffbc00 fffff800`030758e6 : fffff880`03365180 fffffa80`0fd26b50 fffffa80`06d40290 00000000`07fa1011 : nt!PspSystemThreadStartup+0x5a
    fffff880`0bffbc40 00000000`00000000 : fffff880`0bffc000 fffff880`0bff6000 fffff880`0bffb8a0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    avgidsdrivera+10634
    fffff880`04c10634 84c0            test    al,al
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  avgidsdrivera+10634
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avgidsdrivera
    
    IMAGE_NAME:  avgidsdrivera.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55128c2a
    
    FAILURE_BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    Followup: MachineOwner
    ---------
}}}

Please provide any assistance you can on determining the cause of and solution to this problem.",Anomaly13
14537,Linux grsecurity guest kernel will not mount shared folders,Windows,Linux,VirtualBox 5.0.2,2015-09-03T15:44:23Z,2015-09-03T15:44:23Z,"My guest is an Arch Linux 64-bit VM running kernel 4.1.6.201508230818-1-grsec (latest from official Arch repos as of this report). Since installing the grsecurity kernel, mount.vboxsf will fail with a Protocol error. The following is logged to dmesg when attempting a mount:

{{{
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
}}}",kballen
14539,Extreme screen flashing and guest unusable,Windows,Linux,VirtualBox 5.0.2,2015-09-03T18:32:46Z,2015-09-03T18:32:46Z,"While this issue started on Windows 10 and I understand there are[[BR]]
problems there, I have since rebuilt the host machine from scratch[[BR]]
with Windows 8.1 and am still experiencing problems although they have[[BR]]
changed some.
For the history of this issue please see:
https://forums.virtualbox.org/viewtopic.php?f=6&t=69906&p=334049#p334049

Environment
> VirtualBox 5.0.2
> Latest extension pack installed
> Windows 8.1 host
> Ubuntu 14.04 guest

Current problem
1) When starting up the guest the guest window flashes. It is very extreme
2) On some starts when guest starts in full screen mode, the minibar is visible during startup but then is no [[BR]]
longer visible. 
3) The guest periodically becomes unresponsive. [[BR]]
The screen looks perfectly normal but does not respond[[BR]]
to mouse clicks. I have assumed keyboard input as well but to [[BR]]
be completely accurate, I have not tested that. However, it does[[BR]]
seem that the UI has frozen. Nothing within the guest window responds[[BR]]
including the OS bar at the top of the Ubuntu window where you[[BR]]
can shut-down the OS.
4) The screen will be come black
* This is happening in fullscreen and normal view.

I have attached logs
I marked this critical as I'm unable to use my dev environment[[BR]]
and get work done. I understand it may not be critical in your view.
Sincerely,
Karl",kekeke
14540,No files for DOS applications in VBox shared folder,Windows,Windows,VirtualBox 5.0.2,2015-09-04T09:14:48Z,2015-09-04T09:14:48Z,"A DOS application (Foxpro, XtreeGold) can't read list of files in a shared folder. Windows app can see all files. This problem is properly described in https://www.virtualbox.org/ticket/8551 - but there is no solution.

Host (32 bite): Windows 8, Windows 10
Guest (32 bite): Win XP",DanielR
13728,Win 7 Guest/Linux host - integrated webcam on Dell 5520 laptop - black display,Linux,Windows,VirtualBox 4.3.20,2015-09-05T15:15:34Z,2015-09-05T15:15:34Z,"On a Dell 5520 laptop, Fedora 64 bit 21 host, Win 7 64 bit guest, the integrated webcam provides nothing but a black display on passthrough, but on direct connect, the video shows but very slow/choppy.

It works fine on host applications.

An external USB camera works fine passthrough on the same system.

Attached is log.",H0wdy
14523,Windows 98 boot Crashes straight to Guru debugging.,Windows,Windows,VirtualBox 5.0.2,2015-09-05T19:33:17Z,2015-09-05T19:33:17Z,"When i load up windows 98 and attempts to load the GUI/System, It crashes stright to Guru debugging. I have the log attached. For the screenshot? Just black. Not the worth if its black. Can you please find out whats going on?",HSF3232
14548,Add VirtIO drivers for Windows to guest additions image,all,Windows,VirtualBox 5.0.2,2015-09-06T13:24:46Z,2015-09-06T13:24:46Z,"User need to manually install VirtIO drivers on Windows guests using drivers from [http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers Linux-KVM.org driver download page] or prebuilt driver ISO from [https://fedoraproject.org/wiki/Windows_Virtio_Drivers Fedora Project] in order to use VirtIO networking on Windows guests.
Embedding this drivers into Guest Additions installer for Windows could be quiet useful.",invite_ciel
14551,Sound Blaster Direct mode failure,other,all,VirtualBox 5.0.2,2015-09-07T14:33:24Z,2015-09-07T14:33:24Z,This easy and very useful for education mode is still not realized or buggy. :-( It works at Dosbox emulation. The example with sources is attached.,litwr
14479,Virtual box hangs/crashes on VM rename,Windows,other,VirtualBox 5.0.0,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
14557,with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile,Windows,all,VirtualBox 4.2.32,2015-09-08T15:54:29Z,2015-09-08T15:54:29Z,with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile which then break vms when logging into another pc on same domain,clive darra
14559,"GUI: ""Ungroup"" fails",Windows,Linux,VirtualBox 5.0.4,2015-09-09T08:31:38Z,2015-09-09T08:31:38Z,"I created a group with the same name as the only single VM in it, ""oS-TW"", using the ""Group"" feature new in 5.0.  When trying the ""Ungroup"" function, I get the following error:

{{{
Failed to save the settings of the virtual machine oS-TW to C:\Users\voelkerb\VirtualBox VMs\oS-TW\oS-TW\oS-TW.vbox.

Could not rename the directory 'C:\Users\voelkerb\VirtualBox VMs\oS-TW\oS-TW' to 'C:\Users\voelkerb\VirtualBox VMs\oS-TW' to save the settings file (VERR_ALREADY_EXISTS).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
}}}

The VBox.log remains untouched during this, thus not attached.",berny
14561,Failed to open a session for the VM (0x80004005  Component:  MachineWrap),Windows,Linux,VirtualBox 5.0.4,2015-09-09T11:29:06Z,2015-09-09T11:29:06Z,I have a problem. Not start a new VM,SergeyO
14512,Windows XP guest OS does not start,other,Windows,VirtualBox 5.0.2,2015-09-09T14:49:55Z,2015-09-09T14:49:55Z,"I'm using Ubuntu Trusty. Under VirtualBox 4.3.10_Ubuntu R93012, my other OSs (e.g. Debian, openSuse) startup OK. However, Windows XP (my only Windows OS) starts up OK but then displays a window with details of NS_ERROR_FAILURE (0x80004005).

Carried out install of VirtualBox 5.0.2 from LocutusOfBorg's ppa (https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/). Once I'd removed old Extension Pack & installed Extension Pack 5.0.2 from Oracle's site, Windows XPp & other guest OSs started OK.

It's OK on my desktop as detailed above. However, I've just tried the same updates on my laptop. It installs VirtualBox 5.0.2 & its Extension Pack OK. However, starting Windows XP gives a slightly different error:
Failed to open a session for the virtual machine WindowsXP.
Unsupported version 56 of data unit 'PATM' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

PS this is logged on Launchpad (for Ubuntu) as bug 1489279",John Rose
9390,Mac OS X guest video memory remains on 4MB. It does not use the video memory setting of the guest configuration.,Mac OS X,OSX Server,VirtualBox 4.1.0,2015-09-10T02:57:35Z,2015-09-10T02:57:35Z,It does not matter what setting you choose for video memory (0 - 128 MB) for a Mac OS X server guest. The guest OS always reports that there is only 4MB screen memory available. Please see my attached screen shots for the guest Os report. This is evident when trying to use screen share to the guest OS. The screen share quality is in very low. This also could be the cause of the jerky graphics inside the guest OS normal operation eg. the menu navigation. ,Pieter
14568,Regression: protocol error if the host folder name differs from share name,Linux,Linux,VirtualBox 5.0.4,2015-09-10T13:44:00Z,2015-09-10T13:44:00Z,"I remember many years ago in VBox 2 or 3 there was an issue that name of the folder on host system has to match the name of the share for it to work properly. In 4 it worked properly though. Now on 5.0.4 I've encountered the same issue again:

on host:
1. mkdir ~/vm-shared
2. mkdir ~/test

in VBox UI:
1. add folder ~/vm-shared with name ""shared""
2. add folder ~/test with name ""test""

on guest (under root):
1. mkdir /mnt/shared && mount -t vboxsf -o uid=1000,gid=100 shared /mnt/shared
2. mkdir /mnt/test && mount -t vboxsf -o uid=1000,gid=100 test /mnt/test

now on guest, try to execute following command:
1. mkdir /mnt/shared/somedir
2. mkdir /mnt/test/somedir

Second command executed successfully, but first command fails with protocol error.",indifferent
14436,Host screen saver do not start on VirtualBox 5,Windows,Windows,VirtualBox 5.0.0,2015-09-10T16:20:44Z,2015-09-10T16:20:44Z,"When there is a virtual machine running and the relative window is active, the screen saver of the Host, when the time is elapsed, starts but terminates immediately.
Tested on VirtualBox v5.0 and v5.0.2
Host tested: Win 7 x64 Professional SP1
Guests tested: Win 7 x64 Ultimate SP1 and Windows XP x86 SP3
",bmn
14378,Cannot access VirtualBox menus in full-screen mode,other,other,VirtualBox 5.0.0,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
14560,Regression - networking broken after upgrade to 5.0.0 and also subsequent updates,Windows,all,VirtualBox 5.0.4,2015-09-10T19:01:26Z,2015-09-10T19:01:26Z,"This worked with 4.3.x, but the problem started with upgrade to 5.0.0 from 4.3.28, but continues with every minor update - after installation, start-up of every virtual machine reports:

  Cannot connect to the network interface '\DEVICE\{C5EF3C32-2A5B-4649-B646-5A5D3A3BB319}'. The virtual network card will appear to work but the guest will not be able to connect. Please choose a different network in the network settings.

The problem is with !VirtualBox Host-Only Ethernet Adapter.

I tried to restart computer after update, but still the same problem.

Removing and re-adding !VirtualBox Host-Only Ethernet Adapter from !VirtualBox menu does not help.

The Device Manager with ""Show hidden devices"" option enabled shows that ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" has exclamation mark with detail ""This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"".

Please note that I am using 192.168.150.0/24 network for !VirtualBox Host-Only adapter (IP 192.168.150.2, mask 255.255.255.0, DHCP 192.168.150.3, dynamic address from 192.168.150.100 to 192.168.150.199), because ''the default address 192.168.56.0/24 is my regular network''.

When I uninstall and install !VirtualBox, the ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" device still reports the same problem. I need to uninstall !VirtualBox first, reboot and install !VirtualBox afterwards in order to get the networking up-and-running again (after changing the IP and DHCP of the Host-Only adapter from !VirtualBox menu).

This is reproducible with every update, starting from 5.0.0.

I am using Windows 7.

Do you need more info from me?",oldium
14566,E_FAIL (0x80004005) MediumWrap.cpp[2245],Windows,all,VirtualBox 5.0.4,2015-09-11T07:59:48Z,2015-09-11T07:59:48Z,"Ever since the upgrade to VirtualBox 5 I'm unable to add/modify storage controllers or optical drivers.
Either VirtualBox crashes or quits silently. Error is still present even with 5.0.4.2546.",wpa1160
14581,RAM Mapping,all,all,VirtualBox 5.0.4,2015-09-13T08:59:42Z,2015-09-13T08:59:42Z,"It would be great to include RAM Mapping to disk for a VM.

So the VM would allocate RAM directly to disk (mapping) instead of using the host RAM if specified (even though it may be slow but there are SSDs). It would be funny to see VMs with 208 Gb of RAM.

**Preview of how it would look like if implemented** : [[Image(http://zupimages.net/up/15/37/9lgj.png)]]",Ley0k
14582,Hostonlyif not fully initialized after create returns successful,Windows,other,VirtualBox 5.0.4,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
14452,Installing VirtualBox 5.0.2 blocks network on host (Windows 10),Windows,other,VirtualBox 5.0.2,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
14591,Critical Error - Failed to create VirtualBoxClient COM object,Linux,other,VirtualBox 5.0.4,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
14592,Can't use unscaled HiDPI with Linux guest if display scaling enabled in OS X Yosemite host,Mac OS X,Linux,VirtualBox 5.0.4,2015-09-15T19:20:48Z,2015-09-15T19:20:48Z,"Host is a MacBook Pro running OS X Yosemite 10.10.5, connected to a 3840x2160 display. Guest is Debian 8 with KDE 4.14.2, guest additions installed. I am attempting to run the guest OS in full-screen mode.

Display scaling is enabled in the host, with the scaled resolution set to 2560x1440. If ""Use Unscaled HiDPI Output"" is UNchecked, the guest correctly sees 2560x1440 as a resolution choice, and defaults to it.

If ""Use Unscaled HiDPI Output is checked, then the display does not work properly. The highest resolution reported to the guest appears to be 2560x1600 (not 3840x2160 as it should be), and for some reason the resolution selected by default is 1024x2880 (which isn't even a valid resolution). This results in the entire display being compressed into a narrow vertical strip up the middle of the screen, with everything squeezed to illegibly small size. Manually selecting 2560x1600 in the guest results in a similarly unreadable rectangle in the center of the screen.

Disabling display scaling on the host results in correct guest behavior, allowing guest to access full 3840x2160 native resolution. Unfortunately, this results in UI elements on host OS X desktop being unusably small. So it seems it is impossible to have both a usable host desktop, AND give the guest OS access to the full native display resolution.

To summarize, the functionality of the Use Unscaled HiDPI Output checkbox appears to be broken in 5.0.4, at least for the hardware/software configuration described above.",MikeUatCS
14603,"Installation fails on Windows 7 trying to access ""quick launch"" folder",Windows,other,VirtualBox 5.0.4,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
14606,Virtual Screen menu > Resize to 2560x1080?,all,all,VirtualBox 5.0.4,2015-09-18T14:08:30Z,2015-09-18T14:08:30Z,"This is feature request:

I'd like to see Resize to 2560x1080 in View > Virtual Screen menu, There is not yet any resolution supporting ultra wide resolution.

For example Dell uses this resolution.
http://www.dell.com/ed/business/p/dell-u2913wm/pd",zikzak
14070,Virtualbox all guest operating system crashed,Windows,all,VirtualBox 4.3.26,2015-09-19T04:30:29Z,2015-09-19T04:30:29Z,"Hi!

My Virtualbox version 4.3.26.98988
My config: Asroc H55M-LE, Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, 8GB RAM Windows 8.1 Professional 64 bit, ATI RADEON HD 5570

If running guest computer, a few seconds freeze. The same problem 32 or 64 bit.

The work is still in version 4.0.26.

(pasted log file removed)",agostonl119
14569,Full screen flicker Linux guests,Windows,Linux,VirtualBox 5.0.4,2015-09-21T07:58:46Z,2015-09-21T07:58:46Z,"Hello.

I installed VirtualBox 5.0.4 and have tried to install various distributions (Ubuntu 14.04 and Debian 8). In all, after installing the ""guest additions"" when I put the screen in ""full screen"" mode gives me small black image flashes. For example when you open the Control Panel Ubuntu or run a program. If I'm in windowed mode it works perfectly.

I have the following equipment:

Windows 8.1
FX8350
32 GB of RAM
GTX 760
2560x1440 resolution monitor

However on my laptop which has exactly the same software works perfectly full screen. The laptop has the following features:

Windows 8.1
Intel i7 4700-HQ
16 GB of RAM
GTX 750m
1920x1080 resolution monitor

I tried to change the resolution of the desktop PC to 1920x1080 and also happens.

P.D. Sorry for the translation

Thanks",bysurferox11
13452,Please add workdir argument to guestcontrol exec,Linux,Linux,VirtualBox 4.3.16,2015-09-21T09:42:31Z,2015-09-21T09:42:31Z,"I'm working on virtual build-test factory, based on VirtualBox. VBoxManage guestcontrol helps immensely, but tasks such as 'make' often need concrete folder to run in. Because of that I have to use construct as following, wrapping everything under bash command:

{{{
VBoxManage guestcontrol ""$ARG_VM_NAME"" exec --wait-exit --wait-stderr \
--image ""/bin/bash"" --username $VM_USER_LOGIN --password $VM_USER_PASSWORD \
-- -c ""cd '/mnt/ramdisk/$BUILD/buildroot' && make images""
}}}

It would be very helpful to have --workdir or similar argument to guestcontrol exec, similarly to process spawning libraries in programming languages and libraries.",indifferent
14368,Connecting Kemper Profiling Amplifier To VM Aborts the VM,Linux,Linux,VirtualBox 5.0.0,2015-09-21T15:11:23Z,2015-09-21T15:11:23Z,"Connecting Kemper Profiling Amplifier (KPA) [http://www.kemper-amps.com/] via USB to a virtual machine aborts the VM.

I have tried with both Linux and Windows guests. No problems when connecting KPA to Linux or Windows machine directly.

Nothing is written to VBox.log when KPA is connected to VM. The VM just shuts down and the state in VirtualBox GUI becomes ""Aborted"".

In the attached VBox.log you can see bootup of Kubuntu 14.04 VM. After the VM had booted up, I connected KPA to it (nothing written to VBox.log at this point).

In the lsusb-kpa.txt you can see the output of command lsusb -v -d 133e:0001",Janne Rönkkö
14624,STATUS_OBJECT_NAME_NOT_FOUND,Windows,Windows,VirtualBox 5.0.4,2015-09-22T12:15:12Z,2015-09-22T12:15:12Z,"VirtualBox build: 5.0.5-102800-Win

Host: Windows 10
Guest: any VM (Windows XP, Ubuntu, CentOS)

Message error:
""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)Make sure the kernel module has been loaded successfully.
where: supR3HardenedWinReSpawn
what:  3
VERR_OPEN_FAILED (-101) - File/Device open failed.
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.""

Driver verifier disabled for :
vboxnetadp6.sys
vboxnetlwf.sys
vboxusbmon.sys

I can boot any VM with the driver verifier disabled for all drivers, not when only disabled for the oracle drivers above.

Wich  others drivers must get out  of Driver Verifier ?

",Leonardo Lira
14616,Firefox.com Firefox can't completely Download files,Windows,Linux,VirtualBox 5.0.4,2015-09-22T15:26:48Z,2015-09-22T15:26:48Z,"I have been running into what appears to be a bug with !VirtualBox.  

Host OS is Windows7 SP1 x64 with the latest updates.
Guest OS is Centos 7.1 x64 with the latest updates. 

When we use Firefox from www.firefox.com,  it freezes when we try to download a file.

Steps to reproduce:

1.  Start Guest OS
2.  Immediately launch Firefox (38.2.1ESR or the latest 40.x release) and try to download a file (In our case, it is a epub file, http://www.cse.yorku.ca/~jr/epub/w/CV.epub)
3.  Firefox should them freeze

If you close the VM and restart the VM, Firefox should be able to download the file. If you reboot the host and retry the steps above you will reproduce the FF download failure. 


If you look a Wireshark trace during the download you actually see the file start to download, but it seems that it isn't getting fully processed/closed/or TCP session closed. 

Google Chrome/wget  doesn't have this issue. It seems to tied to the FF from firefox.com

I am able to reproduce this with !VirtualBox 5.0.2 and 5.0.4. !VirtualBox 4.3.30 doesn't have this issue.

See the attached log and network captures.",paulg.ca
14628,Multiple Real Monitors/Screen-Sizing issue across multiple monitors,other,other,VirtualBox 5.0.4,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
14626,"segfault Host Ubuntu 15.04 64bit on libQtGui.so, Client Windows 8.1 64bit",Linux,Windows,VirtualBox 5.0.4,2015-09-24T07:36:45Z,2015-09-24T07:36:45Z,"Working nicely on Ubuntu 15.04 (64bit), then after 1 hour it crashes:

[61110.818729] VirtualBox[2470]: segfault at 0 ip 00007fcf16f168f4 sp 00007ffcb35f3720 error 6 in libQtGui.so.4.8.6[7fcf16bc8000+aac000]",jabenitezg2
14631,Host-only interface IP changes on Windows 10,Windows,all,VirtualBox 5.0.4,2015-09-24T12:50:56Z,2015-09-24T12:50:56Z,"When using host only network interfaces on Windows 10, the interface IP address changes and the interface is not working anymore.



'''Reproduction (easy way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Open Windows 10 network settings (Control Panel\Network and Internet\Network Connections)[[BR]]
4 - Notice that the newly created network interfaces uses DHCP configurations instead of manually configured settings.[[BR]]




'''Reproduction (hard way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Create a Linux guest (such as Ubuntu 15.04), and attach it's first network adapter to the host-only interface.[[BR]]
4 - Run the guest (I chose to run in live mode to avoid to install the OS). It usually gets the first ip available, 192.168.56.101 in our case[[BR]]
5 - Ping the host interface from the guest: ping 192.168.56.1[[BR]]
6 - Check the host interface IP: it has changed to 192.168.56.102 and the host-only interface does not work anymore.[[BR]]




Tested on VirtualBox 5.0.4 and latest testing 5.0.5.[[BR]]
Tested with Linux guests (Android, Ubuntu).[[BR]]
Reproduce on Windows 10 host.[[BR]]
Can't reproduce on Linux (Ubuntu, Fedora, Debian), Mac OS (10.8, 10.9 and 10.10), Windows 7 and Windows 8.1 hosts.[[BR]]",srats
14635,A way to start (or list) all the VMs in a group,all,all,VirtualBox 4.3.30,2015-09-25T07:48:51Z,2015-09-25T07:48:51Z,"I know it's possible to start all the VM in a group using the GUI, but I can't find an easy way to do it from VBoxManage.

I would suggest to add something like:
{{{
    VBoxManage startvm --group '/groupname'
}}}
Or at least to allow easy scripting with a command that lists all the VMs in a single group, which right now is only possible with some clever scripting like this:
{{{
    VBoxManage list -l vms | awk '/^Groups:/ { groups = $2; } /^UUID:/ { uuid = $2; if (groups == ""/groupname"") print uuid; }'
}}}
(which as is doesn't support VMs in multiple groups)",Lapo Luchini
14629,VirtualBox 5.0.4-102546~Unbuntu~trusty Crashes when running more then 2 Windows Vm's,Linux,Windows,VirtualBox 5.0.4,2015-09-25T13:59:57Z,2015-09-25T13:59:57Z,When running multiple Windows Vm's at the same time the system will become unresponsive requiring a physical restart. disk usage appears to spike.    ,skiingshark
14644,Feature request: Support self-adapting framebuffer console on GNU/Linux guest,all,Linux,VirtualBox 5.0.4,2015-09-29T15:12:33Z,2015-09-29T15:12:33Z,"Currently on GNU/Linux guest vesafb will be used in the TTY console, AFAIK it is possible to manually set custom screen resolutions for VM to use but it will be better if there's a framebuffer driver that can self-adapt the size of the TTY console to the size of VM window(just as on X Window System)

Please consider it if it's possible, thanks in advance!

",林博仁(Buo-Ren Lin)
14614,Virtualbox kills keyboard when running on Windows 10,Windows,other,VirtualBox 5.0.4,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
14647,Ram Drive as another drive type,all,all,,2015-09-30T12:45:29Z,2015-09-30T12:45:29Z,"Sometimes fast save times to disk are desired. I ran a secondary disk in a guest where the vdi was actually in a ram drive on the host. The access times were very fast.

Since Virtualbox already has the ability to set aside host ram for the guest, a possibly useful service could be to set aside additional ram as a ram drive, disguising the extra ram as another vdi for the guest to see on the IDE or SATA ports. No ram drive software on the host would be necessary. 

When the disk controller is clicked in the GUI settings, another icon could be placed next to Add CD and Add Disk, Add RAM Disk, maybe a little IC chip icon. A slider in the GUI could allow adjustment of how much ram to set aside. During the guest-shutdown process Virtualbox could store the ram drive vdi's contents to a file in the guest's folder, and restore the file's contents back to the ram drive during guest boot. ",scottgus1bug
14605,Date and time on Linux guests is not updated after a session restoration,Linux,Linux,VirtualBox 5.0.4,2015-09-30T15:51:24Z,2015-09-30T15:51:24Z,"When you save the machine state and then restoring it on Linux Guest operating systems after some time the date continues to display the last one before saving and not the current date and time. The problem is not reproduced on Windows Guest, where the clock is refreshed automatically.

It might be in the way that Linux system works to retrieve the time from the hardware clock during boot process and then it is maintained by the OS, but if there is any work around would be great to cause the guest to refresh the date like issuing ""hwclock --hctosys"" automatically.",Panos Kavalagios
13816,Random crashes when NVDA or Narrator are running,Windows,all,,2015-09-30T20:12:08Z,2015-09-30T20:12:08Z,"​In general, the GUI is quite accessible with both ZoomText's Reader and NVDA (I've tested both independently); however, when NVDA is running, VirtualBox will randomly crash at certain points when using the GUI. For example, I could get it to consistently crash when opening the File => Preferences menu, and then pressing ESC to exit. Another example is that I could get all the way through creating my first VM, but then VBox crashes when clicking to create the virtual disk. As a final example, when going to the Settings menu of my VM and pressing ESC to exit/cancel, VBox crashes (I was only able to create the VM in the first place by turning off NVDA).  Please take time to investigate this issue by installing the free NVDA screen reader and just performing one of these actions while it is running.  Thank you.",IcepickSU
14648,"Virtual machines are aborted when selecting ""Contents"" from the Help menu",all,Windows,VirtualBox 5.0.4,2015-09-30T20:36:20Z,2015-09-30T20:36:20Z,"How to reproduce

* Start any virtual machine with the Manager.
* Once started, click Help in the menu.
* Select Contents.

Result:

The virtual machine(s) you're running is ""Aborted"" and comes up with this warning saying:

""unknown has generated errors and will be closed by Windows.  You will need to restart the program.

An error log is being created.""

But it works in previous versions of !VirtualBox and in the !VirtualBox GUI Manager.

Actual:

The help contents are displayed.",Tae
14652,Symbolic links cannot go up file tree on shared folder.,Mac OS X,Linux,VirtualBox 5.0.4,2015-10-02T02:14:13Z,2015-10-02T02:14:13Z,"I've set up a vagrant VM with ubuntu/trusty64 on OS X.

Attempting to create symbolic links in the shared folder that use .. to reference a directory up the tree results in a protocol error (EPROTO).

Symlinks with absolute or relative paths without going up the tree still work. 

",mstone121
14638,VT-x is not available Error while launching Android VM,Windows,Linux,VirtualBox 5.0.4,2015-10-02T18:11:26Z,2015-10-02T18:11:26Z,"Hello,

I am experiencing an error anytime I try to run an android Nexus 4 (KitKat) virtual machine. The error details are as following : 


""VT-x is not available (VERR_VMX_NO_VMX).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"" 

So far what I have read is that this error indicates the computer does not support virtualization when in fact my machine does.
Here are my computer specs:
Asus K55VD Laptop
Intel core i7-3630QM @2.40ghz
8.00gb ddr3 RAM
Samsung 850 EVO SSD",kingjulian
14655,Pithy Widget to Monitor and Control Virtual Machines,all,all,VirtualBox 5.0.6,2015-10-02T19:42:54Z,2015-10-02T19:42:54Z,"I was looking at the nine-year-old enhancement request #93 and decided the request was irretrievably broken.

The problem is that users (those like me running various multiple VMs at different times) need a really compact go-to place to check status of a VM and make quick adjustments.

We have multiple options for doing this, people!

* System Tray control (original request, MS Windows only)
* Menu bar (operationally the same as Windows tray, only on Macintosh)
* Application icon (Taskbar on windows, called taskbar on Gnome too, dock on Mac)
* ""Mini Controller"": movable, independent, tiny window (like iTunes ""Miniplayer"")

The entry points of the UI are ""small"" widgets which bear iconic images with transparency/translucency.  These should size between 16x16 and 256x256 pixels to handle the wide variety of sizes supported in various platforms.  The same display mechanism should be used wherever used - systray, menu bar, taskbar/dock, ""mini controller""

1. ""MASTER"" widget - overall VirtualBox status

This can indicate any of the following:
overall state: VB off, VB active but no running VMs, VB active with running VMs
number of running VMs: number or depiction
resource load: CPU graph of VirtualBox load as percentage of host computer, Memory load of VB in host.

Selection menu:
- Start VB
- Quit VB
- Nice shutdown all VMs (option to quit VB)
- Suspend all VMs (option to quit VB)
- Nasty poweroff all VMs (option to quit VB)
- each running VM
- each off or suspended VM
- submenu to VM groups

2. VM Group widget

Essentially the same display options as VirtualBox Master status

Selection menu same as Master except for ""Start VB"" is replaced by ""Start all VMs""

3. Virtual Machine widget

Icon display options:
- states: Off, Running, Suspended
- resource usage: CPU load, Memory load
- VM Main display thumbnail
- Guest operating system symbol (""Tux"" etc)
- VM Name
- VM's custom icon
- VM Main display Large ""Aero"" or ""Coverflow"" preview

Selection menu should be the same as the context-click menu on a VM in the VirtualBox Manager window.

DISPLAY PREFERENCE SETTINGS

- Hide taskbar/dock icon; default show overall state; alternatives show cpu/mem/etc load, numbers
- Show tray sitter (Mac menu item) as overall VB state; default do not show; alternative show cpu/mem/etc load, numbers
- Hide active VMs from menu completely; default show inline; alternative show in ""Active"" submenu
- Show inactive VMs in menu; default hide off/suspended VMs; alternative show in ""Inactive"" submenu
- Show grouped VMs inline; default show VMs in submenus named for group; alternative hide groups and their VMs
- VM group icon displays as resource load; default show as generic box; alternative show activity, numbers
- Display VM groups as separate icons in taskbar/dock
- Display VM groups as separate icons in tray/menu
- Show VM icon as resource load; default show with custom icon or OS icon; alternatives OS icon, main display as thumbnail or aero, state, other resources, name
- Display VMs as separate icons in taskbar/dock
- Display VMs as separate icons in tray/menu
- Hide MASTER widget icon from taskbar/dock
- Show MASTER widget in tray/menu
- Show vm/group/command icons in Widget top-level menu; default no icons in menus; alternative show icons in all menu levels; alternative show ""Aero"" previews in top-level menu only
- Leave ""miniviewer"" running after VirtualBox manager quits",SchemaCzar
93,Minimize main window to trayicon,other,other,VirtualBox 1.3.6,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
14667,Enhancement: Forward all USB devices except some,all,all,VirtualBox 5.0.6,2015-10-04T19:48:19Z,2015-10-04T19:48:19Z,"USB Device Filters give possibility to forward some specific USB device from host to guest.
They also give possibility to forward some set of devices specified by criteria (e.g. any Kingston-manufactured USB flash drive; great feature!).
What is missing is a possibility to make negative filters; e.g. to forward ''any USB device except keyboard and mouse'' from host to guest.

Use case 1:
For specific reasons I work mostly inside guest OS. I don't want to go to virtualbox menu and click on device every time I insert an USB device; neither I want to create filter for every manufacturer whose device I may use. (On the other hand, I can't use filter that matches all USB devices, because keyboard, mouse and some other stuff need to be in exclusion list, i.e. available to host OS, not forwarded to guest.)

Use case 1.1:
My separately-living relative (hard-learning novice in computers) works only inside guest OS. Actually, he doesn't know anything about host OS and virtualbox at all: guest OS is always in fullscreen mode, trying to behave as it's the only OS. Same problem as above: he needs all inserted USB hardware (with some exclusion list, like: keyboard, mouse, etc) to be forwarded to guest OS, but unlike use case 1 where it's all about convenience, in use case 1.1 it's a critical feature (virtualbox needs to work ''invisibly/seamlessly'' for novice user who never presses Host Key and known nothing about virtualbox menu).

Use case 2.
See https://forums.virtualbox.org/viewtopic.php?f=9&t=49100 (not my post). The topic starter uses virtualbox with guest OS for inspecting suspicious storage media; he wants all devices except some exception list to be by default forwarded to guest OS.",Sasha1024
14251,Ubuntu 14.04 guest additions breaks touchscreen cursor,Linux,Linux,VirtualBox 4.3.28,2015-10-05T07:30:04Z,2015-10-05T07:30:04Z,"Hardware: Microsoft surface Pro 3
VirtualBox 4.3.28 
Guest Additions Installed
Host : Ubuntu 14.04
Guest : Ubuntu 14.04

Hello,

After installation of the Guest Additions on the Linux guest, the Touchscreen does not work properly in Guest OS (Ubuntu 14.04).
The mouse works fine I get the cursor but I cannot control the cursor position with Touchscreen, I have already tried to calibrate the Touchscreen (xinput, calibrate Touchscreen…) but it seems like having no effects.

For information, Without the guest addition there is no problem of cursor position, I get the good positions of the Touchscreen cursor but the click doesn’t work, and with the Guest additions installed I lost the positions of the Touchscreen cursor but the click still works.

Can someone help with this issue ?
",drdr_skilled
13705,"Windows 7 Host and Linux guest, BSOD on host",Windows,Linux,VirtualBox 4.3.20,2015-10-05T22:30:45Z,2015-10-05T22:30:45Z,"I ran 4.3.12 for quite awhile.  After I jumped to 4.3.20, I am now getting BSOD every now and then.  I've done a memory scan, just to be sure I don't have failing RAM.  Anything else I can do to get more information?

I'm not sure if the windows event viewer files are useful or not, but I'm attaching them.",Trent
14657,"guest audio choppy, video lags and windows screen flickers",Windows,Windows,VirtualBox 5.0.6,2015-10-06T03:52:48Z,2015-10-06T03:52:48Z,"Host: Win7 64bit, intel i7-930 processor, VirtualBox-5.0.6-103037-Win
Guest: Win8.1 64Bit with VirtualBox_Extension_Pack-5.0.6-103037

Would also like to refer to:

issue #14633, that describes also the audio problem, but may have a different cause.

issue #4088, latency fixes (Windows hosts only; bug ), fixed in the release



To reproduce this: enable 2d/3d video acceleration for the guest, using an usb mouse

Steps to reproduce:[[BR]]

-start the guest[[BR]]-logon, during logon process the screen flickers[[BR]]
-lauch IE, again sometimes the screen flickers during startup of IE[[BR]]
-goto to youtube and start a music video.[[BR]]


-if you don't use the mouse, the sound and video are almost perfect

-hover the mouse above the playing video area[[BR]]
-rapidly move the mouse from left to right/up/down within the video rectangle
a) the sound will become ""choppy"",
b) the video seems also to lag a little


In the previous version (5.0.4) audio was constantly choppy (even without moving the mouse),
as if you put the volume control to high, like to much voltage on a speaker.[[BR]]

In the previous version (5.0.4) the video was constantly lagging, showing blocks, seems to stop some milleseconds 

After installing 5.0.6, the sound and video performs better but it's not solved.

If I disable 2d/3d video acceleration, audio is back to normal, no video lags and no screen flikkering. (don't see a benefit for enabling video acceleration)

Enabling video acceleration and using the usb mouse together seems to cause the problem.

May be both have an issue.

Attached logs and the description might lead to a solution?
",L.
12383,Chrome viewport becomes always on top when rendering pages with 3d transforms,Mac OS X,Linux,VirtualBox 4.3.2,2015-10-06T08:50:00Z,2015-10-06T08:50:00Z,"Steps to reproduce the problem:

Visit any page with a css 3d transform applied in Google Chrome or Chromium in an Ubuntu VM in VirtualBox, e.g. go to http://www.w3schools.com/css/css3_3dtransforms.asp and click the red ""3d rotate"" rectangle

Expected behavior:

The viewport should not be rendered always on top of other windows; rather, other windows should be able to display on top of the Chrome window.

Observed behavior:

The viewport (note: not the whole Chrome window, but just the viewport) becomes always on top of everything else on the screen until the Chrome window is closed. This does *not* happen in Firefox in the Ubuntu VM.

Please see http://youtu.be/cIc7O9R5eR8 for a demonstration of the bug.

As of this writing, I can consistently reproduce this in an up-to-date Ubuntu 13.10 desktop i386 VM running the latest Chrome stable (Version 31.0.1650.57) inside the latest VirtualBox (4.3.2-90405) with the latest VirtualBox guest additions installed. Unfortunately I don't have an Ubuntu system running as a host OS to test on. Therefore, I can't say that this isn't instead a bug in Ubuntu or just Chrome rather than VirtualBox, or some interaction with my settings, but I'm opening tickets in both places just to be sure.

Chromium issue is at https://code.google.com/p/chromium/issues/detail?id=322085",requiredfield
14676,NDIS6 Network Driver breaking Local Area Connection on Sleep Resume,Windows,all,VirtualBox 5.0.6,2015-10-07T03:11:35Z,2015-10-07T03:11:35Z,"There appears to be a problem with the NDIS6 driver handling power state changes. 

Since updating to VirtualBox 5.0.x, my Local Area Connection reports ""Network cable unplugged"" after waking up from sleep. 

This issues does NOT occur if i uncheck the VirtualBox NDIS6 Bridged Network Driver on the connection. 

Workaround 1: Disable the Virutalbox VirtualBox NDIS6 Bridged Network Driver on the connection

Workaround 2: disable and re-enable the interface every resume. 
 
Workaround 3: Configure the Network Adapter Hardware power management to disable ""Allow this computer to turn off this device to save power."" 

Disabling power management on the interface not only prevents the issue from occuring, but also returns it to service after a sleep/resume cycle without having to disable and re-enable the interace. 


I think this issues could be related to some other host<->guest networking problems commonly reported which I also run into. 

My Hardware: Dell Precision M4800. Intel Ethernet Connection I217-LM. Driver version 12.12.50.7205. Connected via docking station. 

I'm trying to find a way to get into debugging the driver, but could use some guidance. 
",GabeF
14258,Detachable broken when 3d acceleration is enabled,other,other,VirtualBox 5.0.0,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
14679,Deleting Snapshot Error: VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents,other,other,VirtualBox 5.0.4,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
1936,Caps lock not being properly passed through to guest,Linux,Windows,VirtualBox 1.6.4,2015-10-08T02:58:23Z,2015-10-08T02:58:23Z,"The caps lock key is not being correctly passed through to the guest,
using VBoxSDL. If I press caps lock and release it it works fine,
but if i hold down caps lock and press another character, such as j, the caps lock is sent
before the j. This is relatively
important for some assistive technologies that use the caps lock key as a 
modifier for screen reading functions.",Tyler Spivey
14685,Xubuntu 14.04LTS with Virtualbox5 freezes when you drag a window to the border,Mac OS X,Linux,VirtualBox 5.0.6,2015-10-09T12:35:18Z,2015-10-09T12:35:18Z,"Physical Machine: mac book pro, Yosemite, java7 

Xubuntu 14.04LTS + related guest addition 5.0.6
Virtualbox5 + ext pack 5.0.6

Virtual Machine freezes for XX seconds when you drag a window to the border to resize it.",En
14492,drag and drop fails on win 10 host 64bit,other,other,VirtualBox 5.0.2,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
14686,Settings GUI: Number of tabs for NICs set by extradata setting?,all,all,VirtualBox 5.0.6,2015-10-09T15:56:29Z,2015-10-09T15:56:29Z,"In this ticket https://www.virtualbox.org/ticket/2782 Technologov asks for all eight tabs of NICs to be in the GUI. The decision was to stop at four so as to not confuse new users.

This choice leaves users who need five or more nics to have to jump the hurdle of figuring out a rather long command line, which may fail completely due to typos, or worse may set things wrong, leaving more command line finagling to try to fix the error and get it right. 

I may be wrong, but I'm wondering if the first four GUI NIC tabs are established in a programming loop, or could be established that way. Then the upper end of the loop could be any arbitrary number, up to the supported 8 NICs. 

I suggest to make the number of tabs shown be controlled by an extradata setting, defaulting to four or even two. If the user wants up to all 8 to show for his special guest he could do that by changing the extradata setting.",scottgus1bug
14688,BSOD on Windows 10 with pagefusion on,Windows,Windows,VirtualBox 5.0.6,2015-10-09T21:18:36Z,2015-10-09T21:18:36Z,"I always have a BSOD on my Windows 10 Home host when starting a Windows Server 2012 guest with pagefusion on

",mvendramin
10157,Adding vCPUs degrades network performance.,Linux,other,VirtualBox 4.1.8,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
14268,Implementing VMDK relative raw disk partitions on Windows,Windows,all,VirtualBox 5.0.0,2015-10-13T13:39:01Z,2015-10-13T13:39:01Z,"This bug serves to track progress of implementing the -relative option for the '''VBoxManage internalcommands createrawvmdk -filename ... -rawdisk ... -partitions ...''' command on Windows hosts.

See [https://www.virtualbox.org/manual/ch09.html#rawdisk section 9.9.1] of the docs regarding using physical partitions as a Virtual Drive for a VM. The -relative option for the above command was only available on Linux hosts.",regedit
14699,"Wrong icon for ""Other Linux (64-bit)""",Windows,Linux,VirtualBox 5.0.2,2015-10-14T18:54:55Z,2015-10-14T18:54:55Z,"Choose[[BR]]
Type: '''Linux'''[[BR]]
Version: '''Other Linux (64-bit)'''[[BR]]


Icon the same as for '''Other Linux (32-bit)''' without 64 in left top corner.",bmx666
7094,VirtualBox kills network connectivity if VLAN tagging enabled on Realtek NIC,Windows,other,VirtualBox 3.2.6,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
14704,Windows special folders mount as read only when shared,Windows,Linux,VirtualBox 5.0.6,2015-10-15T08:46:37Z,2015-10-15T08:46:37Z,"Windows uses the 'read only' attribute for folders to indicate that the folder is a special folder such as 'Downloads', 'Documents, 'Pictures', 'Videos' and 'Music'.  Consequently this attribute is not intended to indicate that the folder is actually read only or that files should not be able to be created within it (https://support.microsoft.com/en-gb/kb/326549).  Unfortunately Virtual Box does not respect this behavior when mounting a shared folder that contains such folders.

An example of this problem is that if the 'Downloads' special folder is moved to the root directory of drive 'D:' and then drive 'D:' is shared with an Ubuntu client, then it will be impossible to create files or folders within the 'Downloads' folder from within the Ubuntu client. Nor will it be possible to change the permissions from within the Ubuntu client.

There is a workaround (https://forums.virtualbox.org/viewtopic.php?f=3&t=46541), which involves removing the read only attribute from within Windows using the command line 'attrib' command (Explorer does not permit the read only attribute to be removed from folders).

This is not an ideal solution as it removes some of the special folder behavior within Windows.  Ideally, VirtualBox should respect the normal Windows behavior of the read only attribute and ignore it.  This should be a very simple matter to fix.
",TrevorW
10436,"Virtual Box install fails (rollback, MSI code 1603) on Windows 7 64 host",Windows,Windows,VirtualBox 4.1.12,2015-10-15T13:42:19Z,2015-10-15T13:42:19Z,"I have read the posts, howtos and such and still cannot determine why my install is failing (rollback initiated during install) MSI error code 1603. 

Host: Windows 7 64 bit

Tried command line install without USB drivers. Still fails.

The only driver log created was setupapi.app.log. It and the install log are attached.

Any help would be greatly appreciated.",bobheck
14709,VBoxManage (Windows) doesn't accept paths with spaces using quotation marks,Windows,all,VirtualBox 5.0.6,2015-10-17T01:44:29Z,2015-10-17T01:44:29Z,"I need to resize a disk urgently and cannot due to this stupid bug. Can't rename folders and vdi filename to have no spaces as that causes a different error.  eg.

VBoxManage modifyhd ""Windows 10 (64-bit).vdi"" --resize 40960
returns
Syntax error: Invalid parameter '10'
",Ross
13494,Overloaded message loop makes Guest window unresponsive to inputs when guest additions installed,Linux,Windows,VirtualBox 4.3.16,2015-10-17T20:33:36Z,2015-10-17T20:33:36Z,"I'm on Ubuntu 12.04 host using LXDE desktop, and the guest is Windows XP. I haven't tested it with other Windows versions like win7. 

My old GDI+ game completely freezes the guest window after some seconds. The only the to recover is simply killing the virtualbox process. It doesn't happen when guest additions are not installed.

I decided to investigate further and wrote the C program that reproduces the problem. (Simply using the Code::Blocks template with some edits).

The normal behavior is when you see the repeated rederawings clicking on the window should immediately bring up a messagebox with the coordinates. Or pressing key should bring up one with the character pressed. '''This happens on native windows, and in VirtualBox without guest additions'''. 

With guest additions, if you run it for some time and click the window, nothing happens. The drawings keep going and you get response after several seconds. 

It looks like the driver becomes overloaded with stuff, rendering the window unresponsive, till it processed all the events.

It's probably worth noting that the hard disk indicator is red when this hanging happen. Maybe it's writing somehing? I'm not sure whether the VM is thrashing or just because the whole GUI was frozen.

Adding several milliseconds of Sleep() into the message loop relieves the problem a bit. But it makes the game very laggy. 

Hopefully this helps reproducing the problem.

Also a note: at least one OpenGL game the OpenArena works fine on VirtualBox too.


{{{
#if defined(UNICODE) && !defined(_UNICODE)
    #define _UNICODE
#elif defined(_UNICODE) && !defined(UNICODE)
    #define UNICODE
#endif

#include <tchar.h>
#include <stdio.h>
#include <windows.h>

/*  Declare Windows procedure  */
LRESULT CALLBACK WindowProcedure (HWND, UINT, WPARAM, LPARAM);

/*  Make the class name into a global variable  */
TCHAR szClassName[ ] = _T(""CodeBlocksWindowsApp"");

int WINAPI WinMain (HINSTANCE hThisInstance,
                     HINSTANCE hPrevInstance,
                     LPSTR lpszArgument,
                     int nCmdShow)
{
    HWND hwnd;               /* This is the handle for our window */
    MSG messages;            /* Here messages to the application are saved */
    WNDCLASSEX wincl;        /* Data structure for the windowclass */

    /* The Window structure */
    wincl.hInstance = hThisInstance;
    wincl.lpszClassName = szClassName;
    wincl.lpfnWndProc = WindowProcedure;      /* This function is called by windows */
    wincl.style = CS_DBLCLKS;                 /* Catch double-clicks */
    wincl.cbSize = sizeof (WNDCLASSEX);

    /* Use default icon and mouse-pointer */
    wincl.hIcon = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hIconSm = LoadIcon (NULL, IDI_APPLICATION);
    wincl.hCursor = LoadCursor (NULL, IDC_ARROW);
    wincl.lpszMenuName = NULL;                 /* No menu */
    wincl.cbClsExtra = 0;                      /* No extra bytes after the window class */
    wincl.cbWndExtra = 0;                      /* structure or the window instance */
    /* Use Windows's default colour as the background of the window */
    wincl.hbrBackground = (HBRUSH) COLOR_BACKGROUND;

    /* Register the window class, and if it fails quit the program */
    if (!RegisterClassEx (&wincl))
        return 0;

    /* The class is registered, let's create the program*/
    hwnd = CreateWindowEx (
           0,                   /* Extended possibilites for variation */
           szClassName,         /* Classname */
           _T(""Code::Blocks Template Windows App""),       /* Title Text */
           WS_OVERLAPPEDWINDOW, /* default window */
           CW_USEDEFAULT,       /* Windows decides the position */
           CW_USEDEFAULT,       /* where the window ends up on the screen */
           544,                 /* The programs width */
           375,                 /* and height in pixels */
           HWND_DESKTOP,        /* The window is a child-window to desktop */
           NULL,                /* No menu */
           hThisInstance,       /* Program Instance handler */
           NULL                 /* No Window Creation data */
           );

    /* Make the window visible on the screen */
    ShowWindow (hwnd, nCmdShow);

    /* Run the message loop.*/
    for (;;)
    {
        /* Chew window messages. */
        while (PeekMessage(&messages, NULL, 0, 0, PM_REMOVE))
        {
            TranslateMessage(&messages);
            DispatchMessage(&messages);
        }
        /* Step the game world. (omitted)*/

        /* Schedule redraw in next loop. */
        InvalidateRect(hwnd, NULL, TRUE);
    }

    /* The program return-value is 0 - The value that PostQuitMessage() gave */
    return messages.wParam;
}


/*  This function is called by the Windows function DispatchMessage()  */

LRESULT CALLBACK WindowProcedure (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    PAINTSTRUCT ps;

    switch (message)                  /* handle the messages */
    {
        case WM_PAINT:
            BeginPaint(hwnd, &ps);
                /* Simulate expensive painting operation. */
                for (int i = 0; i < 1000; i++)
                {
                    MoveToEx(ps.hdc, rand() % 300, rand() % 300, NULL);
                    LineTo(ps.hdc, rand() % 300, rand() % 300);
                }
            EndPaint(hwnd, &ps);
        break;
        case WM_DESTROY:
            PostQuitMessage (0);       /* send a WM_QUIT to the message queue */
            break;
        case WM_LBUTTONDOWN:
            {
                WORD x = LOWORD(lParam);
                WORD y = HIWORD(lParam);
                TCHAR str[200];
                _sntprintf(str, 200, ""%d: %d"", x, y);
                MessageBox(hwnd, str, """", MB_OK);
            }
            break;
        case WM_CHAR:
            {
                TCHAR str[50];
                _sntprintf(str, 50, ""%c\n"", (char)wParam);
                MessageBox(hwnd, str, """", MB_OK);
            }
            break;
        default:                      /* for messages that we don't deal with */
            return DefWindowProc (hwnd, message, wParam, lParam);
    }

    return 0;
}
}}}",Calmarius
13336,MacBook Pro Retina 2014 crashes when connected to Thunderbolt display,Mac OS X,other,VirtualBox 4.3.14,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
14715,VM renaming,other,other,VirtualBox 4.3.28,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
14726,Remove option for Quick Launch shortcut from installer,Windows,other,VirtualBox 5.0.6,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
11589,Don't create a desktop shortcut by default,Windows,all,VirtualBox 4.2.8,2015-10-21T13:03:30Z,2015-10-21T13:03:30Z,"Please note that Microsoft specifically mentions this point in the Windows Customer Experience Guidelines for developers:

QUOTE BEGIN
If you do only one thing...
Don't abuse the desktop—keep users in control. If your target users are likely to use your program frequently, provide an option during setup to put a shortcut on the desktop, unselected by default.
QUOTE END

http://msdn.microsoft.com/en-us/library/windows/desktop/aa511450.aspx

While you're at it, remove the quick launch shortcut default as well.",gencha
11881,Linux Mint 15 Cinnamon with 3D accelerator crashes ==> Fixed in SVN,Mac OS X,other,VirtualBox 4.2.12,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
14740,"Drag&Drop only works with single files, not with folders",Mac OS X,Windows,VirtualBox 5.0.6,2015-10-24T13:01:10Z,2015-10-24T13:01:10Z,"When I drop a folder (Host = iMac, 10.11) into my Windows 7 guest, the system seems to copy all files that are in it, but when I open the folder it contains only a few files. There is a file "".DS_Store"", which has the size of the original folder.
A single d&d file operation works...
Problem occurs on 5.0.8 too.",SuperAndi
14719,OpenGL Warnings,Windows,Linux,VirtualBox 5.0.6,2015-10-26T09:15:47Z,2015-10-26T09:15:47Z,"Hi,
I think this is a recurring problem with the OpenGL, but none of the previous tickets have a concrete answer.
I have installed VirtualBox 5.0.6 with VirtualBoxAdditions, and when I use two molecular visualization programs that require 3D acceleration I get an OpenGL Error.

VMD
{{{
libGL error: pci id for fd 5: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

Pymol
{{{
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

",cb99
10563,guest addition functions degrade with guest runtime,Windows,Linux,VirtualBox 4.1.8,2015-10-26T14:22:30Z,2015-10-26T14:22:30Z,"Hi!

Sorry, but this is going to be a bit vague and probably hard to reproduce, but has happened to me various times, so I guess it is a bug.

I'm running VirtualBox 4.1.8 on Win7 (64 bit). I know this isn't he current version, but I cannot update the setup now and the release notes of newer versions don't indicate a fix to my problem.

Guest OS is Ubuntu 11.4, but I had the same problems with previous versions of Ubuntu too. There's one shared folder (""Temp"") in the VM mounted via fstab:

{{{
Temp		/media/Temp	vboxsf	rw,uid=1000,gid=1000	0	0
}}}


Right after starting the VM almost everything works (bidirectional clipboard, access to files in the shared folder). But even then only root may write to the shared folder, normal users get

{{{
cp: cannot create regular file `/media/Temp/foo': Permission denied
}}}

To keep my working state I take a snapshot from time to time and reset the VM to the last snapshot instead of a shutdown. So the VM runtime is can get quite long (several weeks or month).

After some time clipboard sharing stops to work completely - guest and host use seperate clipboards.

Later the shared folder also degrades and I cannot write files inside the host anymore, even as root I get an error stating that a file of the same name already exists although it doesn't.

A restart of the VM fixes all the strange effects .. for a while. It seems the restart also fixes at least the shared folder issues of a loaded snapshot too!?
",PinkyBrain
14750,Windows 7 Guest crashes with 3D acceleration turned on,Windows,Windows,VirtualBox 5.0.8,2015-10-26T14:36:34Z,2015-10-26T14:36:34Z,"Since VirtualBox 5.0 all my Windows 7 guests crash if 3D acceleration is turned on. The guest machine boots up, but when I try to login, the ""VirtualBox.exe"" causes an access violation.
I'm running VirtualBox on a Windows 8.1 host.",Feuerfloh
14751,USB flash driver not working on Windows 7,Windows,Windows,VirtualBox 5.0.8,2015-10-26T18:33:05Z,2015-10-26T18:33:05Z,"USB flash driver attach to Windows 7 guest does not work, but working in Windows XP guest.",Steely Wing
14754,OS/2 virtual machines crashes when pressing Ctrl-Alt-NumLock or Ctrl-Alt-F10 and restarting,all,other,VirtualBox 5.0.8,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
14737,Error When starting Windows 1.01 (VINF_EM_TRIPLE_FAULT),Windows,Windows,VirtualBox 5.0.8,2015-10-28T14:29:34Z,2015-10-28T14:29:34Z,"When i try to start the VM it goes to the boot screen and MS-DOS EXCUTIVE and then crashes(Works fine on VBOX4)
",po
14761,Clipboard behavior: Pasting clipboard from paused VM causes destination host app freeze,Windows,all,VirtualBox 5.0.8,2015-10-28T20:17:58Z,2015-10-28T20:17:58Z,"1. Clipboard Direction: Guest to Host
2. Copy any text from guest OS
3. Pause the guest
4. Paste into any application running on host, or another guest (e.g. notepad)

Now, the application of destination freezes until the source of VM is resumed.


This behavior might not incorrect. but I think this scenario should be handled in some way, instead of freezing target app.",ddixuike
14327,virtualbox: VBox crashes when run with a screen reader,Linux,all,VirtualBox 4.3.18,2015-10-29T20:14:44Z,2015-10-29T20:14:44Z,"* What led up to the situation?

I use Debian 8.0, Orca, MATE, qt-at-spi.

 * What exactly did you do (or not do) that was effective (or >>> ineffective)?

1. Run /usr/lib/virtualbox/VirtualBox
2. Go to Machines menu (alt-m)
3. With down arrow key, choose ""Configuration"" (or Settings)
4. Browse 1-2 tabs with down arrow keys
5. Press Escape >>>


* What was the outcome of this action?

I get a segfault

 >>> * What outcome did you expect instead?

Should back to the main Vbox window.


I reproduce from 4.3.18 to 5.0.",texou
14766,VirtualBox breaks USB Drives Permanently Connected,other,other,VirtualBox 5.0.6,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
14767,VirtualBox 5.0.8 causes Wireless Networks to Disappear,Windows,other,VirtualBox 5.0.8,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
14524,VisualStudio 2013 Professional on Windows 10,Windows,Windows,VirtualBox 5.0.2,2015-10-31T02:15:37Z,2015-10-31T02:15:37Z,"I have Windows 10 installed and Visual Studio 2013 Professional. 
Also the host has Windows 10 installed. 
When my computer goes to sleep and starts-up again the screen size 
of the virtual environment is decreased to 800x600.
Before that screen size it was 1600x860. 
To fix this I can only reboot the virtual environment.

When I used Windows 8.1 and VirtualBox 4.2 this problem did not occured.  ",UserVirtualBox
14769,Merging snapshots takes ages,Mac OS X,all,VirtualBox 5.0.8,2015-11-02T22:30:28Z,2015-11-02T22:30:28Z,"I took three snapshots of a VM (with a few seconds between them), shutd own the vm and I'm trying to merge the first one for three hours now.

Progress bar is stuck at ""36 seconds"" left, I dont see any activity (no changing timestamps, no changing file sizes, nothing).

I guess something's pretty wrong here :)

Can you please tell me on how to investigate this issue further?",Eduard Warkentin
12629,Resolution Changes to 640x480 after remote desktop,Linux,Windows,VirtualBox 4.3.6,2015-11-03T10:30:29Z,2015-11-03T10:30:29Z,"I have a Windows 7 guest running on an Ubuntu host.  I can remote desktop to the Windows7 guest without issue.  After closing remote desktop, virtual box resolution is now set to 640x480.  The only way to resolve is to shutdown and restart virtual box guest.

Steps to reproduce
 * Start Windows 7 Guest
 * Login to Guest
 * Move to new workstation and remote desktop to guest
 * logout of remote desktop
 * attempt to login to the console of Windows 7 guest
Using Virtual Box 4.3.6 with Guest Addons.  This issue hass been present on several past versions as well.",shawnl
7874,Guest keyboard starts sending multiple characters for a single keypress after Windows host hibernation,other,other,VirtualBox 3.2.12,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
14780,"Windows host, multiple monitors, 1 virtual screen, fullscreen not working correctly",Windows,all,VirtualBox 5.0.8,2015-11-03T15:29:01Z,2015-11-03T15:29:01Z,"My setup is roughly this:
- Windows 7 as host.
- 3 real monitors: 1680x1050, 1920x1200 (main), 1280x1024, in that order from left to right.
- VirtualBox version 5.0.8, same effect with 4.3.30 and 5.0.6.

I have several clients installed, Linux Mint, Ubuntu, Windows 7, Windows 8, Windows 10, and I have this problem under all of them. The clients are all configured to have one display. As long as the client is windowed (both floating and maximized) everything works fine. 

When i switch to fullscreen (Host-F), the client gets the wrong display resolution. What i would expect to see is it beeing maximized on my main monitor (the same where the client window is at that time) and have its resolution (1920x1200) (*1). But what happens is that the resolution is set to 4880x1200 in Windows (1680+1920+1280) and 784x1200 in Linux (seems to be 4880 mod 4096) (*2). The vertical pixel count seems to be ok with 1200 (it takes either the maximum of the pixels of the current displays, or it's the height of the main display). To be more exact, the clients left margin is where my left margin is on the main screen, the screen extends to the right, some of it beeing on the right monitor, some of it invisible, but it looks like it exists. I can't move the mouse there, but that might be because the host blocks mouse movement. When i maximize progams inside the client, they seem to behave as if there is just one screen with the resolution of 4880x1200 (*3)

One other issue (no problem for me, but it might be for others), is that when the window of the client is on another of my monitors (either in a window or maximized), the fullscreen always goes so the exact same place, that is, it starts on my main monitor and extends to the right from there. I would expect that i could run a client in fullscreen on one of my side monitors somehow, like if the window is on that screen at the time i press Host-F. There might be another way to do this, but i haven't looked into this much, since it's pointless without fixing the first problem.

There might be some configuration option i overlooked, but i doubt it. My guess is, the virtual box host retrieves the wrong pixel count for the display to send to the client when going fullscreen. It should only take the pixels of the one monitor where it is going fullscreen, but instead takes the total pixels of the display area.

To clear up a few things:
- I have installed client additions on all clients, version matching the host.
- I tested it with only one monitor connected, everything works fine and as expected in this case.
- I have not tested other hosts for this effect. I can only guess that the Windows version on the host (7, 8.1 or 10) does not affect this problem, but it might be that a Linux host does not have this.
- I googled about this issue, and i checked the already existing bug reports, i didn't find anything describing this exact problem.
- ""Host-F"" is the keyboard shortcut for fullscreen, in my case right-ctrl-F. I use this terminology since it's called like that in the documentation as well. The described effect is the same when i use the menu entry for fullscreen. I have not tried remapping the host key, but i can't imagine this changing anything about the issue.
- I have not tried to swap the order of monitors around (especially having a monitor with less height as main monitor), but i had a similar effect with only 2 monitors. I doubt trying different monitor configurations will give any more insight to this problem, and if so, it has to be done by a developer/tester who is more familiar with virtualbox in that area.

Notes:
- (*1) I check what the client ""sees"" as its resolution with something like rightclick and ""screen resolution"" in Windows, and xdpyinfo in Linux
- (*2) I tested this in Linux before, when i had only 2 monitors connected (1680+1920) and then the resolution in Linux was 3600.
- (*3) It's hard to explain why it looks like this, it would be much easier for someone else to just try it. For example, when i maximize firefox, the middle of the windows is about 2440 pixels (half of 4880) away from the left margin (of my main monitor), which appears towards the right on my left monitor. It implies the total screen area goes beyond the right edge of that monitor.",waldemar
14398,webcam on Lenovo T550 with CentOS 7.1 guest,Windows,Linux,VirtualBox 5.0.0,2015-11-04T15:32:51Z,2015-11-04T15:32:51Z,"Hi.

I'm running VirtualBox 5.0.0 under Win7 on a Lenovo T550 laptop. 
My guest O/S is CentOS 7.1.
On the Win7 system, the integrated laptop webcam works perfectly.
If I export the webcam to the Linux guest O/S (ie. in the ""Devices"" menu, under Webcams, ""Integrated Camera"" is selected.), then the guest O/S sees the webcam as well (uvcvideo, 04ca:703c).
In the guest O/S, if I start ""cheese"" (a tool to take pictures and video from the webcam), I should see a live preview of the webcam input.  The light on the camera does go on and stays on, but rather than displaying the live preview, I get the first frame that cheese saw when it was started.  That frame doesn't change.  I can click ""take picture"" over and over but it will capture the identical frame.
If I change the video resolution in cheese, then the frame changes one more time.

I tried on an older VirtualBox version 4.3.18, and the problem is identical.
I tried with CentOS 6, under both VirtualBox versions 4.3 and 5.0 (with proper guest extensions), and had the same problem.
I tried with a Lenovo T540p laptop (previous generation of this laptop), and the live preview in cheese worked on both 4.3 and 5.0.

It's important to note that the problem is not explicit to just ""cheese"".  For example, if I visit the following URL in Firefox:

http://mdn-samples.mozilla.org/s/webrtc-capturestill/

This is a WebRTC demo.  In the left box, I should see a live preview of my webcam.  I get the same problem (1 frame).  The same demo works properly on the underlying Linux box, and from the T540p laptop.

I installed a CentOS 7.1 system from scratch with no vbox, and the camera works fine with cheese (and demo above).
I installed VirtualBox 5 on this CentOS 7.1 system, and then installed the same VM that was having the cheese problem, and the video passes through perfectly as well!
I would guess this means that the issue is in the Windows Extension pack.

I'm really really anxious to resolve this issue soon because I really need it for later this month.  If there's any help that I can provide, please let me know.

Jason.",kangaroo
14786,3D acceleration issues persisting on Intel HD video Card,other,other,VirtualBox 5.0.8,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
14791,bridged network error on windows 10,Windows,Windows,VirtualBox 5.0.8,2015-11-05T08:22:08Z,2015-11-05T08:22:08Z,"I installed VirtualBox 5.08 on windows 10 pro which run in a windows domain. Current user had admin rights.
A host-only adapter could be installed.
When trying to use bridged or host-only networking, the VM(windows 2008 r2 server) refused to start. NAT was ok.
After many tries I activated the local Administrator, logged in locally and the VM started fine with bridged networking.
From now I could start the VM also as domain user.
Maybe this description helps fixing this issue. 
",miro25
14795,Linux (Centos-6 x64) guest regularly crashes,other,Linux,VirtualBox 5.0.6,2015-11-06T09:21:47Z,2015-11-06T09:21:47Z,"Centos-6 x64 guest regularly crashes after several days of uptime. No any problems with adjacent windows VM (Windows Server 2003 x86).

VirtualBox: 5.0.6r103037 (same problem with many previous releases).
Host: Windows Server 2008 x64, with latest updates, 24 GB RAM.
Guest: Centos-6 x64, with latest updates, 2 GB RAM, no guest additions.

Kernel errors examples:

kernel BUG at mm/vmscan.c:1083! [[BR]]

invalid opcode: 0000 [#1] SMP[[BR]]

BUG: soft lockup - CPU#0 stuck for 67s! [updater:31994][[BR]]
",Victor Abramoff
5587,"USB device is reported as ""unknown device"" in Windows Guest on Windows Host",Windows,Windows,VirtualBox 3.0.12,2015-11-06T11:06:32Z,2015-11-06T11:06:32Z,"The problem appears related to the slash contained in the device serial number. My guess is that the conversion into a # brokens the guest address. 

Using ""VBoxManage.exe list usbhost"":
{{{
UUID:               d398cf2d-92ee-44bc-aa8e-6ccef37494eb[[BR]]
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       '''GNU/GPL2'''
Address:            {eb781aaf-9c70-4523-a5df-642a87eca567}\0000
Current State:      Busy
}}}
is reported at the guest as:
{{{
UUID:               fd66cabb-4b08-4a90-a877-468e438c50b4
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       GNU/GPL2
Address:            \?\usb#vid_80ee&pid_cafe'''#gnu#gpl2#'''{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State:      Captured
}}}
The guest os see the device as ""unknown device"" with PID and VID to 0. ",Egon
14790,Network communication problem in newer versions of VirtualBox. Possible regression.,other,other,VirtualBox 5.0.8,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
14701,Virtualbox 5.0.6 Slow Loading & Desktop Flickers,other,all,VirtualBox 5.0.6,2015-11-09T03:40:06Z,2015-11-09T03:40:06Z,"My System Specs;

Slackware 14.1 x86_64
Openbox 3.6.1
Nvidia 352.41
xorg-server-1.14.3
compton

I noticed that when starting Virtualbox it loads slowly, taking around 5-10 seconds before it appears on the desktop. Once it loads the entire desktop flickers.

I'm running the compton composite manager and the last safe version I could use without the slow loading and flicker was 5.0.2

Has something changed in virtualbox that is creating a problem when running a composite manager like compton?",VBoxGrl
14752,The GUI and the command line vboxmanage report different status of VM,other,other,VirtualBox 5.0.8,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
14705,Windows XP SP3: Internet Explorer 8 embeding Windows Media Player 11 crashes when navigating away of webpage or on exit,Windows,Windows,VirtualBox 5.0.6,2015-11-10T13:14:03Z,2015-11-10T13:14:03Z,"I am using a TV Online application that makes use Internet Explorer engine to fetch content and Windows Media Player to render the decoded Sopcast streams. The problem is that I can't switch Sopcast channels. The whole application crashes as soon as I browse away from currently playing SopCast stream and also if I close the application while a SopCast stream is playing. This application requires 3D acceleration for SopCast streams to work otherwise you'd experience black screen with audio only, but no crash. 

VMWare is unaffected but I dislike it due to poor performance. 

Applications involved:
-Cool TV Online application: http://www.cool-tv.net/help-tv.html
-Internet Explorer 8
-Windows Media Player 11

Optional software (doesn't affect this issue, removes ads from Cool TV Online application):
-Java Runtime
-nxfilter: http://www.nxfilter.org   ",pal1000
14803,E_FAIL (0x80004005) Critical Error on Windows 10 (Build 1240),Windows,Linux,VirtualBox 5.0.10,2015-11-11T10:36:24Z,2015-11-11T10:36:24Z,"I can't run VM session with Comodo Internet Security installed on my PC. (CIS 8.2.0.4703). 


{{{
The virtual machine 'name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\name\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

}}}
",netak
14815,USB redirection software and VirtualBox,Windows,all,VirtualBox 5.0.8,2015-11-13T07:56:59Z,2015-11-13T07:56:59Z,"Description of the problem is on the forum:

https://forums.virtualbox.org/viewtopic.php?f=6&t=74487",bartekbb1976
14836,Caps-lock cannot be intercepted,Windows,Windows,VirtualBox 5.0.10,2015-11-16T16:35:18Z,2015-11-16T16:35:18Z,"I use vim and various vim modes a lot. For this reason, one of the first things I usually do on my host machine is rewire caps-lock to the escape key using AutoHotKey on my host machine.

This worked just fine until the recent update. Every time I would press caps-lock it would be interpreted as an escape everywhere. 

After upgrading to 5.0.10 however, *inside the VM* it interprets caps-lock as both hitting escape *and* hitting caps-lock. This means, that every time I hit it, my vim flips into a bizarre mode where it does unexpected things with every key stroke. It would be one thing if it wasn't interpreted as escape at all but its interpreted as *both*.

So in order to get the intended behavior, I have to hit caps-lock *an even number of times*. However if, I only hit it an odd number of times, things start jumping around all over (because vim in caps lock mode is no fun).

Guest/Host: both on windows 8.1",gmauer
14838,Search bar on VirtualBox website too small.,other,other,,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
10764,VirtualBox 4.1.18r78361 prevents Windows 7 host from sleeping/entering standby,Windows,Linux,VirtualBox 4.1.18,2015-11-17T06:22:45Z,2015-11-17T06:22:45Z,"While VirtualBox is running, my Windows 7 host OS will not enter standby/sleep after the time of inactivity specified in my Windows power scheme has elapsed.  When I close VirtualBox, Windows sleeps after the time specified in the power scheme.  This problem started after I upgraded to 4.1.18r78361.  This is very inconvenient because I like to keep my guest OS running, so I have to remember to put my host computer into standby whenever I leave the computer or it will needlessly stay on.",bgx90
14840,About dialog needs to be revamped.,Mac OS X,other,VirtualBox 5.0.10,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
14824,Command-W does not close VirtualBox.,Mac OS X,other,VirtualBox 5.0.10,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
14805,Certificate error,Mac OS X,other,VirtualBox 5.0.10,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
14185,ICH AC97 Guest cannot record its own audio,Windows,Windows,VirtualBox 4.3.28,2015-11-19T01:29:53Z,2015-11-19T01:29:53Z,"ICH AC97, select stereo mix and the guest never receives it's own audio for recording.

Windows 2000 pro guest, Windows 8.1 pro x64 host.",Paul17041993
14828,Windows XP resize problem after installing updates and enabling 3D acceleration,Windows,Windows,VirtualBox 5.0.10,2015-11-19T14:36:17Z,2015-11-19T14:36:17Z,"There's currently a problem with XP Guest Additions, more specifically with the auto resize function.[[BR]]
If you enable 3D acceleration (or both 2D and 3D), after installing a certain update (I don't know which) the function gets glitched and every time you log in, after few seconds, all the screen goes black and you need to resize the VM window in a smaller size to make the image appear again (or go to fullscreen and exit).[[BR]]
Also, after you do so, if you resize the window in a bigger size, the ""new"" part of the screen appears black. Fullscreen is also affected.[[BR]]
Both XP Pro, XP Pro x64 and even Ice XP (v6) are affected.[[BR]]
In the log I start up the Ice XP VM with 3D acceleration only, wait for the glitch, resize the window and shutdown.",Zacchi4k
14825,Can not delete iscsi harddisk,other,other,VirtualBox 5.0.10,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
14630,Duplicate host-only Interface name on Windows 10,Windows,all,VirtualBox 5.0.4,2015-11-20T19:46:16Z,2015-11-20T19:46:16Z,"Hi guys, 

There's an anoying bug on '''Windows 10'''.

When creating host-only interfaces, sometimes, a popup appears saying:
 Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

This blocks the interface creation.

When clicking the ""OK"" button, VBoxManage resume the operation and create an interface with a name like 'VirtualBox Host-Only Ethernet Adapter #X'
Eventualy, VBoxManage command ends, saying:
 Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created
'''Notice that it is not the actual name of the interface.'''

To reproduce the issue, just run {{{VBoxManage.exe hostonlyif create}}} a couple of times.

Tested on Windows 10, with VBox 5.0.4 and latest test build (5.0.5)",srats
14852,Grouped command output lost when redirecting to file on shared folder,other,Solaris,VirtualBox 5.0.10,2015-11-20T22:25:42Z,2015-11-20T22:25:42Z,"I am not entirely sure how to describe this issue, but see the comments in the attached test file on how to reproduce.  What appears to happen is that I have a group of commands in a shell script that produce output that is redirected to a file, e.g.

{{{
{
  command1
  command2
} > some_file.txt
}}} 

regardless of whether the commands are shell built-ins or external, only the output of the last command ends up in the redirect file.  This only happens when the redirect file is on a shared-folder mount within the guest.  It does not happen in other directories within the guest.  It also does not happen if the commands are not grouped, i.e. they do not share access to the output file.

In all cases, the test script is run from within the guest, the difference being the current working directory.  I have observed this behavior on both Oracle Solaris 11.3 and OmniOS !r151006 guests. OmniOS is an illumos distribution, similar to Solaris.  In both cases, the Solaris Guest Additions are installed:

{{{
# modinfo | grep vbox
187 fffffffff8115000  29210 265   1  vboxguest (VirtualBox GstDrv 5.0.10r104061)
200 fffffffff8151000   3b28 266   1  vboxms (VBoxMouseIntegr 5.0.10r104061)
201 fffffffff8155000   88a8  24   1  vboxfs (VirtualBox ShrdFS 5.0.10r104061)
}}}

This was discovered while trying to run an autoconf ""configure"" script, which tried to echo a string, pipe it to sed, echo something else, and redirect all the output to a file.  The output from sed never made it to the file.  The attached test script is a condensed version of this.  The effect is that we cannot run configure in a shared folder.

I have verified with truss(1M) that in both cases, identical write(2) syscalls are issued with the same arguments, and succeed in all cases.  I also cannot reproduce this on a Linux guest.  I therefore suspect that the issue lies in the particular VFS implementation provided by the vboxfs Solaris driver.",Eric Sproul
13749,Host Screen numbers are reversed in full screen mode,Windows,Windows,VirtualBox 4.3.20,2015-11-21T09:06:25Z,2015-11-21T09:06:25Z,"I have two identical monitors. When I run a VM (with a single virtual monitor) in full screen mode, I can use Mini Toolbar, View->Virtual Screen 1 to move the VM from one monitor to the other. However the monitor number is wrong - when I select Host Screen 1 (the left monitor), it puts the VM on monitor 2 (on the right), and vice-versa. I've checked the host machine display properties (including ""Identify"") and verified that host monitor 1 is on the left and 2 is on the right.

It used to work correctly, however I recently swapped the two physical monitors, ie left to right and right to left, and so far as I can tell that's when the problem with virtual box started.

At the time I swapped the monitors, I was doing some fault finding, so the host PC was switched on/off a few times with various combinations of one or both monitors disconnected, primary monitor being one or the other, swapping cables between monitors etc. (Virtual Box was not run at any time during this.) The problem turned out to be a physical/optical defect in one monitor - which was originally my primary monitor (number 1, on the left), so that monitor is now my secondary (number 2, on the right). (Swapping them back is not an option.) After I finished, I went to Windows Control Panel and ensured that monitor 1 (eg as shown by the ""Identify"" button) is on the left and is my main display, and the monitor 2 on the right is the secondary - it had changed during the process of testing. The port on the video card that's used for the left monitor hasn't changed - only the monitors have swapped places.

The host machine appears to correctly identify the monitors, but now Virtual Box puts the full-screen VM on the opposite monitor to what the mini toolbar menu item says.

The problem is not user-specific. I can replicate it with a different user on the same host PC.

Uninstalling/reinstalling VirtualBox does not fix the problem.

I've tried assorted combinations of disconnecting one or other of the monitors, restarting the machine etc, to see if that will fix it, but it doesn't make any difference.

I even reverted to a (Windows Backup and Restore) system image taken before the monitors were swapped, and that didn't fix the problem either.

It's as if VirtualBox's ""host screen 1"" is tied to the original physical monitor 1, rather than the logical monitor 1 (ie as Windows identifies it after swapping them).

Technical details:

Host is Windows 7 Ultimate, SP1, 64-bit. (The problem appears to be independent of the guest OS - I can replicate it with Windows and Ubuntu guests, and no guest OS at all, just the VM BIOS on a newly created VM with no software installed.)

The monitors are both Dell 2209WA.

Video card is AMD Radeon HD 6670.
",m6477
14435,ERROR In SupR3HardenedWinResSpawn,Windows,all,VirtualBox 5.0.0,2015-11-21T22:09:45Z,2015-11-21T22:09:45Z,"OS Win7 x32 Ultimate.
Bitdefender Antivirus Free Edition 1.0.21.1099.
VirtualBox - 5.0.0-101573 (similar errors appeared with version 4.3.14)
When I run the guest appears this window:
""ERROR In SupR3HardenedWinResSpawn""
After removal of the antivirus VBox starts as expected.",digitadropper@…
14854,regression: failed to open session VD: error VERR_NOT_SUPPORTED opening image file,Mac OS X,Linux,VirtualBox 5.0.10,2015-11-22T10:29:34Z,2015-11-22T10:29:34Z,"I have a VM that uses raw disk function for an SSD partition, with the proper permissions to do so on OS X. There is a .vmdk file created to point to this partition. The VM works without error using VirtualBox 5.0.0 but somewhere between 5.0.1 and 5.0.8 this now results in an error. I'm using 5.0.10 for this bug report.

Host: Mac OS X 10.9.5
Guest: Fedora 23 (but the VM fails before I even get to the emulated firmware)",Chris Murphy
13135,File corruption with shared folders using VB 4.3.12,Mac OS X,Windows,VirtualBox 4.3.12,2015-11-24T05:26:13Z,2015-11-24T05:26:13Z,"Virtual Box 4.3.12r93733
Host Mac OS X 10.8.5
Guest Windows Server Data Center 2012 R2 (4.3.12 Guest Additions Installed)
I have a large ZIP file (837MB) in a directory on my host.

To reproduce:
1) Create a shared folder mapped to the directory containing the zip on the host
2) Copy the ZIP to a local guest directory (IMPORTANT)
3) Attempt to unzip the file using windows native tools, Java's jar.exe or 7zip.  
They will each fail with fairly meaningless error message.  
Windows Extract All... says: ""Error 0x80004005: Unspecified error""
Java's jar says: ""java.util.zip.ZipException: invalid stored block lengths""

Note that step #2 is important.  Unziping the file in place from the share seems to work so something is occurring when the file is copied.
I've also confirmed that MD5 hash of the file does indeed change after it is copied from the share.  I used this tool from Microsoft to compute the hash.  http://support.microsoft.com/kb/841290/en-us",kminder
14864,VDI eviroment bugs,Solaris,Windows,VirtualBox 4.3.30,2015-11-25T12:51:45Z,2015-11-25T12:51:45Z,"Hi I hope somebody can help me, We are running 25 sunrays in a class with sunray server and a custom broker. Since we upgraded to 4.2.28 from 4.3.30 we are getting strange bugs frequently. We are connected to the VRDEport(console connected) to the running VM. 1. When a user logs off the screen snaps to the smallest 8bit resolution which leave the user with a small screen with mangled colours a windows reboot solve the issue but would like to know what the cause is. 2. When a user logs out it remains on logging off and needs to be powered off hard and started up to recover.   ",Reniervdw
14597,5.0.4 - Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR,Windows,Linux,VirtualBox 5.0.4,2015-11-25T16:09:23Z,2015-11-25T16:09:23Z,"I've been using VirtualBox for a while 4.3.18 - 4.3.30 where i have a VM with a live snapshot.
after upgrading to 5.0.4 i've got a problem on my 4.3.30 created VM: ""Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR""
reverting back 4.3.30 runs the VM fine but not with 5.0.4

Host: Windows 7 x64
guest: Linux based OS

see also: 
[https://forums.virtualbox.org/viewtopic.php?f=6&t=70070]
",talr
14868,VB crashes when switching from window to fullscreen (Host+F),Mac OS X,Windows,VirtualBox 5.0.10,2015-11-26T10:04:01Z,2015-11-26T10:04:01Z,"Sometimes, when switching from window to fullscreen, virtual machine  window disappear and the virtual machine is marked as crashed.

Latest log entries:

{{{
08:55:06.044842 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received
08:55:06.045154 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillExitFullScreenNotification' notification to corresponding machine-window...
08:55:06.045210 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received.
08:55:06.045223 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to exit, notifying listener...
08:55:06.181553 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillExit: Machine-window #0 will exit native fullscreen
08:55:06.719043 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received
08:55:06.719055 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowDidExitFullScreenNotification' notification to corresponding machine-window...
08:55:06.719058 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received.
08:55:06.719061 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode exited, notifying listener...
08:55:06.720477 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenDidExit: Machine-window #0 exited native fullscreen, changing visual-state to requested...
08:55:08.912327 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011ecc9000 w=1680 h=1050 bpp=32 cbLine=0x1A40 flags=0x1
08:55:08.912356 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1680x1050, Sending to async-handler
08:55:08.917657 GUI: UIMachineViewScale::resendSizeHint: Restoring guest size-hint for screen 0 to 1440x900
08:55:08.917679 VMMDev: SetVideoModeHint: Got a video mode hint (1440x900x32)@(0x0),(1;0) at 0
08:55:08.917967 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
08:55:08.919933 OpenGL: Set 3D content scale factor to (8571, 7876), multiplier 10000 (rc=VINF_SUCCESS)
08:55:08.938438 OpenGL: Set 3D content scale factor to (8571, 7666), multiplier 10000 (rc=VINF_SUCCESS)
08:55:09.253520 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1680x1050
08:55:09.253535 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1680x1050
08:55:09.253546 GUI: UIFrameBufferPrivate::performResize: Size=1680x1050, Directly using source bitmap content
08:55:09.253705 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1680x1050
08:55:09.510201 GUI: UIMediumEnumerator: Machine (or snapshot) event received, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:09.512154 GUI: UIMediumEnumerator:  Old usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.513464 GUI: UIMediumEnumerator:  New usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.513482 GUI: UIMediumEnumerator:  Items currently in usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.513551 GUI: UIMediumEnumerator: Machine (or snapshot) event processed, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:09.519719 Switching Gl mode off
08:55:09.519883 GUI: UIMediumEnumerator: Medium-enumeration finished!
08:55:09.520787 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011ecc9000 w=1680 h=1050 bpp=32 cbLine=0x1A40 flags=0x1
08:55:09.520812 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1680x1050, Sending to async-handler
08:55:09.526380 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011ecc9000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
08:55:09.526411 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
08:55:09.527195 VMMDev: Guest Log: VBoxDisp[0]: VBVA enabled
08:55:09.527224 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
08:55:09.527243 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011ecc9000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
08:55:09.527270 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
08:55:09.533594 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1680x1050
08:55:09.533605 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1680x1050
08:55:09.533614 GUI: UIFrameBufferPrivate::performResize: Size=1680x1050, Directly using source bitmap content
08:55:09.534452 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1680x1050
08:55:09.538860 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
08:55:09.538871 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
08:55:09.539005 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1440x900
08:55:09.752626 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
08:55:09.752638 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
08:55:09.752763 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1440x900
08:55:09.820907 2D is supported!
08:55:09.873237 GUI: UIMediumEnumerator: Machine (or snapshot) event received, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:09.873289 GUI: UIMediumEnumerator:  Old usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.874704 GUI: UIMediumEnumerator:  New usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.874715 GUI: UIMediumEnumerator:  Items currently in usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:09.874757 GUI: UIMediumEnumerator: Machine (or snapshot) event processed, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:09.903769 GUI: UIMediumEnumerator: Medium-enumeration finished!
08:55:10.776490 Switching Gl mode on
08:55:12.613982 Switching Gl mode off
08:55:17.098030 GUI: UIMultiScreenLayout::update: GUI/AutomountGuestScreens is disabled
08:55:17.099800 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000011ecc9000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
08:55:17.099828 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
08:55:17.102540 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
08:55:17.102574 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
08:55:17.107272 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
08:55:17.107286 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1680x1050
08:55:17.107298 VMMDev: SetVideoModeHint: Got a video mode hint (1680x1050x32)@(0x0),(1;0) at 0
08:55:17.107760 GUI: UIMachineLogicFullscreen::revalidateNativeFullScreen: For machine-window #0
08:55:17.107768 GUI: UIMachineLogicFullscreen::revalidateNativeFullScreen: Ask machine-window #0 to enter native fullscreen
08:55:17.107893 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
08:55:17.107899 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1680x1050
08:55:17.134223 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillEnterFullScreenNotification' received
08:55:17.134239 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillEnterFullScreenNotification' notification to corresponding machine-window...
08:55:17.134242 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillEnterFullScreenNotification' received.
08:55:17.134245 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to enter, notifying listener...
08:55:17.204133 GUI: UIMediumEnumerator: Machine (or snapshot) event received, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:17.204180 GUI: UIMediumEnumerator:  Old usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:17.205581 GUI: UIMediumEnumerator:  New usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:17.205593 GUI: UIMediumEnumerator:  Items currently in usage: 06da1835-639e-4eda-8361-d27a59857a64, 84f3f635-65a0-42b1-9236-1f0c06ec3a5e
08:55:17.205677 GUI: UIMediumEnumerator: Machine (or snapshot) event processed, ID = d56e627c-578f-4337-a52a-b7c872b1f43c
08:55:17.205941 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
08:55:17.205950 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
08:55:17.205959 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
}}}

OSX 10.11.1  on a MBP (15"", mid 2014, 2 monitors attached)",Megachip
14870,Unable to Accept EULA On XP,Windows,Windows,VirtualBox 5.0.10,2015-11-27T08:30:18Z,2015-11-27T08:30:18Z,"When I try to press any F keys, I can't. And because you need to press F8 to accept the XP EULA, I can't do that.",VirtualMan2000
14113,Ubuntu guest loses keyboard sporadically,Linux,Linux,VirtualBox 4.3.28,2015-12-01T02:14:40Z,2015-12-01T02:14:40Z,"Host: ubuntu 14.04
Guest: ubuntu 12.04

Sporadically guest loses keyboard, xev doesn't show keyboard events, etc. The only way to fix this issue is to restart guest. Save/reload doesn't help.

I'm using the Microsoft Remote Desktop (Win7) as client. If I close it and reconnect to the guest the keyboard still doesn't work.",DO
14884,Cannot chmod directories within guesLinux guest/host,other,other,VirtualBox 5.0.10,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
14428,win 10 host and VB from 5.0 to latest test build = NO bridge networking,Windows,Windows,VirtualBox 5.0.0,2015-12-02T08:43:13Z,2015-12-02T08:43:13Z,"hi!

win 10 64 bit host , upgrade from win 8.1,
win xp guest

no way to set network -bridge-

hope someone will be able to find a workaround as for the 
issue of the no sound:
https://www.virtualbox.org/ticket/14361#comment:21

cheers",giusi
14778,Multi-monitor setup - screens swapped,Windows,Windows,VirtualBox 5.0.6,2015-12-02T14:13:48Z,2015-12-02T14:13:48Z,"Win7 host, WinXP guest, 2-monitors setup (laptop & external monitor), seamless mode.

After upgrading to VBox 5, it seems that VBox perceives monitor1 as monitor 2 and monitor2 as monitor1. Upon guest startup, 1 window opens at first and XP starts booting. After a while, when switching to graphical environment (during the XP boot process, just before the login screen appears) a 2nd window appears and the XP boot progress is shown in that window (the 2nd instead of the 1st). After that, the guest OS seems to treat the 2nd VBox window as the 1st screen and vice-versa. I enabled the mini-toolbar and set the 1st virtual screen to use host screen 1 but instead it used host screen 2. If VS1 is set to HS2, it works as intended but then if the guest is shut down, the external monitor is plugged-out and the guest is restarted, nothing is shown because in the laptop's monitor, the 2nd VS is supposed to be shown.

The ""Display"" of the guest shows as monitor #1 the laptop monitor and as #2 the external (i can tell from the different resolutions), however the contents of monitor 1 are shown in #2 and vice-versa.

Everything worked normally in VBox4 from which i upgraded the host and guest installations.",Wand
14886,Virtual Machine crash,Mac OS X,Linux,VirtualBox 5.0.10,2015-12-03T11:46:39Z,2015-12-03T11:46:39Z,"After several hours of working on mac os x virtual machine with installed ubuntu 12.04 server crashed.
Crash is stable 2-3 time during working day.",grustem7
14899,Screen resolution defaults to 1024x768 and not to the selected before the reboot,Linux,Windows,VirtualBox 5.0.10,2015-12-04T13:07:37Z,2015-12-04T13:07:37Z,"Dear Support,

A guest Windows 7 system defaults to 1024x768 screen resolution and not to the previously selected before the reboot. It is not clear under what circumstances the resolution is not kept between the reboots. It is not reproduced all the time.",Panos Kavalagios
14859,"updeted vbox and guestadd. to version 5, randomly stop working",Windows,Windows,VirtualBox 5.0.10,2015-12-05T06:25:34Z,2015-12-05T06:25:34Z,"used firefox, randomly guest stop working, total blocking
note, I also work at host at same time and go to guest short times.
",Mjau
14911,Black screen with OpenGL only in full-screen mode,Windows,Linux,VirtualBox 5.0.10,2015-12-08T14:52:38Z,2015-12-08T14:52:38Z,"When I'm not in full-screen mode, I can run an OpenGL application such as glxgears, and it works fine. In full-screen mode, however, the entire screen will go black except for the contents of the window where 3D rendering is occurring. For example, with glxgears I see only the gears, and the rest of the screen is black.

I'm running Debian ""jessie"" as a guest with VirtualBox 5.0.10 on a Windows 7 SP1 host. Both the guest and the host are 64-bit. I've installed the guest additions for 5.0.10 via the CD image supplied with VirtualBox. 3D acceleration is enabled in the VM settings. (Disabling it makes the problem go away, but then 3D rendering is slow due to no acceleration.) I have version 10.3.2-1 of most of the mesa lib packages, 9.0.0-2 for libglu1-mesa. My graphics card is an NVIDIA Quadro FX 3800, and I have the NVIDIA drivers installed on the host. (Previously I had a Quadro FX 570, and the behavior was exactly the same with that card.) Everything else is working fine in this Linux guest.",abc123
14424,Shared folder seems to cache old file content for the guest after editing host files,Windows,Linux,VirtualBox 5.0.0,2015-12-08T17:42:12Z,2015-12-08T17:42:12Z,"I have VirtualBox 5.0.0 running on a Windows 7 SP1 x64 host, with an Ubuntu MATE 15.04 Linux as guest.

To exchange script files in development, I mounted a share manually to a shared folder (""sudo mount -t vboxsf {sharename} {targetname}"", because I did not know where to look for the auto-mounted share), where I copied files to in the hosting Windows, and copied files out of the share into a local directory in the guest Linux.

I found that the script files contained some bugs, which I fixed using Windows tools I have more experience with, which reduced the size of some files (e.g. converting CRLF line breaks to LF only, and deleting some text content).

Then I copied the files with the same name and location in the guest Linux out of the share and into the local directory again, overwriting the old versions of these files. So I thought. But I had to discover that the scripts still contained the buggy parts. And on top, the size was now reduced to the new file size, means, a part of the last script line was truncated now.

The only reliable way to edit the files inside the guest Linux was to empty the files, save with 0 bytes, close, re-open (in gedit or similar fork), then copy the text in a Windows text editor in the host, and paste the text into the Linux text editor via shared clipboard in the guest.",LigH
14912,Microsoft RD Client on iOS - keyboard not working,Linux,Linux,VirtualBox 5.0.10,2015-12-09T01:44:02Z,2015-12-09T01:44:02Z,"I am running 5.0.10 Virtualbox on Intel Atom, with 2GBRAM. Latest Guest Extension Pack. I have a Ubuntu 14.4.3LTS guest, latest kernel, 5.0.10 Guest additions. I have configured the guest to share a desktop via VRDE. The gust runs in console mode. When connecting to the guest with Microsoft's official  RD Client software for IOS (either iPad or iPhone), the only key that appears to work on the keyboard is ENTER. That produces a line as expected. Nothing else seems to work. I noticed on log in ""Numlock Enabled"" shows up. I have seen the same problem with a Virtual OpenWRT instance which does not run any guest extensions so it does not seem isolated to just Ubuntu.",Bruksee
14897,Windows 10 handles VBoxManage.exe incorrectly when importing and listing,other,other,VirtualBox 5.0.10,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
14913,Saved vm: Clone + reinitialize network doesn't really change MAC,other,other,VirtualBox 5.0.10,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
14917,Debian guest is aborted when plugging in or unplugging thunderbolt on mac host,Mac OS X,Linux,VirtualBox 5.0.10,2015-12-10T16:20:29Z,2015-12-10T16:20:29Z,"Guest:
Debian Jessie
3.16.0-4-amd64
monitor count 2
video memory 50
ram 9000 MB
cpu 4

Host:
MacBook Pro (Retina 15-inch, Late 2013)
Processor: 2.3 GHz Intel Core i7
Memory: 16 GB
Graphics NVIDIA GeForce GT 750M 2048 MB

Unfortunately this issue is intermittent, but sometimes when I plug in or unplug the thunderbolt to an external monitor the guest goes right to aborted.

I would like to attach logs to this ticket, but I see how to.



",ranamala
14919,Polycom CX600 gets call from Computeraudio when starting VM with ICH AC97 controller,Windows,all,VirtualBox 5.0.10,2015-12-11T09:07:52Z,2015-12-11T09:07:52Z,"Since VirtualBox-5.0.2-102096 I have a strange behavior with my Polycom CX600 phone connected via USB to the my host system (Windows 7).

As soon as a VM is started and the VM BIOS is loading, the phone shows me silently a call to ""Computeraudio"". Every real call to my phone then only is knocking on like the phone is busy.

As soon I stop the VM, the ""Computeraudio"" call is interrupted and the phone works again like it should.

In VirtualBox-5.0.0-101573 and older versions everything works fine.

Every Version since VirtualBox-5.0.2-102096 have the same behavior, including the actual version VirtualBox-5.0.10-104061.

I tried a little bit around with some settings and found out that this doesn't happen when the audio controller is not set to ""ICH AC97"". Intel HD Audio and SoundBlaster 16 doesn't produce this behavior, but I get no sound out of my Linux guests with these two audio controllers (especially tested with Knoppix LiveDVD 7.6 for repeatable results).

Another check was what happen when I disconnect the phone USB cable from the host.
When the guest was already started and the phone shows already the ""Computeraudio"" call, the call is interrupted as soon as I disconnect the USB cable. After connecting it again, the phone dosn't show the ""Computeraudio"" call again (until reboot the VM).
When I disconnect the cable before starting the VM and plug it in after the VM was started, no ""Computeraudio"" call is shown. The phone works normally.

Because of this behavior starts before the guest OS is loading, I think this is independent of it. Nevertheless I checked out lsusb but there are no USB devices shown, except the input device and the USB root hubs.

I will attach four log files (for Version 5.0.0 and 5.0.2 one with ICH AC97 and one with Intel HD Audio controller). And if it works, also an picture of the phone screen.

",Andy1971
14922,Accessing Kinect Camera,Mac OS X,Linux,VirtualBox 5.0.10,2015-12-11T23:47:48Z,2015-12-11T23:47:48Z,"Hi,
I posted my problem on the forum here:
https://forums.virtualbox.org/viewtopic.php?f=8&t=74789

There was no reply for 20 days so I thought to try and open a bug report, since I'm still unable to access the Kinect Camera using VirtualBox.

Thanks!

/Avner

The Original  Post:
--------------------------------------------------------------------------
Hi!
I am using VirtualBox with Boot2docker on OSX and I'm trying to access Microsoft Kinect for XBOX360 on the guest Linux OS.
I installed the extension pack and was able to share access to the 3 USB devices:


{{{
Microsoft Xbox NUI Motor
Microsoft Xbox NUI Audio
Microsoft Xbox NUI Camera
}}}


I was also able to share them from the docker machine to the docker containers using the '''--device''' flag.
However, while applications such as OpenNI2 are able to find the device, and even control its motor, the camera stream is always completely blank and I see messages such as:


{{{
[Stream 70] Lost 23351 total packets in 0 frames (inf lppf)
}}}


On rare occasions, one frame was suddenly able to pass and I could actually get one frozen image.
I read in several locations and also in this forum that at least regarding webcams, It is advised to use the ""Webcam passthrough mode"" described in the VirtualBox manual.
However the Kinect camera is not recognized on my host as a webcam, and the output of '''VBoxManage list webcams''' is just:


{{{
.1 ""FaceTime HD Camera (Built-in)""
0x1a11000005ac8510
}}}


When running ioreg, the XBOX devices appear as such:

{{{
Xbox NUI Motor@1a122000  <class IOUSBDevice, id 0x1000130c1, registered, matched, active, busy 0 (24 ms), retain 11>
Xbox NUI Audio@1a121000  <class IOUSBDevice, id 0x1000131a0, registered, matched, active, busy 0 (6 ms), retain 9>
Xbox NUI Camera@1a123000  <class IOUSBDevice, id 0x1000132a9, registered, matched, active, busy 0 (19 ms), retain 11>
}}}


Is there any way out of this mess?? Would appreciate any advice.
Thank you!

/Avner",Avnerus
14924,GNU/Linux guest aborts while saving when 3D acceleration is enabled,Windows,Linux,VirtualBox 5.0.10,2015-12-12T18:00:46Z,2015-12-12T18:00:46Z,"Virtualized GNU/Linux box (Ubuntu Gnome 15.10) crashes every time when trying to save machine state, only if 3D acceleration is enabled: the progress bar reaches 97%, then the machine status is set to ""Aborted"".

Disabling 3D acceleration makes the problem disappear, while touching any other parameter (including increasing or decreasing guest RAM or video memory) does not seem to have an impact.

I also tried the latest test build (5.0.11-104602 at the time of writing), without success.

All machine details are in the logs attached.
Guest syslog, Xorg.log, and kern.log are also included.

Thanks!",eisenach
14930,Excel 2016 can't open file in Windows 10,Windows,Windows,VirtualBox 5.0.10,2015-12-14T13:15:05Z,2015-12-14T13:15:05Z,"Hi,

I've an issue when I'm trying to open a file in Excel 2016 from the Explorer under Windows 10 guest. The error says that ""There was a problem sending the command to the program""

Reading different solutions on windows forums I found that if I disable the hardware acceleration graphics in excel, then the file opens normally.

Also it doesn't matter the location of the file. The error happens either if the file is on a local disk(desktop) or shared folder or network mapped folder.

There are some roundabouts where the file opens fine with hardware accelerated graphics enabled:
- If Excel is already open and open a file from the explorer.
- If I open the file form Excel.

The only scenery is opening a file from explorer while the Excel is closed and HW acc graphics is enabled.

setup:
- Guest: Windows 10 pro x64 using hyper-v and graphics acceleration enabled.
- Host: Windows 7 Enterprise x64 @ Intel i5 4300M
- Virtualbox: 5.0.10 r104061 also tested in 5.0.11 r104675.",David Eduardo Cortelezzi
14926,kernel 4.2 incompatible headers structure,Windows,Linux,VirtualBox 5.0.10,2015-12-17T08:04:03Z,2015-12-17T08:04:03Z,"virtualbox guest additions (v 5.0.10) claim that can't find headers for current kernel, but install successfully.

In Ubuntu 15.10 amd64.",MikhailRokhin
14948,"""Auto-resize guest display"" feature unstable",Windows,Windows,VirtualBox 5.0.12,2015-12-20T09:15:09Z,2015-12-20T09:15:09Z,"I am talking about this feature:
https://ma.ttias.be/auto-resize-screen-size-windows-10-guest-vms-virtualbox/

I am running Windows 10 guest under Windows 10 host.

After I start virtual machine:
Guest display is autoresized, but ""Auto-resize guest display"" checkbox inside top menu bar is disabled (greyed).

After I login to my Windows account on guest system:
""Auto-resize guest display"" checkbox is enabled, but it does not do anything. I would expect that when I uncheck this checkbox guest display would toggle to fixed size and when I check it guest display would toggle to flexible size. However, this does not happen. Guest display does not react to checking/unchecking ""Auto-resize guest display"" checkbox.

If I click on ""Resize to ..."":
Guest display toggles to fixed size, however ""Auto-resize guest display"" checkbox remains checked. So, checkbox does not reflect current state of guest display. Next, to return to flexible size I need to click on checkbox twice: the first click will uncheck checkbox and the second click will check checkbox and return display to flexible size.

For me it would be logical if:
""Auto-resize guest display"" option would move to the same menu with ""Resize to ..."". Then I would have: ""640x480 resolution"", ""800x600 resolution"", ..., ""Auto-resize guest display"". Then only one option can be enabled at the same time. Current situation when I can have ""640x480 resolution"" and ""Auto-resize guest display"" enabled at the same time is against the logic. The screen can't have two different sizes at the same time.

But most important issue is:
After some time ""Auto-resize guest display"" features breaks, guest display toggles back to fixed size and does not react to ""Auto-resize guest display"" checkbox any more. I have to reboot to toggle flexible display size on. This happens occasionally. I suspect that this may happen when host system goes to sleep mode or other kind of waiting mode, but I can't say for sure.",i8329
14939,VM VirtualBox 5.01 on Windows 10 has excessive disk activity when running Debian 7.0.0,Windows,Linux,VirtualBox 5.0.10,2015-12-22T02:41:26Z,2015-12-22T02:41:26Z,"Since I have upgraded from 4.2.34 to 5.0.10-104061, the performance
of Debian 7.0.0 (40.0 Gb) has gone down significantly.
Whenever I resume the saved state, there is a lot of disk
activity even when I am doing nothing. The Windows 10 Task Manager
indicates disk activity peaking around 30 Mbytes/sec coming
from the VirtualBox Manager. A lot of disk activity continues while I
am working in a command window in Linux. I have encountered the
same issue with Windows 7 (before I upgraded to Windows 10 recently).

I have tried to regress back to 4.2.34, but I am unable to restart
the saved state of Debian 7. ""Failed to open session for virtual
machine debian 7.0.0. Unsupported version 17 of data unit cpum""

Occasionally when I close the Virtual Machine using save state,
it gets aborted. When I restart the virtual machine, Debian reboots.",seymour
13946,Unable to Use USB devices on Virtual box,Windows,Linux,VirtualBox 4.3.24,2015-12-22T15:33:02Z,2015-12-22T15:33:02Z,"We are using Virtual Box 4.3.24 and inside we are using Ubuntu 14.
and also in my Local machine windows 7 we are using McAfee DLP 9.3.

* we raised a ticket with McAfee regarding this and they are saying it must be a problem with virtual Box.

when we uninstall DLP USB works fine in Virtual box. ",sathi
14964,Shared clipboard does not work every second time,Windows,Windows,VirtualBox 5.0.12,2015-12-22T17:33:25Z,2015-12-22T17:33:25Z,"It starts working after restart. So, I regularly have to start virtual machine and then restart it to get it work. Log attached.",i8329
14969,"""Insert Guest Additions CD image..."" should not have trailing ""...""",other,other,VirtualBox 5.0.12,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
14972,VirtualBox disables ASIO analogue inputs on my MIA MIDI soundcard,Windows,Windows,VirtualBox 5.0.10,2015-12-23T13:52:47Z,2015-12-23T13:52:47Z,"I am running Version 5.0.10 r104061 on an ASUS Z87-A motherboard with an Intel i7-4770 CPU and 16GB memory. I also have an Echo Digital Audio Mia Midi PCIe sound card which uses ASIO drivers. I use this as my main soundcard and have disabled the onboard soundcard on my Motherboard.

When I run any guest with sound enabled: Windows Direct Sound, Intel HD Audio, the ASIO analogue virtual inputs are disabled in all my audio programs (DAWs) and replaced with the digital S/PDIF inputs.
If I disable audio in the guest the ASIO ports work correctly.
If I select Windows Direct Sound as input, I can record on the host and still get sound from the guest. However, as I record music, I want the ASIO drivers to be available on the host. 

VB should recognise all the audio hardware on the host and allow me to direct the guest to use the on-board audio hardware on the motherboard 
",MarkT
14974,Windows 10 /Solaris:Linux or Windows Guest,Windows,all,VirtualBox 5.0.12,2015-12-24T16:21:13Z,2015-12-24T16:21:13Z,"The guest, whatever version windows, linux or solaris will work for a few weeks then fail, I have to restart the PC change some ethernet adapter property usually I toggle ipv6 enabled and then virtualbox guest starts ok. This cycle repeats

The log that shows the issue seems to reference two c++ files. 

I had put this one the forum, but I placed in the wrong sub-forum, Windows 10 Guest. The moderator suggested this was incorrect and moved to a Solaris guest.
",matdave
11978,Dup ping and not network connectivity while bridged on WIFI,Linux,all,VirtualBox 4.2.16,2015-12-29T19:30:45Z,2015-12-29T19:30:45Z,"Good day all,
I am running Fedora 19 x64.  Using the same laptop for couple of years now and longer for Virtualbox.  During the last upgrade I started having connectivity issues on some machines.  Further investigation found that only machines that were bridged on the WIFI was affected.  Let me know if you want any configuration files or anything at all.
Thanks, Devon
{{{
[devon@fisc-dcj-rhw ~]$ ping google.com
PING google.com (74.125.229.227) 56(84) bytes of data.
64 bytes from 74.125.229.227: icmp_seq=1 ttl=56 time=15.5 ms
64 bytes from 74.125.229.227: icmp_seq=1 ttl=55 time=15.6 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=2 ttl=56 time=18.6 ms
64 bytes from 74.125.229.227: icmp_seq=2 ttl=55 time=18.7 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=3 ttl=56 time=17.7 ms
64 bytes from 74.125.229.227: icmp_seq=3 ttl=55 time=17.8 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=4 ttl=56 time=83.2 ms
64 bytes from 74.125.229.227: icmp_seq=4 ttl=55 time=83.3 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=5 ttl=56 time=103 ms
64 bytes from 74.125.229.227: icmp_seq=5 ttl=55 time=103 ms (DUP!)
}}}",Devon
14992,Crash Windows 7 / RAW FILE CONVERTER EX powered by SILKYPIX,Linux,Windows,VirtualBox 5.0.12,2015-12-30T16:13:06Z,2015-12-30T16:13:06Z,"When I try to start the program RAW FILE CONVERTER EX powered by SILKYPIX (which is Fuji-supplied raw photo conversion software) Virtualbox crashes out on me. This used to work a couple of months/versions ago (maybe a regression in 5.x?)

I tried disabling 3D both in the guest additions install and the Virtualbox config and I got a blue-screen (unfortunately the VBox.png is corrupt and did not capture the bluescreen)",Andrew Basterfield
14994,Can't enable/disable a Virtual Screen when in full-screen mode,Windows,Windows,VirtualBox 5.0.12,2015-12-30T21:39:43Z,2015-12-30T21:39:43Z,"I have a VM with monitor count set to two in Settings > Display. I have two physical monitors.

When I'm not in full-screen mode in the View > Virtual Screen 2 menu I see the Enable command in that menu and can check or uncheck it to enable or disable the second VM screen as desired.

But in full-screen mode when I go to the View > Virtual Screen 2 menu the Enable command is not shown.

Not sure if this is a defect or enhancement.  

Some background: I disabled the second screen about a week ago as this is a laptop and I was traveling with it and today I was back in the office and wanted to enable it again and couldn't figure it out.  I was toggling between ""Use Host Screen 1"" and ""Use Host Screen 2"" trying to get the second screen to show. This is something I don't do often. ",Wes Manning
14999,"Bridge NIC, ssh from VM will freeze for some cmds",other,other,VirtualBox 5.0.12,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
14949,Drag and drop inside guest doesn't work after installing Guest Additions,Windows,Windows,VirtualBox 5.0.12,2016-01-04T10:52:02Z,2016-01-04T10:52:02Z,"I have been testing Virtualbox for some months and it works really great, very good job guys!
But I have found a strange issue, and can't find a solution here.
Last days I am testing VBox with windows 7 (64bit) embedded guests.
In my latest builds, everything works fine until I install Guest Additions, then drag and drop (in windows explorer and desktop) stops working completely in guest. If I uninstall Guest Additions then it starts working again. 
Also I get some errors trying to run some exe files (mainly installers) from host shares. But if I copy the directory to my desktop or some network share, then the same installers work just fine.
It happens with v. 5.0.10 and also with latest 5.0.12 (with their respective Guest Additions versions), I'll try with older/stabler versions.
I haven't had these problems with Windows 7/8 guests, maybe something related with Windows Embedded. If I install that same image to a real computer, drag and drop works just fine.
Any ideas of what might be happening?
My host has Windows 8.1.
Please see log attached.
You can see the thread I opened in forum here:
https://forums.virtualbox.org/viewtopic.php?f=2&t=75253&p=349185#p349185

Thanks in advance!",ramoncio
14966,Dragging folder with several files from host to guest works partially,Windows,Windows,VirtualBox 5.0.12,2016-01-04T11:41:16Z,2016-01-04T11:41:16Z,"When I drag folder containing several files from host to guest, VirtualBox copies the folder and one file, while all other files except the first one are not copied.",i8329
7260,VBoxTray.exe high CPU usage in RDP session,Windows,Windows,VirtualBox 3.2.6,2016-01-04T12:49:43Z,2016-01-04T12:49:43Z,"Hi

version: 3.2.6
host: Windows Vista 32-bit
guest: Windows 2003 Server 32-bit (guest additions installed)

When connecting guest OS through Windows RDP (I mean not VirtualBox RDP) VBoxTray.exe loads CPU up to 100%. After killing the VBoxTray.exe process it's OK.

Regards, Almir",nalmir
14971,Dragging from Windows 10 guest to Windows 10 host does not work,Windows,Windows,VirtualBox 5.0.12,2016-01-04T12:50:19Z,2016-01-04T12:50:19Z,"Sometimes it works.

Sometimes, when I drag from guest to host nothing happens and when I try to delete the file I dragged, I get error message (see VB-screenshot-1.jpg).",i8329
15007,installing virtualbox on windows 10 version 1511 throws VERR_SHARING_VIOLATION,Windows,other,VirtualBox 5.0.12,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
13967,NatNetwork limits mtu,Windows,Linux,VirtualBox 4.3.26,2016-01-05T16:20:19Z,2016-01-05T16:20:19Z,"I have 4.3.26 in win7 running.

My guests are linux (redhat 5,4 5.10, opensuse 13.2, ...)

All are connected to a virtualbox NatNetwork

Inside the guests an openvpn client is started and i see, that huge packets that the openvpn client sents will be dropped. I investigated further and found out, that the highest Packet size leaving the host is 1295 bytes long.

",RobbySherwood
15006,Cannot update Win 8.1 to Win 10.0 because of display,Linux,Windows,VirtualBox 5.0.12,2016-01-07T18:27:59Z,2016-01-07T18:27:59Z,"host: opensuse 43.2, linux 4.1.13-5-default x86_64

guest: windows 8.1

Occasionally I get a popup to update to window 10. I say ""Yes!"" It then spits out this message:

... cannot upgrade ...
The display manufacturer hasn't made you display compatible with Windows 10. Check with your manufacturer for support.

It then suggests I buy a new computer. I have tried this with the setting ""Windows 8.1 (64 bit)"" and ""Windows 10 (64 bit)"".

Is there a way to convince the upgrade evaluator that the display really is a marvel of modern technology?
",James Moe
15009,Opening the storage settings causes the font color to be temporary black,Linux,Windows,VirtualBox 5.0.12,2016-01-07T19:58:24Z,2016-01-07T19:58:24Z,"If I'm opening directly the storage settings of a virtual machine the color of the pre-selected text (in my case ""Controller: SATA"") is black while it should be white. But selecting the pre-selected text again fixes the issue.",Sworddragon
14988,Starting 2nd instance takes too much time,Windows,all,VirtualBox 5.0.12,2016-01-08T07:26:42Z,2016-01-08T07:26:42Z,"Starting VB for the first time usually takes only less than 1 second on my computer (Windows 10 with SSD drive). But starting the 2nd instance would always take almost 5 seconds or more. That is not normal.

BTW, this problem has been there for years since I started using VB of 3.x.",Edward Yang
14973,Shared clipboard does not allow to copy files with ctrl-c - ctrl-v,Windows,Windows,VirtualBox 5.0.12,2016-01-08T17:13:49Z,2016-01-08T17:13:49Z,"I tried to copy files via cliboard in VMware and it does it easily.
In VirtualBox copying files via clipboard does not work.",i8329
15017,I get black screen after log out desktop environment.,Windows,Linux,VirtualBox 5.0.12,2016-01-09T04:31:46Z,2016-01-09T04:31:46Z,"Host OS: WES7 SP1, OS X 10.11[[BR]]
Guest OS: Arch Linux


Reproduce process:[[BR]]
1) Set ""CustomVideoMode1"" value to ""1280x800x32"".[[BR]]
2) Start VM. Config guest OS to automatic login to virtual console and autostart X at login using xinit according to https://wiki.archlinux.org/index.php/Automatic_login_to_virtual_console and https://wiki.archlinux.org/index.php/Xinitrc#Autostart_X_at_login. [[BR]]
3) Set the value of ""GRUB_GFXMODE"" of /etc/default/grub file to ""1280x800x32"".[[BR]]
4) Run command ""grub-mkconfig -o /boot/grub/grub.cfg"".[[BR]]
5) Poweroff guest OS and start VM again. At the grub selection OS UI, the resolution of VM screen is 1280x800. Before desktop environment start, the information of systemd showing is fine. My desktop environment is Cinnamon or Mate.[[BR]]
6) Log out Cinnamon or Mate back to tty. I get black screen.[[BR]]
6.1) I didn't know what status of VM, so I clicked Close button on the VM title bar. After close dialog showed up, the black screen disappear, the information of tty can be seen.[[BR]]
6.2) I clicked Cancel button of the close dialog. the black screen came back.",SuperDiver
15013,Symbolic Links,Windows,other,VirtualBox 5.0.12,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
15021,Pressure Sensitivity for USB Multitouch Tablet pointing device,other,other,VirtualBox 5.0.12,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
15024,VirtualBox-GuruMeditation error in Ubuntu,Linux,Windows,VirtualBox 5.0.12,2016-01-11T08:48:08Z,2016-01-11T08:48:08Z,"While working on my Virtual Machine Windows 8.1, I often get this error and my machine stops. The '''VirtualBox-Guru Meditation errors''' says-  ""A critical error has occurred while running the virtual machine and the machine execution has been stopped.""",minig
15005,no 3D accelaration when using WebService or VBoxManage startvm --headless (iGPU HD4000),other,other,VirtualBox 5.0.12,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
15026,VB Crashes after creating a machine,Windows,Linux,VirtualBox 5.0.12,2016-01-11T15:30:08Z,2016-01-11T15:30:08Z,VB Crashes after creating a machine and on startup if one machine is present. I've reinstalled VB and tried beta builds.,mysi
14427,"Oracle 12.1.0.2 Grid Installation fails to relink VB5 on Oracle Linux 6.7 guest,OSX host",Mac OS X,Linux,VirtualBox 5.0.0,2016-01-12T09:18:00Z,2016-01-12T09:18:00Z,"When trying to install 12.1.0.2 Grid Infrastructure on Linux 6.7 guest on OS X (Yosemite) host using !VirtualBox 5 the installer hangs at 59% (after passing all the Oracle pre-requisites) with the error
{{{
error invoking target irman ioracle of makefile /u01/app/gi/12.1.0.2/grid/rdbms/lib/ins_rdbms.mk”
The logs provide further detail.

INFO: /usr/bin/ld: cannot find -ljavavm12
collect2: ld returned 1 exit status

INFO: make: *** [/u01/app/gi/12.1.0.2/grid/rdbms/lib/oracle] Error 1
}}}
It is possible to work around this by copying the libjavavm12.a library located in $ORACLE_HOME/javavm/jdk/jdk7/lib to $ORACLE_HOME/lib directory and retrying the install.

Once the workaround is applied, the installer continues but then the oracle root.sh script fails with a segmentation fault.
{{{
rootconfig.sh: line 131: 4562 Segmentation fault
}}}

A workaround can be applied by reinstalling the Perl binaries under the newly created ORACLE_HOME and the installation can continue.

Both errors and their work arounds are described here:
http://laurent-leturgez.com/2015/05/26/oracle-12c-vmware-fusion-and-the-perl-binarys-segmentation-fault/#comment-7644

Note, this is not my blog but has been very helpful in providing the 2 workarounds for the issue I report here.
It would be great if a permanent fix could be found is it seems this is something specific to Virtual Box 5 rather than an issue with the guest config.",MPMDBA
15020,Modifyvm --hardwareuuid does incorrect validation of input.,all,all,VirtualBox 5.0.12,2016-01-12T14:55:03Z,2016-01-12T14:55:03Z,"In order to help a user I tried to test the trick of fixing a VMs hardwareuuid using the VBoxManage ""modifyvm --hardwareuuid"" command.

First problem is that VBoxManage exited without giving an error message. If there is an error then it should give an error message. After a lot of double checking of syntax I finally guessed what the problem was.

VBoxManage wasn't letting me set a hardware UUID which conflicted with the VM UUID. Since these two UUIDs are in separate address spaces there should be no reason for this check.

To confirm that this check is unnecessary I used the command to set a non conflicting UUID, then edited the .VBox file to make it conflicting - with absolutely no ill effect. I then cloned the VM: the clone inherited the hardware uuid as intended, again with no ill effect.

Since this check blocks one of the obvious uses for this feature I would consider this an important error. Happily it must be trivial to fix.

No logs are attached, since I'm documenting a bug in VBoxManage, not describing a problem with a VM.",mpack
15030,DHCP server on natnetwork doesn't return DNS servers,Linux,Linux,VirtualBox 5.0.12,2016-01-12T15:16:39Z,2016-01-12T15:16:39Z,"If I start up a guest VM on old school nat networking I see an option 6 come thru with the DHCP response from the virtualbox DHCP server.

If I do the same on a natnetwork'd guest all but one of the same options arrive in the DHCP response, including 15 for a DNS domain name, but option 6 is consistently missing and obviously this means the DNS server is never configured inside the guest.
If I set it manually in the guest to the IP I configured under ""VBoxManage dhcpserver add"" everything works as expected so networking is certainly working.

This is easily observed with a linux guest by installing and running dhcpdump while running ""dhclient -d""",tommyvn
3348,Small icons/treeview for guest list,Linux,Linux,VirtualBox 2.1.2,2016-01-13T06:34:55Z,2016-01-13T06:34:55Z,"See also http://forums.virtualbox.org/viewtopic.php?t=14385

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

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

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

I think a good idea would be to make the guest list more like Nautilus or Windows Explorer, treating the guests like files/folders.",sej7278
14882,Windows not shown with Seamless mode if launched headless,all,Linux,VirtualBox 5.0.10,2016-01-13T21:15:42Z,2016-01-13T21:15:42Z,"If a vm is started headless and the seamless attribute is enabled, when you switch to the VM, the windows are not actually shown. They are visible in preview. It has been suggested that switching from headless to seamless is not supported functionality, but there are no warnings about it's unsupported nature nor an error message when you try and do it. Nothing crashes, it just does not work as expected, though it would be really handy if it did.
Example Video's
Seamless: https://youtu.be/WvWGAY0o32g
Headless to Seamless: https://youtu.be/eilD1GP3WlQ
Detachable to Seamless: https://youtu.be/iqev-7uCtXQ",DaVinci
14532,Cannot access webcam over getUserMedia(),Linux,Windows,VirtualBox 5.0.2,2016-01-15T14:22:35Z,2016-01-15T14:22:35Z,"When booting Windows 10 with the latest Edge within Virtual Box 5.0.2 from Ubuntu 15.04 I cannot access the Webcam within Edge.

Beware, it works fine when the website uses a Flash plugin. There the webcam shows up. But NOT when it's being loaded through the getUserMedia() API. It's a native Javascript function most modern browsers implement.

I have the drivers installed. Let me repeat: it works fine through Flash, but not via JavaScript. Can you please look at it? This is blocking the development of www.videomail.io where I need to test it for the latest Edge.

Many thanks!",Michael Heuberger
15041,Video not responding,Windows,Windows,VirtualBox 5.0.12,2016-01-18T08:53:42Z,2016-01-18T08:53:42Z,"Hello,
I have an Acer Aspire aspire vn7-792g with windows 10.
I have installed virtualbox with windows 7 inside, I have installed guest addition and enabled 2d and 3d video acceleration.
After installing guest addition, my acer has a critical problem on display, if it turns off (power saving), the video does not respond.
I must power off the computer, otherwise my display remains black, even if virtualbox is not running.

",matteo
15039,"Assertion failed, Please contact the product vendor!",Windows,Windows,VirtualBox 5.0.10,2016-01-18T09:20:19Z,2016-01-18T09:20:19Z,"I got the message below.

Additional info: It occurred after I was trying to delete some snapshots and got various error messages like access denied and invalid object state. I do not know if these errors were related. This time also my harddisk was getting full and eventually the machine refused even to show up in the VirtualBox window.

Just for additinal note, the snapshot delete functionality currently quite often fails, even when disk has enough room. The failures look random - same snapshot always fails, but which ones will fail and which ones will not for same virtual machine, is not predictable.

{{{
Assertion failed: [m->state == MediumState_LockedRead] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\MediumImpl.cpp' (4411) in long __cdecl Medium::i_createDiffStorage(class ComObjPtr<class Medium> &,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0074,class MediumLockList *,class ComObjPtr<class Progress> *,bool).
Please contact the product vendor!.


Result Code: 
E_FAIL (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}",levitation
15038,Black screen in guest,Mac OS X,all,VirtualBox 5.0.12,2016-01-18T09:40:41Z,2016-01-18T09:40:41Z,"Installed 5.0.12r104815 on Mac OSX 10.11.2 an a MacPro (early 2008). Tried several installs, all with the same result: Starting the guest gets me a black guest window, which resizes itself (so it is actually running). It also doesn't show any boot screen at all.",awado
7174,OS/2 Warp 4 Colors are wrong at 16 million setting,Windows,other,VirtualBox 3.2.6,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
15044,"WebGL doesn't work, OpenGL shows warnings",Windows,Linux,VirtualBox 5.0.12,2016-01-19T21:01:39Z,2016-01-19T21:01:39Z,"Hello all,

I've been trying to use WebGL in a VirtualBox VM. It doesn't work in Firefox and Chrome (and probably others). In general, OpenGL seems to be having issues and is printing alot of warnings and errors.

3D acceleration is turned on. If I turn it off, WebGL works and I don't see all the warnings. But it's unusable. It's very, very slow.

{{{
tperkins@ubu1510vm:~$ firefox
pci id for fd 55: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

The host is Windows 10 64-bit, the guest in Ubuntu 15.10 64-bit. VirtualBox is 5.0.12 (r104815). I also tested a few other guests, and they all had this issue: Ubuntu 15.10 32-bit, Ubuntu 14.04 64-bit, Xubuntu 15.10 64-bit.

Things like `glxgears` are working, but they are showing identical warnings and errors. Hopefully that helps reproduce the issue.

{{{
tperkins@ubu1510vm:~$ glxgears
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
221 frames in 5.0 seconds = 44.191 FPS
289 frames in 5.0 seconds = 57.745 FPS
285 frames in 5.0 seconds = 56.949 FPS
}}}",tprk77
15046,Crash when installing guest additions on Windows 10 (1511 / 10586),Mac OS X,Windows,VirtualBox 5.0.14,2016-01-20T08:53:28Z,2016-01-20T08:53:28Z,"Hello,

After upgrading Windows 10 (guest), which had a previous version of Guest Additions working fine, then using Windows Update to upgrade Windows 10 to build 1511/10586, I can no longer install Guest Additions.  There's no problem with the same VM if I restore a snapshot without the Windows update applied.  Even uninstalling Guest Additions first makes no difference.

The first attempt (see ""VBox.log.2"", attached) causes the installer to abort the VM during installation of ""VBoxDrvInst.exe"".  Subsequent attempts (after rebooting the guest) just cause the installer to exit with an error (see below, copied-and-pasted from installer window, and ""VBox.log"" and ""VBox.log.1"", attached).

Thanks.",cbr.reflexe
7018,Enable user to import custom icons with the file menu and/or automatically from a specified directory.,other,other,VirtualBox 3.2.4,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
14589,Excel 2013 Freezes in VirtualBox,Mac OS X,Windows,VirtualBox 5.0.4,2016-01-20T16:24:35Z,2016-01-20T16:24:35Z,"Host system: Mac OS X 10.10.4 on a MacBook8,1 (we've also noticed that it happens on some other models as well)

Whenever working in Excel 2013, attempting to select cells or input formulas into those cells, whether one or multiple, causes Excel to respond extremely slowly. You can replicate this by selecting a single cell, then dragging your mouse in any direction to select multiple cells. You'll notice the delay significantly. We do not notice this issue in Excel 2010.

Lastly, as a University, we deploy VBox 4.3.30 to all our students which where we are having the issue. We've also been testing on VBox 5.0.4 and noticed the same issue.",mrkmiller88
10153,Resizing from the left and top borders is erratic,Mac OS X,other,VirtualBox 4.1.8,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
15059,Virtual box crash when host pc reboots,Windows,all,VirtualBox 5.0.14,2016-01-21T14:17:55Z,2016-01-21T14:17:55Z,"tested using 5.0.14 on W7 / 64 , W10 32 & 64 bit.
Start Virtualbox, do not start any vm in virtual box
Reboot the host PC
Virtual box will stop the host pc from booting

The first error being displayed is ""Failed to set the global Virtualbox extra data for key GUI/Toolbar to value {}""

",Frank Bevers
15052,VBox Manager icons don't adequately distinguish VMs - icons almost useless,other,other,VirtualBox 5.0.14,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
13033,Gnome Shell Dash Icon-text Drop Shadow Distorted / Skewed,Mac OS X,Linux,VirtualBox 4.3.10,2016-01-22T05:24:35Z,2016-01-22T05:24:35Z,"There is an issue with how VirtualBox renders Gnome-Shell dash icon-text drop-shadows.

The text drop-shadow seems to be offset towards the left of the screen and further skewed / distorted and offset in this direction. See attached images for examples.

This issue can be seen across many different Linux installs, for example Ubuntu Gnome 12.04 (x86-64) with Gnome Shell 3.4, Arch Linux x86_64 with Gnome Shell 3.14, on the host systems: Arch Linux x86_64, Mac-OSX 10.6+ - 10.9.3, and Windows 7.",phearus
13648,VirtualBox 4.3.20 Could Not Initialize GLX,Windows,Linux,VirtualBox 4.3.20,2016-01-22T08:37:28Z,2016-01-22T08:37:28Z,"After upgrading from VirtualBox 4.3.12 to 4.3.20, attempting to run a QML application results in the error: ""Could not initialize GLX"". There appears to be a problem with OpenGL in the guest extensions.

------------
System Info:

{{{
Host:
Windows 7 Professional 64-bit SP1
AMD Phenom II N950 Quad-Core
ATI Mobility Radeon HD5650

VirtualBox v4.3.20 r96997
Extension Pack v4.3.20 r96996

Guest:
Xubuntu
lsb_release: Ubuntu 14.04.1 LTS
uname: Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Relevant Packages:
mesa-common-dev
libgl1-mesa-dev
libglu1-mesa-dev
}}}


-------
Output:

{{{
$ qmlscene test.qml --resize-to-root
libGL error: pci id for fd 10: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
Could not initialize GLX
Aborted (core dumped)
}}}


------------
Sample Code:

{{{
import QtQuick 2.2
 
Rectangle {
  width: 640
  height: 480
  color: 'black'
}

}}}

------------
Qt Download:
http://www.qt.io/download-open-source/",amclain
14007,Cannot Insert Linked Cloned Into Group,Windows,other,VirtualBox 4.3.26,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
14728,Virtualbox crash when closing laptop lid,Windows,other,VirtualBox 5.0.6,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
15077,Suggestion: GUI attaching to headless should default close to 'continue',other,other,VirtualBox 5.0.14,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
15076,Wifi connections goes off,Windows,Linux,VirtualBox 4.3.36,2016-01-25T21:47:43Z,2016-01-25T21:47:43Z,"If I leave my virtual machine in saved state and turn off my pc and then turn it on after sometime my host os looses wifi connection  ,it shows limited .The only workaround is to switch on the vm ,turn it off and then restart the pc .

This doesn't happen if I turn off the vm instead of leaving it in the saved state
",rishabh
15079,Seamless mode : taskbar pinned app contextual menu only visible above guest window,Windows,Windows,VirtualBox 5.0.14,2016-01-26T13:41:16Z,2016-01-26T13:41:16Z,"In seamless mode, the contextual menus for pinned apps are only painted when above a guest window.",Billy Braga
15036,SDK Python webserver bindings IMachine::setGroups() inconsistent signature,other,other,VirtualBox 5.0.12,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
15058,Host+<key> doesn't work if host layout not US,other,other,VirtualBox 5.0.14,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
15083,Win 7 / Linux Guest - Cannot delete backup file on shared folder.,Windows,Linux,VirtualBox 5.0.14,2016-01-27T17:29:59Z,2016-01-27T17:29:59Z,"When a backup~ file is created in a directory within a VirtualBox's shared folder, the program that created the backup~ file cannot remove the file preventing the original file from being saved. Trying to remove the backup~ file manually via 'rm' results in an 'Operation not permitted.' message. The only way to remove the backup~ file is navigating to the directory from the Host system and removing the file that way.",agilis
7461,Cannot delete old and unused VM snapshot.,Linux,Linux,VirtualBox 3.2.8,2016-01-27T20:27:06Z,2016-01-27T20:27:06Z,"Hi all.

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

I'm getting:

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

Details:


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

}}}

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

Regards,

-- Shlomi Fish",Shlomi Fish
15053,Genymotion Virtual Box Host Adapter not found,Windows,Windows,VirtualBox 5.0.14,2016-01-28T10:43:45Z,2016-01-28T10:43:45Z,"Hello, i'm using last version 5.0.14 on Windows XP SP3 togheter with Genymotion. 
I write here because there is a virtualbox error and exactely :
The host network interface with the given name could not be found.

I've tried to delete all interface and when i open genymotion it recreate correctly virtual host adapter...

Thanks for helping",Dario Cdj
14474,start VBoxClient inside virtualbox guest only,all,Linux,VirtualBox 5.0.2,2016-01-28T14:48:42Z,2016-01-28T14:48:42Z,"The guest additions can be installed on systems that do not necessarily
start as a virtualbox guest, for example (but not limited to) on live
media (bootable CD/USB, PXE, ...).
Check whether or not we can detect virtualization, exit gracefully if we
detect non virtualbox system.",Christian Hesse
15042,Can't attach USB device Microchip MPLAB Real Ice,Windows,Windows,VirtualBox 5.0.12,2016-01-28T16:55:18Z,2016-01-28T16:55:18Z,"Failed to attach Microchip MPLAB Real Ice to the VM Windows XP SP3

USB device 'Microchip Technology, Inc. (www.microchip.com) MPLAB® REAL ICE tm (www.microchip.com)' with UUID {30576387-492f-41fa-862e-c9b593202bde} is busy with a previous request. Please try again later.
Codice 'uscita: 
E_INVALIDARG (0x80070057)
Componente: 
HostUSBDeviceWrap
Interfaccia: 
IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
 ",Attylus76
15094,Guest windows move to leftmost monitor on X11 when guest resizes its display,Linux,all,VirtualBox 5.0.14,2016-01-29T19:50:21Z,2016-01-29T19:50:21Z,"I have two Linux host machines running different versions of GNOME (RHEL6 - GNOME 2.28 and Arch - GNOME 3.18), both with multiple (host) monitors.  On both of them, whenever a guest resizes its display (e.g. switching from the bootloader to the guest's GUI, or changing display resolutions from within the guest), the guest window will be moved over to the leftmost monitor if it isn't already there.",Michael Hansen
15045,corrections in OSE build,Windows,all,VirtualBox 5.0.14,2016-01-30T18:30:29Z,2016-01-30T18:30:29Z,"1. Incorrect check of renamed variable (v4->v5): bug5man_ose.patch
2. Absent implib's: ose_st_ssl_web.patch
3. Incorrect check of non-standard latex place: pdf_ose.patch",yjh
14905,Error In supR3HardNtChildWaitFor,Windows,Linux,VirtualBox 5.0.10,2016-02-01T09:27:14Z,2016-02-01T09:27:14Z,"Since last week I've been encountering problem with starting Linux virtual machine. It's now starting about 2 minutes and before start it throws an error (in attachment: error-screenshot.jpg).
I've disabled my Avira antivirus real-time protection but it doesn't help, I hadn't installed any additional software before bug started to appear (only Avira Antivirus had made it's update).",DSProgrammer
5568,unable to perform some svn operations on shared folders from guest,Windows,Linux,VirtualBox 3.0.12,2016-02-01T21:02:56Z,2016-02-01T21:02:56Z,"Host: Windows Vista


Guest: Gentoo


Description:

In the development, I need to use some collaboration system whose gui client in windows sucks. So I plan to share the project direcotries with my guest gentoo and then use the command line client in unix instead.[[BR]]
However, because the client depends on the result of 'svn status' and my netbeans uses its own SCM instead of the native one, I have to do this manually, which fails.[[BR]]
This is the error message when I perform some svn operation like 'svn add':
{{{
svn: Can't move '.svn/tmp/entries' to '.svn/entries': Operation not permitted
}}}
This will never happen if the underlying file system is local since I care little about anything inside the .svn directory. I try to chmod it 777 and find that somehow its permission will get ""reverted"" before svn starts its job.[[BR]]
The shared folders are mounted manually with default options. I can do whatever I wish but not with svn, which sounds weird. I hope this does help.[[BR]]
BTW, vbox rocks!",Marvin
15098,Windows VM defaults are well below the required minimum values to run the OS,other,other,VirtualBox 5.0.14,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
15102,Attached USB device filter causes VM to not start/crash,Mac OS X,Linux,VirtualBox 5.0.14,2016-02-04T09:25:46Z,2016-02-04T09:25:46Z,"When I attach a PAX D200 pinpad device under the USB device filters and then proceed to start the VM the VM crashes. This is the only device I have this problem with and am able to connect similar devices from the same manufacturer without problem.

I have attached the logs and crash report.

Forum post for reference:
https://forums.virtualbox.org/viewtopic.php?f=8&t=66526&p=315196#p315196
",Figomann
15111,Unable to create a Virtual machine,Windows,Windows,VirtualBox 5.0.14,2016-02-04T10:57:21Z,2016-02-04T10:57:21Z,"I am unable to create a for the first time a Virtual Machine .
After creating a Virtual machine call eWinXP  I click on the Machine and I get the following:
A small appeared  saying “You have the Auto capture”
A second message saying : “Creating process for for virtual machine eWinXP (GUI/QT)...(1/2)” and e progress bar with no Progress activity shown.(after 20 min) and no activity on the CD player.
He Mouse pointer shown the only activity.
I could not stop any running program . The only way I cuold regaing control of the computer is by using the “Task Manager”
The “Task Manager” show hat :
eWinXP (Power Off) and Oracle VM VitualBox  Running.
After closing both task the following ERROR message apeared:
Fail to open a session for virtual machine eWinXP
The VM sessuion was closed
Result Code : E_FAIL (0x8004005)
Component : SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
 a Copy of “VboxHardening” file attached  for your information.

I am using Windows 7 Enterprise on a HP Mini5102
 
Thank you for your help 
Ferruccio       






",Ferruccio
15113,VBoxManage controlvm savestate fails on Windows Host,Windows,Windows,VirtualBox 5.0.14,2016-02-05T09:41:16Z,2016-02-05T09:41:16Z,"'''Execute:'''[[br]]
{{{VBoxManage controlvm <vmname> savestate}}}

'''Displays:'''[[br]]
{{{VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)}}}[[br]]
{{{VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 101 of file VBoxManageControlVM.cpp}}}

The pause option also displays the same error message. Other options may produce the same error message.
This issue seems to have first appeared in Sept 2015, see https://forums.virtualbox.org/viewtopic.php?f=6&t=70975",Tim T ASP
15119,Trust wireless mouse locks up virtual box,Mac OS X,Windows,VirtualBox 5.0.14,2016-02-05T18:07:29Z,2016-02-05T18:07:29Z,"Using a trust wireless mouse no. 16592, when starting Windows 7 in Virtual box the mouse locks up. Change to Apple wireless mouse and this now works. Then Apple mouse will then lock up and no way of retrieving System. Forces reboot. Loses un-saved work. No problem when starting Windows XP. This is a recent problem and has only just manifested itself since the last upgrade to 5.0.14",mikey
15126,"""X"" in corner does not close dialog box.",other,other,VirtualBox 5.0.14,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
15131,Alt+MouseScroll is broken,Linux,Windows,VirtualBox 5.0.14,2016-02-09T19:58:57Z,2016-02-09T19:58:57Z,"From some time [Alt] + Mouse ScrollUp/ScrollDown doesn't work.
I've tested it in Photoshop, Indesign, Corel Ventura in the Windows Guest.
A Scroll itself is working also [Alt] itself is working too.
But the combination/shortcut is broken.
Seems like pressing [Alt] makes a Scrolling non-working.
",sarbash
15089,Unable to setup base OS using virtual box,Windows,Linux,VirtualBox 4.3.28,2016-02-10T08:50:11Z,2016-02-10T08:50:11Z,"Hi Team,

I tried Oracle Virtual Box 5.12 and 4.2.28 but unable to start the ubuntu VM.
Seeing below error every time. I got my system reimaged with client Windows 7
{{{
00:00:01.107602          VDInit finished
00:00:01.107602          Loading settings file ""C:\Users\a371216\.docker\machine\machines\default\default\default.vbox"" with version ""1.14-windows""
00:00:01.107602          Loading settings file ""C:\Users\a371216\VirtualBox VMs\manualUbuntu64\manualUbuntu64.vbox"" with version ""1.14-windows""
00:01:42.302389          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false
00:01:42.349395          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
}}}",naveenlekhwar
15136,After upgrade Virtual Box 5.0.14 does not recognise USB Key,Windows,Linux,VirtualBox 5.0.14,2016-02-10T09:56:47Z,2016-02-10T09:56:47Z,"I upgraded VB from version 4.3.18 and the USB Key that has been always recognized is not recognized anymore, tested with all of the versions of USB selected. The USB Key is a Kingston Data Travel with 16GB.

Thanks in advance.",PHOTON
15137,Clearing read-only file attribute from Windows guest result in world writable permission.,Linux,Windows,VirtualBox 5.0.14,2016-02-10T10:11:10Z,2016-02-10T10:11:10Z,"The shared folders of VirtualBox blindly maps read-only attribute of Windows guest to POSIX write permission. This behavior cause dangerous and undesired file permissions are set in the host system.

=== Steps to Reproduce ===
{{{
$ umask
0022
$ ls -l a.txt
-rw-r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Set read-only attribute of the file ""a.txt"", from a Windows guest with the shared folder mounted.
{{{
$ ls -l a.txt
-r--r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Unset read-only attribute of the same file, from the same Windows guest.
{{{
$ ls -l a.txt
-rw-rw-rw- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}

----
VirtualBox respects umask when only creating new files, but it should do the same when mapping read-only attribute (or something similar). Leaving files world writable is simply unacceptable.",JackieKu
12459,Host-only adapter interface resets IP address back to default.,Windows,Windows,VirtualBox 4.3.4,2016-02-10T13:49:02Z,2016-02-10T13:49:02Z,"There is an old defect #8796 that describes this same problem for an older version of Virtual Box.  I don't want this issue to get lost under an old defect so I've created this new one since this was not an issue with the last 2 versions prior to 4.3.4.

Starting with my upgrade to v4.3.4, every couple of days I have to reset my host-only adapter's interface IP back to my user configured one of 192.168.56.1.  It keeps resetting to 169.254.x.x, but only after a few days and I have not been able to identify any trigger.

Windows 7-64-bit with a hosted Windows 2008 R2 server.  The previous version did not have this problem so hopefully this will help to identify the cause.

The reset of the DHCP settings for the host-only adapter remains intact, it's only the interface's IP address.
",GCPeters
15141,Virtualbox and Avira,Windows,Windows,VirtualBox 5.0.14,2016-02-11T08:37:47Z,2016-02-11T08:37:47Z,"Hi,

I want to report a problem with antiviruses, especially with Avira (that is my case).

VirtualBox (5.0.14 but also previous versions) worked fine until I installed Avira on my host pc (Windows 7 Pro x64).
Then it started to slow down and show this error:

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap

The error appear also if the antivirus is disabled and creating exceptions in the real time protection doesn't work either.

If I uninstall Avira on my host pc, everything works fine again.
",Baboo85
9983,Virtualbox doesn't start on Windows 7 x64,Windows,other,VirtualBox 4.1.6,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
15147,Guest OS cannot see Host in Bridged Mode,Windows,Linux,VirtualBox 5.0.14,2016-02-14T10:37:51Z,2016-02-14T10:37:51Z,"I have Windows 10 as a host system and Centos 6 as a guest system.
I am connection to internet by wireless
The issue is that bridged network adapter does not allow automatic ip configuration. So I have setup static ip to connect and the rare thing is the the guest system (centos) can get access to internet, can ping the gateway but cannot ping the host system, but the host system can ping the guest system.
",kecondezo
15151,Ubuntu on VirtualBox crashes when laptop goes to hibernate,Windows,Linux,VirtualBox 5.0.14,2016-02-15T13:38:42Z,2016-02-15T13:38:42Z,"

I am running VirtualBox 5.0.14 on Windows 10. I am running Ubuntu Desktop (I tried 14.04, 15.10 and 16.04 (pre release)) in my VirtualBox environment. When my laptop goes to hibernate the Ubuntu session crashes with the following error:

http://imgur.com/74PYXBN

In case image is not available, the error is:

    The instruction at 0x00007FF92F74E80B referenced memory at 0x0000000000000014. The memory could not be read.

I installed the latest version of the Guest additions.

Reference to AskUbuntu question: http://askubuntu.com/questions/734867/ubuntu-on-virtualbox-crashes-when-laptop-goes-to-hibernate
",martijnburger
15132,Problems getting native resolution on Windows 10,Windows,Linux,VirtualBox 5.0.14,2016-02-16T19:06:25Z,2016-02-16T19:06:25Z,"This ticket concerns how to get native resolution in the Virtualbox graphical frontend when running under a Windows 10 host.

By ""native resolution"", I mean a 1-1 mapping between pixels on the display and pixels in the frontend fullscreen window.

My setup is a laptop with a 2736x1824 screen. Connected to this, I have an external monitor with a 2560x1440 resolution.

The behavior I expect from the frontend is that I always get native resolution when I select a scale factor of 100% in the View menu.

The behavior I get is somewhat complicated. It seems like there are two states: I either get native resolution on the laptop monitor or the external monitor. The switch between these two states goes through Windows display settings:

Assume that we have everything working as expected on the laptop display, with native resolution in the Virtualbox frontend.

Now we connect the external monitor and choose to use only that monitor. When we now select fullscreen in the frontend we only get some scrambled rectangles on the screen. However, if we go from a scale factor of 100% to 125%, we get a screen with proper content, but with a high resolution (higher than the display) from the point of view of the guest, scaled down to fit the display.

Going now to Windows display settings, there is a red sentence saying that we need to sign out in order for all apps to adjust to the new scaling (resolution?). Doing that and restarting the guest and the graphical frontend, we now get (for a 100% frontend scale factor) native resolution.

The same thing happens again when going back to the laptop display.

This is clearly a bug since one shouldn't have to save the machine state, sign out and in again, and restart the vm for every monitor switch. I wish there was a way for Virtualbox to ignore the Windows weirdness and simply have a hard mapping between 100% scale factor and native resolution.

I attach a log from a run where I fail to get native resolution on my laptop display (but do get it on the external monitor).",Mikael Djurfeldt
15153,Invalid machine state: GuruMeditation,Mac OS X,other,VirtualBox 5.0.14,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
14770,merging of snapshots destroys VM,all,all,VirtualBox 5.0.0,2016-02-17T23:24:32Z,2016-02-17T23:24:32Z,"Whenever I try to merge a snapshot, regardless of wether I get error messages about OBJECT NOT FOUND or wether the merge is successful, I am unable to (re)start the VM, since a snapshot file is missing.

Trying to restart Virtualbox GUI ends up in a warning that there are missing disk files, the missing snapshot.

This happens on Linux hosts, OSX hosts, with Virtualbox 5.0.0 to 5.0.8.

For me, its totally breaking virtualbox, and I am forced to downgrade to 4.3.32.

Please just add a comment in case you need more information.",Eduard Warkentin
15070,In the guest muted audio is still playing,Mac OS X,Windows,VirtualBox 5.0.12,2016-02-18T10:05:12Z,2016-02-18T10:05:12Z,"From the Version 5.0.12 until the actual test build 5.0.15 audio is playing, although it is muted in the OS settings. Volume muting in applications (if they are available) works, but all system sounds are still playing. Volume regulation is not possible. Audio is playing with the maximum volume (OS Sounds).",Stefan Vogt
15154,Black screen when connecting to a Windows 2012 server from Windows 10 on VirtualBox,Mac OS X,Windows,VirtualBox 5.0.14,2016-02-22T10:14:55Z,2016-02-22T10:14:55Z,After upgrading my Windows 10 guest to version 10.0.10586 I get a black screen when connecting to a Windows 2012 server with Remote Desktop. I can connect to older versions of Windows Server without problems. I doesn't matter if I disable bitmap caching on the connection or not.,jespers
15168,DOS batch file crashes on run attempt (Command Prompt Only) w98,Windows,other,VirtualBox 5.0.14,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
10759,Can't kill Virtualbox.exe process,Windows,Linux,VirtualBox 4.1.18,2016-02-23T02:41:25Z,2016-02-23T02:41:25Z,"Windows 7 64 bit Host.
Ubuntu 11.10. OS will lock when running certain programs and the virtualbox.exe process will keep running at 25% cpu. Can't kill it in the command line or in task Manager. Only option is to reboot the host Windows 7. ",speedkills20
9066,Shared folders lose guest access to folder contents when folders renamed,other,other,VirtualBox 4.0.8,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
14290,Content of the hosts video memory is shown,Linux,Windows,VirtualBox 5.0.0,2016-02-24T03:39:57Z,2016-02-24T03:39:57Z,"For example if I'm opening an application on the guest system that seems to take advantage of 3D acceleration (in this case ""XPS-Viewer EP"" on Windows XP) I'm seeing content from the memory of the graphics card (for example textures from a game that I have played on the host system before).

Additionally to this issue that I'm seeing content of the graphics card instead of the document this behavior could leak unwanted data to the guest system. Maybe VirtualBox could allocate and zeroing the amount of video memory that is configured for the guest system before it starts to avoid that the guest system can read anything at any time from the host system (the same applies for the system memory if not already done).",Sworddragon
15166,Cannot set Host-only connection on OSX El Capitan Host,Mac OS X,all,VirtualBox 5.0.14,2016-02-24T15:30:28Z,2016-02-24T15:30:28Z,"Hi, guys! I'm really exhausted, I've been searching a solution for my problem, I've seen a lot them: uninstall and reinstall VirtualBox, restarting the Daemons from VirtualBox.sh... but I'm not still unable to set this option. I need this config because I can't reach my IP machine from host and vice versa... I don't if can be due to a bug with OSX El Capitan. Waiting for help or an answer to illuminate me T_T. Thanks!!",Myugen
13933,VirtualBox 4.3.24 Could Not Initialize GLX,Windows,Linux,VirtualBox 4.3.24,2016-02-26T11:11:23Z,2016-02-26T11:11:23Z,"I've a problem with running qmlscene from Qt. The program aborts with message: 'Could Not Initialize GLX'. The program runs fine when '3D acceleration' is switched off in the vm settings.

{{{
Host:
Windows 7 x64
Radeon R7 250

Guest:
Linux arch-vm 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux

VirtualBox:
4.3.24

}}}

{{{
qmlscene
libGL error: pci id for fd 10: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
Could not initialize GLX
Aborted (core dumped)
}}}

I've compiled the Qt with debug symbols and got the following backtrace from qmlscene. 

{{{
#0  0x00007ffff4d494b7 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff4d4a88a in abort () from /usr/lib/libc.so.6
#2  0x00007ffff5e38460 in qt_message_fatal (context=..., message=...) at /home/wojtek/banana-pro/qt5/qtbase/src/corelib/global/qlogging.cpp:1422
#3  0x00007ffff5e34e00 in QMessageLogger::fatal (this=0x7fffffffd3b0, msg=0x7fffee5e64c1 ""Could not initialize GLX"") at /home/wojtek/banana-pro/qt5/qtbase/src/corelib/global/qlogging.cpp:643
#4  0x00007fffee590d75 in createDummyWindow (dpy=0x4296d0, config=0x5e50f0, screenNumber=0, rootWin=373) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:103
#5  0x00007fffee591d3e in QGLXContext::init (this=0x454090, screen=0x438cc0, share=0x0) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:294
#6  0x00007fffee59113f in QGLXContext::QGLXContext (this=0x454090, screen=0x438cc0, format=..., share=0x0, nativeHandle=...)
    at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:170
#7  0x00007fffee55b083 in QXcbIntegration::createPlatformOpenGLContext (this=0x41d470, context=0x44d270) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qxcbintegration.cpp:254
#8  0x00007ffff6ae00fc in QOpenGLContext::create (this=0x44d270) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qopenglcontext.cpp:597
#9  0x00007ffff6a959ed in QGuiApplicationPrivate::init (this=0x41a000) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:1295
#10 0x00007ffff6a92c6f in QGuiApplication::QGuiApplication (this=0x7fffffffda00, p=...) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:561
#11 0x00007ffff71c7193 in QApplication::QApplication (this=0x7fffffffda00, argc=@0x7fffffffd8ec: 1, argv=0x7fffffffe008, _internal=328706)
    at /home/wojtek/banana-pro/qt5/qtbase/src/widgets/kernel/qapplication.cpp:562
#12 0x0000000000405427 in main (argc=1, argv=0x7fffffffe008) at /home/wojtek/banana-pro/qt5/qtdeclarative/tools/qmlscene/main.cpp:412
}}}

The problem seems to be in the following part of code (qglxintegration.cpp:103):

{{{
XVisualInfo *visualInfo = glXGetVisualFromFBConfig(dpy, config);
if (!visualInfo)
   qFatal(""Could not initialize GLX"");
}}}

I think the contents of the dpy are:

{{{
{ext_data = 0x0, free_funcs = 0x42aa00, fd = 3, conn_checker = 0, proto_major_version = 11, proto_minor_version = 0, vendor = 0x428890 ""The X.Org Foundation"", resource_base = 41943040, 
  resource_mask = 2097151, resource_id = 0, resource_shift = 0, resource_alloc = 0x7ffff42a5590 <_XAllocID>, byte_order = 0, bitmap_unit = 32, bitmap_pad = 32, bitmap_bit_order = 0, nformats = 7, 
  pixmap_format = 0x42aa50, vnumber = 11, release = 11701000, head = 0x0, tail = 0x0, qlen = 0, last_request_read = 395, request = 395, last_req = 0x7ffff45a39c0 """", buffer = 0x430a50 ""\217"", 
  bufptr = 0x430a50 ""\217"", bufmax = 0x434a50 """", max_request_size = 65535, db = 0x0, synchandler = 0x0, display_name = 0x428ad0 "":0"", default_screen = 0, nscreens = 1, screens = 0x42ab00, motion_buffer = 256, 
  flags = 0, min_keycode = 8, max_keycode = 255, keysyms = 0x0, modifiermap = 0x0, keysyms_per_keycode = 0, 
  xdefaults = 0x436720 ""Xft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintmedium\nXft.rgba:\tnone\n"", scratch_buffer = 0x0, scratch_length = 0, ext_number = 7, ext_procs = 0x4541a0, 
  event_vec = {0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a70d0 <_XWireToEvent> <repeats 33 times>, 0x7ffff45b1ec0, 
    0x7ffff42a7090 <_XUnknownWireEvent> <repeats 30 times>, 0x7fffee313190 <repeats 17 times>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42fb9c0, 
    0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff0d3d1b0, 
    0x7ffff42a7090 <_XUnknownWireEvent> <repeats 12 times>, 0x7ffff5b1fc50 <repeats 17 times>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 
    0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>}, wire_vec = {0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x0 <repeats 33 times>, 0x7ffff45b1e40, 0x7ffff42a70c0 <_XUnknownNativeEvent> <repeats 30 times>, 0x7fffee30e8c0 <repeats 17 times>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff0d3d0e0, 0x7ffff42a70c0 <_XUnknownNativeEvent> <repeats 12 times>, 
    0x7ffff5b1fc40 <repeats 17 times>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>}, lock_meaning = 0, lock = 0x428b50, async_handlers = 0x0, bigreq_size = 4194303, 
  lock_fns = 0x4287d0, idlist_alloc = 0x7ffff42a55e0 <_XAllocIDs>, key_bindings = 0x0, cursor_font = 0, atoms = 0x0, mode_switch = 0, num_lock = 0, context_db = 0x0, error_vec = 0x0, cms = {defaultCCCs = 0x0, 
    clientCmaps = 0x0, perVisualIntensityMaps = 0x0}, im_filters = 0x0, qfree = 0x0, next_event_serial_num = 1, flushes = 0x0, im_fd_info = 0x0, im_fd_length = 0, conn_watchers = 0x0, watcher_count = 0, 
  filedes = 0x42a9d0 ""\003"", savedsynchandler = 0x0, resource_max = 2097146, xcmisc_opcode = 0, xkb_info = 0x436780, trans_conn = 0x0, xcb = 0x428730, next_cookie = 0, generic_event_vec = {0x0, 0x0, 0x0, 
    0x7fffee314260, 0x0 <repeats 124 times>}, generic_event_copy_vec = {0x0, 0x0, 0x0, 0x7fffee312670, 0x0 <repeats 124 times>}, cookiejar = 0x0}
}}}

I still have to figure out how to get contents of config variable as gdb gives me <incomplete type> when I try to print it.

Please let me know if I can further help. I'd really like to see this problem fixed.",bvr
15185,Support to use mounted devices,Linux,Windows,VirtualBox 5.0.14,2016-02-28T07:26:06Z,2016-02-28T07:26:06Z,For example if I'm mounting an USB drive on my Linux host and then starting with VirtualBox a guest that has this USB device in the filters registered the USB device gets unmounted on my host. Maybe VirtualBox can also support to use these devices on the guests without unmounting them on the host.,Sworddragon
14546,Can't install VirtualBox on Windows 10,Windows,Windows,VirtualBox 5.0.2,2016-02-28T09:08:32Z,2016-02-28T09:08:32Z,"I am not able to install VirtualBox nor 5.0.2 or 5.0.x revision 102467 on my Windows 10 laptop. Previous I updated Windows 8.1 to Windows 10 and all works fine. Now after clean install of Windows 10 i can't use VirtualBox again. I think problem is related to VirtualBox network drivers. I enclose a log file where there is some info:

InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
Installing INF file ""C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf"" ...
Install failed, hr (0x80070005)
VBoxNetCfgWinInstallComponent failed, hr (0x80070005)
Installation failed, rolling back installation set ...
",sal3tra
13998,Windows 8 - VirtualBox Disables Wireless Display Support,Windows,other,VirtualBox 4.3.26,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
15184,"""reopening"" 14286",Linux,Windows,VirtualBox 5.0.14,2016-02-29T08:09:37Z,2016-02-29T08:09:37Z,"Attempted to re-open 14286:  Allowed update, but could not change to open/reopened.

Here is my update to the closed/obsolete ticket:

I'm having this same problem. Just started after applying a kernel patch requiring a reboot. So, I tried to find updates/patches and ended up pulling down the latest RPM for SUSE 13.2 64bit.

Here is what I get when I attempt to fire up my W7 Home Premium under VBox (was a working image prior to the kernel patch).

Failed to open a session for the virtual machine W7 Home Premium.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

VBox 5.0.14 r105127 is what is shown with About VirtualBox

Let me know what more you want for diagnosing this.
",Wylbur
15187,"OS X 10.10 guest on 10.11 host, gurumediation after successful installation",Mac OS X,other,VirtualBox 5.0.14,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
14962,USB devices do not show up in VM,Windows,other,VirtualBox 5.0.12,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
15198,Virtualbox misses keypress isuued just after capture,Windows,Windows,VirtualBox 5.0.14,2016-03-03T19:26:11Z,2016-03-03T19:26:11Z,"Whenever I switch to my guest, either using Alt+tab or just clicking with the mouse inside the guest window, the first and sometimes second keypresses are lost.
This only happens if the keypresses are sent very fast after switching
To reproduce:
Open notepad on guest
Place the mouse cursor inside the notepad window
Host should have focus
Click inside notepad and just as you do that, press 1 2 3 on the keyboard
If you're fast enough, 1 is lost 80-90 % of the time and 2 is lost 50 % of the time
This also happens if you alt+tab from host to the guest

Tested on two different hosts",noir04
14410,"Linux-on-Windows 3D support slow, buggy and generates lots of errors",Windows,Linux,VirtualBox 5.0.0,2016-03-04T10:12:28Z,2016-03-04T10:12:28Z,"I'm running a Ubuntu 14.04.3 LTS guest inside VirtualBox 5.0 (with up-to-date additions) on Windows 7 Enterprise (64-bit) host. When 3D acceleration is enabled, screen redraws are slow and often do not refresh blocks of the screen correctly. For example, flipping through a multi-page PDF often results in half of the page not being redrawn. Also, sometimes the terminal (xterm) doesn't redraw when executing a command, giving the illusion that it didn't execute. Moving the window or scrolling will typically restore the contents of the window to what they should be.

Further, when I run the unity_support_test program, I get a lot of OpenGL warnings. In particular:

{{{
$ /usr/lib/nux/unity_support_test -p
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string:   Humper
OpenGL renderer string: Chromium
OpenGL version string:  2.1 Chromium 1.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+:       yes

Unity 3D supported:       yes
}}}

As you can see, it thinks 3D acceleration works, and it's using the Chromium driver, but could not load the vboxvideo driver and as a result, the 3D accelerated behavior is flaky at best (per the description above).

The workaround has been to disable 3D acceleration and switch to a non-Unity desktop (for speed).",memoryhole
15192,High CPU utilization Windows 7 Ultimate on Virtualbox on Macbook Pro,Mac OS X,Windows,VirtualBox 5.0.14,2016-03-04T13:02:25Z,2016-03-04T13:02:25Z,"Macbook Pro Retina 15-inch Mid 2015
OS X El Capitan 10.11.3
2.8 GHz Intel Core i7
16 GB 1600 MHz DDR3
Iris Intel Pro 1536
1 TB SSD

Virtualbox Version 5.0.14 r105127 for  OS X

Windows 7 Ultimate 64bits running as a virtual machine
4 CPUs
4 GB RAM
200 GB hard disk
PA/NX Enabled
VT-x/AMD-V enabled
Nested Paging enabled

Problem: High CPU utilization 120% or more at random for long period of time reported for ""Virtualbox VM"" process in Activity Monitor even with Windows not performing any user's task. Fan speed increases loud and temperature increases. Goes worst to 200%+ or more with Youtube video for instance or even browsing.

This is a snapshot if I click on the ""Virtualbox VM"" task
The process group is made of:
kernel_task(0) %CPU 2.76
launchd(1) %CPU 0
VboxSvc %CPU 0.28
Virtualbox VM %CPU 125%

The %CPU fluctuates from high to low and then high staying random time at each %

Any log you will need or additional information?, please let know.

I have spent weeks searching in forums and found no match for High CPU for the ""Virtualbox VM"" process, found for kernel and other processes but in the case I am reporting those other cases the processes in my laptop are normal. 

I would like to report that I also have Windows 7 Ultimate 64 bits (same patch level as the one running in Virtualbox) running as a VM with the same configuration, CPU, RAM and disk size in VMWare Fusion Pro 8.1.0 in the same Macbook Pro and I do not see the High CPU problem described here for Virtualbox. ",elzorro
15143,Guest Windows 8.1 64 bits freeze every 2-15 minutes for several seconds/minutes,other,other,VirtualBox 5.0.14,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
15204,Soft lockup - CPU stuck for 22s,Mac OS X,Linux,VirtualBox 5.0.14,2016-03-04T18:15:53Z,2016-03-04T18:15:53Z,"After running a Virtualbox VM brought up with Vagrant for a long period of time, we are eventually unable to reach the host. We are forced to restart the VM in order to be able to connect to it again. The kernel log contains soft lockup errors.

Host: OS X 10.10.4
Guest: Ubuntu 14.04 3.19.0-51-generic:amd64",mdelillo
14961,"Windows 10 Guest: ""vboxvideow8"" is stopped on login, screen resolution drops",Windows,Windows,VirtualBox 5.0.12,2016-03-04T18:30:52Z,2016-03-04T18:30:52Z,"This is similar to #14957 but it still happens with VirtualBox 5.0.12

When starting the VM, the guest (Windows 10/1511) shows the start sreen in the expected screen resolution.[[BR]]
After clicking on screen to get the login fields (user name and password), the screen resolution drops to 1024*768 - after the login it can be increased somewhat, but the automatic adjustment of the guest does not work.[[BR]]
In the system log is an entry that ""VBoxVideoW8"" does not respond anymore and was deactivated by Windows.
",Feuerfloh
4381,windows guest - linux host file permissions changed on shared folders -> Fixed in SVN,Linux,Windows,VirtualBox 3.0.6,2016-03-05T01:44:13Z,2016-03-05T01:44:13Z,"I recently upgraded to 3.0.0. 

I have a number of EXT3 and EXT4 share folders which I access from a windows host via VirtualBox's shared folder handler.  When I access a file in one of the EXT folders it reads and writes to it the first time.  When I modify the file and re-save, or auto save it says it is read-only.  This primarily happens with Microsoft office related products.  [URL=""http://ubuntuforums.org/showthread.php?t=1202151]""]This Thread[/URL] was started by some one having the same problem in 2.2.4  It does not happen on NTFS shared folders.  ",Tvtech
14947,Error message when logging off,Windows,all,VirtualBox 5.0.12,2016-03-05T06:16:04Z,2016-03-05T06:16:04Z,"If I have VB running (not VM) and log off, I get the following error:

[https://forums.virtualbox.org/viewtopic.php?f=1&t=74113#p343094]
",Edward Yang
14946,WiFi problem at user logon,Windows,all,VirtualBox 5.0.12,2016-03-05T14:18:19Z,2016-03-05T14:18:19Z,"Starting from version 10.0.8, I have a very weird problem with WiFi connection at logon. The connection appears good as normal, but actually it is not and no internet connections can be made.

I have to disconnect and reconnect to get network working. This happens verytime I logon my account - with one exception.

The exception is - Everyday in the morning I power on my computer, it works as normal; but after that during the day, even a cold reboot would not work.

My system is Windows 10 (build 10586).
",Edward Yang
15212,BoxManage showvminfo --machinereadable vcpfile property value is not properly escaped,other,other,VirtualBox 5.0.14,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
15216,Guru Meditation after installing FreeDOS,Windows,other,VirtualBox 5.0.16,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
15228,Using Ubuntu 14.04 host and Windows 7 guest only max. 12582911 bytes can be transferred via shared clipboard,Linux,Windows,VirtualBox 5.0.16,2016-03-09T19:00:13Z,2016-03-09T19:00:13Z,"I'm using an Ubuntu 14.04 (fully updated) host and a Windows 7 guest (fully updated). The guest has the new (5.0.16) Guest Additions, which was installed using Windows Safe Mode (so I could install basic 3D acceleration as well).

If I open a random text file of 12582911 bytes (eg. in Notepad) in the guest OS, select it's entire contents and copy it to the (shared) clipboard, then I can paste this into gedit in the host OS.

If I add a single character to the end of the file (so it becomes 12582912 bytes long) and do the same, I cannot paste the clipboards contents into eg. gedit in the host OS.

And of course: anything below 12582911 bytes works too and anything above 12582912 bytes doesn't work. :-)

I tried various apps in the guest (Notepad, Wordpad, Notepad++, Total Commander) to open the text file and copy it's contents to the shared clipboard. And I tried various apps in the host OS too to paste the contents of the clipboard. All showed the same symptom.

I created the test text file in linux using this command (I used unix2dos to convert the text file to DOS/Windows line endings so eg. Notepad won't die on me):
{{{
dd if=/dev/urandom bs=12M count=1 | base64 - | unix2dos | dd bs=1 count=12582911 of=test.txt
}}}

It's contents can still be transferred from guest to host via shared clipboard, but if you add only a single extra character to it, the clipboard transfer fails.

Nothing appears in VB's log or in the host's logs (eg. syslog). Neither when the clipboard transfer works, nor when it doesn't.

In the VM I've ""Shared Clipboard"" set to ""bidirectional"".",muzso
15207,Guest kubuntu freezes just after dektop completes loading (more often if loading while virtualbox is not in focus),Windows,Linux,VirtualBox 5.0.16,2016-03-09T19:22:27Z,2016-03-09T19:22:27Z,"Hello there.

Host='''Win10 x64'''
Guest='''Kubuntu 16.04 x64''' (I had the same issue with 15.10)

It is reproducible on kernel 4.0.X up to '''4.4.4''' at least.

Sometimes, after SDDM login desktop appears and freezes in second. I can move one window in that time or click a button but nothing more: virtual box freezes and closes after 4 or 5 tries. I mean, after click stop button it hangs completely and stops to respond.

I had this issue in 5.0.14, 5.0.15 and now in '''5.0.16'''. I never had such problems with the OS running outside virtual box (I have raw image targetting whole SSD drive)

I didn't find anything interesting in VBox.log, but attached it though.

Oh! And one more thing - if virtualbox window is not minimized and doesn't lose focus during the whole boot procedure, chances to be frozen are decreased. It hangs in >80% of cases when the window loses focus during the boot and ~20% only when it stays focused.",Grief
15229,Can't clone with name of deleted VM / clone,Mac OS X,Linux,VirtualBox 5.0.16,2016-03-09T20:35:09Z,2016-03-09T20:35:09Z,"There's something in the Virtualbox internal resources / information that persists when one deletes
the VM files manually (using OS operations), at least on MacOS.
This might have been a mistake, so there should be a way to recover via restoring
the files / directories and re-initializing the VM from recovered files,
but it might have been purposeful / the result of a bug
or failure that you *don't* want to restore (or don't care to) the missing VM.
So, there should be some way to recover by eliminating any knowledge of that VM name,
so that you can re-use it for another clone.
",SteveCat
15230,Restore VM: VERR_TOO_MUCH_DATA,Mac OS X,Windows,VirtualBox 5.0.16,2016-03-10T06:46:32Z,2016-03-10T06:46:32Z,"Can not restore Virtual Machine: Always getting this error:

Failed to load unit 'vga' (VERR_TOO_MUCH_DATA).


Fehlercode:
NS_ERROR_FAILURE (0x80004005)
Komponente:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",fr
15227,On Ubuntu 14.04 host Windows 7 guest crashes when copying a few MB to shared clipboard,Linux,Windows,VirtualBox 5.0.16,2016-03-10T10:13:44Z,2016-03-10T10:13:44Z,"I've upgraded to VB 5.0.16 this morning and ever since I copy a larger amount of data (simple US ASCII text, a few megabytes) to the shared clipboard on the guest, the latter one crashes.

I'm using an Ubuntu 14.04 (fully updated) host and a Windows 7 guest (fully updated).
The guest has the new (5.0.16) Guest Additions, which was installed using Windows Safe Mode so I could install basic 3D acceleration as well.

The VB log has nothing regarding the crash (meaning that it simply cuts off).
It ends like this:
00:01:52.297240 RTC: period=0x20 (32) 1024 Hz
00:01:52.311908 RTC: period=0x200 (512) 64 Hz
00:01:56.312957 RTC: period=0x20 (32) 1024 Hz
00:01:56.327648 RTC: period=0x200 (512) 64 Hz
00:02:00.328344 RTC: period=0x20 (32) 1024 Hz

The host's syslog (and kern.log) does have some useful info:
Mar  9 18:20:51 mydesktop kernel: [29070.988917] SHCLIP[27199]: segfault at 7f714c3ab5a8 ip 00007f7286ee6e0c sp 00007f7243ffece8 error 4 in libc-2.19.so[7f7286e64000+1bb000]
Mar  9 18:20:51 mydesktop kernel: [29071.180556] vboxnetflt: 0 out of 32992 packets were not sent (directed to host)

I haven't had any VB crashes for a long time, but since the 5.0.14 -> 5.0.16 upgrade using the clipboard became a russian roulette. :(",muzso
14711,Doubleclicking text and dragging no longer works.,other,Windows,VirtualBox 4.3.30,2016-03-10T17:06:31Z,2016-03-10T17:06:31Z,"In a Win XP guest, I can no longer do whole-word text selection by doubleclicking and dragging. This normally lets you select chunks of text in whole words, and is standard across the windows GUI.

I have just upgraded from 4.3.20 to 4.3.30 r101610.

Following the installation of 4.3.30, this no longer works. Doubleclicking text selects a whole word, but you cannot extend it by dragging. The drag does nothing. I don't know whether this is a problem in VBoxSvc, or VBoxAdditions, or was caused by a change in how mouse input is handled in the host code. 

Unfortunately this is a real productivity killer for me.

If anyone can reproduce this bug, or can't reproduce it, I would be very grateful if you could add your findings to this ticket. Thank you.

",dan.pope@…
15234,"Starting virutalbox causes ctrl, shift, alt and super key to stay pressed",Windows,other,VirtualBox 5.0.16,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
14880,Guest Additions donot work on windows 10 host,Windows,Windows,VirtualBox 5.0.10,2016-03-11T06:53:57Z,2016-03-11T06:53:57Z,"I am running Windows 7 guest on Windows 10 host. 
Win 7 runs without guest additions but when i install them windows doesn't start and gives this error message
Load library failed with error 1114: A dynamic link library (DLL) initialization routine failed.
If i go to safe mode and uninstall guest additions then windows runs again. I set 3D unchecked in guest settings. and didn't install Direct3D(experimental)when installing Guest additions.",petergemeni
11980,guest additions should write system time to RTC after adjusting it,Windows,Linux,VirtualBox 4.2.16,2016-03-11T12:45:48Z,2016-03-11T12:45:48Z,"When booting a Linux distribution using systemd, the system time is not automatically written to the RTC during shutdown. For further information & rationale, see <http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html>.

As a result, booting my system under VirtualBox results in the following:

{{{
Jul 22 03:46:06 wintermute kernel: rtc_cmos rtc_cmos: setting system clock to 2013-07-22 02:46:03 UTC (1374461163)
...
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: Superblock last write time is in the future.
Jul 22 03:46:07 wintermute systemd-fsck[443]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: clean, 340335/39321600 files, 138917904/157286139 blocks
...
Jul 22 03:46:08 wintermute systemd[1]: Started LSB: VirtualBox Linux Additions.
Jul 22 13:57:43 wintermute systemd[1]: Time has been changed
}}}

After boot, we can observe the RTC is still wrong:

{{{
$ date
Mon 22 Jul 14:10:15 BST 2013

# hwclock -r
Mon 22 Jul 2013 03:58:44 BST  -0.070616 seconds
}}}

After the guest editions have set the system clock from the host clock, they should set the hardware clock to match. That is, perform the equivalent of `hwclock --systohc`.",Sam Morris
15236,E_FAIL (0x80004005)  MachineWrap IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd},other,other,VirtualBox 5.0.16,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
14262,WIndows 7 64 bits guests crash on 32 bits Linux host with VirtualBox v5.0,Linux,Windows,VirtualBox 5.0.0,2016-03-11T14:17:32Z,2016-03-11T14:17:32Z,"I just upgraded to VirtualBox v5.0 today (I previously tried v5.0RC1 and v5.0RC2 and did not run into any issue), from VirtualBox v4.3.28.

After upgrade (including VBox additions upgrade) I got *systematic* BSOD when attempting to run a Windows 7 64 bits guest from my Linux 32 bits host (the 64 bits guest is running fine when launched from a 64 bits Linux host).
I thirst thought it was because of the old VBox additions (v4.3.28) in the 64 bits guest, so I upgraded these while running the guest on the 64 bits Linux host, but even after the upgrade to additions v5.0 in the guest, the latter kept crashing on boot when launched from the 32 bits host.

I'm attaching 3 screen shots of the BSODs: there doesn't seem to be any common crash point (the VM simply crashes at a seemingly random time during the boot process).

For now, I reverted to VirtualBox v4.3.28 which runs all my guests systems (32 or 64 bits, Windows or Linux) just fine on 32 bits Linux hosts...",dinosaur0
14878,critical error - GuruMed - HP Solution Center (printer software) always causes in 4.3.34 and 5.0.10,all,Windows,VirtualBox 4.3.34,2016-03-13T13:25:02Z,2016-03-13T13:25:02Z,"Hello,
Thanks for the work you put into OVB, I think it is great!

I have run into a problem with the latest releases that I would like your help with. I have been running OVB for about a year or so and have not had a problem with this software until recently. HP Solution Center is an app that is installed with the HP all-in-one printer driver/software and I use it to launch the scanner component. 

It works fine with OVB releases 4.3.30 and 4.3.32, but it causes an issue in 4.3.34 and 5.0.10. I have not tested earlier releases of 5.0.x. 

I have 64-bit Win 7 guest running on Ubuntu 14.04 LTS.
I have a Photosmart C7280 connected via USB 2 EHCI controller. I have also reproduced the issue when setting up the printer as a network device (bridged Intel PRO/1000 MT Desktop (82540EM)), rather than a USB device.

To download the software, go to http://support.hp.com/us-en/drivers/ and enter the model of ""photosmart c7280"", change the selected OS to MS Win 7 (if not already selected), and download PS_AIO_02_Net_Full_Win_WW_130_140.exe (released 2009-10-20). 

I believe during installation you can skip the printer setup. However, I'm not sure if the issue is reproducible without a printer/scanner being set up. I can do more research and update this ticket. 

Once the installation has completed (and after rebooting), the next and final step is to launch HP Solution Center. 

I set the priority to major without knowing the cause or the full effect of this issue. My guess is that it could be affecting other printer software, and possibly more. 

Thanks for your help.
Chuck",ceastus
15241,Screen size in macbook pro,Mac OS X,Windows,VirtualBox 5.0.16,2016-03-13T19:26:26Z,2016-03-13T19:26:26Z,You can not use 100% of the screen size of the MacBook Pro. Looking for graphics drivers windose to virtualboks. I refuse to use MacBook Pro that's why. It is not possible to use.,GoodUser
13321,Mac minibar keeps appearing in Fullscreen when mouse hits the top,Mac OS X,all,VirtualBox 4.3.14,2016-03-14T14:19:18Z,2016-03-14T14:19:18Z,"Tried to 

- clear the ""Dock and Menubar: Auto-show in Fullscreen"" checkbox (Main prefs)
- clear the """"Mini toolbar: Show in Fullscreen/Seemless"" checkbox (VM Settings)
- force and set the ""Application UI Presentation Mode"" prop in all 3 Info.plist (VB, VBVM,  vmstarter), tried values 3 and 4 (restarted VB each time)

Checked the many posts about the matter. For VB and Mac (Mavericks).

But still. In Fullscreen, when the mouse hits the top of the screen, that Mac bar appears.

It is very annoying since the guest OS has its menus on top for convenience.",P!
14572,Can't recover the IP when USB2Ethernet adapter is removed and reconnected.,Windows,Linux,VirtualBox 5.0.0,2016-03-14T16:19:00Z,2016-03-14T16:19:00Z,"= Heading =
IP address not recovered in bridged mode when USB2Ethernet adapter is removed and reconnected.

== Description ==
I'm running VirtualBox-5.0.0-r101573 64bit version on Windows 7 64bit OS, having guest as CentOSv6. The guestos is configured with two network adapters, 1) Host-Only 2) Bridged. When the guestos is booted afresh with the USB2Ethernet adapter connected, the Bridged network obtains the IP properly, But when the USB2Ethernet adapter is removed and reconnected the guestos is unable to fetch the IP and waits indefinitely.

'''Steps to reproduce'''
1. Boot the guestos with USB2Ethernet connected.
2. IP should acquire properly.
3. Remove the USB2Ethernet adapter from the System.
4. Try to restart the network service in the guestos.
5. Unable to fetch the IP and waits indefinitely.

'''Note''': Not tested on other guestos whether the same problem exists or not.",lokesh
15242,cannot open VirtualBox imported any machine (Windows or Linux),Windows,other,VirtualBox 5.0.16,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
15221,VirtualBox 5.0.16 Guest Additions fail to install under RHEL 5.11 64-bit,other,Linux,VirtualBox 5.0.16,2016-03-15T15:06:20Z,2016-03-15T15:06:20Z,"The build fails, and the RHEL 5.11 system becomes unusable: it keeps getting a kernel panic (""not syncing"") at boot time.",Daniel U. Thibault
15246,Menus not displayed when using multiple monitors,Linux,all,VirtualBox 5.0.16,2016-03-16T11:06:10Z,2016-03-16T11:06:10Z,"When multiple monitors are connected to my Linux desktop, menus in VirtualBox are not displayed.

When clicking a menu in the menu bar, or right clicking a VM, no menu appears.

I have tried launching the GUI from the command line, including setting VBOX_GUI_DBG_ENABLED=true and VBOX_GUI_DBG_AUTO_SHOW=true. However, no terminal output is displayed when clicking a menu.

GNOME 3.18.2 on Arch Linux
Intel graphics card with i965 driver, kernel 4.4.0
VirtualBox 5.0.16
",Rainmaker
15248,"""BUG: unable to handle kernel paging request""",Mac OS X,Linux,VirtualBox 5.0.16,2016-03-17T07:02:28Z,2016-03-17T07:02:28Z,"VirtualBox 5.1.6. Host is OSX 10.11.3, guest is recent Arch Linux amd64 (4.4.5 kernel). Guest has VM Guest Additions installed.

The kernel periodically BUGs under heavy load (mostly compiling a large C++ project using `make -j 4`; VM is configured to use 4 CPUs).

Attaching dmesg output, as well as VBOX.log",neilc
14703,shared folders not mounting,Windows,Linux,VirtualBox 5.0.6,2016-03-17T13:39:08Z,2016-03-17T13:39:08Z,"I can't see any shared folders on a debian (jessie) guest, win7 host. The shared folders are set up correctly, This is 5.0.6, with the guest additions rebuilt. This used to work on 5.0.0, not sure if the change to 5.0.6 caused it, or something else (debian update).

error is /sbin/mount.vboxsf: mounting failed with the error: No such device

sudo modprobe -a vboxguest vboxsf vboxvideo
solves it - is that a bug in the guest additions or the OS?

This post pointed me in the right direction:
http://stackoverflow.com/questions/28328775/virtualbox-mount-vboxsf-mounting-failed-with-the-error-no-such-device
Thanks
Nils",Nils
15252,Application Error - Sudden crash,Windows,other,VirtualBox 5.0.16,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
15253,USB does not with VirtualBox 5.x on OpenIndiana,Solaris,Windows,VirtualBox 5.0.14,2016-03-18T05:12:42Z,2016-03-18T05:12:42Z,"Guest: Windows XP with CH-340 USB to Serial driver installed
Host: SunOS watt 5.11 oi_151a9 i86pc i386 i86pc  (OpenIndiana)
VirtualBox: 5.0.14 with the extension pack installed

The USB to Serial adapter works fine in VirtualBox 4.*, but does not communicate in Virtual 5.x. The device does enumerate and shows up in the guest's Device Manager.

The VM log contains a number of:
00:00:37.203270 USBProxy:Command 0xc0185694 failed. Req.rc=VERR_PIPE_IO_ERROR
00:00:37.203291 USBProxy:usbProxySolarisUrbQueue Failed!! pProxyDev=0000000002828360[proxy 1a86:7523] pUrb=000000000282a5f0 EndPt=0x1 bEndpoint=0x81 enmType=3 enmDir=1 cbData=8 rc=VERR_PIPE_IO_ERROR

followed by...

00:00:39.525634 PCNet#0: Init: ss32=1 GCRDRA=0x01ae4420[64] GCTDRA=0x01ae4020[64]
00:00:41.820029 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:42.208793 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:52.389837 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices

Current workaround is to remain on VirtualBox 4.x
",Deece
15250,No sound in W2012-2008 Server,Windows,Windows,VirtualBox 5.0.16,2016-03-18T14:38:57Z,2016-03-18T14:38:57Z,"Sound device is detected, but Audio Output is absent.

For Server version of Windows only. Workstation versions are emulated fine.",MikhailRokhin
15255,USB devices not recognized when attached after wakeup,Mac OS X,other,VirtualBox 5.0.16,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
7968,Protocol error with junctions in shared directory,Windows,Linux,VirtualBox 4.0.0,2016-03-21T16:14:42Z,2016-03-21T16:14:42Z,"Host: Win XP Pro SP3 32bit[[BR]]
Guest: Ubuntu 10.04 32bit

In a shared directory on the Windows host I have created junctions (aka ""reparse points"") to other directories. When using guest additions 3.2.12 these are treated as regular directories and the contents of the linked directory is shown.

With guest additions 4.0.0 (both versions tried in the same VM in VB 4.0.0) when I try to ""cd"" into one of the junctions, I get an error like
""bash: cd: Junction: Protocol error"" where ""Junction"" is the name of the junction.

",Michael Butscher
15258,booting issue,Linux,Linux,VirtualBox 5.0.16,2016-03-22T10:29:14Z,2016-03-22T10:29:14Z,"i installed kali as VM 
every time i boot it : i get black screen with Loading , Please wait 

which never goes away ",zee.21
15264,[Request] Add PCI segmentation support on I/O MMU Virtualization,Windows,all,VirtualBox 5.0.16,2016-03-22T13:51:08Z,2016-03-22T13:51:08Z,"Current PCI passthrough support up to Bus/Device/Function only.

For example:
'VBoxManage modifyvm ""VM name"" --pciattach bus:device.function'

Request to add PCI segmentation support on I/O MMU Virtualization, such as:
'VBoxManage modifyvm ""VM name"" --pciattach segment,bus:device.function'",alexander3133
15265,Touchscreen and scaling screen does not fit,Windows,Windows,VirtualBox 5.0.16,2016-03-22T17:12:31Z,2016-03-22T17:12:31Z,"Hello,
I use Virtualbox Host Windows 10 and Guest Winsows 10 with USB-Multitouch-Pointer.
By Scalingfaktor 100% all works fine. By other Scalingfactor i.e. 150%  the position of the touch-input is wrong on Desktop.
I've tried 5.0.17 -> same Problem.

Scaling display is a very usefull feature at HD-Displays, so please fix the bug :-)

Sorry about my worst english

chriskl

ps: my Hardware is HP Spectre X360 13-4104ng",chriskl
15266,VirtualBox 5.0.16 - Windows 10 Host- Bridged Network,Windows,Linux,VirtualBox 5.0.16,2016-03-23T02:58:01Z,2016-03-23T02:58:01Z,"Hello,

I have on Windows 10 Host the !VirtualBox 5.0.16 installed and try a Linux Guest with bridged Network.
On Network tab, i can select the bridged network as interface and then the physical network device from windows.
I am try to install a fresh Linux Ubuntu 14.04 LTS Server. This works fine, but the DHCP Service will not found from Linux. After setting up manual IP-addresses it will not be better. The Interface appears in the Linux system but no ping or other communication will work.

The IP-range is correct, the addresses also. Any idea what is the problem and what can i do?

Thanks Sascha",svalcken
15237,random BSOD on Win7 x64,Windows,Linux,VirtualBox 5.0.16,2016-03-23T03:51:32Z,2016-03-23T03:51:32Z,"Got several random BSOD on my WIN7 Dell Laptop while having Vbox running.


",theetete
14731,"Fedora 22 Host, Windows 7 Guest: switch to seamless turns windows objects into a dark shadow",Linux,Windows,VirtualBox 5.0.6,2016-03-25T23:33:36Z,2016-03-25T23:33:36Z,"Hello,

 in the following configuration:
- Lenovo T440p
- VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
- VirtualBox 5.0.8 (but it occurs with any 5.x - it was ok with 4.x)
- Host: Fedora 22, kernel 4.2.3-200.fc22.x86_64
- Guest: Windows 7 (you can reproduce with Oracle OBI7.3), 4GB ram, 256M video memory

I experience this behaviour:
- (optional) Set the host desktop background to blue and the guest to yellow to have good contrast
- Switch to full screen (successful)
- Switch to seamless mode (unsuccessful)
  - because the windows bar and the windows start menu appear in black
  - windows is unusable
  - you can send ctrl-alt-canc and switch off the guest

I have a video capture I can send.
Thanks.",Billamay77
15275,No host-only adapter,Windows,other,VirtualBox 4.3.12,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
15276,copy&paste alter guest opened file,Windows,Linux,VirtualBox 5.0.10,2016-03-26T15:40:26Z,2016-03-26T15:40:26Z,"Hi All,

I have problem with the share functionalities. When I open for editing a shared file just on the quest (used VBox shared folder, e.g. code editing) and I continue to work in the host (e.g. browsing on the net) and I using copy-paste, sometimes in the guest my text cursor moved and guest clipboard pasted in that position. So paste event triggered on both machines (different content). This problem sometimes I have just working on the guest e.g. editing not a shared file: paste at the end, continue to typing, scroll up and last pasted text inserted multiple times in the old text. These are very annoying.
I had no time to experiment exact what are the problems or reinstall and reconfigure the guest. I will do..., but first I just wanted to know if anyone had a similar issue and if this issue was 'fixed'.
 
Host: Windows 7
Guest: openSUSE 13.1
Enabled: shared copy&paste, drag&drop, shared folder

Regards,",bandki
15291,Linux Gest - Console black in Full Screen,Windows,Linux,VirtualBox 5.0.16,2016-04-04T11:55:38Z,2016-04-04T11:55:38Z,When running Debian (current version 8.3) on a Windows host (Windows 8.1 Pro) in fullscreen switching from Gnome desktop to one of the other ttys (e.g. Hostkey-F1 to get tty1) results in a black screen. Doing the same in window mode (but maximized) does work fine.,jeansen
15282,USB subsystem or USB logging is broken,Mac OS X,Linux,VirtualBox 5.0.16,2016-04-05T08:11:04Z,2016-04-05T08:11:04Z,"The USB subsystem is broken either itself or the logging.

I have a USB device that supports CDC and UVC. Putting UVC aside, I want to talk CDC with the device, but only get garbage. For that reason I ran usbmon on the Linux guest and USB logging from VirtualBox to identify the problem. The USB log from VirtualBox is garbage. Unfortunatly, I can not verify if it is only the logging or f VirtualBox send this out.

I attached the plain text log from the guest and from Virtual Box. Both should be equal, but its not.

The most obvoius is packet number 107 in guest and number 104 in host:

Guest
{{{
Frame 107: 71 bytes on wire (568 bits), 71 bytes captured (568 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x21
    bRequest: 32
    wValue: 0x0000
    wIndex: 2
    wLength: 7
Leftover Capture Data: 00c20100000008
}}}

Host
{{{
Frame 104: 72 bytes on wire (576 bits), 64 bytes captured (512 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x21
        0... .... = Direction: Host-to-device
        .01. .... = Type: Class (0x01)
        ...0 0001 = Recipient: Interface (0x01)
    bRequest: 32
    wValue: 0x0000
    wIndex: 2 (0x0002)
    wLength: 7

No.     Device Source Destination Protocol Length Info URB type URB transfer type Data length [bytes] Leftover Capture Data bString
    105 3          0.3.0                 host                  USB      72     URB_CONTROL out[Packet size limited during capture]             URB_COMPLETE URB_CONTROL       0                                         

Frame 105: 72 bytes on wire (576 bits), 64 bytes captured (512 bits) on interface 0
USB URB
[Packet size limited during capture: USB truncated]

No.     Device Source Destination Protocol Length Info URB type URB transfer type Data length [bytes] Leftover Capture Data bString
    106 3          host                  0.3.0                 USB      71     Unknown type c2 Request                                         URB_SUBMIT URB_CONTROL       0                                         

Frame 106: 71 bytes on wire (568 bits), 64 bytes captured (512 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x00
        0... .... = Direction: Host-to-device
        .00. .... = Type: Standard (0x00)
        ...0 0000 = Recipient: Device (0x00)
    bRequest: Unknown (194)
    wValue: 0x0001
    wIndex: 0 (0x0000)
    wLength: 8
}}}

Here it can be seen that the ""left over capture data"", the actual data of the USB request (setting baudrate to 115200 bps) is recognised as a 2nd USB packet. As 0xC2 is detected as request type, 0x01 as wValue, and 0x08 as wLength instead as part of the packet number 104.",Pingu
2720,Seamless mode has issues on dual head hosts,Linux,Windows,VirtualBox 3.0.2,2016-04-06T23:23:28Z,2016-04-06T23:23:28Z,"I'm using 2 monitors, configured via xrandr --output VGA --below LVDS.
When switching on seamless mode, vbox hides and I see black screen, (no any output), but I can press Home+L - and return to previous mode.",Maksim Melnikau
15002,VRDP audio forwarding broken on Windows 10 RDP client,Linux,Windows,VirtualBox 5.0.12,2016-04-10T23:40:52Z,2016-04-10T23:40:52Z,"Hey,

My host is a NAS-like CentOS 6 box with no attached monitor, no X server and no sound card. On it I spawn a bunch of lightweight bridged Windows machines for browser testing and connect to them from my desktop PC running Windows (gigabit LAN between the client and server).

This setup worked flawlessly with Virtualbox 4.3 and Windows 8.1. I've stopped using the VMs for a while and recently ressurected them with the following changes:

* Updated to Virtualbox 5
* Switched desktop to Windows 10

Since I did that, I'm getting choppy high pitched audio when connecting to the VMs (both before and after installing guest additions). The emulated chipset is Intel HDA and the driver is obviously Null as the host doesn't have a sound card. I originally thought this was an emulation issue, however:

* after doing some research about other issues about windows 10 clients being unable to connect in previous versions
* and reading on some other oracle website that VRDP only supports 22050 audio (not explicitly related to vbox, but pretty sure the V stands for the same thing),

I believe the issue is strictly related to the changes in the Windows 10 RDP client because:

1. playing back a realtime 22050hz stream on a 44100 output device would explain both symptoms (high pitch caused by the freq mismatch and choppiness caused by buffer underrun)
2. setting up a windows RDP server on a guest (tested on a win10 guest) and connecting to that works flawlessly

Unfortunately, I don't have a Windows 7 box to test this on, but I'm going to try some RDP-ception later today.
",Radu Dan
15273,"Inconsistent state of attached disks, cannot close medium",Linux,other,VirtualBox 5.0.16,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
15310,Auto-resize Guest Display not working,Mac OS X,Linux,VirtualBox 5.0.16,2016-04-14T19:26:21Z,2016-04-14T19:26:21Z,"Host: Mac OS 10.10.5 Macbook Pro retina 15 inch with an external auria EQ276W 27"" monitor
Guest: Debian Jessie
Guest using two displays

I have auto-resize guest display enabled

In full screen mode with the primary screen on the Auria and the secondary screen on the macbook it works fine with both.
If you unplug the DP while in full screen mode it still work fine.
However if you exit full screen mode with the two screens on the macbook (external monitor still unplugged), the window for the primary display has a scroll bar on the right and bottom (ei it doesn't resize).
Also if you go back into full screen mode the primary screen no longer fits on the macbook.

Let me know if you need any additional information.

",ranamala
15312,Ubuntu doesn't get to desktop when 3D acceleration is enabled,Windows,Linux,VirtualBox 5.0.16,2016-04-15T17:20:34Z,2016-04-15T17:20:34Z,"I have guest additions with 3D acceleration enabled.
The client is Ubuntu 14.04 LTS

When launching Ubuntu, I can log in but it doesn't make it all the way through to the full desktop. The OS is basically unusable.",raduzard
15314,More complete build number in log file.,Windows,all,VirtualBox 5.0.16,2016-04-18T10:09:12Z,2016-04-18T10:09:12Z,"Would it be possible to give more precise Windows Host version in the VBox.log file?

Concrete example: VBoxHardening.log quotes a Windows version as 10.0.10586.122, whereas VBox.log quotes it as 10.0.10586.  From what I can gather, 10580.0 was released last November, whereas 10580.122 is the latest bleeding edge insider version released AFTER the current VBox version, so the minor build number is important information for support purposes.

This is an enhancement suggestion not a bug report, hence I'm not including log files.",mpack
15321,Enhancing vbox-img from VBoxManage,Linux,Windows,VirtualBox 5.0.18,2016-04-19T19:13:56Z,2016-04-19T19:13:56Z,"vbox-img is capable of doing things from VBoxManage and maybe this can be enhanced further to contain all useful things from VBoxManage that affect disk images. For example ""vbox-img compact"" does not show any progress while I remember that ""VBoxManage modifyhd"" has done this which could also be implemented in vbox-img.",Sworddragon
15323,Sandisk Extreme SDCZ80 flash drive 'no medium found',Mac OS X,all,VirtualBox 5.0.18,2016-04-19T20:04:26Z,2016-04-19T20:04:26Z,"When connecting a Sandisk Extreme SDCZ80 64GB (partitioned as either fat32 or exfat) to either a Linux or Windows 7 guest OS in VirtualBox 5.0.18 running on OS X 10.11, the flash drive is recognised by the guest OS, but in all instances it appears as an empty drive.

On the Windows 7 VM trying to access the flash drive pops up a message requesting to insert a disk (as it does with an empty DVD drive). When trying to access the drive in Linux (Ubuntu) the OS errors ""cannot open /dev/sdb: No medium found"". Also, while lsusb on the Linux VM lists the device and /dev/sdb is created, Gparted does not list the drive for formatting and no /dev/sdb1 partition is present on the Linux VM.

The Sandisk Extreme SDCZ80 mounts fine on dedicated Linux, Windows 7 and OS X hosts. Data can be copied and read without issue. Only when using the Sandisk Extreme USB3 flash drive inside of VirtualBox VM's do they appear as an empty drive.

Other USB3 flash drives do not exhibit this behaviour in VirtualBox and data on the drives is accessible without issue inside both the Linux and the Windows 7 VM. The problem only manifests itself with the Sandisk Extreme SDCZ80 64GB model.

Dmesg output (from the Linux guest VM)
{{{
[   28.654211] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[   28.680737] usb 2-1: New USB device found, idVendor=0781, idProduct=5580
[   28.680741] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   28.680743] usb 2-1: Product: Extreme
[   28.680745] usb 2-1: Manufacturer: SanDisk
[   28.680746] usb 2-1: SerialNumber: AA010118161550470319
[   28.708104] usb-storage 2-1:1.0: USB Mass Storage device detected
[   28.708196] scsi host3: usb-storage 2-1:1.0
[   28.711502] usbcore: registered new interface driver usb-storage
[   28.717525] usbcore: registered new interface driver uas
[   29.708039] scsi 3:0:0:0: Direct-Access     SanDisk  Extreme          0001 PQ: 0 ANSI: 6
[   29.712811] sd 3:0:0:0: Attached scsi generic sg2 type 0
[   29.718321] sd 3:0:0:0: [sdb] Attached SCSI removable disk
}}}

lsusb output (from the Linux guest VM)
{{{
vm@xubuntu:~$ lsusb
Bus 002 Device 002: ID 0781:5580 SanDisk Corp. SDCZ80 Flash Drive
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
}}}

Output when trying to access the drive using cfdisk (from the Linux guest VM)
{{{
vm@xubuntu:~$ sudo cfdisk /dev/sdb
[sudo] password for vm: 
cfdisk: cannot open /dev/sdb: No medium found
}}}

So in summary:
1. Other (somewhat slower) USB3 flash drives work fine in these VirtualBox VM's (they all mount and can be read without issue on both a Linux and Windows 7 VM)
2. The Sandisk Extreme 64GB works fine on dedicated hardware and can be mounted and read by different operating systems (Windows 7, OS X, Linux). But it's detected as a drive without any media inserted (like a DVD drive) on both the Linux and Windows 7 VMs in VirtualBox.

",crahan
13083,Always On Top option for guest window in Windows host,Windows,BSD,VirtualBox 4.3.12,2016-04-22T13:11:50Z,2016-04-22T13:11:50Z,Would you be so kind and make Always On Top option for guest window of Windows host? Thank you in advance.,MikhailRokhin
15014,"Virtual Machine returns duplicate network packets (host SLES 12, guest Win Server 2008, VirtualBox 5.0.4)",Linux,Windows,VirtualBox 5.0.4,2016-04-23T22:04:55Z,2016-04-23T22:04:55Z,"Hello,

the virtual machine with Win Server 2008 and static IP address connected to host machine with SLES 12 via bridged network interface returns duplicate network packets.

First I noticed it when sending ping requests to the virtual machine from another host in the network. The ping returns DUPs. Then I started wireshark on hosting machine and I tested the issue also with netcat: sending simple echo from the virtual machine results to double response received by netcat in my laptop. The wireshark clearly shows that the virtual machine sends back duplicate packets for ICMP, UDP and (testing with SNMP traps) also for TCP protocols.

Would you know whether the higher releases of the virtualbox fix this problem? 

Best rgards
mca0001",mca0001
15343,Internal networking remark on same UID policy is misleading,other,other,VirtualBox 5.0.18,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
15340,Mac OS X operating system running virtual box with Ubuntu cannot access internet,other,other,VirtualBox 5.0.18,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
15347,RPC_S_SERVER_UNAVAILABLE when logging off host while VirtualBox.exe is running,Windows,other,VirtualBox 5.0.18,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
12933,unable to save machine state in case of host reboot/shutdown event,Windows,all,VirtualBox 4.3.10,2016-04-25T13:20:37Z,2016-04-25T13:20:37Z,"Host: Windows 7 SP1 x64[[br]]

When a shutdown/reboot event is issued on the host OS, the VirtualBox frontend presents, to the user, the Close VM window, allowing the user to save or properly shutdown the guest. But saving the VM state isn't possible, because the VirtualBox COM service (VBoxSVC) exits immediately. The user is only able to shut down or power off the VM. When choosing to save the state, the user encounters this error:[[br]]

{{{
Failed to save the state of the virtual machine .

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
}}}",Mihai Hanor
15350,"Cannot use , (comma) as a shortcut key",Windows,Linux,VirtualBox 5.0.16,2016-04-25T16:29:00Z,2016-04-25T16:29:00Z,"Trying to use comma as a shortcut key (In this case for show-menu-bar >>> File - preferences - input - virtual machine - show-menu-bar - HOST+, (comma))

While the comma can be used as a shortcut, it no longer works after restarting VirtualBox and isn't visible in under file-preferences-...

Looking in %user%/.VirtualBox/VirtualBox.xml <ExtraDataItem name=""GUI/Input/MachineShortcuts"" value=""..."">
The keyboard shortcuts are saved in a comma-delimited list, so it just sees the comma as an extra delimiter, and fails to read it.

I worked around this by using < and > as shortcuts, as opposed to , and .

I might get to submitted a code fix, but low priority so I will just log the issue incase someone else is already in that section of code",CraigK
15352,Poor/missing documentation of Balloon parameters,Linux,other,VirtualBox 5.0.18,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
15353,Incorrect quoting in balloon control startup script,Linux,other,VirtualBox 5.0.18,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
15364,USB shadowing to a temp drive (USB boot drive testing capability),other,other,VirtualBox 5.0.18,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
15361,HDA fails to restart when LPIB == CBL,all,other,VirtualBox 5.0.18,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
15367,Cannot remove 4.3.12 Bridged Network Miniport Driver - Bridget Networ not working,Windows,all,VirtualBox 5.0.18,2016-04-28T13:11:53Z,2016-04-28T13:11:53Z,"Hi,
Bridged Network does not work anymore after updating to any 5.x version. There are still remains of the old 4.3.12 driver in the device manager (with exclamation mark) wich I can't ether uninstall or repair. Uninstalling VBox 5.0.18 rebooting, re-installing has no effect. No new drivers were installed. 

I also tried to remove involved keys from the registry, but I could not delete them for whatever reason. I'm running windows 8.1.
",Elsni
15359,20% clock drift in the guest,other,other,VirtualBox 5.0.18,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
15163,iMac running 10.11.3 reboots everytime a VB image is started (host_vmxon),Mac OS X,all,VirtualBox 5.0.14,2016-04-29T08:53:27Z,2016-04-29T08:53:27Z,"After upgrading to the 5.0.14 version of VirtualBox, every time I attempt to launch an existing VB image, or create a new image and start that, the host machine reboots. ",Scott M Stark
14538,Ubuntu 15.04 Desktop - vboxautostart does not work on boot (no output),Linux,other,VirtualBox 5.0.2,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
15369,mac osx i5 crashes when 3+ vms are using > 90% cpu each,Mac OS X,other,VirtualBox 5.0.18,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
15382,Failed to create the host-only adapter,other,other,VirtualBox 5.0.20,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
15370,Exception Breakpoint,Windows,Windows,VirtualBox 5.0.20,2016-05-04T06:54:13Z,2016-05-04T06:54:13Z,"Windows XP guest on a Windows 7 Host
In VirtualBox manager, upon restoring from a save state
I get a Breakpoint exception message (see attached image)
The status of the guest then becomes ""Aborted"".
Upon restoring from this state, the guest boots up correctly.
If I then Save the state of the guest,
then the next time I try to restore it I get this Exception Breakpoint message again.",keuk
15387,"""VirtualBox Guest Additions update available"" wording out of date",all,all,VirtualBox 5.0.20,2016-05-04T13:56:44Z,2016-05-04T13:56:44Z,"When Guest Additions detects that a newer version of the host is running, it will pop up a message like:

""Your guest is currently running the Guest Additions version X. We recommend updating to the latest version (Y) by choosing the install option from the Devices menu.""

In older versions of VirtualBox this wording was fine, as the Devices menu had an entry ""Install Guest Additions"". However, for several versions now the entry is instead ""Insert Guest Additions CD image"".

So I think the wording in the popup should be changed to something like:

""Your guest is currently running the Guest Additions version X. We recommend updating to the latest version (Y) by choosing the option to insert the Guest Additions CD image from the Devices menu.""",JohnVeness
15389,GUI - netwok status icon - context menu => named networks,all,all,VirtualBox 5.0.20,2016-05-04T22:14:25Z,2016-05-04T22:14:25Z,"in the GUI the network status icon has context menu entries regarding the configured networks - to switch the network connection on or off.

these networks names (at the moment just enumerated) should be better named corresponding the names in the configuration PLUS the info for the connected network.
best would be having a way to give individual names in configuration menu and show these individual names.

Many thanks in advance!",SL_1
15391,TTL Expired in Base Machine if 2 VM's runnig,Windows,Windows,VirtualBox 5.0.18,2016-05-05T15:21:21Z,2016-05-05T15:21:21Z,"Been using Virtual box for Years, but I have notice a problem lately ( last week). Using !VirtualBox 5.0.18 r106667

Each of my VM's have 2 Interfaces , one set as bridged (IPV4 Static) , one set as NAT (DCHP) . The NAT interface is set as Cable Disconnected to Keep VM from internet unless I specifically need it.

Now down to my problem, my network on my base machine seems to have TTL Expire errors when I ping 8.8.8.8 from base machine while I have 2 VM's running as soon as I pause them or switch them off/suspend them the TTL EXPIRE error disappears. I have tried with and without the network interfaces in the VM enabled. This can be seen by the time the XP Splash screen shows on Second machine rather than once XP is fully running. 


Ping to 8.8.8.8 from Base machine as second VM is started
{{{
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 8.8.8.8: bytes=32 time=33ms TTL=58
Reply from 8.8.8.8: bytes=32 time=30ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
}}}

Routing Tables from Base Machine
{{{
===========================================================================
Interface List
 28...1a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter
 16...2a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 31...0a 00 27 00 00 1f ......VirtualBox Host-Only Ethernet Adapter
 12...d4 be d9 84 d1 0b ......Realtek PCIe GBE Family Controller
  8...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 21...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
 13...b8 76 3f 20 74 c1 ......Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz)
 23...00 ff 99 5b a6 25 ......TAP-Win32 Adapter V9
 43...00 ff ea 7f 81 0e ......TeamViewer VPN Adapter
  3...b8 76 3f 20 74 c2 ......Bluetooth PAN HelpText
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.176     20
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.172     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     172.16.228.0    255.255.255.0         On-link    172.16.228.176    276
     172.16.228.0    255.255.255.0         On-link    172.16.228.172    281
   172.16.228.172  255.255.255.255         On-link    172.16.228.172    281
   172.16.228.176  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.172    281
     192.168.10.0    255.255.255.0         On-link      192.168.10.1    276
     192.168.10.1  255.255.255.255         On-link      192.168.10.1    276
   192.168.10.255  255.255.255.255         On-link      192.168.10.1    276
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    266
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    266
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    266
    192.168.184.0    255.255.255.0         On-link     192.168.184.1    276
    192.168.184.1  255.255.255.255         On-link     192.168.184.1    276
  192.168.184.255  255.255.255.255         On-link     192.168.184.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.56.1    266
        224.0.0.0        240.0.0.0         On-link    172.16.228.176    276
        224.0.0.0        240.0.0.0         On-link    172.16.228.172    281
        224.0.0.0        240.0.0.0         On-link      192.168.10.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.184.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.56.1    266
  255.255.255.255  255.255.255.255         On-link    172.16.228.176    276
  255.255.255.255  255.255.255.255         On-link    172.16.228.172    281
  255.255.255.255  255.255.255.255         On-link      192.168.10.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.184.1    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 31    266 fe80::/64                On-link
 13    281 fe80::/64                On-link
  8    276 fe80::/64                On-link
 21    276 fe80::/64                On-link
 13    281 fe80::558:9d49:604d:8884/128
                                    On-link
 31    266 fe80::5565:d785:2df6:9cb6/128
                                    On-link
  8    276 fe80::88b5:5871:7b28:d87/128
                                    On-link
 21    276 fe80::c9b3:ca08:7e8b:6e66/128
                                    On-link
  1    306 ff00::/8                 On-link
 31    266 ff00::/8                 On-link
 13    281 ff00::/8                 On-link
  8    276 ff00::/8                 On-link
 21    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
}}}


VM Log ATTACHED",mad4x4
14155,Double-click-hold doesn't work,Windows,Windows,VirtualBox 4.3.28,2016-05-06T18:33:33Z,2016-05-06T18:33:33Z,"I had VBox 4.3.24 and updated to 4.3.28. Since then, holding the mouse button on a double-click doesn't work on my Windows guests. This method of text selection is available on several applications (like Notepad++ and most IDEs) to extend the selection on a word-by-word basis.

This doesn't seem to be a Guest Additions problem since I tried another VM with an older version of Guest Additions and I had the same problem.
",Constantine Dokolas
15208,SSL certificate error on update check,Mac OS X,other,VirtualBox 5.0.16,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
15394,GetLogicalProcessorInformationEx() broken under Windows 7,Linux,Windows,VirtualBox 4.3.36,2016-05-07T08:39:16Z,2016-05-07T08:39:16Z,"Hi.

So, the main issue I want to report is that GetLogicalProcessorInformationEx() basically returns garbage under Windows 7.  It's a fresh, Vanilla install of Windows 7.  The only software installed is the Windows Platform SDK.  The first record returned looks okay, but they rapidly deteriorate until after two or three you're looking at 0xCDCDCDCDCD, etc.

GetLogicalProcessorInformation(), the earlier version (no ""Ex"" on the end), also has a problem, but it seems mainly to work - the problem is that it only reports data caches.  No instruction or unified caches are reported.  Everything else seemed fine, on my one system.

Separately from VB, but related to getting this bug reported, the Oracle account creation process appears to have a number of issues.

1. The account creation page does not load if DOM storage is turned off.
2. Upon creating the account, a page is shown saying an email has been sent with instructions to activate the account.  In fact, a password reset email has been sent.
3. Upon performing the password reset, a SECOND password reset email is sent.
4. Upon performing the second reset, the account is confirmed.
5. Trying to log in does not work, at least not under Firefox - ""page is not redirectly correctly"".  However, you are in fact logged in, and so I was able to come back to this page and post this bug report.

As an aside, I spent three hours this morning trying to get VB 5.0 installed, to see if the GetLogicalProcessorInformationEx() existed there.  I was able to install 5.0 itself just fine from the VB repos, but the QT interface is not provided.  After a few hours, I concluded that although the QT package is shown via the web by Debian to be present in jessie-backports, it in fact is not present (not indeed are any of the 5.0 packages); aptitude only finds 4.3.36.  I gave up.
",Secret Private
15398,USB-devices with the same hardware-ID,Windows,Windows,VirtualBox 5.0.20,2016-05-08T07:27:26Z,2016-05-08T07:27:26Z,"All USB-devices with the same hardware-ID (VID/PID) are sent to the guest system, although only one USB-device is selected. Have been tested modems and flash drives.",VitusSumy
11938,Failed to open a session for the virtual machine (3D-related),Mac OS X,Windows,VirtualBox 4.2.16,2016-05-08T21:05:00Z,2016-05-08T21:05:00Z,"I did a search and did not see anyone post this for V4.2.16.  I am getting the following error for *every* attempt to restore a session saved by the ""Save the machine state"" action.  This is for three different Windows virtual machines, and has been happening since at least V4.2.14.  There were no problems in V4.1.18 and I didn't do an update between 4.1.18 and 4.2.14.  There never is any error information.

===8<---

Failed to open a session for the virtual machine Windows Temp.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

===8<---

I did see a post where someone first tried killing orphaned processes before trying a restore, and that did not work for me today.
",gkholman
15393,Not able to connect to USB Webcam,Linux,Windows,VirtualBox 5.0.20,2016-05-09T13:35:08Z,2016-05-09T13:35:08Z,"I am running on a Windows 10 Host. Guest is Ubuntu 14.04 LST.
I Have a Microsoft LifeCam HD-5000 webcam connected to USB 2.0

I tried to add it via settings. VB recognized the HW and I added it.

However when searching for the device with lsusb and dmesg it was nowhere to be found. 

Here is what I expected to find:
http://www.linux-hardware-guide.com/2013-05-18-microsoft-lifecam-hd-5000-hd-webcam
",Yonatan
15388,Please enable HTTPS for downloads,other,other,VirtualBox 5.0.20,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
15406,VBoxManage copyto file->file rather odd,other,other,VirtualBox 5.0.20,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
15407,VboxManage slash/backslash handling,other,other,VirtualBox 5.0.20,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
15408,Interaction between VboxManage and Node.JS,other,other,VirtualBox 5.0.20,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
12320,3D acceleration not working with Gnome Ubuntu 13.10 guest (falls back to software rendering),other,Linux,VirtualBox 4.3.2,2016-05-12T12:49:23Z,2016-05-12T12:49:23Z,"I have 64-bit Gnome Ubuntu 13.10 running in a VirtualBox 4.3.2 host (Windows 8.1 64-bit) with 4.3.2 guest additions installed by using the CD image that came with the host. Ubuntu's older guest addition packages are not installed (/usr/lib/xorg/modules/drivers/vboxvideo_drv.so is symlinked to /usr/lib/VBoxGuestAdditions/vboxvideo_drv_114.so, and /usr/lib/VBoxGuestAdditions is symlinked to /opt/VBoxGuestAdditions-4.3.2/lib/VBoxGuestAdditions).

According to Xorg.0.log (full log attached):
{{{
[    24.027] (EE) AIGLX error: vboxvideo does not export required DRI extension
[    24.028] (EE) AIGLX: reverting to software rendering
}}}

Needless to say, the guest desktop is terribly slow as a result of this. This has worked in older versions of Ubuntu (12.04 I think, with the bundled guest additions) and VirtualBox.",someguest
15413,Drag and drop only working to host not the other way,Windows,Windows,VirtualBox 5.0.20,2016-05-13T18:46:37Z,2016-05-13T18:46:37Z,"My windows 10 guest does not accept files vie drag and drop only the host does which is also a windows 10 machine.
hope somebody can help me Thx.
log files are attached",DerProGamer2000
15419,vboxguest: module verification failed: signature and/or required key missing - tainting kernel,Windows,Linux,VirtualBox 5.0.20,2016-05-15T13:33:57Z,2016-05-15T13:33:57Z,"I've found the error Message mentioned above in my syslog of an Ubuntu 16.04 X64 Server) , see below.

{{{
May 14 12:00:03 fortuna kernel: [    7.962773] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
May 14 12:00:03 fortuna kernel: [    8.354372] vboxguest: module verification failed: signature and/or required key missing - tainting kernel
May 14 12:00:03 fortuna kernel: [    8.371889] piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
May 14 12:00:03 fortuna kernel: [    8.397995] vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
May 14 12:00:03 fortuna kernel: [    8.398075] input: Unspecified device as /devices/pci0000:00/0000:00:04.0/input/input6
May 14 12:00:03 fortuna kernel: [    8.410875] vboxguest: misc device minor 55, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
May 14 12:00:03 fortuna kernel: [    8.410879] vboxguest: Successfully loaded version 5.0.20 (interface 0x00010004)
May 14 12:00:03 fortuna kernel: [    8.469950] [drm] Initialized drm 1.1.0 20060810
}}}

So on one hand an error, but on the other hand it works.
I've googled a little and found out that it has to do with Kernel Module signing.
Is there any way to fix this?

See also this thread in the Support Forum:
https://forums.virtualbox.org/viewtopic.php?f=3&t=77687",FranzS
5828,Unable to restore VM's saved state,Windows,Windows,VirtualBox 3.1.2,2016-05-18T08:10:31Z,2016-05-18T08:10:31Z,"Information duplicated from this forum post: [http://forums.virtualbox.org/viewtopic.php?f=6&t=26019&p=116632#p116632].

With 3.1.2 and snapshots taken since installing 3.1.2, I get the following when restoring from a saved state:

    00:00:06.170 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
    00:00:06.419 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)} aWarning=false, preserve=false
    00:00:06.420 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=E_FAIL (0X80004005))


When discarding saved state information, I'm able to start the machine without issue. Restored to earlier snapshot and am able to save and restore states without issue.

I'm seeing this on two different XP VMs. Have not tried to take a new snapshot of my Ubuntu VM yet, but did notice that when attempting to take a snapshot of one of my XP VMs that was powered off, the VBoxGUI crashed.",Wipeout
15430,Alias on Desktop corrupt after running,Mac OS X,all,VirtualBox 5.0.20,2016-05-18T19:48:18Z,2016-05-18T19:48:18Z,"If I ""Create Alias on Desktop"" (from the Machine Menu), a shortcut (Alias) is properly created on my desktop.  However, if I use that shortcut to start the machine (when virtual box is not already running) the shortcut may get corrupted by VirtualBox.  By that, I mean that instead of pointing to the .vbox file, it will end up pointing to the .vbox-prev file and thus can't start the VM.  Somehow the application is changing the ""original"" to the preview file.

This happens nearly ever time, but not every time and I am not sure what exactly triggers it.  I generally start the machine from a saved state, with virtual box not already running.

Virtualbox install is standard default installation.  This has existed for at least the last three or four versions.",chrijm
15415,Drag and Drop is not working bith direction,Windows,Linux,VirtualBox 5.0.20,2016-05-19T13:17:59Z,2016-05-19T13:17:59Z,"Hi,
Problem 1 - trying to drag from windows desktop any file into a CentOS guest we get a disable icon in the CentOS X11 that forbidden the drop.

Problem 2 - when trying to drag file from CentOS X11 desktop to Windows desktop the transfer start and immediately halts.

host: Win 7 64 bit
Guest: CentOS 6.7 - 64Bit

Attached host & guest logs",hanken
15434,Host only adapter is not working after host wake up,Windows,Linux,VirtualBox 5.0.20,2016-05-19T17:43:05Z,2016-05-19T17:43:05Z,"hi,

I have configured host only adapter for host-guest communication (Samba). But when host (windows 7) wakes up from sleep, host adapter stops working. I tried few things on guest and host but nothing worked. Please provide some tips...

thanks,
Sai ",Sai
15435,Custom frontends that enable OpenGL redirection and report support only for H3DOR_FMT_RGBA receive improper callbacks.,all,all,VirtualBox 5.0.20,2016-05-19T18:10:21Z,2016-05-19T18:10:21Z,"While implementing 3D redirection in my custom framebuffer I think I've discovered a bug - the H3DOR_FMT_RGBA format is not handled properly. If you look at display_vrdp.cpp:345 then if the returned strings do not match H3DOR_FMT_RGBA_TOPDOWN then successful return code is returned but the initialization functions are not called which results in my framebuffer getting a null pointer in all the instance parameters passed to the calls. I guess since the vrdp server sets both everything goes fine and only issues can be experienced with external framebuffers so this is a minor issue.


",rbundulis
15422,New Linux kernel triggers udev hang,all,Linux,VirtualBox 5.0.20,2016-05-20T03:32:02Z,2016-05-20T03:32:02Z,"Kernel: linux-image-4.5.0-0.bpo.1-686-pae

This is where it hangs:
http://s.natalian.org/2016-05-15/debug2.png

This is the strace screen capture:
http://s.natalian.org/2016-05-16/strace-usr-lib-systemd-systemd-udevd.png

Able to reproduce on Archlinux & Windows 10.",hendry
15436,Modify description of a running VM from vboxmanage,Windows,all,VirtualBox 5.0.20,2016-05-20T16:45:43Z,2016-05-20T16:45:43Z,"I want to modify VM description from vboxmanage. But it fails if VM is running at the time:
vboxmanage.exe modifyvm myVM --description ""new descr of myVM""
vboxmanage.exe: error: The machine 'att9-1034-slave-5' is already locked for a session (or being unlocked)
vboxmanage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
vboxmanage.exe: error: Context: ""LockMachine(a->session, LockType_Write)"" at line 493 of file VBoxManageModifyVM.cpp

At the same time I can change VM description via virtualbox manager GUI.

Please, fix modifyvm (or controlvm) command to make it able change VM description while its running.
",wasapl
15437,"""VBoxManage list runningvms"" does not work with the windows taskplaner",Windows,Linux,VirtualBox 5.0.20,2016-05-20T17:05:53Z,2016-05-20T17:05:53Z,"Hello, i set up my system (Windows 6.3.9600) that the guest (Ubuntu) is starting after systemstart under the permissions of the user ""VM-Helper"" If i use the command 'C:\Windows\System32\runas.exe /user:VM-Helper /savecred ""VBoxManage startvm Ubuntu --type headless""' (running in the VB dir) i can see the status in the GUI with the command 'C:\Windows\System32\runas.exe /user:""VM-Helper"" /savecred ""VirtualBox.exe""'.
But if i start the task ""%programfiles%\Oracle\VirtualBox\VBoxManage startvm Ubuntu --type headless"" (running in the VB dir) as VM-Helper the status can't be read out by VirtualBox.exe and VBoxManage.exe list runningvms"".

I was very pleased if you can reconstruct it.
The VM starts in both cases, the permissions/user are/is right (acc. to taskmanager and log). I have tried detours over batch-files ecetera...
If i want to start the VM again over the GUI as VM-Helper with a still running instance, (of course) i'll get the error ""E_FAIL (0x80004005)""",Mike446
15442,"Virtualbox doesn't refresh any window, unless you resize it. Can't use any vm at all.",Windows,Linux,VirtualBox 5.0.20,2016-05-24T16:35:03Z,2016-05-24T16:35:03Z,"After installing 5.0.18, because 5.0.20 would give a critical error while installing. I tried to load my vm into virtualbox, however, nothing in virtualbox seem to refresh, so when i click on the map to import my vm, it doesn't refresh, i have to resize the window in order to refresh. When i run the vm i get a black screen, while in the preview view of virtual box i see that it works. (using windows 10, virtualization is enabled in bios, 16gb ram, 980m GT video card, should work)",TheCodeKing
14613,raw disk access to bootcamp partition fails with 5.0.2 & 5.0.4,Mac OS X,Windows,VirtualBox 5.0.4,2016-05-25T00:50:03Z,2016-05-25T00:50:03Z,"I've had a Windows 7 guest configured for raw disk access to my bootcamp partition for a long time.  The guest works in VirtualBox 5.0.0, but it fails to start in the version 5.0.2, and 5.0.4.  I've attached the VBox.log file and contents of the pop-up error from version 5.0.4.

Reverting to 5.0.0 fixes the problem.",aschmitz
15447,Win7 BSOD if DHCP server is On for Host-Only Ethernet Adapter,Windows,other,VirtualBox 5.0.20,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
15449,No way to get DHCP-assigned IP address of natnetwork guest without guest additions,other,other,VirtualBox 5.0.20,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
15456,Wrong screen geometry reported to Linux guest for unscaled HiDPI,Mac OS X,Linux,VirtualBox 5.0.20,2016-05-29T16:26:24Z,2016-05-29T16:26:24Z,"I have a MacBook Pro 13"" retina with a resolution of 2560x1600 pixel and a physical screen size of around 286x177 mm.

When activation the ""unscaled HiDPI"" option, the full resolution of 2560x1600 px is reported to the Linux guest (debian jessie).

However, the physical screen size is reported as 677x423 mm, which gives the guest operation system no chance to correctly estimate the DPI resolution.

More over, the reported screen size is not reduced by MacOSX's Menu bar in seamless mode, so the bottom menus inside the linux guest are misplaced below the effective screen area.

I already use guest additions 5.0.21-r107220, because of the cursor displacement issue fixed in this snapshot version compared to the 5.0.20 release of the Linux Guest Additions.",Wolfgang Glas
15457,Uninstall does not remove all network registry entries,other,all,VirtualBox 5.0.20,2016-05-29T19:05:23Z,2016-05-29T19:05:23Z,"When uninstalling Virtual box (see ticket 15404 for why), the registry entries for the network drivers are not removed.  As a result, re-installation doesn't work correctly.  On a clean system, install and uninstall and diff the registry.  ",Curt
15460,Windows 10 VB Error Drag N Drop Not Working N Others More,Windows,Linux,VirtualBox 5.0.20,2016-05-30T13:00:20Z,2016-05-30T13:00:20Z,"I Been Using Virtualbox for a long time, and now because of the venom shitty shit. it broke

Problems that i most have is DRAG AND DROP not working on linux and windows
I Install the Extension and my ZorinOS Broken not working anymore not booting properly. on windows 7 it work fine but i cant drag and drop back then i can i forgot the version but drag and drop is working back then, i use linux.
please fix this problem thanks man.",DogSHlT
15465,User Interface shows up on wrong screen,Linux,Windows,VirtualBox 5.0.20,2016-05-31T12:59:28Z,2016-05-31T12:59:28Z,"I have a configuration with 3 displays. Display 1 shows the ubuntu desktop, display 2 and 3 are running the virtual machine with windows 7. On startup i get a messagebox from virtualbox that one of my serial ports could not be opened (this is another bug). When this happens, usually the GUI in Fullscreen mode is not on the lower side of the displays but somewhere on the first display. When I switch between fullscreen and windowed mode and vice versa everything is ok after that.",audia3
15318,seamless mode does not work after upgrade to VirtualBox 5.0.18 Oracle VM Guest Additions on Ubuntu Guest,Windows,Linux,VirtualBox 5.0.18,2016-05-31T15:40:04Z,2016-05-31T15:40:04Z,"Host ist Win10-64bit and guest is Ubuntu 15.10. The task bar is about 2cm deeper than normal. Staying at the guest additions from xxxx16 works.

Any idea?",beststevie
15468,drag and drop not bidirectional,Windows,Linux,VirtualBox 5.0.20,2016-05-31T16:24:29Z,2016-05-31T16:24:29Z,"Hi, I have a Windows 10 Host, with a Ubuntu 15.10 guest, Virtual Box and Guest addition latest version. When I drag and drop files from guest to host no problem, when I do it from host to guest my files go only in /tmp/VirtualBox dropped files and not where I dropped them.
I attached log files, hope it helps.
Thanks",rok
15470,"VB GUI elements are missing, Windows 10",Windows,all,VirtualBox 5.0.20,2016-06-01T04:38:22Z,2016-06-01T04:38:22Z,"As described in the title, I have an issue with the VirtualBox GUI itself in which the dropdown menu is not showing correctly and looks like it's not responding.

My configuration is like this :
1. OS : Windows 10 Home x64
2. CPU : Core i7-5700HQ
3. GPU : Intel Hd Graphics 5600 + GTX960M
4. Screen resolution : 1920x1080
5. DirectX version : 12

You can see the details in these pictures below :
[[Image(http://s33.postimg.org/6sedk6c33/image.png)]]
[[Image(http://s33.postimg.org/lykfb423z/image.png)]]
[[Image(http://s33.postimg.org/ada93egmn/image.png)]]

After the bug happens, if I close VirtualBox it will remain in task manager as shown in this picture :
[[Image(http://s33.postimg.org/ubq45s1bj/image.png)]]

And if I start another VirtualBox, the GUI itself will be not displayed but a new VirtualBox process appears :
[[Image(http://s33.postimg.org/o88jlvb1r/image.png)]]

If I try to create a new VM, I couln't do that because a lot of GUI elements are missing and I can't setup the guest memory size, guest hard disk, etc

I've tried with older version of VB through 5.0.4 and they have exactly same problem in my setup

If you need more data, please let me know.

Thanks!",iede
15473,When started any virtual machine - VirtualBox crashes and pulls the machine down,Windows,other,VirtualBox 5.0.20,2016-06-02T07:12:49Z,2016-06-02T07:12:49Z,When started any virtual machine - VirtualBox crashes and pulls the machine down,terrybrn
13922,Cant install openvpn when virtualbox is installed. Windows10 x64 build9926,Windows,all,VirtualBox 4.3.24,2016-06-03T14:50:06Z,2016-06-03T14:50:06Z,"Hi, on windows 10 i cant install openvpn only when virtual box is already insalled. It stuck on tap-installer. Without virtualbox install goes fine.",bullet92
15475,Auto updater for system without a repository,all,all,VirtualBox 5.0.20,2016-06-03T19:24:56Z,2016-06-03T19:24:56Z,"An auto update system for VirtualBox would be awesome. Maybe using the integrated downloader (that for now seems quite pointless) as VMWare does, at least in Windows and OS X as there is no repository system and users always has to download and update manually. 
At least download the new version and launch the installer...",QcFe
15486,Cannot start VirtualBox.exe or VBoxSDL.exe because of ntdll.dll error.,Windows,other,VirtualBox 5.0.20,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
15487,Running Linux guest caused udisksd to fail host mounts,Linux,Linux,VirtualBox 5.0.20,2016-06-07T15:30:18Z,2016-06-07T15:30:18Z,"Running a Linux guest (freshly installed Mageia 5) to help gather data for a Mageia 5 bug report dealing with installation.  Left the VM running overnight, and this morning was trying to mount some HDs, only to see /var/log/messages such as this:

Jun  7 10:17:39 prf kernel: EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf systemd[1]: Unit mnt-hd.mount entered failed state.

The mount command on the host appeared to work (no error reported on konsole).

Shut down the guest and host mounts started working again with no other interaction...
Restarting guest to see if this is repeatable...  [not yet]

Looks like I will have to leave guest running for a while to see if this repeats.

",Pierre Fortin
15480,VirtualBox on Linux does not pass ausio when connected using localhost VRDP,Linux,Windows,VirtualBox 5.0.20,2016-06-08T16:55:54Z,2016-06-08T16:55:54Z,"I have a headless Windows 10 VM running on VirtualBox 5.0.20 on an Arch Linux host. 

I make connections to the VM using FreeRDP and Remmina.

When making connections to localhost:<port> (on which I have configured for the headless access), I do '''not''' get any audio.

However, when I connect directly to the VM using RDP (port 3389) and set the audio to ""Local"", I get it loud and clear.

To be sure that this is not a VRDP artifact, I cloned the VM and ran it on a VirtualBox instance on a Windows Host. On Windows, I am ale to access the sound both ways.

There is a wontfix (https://www.virtualbox.org/ticket/10923). However, I think that the issues are slightly different. This case is specifically about a different way in which the VRDP has been implemented in Windows and Linux.




1.2.0-rcgit.11 (git n/a)
When connecting ",Sachin Garg
15491,opengl change of brightness not possible,Windows,Windows,VirtualBox 5.0.20,2016-06-10T07:38:45Z,2016-06-10T07:38:45Z,"We have Quake 3 Demo install on our windows 7 x64 guest. The 3d acceleration is enabled. The screen is too dark and changing the brightness in display settings of game is not working.
The host machine is windows 7 x64 too.",trivalik
15499,seamless mode works only on laptop screen,Linux,Windows,VirtualBox 5.0.20,2016-06-10T17:40:19Z,2016-06-10T17:40:19Z,"I have found that using seamless mode in Fedora and Ubuntu will result in the screen going seamless on the laptop's display only. I have three screens - the laptop screen and two external monitors (via a docking station) in that order:
    laptop screen <--> lcd panel 1 <--> lcd panel 2

I have set my ""middle"" monitor (lcd panel 1) to be the main window however no matter what I do I've not found a way to go seamless and have the seamless display on the monitor of my choosing.

An interesting note is that the desktop manager ""cinnamon"" - DOES work properly. I can move the non-seamless window to whichever screen I choose, use HOST+l to go seamless and it'll be seamless on the monitor that the non-maximized guest OS was on. (this does have some interesting quirks too but it works > 90% of the time pefectly)

It's been a bug for as long as I've used virtualbox (a long time) and I've seen the bug all through the later 4.x and now in the 5.x product.

",dovholuk
15467,Upgrade to Windows 10 fails,Linux,Windows,VirtualBox 5.0.20,2016-06-12T12:21:25Z,2016-06-12T12:21:25Z,"The upgrade from Windows 7 (64 Bit) to Windows 10  with the upgrade tool 'GWX' isn't possible.
Please see attached screenshot.

BS: Ubuntu 16.04 64 Bit",Josef Latt
15502,Regression: Support for middle mouse button (3rd button),Windows,Windows,VirtualBox 5.0.20,2016-06-12T16:44:48Z,2016-06-12T16:44:48Z,"Hello,

I have a 5 button + scroll wheel mouse (Evoluent VerticalMouse 4 USB) and I want to use the middle (3rd) mouse button or scrollwheel as doubleclick in my guest system. Before VirtualBox 5.0 (versions 4.3.x) that was no problem and the middle mouse button was detected.
I use the 3rd party software ""X-Mouse Button Control"" (highrez.co.uk/downloads/XMouseButtonControl.htm) to assign mouse buttons to functions, but in VirtualBox 5.0.x the middle mouse button is only detected as left mouse button. Same goes for the scroll wheel.

The USB filter for the mouse does not work either, besides this is not an option for me because I want to use the mouse in the host and guest system.
Is there a solution?

VirtualBox 5.0.20 r106931 with installed Extension Pack
Host: Windows 7 SP1 64Bit
Guest: Windows 7 SP1 64Bit, also tried with Windows XP SP3 32Bit",Sundowner
14904,Not possible to create Host Only network,Windows,Windows,VirtualBox 5.0.10,2016-06-17T07:23:29Z,2016-06-17T07:23:29Z,"when click on add new receive this error :
Querying NetCfgInstanceId failed (0x00000000).

Result Code: 
E_FAIL (0x80004005)
Component: 
HostNetworkInterfaceWrap
Interface: 
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

This happens on windows 10 build Version 10.0.10586 Build 10586

Without this, cant use 3rd party software like Genymotion (dont launch enymore)",Sergi
3974,OS/2 guest is limited to 1024x768x16777216 resolution,Windows,other,VirtualBox 2.2.2,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
15520,vbox/src/VBox/Devices/Network/slirp/resolv_conf_parser.c:476: bad test ?,other,other,VirtualBox 5.0.22,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
15123,Bluescreen when starting Beckhoff TwinCAT PLC with activated VT-x,Windows,Windows,VirtualBox 5.0.14,2016-06-18T13:39:06Z,2016-06-18T13:39:06Z,"With the VBox Version 5.0.10 and 5.0.14 the Windows 7 crashes with a bluescreen when the Beckhoff TwinCAT PLC 3.1 is started.
This happens on a 32 Bit Windows as Long as the VT-x Support is activated and allways on a 64 Bit Windows, because the VT-x Support coulkdn't be swithed off.
With VBox 5.0.4 the System doesn't Crash.",OTonn
14441,USB devices with a same name hang any further operation,all,all,VirtualBox 5.0.2,2016-06-20T06:32:55Z,2016-06-20T06:32:55Z,If you try to connect any USB devices that have same product or manufacturer ID it will cause a hang to any further operations with any usb devices.,EAX
15535,Host files with (illegal) colon in filename not visible in shared folder,Windows,Linux,VirtualBox 5.0.22,2016-06-20T09:53:47Z,2016-06-20T09:53:47Z,In Windows files are created (through CygWin) having a (illegal) colon in their name. I added this folder as Shared Folder in Virtualbox. All subdirs are visible (not having a colon) but none of the files with the colon are. When the colon is removed from the filename they become visible.,CornePlas
15540,Can't run Unity Editor due to openGL errors,Windows,Linux,VirtualBox 5.0.22,2016-06-22T10:24:09Z,2016-06-22T10:24:09Z,"Not possible to run linux Unity Editor if 3D acceleration is enabled.

Starting Unity Editor fails with following error message in the log:

OpenGL Warning: glXChooseVisual: ignoring attribute 0x22
OpenGL Warning: glXChooseVisual: bad attrib=0x186a1, ignoring
OpenGL Warning: glXChooseVisual: bad attrib=0x186a0, ignoring
No valid fbconfig found
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000000000000
OpenGL Warning: glXChooseFBConfig returning NULL, due to attrib=0x2, next=0x20
[0621/173105:ERROR:gl_surface_glx.cc(613)] glXChooseFBConfig failed.

This is Unity Editor 5.3.5f1 (http://download.unity3d.com/download_unity/linux/unity-editor-5.3.5f1+20160525_amd64.deb) running under Ubuntu 16.04.",elmir
14236,Qt5 developed app not displaying correctly in Linux Cinnamon desktop guest,Windows,Linux,VirtualBox 4.3.28,2016-06-22T10:27:20Z,2016-06-22T10:27:20Z,"Qt5 developed app doesn't display correctly using Cinnamon desktop in VirtualBox

I have an app I've developed in Qt 5.3.1 that doesn't display data in output text boxes when using the Linux Cinnamon desktop in VirtualBox with 3D acceleration enabled in the display settings for the virtual machine. 

It does this when using the Cinnamon desktop in any Linux Distro (I've tried Cinnamon with Linux Mint, Ubuntu and Debian). The regular Unity desktop in Ubuntu and the Xfce desktops in both Linux Mint and Debian have no problem. Just Cinnamon. 

I don't know if this is a Cinnamon, VirtualBox or Qt problem. Months ago I registered a bug with the Cinnamon folks but I never saw a fix, or that the problem was replicated anywhere. If I disable 3D acceleration for any of the Cinnamon virtual machines in VirtualBox the problem doesn't happen.

I'm posting here because maybe some Qt developers have seen similar problems with Cinnamon in either VirtualBox, or a native Linux machine.

The app is called Lottery Analyzer Expert QL: it can be downloaded at http://tcesoftware.webs.com, follow the link to Linux Downloads. 

It's free. My main versions are Windows, but I have both a 32 bit and 64 bit version for Linux developed in Qt 5.3.1. I hope the link I posted is OK. It's a free application, though not open source (because of the nature of the subject). 

It does various analyses on the Powerball and Mega Millions lottery games. I developed the programs out of curiosity of how to do it, and offering them for free for all the very useful free software I've used over the years. 

Again, I hope posting the link is OK. I just want someone to try my program and see if they can replicate the problem in any environment. 

Just double click on either Lottery_32 (32 bit) or Lottery_64 (64 bit) in the folder created by downloading and unzipping the tar.gz. Then choose one of the analyze buttons or ""drawn"" buttons after entering the number of draws to sort. If it runs correctly data will fill the text boxes for the game chosen to sort the totals of. The problem will show if the text boxes are empty except for the last row.

Any comments or replies would be welcome. Thanks in advance for any.",te7
15543,install path environment var not set,Windows,other,VirtualBox 5.0.22,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
15545,Popup menu does not appear,Linux,Windows,VirtualBox 5.0.22,2016-06-23T16:03:22Z,2016-06-23T16:03:22Z,Popup menu in virtual machine does not appear. I have set various settings but it does not resolve problem,Destructor
15165,"Leaving Full-Screen Mode resizes guest with ""Auto-resize Guest Display"" off",Windows,Windows,VirtualBox 5.0.14,2016-06-24T15:15:27Z,2016-06-24T15:15:27Z,"In older versions (when Auto-resize Guest Display could be toggled with Host+G), this worked fine, but when this shortcut toggle was removed, this bug was introduced.

To reproduce:

1. Leave full-screen mode if necessary.
2. Enable ""Auto-resize Guest Display"".
3. Guest resolution should change to match window.  If not, resize the window.
4. Enter full-screen mode (Host+F).
5. Guest resolution should change to match host resolution.
6. Use Host+Home to disable ""Auto-resize Guest Display"".
7. Exit full-screen mode (Host+F).
8. Notice that the guest resolution changes to match the window, but it should not.
",Marc
15507,"Add warning/export to Media manager ""Remove"" for encrypted disks",all,all,VirtualBox 5.0.20,2016-06-26T05:13:34Z,2016-06-26T05:13:34Z,"I found, as reported here: https://forums.virtualbox.org/viewtopic.php?f=1&t=78137&p=364039#p364039 that when an encrypted disk is removed from the Media Manager, the encryption keys in the guest's .vbox file are deleted without warning.

There are legitimate reasons why a person might need to remove a disk from the Media Manager and re-attach it to a guest. One reason that I have experienced is one may find that multiple virtual disks on a single host drive may eventually result in host-drive bandwidth limitations which could be resolved by moving one of the guest's virtual disks to another host drive. This requires completely removing the disk from Virtualbox so the path can be changed and re-registering the drive with the guest.

If one is encrypting one's drives, at present such a solution would result in a dead drive, with no warning and no recovery, unless one had backed up the .vbox file. And even if one had backed up the .vbox, there seems to be no way that I've seen to get the encryption keys back into the original .vbox without shutting down all Virtualbox processes and manually editing the keys back in. 

I would suggest a warning popup in the Media Manager when one clicks Remove on an encrypted drive, saying that removing an encrypted drive will result in removal of the encryption keys for that drive from the .vbox definition file. The popup could provide an opportunity to export the keys to a user-defined file. 

Also, in the Add a Disk wizard when one chooses an existing disk to add to a guest, there could be a choice to mark the added drive as encrypted and import the keys from the user's file.

Thirdly, since the encryption keys are so essential, there could be a new button in the Media Manager, active when an encrypted disk is selected, to export the keys for backup purposes.

None of these exporting/importing functions would compromise security, since the keys are readable in any XML-aware text editor, and the secret password is also needed to use the disk.

Thanks for taking a look at this!",scottgus1bug
15550,Cannot access to USB device in host VM when installed USB redirection SW,all,all,VirtualBox 5.0.20,2016-06-27T07:50:53Z,2016-06-27T07:50:53Z,"When I have installed specific software for USB device redirection (eg. Eltima - Flexihub or Incentives Pro - USB Redirector) on my Windows 7 (or Windows 10) host, I cannot access to any usb device on the guest (Windows XP or Windows 7). 

The only way to have USB working inside the guest is uninstall the software.

I found on the forum the same problem occurred to another user:
https://forums.virtualbox.org/viewtopic.php?f=6&t=74487

I also tried to install VB version 5.0.22 but the problem persists.

The steps for replicate the problem are:
1) Install Flexihub or USB Redirector
2) Run a VM
3) Try to connect an usb device

Error occurred:
USB device 'Kingston DataTraveler G3' with UUID {4b7d935e-b532-4f63-b48c-167b75cbb8c8} is busy with a previous request. Please try again later.
Exit code: E_INVALIDARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Caller: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}



",oscarB
15555,[Feature Request] More Video Memory,Windows,Windows,VirtualBox 5.0.24,2016-06-28T22:00:05Z,2016-06-28T22:00:05Z,"Modern graphics cards have 6GB+ video memory, please allow us to use more than 256mb for VMs.",Stanzilla
15556,Windows 10 consistent video freeze,Windows,Windows,VirtualBox 5.0.24,2016-06-29T10:49:43Z,2016-06-29T10:49:43Z,"Running on Windows 10 guest on a Windows 10 host with VB 5.0.24, updated extensions on the guest.

Under load, the video freezes requiring the VM to be restarted.
This happens constantly and makes the VMs unusable.

Tried to run VM with debug but the console command doesn't show any console.
Attaching the relevant vbox.log.",EPinci
9688,Private host network problem => Fixed in SVN,Windows,Linux,VirtualBox 4.1.4,2016-07-01T09:26:13Z,2016-07-01T09:26:13Z,"Since I have pass to the last version 4.1.4 I have a problem :

The Private host network function for the partage in network don't work.

This functionnaly don't work since i have restart the computer.

I use Windows 7 and a VM with ubuntu 10.10.

I have solve my problem with re-install the version 4.0.12.

Sorry for my english.

Regards.",alex57
15562,Imperfect string matching when VBox suggests machine type by its name,Windows,all,VirtualBox 5.0.24,2016-07-01T10:45:34Z,2016-07-01T10:45:34Z,"Hi guys,

Looks like there is a small problem with how VBox decides on the type of OS by the name of a new virtual machine.

I entered ''Ubuntu 16.04 (restored)'' as a name for the new VM and noticed that after typing ''restored'' the version of the machine changed from ''Ubuntu'' to ''Red hat''. It seems like the regexp matcher considers ''red'' in ''restored'' as a hint while it should not. The solution is rather simple - not to consider the keywords as hints if the words do not start with them.

Another name I just tried is ''Ubuntu twin''. As in the first case, the suggested type of the OS changes from ''Ubuntu'' to ''Windows'' just after typing ''n'' in ''twin''.",kachkaev
15564,"NO RESPONSE from Escape, Backspace, and other keys with VirtualBox on Windows 10 host",Windows,Windows,VirtualBox 5.0.22,2016-07-03T22:07:40Z,2016-07-03T22:07:40Z,"I created a Windows XP-SP3 32-bit guest (extension pack installed) running under VirtualBox 5.0.22 on a 64-bit Windows 10 host.  Everything seemed to work perfectly, except some keys such as backspace and escape, among a few others, exhibited no response.  If I VNC'd into the VM, however, those keys worked fine.  I copied the VM's VDI file onto a 64-bit Windows 7 desktop also running VirtualBox 5.0.22, and all keys worked perfectly.  As such, it seems this may be another issue revolving around Windows 10.  Host and guest were all set to standard U.S. English Keyboard, so this is not an internationalization issue.
",qd01a
15563,VirtualBox Guest Additions 5.0.24 cannot Auto-resize Guest Display,other,Linux,VirtualBox 5.0.24,2016-07-04T07:51:57Z,2016-07-04T07:51:57Z,"VirtualBox Guest Additions 5.0.24 successfully installed in Oracle Linux 6.8 guest, but it cannot auto-resize the guest display when auto-resize option turned on.",Rodery
15570,VBoxManage showvminfo fails to find machines,Linux,all,VirtualBox 5.0.24,2016-07-04T23:16:24Z,2016-07-04T23:16:24Z,"Created VM ""W7"", then: 

# VBoxManage showvminfo W7
VBoxManage: error: Could not find a registered machine named 'W7'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())"" at line 2719 of file VBoxManageInfo.cpp

Added more VMs and problem persists.",Pierre Fortin
15097,VBoxHeadless Crashes OSX El Captain on Host Suspend,Mac OS X,Linux,VirtualBox 5.0.14,2016-07-06T16:37:25Z,2016-07-06T16:37:25Z,"
",jwaldrip
14363,The Instruction at 0x... referenced memory at 0x... The memory could not be read,Windows,all,VirtualBox 5.0.0,2016-07-06T17:58:43Z,2016-07-06T17:58:43Z,"As of version 4.3.16 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""

This is just an update of Ticket #13580 because I cannot update its version number to 5.0.0.",Frank Breitling
15590,"Windows guest hangs with AHCI port resets, cannot close VirtualBox instance",Windows,Windows,VirtualBox 5.0.20,2016-07-10T14:52:46Z,2016-07-10T14:52:46Z,"Hello,

Recently I encountered a Windows guest that hung itself and would not allow me to stop it when right-clicking the VM->Close->Power off. I am running it in headless mode and I saw the vBoxHeadless.exe process on the host was reporting a constant CPU usage value but was not changing, indicating the process was hung.

There are 6 other guests running on this host, all of which did not hang and continued operating properly.

The guest had been booted at 6/30/16 01:31 and some logging software of mine stopped receiving a ping from the guest around 7/9/16 13:30 (232:57 in logfile). I did not attempt to intervene until 20 hours later (252:29 in logfile). It looks like when the guest host process hung the AHCI controller experienced an issue with port resets.

The host is running Windows Server 2008 R2, the guest is running the same.

The VBox.log file is attached.",lbgaus
15559,Win-XP fails to start in normal/last-working-breakpoint 9 of 10 times,Linux,Windows,VirtualBox 5.0.22,2016-07-10T18:30:25Z,2016-07-10T18:30:25Z,"Initiating Windows XP SP3 fails consistently before or during ""Welcome"" Screen. The VM works using all safe modes. (Terminal, GUI, GUI with Network). The VM (WIN XP reports: (see attachment) intelppm.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

On the rare occasion that the VM Win XP boots up, it runs normally, and then shuts down via the O/S shutdown command as expected. 

 ",winthrom
15591,Windows 10 and Host Only Networking,other,other,VirtualBox 5.0.24,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
15548,PC speaker passthrough uses frequency tone from previous call,other,other,VirtualBox 5.0.22,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
15592,"Upgrade from 5.0.8 to 5.0.24 causes ""FATAL: no bootable disk found""",Windows,Windows,VirtualBox 5.0.24,2016-07-10T22:39:59Z,2016-07-10T22:39:59Z,"In a Windows 7 64bit host, running a guest Windows Standard 2012 virtual machine would not boot with ""no bootable disk found"" error.  Reverted back to 5.0.16, and started working again.  Noticed Storage changed on 5.0.24 from SATA to IDE, suspect this is the cause of the ""no bootable disk found"" error, but did not confirm.",Lula
15376,"Keyboard key sticks in ""down"" state, cannot be cleared",other,other,VirtualBox 5.0.20,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
15593,Fail to save machine state,Linux,Windows,VirtualBox 5.0.24,2016-07-11T18:48:59Z,2016-07-11T18:48:59Z,"Hi,

Every time I try to save the machine state I get an error. This has happened through several VirtualBox versions.

The error is: 
Result Code: 
NS_ERROR_FAILURE (0x80004005)

My host is Ubuntu 14.04 LTS and my guest is Windows XP sp3

Thanks
",mau17
15377,Delayed handling of mouse button,other,other,VirtualBox 5.0.20,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
15595,RDP sends scroll wheel events to wrong monitor,Windows,Linux,VirtualBox 5.0.24,2016-07-12T16:10:46Z,2016-07-12T16:10:46Z,"Using the RDP with a dual head display mouse scroll wheel events are being sent to the wrong monitor.  When the mouse is on the second monitor, scroll wheel events are sent as if they were on the first monitor which causes a focus change and other bad behaviour.

xev running on the console shows the events correctly as coming from the second display (coordinates 2593,264):


{{{
ButtonRelease event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 684071, (2,107), root:(2593,264),
    state 0x1000, button 5, same_screen YES

}}}

But when using RDP the same events are received as if they are on the first head, instead of the second display:


{{{
ButtonPress event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 796041, (75,120), root:(97,283),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 796041, (75,120), root:(97,283),
    state 0x1000, button 5, same_screen YES

}}}

The mouse was at 97,283 on the second display, which should have been sent as 2657,283sip.

This problem does not occur with VNC, but is present in 5.0.24 as well as the 5.1 beta and does not seem to depend on window manager or host extension version.

As an additional confusing point, if there is any mouse motion at the same time as the scroll wheel event then the events are sent at the correct coordinates on the second head.",thudson
15506,Feature request: compression,other,all,,2016-07-13T18:30:47Z,2016-07-13T18:30:47Z,"Just as encryption was introduced, it would be nice to have compression as well.
Benefits:
- saves storage space, especially on VMs living on an SSD
- saves data when downloading pre-built appliances
- increases the entropy for the encryption operation

Info:
I tried to use Windows's built-in transparent compression on a Windows 7 guest: the space got shrinked from over 30GB to 16GB.",Lieutenant
15605,Full screen bug,Windows,Linux,VirtualBox 5.0.20,2016-07-13T19:10:47Z,2016-07-13T19:10:47Z,"I know there are 2 tickets for this problmen, but still it's an annoying bug. I can't use full screen mode, either I can't uninstall virtual box. 

When I try to unintall it the wizard came up, then it asks that would I install an another software. No mather what I chose it ends in the same way. The files stayed untouched but I still can run the software.",Zoltanka
15534,VBoxManage hostonlyif ipconfig vboxnet1 --dhcp leads to error,Linux,Linux,VirtualBox 5.0.22,2016-07-13T19:51:07Z,2016-07-13T19:51:07Z,"Host type: Debian jessie amd64

Trying to configure vboxnet1 to use dhcp after creating it leads to the following error:

{{{
VBoxManage: error: Code NS_ERROR_NOT_IMPLEMENTED (0x80004001) - Not implemented (extended info not available)
VBoxManage: error: Context: ""EnableDynamicIPConfig()"" at line 210 of file VBoxManageHostonly.cpp 
}}}

Steps to reproduce:
* create hostonlyif with ''VBoxManage hostonlyif create''
* call ''VBoxManage hostonlyif ipconfig vboxnet1 --dhcp''  (replace vboxnet1 by the name you get from V''BoxManage list hostonlyifs'' after creating it.

Using the VBoxNetworkName: ( HostInterfaceNetworking-vboxnet1 ) instead of vboxnet1 did not change anything.

",manschenk
15547,Virtualbox destroy encrypted discs when delete online snapshots,Linux,Linux,VirtualBox 5.0.22,2016-07-14T17:25:07Z,2016-07-14T17:25:07Z,"I tested this on several servers, and the results are 100% reproducible.

I found 3 ways to destroy the encrypted discs:

First:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Remove the snapshot with VM turned on.
 4. Restart the VM
=> The discs are destroyed and the S.O can't start.

Second:
 1. Encrypt the discs of an VM 
 2. Take a offline snapshot
 3. Start the VM
 4. Remove the snapshot with VM turned on.
 5. Restart the VM
=> The discs are destroyed and the S.O can't start.

Third:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Pause the VM
 4. Remove the snapshot with VM paused.
 5. Resume the VM
 6. Restart VM
=> The discs are destroyed and the S.O can't start.

I was tried to find a way to make a automatic backup of an encrypted VM, without need the save the key on the backup script to start vm again, and hard crash the discs off the VM.

The log of the VM on the first case as attached, and a screenshot of it after the restart.

It was tested with the last 5.0.22 VirtualBox Release and I dont found other tickts about this defect.

Thanks for you guys that develop this great program.  ",Law
14075,"Windows VM crashes Debian host, NMI for unknown reason points to ""vboxdrv""",Linux,Windows,VirtualBox 4.3.26,2016-07-15T13:38:24Z,2016-07-15T13:38:24Z,"The first time the crash occurred was about a month ago, the host was running Debian 6 and latest (at that time) !VirtualBox. Since then, host was wiped and Debian 7 was installed with latest !VirtualBox 4.3.26. A crash occurred again recently and so I started investigating.

Crashes seem random. Windows VM was the only VM on the host at the time of the second crash, it was just applying Windows updates. Reverting to a previous copy of VM and reapplying the same Windows updates again did not cause the crash again. Nothing appears in the logs at the time of a crash (both Linux and !VirtualBox logs).

The suspect lines extracted from `dmesg`:
{{{
[50414.144741] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
[50415.090400] EXT4-fs (md0): Unaligned AIO/DIO on inode 4194333 by AioMgr0-N; performance will be poor.
...
[63477.985050] Uhhuh. NMI received for unknown reason 31 on CPU 4.
[63477.985073] Do you have a strange power saving mode enabled?
[63477.985094] Dazed and confused, but trying to continue
[68728.724996] Uhhuh. NMI received for unknown reason 21 on CPU 7.
[68728.725021] Do you have a strange power saving mode enabled?
}}}

To trace NMI for unknown reason, I have enabled crash dump using ""kdump"", set ""kernel.unknown_nmi_panic=1"" and ""kernel.panic_on_unrecovered_nmi=1"" in ""/etc/sysctl.conf"", and let VM run with HeavyLoad from JAM Software (CPU, memory, file writes and disk access). This crash is now reproducible but it could take anywhere from 1 hour to 1 day of running a VM for a crash to occur.

Call trace from crash dump points to ""vboxdrv"":
{{{
[76034.059602] Uhhuh. NMI received for unknown reason 31 on CPU 3.
[76034.059686] Do you have a strange power saving mode enabled?
[76034.059766] Kernel panic - not syncing: NMI: Not continuing
[76034.059846] Pid: 19036, comm: EMT-4 Tainted: G           O 3.2.0-4-amd64 #1 Debian 3.2.65-1+deb7u2
[76034.059937] Call Trace:
[76034.060006]  <NMI>  [<ffffffff8134a53c>] ? panic+0x95/0x1a2
[76034.060157]  [<ffffffff81352056>] ? do_nmi+0x151/0x258
[76034.060235]  [<ffffffff813517a0>] ? nmi+0x20/0x30
[76034.060312]  <<EOE>>  [<ffffffffa03f97c6>] ? rtR0MemAllocEx+0x17e/0x1de [vboxdrv]
[76034.060470]  [<ffffffffa03f05a3>] ? supdrvIOCtlFast+0x75/0x79 [vboxdrv]
[76034.060555]  [<ffffffffa03ed2a9>] ? VBoxDrvLinuxIOCtl_4_3_26+0x43/0x1eb [vboxdrv]
[76034.060645]  [<ffffffff811087dd>] ? do_vfs_ioctl+0x459/0x49a
[76034.060728]  [<ffffffff81039aa2>] ? finish_task_switch+0x4e/0xb9
[76034.060809]  [<ffffffff8134fb09>] ? __schedule+0x5f9/0x610
[76034.060892]  [<ffffffff81108869>] ? sys_ioctl+0x4b/0x72
[76034.060970]  [<ffffffff81355f92>] ? system_call_fastpath+0x16/0x1b
}}}

Tested RAM with MemTest86 for days, no problems found. High CPU usage from Interrupts is observed inside the VM as described in Ticket #10611, it might be relevant.

Summary of host specs:
* BIOS: VT-x and VT-d enabled, HT disabled
* Motherboard: Intel Server Board S5520HCT
* CPU: 2 x Intel Xeon E5620, 2.4GHz, 8 cores in total
* RAM: 12 x 4GB (DDR3 1333MHz ECC Unbuffered)
* HD: 2 x 600GB WD VelociRaptor 10Krpm

VM configuration:
* OS: Windows 7 SP1 (with latest updates)
* vCPU: 4-7 (it seems the higher the number the higher the chances of a crash occurring sooner)
* vRAM: 8GB

Attached are various logs, crash analyses and hardware info.",Denis Kozlov
15631,Virtual machine list accessibility issues,Windows,all,VirtualBox 5.1.0,2016-07-17T19:42:30Z,2016-07-17T19:42:30Z,"When navigating in the vm list with NVDA, it's not read as every other list, it's not read at all, or some other controls are read. It's not as critical, but it's a nuisance when you have more vms.",tyrylu
15587,lock to a specific window size,all,all,VirtualBox 5.0.24,2016-07-19T06:35:36Z,2016-07-19T06:35:36Z,"Sometimes I have a VirtualBox guest at the resolution I want and I accidentally resize it. It's very annoying because I need the specific resolution I've set. I would like it if you could make a ""lock resolution"" so that if I accidentally try to change the size of the window it won't change, and the next time I start the VM it remembers and uses the locked size without changing.
",quiettime
15641,mouse capture mode problem when scrolling out of window,other,Windows,VirtualBox 5.1.0,2016-07-19T09:46:40Z,2016-07-19T09:46:40Z,"It'a windows 7 in vbox hosted in my windows 7 in native mode.
I've enabled mouse auto capture mode, I dont have to press ctrl-f to release it.
I have 2 monitors, One is for my virtualbox, in 1 monitor mode.
I use eclipse, notepadd, whatever.
I press the mouse button, to select text, and go out of the vbox monitor window.
when I release, the virtualbox begins to be irresponsive, I cannot select some text anymore with the mouse, I have to restart the vbox in reboot mode or keep the state, and when it's restarted the problem has disappeared.",stephane martin
15640,Existing CPU is not supported?,Windows,Windows,VirtualBox 5.0.26,2016-07-19T18:35:12Z,2016-07-19T18:35:12Z,"I tried to update one of my guess Win 7 to Win 10 and it failed saying it was an unsupported cpu (xeon e5405).

Thing is, Win10 upgrade thinks the CPU is fine on the host computer witch is the same CPU (see screen shoots supplied in zip file with logs)",isgdre
15620,Windows 10 guest freeze on startup (Linux x64 host),Linux,Windows,VirtualBox 5.1.0,2016-07-20T05:35:14Z,2016-07-20T05:35:14Z,"I upgraded my VirtualBox installation from Version 5.0.24 to Version 5.1.0. When starting my Windows 10 VM it freezes on startup when the Windows logo with the rotating dots beneath it is shown. The operating system of the host is openSUSE Tumbleweed. I've attached the logfile of the VM if you need more informations i'll try to provide them...

kind regards,

Christoph",happenpappen
15647,VirtualBox 5.1: Ugly icons on non-HiDPI external monitor on OS X,Mac OS X,other,VirtualBox 5.1.0,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_
15341,Unexpected closure of guest when clicking menubar item in fullscreen,Windows,Linux,VirtualBox 5.0.18,2016-07-20T07:52:16Z,2016-07-20T07:52:16Z,"About half the time when I click a menu bar item expecting it to open the menu, it closes the guest without any warnings whatsoever.  That is VERY bad.  The typical time I've noticed, I was either trying to open the View menu or the Devices menu.

In many ways, this is a crash--even if vBox thinks it was told to close.  I was unsure of which component to chose.  Someone may need to correct it.

The only guest/host combination this was noted with was Linux for the guest and Windows for the host.  However, I expect this to affect all guests.",Will Pittenger
15655,KDE Active Screen Edge Actions of host are not disabled when running a guest OS in full screen mode,Linux,other,VirtualBox 5.1.0,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
15656,"mouse disappears in virtualbox, linux installation menu",Windows,Linux,VirtualBox 5.1.0,2016-07-21T15:48:18Z,2016-07-21T15:48:18Z,"First of all, Sorry for my bad English!

my mouse disappears in virtualbox, to be exact in the linux installation menu. I can't choose any of the option system. I mean I can't choose ""Install, or anything"" I've a laptop, I tried to use USB mouse, but it didn't work. I used the insert guest additions, and turned off/on the 3D acceleration. both isn't working. I changed my Pointing device, from USB Multi-Touch tablet to USB Tablet. 

Can anyone help me please? What should I do?",Hisham
15657,File drag from linux host to windows vm when filename has colon causes error,other,other,VirtualBox 5.1.0,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
15663,Windows 10 BSDO in VirtualBox 5.1,Linux,Windows,VirtualBox 5.1.0,2016-07-22T09:10:35Z,2016-07-22T09:10:35Z,"I have tried several times to install Windows 10 x64 in VirtualBox 5.1 on a host Lenovo x61 laptop running Fedora 24 x64. The installation of Windows 10 crashes with a Sad Face and Blue screen. I have tried with Windows 10 1511 and Windows 10 1511_2 DVDs. I also tried windows 8.1 and this also failed with a BSOD. The only installation which finished successfully was of windows 7 SP1.

thanks for your products and keep up the good work",dino.conti
15676,Cannot open guest in full screen mode when autostart is enabled on any VM,Mac OS X,all,VirtualBox 5.1.2,2016-07-24T14:17:53Z,2016-07-24T14:17:53Z,"I have multiple guest VMs of varying operating systems.  Right now, I have two that I use continuously:

* Headless FreeBSD 10-3 (--autostart-enabled=on; --autostart-delay=30)
* Windows 10 Pro x64 (--autostart-enabled=off)

If I boot my OS X host, the FreeBSD VM launches with no problems.  However, when I manually launch my Windows 10 VM and attempt to bring it '''full screen''' (2560x1440) it fails and only gives me a partial full screen (2560x1324).  

If I '''turn off autostart''' {{{ VBoxManage modifyvm $vmname --autostart-enabled=off }}} the problem goes away completely.  Full screen, on the Windows 10 VM works properly with no issues.  I have attempted to change the '''delay''' value from 10 seconds to 5 minutes to see if the running VM was causing the problem.  Regardless of the delay, when {{{ --autostart=on }}},  full screen fails.

This happens on '''all guests.'''  In fact, full screen fails that the Virtual Box splash screen prior to the booting of the OS.  Even if no OS is loaded, I was able to reproduce the full screen failure, so I have ruled out a guest additions issue.  

I am running OS X 10.11.6 and VBox 5.0.26r108824, but this has been happening since Mavericks 10.9.x and every version of VB since 5.0 release.  All upgrades of OS x has been via format of the drive and restoration of data only.  VM's are not backed up using Time Machine, rather they are exported/imported as appliances.

",DigitalBoffin
15404,Windows 10 - Failed to create the host-only adapter,Windows,Linux,VirtualBox 5.0.20,2016-07-26T15:19:29Z,2016-07-26T15:19:29Z,"When I'm trying to run my VM using vagrant I'm getting following error:

{{{
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""hostonlyif"", ""create""]

Stderr: 0%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}

System information:
- VirtualBox 5.0.21r107152
- Vagrant 1.8.1
- Windows 10 Enterprise Insider Preview, Build 14342.rs1_release.160506-1708


",josin
15697,Linux Additions should still be able to read network config without D-Bus,other,Linux,VirtualBox 4.3.36,2016-07-27T12:58:48Z,2016-07-27T12:58:48Z,"Currently lines 1472-1478 of /src/VBox/Additions/common/VBoxService/VBoxServiceVMInfo.cpp look like this:

rc = vgsvcVMInfoWriteUsers();
if (RT_FAILURE(rc))
    break;
	
rc = vgsvcVMInfoWriteNetwork();
if (RT_FAILURE(rc))
    break;

This unfortunately means that '''if vgsvcVMInfoWriteUsers() fails due to a missing system D-Bus, no network info is exposed as guest properties. There is no reason for this'''.

'''Suggestion:''' simply continue with vgsvcVMInfoWriteNetwork() even if vgsvcVMInfoWriteUsers() fails

This affects all currently supported VirtualBox versions.
",AxelFontaine
15710,Full screen tool bar does not work properly on Linux hosts,Linux,all,VirtualBox 5.1.2,2016-07-29T09:37:58Z,2016-07-29T09:37:58Z,"In full screen, the bottom tool bar does not appear as quick as it does before 5.1 when mouse approaches bottom of screen, and no hover effects when mouse hovering on the buttons.

When click a button on the tool bar for the first time, it will work as usual. However, after that, these buttons become decorations. The virtual machine is normal, but the only ways to quit it is to either let itself power off, or use shortcut to minimize all windows.",FiveYellowMice
15712,Mouse Integration and USB 3.0 Controller Problem,Windows,Windows,VirtualBox 5.0.26,2016-07-29T12:54:09Z,2016-07-29T12:54:09Z,"Using a Windows 7 64 bit guest and setting USB 3.0 controller.

When running the guest the mouse integration is greyed out and clicking in the guest screen requires to re-capture the mouse, when this is done the mouse pointer will not traverse the whole of the guest screen, making it impossible to use the desktop fully.

I have attached the correct log file this time.
",Solrac42
15410,USB driver issue,other,other,VirtualBox 5.0.20,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
15715,Shared Clipboard not working with Windows 10,Linux,Windows,VirtualBox 5.1.2,2016-07-30T15:09:07Z,2016-07-30T15:09:07Z,"I have VirtalBox 5.1.2 with a Windows 10 guest. 

After updating (in the guest) the Guest Additions to version 5.1.2 the shared clipboard isn't working anymore. If I re-install the Guest Additions 5.0.26 the shared clipboard works. 

So I assume it's a problem in the Guest Additions. (With the Guest Additions 5.1.0 the clipboard isn't working either.)

Specs:

Host: openSUSE 13.2 (64-Bit), VirtualBox 5.1.2

Guest: Windows 10 (version 1511, 64 Bit)",tischuer
15727,Add HiDPI Support for macOS guests,Mac OS X,OSX Server,VirtualBox 5.1.2,2016-08-02T20:49:40Z,2016-08-02T20:49:40Z,"When running VirtualBox on a MacBook Pro Retina, the Chrome of VirtualBox (Window Frames and the Icons at the Bottom of the Window) are rendered in HiDPI just fine, but the macOS Guest doesn't run in HiDPI mode.",Lars Sonchocky-Helldorf
15729,keyboard differences in VB 5.1,Linux,Linux,VirtualBox 5.1.2,2016-08-03T07:36:49Z,2016-08-03T07:36:49Z,"VB 5.1.2 r108956 on 64-bit Ubuntu 16.04, running 64-bit Ubuntu 16.04 guest with the guest additions.

Something has changed in the way keyboard handling works in VB 5.1.  Two problems that I'm guessing may be related:

'''#1)'''
In the past, the extra ""multimedia"" buttons on my USB keyboard (including the ""calculator"" button) have always worked.  They used to be handled by the host, even when the guest had focus.  In VB 5.1, those buttons don't work anymore when the guest has focus.

'''#2)'''
The other more serious keyboard change in VB 5.1 is that ALT+TAB is no longer always caught by the guest.  Instead of going between the apps in the guest, ALT+TAB is handled by the host, even when the guest has focus.  This doesn't happen 100% of the time.",Stéphane Charette
15328,usb mouse does not work after migrating to 5.0.18,Windows,Linux,VirtualBox 5.0.18,2016-08-03T09:47:26Z,2016-08-03T09:47:26Z,"if I setup guest 5.0.18 addons in linux guest , mouse seems available but no cursor is displayed.
if I remove completely guest kernel modules addons, mouse is working.
if I setup 5.0.16 guest addons and run 5.0.18 host , the mouse does not work , graphic system runs badly.


",sancelot
15736,Crash in crPackExpandDrawElements () from /usr/lib64/VBoxOGLpackspu.so,Windows,Linux,VirtualBox 5.0.24,2016-08-03T11:54:32Z,2016-08-03T11:54:32Z,"1.) Install Qt Creator 4.0.1 under Linux x64[[BR]]
2.) When you start it, it immediately crashes.

Workaround: disable 3D acceleration in Creator with ""qtcreator -noload Welcome -noload QmlDesigner"".

Backtrace:
{{{
#0  0x00007fffd06f2dc8 in crPackExpandDrawElements () from /usr/lib64/VBoxOGLpackspu.so
#1  0x00007fffd05773b5 in ?? () from /usr/lib64/VBoxOGLpackspu.so
#2  0x00007fffe30c7520 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib64/libQt5Quick.so.5
#3  0x00007fffe30c8ccd in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib64/libQt5Quick.so.5
#4  0x00007fffe30cf264 in QSGBatchRenderer::Renderer::render() () from /usr/lib64/libQt5Quick.so.5
#5  0x00007fffe30daa92 in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib64/libQt5Quick.so.5
#6  0x00007fffe30db127 in QSGRenderer::renderScene(unsigned int) () from /usr/lib64/libQt5Quick.so.5
#7  0x00007fffe30e977e in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib64/libQt5Quick.so.5
#8  0x00007fffe3131529 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib64/libQt5Quick.so.5
#9  0x00007fffe321298b in QQuickRenderControl::render() () from /usr/lib64/libQt5Quick.so.5
#10 0x00007fffd6180267 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5
#11 0x00007fffd61803a5 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5
#12 0x00007ffff6821cb4 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#13 0x00007ffff713ee9b in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#14 0x00007ffff70fbb6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#15 0x00007ffff7102af0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007ffff67f8795 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#17 0x00007ffff684694e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#18 0x00007ffff6846d01 in ?? () from /usr/lib64/libQt5Core.so.5
#19 0x00007ffff2e8ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007ffff2e8bc48 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007ffff2e8bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007ffff684702c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#23 0x00007ffff67f6a6b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#24 0x00007ffff78c263f in Utils::SynchronousProcess::run (this=this@entry=0x7fffffffc720, binary=..., args=...) at synchronousprocess.cpp:403
#25 0x00007fffdfd2fc88 in CMakeProjectManager::CMakeTool::run (this=this@entry=0x118e790, arg=...) at cmaketool.cpp:112
#26 0x00007fffdfd2ffc1 in CMakeProjectManager::CMakeTool::supportedGenerators (this=this@entry=0x118e790) at cmaketool.cpp:136
#27 0x00007fffdfd3d5e4 in CMakeProjectManager::CMakeGeneratorKitInformation::fix (this=0xd77f20, k=0x1449ae0) at cmakekitinformation.cpp:248
#28 0x00007fffe922bab7 in ProjectExplorer::KitManager::addKit (this=this@entry=0x9dfc30, k=0x1449ae0) at kitmanager.cpp:518
#29 0x00007fffe922f1e9 in ProjectExplorer::KitManager::restoreKits (this=0x9dfc30) at kitmanager.cpp:204
#30 0x00007fffe91cfff2 in ProjectExplorer::ProjectExplorerPlugin::delayedInitialize (this=<optimized out>) at projectexplorer.cpp:1518
#31 0x00007ffff7bbe6fa in ExtensionSystem::Internal::PluginSpecPrivate::delayedInitialize (this=0x6baa40) at pluginspec.cpp:1025
#32 0x00007ffff7bbb025 in ExtensionSystem::Internal::PluginManagerPrivate::nextDelayedInitialize (this=0x66e6e0) at pluginmanager.cpp:830
#33 0x00007ffff68207d5 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#34 0x00007ffff682dda2 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5
#35 0x00007ffff6821cb4 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#36 0x00007ffff70fbb6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#37 0x00007ffff7102af0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#38 0x00007ffff67f8795 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#39 0x00007ffff684694e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#40 0x00007ffff6846d01 in ?? () from /usr/lib64/libQt5Core.so.5
#41 0x00007ffff2e8ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#43 0x00007ffff2e8bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#44 0x00007ffff684702c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#45 0x00007ffff67f6a6b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#46 0x00007ffff67fe866 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#47 0x000000000040a0d9 in main (argc=1, argv=<optimized out>) at main.cpp:527

}}}
",bmn
15750,Distorted display on / after pausing / taking / restoring snapshot,Mac OS X,Windows,VirtualBox 5.1.2,2016-08-05T21:40:09Z,2016-08-05T21:40:09Z,"Host: VirtualBox 5.1.2 on Mac OS X 10.11.3

Guest: Windows 7 32-bit

When pausing a VM, taking a snapshot or restoring a snapshot the display is distorted. The only way to clear the display is to click the affected areas and / or resize a window to be full screen.

This problem did not occur with VirtualBox 5.1.0. This only seems to affect my Windows 7 32-bit VM, a Windows 10 64-bit VM is unaffected.",Nathan Pardoe
15762,Warning message is not visible and blocks guest interaction,Mac OS X,Windows,VirtualBox 5.1.2,2016-08-08T11:54:52Z,2016-08-08T11:54:52Z,Due to #15659 virtual box is showing an audio warning on starting up a VM. If the VM is not the focused window when this warning is displayed the warning is not visible and all input to the guest is blocked. The only way I've found to show the warning is by pausing the guest.,alanbirtles
15766,Windows 10 - Black Screen After Logic,other,other,VirtualBox 5.1.2,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
15767,"Keyboard capture often escapes to host when using the ""Windows"" key (Windows host, Linux guest)",Windows,Linux,VirtualBox 5.1.2,2016-08-08T19:02:54Z,2016-08-08T19:02:54Z,"I'm not quite sure when this started happening, but it happens to me a lot now (VBox 5.1.2).

My guest VM uses xmonad, and I set it so that using Win-1, Win-2, Win-3, switches desktops. Many times, when I am keyboard-captured, and I start switching desktops, one of them will suddenly escape and do stuff in my Windows host...

How to reproduce:
- Run a Linux guest, Windows host.
- Set it so that your keyboard is captured in the guest.
- Start mashing the Windows key with any other key, like 1, 2, 3, Left.

Effect:
- Within a few seconds of mashing, your host's Windows menu will pop-up.

I tested it with three different keyboards and two different machines.",Ptival
15670,Shared folder is not mounted at VM start,Windows,Windows,VirtualBox 5.1.2,2016-08-09T07:12:10Z,2016-08-09T07:12:10Z,"Under Windows 2000, shared folders are not automatically mounted at system start whereas it was the case with virtualbox 5.0.24. Manual mapping is required.",PBT78
15755,Windows 7 64bit Host - VirtualBox 5.1.2 r108956 The network operation failed,Windows,Linux,VirtualBox 5.1.2,2016-08-10T07:31:53Z,2016-08-10T07:31:53Z,"Dear community,
VirtualBox 5.1.2 r108956 failed with Windows 7 64bit Host and Ubuntu as Guest.
As reported for other versions of VirtualBox, ""The network operation failed with the following error: During network request: Connection refused"". I followed all recommendations suggested for older versions of virtualbox but any of them fixed the problem.
Because the network is failing I do not have access to internet when I'm using ubuntu, and it is critical for accessing some of my documents/data.
Let me know if I need to report something else, and how I can report them.
Thanks,
Peris",Peris_D
15756,Virtual USB Drive information,other,other,VirtualBox 5.1.2,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
15746,At times when virtualizing a windows OS explorer not updating view,other,other,VirtualBox 5.1.2,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
15742,Problem with Full Screen Mode Guest windows 10  PRO 64B Update 2 1511,other,other,VirtualBox 5.1.2,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
15645,3D broken on Solaris 10,Solaris,other,VirtualBox 5.1.0,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
15635,VirtualBox Manager 5.1.0 r108711 ignores system font on XFCE 14.04,Linux,all,VirtualBox 5.1.0,2016-08-10T10:59:21Z,2016-08-10T10:59:21Z,"Host system - Linux XFCE 14.04 LTS
VirtualBox Manager 5.1.0 r108711

Problem VirtualBox Manager uses some font, but not the system.

To reproduce, change system fort to Verdana for instance and start VirtualBox Manager. Font in VirtualBox Manager will be different.

Other application doesn't have this problem.

Thank you.
",macachuto
15552,attaching differencing vhd on host makes it unusable on guest,Windows,Windows,VirtualBox 5.0.22,2016-08-10T12:28:37Z,2016-08-10T12:28:37Z,"When you attach a differencing VHD on Windows host using diskpart or mmc, there's a chance that VBox will no longer understand the format of that VHD. If guest booted, it will see a corrupted filesystem.

I attach my VHD file on Windows 7 host. It's virtual size is 50G and it has one partition formatted to NTFS. I created a dummy VM in VBox GUI to manage snapshots. Currently, the chain consists of 4 image files. 

I didn't boot the guest until now. When I did, guest chkdsk spew tons of errors. Then I stopped the guest and attached the VHD on host again. chkdsk showed no errors.

I went further and restored the 'good' backup (there's a backup of all the .vhd and .vbox files I made before the guest boot). Marked the volume as readonly using diskpart and compared the contents of the block device using cygwin. They're indeed different!

",lfmeloman
15448,Second monitor disappears,Windows,Windows,VirtualBox 5.0.20,2016-08-10T14:41:35Z,2016-08-10T14:41:35Z,"I believe this has been raised as a ticket before and has been closed but I still have an issue with this. I run a windows 10 pro 64-bit guest on a windows 10 Home 64-bit host. Often, at least twice in an 8 hour work day, when I minimize the second monitor it disappears from the host taskbar, leaving only the one virtualbox instance for the primary screen on the host taskbar. The second monitor is restored when I hit ctrl + F twice to take virtual box out of full screen and then put it back in full screen mode.",collusion
14594,Trying to create Windows 10 VB from Parallels 10 Win.hdd,Mac OS X,Windows,VirtualBox 5.0.4,2016-08-10T17:44:31Z,2016-08-10T17:44:31Z,"I just installed latest version of VB on my mac (5.0.4) and did try to import existing hdd file from parallels 10
When I select :Use existing virtual disk file"" And select Win10 copied from Parallels 10 HDD package I get following error. My Host is 10.11 El Capitan GM (15A282a)

The medium '/Users/rob/Documents/Win10.hdd' can't be used as the requested device type.


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: 
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Callee RC: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
",oxoocoffee
15777,Resolution issues across 2 versions and the test build,Linux,Windows,VirtualBox 5.1.2,2016-08-10T19:14:41Z,2016-08-10T19:14:41Z,"On version 5.1.2 of virtualbox and even the testbuild even with guest additions installed and after running vboxmanage controlvm win2008server setvideomodehint 1366 768 60 it will not change the window size beyond this [[Image(https://imgur.com/TuTE05B)]]. If I try seamless mode it just shows a black screen with the vbox controls at the bottom and the same thing happens with the fullscreen mode. The only mode it doesn't do that in is the regular one that's too tiny for me to use or in scaled mode. On version 5.0.24 I can use the VM in regular mode fine but it also has the same issues on seamless mode and fullscreen. 

Specs: slackware 14.2 64bit 
i5-2430M processor
intel integrated graphics (sandybridge/hd 3000)
8gb ram

guest OS: windows 2008 server",MachinaeWolf
15690,Error trying to run,other,other,VirtualBox 5.1.2,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
15709,mouse does not work anymore when newer VB starts a VM,Windows,Windows,VirtualBox 5.1.2,2016-08-11T13:50:02Z,2016-08-11T13:50:02Z,"mouse is frozen when newer VirtualBox (5.024, 5,026, 5.1.2) starts a VM with 4.3.32 everything is fine.
I use a mircosoft touch mouse with.",xdk
15781,VirtualBox 5.1.2 - VBoxGuest.sys BSOD (Win 7 Pro),Mac OS X,Windows,VirtualBox 5.1.2,2016-08-11T17:13:56Z,2016-08-11T17:13:56Z,"Every hour or so VirtualBox 5.1.2 r108956 freezes with a BSOD and VBoxGuest.sys a the bottom, and reboots.",brianjester
15783,VBoxManage: error: Error starting guest session (current status is: starting),Linux,Windows,VirtualBox 5.1.2,2016-08-12T09:32:41Z,2016-08-12T09:32:41Z,"After upgrade from 5.0.26 to 5.1.2 we can not use our automated run sequences controlled by several VBoxManage guestcontrol <vm> run commands, because some of them are returned with the error message:

VBoxManage: error: Error starting guest session (current status is: starting)

This seems to occur not at the first launch of a guestcontrol command after starting the VM, but at one of the following. For example one of such sequence is:

{{{
> VBoxManage snapshot ${VM} restore ""${RestoreSnapshot}""
> VBoxManage  sharedfolder add ${VM} --name RunExecution --hostpath ${HostRunExecutionDirectory}/${BID} --automount
> VBoxManage startvm ""${VM}""  --type headless
> VBoxManage guestproperty get ""${VM}"" ""/VirtualBox/GuestInfo/Net/0/V4/IP""
> VBoxManage controlvm ""${VM}"" setvideomodehint 1920 1080 32
> VBoxManage guestcontrol ${VM} run --username ${VmUser} --password ${VmPassword} --wait-stdout -- \
  ""c:\windows\system32\xcopy.exe"" ""${RunExecutionDirectory}\\runtime-uitest"" ""C:\\runtime-uitest\\"" /r /y /s /i
('''failed''') > VBoxManage guestcontrol ${VM} run --no-wait-stdout --no-wait-stderr \
  --username ${VmUser} --password ${VmPassword} -- ""C:\Windows\system32\cmd.exe"" /c \
  ""${RunExecutionDrive} & cd ${RunExecutionDirectory} & ${RunExecutable} /param:dummy=dummy ""
}}}

Host: 
openSUSE 13.2 Linux r06268 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
VirtualBox-5.1-5.1.2_108956_openSUSE132-1.x86_64
Oracle_VM_VirtualBox_Extension_Pack-5.1.2-108956.vbox-extpack


Guests: 
Windows 7 Professional SP1 64 Bit
Windows Server 2012 R2 Standard
Oracle VM VirtualBox Guest Additions 5.1.2

Until solved we downgrade to 5.0.26.

",rklehm
15784,Video Mixing Renderer 9 (VMR) DirectShow graph building issue,Windows,Windows,VirtualBox 5.1.2,2016-08-12T12:34:03Z,2016-08-12T12:34:03Z,"I've been experimenting with DirectShow video playback in Windows guests (XP, Vista, 7 and 8.1) using GraphStudioNext, and I stumbled on a issue that might be cause by the VirtualBox additions display driver. (The host PC is running Windows 10 x64 and has a Nvidia Geforce GTX 750 Ti graphics card).

If you start GraphStudioNext and drag a video on to it will by default create a graph with the VMR7 and hit play then it will play fine. If you remove the VMR7 filter and then go to Graph -> Insert Video Renderer, you can try out the various other video renderers.

All of these work fine (Video Renderer, VMR7, EVR) except VMR9, which fails to build the graph, reporting a cannot connect pins error. This error is not normal and doesn't occur on non-virtualized versions of Windows.",QuantumSquirrel
7492,Need a progress indicator during Snapshot creation,Windows,Linux,VirtualBox 3.2.8,2016-08-12T12:39:25Z,2016-08-12T12:39:25Z,"For a large VM with 5GB RAM, I tried making a snapshot of a live VM. The snapshot did not finish before 10 minutes and I could not wait any longer, so I canceled the snapshot (breaking my VM, see separate bug report http://www.virtualbox.org/ticket/6877).

I had no way of knowing when the snapshot would finish. Maybe it would have taken another few seconds... I don't know.

A progress indicator for snapshot making would be very helpful.
",BobO
15788,"Cannot resize guest window, auto-resize and seamless mode are greyed out [GuestAddition is installed]",Linux,Windows,VirtualBox 5.1.2,2016-08-13T18:02:26Z,2016-08-13T18:02:26Z,"Host: Fedora 24, Guest: Win8.1
After installing guest OS, and installing GuestAdditions, I am unable to resize guest window.
It's size is fixed, 1024x768. In the View menu intem Seamless mode and Auto resize guest display are both disabled (greyed out).
Earlier everything was fine on my machine, it worked as it expected. But one day it went wrong. I uninstall and reinstall VBox, but the issue is still present. Then I made a clean Fedora 24 install on this machine, but the issue is still present. I've remove my GPU and used my motherboard integrated GPU but the issue is still present. In this machine I am unable to use VBox, because it's screen is too small, and unable to resize.",VChris
3972,OS/2 guest cannot write to floppy disk,Windows,other,VirtualBox 2.2.2,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
5582,"Suggestion: allow disk image data to be aligned in VDI files, for optimal use with SSDs",other,other,VirtualBox 3.0.12,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
15793,Unable to change order of inaccessible VMs in list,Linux,all,VirtualBox 5.1.2,2016-08-15T05:43:56Z,2016-08-15T05:43:56Z,"Lubuntu 16.04 x86-64 host.

The VirtualBox Manager GUI shows a list of available VMs on the left side. You can drag-and-drop VMs to change the order of the list.

However VMs which are shown as Inaccessible can't be moved.

Also, with an inaccessible VM at the top of the list, I couldn't manage to drag another (accessible) VM above it.",Donuts
15794,Can't install ReactOS,Windows,other,VirtualBox 5.1.2,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
15796,Which guest is my vbox duplicating?,all,all,,2016-08-15T12:09:53Z,2016-08-15T12:09:53Z,"When registering a guest via opening the .vbox file, a warning pops up if the new guest has the same UUID as a present guest.:

It may be helpful if the box also mentioned which guest already has that UUID.",scottgus1bug
11277,CPU Hotplug prevents change in vCPU number,all,all,VirtualBox 4.2.4,2016-08-16T10:04:45Z,2016-08-16T10:04:45Z,"After setting up a VM with more than one vCPU and CPU hotplug off, then activating the CPU hotplug feature, it is not possible to reduce the amount of vCPU as long as hotplug is enabled.[[BR]]

Steps to reproduce :[[BR]]
1. Create a VM with 2 or more CPUs
2. Enable CPU hotplug via vboxmanage
3. Start the VM then stop the VM
4. Reduce the amount of CPUs using vboxmanage modifyvm VM --cpus x
5. This will fail with the following code :
{{{
NS_ERROR_INVALID_ARG (0x80070057) There is still a CPU attached to socket x.Detach the CPU before removing the socket.
}}}
The only way to make this work is to disable the hotplug feature before setting the amount of vCPU.

IMO this error shouldn't popup as the VM is a PowerOff state and therefore hotunplugging a CPU doesn't make sense...",Max D
15572,Fedora 24 Kernel 4.3.6-300 Breaks VB 5.0.24 on Mac OS X 11.5,Mac OS X,other,VirtualBox 5.0.24,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
15761,Upgrade to 5.1.2 destroyed all VM,Mac OS X,all,VirtualBox 5.1.2,2016-08-17T08:44:02Z,2016-08-17T08:44:02Z,"After upgrading from version 5.0.24, 5.0.26 and 5.1.0 directly to 5.1.2 destroyed all my virtual machines on three independent Macintosh systems after the first start up, using version 5.1.2 of VirtualBox.

As I was able to see, what's going on, an error with the chipset was displayed with an error message, that the virtual machine was damaged or Could behave like having technical trouble, while there is an issue within the audio codec/ chipset/ driver.

Microsoft Windows VM (7 Ultimate and 10 Pro, both 64-bit) crashed at first and displayed the sad smily. Then the Ubuntu Server, Linux Mint and a FreeNAS crashed after additional reboot. One Windows VM restarted again and again - while the guest addition image was mounted. After ejecting it, a blue screen appeared at the next boot loop.

I've tried to downgrade the version or use the virtual machines on another computer, where no update has been done, but the machines was destroyed, we weren't able to recover it. For sure we've used snapshots before upgrading, but a roll back to the last working snapshot was not successful.

Fortunately, we keep all important data outside the virtual machines, so we only lost the virtual systems, but that was very annoying.

And it doesn't matter, what you change in the virtual machines configuration, the same error messages appears, only with your changed configuration of chipset and audio codec.

We've tried to identify some logs, but what we found is not useful.

May be you can take a look of your structure and another one knows this issue too and can give further informations, why and when his happens exactly.

We've also tried a fresh install of MacOS X (10.10.5 and 10.11.6) with a newly downloaded 5.1.2 of VirtualBox and by creating a new VM, the issue persists even out of the box.

The last working versions of VirtualBox are 5.0.26 and 5.1.0 - so the issue must be directly located in the code of version 5.1.2

May be, you can find the bug and fix it, because we wanna upgrade securely to the next version.",TH3rb5t
11290,DirectDraw clipping/refresh bug with XP guest,Linux,Windows,VirtualBox 4.2.2,2016-08-17T10:20:58Z,2016-08-17T10:20:58Z,"I'm using VirtualBox 4.2.2. Lubuntu 11.10 x86-64 host, Windows XP Pro SP3 guest.

This issue happens with Guest Additions versions 4.1.14 and 4.2.2. It shows up with the WinUAE Amiga emulator.

When WinUAE is using DirectDraw for its graphics output, dragging the window partly off-screen causes the image to appear near the upper left of the screen. See the attached screenshots. The problem does not happen when WinUAE is set to use Direct3D.

To demonstrate:
- Download an example program, e.g. ftp://ftp.amigascne.org/pub/amiga/Groups/D/DOC/DOC-NoName
- Download the WinUAE installer from http://www.winuae.net/ and run it.
- Run WinUAE. When the setting window opens click Miscellaneous in the treeview. Set Graphics API to DirectDraw.
- Click Floppy drives and then the ""..."" button near the top right of the window. Choose the program you just downloaded.
- Click Start to start the emulation. In a few seconds you should see something in the emulation window.
- Press the middle mouse button to un-capture the mouse and drag the emulation window so it is partly off-screen. Notice that the window contents appear at the top left of the desktop, and the actual emulation window no longer updates.
",Donuts
15744,Version 5.1.2 Machine Wrap Error,Windows,all,VirtualBox 5.1.2,2016-08-17T11:09:08Z,2016-08-17T11:09:08Z,"I am currently using version 5.0.26, I have tried upgrading to version 5.1.2 but it never starts, I always get a ""Machine Wrap"" error.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
",Solrac42
15809,Virtual machine not runing,Linux,other,VirtualBox 5.1.2,2016-08-17T13:23:46Z,2016-08-17T13:23:46Z,(removed pasted VBox.log content),SerhiiNI
15811,Mini toolbar hides itself after you click on a menu header,Linux,all,VirtualBox 5.1.4,2016-08-17T13:43:40Z,2016-08-17T13:43:40Z,"Lubuntu 16.04 x86-64 host. This issue seems to apply to all guest OSes.

I have configured guest VMs to show the mini toolbar at the top of the screen when in full-screen mode. If you mouse over the hidden toolbar it appears. On clicking a menu header, the menu appears but the toolbar then hides itself after a second or two. I think the toolbar should remain shown until either the user selects a menu item or clicks away from the menu.",Donuts
11947,High I/O on SharedFolders hangs system,Linux,other,VirtualBox 4.2.16,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
15812,Human Interface devices are not detected by the Virtual machine,Windows,Windows,VirtualBox 5.1.4,2016-08-17T16:53:34Z,2016-08-17T16:53:34Z,"When I connect a Human interface device to my Windows 7 PC it is detected.  When I try to connect it to my Virtual Box machine, it is not detected.  An error appears when I try to pick in the Device menu - Unknown device.
It used to work when the USB settings were set to 2.0 on VB version 5.0.24
I have attached 2 images.
One from my working Win7 PC and one from the Win7 VB that does not work.",skh
15658,[OS X] VM Dock icon should not bounce while saving/restoring state,Mac OS X,all,VirtualBox 5.1.0,2016-08-18T07:40:41Z,2016-08-18T07:40:41Z,"While VM state is being saved/restored VM GUI window displays a progress bar in a popup pane. This coincides with the VM icon in Dock bouncing. Progress bar is not something users need to be notified about, so icon should not bounce.

See the OS X HIG: ""Use bouncing to notify users of serious information that requires their attention. A bouncing Dock icon is very noticeable, so you should use this method only when the user really needs to know about something. Also, make sure you disable bouncing as soon as the user has addressed the problem.""

https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/Dock.html#//apple_ref/doc/uid/20000957-CH60-SW1
",dottedmag
15819,Videos doesn't work,Windows,Linux,VirtualBox 5.1.4,2016-08-18T13:16:42Z,2016-08-18T13:16:42Z,"Videos using players(SMPLAY), and video from internet aren't working on VB 5.1.4 and his guest additions.
Sometimes video on internet is running without audio.",Matipare
15818,Windows 10 guest VM has shared folder hang,other,Windows,VirtualBox 5.1.4,2016-08-18T14:56:33Z,2016-08-18T14:56:33Z,"
== The Issue ==

On using Visual Studio 2013 on my Windows 10 VM to build a project located on a VirtualBox shared folder, Visual Studio will hang during some file I/O operation such as scanning files for intellisense or compiling the C++ source files. Once it is hanging, I cannot access the shared folder via the Windows file explorer which suggests something has failed in the shared folder file operation(s), and the Visual Studio process cannot be terminated. Indeed, even shutting down the VM hangs on the shutdown screen and I must manually force a VM power off. Interestingly or not, copying the entire project folder from the shared folder to the guest C: drive worked without any issues, and then subsequent build operations from the C: drive work fine without any hanging.

This problem appears to have started happening since version 5.1.x. It was happening after I initially upgraded to 5.1.2 but then seemed to sort itself out, but since upgrading to 5.1.4 it is happening constantly (or maybe I'm just being lucky / unlucky depending on timings).

There doesn't appear to be anything in the VM host syslog related to disk I/O at the time that the VM shared folder access hangs but VM startup does produce the following in the syslog:

{{{
Aug 18 11:21:35 centurion kernel: [69073.711857] vboxdrv: ffffffffc0121020 VMMR0.r0
Aug 18 11:21:35 centurion kernel: [69073.783744] vboxdrv: ffffffffc0220020 VBoxDDR0.r0
Aug 18 11:21:35 centurion kernel: [69074.056132] vboxdrv: ffffffffc023f020 VBoxEhciR0.r0
}}}

The VM log (attached) doesn't appear to me to have anything in there related to the shared folder hang. Is there any more verbose logging that can be enabled for the VM?

== About the VirtualBox setup ==

I'm running a Windows 10 (64bit) guest on Linux Mint 17.3 (64bit) host running Linux Kernel 3.19.0-32. The Windows 10 VM is run using a raw disk vmdk file which points to an SSD. The VirtualBox Guest Additions are up-to-date with the version of VirtualBox (5.1.4).",neilc34
15813,Windows Guest crashes when opening keyboard settings on Mac Host,Mac OS X,Windows,VirtualBox 5.1.4,2016-08-18T15:54:17Z,2016-08-18T15:54:17Z,"Host: Mac OS X 10.11.6 -  MacBook Pro (Retina, 15-inch, Late 2013)
Guest: Windows 7 64-bit
VirtualBox version: 5.1.4 r110228 (Qt5.5.1)

When opening the Keyboard --> Keyboard Settings menu item the Guest immediately crashes.  I have observed this in 5.1.2, 5.1.3 as well.  I am new VirtualBox user so I can't confirm this wasn't also present in older versions.

I have attached a snippet of the VirtualBox Log from Guest Startup to crash when opening the menu item.  It doesn't look terribly helpful.",brianthesmith
15492,Some apps not displaying correctly,Windows,Linux,VirtualBox 5.0.20,2016-08-18T15:54:26Z,2016-08-18T15:54:26Z,"Hi,

I've just upgraded my Linux Mint host to lastest, and had to re-install the guest additions ( from reading around this probably implies there was a kernel update... ).

However some apps aren't being displayed at all correctly, e.g. Visual Studio Code which just displays as a load of dark grey blocks.
Also the login screen displays small rather than full screen ( but works ).

With some trial and error I've discovered that guest additions 5.0.16 is the last which doesn't show this problem, but 5.0.18 and 5.0.20 both do.",Barrie
15821,sata disk not seen at guest install,Mac OS X,Windows,VirtualBox 5.1.4,2016-08-18T16:05:44Z,2016-08-18T16:05:44Z,"Trying to create windoww 7 64bit guest on macbook air.  Virtualbox 5.1.4.  Using pxe boot.  error reads:

FAILURE (5456): Unable to Determine Destination Disk, Partition and/or Drive.

This is with SATA enabled.  if i switch to sas, ide, or scsi, i can run the install without a problem.  Worked in vbox 5.0.n without problems.

",ascott
15830,virtualbox 5.1.4 on debian 8 crashed while plugging/unplugging usb phone in flashing mode,Linux,Windows,VirtualBox 5.1.4,2016-08-19T20:11:58Z,2016-08-19T20:11:58Z,"my virtualbox Version 5.1.4 r110228 (Qt5.3.2)
 on debian 8 crashed while plugging/unplugging usb phone in flashing mode. Here is the log:


",tim43263246
15834,Mouse Integration on OS/2 - eCS causes double pointer after guest addition upgrade.,Mac OS X,other,VirtualBox 5.1.4,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
15836,Windows 10 Start button causes taskbar to disappear in Seamless Mode,Windows,Windows,VirtualBox 5.1.4,2016-08-20T16:32:42Z,2016-08-20T16:32:42Z,"I have just installed VBox 5.1.4 Windows 10 64 bit Host, Windows 10 64 bit guest.

Prior to the latest update seamless mode did not work at all with Windows 10 guests as reported by others.
https://forums.virtualbox.org/viewtopic.php?f=2&t=78179

After installing 5.1.4 seamless mode appears to work in that entering seamless mode the taskbar appears as expected and the bottom of the screen, and open windows, or windows opened from the taskbar appear to behave properly.

However left clicking on the start button to open the start menu causes the taskbar to disappear, although the user interface bar remains visible. The start menu appears in the preview window of the Virtual Box manager, but not on the desktop. Closing the start menu (insert Ctrl-Alt-Del and start task manager) causes the taskbar to reappear. 

The same behaviour occurs in a 32bit Windows 10 guest. Host Display is 1920x1200

VBox and VBoxHardening Logs attached.  ",wisty
15842,Error with VBoxManage internalcommands createrawvmdk on SAS 4K block size drive.,Linux,Linux,VirtualBox 5.1.4,2016-08-21T22:16:56Z,2016-08-21T22:16:56Z,"  - The host (and guests) are under Ubuntu 16.04.1 LTS.
  - My system has 2 X SAMSUNG MZ7KM480 SSD and 6 X SEAGATE  Model: ST1000NX0323. I can create virtual drive on SSD drives without any problem but it does NOT work on SAS drives. The problem is the same with DOS or GPT format.
  - The user is in vboxusers and disk groups.
  - Partitions are readable with the dd command.

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdatah6.vmdk -rawdisk /dev/sdh -partitions 6
VBoxManage: error: Logical partition without magic
VBoxManage: error: Cannot read the partition information from '/dev/sdh'
VBoxManage: error: The raw disk vmdk file was not created
ma@X10DRi:~$ fdisk -l /dev/sdh
Disk /dev/sdh: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x44def683

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdh1            256 244190645 244190390 931,5G  5 Extended
/dev/sdh5            512  52429311  52428800   200G 83 Linux
/dev/sdh6       52429568  55051007   2621440    10G 83 Linux

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdataf6.vmdk -rawdisk /dev/sdf -partitions 6
VBoxManage: error: Cannot read the partition information from '/dev/sdf'
VBoxManage: error: The raw disk vmdk file was not created

ma@X10DRi:~$ fdisk -l /dev/sdf
Disk /dev/sdf: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3D5F9AA3-AA3D-49E4-88B7-1E9CD35FFDF8

Device        Start      End  Sectors  Size Type
/dev/sdf5       512 52429311 52428800  200G Linux LVM
/dev/sdf6  52429568 55051007  2621440   10G Linux filesystem

#
# The behavior is exactly the same with the root user.
#
 - hdparm works well with our SSD drive seems NOT to be working with our ST1000NX0323 drives
 - smartctl works well on our both type of drives
 ",michelparis
15424,Crash when suspending Win10 (14342) guest,Windows,Windows,VirtualBox 5.0.20,2016-08-22T04:44:01Z,2016-08-22T04:44:01Z,"... on a Win8.1 host. Both 64bit.

Screenshot of the Error http://i.imgur.com/OVeyzzg.png",Stanzilla
8947,Serial port raw mode should use O_APPEND for the file,Linux,other,VirtualBox 4.0.8,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
14895,iscsi connection to QNAP failure / infinite loop,other,other,VirtualBox 5.0.10,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
1397,Feature request: Overcommitting of memory (swap in/out),Windows,other,VirtualBox 1.5.6,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
9007,Captured/filtered USB devices are released and reacquired when guest reboots,Linux,Windows,VirtualBox 4.0.8,2016-08-23T07:18:59Z,2016-08-23T07:18:59Z,"Hi,

Host: Xubuntu 9.10 x86, VirtualBox 4.0.8 (with PUEL extension pack).
Guest: Windows XP SP3

When the guest is rebooted, VirtualBox seems to free/release any filtered USB devices, then re-capture them. I think all filtered USB devices should remain filtered when the guest reboots.

This problem is most noticeable when using a USB floppy drive. Most(?) Linux distributions treat USB floppy drives as generic removable drives. So when you insert a disk, the kernel attempts to read the last sector and scans for partition tables. In combination with the default block device readahead of 256 blocks, that process can take 30 seconds or so. *Every time you insert a disk*. It's quite annoying. Floppy disks never have a partition table of course so the scan is pointless. Anyway...

To reproduce the problem:
 - Connect a USB floppy drive to your system.
 - Add the floppy drive to the USB Device Filters of a Windows guest VM.
 - Start the Windows VM. Insert a floppy disk. Notice the drive only spins for a short time. Because it is captured, the Linux host OS doesn't attempt to access it.
 - Reboot the guest OS.
 - Notice how when the guest reboots, the kernel creates a /dev/sdX block device and scans for partitions (taking about 30 seconds). Then the block device is removed when VirtualBox re-captures the device.

Other drives are probably affected similarly, so you get an unnecessary block device creation, partition scan and device removal whenever the guest is rebooted. (That takes less time than for USB floppy drives so will be less noticeable.)

",Donuts
14054,Non-stereo (surround) audio,Windows,Windows,VirtualBox 4.3.18,2016-08-23T12:37:19Z,2016-08-23T12:37:19Z,"I require non-stereo/surround audio to work correctly in virtualbox so I can test the behaviour of applications on multiple OSs. Currently if the guest audio is set to anything other than stereo, the resulting audio is corrupt and only ever plays out the L and R speakers.",Paul17041993
15355,Auto-resize guest (Win 8.1 and 10) not working with Guest additions 5.0.18,Windows,Windows,VirtualBox 5.0.18,2016-08-24T20:28:57Z,2016-08-24T20:28:57Z,"Auto-resize guest using the Guest additions 5.0.18 does not work in a Win 8.1 and Win 10 VM.
I've verified that:
- Auto-rezie guest display is enabled
- Maximum guest screen size is automatic

What I've done (and did NOT help):
- Downgrading to 5.0.16 from 5.0.18 (and reinstalling the matching GA)
- Reinstalling/upgrading Guest Additions

What I've done (and DID help):
- Downgrading to 5.0.14 (and matching GA)
- Using vBox 5.0.18 with the 5.0.14 GA",Martien Korenblom
15855,Custom VESA mode does not work for 4bit resolution,all,all,VirtualBox 5.1.2,2016-08-24T23:38:00Z,2016-08-24T23:38:00Z,"I'm trying to add custom VESA mode 1400x1050x4.

I'm using command VBoxManage setextradata ""WinXp"" ""CustomVideoMode1"" ""1400x1050x4""

and the line

	<ExtraDataItem name=""CustomVideoMode1"" value=""1400x1050x4""/>

is created in WinXp.vbox correctly.

When I try to start the virtual machine VB gives me the VERR_VGA_INVALID_CUSTOM_MODE error.

Note, that 1400x1050x8, 16, 24 and 32  work very fine, but I'm interested in 4bit colors.

A small modification in 'VBox/Devices/Graphics/DevVGA.cpp' will probably solve this problem.

Please refer to the attached 'Custom VESA mode 4bit resolution.png' for a possible solution.",ErikB
15843,"Repeated crashes with ""The memory could not be read""",Windows,Windows,VirtualBox 5.1.4,2016-08-25T20:08:49Z,2016-08-25T20:08:49Z,"Virtual Box used to work fine but since I upgraded to 5.1.0 I'm experiencing crashes of the guest system several times a day and I can't see a pattern.
Every time a new version got released I immediately upgraded my system but the crashes still occur.",schnesim
7919,VM VirtualBox Manager GUI crash when deleting snapshot,Windows,Linux,VirtualBox 4.0.0,2016-08-26T10:56:07Z,2016-08-26T10:56:07Z,"Host: Win7 x64[[BR]]
Guest: SLES 10 SP3 x64 w/o GA[[BR]]

Manager GUI crashes when trying to delete (merge) snapshot for running machine.[[BR]]
It is reproducible on new machine.[[BR]]
If snapshot has saved state it loses it before crash.
That VM and other ones are not affected and are running.",Alil
15870,Parallel port passthrough support - bug in I/O resource scanning,Windows,all,VirtualBox 5.1.4,2016-08-30T22:41:16Z,2016-08-30T22:41:16Z,"English is not my mother tongue; please excuse any errors on my part.

In certain circumstances, Virtualbox is unable to detect correct base I/O address of a parallel port. This happens when the parallel port is an add-on card (PCI, PCIe, ExpressCard). The device driver consists of two parts: bus enumerator and the parallel port itself. The first device has assigned all I/O and IRQ, while the LPT port has no resources at all.

There are two functions involved:

drvHostParallelGetWinHostIoPorts(PDRVHOSTPARALLEL pThis)

and

drvHostParallelGetWinHostIoPortsSub(const DEVINST DevInst)

The second function looks for a device and enumerates its I/O resources. As the LPT port lacks of any resources, the function fails. The caller then fails silently, there is no evidence in log files that the passthrough is defunct.

I don't have VS2010 and I cannot make a build environment to test my changes to the code. If I could only create a build environment, I would attempt to make a workaround to let user specify LPT's I/O base (IRQ is not important),
or fix it to make it list bus enumerators and query them for their I/O addresses.",lelekx
14421,Copy/paste not (always) working from host to guest,Windows,Linux,VirtualBox 5.0.0,2016-08-31T13:31:14Z,2016-08-31T13:31:14Z,"Copy paste sometimes works from host to guest, but then often stops working after a few hours of the VM running. 

Copy paste from guest to host works. ",nopaste
15864,Windows Host not start with virtualbox 5.1.4,Windows,Windows,VirtualBox 5.1.4,2016-09-01T12:10:44Z,2016-09-01T12:10:44Z,"Hi, I have updated to version 5.1.4-110228 but the windows xp host crashes on startup. I attach the logs. The pc has windows 10 pro",Sergio
15857,Defect: 5.1.4 Shared Folders not showing in Ubuntu Linux Guest from  Win7 Host,Windows,Linux,VirtualBox 5.1.4,2016-09-01T13:37:14Z,2016-09-01T13:37:14Z,"After creating a share folder in Ubuntu 16 Guest,
  we cannot see it in Media

2) Same for bi-directionnal copy/paste not working.

",brook245
10195,Can't delete snapshot in 4.1.8,Linux,Windows,VirtualBox 4.1.8,2016-09-01T23:10:26Z,2016-09-01T23:10:26Z,"I made a snapshot (by mistake...I thought that was how one was supposed to end a session before going home.) and now I can't delete it. I get the following messages:

{{{
Failed to delete the snapshot Snapshot 1 of the virtual machine Win7.

Could not merge the medium '/local/home/skelem/VirtualBox VMs/Win7/Snapshots/{e28386b1-690c-4b83-acf2-f522ce331a65}.vdi' to '/local/home/skelem/VirtualBox VMs/Win7/Win7.vdi' (VERR_INVALID_PARAMETER).


Result Code: 
VBOX_E_FILE_ERROR (0x80BB0004)
Component: 
Medium
Interface: 
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
}}}

4.1.8 r75467",Chelmite
15775,Could not read from the boot medium. System halted,Linux,other,VirtualBox 5.0.10,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
15878,LastNormalWindowPosition isn't correctly saved for a maximized window,Windows,all,VirtualBox 5.1.4,2016-09-02T18:17:50Z,2016-09-02T18:17:50Z,"Up to VirtualBox 5.1.0 (don't know about 5.1.2), the LastNormalWindowPosition that was saved for a maximized window would contain the coordinates of the window prior to maximization. That is not the case anymore with VirtualBox 5.1.4. 

The way to reproduce:
1) start a vm with guest additions, wait for it to boot
2) resize the window. Let the guest resize as well
3) maximize the window. Let the guest maximize as well
4) save the machine state
5) start the machine from the saved state. It shoule start maximized
6) ""unmaximize"" the window. Expected behavior: window is resized to the same 
size as was in (2). But that doesn't happen (window stays full-screen size, but not maximized anymore).",mskov
15732,Distorted Display on Windows 10 guest,all,Windows,VirtualBox 5.1.2,2016-09-03T06:08:40Z,2016-09-03T06:08:40Z,"Until recently my win10 guest with raw disk on a dual boot system worked fine. Since 2.8.16 it still boots fine but when the login screen appears, the display is totally distorted (see attachment). Also after logging in blindly the problem is not solved. Booting Win 10 to safe mode works fine. Removing and re-installing VBox Extensions did not help. ",neuweiler
15882,Installer for VBox 5.1.4 doesn't honor non C: locations when creating shortcut,Windows,other,VirtualBox 5.1.4,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
15883,Slashes are not converted to underscores when a VM is part of a group,Windows,all,VirtualBox 5.1.4,2016-09-03T17:45:45Z,2016-09-03T17:45:45Z,"Before placing my VMs into groups, I had no trouble naming my VMs as ""FreeBSD/amd64 stable/10 ZFS"". The XML file was magically saved as ""FreeBSD_amd64 stable_10 ZFS.vbox"" upon initial creation. I was happy, and VBox was happy. I could change the configuration of my VMs; the VMs would still have names like ""FreeBSD/amd64 stable/10 ZFS"", and the XML file would still be named ""FreeBSD_amd64 stable_10 ZFS.vbox"".

Enter the use of groups. Shock and horror ensues!

I can no longer give my VMs names such as ""FreeBSD/amd64 stable/11 BIOS ZFS"". Somehow the magic sanitation of file names is put aside.

Here's an example of a VM currently named ""FreeBSD_amd64 stable_11 BIOS ZFS"", and as appropriate, the XML file is named ""FreeBSD_amd64 stable_11 BIOS ZFS.vbox"". Everyone are happy, except me.

Now, I attempt to change the name of the VM from ""FreeBSD_amd64 stable_11 BIOS ZFS"" to ""FreeBSD/amd64 stable/11 BIOS ZFS"".

VBox makes noises such as ""Failed to save the setting of the virtual machine FreeBSD/amd64 stable/11 BIOS ZFS to D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD_amd64 stable_11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox"".

Details: Could not rename the settings file 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox' to 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD/amd64 stable/11 BIOS ZFS.vbox' (VERR_PATH_NOT_FOUND).[[BR]]
Result Code: E_FAIL (0x80004005)[[BR]]
Component: SessionMachine[[BR]]
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Had I refrained from creating groups, none of the above would have happened, and I would not be the one who created this bug report.

A workaround is to stop the VBox GUI, manually edit the XML file, give the VM whatever name I desire, and launch the GUI once more. In the long run, this is not acceptable.",trondfsi
14757,Flickering in Chrome and odd behaviour of Snipping Tool,Linux,Windows,VirtualBox 5.0.8,2016-09-05T01:46:30Z,2016-09-05T01:46:30Z,"Hi,

since version 5.0.8 I have a terrible flickering in Google Chrome. No matter the website, but it makes it impossible to read or use these websites. Same Website in Internet Explorer doesn't flicker.

Snipping Tool: Sometimes when I click on new screenshot the snipping tool window becomes part of the background, sometimes it leaves a white space where the window was and sometimes it works normally. Haven't figured a trigger that reproduces or avoids it. Workaround is is to abort the screenshot and try again.

Setup:
Host: openSUSE Leap 42.1 RC1
Virtualbox from virtualbox.org, not from the openSUSE repos.
Guest: Windows7 Pro 64bit
Dual Screen on host and guest. 128mb Graphics memory for the VM. 3d acceleration enabled for that vbox.
Graphics driver on the host: radeon
[     5.335] (II) LoadModule: ""radeon""

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

I tried VBox guest additions both w/ and w/o the 3d support, no change. Only disabling 3d acceleration in VirtualBox helped.

Kind regards
Vonor",Vonor
15885,Proposed Memory for openSUSE Linux installs is too small,all,Linux,VirtualBox 5.0.26,2016-09-05T09:24:27Z,2016-09-05T09:24:27Z,"Current openSUSE Memory requirements are 1GB of ram while Virtual box currently proposes 768mb so this number should be increased. 

As openSUSE enables its own filesystem snapshots with btrfs users may also run into issues on the 8GB default hard drive size as well.",simotek
15893,Differencing disk for shared immutable disk saved to wrong VM settings file,Windows,Windows,VirtualBox 5.1.4,2016-09-06T15:07:30Z,2016-09-06T15:07:30Z,"Sharing an immutable drive across two VMs causes VirtualBox to save the differencing disk configuration in the wrong VM's configuration file. This is causing my scripts to fail when they search for the differencing disk UUID in the configuration.

After creating both VM's, the following appears in VM1's configuration file:

{{{
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{c1487c8e-ab83-41ca-8efa-92e14b36c4dc}"" location=""E:/Golden Images/W2K12.vhd"" format=""VHD"" type=""Immutable"">
          <HardDisk uuid=""{a721fb7e-9bae-4347-9e32-f6e73fab310e}"" location=""Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" format=""VHD""/>
          <HardDisk uuid=""{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}"" location=""E:/Machines/VM2/Snapshots/{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}.vhd"" format=""VHD"" autoReset=""true""/>
        </HardDisk>
      </HardDisks>
    </MediaRegistry>
}}}

No MediaRegistry exists in VM2's configuration file. I expected to see a MediaRegistry in both configuration files, each containing only their specific VM's differencing disk.

I can reproduce the issue with the following commands. To create VM1:
{{{
VBoxManage.exe createvm --name VM1 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM1 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM1 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM1 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM1 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM1 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
VBoxManage.exe modifyhd ""E:\Golden Images\Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" --autoreset off
VBoxManage.exe modifyvm VM1 --nic1 hostonly --hostonlyadapter1 ""VirtualBox Host-Only Ethernet Adapter""
}}}

To create VM 2:
{{{
VBoxManage.exe createvm --name VM2 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM2 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM2 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM2 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM2 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
# This line is redundant, but executed by my scripts to ensure the shared disk is immutable.
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM2 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
}}}

I apologize if this is simply because I'm not using the command line interface correctly.",Joshua Rehm
15895,Windows 7 Lights Out on Linux Mint (Mate) Host,Linux,Windows,VirtualBox 5.1.4,2016-09-07T02:50:28Z,2016-09-07T02:50:28Z,"Hi all,

We have been running a Windows 7 VM for quite a while and since the update to 5.1 have an issue with this VM just stopping. No lock up or anything, just a random lights out, this seems to happen when using network services more often than not.

Attached are a couple of logs from when this has happened.

TIA.

",FFH4500
15738,Disabling Windows 10 Guest network adapter hangs VM,Mac OS X,Windows,VirtualBox 5.1.2,2016-09-07T12:24:51Z,2016-09-07T12:24:51Z,"VirtualBox 5.1.2 r108956
Mac OS X 10.11.13 host
Windows 10 Pro Guest
Windows Network adapter in Bridged mode
Disabling the adapter in Windows hangs the VM
Worked fine in 5.1.0",twinhats
15902,keyboard not working when using certain rdesktop options,Linux,Windows,VirtualBox 5.1.4,2016-09-08T06:02:40Z,2016-09-08T06:02:40Z,"First of all, this problem *only* occurs on the login screen of the Windows client.
If I succeed logging into the client, the keyboard works fine.

The scenario:

I just updated the host from Ubuntu 14.04 to 16.04. 
On 14.04 I never saw this problem.
Maybe I should mention, that I upgraded Virtualbox also from 4.3.x to 5.1.4.

I have some headless Windows guests (Win 7, Win 10) - all of them have the same problem.

When I now try to connect from a Linux machine:

rdesktop -a 24 -g 1600x950 -z -N -xl -u klaus -d gbr 192.168.1.30

I see the welcome (login) screen and I'm able to use the mouse, but I cannot type in a password.

I can workaround this using the -p option:

rdesktop -a 24 -g 1600x950 -z -N -xl -u klaus -d gbr -p - 192.168.1.30

but thus is nasty, as you cannot put such stuff into a menu item (putting the password in plain text would help, but us at least as nasty).

Strange to say, that this phenomenon does *not* occur, when I omit all those user related options (-u, -d, -p). When using this commandline:

rdesktop -a 24 -g 1600x950 -z -N -xl 192.168.1.30

everything is fine. I see the login screen and can type in my credentials.
Unfortunately I have to type in all the stuff now (user, domain, password) each time ... that's annoying, but it works .... as long as noone uses one of the -u, -d, -p options.
If anyone tries to connect using one of these options, the keyboard is dead at the login screen for all subsequent connects. 
I need to poweroff/startup the guest machine to get this working again.

This is reproducable with rdesktop 1.7.1 (e.g. on LinuxMint 17.1) as well as with rdesktop 1.8.3 (e.g. on Ubuntu 16.04). Therefore I'd say this is no rdesktop problem but rather a problem of virtualbox.
I unfortunately haven't found possibilities to debug/trace those connections - that would possibly give us some more informations...",kläuser
15498,display size 4096 or more is impossible; guest size is screen size modulo 4096,Mac OS X,Linux,VirtualBox 5.0.20,2016-09-08T07:06:31Z,2016-09-08T07:06:31Z,"In ''Auto-resize Guest Display'' mode or also in Fullscreen mode on a very large screen (4096 pixels or more). I see the following wrong behaviour:

The guest's screen size is only ''actual screen size modulo 4096'' rounded down to the next smaller multiple of 8.
If the size is 4096, then 4096 % 4096 = 0, then the default 1024 width is applied. (or 768 for the height)

I tried setting different sizes with `VBoxManage controlvm <VMName> setvideomodehint` command.

I attached the VBox.log file. during that session I had executed the following commands:

{{{
VBoxManage controlvm Kubuntu setvideomodehint 4096 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4095 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4087 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8191 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8193 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 9192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4095 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4096 32
VBoxManage controlvm Kubuntu setvideomodehint 0 0 32
VBoxManage controlvm Kubuntu setvideomodehint 4088 2160 32
}}}


In the log file one can see, that the resulting guest display size is wrong whenever  w > 4095 or h > 4095

{{{
00:00:15.395987 VMMDev: SetVideoModeHint: Got a video mode hint (4096x2160x32)@(0x0),(1;0) at 0
00:00:15.439417 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:02:15.240295 VMMDev: SetVideoModeHint: Got a video mode hint (4095x2160x32)@(0x0),(1;0) at 0
00:02:17.409141 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:02:56.419179 VMMDev: SetVideoModeHint: Got a video mode hint (4087x2160x32)@(0x0),(1;0) at 0
00:02:58.579637 VBVA: InfoScreen: [0] @0,0 4080x2160, line 0x3fc0, BPP 32, flags 0x1

00:03:19.311747 VMMDev: SetVideoModeHint: Got a video mode hint (8192x2160x32)@(0x0),(1;0) at 0
00:03:20.454025 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:03:25.949484 VMMDev: SetVideoModeHint: Got a video mode hint (8191x2160x32)@(0x0),(1;0) at 0
00:03:28.074011 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:03:43.210929 VMMDev: SetVideoModeHint: Got a video mode hint (8193x2160x32)@(0x0),(1;0) at 0
00:03:44.349569 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=2560 h=1600 bpp=32 cbLine=0x2800 flags=0x1

00:04:06.325388 VMMDev: SetVideoModeHint: Got a video mode hint (9192x2160x32)@(0x0),(1;0) at 0
00:04:08.445923 VBVA: InfoScreen: [0] @0,0 1000x2160, line 0xfa0, BPP 32, flags 0x1

00:04:43.460792 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4095x32)@(0x0),(1;0) at 0
00:04:45.586547 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=4095 bpp=32 cbLine=0xFA0 flags=0x1

00:04:49.388757 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4096x32)@(0x0),(1;0) at 0
00:04:51.501883 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=768 bpp=32 cbLine=0xFA0 flags=0x1

00:05:34.159715 VMMDev: SetVideoModeHint: Got a video mode hint (4088x2160x32)@(0x0),(1;0) at 0
00:05:35.290404 VBVA: InfoScreen: [0] @0,0 4088x2160, line 0x3fe0, BPP 32, flags 0x1

}}}


it looks like the size is only an 8 bit integer.  The lowest 4 bits are always 0 and bits 13 and up are lost.

I tried this with several Linux distributions (Ubuntu, Kubuntu, Mint, Fedora). The behaviour is always the same.

",schnidrig
15909,No notification of major new releases,Windows,Linux,VirtualBox 5.0.26,2016-09-08T13:06:06Z,2016-09-08T13:06:06Z,"VB 5.0.26 was released on July 18, 2016. It wasn't until I browsed virtualbox.org on Sept. 8, 2016 that I learned that there was a major dot release (x.0 to x.1) available that had two maintenance releases after July 18. It appears that the built in upgrade notification is failing to notify when stable dot releases are available (I am assuming that a second maintenance release of a dot release = stable).",Aren Cambre
13073,Video Captures are Blank / Green,Linux,Linux,VirtualBox 4.3.12,2016-09-08T21:53:55Z,2016-09-08T21:53:55Z,"When using the Video Capture in Vbox, nothing is recorded. There is only a ""Green Screen"".

Guest Additions are installed

libvpx is installed

This occurs with or without 3D Acceleration enabled.

Host: Ubuntu Gnome 14.04, Virtualbox 4.3.12 r93733
Guest: Lubuntu 14.04",Hashpling
15772,Ubuntu Mini ToolBar causes problems,Linux,Windows,VirtualBox 5.1.2,2016-09-09T14:30:41Z,2016-09-09T14:30:41Z,"I observed this issue for a while now but it got worse either with the latest VirtualBox updates or with upgrading from Ubuntu 14.04 to 16.04.

When the Mini ToolBar is activated for a VM there are two overlays being created by VirtualBox (each for every display see screenshot). These overlays seem to cause some problems:

sometimes they menus render on the wrong place on the display (only happens if menu is at the bottom)

sometimes unity (ubuntu's launcher) consumes clicks from the VM

since VirtualBox 5.1. when I switch Ubuntu workspace it instantly switches back to the workspace where the VM is running which is a show stopper for me

my workaround at the moment is to switch of the Mini ToolBar",ÄxxlForce
5295,Shared folders cannot be exported via NFS,other,Linux,VirtualBox 3.0.10,2016-09-09T17:10:32Z,2016-09-09T17:10:32Z,"192.168.0.1: virtual maschine with additional mounted ext3 and vboxsf partition (shared folder)
192.168.0.2: any extern PC or other, with need to access of the shared folder of the virtual maschine 

Commands on the extern PC:
""mount -t nfs 192.168.0.1:/mnt/ext3 ..."" works well. 
""mount -t nfs 192.168.0.1:/mnt/shared-folder ..."" does not work.
(mount.nfs access denied by server while mounting 192.168.0.1:/mnt/shared-folder)

Configuration files on 192.168.0.1 (linux virtual maschine):
/etc/fstab:
...
/dev/hda3 /mnt/ext3 ext3 rw,nodev 0 2
vboshare  /mnt/shared-folder vboxsf rw,nodev 0 2

/etc/exports: 
/mnt/ext3 192.168.0.2(rw,async,nohide)
/mnt/shared-folder 192.168.0.2(rw,async,nohide)

/etc/hosts.allow:
portmap: 192.168.0.0/255.255.255.0
mountd: 192.168.0.0/255.255.255.0

Command ""df -h"" on the virtual maschine with shared folder: 
...
/dev/hda3 2,3G 68M 2,1G  4% /mnt/ext3
vboshare  200G 43G 157G 22% /mnt/shared-folder

The issues are checked with 32-bit and 64-bit virtual maschines debian 4.0, debian 5.0 and ubuntu 8.04. Because the problem not occurs with similar mounted ext3 partitions, it seems, the problem is connected with vboxsf partitions = shared folders.

",moppel
15917,Host Panel overlaping guest on full screen on dual monitors,Linux,all,VirtualBox 5.0.14,2016-09-11T15:18:55Z,2016-09-11T15:18:55Z,"Virtualbox: 5.0.14 r105127 from source
Host: Slackware 14.1 3.10.103 XFCE + Extension Pack
Guest: Uauntu 14.04 XFCE, Slackware 14.1 XFCE, Debian 8 LXDE, Windows 7 64bit
- Guest additions included on all

Host panel appears forefront and overlapping my guest taskbar on the opposite screen than I'm currently working on. Auto hiding host panel helps but doesn't fix the problem.",nonenene
15919,No sound when VirtualBox is installed,Linux,other,VirtualBox 5.0.26,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
15918,"Bad 3D performance, maybe related to: VERR_BAD_EXE_FORMAT atikmdag.sys",Windows,Linux,VirtualBox 5.0.26,2016-09-13T21:52:24Z,2016-09-13T21:52:24Z,"I have had strange 3D performance problems with VirtualBox while everything was working fine with VMWARE.

I reported the issue in the forum first:
https://forums.virtualbox.org/viewtopic.php?f=3&t=79456

Thanks to 'Perryg', he found out a line in the log which shows VirtualBox is broken/faulty clearly.


{{{
    00:00:08.740768 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x5 fAccess=0x2 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys:
}}}
 

This is not a problem in the file itself because all windows programs which use the GPU work fine and also VMWARE works fine, in addition the problem was with multiple versions of the drivers in different computers. See:
https://community.amd.com/thread/195664

If you read the person's post. He even tried multiple versions of the driver. I have in my laptop the drivers which come with Windows Update and signed properly and function properly. So the file is perfectly fine!

Thanks",yurtesen
15931,can't load windows 7 on virtualbox after moving virtual machine,other,Windows,VirtualBox 5.1.6,2016-09-14T12:50:37Z,2016-09-14T12:50:37Z,"hello, 
i had vbox installed on win7 and i had a win7 vm workining well.
then i moved the vm to another host (win10) by moving all the folder. 
i added the vm, when i start the vm i see the win7 loading screen, then the vm crash and start again in loop.
i triend even with vbox 5.1.6 and vbox 5.1.7, same result

could you help me please?
thanks",niconico999
15876,Some modern application show corrupted graphic in 3D accelerated mode,Windows,Linux,VirtualBox 5.1.4,2016-09-14T14:35:37Z,2016-09-14T14:35:37Z,"On an Ubuntu 16.04 guest running in a Windows 7even host some application show complete corrupted graphic (only some black and white random pattern)
Affected application

1) Chrome and Chromium with acceleration enabled
2) Skype for Linux beta (new version)
3) Ubuntu Amazon app

The VB log gets filled by these warnings:

{{{

0:00:59.077839 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.082506 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.116003 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.128856 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.160880 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.193186 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
}}}


Several users report the problem with different graphic cards, confirmed with Intel HD graphics and Geforce GTX 980 Ti.
Link to forum thread: [https://forums.virtualbox.org/viewtopic.php?f=3&t=77349]",Menion
15581,VirtualBox v5.0 fails on Linux v4.6 kernel host with floppy drive attached,Linux,Windows,VirtualBox 5.0.24,2016-09-15T07:58:08Z,2016-09-15T07:58:08Z,"When I start VirtualBox (currently v5.0.24) on a Linux v4.6 system running on a computer with a floppy drive fitted (yes, I know, it's becoming rare, but I need floppy for file exchanges with my old computers), VirtualBox fails to start Windows guests if the floppy drive is empty or contains a write-protected floppy disk.

Here are VirtualBox's reports:

1.- No floppy disk in drive:
{{{
The floppy controller cannot attach to the floppy drive (VERR_DEV_IO_ERROR).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
and in /var/log/messages:

{{{
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0dbe020 VMMR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0071020 VBoxDDR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0002020 VBoxDD2R0.r0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
}}}


2.- Write-protected floppy disk in drive:

{{{
The floppy controller cannot attach to the floppy drive (VERR_WRITE_PROTECT).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

I'm also attaching the log for a failed start of a Windows 7 guest session, with no floppy disk in drive.

This issue doesn't happen with older kernels (OK at least up to Linux kernel v4.1).",dinosaur0
15828,Desktop shortcuts (Alias) not working on OSX Host (10.9.5) after updating to 5.1.4.,Mac OS X,Windows,VirtualBox 5.1.4,2016-09-15T09:22:47Z,2016-09-15T09:22:47Z,"I have two VMs (Win7 and WinXP) that I always start from shortcuts I have on my desktop (properly created from the ""Create Alias on Desktop"" - selected from the Machine Menu of the Virtualbox Manager). These shortcuts no longer work (either with or without Virtualbox running) after updating to 5.1.4.  Even deleted the existing shortcuts and recreated them using 5.1.4 without any luck.

No error messages are generated, the shortcut icons only blink when I double click on them and nothing else happens.

The VMs start o.k. from the Virtualbox Manager and function normally from that point.",Gregg Haines
14348,Video playback freezes in Linux guests with KVM paravirtualization enabled,Windows,Linux,VirtualBox 5.0.0,2016-09-15T11:36:18Z,2016-09-15T11:36:18Z,"When KVM paravirtualization is enabled in VirtualBox 5.0.0 Linux guest operating systems fail to playback video. This is apparent with all video tested, including web video using Flash or HTML5. This has been tested on Antergos, Mint 17.2, and Fedora 22. Host Operating systems used to confirm this bug were Windows 8.1 and Windows 10.",Markon101
15898,Add Shared Folder - pasting folder path causes VBox Manager to crash - until navigated to.,Windows,all,VirtualBox 5.1.4,2016-09-15T14:13:50Z,2016-09-15T14:13:50Z,"{{{
VirtualBox Manager version 5.1.4.
Windows 10.
}}}

(Up to this time I have never tried to add a Shared Folder. Ie no 
VM has one, and I've never attempted to configure one.)

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Paste a folder path into the Folder Path entry box.
select OK.
VirtualBox Manager crashes.
}}}

This crash was completely repeatable until I approached the task in 
a different way.

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Select the drop-down arrow in the Folder Path entry box.
Navigate to the folder I want to add.
Select it.
Select 'Select Folder'.
All works fine.
}}}

After doing the task once this way it now works entirely 
satisfactorily doing it the first way, ie by pasting in a 
folder name.

So, not as serious a fault as I first thought but smells to 
me like something not initialized if one hits some code first 
by pasting the folder name rather than by navigating to it.

[[br]]
I have reported this on the forum and been advised that it is 
a Qt5 library issue and that I should report it here.

I have no unusual storage devices, it's a conventional Windows
desktop computer.  There is no Bluetooth.
[[br]]
The crash occurred for all the VMs that I tried.  Most are
Windows guests, one is Linux.
[[br]]
Once it works it continues to work.

",Richard Kerry
15935,VirtualBox breaking Unity's Compiz Scale Plugin,Linux,Windows,VirtualBox 5.1.6,2016-09-15T15:09:13Z,2016-09-15T15:09:13Z,"My setup: Ubuntu 16.04 host, Win8 64bit guest.

On the host when I enable the Compiz Scale plugin in CompizConfig Settings Manager and give it a window binding (say the top of the screen initiates the plugin) everything works except when Virtualbox is the active window. When Virtualbox is the active window it ""steals"" the mouse movement when moving to the top of the screen and leaves the desktop in a bad state. The scale plugin is now broken (it no longer triggers) until I manually switch to a different active application then re-initiate the scale plugin via the mouse at the top of the screen. After that it works fine again until I try to trigger it with VirtualBox being the active window. If, however, I press the host key (right ctrl in my case) before I move the cursor to the top of the screen it initiates the Scale plugin as expected.

On previous versions of VirtualBox this all worked. Not exactly sure what version this started happening in unfortunately.

This is quite hard to explain, but it is 100% reproducible on my machine. I've tried everything from clearing all gnome settings, clearing all compiz settings, etc.

Let me know if you need any more information.",shockwave
15822,"window guest on os x host, select multiple items with ctl right mouse click not torking",Mac OS X,Windows,VirtualBox 5.1.4,2016-09-15T16:33:14Z,2016-09-15T16:33:14Z,"if the control key is held down while single left clicking on an item in windows 7, it brings up the same menu that right clicking will bring up. The desired behavior is for the user to be able to select multiple items separately out of a group.  This has changed since vbox 5.0.n.  If the user has a trackpad or a laptop, and enables ""3 finger drag"", you can hold the ctl key and select the individual items by pointing to each item and doing a 3 finger drag with the ctl key held down.  however, this won't work with a mouse, not even the current touch sensitive apple mouse.",ascott
15930,Settings/Storage crashes VBoxManage (always...on one PC),Windows,all,VirtualBox 5.1.6,2016-09-15T16:34:21Z,2016-09-15T16:34:21Z,"Selecting a VM then Settings->Storage crashes VirtualBox Manager.
[[br]]
This happens always on one PC but not at all on another.
Both are running Windows 10.

I note also that having triggered this fault deliberately I am getting
one Application Error at the point of the crash, followed by a number 
of further events relating to this over the following half an hour or 
so.

I am attaching all the Windows Event viewer reports that mention VBox 
Manager, and a zipped copy of all the referenced WER folders.
",Richard Kerry
15940,Failed to open a session while starting a virtual machine,Mac OS X,Linux,VirtualBox 5.1.6,2016-09-16T04:54:36Z,2016-09-16T04:54:36Z,"Virtual Box version 5.1.4

Mac OS X El Capitan version 10.11.6 with McAfee Endpoint protection

16GB Ram, Intel Core I7 processor

I installed virtualbox on my Mac & then imported an OVA [Oracle DB developer apps VM, an old version released in 2013].

The VM n/w settings were NAT with port forwarding enabled [localhost port 1700 & guest VM port 1700]. On starting the VM, it failed with the following message -
{{{
Failed to open a session for the virtual machine DevVM.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
}}}
Setting the n/w to Nothing or NAT network allows the VM to boot without any issues.

To avoid any suspicion with the old OVA, I downloaded a CentOS minimal OVA from the following location -

https://sourceforge.net/projects/virtualappliances/files/Linux/CentOS/CentOS-6.4-i386-minimal.ova

It too failed with the same error, & changing the n/w settings to Nothing or NAT network worked.

I had disabled the McAfee Endpoint protection in both cases, still there was one process McAfee process running in the background -
{{{
bhushan:~$ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  143    3 0xffffff7f8329f000 0x61000    0x61000    org.virtualbox.kext.VBoxDrv (5.1.4) 63317E7D-29D2-38A1-9B7C-BA930B0E017E <7 5 4 3 1>
  146    0 0xffffff7f83300000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.1.4) 40E1F37A-3BAE-3E82-A8CE-8DEB364664E3 <145 143 39 7 5 4 3 1>
  147    0 0xffffff7f83308000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.1.4) 1E11B050-BCCD-31BF-82AC-DACA1E2EB803 <143 7 5 4 3 1>
  148    0 0xffffff7f8330d000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.1.4) 1EE6EA19-32FB-3EF4-93B4-E4AF47EF4051 <143 5 4 1>
  149    0 0xffffff7f83313000 0xe000     0xe000     com.McAfee.AVKext (1) 7116ADFA-51F7-3BC3-8206-BEC1C180A1E0 <4 1>
bhushan:~$
}}}
NOTE: Uninstalling McAfee is not an option for me as this is a company provided machine & IT team would not be happy with it.

Logs attached:

VBox.log - for the DevVM [oracle DB VM from 2013]

CentOS-6.4-i386-minimal-2016-09-12-10-52-32.log - for the CentOS VM",Bhushan
15943,Wrong hostonlyif mask,Windows,all,VirtualBox 5.1.6,2016-09-16T11:14:02Z,2016-09-16T11:14:02Z,"I'm using VirtualBox as a Vagrant provider and when I specify an netmask of 255.255.255.240, the first vagrant up works fine but on subsequent ups a new interface is generated with automatic ip address.

As I explore the source of the issue I find that at vboxmanage list hostonlyifs the interface with the pretended network has a printed netmask of 255.255.255.'''15'''. This is an issue since that in fact, at network interface settings, the actual network mask is the 255.255.255.240.

I'm suspecting that this issue is leading Vagrant to assume that there's no interface for the pretended network and then it creates a new one and setted to the already existing network which cases VirtualBox to change adapter to automatic IP.",nbranco
15848,Choppy Audio and Slow Flash Video in VirtualBox 5.1,Linux,Windows,VirtualBox 5.1.4,2016-09-16T15:52:38Z,2016-09-16T15:52:38Z,"Host: Fedora 24 - 64-bit + Pulseaudio<br>
Guest: Windows 10 - 64-bit <br>
<br>
Audio is choppy with sound artifacts. Am able to reproduce it on a couple of installations now on 2 different laptops. Very difficult to watch a video in VM<br>
<br>
Also, there is another problem which might be unrelated but flash videos on different sites hang while loading inside VM. Sometimes they even become slow.However, they instantly open on browsers outside the VM. In the 5.0 series I used to face flash videos becoming *slow* during playback(like 1 second on the flash video elapsing after 3 seconds in real). I didnt report it because a restart would fix the problem for many hours till it recurred. This problem seems to have been cured in 5.1 though.

",shek
15942,vm crash on macos upon cmd+c,Mac OS X,Linux,VirtualBox 5.0.26,2016-09-16T19:10:50Z,2016-09-16T19:10:50Z,"virtualbox 5.0.26 on macos.
sometimes, the vm crashes (maybe once every two months or so).
last time it specifically happened when (accidentally) pressing cmd+c.

the vm log ends like this :

{{{
92:22:28.521238 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:22:28.521254 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:22:28.521277 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:22:28.521337 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:22:28.521342 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:22:28.521346 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:22:28.521470 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885280 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885336 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x5
92:53:54.885344 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x5
92:53:54.885369 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.885369 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Using fallback buffer since no source bitmap is provided
92:53:54.885610 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885626 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:53:54.885656 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.886947 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.886955 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.886959 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:56:51.703893 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:56:51.703989 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
93:43:17.399764 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received
93:43:17.401758 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.401775 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received.
93:43:17.401778 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to exit, notifying listener...
93:43:17.441045 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillExit: Machine-window #0 will exit native fullscreen
93:43:17.968714 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received
93:43:17.968735 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowDidExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.968740 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received.
93:43:17.968743 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode exited, notifying listener...
93:43:17.970210 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenDidExit: Machine-window #0 exited native fullscreen, changing visual-state to requested...
}}}",Richlv
15950,OS X host UI slowdown during Linux guest usage,Mac OS X,Linux,VirtualBox 5.1.6,2016-09-18T08:49:23Z,2016-09-18T08:49:23Z,"I am using VirtualBox on my OS X laptop since VirtualBox version 4.3.

When I updated my OS X to El Capitan I had to update VirtualBox to version 5.0 too (because vbox 4.x didn't support El Capitan when I applied OS X update).

Since my update to VirtualBox 5.0 I noticed that OS X User Interface (UI) slowdown in time during active guest usage.

First few days all looks OK, but after one week of active guest usage (my guest running CentOS 6 x86_64 with X Window System + Gnome, with VirtualBox guest utils) host system UI slowdown to unacceptable level. All OS X graphical effects lagging.

If I have little usage of my Linux guest, host system may slowdown very little - 1-3 weeks host may work before visible slowdown.

If I stop guest or suspend it and start again (without OS X restart), system will go back to normal state and slowdown will begin accumulate again.

One week ago I updated to Virtual Box 5.1, apply all available updates to OS X, update VirtualBox guest utils in hope to have no slowdowns. But it still happened again.

I had installed in my My OS X host: VirtualBox, Skype, Adium and nothing else, I use Safari very active. Linux guest has installed CentOS 6 with Graphical Interface, nothing special - I am using only gnome terminal + ssh.

",osx-user
15112,Guest Additions autorun doesn't work with Mate Desktop (doesn't recognize mate-terminal),all,Linux,VirtualBox 5.0.14,2016-09-18T18:26:12Z,2016-09-18T18:26:12Z,"Please reference lines 44-63 of autorun.sh in VBoxGuestAdditions_5.0.14.iso ...

{{{
# Get the name and execute switch for a useful terminal emulator
#
# Sets $gxtpath to the emulator path or empty
# Sets $gxttitle to the ""title"" switch for that emulator
# Sets $gxtexec to the ""execute"" switch for that emulator
# May clobber $gtx*
# Calls mywhich
getxterm() {
    # gnome-terminal uses -e differently to other emulators
    for gxti in ""konsole --title -e"" ""gnome-terminal --title -x"" ""xterm -T -e""; do
        set $gxti
        gxtpath=""`mywhich $1`""
        case ""$gxtpath"" in ?*)
            gxttitle=$2
            gxtexec=$3
            return
            ;;
        esac
    done
}
}}}

Lines 52 and 53 should be changed to the following (adding mate-terminal):

{{{
    # gnome-terminal and mate-terminal use -e differently to other emulators
    for gxti in ""konsole --title -e"" ""gnome-terminal --title -x"" ""mate-terminal --title -x"" ""xterm -T -e""; do
}}}

This allows autorun to function within the Mate Desktop environment.",kuacceshi
15292,"Application Error ""The memory could not be read""",Windows,Windows,VirtualBox 5.0.16,2016-09-18T23:05:43Z,2016-09-18T23:05:43Z,"I recently upgraded to 5.0.16 and started to see a crash after some time of actively using a virtual machine. 

I am attaching the log files I found. If there is a way to enable additional log files to be created please let me know. I also enabled the minidumps in Windows but this crash did not seem to generate any sort of dump.",Plazgoth
15959,Save state crashes when 3D acceleration is enabled,Mac OS X,Linux,VirtualBox 5.1.6,2016-09-20T08:13:53Z,2016-09-20T08:13:53Z,"{{{
Process:               VirtualBoxVM [60994]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               5.1.6 (5.1.6)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [60975]
Responsible:           VirtualBoxVM [60994]
User ID:               501

Date/Time:             2016-09-20 08:55:59.868 +0200
OS Version:            Mac OS X 10.11.6 (15G1004)
Report Version:        11
Anonymous UUID:        D9DBB08D-4C4D-8B25-6CC5-48A55E634305

Sleep/Wake UUID:       A19E6FC4-4C2A-4961-BD52-A4258770AA33

Time Awake Since Boot: 390000 seconds
Time Since Wake:       6400 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 0x00000000414b0000
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x414b0000:
-->
    __TEXT                 00000001057e2000-00000001057e9000 [   28K] r-x/rwx SM=COW  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM

Application Specific Information:
Performing @selector(_close:) from sender _NSThemeCloseWidget 0x7fce42ae37f0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtCoreVBox           0x000000010686e7a0 QHashData::free_helper(void (*)(QHashData::Node*)) + 64
1   org.qt-project.QtGuiVBox            0x0000000106ea28e5 QTextFormatCollection::~QTextFormatCollection() + 69
2   org.qt-project.QtGuiVBox            0x0000000106eba708 0x106d7e000 + 1296136
3   org.qt-project.QtGuiVBox            0x0000000106eba79e 0x106d7e000 + 1296286
4   org.qt-project.QtCoreVBox           0x00000001069e4201 QObject::~QObject() + 1841

}}}",eoftedal
15695,mod_timer_pinned will be dropped from linux kernel v4.8,all,all,VirtualBox 5.1.2,2016-09-20T09:34:22Z,2016-09-20T09:34:22Z,"The Linux kernel is about to drop function mod_timer_pinned
See:

http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=177ec0a0a531695210b277d734b2f92ee5796303

This change has meanwhile already been adopted by realtime patch rt8, resulting in vbox modules being un-available for this patched kernel.
The function will be ultimately dropped from kernel series 48.

Current situation in vbox is this:
{{{
$ grep -re ""mod_timer_pinned""

src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c:# define mod_timer_pinned mod_timer
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies);
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies);
src/VBox/Runtime/r0drv/linux/timer-r0drv-linux.c: mod_timer_pinned(&pSubTimer->u.Std.LnxTimer, pSubTimer->u.Std.ulNextJiffies); 
}}}",manjaro_oberon
15955,"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag and drop error from guest Drag (VERR_FILE_NOT_FOUND)""",Windows,Windows,VirtualBox 5.1.6,2016-09-20T11:56:43Z,2016-09-20T11:56:43Z,"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag  and drop error from guest Drag (VERR_FILE_NOT_FOUND)  VBOX_E_IPRT_ERROR (0x80BB0005)"".
My operating system: win10_1607.",zhaoyao
15963,VBoxSVC continues to run after closing Virtualbox manager / wakes host PC,other,other,VirtualBox 5.1.6,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
15953,doc/manual/fr_FR/ missing man_VBoxManage-debugvm.xml and man_VBoxManage-extpack.xml,Linux,Linux,VirtualBox 5.1.6,2016-09-21T14:57:54Z,2016-09-21T14:57:54Z,"I'm trying build Vbox with VBOX_WITH_DOCS_TRANSLATIONS=1


{{{
kmk: *** No rule to make target `/builddir/build/BUILD/VirtualBox-5.1.6/doc/manual/fr_FR/man_VBoxManage-debugvm.xml', needed by `/builddir/build/BUILD/VirtualBox-5.1.6/obj/obj/manual/fr_FR/user_man_VBoxManage-debugvm.xml'.  Stop.
}}}

in ./doc/manual/Makefile.kmk, user_man_VBoxManage-debugvm.xml should not be add to fr_FR translation .

fyi is not a new bug , search on french contributions seems that doesn't have debugvm

https://www.virtualbox.org/pipermail/vbox-dev/2013-February/011232.html etc ",sergiomb
15957,"GUI of guest Fedora 24 4.7.3-200.fc24.x86_64 freeze ""blank"" on login screen",Windows,Linux,VirtualBox 5.1.6,2016-09-21T22:39:03Z,2016-09-21T22:39:03Z,"I'm using VirtualBox version 5.1.6 r110634 on Windows with Fedora 24 4.7.3-200.fc24.x86_64 as guest, both updated to the last patch.

I have the last version of the Guest Additions installed.

And I operate the Guest full screen.

The guest GUI freeze on the login, leaving a blank screen, only the background color is visible, forbidding any action with the mouse or keyboard, apparently.

To refresh the GUI after a mouse or keyboard typing I have to click on the toolbar of the host, to restore the Windows screen.

When I switch back to the guest, the guest screen is updated.

After the login screen all comes back to normality.

",par7133_2
15941,Error occurs trying to add a machine to be fixed.,Windows,all,VirtualBox 5.1.6,2016-09-21T23:58:04Z,2016-09-21T23:58:04Z,"An old machine with an old reference to a DVD image cannot be added as the manager incorrectly tries to ""run"" it before actually adding it in, the machine cannot be fixed if its not already in the manager.",Paul17041993
15968,Crashing VirtualBox,Windows,other,VirtualBox 5.1.6,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
15936,5.1.6 segfault in VBoxDD.so on USB unplug,Linux,Windows,VirtualBox 5.1.6,2016-09-22T17:40:27Z,2016-09-22T17:40:27Z,"Hi,
the VM window just disappears.
It does not happen every time. As matter of fact I was working several days now with many USB unplug events. This time I captured logs.

{{{
04:11:12.098613 VUSB: Detached '00007fe874d5be50[proxy 0c2e:096a]' from port 1
04:11:12.098710 AssertLogRel /home/vbox/vbox-5.1.6/src/VBox/VMM/VMMR3/TM.cpp(1727) int TMR3TimerDestroy(PTMTIMER): <NULL>
}}}

and syslog

{{{
Sep 15 17:14:41 don kernel: [27511.485796] USBDevIo--1[19180]: segfault at e8 ip 00007fe89133910a sp 00007fe85557ae90 error 4
Sep 15 17:14:41 don kernel: [27511.485802] EhciFramer[14246]: segfault at f0 ip 00007fe891335ca0 sp 00007fe85600eb50 error 4 in VBoxDD.so[7fe89127a000+28e000]
Sep 15 17:14:41 don kernel: [27511.485808]  in VBoxDD.so[7fe89127a000+28e000]
}}}

 I can also share the Ubuntu crash report with the devs; but do not want to see it in the public. I this also 9MB.

And I can provide the USB device if that makes a difference (I live close to Endersbach).

Here is the link to the forum post:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=79708&p=372643#p372643]
(there is also wrote about another crash, but I think the two are unrelated).

",ucrasher2
15557,Solaris + SMP: Performance decreases as you add processors to guest,Solaris,Windows,VirtualBox 5.0.22,2016-09-22T21:16:05Z,2016-09-22T21:16:05Z,"I found that with VirtualBox 5.0.x, when you have 1-2 processors assigned to a VM, performance is quite fast. But the more processors you add, the slower the guest VM becomes. I've gone up to 16 processors, which is very slow to boot and extremely laggy after logging in (even Task Manager stopped responding.)

For a scientific test, I used the same host and guest, with a combination of vbox versions and processors assigned to the guest.

The host:
- O/S: Solaris 11.2.15.4.0
- Hardware: Oracle X4-2L
- CPUs: Quantity 2 of E5-2690 v2, 10 cores, 20 threads (Total of 20 cores, 40 threads)
- RAM: 512GB

The guest:
- O/S: Windows 7 + IE 9 Developer VM, downloaded from https://developer.microsoft.com/en-us/m ... tools/vms/
- RAM: 4GB
- Video RAM: 64MB

Below are the timings for how long it takes to boot the guest VM (complete when you see the start button):

VirtualBox 4.3.32:
        - 4 CPU: 0:24
        - 10 CPU: 0:30
        - 16 CPU: 1:06
VirtualBox 4.3.38:
        - 4 CPU: 0:23
        - 10 CPU: 0:30
        - 16 CPU: 0:48
VirtualBox 5.0.4:
        - 4 CPU: 0:22
        - 10 CPU: 1:44
        - 16 CPU: 3:36
VirtualBox 5.0.22:
        - 4 CPU: 0:21
        - 10 CPU: 1:40
        - 16 CPU: 4:15

I'm not 100% sure that this is the cause of the issue. But, by doing ""truss"", ""pstack"" and ""pfiles"" commands, I found that several stack traces that are performing a tremendous amount of ioctl() system calls against the /dev/vboxdrv device. Here are some of the stack traces:

Stack Trace 1:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185687, ffff80ffbe13ddc0)
     ffff80ffa385df0f SUPR3CallVMMR0Ex () + 30f
     ffff80ffa0accad3 _Z19vmR3HaltGlobal1HaltP6UVMCPUjm () + 1e3
     ffff80ffa0acd004 VMR3WaitHalted () + f4
     ffff80ffa0a62d66 EMR3ExecuteVM () + 656
     ffff80ffa0acbbcf _Z25vmR3EmulationThreadWithIdP11RTTHREADINTP6UVMCPUj () + 12f
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}


Stack Trace 2:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185698, ffff80ffbcbceda0)
     ffff80ffa3862442 SUPSemEventWaitNoResume () + 82
     ffff80ff9fd3d440 _Z15ahciAsyncIOLoopP9PDMDEVINSP9PDMTHREAD () + 330
     ffff80ffa0a87aea _Z15pdmR3ThreadMainP11RTTHREADINTPv () + 6a
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}


Stack Trace 3:

{{{
     ffff80ffbf51edba ioctl    (13, ffffffffc0185698, ffff80ffbc2fcc60)
     ffff80ffa3862442 SUPSemEventWaitNoResume () + 82
     ffff80ffa0b45828 _Z29pdmR3R0CritSectEnterContendedP11PDMCRITSECTmPK15RTLOCKVALSRCPOS () + 98
     ffff80ffa0b45914 PDMCritSectEnter () + a4
     ffff80ffa0a98424 PGMR3PhysReadExternal () + 34
     ffff80ffa0a7a4e8 _Z20pdmR3DevHlp_PhysReadP9PDMDEVINSmPvm () + 78
     ffff80ff9fd0b4f4 _Z17ohciR3ThreadFrameP9PDMDEVINSP9PDMTHREAD () + 254
     ffff80ffa0a87aea _Z15pdmR3ThreadMainP11RTTHREADINTPv () + 6a
     ffff80ffa37d8aac rtThreadMain () + 2c
     ffff80ffa38557c1 _Z18rtThreadNativeMainPv () + 51
     ffff80ffbf515ef5 _thrp_setup () + a5
     ffff80ffbf5161a0 _lwp_start ()
}}}

Currently, this issue prevents us from using 5.0.x at all.",KSJohn
15974,python host.create_host_only_network_interface returns bad object,Windows,Linux,VirtualBox 5.1.6,2016-09-22T22:46:19Z,2016-09-22T22:46:19Z,"vbmanager = virtualbox.Manager()
vbox      = vbmanager.get_virtualbox()
host      = vbox.host   

hoa,progress = p_host.create_host_only_network_interface()
progress.wait_for_completion(32000)

print hoa.name

The print statement generates an error 

Failed to find attribute name in <virtualbox.library.IHostNetworkInterface object at 0x0000000008FB6898>



However, the interface was created.",silvermangb
15977,Ubuntu 14.04 crash when open windows 7 guest machine,Linux,Windows,VirtualBox 5.1.6,2016-09-23T09:05:36Z,2016-09-23T09:05:36Z,"Hi everybody,
my ubuntu 14.04.1 with kernel 4.4.0-38-generic #57 crash when i try to open a windows 7 guest machine. i just installed gcc ver. 5.4.1 20160904
watch in other forum... but the problem persist.
New guest addition installed.

Guest machine was installed with VBox 4.xx, and ubuntu kernel 3.16.xx.

When host crash i can only move the mouse on desktop.
Ubuntu 14.04.1 with KDE  4.13.2

What do i do to resolve?

Sorry for my easy English.",zipp0
15979,vertio-net causes Cisco AnyConnect instablity,Windows,Windows,VirtualBox 5.1.6,2016-09-23T18:21:10Z,2016-09-23T18:21:10Z,"I have been running a Windows (8.1 and 10) guest for several years, using AnyConnect from the guest to VPN into our corporate network.  At some point I transitioned to using the virtio-net driver and it worked well for a long time.  

At some point a few months ago the VPN became very unstable.  I would experience random disconnects, especially during periods of constant VPN utilization (screen sharing, large file transfers, etc).  

When it disconnected, it would reconnect, but would not configure the ip stack properly and I could not pass any traffic without disconnecting and reconnecting.  I lived with this for several months and decided to finally take some time to see if I could find a solution.

Ultimately, going to a virtualized Intel PRO/1000 MT Desktop adapter seemed to fix the problems.  For some reason it appears that recent versions of AnyConnect stopped working well with the virtio-net adapter.

I don't know if this would be an AnyConnect, a VirtualBox, or a VirtIO-net issue, and will not be offended if this gets closed immediately.  However I wanted to be sure it was documented somewhere for anyone else who may experience these issues in the future.",J. Fry
15915,Image removed by snapshot restore still shown as attached in media manager,Windows,all,VirtualBox 5.1.4,2016-09-23T19:04:43Z,2016-09-23T19:04:43Z,"Longstanding bug:

Steps to reproduce:
* select a VM with an empty virtual optical drive,
* create a snapshot of this VM,
* attach some new ISO image to the optical drive,
* restore the snapshot (do not create one for current state),
* check ""Attached to"" status of ISO image in virtual media manager.

Observed:
ISO image is still reported as ""Attached to: ''Name_of_VM''"". As a consequence, ""Remove"" button is disabled.

Expected:
ISO image should be reported as ""''Not Attached''"".

Workaround:
Re-add ISO image, and then remove it manually before restoring the snapshot.
",chrfranke
15980,Guests won't go in Save States on Host shutdown with Ubuntu 16.04,Linux,all,VirtualBox 5.1.6,2016-09-23T19:52:18Z,2016-09-23T19:52:18Z,"I've noticed that since Ubuntu 16.04 (probably since systemd was introduced with 15.04), VMs won't automatically go in savestates on shutdown or reboot of the host.
Following instructions in vboxdrv.sh, I created a virtualbox file in /etc/default, containing SHUTDOWN_USERS=""myuser"" and SHUTDOWN=savestate with no luck.
Here's what I've tested:
1. I've done that test with a fresh install 14.04 and it works like a charm.
2. With 16.04, if I run /usr/lib/virtualbox/vboxdrv.sh stop, all VMs will successfully go in savestate.
3. If I run ""systemctl stop vboxdrv.service"", all VMs will successfully go in savestate as well.
I blame systemd. There seem to be some configuration errors concerning the dependencies in vboxdrv.service but I couldn't figure out how to fix them.",uspinosa
15618,"5.1 and Windows XP machine crashes (raw mode, VERR_REM_VIRTUAL_CPU_ERROR Guru)",Windows,Windows,VirtualBox 5.1.0,2016-09-23T22:00:33Z,2016-09-23T22:00:33Z,"Just upgraded to 5.1 from 5.0.24 - and Windows XP machine crashes every time you try to load. The saved session crashed. The fresh boot crashed. I can do a Windows Safe boot (and loaded the new utilities there), but a regular boot still crashes.",Trolleyfan
15642,Never fixed VBox 5.1/5.0.26/24 VGA: fixed an occasional hang when running Windows guests with 3D enabled,Linux,Windows,VirtualBox 5.1.0,2016-09-24T06:08:43Z,2016-09-24T06:08:43Z,"When I installed GuestAddition of VBox5.1/5.0.26 also 5.0.24,
they required to check 2D/3D function as automatically.

I always turned off 3D function for disabling at VMM.
Only 2D using I can not get more bigger screen size 1280x720 on GuestOS
Before your announcement of fixed 3D function,I could used 1920x1200 as GuestOS.
I think this is also bug.

But it is more terrible things which turn on 3D function on VMM.
After turn on 3D function when GuestOS(Windows10 64bit) is started up, GuestOS is crashed and HostOS(Debian8 64bit)Gnome on Xorg also is crashed. I attached log file.

It is seemed to have relationship with GPU.
Crashed GPU is NVIDIA Corporation GF108 [GeForce GT 630] on Debian8

But I also tested below GPU.It is no problem at VBox 5.1.
NVIDIA Corporation GF106 [GeForce GTS 450]

Thank you

Yomo



",Yomo
15960,Copying of HTML from windows host to Firefox on a Linux guest doesn't work,Windows,Linux,VirtualBox 5.1.6,2016-09-26T07:18:07Z,2016-09-26T07:18:07Z,"I don't know if it is a problem of Firefox or of VirtualBox itself. Copy-pasting HTML works perfectly fine to e.g. Chrome and LibreOffice Writer. But for some reason it doesn't work if pasting is done to Firefox. Though if you copy HTML directly from the linux guest (e.g. from Chrome, Firefox or LibreOffice) and paste to Firefox on the same guest - it works fine. I've also tried to examine the content of X11 clipboard in the guest and ""text/html"" target seems to be perfectly fine (when obtained with some tools like xclip). I've also tried to write the exact content of ""text/html"" provided by VirtualBox in the guest to the X11 clipboard (with ""xclip -t text/html -selection clipboard"") - and if I do that, then pasting works fine as well. It would be really great, if you could confirm that the problem is in the way how Firefox reads the content and not in the way how VirtualBox is providing this content to Firefox - then I would create a bug ticket on the Firefox bug tracker instead. 

Thnx in advance if you decide to investigate this issue.",mskov
15903,Media not released after a snapshot revert,Windows,all,VirtualBox 5.1.4,2016-09-26T07:45:19Z,2016-09-26T07:45:19Z,"If you revert to a snapshot where some media was not attached, it doesn't get released. The way to reproduce:[[BR]]
1) Create a snapshot without any media attached[[BR]]
2) Attach an iso image to the VM [[BR]]
3) Revert to a snapshot[[BR]]
4) The VM doesn't have the iso attached anymore (as expected). But in the ""Virtual media manager"" this iso is still shown as attached and ""release"" of the iso doesn't work.

If you kill VBoxSVC and start ""Virtual media manager"" again, then the iso is shown as ""not attached"" and can be released without problem.",mskov
15817,Display with Windows 10 guest and OSX host is corrupted,Mac OS X,Windows,VirtualBox 5.1.4,2016-09-26T09:38:03Z,2016-09-26T09:38:03Z,"I have installed Windows 10 on my retina MacBook Pro and on my (non retina) iMac. Unfortunately with the latest release of VirtualBox the display on a Windows host is corrupted.

Specifically, when I start typing or I perform any mouse-related gui-event activity (i.e. press a button, select some text), then the square area that takes part of this activity is grayed out. Note that only the ""refresh"" part of the screen is damaged, not the whole screen.

If for example VB loose focus and gains it again (i.e. when the display is forced to redisplay/redraw) then the visual returns to normal.

As an example I attach a screenshot. I have clicked on the language button of the Windows login screen at the bottom, where a pop-up appears to select languages as well as on the text field to write the username. For these actions, all partially redrawn screen sections are completely grayed out, making the interface totally unusable.",terataki
15181,Video Capturing broken within guest systems with 3D enabled,Windows,Linux,VirtualBox 5.0.14,2016-09-26T14:29:44Z,2016-09-26T14:29:44Z,"NOTE: This refers to capturing video from WITHIN the guest, and does NOT refer to VirtualBox's ""video capture"" capability, which seems to work fine (but with no sound, by design)

I am trying to record (a portion of) my desktop along with my audio into a video file, from the client OS. In the past I've used two different tools to do this, either [http://www.maartenbaert.be/simplescreenrecorder/ SimpleScreenRecorder] (great for recording only a portion of the screen) and [http://www.videolan.org/ VLC] (full-screen only).

With 3D Acceleration DISABLED in the VBox settings, the applications work as expected. For example, simplescreenrecorder can preview and record what is on the screen with no problems. Of course, CPU usage is considerably higher for most simple operations.

With 3D Acceleration ENABLED in the VBox settings, the applications appear to run correctly, with no errors reported in any logs, however the preview and recordings are blank/black. Occasionally (not always reproducible) the recording is of the generic default Unity background/splash screen, with the words Ubuntu 15.10 in the bottom left, even though this is NOT my selected window background.

I'm not sure if this is a bug, per se, or is a configuration issue.

This APPEARS similar to the problem reported [https://forums.virtualbox.org/viewtopic.php?f=3&t=75795&p=352596&hilit=video+recording here], but everything else 3D appears to work OK. For example, glxgears runs fine and gets about 450 FPS. I do not use any specific 3D apps, however the user interface (Unbuntu Unity) has serious performance issues without basic 3D support...

Other than downgrading VirtualBox to lower than 4.3.28 as had been suggested in the linked forum post, is there a configuration that would enable video capture from within the client OS?

Host: Windows 10
Guest: Ubuntu 15.10

{{{
$ uname -r
4.2.0-30-generic
}}}

{{{
$/usr/lib/nux/unity_support_test -p 
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string:   Humper
OpenGL renderer string: Chromium
OpenGL version string:  2.1 Chromium 1.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+:       yes

Unity 3D supported:       yes
}}}

{{{
$ glxinfo
name of display: :0
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: Chromium
server glx version string: 1.3 Chromium
server glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
client glx vendor string: Chromium
client glx version string: 1.3 Chromium
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
GLX version: 1.3
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
OpenGL vendor string: Humper
OpenGL renderer string: Chromium
OpenGL version string: 2.1 Chromium 1.9
OpenGL shading language version string: 4.40
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, 
    GL_ARB_fragment_shader, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object, 
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shader_objects, 
    GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shadow, 
    GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_compression, GL_ARB_texture_cube_map, 
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine, 
    GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, 
    GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, 
    GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, 
    GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, 
    GL_ATI_texture_mirror_once, GL_CR_bounding_box, GL_CR_cursor_position, 
    GL_CR_head_spu_name, GL_CR_performance_info, GL_CR_print_string, 
    GL_CR_readback_barrier_size, GL_CR_saveframe, GL_CR_server_id_sharing, 
    GL_CR_server_matrix, GL_CR_state_parameter, GL_CR_synchronization, 
    GL_CR_tile_info, GL_CR_tilesort_info, GL_CR_window_size, 
    GL_EXT_blend_color, GL_EXT_blend_equation_separate, 
    GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_compiled_vertex_array, GL_EXT_draw_range_elements, 
    GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_object, 
    GL_EXT_multi_draw_arrays, GL_EXT_secondary_color, GL_EXT_shadow_funcs, 
    GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, 
    GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, 
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, 
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
    GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, 
    GL_IBM_texture_mirrored_repeat, GL_NV_texgen_reflection, 
    GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp
}}}

{{{
$ cat /var/log/Xorg.0.log
[    48.883] 
X.Org X Server 1.17.2
Release Date: 2015-06-16
[    48.883] X Protocol Version 11, Revision 0
[    48.883] Build Operating System: Linux 3.13.0-68-generic x86_64 Ubuntu
[    48.883] Current Operating System: Linux redacted-VBox 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26 UTC 2016 x86_64
[    48.883] Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[    48.883] Build Date: 12 November 2015  05:33:29PM
[    48.883] xorg-server 2:1.17.2-1ubuntu9.1 (For technical support please see http://www.ubuntu.com/support) 
[    48.883] Current version of pixman: 0.32.6
[    48.883] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    48.883] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    48.883] (==) Log file: ""/var/log/Xorg.0.log"", Time: Fri Feb 26 08:22:28 2016
[    48.975] (==) Using system config directory ""/usr/share/X11/xorg.conf.d""
[    49.048] (==) No Layout section.  Using the first Screen section.
[    49.048] (==) No screen section available. Using defaults.
[    49.048] (**) |-->Screen ""Default Screen Section"" (0)
[    49.048] (**) |   |-->Monitor ""<default monitor>""
[    49.048] (==) No monitor specified for screen ""Default Screen Section"".
	Using a default monitor configuration.
[    49.048] (==) Automatically adding devices
[    49.048] (==) Automatically enabling devices
[    49.048] (==) Automatically adding GPU devices
[    49.120] (WW) The directory ""/usr/share/fonts/X11/cyrillic"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.120] (WW) The directory ""/usr/share/fonts/X11/100dpi/"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.120] (WW) The directory ""/usr/share/fonts/X11/75dpi/"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.129] (WW) The directory ""/usr/share/fonts/X11/100dpi"" does not exist.
[    49.129] 	Entry deleted from font path.
[    49.129] (WW) The directory ""/usr/share/fonts/X11/75dpi"" does not exist.
[    49.129] 	Entry deleted from font path.
[    49.129] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[    49.129] (==) ModulePath set to ""/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules""
[    49.129] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    49.137] (II) Loader magic: 0x560d34f1ed40
[    49.137] (II) Module ABI versions:
[    49.137] 	X.Org ANSI C Emulation: 0.4
[    49.137] 	X.Org Video Driver: 19.0
[    49.137] 	X.Org XInput driver : 21.0
[    49.137] 	X.Org Server Extension : 9.0
[    49.138] (II) xfree86: Adding drm device (/dev/dri/card0)
[    49.142] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/134217728
[    49.148] (II) LoadModule: ""glx""
[    49.303] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    49.540] (II) Module glx: vendor=""X.Org Foundation""
[    49.540] 	compiled for 1.17.2, module version = 1.0.0
[    49.540] 	ABI class: X.Org Server Extension, version 9.0
[    49.540] (==) AIGLX enabled
[    49.540] (==) Matched vboxvideo as autoconfigured driver 0
[    49.540] (==) Matched vboxvideo as autoconfigured driver 1
[    49.540] (==) Matched modesetting as autoconfigured driver 2
[    49.540] (==) Matched fbdev as autoconfigured driver 3
[    49.540] (==) Matched vesa as autoconfigured driver 4
[    49.540] (==) Assigned the driver to the xf86ConfigLayout
[    49.540] (II) LoadModule: ""vboxvideo""
[    49.540] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo_drv.so
[    49.557] (II) Module vboxvideo: vendor=""Oracle Corporation""
[    49.557] 	compiled for 1.17.0, module version = 1.0.1
[    49.557] 	Module class: X.Org Video Driver
[    49.557] 	ABI class: X.Org Video Driver, version 19.0
[    49.557] (**) Load address of symbol ""VBOXVIDEO"" is 0x7fdae5a3f340
[    49.557] (II) LoadModule: ""modesetting""
[    49.557] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    49.572] (II) Module modesetting: vendor=""X.Org Foundation""
[    49.572] 	compiled for 1.17.2, module version = 1.17.2
[    49.572] 	Module class: X.Org Video Driver
[    49.572] 	ABI class: X.Org Video Driver, version 19.0
[    49.572] (II) LoadModule: ""fbdev""
[    49.572] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    49.590] (II) Module fbdev: vendor=""X.Org Foundation""
[    49.590] 	compiled for 1.17.1, module version = 0.4.4
[    49.590] 	Module class: X.Org Video Driver
[    49.590] 	ABI class: X.Org Video Driver, version 19.0
[    49.590] (II) LoadModule: ""vesa""
[    49.590] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    49.593] (II) Module vesa: vendor=""X.Org Foundation""
[    49.593] 	compiled for 1.17.1, module version = 2.3.4
[    49.593] 	Module class: X.Org Video Driver
[    49.593] 	ABI class: X.Org Video Driver, version 19.0
[    49.593] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    49.593] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    49.593] (II) FBDEV: driver for framebuffer: fbdev
[    49.593] (II) VESA: driver for VESA chipsets: vesa
[    49.593] (++) using VT number 7

[    49.605] (WW) Falling back to old probe method for modesetting
[    49.605] (WW) Falling back to old probe method for fbdev
[    49.605] (II) Loading sub module ""fbdevhw""
[    49.605] (II) LoadModule: ""fbdevhw""
[    49.605] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    49.607] (II) Module fbdevhw: vendor=""X.Org Foundation""
[    49.607] 	compiled for 1.17.2, module version = 0.0.2
[    49.607] 	ABI class: X.Org Video Driver, version 19.0
[    49.607] (EE) open /dev/fb0: No such file or directory
[    49.607] (WW) Falling back to old probe method for vesa
[    49.607] (II) VBoxVideo(0): VirtualBox guest additions video driver version 5.0.15r105668
[    49.607] (II) Loading sub module ""ramdac""
[    49.607] (II) LoadModule: ""ramdac""
[    49.607] (II) Module ""ramdac"" already built-in
[    49.607] (II) Loading sub module ""fb""
[    49.607] (II) LoadModule: ""fb""
[    49.607] (II) Loading /usr/lib/xorg/modules/libfb.so
[    49.617] (II) Module fb: vendor=""X.Org Foundation""
[    49.617] 	compiled for 1.17.2, module version = 1.0.0
[    49.617] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.617] (II) Loading sub module ""shadowfb""
[    49.617] (II) LoadModule: ""shadowfb""
[    49.636] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[    49.637] (II) Module shadowfb: vendor=""X.Org Foundation""
[    49.637] 	compiled for 1.17.2, module version = 1.0.0
[    49.637] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.637] (II) Loading sub module ""vgahw""
[    49.637] (II) LoadModule: ""vgahw""
[    49.637] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[    49.652] (II) Module vgahw: vendor=""X.Org Foundation""
[    49.652] 	compiled for 1.17.2, module version = 0.1.0
[    49.652] 	ABI class: X.Org Video Driver, version 19.0
[    49.653] (II) Loading sub module ""dri2""
[    49.653] (II) LoadModule: ""dri2""
[    49.653] (II) Module ""dri2"" already built-in
[    49.653] (II) VBoxVideo(0): Creating default Display subsection in Screen section
	""Default Screen Section"" for depth/fbbpp 24/32
[    49.653] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[    49.653] (--) VBoxVideo(0): Virtual size is 32766x32766 (pitch 32766)
[    49.653] (**) VBoxVideo(0):  Built-in mode ""800x600"": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[    49.653] (II) VBoxVideo(0): Modeline ""800x600""x0.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    49.653] (**) VBoxVideo(0):  Built-in mode ""800x600"": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[    49.653] (II) VBoxVideo(0): Modeline ""800x600""x0.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    49.653] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0
[    49.653] (==) VBoxVideo(0): RGB weight 888
[    49.653] (==) VBoxVideo(0): Default visual is TrueColor
[    49.653] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[    49.653] (==) VBoxVideo(0): DPI set to (96, 96)
[    49.653] (II) UnloadModule: ""modesetting""
[    49.653] (II) Unloading modesetting
[    49.653] (II) UnloadModule: ""fbdev""
[    49.653] (II) Unloading fbdev
[    49.653] (II) UnloadSubModule: ""fbdevhw""
[    49.653] (II) Unloading fbdevhw
[    49.653] (II) UnloadModule: ""vesa""
[    49.653] (II) Unloading vesa
[    49.653] (--) Depth 24 pixmap format is 32 bpp
[    50.201] (II) VBoxVideo(0): [DRI2] Setup complete
[    50.201] (II) VBoxVideo(0): [DRI2]   DRI driver: vboxvideo
[    50.221] (II) VBoxVideo(0): Requested monitor count: 1
[    50.221] (II) VBoxVideo(0): Output VGA-0 has no monitor section
[    50.221] (II) VBoxVideo(0): Output VGA-0 has no monitor section
[    50.221] (II) VBoxVideo(0): Printing probed modes for output VGA-0
[    50.221] (II) VBoxVideo(0): Modeline ""1336x790""x60.0   64.09  1336 1338 1340 1342  790 792 794 796 (47.8 kHz Pb)
[    50.222] (II) VBoxVideo(0): Modeline ""2560x1600""x60.0  247.26  2560 2562 2564 2566  1600 1602 1604 1606 (96.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""2560x1440""x60.0  222.63  2560 2562 2564 2566  1440 1442 1444 1446 (86.8 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""2048x1536""x60.0  190.04  2048 2050 2052 2054  1536 1538 1540 1542 (92.5 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1920x1600""x60.0  185.59  1920 1922 1924 1926  1600 1602 1604 1606 (96.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1920x1080""x60.0  125.50  1920 1922 1924 1926  1080 1082 1084 1086 (65.2 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1600x1200""x60.0  116.21  1600 1602 1604 1606  1200 1202 1204 1206 (72.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1680x1050""x60.0  106.82  1680 1682 1684 1686  1050 1052 1054 1056 (63.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1400x1050""x60.0   89.08  1400 1402 1404 1406  1050 1052 1054 1056 (63.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1280x1024""x60.0   79.47  1280 1282 1284 1286  1024 1026 1028 1030 (61.8 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1024x768""x60.0   47.83  1024 1026 1028 1030  768 770 772 774 (46.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""800x600""x60.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""640x480""x60.0   18.84  640 642 644 646  480 482 484 486 (29.2 kHz b)
[    50.222] (II) VBoxVideo(0): Output VGA-0 connected
[    50.222] (II) VBoxVideo(0): Using exact sizes for initial modes
[    50.222] (II) VBoxVideo(0): Output VGA-0 using initial mode 1336x790
[    50.222] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    50.222] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    50.229] (==) VBoxVideo(0): DPMS enabled
[    50.229] (--) RandR disabled
[    50.240] (II) SELinux: Disabled on system
[    50.362] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[    50.362] (II) The file referenced, is *NOT* loaded
[    50.362] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[    50.362] (EE) AIGLX error: vboxvideo does not export required DRI extension
[    50.362] (EE) AIGLX: reverting to software rendering
[    51.108] (II) AIGLX: Loaded and initialized swrast
[    51.108] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    51.109] (II) VBoxVideo(0): Setting screen physical size to 353 x 209
[    51.346] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    51.371] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    51.371] (**) Power Button: Applying InputClass ""evdev keyboard catchall""
[    51.371] (II) LoadModule: ""evdev""
[    51.372] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    51.407] (II) Module evdev: vendor=""X.Org Foundation""
[    51.407] 	compiled for 1.17.1, module version = 2.9.2
[    51.407] 	Module class: X.Org XInput Driver
[    51.407] 	ABI class: X.Org XInput driver, version 21.0
[    51.407] (II) Using input driver 'evdev' for 'Power Button'
[    51.407] (**) Power Button: always reports core events
[    51.407] (**) evdev: Power Button: Device: ""/dev/input/event0""
[    51.407] (--) evdev: Power Button: Vendor 0 Product 0x1
[    51.407] (--) evdev: Power Button: Found keys
[    51.407] (II) evdev: Power Button: Configuring as keyboard
[    51.407] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0""
[    51.407] (II) XINPUT: Adding extended input device ""Power Button"" (type: KEYBOARD, id 6)
[    51.407] (**) Option ""xkb_rules"" ""evdev""
[    51.407] (**) Option ""xkb_model"" ""pc105""
[    51.407] (**) Option ""xkb_layout"" ""us""
[    51.407] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[    51.407] (**) Sleep Button: Applying InputClass ""evdev keyboard catchall""
[    51.407] (II) Using input driver 'evdev' for 'Sleep Button'
[    51.407] (**) Sleep Button: always reports core events
[    51.407] (**) evdev: Sleep Button: Device: ""/dev/input/event1""
[    51.408] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[    51.408] (--) evdev: Sleep Button: Found keys
[    51.408] (II) evdev: Sleep Button: Configuring as keyboard
[    51.408] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1/event1""
[    51.408] (II) XINPUT: Adding extended input device ""Sleep Button"" (type: KEYBOARD, id 7)
[    51.408] (**) Option ""xkb_rules"" ""evdev""
[    51.408] (**) Option ""xkb_model"" ""pc105""
[    51.408] (**) Option ""xkb_layout"" ""us""
[    51.408] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[    51.408] (**) Video Bus: Applying InputClass ""evdev keyboard catchall""
[    51.408] (II) Using input driver 'evdev' for 'Video Bus'
[    51.408] (**) Video Bus: always reports core events
[    51.408] (**) evdev: Video Bus: Device: ""/dev/input/event3""
[    51.408] (--) evdev: Video Bus: Vendor 0 Product 0x6
[    51.408] (--) evdev: Video Bus: Found keys
[    51.408] (II) evdev: Video Bus: Configuring as keyboard
[    51.408] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input4/event3""
[    51.408] (II) XINPUT: Adding extended input device ""Video Bus"" (type: KEYBOARD, id 8)
[    51.408] (**) Option ""xkb_rules"" ""evdev""
[    51.408] (**) Option ""xkb_model"" ""pc105""
[    51.409] (**) Option ""xkb_layout"" ""us""
[    51.409] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event5)
[    51.409] (**) VirtualBox mouse integration: Applying InputClass ""evdev pointer catchall""
[    51.409] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[    51.409] (**) VirtualBox mouse integration: always reports core events
[    51.409] (**) evdev: VirtualBox mouse integration: Device: ""/dev/input/event5""
[    51.409] (--) evdev: VirtualBox mouse integration: Vendor 0x80ee Product 0xcafe
[    51.409] (--) evdev: VirtualBox mouse integration: Found 1 mouse buttons
[    51.409] (--) evdev: VirtualBox mouse integration: Found absolute axes
[    51.409] (--) evdev: VirtualBox mouse integration: Found x and y absolute axes
[    51.409] (--) evdev: VirtualBox mouse integration: Found absolute touchscreen
[    51.409] (II) evdev: VirtualBox mouse integration: Configuring as touchscreen
[    51.409] (**) evdev: VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[    51.409] (**) evdev: VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    51.409] (**) Option ""config_info"" ""udev:/sys/devices/pci0000:00/0000:00:04.0/input/input6/event5""
[    51.409] (II) XINPUT: Adding extended input device ""VirtualBox mouse integration"" (type: TOUCHSCREEN, id 9)
[    51.409] (II) evdev: VirtualBox mouse integration: initialized for absolute axes.
[    51.409] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[    51.409] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[    51.410] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[    51.410] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[    51.410] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event2)
[    51.410] (**) AT Translated Set 2 keyboard: Applying InputClass ""evdev keyboard catchall""
[    51.410] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    51.410] (**) AT Translated Set 2 keyboard: always reports core events
[    51.410] (**) evdev: AT Translated Set 2 keyboard: Device: ""/dev/input/event2""
[    51.410] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    51.410] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    51.410] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    51.410] (**) Option ""config_info"" ""udev:/sys/devices/platform/i8042/serio0/input/input2/event2""
[    51.410] (II) XINPUT: Adding extended input device ""AT Translated Set 2 keyboard"" (type: KEYBOARD, id 10)
[    51.410] (**) Option ""xkb_rules"" ""evdev""
[    51.410] (**) Option ""xkb_model"" ""pc105""
[    51.410] (**) Option ""xkb_layout"" ""us""
[    51.411] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event4)
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass ""evdev pointer catchall""
[    51.411] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: Device: ""/dev/input/event4""
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Vendor 0x2 Product 0x6
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found relative axes
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    51.411] (**) Option ""config_info"" ""udev:/sys/devices/platform/i8042/serio1/input/input5/event4""
[    51.411] (II) XINPUT: Adding extended input device ""ImExPS/2 Generic Explorer Mouse"" (type: MOUSE, id 11)
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[    51.411] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[    51.411] (II) No input driver specified, ignoring this device.
[    51.411] (II) This device may have been added with another device file.
[   130.365] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   132.502] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   132.512] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   146.475] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
}}}

{{{
$ ls -al /usr/lib/xorg/modules/drivers | grep video
lrwxrwxrwx 1 root root      65 Feb 25 15:26 vboxvideo_drv.so -> /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/vboxvideo_drv_117.so
}}}

{{{
$ ls -al /opt/VBoxGuestAdditions-5.0.15/lib/VBoxGuestAdditions/
total 2096
drwxr-xr-x 2 root root   4096 Feb 23 10:02 .
drwxr-xr-x 3 root root   4096 Feb 23 10:02 ..
-rwxr-xr-x 1 root root   1401 Aug 31 10:12 98vboxadd-xclient
-rwxr-xr-x 1 root root  19152 Feb 23 10:02 mount.vboxsf
-rwxr-xr-x 1 root root 715272 Feb 23 10:02 pam_vbox.so
-rwxr-xr-x 1 root root  15796 Feb 23 10:01 vboxadd
-rwxr-xr-x 1 root root   4535 Feb 23 10:01 vboxadd-service
-rwxr-xr-x 1 root root  22252 Feb 23 10:01 vboxadd-x11
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_13.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_14.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_15.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_16.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_70.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_71.so
-rw-r--r-- 1 root root   9056 Feb 23 10:02 vboxmouse_drv.o
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_110.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_111.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_112.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_113.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_114.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_115.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_116.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_117.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_118.so
-rwxr-xr-x 1 root root  61648 Feb 23 10:02 vboxvideo_drv_13.so
-rwxr-xr-x 1 root root  61648 Feb 23 10:02 vboxvideo_drv_14.so
-rwxr-xr-x 1 root root  65928 Feb 23 10:02 vboxvideo_drv_15.so
-rwxr-xr-x 1 root root  65928 Feb 23 10:02 vboxvideo_drv_16.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_17.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_18.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_19.so
-rwxr-xr-x 1 root root  53184 Feb 23 10:02 vboxvideo_drv_70.so
-rwxr-xr-x 1 root root  53184 Feb 23 10:02 vboxvideo_drv_71.so
-rw-r--r-- 1 root root  61728 Feb 23 10:02 vboxvideo_drv.o
-rwxr-xr-x 1 root root   4509 Aug 20  2015 x11config.sh
}}}



From HOST system, AMD's RADEON SETTINGS app reports the following

{{{

Radeon Settings Version - 2016.0203.1043.19267
Driver Packaging Version - 15.301.1801.1001-160203a-299103E
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1533
Direct3D® Version - 9.14.10.1171
OpenGL® Version - 6.14.10.13417
OpenCL™ Version - 2.0.4.0
AMD Mantle Version - 9.1.10.99
AMD Mantle API Version - Not Available
AMD Audio Driver Version - 10.0.0.2
}}}

VBox.Log and VBoxHardening.Log attached

",Michael
15840,Sound fails with VB 5.1.4 on MacOs 10.11.6(host) and 32 bit Fedora 24 (Guest),other,Linux,VirtualBox 5.1.4,2016-09-27T01:14:36Z,2016-09-27T01:14:36Z,On a clean reboot sound is '''sometimes''' briefly available but  quickly fails.,jerrysVB
15991,Ethernet connection hangs on guest,Windows,Windows,VirtualBox 5.1.6,2016-09-27T11:26:59Z,2016-09-27T11:26:59Z,"Ethernet connection on guest is hanging periodically.
After disconnection/connection back it starts to work again",leonik
15814,Virtualbox closes unexpectedly.,Windows,Linux,VirtualBox 5.1.4,2016-09-27T12:55:22Z,2016-09-27T12:55:22Z,"100% reproducible on my x86 Win7 host. Open attached VM, then ''vm settings -> Storage -> select any controller -> click on the blue thingy (add new stor. controller) on the window's bottom -> choose optical drive or hard disk''. After that the whole vbox gui closes.",tico-tico
15992,"Win10 Host, Ubuntu 16 guest, seamless mode, Multiple Virtual Windows",Windows,Linux,VirtualBox 5.1.6,2016-09-27T15:24:41Z,2016-09-27T15:24:41Z,"I'm running a Windows 10 host with an Ubuntu 16.04 virtual machine. I have been running this in seamless mode which worked well earlier. I'm also running ""Multiple Virtual Windows"" (www.actualtools.com) to switch virtual displays on the host.

With the virtual machine in seamless mode, if I switch to another virtual window and then back, the guest doesn't appear to respond. If I click on something I don't see any result, but if I then switch out of seamless mode, I see that the action was in fact taken, just that the display didn't update.

I went back to the Ubuntu 14.04 VM and get the same problem, so it could be a recent update to VirtualBox or something with Multiple Virtual Windows that caused the issue.

",N8DNX
15989,Guru Meditation error,Windows,Windows,VirtualBox 5.0.2,2016-09-27T20:14:56Z,2016-09-27T20:14:56Z,"Hi. I have built 2 test VMs using virtualbox. But, when I have one VM opened and trying to start another one, it throws me the attached Guru meditation error.

I'm new to virtualbox, so request you to guide me in this regard & solve the issue.


Thanks!",RJD
15993,VB 5.1.6 + Solaris 11.3 + SunRay + Multihead + Fullscreen = only first monitor shown,Solaris,Windows,VirtualBox 5.1.6,2016-09-27T20:58:25Z,2016-09-27T20:58:25Z,"When going to fullscreen using VirtualBox 5.1.6 on Solaris 11.3 using SunRay on a multihead Windows 7 instance, only the first (left) screen is drawn. Going back to windowed mode produces the remaining screens.",Marty
15994,Guest additions detect GB as KB and claims about too less free space,Linux,Linux,VirtualBox 5.1.6,2016-09-27T22:07:04Z,2016-09-27T22:07:04Z,"On installing the guest additions on Android 4.4 I'm getting these errors:

{{{
Uncompressing VirtualBox 5.1.6 Guest Additions for Linux-kP: No such file or directory
mnt/VBoxLinuxAdditions.run[367]: 7.2G: unexpected '.'

Not enough space left in /data/local/tmp (7.2G KB) to decompress mnt/VBoxLinuxAdditions.run (7912 KB)
Consider setting TMPDIR to a directory with more free space.
}}}",Sworddragon
15995,Video corruption with gengradd.dll from OS/2 guest additions,Linux,other,VirtualBox 5.1.6,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
13466,VBox 4.3.16 dies when laptop w/ external monitor undocks,other,other,VirtualBox 4.3.16,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
12087,VirtualBox.exe fails to run,Windows,all,VirtualBox 4.2.18,2016-09-28T10:54:18Z,2016-09-28T10:54:18Z,"VirtualBox.exe failed with the message:[[BR]]
Callee RC: E_NOINTERFACE (0x80004002)[[BR]]

VBoxSVC.log reports:[[BR]]
Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false[[BR]]

Running as administrator -> no error[[BR]]

Previous version (4.2.16) does not have this issue.",yefkov
15997,Auto-resize Guest Display greyed out,Windows,Windows,VirtualBox 5.1.6,2016-09-28T11:25:31Z,2016-09-28T11:25:31Z,"I have installed VirtualBox 5.1.6 on a Windows 10 Pro Host. The Guest System is Windows 7 Ultimate. GuestAdditions installed.

Mouse integration and Drag and Drop works fine but Auto-resize Guest Display is greyed out.

Tentatively I have installed the Guest Additions Testbuild.


Stefan",StefanPreuss
15996,MacOS 10.12 Bridge sends bad chksum,Mac OS X,Linux,VirtualBox 5.1.6,2016-09-28T15:40:18Z,2016-09-28T15:40:18Z,"Hello,

i have a special configuration and the shinny new macos 10.12. So It could be that macos is the cause of this error too.

I'm running 5.1.6 on 10.12 macos and installed a own bridge on macos with:
{{{
ifconfig bridge0 create
ifconfig bridge0 10.24.1.1/24 up
ifconfig bridge0 inet6 fd00::10:24:1:1/64 up
}}}
than I bind my guest to these bridge0 and on ipv4 all is good but on ipv6 ping's are working
but any tcp or udp doesn't. 
The root cause is that the guest host receives packet with a wrong checksum:
{{{
1	0.000000	fd00::10:24:1:1	fd00::10:24:1:201	TCP	98	53596→22 [SYN, ECN, CWR] Seq=0 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 MSS=1440 WS=32 TSval=497945749 TSecr=0 SACK_PERM=1
}}}
If add another guest to that bridge and try so access my dest from these new (""linux"") guest everything is ok. Like:
{{{
1	0.000000	fd00::10:24:1:149	fd00::10:24:1:201	TCP	94	45678→22 [SYN] Seq=0 Win=28800 Len=0 MSS=1440 SACK_PERM=1 TSval=301306 TSecr=0 WS=128
}}}
I was not able to check the chksum generation if i plugin a real device to the macos bridge.

And i did not have these ipv6 use case days before where i had run 10.11, so this problem might be new or old from virtualbox or macos ...
I decided to report to you out of the fact that you are not manage the bridges on macos like on linux where you add a virtual device to the bridge. This is a kind of odd-:)

Cheers
meno

P.S.
{{{
$ ifconfig bridge0
bridge0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 7a:31:c1:9c:ed:00
	inet 10.24.1.1 netmask 0xffffff00 broadcast 10.24.1.255
	inet6 fe80::7831:c1ff:fe9c:ed00%bridge0 prefixlen 64 scopeid 0x8
	inet6 fd00::10:24:1:1 prefixlen 64
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	Address cache:
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
}}}",Meno Abels
16000,Can't start VM,Windows,Windows,VirtualBox 5.1.6,2016-09-28T15:47:54Z,2016-09-28T15:47:54Z,Can't start VM due to hardening complaints of Sophos AV,ak11
15689,Some time the guest crash,Windows,Windows,VirtualBox 5.1.2,2016-09-28T21:14:07Z,2016-09-28T21:14:07Z,"Host: Windows 7 x64 professional SP1 with all other updates; 32 GB of RAM; processor Intel I7.

Guest: Windows 7 x64 Ultimate SP1.

Some time the guest crash with a messagebox (image attached).

I attach also VBox.log

",bmn
16005,Missing newline(s) in VBManager VM Description,Linux,all,VirtualBox 5.1.6,2016-09-30T10:28:35Z,2016-09-30T10:28:35Z,"Hello!
There is small problem with Debian GNU/Linux 8 amd64 with Oracle VM VirtualBox Manager v5.1.6 from Oracle repository, but probably problem exist for all platforms.

Reproduce steps:
create any virtual machine in VM Manager, Ctrl-S on it, General -> Description, then enter a few lines with newline between them, press OK.

When user clicks on the machine Details -> Descriptions all lines are displayed together, missing new line.

Here is screenshot attached with problem.",maestro
16006,virutal machine paused with clonezilla,Windows,Linux,VirtualBox 5.0.24,2016-09-30T10:32:21Z,2016-09-30T10:32:21Z,"when i'm trying to clone from a vmdk image to a physical disk, the virtual box pause itself with warning when clonezilla has written the partition table to the new disk and ""informing the OS of partition table changes...""

The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Fehler ID: 
BLKCACHE_IOERR
Dringlichkeit:
Normaler Fehler
",mholzer
16012,Second Monitor disappears,Linux,Windows,VirtualBox 5.1.6,2016-10-02T16:44:02Z,2016-10-02T16:44:02Z,"Second monitor goes black a couple times a day. Unknown trigger. Can be brought back from black screen by pressing Ctrl-F twice (in and out of fullscreen) or by going into the Windows guest resolution properties and slightly adjusting the alignment of the monitor and applying.

Black screen is still in Guest realm as meta windows key still launches guest start menu in the working 1st monitor.

Host Ubuntu 14.04
Guest Windows 7

Very similar to defect #15448 but that one has Host as Win 10, and talks about the taskbar in the host not showing the correct number of instances. In my case in fullscreen the correct number of instances are shown in the host taskbar.",msorel
16017,Only one CPU usable Windows 10 Hyper-V Bug,Windows,Linux,VirtualBox 5.1.6,2016-10-03T09:44:02Z,2016-10-03T09:44:02Z,"Suddenly I couldn't select the amount of cpus to offer to a newly created virtual machine. Even old ones had only one cpu and wouldn't start anymore. 

The issue seems to be related to a Hyper-V Installation on Windows 10 Pro. When you Install Hyper-V for some reason Virtual Box will be broken

Reproduce

1. Instll Virtual Box as usual on Windows 10 Pro
2. Create a Machine with more than 1 Processor
3. Now activate the Hyper-V Feature from the System Settings Programms and 
   Features dialog
4. Wait for Windows to complete tehe setup
5. Try to change the amound of cpus used by your virtual machine in Virtualbox 

The Feature should be grayed out now

So Hyper-V seems to break VirtualBox by now!

You can re enable the processor feature by uninstalling the Hyper-V feature in Windows 10 Pro

I am not sure if Windows 7 is also afected. Needs Teting",horvan
16019,USB Problem in Windows 7 Gust System,Mac OS X,Windows,VirtualBox 5.1.6,2016-10-03T14:11:43Z,2016-10-03T14:11:43Z,"Dear Sir

I am using macbook Pro 13 inch and have installed Windows 7 using Virtual Box (my current version 5.1.6). I am not able to use my Flash Drives, Printer there is some '''error will using Usb'''.. 
Request to fix my problem.",Sanjeevkumar
16022,"""VBoxManage list usbhost"" misidentifies ""USB version/speed""",Mac OS X,other,VirtualBox 5.1.6,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
16015,All VMs crash on macOS 10.12 with NS_ERROR_FAILURE (0x80004005),Mac OS X,all,VirtualBox 5.1.6,2016-10-03T19:50:54Z,2016-10-03T19:50:54Z,"Hello,
Whenever I launch any of my VMs on macOS 10.12, the VM crashes immediately with NS_ERROR_FAILURE (0x80004005). The whole error given by VirtualBox:

Failed to open a session for the virtual machine OS X Install Test.

The virtual machine 'OS X Install Test' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

No VBox.log file is made, but a Crash Reporter log is given, which I have attached. It mentioned ""Illegal Instruction: 4"" and ""BUG IN CLIENT OF LIBDISPATCH: _dispatch_main_queue_callback_4CF called from the wrong thread"".

Jack",JackMacWindows
16030,Video hints / custom resolutions do not work with Windows 10 guest,other,Windows,VirtualBox 5.0.26,2016-10-05T08:56:13Z,2016-10-05T08:56:13Z,"Host: Win 10, VBox 5.0.26, 3 monitors

Guest: Win 10, 1 monitor

Steps to reproduce: 
1. Add video hints as documented in ""9.8. Advanced display configuration""
(basically a set of custom resolutions) - Even stuff that physical display supports like 1920x1080 (Full HD).
2. Guest with 1 monitor, and Full-screen mode
3. Try to switch to this resolution from guest VM. It's not possible.

Worse yet, guest doesn't detect the resolutions that physical host display supports.

-Technologov, 5.10.2016.",Technologov
16026,"error reuse physical disk after open ""computer management"" console",Windows,Windows,VirtualBox 5.1.6,2016-10-06T09:28:24Z,2016-10-06T09:28:24Z,"If I open ""computer management"" console (in Win 7x64 host), to use the physical disk becomes impossible (io error, write error etc.), guest system becomes unbootable. 
Also to install guest, had to remove pre-existing disk partition. Only then became possible to format it from the guest system.

Is it possible to make a mapped physical drive does not fall off when restart host system?

I used the following command:

cd C:\Program Files\Oracle\VirtualBox

VBoxManage.exe internalcommands createrawvmdk -filename H:\VBoxHDTools\ssd7.vmdk -rawdisk \\.\PhysicalDrive5


",Nick07
16031,Video capture on 4K monitors is broken; bitrate too low producing blurry video,other,other,VirtualBox 5.0.26,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
16033,Cannot attach hard drive to VM on 32-bit Windows 7,Windows,other,VirtualBox 5.1.6,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
15913,Installation of guest additions in Fedora 24 32 bits guest hangs => Linux 4.7 bug,Linux,Linux,VirtualBox 5.0.24,2016-10-06T11:49:28Z,2016-10-06T11:49:28Z,"I am trying to install the guest additions in a fresh installed Fedora 24 32 bits but the VBoxLinuxAdditions.run script hangs.

The !VirtualBox version I am using is 5.0.24, but I have tried to install guest additions 5.1.4, since the former one doesn't compile under kernel 4.7.2 32 bits.

The exact sequence of commands used are:
{{{
# sudo dnf install install gcc cpp kernel-devel kernel-headers kernel-PAE-devel
# sudo wget http://download.virtualbox.org/virtualbox/5.1.4/VBoxGuestAdditions_5.1.4.iso
# sudo mkdir /tmp/vbox
# sudo mount -o loop /home/vagrant/VBoxGuestAdditions_5.1.4.iso /tmp/vbox
# sudo sh /tmp/vbox/VBoxLinuxAdditions.run
}}}

In the last step it hangs after the following messages are shown:
{{{
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.4 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Building Guest Additions kernel modules.
vboxadd.sh: Starting the VirtualBox Guest Additions.
}}}

I have also tried with the latest test build at https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.1.5-110588.iso but the result is the same.

Exactly the same procedure for a Fedora 24 64 bits guest is working fine and the guest installation finishes without problems.

A pstree command shows the following relevant process tree:
{{{
  │   │           └─sudo,30032 sh -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │               └─sh,30033 -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │                   └─sh,30090 ./install.sh /tmp/vbox/VBoxLinuxAdditions.run
  │   │                       └─vboxadd,30253 /opt/VBoxGuestAdditions-5.1.5/init/vboxadd setup
  │   │                           └─modprobe,32361 vboxsf
}}}

So it looks like it is loading the kernel module where the installation hangs.
This is the list of packages I have installed which are relevant to the kernel:
{{{
$ rpm -qa | grep kernel 
kernel-headers-4.7.2-201.fc24.i686
kernel-PAE-modules-4.7.2-201.fc24.i686
abrt-addon-kerneloops-2.8.2-1.fc24.i686
kernel-devel-4.7.2-201.fc24.i686
kernel-PAE-core-4.7.2-201.fc24.i686
kernel-PAE-devel-4.7.2-201.fc24.i686
libreport-plugin-kerneloops-2.7.2-1.fc24.i686
}}}

I have tried to have a look to the stack of the modprobe command:
{{{
#sudo cat /proc/32361/stack 
[<f8edddfd>] rtR0SemEventMultiLnxWait.isra.2+0x36d/0x3c0 [vboxguest]
[<f8edde73>] VBoxGuest_RTSemEventMultiWaitEx+0x23/0x30 [vboxguest]
[<f8eec5db>] VBoxGuest_RTSemEventMultiWait+0x5b/0x60 [vboxguest]
[<f8ed4361>] vgdrvHgcmAsyncWaitCallbackWorker+0xe1/0x220 [vboxguest]
[<f8ed44be>] vgdrvHgcmAsyncWaitCallback+0x1e/0x20 [vboxguest]
[<f8ed6ff1>] VbglR0HGCMInternalConnect+0x111/0x130 [vboxguest]
[<f8ed60a5>] VGDrvCommonIoCtl+0xad5/0x1550 [vboxguest]
[<f8ed2245>] VBoxGuestIDCCall+0x45/0x70 [vboxguest]
[<f8625b4d>] vbglDriverIOCtl+0x2d/0x40 [vboxsf]
[<f8626780>] VbglHGCMConnect+0x50/0xb0 [vboxsf]
[<f8626a8e>] VbglR0SfConnect+0x5e/0x90 [vboxsf]
[<f840b075>] init+0x75/0x1000 [vboxsf]
[<c0402182>] do_one_initcall+0x42/0x170
[<c056e0af>] do_init_module+0x50/0x1a8
[<c04f4c1a>] load_module+0x213a/0x27a0
[<c04f54b1>] SyS_finit_module+0xb1/0x100
[<c040388d>] do_fast_syscall_32+0x8d/0x140
[<c0b3f932>] sysenter_past_esp+0x47/0x75
[<ffffffff>] 0xffffffff

}}}

I don't know if that's useful.

I attach the output of running the installation script with sh -x, but I am afraid it doesn't give much extra information.

I also attach VBoxSVC.log just in case it is useful.

Regards
",cquike
16036,supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED,Windows,other,VirtualBox 5.1.6,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
16034,Connection lost in guest when restart failed due to lack of memory,Windows,Linux,VirtualBox 5.0.26,2016-10-06T12:59:59Z,2016-10-06T12:59:59Z,"Sometimes, at startup, VirtulBox complains about the lack of memory (I didn't write down the exact message) and I have to close the VM and launch it again. Then it works. I don't mean restarting the guest. Just record the state of the machine, close the application and run it again.

This is not a big deal and I assume it is due to a lack of RAM on the host, so nothing VirtualBox can do much about.

The issue is that when I do that, sometimes (maybe each time, I'm not 100% sure this is systematic), I lose the connection.

Rather than restarting the guest, this can be solved by restarting network-manager service:

    systemctl restart network-manager

Not sure what the root-cause is and if VirtualBox is to blame. At least if someone encounters the same issue, a workaround is documented here.

Host: Windows 7
Guest: Linux Debian Jessie

There's nothing specifically related in the VM log.",JerNob
15156,Guest Win10 graphics driver never loads with 3D acceleration enabled on Linux Host,Linux,Windows,VirtualBox 5.0.14,2016-10-06T23:42:31Z,2016-10-06T23:42:31Z,"Hi,

Win10 x64 acceleration has never worked for me, since even before 5.x came out. The boot splash screen works correctly, but when the login screen is supposed to appear, instead I see the cursor cycle endlessly between pointer -> busy -> background busy over a black screen; the login screen never appears.
My guest is entirely up to date and has Oracle (i.e. not Ubuntu) additions 5.0.14 installed; other additions functionality seems to work fine (including guest display resizing if acceleration is disabled).
My host is Ubuntu 15.10 x64 running Oracle Virtualbox 5.0.14. I am using Oibaf's git snapshot mesa+drivers ppa in the given log, but I see exactly the same behaviour using the stable graphics stack. (I'm on Intel 4th gen graphics)
VBox log attached - is there any other information I can provide?",akdor1154
16041,Update wined3d in virtualbox,all,Windows,VirtualBox 5.1.6,2016-10-07T03:46:18Z,2016-10-07T03:46:18Z,"Looks like wined3d in virtualbox has not been updated from 2010.

Today I found someone build newest wined3d based on wine 1.9.20:
http://adolfintel.com/?p=wined3d/index.frag

I tried it on my virtualbox guest, it make some game made by unity3d work well that didn't work before.

Are there any plans to update wined3d in virtualbox?

Regards.",coco@…
16043,The guest mouse cursor have big black shadow bellow,Linux,Linux,VirtualBox 5.1.6,2016-10-07T09:51:09Z,2016-10-07T09:51:09Z,"The guest mouse cursor have big, fat, black shadow bellow. The problem exists both in Windows XP and Windows 7 guests. If I turn off mouse integration, the problem disappears.",mozo
15795,The instruction at 0xd756278e referenced memory at 0x00000010. The memory could not be read.,Windows,Windows,VirtualBox 5.1.2,2016-10-07T14:32:02Z,2016-10-07T14:32:02Z,"This happened twice now with the exact same message.

I don't recognise having done anything particular - if anything, I was browsing in Windows Explorer to the Downloads folder, from the Tree View.

Guest: Windows 7 SP1 x86.
Host: Windows 7 SP1 x64.
",danf84
15981,extension pack does not install on vnc desktop,Linux,all,VirtualBox 5.0.6,2016-10-07T15:08:09Z,2016-10-07T15:08:09Z,"hello.
extension pack does not install when running virtualbox on a vnc virtual desktop.

it does install when using the real, hardware based graphical monitor",mraix
16044,version problem,other,other,VirtualBox 5.1.6,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
16003,"Remove the ""Start after installation"" option from Windows installer",Windows,other,VirtualBox 5.1.6,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
16045,"On later RHEL6.8 kernels, hostonly networks stop working after just a few minutes",Linux,other,VirtualBox 5.1.6,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
11455,"VirtualBox 4.2.6 , Guest freeze / hangs on network load",other,Linux,VirtualBox 4.2.6,2016-10-07T18:06:36Z,2016-10-07T18:06:36Z,"Hi,
   Using VirtualBox 4.2.6 on FreeBSD 8.3 host (64bit), and Debian 7.0 guest with kernel : 3.2.0-4-amd64.

   When doing a large rsync of multi gigabyte file sizes, the Guest completely freezes , 
  - Console is frozen (can't type) 
  - Network is down (ping host unknown)
  
It freezes for about 5 minutes, then the transfer aborts and the machine comes back.

No logs in VBox.log when the condition occurs.
No logs in the Guest messages, kern.log or anything...

I tried all the Network Adapters they all fail at some point from 20 Gigs transferred to 200G.

This happens only with more then 1 CPU, with only one CPU it's stable. (Tested 1, 6 and 12 CPU on Guest) on Host : Xeon(R) CPU E5-2620 

Other possibly useful information : I'm using dm-crypt on the Guest to encrypt incoming traffic, I will test without this to rule it out. 

I also at one time using virt-io had this error log :
virtio_net virtio0: output:id 138 is not a head!

But since it freezes using all the network adapters I assume it's not virtio related...

Any help is appreciated , I will perform any test requested ...


Thank you very much!





 


 ",hexa
15952,virtio slow and have unstable performance when VM have >1 vCPU,Linux,Linux,VirtualBox 5.1.6,2016-10-08T10:33:16Z,2016-10-08T10:33:16Z,"
Hi.

I have DL380 G7, with latest CentOS 6. Also, kernel is upgraded to kernel-lt - 3.10.x. Host have 2 NIC's enabled (configured).

I'm using latest VirtualBox 5.1.x.

Test scenario involves two VM's, and both of them are attached to both host NIC's (bridge). In VM's, both vNIC are set as virtio, and vCPU is set to 1. VM's are Centos 6 also.

Everything works ok - i'm getting >140Mbytes/s on all interfaces (eth0<->eth0 and eth1<->eth1 from VM to VM).

Now, on one of those VM's, increase number of vCPU to 2. Things now start to behave erratic.

For a short time, eth0<->eth0 is ok, and then starts to fluctuate widely - from ~100Kb/s to 50Mb/s. At the same time eth1<->eth1 stays >140Mb/s.

In rare occasion, eth0 can work ok, eth1 poorly.

Changing one of interfaces with Intel (so only one vNIC is virtio) makes things work stable - if eth0 was switched to Intel, it is >20Mb/s, while eth1 stays >140Mb/s.

From this, i would conclude that there is some kind of race condition with virtio when VM uses vCPU>1.

Also, i do not know how to debug this furtherer. Please advise.

Regards,

H.",Hrvoje
16049,Starting the operating system,all,all,VirtualBox 5.1.6,2016-10-08T18:52:48Z,2016-10-08T18:52:48Z,"When i try to start ANY operating system, it says FATAL: No boot medium found! System Halted",DingerToaster220
15696,"The memory could not be ""read""",Windows,Windows,VirtualBox 5.1.2,2016-10-09T20:45:37Z,2016-10-09T20:45:37Z,"Hello,
With new 5.1.2 version, I've got this error:

{{{The instruction at ""0xcc47278e"" referenced memory at ""0x00000010"". The memory could not be ""read"".}}}

This occurs only with a specific software (Movicon 11.4) when I start his runtime. But the error is not report in guest side. This crash Guest and error is reported in host.
",DenisFR
8435,VirtualBox only works with floppy disk images which have a certain filename extension,Linux,other,VirtualBox 4.0.4,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
16056,Button for mini toolbar is present on host taskbar,Linux,all,VirtualBox 5.1.6,2016-10-10T16:17:20Z,2016-10-10T16:17:20Z,"Host: Lubuntu 16.04 x86-64

I have a VM in full-screen mode, with mini toolbar auto-hiding at the top of the screen. When I minimise or Alt-Tab out of the VM so the host desktop is visible, there are two buttons on the host taskbar: one represents the running VM:
""vm_name [Running] - Oracle VM VirtualBox""

The second taskbar button seems to be for the mini toolbar:
""VirtualBox""

Would it be possible to have the mini toolbar *not* have its own taskbar button? It seems useless and just wastes space. Clicking it restores the VM, just like clicking the VM's taskbar button.",Donuts
15754,Sound duplication in headless mode,Windows,Linux,VirtualBox 5.1.2,2016-10-10T21:30:59Z,2016-10-10T21:30:59Z,"When I connect to guest VM which is started in headless mode the sound is played '''both''' on host and on client PCs.
Of course in '''mstsc''' connection option ""Play sound on this PC"" was set.
When I connect with the same connection settings to host PC itself all is fine.",Suncatcher
10057,clipboard integration not working for headless guest,Windows,other,VirtualBox 4.1.8,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
14593,Please add support to more network cards,Linux,Windows,VirtualBox 5.0.2,2016-10-11T03:11:55Z,2016-10-11T03:11:55Z,"Hi!

I'm trying to run Siemens WinAC RTX 2010 on Windows XP SP3 Pro English guest. It installs and works fine, but this software needs some specific network cards to be enabled to work with network. The supported network cards by Siemens WinAC RTX 2010:

Intel Gigabit CT (chip set: Intel I82574L)
Intel 2-Port PCIe (chip set: Intel  I82571EB)
Intel Pro/1000 PL (chip set: Intel 82573L)
Intel Pro/1000 GT (chip set: Intel 82541PI)
Intel Gigabit (chip set:  82571EB) 

But none of these network cards are supported by Virtualbox.

So, Can the Virtualbox development team add support to one or two network cards from this list?",fluisgirardi
16058,rdesktop-vrdp SSL not working,other,all,VirtualBox 5.1.6,2016-10-11T09:05:54Z,2016-10-11T09:05:54Z,"Machine created, self-signed cert already generated.

VM host is running on Solaris OS (Solaris 11.3 SRU ver 11.3.12.4.0), current VBox ver 5.1.51.
Client is linux (Linux orca 4.7.6-1-ARCH #1 SMP PREEMPT Fri Sep 30 19:28:42 CEST 2016 x86_64 GNU/Linux), current VBox ver 5.1.51.

{{{
VBoxManage modifyvm ${vmn} --vrdeproperty ""Security/CACertificate=${certpath}/ca_cert.pem""
VBoxManage modifyvm ${vmn} --vrdeproperty ""Security/ServerCertificate=${certpath}/server_cert.pem""
VBoxManage modifyvm ${vmn} --vrdeproperty ""Security/ServerPrivateKey=${certpath}/server_key_private.pem""
VBoxManage modifyvm ${vmn} --vrdeproperty ""Security/Method=negotiate""

}}}

Issue exactly reproducible on ""production"" build (5.1.6), on any machine (not important which VM Host platform is in use - linux nor solaris).

When trying to connect from linux host (rdesktop-vrdp):

{{{
[ilyxa@orca ~]$ rdesktop-vrdp -uconsole -pconsole snooky-vms:3390
Autoselected keyboard map ru
Connection established using SSL.
^C
[ilyxa@orca ~]$ 

}}}


snip of VBox.log:

{{{
...
00:00:45.519191 VRDP: New connection:
00:00:45.519408 VRDP: Connection opened (IPv4): 1
00:00:45.520340 VRDP: Negotiating security method with the client.
00:00:45.606149 VRDP: Using TLS connection.
00:00:45.606254 VRDP: [/C=RU/L=Rostov/O=Home/CN=Ilya V Tyshchenko/emailAddress=ilyxa@nest.org.ru]
00:00:45.674302 VRDP: Methods 0x00000000
00:00:45.674396 VRDP: Channel: [cliprdr] [1004]. Accepted.
00:00:45.674446 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:00:45.674493 VRDP: Channel: [snddbg] [1006]. Not supported.
00:00:45.674539 VRDP: Channel: [rdpdr] [1007]. Accepted.
00:00:45.950352 VRDP: Client seems to be rdesktop.
00:00:45.950447 VRDP: Logon: orca (192.168.171.50) build 2600. User: [console] Domain: [] Screen: 0
00:00:45.951825 AUTH: User: [console]. Domain: []. Authentication type: [External]
00:00:45.953287 AUTH: external authentication module returned 'access granted'
00:00:45.953309 AUTH: Access granted.
00:00:45.956294 VBVA: VRDP acceleration has been requested.
rdesktop-vrdp is ""hang"" (no output nor connection progress) while hitting Ctrl-C:
00:03:15.483995 VRDP: SSL_read failed.
00:03:15.484161 VRDP: Connection closed: 1
00:03:15.484295 VBVA: VRDP acceleration has been disabled.

}}}

Mean while connection with freerdp over ssl is working fine (xfreerdp).",ilyxa
15990,VirtualBox 5.x CLI cannot display snapshot list while VM is running,Windows,Linux,VirtualBox 5.1.6,2016-10-11T12:04:53Z,2016-10-11T12:04:53Z,"The following command produces an error when executed while the targeted VM is running:

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe snapshot MyLinuxVM list
}}}

The error is as follows:
{{{
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 331 of file VBoxManageSnapshot.cpp
}}}

If the command is executed while the VM is stopped (either suspended or powered off) the command is successful.  I do not have any trouble creating snapshots with VBoxManage while the VM is running.

I had this problem in a previous version (5.0.x) and again when I updated to the latest version (5.1.6).",TastyWheat
15804,5.1x Windows Guest Video Playback 2x speed - No Sound,Linux,Windows,VirtualBox 5.1.4,2016-10-12T03:02:56Z,2016-10-12T03:02:56Z,"Problem: 
With 5.1x if I play back a video in Windows 7 guest then it does not have sound and the video plays back at about 2x speed. This is true in several media players. Also, true in Firefox 47, 48 and Google Chrome 52. So this issue is systemic. Tried disabling 2D and 3D with the same issue. Went through several installs, cold power downs, reboots and many experiments.

Solution:
Uninstall / Purge VirtualBox 5.1x and install 5.0x (5.0.24) and video playback and sound work properly.

Host: Ubuntu 16.04 with all updates
Guest: Windows 7 sp1 with all updates
Graphics Card: Nvidia GeForce GTX 980 4GB
Graphics Driver: 3.57 to 3.67
VirtualBox: 5.1, 5.12 5.14
Motherboard: ASUS Rampage V Extreme
CPU: I7-5820K
Memory: 64GB",JavaDev11
16067,typing OS name in vbox GUI in russian layout - just garbage,Linux,all,VirtualBox 5.1.6,2016-10-13T17:28:16Z,2016-10-13T17:28:16Z,"VirtualBox 5.1.x - all versions
Host type: Debian Linux with LXDE desktop
When I create VM or change its name in VBox GUI using Russian keyboard layout I get strange garbage and I can't delete this symbols.

But I have no problems with VirtualBox 5.0.x and VirtualBox 4.x GUI",amiasnikov
10999,extended error 234 when trying to list directory,Windows,Windows,VirtualBox 4.1.22,2016-10-16T20:04:08Z,2016-10-16T20:04:08Z,"Running host windows 7 64 bit
running guest win xp 32 bit, dos program foxprox doing a command prompt from within the program and a dir of a mapped drive or shared vbox folder

extended error 234 and no directory listing",itguru2
16072,"5.1.6 messed them up, shortkeys, session information window",Mac OS X,Linux,VirtualBox 5.1.6,2016-10-16T22:51:43Z,2016-10-16T22:51:43Z,"Myself is not familiarized with VB's internal architecture, so hard to select proper ""component"".

5.1.6 is the first 5.1 version used with this config.
Host OS X 10.9.5
Guests Ubuntu 64Bits Desktop 16.04 LTS
In prior of this - I guess - 5.0.26 was in use without any probs.
Build 110634 was downloaded and installed few hours ago and still in use this minute.
V.M.s run in full-screen mode.

(A)
Host key combination without effect, short-keys practically not working,
e.g. full-screen shortkey, pause V.M. short key, pop-up menu while in full-screen shortkey
Occasionally host's shortkey for making screenshots on host which doesn't have
anything in common with VB nor with its virtual machines is not working.

(B)
While in full-screen mode opening the Session Information window/dialog works quite differently
as it was before upgrade to 5.1. This dialog gets maximized to full-screen, some other 
white-background window/dialog seems to be opening in its background, closing Session Information dialog leaves some strange screen (grey background) with no function - strange host's workspaces.",Nikc
16073,Unity 8 (Ubuntu 16.10) not working,Mac OS X,Linux,VirtualBox 5.1.6,2016-10-16T23:49:39Z,2016-10-16T23:49:39Z,Virtualbox graphics driver incompatible with Unity 8 Mir. Guest reports incompatible driver immediately upon login and return to main login screen.,ljw1
14634,Win 10 VM dual screen terminates to a single screen,Windows,Windows,,2016-10-17T04:41:11Z,2016-10-17T04:41:11Z,"I am using test build Version 5.0.5 r102814. The win 10 VM loses the second screen intermittently. i have to restart the VM in order to get 2 screens again. The Display setting on the Win 10 VM are as follows:

Video Memory - 256 MB
Monitor Count - 2
Scale Factor - 100%
No 3D or 2D acceleration
no Remote Display
no Video Capture
VM Memory allocated: 3072 MB
VM processors: 2

Current laptop system: Windows 10 Professional
laptop memory 32 GB
",Centurion
15525,Linux host hangs during compiling,Linux,Linux,VirtualBox 5.0.22,2016-10-17T17:48:37Z,2016-10-17T17:48:37Z,I'm compiling LibreOffice on Xubuntu 16.04 guest machine and sometimes (3 freezes - 6 compilings) guest machine freezes. Guest machine is allowed to use 2 cores. I have AMD Phenom II with 4 cores. Host machine - Linux Mint 17.3 (based on ubuntu 14.04),yanp.bugz
16077,"Audio: When undocking a laptop, VirtualBox cannot switch to a different sound output",Windows,other,VirtualBox 5.0.26,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
16065,Cannot create symlink inside shared folder on Windows host,Windows,Linux,VirtualBox 5.1.6,2016-10-18T22:37:51Z,2016-10-18T22:37:51Z,"Symlinks do not work inside a VirtualBox Shared Folder when running on Windows 10 host with a Linux guest (Fedora 24)


{{{
$ mount  | grep vboxsf
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)

$ pwd
/home/vagrant/sync
$ mkdir a
$ ln -s a b
ln: failed to create symbolic link 'b': Protocol error
}}}

Outside shared folder:

{{{
$ cd ..
$ pwd
/home/vagrant
$ mkdir c
$ ln -s c d
$ ls -ld d
lrwxrwxrwx 1 vagrant vagrant 1 Oct 12 20:51 d -> c
}}}

Environment:

{{{
$ uname -a
Linux guest 4.5.7-300.fc24.x86_64 #1 SMP Wed Jun 8 18:12:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ VBoxClient --version
5.1.6r110634

>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" --version
5.1.6r110634
}}}
",g_tirloni
16082,vboxmanage updagega cli crashes guest vboxservice,Windows,Windows,VirtualBox 5.1.8,2016-10-19T13:45:50Z,2016-10-19T13:45:50Z,"I am running v5.1.8 along with the latest guest additions. 
My host is windows 8.1 64bit, my guests are a mixture of windows clients (32 and 64 bit) and a mixture of windows servers (32 and 64 bit) and i have the same issue with all of them.

i can start the vms, issue guestcontrol and guestproperty commands and they all run perfectly. However when i use the command:

{{{vboxmanage.exe guestcontrol ""vm name"" updatega}}}

it sits there waiting to talk to my guest vm and then times out with a bunch of errors about not being able to communicate with the vm.

Example errors are
{{{
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={13a11514-402e-022e-6180-c3944de3f9c8} aComponent={GuestWrap} aText={Could not open guest session: VERR_TIMEOUT}, preserve=false aResultDetail=0
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={13a11514-402e-022e-6180-c3944de3f9c8} aComponent={GuestWrap} aText={Could not open guest session: VERR_NOT_FOUND}, preserve=false aResultDetail=0
}}}
Searching around didnt yield any help and it was only when i looked closely at the guest did i notice that the vBoxService crashed.

I ran the service in the foreground using:

{{{vBoxService.exe -f}}}

and even with verbose does not produce any error in the console window, but does generate the following in the event log:

{{{
Faulting application name: VBoxService.exe, version: 5.1.8.11374, time stamp: 0x5806294f
Faulting module name: VBoxService.exe, version: 5.1.8.11374, time stamp: 0x5806294f
Exception code: 0xc0000005
Fault offset: 0x0004e060
Faulting process id: 0x148
Faulting application start time: 0x01d229ee825251a2
Faulting application path: C:\Windows\System32\VBoxService.exe
Faulting module path: C:\Windows\System32\VBoxService.exe
Report Id: 3496c096-95e2-11e6-b2e6-08002785e35e
}}}


Any help really appreciated to debug and get updating of the guest additions working from the host cli (as it appears a few people are experiencing these issues).



",Southdave
16083,VBox/Devices/EFI/Firmware/VBoxPkg/VBoxVgaDxe/Edid.c:401: bad sizeof ?,other,other,VirtualBox 5.1.8,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
15946,"When upgrading virtualbox, icon is removed from the taskbar and unnecessary desktop shortcut created.",Windows,all,VirtualBox 5.1.6,2016-10-19T20:26:39Z,2016-10-19T20:26:39Z,"OS: Windows 10 64-bit, version 1607, build 14393.105.

VirtualBox Version: Both 5.1.4 and 5.1.6.

When upgrading virtualbox, the icon for virtualbox is removed from it's pinned location on the windows taskbar, and a new icon was added to the desktop.

I normally have desktop icons set to not display, but noticed this errata when going through ""This PC"" -> ""Desktop""
",Samuel Flint
15838,download extension pack dialog displayed over upgrade extension pack dialog,Windows,other,VirtualBox 5.1.4,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
16071,Linux Guest is aborting after some time of inactivity (when afk),Linux,Linux,VirtualBox 5.1.6,2016-10-20T07:39:44Z,2016-10-20T07:39:44Z,"I can start up and work with the guest system (Linux mint xcfe 18 64 bit), but after a while (when I am away from keyboard) the VM aborts.



",Klausss
16087,Virtual Box 5.0.28 prevents Windows 7 Guests from Opening,other,Windows,VirtualBox 5.1.8,2016-10-20T10:07:34Z,2016-10-20T10:07:34Z,"i upgraded VirtualBox  5.0.26 to 5.0.28 on my MacPro Host running macoSiera.
No problem opening my Oracle Linux guest VM s but my 2 Windows 7 64 bit guest VMs failed to open.

I tried removing the Windows VMs and the files and copying over clean backups i maintain however the same Abort error always appeared when i tried to start the Windows machines.

I reinstalled version 5.0.26 Virtual Box and i have no problem opening the Windows 7 guests

I have attached a file with the complete error dump and state of my machine

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}




Failed to open a session for the virtual machine Windows7x64_03

Process:               VirtualBoxVM [782]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               5.0.28 (5.0.28)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [776]
Responsible:           VirtualBoxVM [782]
User ID:               501

Date/Time:             2016-10-20 11:01:53.125 +0200
OS Version:            Mac OS X 10.12 (16A323)
Report Version:        12
Anonymous UUID:        FE311170-EE45-253B-B0E6-8B3C837663FC

Crashed Thread:        32  CAQUEUE

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000001202bc64b
Exception Note:        EXC_CORPSE_NOTIFY

Model: MacBookPro11,3, BootROM MBP112.0138.B17, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.21.171.10.1a16)
Bluetooth: Version 5.0.0f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@194,0,0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
Serial ATA Device: ST6000DX000-1H217Z, 6 TB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
Thunderbolt Device: d2 TBT2 USB3, LaCie, 3, 24.3",dba789
16089,MultiMonitor: Guest mode hints do not accept negative numbers for xOrigin in setModeHint.,Windows,Windows,VirtualBox 5.0.26,2016-10-20T12:26:58Z,2016-10-20T12:26:58Z,"The source of the bug is in VBoxHelpers.cpp (hlpResizeRect)
it attempts to maintain monitor order on display resize by comparing the monitor rectangles after the resize and finding intersections between adjacent (according to the previous monitor order) rectangles.

The problem happens if the monitor order changes - for instance, suppose we have 2 monitors - 0 and 1. 
{{{
---------- ---------
|   0    | |   1   |
---------- ---------
}}}
Suppose monitor 0 is 1024x768 starting at 0,0 and monitor 1 is 800x600 starting at 1024,0.
Suppose we call setvideomodehint with monitor 1 being moved to -1024,0 in order to move it to the left of monitor 0. 

What will happen now is that when we look for monitors X-positive adjacent to monitor 0, we'll find monitor 1.
The current code to check whether the monitors now intersect (post potential resize) is: 
(assume iRect=0 and iNextRect=1)
{{{
int delta = paNewRects[iRect].right - paNewRects[iNextRect].left;
}}}
this will result in 1024 (right of monitor 0) - -1024 (new left of monitor 1) = 2048.
next, 
{{{
        if (delta != 0)
        {
            DDCLOG((""XP intersection right %d left %d, diff %d\n"",
                     paNewRects[iRect].right, paNewRects[iNextRect].left,
                     delta));

            paNewRects[iNextRect].left += delta;
            paNewRects[iNextRect].right += delta;
        }
}}}
since delta != 0, we will now move monitor 1 on the x axis by 2048, which will lead to monitor 1 
being in the exact same location before we tried to move it. 
(-1024 + 2048 = 1024)
and we'll end up with the original monitor layout. 


Note the processing of the mode hint event from line 1689 in the log file.
",GilB
16091,"Update to manual, section 9.31.3:command to enter a password for headless encrypted guests.",all,all,,2016-10-20T14:31:28Z,2016-10-20T14:31:28Z,"The command listed is:


{{{
VBoxManage controlvm ""uuid|vmname"" addencpassword ""id"" ""password"" [--removeonsuspend ""yes|no""]
}}}


To me and another user or three (https://forums.virtualbox.org/viewtopic.php?f=1&t=69251) the ""password"" seems to imply that one should type the password in the command line.

However the section 8 VboxManage controlvm addencpassword instructions say the command is:


{{{
addencpassword <id> <password file>|- [--removeonsuspend <yes|no>]
}}}


If one wants to type the password one puts the hyphen in the command line, like this:


{{{
addencpassword <id> -
}}}


and the command line asks for the password separately.

I suspect the command in section 9.31.3 should read the same as section 8, like this:


{{{
VBoxManage controlvm ""uuid|vmname"" addencpassword ""id"" <password file>|- [--removeonsuspend ""yes|no""]
}}}
",scottgus1bug
16094,Blue Screen of computer when plugging in USB drive,Windows,all,VirtualBox 5.1.8,2016-10-20T15:34:04Z,2016-10-20T15:34:04Z,"If I have any virtual box related program running, whether it is the manager or VM if I plug in a certain USB drive it will blue screen the machine.  The usb drive is an Apricorn Aegis Secure Key: [https://www.cdw.com/shop/products/Apricorn-Aegis-Secure-Key-16-GB-USB-2.0/2544731.aspx?cm_cat=GoogleBase&cm_ite=2544731&cm_pla=NA-NA-APR_DR&cm_ven=acquirgy&ef_id=VoqpAAAAAM2hNEIN:20161020153038:s&gclid=CjwKEAjw1qHABRDU9qaXs4rtiS0SJADNzJiskwfgwH9FOtljO4nsvRtWsa6-g1FSC16RwESXdPa8DhoCVqvw_wcB&s_kwcid=AL!4223!3!61836302419!!!g!18283950120!].  I can get around it by not using the drive when I am using the VM, but if I accidently forget for any reason, it will immediately blue screen my computer as soon as it is plugged in.",jammer2000b
16092,Update to Manual for Detachable Guest Windows,all,all,VirtualBox 5.1.8,2016-10-20T15:55:25Z,2016-10-20T15:55:25Z,"The manual seems light on details on how to use the new Detachable Guest Windows capabilities. There is a mention of the ""Vboxmanage startvm {vmname} --type separate"" command, but there are a lot more nuances. 

Maybe a new section, perhaps under section 1.8, about the Detachable options and how to use the GUI and the command line to turn the window on and off. Perhaps something like this: (editor note, windows-centric info, should be checked for accuracy with other host OS's)

*******************************************************

Guests are usually run with a normal GUI interface window, as shown at the start of section 1.8. 
Starting in Version 5.0, guests can be started with a detachable window, which can be closed while the guest is still running. The guest can also be started headless, without a visible window, but the window can be shown on demand. When the guest runs headless it still calculates its GUI as if there was a window present.

To start a guest with a visible but detachable window, do one of the following:

  * Click the guest then click the dropdown next to the Start button at the top of the manager window, and choose ""Detachable Start""

  * Right-click the guest in the Manager window, and choose ""Start"", then ""Detachable Start""

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type separate"" 
	(see section 8.2 under ""startvm"" and 8.12)

To start a guest without a visible window, do one of the following:

  * Click the guest then click the dropdown next to the Start button at the top, and choose ""Headless Start""

  * Right-click the guest in the Manager window, and choose Start, then ""Headless Start""

  * Hold down Shift on the keyboard, then double-click the guest in the Manager window.

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type headless"" 
	(see section 8.2 under ""startvm"" and 8.12)

To hide the guest's detachable window and leave the guest running:

  * In version 5.0, click the guest window's Close box. Select ""Continue Running in the Background"", then OK.
	(Note that under versions earlier than 5.1, clicking the guest window's Close box pauses the guest. 
	To prevent this pause when hiding the guest's window, upgrade to version 5.1 or later is required.

  * In version 5.1 or later, click the guest window's ""Machine"" menu, then ""Detach GUI"". 
	A custom Host-key combination can be set for ""Detach GUI"" in the Manager window
	under the File menu, Preferences, Input, Virtual Machine tab.

To show the guest's window after it has been hidden:

  * Click the guest then click ""Show"" at the top of the Manager window.

  * Right-click the guest in the Manager window, and choose ""Show""

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type separate"" 
	(see section 8.2 under ""startvm"" and 8.12)

See section 9.31.3 on how to start an encrypted guest in Headless mode.

Things to remember:[[BR]]

At present Detachable mode is experimental.[[BR]]

A guest that is started in Detachable or Headless modes does not have 3D acceleration. [[BR]]

When a guest is started in Normal mode the window cannot be detached.[[BR]]

When a guest is running in Detachable mode and the guest's window has been hidden, the guest does not appear in the taskbar.",scottgus1bug
11889,OpenGL Warning,Windows,Windows,VirtualBox 4.2.14,2016-10-20T17:16:30Z,2016-10-20T17:16:30Z,"{{{
OpenGL Warning: State tracker is being re-initialized..

OpenGL Warning: Assertion failed: g_pAvailableContexts[ctx->id] == ctx, file D:\tinderbox\add-4.2\src\VBox\GuestHost\OpenGL\state_tracker\state_init.c, line 346
}}}

P.S. Nothing was listed in VBox.log",nothx
16096,"with a socks proxy set in gnome, guest OS randomly freeze black screen",Windows,Linux,VirtualBox 5.1.6,2016-10-21T06:22:48Z,2016-10-21T06:22:48Z,"Description of problem:
when a socks proxy is set in gnome, in the guets OS, gnome freezes black screen, randomly without halting the system

Version-Release number of selected component (if applicable):
VitualBox 5.1.6 on Windows7 SP1 64
Fedora 24 4.7.6-200.fc24.x86_64
Gnome ver 3.20.4

Please note:
I'm using VitualBox 5.1.6 on Windows7 SP1 64.
I'm inside a VirtualBox VM where Fedora 24 is my Guest OS.
I installed the VirtualBox Guest Additions ver 5.1.7-110797
I configured the KVM acceleration.
I configured the VM network to Bridged Adapter.
I'm using Snort in Fedora. 

How reproducible:
happens randomly 

Steps to Reproduce:
1. Configure a socks proxy in NetworkManager, in the guest OS

Actual results:
Randomly the screen freeze blank, although the system appears not halted but it is not possible to interact with it


Expected results:


Additional info:
unset the sock proxy all run normally",par7133_2
16098,VirtualBox Version 5.1.8 r111374 (Qt5.6.1) does not remember screen size,other,other,VirtualBox 5.1.8,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
16070,Running Virtualbox over a VNC connection,Linux,Windows,VirtualBox 5.1.6,2016-10-21T15:21:23Z,2016-10-21T15:21:23Z,"Attempting to run a VirtualBox guest over a VNC connection to a Linux host (xfce4 desktop for remote VNC session; Mint 18 / cinnamon desktop for native login). After completing the Windows 7 guest splash screen, the guest session aborts. When logged directly into the host system (no VNC), the guest boots up without issue. The guest can be started remotely in headless mode, and accessed through the emulated RDP interface.  So I believe this has something to do with the guest video/display settings interfacing correctly with VNC or the underlying X-session?
Virtualbox .log file is  attached to this ticket.  Core dump file is available through the dropbox link below:
https://www.dropbox.com/s/b7a799cktnp8trn/core.W7TestMachine-2016-10-13-23-33-47?dl=0",otobyt
4088,Noticeable audio latency,Windows,Linux,VirtualBox 2.2.2,2016-10-22T15:52:58Z,2016-10-22T15:52:58Z,"There is a noticeable delay between when the guest operating system starts to play a sound, and when it actually becomes audible. Perhaps in the range of 100-200 ms--just a guess though, I'm not sure how to time it.

The host is Vista Home Basic x64 and the guest is Debian running Linux 2.6.26.",Sam Morris
16042,"Sound lag. The sound and present actions walk past each other. Arch Linux host, Windows guest",Linux,Windows,VirtualBox 5.1.6,2016-10-22T16:10:53Z,2016-10-22T16:10:53Z,"Since month or two when I take an action sound lags behind. I use heavily GuitarPro 4 and when I press Play, the program start playing as the cursor moves around the notes, but the sound lags behind and the playback  starts approximately 2 seconds after the pressing. When I want to stop playing, the moving cursor, which shows which note is being played at the moment, stops immediately but the sound actually stops after 2 seconds. 

This lag is presented everywhere - for example start a browser and watch video on YouTube - sound and picture walk past each other and the synchronization is lost.

This happens on Arch Linux host and Windows XP, Windows 7 and Windows 10 guests. There is no difference between the different guests. All of the guests have the latest Virualbox Guest Additions 5.1.6 installed.

There has been a discussion about this in https://bbs.archlinux.org/viewtopic.php?id=217686.

Here you are a reference video of the problem:

https://youtu.be/gej7gMwAQug

So the program is completely useless for I don't know which note playing at the moment.",mozo
16100,Win10 graphic adapter driver fails after install 5.1.8+addons,Windows,Windows,VirtualBox 5.1.8,2016-10-24T09:17:23Z,2016-10-24T09:17:23Z,"Host: win7, i7 4770, 1440x2560(portrait)[[BR]]
Guest: Win10, use with 1440x2560(portrait)[[BR]]
[[BR]]
When i trying to install 5.1.8 driver i got black screen with task panel at the bottom, few secods after win10 tells me that cant launch screen driver and will use default microsoft driver with 1280x1024 resolution.[[BR]]
VirtualBox Graphics Adapter for Windows 8+ : device is stopped because error №46",adrenalin86
15706,VBoxClient pidfile no copy paste on second running image.,Windows,Linux,VirtualBox 5.1.2,2016-10-24T13:19:22Z,2016-10-24T13:19:22Z,"The VBoxClient process is making .vboxclient-*.pid files in the users home directory, to prevent from starting it more than ones. But if the users home dir is a nfs shared home dir to multiple virtualbox images the VBoxClient process will see .vboxclient-*.pid files in the users home dir and does not start the VBoxClient in the second virtualbox image. With the result that copy/past is not working on the second image. 

Solution: Don't make the pid files in the users home dir, but in /var/run or elsewhere on the local machine.



",Edwin
1930,The ability to exclude selected USB devices in the setup.,Linux,Windows,VirtualBox 1.6.4,2016-10-24T15:19:14Z,2016-10-24T15:19:14Z,"I have been using VirtualBox for a couple of months now. I have had a couple of occasions where I have attempted to mount a USB flash key by doing a right mouse click selection on the icon in the lower right side of the virtual machine screen, only to accidentally select my USB mouse. This resulted in the inability to use the mouse in either the host system or virtual machine causing me to have to dump out of the GUI with a <alt><ctrl><backspace>. (not good)

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

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

Walt Williams
Boulder, Colorado, USA",Walt L. Williams
16111,Incorrect video output after VirtualBox guest screen resizes (w&w/o guest agent),Linux,all,VirtualBox 5.1.8,2016-10-24T19:09:50Z,2016-10-24T19:09:50Z,"I face with various problems with windows size. I'm awesomewm (tiled wm) user.
So, what happens.
After video mode changed, GUI windows is resized.
Then window output immediately moves to the top left corner (maybe because of tiled wm layout). The rest screen may be filled with the previously placed parts of video output of guest.
The second issue - size of video output. After resize there may be options (when guest addons are installed)
1. Video output it just ok 
2. Screen size bigger then actual window, so scrollbars are drawn. It is bigger exactly on the size of that scrollbars.
3. Screen height equals to the screen height of the smallest screen (when there are more than one display). Currently I face with this issue only with ubuntu as a guest.

[[Image(http://s1.alxchk.me/guest-window-output-garbage-after-resize.png)]]

[[Image(guest-agent-window-resized-to-second-screen-height-01.png)]]

[[Image(guest-agent-window-resized-to-second-screen-height-02.png)]]
",Oleksii
16112,USB Sound Card unuseable in WinXP Guest.,Mac OS X,Windows,VirtualBox 5.0.28,2016-10-25T03:14:37Z,2016-10-25T03:14:37Z,"Trying to use SignaLink USB sound card to import sound into Fldigi for  processing. Data is unusable. Looking at VBox.log I find many USB errors which probably explain the reason the data is unusable. I've tried VBox 5.1.4, 5.1.6 and 5.1.8 as well as 5.0.28 all with the same results.",Cfly
16021,VirtualBox 5.1.x on Windows 2012 and Windows 2016 do not guest additions.,Linux,Windows,VirtualBox 5.1.6,2016-10-25T13:17:56Z,2016-10-25T13:17:56Z,"Извините, что на русском. Вообщем проблема такая: В качестве хостовой машины - Ubuntu 16.04. Запускаю серверные платформы - Windows 2012 Standard и Windows 2016 Standard. Устанавливаю гостевые дополнения - все ставится, но после перезагрузки - сервис запускается, а вот програмка VBoxTray.exe стартует, висит 1-2 минуты и выгружается.
Взял из старых дополнений (от VirtualBox 5.0.26) VBoxTray.exe и заменил им новую, и все заработало. Но это конечно не правильно.
Интиересно, что у меня есть образ Windows 2012 с SQL 2008. Вот в нем работает и от VirtualBox 5.1.6.
Что нужно для нормальной работы дополнений?",Sergey
16107,Random Freeze of Ubuntu 16.04 guest under 16.04 Host,Linux,Linux,VirtualBox 5.1.6,2016-10-25T19:08:40Z,2016-10-25T19:08:40Z,"I encouter random freezes of a 16.04 guest system under a 16.04 host system.

This seems not to be new in the 5.1 versions as I had this problem in previous versions, too. The same guest system was working fine before the update to Ubuntu 16.04 (The box was 14.04 before). 

Unfortunately I do not find a pattern when the box freezes. Sometimes it happens soon after the start of the box, sometimes the box runs stable for 1-2 days. The guest system just freezes. 



",Andreas P
16115,"Insert the information ""cable connected"" into the main window",all,all,VirtualBox 5.1.8,2016-10-25T20:07:51Z,2016-10-25T20:07:51Z,"Hi

 I often work with VMs (from modern.ie site) that have a 90-day-limit and change often the setting ""Cable connected"" at the VM Settings unter Network => Advanced. So i would like to have the information if an cable connected or not at the main window of VirtualBox. (like at the picture)

for example:
{{{
Audio
Host driver: Windows DirectSound
Controller:  ICH AC97

Network
Adapter 1: Intel PRO/1000 T Server (Host-only adapter, 'VirtualBox Host-Only Adapter)
Cable connected / Cable not connected
}}}
",AndreeF94
15874,"VBOX session crashes - aborted - on NAT: DHCP offered IP address. Fixed in the past, reintroduced.",Linux,Windows,VirtualBox 5.1.4,2016-10-27T14:05:46Z,2016-10-27T14:05:46Z,"Hallo

Running Windows 7 guest, hosted in VBox 5.1.4 under Fedora 24. Same problem on RHEL6 and RHEL7.

Session of VM randomly crashes without notice, getting status '''ABORTED'''. No obvious errors in neither Windows not Linux logs. In VBox log, after every crash there is this single message as last one:

'''NAT: DHCP offered IP address 10.0.2.15'''

I've seen same problem beeing solved in much older version of VBox: https://www.virtualbox.org/ticket/13874

I guess the error got reintroduced along the VBox evolution.

Could you please check and fix according to previous solution?

Thanks a lot",Flamestring
16119,Extremely slow text display in safe mode boot with Windows Server 2008 guest,Linux,Windows,VirtualBox 5.1.8,2016-10-27T15:16:49Z,2016-10-27T15:16:49Z,"Host: Lubuntu 16.04 x86-64, Core 2 Duo T9500 CPU
Guest: Windows Server 2008 x86

I created a Windows Server 2008 VM, single CPU, VT-x, no I/O APIC.

It boots normally fine. However if I boot in safe mode (press F8 at startup), text rendering is incredibly slow. It's like a 300 baud modem: each line of text appears slowly. Once the screen is full, it takes ages to redraw the whole screen scrolled up by one line.

I noticed this in the changelog for VirtualBox 2.2.0:
""VMM: ﬁxed extremely slow safe mode booting in e.g. Windows 2008 (VT-x/AMD-V only)""

Could there have been some regression causing that problem to reappear?",Donuts
16117,Kernel Panic on 10.10.1,Mac OS X,Linux,VirtualBox 5.1.8,2016-10-28T06:03:57Z,2016-10-28T06:03:57Z,There is kernel panic when using virtualbox.,Majksner
15901,Copyig files over USB hangs with USB 3 support,Windows,Linux,VirtualBox 5.1.4,2016-10-28T13:16:58Z,2016-10-28T13:16:58Z,"Windows 7 host. 

I copied files from my Kubuntu 16.04.1 to an external tablet via adb push. 

The file I copied is roughly 600 MB. The file takes about 3 minutes to copy from Windows, in VirtualBox Linux Guest the file is still stuck copying after 12 hours. 

I started experiencing this problem since USB 3 support was introduced with VirtualBox 5.0. I do not have this problem with USB 2 enabled. 

My USB port is the following:
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller

I had the problem driver version 1.0.4.225 then upgraded to 1.0.10.255, but had the same problem. 

The external device I am copying to is a Texas Instrument Blaze Tablet. 
",nopaste
16104,Build 5.1.8: Cannon view or hear YouTube videos in various guests (or flash based vid),Windows,all,VirtualBox 5.1.8,2016-10-28T14:48:15Z,2016-10-28T14:48:15Z,"Host: Win 7 64 pro sp1: Guests: 1) ubuntu 16.04 64, 2) win 10 latest fast ring build 64. 

In either guest with all same working settings as 5.1.6 and before, I can use any available browser (chrome, firefox, or native) , bring up YouTube, choose any video, and it ""might"" show the first frame and hang there, or it might now show a frame. This is true for video & audio.

It will not play a video regardless of any other attempts on my part. I don't see anything about it showing up in logs so for now will hold off on including one. 

It just seems like a regression from the last build.

Notes: Ubuntu won't give me a screenshot that contains anything but the screen background regardless of how I select or take it.

I'm going to attempt to put my ""post-screenshot"" log here at the end:


{{{
00:00:24.411887 VMMDev: Guest Log: VBoxService 5.1.8 r111374 (verbosity: 0) linux.amd64 (Oct 18 2016 15:52:41) release log
00:00:24.411907 VMMDev: Guest Log: 00:00:00.000100 main     Log opened 2016-10-22T12:10:54.019610000Z
00:00:24.411970 VMMDev: Guest Log: 00:00:00.000182 main     OS Product: Linux
00:00:24.412011 VMMDev: Guest Log: 00:00:00.000217 main     OS Release: 4.4.0-45-generic
00:00:24.412049 VMMDev: Guest Log: 00:00:00.000248 main     OS Version: #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016
00:00:24.412088 VMMDev: Guest Log: 00:00:00.000278 main     Executable: /opt/VBoxGuestAdditions-5.1.8/sbin/VBoxService
00:00:24.412122 VMMDev: Guest Log: 00:00:00.000279 main     Process ID: 1053
00:00:24.412126 VMMDev: Guest Log: 00:00:00.000280 main     Package type: LINUX_64BITS_GENERIC
00:00:24.413273 VMMDev: Guest Log: 00:00:00.001226 main     5.1.8 r111374 started. Verbose level = 0
00:00:24.419240 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.419266 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.425031 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.425057 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.425063 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.425067 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.433624 VMMDev: Guest Log: 00:00:00.020413 automount vbsvcAutoMountWorker: Shared folder 'XPDrive' was mounted to '/media/sf_XPDrive'
00:00:24.663061 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.663105 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.663112 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.663116 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.678804 VBVA: InfoScreen: [0] @0,0 1592x1029, line 0x18e0, BPP 32, flags 0x1
00:00:24.678851 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.678896 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.678959 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.678974 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.678992 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.680061 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.680061 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.680754 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:24.699300 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.699323 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.699339 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.699403 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:26.240260 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:26.334726 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.649947 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.659948 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:34.756490 VMMDev: Guest Additions capability report: (0x0 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:00:34.756891 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:34.756935 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:34.756945 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:34.756951 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:36.216479 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.216499 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.216506 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.216515 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:36.262052 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.262087 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.262097 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.262106 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:41.700223 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:41.710224 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
}}}

",Papolytic
11475,Shared Folders with OS/2 as guest.,Mac OS X,other,VirtualBox 4.2.6,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
16124,Sudden crash of VirtualBox.exe,Windows,Linux,VirtualBox 5.1.8,2016-10-29T12:18:35Z,2016-10-29T12:18:35Z,"It happens from time to time that the running Virtual Machine suddenly crashes, without any particular action on the guest system other than using it normally.
For example, last time I was just about to enter a search term into the address bar of the Firefox Browser of my Ubuntu 14.04LTE guest system when it crashed. The moment I clicked on the address bar, VirtualBox crashed. This was only one example of many crashes.

Unfortunately, the appearing error message doesn't say much (see attached screenshot) and from the log file I couldn't find an answer either. It looks like it didn't log anything.
",tacarrie
15888,VirtualBox 5.1.0 - 5.1.4 Guest Additions problem in Windows XP Guest,Windows,Windows,VirtualBox 5.1.4,2016-10-29T16:35:03Z,2016-10-29T16:35:03Z,"
Host: Windows 8.1  Pro 64 bit, Intel Core i7-4770K, 16 GB RAM 

Guest: Windows XP SP3, 512 MB RAM, all other settings default.


Problem with guest additions in Windows XP


The guest additions worked properly in VirtualBox 5.0.24 and earlier. In all 5.1 versions (5.1.0 - 5.1.4) the following problems are observed: 

•the guest additions icon does not appear in the system tray;  


•seamless mode is disabled and does not switch; 


•mouse wheel does not response.



I also noticed that VBoxTray process gets started but then terminates in approximately a minute after the start and guest additions icon never appears.


This problem pertains in my virtual machine with Windows XP what I used continuously with Virtual Box 5.0.24 without any problems. 


Other guest OS including Windows 7, 8.1 and 10 do not have this problem.

",batyrulan
12495,Sampling profiling method not usable in Visual Studio 2013,Linux,Windows,VirtualBox 4.3.4,2016-10-30T10:56:59Z,2016-10-30T10:56:59Z,"Windows 7 Enterprise SP1 x86 guest (VM from Microsoft's http://modern.ie/ site), Lubuntu 11.10 x86-64 host. Laptop CPU Intel Core 2 Duo T8100. VM is set to use one CPU core.

I installed Visual Studio 2013 and am trying to use its profiling feature. However the ""sampling"" mode doesn't work. I can launch the executable to be profiled, but on exiting it Visual Studio reports that no samples were captured.

This bug report is to suggest that support for whichever CPU performance counters or timer hardware that Visual Studio profiling uses, be added to VirtualBox.

I found an MSDN blog post about profiliing in virtual environments:
http://blogs.msdn.com/b/mgoldin/archive/2010/01/09/visual-studio-profiler-in-virtual-environment.aspx
That mentions VS 2010, so I assume VS 2012 and VS 2013 have the same issue. According to that post, Visual Studio has specific support for VMWare, Virtual PC and Hyper-V VMs.
""Visual Studio profiler usage on virtual machines was limited so far, as it didn’t support Sampling mode in such environment. I’m glad to note that in Visual Studio 2010 you can sample your applications inside of virtual machines. VMs could be created using either VPC, VMWare of Hyper-V technologies. 
Some hardware is not virtualized, though, and CPU performance counters (that are used by profiler) are, unfortunately, in the list. To overcome the issue, we used a different approach that targets each VM-vendor specifically, and timers that are used in virtual world are not the same as on a raw hardware. Some functionality, however, suffers from lack of CPU performance counters virtualization.""

Also a comment at
   http://serverfault.com/questions/194585/visual-studio-profiler-in-virtual-machine 
mentions that profiling uses the Local APIC timer.
",Donuts
15666,VirtualBox 5.1.0 and 5.1.2 fails to import digitally signed appliance (OVA file),Windows,Linux,VirtualBox 5.1.2,2016-10-30T21:07:22Z,2016-10-30T21:07:22Z,"When attempting to import appliance from ova file, VBoxMAnage.exe fails with:


{{{
C:\Users\...\Downloads>""C:\Program Files\VirtualBox\VBoxManage.exe"" import <path to OVA file>
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Appliance read failed
VBoxManage.exe: error: Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)"" at line 307 of file VBoxManageAppliance.cpp
}}}

Import from GUI ends with error dialog:

{{{
Failed to import appliance <path to OVA file>.

Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed).

Result Code: E_FAIL (0x80004005)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}
}}}

There is no relevant information in logs except:

{{{
00:40:08.764715 ApplRead ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)}, preserve=false aResultDetail=0
}}}


I have seen the same behavior on Windows 7 x64 and Windows 10 x64. On another Windows 7 appliance import finished with information popup stating that certificate cannot be verified. 

The same OVA file can be successfully imported using VirtualBox 5.0.X and software of other vendors. 

Content of ""*.mf"": 

{{{
SHA1(ERA_Appliance-disk1.vmdk)= 44f1d187daa9f6ed129381eec155ece99530bfee
}}}

and content of ""*.cert"":

{{{
SHA1(ERA_Appliance.mf)= 7334b00ada502ae4420c9c01ba5c6baf1809e0539a0ca74da780d00b38c89c8fedc6be81f8d8e2e4626a7e0d1e5c19dae2beaded0abde864584b4b1a8dc80294a42e92960ee40a0065a5dfb06a088b8435690475c14a828256b2137c433f868b0bb284c343e84c55c0bc609ea1269f773cbd24269e98b89a2d98332a0aad49d147f3246d47183ee9bf916a4a0b3a774afa49aa885953e1c4535199c86ac59579d07f02a34a68c466becf471cec3d3de7c46fc859740e3cb7dbc7cf8ece6afecbe2baa4072dbe8e7692e58e8a596f2a76499f7c886ab45281608c22e7e4be47da67800eba89627365febeb40bed86c01b3c1706fffc5685bda2d840c3f1c64169
-----BEGIN CERTIFICATE-----
MIIFTjCCBDagAwIBAgIQHeEN7VQdUec7xIb0kkmINjANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykxMDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAxMCBDQTAeFw0xNjA0MTkw
MDAwMDBaFw0xOTA3MTkyMzU5NTlaMIGvMQswCQYDVQQGEwJTSzERMA8GA1UECBMI
U2xvdmFraWExEzARBgNVBAcTCkJyYXRpc2xhdmExGzAZBgNVBAoUEkVTRVQsIHNw
b2wuIHMgci5vLjE+MDwGA1UECxQ1RGlnaXRhbCBJRCBDbGFzcyAzIC0gTWljcm9z
b2Z0IFNvZnR3YXJlIFZhbGlkYXRpb24gdjIxGzAZBgNVBAMUEkVTRVQsIHNwb2wu
IHMgci5vLjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKW9l/iFn1Y/
BJouXaVLHs6+TlhWgZztdjUWtyuF6FHJaHk8eaU3UbtZJuKzINeg+VLdVCk1O8RN
w2P1XRoDecxb5W2m7rX4sUrBHvYY62G6KDYHxzWYqfCLNkgC8R5gpkKtYHROwg4W
HP0h+OnRBv0ojYoP8q/lNma1pTcABOQVmYVm8Rg7/NaAmqAAquk0n03Y2+y5rfh2
G2FM3xlLzjBocephZeS30ZxkUhm12TnTf9P+0ZB7j0f8V7N9ecZy8NeUaTSWmjkW
czxbwjphePpK9A4xAaca5uoNrvQV4SarnAM1iVJb+zyA/qMRhR78giyfOVQjDGoX
Q2U0XovY/HECAwEAAaOCAV0wggFZMAkGA1UdEwQCMAAwDgYDVR0PAQH/BAQDAgeA
MCsGA1UdHwQkMCIwIKAeoByGGmh0dHA6Ly9zZi5zeW1jYi5jb20vc2YuY3JsMGEG
A1UdIARaMFgwVgYGZ4EMAQQBMEwwIwYIKwYBBQUHAgEWF2h0dHBzOi8vZC5zeW1j
Yi5jb20vY3BzMCUGCCsGAQUFBwICMBkMF2h0dHBzOi8vZC5zeW1jYi5jb20vcnBh
MBMGA1UdJQQMMAoGCCsGAQUFBwMDMFcGCCsGAQUFBwEBBEswSTAfBggrBgEFBQcw
AYYTaHR0cDovL3NmLnN5bWNkLmNvbTAmBggrBgEFBQcwAoYaaHR0cDovL3NmLnN5
bWNiLmNvbS9zZi5jcnQwHwYDVR0jBBgwFoAUz5mp6nsm9EvJjo/X8AUm7+PSp50w
HQYDVR0OBBYEFIKSJNBoZdrPFMTF6cPzFNk4c63aMA0GCSqGSIb3DQEBBQUAA4IB
AQDzz/hCjjc1kc15nqKjnFy/oiRPDhQpM+C5/bputO8q0AE0uUv17DcGuPQgbQsG
7gfDr4x2suxJfxasRBU2OKKWZfpUfuALqIC5oHviD/8UPU3gk8m+LiwgYr13i5sN
ujbBeUaa4WfzrQo+7+GvdfKPw/NpHnmrDSSRadM0AckpyhrLRqMkgVjvIz7t00Yd
AQoBhFvQTaOk/I8iIQqsQcK0qyVbdOJFnO7Wu16XNeSb0TxqFzXCsGoI0qDUCatm
1uDWPzIKL7omFDrKNxxGZhCoJAV4btgZE1Ys6NFWazUa43//lGl11f6pncXv7BQf
sIlwnYi5uqq1MvtD1mV57wWh
-----END CERTIFICATE-----
}}}",koso
16133,Crashes if GUI used with a screen reader,Linux,Linux,VirtualBox 5.1.8,2016-11-01T21:25:38Z,2016-11-01T21:25:38Z,"Hi,

On a Debian testing with upstream repo's package:
1. Install qt-at-spi
2. Enable accessibility in the Desktop.
3. Run VirtualBox.
4. Arrow keys, opening dialogs, crash the graphical interface.
5. Run without Orca running.
6. Arrow keys work. Run again screen reader, it crashes as soon as you press an arrow key.

VBoxManage works, VMs as well, but GUI is unusable.

Best regards",texou
16139,Invisible network adapter in network settings,Windows,all,VirtualBox 5.1.8,2016-11-02T09:09:45Z,2016-11-02T09:09:45Z,"Host: Windows 7 Pro 64 bit, Intel Core i5-2400, 8 GB RAM

Guest: All

Problem:
On windows hosts not all network adapters are visible in dropdown list. 
On a computer with two onboard NICs and one PCI NIC only one of the onboard NICs and the PCI NIC is shown in the list. The second onboard NIC is missing in the list. VirtualBox NDIS6 Bridged Networking Driver is installed and activated for all three adapters. ",KilO76
16136,VirtualBox not detecting VMs started on boot,Windows,Linux,VirtualBox 5.1.8,2016-11-02T23:26:02Z,2016-11-02T23:26:02Z,"I have a server using Microsoft Windows Server 2012 R2, and a virtual machine on it (Debian).

However, I'd like for the virtual machine to be started on boot, without user log in.

So, I used Task Scheduler for this (also tryied nssm and pstools), but no success.

The virtual machine DOES START, however, when I log in and open VirtualBox,
it does not detect the virtual machine running, so it's quite troublesome as I am not planning on RDP or SSH to the guest.

If I do start the VM with VBoxManage while logged in, all works ok.
If I do start the VM with Task Scheduler (admin nor non-admin) it does not work.

I've also reinstalled VirtualBox and ran it without success.",Hario
16140,copy paste is not working,Windows,Windows,VirtualBox 5.1.8,2016-11-02T23:29:54Z,2016-11-02T23:29:54Z,"Yesterday I upgraded my version to 5.1.8 and my copy paste stopped working thru out the windows 10 ver 1607 (OS Build 14393.351). This happens when I have bi-directional clipboard sharing enabled. Once I disable this things go back to normal. This is truly a pain as I have to copy and paste all the time for differnt bugs and event or commands all the time. My guest OS is windows 2012 R2 (all the latest patches are applied on host and guest OSs)

Ctrl+C and Ctrl+V as well as right click copy and paste are acting the same I have tried relauncing clip.exe on host and also cleared out the buffer with cmd \c.. commands nothings works until I disable the clipboard sharing",sys janitor
16143,Trouble attaching Intel HD 530 from linux host to win7 guest via PCI passthrough.,Linux,Windows,VirtualBox 5.1.8,2016-11-03T16:36:20Z,2016-11-03T16:36:20Z,"I have an intel 6600k with HD 530 graphics. z170 chipset.  I have a GTX 1070 running my arch linux host displays.  I would like to use PCI passthrough to attach the intel graphics to the win7 guest.  So I ran the modifyvm --pciattach command with no errors and booted up the guest.  Windows detected the new hardware and downloaded and installed the HD 530 driver.  In device manager, it says the device could not start because there are not enough resources. So I tried disabling the virtualbox display adapter and rebooting.  However when I rebooted, it hard locked my host.  I could not even use the magic sysrq shortcuts to reboot.  I tried two more times shutting down and rebooting the guest, but it hard locks the host every time. I wanted to do further testing to try to get the guest to enable and use the HD 530 card, but I don't want to risk losing data from the hard lockups, so I have stopped testing and detached the device.",walmartshopper12
16144,"Unhelpful feedback ""DrvVD: Configuration error: keys incorrect at level 0""",Linux,Linux,VirtualBox 5.1.8,2016-11-03T17:55:34Z,2016-11-03T17:55:34Z,"Starting a VM which formerly worked fine fails due to
{{{
    DrvVD: Configuration error: keys incorrect at level 0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).
    AHCI: Failed to attach drive to Port0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).


    Fehlercode:
    NS_ERROR_FAILURE (0x80004005)
    Komponente:
    ConsoleWrap
    Interface:
    IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
displayed in dialog after start. It'd be helpful to know what failure occurred for what reason and what are useful steps to proceed. It looks like an error in the configuration file, but it's just too useless to guess if you could improve the feedback.

experienced on Ubuntu 16.10 host with Gentoo guest",krichter
16145,Music is cutt when resizing iTunes,Linux,Windows,VirtualBox 5.1.8,2016-11-03T18:22:30Z,2016-11-03T18:22:30Z,"Hello,
when I resize iTunes 12.5.3 (latest version) in a little windows has the virtualbox, I pause the music and I restart it, the music is cut. As if I put play/pause button in loop.
Also, if I try to listen the radio Beats 1, there is a problem with the audio stream. I have the same problem on Windows 7 and Windows 10. (It's not a iTunes problem because it works with VMware.",CLeBeR
16148,CAINE 8 VGA does not work fine,other,other,VirtualBox 5.1.8,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
15652,PowerDown and DisplayRefresh race condition,Linux,all,VirtualBox 5.0.20,2016-11-04T10:58:38Z,2016-11-04T10:58:38Z,"Sometimes VBoxHeadless crash happens:
{{{
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
33      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.

(gdb) thread apply all bt
Thread 28 (Thread 0x7fdb3da64700 (LWP 6747)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3cfa2472 in VBoxNsprPR_WaitCondVar (cvar=0x6ca700, timeout=4294967295) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptsynch.c:392
#2  0x00007fdb3cfa2702 in VBoxNsprPR_Wait (mon=0x6d4090, timeout=<optimized out>) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptsynch.c:571
#3  0x00007fdb360e3deb in Wait (interval=4294967295, this=0x7fdb3da63de0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/xpcom/threads/nsAutoLock.h:285
#4  DConnectWorker::Run (this=0x6c9fd0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2956
#5  0x00007fdb3cf91607 in nsThread::Main (arg=0x6ca280) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
#6  0x00007fdb3cfa11a7 in _pt_root (arg=0x6d4330) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#7  _pt_iprt_root (Thread=<optimized out>, pvUser=0x6d4330) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#8  0x00007fdb3d312274 in rtThreadMain (pThread=0x6d44a0, NativeThread=140579608872704, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#9  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6d44a0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#10 0x00007fdb3d676184 in start_thread (arg=0x7fdb3da64700) at pthread_create.c:312
#11 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 27 (Thread 0x7fdb05355700 (LWP 6771)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=20000, hEventSem=0x7fdb184a0200) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb184a0200, cMillies=20000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb076397ef in drvACPIPoller (pDrvIns=0x7fdb1849f390, pThread=0x7fdb1849f500) at ../VirtualBox-5.0.20/src/VBox/Devices/PC/DrvACPI.cpp:894
#4  0x00007fdb0763a3f1 in drvACPIPoller (pDrvIns=<optimized out>, pThread=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/PC/DrvACPI.cpp:515
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb1849f660, pvUser=0x7fdb1849f500) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1849f660, NativeThread=140578661947136, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1849f660) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb05355700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 26 (Thread 0x7fdb3d941700 (LWP 6818)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb28007cd0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb28007cd0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb35545451 in videoRecThread (Thread=<optimized out>, pvUser=0x7fdb280087f0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/VideoRec.cpp:397
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb28008d30, NativeThread=140579607680768, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb28008d30) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d941700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 25 (Thread 0x7fdb3d8c0700 (LWP 6752)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=2000, hEventSem=0x7fdb20003600) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb20003600, cMillies=2000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3548f0fd in waitRemoteUSBThreadEvent (cMillies=2000, this=0x7fdb280070a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleVRDPServer.cpp:3070
#4  threadRemoteUSB (self=<optimized out>, pvUser=0x7fdb280070a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleVRDPServer.cpp:3047
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20003670, NativeThread=140579607152384, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20003670) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d8c0700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 24 (Thread 0x7fdb054d8700 (LWP 6768)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d39a031 in SUPR3CallVMMR0Ex (pVMR0=<optimized out>, idCpu=<optimized out>, uOperation=<optimized out>, u64Arg=<optimized out>, pReqHdr=0x7fdb054d7cd0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLib.cpp:683
#3  0x00007fdb341beba1 in pdmR3DrvHlp_SUPCallVMMR0Ex (pDrvIns=0x7fdb25eb81c0, uOperation=52, pvArg=0x7fdb054d7cd0, cbArg=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMDriver.cpp:1437
#4  0x00007fdb0763677a in PDMDrvHlpSUPCallVMMR0Ex (cbArg=24, pvArg=0x7fdb054d7cd0, uOperation=52, pDrvIns=0x7fdb25eb81c0) at ../VirtualBox-5.0.20/include/VBox/vmm/pdmdrv.h:1736
#5  drvR3IntNetRecvRun (pThis=pThis@entry=0x7fdb25eb8280) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:856
#6  0x00007fdb07637487 in drvR3IntNetRecvThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb8280) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:904
#7  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb184445a0, NativeThread=140578663532288, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#8  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb184445a0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#9  0x00007fdb3d676184 in start_thread (arg=0x7fdb054d8700) at pthread_create.c:312
#10 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 23 (Thread 0x7fdb3da85700 (LWP 6746)):
#0  0x00007fdb3c6fdfdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3cfa4427 in poll (__timeout=-1, __nfds=2, __fds=0x7fdb3da84b90) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _pr_poll_with_poll (pds=0x6c8ea8, npds=2, timeout=4294967295) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptio.c:3906
#3  0x00007fdb3cfa6070 in VBoxNsprPR_Poll (pds=<optimized out>, npds=<optimized out>, timeout=<optimized out>)
    at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptio.c:4308
#4  0x00007fdb360e67df in ConnThread (arg=0x6c8ea0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/ipc/ipcd/client/src/ipcConnectionUnix.cpp:336
#5  0x00007fdb3cfa11a7 in _pt_root (arg=0x6c91b0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#6  _pt_iprt_root (Thread=<optimized out>, pvUser=0x6c91b0) at ../VirtualBox-5.0.20/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#7  0x00007fdb3d312274 in rtThreadMain (pThread=0x6c9320, NativeThread=140579609007872, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#8  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6c9320) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#9  0x00007fdb3d676184 in start_thread (arg=0x7fdb3da85700) at pthread_create.c:312
#10 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 22 (Thread 0x7fdb05126700 (LWP 6854)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb342c24ef in pdmR3R0CritSectEnterContended (pCritSect=0x7fdb240473c8, hNativeSelf=140578659657472, pSrcPos=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp:172
#5  0x00007fdb075ca22a in vgaPortSetRenderVRAM (pInterface=0x7fdb24044e10, fRender=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:5315
#6  0x00007fdb35496ed3 in Display::i_handleDisplayResize (this=this@entry=0x7fdb28003a00, uScreenId=uScreenId@entry=0, bpp=bpp@entry=32, pvVRAM=0x7fdb05701000, cbLine=4608, w=1152, h=864, flags=1)
    at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:911
#7  0x00007fdb354982b5 in Display::i_notifyPowerDown (this=0x7fdb28003a00) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1557
#8  0x00007fdb3544f060 in Console::i_powerDown (this=0x7fdb28001180, aProgress=0x7fdb280083a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleImpl.cpp:7630
#9  0x00007fdb35450358 in Console::i_powerDownThread (Thread=<optimized out>, pvUser=0x7fdb28008210) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/ConsoleImpl.cpp:10074
#10 0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb29978920, NativeThread=140578659657472, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#11 0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb29978920) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#12 0x00007fdb3d676184 in start_thread (arg=0x7fdb05126700) at pthread_create.c:312
#13 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 21 (Thread 0x7fdb3da43700 (LWP 6748)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=30000, hEventSem=0x6d7960) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x6d7960, cMillies=30000) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb354bdce7 in VirtualBoxClient::SVCWatcherThread (ThreadSelf=<optimized out>, pvUser=0x6d6560) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/VirtualBoxClientImpl.cpp:284
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x6d79d0, NativeThread=140579608737536, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x6d79d0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3da43700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 20 (Thread 0x7fdb053d6700 (LWP 6770)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d394a11 in rtSemEventMultiPosixWaitTimed (pThis=0x7fdb1849e030, fFlags=<optimized out>, uTimeout=<optimized out>, pSrcPos=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:562
#2  0x00007fdb07668509 in ohciR3ThreadFrame (pDevIns=<optimized out>, pThread=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/DevOHCI.cpp:3977
#3  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb1849e300, pvUser=0x7fdb1849e1a0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1849e300, NativeThread=140578662475520, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1849e300) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb053d6700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 19 (Thread 0x7fdb3d9c2700 (LWP 6749)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007fdb3d3942b5 in rtSemEventWait (fAutoResume=true, cMillies=999, hEventSem=0x7fdb2800e3e0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:479
#2  RTSemEventWait (hEventSem=0x7fdb2800e3e0, cMillies=999) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3d360953 in rtTimerLRThread (hThreadSelf=<optimized out>, pvUser=0x7fdb2800e390) at ../VirtualBox-5.0.20/src/VBox/Runtime/generic/timerlr-generic.cpp:341
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb2800bfd0, NativeThread=140579608209152, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb2800bfd0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb3d9c2700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 18 (Thread 0x7fdb052d4700 (LWP 6772)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb184a05f0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb184a05f0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb075b6d8e in usbHidUrbReap (pUsbIns=0x7fdb184a0320, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Devices/Input/UsbMouse.cpp:1686
#4  0x00007fdb07673aea in vusbUrbDoReapAsyncDev (pDev=0x7fdb184a3530, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/VUSBUrb.cpp:2067
#5  0x00007fdb0766aeb3 in vusbDevUrbIoThread (hThread=<optimized out>, pvUser=0x7fdb184a3530) at ../VirtualBox-5.0.20/src/VBox/Devices/USB/VUSBDevice.cpp:1155
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb184a4400, NativeThread=140578661418752, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb184a4400) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb052d4700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7fdb36aef700 (LWP 6773)):
#0  0x00007fdb3c702c53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb276842fc in ?? () from /usr/lib/x86_64-linux-gnu/libvncserver.so.0
#2  0x00007fdb3d676184 in start_thread (arg=0x7fdb36aef700) at pthread_create.c:312
#3  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7fdb05457700 (LWP 6769)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb0763639d in drvR3IntNetXmitThread (pDrvIns=0x7fdb25eb81c0, pThread=0x7fdb184450f0) at ../VirtualBox-5.0.20/src/VBox/Devices/Network/DrvIntNet.cpp:626
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb18445250, pvUser=0x7fdb184450f0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18445250, NativeThread=140578663003904, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18445250) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb05457700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7fdb340fb700 (LWP 6751)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb20000b10, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb20000a30, ppMsg=ppMsg@entry=0x7fdb340fadf0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483649, ppMsg=ppMsg@entry=0x7fdb340fadf0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553d31b in hgcmThread (ThreadHandle=2147483649, pvUser=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:1812
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb20000a30) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20000c60, NativeThread=140579448010496, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20000c60) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb340fb700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7fdb0563b700 (LWP 6765)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb076ab218 in ahciAsyncIOLoop (pDevIns=<optimized out>, pThread=0x7fdb183aabd0) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevAHCI.cpp:6881
#5  0x00007fdb341c728b in pdmR3ThreadMain (Thread=0x7fdb183eac50, pvUser=0x7fdb183aabd0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:788
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183eac50, NativeThread=140578664986368, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183eac50) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb0563b700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 13 (Thread 0x7fdb24891700 (LWP 6761)):
#0  0x00007fdb3c648e3a in do_sigwaitinfo (info=0x7fdb24890d00, set=0x7fdb24890c80) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigwaitinfo.c:54
#1  __GI___sigwaitinfo (set=0x7fdb24890c80, info=0x7fdb24890d00) at ../nptl/sysdeps/unix/sysv/linux/../../../../../sysdeps/unix/sysv/linux/sigwaitinfo.c:81
#2  0x00007fdb3d391d55 in rttimerThread (hThreadSelf=<optimized out>, pvArg=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/timer-posix.cpp:373
#3  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18354fc0, NativeThread=140579187529472, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#4  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18354fc0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#5  0x00007fdb3d676184 in start_thread (arg=0x7fdb24891700) at pthread_create.c:312
#6  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 12 (Thread 0x7fdb0718e700 (LWP 6763)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0042f0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c004470, ppMsg=ppMsg@entry=0x7fdb0718ddf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483689, ppMsg=ppMsg@entry=0x7fdb0718ddf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483689, pvUser=0x7fdb1c0043a0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c004470) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c004630, NativeThread=140578693637888, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c004630) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb0718e700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7fdb05700700 (LWP 6764)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb183a5960)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb183a5960, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb343186df in pdmacFileAioMgrNormal (hThreadSelf=<optimized out>, pvUser=0x7fdb183a5890) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1626
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183a5e00, NativeThread=140578665793280, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183a5e00) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb05700700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7fdb2629e700 (LWP 6759)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394390 in rtSemEventWait (fAutoResume=true, cMillies=<optimized out>, hEventSem=0x7fdb080013d0)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:383
#2  RTSemEventWait (hEventSem=0x7fdb080013d0, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semevent-posix.cpp:496
#3  0x00007fdb3d30fcee in RTReqQueueProcess (hQueue=0x7fdb08001350, cMillies=4294967295) at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/reqqueue.cpp:127
#4  0x00007fdb262a08fe in guestProp::Service::threadNotifyHost (self=<optimized out>, pvUser=0x7fdb080012d0)
    at ../VirtualBox-5.0.20/src/VBox/HostServices/GuestProperties/service.cpp:1531
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb08001440, NativeThread=140579214845696, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb08001440) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb2629e700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fdb3da87780 (LWP 6744)):
#0  0x00007fdb3c702c53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000000040caab in com::waitForEventsOnXPCOM (pQueue=<optimized out>, cMsTimeout=cMsTimeout@entry=4294967295) at ../VirtualBox-5.0.20/src/VBox/Main/glue/NativeEventQueue.cpp:348
#2  0x000000000040cfcc in com::NativeEventQueue::processEventQueue (this=0x6c3af0, cMsTimeout=cMsTimeout@entry=4294967295)
    at ../VirtualBox-5.0.20/src/VBox/Main/glue/NativeEventQueue.cpp:524
#3  0x0000000000405c68 in TrustedMain (argc=argc@entry=7, argv=<optimized out>, envp=envp@entry=0x7ffd3e0fcf88)
    at ../VirtualBox-5.0.20/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp:1238
#4  0x0000000000403419 in main (argc=7, argv=0x6829f0, envp=0x7ffd3e0fcf88) at ../VirtualBox-5.0.20/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp:1376

Thread 8 (Thread 0x7fdb26a3d700 (LWP 6756)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c000a70, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c000990, ppMsg=ppMsg@entry=0x7fdb26a3cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483651, ppMsg=ppMsg@entry=0x7fdb26a3cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483651, pvUser=0x7fdb1c0008c0) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c000990) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c000bc0, NativeThread=140579222836992, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c000bc0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb26a3d700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7fdb05599700 (LWP 6767)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb075e0678 in ataR3AsyncIOThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb1ae8) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevATA.cpp:5483
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1843eec0, NativeThread=140578664322816, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1843eec0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb05599700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7fdb055ba700 (LWP 6766)):
#0  0x00007fdb3c7021e7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39c78d in suplibOsIOCtl (pThis=<optimized out>, uFunction=<optimized out>, pvReq=<optimized out>, cbReq=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/linux/SUPLib-linux.cpp:184
#2  0x00007fdb3d396dba in supSemOp2 (pSession=<optimized out>, u64Arg=<optimized out>, uOp=0, hSem=<optimized out>, uType=0)
    at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:68
#3  SUPSemEventWaitNoResume (pSession=<optimized out>, hEvent=<optimized out>, cMillies=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/HostDrivers/Support/SUPLibSem.cpp:138
#4  0x00007fdb075e0678 in ataR3AsyncIOThread (ThreadSelf=<optimized out>, pvUser=0x7fdb25eb1350) at ../VirtualBox-5.0.20/src/VBox/Devices/Storage/DevATA.cpp:5483
#5  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb183ee710, NativeThread=140578664457984, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#6  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb183ee710) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#7  0x00007fdb3d676184 in start_thread (arg=0x7fdb055ba700) at pthread_create.c:312
#8  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fdb24810700 (LWP 6762)):
#0  0x00007fdb3d67db9d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fdb3d39189d in RTThreadSleep (cMillies=100) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread2-posix.cpp:82
#2  0x00007fdb34318b5a in pdmR3NsTxThread (pVM=<optimized out>, pThread=0x7fdb18363db0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMNetShaper.cpp:418
#3  0x00007fdb341c73a3 in pdmR3ThreadMain (Thread=0x7fdb18363f10, pvUser=0x7fdb18363db0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/PDMThread.cpp:792
#4  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb18363f10, NativeThread=140579187001088, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#5  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb18363f10) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#6  0x00007fdb3d676184 in start_thread (arg=0x7fdb24810700) at pthread_create.c:312
#7  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fdb267b7700 (LWP 6757)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0018e0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c001800, ppMsg=ppMsg@entry=0x7fdb267b6df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483658, ppMsg=ppMsg@entry=0x7fdb267b6df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483658, pvUser=0x7fdb1c001730) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c001800) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c001a30, NativeThread=140579220190976, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c001a30) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb267b7700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fdb2621d700 (LWP 6760)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c003630, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c003550, ppMsg=ppMsg@entry=0x7fdb2621cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483684, ppMsg=ppMsg@entry=0x7fdb2621cdf8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483684, pvUser=0x7fdb1c003480) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c003550) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c003780, NativeThread=140579214317312, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c003780) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb2621d700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fdb2652a700 (LWP 6758)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fdb3d394892 in rtSemEventMultiPosixWaitIndefinite (pThis=0x7fdb1c0025a0, pSrcPos=<optimized out>, fFlags=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/linux/../posix/semeventmulti-posix.cpp:433
#2  0x00007fdb35539678 in HGCMThread::MsgGet (this=this@entry=0x7fdb1c002720, ppMsg=ppMsg@entry=0x7fdb26529df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:543
#3  0x00007fdb35539e6e in hgcmMsgGet (hThread=hThread@entry=2147483665, ppMsg=ppMsg@entry=0x7fdb26529df8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:799
#4  0x00007fdb3553adbc in hgcmServiceThread (ThreadHandle=2147483665, pvUser=0x7fdb1c002650) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCM.cpp:519
#5  0x00007fdb35538d11 in hgcmWorkerThreadFunc (ThreadSelf=<optimized out>, pvUser=0x7fdb1c002720) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/HGCMThread.cpp:194
#6  0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb1c0028e0, NativeThread=140579217516288, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#7  0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb1c0028e0) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#8  0x00007fdb3d676184 in start_thread (arg=0x7fdb2652a700) at pthread_create.c:312
#9  0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fdb27424700 (LWP 6753)):
#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#1  0x00007fdb3549bca6 in memcpy (__len=4608, __src=0x0, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#2  Display::i_handleDisplayUpdate (this=0x7fdb28003a00, uScreenId=0, x=0, y=826, w=<optimized out>, h=38) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1058
#3  0x00007fdb075cb665 in vga_draw_graphic (pThis=pThis@entry=0x7fdb24034100, full_update=false, fFailOnResize=fFailOnResize@entry=false, reset_dirty=reset_dirty@entry=true, pDrv=0x7fdb183937f8)
    at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:2521
#4  0x00007fdb075d32e5 in vga_update_display (pThis=pThis@entry=0x7fdb24034100, fUpdateAll=fUpdateAll@entry=false, fFailOnResize=fFailOnResize@entry=false, reset_dirty=reset_dirty@entry=true, 
    pDrv=<optimized out>, pcur_graphic_mode=pcur_graphic_mode@entry=0x7fdb240347a8) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:2670
#5  0x00007fdb075d36f8 in vgaPortUpdateDisplay (pInterface=0x7fdb24044e10) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:4684
#6  0x00007fdb35498859 in Display::i_displayRefreshCallback (pInterface=0x7fdb183937f8) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:3018
#7  0x00007fdb075cc3b8 in vgaTimerRefresh (pDevIns=<optimized out>, pTimer=0x7fdb25ea9450, pvUser=0x7fdb24034100) at ../VirtualBox-5.0.20/src/VBox/Devices/Graphics/DevVGA.cpp:5335
#8  0x00007fdb34213ef3 in tmR3TimerQueueRun (pVM=pVM@entry=0x7fdb3405a000, pQueue=0x7fdb25e9c920) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/TM.cpp:2171
#9  0x00007fdb342174a9 in TMR3TimerQueuesDo (pVM=0x7fdb3405a000) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/TM.cpp:2087
#10 0x00007fdb34221809 in vmR3HaltGlobal1Halt (pUVCpu=0x7fdb27addfa0, fMask=607, u64Now=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:685
#11 0x00007fdb34222982 in VMR3WaitHalted (pVM=0x7fdb3405a000, pVCpu=0x7fdb34075000, fIgnoreInterrupts=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:1105
#12 0x00007fdb34192eb2 in EMR3ExecuteVM (pVM=<optimized out>, pVCpu=<optimized out>) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/EM.cpp:2566
#13 0x00007fdb34222d61 in vmR3EmulationThreadWithId (ThreadSelf=0x7fdb20008610, pUVCpu=0x7fdb27addfa0, idCpu=0) at ../VirtualBox-5.0.20/src/VBox/VMM/VMMR3/VMEmt.cpp:235
#14 0x00007fdb3d312274 in rtThreadMain (pThread=0x7fdb20008610, NativeThread=140579233220352, pszThreadName=<optimized out>)
    at ../VirtualBox-5.0.20/src/VBox/Runtime/common/misc/thread.cpp:717
#15 0x00007fdb3d39133c in rtThreadNativeMain (pvArgs=0x7fdb20008610) at ../VirtualBox-5.0.20/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
#16 0x00007fdb3d676184 in start_thread (arg=0x7fdb27424700) at pthread_create.c:312
#17 0x00007fdb3c70b37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

(gdb) up
#1  0x00007fdb3549bca6 in memcpy (__len=4608, __src=0x0, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:51

(gdb) list
51	  return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
46	
47	__fortify_function void *
48	__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
49		       size_t __len))
50	{
51	  return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
52	}
53	
54	__fortify_function void *
55	__NTH (memmove (void *__dest, const void *__src, size_t __len))

(gdb) up
#2  Display::i_handleDisplayUpdate (this=0x7fdb28003a00, uScreenId=0, x=0, y=826, w=<optimized out>, h=38) at ../VirtualBox-5.0.20/src/VBox/Main/src-client/DisplayImpl.cpp:1058
1058	                        memcpy(pu8Dst, pu8Src, w * 4);
1053	                    const uint8_t *pu8Src = pFBInfo->updateImage.pu8Address + pFBInfo->updateImage.cbLine * y + x * 4;
1054	
1055	                    int i;
1056	                    for (i = y; i < y + h; ++i)
1057	                    {
1058	                        memcpy(pu8Dst, pu8Src, w * 4);
1059	                        pu8Dst += w * 4;
1060	                        pu8Src += pFBInfo->updateImage.cbLine;
1061	                    }
1062	

(gdb) print pu8Src
$1 = (const uint8_t *) 0x0
(gdb) print pFBInfo
$1 = (DISPLAYFBINFO *) 0x7fdb28003aa8
(gdb) print pFBInfo->updateImage.pu8Address
$2 = (uint8_t *) 0x0
(gdb) print pFBInfo->updateImage.cbLine
$3 = 0
(gdb) print pu8Dst
$4 = <optimized out>
(gdb) print w
$5 = <optimized out>

}}}


Thread 1 trying to refresh VGA Display and Thread 22 trying to power down virtual machine and resize display.

In i_handleDisplayResize pFBInfo->updateImage probably was nulled:
{{{
int Display::i_handleDisplayResize(unsigned uScreenId, uint32_t bpp, void *pvVRAM,
                                   uint32_t cbLine, uint32_t w, uint32_t h, uint16_t flags)
{
    LogRel((""Display::handleDisplayResize: uScreenId=%d pvVRAM=%p w=%d h=%d bpp=%d cbLine=0x%X flags=0x%X\n"", uScreenId,
            pvVRAM, w, h, bpp, cbLine, flags));

    if (uScreenId >= mcMonitors)
    {
        return VINF_SUCCESS;
    }

    DISPLAYFBINFO *pFBInfo = &maFramebuffers[uScreenId];

    /* Reset the update mode. */
    pFBInfo->updateImage.pSourceBitmap.setNull();
    pFBInfo->updateImage.pu8Address = NULL;
    pFBInfo->updateImage.cbLine = 0;
}}}
",gim
16147,Error in supR3HardenedWinReSpawn (System32\ntdll.dll rc=-626),Windows,Linux,VirtualBox 5.1.8,2016-11-04T12:47:38Z,2016-11-04T12:47:38Z,"VirtualBox on my machine is failing to start any virtual machine.  I'm sure the log can explain what's going on better than I can, so I've attached the log.

Thanks for any help you can provide,
skippythegoat",skippythegoat
16151,[5.1.6 & 5.1.8] - Failed to open a session for the virtual machine,Windows,Linux,VirtualBox 5.1.8,2016-11-04T17:29:21Z,2016-11-04T17:29:21Z,"I just reinstalled my OS and noticed that none of VirtualBox versions work in my system. I can't launch any machine. Thoughts?

Error details
----
The virtual machine 'Linux' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'G:\Other\VMs\Linux\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

----

VBoxHardening.log

{{{
1030.3bc: Log file opened: 5.1.6r110634 g_hStartupLog=00000000000000e4 g_uNtVerCombined=0xa0383900
1030.3bc: \SystemRoot\System32\ntdll.dll:
1030.3bc:     CreationTime:    2016-11-02T22:03:40.495512200Z
1030.3bc:     LastWriteTime:   2016-10-15T04:47:16.150180800Z
1030.3bc:     ChangeTime:      2016-11-02T22:18:32.862586300Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x1cbe88
1030.3bc:     NT Headers:      0xd8
1030.3bc:     Timestamp:       0x5801a332
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x5801a332
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x1d1000 (1904640)
1030.3bc:     Resource Dir:    0x168000 LB 0x67998
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.351
1030.3bc:     FileVersion:     10.0.14393.351 (rs1_release_inmarket.161014-1755)
1030.3bc:     FileDescription: NT Layer DLL
1030.3bc: \SystemRoot\System32\kernel32.dll:
1030.3bc:     CreationTime:    2016-07-16T11:42:16.155721400Z
1030.3bc:     LastWriteTime:   2016-07-16T11:42:16.155721400Z
1030.3bc:     ChangeTime:      2016-11-02T20:44:02.571188800Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0xaade8
1030.3bc:     NT Headers:      0xf0
1030.3bc:     Timestamp:       0x57899a29
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57899a29
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0xab000 (700416)
1030.3bc:     Resource Dir:    0xa9000 LB 0x528
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.0
1030.3bc:     FileVersion:     10.0.14393.0 (rs1_release.160715-1616)
1030.3bc:     FileDescription: Windows NT BASE API Client DLL
1030.3bc: \SystemRoot\System32\KernelBase.dll:
1030.3bc:     CreationTime:    2016-11-02T22:03:41.375540300Z
1030.3bc:     LastWriteTime:   2016-10-05T10:31:27.772259900Z
1030.3bc:     ChangeTime:      2016-11-02T22:18:30.003207600Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x21c580
1030.3bc:     NT Headers:      0xf8
1030.3bc:     Timestamp:       0x57f4c4f0
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57f4c4f0
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x21d000 (2215936)
1030.3bc:     Resource Dir:    0x201000 LB 0x560
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.321
1030.3bc:     FileVersion:     10.0.14393.321 (rs1_release_inmarket.161004-2338)
1030.3bc:     FileDescription: Windows NT BASE API Client DLL
1030.3bc: \SystemRoot\System32\apisetschema.dll:
1030.3bc:     CreationTime:    2016-07-16T11:42:21.577586000Z
1030.3bc:     LastWriteTime:   2016-07-16T11:42:21.577586000Z
1030.3bc:     ChangeTime:      2016-11-03T05:41:32.804568800Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x18960
1030.3bc:     NT Headers:      0xc8
1030.3bc:     Timestamp:       0x57899bd2
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57899bd2
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x19000 (102400)
1030.3bc:     Resource Dir:    0x18000 LB 0x400
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.0
1030.3bc:     FileVersion:     10.0.14393.0 (rs1_release.160715-1616)
1030.3bc:     FileDescription: ApiSet Schema DLL
1030.3bc: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1030.3bc: supR3HardenedWinFindAdversaries: 0x0
1030.3bc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1030.3bc: Calling main()
1030.3bc: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
1030.3bc: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1030.3bc: SUPR3HardenedMain: Respawn #1
1030.3bc: System32:  \Device\HarddiskVolume4\Windows\System32
1030.3bc: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1030.3bc: KnownDllPath: C:\Windows\System32
1030.3bc: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
1030.3bc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe)
1030.3bc: supR3HardNtEnableThreadCreation:
1030.3bc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffad02a8d60 pvNtTerminateThread=00007ffad02d58b0
1030.3bc: supR3HardenedWinDoReSpawn(1): New child 13d0.8e4 [kernel32].
1030.3bc: supR3HardNtChildGatherData: PebBaseAddress=00000000010af000 cbPeb=0x388
1030.3bc: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffad0230000 uNtDllChildAddr=00007ffad0230000
1030.3bc: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffad02a8d60
1030.3bc: supR3HardenedWinSetupChildInit: Start child.
1030.3bc: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1030.3bc: supR3HardNtChildPurify: Startup delay kludge #1/0: 257 ms, 30 sleeps
1030.3bc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1030.3bc:  *0000000000000000-ffffffffff06ffff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000f90000-0000000000f6ffff 0x0004/0x0004 0x0020000
1030.3bc:  *0000000000fb0000-0000000000f99fff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fc6000-0000000000fbbfff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fd0000-0000000000fcbfff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fd4000-0000000000fc7fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fe0000-0000000000fddfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000000fe2000-0000000000fd3fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000ff0000-0000000000feefff 0x0040/0x0040 0x0020000 !!
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: Freeing exec mem at 0000000000ff0000 (LB 0x1000, 0000000000ff0000 LB 0x1000)
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: Free attempt #1 succeeded: 0x0 [0000000000ff0000/0000000000ff0000 LB 0/0x1000]
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: QVM after free 0: [0000000000000000]/0000000000ff0000 LB 0x10000 s=0x10000 ap=0x0 rp=0x00000000000001
1030.3bc:   0000000000ff1000-0000000000fe1fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000001000000-0000000000f50fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000010af000-00000000010abfff 0x0004/0x0004 0x0020000
1030.3bc:   00000000010b2000-0000000000f63fff 0x0000/0x0004 0x0020000
1030.3bc:  *0000000001200000-0000000001104fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000012fb000-00000000012f7fff 0x0104/0x0004 0x0020000
1030.3bc:   00000000012fe000-00000000012fbfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000001300000-ffffffff8261ffff 0x0001/0x0000 0x0000000
1030.3bc:  *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000
1030.3bc:   000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000
1030.3bc:   000000007fff0000-ffff800a248effff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6db6f0000-00007ff6db6ccfff 0x0002/0x0002 0x0040000
1030.3bc:   00007ff6db713000-00007ff6da8d5fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6dc550000-00007ff6dc550fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc551000-00007ff6dc5bffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c0000-00007ff6dc5c0fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c1000-00007ff6dc605fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc606000-00007ff6dc606fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc607000-00007ff6dc607fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc608000-00007ff6dc60cfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60d000-00007ff6dc60dfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60e000-00007ff6dc60efff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60f000-00007ff6dc612fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc613000-00007ff6dc65afff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc65b000-00007ff2e8a85fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffad0230000-00007ffad0230fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0231000-00007ffad0337fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0338000-00007ffad037bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad037c000-00007ffad0384fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0385000-00007ffad0392fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0393000-00007ffad0393fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0394000-00007ffad0396fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0397000-00007ffad0400fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0401000-00007ff5a0821fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffffffe0000-00007ffffffcffff 0x0001/0x0002 0x0020000
1030.3bc: VirtualBox.exe: timestamp 0x57d6d53c (rc=VINF_SUCCESS)
1030.3bc: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
1030.3bc: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1030.3bc: supR3HardNtChildPurify: cFixes=1 g_fSupAdversaries=0x80000000
1030.3bc: supR3HardNtChildPurify: Startup delay kludge #1/1: 513 ms, 59 sleeps
1030.3bc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1030.3bc:  *0000000000000000-ffffffffff06ffff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000f90000-0000000000f6ffff 0x0004/0x0004 0x0020000
1030.3bc:  *0000000000fb0000-0000000000f99fff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fc6000-0000000000fbbfff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fd0000-0000000000fcbfff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fd4000-0000000000fc7fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fe0000-0000000000fddfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000000fe2000-0000000000fc3fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000001000000-0000000000f50fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000010af000-00000000010abfff 0x0004/0x0004 0x0020000
1030.3bc:   00000000010b2000-0000000000f63fff 0x0000/0x0004 0x0020000
1030.3bc:  *0000000001200000-0000000001104fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000012fb000-00000000012f7fff 0x0104/0x0004 0x0020000
1030.3bc:   00000000012fe000-00000000012fbfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000001300000-ffffffff8261ffff 0x0001/0x0000 0x0000000
1030.3bc:  *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000
1030.3bc:   000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000
1030.3bc:   000000007fff0000-ffff800a248effff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6db6f0000-00007ff6db6ccfff 0x0002/0x0002 0x0040000
1030.3bc:   00007ff6db713000-00007ff6da8d5fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6dc550000-00007ff6dc550fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc551000-00007ff6dc5bffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c0000-00007ff6dc5c0fff 0x0040/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c1000-00007ff6dc605fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc606000-00007ff6dc612fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc613000-00007ff6dc65afff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc65b000-00007ff2e8a85fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffad0230000-00007ffad0230fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0231000-00007ffad0337fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0338000-00007ffad037bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad037c000-00007ffad037ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0380000-00007ffad0384fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0385000-00007ffad0392fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0393000-00007ffad0393fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0394000-00007ffad0396fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0397000-00007ffad0400fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0401000-00007ff5a0821fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffffffe0000-00007ffffffcffff 0x0001/0x0002 0x0020000
1030.3bc: supR3HardNtChildPurify: Done after 852 ms and 1 fixes (loop #1).
13d0.8e4: Log file opened: 5.1.6r110634 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa0383900
13d0.8e4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffad0230000 g_uNtVerCombined=0xa0383900
13d0.8e4: ntdll.dll: timestamp 0x5801a332 (rc=VINF_SUCCESS)
13d0.8e4: New simple heap: #1 0000000001400000 LB 0x400000 (for 1904640 allocation)
1030.3bc: supR3HardNtEnableThreadCreation:
13d0.8e4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
13d0.8e4: System32:  \Device\HarddiskVolume4\Windows\System32
13d0.8e4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
13d0.8e4: KnownDllPath: C:\Windows\System32
13d0.8e4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
13d0.8e4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
13d0.8e4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
13d0.8e4: Registered Dll notification callback with NTDLL.
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
13d0.8e4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ffacd5a0000 LB 0x0021d000 C:\Windows\System32\KERNELBASE.dll [fFlags=0x0]
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ffacef80000 LB 0x000ab000 C:\Windows\System32\KERNEL32.DLL [fFlags=0x0]
13d0.8e4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
13d0.8e4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffacef80000 'C:\Windows\System32\KERNEL32.DLL'
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ff6dc550000 LB 0x0010b000 C:\Program Files\Oracle\VirtualBox\VirtualBox.exe [fFlags=0x0]
13d0.8e4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 74 ms, CloseEvents);

}}}

",x7370616d
16153,Trac detected an internal error.,Windows,Windows,VirtualBox 5.1.8,2016-11-05T15:10:30Z,2016-11-05T15:10:30Z,It happened when I was finishing to create my VirtualBox account.,Nelson Sampaio Jr
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,other,VirtualBox 5.1.8,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)"
16157,Windows installer should add VirtualBox path to the PATH environment variable,Windows,other,VirtualBox 5.1.8,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
16158,One-click experience for closing VM,all,all,VirtualBox 5.1.8,2016-11-06T11:06:30Z,2016-11-06T11:06:30Z,"When you close the VM window at the host, the machine's state would be saved without any prompts.

At the moment this behavior can be ONLY enabled from the command line for a SELECTED machine.

It would very convenient when you have several virtual machines running in the background.
Moreover, this scenario would be safe for the vast majority of the use cases.",Leonid Dorogin
16160,Add option to not return immediately after a contolvm command,other,other,VirtualBox 5.1.8,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
16161,Opening a VBOX file from Win Explorer opens a 2nd instance of VirtualBox Manager,Windows,all,VirtualBox 5.1.8,2016-11-06T16:56:24Z,2016-11-06T16:56:24Z,"== NOTE: This affects BOTH Win & Linux Hosts ==
Launch !VirtualBox Manager. Double-click (or open) a VBOX file from Windows Explorer/File Manager.
* If the VM is already registered and not running, it will run. Good.
* If the VM is already registered and running, it will get the focus. Good.
* If the VM is not registered, a 2nd instance of !VirtualBox Manager opens up just to register the VM, which also appears on the 1st instance as well. __Not good__.
Especially on Windows, if you couple this, with #14988 it makes things not ... optimal.",Socratis
16164,VirtualBox 5.0 causes lost interrupts / disk stalls on a Linux system,Linux,Linux,VirtualBox 5.0.28,2016-11-07T07:11:16Z,2016-11-07T07:11:16Z,"The host system is an 8-core AMD 64-bit system with 32 GB of RAM, a 128 GB SSD drive and a 1 TB regular rotating disk drive. The operating system is Linux Mint 18; kernel is Ubuntu's 

Linux AlgoCompSynth 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox is 5.0.28 r111378 directly from Oracle's download page. I've tried this with 5.1 and it's worse.

In normal use - creating a virtual machine, exporting to an OVA, etc., sometimes the system will freeze for a second or two, then pick up where it left off. It only does this when I'm using VirtualBox.

I dug through kernel ""dmesg"" output and found out what's happening. 


{{{
[  +0.418779] vboxdrv: ffffffffc0835020 VMMR0.r0
[  +0.108599] vboxdrv: ffffffffc0930020 VBoxDDR0.r0
[  +0.003241] vboxdrv: ffffffffc0006020 VBoxDD2R0.r0
[  +0.056406] vboxpci: created IOMMU domain ffff8808170fec20
[Nov 6 22:38] ata1: lost interrupt (Status 0x58)
[  +0.000029] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  +0.000007] ata1.01: failed command: READ DMA
[  +0.000009] ata1.01: cmd c8/00:01:00:e8:d9/00:00:00:00:00/f7 tag 0 dma 512 in
                       res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)
[  +0.000005] ata1.01: status: { DRDY }
[  +0.000023] ata1: soft resetting link
[  +0.184530] ata1.00: configured for UDMA/33
[  +0.007848] ata1.01: configured for UDMA/33
[  +0.000018] ata1: EH complete
[  +0.019241] ata1.00: Enabling discard_zeroes_data
[  +0.156301] ata1.00: Enabling discard_zeroes_data


}}}
I've seen this happen on both the SSD and the rotating disk - whichever VirtualBox is using at the time.",znmebznmeb
16167,Clipper directory() and shared folders inconsistency,Windows,Windows,VirtualBox 5.1.8,2016-11-07T19:56:28Z,2016-11-07T19:56:28Z,"Hi,
I'm using a VM with xp sp3 (home edition) as guest and Win10 Home as host.
Under the VM I develop using the old Ca-clipper compiler: the compiler and the sources, together with the files for testing, are stored on the hd of Win10 and I access them by shared folders on the VM.
When I use CA-Clipper directory() function to get a list of files stored on a shared folder, the return value (directory() returns an array of filenames) is empty, like in the folder there isn't any file.
I investigated deeply and I found that if in the folders there are no more than 8 files the function returns a correct array.
Then I copied all the test shared folder, locally on the hd of the VM, and when I launched the program and tested the directory() function, it runs without any problem and returns all the filenames that are stored on the folder, no matter if they are more then 8, 1000, or more.
To be sure that it's not a Clipper related problem (maybe with shared folders), I tested the program with WMWare. I exported the Virtualbox VM and then imported in WmWare, created the shared folders (like in Virtualbox) and launched the program to read the content of shared folder: in this case there was any problem and the content of the test (shared) folder was returned entirely. So I think the problem is related to VirtualBox.
Regards,
Marco",mark63
15929,"Restored VM stays ""darkened"" if switching workspaces while restoring",Linux,Windows,VirtualBox 5.0.26,2016-11-09T13:03:53Z,2016-11-09T13:03:53Z,"The following applies to Fedora 24. The latest VirtualBox version distributed from packages with it is 5.0.26.

To reproduce:

1) have more workspaces active in Gnome, e.g. A and B
2) start restoring a suspended Windows 10 VM in workspace A; the Windows desktop is showed darkened, to represent that you can't use it yet
3) switch to workspace B before restore is completed
4) wait some time for restoring to complete
5) switch back to workspace A

... and the Windows desktop will still be darkened, despite being active. 

If, instead, you don't switch workspace for the duration of the restore, the darkening is removed at completion.

Note that if - from another workspace - I ""look"" at the VirtualBox window using a video capture device (e.g. obs-studio), the window is correctly not darkened.

The issue could be VirtualBox's or of the way VirtualBox interacts with Gnome's window manager / composite manager (mutter?). I found a similar issue from the past at https://forums.virtualbox.org/viewtopic.php?f=7&t=68896&p=372386#p328269 , with compton, another Linux composite manager.

Thanks.",giacecco
16173,USB3 Passthrough Fails w/ VLI USB3 Controller,Windows,Windows,VirtualBox 5.1.8,2016-11-09T13:38:39Z,2016-11-09T13:38:39Z,"I've been unable to get USB 3.0 or 2.0 devices to attach to VMs on a machine I've added a VLI-based PCIe USB 3.0 card to. It shows up as ""captured"" in the devices menu, but never appears in the VM. The device is also not replaced with the passthrough driver on the host. I've reason to believe this is related to the VLI chipset the card uses as USB 2.0 devices attached to the Intel chipset's USB 2.0 controller work just fine. The same VMs are able to have devices passed through to them properly on a machine that uses Intel's USB 3.0 controller. I've tested this with an external USB 3.0 hard drive (ASMedia controller) and two flash drives. (Sandisk Ultra and a Silicon Power.)",Ziginox
16174,HPE Smart Storage Administrator utility lockup error 851,Windows,Linux,VirtualBox 5.0.26,2016-11-09T17:01:13Z,2016-11-09T17:01:13Z,"Long time we have curious trouble with virtualbox.
HOST W2012 64 SERVER HP ProLiant ML310e Gen8
When we use smart array gui or utility , this report on Dynamic Smart Array B120i RAID
851 Controller lockup error: Restart the server and run a diagnostic report. Install the latest version of controller firmware. If the condition persists, the controller may need to be replaced or require service 

This error ocurs when virtualbox is run and use direct hardware access with VTx.
Guest os is openSUSE 64 13.1 

Issue not change more as year and last four kernels...

When vbox is off lockup not present, when no hardware direct , too no lockup, but Linux guest system is unstable .

Raid Works ok with or without lockup, but with lockup we cant control raid status. HP utility show nothing in error state.

Dynamic Smart Array B120i RAID controller have latest drv and fw.
Issue tested on 5.0.4 - 5.0.26 i mean next too but not tested now.

Please help.
",mguru
14208,Virtualbox crashes when undocking,Windows,Windows,VirtualBox 4.3.28,2016-11-11T10:23:05Z,2016-11-11T10:23:05Z,"Hi,

I am using a docking station and most of the time (I would say 80%) virtual box crashes when I undock.

I am using VB version 4.3.28 r100309 under windows 7 enterprise SP1.

After having investigated a little bit this seems to happen when 2D acceleration is enabled (never tried with 3D) 

I attached the logs in case it can help to investigate.",thedavix
16179,BSOD after Update,other,other,VirtualBox 5.1.8,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
16180,windows host crashes when memory is full,Windows,Linux,VirtualBox 5.1.8,2016-11-11T15:03:37Z,2016-11-11T15:03:37Z,"I have recently started to get windows BSODs when the guest VMs are trying to allocate too much memory.

I am running Win 8.1 64bit on a laptop with 16GB of RAM, and have 2 VMs open at the same time with 8GB of memory set to each, so there is obviously some over-provisioning going one.
This works fine until some heavy-duty operation starts in one of the VMs. What happens then is:
- windows slows down to a crawl - I can see screen and cursor refreshes
- I can briefly see the 'vm has been suspended because of lack of memory' dialog box popping up
- the win BSOD kicks in

This did not happen until recently (version 5.1.8) at the moment, but it might be simply due to the fact that I was not using intensively 2 VMs with memory over-provisioning before.

The windows event log says:

L’ordinateur a redémarré après une vérification d’erreur. La vérification d’erreur était : 0x0000007e (0xffffffffc0000005, 0xfffff8015d657f50, 0xffffd0005c195d78, 0xffffd0005c195580)

The guest OS is dDebian 8.6

Note that the VM additions inside the VMs might not correspond exactly to the version of VBox running.",gggeek
16176,"No documentation exists for GAs' ""VBoxControl""",all,all,VirtualBox 5.1.8,2016-11-11T15:40:24Z,2016-11-11T15:40:24Z,"As the title plainly says, there is no documentation whatsoever for the ""{{{VBoxControl}}}"" program that gets installed with the GAs. No mention of the syntax, parameters, logic, effects. None, except the command line syntax help.

In fact, it would be nice to mention what the rest of the programs installed with the GAs also do. Even briefly.",Socratis
16178,Please fix audio debugging instructions,Linux,all,,2016-11-11T17:04:29Z,2016-11-11T17:04:29Z,"The instructions available here https://www.virtualbox.org/wiki/AudioDebug to provide useful log files for audio issues debugging are misleading, at least for Linux.

They suggest to set an environment variable in a shell with elevated privileges, then kill this shell and check in another, non-privileged, shell that the variable is set. I'm quite sure that running VirtualBox with VBOX_RELEASE_LOG set will never happen this way.

My suggestion would be to ask people to close VirtualBox, then run from the command line


{{{
VBOX_RELEASE_LOG=drv_host_audio.e.l.l2.l3.f+drv_audio.e.l.l2.l3.f+audio_mixer.e.l.l2.l3.f+dev_hda_codec.e.l.l2.l3.f+dev_hda.e.l.l2.l3.f+dev_ac97.e.l.l2.l3.f VirtualBox
}}}


then check in the log that ""Audio: Verbose logging enabled"" is there.

I can't test the provided instructions for Windows.",slv
16181,RTC not updated when VM is resumed.,all,all,VirtualBox 5.1.8,2016-11-11T18:19:07Z,2016-11-11T18:19:07Z,"Actual:
When a vm is suspended, unlike real hardware, both the RTC and the system clock are stopped.

Expected:
Like on actual hardware the RTC should continue, or should appear to do so by virtue of being synchronized with the host when the VM is resumed.

If the VM is power cycled, VirtualBox resets the virtual RTC to the correct time.",DaVinci
16182,osx host full screen window switching display errors,Mac OS X,all,VirtualBox 5.1.8,2016-11-11T21:58:16Z,2016-11-11T21:58:16Z,"VBox under OSX host, switching to a running full screen (for example windows 7) guest by double clicking on a VBox guest list item, results in the listed item's icon becoming a screen graphic artifact. This can be fixed/repaired/disappear by most keyboard operations (e.g. pressing the shift key) (making screen shots difficult). 
",littlerunningdeer
16183,Add a warning if user running VirtualBox isn't in group vboxusers on Linux hosts,other,other,VirtualBox 5.1.8,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
16186,"With Windows 10 guest and linux host, selecting VBox ‘Shared Clipboard – Bidirectional’ disables internal guest copy/paste functionality of all but text.",Linux,Windows,VirtualBox 5.1.8,2016-11-15T00:13:06Z,2016-11-15T00:13:06Z,"With VBox ‘Shared Clipboard’ set to bidirectional it is not possible to copy Formulas within an Excel spread sheet. It appears to affect the Windows ‘copy’ functionality, only allowing text values onto the clipboard.

Host Gentoo Linux 64 bin KDE5 virtualbox 5.1.8 ; Guest Windows10 64 bit version 1607
Also tested against Windows 10 32 bit version 1607 and Windows 8.1 32 bit. Both are affected.

See attached document for steps to demonstrate and reproduce this issue.",normanb46
16184,Invisible Mouse Cursor,other,Linux,VirtualBox 5.1.8,2016-11-15T02:20:51Z,2016-11-15T02:20:51Z,"Hi there,

I am using VBox 5.1.8 for Windows (also tried test build 5.1.9) but am unable to get the mouse to work on RHEL 7. The cursor is apparently there but its just not showing. When I press left ctrl key and move mouse around the ""show location of pointer"" gets highlighted as I move in different areas. My machine config -

HP Pavillion Laptop / Windows 10 (Home 64bit) / Intel i7-6700HQ / GPUs (Intel HD Graphics 530 & Nividia GeForce GTX 960M)

I will be upfront and open, I am very new to VBox and Linux but nonetheless, I have been reading into forums and bug tickets for the past 3 days but to no avail.

Will appreciate any and all help. Many thanks.",Dan J
16187,VirtualBox-Error in suplibOsinit,Windows,all,VirtualBox 5.1.8,2016-11-15T12:13:04Z,2016-11-15T12:13:04Z,"In Windows 10 Professional when I like to run any virtual machine I got an error.

Does anybody knows something about this error?",VIrtualtest
15560,Linux guest on Windows 10 host keeps freezing,Windows,Linux,VirtualBox 5.0.24,2016-11-15T22:38:46Z,2016-11-15T22:38:46Z,"I have a current Debian testing VM running on a current Windows 10 host.
It started to freeze very frequently with 5.0.22. 5.0.23 r108298 (and subsequently 5.0.24) reduced the frequency of the freezes, but did not quite eliminate them.

I experienced this freeze while running Knoppix 7.6.1 on 5.0.23 r108298 as well.

The kernel started out as a 4.5 version and was upgraded to 4.6 recently (shortly before VBox 5.0.24 was released but after my switch to 5.0.23 r108298).

It seems likely that this ticket is related to #15529, as the freezes started happening with the same release and the ACPI code change revert seems to have helped (reducing the frequency of the freeze from one every couple of minutes to once or twice a day).

The symptoms for the 5.0.24 freeze were:
* While actively working with the VM, it suddenly stopped responding.
* Most of the video was frozen, with the notable exception of an open but not focused tab in Chromium - the ""page is loading"" animation remained functional.
* The VM stopped responding to SSH login attempts.
* The VM stayed this way for about 15 mins, until I forcibly turned it off.
* I tried to see whether exiting fullscreen mode would make a difference - it did not.
* After the freeze, the VM displayed no apparent disk or CPU activity.

Unfortunately, neither my notebook not my keyboard have status indicator leds, so I cannot tell whether a kernel panic occurred.",ancow
15213,Unable to remove device with attached diff images,Windows,Windows,VirtualBox 5.0.16,2016-11-16T13:00:51Z,2016-11-16T13:00:51Z,"Receive message box - one or more disk image files are not currently accessible......

Select ""check""

VDI device is not attached to any machine.  Also, rechecked all machines and non are using this vdi in this location.  Attempt to remove it but it says it has 1 child media and object in use.

a) cryptic message as it should really say in plain english what object name its associated with.

b) there are no machines that I currently have using this particular vdi.

c) have similar named vdi located in another directory but not attached to this one here.  Nothing is attached to it.
",ArtZ
16193,Need a way to save machien state when Windows 10 restarts automatically,other,other,VirtualBox 5.1.8,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
16201,"Wacom pan/scroll facility does not work when VirtualBox has focus, but does work when it does not",Mac OS X,Windows,VirtualBox 5.0.28,2016-11-19T13:33:04Z,2016-11-19T13:33:04Z,"I am running a Mac Sierra host with a Windows 10 guest.  In the guest I am running Firefox with a lengthy web page longer than the height of the window.

I have long lived with the Wacom pan/scroll not working in the Windows 10 guest, but today I accidentally discovered a condition when it does work.  I used a habit motion without being prepared as I usually am.  This brought out the contrast in behaviours.

When the guest virtual machine has the application focus, pan/scroll does not work.

When I move the application focus to another Mac application, say Folder, and while the focus remains there in Folder I do pan/scroll in the virtual machine, the application in the virtual machine response to the activity.  As soon as I move the focus to the virtual machine, the facility disappears.

I have configured my Intuos Pro M tablet to engage pan/scroll on the pen click and drag function.  Works fine in Mac apps.  Works fine in the virtual machine when the virtual machine does not have focus.  Does not work in the virtual machine when the virtual machine has focus.

In this example I am using pan/scroll to scroll the web page in the browser in the guest machine.

I hope this helps!

. . . . . . Ken",gkholman
16205,Can't open a Word document located in shared folder,Mac OS X,Windows,VirtualBox 5.1.8,2016-11-19T17:27:39Z,2016-11-19T17:27:39Z,"I upgraded to 5.1.8, but I can't open Word files (.docx or .doc) located on the shared folder anymore (message: ""non è possibile aprire"" is ""it is not possible open""). Moreover if I try to move a Word file from the shared folder to the desktop an error message come out (error 0x80070057: the parameter is incorrect).
Excel files open and move without problem. 

Didn't have any problem with previous issue (don't remember exactly the last, but sure 4 and something else)",reboox
12382,Very slow guest OS performance when Windows XP Guest guest has more than 1 VCPU,other,other,VirtualBox 4.3.2,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
16203,Windows 10 Pro 64Bit crashes when VirtualBox 5.1 loads,Windows,Windows,VirtualBox 5.1.8,2016-11-21T11:04:15Z,2016-11-21T11:04:15Z,"I installed VirtualBox 5.1 successfully 
but when it starts, the computer crashes.
",tonyc49
16177,in linux 64bit plasma 5 virtualbox start only from terminal,Linux,all,VirtualBox 5.1.8,2016-11-21T11:22:12Z,2016-11-21T11:22:12Z,"As the title say: virtualbox, from release 5.1.6 (and included the build 5.1.9) does not start from menu, but only from terminal.",duns
16086,VBOX 5.1.8 is crashing,Windows,Windows,VirtualBox 5.1.8,2016-11-22T08:17:51Z,2016-11-22T08:17:51Z,"My Windows 10 box upgraded on Monday. I'm running Windows 10 Pro 10.0.14393 Build 14393 x64 now. My vbox did not work after the upgrade, so I downloaded the latest version (5.1.6) and upgraded vbox
Since the upgraded, vbox is crashing. It crashed once on Tuesday, once yesterday, and already 5 times this morning. I've upgraded to 5.1.8 this morning, and disabled Audio, but it crashed again.

Is there something that I can do to prevent this?",Jaques
16120,VirtualBox 5.1.8r111374 aborts Debian guest after random period - NAT?,Linux,Linux,VirtualBox 5.1.8,2016-11-22T08:28:23Z,2016-11-22T08:28:23Z,"I have a Debian Jessie guest running on a Arch host. After a seemingly random period of time, the guest will transition to the ""aborted"" state. I am yet to observe it happening, I normally notice after I find my VirtualBox guest has disappeared after a few hours. 

I think it's possible that this is associated with an older ticket. Sorry if I have not formatted this ticket correctly, this is my first time doing so.

I will provide any information you require, please ask.



",sam.4325224
16214,Blocking delay when switching Guest and Host,Windows,Linux,VirtualBox 5.1.4,2016-11-22T14:35:14Z,2016-11-22T14:35:14Z,"I have a Ubuntu16.04 Desktop guest on my Windows 7 Host. My VirtualBox version is Version 5.1.4 r110228 (Qt5.5.1) and VirtualBox additions installed on the guest. 

When I switch between my guest window and any other window in the host, everything blocks for 1-2 seconds. It is annoying since when I change the context and type something, the text gets lost and need to re-type again.

Log attached. ",jlausuch
16166,vboxusers group disappeared after last update,Linux,Windows,VirtualBox 5.1.8,2016-11-22T17:45:58Z,2016-11-22T17:45:58Z,"Hi,

I recently upgraded to VirtualBox 5.1.8 r111374 (Qt5.6.1) from the previous version, on my Ubuntu 14.04 host. The guest is Windows 7. I also have the proper guest addition and extension pack.

After this upgrade VirtualBox can't detect any USB flash drives connected to my computer. After digging into this a bit, I realized that the vboxusers group has disappeared from my computer! I tried reinstalling the extension pack but had no luck.

Everything else seems to be working fine.

",mau17
14145,Virtualbox installer does not ask for admin rights (UAC) automatically,Windows,other,VirtualBox 4.3.28,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
16215,Crash while installing Avast,Windows,Windows,VirtualBox 5.1.10,2016-11-23T05:37:36Z,2016-11-23T05:37:36Z,"Host OS = XP Prof 32 bit V 2002 SP3 on 800GB partition. 1GB (of 2) ram
Guest OS = Windows 7 Prof 32 bit SP1 30 GB on 50GB partition (7 GB free).  1GB (of 2) ram
Guest originally restored from Macrium image.
When installing Avast anti-virus (free version) I get a ""guru meditation"" before it completes.
Tried with normal and immutable guests, and with a similar Vista guest
Gets to about 99% (going by the progress bar)
",jchrisj
16217,Defaultly started VM  goes to shutdown if send it to background,Mac OS X,all,VirtualBox 5.1.10,2016-11-23T09:48:14Z,2016-11-23T09:48:14Z,"1) Start VM as always.

2) Choose ""Send to background"" in window context menu from Dock.

3) Window dissapeas, in VirtualBox.app discover that VM goes to shutdown.",776166
16218,"Win10 host Ubuntu 16.04 guest, graphics problems",Windows,Linux,VirtualBox 5.1.10,2016-11-23T10:09:57Z,2016-11-23T10:09:57Z,"I have over the last couple of months set up several Ubuntu 16.04 guest and noticed a pattern of problems over all the version 5.X's of VirtualBox:

It seems to be generally slow at times. Sometimes 10-15 seconds to start up until one gets to login. After logging in another 10-15 seconds before the machine becomes fully available, i.e the app icon bar shows.

When using the front end of the OS (i.e. opening, closing or minimising windows), the machine becomes sluggish but not always. when checking processes running ""Compiz"" will typically be using a lot of CPU, e.g. 70-100% for some time, after which it drops and the OS front end becomes responsive/accessible again.

If one enables 3D Acceleration it sometimes help, but may have other consequences such as the Chromium browser just displaying large rectangular, black or white areas with no menu or anything else displayed. The front end of other running applications also becomes either sluggish or non-responsive.

I have also seen problems with videos, sometimes there sometimes not. Sometimes the sound may be out of sync with the picture. But the problems are intermittent. 

So, in general it seems that graphics is not handled properly by VirtualBox and/or Ubuntu 16.04 itself, possibly a combination of the two. Since VirtualBox are handling the graphics in the form of special drivers, the solution probably has to come from VirtualBox.

",Orionsg
15558,"VBoxDrvStub error: Unknown image file (NtCreateFile, Unknown Status - 5633)",Windows,Linux,VirtualBox 5.0.24,2016-11-23T18:33:51Z,2016-11-23T18:33:51Z,"Host Windows 7 SP 1[[BR]]
McAfee VirusScan Enterprise Workstation, v 8.7.0.570
Ubuntu 14.04 LTE guest

Error dialog ""Error in supR3HardenedWinReSpawn"":
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status - 5633
(0xffffe9ff) (rcNt=0xe986e9ff)
VboxDrvStub error: Unknown image file
\Device\HarddiskVolume2\PROGRA~1\Oracle\VIRTUA~1\VIRTUA~1.EXE at 000000013f740000. (rc=-5633)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_NOT_KNOWN_DLL_OR_EXE (-5633) - Process Verification Failure:
An unknown and unwanted DLL was found loaded into the process.",Liberry Man
16128,"Client loses TCP/UDP connectivity, VirtualBox on host uses 100% CPU",Linux,Linux,VirtualBox 5.1.8,2016-11-24T08:00:57Z,2016-11-24T08:00:57Z,"I have a guest debian server running on ubuntu host (both 64 bits). Networking mode was set to NAT and port forwarding was set for guest ports 22 and 80 to control and use this server.

It worked fine during low-load testing, but when it come to production with some load (1-2 requests per seconds from around the world), following issue was discovered:

- It's happening after some time, usually after 2-3 days but last time it happens after 7 hours only.
- CPU usage of VBoxHeadless process on host jumps and stay at 100%, although there is no any load on the guest.
- Guest system continues to work but it cannot nor accept nor create new TCP connections (existing TCP connections, e.g. early opened ssh session, continues to work).
- Outgoing TCP connection from the guest (e.g. wget) fails with error code ""Network is unreachable"". This error code is a clear sign that ""bad thing happened"".
- DNS resolving on guest fails so it seems that UDP is affected too.
- PINGs from guest are working! So I consider that network, routing, etc is OK, and the bug is in NAT code.

Of course there are no any messages in any logs when it happens.

I think that symptoms are quite similar to Bug #15223, but don't know could they have common reason or not. First discovering this issue in 4.3.old, I've upgraded to 4.3.40 and then to 5.1.8, but the issue is still here.

",Roman Trunov
16223,Can't install VirtualBox on Windows 10,other,other,VirtualBox 5.1.10,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
16225,"When I Change Network setting to “Bridge” Mode, Virtual Machine isn't available again.",other,other,VirtualBox 5.1.10,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
16226,vbox file is missing after adding port-forwarding config while guest is running and later guest shutdown,Windows,Linux,VirtualBox 5.1.10,2016-11-24T12:39:23Z,2016-11-24T12:39:23Z,"Steps to reproduce this problem:

- Create a Linux guest (without installing guest tools).
- Create a snapshot of this guest.
- Fully clone the guest (not linked), not including any snapshot (last state only).
- Run the clone guest.
- Add some port-forwarding configurations while guest is running and save.
- Do ""shutdown -h -t 0"" on the guest.
- It's not previsible how many guest restarts could led .vbox file to be deleted. I had the same problem even with just restarting VirtualBox manager itself or rebooting the host.

Additional info:

Host: Windows 10 Pro Anniversary 64-bits (Hyper-V disabled via ""bcdedit /set hypervisorlaunchtype off"").
Guest: Ubuntu Server 16.04 LTS x64, cloned from another guest.",calamann
16227,USB M-Audio fast track ultra device not working,Windows,Windows,VirtualBox 5.1.10,2016-11-24T17:07:29Z,2016-11-24T17:07:29Z,"After reading several forums I managed to have my guest (windows 7 home) recognising my audio device.
I installed the appropriate M-Audio drivers with no errors.

However, if I try to play any sound the device basically freezes the program which is attempting to use it and seemed to play like a microsecond of music every several seconds. This also happens if I directly try to test it from windows (the green bars indicating the volume in output move incredibly slowly).",epifab
16228,"VM crashes with ""Aborted"" status when host machine connects to bluetooth device",Mac OS X,other,VirtualBox 5.1.2,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
16231,Windows 10 - Problem with brightness and 2D/3D,Linux,Windows,VirtualBox 5.1.10,2016-11-25T14:00:14Z,2016-11-25T14:00:14Z,"Dear support,

I have fedora 24 server with Virtualbox 5.1.10. I hoped that with time and new releases of Virtualbox, Windows 10 problems would be resolved but now I have the following issue:
- I can't set up brightness of video
- Powerpoint with video is slow

With Windows 7/8 performance were good but with windows 10, system is in general slower.

My host is a Thikpad T540p with 6 GB memory, Bumblebee-neauveau for Intel with Nvidia GPU:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)

Windows 10 release is 1607 (Build 14393.447).

If I select 2d or 3d or disable both, nothing change... It seems better without flag in configuration.

Have you any advices?

I attache Vbox.log

Thanks in advance
Mario

",santomar
16232,Automatic Screen Resizing doesn't work anymore,Mac OS X,Windows,VirtualBox 5.1.10,2016-11-25T20:04:11Z,2016-11-25T20:04:11Z,"Mac Os host and Windows 8.1 Guest.

",FlavioMattosRj
16234,Virtual Machine Crashes when changing to Seamless mode,Mac OS X,Windows,VirtualBox 5.1.10,2016-11-25T20:55:52Z,2016-11-25T20:55:52Z,,FlavioMattosRj
16235,latest Guest Additions crash linux guests after installation and rebooting the guest,Windows,Linux,VirtualBox 5.1.10,2016-11-28T11:20:17Z,2016-11-28T11:20:17Z,"I've find out that the new version of guest extensions crashes down newder debian derivates as elementary os and deepin. I can't confirm this for ubuntu but at least for these too. 

T reproduce 

Download an iso  at deepin.org or elementary.io
install the system on windows at usual 
update the system with sudo apt -y full-upgrade
install guest additions from the iso image delivered with virtualbox as root or with sudo
reboot the guest

The expected result is virtual box on windows will hang up and not respond anymore

",horvan
15699,Issue with Windows Guest Digital License no longer valid,Windows,Windows,VirtualBox 5.1.2,2016-11-28T11:30:14Z,2016-11-28T11:30:14Z,"When upgrading Virtual Box from V5.0 platform to V5.1, I have issue with the Digital license being invalid for Window 10 guests. Once the guest additions are installed I get a message that this copy of Windows is not active. When trying out the activation trouble shooter it prompts you to go to the Store to buy another copy.

I have tried both 5.1.0 and 5.1.2.  The Host OS is Windows 10 Pro 64 bit, while the two clients are Windows 10 Pro 32 bit preview versions.",WMurdockJr
16101,Windows guest desktop refresh rate is assumed to be 60Hz,Linux,Windows,VirtualBox 5.1.8,2016-11-28T18:29:38Z,2016-11-28T18:29:38Z,"Host: Lubuntu 16.04 x86-64, Nvidia binary driver
Guest: Windows XP SP3

The host desktop vertical refresh rate is 50Hz.

The XP guest emulated vertical refresh rate is 60Hz. For example, Display Properties -> Advanced -> Monitor tab allows only one setting for Screen refresh rate: 60 Hertz.

Programs running in the guest which calibrate their timing to the Windows desktop refresh rate ""see"" a refresh rate of 60Hz, not the host's actual 50Hz rate.

To fix that, perhaps the guest graphics driver could have other selectable refresh rates?",Donuts
14727,"With Windows 10 host, VirtualBox guest window jumps between monitors",Windows,Linux,VirtualBox 5.0.6,2016-11-29T14:00:32Z,2016-11-29T14:00:32Z,"With a Windows 10 x64 host using multiple monitors, the VirtualBox guest window now jumps between monitors. When it jumps, it always jumps from monitor 2 (extended desktop) to monitor 1 (main desktop). It jumps under these circumstances:
* resizing guest window, especially when the mouse cursor is close to the screen edge
* when guest window changes from text only mode to GUI mode (guest is Ubuntu 15.10, so it starts in text mode upon boot and switches back to text mode for a several seconds at the end of a shut down)
* when moving guest window while mouse is close to screen edge

I am aware of Windows's Aero Snap feature, starting with Windows 7, where dragging windows to the edge of the monitor causes the windows to be maximized or positioned differently. I am not activating this feature. Also:
1. this feature does not cause windows to jump between monitors
1. this feature did not cause problems with VirtialBox when using Windows 7, 8, or 8.1 as a host
1. no other program on my PC exhibits this behvaior

This happens despite the fact that I clean installed Windows 10 and VirtualBox twice. This has happened with all versions of VirtualBox that came out since about a month after Windows 10 RTM was released.

I normally have VirtualBox close to maximized in my monitor 2. By close to maximized, I mean I have about a 10-20 pixel margin around all sides of the guest OS window. That means I am having to drag the guest OS window extents near to but not at the monitor edge.

I am actually on VirtualBox 5.0.8. That was not available as an option in the '''Version''' dropdown.

(#12209 could be related, but I don't think it's the same.)",Aren Cambre
16146,Double click to single click in VirtualBox GUI,Linux,Windows,VirtualBox 5.1.8,2016-12-01T17:28:16Z,2016-12-01T17:28:16Z,"Whether I click on the QT Menu's(File, Machine, View...) or within the VM I have to double-click to produce a single click, I think it might be a QT bug along these lines, http://stackoverflow.com/questions/18444431/mouse-events-blocked-because-of-qgl-view
If I turn off Mouse Integration in the menu the cursor is captured and I can use the VM normally.

",chrisq
16250,Display resolution capped at 1024x768,Windows,Linux,VirtualBox 5.1.10,2016-12-01T17:28:20Z,2016-12-01T17:28:20Z,Just installed 5.1.10 r112026 Qt5.6.2 and tried to get Lubuntu running on a Win 7/64 workstation with dual 1920x1080 displays. Tried setting everything in sight including preferences but the Lubuntu VM still shows a capped display size. Similar to bugs: 15997  15788  15310,stkvbox
16254,VxWorks guest broken on v5.X,Mac OS X,other,VirtualBox 5.1.10,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
16253,Starting vm hides itself and all apps on 2 desktops,Linux,Linux,VirtualBox 5.1.10,2016-12-02T02:53:25Z,2016-12-02T02:53:25Z,"Host is Dell M6800 running Mageia 5 Linux, KDE4(with 8 desktops).
On desktop 3, running VB, I install/updatee Mageia 6-RC, then reboot to test -- it minimizes ALL apps, as if I clicked host's Show Desktop, on desktop 3 _and_ 4...
Via the taskbar, I can restore (un-minimize) the apps; but when I do this on the started vm, it minimizes all the apps again.  All I can do with this running vm is to power it off which then restores all the minimized apps on both desktops. No idea how this vm could impact 2 desktops on host...

Screenshot of no visible apps would not help...  :)",Pierre Fortin
16252,Share clipboard cause host copy and paste stuck,Linux,Windows,VirtualBox 5.1.10,2016-12-02T17:15:48Z,2016-12-02T17:15:48Z,"Guest XP: Shared Clipboard is set to bidirectional

After a while (or one or more hour),  the copy and paste in host is not stable. If you select some text in google Chrome and copy, the page of Chrome suspended, even crash whole chrome.

when shutdown the guest, end program dialog: VBoxSharedClipboardClass

If the guest XP is shutdown, host clipboard works fluently.

If the disable the Shared Clipboard of guest, host clipboard works great.

Thus, I suppose that the problem is in the guest addition of virtualbox.",maxchen
16191,"Microphone not detecting any sound: Windows guest, Linux host",Linux,Windows,VirtualBox 5.1.6,2016-12-02T17:45:20Z,2016-12-02T17:45:20Z,"Host: Ubuntu 16.10 64-bit, 4.8.0-27-generic

Host audio controller: PulseAudio

Guest: Windows 7 32-bit

Guest audio controller: ICH 97 (Sound Blaster 16 not detected by guest, with Intel HD Audio guest does not detect any capturing device)

Microphone is correctly enumerated by the guest, but it never detects any sound from the host. On occasions the device shows as ""unavailable"" in the guest.

The logs show that the capture device is being correctly recognized.

Additional information:

* Problem symptoms seem similar to the ones reported #15802, which is marked as closed.
* Problem shows in official VirtualBox package for Ubuntu 16.10, version is 5.1.6_Ubuntu r110634 (using matching extension pack & Guest additions)
* Problem persists in virtualbox-5.1_5.1.8-111374~Ubuntu~yakkety_amd64.deb
* It used to work correctly in the official package for Ubuntu 16.04: virtualbox-5.0.24-dfsg-0ubuntu1.16.04.1
* These users seem to be affected by the same problem: https://forums.virtualbox.org/viewtopic.php?f=7&t=78797
",trifon
16263,VDE networking support seems not to be present,Linux,other,VirtualBox 5.0.24,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
16245,HiDPI host (KDE Plasma 5) menu clicks are in wrong place,Linux,Windows,VirtualBox 5.1.6,2016-12-04T15:38:03Z,2016-12-04T15:38:03Z,"When using KDE Plasma 5 as a host, menu clicks in the UI are misplaced; clicking a menu item in the VirtualBox UI causes the click to be registered inside the guest OS window.

Clicks also do not register anywhere inside the window sometimes (multiple client clicks required to get the guest OS to realise one single click).

OS: Kubuntu 16.10 (fresh installation)
PC: Dell XPS 13 Late 2016

Video: https://1drv.ms/v/s!Aqb97db1Lae8gvArfCENGu1I8RZsCQ",davewthompson
16261,no media in w7 when connecting usb3 disk with uas,Linux,Windows,VirtualBox 5.1.10,2016-12-05T08:11:55Z,2016-12-05T08:11:55Z,"I'm using gentoo, kernel 4.4.26, VB version 5.1.10. Also I have an external disk seagate 3tb st3000dm001 in its native external enclosure (with usb3). I get a contradiction.
On the host (gentoo) it is seen as a disk ONLY if the module ""uas"" (USB attached SCSI) is loaded. Otherwise, only as some usb controller.
In the guest (w7pro) it appears as a disk ONLY if the ""uas"" module of the host is disabled. Otherwise, again only as some attached usb device.
I could reproduce it several times in a row. With and w/o a reboot.

Technically I can insert/remove the ""uas"" module depending on a situation. Also, I'm not sure is it a problem of ""uas"" module or VB, but the pattern is clear.

Any suggestions to solve/improve this behaviour?",alex-kas
16262,shared folder not write-able for non-root users for special windows folders,Windows,Linux,VirtualBox 5.1.10,2016-12-05T08:13:01Z,2016-12-05T08:13:01Z,"I would like to mount the Windows ''Downloads'' directory as a shared folder, but the mounted folder is not writable to regular users. Yet the root user can still write to it.

Played all mount options but to no avail: the permissions of all files and sub-folders in the mounted folder are correctly set, and the issue is about the permission bits of the mount point itself. Tried to mount a sub-folder in the ''Downloads'', then the permission bit is correct.

{{{
    C:\Users\opensrc\Downloads     -> Downloads: dr-xr-xr-x
    C:\Users\opensrc\Downloads\Sub -> Subfolder: drwxr-xr-x
}}}

Wonder why the ''Downloads'' folder is treated differently.
",opensrc
16265,"Virtualbox 5.1.10 on Ubuntu 6.10 running on Mac Pro 3,1 incorrectly assumes hyperthreading",Linux,all,VirtualBox 5.1.10,2016-12-05T11:31:42Z,2016-12-05T11:31:42Z,"When running the Oracle 5.1.10 deb of Virtualbox-5.1 (5.1.10) on Ubuntu 6.10 installed on a MacPro 3,1 running on Harpertown processors, the Processor tab incorrectly assumes that Hyperthreading is available on that processor and shows 16 CPUs being available on a dual quad-core system.

",howarth
16258,Install fails v5.1.10 - Linux 64 - Ubuntu,Linux,all,VirtualBox 5.1.10,2016-12-05T14:55:33Z,2016-12-05T14:55:33Z,"I downloaded the full installer for VirtuabBox, debian distro Linux 64bit.

The package manager reports an ""unsatisfiable Dependency"" on QT Core:

{{{
Error: Dependency is not satisfiable: libqt5core5a (>=5.6.0-beta)
}}}


I have scanned the debian repositories.  Sure enough there is No Stable package available to support this installer package.

I don't know what using the in-test version might be on my other stable system programs.

{{{
Package libqt5core5a

    wheezy-backports (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1~bpo70+1: amd64
    jessie (stable) (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1: amd64
    stretch (testing) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
    sid (unstable) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
}}}

I suggest it is infeasible to use this version of virtualbox on a stable system.  It might be OK for a test system or development system.  I had a mismatch of GTK versions one time and it caused all kinds of chaos with the GUI.  I don't recommend the experience.",Will
16273,Mouse Wheel Bug in FreeBSD/TrueOS guest,all,BSD,VirtualBox 5.1.10,2016-12-07T00:01:20Z,2016-12-07T00:01:20Z,"Hi There,

Whats broken:
When running FreeBSD as a guest on any host for some reason the mouse scroll wheel issues back and forward browser (web browser such as Firefox or Chromium) commands in FreeBSD and TrueOS. 

Whats expected:
The Mouse wheel should only scroll up and down when using a web browser

Whats happening:
The mouse simultaneously issues backwards and forwards commands in addition to scrolling up and down when using a web browser.

Scope:
This issue affects FreeBSD/TrueOS VirtualBox additions for FreeBSD guests 5.1.10 and earlier /usr/ports/emulators/virtualbox-ose-additions
This issue has no effect on guests which do not use the FreeBSD OS type in Virtual Box host.
There is no effect switching between ps3/usb tablet settings on the host config.

I posted briefly in the Virtual Box forums on this issue
https://forums.virtualbox.org/viewtopic.php?f=4&t=80912&p=379748#p379748

And have had some nice folks in the TrueOS chatroom track down that this bug seems to be limited to Virtual Box's FreeBSD mouse driver.

Jeffrey Baitis @baitisj posted in the TrueOS chat the following:
so here's the proof. That's running xev and showing the mouse events when I'm scrolling the mouse wheel up and down., I tried the same test in a linux host, and it worked fine. There's clearly some issue with the freebsd virtualbox input driver

[[Image(1)]]


Thank you for your assistance!
Jason",Oclair
16236,Bug in the vboxdrv module (rtR0MemAllocEx) on Linux 4.8.8+ (grsecurity),Linux,other,VirtualBox 5.1.10,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
16270,Impossible to reconnect VRDP after disconnection,Linux,Windows,VirtualBox 5.1.10,2016-12-07T09:08:08Z,2016-12-07T09:08:08Z,"Hi, we are using VRDP on virtualbox 5.1.10 on Debian Wheezy. Virtual Machine is a Windows XP.

5.1.10-112026~Debian~wheezy

VBox ExtPack is install too.

My problem with vrdp occurs when there is a network disconnection or if the PC that connects to VRDP is disconnected suddenly without properly closing the RDP connection.
{{{
00:14:22.877226 VRDP: Connection opened (IPv4): 15
00:14:22.877825 VRDP: Negotiating security method with the client.
00:14:22.891875 VRDP: Methods 0x0000001b
00:14:22.891913 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:14:22.891929 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:14:22.891942 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:14:22.891974 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:14:22.966644 VRDP: Client seems to be MSFT.
00:14:22.966680 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:14:22.967984 AUTH: User: []. Domain: []. Authentication type: [Null]
00:14:22.968014 AUTH: Access granted.
00:14:22.968756 AUTH: Multiple connections are not enabled. Access denied.
00:14:22.968779 VRDP: Connection closed: 15
00:14:35.670630 VRDP: New connection: 
00:14:35.670763 VRDP: Connection opened (IPv4): 16
00:14:35.671358 VRDP: Negotiating security method with the client.
00:14:35.672871 VRDP: Connection closed: 16
00:14:35.705151 VRDP: New connection: 
00:14:35.705210 VRDP: Connection opened (IPv4): 17
00:14:35.705832 VRDP: Negotiating security method with the client.
00:14:35.723321 VRDP: Methods 0x0000001b
00:14:35.723383 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:14:35.723398 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:14:35.723412 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:14:35.723425 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:14:35.783553 VRDP: Client seems to be MSFT.
00:14:35.783592 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:14:35.784755 AUTH: User: []. Domain: []. Authentication type: [Null]
00:14:35.784785 AUTH: Access granted.
00:14:35.785588 AUTH: Multiple connections are not enabled. Access denied.
00:14:35.785618 VRDP: Connection closed: 17
00:16:08.662647 VRDP: New connection: 
00:16:08.662747 VRDP: Connection opened (IPv4): 18
00:16:08.663370 VRDP: Negotiating security method with the client.
00:16:08.664983 VRDP: Connection closed: 18
00:16:08.689273 VRDP: New connection: 
00:16:08.689333 VRDP: Connection opened (IPv4): 19
00:16:08.689886 VRDP: Negotiating security method with the client.
00:16:08.719393 VRDP: Methods 0x0000001b
00:16:08.719401 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:16:08.719404 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:16:08.719407 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:16:08.719410 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:16:08.789932 VRDP: Client seems to be MSFT.
00:16:08.789994 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:16:08.791341 AUTH: User: []. Domain: []. Authentication type: [Null]
00:16:08.791372 AUTH: Access granted.
00:16:08.792399 AUTH: Multiple connections are not enabled. Access denied.
00:16:08.792434 VRDP: Connection closed: 19
00:19:15.028325 VRDP: New connection: 
00:19:15.028558 VRDP: Connection opened (IPv4): 20
00:19:15.029174 VRDP: Negotiating security method with the client.
00:19:15.030794 VRDP: Connection closed: 20
00:19:15.073957 VRDP: New connection: 
00:19:15.074088 VRDP: Connection opened (IPv4): 21
00:19:15.074707 VRDP: Negotiating security method with the client.
00:19:15.091989 VRDP: Methods 0x0000001b
00:19:15.092058 VRDP: Channel: [rdpdr] [1004]. Accepted.
00:19:15.092076 VRDP: Channel: [rdpsnd] [1005]. Accepted.
00:19:15.092091 VRDP: Channel: [drdynvc] [1006]. Accepted.
00:19:15.092107 VRDP: Channel: [cliprdr] [1007]. Accepted.
00:19:15.219874 VRDP: Client seems to be MSFT.
00:19:15.219935 VRDP: Logon: VM-W7-PC (11.46.49.32) build 7601. User: [] Domain: [] Screen: 0
00:19:15.220837 AUTH: User: []. Domain: []. Authentication type: [Null]
00:19:15.221122 AUTH: Access granted.
00:19:15.221791 AUTH: Multiple connections are not enabled. Access denied.
00:19:15.221815 VRDP: Connection closed: 21
}}}

Similars problems are already evoke in many tickets like #4655.

Just disconnect your RJ45 cable, on your server or on the PC who RDP WHEN RDP is connected and you will not can connect you again.
For reconnect you will have to reboot VM or disable/enable VRDP.",Ravinou
16123,"Host: Windows 10 x64, Guest: Debian x64. Host gets unusable, kind of freezes.",Windows,Linux,VirtualBox 5.1.8,2016-12-07T09:59:30Z,2016-12-07T09:59:30Z,"Hi,

first my Setup:

Host:
CPU: Intel i7-6700K.
GPU: NVIDIA GeForce GTX 1060, Driver: 372.90.
Windows 10 64-Bit. Avira Antivirus.
VirtualBox 5.1.8

Guest:
Debian 8.6.0 amd64.


Basically most functionality works fine. The VM starts and works like a charm. But after a few minutes of using the Debian-Guest the Host begins to act strange. On the Windows 10 Host i can't start new Windows anymore. The Processes start, as seen in the Task-Manager, but no Windows appear. Already before started Programs in already running Windows are still working perfect, except something like System-Monitor Desktop-Widgets, which are freezing. Even the Start-Menu doesn't show up, if i click on the Windows-Banner. Ctrl+Alt+Del brings me a BlackScreen.
From this Point the VM still works great. But if i try to shut it down, VirtualBox freezes completely.
The only Way to get the Host back working from this Point is the Hard-Reset-Button.
Maybe a compatibility Problem between the Virtualization and the Graphics-Driver. I encountered a similiar Problem some time ago with another Virtualization Solution on another Platform, where it caused the NVIDIA Driver to collapse.",DenKr
16024,Win10 host Ubuntu 16.04 guest random crashes,Windows,Linux,VirtualBox 5.0.26,2016-12-07T10:02:03Z,2016-12-07T10:02:03Z,"I am using Ubuntu 16.04 with X on Win10 host. It randomly crashes from time to time. I found a remedy. If I select Other 64bit OS from the settings, it does not crash anymore. Below is the Vbox.log file from a crashed machine (after machine was force shut down).
",yurtesen
16269,Extension pack won't load - Windows 10,other,other,VirtualBox 5.1.10,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
16266,Segmentation fault,Mac OS X,Windows,VirtualBox 5.1.10,2016-12-08T10:30:53Z,2016-12-08T10:30:53Z,"I don't know what prompted it, unfortunately. A couple minutes earlier I had attached a USB external storage device to the VM (which seemed to be handled by the guest OS without incident), then I told Windows 10 to check for updates. While it was doing that the VM window disappeared and I found a crash file. That VM session had been running for a while and been through at least one sleep–wake cycle of the host machine and the accompanying wireless network disconnections and reconnections.

I restarted the VM, and tried to reproduce by attaching the same USB device and telling Windows to check for updates again, but the crash did not repeat.

VirtualBox version: 5.1.10 r112026
Host OS: macOS 10.12.1
Guest OS: Windows 10 Pro Insider Preview version 1607 build 14965.1001",terry
16278,Guest OS Windows 7 gets locked up if java applet is running on 2nd virtual screen,Mac OS X,Windows,VirtualBox 5.1.10,2016-12-09T02:44:47Z,2016-12-09T02:44:47Z,"Hi my windows 7 guest OS running on Mac OS host on the new macbook pro Retina 2016 gets locked up if I run a Java applet on the 2nd virtual screen.
It has no issue if I run it on just one screen. Basically I could not get any keyboard response from the guest OS. It is the guest OS that froze, no issues with the host OS. I tested this on 5.1.10, 5.1.11 test build and development build 5.1.51 all exhibit the same issue.

",TJSIA
16275,Virtual Box crash on more screen,other,Linux,VirtualBox 5.1.10,2016-12-09T06:41:23Z,2016-12-09T06:41:23Z,"I can translate to english.
Программа аварийно завершается с ошибкой sigfault. Эта ошибка у меня была при использовании Windows 8, 8.1, 10 в качестве основной ОС и Ubuntu 14,15,16 в качестве гостевой ОС. На моём компьютере на работе имеется два монитора. Основная система Win10, гостевая Ubuntu. Ubuntu настроена на использование обоих мониторов. Далее, если я подключаюсь с ноутбука с одним дисплеем к своему рабочему компу через RDP то VirtualBox аварийно завершается. Если так-же удаленно включить её заново и запустить Ubuntu, то всё как-бы загружается и работает. Но при этом в Windows в панели задач я вижу только один ""виртуальный дисплей"" гостевой ОС, но Ubuntu считает что их два! Из-за этого я не могу получить доступ к окнам, открытым на невидимом виртуальном дисплее.",StarVld
15910,Sound delay,Linux,Windows,VirtualBox 5.1.4,2016-12-10T07:56:16Z,2016-12-10T07:56:16Z,"After upgrading to VirtualBox 5.1.x and installing the anniversary update of Windows 10 (on the guest) I'm noticing sound delays of about ~1 second and that accessing files on the shared folder causes it often to lock up (seems to be a race condition). The latter causes related applications (like any browser and the Windows explorer) to hang and Windows is mostly not able anymore to cleanly shutdown.

I'm not sure if the issues are caused by Windows (at least a clean reinstall did not solve them) or VirtualBox but to go sure I have created this ticket. In the attachments is the VBox.log of a session where both issues got reproduced. Also there is a testcase for the lockup issue (testcase.css and testcase.html) which needs to be put into a shared folder and testcase.html needs then to be opened with any browser (for example Google Chrome). Keeping F5 pressed to cause Chrome to reload the testcase multiple times should cause the race condition to appear after a few seconds (noticeable by not seeing the green circle on Virtual Box's shared folder symbol anymore and Chrome trying to load the site for an infinite amount of time).",Sworddragon
16281,VM screen flickers during booting until I'm completely logged in on the win7 vm,Linux,Windows,VirtualBox 5.1.10,2016-12-12T12:58:31Z,2016-12-12T12:58:31Z,"I'm running VirtualBox-5.1-5.1.10_112026_fedora25-1.x86_64 on Fedora 25 with win7 as guest. My problem: If booting the VM (full screen mode), the screen flickers rhythmically (about 1 Hz freqency)   until I'm completely logged in with my win 7 account.

Only a very few times the VM boots flawlessly.

This effect is new, no such effect on Fedora25 as host with my previous Vbox version
VirtualBox-5.1-5.1.8_111374_fedora24-1.x86_64. Going back to this version will help as workaround.

My current F25 kernel is 4.8.13-300.fc25.x86_64, but same problem with previous F25 kernels.

Anybody sees such effect too?

Any comments are welcome.

Kind regards

Joachim Backes",backes
13580,The Instruction at 0x... referenced memory at 0x... The memory could not be read,Windows,Linux,VirtualBox 4.3.18,2016-12-12T17:22:47Z,2016-12-12T17:22:47Z,"As of version 4.3.16 and 4.3.18 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
",Frank Breitling
16284,after osx Sierra upgrade - docked VM now requires two clicks,Mac OS X,all,VirtualBox 5.1.10,2016-12-12T21:33:00Z,2016-12-12T21:33:00Z,"After upgrading to osx sierra, I noticed that a running, minimized VM in the dock, now requires two clicks (on the docked VM icon) to restore said window (formerly it only required one). The first click restores focus to VB menubar, the second restores the VM window. ",littlerunningdeer
16271,Interface scale up hidpi gnome,Linux,all,VirtualBox 5.1.10,2016-12-13T07:05:32Z,2016-12-13T07:05:32Z,"After updating to the new version of virtualbox, the whole interface is scaling up. I attach a picture of the the interface itself.

I went and uninstalled the package called virtualbox-qt and installed the previous version of it and everything went back to normal. This might have to do something with bug #15707.

I'm running openSUSE Tumbleweed, gnome, full HD 14""",flanaras
14457,cannot ping host <--> VMs after upgrade to VirtualBox 5.0.x with NDIS6 driver,Windows,all,VirtualBox 5.0.2,2016-12-13T10:29:47Z,2016-12-13T10:29:47Z,"In reference to this forum post:

https://forums.virtualbox.org/viewtopic.php?f=6&t=69597

after upgrading to VirtualBox 5.0.x I could no longer ping between the host and the VMs (bridged mode), while the VMs could still ping each other, and all (host and VMs) could still ping other computers on the same subnet.  By reverting back to using the NDIS5 driver, all worked properly again, so the issue is related to some bug/defect in the new NDIS6 driver implementation.
",qd01a
16285,Crash disconecting host monitor while saving state,Windows,Windows,VirtualBox 5.1.10,2016-12-13T19:16:33Z,2016-12-13T19:16:33Z,"While I was saving the state of a VM in fullscreen mode, I disconnected a host monitor (physically, by unplugging the video cable). The VM process crashed with the following error (translated):
 Application Error : The instruction at 0x00000000775C4756 referenced the memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.

After that, the VM in the VBox Manager resulted in an ""Interrupted"" status.

Here are some useful details:
* The host screens '''before''' unplugging were:
 1. Notebook native monitor
 2. HDMI external monitor, with fullscreen VM
 3. MiniDP external monitor, ''main host screen''
* The host screen '''after''' unplugging were:
 1. Notebook native monitor, ''main host screen''
 2. HDMI external monitor, with fullscreen VM
* Of course the host screen configurations before and after unplugging are as expected, including the fact that the main host screen switched from the screen no. 3 to the no. 1
* All 3 monitors have the same resolution, 1920x1024
* The VM has 2 guest screens, but only 1 was enabled
* The VBox Manager was open but '''did not''' crash, i.e. only the VM process crashed",FstTesla
16289,Camera access not working,Linux,Linux,VirtualBox 5.1.10,2016-12-14T16:14:02Z,2016-12-14T16:14:02Z,"Apps such as Viber and Camera apps aren't able to connect with the host camera on my laptop since updating to the new VBox version. 

Running Android version 4.4 lollipop 32-bit on VBox 5.1 on Ubuntu 16.04 (64-bit)

(see screenshots)",d3m0nking
16276,Audio in OS X host and Windows-10 client is not working in VB 5.1.10 r112026 (Qt5.62),Mac OS X,Windows,VirtualBox 5.1.10,2016-12-14T16:23:45Z,2016-12-14T16:23:45Z,"Audio in VirtualBox 5.1.10 r112026 (Qt5.62) (the latest release) on OS X 10.12.1 (Sierra) host and Windows-10 client with latest service packs/updates is not working again.

It was working OK in previous VirtualBox release. It was not working in yet earlier VirtualBox releases.

This is a blocker for me because I use a music program available only on Windows. This is the whole reason for having VirtualBox and Windows-10 for me.",mhakman
12567,snapshot to a remote iSCSI volume (builtin initiator) broken since 4.3.0 (verified on Windows and Mac hosts),all,all,VirtualBox 4.3.6,2016-12-14T23:05:17Z,2016-12-14T23:05:17Z,"Hello,

I used to have workstations running local !VirtualBox VMs which base disk are connected to the same remote iSCSI read-only lun. It use to work because each VM also have a default snapshot to the base disk meaning disk writes are redirected to the local differential disk created by the snapshot.[[BR]]
This worked correctly from version 4.0 to latest 4.2.20 and seems broken starting from 4.3.0, including latest 4.3.6.[[BR]]
I could verify this on a Mac host (OSX 10.9) and a Windows host (Windows 7 Prof.). I expect it to be the same on a Linux Host but didn't have a chance to verify.

How to reproduce:[[BR]]
machine 1: iSCSI server (I used ietd on SLES). IP address 192.168.0.19[[BR]]
machine 2: !VirtualBox host (Windows or OSX using Virtualbox 4.3.6). IP address 192.168.0.23

 1. machine 1: 
  - create an iSCSI target and a read-write 20GB Lun [[BR]]
  target: iqn.1995-09.fr.univ-lr:storage.win7 [[BR]]
  lun: 2

 2. machine 2:
  - create a VB VM 'win7' without a hard disk
  - attach the iSCSI volume from machine 1 with VBoxManage:
  {{{
VBoxManage storageattach ""win7"" --storagectl IDE --port 0 --device 1
  --type hdd --medium iscsi --mtype normal --server ""192.168.0.19""
  --target ""iqn.1995-09.fr.univ-lr:storage.win7"" --lun 2
}}}
  - install the guest OS (Windows 7 Pro.)
  - start the guest OS once after install to make sure booting read-write from the remote target works fine
  - poweroff the VM and create a snapshot

 3. machine 1:
  - make the previous Lun 2 read-only

 4. machine 2:
  - start the VM

With !VirtualBox 4.3.6, the VM hangs just after starting and the associated host process is using 100% CPU time. The diffential disk never grows and there isn't any iSCSI network traffic on machine 1.
Unfortunately, nothing interresting in the VM log file (Windows host or Mac host).

With !VirtualBox 4.2.20, the guest OS starts and differential disk of the snapshot starts to grow while block are written

If I downgrade from 4.3.6 to 4.2.20 everything works fine again.
So it's clearly related to something changed starting from 4.3.0
Note, I also tried with immutable disk wich avoid creating a snapshot manually and makes the VM revert to its pristine state at each start (which is the desired behaviour) and the results are the same.

Thanks for you help and ready to provide any additional details as needed.

Happy new year

Alban
",Alban
16290,Virtual Screen menu > Resize to 1600x1200?,all,all,VirtualBox 5.1.8,2016-12-14T23:58:52Z,2016-12-14T23:58:52Z,"This is a shameless copy of ticket #14384, but for a different resolution. It's a rather glaring omission to not have 1600x1200 available which is quite a common resolution.

I have the following feature request:
I'd like to see Resize to 1600x1200 in View > Virtual Screen menu, as an additional 4:3 resolution.


One other thing I'd like to bring up is that with the growing popularity of QHD and 4K monitors, other requests may start flowing in to request higher resolutions. I'm not sure how much work it would require, but would it be possible to add a possibility to edit what appears in the list of available resolutions and to add custom resolutions to the list without having to engage Virtualbox developers in the process?",marek_k
16293,memory can't be written,Windows,Windows,VirtualBox 5.1.4,2016-12-15T13:50:37Z,2016-12-15T13:50:37Z,"tried to create common folder and got bug with nulls and message ""memory can't be written"".
i remove this version of VBox and install 4.1.4, and now it works
fix this bug in 5.1.4 pls :)",ilyarik
16283,Detachable run won't let its window close correctly,Linux,other,VirtualBox 5.0.18,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
16295,RDP-Server very slow then 1 connection unreachable,Linux,all,VirtualBox 5.1.10,2016-12-16T14:05:11Z,2016-12-16T14:05:11Z,"Hello,

the RDP-Server have some trouble if the client gets unreachable. All another connections (available and future) are extreme slow and unusable.

The problem comes up then someone change from LAN to WLAN, without cancel conventional the connection before.

To reproduction that issue do the follow:


{{{
1. Enable RDP for a VM
2. Start the VM
3. Connect via RDP-Client to the VM
}}}

Way 1:

{{{
4. Change the IP ( ifconfig eth0 192.168.1.15 netmask 255.255.0.0 )
5. Close the connection and reconnect
}}}

Way 2:

{{{
4. Unplug the networkcable physical.
5. Connect with a another PC
}}}

Now the RDP connection is unusable / heavy slow.",dk_lcom
16297,"vboxweb and vboxbaloonctrl service scripts depend on 'killall', which is not installed by default on CentOS7",Linux,other,VirtualBox 5.1.10,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
16301,Cut off top and bottom on full screen,Linux,Windows,VirtualBox 5.0.22,2016-12-17T09:41:39Z,2016-12-17T09:41:39Z,"Preconditions:
- Host: Linux Mint 17.3 64bit
- Guest: Windows 7 64bit
- Guest additions installed
- Fullscreen mode on (host+f)

Reproduction route:
1. lock guest windows (Win+l)
2. leave fullscreen (Host+f)
3. go back to fullscreen (Host+f)
4. click to unlock guest windows

Expected: Fullscreen covers all area
Actual: Top and bottom of the screen are cut off",JanuszWirtualizacji
16307,sda_hda_intel 0000:00:05: CORB reset ...,Windows,Linux,VirtualBox 5.1.10,2016-12-19T11:25:07Z,2016-12-19T11:25:07Z,"Any version VB 5 - 5.1.11r112223. Host Windows, Guest Linux. I it see at everyone loadings of Debian 8.4, 8.5 (Xu 15-17,Lu 16,U 16). 

The text sda_hda_intel 0000:00:05: CORB reset ... appears only if to use Intel HD Adio in the VB settings.

Why I use Intel HD Audio? I have two sound cards. One built-in the motherboard, second external. They have characteristics: 8-32bit 192kHz.

AC-97 (Audio Codec '97) ""AC'97 defines a high-quality, 16- or 20-bit audio architecture with surround sound support for the PC. AC'97 supports a 96 kHz sampling rate at 20-bit stereo resolution and a 48 kHz sampling rate at 20-bit stereo resolution for multichannel recording and playback. AC97 defines a maximum of 6 channels of analog audio output"" 

If load time speed is very fast this text can be not seen. The sound works without visible problems for Guest.",q34er6ty7
12477,Can't operate any more on a locked VM -- a way to force lock removal is needed,Linux,Windows,VirtualBox 4.3.4,2016-12-19T13:20:55Z,2016-12-19T13:20:55Z,"Sometimes it happens that a VM stops or hangs for some unknown reason and it becomes impossible to operate on it any more because vbox says it's locked.

For example:
{{{
$ VBoxManage controlvm xyz poweroff
VBoxManage: error: The virtual machine is being powered down
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: ""PowerDown(progress.asOutParam())"" at line 222 of file VBoxManageControlVM.cpp
}}}

and trying to start it gives:
{{{
$ VBoxHeadless -s xyz
Oracle VM VirtualBox Headless Interface 4.3.4
(C) 2008-2013 Oracle Corporation
All rights reserved.

VBoxHeadless: error: The machine 'xyz' is already locked for a session (or being unlocked)
VBoxHeadless: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxHeadless: error: Context: ""LockMachine(session, LockType_VM)"" at line 955 of file VBoxHeadless.cpp
}}}

Now I'm stuck: the only way I know to solve this problem is to completely shutdown vbox and/or restart the server, but this forces to shutdown all the other running vms, and thats not really easy on some situation.

I suppose that a way to force the removal of a lock is much needed.",Alex
16280,Shared clipboard is not working in GUI mode,Mac OS X,Linux,VirtualBox 5.1.6,2016-12-19T20:17:51Z,2016-12-19T20:17:51Z,"'''How to reproduce:'''

1. Set the bidirectional clipboard mode.
2. Run the guest for a while or pause and restore it. (I haven't yet found out the trigger for sure).
3. Copy a text from the guest into the clipboard.
4. Paste the text from the clipboard into the host or another guest.

'''Expected result:'''
The clipboard text is pasted into the host/other guest.

'''Actual result:'''
The clipboard text is not pasted into the host/other guest.

Unlike bug #15986 the problem occurs in GUI mode. The other bugs referred in bug #15986 don't match here. It only occurs in a Debian Linux guest, not in a Windows 7 guest. Copy and paste within each guest works fine. After restarting the guest the clipboard works fine.
I noticed it first in version 5.1.6, but the problem persists in version 5.1.10.

The clipboard related entries in VBox.log are:

{{{
00:00:05.989716 Shared clipboard service loaded
00:00:05.989747 Shared clipboard mode: Bidirectional
...
00:00:18.768979 HGCM: restoring [VBoxSharedClipboard]
}}}

",VBoxer1
16302,memory usaly error on ubuntu-16.04.1-desktop-amd64,Windows,Linux,VirtualBox 5.1.10,2016-12-20T12:29:13Z,2016-12-20T12:29:13Z,"1. run WarZone2100
2. Инструкция по адресу 0х0000000058383А30 обратилась к памяти по адресу 0x0000000000000008. Память не может быть read. ""OK"" — завершение приложения

p.s. https://yadi.sk/i/cDluGr-q33qgq8",fix27
16282,Win7: Cannot start a virtual box machine,Windows,other,VirtualBox 5.1.10,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
16294,Snapshot confirmation after closing virtual machine,other,other,VirtualBox 5.1.10,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
15653,VRDP not working after upgrading to 5.1,Linux,other,VirtualBox 5.1.0,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
16309,VBoxtray and VBoxservice sometimes block  windows 7 guest responsiveness,Linux,Windows,VirtualBox 5.0.30,2016-12-20T23:32:31Z,2016-12-20T23:32:31Z,"Since this fall my windows 7-64 guest occasionally stops responding to mic, mouse, and keyboard input and seems to hang. This typically happens when the host and guest interact, as in a drag-and-drop, or when two windows programs that both interact with the host seem to tangle (e.g. word and dragon naturally speaking). In fact the guest is not hung, as it's fully responsive to sending the ctrl-alt-delete signal and starting the task manager--which shows the same minimal responsiveness. I've ""solved"" the problem using VBoxManager guestcontrol to taskkill vboxtray or vboxservice, which I then restart inside the guest. 
Host: Linux Mint17.3x64 KDE fully patched, kernel 4.4.39

Log file attached.",matthewls
16303,Bluetooth disconnect when starting W10 64bit on OS X host,Mac OS X,Windows,VirtualBox 5.1.10,2016-12-21T18:52:37Z,2016-12-21T18:52:37Z,"
Re: Bluetooth disconnect when starting W10 64bit on OS X host
Postby rcatyvr » 17. Dec 2016, 23:45

Problem hunted down and solved for now:

Latest VirtualBox on El Capitan Mac, latest Window 10 from upgrade on 64 bit VM. 

Starting the VM caused my host Mac's Bluetooth services to stop and refuse to connect to my keyboard and trackpad and from operating inside/outside of, or after closing the VBox application. It is a BIG problem as the only way to close the VM  and restart my host's Bluetooth was to power off then reboot the computer which is an annoying waste of time and can break the HFS+ file system.

Fortunately, I found a wireless Logitech keyboard & mouse handy so I plugged the dongle into my USB hub and was able to continue to troubleshoot without having to crash the system repeatedly just to close the VM

Solution/Work around:

You will need to have at least a wireless or hard wired USB mouse plugged in. Especially if you are using a Mac, be sure that before the Windows VM actually starts to boot that you prevent it from going full screen and you lose the ability to click on the Apple control icon at the top left of the host's screen to do a controlled reboot. If you don't you will probably have to power the unit off the hard way. Note: a similar keyboard setup would help, but is not essential as both in the VM and the host, a functioning mouse can get you through to solution. 

1. Confirmed that I had replicable problem--repeatedly from cold start to full power-off crash.
2. Used an archived Win 10 VDI dated September 22, 2016 to confirm the problem originates in fact in Windows, not VBox--no problems seen
3. Went back to the most up-to-date Windows 10 VDI: Services control, I stopped & disabled: a) Bluetooth Handsfree Service, b) Bluetooth Support Service.
4. REBOOTed the Windows VM
5. Tested and had no further interference with the host's Bluetooth hardware.

Problem solved. I would call this a solution, though it is technically a work around, because disabling Windows' bluetooth should be moot. The host shouldn't be able to pass those services to the VM and therefore there is no need for them to even be there/on. However, that as by default they try to start up (and revert to a manual-start service) at boot time, and as it seems that just querying for the hardware is enough to crash the host's own hardware, those services should be disabled.

I don't know how it does it, but have I found out experimentally that in a VBox VM, Windows 10's bluetooth services/hardware layer have been recently changed and are now somehow attempting to control/attach to the host's Bluetooth stack during the client's boot up--causing them to crash and the host loose its hardware bluetooth service. Not supposed to happen, but it does. 

A long term solution would be for Oracle to figure how the Win10 VM is trying to access the hosts' hardware and crash it, and prevent it from doing so.",rcatyvr
16312,RPM upgraid fails when VBoxSVC --auto-shutdown is running,Linux,other,VirtualBox 5.1.12,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
16222,"dragndrop file fails (Windows 10 host, Ubuntu 64bit guest)",Windows,Linux,VirtualBox 5.1.10,2016-12-22T09:26:59Z,2016-12-22T09:26:59Z,"As per instructions, logs enclosed!",robertbaruch
16313,drag and drop in virtualbox 5.1.12 fail in Centos 7.3,Windows,Linux,VirtualBox 5.1.12,2016-12-22T09:27:30Z,2016-12-22T09:27:30Z,"When you log in Centos 7.3, after some times trying to drag and drop some file between guest and host systems a file repetively, this will not run ever again. Process will not run never again until you logoff from the system and login in it again.
Bidirectional mode are selected for drag and drop option.
It seem run only a few times, should be about three or four times until drag and drop crash it. Generally the process crash when you drag files at guest client, for example from windows to linux, having a virtual Centos 7.3 machine. The host machine is a windows 10 with the anniversary edition update included.",anruvel
16316,Kubuntu guest rendering errors with 3D acceleration enabled,Windows,Linux,VirtualBox 5.1.12,2016-12-22T14:15:09Z,2016-12-22T14:15:09Z,"I'm running a Kubuntu 16.10 (64-bit) guest on VBox 5.1.12, host OS Windows 10 64-bit. As long as 3D acceleration is disabled, everything is fine. After enabling 3D acceleration the KDE toolbar disappears, and there are some artifacts on the screen.

Guest additions were installed",ErnstH
16272,VirtualBox crashes out when attempting to boot Windows Me,Windows,Windows,VirtualBox 5.1.10,2016-12-23T04:53:07Z,2016-12-23T04:53:07Z,"When attempting to use Windows Me on one of my machines, VirtualBox crashes out with the message (from Windows host):

VirtualBox.exe - Application Error
The instruction at 0x758BA614 referenced memory at 0x000C000C. The memory could not be written.
Click on OK to terminate the program
Click on CANCEL to debug the program

The result is quite predictable. It happens when I attempt to boot a Windows Me floppy. I can use a Windows 95 floppy to get the VM started, and so install Me from source files, but the resulting hard disk crashes out with the same error.

I’m using VirtualBox 5.1.10 in Windows 10 on an Acer Extensa 5635Z laptop, with a T4200 processor (32-bit, no VT-x) and 2Mb RAM.
The problem does not happen on my other machine, which has a Core i5 (2500) processor amd 16Gb RAM.

I have managed to pin down the problem on the floppy to the disk boot sector, and the particular block of 54 bytes starting at offset 0x8D.
",dlharper
16320,Virtualbox uses 100% of CPU when suspending PC,Linux,Linux,VirtualBox 5.0.24,2016-12-23T16:48:45Z,2016-12-23T16:48:45Z,"Hello,
When I suspend the computer while virtualbox is running and then start it again, vboxheadless process use 100% of CPU.

This happens always, every single time.

Ubuntu 16.04

VB log: http://pastebin.com/1PQexHkQ ",Bonomon
16321,Failure when trying to do a second clone from one machine,Windows,Windows,VirtualBox 5.1.12,2016-12-23T17:18:55Z,2016-12-23T17:18:55Z,"I need to make a total of 5 clones from a VHD, all with their own diff drive. See [http://koussilicious.blogspot.ca/2016/12/70-462-training-kit-setup-preparation.html]; these instructions are for Hyper-V but I thought it would work in VirtualBox.

I was able to successfully clone once. But when I did the second, I got this message:

Failed to create a snapshot of the virtual machine 2012R2Parent.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\Will\VirtualBox VMs\2012R2Parent\Snapshots\{a0565d45-af1f-44d6-809a-904e04b32f85}.vhd' does not match UUID {98edf193-685e-4931-8a08-66942b857091} of its parent medium stored in the media registry ('C:\Users\Will\.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

So in thinking it was that you could not have multiple clones, I tried a clone of a clone. The UI allowed this, but when clicking Create, I got a similar message. When trying to do this a second time to get the error details, the clone on a clone was disabled.

One thing to note is that, as soon as the above happened, the parent VHD was hopelessly corrupted, requiring the VM to be deleted and the VHD to also be deleted.",Will Power
15164,"Linux kernel 4.4.0-7.22 (amd64, Ubuntu Xenial) locks up if not using serial output",Linux,Linux,,2016-12-25T22:06:53Z,2016-12-25T22:06:53Z,"Hello!

I'm experiencing a rather strange bug. It's perfectly possible that it's a guest kernel bug, and in that case sorry for the noise.

Linux host, Linux strange 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux, 5.0.15r105570 test build

Guest, created by Vagrant, using Ubuntu's linux-image-4.4.0-7-generic_4.4.0-7.22_amd64.deb kernel package.

If I enable a serial port (COM1, raw file output), the guest boots without a problem (but a bit slowly, because it uses a low baud rate by default, I guess). If on the other hand I don't and it doesn't switch to it, the guest kernel basically stops progress after ""no floppy controllers found"" (or work still pending). Eventually initializes the random pool (random: nonblocking pool initialized), and nothing further. I can type, but of course nothing happens, just keys get echoed. Upon sending a SysRq T (tasks?) only the last lines are visible, but it informed me of a pending console_callback.

Any ideas?",Pas
13053,VirtualBox linked cloned machine (link lost when deleted),other,other,VirtualBox 4.3.12,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
16331,Repairing Windows' VirtualBox v5.1.12 r112440 (Qt5.6.2) reverts back to default path.,other,all,VirtualBox 5.1.12,2016-12-27T19:17:33Z,2016-12-27T19:17:33Z,"Repairing virtualbox failed since it used its default ""C:\Program Files\Oracle\VirtualBox\"" path instead of my custom ""C:\winstuff\VirtualBox\VirtualBox.exe"" location. It should reuse the custom path I had. I had to uninstall and reinstall it to fix it. Originally, I installed in my couple months old 64-bit W7 HPE SP1 machine.",Ant
16332,Guest Windows 10 displays black desktop on second screen,Windows,Windows,VirtualBox 5.1.12,2016-12-28T07:27:35Z,2016-12-28T07:27:35Z,"My Virtualbox is installed in laptop, OS is windows 10, I also install a guest windows 10 to do some other tasks. I have a second screen connected to laptop and the guest windows 10 is displayed on second screen. 

If I don't shutdown/save the guest windows 10 then unplug in the second screen and then plugin second screen again:

1. The guest windows 10 will display a black desktop after I run mstsc on guest windows(even I closed mstsc). If I press Windows key on keyboard, Start menu and taskbar can be displayed on guest, but the desktop is still black. After the Start Menu and taskbar is hidden, all desktop is black again. To show the desktop, I write a bat file to restart explorer.exe, press Windows key + R to run the bat file, then the desktop can be displayed.

2. The virtualbox min bar will be displayed on first screen of laptop

My VirtualBox version is 5.1.12r112440(Qt5.6.2)
Host and Guest are latest Windows 10
Extention is installed on host, guest additional is install on guest and 3D support is open",Peak Zhang
16329,Corruption when accessing files via Shared Folders,Linux,Linux,VirtualBox 5.1.12,2016-12-28T19:36:57Z,2016-12-28T19:36:57Z,"I am seeing intermittent file corruption when checking a borgbackup repository via a Shared Folder

Host is Ubuntu x64 16.04 using Virtualbox 5.1.12
Guest is Ubuntu Mint x64 16.10

Here is the output of 5 sequential runs of the same command to verify the repository, you can see that some detect errors and others don't.  The errors that are detected are different between runs as well.


{{{
jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 273, offset 8]
Index object count mismatch. 117954 != 117952
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 155, offset 2726665]
Index object count mismatch. 117954 != 117951
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backup
}}}


I'm unable to recreate the errors when checking the repository from the host machine.

I've also noticed occasional errors in files hosted on the shared folder in other applications as well.  E.g. unzipping a file, errors about duplicity archive errors etc etc so the problem isn't just limited to borg

I will run memory diagnostics again tonight just to be sure, I've run them before and found no errors.

",jlm
15281,Windows 7 guest hangs reading hard disk,other,other,VirtualBox 5.0.16,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
16343,Guest screen corruption with 3D enabled unless mini-toolbar enabled,Windows,Linux,VirtualBox 5.1.12,2017-01-01T08:50:41Z,2017-01-01T08:50:41Z,"Seems likely this is actually a host problem, given the toolbar's impact.

VirtualBox 5.1.12 (also tested with 5.1.10 and 5.0.30, same results).
W7SP1 x64 host 8GB, Ubuntu MATE 14.04 x64 guest (kernel 3.13.0-106, X 1.15.1), GA, 2GB.
Host graphics: Radeon 7950 running 16.12.1 drivers.

In a fullscreen VM with 3D acceleration enabled, running glxgears (or even just glxinfo) blacks out the entire screen, and regions outside the glx-invoking window don't redraw until damaged. With no changes to host or guest, enabling ""Show in Fullscreen"" for the mini-toolbar makes the display behave correctly. Very bizarre. :)

I also completely uninstalled VirtualBox and reinstalled 5.1.12, no difference.

The guest WM is Marco (Metacity, effectively) and the behavior is the same whether that's running with or without compositing.

Q: Should I duplicate the logfiles in this ticket, or are the copies in the forum enough?
",arQon
16344,macos sierra mouse focus,Mac OS X,other,VirtualBox 5.1.12,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
16345,fatal error while FreeBSD VM is configuring network interface for IPv6,other,other,VirtualBox 5.1.12,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
16346,BIOS date in orgs.asm is always 06/23/99,all,all,VirtualBox 5.1.12,2017-01-02T01:54:52Z,2017-01-02T01:54:52Z,"https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/PC/BIOS/orgs.asm

Notice BIOS_BUILD_DATE is always 06/23/99. I think Win2000 and Win98 often uses this to determine the BIOS date. For example the BIOS date for enabling ACPI in Win2000 is 01/01/99 and in Win98SE is 12/01/99.",Yuhong Bao
16305,Can't start session for virtual machine,Windows,all,VirtualBox 5.1.10,2017-01-03T09:08:43Z,2017-01-03T09:08:43Z,"I've got an error: 

'''Can't start session for virtual machine'''. 

The virtual machine 'MS DOS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VirtualBox VMs\Machines\MS DOS\Logs\VBoxHardening.log'.

Erro code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}



Host - win 7, 64bit. Guest - any vmachine (tried msdos, win xp, win 7, ubuntu and got the same error).

BUT if I start the machine in the background session and then click show (or start background session with interface) - everything works!

Tested on 5.1.10, 5.1.8, 5.1.0 and test build (5.1.11). Seems like an issue with all 5.1.x versions.

Note that 5.0.x works fine on my host.",coldshine
16349,"Linux host, Windows 10 guest: USB headset functions intermittently with Skype",Windows,Windows,VirtualBox 5.1.12,2017-01-03T13:13:02Z,2017-01-03T13:13:02Z,"My system is the following.
Hardware: Lenovo ThinkPad T460
OS: Linux host (kernel 4.8.15, distribution Fedora 25) with Windows 10 guest
VirtualBox: 5.1.12 with extension packs on both ends of the same version
Additional hardware: Logitech USB headset H650e connected via xHCI USB 3.0 controller
Additional software: Skype 7.3.80.105 under Windows 10 guest

Symptoms
- during an audio call via Skype, the microphone of the USB headset will cease to function
- the Skype connection bars turn red and a warning appears that no microphone is connected
- the behaviour sometimes corrects itself but can not be predicted and is hard to reproduce

My VBox.log is attached.",aljperso
16351,"Segfault on Wayland, QTBUG-55583",Linux,other,VirtualBox 5.1.12,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
16353,Sever Clock Drift,Mac OS X,Linux,VirtualBox 5.1.12,2017-01-04T03:11:31Z,2017-01-04T03:11:31Z,"MacOS Sierra Host - Virtualbox Version 5.1.12 r112440 (Qt5.6.2)

Problem on both:

  Guest: ubuntu/xenial64 - 16.04


  Guest: boot2docker (docker-machine create -d virtualbox)

This does not seem to be related to other tickets I found.


Here are some examples:


30 seconds on guest -- 1min40 real time
{{{
ubuntu@ubuntu-xenial:~$ 
while true; do echo $(date -u -Iseconds) == $(curl --silent http://www.timeapi.org/utc/now) ;sleep 10; done
2017-01-04T02:48:35+00:00 == 2017-01-04T03:02:31+00:00
2017-01-04T02:48:46+00:00 == 2017-01-04T03:02:49+00:00
2017-01-04T02:48:56+00:00 == 2017-01-04T03:03:06+00:00
2017-01-04T02:49:06+00:00 == 2017-01-04T03:03:23+00:00
}}}

And here is another: 17 seconds on guest --> 30 seconds on host (real time)
{{{
daniel@darwin:~$ while true; do echo $(docker-machine ssh dev date) == $(date); sleep 10; done
Wed Jan 4 03:01:28 UTC 2017 == Tue 3 Jan 2017 22:06:10 EST
Wed Jan 4 03:01:32 UTC 2017 == Tue 3 Jan 2017 22:06:20 EST
Wed Jan 4 03:01:38 UTC 2017 == Tue 3 Jan 2017 22:06:31 EST
Wed Jan 4 03:01:45 UTC 2017 == Tue 3 Jan 2017 22:06:41 EST
}}}

",daneroo
16359,VBOX XML files are not locked by VBOX Manager instances,Windows,all,VirtualBox 5.1.4,2017-01-05T15:43:42Z,2017-01-05T15:43:42Z,"We have lost snapshots recently because the .vbox XML files are not locked by the Virtualbox Manager. 

Steps to reproduce:
1. Create a new VM in User1 Windows account.
2. Don't quit from the Virtualbox Manager GUI.
3. Switch to Windows user account User2. 
4. Open the same VM in the Virtualbox Manager.
5. Create a new snapshot (Snapshot 1). 
6. Close the Virtualbox Manager in User2 account, logoff from User2.
7. Switch back to User1.  Snapshot 1 is not listed. 
8. Close the Virtualbox Manager.
9. Start the Virtualbox Manager. Snapshot 1 is not listed. 

Expected result: When the User2 opens the VM in the Virtualbox Manager, it should raise an error that this VM is locked by another user. 

These errors never happen intentionally, so it would be great if the Virtualbox Manager could lock the vbox files.

Sometimes we can recover the snapshots by manually recreating the snapshot entries in the vbox XML file, but this is not optimal.

Thank you for your help",Z6543
15751,"Windows VM host crashes randomly, when using Ubuntu 16.04 LTS and 3D is enabled",Windows,Linux,VirtualBox 5.1.2,2017-01-06T01:54:24Z,2017-01-06T01:54:24Z,"I have an Ubuntu 16.04 freshly installed on my system.
Randomly, the VirtualBox host crashes with the following data:

""Virtualbox.exe - Application Error""

""The instruction at 0xd953b275 referenced memory at 0x00000088.  The memory could not be read"".

After a few reinstalls, and searching different settings I quickly figured-out, disabling the 3D acceleration was responsible.  Disabling it and the random crashes were completely gone.

Tried to downgrade to the lastest build of version 5.0, configuring sw + virtual machine with the right additions, but the exact same (random) error occurs.
Browsing several forums, 1 hint I tried were the graphics drivers.  I installed a few different revisions (Intel HD Graphics), now using version 10.18.14.4414  

But doesn't resolve the issue.

I checked the LOG files, as well the VBoxHardening.log file and when the crash occurs, the following 2 lines appear which i assume may be related ...

Since the Virtualbox host itself crashes, I clearly assume it should be some kind of bug when using the 3D enabled, which is in fact handy in Ubuntu desktop environments (drastically increases performance)...",Smoetje
8796,Host-only adapter interface lost it's manual configured ipv4 address,Windows,Windows,VirtualBox 4.0.6,2017-01-06T04:00:56Z,2017-01-06T04:00:56Z,"I have a host-only interface created by 2.x long time ago. After installation of 4.0.6, I find I have to re-configure the ip address of host-only interface after every reboot.
The ip address is manually configured by vbox manager gui, and then I add gateway and dns server in the ipv4 properties。 After reboot，the configuration in the ipv4 properties seems not changed, but in the vbox manager gui, the ip address will be something like ""169.254.4.67"", and the ipconfig.exe command will show the same address.",kidault
16291,Guest SuSe 13.2 freezes on Host Windows 7 when more than 1 processor (core2 quad) is assigned,Windows,Linux,VirtualBox 5.1.10,2017-01-06T10:27:29Z,2017-01-06T10:27:29Z,"This issue is similar to that in [https://www.virtualbox.org/ticket/7619 ticket 7619]. However, the issue occurs with a recent VirtualBox version.

When more than 1 processor is assigned to the Guest (Open SuSe 13.2, XFCE Desktop) it freezes after some time and does not react anymore (commonly after below 1 hour). VirtualBox itself still runs. Pausing the VM or Saving it to the Disk (and resuming) works fine but the Guest is still frozen. The Host is Windows 7 SP1.

When I assign 1 processor it works fine (I worked for 2 month with this 1-processor-setup and experienced some performance problems recently, which is way I came back testing a >1 processor setup. But this is not the topic of this ticket).

3D acceleration is not enabled. The issue seems to be correlating with the usage of Mozilla Firefox and/or Thunderbird - but not exclusively. The freezes occured also without Firefox running (but less ofter). 

The host computer has a Core2 Quad Q9400 Processor. It does not support hyper-threading. I could assign up 8 cores in the settings dialog. I mention this because I found some discussion on whether cores or virtual processes are assigned. Idependent whether the processor supports hyper-threading or not, there should be only 4 cores available.

Currently, I am using VirtualBox v5.1.10 but the issue occured also in v5.1.6 and v5.1.8.

Since the number of Core2 processors is declining this issue probably has a quite low priority.",neumannd
16362,Cannot create solid state drives when VM is running,Mac OS X,Linux,VirtualBox 5.0.30,2017-01-06T15:38:34Z,2017-01-06T15:38:34Z,"I want to simulate the replacement of a solid state drive while the system is running.

I have a VM (guest OS: ubuntu 14:04), with a SATA controller of 4 hotpluggable disks. The solid-state drive is on port 3.

I first create a new medium to represent the replacement disk:
$ vboxmanage createmedium disk --filename disks/ssd6.vmdk --size 8192 --format VMDK
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Medium created. UUID: 9532c0bc-f14b-4f0c-a4df-b366024ed58d

Then I remove the solid state drive from the VM:
$vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=none

Then I want to replace it with a new virtual Solid-State Drive:
$ vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=disks/ssd6.vmdk --type hdd --nonrotational on

I get the following  error:
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""NonRotationalDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 837 of file VBoxManageStorageController.cpp


If I omit the option --nonrotational on, the command succeeds, but it's added as a regular (hotpluggable) hard disk. 






",jkv
16358,USB MSD device BBB (bulk only) transfer fails due to CBW/CSW tag mismatch,Windows,other,VirtualBox 5.1.12,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
16364,SYSTEM_SERVICE_EXCEPTION BSD in Windows 10 x64 guest on Windows 7 x64 host,Windows,Windows,VirtualBox 5.1.12,2017-01-07T19:23:27Z,2017-01-07T19:23:27Z,"I'm getting a SYSTEM_SERVICE_EXCEPTION blue screen in Windows Pro 10 x64 guest on Windows 7 x64 host after I've updated VB to ver. 5.1.8. Until then (in ver. 5.1.6) everything was working just fine. Back then I couldn't find a ticket or a topic about a similar issue and I thought will be fixed in the next changes but it didn't. I've updated VB to the latest 5.1.12 version and I'm having the same issue. I've tried to reinstall the Windows 10 guest but the process crashes at some point with the same blue screen error.

I have 2 other VB machines running without issues with the latest VB 5.1.12 (Windows ThinPC x86 and Windows 7 Ultimate x64 same as the host OS).

HOST: Notebook HP Pavilion DV7-1005TX (with Virtualization Support enabled in Bios), Windows 7 Ultimate x64, 8 Gb RAM, video Nvidia 9600M GT on 17 inch display, Bitdefender Antivirus Free Edition.

GUEST: Windows 10 Pro x64 (September 2015)

I'm not an IT professional or expert (just a mechanical engineer). I usually don't change anything that is working, unless it's a critical update available. I never tried to boost, overclock, tune-up or anything beyond my limits as a simple regular Windows PC user.

Thank you.",Mike Skywalker
16367,"When you start the VM that is in the ""Save State"", i receive the error message ""Failed to look for handy pages; rc = VERR_NO_MEMORY"".",Windows,Windows,VirtualBox 5.1.12,2017-01-09T08:31:07Z,2017-01-09T08:31:07Z,"Ladies and Gentlemen,

Good Morning.

I have a machine with the Windows Vista Home Basic 32-bit operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has an Intel Pentium (R) Dual CPU T2370 of 1.73Ghz, with RAM of 2.00 GB, in this machine. I created a virtual machine with the Windows 7 Home Premium 32-bit (guest) operating system, with Service Pack 1 installed, as well as all the updates for that system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the version ""VirtualBox-5.1.2-108956-Win.exe"", since then I have updated VirtualBox with every release version, until the version ""VirtualBox-5.1.12-112440-Win.exe "". The virtual machine was in ""Save State"" in the ""VirtualBox-5.1.12-112440-Win.exe"" version. When I started Virtual Machine again with the following error message:

00: 00: 47.280263 PGM: Failed to look for handy pages; Rc = VERR_NO_MEMORY rcAlloc = VINF_SUCCESS rcSeed = VINF_SUCCESS cHandyPages = 0x8
00: 00: 47.280287 cAllPages = 0x5624d cPrivatePages = 0x4adb7 cSharedPages = 0x0 cZeroPages = 0xb46d",MFS68
10611,High CPU usage from interrupts (20% on 8 idle processors),Linux,Windows,VirtualBox 4.1.16,2017-01-10T16:55:06Z,2017-01-10T16:55:06Z,"The idle guest OS has a high CPU usage from interrupts, consuming around 20-25% of the 8 available virtual processors. When load increases so do the interrupts. If I drop the number of processors then the usage from interrupts drops substantially.

Number of processors with corresponding CPU usage from interrupts:
* 2 processors = 5%
* 4 processors = 4%
* 6 processors = 5%
* 8 processors = 20-25%

Host: Debian 6.0.5 [[br]]
Guest: Windows 7 SP1 [[br]]
VirtualBox: 4.1.16 [[br]]

Specs of the physical host: [[br]]
2 x Xeon E5620 @ 2.40GHz, 8 cores in total, 24GB RAM",Denis Kozlov
16369,Configuring VirtualBox OSE to build with OpenSSL 1.1.0 on Windows,Windows,all,VirtualBox 5.1.12,2017-01-11T09:21:04Z,2017-01-11T09:21:04Z,"Currently it is not possible to configure VBox OSE to compile with OpenSSL 1.1.0 libraries on Windows.
The configure.vbs script fails:


{{{
Checking for openssl...
error: Can't locate openssl. Please consult the configure.log and the build requirements.
}}}

The problem is that with OpenSSL 1.1.0 the libraries are now called libcrypto.lib and libssl.lib. However configure.vbs is still looking for libeay32.lib and ssleay32.lib.",IndyJones
16374,"Problem with usb flash disk: host = W10, guest=W7 and XP",Windows,Windows,VirtualBox 5.1.12,2017-01-11T19:32:01Z,2017-01-11T19:32:01Z,"I use win 10 64 bit laptop and virtualbox  5.1.12. When I use VM with W7 or XP: USB flash disk work randomly. Most of the time : doesn't work. When I catch usb device on VM, it disappear on host , doesn't appear on guest and usb device disappear of the list of USB device. You have to disconnect USB flash disk to have it on host.
All VM I use, work very well with host:W7 32b.
I have reinstall lot of time: virtualbox, extension pack and addition guests.
Bests regards.
",galexis
16371,After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch,Windows,Windows,VirtualBox 5.1.12,2017-01-12T16:15:58Z,2017-01-12T16:15:58Z,"After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch, below is the error I am receiving. I uninstalled and reinstalled Virtual Box, as well as tried starting in Win 8 Compatibility mode. Let me know if you need any other info.
{{{
Log Name:      Application
Source:        Application Error
Date:          1/10/2017 11:07:04 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CAT-670ZH72.catapultsystems.com
Description:
Faulting application name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Faulting module name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Exception code: 0xc0000005
Fault offset: 0x0000000000013a1d
Faulting process id: 0x2470
Faulting application start time: 0x01d26b63f72f8901
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: e55f15cb-c698-496e-8288-7f3763f5933a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""Application Error"" />
    <EventID Qualifiers=""0"">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2017-01-10T17:07:04.074275800Z"" />
    <EventRecordID>496</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CAT-670ZH72.catapultsystems.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>c0000005</Data>
    <Data>0000000000013a1d</Data>
    <Data>2470</Data>
    <Data>01d26b63f72f8901</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>e55f15cb-c698-496e-8288-7f3763f5933a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
}}}",Bobbyw87
16079,Windows guest freezes when partitioning/formatting NVMe drive,other,Windows,VirtualBox 5.1.8,2017-01-12T18:05:47Z,2017-01-12T18:05:47Z,"Windows 10 1607 guest freezes when trying to partition/format a blank NVMe drive. This happens if the VM has only n=1 processor. If the VM has n=4 processors, then the guest does not freeze. Other values for n have not been tried.",Sven
11357,Mouse Lag in Age of Empires 2,Mac OS X,Windows,VirtualBox 4.2.6,2017-01-12T19:19:10Z,2017-01-12T19:19:10Z,"I had this problem several years ago on virtualbox but it was fixed. In the last two public releases 4.18 4.20. The problem seems to have reappeared, and that is the mouse lags on Age of Empires II AOE2 during game play no matter which computer I use. Several months ago it was working fine. I've tried it on 4 different machines some are better, but none are right.

Host MacOSX Mountain Lion 10.8
Guest Windows XP SP3
DirectX 9c

It's only in game play that the mouse lags by .5 to 1 second. The game menu is fine. Network versus standalone is exactly the same.

Medal of Honor Breakthrough runs perfect. I've never had it run on a real PC as well as it does on Virtualbox 

the latest 4.2.6 still has the mouse lag in Age of Empires 2 in Windows XP. Same problem in both SP3 and SP2. I also did a clean install with no better results. Because it runs so well with 3d it makes me think it's in the 2d part of the directX video driver or something with the mouse driver

BUT I think I figured out what is going on. The video driver appears to have gained a bug in 4.18 or thereabouts and forward.

If I turn off all acceleration on the slide bar in troubleshooting in Windows XP advanced settings (even keeping Enable Write combining checked) it will play without any lag. I don't know how to address the issue though. It's not smooth anymore, but the lag is gone and makes it useable.

I don't have a log, but I could get one if needed. It doesn't crash at all or give any errors so I'm not sure what I would send.",BryceSteiner
16388,Guest CPU utilization pegged at 100% making the guest unusable,Windows,Windows,VirtualBox 5.1.12,2017-01-15T22:28:42Z,2017-01-15T22:28:42Z,"Pretty much any activity in the guest pegs the guest CPU utilization at 100% for extended periods of time (for example client booting takes half an hour or more) during which the client is unusable. This affects Windows 7 and 10 clients, but Windows XP and OS/2 clients seem to be unaffected.
This has been introduced by either host upgrade from Windows 7 to version 10, or in VBox version 5.0 or 5.1. Last time a Windows 7 client was working correctly was on Windows 7 host and VBox version 4.3.x. Like I mentioned, multiple clients are affected, all are either Windows 7 or 10, both 32 and 64 bit.
",Rafcio
16392,BSOD SYSTEM_SERVICE_EXCEPTION on Windows 10,Windows,Linux,VirtualBox 5.1.12,2017-01-16T13:48:12Z,2017-01-16T13:48:12Z,"I use a VM from MongoDB University course M310.
When I run the VM I get BSOD.",enabokov
16385,PCI passthrought works incorrectly with I/O ports,Linux,Linux,VirtualBox 5.0.20,2017-01-16T15:45:15Z,2017-01-16T15:45:15Z,"Hello,

I am using virtualBox 5.0.20 OSS with extension pack

# VBoxManage list extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.0.20
Revision:     106931
Edition:      
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption.
VRDE Module:  VBoxVRDP
Usable:       true 
Why unusable:

Host kernel is 3.16.7
Guest kernel is 4.9.0

On the host machine I have the following PCI device:

04:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 19
        Region 1: I/O ports at e080 [size=128]
        Region 2: I/O ports at e100 [size=64]
        Region 3: I/O ports at e140 [size=16]
        Kernel driver in use: pci-stub
        Kernel modules: mxser

When passed into the guest system it looks like the following:

03:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 17
        Region 1: I/O ports at e000 [size=128]
        Region 2: I/O ports at e080 [size=64]
        Region 3: I/O ports at e0c0 [size=16]

However, access to I/O ports doesn't work in guest system.

To test I/O ports the following simple code snipped is used: https://gist.github.com/matwey/b42f8b9fb50ab8c603d120c54d04c9be

On the host (when accessed to 0xe100) result is the following:

# ./a.out 
64: FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00

On the guest (when accessed to 0xe080) result is the following:

# ./a.out 
64: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF",Matwey V. Kornilov
16335,"VirtualBox automatically forces shut down of guest before displaying ""new version available"" dialog",Windows,Linux,VirtualBox 5.1.12,2017-01-18T10:09:19Z,2017-01-18T10:09:19Z,"VirtualBox version 5.x (any since 5.0) forces a shutdown of a running guest process to display a dialog stating that there is a new version available.

Steps to reproduce:
1. Install and run a guest operating system (Fedora Linux 23/24/25 in this case(s)).
2. Leave the guest operating system running on the host (Win10 in this case) for many weeks without issue.
3. When a new version of VirtualBox is released, the guest is automatically forced to shut down, and then the VirtualBox GUI displays a notice dialog box stating ""VirtualBox - Information: A new version of VirtualBox is has been released!...."".

Expected behavior:
Don't shut down my running guest operating system to display a simple informational dialog.

Notes:
This has happened to me on various VirtualBox versions 5.0.x and 5.1.x for over 10 months now.  VirtualBox guest tools are installed and are always updated with the host update.  Although I list a Windows 10 host and Fedora guest above, I have had the same exact issue happen on a Fedora 23/24 host and Windows 7 guest, with the same 5.x series of VirtualBox (I did run version VirtualBox 4.x on that combination for a while, however I never experienced this issue).

",gats
16339,"The State of the VM has changed from RUNNING to ' GURU_MEDITATION '. Error ""(VERR_PATM_IPE_TRAP_IN_PATCH_CODE)""",Windows,Windows,VirtualBox 5.1.12,2017-01-18T10:13:27Z,2017-01-18T10:13:27Z,"Gentlemen/Ladies,

Good morning.

I have a 32-bit Windows Vista Home Basic operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 2.00 GB. In this machine I created a virtual machine with the Windows 7 Home Premium 32-bit operating system (guest), with Service Pack 1 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the ""!VirtualBox-5.1.2-108956-Win.exe"" version, since I have been updating !VirtualBox with each release version until I get the version ""!VirtualBox-5.1.12-112440-Win.exe"" . I noticed that the error messages were intencificated from the ante-penultimate version. The virtual machine was in ""Save State"" by the ""!VirtualBox-5.1.10-112026-Win.exe"" version, when I upgraded to the ""!VirtualBox-5.1.12-112440-Win.exe"" version. And several times this week, I entered the ""Machine / Close / Save State"" menu. Saving the state of the machine so I could continue my work from where I left off. In the last two days after starting the machine to continue my work in the state where I stopped, there were some errors, but I would close everything and then start the process again and the virtual machine would go up normally. Before Yesterday after this procedure, I worked normally and when restarting Virtual Machine, a screen appeared informing that the virtual machine suffered serious failures and suggested to me that I pressed the ""Ok"" button to leave the virtual machine and to contact the community !VirtualBox to get help with the problem. Referring to the ""VBox.log"" and ""VBox.png"" files in the ""C: \ Users \ Administrator \ !VirtualBox VMs \ Logs"" directory. Editing the file ""VBox.log"" I extract the following text below:
{{{
Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
04: 57: 53.186726 Console: Machine state changed to 'GuruMeditation'
04: 57: 53.480547

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!
04: 57: 53.480551 !!
04: 57: 53.480552 !! VCPU0: Guru Meditation -1432 (VERR_PATM_IPE_TRAP_IN_PATCH_CODE)
}}}
I will forward you these and the other log files contained in this
folder.

Note: In the virtual machine I made the Microsoft SQL Server 2014 Service Pack 1 Express Downloads, all the Microsoft SQL Server 2014 SP1 Feature Packs files, and the IIS 10 Express download and installation, after that I rebooted the machine and then the error already described appeared. I wonder If this virtual machine is compromised because of these errors and if has how to recover it?",MFS68
16390,Problem with graphic interface,other,other,VirtualBox 5.1.10,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
16398,Boot up of Windows 7 VM running on Windows 10 post upgrade to v5.0.32 crashed,Windows,Windows,VirtualBox 5.0.32,2017-01-18T16:58:31Z,2017-01-18T16:58:31Z,"Windows 10 Host
Windows 7 Guest
vBox v5.0.32

Post upgrade to VirtualBox v5.0.32 the Windows 7 Guest crashed during boot up.
",n3kfh
15970,Failed to create the host-only adapter (Windows 7),Windows,all,VirtualBox 5.1.6,2017-01-19T21:35:50Z,2017-01-19T21:35:50Z,"I cannot create host-only adapter neither with the command 
{{{
VBoxManage.exe hostonlyif create
}}}
nor from UI. I get error:

{{{
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 VirtualBoxWrap, interface IVirtualBox
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}

When I try to do it from UI I get error message with the text:
{{{
Failed to create the host network interface.

Could not operate the communication channel (VERR_BROKEN_PIPE).

Result Code: E_FAIL (0x80004005)
Component: VirtualBoxWrap
Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
}}}

This doesn't allow me to use Docker so it is blocker for me.

It is reproducable with older 5.0.* versions too. I tried to reinstall VirtualBox, install with ""-msiparams NETWORKTYPE=NDIS5"" parameter, reset driver cache in ""windir%\inf\INFCACHE.1"" without any result.

After error there is new ""Unknown Device"" in Windows Device Manager.

Lines added to setupapi.app.log after failure:
{{{
>>>  [Build Driver List - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:22.977
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
     cpy: Policy is set to make all digital signatures equal.
!    sig: No installed catalogs matching catalog name '' were found that validated the file.
!    sig: Error 1168: Element not found.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x00000057)
!    sig: Error 87: The parameter is incorrect.
!    sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003)
!    sig: Error 0x80092003: An error occurred while reading or writing to a file.
<<<  Section end 2016/09/22 16:00:23.698
<<<  [Exit status: SUCCESS]


>>>  [DIF_REGISTERDEVICE - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.761
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.763
<<<  [Exit status: SUCCESS]


>>>  [DIF_ALLOW_INSTALL - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.763
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.765
<<<  [Exit status: SUCCESS (DI_DO_DEFAULT)]


>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.765
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<ins>
}}}

also (which looks weird) some lines are added to section dated 2015/09/23:
{{{
>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2015/09/23 20:02:36.865
...
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     dvi: Committing file queue...
     flq: CopyFile: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\Temp\OLD1D54.tmp'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_neutral_978f7ab983bb20bd\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq: MoveFile: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq:       to: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
}}}


Please let me know what information may I provide to help to fix this defect or find some workaround.

OS: Windows 7, 64bit, SP1.

I have Aventail VPN installed but it is inactive when I reproduce the problem. 
",Dron007
16383,cannot ping but can ssh and http,Windows,Linux,VirtualBox 5.1.12,2017-01-20T02:17:57Z,2017-01-20T02:17:57Z,"Host: Windows 10
Guest: Centos 5
Network: NAT

Why: cannot ping in guest, but can http or ssh.

Debug: 
 1. Use tcpdump in guest and host, will see icmp request is sent to host and host resent this packet to the target, but after got icmp reply, host will try to resent reply to 10.96.1.19, then return ""unreachable network""
 1. Try to capture virtual machine packet by(there is only lo0 and eth0 interface in my guest):
{{{
VBoxManage.exe modifyvm ""redhat32"" --nictrace1 on --nictracefile1 c:\Users\xxxx\netlog.pcap
}}}
 But nothing is logged.
",JacksonZheng
16410,Keyboard capturing sometimes not working,Linux,Windows,VirtualBox 5.1.14,2017-01-20T19:04:41Z,2017-01-20T19:04:41Z,Since upgrade to 5.1.12 my keyboard is sometimes not automatically captured when I change between host and guest. I'm running a Windows 7 Professional guest on a Ubuntu 16.04 host with current host extensions installed.,Mellon
16341,With 3D Enabled OpenGL apps fail to work in Stretch Client on Jessie Host,Linux,Linux,VirtualBox 5.1.12,2017-01-20T21:03:13Z,2017-01-20T21:03:13Z,"Using the following as OpenGL Test Applications:  KDE Plasma (Stretch), glxgears(Stretch), QT5 Development Tools (Stretch & Download), blender (Stretch).

Toggled Setting: Settings/Display/3D Acceleration (3D_A) in VirtualBox Manager.
* When 3D_A “IS Enabled” VM Guest OpenGL test applications, “Do not work!”.
* When 3D_A “IS Not Enabled” VM Guest OpenGL test applications, “Do work!”.

Note: It would be nice to track this down before Stretch transitions to stable and have it included!

Virtualbox Version:
Jessie sources.list:
deb http://download.virtualbox.org/virtualbox/debian jessie contrib
Virtual Box Version 5.1.12 r112440 (Qt5.3.2)

Virtualbox Guest Additions Version:
VBoxGuestAdditions_5.1.12.iso

NVIDIA Driver Used:
NVIDIA-Linux-x86_64-375.26.run
Both: Titan Black (Kepler) & GTX-1060 (Pascal) showed the same results.

Host Kernel (uname -r):
3.16.0-4-amd64

Guest Kernel (uname -r):
4.8.0-2-amd64

Much work correctly:  In all the test, Jessie (host) neither hung nor needed to be rebooted;   One VM did not effect another;  VM Manager neither hung nor needed to be rebooted do to a failure; sharing worked (within VM KDE Plasma did not mount share correctly when 3D_A was not enalbed.);  copy/paste worked; issues on one VM did not impact other VMs; the base guest Linux kernel did not show instability even when there were failures ongoing; with 3D unchecked OpenGl applications seemed to work.  More testing is needed.

See attachment for more details or the links below where it is also posted to support the stretch alpha8 installation testing process.

Tests were conducted using Stretch Alpha8 Install process.

[https://lists.debian.org/debian-boot/2016/12/msg00275.html Related Post]
See Attachment: hkb_stretch_20161227_1000.pdf
",Hal B.
16411,Fails to transfer binary values copy/paste clipboard to and from host/guest,Windows,Windows,VirtualBox 5.1.14,2017-01-23T13:20:41Z,2017-01-23T13:20:41Z,"Try to copy binary value from Windows registry either at host or guest
 and to paste to guest/host.

Expected - ordinary copy/paste.

While ordinary text is copy/past -ed as expected.
",MikhailRokhin
15962,Wayland Login Manager Borks Login process in Fedora 24,other,Linux,VirtualBox 5.1.6,2017-01-23T15:07:39Z,2017-01-23T15:07:39Z,"Host: MacOSX 10.11.6 Guest: Fedora 24 VB 5.1.6
I am not sure when this happened, but recently.

In the current version of Fedora 24 the Wayland Login Manager is used. Booting Fedora
give a blank grey screen.

If I manually refresh the screen ( minimize or drag a window over the VM window) My login
name will appear.

If I click on the login name and manually refresh the screen the password box will appear.

If I click on the password box and blind type ( no dots appear as I type) the password and hit 
return I will be presented with the desktop and everything ( except sound) works. Bummer.

If I go to /etc/gdm/custom.conf and uncomment out the line:
{{{
  # WaylandEnable=false
}}}
and reboot there is no problem ( well sound randomly appears and vanishes ).

I think Wayland will be the default in Fedora 25 so y'all might want to find out
why the login screen is not properly being refreshed.",jerrysVB
16403,VBox on linux host randomly power off.,Linux,Windows,VirtualBox 5.1.10,2017-01-23T15:55:09Z,2017-01-23T15:55:09Z,"I have a problem like https://www.virtualbox.org/ticket/10831/.
I start two Windows2012R2 virtual machines headless on console CentOS7.1.
Sometimes vms randomly crash (not both simultaneously). 

",Nika
16360,vbox guest additions disable gnome graphical login,Mac OS X,Linux,VirtualBox 5.1.12,2017-01-23T20:31:01Z,2017-01-23T20:31:01Z,"There appears to be a bug with the VirtualBox Guest Additions for Linux that results in this error:

'''gnome-keyring-daemon[PID]: failed to unlock login keyring on startup'''

System Installs/Updates and configurations seem to behave as expected. 

However, I've performed this process 4 times; after installing the guest additions (either from the GUI/or in the terminal) the Gnome GUI login becomes unusable. SSH Logins still work as they are not reliant on the gnome-keyring. 

I have all the logs to support this issue. I will make the attempt to attach them. If they are not present please contact me with other options. 

== The Mechanics ==
'''The Host''' OS X Yosemite (10.10.5)
{{{
vboxmanage list hostinfo 
Host Information:

Host time: 2017-01-05T18:50:17.676000000Z
Processor online count: 8
Processor count: 8
Processor online core count: 4
Processor core count: 4
Processor supports HW virtualization: yes
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: yes
Processor#0 speed: 2600 MHz
Processor#0 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#1 speed: 2600 MHz
Processor#1 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#2 speed: 2600 MHz
Processor#2 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#3 speed: 2600 MHz
Processor#3 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#4 speed: 2600 MHz
Processor#4 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#5 speed: 2600 MHz
Processor#5 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#6 speed: 2600 MHz
Processor#6 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Processor#7 speed: 2600 MHz
Processor#7 description: Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Memory size: 16384 MByte
Memory available: 3557 MByte
Operating system: Darwin
Operating system version: 14.5.0
}}}

'''VirtualBox'''
{{{
vboxmanage --version
5.1.12r112440
}}}

'''The Guest'''
{{{
vboxmanage showvminfo ""F25_max""
Name:            F25_max
Groups:          /client_linux
Guest OS:        Fedora (64-bit)
UUID:            997eb8e8-ee61-461e-a8ea-5992ce5fecae
Config file:     /Users/myUser/vms/vbox/client_linux/F25_max/F25_max.vbox
Snapshot folder: /Users/myUser/vms/vbox/client_linux/F25_max/Snapshots
Log folder:      /Users/myUser/vms/vbox/client_linux/F25_max/Logs
Hardware UUID:   997eb8e8-ee61-461e-a8ea-5992ce5fecae
Memory size:     4096MB
Page Fusion:     off
VRAM size:       64MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:           running (since 2017-01-05T14:30:03.103000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (1, 0): /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso (UUID: 8d677575-7f59-45ab-b7e4-00348ca43f57) (temp eject)
SATA (0, 0): /Users/myUser/vms/vbox/client_linux/F25_max/F25_max.vdi (UUID: 237f88ad-0eb4-496e-a1bb-36b9c4dddc0b)
NIC 1:           MAC: 080027EE946B, Attachment: Bridged Interface 'en0: Wi-Fi (AirPort)', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: CoreAudio, Controller: AC97, Codec: AD1980)
Clipboard Mode:  Bidirectional
Drag and drop Mode: disabled
Session name:    GUI/Qt
Video mode:      800x600x32 at 0,0 enabled
VRDE:            disabled
USB:             enabled
EHCI:            enabled
XHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  

Name: 'code', Host path: '/Users/myUser/code' (machine mapping), writable

VRDE Connection:    not active
Clients so far:     0

Video capturing:    not active
Capture screens:    0
Capture file:       /Users/myUser/vms/vbox/client_linux/F25_max/F25_max.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Description:
F25 build for Max.
Guest:

Configured memory balloon size:      0 MB
OS type:                             Linux26_64
Additions run level:                 2
Additions version:                   5.1.12 r112440


Guest Facilities:

Facility ""VirtualBox Base Driver"": active/running (last update: 2017/01/05 17:08:18 UTC)
Facility ""VirtualBox System Service"": active/running (last update: 2017/01/05 17:22:11 UTC)
Facility ""Seamless Mode"": not active (last update: 2017/01/05 17:08:18 UTC)
Facility ""Graphics Mode"": not active (last update: 2017/01/05 17:08:18 UTC)
}}}



== The Process ==

Install F25 OS: 
  * accept all defaults.
  * Set root password
  * Create new user

Reboot the system:

`sudo poweroff --reboot`
--------------------------------------------------------------------------------

Gnome GUI login: successful.

Modify sudoers file: only the last line has changed.
Before:

{{{
$ sudo egrep -v '^(#|$)' /etc/sudoers
....
%wheel	ALL=(ALL)	ALL}}}

After:

{{{$ sudo egrep -v '^(#|$)' /etc/sudoers
Defaults   !visiblepw
Defaults    env_reset
Defaults    env_keep =  ""COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS""
Defaults    env_keep += ""MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE""
Defaults    env_keep += ""LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES""
Defaults    env_keep += ""LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE""
Defaults    env_keep += ""LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY""
Defaults    secure_path = /sbin:/bin:/usr/sbin:/usr/bin
root	ALL=(ALL) 	ALL
%wheel	ALL=(ALL)	NOPASSWD: ALL
}}}


ssh login: successful.


{{{
journalctl --list-boots
 0 94d4de4733c640ce8722b8705438184e Wed 2017-01-04 19:15:46 CST—Wed 2017-01-04 19:31:02 CST
}}}

Full log since last boot:

`journalctl -b > boot-0.out`

Logged errors since last boot:

`journalctl -b -p err > boot-0-errors.out`



'''Update OS'''

`sudo dnf -y upgrade | tee -a dnf-upgrade.out`

Packages, versions, etc:

`rpm -qa --queryformat ""%{NAME}-%{VERSION}-%{RELEASE}\n"" > rpm-upgrade-packages.out`

Reboot the system:

`sudo poweroff --reboot`


SEE Logs: 
  * boot-0.out
  * boot-0-errors.out
  * dnf-upgrade.out
  * rpm-upgrade-packages.out

--------------------------------------------------------------------------------


Gnome GUI login: successful.
ssh login: successful.


{{{
journalctl --list-boots
-1 94d4de4733c640ce8722b8705438184e Wed 2017-01-04 19:15:46 CST—Wed 2017-01-04 19:55:32 CST
 0 e9c7b5d03ef943afa2617f0d898f1bc6 Wed 2017-01-04 19:55:40 CST—Wed 2017-01-04 19:58:05 CST
}}}

Full log since last boot:

`journalctl -b > logs/boot-1.out`

Logged errors since last boot:

`journalctl -b -p err > logs/boot-1-errors.out`



Prep to install VirtualBox

Add ENV VARS to `~/.bashrc` (Under: User specific aliases and functions)

{{{
$ cat ~/.bashrc 
# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
	. /etc/bashrc
fi

# Uncomment the following line if you don't like systemctl's auto-paging feature:
# export SYSTEMD_PAGER=

# User specific aliases and functions
############################################################################### 
###                                  System                                 ### 
############################################################################### 
export KERN_DIR=""/usr/src/kernels/$(uname -r)""

############################################################################### 
###                                VirtualBox                               ### 
############################################################################### 
export VBOX_USER_HOME=""$HOME/vms""
}}}


Source-in ~/.bashrc

`source ~/.bashrc`

{{{
echo ""$KERN_DIR""
/usr/src/kernels/4.8.15-300.fc25.x86_64

uname -a
Linux guihost 4.8.15-300.fc25.x86_64 #1 SMP Thu Dec 15 23:10:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

echo ""$VBOX_USER_HOME""
/home/myUser/vms
}}}


Update OS

`sudo dnf -y install dkms kernel-headers gcc kernel-devel  | tee -a logs/dnf-install-vbox-support.out`

Packages, versions, etc:

`rpm -qa --queryformat ""%{NAME}-%{VERSION}-%{RELEASE}\n"" > logs/rpm-post-vbox-support.out`


{{{
diff logs/rpm-upgrade-packages.out logs/rpm-post-vbox-support.out 
53a54
> dkms-2.3-1.20161202gitde1dca9.fc25
1452a1454
> kernel-devel-4.8.15-300.fc25
}}}

Reboot the system:

`sudo poweroff --reboot`

SEE Logs: 
  * boot-1.out
  * boot-1-errors.out
  * dnf-install-vbox-support.out
  * rpm-post-vbox-support.out


--------------------------------------------------------------------------------


Gnome GUI login: successful.
ssh login: successful.


{{{
journalctl --list-boots
-2 94d4de4733c640ce8722b8705438184e Wed 2017-01-04 19:15:46 CST—Wed 2017-01-04 19:55:32 CST
-1 e9c7b5d03ef943afa2617f0d898f1bc6 Wed 2017-01-04 19:55:40 CST—Wed 2017-01-04 20:09:49 CST
 0 bd1ee979bf85487ca8fb2d05ed94167b Wed 2017-01-04 20:09:57 CST—Wed 2017-01-04 20:11:16 CST
}}}


Full log since last boot:

`journalctl -b > logs/boot-2.out`

Logged errors since last boot:

`journalctl -b -p err > logs/boot-2-errors.out`


Verify variables still expand properly:

{{{
echo ""$KERN_DIR""
/usr/src/kernels/4.8.15-300.fc25.x86_64

uname -a
Linux guihost 4.8.15-300.fc25.x86_64 #1 SMP Thu Dec 15 23:10:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

echo ""$VBOX_USER_HOME""
/home/myUser/vms
}}}
----------

Check SELinux Issues:
{{{
sudo ausearch -m avc > logs/boot-2-avcs.out
----
time->Wed Jan  4 19:41:30 2017
type=AVC msg=audit(1483580490.614:387): avc:  denied  { create } for  pid=1 comm=""systemd"" scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=unix_stream_socket permissive=0

date -d @1483580490.614
Wed Jan  4 19:41:30 CST 2017
}}}

The Fix:
{{{
sudo ausearch -c 'systemd' --raw | audit2allow -M  systemdCreate
sudo semodule -i systemdCreate.pp
}}}

----------

Reboot the system:

`sudo poweroff --reboot`

SEE Logs: 
  * boot-2.out
  * boot-2-errors.out
  * logs/boot-2-avcs.out
  * SELinux Policy: logs/selinux/systemdCreate.pp

--------------------------------------------------------------------------------


Gnome GUI login: successful.
ssh login: successful.


{{{
journalctl --list-boots
-3 94d4de4733c640ce8722b8705438184e Wed 2017-01-04 19:15:46 CST—Wed 2017-01-04 19:55:32 CST
-2 e9c7b5d03ef943afa2617f0d898f1bc6 Wed 2017-01-04 19:55:40 CST—Wed 2017-01-04 20:09:49 CST
-1 bd1ee979bf85487ca8fb2d05ed94167b Wed 2017-01-04 20:09:57 CST—Thu 2017-01-05 04:54:52 CST
 0 fe804aceaae24d818fd2beb53f7a3333 Thu 2017-01-05 04:43:15 CST—Thu 2017-01-05 11:04:10 CST
}}}


Full log since last boot:

`journalctl -b > logs/boot-3.out`

Logged errors since last boot:

`journalctl -b -p err > logs/boot-3-errors.out`

  * Still nothing related to the gnome-keyring.

----------

Check SELinux Issues:

`sudo ausearch -m avc > logs/boot-3-avcs.out`  

   * Nothing new since the last check.

----------

Install the vbox guest additions:

1. Insert the CD (from VM menu)
2. GUI: authenticate 
3. Installed without errors to stdOut
4. Saved logs:
      `journalctl -b -p err > logs/boot-3-errors-vbox.out` 
      (no vbox-related errors)
5. Saved logs:
      `journalctl -b | grep vboxadd.sh > logs/boot-3-vbox-install.out`


Reboot the system:

`sudo poweroff --reboot`

SEE Logs: 
  * logs/boot-3.out
  * logs/boot-3-errors.out
  * logs/boot-3-avcs.out
  * logs/boot-3-errors-vbox.out
  * logs/boot-3-vbox-install.out
  * SELinux Policy: logs/selinux/systemdCreate.pp

--------------------------------------------------------------------------------


ssh login: successful.


{{{
journalctl --list-boots
-4 94d4de4733c640ce8722b8705438184e Wed 2017-01-04 19:15:46 CST—Wed 2017-01-04 19:55:32 CST
-3 e9c7b5d03ef943afa2617f0d898f1bc6 Wed 2017-01-04 19:55:40 CST—Wed 2017-01-04 20:09:49 CST
-2 bd1ee979bf85487ca8fb2d05ed94167b Wed 2017-01-04 20:09:57 CST—Thu 2017-01-05 04:54:52 CST
-1 fe804aceaae24d818fd2beb53f7a3333 Thu 2017-01-05 04:43:15 CST—Thu 2017-01-05 11:21:49 CST
 0 decb47c63de742689f3b497016126f04 Thu 2017-01-05 05:01:51 CST—Thu 2017-01-05 11:24:02 CST
}}}


Full log since last boot:

`journalctl -b > logs/boot-4.out`

Logged errors since last boot:

`journalctl -b -p err > logs/boot-4-errors.out`
  * ERRORS: gnome-shell/pulseaudio

----------

Check SELinux Issues:

`sudo ausearch -m avc > logs/boot-4-avcs.out`
  * ERRORS: gnome-shell/pulseaudio

----------

Check running processes: (before first login attempt)
{{{
ps aux | grep key
myUser    1688  0.0  0.0 119372   912 pts/0    S+   11:32   0:00 grep --color=auto key
}}}


Gnome GUI login: FAIL.
These log entries detail a gnome/GUI login failure: attempt 1
{{{
Jan 05 11:29:15 guihost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm=""systemd"" exe=""/usr/lib/systemd/systemd"" hostname=? addr=? terminal=? res=success'
Jan 05 11:29:24 guihost audit[1568]: USER_AUTH pid=1568 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix,pam_gnome_keyring acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty1 res=success'
Jan 05 11:29:24 guihost audit[1568]: USER_ACCT pid=1568 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty1 res=success'
Jan 05 11:29:24 guihost audit[1568]: CRED_ACQ pid=1568 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix,pam_gnome_keyring acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty1 res=success'
Jan 05 11:29:24 guihost audit[1568]: USER_ROLE_CHANGE pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty2 res=success'
Jan 05 11:29:24 guihost systemd[1]: Started Session 4 of user myUser.
Jan 05 11:29:24 guihost systemd-logind[711]: New session 4 of user myUser.
Jan 05 11:29:24 guihost gdm-password][1568]: pam_unix(gdm-password:session): session opened for user myUser by (uid=0)
Jan 05 11:29:25 guihost audit[1568]: USER_START pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty2 res=success'
Jan 05 11:29:25 guihost audit[1568]: USER_LOGIN pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=? res=success'
Jan 05 11:29:25 guihost systemd[1489]: Started D-Bus User Message Bus.
Jan 05 11:29:25 guihost dbus-daemon[1593]: [session uid=1000 pid=1593] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=1000 pid=1614 comm=""/usr/libexec/gnome-initial-setup-copy-worker "" label=""unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023"")
Jan 05 11:29:25 guihost kernel: fuse init (API version 7.25)
Jan 05 11:29:25 guihost systemd[1489]: Starting Virtual filesystem service...
Jan 05 11:29:25 guihost dbus-daemon[1593]: [session uid=1000 pid=1593] Successfully activated service 'org.gtk.vfs.Daemon'
Jan 05 11:29:25 guihost systemd[1489]: Started Virtual filesystem service.
Jan 05 11:29:25 guihost gnome-keyring-ssh.desktop[1624]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 05 11:29:25 guihost gnome-keyring-secrets.desktop[1626]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 05 11:29:25 guihost org.gnome.Shell.desktop[1641]: pci id for fd 9: 80ee:beef, driver (null)
Jan 05 11:29:25 guihost gnome-shell[1641]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
Jan 05 11:29:25 guihost gnome-shell[1641]: Unable to initialize Clutter.
Jan 05 11:29:25 guihost gnome-session[1598]: gnome-session-binary[1598]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 05 11:29:25 guihost gnome-session-binary[1598]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 05 11:29:25 guihost gnome-session-binary[1598]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jan 05 11:29:25 guihost gdm-password][1568]: pam_unix(gdm-password:session): session closed for user myUser
Jan 05 11:29:25 guihost audit[1568]: USER_END pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty2 res=success'
Jan 05 11:29:25 guihost audit[1568]: USER_LOGOUT pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=? res=success'
Jan 05 11:29:25 guihost audit[1568]: CRED_DISP pid=1568 uid=0 auid=1000 ses=4 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix,pam_gnome_keyring acct=""myUser"" exe=""/usr/libexec/gdm-session-worker"" hostname=? addr=? terminal=/dev/tty2 res=success'
Jan 05 11:29:25 guihost gdm[917]: GdmDisplay: display lasted 0.391821 seconds
}}}
----

Check running processes: (after first login attempt)
{{{
ps aux | grep key
myUser    1580  0.0  0.1 323520  7200 ?        Sl   11:29   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
myUser    1688  0.0  0.0 119372   912 pts/0    S+   11:32   0:00 grep --color=auto key
}}}

Check running processes: (after second login attempt)
{{{
ps aux | grep key
myUser    1580  0.0  0.1 323520  7200 ?        Sl   11:29   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
myUser    1703  0.0  0.1 323524  7128 ?        Sl   11:33   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
myUser    1763  0.0  0.0 119372   980 pts/0    S+   11:33   0:00 grep --color=auto key
}}}

Additional gnome-keyring-daemon processes will persist with each failed login entry.

----------


Save full log:

`journalctl > logs/boot-4-complete.out`

Shut down the system:

`sudo poweroff`

SEE Logs: 
  * logs/boot-4.out
  * logs/boot-4-errors.out
  * logs/boot-4-avcs.out
  * logs/boot-4-complete.out



'''Observations:'''

After uninstalling the guest additions the problem is resolved. However, the mouse misbehaves; the host/virtual pointer never line up again.

Please let me know if you should need anything else.


Thanks in advance,

TT",Todd E Thomas
16422,"Change error message for ""BLKCACHE_IOERR""",all,all,,2017-01-24T18:26:27Z,2017-01-24T18:26:27Z,"As in this post: https://forums.virtualbox.org/viewtopic.php?f=1&t=81546
The error says:

{{{
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.
}}}


If it were made clear that the ""disk"" being discussed was the host's physical disk the guest was stored on, the error may be a hint more interpretable by newer users.",scottgus1bug
15565,Host adapter showing zero bytes traffic,Windows,other,VirtualBox 5.0.24,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
10317,Windows 8 Host: No network adapters after resume from sleep,Windows,other,VirtualBox 4.1.8,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
16366,Solaris x86 Host - Centos 7 Guest hangs after using all the memory,Solaris,Linux,VirtualBox 5.1.12,2017-01-26T22:18:55Z,2017-01-26T22:18:55Z,Solaris x86 Host has 64GB Memory. Centos7 Guest VM given 16GB. After about 3-4 days the VirtualBox process consumes all 16GB and the VM is unavailable. Am able to stop and start the VM and it will stay running for another 3-4 days.,Buster Gonad
16423,Unable to boot after converting .vmdk to .vdi,Linux,Linux,VirtualBox 5.1.12,2017-01-26T23:06:27Z,2017-01-26T23:06:27Z,"Host: Arch Linux x86_64 with 4.8.13-1-ARCH

After converting a 50GB vmdk file to vdi using the command below, I wasn't able to boot the virtual machine with the newly created vdi file because of a ""fatal error: no bootable medium found"" 

{{{
VBoxManage clonemedium --format VDI actual.vmdk new.vdi
}}}

The conversion went well though. You will find my ''actual.vmdk'' file attached to this post, alongside 2MB of my ''actual-flat.vmdk'', as requested by an IRC user on #vbox.",closingin
16433,The installer won't work error 2755 and when I can get it installed another problem happens.,Windows,Linux,VirtualBox 5.1.14,2017-01-30T04:26:09Z,2017-01-30T04:26:09Z,"The problem when I got virtualbox installed, it would tell me an error that it couldn't acquire the COM object. I have checked to make sore there are no corrupt registry files, I've deleted some of the old virtualbox files on my system, I even deleted the installer folder in windows32, along with deleting and removing virtualbox and reinstalling. I haven't been able to fix this problem, it was all working fine about a month ago and then one day when I decided to use VBox it just stopped working saying that it can't acquire the COM object ",Kingy
16420,Snapshots present but required Machine/@currentSnapshot attribute is missing.,Windows,Linux,VirtualBox 5.1.14,2017-01-30T11:58:24Z,2017-01-30T11:58:24Z,"Hello,

since morning I receive this issue when starting directly into Virtualbox.
Yesterday I used my Ubuntu VM, took a snapshot and closed it.

Everything looked fine.

Please tell me a solution.

Thank you.

Regards

Andreas",Haemma
16007,Allow overriding existing snapshots,other,other,VirtualBox 5.1.6,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
16437,VBoxManage controlvm savestate fails with NS_ERROR_FAILURE (0x80004005),Linux,Linux,VirtualBox 5.1.14,2017-01-31T14:09:22Z,2017-01-31T14:09:22Z,"When I call 
{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
}}}
from a bash script I get the following error:


{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to save machine state
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg*)"" at line 276 of file VBoxManageControlVM.cpp

}}}

'''Environment:'''

VBoxManage: Oracle VM VirtualBox Command Line Management Interface Version 5.1.14

Host operating system: CentOS Linux release 7.2.1511 (Core)

Guest operating system: Ubuntu 14.04.4 LTS",acho-bacho
16400,Mouse loses ability to drag,Mac OS X,Windows,VirtualBox 5.1.12,2017-01-31T19:05:42Z,2017-01-31T19:05:42Z,"Win-XP VM on OS-X 10.12.2, VB 5.1.12 r112440 (Qt5.6.2)

After a short period (5 to 10 minutes) the mouse loses the ability to click and drag anything in the XP UI. This happens regardless of the pointer device (mouse, trackpad, etc.) The mouse can still select and click event and hoover are processed correctly. It is only drag that does not work. This applies to any draggle object: windows, filed, window position widgets, etc.

It is possible/likely that this is not caused by time, but by some common activity. But, I have  not been able to identify any such activities.",berkinet
16439,Clipboard add CR character,Windows,Linux,VirtualBox 5.1.8,2017-02-01T15:48:36Z,2017-02-01T15:48:36Z,"Hi,
I have problem with the end of line with the clipboard, it appears that virtualbox add a CR (carriage return) character before every LF (line feed). So if I change a file in the guest (linux) that ends already with CRLF, when I paste the result ends with CRCRLF and some program, i.e. pspad, add a blank line.

As example, if in the guest I copy
a
b

becomes in the host
a

b
",ubuguest
16363,App using OpenGL asserts in Visual Studio,all,Windows,VirtualBox 5.1.12,2017-02-02T19:19:08Z,2017-02-02T19:19:08Z,"I have an app written in C++ that runs in Visual Studio 2013. This works fine in a Windows 7 VM but when I upgraded to Windows 10 I find it asserts when attempting to use OpenGL. The app works on Windows 10 without a VM. I've tried turning 3D and 2D acceleration off but it makes no difference.

This happens on hosts using MacOS and Linux.
",tom.isaacson
16434,Cannot resize VM Win7 on Win 10 Host,Windows,other,VirtualBox 5.1.14,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
16445,VM gets stuck at online snapshotting,Linux,Linux,VirtualBox 5.1.12,2017-02-03T11:01:21Z,2017-02-03T11:01:21Z,"In our backup script, we perform online snapshotting of headless VMs to ensure we get a consistent state with the following command:

{{{
vboxmanage snapshot $BCK_VM_UUID take
}}}

One of the VM got stuck in ""online snapshotting"" (as per vboxmanage) for 3h when we took action.

Host is latest update of Debian 8 (Jessie)[[BR]]
Guest is latest update of Ubuntu 16.04 LTS

Core dumps of the vboxheadless process and VBoxSVC are available on request (or via Klaus).",Max D
16447,Multi-monitor failure with drag & drop enabled,Windows,Windows,VirtualBox 5.1.14,2017-02-03T15:18:00Z,2017-02-03T15:18:00Z,"Host and Guest are both Win-7 64-bit.  Bi-directional drag-and-drop is enabled.  Beginning immediately after booting, moving a file from desktop on primary monitor to secondary monitor works fine.  Attempting to drag a file back from secondary monitor to primary causes screen lockup when transitioning across screen boundaries, even before releasing left mouse button.  Clicking start orb brings up menu, which then becomes permanent on screen.  CPU usage indicator looks like it goes to 50%.  Session information shows disk read data continuously climbing.  Inserting ctrl-alt-del brings up full-screen menu.  Process monitor will come up if selected, but response is extremely slow.  Switching users from ctrl-alt-del back to same (only defined user) comes back to black screens.  Logout and then login from ctrl-alt-del menu clears the problem and screens are unlocked until trying to do another d&d from secondary to primary monitor.  Enabling/disabling 2D and 3D acceleration has no effect.  Switching drag-and-drop to host-to-guest solves the problem, while obviously losing guest-to-host functionality.  I have been using a shared folder for years to move files back and forth between host and guest, so this is a very minor inconvenience.  Other than, it took many hours to figure out why my shiny new 64-bit VM was locking up.  I have not found any other reporting of this problem.  Because this is a production machine, I did not test with a test version of VirtualBox.  Please let me know how I can be helpful.",DougL
16451,GUI Manager crashes when adding existing vdi file,Windows,Windows,VirtualBox 5.1.14,2017-02-04T12:21:09Z,2017-02-04T12:21:09Z,Creating a new Windows guest under Windows 7 Host.  Trying to attach an existing vdi file.  If you click on the + at the bottom of the screen the manager crashes (see attached screen capture).  Luckily if you click on the + at the top of the screen it all works!  Maybe the easiest fix would be to remove the + and - at the bottom of the screen.  ,JimAttrill
15603,VirtualBox 5.1 3D acceleration issues,Windows,Linux,VirtualBox 5.1.0,2017-02-04T15:34:10Z,2017-02-04T15:34:10Z,"When 3D acceleration is enabled, several odd things happen.  By the way, VB 5.0.24 did not have any of these issues.

* Sometimes only a small rectangle of the screen will redraw after boot with VB set to a normal window.  It's about the size rectangle as the boot windows.
* The VB mini toolbar and dialogs are hidden in full-screen.
* Can't display full-screen on display 1 when display 2 is primary.  It just ignores the menu setting.
* The non full-screen window randomly shifts to my primary monitor on restart.

With or without 3D enabled, and when the VM is set to auto-login, the Ubuntu launcher is randomly invisible at boot time until I click in the VB window, and it immediately appears.  Clicking does not consistently make the launcher appear with 3D enabled.

Host: Windows 10 Home, NVIDIA GTX 650 Ti 368.69
Client: Ubuntu 16.04 with VB guest additions 5.1
",John JJ
16456,"Windows 10: Installation hangs at ""NetLwf will be installed ...""",Windows,all,VirtualBox 5.1.14,2017-02-05T21:22:34Z,2017-02-05T21:22:34Z,"I tried to install VirtualBox 5.1.14 on the weekend on my computer (Windows 10 Version 1607).
Unfortunately the installation hangs at a certain point.
The log shows the following information:

{{{
InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
}}}


I used a Windows 10 image to restore my computer and tried the installation several times, but it never worked.

If I performe the installation without the VBoxNetwork-features the installation works.

It would be really great if somebody could help me.
If you need any more logs just tell me.",Rafter
14034,NMI kernel panics on HP Proliants running RHEL causing machines to reboot at VBoxHost_RTSemEventMultiWaitEx,Linux,Windows,VirtualBox 4.3.26,2017-02-06T10:09:06Z,2017-02-06T10:09:06Z,"Over the past few months we have been experiencing seemingly random reboots of our DL360 G7 and DL360 G6 machines every few days when using VirtualBox 4.3. We don't think we have been suffering from this problem when using VirtualBox 4.2. The vmcore-dmesg.txt file that is written to /var/crash contains stack traces that might seem to implicate VirtualBox as a cause of the crashes

{{{
<4>Pid: 5567, comm: EMT-0 Not tainted 2.6.32-504.12.2.el6.x86_64 #1
<4>Call Trace:
<4> <NMI>  [<ffffffff8152933c>] ? panic+0xa7/0x16f
<4> [<ffffffffa002e4df>] ? hpwdt_pretimeout+0x9f/0xcc [hpwdt]
<4> [<ffffffff815300f5>] ? notifier_call_chain+0x55/0x80
<4> [<ffffffff8153015a>] ? atomic_notifier_call_chain+0x1a/0x20
<4> [<ffffffff810a4eae>] ? notify_die+0x2e/0x30
<4> [<ffffffff8152de17>] ? do_nmi+0x217/0x340
<4> [<ffffffff8152d680>] ? nmi+0x20/0x30
<4> <<EOE>>  [<ffffffffa04bb210>] ? VBoxHost_RTSemEventMultiWaitEx+0x10/0x20 [vboxdrv]
<4> [<ffffffffa04b84da>] ? rtR0MemAllocEx+0x8a/0x250 [vboxdrv]
<4> [<ffffffffa04a98ca>] ? supdrvIOCtlFast+0x8a/0xa0 [vboxdrv]
<4> [<ffffffffa04a93a4>] ? VBoxDrvLinuxIOCtl_4_3_26+0x54/0x210 [vboxdrv]
<4> [<ffffffff811a3782>] ? vfs_ioctl+0x22/0xa0
<4> [<ffffffff811a3924>] ? do_vfs_ioctl+0x84/0x580
<4> [<ffffffff810e5c7b>] ? audit_syscall_entry+0x1cb/0x200
<4> [<ffffffff811a3ea1>] ? sys_ioctl+0x81/0xa0
<4> [<ffffffff810e5a7e>] ? __audit_syscall_exit+0x25e/0x290
<4> [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
}}}
These machines are running recently patched versions of Red Hat Enterprise Linux Server release 6.6 (Santiago). The problem has been seen on about 6 different machines. This is occuring with VirtualBox 4.3.26 but has been happening with many other recent releases in the 4.3 series. We only have 1 guest VM running on each of these RHEL machines and it is running Windows 2008 R2 64 Bit as a guest.

We have not as far as we know configured the HP Watchdog Timer in any special way.
Ticket 13762 seems to bear some similarities to this ticket. I have attached one example of vmcore-dmesg.txt

",nj
16446,Virtualbox can only use one core with isolcpus,Linux,Linux,VirtualBox 5.1.14,2017-02-06T13:59:27Z,2017-02-06T13:59:27Z,"On our server we installed ''isolcpus'' to dedicate our cpus for special tasks. Unfortunately it is not possible to assign virtualbox for more than one core with 

{{{
taskset -c 4,5,6,7 VBoxManage starvm ""[vm_name]"" --type headless
}}}

If we start the virtual machine only with 

{{{
VBoxManage starvm ""[vm_name]"" --type headless
}}}

the virtual machine runs on core 0-3.

After we uninstalled isolcpus we can use ''taskset'' to assign certain cpus.",seide
16443,Weston doesn't render a cursor.,other,other,VirtualBox 5.1.14,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
4890,"Linux guest, ""mv -f file1 file2"" fails on shared folder without write permissions on file2 (Windows hosts)",Windows,Linux,VirtualBox 3.2.10,2017-02-07T21:35:02Z,2017-02-07T21:35:02Z,"Test case:

touch file1 file2
chmod a-w file2
mv -f file1 file2

On the guest disk, there is no message whatsoever and file2 is replaced by file1. This is the behavior I expect.


On a shared folder pointing to a directory on the host's local hard disk drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': Operation not permitted


When the shared folder is pointing to a network drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': File exists

",David
16256,Host OS kernel panic when running Redox 0.0.3 in VirtualBox,Mac OS X,other,VirtualBox 5.0.26,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
16467,Unlink of locked file fails on shared folder,Windows,Linux,VirtualBox 5.1.14,2017-02-08T16:42:00Z,2017-02-08T16:42:00Z,"I noticed that some programs crash, when working on data in a shared folder. I recorded the file operations with strace and was able to write a small program, that reproduces the error. The attached program basically acquires a lock on a file and then tries to delete it before closing.

To reproduce the error, execute the attached program in a Linux guest, on a Windows host. It prints ""Test failed"" when being executed in a shared folder. When executed outside the shared folder, it prints ""Test passed.""",egooo
16468,Unable to fix the mislocated vboxguestadditions.iso file in Virtual Media Manager.,other,other,VirtualBox 5.1.14,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
16470,Install Oracle Certificate automatically to Trusted Publishers store,all,Windows,VirtualBox 5.1.14,2017-02-09T09:48:11Z,2017-02-09T09:48:11Z,"Please install the Oracle Corporation vertificate to Trusted Publishers store inside the MSI setup to prevent the driver popups. WiX has such a feature, see http://wixtoolset.org/documentation/manual/v3/xsd/iis/certificate.html

Without this it is complicated to deploy VirtualBox via AD for nothing. Other sofware also does this and does not bubble message boxes with untrusted drivers.",vboxuser4
16471,TinyCore 7.2 boots on VB 5.0.32 but not on 5.1.14,Windows,Linux,VirtualBox 5.1.14,2017-02-09T10:41:13Z,2017-02-09T10:41:13Z,"On a first machine: Win10 - VB 5.1.6, TinyCore-7.2.iso boots fine.

On a second machine: Win8 - VB 5.1.14, CorePlus-7.2.iso or TinyCore-7.2.iso fail with:

{{{
Code:  Bad EIP value.
EIP: [<fefa201c>]  SS:ESP 0068:c703bea4
---[ end trace 91cd7754bf702e09 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

}}}

Full console log attached. The VB log is no more available.

For trial, I uninstalled 5.1.14 and installed 5.0.32, and it worked.",Psam
16063,"Any immediate ""VBoxManage modifyvm"" commands after detaching a dvd drive fail with 'The machine 'vm_name' is already locked for a session'",other,other,VirtualBox 5.1.6,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
16475,Enhancment - Self-ejecting VBoxGuestAdditions.iso,all,all,VirtualBox 5.1.14,2017-02-10T09:52:08Z,2017-02-10T09:52:08Z,"There are a lot of problems when users forget to eject their VBoxGuestAdditions.iso right after installing the GAs. Then they upgrade and the UUIDs don't match, or clone the VM while on saved states, or getting VERR_PDM_MEDIA_LOCKED errors.

Please explore the possibilities to have the GAs ISO self-eject at the end of a successful installation.",Socratis
16229,Blue screen of the death when you change to Bridged Adapter,Windows,Windows,VirtualBox 5.1.10,2017-02-11T08:36:03Z,2017-02-11T08:36:03Z,"All worked fine before update of my network driver. (I updated by KillerSuite_1.1.65.1752_Win7_Win81_Win10).

But after update, when I share internet using Bridge, blue screen of the death for host machine is appeared. If i don't have connection to the internet on host machine (Wi-Fi/Ethernet), all are working fine, but after connection all crash too.   

version of Vbox is 5.1.10 r112026 (Qt5.6.2)
Both(host and guest) have windows 10

Could you please tell, is it problem of Vbox or my driver? What is the best way to resolve it? Rollback driver\create ticket for them or is it Vbox problem? ",AlekseiG
16484,Crash during guest OS startup,Windows,other,VirtualBox 5.1.14,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
12167,Security Tab is missing in shared folders,all,other,VirtualBox 4.2.18,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
16487,Shared Folder /copying an overwriting modified text file causes error on Ubuntu 16 guest,Linux,Linux,VirtualBox 5.1.14,2017-02-16T03:10:30Z,2017-02-16T03:10:30Z,"== Summary ==
*copying an overwriting modified text file causes error on Ubuntu 16 guest
after overwriting, file contains invalid characters. (can be check with Ubuntu's gedit) and sometimes missing characters.
One thing I found weird is, if you open the modified file in the shared folder from guest, it doesn't contain any invalid characters. Invalid character problem only rise when the file is overwritten to the folder in guest env.

*copying an overwritten text file steps can be found under 'How to reproduce the problem'

== How to reproduce the problem ==
1. (host OR guest) create a text file from the host shared folder
2. (guest) copy the shared file to any folder
3. (host) modify the file and save (if you modify the file from guest, it won't happen)
4. (guest) copy the modified file and overwrite it

== Attach a (full) log file ==
see the attached log file

Thank you for the great SW!",haku
16488,Build errors on MacOS Sierra,Mac OS X,all,VirtualBox 5.1.14,2017-02-16T04:04:40Z,2017-02-16T04:04:40Z,"https://www.virtualbox.org/browser/vbox/trunk/configure#L2327 checks `uname -r` but for me this reports 16.4.0

Not sure if there will be other errors in the toolchain, I'm going to attempt to apply trivial / obvious changes and see what happens.",rss
16491,Problem with Open Semantic Desktop Search,other,other,VirtualBox 5.1.14,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
15612,"OSX dock icon set to app icon, settings ignored",Mac OS X,all,VirtualBox 5.1.0,2017-02-20T07:06:10Z,2017-02-20T07:06:10Z,"All VM dock icons have switched from ""Show Monitor Preview"" to ""Show Application Icon"", so all you have is a generic icon, for all VMs. Furthermore, if you switch it back to ""Show Application Icon"", although it seems that this option is selected/checked the behavior remains the same; generic icon.

I don't believe a VBox.log will shed any more light, so to conserve space, I didn't attach one. If there is a need for it, please say so.

Host: MacBookPro 17"", early 2011. OSX 10.9.5.",Socratis
14501,VBox 5.0x unresponsive running VS1015 (or other WPF?),Mac OS X,Windows,VirtualBox 5.0.2,2017-02-21T02:08:38Z,2017-02-21T02:08:38Z,"I had installed VBox version 5.0.2 on a Mac OSX machine running 10.10.5.

I created two (one from clean under 5.0.2 and one from clone of a machine installed under 4.3) windows 8.1 guest images each updated with latest windows updates and VBox guest additions.

On each of these I installed Visual Studio 2015.

When run up, Visual studio gets as far as openning the screen, at this point the host machine indicates that the process is fully utilising the four cores it is allocated and the windows machine becomes almost completely unresponsive. I have to power off to shut them down.

I have tried the following:

1) Disable 3d acceleration in the guest definition.
2) enable and disable the Hyper-V integration.
3) Apply the registry setting to disable WPF hardware acceleration usage: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration
4) upgrade to latest build: 5.0.3 (with matching guest additions) same issues.
5) downgrade to build 5.0.0 (with matching guest additions) same issues.

finally downgrading to build 4.3.30.r101610 (with matching guest additions) Visual studio will now run as expected.

All experiments carried out on the same virtual machines.

I have during these experiments concentrated on Visual Studio, though the machines also appeared to occasionally lockup in the same manner with other causes. On one occasion the machine froze with the guest additions prompt on the screen.
But on most occassions windows ran sufficiently to start Studio before hanging.
",wuzzy
16500,An USB issue only on Linux guest,Windows,Linux,VirtualBox 5.1.14,2017-02-22T21:07:35Z,2017-02-22T21:07:35Z,"I try to use a common FTDI based USB UART (virtual serial port) chips on Win7 host and 32 bit Linux guest and it causes serial communication to drop because some received serial data is lost within seconds of usage. FTDI chips use USB 1.1 are known to work reliably on Linux too.

It has repeated at least on VBox 4.3.5, 5.1.10, 5.1.12 and 5.1.14 on two completely different host computers and various 32bit guests also (debial/ubuntu). USB mode setting 1.1, 2.0 and 3.0 have been tested - no difference.

I've tested vmWare Workstation Player on same computer and same guest image, and it WORKED FLAWLESSLY (10hr+ stress test done). Also it works on same computers with Win7 guest. So problem seems to occurs only with Linux guest + virtualbox combo.

I hope this helps!",reTok
16507,Windows 10 freezes when using a KVM switch while VirtualBox is running VMs,Windows,Linux,VirtualBox 5.1.14,2017-02-23T18:53:48Z,2017-02-23T18:53:48Z,"I have the following problem. I have Windows 10 PC, Virtualbox 5.1.14 r112924 installed, and a Keyboard/Mouse Switch via USB connected to this PC for Mouse and Keyboard.
Using the KVM switch is working perfectly fine with all applications.
BUT when I run a VM in VirtualBox, and then I use the KVM switch to connect to another computer, and switch back to Windows 10, I have no access to that computer anymore. Keyboard and Mouse don't work anymore. I have to hard reboot the Windows 10 computer. This is reproducible every time. The guest OS is always CentOS 7.2.",bati2712
13889,VirtualBox Bridged Networking Driver error,Windows,other,VirtualBox 4.3.22,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
16440,"As a guest, must hold keyboard key a second or more",Windows,Linux,VirtualBox 5.1.14,2017-02-24T20:12:44Z,2017-02-24T20:12:44Z,"Previously used Control Panel to uninstall VBox 5.0.4 (was installed through MyDesktop)

Uninstalled VBox 5.1.14 which I'm having keyboard issues with (must hold keys for them to be recognized)

Re-downloaded VirtualBox-5.1.14-112924-Win.exe

Installed VBox 5.1.14, used all defaults

Used Start to bring up Oracle VM VirtualBox

Within VBox Manager, clicked on Start (Oracle Linux Server 6.6), replied with password to ""jhoelsch4.dev"" login.  Information had apparently been retained from a previous install of VBox.  So, looks like there are bits of configuration detail, probably retained in the registry.

Three windows are generated:
- Development [Running] - Oracle VM VirtualBox : 1
- Development [Running] - Oracle VM VirtualBox : 2  (contains icons Computer, jhoelsch's Home, Trash, sf_AutoImage, VBOXADDITIONS_5  1.13_112924)
- Development [Running] - Oracle VM VirtualBox : 3 (identical to window 1 above)
When password was entered in window 1, the same keystrokes were echoed in window 3.

Right-click on jhoelsch's Terminal -> Open In Terminal.  This is where keys must be held extra long to be recognized

Notes: 
sf_AutoImage is residual from a shared folder from a prior VBox install.
",John Hoelscher
16510,Sound volume not working in guest (winxp x32). Host - kubuntu 16.04.2 LTS x64,Windows,Linux,VirtualBox 5.1.14,2017-02-25T08:52:43Z,2017-02-25T08:52:43Z,"Sound volume not working in guest (winxp x32). Host - kubuntu 16.04.2 LTS x64
Not work change sound volume (Even if off - really volume is 100%). I tested 5.0.32 and 5.1.14. Not work checkbox to volume off (volume is 100%)

For disable sound in VM - i disable Intel 82801AA sound controller in VM.

I test with last guest addition for winXP. - volume not changed.
Win7 x32 guest - volume work all right (but slight stutters).",unicorp99
16511,Running VBox prevents notebook from switching into sleeping mode,Windows,other,VirtualBox 5.1.14,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
4862,"Files in shared folder which open in mode ""w+b""(Linux guest) could not be read(Protocol Error)",Windows,Linux,VirtualBox 3.0.4,2017-02-25T16:48:42Z,2017-02-25T16:48:42Z,"I am using a python programe(ZODB) to read file's content in shared folder.But I got a [IOError]Protocl Error when I run the programe.And I check out the source,found that ZODB open this file in ""w+b"" mode.I write a very simple test programme(also python),and got the same problem.Here is the source:
{{{
#Test programme
f = open(""Data.fs"",mode=""w+b"")
f.read(10)#got error here
}}}
Data.fs is the file in shared folder.I also test in mode ""r+b"",it's ok for both write and read.",Yao
6465,Blackberry synchronization appears broken => Fixed in SVN,Linux,Windows,VirtualBox 3.1.4,2017-02-26T04:17:27Z,2017-02-26T04:17:27Z,"Host Debian Lenny 64 bit, client Windows XP SP3.

Blackberry synchronization works fine in VB 3.0.2. Since then, I've tried VB versions 3.0.4, 3.0.6, 3.0.8, 3.1.2 and 3.1.4 and the Blackberry USB support fails in various ways, some quite comical, so I revert back to VB 3.0.2.",George R. Young
16516,HTTPS request before LaunchVMProcess let sound crash in guest,Windows,Windows,VirtualBox 5.1.14,2017-02-27T06:49:59Z,2017-02-27T06:49:59Z,"On a Win7 Guest, Host doesn't mind (tested Win 7 and 10), doing 
[[BR]]
{{{
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(""https://www.google.de"");
HttpWebResponse res = (HttpWebResponse)req.GetResponse();
}}}
before
[[BR]]
{{{
VirtualBox.VirtualBox vBox = new VirtualBox.VirtualBox();
IMachine m = vBox.FindMachine(""VM"");
m.LaunchVMProcess(new Session(), ""gui"", """");
}}}
[[BR]]
the sound in the guest system stops working with 
[[BR]][[BR]]
DSound: Starting playback failed with E_ACCESSDENIED
[[BR]][[BR]]
Switching the https to http in above code, everything will work as expected. 
[[BR]][[BR]]
Additionally, starting the VM without a webrequest (from API or VBoxManage), stopping it and letting VBoxSVC not terminate, means starting the guest by above code immediately, then the https request will not interfere with the guest sound.

Thanks in advance.[[BR]]
Kind regard[[BR]]
Ben",Benne
16517,Drag and drop not working,Windows,Solaris,VirtualBox 5.1.14,2017-02-27T06:59:51Z,2017-02-27T06:59:51Z,"I used to be able to drag and drop using solaris 11.4.2 but lost that when I upgraded to solaris 11.3. 
I am using a windows 7 (host )  and running solaris 13 as a guest on virtual box 5.1.14. 

Extension pack is updated. ",fg2017
16441,Kernel Panic on Mac host when doing file operations on shared NFS drives,Mac OS X,other,VirtualBox 5.1.14,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
14182,Host detects wrong number of cores (half of them),Linux,Linux,VirtualBox 4.3.28,2017-02-27T21:55:31Z,2017-02-27T21:55:31Z,"I've a system with 4 Opteron 6174, each of them has 12 cores so the system has a total of 48 cores.

But Vbox seems to detect just half of them, this is the relevant line on one of the client log files:

00:00:00.728345 Physical host cores: 24

I attach the full log for completeness",Alex
8195,Shared folder error with long filename after snapshot restore,Windows,Windows,VirtualBox 4.0.0,2017-02-28T13:18:45Z,2017-02-28T13:18:45Z,"- Snapshot created during running (WinXP) gast

- Snapshot restored (with vboxmanage startvm)

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

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

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

- For Example:

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

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

- Hint:

  - An other program tell, the shared folder support only 8 standard characters.
",vbdevtest
16520,Windows 7 guest does not fill out all the screen on mac,Mac OS X,Windows,VirtualBox 5.1.14,2017-02-28T18:01:28Z,2017-02-28T18:01:28Z,"I installed virtualbox 5.1.14 and the Extension Pack as well to run Windows 7 as a guest on macbook pro. Everything is fine except that Windows 7 does not fill out the screen (even though I have it on full screen).

Any help would be appreciated. 

",SG07
16521,no NetworkBridge Mode,Windows,all,VirtualBox 5.1.14,2017-02-28T18:40:31Z,2017-02-28T18:40:31Z,"NAT works fine
NetworkBridge Mode dont work.
It gets an IP-Adress, ping works,
but no trafic, no Website loads, div. ...

last things done:
Update from 5.0.32 to 5.1.14rxxxxxx

Machines:
Ubuntu 16.04,
W10pro
W7pro
Xubuntu
Linux Mint Sarah
WinXP-Pro
ipFire
pfSene
",Bardo
16463,"""Operation not permitted"" on file in shared folder",Windows,Linux,VirtualBox 5.0.26,2017-02-28T19:41:09Z,2017-02-28T19:41:09Z,"* Host: Windows 7 x64
* Guest: Linux CentOS 6.7 x64 ( VirtualBox Guest Additions 5.0.26 r108824 )

If you look at ticket #4890, which is very likely the same underlying issue, the most recent comment is still reporting the issue on 5.1.12

In a vbox shared folder:
{{{
[user@server ~]$ mount | grep vboxsf
sv on /sv type vboxsf (uid=500,gid=500,rw)
[user@server ~]$ sudo touch /sv/a.txt
[user@server ~]$ sudo chmod a-w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
rm: cannot remove `/sv/a.txt': Operation not permitted
[user@server ~]$ sudo chmod a+w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
[user@server ~]$
}}}

Not in a vbox shared folder:
{{{
[user@server ~]$ sudo touch /a.txt
[user@server ~]$ sudo chmod a-w /a.txt
[user@server ~]$ sudo rm -f /a.txt
[user@server ~]$
}}}

Possible related tickets:
* https://www.virtualbox.org/ticket/4890
* https://www.virtualbox.org/ticket/5568
* https://www.virtualbox.org/ticket/15083",bompus
16522,Failed to open sessions after update to vm 5.1.14 on windows 7 sp1,other,other,VirtualBox 5.1.14,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
15691,VM stuck when restoring the session,Linux,Windows,VirtualBox 5.1.2,2017-03-01T10:07:18Z,2017-03-01T10:07:18Z,A session that was restored has stuck the entire VM.,Panos Kavalagios
16523,Multiple Monitors on Full Screen MAC do not work,Mac OS X,Linux,VirtualBox 5.0.32,2017-03-01T12:50:55Z,2017-03-01T12:50:55Z,"I started a discussion regarding this on https://forums.virtualbox.org/viewtopic.php?f=8&t=82004&p=386615#p386615

I have tested in on 5.1.15 (pre-release) and 5.0.32. The matching Guest additions were installed from the iso in all tests.

When trying to use multiple monitors on a MAC (Sierra) with a Linux client (tested Debian 8 and Mint (17 & 18)) they work in normal mode. Set monitor count to 2, you get 2 Windows and it all works well.

Clicking any of the Windows to full screen, the primary screen maximises, the second screen disappears. It is not shown in mission control or available anywhere I can find. I checked with Apple support to ensure I was not doing anything silly!

If you enable 3D support for those guests and you get an unusual window for the second display. i.e. when you first click full screen, the primary goes full screen, the second disappears. Go to mission control, and you see a small icon with an image fragment next to it. Click on this and you get the second monitor back. But this second monitor does not work, most of the window is white with a tiny bit (top left) shows a small amount of the second screen.

Image attached of the second window. If you try to full-screen this window, it bounces up, and straight back down to a window (maintaining what you see in the image).

Revert from full screen and both monitors start to work again. All other applications on this computer use multiple full screens without problems.",tinpotnick
16525,Automatically switching to Seamless mode on start does not use full screen area,Windows,Linux,VirtualBox 5.1.14,2017-03-02T13:15:31Z,2017-03-02T13:15:31Z,"If my Arch Linux x64 guest (on Win10 x64 host) is closed with seamless mode running, when I restart the guest there's a popup saying to switch back to seamless mode. If I click okay, seamless mode starts but there's a gap at the top from the vbox guest OS menu. I have to ctrl+L and ctrl+L again to get it to recognize the actual display size.",R
16526,Google Chrome Stable Crashes Linux Guest,Windows,Linux,VirtualBox 5.1.14,2017-03-02T16:40:47Z,2017-03-02T16:40:47Z,"I am not sure about the complete steps, but I can reproduce this each, and every time.  I launch Google Chrome (Version 56.0.2924.87 (64-bit)) under Ubuntu GNOME 16.04.2 Guest.  I visit a Cisco Acano URL to join a meeting (such as https://join.<some domain>.com/invited.sf?secret=QtsgKqo7mTqO2O4pOM0ouB&id=77223344).  When I join the meeting, VirtualBox crashes with an error message, such as:

    The instruction at 0xdc7aa4f2 referenced memory at 0x00000028.  The memory could not be read.  Click on OK to terminate the program.

Host:  Windows 7 Professional SP-1
       16GB RAM
       AMD Radeon R7 M360/Intel HD Graphics 520
       Dual Core i7
       Three monitors (laptop + two external)
Guest: Ubuntu GNOME 16.04.2
       8GB RAM
       128MB VRAM
       2 CPU
       2 Monitors
",JayBofMA
16527,vbox autostart-enable on deletes the autostart file /etc/vbox/[user].start,Linux,Linux,VirtualBox 5.1.14,2017-03-02T18:14:39Z,2017-03-02T18:14:39Z,"it looks like the problems with autostart at ubuntu are somehow logical issues
I wasn't able to bring the vms in autostart mode. all files and folders are fine. But the ...-enabled on reports nothing and the enabled-off showed VERR_FILE_NOT_FOUND

a sudo touch [username].start at /etc/vbox/ followed by sudo chown [user] [user].start changed the the behavior that ..-enabled off doesnt fail.

but after a enabled on the .start script is lost. So something must be wrong there.

Ubuntu 16.04.04 VBOX 5.1.14",bba_fan
16066,The instruction at 0x... referenced memory at 0x.... The memory could not be read.,Windows,Windows,VirtualBox 5.1.6,2017-03-03T18:22:55Z,2017-03-03T18:22:55Z,"Hello, after some weeks ago my virtual machine start crashing many times per day with error:

'''The instruction at 0x00007FFCCB3949F9 referenced memory at 0x0000000001C9196C. The memory could not be read.'''

It happened in old and new version too. As host I use Windows 10 with '''Anniversary update'''. '''Probably problems come after this update'''. Guest operating system is Windows Server 2012 R2.

I tried to create mini dump via instructions on link https://www.virtualbox.org/wiki/Core_dump but it is not working in Windows 10 Anniversary update. I did it via Process Explorer.

Attached Dumps.zip file contains mini dumps from all processes in process tree of problematic VirtualBox.exe process:

{{{
- VBoxSVC.exe (VBoxSVC_Mini.dmp)
  - VirtualBox.exe (VirtualBox1_Mini.dmp)
    - VirtualBox.exe (VirtualBox2_Mini.dmp)
      - VirtualBox.exe (VirtualBox3_Mini.dmp - VM process)
}}}

Thanks for any suggestion/help.",Paul B.
16533,Boot from usb device.,Windows,other,VirtualBox 5.1.14,2017-03-04T11:39:58Z,2017-03-04T11:39:58Z,Add boot from usb device.,q34er6ty7
16534,Unable to detach media from past snapshot that causes warnings,other,other,VirtualBox 5.1.14,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
16535,High CPU on Host while Low CPU on Guest,other,other,VirtualBox 5.1.14,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
16536,Windows 7 guest - cannot control-click to select items,Linux,Windows,VirtualBox 5.1.14,2017-03-07T15:32:44Z,2017-03-07T15:32:44Z,"Hello,

Holding the left ctrl key and clicking into items to select them does not properly: After having selected 3 o 4 items, the selection is gone. It happens with Explorer and Groupwise (mail client).

If I disable 'Mouse Integration' it works properly.

I downgraded to 5.0.32 and now it works properly with 'Mouse Integration'

I think this is somewhat related to:
https://www.virtualbox.org/ticket/1766
https://www.virtualbox.org/ticket/15714

But and I'm not sure that was an OSX only issue since we have similar problems here with 5.1.14 running on Centos 6.8 with Win7 as a guest.

Regards, 

  Edgar

",esaumell
16537,Hgh screen resoluton on a MS-DOS 6.22/Win 3.1 VM,Windows,other,VirtualBox 5.1.14,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
10309,USB is busy with a previous request [E_INVALIDARG (0x80070057)],Windows,Windows,VirtualBox 4.1.8,2017-03-08T09:03:23Z,2017-03-08T09:03:23Z,"Hi,
I still have problems with connecting my USB device on this Win7-64bit host to a WinXP SP3 guest in 4.1.8 with usb_extension 4.1.8 and guest additions 4.1.8.

Connecting some usb flash drives succeeds but connecting my USB-to-CAN - device from peak-systems ([http://goo.gl/MSxX1 more info]) is not working. In earlier versions I got a message when starting the guest like ""Virtualbox USB is installing..."" and after the next complete restart of my computer the device was working. But now I don't get the windows tray message ""Virtualbox USB is installing..."" and if I want to connect my usb device while vm is running I get the error

{{{
Das USB-Gerät VER1:PEAK    
VER2:02.8.01        
DAT :06.05.2004
TIME:09:35:37
                             ... [1C11] konnte nicht an die virtuelle Maschine Windows XP gebunden werden.

USB device 'VER1:PEAK    

VER2:02.8.01        

DAT :06.05.2004

TIME:09:35:37

                             ...' with UUID {2fb58d0c-81b4-4505-9984-a67bfc272a87} is busy with a previous request. Please try again later.

Fehlercode:E_INVALIDARG (0x80070057)
Komponente:HostUSBDevice
Interface:IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee:IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
}}}

USB-filters are set correctly, as already mentioned other usb mass storages are working. On my host this peak usb device is running with latest drivers and all seems to work.

I've been searching already for some hours in google and had a look at [https://www.virtualbox.org/ticket/3033 #3033] and [https://www.virtualbox.org/ticket/5343 #5343] and [https://forums.virtualbox.org/viewtopic.php?f=5&t=31926 Forums] but nothing solved it until now.

Is there a way to find a solution? I don't want to reinstall earlier versions...
Is there a problem to disconnect the device from host because it's busy?

Thanks for your help",Jacky Ryan
15597,"Kaspersky hangs VirtualBox 4.3, 5.0, 5.1 on C2Duo E6850, Xeon L5420",all,Windows,VirtualBox 5.1.0,2017-03-09T06:35:58Z,2017-03-09T06:35:58Z,"Kaspersky EndPoint Security 6.0-10.2, Kaspersky Free 16
in VirtualBox 4.3, 5.0, 5.1 
HANGS on C2Duo E6850, Xeon L5420
work normally on i5

update antivirus databases is ok. if start any type of shield (file, network..) then hangs.

hosts:linux32,linux64,win7x64
guest:winxp

---

or hangs with 100% load of vm cpus,
or error (log file included)",unicorp99
16503,VM title cannot contain slashes,Windows,all,VirtualBox 5.0.16,2017-03-09T09:24:26Z,2017-03-09T09:24:26Z,"When renaming a virtual machine to a name containing ""/"", an error appears about VM folder not being able to be moved. The slash is a very useful symbol in names and should be supported.",Urmas
16532,"Wrong spanish word used since a long time ago: ""eliminar"" -> duplicate of #4503",all,all,VirtualBox 5.1.14,2017-03-09T14:02:51Z,2017-03-09T14:02:51Z,"Hello,

Just giving some help on Spanish word used for CD extraction in virtualbox VM settings.

Where it says ""Eliminar disco de la unidad virtual"" it should say ""quitar disco de la unidad virtual"" or maybe ""extraer ..."". This is because, in spanish, ""eliminar"" is related to ""destroy, eliminate"" wich makes one think or doubt if the ISO file will be deleted from the hard drive.


Thank you",raulrrojas
16519,Network bandwidth limit in GUI,Windows,all,VirtualBox 5.1.14,2017-03-09T15:17:34Z,2017-03-09T15:17:34Z,It would be good if one could adjust the network speed or limitation easily in the GUI. The detour via the VBoxManager is very cumbersome.(https://www.virtualbox.org/manual/ch08.html --> bandwidthctl),LMS23
16442,Could not install Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924,Windows,other,VirtualBox 5.1.14,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
16387,virtualbox 5.1 not reading properly certain box.ovf files?,other,other,VirtualBox 5.1.12,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
16552,Guest is super sloooow,Mac OS X,Windows,VirtualBox 5.1.16,2017-03-11T19:44:52Z,2017-03-11T19:44:52Z,"Don't know why Win XP and 7 (64bit) are both super slow!

macOS Sierra 10.12.2",Mungo
11496,Vboxmanage and host-only interfaces,Windows,all,VirtualBox 4.2.6,2017-03-12T09:28:34Z,2017-03-12T09:28:34Z,"Original findings and history can be found here -> https://forums.virtualbox.org/viewtopic.php?f=6&t=54119
[[BR]]

Under Windows, when trying to use host-only adapter commands on vboxmanage, they fail intermittently and return this:
{{{
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.
}}}

Taken from the forum post :
{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       192.168.74.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       172.17.101.143
NetworkMask:     255.255.0.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
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.
}}}

{{{
c:\Program Files\Oracle\VirtualBox>Vboxmanage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            a5f0012b-7729-4d31-8d4a-744f67e13797
DHCP:            Disabled
IPAddress:       192.168.123.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:dc5b:cdf6:ea70:c8a2
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:94:7b
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101.143 --netmask 255.255.0.0

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
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.

c:\Program Files\Oracle\VirtualBox>ipconfig

Windows IP Configuration
--snip--
Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::dc5b:cdf6:ea70:c8a2%25
   IPv4 Address. . . . . . . . . . . : 172.17.101.143
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
--snip--
}}}

Again, this problem is very intermittent.

4.2.4 & 4.2.6 currently broken.",Max D
16554,"VirtualBox on Windows 10 leaks hostonlyifs, turning them into bridgedifs which cannot be removed",Windows,Linux,VirtualBox 5.1.14,2017-03-12T09:34:39Z,2017-03-12T09:34:39Z,"It has happened twice now on my machine. The first time I lost hostonlyif 1 through 5 after an Vbox upgrade - searched a while for a solution, but gave up and created new ones ""VirtualBox Host-Only Ethernet Adapter #6"" through #12. That was more than 6 months ago.

Last week I noticed that my host only interfaces were gone again. Not sure on which upgrade, but I was on a 5.0 version. Upgraded to the latest, and some cleanup and reboots, and the problem is still there. Did not try an uninstall and reinstall because that didn't help the last time.

The current state is as follows:

I can create and delete host only interfaces, but the starting number is ""VirtualBox Host-Only Ethernet Adapter #13""
""VBoxManage.exe list -l bridgedifs"" returns a list with all my lost host only interfaces - but I cannot find a command to delete the bridged interfaces.
I can find these in the windows registry by searching the GUID, and also by name in Computer/HKEY_LOCAL_MACHINE/SYSTEM/Setup/Upgrade/NetworkDriveBackup/Control/Class but hesitate to mess with the registry manually, because there are too many references to clean up by hand. Searched for a powershell utility that could clean and free them up, but didn't find one.
Looking for help. Partial output of ""VBoxManage.exe list -l bridgedifs"" looks like this - as you can see by the name they used to all be host only ifs:

PS C:\WINDOWS\system32> VBoxManage.exe list -l bridgedifs

Name: VirtualBox Host-Only Ethernet Adapter #8 GUID: ef9a148d-dbbd-4eac-a072-bae5f0aae49b DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #8

Name: VirtualBox Host-Only Ethernet Adapter #3 GUID: 873d770d-328c-4af6-a0e8-900433a03cf6 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

Name: Microsoft Virtual WiFi Miniport Adapter GUID: a35fb3ad-bb85-4bfc-b9c1-05ce81d512cb DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-Microsoft Virtual WiFi Miniport Adapter

Name: VirtualBox Host-Only Ethernet Adapter #10 GUID: 1e88234f-d548-4b03-a2c2-b7c73f1016b1 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #10

Name: VirtualBox Host-Only Ethernet Adapter #6 GUID: fed303cd-386b-4f60-8419-1c71b53fa90a DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #6

Name: VirtualBox Host-Only Ethernet Adapter #2 GUID: f6d1349b-82f4-4ce2-ae42-e7fb19f7fdf4 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

",rezroo
16555,Windows 10 guest crashes during USB disk access after upgrade to v5.1.16,Mac OS X,Windows,VirtualBox 5.1.16,2017-03-13T15:59:09Z,2017-03-13T15:59:09Z,"I have been running a Windows 10 Pro 64-bit virtual machine on my early 2016 MacBook Pro for several months with no issues. I am running the latest macOS Sierra. 
Today I upgraded from v5.1.14 to v5.1.16. Now the machine will crash (abort) at random times but usually coinciding with access to my USB external drive. 
I had to revert to v5.1.14 and roll Guest Additions back, then the system was back to normal and no crashes.
I will be sticking to v5.1.14 until the broken update is fixed.",S_Vbox_User
16558,missing menu item to enable/disable virtual screen,Windows,Linux,VirtualBox 5.1.16,2017-03-13T17:51:02Z,2017-03-13T17:51:02Z,"While Debian Linux Virtualbox machine running on windows 7 host with 3 screens configured, there is no longer a menu item to enable/disable virtual screens.  Lost the menu item one I messed with toolbar and menu placement configuration. Also, hover over disable toolbar icon shows 3 displays, but right click does not bring up any menu either.  ",smichel
16559,Mouse pointer misaligned,Windows,Linux,VirtualBox 5.1.16,2017-03-14T09:13:12Z,2017-03-14T09:13:12Z,"Host Windows 7, guest Fedora 25, VirtualBox 5.1.16
Two displays (different resolutions), extended

The mouse pointer is misaligned in several applications. After started Fedora 25, I click Activities in top left corner. The sidebar with activities appears on the left side of the display. At this moment no problems with mouse alignment, i.e. the icon highlights when the mouse hoovers it.

I click 'Show Applications' from the sidebar. The list with applications shows up. Now the mouse is misaligned: the icon that is highlighted is not the one where the mouse pointer is. E.g. when the mouse is in the middle of the display, a icon much further to the right lights up.

I couldn't find a solution for it. Latest updates for the Windows host and Fedora guest are installed.
",peterka
16553,Virtual Machines running very slowly,Windows,Linux,VirtualBox 5.1.16,2017-03-14T09:18:51Z,2017-03-14T09:18:51Z,"Hi there,

Apologies if this turns out to be something trivial, but I hope you can help - I've been running Kali Linux / Metasploitable / Windows XP virtual machines using virtual box with no issues until a couple of weeks ago they all suddenly started going unusably slowly, taking ages to even log in and even then extremely laggy to use.

I'm running windows 10 on a HP Desktop with Dual core 1.9GHz and 8GB RAM

What I've tried:

Allocating more RAM / Vram to the VMs - Kali 2GB / 128MB Video

switching between 64-bit and 32-bit versions (my OS is 64 bit)

Uninstalling Vbox and removing all VMs, then re-installing them.

changing chipset from PIIX 3 to ICH9

enable I/0 APIC has always been checked
Hardware clock in UTC time always checked
Enable PAE/NX always checked
Video - Enable 3D Acceleration checked, 128MB allocated 
Storage controller SATA, AHCI, Port count 1, Use host I/O cache checked
Network adapter enabled, NATNetwork selected

I noticed that in the system settings, the 'acceleration' tab was suddenly 'greyed' out - this definitely wasn't the case previously. After some digging, I realised this was related to VTx acceleration, so I logged into my BIOS, enabled it and the acceleration tab came back - I checked the box, but unfortunately it has made no difference. Paravirtualization interface set to 'Legacy' (as it has been), Enable VTx/AMD-v checked, Enable nested paging checked.

Seems really strange as it was working perfectly well previously, so obviously something has changed... perhaps some windows update has caused problems, I have no idea.

I have the same setup running on other machines in the school I work at - older apple machines with a lower spec than my own, and it works fine on them!

Any assistance you can offer is greatly appreciated - sorry if I haven't provided enough info, please let me know what you need.

Many thanks,

George



",GMullin
16560,Multiple password prompts for encrypted drives,other,other,VirtualBox 5.1.16,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
16565,5.1.16 Guest Additions render CentOS7 VM unusable,Windows,other,VirtualBox 5.1.16,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
11802,Enable user to set a separate directory for current state,all,all,VirtualBox 4.2.12,2017-03-16T13:16:54Z,2017-03-16T13:16:54Z,"This enhancement is an alternative solution to Ticket #11726.

While the suggested enhancement in 11726 covers the problem somewhat, this here would be the fullscale solution.

Just as you can set a directory for snapshots of a given virtual machine, you could now also set the directory for the current state.
This would enable running current state from faster drives, such as RAM disks.",bostjan
16322,Allow specifying a VHD diff file location when cloning,Windows,Windows,VirtualBox 5.1.12,2017-03-16T13:19:38Z,2017-03-16T13:19:38Z,"When cloning, I expected to be able to specify the destination folder when using the diff method, just like you can when creating a new machine and creating a new disk.",Will Power
16541,W10 guest crashes on Win8.1 host all the time (ICH9),Windows,Windows,VirtualBox 5.1.16,2017-03-16T13:19:47Z,2017-03-16T13:19:47Z,The screen freezes so I can't make out what the bluescreen is.,Stanzilla
16365,Error after clean Install VirtualBox 5.1.12 on Windows 7 64 bit.,Windows,all,VirtualBox 5.1.12,2017-03-17T10:14:38Z,2017-03-17T10:14:38Z,"Hello, I'm on Windows 7 64 bit.

After try to upgrade VirtualBox from 5.0.x to 5.1.12, I received following error:

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_INVALIDVALUE.

Error Code: 
REGDB_E_INVALIDVALUE (0x80040153)
Component: 
VirtualBoxClientWrap
Interface: 
IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

No one of any version the last stable or the previous one is not working, after install I received same errors. 

Tried to clean registry manually and via software, reinstalled any component of Virtualbox, no one was not help. ",aidjek
16540,"Deleting older snapshot reproducibly, deterministically corrupts newer snapshot",Mac OS X,all,VirtualBox 5.1.14,2017-03-17T10:44:30Z,2017-03-17T10:44:30Z,"On a virtual machine with a series of snapshots, deleting one of the older snapshots will, under some circumstances, cause changes to the contents of the virtual disk on newer snapshots. (That may be an overly simplified description, but I believe the reduced test case will clear up the details.)

The real-world manifestation of this bug is that, on a Win10 1607 VM of mine, deleting one of the older snapshots causes the Start menu to malfunction (lose the Settings button and all tiles) on newer snapshots.

I created a reduced test case by deleting as many snapshots as I could without the corruption happening, then creating and using a quick-and-dirty program to replace each non-empty (i.e. not all zeroes) 1MB block in each VDI file with a repeated byte value. (By the way, if I do this on all blocks rather than all non-zero blocks, the bug is no longer reproducible.)

Instructions to reproduce:
1. Extract the attached xz-compressed tar archive (it will expand to something like 33GB) and add the resulting VM to VirtualBox.
2. There are 3 snapshots: Snapshot 1, Snapshot 5, and Snapshot 11. Get the md5sum of Snapshot 11 by doing one of the following:
  a. `VBoxManage clonemedium 7e718487-9538-4552-b223-69ce21b421d0 good.raw --format RAW` then something like `openssl md5 good.raw`
  b. Boot into a simple Linux CD/DVD (I used the Slackware 14.2 installer DVD), run `md5sum /dev/sda`, then power off the VM.
3. Delete Snapshot 5. (By the way, if you delete Snapshot 1 before deleting Snapshot 5, the corruption does not occur.)
4. Check the md5sum of Snapshot 11 again by doing one of the following:
  a. `VBoxManage clonemedium 750ff504-0292-427f-b108-f4c9b78f88df bad.raw --format RAW` then something like `openssl md5 bad.raw`
  b. Repeat step 2(b).

Expected results: md5sum should be `94157a72c97d2d61e288748ec4029b6a` both times.

Actual results: md5sum is originally `94157a72c97d2d61e288748ec4029b6a` but becomes `75dc8ef4596478dee7abf47780471c98`. An examination of the difference between good.raw and bad.raw shows that some sectors that are filled with zeroes in good.raw are filled with 0x2A ('`*`') in bad.raw (the pattern that I used to fill the non-zero blocks in the base VDI).

I think what's happening is, data that was originally non-zero in the base VDI and that was overwritten with zeroes later on (probably in Snapshot 5) is being incorrectly reverted back to the older non-zero data in Snapshot 11 after Snapshot 5 is deleted. (This is the same pattern of corruption that I was seeing with the original Windows 10 VM. I did not dig into why this particular pattern of corruption causes the Start menu to malfunction.)

Emotionally, I'm tempted to set the priority of this bug to ""blocker"" because I'm not happy about data corruption. However, I'm able to reproduce this bug going back at least to VirtualBox 4.3.4 (the oldest that I've tested so far), so this bug has been around for a while and I'm guessing that either it doesn't happen often in general use or it usually has insignificant consequences.

So far I have only tested this on a Mac OS X host -- I have not yet tested a Windows or Linux host.",Barry K. Nathan
14724,Need way to move virtual-disk files of running VM,Linux,other,VirtualBox 5.0.6,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
11726,Add ability to flush (merge) Current State into the parent snapshot,all,all,VirtualBox 4.2.12,2017-03-17T11:07:48Z,2017-03-17T11:07:48Z,"
I have encountered a complex situation which can be resolved by this.

I would like to use VirtualBox with fast disks to store the Current State on.
By fast disks, I mean RAM disks (or small SSD disks if that's what someone has available).

When using RAM disks, the space is very precious. But even when we buy a lot of RAM, it still takes long to copy big VMs to it, as the copy is performed from slow drives. Equally slow is copying the changed VMs back when we are done.

Therefore, copying is not ideal.
The idea is to keep big VMs in their directory on an SSD disk, while the snapshots directory is relocated to the RAM disk.
Like this, non-changing data is read occasionally, but all volatile data is accessed with almost no latency.
Also, an SSD disk is spared a lot of wear and tear (assuming using SSD disk as 'the slow' disk).

The funny thing is, that creating such a setup is easy with Virtual PC, because user has total control over the differencing disk chain and the ""undo"" feature. I tried to do it with VirtualBox GUI and VBoxManage, but couldn't. Maybe someone will correct me, but as far as I know, it is not practically possible with the current VirtualBox.

There are several issues.

1. Currently, one may keep only one snapshot per machine, as this is what would actually stay on the SSD. All others would be moved to RAM disk and become volatile. While issue 1 is annoying, it can be bypassed by creating linked clone VMs. Like this, when each machine is kept at maximum of one snapshot, it could retain it on the SSD. However, issue 2 crushes this idea as well - linked machines cannot be used.

2. All machines need to be independent, even when I would like to use linked clones to represent several states of the system. This is because when I create a linked clone, VirtualBox creates the initial Current State as a sort-of-snapshot. Now, to utilize the RAM disk, one snapshot of course must be created (for Current State to be pushed onto the RAM disk). But even if I assure that the original linked VM snapshot is placed on the SSD, the moment I want to commit some changes, I need to create a new snapshot and delete the old one. And, because the old ""snapshot"" is not a base virtual harddrive, it gets merged into its child - onto the RAM disk.
Issue 2 is just impossible to solve, as VirtualBox cycles the differencing disks in such a way.
Currently, one cannot merge changes from Current State into its parent (it only makes an exception if the parent is the only snapshot on a non-linked VM).
Also, not being able to use linked clones, it means full clones need to be used - always.
So this also causes wasting a lot of space for big VMs, and takes a long time when creating them.
Not to mention unnecessary wear and tear on the SSD, when you use it as 'the slow' disk.
Often, you already know you will discard all changes at the end of session, and you don't want the tens of new gigabytes to touch the SSD at all. That's why OS caching is not a suitable replacement, even if OSes would happily use 30 GiB RAM as read/write cache (which they don't!).

This is exactly why RAM disks exist in the first place: to speed up reads, accumulate a lot of writes, and in the end perform only one flush, or (even more often) discard the changes.


'''The solution.'''
It's pretty simple.
For the Current State, add the option ""Flush changes to <name-of-parent-snapshot>"".

This would merge the changes to the parent disk.
Also important: when doing this, neither of the two disks would have its filename, or disk location, changed.
Parent receives the changes, and child (the Current State) becomes empty.
If the child disk needs to be destroyed in the process, it should be recreated with the same name.



This enables setups which utilize snapshot directories on RAM disks, including using linked clones.

And, it also adds a good option which I believe many people miss (I know I do).
Why do we need to do this:
1. Create a new snapshot, retype the same name as the snapshot above.
2. Delete the previous snapshot.
when we just want to flush some small changes from the Current State to the snapshot above?

The ""flush"" option would be most welcome for this reason as well, removing the annoying two-step operation, not to mention the expected speedup (it usually takes much longer to merge parent into child, as the child is the differencing disk and usually caries less data).

Naturally, the new option would only display when Current State is changed and it actually has a parent snapshot.
",bostjan
16548,Win7 guest does not enumerate COM port with new MacBook Pro,Mac OS X,Windows,VirtualBox 5.1.14,2017-03-17T11:13:35Z,2017-03-17T11:13:35Z,"I have a new MacBook Pro (USB-C ports only) with macOS Sierra 10.12.3.  It has a FTDI232R serial device connected.

Attaching the serial device causes Win7 to show the device in Device Manager with errors and it cannot enumerate a COM port.

This was never a problem with my old MacBook.

I tried using VirtualHere (USB over IP) between host and guest.  This solution usually solves my USB problems with VB, but not in this case.  It has the exact same symptoms.

I tried running VirtualHere on a RaspberryPi and then the FTDI232R device successfully enumerated in the Win7 guest.

Therefore I think something has changed with the USB on the new MacBook Pro, and VB needs modifications to support it properly.",BrendanSimon
15851,"Can't use an USB device in Windows 10 guest: ""is in use by someone else""",Mac OS X,Windows,VirtualBox 5.1.4,2017-03-18T18:45:01Z,2017-03-18T18:45:01Z,"I'm running Windows 10 guest on OS X El Capitan host.

I can't ever pass USB smart cart reader to the guest using the status bar icon because of the following error:

{{{
Failed to attach the USB device SCM Microsystems Inc. SCR3310 v2.0 USB SC Reader [0204] to the virtual machine Boot Camp.

USB device 'SCM Microsystems Inc. SCR3310 v2.0 USB SC Reader' with UUID {34262c72-da4e-4d08-99ff-ca2bee575214} is in use by someone else.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

The USB device in question is not really in use other than being plugged in.

Things I tried so far:
1. Create and use an USB filter
2. Switch between USB 2 and USB 3 in VM settings.

This is a critical issue for me, because I need to use VPN for work and I can't use the host VPN either because of VM crash in NAT mode (a separate issue).",DKroot
16581,Scaled mode: documentation explains different,Windows,other,VirtualBox 5.1.18,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
16249,Qt frontend doesn't set HiDPI attributes,other,all,VirtualBox 5.1.10,2017-03-19T20:48:32Z,2017-03-19T20:48:32Z,"The VirtualBox Qt Frontend doesn't set HiDPI Qt attributes, so the the rendering on HiDPI display is horrible.

See the attached patch fixes the rendering of the management GUI. More details are at:

  https://doc.qt.io/qt-5/highdpi.html

However the guest window still doesn't not render correctly. I think it uses images for that and needs to be adapted for that.

https://doc.qt.io/qt-5/qpainter.html#drawing-high-resolution-versions-of-pixmaps-and-images

So the attached patch is only half of the story.",Andreas Schneider
16585,guest additions initscripts should be more flexible,other,Linux,VirtualBox 5.1.18,2017-03-20T13:24:28Z,2017-03-20T13:24:28Z,"Adding options to the virtualbox guest additions startup requires editing the init script.  This is a pain, especially when installing from source or creating a new install. Note that with systemd the init file isn't in /etc/init.d, but rather /opt/VBoxGuestAdditions-$VERSION/init - which is refreshed on an install/upgrade.

Most init scripts separate the startup script from options by providing a file in /etc/default or /etc/sysconfig.

e.g. This should work for most distributions conventions
{{{
/etc/sysconfig:
OPTIONS=""--disable-timesync""

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/linux/installer/vboxadd-service.sh

[ -f /etc/default/vboxadd-service ] && . /etc/default/vboxadd-service
[ -f /etc/sysconfig/vboxadd-service ] && . /etc/sysconfig/vboxadd-service

and 
         vboxaddrunning || {
             echo ""VirtualBox Additions module not loaded!""
             exit 1
         }
         testbinary
-        daemon $binary --pidfile $PIDFILE > /dev/null
+        daemon $binary --pidfile $PIDFILE $OPTIONS > /dev/null
         RETVAL=$?
         succ_msg
     fi

     return $RETVAL
}}}",Timothe Litt
16586,Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) on Ubuntu 16.04.2 LTS,Linux,Linux,VirtualBox 5.0.36,2017-03-20T15:23:34Z,2017-03-20T15:23:34Z,"One of our Production-VMs (the gateway) just crashed with this error after 3.5 days of runtime.

We have no idea how to debug this further.
Googling does not really show up anything helpful either.

* Guest + host have vbox-extensions installed
* host did not run out of ram
* Guest worked fine for weeks prior to getting moved to this Guest-Machine.

Host and Guest are Ubuntu 16.04.2 LTS.",Someone
10620,"screen locks in host OS, despite actively working in fullscreen guest OS",Linux,Windows,VirtualBox 4.1.14,2017-03-20T18:17:18Z,2017-03-20T18:17:18Z,"I am running Ubuntu 12.04 (64 bit) as the host OS and Windows 7 (64 bit) as the guest OS (in fullscreen mode). If I work long enough in the Windows 7 environment and then go back to my host OS (using cube rotate in compiz), the host OS presents my desktop for 1-2 seconds and then locks the screen with a password lock screen. Once I enter my password, the screen is then unlocked and I can proceed to work in Ubuntu.

This is easily repeatable and was not the case when running Windows XP (32 bit) as a guest OS on Ubuntu 10.04 (64 bit host OS). Previous releases kept the host OS from locking, despite working in the guest OS. If no actions were taking place in the guest OS, then the host OS would lock, after the predetermined time period for locking a screen would pass.",sf_basilix
16594,Apple trackpad bluettooth doen't work anymore,other,other,VirtualBox 5.1.18,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
16590,extension pack breaks safari and unlock on Mac OSX,Mac OS X,all,VirtualBox 5.1.18,2017-03-22T19:55:54Z,2017-03-22T19:55:54Z,"I installed the extension pack (latest downloaded from the website) and after that I had the following issues on my Mac host:
- Safari stopped working and could not be started again
- when screen was locked I could not unlock it anymore.  Only option was a reboot.

Removed extension pack and functionality is back to normal.",Dave Geysemans
16589,Raw mode release assertion,Windows,Linux,VirtualBox 5.1.18,2017-03-23T11:00:33Z,2017-03-23T11:00:33Z,"Ubuntu Linux 16.04 server as guest,
Windows 7 as host

Virtualbox version 5.1.18r114002

While updating the Linux kernel (using apt), the following error stopped the virtual machine:

{{{
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0xe555a9ac.

Click OK to terminate the program
Click CANCEL to debug the program
}}}


[[Image(https://i.imgur.com/K0duG4a.png)]]
[[Image(https://i.imgur.com/SRYeDD0.png)]]",Brianetta
16572,shared folders can not be mount,Linux,Linux,VirtualBox 5.1.16,2017-03-23T11:14:28Z,2017-03-23T11:14:28Z,"I use Linux Mint LMDE2 (Jessie) as Host with some Linux Guests.

Since VirtualBox 5.1.16 can shared folders not be mounted on the guests.
Until Version 5.1.14 its well done.
(5.1.18 don't work too) 

I gone back to 5.1.14 and it works fine.",Alex175
16596,Unable to access desktop of host (Mac OS X) when Seamless mode is enable (Guest: Windows 7),Mac OS X,Windows,VirtualBox 5.1.18,2017-03-23T18:41:22Z,2017-03-23T18:41:22Z,"Host: Mac OS X 10.11.6
Guest: Windows 7, Extension Pack including Direct X support installed

When Seamless mode is enable, desktop of host is visible as usual. However, it's unable to click icons of desktop of host. It's still possible to switch application by Alt+Tab or Multi-Touch gestures.

I only tested on this combination only, no others yet.",DolphinKeeper
16243,"OpenGL acceleration messed up in guest OS (flickers, ghost windows, buffers showing...)",Mac OS X,Windows,VirtualBox 5.1.10,2017-03-23T21:43:18Z,2017-03-23T21:43:18Z,"Dear Developers,

I am running the latest VirtualBox 5.1.10 r112026 for MacOS Hosts and multiple Windows OS guest systems with the respective and latest VBoxAdditions.

3D Acceleration is activated
2D Acceleration is activated 

Hoever when running a OpenGL based application in the guest (e.g. Solidworks) it always messes up the display by showing buffered window contents (which are either in the background or contents of windows that have already been closed)  right on top of parts of the openGL window. It happens most of the time when the mouse is moved around.  

I have seen this problem around for quite a while now (using Virtualbox since Version 3.x) and this issue somehow has never been solved.

Is there any hint, patch or workaround? 
Disabling the 3D Acceleration completely solves the problem but the CAD application gets terribly slow then. 

Thank you very much.
Best regards

Thomas ",careyer
16601,Windows 10 on Surface Book virtualbox install,Windows,Linux,VirtualBox 5.1.18,2017-03-24T01:13:41Z,2017-03-24T01:13:41Z,"I have a brand new Microsoft surface pro book with windows 10.  I have the latest update.  I even uninstalled
the software, removed the files off the hard, removed from windows registery
then reinstalled virtualbox.  I downloaded the latest version of Kali Linux
and I get the same problem.  Windows crashes on me and restarts itself
saying it is writing the report.  I even reinstalled windows 10 and then
did a update, downloaded a fresh virtualbox, fresh kali Linux and the system
bombed out again.  Is there anyway we can fix this problem?",henrygh101
10014,"Linux (64-bit) host, Windows 7 64-bit guest: can't execute files from shared folders",Linux,Windows,VirtualBox 4.1.6,2017-03-24T20:32:11Z,2017-03-24T20:32:11Z,"With a Linux (debian 64-bit) host and a Windows 7 64-bit guest, I've enabled shared folders.  Most access works fine, and the performance is great.  However, I am not able to execute programs (.exe, etc.) or do certain other operations such as opening pdf files by double-clicking on them.  Instead, I have to copy the folders locally in order to operate on them.

I have seen other reports similar to this with Windows host and Linux or Solaris guest that can be resolved by specifying permissions at the time of mounting, but I don't see any options like this for attaching a Windows share.  (My Linux experience is much deeper than my Windows experience.)  I know that when sharing a volume on Windows, you can set things up this way, so perhaps this is intentional.  My shared folder is set as ""full"" access. ",Jay Berkenbilt
16608,Guest LPT error stops VM to start since VM versions 5.1.4 ... 5.1.18,Windows,Windows,VirtualBox 5.1.18,2017-03-25T13:34:44Z,2017-03-25T13:34:44Z,"Host Win7Pro 64bit, guest Win XP Pro, on-motherboard LPT. Worked fine until v5.1.2. Starting from v5.1.4 ... v5.1.18 all versions crash during starting guest. LPT initialization error. If downgrading to v5.1.2 (with corresponding extensions)- works fine again.",Lager-Ju
16612,Snapshots: Inheritance of options from parent snapshot should be improved (wishlist?),other,other,VirtualBox 5.1.18,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
14340,VBoxSVC usb initialization causes host USB device to disconnect,Windows,all,VirtualBox 5.0.0,2017-03-27T00:56:53Z,2017-03-27T00:56:53Z,"VirtualBox is causing the (host) SD card reader on my Microsoft Surface Pro 3 to disconnect/crash when VBoxSVC attempts to enumerate / initialize theUSB devices on the host. Any VirtualBox activity that attempts to enumerate the host USB devices (i.e. starting the VirtualBOX GUI, or executing a ""VBoxManage list usbdevices"") appears to cause this problem.

This occurs without any guest VM's running, and without any USB devices being configured for capture by VirtualBox.

I don't know if this is a bug in the Windows SD card driver that's being exposed by VirtualBox, or if it's a bug in VirtualBox itself.

To reproduce:
1. On a Surface Pro 3, mount an SD card
2. Initiate a large file copy to the SD card.
3. While the file copy is underway, execute the ""VBoxManage list usbdevices"" command. (or just start the VirtualBox GUI)

Expected result:
Files continue to copy to the SD card

Actual result:
The SD card volume drops offline. Windows displays a ""destination does not exist"" error. The windows event log shows a ""An error was detected on device \Device\Harddisk2\DR2 during a paging operation."" error.

The only error that I see in VBoxSVC.log file is ""Getting USB descriptor failed with error 31"". 

I have not attached the VBox.log file, as this error occurs without any guest instances running.",Hugh
16406,Display bugs on HiDPI Windows hosts with two displays,Windows,all,VirtualBox 5.1.14,2017-03-27T15:47:08Z,2017-03-27T15:47:08Z,"I'm running VirtualBox on a Windows machine which has two screens: one HiDPI with 200% scaling enabled, and the second one using 100% scaling.

When I launch VirtualBox Manager, it launches with 200% scaling (which is correct), but when I drag VirtualBox Manager window to my second display, it doesn't rescale correctly (see attached screenshots).

What's worse, VM window doesn't scale at all when dragged to the second screen.

This bug was introduced in 5.1.0 release.",VasilyA
15179,Severe time drift in guest OS,Linux,Linux,VirtualBox 5.0.14,2017-03-27T18:51:09Z,2017-03-27T18:51:09Z,"Installed ubuntu 14 lts guest on centos7 virtualbox Version 5.0.14 r105127

ubuntu guest has latest version: 5.0.14r105127

everything is standard and updated.

Problem is that time drift is so extreme that i run into trouble.

the guest loses about 10 seconds every 15 minutes!

i already tried setting a ntp daemon.. but it does nothing.. also adding a crontab with ntpdate does nothing.

also adding --timesync-set-start --timesync-set-on-restore 1 --timesync-set-threshold 5000 to /etc/init.d/vboxadd-service does not help.


",geegee
16615,No USB Device Access with NoMachine v5.2.11 Innstalled,Windows,Linux,VirtualBox 5.1.18,2017-03-28T06:25:45Z,2017-03-28T06:25:45Z,"With the current version of NoMachine installed (v5.2.11) it is not possible to pass thorugh USB devices to VirtualBox.
The device lists in available devices, and when selected is removed from the Windows host. 
The VirtualBox status bar indicates that no device is captured and shows no read or write activity.
If you hover over the status of the device, this says the device is captured, but 'lsusb' in a Linux guest does not show the device, only the hub.
Attempting to capture the device results in an error 'E_INVALIDARG' and a message that the device is busy.
Removing the USB device and reinserting leads to multiple copies of the device appearing in the list.
To clear the list, VirtualBox has to be completely restarted.
This appears to be a clash between the USB device handing in NoMachine and VirtualBox.
I was trying to setup some VirtualBox VMs to test the current version of NoMachine.",Karl Foley
16616,The instruction at 0xdbbf26a0 referenced memory at 0x00000018. The memory could not be read.,Windows,Windows,VirtualBox 5.1.18,2017-03-28T10:21:12Z,2017-03-28T10:21:12Z,"This happens when Guest VM window is minimized and I double-click it in VirtualBox Manager. Happens every time.

Logs not attached as they appear to be showing the VM running happily and nothing whatsoever is in there to indicate its gone down.",danf84
15417,GUI Artifacts after opening Chrome,Windows,Linux,VirtualBox 5.0.20,2017-03-28T14:14:25Z,2017-03-28T14:14:25Z,"Starting from 5.0.16 theres been graphics artifacts which hang the desktop (Gnome 3) on a Ubuntu 14.04 guest with the latest Xenial LTS kernel (4.4) and guest additions installed on a Windows 7 64bit host.

The graphics artifacts effectively start after you open Chome and even restarting Gnome 3 doesnt resolve the artifacts. This partially happened in 5.0.14 but only for a few seconds when you initially open Chrome and then it goes away and is usable. From 5.0.16/20 this pretty much makes the GUI desktop unusable once you open Chrome.
",Julio Lajara
16617,Virtual Machine Launching Causes Touch Bar to Disappear,Mac OS X,Windows,VirtualBox 5.1.18,2017-03-28T17:13:00Z,2017-03-28T17:13:00Z,"It appears that when launching a virtual machine in VirtualBox, the Touch Bar functionality disappears system wide until the virtual machine is terminated.",Ben.S
16618,USB Device Filter ASK ME WHAT TO DO,all,all,VirtualBox 5.1.18,2017-03-29T12:21:46Z,2017-03-29T12:21:46Z,"Currently you need to set up a device filter for each USB device that you want to connect to VM instead of Host device.

It would be great if you could have a filter called ASK ME WHAT TO DO WHEN USB DEVICE IS CONNECTED

When this filter is enabled, and any USB device is plugged in, then a popup window would say ""Would you like to connect to Host computer or to VM #1 (or VM #2 or VM #3)""

Basically its a popup that asks where you to connect the newly plugged in USB device. This would eliminate the need of having to create seperate filters for new USB device you want to connect to a VM. It would also make it easier to move the device between VM and Host.
",jshrek
16620,Crash when removing USB device,Windows,Linux,VirtualBox 5.1.18,2017-03-29T16:07:08Z,2017-03-29T16:07:08Z,"I have a USB Wi-Fi dongle which I occasionally use from my virtual Linux guest (besides an ordinary Ethernet connection via the Windows host). I got into the habit of removing it virtually (i.e making it invisible to the guest via the VirtualBox pop-up menu → Devices → USB, then unchecking the relevant device) before saving the state of the virtual machine, because if I don’t do that I occasionally get my Linux guest’s system log spammed with error messages when I restore the virtual machine.

In 5.0.32 (and at least a couple of earlier versions) it worked without a hitch, but in 5.1.18 the guest crashes when I do it. Specifically, I get a Windows pop-up (and an entry in Windows application log) with a message like this:
>  VirtualBox.exe - Application Error : The instruction at 0x00007FFD56EA7D70 referenced memory at 0x00000000000000E8. The memory could not be read.

If I do not close the pop-up, the virtual machine crashes soon anyway. In one case, it crashed when I tried to save its state; in another, it crashed as soon as I tried to sync the filesystem in the Linux guest (via the sync command).

As the bug is a deal-breaker to me, I have returned to 5.0.32.

Host: Windows 10 Pro 64-bit[[br]]
Guest: Ubuntu 14.04.5 LTS 64-bit with Guest Additions installed",mgrzegor
16605,Network dropouts in guest since Windows 10 update to 1607 version,Windows,Windows,VirtualBox 5.1.18,2017-03-31T10:07:18Z,2017-03-31T10:07:18Z,"I got here following situation. I have a Windows 10 x64 guest on the same OS host. Right now I reduced the amount of installed programs in the guest to the minimum to find the culprit. So right now there is an antivirus (latest Nod32), Firefox and MP3 Player (Xmplay) beside the OS itself. I use the last program for Internet radio since XP days, and there were no problem until now, in and outside the VM. 

Since guest update to the 1607 I can see following behavior: after 15 or 20 minutes of the streaming player starts to buffer at 70-80 % spontaneously around once in a minute, which breaks a streaming experience. One still can listen to the radio, but this is a little bit annoying. This problem only occurs if the Firefox also running in the guest. Something, I don’t know what, but probably some advertisement or data refresh, loads a little amount of the data over and over again once in nearly a minute. I got some network bandwidth pictures which explain the network flow better. But the problem isn’t a bandwidth itself – I can run a bandwidth test, which would use the whole bandwidth and still there would be no buffering. The problem is a timing, because as one can see we have something like 6 or 8 KB/s from the stream constantly, but once in a while the browser adds some 18-20 KB/s to it. So after a while there are some de-synchronization in the flow, which causes the buffering.

This only happens in the guest and only if the browser running with some sites open. If one turns the browser off, there is no buffering. Also, this can’t be reproduced running same player and stream on the host, neither with Firefox also opened on the host with some sites in it, or with Firefox running in the guest, causing the same traffic shape on the host. First of all a thought that this was a new issue with a new VB version, but I tested this with following versions (5.0.30 - 36, 5.1.6, 5.1.10, 12, 14, 16, 18) and the picture is always the same. Changing network adapter from 82540EM to paravirtualized also brings no cure. I tested it with following version of the network adapter drivers (virtio-win-0.1.110, 112, 113, 117, 118, 126, 134), but it always looks the same. There were also no such problems as I updated the host first, before the guest. The clean install of the guest OS from the scratch also doesn’t change anything in this case, but installing the previous version of Windows 10 (1511) in the guest solves the problem. I think, that the problem caused by some TCP/IP optimization in the new Windows version, as described [[https://blogs.technet.microsoft.com/networking/2016/07/18/announcing-new-transport-advancements-in-the-anniversary-update-for-windows-10-and-windows-server-2016/|here]], the Initial Congestion Window 10 probably. If this is important – I hear following [[https://rfe04.akacast.akamaistream.net/7/509/437762/v1/ibb.akacast.akamaistream.net/rfe04?download=1|stream]] for example, but I think any other stream should also do the job. I would like to debug the network stack in the guest, but I don’t know how.

VM is running in the NAT mode. I hope that my description of the issue is clear, in spite of so much text.",boxer01
6236,"USB device ""cannot start"" after installation",Windows,Windows,VirtualBox 3.1.4,2017-03-31T14:31:13Z,2017-03-31T14:31:13Z,"Host:
  - Windows 7 Professional

Client:
  - Windows XP SP3 Professional

Synopsis: 

USB smart card reader (ACS ACR80) gets recognized in client, but when the driver installation finishes, Windows XP reports the following error:

""The device cannot start. (Code 10)""

I tried rebooting both host and client, then disabling EHCI (USB 2.0) but it made no difference.

In general, USB devices handling in VirtualBox is very tricky and far for perfect. I believe this aspect of the functionality requires far more attention in the future releases.

I like how elegant USB handling is in VMware Player, but I still prefer VirtualBox for many other reasons.
",Dragan Obrenovic
16622,Adding an SSD on 2-HD system can confuse drive assignments,Linux,Linux,VirtualBox 5.1.18,2017-03-31T15:00:41Z,2017-03-31T15:00:41Z,"Starting with a 2 HD Dell M6800, VB sees the drives as HD1 = sda & HD2 = sdb.

Adding a Samsung EVO 250GB SSD drive caused Linux to assign drives as:
 HD1 = sda, SSD = sdb & HD2 = sdc

My local Mageia Linux install repository resides on HD2p7. This physical source disk was originally defined in DIST[-pt].vmdk as sdb.  After the SSD was installed, VB could not see the installation files because HD2(sdb) was now at sdc.  

Simply editing DIST.vmdk to change the only occurrence of sdb to sdc resolved the problem.

Could this have been overcome by using UUID instead of sdX?
",Pierre Fortin
16634,Unexpected opening of a subwindow causes annoyance,Linux,Windows,VirtualBox 5.1.18,2017-04-02T01:55:28Z,2017-04-02T01:55:28Z,"If I'm staring a VM I'm noticing that sometimes after a few seconds a subwindow with the text ""Starting virtual machine ..."" and a progress bar is appearing. Since the subwindow opens delayed I have encountered the issue that it claims the focus and switches to it if I'm already working on another window which is annoying. Maybe there is a way to solve this issue.",Sworddragon
16633,Problem in Oracle VM Virtual Manager Screen,Mac OS X,all,VirtualBox 5.1.18,2017-04-02T14:44:48Z,2017-04-02T14:44:48Z,"On top left, when i click for the first time to full screen (green button), there is a defect on screen. the problem gone away if i click on any guest machine. i attached a screen to help you to see the problem.


regards,

Eduardo.",Farah
16501,All VM fails when changing dual monitor setup,Linux,all,VirtualBox 5.1.14,2017-04-04T16:27:10Z,2017-04-04T16:27:10Z,"Hello, here is what I get when I change the setup several times :
{{{
virtualbox --debug
Gtk-Message: Failed to load module ""canberra-gtk-module""
Qt WARNING: QObject::connect: No such signal QApplication::screenRemoved(QScreen *)
Qt WARNING: QObject::connect: No such signal QScreen::availableGeometryChanged(const QRect &)
Qt WARNING: QObject::connect: No such signal QScreen::availableGeometryChanged(const QRect &)
Qt WARNING: QPainter::begin: Paint device returned engine == 0, type: 2
Qt WARNING: QPainter::end: Painter not active, aborted
Segmentation fault
}}}
All virtualbox VM crashes. 

I'm running debian 8.7 with 4.9 linux kernel. 
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)
I'm using the radeon opensource driver. The dual monitor is working perfectly except for this issue.",gyust
16639,Virtualbox 5.1.X prevents Mac Sierra from sleeping / recognizing attached screen on resume from sleep,Mac OS X,other,VirtualBox 5.1.18,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
1766,ctrl key on OS X is not usable,Mac OS X,other,VirtualBox 1.6.2,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
16638,Don't import appliances if there's not enough space on disk,Windows,Linux,VirtualBox 5.1.18,2017-04-06T10:26:05Z,2017-04-06T10:26:05Z,"When importing appliances, it is common that the appliance file is smaller than the actual guest disk size.
Given that, if you are importing an appliance and you don't know the guest disk size, you'll get an error after the host disk is full.
Some import operations may take up to a hour, or more, so if you get the error after the import cannot continue, this is a little frustating to see the time you could save.

E.g.: I have a 20GB appliance the allocates more than 100GB. I was trying to import it on a disk with 80GB free. After 40min importing, I got the allocation error.

So, my suggestion is to show the final size for allocated space in the import dialog, or maybe even check the drive that the user is placing the VM disk and give a message like 'You don't have enough space to import that machine here', or something like that.",tgarcia
16577,VirtualBox Networking causing BSOD,Windows,Windows,VirtualBox 5.1.14,2017-04-06T11:26:54Z,2017-04-06T11:26:54Z,"After installation of VirtualBox I see very often BSOD with error message DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by nwifi.sys. This actualle makes the computer more or less useless.

I have found out that installing VirtualBox without networking solves the problem (restored backup of computer to point without any virtualbox installed and retried. Also did it again and installed with networking and BSOD is back on first reboot).

Host Dell XPS13, Windows 10 Pro 64bit build 10586.839. It's not affected bu guest OS as the BSOD shows up just by installing VirtualBox so there is some driver issue in the host OS/VirtualBox",TurboJens
16641,"Shared Clipboard, drag and drop, and mouse-dragging STOP working in Win XP Guest",Windows,Windows,VirtualBox 5.1.18,2017-04-06T21:10:22Z,2017-04-06T21:10:22Z,"I'm hosting in Windows 7 x64
Guest OS: Windows XP 5.1 SP3
I'm using Virtual Box 5.1.18r114002


I repeatedly get the following symptom. I can sometimes fix it by reinstalling the Guest Extensions (v5.1.18)

Mouse Dragging in the Guest OS (Windows XP) stops working. I can't drag Windows Xplorer window
I can't drag or paste files from Host to Guest. (If I copy a file from Host, and right-click in Guest, PASTE is disabled.)

This has been happening for months. Driving me crazy :(


",MrAnalogy
16492,WebEx screen sharing with Windows 10 host causes guest to crash and out of memory error.,Windows,Linux,VirtualBox 5.1.12,2017-04-07T11:48:20Z,2017-04-07T11:48:20Z,"When sharing a screen with Cisco WebEx while running a VirtualBox guest, the guest eventually crashes.  The host (Windows 10) complains about running low on memory, and the screen (or both screens) flicker or go blank.  Sometimes the host is usable after this but oftentimes it must be rebooted to become functional again.

The issue appears to be related to 3D acceleration.  When 2D/3D acceleration is disabled for the Linux guest, the issue goes away.

See:  https://forums.virtualbox.org/viewtopic.php?f=6&t=79382&p=385575#p385575

Host:  Windows 10 Enterprise 64 bit (Intel i5, 12 GB RAM)
Guest: Linux Mint 17 32 bit

Thx........",rbc
16531,VirtualBox has issue With my Windows 10 Build 15046,Windows,Windows,VirtualBox 5.1.14,2017-04-08T12:42:43Z,2017-04-08T12:42:43Z,"Hello

I have Windows 10 Build 15046 Installed in my Host, I also Installed VirtualBox. but When I started The Virtual Machine, It only show Windows 10 boot screen and VirtualBox BIOS initial screen, and It only Preview can Display Desktop, And the virtual machine window cannot display Windows 10 Guest desktop.

My Host: Windows 10 Build 15046

My Guest Windows 10 (1607)

Hope The issues will be resolved soon.

Thank you

-htjywf2008",htjywf2008
16259,Cannot start VMs due to VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED,Windows,all,VirtualBox 5.1.10,2017-04-10T07:02:31Z,2017-04-10T07:02:31Z,"On some windows hosts VirtualBox will not start VMs with DigitalGuardian installed. An error message box with ""VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED ... supR3HardNtChildPurify what:5"" appears. This has been reproduced on both a Windows 7 and 2K8R2 systems but not all Win7 and 2K8R2 machines. This is system configuration depended. I have a windows 7 machine where I uninstalled DG but left our driver in place and it still failed. I then copied an MS driver, vms3cat.sys, into dgmaster.sys rebooted and it still failed. I believe there is a logic error in the code that replaces suspect virtual memory.

I have a 2K8R2 VM that reproduces the issue.
",Stevel
16650,WXP VM crashs at startup after upgrade VB to 5.1.18 (raw mode),Linux,Windows,VirtualBox 5.1.18,2017-04-12T13:15:43Z,2017-04-12T13:15:43Z,"I have a WXP VM. It ocasionally broke.
I have upgrade VB to 5.1.18 version. I have upgrade also the extension pack.

VM start up crashes with error 

Not in text mode!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
emR3Debug: rc=VERR_REM_VIRTUAL_CPU_ERROR

My OS is Ubuntu 16.04",EduardoNicolano
16645,"VirtualBox.dll"" failed, rc=1790",Windows,other,VirtualBox 5.1.18,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
11720,Solaris Autostart service can only work for 1st user in staff group => fixed in SVN,Solaris,other,VirtualBox 4.2.12,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
16662,SoftICE Doesn't Refresh,Windows,Windows,VirtualBox 5.1.18,2017-04-18T11:02:35Z,2017-04-18T11:02:35Z, https://forums.virtualbox.org/viewtopic.php?f=2&t=41499,Tommaso Blarzino
16656,"after command init 6, generate core dump and duplicate UUID",Windows,Linux,VirtualBox 5.1.18,2017-04-18T20:12:40Z,2017-04-18T20:12:40Z,"Hello,
unfortunately I answered yes to upgrade on Virtualbox 5.0.12 hang on create new disk, resolved on 5.1.19 and install it.
Virtualbox 5.1.19 corrupted 6 Guest Machine and install 5.1.51-114298

Now it is not present later, he returned to version 5.0.12 that worked well?
I honestly did not know if the problem is in virtualbox core or in the host machine, with win7.

the problems that I see right now are:
- Duplication of Guest UUID that worked and you can not run the start
- see attach: although, on this generated core dump I found something and I just solved will update

Regards, Massimo",maximilian
16546,5.1.16 seamless mini toolbar broken,Linux,Windows,VirtualBox 5.1.16,2017-04-20T13:02:00Z,2017-04-20T13:02:00Z,"Toolbar problems. Toolbar settings fails--on screen, not dismissable, but works otherwise .Minitoolbar does not work in seamless mode (mouseclicks do nothing to menu items). Both toolbar & mini work fine in 5.1.15 r113680 and below.

Reproduce:
1. windowed :start vm, click view menubar, menubar settings. try to dismiss settings bar, no dice.
2. seamless: click menubar item, no response.

",matthewls
16676,I get an error E_FAIL (0x80004005) when saving the state of my machine,Windows,Windows,VirtualBox 5.1.18,2017-04-20T13:47:11Z,2017-04-20T13:47:11Z,"I work on a virtual machine with a lot of things open and I like save the state of my machine instead of turn it off, but a few days ago that I get this error every time and i don't know why it is",rusoLoco22
16681,Virtual core XTEST pointer/keyboard inoperative under X11,Windows,Linux,VirtualBox 5.1.20,2017-04-21T10:08:53Z,2017-04-21T10:08:53Z,"Guest: Arch Linux LTS 4.9.23-1 x64; also happens on Arch Linux 4.10.10-1
Host: Windows 10 Pro x64, Intel Core i7

Started happening after an update to VirtualBox 5.1.20. Downgrading on guest side to 5.1.18 had no effect. Unrelated to window manager, happened using X11 default as wel.

Found a workaround by adding two configuration files to /etc/X11/xorg.conf.d/ first to define keyboard to use evdev drivers and mouse to use libinput drivers.",gingerale
16457,Some menu categories in Linux guest OSes no longer populate,Windows,Linux,VirtualBox 5.1.14,2017-04-21T14:43:31Z,2017-04-21T14:43:31Z,"Beginning with VirtualBox 5.1.14 r112924 and VirtualBox's corresponding Linux guest additions, certain menu categories in Linux Mint 18.1 Cinnamon and Chapeau Linux 24 guest OSes no longer populate. Specifically:

In Linux Mint 18.1 x64 Cinnamon, the following menu categories don't populate (i.e., are empty when selected):

* All Applications
* Accessories
* Administration
* Preferences
* Places

In Chapeau Linux, clicking on the ""All"" subpanel of Gnome 3.2's Activities > Applications panel causes all of the application icons to quickly flash onscreen and then disappear. The ""Frequent"" subpanel populates normally.

In Chapeau Linux with the Application Finder utility installed, the following menu categories in the Applications menu (which replaces the native Activities menu) don't populate:

* Accessories
* Utilities

If Application Finder itself is launched, all categories populate correctly.

Additional background:

* I'm running a Windows 7 x64 host.

* This problem did not occur with previous versions of VirtualBox. It began with the upgrade to VirtualBox 5.1.14 r112924 and installation of VirtualBox's corresponding Linux guest additions.

* This problem still does not occur in Linux Mint 18 ""Sarah"" Cinnamon.

* This problem does not occur with Linux Mint 18.1's own version of guest additions. (Unfortunately, Linux Mint's additions don't seem to support hardware rendering.)

* Because this bug prevents or hinders access to many applications, utilities, and settings via the GUI, I consider it major.",PierrePotame
16687,"2D Acceleration breaks Scaled mode (Windows 7 host, Windows XP guest).",other,other,VirtualBox 5.1.20,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
16690,calculate required temp storage and check available storage before merging snapshots,other,other,VirtualBox 5.1.20,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
16691,UltraNav mice cannot scroll horizontally,Windows,Windows,VirtualBox 5.1.20,2017-04-24T15:05:15Z,2017-04-24T15:05:15Z,"On my Lenovo W530 with UltraNav, horizontal scrolling does not work in Windows or Linux VMs (Win10 Host). Horizontal scrolling does work in every other app, including VBox Manager (within Show Log). Trying the different input device types in VM's settings did not resolve the issue. 

The previous solution of adding a few lines to tp4table.dat used to work (https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/tp01_en/thread-id/37809/page/2 and in fact I'm one of the people reporting there that the solution works), but is no longer the case. As a point of difference between the current and previous issue: scrolling in VBox Manager (within Show Log) used to not work unless the tp4table.dat solution was in place. However in the current issue scrolling does work within Show Log of VBox Manager, but horizontal scrolling does not work in Win7 or Linux Guests.

Furthermore, downgrading from 5.1.20 to version 5.0.38 r114632 did not resolve the issue.

Is there any additional information I can provide to request a fix for this?",R
16233,Vbox bridge loses outer QinQ tag,Linux,Linux,VirtualBox 5.1.10,2017-04-24T16:13:18Z,2017-04-24T16:13:18Z,"Virtualox bridge loses outer QinQ tag if bridged with Linux TAP interface

Steps to reproduce:

 1. Install OS Linux on PC.
 In my case: Ubuntu 14.04.5
 kernel 4.2.0-42-generic X86_64

 2. Install !VirtualBox (in my case ver. 5.1.10 !r112026 (Qt5.6.1)) from [http://download.virtualbox.org/virtualbox/5.1.10/virtualbox-5.1_5.1.10-112026~Ubuntu~trusty_amd64.deb here]

 3. Download and install guest Linux OS.
 In my case Ubuntu 16.04.01 from [http://releases.ubuntu.com/16.04/ubuntu-16.04.1-server-i386.iso here]

 4. On host system create tap interface:
{{{
ip tuntap add dev tap10 mode tap
ip link set dev tap10 up
}}}
 5. In guest VM netwrok settings set network adapter to ""bridge"" mode to interface tap10
{{{
vboxmanage modifyvm TESTVM --nic2 bridged
vboxmanage modifyvm TESTVM --bridgeadapter2 tap10
}}}
	
 All other network settings may be set to default. I tried to change the ""adapter type"" and ""promiscuous mode"". Their change does not change the result. 
	
 6. Create QINQ subinterface on host interface tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link add link tap10 tap10.100 type vlan proto 802.1q id 100
ip link set up tap10.100
ip link add link tap10.100 tap10.100.2000 type vlan proto 802.1q id 2000
ip link set up tap10.100.2000
ip addr add 10.11.12.1/24 dev tap10.100.2000
}}}
	
 7. Start up guest VM and determine which interface bridged with tap10
	In my case this is a '''enp0s8'''
 8. Create QINQ subinterface on VM interface which bridged with tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link set up enp0s8
ip link add link enp0s8 enp0s8.100 type vlan proto 802.1q id 100
ip link set up enp0s8.100
ip link add link enp0s8.100 enp0s8.100.2000 type vlan proto 802.1q id 2000
ip link set up enp0s8.100.2000
ip addr add 10.11.12.2/24 dev enp0s8.100.2000
}}}
 9. start watch for traffic on host PC on tap10 interface:
{{{
tcpdump -i tap10 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i tap10 -vvv -e -w qinqPC.pcap
}}}
	
 10. start watch for traffic in guest VM on ""physical"" interface:
{{{
tcpdump -i enp0s8 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i enp0s8 -vvv -e -w qinqVM.pcap
}}}
	
 11. Try to ping 10.11.12.2 from 10.11.12.1 (Host PC => Guest VM)
{{{
ping 10.11.12.2
}}}
	
 12. You should get the following results:[[BR]]
 on physical PC (tap10):
{{{
21:22:06.345997 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:07.346093 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:08.346032 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
}}}
 on VM (enp0s8):
{{{
21:30:21.737754 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:22.738035 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:23.737981 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
}}}

As seen, on VM side is missing outer vlan (vlan 100)

If a try to ping from VM to PC the outer vlan in right place only in ARP request. In ARP reply (PC -> VM) the outer vlan is missing.
on physical PC:
{{{
21:35:12.342498 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342501 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342521 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
21:35:13.343489 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343495 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343516 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
}}}

on VM:
{{{
21:35:10.614413 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:10.614556 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:11.615368 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:11.615549 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:12.615063 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
}}}


It does not look as a TAP bug. If a try to bridge two tap interface via linux bridge, and create QINQ subinterfaces for each of them, this problem does not appear.

PCAP-s from VM and PC (qinqVM.pcap and qinqPC.pcap) in attachement.

Thanks in advance!",Arc
16685,Booting error (VINF_EM_DBG_HYPER_ASSERTION / raw mode),Linux,Windows,VirtualBox 5.0.32,2017-04-24T16:16:30Z,2017-04-24T16:16:30Z,When booting getting a critical error.  This happens at the start up of the virtual session,Brett
16684,VBoxManage.exe extpack command exhausts StdOut buffer,Windows,other,VirtualBox 5.1.20,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
16692,3D acceleration causes Excel to fail to open with a file,Mac OS X,Windows,VirtualBox 5.1.20,2017-04-25T03:41:59Z,2017-04-25T03:41:59Z,"Double clicking a xlsx file gives the error

{{{
There was a problem sending the command to the program
}}}

under this setting
{{{
VirtualBox
Enable 3D Acceleration
Enable 2D Video Acceleration

Excel
Enable hardware graphic acceleration
}}}

The following settings work fine
{{{
VirtualBox
Enable 3D Acceleration
Enable 2D Video Acceleration

Excel
Disable hardware graphic acceleration
}}}

{{{
VirtualBox
Disable 3D Acceleration
Enable 2D Video Acceleration

Excel
Enable hardware graphic acceleration
}}}

Excel 2016[[BR]]
Guest Windows 10[[BR]]
Host OS X 10.12.4 (16E195)",Keith Yip
16694,Host fails to resume from suspend when virtualbox installed,Linux,other,VirtualBox 5.1.18,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
16695,VBoxNetNAT refuses connections for port-forwarding after one day or two,Linux,all,VirtualBox 5.1.20,2017-04-25T12:17:09Z,2017-04-25T12:17:09Z,"I started using NAT network since several months ago.  My setup is quite simple: Linux host (CentOS 7.3) running two Windows 7 guests.  All guests use NAT network with static IPs.  Port-forwarding is configured on the NAT network.


{{{
NAT network: 10.0.2.1/24
Guest 1 IP: 10.0.2.11
Guest 2 IP: 10.0.2.12
Forward 1: <host_ip>:5911 <--> 10.0.0.11:5900
Forward 2: <host_ip>:5912 <--> 10.0.0.12:5900
}}}


Everything work great, until, after some time, maybe one day or two, connections to host port 2211/2212 got rejected.  One solution I find is to restart guest OS, sometime more than once, until the port-forward is normal again.

During the whole process (good --> bad --> restart --> good again), I can see that port 2211/2212 are always bound by process /usr/lib/virtualbox/VBoxNetNAT, and its pid never changed.

When connections are rejected on port 5911 and 5912, guests can connect to each other's 5900 port, which rules out guests failures.

Another observation is, sometimes the restart of one guest OS can solve problems for all guests.
",Steve Sun
16699,"createHostOnlyNetworkInterface() returning iProgress, iProgress instead of iProgress,IHostNetworkInterface",Windows,all,VirtualBox 5.1.20,2017-04-26T11:16:31Z,2017-04-26T11:16:31Z,"Hello everybody. I'm using Virtualbox 5.1.20 on Windows 10 x64. I'm using the python SDK (version 5.1.20) to bind irtualbox functions via XPCOM. Python version in use is the 2.7 32bit.

PROBLEM:
Function createHostOnlyNetworkInterface() returns iProgress twice instead of returning on iProgress and an IHostNetworkInterface.

Have a look at the attached screenshot, which is pretty eloquent.
",Alberto Geniola
16705,VirtualBox cannot read partititon scheme on a Win10/Bootcamp combination,Mac OS X,Windows,VirtualBox 5.1.20,2017-04-28T12:03:08Z,2017-04-28T12:03:08Z,"This is a bug according to the forum topic ''VBoxManage internalcommands createrawvmdk error: Cannot read the partition info...'' ([https://forums.virtualbox.org/viewtopic.php?f=8&t=82508])[[BR]]
On a fresh Win10 partition installed with Bootcamp, the VirtualBox command {{{sudo VBoxManage internalcommands listpartitions -rawdisk /dev/diskX}}} does not list any partitions.
This was tested on VB 5.1.12 to 5.1.20 and on macOS 10.12.2 to 10.12.4.",quantor
16498,VBoxManage createrawvmdk doesn't work on 2016 MacBook Pro,Mac OS X,Windows,VirtualBox 5.1.14,2017-04-28T12:07:56Z,2017-04-28T12:07:56Z,"I've had success with this tool on my previous laptops, but no luck on this computer. I'm running macOS Sierra 10.12.3. I've tried Virtual Box versions 5.1.14 and 4.3.40, both fail in the same way:
{{{
marcel@marcel $ sudo VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename win10raw.vmdk -partitions 1,4
VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
}}}

I've confirmed it's not a permissions or locking issue:
{{{
marcel@marcel $ dd if=/dev/disk0s1 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.006011 secs (170354 bytes/sec)

marcel@marcel $ dd if=/dev/disk0s4 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.005971 secs (171497 bytes/sec)

marcel@marcel $ dd if=/dev/disk0 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.006038 secs (169587 bytes/sec)
}}}

SIP is disabled:
{{{
marcel@marcel $ csrutil status
System Integrity Protection status: disabled.
}}}

I can even confirm with dtruss that the tool is reading the disk just fine, but seems to fail to parse the partition map.
{{{
open(""/dev/disk0\0"", 0x0, 0x180)		 = 6 0
fcntl(0x6, 0x2, 0x1)		 = 0 0
fstat64(0x6, 0x7FFF5FBFE390, 0x1)		 = 0 0
ioctl(0x6, 0x40086419, 0x7FFF5FBFE530)		 = 0 0
ioctl(0x6, 0x40046418, 0x7FFF5FBFE55C)		 = 0 0
lseek(0x6, 0x0, 0x0)		 = 0 0
read(0x6, ""\0"", 0x200)		 = 512 0
lseek(0x6, 0x200, 0x0)		 = 512 0
read(0x6, ""\0"", 0x200)		 = 512 0
write_nocancel(0x2, ""VBoxManage\0"", 0xA)		 = 10 0
write_nocancel(0x2, "": \0"", 0x2)		 = 2 0
write_nocancel(0x2, ""error: \0"", 0x7)		 = 7 0
write_nocancel(0x2, ""Cannot read the partition information from '/dev/disk0'\0"", 0x37)		 = 55 0
}}}

My partition table is pretty standard:
{{{
marcel@marcel $ diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         2.0 TB     disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            1.9 TB     disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                117.8 GB   disk0s4
}}}

Any suggestions for next steps?",marcel.laverdet
11486,Support passthrought of TRIM commands to raw partitions,Linux,all,VirtualBox 4.2.6,2017-04-29T14:31:38Z,2017-04-29T14:31:38Z,"Since VirtualBox 4.2 it appears that the AHCI virtual controller supports the ATA TRIM command.

However, only the VDI image file backend actually implements it, where it is used to detect unused blocks so that the image file size can be reduced (if using a dynamic image). The rest of backends do not seem to use it for anything.

My request is for the RAW block device backend to send TRIM/DISCARD commands to the backing block device upon receiving a TRIM command from the guest. 

This would enable e.g. Windows guests on raw partitions (via VMDK's partitionedDevice) sending TRIM commands to a backing SSD device, thereby increasing performance and SSD longevity. 

Unlike discard support for VDI images, this should not involve any extra bookkeeping (""discard"" commands can be sent to the raw block device mostly ""as is"", no need to cluster them).",javispedro
16711,Convert TRIM commands to hole-punching over raw flat disk image.,all,all,VirtualBox 5.1.22,2017-04-29T15:39:24Z,2017-04-29T15:39:24Z,"We can create a raw disk via:
VBoxManage internalcommands createrawvmdk -filename rawtest.vmdk -rawdisk /path/to/rawdisk.img

Since VirtualBox 4.2 it appears that the AHCI virtual controller supports the ATA TRIM command. However, only the VDI image file backend actually implements it.

My request is for the RAW disk image backend, when receiving a TRIM command from the guest, then hole-punching the RAW disk image file. This will save disk space of the host system.
",jack lee
16717,VirtualBox 5.1.22 | Bug| macOS | Display and Software,Mac OS X,Windows,VirtualBox 5.1.22,2017-05-02T08:58:16Z,2017-05-02T08:58:16Z,"MacBook Pro 8.2 (late 2011)

OS Host: macOS Sierra
OS Guest: Windows 10 ""Creator Update"", i386/x86

a) Display
Display resolution max.: 1152x768
Display standard resolution: 1400x900

b) Software
Adobe Creative Suite CS2 didn´t work. It couldn´t load the the ""fonts"" and the ""plugins""



If I use ""VirtualBox/Guest additions 5.1.18"", everything works fine.",fischer-ttd
15588,USB device passthrough does not work,Windows,Windows,VirtualBox 5.0.24,2017-05-02T10:34:01Z,2017-05-02T10:34:01Z,"Hello,

Since a couple of months, I'm having trouble passing through USB devices to virtual machine.
My host operating system is Windows 7 x64 Professional with all the updates and I'm running the latest version of VirtualBox (this happens with all the latest version and since I've had the problem reverting doesn't seem to do anything).

In the VirtualBox log I've found this line, which is added twice every time I try to assign a USB device:

{{{
USBPROXY usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

At the very beginning of each log file I also see the following:

{{{
usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

which I've seen in a lot of log files (not related to this problem) on the internet. I'm not really sure if this is an issue o maybe a mis-initialization.

If I re-try assigning the same USB device a second time I see the following message:

{{{
Connessione del dispositivo USB USB Flash Disk [1100] alla macchina virtuale VmXP_Temp non riuscita.

USB device 'USB Flash Disk' with UUID {a416ea81-cffc-4c89-8ce1-80a66a1aedcd} is busy with a previous request. Please try again later.

Codice 'uscita: E_INVALIDARG (0x80070057)
Componente: HostUSBDeviceWrap
Interfaccia: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

which might mean something is ""stuck"" in VirtualBox and this may not be an host issue.

The host logs don't contain anything suspicious and the guest logs too (it doesn't seem I reach a point in which the guest sees anything).

I didn't try with a Linux guest but I'm pretty sure that won't make any difference.

Thanks,
Filippo",filipposironi
16722,Crash on changing optical drive assignment,Windows,Linux,VirtualBox 5.1.22,2017-05-03T11:22:00Z,2017-05-03T11:22:00Z,"Hi,
right from clean install of 5.1.22, when I prepared initial config of Debian64 VM, I went to properties, wanted to delete IDE controller (optical disk) and use opt drive under existing SATA there, it crashed - and always crashes.",peterg91
16724,Usb disconnect causes guest USB driver crash,Mac OS X,Linux,VirtualBox 5.1.22,2017-05-03T18:29:15Z,2017-05-03T18:29:15Z,"When disconnecting a USB device that is passed through to a linux (Ubuntu 14.04 VM), the result is a tainted driver in the VM.  After this, USB devices no longer pass through correctly.  Dmesg trace below:

[63154.986873] usb 2-2: Product: Adafruit Industries
[63155.395258] ohci-pci 0000:00:06.0: frame counter not updating; disabled
[63155.395266] ohci-pci 0000:00:06.0: HC died; cleaning up
[63159.987813] usb 2-2: can't set config #1, error -110
[63159.987878] usb 2-1: USB disconnect, device number 2
[63161.397977] irq 22: nobody cared (try booting with the ""irqpoll"" option)
[63161.397985] CPU: 0 PID: 303 Comm: systemd-udevd Tainted: G           OE  3.19.0-25-generic #26~14.04.1-Ubuntu
[63161.397987] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[63161.397988]  ffff880035c47aa4 ffff88003fc03ce0 ffffffff817aed00 0000000000003a40
[63161.397991]  ffff880035c47a00 ffff88003fc03d10 ffffffff810ce3b6 ffff88003fc03d10
[63161.397992]  ffff880035c47a00 0000000000000016 0000000000000000 ffff88003fc03d60
[63161.397994] Call Trace:
[63161.397996]  <IRQ>  [<ffffffff817aed00>] dump_stack+0x45/0x57
[63161.398010]  [<ffffffff810ce3b6>] __report_bad_irq+0x36/0xd0
[63161.398012]  [<ffffffff810ce8ec>] note_interrupt+0x24c/0x2a0
[63161.398016]  [<ffffffff814c588a>] ? add_interrupt_randomness+0x3a/0x1e0
[63161.398019]  [<ffffffff810cbfde>] handle_irq_event_percpu+0xae/0x1a0
[63161.398020]  [<ffffffff810cc111>] handle_irq_event+0x41/0x70
[63161.398022]  [<ffffffff810ced12>] handle_fasteoi_irq+0x82/0x140
[63161.398025]  [<ffffffff81017682>] handle_irq+0x22/0x40
[63161.398027]  [<ffffffff817b9621>] do_IRQ+0x51/0xf0
[63161.398031]  [<ffffffff817b742d>] common_interrupt+0x6d/0x6d
[63161.398034]  [<ffffffff81078e7f>] ? __do_softirq+0x7f/0x270
[63161.398036]  [<ffffffff81078e20>] ? __do_softirq+0x20/0x270
[63161.398038]  [<ffffffff810792ad>] irq_exit+0x9d/0xb0
[63161.398039]  [<ffffffff817b970a>] smp_apic_timer_interrupt+0x4a/0x60
[63161.398041]  [<ffffffff817b773d>] apic_timer_interrupt+0x6d/0x80
[63161.398042]  <EOI>  [<ffffffff8107354b>] ? copy_process.part.26+0x13db/0x1c00
[63161.398047]  [<ffffffff81073f25>] do_fork+0xd5/0x340
[63161.398052]  [<ffffffff8168be11>] ? sock_alloc_file+0x91/0x120
[63161.398054]  [<ffffffff81074216>] SyS_clone+0x16/0x20
[63161.398056]  [<ffffffff817b69d9>] stub_clone+0x69/0x90
[63161.398057]  [<ffffffff817b668d>] ? system_call_fastpath+0x16/0x1b
[63161.398059] handlers:
[63161.398069] [<ffffffff815a7280>] usb_hcd_irq
[63161.398070] Disabling IRQ #22
[63161.399293] usb 2-2: USB disconnect, device number 4

Removing and re-installing guest addons will allow devices to pass through successfully again, but only until they are disconnected.  Guest reboots do not seem to always allow passthrough again without uninstalling and reinstalling guest addons.  I can provide more logs if necessary.",Vbuntu
16730,About Qt translations.,other,other,VirtualBox 5.1.22,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
16733,Keyboard Layout VirtualBox 5.1 - Ubuntu 16.04 Host - Incorrect keymap,Linux,Linux,VirtualBox 5.1.22,2017-05-05T16:00:58Z,2017-05-05T16:00:58Z,"Hi,

When using VirtualBox 5.1 on Ubuntu 16.04 host, the VirtualBox GUI interface does not use the correct keymap.

All other programs on the Host operate without issues.

I tried on 2 hosts and they both display the same problem.

Only solution I found was reinstall VirtualBox 5.036 that is provided by apt-get.

I also installed VirtualBox 5.1 on Centos 7 and the issue does not happen.

I will update this ticket soon when I trie on a Debian 8.7 host...",leo.rudolph
16734,Keyboard re-captured with no clear reason,Linux,Windows,VirtualBox 5.1.22,2017-05-05T16:56:11Z,2017-05-05T16:56:11Z,"I'm on a laptop with classic brightness and volume control hotkeys, and when the keyboard and mouse integration is active in the guest these hotkeys don't work but that's expected, I'd say (keyboard backlight control always works, though).

So I press the host key, right ctrl, to disable integration, and that kinda works, but only for a brief moment. Meaning:

- I press host key, icon goes from green to black.
- I can wait forever and nothing happens (ok)
- I press volume up or down, volume is changed in the host
- After about 1/2 sec the icon goes back to green and integration is active, hotkeys don't work anymore in the host.

Even more strange is the behaviour with brightness control:

- I press host key, icon goes from green to black.
- I press dimming up or down ONCE, host screen is affected
- I can wait whatever time I want
- I press dimming up or down again, host screen is affected again
- After about 1/2 sec the icon goes back to green and integration is active, hotkeys don't work anymore.

Maybe it has something to do with windows focus because these hotkeys trigger on screen notifications, but the integration is reactivated well before the notification is gone, and for brightness it only happens on the second event, so the first notification does nothing.

I know it's more of an annoyance than an issue, but still...",ctrl
16738,Cannot Switch Virtualization Off,Windows,Linux,VirtualBox 5.1.22,2017-05-08T05:58:12Z,2017-05-08T05:58:12Z,"If a VM has virtualization switched on, but the BIOS of the physical machine has virtualization switched off, it is impossible to switch virtualization off for the VM.  This is because Virtual Box detects the missing virtualization and grays out the ""Acceleration"" tab under the System Settings.  With this tab missing, it is not possible to deselect hardware virtualization.  Further, Virtual Box does not cascade this detection to actually forcing virtualization off for the VM on execution.  This causes the VM to crash as it starts up (because the virtualization is physically not available).  My suggestion is to always allow the acceleration tab to be accessible.  Alternatively, if virtualization is physically not available, just run the VM with the option deselected, even if it is selected under the acceleration tab (in which case, the acceleration tab can remain grayed out if virtualization is off)",Tim Ellis
16742,can connect to virtual usb3 port. can not connect to virtual usb2 port.,Mac OS X,Linux,VirtualBox 5.1.22,2017-05-08T12:08:28Z,2017-05-08T12:08:28Z,"Virtualbox-5.1.23-115260-OSX also, 5.1.18 and 5.1.22

when the usb controller is set to usb3, connected a thumb drive works fine. when set to usb2, it cant connect. the error is in the last line of the included log file.

this ticket seems relevant, https://www.virtualbox.org/ticket/15050",pixelfairy
16714,starting with 5.1.20 the mini toolbar does not appear,Linux,all,VirtualBox 5.1.22,2017-05-08T15:10:25Z,2017-05-08T15:10:25Z,"I run arch linux x86_64 curently kernel is 4.10.11-1-ARCH #1 SMP. If I run  5.1.18 then guests have the mini toolbar showing at the top. If I run 5.1.20 then I lose alsa sound and the mini toolbar does not appear. If I run 5.1.22 then alsa sound is restored, but the mini toolbar is not showing.

In the guest setup user interface I have both show in seamless and appear at top picked.

I use openbox as window manager and slim as login manager.",replabrobin
16744,Unable to open virtual machines after upgrading,Linux,all,VirtualBox 5.1.22,2017-05-08T16:30:44Z,2017-05-08T16:30:44Z,"Host: Linux Mint Sarah
Guests: Multiple (xenial xerus + Windows)


Immediately after upgrading VB, I get the following error on attempting to open any of the machines:

************

RTR3InitEx failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox
Fallo al abrir una sesión para la máquina virtual jvr.

The virtual machine 'jvr' has terminated unexpectedly during startup with exit code 1 (0x1).

Código Resultado: NS_ERROR_FAILURE (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

**************

I'm aware there are some posts on the Internet about it, but the information is not clear to me. Any help would be appreciated!



",kalevala
16746,Explicit clipboard mode,all,all,VirtualBox 5.1.22,2017-05-09T12:16:09Z,2017-05-09T12:16:09Z,"The 4 clipboard modes currently implemented involve hard tradeoffs between usability and security. I propose adding fifth clipboard mode, let's call it Explicit, that would behave like QubesOS clipboard.

In Explicit clipboard mode, no clipboard contents would be shared by default. User could however press a keyboard shortcut to transfer clipboard host->guest or guest->host for the currently focused VM.

Proposed default shortcuts:
- host -> guest: Ctrl+Shift+V
- guest -> host: Ctrl+Shift+C

New workflow:
- host app -> guest app: Ctrl+C, focus VM app, Ctrl+Shift+V, Ctrl+V
- guest app -> host app: Ctrl+C, Ctrl+Shift+C, focus host app, Ctrl+V

This should be easy to implement and yet very valuable for people who routinely use VMs as a secure sandbox.

Note that this is not the only way to streamline clipboard without compromising security. For example, one other option is to tie clipboard transfers to well-known shortcuts, i.e. to perform host->guest transfer before Ctrl+V and guest->host transfer after Ctrl+C. Let's call this other mode Smart or Automatic. It's harder to implement though, because there are more shortcuts to consider and they vary between platforms.",robertvazan
16708,HostAudioNotResponding,Linux,Windows,,2017-05-09T13:56:54Z,2017-05-09T13:56:54Z,"Some AC'97 audio streams (PCM Input, PCM Microphone) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem.

Using the latest test build, Version 5.1.21 r115071 (Qt5.6.1) on Arch Linux.

Audio works, it's ALSA (no PulseAudio), in both the main operating system and Virtualbox.

So why the error?

I've tried using special kernels as I thought it might be a latency issue. No improvement with linux-ck, linux-pf or linux-rt.

Doesn't matter if you use AC 97 or Intel HD Audio drivers.",shillshocked
12813,Mini toolbar activation area is too big,Windows,Windows,VirtualBox 4.3.8,2017-05-09T14:32:48Z,2017-05-09T14:32:48Z,"In fullscreen mode mini toolbar gets activated too early. It hinders when operation with task bar in the bottom of screen.
Older versions of VirtualBox had activation area at the very bottom of screen so it did not interfere with task bar of guest OS.
Hosts: Windows 7, Windows 8.1
Guest: Windows XP",denZXabc
16751,Horizontal scroll for windows guest.,Linux,Windows,VirtualBox 5.1.22,2017-05-11T17:55:34Z,2017-05-11T17:55:34Z,Currently there still isn't any support of horizontal scrolling for guest vm.,amosb
16718,VM keeps keyboard when switching to host,Linux,Windows,VirtualBox 5.1.22,2017-05-15T06:10:43Z,2017-05-15T06:10:43Z,I'm running a Windows 7 VM with guest addons installed in full screen mode on a Linux Mint Serena host. Mouse and keyboard integration are working well but whenever I minimize the VM to work on the host the keyboard keeps captured by the VM. I always have to click somewhere on the host screen to release the keyboard from the VM.,Mellon
16758,winxp,Windows,other,VirtualBox 5.1.22,2017-05-15T10:29:38Z,2017-05-15T10:29:38Z,Problem run VB,keriks
16310,Segmentation fault in VirtualBox,Linux,Linux,VirtualBox 5.1.10,2017-05-15T15:18:55Z,2017-05-15T15:18:55Z,"Hi there! My VirtualBox crash and can not use it!

There are the step to reproduce the step:
1) create a new VM
2) start it
3) when prompted for iso click on the browse icon
HERE IT CRASH!

Can you help me, please?
What can I check?
Which logs do you need?

Thanks,
Marco",marco.fortina
11375,Running Virtualbox causes high CPU usage in Elan Touchpad drivers,Windows,all,VirtualBox 4.2.6,2017-05-16T18:05:57Z,2017-05-16T18:05:57Z,"Seeing high cpu usage on etdctrl.exe on Win 8 64bit host when any VM is started. Process must be killed manually and restarted to regain touchpad features. 

etdctrl.exe is part of the Elan Touchpad driver suite.

Host is on Win 8 64bit, Acer Aspire S7-391. ",tmk
16765,Virtualbox crashes whit device in DFU mode attached to USB,Linux,Linux,VirtualBox 5.1.22,2017-05-17T23:19:19Z,2017-05-17T23:19:19Z,"I work with a device that needs to be rebooted in DFU mode in order to be updated. This device is already connected to the VM with JTAG and UART connections through USB connectors. So far so good, I can see the devices, read data on serial port, list the devices using lsusb, udev rules are properly applied, everything works fine. My problem happens when I reboot the device and remove the jumper that puts the device in DFU mode. As soon as the device boots the VM freezes and goes to an Aborted state. 

I'm using Virtualbox + vagrant but I was also able to reproduce this issue using a pure Virtualbox machine. Issue is also reproducible with older versions of Virtualbox. Host runs on Ubuntu 14.04 and guests are Ubuntu 14.04 and Ubuntu 16.04.

I went through tutorials and forums posts trying to get it to work but I was not able to find a solution and I really need it working as it is a blocker to use virtual machines on my environment. 

Attached are Virtualbox log and core dump.   ",carlosavj
16770,Windows failure to boot after VirtualBox hangs up,Linux,Windows,VirtualBox 4.1.2,2017-05-19T14:00:38Z,2017-05-19T14:00:38Z,"When I connected to ubuntu server via x2go software,
where VirtualBox is usually running 
I have seen that VirtualBox hangs up, and then I kill it.
After this, Windows (guest system) fails to run (it freezez on Please wait when iitializing).",sayfull
16775,Multiple snapshots cause inconsistent parent UUID in vdi causing VER_FILE_NOT_FOUND error,Linux,Windows,VirtualBox 5.1.22,2017-05-21T16:05:59Z,2017-05-21T16:05:59Z,"'''Problem:'''  Snapshotting and deleting of old snapshots in a running VM results in the retention of a reference to a deleted snapshot, inhibiting the resume of saved state.

Setup and process of snapshotting and snapshot removal:

I have a situation where I need to run a long set of analytics in a guest VM.  I constructed a single base VM that installed all the software and base set of data.  I then created 4 linked clones of that base VM.  In each clone, I then configure the specific parameters of an algorithm.  The execution of each set of analysis is approximately 1 month.

To protect myself from unexpected problems that require a complete restart of the analysis, I began to use snapshots twice a day to capture the current state so if the VM crashed for any reason (e.g. power outage or the host becoming frozen), I have a state that I can revert to and resume, losing at most 12 hours of analysis.

After a couple of days, I decided to clean up a few of the older snapshots (using the UI to remove old snapshots in the order of oldest to newest until I had only one snapshot left and the current state for each clone).

I performed the snapshot operation one each of the running clones and I conducted the snapshot removal against the running clones.  In other words, as the VM was running, I began with the oldest snapshot and used the GUI to do the removal (merge and delete).  All worked well.  The VM continued to run and I was able to take another snapshot and then remove the older snapshot.  However, when I decided to do maintenance to the host, the problem emerged.  

I saved the state of each running clone, conducted my host maintenance (basic patching and rebooted the host).  When I went to restart the 4 clones, each reports that there is a missing snapshot.  The snapshot is the immediate parent which is the snapshot just prior to the current snapshot.  Error message below.


{{{
Error:
Could not open the medium '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi' (VERR_FILE_NOT_FOUND).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

}}}

The missing snapshot that it cannot find I believe to be the most recently removed snapshot from the running VM prior to saving the state.

I've attached 2 views from the Virtual Media Manager.  View 1 shows the child of Clone1 which represents the current state (I believe).  It also shows its parent ""missing"".  View 2 is the same but I highlighted the ""missing"" snapshot.

The third attachment is from the VBox Manager showing the snapshots for Clone1.

Doing a showmediuminfo command against the lowest level snapshot (current state), it shows that the Parent UUID as the missing snapshot (which was deleted via the GUI after it merged it with the base).
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage showmediuminfo f1a42411-6f9a-44ae-be07-00ae7de93f89
UUID:           f1a42411-6f9a-44ae-be07-00ae7de93f89
Parent UUID:    fe2f4eca-c178-4a2d-9092-8c82d6bab0b0
State:          created
Type:           normal (differencing)
Auto-Reset:     off
Location:       /home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
Storage format: VDI
Format variant: differencing default
Capacity:       81920 MBytes
Size on disk:   678 MBytes
Encryption:     disabled
In use by VMs:  OT-Strat-Dev Clone1 (UUID: 640b91f3-4748-480a-8d8e-51c576201b5e)
}}}


However, when I use the dumphdinfo, I get a different value for the uuidParent - which is actually the higher (and correct) UUID of the surviving and recent snapshot.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage internalcommands dumphdinfo {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
--- Dumping VD Disk, Images=1
Dumping VD image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" (Backend=VDI)
Dumping VDI image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" mode=r/o uOpenFlags=9 File=0x00563f4bf61680
Header: Version=00010001 Type=4 Flags=0 Size=85899345920
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=81920 cBlocksAllocated=676
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={f1a42411-6f9a-44ae-be07-00ae7de93f89}
Header: uuidModification={eff43f9a-8441-4e7b-9956-17fad78601a5}
Header: uuidParent={3f80396b-40b9-4c17-aa02-8013bf5a3ea6}
Header: uuidParentModification={44e04488-2274-4b00-92ac-1d0c0a02d180}
Image:  fFlags=00020000 offStartBlocks=1048576 offStartData=2097152
Image:  uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

}}}

I haven't found the way to change the uuid that shows up in showmediuminfo to match the uuidParent of the dumphdinfo.  I believe this would resolve my problem and allow me to restore the saved state of my clones.

My snapshot directory also interestingly has multiple saved state files which I assume happens as part of the snapshotting of a running VM since the date and time stamp corresponds to the snapshotting events.  So, these do not look to be cleaned up by the snapshot process.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ ls -l
total 11186860
-rw------- 1 jpb jpb  905360735 May 10 16:03 2017-05-10T21-03-44-944351000Z.sav
-rw------- 1 jpb jpb  872413499 May 20 07:54 2017-05-20T12-53-55-899688000Z.sav
-rw------- 1 jpb jpb  970377870 May 20 17:29 2017-05-20T22-28-49-589899000Z.sav
-rw-r--r-- 1 jpb jpb 7647264768 May 20 07:55 {3f80396b-40b9-4c17-aa02-8013bf5a3ea6}.vdi
-rw------- 1 jpb jpb  352321536 May 17 09:55 {7b0b9120-8a8d-46a1-a82b-fec4448e9b9f}.vdi
-rw------- 1 jpb jpb  710934528 May 20 17:28 {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi

}}}




My current option is to revert to the snapshot, discarding the current state and reprocess the work from the last 12 hours.  I'll save clone1 as is incase you need more information.






",jbrown10
16776,use of USB Audio device in guest trap the host on exiting VM,Windows,other,VirtualBox 5.1.22,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
16627,Create a VM in a non-default directory,Linux,all,VirtualBox 5.1.18,2017-05-23T00:11:22Z,2017-05-23T00:11:22Z,"When creating a VM (using the VirtualBox GUI), it should be possible to override the ''default machine folder''.

This would make it easier to put different VMs in different places.  As it is, one's only recourse is to either change the preference setting first, create the VM, then set it back afterward; or to create the VM where it isn't wanted, and then move it using the remove/move/re-add sequence.  Both of these options are annoying.

Suggested UI: add a ""folder"" button next to ''Name'' input field in the dialog (or the first page of same in guided mode), like the one that already appears next to the virtual-disk ''File Location'' input field.",Eric Siegerman
16076,Ubuntu 16.04.1 VM slow after copying data to external USB drive (irq 20: nobody cared),Mac OS X,Linux,VirtualBox 5.1.6,2017-05-23T09:32:29Z,2017-05-23T09:32:29Z,"When I copy a lot of data to an external Western Digital passport drive (USB3) either using rsync or just drag and drop in a Ubuntu 16.04.1 Desktop VM now and then the desktop slows down to a crawl and stays like this even if I cancel the rsync. The dataset is a lot of 30-40MB files (rsync), or ~8 of 4-5G files (drag and drop). It does not always occur, but when I check dmesg -w I do see ""irq 20: nobody cared"" followed by a call trace. Reboot of the VM fixes this, until it happens again.",John Bokma
16781,Strange handling of encryption keys in case of encrypted media vs. encrypted VM.,Linux,Linux,VirtualBox 5.1.22,2017-05-24T18:11:11Z,2017-05-24T18:11:11Z,"I have created a new medium and encrypted it according the docs[1] WITHOUT attaching it to a VM first. This succeeded and made me wonder where the encryption keys got saved? According to some blog posts and because of tests I made before with encryption on VM level, those should be saved in the XML config of a VM, but in my case I didn't have a VM the media was attached to. I had a look in the global configuration file of the user running the VBoxManage command as well and didn't find any keys.

So where should the keys be saved if only a new medium was created and encrypted, e.g. using VBoxManage, WITHOUT attaching that medium to a VM before encryption?

Afterwards I attached the newly created, encrypted media to some test VM and at some point recognized keys in the XML config of the test VM. Did some testing and stuff and removed the medium from the test VM again to attach it to another VM. But looking at the config of the first test VM, the keys of the re-attached medium is still present there, not in the VM where the medium is currently attached to. Additionally, it is really ONLY attached to the new VM, not the former test VM anymore.

Shouldn't the keys now be part of the one and only VM the medium is attached to? I'm supposed to backup the keys for all media, but how should I do that reliably if I can't be sure where the keys are actually stored? In my case the first VM was for test purposes, the second for production. What happens if I delete the test VM now, still containing the keys of my encrypted medium, even if it's not attached anymore?

I couldn't find any more detailed documentation about where VirtualBox stores the keys when and if/how/when those parts of the config are moved in case of attaching and removing encrypted media from VMs. Looking at how important those keys are, I strongly suggest adding some paragraphs to the docs how to deal with those and what VirtualBox does automatically. Or not at all, because in my case it doesn't seem to move case around as expected...

[1]: https://www.virtualbox.org/manual/ch09.html#diskencryption-encryption",Thorsten Schöning
16783,"held keypress causes ""flickering"" responses in VM",Linux,Windows,VirtualBox 5.1.22,2017-05-24T19:25:59Z,2017-05-24T19:25:59Z,"Through version 5.1.22, press-and-holding a key in a VM produced continuous responses. Now, in Version 5.1.23 r115604 (Qt5.6.1), the response is flickering and functionally broken. Specifically, I press and hold numeric keyboard 5 to temporarily activate the microphone input for Dragon Naturally Speaking dictation. This always worked before to keep the mic on (red mic icon to green); now the mic icon color flickers during and after the key hold, as though the keyboard buffer is overflowing or not being read immediately. This happens in both seamless and window mode guest. Host: Mint KDE 18.1, kernel 4.1.2, AMD FX-9370 8 core CPU, 32GB RAM, microsoft wireless keyboard; Guest: windows 7 64, 5GB VRAM, 4 VCPUs",matthewls
16785,kde plasma 5 activity switching blocked by seamless or fullscreen VM,Linux,Windows,VirtualBox 5.1.22,2017-05-24T20:06:00Z,2017-05-24T20:06:00Z,"Seamless and full screen sessions assigned to one activity prevents switching away from that activity. Activity switching works normally if the VM is windowed or minimized, whether or not the VM is assigned to one or all activities. 

Switching is normal in all modes if VM is assigned to all  activities, and virtual window assignment and switching work fine.
Version 5.1.23 r115730 (Qt5.6.1)",matthewls
16787,"Clipboard actions interference [Host:Debian 9 Stretch RC03][Guests: Win7Ultimate, Debian 8.8 Jessie]",Linux,all,VirtualBox 5.1.22,2017-05-26T06:21:04Z,2017-05-26T06:21:04Z,"VirtualBox Graphical User Interface
VirtualBox version 5.1.22 r115126 (Qt5.7.1)

Prerequisites:

(P0) HOST: NVIDIA, Wacom drivers, 3 monitors total, Xorg under xfce4, Clipman for clipboard monitoring (Debian 9 Stretch RC03)
(P1) Each guest has installed the corresponding ""Guest Additions"";
(P2) Each guest has bidirectional clipboard sharing enabled;
(P3) Windows 7 Ultimate guest has the ""seamless mode"" enabled (thanks guys, this is awesome)
(P4) After launching Win 7 Ultimate guest, xfce4-screenshooter can no longer catch screenshots and move it to clipboard; the copy-paste operations are still nominal;
(P5) With both Win 7 Ultimate and Debian 8.8 Jessie guests clipboard operations within the HOST (within the guests this phenomena has not been confirmed) are being interfered the following way:

(01) Any and every mouse/Wacom Pen selection renders as copying to clipboard, before even the Ctrl+C is pressed; that means any selection automatically puts the selected text into the Host's clipboard, from within any and every application of the Host (Chrome, Chromium, Opera, Libre Office Calc, Libre Office Writer, Notes, Thunar, Terminal, and whatnot)

(02) After reboot both xfce4-screenshooter and clipboard operations work fine PRIOR to launching the VirtualBox

",al64128
16784,Encrypting an unregistered disk from command line while no VBoxSVC.exe running may cause data loss,all,all,,2017-05-26T18:23:14Z,2017-05-26T18:23:14Z,"If the command ""VBoxManage encryptmedium"" is run on an unregistered disk file while no Virtualbox window is open, data loss may result:

1. Release a good disk from a test guest (make a copy for a backup). Unregister the disk from the Media Manager so it does not show in the list. Close all Virtualbox windows. Ensure that the VboxSVC.exe process has closed.

2. Run the command line on the good disk file.

3. The running of the command will launch a new VBoxSVC.exe to support the command. When the command completes, the associated VBoxSVC.exe will close in a few seconds. If you can get the main Virtualbox window open before the VBoxSVC.exe from the command line closes, the main Virtualbox Window will know about the newly-encrypted disk and use it properly.

4. If you cannot get the main Virtualbox window open before the command's associated VboxSVC.exe closes, then the main Virtualbox windows will not know the disk was encrypted. The DEK for that disk will be lost, and the disk's internal data is scrambled and unusable.",scottgus1bug
16792,Internal network no connectiion between VM's on Windows10 host,Windows,Windows,VirtualBox 5.1.22,2017-05-27T19:14:33Z,2017-05-27T19:14:33Z,"I'made 2 VM's both with an WS2012R2.
Connect the network both on Intern netwerk with the name intnet
Switched from both the firewall off.

Adresses

SERVER A
IP adress 10.0.0.10
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

SERVER B
IP adress 10.0.0.12
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

Can ping the machine itself correctly

Problem is 
On the command line prompt using the ping command it gives unreachble 4 time's on both sides.",Fanatic11
15975,VBoxManage always shows host only interfaces as disabled,Windows,Linux,VirtualBox 5.1.6,2017-05-29T14:22:50Z,2017-05-29T14:22:50Z,"VBoxManage list --long hostonlyifs

always shows DHCP disabled, even for an enabled, and functioning NIC.",silvermangb
16793,Guest machine freeze when network is active,Windows,Windows,VirtualBox 5.1.22,2017-05-29T19:26:12Z,2017-05-29T19:26:12Z,"I have a version of VirtualBox 4.3.38 installed on my Debian, runs, and I keep this version !
Why ?
I installed a version 5.3.1 on a Windows Seven machine, version strongly discouraged!
I will join the logs because the guest machine freeze!
Especially when I add the network card from menu Configuration-> NAT network or bridge,
then systematically blocks the FREEZE guest machine!
I keep version 4.3.38.
I join the log!
I have AVG and spyHunter installed on the Windows machine.
I TRY DISABLED SERVICE SPYHUNTER AND AVG THEN FREEZE ALWAYS

J'ai une version de VirtualBox 4.3.38 installé sur ma Debian , fonctionne , et je garde cette version
pourquoi ?
J'ai installé sur une machine Windows Seven la version 5.3.1 , version vivement déconseiller !
Je vous joint les logs car la machine guest freeze !
Surtout quand je rajoute la carte réseau depuis menu Configuration->Reseau NAT ou pont à pount, 
ca freeze  systématiquement , la machine guest FREEZE !
Je garde la version 4.3.38.
Je joint les log !
Product not tested.",Sizy458
16429,Hard lockup of Linux guests on Mac Host,other,Linux,VirtualBox 5.1.14,2017-05-30T23:50:35Z,2017-05-30T23:50:35Z,"I am running an Ubuntu 16.04 guest on a MacOS Sierra host.  In my guest I am running a Yocto project build (https://yoctoproject.org/).  This is a fairly substantial workload and eventually the target apparently locks up.  I've try to get kernel logs out of dmesg, /var/log/syslog and the VT1 console but when the system is hung, there is nothing printed to any of those locations indicating any trouble.

I have seen this happen also on Ubuntu 14 and CentOS 7 targets.

It is reproducible 100% of the time with the Yocto project build.  When it is hung, the GUI is still displayed but nothing updates, not even the clock app.

I tested with both VirtualBox 5.1.14 and 5.0.32 and could reproduce the issue with both versions.  I'm testing now with the 5.1.15 nightly build",drewmoseley
16804,Kernel panic on Arch Linux guest,Linux,Linux,VirtualBox 5.1.22,2017-06-01T09:34:49Z,2017-06-01T09:34:49Z,Arch Linux kernel is producing a kernel panic. A screenshot and the log is provided.,Panos Kavalagios
16750,VirtualBox GUI Crashed when cloning after upgrading to latest version,Linux,Windows,VirtualBox 5.1.22,2017-06-02T14:21:45Z,2017-06-02T14:21:45Z,"We upgrade the servers to CentOS Linux 6.9 2.6.32-696.1.1.el6.x86_64 with VirtualBox 5.1.22_115126_el6-1

Now when we try to clone a machine it crashes the GUI.  All machines show ""aborted"" though they are running fine and each states the VirtualBox Critical Error.  I'm attaching the error here.",Tomqwe
16807,Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).,Windows,Linux,VirtualBox 5.1.22,2017-06-02T21:07:58Z,2017-06-02T21:07:58Z,"1) Context
Virtual Version : v5.1.22
Host : Windows 10
Guest : Debian v8.7

2) Problem description : 
An error message appears when starting my Guest.

3) Error Message :
Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).
Code d'erreur : 
E_FAIL (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

4) Usefull infos :
I suspect that the problem was appeared when I have updated VirtualBox from v5.1.10 to v5.1.22
The host only network adapter was #2 and now as you can see in screen shots
this is the #3. So I suspect there a ""binding"" problem between #2 (old version of VBox) and #3 (new version of Vbox)
Is there new network devices between v5.1.10 and v5.1.22 ?
Is the default network device for my Host was changed ?

Best Regards",ManWithNoName
16812,VINF_EM_TRIPLE_FAULT (Win 10 guest on Linux Mint 18.1),Linux,Windows,VirtualBox 5.1.22,2017-06-05T01:05:17Z,2017-06-05T01:05:17Z,"After the guest Windows OS performed software updates, VirtualBox logged a VINF_EM_TRIPLE_FAULT error.   ",chonak
16719,Virtualization not working without VT-x in the newer versions (5),Linux,Windows,VirtualBox 5.1.22,2017-06-05T08:14:25Z,2017-06-05T08:14:25Z,"After upgrading VBox from 4.3 to 5.1.20 (the latest version), my Windows VM has failed to start, along with VBox showing the following error message:

''Invalid parameter. (VERR_INVALID_PARAMETER)''[[BR]]
Result Code: NS_ERROR_FAILURE (0x80004005)[[BR]]
Component: ConsoleWrap[[BR]]
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This issue is specific to the version 5 of VBox, because this error didn't occur at all before the upgrade.

This is the log prior to the upgrade can be found [https://forums.virtualbox.org/download/file.php?id=25276&sid=e07968bd0f4d95599392179d071b8104 here].
The log resulted after the upgrade can be found [https://forums.virtualbox.org/download/file.php?id=25274&sid=e07968bd0f4d95599392179d071b8104 here].

This issue affects many users, and needs some action.",kaisbe
16811,VBox 5.1.12.12440 immediately crashes - Win10 x64 Home,Windows,Linux,VirtualBox 5.1.12,2017-06-05T14:25:59Z,2017-06-05T14:25:59Z,"I cannot run VirtualBox 5.1.12.12440 x64. It crashes immediately when launced. I can't confirm, but I suspect the recent Windows 10 Creators update maybe did something to harm VBox, only becuase VBox worked fine until that Windows update was applied to my computer.

I've attached a crash dump of the most recent launch. I've also attached the most recent logs.",Malchore
16805,darwin kernel crash on starting VM,Mac OS X,Windows,VirtualBox 5.1.22,2017-06-05T17:29:50Z,2017-06-05T17:29:50Z,"I've got 3 crashes in sequence each time when running Windows VM, either from scratch or saved state.

One of the crash report reads this error:
{{{
panic(cpu 5 caller 0xffffff8003809f4a): ""vmx_on: unexpected return -2 from __vmxon()""@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/i386/vmx/vmx_cpu.c:198
}}}
Another two have:
{{{
panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode, registers:
panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode, registers:
}}}
It happens in 5.1.22 as well as before the upgrade.

Please find crash report details in the attachment.",bronek
16816,8042/BIOS16 keyboard issues,Windows,other,VirtualBox 5.0.12,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
16817,Debugging high CPU usage macOS,Mac OS X,Linux,VirtualBox 5.1.22,2017-06-06T20:13:09Z,2017-06-06T20:13:09Z,"I'm using docksal to run a virtual box on macOS 10.12.4. When I view the activity monitor VBoxheadless is consumming 120-140% CPU. I've tried toggling a few things in the settings, but I'm out of my depth in terms of actually debugging the issue.",Claytron
16820,Critical error on Windows 7 guest,Linux,Windows,VirtualBox 5.1.22,2017-06-08T11:10:42Z,2017-06-08T11:10:42Z,A critical error has occurred to win7 VM. Information attached.,Panos Kavalagios
16821,Virtual Box won't load existing or new VMs,Windows,all,VirtualBox 5.1.22,2017-06-08T14:00:52Z,2017-06-08T14:00:52Z,"Hi,

For the last week I've been having an issue where Virtualbox is refusing to load VMs and gives an error whilst creating the process.

It was working perfectly fine and suddenly this problem has started appearing.

Please check attached documents.

I'm running a W7x64 Host.",jdoe3618
16822,Default Machine Folder link removed,Windows,all,VirtualBox 5.1.22,2017-06-08T16:40:50Z,2017-06-08T16:40:50Z,"hello


I encountered an unexpected behavior during VM creation/removal through the VirtualBox Manager GUI - done some testing and found the manager sometimes remove the Default Machine Folder configured in File / Preferences / General

''1st case'' - there is no existing VM in the GUI - create a new VM then abort during creation (I usually abort at the memory setting) => the VM folder is gone as is the Default Machine Folder - it's ok, cleaning is always a good idea as there is no existing or created VM in the folder, but I think this is linked with my problem below : the 2nd case

''2nd case'' - the Default Machine Folder is a junction (folder hard link in Windows world) - in that case, even if there is other existing and possibly running VM, removing one VM results in the removed VM folder removal (expected) and Default Machine Folder link removal (unexpected) - no harm as only the link is removed, the true folder and all VM folders inside are still there, its only annoying as I need to recreate the link each time a VM is removed or VM creation is aborted


'''how to reproduce the problem'''[[BR]]
1) create a junction : in command line ""mklink /j C:\Users\(your-username)\Documents\VM D:\{test-folder}""[[BR]]
2) set the Default Machine Folder to C:\Users\(your-username)\Documents\VM[[BR]]
3) create VM test-1[[BR]]
4) check C:\Users\(your-username)\Documents\VM\test-1 exists as well as D:\{test-folder}\test-1[[BR]]
5) start creating VM test-2[[BR]]
6) abort test-2 VM creation => C:\Users\(your-username)\Documents\VM link should be gone


my current configuration involve iSCSI disks mounted as folders, reason for the links - hope I made the reproduce steps as simple and straight as possible

feel free to ask if you need more tests or information


regards[[BR]]
Bruno",!bruno
16813,/dev/tty: No such device or address,Linux,all,VirtualBox 5.1.22,2017-06-11T18:32:49Z,2017-06-11T18:32:49Z,"I've got an error message thrown by VBox->Preferences->Extensions, whenever trying to upgrade the VBox Extension Package:

'''""The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.""'''

This seems little bit weird since `/dev/tty` is part of the system:

{{{
ls /dev/tty
/dev/tty
}}}

I need some help regarding this issue.",kaisbe
16754,VM config lost after saving state,Mac OS X,Linux,VirtualBox 5.1.22,2017-06-12T23:32:35Z,2017-06-12T23:32:35Z,"I've had this issue happen several times recently. I click to save the state of a VM. It saves the state completely and the window closes. I then close out of VirtualBox (UI). 

The next time I open the Vbox UI, the VM looks normal. However, when I attempt to start the VM, I'm greeted with ""Fatal: no boot media"". It seems that the *.vbox file may have been saved incorrectly as a result of the previous shutdown. What I see in the UI is that the entire Storage area is blank (it's lost all of the hard drives, CD, etc). It also has reset the memory and possibly other settings. It's almost like it's overwritten the *.vbox file with a generic template. Or, perhaps a generic template is created because the original *.vbox file has gone missing... not sure which?

I have encountered this bug at least 3 times since 5.1.18. I am still seeing it in the latest version (5.1.22). So, whatever is causing this issue is not fixed. Two of the times, I could easily recreate the VMs. However in this latest one, I need to recover some information for reference.

As an FYI, the *.vdi hard drive files exist. In the snapshot director, I see the *.sav file and the various snapshot files. Unfortunately, trying to hand recreate the working *.vbox file for this VM the way that it was is probably next to impossible.

Note that this VM began its life as a linked clone from another VM. I have not modified the original from which it was cloned, so it shouldn't be related to that. However, for each of these I have encountered, they have all been from linked clones making recreating the *.vbox file more complicated.

It would be great if there were a repair tool included to scan the VM's directory and attempt to repair or recreate the *.vbox file using the files it can find. If such a tool already exists, please let me know. If there's an easy way to recreate this *.vbox file, that would be helpful.

As an FYI, I've also looked at the 'backup' *.vbox file and it also appears to be a generic template. So, I can't even recover from that.",commorancy0
16809,PCI MMIO Address Not Listed In Memory Map,all,Linux,VirtualBox 5.1.22,2017-06-13T08:01:10Z,2017-06-13T08:01:10Z,"When using the ICH9 chipset, the ""MCFG"" table is added to the ACPI table list, and it has an address of 0xDC000000.  However, this address is not included in the memory map returned by INT 15h AX=E820h.  This causes Linux to ignore the MMIO PCI area, altogether, and it may cause issues if the OS tries to use this area when reassigning addresses to PCI devices.

Please add the PCI MMIO area, and any other chipset specific memory areas to the memory map returned by E820.

Thanks.",SpyderTL
16789,VM dropped from network because of DHCP problems,Windows,Windows,VirtualBox 5.1.22,2017-06-13T15:41:09Z,2017-06-13T15:41:09Z,"I have a VM in the NAT mode. It happened only once last month, but suddenly guest network lost its internet connection. So the card and network was here, but it has this standard 169 IP address and because of this no access to internet. Only the shutdown and start of the guest helped here. As one can see from the log, it looks like VM suddenly got some problems with DHCP in my local network, where my router is a DHCP server, and lost his 10.x.x.x address. Therefore, it got an 169.x.x.x address. Both guest and host are latest Windows 10.",boxer01
16828,Unknown USB device detected,Windows,Linux,VirtualBox 5.1.20,2017-06-14T16:14:45Z,2017-06-14T16:14:45Z,"There is a line in my VBoxSVC.log that says:
00:00:00.546001          USB: Unknown USB device detected (idVendor: 0x8087, idProduct: 0x07da). Please, report the idVendor and idProduct to virtualbox.org.

So, I am reporting it.",RayH
12564,Unable to drag/drop ISO on cd icon on status bar,Windows,other,VirtualBox 4.3.6,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
16842,Remember last view in VM settings,Windows,all,VirtualBox 5.1.22,2017-06-18T16:51:44Z,2017-06-18T16:51:44Z,"I currently try different live ISO images. To change the image, in the VM settings I have to select the page ""mass storage"" and the port every time. It would be very nice to have the settings dialog open with the same view as it was when the settings were saved (in this case page ""mass storage"" and the optical drive port).

Of course, other times the requirements could be different, so for different pages the opened tab (for example, page ""network"", tab ""adapter 2"") should also be saved.",bm1n
16845,3D stopped working in Ubuntu 16.04 with NVIDIA  nouveau 1.0.0,Linux,all,VirtualBox 5.1.22,2017-06-19T02:44:08Z,2017-06-19T02:44:08Z,"After updating the OS (possibly including vbox), all my VMs now won't start any longer.
   Ubuntu 16.04, kernel 4.4.0-79-generic

   Virtualbox Version 5.1.22 r115126 (Qt5.5.1)

   NVIDIA graphics card; I think using nouveu driver (please see Xorg.0.log, attached)

If I disable 3D in each VM (and discard saved state!) then they start OK.

Don't know if this was caused by a change in VirtualBox or the OS or driver...

Here is the error pop-up I get when trying to start a previously-working VM: 

""This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""



",Jim Avera
16847,Incomplete DMG support,Mac OS X,OSX Server,VirtualBox 5.1.22,2017-06-19T08:56:04Z,2017-06-19T08:56:04Z,"Some DMG cannot be mounted in a VM with a ""`VERR_VD_DMG_INVALID_HEADER`"" error. Example [https://dl.bintray.com/xquartz/downloads/XQuartz-2.7.11.dmg XQuartz-2.7.11.dmg], but there are actually the majority. The validity of each of the DMGs has been verified. Full error message:

> ''Could not open the medium '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""'''. [[br]] [[br]]
> VD: error VERR_VD_DMG_INVALID_HEADER opening image file '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""''' (VERR_VD_DMG_INVALID_HEADER)''

[[br]]
Other examples include:
* Any DMG created from the Disk Utility will not mount. I believe I've tried all possible combinations, but they all fail with the above error message.
* [http://adcdownload.apple.com/Developer_Tools/Xcode_7.3.1/Xcode_7.3.1.dmg Xcode 7.3.1], that's actually the weirdest. The VM (OSX) shows a ""`The disk you inserted was not readable by this computer. Ignore | Eject`"". If you copy the same exactly DMG in the VM, it is mounted and works as expected.
",Socratis
16574,Win7 Pro lockup using WDDM and Aeroglass Decorations,Linux,Windows,VirtualBox 5.1.18,2017-06-19T09:50:09Z,2017-06-19T09:50:09Z,"All,

  I have openSuSE x86_64 host and Win7 32-bit guest. I experience regular lockups (guest and host) when using WDDM and Aero on Win7. The strange part is when the Win7 crashes or locks up, it will also lock the host desktop (kde3, i3 or fluxbox). I know that WDDM is experimental, but given then number of ""Hey, I'm using it and it works great"" howtos and tutorials, I would expect it to be a bit more reliable than I am seeing.

  I have the virtualbox.org rpms and extension packs installed, along with the guest additions, e.g.:

Oracle_VM_VirtualBox_Extension_Pack-5.1.18.vbox-extpack
VirtualBox-5.1-5.1.18_114002_openSUSE132-1.x86_64.rpm
VBoxGuestAdditions_5.1.18.iso

  I am running the guest on hp_8670W laptop, i7, quad core, hardware virtualization, 8G of ram. Guest is allocated 1 CPU, 2560M Ram, 256M Ram to display with 3D and 2D video acceleration checked.

  The lockups are semi random. Enabling Aero works fine. The desktop looks great, but anywhere from 30 seconds to 5 minutes later, all CPU/Network/etc. indicators in the status bar go red and the guest is locked. The mouse and keyboard are also trapped in the guest and the host desktop is locked (well, left without any input devices) as well.

  When I reinstall the guest additions, removing WDDM, and drop back to the basic Win7 Pro desktop, all is fine. I can run all day/night without issue. (64M Ram for display, 2D acceleration, no 3D.)

  I'm not sure where the bug is, but I would sure like to help get it fixed.",drankinatty
16660,VM window freezes and process keeps running after manual savestate,Linux,Linux,VirtualBox 5.1.18,2017-06-19T17:19:42Z,2017-06-19T17:19:42Z,"There are several vms on this host, usually running in full screen mode. One vm has been experiencing this issue where the full screen vm window freezes, usually after the vm has been running for one or more days. I haven't noticed that issue with other vms, however, most other vms don't run for weeks.

When it happens, the vm window is not updated anymore. It doesn't show the vm anymore. Instead, it shows whatever was there on the screen earlier. If there was another window above the frozen window and that other window is closed, it's still shown in the frozen vm window. If I switch workspaces back and forth, when I switch back to the workspace with the frozen vm window, the vm window (which is in full screen mode) shows the previous workspace.
For that reason, a screenshot wouldn't be helpful, as it would simply show whatever else was on the screen before the frozen vm window was activated.

This affects the vm window, i.e., the window that shows up when you start a vm in the VirtualBox gui. The affected vm itself is still running and can be accessed via ssh.

It is possible to suspend the vm using ""vboxmanage controlvm [NAME] savestate"", but the frozen vm window won't go away. It visually looks as if nothing had changed.
The vm process keeps running after the vm is suspended:
{{{
user     985 27147 64 00:02 ?        08:10:26 /usr/lib/virtualbox/VirtualBox --comment Fedora-1 --startvm 5c908c7b-bf32-4965-be4d-a11f5abdbf04 --no-startvm-errormsgbox
user    7016     1  0 Apr04 ?        00:38:56 /usr/lib/virtualbox/VBoxXPCOMIPCD
user   27123     1  0 Apr10 ?        00:22:27 /usr/lib/virtualbox/VirtualBox
user   27147     1  0 Apr10 ?        00:47:51 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

If this process (985 in this example) is killed, the frozen window disappears and VirtualBox marks the vm as ""Aborted"". The saved state is lost.
I usually reset the vm to its last healthy state and start it again, which works fine every time. Until the vm window freezes again a few days later.

It's not clear what causes these freezes. I understand that this makes it very difficult to debug this, but I'm hoping this bug report helps someone else out there who is experiencing the same behavior.

Looking at the log (attached), it seems like two log entries are missing. These entries can be found at the end of the log files of other vms that were also suspended (without freeze):
{{{
12:07:58.276482 GUI: UIMediumEnumerator: Medium-enumeration finished!
12:07:58.551772 GUI: Passing request to close Runtime UI from machine-logic to UI session.
}}}




",Philip Seeger
14411,mini-toolbar is missing when guest VM is set to full screen.,Linux,Windows,VirtualBox 5.0.0,2017-06-20T00:54:09Z,2017-06-20T00:54:09Z,"Both the mini-tool bar and bottom bar are unavailable when the guest VM is set to full screen. I have tested on both Ubuntu 15.04 and a Windows 7 64-bit professional guests.

I tried resinstalling the guest additions and rebooting but this did not fix the issue. I have also tried removing the option for 3d acceleration from both guests and rebooting but the same problem persists. Virtualbox extensions are also installed.

Host details:

Linux computer1 4.1.4-1-ARCH #1 SMP PREEMPT Mon Aug 3 21:30:37 UTC 2015 x86_64 GNU/Linux
GNOME Shell 3.16.3
Virtualbox version 5.0.0_OSE r101573

Cycling into and out of fullscreen using Ctrl+F does not restore the mini-toolbar. It is important to note that the mini-tool bar does appear in seemless mode.

Ctrl+home key brings up an alternate mini-toolbar menu which is a workaround until this bug is fixed.

There have been others who reported similar issues with the mini-toolbar ranging back 10 months to 3 years ago but no fix was provided. 

Reference:

https://www.virtualbox.org/ticket/9775
https://www.virtualbox.org/ticket/10599
",Nelson Pereira
16832,When running any machine in VirtualBox 5.1.22 Windows bluescreens,Windows,all,VirtualBox 5.1.22,2017-06-20T08:54:26Z,2017-06-20T08:54:26Z,When I try and run a machine on VirtualBox Windows bluescreens and shuts down. I'm running Windows 10 Enterprise version 1703 build 15063.413.,Allan Kjær
16849,"virtualbox gust os crashes and disapear when host os ""Display driver stopped responding and has recovered"" error in ...",Windows,Windows,VirtualBox 5.1.22,2017-06-20T16:22:39Z,2017-06-20T16:22:39Z,"virtualbox gust os crashes and disapear
when host os ""Display driver stopped responding and has recovered"" error in ...

When the guest os crash occurs:
Power saving function, when the host OS returns from display off.
",0o0o
16835,rtlogFlush: Potential null pointer dereference,Linux,all,VirtualBox 5.1.22,2017-06-21T12:12:33Z,2017-06-21T12:12:33Z,"Function rtlogFlush() in vboxguest/common/log/log.c performs a paronoid check:
{{{
    /*
     * If the ring buffer is active, the other destinations are only written
     * to when the ring buffer is flushed by RTLogFlush().
     */
    if (   (pLogger->fDestFlags & RTLOGDEST_RINGBUF)
        && pLogger->pInt
        && pLogger->pInt->pszRingBuf /* paraoia */)
    {
        rtLogRingBufWrite(pLogger->pInt, pLogger->achScratch, pLogger->offScratch);
        pLogger->offScratch = 0; /* empty the buffer. */
    }
    else ... 
}}}   
This implies that pLogger->pInt could be NULL (even if this is an unlikely paranoid case). In the else path we have the following code that dereferences pLogginer->pInt and hence we may have a NULL pointer deference:
{{{
        if (pLogger->pInt->pfnFlush)
            pLogger->pInt->pfnFlush(pLogger);
}}}
I guess this is unlikely, but I think it would be good to correctly sanity check this for this corner case.",ColinIanKing
16852,USB Barcode Scanner not working properly under Windows Virtualbox,Linux,Windows,VirtualBox 5.0.20,2017-06-22T06:31:25Z,2017-06-22T06:31:25Z,"'''Environment:''' Using a Linux host with Virtualbox 5.0.20 and a Windows 7 Prof. guest. [[BR]]

USB 3.0 XHCI activated. [[BR]] [[BR]]


There is a USB Barcode Scanner (Datalogic Powerscan) connected
and installed.
For some reasons, the scanner is not working proberly. 
It works correct for 5-10 times of scanning
and then it drops a couple of characters out for the next scan.
It correctly scans into Linux - without any error.

''It must be a reason of the Virtualbox USB Handling.''

'''If i open wireshark with USBPcap installed and start to sniff the USB ports the problem is solved, as long as the Wireshark is running.'''
See attached File for more information of scans.

There are already 2 Tickets of this problem, years ago but without any solution

[https://www.virtualbox.org/ticket/11671 Ticket 11671][[BR]]

[https://www.virtualbox.org/ticket/11772 Ticket 11772]


",itsbasti
16851,Win 7 x64 Guest on Ubuntu 16.04 Host Freeze after ~4 Hours,Linux,Windows,VirtualBox 5.1.22,2017-06-22T08:50:14Z,2017-06-22T08:50:14Z,"Have had a persistent problem for some time now (unsure when it started) whereby my Windows 7 x64 guest will completely lock up and is unresponsive.  VirtualBox console and other running non-Windows VMs do not seem to be affected.  The VirtualBox interface is still active and I can manipulate settings via the menu options in the GUI, but the guest OS GUI is frozen at the point it stopped working.

Saving State, then Restoring doesn't affect the outcome - only way to recover is to power off the guest VM and start it up again.

Reported this issue over in the forum (https://forums.virtualbox.org/viewtopic.php?f=7&t=82819) and was advised that this may be a rarely reproducible issue involving the NAT network subsystem and that logging a bugtrac ticket would be the best way to address this issue.

This appears to be the point at which the guest crashes (from Vbox.log):

{{{
00:26:21.080234 NAT: resolv.conf: nameserver 192.168.56.50
00:26:21.080254 NAT: resolv.conf: nameserver 127.0.1.1
00:26:21.080262 NAT: Adding domain name laptop
00:26:21.080264 NAT: DNS#0: 192.168.56.50
00:26:21.080266 NAT: DNS#1: 127.0.1.1
00:26:21.080269 NAT: DHCP offered IP address 10.0.2.15
00:26:22.688094 NAT: dnsproxy: timeout: req 00007f56d4071640 dnsgen 2 != 3 on socket 50 (udp) exp. in -427 state=SS_ISFCONNECTED f_(addr:port)=10.0.2.3:53 l_(addr:port)=10.0.2.15:50425 name=0.0.0.0:54045
03:01:30.079058 NAT: Can't allocate mbuf
03:01:38.957814 NAT: Link up
03:01:44.952776 NAT: Link up
03:01:50.966947 NAT: Link up
03:01:56.962828 NAT: Link up
03:02:02.966836 NAT: Link up
03:02:23.001524 NAT: Link up
03:02:29.001906 NAT: Link up
03:02:32.603387 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}


Full vbox.log file attached.
Core dump is available, but may contain sensitive data so I'd prefer not to attach to this ticket.  Have an email out to Frank Mehnert, but would gladly take instruction from elsewhere on how to get this to interested parties, securely.",John Mackoy
16833,Installation of 5.x Prevents Host Machine Networking,Windows,other,VirtualBox 5.1.22,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
16529,Linux guest additions update creates spurious initramfs copies,Windows,Linux,VirtualBox 5.1.14,2017-06-25T15:13:43Z,2017-06-25T15:13:43Z,"With a Win7-X64 host and a CentOS7 guest, I've been seeing a problem for several months where everytime I tried to update the Guest Additions, more than a dozen old initramfs versions would get created, overflowing /boot. The Guest Additions update would only complete after I removed the earliest initramfs versions to make more room. Note that there are not old kernel versions on this system; only the 2 most recent kernels and a recovery are present.

After several attempts, I finally tracked this down to multiple old guest additions subdirectories under /opt. These were empty; apparently the old additions had been properly removed but the empty directories had been left around and this was confusing the guest additions update process. Removing these empty directories cured the problem.",JMHOGM
15090,"Linux host running ""perf top"" kills Virtualbox vm's (VERR_PGM_INVALID_CR3_ADDR)",Linux,all,VirtualBox 5.0.14,2017-06-26T07:20:41Z,2017-06-26T07:20:41Z,"If I run Linux tool ""perf top"" on host and Virtualbox VM at the same time, VM crashes. It doesn't matter which is started first.

Host versions tested:
 * Linux 4.3.3-3-ARCH #1 SMP PREEMPT x86_64
 * perf version 4.4.gafd2ff
 * !VirtualBox 5.0.14_OSE !r105127

Guest versions tested:
 * Linux 4.4.0-4-ARCH #1 SMP PREEMPT x86_64
 * Linux 2.6.18-164el5PAE #1 SMP i686
 * Windows10 64-bit modern.ie without guest additions

Host dmesg:
{{{
[  313.192046] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[  371.880286] SUPR0GipMap: fGetGipCpu=0x3
[  372.327223] vboxdrv: ffffffffa08b4020 VMMR0.r0
[  372.522422] vboxdrv: ffffffffa09af020 VBoxDDR0.r0
[  372.529397] vboxdrv: ffffffffa00c6020 VBoxDD2R0.r0
[  372.617800] VBoxNetFlt: attached to 'eth0' / 74:d0:2b:95:1b:92
[  372.624009] device eth0 entered promiscuous mode
[  374.602722] HPET: Using timer above configured range: 2
[  374.603501] HPET: Using timer above configured range: 2
[  374.603507] HPET: Using timer above configured range: 2
[  374.603511] HPET: Using timer above configured range: 2
[  374.603515] HPET: Using timer above configured range: 2
[  374.603519] HPET: Using timer above configured range: 2
[  374.603523] HPET: Using timer above configured range: 2
[  374.603527] HPET: Using timer above configured range: 2
[  374.603531] HPET: Using timer above configured range: 2
[  374.603535] HPET: Using timer above configured range: 2
[  374.603539] HPET: Using timer above configured range: 2
[  374.603543] HPET: Using timer above configured range: 2
[  389.380249] device eth0 left promiscuous mode
[  390.099756] vboxnetflt: 0 out of 4 packets were not sent (directed to host)
}}}
Attaching VBox.log's in a second.",dimaqq
16861,Safenet Sentinel Driver,Windows,Windows,VirtualBox 5.1.22,2017-06-28T08:31:04Z,2017-06-28T08:31:04Z,"Hi,
I am using Safenet Sentinel Drivers (security dongles).
Since Virtual Box V5.0 the driver is no longer usable on my Windows Virtual Box machines (W7 64 bits).
So I used to stay on V4.3.40 version.
Unfortunately, last W10 update forced me to upgrade my Virtual Box version cause V4.3.40 does not work anymore.
Could you make Safenet Sentinel Drivers work again please?
Thanks a lot.
Regards,",Zikbull
16862,problem with eCS (OS/2) guest on copy,other,other,VirtualBox 4.2.36,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
16867,Windows Aero on Windows Vista & Windows 7 won't working,Windows,Windows,VirtualBox 5.1.22,2017-07-02T04:41:09Z,2017-07-02T04:41:09Z,I cannot running Windows Aero on Windows Vista and Windows 7 (except Windows 8.x and Windows 10) on latest version of VirtualBox. Please make changes on display driver to support Windows Aero like a Windows 8+ display driver.,Hanif Shaquille
16868,Guest background not fully cleared in seamless mode,Linux,Windows,VirtualBox 5.1.22,2017-07-03T09:33:11Z,2017-07-03T09:33:11Z,I'm running Windows 7 Pro as guest on a Linux Mint 18.1 host (both 64 bit). Seamless mode seems to work quite well despite relatively slow redrawing of guest windows. But there is a problem with the suppression of the windows background: There is always a square of the windows desktop keeping on the host desktop and I cannot get rid of it.,Mellon
16877,BSoD CLOCK_WATCHDOG_TIMEOUT,Windows,Linux,VirtualBox 5.1.22,2017-07-05T17:30:24Z,2017-07-05T17:30:24Z,"Machine Log: https://pastebin.com/raw/zYqqUp1T
Host OS: Windows 10
There is a dmp file from the bluescreen wich shows VBoxDrv.sys
I'm using Homestead (laravel) with vagrant. Maybe that helps.
Hopefully this is not a duplicate

This bsod just happens randomly when doing something in host system
DMP file can be loaded here: http://www49.zippyshare.com/v/1pxcsU2X/file.html
as to big for the attachmnent page.",keving
16875,VBox 5.1.22 on intel i3 samsung laptiop virtualbox fails to start,Windows,Windows,VirtualBox 5.1.22,2017-07-06T14:24:46Z,2017-07-06T14:24:46Z,(pasted log file removed),Robert Fernando
16864,VBox 5.1.22 Does Not Start VM after Upgrade from Win7 to Win10,Windows,Linux,VirtualBox 5.1.22,2017-07-06T14:39:40Z,2017-07-06T14:39:40Z,"VM's created with Manager 5.1.22 r115126 were working in Win7.
Upgraded to Win10 Enterprise, ver 1703, build 15063.0.
VMs will not start.
VMs are Ubuntu Xenial 16.04.
Tried running the repair VM Manager from the VBox installer.  Did not work.

On VM ""Start"", I get 2 popups.  
The 1st popup refers to running a cmd 'sc.exe', the results of which are posted.
The 2nd popup refers to a file that I pasted below.
I could not find a button to attach the file.

COMMAND - SC.EXE
{{{
sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.
}}}",jkAB
13163,Clipboard errors,Windows,Windows,VirtualBox 4.3.12,2017-07-07T17:09:11Z,2017-07-07T17:09:11Z,"Hi, all. I posted my experience with clipboard problems in the Forum as follows:
Hi, we have several troubles with a COM Add In using VSTO technics. What happens: The COM Add In does more then one clipboard operation in one thread (using the copy-paste-commands of the application). It works fine, except if: Virtual Box is running (on the host System where the Add In runs), with Windows Guest System and installed Virtual Box Extensions and with at least one user. Then we get clipboard errors, which show, that after a copy command the clipboard is empty or contains invalid data for the paste command. These errors don't occur, if there is no user on the guest machine or if there is a user, but the Virtual Box extensions are not installed. We feel there is a big bug in the Virtual Box extensions handling the clipboard.
This error occurs only with Virtual Box (not with MS Virtual PC nor with VM Ware nor with TeamViewer Virtualization) and only with at least one user logged on to the guest and only with installed VB Extensions on the guest. 
The shared clipboard in the General Settings is turned off! I don't believe that the error occurs in our MS Office Solutions with VSTO COM Add Ins (I got the error in other add ins, too: clipboard empty or invalid data) because of the mentioned circumstances.",EP
16884,custom vbox icons revert second time vm is run,Mac OS X,all,VirtualBox 5.1.22,2017-07-07T17:55:59Z,2017-07-07T17:55:59Z,"Related to https://www.virtualbox.org/ticket/15052

I would like to give my VMs custom icons, to distinguish between them in the Dock (tray) and in the app switcher (which for all but the selected app shows only the icon)

In macOS you can give a file or app a custom icon via the Finder by opening the `Get Info` window, selecting the icon, and pasting a new one on top of it.

If I give one of my _.vbox_ VM files a custom icon via `Get Info > paste the new icon`, VirtualBox reverts it to the default light blue cube after on the second open. That is, I apply a custom icon, open the VM, shut down the VM, and open the VM, and while it's opening for the second time the icon reverts.

",olets
16895,"Host BSOD when starting any VM on Windows 10 host, without Hyper-V",Windows,all,VirtualBox 5.1.22,2017-07-10T16:52:16Z,2017-07-10T16:52:16Z,"I have a largely-clean Windows 10 system with VirtualBox installed. When I attempt to start any VM (including a Centos 7.0 box, and a basic DOS VM), Windows 10 BSODs with `SYSTEM_SERVICE_EXCEPTION`, Bug Check Code `0x0000003b`.

I found multiple references to this being a conflict with Windows 10's own Hyper-V Virtualisation, so I have disabled the Hyper-V services and removed the feature from Windows; the BSOD still happens. I have also updated host graphics and audio drivers (just in case). I have tested VirtualBox versions 5.1.22 (last stable), preview 5.1.23, and 5.0.40 (which is known-good in my department).

Attached are the VBox.log, VBoxHardening.log for both the DOS and Centos systems, and a representative minidump. Analysis of the minidump on Superuser.com (https://superuser.com/a/1228520/82337) suggests that VMMR0.r0 has attempted to execute a Privileged Instruction.

I'm not sure if any further diagnostics would be helpful here, but please ask and I will attempt to get them for you.",Chowlett
16902,P2P connections die quickly under certain circumstances,Windows,Windows,VirtualBox 5.1.22,2017-07-15T09:03:45Z,2017-07-15T09:03:45Z,"Conditions to replicate are rather unusual so please cope with me:
- an application using P2P connectivity is let to operate for a few minutes (5 minutes should be more than enough);
- you may close the P2P application when you want to get to the next step. Wherever you close the P2P application and its active connections won't make a difference;
- pause the VM execution for a few minutes (5 minutes should be more than enough);
- when resuming VM try to repeat the first step and witness the connection failure.
TCP connections seam unaffected.
I only tested NAT network.

I reproduced this with [http://www.sopcast.com Sopcast] which is a P2P application.
- Install the latest version (4.2.0) in a Windows VM;
- Visit [http:///www.cooltvi.com cooltvi.com] in Internet Explorer and select a channel;
- Allow the ActiveX to run - this would start the live broadcast which is P2P based. 
Sopcast requires Direct3D9 for video to render. But this is not required to reproduce this issue, it can very well be reproduced with black screen.

I could reproduce with Windows xp/posready 2009, 7, 8.1 and 10 guests.
I tested with AMD PCNET Fast III, Intel PRO 1000 T-Server and MT Desktop, Paravirtualized Network.

I'll post logs if necessary. 
  
 
 
",pal1000
16600,Strange icon under Fedora 25 KDE,other,other,VirtualBox 5.1.18,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
12616,Implement write support for VHDX,all,all,VirtualBox 4.3.6,2017-07-17T11:16:26Z,2017-07-17T11:16:26Z,"When trying to create a virtual machine, when selecting hard drive, I've selected a vhdx create by Windows 8 Hyper-V. I get the following errors:

Failed to open the hard disk file C:\SharePointDev.vhdx.

Could not open the medium 'C:\SharePointDev.vhdx'.

VD: error VERR_NOT_SUPPORTED opening image file 'C:\SharePointDev.vhdx' (VERR_NOT_SUPPORTED).

Result Code: E_FAIL (0x80004005)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)




",mrwjr2003
16907,"Vbox additions 5.1.22 in CentOS 6 cause display adapter to be ""unknown""",Windows,Linux,VirtualBox 5.1.22,2017-07-18T06:02:11Z,2017-07-18T06:02:11Z,"I've just upgraded vbox from 5.0.30 to 5.1.22. One of my guests runs CentOS (6.3). 

After updating the vbox additions in this guest, the first symptom I noticed is that screen resize stopped working (was not reflected in the X server in the guest). I then noticed that the display is recognized as ""unknown"" (not ""vbox""), and all options in ""View -> Virtual Screen 1"" were greyed out. 
All in all, it looked as if the graphics driver piece of the vboxadditions is misbehaving or missing, even though the install went smoothly.

I have downgraded the vbox additions in this guest to 5.0.30 - left the host at 5.1.22 - and lo and behold, everything seems to work fine.

I tried a couple of back-and-forth installs of 5.1.22/5.0.30, and it is 100% reproducible.",doron
15669,VM crash during start (Intel Atom D525),Linux,Windows,VirtualBox 5.1.2,2017-07-18T18:36:36Z,2017-07-18T18:36:36Z,During start of Windows 2000 VM under Ubuntu 14.04 LTS crashes whereas it was working fine with 5.0.24.,PBT78
15303,NAT host adapter responds to traffic when it shouldn't,other,all,,2017-07-19T11:23:01Z,2017-07-19T11:23:01Z,"When using a NAT network, the host adapter will generate TCP RST packets in response to packets that are not destined for that interface. For example, here we have the following network setup:
{{{
52:54:00:12:35:02 10.0.2.2   VirtualBox router
08:00:27:7c:00:6c 10.0.2.15  VM
}}}
And the VM sends this packet:
{{{
TCP SYN
Src: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
Dst: Eth 08:00:27:7c:00:6d / IP 10.0.2.100 / TCP 80
}}}
Then, the VM will receive this spurious packet:
{{{
TCP RST,ACK
Src: Eth 52:54:00:12:35:02 / IP 10.0.2.100 / TCP 80
Dst: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
}}}
Note the source MAC. This is the host adapter's MAC. The expected result is that no packet will be sent in response to the original packet above, since the target host does not exist on the network and any other host receiving the packet should disregard it since the destination MAC does not match their MAC.

I have attached a pcap of the problem that was generated like this (nping is part of nmap):
{{{
arping -I enp0s3 -c 1 10.0.2.2
nping --tcp --dest-mac 08:00:27:7c:00:6d 10.0.2.100
}}}
Tested with VirtualBox 4.3.36, 5.0.12 and 5.0.16 using Debian, Ubuntu and FreeBSD.",Mike446
16919,"Crash, possibly when pressing several keys very fast or simultaneously",Windows,Windows,,2017-07-19T20:00:06Z,2017-07-19T20:00:06Z,"After installing version 5.1.24 and worked for a while in an XP guest, it crashed. It did that a 2nd time and that's when i got the attached log. Both times i was typing, so i got the impression (without being sure) that it crashed because i was typing too fast or because i pressed many keys simultaneously.

After a fresh start, i tried to reproduce the crash by typing fast and pressing many keys at the same time but without any success.

The same host/guest combination has worked without such issues from version 5.1.0 up to 5.1.22.

Host: WIn7 SP1, Guest: WinXP SP3.

P.S. After installing 5.1.24, i noticed a certain slugginess (even after installing guest additions) when maximizing/restoring/resizing the guest window. Again, was not happening in 5.1.22.",Wand
16905,Shared folders hangs by configuration,Windows,Windows,VirtualBox 5.1.22,2017-07-19T22:32:44Z,2017-07-19T22:32:44Z,"I have windows 10 host with windows 10 guest and when I try to configure the shared folders it hangs always and I have to kill the process.
It is the same where I configure it, in the VM manager (guest turned off) after choosing the folder on the host it hangs, in the virtual machine menu as soon as I try to configure a shared folder it hangs and I can't choose any folder on the host.
I was checking the log file of both (VM manager and virtual machine) but there is exactly nothing. I saw other similar tickets about shared folders hanging, but not really my problem, in my case it freezes during the configuration of the shared folder, and moreover the other tickets have been resolved.",spamme1
16417,vboxsf crashes process or VM in case of many file stat operations on shared vboxsf file system in a short time,Linux,Linux,VirtualBox 5.1.14,2017-07-20T17:23:49Z,2017-07-20T17:23:49Z,"We use a vagrant based toolchain to automatically generate VMs for executing unit tests. They run on Ubuntu 16.04 LTS 64-bit hosts, and the VMs themselves contain various different older and newer Linux distributions. We use current VirtualBox 5.1.14 and also the 5.1.14 guest tools.

Quite a significant percentage (10-20%) of our VM deployments was not successful. In case of ""default"" paravirtualization using KVM, the whole VM freezes, and the VBox.log file just says:

{{{
00:00:42.027263 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}

If using the ""minimal"" paravirtualization, VM operation continues, just the unit test process itself dies (see log below). This happens consistently at the same place where there are many stat() calls made to get the ctime information of many thousands of (empty) cache files on a shared vboxsf file system, before outdated files are supposed to be cleaned up. If I remove this code part, the error does not occur any more. Therefore my (uneducated) assumption is that it could be related to running many stat operations in a short time. Here's the stack trace as found in /var/log/kern.log in the instance.

{{{
Jan 21 22:23:14 vagrant kernel: [    8.021389] vboxsf: Successfully loaded version 5.1.14 (interface 0x00010004)
Jan 21 22:23:14 vagrant kernel: [    8.328536] VBoxService 5.1.14 r112924 (verbosity: 0) linux.amd64 (Jan 16 2017 17:38:46) release log
Jan 21 22:23:14 vagrant kernel: [    8.328536] 00:00:00.000093 main     Log opened 2017-01-21T22:23:14.323839000Z
Jan 21 22:23:14 vagrant kernel: [    8.328566] 00:00:00.000154 main     OS Product: Linux
Jan 21 22:23:14 vagrant kernel: [    8.328578] 00:00:00.000170 main     OS Release: 3.16.0-4-amd64
Jan 21 22:23:14 vagrant kernel: [    8.328589] 00:00:00.000182 main     OS Version: #1 SMP Debian 3.16.39-1 (2016-12-30)
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000193 main     Executable: /opt/VBoxGuestAdditions-5.1.14/sbin/VBoxService
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000194 main     Process ID: 1028
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000195 main     Package type: LINUX_64BITS_GENERIC
Jan 21 22:23:14 vagrant kernel: [    8.329284] 00:00:00.000860 main     5.1.14 r112924 started. Verbose level = 0
Jan 21 22:27:01 vagrant kernel: [  233.348410] VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-228.
Jan 21 22:27:01 vagrant kernel: [  233.348430] general protection fault: 0000 [#1] SMP 
Jan 21 22:27:01 vagrant kernel: [  233.348461] Modules linked in: vboxsf(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc vboxvideo(O) ttm drm_kms_helper ppdev drm evdev vboxguest(O) crc32_pclmul i2c_piix4 pcspkr i2c_core serio_raw aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd parport_pc battery processor parport video thermal_sys ac button autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic ata_generic crct10dif_pclmul crct10dif_common crc32c_intel e1000 psmouse ata_piix libata scsi_mod
Jan 21 22:27:01 vagrant kernel: [  233.348614] CPU: 1 PID: 1925 Comm: otrs.UnitTest.p Tainted: G           O  3.16.0-4-amd64 #1 Debian 3.16.39-1
Jan 21 22:27:01 vagrant kernel: [  233.348661] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jan 21 22:27:01 vagrant kernel: [  233.348689] task: ffff8800797bcce0 ti: ffff88007bdcc000 task.ti: ffff88007bdcc000
Jan 21 22:27:01 vagrant kernel: [  233.348718] RIP: 0010:[<ffffffffa02666c1>]  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.348763] RSP: 0018:ffff88007bdcfb98  EFLAGS: 00010282
Jan 21 22:27:01 vagrant kernel: [  233.348784] RAX: 00000000ffffff1c RBX: 0000a0007bdcfc84 RCX: 0000000000000001
Jan 21 22:27:01 vagrant kernel: [  233.348813] RDX: 0000000000000000 RSI: 000000000000002f RDI: ffff88007bdcf9a0
Jan 21 22:27:01 vagrant kernel: [  233.348842] RBP: 5f7c81f4149bd010 R08: 000000000000000a R09: 00000000000001c0
Jan 21 22:27:01 vagrant kernel: [  233.348870] R10: 0000000000000000 R11: ffff88007bdcf6be R12: 0000b00000000000
Jan 21 22:27:01 vagrant kernel: [  233.348898] R13: 1b3eed7500000000 R14: 5f7c81f4149bd064 R15: 5f7c81f4149bd010
Jan 21 22:27:01 vagrant kernel: [  233.348927] FS:  00007ff073ca7700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.348958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 22:27:01 vagrant kernel: [  233.348981] CR2: 00007ffec82d3ff8 CR3: 000000007bcd8000 CR4: 00000000000406e0
Jan 21 22:27:01 vagrant kernel: [  233.349008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.349033] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jan 21 22:27:01 vagrant kernel: [  233.349072] Stack:
Jan 21 22:27:01 vagrant kernel: [  233.349082]  001041ed149bd010 000003e900000000 00000002000003e9 013aa00300000902
Jan 21 22:27:01 vagrant kernel: [  233.349114]  0000000000000000 0000000000000000 ffff880023350880 0000006c00000004
Jan 21 22:27:01 vagrant kernel: [  233.349147]  ffff88007bdcfbfc 0000a00000020830 ffff88007b0c6000 ffffffffa03f877c
Jan 21 22:27:01 vagrant kernel: [  233.349178] Call Trace:
Jan 21 22:27:01 vagrant kernel: [  233.349194]  [<ffffffffa03f877c>] ? sf_stat+0x5c/0x110 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349219]  [<ffffffffa03f88b0>] ? sf_inode_revalidate+0x80/0xd0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349246]  [<ffffffff811b5192>] ? __inode_permission+0x22/0xb0
Jan 21 22:27:01 vagrant kernel: [  233.349269]  [<ffffffff811b58e6>] ? link_path_walk+0x256/0x870
Jan 21 22:27:01 vagrant kernel: [  233.349292]  [<ffffffff811c281a>] ? __d_lookup+0x7a/0x150
Jan 21 22:27:01 vagrant kernel: [  233.349979]  [<ffffffffa03f8914>] ? sf_dentry_revalidate+0x14/0x20 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.350641]  [<ffffffff811b47de>] ? lookup_fast+0x25e/0x2b0
Jan 21 22:27:01 vagrant kernel: [  233.351302]  [<ffffffff811b6055>] ? path_lookupat+0x155/0x780
Jan 21 22:27:01 vagrant kernel: [  233.351927]  [<ffffffffa03fa6ee>] ? VbglR0SfCreate+0x7e/0xa0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.352603]  [<ffffffff811b66a6>] ? filename_lookup+0x26/0xc0
Jan 21 22:27:01 vagrant kernel: [  233.353267]  [<ffffffff811ba8e4>] ? user_path_at_empty+0x54/0x90
Jan 21 22:27:01 vagrant kernel: [  233.353855]  [<ffffffff810ed71e>] ? from_kgid_munged+0xe/0x20
Jan 21 22:27:01 vagrant kernel: [  233.354431]  [<ffffffff811af53a>] ? cp_new_stat+0x13a/0x160
Jan 21 22:27:01 vagrant kernel: [  233.354976]  [<ffffffff811af0e6>] ? vfs_fstatat+0x46/0x90
Jan 21 22:27:01 vagrant kernel: [  233.355536]  [<ffffffff811af57a>] ? SYSC_newstat+0x1a/0x40
Jan 21 22:27:01 vagrant kernel: [  233.356067]  [<ffffffff8151adcd>] ? system_call_fast_compare_end+0x10/0x15
Jan 21 22:27:01 vagrant kernel: [  233.356577] Code: 01 b9 ff ff ff ff 48 89 da 4c 89 d6 4c 89 ef e8 b6 df ff ff 41 89 c7 0f 1f 00 48 83 c4 40 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d <c3> 66 0f 1f 44 00 00 49 83 f8 17 0f 86 34 0c 00 00 48 8d 83 00 
Jan 21 22:27:01 vagrant kernel: [  233.358611] RIP  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.359118]  RSP <ffff88007bdcfb98>
Jan 21 22:27:01 vagrant kernel: [  233.359636] ---[ end trace 54b9778e1a5d744b ]---
}}}

For reference, here's the Perl code that is used to cleanup the (empty cache files):

{{{
my $Wanted = sub {

    # Skip nonregular files and directories.
    return if ( !-f $File::Find::name );
    my $Stat = File::stat::stat($File::Find::name);
    if ( $Stat && ( time() - $Stat->ctime() > $CacheTTLSeconds ) ) {    ## no critic
        unlink $File::Find::name;    # Don't die here, this could be removed in the background by another process too.
    }
};
File::Find::find( $Wanted, $CacheDir );
}}}

Less often, a similar error occurs during the vagrant provisioning of the instances, where we copy the source code of our project from the /vagrant shared vboxsf folder into the VM. Here just a simple ""cp -r"" is used during the deployment. It could be the same problem:

{{{
==> default: Copying OTRS code to /opt/otrs
==> default: cp: cannot stat â/vagrant/Sources/otrs/var/httpd/htdocs/js/thirdparty/ckeditor-4.5.6/plugins/mathjax/lang/cy.jsâ: Protocol error
}}}

Please let me know if I should try to provide additional information, and thanks a lot for taking a look at this.",mrtngrnr
16059,Unpaused hidden vms are crashing in i3-wm when removing host-screen,Linux,all,VirtualBox 5.1.6,2017-07-21T15:18:20Z,2017-07-21T15:18:20Z,"I'm running virtualbox on archlinux with the i3 window manager (all installed via pacman). Furthermore I'm working with two monitors on my host, thus using two screen outputs.  Since updating virtualbox from version 5.0.22-1 to 5.1.6-1 (i3-wm stood in newest available verion 4.11-1) the following error was introduced:

If I store the virtual-guest GUI-representations in an tabbed i3-container (thus only the guest behind the active tab is displayed and the other ones are kept hidden behind their tabs) and remove one of my two outputs via „xrandr --output <OUTPUT> --off“, i3 (as always) starts to merge all workspaces to the remaining monitor. Unfortunately all vms which were awake and hidden behind a inactive (meaning not displayed) i3 tab are crashed afterwards. 

The logfiles carry no information about the crashing reason, meaning both, the crashed and survived ones, whose which moved (or had to be moved) to another output and those which stayed (or should have stayed) on the remaining one, they all contain this lines in their logfile:

00:02:03.886456 GUI: UIMachineLogic: Host-screen count changed
00:02:04.014195 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.014233 GUI: UIMachineLogic: Host-screen available-area changed
00:02:04.045512 GUI: UIMachineLogic: Host-screen geometry changed
00:02:04.045641 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.045655 GUI: UIMachineLogic: Host-screen available-area changed

Is there a way to tune the logging amount for this purpose? Here is my output of

vboxmanage debugvm testvm show logdbg-settings    
Debug logger settings:
                    VBOX_LOG=all=0x0
              VBOX_LOG_FLAGS=enabled unbuffered uself overwrite abs hex
  

One possible workaround is to pause all vms, another is to keep all vms visible on a focused workspace while removing one output. Furthermore while working with two monitors the workspaces can be moved between them without causing a crash of the hidden and unpaused vms.

This is a quite strange but easy reproducible behavior. For testing purposes I set up new vms without virtual HDs just running into BIOS-settings and they crashed too.

Could be related to: https://www.virtualbox.org/ticket/15863 
",1337
16934,Pause or auto-snapshot on guest restart,all,all,VirtualBox 5.1.24,2017-07-24T09:16:09Z,2017-07-24T09:16:09Z,"== The Problem ==
There are some cases where it would be advantageous to automatically pause or take a snapshot of a guest that is in the process of restarting.

For example:
* Pausing during OS install to allow device removal, etc.
* Automatic snapshots during OS/software install as clean points to return to or clone.
* Pausing if there is an unexpected restart (to prevent restart loops, etc.)

Trying to do this manually often becomes a test of reflexes. It's necessary to catch the guest in the act of restarting, move focus to that window, and pause it before the guest OS takes over after restarting.

== Implementation ==
Pausing would occur immediately after the restart (on the ""Oracle"" screen).

Taking snapshots would require converting the restart into a shutdown, taking an offline snapshot, and then starting the VM again.

For the GUI, I envision an ""Action on Restart"" menu item, and sub-items to pause during the next restart, or to take snapshots during the next 1-3 restarts (as the current operation may restart the guest multiple times). A CLI implementation of those options is straightforward enough as well.

In most cases, there would seem to be no need for this setting to be stored if the VM isn't running. However, the pause setting being sticky might be useful in cases such as the third example above.",Galactic
16925,virtio-net slower than Intel PRO/1000 Desktop,Windows,Linux,VirtualBox 5.1.22,2017-07-24T09:32:36Z,2017-07-24T09:32:36Z,"Confirmed on version 5.1.24.

Host: Windows 10[[BR]]
VM: Debian 9 with Guest Additions

Host-only NIC with Intel PRO/1000 Desktop
 * iperf3 
  * Host => VM : 2.68 Gbps
  * Host <= VM : 1.20 Gbps

Host-only NIC with virtio-net
 * iperf3
  * Host => VM : 2.11 Gbps
  * Host <= VM : 0.96 Gbps",cantonese
16909,kali linux is not installing,Linux,Windows,VirtualBox 5.1.22,2017-07-24T09:47:57Z,2017-07-24T09:47:57Z,i choosed the version debian 32bit and then i started the machine and clicked Graphical install after this all i see its a black screen,LazyDanu
16897,NtCreateFile failed: Unknown Status -626,Windows,Linux,VirtualBox 5.1.22,2017-07-24T10:01:14Z,2017-07-24T10:01:14Z,"Windows 10 Version 1703 Build 15063.413[[BR]]
Virtual Box Version 5.1.22r115126(Qt5.6.2)

The virtual machine 'AHF' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ~\Logs\VBoxHardening.log'.

{{{
Result Code: E_FAIL (0x80004005)
Component:   MachineWrap
Interface:   IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}",TheChris
16917,vb virtual display adapter not VGA Compatible,other,other,VirtualBox 5.1.22,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
16916,vb crashes guest with guest additions Divide by Zero Error,other,Windows,VirtualBox 5.1.22,2017-07-24T16:11:01Z,2017-07-24T16:11:01Z,"Divide by Zero Error
VirtualBox Graphical User Interface Version 5.1.24 r117012 (Qt5.6.2)
VBoxGuestAdditions_5.1.25-117026
Win2Ksp4
",Tracey
16942,removing the deb package should also remove the systemd service,Linux,other,VirtualBox 5.1.24,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
16906,Unable to start Virtual Machine (exit code 0x01),Windows,Windows,VirtualBox 5.1.22,2017-07-25T21:57:34Z,2017-07-25T21:57:34Z,"Dear Virtual Box support,

i have a critical problem on my Windows 10 machine (64bit), without any previous advice all the Virtual Machines installed are unable to start. 
I started and used VM succesfully one day and after restarting my toshiba notebook PC i had this problem.


Here is the error reported when starting a Virtual Machine:

------

Apertura di una sessione per la Macchina Virtuale Win 7 (64-bit) non riuscita.

The virtual machine 'Win 7 (64-bit)' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Virtual Box VM\Win 7 (64-bit)\Logs\VBoxHardening.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaccia: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

----

The log of the startup are attached to this message .

Please give me some feedback about this issue.

I used VB for many years and this is first time i encouter souch a big problem.

Best regards,
Massimo Cavagni",MC77
15889,Windows 10 guest turned to abort state when 3D acceleration is enabled,Linux,Windows,VirtualBox 5.1.4,2017-07-26T10:35:14Z,2017-07-26T10:35:14Z,,Kaho Ng
16924,Linux 4k Display with interface scaling double Hi-DPI VirtualBox too small,other,other,VirtualBox 5.1.22,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
16883,Virtualbox 5.1.22 crashes ethernet card on Ubuntu 16.04 64bit,Linux,Linux,VirtualBox 5.1.22,2017-07-26T13:13:51Z,2017-07-26T13:13:51Z,"I have a stock install of Ubuntu 16.04 64bit (Unity desktop) on my laptop.
As an addition there is virtualbox 5.1.22 installed from official Oracle repository and vagrant 1.9.5.

Whenever I start any virtual machine ethernet card just crashes.

Steps to reproduce:

mkdir -pv ~/foo
cd ~/foo
vagrant init bento/ubuntu-16.04
vagrant up

",kiklop74
16947,Virtual Kernel module effects bluetooth audio,Mac OS X,all,VirtualBox 5.1.24,2017-07-26T13:30:52Z,2017-07-26T13:30:52Z,"When VirtualBox is installed on a Mac, currently Sierra, but it's been this way for years, the bluetooth streaming audio if effected adversely.  It seems like the bluetooth is put into a two-way phone mode and streaming audio sounds terrible and the volume level wanders around.  This occurs when VB is not running.
If a start a Linux VM that enables audio, the bluetooth audio is ""fixed"".  The result of this is that each time I pair Bluetooth a headset I have to start a (linux) VM to fix the audio.  I can then close the VM and the audio usually remains working.  I use VB infrequently on my Mac but it must be installed to run both Linux and Windows clients.  I've tried uninstalling VB, but that doesn't seem to help.  However reinstalling the OS does help.  However as soon as VB is installed, the problem returns.",rsteele
15916,Windows 10 Guest - No Audio whenever screen is resized,Mac OS X,Windows,VirtualBox 5.1.4,2017-07-26T13:36:02Z,2017-07-26T13:36:02Z,"I'm running Virtualbox 5.1.4.r110228 

Host: OS X 10.10.5
Guest: Windows 10 ( guest additions installed, latest OS updates installed)

Whenever I resize the guest's screen size (like entering full screen) audio stops working. 

I haven't found a way of getting audio to start working again without a restart. 

",brian2000
16896,strange slow behavior in highly specific example,other,Windows,VirtualBox 5.1.22,2017-07-26T19:20:14Z,2017-07-26T19:20:14Z,"We use a program Plexon Offline Sorter to manipulate acquired data. Specifically, on an iMac with an i5 (identifier 15,1), the most recent version of Virtualbox (5.1.22), the program is impossible to manipulate data because it's too slow. It's not clear at which version of Virtualbox the program became unusably slow. 5.0.36 works fine. In addition, and quite oddly, the current version works fine when tested on a Mac Pro using the same vdi file. I tried to maintain the same settings in the vbox.

To reproduce this requires a number of steps.

The program is available for download at http://www.plexon.com/sites/default/files/OFSx64v3w7Setup.exe. 

It is installed on a Windows 7 SP1 x64 guest machine with security updates current as of 6/17. The RAM is set to 3072 MB.

An example data file can be found at https://drive.google.com/file/d/0B9hWBqS8eh_QUkZlYVNla0c3ODQ/view?usp=sharing

We configure Plexon to open this file by selecting for its extension, .nev, in the open file dialog.

Once the file is open, click on the channel 1 marker to select that channel. The center window is where manipulation takes place. Hold down the control key and drag shapes around the data with the left mouse button held down. The mouse should draw in real-time and then fill in the shapes once the mouse is released.

As mentioned above, on this particular iMac, this worked with older versions of Virtualbox such as 5.0.36. In the current version, the mouse dragging barely registers because the program can't keep up. ",mauricev
5233,"""fn + return = Insert"" does not work for host = mac",Mac OS X,Windows,VirtualBox 3.0.8,2017-07-27T06:53:59Z,2017-07-27T06:53:59Z,"Host: macnotebook pro running snow leopard up-to-date. VirtualBox version: 3.0.8. Guest: windows XP.

According to the mac documentation, in the mac keyboards of notebooks pressing ""fn + return"" produces ""insert"". That works well within the mac and also running windows via bootcamp. But when running it within VirtualBox the combination fn + return"" results in ""return"", not insert.
Expected: pressing the combination of keys ""fn + return"" produces ""insert"".",ecterrab
16950,crashis when adding virtual device to sata controller,Windows,all,VirtualBox 5.1.24,2017-07-27T09:32:16Z,2017-07-27T09:32:16Z,"in mashin settings window i opens the storage tab and right click on the controller's item on the list of the devices and select add harddisk or dvd in context menu
next the VirtualBox Manager crashis.",ilyapashuk
16951,SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with 4K resolution in Win10 guest,Windows,Windows,VirtualBox 5.1.26,2017-07-27T19:26:56Z,2017-07-27T19:26:56Z,"I have Win10 1703 (Creators Update) as both the host and the guest. My host computer is connected to a 4K (3840x2160) display which is set at 100% scaling (no HiDPI handling). The guest machine has both 2D and 3D acceleration enabled and virtual GPU RAM size is set all the way up to 256 MiB.

When I install guest additions, it works great at first. But when I maximize the guest window (which sets the guest's screen size at 3840x2055) and attempt to reboot the VM in that state, the guest OS tries to switch to that screen mode (borders of the black screen in guest window expand to the desired size) for a brief moment, but then BSODs with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

The only way to fix this is to select low-res mode from recovery boot options and set some lower resolution so that it gets saved in the registry - rebooting in normal mode works fine afterwards.

So all in all, it seems like the virtual GPU driver crashes if screen size is too big at boot time, even though it can switch to such mode just fine on a fully booted system.",kFYatek
16904,guest OS screen and host OS screen,Linux,Linux,VirtualBox 5.1.22,2017-07-28T05:51:21Z,2017-07-28T05:51:21Z,"My host OS is https://parabola.nu  with XFCE desktop .
I downloaded virtualbox latest version, SHA256 is right. And I run 'pacman -S gcc make linux-libre-headers' as root , and then virtualbox successfully installed.
Sometimes I use Ctrl + Alt + F1 to switch to terminal and use Alt + F2 to back to graphical user interface. I installed some guest OSes , one of the guest OSes is parabola too . When the guest OS sleeps, my host OS decreases screen brightness too",vbgaofei
16893,Windows XP guests hang/freeze during and after setup with choppy audio,Windows,Windows,VirtualBox 5.1.22,2017-07-28T06:17:40Z,2017-07-28T06:17:40Z,"The Windows XP guest stops responding and hangs for while and then continues to work normally. After a little time it freezes/hangs again and the cycle continues. The mouse won't move whenever Windows XP freezes. This cycle starts of hangs start during the part of setup that occurs after entering the product key and while getting the dialog for network settings. Additionally, I get cycles of extremely choppy audio that almost sounds like a chainsaw during the ""welcome to microsoft windows"" screen. I haven't experienced any of this behavior with Windows Server 2003 guests so far which is weird given that the two OSes are similar.",Eddy Smith
16952,Cannot start any VM after install extension pack.,Linux,all,VirtualBox 5.1.26,2017-07-28T08:44:45Z,2017-07-28T08:44:45Z,"After installation ""Extension Pack"", I cannot start any VM with error:
Loading VD plugins failed (VERR_ACCESS_DENIED).

After removing ""Extension Pack"" works all fine (of course without extension pack funcions).ls ",Polish
10081,"Updating damages existing ""pinned"" shortcuts",Windows,other,VirtualBox 4.1.8,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
16946,Windows 7 Home Premium with VirtualBox 5.1.24 64-bit VMs not offered,Windows,all,VirtualBox 5.1.24,2017-07-28T12:48:36Z,2017-07-28T12:48:36Z,"Problem:
- When I click New in VirtualBox, no matter which Type I select, there are no 64-bit choices listed in the Version, only 32-bit choices.

This is what I have:
- ASUS laptop
- Windows 7 Home Premium, 64-bit

This is what I did:
- Upgraded to VirtualBox 5.1.24.
- Ran this successfully in an elevated cmd window:
    bcdedit /set hypervisorlaunchtype off
- Enabled VT-d in my BIOS.  I do not see any setting named Virtualization.

Priority is 'blocker', because I cannot install Windows Server 2016.",clairestreb
16956,Presonus Mixer does not load the driver properly,Windows,Windows,VirtualBox 5.1.26,2017-07-29T01:02:41Z,2017-07-29T01:02:41Z,"I have a software title that we use in the Court Systems, we use mixers to record court proceedings. However, in VB I am unable to get the driver to load completely. I see the driver I see it in the USB settings but my software errors out with ""ASIO driver not loaded""

I have attached a log, as directed. 

E",EmGone
16958,Guest display auto-resize dit not work anymore,Linux,Windows,VirtualBox 5.1.26,2017-07-29T15:41:06Z,2017-07-29T15:41:06Z,"Guest display auto-resize worked perfectly for years (Windows 10 guest on Kubuntu 14.04 host). Since upgrade to VirtualBox 5.1.26 r117224 (from 5.1.24 r117012), the display resolution is not evaluated properly.

At startup the VM display resolution is wrong in fullscreen mode (1920x1080 instead of 1340x1440 on the host). There is no way to set it manually in Windows display properties settings. The maximum proposed resolution is 1920x1080. The host resolution (1340x1440) is not present in the proposed list.

The following workaround works:

* Disable ""Auto-resize Guest Display""
* Enable it again immediately (without any screen mode change before)

Then the guest window is set to the proper resolution (and this resolution become available in the Windows display settings).

'''Remark:''' there is another bug. Just after the VM startup (in fullscreen mode), this workaround cannot be applied directly. In the mini bar, the ""Auto-resize Guest Display"" option is not clickable (like if it was disabled). Pressing <host>-F  (to exit fullscreen mode) then  pressing <host>-F one time again (to get back in fullscreen mode) fixes it. The ""Auto-resize Guest Display"" option become operable.

The effect of the workaround is very volatile. If, for any reason, the guest display resolution is reevaluated, then the correct resolution is lost. For example, in all the following situations (but not limited to), the correct resolution is lost and the workaround has to be applied again to recover the correct screen resolution:

* The VM state is saved and the restored later
* The VM window is minimized and then restored on the host.
* The guest screen mode is changed (any mode), then restored to fullscreen.
* ...

Apparently, any action that conduct to reevaluate the guest display resolution bring back a wrong one (except if you are lucky and have a 1920x1080 display). The workaround must be applied again to get back to the correct screen resolution.

== Environment ==

=== Host ===

* OS : Ubuntu 14.04.1 (88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 )
* Kernel release: 3.19.0-80-generic
* Platform: x86_64
* Desktop: KDE (kubuntu-desktop)
* KDELibs Version: 4.13.3
* Qt version: 4.8.6
* VirtualBox version: 5.1.26 r117224

=== Guest ===

* OS: Windows 10 Pro
* Version: 1703 15063.483
* Platform: x64
* VirtualBox Guest Additions: 5.1.26




 ",Laurent Simon
16963,Repeating Left Mouse Click after Drag&Drop of files into the VM,Windows,Windows,VirtualBox 5.1.26,2017-07-31T08:49:38Z,2017-07-31T08:49:38Z,"Now and then it happens, that copying a file into the VM by drag & drop the mechanism does not work. Instead endless repeating mouse clicks are fired that make the running VM unusable.",angelo_kairos
16914,Implement YMF262 chip emulation for Sound Blaster sound card,all,all,VirtualBox 5.1.22,2017-07-31T10:13:28Z,2017-07-31T10:13:28Z,"Hello! It's sad that VirtualBox doesn't provide YMF262 chip emulation for the Sound Blaster 16 sound card. I have to install Windows 98 or MS-DOS as a guest to experiment with old musical software and some games, but a result is no sound from MIDI or anything sent to chip's registers.

You can use Nuked OPL3 emulator (LGPLv3 licensed)
http://www.vogons.org/viewtopic.php?f=9&t=37782
to provide complete and accurate YMF262 chip emulation with Sound Blaster 16 sound card.",Vitaly Novichkov
16964,Repeatable error copying network file into virtual box,Windows,Windows,VirtualBox 5.1.26,2017-07-31T15:58:31Z,2017-07-31T15:58:31Z,"Never had a problem with Virtual Box before. Using Virtual box on a win10 pro computer running an XP Pro virtual O/S. With the latest 5.1.26 I now am unable to copy large files from a network share into the VHD. I am able to copy the files from the shared folder with the Win10 pro box. Attached is the error message.
",Affiance
16974,VirtualBox crashes whenever Microsoft Lifechat USB headphones are plugged-in/out on Mac,Mac OS X,other,VirtualBox 5.1.26,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
16976,Fullscreen mode unavailable on FreeBSD,other,all,VirtualBox 5.1.24,2017-08-03T12:12:06Z,2017-08-03T12:12:06Z,"Display is fronze or mess when a guest switch to fullscreen mode(but guest OS still running and can connect with SSH or RDP). both Linux and Windows.

The OS & software

{{{
FreeBSD 11.1-RELEASE r321648 amd64
virtualbox-ose-5.1.24          General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-5.1.24     VirtualBox kernel module for FreeBSD

}}}

forgive my poor english and THKS for fix. 
",rezo.chiang
16948,Blank Screen (crash?) on update V5.1.22 -> V5.1.24,Windows,Windows,VirtualBox 5.1.24,2017-08-03T15:47:01Z,2017-08-03T15:47:01Z,"A few minutes after I updated to V5.1.24 my computer screen suddenly went black.   Ctrl-Alt-Delete did not bring up the Windows 10 blue options screen.  I couldn't get it to respond in any way.  Maybe crashed but without seeing anything I couldn't verify that.  Had to power off.   Tried again and same thing happened within about 10 min.  Had to roll back to V5.1.22.

In the change log I noticed ""GUI: prevent stopped screen updates or black screen on reboot in a multi-screen setup under certain conditions""

FYI: I do have two video cards in this computer.  One on the mother board (not used) and a NVIDIA NVS 315

",isgdre
16954,"Ubuntu 16.04 VM Win 7 Host; VM worked fine on 5.1.24, crashes on fullscreen in 5.1.26",Windows,Linux,VirtualBox 5.1.26,2017-08-03T19:25:17Z,2017-08-03T19:25:17Z,"I normally launch this VM fullscreen. It gave no issues up until v5.1.24. In v5.1.26, it crashes unless I run it in windowed mode.",Dale Visser
9987,Provide Additions for Mac OS X guests,Mac OS X,OSX Server,VirtualBox 4.1.6,2017-08-05T02:27:14Z,2017-08-05T02:27:14Z,There are no guest additions for Mac OS X for server editions or regular additions.,Matthew Sedam
16981,Inaccessible Virtual Machines,Windows,Windows,VirtualBox 5.1.22,2017-08-05T04:05:58Z,2017-08-05T04:05:58Z,"Hi, I have VirtualBox 5.1.22r115126 installed in my C drive. 
I set the Default Machine folder as: X:\Portable Installations\VirtualBox Saved Files. I store my VMs in my X Drive so that I don't lose my VMs when restoring a C drive backup with Macrium Reflect.

I recently restored a Macrium Reflect C Drive backup. Everything was fine and all my VMs were working. These are my VMs:

""Windows 7 64-bit New Install (Nothing Changed)"". As the name suggests this has Windows installed with nothing else on it.
""Windows 7 64-bit - Opera Portable"". This is a linked clone of the above which I then have Opera Portable on.

I had the linked clone running today and I saved a snapshot. I closed VirtualBox and restarted my PC. When I opened VirtualBox, both VMs are ""inaccessible"". It says a differencing image of snapshot ""snapshot name here"" could not be found. Could not find an open hard disk with UUID ""name here"".

How can I find out what caused the problem and how can I fix it?
Is there any reason why I can't have VMs on my X Drive but VirtualBox installed on the C Drive?
",DaveyMames
16983,Autorun.inf not correctly identified from 'file' command.,all,Windows,VirtualBox 5.1.26,2017-08-06T06:46:35Z,2017-08-06T06:46:35Z,"Based on a [https://forums.virtualbox.org/viewtopic.php?f=9&t=84005 recent discussion in the forums], the contents of the ""`Autorun.inf`"" file used in the GAs Windows installer, could/should be slightly modified to bring it in ""''compliance''"" with the '`file`' command found in almost all Unix-based OSes.

The problem arises from the fact that a proper ""`Autorun.inf`"" file should start with the ""`[autorun]`"" text. The current ""`Autorun.inf`"" file starts with the license (a comment). If  the ""`[autorun]`"" entry gets moved at the beginning of the file, before the comment, everyone/everything is happy.

Patch is published under the terms of the MIT license. Both lines ;) :
{{{
--- /Users/Shared/VirtualBox/Source/VirtualBox-5.1.26/src/VBox/Additions/WINNT/Installer/ISO/AUTORUN.INF	2017-07-27 16:13:52.000000000 +0300
+++ /Users/Shared/VirtualBox/Source/vbox/src/VBox/Additions/WINNT/Installer/ISO/AUTORUN.INF	2017-08-06 09:30:40.000000000 +0300
@@ -1,5 +1,6 @@
+[autorun]
 ;
-; Copyright (C) 2006-2016 Oracle Corporation
+; Copyright (C) 2006-2017 Oracle Corporation
 ;
 ; This file is part of VirtualBox Open Source Edition (OSE), as
 ; available from http://www.virtualbox.org. This file is free software;
@@ -10,7 +11,6 @@
 ; hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
 ;
 
-[autorun]
 open=VBoxWindowsAdditions.exe
 icon=VBoxWindowsAdditions.exe
 label=VirtualBox Guest Additions
}}}

Before the patch:
{{{
$ file /Users/Shared/VirtualBox/Source/VirtualBox-5.1.26/src/VBox/Additions/WINNT/Installer/ISO/AUTORUN.INF
AUTORUN.INF: ASCII English text, with CRLF line terminators
}}}
After the patch:
{{{
$ file /Users/Shared/VirtualBox/Source/vbox/src/VBox/Additions/WINNT/Installer/ISO/AUTORUN.INF
AUTORUN.INF: Microsoft Windows Autorun file.
}}}
",Socratis
16985,VB Additions incompatible with RAID driver,Windows,Linux,VirtualBox 5.1.26,2017-08-06T12:12:30Z,2017-08-06T12:12:30Z,"When installing a Linux (tested Xubuntu, Kubuntu and OpenSuse) in VirtualBox on a physical partition it hangs up when booting this partition natively '''if''' the machine uses a RAID (ie. Intel Matrix Storage Manager). The last message of boot is ""A start job is running for dev-disk-by\ ... .device""

When installing the Linux natively and then booting it in VirtualBox, it works but the VB-Additions fail to install.

On a normal AHCI-enabled machine, every thik's fine.",msta
16988,32 bit Windows 8 Guest on Ubuntu 17.04 spontaneously restarting with PIIX3 ATA error,Linux,Windows,VirtualBox 5.1.22,2017-08-07T07:01:52Z,2017-08-07T07:01:52Z,"I could find one similar report to the one I'm filing, but it's from 9 years ago here: https://www.virtualbox.org/ticket/2600 so I decided to file a new report.

I have a Windows 8 guest running on Ubuntu 17.04. When I trying to manipulate data in Excel (copying and pasting), the machine freezes then spontaneously restarts. I think this is the relevant error code from the log file:
{{{
00:12:32.753320 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:12:32.753435 PIIX3 ATA: Ctl#1: finished processing RESET
00:12:32.755451 PIIX3 ATA: LUN#2: performing device RESET
}}}",theronmuller
16975,Host-Only network vboxnet0 unvaliable until reload kernel module (FreeBSD host),other,all,VirtualBox 5.1.24,2017-08-07T07:03:17Z,2017-08-07T07:03:17Z,"Such as the problem, My guest use 3 ethercard:1 bridged, 1 NAT and 1 host-only.
the guest can't boot and show a error message after I reboot my computer. I have to unload and reload module to boot the guest.


The OS & software
{{{
FreeBSD 11.1-RELEASE r321648 amd64
virtualbox-ose-5.1.24          General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-5.1.24     VirtualBox kernel module for FreeBSD
}}}


forgive my poor english and THKS for fix.",rezo.chiang
16661,Maximized windows broken in seamless mode,Linux,Windows,VirtualBox 5.1.18,2017-08-08T07:48:32Z,2017-08-08T07:48:32Z,"When i maximize a window in seamless mode (host debian stretch, guest win 7), only the area of the former non maximized window is displayed the rest of the now maximized window is transparent.",mietz
16668,Office apps display error in seamless mode,Linux,Windows,VirtualBox 5.1.20,2017-08-08T07:50:13Z,2017-08-08T07:50:13Z,Windows with an non standard frame such as the ms office 2013 apps got an transparent aura surrounding them.,mietz
16993,Various widgets without labels for accessibility,Linux,all,,2017-08-10T15:44:38Z,2017-08-10T15:44:38Z,"Hi,

While Oracle assertions are for accessibility introducing VBox beta, I can say we are far from it. Beyond bugs I have submitted about crashes and I confirm with this release, a lot of buttons do not have any label on their widgets, hence a screen reader cannot tell what the button does. Filling the label area sends to qt-t-spi what an assistive technology needs to work properly.

Here is an examples:
- Main window: once opened, press tab twice. The focus reaches, respectively, on two buttons without labels, and ths screen reader just says ""Button""
",texou
16992,Linux filesystem through share folder will be data crash,Windows,Linux,VirtualBox 5.0.40,2017-08-10T20:44:24Z,2017-08-10T20:44:24Z,"Host Windows 7, Phy 16 GB RAM[[br]]
Guest Linux Centos 6.8, Virtual 3 GB RAM[[br]]
/share is share folder on Windows NTFS.[[br]]
[[br]]
Reproduce command:[[br]]
*---------- Start[[br]]
dd if=/dev/zero of=/share/tmp_fs bs=1M count=300[[br]]
mkreiserfs -f /share/tmp_fs[[br]]
mount -o loop /share/tmp_fs ~/x[[br]]
touch ~/x/mark (or copy anything to there)[[br]]
umount ~/x[[br]]
*---------- End[[br]]
[[br]]
Now, if you re-mount tmp_fs, you will found nothing in filesystem, and if you fsck on it, it will show filesystem broken.[[br]]
[[br]]
On 5.0.28, all thing are fine[[br]]
On 5.0.40 and above 5.1.x (Note: I don't try on 5.0.30 - 5.0.38), you will catch the bug.[[br]]
",C-MIKE
16999,VBoxDrv: Too many CPUs (288) for the GIP (max 256),Linux,other,VirtualBox 5.1.26,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
17002,Machine not running,Windows,Windows,VirtualBox 5.1.26,2017-08-12T06:02:35Z,2017-08-12T06:02:35Z,"I loaded VB easily enough, had issues getting Kali Linux loaded and installed on VB but finally had success. However, now when I run the machine I get a blank screen:
 and Kali Linux does not open. Any ideas?",Sailingonu
17005,Inaccurate Translation to Chinese,Windows,Windows,VirtualBox 5.1.26,2017-08-12T08:06:21Z,2017-08-12T08:06:21Z,"The label ""Name"" in the ""Network"" of ""Settings"" could be translated into ""接口名称""(""Interface Name"") rather than ""界面名称"".",kx_sun
16879,Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS),Linux,Linux,VirtualBox 5.1.22,2017-08-14T10:55:08Z,2017-08-14T10:55:08Z,"While using packer tool to automate creation of VM images I face the following errors:
{{{
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Error deleting virtual machine: VBoxManage error: VBoxManage: error: Cannot unregister the machine 'foo' while it is locked
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""Unregister(CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))"" at line 156 of file VBoxManageMisc.cpp
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
}}}
After this happens VM enters ""Guru Meditation"" state.

I searched for more information about the error got and found https://github.com/hashicorp/packer/issues/4309 referring to https://www.virtualbox.org/changeset/64906/vbox that seems to be some attempt to fix this (?).
Anyway, https://www.virtualbox.org/changeset/64906/vbox looks not to be included in VirtualBox-5.1-5.1.22_115126_el7-1.x86_64 RPM I am using in my Centos 7.3 (judging by the lack of VboxManage keyboardputstring/keyboardputfile API added in this changeset).

Steps to reproduce:
{{{
packer build -var vm_name=foo -var no_gui=true centos-vbox.json
Packer version 1.0.0
}}}
Mapping from packer API to VBoxManage calls can be seen in attached packer debug log. ISO image used is just a minimal CentOs 7.3 image. kickstart file should not be relevant for this bug.
The bug is not deterministic, it happens once per ~4 executions.",pstrzelczak
17008,VBOX running RHEL aborting,Mac OS X,Linux,VirtualBox 5.1.26,2017-08-14T19:17:59Z,2017-08-14T19:17:59Z,"I am running the following version of VBox:

'''VirtualBox VM 5.1.26 r117224 darwin.amd64 (Jul 27 2017 14:04:15) release log''

I am running RHEL guest from a Mac host. This has been working perfectly for almost 2 years now. However, recently I upgraded from a prior version (unfortunately I am not sure what the previous version was) to the current 5.1.26 version and ever since then I the guest OS aborts after a few hours of being up. I am not certain what is causing this, however, I do have a crash dump that I will attach from my Mac OS host.",Garfield-LzLabs
17012,Support Split2G variant for VDI format,all,all,VirtualBox 5.1.26,2017-08-14T19:24:24Z,2017-08-14T19:24:24Z,"I would like to have the Split2G variant for VDI just like for VMDK.
I know I could use VMDK, but Virtualbox cannot compact VMDK files.",opensourcer
17011,"VBox crashes; Host Win 8.1, Guest Debian Strech; amd64",Windows,Linux,VirtualBox 5.1.26,2017-08-15T08:35:23Z,2017-08-15T08:35:23Z,"VBox crashes on my new installation of Debian Stretch amd64 as guest system. My host system is Win 8.1, amd64. The crash happens after the installation of the Virtualbox Guest Additions during booting the guest. It is a permanent fault and happens during every boot.

Appended is the Win error message as image (part of a screen dump).",hwkraus
17016,instruction referenced at 0xe6826d43 referenced memory at 0x00000018 could not be read,Windows,Linux,VirtualBox 5.1.26,2017-08-15T16:47:38Z,2017-08-15T16:47:38Z,"windows7 host ubuntu 16.04 guest
moved the vm from a win7 notebook to a win7 workstation
a repeatable crash during vm startup, various instruction address

apparently solved the issue by changing chipset type from PIIX3 to ICH9, all other changes to vm settings had no effect

",devotip
16989,Snapshots should store differencing disks alongside parent virtual disks,Windows,other,VirtualBox 5.1.26,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
17001,Getting memory Access Violations 5.1.26,Windows,Linux,VirtualBox 5.1.26,2017-08-15T18:04:07Z,2017-08-15T18:04:07Z,"Randomly getting Memory Access Violations.  Often at some point during startup, but not always.

I looked in the VBox.log file, but nothing jumped out at me.

Are there other ways to debug this?

The VBox.log is attached.",jhellmers
16841,"5.1.18 working on Mavericks, but not with 5.1.20",Mac OS X,other,VirtualBox 5.1.22,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
15905,Running Windows 10 as a guest in Xubuntu 16.04.1 host freezes the machine (3D-related),Linux,Windows,VirtualBox 5.1.4,2017-08-17T15:12:28Z,2017-08-17T15:12:28Z,"While attempting to boot a Windows 10 guest on Xubuntu 16.04.1 host, as soon as the Windows logo and the dots running in a circle appear, the whole system hangs. Nothing can be done except pressing the physical power button to shut down the machine.

At first I thought this is related to https://www.virtualbox.org/ticket/13795, but that ticket tells the problem has been fixed already for 5.0.2 and my version is 5.1.4 directly from vbox repository.

I found somewhere that adding `nosmap` to kernel parameters would work, and once I managed to boot the guest system up. Today it didn't help.

I'm attaching the VBox.log, hopefully it helps. In it you will see that guest additions are from an older version. The guest OS was used in an older version (Ubuntu repository version 5.0.24-dfsg-0ubuntu1.16.04.1), but it shouldn't affect this as during the aforementioned time I managed to run the system, it informed me about this but didn't prevent the usage at all.

My setup:

{{{
jaska@ardbeg:~ 11:15:31 $ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

jaska@ardbeg:~ 11:16:37 $ uname -a
Linux ardbeg 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

jaska@ardbeg:~ 11:17:42 $ apt-cache policy virtualbox-5.1
virtualbox-5.1:
  Installed: 5.1.4-110228~Ubuntu~xenial
  Candidate: 5.1.4-110228~Ubuntu~xenial
  Version table:
 *** 5.1.4-110228~Ubuntu~xenial 500
        500 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 Packages
        100 /var/lib/dpkg/status
}}}",astraljava
16900,Guest Additions Will Not Install,Windows,Windows,VirtualBox 5.1.22,2017-08-17T15:14:00Z,2017-08-17T15:14:00Z,"Host: Windows 10 (64-bit)
Guest: Windows Server 2012 (64-bit)

Guest Additions will not install on the guest. When trying to install it, I get an error that it cannot execute ""VBoxDrvInst.exe"". I tried everything and nothing fixes it.

I have attached the log file for VM and also 2 screenshots of the error.

Thank you in advance for helping. I really need guest additions.


",pjkim
16903,Windows 10 crashes on VirtualBox session startup,Windows,Linux,VirtualBox 5.1.22,2017-08-17T15:27:49Z,2017-08-17T15:27:49Z,"VirtualBox: 5.1.22
Host: Windows 10
Guest: Kali

Windows 10 crashes when starting Kali - the blue screen shows error IRQL_UNEXPECTED_VALUE.

",caveman14
16242,"MacOS Sierra host, CentOS 7 guest, VBoxClient clipboard breaks when copying rich text in guest",Mac OS X,Linux,VirtualBox 5.1.10,2017-08-18T07:22:38Z,2017-08-18T07:22:38Z,"VirtualBox (on Mac host), version 5.1.10 r112026 (Qt5.6.2)

Host version Mac OS Sierra 10.12.1

All host patches up to date

CentOS 7 guest, version 7.2.1511

Guest additions installed and up to date, all guest OS patches up to date

Application running in guest: CLion 2016.3 Build #CL-163.7743.47, built on November 18, 2016
(https://www.jetbrains.com/clion/)


When copying text from CLion using Ctrl+C which seems to be copying rich text rather than plain text by default, the VBoxClient clipboard in the CentOS guest stops working. Nothing can be copied anymore between host and guest. If only plain text is copied, the clipboard works OK, but as soon as rich text is copied, the clipboard breaks completely.

The only way to fix it is to restart VBoxClient in the guest:

{{{
killall VBoxClient
VBoxClient-all
}}}


I do not expect rich text copy/paste to work correctly, but it must not take down the entire clipboard functionality in the guest and require VBoxClient to be restarted.

",tkvb
16995,Vb 5.1.26 can't display GUI on Solaris 10,other,other,VirtualBox 5.1.26,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
17026,VBox 5.1.26.117224 crashing guest with error,Windows,Windows,VirtualBox 5.1.26,2017-08-20T21:39:39Z,2017-08-20T21:39:39Z,"Hello,
as noted in summary there is some situations with my VirtualBox which often lead to crashing guest.
Host is Windows 7 Ent, X64.
Guest is Windows XP SP3.
Any other info please message me.
Log is attached.
Any help would be appreciated.
",H4rDw4rE
17028,ata2.00 exception Emask 0x0 SAct 0x0 SErr action,Linux,Linux,VirtualBox 5.1.22,2017-08-21T09:50:55Z,2017-08-21T09:50:55Z,"Hi

Every alternate day on Guest VM running with RHEL 6.5 64bit cpu usage is high and after reboot it shows this error
 
ata2.00 exception Emask 0x0 SAct 0x0 SErr action  on 0x6 is frozen

attached screen shot for more details[[Image()]]",prabhakarraksan
16486,VirtualBox on macOS crashes when laptop suspends/resumes,Mac OS X,Windows,VirtualBox 5.1.14,2017-08-21T17:33:28Z,2017-08-21T17:33:28Z,"I have a Macbook Pro (2015 retina display, switchable graphics) running a Windows 10 guest that crashes frequently when the laptop decides to suspend. Usually this is associated with me unplugging external displays and power while the lid is closed. However, it can happen even without the external displays, and just the laptop itself going to sleep.

I have tried:

- Reducing virtual CPUs to 1 and RAM to 4096.
- Enabling and disabling switchable graphics
- 2D acceleration and no 2D acceleration
- VirtualBox 5.1.8 and 5.1.14 (guest additions always at the appropriate matching level)
- Two external displays, one external display, no external display

I cannot solve the problem, and the regular crashes are causing major interruptions. I can't always control when the laptop suspends, as the power cord might be bumped or I might have it with me during a meeting and long enough gap between usage results in sleep.

I have attached the logs and macOS problem report from both 5.1.8 and 5.1.14.",Jason Hagar
17025,Problem in Virtual Box,other,other,VirtualBox 5.1.26,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
17029,"Multiple Instances of VBoxXPCOMIPCD, VBoxSVC, VBoxHeadless",Linux,Windows,VirtualBox 5.1.26,2017-08-23T12:18:41Z,2017-08-23T12:18:41Z,"Hello!

After upgrading from debian 8/jessie running virtualbox 5.1.24 to debian 9/stretch and virtualbox 5.1.26, multiple processes (at least two) for a single virtual machine may be started (with two seperate VBoxSVC-processes as their parents).

The commands ""vboxmanage showvminfo"" and also ""vboxmanage list runningvms"" sometimes report a wrong - ""powered off"" or ""aborted"" - state for running and fully functional machines.

Several Win10 and Win8 guests are not able to start anymore due to severe filesystem damages.

The relevant part of ""ps aufx"" looks something like this:

{{{
...
vbox      1788  Sl   /usr/lib/virtualbox/vboxwebsrv --background -F /var/log/vboxweb.log -R 10 -S 1048576 -I 86400
vbox      1800  S    /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      1809  Sl   /usr/lib/virtualbox/VBoxSVC --auto-shutdown
vbox      3834  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM221 --startvm 5e5c64e7-...
vbox      4093  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM320 --startvm cfe3de02-...
vbox      4186  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM050 --startvm 43d2653e-...
vbox      4187  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM222 --startvm 6206dddc-...
vbox      4441  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM223 --startvm 056443b9-...
vbox      4936  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM057 --startvm 0bd9f77d-...
vbox     18145  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM322 --startvm 0429d803-...
vbox      2083  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM321 --startvm 5b36d602-...
...
vbox      2169  S    /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      2174  Sl   /usr/lib/virtualbox/VBoxSVC --auto-shutdown
vbox      2218  Sl   \_ /usr/lib/virtualbox/VBoxHeadless --comment VM322 --startvm 0429d803-...
...
}}}

in this excerpt ""VM322"" is running as PID 18145 and 2218.

The host system is a DELL PowerEdge T620 server powered by two Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz running Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux.
Guests are about 36 machines running MS Windows (Win2000 - Win10).

A downgrade to the virtualbox 5.1.24 deb-package installed in debian ""stretch"" did not solve the problem.

Thanks a lot for any advice!",mh367
14898,VBox 5.0.10 Aborts Guest session on resume,Mac OS X,Linux,VirtualBox 5.0.10,2017-08-23T16:15:41Z,2017-08-23T16:15:41Z,"May be similar to #13874 but that was resolved...
I am running VBox for over a year and never experienced this, until running v5.0.10. All of a sudden now my guest session (Ubuntu 12.04 LTS with kernel 3.2.0-95) aborts when my MacBook Pro awakens (OS Mavericks).
This has happened several times and while I cannot reproduce at will, it is quite frequent.",RobCIQ
17036,VBOX_WITH_EXTPACK_VBOXDTRACE fails to build with glibc >= 2.26-2.fc27,other,other,VirtualBox 5.1.26,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
14979,mouse Lag on newer versions with DirectX games,Mac OS X,Windows,VirtualBox 5.0.12,2017-08-25T17:21:25Z,2017-08-25T17:21:25Z,"Hello,

I love Virtualbox. I do use the newest version 5.0.12 for everything except games. My guest is Windows XP SP3 and (I can confirm this is the same for SP2) and in the games Age of Empires II and Medal of Honor (Breakthrough).
Problem: Mouse lags a lot in the games. It makes it very difficult to play. I could provide a video if you want.
The last version that works right is 4.3.26 and it works quite well (but I have to uncheck the box ""Enable 2D acceleration"")
If there is some way I can help, please let me know.
You really have one of the best products out there. If there is a way to donate, let me know too.",BryceSteiner
17021,Problem showing a bsod (blue screen) in the guest machine,Linux,Windows,VirtualBox 5.1.26,2017-08-26T16:14:44Z,2017-08-26T16:14:44Z,"
When i have a bsod (blue screen) in the guest machine Windows 10,
then i don't view the bsod.
I can not know what is written in the BSOD.
I think this problem comes from the driver graphics Virtualbox.",Sizy458
17039,OSX 10.12.6 VB 5.1.26 r117224 reproducible crash /w Kubuntu,Mac OS X,Linux,VirtualBox 5.1.26,2017-08-27T19:20:40Z,2017-08-27T19:20:40Z,"
I have a MacBook Pro with OSX 10.12.6 running VB 5.1.26 r117224

The following steps will produce a hard crash/black screen reboot of OSX.

Download Kubuntu 17.04

Install with two gig, two cores, bump graphics memory to 64 meg, otherwise graphical installer won't work

Inside Kubuntu, apt update, then apt upgrade


I've watched it a couple times, seems to be during the *unpacking* of the new kernel, which strikes me as odd. Every time it just completely black screen reboots OSX, which is unusual - the OS normally stops in a graceful fashion with a notification screen.

I also use Lubuntu, which is very similar - no complaints here, just ran an apt upgrade on a fresh install, no problems.

I'm going to see if this also fails on Win8.1, will post a separate ticket if it does.",nrauhauser
6050,[feature-request] GUI: Please allow to delete branched snapshots sub-tree,other,other,VirtualBox 3.1.2,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
17042,"5.1.26, Mac OS X, VM aborts when external monitor/keyboard/mouse is unplugged",Mac OS X,Linux,VirtualBox 5.1.26,2017-08-29T15:35:42Z,2017-08-29T15:35:42Z,"Hello, 

Setup: VirtualBox 5.1.26 on Mac OS X 10.11.6 (El Capitan), guest os is Linux Ubuntu 14.0.4 LTE. Dual monitor. Keyboard, mouse and external monitor are routed from the lightning connector on the mac through an El Gato Thunderbolt2 Dock box. Specifically, the setup looks like:

MAC (lightning connector) -> El Gato Dock (USB + video cables) -> Dell U3415W monitor (USB ports)-> Keyboard, Mouse 

I updated today to 5.1.26 from '24. On the previous version I used to be able to unplug the lightning connector to the dock box from the Mac,  and the VM window would just move to the builtin display and keep going, receiving input from the builtin keyboard and trackpad.

However, on the new version the VM aborts instantly and repeatably as soon as I unplug the connector. 
  ",khomeino
17043,Can't update because of SSL certificate format error,all,Windows,VirtualBox 5.1.26,2017-08-29T16:26:01Z,2017-08-29T16:26:01Z,"VirtualBox 5.1.26 AND 5.1.27 R117677 (Qt5.6.2)

The network operation failed with the following error:
During network request: Wrong SSL certificate format.

My OS: Windows 10 Enterprise
version 10.0.15063

",arrobles
16984,Can't enter encryption password  OSX 10.12.5,Mac OS X,Linux,VirtualBox 5.1.26,2017-08-30T11:21:23Z,2017-08-30T11:21:23Z,"Hello,

Every machine that using a saved state + virtual encryption, can't be unlocked.  Either no password prompt shows up or the password prompt that appears does not allow any typing in it (can't be clicked).

Only solution for now is to discard the saved state and start up normally.

Another remark:  When pausing a VM, no password has to be entered to unlock/decrypt, ideally behaviour should be the same then we starting/starting from saved state.


",Neekoh
15630,Virtualbox guest control controls inaccessible with NVDA on Windows,Windows,all,,2017-08-30T12:55:11Z,2017-08-30T12:55:11Z,"When pressing for example host+q to access the shutdown dialog or accessing the menu with the usb devices, NVDA can not determine any type of a control and reports everything as unknown.",tyrylu
17045,"""vboxmanage list hostinfo"" fails if CPUs have gaps in their processor IDs.",Linux,other,VirtualBox 5.1.26,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
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,other,VirtualBox 4.3.4,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
17046,"host only network lost after resuming from sleep (H: win10, G:winserver2012)",Windows,Windows,VirtualBox 5.1.26,2017-08-30T23:51:01Z,2017-08-30T23:51:01Z,"Before host goes to sleep, connection works fine. After resuming from sleep, I can no longer ping the guest from the host (""Request timed out""). Occasionally, stoping vbox, resetting the interface on the windows side, then restarting vbox fixes connectivity. In other times, only a full host restart allowed me to recover.

before sleep: 
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           192.168.214.1
    Subnet Prefix:                        192.168.214.0/24 (mask 255.255.255.0)
    InterfaceMetric:                      25

>vboxmanage list hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            539037ce-b029-4212-858f-1b368320c5e5
DHCP:            Disabled
IPAddress:       192.168.214.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:4571:268b:9d7d:c79b
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:09
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

after resume:
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           169.254.199.155
    Subnet Prefix:                        169.254.0.0/16 (mask 255.255.0.0)
    InterfaceMetric:                      25

(vboxmanage's report is unchanged)",somersby
17047,"Memory Issue since updated to 5.1.26 - ""Instruction at 0x4336d43 referenced memory at 0x00000018. The memory could not be read.""",Windows,Linux,VirtualBox 5.1.26,2017-08-31T06:59:07Z,2017-08-31T06:59:07Z,"Host: Windows 7
Guest: Ubuntu Mate 16.04 LTS

Since I have updated to version 5.1.26, I often get a error message when starting the virtual machine (see attached picture).
After the error message, the virtual machine aborts.
After a few tries it finally starts.",TK87
6681,"VirtualBox Accessibility for Mac OS X Hosts Reduced, Possibly Others",Mac OS X,other,VirtualBox 3.1.8,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
16931,"Full screen mode unusable on RHEL 6 since VBox 5.0, still not fixed",Linux,Windows,VirtualBox 5.1.24,2017-09-06T05:48:25Z,2017-09-06T05:48:25Z,"This was reported previously, but the ticket has been closed as too old with no resolution. Since VBox version 5.0 the full screen mode is unusable on Red Hat Enterprise Linux. If switched to full screen mode, the screen is not painted correctly showing either the host desktop (not the guest desktop), or the host desktop is overlaid over the guest desktop. Major issue that seems to be ignored by developers. The hardware is ThinkPad W520.",Rafcio
16996,Application Error and a crash. The memory could not be read.,Windows,Windows,VirtualBox 5.1.26,2017-09-06T08:56:58Z,2017-09-06T08:56:58Z,During vm operation message box appears and VirtualBox.exe crashes.,Mik
17059,Add VM state saving compression level option,all,all,VirtualBox 5.1.26,2017-09-07T05:26:19Z,2017-09-07T05:26:19Z,"AFAIK, VirtualBox currently uses some default(?) value for libgzip(?) when saving and thus compressing running VM's RAM into disk. Sometimes it's needed to tune (as for me, to lower compression levels to compress VM state faster) the compression level. Peculiarly it's very highly desired feature when using SSD storage, where I/O bandwidth capability is super fast.

I see implementation as some global option for all VMs and custom trigger per VM configuration ""use global compression level when saving to disk"" / ""use X compression level when saving to disk"".
",maestro
17061,NVMe w/o extension pack has too generic of error message,Linux,Linux,VirtualBox 5.1.26,2017-09-07T18:12:07Z,2017-09-07T18:12:07Z,"Steps to reproduce:
- Create new Debian 64 VM using defaults for all choices
- Add NVMe controller
- Run VM and note that error message correctly indicates that extpack required but does not mention NVMe even though it does mention USB and RDP.",LNS
17062,Login screen not working on VBox 5.1.26,other,other,VirtualBox 5.1.26,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
17063,Kernel panic on Other (Android-x86-4.4*) guest,Windows,other,VirtualBox 5.1.26,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
8801,only printable Serial-Number allowed for the USB-filter,Linux,Windows,VirtualBox 4.0.6,2017-09-08T12:43:16Z,2017-09-08T12:43:16Z,"Hi, when i want to make an permanent filter for an USB-Device, which has none-printable characters, the whole VM will crash at the next startup. The failure which is shown, said that in line X a wrong value has been readed. For a workaround, the serial-number could be deleted and the VM will start. The USB-device was an ST-Link from STMicroelectronics.",BjoernC
17064,VM setting for all PC users,Windows,other,VirtualBox 5.0.24,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
17065,SEGV with plymouth on Ubuntu GNOME 16.04,Windows,Linux,VirtualBox 5.1.26,2017-09-08T14:31:53Z,2017-09-08T14:31:53Z,"When booting into Ubuntu GNOME, most of the boots are causing a SEGV in Plymouth as follows:
{{{
Aug 26 17:03:55 matthias-VirtualBox systemd[1]: Received SIGRTMIN+20 from PID 356 (plymouthd).
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Unit entered failed state.
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
}}}

Searching the Internet, I have found the issue: With the installation of the VBox Additions, it seems that the plymouth service needs to be re-configured to use the framebuffer.

After issuing the following command, I got never again a SEGV:
{{{
echo ""FRAMEBUFFER=y"" | sudo tee -a /etc/initramfs-tools/conf.d/splash && sudo update-initramfs -u -k all
}}}


I have found this information here:

https://askubuntu.com/questions/695761/plymouthd-crashes-on-startup-intel-hd-3000-15-10

So a potential solution could be to issue this command (or similar) when installing the guest additions on a Linux guest containing plymouth.",Matthias.Winker
17058,Memory protection exception on booting Ubuntu 16.04 VM,Windows,Linux,VirtualBox 5.1.26,2017-09-10T10:55:25Z,2017-09-10T10:55:25Z,"Host OS: Windows 10 64 bit, 
Processor: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (12 CPUs), ~3.5GHz
Memory: 32768MB RAM
Available OS Memory: 32692MB RAM
Page File: 9687MB used, 27869MB available

Guest OS: Ubuntu 16.04.3 amd64 desktop, new installation

Logs: https://www.dropbox.com/sh/mzdf371kdpecwcz/AAAvcNt4NIjOd4FqpqzKyrora/MemoryProtectionException1?dl=0

[[Image(https://www.dropbox.com/sh/mzdf371kdpecwcz/AAALaQqILsIp3klecoRjHd-ia/MemoryProtectionException1/ApplicationError.png?dl=1)]]

Ubuntu guest progresses to grub boot menu, then the VM crashes with memory protection exception during the early phase of Ubuntu startup.

Reproducibility: The problem happens many times in a row. If you restart VirtualBox Manager it seems to go away.

No dump yet. Enabled full dumps, will link that here next time it happens.",fviktor
17054,"Please fix virtualbox causing bsod, thx.",Windows,other,VirtualBox 5.1.26,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
17069,Virtual Box cannot create Virutal Machine of 64bits OS on Windows10 Creators Edition.,Windows,Linux,VirtualBox 5.1.26,2017-09-10T21:42:59Z,2017-09-10T21:42:59Z,"When I installed VirtualBox Ver5.1.26 or Ver5.2.0 Beta2 and tried to create new VM image of CentOS 64bit on Windows 10 64bit Creators Edition, then I could not choose any 64bits OS in each OS Version list of ""Create Virtual Machine"" dialog.

What I configure on Windows 10, can I choose 64bit OS in OS version list of ""Create Virtual Machine"" Dialog box.


 ",pioarai
17072,crash when reloading vm settings while editing USB filter,Linux,Windows,VirtualBox 5.1.26,2017-09-11T09:03:52Z,2017-09-11T09:03:52Z,"VirtualBox crashes when editing a newly added but not-yet-saved USB filter, if the vm's settings got reloaded in the mean time. This is with virtualbox-5.1 (5.1.26-117224~Ubuntu~xenial) on Ubuntu 16.04.

I could reproduce it with these steps:
- start guest (Windows 7 in my case)
- open USB settings for that VM
- add new USB device filter
- edit the new USB device filter
- while edit window is open, resize VM window
- vbox asks whether to reload settings because they changed while being edited
- yes, reload
- newly added filter disappears, but edit window is still open
- keep editing in edit window
- close edit window with ok
- crash, VM aborted:
[  732.398256] VirtualBox[3393]: segfault at 2 ip 00007f160d12e773 sp 00007ffe48efbb58 error 4 in VirtualBox.so[7f160d028000+9b7000]

I didn't test with other hosts/guests, but it may not be specific to my setup.",daniel.klauer
17077,DVD in OVF does not appear in imported VM,other,other,VirtualBox 5.1.26,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
17078,Serial ports,Windows,Windows,VirtualBox 5.1.26,2017-09-13T00:48:44Z,2017-09-13T00:48:44Z,Phisical serial port works under host OS and does not work under guest OS (Mode: Host Device). At the same time there is everithing OK in Device Manager of Guest OS (The device is working properly). Once the guest OS being launched the serial port vanishes from Host OS. Host and Guest OSes are Windows 7 SP1. I have checked with different motherboards.,MIke
13046,modifyhd --resize should not be permitted when snapshots exist,all,all,VirtualBox 4.3.10,2017-09-13T12:19:16Z,2017-09-13T12:19:16Z,"Currently, a VM with snapshots can be ""resized"" via `VBoxManage modifyhd --resize`. However, this puts the user between a rock and a hard place. The VM settings show the new size, but the guest OS does not. The VM cannot be reduced to its former size (`VBOX_E_NOT_SUPPORTED`). The snapshots cannot be deleted. Basically, the program claims the snapshot is being deleted, then when that dialog disappears, all VMs say ""Information Unavailable"" and the Settings windows are blank. When !VirtualBox Manager is restarted, all the VMs are fine again, but the snapshot still exists.

The issue is irreversible. The only solution I've found thus far ([http://www.codereactor.net/changing-size-of-virtualbox-disks-before-and-after-deleting-snapshots/ here]) is to clone the VM without also cloning the snapshots, assign a new UUID to this disk (another issue), and proceed from there. 

This issue has existed for many years, yet remains completely undocumented. Furthermore, because it is not mentioned in the User Guide or the numerous blog posts outlining how to expand a VM, the only way the user will discover it is when they search for information //after// they've done an irreversible procedure. 

This is essentially a duplicate of ticket:9103. However, I felt the need to open a new ticket because that ticket and its specified version are over 3 years old, no support activity has occurred in over 3 years (though 1 user commented on it recently), and the issue has yet to be addressed. At the very least, this caveat should be documented under section 8.23 of the User Manual.",skittleys
10818,modifyhd --resize should warn users about existing snapshots,other,other,VirtualBox 4.1.18,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
17051,Caps Lock key being remapped in Linux guest can cause the mapping to malfunction,Linux,Linux,VirtualBox 5.1.26,2017-09-13T12:53:46Z,2017-09-13T12:53:46Z,"When Colemak is set as the default keyboard layout and Shift+Shift is mapped to serve as a Caps Lock (e.g. with ""setxkbmap -option shift:both_capslock""), Shift+Shift also starts working as Backspace for a little while.",GeneralFailer
9103,modifyvm --resize doesn't work with snapshots,Linux,other,VirtualBox 4.0.8,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
8324,Windows Host shutdown -any guests running stop windows from shuting down correctly,Windows,Windows,VirtualBox 4.0.2,2017-09-13T19:46:44Z,2017-09-13T19:46:44Z,"Is there a way to improve the shutdown of guests on a windows host which is performing a shutdown / reboot.

the only way to reboot a windows host (ie for windows updates) is to use vboxtray which detects the reboot and auto-saves state of the guests...

I'm running 2 guests on a windows server which I can only get to remotely... as soon as I issue a restart (or windows udpates do) it kills my remote connection but the server is left hanging there as it cannot shutdown the guest's running on it. I end up having to get someone to manually click close / force reboot etc,etc to get the host server to shutdown / reboot.

the server can reboot / shutdown automatically for various resaons such as a UPS shutting the server down after a power cut...

as I say vboxtray manages to just about get round this by auto-save state but surely virtualbox host or guest apps could do with a settings that detects host shutdown (whether guest is in GUI or headless mode) and does a save state as a default and helps the windows host do a clean shutdown / reboot???


I have this problem on all version of VB since I started using it on 3.2.6 and I've tried it on different HOST machines - win xp pro, win 7 biz, server 2003 64bit.

Without vboxtray we wouldn't have a get round solution, which sort of works but I find that vboxtray sometimes closes on the tray so can fall over too sometimes.

can this be added as a feature request for windows hosts please

many thanks",Jimbo
16118,Ubuntu 16.04.1 crash of UI,Linux,other,VirtualBox 5.1.8,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
17071,Random memory reading errors on Windows XP VMs,Windows,Windows,VirtualBox 5.1.26,2017-09-14T17:15:32Z,2017-09-14T17:15:32Z,"Hello.

When I set a Windows XP VM, it crashes randomly (after setup, when installing Guest additions) with the message ""The instruction at 0x0000... referenced memory at 0x00000... the memory could not be read"".

Tested with 2 different Windows XP ISOs : Same problem
Tested on another Windows computer host : Same problem
Updated the graphics card driver to the latest version : Same problem
Tested with all antivirus softwares uninstalled : Same problem

Both of the hosts OS is Windows 10 Pro v.1703 x64",Kakoussnight
17081,VM virtual hard disk deleted,other,Windows,VirtualBox 5.1.26,2017-09-15T08:19:06Z,2017-09-15T08:19:06Z,"Hi,

I installed the latest Windows update (Windows 7 is my guest OS) and an update of the VirtualBox expansion pack this morning. After restart, the majority of my VMs were shown as inaccessible. When I checked, the hard disk files were not present. I looked at the VirtualBox logs and I can see VirtualBox doing the deletion in the logs. I never requested this deletion. Fortunately I have backups. Log files will be attached.
Thanks!
Jean",Zed
15513,VM stuck when attempting to open a Microsoft Office file from network,Linux,Windows,VirtualBox 5.0.22,2017-09-15T08:50:52Z,2017-09-15T08:50:52Z,"When you try to open a document from a network share the entire VM is stuck. The log report:

00:12:18.795744 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago",Panos Kavalagios
16901,Non-driver certificates not handled correctly by hardening (OpenText SOCKS),Windows,Linux,VirtualBox 5.1.22,2017-09-15T13:22:10Z,2017-09-15T13:22:10Z,"I had originally raised an issue with OpenText socks that theri DLL was not signed and so did not work with VirtualBox. They have now provided a signed version, but it is not signed with a driver certificate. According to OpenText support VirtualBox is not handling the signing check correctly. Some of my correspondance with OpenText support pasted below.

----------------------------------------------------------------------------
---- From OpenText Support -----

Hello Lars,

In regards to ticket #3056978, I received input from Engineering.  This issue appears to be related to the third party application.

According to Engineering: 
If you used signtool, it would show DLL is properly signed.  Note, using the default option, will show a trust error because the default assumes driver signing and this is a not a driver with signed catalog file.  You need to use /pa argument for the signing to show as valid.  Since you use SigCheck (Sysinternals), you do not need to use any parameters to show the DLL is signed

C:\Users\xx>sigcheck64 ""c:\Program Files\Open Text\SOCKS Client\*"" > C:\xx\sigcheck_socks.14.0.16.txt

(Refer to the output in the attached file.)
 

The root issue is that Virtualbox process will have HumSOCKS.dll injected into its process space (this is simply how SOCKS works on Windows).  On startup it does a complicated self-validation on itself and all loaded DLLs in the main process space.  Essentially the rules force that all DLLs need to be signed properly (or a couple of other exceptions for specific location and owner of file).  It appears that their code fails the same way that signtool does without the /pa flag and ultimately will not start up when we are in their process space because of that.  In one sense this is correct behavior because there's no signed catalog file for us at all but it's definitely unwanted because it should not apply that logic for 3rd party dlls that are not drivers.

This appears to be a long standing issue with VirtualBox - check out https://www.virtualbox.org/ticket/13659.  The corrupted path it starts out as is not a problem for us but the exact same issue with failed trust for a correctly signed DLL is the main issue left.

Regards,
OpenText Support



---- From me to OpenText Support ---
To: support@opentext.com
Subject: Re: FW: OTCS Ticket 3056978 Socks 14:  VirtualBox does not work when SocksClient is installed

Hi, I have tried your recommendation of importing the certificate. I also tried disabling the virus scanner. I also tried importing the intermediate certificate and tried loosening some policy settings, but nothing solves the problem. SHA-256 certificates show up fine in Windows and the patch required for support is installed.   The error I'm getting in the VBoxHardening.log is:

{{{
14a4.1a9c: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll) WinVerifyTrust
14a4.1a9c: Error (rc=0):
14a4.1a9c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll: None of the 1 path(s) have a trust anchor.: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll 
14a4.1a9c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll
14a4.1a9c: Error (rc=0): 
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll' (C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll): rcNt=0xc0000190
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll'
}}}",Lars Hupfeldt
17094,Won't install on Ubuntu 16.04,Linux,all,VirtualBox 5.1.28,2017-09-18T14:22:06Z,2017-09-18T14:22:06Z,"I downloaded the package for Ubuntu 16.04 from http://download.virtualbox.org/virtualbox/5.1.28/virtualbox-5.1_5.1.28-117968~Ubuntu~xenial_amd64.deb

By double-clicking on it it opens with Ubuntu Software Whatever, an ""install"" button shows up. That doesn't work, https://forums.virtualbox.org/viewtopic.php?f=1&t=84623&sid=255ddb223689adba4a433f51a9e7500d&p=401997#p401997it just shows a progress bar for a fraction of a second and then the button appears again, it does nothing, gives no error message. But that probably is a bug in Ubuntu.

So in a terminal I did:
{{{
$ sudo apt install ./virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb 
}}}
And this is the output:

{{{
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'virtualbox-5.1' instead of './virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb'
The following packages were automatically installed and are no longer required:
  fonts-horai-umefont fonts-unfonts-core libgif7:i386
  libp11-kit-gnome-keyring:i386 linux-headers-4.4.0-79
  linux-headers-4.4.0-79-generic linux-headers-4.4.0-83
  linux-headers-4.4.0-83-generic linux-headers-4.4.0-89
  linux-headers-4.4.0-89-generic linux-headers-4.4.0-91
  linux-headers-4.4.0-91-generic linux-image-4.4.0-79-generic
  linux-image-4.4.0-83-generic linux-image-4.4.0-89-generic
  linux-image-4.4.0-91-generic linux-image-extra-4.4.0-79-generic
  linux-image-extra-4.4.0-83-generic linux-image-extra-4.4.0-89-generic
  linux-image-extra-4.4.0-91-generic linux-signed-image-4.4.0-79-generic
  linux-signed-image-4.4.0-83-generic linux-signed-image-4.4.0-89-generic
  linux-signed-image-4.4.0-91-generic ocl-icd-libopencl1:i386 odbcinst
  odbcinst1debian2 p11-kit-modules:i386 p7zip unixodbc wine-gecko2.21
  wine-gecko2.21:i386 wine-mono0.0.8 winetricks
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libsdl-ttf2.0-0
The following NEW packages will be installed:
  libsdl-ttf2.0-0 virtualbox-5.1
0 upgraded, 2 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B/66,0 MB of archives.
After this operation, 163 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /home/teo/Downloads/virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb virtualbox-5.1 amd64 5.1.28-117968~Ubuntu~xenial [65,9 MB]
Preconfiguring packages ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 454844 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.1.
Preparing to unpack .../virtualbox-5.1_5.1.28-117968-Ubuntu-xenial_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.28-117968~Ubuntu~xenial) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.1 (5.1.28-117968~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
depmod: ERROR: could not open directory /lib/modules/3.19.0-30-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/3.8.0-19-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.2.0-30-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
Processing triggers for libc-bin (2.23-0ubuntu9) ...
}}}",teo8976
17000,Cumulative update for Windows 10 1703 broke Virtualbox VT-x recognition,Windows,Linux,VirtualBox 5.1.26,2017-09-18T19:17:38Z,2017-09-18T19:17:38Z,"On 2017-0809 around 1700EDT I upgraded my laptop with a security update for Windows 10 (https://support.microsoft.com/en-us/help/4034674/windows-10-update-kb4034674) and a security update for Adobe Flash player for windows 10 (https://support.microsoft.com/en-us/help/4034662/security-update-for-adobe-flash-player-aug-08-2017).

The following morning I attempted to power up my VM that has been running without major hiccups since mid July and got the following failure code:

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Online searches revealed that this type of problem has been encountered before.

1. https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios

I tried 
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and rebooted but problem persisted.

2. https://stackoverflow.com/questions/5482223/vt-x-is-not-available-when-i-start-my-virtual-machine

I reduced my VM's memory footprint below 4096 but when I powered it up I got a Win10 BSOD

3. https://forums.virtualbox.org/viewtopic.php?f=6&t=58820

I ran
c:\Program Files\Oracle\VirtualBox>VBoxManage.exe modifyvm CentOS-Adva-Dev --longmode off

without any noticable effect on this problem.

I confirmed my laptop's virtualization support is enabled in the bios settings.

I attempted to create another VM and noticed that my only VM guest types are 32 bit. 

I attempted to run an installation repair to my VirtualBox 5.1.26 installation without any success.

I have not tried:
1. Uninstall and reinstall VirtualBox application on my host - I have no reason to believe that this will resolve the issue

2. Rolling back the Windows security updates - this action probably carries more risk than reward.

",edwaldner
17068,AVG installation locks up Virtual Box version 5.1.26,other,other,VirtualBox 5.1.26,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
3500,Auto startup and shutdown for VMs,Linux,other,VirtualBox 2.1.4,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
17097,After drag and droping files from guest to host the cpu usage of the guest additions tray application skyrockets without any sense,Windows,Windows,VirtualBox 5.1.26,2017-09-19T09:52:31Z,2017-09-19T09:52:31Z,"Sometimes after copy some files per drag and drop from the guest to the host the CPU usage of the guest additions tray application skyrockets without any sense, because the files are copied and it is doing anything else (s. screenshot).
I was looking for the log files of the guest additions tray application, but I couldn't find any.",spamme2
17027,Installing VirtualBox Guest Additions in Windows 7 does nothing,Linux,Windows,VirtualBox 5.1.26,2017-09-19T15:14:48Z,2017-09-19T15:14:48Z,"NOTE: I already raised this issue in the forum. No luck, nevertheless. The thread is https://forums.virtualbox.org/viewtopic.php?f=2&t=84071&p=399327#p399327

My host is a 8GB Ubuntu 16.04 running VirtualBox 5.1.26. I have been running a Windows XP guest without problem for the last eight years.

I upgraded my host OS and I don't want to dual boot anymore (Ubuntu/Windows 7), so I copied the relevant harddisks partitions to a VDI image. After messing around a bit with ""fdisk"" and ""grub"", I am successfully booting Windows 7 as a guest. Slow running but Nice!. It is a Windows 7 x86-64 guest.

I proceed to uninstall most HP, Adobe, etc, crap, even the ATI video driver, the WIFI driver, etc. I reboot Windows 7 guest and everything works fine except sound (disabled) and network (drivers uninstalled). I insist that windows works fine, although harddisk performance is not stellar. I disabled Security Esencials and Windows Defender too.

After rebooting one more time, I install ""VirtualBox Guest Additions"" . Install finishes correctly and prompts to reboot. I reboot... and Windows 7 guest is working fine but... with no ""VirtualBox Guest Additions"", Nothing seems to happen. Host integration is not working and VirtualBox says that there are not guest additions running in the guest. I repeat install (it goes fine) and reboot. Same thing.

Checking the guest harddisk, I see ""VirtualBox Guest Additions"" directory with 19 files inside the ""C:/Program files"" directory. Everything seems ok. But the virtual machine is not enabling the Guest Additions.

I wonder if this is a Windows 7 32/64 issue but I lack the knowledge to debug this issue myself.

Please, Help!

Thanks in advance!.",jceajcea
17099,Shared clipboard : bidirectional mode causes host clipboard malfunctions,Windows,Linux,VirtualBox 5.1.28,2017-09-19T17:33:33Z,2017-09-19T17:33:33Z,"Windows 10 host
Linux (Ubuntu 16.04) guest

When the Shared Clipboard is set to Bidirectional, the following issues manifest on the Windows 10 host:

* In Excel, copy cell, paste to multiple cells (select range of cells and paste) does not work
* In Office applications, copy/paste of formatted text does not work; only the text is copied

If Shared Clipboard is set to any of the other three options (Disabled, Host to Guest, or Guest to Host) then the problem does not manifest itself and the above functionality works properly.

This is reproducible at will.

I also noticed this issue on a Windows 7 host running a Linux VM.",Studio
17088,Crash when trying to access SMB network shares under evaluated user,Windows,Windows,VirtualBox 5.1.28,2017-09-20T08:18:21Z,2017-09-20T08:18:21Z,"Issue came with update 5.1.26 to 5.1.28.

Guest: Windows 10 Pro 1703
Host: Windows 10 Pro 1703 as well as Windows 7

Crash in the guest system only with the evaluated user, so it might be related to the others issues which Windows 5.1.28 guest extensions has with evaluated users. No problem with standard user. 

The crash is that after login for accessing the SMB shares the explorer terminates. Doing this with another file manager (total commander 9.0a), the file manager hangs. No SMB access for the evaluated user possible.",Denis.L
17102,Virtual Box does not list Virtual USB device (created by fallocate),other,other,VirtualBox 5.1.28,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
17103,Mouse direction locked in opengl programs,Windows,Linux,VirtualBox 5.1.28,2017-09-21T04:51:24Z,2017-09-21T04:51:24Z,"Host Win10, Virtual box 5.1.28 with Ubuntu 16.04 installed.
After install the VBoxGuestAdditions, when i start an opengl Application, the mouse lost control, just pointting to the sky.
When I tried to move left/right, the picture just rotate, not looking around.",ffpwserver
17096,Stuck error after Guest Addition CD install,Mac OS X,Windows,VirtualBox 5.1.28,2017-09-21T12:45:19Z,2017-09-21T12:45:19Z,"File System error (-1073741819)

Administrative privilege got lost after Guest Addition CD installation for VirtualBox 5.1.28 r117968 (Qt5.6.2).
Opening cmd.exe in administrator privilege runs smoothly before installing Guest Addition CD, but it returns error above after the installation.

MSEdge on Windows 10 x64 Stable (15.15063) for VirtualBox",HeavyLight
17083,Virtualbox Graphics Adapter for Windows 8+ incompatible with Skype For Business 2016,Windows,Windows,VirtualBox 5.1.28,2017-09-21T12:46:04Z,2017-09-21T12:46:04Z,,FrankW
16702,Virtual Box in Full screen mode can't switch to other virtual desktop,Linux,Linux,VirtualBox 5.1.20,2017-09-22T08:19:46Z,2017-09-22T08:19:46Z,"I am running Linux Mint 18.1 x64 and noticed after upgrading VirtualBox from 5.1.18 to 5.1.20 that when I enter VBOx full screen mode running Ubuntu 16.04 Desktop with fallback installed as guest that I can't switch to other virtual screen using keyboard shortcuts. My short cut was ""Control+Alt+ArrowKeys. This used to work in 5.1.18. When I exit full screen mode and just maximize VBox window it still works. Something I noticed that when in full screen mode when I try to switch virtual screens with above keyboards shortcuts I see for split of a second ""sliding"" like it is trying to do so but then it snaps back to VirtualBox on same screen. So my setup is 3x3 virtual screen setup. So if I enter full screen mode (first row third column) and try to switch to left I see for split of a second 2nd desktop about 5% or it before it snaps back to VirtualBox. I also see Mint 3x3 preview window overlay ed over Virtual box indications all configured screens. But I can switch. I have fairly recent update but this starts happening after Virtual box upgrade. I did reinstall guest tools as well",oxoocoffee
17107,"Hello, Today I just upgrade my Vbox, and now I can't open the software. Need Help",Windows,Windows,VirtualBox 5.1.28,2017-09-22T14:23:00Z,2017-09-22T14:23:00Z,"Fallo al abrir una sesión para la máquina virtual Siemens Win 7 64 bit.

The device helper structure version has changed.

If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH).

Código Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Rocko
17108,Virtualbox 5.1.28 running under Windows 10 corrupts clipboard copy & paste,Windows,Linux,VirtualBox 5.1.28,2017-09-22T16:16:06Z,2017-09-22T16:16:06Z,"Performing Windows cut & paste operations (using Ctrl+c/Ctrl+v) between VirtualBox VM and Windows frequently corrupts Windows clipboard... VirtualBox 5.1.28 r117968, Windows 10 Pro (v1703 OS Build 15063.608), RHEL 6.9 VM.

Once corruption occurs, pasting between Windows applications such as Notepad, Word or Outlook Email exhibit pages of non-printable characters. Eventually Windows 10 mouse clicks used to switch between applications stop working, Windows taskbar crashes (and won't restart), Desktop background goes black, and Windows becomes non-functional without being rebooted. Ctrl+Alt+Delete still functions and Windows Task Manager runs normally. Task Manager allows switching between applications and doing normal Windows shutdown.",Jayb
17109,"5.1.28 - after upgrading guest additions, teamviewer 12 becomes unstable in Win 7 64-bit guest",Linux,Windows,VirtualBox 5.1.28,2017-09-22T16:36:19Z,2017-09-22T16:36:19Z,"upgraded virtualbox 5.1.26 on xubuntu 16.04.3 to version 5.1.28, and upgraded guest additions simultaneously on Win7 64-bit Guest. Noticed that Teamviewer 12 started crashing (""TeamViewer 12 has stopped working"") intermittently, but most often when manipulating TV controls and reliably when ending the TV session.  Bringing Windows patches up-to-date and updating Teamviewer had no effect.

I have another VM with Teamviewer as an ""emergency spare"" (both machines were cloned from a common ancestor).  I did not update the guest additions (remained at 5.1.26), and the same (non-updated) version of TeamViewer worked as normal.  Immediately after updating the Guest Additions to 5.1.28, and re-connecting with the same remote Teamviewer host, Teamviewer began crashing as on the other VM.",BISISysadmin
17100,Machine inaccessible after snapshot deletion,Linux,Windows,VirtualBox 5.1.28,2017-09-22T18:33:09Z,2017-09-22T18:33:09Z,"Deleting second-to-last snapshot corrupts the VM, leading to machine inaccessible - line 9 - current snapshot missing.  This problem began with release 5.1.26 or before.  It occurs with 5.1.28 and also with 5.2.0_BETA3, which I'm running now.  Everything works fine before the snapshot deletion, including the ability to take a new snapshot.  The only way I know to recover is to restore the entire VM from backup.",kingfisher289
17110,d3d9.dll error/Starting Quicken2015/Starting Adobe Acrobat Reader/OSX Host/Win 10,Mac OS X,other,VirtualBox 5.1.28,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
15774,VirtualBox incorrectly counts processors on AMD products,Windows,Linux,VirtualBox 5.1.2,2017-09-24T05:21:17Z,2017-09-24T05:21:17Z,"VirtualBox incorrectly counts processors on AMD products.  I have an AMD CPU with 8 physical processors.  This processor has 8 full processor cores.  Evidently, VirtualBox assumes this processor is an Intel product with Hyper-Threading, but this assumption is not correct.
",Kriston
13697,4.3.20 doesn't start virtual machines any more (supHardenedWinVerifyProcess failed),Windows,Windows,VirtualBox 4.3.20,2017-09-25T14:30:00Z,2017-09-25T14:30:00Z,"Hi,
yesterday I upgraded from 4.3.12 to 4.3.20 r96997 and every virtual machine on my Win7-32bit SP1 Enterprise Host hangs on startup with this messages (see screenshots):

Error in supR3HardNtChildPurify:
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc=-5673)

I executed KB3024777-x86.exe to remove KB3004394 but it doesn't seem to do anything. In system control, programs, ""installed updates"" I can't find KB3004394.

[[Image(http://abload.de/img/1jgahq.png)]]
[[Image(http://abload.de/img/2hpbct.png)]]

It would be great to get some help on this issue!
If you need any further information about it I'll provide it:-)
Thanks in advance.",JackyRyan
16542,Windows 10 Insider - Not booting correctly with GA Video Driver,Linux,Windows,VirtualBox 5.1.16,2017-09-26T10:30:50Z,2017-09-26T10:30:50Z,"As reported in https://www.virtualbox.org/ticket/15973
Using Fedora 25.
Just upgraded to VirtualBox 5.1.16.
Installed GA 5.1.16
Guest Settings:
2D Acceleration enabled
3D Acceleration disabled

Windows 10 refuses to boot, with the Video driver installed. After two tries, using Basic Video Driver works.

Relevant lines from log file (also attached):

{{{
00:00:07.649607 RTC: period=0x200 (512) 64 Hz
00:00:07.689199 VBVA: InfoScreen: [0] @0,0 3840x2025, line 0x3c00, BPP 32, flags 0x1
00:00:07.689219 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f9078000000 w=3840 h=2025 bpp=32 cbLine=0x3C00 flags=0x1
00:00:07.689250 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=3840x2025, Sending to async-handler
00:00:07.689364 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=3840x2025
00:00:07.689375 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=3840x2025
00:00:07.689620 GUI: UIFrameBufferPrivate::performResize: Size=3840x2025, Directly using source bitmap content
00:00:07.694329 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc0000005 P2=0xfffff807d604e92b P3=0xffff8c0106b45cd8 P4=0xffff8c0106b45510
00:00:09.134352 NAT: Link up
00:00:10.146743 AHCI#0: Reset the HBA
00:00:10.147380 AHCI#0: Port 0 reset
00:00:11.354005 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:00:20.399165 GIM: HyperV: Reset initiated through MSR
00:00:20.399202 Changing the VM state from 'RUNNING' to 'RESETTING'
}}}

Enabling 3D Acceleration gives a ""System Exception Thread not handled"" error.",bhahlen
16898,excel 2002 crashes upon close on win7 guest in VB 5.1.22 r115126 (Qt5.6.1) on ubuntu 14.04,Linux,Windows,VirtualBox 5.1.22,2017-09-27T04:13:01Z,2017-09-27T04:13:01Z,"host os ubuntu 14.04 LTS 64 bit
virtualbox Version 5.1.22 r115126 (Qt5.6.1)
guest os win 7 pro ver 6.1 build 7601 service pack 1
excel 2002 (10.6871.6870) sp3

On close or exit win7 reports excel crashed.
This crash happens every time.

The VB log file has no indications at all for this event.

Win7 reports:
Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	EXCEL.EXE
  Application Version:	10.0.6871.0
  Application Timestamp:	4daf71c5
  Fault Module Name:	TFSOfficeAdd-in.dll
  Fault Module Version:	15.112.26313.0
  Fault Module Timestamp:	58c6a842
  Exception Code:	c0000005
  Exception Offset:	0000f27a
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  LCID:	1033

",oldunixguy
4656,USB device is busy with a previous request,Windows,Linux,VirtualBox 3.0.2,2017-09-27T15:32:17Z,2017-09-27T15:32:17Z,"Windows XP host and Fedora 11 guest. After a crash while transferring a huge amount of files between the pen drive and the Fedora guest, the pen drive becomes unavailable. When clicking Devices -> USB Devices -> Device Name this message is shown:

""Failed to attach the USB device xxx to the virtual machine Fedora 11
USB device xxx with UUID yyy is busy with a previous request. Please try again later.

Details:

Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDevice
Interface: 
IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: 
IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}
""

Forum discussion topic:

http://forums.virtualbox.org/viewtopic.php?f=6&t=20744&start=0#p89540",Clodoaldo Pinto Neto
16459,Cannot change Virtual Screen from Host screen 1 to 2 in Fullscreen mode,Windows,Windows,VirtualBox 5.1.14,2017-09-28T04:06:13Z,2017-09-28T04:06:13Z,"Host: Windows 10 Pro x64 with 2 monitors

Guest: Windows 7 Pro x64

When in Full-screen mode, I used to be able to change from monitor 1 to monitor 2 and vice versa by going to View > Virtual Screen 1 > Use Host Screen 1/Use Host Screen 2. 

I believe since v5.1.12, I have to complete the previous step, exit reenter the Full-screen mode to switch the guest display to the other monitor.",Anh Le
16857,VBoxNetAdp.kext conflict with tap.kext on macOS,other,other,VirtualBox 5.1.22,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
17115,X of guest freezes with 3D acceleration enabled,Windows,Linux,VirtualBox 5.1.28,2017-09-28T11:11:49Z,2017-09-28T11:11:49Z,"Hello.

I found that X seems to freeze after login to my Ubuntu 16.04 if 3D acceleration is enabled. The screen is not updating, the mouse cursor moves as it should and I can Ctrl+Alt+F1 to a TTY (and back).

If I change screen resolution by pressing Host+F, I get garbage that remains there even if I change the resolution back to full-screen.

I think this might be related to the closed issue #13487 because the symptoms sound similar.

My Ubuntu 16.04 is up to date and so are the guest additions. The host is Windows 10.

Cheers,

Jan",Jan P.
17120,Installation of 5.1 & 5.2 Beta failing for Windows 10 Pro,Windows,other,VirtualBox 5.1.28,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
4208,Command-Q not passed to client OS,Mac OS X,Linux,VirtualBox 2.2.4,2017-09-30T06:44:01Z,2017-09-30T06:44:01Z,"
Certain key combinations are not being passed through to the client OS. 

Usecase: Command-Q (in X11 as Meta-Q) to quit an application in the client OS results in the  ""Close virtual machine"" dialog (and leads to a 'stuck' command key modifier after dismissal, until meta is pressed again).

Also see Command-H for another example of this problem

http://www.virtualbox.org/changeset/1320 describes a fix, but from what I can tell has either not been applied, or does not work.

Partially related to Ticket #1668, but currently the exhibited behaviour is inconsistent with the behaviour of other keyboard combinations (i.e. pass everything to the client) - 1668 describes how passing through these key combos, if _optional_, may still be useful to some.",Gil Pinheiro
17124,Host Hard not recognized,other,other,VirtualBox 5.1.28,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
17126,keyboard mouse not functional on host after dock(or unplug/plug mouse/kb),Mac OS X,Linux,VirtualBox 5.1.28,2017-09-30T17:24:00Z,2017-09-30T17:24:00Z,"Steps to reproduce:

1. Host has usb mouse plugged in.
2. Run VBox. Start VM.
3. Notice mouse still works on host.
4. Unplug, replug mouse
5. Notice Mouse is now not functional on host.
6. Notice Mouse is now grabbed by Virtualbox and passed to VM, though no filter exists.
Note mouse/keyboard grabbed with no filter or even when filter is created and disabled.

Expected behavior:
5. Mouse not grabbed by Vbox unless filter is created and enabled.

This is greatly undesirable for docking scenarios.  If vitualbox is running and laptop is undocked/docked.  Mouse/keyboard are not functional.  Only apparent workaround is open up laptop use touchpad to manually disable grabbed mouse/keyboard or save and re-run VM.

Reproduces on 5.1.28, 5.1.29 r118065, and previous versions.",donemo
17123,Regular freezing of (windows 7) guest on macosx host (high sierra),Mac OS X,Windows,VirtualBox 5.1.28,2017-09-30T17:28:28Z,2017-09-30T17:28:28Z,I develop in a windows 7 guest system with java and eclipse. For several weeks now the guest freezes after an arbitrary time. After minimalising and restoring the guest window it shows the state as it had when the guest freezed. The same I had with 5.1.26 too. It is similar to reported ticket 8511.,chrigel
17121,BSOD after launching VM,Windows,Windows,VirtualBox 5.1.28,2017-10-02T08:11:17Z,2017-10-02T08:11:17Z,"Hello,

Recently I've upgraded VirtualBox from 5.0.20 to 5.1.28 version. Unfortunatelly it caused that after launching VM appears blue screen; it is possible to launch VM in safe mode, but normal mode crashes. I' ve tried to back to my prior version, but it didn't help; reinstall VirtualBox and change VM settings in many different ways also didn't help. Host is Windows 7 64-bit; guest is Windows XP 32-bit. Interestingly I' ve set this host image on other guest, Windows 10 32-bit on VirtualBox 5.1.10 and it run, but on Ubuntu 32-bit and 64-bit not. Please give me a hint what I have to do to solve this issue.",Skywanter
17118,virtualbox nataliasmode proxyonly breaks local network connectivity on windows 10,Windows,Linux,VirtualBox 5.1.28,2017-10-02T14:42:29Z,2017-10-02T14:42:29Z,"Hi,

I have enabled proxyonly for the nat and now for the entire local network i am unable to access the guest machine in any of the protocols. thoouh it is accessible from the internet.

Thanks,
Vipin",Vipin Jain
17113,Can't reboot after changing windows 10 display resolution on ubuntu-16.04 and virtualbox-5.1.28,Linux,Windows,VirtualBox 5.1.28,2017-10-02T15:40:15Z,2017-10-02T15:40:15Z,"
After changing windows 10 display resolution, I encountered boot fail of windows 10 vm.
I's using virtualbox-5.1.28 and ubuntu-16.04. And I've installed vargrant-2.0.0 but I didn't use it.

I found following error messages from VBox.log but I can't figure out any clues.

1111 00:00:00.337951 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aCompo     nent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
1112 00:00:00.343556 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aCompo     nent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0

",edward.lee
17132,VRDP crashing guest machine,Linux,Windows,VirtualBox 5.1.28,2017-10-03T14:07:02Z,2017-10-03T14:07:02Z,"Hello,

Have some problems with Win7/64 machines on Linux/64 host. There are several VM on one host with VRDP activated. Only 4-6 are running in parallel. The problem is a VM crashing when trying to use VRDP. Sometimes it happens with a first try, sometimes on one of the next. When crashed, VM does not give any messages in own log file, any clue in VBoxSVC.log, the only one is in /var/log/messages/kern.log

Oct  3 12:18:49 s07 kernel: [49758.816603] VRDP-IN[32682]: segfault at 0 ip           (null) sp 00007f83e6bfcb30 error 14 in VBoxHeadless[400000+25000]

When possible I'll try to catch core dump - it is productive machine, I'll be able to do so in the evening.",vinyl
17134,Arch Linux - kernel 4.13 video problems,other,other,VirtualBox 5.1.28,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
16448,VBoxHardening issue (AV software),Windows,Linux,VirtualBox 5.1.14,2017-10-04T09:15:23Z,2017-10-04T09:15:23Z,"Windows 7 Enterprise SP1
Virtual Box 5.1.10 was working fine until company pushed an update to my workstation.

I think the issue is related to Cylance Protect as that software seems to have been updated the day VB broke.
It's also possible kernel32.dll was updated by a windows update.

Error starting ALL VMs..

The virtual machine 'DeleteMe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\MyProfile\VirtualBox VMs\DeleteMe\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


The workstation/host has Cylance Protect and Symantec Endpoint Protection enabled (and I can't disable them to test).

I tried test builds.

5.1.10 original had the issue.
5.1.14 - same issue
5.1.15 - test build same issue.
5.1.51 - dev build same issue

",gingleby
17138,Changes to VMDK image on USB Storage Not Preserved,Windows,other,VirtualBox 5.1.28,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
17141,"Guests hang in ""restoring snapshot"" or ""deleting snapshot""",other,all,VirtualBox 5.1.28,2017-10-05T17:30:02Z,2017-10-05T17:30:02Z,"On an Arch Linux host, after running some VirtualBox-related maintainence scripts that do things such as take and restore snapshots, I observe that several virtual machines are in strange states.  None of the machines are active.

{{{
deb8: ""Restoring Snapshot""
fedora: ""Aborted""
theodore: ""Deleting Snapshot""
ubu12-32: ""Deleting Snapshot""
win10x64: ""Powered off""
}}}

This happens fairly often for me.  I will attach stacktraces.",plujon
17142,Virtual machine crashed while installing IBM Maximo,Windows,Windows,VirtualBox 5.1.28,2017-10-06T09:13:04Z,2017-10-06T09:13:04Z,"I'm hoping somebody can help me figure out this problem. I created a Windows 2012 Server as a guest and tried to install IBM Maximo and the VM crashed.  The log and png file are attached.

I am using VirtualBox v5.1.28 on a older Windows 7 system with 32Gb of RAM.",Al Menendez
17143,Windows 10 BSOD if Guest OS started,Windows,Linux,VirtualBox 5.1.28,2017-10-06T09:47:15Z,2017-10-06T09:47:15Z,"Hello.
If I start guest operation system - I tried FreeBSD, Ubuntu, my laptop got BSOD. Windows 10 Enterpise  1703 (OS Build 15063.384). I made searh about this type of issues - WTx - instructions enabled in BIOS and HYPER-V uninstalled.
",lvesel
17144,Direct3D11.1 crashes,Windows,Windows,VirtualBox 5.1.28,2017-10-07T10:38:48Z,2017-10-07T10:38:48Z,"Dear Sirs!

I have a platform:
Host is a Windows 10 Creators Update.
Virutal PC has Windows 8.1 Up to Date.
DirectX applications are crashing in this configuration.
It is possible to create a Direct3D11.1 and its Context.
Releasing the device throws an hardware exception (bad pointer).
I can not use the DXDiag.exe, it crashes also.

[[Image(https://www.kubera.info/ms/2017-10-07.png)]]",kubera
17145,E_FAIL (0x80004005) SessionMachine,Windows,Windows,VirtualBox 5.1.28,2017-10-08T13:53:54Z,2017-10-08T13:53:54Z,"Не удалось открыть сессию для виртуальной машины BOT.

The VM session was aborted.

Код ошибки: E_FAIL (0x80004005)
Компонент: SessionMachine
Интерфейс: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

",free0n
17147,VirtualBox doesn't work and can't finish reinstall,Mac OS X,all,VirtualBox 5.1.28,2017-10-09T08:52:07Z,2017-10-09T08:52:07Z,"After I upgrade my macbook pro(2015mid) to High Sierra, the virtualbox does not work any more. When i start a vm, it alarted ""Kernel driver not installed (rc=-1908)"". And when I reinstall virtualbox with pkg, (with or without VirtualBox_Uninstall.tool), the progress failed near finish. install log in attach.
Reinstall High Sierra (without format disk) doesn't help.
No Button appare in Security & Privacy when installation failed.
I found some simular question in tickets and forum, but the solutions does not work at all...",ply_xyz
17133,Direct3D 7 Failure at step40 - NVIDIA GTX460,other,other,VirtualBox 5.1.28,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
17151,Crashes with critical error when trying to start Window 7 32-bit in Windows 7 64-bit,Windows,Windows,VirtualBox 5.1.28,2017-10-10T09:13:01Z,2017-10-10T09:13:01Z,"""A critical error has occurred while running the virtual machine and the machine execution has been stopped"" 

Yesterday it ran correctly until now. I tried to start the system and when the Windows logo disappears the message appears.",Francisco Gonzalez
16870,VB 5.1.22 Aborts and issues running Outlook 2016 on Windows 10 Guest,Linux,Windows,VirtualBox 5.1.22,2017-10-10T16:45:53Z,2017-10-10T16:45:53Z,"I get sudden aborts of VB 5.1.22 r115126 running a windows 10 guest on a Linux Mint 18.1 Cinnamon 3.2.7 machine.

First, I must run Outlook 2016 in safe mode ""outlook.exe /safe"" or outlook will immediately go into ""Not Responding"" and never recover.  This is Outlook connected to company Exchange server and Windows 10 guest is joined to domain.

Typically see crash when copying items from host to paste into new email open in guest.

Nothing in Oracle VB logs to indicate why the crash happens, and not seeing anything relevant in Linux logs.",Paul Allen
17153,Blue screen when starting Windows 7,Windows,Windows,VirtualBox 5.1.28,2017-10-10T17:02:52Z,2017-10-10T17:02:52Z,"Blue screen when starting Windows 7. After 4 or 5 restarts ok. 
When shutting down a report of a serious error appears. Contact support.",stback
17157,100% CPU usage (windows 10 VM) running on WIndows 10 VM,Windows,Windows,VirtualBox 5.1.28,2017-10-11T16:55:55Z,2017-10-11T16:55:55Z,"I've recently moved 2 virtual PCs from a windows 10 PC to another windows 10 Pc. They have the same hardware spec. When I run the VM's on the new PC they just run at 100% CPU usage (after login). This did not occur on the other PC. 
I created a new Windows 10 VM and this seems to work with the CPU usage issue.
I have checked various settings on the W10 VM and on the Oracle Virtual Machine settings. They are not 'useable' on the new machine. I did upgrade from VM 5.1.22 to 5.1.28. I need to use the VM's on the new PC - but the CPU issue is stopping any productive use.",RhUkDev
17149,UI breaks as soon as a VM is created or added built with QT 5.9.2,Linux,all,VirtualBox 5.1.28,2017-10-11T17:03:30Z,2017-10-11T17:03:30Z,"UI starts fine prior to addition or creation of any VM. As some as a VM is created or added, the UI crashes and continues to crash until configuration is deleted.

Qt FATAL: ASSERT failure in QCoreApplication::sendEvent: ""Cannot send events to objects owned by a different thread. Current thread 0x0x26cba40. Receiver '' (of type 'UITaskMediumEnumeration') was created in thread 0x0x22e65d0"", file kernel/qcoreapplication.cpp, line 563

Thread 18 ""UIThreadWorker"" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f056bfff700 (LWP 19353)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007f05a1ed9930 in __GI_abort () at abort.c:89
#2  0x00007f059c86f657 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#3  0x00007f059c86a4ea in qt_assert_x(char const*, char const*, char const*, int) () from /usr/lib64/libQt5Core.so.5
#4  0x00007f059ca41686 in QCoreApplicationPrivate::checkReceiverThread(QObject*) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f0597aad848 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#6  0x00007f059ca41d07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#7  0x00007f059ca77f2c in QObject::setProperty(char const*, QVariant const&) () from /usr/lib64/libQt5Core.so.5
#8  0x00007f059df826d0 in UITaskMediumEnumeration::run (this=0x24b7170)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/medium/UIMediumEnumerator.cpp:65
#9  0x00007f059df5adca in UITask::start (this=0x24b7170)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/globals/UIThreadPool.cpp:298
#10 UIThreadWorker::run (this=0x26cba40)
    at /var/tmp/portage/app-emulation/virtualbox-5.1.28/work/VirtualBox-5.1.28/src/VBox/Frontends/VirtualBox/src/globals/UIThreadPool.cpp:322
#11 0x00007f059c8843d0 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5
#12 0x00007f05a245e867 in start_thread (arg=0x7f056bfff700) at pthread_create.c:456
#13 0x00007f05a1f9c9cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
",ekigwana
17154,Guru meditation running OPENSTEP 4.2,Mac OS X,other,VirtualBox 5.2.0 RC 1,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
17158,Guest OS Additions crashes Windows XP and Windows 7 Guests,Linux,Windows,VirtualBox 5.1.28,2017-10-11T23:39:27Z,2017-10-11T23:39:27Z,"This one is new to me. I was previously running an XP Guest x86 using VB 5.1 under Windows 10 Pro x64. Everything was fine. I had virtualization, nested pages, etc. enabled.

I then installed VB 5.1 under Ubuntu 16.04.LTS, x64 (of course), on ""super spiffy"" (that's ""shiny"") hardware and re-created the XP Guest x86. Things ran OK for a while and then began crashing.

I had been thinking about moving the ""content"" (applications) to a virtual Windows 7 box instead anyway, so I created a new Windows 7 x86 Guest. Again, everything ran fine for a while, and then would all of a sudden crash, or not boot, or freeze.

After having pulled my hair out for a few days, I tried uninstalling the VirtualBox GuestOS Additions. First from the XP Guest, and when that got a lot more stable, I did the same thing for the Windoes 7 Guest.

No more crashes, no more sudden freezing, no more BSOD.
(Or at least not yet, two days and counting.)

Every once in a while though, Ubuntu will report a ""System Problem"" and the VirtualBox Guest Window disappeares. In the Ubuntu crash log it says ""This is not an official version ..."" (I'm assuming they're talking about VirtualBox since the 16.04 dist contains 5.0.x). When that happens, however, I am still connected via RDP to the actual Guest OS, and it continues to run.",joho68
17155,Running VirtualBox on Ubuntu 17.04 with guest Ubuntu 16.04 crashes VM during apt-get update,Linux,Linux,VirtualBox 5.1.28,2017-10-12T12:41:54Z,2017-10-12T12:41:54Z,"I setup a pretty empty VM of Ubuntu 16.04 inside of a host 17.04 running VirtualBox.

When executing the command `sudo apt-get update` the VM crashes and goes into ""aborted"" state.  There appears to be no work-around, and nothing in the apt logs of interest.

Seems similar to this StackOverflow post:
https://stackoverflow.com/questions/30889170/vagrant-enters-aborted-state-during-apt-get-update

The process to create my VM is using Packer, extending a base image from:
https://app.vagrantup.com/box-cutter/boxes/ubuntu1604

and then running a few file copy commands, and then finally ""sudo apt-get update"" and partway through the update the VM vanishes, and is in ""Aborted"" state.

The same VM builds fine on Mac OSX as the host, but fails when Ubuntu is the host.  
",apatrida
17159,vboxsf file timestamp not set properly,Windows,Linux,VirtualBox 5.1.28,2017-10-12T15:40:37Z,2017-10-12T15:40:37Z,"Setting file modification timestamp on a file seated in shared folder does not work properly.

The case description:

{{{
$ df -h .
Filesystem      Size  Used Avail Use% Mounted on
Shared          932G  317G  616G  34% /media/sf_Shared
$ mount -l | grep Shared
Shared on /media/sf_Shared type vboxsf (rw,nodev,relatime)
$ touch -md ""1970-01-01 00:00:00""   test
$ ls -l test
-rwxrwx--- 1 root vboxsf 0 '''Jul 22  2554''' test

}}}

Doing the same on a native fs does work as expected.",Norbert Novotny
17122,Regular freezing of (windows 7) guest on macosx host (high sierra),Mac OS X,Windows,VirtualBox 5.1.28,2017-10-13T12:03:03Z,2017-10-13T12:03:03Z,I develop in a windows 7 guest system with java and eclipse. For several weeks now the guest freezes after an arbitrary time. After minimalising and restoring the guest window it shows the state as it had when the guest freezed. The same I had with 5.1.26 too. It is similar to reported ticket 8511.,chrigel
15084,Scale Factor Causes Malfunction of USB Multi-Touch Tablet in Debian-Based Linux,Windows,Linux,VirtualBox 5.0.14,2017-10-15T18:45:26Z,2017-10-15T18:45:26Z,"I just acquired a Surface Book that has a high resolution touchscreen interface. Enabling the USB Multi-Touch Tablet interface, touches register correctly in the guest only when the Scale Factor is set to 100%.

When the Scale Factor is set to 200%, the upper-left quarter of the screen registers input for the entire render and the other three quarters register nothing at all.

For example, with the Scale Factor set to 200%, I can register a click on the Menu button in the lower-left corner of the screen by tapping on a point just above the center of the left edge of the screen. Tapping directly on the Menu button registers nothing.

It's easy to see this bad behavior as well by running `xinput test 11` and dragging a finger around the screen. With the Scale Factor set to 200%, it's pretty clear where the events register and where they stop registering.

I retested on build 105205 and this hasn't been miraculously fixed. Running LMDE 2 (Mate) or Debian (Gnome), the result is the same.",bazald
17169,Magix Music Maker (Free) freezes current VM,Linux,Windows,VirtualBox 5.1.26,2017-10-15T20:28:54Z,2017-10-15T20:28:54Z,"I have downloaded and installed ""Magix Music Maker Free"" in a Windows 10  VM (with Guest Additions).
The installation went fine, but when I started the program, right before starting the UI (was in Splashscreen) it froze the Virtual Mashine completly. The UI of the VM was responsive but when I e.g. selected ""Close"" the dialog did not appear and I had to kill the process of the VM.

I also tried the same with a Windows 7 VM (also with Guest Additions) and the same happened.",LinusCDE
17164,wireless mouse stopped working,Windows,Windows,VirtualBox 5.1.28,2017-10-16T14:58:02Z,2017-10-16T14:58:02Z,"I installed the new 5.1.28 version and it caused my wireless mouse to stop working in BOTH the HOST and the virtual computers.  I tested this with both a wired and wireless mouse and several virtual computers, rebooted several times.  Each time this was the cause of the interference.  This was not present in previous versions of virtualbox and I previously was using 5.0.46.",3_laws
17171,KDE scale display causing mouse offset,Linux,Windows,VirtualBox 5.1.28,2017-10-16T18:06:53Z,2017-10-16T18:06:53Z,After setting up scale display option in KDE plasma (5.10) mouse cursor doesn't point to right place. Cursor is visible but it points to place with certain offset in guest machine. I'm guessing offset value relates to scale value. The problem seems to occur only with mouse integration turned on.,Kamil
17167,Can't install Extensions in WMaker / Linux Mint 17.2,Windows,Linux,VirtualBox 5.1.28,2017-10-16T22:27:26Z,2017-10-16T22:27:26Z,"Clicking on ""Insert Guest Additions CD Image"" while running WMaker (0.95.8+20170322) running on Linux Mint 17.2 fails.

VBOXADDITIONS_5.1.28_117968 never shows up under /media/my_name/

Inserting Guest Additions has never worked under any version of WMaker I've ever run.

I can log out of WMaker and log back in under XFCE and install guest additions but that's trashed the MDM Menu and my ability to log back in to WMaker.",BasilRathbone
17106,5.1.28 + 5.1.29 - After installing guest additions - Memory Exception explorer.exe,Mac OS X,Windows,VirtualBox 5.1.28,2017-10-17T14:29:59Z,2017-10-17T14:29:59Z,"After updated from 5.1.26 to version 5.1.28 and installing the gust additions in Windows 10 (1703) guest, I've expected an exception by shutting down the guest out from the task bar.

While Windows shuts down, and the white dots are spinning, the exception appears.

Then it take a few seconds and the VM turns off.

Then I've tried the test version 5.1.29 r118026 (Qt5.6.2) - same issue.

With version 5.1.26 and guest additions all is fine. Fortunately I made a snapshot, so I can still work on old additions.",TH3rb5t
17176,Linux Host Freeze,Linux,Windows,,2017-10-17T22:08:53Z,2017-10-17T22:08:53Z,"I am trying to use 5.2 RC1 with VBoxGuestAdditions_5.2.0-118335.iso. While compiling it gives the error.

Removing existing VirtualBox kernel modules.
Building the main Guest Additions module.
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.13.5-200.fc26.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 ""  ERROR: Kernel configuration is invalid."";           \
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0


Due to this VM freezes 

[  374.469053] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.485162] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.498844] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.751049] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.767185] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.783423] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.799557] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.809525] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.818953] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.834671] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.853894] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  374.871137] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  374.903968] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  375.086138] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  375.105844] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  375.130701] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000
[  375.153612] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728313400
[  380.547353] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad ffff973728312000


Linux 4.13.5-200.fc26.x86_64 #1 SMP Thu Oct 5 16:53:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

",Taral
17179,Extension pack upgrade failure (from within VirtualBOX offer to do so),Windows,other,VirtualBox 5.2.0,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
17152,VirtualBox RC1 guest additions hang Poser 6 & 7 on startup under XP guest,Linux,Windows,VirtualBox 5.2.0 RC 1,2017-10-18T22:59:06Z,2017-10-18T22:59:06Z,"Greetings,

I recently updated to VirtualBox v5.2.0 RC1 to give it a try and see if my VMs could still work fine in it. I was well inspired, since I found a show-stopper bug (at least for my needs).
So, I installed VirtualBox v5.2.0 RC1, the v5.2.0 RC1 extension pack, booted my Windows XP guest VM in fail-safe mode, installed the VirtualBox guest additions (which, strangely, identify themselves as being v5.2.0 Beta 3 additions, instead of RC1...) with DirectX support.

Once the VM rebooted, when I start Poser 6 or 7 (the only two versions I got) on a Windows XP (32 bits) guest running on a 64 bits Linux host, the program hangs shortly after starting, on the startup screen, and Windows reports the program as ""non responding"" in its title bar. After a few more seconds waiting, the window of the program turns white and it stays stuck forever like that.

I then reinstalled the v5.1.28 guest additions (still keeping VirtualBox v5.2.0 RC1) and found out that Poser then works fine again.

Probably an issue in DirectX support ?

VBox.log attached (in its state, just after launching Poser).",dinosaur0
16850,No Connection to Mobile Phone with MTP via USB,Windows,Linux,VirtualBox 5.1.22,2017-10-20T07:30:48Z,2017-10-20T07:30:48Z,"
== My configuration: ==

My Host-OS is Windows 8.1 and my VirtualBox is V5.1.22r115126 including its extension pack and installed USB-controller.
  

== The problem: ==

While my Samsung Galaxy Note 4 (SM-N910F) with Android 6.0.1 perfectly connects through USB with MTP to any native installed Mint or Ubuntu Linux OS, it does not connect to any Mint or Ubuntu if it runs virtual under VB. The file browser of the guest system shows the mobile phone but doesn't show any files. It further appears to hang. All other USB devices work well.

The phone is automatically detected as follows:
Name:         SAMSUNG_Android[0400]
Manufacturer: 04e8
Product ID:   6860
Revision no:  0400
Manufacturer: SAMSUNG
Product:      SAMSUNG_Android
Serial No.:   55xxxx7b
Port:         
Remote:       No
 
Special observation:
Two virtual Guest-OS (both MINT) were running. After I tried to connect my mobile phone without success to one Guest-OS, I shut the Guest-OS down and suddenly found that the phone was connected to the remaining Guest-OS as MTP-device and showed all directories and files as it should be and everything worked fine.


== Conclusion: ==

VB has a bug in handling USB MTP devices or certain USB MTP devices (like my Samsung Galaxy Note 4).

I would be grateful if you could provide a solution or if you book and confirm this as a VB bug.

Didi

  
",Didi
17185,VirtualBox v5.x & nVidia Graphics Card: Driver reverts to VGASave upon VB Installation,other,all,VirtualBox 5.2.0,2017-10-20T12:04:38Z,2017-10-20T12:04:38Z,"My system:

MS-WinXP with SP3 and fully Updated

Palit nVidia GeForce 7300GT AGP 8X 512MB DDR2 128bit

nVidia Driver Packages tried:
  * 306.81-desktop-winxp-32bit-english-whql.exe
  * 307.74-desktop-winxp-32bit-english-whql.exe
  * 307.83-desktop-winxp-32bit-english-whql.exe

Example nVidia driver details output:

{{{
CMD>filever -v \WINDOWS\system32\nv4_disp.dll
--a-- W32i   DRV ENU     6.14.13.774 shp  4,493,440 01-03-2013 nv4_disp.dll
        Language        0x0409 (English (United States))
        CharSet         0x04b0 Unicode
        OleSelfRegister Disabled
        CompanyName     NVIDIA Corporation
        FileDescription NVIDIA Windows XP Display driver, Version 307.74
        InternalName    nv4_disp.dll
        OriginalFilenam nv4_disp.dll
        ProductName     NVIDIA Windows XP Display driver, Version 307.74
        ProductVersion  6.14.13.0774
        FileVersion     6.14.13.0774
        LegalCopyright  (C) 2012 NVIDIA Corporation. All rights reserved.

        VS_FIXEDFILEINFO:
        Signature:      feef04bd
        Struc Ver:      00010000
        FileVer:        0006000e:000d0306 (6.14:13.774)
        ProdVer:        0006000e:000d0306 (6.14:13.774)
        FlagMask:       0000003f
        Flags:          00000008 private
        OS:             00040004 NT Win32
        FileType:       00000003 Driver
        SubType:        00000004 DisplayDrv
        FileDate:       00000000:00000000
}}}

The problem:

Using VirtualBox v5.1.28 [VirtualBox-5.1.28-117968-Win.exe] with the corresponding extension pack, also previous versions, also with two other, GeForce 6200 nVidia cards, I was experiencing the following:

  a. occasional screen blanking, which, after a few seconds, was restored

  b. my graphics card driver was spontaneously reverting to VGASave [the Microsoft “failsafe” generic driver, that is not able to provide my graphics card & monitor optimal native resolution] after rebooting my system, but a re-installation of the driver package would return things to normal

After having upgraded to the current version of VirtualBox [VirtualBox-5.2.0-118431-Win.exe (with the corresponding extension pack)] my graphics card driver permanently reverted to the VGASave and consistently does so immediately after I install VirtualBox, ever since [I have also tried installing two previous versions, v5.1.30 and v5.0.40, to no avail]. After I uninstall VirtualBox, things magically return to normal.",Pol_JS
17187,GPO: automatic update need to be disalbed per machine,Windows,other,VirtualBox 5.1.30,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
16472,Default VirtualBox configuration in MSI,Windows,Windows,VirtualBox 5.1.14,2017-10-20T16:34:55Z,2017-10-20T16:34:55Z,"I need to preconfigure some global defaults for my users.

These are
- GUI/SuppressMessages=all
- GUI/UpdateDate=never
- defaultMachineFolder=""D:\Virtual Machines""

Updates are controlled via AD with MSI deployment. Can you add this as registry keys to the MSI setup, please? I explicitly need a way to set GLOBAL settings that are enforced to all users.",vboxuser4
17182,Black screen on Windows10 host vm 5.2.0,other,Windows,VirtualBox 5.2.0,2017-10-20T17:05:30Z,2017-10-20T17:05:30Z,"In a host Windows 10 Pro versión 1709, compilatión 16299.19 running W10 vm's, a black screens appears and don't show desk or logon.
When  im try to Close the vm, w10 desktop appears all grey but correctly showed.

Deactivating 3D acceleratión all W10 vm's run ok.

",hekmo
15305,Allow Relative Paths for Shared folder,Windows,all,VirtualBox 5.0.16,2017-10-21T08:12:00Z,2017-10-21T08:12:00Z,"It is not uncommon for VirtualBox users to keep one or more Virtual Machines on flash drives, or other external storage, so they can have the convenience of their VMs in their pocket.

Such an external drive might have a folder structure like this:

{{{
DevDrive
\-- Virtualbox_Instances
    |-- Ubuntu14.04_Client
    |   |-- Logs
    |   |-- SharedFiles
    |   |-- client.vbox
    |   \-- client.vdi
    \-- Ubuntu14.04_Server
        |-- Logs
        |-- SharedFiles
        |-- server.vbox
        \-- server.vdi
}}}

When attached on Windows, the drive letter assigned to the drive can generally not be predicted, especially across multiple host machines.

Therefore if the user wishes to have the convenience of an [[https://www.virtualbox.org/manual/ch04.html#sf_mount_auto|auto-mounted shared folder via guest additions]], it is not unusual to have to re-define the shared folder whenever they try running their VM on a new host machine.

The logical solution to this problem would be to define the path of the shared folder relative to the VM, but currently relative paths seem to not be allowed.

Specifically, given the above Folder Structure, if the user modifies u14.14_client.vdi to contain:
{{{
<SharedFolders>
  <SharedFolder name=""SharedFiles"" hostPath="".\SharedFiles"" writable=""true"" autoMount=""true""/>
</SharedFolders>
}}}
They will receive this error:

[[Image(https://i.imgur.com/usGTFOq.png)]]

While adding the path as intended will result in something like:
{{{
<SharedFolders>
  <SharedFolder name=""SharedFiles"" hostPath=""F:\Virtualbox_Instances\Ubuntu14.04_Client\SharedFiles"" writable=""true"" autoMount=""true""/>
</SharedFolders>
}}}

But there is no guarantee that this drive will mount as letter `F` when connected on another host machine.

We cannot assume that the user would even have the privileges necessary on the host machine to assign a drive letter, especially since it may already be bound to another drive.


----

It would be really useful if VirtualBox supported relative Paths for Shared Folders. 

The path should be relative to the `.vbox` file itself.

",JohannesMP
16990,Cannot start the Guest in VirtualBox,Linux,Windows,VirtualBox 5.1.26,2017-10-21T09:19:21Z,2017-10-21T09:19:21Z,"'''Some of my information:'''[[BR]]
Machine: MSI GE62-489 (CPU: Intel® Core™ i7-6700HQ @ 2.60GHz × 8 )[[BR]]
Host system: Ubuntu 14.04 64-bit(kernel: 4.4.0-89-generic)[[BR]]
VirtualBox version: 5.1.26 r117224[[BR]]
Guest system: Windows 7 64-bit[[BR]]
[[BR]]

When I try to start Guest in VirtualBox, it showed 2 error messages:[[BR]]

'''First message:'''

{{{
Failed to open a session for the virtual machine Windows 7.

The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

Just like the following figure:[[BR]]
[[Image(http://i4.bvimg.com/1949/3876f081487a381e.png)]]

'''Second message:'''

{{{
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or 
there is a permission problem with /dev/vboxdrv. Please reinstall 
the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED 
(-1908) - The support driver is not installed. On linux, open returned 
ENOENT.
}}}
 
Just like the following figure:[[BR]]

[[Image(http://i4.bvimg.com/1949/5c44b8e679464f9c.png)]]

Then, I do what he told me to do, run the following command in terminal:

{{{
$ sudo /sbin/vboxconfig
}}}

It shows the following message:

{{{
Adding system startup for /etc/init.d/vboxdrv ...
   /etc/rc0.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc1.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc6.d/K80vboxdrv -> ../init.d/vboxdrv
   /etc/rc2.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc3.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc4.d/S20vboxdrv -> ../init.d/vboxdrv
   /etc/rc5.d/S20vboxdrv -> ../init.d/vboxdrv
 Adding system startup for /etc/init.d/vboxballoonctrl-service ...
   /etc/rc0.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc1.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc6.d/K65vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc2.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc3.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc4.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
   /etc/rc5.d/S35vboxballoonctrl-service -> ../init.d/vboxballoonctrl-service
 Adding system startup for /etc/init.d/vboxautostart-service ...
   /etc/rc0.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc1.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc6.d/K65vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc2.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc3.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc4.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
   /etc/rc5.d/S35vboxautostart-service -> ../init.d/vboxautostart-service
 Adding system startup for /etc/init.d/vboxweb-service ...
   /etc/rc0.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc1.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc6.d/K65vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc2.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc3.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc4.d/S35vboxweb-service -> ../init.d/vboxweb-service
   /etc/rc5.d/S35vboxweb-service -> ../init.d/vboxweb-service
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
}}}

You can see this line:

{{{
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
}}}

So I run the following command in terminal:

{{{
$ dmesg
}}}

It shows about 1000 lines. The whole information it shows is in the attach file. There are some errors and warnings from this information:

{{{
[    0.019546] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
[    0.027179] ACPI Error: 1 table load failures, 9 successful (20150930/tbxfload-214)
[    0.205608] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.205611] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    0.205622] ACPI : EC: Fail in evaluating the _REG object of EC device. Broken bios is suspected.
[    0.221593] ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    0.221596] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC._REG] (Node ffff88027b0ef4b0), AE_NOT_FOUND (20150930/psparse-542)
[    2.603310] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2
[    2.603334] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2
[    2.603347] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[    3.273673] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro
[  126.578953] systemd-hostnamed[5793]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 1952.203735] systemd-hostnamed[13694]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
}}}

Now I don't know what to do. The Guest system just cannot start.[[BR]]

'''Another information:'''[[BR]]

If I choose kernel 3.19.0-25-generic to come in when I start up my machine, the same VirtualBox can use normally. The Guest system win7 can start normally. But I never succeed to start guest normally with any linux kernel who is newer than 3.19.0-25

So, how to solve this problem? Thank you very much!",TimeCoder
17199,Virtual appliance of Debian Stretch 32 bit fsails to boot on a native  64 bit,Linux,Linux,VirtualBox 5.1.30,2017-10-22T12:22:08Z,2017-10-22T12:22:08Z,"Failed to open a session for the virtual machine Debian 32bit.

Unresolved (unknown) host platform error. (VERR_UNRESOLVED_ERROR).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",flipper88
17177,Loss of usb device after live snapshot or snapshot restore,Linux,Linux,VirtualBox 5.1.30,2017-10-24T15:20:39Z,2017-10-24T15:20:39Z,"{{{
Host OS: Solus 3 (linux)
Guest OS: Solus 3
Solus kernel: 4.13.5-24.current
VirtualBox Build: 5.1.30r118389
Extension pack installed
USB 2.0 selected
}}}

* USB gamepad shared with the guest.
* Cold boot.
* Play a game using gamepad (e.g. supertux 2)
* Take a live snapshot.
* Gamepad no longer working.
* Restore snapshot.
* Gamepad not working.
* Reboot = gamepad working again.

",romulous75
17201,Installing 5.2 Extension pack disables the VB Shared Folders,other,other,VirtualBox 5.1.30,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
17209,VB Unusably slow,Linux,Windows,VirtualBox 5.1.28,2017-10-25T13:51:20Z,2017-10-25T13:51:20Z,"I had been using VB 3.x and 4.x for years, years ago. It has always been slow but it used to be almost usable.

Now I have upgraded to 5.1.28 and it's unusably slow. Even the application's menus on the host are unresponsive (to the point you even lose clicks on the menus, e.g. the Machine or Devices menu.

I did view->Take screenshot and it took more than a minute for the popup to appear. That's just an example.

My host is ubuntu (on an i7 processor with 4GB RAM) and the guest is Windows 7. Both 64bit.

I am using the very same computer and the same host and guest OS (and the same VM) that I was using years ago with VB 3.x and 4.x and it is WAY slower.

It's pathetic.",teo8976
17192,5.2 Guest Extension : no share Drives ?!,Windows,Windows,VirtualBox 5.2.0,2017-10-25T20:15:37Z,2017-10-25T20:15:37Z,"1.) have upgrade from 5.1.30 and run 5.2 OK. than install Guest Extension.
2.) after reboot i want to reject CD and saw NO share Drives any more ?
3.) after change User i complete lost setup information so i have to attach VDI again and make all setup entry
both Windows 10 1703 Host 64bit / Guest 32bit",Xbase++
17210,Updated to VB 5.2.0; install failed,Linux,Linux,VirtualBox 5.2.0,2017-10-25T22:08:28Z,2017-10-25T22:08:28Z,"I have tried to upgrade VirtualBox to 5.2.0 but the installation failed. Then I tried the ""latest
test (dev?) build (VirtualBox-5.2.1-118468-Linux_amd64.run) but the installation has again failed.

I must be doing something wrong since I am almost continually getting this error (see the enclosed log).

Am I doing something wrong? The error log suggests various versions of ""libelf"" but Fedora 28 (rawhide) doesn't
have any of these packages and as far as I know, never has.

Any help you can give me about this problem would be greatly appreciated.

Regards,

George...
",George R. Goffe
17211,arm64/arm hypervisor add ons,all,all,VirtualBox 5.1.30,2017-10-26T01:39:43Z,2017-10-26T01:39:43Z,"I have windows /Gentoo  getting arm64 is slightly doable 
however qtemu or aqemu and some hacking backends . 
reliability next to Zilch..  today working tomorrow updates ...s@#$ its broken.. 

say you wish to piddle with Debian 9 arm64 iso well you SOL ... or windows 10 with more Umph than an RPI-3 in 64 mode. 

anyhow , the smooth reliable Virtualbox hypervisor , just add  to Vbox-hyper-arm64 etc.. sub modules.. 

",necrose99
17212,UEFI Hybrid,all,all,VirtualBox 5.1.30,2017-10-26T01:52:01Z,2017-10-26T01:52:01Z,"'''UEFI Hybrid boot mode''',  enable UEFI in vbox bios... 

boot up , Linux or windows , some Linux can do EFI , however have to build first.  also if you care to migrate to U/EFI ,  from a legacy boot image.''''''

if efi isn't up on iso count down , or skip. then use can build ie Gentoo /Arch Linux  

anyhow this has been a wishlist feature for sometime... @ Work VMware 12 dose this .. 

however less i have 200 bucks... ",necrose99
16965,Mini Toolbar hidden in full screen mode in 5.1.26,Linux,Windows,VirtualBox 5.1.26,2017-10-26T12:06:29Z,2017-10-26T12:06:29Z,"VB 5.1.26, Linux host, Windows 10 guest.  After upgrading from 5.1.24 to 5.1.26 the mini-toolbar no longer appears when I mouse-over the top of the screen in full-screen mode.  host-home does bring up the menu.",Don Hughes
16131,Dual full-screen windows both displayed on monitor 1 at boot,other,other,VirtualBox 5.1.8,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
17214,Random Crash,Mac OS X,Windows,VirtualBox 5.1.18,2017-10-27T04:40:23Z,2017-10-27T04:40:23Z,Middle of Entering Data on a web form when crash occurred.,Modem56k
17216,Should be able to add USB filesystem dump,other,other,VirtualBox 5.0.40,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
17197,Windows XP SP3 blue screen (VBoxGuest.sys),Linux,Windows,VirtualBox 5.2.0,2017-10-27T20:26:20Z,2017-10-27T20:26:20Z,"After updating from VirtualBox 5.1 to 5.2, I updated the Guest Additions in safe mode, rebooted and logged in my Virtual Machine (Windows XP SP3 Professional with the Microsoft Extended Support). The login was fine, but I noticed that some programs were misbehaving like Team Viewer and everything was kinda laggy (not smooth). I turned the virtual machine off and on again, logged, same. I did some tests with Advanced Chromium (updated Chromium builds for XP) and Firefox 52 ERS and both were kinda slow. I then tried to open Aspera Connect and it worked fine. Avast was working fine. Disabling it and doing a fresh install of it didn't solve the issue, though. I then left my computer open during the night to download files from a TV Studio using Aspera (these master files were fine and virus free, for the records). Then I woke up, I went to work and I found out that my Virtual Machine had a blue screen caused by VBoxGuest.sys.

Host: Fedora Workstation 26, updated constantly.
CPU: Intel i7 6700HQ 4c/8th
RAM: 16 GB DDR4 (8x2)
GPU: NVIDIA 950M 4GB GDDR5
Hard Drive Host: Toshiba 1TB Sata III

Guest: Windows XP Professional SP3 x86 + Microsoft Premium Support + PAE
CPU: 8 cores (I know VBox works with cores and not with thread, in fact I shouldn't assign threads to the virtual machine, 'cause timing would be terrible, but I do it anyway 'cause benchmarks shows that it slightly increase performances. Anyway, limiting it to 4core didn't solve the issue).
RAM: 6 GB (read correctly as 6)
Hard Drive: Seagate SSHD 1TB Sata III (XP is installed on a Physical SSHD and I use it with the raw disk function. I also have no intention of migrating it into a virtual machine file. It's an install I've been working on flawlessly as programmer since 2001, which has been cloned several times to several different hard drives. It's like my baby).

Screenshot and VBox log file in attachment.
Thank you in advance.",FranceBB
14438,Please add support for Windows Server 2016,all,Windows,VirtualBox 5.0.2,2017-10-28T11:09:51Z,2017-10-28T11:09:51Z,"Currently if you name your VM Windows Server 2016 VirtualBox doesn't detect it as Windows Server and doesn't use appropriate parameters.

Windows Server 2012 is suitable as a template.",Artem S. Tashkinov
17222,"Feature request: create full/complete snapshots instead of ""differential""",all,all,,2017-10-28T13:48:31Z,2017-10-28T13:48:31Z,"I usually need to create many snapshots at different points in time. This makes a mess, because every snapshot is a child of the one before, and deleting any of them take HOURS.

I'd die for the ability to create '''full/complete snapshots''' without any hierarchy tree above!

Disussion here: https://forums.virtualbox.org/viewtopic.php?f=1&t=85226",gianluigi.zanettini
17150,VirtualBox triggers a kernel panic in macOS 10.13.1 public beta 1,Mac OS X,Windows,VirtualBox 5.1.28,2017-10-28T15:58:41Z,2017-10-28T15:58:41Z,"Using the first public beta of 10.13.1, a kernel panic and system crash occurs as soon as you start VirtualBox.  This happens with both VirtualBox 5.1.28 and the 5.2 release candidate.

I found  workaround that works for me:

1.  Run ""VBoxManage list vms” to list your VM’s along with their display names and kids
2.  Run your VM in headless mode by running “VBoxManage startvm your-vm-name —type headless” where your-vm-name is the name listed in step 1.
3.  Run virtualbox to bring up its UI
4.  Select the running VM in VirtualBox and click “Show”.  At this point the UI for your running VM should appear.

After that the virtual machine (Windows 10) ran as expected and I was able to shut it down in the normal way from its UI.",Matt L.
17223,virtualbox 5.2 win nt 4 sp1,Windows,other,VirtualBox 5.2.0,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
16743,"Allow ""Restore current snapshot"" from right-click Close in Manager",Mac OS X,all,VirtualBox 5.1.22,2017-10-29T09:27:32Z,2017-10-29T09:27:32Z,"When a VM window is closed, there are 3 options (save, shut down, power off), and the last option ""Power off the machine"" has a checkbox for ""Restore current snapshot [...]"".

It would seem appropriate to give the same checkbox choice when closing from Oracle VM VirtualBox Manager, and also to use the same option names instead of, e.g., ""Send the shutdown signal"" vs. ""ACPI Shutdown"".",RafSchietekat
15853,audio and video out of sync on Ubuntu 16.04.1,Linux,Linux,VirtualBox 5.1.4,2017-10-30T10:52:29Z,2017-10-30T10:52:29Z,"Audio and video are out of sync when a youtube video is playing.
Behaviour noticed in a topic of VirtualBox forum: [https://forums.virtualbox.org/viewtopic.php?f=3&t=79360]

My original issue concerned the fact that the Linux guest was unable to reproduce all media contents. In the forum I was suggested to change the Audio Controller, solution that solved the issue.

However @Perryg noticed that audio and video are out of sync and suggested to open this ticket.

My Linux host  is Ubuntu 14.04 LTS, 5,7 GB of total memory
My Linux guest is Ubuntu 16.04.1 LTS, 2 GB of memory and 50 GB of fixed-size file as virtual hard disk.

I attach two log files:

VBox1.log file concerning my original issue posted to the forum
Vbox2.log file recording the reproduction of a youtube video and the reproduction of the same video with videos application.",jrkul
15633,Unable to uninstall VirtualBox,Windows,other,VirtualBox 5.0.22,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
17226,Virtualbox 5.2 crashed,Linux,Windows,VirtualBox 5.2.0,2017-10-31T09:28:17Z,2017-10-31T09:28:17Z,The VM has crashed. The log and dump information are attached.,Panos Kavalagios
17080,"guest additions do not build with 4.14 kernel -> fixed in builds after 1. November 2017, 5.2 and later",other,Linux,VirtualBox 5.1.26,2017-10-31T16:46:43Z,2017-10-31T16:46:43Z,"Got an error message while attempting to install guest additions in a Fedora Rawhide guest for the 4.14.0-0.rc0.git5.1.fc28.x86_64 kernel.
{{{
vboxadd.sh: failed: Look at /var/log/vboxadd-install.log to find out what went wrong.
}}}",Andre Robatino
17229,Please add HP Sure Click as a hardening adversary.,Windows,all,VirtualBox 5.2.0,2017-10-31T18:47:23Z,2017-10-31T18:47:23Z,"Please see a forum discussion here: https://forums.virtualbox.org/viewtopic.php?f=6&t=85134.

A log is provided in the forum.

The user was having typical hardening problems, it looked like an AV conflict, but the ""adversaries"" list in VBoxHardening.log was empty. Plus the user said he normally uses Defender on his Win10 host, which we usually consider as not a problem.

Eventually, after tips on what kind of software to consider, the user discovered that removing ""HP Sure Click"" (a browser filter) fixed the problem.

I am drawing attention to the discussion in case you decide that ""HP Sure Click"" should be added to the adversaries that the hardening feature looks for. Had it been listed then we would have come to the correct diagnosis much faster.
",mpack
17166,Installing Extension Pack trashes Linux MDM Login options,Windows,Linux,VirtualBox 5.1.28,2017-10-31T19:41:42Z,2017-10-31T19:41:42Z,"Windows 10 Pro
AMD Athlon™ II X4 650 Processor 3.20Ghz
nVidia GeForce GTX 750 Ti (GeForce Game Ready Driver 3.87.92)
Microsoft Security Essentials
VirtualBox-5.1.28-117968-Win.exe
Oracle_VM_VirtualBox_Extension_Pack-5.1.28-117968.vbox-extpack

There is something about installing the VirtualBox Extension Pack (5.1.28) that wipes out my MDM Login menu in my Linux Mint 17.2 / XFCE / Wmaker VM.

I updated my Windows 10 Pro machine to VirtualBox-5.1.28-117968-Win.exe and installed Oracle_VM_VirtualBox_Extension_Pack-5.1.28-117968.vbox-extpack in my Linux VM. This trashed my ability to log into any of my desktops other than my original XFCE Desktop.

My MDM Login menu worked as expected under 5.1.22 but exhibited the same problem in earlier extension packs.

This also happened when I tried to upgrade VirtualBox to v5.0.24 - I didn’t report it then. I just assumed a later version (5.1.22) would fix the issue.

------------- Prior Issue ---------------

by BasilRathbone » 17. Oct 2016, 19:14 

I run VirtualBox 5.0.16 under Windows 10 Home Premium. One of my VM's is Linux Mint 17.2. I run multiple desktops under Linux Mint 17.2, XFCE and WMaker, my favorite being Wmaker.

I tried updating VirtualBox to version 5.1.6. Installing 5.1.6 Extensions in my Linux VM trashes my ability to log into any of my desktops other than my original XFCE Desktop. My MDM Login menu works under 5.1.6 until after I run VBoxLinuxAdditions. Something in that installation process trashes MDM.

This also happened when I tried to upgrade VirtualBox to v5.0.24 - I didn’t report it then. I just assumed a later version would fix the issue.

The last version that works properly for me is 5.0.16 running under Windows 10 Home. ",BasilRathbone
17231,Installing Grisoft's AVG into Win 7 SP1,Windows,Windows,VirtualBox 5.1.30,2017-10-31T21:01:12Z,2017-10-31T21:01:12Z,Nearly installed (97%) and it stopped with your 'Guru Meditation' screen,Lofty
17232,/sbin/vboxconfig fails during upgrade of Vbox,Linux,Linux,VirtualBox 5.2.0,2017-11-01T16:20:41Z,2017-11-01T16:20:41Z,"I have upgraded kernels on this Fedora 28 (rawhide) system and tried the latest Vbox release (!VirtualBox-5.2-5.2.0_RC1_118201_fedora26-1.x86_64.rpm) as well as the latest developer version (!VirtualBox-5.2.1-118869-Linux_amd64.run) with the same apparent result.

Can someone tell me what I'm doing wrong here please?

George...",George R. Goffe
14336,Error with copyfrom,other,other,VirtualBox 5.0.0,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
17234,Cannot Install VirtualBox Extension pack after upgrade,Windows,Windows,VirtualBox 5.1.30,2017-11-04T23:33:50Z,2017-11-04T23:33:50Z,"I am running virtualbox on Windows 10. I just upgraded to VirtualBox V5.1.30 r118389. I uninstalled old version of guest edition extension pack and downloaded latest version 

On installing, the following error is reported:

Failed to install the Extension Pack C:/Users/Administrator/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.2.0-118431 (1).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-11020' -&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}

I had no problem when upgrading to VirtualBox V5.2.26",Tony_UK
17244,CentOS 7 Kernel-ml hangs,Windows,Linux,VirtualBox 5.2.0,2017-11-05T13:45:10Z,2017-11-05T13:45:10Z,"Documented here: https://bugs.centos.org/view.php?id=11065

Kernel hangs on CPU making the guest graphics mainly unuseable unless you run all Linux in CLI

I'm using the Virtualbox guest additions as advised on the main site, aware that the latest won't compile properly.

Also doesn't like bridging with an RTL8188EE adapter properly, this could be because of the native drivers.",koolholio
17243,VirtualBox COM service process doesn't exit on its own,other,other,VirtualBox 5.2.0,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
17246,VirtualBox Guest Additions Fails to start,Linux,Linux,VirtualBox 5.2.0,2017-11-05T18:24:07Z,2017-11-05T18:24:07Z,"VirtualBox Guest Additions: Starting.
/etc/rc.d/init.d/vboxadd: line 255: : No such file or directory
",PresidentTrump
16880,USBPROXY Getting USB descriptor failed with error 31,Windows,Windows,VirtualBox 5.1.22,2017-11-06T04:07:05Z,2017-11-06T04:07:05Z,"I cannot use the USB extension pack anymore. It was working fine a few weeks ago but now I get this error whenever I try to add a USB device (from the host) to the guest machine:

USBPROXY Getting USB descriptor failed with error 31

The USB device disappears from the host but dooes not appear on the guest. I tried to downgrade to older versions of VirtualBox but it does not work.

The USB devices are working fine on the host.

Both host and guest run Windows 10 X64 Creator Update.",M.
17247,i-beam cursor missing / tiny scale (Win guest additions 5.2.1),Windows,Windows,VirtualBox 5.1.30,2017-11-06T18:29:09Z,2017-11-06T18:29:09Z,"Windows host (5.2.0) and Windows guest with additions (5.2.1).

With a 4K screen (3840x2160) at 100% scale, the ""Text Select"" (i-beam) cursor is missing (not rendered). When Windows mouse properties / pointers set to a custom cursor (e.g. beam_r.cur) it is really tiny - too small to see properly.

With the host set at 300% scaling, beam_r.cur is the correct size.

[Update after further testing]
c:\windows\cursors - cursors with the small 9KB file size are not scaled properly. Cursors with the > 100KB file size are.

(This affects windows guests. Using these smaller cursor files on the Windows host scales correctly.)",dangr
17248,Guest Additions Directory Listing in Windows XP,Windows,Windows,VirtualBox 5.1.30,2017-11-06T21:19:25Z,2017-11-06T21:19:25Z,"Windows XP installed in VirtualBox.  
Host Window 7 or Windows 10.  
Directory listing works OK as 'dir' from DOS Prompt or as 'file open' from notepad.  
But for some programs, if directory listing returns 8 or fewer files, OK; but if directory listing returns 9 or more files, nothing.  
An example program with this problem is the old Norton fa.exe command which lists files and attributes (eg, archive, readonly).  
",Roger
17251,Critical Error whilst starting game,Windows,Windows,VirtualBox 5.2.0,2017-11-07T06:04:55Z,2017-11-07T06:04:55Z,I was trying to start Melbourne Cup Challenge/Frankie Dettori Racing when the Critical Error message came up. I am running Windows 10 and this game last ran on Windows XP. I have Windows XP 32-bit installed on Virtual Box.,James Bluntus
16932,"Microsoft Office unusable in version 5.1.24, was working in 5.1.22 fairly well, not perfect though",Linux,Windows,VirtualBox 5.1.24,2017-11-08T04:52:07Z,2017-11-08T04:52:07Z,"After installing the latest VBox (5.1.24) the guest becomes unusable when Microsoft Office is running. It becomes completely unresponsive. The clock (showing seconds) no longer advances by 1 second, instead it jumps every few seconds showing that the VM is hung most of the time. The guest window even darkens periodically showing that the host detects it as unresponsive.[[BR]]

For some applications, it's enough to open it without loading anything (Word 2016 or Excel 2016 for example). The older versions (i.e. Word 2013 or Excel 2013) can be opened, but if a document is loaded, or in the case of Excel if any single cell (or a range of cells)  is copied to the clipboard, the guest becomes pretty much locked. It is possible with persistent clicks on the close button to terminate MS Office application and regain guest responsiveness, but this usually takes minutes as the VM pretty much doesn't respond for most of the time.[[BR]]

I have reverted to 5.1.22 and the problem went away proving it's a regression in 5.1.24.
",Rafcio
17245,VBoxGuestAdditions_5.2.1-118918 does not work with Ubuntu 17.10 guest,Windows,Linux,VirtualBox 5.2.0,2017-11-08T11:57:40Z,2017-11-08T11:57:40Z,"After installing guest additions version VBoxGuestAdditions_5.2.1-118918, Ubuntu 17.10 will not boot. Initially the ""Ubuntu"" logo appears as per normal, then screen goes black, does not get to login screen. However, pressing ctrl-alt-F* keys will bring up terminal prompt.
In order to get Ubuntu guest to boot, I have to re-install distribution-package version of guest additions (5.1.30)",Christopher777
17257,Linux host + Windows 10 + client tools results in minor display corruption,Linux,Windows,VirtualBox 5.1.30,2017-11-09T11:50:46Z,2017-11-09T11:50:46Z,"Steps to reproduce:

1. Start with host Ubuntu Linux 16.04 LTS 64 bit (I'm able to reproduce with intel i7-3770K + integrated graphics (i915 driver)).
2. Install Windows 10 as client (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ - I'm reproducing with 32 bit Windows 10).
3. Launch Internet Explorer 11
4. Visit https://jsfiddle.net/rwfvo4L7/

Expected results:

Rounded corners for the grey rounded boxes should look normal.

Actual results:

Rounded left side corners have some kind of horizontal comb-like effect. Similar problems may appear on some diagonal lines in SVG graphics etc.

Additional information:

May be related: https://www.virtualbox.org/ticket/14637
",mtrantalainen
12738,OpenGL windows are always on top of everything else in linux guest,Windows,Linux,VirtualBox 4.3.8,2017-11-09T13:00:22Z,2017-11-09T13:00:22Z,"System:
Host = windows 7 home premium
Guest = ubuntu 12.04 LTS

Virtualbox versions 
4.3.6r91406
4.3.8r92456

Hardware: AMD, INTEL, 32 and 64 bit, nvidia ati amd chromium

OpenGL windows from any application are always topmost, that is they are always on top of everything else.
In applications such as Blender, FreeCad etc drop down menus disappear behind the opengl window which is the main frame of the application. This makes it very difficult to use the program.
All opengl features seem to work.
I have reproduced this on at least 3 completely different hardware systems. 32 bit and 64 bit
When you run glxgears and drag the application to another location on the screen the application window moves with the cursor but the opengl window doesn't move until the mouse button is released.
Also all screenshots come out black, probably due to reversed window layering.
This must be a virtualbox bug as none of this behaviour occurs in Ubuntu 12.04 LTS when run natively. 
There are no errors reported nothing noted in any logs.
I've been trying to find a solution to this for almost 2 years.
There are a lot of similar bug reports which all claim it is fixed. Yet all I need to do is install virtualbox on any windows machine then install Ubuntu 12.04 LTS, install guest additions and I have the same problem. All other 3d acceleration works fine it's just the opengl window layering. 
Compiz cube works.
I think I started using virtualbox at version 4.2 and have always had this problem.
Running identical Ubuntu 12.04 LTS installations, one natively the other in a virtualbox on a windows 7 host on the same hardware platform. The native installation has no issues. The virtualbox guest installation always has this issue with opengl windows.
Please help...",solaris235
16474,5.1 installation fails on Sierra due to kext load issue,Mac OS X,other,VirtualBox 5.1.14,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
17258,vbox kernel modules should be signed for OL7,other,other,VirtualBox 5.2.0,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
17240,GUI Bug With Snapshots on macOS,Mac OS X,other,VirtualBox 5.2.0,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
17263,VirtualBox encounters an application error and aborts the guest,Windows,Linux,VirtualBox 5.1.28,2017-11-10T15:50:50Z,2017-11-10T15:50:50Z,"On a Windows 7 x64 host and a Linux Mint 18.2 guest using Virtualbox version 5.1.28 r117968.
I find that on my Dell Latitude E7440 occasionally when I edject from my docking station I will get the attached Application error, forcing my guest to abort.

At the time I have not mapped any USB ports though and and the network interface is set to my LAN controller. 

Attached will be the log of the aborted machine and a screenshot of the application error.
",BWhitten
17265,Error fetching directory count. (TIFFRewriteDirectory),other,other,VirtualBox 5.1.30,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
17271,New OS icon for ArcaOS,all,other,VirtualBox 5.1.30,2017-11-14T01:19:49Z,2017-11-14T01:19:49Z,I have the following icon to submit for ArcaOS (OS/2 distro).,Lewis Rosenthal
16843,"WDDM driver does not validate custom video resolutions, causing graphics freeze on boot",Linux,Windows,VirtualBox 5.1.22,2017-11-14T10:55:32Z,2017-11-14T10:55:32Z,"See investigation on [https://forums.virtualbox.org/viewtopic.php?f=7&t=83489 this forum post]

For some reason (possibly the tiling WM resize bug on Linux) the custom/transient display resolution can be set to a very small size (e.g. 400x191) and this small size is saved to the registry in Windows. Once the WDDM driver is installed, Windows will try to add this mode to the target modes in the VidPn framework. This fails and the boot sequence appears to freeze on the Windows splash screen, rendering the VM unusable.

A workaround is to install the Guest additions in safe mode, then edit the registry keys storing the custom resolution to be a larger size, e.g. 800x600. See the attached image.

Reproduced on both OSE and non-OSE versions of Virtualbox, 5.1.22 with corresponding extpack and Guest Additions ISO installed.

I have attached the boot log when the problem occurs. ",machfour
17259,"Upgrade 5.1.28 to 5.2 headless guest can no longer be accesses, video performace degraded",Linux,Windows,VirtualBox 5.2.0,2017-11-15T06:18:24Z,2017-11-15T06:18:24Z,"Upgrade from 5.1.28 to 5.2 (Arch x86_64 host) leaves headless Win7 guests unable to capture mouse or keyboard regardless of host-key use until virtualbox is started on host machine and guest launched via gui interface and windows guest addtions updated from 5.1.28 to 5.2.

PUEL from VirtualBox-5.2.0-118431-Linux_amd64.run with Oracle_VM_VirtualBox_Extension_Pack-5.2.0.vbox-extpack

This is unexpected new behavior. The expected result is that following update, the headless client can be started and accessed as normal remotely via rdesktop and guest additions updated from within headless guest as has been the case with all prior 5.1.X updates. 

An update to 5.2 on the host will leave Win7 (and probably others) unable to access the headless guests remotely. There is no way to have the mouse or keyboard captured when first accessing a headless Win7 guest remotely after the 5.2 update on the host. The login screen is displayed and visible, but there is no way to interact with it -- with or without host-key use (currently the default rt-control)

When virtualbox is started on the host machine, prior guest additions are ignored and prior setvideomodehint resolution and color depths settings are ignored. The default capture host-key dialog is shown as if no prior guest additions are present.

If the incompatibility between 5.1.2X guest additions and 5.2 is a known issue, this should be clearly stated in the changelog as it impacts remote headless guest access that guest users cannot correct without access to the host machine.

Secondly, after 5.2 guest additions are installed from the host, and the guest and virtualbox shut down, the guest can then be restarted headless and access remotely. setvideomodehint on the host must be reset to restore 32bit display color depth for remote access. Video performance within the headless guest is degraded compared to 5.1.28 with lagging window moves within the Win7 guest and artifacts at the window corners on repaint that were not present in 5.1.28. (this is with 2D accell only, no 3D or aero active)

Please let me know what additional information you may need to help with this bug and I'll be happy to provide it.",drankinatty
17233,vm not start,Windows,other,VirtualBox 5.2.0,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
16886,4.x -> 5.x crash,Windows,Windows,VirtualBox 5.1.22,2017-11-15T21:27:54Z,2017-11-15T21:27:54Z,"I updated my virtual box from 4.* to 5.*, now my virtual PCs crash when I start them from any snapshot.

P.S. Can't get log from VM.",Mikha Mikhin
17278,Desplome de la Maquina virtual gana 10 al usar que Explorer,Windows,Windows,VirtualBox 5.2.0,2017-11-16T10:40:21Z,2017-11-16T10:40:21Z,"Iniciar Internet explorer, y en ocasiones sin hacer nada se produce un error 
critico, abrir una nueva pestaña, cerrar I E., no es posible hacer nada con
 I. E.

Produce un error y muchas veces cierra la maquina virtual.

solo es necesario abrir I.E. y cerrarlo.

host 1709 ( c de so 16299.64 )
guest 1709  ( c de so 17035.1000 )

con guest windows 8.1 ocurre muy parecido, pero no cierra la maquina virtual
",Josep Maria Mercé Currià
17279,Not Responding when going to settings after upgrade,Windows,all,VirtualBox 5.2.0,2017-11-16T12:10:05Z,2017-11-16T12:10:05Z,"Upgraded to 5.2 - When going to settings of any previous or new VM - it
freezes and says ""not responding"". it never recovers and you must force close
VirtualBox. Just had a couple of Windows updates prior to this upgrade.
(KB4049011) and (KB4048954)
Windows 10 Pro Version 1703
SurfaceBook",marshef
17286,OSType and longmode don't stay in sync (eg OSType Debian_64 but longmode is off),all,all,VirtualBox 5.2.0,2017-11-18T05:51:39Z,2017-11-18T05:51:39Z,"I am working with a VM that has several snapshots taken when the OSType was set to Linux 32-bit but I have since switched the OSType to Debian 64-bit. What I have noticed is if I restore a snapshot that was taken with a 32-bit OSType it will still say Debian 64-bit, and it appears it is not a per-snapshot value.

If I want to boot with 64-bit support after working in a 32-bit snapshot (ie longmode disabled) I have to switch from Debian 64-bit to Debian 32-bit, click OK, go back again switch back to Debian 64-bit and click OK. That will set longmode on. This caused me a lot of confusion because when I had checked the OS I couldn't figure out why it was crashing, since it said Debian 64-bit, then I did some diffs comparing to a new VM and realized what happens.

I think OS_Type should be a per-snapshot value. Basically you shouldn't show Debian 64-bit when 64-bit is not actually supported (ie longmode disabled). I think that is a reasonable assumption.

Version 5.2.0 r118431 (Qt5.6.2)
",quiettime
17287,Guest crashed when connecting to remote system using Remote Desktop,Linux,Windows,VirtualBox 5.2.0,2017-11-18T06:00:24Z,2017-11-18T06:00:24Z,"The title says it all. And I wouldn't even bother opening a new ticket if it happened once, but it actually happened twice in a row. There was no guru meditation. The guest window simply disappeared. I restarted the guest and tried to establish connection to remote system, and again the same thing happened. On the third attempt the connection was successful, but there might be something in the log files from those 2 sessions that will allow you to find and fix the bug. ",Rafcio
17289,'Take Screenshot' doesn't remember last directory location,all,all,VirtualBox 5.2.0,2017-11-18T06:43:18Z,2017-11-18T06:43:18Z,"I just used 'Take Screenshot' to take a bunch of screenshots and for each screenshot I wanted to save I had to switch to the directory that I had used to take the previous screenshot. In other words I wanted all the screenshots in one folder that was not my VM folder.

My suggestion is that you change VirtualBox to remember the previous location. My host is Windows and in that OS it's commonplace to use the last selected location.

Version 5.2.0 r118431 (Qt5.6.2), Windows 7 host.
",quiettime
17288,Crash while installing DirectX 9.0c on Windows 98,Windows,Windows,VirtualBox 4.3.36,2017-11-18T11:24:32Z,2017-11-18T11:24:32Z,"While following forum instructions https://forums.virtualbox.org/viewtopic.php?f=2&t=59559

The critical error guru box showed up and suggested I submit this ticket.

My virtualbox version is actual 4.3.40 r110317. On that note, this new ticket form has the version list all out of order, could that be sorted?

The host system is Windows 7 64-bit",Brrwrist
17292,VirtualBox-5.2.0-118431-Win.exe post install causing NetBT errors in Event Log,Windows,Windows,VirtualBox 5.2.0,2017-11-19T21:11:16Z,2017-11-19T21:11:16Z,"After i installed VirtualBox-5.2.0-118431-Win.exe along with the Guest Additions on a 64 bit Windows 7 machine i continually get the following errors every few seconds in the Event Logs.  I downgraded back to 5.1.30 and the errors stopped.  So, 5.2.0 has some bugs with the NIC.  I am using NAT for Host Network settings and disabled all other NIC cards.  The only active NIC is the Wireless NIC: Intel(R) Dual Band Wireless-AC 7260

Here is the error with attachment:

Level	Date and Time	Source	Event ID	Task Category
Error	11/18/2017 10:37:24 AM	NetBT	4321	None	""The name """"WORKGROUP      :1d"""" could not be registered on the interface with IP address 10.0.2.15. The computer with the IP address 10.0.2.2 did not allow the name to be claimed by this computer.""
",kingpoop
17295,VM doesn't works after last windows10 upgrade on Host,Windows,Windows,VirtualBox 5.2.0,2017-11-19T23:57:44Z,2017-11-19T23:57:44Z,"Windows 10 running on host, and VMs (Windows10) works fine until the last Windows10 on host
After this update, VM can be launch (I have a Virtual Box 5.0 installed),
So I upgrade Virtual Box to 5.2 and I can launch the VM.
The problem is VM have a black screen ...
I remove the additional guest on my vm, no change.
from now all my VMs are out of order

",dingdingdong
17148,5.1.28 r117968 (Qt5.6.2) VBoxTray.exe bug,other,other,VirtualBox 5.1.28,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
4456,Direct support for ZFS would be nice,other,other,VirtualBox 3.0.0,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
17297,critical typo in documentation for installation of Linux Guest Additions,all,Linux,VirtualBox 5.1.30,2017-11-20T14:13:12Z,2017-11-20T14:13:12Z,"The last sentence of section 2.3.2 of the VirtualBox documentation reads as follows:

----------------------------------------------------------------
If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running (as root) the following command:

rcvboxdrv setup
------------------------------------------------------------------

The command cited (""rcvboxdrv"") does not exist. I believe that what was intended is as follows:

---------------------------------------------------------------------
If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running (as root) the following command:

rcvboxadd setup
----------------------------------------------------------------------

While this might be obvious to someone with experience with Virtualbox, it is likely that any user who actually needs to read that documentation will find it difficult to correct the error that is returned when s/he tries to follow what is written:

---------------------------------------------------------
-su: rcvboxdrv: command not found



",sbpetrack
17254,VM inaccessible due to guest additions attach issue,Windows,other,VirtualBox 5.2.0,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
17009,Windows XP SP3 VM application error on VirtualBox 5.1.26 on Windows hosts,Windows,Windows,VirtualBox 5.1.26,2017-11-22T02:42:41Z,2017-11-22T02:42:41Z,"Windows XP SP3 VM consistently causes application error within 10 minutes from startup on VirtualBox 5.1.26. This error happened on three different Windows host PCs.  Error occurs with VirtualBox 5.1.26 running on Windows 10 64 bit host or on Windows 7 64 bit host.  The error message from a Windows 10 host PC is ""The instruction at 0x00007FFADAF76D43 referenced memory at 0x0000000000000018. The memory count not be read."" (see attached image). Windows 7 host may of had a different instruction address but it still had the ""referenced memory at 0x00000018"" text.  No special action was performed to cause the error. I downgraded to 5.1.24 on a Windows 10 host and the XP VM ran very stable with the error happening only once after days of use. I only tested on Windows hosts and not on Linux hosts.",Nick1
17272,My Windows 10 crash when I try to start the install of a linux vm,Windows,other,VirtualBox 5.2.0,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
17303,"No obvious way to exit snapshot ""Properties"" without changes",Linux,all,VirtualBox 5.2.0,2017-11-22T22:06:27Z,2017-11-22T22:06:27Z,"In vboxmanage, Snapshots view, if an existing snapshot is selected and then the ""Properties"" button is pressed, a large editable form appears. It has ""Reset"" and ""Apply"" buttons but they are grayed out if no changes have been made (as they should be).

The problem is, there is no apparent way to make the form go away without making any changes.

I suggest adding a ""Cancel"" button which closes the form without making changes (and discarding changes if entered).  Most users will immediately understand it's function, since many dialogs in Linux and Open Office work that way (for example).",Jim Avera
17310,virtualbox extension pack accept-license issue,other,other,VirtualBox 5.2.0,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
17313,Feature: Keyboard scancode translation,other,OSX Server,VirtualBox 5.1.30,2017-11-26T06:16:09Z,2017-11-26T06:16:09Z,"Most modern keyboards use IBM scancodes, and so VirtualBox users are likely to get fairly consistent behavior when sending these scancodes to just about every VM, via VBoxManage controlvm <vm> keyboardputscancode <hexpair>... However, macOS guest VM's use a different scancode set, one for Apple keyboards. This does not present a problem for most graphical VirtualBox users, however it does break some things for command line driven systems such as packer.io. In particular, systems like packer that are built on top of VirtualBox and want to send key codes to macOS VM's are faced with the nuisance of performing scancode translation. I propose that VirtualBox offer a VM configuration option like:

VBoxManage modifyvm <VM> --fromscancodes ibm --toscancodes apple

or similar flag syntax, that declares that VirtualBox should automatically remap scancodes sent via VBoxManage controlvm <VM> keyboardputscancode <hexpair>..., relieving packer and other tools from having to worry about such low level details (packer could then simply use IBM scancodes all the time).

I've also filed a ticket with packer to select more appropriate scancode sets for different kinds of VM's:

https://github.com/hashicorp/packer/issues/5635

As a mac user, I really don't care which of these is implemented, I just want to be able to use macOS guest VM's without having to hack around keyboard incompatibility issues!",mcandre
17314,V 5.2.2 doesn't work and cannot be unistalled,Windows,Windows,VirtualBox 5.2.0,2017-11-26T22:03:29Z,2017-11-26T22:03:29Z,"I downloaded and installed the latest release over a 5.1 release under Win10. When I attempted to run an XP VM used 15 mins earlier it saied teh Extensions were out of date. I attempted to installed the new extensions but it failed with an URL error on the validation. So now I could not run my XP machine. I deleted the VM and tried to uninstall VirtualBox. That was rejected - cannot access path - you may not have authority, (I run as administrator). Nor would it let me modify the installation. Can anyone tell me how to get out of this mess, please? ",Benjiboy
17317,scaled mode in ubuntu 17.10,Linux,Linux,VirtualBox 5.2.0,2017-11-27T15:25:10Z,2017-11-27T15:25:10Z,"Depending on the state (seems scaled first). when going back to normal mode, the VM 
is not responsive to keystrokes.  They appear to buffer, when returning to scaled mode 
they will then show up.

Speculation is on the new WM that comes with 171.0

Saw with with 5.1.28, 5.2.0 and 5.2.2",chad
17319,"""VBoxManage guestcontroll run"" stdin/out redirection not working",Linux,Windows,VirtualBox 5.1.30,2017-11-28T15:18:10Z,2017-11-28T15:18:10Z,"I'm trying to run a python script inside a Windows 7-64bit virtual machine, redirecting stdin and stdout from/to Ubuntu 17.10 host.

GuestAdditions and python have been installed on the VM. I placed the python script on a shared directory.

The following commands never exits and does not echo anything until I pressed CTRL+C :

{{{
echo -1 | VBoxManage --nologo guestcontrol ""w764 Clone"" run --username Hector --password hectorH --exe ""C:\Python27\python.exe"" --wait-stdout -- E:\test.py
}}}

Here is the script ""test.py"":


{{{
print(""Hello"")
while True:
    s = raw_input()
    a = int(s)
    print(a)
    if a < 0:
        break
}}}

I first tried to run it inside a windows terminal on the VM, and this works:

{{{
c:\> c:\python27\python.exe E:\test.py
Hello
-1
-1
}}}

To make sure the login parameters are ok, I run iexplore with success:
{{{
VBoxManage --nologo guestcontrol ""w764 Clone"" run username Hector --password hectorH --exe ""C:\Program Files\Internet Explorer\iexplore.exe""
}}}
",shangouet
17322,VirtualBox 5.2.x guest additions hang Poser 6 & 7 on startup under XP guest,Linux,Windows,VirtualBox 5.2.0,2017-11-28T15:51:27Z,2017-11-28T15:51:27Z,"I already reported this issue under [https://www.virtualbox.org/ticket/17152 Ticket #17152] (for 5.2RC), but 5.2.0 was released shortly after and it looks like that ticket got overlooked/ignored entirely, so I'm opening a new ticket for VirtualBox v5.2, since the bug is still there...

With VirtualBox v5.2.2 and its extension pack installed, and after booting my Windows XP guest VM (with corresponding v5.2.2 guest additions installed), when I start Poser 6 or 7 (the only two versions I got) on a Windows XP (32 bits) guest running on a 64 bits Linux host, the program hangs shortly after starting, on the startup screen, and Windows reports the program as ""non responding"" in its title bar. After a few more seconds waiting, the window of the program turns white and it stays stuck forever like that.

If I reinstall the v5.1.30 guest additions (still keeping VirtualBox v5.2.0 and its extension pack) Poser then works fine again.

Probably an issue in DirectX support ?
",dinosaur0
14296,Failed to create COM object - 0x80040154,Windows,other,VirtualBox 5.0.0,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
17327,alt tab within vm passes alt tab to windows 10,other,other,VirtualBox 5.1.30,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
15324,Mouse pointer offset in Linux client => fixed in releases higher than 5.1.4,other,other,VirtualBox 5.0.18,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
17328,Virtual Machine work very slowly,other,Windows,VirtualBox 5.2.0,2017-11-29T23:59:00Z,2017-11-29T23:59:00Z,"Hi, 
I have a very big problem with my VM's. Before installing the extensions pack, my virtual machines worked very well, did not jam, worked properly. I wanted to run USB 2.0 so I installed the Extension pack. After installing machines have slowed down, clipping. They have allocated 4GB of RAM, an Intel i5-3360M processor, 128MB of graphics memory and walk slower than computers before 15 years ago. What can I do to speed it up? On the I have an SSD hard drive installed. Please help me.

Karina

P.S. I have now Virtual Box 5.2.2 with extensions pack for this version. It still work very slowly.",Inka
17330,Ubuntu 17.10 guest freezes when restoring guest windows,Windows,Linux,VirtualBox 5.1.30,2017-11-30T00:08:01Z,2017-11-30T00:08:01Z,"Okay, so this is driving me nuts. Running VB 5.1.30 on a windows 7 host with a Ubuntu 17.10 (desktop) guest OS. 

I installed the guest additions without issue, though I read here https://forums.virtualbox.org/viewtopic.php?f=6&t=85186 that Ubuntu comes with a set of guest additions installed by default that may cause issues, not sure if that's relevant.

Everything works fine (for the most part) but when I enable 3d acceleration (host has a gtx1070) it runs smoothly... until I 'restore' (un-maximize) a window within the guest. 

Then the machine freezes (any actions take 3-10 seconds for a response) and begins consuming as much as 15-17% of my (i7) cpu and even slowly getting the original window to close in the guest does not restore it's usability or reduce it's cpu consumption. 

Disabling 3d acceleration allows the machine to run stably however it's not very smooth comparably, and simulating both my 2560x1440 monitors makes the machine so sluggish it's not usable.

Any hints to why this would be happening and how to fix it would be much appreciated.",DMeganoski
17285,Mapping shared folder fails if USB drive is connected after VM is started,Linux,Windows,VirtualBox 5.1.30,2017-11-30T06:50:57Z,2017-11-30T06:50:57Z,"This basically is ""reopening"" of ticket #11445 (https://www.virtualbox.org/ticket/11445#comment:1) . The issue is still present in version 5.2.
",Rafcio
17270,Scrolling with mouse integration,Windows,Linux,VirtualBox 5.1.30,2017-11-30T16:20:57Z,2017-11-30T16:20:57Z,"While using VBox 5.1.30 with Mouse Integration turned on the wheel scroll event is not passed to some windows while moving the mouse. If mouse is stationary the scroll is registered fine. It happens over Chrome, Firefox, GTK windows, but works fine for Java and urxvt windows.

I've already tried it with libinput and evdev on the guest Fedora 26 system. The behavior is the same.

Thank you.

Yaroslav",Yaroslav
17180,Unable to get properly into full screen after VM resume,Mac OS X,Linux,VirtualBox 5.1.28,2017-11-30T22:15:48Z,2017-11-30T22:15:48Z,"I recently noticed the following issue, after a recent update (version 5.1.28 r117968 (Qt5.6.2) under macOS):
after I resume a VM, it is unable to go to full screen; it also show two windows, one of which shows the state before resume and is frozen.

Steps:
- Run a VM (I had this happen with several Linux Guests)
- Have it work in full screen
- Save the machine
- Resume it; then the first anomaly occurs: two windows show the status of the VM; the first one is not full screen, and reacts to inputs; the other is full screen and does not react to inputs

After that it is sometimes possible to put back to full screen the window that started as non full screen, but the frozen full screen view never goes away.",Merrilin
17249,Opening VM Settings dialog can hang (infinite loop) if column is narrow,other,other,VirtualBox 5.2.0,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
17332,Windows taskbar is not visible,Linux,Windows,VirtualBox 5.2.0,2017-12-01T00:52:07Z,2017-12-01T00:52:07Z,"I've installed Ubuntu 17.10 and VirtualBox 5.2.2 r119230 (Qt5.9.1) when I star run Windows 7 Ultimate as guest, the windows taskbar is not visible in seamless mode",pigus92
17338,Rename repository name in virtualbox.repo (for Fedora distro),other,Linux,VirtualBox 5.2.0,2017-12-01T19:34:59Z,2017-12-01T19:34:59Z,"Repo file provided for Fedora (see link below) defines the repo's name as:


{{{
name=Fedora $releasever - $basearch - VirtualBox
}}}


Example: ''Fedora 26 - x86_64 - VirtualBox''

From a user perspective, in my personal opinion, it would make more sense to print something like

''VirtualBox - Fedora 26 - x86_64''


{{{
name=VirtualBox - Fedora $releasever - $basearch
}}}

This order would be more consistent with other repositories provided for Fedora, first naming the repository, followed by some info about release version and architecture.


Link: http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
",F
17326,Serial ports do not work correctly,all,all,VirtualBox 5.1.30,2017-12-02T06:15:06Z,2017-12-02T06:15:06Z,"Only serial ports COM1 and COM2 work in EFI mode. Any other serial port configurations are either not detected or do not perform any requested actions. EFI_SERIAL_IO_PROTOCOL seems to not be reliable in writing to the serial port, timeout happens before the timeout could have possibly passed, set to multiple seconds and it fails instantly. Trying to solve this by writing in a loop produces incorrect results as the size written is incorrectly reported so some data gets written multiple times. Also, garbage is always written to a serial port when the machine is started, sometime during post. This can be proven by assigning COM1 or COM2 to a Raw file output. I have attached an two examples. I have tested this in Windows, Linux, and macOS, so it appears to be a core EFI issue.",apianti
17341,~30% keyboard strokes reach VM for vbox 5.2.2 only,Linux,Linux,,2017-12-02T16:45:06Z,2017-12-02T16:45:06Z,"Host: Debian GNU/Linux 9 amd64, Extension Pack 5.2.2 installed
VM: Debian GNU/Linux 8 amd64

When reverted vbox (and extension pack 5.2.0) to 5.2.0, keyboard strokes reach 100% back again.

(Can't select Version for the ticket, due to lact of 5.2.2 version string in popup menu)",maestro
17339,"Windows 98 can't be installed on windows xp, but can on windows 10",Windows,Windows,VirtualBox 5.2.0,2017-12-02T22:42:05Z,2017-12-02T22:42:05Z,"When I put windows 98 se iso which is itself bootable, immediately, even before anything is read from it, app in my host windows xp os says ""VirtualBox.exe . Application Error"", ""The instruction at ""0x77c47631"" referenced memory at ""0x000c000c"". The memory could not be ""written"".""
Click on OK to terminate the program...

This is an all versions. Tested on xp pro sp3 with or without windows updates and addons like net framework, dx, vc redists...
I was never since i was born able to install windows 98 while using windows xp.

Windows XP cd boots when used in for win98 settings.",nijazxp
17340,Windows PosReady 2009 doesn't work,Windows,Windows,VirtualBox 5.2.0,2017-12-02T22:49:27Z,2017-12-02T22:49:27Z,"I do not even know did i install it, but i think there were various errors even during isntall, hell I forgot...
Anyway now when I start os it's giving bsod in guest os DRIVER UNLOADED WITHOUT CANCELLING PENDING OPERATIONS. And at the same time my host os windows xp pro sp3 says The instruction at ""0x121d39d4"" referenced memory at ""0x00000008"". The memory could not be ""read"".

So let's conclude: Posready 2009 is not supported by virtualbox???
Regardless is it install or running of that os or somewhere in between or both.

Posready 2009 is downloaded as preview directly from microsoft.com and size is less than GB, or few hundreds MB.
https://www.microsoft.com/en-us/download/details.aspx?id=11196",nijazxp
17344,VirtualBox 5.2.x installer: ProductID in MSI File and ProductID on installed system do not match,Windows,other,VirtualBox 5.2.0,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
17202,Please add Ubuntu 17.10 (artful) Support to the PPA,Linux,all,VirtualBox 5.2.0,2017-12-04T13:43:20Z,2017-12-04T13:43:20Z,Please add Ubuntu 17.10 (artful) Support to the PPA,Neti_Netwalker
17117,"Host Win7 x64, Guest Win7 x64, microphone not working after upgrade to 5.1.28",Windows,Windows,VirtualBox 5.1.28,2017-12-04T16:27:50Z,2017-12-04T16:27:50Z,"Dear support

Host Win7 x64, Guest Win7 x64, Intel HD Audio,  microphone is detected but input is not working any more after upgrade from VB 5.1.26 to  5.1.28 r117968 (headset mic analogue 3.5mm jack). In host or VmWarePlayer machine it works (Win7 - sound recording tool, Skype, Win settings test etc.). Uninstallation of Intel HD audio driver caused automatic installation after restart, but it did not help. After downgrade to 5.1.26 VB refuses to use virtual drive file already used in VB 5.1.28 (inconsistent helper structure). Please try to record sound using Intel HD Audio analogue microphone in fresh Win7 x64 guest in VB 5.1.28.

Thank you
Best regards
Jiri",DevTc
17346,No machine can be started on MacMini 10.12.6 host,Mac OS X,all,VirtualBox 5.2.0,2017-12-05T09:19:14Z,2017-12-05T09:19:14Z,"Hi, i wrote in the forum and they told me to open a bug.

I bought a macmini with 10.13 preinstalled and installed 10.12.6.
Virtualbox installer is running without errors, and i can add machines. As soon as i start a machine (xp, mac, ubuntu, any....) it write an error and guru meditation.

kextstat | grep -v com.apple

{{{
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  132    3 0xffffff7f83292000 0x63000    0x63000    org.virtualbox.kext.VBoxDrv (5.2.2) 62C4748E-00E8-38C9-8820-3C8791212EA9 <7 5 4 3 1>
  134    0 0xffffff7f832f5000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.2) 9C6CEA90-40EE-323B-8A1F-AF84BC91E127 <133 132 40 7 5 4 3 1>
  135    0 0xffffff7f832fd000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.2) 5A0170AB-E76F-3CCE-A017-2FB020D6BFD0 <132 7 5 4 3 1>
  136    0 0xffffff7f83302000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.2) 5B0F7EF3-7B51-3AA7-B60C-5C9615288D9A <132 5 4 1>
}}}

Hope you can help me",_michael
17348,Virtualbox built-in debugger does not work,all,other,VirtualBox 5.2.0,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
17355,Key fingerprint in downloads area cannot be verified,other,other,VirtualBox 5.2.0,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
17224,VM crashes after input switch with KVM switch,other,other,VirtualBox 5.2.0,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
17349,VINF_EM_TRIPLE_FAULT,Windows,Linux,VirtualBox 5.2.0,2017-12-07T02:13:13Z,2017-12-07T02:13:13Z,"I get guru meditation immediately after the Virtualbox BIOS screen and the log says VINF_EM_TRIPLE_FAULT. This is in a guest machine where I just freshly installed RHEL 7.4 64 bit running on Windows 7 64 bit host. The guest started to boot the first start after I installed RHEL but triple fault occurred before boot finished. Every other boot gets triple fault immediately after the Virtualbox BIOS screen. I see lots of other triple fault bugs but none for Red Hat.

Error occurs on latest stable and latest testing builds

Stable
VirtualBox-5.2.2-119230-Win.exe

Testing
Version 5.2.3 r119405 (Qt5.6.2)",ke
17239,Serial port missing characters.,Windows,Linux,VirtualBox 5.2.0,2017-12-07T08:32:04Z,2017-12-07T08:32:04Z,"Using 'Windows 10' as host, and being Linux 'Ubuntu 14.04 LTS' as guest, with 
Virtual Box 5.2.0 and its associated guest additions, once the guest Ubuntu has
been launched, by using the serial port: /dev/ttyS0, from within the guest, some 
characters are missed (they don't appear in the serialized stream of data 
shown in the terminal's screen).

This problem is also present in other versions of virtual box (for example: 
5.1.18). On the other hand, this issue works fine under Windows 7 as host 
using virtual box 5.1.18.

¿Perhaps is there some incompatibility between guest additions and windows 10?
",jim_
17359,Bug in VirtualBox 5.2.2,other,other,VirtualBox 5.2.0,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
5598,ReactOS not listed under OS,Windows,Windows,VirtualBox 3.0.12,2017-12-08T15:30:40Z,2017-12-08T15:30:40Z,"Dear VirtualBox support,
I test ReactOS with VirtualBox, it works ver well, it's even listed in the OS matrix, but it isn't available as an OS in VirtualBox itself, could you please add it?
Best regards.

Gabriel.",gabriel
17362,Cannot map network drive to vboxsvr file,Mac OS X,Windows,VirtualBox 5.2.0,2017-12-09T16:03:06Z,2017-12-09T16:03:06Z,"I am using VirtualBox on a macOS Host running a Windows 7 guest. I would like to map a network drive to Network\VBOXSVR\then a subdirectory. Windows objects with ""Windows cannot access \\VBOXSVR\the subdirectory"".
",Horatio
16854,virtualbox does not build reproducibly,other,other,VirtualBox 5.1.22,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
16741,"When installing Guest Additions from CD image, first uninstall packages shipped with client OS",Mac OS X,Linux,VirtualBox 5.1.22,2017-12-11T05:25:58Z,2017-12-11T05:25:58Z,"Motivation:

I was having difficulties with NetBeans 8.1 (the version installed by Software Manager on the guest OS, I didn't try the more recent NetBeans 8.2 but I don't suspect that it would make a difference) on a 64-bit GNU/Linux Mint 18.1 Cinnamon guest (on an Apple macOS host) that I *suspect* are related to VirtualBox Guest Additions. The manifestation is presumably an exception related to the pasteboard (see later), which then results in incomplete application startup (stuck at splash window), then a new application launch resulting in NetBeans minimally sized on top left corner of screen, an exception report in the IDE (some class not found), Project pane absent (C++), quitting during Reset Windows, ...unless I forgot something, but it's a real show-stopper.

Reproducing and avoiding:

After several tries, the problem seems to reappear whenever Guest Additions are installed from a CD image (I noticed this a few times), but I don't know whether I could reproduce from scratch. When I reinstalled a whole new VM from scratch (once, because it takes a while), and did a complete removal of 3 pre-installed virtualbox-guest-* packages as the first step after installation (those were on the guest OS installation .iso), after updating the client OS and then installing Guest Additions from CD image, I got an apparently stable-running NetBeans 8.1.

Suggested solution:

Could the script that installs the Guest Additions first detect which package manager is used in the current environment and propose to the user to uninstall the virtualbox-guest-* packages (or however they are called on each guest OS)? Even if the analysis above doesn't pan out, it doesn't seem like a bad idea to just always do that... and warn the user not to reinstall those packages later!

Further (de)motivation:

I don't know whether it still helps if the guest OS was already updated, but my hunch is that it's not a good idea to have both active and possible interfering with each other, and then perhaps letting a guest OS update overwrite the version installed by VirtualBox, etc. But if it is relevant, it would help the user avoid trouble.",RafSchietekat
17235,5.2 causes blue screen of death on windows 10,Windows,Linux,VirtualBox 5.2.0,2017-12-11T20:00:20Z,2017-12-11T20:00:20Z,"I upgraded from 5.1.30 to 5.2 to use my ubuntu 17.04 and 17.10 machines. I had multiple BSOD per hour until I reverted to 5.1.30. No BSOD since then.

I have a Surface Pro 4 with the latest Windows 10 updates.

Sorry, I could not capture the error code or QR on the blue screen before the PC rebooted.",silvermangb
10958,Windows guest does not recognized Broadcom 5880 smart card reader,Windows,Windows,VirtualBox 4.2.0,2017-12-12T06:27:22Z,2017-12-12T06:27:22Z,"I have a Dell Latitude E6520 with a built in Broadcom 5880 smart card reader that refuses to work inside my Windows Guest OS. Some relevant notes:
* the 5880 reader works fine on my host system. 
* if I plug in an external USB smart card reader (SCR3310), that works fine inside the guest OS
* the built in 5880 reader works fine in a guest if I use VMware.

Virtual box will allow me to connect the 5880 from the USB devices menu. It then indicates a lot of flashing red/green lights on the USB icon, but my smart card software inside the guest (ActivClient) does not recognize that a reader is present. Inserting/removing the card has no effect.

My configuration:
* Windows 7 64-bit Professional on the host, 8GB RAM
* Windows 2008 R2 64-bit as the guest, 3.5GB RAM

I just updated to VirtualBox 4.2 but have tried this on a bunch of previous 4.0 and 4.1 versions. I was hoping this would eventually be fixed. My googling through the community indicates that others have had this problem and it has never been solved.

Any idea how to make this work or whether it will be fixed?
",armillz
17252,"Resume fails with 0x80004005, sometimes after an hour",all,Windows,VirtualBox 5.2.0,2017-12-12T07:24:52Z,2017-12-12T07:24:52Z,"I'm having, and I always had as far as I can remember, issues resuming virtual machines. Sometimes it works, but usually fails with 0x80004005 and I have to discard the state. This happened with mixed host machines and host os. In this moment I'm on a linux host with an xp guest.

I noticed a difference in the detected gl library version between the vbox log files when the machine fails resuming and when it starts correctly:

This is a normal startup:
{{{
00:00:00.714721 Console: Machine state changed to 'Running'
...
00:00:19.772224 gl version string: 03.0 Mesa 17.0.7
00:00:19.772243 gl version: 0x30000
00:00:19.772246 gl extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color [...]
}}}

This is a failed resume (immediate crash):
{{{
00:00:05.617476 Console: Machine state changed to 'Running'
00:00:05.618122 gl version string: 04.5 (Core Profile) Mesa 17.0.7
00:00:05.618129 gl version: 0x40500
00:00:05.618133 gl extensions: <NULL>
<<crash>>
}}}

This is a ""working"" resume where there is no reference to gl version in the logs up to 52 minutes after the resume, and then immediately we have a crash:
{{{
00:00:02.483845 Console: Machine state changed to 'Running'
00:00:02.503065 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1920x1107
00:00:02.510500 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
00:00:02.510527 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
00:00:02.510986 OpenGL: Set 3D content scale factor to (10000, 10000), multiplier 10000 (rc=VINF_SUCCESS)
00:00:02.511007 OpenGL: Set OpenGL scale policy on HiDPI displays (fUnscaledHiDPI=0)
00:00:02.579089 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:02.579105 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:02.579686 GUI: 2D video acceleration is enabled
00:00:02.579695 GUI: HID LEDs sync is not supported on this platform
00:00:02.583994 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
<<After 52 minutes of normal work>>
00:52:02.223175 gl version string: 04.5 (Core Profile) Mesa 17.0.7
00:52:02.223247 gl version: 0x40500
00:52:02.223267 gl extensions: <NULL>
<<crash>>
From dmesg:
[ 3335.532765] VirtualBox[2688]: segfault at 0 ip 00007f5db4a390bd sp 00007ffc7916fd78 error 4 in libc-2.23.so[7f5db498f000+1c0000]
}}}

glxinfo says:

{{{
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Kabylake GT3  (0x5926)
    Version: 17.0.7
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
}}}

So when it detects 04.5 core profile it crashes, when it detects 03.0 compatibility profile it works. I now disabled 3D accel but I used to have it disabled so I'm not sure this will change anything.
",ctrl
16449,Flashing ROM on USB device fails,Windows,Linux,VirtualBox 5.1.14,2017-12-12T10:11:07Z,2017-12-12T10:11:07Z,"I'm working with a custom device so there isn't an obvious way to reproduce the problem. When we flash the ROM on our custom USB device from Linux as a guest of Windows using VirtualBox, the process fails at the beginning of the process. One thing of note is that our device uses a different device ID when it's waiting to be flashed and when it is operating normally. This required 2 USB Device Filters to be added to VirtualBox. Thus process works on VMWare and on native Linux.
",capellsk
15553,USB 1.1 (OHCI) controller stops working after a period of time,Windows,Linux,VirtualBox 5.0.22,2017-12-12T10:11:26Z,2017-12-12T10:11:26Z,"I have 2 identical FTDI Quad RS232-HS USB virtual serial port chips connected to a Ubuntu 12.04.5 LTS guest running on Windows host (behaves the same on Win7x64 and Win10x64).
I am using USB 1.1 (OHCI) controller, but the FTDI chips are physically connected to the host via USB2.0 ports.
On VirtualBox 4.3.12 everything works just fine.
On higher versions (I tried 4.3.38, 5.0.22, 5.0.23, 5.1.0 Beta 3) I am able to open the virtual serial ports and read and write data to them for a few minutes (maybe 5) after which the communication stops and no data can be sent nor received.
When monitoring the USB ports on the guest with usbmon+wireshark, I can see no packets being sent or received after it stops working.
This only happens when 2 are connected and open at the same time. One on its own doesn't do it.
When I install the extension pack and use USB3.0 (xHCI), the problem doesn't appear.

I am attaching two logs, one running USB1.1 and one USB2.0 controllers both manifesting the issue.",rp3k
17020,dd on USB drive results in Input/output error,Windows,Linux,VirtualBox 5.1.26,2017-12-12T10:11:41Z,2017-12-12T10:11:41Z,"Since version 5.1.22 and probably earlier I cannot write images to my USB SD card adapter anymore. Especially when writing larger images such as 4 GB of Raspbian I see the following error after some minutes:

{{{
debianguest:~$ time sudo dd if=/dev/loop0p2 |pv -s 4300M |sudo dd of=/dev/sdc2
dd: writing to '/dev/sdc2': Input/output error                ] 34% ETA 0:17:38
3068849+0 records in
3068848+0 records out
1571250176 bytes (1.6 GB, 1.5 GiB) copied, 567.657 s, 2.8 MB/s
1.46GiB 0:09:27 [2.64MiB/s] [==========>                      ] 34%            

real    9m27.844s
user    0m5.073s
sys     0m43.153s
}}}

Something with the USB driver seems to be broken on Windows 10 hosts. It used to work correctly with earlier versions.

This is an update of bug #17019 with corrected fields.
",Frank Breitling
14875,USB ISO packets get stuck in VB 5.X,Linux,Windows,VirtualBox 5.0.10,2017-12-12T10:12:43Z,2017-12-12T10:12:43Z,"Hello VB,

After having used 4.X with great pleasure for a long time to debug Windows USB issues in Linux (Fedora), i have hit a snag in the 5.X series.

The problem is always the same. If i start streaming ISO packets they get stuck after a very short while. In the early 5.X builds the entire VM would implode, but now it just hangs the USB stream until i unplug the device.
There is some kind of bug in the 5.X USB implementation. If its the VB drivers in Linux or the virtual drivers in Windows is not clear to me.

Has anyone else seen this problem? I have tried all combinations of options i could think of but the problem persists.

I have attached a Wireshark trace that shows the problem up until the hang. Note that when this happens the *entire* USB freezes up, not just the ISO packets.

Thanks,

/pedro",donpedro
15927,USB Wifi Dongle drops connection after short period,Mac OS X,Linux,VirtualBox 5.1.6,2017-12-12T19:08:52Z,2017-12-12T19:08:52Z,"Trying to use a [https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb Think Penguin TPE-N150USB] USB WIFI adapter in close proximity to my router.

The guest VM will recognize and use the adapter just fine. I can usually connect to my wifi, but the connection drops after 5-10 seconds (usually as soon as I try to access any over it). Subsequent attempts to connect to any WIFI connection will fail. Result is the same for any network I try to connect to, and on several different linux's, though primarily with fully up-to-date Ubuntu 16.04 ( Kernel 4.4 and 4.6 for grins and giggles). USB 2 and USB 3 both yield the same result.

I have ruled out a problem dongle since if I boot natively into the same version of linux, the wifi connection works flawlessly. 

My  problem seems unrelated to [https://www.virtualbox.org/ticket/9511 Ticket #9511] since my drivers load properly. 

Not sure if its helpful, but I have a [https://forums.virtualbox.org/viewtopic.php?f=8&t=79442 Forum Post here] with more info. Forum Moderator says he doesn't experience a similar issue with Linux Host, so perhaps the problem is specific only to Mac hardware?

(VirtualBox version 5.1.6 w/ latest Extension Pack and Guest Additions)

Please let me know if there is any further information I can provide, or any troubleshooting I should attempt. 

",Briantb
16333,"""The installer has detected running Virtual Machines"" message is confusing",Mac OS X,all,VirtualBox 5.1.12,2017-12-13T10:41:25Z,2017-12-13T10:41:25Z,"This error message is shown if I happen to have the VirtualBox UI running when attempting to update VB on a Mac - even if all VMs have been shut down.

As ""klaus"" mentioned in #12392 the error message is confusing.",vpvainio
17370,Unknown USB device detected,Windows,Linux,VirtualBox 5.1.22,2017-12-14T21:27:57Z,2017-12-14T21:27:57Z,"00:00:00.054173 USB: Unknown USB device detected (idVendor: 0x096e, idProduct: 0x0007). Please, report the idVendor and idProduct to virtualbox.org.

It's enough for ""report""?",igm
17373,vbox driver does not compile with kernel 4.14.5,Linux,Linux,VirtualBox 5.1.30,2017-12-15T17:36:32Z,2017-12-15T17:36:32Z,"Hello,

I try a 4.14.5 kernel and the Vbox driver does not compile.
The trace is included.

Regards

JP P",jppo
17358,Guru Meditation when starting Windows 10 VM on Linux after 5.2.2 upgrade,Linux,Windows,VirtualBox 5.2.0,2017-12-18T17:31:40Z,2017-12-18T17:31:40Z,"After the Upgrade from VirtualBox 5.2.0 to VirtualBox 5.2.2 the vm no longer starts, it fails with a guru meditation. 

Surprisingly only Windows 10 appears to be affected, any Linux, even ReactOS are working as expected.



The requested PNG file only shows a black screen, little helpful so i only attached the logfile. ",Jörg Skottke
17378,/sbin/vboxconfig fails during upgrade of Vbox to 5.2.2,Linux,Linux,VirtualBox 5.2.2,2017-12-18T19:52:19Z,2017-12-18T19:52:19Z,"Current system is Fedora 28 x86_64 (Rawhide).

Install of VirtualBox released version fails during config. The developer version fails as well... with the same error message (see inclosed install log).",George R. Goffe
16771,Qubes install ISO fails to run,Windows,Linux,VirtualBox 5.1.22,2017-12-18T22:58:20Z,2017-12-18T22:58:20Z,Am attempting to run install Qubes OS from ISO [https://www.qubes-os.org/downloads/] on 64 bit host using 64 bit Virtualbox and 64 bit VM environment. Was able successfully install Qubes on 1 of 3 different hosts: Dell Latitude E5420. Failed on Surface Pro 4. Also failed in Lenovo Think Center.,mutsuura
16815,VirtualBox 5.1 disables iSight camera on MacBook Air with MacOS Sierra,Mac OS X,all,VirtualBox 5.1.22,2017-12-20T15:15:04Z,2017-12-20T15:15:04Z,"Steps to reproduce:

1. On a clean system, launch the FaceTime app to verify the camera is working
2. Install VirtualBox 5.1.22 using the downloaded dmg
3. Reboot
4. Launch the FaceTime app again

Observed:
The FaceTime app launches with a black screen. The Camera LED does not turn on and the system information indicates the camera is not detected.

Expected:
The camera turns on and in unaffected by the virtualbox installation.


Similar issue with Parallels: https://forum.parallels.com/threads/parallels-desktop-disables-isight-camera-on-macbook-pro-with-os-x-sierra.338294/",bulgur
17384,ElementaryOS Loki not usable with 3D enabled -> unlikely to be fixed in near future,Windows,Linux,VirtualBox 5.2.4,2017-12-21T09:05:22Z,2017-12-21T09:05:22Z,"If I activate 3D support, the Desktop turns black or is not usable at all, that is I see the Icons, but nothing happens.

This issue persisted for some time now and I had hoped with the latest release which also fixed a 3D issue for GDM, this would be solved now. Obviously it is not.",jeansen
17377,VirtualBox 5.2.2 issues on Xubuntu 16.04 x64,Linux,Linux,VirtualBox 5.2.2,2017-12-21T09:45:06Z,2017-12-21T09:45:06Z,"Hi,

Last night I uninstalled VirtualBox 5.1.30 from my Xubuntu 16.04 x64 system, deleting all relative files and I did a brand new 5.2.2 installation from scratch. The new installation is facing two issues:

1. It doesn't use the system GTK theme whereas 5.1.30 did. All other GTK, QT4 and QT5 apps do use it, since the system is correctly configured for this.

2. Shared folder auto-mount doesn't work on Xubuntu 16.04 x64 guests whereas it works fine on Windows guests. On Xubuntu guests I have to mount it manually using ""mount -t vboxsf -o uid=1000,gid=1000 shareName /media/sfPublic"". This command mounts it correctly with read/write access.

Thank you.

p.s. The guest additions have been installed of course, using ""sh ./VBoxLinuxAdditions.run"".",StormLord
17387,USB Dongle not recognized correctly,Windows,Linux,VirtualBox 5.1.22,2017-12-21T13:56:46Z,2017-12-21T13:56:46Z,"Host: Windows 10 Pro x64
Client: Ubuntu 16 LTS
VirtualBox: 5.1.22r115126 with ExtensionPack

Synopsis:
An USB-Dongle (Dinkey Pro Lite Mini) is plugged in and gets not recognized correctly from the VirtualBox.
I have to disable/enable this ""Human Interface Dongle / USB Input Device"" from the device manager (or replug it) once after starting the VB. This is an issue only with the Windows 10 OS.
The same setup (dongle, VB) on Windows 7 is working perfectly.

Attacments:
logs.zip: Logs from Machine => Show Log...
usbhost1.log: usb host list after virtual box start
usbhost2.log: usb host list disable/enable the specified USB Input Device
01.jpg: Screenshot after virtual box start
02.jpg: Screenshot disable/enable the specified USB Input Device

The correctly attached device name is ""OEM HID Dongle [0106]"". If the Dongle is recognized correctly as OEM HID Dongle the serial number is attached correctly.
",igm
17383,VirtualBox crashed with SIGABRT,other,other,VirtualBox 5.2.4,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
17379,https for download.virtualbox.org is wrongly configured,other,other,VirtualBox 5.2.2,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
17388,PCI passthrough fails with general protection fault in VBoxPciRawR3.so,Linux,all,VirtualBox 5.2.4,2017-12-21T21:37:03Z,2017-12-21T21:37:03Z,"starting a VM with a PCI device attached fails with a segfault in VBoxPciRawR3.so.

{{{
kernel: traps: EMT-0[15909] general protection ip:7f846c2b908f sp:7f84923cccd0 error:0 in VBoxPciRawR3.so[7f846c2b6000+c000]
}}}

This is 100% reproducible.

Linux kernel version 4.14.8-1-ck",Thermi
17381,virtualbox additional functions are uninstallable,Windows,Linux,VirtualBox 5.2.4,2017-12-22T06:20:14Z,2017-12-22T06:20:14Z,"host computer:windows10 64bit
guest: ubuntu 16.04.3
When I click install additional functions, an error raised.

未能加载虚拟光盘 C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso 到虚拟电脑 ubuntu.



Could not mount the media/drive 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED).

返回 代码:E_FAIL (0x80004005)
组件:ConsoleWrap
界面:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
被召者:IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",f-sky
14978,Error In supR3HardNtChildWaitFor,Windows,Linux,VirtualBox 5.0.12,2017-12-22T06:27:04Z,2017-12-22T06:27:04Z,"Hello,
I get this error on startup since 5.0.8 (also on .10 and .12).
Key Host Info:
- Lenovo x250 16GB RAM, 512 SSD
- Host win7 (latest patches some win10 upgrade stuff suppressed)
- guests: debian (but probably irrelevant)
- avira antivir antivirus
- comodo firewall

When I start vbox, after a while I get the following error:
---------------------------
VirtualBox - Error In supR3HardNtChildWaitFor
Timed out after 60001 ms waiting for child request #1 (CloseEvents).
(rc=258)
where: supR3HardNtChildWaitFor
what:  5
Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)
---------------------------

If I do not close it and wait a while (another minute or so) I get it again, and then the guest opens just fine. See this bug description:
https://forums.virtualbox.org/viewtopic.php?t=64111&f=6#p301426 (way back from Oct 2014 and 4.3.18)
...it is essentially this. If I close any of the dialogs, then the guest does not open. Attached are the logs (from 5.0.10, I can recreate with .12 if desired) and a screenshot of the errors. The logs appear normal.

Thanks
Nils
",Nils
17390,"Received a ""VirtualBox Manager has stopped working"" error when I click on import appliance or ""New""",other,other,VirtualBox 5.2.4,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
17389,"VM starts, but UI stuck at creating process",Linux,other,VirtualBox 5.2.4,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
17398,Machine remains in aborted state with 3D enabled,Linux,Linux,VirtualBox 5.2.4,2017-12-24T10:07:30Z,2017-12-24T10:07:30Z,With guest additions 5.2.4 when I save the state of a VM it starts saving the state but remains in an aborted state. This only happens with 3D enabled. Log has been attached.,mcpudding
16623,Window position not saved correctly...,Mac OS X,all,VirtualBox 5.1.18,2017-12-24T10:37:01Z,2017-12-24T10:37:01Z,"VirtualBox Manager window will not save where placed by about a menu bar's height. Any place you put it on the desktop will place it approximately 20 pixels down from where you actually last left it upon relaunch of VirtualBox.

Others have tested that this bug currently exists in the 5.1.x series.

See community forum post entitled ""Window position not saved correctly..."".",starion
15081,VB 5.0.14 disables bluetooth on OSX 10.11.3 host,Mac OS X,all,VirtualBox 5.0.14,2017-12-24T18:17:39Z,2017-12-24T18:17:39Z,"VB 5.0.14 disables bluetooth on an iMac running OSX 10.11.3 thereby preventing the use of the wireless keyboard and trackpad. Hence the loss of control of both host and guest! [[BR]]
[[BR]]
The only(?) way out of this is to force a reboot of the system using power switch.[[BR]]
[[BR]]
This is not a problem with VB 5.0.10",esLivingston
17400,"Seamless mode fails on Solaris hosts, VB 5.2.4",Solaris,all,VirtualBox 5.2.4,2017-12-25T03:13:38Z,2017-12-25T03:13:38Z,"This started with 5.2.0 beta 1 and continues through VB 5.2.4.  Problem does not exist with 5.1.x.  All guest additions have been updated.

I've tested with Ubuntu Mate 16.10, Solaris 11.3, Windows 7, and Windows XP guests.  With all, the toolbar never appears, and the mini-toolbar of VirtualBox appears for a short time, but also vanishes without even the small row of pixels you can normally click on to have it appear.

Guest toolbar/start bar does not appear, but if you move the mouse over where it should be and click, you get some distortion of the host's desktop, but no guest menus appear.  Compiz is NOT running on host or guests.

I'm attaching log files for the Ubuntu, XP, and Solaris VMs.  Will have to wait for the Windows 7 VM until I get back to that computer in a week.",bq
17393,failed to open a session Machinewrap E_FAIL 0x80004005,Windows,other,VirtualBox 5.1.16,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
17399,Video driver fails for Win 10 guest version 1709 Preview build 17063.1000,Windows,Windows,VirtualBox 5.2.4,2017-12-26T00:27:40Z,2017-12-26T00:27:40Z,"Video driver fails for Win 10 guest version 1709 Preview build 17063.1000

Fails for VB 5.1.28 , 5.1.30 and 5.2.4 .

Repeat:
1. Turn on Windows insider program from Windows Settings/Windows Insider Program and chose ""What pace do you want to get new builds"" - ""fast""
2. Check for updates via Windows Settings/Windows Update
3. Reboot
4. See the way it fails and Win 10 guest substs VB driver by default Microsoft Basic Display driver

Thank you for development.",MikhailRokhin
17361,VM Crash on Android USB (debug+tether) unplug,Linux,Linux,VirtualBox 5.2.0,2017-12-26T09:35:51Z,2017-12-26T09:35:51Z,"Sometimes, when I unplug my Android device (LineageOS 7.1.2), the VM crashes.
VirtualBox 5.2.2 (it also crashed with VirtualBox 5.1.0).
Host and Guest are Ubuntu Server 17.10.
Host and Guest where rebooted only two days ago.
See crash dump attached.
When plugged, the Android device runs in USB Debug mode, with USB tethering enabled. The linux interface is set with ""allow-hotplug"".",flechaig
17402,Unexpected input upon minimize/maximize host window,Windows,Linux,VirtualBox 5.2.4,2017-12-26T20:13:40Z,2017-12-26T20:13:40Z,"After upgrading VirtualBox to VirtualBox-5.2.4 (VirtualBox-5.2.4-119785-Win.exe) I noticed the Linux guests started receiving weird escape sequences (`~`, `^[^[[29~`) or mouse clicks on the Linux guests.


Going back to the older version is not an option, as after reinstalling the host (Windows 10) the older versions (5.0.20, 5.0.40, and 5.1.30) all fail to start VMs with a `hardening error` (the problem persists even after following the instructions [https://forums.virtualbox.org/viewtopic.php?f=25&t=82106 on the support forum]).

Reproduction steps:

- host: Windows 10 Pro, 64 bits, all updates installed
- Salix guest:
  1. create a VM with [https://www.salixos.org/download.html the latest version (salix64-xfce-14.2.iso)]
     * Type: Linux
     * Version: Other Linux (64-bit)     
     * no swap
     * install from disk
     * auto select
     * Basic installation mode
     * select mirror: mirrors.xmission.com/salix
  2. on the VM, open a terminal and then:
     a. minimize and maximize the VBox window using the keyboard (Win key + D)
     b. alt-tab
     c. or switch Windows 10 workspaces (Win key + Tab)
     --> a right-mouse click is issued on the guest on the last mouse position
  3. installing guest additions does *not* change the problem
     {{{
     (as root)
     slapt-get --update
     slapt-get --install kernel-huge kernel-headers kernel-modules kernel-firmware 
     lilo -v
     slapt-get --install kernel-source
     reboot
     <insert the guest additions media, double click it on desktop to mount>
     sudo /run/media/<user name>/VBox_GAs_5.2.4/VBoxLinuxAdditions.run
     }}}
     
     
- Ubuntu guest:
  1. create a VM with [https://www.ubuntu.com/download/desktop the current LTS (ubuntu-16.04.3-desktop-amd64.iso)] with all the default options      
  2. install urxvt: sudo apt-get install rxvt-unicode-256color
  3. on the VM, open urxvt and then:
     a. minimize and maximize the VBox window using the keyboard (Win key + D)
     b. alt-tab
     c. or switch Windows 10 workspaces (Win key + Tab)
     --> `~` or `[29~` are inserted in urxvt
  4. installing guest additions does *not* change the problem
",mMontu
17342,PokerStars freezes up in Virtualbox 5.2+ but not in 5.1.30,Linux,Windows,VirtualBox 5.2.0,2017-12-27T06:01:41Z,2017-12-27T06:01:41Z,"Arch Linux 64-bit host, Windows 7 64-bit guest

To encounter the issue:

Use the following:
* virtualbox-5.2.2-2
* virtualbox-ext-oracle-5.2.2-1
* virtualbox-guest-iso-5.2.2-1
* virtualbox-host-dkms-5.2.2-2
Start the Windows 7 guest in Safe Mode, install the Guest Additions, select Direct3d support, agree to install only Basic Direct3d support, reboot the guest, then start PokerStars (the most recent build is 20294) and click the ""Challenges"" button in the menu. This resulted in the window freezing for several minutes (I had to force-kill it).

The program similarly hangs when sitting down at a table, which is the more serious part; the Challenges window just provides a more convenient way to test the issue.

Using all 5.2.0 VirtualBox components instead of 5.2.2 made no difference (PokerStars froze just the same).

It does not seem specific to the PokerStars build, as trying it with an earlier build of PokerStars made no difference.

For comparison, using VirtualBox 5.1.30 instead of 5.2+ and following the same steps as described above did NOT produce the issue (PokerStars works fine without hanging using the following):
* virtualbox 5.1.30-1
* virtualbox-ext-oracle 5.1.30-1
* virtualbox-guest-iso 5.1.30-1
* virtualbox-host-dkms 5.1.30-1",sleepnought
17403,Touchscreen input is not scaled to VM location on screen,Windows,Linux,VirtualBox 5.2.4,2017-12-27T06:40:05Z,2017-12-27T06:40:05Z,"host: Win 10 on HP Envy 14-k111nr with touchscreen (3200x1800), virtualization enabled.
guest: Android 7.1-rc1 64bit, set as Linux (Version 2.6/3.x/4.x 64 bit)


Problem: When I dont disable mouse-integration i can only control the cursor with touch interactions. Also cursor only moveable by mouse when clicked - otherwise it just wouldnt move. 
When I disable it I can ""use"" the touchscreen ""nativly"". But thats the problem because it seems that it just reads out the coordinates of the touch input rather than the position in the VM-machine. It doesnt bother where the VM-""display"" is located on the desktop. If i push at 3000;1000 the VM will detect the click on 3000;1000 even though it only covers the area until 2000;500.

The solution would be to detect the VM window if not 100% fullscreen and translate the touch input postition to the guest screen. ",FUKU
17412,Installing Guest Additions 5.2.4 on CentOS 7 fails,Windows,Linux,VirtualBox 5.2.4,2018-01-02T17:12:13Z,2018-01-02T17:12:13Z,"Host: Windows 7, 64-bit, VirtualBox 5.2.4
Guest: CentOS 7 with all upgrades, initially set up for VirtualBox 5.1.22

Bug: 
When I upgraded VirtualBox and ran the Guest Additions installer in my CentOS guest to upgrade Guest Additions, the video driver build failed.  It seems to have failed on an unimportant driver, because it actually works correctly.  Still, it's worth reporting the build failure.  The attached is an excerpt from the log file.

Building the graphics driver module
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/3.10.0-327.18.2.el7.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j2 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (	\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/.hgsmi_base.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include -Iarch/x86/include/generated  -Iinclude -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/uapi -Iinclude/generated/uapi -include /usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -Wframe-larger-than=2048 -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/3.10.0-327.18.2.el7.x86_64/build/include -I/tmp/vbox.0 -Iinclude/drm -D__KERNEL__ -DMODULE  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(hgsmi_base)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxvideo)"" -c -o /tmp/vbox.0/.tmp_hgsmi_base.o /tmp/vbox.0/hgsmi_base.c
  gcc -Wp,-MD,/tmp/vbox.0/.modesetting.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include -Iarch/x86/include/generated  -Iinclude -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/uapi -Iinclude/generated/uapi -include /usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -Wframe-larger-than=2048 -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/3.10.0-327.18.2.el7.x86_64/build/include -I/tmp/vbox.0 -Iinclude/drm -D__KERNEL__ -DMODULE  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(modesetting)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxvideo)"" -c -o /tmp/vbox.0/.tmp_modesetting.o /tmp/vbox.0/modesetting.c
In file included from /tmp/vbox.0/vboxvideo_guest.h:32:0,
                 from /tmp/vbox.0/modesetting.c:27:
/tmp/vbox.0/vbox_drv.h:256:24: error: field ‘gem’ has incomplete type
  struct drm_gem_object gem;
                        ^
In file included from /tmp/vbox.0/hgsmi_base.c:27:0:
/tmp/vbox.0/vbox_drv.h:256:24: error: field ‘gem’ has incomplete type
  struct drm_gem_object gem;
                        ^
make[2]: *** [/tmp/vbox.0/hgsmi_base.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/tmp/vbox.0/modesetting.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxvideo] Error 2
",gbartlett
17404,Windows 10 guest aborts on 5.2.4,Linux,Windows,VirtualBox 5.2.4,2018-01-02T19:55:46Z,2018-01-02T19:55:46Z,After updating to 5.2.4 on CentOS7 my Windows 10 guest aborts frequently. This occurred every now and then on prior Virtualbox builds but is much more frequent on this version. I would be happy to provide any additional requested information on how to resolve but I am not sure what files you would like. I do use shared folders and recall in the past that was sometimes an issue.,jim.rather
17413,simplify the automatically offered extension pack upgrade procedure,Windows,other,VirtualBox 5.2.4,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
17414,Virtualbox 5.2.4 crashed,Linux,Windows,VirtualBox 5.2.4,2018-01-03T14:28:41Z,2018-01-03T14:28:41Z,"On Fedora 27 with:

VirtualBox-5.2-5.2.4_119785_fedora26-1.x86_64

a crash has occurred. The logs and gdb info of the core are attached.",Panos Kavalagios
17415,VirtualBox - Error In supR3HardenedWinReSpawn when the starting the VM,Windows,Windows,VirtualBox 5.0.40,2018-01-03T18:38:49Z,2018-01-03T18:38:49Z,"I am using VirtualBox 5.0.40 and I have created a VM which has Windows XPMode configured.
When I am starting the VM, I am getting the below exception pop up with the error message:

VirtualBox - Error In supR3HardenedWinReSpawn

(rc=-5640)

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn 
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE
(-5640) - Process Verification Failure: 
The process has more than one thread.

When I click the OK, it brings another exception pop up with the below error message:

VirtualBox - Error

Failed to open a session for the virtual machine 'My Guest Machine'

Details
The virtual machine 'My Guest Machine' has terminated unexpectedly during startup with exit code 1(0x1).
More details may be available in 'C:\Users\myuser\VirtualBox VMs\My Guest Machine\Logs\VBoxHardening.log'. 

I clicked OK to close the window.

But when I start the VM again, it launches successfully with out any error.
But at times when I start again after the above mentioned error, it is not launching and give the same error.
This behavior is inconsistent.

Could you please suggest me any possible fix to avoid this error?",PbuHCL
16878,VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error on Windows 10,Windows,Linux,VirtualBox 5.1.22,2018-01-04T11:44:53Z,2018-01-04T11:44:53Z,"Hello

I keep getting the above mentioned error when I start a guest. I remove and reinstall VirtualBox and the error goes away, but after a few days it comes back again (usually after a restart of my PC). I am attaching the screen shot of error box and VBoxHardening log. A shorter error message is below:


{{{
Failed to open a session for the virtual machine Ubuntu-16.04.

The virtual machine 'Ubuntu-16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\arshad.khan\VirtualBox VMs\Ubuntu-16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}


Any help is greatly appreciated.

Thanks
Arshad",arshad01
17418,Incorrect color map for Solaris 11.3 host when upgrading from 5.1.22 to 5.1.24 and beyond,Solaris,Windows,VirtualBox 5.1.24,2018-01-04T20:41:34Z,2018-01-04T20:41:34Z,"I'm using a Solaris 11.3 x64 SunRay server and after upgrading from 5.1.22 to 5.1.24 or newer, including 5.2.4, the color map appears to be inverted.

This affects both the GUI and the clients.

Downgrading to 5.1.22 restores the correct behavior.",Tipo
17421,Clipboard sharing stops working after large copying on guest,Linux,Windows,VirtualBox 5.2.4,2018-01-05T07:59:44Z,2018-01-05T07:59:44Z,"When copying an image which is large (tested larger 2MB), the clipboard sharing stops working completely.",amosb
17417,VirtualBox crashes,Windows,Windows,VirtualBox 5.2.4,2018-01-05T08:37:09Z,2018-01-05T08:37:09Z,"When I craete a new SATA-HD, then the Client crashes if I create with right mouse button on SATA.

There runs a windows 2012 r2 server.

",rhino
17419,Regression: VirtualBox 5.1.30 can not be compiled without kernel build/source directory,Linux,Linux,VirtualBox 5.1.30,2018-01-05T17:51:46Z,2018-01-05T17:51:46Z,"In VirtualBox Release 5.1.6 it was possible to compile VBox from Sources without access to the kernel build- and source directory when using --disable-kmods.

When compiling VirtualBox 5.1.30 this gives errors. Not in all environments is the kernel source accessible when compiling a user mode program (or the kernel module build is separated).",core-it-admin
17422,Switching away from guest alters NumLock state of host,Windows,Linux,VirtualBox 5.2.4,2018-01-05T18:55:21Z,2018-01-05T18:55:21Z,"Host: Windows 7 Enterprise, initial NumLock state at ""On""
Guest: KDE Neon, initial NumLock state at ""On""

Steps:
Ensure NumLock is on for the host.
Start the guest.
Observe that the host's NumLock remains on.
Enter the guest (e.g. click within the window).
Ensure NumLock remains on.
Return to the host (click the task bar or something that causes VBox to lose focus).

Expected outcome:
Host's NumLock remains on.

Actual outcome:
Host's NumLock turns off.

VBox version first observed: 5.1
Is 5.2.4 affected: Yes

After running a search, I wonder if these bugs are related in some way:
https://www.virtualbox.org/ticket/14614
https://www.virtualbox.org/ticket/14302

I am happy to provide any logs that might be needed.",Twisted Lucidity
17426,Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR),Linux,Linux,VirtualBox 5.0.40,2018-01-08T12:07:57Z,2018-01-08T12:07:57Z,Running virtualbox on ubuntu 16.04 host with arch linux as guest after first crash with same error i completelly reinstalled arch so now this error appear on fresh installed system.,Den
17432,After upgrade 5.1.30 it never worked again,Windows,Windows,VirtualBox 5.1.30,2018-01-08T19:03:22Z,2018-01-08T19:03:22Z,"Long time using VirtualBox and after install upgrade 5.1.30 it left working again. I upgrade to 5.2 version and the same result with a different problem. Each time updated Extension Pack, but nothing.",FGGarcia
17424,Old Linux on Virtual Box 5.2.4 gets Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),other,Linux,VirtualBox 5.2.4,2018-01-08T21:38:36Z,2018-01-08T21:38:36Z,"Migrating a running (older) Linux guest from Mac OS hosted VirtualBox 5.2.3 to FreeBSD hosted
VirtualBox 5.2.4.

Exported all the machines as an appliance from 5.2.3 and imported them to the 5.2.4.

All virtual machines operate correctly except a rather ancient Linux that fails to boot
with a VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

I will attach the log files.",Dave Rivers
17439,Using Intel Realsense SR300 camera causes VM Abort,Linux,Linux,VirtualBox 5.2.4,2018-01-09T15:50:27Z,2018-01-09T15:50:27Z,"1- guest
1.1 - Linux vagrant 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1.2 - 
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial

2- install librealsense in vm:

{{{
# if the realsense ubuntu repository was not added add it to ubuntu source list.
if [ ! -f /etc/apt/sources.list.d/realsense-public.list ]; then
    echo 'deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial main' | tee /etc/apt/sources.list.d/realsense-public.list
    apt-key adv --keyserver keys.gnupg.net --recv-key 7DCC6F0F
fi

# make sure you have kernel headers installed, otherwise realsense dkms will not patch the kernel.
apt-get -y install linux-headers-`uname -r`

apt-get -y update
apt-get -y upgrade

apt-get install -y realsense-uvcvideo # kernel patch to support the camera
apt-get install -y librealsense2-utils # demos for the camera 
}}}

3- Plug the camera, and connect to the guest
3.1 - execute the command

{{{
rs-pointcloud
}}}

4- After some seconds the camera vm aborts.

Note: Same setup was tested with VMWare Palyer 14, and vm does not crashes, and the rs-pointcloud application works despite some delays.",mjscosta
17430,Invisible mouse pointer with remote control. (Linux host),Linux,all,VirtualBox 5.2.4,2018-01-09T19:55:37Z,2018-01-09T19:55:37Z,"When I try to remote control a virtual machine with TeamViewer or vnc the Mouse pointer of the ""supporter"" is not shown in the virtual machine.[[BR]]
The ""local"" mouse pointer of the virtual machine remains where it was left. The remote Pointer is invisible.[[BR]]

TeamViewer as well as vnc do work without restrictions, only the remote mouse is invisible in the virtual machine.[[BR]]

The local mouse pointer reflects the state of the remote pointer (hand, arrow, busy, ...) but does not move from the position where it was left by the local user.

I tried Debian stretch (KDE) and Linux Mint (Cinnamon) as host and Windows and Debian as guest.[[BR]]

In the Windows guest I tried no 3d-acceleration, Direct3D and WDDM with no avail.[[BR]]

The host is equipped with a Intel i3-6100 CPU and uses the builtin Intel graphics.
",Gurkensalat
17440,VBoxHardening- Exit Code 0x1,Windows,Windows,VirtualBox 5.2.4,2018-01-09T22:41:16Z,2018-01-09T22:41:16Z,"I have a few different VMs on my current laptop which I am trying to move to my new laptop. However, after importing the machines, I am getting an error message when I try to open the VMs:

[[Image(ticket:1:ErrorMessage.gif)]]

and

[[Image(ticket:1:ErrorMessage2.gif)]]

My previous laptop is running Win7x64 and I am using VirtualBox 5.1.30 r11838. This has been upgraded as releases have come out so I am not sure what version of VirtualBox I was using when I created the VMs. Each machine is running a similar copy of Windows Server 2008 R2.

I have attached the VBoxHardening.log file for one of the VMs- they are all causing the same error.

I was able to open a few of the VMs once, but then after either powering off  (no saved state) or saving, I get the error message again on restart. I  have tried headless, normal, and detached starts. 

I know this issue has been raised on past versions of VirtualBox, but I didn't see a method for fixing the error which worked- I have un-installed and re-installed VirtualBox, I have tried to recreate the VMs using the same hard disk image, I have turned off my virus software, I have confirmed that I do not have the layout registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers), and I have done a software scan (sfc /scannow). I would appreciate any assistance in trying to solve this issue.",mdr
17444,After start virtualbox my bluetooth dongle doesn't  work.,other,Windows,VirtualBox 5.1.30,2018-01-10T10:19:12Z,2018-01-10T10:19:12Z,"In my worktime I want to use an usb bluetooth adapter (Asus USB-BT400) for my bluetooth headset but it's doesn't work. Previously, I thought the problem was with the driver or my motherboard, but later I realized the problem occurs when I launch the virtualbox.
I just need to start the basic program without launching any guest.

The device status is as follows: This device cannot start. (Code 10)
If I close the virtualbox and I replug the adapter, The error will be terminated.

I tried different drivers, usb hubs, and computers but nothing changed.
The host type all of my computer I tried: Windows 10 Enterprise N 64bit",JosephK
17114,Win10 guest hangs when USB attached,Linux,Windows,VirtualBox 5.1.28,2018-01-10T19:56:07Z,2018-01-10T19:56:07Z,"When I attach a USB device to the Win10 guest, it ''sometimes'' causes total freeze of the system. That ''sometimes'' means like 1/10 to 1/50. I can only do hard power off, the system does not react on anything (I tried sending Ctrl+Alt+Del, sending the shutdown signal). The screen remains frozen (no BSOD or such). The integrated cursor moves normally and shows the Windows cursor, though.

I mostly experience the problem with USB device SEGGER J-Link Ultra [0100] (1366:0101), as I do need to attach it detach it quite frequently. I have it in the autoconnect filter. There was no problem with this device on my previous machine (Debian 8 64bit host, Win7 Pro 32bit guest, VirtualBox 4.3). Anyway, I don't think it's a problem of this particular device. Once or twice I experienced this behaviour without having the device attached to the computer.

I'm experiencing the problem since I upgraded my PC (new HW, new host system, new virtual system). I already updated all (host, vbox, guest) a couple of times, with no change.

Host: Debian 9 Stretch, 64bit, 16 GB RAM[[BR]]
Guest: Windows10 Pro, 64bit, 4 GB RAM[[BR]]
VBox: 5.1.28 r117968 linux.amd64 (Sep 13 2017 15:04:33), Guest Additions installed
",ymanCZ
17448,Python bindings for Python 3.x fail on sys.abiflag() because of module and init name mismatch,all,all,VirtualBox 5.2.4,2018-01-10T21:14:13Z,2018-01-10T21:14:13Z,"Reporting an issue where if `sys.abiflags() != ''` you will not be able to import vboxapi on Python 3.x systems because of how the PyInit function is named.

Python requires .so modules to have an exported function with the name `PyInit_[MODULE NAME]` and in this case when the user installed via the .deb
file for Ubuntu 16.04 the .so file was named `VBoxPython3_5m.so` but when examining the exported function names we received only `PyInit_VBoxPython3_5` (note that there is no `m` at the end).

This mismatch makes it tough for users to install vboxapi without having to take additional steps such as renaming their .so file to not include the `m`.

Source file where this PyInit function is generated: https://www.virtualbox.org/svn/vbox/trunk/src/libs/xpcom18a4/python/src/module/_xpcom.cpp

See https://github.com/mjdorma/pyvbox/issues/102 for the original issue reported by another user.",SethMichaelLarson
17350,use of serial port crashes VM w/ non-mainstream OS,Mac OS X,other,VirtualBox 5.1.30,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
17436,[FIXED IN SVN] VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation,Windows,Linux,VirtualBox 5.2.4,2018-01-10T23:04:19Z,2018-01-10T23:04:19Z,"I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows:

A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows)

I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out:

00:00:17.401353 !!   VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)

I am attaching a .ZIP file of the VBox.log.



",GregB3
17433,VMMR0.r0 Bluescreen on HP Laptop Win10 v1709,Windows,other,VirtualBox 5.2.4,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
17442,Mac OS High Sierra VM crash,Mac OS X,other,VirtualBox 5.2.4,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
6979,Hard disk boot order,other,other,VirtualBox 3.2.4,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
17454,Critical error,Mac OS X,Linux,VirtualBox 5.1.30,2018-01-15T19:04:02Z,2018-01-15T19:04:02Z,"On startup of Ubuntu 16.04 virtual machine:

""A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""

",dwhea
12600,Allow dns proxy in the new NAT Network mode,all,all,VirtualBox 4.3.6,2018-01-16T13:37:54Z,2018-01-16T13:37:54Z,"I would like to be able to activate DNS proxy in the new NAT Network mode as it is possible in NAT mode (with the command VBoxManage modifyvm ""VM name"" --natdnsproxy1 on).

As it is, if I set my VM with the new NAT Network mode and run the command (VBoxManage modifyvm ""VM name"" --natdnsproxy1 on), this change nothing and continue to give the host DNS server to the guess.

Allowing this setting would be awesome as it would completely shield the VM from host change while allowing VM to talk to each other.",djf_jeff
17446,Multiple pointing device reported when choosing USB Multi-Touch Tablet,Windows,other,VirtualBox 5.2.2,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
17462,VM Lockup with evernote screenshot,Windows,Windows,VirtualBox 5.2.4,2018-01-16T20:01:22Z,2018-01-16T20:01:22Z,"Version 5.2.4 r119785 (Qt5.6.2)
Windows 7 VM 32 bit. 
Windows 10 Host. 

I have evernote 6.7.5.5825 on my host machine. 

I can use the VM all day long with no issues whatsoever. 
As soon as i use evernote to take a screenshot of either the VM or the host, any pert of either, it locks up the VM to the point that it is nearly un-responsive. Only a left click works, and it only marginally works at that.

Evernote is the only application that i have seen cause this, and it is only when a screenshot is taken. ",link81
17466,Win GAs installation dialog; clarify Direct3D vs WDDM installation option.,all,Windows,VirtualBox 5.2.4,2018-01-17T04:51:32Z,2018-01-17T04:51:32Z,"When installing the GAs in a Win7 guest, the following question is asked at the graphics interface choice phase:
> ''This system supports the Windows Aero (WDDM) interface.'' [[br]]
> ''!VirtualBox support for this feature is experimental and should not be used on production systems yet.''
> 
> ''Would you like to install basic Direct3D support instead?''
The answer is a ""Yes""/""No"" one. I believe that it could be clearer if the answer was ""Install Direct3D""/""Install WDDM"".

I tried to find the dialog answers in ""[https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/WINNT/Installer/Languages/English.nsh /vbox/src/VBox/Additions/WINNT/Installer/Languages/English.nsh]"" but there seems to be no provision to change the text in the ""Yes""/""No"" buttons.

I know that the change has to happen in ""[https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/WINNT/Installer/VBoxGuestAdditions.nsi /vbox/trunk/src/VBox/Additions/WINNT/Installer/VBoxGuestAdditions.nsi]"" as well, I just don't know how to implement custom buttons in the NSI installer.",Socratis
17458,"type/mtype can't be set to ""shareable""",Windows,Windows,VirtualBox 5.2.4,2018-01-17T07:13:22Z,2018-01-17T07:13:22Z,"The virtual drive is erroneously recognized as dynamic. See cmd-responses:

C:\Program Files\VirtualBox>VBoxManage storageattach Win10 --storagectl SATA --port 2 --medium E:\DataW10.vdi --mtype shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 708 of file VBoxManageStorageController.cpp
VBoxManage.exe: error: Failed to set the medium type

C:\Program Files\VirtualBox>VBoxManage modifymedium  disk e:\dataw10.vdi --type shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 705 of file VBoxManageDisk.cpp

C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi
UUID:           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Parent UUID:    base
State:          created
Type:           writethrough
Location:       E:\DataW10.vdi
Storage format: VDI
Format variant: fixed default
Capacity:       4096 MBytes
Size on disk:   4098 MBytes
Encryption:     disabled
In use by VMs:  Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)
",Loafer
17445,VirtualBox 5.2.4-119785 does not work on High Sierra 10.13.2,Mac OS X,Linux,VirtualBox 5.2.4,2018-01-17T07:20:22Z,2018-01-17T07:20:22Z,Self titled.  Pre-existing VMs are Kali and Ubuntu 16.04.  Attaching crash log.,hamy
17459,Keyboard/mouse not working after connecting to Dell Docking Station,Windows,Linux,VirtualBox 5.2.4,2018-01-17T07:23:43Z,2018-01-17T07:23:43Z,"I have a Dell docking station and the USB keyboard and mouse are plugged into the docking station. If VirtualBox is already running and I connect the laptop to the docking station, the keyboard and mouse do not work. If I first connect the laptop to the docking station and then start VirtualBox, then keyboard and mouse work fine. So I have to close down all VirtualBox windows everytime I disconnect and reconnect back to the dock.",vix
17401,Snapshot saved state discarding,Windows,all,VirtualBox 5.2.2,2018-01-17T07:33:42Z,2018-01-17T07:33:42Z,Can't find an option to discard a snapshot saved state. I.e. discard its running instance saved memory leaving the drive snapshot. If you made a snapshot of a running machine then its memory is saved forever too. This ram state is probably responsible for the most of its snapshot size.,GnomeUser
17464,Left clicking not responding in a short time after typing,Mac OS X,Windows,VirtualBox 5.2.4,2018-01-17T07:58:39Z,2018-01-17T07:58:39Z,"When I finished typing something, the mouse (left click) is not responding in a short time.  I need to click twice or more, or wait for a short time and then click again.


Guest Operating System: Windows 10

Host Operating System:  macOS",jaywang
17206,VBoxLinuxAdditions.run fails in Ubuntu Server 16.04.3 -> module signing problem,Windows,Linux,VirtualBox 5.2.0,2018-01-17T11:42:56Z,2018-01-17T11:42:56Z,"VBoxLinuxAdditions.run fails in Ubuntu Server 16.04.3:

{{{
administrator@ubuntu:~$ sudo /media/cdrom/VBoxLinuxAdditions.run
.
.
.
  ld -r -m elf_x86_64 -T ./scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxvideo.ko /tmp/vbox.0/vboxvideo.o /tmp/vbox.0/vboxvideo.mod.o
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.4.0-97-generic/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 ""  ERROR: Kernel configuration is invalid."";           \
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /lib/modules/4.4.0-97-generic/misc
make -f ./scripts/Makefile.modinst
  mkdir -p /lib/modules/4.4.0-97-generic/misc ; cp /tmp/vbox.0/vboxvideo.ko /lib/modules/4.4.0-97-generic/misc ; true /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko ; if (echo ""/lib/modules/4.4.0-97-generic/misc/vboxvideo.ko"" | egrep -q ""\/drivers\/staging\/"") && (! egrep -x ""vboxvideo.ko"" ./drivers/staging/signature-inclusion) ; then echo Not signing ""/lib/modules/4.4.0-97-generic/misc/vboxvideo.ko""; else scripts/sign-file ""sha512"" ""certs/signing_key.pem"" certs/signing_key.x509 /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko || true && true /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko; fi
At main.c:222:
- SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  /bin/bash ./scripts/depmod.sh /sbin/depmod 4.4.0-97-generic """"
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Could not find the X.Org or XFree86 Window System, skipping.
}}}

Fails for following:

VBoxGuestAdditions_5.2.1-118447.iso
[[BR]]
VBoxGuestAdditions_5.2.1-118468.iso
[[BR]]

{{{
administrator@ubuntu:~$ uname -a
Linux ubuntu 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

}}}
",Red Viking
17268,Guest Addition graphics driver build fails on Debian 9.2 -> fixed,Windows,Linux,VirtualBox 5.2.0,2018-01-17T15:12:04Z,2018-01-17T15:12:04Z,"Running Debian 9.2, Kernel 4.9.0-4-amd64 as client on a Win10 guest the build of the grahics guest addition driver fails.

vboxadd-setup.log attached.

Maybe related to #17210",Gevatter Gaul
17300,crash of all virtual machines,Windows,Windows,VirtualBox 5.2.0,2018-01-18T14:35:20Z,2018-01-18T14:35:20Z,"Running several VM's.  When all VM's crash with same error simultaneously.  Log of one vm's crash is attached.  This has happened twice over the last week or two. 

Cannot say what steps are needed to reproduce as it seems random when this occurs.",ArtZ
17070,vboxvideo does not work with Xorg 1.19,all,Linux,VirtualBox 5.1.26,2018-01-18T17:18:48Z,2018-01-18T17:18:48Z,"'''Problem''':

''Guest Additions'' works up to ''Xorg 1.18''. Under latest ''1.19'' (which was released nearly year ago), 3d acceleration does not work and there is error in ''Xorg.0.log'':
{{{
   (II) LoadModule: ""vboxvideo""
   (WW) Warning, couldn't open module vboxvideo
   (II) UnloadModule: ""vboxvideo""
   (II) Unloading vboxvideo
   (EE) Failed to load module ""vboxvideo"" (module does not exist, 0)
}}}

'''Simple reproduction''':

install Arch Linux with desktop environment inside VirtualBox, then install Guest Additons.

----

I downgraded Xorg to 1.18 and everything was running smoothly and there were not any errors in xorg log. Why can't you just provide Guest Additions with videobox_drv_119.so? 
",andrzej1_1
17478,ExtensionPack Installation Error,Windows,all,VirtualBox 5.2.6,2018-01-18T18:06:15Z,2018-01-18T18:06:15Z,"Не удалось установить плагин C:/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.2.6-120293.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-1048' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')

rcExit=1.

Код ошибки: E_FAIL (0x80004005)
Компонент: ExtPackManagerWrap
Интерфейс: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",zats
17467,Ubuntu host does not start after 5.2.6 GUest Additions installed,Linux,Linux,VirtualBox 5.2.6,2018-01-18T21:46:15Z,2018-01-18T21:46:15Z,"I upgraded VirtualBox to 5.2.6 on my Ubuntu 16.04 host and also installed Guest Additons 5.2.6 on Ubuntu 16.04 guest. Then I powered off guest. Now, when starting guest it just does not start. I can see Ubuntu starts running but then it gets stuck somewhere...",SamH
17429,VM  Manager crash crash when creating new VM Machine,other,other,VirtualBox 5.2.4,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
14985,Enable 3D acceleration cause black screen or flickering -> obsolete,Linux,Linux,VirtualBox 5.0.12,2018-01-19T12:51:38Z,2018-01-19T12:51:38Z,"Ubuntu 14.04.3 X64 + mate 1.82 for both host and guest
Enable 3D acceleration for guest VM
enable hardware acceleration for Chrome in both guest and host
for Chrome, flicking in VM, but works fine in host 

the screen of VM will go black randomly, only can I sent ctrl-alt-backspace to restart X. However, after update both kernel to 4.2 (sudo apt-get install linux-generic-lts-wily). no more black screen in VM. But Chrome still flickering screen when launch if  hardware acceleration is enable in its setings. A 4 seconds screen cast is on https://youtu.be/paVfpClhyj8",maxchen
17481,VM crashes when allocating memory at MSR_LSTAR address range,Windows,Linux,VirtualBox 5.2.6,2018-01-19T22:32:20Z,2018-01-19T22:32:20Z,"Hi,

I'm developing a Linux LKM, and I tried to reserve memory in the same range of MSR_LSTAR (SYSCALL handler), with __vmalloc_node_range().

On the 3rd execution of that function, returning first NULL, second an address and third time NULL, the Guru Mediation spawns.

I'm attaching the source code to reproduce the bug, the log and the screenshot.

Thanks for help.",D1W0U
15019,Unable to create Host-Only Network in Windows 10,Windows,all,VirtualBox 5.0.12,2018-01-19T22:32:40Z,2018-01-19T22:32:40Z,"I was unable to create host-only network in Windows 10 Home Single Language using {{{VBoxManage hostonlyif create}}} with following output:

{{{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}
",rkurniawan
17468,Audio is not working in the Virtual Box 5.2.6,Mac OS X,Windows,VirtualBox 5.2.6,2018-01-19T22:46:15Z,2018-01-19T22:46:15Z,"After the update to the new version 5.2.6 now the audio in my Virtual Box which is running windows is not working. I had this issue some versions ago and just deactivate the audio and then activate again and works, but now is just not working and for me is vital to have audio, since I have audio alerts running.

Any comments or help on this matter.

Thanks",MYOS
17406,Failed to create a host network interface (windows10),other,other,VirtualBox 5.2.4,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
17496,critical error guru meditation,Windows,Windows,VirtualBox 5.2.6,2018-01-23T09:35:36Z,2018-01-23T09:35:36Z,"sir,
   there is an issue in my virtual box in which my xp virtual window going to
 guru meditation & not work my virtual box window.
",lalla
17473,GRUB countdown problem,Linux,Linux,VirtualBox 5.1.26,2018-01-23T10:14:51Z,2018-01-23T10:14:51Z,"The file /etc/default/grub   contains GRUB_TIMEOUT=5 by default . After starting my Guest OS , it will show a sentence ""The highlighted entry will be executed automatically in 5s"" .
VirtualBox has such a problem that makes GRUB (That's Guest OS ,but not host OS) unable to show this sentence when it's countdowning at 5s . After countdowning at 5s , GRUB shows 4s 3s 2s and 1s very normally . This problem doesn't always appear ,but only sometimes appears ",vbgaofei
17488,virtualbox freezing the my system linux mint 18.3,Linux,Linux,VirtualBox 5.1.20,2018-01-23T10:38:07Z,2018-01-23T10:38:07Z,"i try many time to solve this issue but no way to solve it because that i need your help kindly , i was trying to install Linux Kali in my system guest (Linux mint 18.3) and after i finish form all the setting a start the vm image suddenly the system is freezing 
and the only way to re-start all things is by re-start my guest system 
and i can't provide you with the screen-shoot because the system is freezing 
kindly your support 
my regards 
",astrokinght
17495,Échec de l'installation de l'extension,Windows,other,VirtualBox 5.2.4,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
17172,VirtualBox crashes on adding new disk to VM,other,other,VirtualBox 5.1.30,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
6023,VHD Delete Snapshot results in corrupt virtual hard disk or double snapshot revert,other,other,VirtualBox 3.1.2,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
16933,"guru meditation at ""Starting Windows"" in Windows 7 guest",Linux,Windows,VirtualBox 5.1.24,2018-01-25T21:07:18Z,2018-01-25T21:07:18Z,Windows 7 guest failed to start.,jlong
17499,"Can't start vmachine, MachineWrap E_FAIL (0x80004005)",Windows,Windows,VirtualBox 5.1.22,2018-01-26T10:28:13Z,2018-01-26T10:28:13Z,"Hello there.

I don't know why, but i can't even start v-box machine. It gives me this error:


{{{
The virtual machine 'TESTING' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Admin\VirtualBox VMs\TESTING\Logs\VBoxHardening.log'.

Návratový kód: E_FAIL (0x80004005)
Komponenta: MachineWrap
Rozhraní: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

Log output:

{{{
41c.1af0: Log file opened: 5.1.22r115126 g_hStartupLog=000000000000006c g_uNtVerCombined=0xa03fab00
41c.1af0: \SystemRoot\System32\ntdll.dll:
41c.1af0:     CreationTime:    2018-01-05T15:56:46.395451500Z
41c.1af0:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
41c.1af0:     ChangeTime:      2018-01-06T08:02:19.865353700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1dd100
41c.1af0:     NT Headers:      0xe0
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1e0000 (1966080)
41c.1af0:     Resource Dir:    0x174000 LB 0x6a1d8
41c.1af0:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.192
41c.1af0:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
41c.1af0:     FileDescription: NT Layer DLL
41c.1af0: \SystemRoot\System32\kernel32.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:04.954227600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.735385400Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0xab868
41c.1af0:     NT Headers:      0xe8
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0xae000 (712704)
41c.1af0:     Resource Dir:    0xac000 LB 0x520
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\KernelBase.dll:
41c.1af0:     CreationTime:    2017-09-29T13:41:43.124345500Z
41c.1af0:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.829134900Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x266000
41c.1af0:     NT Headers:      0xf0
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x266000 (2514944)
41c.1af0:     Resource Dir:    0x245000 LB 0x548
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\apisetschema.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:07.095026600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
41c.1af0:     ChangeTime:      2018-01-08T20:50:10.598880700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1b398
41c.1af0:     NT Headers:      0xc8
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1c000 (114688)
41c.1af0:     Resource Dir:    0x1b000 LB 0x408
41c.1af0:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: ApiSet Schema DLL
41c.1af0: supR3HardenedWinFindAdversaries: 0x0
41c.1af0: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: Calling main()
41c.1af0: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
41c.1af0: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: SUPR3HardenedMain: Respawn #1
41c.1af0: System32:  \Device\HarddiskVolume1\Windows\System32
41c.1af0: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
41c.1af0: KnownDllPath: C:\WINDOWS\System32
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
41c.1af0: supR3HardNtEnableThreadCreation:
41c.1af0: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardenedWinDoReSpawn(1): New child 2d54.35dc [kernel32].
41c.1af0: supR3HardNtChildGatherData: PebBaseAddress=000000000116e000 cbPeb=0x388
41c.1af0: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
41c.1af0: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
41c.1af0: supR3HardenedWinSetupChildInit: Start child.
41c.1af0: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
41c.1af0: supR3HardNtChildPurify: Startup delay kludge #1/0: 263 ms, 16 sleeps
41c.1af0: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
41c.1af0:  *0000000000000000-0000000000e5ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000e60000-0000000000e7ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000e80000-0000000000e98fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000e99000-0000000000e9ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000ea0000-0000000000f9afff 0x0000/0x0004 0x0020000
41c.1af0:   0000000000f9b000-0000000000f9dfff 0x0104/0x0004 0x0020000
41c.1af0:   0000000000f9e000-0000000000f9ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000fa0000-0000000000fa3fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000fa4000-0000000000faffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000fb0000-0000000000fb0fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000000fb1000-0000000000ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000001000000-000000000116dfff 0x0000/0x0004 0x0020000
41c.1af0:   000000000116e000-0000000001170fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000001171000-00000000011fffff 0x0000/0x0004 0x0020000
41c.1af0:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
41c.1af0:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
41c.1af0:   000000007fff0000-00007ff7ed97ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7ed980000-00007ff7ed9a2fff 0x0002/0x0002 0x0040000
41c.1af0:   00007ff7ed9a3000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
41c.1af0: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
41c.1af0: supR3HardNtChildPurify: Done after 417 ms and 0 fixes (loop #0).
2d54.35dc: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2d54.35dc: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
41c.1af0: supR3HardNtEnableThreadCreation:
2d54.35dc: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2d54.35dc: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: System32:  \Device\HarddiskVolume1\Windows\System32
2d54.35dc: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2d54.35dc: KnownDllPath: C:\WINDOWS\System32
2d54.35dc: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2d54.35dc: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2d54.35dc: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2d54.35dc: Registered Dll notification callback with NTDLL.
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2d54.35dc: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2d54.35dc: \SystemRoot\System32\ntdll.dll:
2d54.35dc:     CreationTime:    2018-01-05T15:56:46.395451500Z
2d54.35dc:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2d54.35dc:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1dd100
2d54.35dc:     NT Headers:      0xe0
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1e0000 (1966080)
2d54.35dc:     Resource Dir:    0x174000 LB 0x6a1d8
2d54.35dc:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.192
2d54.35dc:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: NT Layer DLL
2d54.35dc: \SystemRoot\System32\kernel32.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:04.954227600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0xab868
2d54.35dc:     NT Headers:      0xe8
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0xae000 (712704)
2d54.35dc:     Resource Dir:    0xac000 LB 0x520
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\KernelBase.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:41:43.124345500Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x266000
2d54.35dc:     NT Headers:      0xf0
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x266000 (2514944)
2d54.35dc:     Resource Dir:    0x245000 LB 0x548
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\apisetschema.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:07.095026600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2d54.35dc:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1b398
2d54.35dc:     NT Headers:      0xc8
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1c000 (114688)
2d54.35dc:     Resource Dir:    0x1b000 LB 0x408
2d54.35dc:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: ApiSet Schema DLL
2d54.35dc: supR3HardenedWinFindAdversaries: 0x0
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: Calling main()
2d54.35dc: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2d54.35dc: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: SUPR3HardenedMain: Respawn #2
2d54.35dc: supR3HardNtEnableThreadCreation:
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ntdll.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff956000000 'C:\WINDOWS\System32\ntdll.dll'
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardenedWinDoReSpawn(2): New child 2fb0.1318 [kernel32].
2d54.35dc: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
2d54.35dc: supR3HardNtChildGatherData: PebBaseAddress=00000000010b9000 cbPeb=0x388
2d54.35dc: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
2d54.35dc: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
2d54.35dc: supR3HardenedWinSetupChildInit: Start child.
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 1 ms.
2d54.35dc: supR3HardNtChildPurify: Startup delay kludge #1/0: 257 ms, 15 sleeps
2d54.35dc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2d54.35dc:  *0000000000000000-0000000000e8ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000e90000-0000000000eaffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000eb0000-0000000000ec8fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000ec9000-0000000000ecffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000ed0000-0000000000fcafff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000000fcb000-0000000000fcdfff 0x0104/0x0004 0x0020000
2d54.35dc:   0000000000fce000-0000000000fcffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000fd0000-0000000000fd3fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000fd4000-0000000000fdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000fe0000-0000000000fe0fff 0x0004/0x0004 0x0020000
2d54.35dc:   0000000000fe1000-0000000000ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000001000000-00000000010b8fff 0x0000/0x0004 0x0020000
2d54.35dc:   00000000010b9000-00000000010bbfff 0x0004/0x0004 0x0020000
2d54.35dc:   00000000010bc000-00000000011fffff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2d54.35dc:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
2d54.35dc:   000000007fff0000-00007ff7edc0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edc10000-00007ff7edc32fff 0x0002/0x0002 0x0040000
2d54.35dc:   00007ff7edc33000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
2d54.35dc: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supR3HardNtChildPurify: Done after 463 ms and 0 fixes (loop #0).
2fb0.1318: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2fb0.1318: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
2fb0.1318: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2fb0.1318: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2d54.35dc: supR3HardNtEnableThreadCreation:
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: System32:  \Device\HarddiskVolume1\Windows\System32
2fb0.1318: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2fb0.1318: KnownDllPath: C:\WINDOWS\System32
2fb0.1318: supR3HardenedVmProcessInit: Opening vboxdrv...
2fb0.1318: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2fb0.1318: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2fb0.1318: Registered Dll notification callback with NTDLL.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2fb0.1318: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2fb0.1318: \SystemRoot\System32\ntdll.dll:
2fb0.1318:     CreationTime:    2018-01-05T15:56:46.395451500Z
2fb0.1318:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2fb0.1318:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1dd100
2fb0.1318:     NT Headers:      0xe0
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1e0000 (1966080)
2fb0.1318:     Resource Dir:    0x174000 LB 0x6a1d8
2fb0.1318:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.192
2fb0.1318:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: NT Layer DLL
2fb0.1318: \SystemRoot\System32\kernel32.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:04.954227600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0xab868
2fb0.1318:     NT Headers:      0xe8
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0xae000 (712704)
2fb0.1318:     Resource Dir:    0xac000 LB 0x520
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\KernelBase.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:41:43.124345500Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x266000
2fb0.1318:     NT Headers:      0xf0
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x266000 (2514944)
2fb0.1318:     Resource Dir:    0x245000 LB 0x548
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\apisetschema.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:07.095026600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2fb0.1318:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1b398
2fb0.1318:     NT Headers:      0xc8
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1c000 (114688)
2fb0.1318:     Resource Dir:    0x1b000 LB 0x408
2fb0.1318:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: ApiSet Schema DLL
2fb0.1318: supR3HardenedWinFindAdversaries: 0x0
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: Calling main()
2fb0.1318: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2fb0.1318: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: SUPR3HardenedMain: Final process, opening VBoxDrv...
2fb0.1318: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2fb0.1318: supR3HardNtEnableThreadCreation:
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff94e950000 LB 0x00005000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msasn1.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'crypt32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\wintrust.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\wintrust.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume1\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #33 'msasn1.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\crypt32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\crypt32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msasn1.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msasn1.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msvcrt.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msvcrt.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9557b0000 LB 0x0009d000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951c10000 LB 0x00012000 C:\WINDOWS\System32\MSASN1.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951ed0000 LB 0x000f6000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ucrtbase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ucrtbase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9529b0000 LB 0x001ce000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952eb0000 LB 0x0011f000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff954e70000 LB 0x0005b000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\sechost.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\sechost.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff953340000 LB 0x000a1000 C:\WINDOWS\System32\advapi32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'sechost.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\advapi32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\advapi32.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952c20000 LB 0x00058000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-localization-l1-2-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\WINDOWS\system32\Wintrust.dll'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> -626 (\Device\HarddiskVolume1\Windows\System32\bcrypt.dll)
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 60 a9 01 80 01 00 00 00
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\system32\bcrypt.dll' (C:\WINDOWS\system32\bcrypt.dll): rcNt=0xc0000190
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\bcrypt.dll'
2fb0.1318: Warning! Failed to load bcrypt.dll
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'sechost.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'sechost.dll' -> '\Device\HarddiskVolume1\Windows\System32\sechost.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\sechost.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\cryptsp.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\cryptsp.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9515d0000 LB 0x00017000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rsaenh.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rsaenh.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume1\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/Imports: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=2 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\rsaenh.dll'
2fb0.1318: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x8 (<NULL>) on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: Error -22919 in VirtualBox! (enmWhat=1)
2fb0.1318: WinVerifyTrust failed on stub executable: WinVerifyTrust failed with hrc=Unknown Status 0x8 on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'vboxrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'qt5printsupportvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'qt5openglvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #14 'oleaut32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #15 'winmm.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmm.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmm.dll' -> '\Device\HarddiskVolume1\Windows\System32\winmm.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'msvcrt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\winmm.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\winmm.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume1\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'combase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #23 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\oleaut32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\oleaut32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'ole32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'ole32.dll' -> '\Device\HarddiskVolume1\Windows\System32\ole32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #22 'rpcrt4.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #46 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #47 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #48 'combase.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ole32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ole32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'shell32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'shell32.dll' -> '\Device\HarddiskVolume1\Windows\System32\shell32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #73 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #75 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\shell32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\shell32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'advapi32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'advapi32.dll' -> '\Device\HarddiskVolume1\Windows\System32\advapi32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\advapi32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'user32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'user32.dll' -> '\Device\HarddiskVolume1\Windows\System32\user32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'win32u.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #34 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\user32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\user32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5openglvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5openglvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5openglvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5printsupportvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5printsupportvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5printsupportvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'winspool.drv'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'comdlg32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5widgetsvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5widgetsvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5widgetsvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5guivbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5guivbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5guivbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5corevbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5corevbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5corevbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'mpr.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcr100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcr100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'vboxrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'vboxrt.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\vboxrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'opengl32.dll'...
2f",Toby (:
17501,Ubuntu guest fails after waking from windows 10 host sleep,Windows,Linux,VirtualBox 5.2.6,2018-01-26T17:46:47Z,2018-01-26T17:46:47Z,"Hi, 
I have the latest version of VirtualBox -- 5.2.6 running on a windows 10 host.   I've tried a couple of different guest OSes, Fedora Core 27 and Ubuntu 16.04.   Both fail to survive a sleep-wake-cycle on the Windows 10 guest.    

I've tried many things from previous bug reports, more memory, more video memory.   Also with and without 3D acceleration and with and without hardware virtuatization, etc.  

Occasionally, the guest will survive one sleep-wake cycle but will slip into  'Guru Mediation' after the second cycle.  

I have also installed the latest guest additions on the host as well. 

I'll attach the virtualbox log file and the virtualbox hardening log file.  


Please advise. 
Thanks,
Jeff
",jmcdonal
7972,Cannot install extension pack -- VERR_ACCESS_DENIED,Windows,other,VirtualBox 4.0.0,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
17503,VBoxExtPackRegister returned VERR_VERSION_MISMATCH,Windows,Windows,VirtualBox 5.2.6,2018-01-27T09:44:05Z,2018-01-27T09:44:05Z,"VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='VirtualBox version mismatch - expected 5.2 got 5.0'.


Result Code: 
E_FAIL (0x80004005)
Component: 
ExtPackManagerWrap
Interface: 
IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}
",DSquad
17506,It should be possible to boot a guest with an unconnected hotplug disk,Windows,Linux,VirtualBox 5.2.4,2018-01-28T01:57:16Z,2018-01-28T01:57:16Z,"If there is a hotplug virtual disk (a VDI file on an external drive) attached to a SATA controller, the virtual disk is unplugged in the running guest, the external drive is removed and the guest is shutdown, then the guest cannot be booted anymore. I got the following message:
{{{
Could not open the medium 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi'.
VD: error VERR_PATH_NOT_FOUND opening image file 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi' (VERR_PATH_NOT_FOUND).

Fehlercode:
E_FAIL (0x80004005)
Komponente:
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}

Steps to reproduce the problem:

1. Assume you have a Windows 7 host (other host may have the same problem), an USB drive (an USB stick may have the same problem) and a Linux guest (other guests may have the same problem).
2. Shut down the guest.
3. Connect the USB drive to the host.
4. Add a new virtual disk to the guest as a VDI file on the USB drive with a virtual SATA controller. Mark the virtual disk as hotpluggable.
5. Start the guest.
6. Check that the hotplug disk is there: {{{ls /dev/sdb1}}}
7. Unplug the disk: {{{echo 1 > /sys/block/sdb/device/delete}}}
8. Check that the hotplug disk is unplugged (output should be an error message): {{{ls /dev/sdb1}}}
9. Disconnect the USB drive from the host.
10. Shut down the guest.
11. Start the guest.

For a simple test you can omit the steps 5 to 8 and 10.

From my point of view a hotplug disk should be handed like a DVD: It is not necessary that it there (is in the drive) to boot the guest.

Workaround: Disconnect the hotplug disk by hand from the SATA controller before booting, in cold state between step 10 and 11 (in the GUI or by the command {{{VBoxManage storagectl}}}).
 ",dlippold
17405,Bridged Networking Malfunctioning,Linux,all,VirtualBox 5.2.4,2018-01-28T17:24:12Z,2018-01-28T17:24:12Z,"'''Host OS:''' Debian 9.3 (Linux)
'''Hypervisor:''' Virtualbox 5.2.4 
'''Guest OS:''' Security Onion (Elastic) Beta 3, Kali 2017.3, and I feel confident in assuming all OS's would have the same issue and I can test others if needed.

'''Situation:''' This week I upgraded my home lab from older versions of the above software, all previously worked on my hardware without issue, but Bridge Mode Networking is now failing to connect to SOME online resource and has dropped packets when it does connect. However NAT Mode Networking allows access to all online resources without issue.

'''Guest Configuration:''' My SecurityOnion Guest VM has a Bridged Adapter connection on Network Adapter 1, giving it internal vm network and external network access / Network Adapter 2 is listening in promiscuous mode on my switch's Mirrored Port.

Upon installing the guest OS (SecOnion) I began having issues pulling updates from the ubuntu.com software repositories. This was odd because on my host machine Speedtest.net was saying I had a 60+mbps connection to my ISP and furthermore my host machine was able to access ubuntu.com and pull down the same repositories without issue, this is what led me to verifying that I can use NAT but not Bridged Mode. NAT does allow me to access all resources (and update the systme), but I need to use Bridge Mode for my lab.

What's REALLY odd is that even with Bridge mode in its limited capacity, it IS able to pull down Google.com, Wikipedia.com, even Reddit.com with little issue (It does seem like it doesn't fully resolve any of the webpages though -spinning tabs and whatnot). But it completely fails to access Ubuntu.com, Fedora.com, Amazon.com... It's just VERY odd behavior... and it only happens in the VM when using Bridged Mode.

This behavior is repeatable (unable to access ubuntu.com and others) and happens every time I've tried to build a VM on this newer software.

Please let me know if there is any additional information I can provide.

-J

",Id1010terror
17508,USB Passthrough Keyboard sometimes does not detect keystrokes,Windows,other,VirtualBox 5.2.6,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
17510,E_FAIL (0x80004005) err,other,other,VirtualBox 5.2.6,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
17514,Audio stops working on Windows 7 guest,Linux,Windows,VirtualBox 5.2.6,2018-01-31T18:35:26Z,2018-01-31T18:35:26Z,"Hello,
I am running VirtualBox 5.2.6 on Ubuntu 16.04 with Windows 7 guest. When I launch GoToMtg and connect to a conference using computer audio, it starts sound starts to crackle then stops completely. I am using a headset.

This worked flawlessly in 5.1.<latest>

I have an almost identical system, exact same problem on 5.2.6",KLN
12359,Can't switch workspace on Linux host when guest in fullscreen,Linux,Windows,VirtualBox 4.3.2,2018-02-01T04:55:49Z,2018-02-01T04:55:49Z,"Whenever the guest (in this case Windows 7) is running fullscreen (in my case with 2 monitors, one of each guest is replicated in fullscreen on my two physical monitors) I cannot hit right-ctrl and change workspace. Often times the guest menu (at the top) gets locked and/or I am completely ""locked into"" the guest without possibility to move out into the host except for shutting down the guest from within the VM.

This worked without a problem in 4.2.x. Also, whenever I run anything else on the host in fullscreen (youtube video, whatever) the guest VM decides for unknown reasons that I have unplugged all monitors and resizes guest-resolution seemingly randomly. Very annoying!",isecore
17482,Windows 7 guest - Shared Folders empty,Linux,Windows,VirtualBox 5.2.6,2018-02-01T12:40:51Z,2018-02-01T12:40:51Z,"Upgrading from Virtualbox 5.2.0 shared folders on windows 7 guest machine stops to play. 
VBOXSVR network resource is still visible but it's empty.
Adding ""homegroup"" on ""home network"" Windows configuration enable folders, but on machine restart stops again.

Host is Ubuntu 17.10.",pmonaco
17516,Ubuntu Virtual Machine Aborts,other,other,VirtualBox 5.2.6,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
17519,Phantom Menu Bar in Host Network Manager on macOS High Sierra (Version 10.13.3),Mac OS X,Linux,VirtualBox 5.2.6,2018-02-02T09:41:08Z,2018-02-02T09:41:08Z,"When interacting with the Oracle VM Virtual Box Manager Host Network Manger tool, if I move the window (Oracle VM Virtual Box Manager) to another location on the screen a copy of the tool bar separates from the main Oracle VM Virtual Box Manager window in the original location of the window.  I attached a picture.

I'm running:

VirtualBox Graphical User Interface
Version 5.2.6 r120293 (Qt5.6.3)",cfo64nc
17518,Scratchy/cracklinkg sound on all VM with Windows host,Windows,all,VirtualBox 5.2.6,2018-02-02T18:52:43Z,2018-02-02T18:52:43Z,"For quite a long time (at least 5.1.26, but probably earlier, i think i got this problem back in 5.0.6 on winxp, but I'm not sure) there's a problem with scratchy sound on all my VM. It doesn't matter it's windows xp, 8.1, 10 or various linuxes (ubuntu 14.04, 16.04, 17.10, manjaro) sound is scratchy, but new windows (8.1, 10) are worse. I tested it on 3 machines, one with win7 and two with win8.1. It doesn't matter it's new vm, old one, with or without addons.
The best part is, everything is ok on linux hosts (same vm, same pc).

How is sound scratchy? When playing any sound (win8.1 test sounds in device settings are best example) are similar to electronic crackling 50% of time. When playing music it gets a little better, but still ~10% of time it's crackling.
",Akkak
17523,CentOS7 hangs after installing guest additions,Windows,Linux,VirtualBox 5.2.6,2018-02-03T13:08:36Z,2018-02-03T13:08:36Z,"This Virtual machine was working just fine in previous version of Virtual Box. After installing version 5.2.6 of Virtual Box the os was still booting fine. Then I installed Guest Additions and restarted os. Now, the os hangs (see picture attached).",noone
12168,Oracle Virtualbox manager has stopped working,Windows,Linux,VirtualBox 4.2.18,2018-02-04T11:03:41Z,2018-02-04T11:03:41Z,"I have the following scenario:

VirtualBox 4.2.18
Host: Windows 7 Enterprise 64-bit 6GB RAM
Guest: Oracle Linux Release 6.4 32bit 2GB RAM

Virtualbox stopped working twice:
1. After press Reboot button when installation progress had been finished
2. After press Finish button in the last step(Kdump) of configuration process..

I have checked similar threads who had posted the same error at the same stage but there was no resolution or response provided and hence I am creating this ticket.

Thanks,
Nayagam",Nayak
17525,Conflict between VESA VBE 2.0 graphic adapter and NAT network on WINDOWS ME,Windows,Windows,VirtualBox 5.2.6,2018-02-05T03:55:19Z,2018-02-05T03:55:19Z,"When you install VESA VBE 2.0 Oracle VM VirtualBox VBE Adapter to have 32 bits true color on WINDOWS ME MILLENIUM EDITION with a program called SciTech Display Doctor (this also works with win 98) you can't connect with the internet cause it seems that there's a conflict between the NAT network adapter and VESA VBE 2.0 cause I uninstalled SciTech Display Doctor and went back to standard 16 colors graphic adapter and I could access internet again. This doesnt happen with Win 98 I can install it and internet works, it's just with Millenium edition",tonypark77
17504,VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,Linux,VirtualBox 5.2.6,2018-02-05T11:35:34Z,2018-02-05T11:35:34Z,"Upgraded VB on VirtualBox 5.2.6 version.
Run Guest Ubuntu 16.04 host (has not been running/updated for about a month)
Executed ubuntu updates with:

{{{
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
}}}

Was unable to create a symlinks in my shared directory.
Executed the following command which was supposed to help:


{{{
VBoxManage.exe setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/SHARE_NAME 1
}}}

Then unable to start the Guest machine because of GURU error from the subject.",Faly
17526,Memory exception,Windows,Linux,VirtualBox 5.2.6,2018-02-05T16:35:56Z,2018-02-05T16:35:56Z,Get an error message that program is trying to access protected memory location 0x0000000000000040 and on click of OK button guest session ends.,kpenrose
13874,"On host sleep/resume, guest becomes ""aborted""",Mac OS X,Linux,VirtualBox 4.3.22,2018-02-07T12:34:47Z,2018-02-07T12:34:47Z,"Ubuntu 12.04 with up-to-date guest additions. Did not happen in 4.1.

{{{
00:00:23.836304 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:24.049241 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:25.603698 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:25.783293 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:43.873102 Guest Log: VBoxService 4.3.22 r98236 (verbosity: 0) linux.amd64 (Feb 12 2015 16:53:43) release log
00:00:43.873123 Guest Log: 00:00:00.000103 main     Log opened 2015-02-21T04:21:53.707725000Z
00:00:43.873193 Guest Log: 00:00:00.000219 main     OS Product: Linux
00:00:43.873234 Guest Log: 00:00:00.000263 main     OS Release: 3.2.0-23-generic
00:00:43.873273 Guest Log: 00:00:00.000301 main     OS Version: #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
00:00:43.873311 Guest Log: 00:00:00.000337 main     OS Service Pack: #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
00:00:43.873356 Guest Log: 00:00:00.000377 main     Executable: /opt/VBoxGuestAdditions-4.3.22/sbin/VBoxService
00:00:43.873363 Guest Log: 00:00:00.000382 main     Process ID: 2505
00:00:43.873369 Guest Log: 00:00:00.000385 main     Package type: LINUX_64BITS_GENERIC
00:00:43.877150 Guest Log: 00:00:00.004170 main     4.3.22 r98236 started. Verbose level = 0
00:00:43.978632 NAT: DHCP offered IP address 10.0.2.15
00:00:47.310609 Pausing VM execution, reason ""host suspend""
00:00:47.311013 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:00:47.313057 AIOMgr: Endpoint for file '/Users/alex/VirtualBox VMs/t11e-vm1/box-disk1.vmdk' (flags 000c0781) created successfully
00:00:47.372196 PDMR3Suspend: 61 135 737 ns run time
00:00:47.372214 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:00:49.747565 Resuming VM execution, reason ""host resume""
00:00:49.748181 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
00:00:49.748329 AIOMgr: Endpoint for file '/Users/alex/VirtualBox VMs/t11e-vm1/box-disk1.vmdk' (flags 000c0723) created successfully
}}}",atombender
17532,virtualbox-5.2 depends on libfontconfig1 (>= 2.9.0); (Ubuntu 14.04 LTS),Linux,other,VirtualBox 5.2.6,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
17530,"I can not startup my Vbox, Somo time ago changed my computer and from the DVI backups cant run the machine",other,other,VirtualBox 5.2.6,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
16169,after restoring guest XP guest Bugcheck KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e),Windows,Windows,VirtualBox 5.1.8,2018-02-08T15:53:58Z,2018-02-08T15:53:58Z,"The guest runs fine, the problem only happens after restoring a saved state.
The Bluescreen appears only in VBox 5.1 (not in version 5.0) for me and only when AMD-V is enabled.

The CPU is AMD Phenom II X4 965[[BR]]
Host OS: Win7 x64[[BR]]
Guest OS: WinXP 32bit I/O APIC enabled / PAE setting has no effect[[BR]]

Here is the Bugcheck: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)[[BR]]
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

Attached are two minidumps of the guest os. The crash is reproducible every time. Please let me know if you need any more information.",oracle_email_with_a_plus_sign
17535,Guest Additions contain old DirectX9 DLLs,Windows,Windows,VirtualBox 5.2.6,2018-02-12T11:09:20Z,2018-02-12T11:09:20Z,"Hello,

when installing the Guest Additions, the following files are replaced d3d8.dll and d3d9.dll. Unfortunately this are old DLL versions (it should be at least 5.03.2600.5512), the Oracle Version is 5.02.0006.20293. So DxDiag shows an error with those two files. Furthermore, it seems that this error is also causing sound issues with iTunes and VirtualDj 8, as there is a crackling in the sound. Both are using DirectX.

Can you please fix this in the next version of the GuestAdditions?

Kindest regards,
Heiko",Boettgerie
15217,McAFee Agentblocks virtual machine running,Windows,Linux,VirtualBox 5.0.16,2018-02-12T11:15:54Z,2018-02-12T11:15:54Z,"Good Morning, 

I use the Business PDL with O.S. Host Windows 7 Enterprise edition (x64).
In this sistem running McAfee Agent and i '''can't''' uninstall it.
But this block a VirtualBox Process. The VM is extremely important to testing a Engineering Siemens's software on Debian's O.S.

The message error are:

supR3HardNtChildPurify

supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED

Apertura di una sessione per la Macchina Virtuale Debian non riuscita.

The virtual machine 'Debian' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'D:\Bresciani\VM\Debian\Logs\VBoxHardening.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaccia: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

",abresciani@…
17538,Virtual Box displays black screen,Windows,Windows,VirtualBox 5.2.6,2018-02-12T11:31:18Z,2018-02-12T11:31:18Z,I have been using Virtual Box for a class I am in for college. The other day I tried to bring up my Virtual Box VM program and only had a black screen. I have attached a picture showing what my screen has. It just sits there and not doing anything. I have loaded up a new OVA file for my VM program and still get same thing. What can I do to fix this or what is causing this. I have been using Virtual Box and this program for about 4 weeks now.,fuzzwuzzy13
17539,VirtualBox driver crashes when rebooting with kexec on Ubuntu 16.04,Windows,Linux,VirtualBox 5.2.6,2018-02-12T11:33:03Z,2018-02-12T11:33:03Z,"Restarting into another kernel is faster with kexec. There's a crash when I try to reboot into another kernel with kexec. The problem (says the screenshot) is because VirtualBox.

The commands I issued were:

diwou@diwou-VirtualBox:~$ sudo kexec -l /boot/vmlinuz-`uname -r` --reuse-cmdline
[sudo] password for diwou:
diwou@diwou-VirtualBox:~$ sudo systemctl kexec

Then I can see a crash on the GUI screen...

This bug was reported 5 years ago, I read it was marked as obsolete, but I think it's not fixed.",D1W0U
15844,vboxmanage option to enable advertising default route for ipv6,other,other,VirtualBox 5.1.4,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
17213,Distorted audio in Windows 10 FCU or Windows 10 Insider Preview (RS4) guest running on Windows 10 FCU (16299.19) host,Windows,Windows,VirtualBox 5.2.0,2018-02-13T08:43:00Z,2018-02-13T08:43:00Z,"When I run Windows 10 FCU as well as Windows 10 Insider Preview (RS4) guest on top of the Windows 10 FCU (16299.19), the sound played by the virtual machine is very distorted and noisy. Especially when it plays for the first time after VM launch.

When I launched for the first time a Windows 10 FCU in the VirtualBox running also on Windows 10 FCU, immediately after lauch the OneDrive toasted has popped out and I've heard something like very loud white noise instead of Windows 10 notification sound. The next times, VM tried to play sound it was less distorted but still very much.

When I set the volume in sound mixer on VM to smaller value, it's less distorted, then I set volume to bigger value, it's more distorted.

I use the VM with the following setting:
-3 GB of RAM, 32 GB of HDD as SATA drive
-2 CPU cores
-2D video and 3D graphics acceleration enabled
-Intel HD Audio
-USB 1.1 enabled
-EFI disabled
-PAE/NX disabled.
",przemek1234pl
15924,Very large audio delay in Windows XP guest while CPU loaded at 100%,Linux,Windows,VirtualBox 5.1.6,2018-02-13T10:17:48Z,2018-02-13T10:17:48Z,"I discovered a new bug in VirtualBox v5.1 that did not happen in v5.0 and older versions.

When running a Windows XP SP3 guest on a Linux host (with sound configured for ALSA on the host side and AC97 on the guest side), I get very long delays in games (1 to 3 seconds !) between the moment the sound is triggered and the moment it gets played: the higher the load on the CPU, the longer the delay.

Turning on HPET on the guest doesn't change anything...

I'm attaching a log of a short session when I started the VM and a game in it, clicked on menu items (which produce sounds at each click), got the delays each time, and shut down the game and the VM.",dinosaur0
17541,Input/output error when running ./VBoxLinuxAdditions.run on headless guest,Windows,Linux,VirtualBox 5.2.6,2018-02-13T15:47:00Z,2018-02-13T15:47:00Z,"After having installed build-essential on a fresh installed Guest running Ubuntu 17.10 Server (installed from ubuntu-17.10.1-server-amd64.iso) I tried to install the Guest Additions but failed with an Input/output error.

{{{
peter@ubuntu-s:~$ sudo /mnt/VBoxLinuxAdditions.run
sudo: unable to execute /mnt/VBoxLinuxAdditions.run: Input/output error
}}}

Next I tried to install the guest additions for 5.2.7. While this worked so far it produced a ""modprobe vboxsf failed"" message.

After a reboot and a second try to install VirtualBox 5.2.7 Guest Additions for Linux the installation finished without an error.

For further details see attached console-log-1.txt.",PeterG
16370,Main window showing guest freezes after using virtualdesktop on Win7,other,Linux,VirtualBox 5.1.12,2018-02-13T17:28:01Z,2018-02-13T17:28:01Z,"Host: Windows 7, running virtual desktop program Dexpot version 1.6.10, Build 2362. 
Host Video card: NVIDIA GeForce GTX 960
VirtualBox version 5.1.12r112440 (QT5.6.2)

Guest OS: KUbuntu 16.04.1

This behavior started after I just upgraded from VirtualBox version 5.0.?? to version 5.1.12. 

When VB is in fullscreen mode, on the host I switch virtual desktops away from the desktop showing VB guest OS. When I switch back to the host virtual desktop the guest OS screen is frozen. HOWEVER, the VB preview window works. I can see applications switch, and can use a console to tell the machine to reboot. 

The screen does not feeze if the VB guest OS is kept in Windowed mode (not full-screen mode). In fact, switching to windowed mode unfreezes the display. 

The attached log is after the guest screen freezes, then I switch VB to windows mode to unfreeze the display, then switch virtual desktops on the host a couple of times. 
",P-Dog
17542,VirtualBox 5.2.6 Guru Meditation Error,Windows,Linux,VirtualBox 5.2.6,2018-02-13T17:37:21Z,2018-02-13T17:37:21Z,"Since VirtualBox 5.2.6 my VirtualBox keeps crashing with a Guru Meditation Error on Windows 10 Host with Debian guest.
My Log.txt is attached.",Frank Breitling
16105,Audio capture for multiple VMs problem since 5.0 version,Linux,other,VirtualBox 5.1.8,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
17545,"Drag and Drop does not work: Windows 7 host, Fedora linux guest",Windows,Linux,VirtualBox 5.2.6,2018-02-14T16:41:17Z,2018-02-14T16:41:17Z,"The context:
Host: Windows 7 Pro SP 1
Guest: Fedora 23 linux
Guest Additions 5.2.6 installed and confirmed to work (for example, dynamic screen resizing works, and bidirectional clipboard works).

The problem:
Drag and Drop between guest and host does not work in either direction. When dragging from Windows 7 host to Fedora 23 linux guest the file icon under the mouse pointer in the guest windows has a red, ""not allowed"" sub-icon once the guest window boundary is crossed. When released inside a file manager window, the icon disappears, and the files are not copied. This happens both with directories and simple text files.

When dragging from guest to host the file icon under the mouse pointer disappears at the guest window border and no files are copied.",ryac
17423,Oracle Linux 6 Booting Error From vboxadd,Windows,Linux,VirtualBox 5.2.4,2018-02-15T01:41:36Z,2018-02-15T01:41:36Z,"When booting version 6 of Oracle Linux (4.1.12-112.14.2.el6uek.x86_64 in this case but failed in previous ones) in the vboxadd script. This is because the log is not yet initialized. By adding line 256 shown below, the error no longer occurs and the script completes.

    253     fi  # INSTALL_NO_MODULE_BUILDS
    254 
    255     # Put the X.Org driver in place.  This is harmless if it is not needed.
    256 log ""Dons fix.""
    257     ""${INSTALL_DIR}/init/vboxadd-x11"" setup 2>> ""${LOG}""
    258     # Install the guest OpenGL drivers.  For now we don't support
 ",DonC
13118,Presenting compatible CPU architecture to Mac OS X guest VMs,Mac OS X,other,VirtualBox 4.3.12,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
17544,"VM not responsive after hibernation: Mac OS host, Ubuntu Linux Guest",Mac OS X,Linux,VirtualBox 5.2.6,2018-02-15T08:52:11Z,2018-02-15T08:52:11Z,"This is the version info:

Version 5.2.6 r120293 (Qt5.6.3)

Host OS:  Mac OS, 10.12.6

Guest OS: Ubuntu 16.04 64bit

After a period of hibernation of the host os, the vm becomes not responsive. Though the VM looks like where it is left before hibernation, any actions including clicking and  keyboarding can not make it work.  Power-Off is the only way to kill the VM and start it again.",JayyCee
6930,Error: Failed to open a session for the virtual machine - session was closed before any attempt to power it on,other,other,VirtualBox 3.2.4,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
17337,guest windows distorted in seamless mode works on 5.2.2 (no such problems on 5.1.30),Linux,Windows,VirtualBox 5.2.0,2018-02-15T20:19:34Z,2018-02-15T20:19:34Z,"== STEPS TO REPRODUCE
 1. Using Kubuntu Trusty host, Create XP VM in ≤ 5.1.30. Seamless mode should work fine (see expected results below).
 2. Upgrade to 5.2.2. 
 3. Boot XP guest.
 4. Switch to seamless mode.

== EXPECTED RESULTS
 1. Guest desktop disappears.
 2. Host window decorations disappear.
 3. Space is drawn on the host desktop for the guest windows.
 4. Guest windows act like host windows, responding appropriate to movement, e.g.
 5. Guest windows appear normally.

== ACTUAL RESULTS
All of the above assumptions are correct except for the 5th one. The space is drawn, the windows act normally, there are no other decorations, but every guest window is a visual nightmare. See attached screenshot.

== NOTES
 * Host is Kubuntu Trusty running the 4.2.0-42-generic kernel and is fully up to date and restarted.
 * Tested with versions from the repos at download.virtualbox.org: 5.1.30-118389~Ubuntu~trusty and 5.2.2-119230~Ubuntu~trusty. In both cases, the expansion packs and guest additions were updated accordingly.
 * Guest video memory is maxed out.
 * Turning acceleration off, enabling both 2D/3D or one or the other had no effect.
 * Initially the guest was using multiple monitors. Disabling the virtual screen had no effect. Lowering the number of monitors to one had no effect, either.
 * Full screen, scaled, and normal modes all function appropriately.
 * VM has been running for years with no problems.
 * Logs are attached. You should see the switch to seamless at 0:00:48.457777.",Walter Lapchynski
17546,Windows 10 guest keeps hanging,Windows,Windows,VirtualBox 5.2.6,2018-02-16T19:53:37Z,2018-02-16T19:53:37Z,"I'm using VirtualBox v5.2.6r120293. My host and guest are Windows 10. The guest is frequently hanging, becoming completely unresponsive; when it does, VirtualBox Manager will oftentimes be unresponsive, too. My only recourse is to close either the guest or the VirtualBox Manager, sometimes having to resort to doing so via Task Manager. After such an event, the guest has a status of ""Aborted"" but I can re-start it without apparent issue.

The guest just froze again; VirtualBox Manager didn't freeze this time. The VirtualBox Log Viewer lists five log files; however, I don't see much of interest therein except the last line which reads (in VBox.log and VBox.log.2) ""GUI: Request to close machine-window."", (in VBoxHardening.log) ""4a88.4ccc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xcfffffff (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1429056 ms, the end);"", and (in VBox.log.3) ""GUI: Passing request to close Runtime UI from machine-logic to UI session."" I've attached the log from Machine > Show Log > Save.

Any suggestions on how to resolve this issue?",CGW
17548,[5.2.6 r120293] Guest linux hangs on boot-up if audio is enabled,Windows,Linux,VirtualBox 5.2.6,2018-02-18T10:16:00Z,2018-02-18T10:16:00Z,"Host :- Windows 7 Enterprise 64 Bit
Guest:- Linux unix 4.13.0-32-generic lubuntu 17.10 64 bit
Audio :- ICH AC97

When i unable audio support linux failed to boot-up and if i disable everything works correctly.
",manoj_red_hat
15694,WinXP guest BSOD after start from saved state in 5.1.2,Windows,Windows,VirtualBox 5.1.2,2018-02-18T14:49:56Z,2018-02-18T14:49:56Z,After I update from 5.0.26 to 5.1.2 my WinXP guest is BSODing just after start from saved state.,tico-tico
17549,Themes and UI elements missing after installing Guest Additions,Linux,Linux,VirtualBox 5.2.6,2018-02-18T18:12:42Z,2018-02-18T18:12:42Z,"Host: Debian 8 / jessie
Guest: Ubuntu 16.04.3 LTS (Xenial)

After installing Guest Additions on the guest, all of the the theming is gone, all of the icons are blank / x-ed out.  See attachment.",VeHav2GoVeeper
14632,Double click not working with precision touchpad -> believed fixed in releases greater than 5.1.24,Windows,all,VirtualBox 5.0.4,2018-02-19T15:33:15Z,2018-02-19T15:33:15Z,"Hi! Im using an Acer Aspire Nitro v17 (VN7-791G-76Z8) which has Precision Touchpad (the new touchpad standard which enables to use all Windows 10 gestures). Im using VirtualBox 5.0.4 with 5.0.4 extensions and Windows 10 x64 Home as Host and Windows 7 x86 as guest (the same error happens in Windows x64 as guest). The problem is that when using the touchpad, I cannot use double click in the guest but I have to do 3 clicks instead to get the double click effect (trust me, that extra click annoys me a lot). If I use a standard mouse, there is not problem.",matias-uy
17551,Error relaunching VirtualBox process : 5,Windows,Windows,VirtualBox 5.2.6,2018-02-19T15:36:29Z,2018-02-19T15:36:29Z,"VirtualBox crash during Windows 2012 server installation on new VM. Then get an error message when i was trying to restart VM.
",cbr45
17391,VB 5.2.4 - Guest Additions won't install on Win 10 Guest,Mac OS X,Windows,VirtualBox 5.2.4,2018-02-20T17:26:52Z,2018-02-20T17:26:52Z,"Host: Mac OS Sierra 10.13.2
Hardware is Macbook Air 11"" - mid 2011 
Guest: Windows 10.0 16299 Build 16299

Guest Additions hangs on driver install.  Same issue with 5.2.2. In both cases I had to revert back to 5.2.0 which installs and works fine.
",SteveB
17449,Virtualbox general protection fault,Linux,Windows,VirtualBox 5.2.4,2018-02-21T18:14:32Z,2018-02-21T18:14:32Z,I am running Virtualbox on Gentoo 64 bit OS kernel linux-4.14.13 and am getting general protection fault while running the VM and Virtualbox crashes.,adimanav
16998,driver services missing,Windows,Windows,VirtualBox 5.1.26,2018-02-23T09:31:58Z,2018-02-23T09:31:58Z,"NtCreateFile(\Devie\VBoxDrvStub)failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 RETRIES) (rc=-101)

Make sure the kernel module has been loaded succfully.
where:supR3HardenedWinReSpawn what:3 VERR_OPEN_FAILED (-101) -file/
Device open failed. Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
",amrtin34
17014,Fedora Gnome slow UI performance,Windows,Linux,VirtualBox 5.1.26,2018-02-23T10:35:13Z,2018-02-23T10:35:13Z,"I've installed fresh and latest Fedora 26 as a VM and when I'm trying to use it, I'm receiving slow GUI response and overall graphic performance is bad. I've tried to use 3d acceleration as well, so the guest starts normally but when GUI part is loaded and login window appeared it's starts to work so slowly, that it's impossible to do anything.

The guest has 4vcpu's, 128mb of video memory and virtualbox additions installed. I'm using windows 10x64 Enterprise (build 10240) with latest intel video drivers (Intel® Graphics Driver for Windows* [15.33]) and latest virtualbox (Version 5.1.26 r117224 (Qt5.6.2)). I have plenty of RAM and i5-3470.",mate
14883,Sound Blaster 16 Issues Located,other,other,VirtualBox 5.0.10,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
17561,VBOX_E_FILE_ERROR,Linux,Linux,VirtualBox 5.1.28,2018-02-23T18:14:15Z,2018-02-23T18:14:15Z,"VirtualBox-5.1.x86_64 on Red Hat Enterprise Linux Server release 6.6
2.6.32-504.el6.x86_64
/VirtualBox-5.1-5.1.28_117968_el6-1.x86_64

We have a process we have been using for years where we take a Virtual Machine image and convert it to an OVA.  We recently took a new Virtual Machine image for the input because of the Spectre and Meltdown SV's so we need an updated VM image.   The size of the image changed slightly, that is about all I can tell.

I cannot find any documentation or reference that explains what this message means.

/opt/VirtualBox/VBoxManage export VBOX_8_56_07_SHELL --output /ds2/templates/vboxshell.23492/VBOX_8_56_07_SHELL.ova --vsys 0 --product 'XXX VBox Shell Appliance' --vendor XXX --version 8.56.07
0%...10%...20%...30%...40%...50%...60%...70%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance write failed
VBoxManage: error: File not accessible or erroneous file contents
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: ""int handleExportAppliance(HandlerArg*)"" at line 1121 of file VBoxManageAppliance.cpp
",lno184
17476,Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10,Windows,other,VirtualBox 5.2.6,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
11976,long paths  (>260chars) cannot be created using a host:win + guest:linux setup,Windows,Linux,VirtualBox 4.2.16,2018-02-23T21:23:47Z,2018-02-23T21:23:47Z,"From https://github.com/mitchellh/vagrant/issues/1953 and https://github.com/isaacs/npm/issues/3670, VirtualBox on windows cannot generate paths longer than ~260 characters on windows, despite windows supposing UNC paths to allow for ~32k character paths. This means that using things like Vagrant, with a project that uses node/npm, is blocked by VirtualBox because node module dependencies (but also just any deeply nested software project being tested in a virtualbox VM) end up having paths that are longer than the standard 260 character limit.

Somewhere, VirtualBox is not communicating the correct error from host to guest OS; it would be extremely useful if this was solved somehow (allowing UNC paths by default? perhaps something else altogether)",Urrich
17566,"""VBoxManage natnetwork list"" output incomplete",Mac OS X,all,VirtualBox 5.2.6,2018-02-26T15:46:42Z,2018-02-26T15:46:42Z,"The command ""VBoxManage natnetwork list"" does not show as much information about configured networks as ""VBoxManage list natnetworks"" does.

The attached ""output.txt"" shows the output of the two commands for an example natnetwork.

If a network has ports forwarded, this part of the configuration can only be seen with ""VBoxManage list natnetworks"".

It's counter-intuitive that not everything about natnetworks can be observed/managed with ""VBoxManage natnetwork ..."". Technically, this behaviour is documented [https://www.virtualbox.org/manual/ch06.html#network_nat_service] but it's easily overlooked. The documentation should emphasise more clearly that not all natnetwork-related commands can be reached with ""VBoxManage natnetwork ..."". Or, alternatively an additional command-line argument in the spirit of ""VBoxManage natnetwork list --detail"" would print the port forwardings as well.",damiano++
17568,Option to bundle installation media into exported VM,other,other,VirtualBox 5.2.6,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
17183,Ubuntu guest on Windows host not properly shut down,Windows,Linux,VirtualBox 5.1.28,2018-02-27T08:03:21Z,2018-02-27T08:03:21Z,"It seems that after installing version 5.1.28, Ubuntu guest (32-bit version 16.04.3 LTS) cannot properly shutdown, and an exception is thrown. State of ubuntu guest is displayed as ""abandoned"" afterwards.",Kanaris
17547,Facing NS_ERROR_FAILURE on starting all virtual machines,Mac OS X,Linux,VirtualBox 5.2.6,2018-02-27T22:22:54Z,2018-02-27T22:22:54Z,"Failed to open a session for the virtual machine Ubuntu.

The virtual machine 'Ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}



Host OS: 10.13.1 MacOS High Sierra

I couldn't find any related log file anywhere. Please help. This is blocking me. Tried reinstall multiple times

Also. tried all the solutions suggested on this thread https://www.virtualbox.org/ticket/16015

Nothing worked.

",Rakesh Sharma
17550,drop when creating snapshot,other,other,VirtualBox 5.2.6,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
17296,Error in supR3HardenendWinReSpawn,all,Windows,VirtualBox 5.1.30,2018-02-27T23:27:20Z,2018-02-27T23:27:20Z,"My virtual box VMs do not start anymore, I get rc=-5640 for all VMs. I have also installed the latest version of docker toolbox (Hyper-V disabled) where the default-VM also stopped working.

Reinstallation and also rollback to version 5.1.14 did not resolve the issue.",danielguenzel
17555,"Win10 ""Display driver failed to start"" always if 3D accel is enabled (Linux host)",Linux,Windows,VirtualBox 5.2.6,2018-02-28T05:24:18Z,2018-02-28T05:24:18Z,"Linux 17.10 host using X.Org (not Wayland), Intel i7-8700K built-in graphics.

Every time the Win10 guest starts, a ""slide out"" notification says:

   ""Display driver failed to start""

(and the desktop can not be resized I'll attach a screen shot).

I've re-installed the Guest Additions multiple times and rebooted the host too.

Finally I tried disabling 3D Acceleration for the guest, and now it works okay.

I'll attach log files which might be useful.  LMK if you need other info.

",Jim Avera
17559,Error al mostrar informacion,Windows,all,VirtualBox 5.2.6,2018-02-28T06:42:10Z,2018-02-28T06:42:10Z,al mostrar la informacion si el puntero esta en el anfitrion o en la MV sale codigo html,FalconXCI
17560,System Unstable,Windows,other,VirtualBox 5.2.6,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
17562,[Feature Request] Treat virtual USB hard disk as removable,all,Windows,VirtualBox 5.2.6,2018-02-28T08:42:49Z,2018-02-28T08:42:49Z,"Hello,

when adding a virtual hard disk drive via an USB storage controller, at least Windows will treat the connected drive as an ""USB Mass Storage"" device but in **fixed**-layout.

Also, when checking the ""Hot-plug""-feature of the hard disk, the Drive will be treated as fixed-disk.

My expectation was, that when checking ""Hot-Plug"" it would be a removable one.

Would it be possible to optionally set the ""Removable-Bit"" in the USB-Drive's properties, so that it is marked as ""removeable"" ?

Would be great, as some applications check drives for this.

Thank you and kind regards,
Wolfgang",Wolfgang Andreas
14747,No sound. Windows 7 host / Arch Linux guest.,Windows,Linux,,2018-02-28T09:22:23Z,2018-02-28T09:22:23Z,"I have the same problem as described in https://www.virtualbox.org/ticket/14361.
I see ""DSound: CreateCaptureBuffer E_FAIL"" and ""DSound: playback start E_ACCESSDENIED"" in the logs.

VirtualBox v5.0.8 (it is not available in the version list for some reason).
",noname1
17474,Black Screen of Death after update to 5.2.6 from 5.2.4,Windows,Linux,VirtualBox 5.2.6,2018-02-28T09:59:38Z,2018-02-28T09:59:38Z,I am using Windows 10 to run Oracle Virtual Box 5.2.4. The notification of an update came and I updated it to the latest (5.2.6) and that was fine. I have a virtual machine running Ubuntu 16.04 and while running the old vm tools I updated the vm tools and it crashed. The virtual machine will not boot past the Oracle boot screen,Dominic M
17571,Guest additions will not build using gcc 6,Windows,Linux,VirtualBox 5.2.6,2018-02-28T14:51:56Z,2018-02-28T14:51:56Z,"See attached log.
This is on a Ubuntu 1204 guest using gcc6 from 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test 

Builds are OK using gcc5 from same source",tomasth
17479,Ubuntu host does not start after 5.1.32 Guest Additions installed,Linux,Linux,VirtualBox 5.1.32,2018-02-28T15:03:15Z,2018-02-28T15:03:15Z,"The issue is the same as in https://www.virtualbox.org/ticket/17467 in 5.1.32: Ubuntu starts, but then stops at some moment after upgrading VirtualBox from 5.1.30 in 16.04 host to 5.1.32 and the guest additions to 5.1.32. The guest OS is 16.04 as well.
The only way to load the system is to uncheck the option ""Enable 3D Acceleration"".
All features (with unchecked ""Enable 3D Acceleration"") work: buffer, sharing folders etc.
There was a recent update of mesa library from 17.2.2 to 17.2.4 at the same time of 5.1.30->5.1.32, can they be related?",ar123
17575,macos - virtualbox manager window toolbar,Mac OS X,all,VirtualBox 5.2.6,2018-02-28T16:17:29Z,2018-02-28T16:17:29Z,"Hi all, i have searched about something this but, could not find anything yet.  So i created new, but you are able to merge-join this already open and releated one.

I attached a screenshot.  As far as i remember this problem has been there from the first release of 5.2.

As you can see from the attachment,
- toolbar is there, over the guest vm item
- toolbar's buttons are not visible but functional, so you can click one of it and execute the releated command
- minimize, maximize, window change etc does not fix or affect it
- sometimes it start without toolbar, but when you select and run a command for one guest item then toolbar is comming again with same problematic state.
  ",AOZKESEK
17565,appcrash virtualbox.dll,other,all,VirtualBox 5.2.6,2018-02-28T16:20:18Z,2018-02-28T16:20:18Z,"It is not possible to create a virtual machine, when creating, error occurs.

O.S: windows7 32bit ver:6.1.7601.2.1.0.256.1

  Nombre del evento de problema:	APPCRASH
  Nombre de la aplicación:	VirtualBox.exe
  Versión de la aplicación:	5.2.6.20293
  Marca de tiempo de la aplicación:	5a5cc3df
  Nombre del módulo con errores:	VirtualBox.dll
  Versión del módulo con errores:	5.2.6.20293
  Marca de tiempo del módulo con errores:	5a5cc3f2
  Código de excepción:	c0000005
  Desplazamiento de excepción:	001edcd7
  Versión del sistema operativo:	6.1.7601.2.1.0.256.1
  Id. de configuración regional:	11274
  Información adicional 1:	0a9e
  Información adicional 2:	0a9e372d3b4ad19135b953a78882e789
  Información adicional 3:	0a9e
  Información adicional 4:	0a9e372d3b4ad19135b953a78882e789
",ndarz
17527,appcrash virtualbox 5.2.6 on win7 32 bit,Windows,Linux,VirtualBox 5.2.6,2018-02-28T16:20:38Z,2018-02-28T16:20:38Z,"Hello kindly help us solve the application crash every time we press on ""New"" to create a new Machine. We are using win 7 32bit..

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	5.2.6.20293
  Application Timestamp:	5a5cc3df
  Fault Module Name:	VirtualBox.dll
  Fault Module Version:	5.2.6.20293
  Fault Module Timestamp:	5a5cc3f2
  Exception Code:	c0000005
  Exception Offset:	001edcd7
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

",reviewsarl
17569,QtCreator does not work on Linux Ubuntu after new Update,Windows,Linux,VirtualBox 5.2.6,2018-02-28T23:13:10Z,2018-02-28T23:13:10Z,"Host: Windows 10 Guest: XUbuntu 14.04 linux (64 bit sytem)Guest Additions 5.2.6 installed.

QtCreator does not work on Linux Ubuntu after new Update.
QtCreator does not start after an update. 
VirtualBox graphics adapter: This device is not working.

Error message: OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.

 Can somebody help?",m.k.IOSB
17578,Blue screen after upgrading to 5.2.6 version,Windows,Windows,VirtualBox 5.2.6,2018-03-01T01:54:57Z,2018-03-01T01:54:57Z,"5.1.30 version of the work is normal, upgrade to 5.2.6 version of the virtual machine and the host has a blue screen phenomenon.
The following is the host debugging information.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61948, 2332810, 1, 2332810}

Probably caused by : memory_corruption ( nt!MiDereferenceIoPages+ccea8 )

Followup:     MachineOwner
---------

nt!KeBugCheckEx:
fffff802`1ad85430 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe68b`5f1bf1b0=000000000000001a",Minghao
17351,Virtual box GUI bad access crash on NAT network settings edit,Mac OS X,other,VirtualBox 5.2.0,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
17581,Vbox Guest Additions support for kernel-4.16.0-rc2,Windows,Linux,VirtualBox 5.2.6,2018-03-02T08:24:33Z,2018-03-02T08:24:33Z,"1> Virtual Box version - 5.2.6 r120293

2> Created Virtual Machine  ( CentOS Linux (3.10.0-693.el7.x86_64) 7 ).

3> Default Guest additions image ( which comes when we mount it from devices options ) is working fine.  

4> Downloaded Linux Kernel  ( version - 4.16.0-rc2 )

5> Compiled Linux Kernel ( version - 4.16.0-rc2 ) and booted with it.

6> Guest Additions stopped working, so I debugged around it.

7> And re-installed default guest addition, but its not working ( auto-size guest display is not working  )

8> Downloaded Guest Addition iso image ( VBoxGuestAdditions_5.2.8.iso ) from ""http://download.virtualbox.org/virtualbox/5.2.8/"".

9> Run the Vbox Guest additions agains. I see some compilation errors. Attaching logs.

So I just want to understand if I did something wrong here or is the kernel with which I have booted is still not supported in Virtual Box guest additions 5.2.8.
  

",Zubraj
17572,USB device named incorrectly,Linux,Windows,VirtualBox 5.0.40,2018-03-02T08:49:28Z,2018-03-02T08:49:28Z,"Hi All,

Really odd behaviour we are getting from our VMs. We have 3 VMs running windows 7 and each has a dongle that grants access to proprietary software. 2 dongles grant access to HASP software and 1 grants access to Windfarmer. These usb devices are incorrectly named in Virtual box which is causing some confusion, We can only use Windfarmer software when one of the ""HASP"" dongles is connected and vice versa.

Not sure how/when this began happening or why. This would be a purely aesthetic problem but the two HASP dongles are identical and cannot be distinguished between each other using the USB filter so occasional they are assigned to the incorrect VM which means we have to manually fix it.

Logs attached.  





",DanitDan
17580,PulseAudio-related segmentation fault from PowerShell beeps,Linux,Windows,VirtualBox 5.2.8,2018-03-02T09:12:00Z,2018-03-02T09:12:00Z,"I previously reported this issue as https://bugs.debian.org/889791 and was requested to report it here.

On a Debian buster/sid amd64 host, using virtualbox 5.2.8-dfsg-1 packages, with kernel 4.15.7, when running a Windows 7 guest using the PulseAudio host audio driver and ""ICH AC97"" audio controller, running PowerShell and causing repeated beeping (e.g. by pressing `^G` repeatedly and `<Enter>` occasionally) will cause VirtualBox to crash with SIGSEGV.

I was able to reproduce the issue using the Microsoft-provided [https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ ""IE8 on Win7 (x86)"" VM image] after installing the [http://www.realtek.com.tw/downloads/downloadsCheck.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false Realtek AC'97 Audio Codecs] but was unable to reproduce it from terminal beeps using a Linux image.  I was also unable to reproduce the issue with the ""Intel HD Audio"" audio controller using 5.2.8-dfsg-1, although it was previously reproducible with 5.2.6-dfsg-3+b1.

I will attach VBox.log and a backtrace momentarily.

Thanks,
Kevin

Note: This sounds similar to https://www.virtualbox.org/ticket/15725 which was closed for lack of follow-up.",kevinoid
17582,Guest Addition don't work with latest version of Fedora 27,other,other,VirtualBox 5.2.6,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
17564,Lock-up in the file browser on rename,Linux,all,VirtualBox 5.2.6,2018-03-03T20:49:55Z,2018-03-03T20:49:55Z,"Reprod as follows:

- Create a new virtual machine
- Add new storage attachment
- Choose 'add hard disk'
- Navigate to a file (pretty much any file or folder will do)
- Right-click 'rename'
- Hit backspace to remove the content of the filename so it is blank.
- Now click 'open'

A dialog is permanently displayed on the screen saying:

The name """" can not be used.

Try using another name, with fewer characters or no punctuation marks.

From this point there is no option but to kill VirtualBox.
",Biff
17585,Audio Output and Input issues on Ubuntu 17.04 with Windows 10 Host,Windows,Linux,VirtualBox 5.2.6,2018-03-04T01:01:21Z,2018-03-04T01:01:21Z,"There are two Audio issues that I've found, one is already documented and the other is not.

Firstly, audio output periodically becomes filled with static in the most recent releases (I believe 5.2.6 was the start of it).  The static is not constant, but rather it comes and it goes.  This has persisted for the past two versions I've used, but as I've stated previously it's already known.

Secondly, with the most recent release of Virtualbox (5.2.8) my guest does not detect any input Audio.  I have tried all of the various available audio drivers, and none of them detect any form of audio input.  Reverting back to 5.2.6 has rectified the issue.",Aaro
17567,why can't played  camera video  in windows 7  guest  by  web browser  with  DirectX,other,other,VirtualBox 5.1.30,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
17587,exiting full screen resizes guest desktop size,Windows,Windows,VirtualBox 5.2.8,2018-03-05T09:01:41Z,2018-03-05T09:01:41Z,"Steps to reproduce:
1. Turn on Auto-resize Guest Display.
2. Enable Full-screen Mode.
3. Turn off Auto-resize Guest Display.
4. Disable Full-screen Mode.
Guest display is resized despite auto-resize is off.

This bug might be related to #6917, #7219 and possibly also to #14948.",_mik
17589,No virtual screen repaint when external monitor is connected to laptop.,Windows,Linux,VirtualBox 5.2.8,2018-03-05T10:44:33Z,2018-03-05T10:44:33Z,"I have Windows 10 host with Ubuntu 16.04 guest. With enabled 3D acceleration (which is required because without that everything is laggy) and external monitor connected (tested with dvi and mini display port), the drawing on virtual screen freezes when in gnome. It does not matter whether monitor is an extension, clone or primary display. Immediately after monitor disconnection, the virtual screen starts to repaint.

Under the frozen screen the system is running (cursor changes with the windows even after repositioning which is not visible on the frozen screen, ctrl alt fx can be used to display working and visible shell).

When 3D acceleration is disabled, screen repaints fine with external monitor connected. 
I tested also development version 5.97 with the same result.",mvodolan
17552,Invalid SELinux context for /etc/ld.so.cache and/or restorecon,Mac OS X,Linux,VirtualBox 5.2.6,2018-03-05T17:19:01Z,2018-03-05T17:19:01Z,"Every time my Fedora 27 guest boots, when I log in, I have audit alerts relating to ""restorecon"" being denied access to ""/etc/ld.so.cache"".  I am not strongly familiar with SELinux, but, after reviewing bug reports to the Fedora bug tracker, I believe the cause of the issue is the VirtualBox Guest Additions invoking ""restorecon"" with an incorrect security context, as it attempts to set the proper security context on ""/etc/ld.so.cache"".

I have the guest additions 5.2.7-120528 installed on the guest, and I keep the Fedora 27 packages up to date.",Kevin L Mitchell
17593,Unable to Rename Screenshot - Keyboard Capture,Mac OS X,other,VirtualBox 5.2.8,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
17594,Tela azul,other,other,VirtualBox 5.2.8,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
17595,Try to attach USB device to VM crashes the VM,Windows,Linux,VirtualBox 5.2.8,2018-03-06T14:51:24Z,2018-03-06T14:51:24Z,"When enabling access to intel USB device (Vendor ID: 8087 Product ID: 07dc) the VM gets totally stucked and a reboot of the host is necessary. That is easily reprocible and happens each time.

The logs displays this error message:
ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={c19073dd-cc7b-431b-98b2-951fda8eab89} aComponent={HostUSBDeviceWrap} aText={USB device 'Intel Corp.' with UUID {674944f8-07e8-4224-b303-cb4161d16cb4} is busy (state 'CapturingForVM[Detach]'). Please try again later}, preserve=false aResultDetail=0

Tried with Lubuntu & Debian Guest OS. Of course guest Add-ons have been properly installed.

The bluetooth device works properly on the host.

",jeanbox
15149,"Files are not deleted when deleting many files, but VM thinks they are",all,Linux,VirtualBox 5.0.14,2018-03-06T15:54:46Z,2018-03-06T15:54:46Z,"When we try delete many individual files in the VM on a shared folder, the files still exists but the VM reports them as not existant. The Symfony cache:clear command does this and fails because directory's can't be removed (the VM thinks they are empty but they are not).

Host: tested with Windows and OSX
Guest: tested with Debian 8 64, Ubuntu 14.04 64, Ubuntu 14.04 32
Note: Debian 7 64 does not have this problem.

To reproduce:
- Clone https://github.com/marijnotte/file-delete-test
- Install Vagrant
- Do vagrant up in the project folder
- When provisioned login into the box (vagrant ssh)
- cd /vagrant
- php composer.phar install

Error message:

{{{
  [RuntimeException]                                                                                                                                                                                                                        
  Error Output:                                                                                                                                                                                                                             
                                                                                                                                                                                                                                            
  [Symfony\Component\Filesystem\Exception\IOException]                                                                                                                                                                                    
  Failed to remove directory ""/vagrant/app/cache/pro~/doctrine"".    
}}}

- cd /vagrant/app/cache/pro~/doctrine
- ls --> directory is empty
- Go to the same directory on your host --> directory is not empty",Marijn
15897,Symfony clearing cache fails when done through shared folder (rmdir fails),Windows,Linux,VirtualBox 5.1.4,2018-03-06T15:58:02Z,2018-03-06T15:58:02Z,"I have opened a bug on the Symfony bug tracker (https://github.com/symfony/symfony/issues/19851), however, I believe this is an issue between Linux and Windows with a shared folder.

I am using RHEL7 on the guest machine and windows 8 on the host. The /var/www/ dir is a mount of a shared folder on the windows machine (a Virtual Box share). I have installed Symfony on the guest, so its files are done through the share (I can browse them on the host).

Everything seems to run fine except clearing of cache. This fails saying that there are files in the dir that it is trying to run an rmdir on:
{{{
(Failed to remove directory ""/var/www/html/tut1/var/cache/pro~/twig"": rmdir(/var/www/html/tut1/var/cache/pro~/twig): Directory not empty.)
}}}
Looking in windows, I can see that there are a bunch of files still showing there, however, when I try list (dir, ll and a bunch of other options attempted), it shows no files. Yet if I try to do an rm -R on the dir:
{{{
rm -R /var/www/html/tut1/var/cache/pro~/twig/
}}}
it says that it can't:
{{{
rm: cannot remove ‘/var/www/html/tut1/var/cache/pro~/twig/’: Directory not empty
}}}

If I remount the /var/www/ mount (or reboot the guest), the files all show and I can run the rm command without any issues.

It's like in the Symfony script it is sending the unlink command that is being reported as successful even though on the host the files are not deleted.

I will attach an strace log if that is of any help. The main lines I looked at are copied into the Symfony bug report.

If you want to replicate this, install with a linux guest, windows host and install and run Symfony on it. Browse to a prod page (go to /project-name/web/app.php) and then clear the cache with the following command:
{{{
php bin/console cache:clear --env=prod
}}}
if you then delete the /project-name/var/cashe/pro~ dir and try that command again (or remount the share) it will work.",MicWit
17598,VMs do not adapt to hi-res screen,Linux,Windows,VirtualBox 5.2.8,2018-03-06T23:31:27Z,2018-03-06T23:31:27Z,"I have installed VirtualBox 5.2.8 on a Lenovo X1 Carbon 5th generation, which is running KUbuntu 17.10.1, which has a max screen resolution of 2560x1440.

Guest operating systems will not adapt to the resolution of the laptop screen (neither in terms of proportions, nor size). Guest additions are correctly installed.

All attempts to condition the behaviour of the VMs fail, and the desktop of the VMs appears small and surrounded by a black margin to the right and below.

I have (obviously) tried the File-Environment-Display settings, auto resize guest, VBoxManage setextradata, etc. but none of these works.

It is possible to increase the resolution a little, but this setting does not persist, and is never in line with the actual resolution. In the Win10 machine, the pointer is also misaligned, making it impossible to use.

Same behaviour with a previous installation, version 5.1.22 on KUbuntu 17.04.
",JonPr
10851,VM config file lost after host power off,Windows,other,VirtualBox 4.1.20,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
17603,"Group of device files changes after running VirtuaBox with ""raw partitions image""",Linux,Windows,VirtualBox 5.2.8,2018-03-07T14:24:26Z,2018-03-07T14:24:26Z,"I'm using VirtualBox to run a ""real"" Windows 10 installation, using an image created according to the instructions in section 9.9.1.2 under https://www.virtualbox.org/manual/ch09.html#rawdisk. The actual partition numbers specified were 1,2,3 in my case.

This works fairly well, but there is one slight issue: The group ownership of the /dev files corresponding to the above mentioned partitions changes after I complete the VirtualBox session. The following sequence of shell commands and output should illustrate what happens:

{{{
[toralf@osl-97214 ~]$ ls -tlra /dev/sda[123]
brw-rw---- 1 root disk 8, 1 Mar  7 14:54 /dev/sda1
brw-rw---- 1 root disk 8, 3 Mar  7 14:54 /dev/sda3
brw-rw---- 1 root disk 8, 2 Mar  7 14:54 /dev/sda2
[toralf@osl-97214 ~]$ VirtualBox --startvm Win10partition
[toralf@osl-97214 ~]$ ls -tlra /dev/sda[123]
brw-rw---- 1 root root 8, 1 Mar  7 15:05 /dev/sda1
brw-rw---- 1 root root 8, 3 Mar  7 15:05 /dev/sda3
brw-rw---- 1 root root 8, 2 Mar  7 15:05 /dev/sda2
}}}
Note that the first output represents the way everything looks after a reboot.

This is a bit annoying as it means I can't give a regular users access to the Windows installation via addition to group ""disk"". Or rather, I can, but there can only be one VirtualBox session after each boot, unless someone intervenes. I guess I can add users to ""root"", to, but I'm somehow less comfortable doing that.",toralf
17605,VirtualBox does not see 255 char filename,other,Linux,VirtualBox 5.2.6,2018-03-08T04:29:47Z,2018-03-08T04:29:47Z,"The following file in a shared folder was invisible to VirtualBox, even though the filename should be short enough:

5b494649325c42726f6b6572506f7274616c42756e646c655c4d616e616765725c42726f6b6572506172746e65724167656e63794d616e6167657223676574436f6272616e6451756572794275696c646572466f7242726f6b6572506172746e65724167656e63794964405b416e6e6f745d5d5b315d.doctrinecache.data

The file cannot be viewed using ls, nor can directories containing it be removed using rm -R",shkkmo
17591,windows10 host failed to open a session for virtual machine,Windows,Windows,VirtualBox 5.2.8,2018-03-08T07:35:24Z,2018-03-08T07:35:24Z,"host:
OS name:          Microsoft Windows 10 enterprise
OS edtion:          10.0.16299  
manufactor:       Dell Inc. OptiPlex 790    x64-based PC

BIOS edtion:        Dell Inc. A18, 2013-9-24


The virtual machine 'win10'
 has terminated unexpectedly
 during startup with exit code -1073741819


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
",eiddy
17607,5.2.8 Has Issues Passing Though USB Devices Consistently,Linux,Linux,VirtualBox 5.2.8,2018-03-08T14:27:46Z,2018-03-08T14:27:46Z,"I use USB passthrough often, and after updating to the newest version, the passthrough was working maybe 1 of 10 tries. Currently, I am trying to passthrough USB to Serial cables. Downgrading to 5.2.6 has solved these issues. ",SheepyBloke
7345,Entering Fullscreen with Guest - Disrupts Synergy,other,other,VirtualBox 3.2.8,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
17609,problem with kernel,Linux,other,VirtualBox 5.2.8,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
17613,Installing Guest Additions fails on Windows Vista Guest.,Windows,Windows,VirtualBox 5.2.6,2018-03-10T16:51:46Z,2018-03-10T16:51:46Z,"I am trying to install Guest Additions onto a Windows Vista Sp1 VM, but it keeps stopping. All I try to do is install it, but it fails. My Host System is Windows 10 Fall Creators Update.",RealTTNetwork
17615,spectre v2 mitigation: lfence not serializing. switching to generic retpoline,other,other,VirtualBox 5.2.8,2018-03-11T07:41:27Z,2018-03-11T07:41:27Z,Error to install ubuntu-16.04.4-desktop-i386. See attach...,starvit
17469,VB 5.2.6 Audio issues,Windows,Windows,VirtualBox 5.2.6,2018-03-11T20:16:47Z,2018-03-11T20:16:47Z,"I think v5.2.6 messed up the audio somehow - after a while, it goes distorted & echo-y - I only use audio in the browser, not sure via WMP/etc.

Tried un-ticking ""Audio Input"" (new on Status Bar), no dice.

Even tried reverting to 5.2.2, but the GUI still looks like 5.2.6. 

I made a capture of what this audio on VB does now... http://www.screencast.com/t/98kW3skJVejU  you can hear it after 23 secs

Is this just me?",PalsyP
17618,Use all host threads to compress/decompress VM save state to speedup,all,all,VirtualBox 5.2.8,2018-03-13T05:29:32Z,2018-03-13T05:29:32Z,"Use all host threads to compress/decompress VM save state to speedup.

It would be N times faster to do the operations.",maestro
17620,VERR_VMX_NO_VMX,Windows,Linux,VirtualBox 5.2.6,2018-03-14T01:03:52Z,2018-03-14T01:03:52Z,"Hello 
I imported a virtual disk from W7 to W10.
When I run it I got the error message :
VT-x is not available (VERR_VMX_NO_VMX).
E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

VirtualBox is version 5.2",Harvey13
17024,"VHD Disks created on Disk Manager cannot be moved tho another folder after attaching and desattaching on VM, fail on reattaching without registration deletion",all,all,VirtualBox 5.1.26,2018-03-14T17:19:07Z,2018-03-14T17:19:07Z,"Recipe to bug/enhacement : 

 1. Create a .VHD (not VHDx not tested) disk on Windows Disk Manager with dinamic size.
 2. Desattach disk from system using the same Disk manager
 3. Create a Virtual Machine and choose the Existing Disk created
 4. Run the virtual machine, after error boot, stop.
 5. Remove the VHD hardDisk from VM using the Virtual Disk configuration UI
 6. On windows explorer, MOVE the created VHD Disk to another folder
 7. Try to attach the disk ON VM ou other VM using Virtual Box UI

you got the error/failure.
{{{
Cannot register the hard disk 'C:\Users\username\Desktop\FolderToMove\VirtualDisk1.vhd' {fa3d7a1c-xxxx-49ae-xxxx-63a83b45916e} because a hard disk 'C:\Users\username\Desktop\VirtualDisk1.vhd' with UUID {fa3d7a1c-xxxx-49ae-xxxx-63a83b45916e} already exists.


Código de Resultado: 
E_INVALIDARG (0x80070057)
Componente: 
VirtualBoxWrap
Interface: 
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
RC do Chamador: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}
Ok, on Virtual Box UI, you have to click on File - Virtual Media manager and remove the registred VHD disk from the list. but enhancing Virtual Box can be check the old file location not exist anymore and update to the new file location on disk without error, or ask to the user if he want to update.
",Armored
17619,tools (guest additions) and drivers don't build on SL7,Linux,Windows,VirtualBox 5.2.8,2018-03-16T02:04:08Z,2018-03-16T02:04:08Z,"Hi,
With updated kernel in SL7 (and I assume CentOS7 and RHEL7) 3.10.0-693.21.1.el7.x86_64 drivers (and tools on linux guest) no longer compile.
Looks like it is due to REPTOLINE kernel changes.

make V=1 CONFIG_MODULE_SIG= -C /lib/modules/3.10.0-693.21.1.el7.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j12 modules
arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Toolchain update recommended.. Stop.
make: *** [vboxdrv] Error 2

I can reboot in previous kernel as a workaround.

Thanks,

GZU",GZU
15403,"Clone Function Errors Out when using ""/"" Character",Windows,Windows,VirtualBox 5.0.20,2018-03-16T14:36:16Z,2018-03-16T14:36:16Z,"I am trying to create a cloned VM using the following name in the Clone Disk wizard:

Windows 7 / Visual Studio 15 Preview

This worked in prior builds of VirtualBox.  It doesn't seem to like the ""/"" in the cloned disk's name, and it errors out and won't create it.

When I change the cloned name in the wizard to ""Windows 7 - Visual Studio 15 Preview"" (i.e. replacing the ""/"" with a ""-""), then it works.

Again, I had no problem using this in my clone name in prior builds.  I am using the latest build (i.e. 5.0.20.106931)

Please advise.",Master VB Guru
17624,Files containing only zeroes gets modified after restart,Windows,Linux,VirtualBox 5.1.12,2018-03-16T16:49:37Z,2018-03-16T16:49:37Z,"Hi,

I would like to report that files containing only zeroes, gets modified after turning the virtual machine off and on.

Before the restart:
{{{
piotrek@sue:~> dd if=/dev/zero of=zeroes_1GB bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,678558 s, 1,6 GB/s
piotrek@sue:~> cmp /dev/zero zeroes_1GB
cmp: EOF on zeroes_1GB
}}}

After the restart:
{{{
piotrek@sue:~> cmp /dev/zero zeroes_1GB
/dev/zero zeroes_1GB differ: byte 647411201, line 1
}}}

The place of the first difference seems to be pretty much random. This can be illustrated by another example.

Before the restart:
{{{
piotrek@sue:~> for i in {1..10}; do dd if=/dev/zero of=zeroes_1GB_$i bs=1M count=1024; done
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,62127 s, 1,7 GB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 1,80431 s, 595 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,4662 s, 310 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,16451 s, 339 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,0117 s, 357 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,51445 s, 306 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 2,57957 s, 416 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 6,12661 s, 175 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 7,04536 s, 152 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 5,41265 s, 198 MB/s

piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
cmp: EOF on zeroes_1GB_1
cmp: EOF on zeroes_1GB_2
cmp: EOF on zeroes_1GB_3
cmp: EOF on zeroes_1GB_4
cmp: EOF on zeroes_1GB_5
cmp: EOF on zeroes_1GB_6
cmp: EOF on zeroes_1GB_7
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

After the restart:
{{{
piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
/dev/zero zeroes_1GB_1 differ: byte 794570753, line 1
/dev/zero zeroes_1GB_2 differ: byte 242036737, line 1
/dev/zero zeroes_1GB_3 differ: byte 184365057, line 1
/dev/zero zeroes_1GB_4 differ: byte 10874881, line 1
/dev/zero zeroes_1GB_5 differ: byte 460075009, line 1
/dev/zero zeroes_1GB_6 differ: byte 48693249, line 1
/dev/zero zeroes_1GB_7 differ: byte 101187585, line 1
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

When I cat one of the files, I recognize the content that is normally on my disk (for example xml requests that I store).

VirtualBox version: 5.1.12 r112440 (Qt5.6.2)

Host: Windows 7

Guest: OpenSuse 42.2

Linux kernel version: 4.4.104-18.44-default

Laptop: Dell Precision 3510

Screenshots of applicable virtual machine settings attached.

Best regards,

Piotr",PeterC
16130,VirtualBox Manager fonts+colors messed up on Linux host,Linux,all,VirtualBox 5.1.4,2018-03-16T18:35:45Z,2018-03-16T18:35:45Z,"At version 5.1-5.1.4, the UI in VirtualBox Manager seriously degraded in both text clarity and coloring.   At version 5.1-5.1.2, there were no issues but at 5.1-5.1.4 through -5.1.8, the problem is present.  All versions mentioned were tested on a fully updated CentOS 7 install.  Pictures attached of -5.1.2 vs -5.1.4
",ChrisE
12969,SSL authentication failed,other,other,VirtualBox 4.3.10,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
17321,Unhandled exception in DirectSound,Windows,Windows,VirtualBox 5.2.0,2018-03-18T04:47:20Z,2018-03-18T04:47:20Z,"Vbox crashes when resume a vm on my win 10 host. It happens 90% of time to vm which has audio enabled.

There is a problem with my windows 10. The DirectSound device has a problem(0x88890008, I don't think the meaning of the code is ERROR_NOT_ENOUGH_MEMORY). The error causes any application which uses DirectSound no sound on my win host. The other applications(such as media player, audio player) simply have no sound output. It should not cause the crash though.

A suggestion from me is to check this exception and ignore it(or report to user whichever solution applies to your coding standard). No crash is expected. I knows the issue with DirectSound so I do expect some of applications do not output sound. It is good to have an option to select device from DirectSound or WASAPI. Audio output available when switch to WASAPI in some applications. It's very strange.

If you need more info, I'll attach log files.

The partial log from VBox.log:
{{{
00:00:08.098377 DSound: Starting playback failed with ERROR_NOT_ENOUGH_MEMORY 0x88890008
00:00:08.099284 
00:00:08.099284 !!Assertion Failed!!
00:00:08.099285 Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:08.099285 Location  : F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\PDM.cpp(1006) int __cdecl pdmR3LoadExec(struct VM *,struct SSMHANDLE *,unsigned int,unsigned int)

00:00:08.099404 
00:00:08.099404 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001eb8!!!
00:00:08.099409 
00:00:08.099409 ExceptionCode=0x80000003 ExceptionFlags=0x00000000 ExceptionAddress=00007ffbafc9c395
00:00:08.099413 ExceptionInformation[0]=0000000000000000
00:00:08.099417 
00:00:08.099417 cs:rip=0033:00007ffbafc9c395
00:00:08.099421 ss:rsp=002b:000000000955d3e0 rbp=000000000955d458
00:00:08.099424 rax=0000000000000001 rcx=8aecc971d1340000 rdx=0000000000000000 rbx=00000000084fc000
00:00:08.099428 rsi=000000000955d5e0 rdi=0000000000000000 rsp=000000000955d3e0 rbp=000000000955d458
00:00:08.099432 r8 =7efefefefefefeff r9 =7efefefefefeff52 r10=0000000000000001 r11=8101010101010100
00:00:08.099436 r12=0000000000000000 r13=00000000084e0000 r14=0000000000000005 r15=00007ffbafe53550
00:00:08.099440 ds=002b es=002b fs=0053 gs=002b eflags=00000206
00:00:08.099443 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000084fc000
00:00:08.099447 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:00:08.099450    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:00:08.099453 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:00:08.099457 
00:00:08.099458 Stack 000000000955c360, dumping 0x3ca0 bytes (low=0000000009460000, high=0000000009560000)
00:00:08.099462 000000000955c360 0000: 60 c3 55 09 00 00 00 00-73 74 61 63 6b 6d 61 72 `.U.....stackmar
00:00:08.099465 000000000955c370 0010: 6b 65 72 00 fb 7f 00 00-80 00 00 00 00 00 00 01 ker.............
00:00:08.099467 000000000955c380 0020: 00 f0 59 00 00 00 00 00-40 c5 55 09 00 00 00 00 ..Y.....@.U.....
00:00:08.099468 000000000955c390 0030: 70 c6 55 09 00 00 00 00-30 fa 55 09 00 00 00 00 p.U.....0.U.....
00:00:08.099470 000000000955c3a0 0040: 01 00 00 00 00 00 00 00-70 92 12 97 fb 7f 00 00 ........p.......
00:00:08.099472 000000000955c3b0 0050: 00 00 00 00 00 00 00 00-30 fa 55 09 00 00 00 00 ........0.U.....
00:00:08.099473 000000000955c3c0 0060: 00 00 00 00 00 00 00 00-f0 94 12 e3 fb 7f 00 00 ................
00:00:08.099475 000000000955c3d0 0070: 40 c5 55 09 00 00 00 00-95 c3 c9 af fb 7f 00 00 @.U.............
00:00:08.099476 000000000955c3e0 0080: 00 00 56 09 00 00 00 00-00 00 46 09 00 00 00 00 ..V.......F.....
00:00:08.099478 000000000955c3f0 0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
00:00:08.099479 000000000955c400 00a0: 04 00 00 00 06 00 00 00-00 00 00 00 01 00 00 00 ................
00:00:08.099481 000000000955c410 00b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
00:00:08.099482 000000000955c420 00c0: 00 00 00 00 00 00 00 00-10 16 95 e6 fb 7f 00 00 ................
00:00:08.099484 000000000955c430 00d0: 40 c5 55 09 00 00 00 00-00 c8 55 09 00 00 00 00 @.U.......U.....
00:00:08.099485 000000000955c440 00e0: 38 de c5 cc fb 7f 00 00-b8 ce 55 09 00 00 00 00 8.........U.....
00:00:08.099487 000000000955c450 00f0: fe ff ff ff ff ff ff ff-04 00 00 00 00 00 00 00 ................
00:00:08.099488 000000000955c460 0100: 04 15 24 c0 ec 8a 00 00-5d 5d 06 e6 fb 7f 00 00 ..$.....]]......
00:00:08.099490 000000000955c470 0110: 48 cc 31 07 00 00 00 00-da 20 cc 60 00 00 00 00 H.1...... .`....
00:00:08.099492 000000000955c480 0120: 00 00 00 00 fb 7f 00 00-80 a7 48 03 00 00 00 00 ..........H.....
00:00:08.099493 000000000955c490 0130: b8 ce 55 09 00 00 00 00-b7 f2 97 e6 fb 7f 00 00 ..U.............
}}}",jumperstart
17588,KB4056448 cause hardening error,Windows,all,VirtualBox 5.1.34,2018-03-20T21:08:14Z,2018-03-20T21:08:14Z,"KB4056448 on Windows Server 2008 x64 SP2 cause hardening error. Same with VBox 5.2.8.
",Victor Abramoff
7009,Starting VM with Intel-VT enabled freezes system,Linux,other,VirtualBox 3.2.10,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
17273,5.1.24 regression: Windows 10 guest microphone stops working after high host CPU load,all,Windows,VirtualBox 5.1.24,2018-03-21T07:02:43Z,2018-03-21T07:02:43Z,"In VirtualBox 5.1.24, when the host CPU usage gets very high (i.e., close to 100% on all cores), then the microphone in a Windows 10 guest stops receiving sound. Note that it continues to receive no sound even after the high host CPU usage has stopped. The microphone works just fine ''before'' the high CPU load in the host. This issue does not occur in VirtualBox 5.1.22, and therefore appears to be a regression (the changelog mentions audio-related changes for better Windows 10 support, so it would make sense).

This issue occurs with both a Linux host (Ubuntu xenial) and a Windows 10 host. The guest was Windows 10 in both cases.

Steps to reproduce this issue:
1. Create an up-to-date Windows 10 guest using Intel HDA as the sound device. The host can be either Windows or Linux since the issue occurs with both. The host should be using VirtualBox 5.1.24.
2. In the guest, right-click the audio icon next to the clock and choose Recording Devices. This shows a volume meter for the microphone. Check to see that the microphone works before proceeding. Do not switch to another tab in the window during the test since that seems to reinitialize the microphone ""connection.""
3. In the host, cause a high CPU load. I did this by running 5 instances of a simple Python script that calculates Fibonacci numbers (attached).
4. After about 10-20 seconds, the volume meter either doesn't respond anymore or stays stuck on a particular volume. Killing/waiting for the Python scripts to terminate doesn't cause the volume meter to start working again. Only switching to another tab and back seems to reinitialize the microphone and fixes the issue temporarily. In 5.1.22, the volume meter never freezes.

It is also possible to test using the Voice Recorder, there I noticed that only a static noise is received after several seconds of high host CPU usage. The easiest way to reproduce, however, is to use the Recording Devices panel.

I have tested using VirtualBox 5.2.0 as well, and the same issue exists there. However, 5.1.24 is the earliest version that has this issue.",ocecaco
17630,wireshark can capture only one way packet,Windows,other,VirtualBox 5.2.8,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
17631,A critical error,Linux,Windows,VirtualBox 5.2.8,2018-03-21T15:20:42Z,2018-03-21T15:20:42Z,"VirtualBox stops with the message ""A critical error has occurred while running the virtual machine and the machine execution has been stopped."" It is random but usually within 10 minutes after the booting. The host is Arch linux and the guest is Windows 10. I attached the log.",asitstands
16361,Windows XP guest keeps crashing in recent releases,Windows,Windows,VirtualBox 5.1.12,2018-03-22T02:34:05Z,2018-03-22T02:34:05Z,"I can't tell exactly when this started, but the XP guest was very stable in versions 4.3 and 5.0 (at least the early ones). The guest keeps crashing now at random intervals, so the regression could have been introduced with version 5.1. I didn't upgrade to version 5.1 from 5.0 right away as there were audio issues initially, and when the audio was ""fixed"" the 5.1.x version was already ""broken"" for that XP client. That XP client heavily uses network adapter, but I'm not sure if that's a contributing factor or not. The host is Windows 10 version 1607.

BTW, this is not related to this issue, but I want to mention this for clarity. Bug #16221 did not concern Linux client only. I had major issues with transmit pauses (between few seconds to few minutes) on Windows 10 host. So the bug affected Windows also and also host network interface. It seems to be fixed now, so I'm not going to open a new ticket unless I notice a troubling network interface behavior, but the comment that bug #16221 was concerning Linux only (wrong) client (wrong again) troubles me that there could be things not fixed correctly. Like I said, no issue with pausing after upgrading to 5.1.12.
",Rafcio
16419,"Transmit pauses still happen, not on Linux guests but on Windows host",Windows,Windows,VirtualBox 5.1.12,2018-03-22T02:52:05Z,2018-03-22T02:52:05Z,"Despite claim that bug #16221 has been fixed, that fix was at best partial. True, the send side pauses happen far less often than in version 5.1.10, but they still happen. They happen on Windows 10 host and on an interface that has no guests bound to it. I'm going to attach log from a guest, because it may have important information about the host, but this issue really applies to the host and not a guest.
",Rafcio
17622,MacOS host Debian 9 guest hangs on big load,Mac OS X,Linux,VirtualBox 5.2.8,2018-03-22T13:04:46Z,2018-03-22T13:04:46Z,"when I start the guest with vboxmanage --headless, I kick off a build script over ssh to the guest.  eventually, the guest will become unresponsive and use 100% of one cpu.  This does not happen in the dev build (5.2.97) but does happen in the test build (>=5.2.9).  This is not reproducible if I run the same script from a gui login session on the host.

VBox.log is from a run with 5.2.9 which ends with a heartbeat flatline, after which I power the machine off.  VBox.log.2 is from a run with 5.2.97 which finished successfully followed by a power down.",jkordani-lsa2
17635,Linux guest OGL regression in 5.2.8 (LKG 5.1.30),Windows,Linux,VirtualBox 5.2.8,2018-03-23T07:20:30Z,2018-03-23T07:20:30Z,"After updating the host from 5.1.30 to 5.2.8, an Ubuntu 16.04 guest that has 3D enabled continued to work fine for a couple of hours, until I got round to updating the GAs as well. At that point, restarting the guest arrived at the desktop but immediately started consuming memory at an impressive rate, killing the X session (as you'd expect).

The leak can be traced to the Compton compositor, which when started from a terminal instead of automatically is spitting out thousands of these messages:

glx_bind_pixmap(32): Couldn't find FBConfig with requested depth.
win_paint_shadow(0x0320002d): Missing painting data. This is a bad sign.

glxinfo looks good, containing the one visual I'd expect to see:

1 GLX Visuals
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y y   8  8  8  8 .  .  0 24  8 16 16 16 16  0 0 None

1 GLXFBConfigs:
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  1 1 None

I can try bisecting to narrow down the breaking revision, but it'll take a while.
",arQon
17637,VBoxManage encryptmedium - cipher validation and documentation,all,all,VirtualBox 5.2.6,2018-03-25T11:48:45Z,2018-03-25T11:48:45Z,"Hi, 
As reported in https://forums.virtualbox.org/viewtopic.php?f=6&t=87254, i had some issues encrypting a disk.

Long story short, the encryptmedium command '''requires''' a cipher parameter, but a) does not validate it is present and b) does not present clear usage instructions (in my humble opinion).

Can I suggest that a check is done in handleEncryptMedium (VBoxManageDisk.cpp, line 1756) that if a user has provided a new password and password id, but no old password, that either the method picks a cipher by default if none is provided or reports the issue to the user. At the moment the error reported is pretty misleading.

For example:


{{{
VBoxManage encryptmedium 2f6ab46f-8db4-44d9-af1e-152c35178724 --newpasswordid test --newpassword -
Enter new password:
0%...
Progress state: VBOX_E_INVALID_OBJECT_STATE
VBoxManage.exe: error: Failed to encrypt hard disk
VBoxManage.exe: error: The password and password identifier must be empty if the output should be unencrypted
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleEncryptMedium(struct HandlerArg *)"" at line 1890 of file VBoxManageDisk.cpp

}}}


Supplying the cipher:


{{{
VBoxManage encryptmedium 2f6ab46f-8db4-44d9-af1e-152c35178724 --newpasswordid test --newpassword - --cipher AES-XTS128-PLAIN64
Enter new password:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%


}}}
",andy-g
17638,"Changing ""View -> Virtual Screen -> Use Host Screen Y"" does not respect the VM "" ""Full Screen Mode"" / ""Auto-resize guest"" setting combo",Linux,all,VirtualBox 5.2.8,2018-03-26T10:49:30Z,2018-03-26T10:49:30Z,"On an Ubuntu 16.04 multi-monitor machine that has at least 2 monitors of different resolutions. Start a VM (with guest additions installed) in full screen mode and using ""Auto-resize guest display"" on ""resolution 1"" monitor. Open the VM context menu (Host Key + Home). Select View -> Virtual Screen -> Use Host Screen and select a monitor with ""resolution 2"". The VM retains the previous resolution (resolution 1).

Expected behavior: The VM is automatically resized to the new screen resolution (resolution 2) so that it is full screen in that new resolution.

Known workaround: Use the VM context menu. Deselect ""Auto-resize guest display"". Open the VM context menu. Select ""Auto-resize guest display"".

I highly suspect that this can be reproduced on any guest/host combination and any video card driver, so I won't be attaching the log file unless necessary to debug, as it would take me some time to filter out some of the lines in it. I'm attaching the relevant lines I saw (I've included the lines triggered by me turning a monitor off and on again; the action is unrelated to this bug that I've been able to consistently hit for the past few months).",Maximilian Machedon
17641,VM console not displayed properly,other,other,VirtualBox 5.2.6,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
17364,With python3 find_machine always throws TypeError,Linux,other,VirtualBox 5.1.30,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
17645,Host modules build without dkms patch,Linux,Linux,VirtualBox 5.2.6,2018-03-28T14:10:58Z,2018-03-28T14:10:58Z,"Using VirtualBox 5.2.8 I cannot get the host modules to build. The 5.0.x modules build fine. It seems the makefile no longer functions correctly on systems without DKMS. System is LFS, GCC 5.3, QT5.10.1, kernel 4.14.29 

The errors are below. I've created a patch to fix these issues, I'm not sure if this patch is the correct way to fix it though.


{{{
=== Building 'vboxdrv' module ===
make[1]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make V= CONFIG_MODULE_SIG= -C /usr/lib/modules/4.14.29/build SUBDIRS=/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv SRCROOT=/mnt/data/pl/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv -j4 modules
make[2]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o] Error 1
make[2]: *** [Makefile:1519: _module_/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv] Error 2
make[2]: Leaving directory '/usr/lib/modules/4.14.29/build'
make[1]: *** [/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/Makefile.include.footer:101: vboxdrv] Error 2
make[1]: Leaving directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make: *** [Makefile:49: all] Error 2

}}}
",Willie
17648,Host-Only adapter failed to install on Windows 10 OS,Windows,other,VirtualBox 5.2.6,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
17639,synced folder not working  (Ubuntu 16.04 hosting debian/stretch64 9.4.0 ),Linux,Linux,VirtualBox 5.2.8,2018-03-29T08:35:23Z,2018-03-29T08:35:23Z,"When setting up a VM via '''Vagrant 2.0.1''' using '''VirtualBox 5.2.8''' and guest additions 5.2.8, touching a file in the default synced folder /vagrant does not make that file appear on the host side.

a similar test works fine for a guest of type ""ubuntu/xenial64 v20180215.0.0"".

how to reproduce: create following Vagrantfile (also attached):


{{{
Vagrant.configure(""2"") do |config|

      config.vm.box = ""debian/stretch64"" # or generic/debian9
      config.vm.box_version = ""9.4.0""
      config.ssh.insert_key = false

      config.vm.network ""private_network"", ip: ""192.168.33.10""
end
}}}

and the run following script from the hos:

{{{
#!/usr/bin/env bash

# to run from tools/vagrant/

set -x
set -e
set -u

GUEST=${1:-""default""} #$1    # name from `vagrant status`

export VERSION=5.2.8   # must be equal to the VirtualBox version!
export URL=""http://download.virtualbox.org/virtualbox/""$VERSION""/VBoxGuestAdditions_""$VERSION"".iso""

time vagrant ssh $GUEST << HERE

set -e
set -x

sudo bash

apt-get update

apt-get install -y dkms build-essential

apt-get install -y linux-headers-amd64 linux-headers-4.9.0-4-amd64

apt-get install -y module-assistant

cd /opt/

wget -c $URL -O vb.iso
mount vb.iso -o loop /mnt

cd /mnt/
sh ./VBoxLinuxAdditions.run --nox11

cd /opt
sudo rm *.iso

lsmod | grep vboxguest || echo ""*** something went wrong while attempting to install the guest additions""

HERE


}}}

touch a file in /vagrant

observe that the file does not appear in the host location.

",axd
16378,Slow GUI on MAC with external 4k display when res is scaled,Mac OS X,Windows,VirtualBox 5.1.10,2018-03-29T18:44:16Z,2018-03-29T18:44:16Z,"I'm using a Macbook Pro 15 Mid 2014 running Sierra and a Windows 7 guest.

The GUI performance (dragging a window, scrolling) is unusable slow when the external screen is running a resolution lower than it's native one.
So e.g. if the resolution is set scaled to 1920x1080 the guest is slow, if I change the resolution to its native 3840x2160 everything is super smooth.
The issue does not occur at allwhen I move the guest window to the built in screen of the Macbook.",schnesim
17661,iMac High Sierra - host kernel panic when adding load to guest,Mac OS X,Linux,VirtualBox 5.2.8,2018-04-03T09:50:43Z,2018-04-03T09:50:43Z,"Steps to reproduce: Create a simple Virtualbox with vagrant:

{{{
Vagrant.configure(""2"") do |config|
  config.vm.box = ""bento/ubuntu-16.04""
  config.ssh.forward_agent = true
  config.vm.network :private_network, ip: ""192.168.91.21""
  config.vm.provider ""virtualbox"" do |v|
    v.name = ""maschinenring test""
    v.customize [""modifyvm"", :id, ""--memory"", ""4096""]
  end
end
}}}

ssh into it and install the stressapptest

{{{
sudo apt-get install stressapptest
}}}

Runn the stressapptest with

{{{
stressapptest -s 9000 -m 8 -C 8 -W --findfiles -i 2 -M 4500
}}}

Wait for one to two hours untill the host system rects with a cernel panic. I have also attached three panic reports. For me they it looks like the vm just create some random errors in the kernel memory space. I reproduced this bug on three iMacs. All software was up to date , the iMacs do not crash in normal usage or with load testing on the host system.

I haven't seen this happening before the upgrade from Sierra to High Sierra.

Softweare Versions:
* High Sierra version: 10.13.3 (17D102)
* Virtualbox: 5.2.8
* Vagrant: 2.0.3

As the test Version of Virtualbox on https://www.virtualbox.org/wiki/Testbuilds is linking to https://www.virtualbox.org/download/testcase/VirtualBox-5.2.9-121224-OSX.dmg and this gives me a 404 I was not able to test it with the latest Test version release.

It looks like this Problem is spcific to the iMac as I was not able to reproduce it on MacBooks.

Some data from my Host OS:
{{{
Hardware-Übersicht:

  Modellname:	iMac
  Modell-Identifizierung:	iMac14,2
  Prozessortyp:	Intel Core i5
  Prozessorgeschwindigkeit:	3,2 GHz
  Anzahl der Prozessoren:	1
  Gesamtanzahl der Kerne:	4
  L2-Cache (pro Kern):	256 KB
  L3-Cache:	6 MB
  Speicher:	16 GB
  Boot-ROM-Version:	IM142.0123.B00
  SMC-Version (System):	2.15f7
  Seriennummer (System):	DGKLQ07LF8J9
  Hardware-UUID:	4328169B-16AA-518C-B249-7CDD6179774A
}}}
",codekunst
17665,"An error, log attached",other,other,VirtualBox 5.2.6,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
14846,VBoxManage Error about Machine XXX is not currently running and Machine XXX is really running in Windows Task Manager,Windows,other,VirtualBox 5.0.10,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
17669,Virtual Box not saving Default Machine Folder after closing app,Windows,Linux,VirtualBox 5.2.8,2018-04-06T03:55:38Z,2018-04-06T03:55:38Z,"The version of VBox I have is 5.2.8. I have Windows 10 as my host. I have an SSD as my C drive and a HDD as my D drive. Both internal drives. When I go to file-> Preferences->Default Machine Folder->Other and select a folder on my D drive. It changes. However, when I close the application, all the preferences revert back to the default, and the VMs that were save to the D drive are removed from the main list of VMs.",Joe5232
17627,Unconditional upscaling of display on HIDPI systems,Linux,Windows,VirtualBox 5.2.6,2018-04-06T06:41:39Z,2018-04-06T06:41:39Z,"When using VirtualBox on systems with HiDPI screens, VirtualBox unconditionally scales the VM display using the system-wide scale factor - despite a scale-factor of 100% is selected in the VM settings.

This leads to several consequences:
* Text is barely readable (glyphs simply can't be simply upscaled using whole-screen image scaling)
* The guest OS is presented a lower resolution than the host's monitor would be capable of, so even HiDPI-aware guest OSs have to run in super-ugly upscaled mode.

please see:
https://forums.virtualbox.org/viewtopic.php?f=7&t=86809
https://forums.virtualbox.org/viewtopic.php?f=7&t=87184",Linuxhippy2
16539,Virtualbox Manager Doesn't Refresh Groups,other,other,VirtualBox 5.1.14,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
17230,"When using modifyvm --groups from the command line, the Virtualbox GUI displays the new VM, but grouping does not update until you close and reopen the GUI.",Windows,all,VirtualBox 5.1.30,2018-04-06T10:57:00Z,2018-04-06T10:57:00Z,"1) Open VirtualBox Manager

3) .\VBoxManage.exe modifyvm ""vm1"" --groups ""/group1"" 

4) .\VBoxManage.exe modifyvm ""vm2"" --groups ""/group1""

5) Switch to VirtualBox Manager

Result: VirtualBox Manager doesn't show newly created group.

Restart VirtualBox Manager
Result: VirtualBox Manager shows the group and the two VMs are under it.
",oak_leaf
15159,Need bzimage feature in iPXE build for network adapter boot ROM,Mac OS X,Linux,VirtualBox 5.0.14,2018-04-08T08:17:51Z,2018-04-08T08:17:51Z,"see ticket #13628 for background. That ticket can be closed.

I cannot boot Linux (specifically CoreOS Linux) over PXE because the bzimage feature is needed to support the CoreOS cpio.gz file.

Please enable the bzimage feature in your iPXE build. Thanks.

here's my iPXE script if it matters:

{{{
kernel /assets/coreos/current/coreos_production_pxe.vmlinuz coreos.autologin coreos.config.url=http://10.3.0.154:8080/ignition?uuid=dontmatch coreos.first_boot=1
initrd /assets/coreos/current/coreos_production_pxe_image.cpio.gz
boot
}}}",MyDogHasFleas
17522,After updating software and kernel of Xubuntu 17.10.1 - critical error on restart,Windows,Linux,VirtualBox 5.2.6,2018-04-09T05:43:59Z,2018-04-09T05:43:59Z,"After a good install of Xubuntu, ran software updates, during restart got a critical error:

Installed latest 5.2.7 test build and got same error:

""A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on  https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""",wadesnj
16651,fatal error in recompiler cpu (raw mode),Windows,Windows,VirtualBox 5.1.18,2018-04-09T05:48:09Z,2018-04-09T05:48:09Z,"VirtualBox VM 5.1.18 r114002 win.amd64 (Mar 15 2017 16:16:14) 

When I try to reboot a VM that avails worked fine I got this error.
When I use a cone of the same VM all works fine.  ",Giorgio SIlvio
17672,VM crash after winXP resumes from hibernation,Windows,Windows,VirtualBox 5.2.6,2018-04-09T11:30:26Z,2018-04-09T11:30:26Z,WinXP install > hibernate it via windows's own hibernation > start VM back up > VM crashes with the 'critical error' dialogue.,Paul17041993
17667,Screen freezes above 1439p,other,other,VirtualBox 5.2.6,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
17673,Guru Meditation,Linux,all,VirtualBox 5.2.8,2018-04-10T13:37:54Z,2018-04-10T13:37:54Z,Both Ubuntu and Win7 Guest VM,maxine
17668,Keyboard does not work in Linux Build 5.2.8 r121009,Linux,Windows,VirtualBox 5.2.8,2018-04-11T09:49:23Z,2018-04-11T09:49:23Z,I am running build 5.2.8 r121009 on Centos 7. The keyboard stops working in the VM (I am unable to type anything in the VM) but continues to work just fine in the host OS.  The only way I can get the keyboard back is to reboot the guest operating system.  I just ran rum update and all patches are installed.,ErikJ
17681,mini toolbar not working. Seamless mode is never on,Windows,Windows,VirtualBox 5.2.8,2018-04-12T19:22:56Z,2018-04-12T19:22:56Z,"I was not able to open a VM win7 in Seam Less mode. 

Also, Mini Tool Bar is not visible. Even after setting in the User Interface tab in the settings.

I installed Oracle Virtual Box in Win server 2012 R2",smangu
17684,Windows Server 2016 guest freezes after a few minutes,Windows,Windows,VirtualBox 5.2.8,2018-04-13T12:22:13Z,2018-04-13T12:22:13Z,"VirtualBox Version:
5.2.8 r121009 (Qt5.6.2)

Host:
Microsoft Windows 10 Pro
64-bit
Version        : 10.0.16299
BuildNumber    : 16299

Guest:
Windows Server 2016 (64-bit)

Problem:
Guest freezes after a few minutes. Happens every time I restart the guest.

Host & guest up-to-date with updates.

Host has been rebooted and problem continues.

Log attached.",rafinnerty
17606,DeleteSnap ERROR with aRC=VBOX_E_FILE_ERROR (0x80bb0004),Linux,Windows,VirtualBox 5.2.8,2018-04-14T08:39:55Z,2018-04-14T08:39:55Z,"I am running VBox 5.2.8 under fc26. When I tried to delete the oldest snapshot from my Guest Win10x64 it showed progress 4, 3, 2 minutes,
but the all of a sudden the CPU consumption of all 4 cores went up
and the Delete Snapshot ended with a dialog message 
""Callee RC: NS_ERROR_CALL_FAILED (0x800706BE)"".
In the VBoxSVC.log I found the last message:

00:11:03.872176 DeleteSnap ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not merge the medium '/home/ksp/VB/Machines/Win10/Snapshots/{299f0e8c-9fca-4d32-be09-8e3201ee7117}.vdi' to '/home/ksp/VB/Machines/Win10/Win10-disk1.vdi' (VERR_INVALID_PARAMETER)}, preserve=true  aResultDetail=0

The problem is reproduceable
",snoopy26
17689,Screen zoom Bug,other,other,VirtualBox 5.2.6,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
17596,Critical Error occurs when trying to build Ubuntu 16.04.4,Windows,other,VirtualBox 5.2.8,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
17601,Error when loading VM,Windows,Windows,VirtualBox 5.2.6,2018-04-17T13:42:01Z,2018-04-17T13:42:01Z,"Hi
i have error on VBOX when i try to run VM 
The error is 
(rc=-5640)
Where supR3HardenedWinReSpawn What :1 VERR_SUP_VP_THREAD_NOT_ALONE(-5640) - Process Verification Failure The Process have more than one thread.

how can i fix this issue it happen to Laptop and Desktop IBM hardware VT enabled 
we try to install the new Ver and try to install old ver 
we try to go back to Windows 10 1607 
Please help 

Thank you for the help",yotama
15879,VBoxSVC.exe prevents logoff,Windows,all,VirtualBox 5.1.4,2018-04-17T20:31:24Z,2018-04-17T20:31:24Z,"If you kill a running virtualbox.exe process, then VBoxSVC.exe would stay running (as it always did) and would prevent logoff/shutdown saying that it ""Has active connections"". That was never the case at least up to VirtualBox 5.1.0. The way to reproduce:
1) start any VM
2) kill the running virtualbox.exe process 
3) try to logoff. 

I can always reproduce the problem (at least) on a Win7 x64 host.
",mskov
17685,Weird acting of vboxmanage.exe's --compact flag,Windows,Windows,VirtualBox 5.2.8,2018-04-18T15:01:10Z,2018-04-18T15:01:10Z,"When using the 
{{{
vboxmanage modifymedium <virtual VDI disk> --compact
}}}
command on a dynamic type VDI disk (previously nulled the free spaces, with [https://technet.microsoft.com/en-us/library/2009.08.utilityspotlight.aspx Sdelete] on Windows), it seems to be successful, though, the resulted image's content cannot be viewed with [https://www.7-zip.org/ 7zip] anymore, even though, VDI is a supported format of it and before running the command, it was working too. At this point, the image is mountable and the system on it is bootable, like it should.
But, after all of these, when i try to clone the image with
{{{
vboxmanage clonemedium <input file> <output file>
}}}
even though, the operation is finishes, without any problems, the system on the cloned disk, isn't bootable anymore, because the whole VM crashes, right in the middle of the boot process. Suprisingly, it can be opened with 7zip again. Cloning again and again doesn't change anything, while ''chkdsk'' cannot find any problems.
Additionally, this isn't the first case, when i have to face with this issue, so i guess, i can label it, as reproducible.",T800
17683,vboxdrv.sh: failed: modprobe vboxpci failed with linux 4.15 (centos7) -> fixed after (not in) 5.1.36,Linux,other,VirtualBox 5.1.34,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
14855,Linux: Link local IPv6 address is the only one returned for host-only interfaces,Linux,other,VirtualBox 5.0.10,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
16735,Issue with Linux guest 3D acceleration when logging in -> not likely to be fixed in near future,all,Linux,VirtualBox 5.1.22,2018-04-19T11:07:00Z,2018-04-19T11:07:00Z,"VirtualBox (5.1.22 and many earlier versions) on some Linux guests (Linux Mint Cinnamon 18.1 and several earlier versions) has a 3D acceleration issue that affects the desktop background when first logging in to the guest. This problem appears to be independent of host OS and host graphics hardware. I have reproduced the behavior on a Windows 10 host with NVIDIA graphics, and on a Linux host with Intel graphics.

The problem is that the desktop background is too bright. I've attached screenshots of the normal case and the too bright case for comparison.

The problem may be related to an animation/effect. When first logging in with Linux Mint Cinnamon, there is an effect where the desktop is zoomed  to from the center of the screen. It's hard to capture this as the effect happens pretty quickly, but it appears that the desktop background is correct until the very end of the effect, when it suddenly  brightens.

If I disable 3D acceleration in the guest settings, the desktop background does not have this problem.

If I change the desktop background after logging in, it does not have this problem.

To reproduce the problem:

1. Install Linux Mint 18.1 Cinnamon 64-bit
2. Install VirtualBox Guest Additions
3. Log in

It may be easier to see the problem with a non-default desktop background. Right click on the desktop and select Change Desktop Background. The categories Sarah and Serena have lots of pretty pictures that should show the image brightness problem. Log out and log back in to see the problem with the newly selected desktop background.",jmwestfahl
17629,Virtualbox failed on VM startup,other,Windows,VirtualBox 5.2.6,2018-04-19T15:24:15Z,2018-04-19T15:24:15Z,,Josh99
17632,aero in vBOX,Windows,Windows,VirtualBox 5.2.8,2018-04-19T15:39:30Z,2018-04-19T15:39:30Z,"in virtualbox, when i install windows 7 for exemple and install add-ons for drivers, i am not able to activate aero or other visual effects. I have also activate 3d support in the configuration of the VM.

Is it a bug?",jejelegeek
17634,3Dconnection Space Navigator doesn't work,Linux,Windows,VirtualBox 5.2.6,2018-04-19T17:49:21Z,2018-04-19T17:49:21Z,"3Dconnection fails to initialize player. I have the impression, that 3Dacceleration does not work properly.
I attach screen shots and dxdiag info file.",steamer
17640,supR3HardenedWinReSpawn VERR_INVALID_NAME on specific driver paths,Windows,all,VirtualBox 5.2.8,2018-04-19T18:09:38Z,2018-04-19T18:09:38Z,"When Hardening rejecting DLL with name like ""\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll"", an error will always show as below and none of the VM can be started.


VirtualBox - Error In supR3HardenedWinReSpawn 
Error relaunching VirtualBox VM process: 5 Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment Windows10 --startvm 1e2c22cb-276b-43b0-9049-1e50628f9490 --no-startvm-errormsgbox ""--sup-hardening-log=C:\Users\latifrons\VirtualBox VMs\Windows10\LogsWBoxHardening.log's (rc=-104) 
Please try reinstalling VirtualBox. 
where: supR3HardenedWinReSpawn what: 5 '''VERR_INVALID_NAME''' (-104) -Invalid (malformed) file/path name. 


VBoxHardening.log:
{{{
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: Error (rc=0):
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll
4530.4674: Error (rc=0):
4530.4674: supR3HardenedMonitor_LdrLoadDll: rejecting 'D:\opt\adguolvds\glhp64.dll' (D:\opt\adguolvds\glhp64.dll): rcNt=0xc0000190
4530.4674: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'D:\opt\adguolvds\glhp64.dll'
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]WinVerifyTrust]\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4788.4444: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 129076 ms, the end);
}}}


Seems that file path beginning with \Device is not supported?

How to get this dll:
Goto http://www.admon.cn and download the installer at the bottom of the page. This software is a low level ad removing tool which hooks many processes. D:\opt\adguolvds\glhp64.dll is its dll hook.

For those who comes here from Google:
Just remove this software and your VirtualBox will be fine.",latifrons
17643,Windows dosn't start 7 or 10,other,Windows,VirtualBox 5.2.6,2018-04-19T18:39:56Z,2018-04-19T18:39:56Z,"Failed to open a session for the virtual machine Win8 007.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",KHS
17646,Failure to launch windows 10,Windows,other,VirtualBox 5.2.8,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
17651,A critical error has occurred while running the virtual machine and the machine execution has been stopped,Linux,Linux,VirtualBox 5.2.6,2018-04-19T20:14:39Z,2018-04-19T20:14:39Z,"While starting new virtual box and choosing to install Ubuntu 32bit OS I received Guru Meditation box stating that ""A critical error has occurred while running the virtual machine and the machine execution has been stopped"".

Log attached.",H88
17652,Error message,Windows,other,VirtualBox 4.3.26,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
17654,Windows 98 VM won't boot,Windows,Windows,VirtualBox 5.2.8,2018-04-19T20:37:39Z,2018-04-19T20:37:39Z,"Every time that I try to install Windows 98 on a VM, the VM would not boot at all, showing two different errors: [https://imgur.com/3m4qkX5] [https://imgur.com/xQWl2HV]

The only two OSs that I know of that do this when I try to install them are Windows 98 and Windows ME, any help?",GenericUsername
17660,Critical Error on Boot,Windows,Windows,VirtualBox 5.2.8,2018-04-19T20:47:18Z,2018-04-19T20:47:18Z,"can not star my virtual machine, I recceive a critical error and cirtual machine stops.",joaocamara
17662,NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries),Windows,Windows,VirtualBox 5.2.8,2018-04-19T21:26:40Z,2018-04-19T21:26:40Z,"Unable to start the VM after system reboot

{{{

{{{
9d4.9d8: supR3HardNtChildPurify: Done after 1093 ms and 1 fixes (loop #1).
9d4.9d8: supR3HardNtEnableThreadCreation:
293c.2ac4: Log file opened: 5.2.8r121009 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03ad700
293c.2ac4: supR3HardenedVmProcessInit: uNtDllAddr=00007ff906860000 g_uNtVerCombined=0xa03ad700
293c.2ac4: ntdll.dll: timestamp 0xb79b6ddb (rc=VINF_SUCCESS)
293c.2ac4: New simple heap: #1 0000000000c00000 LB 0x400000 (for 1945600 allocation)
293c.2ac4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Program Files\Oracle\VirtualBox'
293c.2ac4: System32:  \Device\HarddiskVolume1\Windows\System32
293c.2ac4: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
293c.2ac4: KnownDllPath: C:\WINDOWS\System32
293c.2ac4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
293c.2ac4: Error opening VBoxDrvStub:  STATUS_OBJECT_NAME_NOT_FOUND
293c.2ac4: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
293c.2ac4: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
293c.2ac4: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
9d4.9d8: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
}}}

}}}
",AshokMazumder
17680,Problem Starting Windows 10 VM,Windows,Windows,VirtualBox 5.2.8,2018-04-20T07:11:18Z,2018-04-20T07:11:18Z,"Dear, I use windows 10 pro (64-bit) on my physical machine in version 1709 and need to install install vm with windows 10 pro (32-bit). But when you start vm you have an error. Code: ""Failed to open a session for Win10 virtual machine.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

""

I have already changed the settings several times, but all to no avail.
Any help is welcome.

I have a dropbox link where I am sharing the error screens.
https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0

[https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0]

Thank you!",macklains
17692,Seamless mode not available with MacOS 10.13.4 and Windows 1,Mac OS X,Windows,VirtualBox 5.2.6,2018-04-20T08:40:58Z,2018-04-20T08:40:58Z,"I have downloaded VB Version 5.2.8 r121009 (Qt5.6.3) to my MacBook Pro running Macos 10.13.4. I have downloaded a version of Windows 10 for use on VB. When I try to use seamless mode, the option is greyed out under View.  ",johnskeffington
17694,Virtualbox choppy sound issue with Genymotion on Linux,Linux,Linux,VirtualBox 5.2.10,2018-04-20T08:49:21Z,2018-04-20T08:49:21Z,"There are known sound issues with Genymotion using Virtualbox since Virtualbox version 5.1x and newer, the audio becomes kind of choppy and the virtual machines have performing issues.

In Virtualbox 5.0.26 (up to 5.0.40 in my pc) it worked perfectly. After 5.1 the issue began.

I already tried setting all the audio combinations in Virtualbox (alsa and pulse with all available audio controllers) but the issue remains.

I have done this procedure https://www.virtualbox.org/wiki/AudioDebug and will be attaching a zip file containing the VBox.log file and 3 wav files.",pemartins
17698,The virtual machine does not start.,other,other,VirtualBox 5.2.6,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
17670,clonevm --groups does not create new group,Windows,Windows,VirtualBox 5.2.8,2018-04-20T19:29:27Z,2018-04-20T19:29:27Z,"`VBoxManage clonevm VM1 --groups /NewGroup --register` successfully clones and registers `VM1` (placing it in a subdirectory `NewGroup`), but does not create the group `/NewGroup`. (`VBoxManage list groups` does not show the new group.)",BrianNixon
17703,Check for Updates menu option,Mac OS X,all,VirtualBox 5.2.10,2018-04-22T10:31:54Z,2018-04-22T10:31:54Z,"I'm getting this since 5.2.8 and I just updated to 5.2.10 but this persists.


{{{
The network operation failed with the following error: 
During network request: Wrong SSL certificate format.
}}}

Yes, I know I can download the updates from the website, but now I don't get notified of an update from within the application.",Daniel Bair
17590,Freezing every time a BSOD appears on Windows 10 guest,Mac OS X,Windows,VirtualBox 5.2.8,2018-04-22T17:25:16Z,2018-04-22T17:25:16Z,I am running the latest VirtualBox and every time a bsod appears Windows 10 it will also freeze,Neptune BSC LLC
17706,Civilzation II (2) crash at opening,Linux,Windows,VirtualBox 5.2.10,2018-04-23T09:41:58Z,2018-04-23T09:41:58Z,"When Civilization II (2) is open, the opening of session Win XP 32 fail with the following message: 

The VM session was aborted.

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : SessionMachine
Interface : ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

Otherwise, it runs OK, I mean : if I close Civ2 before closing the session, it started OK.

Interface graphique de VirtualBox
Version 5.2.10 r122088 (Qt5.6.1)

Ubuntu 16.04 LTS, 8 Go RAM

Same problem with version 5.2.8

OK with version before 5.2.8

",jeando
17707,Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10,Linux,Linux,VirtualBox 5.2.10,2018-04-23T15:25:29Z,2018-04-23T15:25:29Z,"Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10. Please see he video capture: https://drive.google.com/open?id=1aZfyoduWR4IvysM6UQdDePNEVMWjQEHE

One more detail: I was able to start the guest after upgrade to VirtualBox 5.2.10 . I installed guest additions. And the thing is not working any more... Same as last time. Something is broken with guest additions.

I tried to disable 3D acceleration. It does not help...",SamH
17644,VBoxHeadless crash,Linux,Linux,VirtualBox 5.2.8,2018-04-23T15:29:29Z,2018-04-23T15:29:29Z,"Hi everyone.

Since our VirtualBox upgrade (5.0.40 -> 5.2.8), we started seeing some VBoxHeadless process disappearing. 

Crash file attached.

We'll be glad to help you in any way we can to fix investigate the issue.
",srats
17710,"LsiLogic SCSI BIOS: int13_harddisk: function 02, error 04 ! or  int13_harddisk_ext: function 42, error 04 !",Linux,Windows,VirtualBox 5.1.22,2018-04-24T20:00:33Z,2018-04-24T20:00:33Z,"while starting winxp32/64 win764 guests(linux guests same controller work fine) using LsiLogic SCSI controller(also SAS) with ""Use Host I/O cache"" active, on debian 8 host i get very often these errors while hang

same guests same setup on win764 host work fine

win xp 32/64: VMMDev: Guest Log: BIOS: int13_harddisk: function 02, error 04 !
win764: VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 42, error 04 !

the bug doesnt appear if ""Use Host I/O cache"" is off
also no data corruption on guests

more detail: https://forums.virtualbox.org/viewtopic.php?f=7&t=87646&p=418668#p418668


'''my setup'''
vbox 5.1.22 r115126 (Qt5.3.2)
guest: Hdd controller LsiLogic SCSI
host: 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux Debian 8.10",justaquiz
17617,guru meditation,Windows,Linux,VirtualBox 5.2.6,2018-04-24T20:03:27Z,2018-04-24T20:03:27Z,"Hi,

Please am unable to install my new kali-linux-light-2018.1-i386 on windows 7 host which is giving me a guru meditation error.

Attached are details of error report.
Thank you.",swagalimo
17711,VMs no longer start from saved state,Linux,Windows,VirtualBox 5.2.10,2018-04-26T08:03:43Z,2018-04-26T08:03:43Z,"Since I've upgraded to 5.2.10r122088 (Ubuntu 16 LTS, Kernel: 4.4.0-121-generic), I'm no longer able to start my VMs from saved state:

{{{
Waiting for VM ""VM_W10"" to power on...
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
}}}

The vbox log (attached) doesn't say much.
This happens on all ~150 vms across all 10 vbox hosts I have.",LennyHers
17699,Error when starting VM after a snashot restore,other,other,VirtualBox 5.2.10,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
17690,Windows 98SE will not install,Windows,Windows,VirtualBox 5.2.8,2018-04-26T09:19:52Z,2018-04-26T09:19:52Z,"Hi, Windows 98SE won't install on my system.

Here's the sitation.

I have two Win 98SE installation packages.  One is a bootable CD, the other a non-bootable one.

With the bootable installation CD, the error appears immediately.  With the non-booable one (where setup is started with MS-DOS), the machine goes a fair way through the process..installing the system on the hard drive. The error appear when the system reboots to load WIN98 from the hard drive to complete the installation .

The error is the same in both cases. It says ""

VirtualBox.exe - Application Error

The instruction at 0x77839A95 referenced memory at 0x000C000C.  The memory could not be written.""

Installation cannot proceed from this point.

I'm using Virtual Box Version 5.2.8 r121009 (Qt5.6.2)

The machine I am using is a 32-bit Intel(R) Core TM i5 CPU running Windows 10.  

In the virtual machine, the acceleration tab in the System property is greyout out (I've checked CMOS and it looks as if the motherboard doesn't support hardware virtualisation). All extended features (PAE/NX, I/O APIC) are switched off.  RAM is set for 64MB.

Other OS's (MS-DOS, Windows 95, Windows 2000, Xp and 7) install just fine.

The Log attached is that produced from the bootable CD.",tezza
12708,USB-Dongle with Vendor-ID 0000 cannot be attached,Windows,Windows,VirtualBox 4.3.6,2018-04-26T18:51:38Z,2018-04-26T18:51:38Z,"I have to connect a USB-Licence-Dongle with Vendor-ID 0000 and Product-ID 9999 to a virtual machine (Windows 7/64 Professional).

This fails with:

{{{
Assertion failed: [mData.vendorId] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-client\USBDeviceImpl.cpp' (62) in long __cdecl OUSBDevice::init(struct IUSBDevice *).

Please contact the product vendor!.

Fehlercode:E_FAIL (0x80004005)
Komponente:OUSBDevice
Interface:IUSBDevice {f8967b0b-4483-400f-92b5-8b675d98a85b}
}}}

Having a look at this Code-Line shows
{{{
ComAssertRet(mData.vendorId, E_INVALIDARG);
}}}

It seems there is no reason for failing here besides the fact, that 0000 is not an allowed vendor-id. At least VMware Workstation 10 can handle this. Don't tell me to contact the Vendor, I have to work with what I get, and what I get has Vendor-ID 0000.
",RainerHohn
17718,Poor network latency performance / consistency,Windows,Linux,VirtualBox 5.2.10,2018-04-28T21:02:15Z,2018-04-28T21:02:15Z,"For VBox.log see the attached log from #17717.

Pinging a computer in the LAN from the host I get constant <1 ms RTT.

Pinging the same computer through from the guest I get ping times that fluctuate from >1 to 10ms. Sometimes it jumps to over 70ms, and even over 160 ms.

This is with both the host and guest essentially idle. Similarly poor performance is observed with TCP and UDP.",xnoreq
17712,ed stat  Guest VM with OS/2 does not resume from saved state,Linux,other,VirtualBox 5.2.10,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
17719,"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors",Windows,other,VirtualBox 5.2.10,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
17602,"USB passthrough problem, when flashing embedded system using PSOC Creator.",Linux,Windows,VirtualBox 5.2.6,2018-04-30T14:42:56Z,2018-04-30T14:42:56Z,"I have a problem with PSOC Creator. I'm using usb passthrough to pass cypress development board to Windows 10 on virtual machine. 

My host machine is Arch Linux. I've set up usb filter, and device is correctly recognized on guest machine, but when i try to program the board or connect debugger, PSOC Creator application hangs until i disconnect and reconnect usb cable. Then this error shows up: ""There was an error while programming the device: failed to reacquire the device.""

Trying several times, sometimes it works, sometimes it gets stuck and I need to reconnect device. But most of the time it doesn't work.

I have disabled auto suspend for this device.

If you need some extra information about the system please tell me, I will try to provide them.",morali
17717,DNS resolver does not work,Windows,Linux,VirtualBox 5.2.10,2018-04-30T14:56:28Z,2018-04-30T14:56:28Z,"Adapter in NAT mode, network ""192.168.100/24"".

Guest network adapter is called enp0s3, `ip addr` shows the interface is up with ""inet 192.168.100.15/25"".

`ip route` shows ""default via 192.168.100.2 dev enp0s3"".


Now, on the host-side the default DNS is 192.168.1.1.
The guest can ping this IP, but according to the [https://www.virtualbox.org/manual/ch09.html#changenat manual/ch09.html#changenat] the name server should be available at 192.168.100.3.

In the guest: `drill virtualbox.org @192.168.100.3` fails with ""Error: error sending query: Could not send or receive, because of network error"".
`drill virtualbox.org @192.168.1.1` (""directly"" through the DNS in the host's network) works.

I can however ping 192.168.100.3. I can also ping .2 and .4 successfully.",xnoreq
17725,Recording audio non detected on Linux,other,Linux,VirtualBox 5.2.8,2018-05-02T08:02:13Z,2018-05-02T08:02:13Z,On VirtualBox 5.2.6 - 5.2.8 and 5.2.10 recording audio is not working with system microphone or directly in-browser (using Web Audio API). ,mdameda
17727,Bug In VirtualBox in 5.2 Latest Version,Linux,Windows,VirtualBox 5.2.10,2018-05-02T22:28:33Z,2018-05-02T22:28:33Z,"Hi I am using the latest version of Virtual box. When I am trying to reverting the snapshot and starting it showing me the VM has aborted error. But if I am executing normally. without reverting the snapshot it running the VM. 

I am using CentOS7 has host machine.
and my guest machine is Windows 7
.
Kindly fix this issue.
I am also attaching the log file.",seantree
17720,State/Powered off since ??,Linux,Windows,VirtualBox 5.2.10,2018-05-03T14:17:06Z,2018-05-03T14:17:06Z,"So this is not a bug, but I guess a ""feature request"". If I copy a VM between machines, usually via rsync, I notice that the State (if the VM was off would state ""Powered off since.."") listed in a vboxmanage showvminfo is from the local machine not the machine that I copied it from. Even if I have copied all of the files from the VMs folder from another machine.

However, if I have copied the files, yet remove the VM from VirtualBox (while choosing not to remove the files) and then add the VM back, it has the correct date/time of when it was powered off on the original machine. 

So I am wondering if it got that information from the VM files that were copied, how can that information be locally updated to indicate that?",jim.rather
17731,virtual drive,Windows,Linux,VirtualBox 5.2.10,2018-05-04T14:30:07Z,2018-05-04T14:30:07Z,"the problem enhances, wen I am testing a new OS X86 / internet data mikeOS
the drive get un link’t , after 1 after a month of use


",NadirVT
17736,Windows 10 displays random BSOD with 0x00000109,Mac OS X,Windows,VirtualBox 5.2.10,2018-05-05T22:31:11Z,2018-05-05T22:31:11Z,"In Windows 10 version 1803 and 1709 it displays random BSODs with 0x00000109. the module is ntoskrnl.exe. in 5.2.8 it would also freeze the VM until you reopen the VM. 5.2.10 fixed the freezing when the BSOD appears bug.
",Neptune BSC LLC
17734,Error on starting the new machine,Windows,Linux,VirtualBox 5.2.10,2018-05-05T22:49:17Z,2018-05-05T22:49:17Z,I installed virtualbox and set all the settings and installed the extension pack. Then created my first vb with vhd and 32 bit linux os.,greybeard74
17740,"resolution lock with VB and GA  5.2.10  ubuntu 18.04 host, windows 10 pro guest, nvidia-340 driver",Linux,Windows,VirtualBox 5.2.10,2018-05-07T11:10:17Z,2018-05-07T11:10:17Z,"Tried several times to install/uninstall Guest Additions,
however there are problems with video driver, as resolution gets locked to 800x600, with flickers etc.

GA: 5.2.10, VB: 5.2.10_Ubuntu r121806

Guest: windows 10 pro

changed generic nvidia driver with specific nvidia-340.106 driver

The graphics card is an old

Quadro FX 580
  ",ft
17705,Question regarding status of upstream vboxguest module,all,Linux,VirtualBox 5.2.10,2018-05-07T15:17:26Z,2018-05-07T15:17:26Z,"Not really sure what's the best place to ask such question but I hope someone here will know the answer.

I've just tried vboxguest module shipped with 4.16 kernel in a guest running both under VirtualBox 5.2.8 (Windows) and VirtualBox 5.2.10 (Linux). Every time it ends up the same:
{{{
vbg_status_code_to_errno: Unhandled err -1
vboxguest: probe of 0000:00:04.0 failed with error -71
}}}
followed by unknown symbols from vboxsf:
{{{
vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err 0)
...
}}}
From what I've gathered so far vboxsf is not expected to work until it's mainlined as well. However my primary question is whether mainlined vboxguest is expected to work now? Or maybe not ready for prime time yet?",Jan Palus
17728,Can't mount shared folder from fstab,Mac OS X,Linux,VirtualBox 5.2.10,2018-05-07T19:01:37Z,2018-05-07T19:01:37Z,"I an Arch Linux guest on a MacOS install of VirtualBox. I mount the shared folder using the following line in my Arch installation's fstab file:

{{{archway /home/josh/archway vboxsf uid=1000,gid=1000 0 0}}}

Recently Arch began booting into emergency mode with the error:

{{{vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.}}}

This is the same issue described by a user on the Arch Linux forums:
https://bugs.archlinux.org/task/58272

Commenting out the aforementioned line in the fstab file allows the guest to boot normally, but this is not a desirable fix.
",professed
17743,Ryzen 7 X2700 - Not detecting 64bit host,Windows,all,VirtualBox 5.2.10,2018-05-08T18:45:38Z,2018-05-08T18:45:38Z,"On windows 10 Pro x64 running a Ryzen x2700 VirtualBox does not correctly detect it is running on a 64bit host, as a result only 32bit guest machines can be created. This applies to both Windows/Linux guest machines.",Timur
16696,KDE taskbar is not visible,Linux,Linux,VirtualBox 5.1.20,2018-05-08T21:46:35Z,2018-05-08T21:46:35Z,The KDE taskbar is not visible on a Linux guest. It disappears as soon as you click on the bar. Screenshots and log attached.,Panos Kavalagios
17691,Status Window for .OVA Appliance Import as .VDI shows .VMDK File Extension,other,other,VirtualBox 5.2.8,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
17749,Segmentation fault in libQt5Widgets.so when trying to open preferences,Linux,Linux,VirtualBox 5.2.0,2018-05-10T09:31:42Z,2018-05-10T09:31:42Z,"When I open Preferences (File->Preferences) a dialog window appears and then application crashes.

GUI is an package virtualbox-qt (5.1.34-dfsg-0ubuntu1.16.04.2) from Linux Mint's repository. In syslog I see messages like this:

""kernel: [ 6494.722842] VirtualBox[954]: segfault at 28000002c ip 00007fe52d0277b1 sp 00007ffd04fb9380 error 4 in libQt5Widgets.so.5.5.1[7fe52cbfe000+659000]""

I tried reinstall all it but it not helps. Application I have downloaded directly from virtualbox.org works fine. Seems, its GUI doesnt use qt.

My version Linux is Mint 18.3 x64

",akerka
17723,VirtualBox cannot catch USB devices if RemoteFX USB Redirection enabled,Windows,Linux,VirtualBox 5.2.10,2018-05-10T19:19:25Z,2018-05-10T19:19:25Z,"Host: Windows 7 SP1 Pro 64 bit. VirtualBox Version 5.2.10 r122406
Guest: Mageia Linux 6 with kernel 4.14.30
The guest additions have been installed 

I had to enable RemoteFX USB Redirection on my Windows 7 Laptop using Group Policy Editor (Enabled for Administrator and User). This feature is necessary in order to redirect ""other"" devices like Dongles etc. to a remote computer using Microsoft RDP protocol version 8.0.
But if this feature is enabled VirtualBox is not able to catch any USB device, neither a simple mass storage device like an USB stick nor a camera...
The first try to connect doesn't show anything, the second try results in an error ""USB device is busy with a previous request""

I tested this on Windows 7 SP1 Pro 64 bit host with a Mageia Linux 6 Guest and with a Knoppix Live ISO (Guest).
When disabling RemoteFX USB Redirection on the host again, everything works as expected.

How to reproduce:
1. Open Group Policy Editor (gpedit.msc) from the command line and 
2. navigate to: Computer Configuration \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop  Connection Client \  RemoteFX USB Device Redirection \ Allow RDP redirection of other supported RemoteFX USB devices from this computer
3. Set to Enabled and the rights to Administrator and User
4. Run gpupdate /force from an elevated command prompt or better do a reboot of the host as advised within the description
5. Connect a simple USB Stick to Windows host
6. Start a virtual machine within VirtualBox and try to catch this USB stick within the Guest
7. The USB device will not be connected. A second try will result in the error: ""USB device is busy with a previous request""

Related tickets: There may be some parallels to Ticket #13513 but the setting is little bit different. Host is a native computer (not a guest somewhere) and Windows 7 itself is not connected via RDP.

Expected behaviour: The setting of ""RemoteFX USB Redirection"" should not have any impact on the USB driver used within VirtualBox

--> maybe it would be helpful to ad this setting to ""USB basics and troubleshooting"" within the VirtualBox forum as it took me hours to narrow this bug down
",spuch
17752,fatal error in recompiler cpu: Trying to execute code with memory type,Linux,Windows,VirtualBox 5.1.34,2018-05-10T19:54:32Z,2018-05-10T19:54:32Z,"hello the community.
I have a crash with:
Gest windows 7 - Host linux kubuntu 17-10 - virtualbox 5.1.34
I tested this with XP and it's OK. Only windows 7 crash. Windows 7 boot with boot without error.
Please help me to resolve this problem.
Thank you for your help and excuse me for my poor english...
regards",GB74
17751,"""A critical error has occured while running the virtual machine and the machine execution has been stopped.""",Windows,Linux,VirtualBox 5.2.12,2018-05-10T20:03:42Z,2018-05-10T20:03:42Z,"Hello.
I just installed VirtualBox on Windows 8.1, in order to install Kali Linux, however I keep getting the warning ""A critical error has occured while running the virtual machine and the machine execution has been stopped."".
What should I do?
Thank you in advance.",Nyctivoe
17753,Failed to open a session for the virtual machine,other,other,VirtualBox 5.2.12,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
17757,writev() blocks over vboxsf on Linux 4.16 guest,other,other,VirtualBox 5.2.12,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
17758,Windows 10 guest crashes when Settings are opened,Linux,Windows,VirtualBox 5.2.10,2018-05-11T10:00:20Z,2018-05-11T10:00:20Z,A windows 10 guest is crashing when the Settings are selected from the start menu. The host is Fedora 28 64-bit.,Panos Kavalagios
17755,[guest additions] mouse laggy after unlock screen,Windows,Linux,VirtualBox 5.2.10,2018-05-11T15:33:08Z,2018-05-11T15:33:08Z,"After locking screen and unlocking it in guest system the mouse pointer becomes slow and laggy. I have enabled guest additions.

guest xubuntu 64bit 18.4 running on xfce4,
host win 10

",mar10
13635,Reduce dialog overload on extension pack upgrade,Linux,all,VirtualBox 4.3.20,2018-05-13T11:41:00Z,2018-05-13T11:41:00Z,"Hi,

When you've updated VirtualBox to a newer version and you had the extension pack installed before, you'll get presented with the notification that a newer extension pack is available when you start VirtualBox again after the VirtualBox update.

It's nice to get the reminder and the option to upgrade the extension pack, but the amount of subsequent dialogs the user is presented with is just madness. 7 in total just to perform the upgrade.

These are the action the user has to perform at the moment:
1. Press ""Download"" button on the upgrade available dialog
2. Press ""Download"" button on the download dialog
3. Press ""Install"" button on the download complete dialog
4. Press ""Upgrade"" button on a confirmation dialog
5. Press ""I agree"" button on the license dialog
6. Supply password on the system's admin rights needed dialog
7. Press ""OK"" button on the installed confirmation dialog

This makes a handy feature just tedious instead of being helpful and efficient.

I understand that there are different situations in which a user can install the extension pack and that there are different dialogs needed in those situations, but those dialogs should only be displayed when they actually apply.

The first 4 actions can, and IMHO should, be combined into just 1 when we are dealing the the update available notification. There's a new upgrade -> download and install.
Having to agree to the license could even be considered redundant on upgrade. You already agreed on it on the first install. If the license hasn't changed there's no point in displaying it again.

Would it be possible and desired to reduce the extension pack upgrade step to 3 or 4 steps instead of the current 7?
The current situation only makes it tedious and leaves a messy impression.",Forage
17761,Virtual machine stuck at initializing (windows logo),Windows,Windows,VirtualBox 5.2.12,2018-05-14T06:01:19Z,2018-05-14T06:01:19Z,"-Create a windows 10 32 bits virtual machine
-2 GB of hard disk + ISO Image (SATA)
-128 MB graphics
-4 GB of dedicated TAM",Leviathan
17760,"can not start the vm and get the error ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""",Windows,Linux,VirtualBox 5.2.12,2018-05-14T14:15:32Z,2018-05-14T14:15:32Z,"Hi,

I created a centos 7.4 virtual machine. After creating, it works ok under virtual box. However it randomly can not start and the log complains below error: 
VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

Attached please find the log file and the screenshot image. 

Thanks,
Shifeng",shzhang
17729,Current GuestAdditions have problems with resolutions on CentOS 6.2 guests,Windows,Linux,VirtualBox 5.2.8,2018-05-15T15:51:35Z,2018-05-15T15:51:35Z,"Hi. Plse see this discussion for additional details, log files and a duplication procedure: https://forums.virtualbox.org/viewtopic.php?f=6&t=87685&start=15

In short, on a CentOS 6.2 guest I am stuck with only three display resolution settings if I use GuestAdditions >= 5.1.0. GAs version 5.0.40 work fine and offer a multitude of resolutions and although I have not tried it, I suspect that using 5.0.40 I could also use xrandr to add additional modes. Moderator socratis has reproduced the issue also in 5.2.10. I have not tried this on other hosts than my Win7 laptop. socratis is on a MAC if I remember correctly, I doubt the host matters here. For me personally the priority could be set to minor since there is a workaround, on the other hand, many users may  depend on other GAs-stuff fixed in newer versions.",MatsBoekelund
13308,GUI Always Start Headless,all,all,VirtualBox 4.3.14,2018-05-15T16:47:04Z,2018-05-15T16:47:04Z,"I would appreciate an option in the GUI to always start a VM in headless mode (without holding down shift key which I forget to do about 99% of the time).

Thanks.",jeremywj
17767,hdaR3SaveStream compile bug in non VBOX_STRICT,all,all,VirtualBox 5.2.12,2018-05-16T14:16:02Z,2018-05-16T14:16:02Z,"{{{
VirtualBox/src/VBox/Devices/Audio/DevHDA.cpp: In function ‘int hdaR3SaveStream(PPDMDEVINS, PSSMHANDLE, PHDASTREAM)’:
VirtualBox/src/VBox/Devices/Audio/DevHDA.cpp:3506:30: error: ‘pThis’ was not declared in this scope
               HDA_STREAM_REG(pThis, LPIB, pStream->u8SD), HDA_STREAM_REG(pThis, CBL, pStream->u8SD), HDA_STREAM_REG(pThis, LVI, pStream->u8SD)));
}}}



In this function pThis will be defined only when VBOX_STRICT defined:
{{{
/* Saved state workers and callbacks. */

static int hdaR3SaveStream(PPDMDEVINS pDevIns, PSSMHANDLE pSSM, PHDASTREAM pStream)
{
    RT_NOREF(pDevIns);
#ifdef VBOX_STRICT
    PHDASTATE pThis = PDMINS_2_DATA(pDevIns, PHDASTATE);
#endif

...

#ifdef VBOX_STRICT /* Sanity checks. */
    uint64_t u64BaseDMA = RT_MAKE_U64(HDA_STREAM_REG(pThis, BDPL, pStream->u8SD),
                                      HDA_STREAM_REG(pThis, BDPU, pStream->u8SD));
    uint16_t u16LVI     = HDA_STREAM_REG(pThis, LVI, pStream->u8SD);
    uint32_t u32CBL     = HDA_STREAM_REG(pThis, CBL, pStream->u8SD);

    Assert(u64BaseDMA == pStream->u64BDLBase);
    Assert(u16LVI     == pStream->u16LVI);
    Assert(u32CBL     == pStream->u32CBL);
#endif

...

#ifdef VBOX_STRICT /* Sanity checks. */
    PHDABDLE pBDLE = &pStream->State.BDLE;
    if (u64BaseDMA)
    {
        Assert(pStream->State.uCurBDLE <= u16LVI + 1);

        HDABDLE curBDLE;
        rc = hdaR3BDLEFetch(pThis, &curBDLE, u64BaseDMA, pStream->State.uCurBDLE);
        AssertRC(rc);

        Assert(curBDLE.Desc.u32BufSize == pBDLE->Desc.u32BufSize);
        Assert(curBDLE.Desc.u64BufAdr  == pBDLE->Desc.u64BufAdr);
        Assert(curBDLE.Desc.fFlags     == pBDLE->Desc.fFlags);
    }
    else
    {
        Assert(pBDLE->Desc.u64BufAdr  == 0);
        Assert(pBDLE->Desc.u32BufSize == 0);
    }
#endif

...

    Log2Func((""[SD%RU8] LPIB=%RU32, CBL=%RU32, LVI=%RU32\n"",
              pStream->u8SD,
              HDA_STREAM_REG(pThis, LPIB, pStream->u8SD), HDA_STREAM_REG(pThis, CBL, pStream->u8SD), HDA_STREAM_REG(pThis, LVI, pStream->u8SD)));

#ifdef LOG_ENABLED
    hdaR3BDLEDumpAll(pThis, pStream->u64BDLBase, pStream->u16LVI + 1);
#endif

    return rc;
}
}}}
",gim
17768,hdaR3WalClkSet compile bug in non VBOX_STRICT,all,all,VirtualBox 5.2.12,2018-05-16T14:34:14Z,2018-05-16T14:34:14Z,"
{{{
VirtualBox/src/VBox/Devices/Audio/DevHDACommon.cpp: In function ‘bool hdaR3WalClkSet(PHDASTATE, uint64_t, bool)’:
VirtualBox/src/VBox/Devices/Audio/DevHDACommon.cpp:183:15: error: ‘u64WalClkCur’ was not declared in this scope
               u64WalClkCur, u64WalClk, fForce,

}}}


u64WalClkCur will be defined only when VBOX_STRICT defined
{{{
bool hdaR3WalClkSet(PHDASTATE pThis, uint64_t u64WalClk, bool fForce)
{
...

# ifdef VBOX_STRICT
    const uint64_t u64WalClkCur       = ASMAtomicReadU64(&pThis->u64WalClk);
# endif

...
    const uint64_t u64WalClkNew = hdaWalClkGetCurrent(pThis);

    Log3Func((""Cur: %RU64, New: %RU64 (force %RTbool) -> %RU64 %s\n"",
              u64WalClkCur, u64WalClk, fForce,
              u64WalClkNew, u64WalClkNew == u64WalClk ? ""[OK]"" : ""[DELAYED]""));

    return (u64WalClkNew == u64WalClk);
}
}}}
",gim
17773,Distorted sound Host: Windows 10 Guest: Ubuntu 18.04,Windows,Linux,VirtualBox 5.2.12,2018-05-17T14:03:17Z,2018-05-17T14:03:17Z,"Distorted sound after about 8 minutes, restores to normal by another minute.[[BR]][[BR]]
Repeat this issue indefinitely with random times.
[[BR]][[BR]]
Recorded audio debug wav files as in [https://www.virtualbox.org/wiki/AudioDebug]
and found no file with distortion. (So they are not attached)

It should be the first case in Diagnosis table
||= Playback in running VM =||= Dumped file(s) =||= Diagnosis =||
|| Distorted || OK || '''Host driver (backend) problem''' ||
[[BR]]
Same issue with a previous configuration Host: Windows 7 Guest: Ubuntu 16.04 with many versions of VirtualBox.
Only VirtualBox 5.2.7 solved partially as instead of distorted sound it goes mute. 

Thanks.[[BR]]

P.S. Classified as major priority as this issue is a long time pending.[[BR]]

P.P.S. by the way debug wav files are not compatible with windows media player",Han Fastolfe
17732,64bit guest on 32bit host,Windows,Windows,VirtualBox 5.2.10,2018-05-18T08:43:06Z,2018-05-18T08:43:06Z,"After downloading the newest 64bit version of Windows 10 (April update), i faced with a serious problem, when i tried to create a fresh install on a new virtual disk (12GB dynamic VDI). Most likely, the cause of the issue, that my host (it has a C2D P8400 CPU) is running the 32bit version of Windows 7. Altought, it'd be not a problem at all, as long, as VT-x is turned on, in both the BIOS and the VM and the CPU has 64bit support. Nonetheless, installing this OS is currently impossible, because guest is always going to hang, shortly after starting (captured wbem file is attached).
Anyways, i'm pretty sure, VT-x is enabled system-wide, because when i disable it in BIOS, i get the expected error message:

{{{
Failed to open a session for the virtual machine VM_00002.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Also i'm sure, the bug is hiding somewhere in Virtualbox's Windows 10 support, since right after this, i successfully managed to install a 64bit Windows 7 system on exactly the same guest and host (screenshot is attached of this).
",T800
17780,CentOS 7.5 Guest Additions not installing,Windows,Linux,VirtualBox 5.1.38,2018-05-21T16:00:44Z,2018-05-21T16:00:44Z,"I had a CentOS 7.4 VM and then I updated it to the latest kernel so that it is now running CentOS 7.5 and my screen won't resize and I can't copy/paste between my Windows Host and my VM. Originally I was on VirtualBox 5.1.32 and I tried reinstalling the guest additions, this didn't work and I couldn't work out what was causing the issue from the VBoxAdd-install.log.

I saw a fix in the latest version of VirtualBox but this didn't fix the issue even after installing the latest guest additions.

Rough Steps to Reproduce:

 - Upgrade CentOS 7.4 VM to CentOS 7.5
 - Install latest guest additions",oletts
14718,guest window resizes to a very minimal size (vertically),Linux,all,VirtualBox 5.0.6,2018-05-21T17:57:37Z,2018-05-21T17:57:37Z,"This started when I upgraded from 4.3.30 to 5.0.6 using RPMs for openSUSE 13.2 as provided by virtualbox.org.
Every guest resize event leads to the host window to become very small (height is very minimal; width also but not that much). I can provide a screenshot when required.
This happens for every guest system (Windows, Linux etc). For Windows where the default is that the guest resizes to adapt to the host window it's worst because every resize of the host window results in a resize event within the guest which immediately makes the host window small again. I have to disable the the automatic guest resizing to be able to do anything.",Wolfgang Rosenauer
17714,Ciritical Error during Windows Update (possibly VERR_PAGE_TABLE_NOT_PRESENT related),Linux,Windows,VirtualBox 5.2.10,2018-05-22T06:23:03Z,2018-05-22T06:23:03Z,"Host: Ubuntu 16.04.4 LTS (Xenial)
Guest: Windows 7 Professional 32-bit
VirtualBox: Version 5.2.10 r122088 (Qt5.6.1) (Installed from the VirtualBox repository) with Windows Guest Additions v5.0.36

I am getting a 'Critical Error' when booting my Win 7 OS and it occurs when attempting to install a Windows update during boot time. I have narrowed it down to the '2018-04 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4093118)' update (I say narrow but there's 137MB worth of update in that so a fair amount going on).

I raised the issue [https://forums.virtualbox.org/viewtopic.php?f=7&t=87736 in the forum] and it was suggested that the presence of 'VERR_PAGE_TABLE_NOT_PRESENT' in the logfile (attached) *might* be a clue.
",MJN
17577,Unusable window system on Ubuntu 1204 guest using 5.2.8 or GA 5.2.7,Windows,Linux,VirtualBox 5.2.8,2018-05-22T09:56:11Z,2018-05-22T09:56:11Z,"After installing 5.2.8 (and also after testing GA 5.2.7 against 5.2.6 to address 3D acceleration bug - Ticket #17463, Ticket #17569) my Ubuntu 1204 system became unusable. E.g. when I try to run terminal I cannot see the console window and cannot switch to it with Alt-Tab or any other means. The Alt-Tab icons look different as well. The problem went away on 5.2.6 after moving back to GA 5.2.6 but I really need a fix for the 3D issue so that is not where I want to be.",tomasth
17782,"Virtualbox for Windows 5.2.12: ""Failed to aquire the Virtualbox COM object""",Windows,Windows,VirtualBox 5.2.12,2018-05-22T20:35:51Z,2018-05-22T20:35:51Z,"Hi,
I have been having this issue for multiple weeks, and I was hoping someone could help.
I understand that many people have had this issue, and I have tried almost every fix, repair, and etc. that I have the power to do.
",MaxMega12
17784,Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).,other,other,VirtualBox 5.2.12,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
17785,Start Kali Linux,Windows,Linux,VirtualBox 5.2.12,2018-05-23T16:25:01Z,2018-05-23T16:25:01Z,I installed kali linux virtual machine and the error occurs during startup,LucaFaggiani
17763,UI Fails to start - 5.2.12 - qtcore 5.9.4,other,other,VirtualBox 5.2.12,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
17747,Confilct between Virtualbox 5.12.10 r122088 and compiz ubuntu 18.04,Linux,Windows,VirtualBox 5.2.10,2018-05-24T12:53:34Z,2018-05-24T12:53:34Z,"Hello !
 This ticket for report a bug between Oracle Virtual box 5.12.10 on Ubuntu 18.04 and Compiz tools !
When Ubuntu 18.04 is set on compiz management, the task bar setting in top of the screen in a virtual machine doesn't appear ! When setting in Marco appearance, it's work fine and task bar appear in the right position in the top of the screen ! For information, this trouble doesn't appear in VMware machines with compiz setting !
Here details of the configuration :
Ubuntu 18.04
Virtual Box 5.12.10 r122088
Virtual machine with Windows XP SP3 !",Papusone
16347,Full screen mode broken on MacOS hosts with Guest additions 5.1.4 and later,Mac OS X,Linux,VirtualBox 5.1.12,2018-05-25T19:57:59Z,2018-05-25T19:57:59Z,"I am running VBOX on MacOS. I am tracking both MacOS versions (currently on macOS Sierra (10.12.2), and VirtualBox versions (currently on 5.1.12). I use all my VMs (Linux) in full screen mode

Last september I had upgraded VBOX to 5.1.4. I then upgraded the guest editions to 5.1.4 as well As a result, full screen mode stopped working: the VMs no longer occupied the whole screen, but only part of it. Luckily I was able to go back to the previous guest additions (5.0.20) and got full screen back to working as usual.

Today I upgraded VBOX to 5.1.12 and tried again upgrading the guest additions to 5.1.12. Same effect: full screen broken the same way (full screen no longer occupies the entire screen). Again, downgraded guest additions to 5.0.20.

What seems to happen is that the guest additions somehow no longer automatically match the resolution of the VM screen to the resolution of the host display (1280x800).

I also see differences in the View menu. 
With guest additions 5.0.20, the View menu is like this:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked.
- Scaled Mode (Host+L) is unchecked

With guest additions 5.1.4 and later:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked but greyed out
- Scaled Mode (Host+L) is unchecked but greyed out


",agodfrin
17754,Installation without disabling secureboot,Linux,other,VirtualBox 5.2.12,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
10428,Need middle button simulation on MacBook Pro,Mac OS X,Solaris,VirtualBox 4.1.12,2018-05-27T17:42:27Z,2018-05-27T17:42:27Z,The native X11 that comes with OS X will treat the combination of the option key + left trackpad click as a middle button press and command key + trackpad click as a right button press event. It would be nice if Virtual Box supported this as this would make my life a bit easier when working in a Solaris 11 guest session on my MacBook Pro OS X host.,Will Fiveash
17697,all new VirtualBox session hang when Skype for Business start a conference/meeting call,Windows,Windows,VirtualBox 5.2.10,2018-05-28T07:23:16Z,2018-05-28T07:23:16Z,all new VirtualBox (after interface changed) session hang when Skype for Business start a conference/meeting call.,blaine
17789,Virtual computer failed to start,Windows,Linux,VirtualBox 5.2.8,2018-05-30T14:21:39Z,2018-05-30T14:21:39Z,,zhangwei01
17792,vboxmanage guestcontrol run --exe doesn't display any output,Linux,Linux,VirtualBox 5.2.12,2018-05-31T09:19:03Z,2018-05-31T09:19:03Z,"Hello,

== 
The vboxmanage guestcontrol run/start doesn't show any information on the standard output. ==
 
I have tried with the --wait-stdout and/or --wait-stderr but nothing change.
Sessions seems to be created but I even obtain acore dumped while watching operation.
Here my details :

What I do :
{{{
[fredmj@Lagrange ~]$ vboxmanage --nologo guestcontrol ""CENTOS7.TMP"" --verbose run --exe ""/bin/ls"" --username fredmj --password dummyPass --wait-stdout

}}}


{{{
[fredmj@Lagrange ~]$ vboxmanage guestcontrol CENTOS7.TMP watch
Session ID=1 ""[12121] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=2 ""[12154] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=3 ""[12186] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" registered
Process ""/bin/ls"" registered
Process PID=15554 ""/bin/ls"" changed status to [started]
Process PID=15554 ""/bin/ls"" changed status to [successfully terminated]
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Erreur de segmentation (core dumped)

}}}


My configuration:

{{{
[fredmj@Lagrange ~]$ cat /etc/redhat-release 
CentOS Linux release 7.5.1804 (Core)
}}}
 


{{{
[fredmj@Lagrange ~]$ vboxmanage --version
5.2.12r122591
}}}



{{{
[fredmj@Lagrange ~]$ vboxmanage showvminfo CENTOS7.TMP
Name:            CENTOS7.TMP
Groups:          /BuildingBlocksLab
Guest OS:        Red Hat (64-bit)
UUID:            f415d3d3-cc35-488a-82d4-a9dbfd529cca
Config file:     /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vbox
Snapshot folder: /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Snapshots
Log folder:      /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Logs
Hardware UUID:   f415d3d3-cc35-488a-82d4-a9dbfd529cca
Memory size:     1024MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:           running (since 2018-05-30T23:32:13.661000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vdi (UUID: 92b5d7ab-8cac-41cf-ae63-98c5d51205c9)
SATA (1, 0): /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: 3cc8e4fb-e56e-4eb6-a214-d1be7ca16272)
NIC 1:           MAC: 080027A06520, Attachment: Bridged Interface 'wlp2s0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: AC97, Codec: AD1980)
Audio playback:  disabled
Audio capture: enabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
Session name:    headless
Video mode:      800x600x32 at 0,0 enabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Capturing:          not active
Capture audio:      not active
Capture screens:    0
Capture file:       /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:    ac_enabled=false

Guest:

Configured memory balloon size:      0 MB
OS type:                             Linux26_64
Additions run level:                 2
Additions version:                   5.2.12 r122591


Guest Facilities:

Facility ""VirtualBox Base Driver"": active/running (last update: 2018/05/30 21:35:01 UTC)
Facility ""VirtualBox System Service"": active/running (last update: 2018/05/30 21:35:03 UTC)
Facility ""Seamless Mode"": not active (last update: 2018/05/30 21:35:01 UTC)
Facility ""Graphics Mode"": not active (last update: 2018/05/30 21:35:01 UTC)

}}}

",Frédéric MARIE-JOSEPH
17794,Host Network Manager GUI for macOS lack of refresh,Mac OS X,other,VirtualBox 5.2.12,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
17797,Error in ipl windows xp,Linux,other,VirtualBox 5.1.34,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
17798,help info of autostart wrong => Fixed in SVN,other,other,VirtualBox 5.2.12,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
17800,virtualbox gui is not that accessible,Linux,all,VirtualBox 5.2.12,2018-06-04T11:14:25Z,2018-06-04T11:14:25Z,"hey there,
the virtualbox gui is not that accessible compared to what it used to be
i'm unable to read the name of the virtual machines when arrowing up and down the list of machines, or locate the place to create snapshotts for the sillected vm, when I am in the settings dylog box, the catagorys such as mutherbord, audio, basic shared folders is not announsed any more.
host arch linux running the latest version of virtualbox.
I use orca the screen reader to navigate around.
I realize that you are really bizy  people I would be greatful if you could look in to this.
stepps to reproduce,
1.
launch orca the screen reader.
2.
launch virtualbox.
3 try navigateing up and down the list of vms and settings dylog boxes.
what should happen,
all catagorys should be announced when navigateing using arrow keys, the names of vms should be spoken currently this is not the case,
i'm no longer able to create snappshots.
thanks",maj
17200,Disable COW for disk images on btrfs,other,other,VirtualBox 5.1.30,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
16355,Mini ToolBar on different monitor than virtual machine window,Linux,Windows,VirtualBox 5.1.12,2018-06-05T13:27:28Z,2018-06-05T13:27:28Z,"Host: Linux Mint 18.1 Mate, 2 monitors
Guest: Windows 10

Mini ToolBar shows up on different (primary) monitor, whereas virtual machine window starts in its remembered position on secondary monitor. When the machine is minimized and maximized Mini ToolBar moves to correct screen. This is not remembered after virtual machine is stopped and started.",morvael
17023,"Win 10 Surface Book and multiple Host screens, cannot start on Screen 3",Windows,other,VirtualBox 5.1.26,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
17074,Windows 10 Pro Host/Win7Pro Guest Mouse/Cursor Issue,Windows,Windows,VirtualBox 5.1.26,2018-06-07T06:50:41Z,2018-06-07T06:50:41Z,"I have recently replaced my Host System with a Surfacebook running Win 10 Pro with I7 duo core with 16 gig ram and 1TB SSD. VB is version 5.1.26. Guests are windows 7 Pro and Win 10 Pro. Guest in full screen mode. USB mouse and built in Mouse Pad are being used.

VB works however; when in the guest opening Notepad++ and any other apps with text boxes the mouse cursor disappears, I need to change the Input mouse setting to see the cursor. This is annoying since I've uninstalled VB extensions and reinstalled and it requires the Host hot key to exit the VM Guest.

This only occurs when guest is used on secondary monitors. When on the SurfaceBook main screen no issue.  External monitor(s) are attached via the Docking station, and I've tested with the built Display port and had same results there as well.

But after many tries and testing I found if I increase the Guest screen Fonts to 150% the problem no longer exists. This is not really best solution.",Mudoch
17793,Change in VM settings not taken into account with snapshots,Windows,Windows,VirtualBox 5.2.12,2018-06-08T14:58:51Z,2018-06-08T14:58:51Z,"On a UEFI Windows 10 x64 virtual machine with multiple snapshot, change in the configuration are not taken into account when booting, even if the virtual machine file show that these change are saved.

For example, I tried to change the boot order to ''Network'' on that virtual machine, but it still tries to boot to ''DVD'' and then ''Hard Drive'' (if I press F12 and go to '''Boot Manager''', ''Network'' is not even there and the order doesn't correspond to the one saved.

Virtual Box version 5.2.12 r122591 running on Windows 10 Pro x64 v1709",Michael Tremblay
17810,vm fails to stop or reset,other,Windows,VirtualBox 5.2.8,2018-06-10T16:51:34Z,2018-06-10T16:51:34Z,"Running vbox virtualbox-ose-5.2.8_1 on freebst 11.1 host.
VM hangs on attempt to reset or to poweroff it",Dian
17813,Page fusion causes VERR_PGM_PHYS_INVALID_PAGE_ID,other,Windows,VirtualBox 5.2.12,2018-06-11T16:28:26Z,2018-06-11T16:28:26Z,"VMs with Windows guests have pagefusion on and Guest Additions 5.2.12 installed.

VBox.log of one of them (Windows 2012 R2 64-bit) shows:

08:37:31.516883 AssertLogRel /home/vbox/vbox-5.2.12/src/VBox/VMM/VMMR3/PGMShared
Page.cpp(237) VBOXSTRICTRC pgmR3SharedModuleRegRendezvous(PVM, PVMCPU, void*): R
T_SUCCESS_NP(rc)
08:37:31.516935 VERR_PGM_PHYS_INVALID_PAGE_ID (-1637) - Trying to free a page wi
th an invalid Page ID.

The VM is effectively useless after this and can only be recovered by power-cycling the VM.",Stephen Rondeau
17806,Error 0x80070057 usb,Windows,Windows,VirtualBox 5.2.12,2018-06-11T16:30:57Z,2018-06-11T16:30:57Z,"Hola, cree una maquina virtual w10, el SO donde esta instalado virtualbox es w7. y no logro utilizar un pendrive, probé varios.",woltsp
17807,VM fails to start,Windows,Linux,VirtualBox 5.2.12,2018-06-11T16:32:38Z,2018-06-11T16:32:38Z,"Running Version 5.1.14 r112924 (Qt5.6.2) on Windows 7 64bit, suddenly it fails to start with below error:

The virtual machine 'Oracle Linux 6.7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Virtual_Machines\Oracle Linux 6.7\Logs\VBoxHardening.log'.
",Abdelj
17814,Seamless mode & sleep,Windows,Windows,VirtualBox 5.1.30,2018-06-11T18:37:51Z,2018-06-11T18:37:51Z,"After wake up in seamless mode, the taskbar is not shown (guest OS is XP).
In addition when I tried to log off the saved state of VM was lost. It is better to do hibernate of shut down when host OS is logging off or shutting down.

",386sx
14302,"Keyboard Caps lock, Num lock and Scroll Lock problems with Virtualbox 5.0",Windows,Windows,VirtualBox 5.0.0,2018-06-12T00:40:49Z,2018-06-12T00:40:49Z,"Steps to reproduce the problem:
1) With no virtual machines running, activate Caps lock and/or Num lock and/or Scroll lock.
2) Start a virtual machines from saved state.
3) When I reduce the window of the virtual machine or I close it (by saving the state or by shut down the system) the state of Caps lock, Num lock and Scroll lock are deactivated.

Host: Windows 7 x64
Guest tested: Windows Xp SP3: Windows 7 x64 SP1; Windows 8.1 x64",bmn
17621,USB and LAN error when re-connecting notebook to dock,Windows,other,VirtualBox 5.2.8,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
17804,Win10 and 7 host OracleEnterpriseLinux 6.7 guest addition clipboard and window resize does not work,Windows,Linux,VirtualBox 5.2.12,2018-06-12T09:39:34Z,2018-06-12T09:39:34Z,"HostOS: Win10 Pro, Win7Pro
GuestOS: Oracle Linux 6.7
uname -a: Linux demo.us.oracle.com 3.8.13-118.4.2.el6uek.x86_64 #2 SMP
VBox: Version 5.2.12 r122591 (Qt5.6.2)
Guest Addition: 5.2.12 successfully installed under OS user 'oracle' and root authentication was given during the install.
Mouse integration works, I can move the mouse outside of VBox window without pressing Right-CTRL.
Devices/Shared Clipboard is set to bi-directional
Devices/Drag and drop disabled
Devices/Shared Folder is set and auto-mount is working, files can be read and written.

What does not work is:
1. Clipboard between host and guest do not work in any direction regardless what is the Devices/Shared Clipboard setting
2. VBox window resizing worked before guest addition was installed, after that it stopped working only 800x600 screen size is available by default. Within Linux manual reset of the resolution works but the information gets lost and reset to 800x600 after reboot.
3. when switching Linux OS user from 'oracle' to 'root' the screen resizing starts working and the clipboard bidirectional as well.
4. When switching back to 'oracle' it is not working

The clipboard integration makes it as a major incident.

",Laszlo
17790,Screen resolution limited after Linux guest OS update,Mac OS X,Linux,VirtualBox 5.2.12,2018-06-12T09:39:42Z,2018-06-12T09:39:42Z,"After updating the OS of an Oracle Linux guest OS, the screen resolution becomes limited to 640x480, 800x600 and 1024x768 and cannot be set to a higher resolution. 

Related forum thread:
https://forums.virtualbox.org/viewtopic.php?f=3&t=88072

To reproduce the result: 
1) download the Oracle DB Developer VM image
2) import and start the Linux guest VM
3) review the screen resolution options 
4) set screen resolution to a high resolution option (e.g. 1600x1200)
5) shutdown VM
6) update the guest OS using the standard OS update process
7) restart the VM
8) review screen resolution options on the Linux guest
9) display options should show only 640x480, 800x600 and 1024x768

",elewis33
17815,Failed to save settings - Empty or null bridged interface name is not valid.,Windows,Linux,VirtualBox 5.2.12,2018-06-12T13:15:56Z,2018-06-12T13:15:56Z,"After I disable the bridged network (because is no adapter for some reason, so can't use it) and try to save settings, I get the following error:

Failed to save settings

Empty or null bridged interface name is not valid.


Result Code: 
E_FAIL (0x80004005)
Component: 
NetworkAdapterWrap
Interface: 
INetworkAdapter {e925c2aa-4fe4-aaf6-91c5-e9b8ea4151ee}

",szx
17816,Can't connect to on Linux guest from Windows via host-only network,Windows,Linux,VirtualBox 5.2.12,2018-06-12T17:32:08Z,2018-06-12T17:32:08Z,"I have an Ubuntu VM that runs a MySQL server among other things. I connect to it from different host systems - macOS, Windows.

For some unknown reason the host system can no longer connect to the server (mysql says ""connection refused""). I'm connecting through a host-only network via 192.168.56.101. I can ping this IP address without problems.

I have no idea why it stopped working. I did not change any configuration. Deleting and re-creating the host-only network doesn't solve the issue. 

I'm not a networking expert, I have no knowledge of debugging this sort of issues. I was hoping that you could fix this bug.",szx
17802,After upgrade to Fedora 28 mouse not working in VM,Linux,Windows,VirtualBox 5.2.12,2018-06-13T20:48:28Z,2018-06-13T20:48:28Z,"Hello all.

After i performed the upgrade to Fedora 28 in my notebook Dell Inspiron 15 Series 5000 (I15-5557-A40), at the Microsoft Windows 10 VM the mouse not working ( i can see the mouse, but the right/left click not working any more). To resolve this, i need to pause the VM and start it again, and by this the mouse click working fine after this process.

I also tried to reinstall the VirtualBox (versions 5.2.12, 5.2.11, 5.2.10), but not worked also.

Please help me in this to resolve",Cautella
17819,"Support for specifying bridged interface name by guid, not only name",other,Windows,VirtualBox 5.2.12,2018-06-13T20:56:05Z,2018-06-13T20:56:05Z,"Some network interface drivers on Windows has ability to display interface options and description in various languages based on current user set locales. This could lead to situations where VM template created for such shared system could not be started when target user uses different locale (""Network interface named XXX could not be found"") as the interface description, used by VirtualBox for bridged network, is different - altough the real interface stays the same.
As the interface guid (using eg. vboxmanage list bridgedifs) stays the same, it would be benefitial to use this instead of interface description in VM configuration.",M@…
17817,Add support for OpenBSD in guest additions,other,BSD,VirtualBox 5.2.12,2018-06-13T23:31:26Z,2018-06-13T23:31:26Z,"https://www.virtualbox.org/manual/ch03.html#guestossupport states no OpenBSD support in guest additions //yet//. OpenBSD support in VirtualBox has come a long way over the years and it's an attractive option for development/testing and virtual desktop use. Is guest addition support feasible?

Would be great to see support for some pressing usability enhancements, e.g. resizing guest display support, shared folders, shared clipboard, time synchronization. ",crater
16328,"Clone with Everything, Linked Clone errors",Mac OS X,all,VirtualBox 5.1.12,2018-06-13T23:41:35Z,2018-06-13T23:41:35Z,"* Select a VM (""Test"") and choose ""Clone"". The VM did not have snapshots, but it doesn't really matter.
* Switch to ""Expert Mode"", if not already selected.
* The defaults are: Full Clone (for CloneType), Current machine state (for Snapshots).
* Select in that order: Everything (for Snapshots), Linked Clone (for CloneType). Press ""Clone"":
{{{
Failed to clone the virtual machine Test.

Linked clone can only be created for a single machine state.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: SnapshotMachine
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}
* We return to the Clone dialog. If you Cancel out, you see the results:
 * No ""Test Clone"" VM has been created.
 * A snapshot for the ""Test"" VM has been created: ""Linked Base for Test and Test Clone"".",Socratis
15908,XBoxAutostart service starts and completes before NFS and iSCSI start,Linux,Linux,VirtualBox 5.1.4,2018-06-14T04:19:55Z,2018-06-14T04:19:55Z,"I have a fresh install of Ubuntu 16.04 Server and VirtualBox 5.1. I have an Ubuntu guest created on an NFS mount with the storage attached to an iSCSI LUN on my NAS. Starting and stopping it manually works fine, but it does not start at boot.

Manually starting the guest works via any one of these commands:
* VBoxHeadless --startvm ""Ubuntu Server""
* sudo service vboxautostart-service restart
* vboxautostart --start --config /etc/vbox/autostart.cfg

The syslog shows the vboxautostart-service starting and completing before the NFS mounting and the iSCSI initiator daemon is ready.  With the help of the forum moderator Perryg, I added 'sleep 10' to the top of the /etc/default/virtualbox and the VM started and working as expected.

The vbox services with my install are started via S02vboxdrv and S03vboxautostart-service in the appropriate rc.d folders.

syslog
{{{
Sep  7 15:12:03 MyHost systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
Sep  7 15:12:03 MyHost vboxdrv.sh[2811]: vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost kernel: [   14.354340] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Sep  7 15:12:03 MyHost kernel: [   14.359014] vboxdrv: Found 4 processor cores
...
Sep  7 15:12:03 MyHost kernel: [   14.378254] vboxdrv: TSC mode is Invariant, tentative frequency 1596300487 Hz
Sep  7 15:12:03 MyHost kernel: [   14.378258] vboxdrv: Successfully loaded version 5.1.4 (interface 0x00260000)
...
Sep  7 15:12:04 MyHost kernel: [   14.582075] VBoxNetFlt: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.583189] VBoxNetAdp: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.584579] VBoxPciLinuxInit
Sep  7 15:12:04 MyHost vboxdrv.sh: VirtualBox services started.
Sep  7 15:12:04 MyHost kernel: [   14.586318] vboxpci: IOMMU not found (not registered)
Sep  7 15:12:04 MyHost systemd[1]: Started VirtualBox Linux kernel module.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxautostart-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxballoonctrl-service.service...
Sep  7 15:12:04 MyHost vboxautostart-service.sh[3023]: vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxweb-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Started vboxballoonctrl-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxweb-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxautostart-service.service.
...
Sep  7 15:12:10 MyHost systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Sep  7 15:12:10 MyHost systemd[1]: Starting OpenBSD Secure Shell server...
Sep  7 15:12:10 MyHost systemd[1]: Started /etc/rc.local Compatibility.
Sep  7 15:12:10 MyHost iscsid: iSCSI logger with pid=3172 started!
Sep  7 15:12:10 MyHost systemd[1]: Started iSCSI initiator daemon (iscsid).
Sep  7 15:12:10 MyHost systemd[1]: Starting Login to default iSCSI targets...
Sep  7 15:12:10 MyHost iscsiadm[3180]: iscsiadm: No records found
Sep  7 15:12:10 MyHost systemd[1]: Started OpenBSD Secure Shell server.
Sep  7 15:12:10 MyHost systemd[1]: Started Login to default iSCSI targets.
Sep  7 15:12:10 MyHost systemd[1]: Reached target Remote File Systems (Pre).
Sep  7 15:12:10 MyHost systemd[1]: Mounting /mnt/nfs/myNas...
Sep  7 15:12:10 MyHost kernel: [   21.235486] FS-Cache: Loaded
Sep  7 15:12:10 MyHost kernel: [   21.247575] FS-Cache: Netfs 'nfs' registered for caching
Sep  7 15:12:10 MyHost kernel: [   21.258497] NFS: Registering the id_resolver key type
Sep  7 15:12:10 MyHost kernel: [   21.258505] Key type id_resolver registered
Sep  7 15:12:10 MyHost kernel: [   21.258506] Key type id_legacy registered
Sep  7 15:12:10 MyHost systemd[1]: Mounted /mnt/nfs/myNas.
}}}

Forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=79617",Brian Duguid
17570,vboxmanage cli - Segmentation fault,Linux,Linux,VirtualBox 5.2.6,2018-06-14T12:42:52Z,2018-06-14T12:42:52Z,"I'm running CentOS 7 on a dedicated server. And was running a single Linux Guest deployed via VBOX and Vbox-web. Since last year mid Oct I have not been able to use this setup any more. All commands result in segmentation fault.

I have updated Vbox , OS, all packages, rebooted the server. All without any result.
{{{
root@dedi ~ # cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core) 
}}}
{{{
root@dedi ~ # rpm -qa | grep VirtualBox
VirtualBox-5.2-5.2.6_120293_el7-1.x86_64
}}}

dmesg results in the below being logged
{{{
[746521.108089] vboxwebsrv[20856]: segfault at c ip 00007fac8d5fdb65 sp 00007ffe6872ea78 error 6 in libcrypto.so.1.0.2k[7fac8d58d000+234000]
[747035.697541] VBoxManage[23082]: segfault at 9 ip 00007fe6f8fb7b65 sp 00007ffed3c10ec8 error 6 in libcrypto.so.1.0.2k[7fe6f8f47000+234000]
[747292.271164] VBoxManage[24094]: segfault at 9 ip 00007f7eb7d20b65 sp 00007ffe5c8262b8 error 6 in libcrypto.so.1.0.2k[7f7eb7cb0000+234000]
[747329.919469] vboxwebsrv[24204]: segfault at c ip 00007f90a5595b65 sp 00007fff96e61938 error 6 in libcrypto.so.1.0.2k[7f90a5525000+234000]
}}}",ahurjui
17818,Guru Meditation 1155 (VING_EM_TRIPLE_FAULT),Windows,other,VirtualBox 5.2.12,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
17825,Restoring VM goes from running to Guru Mediation state,Windows,Windows,VirtualBox 5.1.30,2018-06-16T14:06:50Z,2018-06-16T14:06:50Z,"I have created saved state and restoring it. It works fine on Windows 10 Host OS where as in Windows 8.1 Host it gives below error [[BR]]
''aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} '''aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}''', preserve=false''

before this line log shows that guest is getting some fatal condition [[BR]]
''00:00:37.170678 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc000001d P2=0xfffff803462b21ec P3=0xffff9e0187736768 P4=0xffff9e0187735f90
''[[BR]]

System configuration is:[[BR]]

Guest OS: Windows 10 64 bit[[BR]]

Host OS: Windows 8 64 bit[[BR]]


I have attached log for more information. Not sure what is the reason of failure.",Jeet15
17781,"""Failed to save settings"" for registered VM if HostNetwork or NATnetwork is not available in new host => Fixed in SVN",all,all,VirtualBox 5.2.12,2018-06-18T14:27:43Z,2018-06-18T14:27:43Z,"'''__Problem__'''
* Create a VM, no need for HD, CD or anything like that. See the ""TestDOS.vbox"" that's attached.
* Select the NATnetwork option, with a NATnetwork that exists on Host A, for example ""VBoxNATnetwork"", that I have only created on Host A.
* Disable the adapter.

* Take that .vbox file to another host, Host B, where the ""VBoxNATnetwork"" does '''not''' exist.
* Register the VM, run the VM. No problems.
* Open the settings. Press OK to close the settings.
Error message:
> ''Failed to save the VM settings.''
> 
> ''__Empty of null NAT network name is not valid.__''
> 
> ''Result Code: E_FAIL (0x80004005)''[[br]]
> ''Component: NetworkAdapterWrap''[[br]]
> ''Interface: INetworkAdapter {e925c2aa-4fe4-aaf6-91c5-e9b8ea4151ee}''
[[br]]
Followed by:
> ''The machine settings were changed while you were editing them. You currently have unsaved setting changes.''
>
> ''Would you like to reload the changed settings or to keep your own changes?''
[[br]]

'''__Workaround__'''

Enable the network adapter in question, change the ""Attached to"" option to something else, preferably ""Not attached"". Disable the network adapter again, if you want to.
[[br]]

'''__Solution__'''

Force the non-enabled adapters to become ""Not attached"".",Socratis
17534,Importing a multi-CPU/VT-x VM on a non-VTx host makes changing VM settings impossible  => Fixed in SVN,all,all,VirtualBox 5.2.6,2018-06-18T14:27:54Z,2018-06-18T14:27:54Z,"Assume you have a VM with multiple CPUs, or a VM that has VT-x enabled in the settings. Copy VM folder (.vbox, VDIs, Snapshots and Logs) to a host that does not have VT-x available. Add the VM. Since there's no VT-x on the host:
* The System » Acceleration settings become disabled.
* The CPU count drops to 1. In the GUI.
Problem is that neither the ""hwvirtex"" changes, nor the number of CPUs. End result? Can't start the VM (<VERR_VMX_NO_VMX>), can't change the VM settings, at least via the GUI (hence the ""GUI"" component selected).

The logic needs to change so that things do not become disabled, they become ""flagged"". I would go to the path/logic followed by the ""2D acceleration"" setting in a non-Windows VM.
1. Flag it (yellow triangle, warning/error notification)
2. ''(Optional)'' Force-modify the settings to what's acceptable/allowed, just like 2D is disabled (even when selected) in a non-Windows VM. 1 CPU, no VT-x.
I'm leaving open the second option, just like the amount of CPU/RAM settings are flagged, but not force-modified. If someone wants to be greeted by an error, fine by me.

No VM logs (for obvious reasons) but if you want a .vbox, please say so.",Socratis
16454,VERR_ACCESS_DENIED when using raw disk on Windows 10 host,Windows,Linux,VirtualBox 5.1.14,2018-06-19T09:32:03Z,2018-06-19T09:32:03Z,"I created an Ubuntu 16.10 x86_64 VM and attach added raw disk to it which is an internal SATA hard drive (not the system one). I followed the procedure described in the manual for Windows hosts and successfully created a raw disk with VBoxManage.

However, during installation of the gust Ubuntu system as soon as it attempted to modify the disk the VM was paused with the following error:

The I/O cache encountered an error while updating data in medium ""ahci-0-0"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Error ID: 
BLKCACHE_IOERR
Severity: 
Non-Fatal Error

despite that I was running VirtualBox as admin.
",szx
17471,"regression 5.2.2 -> 5.2.4, USB stopped work with TomTom Go",Linux,Windows,VirtualBox 5.2.4,2018-06-20T23:01:34Z,2018-06-20T23:01:34Z,"Moving from 5.2.2 to 5.2.4 TomTom My Drive software is unable to connect to my TomTom.
TomTom Go software seems to see the TomTom device but it can't connect to it anymore.

Virtualbox was working fine with 5.2.2.

USB is configured as 2.0. Host is Debian running kernel 4.14.7, guest is Windows 7.

Still not working with 5.2.6.



thanks",IvanSB
17799,USB Webcams are Not Working in Windows Guest (w. Extension Pack & Guest Additions),Windows,Windows,VirtualBox 5.2.8,2018-06-21T05:24:35Z,2018-06-21T05:24:35Z,"I am trying to get my webcam, Microsoft LifeCam (USB), to work in a Windows 7 (64 bit) Guest on Windows 7 (64 bit) Host.


The camera works fine in the Host using two different applications:
1. Microsoft LifeCam software
2. Portable Webcam (http://sourceforge.net/p/portablewebcam)

I am currently using VirtualBox 5.2.8 w. Guest Edition and Extension Pack. I select the WebCam under devices (and not in USB devices). The camera is recognized in Device manager. However, the Camera is not working;
1. Microsoft LifeCam software: ""No Camera found""
2. Portable Webcam: Camera light turns on then off. I just get a white screen

I can use the camera in the Host, using either application, even when virtual box is running with the camera attached to the Guest (Should that work? I had expected the Guest to take ownership of the camera).

I also tried Logitech C270 Webcam and I have the same problem. 

Please help, I have spent several months on this using different guests and versions of VirtualBox.
Thank you in advance!

p.s. 
1. The cameras works fine in VMware virtual machines and Windows 7 Host/Guests.
2. I posted this previously in the forum but got no response (https://forums.virtualbox.org/viewtopic.php?f=6&t=87569)",ppan
17834,PGM: Failed to procure handy pages; rc=VERR_GMM_HIT_VM_ACCOUNT_LIMIT,Windows,Windows,VirtualBox 5.2.2,2018-06-22T04:36:45Z,2018-06-22T04:36:45Z,"Bug reproduce:
- Set guest memory balloon to maximum value
- Power on VM and make it crash, Ex: driver failure
- Windows guest will be restarted after crash
- Error will be occurred while VM restart

Error cause:
- When guest crashed, ballooned pages are not cleanup

Suggest fix:
- Cleanup all ballooned pages when VM state change to RESETTING",AnhNN
17832,Vt-x is not available.  What tool will identify the problem?,Windows,other,VirtualBox 5.2.12,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
16396,Guest Freeze: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [firefox:3744],Mac OS X,Linux,VirtualBox 5.1.12,2018-06-22T15:31:03Z,2018-06-22T15:31:03Z,"I searched a lot for a similar problem and could not find one.
The problem occurs with both 5.1.12 or 5.0.30 and also earlier versions for a few months now.
I tried ubuntu 16.04 64bit VM and also Debian machine 32 bit with jessie and now stretch.
I recompiled the kernel, 4.8.15 same thing.
I am using docker to run the firefox so that is an important information.
The freeze occurs after a while using the firefox. I don't have an idea why it happens or in what situation. Sometimes it can run for a long time, sometimes not. It is sporadic.",Tzahi
17836,ERROR TO OPEN VB,Windows,Windows,VirtualBox 5.2.12,2018-06-22T20:51:18Z,2018-06-22T20:51:18Z,"I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB:

""Error in supR3HardNtChildWaitFor
Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles).
Plea try reinstallin VirtualBox.
where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)""

So I tried to reinstal but it's the same error.

What's happening???",alaz
17820,VERR_INTERRUPTED errors from guest control service during ptrace debugging,Linux,Linux,VirtualBox 5.1.38,2018-06-25T09:14:07Z,2018-06-25T09:14:07Z,"VBoxService should cleanly handle interrupted syscalls. When receiving an error with errno=EINTR, the syscall should be retried.

We have a service that performs an anti-virus scan of running processes, which attaches to processes as a debugger to inspect memory to check for injected malware. Every time a scan is performed an error is reported by the Guest control service:

{{{
May 31 09:36:37 rhel74 kernel: 186:39:59.180297 control  Error: Getting host message failed with VERR_INTERRUPTED
}}}


After a few scans (17?) the Guest control service aborts:

{{{
May 31 09:41:10 rhel74 kernel: 186:44:32.414453 control  Error: Getting host message failed with VERR_INTERRUPTED
May 31 09:41:10 rhel74 kernel: 186:44:32.414591 control  Error: Too many failed attempts in a row to get next message, bailing out
May 31 09:41:10 rhel74 kernel: 186:44:32.414636 control  Guest control service stopped
May 31 09:41:10 rhel74 kernel: 186:44:32.414667 control  Guest control worker returned with rc=VERR_INTERRUPTED
}}}

The error can be reproduced with gdb by attaching to the running VBoxService process:


{{{
[root@rhel69 pair]# tail -f /var/log/messages &
[1] 4714
[root@rhel69 pair]# May 31 13:44:00 rhel69 kernel: 00:00:00.000152 main     Log opened 2018-05-31T12:44:00.767090000Z
May 31 13:44:00 rhel69 kernel: 00:00:00.000266 main     OS Product: Linux
May 31 13:44:00 rhel69 kernel: 00:00:00.000307 main     OS Release: 2.6.32-696.3.2.el6.x86_64
May 31 13:44:00 rhel69 kernel: 00:00:00.000355 main     OS Version: #1 SMP Wed Jun 7 11:51:39 EDT 2017
May 31 13:44:00 rhel69 kernel: 00:00:00.000388 main     Executable: /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
May 31 13:44:00 rhel69 kernel: 00:00:00.000390 main     Process ID: 4698
May 31 13:44:00 rhel69 kernel: 00:00:00.000391 main     Package type: LINUX_64BITS_GENERIC
May 31 13:44:00 rhel69 kernel: 00:00:00.001758 main     5.1.38 r122592 started. Verbose level = 0
May 31 13:44:00 rhel69 vboxadd-service.sh: VirtualBox Guest Addition service started.
May 31 13:44:01 rhel69 kernel: 00:02:52.579824 main     Ended.

[root@rhel69 pair]# gdb -p `pidof VBoxService` -batch -ex quit
Missing separate debuginfo for /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
[New LWP 4710]
[New LWP 4709]
[New LWP 4708]
[New LWP 4707]
[New LWP 4706]
[New LWP 4705]
[New LWP 4704]
[Thread debugging using libthread_db enabled]
0x0000003f5ca0f585 in sigwait () from /lib64/libpthread.so.0
A debugging session is active.

	Inferior 1 [process 4703] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
May 31 13:45:55 rhel69 kernel: 00:01:54.476487 control  Error: Getting host message failed with VERR_INTERRUPTED
[root@rhel69 pair]# 
[root@rhel69 pair]# kill %1
[root@rhel69 pair]# 
[1]+  Terminated              tail -f /var/log/messages
[root@rhel69 pair]# 
}}}

It looks like VBoxService is failing to handle interrupted system calls correctly.


From http://man7.org/linux/man-pages/man2/ptrace.2.html :
(Programs which do not expect such ""stray"" EINTR errors may behave in an unintended way upon an strace(1) attach.)


I presume VBoxService is waiting on a syscall, such as poll() and receives an EINTR error when the process is interrupted. The error is recoverable, and the call should just be retried in this case, but it looks like the error is being treated as a problem and isn't silently/cleanly recovered.


VBox guest attributes:


{{{

￼
Runtime attributes


Screen Resolution

800x600x32 @0,0
VM Uptime

1d 03:48:55
Clipboard Mode

Disabled
Drag and Drop Mode

Disabled
VT-x/AMD-V

Active
Nested Paging

Active
Unrestricted Execution

Active
Paravirtualization Interface

KVM
Guest Additions

5.1.38 r122592
Guest OS Type

Linux 2.6 / 3.x / 4.x (64-bit)
Remote Desktop Server Port

Not Available
}}}

",Tim@…
15765,[Linux] [KDE5] Windows Guest scales incorrectly on High DPI host with Guest Additions,Linux,Windows,VirtualBox 5.1.2,2018-06-25T15:42:01Z,2018-06-25T15:42:01Z,"Hello,

I have a Dell XPS 15 9530 with a high DPI (3200x1800) screen. I'm running Arch Linux with KDE Plasma 5, which has support for high resolution displays.

With the migration of VirtualBox to QT 5, the GUI scales very well and is a pleasure to use on my high DPI screen. Except for one problem: when I install the VirtualBox Guest Additions on a Windows 8.1 or 10 host, the VM only fills up a quarter of the screen; the rest is black. The strange thing is that this only happens when the Guest Additions are installed on the Windows Guest. Without them, it runs fine.

Input is also registered wrong: I have to move in the ""black area"" in order to be able to click on something on the Windows desktop. 

Another strange thing is that when pausing the VM, VirtualBox scales the VM perfectly fine, but when resuming, it's gone.

I attached screenshots to make things a little bit more clear, together with the VBox.log file from a Windows 8.1 guest.",JonasDeMoor
17843,The display with Screen Factor larger than 100% produces offsets in the display of some graphics,Linux,Windows,VirtualBox 5.2.12,2018-06-28T21:23:34Z,2018-06-28T21:23:34Z,"When using screen factor of 100% the display of the graphics present in an Excel sheet are OK. (see screenshot 100% attached)
When using screen factor of say 125% the graphics in this Excel sheet are partially offsetted ! (see screenshot 125% attached)

Is this an issue with the way these graphics are handled by Excel, meaning that in such case there is nothing that can be done about that, or rather is there anything the virtual machine can do to fix this ?

Details : screenshots taken in fullscreen 1920x1080, on Excel 2003 running in XP, on Ubuntu 18.04 host.  ",Lucien
17741,Raw-mode is unavailable courtesy of Hyper-V,Windows,other,VirtualBox 5.2.10,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
17845,"Managing groups of VMs will not be synchronized in filesystem, VM stay on their location",Windows,all,VirtualBox 5.2.12,2018-07-01T10:02:34Z,2018-07-01T10:02:34Z,"Managing of groups (new group, move VM to new group, add VM to group) will not synchronized in filesystem.

Steps: 
- VBox running without any Virtual Machines (VM)
- Create on VM: ""vm1""
- ""Group"" this ""vm1"": Group ""New Group"" will created, also in Filesystem (FS) a directory ""New Group"" is created, directroy ""vm1"" is now inside ""New Group""
- Rename ""New Group"" to ""grp1"": ""vm1"" is displayed in group ""grp1"", in FS directory is renamed to ""grp1"", ""vm1"" is inside ""grp1"": OK 
- Clone ""vm1"" to ""vm2"": ""vm2"" is displayed outside ""grp1"", directory ""vm2"" is created outside ""grp1"" (parent directory)
- ""Group"" ""vm2"" to a second group ""grp2"" as before: Group ""grp2"" is displayed with ""vm2"" inside. But no directory for group ""grp2"" is created, ""vm2"" is still outside.
- Move ""vm2"" to ""grp1"" (drag an drop): ""grp2"" is no longer displayed, ""grp1"" has members ""vm1"", ""vm2"". In FS ""vm2"" is still outside of ""grp1""
- ""Add new VM"" in group ""grp1"": Displayed in ""grp1"", but in FS it is created outside of ""grp1"".

Summary:
Only one group will be managed in filesystem. Display and Filesystem are not synchornized.
The first VM of the group will be moved inside group directory.
No further group directories will be created.
Other vms (by clone, by add, by move) will stay outside (in the parent-directory).
",TKinVBOX
17846,vboxmanage does not work with ubuntu 18.04,Mac OS X,Linux,VirtualBox 5.2.12,2018-07-01T20:26:04Z,2018-07-01T20:26:04Z,"wes:tmp zmansour$ vboxmanage guestcontrol ubu1804 --verbose --username juser --password jpassword run --exe /bin/ls --timeout 3000 --wait-stdout --wait-stderr
Creating guest session as user 'juser'...
Waiting for guest session to start...
Successfully started guest session (ID 1)
Starting guest process (within 3000ms)
Process '/bin/ls' (PID 1738) started
VBoxManage: error: Reading from process ""/bin/ls"" (PID 1738) failed: VERR_TIMEOUT.
VBoxManage: error: Reading from process ""/bin/ls"" (PID 1738) failed: VERR_TIMEOUT.
Process monitor loop quit with vrc=VERR_GENERAL_FAILURE
Closing guest session ...
wes:tmp zmansour$ ",zmansour
17848,editing of shared folders is very annoying - folder name changes arbitrarily,all,all,VirtualBox 5.2.12,2018-07-02T15:45:14Z,2018-07-02T15:45:14Z,"When editing an existing share, changing the folder path changes the folder name

so... If I have a folder z:\codebase\dev mapped to a 'code' share, all is well... but when I update the folder to z:\codebase\prod, the name changes to 'prod'

This copy-down from (leaf name from folder path) to folder name should only happen if the folder name is empty - otherwise... leave it alone!!",tim61
17756,Guest (windows 10) cannot detect microphone (playback works fine),Linux,Windows,VirtualBox 5.2.12,2018-07-03T07:40:51Z,2018-07-03T07:40:51Z,"Host: Debian stretch

Guest: Windows 10

Audio Controller: Intel HD Audio 

Virtualbox version:5.2.12 r122591

Playback works fine, but windows 10 (guest) cannot detect microphone (there is no microphone in the devices list) (microphone in host works perfectly)",MeatShooter
17854,Can't upgrade extension pack as normal user from GUI on Ubuntu 18.04 (due to missing gksu?),Linux,all,VirtualBox 5.2.14,2018-07-03T19:33:43Z,2018-07-03T19:33:43Z,"On Ubuntu 18.04, it is no longer possible to upgrade the extension pack from the VirtualBox manager GUI when running as an unprivileged user.  This used to work under Ubuntu 17.10 and earlier versions (you were prompted for a password to gain root privileges).

After accepting the license, I get the following error message:

{{{

Failed to install the Extension Pack /home/nate/.config/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.14.vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

}}}

I think the root cause of the error is that Ubuntu 18.04 no longer includes gksu (see [https://bugs.launchpad.net/ubuntu/+source/umit/+bug/1740618 Ubuntu bug 1740618]).  Looking at the source to VBoxExtPackHelperApp, it tries to execute gksu to elevate privileges.  If that doesn't work it tries to run pkexec, which here doesn't work either, I guess because it doesn't have a tty to talk to.  The ""Error creating textual authentication agent"" message is apparently from pkexec.

A workaround is to install the extension pack manually with VBoxManage, or to run the VirtualBox GUI as root under sudo (but this is a bit annoying for me, because root has a different ~/.config/VirtualBox which points to a bunch of stale VMs and produces more warnings).  However, from the symptoms above, it would be hard for a new user to know to try this.

VirtualBox 5.2.14 installed from http://download.virtualbox.org/virtualbox/debian.  The package file is virtualbox-5.2_5.2.14-123301~Ubuntu~bionic_amd64.deb.

(Not sure which component applies to the GUI manager, or if this is ""installer"".  Have marked as component GUI for now but feel free to change.)",Nate Eldredge
17856,Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1) (Hardening Issue while starting an image),Windows,Linux,VirtualBox 5.2.6,2018-07-04T18:34:01Z,2018-07-04T18:34:01Z,"I am running Oracle Virtual Box 5.2.6 r120293 (Qt5.6.2) and I am trying to launch CentOS 7 gust image and see the error ""Error (rc=-5640)""

I am on Windows 10 [1709] 64-bit OS and x64-bit Processor.

I have tried most of the options that are mentioned in the link:

https://forums.virtualbox.org/viewtopic.php?f=25&t=82106

Can anyone help us if this is a bug or something that is coming from my environment.

I have attached the VBoXHardening.log",SarmaK
17857,- Buscador,Mac OS X,Linux,VirtualBox 5.2.14,2018-07-09T09:00:19Z,2018-07-09T09:00:19Z,"Hello!

We have 3 MacBook Pro's, all running High Sierra (10.13.5), all with the same error after opening a Buscador ISO 2-3 times. The first time it works fine, it seems to run into the boot error sometime later.

I saw an error in a few of the logs: vmmdev guest log bios cd rom boot failure code 0004

Not sure if this is a generic error, or something more telling. Any help would be appreciated, thanks!

",Kujo
17860,USB 3.1 support,Windows,Linux,VirtualBox 5.2.14,2018-07-09T12:17:10Z,2018-07-09T12:17:10Z,"The usb camera that reports as USB 3.1 will not be recognized by Virtual box while every things working fine with USB 3.0 camera. 

I am not sure if anyone has already reported this. But I did not find any thing in google search.

I am using latest version of Virtual box 5.xx and USB extension package.  ",T1000
11031,'Bridged Networking' on host vlan interfaces does not work,Linux,other,VirtualBox 4.2.0,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
17862,Full screen view out of sync,Linux,Windows,VirtualBox 5.2.14,2018-07-10T07:09:22Z,2018-07-10T07:09:22Z,"Host is Ubuntu 18.04 with Gnome Shell as the desktop. Guest is Windows 10.
Switch guest to full screen (HOST+f), then minimise using the mini toolbar.
Use the VB manager option to ""Show"" the VM. The top of the display is missing, and all mouse clicks are out of alignmnent by this gap.
The problem does not happen if the VM is re-displayed by using the operating system to select the guest, only when the ""Show"" button is used.
See screenshot.

",Smot
17847,vboxdrv failed to build - Virtualbox 5.2.12 r122591 Linux Fedora 28 x86_64,other,Windows,VirtualBox 5.2.12,2018-07-10T15:49:27Z,2018-07-10T15:49:27Z,"Kernel module vboxdrv is VERY broken on Fedora 28
Cannot build on Fedora 28 - 4.17.3-200.fc28.x86_64

Please see dmesg log and output from /var/log/vbox-install.log",Max E
17863,VirtualBox 5.2.12 on Mac OS X 10.13.5 stalling while installing Windows Server 2016,Mac OS X,Windows,VirtualBox 5.2.12,2018-07-10T22:12:49Z,2018-07-10T22:12:49Z,"Hey guys,

I was trying to install Windows Server 2016 and when the file copy finished and the VM restarted to start recognizing hardware, this never happened, it got stalled there and did not move (I waited for about 45 min), finally I had to switch the type of VM from Windows 2016 to Windows 10, then the installation of Windows Server 2016 finished correctly, but this is something you should look into.

Thanks.",jfha73
17772,Guru meditation 1155 on loading driver in guest,Windows,Windows,VirtualBox 5.2.12,2018-07-12T11:45:41Z,2018-07-12T11:45:41Z,"So we trying to load driver inside Windows 7 (6.1.7601.24000) guest machine on Windows 7 host machine with VirtualBox:

{{{
sc create ltest type= kernel start= demand error= ignore binpath= ""<full path to sample>"" DisplayName= ltest
sc start ltest
}}}
and we catch ""Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""

Actually the driver is windows kernel 6.1.7601.24000 (win7sp1_ldr.171231-1547), so it's like trying load second kernel to system. Yes, I known it's crazy, but anyway it's not ok catch guru meditation on this crazy actions.
",gim
17865,Error (rc=-5640): More than one thread in process - Windows 10,other,other,VirtualBox 5.2.14,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
17853,Sayign that Virtualisation is disabled when it is definitely enabled,Windows,Linux,VirtualBox 5.2.14,2018-07-12T21:59:26Z,2018-07-12T21:59:26Z,"When i try to load a virtual machine i get the following error

    ''Failed to open a session for the virtual machine Linux.
    
    VT-x is not available (VERR_VMX_NO_VMX).
        
    Result Code: E_FAIL (0x80004005)
    Component: ConsoleWrap
    Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
''
This is also happening for my Windows 7 Virtual machine (Both machines are 64-bit)

I have checked all the the things i could think of, and anything that came up after a quick google search and all seems okay to me.

So far i have checked:

Virtualisation Enabled in BIOS - Yes ->(https://imgur.com/gallery/cxYxs7d)

Hyper-V disabled in Windows - Yes -> (https://imgur.com/gallery/rO8u0j9)

Windows sees that Virtualisation is enabled in the Task Manager ->(https://imgur.com/gallery/92A0Ebb)

I have tried enabled and disabling Hyper-V to no avail.
I have also tried with both VT-D enable and disabled - Yet it makes no difference",TheBritishBoi
1347,"USB device reported working, but no communication",other,other,VirtualBox 1.5.6,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 
9717,Unable to restore from state saved with memory balloon active,Windows,Windows,VirtualBox 4.1.4,2018-07-18T15:19:40Z,2018-07-18T15:19:40Z,"Steps to reproduce:

 1. Create a VM, install an operating system that supports the VirtualBox Guest Additions (Windows, Linux)
 2. Install Guest Additions, Reboot guest
 3. VBoxManage controlvm [vnname] [balloon size][[BR]]
   (any balloon size grater than zero causes the issue)
 4. Save the VM state
 5. Attempt to start the VM

Error message is Failed to load unit 'pgm' (VERR_SSM_LOADED_TOO_LITTLE).",cb1
17872,"virtualbox in text-only mode (for a better Accessibility of old guest systems, especially when using a Braille display on the host)",other,other,VirtualBox 5.2.16,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
17876,Audio gets looped over.,Windows,Windows,VirtualBox 5.2.16,2018-07-19T16:08:49Z,2018-07-19T16:08:49Z,"So i have:

 1. [ host] Win10x64
 2. [ guest] win7
 3. in win7 installed ""Screen.Capturer.Recorder.v0.12.10"" for audio capture
 4. listening siriusxm via chrome
 5. issue starts in 5-15mins

on VirtualBox-5.1.30-118389-Win same ""machine"" works fine, and
each new version of vbox up to VirtualBox-5.2.16-123759-Win have the same issue
with audio.
Need some additional files/tests ?",Genius
17879,Slow traffic on Bridged network interface when using anything but virtio-net,Linux,Linux,VirtualBox 5.2.16,2018-07-20T18:48:38Z,2018-07-20T18:48:38Z,"Hi,

I'm noticing my network interfaces on my VM is very slow 300-400KB/s when using any of these network intefaces:

PCnet-PCI II (Am79C970A)
PCnet-FAST III (Am79C973)
Intel PRO/1000 MT Deesktop (82540EM)
Intel PRO/1000 T Server (82543GC)
Intel PRO/1000 MT Server (82545EM) - couldn't bring network up

When I used:

Paravirtualized Network (virtio-net)

I saw the normal speeds ie 3-4MB/s which is what I should be getting.

The virtual machine is a Debian 9 (Stretch)

Linux virtualmachine 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux


 ii  virtualbox-guest-dkms             5.2.10-dfsg-6~bpo9+1           all          x86 virtualization solution - guest addition module source for dkms
ii  virtualbox-guest-utils            5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - non-X11 guest utilities
ii  virtualbox-guest-x11              5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - X11 guest utilities

The host is Archlinux (latest updates 2018-07-20) ie:

Linux host 4.17.6-1-ARCH #1 SMP PREEMPT Wed Jul 11 19:14:29 UTC 2018 x86_64 GNU/Linux

The virtual machine currently has:

Base Memory: 2048MB
Chipset:     PIIX3
Enable I/O APIC = yes
Proceessor(s) = 4
Execution Cap = 100%
PAE/NX = false
Paravirtulization Interface: Default
VT-x/AMD-V = yes
Nested Paging = yes
Video Memory 128MB

Network:

Bridged Adaptor, on VLAN 2. (VLAN is set inside of the virtual machine).
Has dual stack IPv4 & IPv6 ie NAT IPv6 addressss and IPv6 GLA address.

The version of VirtualBox that ArchLinux has at the moment is 5.2.16 r123745",Tyler A
17885,AVAST Internet Security reports threats when I start any machine under VB,Windows,Windows,VirtualBox 5.2.16,2018-07-23T13:07:15Z,2018-07-23T13:07:15Z,"Hi! I've been using VBox since Jan 2014. Since last year I keep getting Threats Blocked messages by my AVAST Internet Security. Threats messages read:
""We’ve safely blocked connection on Sportgoods.co.in because infected with URL:Mal.
 We’ve safely blocked connection on Spmpart.com because infected with URL:Mal.
We’ve safely blocked connection on Tektasarim.com because infected with URL:Mal.
""
This threat is quite annoying. And always shows that Virtual Box is trying to contact the above 3 sites!?!
I'm running Virtual box under Windows-10, fully updated. The guest system runs Windows XP. ",VBFan2018
17786,Consider using Digital Mars C compiler,all,all,VirtualBox 5.2.12,2018-07-24T11:11:07Z,2018-07-24T11:11:07Z,Consider using Digital Mars C compiler for things like the BIOS. It should have full support for x86 segmentation etc. It is now fully open source: https://github.com/DigitalMars/Compiler,Yuhong Bao
17864,VirtualBox kernel modules do not build on Fedora 28,Linux,all,VirtualBox 5.2.14,2018-07-24T15:44:33Z,2018-07-24T15:44:33Z,"VirtualBox-5.2-5.2.12_122591_fedora26-1.x86_64

Issuing /sbin/vboxconfig fails.

There's multiple files being complained about containing the line
IPAddressDeny=any (""File /usr/lib/systemd/system/systemd-logind.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling""):

systemd-machined.service
systemd-udevd.service
systemd-journald.service
systemd-logind.service

Finally (and after commenting out IPAddressDeny=any for debugging purposes in named files) it still fails:
{{{
(...)
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClient.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClient.c
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClientComponent.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClientComponent""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/SUPR0IdcClientComponent.c
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPR0IdcClient-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient_linux""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.c
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClientComponent.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClientComponent.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClientComponent.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o"";
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClient.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/SUPR0IdcClient-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o""; fi; fi;
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClient.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClient.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/VBoxPci.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/VBoxPci.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/VBoxPci.o""; fi; fi;
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:80,
                 from /tmp/vbox.0/linux/VBoxPci-linux.c:31:
In function ‘strncpy’,
    inlined from ‘vboxPciLinuxDevDetachHostDriver’ at /tmp/vbox.0/linux/VBoxPci-linux.c:436:9,
    inlined from ‘vboxPciOsDevInit’ at /tmp/vbox.0/linux/VBoxPci-linux.c:645:14:
./include/linux/string.h:246:9: warning: ‘__builtin_strncpy’ specified bound 64 equals destination size [-Wstringop-truncation]
  return __builtin_strncpy(p, q, size);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/VBoxPci-linux.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/VBoxPci-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/VBoxPci-linux.o""; fi; fi;
  ld -m elf_x86_64 -z max-page-size=0x200000   -r -o /tmp/vbox.0/vboxpci.o /tmp/vbox.0/linux/VBoxPci-linux.o /tmp/vbox.0/VBoxPci.o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o 
make -f ./scripts/Makefile.modpost
  find /tmp/vbox.0/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost   -i ./Module.symvers -I /tmp/vbox.0/Module.symvers  -o /tmp/vbox.0/Module.symvers -S  -w  -s -T -
  gcc -Wp,-MD,/tmp/vbox.0/.vboxpci.mod.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DKBUILD_BASENAME='""vboxpci.mod""' -DKBUILD_MODNAME='""vboxpci""' -DMODULE  -c -o /tmp/vbox.0/vboxpci.mod.o /tmp/vbox.0/vboxpci.mod.c
  ld -r -m elf_x86_64 -z max-page-size=0x200000 -T ./scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxpci.ko /tmp/vbox.0/vboxpci.o /tmp/vbox.0/vboxpci.mod.o ;  true
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.17.3-200.fc28.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc
make -f ./scripts/Makefile.modinst
  mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc ; cp /tmp/vbox.0/vboxpci.ko /lib/modules/4.17.3-200.fc28.x86_64/misc ; true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko ; scripts/sign-file ""sha256"" ""certs/signing_key.pem"" certs/signing_key.x509 /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko || true && true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
  /bin/sh ./scripts/depmod.sh /sbin/depmod 4.17.3-200.fc28.x86_64 """"
}}}
After updating to VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64 there's an empty vbox-install.log after issuing /sbin/vboxconfig, vbox-setup.log shows:

Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.

No information on why it failed to build.",ThygWedd
16508,Shared Clipboard gives guests too much access to the clipboard,all,all,VirtualBox 5.1.14,2018-07-24T15:46:20Z,2018-07-24T15:46:20Z,"The VirtualBox Shared Clipboard gives guests read or write access to the clipboard even when the window for the virtual machine is not focused.  With clipboard sharing enabled, the guest can indefinitely monitor the host clipboard or replace its contents even with no recent user interaction with the VM.  I believe this level of access is almost never necessary.  VirtualBox could instead 1) wait for the VM window to become focused before copying the host clipboard into the VM 2) only let the VM set the host clipboard if the VM window is focused.  This would drastically reduce the severity of attacks by guests that continuously sniff the host clipboard or maliciously replace its contents.

Tested: VirtualBox 5.1.14 official packages on Ubuntu 16.04.2 host, Ubuntu 16.04.2 guest

Continuously read the host clipboard, even when the VM window is not focused:

{{{
while true; do sleep 1; xclip -o; echo; done
}}}

Write the host clipboard, even when the VM window is not focused:

{{{
sleep 5; echo ""rm -rf /tmp\n"" | xclip -in -selection clipboard
}}}
",ivank
17892,Guest freeze when virtualizing 9 or more CPU,other,all,VirtualBox 5.2.16,2018-07-25T02:13:37Z,2018-07-25T02:13:37Z,Attempt to virtualize 9 or more CPUs results guest freeze. Different guest OS'es affected.,Dian
17871,Missing installation instructions at Web site (virtualbox.org) for openSUSE 15.0 -> fixed after 5.2.16,other,other,VirtualBox 5.2.16,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
17895,Cannot create a disk image via GUI,other,other,VirtualBox 5.2.8,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
17900,"after install old Ubuntu 8.04 and then reboot, the virtualbox will show error",other,other,VirtualBox 5.2.16,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
17902,VirtualBox non funziona,Windows,Windows,VirtualBox 5.2.16,2018-07-28T16:23:31Z,2018-07-28T16:23:31Z,"ho effettuato una pulizia con CCleaner e non riesco a fare ripartire VirtualBox.
Il log che esce è:
VirtualBox COM Server 5.2.16 r123759 win.amd64 (Jul 16 2018 15:52:14) release log
00:00:00.015619 main     Log opened 2018-07-26T11:32:49.851605900Z
00:00:00.015619 main     Build Type: release
00:00:00.015619 main     OS Product: Windows 10
00:00:00.015619 main     OS Release: 10.0.17134
00:00:00.015619 main     OS Service Pack: 
00:00:00.031240 main     DMI Product Name: System Product Name
00:00:00.031240 main     DMI Product Version: System Version
00:00:00.031240 main     Host RAM: 4016MB (3.9GB) total, 1812MB available
00:00:00.031240 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031240 main     Process ID: 13232
00:00:00.031240 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.031240          VirtualBox: object creation starts
00:00:00.046862          Home directory: 'C:\Users\piero\.VirtualBox'
00:00:00.046862          Installed Drivers:
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.2.16.23759)
00:00:00.062483          Loading settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:00.062483          Getting USB descriptor failed with error 31
00:00:00.078104          USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
00:00:00.171832          HostDnsMonitor: old information
00:00:00.171832            no server entries
00:00:00.171832            no domain set
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitor: new information
00:00:00.171832            server 1: 192.168.1.1
00:00:00.171832            domain: station
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitorProxy::notify
00:00:00.203076          SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:00.250013          VD: VDInit finished with VINF_SUCCESS
00:00:00.250013          Loading settings file ""C:\Users\piero\VirtualBox VMs\Windows Xp\Windows Xp.vbox"" with version ""1.15-windows""
00:00:00.265565          VirtualBox: object created
00:00:01.653184          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:01.663208          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:05.471174          Load [C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL] rc VINF_SUCCESS
00:00:05.714537          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
01:21:15.783203 USBPROXY Getting USB descriptor failed with error 31
02:59:48.161337 MainPower Host suspending: Paused 1 VMs
03:01:39.953430 MainPower Host resumed: Resumed 1 VMs
03:01:41.573588 dns-monitor HostDnsMonitor: old information
03:01:41.573588 dns-monitor   server 1: 192.168.1.1
03:01:41.573588 dns-monitor   domain: station
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitor: new information
03:01:41.573588 dns-monitor   no server entries
03:01:41.573588 dns-monitor   no domain set
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitorProxy::notify
03:02:05.331431 USBPROXY Getting USB descriptor failed with error 31
03:02:05.332406 USBPROXY USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
03:02:05.896003 dns-monitor HostDnsMonitor: old information
03:02:05.896003 dns-monitor   no server entries
03:02:05.896003 dns-monitor   no domain set

Ho provato anche a fare la riparazione reinstallando il programma ma non funziona ugualmente. 
Qualcuno mi può aiutare? Ringrazio. Piero",Piero
17868,VirtualBox doesn't work and can't finish reinstall (but booting virtual box still works) (cant boot my vm),other,other,VirtualBox 5.2.14,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
17869,"VM minimized to Dock not un-minimized by ""Show""",Mac OS X,all,VirtualBox 5.2.12,2018-07-28T17:20:31Z,2018-07-28T17:20:31Z,"Running VirtualBox 5.2.14 on macOS 10.13.6; I also observed this with 5.2.12, but that's the only other version I've checked.

If a VM window is minimized to the Dock, the window is not unminimized by clicking ""Show"" in the VirtualBox Manager window, regardless if from the toolbar, right-clicking on the VM name, or from the Machine menu. The window has to be unminimized by clicking the VirtualBoxVM icon in the Dock, or clicking the minimized window in the Dock.

Note: this for VM windows minimized using the yellow (middle) button in the upper left corner of the title bar; NOT by right-clicking the VirtualBoxVM icon in the dock and clicking ""Hide"". ""Show"" works fine for hidden windows and windows in full-screen or in another space.

This is regardless of the guest OS.

I have attached a log for a test VM (new, no OS) just after minimizing and clicking ""Show"", run under the macOS ""Guest User"" temporary account.",Christopher Chavez
17877,RHEL 7.5 Guest Blank Login screen,Windows,Linux,VirtualBox 5.2.16,2018-07-28T17:45:32Z,2018-07-28T17:45:32Z,"Installed Latest RHEL 7.5 and used Virtual Box 5.2.16 r123759. As soon as 
I install the Guest additions and reboot, I can not login to 
Graphical Desktop. Instead of login, it just shows blank screen. Uninstalling
the guest additions fixes the issue. 

Please note that guest additions installs fine and no issues are
reported. 

Output of /var/log/vboxadd-setup.log
Building the main Guest Additions module.
Building the shared folder support module.
Building the graphics driver module.

Red Hat Enterprise Linux Server release 7.5 (Maipo)

Kernel version

3.10.0-862.9.1.el7.x86_64",ketan
17899,Fail creating machine via SOAP vboxwebsrv,other,other,VirtualBox 5.2.16,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
17880,AppleKeyStore: operation failed (pid: 31 sel: 7 ret: 'e00002c2 ...,other,other,VirtualBox 5.2.16,2018-07-28T20:00:19Z,2018-07-28T20:00:19Z,AppleKeyStore: operation failed (pid: 31 sel: 7 ret: 'e00002c2 ...,Moo
17881,Network in Bridged mode - Guest can't ping host,Windows,Linux,VirtualBox 5.2.16,2018-07-28T20:45:37Z,2018-07-28T20:45:37Z,"- Network configuration: 1 Interface using the Bridged Mode on the Ethernet interface.
- The Guest has access to the internet.
- The host can connect to the guest (ping, ssh, ...)
- The Guest can find the host MAC address and fills the ARP table.
- The Guest can't ping the host. (no answer for the ping).

",zeralight
17883,Bridge adaptor removed when updating to 5.2.16,Windows,Linux,VirtualBox 5.2.16,2018-07-28T20:57:56Z,2018-07-28T20:57:56Z,"Hello,

When updating from 5.2.14 on a Windows 10 host, my VM configured with network using a Bridge Adaptor were not able to boot. By looking at the settings, the dropdown list when selecting the Bridged Adapter is empty. If I'm not mistaken, there is a Network adapter that should be showing in the Windows control panel, but it doesn't. Is it like the update deleted the adapter (as design I guess since there is a warning for that in the installer), but didn't recreate it.

I was able to resolve this by doing a complete uninstall and install, the bridged adapter was shown in the list. But I feel the update shouldn't break that.

PS: I selected Linux as Guest type, as it's my only guest, but I'm sure it applies to all guest.",sharky98
17903,Guru meditation (VERR_VMX_INVALID_GUEST_STATE) on any host with any guest.,Linux,Windows,VirtualBox 5.2.16,2018-07-29T05:15:35Z,2018-07-29T05:15:35Z,"I have tried numerous BIOS settings and software settings however whenever trying to run a guest on my system (Ubuntu 18.04) I receive (VERR_VMX_INVALID_GUEST_STATE) on both Ubuntu 18.04 and Windows 10 1803 hosts. You can see a list of what I have tried here https://forums.virtualbox.org/viewtopic.php?f=6&t=88833&p=426110#p426110

I have tried downgrading to 5.1.x but I receive hardening issues when doing so. 

Attached are the logs. ",Surgikill
17890,Double Clicking or Open of .vbox File or Alias Error,Mac OS X,Windows,VirtualBox 5.2.16,2018-07-29T07:50:16Z,2018-07-29T07:50:16Z,"Double Clicking or Open of .vbox File or Alias produces the error:
""Failed to open virtual machine located in /Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox.

Trying to open a VM config '/Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox' which has the same UUID as an existing virtual machine.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}""

Have changed the UUID withe command line "" /Applications/VirtualBox.app/Contents/MacOS/VBoxManage internalcommands sethduuid '/Users/mike/VirtualBox VMs/Widows 10/Windows 10.vdi'"" but get the same error.
",McTTRS
17891,Cannot Create Host-Only Network on Windows 10,other,other,VirtualBox 5.2.16,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
17893,Image doesn't start under Windows 10,Windows,all,VirtualBox 5.2.16,2018-07-29T08:33:03Z,2018-07-29T08:33:03Z,"I try to create a virtual box under Windows 10. I tried multiple OSs and also VirtualBox 5.1.38. I always get the following error code when I try to start the newly generated image:

Failed to open a session for the virtual machine UbuntuDon.

The virtual machine 'UbuntuDon' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\do991164\VirtualBox VMs\UbuntuDon\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",Don83
17894,Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack not installing,other,other,VirtualBox 5.2.16,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
17901,Bugs related to Copy files from Host to the virtual machine.,Windows,Windows,VirtualBox 5.2.16,2018-07-29T13:54:19Z,2018-07-29T13:54:19Z,"  Can not copy and paste with Bi-directional option enabled
and it is stopping drag and drop when I freeze the current state and return later, so I always have to shut down the machine in order to work Drag and drop
these problems are happening with Windows 7 64 Bit and Windows 10 64 Bit

Note: I installed the virtual machines using the standard Virtual Box did not do customizations in the HD, just changed the size of ram memory to 4 GB and put 4 processor cores, the network card I used Bridge.",Luciano_F
17875,problems with win10 1803 and virtualbox,other,other,VirtualBox 5.2.16,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
17873,macOS Host: dont work UAC windows 7 and 8.1 guest vm,Mac OS X,Windows,VirtualBox 5.2.16,2018-07-29T13:59:15Z,2018-07-29T13:59:15Z,"Hello! In the guest system Windows 7 and 8.1 the UAC request does not work!
",@…
17746,"Slow I/O when ""Use Host I/O Cache"" is switched on",Linux,Linux,VirtualBox 5.2.10,2018-07-29T15:08:38Z,2018-07-29T15:08:38Z,"I installed VirtualBox 5.2 and when I/O cache is switched on, I/O is very slow.

Steps to reproduce:

1. Create a virtual machine with Debian or Ubuntu
2. Switch ""Use Host I/O Cache"" on, on SATA controller.
3. Try to upgrade existing packages or install new in the virtial machine. I have spinning disks on my host computer and they become noisy and IO speed is between 900KB/s and 1.3 MB/s during installation or upgrade of packages. I had no such problem with VirtualBox 5.1.",Georgi
17906,I cant run my VM,Windows,Windows,VirtualBox 5.2.16,2018-07-31T14:24:44Z,2018-07-31T14:24:44Z,"Good day,
I need your help solve my vm problem, it cant run, I have the message and the name error that printout.
""
Error in supR3HardNtChildWaitFor
Timed out after 2001 ms waiting for child request #0
(PurifyCuildAndCloseHandles).
(rc=258)

Please try reinstalling VirtualBox.

where supR3HardNtChildWaitFor what? 5 Unknow Status 258 (0x102)(258)-
Unknown Status 258 (0x102)
""",BrADT23
17739,Seamless mode not working with Fedora 28 guest,Windows,Linux,VirtualBox 5.2.10,2018-07-31T19:11:04Z,2018-07-31T19:11:04Z,"After vbox guest additions are installed with no errors, I observe that the seamless mode option is no longer disabled but I am still unable to copy/paste in either direction.

Entering seamless mode also does not show the windows open in guest OS but I am unfamiliar with seamless mode to know if it was user error or system error.

Host - 
Windows 10
Virtual box version - 5.2.10 r122406

Guest - 
Fedora 28
`uname -r` - 4.16.6-302.fc28.x86_64",AB
17487,Strange behaviour of linked clones.,all,all,VirtualBox 5.2.6,2018-08-01T05:31:41Z,2018-08-01T05:31:41Z,"This one was reported by a user in the forums here: https://forums.virtualbox.org/viewtopic.php?f=6&t=86354&start=15.

I have reproduced the behaviour he reports and must admit that I find it hard to explain.

The behaviour is that, if you create a linked clone then the difference image for the clone is registered in the media register of the base VM, not in the .vbox file of the clone. Surely the media should be registered with the VM which owns the media?

This is not a problem as long as both VMs remain registered. However, if you unregister the clone VM then the media is deleted from the parent VM register. When you try to re-register the clone VM (e.g. you wanted to move it to another drive) you get a media not found error.

It's possible there is some reason for this that escapes me, but frankly it seems like a bug. Of course it would normally escape attention as long as the two VMs remain registered.",mpack
17907,"Mouse pointer icon frozen, mouse clicks working when USB2 enabled in Win10 VM",Windows,Windows,VirtualBox 5.2.16,2018-08-01T23:00:57Z,2018-08-01T23:00:57Z,"1. hp Zbook STudio G3 laptop, 16GB RAM, I7-6700HQ CPU @2.6GHz
2. Windows 10 Enterprise, 64-bit OS, x64-based processor
3. Logitech wireless mouse and keyboard, M510.
3. VirtualBox-5.2.16-123759-Win.exe
4. Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack

Problem Description:

Installed VirtualBox-5.2.16-123759-Win.exe.  
Downloaded Windows 10 trial to create a Windows 10 VM with.
Used without issue for several days.  Mouse and keyboard working fine.

Installed VirtualBox guest additions.  
Settings->UserInterface->Devices checked Insert Guest Additions CD Image.
Started VM.
Ran the installer, VBoxWindowsAdditions-amd64. rebooted.
Mouse and keyboard still working fine.

Needed access to usb2 devices.
shutdown vm.
USB2 & 3 could not be enabled. Instructions said to install extension pack.
downloaded Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack and installed.
Enabled USB2:  Settings->USB.  Added USB devices, Intel Corp. [0001], Logitech USB Receiver [1203] 
Usb2 & usb3 could now be enabled in Settings.
start vm.

As soon as Windows initial screen appears, mouse pointer icon appears frozen.
The wait cursor (round circle) is showing and changing.
moving the mouse makes the mouse cursor blink but the actual cursor does not change position.
as you physically move the mouse, You can see different areas of the windows screen responding as 
an ""invisible"" mouse cursor passes over them.
clicking the mouse brings up the mouse dialog menus. 
The host computer has no mouse capability.
If I don't login and enter windows, and I stay on the login screen, I can use the tab key to move over and select 
shutdown.
As soon as the VM shuts down, I have control over the mouse again.

While VM is shutdown, I can go back to settings, delete the USB devices I added for USB 2.
when vm is restarted, I can move mouse.

I also tried a wired HP usb mouse.  Same behavior.

I tried going to logitech site for updates for mouse driver.  Did not find anything.
Since the HP wired mouse has the exact same behavior, I don't think it is Logitech related.",inxe
17909,weird time adjustment,Linux,Windows,VirtualBox 5.1.38,2018-08-02T08:39:40Z,2018-08-02T08:39:40Z,"Hello. I use ""VirtualBox Graphical User Interface Version 5.1.38_Ubuntu r122592 © 2004-2018 Oracle Corporation (Qt5.5.1)"". And using Windows XP on it. I use my own program to track the accuracy of the time, and sometimes I notice that Windows is weirdly tuning the time. For example I attach today's graph of adjustment.

It can be seen that the detuning runs on some kind of sinusoid, and then at some point it goes out on a flat line. Then, when the detuning builds up, it for some reason again goes to the sinusoid of an unacceptably large amplitude, and then again sets the normal time. On the vertical axis - milliseconds. That is, during these sinusoid detuning reaches 15 seconds - it's terrible, I think. 

I tried to disable the vm module on WindowsXP, and the tuning is disabled, but the clipboard between vm and my machine stops working as well - thats not good.

So, I have a couple of questions:

1) Why is there such a strange sinusoid used in the time adjustment (which uses the SetSystemTimeAdjustment) instead of a rapidly decaying exponent?

2) can I disable this strange time adjustment without disabling the clipboard?

",daybit
17889,"VBox 5.2.16: Microphone not working: macOS Host, Linux/Debian Guest",Mac OS X,Linux,VirtualBox 5.2.16,2018-08-02T18:26:21Z,2018-08-02T18:26:21Z,"Host: MacBook Pro, macOS El Capitan, VirtualBox 5.2.16
Guest: Linux/Debian 9 (stretch)

Audio out works. Audio in (via mic) does not. (Full disclosure: I did not test other types of audio sources.)
I tried ""Sound Recorder"" and ""Audacity."" Neither worked.
Audacity gives me various mic sources; I tried them all. None worked.
VM log attached.

I haven't been able to find any relevant ticket that's still open.
If I've missed one, I'm sure I'll be admonished and this ticket ""merged.""",LiamF
16084,ssl connection incorrectly reset when using NAT,Mac OS X,Linux,VirtualBox 5.0.28,2018-08-08T16:17:15Z,2018-08-08T16:17:15Z,"After upgrading VirtualBox from version 5.0.26 to 5.0.28 on OS X 10.11.6, I noticed that ssl connections created in python with urllib2.urlopen are incorrectly reset on a Debian 8 guest with a single network interface in NAT mode. I attached a minimal python script that almost always fails with the following traceback:
{{{
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Failed
Traceback (most recent call last):
  File ""./test.py"", line 12, in <module>
    shutil.copyfileobj(xact, pipe)
  File ""/usr/lib/python2.7/shutil.py"", line 49, in copyfileobj
    buf = fsrc.read(length)
  File ""/usr/lib/python2.7/socket.py"", line 380, in read
    data = self._sock.recv(left)
  File ""/usr/lib/python2.7/httplib.py"", line 602, in read
    s = self.fp.read(amt)
  File ""/usr/lib/python2.7/socket.py"", line 380, in read
    data = self._sock.recv(left)
  File ""/usr/lib/python2.7/ssl.py"", line 714, in recv
    return self.read(buflen)
  File ""/usr/lib/python2.7/ssl.py"", line 608, in read
    v = self._sslobj.read(len or 1024)
socket.error: [Errno 104] Connection reset by peer
}}}
I also attached the tcpdump output on both the host and the guest. The issue seems to only occur when the network traffic goes through the host thunderbolt ethernet adapter. If I switch to Wi-Fi, the issue does not occur. Moreover, I am unable to reproduce the problem with curl or wget.",exg
17919,Hackshield doesn't work in Virtualbox,Mac OS X,Windows,VirtualBox 5.2.16,2018-08-08T18:40:01Z,2018-08-08T18:40:01Z,"The issue is related to this one: https://www.virtualbox.org/ticket/4572

Guest OS: Win 7
Host OS: OSX Sierra

After 5-6 minutes playing to AirFlyFF (https://airflyff.com/) the game crashes due to Ahnlab Hackshield game hack found, when there is nothing else running besides the game itself. The game works smoothly on a Windows PC, and crashes only with Virtualbox.",Gnemes
5595,Request: built in VDI disk-size optimization routine,Mac OS X,Linux,VirtualBox 3.0.12,2018-08-11T05:39:54Z,2018-08-11T05:39:54Z,"Currently there are few available routes for shrinking a VDI image file successfully. Zeroing unused space is an unsupported requirement which requires software outside of virtualbox. Additionally, third party utilities can be flakey, or may not exist for the platform at hand. A terrific addition would be an integrated solution to the problem of dynamically expanding storage. Perhaps an all encompassing routine a user can run to clean up wasted space in a VDI file (i.e. shrink them in place), incorporated directly into virtualbox, without the need to run third party software.",DGF
17923,miracast on Windows 10 guest system not working,Windows,Windows,VirtualBox 5.2.16,2018-08-11T05:41:59Z,2018-08-11T05:41:59Z,"trying to use miracast on windows 10 (virtual) system of virtualbox not working?
could you please tell me if it's possible to make it work or is it a limitation.
thanks",babouchka
17927,VBoxLinuxAdditions.run --target is dangerous if dir exists (possible data loss),all,Linux,VirtualBox 5.2.16,2018-08-14T12:30:53Z,2018-08-14T12:30:53Z,"Running VBoxLinuxAdditions.run usually creates a directory in /tmp. But running this script with option --target <dir> is very dangerous, if the directory <dir> already exists. This may result in a possible large data loss! The script more or less does:

1.  mkdir <dir>
2.  [extract several files to <dir>]
3.  chown -R <currentuser>:<currentuser> <dir>
4.  [build and install drivers]
5.  rm -rf <dir>

Now imagine you call this with the home directory as argument.

  sudo ./VBoxLinuxAdditions.run --target ~

1. This is a no-op, the home directory already exists.
2. This will extract files all across the home directory. Bad idea!
3. This will transfer ownership of *all* files in user's home directory (including the directory itself) to root. Very bad idea!!!
4. [not relevant]
5. This will remove the whole home directory. Totally unacceptable!!!

This is a grossly negligent, even fatal script design!!!!

If you want to do it this way, then there *must* be a check if the target directory <dir> already exists and the script must fail with an error if so.",Hagge
17928,Kernel panic for 5.2.16 virtual box on MacOs,Mac OS X,other,VirtualBox 5.2.16,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
17936,ERROR: could not insert 'vboxdrv': Exec format error,Linux,other,VirtualBox 5.1.38,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
17935,"VBox crash restarting after Windows guest put into fullscreen mode, and VM unusable after that",Mac OS X,Windows,VirtualBox 5.2.18,2018-08-19T08:19:45Z,2018-08-19T08:19:45Z,"I'm using Virtualbox 5.2.18 to run a new Windows 10 VM on Mac OS 10.13.6 on a 12"" MacBook. If I take the Windows 10 guest full screen, then save the machine state, I am unable to restart it. I get:

Failed to open a session for the virtual machine Win10.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

After that, Virtualbox itself crashes, and the machine has a status of Aborted. I've not found a way to get the machine started after that, short of restoring from a Time Machine backup. Even if I delve into the vbox file and change fullscreen to false, I get the same crash trying to restart the machine. I've attached a zip archive of the Mac OS crash log, and the Virtualbox log. This is entirely repeatable, and I get the same error on an old Windows 7 VM.",SDD
17938,Deleting snapshot on-line causes I/O errors in guest,Linux,other,VirtualBox 5.2.16,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
17940,"For Fedora, Virtualbox is being built for unsupported releases (Fedora 26)",Linux,other,VirtualBox 5.2.18,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
16543,High CPU load with MP Linux 4.10 guest,Windows,Linux,VirtualBox 5.1.16,2018-08-22T07:53:27Z,2018-08-22T07:53:27Z,"When a Linux 32-bit guest is configured with 2 processors and uses the 4.10 kernel, it loads 100% a host processor core.
It doesn't happen with kernel 4.9 and before.
It doesn't happen with a single guest processor.

During boot the message {{{smpboot: do_boot_cpu failed(-1) to wakeup CPU#1}}} appears.",Urmas
17948,Saving a Linux VM (Debian) crashes very often,Windows,Linux,VirtualBox 5.2.18,2018-08-22T15:49:52Z,2018-08-22T15:49:52Z,"I have a Windows 10 host system where VirtualBox 5.1.28 is installed.
In one VM I installed Linux Debian Stretch.

Starting and running that Linux system works fine.
However when closing the VM by saving its state, the saving process crashes in about 7 out of 10 cases.

A windows with these error messages is shown (translated back from German so it might not be totally correct):

The state of the virtual machine could not be saved.

Details: The object is not ready
Error code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}


These crashes also occured in older versions of VirtualBox (5.1.x).

I could not notice this crashing behaviour with other VMs running a different flavour of Linux (Centos).

",DonJuan
17943,Windows 2000 image does not start,other,other,VirtualBox 5.2.18,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
17944,Critical Error,other,other,VirtualBox 5.2.18,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
16432,Unable to open sqlite database on shared folder,Linux,Linux,VirtualBox 5.1.14,2018-08-22T16:43:17Z,2018-08-22T16:43:17Z,"When attempting to open an sqlite database on a shared folder it fails with ""Error: disk I/O error""

If I copy that same database from the shared folder locally to the VM then the open succeeds.
{{{
jlmcgraw@mate1604:~$ sqlite3 /media/sf_Shared_Folder/Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.
 sqlite> .tables
 
 Error: disk I/O error
 sqlite> .q

jlmcgraw@mate1604:~$ cp /media/sf_Shared_Folder/Recordings.db .

jlmcgraw@mate1604:~$ sqlite3 Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.

 sqlite> .tables
 ZDATABASEPROPERTY  ZRECORDING         Z_MODELCACHE     
 ZENTITYREVISION    Z_METADATA         Z_PRIMARYKEY     

 sqlite> .q
}}}",jlm
17950,5.2.18 still not in fedora 28 repository,Linux,other,VirtualBox 5.2.18,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
17952,5.2.18 - Windows 10 Pro Host 64-bit only supports 32-bit OS.,Windows,Linux,VirtualBox 5.2.18,2018-08-23T05:20:54Z,2018-08-23T05:20:54Z,"In Setting-General for Linux virtual machine, Type: Linux Version: only displays 32-bit OS.  Need 64-bit OS as in past.",BigAlKC
17953,supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll,Windows,Linux,VirtualBox 5.2.18,2018-08-24T14:12:37Z,2018-08-24T14:12:37Z,"VM boot fails with following error in the VBoxHardening.log

768.1808: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Error (rc=0):

768.1808: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Fatal error:

768.1808: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\SHELL32.dll' / '\??\C:\Windows\system32\SHELL32.dll': 0xc0000190

1d50.15d4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1651 ms, the end);

1b18.ac8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2014 ms, the end);
",IvanP2017
17956,Sort button in the context menu,Linux,all,VirtualBox 5.2.16,2018-08-26T00:10:15Z,2018-08-26T00:10:15Z,"Can you please move the sort button in the context menu away from the bottom of the menu, or at least make it prompt the user?

In KDE 5 I keep triggering it by accident when I nudge my mouse while right-clicking a VM near the bottom of the list in the left sidebar, and I'm tired of rearranging my VMs all the time.",Rmb1
17576,After update vbox guest machines force window decorations even when disabled by window manager,Linux,all,VirtualBox 5.2.8,2018-08-26T07:21:32Z,2018-08-26T07:21:32Z,"After VirtualBox was updated last night to 5.2.8 on Debian Testing, guest machines now have window decorations and borders forced even though my window manager (JWM) is set to remove them.

Before last night's VirtualBox update, my window manager rules worked properly.  It appears that something was changed in VirtualBox to cause this.",Will B
17955,fullscreen and gpu passtrough,Windows,other,VirtualBox 5.2.18,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
17057,VBoxManage freezes,Linux,Windows,VirtualBox 5.1.26,2018-08-27T12:44:32Z,2018-08-27T12:44:32Z,"Since the latest release of vbox (5.1.26), vboxmanage suddenly freezes. I'm able to run vboxmanage from command line (e.g. vboxmanage --version) but it appears that it is no longer able to communicate with the virtual machines. e.g.

{{{
VBoxManage showvminfo TEST-W10
VBoxManage controlvm TEST-W10 screenshotpn /tmp/test.png
etc...
}}}

Running these commands will not return anything (the command ""freezes"" and I have to hit CTRL+C to aboard it). This happens every 1-3 days.

The VMs are still running (and I can connect to them via vbox RDP), but I'm not able to control them on the host anymore (via vboxmanage). The only way to get it running again is to kill all VMs (killall VBoxHeadless) and do a complete reboot of the system.


{{{
OS:
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial


Kernel:
Linux X 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

VBox:
5.1.26

Virtual Additions:
None

}}}
",LennyHers
17949,Mac OS High Sierra Host - Windows 10 Guest - Shared folder is read-only,Mac OS X,Windows,VirtualBox 5.2.18,2018-08-27T23:52:12Z,2018-08-27T23:52:12Z,"I have created a shared folder. I made sure that read-only is not checked. Virtualbox guest additions is installed. When shared folder is mounted, all directories in the Windows 10 guest are marked as read-only. Unchecking them, to make writable does nothing.",MB2
14923,`guestcontrol run` memory leak in host,Linux,Windows,VirtualBox 5.0.10,2018-08-28T09:12:25Z,2018-08-28T09:12:25Z,"#14850 is the only other open memory leak I can find.  That looks like a guest side leak associated with disk IO, but this is a host side leak associated with `vboxmanage <name> guestcontrol run`

I'm running an Ubuntu host, and a Windows 7 (all updates installed) guest.  The guest is given 1 CPU and 2GB of RAM, but I can get it to consume >8GB of RAM (enough to have the Linux OOM system kill it).  I verified that the guest stabilizes at using ~650MB of RAM in this case, so the leak is definitely on the host side.  To trigger the leak, I first start my VM:

{{{
ian$ vboxheadless -startvm win-7-pro-loaded-base
}}}

Then I run: 
{{{
ian$ vboxmanage guestcontrol win-7-pro-loaded-base run --username administrator ""C:\\Windows\\System32\\ping.exe"" -- ""-t"" ""localhost"" 2>&1
}}}

You can accelerate the leak by running many of the `vboxmanage` commands in parallel.  With 6 running, the `vboxheadless` process went from using 3GB to 5GB (RES in `htop`) RAM in 12 minutes.

Attached are the VBox.log from one occassion of running this, along with an image of `vboxheadless` memory use over time with 6 `vboxmanage` commands running, and an image of the stabilized guest memory.

I also attached a zip of running:
{{{
sudo strace -i -ff -p <vboxheadless first thread PID> -o strace_output/strace
}}}

for a few minutes while the 6 `vboxmanage` commands were running.

Let me know if there's more information I can supply, or if you'd like me to try anything.  I started along the path of building and running virtualbox from source so I could poke around, but I'm having a few issues.

Thanks in advance for all of your help!",iano
16710,Error while drag and dropping files,Windows,Windows,VirtualBox 5.1.20,2018-08-28T09:22:18Z,2018-08-28T09:22:18Z,"In recent build but also in previous builds I very often came accross this error:

Drag and drop error from guest (VERR_FILE_NOT_FOUND).

Resultaatcode:
VBOX_E_IPRT_ERROR (0x80BB0005)
Component:
GuestWrap
Interface:
IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

drag and dropping files should work seamless without problems, just as in VMware player (concurrent). Why does it not work in Virtualbox. Please solve this mather in a next build.
",HookyPooky
17032,Drag and Drop doesn't work from host W7 to guest W10,Windows,Windows,VirtualBox 5.1.26,2018-08-28T09:24:01Z,2018-08-28T09:24:01Z,"Host W7 Professional 64bit latest SP and patches, guest W10 Professiona 64bit.
Bidirection setting.
Drag form host to guest never work.
Drag from guest to host work, but sometime guest freeze and a reboot of the  guest is necessary.
In attach vbox.log and vboxtray.log.",Bonato Agostino
17874,Drag and drop feature doesnt work Windows 10,Windows,Windows,VirtualBox 5.2.14,2018-08-28T09:42:29Z,2018-08-28T09:42:29Z,"Multiple installations and different versions of 64bit win 10
Drag and drop is enabled, this does not allow drag and drop of a folder onto the VM  

The red circle is presented.

This works sporadically, sometimes a reboot of vm required with it turned on or off before it works
Sometimes I cannot get it to ever work.",Pierre81
15489,not working copy / paste and  Drag & Drop,other,Windows,VirtualBox 5.0.20,2018-08-28T12:15:06Z,2018-08-28T12:15:06Z,"not working copy / paste and  Drag & Drop
I have VB on my mac 
On VB is installed Windows
I can't copy paste from mac to win and from win to mac",SK
16943,Drag and Drop Feature not working,other,Windows,VirtualBox 5.1.24,2018-08-28T12:19:32Z,2018-08-28T12:19:32Z,"Drag and Drop setting is already Bidirectional.. but this feature is not functioning properly.

Restart will solve it temporarily then again the issue will come.

Similar ticket has been already issued but for older version ""5.1.22"". 
I'm using latest version ""5.1.24"" and tested on Win 2016 & win10. ",alman7005
14765,Drag and Drop failure,other,other,VirtualBox 5.0.8,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
14499,vboxmanage guestcontrol never returns / hangs,other,other,VirtualBox 4.2.32,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
17490,VBoxManage and Guest Additions 5.2.x: Can't communicate with Linux Guests,Linux,Linux,VirtualBox 5.2.6,2018-08-29T02:14:05Z,2018-08-29T02:14:05Z,"VirtualBox was updated from 5.0.32 (very stable version) to 5.2.4 and later 5.2.6.

All VM:s are provisioned through VBoxManage, but with Guest Additions 5.2.x on Linux guests, the VBoxManage processes just hang. Windows guests work fine, though.

So, with VirtualBox 5.2.6 and Guest Additions Version:

5.2.0-Hangs

5.2.2-Hangs

5.2.4-Hangs

5.2.6-Hangs

5.2.7-120349-Hangs

5.1.30-Works!",Jonas Almroth
17959,Cannot copy text data from Win10 guest onto Mac OS host,Mac OS X,Windows,VirtualBox 5.2.18,2018-08-31T12:43:27Z,2018-08-31T12:43:27Z,"Host: MacOS High Sierra (10.13.5)[[br]]
Guest: Windows 10 64-bit; Guest Additions installed; bi-di copy&paste enabled[[br]]
VirtualBox Version: 5.2.18 !r124319 (Qt5.6.3) - latest as of Aug 28, 2018; latest Extenions installed[[br]]

Issue:

Copying any rich-text data from within the Windows 10 guest is not paste-able into the Mac OS host.  This is somewhat new behavior that was introduced with a clipboard crash fix in the release after version 5.1.32.  

Before the crash fix was made, pasting copied rich-text from the guest onto the host pasted the plain text extracted from the clipboard.  While not as ""perfect"" of a feature solution as being able to paste the full rich-text, plain text pasting would be welcomed back with open arms.  An ongoing discussion is here:

https://forums.virtualbox.org/viewtopic.php?f=8&t=86056&sid=ef11b0345dfa4278164ef407b4f4a626

While most of the commenters experiencing this bug are seeing the issue with Microsoft Office products, I also see it with Chrome and Firefox.  To reproduce, do the following:

1) within Win10 guest, browse to Google from within Chrome or Firefox, do a search for ""virtualbox""
2) highlight and copy the first found result, which is ""Oracle VM Virtualbox"".  I copied the entire result listing: title, URL, description.
3) hit CTRL+C or right-click/copy
4) mouse-out to Mac OS host and paste into any app such as TextEdit: no data is pasted.

The very inconvenient workaround that most people do is to paste the data into Notepad within the Win10 guest, copy that data, then paste into the host.  A nicer solution that still requires an extra click is to install the PureText app within Win10, which when used, strips the rich text and makes the plain text paste-able into the Mac OS host.

We would like to have the ability to paste any text data (as at the minimum plain text) into the host, which was working in VirtualBox up until and including 5.1.32.
",TonyRockyTiger
17967,Shared Folders from Linux Guest VM not accessible,Windows,Linux,VirtualBox 5.2.18,2018-09-02T03:45:25Z,2018-09-02T03:45:25Z,"After an update from Arch Linux 4.15.12-1 to 4.18.3 the use of shared folders in a Linux Guest VM is broken. The VirtualBox drivers were updated from 5.2.8 to 5.2.18.

During the build of my Arch Linux I performed the following steps:
I created a file /etc/modules-load.d/virtualbox.conf with three lines:

{{{
vboxguest
vboxsf
vboxvideo
}}}

Then I entered:

{{{
pacman -S virtualbox-guest-modules-arch
pacman -S virtualbox-guest-utils
systemctl enable vboxservice.service
reboot

}}}

My Arch Linux systems were running without problems for more than a year. I had several updates in between. After the last update I can’t access the files on the Windows host via shared folders.
Every time I boot I get the following error message in front of the login prompt:
vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.

My mount as a user in .bashrc doesn’t work:

{{{
sudo mount -t vboxsf D_DRIVE /home/peter/d
}}}


I have tried a lot to find a solution. I have renamed or removed the following files:

{{{
/usr/lib/virtualbox/mount.vboxsf
/usr/bin/mount.vboxsf
/etc/modules-load.d/virtualbox.conf
}}}


----

Then I have built a completely new Arch Linux VM system with Kernel 4.18.5. I know that since kernel 4.16 the modules vboxguest and vboxvideo are integrated into the kernel.
I don’t get the error message, but I can not mount as root:

{{{
mount -cit vboxsf D_DRIVE d
}}}


I have tried to blacklist the vboxguest module and install the drivers like above. Then I get the error message.

I think there is a bug in the vboxguest modules.
",PeterE
14040,Windows host-only adapter creation fails due to slow background processing,Windows,all,VirtualBox 5.0.0,2018-09-03T15:36:47Z,2018-09-03T15:36:47Z,"I was debugging why Xamarin Android Player could not prepare a VM for me and determined the failure to be in the host-only adapter creation, isolating the problem to this:

{{{
C:\Program Files\Oracle\VirtualBox\>VBoxManage.exe hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""int __cdecl handleCreate(struct HandlerArg *,int,int *)"" at line 66 of file VBoxManageHostonly.cpp
}}}

After some time spent in the debugger, I've found the real error to be `CO_E_CLASSSTRING` (Invalid class string), naturally returned by some `CLSIDFromString()` API call. Interestingly enough, the input GUID string contained garbage only.

Further debugging revealed a data race in `VBoxNetCfgWinCreateHostOnlyNetworkInterface()`. By the time `RegQueryValueExW(..., ""NetCfgInstanceId"", ...)` is called, the network device might still not be fully constructed by another process and this registry value might not be present yet. Because the result of this operation is effectively ignored, the program silently continues and the function fails only later due to the GUID being invalid.

A proof from Process Monitor - it took the system ~0.4 seconds more to write the value:
{{{
03:11:01.9426053	VBoxSVC.exe	15024	RegQueryValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	NAME NOT FOUND	Length: 144
03:11:02.3592881	svchost.exe	1140	RegSetValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	SUCCESS	Type: REG_SZ, Length: 78, Data: {F4CCBF3A-4C8B-4FE7-A659-725C3DF52E69}
}}}

Waiting in the debugger for a while before the `RegQueryValueExW()` call helped and I was able to create host-only network adapters fine.

Setting as priority minor because:
* it happened on a pre-release OS (Windows 10 preview build 10052)
* it happened on a pre-release VirtualBox (5.0.0_BETA1 r99371).

On the other hand, I submitted a ticket anyway because:
* the race is still a bug and can possibly crash the program, it might have been working with a little bit of luck only
* it seems the relevant VBox code has not been changed for the current beta
* I hear there was some refactoring done in Windows 10 regarding network adapters, this might show up later for more people",Jiri Hruska
17791,Guest VM becomes unresponsive after 2 or 3 days continuous uptime,Linux,Windows,VirtualBox 5.2.12,2018-09-04T18:09:22Z,2018-09-04T18:09:22Z,"Using CentOS 7.5.1804 host and Windows 7 guest with dual monitors full screen, USB mouse.

After the VM has been running continuously for about 2 or 3 days, the VM starts going into an abnormal wait state. The cursor can be moved with the mouse, but it changes from a pointer to a blue circle after clicking on something. At first, the ""wait state"" circle is short-lived, changing back to the normal pointer after less than a second. The problem gets worse over time and the cursor will begin to flash between normal pointer and blue circle a few times and then for longer and longer intervals. The longer I let it go, the more time it spends in the wait state. When the cursor is displayed as a blue circle, any button press on the mouse is ignored as well as key presses on the keyboard, although there was one time that I must have been clicking all over the place trying to get a response and on killing the VM, those clicks seemed to appear in the Linux host.

If I let the problem persist and don't reboot the VM, eventually the VM becomes completely unusable. The cursor stayed as a blue circle for over 30 minutes one time before I gave up and killed it. I have to reboot the VM to clear the problem and when I first started doing that, I would halt the VM and also reboot the Linux machine. More recently, I have only been shutting down the VM and restarting it. Earlier today, I shut down the VM and restarted, but noticed I was still having the problem. I shut the VM down again, exited the VB GUI console and made sure all VB processes were stopped, then started it back up. That cleared the problem.

When the guest system enters a wait state hang, CPU utilization on both host and guest still seem normal; no CPUs are pegged. When the guest seems to have entered a permanent wait state, it is still getting work done. I have had this happen when the Windows task manager was running and showing the CPU usage history. I had it set to slow updates, meaning it should update every 4 seconds but I was getting updates more like around 16 seconds.

I had been using the paravirtualized network driver and wondered if that could be a problem, so changed to the Intel PRO/1000 MT Desktop adapter with no change.

I first started having this problem in later versions of 5.0 on CentOS 6 and I had other problems with 5.1 so didn't run that for any appreciable amount of time. I have captured trace files of a hung VM if that could be useful to anyone.

I see similar reports on the forum about lost mouse clicks, and dual monitors may be one of the conditions required to reproduce.
",linus100
17971,Protocol error when using PHP rename over shared folders.,Linux,Windows,VirtualBox 5.2.18,2018-09-06T18:45:34Z,2018-09-06T18:45:34Z,"I am trying to rename/move a file that is living in a directory and I am giving a new name to the file and a new directory as well. Below is an snippet of such code:

{{{
rename($currentFilePath, $newname);
}}}

For some reason `rename()` is returning an error like the following:

> Protocol error var/www/html/editor/application/models/forms_model.php 455

I am trying now executing the command `mv` directly into the VM and this is the result:

{{{
$ mv /var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf ""/var/www/html/epa _editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf""
    mv: cannot move `/var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf' to `/var/www/html/epa_editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf': Protocol error
}}}

So apparently is a VBox issue with shared folders that has not been fixed. 

Related issues closed as ""fixed"":

 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/8463
 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/1321

The original issue was reported at SO (https://stackoverflow.com/questions/52209856/php-5-3-3-rename-function-fails-with-protocol-error) looking for help but it's not a PHP error but VBox.

  [1]: http://php.net/manual/en/function.rename.php
  [2]: https://stackoverflow.com/questions/19139434/php-move-a-file-into-a-different-folder-on-the-server
  [3]: https://www.virtualbox.org/ticket/1393",reynierpm
16753,Pen_Tablet.exe takes more and more memory when VM is on.,Windows,Linux,VirtualBox 5.1.22,2018-09-06T19:28:55Z,2018-09-06T19:28:55Z,"Tablet is Wacom CTL-470.[[BR]]
Driver version 5.3.5-3 (newest for this tablet).[[BR]]
Memory leak occurs on host while VM is running and tablet is connected. Process name is Pen_Tablet.exe (Tablet service for consumer driver). The process gains around 20K memory every second.[[BR]]
Host is running Windows 10 build 15063.250 (Creators update).[[BR]]
Guest is Arch Linux.[[BR]]

",snow
14272,"When VM run, Wacom_Tablet.exe consume much more memory",other,other,VirtualBox 5.0.0,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
17972,vboxsf module crashes guest OS after accessing host-side symlinks in shared folder,Windows,Linux,VirtualBox 5.2.18,2018-09-07T17:11:50Z,2018-09-07T17:11:50Z,"Host OS: Windows 7 x64 Enterprise[[BR]]
Guest OS: CentOS 7 x64, kernel 3.10.0-862.11.6.el7.x86_64

Scenario:
* A shared folder is configured, with host path ""d:\VirtualBox Shared"", under name ""shared"".
* HOST: Create a file symlink d:\VirtualBox Shared\2\test.txt pointing to a file C:\Temp\test.txt:[[BR]]
{{{
C:\>mklink ""d:\VirtualBox Shared\2\test.txt"" c:\Temp\test.txt
symbolic link created for d:\VirtualBox Shared\2\test.txt <<===>> c:\Temp\test.txt
}}}
* GUEST: try to access the symlink (in the last output, the link target is blinking, indicating it's inaccessible):
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
cp: cannot stat ‘/media/sf_shared/2/test.txt’: No such file or directory
flint@localhost / $ ls -l /media/sf_shared/2/test.txt
lrwxrwx--- 1 root vboxsf 0 Sep  7 18:39 /media/sf_shared/2/test.txt -> C:/Temp/test.txt
}}}
* HOST: Delete the link and replace it with a plain file:
{{{
C:\>del ""d:\VirtualBox Shared\2\test.txt""

C:\>copy nul ""d:\VirtualBox Shared\2\test.txt""
        1 file(s) copied.
}}}
* GUEST: try to acccess the replaced file again:
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
}}}

Result: guest OS crashes and reboots. My friend helped with analyzing the dump, and concluded that the crash occurred in the vboxsf.ko module. Most of the dentry->d_inode->i_op callback fields on this file have zero values (all of them, except for getattr and setattr).

The dmesg is attached; kernel core dump can be downloaded from here:
https://drive.google.com/open?id=1yFrDInJg8bgWXv-8kErs31W8Vn90aRYo",Konstantin Vlasov
17974,Unable to burn Audio CD,Linux,Windows,VirtualBox 5.2.18,2018-09-09T15:04:04Z,2018-09-09T15:04:04Z,"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

My machine has a DVD/RW drive that is connected to the Windows 7 guest via Passthrough.

I am able to burn data discs, but cannot burn audio discs. I checked the Virtualbo releases, and as of version 4.2 the changelog says that audio cd burning is supported.

How can I get this working correctly?

I have attached a log file from right after burning an audio cd fails.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance.",SloanUser
17975,Input Capture Fails,Linux,Windows,VirtualBox 5.2.18,2018-09-09T15:12:52Z,2018-09-09T15:12:52Z,"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

I but both Windows XP and Windows 7 as guests.

Whenever I make use of the Virtualbox control bar at the bottom of the screen, and then click back into my VM, the mouse and keyboard input are not captured by the VM. I need to click off onto my second screen and then click back into the VM for the input to be captured.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance.",SloanUser
17934,PulseAudio failed to init context,Linux,Linux,VirtualBox 5.2.18,2018-09-09T17:50:51Z,2018-09-09T17:50:51Z,"Host: Ubuntu 16.04[[BR]]
Guest: Ubuntu 16.04

updated VBox from 5.2.16 to 5.2.18;[[BR]]
installed extpack 5.2.18;[[BR]]
rebooted host;[[BR]]
start guest, get error as below;[[BR]]
install guest additions 5.2.18 in guest;[[BR]]
shutdown guest;[[BR]]
restart guest VM, get same error as before (log excerpt):


{{{
00:00:00.801653 Audio: Initializing PulseAudio driver
00:00:30.807983 PulseAudio: Failed to initialize context (state 5)
00:00:30.808320 Audio: Initialization of host backend failed with VERR_AUDIO_BACKEND_INIT_FAILED
00:00:30.808478 Audio: Initializing NULL driver
00:00:30.808523 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0)
00:00:30.808538 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message=""Host audio backend initialization has failed. Selecting the NULL audio backend with the consequence that no sound is audible""
}}}

As the error msg says there is no guest audio playing through the host.

Host audio itself is ok, i.e. all audio functions on host are intact.

",sunrider
17965,New Kali Linux Kernel 4.17.0 error,Linux,Windows,VirtualBox 5.2.18,2018-09-11T14:19:35Z,2018-09-11T14:19:35Z,"I updated virtualbox to the lastest version and then i upgraded my Linux host (Kali) and it has changed from kernel 4.15.0 to kernel 4.17.0... after this upgrade my Linux machine is unable to run graphical environment... i get a black screen for a long time and only some times it give me this message:

''' started update utmp about system runlevel changes '''

and it remains stuck like this. I switched to a new console (alt-ctrl-F1) for try to resolve somehow, but without results.
I updated the same version of Kali Linux (always kernel from 4.15.0 to 4.17.0) to another virtual host (under VMWare) and i didn't have problems, it runs fine.",Maxxx
14545,"""Failed to create host network interface"" on Windows 10",Windows,other,,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
17982,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,Windows,VirtualBox 5.2.18,2018-09-12T09:53:20Z,2018-09-12T09:53:20Z,"Hello, i have virtual machine with Win 7 Pro x64, on Win 10 x64 host. Last week it was fully functional, but when I started it today it shows me an error VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) and virtual machine stops working. When I start virtual machine in safe mode, it is working fine, but in normal mode don't :(
I' ve attached logs.
Thanks for any advice.",petrsk
17964,5.2.18 still not availale for RHEL / CentOS 7 -> fixed,Linux,other,VirtualBox 5.2.18,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
17985,VM stop working,Windows,Windows,VirtualBox 5.2.18,2018-09-13T08:01:33Z,2018-09-13T08:01:33Z,"Hi.
Very often a Windows 10 virtual machine crashes.
The error message says to open a ticket and send the log files.
From the logs I could not understand why.

I attach log files.

Best Regards
Paolo",paolo_len
17973,Graphical Glitch on Virtualbox Window Maximization,Linux,Windows,VirtualBox 5.2.18,2018-09-13T09:26:12Z,2018-09-13T09:26:12Z,"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

My machine has two monitors (1 VGA; 1 DVI). 

I run both Windows XP and Windows 7 as guests, with one running on each screen.  

If I minimize either VM via the virtualbox control bar I am correctly shown the Linux desktop. However, when I try to restore/maximize the VM by choosing it from the Linux taskbar, the VM desktop is restored with significant graphical glitches. I am forced to CTRL-F twice to take the VM out of fullscreen mode/restore fullscreen mode to correct it.  This is completely reproducible and happens 100% of the time, independent of guest OS. 

I have attached the following pictures (VM icons deleted to protect privacy):

1. Dual Screen Linux Desktop
2. Both VMs running
3. One VM Minimized
4. VM Restored with graphical glitch

I have also attached the log from the VM that was minimized/maximized from right after picture 4 was taken.

I purchased a Virtualbox Enterprise license on CDW so that this ticket may receive priority attention since I am a paying customer. Please feel free to call me via the information on my account if you need any confirmation of the CDW purchase.

Thank you in advance.
",SloanUser
17988,Change Group Fails - Forward-slash in VM name (host: Windows 64-bit),other,other,VirtualBox 5.2.18,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
17978,Menuet64 intelhda does not work anymore,Windows,other,VirtualBox 5.2.18,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
11919,"vboxmanager hostonlyif create --name """"",all,all,VirtualBox 4.2.14,2018-09-17T13:55:23Z,2018-09-17T13:55:23Z,"To enable the naming of 'hostonlyif' the create command needs to have a --name option such that (especially) on Windows host systems the name doesn't default to ""VirtualBox Host-Only Ethernet Adapter"", but instead can be set to something more useful.",Sauraus
17994,New fearture: Clone with blank disk,all,all,VirtualBox 5.2.18,2018-09-18T13:38:27Z,2018-09-18T13:38:27Z,I would like to propose a new feature. I would like to propose a ability to clone a machine with blank disk to have ability to create machine with the same settings.,xearo
17997,Re-ordering VMS is a royal pain,Linux,other,VirtualBox 5.2.18,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
16192,Virtualbox Windows clipboard integration causes problems copying in Excel,Windows,Linux,VirtualBox 5.1.8,2018-09-20T12:28:19Z,2018-09-20T12:28:19Z,"Host: Windows 10 1607 14393.447 (+ all available updates up to mid-November 2016) with Office 2016 (+ all available updates up to mid-November 2016; Excel version 16.0.7466.2038)
VirtualBox: 5.1.8 r111374
Guest VM: Linux Mint

When, and only when, a guest VM is running (but even if the clipboard integration is disabled for that VM) then copying data in Excel 2016 on the host frequently gives the error ""There's a problem with the clipboard, but you can still paste your content within this workbook.""

How to reproduce: run Excel 2016 on the host, and start the guest VM. In Excel 2016 on the host, select a cell with some data, and repeatedly press CTRL+C - roughly 1 in 4 attempts will cause the above error - highly reproducible. With the VM shut down, CTRL+C on Excel on the host will never give this error.

Note that Excel has long been affected by applications that access/lock the clipboard. It seems that MS have recently tried to mitigate, and changed the message in Excel. I suspect it is possible older Excel versions may also be affected, but if so, the error will be slightly different: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_win10/clipboard-problem-in-excel-2016/224b2a59-8a0c-4897-baba-a481dd06e085?page=5


",hakster
18003,Error -104 in supR3HardenedWinReSpawn,Windows,other,VirtualBox 5.2.18,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
18004,Can't restore state of Windows XP guest machine when playing games,Windows,Windows,VirtualBox 5.2.18,2018-09-23T08:33:53Z,2018-09-23T08:33:53Z,"Hello.

I have a '''Windows XP SP3 guest machine'''. It's running fine and I can pause it, close (with saving state option) and restore it when I'm in desktop.

When I play games and I want to do the same, '''I'm getting error (unknown software exception) in application in localization'''. 

'''So what I'm doing is:'''
1. Start the game.
2. Pause machine once games has loaded.
3. Close machine by saving its state.
4. Open machine with its saved state.

I tried two games: Superbike 2001 and International Rally Championship. Both produce similar error.",Mtik
18009,Guest screen size is not same as window size HiDPI @1.5 Linux host,Linux,Windows,VirtualBox 5.2.18,2018-09-25T13:56:06Z,2018-09-25T13:56:06Z,"Host openSUSE Tumbleweed 2018-09-23
VirtualBox 5.2.18_SUSE r123745
Qt 5.11.1
HiDPI@1.5

Guest Windows 10
VirtualBox additions installed
2D accelerate
3D accelerate
VirtualBox screen scale 100%
Windows display scale 150%

Guest system display is smaller than the window, leaving black space around. Mouse pointer is wrongly mapped to the whole window instead of guest system display area.

[[Image(https://i.imgur.com/nPo9esr.png)]]",Guo Yunhe
17993,Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) while debugging in guest Windows,Linux,Windows,VirtualBox 5.2.18,2018-09-26T03:43:32Z,2018-09-26T03:43:32Z,"Whenever I try to debug application and/or attach debugger to running process, the machine crashes with Guru Meditation. Crashes on msvc 2010 and msvc 2015.",Marcin Wichtowski
16515,DxgiOutputDuplication::AcquireNextFrame() does not work after Windows 10 1607 update,Windows,Windows,VirtualBox 5.1.14,2018-09-26T12:57:59Z,2018-09-26T12:57:59Z,"I used to think this has been broken by VirtualBox update. But I have tried several versions, none of them work after Windows 10 1607 update. This API returns correct value, but the frame is just empty.
The API works well before 1607 update, but it also works well on several regular PCs. So it looks like something is wrong in VirtualBox driver or at least an incompatible behavior.

I have tried only on Windows host, I cannot tell whether it also stops working on other hosts.

You can try a MSDN sample at https://code.msdn.microsoft.com/windowsdesktop/Desktop-Duplication-Sample-da4c696a.

On VirtualBox instance https://drive.google.com/open?id=0B0OFNI4uoZGRNzdkSkZVcUdqOEk
On Thinkpad X1 forth generation https://drive.google.com/open?id=0B0OFNI4uoZGRdTFfbzctSml1RXc",Hzj_jie
18013,Suggestion: ability to enable/disable 2nd Virtual Screen in Full-screen mode,Windows,all,VirtualBox 5.2.18,2018-09-27T08:52:13Z,2018-09-27T08:52:13Z,"Tested on Windows host. If a 2nd Virtual Screen is present in the vm settings, it can only be enabled and disabled while the VM is running if the vm is not in Full-screen mode. This can be done from the ""Virtual Screen 2"" menu item in the ""View"" menu. Once Full-screen mode is active, the ""Enable"" menu item from this menu disappears and only ""Use Host screen 1"" etc are available.

To disable ""Virtual Screen 2"", you must now first exit Full-screen mode, uncheck the ""Enable"" menu item that is then present in windowed mode, and then re-enter Full-screen mode. 

The suggestion is to show the ""Enabled"" menu-item for the Virtual Screen menu's also in Full-screen mode, so that exiting and re-entering Full-screen mode would no longer be necessary. ",Jeroen V
18015,A forwarded Dectel CI692 doesn't work if the controller is USB 2.0,all,Linux,VirtualBox 5.2.18,2018-09-27T14:30:26Z,2018-09-27T14:30:26Z,"When I use USB forwarding and a virtual USB 2.0 controller to attach a Dectel CI692 smart card reader to a CentOS 7.5 guest, attempts to use the smart card fail, with an error that traces back to ""libusb_error_timeout"" from PC/SC on the guest. The problem seems specific to this narrow configuration. Here's what I've discovered by testing various combinations of things:

* The problem occurs on both a 2017 MacBook Pro running High Sierra and a Dell OptiPlex 7050 running CentOS 7.5 as the hosts.
* The problem occurs whether the real USB port on the host is USB 2.0 or USB 3.0.
* The problem doesn't occur if I use a virtual USB 1.1 controller or a virtual USB 3.0 controller. For now, this is my workaround.
* The problem only occurs with certain smart card readers. When I tried it with an HID Omnikey smart card reader instead, it worked fine.
* The problem doesn't occur if I use the reader in a real USB 2.0 port with CentOS 7.5 on bare metal.
* The problem doesn't occur if I just run ""pcsc_scan""; it sees the smart card fine. The problem only occurs when I try to use the keys on it, such as by running ""ssh-keygen -D /usr/lib64/pkcs11/libcoolkeypk11.so"".

Steps to reproduce:

* Install CentOS 7.5 in a guest
* Set the guest to use a USB 2.0 controller, and forward the Dectel CI692 to it
* Insert a smart card into the Dectel CI692
* Install the packages ""epel-release"", ""pcsc-tools"", and ""coolkey"" in the guest
* Run ""ssh-keygen -D /usr/lib64/pkcs11/libcoolkeypk11.so"" in the guest

Expected result: the public keys from the smart card should be printed.
Actual result: the command fails with the message ""cannot read public key from pkcs11"".

Attached are two logs: one with a USB 1.1 controller, where the command works correctly, and one with a USB 2.0 controller, where the problem occurs. Both logs were saved immediately after running the ssh-keygen command.",jsible
17830,Virtual machine detaches after startup in full screen,Mac OS X,Windows,VirtualBox 5.2.12,2018-09-28T00:43:32Z,2018-09-28T00:43:32Z,when I start windows 10 or it restarts because of a BSOD or update. it will detach from the VM window while in full screen.,Neptune BSC LLC
18017,"Linux host, Windows guest: screen resolutions limited and fix messes up the pointer",Linux,Windows,VirtualBox 5.2.18,2018-09-28T05:16:57Z,2018-09-28T05:16:57Z,"1) Windows 10 VM exposes only resolutions lower than my native one. I worked around the problem by issuing this command:


{{{
VBoxManage setextradata global GUI/MaxGuestResolution any
}}}

''However'' - and this is problem 2) - once the VM was using my native resolution, setting the scaling within my Windows 10 Guest to 150%, and especially to anything higher, causes pointer strangeness in Word 365. For, once the pointer changes - changes upon mouse-over of an icon in the Word ribbon - it does not, for some time or occasionally permanently, change back.

Virtual Box 5-2
Linux Mint 19 x64 Cinnamon

An existing bug report contains the first of the two problems that I have detailed; however, I am afraid that I cannot manage to re-locate that report.",JN
12048,No OpenGL Support for Windows 8,Windows,Windows,VirtualBox 4.2.16,2018-09-29T13:25:25Z,2018-09-29T13:25:25Z,"Host: Windows 7 64 bit
Guest: Windows 8 32 bit
Problem: No opengl GL support.

I'm trying to get accelerated opengl in my Windows 8 guest. All I get is the Microsoft Software OpenGL 1.1 driver. 

Additional Info:
- guest additions installed and selected the D3D support during installation
- 3D hardware acceleration enabled in the VM settings
- Direct 3D 9 acceleration works

To make sure it's not a problem with my host I installed Windows 7 32 bit as a guest. In this virtual machine the OpenGL Adapter of the host seems to be passed through to the guest.

I will attach a log for the windows 8 guest where OpenGL is not working.",muhkuh
18011,Video capture doesn't work after upgrade from 5.1.38 to 5.2.18,Mac OS X,other,VirtualBox 5.2.18,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
18000,inaccessability of virtual box guest controls on nvda,Windows,all,VirtualBox 5.2.18,2018-10-01T22:54:56Z,2018-10-01T22:54:56Z,"the guest controls that contains in running machine window is fully unaccessable for nvda screenreader (nvaccess.org)
this impacts 99% of controls in machines window (machine menu, shutdown dialog, settings dialog, error dialogs...)
settings dialog unaccessable only when it opened from machine window. if it opened from main vbox window, it fully accessable.

also I have sugestion to fix it:
the nvda screenreader has an a special library, called nvda controller client (https://github.com/nvaccess/nvda/tree/master/extras/controllerClient)
this library allow apps to send text directly to screenreader.
I know that every gui item has focus event.
If VirtualBox Gui Application will send to nvda names of dialogs and menu items, possible without any status information, it will become accessable without any big interface changes.
I'm also starting developer and I know that it's very easy to implement, but, if it will be implemented, vbox become mutch more accessable.

I placed the same request in main VirtualBox forum and in VBoxDev list, but no get any response.",ilyapashuk
18020,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your system",Windows,Windows,VirtualBox 5.2.18,2018-10-01T23:16:53Z,2018-10-01T23:16:53Z,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your windows 10 machine

Scenario to reproduce the issue.

1. reboot the laptop/system
2. try to ping any static IP 192.168..
3. you will see ""destination host unreachable"" for the 1st packet
4. result:""destination host unreachable"" for first ICMP packet 

Manual solution:
1. reboot the machine
2. go to control panel/network and sharing center
3. then go to change adapter settings
4. disable ""virtualBox Host-Only Network""
5. enable  ""virtualBox Host-Only Network""
6. Now ping any static IP
7. results: No error. Works great


",raza
15004,Can't compile Virtual Box on Mac OS X El Capitan,Mac OS X,all,VirtualBox 5.0.12,2018-10-02T08:40:00Z,2018-10-02T08:40:00Z,"Hello there,

  I made the Virtual Box source code checkout (svn ....), then I followed the instructions to build Virtual Box on Mac OS X (as from here: https://www.virtualbox.org/wiki/Mac%20OS%20X%20build%20instructions ), but the configure has instructions for older versions only, so it can't ""detect"" the new version, so I modified the configure and ""hardcoded"" the ""detection"" of 10.15, the path to Xcode and the MacOSX10.11.sdk path, and added the path to the openssl lib with --with-openssl-dir=..., then the configure script executed ok, but when I executed kmk command, there was no kmk executable, so I made a checkout of the source code as instructed here http://trac.netlabs.org/kbuild/wiki/Download, but I had trouble compiling it, so I downloaded the source code of  Virtual Box (VirtualBox-5.0.2.tar.bz2), extracted, modified the configure file, executed it, then issued kmk, and it failed saying that I had not a compatible Xcode, then I edited the Config.kmk, ""hardcoded"" the Xcode version (7.2), executed it again, then it started building, but failed because it was not able to figure out the compilers (wanted the gcc ones version 4.2).
Please, someone there update a Mac machine to OS X El Capitan and Xcode to 7.2 version and update the kbuild files to deal with Xcode 7.2.
Also, Xcode now has multiples platforms sdks, so the path to the Mac OS X Sdk is now a bit longer.",Enclle
18026,Detach GUI Option on Window close (suggestions for improvements),Windows,Windows,VirtualBox 5.2.18,2018-10-02T09:27:49Z,2018-10-02T09:27:49Z,"Hi I am a Windows user and I have a suggestion,
 when you close the virtualbox window with the X (top right to close a window) you can also have the option to ""Detach GUI"" This would be much easier to use this way!
Thanks a lot for listening to my suggestion :)",adamw
18025,Can't launch VirtualBox 5.2.18-1 on fedora 28.,Linux,other,VirtualBox 5.2.18,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
18028,"Mouse wheel scrolling usually not working, cursor off, hotkeys not sent to vm, after moving to edge of screen",Linux,Linux,VirtualBox 5.1.0,2018-10-03T14:20:07Z,2018-10-03T14:20:07Z,"This is not a new issue but I couldn't find a related bug report that's still open.

I believe the following issues may be related.

A) Mouse wheel scrolling usually doesn't work while ""mouse integration"" is not active (input captured). It always works fine at first, right after clicking or hitting Ctrl in the VM window to capture both mouse and keyboard. At some point, it stops working. Hitting Ctrl to release the mouse reveals that the host's mouse cursor is usually about half a screen away from the VM's cursor. After moving the host's cursor back to where the VM's cursor is and then clicking to recapture the input, it works again. But not for long.
This is happening so often that I tend to not use the mouse wheel at all and use the good old scrollbar buttons instead. Unfortunately, some desktop environments (Gnome/GTK) have lost the scrollbar buttons for whatever reason. In that case, the combination of a temporarily broken scroll wheel *and* a broken scrollbar makes it rather difficult to navigate through content (vertically and horizontally).

B) Whenever a VM is started, mouse integration is active by default, which means the VM's cursor is moved together with the host's cursor as long as it's within the VM window without requiring the user to click into the VM window first.
Unfortunately, the cursor is often way off. Sometimes even a third cursor would fit between the host's and the VM's cursor. I'll attach a screenshot.
This is one of the reasons why I usually disable mouse integration after starting a VM. But then, the first issue happens.

C) While mouse integration is active, hotkeys often don't work, i.e., they're not sent to the VM. For example, after starting a VM, you'd hit Alt + Tab while working inside the VM and you get the host's task switcher showing your open Virtualbox windows. What you actually wanted to do is switch windows inside the VM.
You have to first click somewhere inside the VM and then hit Ctrl to temporarily capture the keyboard and send hotkeys to the VM. I say temporarily because at random times, apparently when moving the cursor to the edge of the screen (but strangely not always), it stops working again and the next time Alt + Tab is used, it's sent to the host again.
This is the main reason why I have to disable mouse integration after starting a VM and then only interact with the VM with mouse and keyboard captured and locked inside the VM window.

D) This is just a minor glitch. I don't remember when I first noticed that but it wasn't always like this. The user interface bar at the top of the screen gets stuck, covering that area in the VM. That's particularly annoying if the DE's panel (task bar) is at the top of the screen. This is solved by moving the host's cursor over the user interface panel and back in the VM, then it disappears normally.

E) This is not a glitch, just a note: When mouse integration is disabled but the input controls are *not* captured (e.g., VM on one monitor, host applications on another monitor), most keystrokes are still sent to the guest system (of course no hotkeys) while the VM window is focused. This may be counterintuitive because not having clicked into the VM window means that the user does not want to interact with it. Accidentally moving the host's mouse to the VM window may change the focus and then hitting space may active a button in the guest instead of inserting a whitespace in a host application window.

If it makes a difference, most VM windows are used in full screen mode. There may be a second or third monitor with other VMs or host application windows running.

Again, I am under the impression that the issues described above may be symptoms of one general issue. It appears that the VM window sometimes loses the input controls while the user is working with the VM or they get ""out of sync"" unexpectedly.

This behavior has been seen on different systems, but most recently on Debian, currently running Virtualbox 5.1.38. Some guest systems are running Fedora 28.

",basic6
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,other,VirtualBox 5.2.18,2018-10-06T00:40:34Z,2018-10-06T00:40:34Z,,turi
18002,Heap corruption in VBoxSVC.exe leading to a crash (possibly due to double free),Windows,Linux,VirtualBox 5.2.18,2018-10-08T14:28:45Z,2018-10-08T14:28:45Z,"I have encountered a crash of latest VBoxSVC.exe 5.2.18.24319 on a Windows 10 host while running two VMs in parallel (one Windows VM and one Linux VM). The crash happend while I was accessing internet resources from the Linux VM.

I have collected a crash dump which indicates that the crash is caused by a heap corruption in VBoxSVC.exe while calling free function from msvcr100.dll. So, this looks like a double-free issue in VBoxSVC.exe.

I could not find a way to reproduce this crash. Usually, I run 3 or 4 VMs at the same time but VBoxSVC never crashed but this time just with 2 VMs and no extensive CPU load (just internet browsing) and it crashed.

I'm attaching the full log from Linux machine. For the crash dump, I can post it but since it is related to potential double free issue in VBoxSVC which are sometime a security vulnerability I prefer to confirm with you first that it is ok to post here.

",idrassi
18034,Windows XP Guest Random Aborting,Linux,Windows,VirtualBox 5.2.18,2018-10-08T15:06:28Z,2018-10-08T15:06:28Z,"Hello,

I am running Ubuntu Linux 18.04 LTS with all the latest patches installed.

Linux xxxxxxx 4.15.0-34-generic #37-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I installed Virtualbox/Extension Pack/Guest Additions from virtualbox.org; version 5.2.18 r124319 (Qt5 9.5)

When running a Windows XP guest, the machine randomly aborts. I have attached the Virtualbox log file. 

The aborting generally happens when running Lotus 123, which is a spreadsheet program. I have tried the standard ideas of turning off 3D/2D acceleration, but the crashes continue to happen. 

Any/All help is appreciated.

Thanks.",SloanUser
16829,Switching a guest window to full screen with more than one guest display hides other guest windows,Mac OS X,Windows,VirtualBox 5.1.22,2018-10-09T05:03:53Z,2018-10-09T05:03:53Z,"https://forums.virtualbox.org/viewtopic.php?f=8&t=82004

The last version that this worked was 5.0.4 and even then it was a little buggy (not expanding past the dock and other weirdness).

If you are running a guest with two virtual displays, when you expand one display to full screen (green icon), it will hide the other virtual windows. When you 4-finger-up to manage windows, you only see ""VirtualBox VM"" instead of the guest name. In 5.0.4- you saw to entries labeled ""vm guest name 1"" and ""vm guest name 2"".

Tried on most versions since 5.0.4 including 5.1.22 with the same behavior. Tried on El Capitan (10.11.6) and Sierra (10.12.5). ",Shonn
18036,MachineTools toolbar buttons disappear after starting VM from Windows Explorer,Windows,all,VirtualBox 5.2.18,2018-10-09T19:16:36Z,2018-10-09T19:16:36Z,"Normally in the VM VirtualBox Manager (VirtualBox.exe) I have the Machine Tools toolbar showing both Details and Snapshots. However if I run a VM by double-clicking the .vbox file in Windows Explorer when VirtualBox.exe is not running, next time I run VirtualBox.exe those buttons are not showing on the toolbar. In particular, before I have in VirtualBox.xml
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""Details,Snapshots""/>
but after, I have
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""None""/>",mf86a
18038,Mouse Integration Bug Windows 10 April 18 Host - Pointer In Wrong Location,other,other,VirtualBox 5.2.18,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
18042,[X11] Virtual machine window WM_NAME name and class being set too late,Linux,all,VirtualBox 5.2.18,2018-10-11T04:39:56Z,2018-10-11T04:39:56Z,"Under X11 VirtualBox sets the virtual machine window's WM_NAME name and class too late, interfering with window manager rules.  ""Too late"" meaning that the virtual machine window has been displayed and handled by the window manager, *then* the WM_NAME name and class is set.

The virtual machine window class was being set correctly with VirtualBox 5.2.6, however all versions thereafter have not worked correctly.

After looking at the code in `src/VBox/Frontends/VirtualBox/src/runtime/UIMachineWindow.cpp void UIMachineWindow::prepare()` it appears the X11 window class-setting code was moved in 5.2.8 from the beginning of the `prepare()` function to the end. This appears to be the root cause of this issue.",Will B
18043,Virtual box starts up in the background,other,other,VirtualBox 5.2.18,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
15900,Remote Desktop (RDP) into Windows10 (64-bit) Host Crashes Full Screen Guests 5.1.4,Windows,Windows,VirtualBox 5.1.4,2018-10-11T16:52:46Z,2018-10-11T16:52:46Z,"I've had multiple full-screen VMs crash twice now upon getting connected to my Windows 10 64-bit host via the standard Windows Remote Desktop client. The sequence of events scenario was similar both times: I'll typically leave a few guests running full-screen in the background, remote into the host while away, reconnect to the local host console upon returning, then remote in again next day. On the 1st remote connection, the full-screen guests that were left running flash the hosts Windows taskbar, and switching to them restores the full-screen display. Upon the 2nd or so remote connection, the full-screen guests that were left running again flash the host's Windows taskbar, and clicking then to switch to them causes them to crash with (latest example):

[Running] - Oracle VM VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x000000005B16C025 referenced memory at 0x000000000D41E000. The memory could not be read.

Host: Windows 10.0.10586 (64-bit), Dell Precision T5500 36GB RAM
Displays: (NVIDIA GeForce GTS 240)
Primary (Dell 2408WFP) 1920x1200
Extended (Samsung TV) 1920x1080
Guests (all configured for a single display):
Windows 10
Windows Vista (2 CPUs)
Windows XP
(not sure about Linux/Mint)

In all cases, the Remote Desktop client is set to start full-screen on 1 display. Not sure if this could be the reason or if it could be caused by the host having two different screens (speculation of course). However, simply connecting to a host should not crash guest VMs.
",CM7
17735,Guru crash with Redox 0.3.5,all,other,VirtualBox 5.2.10,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
15802,"[Regression] No microphone, Windows Guest, Linux Host.",Linux,Windows,VirtualBox 5.1.2,2018-10-14T12:00:32Z,2018-10-14T12:00:32Z,"Linux Host

Ubuntu 16.04

Kernel 4.7.0-040700-generic

Guest: Windows 8.1 (also appears to affect any other guest)

Audio Controller: Intel HD Audio

Microphone is enumerated by the guest, but it is always silent. On occasions fiddling with microphone driver enumeration (i.e. toggling ""Show unplugged recording devices"" several times, going to its properties, etc) can even crash VirtualBox (rare, happened to me only twice).

PulseAudio shows VirtualBox has requested and received microphone and speaker.
I've also tried the ALSA driver, same result. Couldn't try OSS driver (immediately aborts VM, didn't look much into it; I assumed either I had a missing dependency or the OSS device couldn't be grabbed)

I tried AC97 audio controller but Windows 8.1 won't install drivers for it.

Useful info:
* Problem shows in official virtualbox-5.1_5.1.2-108956-Ubuntu-xenial_amd64 (using matching extension pack & Guest additions)
* Problem persists in test build VirtualBox-5.1.3-110032-Linux_amd64.run (using matching extension pack & Guest additions)
* It works correctly in virtualbox-5.1_5.1.0-108711-Ubuntu-xenial_amd64.deb

More info:

These users seem to be affected by the same problem:
https://forums.virtualbox.org/viewtopic.php?f=7&t=78797",dark_sylinc
18045,glGetFramebufferAttachmentParameter missing in libGL.so.1,Windows,Linux,VirtualBox 5.2.18,2018-10-17T08:08:26Z,2018-10-17T08:08:26Z,"I run a linux guest in a Windows 10 host.

In the guest, the OpenGL function glGetFramebufferAttachmentParameter is missing in /usr/lib/virtualbox/additions/libGL.so.1

Due to this, I get linker errors in many packages and can't enable 3D acceleration.

Is this something you can support? What is the status on this?
",Mikael Djurfeldt
18041,guest suse leap 15.0 could not be started after kernel update openSUSE-2018-1140,Windows,Linux,VirtualBox 5.2.18,2018-10-17T08:11:08Z,2018-10-17T08:11:08Z,"With VirtualBox 5.2.18r on a Windows 10 host my Open Suse Leap Linux updated
the kernel with openSUSE-2018-1140 and from then on the suse guest couldn't be
started again.
Attached you'll find a hardcopy of the Startup sequence Messages.

An native Installation of Suse, including the kernel 4.12.14.lp150.12.19, 
works w/o any issues.",guenni
18051,My screen is all discombobulated! SOS,Windows,Linux,VirtualBox 5.2.18,2018-10-17T08:20:08Z,2018-10-17T08:20:08Z,"When I start my VM for Linux Mint, my laptop cant seem to get
the display right. All I can see is a bunch of lines that seem
to make up my screensaver and I see my mouse divided into approx.
12 different slices along the lines that seem to make up my 
screensaver. I use the VM as a programming environment for my 
CS class and I have project due tomorrow but can't get it to run
so I can add the finishing touches... Please help. I would add a
pic if a knew how
",Diddy
18058,Installation fails > Failed to send WATCHDOG=1 notification message: Connection refused,Linux,all,VirtualBox 5.2.20,2018-10-17T18:00:02Z,2018-10-17T18:00:02Z,"Hi,

I'm on openSUSE Tumbleweed.  When I use the '''5.2.20/All distributions''' bits, my desktop has a brain freeze.  I get the errors below.  Using the '''5.2.18/All distributions''' bits does not cause this issue.

When this happens, I cannot properly shutdown my machine.  I have to hit the power button.

I tried it twice.  The second time after a clean boot.

My workaround is to revert to '''5.2.18'''

The strange thing is my laptop is also running Tumbleweed and I had no issue going to 5.2.20.

Let me know what debug information I can provide.  I know this information is a bit .. sparse to act upon.  ;)  

Thx!

{{{
[ 1518.687793] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Connection refused
[ 1588.685640] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1698.682197] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1768.680023] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
}}}
",Pablo Sanchez
18060,virtual computer disk removes,Linux,Windows,VirtualBox 5.2.20,2018-10-18T11:52:52Z,2018-10-18T11:52:52Z,"after a wile de virtual computer disk removes it self from the settings.
And need to reinitialize from the disk section menu. 
Like the data setting are removed.
",Nadvt
18062,VirtualBox Application Error - memory could not be read,Windows,Linux,VirtualBox 5.2.20,2018-10-18T15:34:24Z,2018-10-18T15:34:24Z,"Updated from 5.2.18 to 5.2.20 last night (with Guest Additions) and left for the day.  Since this morning, two similar crashes - the second is below and attached.  I've updated to Win10 Pro (1809) last week (from previous patch level).  Some additional information that I suspect as relevant ... Dell laptop with Dell D1000 USB3.0 Dock (DisplayLink driver).  Main video, Wired Internet, and USB is run through the dock.

The instruction at 0x00007FFF24DBD680 referenced memory at 0x0000000000000010. The memory could not be read.",Brewsters
18068,NAT process infinite loop call `poll` function,Linux,Linux,VirtualBox 5.2.20,2018-10-22T07:42:56Z,2018-10-22T07:42:56Z,"Host machine: Fedora 28
Guest machine: Windows 10

My guest system is Windows 10 and using NAT network, and Windows 10 system suddenly unable to access the Internet at some point, but my host machine can access the network normally. I using Wireshark capturing some ARP data flow in Windows 10:

{{{
1   0.000000 PcsCompu_7a:1a:df → RealtekU_12:35:02 ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    2   0.207297 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    3   3.718693 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    4   4.500012 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    5   5.500048 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    6   6.719889 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    7  10.721331 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    8  11.499537 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    9  12.500007 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   10  15.499582 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   11  16.721794 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   12  17.500389 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   13  18.500008 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   14  21.499517 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   15  22.725696 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   16  23.499997 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   17  24.499501 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   18  27.499508 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   19  27.982749 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   20  28.500004 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   21  29.500001 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   22  34.985277 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   23  35.500502 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   24  36.500023 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   25  38.248133 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   26  42.249642 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   27  42.999528 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   28  43.999519 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   29  47.235338 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   30  48.000015 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   31  49.000018 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
}}}

IP 10.0.2.2 is NAT's gateway address, as you see, my Windows system send some ARP broadcast packet to find 10.0.2.2's MAC address, but not recive any response packet.

At the same time, in my host machine, the `NAT` process occupies a lot of CPU resources. I using `strace` command tracing `NAT` process:

{{{
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
.......

}}}

as you see, NAT process infinite loop call `poll` function",lu4nx
16818,VirtualBox Drag and drop failure on Windowd 10,Windows,Linux,VirtualBox 5.1.22,2018-10-24T09:02:15Z,2018-10-24T09:02:15Z,"VirtualBox Drag and drop failes on Windowd 10 with the following error:

Drag and drop operation from host to guest failed.
Drag and drop error from host (VERR_PATH_NOT_FOUND).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

",Sciex
14349,Important Bug in Unscaled HiDPI Support on Windows8.1/10 Guest,Mac OS X,Windows,VirtualBox 5.0.0,2018-10-24T19:41:33Z,2018-10-24T19:41:33Z,"VirtualBox Version: 5.0 r101573(official release version)[[BR]]
Host Version: OS X 10.10.3 with MacBook 12`(Retina HiDPI 1280*800 default setting)[[BR]]
Guest Version: Windows 8.1 / Windows 10 '''but not''' Windows 8[[BR]]
[[BR]]


'''What's wrong:'''[[BR]]

After installed VirtualBox GuestAddition(with build-in version or  5.0.0 RC1,RC2,RC3 or whatever the latest 5.0.1 test version),the Unscaled HiDPI Support was broken.The entire monitor image distortion where the mouse pointer are.Look at the screenshot(which means what I see from screen).
[[BR]]

What I see:[[BR]]

[[Image(http://img.hb.aicdn.com/732c6e18a2fd38e4f46b93fd678c9bb0dbfa64849196d-iV9kkv_fw658)]]
[[BR]]
But at the same time ,use the '''build-in''' screenshot(which means use the VBox toolbar option),everything '''looks''' OK.

[[BR]]
What VBox screenshot show:[[BR]]
[[Image(http://img.hb.aicdn.com/72dbce851d5a0d23713712e204d933a1a420ed2910c78a-UnofOO_fw658)]]
[[BR]]

'''What I do:'''[[BR]]

After installed the older GuestAddtion(VBoxGuestAdditions_5.0.0_BETA4,link here: [http://download.virtualbox.org/virtualbox/5.0.0_BETA4/VBoxGuestAdditions_5.0.0_BETA4.iso])[[BR]]
it works OK! But this GuestAddition may cause WPF-Application crash(include VS2015 or some Metro Apps),and the latest version GuestAddtion(VBoxGuestAdditions_5.0.1-101689.iso) also have this bug.So there are no way to keep both useable and Retina support...Therefore I think maybe some commits after that '''BETA4''' reinsert this bug.....
[[BR]]

'''What I guess:'''[[BR]]

Windows 8.1/10 use the new DPI-Aware API([https://msdn.microsoft.com/en-us/library/windows/desktop/dn469266%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396])[[BR]]
which may behave differently from Windows 8.[[BR]]
So this may be fixed by find the bug commit or add some special judgement code? I don't sure this may happen only in OS X Guest or All platforms.But i'm hopefully to fix this..
[[BR]]

'''Attach are here.Include the VBox Guest and Host.'''",DreamPiggy
18040,Failing to attach USB device,Windows,Windows,,2018-10-25T10:01:59Z,2018-10-25T10:01:59Z,"Not able to attach a USB device to VM with USB over Ethernet Connector ([https://www.eltima.com/products/usb-over-ethernet/]) installed on the host.

Virtualbox is the latest version.

Host and guest are both Win7 64-bit.

If I uninstall USB redirection software from the host, then everything works fine.

Attached a screenshot of the error message.",redhotchili
18082,still doesn't work copying and pasting some words with shift + insert,Windows,Linux,VirtualBox 5.1.38,2018-10-25T12:45:57Z,2018-10-25T12:45:57Z,"Hi experts,

I tried that above after installing each GuestAddition at 3 version, but all failed. The version are 5.1.38, 5.1.28, 5.1.24 for windows host.

when input shift + ins, F was displayed only. 
I don't know why it occurred.

My computer is ThinkPad X270 installed Win10 latest patch.

Br,
Tomio

",Tomio
18047,VirtualBox Icon Not Centered,Mac OS X,other,VirtualBox 5.2.18,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
18053,Query Installed Guest Extensions Version,Linux,other,VirtualBox 5.2.18,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
18056,Linux VM fails to PXE boot on MacOS host,other,Linux,VirtualBox 5.2.20,2018-10-26T00:02:00Z,2018-10-26T00:02:00Z,"Virtualbox (5.2.18) + extensions installed on a 2017 iMac with MacOS (OSX) 10.14 Mojave and it seems impossible to make the VM get an IP address from my DHCP server during PXE booting.

I tried all possible combinations for configuring the network adapter for the VM but still it fails to get the DHCP IP. I even checked the DHCP server logs and I am sure that the IP used by the VM never reached it.

The config I was expecting to be working:

    Bridged Adapter: en0 (this is the LAN of the iMac)
    Adapter Type: one of Intel ones (but tried all 6 possible alternatives)
    Promiscous Mode: deny
    MAC Address: a generated one
    Cable Connected: Checked.

I am not sure if this problem is specific to MacOS Mojave or the Ethernet board in iMac as I did not had the chance to test with other versions.

Initially posted on https://forums.virtualbox.org/viewtopic.php?f=8&t=89792",sorin
18061,"Choosing 64-bit Windows 7 machine, once I launch it the OS is 32-bit",other,other,VirtualBox 5.2.20,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
18063,Disk encryption causes guest to crash,other,other,VirtualBox 5.2.20,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
18076,Linux Mint 19 guest using Touch Keyboard in Windows 10 host not working with some keys,Windows,Linux,VirtualBox 5.2.20,2018-10-26T00:42:48Z,2018-10-26T00:42:48Z,"I am having problems with Windows 10 the full touch keyboard not the basic one with the arrow keys, Shift and space bar not working and it is in USB Tablet mode. The strange thing is that basic touch keyboard work with space bar, but arrow keys still not working.",Motoko
17354,Can't setup Host-Only Network Adapter on Windows 10 Client,Windows,Linux,VirtualBox 5.1.30,2018-10-26T04:03:44Z,2018-10-26T04:03:44Z,"Hi,


'''[How to reproduce it]'''
From fresh installation, installation was ok, no errors, the problem began when I tried to setup the missing IP and network mask for the Host-Only Network Adapter, first thing I noticed is that upon setting up the values VBox was resetting the values every time and clean the values up.

-I'm using VirtualBox Version 5.1.30 also tried with 5.2.0 for Windows
-I have Windows 10 Pro running on a Dell Precision, 16GB RAM, 64-bit, core i7 vPro
-I'm trying to host a Linux VM that contains some web application, so I can access them via u.r.l. , this is a RedHat VM

After this I tried a lot of things to make the Host-Only adapter work

- I had 3 VM, I remove 2 of them and test 1 with one
- Remove every single VM and try to set the values
-Try to set the values using TCP/IP v4 properties in the actual Network device on Windows' Network connections
- Uninstall VBox, install a older version (VirtualBox-5.1.30)
- Reinstall VBox using Admin option
- Uninstall VBox, delete completely .VirtualBox folder, reboot the machine, then reinstall VBox as: user and admin
- Delete all the Devices using the GUI and create the device using VBoxManage hostonlyif create

",Diego Resendi
18084,Audio ICH AC97 Host Win7 x64 troubles 5.2.x and 6.x BETA,Windows,Windows,VirtualBox 5.2.20,2018-10-27T16:12:52Z,2018-10-27T16:12:52Z,"Guest - Windows 7 SP1 x64 and Windows XP SP2 x64 - with '''ICH AC97''' audio will not work in/with Host Windows 7 SP1 x64.[[BR]]
The same troubles in 5.2.x and 6.x Beta.[[BR]]
But no troubles with Host Windows XP SP2 x64.",Harald Welkovics
16127,Setting up virtual LPT port to connect through to real LPT port stops DOS VM starting,Windows,other,VirtualBox 5.1.8,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
18085,Audio ICH AC97 Host Win7 x64 troubles 5.2.x and 6.x BETA,Windows,Windows,VirtualBox 5.2.20,2018-10-29T11:11:53Z,2018-10-29T11:11:53Z,"Guest - Windows 7 SP1 x64 and Windows XP SP2 x64 - with '''ICH AC97''' audio will not work in/with Host Windows 7 SP1 x64.[[BR]]
The same troubles in 5.2.x and 6.x Beta.[[BR]]
But no troubles with Host Windows XP SP2 x64.
Have a look in the attached LOG at line 1429:[[BR]]
DSound: Creating capture buffer failed with E_FAIL[[BR]]
[[BR]]
Harry",Harald Welkovics
17493,Guest audio pass via vRDP sound weird (jitter?),Linux,Windows,VirtualBox 5.1.32,2018-10-29T11:18:55Z,2018-10-29T11:18:55Z,"HOST is Debian 9.3[[br]]GUEST is Windows XP

What sound like: Jitter? echo in the tunnel?[[br]](It may not be noticed if playback duration is less than a second.)

At first I suspect that remmina client cause it. Later I found Microsoft's RDP client (mstsc.exe) also run into this.

Tried to change sound back-end between PulseAudio and ALSA, No avail.",NoNoNo
17911,Audio missing with applications on Windows 98,Windows,Windows,VirtualBox 5.2.16,2018-10-29T19:37:46Z,2018-10-29T19:37:46Z,"When I first install Windows 98, the audio and start sound work as expected but any other applications such as the built in media player are silent. The only audio I can hear is the Windows notification sounds and everything else is silent. I'm unsure as to whether this is being caused by something I'm doing or if this is being caused by a VirtualBox bug.",Eddy Smith
18088,guest additions fail to compile against kernel 4.19,Windows,Linux,VirtualBox 5.2.20,2018-10-30T17:08:44Z,2018-10-30T17:08:44Z,"Here is the link for the errors I get:
https://paste.pound-python.org/show/ohbTEHj8QWpqgz3vjxWS/

Best regards,
Serge",pourpier
18091,virtualbox 5.2.20 fails to compile with glibc 2.26 because xlocale.h was removed,Linux,all,VirtualBox 5.2.20,2018-10-31T13:51:06Z,2018-10-31T13:51:06Z,"As of glibc 2.26 the file xlocale.h is no longer provided as it was never intended to be there as it's a subset of locale.h

see also this article: https://ahelpme.com/linux/compiling/glibc-2-26-and-failure-to-compile-because-of-xlocale-h/

please fix source code so no awkward symnlinks are necessary in order to build Virtualbox.",marcelser
18092,Guest editions won't install in new Windows 10 1809,Windows,Windows,VirtualBox 5.2.20,2018-10-31T20:21:13Z,2018-10-31T20:21:13Z,"As soon as guest edition installation is run on Windows 10 1809 host, the mouse and keyboard stops working. The installation can never be completed because it is impossible to respond to UAC prompt. Tried reboot several times, windows updates, didn't fix the issue.",Skippy
18090,Virtualbox crashes on taking a snapshot,Linux,Linux,VirtualBox 5.2.20,2018-10-31T23:23:29Z,2018-10-31T23:23:29Z,"I've just installed ubuntu 18.04.1 64bit on VirtualBox 5.2.20.
The installation was the minimal version of ubuntu, everything else at default settings.
My host is Ubuntu 18.04.1 64 bit, too.

After the installation I ran update and upgrade.
I installed gcc, perl, make and build-essential.

Then I ran the guest additions.

The system runs stable and without problems so far. But if I try to make a snapshot, the machine crashes reproducably.
I'm taking the snapshot while the machine is running. The window closes and the state of the machine is changed to ""aborted"".
No snapshot is taken.

Here is the logfile:
https://pastebin.com/f1dqGkxV",lhk
18094,Several bug on sound,Linux,Windows,VirtualBox 5.2.18,2018-11-01T20:00:33Z,2018-11-01T20:00:33Z,"When i have played a sound and i stopped the playing,
this guest machine and host machine random freeze.

Can you solve this bug please ?
I join log .
",Sizy458
18097,"Repeatable Kernel Panic OSX Host 10.13.6, 5.2.18/5.2.20",Mac OS X,Linux,VirtualBox 5.2.18,2018-11-02T15:20:03Z,2018-11-02T15:20:03Z,"Hi there. I've been contributing to a forum topic about this here: https://forums.virtualbox.org/viewtopic.php?f=8&t=89890&sid=71ba74a8550785a1228b2d0ccdcefa74&p=432426#p432426

I have a Mac Mini (10.13.6, 16GB RAM) which is having regular kernel panics while running three Ubuntu VMs, particularly when under load. The three instances are Ubuntu 16.04 and serve as a three-node Graylog cluster (one master, two additional nodes). Perhaps complicating matters is that the .vdi's being written to are not on the local disk; rather they are saved to a Pegasus R2 RAID-5 array connected over (Apple standard) Thunderbolt cable. This allows them to be 2TB each with battery-backed writes, or believe me I'd be keeping them on the boot disk.

I've tried, to no avail:
* Moving to 5.2.20
* Wild ass guess that the repeated appearance of com.apple.msdosfs as a last-loaded/uloaded kernel extension was somehow the problem, boot into recovery to disable SIP and move aside that kext (when this didn't work, put it back in place again). 
* Altering the paravirtualization settings on the Ubuntu guests (Default, None, KVM) - currently sitting at the recommended KVM option
* Finally, added the ""keepsyms=1"" nvram parameter to at least get the backtrace symbolicated.

I'd be *beyond* happy to take any wild suggestions for additional logging to help diagnose this in any way. The full panic is attached, but this is the top relevant section I believe: 

{{{
Anonymous UUID:       8C247A86-017F-C949-405A-1CFF90AF12B3

Thu Nov  1 15:15:43 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff8006f8776f): Kernel trap at 0xffffff80072d36b0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000100000008, CR3: 0x00000003a8a860ea, CR4: 0x00000000001627e0
RAX: 0xffffff8025937610, RBX: 0x0000000100000000, RCX: 0x0000000009000000, RDX: 0xffffff80076a5128
RSP: 0xffffff91f69dbea0, RBP: 0xffffff91f69dbef0, RSI: 0x0000000000000002, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000000000000400, R10: 0x0000000000000061, R11: 0xffffff91f6b07770
R12: 0xffffff91f69dbea0, R13: 0x0000000000000000, R14: 0xffffff802b6025f0, R15: 0xffffff800782b8d0
RFL: 0x0000000000010206, RIP: 0xffffff80072d36b0, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000100000008, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff91f69db970 : 0xffffff8006e6c1c6 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffff91f69db9c0 : 0xffffff8006f95274 mach_kernel : _kdp_i386_trap + 0x114
0xffffff91f69dba00 : 0xffffff8006f87544 mach_kernel : _kernel_trap + 0x4e4
0xffffff91f69dba70 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dba90 : 0xffffff8006e6bc3c mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffff91f69dbbc0 : 0xffffff8006e6b9fc mach_kernel : _panic + 0x5c
0xffffff91f69dbc20 : 0xffffff8006f8776f mach_kernel : _kernel_trap + 0x70f
0xffffff91f69dbd90 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dbdb0 : 0xffffff80072d36b0 mach_kernel : _audit_mac_free + 0xa0
0xffffff91f69dbef0 : 0xffffff80072c5a65 mach_kernel : _audit_free + 0x115
0xffffff91f69dbf10 : 0xffffff80072c6676 mach_kernel : _audit_syscall_exit + 0x46
0xffffff91f69dbf40 : 0xffffff8007403987 mach_kernel : _unix_syscall64 + 0x287
0xffffff91f69dbfa0 : 0xffffff8006e1e9c6 mach_kernel : _hndl_unix_scall64 + 0x16

BSD process name corresponding to current thread: VBoxHeadless
Boot args: -v keepsyms=1

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide:     0x0000000006c00000
Kernel text base: 0xffffff8006e00000
__HIB  text base: 0xffffff8006d00000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

System uptime in nanoseconds: 2300159388101
last loaded kext at 246145680169: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
last unloaded kext at 306907560558: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.18
org.virtualbox.kext.VBoxNetFlt	5.2.18
org.virtualbox.kext.VBoxUSB	5.2.18
org.virtualbox.kext.VBoxDrv	5.2.18
com.promise.driver.stex	6.2.9
com.apple.iokit.SCSITaskUserClient	404.30.2
<SNIP>
}}}

Best regards, and much respect: VirtualBox is a wonderful technology.
./scc",Scott Corscadden
12894,Deleted snapshots leave removable media attached,other,other,VirtualBox 4.3.10,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
18099,Windows 10 won't start,other,Windows,VirtualBox 5.2.20,2018-11-03T06:55:39Z,2018-11-03T06:55:39Z,"I've got other virtual machines running without any problems (windows server 2008, ubuntu, centos, windows 7) but windows 10 won't even start.",AlexFlynn
18100,Old DHCP leases interfere with changed server configuration,Linux,Linux,VirtualBox 5.2.20,2018-11-03T19:35:58Z,2018-11-03T19:35:58Z,"Host: openSUSE Leap 15

virtualbox-host-kmp-default-5.2.20_k4.12.14_lp150.12.22-lp150.4.20.1.x86_64
virtualbox-host-source-5.2.20-lp150.4.20.1.noarch
virtualbox-5.2.20-lp150.4.20.1.x86_64
virtualbox-qt-5.2.20-lp150.4.20.1.x86_64

In short, the lease file for a NAT net must be deleted by hand. Otherwise the DHCP server (with a different IP) hands out the old leases (wrong IPs).",robert spitzenpfeil
18096,Download froze,other,other,VirtualBox 5.2.20,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
18095,Problem input audio,Linux,Windows,VirtualBox 5.2.18,2018-11-04T14:37:06Z,2018-11-04T14:37:06Z,"I tested recording audio since audacity runned in the host machine ,it's work fine !

On Goldwave runned in the guest machine i note :
I find that the record level sound of its saturates at
33% and 
that virtualbox regresses !!.",Sizy458
18083,Ordering of groups (inside groups) gets lost upon GUI restart,Linux,all,VirtualBox 5.2.20,2018-11-05T07:37:26Z,2018-11-05T07:37:26Z,"This issue did appear with 5.2.18 (AFAIK) and is still in the current one. I have not been able to pinpoint, what exactly is missing and in which file.

This is happening: VBox GUI shows groups + vm's, but in a messed up order. Next i manually sort them, as they should show up, close the app, reopen, and the order is back to the messed up one, which did not happen half a year ago.

I am going to attach 2 screenshots and the main config file.",Bard0
18103,User-manual amendment regarding DHCP IP / NAT networking,other,other,VirtualBox 5.2.20,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
18059,Upgrade to 5.2.20 breaks usb passthrough,Windows,all,VirtualBox 5.2.20,2018-11-05T15:10:52Z,2018-11-05T15:10:52Z,"Host : Windows 10 Enterprise 1607

Upgraded Virtualbox to 5.2.20 from 5.2.18 with extension pack and USB passthrough does not detect any connected devices. Downgrading Extension pack to 5.2.18 does not resolve the issue, downgrading Virtualbox to 5.2.18 solves it.

I can upgrade again to collect any logs you want to help you solving this bug

Regards",3mptyy
18108,Very poor performance on iMac 2017 5K,Mac OS X,Windows,VirtualBox 5.2.20,2018-11-05T22:42:10Z,2018-11-05T22:42:10Z,"IiMac 2017, 27 inch, 5K, 32 GB RAM. It is impossible to work properly on virtual machines. The virtual machines are Windows 10, Windows 7 and Windows XP. All systems run badly.",macjacke
18109,Error when drag-and-drop zero length files from guest to host,Windows,Windows,VirtualBox 5.2.20,2018-11-06T06:41:33Z,2018-11-06T06:41:33Z,"Version: 5.2.20, 5.2.18
Host: Windows 7 SP1
Guest: Windows 7 SP1 RU/EN, Windows XP SP3 RU
Guest additions: installed according to VirtualBox version

Error occurs when dragging zero length file from guest to host:
{{{
Drag and drop operation from guest to host failed.
Current drop operation still in progress.
Result Code: E_FAIL (0x80004005)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Same error occurs when dragging folder with zero-length file from guest to host.

After that error any other drag-and-drop operation even with non-enpty files fails with error:
{{{
Drag and drop operation from guest to host failed.
Another drop operation already is in progress.
Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Steps to reproduce:
1) Install guest Windows 7 or Windows XP (any language in to the VB) 
2) Install VB Additions
3) Turn on drag-and-drop from guest to host (or bidirectional)
4) Drag and drop any non-zero-length file to check that it works
5) Create any new empty file (for ex. new notepad document)
6) Drag it from guest to host
7) Get error

It is possible to ""reset"" the satuation by trying to drag any file from host to guest. May be not immediately, may be couple of times.
I did not find exact scenario. 
Sometimes attempts to drag files from host to guest after error leads to guest interface partially hang. In that case shutdown procedure asks to forcibly close VBoxTrayDnDWnd.

Additional: errors appear in host log files, not in guest.
",yumashka
18110,Unable to save window state,other,other,VirtualBox 5.2.20,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
18111,Always in Snapshot-View - 5.2.20,Windows,Windows,VirtualBox 5.2.20,2018-11-06T17:31:43Z,2018-11-06T17:31:43Z,"My english isn't so good to translate my problem:
https://forums.virtualbox.org/viewtopic.php?f=5&t=90176",VM-F4n
17858,VBox Guest Additions make crash VM VB during take VM snapshots,Windows,Linux,VirtualBox 5.2.14,2018-11-07T05:58:14Z,2018-11-07T05:58:14Z,"Hi All!

I have a VBox VM with Ubuntu 18.04 as guest on WIndows 10 Host. Before installing the VBox Guest Addition (VB GA) on Ubuntu VM, the VM snapshots all worked very well! But after installing it, all the snapshots that are made cause a crash of the same VM (they interrupt its functioning). In practice, the snapshot process stops and crashes as soon as it reaches 96% of the acquisition of the same. I need the VB GA to implement the shared network folder between guest and host.

In my opinion this is a bug of the VB GA.

  - What's the cause of this crash? Is it possible to fix it?

Thank you.

Greetings,

Lorenzo",Kowa92
18102,audio total loss after vm pause,Mac OS X,Windows,VirtualBox 5.2.20,2018-11-08T08:25:29Z,2018-11-08T08:25:29Z,"host is Mac OS X 10.14.1
guest is win xp
VM is 5.2.20.

i launch my win app (Age of Empires ii, if that makes any difference). 
i enter key-p (for VM pause), then same again to exit pause, and all audio on that VM is gone for good. closing/restarting the app does not help.
the only known cure is shutting down the VM and re-launching.
This is not dramatic for the case in hand, but tedious anyway.

This symptom is new with 5.2.20 (did not happen in 5.2.18)
Not sure if/how this ties in with other recent audio observations.
Not sure if/how this is host specific or guest specific.

Do feel free to prioritize this down, i do not mean to be alarmist, i simply wanted to doc the observation to help complete the picture.

Good luck.",MatsWolpers
4626,PPPoE fails over bridged HP8510w 4965AG WLAN card,Windows,Windows,VirtualBox 3.0.2,2018-11-08T23:11:59Z,2018-11-08T23:11:59Z,"I have a problem where I have a host machine, an HP8510w laptop with an intel 4965AG WLAN card. I am running Vista 64 Ultimate (same problem with Win 7 64 RTM) with a guest machine running Windows XP Sp3. The most important aspects of this setup is that the guest machine is set to be bridged to my WLAN card (Intel 4965AG). I am using static IP's with a router.

After the Guest OS is installed, I have configured an IP address. I can ping the router from the Host OS and I can also ping the router from the Guest OS. All other aspects of networking seem to be working. (I do not use DHCP purely because of my network setup but I feel this is unimportant).

I have several PPPoE accounts and a router that is in bridge mode. When I try to initiate a PPPoE connection in the Guest OS (WinXP), PADI packets leave the guest machine, go through the bridged network, reach the router. The router then sends a PADO response which can be seen on the Host OS and is also passed on to the Guest OS.

Unfortunately, the Guest OS is ignoring these packets as the target MAC address does not seem to be for the Guest OS (Which is understandable, but surely the bridging driver/service installed on the Host OS NIC is supposed to correct this?)

This seems to be a problem with the bridging driver/service for VirtualBox. This may not be of any concern to you, but the problem also exists in VMware Workstation. This is not a problem for Microsoft Virtual Machine though.

I have discovered a slight workaround. If I set the MAC address of the virtual network card in the guest to the same MAC address of the Host OS WLAN card, the PADO packets are relayed and it now works. Unfortunately, this causes other problems with Linux Guest's trying to use the same workaround and I cannot use this solution permanently.

I have attached the Vbox.log, as well as two wireshark captures from both the host and the guest machine.",Kinnoken
17425,Ubuntu 18.04 xcb not found... but found.,Linux,all,VirtualBox 5.2.4,2018-11-09T00:01:34Z,2018-11-09T00:01:34Z,"Attempting to start virtualbox produces the following error:

------------------------------
08:56:19 evil@sager ~» virtualbox
Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin ""xcb""
in """".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)
----------------------------------

Oddly the message lists xcb as an available plugin.

Attempting to run VirtualBox as root, and to force the library path (P=/usr/lib/virtualbox; sudo LD_LIBRARY_PATH=$P:$P/plugins/platforms $P/VirtualBox) produces the same error as seen above.

Running ldd, there appear to be no missing dependencies for any of the virtualbox libraries or libqxc

----------------------------------
09:06:47 evil@sager ~» ldd /usr/lib/virtualbox/*.so | grep not
09:06:50 evil@sager ~» 

09:25:32 evil@sager ~» ldd /usr/lib/virtualbox/components/*.so | grep not
09:26:17 evil@sager ~»

09:04:44 evil@sager ~» ldd /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so | grep not
09:05:44 evil@sager ~» 
----------------------------------

Only the extension pack VNC files, which I wouldn't think would be necessary to start the GUI show anything not found:

----------------------------------
09:29:23 evil@sager ~» ldd /usr/lib/virtualbox/ExtensionPacks/VNC/linux.amd64/*.so | grep not
        VBoxRT.so => not found
        VBoxRT.so => not found
09:29:40 evil@sager ~»
----------------------------------

What I've tried:

1.  apt uninstalling (with --purge) virtualbox* and re-installing.  Same results.

2.  apt uninstalling (with --purge) virtualbox* and backleveling to v5.1.  Same results.

3.  apt uninstalling (with --purge) virtualbox* and re-installing using the latest deb downloaded from your site rather than the artful repo.  Same results.

4. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins /usr/lib/virtualbox/plugins  (same results)

5. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms /usr/lib/virtualbox/platforms  (same results)

6. sudo ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so /usr/lib/virtualbox/libqxcb.so  (same results)

7. Re-installed _all_ of the Qt5 libraries and rebooting.  Same results.

8. Running a trace (I will attach it to the ticket).  Line 1313 is where it loads libqxcb.so.


I'm not having any issues with any other Qt5 applications on this system - and even use it to develop Qt5 apps.  Any help figuring this out would be appreciated.",3vi1J
18118,After upgrade XP game hangs,Mac OS X,other,VirtualBox 5.2.20,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
18086,vboxa uthentication segfaults SQW01,Linux,other,VirtualBox 5.2.20,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
18119,Linux Mint 19 freezes when resizing Window,Windows,Linux,VirtualBox 5.2.20,2018-11-10T14:14:49Z,2018-11-10T14:14:49Z,"Sometimes when I maximize the virtual machine window the guest OS freezes.  I am running Mint 19 guest on Windows 10 Host.
",Motoko
18114,Tray task start looping after dragging a file object from Host to Guest,Windows,Windows,VirtualBox 5.2.20,2018-11-11T11:02:40Z,2018-11-11T11:02:40Z,"When I try to drag file objects from my Windows 10 1803 64bit Host-Desktop to the Desktop of Windows 10 1803 32 bit Guest, VirtualBox Guest Additions Tray Application immediately starts to loop during creating interrupts. After passing to the Guest windows, the drag indicator changes ""Cannot drop"".

This is fully reproducible. When dragging extremely slow, the drop may succeed.",SchweizerGarde
18125,Extention Pack  Install Error,Windows,Windows,VirtualBox 5.2.22,2018-11-12T16:25:37Z,2018-11-12T16:25:37Z,"Failed to install the Extension Pack F:/Downloads/Tools/Oracle/Oracle_VM_VirtualBox_Extension_Pack-5.2.22.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-16880' -&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}

",Hercules Oberholzer
18117,vboxsf filesystem doesn't handle no extension file name,Windows,Linux,VirtualBox 5.2.20,2018-11-12T16:32:23Z,2018-11-12T16:32:23Z,"I am using VirtualBox version 5.2.20. 
My virtual machine (Ubuntu Linux) is running Windows 10.
I set up shared folders and it mounted with -t vboxsf on the Ubuntu.

Here is error case with vboxsf filesystem: I created "".new.test1."" file but it created "".new.test1"" file.
{{{
chwon@chwon-VirtualBox:~/sandbox/tmp$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls -la
total 5
drwxrwxrwx 1 chwon chwon    0 Nov  8 15:12 .
drwxrwxrwx 1 chwon chwon 4096 Nov  8 15:11 ..
-rwxrwxrwx 1 chwon chwon    6 Nov  8 15:12 .new.test1
chwon@chwon-VirtualBox:~/sandbox/tmp$ 
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1.
ls: cannot access .new.test1.: No such file or directory
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1
.new.test1
}}}

I did same test on Linux ext4 filesystem.
{{{
chwon@chwon-VirtualBox:~/tmp/test$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls -la
total 12
drwxrwxr-x 2 chwon chwon 4096 Nov  8 15:28 .
drwxrwxr-x 4 chwon chwon 4096 Nov  8 15:28 ..
-rw-rw-r-- 1 chwon chwon    6 Nov  8 15:28 .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1. 
.new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1
ls: cannot access .new.test1: No such file or directory
}}}

",Arirang
18112,VirtualBox crash on start ReactOS with BTRFS,other,other,VirtualBox 5.2.20,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
15986,Shared clipboard is not working in headless mode,Windows,all,VirtualBox 5.1.6,2018-11-13T09:07:10Z,2018-11-13T09:07:10Z,"I've found plenty similar tickets about this issue but they all are related to obsolete versions so I created this one.[[BR]]

Several tickets ([https://www.virtualbox.org/ticket/14964 14964], [https://www.virtualbox.org/ticket/14645 14645] and [https://www.virtualbox.org/ticket/14421 14421]) are ''likely'' to be the same (I don't know this for sure) but there was no mention about headless mode  or VRDP and my tests clearly say this is headless-only bug.
The most appropriate '''recent''' tickets I found were [https://www.virtualbox.org/ticket/11397 11937] and [https://www.virtualbox.org/ticket/10057 10057] (which are still open), but there are much-much older ones ([https://www.virtualbox.org/ticket/11140 11140], [https://www.virtualbox.org/ticket/3794 3794])[[BR]]

I decided to create my own as I don't know exactly is my issue related to any of them so it's up to admins to merge them or leave them as is.[[BR]]

All in all, my bug comprises several symptoms:
1. shared clipboard does not work guest2host direction on Windows and Linux guest.
2. shared clipboard does not work inside Windows guest at all (in Linux guest does)
3. All this is observed only in headless mode (guest is accessed via VRDP).

Host2guest direction works good.
In GUI mode both directions work wonderful.",Suncatcher
18126,Guest linux fails to receive key input after X11 screen appears on resume from saved state.,other,other,VirtualBox 5.2.22,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
18128,Some strings are not translatable in macOS,Windows,other,VirtualBox 5.2.22,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
11590,Win 7 VM slows down when presenting in GoToMeeting,Linux,Windows,VirtualBox 4.2.8,2018-11-14T23:53:24Z,2018-11-14T23:53:24Z,"This bug has been on-going for me since the January time frame. The basic issue is that when using GoToMeeting in a Win7 VM, and if my VM is made the presenter, then graphics slow down to the point where the VM becomes unusably slow. The VM can be in a meeting with someone else presenting and it's fine. Only slow when the VM becomes the presenter. Slow means the cursor is unresponsive, gui interaction inside the Win 7 VM is very slow, cursor flicker. Pause the screen so that it's not being updated and the VM becomes fast again.

I've seen this problem on 3 Win 7 VMs, two on this machine and one on my laptop. Both hosts are Gentoo Linux 64-bit, mostly stable and completely up to date. 

Both machines can boot Win 7 natively and have not problems. VMWare running Win XP on the same machines has no problems.

I am going to attempt to attach a log file of the VM booting, starting Google Chrome, starting G2M, having the problems and then shutting down the VM.",Mark Knecht
18134,"Qt5 interface does not start with hardening, with qt-xcb enabled.",Solaris,other,VirtualBox 5.2.22,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
17886,VM self-terminates on MacOS,Mac OS X,Linux,VirtualBox 5.2.16,2018-11-15T16:50:17Z,2018-11-15T16:50:17Z,"Note: ''' I have only witnessed this behavior since upgrading''' to the last version I was prompted for.

Since upgrading to this version of VirtualBox, my VM disappears from the Dock, and its status is 'Aborted' in the VM manager window.

I am unable to identify any particular action taken by me that causes it, since I am never looking or using the VM when it happens.

----
'''MacOS:''' 10.13.6[[BR]]
'''VirtualBox:''' 5.2.16 r123759 (Qt5.6.3)[[BR]]
'''VM:''' Ubuntu 16.04 x64[[BR]]
'''Hardware:''' 2016 15"" MBP, 2.9GHz, 16GB 2133MHz, Raedon Pro 460 4GB/Intel HD 530 1.5GB [[BR]]
----

I'm attaching the logs I saved through the GUI, and a cursory grep through `/var/log/system.log` yielded the following (''I have no idea if it's related to the shutdown or not''):

{{{
VirtualBox[26651]: objc[26651]: Class FIFinderSyncExtensionHost is implemented in
both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8e04cc90)
and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10dc79cd8).
One of the two will be used. Which one is undefined.
VirtualBox[26651]: notify name ""user.uid.501.BRNotificationServerAvailabilityChanges""
has been registered 20 times - this may be a leak
VirtualBox[26651]: assertion failed: 17G65: libxpc.dylib + 75013
 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89
}}}",Ryan Lederman
17942,"Audio is almost unusable on Windows 10 Insider builds, when they are cleanly installed.",Windows,Windows,VirtualBox 5.2.18,2018-11-15T23:23:56Z,2018-11-15T23:23:56Z,"Steps to reproduce
* Install Windows 10 into a virtual machine.
* Upgrade it to latest fast ring insider build (at the time of this report 17741).
* Notice that audio is working as expected.
* From settings; update and security; reset perform reset of this machine.
* Notice, that audio sounds horribly.
I'm Attaching a logs before and after reset, audio files dumped before a reset and after a reset.
This issue is very important, because it affect also a clean installations of recent Insider builds into Virtual Box vms, and it prevents blind people like me from doing it independently.
I've also verified, that the driver used for the sound card is the same before and after the reset.",lukaszgo1
18132,Sound in running VM distorted,Mac OS X,Windows,VirtualBox 5.2.22,2018-11-16T16:12:18Z,2018-11-16T16:12:18Z,"Host: macOS Mojave 10.14.1,
Guest: Windows 10 pro 1809

As the sound was distorted during the installation of 1809 and is still after installing Guest Additions I followed this article:

https://www.virtualbox.org/wiki/AudioDebug

According to that the diagnosis is ""Device emulation problem"".

Please find VBox.log attached.

Could you please help to fix the issue?
Thanks",tom.txc
18135,Guest network down with version 5.2 and e1000,Linux,Linux,VirtualBox 5.2.20,2018-11-17T15:07:25Z,2018-11-17T15:07:25Z,"After an upgrade from 5.1.38-122592 to 5.2.20-125813 the guest network did not automatically come up. The network worked fine after bringing the interface down/up.
Another copy of the same VM running on different hardware with identical software did not have the problem.

Both VMs were using E1000 network adapters in bridged mode. Switching to either of the PCnet adapters fixed the issue on the ""not working"" system.

[Beware: User speculation] The not working system is slower and it looks like there was a recent change to the E1000 LinkUpDelay from 5000ms to 3000ms. I'm suspecting that the shortened delay may be related to the problem. I could not find a configuration setting for the LinkUpDelay.

Host systems: Debian 9 (stable) 64 bit (fully up to date)

Guest systems: Debian 9 32 bit (fully up to date)

About the VirtualBox version. I first noticed the issue on 5.2.20, but did not have a chance to gather logs until after upgrading to 5.2.22. Both versions have the issue.

Not working hardware:
{{{
  AMD Turion(tm) 64 Mobile Technology ML-34 (800 MHz single core)  
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
	Subsystem: Hewlett-Packard Company RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
	Flags: bus master, medium devsel, latency 128, IRQ 22, NUMA node 0
	I/O ports at a000 [size=256]
	Memory at c020a400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
	Kernel driver in use: 8139too
	Kernel modules: 8139cp, 8139too
}}}
Working hardware:
{{{
  Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (dual core, 800 MHz)  
  Ethernet controller: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
	Subsystem: Hewlett-Packard Company 6710b
	Physical Slot: 1
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at e4000000 (64-bit, non-prefetchable) [size=64K]
	Expansion ROM at <ignored> [disabled]
	Capabilities: [48] Power Management version 3
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-1c-c4-ff-fe-c9-02-6d
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: tg3
	Kernel modules: tg3
}}}",FixItDad
18136,Audio canceled strangely with virtualbox grater than 5.2.18.,Windows,Linux,VirtualBox 5.2.22,2018-11-18T00:33:05Z,2018-11-18T00:33:05Z,"== The problem ==

Starting with virtualbox 5.2.20, the audio began to not work properly for me.  When I try to play some audio, I hear the first part of the audio, but it is cut of a short time before the end. So, if I for example try to play a file containing the words ""Hello World!"", I may only hear ""Hello Wo"". If I then try to replay the file, it works exactly as previously: I only hear the first part of the file. It works with virtualbox 5.2.18, but not with 5.2.20 or later, so the bug was introduced with the 5.2.20 release.

== System ==

I am running windows 7 as host and headless arch linux as guest. I am using alsa as sound server on the guest.

== Attachments ==

I will attach VBox.log and a webm file where I try to play audio. The webm file is recorded video from the guest. I try to create a file containing ""Hello world!"", called hello.wav, with espeak. Then I try to play the file with aplay, both in userspace and as root. Audio is included so you can hear the result.

== Priority ==

This bug is very critical for me. I am blind and therefore I am partially using speech to access the screen content.

Thanks in advance!",Tage
17947,Virtualbox 5.2.18 (and 5.2.19) crash on OpenIndiana Hipster,other,all,VirtualBox 5.2.18,2018-11-20T09:01:19Z,2018-11-20T09:01:19Z,"Hi,
ref: https://www.illumos.org/issues/9752

When starting a VM on 5.2.18/19 from hostOS openindiana (illumOS) it crashes in 

rtR0SegVBoxSolCreate().

#echo disable_smap/d | mdb -k
disable_smap:
disable_smap: 1
",Espen Martinsen
14058,Snapshots does not work if VHD files are not in default VB folder,other,Windows,VirtualBox 4.3.26,2018-11-20T11:07:58Z,2018-11-20T11:07:58Z,"I use Virtual Box in Windows 7 Prof machine using VHD hard drives.  The snapshots feature does not work if the VHD files are not in the default virtual machine folder (C:\Users\[username]\VirtualBox VMs\[VM name]\).

The error I get when trying to start a VM with snapshot taken in this case is:
----------------
Failed to open a session for the virtual machine XPMCEV.

No error info.

Result Code: E_FAIL (0x80004005)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
-----------------

If I try to delete the snapshot I get the following error:
-----------------
Failed to delete the snapshot Snapshot 1 of the virtual machine XPMCEV.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\T\VirtualBox VMs\XPMCEV\Snapshots\{aa909f03-903f-49a6-95e4-86be9b669c90}.vhd' does not match UUID {58c773b9-e66b-2a4f-a805-91367074598d} of its parent medium stored in the media registry ('C:\Users\T/.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
-----------------

When I move the VHD file to the default machine folder, the snapshot works.

I put the VHD file in a different drive due to space and performance constraints.

The snapshot feature really makes it easy to test and rollback changes when needed.

Thank you in advance.",S T
18141,VBoxManage usbfilter add/modify --product does not set value,other,other,VirtualBox 5.2.22,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
8473,Error opening current controlling terminal for the process,Linux,other,VirtualBox 4.0.4,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
18029,NAT network UDP port forwarding not working,Windows,Linux,VirtualBox 5.2.18,2018-11-23T11:25:11Z,2018-11-23T11:25:11Z,"I've created a machine with linux ubuntu with NAT network attached.
The machine connects properly and receives an address 10.0.2.7.
I've created a port forwarding from UDP 500 to 10.0.2.7 UDP 500.
It seems that packets sent to UDP 127.0.0.1:500 are not arriving to the machine. (checked with tcpdump -i enp0s3 udp 500 on the machine.
Doing the exact same with TCP works fine.
Packets are sent with ""Packet Sender"", and verified with rawcap on the host.",Asi Lev
14484,Host-only adapter fails after sleep-wake transition,Windows,Linux,VirtualBox 5.0.2,2018-11-25T15:46:20Z,2018-11-25T15:46:20Z,"In 5.0.2, Window 7 host, Debian 8 guest, the host-only adapter only works after a full restart of host and guest.  Once you put the host to sleep and wake it back up again, the host-only adapter is broken.  Here is what ping from the guest gives:

root@byted> ping 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
From 192.168.56.101 icmp_seq=1 Destination Host Unreachable

where 192.168.56.101 is the guest IP and 192.168.56.1 is the adapter IP.  There is a similar break in ping of guest IP from host.

jpm
 ",Jeff Morgenthaler
15792,Switching between Guided and Expert modes in Create Virtual Machine window loses settings,Linux,all,VirtualBox 5.1.2,2018-11-25T21:27:10Z,2018-11-25T21:27:10Z,"I noticed a small problem when creating a VM using the GUI. Lubuntu 16.04 x86-64 host.

Click New, then when the Create Virtual Machine window appears type something in the Name field and change the Type and Version fields.

Click Expert Mode. The name and OS fields get reset to the default blank and Microsoft Windows / Windows 7 (64-bit). Similarly you can change those then click Guided Mode, and those fields reset again.",Donuts
18152,Windows 2012 R2 Build 9600 broken networking,Mac OS X,Windows,VirtualBox 5.2.22,2018-11-28T12:44:54Z,2018-11-28T12:44:54Z,"Upgraded to VirtualBox Version 5.2.22 r126460 (Qt5.6.3) on macOS 10.12.6 and Windows 2012 R2 as a VM networking does not work. In fact, the 2012 VM does not even detect a network interface.

[[Image(https://user-images.githubusercontent.com/6723257/49027270-7020f880-f165-11e8-86bc-621db519a02c.png)]]	

[[Image(https://user-images.githubusercontent.com/6723257/49028433-00603d00-f168-11e8-9456-67cf6261b690.png)]]	",Bob Tanner
18156,MacOSX shutdown wedges VirtualBox,other,other,VirtualBox 5.2.22,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
18130,VBoxGuestAdditions 5.2.22 3d acceleration not working,Windows,Linux,VirtualBox 5.2.22,2018-11-28T16:46:56Z,2018-11-28T16:46:56Z,"System environment:[[BR]]

''Host OS'': Windows8 Pro 64 bit (all updates)[[BR]]

''Guest OS'': Debian 8.11 (kernel 3.16.0-4, all updates from stable branch 8.11)

After update from 5.2.20 to 5.2.22 and apply VBoxGuestAdditions.iso - 3d acceleration stopped working.

If roll back GuestAdditions to 5.2.20 (but save Vbox version 5.2.22) - 3d acceleration working again.",ilyalesnoi
17443,Drag and drop operation from guest to host failed - Occurs when trying to move a file with 0kb file size -> fixed in 5.2.20,Windows,Windows,VirtualBox 5.2.4,2018-11-29T12:37:48Z,2018-11-29T12:37:48Z,"Windows XP guest

After receiving this error I started transferring files one at a time and noticed that empty text documents with a file size of 0kb were causing the error.

Error info:

{{{
Drag and drop operation from guest to host failed.

Another drop operation already is in progress.

Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

}}}

Each time the error occurs, I can no longer move any files and must restart the virtual machine.

VirtualBox does not crash, however
When exiting the machine there is an Application Error

Error Details:

{{{
The instruction at 0x00007FF8C4742C98 referenced memery at 0x0000000000000028. The memory could not be read.
}}}



",lukemeow
18139,SIGINT (or Ctrl-C) on Mac Host not passed to Guest,Mac OS X,Linux,VirtualBox 5.2.22,2018-11-29T23:59:14Z,2018-11-29T23:59:14Z,"When running a CentOS 7 guest on Max OS X (High Sierra & Mojave), any Ctrl-C command on the terminal is not captured and passed to the guest.

I ran into this issue originally via the terminal app when running the VirtualBox instance with Vagrant. However, i enabled the VBox Gui and then logged in directly. The Ctrl-C command is not being captured correctly and passed to the foreground process. 

You can see in the attached image the keyboard input as i tail a log file. The command should have terminated the tail, instead the key combination is displayed. ",BStopp
18142,"disable option for ""Welcome to VirtualBox!""",Linux,all,VirtualBox 5.2.22,2018-11-30T00:17:10Z,2018-11-30T00:17:10Z,"after I start VirtualBox, before the machines and the details was shown, now I see this ""Welcome to VirtualBox!"" Mickey Mouse design. I would like a preference to disable this or to have the choice what so see, the Mickey Mouse Welcome, the machine details, the machine snaps, etc..",keinereiner
18140,perte du clavier après installation virtualbox Version 5.2.22 r126460 (Qt5.6.2),other,other,VirtualBox 5.2.22,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
18144,VBoxManage list usbhost fails to correctly identify USB Reader,Linux,Windows,VirtualBox 5.2.22,2018-11-30T00:34:21Z,2018-11-30T00:34:21Z,"Here is the output of various commands that might be useful. My report and comments are disclosed below.

{{{
$ uname -a
Linux wangwq-mint 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
}}}


{{{
$ sudo lsusb -vv -d 0000:a180
[sudo] wangwq 的密码：

Bus 001 Device 008: ID 0000:a180  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0000 
  idProduct          0xa180 
  bcdDevice            1.00
  iManufacturer           1 NARI
  iProduct                2 Sgchip Smart Card Reader
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          338
    bNumInterfaces          4
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              3 Sgchip Dual Reader ICC 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4800
        dwMaxiumumClock      8000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      412903 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             254
        dwSyncProtocols  00000007  2-wire 3-wire I2C
        dwMechanical     00000000 
        dwFeatures       000207B2
          Auto configuration based on ATR
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          CCID can set ICC in clock stop mode
          NAD value other than 0x00 accepted
          Auto IFSD exchange
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              4 Sgchip Dual Reader PICC
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             2  T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      250000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             256
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       00020040
          Auto parameter negotation made by CCID
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              5 Sgchip Dual Reader SAM 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              6 Sgchip Dual Reader SAM2
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
}}}


{{{
$ sudo VBoxManage list -l usbhost
Host USB Devices:

UUID:               4a8de244-7a20-4628-b37b-ccf8dc8d5eb3
VendorId:           0x147e (147E)
ProductId:          0x1002 (1002)
Revision:           0.72 (0072)
Port:               2
USB version/speed:  1/Full
Manufacturer:       UPEK
Product:            TouchStrip Fingerprint Sensor      
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3//device:/dev/vboxusb/001/004
Current State:      Captured

UUID:               2d39f89a-f8da-491e-8fdd-83194944aaf9
VendorId:           0x093a (093A)
ProductId:          0x2510 (2510)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  1/Low
Manufacturer:       PixArt
Product:            USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               38696f50-c6ad-4b9c-8953-48d5beda95bd
VendorId:           0x04f2 (04F2)
ProductId:          0xb2ea (B2EA)
Revision:           5.24 (0524)
Port:               5
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co., Ltd.
Product:            Integrated Camera
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6//device:/dev/vboxusb/001/006
Current State:      Busy

}}}


{{{
$ dmesg
...
[13121.127104] usb 1-1.2: new full-speed USB device number 8 using ehci-pci
[13121.243283] usb 1-1.2: New USB device found, idVendor=0000, idProduct=a180
[13121.243287] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13121.243290] usb 1-1.2: Product: Sgchip Smart Card Reader
[13121.243292] usb 1-1.2: Manufacturer: NARI

}}}


I have properly working Virtualbox and full list of USB devices available inside Windows guest OS. The problem I face is that a specific USB serial device 0000:a180 is not properly exposed by ""VBoxManage list -l usbhost"" and respectively not properly passed-through to Windows guest. All other devices are properly passed-through.

",XiaoQ
18145,Installing VB 5.2 and VB 5.1 are not installing on my system.,Mac OS X,other,VirtualBox 5.2.22,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
18150,Extremely sluggish mouse movement on macOS,other,Linux,VirtualBox 5.2.22,2018-11-30T00:56:15Z,2018-11-30T00:56:15Z,"Dear fellow developers!

I've been a long-time user of VirtualBox and I've come to appreciate it for it's stable set of features and the fact that it is cross-platform and thus available anywhere. However, with the latest couple of versions, I've run into some real issues. The visual performance is severely degraded. Also, every time I shut down a virtual machine, VirtualBox crashes. I've done a screen recording: https://youtu.be/ndXNDt9kXAY on an example VM running AndroidX86, but I've also observed this on other Linux VMs.

I first noticed this a few months ago when I got a new machine (MacBook Pro 13"" 2017). I initially assumed it was just a bug from a rushed release, but after a couple new releases nothing has changed and unfortunately, VirtualBox is not really usable like this for me.

Could you please look into it? I'm happy to run any kind of diagnostics or try stuff out.

Greetings,
xfbs",xfbs
18154,Windows 10 Pro Host 64-bit only supports 32-bit OS,all,all,VirtualBox 5.2.22,2018-11-30T01:38:59Z,2018-11-30T01:38:59Z,"I already checked in the BIOS and I have the intel virtual technology option enabled, what additional information do you need to help me with this case, thanks",jesusemarquezz
18155,Unknown fatal error!,Windows,other,VirtualBox 5.2.22,2018-11-30T01:55:31Z,2018-11-30T01:55:31Z,Virtual box for Windows 7 x64.,AlnXpr
18158,Windows does not start when the virtual machine is allocated 9 or more processors,other,other,VirtualBox 5.2.22,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
18160,Virtual Box machines fail to start after migration from Win7 to Win10,Windows,Linux,VirtualBox 5.2.22,2018-11-30T14:31:46Z,2018-11-30T14:31:46Z,"I upgraded to Windows 10, turned off hyper-v, rebooted, etc.: I can create new 64bit machines, I can run rescue disk .iso in them but existing machines fail to start.",aivarsk
18161,Sound truncates on Windows XP,Windows,Windows,VirtualBox 5.2.22,2018-11-30T14:36:46Z,2018-11-30T14:36:46Z,"Hi

I use Windows XP for using Microsoft Encarta Encyclopedia 99. It may be a bit outdated, but just because something is a bit outdated does not necessarily mean it has lost its charm. The problem I have with Windows XP is that the sound truncates just before the sound clip ends. For example, when I hear the sound clip that is supposed to go ""That's one small step for man. One giant leap for mankind."", it actually goes ""That's one small step for man. One giant leap for--"" and all the other sound clip ends just like that and it is very annoying. I would appreciate your help.",Lukester
18162,Linux guest cannot perform large USB requests,Mac OS X,Linux,VirtualBox 5.2.22,2018-12-01T19:30:17Z,2018-12-01T19:30:17Z,"I have a Starlight Express Trius SX-56 astrophotography camera. This camera performs image transfers as single USB bulk transfers. Due to the large sensor size, these transfers are 32MB in size. While this is larger than the default memory size for usbfs in the kernel (16MB), by writing a larger number to /sys/module/usbcore/parameters/usbfs_memory_mb, this limit can easily be extended. However, that does not make the camera work in a VirtualBox virtual machine. It turns out that the 32MB request formulated in the guest arrives as a 5MB request in the host (tested on MacOS mojave, USB packets inspected with Wireshark on MacOS host and Linux guest). The camera cannot handle this short request and locks up.",Andreas Müller
18163,Guest property LoggedInUsers does not work with 'wait' in VBoxManage,Windows,Linux,VirtualBox 5.2.22,2018-12-02T17:47:06Z,2018-12-02T17:47:06Z,"To wait for a machine to be ready for logins I used

    vboxmanage guestproperty wait <machine> /VirtualBox/GuestProperty/OS/LoggedInUsers

At some point (before 5.2.22) that stopped working. You can still 'get' that property, and it is listed with 'enumerate' for a running <machine>.",thoni56
18164,FUll screen with VBox 5.2.22 on windows 7,Windows,Linux,VirtualBox 5.2.22,2018-12-02T17:50:11Z,2018-12-02T17:50:11Z,"Hi,
I have been using fedora as guest system on windows 7 hosted VBox since years. Yesterday I upgraded from 5.2.18 to 5.2.22 and installed also the vbox additions for it under fedora 29 (linux 4.19).
As a result of this upgrade, suddenly full screen does not work, only normal window mode as well as the adaptive mode (Host-C) are working. Switching to full screen results in the screen freezing - reacting neither to mouse nor to keyboard.",TomKov
18165,Problem to open all VM's,other,all,VirtualBox 5.2.22,2018-12-03T05:55:08Z,2018-12-03T05:55:08Z,I have in Virtual box two VM (Linux Ubuntu and Windows 10) but all the VM don't open . I have an error but I can't resolve it. [[Image()]]Can i have one help ??,Cris96
18166,Ryzen 1700x - no 64 bit option,Windows,Linux,VirtualBox 5.2.22,2018-12-03T05:56:39Z,2018-12-03T05:56:39Z,"Hello,
- I have windows 10
- I have a ryzen 1700X.
- SVM is enabled in the BIOS.
- HyperV is not installed.
VirtualBox won't let me chose a 64 bit option for guestn or even if i try 32bit it won't let me give it more than 1 core.
thanks for the help.",Wolfkiller
18167,"Shared Folders: if disk removed from host, all disks don't auto-mount in guest",all,Linux,VirtualBox 5.2.22,2018-12-04T00:30:30Z,2018-12-04T00:30:30Z,"Host: Win7 + VBox 5.2.22 (tried 6.0-BETA3)

Guest: Debian Linux 9

I have multiple mounts enabled:
1. DRIVE_C
2. DRIVE_D
3. DRIVE_E
4. DRIVE_F


now... I have removed drive D from host (physically disconnecting HDD).
what happens next is that Auto-mount only works for Disk C, then it fails for D (expected), but also for Disk E and F... (which must not happen).
Every letter is physically separate HDD.

{{{
root@deb9ws:~# ls /media/sf_C_DRIVE/                                                                                                                                                                              
$Recycle.Bin  Documents and Settings  Install-UltraISO  PerfLogs             Python26                   Temp        WinBoard-4.8.0  hiberfil.sys  virtualbox-opennodes-2018-12-03                                 
$WINDOWS.~BT  Dropbox                 Install.log       Program Files        Recovery                   Temp-Music  Windows         log.log       win32-loader                                                    
$Windows.~WS  Fraps                   Intel             Program Files (x86)  SIERRA                     Temp2       csb.log         log.txt                                                                       
Config.Msi    Games                   NeroHistory_All   ProgramData          System Volume Information  Users       found.000       pagefile.sys                                                                  
root@deb9ws:~# ls /media/sf_D_DRIVE/
root@deb9ws:~# ls /media/sf_E_DRIVE/
root@deb9ws:~# ls /media/sf_F_DRIVE/
}}}


-Technologov. 04.12.2018.",Technologov
18157,keys repeat (example: moving the cursor) will make shift or control key stick,Linux,Windows,VirtualBox 5.2.10,2018-12-05T01:56:28Z,2018-12-05T01:56:28Z,"Hello,

I have a problem with the indiscriminately activation of caps-lock and/or ctrl while typing, moving the cursor or selecting text.

This symptom will happen if I use one key very long (selecting text...) . (Not often and not exact reproducible, but several times a day.)


'''Host is:'''
- Linux Mint 19 Tara / Cinnamon (freshly installed 8 Weeks ago)
- 2 different computers (physical identical and with similar installation) with the same problem!
- 16 GB Ram, i3 CPU
- ASRock H370M ITX ac / BIOS v3
- Onboard/CPU graphics
- Virtual Box 5.2.10


'''Guest is:'''
- Windows 7 (several installations (old converted computer and freshley installed also))
- Guest Additions are also installed
- USB Additions are also installed... but the issue was earlier as this installation

- no test with Linux as guest!


'''Annoying:'''
- text will be selected if virtualbox thinks that shift is pressed
OR
- the cursor jumps by word like the ctrl key is pressed

This can change in ""one session"" of this issue. (selecting ... jumping ... selecting)

 
'''
I'm able to ""solve"" the problem with:'''
continue with selecting text!  cursor right ..... cursor left ..... cursor up and down.... 
watching if text is selected (blue) while the cursor is moving the text.

No typing of Letters is possible, because every character is combinated with the ""virtual ctrl"" or the ""virtual shift"" key. Result: typing ""s"" is combinated with ctrl to: save my document... and so on.

Clicking with the mouse (on a existing document in task bar) will cause to open a very new document. I'm not able to get into an opened document with the mouse via taskbar. Every mouse-click will open an new instance of the program.



'''I can see ""this"" before the issue begins:'''
- If I move the cursor along the line the cursor has a certain speed. Very short time before the issue starts, the speed will reduce a little bit.

- While the issue is active the cursor has his regular speed.

short time before the issue ""ends"" (for an hour or two or 15 minutes) the speed of the cursor is reduced  to zero. Sometimes the issue has a continuation. Sometimes the issue ends and regular work is possible.

This can last up to 5 minutes!

The reboot of the guest is no real solution. Sometimes the issue takes part within 5 minutes.

The time itself is no factor: If I leave the computer for a while, the issue is still alive.
ONLY continuous run over the timer will solve the problem.


'''the keyboard''' 
is working fine in Linux! No ""virtual ctrl"" or ""virtual shift"" key.


'''Any open questions?'''
- what is needed? (log-files, list of installed programs, ...?)


''Any ideas?
''

regards
Linu
",Galin
18050,White screen after Windows or other VM restart,Mac OS X,Windows,VirtualBox 5.2.18,2018-12-06T13:05:22Z,2018-12-06T13:05:22Z,"Every time I restart Windows to install an update to Windows or another Vm running Linux, it displays a white screen in MacOS Mojave",Neptune BSC LLC
16830,VM Manager does not remember its restored window size,Windows,other,VirtualBox 5.1.22,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
18138,Please add a fedora 29 repo,Linux,other,VirtualBox 5.2.22,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
16097,3D acceleration no work on Win10 With Intel HD3000,Windows,Windows,VirtualBox 5.1.6,2018-12-09T21:21:14Z,2018-12-09T21:21:14Z,"When open a software use 3D like OpenGL or DirectX on guest OS, It go stuck.(even dxdiag.exe)
Host OS is Windows 10 with Intel HD3000 Graphic.
This is a topic from forum following this problem: https://forums.virtualbox.org/viewtopic.php?f=6&t=79820",Yanfeng
16075,"VBox ""draganddrop"" CPU Spike on Ubuntu Guest",Windows,Linux,VirtualBox 5.0.18,2018-12-10T11:10:40Z,2018-12-10T11:10:40Z,"Version: 5.0.18_Ubuntur106667
Host: Windows 7 Professional Service Pack 1 64-Bit
Guest: Ubuntu 16.04 LTS 64-Bit

I have a very peculiar issue with VirtualBox. To replicate on my machine:
1) Open Guest to desktop and leave open in one window
2) Open windows explorer and place on top of Guest
3) Drag arbitrary file from window on top of Guest to anywhere outside Guest, ensuring cursor with file moves over any section of Guest.
4) CPU immediately spikes to 100% with the two processes of the name ""/usr/bin/VBoxClient --draganddrop"" using the highest percentages

I've attached my logs to this ticket.",craymichael
18175,"Windows 10 build 1709 build 16299 64bit VM is not working showing error as ""Error In supR3HardenedWinReSpawn""",Windows,other,VirtualBox 5.2.22,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
13108,Guest mouse cursor range limited without guest additions installed,Windows,all,VirtualBox 4.3.12,2018-12-11T13:28:24Z,2018-12-11T13:28:24Z,"When using a guest OS without VirtualBox Guest Additions installed, the guest mouse cursor can only be moved within a part of the guest desktop.  Before the guest mouse cursor reaches the edge of the desktop, the cursor suddenly jumps outside the guest window and appears on the host OS desktop.

The problem happens in version 4.3.12 and 4.2.24 as well as previous versions.  The specific host OS is Windows 7 Professional SP1 and the guest OS is Windows XP SP3 (without guest additions).   The same problem happens for other guest operating systems without guest additions installed.

The display resolution on the host OS is higher than that of the guest OS.  The host OS resolution is 1680 x 1050.  The guest OS resolution is 1024 x 768.

It appears that the mouse becomes un-captured when the (invisible) host cursor position moves outside the guest window.  The cursor in the guest moves slower than in the host, so the guest cursor has not reached the edge of the guest desktop.  Either the mouse should remain captured, or the mouse position in the host should be converted to the correct guest position based on the different screen resolutions.

The problem also happens in full screen mode.  The guest display uses only a portion of the host screen, and the guest mouse cursor stops moving when the (invisible) host cursor moves outside the guest portion of the screen.  The host mouse cursor reappears before the guest cursor has moved to the edge of the guest desktop.

This problem makes VirtualBox very difficult to use with boot CDs or operating systems not supported by guest additions.  In some very old versions of VirtualBox (3.x) this problem did not occur.  I frequently use VirtualBox to test boot CDs that I have created for backup, partitioning and encryption software.",ErikW
16380,Mouse pointer disappears after VM resume,Linux,Linux,VirtualBox 5.1.12,2018-12-11T20:44:10Z,2018-12-11T20:44:10Z,"When I resume my Linux VM, the mouse cursor is never visible when moved into the VM window.

The mouse appears to be working correctly, as I can see icons / menus become ""highlighted"" when I move the mouse around.

And mouse clicks also work as expected.

It's just that the cursor itself is invisible !!

This issue is never present when starting the VM from scratch.[[br]]
It *only* happens when starting from a suspend.

Host : Ubuntu 16.04.1 LTS (64bit)[[br]]
Guest : Ubuntu 16.04.1 LTS (64bit)

Both host and guest are fully up-to-date.",mpfj
18179,Error unclear when cloning and default vm folder is not available,Linux,all,VirtualBox 5.2.22,2018-12-12T09:56:10Z,2018-12-12T09:56:10Z,"Hi, I think there should be a more readable error when you try to clone a vm and the default vm folder is not available (e.g. was an external drive, now unplugged). On 5.2.22 on Linux I only get a generic VBOX_E_IPRT_ERROR.

To reproduce:
- Configure the default vm folder to a new position
- Render the position unavailable (rename, remove, unplug)
- Create a linked clone of a vm
- A snapshot is created on the original vm
- Error VBOX_E_IPRT_ERROR appears

I think it should say that folder xyz is not available, would make troubleshooting faster.",ctrl
18178,NAT driver drops inbound retransmits that happen after FIN,other,other,VirtualBox 5.2.22,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
18180,"Linux host, Windows and Linux guests: CPU does not exceed 1.99GHz",Linux,other,VirtualBox 5.2.22,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
16683,DHCP Reservations,other,other,VirtualBox 5.1.20,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
18181,"Windows guest, Linux host: copying directories from host to guest copies top-level directories only, not contents",Windows,Linux,VirtualBox 5.2.22,2018-12-13T18:25:21Z,2018-12-13T18:25:21Z,"Virtual Box test build 5.2.23
Host: Windows 8.1 x64
Guest: Linux Mint 19.1 x64 beta, Cinnamon.

Guest Additions installed. Bidirectional clipboard enabled.

Copying directory D1, with contents directory D2 and file F1, copies only D1.

The same setup, but with a Linux Mint 19.0 host, does not seem to have the problem.",JN
18169,Guest Additions will not install properly in Centos,Linux,Linux,VirtualBox 5.2.22,2018-12-14T10:19:53Z,2018-12-14T10:19:53Z,"{{{
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_unpin’:
/tmp/vbox.0/vbox_ttm.c:486:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_push_sysram’:
/tmp/vbox.0/vbox_ttm.c:525:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
make[2]: *** [/tmp/vbox.0/vbox_ttm.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxvideo] Error 2
}}}",bc
18186,Audio Lipsync Problem with VBox 5.2.22,Windows,Windows,VirtualBox 5.2.22,2018-12-15T17:28:58Z,2018-12-15T17:28:58Z,"When I upgraded to VBox 5.2.22 I get audio lipsync errors in games using the 3D support from the extensions pack disk.

Downgrading back to VBox 5.2.18 the audio lipsync is fine again.

I am using Windows 7 Home Premium 64bit as the host and Windows XP 32bit as the guest.

I can run OFP GOTY edition (Bohemia Interactive Operation Flashpoint) very well under these conditions, I do this because it is impossible to install video drivers for my hardware into Windows XP and the game will only run under Windows XP.
",Solrac42
18185,"Windows host removes HardDisks section if the version attribute is ""1.15-macosx""",all,Windows,VirtualBox 5.2.22,2018-12-15T17:30:39Z,2018-12-15T17:30:39Z,"I have a Windows guest that I open in both Mac and Windows hosts. The Mac is the laptop that I use when I'm working remotely, and the Windows is my home office computer.

Usually, there isn't a problem with that, as long as I do a full shutdown of the guest before switching.

However, it seems that the Windows host will sometimes delete the MediaRegistry/HardDisks section in the .vbox file on opening if it has a version of ""1.15-macosx"". The same file is untouched if it has a version of ""1.15-windows"".

All of the changes that it does:
 - Removes MediaRegistry/HardDisks section
 - Sets Memory RAMSize from 8192 to 128
 - Removes Hardware/Display
 - Removes Hardware/VideoCapture
 - Removes Hardware/BIOS
 - Removes child elements and all attributes except type=""Am79C973"" from Network/Adapter slot=""0""
 - Removes Hardware/Clipboard
 - Removes Hardware/DragAndDrop
 - Removes StorageControllers",Shonn
18189,"VirtualBox created ""System Volume Information"" folder in all Shared Folders on Host on Version 6.0 RC1",Mac OS X,Windows,,2018-12-16T17:54:34Z,2018-12-16T17:54:34Z,"I've got 4 shared folders on my VM
VirtualBox 6.0 RC1 created a ""System Volume Information"" folder in all Shared Folders on my Host 
I'm on Mac OS X MOJAVE 
The Guest is Windows 10 64bits",jlavancier
7633,Add an example of scan codes for VBoxManage controlvm,other,other,VirtualBox 3.2.10,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
18016,Mouse problem with Win10 1809 guest and two displays,Linux,Windows,VirtualBox 5.2.18,2018-12-17T11:33:59Z,2018-12-17T11:33:59Z,"Hi,
using the latest Win10 build causes a problem when using two displays: The cursor is not in place 'where the action is' (sorry, don't have better words to describe it). There is kind of an offset that gets larger the more I move the mouse to the right. You point the mouse to a desktop icon, and another icon to the right gets highlighted. Happened after updating the guest to Win10 1809. With one display all is fine.
Host: Laptop with core-i5, two additional 1080p-displays (VGA and HDMI), Mageia Linux 6 (64bit), VBox 5.2.18, kernel 4.14.70
Guest: Windows 10 Version 1809 build 17763.1, 64bit",Squonk
18190,WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX,Windows,Windows,VirtualBox 5.2.22,2018-12-17T12:03:43Z,2018-12-17T12:03:43Z,"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY.",dannyo1
18191,VirtualBox VM start crashes Win10 host inside a Linux KVM,other,other,VirtualBox 5.2.22,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
18184,arp fails when connecting to a wireless connection on host via bridged network,Windows,other,VirtualBox 5.2.22,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
18196,OSX GAs binaries not in OSX guest path,Mac OS X,OSX Server,VirtualBox 6.0.0,2018-12-18T21:04:40Z,2018-12-18T21:04:40Z,"On Linux based systems the Guest Additions are installed in several places, one being the actual binary (`/opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl`), with two additional links:
{{{
$ whereis VBoxControl
VBoxControl: /usr/bin/VBoxControl /usr/bin/X11/VBoxControl /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl

 $ ls -al /usr/bin/VBoxControl /usr/bin/X11/VBoxControl /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
-rwxr-xr-x 1 root root 911520 Dec  18 13:45 /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
lrwxrwxrwx 1 root root     45 Dec  18 22:27 /usr/bin/VBoxControl -> /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
lrwxrwxrwx 1 root root     45 Dec  18 22:27 /usr/bin/X11/VBoxControl -> /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
}}}
On an OSX guest however only the actual binary(ies) are installed, with no additional links in the Path:
{{{
$ locate VBoxControl
/Library/Application Support/VirtualBox Guest Additions/VBoxControl
/Library/Application Support/VirtualBox Guest Additions/VBoxControl-amd64

$ ls -al /Library/Application\ Support/VirtualBox\ Guest\ Additions/VBoxControl \
         /Library/Application\ Support/VirtualBox\ Guest\ Additions/VBoxControl-amd64 
-rwxr-xr-x  1 root  wheel  907364 Dec 18 13:45 /Library/Application Support/VirtualBox Guest Additions/VBoxControl
-rwxr-xr-x  1 root  wheel  907364 Dec 18 13:45 /Library/Application Support/VirtualBox Guest Additions/VBoxControl-amd64
}}}
Please consider adding symbolic links for the !VirtualBox programs in the Path, wherever this is allowed by the OSX policy (most probably ""`/usr/local/bin`""):
{{{
$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
}}}
It's going to make it easier/less awkward...",Socratis
18188,WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX,Windows,Windows,VirtualBox 5.2.22,2018-12-18T23:14:41Z,2018-12-18T23:14:41Z,"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY.",dannyo1
18201,Menues detached from top bar in UI,Linux,all,VirtualBox 6.0.0,2018-12-18T23:18:44Z,2018-12-18T23:18:44Z,"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5. 

On the higher resolution screens, the menubar elements attached to guest machines ('File Machine View Input...') are detached from the top bar. 
",ronabop
18193,"Increase vCore limit, 32 Cores are not enough",other,other,VirtualBox 5.2.22,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
18183,vbox-dkms  modules (vboxnetadp vboxdrv) compilation error  against kernel 4.20.0-rc6 -> fixed after (not in) 5.2.22,Linux,other,VirtualBox 5.2.22,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
18203,Confirmation box to Remove Machine with Delete all files,Windows,all,VirtualBox 5.2.18,2018-12-20T05:48:06Z,2018-12-20T05:48:06Z,"Machine is deleted immediately after pressing Delete all files.
There should be some confirmation box to remove all files :).",twom
18195,CentOS 7 boot hangs after installing Guest Additions,Mac OS X,Linux,VirtualBox 5.2.20,2018-12-20T07:37:12Z,2018-12-20T07:37:12Z,"
Host: Mac OS
Guest: CentOS 7
VirtualBox Version: 5.2.20 r125813 (Qt5.6.3)

I installed ""Guest Additions"" and restarted my CentOS. Since the CentOS doesn't boot....  it hangs while booting. 
",Harish
18209,Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox,Windows,Linux,VirtualBox 6.0.0,2018-12-20T11:25:32Z,2018-12-20T11:25:32Z,"Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox, and it does not report to guest system that this CPU supports AVX512 instruction sets. I tried to modify CPUID data for guest, but after doing so Linux guest was not able to boot, so looks that some extra support on VBox side it needed too.

VBoxManage.exe list hostcpuids
Host CPUIDs:

Leaf no.  EAX      EBX      ECX      EDX
00000000  00000016 756e6547 6c65746e 49656e69
00000001  00050654 04100800 7ffefbff bfebfbff
00000002  76036301 00f0b6ff 00000000 00c30000
00000003  00000000 00000000 00000000 00000000
00000004  1c004121 01c0003f 0000003f 00000000
00000005  00000040 00000040 00000003 00002020
00000006  00000ef5 00000002 00000009 00000000
00000007  00000000 d39ffffb 00000000 9c000000
00000008  00000000 00000000 00000000 00000000
00000009  00000000 00000000 00000000 00000000
0000000a  07300804 00000000 00000000 00000603
0000000b  00000001 00000001 00000100 00000004
0000000c  00000000 00000000 00000000 00000000
0000000d  000000ff 00000a80 00000a80 00000000
0000000e  00000000 00000000 00000000 00000000
0000000f  00000000 0000002f 00000000 00000002
00000010  00000000 0000000a 00000000 00000000
00000011  00000000 00000000 00000000 00000000
00000012  00000000 00000000 00000000 00000000
00000013  00000000 00000000 00000000 00000000
00000014  00000001 0000000f 00000007 00000000
00000015  00000002 000000f2 00000000 00000000
00000016  00000b54 00000b54 00000064 00000000
00000017  00000b54 00000b54 00000064 00000000
80000000  80000008 00000000 00000000 00000000
80000001  00000000 00000000 00000121 2c100800
80000002  65746e49 2952286c 6f655820 2952286e
80000003  322d5720 20323031 20555043 2e322040
80000004  48473039 0000007a 00000000 00000000
80000005  00000000 00000000 00000000 00000000
80000006  00000000 00000000 01006040 00000000
80000007  00000000 00000000 00000000 00000100
80000008  0000302e 00000000 00000000 00000000
80000009  00000b54 00000b54 00000064 00000000",SirZooro
18098,Screen does not refresh when connecting over RDP,other,other,VirtualBox 5.2.20,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
18222,Problem with VBoxAutostart and possible workaround,Linux,all,VirtualBox 6.0.0,2018-12-22T10:39:26Z,2018-12-22T10:39:26Z,"Hello,
in the last days I've discovered a problem which seems to be a bug in the virtualbox autostart service. Here follows the overview now:

How to reproduce?
Create several virtual machines and add them to the autostart of VirtualBox by following e.g. that guide (it doesn't matter which you choose) https://pgaskin.net/linux-tips/configuring-virtualbox-autostart/ . Now set also the ""autostop-type"" of all your autostart VMs to ""savestate"". If you reboot your system now, all VMs will crash and only the first VM will be automatically started, the rest stays off.

What is my system?
It could be reproduced using a fresh installed debian 9 and the virtualbox version 6-RC1 (installed by https://wiki.debian.org/VirtualBox).

What is the reason for that failure?
If you add more than two VMs to the autostart, the script ""vboxautostart-service.sh"" will start in the line
{{{
start_daemon `basename $user | sed -ne ""s/\(.*\).start/\1/p""` $binary $PARAMS > /dev/null 2>&1
}}}
multiple instances of VBoxAutostart - the second one will crash, because an other instace is already running. That causes a return of the exit code of 1 - the systemd envroiment (activated by that file /lib/systemd/system/vboxautostart-service.service) take that as a failure of the service and marks it as crashed too. If you now try to stop the service by hand or reboots the system systemd will (i guess) skip the stop part of the script, because the service is not running / crashed - regardless that a VM is running. That causes the system not to stop and wait for the VMs and let them crash.

How to fix?
Simply remove the ""--background""-flag from the parameter list of the start procedure.
{{{
PARAMS=""--background --start --config $VBOXAUTOSTART_CONFIG""
}}}
->
{{{
PARAMS=""--start --config $VBOXAUTOSTART_CONFIG""
}}}
Now the bootup maybe takes some more time, but all VMs are started correctly and also gets correctly shutdowned impliced by the ""autostop-type"" setting.

Thanks for reading this (short) report,
Simonmicro",Simonmicro
18208,VMs with a PIPE in the name cannot be moved in groups,Windows,all,VirtualBox 6.0.0,2018-12-23T17:46:13Z,2018-12-23T17:46:13Z,"If a machine has a PIPE (|) in its name it cannot be moved in or out a group because the config file of the machine (vbox) cannot be edited.

If I rename the VM and replace the pipe with another character (i.e. a minus or a space) it works perfectly.",KevinW
18217,Stealing ram,other,other,VirtualBox 6.0.0,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
16489,Cannot set VM icon,Windows,Windows,VirtualBox 5.1.14,2018-12-24T17:02:42Z,2018-12-24T17:02:42Z,"While reading the manual I came across the vboxmanage command 'vboxmanage modifyvm VMNAME --iconfile'
According to the manual you can change the icon for the VM. I could not find anything else in the manual to emailed the iconfile specs (file type/resolution).
I tried to run the command and gave it the absolute path to a 128x128 .png file but the icon for the VM did not change. 
Is there more information for the --iconfile command? ",fletch
18231,unable to see mouse pointer in guest,Windows,Linux,VirtualBox 6.0.0,2018-12-24T21:56:53Z,2018-12-24T21:56:53Z,,kapstone
18229,CentOS VM does not start after virtual guest additions 5.2.22 upgradation,Windows,Linux,VirtualBox 5.2.22,2018-12-24T22:28:28Z,2018-12-24T22:28:28Z,"My CentOS VM was running fine in Windows 10, Virtualbox 5.2.18 . But after updating it to 5.2.22 and installing the guest additions 5.2.22, it does start. It gives error during boot : Job x11vnc.service/start deleted to break ordering cycle started with multi-user.target/start. My Caps lock led keeps blinking and I have to shutdown the VM.",anupam.m
18232,RFE: Cloning a VM from the GUI should place the cloned VM right below the original in the list,all,all,VirtualBox 6.0.0,2018-12-25T09:12:49Z,2018-12-25T09:12:49Z,"This is a Request For Enhancement. When you're cloning a VM, chances are that you'll need to have it close to the original in the VM list (left side of the !VirtualBox Manager). Currently the cloned VM ends in the bottom of the list. If you have about 80 or more VMs it makes it cumbersome to scroll all the way to the bottom of the list, and drag the cloned VM all the way next to the original.

I'm proposing to have the cloned VM placed right below the original VM in the list after the cloning process.

A similar logic was introduced recently with the Deletion of a VM, where you don't end up in the beginning of the list, but you ""land"" to a VM close to the one that was deleted. BTW, thank you for that!",Socratis
18182,Latest Insider Build Sound Driver Broke,Linux,Windows,VirtualBox 5.2.22,2018-12-26T19:16:15Z,2018-12-26T19:16:15Z,"Running build 18298, sound driver not working on Windows 10 guest, Ubuntu 18.10 host. Getting error in Device Manager:
该设备无法启动。 (代码 10)

{操作失败}
请求的操作不成功。

Or Google Translate: The device could not be started. (Code 10)

{operation failed}
The requested operation was unsuccessful.


Using Virtualbox 5.2.22 r126460.",Paul Stejskal
18194,netplan bond not working (ubuntu 18.04),all,Linux,VirtualBox 5.2.22,2018-12-27T17:17:21Z,2018-12-27T17:17:21Z,"Hey guys,

today I set up a network bond environment under Ubuntu 18.04 (4.15.0-42-generic). After running ""sudo netplan apply"" interface ""bond0"" with the given IP comes up. But it is not possible to tranfer any packets through this interface, neither in nor out.
This issue exists with the latest dev versions of !VirtualBox 5.2 and 6, too.

My netplan configuration:
{{{
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: no
      dhcp6: no
    eth1:
      dhcp4: no
      dhcp6: no
  bonds:
    bond0:
      dhcp4: no
      dhcp6: no
      interfaces: [eth0, eth1]
      addresses: [192.168.56.81/24]
      parameters:
        mode: active-backup
        mii-monitor-interval: 100
        primary: eth0
}}}",lemerp
18241,unable to install centos in VM. Facing error which says kernel panic,Windows,other,VirtualBox 6.0.0,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
13187,VirtualBox 4.3.14 can't start VMs on certain Windows hosts,Windows,other,VirtualBox 4.3.14,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
18236,Screen distortion with Cadence Allegro 17.2,other,other,VirtualBox 6.0.0,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
18251,Unable to mount shared windows folder to Linux via VirtualBox,Windows,Linux,VirtualBox 5.2.20,2018-12-30T20:57:08Z,2018-12-30T20:57:08Z,"Unable to mount shared windows folder to Linux via VirtualBox

I am following steps mentioned in the below below blog 
https://blogs.sap.com/2017/09/04/newbies-guide-installing-abap-as-751-sp02-on-linux/

I am using Version 5.2.22 r126460 (Qt5.6.2) VirtualBox - I installed Linux  openSUSE-Leap-42.3-DVD-x86_64.iso version. 

The config goes through fine in Virtual Box but when I look for the cd /media/sf_s4installer folder ( media folder) - it is not available in Linux. 

Please help. 

Thanks,
Rama 
",Rama
18256,Install failure for VB6.0.0 on openSUSE Tumbleweed,other,other,VirtualBox 6.0.0,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
18254,Windows 10 VM disconnected shared drive drive Z:,other,Windows,VirtualBox 6.0.0,2018-12-31T18:57:40Z,2018-12-31T18:57:40Z,"This communication concerns an issue whereby subsequent logins to a Windows 10 Pro based VM show a disconnected drive Z:, even though you can still navigate to it.

Please be kind enough to see the attached (I hope ;) ) PDF file, which explains the whole issue, together with images.

With kindest regards

David",DJB
2935,BIOS support for booting from usb devices,other,other,VirtualBox 3.1.6,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
18255,Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors.,Linux,Windows,VirtualBox 5.2.22,2019-01-02T11:21:33Z,2019-01-02T11:21:33Z,"Host : Ubuntu 16.04
Host System: NVIDIA Graphics, i7 core, 24 GB RAM
VirtualBox Client: Windows 10
worked with VirtualBox 5.2
Issues that the second screen has only 1280x1024 instead of 1600 x1200

That was working before I run the machine today.I have not worked for month with the target.

An update to 5.2.22 was announced. I clicked it away. Then I got the small issue mentioned above. I decided to do the update. On the homepage 6.0 was announced instead of 5.2.22. So I downloaded the deb-File for 16.04. Ubuntu Software Center could not install it. Old version has been still installed at this time. But then followed the instructions on the page and downloaded and installed it by command line adding the repo for it.

After starting my Windows 10  machine, there was only two very small VGA screens left. After trying to reinstall the vboxguestadditions, there was only one screen left at least with 1280x1024 resultion.

There have been errors installing the guest additions they stuck installing some driver fro VBoxVideoW8 for a ""hardware that is currently not present"". Please see the log.

How can I rescue my windows copy. Because I think something was messed up during installation of VB 6.0 or the guest additions. I meanwhile deleted the vbox in /usr/share/virtualbox but after reinstallation error stays stable. I am not able to continue working on my projects
.

In the end I deinstalled 6.0 and get me a copy of 5.2.22.

Please help save my work, because last time it all worked perfectly!

Best regards
Peter
",peddanet
18266,I met 0X00000000 error when I click the menu->device->usb on windows system.,other,other,VirtualBox 6.0.0,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
18245,Prevent boot if Shared folder is not available or Require Shared folder in order to boot,Linux,Windows,VirtualBox 6.0.0,2019-01-03T16:01:54Z,2019-01-03T16:01:54Z,"I searched but could not find an answer for this. Is there a way to prevent a guest system from booting if the attached Shared Folder is unavailable? I realize you get a prompt disclosing this fact, but I would like to prevent the VM from booting.",jim.rather
18276,Graphic glitches,Windows,Windows,VirtualBox 6.0.0,2019-01-04T01:10:07Z,2019-01-04T01:10:07Z,"When i downloaded the version 6.0.0 (first time install on this computer on all of versions of windows that i installed xp-10)i installed the virtualbox guest additions as well and when i am moving the windows programs i see graphic glitches and problems during moving the window on host and i am using cpu virtualaziation too.


my system specs

AMD A8-9600, 
Kingston 4gb ram ddr4 2666 mhz
, ASRock A320M Pro4 (mb)
 ,Coolermaster masterwattlite 500w 80+
 and Intergrated GPU AMD Radeon R7 ",Undead
18281,Feedback of /sbin/vboxconfig on failing module load not always helpful,Linux,other,VirtualBox 6.0.0,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
18275,Microsoft Agent voice not working,other,Windows,VirtualBox 6.0.0,2019-01-04T15:39:47Z,2019-01-04T15:39:47Z,"Ok, I downloaded BonziBUDDY on a virtual machine running Windows XP Professional Service Pack 3, and the voice isn't there, and the speech bubble freezes and the agent stops its animations (so, freezes)

Is there a fix for this or if Oracle are already on a fix for this?",cso73438
15405,Severe time drift with KVM paravirt and Linux guests,Mac OS X,Linux,VirtualBox 5.0.20,2019-01-05T10:42:46Z,2019-01-05T10:42:46Z,"I see very strong time drift with the kvm paravirt interface, on an OS X host - reproducible with both ""debian/jessie64"" and ""centos/7"". I let it run overnight for a more precise measurement. The guest time drifts very fast:
* 60 host seconds -> 8 guest seconds
* 8h37m host -> 0h53m38s guest

Raw measurements (host time as comment - OS X is set to the Europe/Berlin timezone):
{{{
[vagrant@localhost ~]$ date # 0:59:00
Tue May 10 18:56:18 EDT 2016
[vagrant@localhost ~]$ date # 1:00:00
Tue May 10 18:56:26 EDT 2016
[vagrant@localhost ~]$ date # 9:37:00
Tue May 10 19:50:04 EDT 2016
}}}

I found two workarounds to get a stable time:
1. set the paravirt interface to legacy, instead of kvm
2. use `kvm` as the paravirt interface, but set the guest kernel `clocksource` to `acpi_pm` (`hpet` also works, if i enable it - `tsc` too, i think).

Both the Debian Jessie and CentOS kernels default to `kvm-clock` as its `clocksource`, if KVM is available. I can reproduce this problem with VirtualBox 5.0.20 and 5.0.18 on OS X 10.11.4, both with and without the Guest Additions (I use a NTP daemon in the guest, when the Guest Additions are not installed, but the drift is too big to compensate). The attached log is with the CentOS guest.

The official Vagrant images for CentOS don't come with the Guest Additions preinstalled. If you have Vagrant and Ansible installed on the host, you can use https://github.com/lpancescu/cloud-instance-starter-kit for automatically updating the system and installing the guest additions (you'll need to issue `vagrant reload` after it's done).",lpancescu
18260,Not able to Start VM in Virtual Box when Bridge Adapter Network Setting is Selected After latest update to Windows 10,Windows,Linux,VirtualBox 6.0.0,2019-01-05T15:27:30Z,2019-01-05T15:27:30Z,"Hi Team,

I am Not able to start VM on virtual box when Bridge Adapter Network Setting is Selected and This is seen after latest update to Windows 10.

Have tried all the possible solutions listed in google, Nothing Worked.

Have tried 5.2.18, 5.2.22 and also 6.0 versions of VB but observing same Error on all these version.

Below Error is Observed:

Failed to open a session for the virtual machine .

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Linda
18204,PCI passthrough :invalid region,Linux,Windows,VirtualBox 6.0.0,2019-01-06T11:42:00Z,2019-01-06T11:42:00Z,"'''Host:''' debian 9  amd64

'''CPU:''' AMD

'''Virtualbox:''' 5.2.x , 6.0.0

'''Guest:''' win7  64-bit

'''PCI passthrough :''' AMD GPU

'''lspci -vv  -s1e:00.0'''

{{{
1e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 687f (rev c1) (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 6b76
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 41
        Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
        Region 4: I/O ports at f000 [size=256]
        Region 5: Memory at f7800000 (32-bit, non-prefetchable) [size=512K]
        [virtual] Expansion ROM at f7880000 [disabled] [size=128K]
...
}}}

'''Second GPU:''' (not passthrough)
{{{
1b:00.0 VGA compatible controller: NVIDIA Corporation GP108 
}}}

'''dmesg'''
{{{
[10178.205401] vboxpci: detected device: 1002:687f at 1e:00.0, driver <none>
[10178.205458] pci-stub 0000:1e:00.0: claimed by stub
[10178.205486] vboxPciFileWrite: error -19
[10178.205560] vboxpci 0000:1e:00.0: vboxPciOsDevInit
[10178.205665] vboxpci 0000:1e:00.0: region 0: mmio e0000000+268435456
[10178.205668] vboxpci 0000:1e:00.0: region 2: mmio f0000000+2097152
[10178.205671] vboxpci 0000:1e:00.0: region 4: pio f000+256
[10178.205673] vboxpci 0000:1e:00.0: region 5: mmio f7800000+524288
[10178.205676] vboxpci 0000:1e:00.0: region 6: mmio f7880000+131072
[10178.205697] vboxpci 0000:1e:00.0: got irq 94
[10179.615799] vboxpci: created IOMMU domain ffff8a6575448a20
[10179.667123] vboxpci 0000:1e:00.0: PCIRAW_POWER_ON
[10179.667134] vboxpci 0000:1e:00.0: pci_reset_function() failed
[10179.667182] vboxpci 0000:1e:00.0: attached to IOMMU
[10179.673069] vboxpci 0000:1e:00.0: invalid region 5
[10179.673119] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10179.677495] vboxpci 0000:1e:00.0: invalid region 2
[10185.325467] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10185.327882] vboxpci 0000:1e:00.0: invalid region 2
[10185.327885] vboxpci 0000:1e:00.0: invalid region 5
[10186.596095] vboxpci: freeing IOMMU domain ffff8a699a958c20
[10187.832128] vboxpci 0000:1e:00.0: reg=0 start=e0000000 size=268435456
[10187.836709] vboxpci 0000:1e:00.0: invalid region 2
[10187.836714] vboxpci 0000:1e:00.0: invalid region 5
[10215.836023] vboxpci 0000:1e:00.0: PCIRAW_POWER_OFF
[10215.836071] vboxpci 0000:1e:00.0: detached from IOMMU
[10215.898276] traps: EMT-0[7904] general protection ip:7f1f36e5e1bf sp:7f1f6cff2db0 error:0
[10215.898284]  in VBoxPciRawR3.so[7f1f36e5b000+c000]
[10216.035409] vboxpci 0000:1e:00.0: freeing irq 94
[10216.035428] vboxpci 0000:1e:00.0: vboxPciOsDevDeinit
[10216.035612] vboxpci: freeing IOMMU domain ffff8a6575448a20
[10219.287799] vboxpci: created IOMMU domain ffff8a6a1c90cc20
}}}

Checking out from yours Subversion server. 

'''I think problem is  in file:''' src/VBox/HostDrivers/VBoxPci/linux/VBoxPci-linux.c

'''Method:''' vboxPciOsDevMapRegion

'''Line:'''813  

'''In commit''':75599
{{{
if (!pPciDev || iRegion < 0 || iRegion > 0)
}}}

'''IMHO corect line is:'''
{{{
if (!pPciDev || iRegion < 0 || iRegion > 6)
}}}



'''svn  diff -r58962:58963''' (line 776 in 58962  vs line 787 in 58963)
",svj
18284,Menu- and status-bar centralized (move to Control center) to more view visual space for guest,all,all,VirtualBox 6.0.0,2019-01-06T18:54:33Z,2019-01-06T18:54:33Z,"My future request is: Menu- and status-bar not to only deactivade. It more an request to born a control Center and add it to Virtualbox Manager.

When menu- and status-bar in virtualBox deactivaded is and the title space from virtualBox-window not view, come more visual space but some times menu- and status-bar is helpfuel. But centralized in a separate window / in Virtualbox Manager is better for some users.

Or better add in ""guest Additions"", as Bar on the guest-desktop? But what when guest crash? Better status-bar just optional on guest desktop.",RomaBianca
18261,"VM self-terminates during first boot after install (Virtualbox 6.0 MacOS Mojave 10.14.2 Host, Ubuntu 18.04.1 Guest)",Mac OS X,Linux,VirtualBox 6.0.0,2019-01-07T02:26:14Z,2019-01-07T02:26:14Z,"Not long before the ubuntu login screen would be reached, the VM stops with an error alert box showing (not pointing to anything in particular).

Second boot works fine. I observed this twice.",0x7766
18253,"Windows10 sleep, wake up, VirtualBox(V6.0.0) display: abnormal exit.",Windows,Linux,VirtualBox 6.0.0,2019-01-07T05:10:39Z,2019-01-07T05:10:39Z,"Host Machine System: Windows10 1809
Virtual Machine System: CentOS7.0
Virtual machine running, and then wait 10 minutes not to use Windows system, then Win sleep... Then, wake up Windows, VirtualBox shows: abnormal exit.",solan
16664,"Graphics: extensive pixelation and discoloration with VirtualBox graphcis driver and Aero enabled; Windows 7, 8.1, 10",Windows,Windows,VirtualBox 5.1.18,2019-01-08T13:12:32Z,2019-01-08T13:12:32Z,"I install clean Windows 7/8/1/10 installations.
I then install Guest Additions with the default graphics driver, and restart.
For Windows 7, I manually enable Aero. For Windows 8.1 & 10, this is automatic.
Everything is fine until I start a Windows Installer program, or try to uninstall certain programs.
At this point the display starts to become pixelated and discolored.
Each time I change screens or move the cursor the pixilation becomes worse.

SPECIFICS:
The only way to get rid of the pixilation without restarting the VM is to restore (un-maximize) and maximize the VM display window.
I started noticing this about a month ago.
I tried rolling back the VM additions and graphics drivers to the versions when this wasn't yet a problem, but that does not fix it.
This occurs in Windows 7, 8.1, and 10, in both x86 and x64.
This problem can be avoided by disabling Aero in Windows 7. HOWEVER, disabling Aero transparency does NOT fix Windows 8.1 or 10.
This is not remedied by changing the amount of VM graphics memory, 2D settings, or 3D settings. I tried ALL combinations of enabling and disabling these.
HOST GRAPHICS: NVidia GeForce GTX 970M
HOST OS: Windows 10 x64
LOG: Attached. Starts at VM bootup and ends at first signs of this pixilation.",JMH1
18289,Machine unable to open,Linux,all,VirtualBox 6.0.0,2019-01-08T14:35:46Z,2019-01-08T14:35:46Z,A critical error has occurred while running the virtual machine and the machine execution has been stopped.,sgaur
18287,windows 10 x64 guest crashes (vb restarts the guest windows),Windows,Windows,VirtualBox 6.0.0,2019-01-08T14:44:24Z,2019-01-08T14:44:24Z,"so I have a windows x64 host and a windows x64 guest, from time to time the os of the guest reboots for no reason (no error shown)",xhums1
18252,RFE. VirtualBox 6 MacOS 10.14.2 host with 10.12.6 guest - network share doesn't appear,Mac OS X,other,VirtualBox 6.0.0,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
18149,USB headset disconnection on windows host freezes linux guest,Linux,Linux,VirtualBox 5.2.22,2019-01-10T18:02:43Z,2019-01-10T18:02:43Z,"After disconnecting a USB headset (sennheiser mb 660 uc ms) in the host system, the vm freezes (i.e. is no longer responsive to clicks or any other form of interaction including network access). The VirtualBox GUI is no longer responsive either. Repeatedly clicking in the guest window eventually causes it to abort and the VirtualBox GUI becomes responsive again.

Host: Windows 7 x86_64
Guest: Arch linux x86_64

",oksijun
18300,VNC connect callback problem,Linux,other,VirtualBox 6.0.0,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
18303,No way in the GUI to reset the per-VM scale factor to follow the global one.,all,all,VirtualBox 6.0.0,2019-01-11T19:00:42Z,2019-01-11T19:00:42Z,"If you set ''(even once)'' the per-VM scale factor in VM Settings > Display > Screen > Scale Factor, then an ExtraData item is inserted in the .vbox configuration file:
{{{
<ExtraDataItem name=""GUI/ScaleFactor"" value=""1.5""/>
}}}
Once that setting is there, there's no way to reset it back to follow the global scale factor from the GUI, only from the CLI:
{{{
VBoxManage setextradata <uuid|vmname> ""GUI/ScaleFactor""
}}}
A mechanism is needed, such as a ""`Reset to Defaults`"" or ""`Reset to Global`"" button, where the ExtraData item is removed, and the VM follows the global settings.",Socratis
18302,Can not install VirtualBox Guest Additions in CentOS 6.10,Windows,Linux,VirtualBox 6.0.0,2019-01-12T17:17:14Z,2019-01-12T17:17:14Z,"I am using Vagrant 2.2.3 and I have installed the latest VirtualBox 6 (VirtualBox-6.0.0-127566-Win). My Vagrantfile looks like follow:

{{{
  # -*- mode: ruby -*-
  # vi: set ft=ruby :

  Vagrant.configure(""2"") do |config|
    config.vm.box = ""reynierpm/centos6""
    config.vm.box_version = ""4""

    config.vm.provider :virtualbox do |vb|
      vb.customize [""modifyvm"", :id, ""--memory"", 2048]
    end
  end
}}}

But VirtualBox Guest Additions won't install and fails with the following error:

    VirtualBox Guest Additions: modprobe vboxsf failed

Have tried to install them manually and I got the same result:

{{{
# sh VBoxLinuxAdditions.run                                                          
Verifying archive integrity... All good.                                                                   
Uncompressing VirtualBox 6.0.0 Guest Additions for Linux........                                           
VirtualBox Guest Additions installer                                                                       
Removing installed version 6.0.0 of VirtualBox Guest Additions...                                          
vboxadd-service.sh: Stopping VirtualBox Guest Addition service.                                            
You may need to restart your guest system to finish removing the guest drivers.                            
Copying additional installer modules ...                                                                   
Installing additional modules ...                                                                          
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run                              
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>                                         
VirtualBox Guest Additions: Building the modules for kernel 2.6.32-754.9.1.el6.x86_64.                     
																										   
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong                 
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted      
VirtualBox Guest Additions: Starting.                                                                      
VirtualBox Guest Additions: modprobe vboxsf failed                                                         
}}}

Logs aren't helpful:
{{{
# cat /var/log/vboxadd-setup.log
Could not find the X.Org or XFree86 Window System, skipping.
}}}",reynierpm
18304,VirtualBox 6.0 crashes on Ubuntu 18.10,Linux,other,VirtualBox 6.0.0,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
18297,Can't unmount vdi file,Linux,Linux,VirtualBox 6.0.0,2019-01-12T21:41:45Z,2019-01-12T21:41:45Z,"I just tried to gparted one of the vdi files and I am getting error unmount it. I have two VM setup both are Ubuntu 18.04 with latest updates

VM1 - is what I am booing into (fresh install)
VM2 - is what is attached as additional IDE or SATA to VM1

VM2 was cloned from VM1

Here is what I did try to do

1. in VM1 attach VM2 vdi file. I did try as IDE and SATA each time
2. Boot to VM1
3. Start gparted
4. Select /dev/sda (VM2)
5. Try to resize ext4 partition (Did checked it is not mounted)
6. Apply changes

It seams that /dev/sdb is VM1 what I booted into.

Resize fails

",oxoocoffee
18309,VirtualVox 6.0.0-127566 will not start VMs under latest Windows 10 update,other,other,VirtualBox 6.0.0,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
18307,VM Hang during installing of Centos,Windows,other,VirtualBox 6.0.0,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
18310,Can't change display settings in an Oracle Linux 6.5 guest,Windows,Linux,VirtualBox 6.0.0,2019-01-14T08:37:37Z,2019-01-14T08:37:37Z,"I recently updated to v 6.0.0 r 127566 on Windows 10. All other guests (Debian Linux distros & earlier Windows versions) work fine, except Oracle Linux 6.5. Display becomes garbled when trying to change the resolution after installing the Guest Addition.",whosnick
18311,user interface not accessible any more using nvda screen reader,Windows,other,VirtualBox 6.0.0,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
18214,"VM Crash when hovering optical media menu, with inaccessible media",Windows,other,VirtualBox 6.0.0,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
18306,Virtual box causes the PC to restart many times,Windows,other,VirtualBox 6.0.0,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
18295,VM Audio appears distorted,other,other,VirtualBox 6.0.0,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
18314,"6.0.2 RPM was built for fedora26, while 6.0.0 RPM was built for fedora29. Regression?",Linux,other,VirtualBox 6.0.2,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
14102,Kubuntu 15.04 Guest: 3D acceleration broken,Windows,Linux,VirtualBox 4.3.26,2019-01-16T08:05:02Z,2019-01-16T08:05:02Z,"3d support is unavailable for every KDE5 (Plasma) based Linux distro on Windows Host. Reference
https://forums.virtualbox.org/viewtopic.php?f=3&t=67589&p=320394#p320394
https://forums.virtualbox.org/viewtopic.php?f=6&t=64452

If 3D acceleration is enabled, KDEs login screen appears normally, one can login. After logging in, the Desktop appears, everything seems to be normal. BUT:

1.) Right clicking somewhere at the desktop doesn't bring up the context menu
2.) Clicking the ""KDE"" Menu: the KDE Menu appears, but the Control Bar disappears completely
3.) When starting an application in KDE Menu (which can still be opened with Alt+F1), the application seems to start, but no application window appears
4.) Trying to get out of KDE and switch to a console TTY (STRG+ALT+F1) just switches to a smaller screen but in this KDEs background image remains.
==> So the Desktop is completely unusable, it isn't even possible to get a terminal window, so one even can't examine ""glxinfo"" or some logs...

It looks like the KDE Background lays in front of everything, similar to an ""z-axis 9999""...

After disabling 3D acceleration the Desktops behaves absolutly normal but not with the performance it could have...

My System is this:

Host:
Windows 7 Pro 64Bit
Latest VirtualBox 4.3.26, Extension Pack for 4.3.26 installed

Guest:
Kubuntu 15.04, all current patches installed
GuestAdditions from iso shipped with VirtualBox 4.3.26",sac
18317,Can't install Guest Additions on Solaris 11.4 guest,all,Solaris,VirtualBox 5.2.24,2019-01-17T14:16:50Z,2019-01-17T14:16:50Z,"Hello,

The Solaris Guest Additions have a dependency on a svr4 package named ""SUNWuiu8"" (iconv support). In Solaris 11.3, this dependency was satisfied by installing the IPS package system/library/iconv/utf-8.

{{{
#------Solaris 11.3--------
vagrant@dev-main:~$ uname -a
SunOS dev-main 5.11 11.3 i86pc i386 i86pc
vagrant@dev-main:~$ pkg contents -m system/library/iconv/utf-8 | grep uiu8
legacy arch=sparc category=system desc=""Iconv modules for UTF-8 Locale"" hotline=""Please contact your local service provider"" name=""Iconv modules for UTF-8 Locale"" pkg=SUNWuiu8 variant.arch=sparc vendor=""Oracle Corporation"" version=11.0,REV=2010.12.06
legacy arch=i386 category=system desc=""Iconv modules for UTF-8 Locale"" hotline=""Please contact your local service provider"" name=""Iconv modules for UTF-8 Locale"" pkg=SUNWuiu8 variant.arch=i386 vendor=""Oracle Corporation"" version=11.0,REV=2010.12.06
#------Solaris 11.3--------
}}}

On Solaris 11.4, the utf-8 package was renamed. Also, no packages replacing the utf-8 package contain the legacy line.

{{{
#------Solaris 11.4--------
root@dev-11-4-main:~$ pkg info -r system/library/iconv/utf-8
          Name: system/library/iconv/utf-8
         State: Not installed (Renamed)
    Renamed to: consolidation/l10n/l10n-incorporation
                system/library/iconv/iconv-core@5.12,5.11-5.12.0.0.0.67.6
     Publisher: solaris
       Version: 5.12
        Branch: 5.12.0.0.0.67.6
Packaging Date:  9. Februar 2015 um 04:00:43 Uhr
          Size: 5.46 kB
          FMRI: pkg://solaris/system/library/iconv/utf-8@5.12-5.12.0.0.0.67.6:20150209T040043Z
root@dev-11-4-main:~$ pkg contents -m l10n-incorporation iconv-core | grep uiu8
depend fmri=pkg:/SUNWuiu8@0.5.11,5.11-0.175.1.0.0.9.1162 type=incorporate		  
#------Solaris 11.4--------
}}}

As no package installs the legacy package entry for SUNWuiu8 anymore, the Guest Additions installer complains about the missing package.
I don't know if the iconv stuff is really necessary. If not I would edit the manifest or something to remove the dependency.

Can I do anything else? Is this a VirtualBox bug or is this a Oracle Solaris bug?

Side note: Can't you provide an Guest Additions IPS package? Or is that too much work or can't be generated from the svr4 package?",DANoWAR
18326,Distorted audio on Windows guest after upgrade,Windows,Windows,VirtualBox 6.0.2,2019-01-17T19:46:41Z,2019-01-17T19:46:41Z,"I upgraded my virtualbox installation from 5.2.22 to 6.0.2.

Now, the audio of one of my guests (Windows XP - 32 bits) is completely distorted. Actualy sometimes the sound plays nicely, sometimes distorted, and sometimes it didn't play at all.

I also updated the guest additions, trying to fix the problem, but no luck.

Host: Windows 10 (1809)
 ",rdweb
18199,Roll-over highlighting does not work right/simlarly on my different screens,Linux,all,VirtualBox 6.0.0,2019-01-18T00:03:22Z,2019-01-18T00:03:22Z,"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5.

When the VirtualBox Manager UI is on the 1900x1200 screens, and I ""roll over"" the machines on the left hand side panel, the entries highlight with a blue color.

When the VirtualBox Manager UI is on the 1900x1080 screen, and I roll over the machines on the left hand side panel, the machines highlight with a blue color... but the machine that is highlighted is not the machine my cursor is over.",ronabop
18173,Bridged Adapter not working version 5.2.22,Windows,Windows,VirtualBox 5.2.22,2019-01-18T02:44:59Z,2019-01-18T02:44:59Z,"Using Bridged Adapters with Windows 10 Host and Windows 10 Guest fails to work as expected. The host and the guest can not ping each other , neither can the guest ping anything outside of its own machine. 

This issue I have narrowed down to having a locally administered MAC address with in the Guest machine.  While the work around is to use the VirtualBox setting as the MAC address - this is not the preferred method for portability of the Disk Image File. I had narrowed it down by swapping the bound network interface lan and wifi to network 1 and network 2 and then reversing that - disabling the first network with in the guest (which had the locally administered address) - everything then worked - and I only realized it was the MAC address being locally administered within the guest - because I needed to set it for Network2 at which point everything failed to communicate again. 
I then administered the local mac in the Vbox Settings network page. I would prefer this to be with in the image itself in network properties. If I have several images with the same locally administered MAC , I would think the VBox Bridge would act as the router hop so that I could  have multiple of this image on the same network.



",Ken The Eskimo
18330,Linux Mint 19.1 doesn't display on large monitor,Solaris,Linux,VirtualBox 6.0.2,2019-01-18T23:28:29Z,2019-01-18T23:28:29Z,"I'm running VirtualBox 6.0.2 on Solaris 11.4.
I have a 24"" Sun monitor.

Running Linux Mint 18.1, I can run in full screen just fine.

Running Linux Mint 19.1, if I try to resize the VM window to be close to
the size of the monitor, or run in full screen mode, it only displays a
black screen.  Resizing the window to be smaller causes the display to
appear.

I've installed the 6.0.2 Guest Additions in both cases.

I've updated Linux Mint in both cases.

Even with Linux Mint 18.1, I had at least one case where it would refuse
to use the entire screen size.  I reinstalled the Guest Additions and
then it started working correctly.

Of course all of this could be a problem with Linux Mint, but I have no
idea how to determine that.

I was previously using VirtualBox 6.0.0 with Linux Mint 18.1 and never
had any problems at all with that combination so I fear that something
might be broken with 6.0.2.
",bs
18320,Virtual Hard Disk wizard defaults to file size less than recommended for Ubuntu 18,Windows,Linux,VirtualBox 6.0.0,2019-01-19T20:51:09Z,2019-01-19T20:51:09Z,"Using VirtualBox 6.0.0 r127566 (Qt5.6.2) on host Windows 7 SP1 amd64.

I am creating a new VM using the GUI wizard. The Create Virtual Machine wizard detects I am intending to install Ubuntu and set the ""Version"" to ""Ubuntu (64-bit)"". The Virtual Hard Disk wizard defaults to a 10GB hard disk.

The download page for Ubuntu 18 (Desktop) at https://www.ubuntu.com/download/desktop suggests 25Gb of free hard drive space.

",Adam Piggott
18321,Virtual Machine has terminated unexpectedly.,Windows,Windows,VirtualBox 6.0.2,2019-01-19T21:14:17Z,2019-01-19T21:14:17Z,"The virtual machine 'Windows 10 Test' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\Program Files (x86)\Oracle\VirtualBox VMs\Windows 10 Test\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
",Excaluburjmk
18323,Video Memory Expanding to 256 MB Fail,Linux,Linux,VirtualBox 6.0.2,2019-01-19T21:27:44Z,2019-01-19T21:27:44Z,"Can no longer extend video memory to 256MB using the command line:

VBoxManange modifyvm ""vm name"" --vram 256

This creates an error upon boot up and stops boot.

Legacy machines created in VirtualBox 5.2 seem to work fine with this mod when installed on VB 6.0.",andrewf
15752,Failed to open a session for the virtual machine,Windows,Linux,VirtualBox 5.1.2,2019-01-19T21:31:44Z,2019-01-19T21:31:44Z,"Fresh install of Windows 10.
Fresh install of VB 5.1.2
Created a default Ubuntu x64 VM using Ubuntu 16.04 .iso
When I try to start the VM I get the following error:

''Failed to open a session for the virtual machine Xerus.

The virtual machine 'Xerus' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\brad\VirtualBox VMs\Xerus\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
''

I have created a default Win7 VM and get the same result when trying to start it.
",slattdog
18332,Windows 10 Guest additions 6.0.2 scramble drive mappings into shared folders,Windows,Windows,VirtualBox 6.0.2,2019-01-20T02:17:18Z,2019-01-20T02:17:18Z,"Running Win 10 Pro (October 2018 Update, build 17763) on both host and guests, updated host from 5.2.22 to 6.0.2 with 6.0.2 guest additions.  Upgrading guest VMs to 6.02 guest additions scrambled the mapped drives into shared folders.  The windows drive mappings no longer corresponded to the originally assigned shared folders,.  Rolling back to a previous version of the VM (which still had 5.2.22 guest additions installed restored correct behavior.  

FWIW:
  net use v: \\vboxsrv\bbj5-c /persistent:yes
  net use w: \\vboxsrv\data   /persistent:yes
  net use x: \\vboxsrv\bbj5-e /persistent:yes
  net use y: \\vboxsrv\a      /persistent:yes
  net use z: \\vboxsrv\aa     /persistent:yes


Reproduced this behavior on a second (and different) vin 10 pro vm: changing nothing other than upgrading guest additions from 5.2.22 to 6.0.2 corrupted the mappings into shared folders.  

two logs
w10p-1-2019-01-18-21-21-45.log  scrambled VM 6.02 guest additions
w10p-1-2019-01-18-21-41-13.log	correctly mapped VM 5.2.22 guest additions					",BBoyar
18334,Windows 10 guest freeze or crash,Linux,Windows,VirtualBox 6.0.2,2019-01-20T07:17:32Z,2019-01-20T07:17:32Z,"After update to VBox 6.0.2 a Windows 10 64bit guest always freezes or completely crashes when VBoxSVGA and 3D acceleration are chosen. It happens as soon as Skype for Business starts on the VM.

Additionally I've got problems with keyboard grabbing as well as graphics (Outlook 2016 moves cursor to and fro while typing with hardware acceleration off but Excel opens files only when it's off).

Disabling 3D acceleration in the VM settings seems to solve the problems.

My host runs on Linux Mint Cinnemon 19 with an nVidia graphics adapter using the proprietary graphics driver.",Mellon
18336,Virtual Box Extension Pack 6.0.0 Installation Error,Windows,Windows,VirtualBox 6.0.0,2019-01-20T08:10:14Z,2019-01-20T08:10:14Z,"Every time I update VirtualBox and install extension pack I got an error message.In previous update when I update VirtualBox to 6.0.0 and then I install Extension Pack I got the same error message.
I have detailed video link of this error message on youtube:- https://youtu.be/orHQHsoe6NY

Can any one help me?",Binoy
17318,"Permanent, human readable anchors in the HTML User Manual",other,other,VirtualBox 5.2.0,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
1139,"Feature request: wider copy/paste support, in Console for instance -> user contributions welcome",other,other,VirtualBox 1.5.4,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
18337,"""Create a Shortcut on Desktop"" overwrites existing shortcut with no warning",all,all,VirtualBox 5.2.0,2019-01-21T22:25:35Z,2019-01-21T22:25:35Z,"The issue was brought to my attention on IRC by ""instantp10neer"" and later in a discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=91366 by ""corhsin"" (same user).

If you have a shortcut to the Desktop named exactly as your shortcut-want-to-create, the ""Create a Shortcut on Desktop"" action overwrites the existing shortcut without asking for confirmation.

'''__Steps to reproduce__'''
* Create a shortcut on the desktop named ""Anything"" that points to a text document (for example).
* Create a new VM in !VirtualBox named ""Anything"".
* Right-click on the VM, ""Create a Shortcut on Desktop"".
* The existing shortcut is overwritten without any confirmation.

'''__Solution__'''
* Have a confirmation dialog:
> ''The shortcut/alias ""Anything"" already exists on the Desktop. Do you want to overwrite it? Y/N''\\
\\
BTW, this occurs since 5.2.0 (didn't go further back, but I don't doubt that it's there for ever), and it happens on Win/Linux hosts. On OSX hosts, the same operation results in a NoOp...",Socratis
18346,Crash after reboot Windows 10 guest,Linux,Windows,VirtualBox 6.0.2,2019-01-22T11:13:04Z,2019-01-22T11:13:04Z,"Hi,

I rebooted a Windows 10 guest because a shared folder was showing up twice (I have reported this issue in the Windows Guest forum) but it crashed. After powering down the guest it boots normally.
Host OS is ubuntu version 18.04.1, Virtualbox version is 6.02, guest OS is a new install of Windows 10 1803 with the 6.02 guest additions. 
I have attached the logs for review.

Regards,
Gijsbert
",gwiesenekker
18262,Not enough video memory to restart gnome after loading from save state,Mac OS X,Linux,VirtualBox 6.0.0,2019-01-22T13:22:51Z,2019-01-22T13:22:51Z,"After saving state, upon reloading a black screen is shown and VM is totally unresponsive.

This is fixed by increasing the default video memory from 16mb to something like 48mb.

Took me a long time to figure out - maybe the default should be larger.

Host: VBox 6.0 MacOS Mojave 10.14.2
Guest: Ubuntu Bionic Beaver 18.04.1",0x7766
18349,Audio getting muted in screen reader installed on Windows 10 guest (Virtualbox 6.0.2),Linux,Windows,VirtualBox 6.0.2,2019-01-22T17:45:46Z,2019-01-22T17:45:46Z,"I've upgraded recently from Virtualbox 5.2.6 to 6.0.2 - Archlinux is the host and Windows 10 the guest system. As I'm totally blind, I use a screen reader to access the computer (NVDA 2018.4.1 installed on the guest). Both virtualbox-ext-oracle and guest additions are up to date.

After upgrading I noticed that the screen reader gets muted for a while and starts speaking again. The problem happens suddenly and frequently. When it gets muted and I switch to the host window and go back to the guest, it starts speaking again and after some seconds (or minutes) the problem repeats.

I've already confirmed that the problem isn't related to the screen reader; its commands continue working even when it is muted and there are no logs showing a NVDA crash. Initially, I thought that the entire audio was being affected by the problem, but when I play a video (from Youtube, for example) in background and continue to use the screen reader, surprisingly the issue doesn't happen (after stopping the video the problem back to arise as before).

Are you aware about some known issue that may be related to the aforementioned problem?",alan-ghelardi
18354,Centos guest crashes when accessed form list of VMs in VBox,other,other,VirtualBox 6.0.2,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
18347,Always NS_ERROR_FAILURE after latest Fedora 29 update,Linux,all,VirtualBox 6.0.2,2019-01-24T08:01:39Z,2019-01-24T08:01:39Z,"After Fedora 29 latest update, it's not possible to start any VM in virtualbox.

Kernel version is '''4.19.15-300.fc29.x86_64'''

The message '''The virtual machine '<name>' has terminated unexpectedly during startup with exit code 1 (0x1).''' is always returned with :


{{{
Error code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
}}}


I've remove VirtualBox and reinstalled it with same problem.

I've remove 6.0.2 and installed 6.0.0 with same problem.

There's no error when ""/sbin/vboxconfig"" is launched.

There's no error when ""/sbin/rcvboxdrvd setup"" command is launched.

And no log is generated in the vms... I have no idea to solve the problem.

Same behaviour for all my VMs (as root or not): Windows, Kali, RedHat.",chla
18148,Audio hangs when host screen turns off,Windows,Windows,VirtualBox 5.2.22,2019-01-24T10:16:52Z,2019-01-24T10:16:52Z,"I upgrade to 5.2.22 from 5.2.20 because it should fix the problem, according to the changelog:
""Audio: fixed a regression in the Core Audio backend causing a hang when returning from host sleep when processing input buffers"".

But it's not, at least for me. Tested under W2k8 R2 (host) and W7 (guest).
Once the screen enter into power save mode, the audio hangs until I shutdown the guest machine (rebooting the machine doesn't solve the problem).",IzK
18357,Clone fails because newly created vdi is attached to clone it just made.,Linux,Windows,VirtualBox 6.0.2,2019-01-24T11:59:38Z,2019-01-24T11:59:38Z,"Failed to clone the virtual machine Windows 10 MAIN (64 Bit) Fresh SSD.

Medium '/home/mark/VirtualBox VMs/Windows 10 MAIN (64 Bit) Fresh SSD Clone1/Windows 10 MAIN (64 Bit) Fresh SSD Clone1.vdi' '''cannot be closed because it is still attached to 1 virtual machines.'''

Result Code: VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
----------------------------

Repeatable. Ubuntu 18.04.1 host

",BFG
16936,Snapshot Deletion of Encrypted VM always corrupts filesystem,Windows,Linux,VirtualBox 5.1.24,2019-01-24T20:23:59Z,2019-01-24T20:23:59Z,"Given this setup:

* Windows 10 Pro Host
* VitrualBox 5.1.22/24
* Ubuntu 16.04 Guest
* VBox Additions Installed
* Guest is encrypted.
* VBox Web Service is running

I wrote a java tool that uses the web service and does the typical thing in creating a VM backup.  This includes taking a snapshot prior to copying the VDI(s) to an archive and then once completed, deletes the snapshot.  This occurs while the VM is running (or off as well).  The duration of the VM running on the snapshot is probably on the order of 20-30 minutes.

I have several VMs I use day to day. 1 is encrypted and the other 1 isn't.  Invariably the deletion of the snapshot on the encrypted VM results in a corrupt and non-bootable system even though the merge back into the parent is 100% successful.  This does not happen on the non-encrypted VM.

As an additional validation of the issue, I removed the encryption from the encrypted VM and I do the same thing with my java tool.  No problems at all and the VM is fine.  I put the encryption back on the VM and get the same original corruption problem.

In addition I run the tool with the encrypted VM off, and I don't see the problem.  All works as expected.

I've run this over 10 times and the same thing happens every time.  My running + encrypted VM always corrupts the filesystem when the Snapshot deletion/merge occurs.

I read another Bug report on the VirtualBox support site that states the same thing (from a few versions back I believe).

Thanks and let me know what else you need.

",declay
17461,writethrough affected by snapshots,Windows,Windows,VirtualBox 5.2.4,2019-01-26T03:29:12Z,2019-01-26T03:29:12Z,"I made this critical because not everyone will check for correct functionality. Restoring a snapshot will cause an unexpected data loss on a drive of type writethrough.

I've got a VM with a main drive and an attached writethrough drive. I see twice as many .vdi files than .sav files in the snapshot directory. And yes a restore changes the writethrough drive.


C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi[[BR]]
UUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx[[BR]]
Parent UUID: base [[BR]]
State: created [[BR]]
Type: writethrough [[BR]]
Location: E:\DataW10.vdi [[BR]]
Storage format: VDI Format [[BR]]
variant: fixed default [[BR]]
Capacity: 4096 MBytes [[BR]]
Size on disk: 4098 MBytes [[BR]]
Encryption: disabled [[BR]]
In use by VMs: Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)",Loafer
18360,iMac (mojave 10.14.2) repeated panic crashes,other,other,VirtualBox 6.0.2,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
18366,Can't use vboxapi on Mac using Python bindings with anything other than the system version of Python,Mac OS X,other,VirtualBox 6.0.2,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
18228,Copy/Paste From Shared Folder Hangs Win7 32 bit Guest With 6.0.0r12766 Additions,Windows,Windows,VirtualBox 6.0.0,2019-01-27T22:02:03Z,2019-01-27T22:02:03Z,"VBox 6.0.0r127566 (QT5.6.2) in win10 1809 host with win7 32 bit guest works fine using additions from previous release. After updating guest to new additions attempting to copy a file from a shared folder hangs the win7 32 bit guest. If VM is powered down -- regular shut down or restart won't work -- & restarted, shared folder will not show up in win7 guest's Windows Explorer. If when the guest is shut down, VBox is closed & restarted, the shared folder will appear, but the guest hangs next time any file transfer is attempted.",mikiem
17455,Host USB is locked after shared folders were added,Windows,Windows,VirtualBox 5.2.4,2019-01-27T22:12:20Z,2019-01-27T22:12:20Z,"I have a USB Stick with Windows 10 Installation files on it. If this stick is attached and I added some folders in the VM, I simply can’t eject it in the host Windows, because it is constantly locked. Even if I add some folders not on the USB drive. After I used a Process Explorer I could see, that there is a handle to the setup.exe on the USB. I attached the logs, because there one can see, that this is hardening issue. The only way to solve it right now is either kill the handle or close VM. This started way back, as hardening was added.",boxer01
18375,Red Hat Linux 7.6 VM kernel panic running under Windows 10 host,Windows,Linux,VirtualBox 6.0.2,2019-01-28T17:28:55Z,2019-01-28T17:28:55Z,"When I try running a Red Hat 7.6 VM under Windows 10 using Oracle VirtualBox 6.0.0 or 6.0.2 I get a Kernel Panic.

If the guest is configured for Enable I/O APIC unchecked and so 1 CPU I get a panic in: __native_set_fixmap
If the guest is configured for 4 CPUs I get a panic in: __lookup_address_in_pgd

I have Hyper-V disabled in Windows Features. I have Windows Hypervisor Platform enabled (as without that I get errors reported in my VirtualBox config and can't even get the VM to start).

Prior to a reboot on Jan 17th 2019 I'd not had a problem. After the reboot Windows Hypervisor Platform was disabled and that stopped the VM running at all. When I enabled that setting I got the kernel panic. I tried reinstalling the Red Hat 7.6 VM, but that also suffered from the kernel panic during the install.

Between the previous reboot and the Jan 17th reboot the only things installed on my machine were:

* Dell SupportAssistAgent 3.1.0.142
* Adobe Acrobat Reader DC (19.101.20069) 

I tried uninstalling the Dell utility. However it did not resolve the issue.


Attached is a log from a startup with 4 CPUs.",David Castell
18382,Cursor scaling - cursor becomes very small or sometimes almost invisible,Windows,Windows,VirtualBox 6.0.4,2019-01-29T07:16:02Z,2019-01-29T07:16:02Z,"This bug is not new to version 6 as I've seen it in 5.2 also. The mouse pointer (hardware cursor) depending on the application can become very small or even almost disappear. The cursor becomes much smaller in the RDP session started from the guest. Also it is smaller and with weird shapes in MS Office applications like Excel or Word. In Word or any other text editor (like Notepad++) where the cursor should be an I-beam it pretty much disappears. What is left of it when the mouse pointer is over an editor window are literally 2 pixels. Almost impossible to see.
This bug has been on and off over the last few months. I suspect although have no proof that Microsoft patches to the host or guest OS cause this change of behavior. Right now the bug is fully ""visible"" (pun intended).",Rafcio
18384,Cursor disappears during Linux installation,Windows,Linux,VirtualBox 6.0.4,2019-01-29T10:20:20Z,2019-01-29T10:20:20Z,"When using 6.0.2 and 6.0.4 to install Oracle Enterprise Linux 7.5 the cursor disappears and is replaced by a smudge-like object. However that object is displaced by random factor of pixels in the X and Y direction making it unusable.
On version 5.X the smudge was also there, but so was the cursor - so I lived with it, but now I can not install the OEL 7.5.",htx
18372,"00:08:27.570846 !!Assertion Failed!! 00:08:27.570847 Expression: RT_SUCCESS_NP(rc) 00:08:27.570847 Location  : F:\tinderbox\win-rel\src\VBox\VMM\VMMAll\PGMAllPool.cpp(2645) int __cdecl pgmPoolMonitorInsert(struct PGMPOOL *,struct PGMPOOLPAGE *) 00:08:27.570850 PGMHandlerPhysicalRegisterEx 00000000dea18000 failed with -1701 00:08:28.581275 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'",Linux,Windows,VirtualBox 6.0.2,2019-01-29T10:31:48Z,2019-01-29T10:31:48Z,"I've installed this morning my first Virtual machine, based on the last version of Debian, my laptop running a version of Window 8

I've installed on my VM Apache and MySQL, cus I need a web development environment.

And when I'm running my VM I got an issue, it stops to run, and close it, I don't know why, I do nothing extraordinary, just running Apache and MySQL and try to download a file from my Gmail. I don't understand what happened...",Hota
17533,USB3.1 USB stick fails to enumerate,Windows,Linux,VirtualBox 5.2.6,2019-01-29T15:19:48Z,2019-01-29T15:19:48Z,"Host: W10 LTSB (64bit)
Guest: Linux (64bit)
VB Version: 5.2.6 r120293 (Qt5.6.2)

I've recently purchased another one of these sticks (Verbatim Go V3 MAX). The old ones (read out as USB3.0) work just fine.

This one however shows up as USB3.1 (booting linux on physical machine). The stick works just fine on W10 / linux, as long as I don't use a VM.

Disabling USB3 in the VM ""helps"", but USB2 speeds are just 5MB/s.",robert spitzenpfeil
18348,VBoxGuestAdditions 6.0.2 failed with OpenArena game (ioquake3/renderer_opengl1_x86_64.so),Windows,Linux,VirtualBox 6.0.2,2019-01-29T16:16:36Z,2019-01-29T16:16:36Z,"System environment:
Host OS: Windows8 Pro 64 bit (all updates)
Guest OS: Debian 8.11 (kernel 3.16.0-4, all updates from stable branch 8.11)

After update from 6.0.0 to 6.0.2 and apply VBoxGuestAdditions.iso - game OpenArena cant be run with this error text:

""Trying to load ""renderer_opengl1_x86_64.so"" from ""/usr/lib/ioquake3""...
Trying to load ""renderer_opengl1_x86_64.so"" from ""/usr/lib/openarena""...
Loading ""renderer_opengl1_x86_64.so"" failed
failed:
""Failed loading /usr/lib/openarena/renderer_opengl1_x86_64.so: /usr/lib/openarena/renderer_opengl1_x86_64.so: cannot open shared object file: No such file or directory""
Failed to load renderer""

But file in /usr/lib/ioquake3/renderer_opengl1_x86_64.so is exist, and if downgrade GuestAddition to 6.0.0 OpenArena then can be run again.

But generally 3d acceleration works, AlienArena succefully run and play with fast fps.",ilyalesnoi
18386,VirtualBox 6.0 crash and make Windows reboot,other,other,VirtualBox 6.0.4,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
18291,FileManager: progress bar stops at 50% while copying,all,all,VirtualBox 6.0.0,2019-01-30T11:21:37Z,2019-01-30T11:21:37Z,"This has been reported during the beta (https://forums.virtualbox.org/viewtopic.php?f=15&t=90668), after the release (https://forums.virtualbox.org/viewtopic.php?f=1&t=90824&start=45#p437977) and I've seen it several times, I just didn't check the bug tracker so far..

This is mostly a cosmetic issue, since the copying seems to succeed, but still, it scares users, big time, hence the ""major"" priority.",Socratis
18389,numeric username issue,Linux,other,VirtualBox 5.2.26,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
18393,USB3 drive not recognized when connected to USB3 port,Windows,Linux,VirtualBox 5.1.24,2019-01-30T18:12:30Z,2019-01-30T18:12:30Z,"I have a Windows7 host w/ Debian8 guest on VirtualBox 5.2.8.  WD Elements 2TB disk (https://smile.amazon.com/gp/product/B00D0L5BH8/) and Thinkpad E560 laptop (https://smile.amazon.com/Lenovo-ThinkPad-20EV002JUS-15-6-Inch-Processor/)

The disk connected into any usb3 port on the laptop.  It is recognized and works fine under the Windows host.  Once I connect the disk to the virtualbox guest, windows correctly stops seeing it and the guest shows:

{{{
[ 1786.262759] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 1786.486278] usb 1-2: device descriptor read/64, error 18
[ 1786.775519] usb 1-2: device descriptor read/64, error 18
[ 1787.063049] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[ 1787.247705] usb 1-2: device descriptor read/64, error 18
[ 1787.535498] usb 1-2: device descriptor read/64, error 18
[ 1787.818462] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 1787.835491] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.018588] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[ 1788.035487] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.036814] usb usb1-port2: unable to enumerate USB device
}}}

''virtualbox list usbhost'' when the device '''is not''' connected to the virtualbox guest:
{{{
UUID:               91f87b8b-5c6c-4318-b582-48e82af85f67
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/Super
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0008
Current State:      Busy
}}}

.. and ''virtualbox list usbhost'' when the device '''is''' connected to the virtualbox guest:
{{{
UUID:               d4973955-0c60-418e-bd19-29d060869977
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/High
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0009
Current State:      Unavailable
}}}

the device does not show up in /dev/sd* at all and ''lsusb'' does not show the device

the guest is configured for USB3 in virtualbox settings and the guest does have the usb3 drivers loaded.

when I use a USB2 extension cable between the disk and the laptop, the device works in the virtualbox guest.


see for discussion: https://forums.virtualbox.org/viewtopic.php?f=6&t=82474",jkister
18395,animations and mouse movement flicker [OS/2 guest],Windows,other,VirtualBox 6.0.4,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
18221,"Getting ""can't apply partial context to unlabeled file"" in Version 6.0.0 -> fixed after (not in) 5.2.26/6.0.4",Windows,Linux,VirtualBox 6.0.0,2019-01-31T22:40:16Z,2019-01-31T22:40:16Z,"While booting after changing to Version 6 of VirtualBox running a guest  Oracle Linux 4.1.12-124.22.4.el6uek.x86_64, I get the following message in boot.log:
{{{
VirtualBox Guest Additions: Starting.
chcon: can't apply partial context to unlabeled file `/opt/VBoxGuestAdditions-6.0.0/src/vboxguest-6.0.0/build_in_tmp'
Starting auditd: ^[[60G[^[[0;32m  OK  ^[[0;39m]^M
}}}

It seems stuff is working, I think, but would like to know if this error is a sign that trouble is on the way.

The machine log is also attached.",DonC
18405,Deleting a snapshot with multiple children,all,all,VirtualBox 6.0.4,2019-02-01T15:09:28Z,2019-02-01T15:09:28Z,"Currently, deleting a snapshot with multiple children is not possible:
> Snapshot [...] cannot be deleted, because it has 2 child snapshots, which is more than the one snapshot allowed for deletion.

I suggest merging the disk images for each child separately.",robert@…
18397,3D Accelaration under macOS results in unreadable characters,Mac OS X,Windows,VirtualBox 6.0.4,2019-02-01T20:12:38Z,2019-02-01T20:12:38Z,"when enabling 3D Accelaration under macOS I see in unreadable characters in my windows 10 guest system

attached document contains screenshots of the grafic errors + screenshots of the VBox settings, Host & guest system",SOO1
18359,Wrong driver in the Windows 7 guest after the switch to the VBox SVGA adapter.,Windows,Windows,VirtualBox 6.0.2,2019-02-05T07:25:49Z,2019-02-05T07:25:49Z,"I have a Windows 7 guest on the Windows 8 host. Because it’s new, after the test with an old VGA adapter I tested the new VBox SVGA adapter. After the first start the new device was automatically detected and installed. I have had to reboot the guest and after the reboot the new driver was active and I even had the Windows Aero activated.

Because of the problem I already posted in the forum (if I activate the experimental WDDM driver, my only Java desktop program, the TV Browser, has big skinning issues and becomes unusable) I usually install a regular driver with non-experimental Direct3D support only (Virtual Box Graphics Adapter). I have to boot my guest in safe mode for installation because of this. But time after time I test the experimental one. So after the reboot I found that the device name is “Virtual Box Graphics Adapter for Windows Vista and 7” now and beside the working Aero I also have the already mentioned issues in my Java program. More important: the driver version is 5.2.1 and it’s from the end of the year 2017. This was probably the last time I tested the experimental Aero supported drivers.

So I have to boot in safe mode once again, re-install the guest additions, but this time I answered “no” in the dialog about installing the regular Direct3D drivers and not the experimental WDDM ones. It looks for me, that by activating SVGA adapter the other device is simulated and under Windows 7 and Vista the Aero WDDM driver is used. And if one doesn’t install or re-install the additions explicitly, the wrong version of the drivers are used.

This was my experience from my test of original 6.0 release from December 2018. As I tested the 6.0.2 release, the new device was also detected and the driver was also installed. But this was probably once again not the newest one, so after the reboot I had the BSOD on the boot, more then once. Therefore, I have to repeat the additions installation and this way probably renew the Aero WDDM driver as well. After that the BSOD was gone, but I got the same situation with Aero and Java program as I already had before.",boxer01
18409,Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) after experimental WDDM video driver installation.,Windows,Windows,VirtualBox 6.0.4,2019-02-05T07:41:44Z,2019-02-05T07:41:44Z,"I have Windows 7 x86 guest on Windows 8 x64 host. Because of my issues (#18359) with SVGA adapter driver (not the current version is used even if current version of non-WDDM driver was previously installed) I tried the new approach. The new version of experimental (WDDM) driver was installed before the switch from the VGA to SVGA, after the non-experimental driver was already installed previously from the safe mode boot. As a result after the required restart of the guest OS I got the guru meditation. 

Side note: I installed the experimental driver in the normal mode, I didn’t boot the OS in the safe mode,because for the experimental drivers this isn’t a requirement. Other note: if I install the experimental driver (I say no to the standard one after activating the Direct3D support during the guest addition installation) in the safe mode, I have no issues with my desktop Java application, [https://forums.virtualbox.org/viewtopic.php?f=2&t=85458 TV Browser]. They appear as soon as I installed them in normal OS boot mode.",boxer01
18392,"Accented Characters causes the ""Failed to set the global VirtualBox extra data for key GUI/GroupDefinitions"" bug",all,all,VirtualBox 6.0.4,2019-02-05T11:42:18Z,2019-02-05T11:42:18Z,"!VirtualBox 6.0.4 presents the following failure report when you move the position of a virtual machine inside a group: 
'''""Failed to set the global !VirtualBox extra data for key GUI/GroupDefinitions""'''

Affected Hosts: All. Already confirmed in Windows and Linux (KDE) hosts.

Affected Guests: ANY.

Is it reproducible? Yes, always. Just follow instructions bellow.


== Instructions to reproduce the bug: ==

1. Begin with !Virtualbox version 5.2 with some guest machines.
2. Create a group with 2 or more machines
3. Rename the group using accented characters (for example á é ç ã etc)
4. Move the position of any machine upwards or downwards inside the group.
- It works perfectly in this version of !VirtualBox 5.x
5. Upgrade !VirtualBox to Version 6.0.x
6. Move the position of any machine upwards or downwards inside the group.
- It throws '''""Failed to set the global !VirtualBox extra data for key GUI/GroupDefinitions""'''


Workaround: Rename '''ALL WORKGROUPS''' that use accented characters using '''only''' standard basic American characters. Of course this is not desirable for non English speaking users. It is only a workaround.

Other issues and '''MORE BUGS''' (or other aspects of the same bug):
1. On !VirtualBox 6.x it is '''NOT''' possible to rename the group back to accented characters (generally they are generated using 2 key presses: the accent followed by the standard letter), but here is where you will see '''ANOTHER RELATED BUG:''' My Brazilian Portuguese Keyboard has a key with the letter ""ç"" and !Virtualbox 6.x just accepts the letter ""ç"" and enters in the bug condition described above.
2. Whenever any machine group is named using accented characters, !Virtualbox is completely unable to cleanly shutdown. I have already described this failure mode in another completely different bug report: #18318 . The main bug is described here and whenever it is fixed, the other bug is going to be fixed as well as it is only a collateral effect of the bug reported here.

I hope this explanation is clear enough to trigger a bug fix action.

Regards,

Hilário Fochi Silveira",Fochi
18412,The Virtual Machine Won't Start Unless Run Headless Start,Linux,Windows,VirtualBox 6.0.4,2019-02-05T13:08:15Z,2019-02-05T13:08:15Z,"Hi,
When trying to boot a virtual machine clicking on Start button it crashes with the an error, see attached screenshot. Also attached a log file.

If the files are not attached it is due to I do not see how to attach them.

Thanks
Kiko",kiko
18353,Linux Mint 18.x VM Multimedia/Graphics Broken By 6.0.2 Guest Additions Install,Windows,Linux,VirtualBox 6.0.2,2019-02-05T16:42:36Z,2019-02-05T16:42:36Z,"After installing the 6.0.2 guest additions on Linux Mint Cinnamon the following problems were observed:

-The screen lock window does not appear when the computer is locked after a period of inactivity, and the desktop is visible, but inaccessible to mouse clicks. The password can still be entered and the VM will wake up and return to the normal desktop.

-VLC media player 2.2.2 Weatherwax crashes with the error:
""corrupt module: /usr/lib/vlc/plugins/gui/libqt4_plugin.so""

-Web browser based video streams from FireFox fail to run or stop after rendering 100 or less frames

-Media Player does not render its window frame properly with respect to other windows, does not display menu contents, and freezes when playing content if launched as the default multimedia app.

-There may be many other graphical rendering and multimedia anomalies. So far the above were observed from a limited amount of troubleshooting time.

The environment(s) in which these problems were observed is:

o Linux Mint Cinnamon 18.2 with multimedia bundle accepted during install
o Linux Mint Cinnamon 18.3 with multimedia bundle accepted during install
o Running in VirtualBox 6.0.2 from Windows 10 with guest additions added to the VM (updated from 6.0.0 recently)
o VM configured with:
  - 2 Processors, VT-x/AMD-V, Nested Paging, PAE/NX, KVM Paravirtualization
  - >= 2 Gb RAM
  - >= 20 Gb HDD
  - 64 MB Video Memory
  - VBoxVGA Graphics Controller

The above issues did not exist before upgrading from VirtualBox 6.0.0 to 6.0.2. To confirm that the issue is caused by the guest additions, we created a new VM in 6.0.2 with the configuration described above and loaded a new install of Linux Mint Cinnamon 18.3, accepting the default Mint multimedia bundle during the install process. Before adding the guest additions, testing shows that none of the problems above were present. We then added the 6.0.2 guest additions and then re-tested and observed all the issues described above. Furthermore, we have confirmed that if the Graphics Controller setting on the VMs is changed to VMSVGA in 6.0.2 then the observed problems go away.
",cjrussell1962
18413,All VM guests stuck (black screen) and can't be killed - after a USB filter is set,Linux,Windows,VirtualBox 6.0.4,2019-02-05T17:00:11Z,2019-02-05T17:00:11Z,"HOST: Linux Mint 19.1/Cinnamon + VirtualBox 5.2.24 first, then 6.0.4
GUESTS: Windows 10 Home, Windows 7 Prof, both worked fine until

I SET a new USB FILTER for Win10 (I am in the vboxusers group)
and then I started Win10 : just a black screen appeared, nothing else.
I could nor stop it, neither kill it from a terminal. Then I even had my Linux host to force to stop with the power button, too.

TESTS
1. After a new Linux host start I started Vbox again (now without any modification) and then Win7 guest. Same result as above.

2. I deleted completely VirtualBox 5.2.24 with all its files, even the VM-s from my laptop, (they were exported not long ago to an external drive). Then I installed VirtualBox 6.0.4 and its Extension Pack, and imported my 2 Windows VMs. They both worked fine again. I installed the apropriate GuestAdditions in both. Still ok. I could work with them well. 
Then I added myself to the vboxusers, rebooted Linux and started VirtualBox again. I set a new USB filter for Win10 and started it. Black screen again which could not be killed, and Linux could not be stopped. 

3. After a new start I tested my Win7 guest as well, neither works it any more. Black screen, stuck, Lx can't be stopped.

I think some Vbox configuration goes bad... I use Vbox since many years, and I do not rememeber similar problem. In a formerly Vbox version I could set USB filters, however I do not remeber the version number unfortunately. Anyhow, I appreciate Vbox very much, it is an excellent work. 

",JBM
18363,VirtualBox GUI infinite loop changing window layout - GUI unusable,Mac OS X,other,VirtualBox 6.0.2,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
18417,USB thumb drive is persistent.  It does not disappear while removed,Windows,Linux,VirtualBox 6.0.4,2019-02-06T17:34:03Z,2019-02-06T17:34:03Z,"SanDisk drive showed correctly in Devices, and was gone when I removed the drive.  That was then!  

Now, it does not disappear when removed, and in fact shows twice when I again install it.

Underlying Windows 10 device does come and go as expected.

Comment: is there a way to refresh devices (USB devices)?",Derick Moore
18418,Broken display output for guest application entering full screen mode with changed resolution,Linux,Windows,VirtualBox 6.0.4,2019-02-06T17:54:29Z,2019-02-06T17:54:29Z,"Steps to reproduce:
1. Install guest OS, install guest addons
2. Have guest OS in maximised window (not full screen)
2. Start application (a game in my case - Heroes of Might and Magic IV, DirectX 9.0c)

Expected result:
Application should be started, due to its lower resolution it should be surrounded by unused area (like when OS boots).

Actual result:
Guest display is broken.",mmikk
18414,Menu bar very small on portrait screen,Linux,other,VirtualBox 6.0.4,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
17335,unattended install uses wrong path for UnattendedTemplates dir,Linux,all,VirtualBox 5.2.0,2019-02-07T00:18:48Z,2019-02-07T00:18:48Z,"This is for VirtualBox 5.2.2 (that version wasn't available as a selection)

* Host OS:  CentOS 7.4 (all updates current)
* Version:  VirtualBox-5.2-5.2.2_119230_el7-1.x86_64

When trying to use the new ""unattended install"", it fails, presumably because it's trying to find the UnattendedTemplates directory in the wrong location:

{{{
$ vboxmanage unattended install centos7 --iso /iso/CentOS-7-x86_64-Minimal-1708.iso
VBoxManage: info: Preparing unattended installation of RedHat_64 in machine 'centos7' (62f5cf05-2814-4ba8-95f3-4d51a94f5507).
VBoxManage: error: Failed to open '/usr/share/virtualbox/UnattendedTemplates/redhat67_ks.cfg' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component UnattendedWrap, interface IUnattended, callee nsISupports
VBoxManage: error: Context: ""Prepare()"" at line 1643 of file VBoxManageMisc.cpp
}}}

The UnattendedTemplates directory appears to be in a different location when installing via RPM:

{{{
$ rpm -ql VirtualBox-5.2 | grep UnattendedTemplates
/usr/lib/virtualbox/UnattendedTemplates
/usr/lib/virtualbox/UnattendedTemplates/debian_postinstall.sh
/usr/lib/virtualbox/UnattendedTemplates/debian_preseed.cfg
/usr/lib/virtualbox/UnattendedTemplates/fedora_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/ol_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/redhat67_ks.cfg
/usr/lib/virtualbox/UnattendedTemplates/redhat_postinstall.sh
/usr/lib/virtualbox/UnattendedTemplates/ubuntu_preseed.cfg
/usr/lib/virtualbox/UnattendedTemplates/win_nt5_unattended.sif
/usr/lib/virtualbox/UnattendedTemplates/win_nt6_unattended.xml
/usr/lib/virtualbox/UnattendedTemplates/win_postinstall.cmd
}}}

If I create a symlink from `/usr/share/virtualbox/UnattendedTemplates` to `/usr/lib/virtualbox/UnattendedTemplates`, then the unattended installation succeeds.



",Greg Bailey
18403,Linux Host and Windows guest both consume same input event (windows/action key),Windows,Linux,VirtualBox 6.0.4,2019-02-07T09:08:40Z,2019-02-07T09:08:40Z,"Windows 10 Host
Linux Guest (Fedora 29 Workstation) 

Steps to reproduce:
Boot Fedora guest,
Press Windows Key

Observed behavior:
Windows start menu is opened and Gnome Activities is triggered at the same time

Expected behavior:
Only the guest receives the key event and the Gnome Activities is triggered without triggering the Windows start menu

Note:
This Problem did not exist in VirtualBox 5. ",nopaste
18422,Cannot install Extension Pack 6.0.4,Linux,other,VirtualBox 6.0.4,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
18123,Regression when play mci mp3 since 5.2.20,Linux,Windows,VirtualBox 5.2.20,2019-02-08T10:58:30Z,2019-02-08T10:58:30Z,"Hello,

I debian 9.5 Stretch installed in the Host machine.

Since the release of VirtualBox 5.2.20 and 5.2.22,
In windows guest (2000,7) when I want to play a youtube video in the guest machine it's OK ,it's work fine !!.
ON THE OTHER HAND :
when i play an mp3 / wav from the MCI player windows or windows media player THEN result the sound jerks and hash.

In short:
Since version 5.2.20 when I want to play an mp3 from the MCI, it plays only 80% time of the mp3.
And apparently I'm the only one with this problem.
In versions prior to 5.2.20 I have no problem.

How to solve this problem?

I DON'T KNOW if the log can you help it;;


Thank you.",Sizy458
18240,audio clips are truncated at the end,Windows,Windows,VirtualBox 5.2.20,2019-02-08T11:01:38Z,2019-02-08T11:01:38Z,"VirtualBox [v5.2.20 and 5.2.22] stops playing audio clips before they finish.

I had this issue somewhere back around ???[v5.1.26/27]???, but is was corrected shortly there after.

The issue has now resurfaced since v5.2.18.

I was keeping up with updates, but was not using the audio applications.

I downgraded to v5.2.18 and plan on staying {safe} with v5.2.18 just because I know the audio is still working correctly.

Just FYI, Tracey

If anyone cares, maybe the archived versions (5.2.20 and 5.2.22) should be fixed as well.",Tracey
11758,"""Take Screenshot"" just makes black PNG ==> Fixed in SVN",Windows,Linux,VirtualBox 4.2.12,2019-02-08T12:32:17Z,2019-02-08T12:32:17Z,"If I hit '''Take Screenshot''', all I get is a black PNG. I've attached the PNG. I've also attached a user-generated screenshot, created from hitting PrtScn while VirtualBox does not have the focus (and later cropped with GIMP).

System state:
* guest is Ubuntu 13.04, fresh install
* Guest Additions installed, has been rebooted
* host is Windows 8 x64

If you look at the manually-taken screenshot, you'll notice a problem with z-order on the windows: even though Chromium is below gedit, Chromoium's '''chrome web store''' content is displaying above gedit. I'm filing a separate issue with Ubuntu over this, but that should not affect VirtualBox's ability to take a screenshot, as it really should just be slicing off a copy of the final rendered output.",Aren Cambre
18299,cannot start guest from snapshot,Mac OS X,Windows,VirtualBox 6.0.0,2019-02-10T00:10:05Z,2019-02-10T00:10:05Z,"Restored current state from snapshot. Snapshot fails to start:

Failed to open a session for the virtual machine IE11 - Win7.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

Can then restart from this point but enters error recovery in Windows. If I then pause and save another snapshot, I cannot start from that snapshot either.
",keefw
18351,The VM session was aborted,Linux,Windows,VirtualBox 6.0.2,2019-02-10T03:55:53Z,2019-02-10T03:55:53Z,"I'm using virtualbox6.0.0 on Ubuntu18.10 and run Windows XP as guest os, every time it throw error when I restore a sleep session:

The VM session was aborted.

返回 代码: 
NS_ERROR_FAILURE (0x80004005)
组件: 
SessionMachine
界面: 
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

I have upgrade to 6.0.2, but not fix.
",shada
18399,restore an acronis (.tib )backup of solaris10 OS into VM,Windows,Solaris,VirtualBox 6.0.4,2019-02-10T08:23:57Z,2019-02-10T08:23:57Z,"hello
i got a backup of my solaris10 OS with acronis 2018 and restored in VirtualBox.
the system comes up and restart periodictly !
please help",bakia
18406,no 64 bit guest support in VB on  intel 64bit CPU and 64bit Kubuntu 18.4 host,Linux,Windows,VirtualBox 6.0.4,2019-02-10T08:40:38Z,2019-02-10T08:40:38Z,"VTX is enabled in bios, Kubuntu 18.04 64bit host OS is running fine, Virtual box 64 bit is installed latest version and matching Evtension Pack. However there is no 64 bit support for the guests, only 32 bit.
This feature was working previously on the same machine on Kubuntu 17.1, but doesn't work any more after fresh install Kubuntu 18.04., Kubuntu 18.10 has same issue.
Hint: problem could be CPU specific",ElenaLight
18424,Host crashes when using VirtualBox,Windows,Linux,VirtualBox 5.2.26,2019-02-11T03:19:50Z,2019-02-11T03:19:50Z,"The problem I have is that sometimes my host (Windows 10 laptop) crashes sometimes when I am using VirtualBox. This only happens if I close the laptop or if it goes to sleep while a VM is still running. 

Whenever the laptop goes to sleep while a VM is running, the host will shut down all applications and restart the computer. Occasionally, there will be a BSOD instead of the host just restarting. I was wondering if this is a common issue when users leave a VM running. The VM was Ubuntu 18 and the host was Windows 10.",mttwh
18416,Each time VirtualBox starts VM from the saved state it hangs up with error E_FAIL (0x80004005),Windows,all,VirtualBox 6.0.4,2019-02-11T08:05:44Z,2019-02-11T08:05:44Z,"This problem occurs each time I start virtual machine from the saved state.

This problem occurs on VirtualBoX versions 6.03, 6.04 and 6.05 r128628

This problem occurs on any kind of virtual machines (Windows XP, Windows 7, Ubuntu etc)
",gastor
18425,Spontanious guest hanging after rollback,Linux,Linux,VirtualBox 6.0.4,2019-02-11T08:55:10Z,2019-02-11T08:55:10Z,"After a number of rollbacks to a certain live snapshot the guest (Ubuntu Server 16.04) seems to restore its state but becomes totally unresponsive. It just hangs on the prompt, the video doesn't change at all (even the cursor doesn't blink), and pressing any keyboard keys doesn't have any effect. Htop also shows that one of the cores is loaded 100% with the VBoxHeadless process. You may reboot the guest forcefully and it starts just fine. It's just I have to do a lot of rollbacks to live snapshots automatically that this occasional freeze bugs me big time.

P.S. If that makes any difference - I'm doing headless start instead of normal start

P.S.S. Bug seems to be very occasional - once in a few dozen times maybe
",CIDJEY
18430,DnD does work from Host to Guest but not the reverse,Windows,Windows,VirtualBox 6.0.4,2019-02-11T22:27:26Z,2019-02-11T22:27:26Z,"Hi, I'm kind of new with VirtualBox and I recently install VirtualBox 6.0.4 version with Win 7 OS as my guest machine, with my Win 7 pro host machine. As I did some searches before, I of course did follow all of the usual common recommandations about:(i) ""Setting>General>Advanced>Bidirectional"" stuff, as well as (ii) I did install the ""Guest Additions"" with the Devices recommanded procedure. Now, I can copy/paste text (ex. https sites adresses) both ways. I can also drag n drop pdf, zip files/docs (like the one attached hereto) from host to guest machine. Now, the only thing missing, is drag n drop from guest to host!! I attached the log files of both host and guest, as per recommandations of your collegue in previous ""Investigating drag and drop (DnD) problems"" (https://www.virtualbox.org/wiki/DnDDebug). Thanks for any kind of help from anybody.",TrueGeek
18429,VirtualBox 5.2.26 fails to build due to VBoxFUSE,Linux,Linux,VirtualBox 5.2.26,2019-02-12T10:57:52Z,2019-02-12T10:57:52Z,"Hello,

I'm using a fairly ancient system (Slackware 14.2), but the following is a bug I encountered building VirtualBox, and a patch that enabled me to build it successfully.

While trying to compile, I encountered this error:

{{{
  CXX     VBoxFUSE - {C}/VBoxFUSE.cpp
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:112:5: error: 'PVBOXHDD' does not name a type
     PVBOXHDD                pDisk;
     ^
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function 'bool vboxfuseNodeDestroy(PVBOXFUSENODE, bool)':
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:200:29: error: 'VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}' has no member named 'pDisk'
             if (pFlatImage->pDisk)
                             ^
}}}

After searching through the source code, and scouring the internet, I could not find a reference to '''PVBOXHDD''' anywhere.

Finally I found a very old copy of vdfuse ([https://github.com/vasi/vdfuse/blob/7e10fc7aeeffae251042055bc55fb83a09120156/include/VBox/vd.h]) which defined '''PVBOXHDD''' as '''VBOXHDD''', and I found further details that revealed '''VBOXHDD''' could be referenced here as '''PVDISK'''.

I created the following patch:

{{{
--- /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE-old/VBoxFUSE.cpp      2018-10-15 10:31:04.000000000 -0400
+++ /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp   2019-02-11 11:31:30.587919884 -0500
@@ -53,6 +53,7 @@
 #include <iprt/initterm.h>
 #include <iprt/stream.h>
 
+#define PVBOXHDD PVDISK
 
 /*********************************************************************************************************************************
 *   Structures and Typedefs                                                                                                      *
}}}

And upon continuing my build, it succeeded.",peterwwillis
18432,Ubuntu is failing to install,other,Linux,VirtualBox 6.0.4,2019-02-12T15:45:41Z,2019-02-12T15:45:41Z,"When installing Ubuntu (32x) the installation will hit a large error sending the following text in the attached files. I can sometimes get to the installation page where Ubuntu asks where I am from, and then the installation fails with the same error message. I believe this issue may be unrelated, however, Ubuntu will freeze continually. I managed to reduce the freezing-frequency by changing the video source component to 128MB instead of 12MB. 

I supply roughly 4GBs of RAM to Ubuntu.",ChachiChamp
18433,Application Error - The instruction xxx referenced memory at xxx. The memory could not be read.,Windows,Windows,VirtualBox 6.0.4,2019-02-12T23:38:53Z,2019-02-12T23:38:53Z,"Intermittently, a running Windows guest VM will crash and display the following error. The console window will then close on its own and return you to the VM manager.
Once it occurred during install of Windows 10 1809 and once after install and installing programs. I have rebooted the host in between the two occurrences.
Afterwards the VM is left in an Aborted state.
This has only appearing since installing VirtualBox 6.x, it has not occured before on v5.x.
The host is running Windows 10 1809 x64.",rjcuk
18335,Deleting a snapshot shows an incorrect estimated time (14714 days 5 hours),Windows,Windows,VirtualBox 6.0.2,2019-02-13T07:13:41Z,2019-02-13T07:13:41Z,"After upgrading VirtualBox to version 6.0.0, when deleting a snapshot, the same time is always displayed (14714 days 5 hours), even if the snapshot deletion only takes a few minutes.
The problem also exists in version 6.0.2.
See also:
https://forums.virtualbox.org/viewtopic.php?f=8&t=90855
https://forums.virtualbox.org/viewtopic.php?f=15&t=90741
",MisVin
17076,No sound from any guest OS,Windows,all,VirtualBox 5.1.26,2019-02-13T11:16:00Z,2019-02-13T11:16:00Z,I never get any sound from guest OSs.  I have tried many Windows and Linux guests with the same result.  The Host OS is Windows 8.1.  This problem has existed for many versions of VirtualBox,mafw
18436,Strange behavior for Full-screen minimize/restore on host screen 2,Linux,Windows,VirtualBox 6.0.4,2019-02-13T17:05:55Z,2019-02-13T17:05:55Z,"If my VB guest session is on host screen 2, a minimize/restore sequence will display the VM guest on host screen 1, while the full-screen menu will correctly be displayed on host screen 2.

The issue can subsequently be resolved by using the menu to switch to host screen 1 and then back to host screen 2 once again.

My configuration:[[BR]]
Virtualbox 6.0.4 and 5.2.26, No video acceleration[[BR]]
Host:  Ubuntu 18.04 running X Windows/GNOME[[BR]]
Video: NVidia 415.27 driver, dual monitors[[BR]]
Guest: Windows 10 (1809)
",John JJ
18434,Mouse Integration Issue version 6.0.4 r128413,Windows,Windows,VirtualBox 6.0.4,2019-02-14T09:51:44Z,2019-02-14T09:51:44Z,"Hi, 

I'm experiencing an issue with the mouse pointer in the latest release. When mouse integration is enabled the mouse pointer is distorted and very difficult to use. If I disable the mouse integration it looks and behaves as expected. I have looked on the forums and can't see any bugs logged for this version. 

Regards
James ",JamestheOracle
729,"If you delete an iso image,you can't remove it from the list",other,other,VirtualBox 1.5.0,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
17583,VBoxControl guestproperty set fails with error VERR_PERMISSION_DENIED,Windows,Linux,VirtualBox 5.2.8,2019-02-16T22:39:27Z,2019-02-16T22:39:27Z,"The VBoxControl commands below have run fine on numerous previous versions of VirtualBox no longer work on VirtualBox 5.2.8 in the specified guest/host

These commands are being run as root in the guest and fail as shown below:

[root@localhost sva.ledgerU]# VBoxControl --nologo guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountPrefix ''

VBoxControl: error: Failed to store the property value, error VERR_PERMISSION_DENIED

[root@localhost sva.ledgerU]# VBoxControl --nologo guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir ""/mnt/hgfs""

VBoxControl: error: Failed to store the property value, error VERR_PERMISSION_DENIED

",jimf
17933,RDP from iPad 3 (iOS 9.3.5) Problem Keyboard Access to Windows 10 pro,Windows,other,VirtualBox 5.2.18,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
18441,Crash host,Linux,Windows,VirtualBox 6.0.4,2019-02-17T19:11:30Z,2019-02-17T19:11:30Z,"I have developpe dopengl windows application[[BR]]

i have sended corrupt data in glDrawArrays without doing it on purpose ,
and i my machine guest and host freeze.",Sizy458
18377,VB 6.0.2 and 6.0.4 installation fails on macos 10.13.6,Mac OS X,all,VirtualBox 6.0.4,2019-02-19T18:36:43Z,2019-02-19T18:36:43Z,"This is not a security/KEXT problem (directly, at least). 

Trying to install VirtualBox 6.0.2 a week ago and again today with 6.0.4, ran into an issue where the install would get all the way through until the last screen reported Installation Failed. The workaround I found was to do an Advanced install and deselect the FUSE option. Unfortunately, this seems to defeat the point of having updated to the 6. series, other bug fixes, &c aside. 

Attached is the install.log which shows both the 6.0.2 and 6.0.4 install attempts. Both were ultimately successful once I deselected the FUSE option. ",wgd
18445,Problem when starting my virtual machin,Windows,Linux,VirtualBox 5.2.18,2019-02-21T16:22:15Z,2019-02-21T16:22:15Z,"i've downloaded an i386 version of Kali linux but when i start it in my virtual machin, it doesn't work.
It was giving me this error: this kernel requires the following features not present on the CPU:pae but i've been able to fix it and now when i start my virtual machin it tells me that it find a critical error when executing the virtual machin and the virtual machin has stopped working. ",Elbro
18447,libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory,Linux,Linux,VirtualBox 6.0.4,2019-02-22T03:57:05Z,2019-02-22T03:57:05Z,"Hi,

I have linux laptop with with ubuntu 18.04 OS.

          $lsb_release -a No LSB modules are available.
            Distributor ID: Ubuntu Description: Ubuntu 18.04.2 
            LTS Release: 18.04
            Codename: bionic

I have virtualBox 6 installed in it. Below is the VBox details -

Version 6.0.4 r128413 (Qt5.9.5) Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.


When I tried to create virtual OS using virtual Box I get below error - 

 libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory

I have attached the completed error trace



",rajpsgit
18446,Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available),Linux,Linux,VirtualBox 6.0.4,2019-02-22T09:28:11Z,2019-02-22T09:28:11Z,"Hi,

I have linux laptop with with ubuntu 18.04 OS.

$lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic


I have virtualBox 6 installed in it. Below is the VBox details -

          Version 6.0.4 r128413 (Qt5.9.5)
          Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

I have minidcos installed and tried to create virtual machine https://minidcos.readthedocs.io/en/latest/dcos-vagrant-cli.html# .

When I run the command `minidcos vagrant create ./dcos_generate_config.sh --agents 0` I get below error.

Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)

I have below permissions for my `/tmp` folder.

ajkumar@rajkumar:Downloads$sudo ls -ld /tmp
[sudo] password for rajkumar: 
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp
rajkumar@rajkumar:Downloads$ls -ld /tmp
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp






",rajpsgit
18449,Mouse Cursor Corrupts when running Citrix Session in VirtualBox,other,other,VirtualBox 5.2.26,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
18450,Main Window closes when second display has 150% scale,Windows,other,VirtualBox 6.0.4,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
18451,Guest Additions breaks keyboard on Windows Server 2019 Guest,Windows,Windows,VirtualBox 6.0.0,2019-02-25T14:54:51Z,2019-02-25T14:54:51Z,"Host = Windows 10 64-bit
Guest = Windows Server Core 2019 64-bit
Note: Core means no Desktop GUI included i.e. Command-line only

After installing Guest Additions, the keyboard no longer works inside the Guest, meaning I cannot type anything inside the guest command line. I used remote desktop to access the guest so I could uninstall Guest Additions after which the keyboard works fine.
",jahbwoy0
15174,Fresh install of windows 10 stops responding (repeatable).,Windows,Windows,VirtualBox 5.0.14,2019-02-25T17:36:04Z,2019-02-25T17:36:04Z,"Windows 10 guest stops responding after leaving it run in the background.  It may have something to do with how windows 10 sleeps or hibernates.   Maybe something to do with the power settings and how it lets hard disks spin down or other such things.   The screen looks fine (not black).  The mouse doesn't move.  It doesn't respond to Ctrl-Alt-Delete.   It doesn't respond to “Send the shutdown signal”.   Sending the “Power off the machine” does close the box and restarting it doesn't give me the options for safe more like windows 7 did.  

Running on Windows 7 Ultimate Host.",isgdre
15638,Win10 Guests stopped working with upgrade to 5.1.,other,other,VirtualBox 5.1.0,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
17980,Menuet64 network I8254X does not work anymore,other,other,VirtualBox 5.2.18,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
18452,"rc=-1908 , suplibOsInit : 3 ENOENT",Mac OS X,Windows,VirtualBox 6.0.4,2019-02-25T23:12:08Z,2019-02-25T23:12:08Z,"Version 6.0.4 r128413 (Qt5.6.3)
+
Windows 10 Enterprise (Evaluation - Build 201812) 20 GB download
=

Failed to open a session for the virtual machine WinDev1811Eval.

The virtual machine 'WinDev1811Eval' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

??
",A Denevér
18455,Unable to create VM: Error in sup3RHardenedWinReSpawn,Windows,Windows,VirtualBox 5.2.26,2019-02-26T07:02:47Z,2019-02-26T07:02:47Z,"I'm trying to run the VM that I created, unfortunately, there's a frequent error that I received. ""VirtualBox - Error in sup3RHardenedWinReSpawn"", hope to hear from y]ou soon. Thanks in advance,
",LMPadolina
17778,Double cursor on Mac OS host with unscaled HiDPI / W10 Guest with 200% scale,Mac OS X,Windows,VirtualBox 5.2.12,2019-02-26T11:24:24Z,2019-02-26T11:24:24Z,"Mac OS host (MacBook retina) with unscaled HiDPI enabled, 3d acceleration disabled (otherwise bug #17369 resurfaces). W10 Guest with 200% DPI scale (to compensate for the smaller fonts etc - is there a different way in W10 to do this?). VB Version 5.2.12 r122591 (Qt5.6.3), matching guest additions version installed. Result - double two cursors, host and guest, with guest cursor ""chasing"" host cursor. ",plexus
18456,Corrupted UI under Windows 7 with classic theme,Windows,Windows,VirtualBox 6.0.4,2019-02-26T13:48:47Z,2019-02-26T13:48:47Z,"Under Windows 7 with classic theme (144 dpi) the VirtualBox UI is corrupted: invalid checkbox size in the scrollable list of checkboxes, the checkmark is larger than the checkbox frame - see the picture.
",Codemaster
18457,BSOD on Windows 7 host,Windows,other,VirtualBox 6.0.4,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
18463,console boot hangs/highcpu without vbox serial & console=ttyS0 in grub,other,other,VirtualBox 6.0.4,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
18464,Virtual box 6.x hangs VM,Windows,Windows,VirtualBox 6.0.4,2019-03-01T11:17:35Z,2019-03-01T11:17:35Z,"Hello.
I'm running VirtualBox 6.0.4 in the following environment:
Host: Ms-Win10_64
Guests: Ms-Win10_64 Ms-Win7_64

After update to 6.x release, VM hangs after a few minutes ! ",Kotekino
18466,"Resizing VDI with VBoxManage, shows incorrect value in the Details pane and/or MediaManager",all,all,VirtualBox 5.2.0,2019-03-02T03:55:23Z,2019-03-02T03:55:23Z,"'''__Summary__'''\\
Resizing a dynamic VDI (no snapshots) from the CLI, does not reflect the new size in the Details pane and/or the MediaManager.

'''__Setup__'''
* __Host__: OSX 10.9.5, 10.11.6, 10.13.6
* __!VirtualBox__: 5.2.0, 5.2.27, 6.0.5 and 6.0.97, didn't try even earlier, they're EOLed.
* __Guest__: a Win7-32 and a FreeDOS VM, doesn't really matter.
* __VDI size__: 80 GB and 500 MB respectively.
Example with the Win7 / 80 GB VDI:
{{{
$ VBoxManage showmediuminfo /Users/Shared/VirtualBox/Machines/Win/Win.vdi 
UUID:           6b59350c-5ca0-4265-9920-0805864801dd
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /Users/Shared/VirtualBox/Machines/Win/Win.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       81920 MBytes
Size on disk:   14473 MBytes
Encryption:     disabled
In use by VMs:  Win (UUID: 54c42cec-1890-4ec1-ae7a-aacb7677e6db)

$ VBoxManage modifymedium /Users/Shared/VirtualBox/Machines/Win/Win.vdi --resize 102400
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

$ VBoxManage showmediuminfo /Users/Shared/VirtualBox/Machines/Win/Win.vdi 
...
Capacity:       102400 MBytes     <-- That's correct!
...
}}}
The problem is that in the Details of the !VirtualBox Manager the newly 100 GB ($NEW_SIZE) is '''__not__''' reflected. It still shows the VDI as being 80 GB ($OLD_SIZE).

Using the latest test/development builds at the writing of the ticket, 2019-03-01:
* '''5.2.0 !r118431, 5.2.27 !r129042''' \\
 Not even the MediaManager shows the correct size, it shows 80 GB. Only a ''__complete restart__'' of !VirtualBox correctly identifies the VDI as being 100 GB on both the Details pane and the MediaManager.


* '''6.0.5 !r129045, 6.0.97 !r129043'''\\
 Just opening MediaManager ""forces"" the Details pane to be updated to 100 GB, otherwise it's still identified as 80 GB in the Details.",Socratis
18339,VBox 6 unresponsive with ultrawide display,Windows,Windows,VirtualBox 6.0.2,2019-03-02T06:28:21Z,2019-03-02T06:28:21Z,"11520x2160, dual Nvidia 1080's. This display size works fine with VBox 5, upgraded to Vbox 6 and VM becomes unresponsive until I reduce the screen size back to 4k or lower. Using the VboxSVGA driver. Windows 10",jamesf007
18277,VBoxSVGA not showing correct resolutions,Linux,Windows,VirtualBox 6.0.0,2019-03-02T19:11:12Z,2019-03-02T19:11:12Z,"Host with Xubuntu 18.04 dual monitor: 1920x1080 and 2560x1080
Guest with Windows 10 registered and update and dual monitor enabled.VBox additions updated to 6.0.

In VirtualBox with VBoxVGA all works fine.

When changed to VBoxSVGA second monitor not showing correct resolution 2560x1080 in the list of supported resolutions. No problem with main 1920x1080 monitor.",vicsanc
8760,VMDK: VERR_SHARING_VIOLATION,Windows,Linux,VirtualBox 4.0.6,2019-03-03T04:57:10Z,2019-03-03T04:57:10Z,"When running in an administrator command line and attempting to create virtual drives from raw disks under a windows 7 host, vboxmanage fails with this error message.  I was previously able to use these commands to mount my ubuntu partition under virtualbox on a windows XP host.  

Regards,
Alaric

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands listpartition
s -rawdisk \.\PhysicalDrive0
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
5       0x83  0   /2  /1   29  /254/63           235          126
6       0x82  30  /1  /1   333 /254/63          2384       482013
7       0x83  334 /1  /1   1023/254/63         18119      5365773
8       0x83  1023/254/63  1023/254/63         17406     42475520
2       0x07  1023/254/63  1023/254/63        114470     78124095

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands createrawvmdk
 -filename ""c:\Users\alaric\mydrive.vmdk"" -rawdisk \.\PhysicalDrive0 -partition
s 5,6,7,8
VBoxManage.exe: error: VMDK: could not open raw partition file '\.\PhysicalDriv
e0'
VBoxManage.exe: error: Error code VERR_SHARING_VIOLATION at D:\tinderbox\win-4.0
\src\VBox\Storage\VMDK.cpp(3762) in function vmdkCreateRawImage
VBoxManage.exe: error: Cannot create the raw disk VMDK: VERR_SHARING_VIOLATION
VBoxManage.exe: error: The raw disk vmdk file was not created
",Alaric
18473,Windows7 VM keeps crashing,Windows,Windows,VirtualBox 6.0.4,2019-03-05T08:55:24Z,2019-03-05T08:55:24Z,"Good Day. Since I upgraded to V6.04 my Windows7(32bit) VMs keep crashing/freezing. It sometimes happens while I'm using one of my apps and almost all the time when I'm working in windows explorer. It is extremely frustrating and corrupts my projects, which means engineering time lost.

I though it is a problem on only one VM but I started working on another VM wit the same OS and it does exactly the same. At the moment it is unbearable and causes a lot of lost time.",Omega
18467,Unable To Install VM's,other,other,VirtualBox 6.0.4,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
18469,Version 6.0.4 r128413 (Qt5.6.2) Shared Folders not Accessible,Windows,Windows,VirtualBox 6.0.4,2019-03-05T09:47:01Z,2019-03-05T09:47:01Z,"When the save machine state on Version 6.0.4 r128413 (Qt5.6.2) shared folders disconnected and is not reconnect until system complete restart. Saved state is not possible with shared folders.
Shared folders drive letter seems in Win7 Explorer but not connected. User is not enter to the drive. 

Host: Windows 7 Ultimate 64 Bit
Guest: Windows 7 Ultimate 64 Bit
All extension package and VirtualBox Guest Additions installed.
",Flu
18471,Issue with OEL 7.2 on Macbook Pro VB 5.2/6 with Guest additions,other,other,VirtualBox 5.2.26,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
18480,VBoxManage hangs after some parallel operations,other,other,VirtualBox 5.2.22,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
18478,"Impossible to copy files or dir beginning with a dot from guest to host, the 2 ones being Windows machines.",Windows,Windows,VirtualBox 6.0.4,2019-03-08T05:04:48Z,2019-03-08T05:04:48Z,"Impossible to copy '''files or dir beginning with a dot''' from guest to host, the 2 ones being Windows machines. 

This is the summary of several existing tickets : #17859, #17067, #16762.

",JLB
18479,Can't restart saved state on Windows 10. Exception breakpoint 0x80000003,Windows,Windows,VirtualBox 6.0.4,2019-03-08T06:02:22Z,2019-03-08T06:02:22Z,"Hi,

I'm running Virtualbox on a Windows 10 64b Pro 1803, and operating with a ""IE 10 - Win 7"" VM (downloaded on Virtualbox site a long time ago), NAT connection and Guest Add-ons installed.
The VM runs perfectly well, but if I stop it via Saving State and try to re-open it I systematically have a crash error. The session is then marked as Aborted and If I start it again it works (I have to start Windows via the ""BIOS"" ""Start windows normally"" menu option, though).
Is there any way I can solve this ?

I've seen in the tickets some which refer to that same breakpoint but they don't seem to apply to my case.

I attached :
- VBox.log
- VBoxHardening.log
- Screenshots of the various error messages I get

Thanks in advance.",jeanmiraptor
18361,VirtualBox 6.0.2 assertion failed while starting a macOS VM,Mac OS X,other,VirtualBox 6.0.2,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
18481,Upgraded to 6.x and now VB is broken,Windows,other,VirtualBox 6.0.4,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
18483,Failed to open session,Windows,Linux,VirtualBox 6.0.4,2019-03-09T21:02:07Z,2019-03-09T21:02:07Z,"Hi!

I saved state of my virtual machine.
Sometimes I get error:
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
",SChernolyas
17912,Crash on Dell docking station disconnect,Windows,Windows,VirtualBox 5.2.12,2019-03-11T10:30:45Z,2019-03-11T10:30:45Z,"Hello,

I'm using VirtualBox 5.2.12 r122591 (Qt5.6.2) on Windows 7 x64 Dell Latitude E7440. This laptop is usually connected with the docking station to which I have connected 2 monitors. One of those monitors is also a USB hub to which I have attached USB Wifi. I use this Wifi in my Virtual Machine.

My VM is also a Windows 7 x64 system.

Now... sometimes (not everytime but several times per week) when I disconnect laptop from docking station - VirtualBox crashes (only the window with virtual machine, the main window with list of machines is still open).
This isn't a new issue - with previous versions I had the same problem.


{{{
03:44:32.016942 VUSB: Detached '000000000eebcd30[proxy 7392:7811]' from port 1 on RootHub#0
03:44:32.026037 
03:44:32.026039 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000264c!!!
03:44:32.026081 
03:44:32.026082 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fed194d510
}}}
",dariuszszyc
18492,failure to install completely,Linux,Linux,VirtualBox 6.0.4,2019-03-13T00:20:57Z,2019-03-13T00:20:57Z,"This is a new Fedora Core system (fc31/rawhide). 

Installation file is: VirtualBox-6.0.5-129304-Linux_amd64.run

Again, the execution of vboxconfig has failed. I know, it's expected. The problem is one that I seem to have seen A LOT. Eventually it gets fixed but it seems to come back (always(?)). Is the fix NOT being propagated to the development tree? Here's the same old message that I've been seeing:

     22    ./tools/objtool/objtool orc generate  --module --no-fp --retpoline /tmp/vbox.0/SUPR0IdcClient.o
     23 /tmp/vbox.0/linux/VBoxPci-linux.c: In function ‘vboxPciFileWrite’:
     24 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
     25   375 |     set_fs(get_ds());
     26       |            ^~~~~~
     27       |            get_fs
     28 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: incompatible type for argument 1 of ‘set_fs’
     29   375 |     set_fs(get_ds());
     30       |            ^~~~~~~~
     31       |            |
     32       |            int

Am I doing something wrong?

Best regards,

Obiewan (George)
",George R. Goffe
10534,"Virtualbox overrides umask, making it unusable for shared setup",Linux,other,VirtualBox 4.1.14,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
18486,Black screen when trying to use Kali Linux,Windows,other,VirtualBox 6.0.4,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
13669,Virtual Box 4.3.20 stuck on creating process for virtual machine,Windows,Windows,VirtualBox 4.3.20,2019-03-14T16:03:24Z,2019-03-14T16:03:24Z,"Hi,
I have updated my Version from 4.3.12 to 4.3.20. since then I can´t start the VM. I stuck in creating process in Virtual Machines.
As Antivir I am using Symantec. 
My Host is Windows 7 64 bit Enterprise and the VM is a Win 7 32-bit
",cyberoner1
18495,VirtualBox NAT alias option use-same-ports (--nataliasmode1=sameports) has no effect on Ubuntu 16.04 host OS,Linux,Linux,VirtualBox 6.0.4,2019-03-14T20:53:00Z,2019-03-14T20:53:00Z,"== Steps to reproduce ==

    1. Create a VirtualBox VM as follows, accepting default values for anything not listed here:

        * Name: archlinux-2019.03.01-x86_64
        * Type: Linux
        * Version: Arch Linux (64-bit)

    2. Download archlinux-2019.03.01-x86_64.iso into the VM directory:

    {{{
cd 'VirtualBox VMs'/archlinux-2019.03.01-x86_64
curl -O http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/archlinux-2019.03.01-x86_64.iso
    }}}

    3. Confirm the MD5 checksum. First, display the expected checksum:

    {{{
curl http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/md5sums.txt
    }}}

    Verify on Linux:

    {{{
md5sum archlinux-2019.03.01-x86_64.iso
    }}}

    Verify on macOS:

    {{{
md5 archlinux-2019.03.01-x86_64.iso
    }}}

    4. Start the VM in VirtualBox, click '''Choose a virtual optical disk file''' (represented by a folder icon with an upward-pointing green arrow), and select the archlinux-2019.03.01-x86_64.iso file downloaded in Step 2.

    5. Boot the VM, selecting default options for everything.

    6. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), find two unused privileged (port number less than 1024) ports; for example, the following command will return nothing if both ports 1022 and 1023 are free:

    {{{
netstat -Wa | grep -E '1022|1023'
    }}}

    7. On the guest (64-bit Arch Linux 2019.03.01), confirm that the first free port from Step 6 is also free on the guest:

    {{{
netstat -Wa | grep 1022
    }}}

    If this  command returns any output, repeat Steps 6 and 7 until you have found two free ports.

    8. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), start listening on the second free port, the receiving port:

    {{{
sudo nc -l 1023
    }}}

    9. On the guest (64-bit Arch Linux 2019.03.01), open a connection to the receiving port on the host, originating the connection from the first free port, the sending port:

    {{{
nc -p 1022 ala-michaelk-lx1.corp.ad.wrs.com 1023
    }}}

    Replace `ala-michaelk-lx1.corp.ad.wrs.com` with the fully qualified domain name (FQDN) of the host, as returned by the `hostname -f` command.

    After running both `nc` commands, any text entered on the guest should appear on the host and vice versa.

    10. In another shell on host, look for connections to the receiving port:

    {{{
netstat -W | grep 1023
    }}}

    Initially observe that network address translation (NAT) has replaced the sending port (1022) with a random port (48946), as expected for `--nataliasmode1=default`:

    {{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48946 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48946 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
    }}}

    11. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), close the connection by pressing Ctrl-D (EOF) in the shell running `nc`.

    12. Close the guest console window, select '''Save the machine state''', and click '''OK'''.

    13. On host, switch the VM to `--nataliasmode1=sameports`:

    {{{
VBoxManage modifyvm archlinux-2019.03.01-x86_64 --nataliasmode1=sameports
    }}}

    14. In VirtualBox, click '''Start''' to restore the VM.

    15. Repeat Steps 8–11.

== Expected ==

The port number for the sending port (1022) is preserved, as seen on host macOS Mojave Version 10.14.3:

{{{
inu:~ michael$ netstat -W | grep 1023
tcp4       0      0  inu.corp.ad.wrs.com.1023  inu.corp.ad.wrs.com.1022  ESTABLISHED
tcp4       0      0  inu.corp.ad.wrs.com.exp2  inu.corp.ad.wrs.com.1023  ESTABLISHED
}}}

== Observed ==

The port number for the sending port (1022) is replaced with a random port number, as seen on host 64-bit Ubuntu Xenial Xerus 16.04.6 LTS:

{{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48972 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48972 ESTABLISHED
}}}
",interfrastic
18493,Guest W7-32Bit hanging with 6.4.0,Windows,Windows,VirtualBox 6.0.4,2019-03-15T14:45:17Z,2019-03-15T14:45:17Z,"After upgrading to 6.0.4, my long used Windows 7 32Bit guest hangs after a few minutes or sometimes hours. It seems to work allright at first.

No specific action has been identified which leads to it hanging. It happend while browsing the internet, using the file-explorer and even during logout or shutdown.

The VM has to be killed - no other ways to shut it down. It happend 4 times now, definitively too often for my understanding - and it never happened with 5.2.

I have already upgraded the Guest-Additions, to no avail.

Other guests (e.g. W10 64Bit) work fine on the same host - even more stable in terms of audio I dare say.

I do use dual-screen, which is a very useful feature - one reason for having upgraded from the very stable former versions.
",ufotech
18498,Machine switch to power off,other,other,,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
18510,#GP when Windows guest driver tries to write X86_CR4_PCIDE in non-HyperV environment,Windows,Linux,VirtualBox 6.0.4,2019-03-21T01:13:34Z,2019-03-21T01:13:34Z,"Change 70917 [1] introduced code to check whether CR4 can be modified. The code might work on Hyper-V, but not on other VMMs, as the code may set the X86_CR4_PCIDE bit in CR4 while CR3[11:0] is not zero, which generates a #GP according to Intel SDM:

""MOV to CR4 causes a general-protection exception (#GP) if it would change CR4.PCIDE from 0 to 1 and either IA32_EFER.LMA = 0 or CR3[11:0] ≠ 000H""

This issue can be triggered by installing a VM on VirtualBox 6.0.4 installed on a Windows _virtual_ machine that runs on top of other VMM platforms, such as VMware ESX. 

[1] https://www.virtualbox.org/changeset/70917/vbox/trunk/src/VBox/HostDrivers/Support/win/SUPDrv-win.cpp",jiajun
18517,"blocage VM WIN7/32bits quand utilisation ""partage""",other,other,VirtualBox 6.0.4,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
18488,standard tty control sequences ignored in all VM's,Linux,Linux,VirtualBox 6.0.4,2019-03-24T00:24:35Z,2019-03-24T00:24:35Z,"Running ubuntu 15.04 Server as well as newer Ubuntu Server VM's as well as RH and Suse within VMs.  When using terminal the typical control sequences (ctrl+c, ctrl+v, ctrl+d, etc) are ignored.  The ctrl portion is eaten/suppressed and the following letter is displayed.   When I run showkey and repeat those the ctrl portion is ignored.  On the host os showkey shows the correct values.  I've even tried a different usb keyboard to make sure it wasn't that.
Trying to run and work on a tty without these controls is extremely frustrating.
I've been researching for almost a week now without any results.   Please address? Thanks",bobmct
18502,"VBOXSVGA driver not update screen on ""Microsoft Store"" when scrolling.",Windows,Windows,VirtualBox 6.0.4,2019-03-24T01:42:01Z,2019-03-24T01:42:01Z,"VBOXSVGA driver not update screen on ""Microsoft Store"" when scrolling.

VBOXVGA will draw correctly.

This problem occurs with VBOXSVGA.

",0o0o
18514,Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).,Windows,Linux,VirtualBox 6.0.4,2019-03-24T03:45:44Z,2019-03-24T03:45:44Z,"Failed to open a session for the virtual machine Ubuntu.

Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",SChernolyas
18503,Mac wireless keyboard causes crash while running windows server 2019,Mac OS X,Windows,VirtualBox 6.0.4,2019-03-24T04:35:58Z,2019-03-24T04:35:58Z,"Running macOS 10.14.3 Mojave on
MacBook Pro (Retina, 15-inch, Early 2013)
Memory 16GB 1600 MHz DDR3
Running VirtualBox 6.0
Windows Server 2019 installed from 
17763.253.190108-0006.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

After Windows Server starts up, I inserted a control-alt-del and a dialogue box appeared
asking for my password. As soon as a struck the first key on my apple wireless keyboard,
the Apple macOS crashed. This is repeatable. I must have been nuts to run windows on my mac.",DouglasGoodall
18064,Audio/Video out of sync for Linux guest (since 5.2.20),Linux,Linux,VirtualBox 5.2.20,2019-03-26T03:15:54Z,2019-03-26T03:15:54Z,"Host: Ubuntu 16.04
Guest: Ubuntu 16.04

Playing video (e.g. in FF Browser on YouTube) always has audio out of sync (audio lagging behind).
Problem is reproducible.

The problem is NOT present for Windows 10 guests on same host system.

The problem was NOT present on VBox 5.2.18 and has been introduced with VBox 5.2.20.",sunrider
18049,"High cpu usage logd after sleep while using microphone, audio does not work",Mac OS X,Windows,VirtualBox 5.2.18,2019-03-26T16:33:58Z,2019-03-26T16:33:58Z,"1. Start up a virtual box Windows 7 VM on a Mac OS high Sierra host
2. Start-up activity monitor on Mac OS
3. Start up a sound recorder recording
4. Put the Mac OS to sleep
5. Wait five seconds and then wake up the Mac
6. Speak anything into the microphone for a second

Watch the CPU usage rise as shown in the screenshot below. Also, sound recorder inside the Windows VM will not be picking up any audio.

----
----


There also may be a crash that is related to this issue. It happens several times a day since I bought this model of MacBook Pro (2018 15 inch) because I use the microphone inside the virtual machine all day for dragon naturally speaking 15. I cannot find a reliable way to replicate this issue, but yet it happens several times a day. I will add more information to this ticket if i find a reliable way to replicate this but over the past month i have not been able to find a reliable way to replicate this. I am hoping this particular issue will be solved accidentally while solving the above issue
",Pi Guy
18489,Can't run VirtualBox as non root-user.,Linux,all,VirtualBox 6.0.4,2019-03-26T19:05:35Z,2019-03-26T19:05:35Z,"As a normal user I get:
> virtualbox
Qt FATAL: FATAL: The application binary appears to be running setuid, this is a security hole.
Abgebrochen

Existing vms can be started by e.g. vboxmanage startvm VMName 
",ThomKB
18520,Guest seems to be unresponsive,Windows,Windows,VirtualBox 6.0.4,2019-03-26T19:16:09Z,2019-03-26T19:16:09Z,My system freezes after running for a few moments. I start and application and it freezes. The log details that the Guest is unresponsive. This is a regular occurrence for me. I've checked previous tickets and comments on the forum and made changes accordingly but I'm still having the problem. If someone could point out what the issue may be I could fix it myself and should it occur again on another machine I would know how to resolve the problem. Any help would be greatly appreciated. I don't want to have to delete the machine again.,GavEB
18525,Cannot launch Virtual Machine - Argument aWidth is invalid,Linux,Linux,VirtualBox 6.0.4,2019-03-27T11:06:59Z,2019-03-27T11:06:59Z,"I can not launch any of my former created or new created VMs.

VirtualBox Guru Medition Error is showing up. Fatal Error (my translation from german text showing up)

Host: Ubuntu 18.04
Guest: any

Ataching log to investigate error.

Thanks for good work!",Mate
18526,Error warning at the boot,Windows,Windows,VirtualBox 6.0.4,2019-03-27T13:37:20Z,2019-03-27T13:37:20Z,"When i start the system, i get a warning about a bug and an option to ignore it  or turn of the machine. If i ignore it i cant capture input on my system and when i press right ctrl to do so it does nothing, just highlights the input capture botton in the bottom left corner.",ceca
17376,unable to start vm: VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH,Windows,Linux,,2019-03-28T09:33:28Z,2019-03-28T09:33:28Z,"I'm getting the following error again when trying to restore a saved machine. Same machine worked fine a couple of days ago.
No update or reinstall of VirtualBox in the meantime.

{{{
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)

Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)- Process Verification 
Failure: Executable file name and process image name does not match up.
}}}

After reinstalling VirtualBox by choosing ""repair"" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

VirtualBox: 5.2.3r119650

Host: Windows 10 64bits",rosch
18527,Updated MacOS Mojave to 10.14.4 - VirtualBox Crashes,Mac OS X,Linux,VirtualBox 5.2.26,2019-03-28T19:54:50Z,2019-03-28T19:54:50Z,"Using VirtualBox 5.2.26 and have extension pack installed.  There was a MacOS for Mojave this past week (10.14.4) and after installing VirtualBox opens but once I login it shows desktop for a brief second and goes back to the login screen.   The VirtualBox is running CentOS 7.

I am attaching the log file which contains a CFGM dump, CPUID dumps.   I don't see anything obvious in the log file ",dduck721
18528,"ISO Windows 7 SP 4 - USB visible in host, not showing up in tree",other,other,VirtualBox 6.0.4,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
18531,Vbox 6.0.4 / HOST - Windows 10 ( 1809 ) / GUEST - Raspbian Stretch Kernal v4.14 / Surface Pro 6,Windows,Linux,VirtualBox 6.0.4,2019-03-30T09:25:11Z,2019-03-30T09:25:11Z,"Bug noted regarding Mouse Visibility in reagrds to Virtual Machine Suspend as oposed to Shut Down.

Mouse integration on the Guest is Visible and Function upon Machine Startup.

If the machine is Shut Down ( Power off the machine ) then the mouse is Visible and Functional when restarted.

If the machine is Suspended ( Save the machine state ) then the mouse is Not Visible but Functional when restarted.

The condition is Repeatable and Consistent regardless of any changes in settings ( ie: PS2 Mouse vs Tablet ... )

NOTE: With the machine having been Resumed from a Suspended ( Saved State ) the mouse is visible on the host system and when hovering over the guest window. Once any region of the guest window is clicked on, then the mouse pointer disappears and only the effects of izems on the guest being hovered over is present. Mouse functionality is present, Only the Pointer is Not Visible.",ZAR
11143,vboxmanage startvm fails with E_ACCESSDENIED,other,other,VirtualBox 4.2.4,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
18534,Mouse Misalignment,Windows,Windows,VirtualBox 6.0.4,2019-04-02T16:30:45Z,2019-04-02T16:30:45Z,"When returning from full screen via the Guest mouse is off by a significant amount.

In the screen shot attached the mouse is where the red arrow is.  Clicked and line that highlights is off by 1-2 rows.",isgdre
18537,Keyboard not working in Virtual box while installing ubuntu 18.04LTS on Windows10pro on Microsoft surface,other,other,VirtualBox 6.0.4,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
18538,Launching Firefox crashes VM with The memory could not be read.,Windows,Linux,VirtualBox 6.0.4,2019-04-03T00:49:12Z,2019-04-03T00:49:12Z,"Installed Virtual Box 6.0.4 on Windows 10 1803 64 bit. Installed Red Hat Linux
6.10 Guest OS. 

After all the updates to Firefox and OS, launching the firefox
gives the message

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFBEA84E889 referenced memory at 0x000000000000001C. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------

Please fix this issue. 
",ketan
18542,Windows 8.1 Pro host freezes and reboots,Windows,Windows,VirtualBox 6.0.4,2019-04-03T20:49:53Z,2019-04-03T20:49:53Z,The Windows 8.1 Pro host freezes and reboots at random times with the Windows Server 2003 guest I had. I'm not sure whether this is related to VirtualBox or not. I have OpenShell/ClassicShell installed on the host computer and I don't know whether that's relevant. I without thinking deleted the virtual machine. I'll be creating a new virtual machine with the same setup and uploading the logs.,Eddy Smith
18533,Fedora 29 Guest Additions Failure,Mac OS X,Linux,VirtualBox 6.0.4,2019-04-04T11:41:12Z,2019-04-04T11:41:12Z,"Following upgrade to Kernel 5.0.3-200 and and subsequent upgrade to Kernel 5.0.4-200, the 
virtualbox guest additions fail. Symptom: guest screen no longer resizes automatically, and it is no longer possible to access shared folders. The only workaround I could find was to boot from Kernel 4.20.16-200 from which the screen performance is fine and it is possible to fully access shared folders as needed. 
VirtualBox Version: 6.0.4 r128413. Attempts to directly run the virtualbox guest addition: /run/media/<user name>/VBoxLinuxAdditions.run resulted in the error message: mod probe vboxsf failed.",E. Lewis
18541,Memory Reference,Windows,Windows,VirtualBox 6.0.4,2019-04-04T16:55:43Z,2019-04-04T16:55:43Z,"""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
IDK what happened?
Help please.",HadeedTheError
18546,If a rootFolder of a Novell eDir is Shared it can not be accessed,Windows,Windows,VirtualBox 6.0.4,2019-04-05T08:53:10Z,2019-04-05T08:53:10Z,"This happens since Oracle VirtualBox version 5.2.2 (so 5.2.0 is the last version where access to a Novell eDirectory Root Folder is possible!)

If you share a subdirectory of the eDir-Root it works!

This happens with Shared Server-Directorys from:
Novell E-Directrory Version 8.8. SP5
NDS Version: 20219.15

Host = Windows 7 Pro x64
Guest = Windows 10 LTSB x64",SO4620
18544,detection and configuration of pulse audio is inconsistent,all,all,VirtualBox 6.0.4,2019-04-05T09:05:02Z,2019-04-05T09:05:02Z,"
The way 'configure' detects and enables Pulse audio support is inconsistent and seems like there may be some steps missing.

- unlike most of the check_<something>() functions in configure, if check_pulse() is even
  called (more on that in a minute), and it detects that Pulse is present and usable, it
  doesn't do anything to enable Pulse.  In particular it does not call

    cnf_append ""VBOX_WITH_AUDIO_PULSE"" ""1""

  if it finds pulse.

- in addition to the fact that check_pulse doesn't set the define, check_pulse is limited to
  only being called on certain platforms, by this code:

{{{
  if [ ""$OS"" = ""linux"" -o ""$OS"" = ""freebsd"" -o ""$OS"" = ""netbsd"" ]; then
    if [ $WITH_PULSE -eq 1 ]; then
      check_pulse
    elif [ $WITH_PULSE -eq 0 ]; then
      cnf_append ""VBOX_WITH_AUDIO_PULSE"" """"
    fi
 fi
}}}

- finally, if you pass --enable-pulse to configure, it sets WITH_PULSE=2 ... which does
  nothing.


What I think should happen, to make this more consistent:

1) check_pulse() should be modified so that

    - if it finds working/acceptable pulse, it calls cnf_append to
      add VBOX_WITH_AUDIO_PULSE=1
    - conversely, if check_pulse is called and it *doesn't* find acceptable pulse,
      it should call cnf_append to set ""VBOX_WITH_AUDIO_PULSE"" """"

2) the code block that decides whether check_pulse should even be called should be adjusted so that it doesn't restrict the call by OS and it handles the --enable-pulse case.  Some preliminary code might look like:


{{{
  if [ $WITH_PULSE -eq 1 ]; then
    check_pulse
  elif [ $WITH_PULSE -eq 0 ]; then
    # --disable-pulse or platform default
    cnf_append ""VBOX_WITH_AUDIO_PULSE"" """"
  elif [ $WITH_PULSE -eq 2 ]; then
    # --enable-pulse was passed
    cnf_append ""VBOX_WITH_AUDIO_PULSE"" ""1""
  fi

}}}

These changes still honor platform defaults for darwin & haiku (both set WITH_PULSE=0 early
in configure).  If there isn't a platform-specific override, then the configure default of
WITH_PULSE=1 causes check_pulse() to be called, and it sets VBOX_WITH_AUDIO_PULSE appropriately, based on whether it found pulse or not.  Finally, if --enable-pulse is passed
to configure, VBOX_WITH_AUDIO_PULSE=1 is forced on, with no call to check_pulse.

I can provide patches to configure to make these changes, if you agree that the proposed changes are good ones and make things more consistent.

Thanks,

Tim",tim.mooney
18550,SIP has to be disable,Mac OS X,Windows,VirtualBox 6.0.4,2019-04-08T05:31:24Z,2019-04-08T05:31:24Z,"hi,
Im using VirtualBox for some time now on a MacMini.
Last week after an upgrade of OSX 10.13.16. I think since automatic update is activated. I got kernel errors as soon as I opened my windows guests.
Installation of new VirtualBox 6 wasn't possible, neither old versions
I disabled SIP, and All issues were solved.
After installation of VirtualBox 6. the Windows guest worked again
Enabled SIP again and the kernel errors appeared again
Can there be a setting change in my host that Im unaware of? I found other cases where users turned off SIP some time ago. So I think SIP is the strong medicine for another small issue.
Have you seen this before? I might have surged with the wrong key words. I dont know which rights need to be set for the kernel. I didnt change any settings actively so this must have happend during the update.
",itIsMe
18540,PPTP not connecting from Windows guest in 6.0.4,Windows,Windows,VirtualBox 6.0.4,2019-04-09T14:35:06Z,2019-04-09T14:35:06Z,"Hi,

Running Virtualbox 6.0.4 on Windows 10 x64 host, guests cannot connect to PPTP VPN. Tried with both Windows 7 x64 and Windows 10 32bits guests.

Connection hangs at ""checking username and password"" and finally disconnects with ""Error 734: The PPP Link Control Protocol Was Terminated""

Downgrade to 6.0.2 solves the issue, guests can connect again to PPTP.

Using bridged networking :-)

I will be happy to provide any log or test you may need.

PKX.",pkx232c
10754,Running xperf -on latency -stackwalk profile doesn't capture CPU Sampling data in Windows 8,Windows,Windows,VirtualBox 4.1.18,2019-04-09T15:49:32Z,2019-04-09T15:49:32Z,"When I run xperf -on latency -stackwalk profile in Windows 8 it doesn't capture CPU Sampling data (http://msdn.microsoft.com/en-us/library/ff191014.aspx, http://blogs.msdn.com/b/pigscanfly/archive/2009/08/06/stack-walking-in-xperf.aspx )

I've asked Microsoft and they told my that VirtualBox reports CPU h/w counters but then in fact not supporting them.",Andre.Ziegler
18556,I can´t able to start a virtual machine,Windows,other,VirtualBox 6.0.4,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
18557,Resolution import/export too low,other,other,VirtualBox 6.0.4,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
18558,Shutdown gracefully upon Windows Update reboot,Windows,all,VirtualBox 5.2.26,2019-04-11T15:10:48Z,2019-04-11T15:10:48Z,"On Windows 8 and up, it's difficult (at best) for users to prevent Windows from automatically rebooting after some automatic updates have been installed.

Several times, I have had one of my guest OS's running, and lost whatever was going on there when the process was killed during an automatic reboot.

My suggestion is to have options upon reboot to allow...
-- preventing the reboot
-- save guest machine state and exit
-- shut down guest machine and exit
-- power off guest machine and exit
",adaptatron
18547,"Host Win 10, Guest win XP works fine with 5.2.22. Win XP crash wtih 6.02 or higher",Windows,Windows,VirtualBox 6.0.2,2019-04-12T22:52:50Z,2019-04-12T22:52:50Z,,Trehin
18472,VirtualBox no longer working after latest set of Windows 10 security patches.,Windows,Windows,VirtualBox 6.0.4,2019-04-14T21:24:06Z,2019-04-14T21:24:06Z,"  I already submitted a Windows 10 feedback on this, as I'm not sure if it's a Windows 10 bug or a VirtualBox issue.
  
  After last week's Windows 10 Pro security patches, I can no longer start a VirtualBox virtual machine. On version 5.26, it gives the error
    verr_intnet_flt_if_not_found
when using a Windows 7 machine with a bridged wifi and Ethernet network. On
VirtualBox version 6.04, it just hangs forever at the ""Starting virtual machine"" screen, and I have to kill the process to cancel it.

    Even before this set of patches, it had run fine on 5.22 and 5.26, but 
6.04 would always hang after getting almost all the way through the boot process, up to starting most of the commands in the startup folder. That would happen from Windows 10 to Windows 7 or 10 VMs, and from Linux Ubuntu 18 to Windows 10 VMs with a similar set of startups, but not from Mac OSX to Windows 10; that one ran fine.",baseballbob
18460,Windows 10 guest works very slowly. This defect appeared with 6.0.x versions.,Windows,Windows,VirtualBox 6.0.4,2019-04-15T01:51:59Z,2019-04-15T01:51:59Z,"Host: Win10 Pro x64 1809 17763.316

Guest: Win10 Pro x86 1809 17763.316

Guest works correctly on 5.2.24.

This defect with guest performance appeared with 6.0.x versions. 

I have tested on 6.0.5 revision 128999 test build because I previously created ticket #18319. The defect of serial ports has probably been fixed.  

There is a performance problem with the guest machine.
It utilizes 50% of host CPU (4 cores), the guest works very slowly.
The log file is full of 
""TM: Giving up catch-up attempt at a ""x"" ns lag; new total: ""y"" ns""

The guest has a delay in every operation. Sometimes it freezes and suddenly unfreezes, makes some operations and freezes again.

Guest virtual hard disc blinks red/green dot on status bar most of the time but host hard disc is not active.  
",Vonkaz
18560,Guest Windows hangs on startup with guest additions installed,Windows,Windows,VirtualBox 6.0.4,2019-04-15T08:26:48Z,2019-04-15T08:26:48Z,"Host: Windows 10 1803 prof
Guest: Windows 7 x86 prof

Today I found that my old VM hangs on startup: black screen with ""Starting Windows"" message.
It doesn't connect to debugger (the debugging was turned on in the guest etc; in previous version of VirtualBox it worked).
I reinstalled Windows fresh in the guest.
It worked normally for a while.
I installed Guest Additions, rebooted and it hung.
Log file contains nothing interesting. The last message is:
00:05:11.555304 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
",iakovk
6314,Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER) on restoring from saved state,Windows,Windows,VirtualBox 3.1.4,2019-04-15T08:45:31Z,2019-04-15T08:45:31Z,"On restoring machines from a saved state, I regularly get the error:

Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER)

This occurs after the progress bar for the restore has reached 100%. It does not happen every time I try and restore a machine, but once it does happen, it will happen every time I try and restore that particular machine until I discard the saved state. Therefore, I suspect the problem is occurring while saving the state.

Both host and guest are Windows 7 64-bit. I have yet to experience this on other guest operating systems, but I have not used saved state on other guests as much as the Windows 7 ones, so that may be pure chance.


",Ravenous Bugblatter Beast
18559,shared folder host system locks virtual machine,other,Windows,VirtualBox 6.0.4,2019-04-15T09:19:54Z,2019-04-15T09:19:54Z,"I am having problems with 32 bit virtual machines in folder sharing, when I go to any shared system main folder the virtual machine hangs and all applications",jair pinho
18565,"Windows 8.1 host, Linux Mint 19 Cinnamon guest, seamless mode: no menu bar, no host key",Windows,Linux,VirtualBox 6.0.6,2019-04-17T09:36:27Z,2019-04-17T09:36:27Z,"On the lastest release of Virtual Box (6.0.6), and the one before that, I see the VirtualBox menu bar when booting Mint on my Windows 8.1 machine but, once Mint Cinnamon has finished booting, the menu bar disappears, seemingly never to return. Nor do the host keys (e.g. <host>+a) do anything. Thus, since I have the VM set to run in seamless mode, the only way to move outside the VM is to shut it down.

The version of Mint Cinnamon that I am booting is fairy vanilla: I have not customised it much or installed much software on it. It is running a 4.15 Linux kernel.

I do not seem to have the latest Guest Additions installed. I did, via Windows, download them and run them, but then my guest tells me they are not installed - and, it's the case that, because of the aforementioned problems, I cannot install them from within the guest.",JN
18574,Enhancement Dual Screen Single Click activation,Windows,Linux,VirtualBox 6.0.6,2019-04-18T15:56:53Z,2019-04-18T15:56:53Z,"Hi,
I am on Linux with dual screen and when I activate my Virtual Box (which has two screen) I have to manually click each Virtual box windows to bring them on top.
Expected enhancement would make one click on a Virtual Machine having two monitor to become on top.
regards",JGWill
18575,Virtualbox Graphics Adapter for Windows 8+ incompatible with AnyDesk,Windows,Windows,VirtualBox 6.0.6,2019-04-18T16:11:23Z,2019-04-18T16:11:23Z,AnyDesk show black screen when connect with Virtualbox Graphics Adapter for Windows 8+ installed,Prisma
18508,Re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset,Windows,Linux,VirtualBox 6.0.4,2019-04-18T19:06:00Z,2019-04-18T19:06:00Z,"System Information:
 * Host: Windows 10 Enterprise:
 * VirtualBox 6.0.4
 * VirtualBox Extension Pack 6.0.4
 * Guest: Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso)
 * VirtualBox Guest Additions: 6.0.4

Issue:
Upon installation of the VirtualBox Guest Additions 6.0.4 in Ubuntu 18.04.2 whenever you attempt to re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset.

Steps to Reproduce:
I have tested this various times by performing the following:
1. Performing a fresh installation of Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso) in VirtualBox with the following specifications:
 * Base Memory:  2048 MB (2 GB)
 * Processors: 2
 * Disk Space: 25 GB
 * Encryption Enabled: Yes (via the graphical Ubuntu installer prompts)

2. Navigating to “Devices -> Insert Guest Additions CD image”

3. Ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

4. Received the “Please install the gcc make perl packages from your distribution.” error message

5. Ran the “sudo apt-get update” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

6. Ran the “sudo apt-get install build-essential gcc make perl dkms” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

7. Ran the “reboot” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

8. Re-ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

9. Attempted to re-size the VirtualBox Ubuntu Guest Window which created a black Ubuntu Guest screen

10. Navigate to “Machine -> Reset”

If I ever re-attempted to re-size the VirtualBox Ubuntu Guest Window then it would re-create black Ubuntu Guest screen

To resolve this issue I would manual uninstall VirtualBox Guest Additions 6.0.4 from the Ubuntu Guest via the Command Line Interface (CLI) by performing the following steps:
 1) Ensure the “Guest Additions CD image” is still mounted to the Ubuntu Guest
 2) Run the “sudo sh /<USERNAME>/media/<VIRUTALBOXNAME>/VBoxLinuxAdditions.run uninstall” command

Outcome:
This issue needs to be resolved so that one can re-size the a Ubuntu 18.04.2+ Guest window",elyons
18576,VM disables bluetooth,Mac OS X,Windows,VirtualBox 6.0.6,2019-04-18T19:32:53Z,2019-04-18T19:32:53Z,After upgrade to new Version 6.0.6 bluetooth on iMac is turned off. Hence BT mouse and keyboard can't be used anymore. Connecting a wired mouse helps turn off VN and VB then bluetooth turns back on by itself. This problem did at first not exist with 6.0.4. But when going back to 6.0.4 from 6.0.6 with Time Machine the problem with BT still existed. The update must have changed something outside the VB itself. How can I solve the problem?,ALG
16720,Sound randomly stops working until vm restarted (Fedora vm on Debian host running VirtualBox 5.1.18),Linux,Linux,VirtualBox 5.1.18,2019-04-18T20:53:26Z,2019-04-18T20:53:26Z,"It happens very often that the sound stops working after a vm has been running for more than a day.

To clarify: ""Sound stops working"" means just that. For example, an audio file would be played in VLC and no sound would be produced (volume settings have not been changed).

There's a hint that it must have something to do with VirtualBox: After restarting the vm, it works again. It's not even necessary to restart the guest system. The vm can be suspended while VLC is running, it's then immediately resumed and as soon as it's running again, the sound is working again, the music played by VLC will come out.

This is an annoying bug because the vm has to be suspended/resumed all the time and sometimes that's not possible when certain connections should no be disrupted.

Nothing is logged in VBox.log. Host audio driver is PulseAudio, audio controller is ICH AC97 (default settings). Guest OS is Fedora 25. Host OS is Debian 8. VirtualBox 5.1.18.",Philip Seeger
18571,Vboxmanage export / import not working - invalid 'ovf:id' attribute,Linux,Linux,VirtualBox 5.2.28,2019-04-19T08:05:40Z,2019-04-19T08:05:40Z,"I'm running am Ubuntu 18.04.2 LTS Server with Virtualbox 5.2.28

Exporting an virtual machine with command line works without any reported error. Result is an *.ova file.

Importing this machine with the command vboxmanage import file.ova ends with this error:

root@nono2018:~# vboxmanage import 20210417_ADC2.ova
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Error reading ""/root/20210417_ADC2.ova"": missing or invalid 'ovf:id' attribute in operating system section element, line 18
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 307 of file VBoxManageAppliance.cpp

If I open the *.ova file with a editor, i can see
<Section xsi:type=""ovf:OperatingSystemSection_Type"" ovf:id=""-1160446143"">

Why is the ovf:id negativ?

Any suggestion to solve the problem?

Regards
Michael",Curval1230
18584,RFE: Add GAs CD insert option/visibility in the status bar,all,all,VirtualBox 6.0.6,2019-04-20T12:17:53Z,2019-04-20T12:17:53Z,"== Current State of affairs ==
Clicking on the CD icon in the status bar, you're presented with
{{{
Choose disk image...
Create ad-hoc VISO...
------------------------------------------
{list of previously used CDs/DVDs}
------------------------------------------
Remove disk                               <-- greyed-out if no CD/DVD is inserted
}}}
There's nowhere a mention of the GAs, whether they're inserted or not! Even worse, when the GAs are mounted, they don't appear anywhere on the list of used CDs.

== Proposed State of affairs ==
When the GAs ISO is '''not''' inserted/mounted:
{{{
Choose disk image...
Create ad-hoc VISO...
(Insert) Guest Additions CD image...      <-- *** NEW ENTRY ***
------------------------------------------
{list of previously used CDs/DVDs}
------------------------------------------
Remove disk                               <-- greyed-out if no CD/DVD is inserted
}}}
When the GAs ISO '''is''' inserted/mounted, option 1:
{{{
Choose disk image...
Create ad-hoc VISO...
(Insert) Guest Additions CD image...      <-- *** CHECKED ***
------------------------------------------
{list of previously used CDs/DVDs}
------------------------------------------
Remove disk                               <-- NOT greyed-out
}}}
or even better, option 2:
{{{
Choose disk image...
Create ad-hoc VISO...
Remove Guest Additions CD image           <-- *** s/Insert/Remove ***
------------------------------------------
{list of previously used CDs/DVDs}
------------------------------------------
Remove disk                               <-- NOT greyed-out
}}}
So, in summary:
* The whole menu's behavior stays as is, except with the addition of one menu entry.
* The menu can either be mimicking the Devices menu entry ""Insert Guest Additions CD image..."" which changes to ""Remove Guest Additions CD image"", or with the entry being simply ""Guest Additions CD image..."" which is either checked or not.",Socratis
18587,Host-Only Adapter reverse to 0.0.0.0,Windows,Windows,VirtualBox 6.0.6,2019-04-21T07:18:50Z,2019-04-21T07:18:50Z,"Hello, i was using Host-Only Adapter and when i try to configure adapter, it change back to 0.0.0.0 . I was searching but i only got sites without solution. Any help will be good.",SCr
18589,I am experiencing an issue starting my Windows 10 virtual machine,Windows,Linux,VirtualBox 6.0.6,2019-04-21T12:38:16Z,2019-04-21T12:38:16Z,"I downloaded a windows 10 virtual machine from their website and extracted the VM, I imported the virtual machine using the default settings and I received the error in the picture, I have increased my RAM dedicated to the machine and given it higher processing power, I use many VM's but only experiencing the issue with this virtual machine.",Erynh777
18590,keyboard losing functionality in guest,Windows,other,VirtualBox 6.0.6,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
18580,Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.,Windows,Windows,VirtualBox 6.0.6,2019-04-21T13:19:53Z,2019-04-21T13:19:53Z,"Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.
Host: Windows 10 1809 (64-bit).

Quote from VirtualBox 6.0.6 Release Notes:
''""This is a maintenance release. The following items were fixed and/or added:
[...]
User interface: fixed operation progress when deleting snapshots""
''",MisVin
17738,Distorted sound is still present in 5.2.10,Windows,Windows,VirtualBox 5.2.10,2019-04-21T19:23:16Z,2019-04-21T19:23:16Z,"This is follow-up ticket for the #17225. The situation has changed after some experiments in the audio back end. So now this distortion is always slightly here and can be clearly heard. But not in the dumped files. Previously this distortion came for thirty seconds every 5 or 7 minutes, but then the sound was heavily distorted. Hope this would help to locate and eliminate this issue.",boxer01
17614,Sound distortion and disappearance in Windows guest,Windows,Windows,VirtualBox 5.1.34,2019-04-21T19:26:35Z,2019-04-21T19:26:35Z,"This is follow-up ticket for some other tickets with this problem, such as #17225 or #17492. So after some issues appeared on the 5.1.32 it now gets even worth. On Windows 8 host / Windows 7 guest combination sound works nearly fine but completely disappears after some minutes. And there is nothing in the logs, everything looks fine here. On Windows 10 host and guest combination I can’t get any sound at all. Everything is kind of here and presented, but if you try to play something in the guest, the playing software got some seconds of hesitation at the first moment and then time starts to run without a sound. At the second try everything starts immediately but also without a sound. Going back to the previous version helps of course.

For socratis: I know that this is 1001 ticket about this, but I file it anyway. Because it is a new version and it’s a new behavior. So now I’m back to the 5.1.30 where I have no problems with sound. And in my case I simply see further declining in this version after we already got some slight problems in 5.1.32. Anyway I like to thank anybody how is working on this problem.",boxer01
18595,No drag and drop between guest and host,Windows,Windows,VirtualBox 6.0.6,2019-04-23T14:16:30Z,2019-04-23T14:16:30Z,"Hello all
There is the following problem since version 6.0.4.
After installing 6.0.6. there is still no Drag and Drop from Guest to Host.
Works only from Host To Guest.

OS Tested Windows XP and Windows 7 64 Bit.

Drag and drop services started (see log)

Thanks
Michele",MicheleGo
18586,"After 18.04 LTS Ubuntu installation and reboot on VM with Windows7 32bit as host, the guest freezes after 1 min",Windows,Linux,VirtualBox 5.2.28,2019-04-23T17:43:03Z,2019-04-23T17:43:03Z,"Hi,

I was able to successfully install the Ubuntu as my guest OS (though had lot of struggle to get there) however every time guest OS is started, it only works for few secs to a minute and then it is frozen completely.
I don't run any other program on my host OS and have monitored the resources as well to check on whether RAM is getting exhausted but i don't this so think that is happening.

Below is the Host setup that I have:
OS: Windows 7 ultimate 32 bit with 4GB Ram and Usable is 2.44GB

Virtual Box Version: 5.2.28

Below is the Guest setup that I have:
OS: Ubuntu 18.04 with 64Bit
Video Memory: 120MB
Base Memory: 1149MB
Pointing Device: USB Tablet
CPUs: 2
EFI: Enabled
3D Accelration: Disabled
Paravirtualization Interface: Default
Hardware Virtualization: Enabled Nested Paging and Enabled VT-x/AMD-V
",Dinesh
18596,QT Recursive repaint detected -> Segmentation fault (core dumped),Linux,all,VirtualBox 6.0.6,2019-04-24T13:16:01Z,2019-04-24T13:16:01Z,"~$ virtualbox

Qt WARNING: QWidget::repaint: Recursive repaint detected
Qt WARNING: QBackingStore::endPaint() called with active painter on backingstore paint device
Segmentation fault (core dumped)

---

Rescaling VirtualBox Manager window while looking at VBox.log in the VirtualBox Manager, same crash happens when i use the logviewer(ctrl+l).

Fault seems to happend shortly after scaling the window so bottom slide bar is supposed to disappear.",KjerkreitYtre
18599,Virtual machines VBOX 6 works extremely slowly on iscsi.,Windows,Windows,VirtualBox 6.0.6,2019-04-26T04:34:35Z,2019-04-26T04:34:35Z,"After updating virtualbuox for version 6, virtual machines with 
disks, connected via a protocol iscsi, began to work extremely slowly.
Network storage, showed that the iscsi-target opens 4 connections
at once.",Bigfut
18601,Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack error,Windows,other,VirtualBox 6.0.6,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
18602,Failure Restoring machine,Linux,Windows,VirtualBox 6.0.4,2019-04-26T15:20:30Z,2019-04-26T15:20:30Z,"On a virtual machine when i restore[[BR]]
I have error ""Session avorted""[[BR]]


[[BR]]

AND
[[BR]]
i have a other error in log :
''00:00:01.865624 !!Assertion Failed!!
00:00:01.865624 Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:01.865625 Location  : /home/vbox/tinderbox/6.0-lnx64-rel/src/VBox/VMM/VMMR3/PDM.cpp(1006) int pdmR3LoadExec(VM*, SSMHANDLE*, uint32_t, uint32_t)
00:00:01.865658 Stack     :
00:00:01.865658 00007fd31c0334e3 VBoxRT.so + 0x1f04e3''
",Sizy458
18600,Audio input gets automatically enabled,Linux,Windows,VirtualBox 6.0.6,2019-04-26T17:26:28Z,2019-04-26T17:26:28Z,"I have a Windows 10 Guest for which I would like to disable audio input (not output), I have used the settings and the menu options to disable audio input several times but it always seems to get re-enabled automatically after closing and opening VirtualBox.

Host: Fedora 29 with VirtualBox 6.0.7 r130207 (test build)
Guest: Microsoft Windows 10 Pro (Version 10.0.17134 Build 17134) with latest Guest Additions installed

Happy to provide more information :)",Damon Harris
18609,VirtualBox 6 feels/runs/works a lot slower than VirtualBox 5.2,Linux,all,VirtualBox 6.0.6,2019-04-28T06:15:29Z,2019-04-28T06:15:29Z,"I wonder why VirtualBox 6.0 is quite slower than VirtualBox 5.2 in many regards:

* it's a lot slower to launch: VBox 5.2 launches pretty much instantly, 6.0 takes 2-3 seconds.
* it takes additional time to launch guest OSes: I see no delay in VBox 5.2, while 6.0 takes a second or two.

My hardware:
 * SSD disk 500MB/sec read/write (it doesn't even matter, since consecutive launches impose the same delays when everything is cached)
 * 16GB DDR3 800MHz RAM in dual channel mode
 * Intel Core i5 2500
 * OS: Fedora 30 with XFCE, without any fancy features like desktop compositing. I also see the same slowness under CentOS 6.x x86_64.",Artem S. Tashkinov
18551,Virtualbox 6.0.4 stuck on power-on any VM guest,Mac OS X,all,VirtualBox 6.0.4,2019-04-29T10:09:04Z,2019-04-29T10:09:04Z,"Hi everybody!

I'm facing some difficulties to power my VMs with Virtualbox Version 6.0.4 r128413 (Qt5.6.3) on MacOS X 10.14.4 (18E226) Mojave. All of them get stuck so I have to reboot twice my laptop.

Log attached.",Omoges
18612,VM window can’t be seen or activated after host’s hibernation.,Windows,Windows,VirtualBox 5.2.28,2019-04-30T06:44:13Z,2019-04-30T06:44:13Z,"I have a Windows 8.1 x64 host with Windows 7 x86 guest combination. This happened only once, but I couldn’t find any similar ticket, so I file this one here. After my host was woken up from the hibernation I couldn’t activate the VM window. It can’t be seen in the taskbar, only the manager’s window is here and can be seen and activated. Beside the VM window is present in the list of the running applications (Alt + Tab) but you can’t activate it here as well. What could be done is: save the state of the VM from menu in the manager window and start it again. This way the window of VM appears in taskbar and can bee fully seen and activated. I put my logs here, probably somebody could see what went wrong here.",boxer01
16220,Improper font scaling in VB Manager,Windows,other,VirtualBox 5.1.10,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
18344,Windows 10 Issues with VirtualBox 6 VBoxSVGA Graphics Controller,Linux,Windows,VirtualBox 6.0.2,2019-05-03T20:44:38Z,2019-05-03T20:44:38Z,"I have setup a Windows 10 (1809 x64) VM on a linux host using VirtualBox 6.0.2. I have installed Guest Additions only (otherwise a clean Windows 10 installation. Everything seems to be working fine for a little while, then several strange things start happening. Most notably I am not able to run anything as administrator. When a UAC prompt should show the screen gets dark as normal, then instead of showing the UAC prompt I get an error dialog like the one below. This occurs when trying to run anything (not just the 7-Zip installer) as admin. When this starts happening I am no longer able to open the settings app (it opens the splash screen but immediately closes). Search also stops working in Cortona/Start. Some graphical glitches also start happening at this time.

[[Image(https://i.imgur.com/760eziG.png)]]

All of these issues stop when I switch the Graphics Controller from VBoxSVGA to VBoxVGA.

The host System used is a Dell Inspiron 15 5570 (Core i5, 16GB RAM). I have tried hosting with Linux Mint 19.1 and Windows 10. Always with VirtualBox 6.0.2.",Androprise
18619,VirtualBox 6.0.6 VM guest boot hangs with customized Fedora 30 Remix,Linux,Linux,VirtualBox 6.0.6,2019-05-03T21:46:33Z,2019-05-03T21:46:33Z,"I am creating a customized 64bit Fedora 30 Remix called Untochat. It is a Live Linux that allows you to install to harddisk, too. Live image boots fine with VirtualBox and installation to (virtual) VDI disks succeeds as well. But when booting the newly installed Untochat9 from disk, the boot never reaches graphical login screen.

The problem is deterministic, but I am unable to debug this myself. To reproduce the problem, Untochat ISO image (1.4GB) can be downloaded from:

  https://kolttonen.fi/iso/untochat9.iso

My main host is stock Fedora 30, but the same problem occurs on host MacOS Mojave 10.14, too.

Using libvirt + qemu + kvm on Fedora 30 host, everything works fine, so I suspect this could be a bug in VirtualBox 6.0.6. ",KaleviKolttonen
18622,Drag-and-drop replication causes BUG,other,other,VirtualBox 6.0.6,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永恒
18623,Kernel modules doesn't build with linux kernel 4.4.176 on openSuse 42.3,Windows,Linux,VirtualBox 6.0.6,2019-05-06T08:14:19Z,2019-05-06T08:14:19Z,"On openSuse 42.3 kernel modules doesn't build, error message is:

VirtualBox Guest Additions: Building the modules for kernel 4.4.176-96-default.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong

Error message in log file is:

/tmp/vbox.0/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);


Problem exist in version 6.0.4, 6.0.6 and latest testbuild 6.0.7 with proper VB guest extensions installed. Guest OS is updated.
",regnotyp
6324,Bridging guest on mac os x host vlan cause reception of malformed packets on gest NIC,Mac OS X,Linux,VirtualBox 3.1.4,2019-05-06T23:59:38Z,2019-05-06T23:59:38Z,"On Mac OS X 10.5.8 with a primary NIC named en0 and a virtual NIC named vlan3 accessing tagged traffic on en0

Guest is linux, eth0 is bridged to vlan3

Sniffing traffic with tcpdump on both host (vlan3) and guest (eth0) shows that some of the packets reaching guest contains additional 4 bytes after source/dest MAC address replicating the last 4 bytes of the source MAC.",Luca Ghedini
18616,Shared Folder error when using reposync,Linux,Linux,VirtualBox 6.0.6,2019-05-07T05:39:21Z,2019-05-07T05:39:21Z,"I have a couple of VMs (specifically CentOS6 and CentOS7) that I use to sync repositories for a disconnected network. EPEL, Cloudera, MySQL, etc. I keep these VMs pretty lean and but mount Shared Folders to a USB so that I can transfer the files. I download the files in the repos directly to the Shared Folder. For example to update the EPEL6 repository. I cd into a directory on the Shared Folder and use the command, reposync -n -d -r epel6. Since 6.0.6 this causes errors. To test it I tried a created a new directory and here is a sample output from one of the first attempted download:

[jrather@localhost sat]$ reposync -n -d -r epel6
[epel6: 1     of 12532 ] Downloading Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm
Could not retrieve package 2048-cli-0.9.1-1.el6.x86_64. Error was failure: Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm from epel6: [Errno 256] No more mirrors to try.

I get errors on every file. If I try the command within a directory on the VM (for example, /tmp or my user's home directory) everything is fine. It is only with the Shared Folder or trying to write to it. This error occurs with the CentOS7 guest too. I have tried it from both CentOS7 host and Ubuntu 18.04 host both with Guest Additions installed. I have also tried using a physical disk for the Shared Folder instead of USB drive with the same results. This used to work fine with 6.0.4 and previous versions.

I am not sure what else to submit but would be more than happy to if instructed.",jim.rather
18627,Guru meditation when execute perf top on Linux,Linux,Windows,VirtualBox 6.0.6,2019-05-08T03:39:04Z,2019-05-08T03:39:04Z,"This is always reproducible. Steps to reproduce:
1. Boot Windows 10 guest. Image from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines
2. Execute 'sudo perf top' on the Linux host shell.
3. VirtualBox shows a Guru Meditation error dialog.

Host: Ubuntu 19.04
Kernel: Linux 5.0
CPU: i7-8700K
RAM: 32GiB",Eric Zhang
18628,Windows 7 crash (blue screen) on start VM,other,Linux,VirtualBox 6.0.6,2019-05-08T12:26:26Z,2019-05-08T12:26:26Z,"On start VM, Widows 7 crash (blue screen).",akurgan
18631,Win10/Win 10 Error 0x80070032: Can't copy file from VM to Host through Shared Folders,Windows,Windows,VirtualBox 6.0.6,2019-05-08T23:07:38Z,2019-05-08T23:07:38Z,"This looks a lot like https://forums.virtualbox.org/viewtopic.php?f=2&t=84800&sid=99e7dde8811ab1c34e06e7a4e5057507 except for VirtualBox 6.0.6 r130049 (Qt5.6.2)

 Windows 10 Host (Surfacebook Laptop) [Version 10.0.17763.475][[BR]]

 Windows 10 VM [Version 10.0.17763.437][[BR]]

 VirtualBox 6.0.6 r130049 (Qt5.6.2)

The issue is I can't copy a file from the VM to the Host through the Shared folders path, both from the GUI and the command line with Host filesystems permissions set to [Everyone - Full Access].

Command Line Example:[[BR]]

C:\Users\v-crarno>copy C:\Users\v-crarno\Desktop\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM\Debug\Microsoft.Maker.Sparkfun.WeatherShield.winmd Z:\Users\craig\Documents\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM[[BR]]

'''The request is not supported.'''
        0 file(s) copied.

C:\Users\v-crarno>ver

Microsoft Windows [Version 10.0.17763.437]

From the GUI I get the File Copy Error 0x80070032.

What I -can- do from the VM on the Shared folder is ""Create a file"", and ""Delete a file"".  And I can make a copy of a remote file [copy z:\... z:\...].  I just can't copy from C:\... to Z:\... [VM to Host]

Another important difference is I'm logged into a Domain Joined system in the VM, and Windows Networking with a different userID on the host system. I opened up security on the destination folder to [Everyone-Full Access]",craiga
18630,Using dd to write to SD Card in a USB SD Card device results in an error,Mac OS X,Linux,VirtualBox 6.0.6,2019-05-09T00:54:35Z,2019-05-09T00:54:35Z,"NOTE: This may be a duplicate of ticket #17020. That issue appears to be the exact same problem and is not resolved.

On VirtualBox Version 6.0.6 r130049 (Qt5.6.3), using dd to write to SD Card using an external USB SD Card device has an error.

""dd: error writing '/dev/sde': No space left on device""

I am using a process I have previously used through VirtualBox and an external USB-A SD Card device to write to our stocked SD Cards. For simplicity, I used the same image that previously worked.

The host MacOS 10.14.4 has no issues with the exact same command.
NOTE: On host MacOS, may use ""brew install pv iozone""

Using ""iozone"", I established the max ""write"" speed at 7 MiB/s to our in stock, SanDisk Edge 16GB Micro SD HC 1 ""4"". We've been using these same SD Cards for years.


USB-C SD Card device on host MacOS completes correctly, at about 2.7MiB/s. I validated this SD Card on target hardware and it is correct.
{{{
bzcat 07626-38_sandisk-1.1.1-smc-2.8.0-with-ADCP.img.bz2 |  pv --size 15931539456 | sudo dd of=/dev/rdisk2 bs=512 conv=noerror,sync
[=================================================================================================================================================================>] 100%            
31116288+0 records in
31116288+0 records out
15931539456 bytes transferred in 5748.904531 secs (2771230 bytes/sec)
}}}


USB-C SD Card device on VirtualBox Ubuntu 16 error at this repeatable number of records out. Note the speed is too fast for this device.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sde bs=512 conv=noerror,sync
dd: error writing '/dev/sde': No space left on device===========================>                                                                                                                                                               ] 25% ETA 0:07:00
8131777+0 records in
8131776+0 records out
4163469312 bytes (4.2 GB, 3.9 GiB) copied, 142.747 s, 29.2 MB/s
3.88GiB 0:02:22 [27.8MiB/s] [=====================================================>                                                                                                                                                             ] 26%      
}}}



USB-A SD Card device on VirtualBox Ubuntu 16 also failed.
NOTE: This process and this exact USB-A SD Card device worked on some older version of VirtualBox, but unknown what that was because I did that about a year ago.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sdi bs=512 conv=noerror,sync
dd: error writing '/dev/sdi': Input/output error============================================================================================================================================>                                                   ] 76% ETA 0:20:48
23878697+0 records in
23878696+0 records out
12225892352 bytes (12 GB, 11 GiB) copied, 4279.2 s, 2.9 MB/s
11.4GiB 1:11:19 [2.72MiB/s] [===============================================================================================================================================================>                                                   ] 76%      
}}}


After powering off the VM and starting it again, using the USB-C SD Card device fails in a different way. Write speed is reasonable, but still has an error.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sde bs=512 conv=noerror,sync
dd: error writing '/dev/sde': No space left on device============================================================================================================================================================>                              ] 86% ETA 0:05:01
406158+80035 records in
486192+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 2192.37 s, 7.3 MB/s
12.9GiB 0:36:32 [6.03MiB/s] [======================================================================================================================================================================================>                            ] 87%   
}}}",Andrew Trapani
18071,Guest audio pass via vRDP no sound at all,Linux,all,VirtualBox 5.2.20,2019-05-11T23:40:16Z,2019-05-11T23:40:16Z,"HOST is Debian 9.5[[BR]]GUEST is Windows XP and Debian 8

Situation change after VBox 5.1.x ([https://www.virtualbox.org/ticket/17493 # 17493]). From weird sound to heard no sound with VBox 5.2.20.

Both clients, remmina and Microsoft's mstsc.exe, got the same situation.",NoNoNo
18634,"Linux host, Windows guest: screen corruption; and once the pointer changes it does not change back",Linux,Windows,VirtualBox 6.0.6,2019-05-12T02:15:12Z,2019-05-12T02:15:12Z,"To reproduce the screen corruption:

In Windows, set the 'scale and layout' option to 200%.
Do things.
Rebooting seemed to fix the problem but then the corruption returned.

To reproduce the pointer problem:

In Windows, set the 'scale and layout' option to 200%.
Open Word. Move pointer over toolbar and then to text area.

These problems makes the VM unusual at the 200% scale. I do not have the problems when the scaling is set to 175%.

Host: Linux Mint 19.1 Cinnamon x64; kernel 5.1
Guest: Windows 10 Home, build 1809
Machine: Lenovo Thinkpad X1CG2560x1440 6; 16GB RAM; Intel i7-8550U (8) @ 4.000GHz; Intel UHD Graphics 620; resolution 2560x1440 - HiDPI enabled on the host OS.
VirtualBox Version 6.0.6 r130049 (Qt5.9.5)
",JN
14271,"Start/Stop VM affect PPPoE link, with bridged networking.",other,other,VirtualBox 5.0.0,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
17597,Audio input broken on Windows 10 v1709 hosts,Windows,Windows,VirtualBox 5.2.8,2019-05-12T16:57:43Z,2019-05-12T16:57:43Z,"Audio input seems to be broken on Windows 10 v1709 hosts for any guest OS with the latest (didn't test for regressions) version of VirtualBox (5.2.8). I tested Win10 v1709 guests and modern Linux guests (Arch Linux). On an Arch Linux host with the latest VirtualBox a Win10 v1709 guest works fine. So this seems to only impact Windows hosts.

I've tried it on 3 completely different machines, an older Sandy Bridge era desktop, a modern desktop and a current laptop.

I've tried it on Realtek audio hardware with a 3.5mm microphone plug and a Logitech G533 wireless headset with a USB dongle. I tried disabling (from Device Manager) all other hardware devices except the Logitech device when testing this. I tried uninstalling the Realtek drivers as well.

I tried a clean install of the latest VirtualBox with a clean Win10 v1709 guest install with audio input/output enabled from the start.

Everything appears fine on the surface, audio input/output are enabled in VirtualBox settings, the devices appear in the guest, audio output works fine but audio input does not - there's only silence. The Windows Sound -> Recording dialog in the guest does not show any activity and ""Listen to this device"" does not result in any output. On the host itself it does work.

I didn't see a relevant looking ticket for this so I'm submitting a new one.",vbutilizer
11092,Add option to pass through guest trim/UNMAP by punching holes in VDI file to free host disk space,all,all,VirtualBox 4.2.0,2019-05-14T10:21:11Z,2019-05-14T10:21:11Z,"With VirtualBox 4.2, one of the new features was ""Storage: implemented support for discarding unused image blocks through TRIM for SATA and IDE and UNMAP for SCSI when using VDI images""

If my thinking is correct, that means that for expanding VDI files, the guest OS tells VirtualBox (via trim/UNMAP) which regions of the virtual disk can be erased. Then when the guest next writes new data, VirtualBox knows it can re-use those regions of the VDI which were marked as freed-up, instead of increasing the size of the VDI file.

The benefit of that is, the rate of expansion of VDI files is reduced. There is another related feature which would be very useful.

Windows and recent Linux kernels support ""punching holes"" in files. Unused regions of the file can be made into holes, so the file becomes sparse. The new hole regions read back as all-zero. You can think of hole-punching as analogous to trim/UNMAP, but for files.

It would be great if an option could be added to pass through trim/UNMAP requests from the guest, so that VirtualBox punches holes in the VDI file. Benefits of that:
 - When files are deleted in the guest, the VDI file would occupy less disk space on the host. Very useful if you're tight on disk space. The amount of space occupied by the VDI file would be roughly equal to the amount of space actually used in the guest. E.g. 100GB VDI, guest has used 50GB of that -> VDI occupies ~50GB on host, even though the apparent VDI file size may be larger. (Expanding VDI apparent file size will correspond approximately to the high water mark of disk usage in the guest.)

 - VDI would always occupy the minimum amount of space on the host drive, without needing to do VBoxManage modifyhd --compact manually.

 - If the user has a fixed-size VDI file but needs more disk space on the host, they could enable hole punching and thus free up approximately the amount of free space in the VDI, on the host drive.
",Donuts
15758,"Blinking displays on Windows guests with DWM (10, Vista, 7, 8.x)",Linux,Windows,VirtualBox 5.1.2,2019-05-15T10:51:49Z,2019-05-15T10:51:49Z,"Hi,

I've remarked that since VirtualBox 5.0 (and further versions) any Windows guest with DWM has a very annoying blinking effect. It's very proeminent on Windows 10, 7 and Vista guest, much less on Windows 8 guests.

This problem appears especially once Firefox has been started in the guest, but also with Windows 10 start menu or if you start CCleaner in Vista with admin privileges. It is also much more likely to occur if you start the VM, then switch to another host window, and then switch back to the VM window.

Under Windows 10 you can also the problem when starting Age of Empires 3 in the guest.

Note that w/ VirtualBox 4.x such blinking problem did not appear.

Guests affected :
Windows 10 x64, Windows 8.1 x32, Windows 7, Windows Vista, all with guest additions 5.1.2 installed.
256 MB of VRAM allocated to each VM.
All updates installed to each VM.

Host :
Debian GNU/Linux Jessie 8 stable with all updates installed, including backports (Kernel 4.6.74). Arch AMD64
NVidia binary driver 367.27 (but actually the issue also appeared with older versions of the driver incl. 352.xx)
Intel Core i7 4790 (not overclocked)
32 GB system RAM
NVidia GeForce GTX 1070 (but the issue also occured when I have a GTX 970)",gojul
18647,E_FAIL (0x80004005),Windows,other,VirtualBox 6.0.8,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
18648,Incorrect and unhelpful log reporting of VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES details,all,all,VirtualBox 6.0.8,2019-05-15T20:42:03Z,2019-05-15T20:42:03Z,"I set a bunch of EFI  ""Bios Dmi Information"" Key/Value pairs for a Windows 10 Guest on a(n arch) Linux host. I doubt very much that particular details of  VirtualBox, Host or Guest matter for what happened; but if they do, surely they are in the attached Log. When I started up the VM, the result was an abortion + pop-up as follows:

Configuration error: Invalid config value(s) for the EFI device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES).
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Clear Enough. But when I looked at the Log to see my error, the relevant line (line 663 in the attached log) was:´

00:00:00.993661 PDM: Failed to construct 'efi'/0! VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES (-2801) - A device encountered an unknown configuration value. This means that the device is potentially misconfigured and the device construction or unit attachment failed because of this.

It was not possible to determine from this which assignment contained the error or why. Comparing strings for minute errors is extremely tedious and error-prone, **especiallly** when the were no obvious typos in any of the strings I had set. 

Eventually I realized that the problem was simply that I had set an entirely non-existent Bios Parameter. The mistaken command was

VBoxManage  setextradata ""Win10 raw""  ""VBoxInternal/Devices/efi/0/Config/DmiSystemBiosVersion""    ""DELL   - 1072009 1.7.0 American Megatrends - 500""

and I now see that there is no such key in the documentation. so entering 

VBoxManage  setextradata ""Win10 raw""  ""VBoxInternal/Devices/efi/0/Config/DmiSystemBiosVersion""  

unset the key and enabled my VM to start -- but that took me an exhausting 45 minutes, when it could/should have taken me a trivial 2-3 minutes. I understand that it is ""feature request"" to ask that the log file contain information that it doesn't contain today. It is also a feature request to ask that there be an error returned already from a ""setextradata"" request which is 100% certain to cause a failure at VM Runtime. But it is a Buig Report to state that the log contains information which is misleading  and unhelpful:  I doubt that ""PDM failed to construct 'efi'/o! "" (which is what the log reports), and even if it did, it's not useful or relevant to the reader of the log. And it also wasn't a an unknown configuration value that was the problem, it was an unknown NAME of a Dmi Information key that was the problem. And since the code knew that the particular name it didn know was DmiSystemBiosInformation, it could and should have shared this information with the user. 

Please at least remove the misinformation from the log ; but I hope you will also consider REPLACING that  with the actual offending key or value, as a welcome time-saver to the user. 

Please note that I filed this under ""other"" as the component.  There is no component of either ""Log"" or ""Configuration"". I thought to file it under ""EFI"", but i am sure that it applies to BIOS VMs as well.

With thanks,
scott

",sbpetrack
18654,Todas as Máquinas Virtual Apresentando:  Código de Resultado:  E_FAIL (0x80004005),all,other,VirtualBox 6.0.8,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
18603,CentOS 7.6 guest in MacOS host receives spurious input when switching between desktop screens,Mac OS X,Linux,VirtualBox 6.0.6,2019-05-17T19:01:07Z,2019-05-17T19:01:07Z,"Host: MacOS 10.13.6 High Sierra
Guest: CentOS 7.6, running KDE

When using the MacOS ""Spaces"" virtual desktop feature, you can use Ctrl-Left arrow/Ctrl-Right arrow to move between desktops. If you make CentOS full screen, then move between virtual desktops, when you switch to the full screen VM, when you first click in the VM it receives some kind of input that causes windows (particularly maximized windows) to come out of maximized state and move locations. Sometimes, a desktop right-click contextual menu to be activated.

After this happens, CentOS gets in a state where it interprets clicks in the wrong location. For example, clicking on a foreground window results in a window behind receiving the click. Clicking on a title bar lets you drag a window, but double clicking on it does not maximize it as expected. However, if you click on the maximize button, the window maximizes.

Another symptom which seems to be related is when the VM is in full screen, moving the mouse pointer down to the bottom to cause the MacOS dock to show itself causes a similar situation to switching desktops.",Glen Kawano
18655,Release of shift key not recognised in Guest when Hostkey is Shift-Ctrl,Windows,all,VirtualBox 6.0.8,2019-05-17T19:30:06Z,2019-05-17T19:30:06Z,"When the Host Key is set to Right-Shift+Right-Ctrl, the release of the right shift key is not recognised when both shift keys are pressed and released. This leads to a behavior as if Caps Lock is active. Pressing and releasing the right shift key again ends this Caps Lock behavior.

The behavior has been observed with a Linux (Debian) Guest in an X11-Session as well as on the Linux Console. Even on the Grub Command Line this behavior occurred.

Using xev I could observe that there was no release event for the right shift key after pressing and releasing both shift keys.

Choosing a different Host Key solved the problem for me.",vbu
18642,Screen Video Recorder,Windows,other,VirtualBox 6.0.6,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
18497,Segfault due to audio driver,Linux,Windows,VirtualBox 6.0.4,2019-05-18T14:48:15Z,2019-05-18T14:48:15Z,"Windows guest is crashing within minutes after starting. The crash is reproducible on Ubuntu 18.10 and 19.04 (daily build). Also reproducible in current test build of virtualbox.
Issue occurs when:
1. Audio output is enabled and host driver / audio controller combination results in valid sound within guest os.
2. Virtualbox guest additions are installed. 

Audio input does not seem to effect the problem. Disabling microphone in hard- or software has no difference.

Logs:

Output in syslog:
{{{
Mar 15 15:37:32 m-7223 kernel: [ 3061.086031] EMT-3[28881]: segfault at 7f4a46dfcfec ip 00007f4a8b7b9594 sp 00007f4a46efb8c8 error 4 in libc-2.29.so[7f4a8b655000+173000]
Mar 15 15:37:32 m-7223 kernel: [ 3061.086048] Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
}}}

No relevant log in (guest) windows event viewer.
Audio debug logs and VBox.log are attached.",06b7e
18379,New OS/2 shared folders feature locks up the guest => Fixed in SVN,Windows,other,VirtualBox 6.0.4,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
18659,Virtual Machine Freezes after host desktop switched,Windows,Windows,VirtualBox 6.0.6,2019-05-19T14:24:43Z,2019-05-19T14:24:43Z,"I have a Windows 2000 VM running under VirtualBox 6.0.6 r130049 (Qt5.6.2)

This is upon a fully up-to-date Windows 7 Ultimate host machine, using a  tool called Dexpot to switch host desktops upon a three-monitor system.

When I switch back to the desktop upon which the previously functional and running VM is displayed, the VM is locked up.  The only way to recover it is to pause and snapshot the VM, close it and then start it up again (not always successful in such cases).

As I have been using Dexpot for some years and can definitely say that the only software on the host affected by this problem (out of literally hundreds of software engineering tools, including VMWare, and office applications) is VirtualBox.

Is this a known problem and can it be fixed?
",Alex Tidmarsh
18661,Audio ouput is obfen disabled at start up since VBox 6,all,other,VirtualBox 6.0.8,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
18664,Reset of USB device causes failure to attach,Linux,Windows,VirtualBox 6.0.8,2019-05-21T11:28:08Z,2019-05-21T11:28:08Z,"For some time now we have been able to test our USB3 machine vision cameras in a Windows VM but a recent change to VirtualBox has introduced a device reset during the attach process. 
The cameras we use are designed for continuous running in a factory and so the reset being issued is causing them to go through a full reset to ensure that they can be recovered in a fault case. This means that they are disconnecting from the host causing VirtualBox to lose track and fail to attach them to the guest. 
If I set a USB filter it gets stuck in a loop of constantly resetting the device and failing to attach it.

Is it possible to configure VirtualBox to disable the new device reset feature either globally or for a specific device?",Dan
18666,feature request,all,other,VirtualBox 6.0.8,2019-05-21T15:52:31Z,2019-05-21T15:52:31Z,add built in boot to netboot.xyz (https://netboot.xyz/downloads/),foilguitar
18644,mouse doesn't work in new version,Linux,Windows,VirtualBox 6.0.6,2019-05-21T16:21:46Z,2019-05-21T16:21:46Z,"Hello
When I use a [java] robot to do something repetitive for me, mouse doesn't work when I'm not in virtual machine. sometimes I need to do something like that and I open few virtual machine in same time, but in new version it doesn't work anymore.
also sometimes, when I focus on virtual machine, right click occurs automatically and it bothers me.
both of them don't exist in previous versions. 

Thank you

Version 6.0.6_Debian r129722
I just installed it from repository and it was newest version.",Java
18626,Tabs moving to new window after inactivity,Linux,Windows,VirtualBox 6.0.6,2019-05-23T06:42:26Z,2019-05-23T06:42:26Z,"I think the trackpad on my laptop has a glitch.  This doesn't happen during host operation.  When I let my laptop idle for a bit, and then come back, as soon as I touch the touchpad, all internet tabs, except the first one, move to a new window.  At first I thought it was closing them all, but then I realized I had multiple firefox windows open, when I didn't open any new windows.  I don't know what's going on.  I tried searching for a solution and came up empty.",adamgfloro
18650,Ubuntu Issues,Linux,Linux,VirtualBox 6.0.8,2019-05-23T08:21:01Z,2019-05-23T08:21:01Z,"Good Evening,

I just wanted to raise an issue I have with Ubuntu on VirtualBox. I have tried increasing the memory, changing from dynamic to fixed memory, changing CPUs as well as changing various advanced settings.

I tried on a different laptop and it worked fine with 18.04, I exported the appliance and importing it onto this laptop failed. The only difference is that Hyper-V is not installed on the other laptop though it is on this. I saw there may be an issue with Hyper-V but I use both VirtualBox and Hyper-V.

I'd just like to raise this as a defect, and also this has been an issue on the current version and the base 6.0.0",MitchB
18660,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",Windows,Windows,VirtualBox 5.2.30,2019-05-23T09:01:44Z,2019-05-23T09:01:44Z,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",0o0o
17131,Wrong core count on THREADRIPPER system,Linux,all,VirtualBox 5.2.0 RC 1,2019-05-26T19:48:58Z,2019-05-26T19:48:58Z,"On Fedora F26 host system Virtualbox only see 6 physical and 12 virtual cpu'es  on a system with Threadripper 1920x (12 physical and 24 virtual cpu's)

testet on 5.1.28 and 5.2.0 rc1 118201",Knud
18678,macOS app nap: effecting performance of VirtualBox VM,Mac OS X,Linux,VirtualBox 6.0.8,2019-05-27T22:36:39Z,2019-05-27T22:36:39Z,"host macOS 10.14.5 (Mojave) iMac 19,1 (Intel i5, 6 core, 40GB RAM), guests linux (ubuntu 19.04, Windows10 1809) the `VirtualBox VM` process will get AppNap'd by macOS resulting in:

1. approximately 20-25% performance compared to when AppNap=no for cpu-bound guest process
2. while degraded, host still reports full CPU core consumption. to be clear, if running 1 cpu-bound guest process, when AppNap=no host reports 100% CPU utilitizatiion (expected), when AppNap=yes host still reports 100% CPU utilization (not expected).
3. this does NOT happen when VM is run headless (presumably because AppNap targets .app with GUI contexts)

Steps taken to produce problem:

0. rm `VBox.log`
1. launch linux guest with head
2. ssh into linux guest
3. launch `spin.rb` script to loop/bump counter, and every 1.0 second emit count/reset-count, output is @4,400,000/s
4. minimize (yellow button on macOS host) guest head
5. watch `Activity Monitor.app` CPU tab with added field `App Nap` and filter on `virtualbox`, and notice `VirtualBox VM` nap=`no`
6. watch `Intel Power Gadget.app` Frequency monitor, core pegged at turbo rate of 4.0GHz
7. wait for something around 30-60 seconds passes
8. notice (3) changed output from @4,400,000/s → @1,200,000/s
9. notice (5) changed nap from `no` → `yes`
10. notice (6) changed from 4.0GHz → 2.0GHz and stabilized at 1.5GHz
11. wait an arbitrary 45 seconds or so
12. un-minimize previously minimized guest head (from step (4))
13. notice (3),(5),(6) change back to output @4,400,000/s, nap=`no`, core=4.0GHz
14. shutdown linux guest
15. save `VBox.log`

related forum thread: https://forums.virtualbox.org/viewtopic.php?f=8&t=93183",PikeSandwich
18656,Cannot boot from .vmdk if 'Use Host I/O Cache' is disabled,Mac OS X,Linux,VirtualBox 6.0.8,2019-05-28T14:25:40Z,2019-05-28T14:25:40Z,"Attempting to boot VM from a raw disk fails when 'Use Host I/O Cache' is disabled. When the option is enabled the VMboots normally.

The disk is formatted as GUID with an EFI partition, a macOS HFS+ partition and 2 Linux ext4 partitions (root and swap).
",granada29
18597,Large icons when i drag from small to big monitor,Linux,all,VirtualBox 6.0.6,2019-05-29T09:39:05Z,2019-05-29T09:39:05Z,"I have a problem with virtualbox 6.0.X, when I have 2 monitors and one is 17' and monitor 2 is 32' then when I drop virtualbox from small monitor to larger then I have big icons in virtualbox. Others program works good. When I can then I send screen in attachment",liske1
18684,Mini Toolbar stop working in full srceen in 6.0.8,other,other,VirtualBox 6.0.8,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
18681,Windows 10 1903 + VirtualBox 6.0.8,other,other,VirtualBox 6.0.8,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
18683,Automount of Shared folder stopped working in 6.0.8,other,other,VirtualBox 6.0.8,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
18652,Reiner SCT CyberJack USB no longer works (reset full speed usb device ...),Linux,Windows,VirtualBox 6.0.8,2019-05-31T07:57:06Z,2019-05-31T07:57:06Z,"Since Virtualbox 6.0.6 it appears that the Reiner SCT CyberJack Standard Chipcard reader (USB) can no longer be used from within a Windows VM.

Card reader is detected ok by Linux
[  611.544511] usb 1-7: new full-speed USB device number 5 using xhci_hcd
[  611.879182] usb 1-7: New USB device found, idVendor=0c4b, idProduct=0500, bcdDevice= 0.01
[  611.879185] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  611.879187] usb 1-7: Product: cyberJack RFID standard
[  611.879188] usb 1-7: Manufacturer: REINER SCT
[  611.879189] usb 1-7: SerialNumber: 5287xxxxxx

After launching a Windows 10 VM (USB device connected automatically to VM) countless messages of type
[  612.661394] usb 1-7: reset full-speed USB device number 5 using xhci_hcd

and the CyberJack driver within the VM cannot access the chipcard reader.

*Additional info*
Symptom: The reader does not seem to accept the card if plugged in",Jörg Skottke
16762,Folder copy silently fails to copy children when folder name begins with a dot (“.”) and the destination resides in a shared folder,Mac OS X,Windows,VirtualBox 5.1.22,2019-06-04T06:05:24Z,2019-06-04T06:05:24Z,"'''Setup:'''[[BR]]
VB version 5.1.22 or 5.1.23 !r115382[[BR]]
Host: macOS Sierra 10.12.5 or 10.12.4[[BR]]
Guest: Windows 10[[BR]]
[[BR]]
'''Issue:'''[[BR]]
On Windows 10 guest copying a folder with a name beginning with a dot (“.”) to a shared folder results in an incomplete copy. For example a Visual Studio project folder with a “.vs” child folder. VBox seems to stop copying once it hits the .vs folder children. No error is displayed in File Explorer. Win 7 guest does not have this issue.[[BR]]
[[BR]]
'''Steps to reproduce:'''
 * Setup Win 10 guest.
 * Install Guest additions.
 * Create a shared folder on host and mount it in guest.
 * Using a command prompt to create a folder with a name beginning with a dot (e.g. md “.test”).
 * Create a file under .test such as “New Test Document.txt”.
 * In File Explorer right-click .test and select copy.
 * Right-click a destination folder on a shared folder, right-click and and paste.

Notice .test is created but “New Test Document.txt” is not present under it. [[BR]]
Also, using the command prompt to rename .test results in “The system cannot find the file specified”.[[BR]]
",pupSci
17067,Dir Copy Fails to Copy Files to Shared Dir,Linux,Windows,VirtualBox 5.1.26,2019-06-04T06:05:46Z,2019-06-04T06:05:46Z,"Running VB Version 5.1.26 r117224 (Qt5.5.1) on Linux Mint 18.2 Cinnamon x64. Guest is Windows 10 Home x64 version 10.0.15063. All with latest updates (including the Creator's Update). 
Several shared folders set up on the Host. Shared Clipboard & Drag and Drop set to Bidirectional. VB.log attached.

Problem: Copying a directory FROM the Windows 10 guest to a Linux Shared Directory results in only the first directory being created. No files or sub-directories are copied. This has only been the case since Windows 10 Creator's Update installed. The last version that did not have this problem was 5.1.22 but that was before the Creator's Update installed.

Steps to reproduce:-
1. In the Windows 10 Guest open two instances of File Explorer.
2. Set one to a directory containing files on the Guest and the other to a Shared Folder on the Host.
3. Drag the Windows directory to the Shared folder.

I'm finding nothing is transferred except the top-most directory but none of it's children.

This forum post refers: https://forums.virtualbox.org/viewtopic.php?f=7&t=83829",Craig100
18689,HiDPI detection does not work after sleep and switching monitor.,Mac OS X,Windows,VirtualBox 6.0.8,2019-06-04T09:21:02Z,2019-06-04T09:21:02Z,"I'm running a MacBook Pro (2018) with a Windows 10 guest. Before version 6 scaling used to work fine all the time. Now it's wrong almost all the time. At first I tried using the new VBoxSVGA adapter, but since the graphics are very broken #18397 I had to change it to the old VBoxVGA adapter, which works much better. Running without 3D acceleration is out of the question since the performance is totally unusable.

I usually run the VM in fullscreen at one of four virtual macOS desktops.

Usually I'm switching a lot between using the built-in retina display and two different external non-retina displays (one at the time) In between the switching I usually put my mac into sleep. After waking it up, the windows guest usually have very incorrect scaling. Sometimes it's half the size (half-pixels) and sometimes it's the double size (double pixels) and sometimes it's correct size (normal pixels). 

The solution is to switch between 100% scaling and 200% scaling or vice versa. That works most of the time unless it's in half-size (half pixels), then I have to shut down and restart the VM. I'm not sure why the 200% mode is called ""auto-scale"" since it never auto scales from a user perspective.

I also tried switching between fullscreen and normal mode, but that makes no difference.

On top of this, the VM screen is black some times after waking up. The only solution to that is to try a ACPI-shutdown and if that fails power off the VM and then restart.",klas
18675,File corruption on shared folder - Linux host + Windows 7 guest,Linux,Windows,VirtualBox 6.0.8,2019-06-05T00:38:48Z,2019-06-05T00:38:48Z,"Setup :
Host : Ubuntu 16.04 x64
Guest : Windows 7 x64
Shared folder (on ext4 partition) between host and guest

I'm using a Windows 7 virtual machine only for Adobe Photoshop CS6 x64.

Before v6.0.8 I installed v6.0.6 only briefly, I had to revert back to 6.0.4 because of the mouse integration bug. So I for the present issue I installed 6.0.8 over 6.0.4.

I encountered a strange behaviour with the shared folder I'm using to exchange files between the host and the guest. 
In Photoshop CS6 x64, after I installed VirtualBox v6.0.8, sometimes Photoshop tells me it couldn't read the TIFF files I had worked on before. And when it could, sometimes the content was scrambled.
I checked my images in other software (under Windows ''and'' Ubuntu) : correct.
I opened the files in the VM with Photoshop CS6 x32 this time : correct.
I checked my TIFF files with an utility called jHove, which checks the TIF file integrity : no errors.
So my image files are without flaws. I can save them in Photoshop but not read them back, at least in the x64 version. Weird.
I also copied the files directly on the guest : this time Photoshop CS6 x64 was happy.

For 2 days I have tested many things. It only occurs in Photoshop CS6 x64, when I'm using the shared folder.

So I decided to revert back to VirtualBox v6.0.4, and dang! Photoshop CS6 x64 was happy again with my files...

So my conclusion is the problem comes from the shared folder functions, but only when reading my files, not when I'm writing.

I'm including my v6.0.4 last log file, I didn't think about saving one when I was under v6.0.8 sorry.",Parazythum
18651,Extention Pack install failed,other,all,VirtualBox 6.0.8,2019-06-05T21:38:44Z,2019-06-05T21:38:44Z,"Het is niet gelukt het Extention Pack C:/Users/MAARTE~1.KES/AppData/Local/Temp/Oracle_VM_VirtualBox_Extension_Pack-6.0.8.vbox-extpack te installeren.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-15100' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Resultaatcode:E_FAIL (0x80004005)
Component:ExtPackManagerWrap
Interface:IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

",MJvK
18614,Windows clipboard borked (regression),Windows,Linux,VirtualBox 6.0.6,2019-06-06T17:50:14Z,2019-06-06T17:50:14Z,"VMs running under 6.0.6 with the bidirectional clipboard enabled break all cut & paste, whether within the VM itself or between Windows apps.",vboxsf
18688,VirtualBox intermittently crashes when cursor approaches app menu,Mac OS X,all,VirtualBox 6.0.8,2019-06-06T22:23:26Z,2019-06-06T22:23:26Z,"VirtualBox manager was open for a few hours with no machine running.  I went into macOS's System Preferences and adjusted the selection color to a custom value.  When I returned to the vbox manager, I went to close it via the app menu at the top of the screen, but when my cursor approached vbox's app menu, the vbox manager crashed.  The crash report is attached to this report.

This has happened at least two times this week.  I am unable to manually reproduce this issue.

macOS 10.14.5
3.2 GHz Intel Core i7
16 GB RAM
Intel UHD Graphics 630 1536 MB




",Will B
18582,Slow startup,Linux,Linux,VirtualBox 6.0.6,2019-06-07T06:38:42Z,2019-06-07T06:38:42Z,"Ever since VB 6.x, start up process of the VM is extremely slow. However, if performing multiple mouse clicks in a quick succession (10+) during the process, start up will perform almost in normal speed.

Virtual Machine is Android x86 project, version 8.1-r1",blubber
15833,Guest video driver doesn't work with host's Nvidia card,Linux,Windows,VirtualBox 5.1.2,2019-06-07T13:13:00Z,2019-06-07T13:13:00Z,"I have two video cards on my host system: Intel 530 and Nvidia GT 610. On Intel's card everything is okay, but when I'm switching to the Nvidia, guest Windows 10 doesn't load video driver properly and reports following message in device's properties: ""Windows has stopped this device because it has reported problems. (Code 43)"". Window auto resize doesn't work.",ashep
18696,Host-only interface does not support IPv6 NDP properly?,Windows,Linux,VirtualBox 6.0.8,2019-06-07T17:33:12Z,2019-06-07T17:33:12Z,"I'm having some issues with IPv6 networking via a host-only interface between a Windows 10 1803 host and Arch Linux guest...

Without configuring any additional addresses and just using IPv6 link-local addresses, I'm able to ping the guest intermittently from the host but the reverse does not work at all. It appears the host doesn't respond to neighbor solicitations...

IPv4 on the same interface works fine with the RFC1918 address and ARP...

See the attachments for command line output on both sides. Not included from the Windows side is the firewall rules from Windows Firewall but core stuff is allowed by default and I allowed incoming Echo Requests for ping testing.",vbutilizer
18693,Memory Leak in VirtualBox 6.0.8,Linux,Linux,VirtualBox 6.0.8,2019-06-08T07:34:02Z,2019-06-08T07:34:02Z,"Hello,

It seems like there's a memory leak in VirtualBox 6.0.8.

I'm running with a Linux host (Ubuntu 16.04) and a single Linux guest (Ubuntu 16.04) in headless mode, being accessed by another machine on the network via Virtualbox's RDP server.

What I see is that the ""VBoxHeadless"" process consumes more and more memory as time goes on, at a rate of about 100 MiB every few minutes. This continues indefinitely until the system runs out of memory.

The only thing running on the guest is an instance of Firefox with some web-based FB game.

I've attached the log and vbox file. Please let me know if there's anything else needed.

As of now, the system is up and running, consuming more and more memory.

Thanks,
Jake",unklejoe
18694,"Add ""minimize"" command to VBoxControl",all,Linux,VirtualBox 6.0.8,2019-06-08T07:43:27Z,2019-06-08T07:43:27Z,"I wish there was a way to minimize a VM from inside the guest using VBoxControl.  I have my host key set to right ctrl, which is kind of awkward to use, but I picked it because I didn't want it to shadow one of the modifier keys I use regularly in the guest OS.  Being able to programmatically minimize the window from inside the guest would make it easier to assign a convenient key combo without dedicating a modifier key entirely to VirtualBox.

More broadly speaking, it seems like all of the host key commands should be available through VBoxControl, but minimize is the only one I have use case for at the moment.",lolcatnip
18698,Проблема с запуском Kali-Linux,other,other,VirtualBox 6.0.8,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
18699,VBoxSVGA 3D acceleration issue on windows 7 guest.,Linux,Windows,VirtualBox 6.0.8,2019-06-08T14:38:49Z,2019-06-08T14:38:49Z,"Problem:
No 3D acceleration on windows 7 guest with VBoxSVGA adapter.

i posted all info here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=93460]
",navarobot
17492,Guest audio playback sound like fast-forward tape.,Windows,Windows,VirtualBox 5.1.32,2019-06-08T16:57:06Z,2019-06-08T16:57:06Z,"HOST is Windows 7 64-bit[[br]]GUEST is Windows XP

Additionally, some video playback be affected, too. (most files are MP4, quite few can test.)

Some walkaround I tried:
* Downgrade VBox to 5.1.30[[br]]-> Good, Back to normal.
* Boot same VM Guest in Debian HOST (5.1.32)[[br]]-> Good, Work as expected.",NoNoNo
18700,Virtualbox.exe - application error when running dxdiag or hl2 in Windows XP sp3 guest,Windows,Windows,VirtualBox 5.2.30,2019-06-09T19:36:13Z,2019-06-09T19:36:13Z,"When running dxdiag or hl2 in windows xp sp3 guest, appears window Virtualbox.exe - application error",nikitastepanov
18702,Windows Server 2016 guest completely hangs in loading UserProfileService after upgrading GA to 5.2.30,Windows,Windows,VirtualBox 5.2.30,2019-06-11T16:00:50Z,2019-06-11T16:00:50Z,"Version: VirtualBox 5.2.30
Host OS: Windows 2010 Professional
Guest OS: Windows Server 2016 Standard Version 1607 (64-bit)

on a Windows Server 2016 Standard Version 1607 (64-bit), immediately after upgrade from VBox Extensions v5.2.26 to v5.2.30 and the suggested guest reboot, Windows fails to come up completely and hangs permanently loading User Profile Service. 

""Please Wait for the User Profile Service"" with Windows startup spinner. 

PS: I have redone this 4 times after restoring from Snapshots... inclduing with the only change made the Guest Additions install. 
Note: the guest VM is running from .vmdk disks (as it was imported), but it was working fine on VBox 5.2.26, and still works fine in VBox 5.2.30 AS LONG AS I DON'T UPDATE GUEST ADDITIONS.  As soon as GA are updated to 5.2.30 + reboot, it explodes.


",mkorning
18703,VirtualBox doesn't record the video/audio on FreeBSD: the .webm file isn't saved,other,other,VirtualBox 6.0.8,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
18665,VBOX doesn't work,other,other,VirtualBox 6.0.6,2019-06-12T12:16:28Z,2019-06-12T12:16:28Z,"Until yesterday it works, now no.
Thanks 
Mattia",mattia.bonini@…
18707,Windows 1903 - Host Only Adapter - VM not starting,Windows,Linux,VirtualBox 6.0.8,2019-06-14T08:52:54Z,2019-06-14T08:52:54Z,"Problem with Windows 1903 and latest VirtualBox / Extension Package
VM won't start when a Host-Only Adapter was attached.

Removal and a new fresh install of VirtualBox did not solve this issue.
Under Windows 1809 the VM runs fine but not under 1903 it crashes.

This error occurs also by the newly created machine. Recreating a new Host-Only-Adapter with DHCP enabled don't do the trick, too.

* Version 6.0.8 r130520 (Qt5.6.2)
* Latest Ext Pack installed

Error Message:[[BR]]
{{{
Für die virtuelle Maschine Cacti konnte keine neue Sitzung eröffnet werden.

Failed to open/create the internal network 'HostInterfaceNetworking-
VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Technical details:
{{{
sc query vboxdrv

SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}
",Cookie
18711,SCSI port 7 can not be used,Linux,Linux,VirtualBox 5.2.30,2019-06-16T13:34:02Z,2019-06-16T13:34:02Z,"[root@rac01-priv ~]# lsscsi -d
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda [8:0]
[2:0:0:0]    disk    VBOX     HARDDISK         1.0   /dev/sdb [8:16]
[2:0:1:0]    disk    VBOX     HARDDISK         1.0   /dev/sdc [8:32]
[2:0:2:0]    disk    VBOX     HARDDISK         1.0   /dev/sdd [8:48]
[2:0:3:0]    disk    VBOX     HARDDISK         1.0   /dev/sde [8:64]
[2:0:4:0]    disk    VBOX     HARDDISK         1.0   /dev/sdf [8:80]
[2:0:5:0]    disk    VBOX     HARDDISK         1.0   /dev/sdg [8:96]
[2:0:6:0]    disk    VBOX     HARDDISK         1.0   /dev/sdh [8:112]
[2:0:8:0]    disk    VBOX     HARDDISK         1.0   /dev/sdi [8:128]
[2:0:9:0]    disk    VBOX     HARDDISK         1.0   /dev/sdj [8:144]
[2:0:10:0]   disk    VBOX     HARDDISK         1.0   /dev/sdk [8:160]

As you can see, when I attach disks to SCSI controller, I can never use the 7th one:  [2:0:7:0]. My OS is oracle linux 7.6",Nil
18713,Error when going to full screen Windows 10 (Host+F),Linux,Windows,VirtualBox 6.0.8,2019-06-17T09:43:57Z,2019-06-17T09:43:57Z,"When I go from reduced to full screen I loose the precision of the mouse pointer and sometimes no keyboard.

To get the keyboard again I go to the bottom menu use the menu line full screen line twice (Host+F). Sometimes I get the keyboard response again sometimes I have to do it once more.

The shift of the mouse pointer works immediately when using Host+F. The mouse pointer is shifted from about the size of a menu-bar only vertically.",alainsc11
18407,vboxmanage controlvm <> savesate crashes if 3D acceleration is enabled,all,all,VirtualBox 6.0.4,2019-06-18T09:40:00Z,2019-06-18T09:40:00Z,"I wanted to create headless vms server. I found an strange error. When in specific conditions you exec:
{{{
vboxmanage controlvm <vmname> savestate
}}}
you go something like:
{{{
$ vboxmanage controlvm <cmname> savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_ABORT
VBoxManage: error: Failed to save machine state
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg*)"" at line 622 of file VBoxManageControlVM.cpp
}}}
and vm is aborted.

It looks similar to [https://www.virtualbox.org/ticket/16437] but I collected more information.
Error occurs only when 3D acceleration is enabled. Moreover it usually disappears when VirtualBox GUI windows is opened on any(or many) tty. Sometimes opened window dosn’t help. Problem sometimes disappears till next reboot.

Most of my tries started with  vboxmanage startvm <vmname> --type headless via ssh but problem occurs also with normal vboxmanage startvm <vmname> in X environment.

It doesn’t matter what type of guest os family and type is set (you don’t have to install it).

I did tests which this hosts' os:
Win 10 on physical machine – error sometimes occur
Debian 9 on physical machine – error often occur
Centos 7.6 on physical machine – error almost ever occur
Debian, Ubuntu, Centos as VirtualBox Guest - error almost ever occur",domino-pl
18715,Resolutions >= 4096px wide break VboxVGA and VboxSVGA,Windows,Linux,VirtualBox 6.0.8,2019-06-19T17:22:15Z,2019-06-19T17:22:15Z,"When trying to use a DCI 4k monitor (4096x2160) in fullscreen mode, the resolution kept being set to 1024x2160. VMSVGA correctly supports the resolution, but with a huge performance hit.

With more investigation, it seems like the resolution width is being calculated as `resolution_width = requested_resolution_width mod 4096` with it falling back to 1024 if the result is 0.",SinisterMinister
5104,VirtualBox taskbar item flashing for no reason (or reason not apparent),Windows,other,VirtualBox 3.0.6,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
18701,virtual box and multiple ubuntu 16 vagrant images have intermittent hanging problems via ssh,other,other,VirtualBox 5.2.30,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
18710,sharing folders from windows 10 host to win xp pro 64 bits doesn't work,Windows,Windows,VirtualBox 6.0.8,2019-06-21T21:51:44Z,2019-06-21T21:51:44Z,"Hello,

i've tried to share two folders from windows 10 host system to win xp pro 64 bits (virtual machione) without success. i'm using oracle vm virtualbox 6.0.3 with guest additions.

is it a known issue and how can I solve it ? should i use an older version of virtualbox to make it work ?",Harlock59
18712,Digest mismatch (VERR_NOT_EQUAL),other,other,VirtualBox 6.0.8,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
18716,Installation on macOS 10.15 fails,other,other,VirtualBox 6.0.8,2019-06-21T23:07:22Z,2019-06-21T23:07:22Z,It is impossible to install VirtualBox to macOS 10.15,tianyl
18709,Problems importing .ova appliances on 6.0 versions,other,Windows,VirtualBox 6.0.8,2019-06-22T08:47:18Z,2019-06-22T08:47:18Z,"I've been experiencing an issue when importing .ova appliances on all 6.0 versions, included the latest ( 6.0.8 ).

Just after importing it, it works fine. But if I log on to Windows with another user and try to add (via ""Machine -> Add"" in VirtualBox Manager) the already imported virtual machine, I get an error message with result code ""VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)"", and the operation fails. In the details, it says ""Could not find an open hard disk with UUID ..."". Also, when I'm logged with the same Windows user that imported the .ova appliance, if I remove the virtual machine (without deleting its files) and then try to add it again (""Machine -> Add""), I get the same error. These problems never happened to me on 5.2 versions.

I've realized that, just after importing the .ova appliance, the '''.vbox''' file lacks section '''<MediaRegistry>''', and also subsection '''<HardDisks>'''. Despite this, for the same Windows user that has imported the appliance, for some reason it works at first.

A workaround that I've found is, just after importing the .ova appliance, to remove hard disks attachments and then add them again. Doing this, section <MediaRegistry> (and subsection <HardDisks>) gets written in .vbox file. After this operation, other Windows users can add the virtual machine.

Thank you.",MBE76
18720,Host system freezes as soon as the mouse pointer enters the VM on nVidia,Linux,Linux,VirtualBox 6.0.8,2019-06-22T16:19:15Z,2019-06-22T16:19:15Z,"Host system freezes immediately when mouse pointer enters the VM when running on nVidia with proprietary drivers. I tried to disable nVidia and run on Intel HD and the issue is not reproducible.
The rest of the system is perfectly stable when running on nVidia.
These are two logs of Virtualbox with different graphics controllers:

https://pastebin.com/azj2dG3v
https://pastebin.com/uCcQ45jL

After the mouse pointer enters the VM, the host freezes, so I cannot control the system anymore, I can only send sysrq and reboot. If I check kernel messages after the boot, this is what I found at the end of the previous session:

https://pastebin.com/n83NqFhA

I do not know where the issue comes from, so I tried to report the issue also to nVidia here:

https://devtalk.nvidia.com/default/topic/1056067/linux/virtualbox-freezes-my-system-when-on-nvidia-but-not-when-on-intel-hd/

but I thought I could also report to Virtualbox and see if together we can find a fix.

Host system is Kubuntu 19.04. Guest system I tried are KDE Neon and Kubuntu 19.04. I tried with official VirtualBox 6.0.8.",Luca Carlon
18718,VBox crashes using 32 bit Linux guest on a 64 bit Windows 10 host,Windows,Linux,VirtualBox 6.0.8,2019-06-22T17:04:28Z,2019-06-22T17:04:28Z,"I've created a virtual machine with a 32 bit Linux on a Windows 7 64 bit host.
Now I tried to use the same VDI disk file on a Windows 10 64 bit host computer.
But when I created a new virtual machine in the current Version of VirtualBox
using the existing VDI disk Image an exactly the same settings as on the
Windows 7 host the virtual machine crashes (""Guru Meditation"" - Fatal error)
immediately after selecting the GRUB boot options in the guest.

This problem could be fixed by choosing ""Linux 2.6 / 3.x / 4.x ('''64 bit''')"" as
the guest OS in the ""general settings"" for the virtual machine -- although the
Linux guest has only 32 bit (80386 32 bit ELF binaries).
",Martin_G
8242,VRDP shows black screen on connection,Windows,Windows,VirtualBox 4.0.2,2019-06-22T17:49:53Z,2019-06-22T17:49:53Z,"Windows XP 64 bit SP2 host, Windows XP 32 bit SP3 guest.

When I connect to a headless session via the Windows remote desktop client and the Virtualbox VRDP server, the display will be solid black. If no user is logged in. a blinking white cursor will display. If I start typing, the input fields and buttons of the login dialog will display with everything else remaining black. If I log in, the display will come up normally.

If there is a user logged in, clicking the mouse will cause a small square of the display to show. In this case, disconnecting and reconnecting will usually result in the display coming up correctly.",Russ Lehman
18721,vdi disk got filled up and now VirtualBox refuses to revert to an earlier snapshot,Linux,Linux,VirtualBox 5.2.18,2019-06-22T21:39:05Z,2019-06-22T21:39:05Z,"Hello,

I am running VritualBox 5.2.18, host OS being Ubuntu 18.04 and guest being Mint 19. 

In Mint I have a riscv/rocket-chip environment setup in order to simulate behavior of a processor and observe its output waveforms, given the input in the form of c/assembly programs. Once I had installed the Mint OS I created a snapshot, and then again, once I had setup the environment, I created another snapshot and only then moved on to run different simulations.

The output waveform files do tend to get big, so my VDI is 110 GB fixed-size. Nevertheless, yesterday the simulation went on and on, and the output waveform file simply filled the whole VDI, completely. 

That I conclude from this is the message I get when I try turning the VM in its current state:


{{{
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}


So, ok - it makes sense: the file got to big, filled up the disk, the VM can't boot. Ok, no problem there. However, once I tried bringing back the snapshot (either one of them), I get:


{{{
Failed to restore the snapshot intenuser of the virtual machine rockettest.

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
}}}


And this, definitely, is not ok - it brings me into a terrible position, as it completely destroys the work on setting up everything.

I tried increasing size of the VDI, but for some reason - I am not allowed to type in the new size (image attached - 1).

VirtualBox does allow me to enter the new size for a snapshot (image attached - 2), but once I click Apply, that leads to a new error:


{{{
Failed to resize the storage unit of the hard disk /media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi from 100.00 GB to 120.00 GB.

Could not resize medium '/media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi' (VERR_DISK_FULL).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}


Please help.",dndrdm
18725,WebCam passtrough doesn't properly pass format capabilities to guest GStreamer,Linux,Linux,VirtualBox 6.0.8,2019-06-25T07:26:33Z,2019-06-25T07:26:33Z,"When attaching a webcam to a Guest OS using Devices->Webcams menu, resulting device in the Guest system reports following format capabilities to GStreamer:
{{{
...
0:00:00.206792405 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   MJPG
0:00:00.207621489 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
image/jpeg, width=(int)1280, height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
...
}}}
(continues in similar fashion with similar formats)


This results in webcam being incompatible with CameraBin pipeline:

{{{
0:00:00.208131863 15881  0x88fee00 INFO        GST_ELEMENT_PADS gstutils.c:1227:gst_element_get_compatible_pad:<src-crop> Could not find a compatible pad to link to camerasrc-real-src:src
0:00:00.208198762 15881  0x88fee00 INFO                GST_PADS gstutils.c:1035:gst_pad_check_link: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209174846 15881  0x88fee00 INFO                GST_PADS gstpad.c:2378:gst_pad_link_prepare: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209487092 15881  0x88fee00 INFO                GST_PADS gstpad.c:2434:gst_pad_link_prepare: caps are incompatible
0:00:00.209526143 15881  0x88fee00 INFO                GST_PADS gstpad.c:2529:gst_pad_link_full: link between camerasrc-real-src:src and src-crop:sink failed: no common format
0:00:00.209583393 15881  0x88fee00 INFO           GST_PARENTAGE gstbin.c:1799:gst_bin_remove_func:<camerasrc> removed child ""src-crop""
0:00:00.209642419 15881  0x88fee00 WARN                 default camerabingeneral.c:87:gst_camerabin_add_element_full:<camerasrc> error: linking src-crop failed
0:00:00.209701572 15881  0x88fee00 INFO        GST_ERROR_SYSTEM gstelement.c:2145:gst_element_message_full_with_details:<camerasrc> posting message: GStreamer error: negotiation problem.
}}}


While on guest system or when attaching as a regular USB device, it reports the following format capabilities:
{{{
...
0:00:00.213225446 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   YUYV
0:00:00.213341622 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
video/x-raw, format=(string)YUY2, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
video/x-raw, format=(string)YUY2, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
...
}}}

And everything works fine. This makes a webcam incompatible with any application that uses gstreamers' camerabin, for example, a Qt applications.

Attached are exempts from different logs, but there isn't much of interest except for what is provided.

This has been tested on two Host 64-bit machines running Arch Linux and Ubuntu 18.04, with 64-bit Ubuntu 18.04 Guest and another 32-bit Linux-based Guest OS. Results are identical.",SuperPrower
18726,Unable to export,other,other,VirtualBox 6.0.8,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
18717,VM fails when send to background,Mac OS X,all,VirtualBox 6.0.8,2019-06-26T07:17:40Z,2019-06-26T07:17:40Z,One can run VM on macOS 10.15 but when vm is send to background it fails. This happens with any virtual machines. ,tianyl
11862,VirtualBox freezes on btrfs / add check for COW,Linux,Windows,VirtualBox 4.2.12,2019-06-26T07:52:50Z,2019-06-26T07:52:50Z,"On a linux machine with btrfs filesystem, installation of a guest goes just fine but at first restart the guest freezes with popup showing ""20%"" during launch phase.
Installing the same machine on XFS, no problems at all.
I've seen similar reports, but with slightly different behaviours and declared fixed.
host machine: linux 3.9.5 x86_64 (gentoo)
guests: W8/W7 64bit
attached: vbox.log of failed session",Fabio Coatti
18728,ntoskrnl.exe+939a0  error when i started virtual machines,Windows,all,VirtualBox 6.0.8,2019-06-26T16:01:36Z,2019-06-26T16:01:36Z,my virtualbox crash my windows7 when i start any virtual machine,luizprogrammer
18727,Problem when boot a VM,Windows,Windows,VirtualBox 6.0.6,2019-06-26T20:44:59Z,2019-06-26T20:44:59Z,I instal a Virtual Box to another PC and copy a VMs Folder. I add the VM. When i start the VM after few minute an error occurred,Giampiero1972
18637,"HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter WIn10 host, v6.0",Windows,all,VirtualBox 6.0.6,2019-06-26T20:47:30Z,2019-06-26T20:47:30Z,"Had VMs working.  Win10 1809 update, then stopped working on all VMs.  Now get ""Failed to open a session for the virtual machine KubuntuVM.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""

of course removed existing adapter.  Added a new one.  It was manually configured.  I did have to click Enable box.  And still get this message.",RoryGriffin
18692,No sound or internet with Virtualbox 6,other,Windows,VirtualBox 6.0.8,2019-06-27T14:13:57Z,2019-06-27T14:13:57Z,"Using ALSA and NAT. Tried an earlier version, sound also didn't work, had to revert to an old version of Virtualbox 5. Too many system-wide updates this time with my kernel and other software, can't revert, so if this is unfixable I'll probably have to go with VMWare until they can iron these bugs out. I've been using Virtualbox for years and years with occasional issues but now it seems I've hit a wall.

Also, for the record I have the same problems in the latest version of Virtualbox 5.",shillshocked
18729,virtualbox.exe - application error when running steam on windows xp sp3 guest,Windows,Windows,VirtualBox 5.2.30,2019-06-27T18:39:54Z,2019-06-27T18:39:54Z,"when running steam on windows xp sp3 guest, appears window: virtualbox.exe - application error",nikitastepanov
18730,Ignore extra entries in OVF manifest file (.mf),Linux,other,VirtualBox 6.0.8,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
9786,USB devices freeze VM instances and VB main window under certain conditions,Windows,Windows,VirtualBox 4.1.4,2019-06-28T19:44:54Z,2019-06-28T19:44:54Z,"In one certain instance I have found that any tested usb Headsets will freeze the VM and the VirtualBox windows. Since the latest upgrade when connecting a USB headset (I have tried 3), upon opening any program that would use the headset the VM will freeze. It will also make the main VirtualBox windw freeze to where you cannot shut down that VM or open new ones. I have tried with a soft phone, voice recognition and sound recorder. All produce the same effect.
1. open a Windows VM on a Windows host
2. attach a USB headset
3. start Windows sound recorder
next clicking on anything shaould freeze the VM indefinitely
This was tested with Win 7 Ult. X64 host and Win 7 Pro X64 guest",Mark S Klopf
18679,Segmentation fault on startup up of `VirtualBox` under sway-wm using Wayland,Linux,other,VirtualBox 6.0.8,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
18734,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Windows,Linux,VirtualBox 6.0.8,2019-07-01T09:46:42Z,2019-07-01T09:46:42Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
7982,OVA file made with VirtualBox 4.0 can't be read by VMware ovftool,Linux,Linux,VirtualBox 4.0.0,2019-07-01T22:52:08Z,2019-07-01T22:52:08Z,"I created a 32-bit openSUSE 11.3 virtual machine using VirtualBox 4.0.0 on a 64-bit openSUSE 11.3 host. The machine works fine. I then exported it to an OVA file using the Export wizard, which did not report any errors. But when I try to read it into VMware using VMware's ""ovftool"" conversion utility, ""ovftool"" reports an error:


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


I've attached the XML 'ovf' file - it is indeed calling this a 'virtualbox-2.2' machine, which the VMware tools apparently do not support. I haven't checked the VMware documents yet to see what they do support, but I can do that if you don't have that filed away somewhere.
",Ed Borasky
18735,Certain VM (RedHat) crashing module VBoxNetFlt if launch any other VM,Linux,Linux,VirtualBox 6.0.8,2019-07-02T10:01:17Z,2019-07-02T10:01:17Z,"I'm using come vms, but I have one merged from VMware with RedHat inside which crashing module VBoxNetFlt if start together with any other VM. If only ""problem"" VM launched - it's OK.
Crash accompanied with VirtualBox-Guru-Mediatation screen and after that there is no way to launch any VM (just not starting) until perform the full-reboot. 
Instead rebooting I've tried to reload modules VBox*, but module VBoxNetFlt cannot be unloaded with ""it's using"" reason (while it's not actually using).
Logs and dmesg included.",e01
18741,VBoxManage see fixed size disk as dynamic,Mac OS X,Linux,VirtualBox 6.0.4,2019-07-03T05:48:08Z,2019-07-03T05:48:08Z,"I have faced with the following problem during the attaching vdi disk to the virtual machine. 
The disk is fixed size:
{{{
VBoxManage showmediuminfo /opt/asm1.vdi
UUID:           8f62813f-0329-426a-8c65-def93934337a
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /opt/asm1.vdi
Storage format: VDI
Format variant: fixed default
Capacity:       20480 MBytes
Size on disk:   20482 MBytes
Encryption:     disabled
}}}
but when I try to attach it:

{{{
VBoxManage storageattach node1_rac --storagectl ""SATA"" --port 1 --device 0 --type hdd --medium asm1.vdi --mtype=shareable
VBoxManage: error: Cannot change type for medium '/opt/asm1.vdi' to 'Shareable' since it is a dynamic medium storage unit
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

}}}

Could you explain the reason?


",SAlex
18731,Fatal No bootable medium found system halting (with iso inserted),Windows,all,VirtualBox 6.0.8,2019-07-05T11:57:35Z,2019-07-05T11:57:35Z,"Error:
When trying to start a new vm with the disk and iso inserted into sata receiving error: Fatal No bootable medium found system halting. Solutions already attempted: changing from sata to ide, making it a live cd/dvd and hot pluggable, and updating to the most recent version (stable or not stable).",28202
18733,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Windows,Linux,VirtualBox 6.0.8,2019-07-05T12:06:57Z,2019-07-05T12:06:57Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
18736,attach two similar usb device always fail,Windows,Linux,VirtualBox 6.0.8,2019-07-05T12:10:22Z,2019-07-05T12:10:22Z,"Hi,
I want to attach two generic usb card reader, there is 3 problems :
- I can't differenciate which card in the menu (peripheral -> usb show me the same device twice)
- attaching the first device work, the second always fail
- once an attachement fail, the device will always be listed in peripheral -> usb, ejecting the device still show it, pluging the device again will create a new entry, trying to attach the device again will fail and so on...",JLM
18740,Win7 64 bit  guest crashes,Linux,Windows,VirtualBox 5.2.30,2019-07-05T12:16:10Z,2019-07-05T12:16:10Z,"reproduction steps:
1. I start the virtual machine
2. A window appears in which windows 7 x64 starts to load
3. After 10-30 seconds the virtual machine window closes.",art
18743,"Poweroff, Delete prompt NEVER REMEMBERS PREFERENCE",Mac OS X,other,VirtualBox 6.0.8,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
18744,Virtualbox causes an abend Windows when it opens a Linux VM,Windows,Linux,VirtualBox 6.0.8,2019-07-05T16:51:53Z,2019-07-05T16:51:53Z,"I Use Virtualbox since several years. My host is a Windows seven with 8 Go RAM. I tried several linux with success until some days. 
I had Linux Mint Plasma, Windows 10 as VM. Windows 10 works ithout problem. But when i tried to access Linux Mint, it abends Windows Seven. I get out Linux Mint from Virtualbox, and tried to re-install it. No success. Each try Abends Windows. 
I tried the Virtualbox 6.0.6 .... : same effects.

'''The message in Windows events is :
'''
Nom du journal :System
Source :       VBoxNetLwf
Date :         05/07/2019 16:08:37
ID de l’événement :12
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   Daniel-PC
Description :
Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf.
XML de l’événement :
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""VBoxNetLwf"" />
    <EventID Qualifiers=""49156"">12</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2019-07-05T14:08:37.444012300Z"" />
    <EventRecordID>794248</EventRecordID>
    <Channel>System</Channel>
    <Computer>Daniel-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\VBoxNetLwf</Data>
    <Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000BCAEC55CB4500000</Binary>
  </EventData>
</Event>

I Hope to understand this problem, and resolve it !
Thanks.",Speedycool
18732,.iso file not listed when attempting to add it to a VM,other,other,VirtualBox 6.0.8,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
18749,vbox VERR_BUFFER_OVERFLOW GTX 1650,Windows,Linux,VirtualBox 6.0.8,2019-07-09T03:32:08Z,2019-07-09T03:32:08Z,"Good day,

Any time I run anything that uses OpenGL, and I run with the 3D checkbox enabled, I receive this error...

OpenGL Warning: vbox Call failed with VBox status code VERR_BUFFER_OVERFLOW

I am running VB 6.0.8.

I recently moved my hard drive from an old machine to a new machine with...
i9 9900k with ROG-STRIX-Z390-E-GAMING.  If you need the full specs of the machine, just let me know.  Anyhow, I simply moved it and re-activated windows 10.

Unchecking the 3D box fixes the problem, albeit at a generally reduced performance for Google Chrome, my development IDE, etc.

I have attempted a re-install of virtualbox, as well as a re-install of the vbox client drivers, to no avail.

If someone wants me to run a special GTX 1650 build to try, just let me know.

Thanks.",Trent
16452,Guest OS time is not in sync with host OS time after host is awake from sleep mode,Linux,Windows,VirtualBox 5.1.14,2019-07-10T08:51:22Z,2019-07-10T08:51:22Z,"Details:
Host OS - Win 7 64x
Guest OS - Ubuntu Desktop 64x

Steps to replicate:
Start the Guest OS in VM box.
Put the Host OS in sleep mode.
Start the Host OS after some time from sleep mode.
Observe the clock on guest OS in VM, it displays the time when the host was put in to sleep. (I usually put to sleep after leaving work and start next day)
Even after login to Guest OS, the time doesn't sync have to manually sync.

Please see the screen shot for reference.
Couldn't find a reference to this issue in community.",anurag26
18750,Crash / BSOD of Windows 10 host when running any VM,other,other,VirtualBox 6.0.8,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
18752,BSOD When Running VM in Windows 7,Windows,other,VirtualBox 6.0.8,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
18747,vt-x imbricate grayed,other,other,VirtualBox 6.0.8,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
18756,Adding permanent shared folder through VBoxManage,Windows,all,VirtualBox 6.0.8,2019-07-15T15:18:49Z,2019-07-15T15:18:49Z,It is not possible to add a permanent shared folder while the VM is running with VBoxManage whereas it is possible from the GUI.,Luc123
18757,On Windows!0 very often the VM Win10 or Win7 goes in stuck state,other,other,VirtualBox 6.0.8,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
7756,Occasional Hang when saving machine state - data loss,Windows,other,VirtualBox 3.2.10,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
18759,documentation error -> fixed as of 17 July 2019 (6.0.x and later),other,other,VirtualBox 6.0.8,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
18742,Left and right modifier keys mirrored on Mac OS X 10.14.5 (Mojave) as host,Mac OS X,Windows,VirtualBox 6.0.8,2019-07-17T08:26:35Z,2019-07-17T08:26:35Z,"Repro steps:
1. Connect external keyboard
2. Under System Preferences --> Keyboard --> Keyboard --> Modifier Keys
Change option to command and command to option
3. Start VirtualBox
4. Under Preferences -->  Input --> Virtual Machine 
Set ""Host Key Combination"" press command + option to the left 
Note:  it says right command + right option

Impact: on Windows guest running a non US keyboard, e.g. Swedish layout, the option key is now alt gr and not alt

Same thing on 5.2.30

Might be something in Mac OS which also affect Emacs: http://emacs.1067599.n8.nabble.com/bug-34984-ns-right-command-modifier-has-influence-to-left-td478781.html",Lars
18669,Virtualbox causes a leak in cursors as reported by xrestop,Linux,Linux,VirtualBox 6.0.8,2019-07-17T13:44:52Z,2019-07-17T13:44:52Z,"I am seeing ""cursors"" as reported by xrestop constanly increasing, which I believe is leading to a leak in X11 which slowly but surely eats up all memory, forcing me to restart.

This has been happening for at least all of the 6.0 branch of virtualbox, but maybe earlier.

After searching, I found a similar comment suggesting the same thing:

https://www.virtualbox.org/ticket/15892?cversion=0&cnum_hist=14#comment:14

I graphed it out over a day or so, and I could see that it was constantly increasing whenever I was using the VM, but remained stable otherwise (graph attached).  It never went down.

I've attached a small screenshot video (for whatever reason, it seems gnome screenshot didn't actually capture the cursor... but you can see the link highlighting and the cursors value constantly increasing).

I would note it happens only the cursor switch when *not* in capture mode (i.e., turn off mouse integration and you can switch the cursor as much as you like and it never increases on the host).  Maybe for someone skilled in the art that could help pinpoint which library this is related to?

I am currently running 6.0.8 on Fedora 30, but as mentioned it has been happening before that and the original bug was in the 5.1 series.

I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1713162 too

",iwienand
18529,Heavy graphics activity in GUI locks VM,Mac OS X,Windows,VirtualBox 6.0.4,2019-07-17T14:45:53Z,2019-07-17T14:45:53Z,"I'm running Windows7 as a guest with MacOS as host. I've noticed that since some versions back, heavy graphics activity inside the guest causes extremely high CPU usage, bringing the guest to a crawl. The guest becomes unuseable slow and after some seconds the entire VM-Windows locks up and no longer redraws; interestingly this only affects the GUI, the VM itself continues running (I can see it's network-traffic).

""Heavy graphics activity"" in this context seems to be anything that causes lots of redraws. This includes simple GUI-animations, videos, or anything else which causes fast redraws inside the guest. 

Since the VM-logs show nothing of interest, I did acquire a CPU usage profile while a simple program inside the VM hammers it with window-redraws. It seems the redraws cause an event-storm in VirtualBox's Cocoa implementation: While the VM crawls and ultimately locks, the VirtualBox-process spends all of it's CPU-time inside the QEventLoop, specifically CGContextDrawImage.

My semi-educated guess is that the event-loop drowns in redraw requests which take much longer to process on the host than to generate in the guest.

I've attached the profile taken while VirtualBox is locked up.

Disabling 2D-Acceleration fixes the lockup.",ebfe
18765,ICH AC97 don't work on Wondows ME,Windows,Windows,VirtualBox 6.0.10,2019-07-17T16:17:13Z,2019-07-17T16:17:13Z,"When I've updated to VirtualBox 6.0.0, audio in Windows ME became buggy or don't working.",WinWins
17908,Optional entries in the <MediaRegistry> section may prevent VM registration,all,all,VirtualBox 5.2.16,2019-07-18T08:51:31Z,2019-07-18T08:51:31Z,"The <MediaRegistry> section of the .vbox file contains a registry of active and previously used media; HDs and DVDs, a.k.a. the Most Recently Used (MRU). The MRU list is nothing but a convenience for the end user.

'''Problem''': If there's an MRU entry that conflicts with an existing registered medium, the import/registration of a VM fails.

'''Example''': __Registered__ VM1 has an entry in the MediaRegistry section for a ''__previously used__'' DVD:
{{{
<MediaRegistry>
  <DVDImages>
    <Image uuid=""{11111111-1111-1111-1111-111111111111}"" location=""Test.iso""/>
  </DVDImages>
</MediaRegistry>
}}}
A second VM2 has the following in the MediaRegistry section for a ''__previously used__'' DVD:
{{{
<MediaRegistry>
  <DVDImages>
    <Image uuid=""{22222222-2222-2222-2222-222222222222}"" location=""Test.iso""/>
  </DVDImages>
</MediaRegistry>
}}}
The names of the DVDs are the same, the UUIDs are different (it happens more often than you think). Trying to register VM2 results in the following error:
> ''Failed to open virtual machine located in /Users/Shared/Test2.vbox.''
> 
> ''Cannot register the DVD image '/Users/Shared/Test.iso' {22222222-2222-2222-2222-222222222222} because a CD/DVD image '/Users/Shared/Test.iso' with UUID {11111111-1111-1111-1111-111111111111} already exists.''
> 
> ''Result Code: NS_ERROR_INVALID_ARG (0x80070057)''[[br]]
> ''Component: VirtualBoxWrap''[[br]]
> ''Interface: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}''
and the import fails. Not good.

'''Workaround''': The only workaround so far is to ''manually'' edit the .vbox file and remove the __''optional''__ entry for the ""offending"" medium. Remember, this entry is purely optional, the DVD is __not__ actively attached.

'''Solution''': If an entry in the MediaRegistry section is solely used so that it can be displayed in the MRU, ignore that entry upon registration and delete that entry from the MediaRegistry section, as to not cause conflicts.",Socratis
18763,CMPXCHG16B,Windows,Windows,VirtualBox 6.0.10,2019-07-18T11:29:54Z,2019-07-18T11:29:54Z,"Just upgraded from v5.32 to v6 here, but get this error on about half of the VM's I am trying to upgrade.  I didnt see where a user can change this, please help!
Occurs when I try to launch the VM's.
Thank you.

Duplicate config values '/CPUM/CMPXCHG16B' and '/CPUM/IsaExts/CMPXCHG16B' - please remove the former! (VERR_DUPLICATE).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",LindaCarter
18769,headless on server without xserver,other,other,VirtualBox 6.0.10,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
18772,USB flash drive selection / addition causing crash or on removal,Windows,Linux,VirtualBox 6.0.10,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,"Intermittent, but fails enough to be extremely troublesome.",xlar54
18771,vboxdrv.sh does not attempt to build modules on Fedora if Secure Boot is enabled,Linux,other,VirtualBox 6.0.10,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
18773,VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64 doesn't build kernel modules,other,other,VirtualBox 6.0.10,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
18774,Virtual Box is causing random host reboots,Windows,all,VirtualBox 6.0.10,2019-07-20T15:39:34Z,2019-07-20T15:39:34Z,"When I turn on three virtual machines windows 7, windows vista, windows 8.1 pro my computer just reboots after 10 minutes. When I only run Windows 8.1 pro I get a BSOD system service exception error. Also, in vmware that happens. Hyper-V on my computer was disabled and also Virtualization Based Security in Device Guard was disabled. Can anyone help me with this?",obedyaw
18775,New VM wizard fails to delete directory if going back one step in the wizard.,all,all,VirtualBox 6.0.10,2019-07-21T06:15:10Z,2019-07-21T06:15:10Z,"
== Steps to reproduce ==

1. Menu ""Machine"" » ""New..."", ""Guided Mode"".
2. Enter the VM name, e.g. ""Windows 2012"".
3. Press ""Continue"", a directory with the same name is created in the default VM location.
4. __Press ""Back""__, because you realize that you actually wanted to be in ""Expert"" mode.
5. Switch to ""Expert Mode"".
6. Re-enter the VM name ""Windows 2012"", because the two wizards are independent, AFAIK.
7. Press ""Create"".
> ''Cannot create the machine folder '''Windows 2012''' in the parent folder '''/Users/Shared/VirtualBox/Machines'''.''
> 
> ''This folder already exists and possibly belongs to another machine.''

== Steps to reproduce, part deux ==

1. Menu ""Machine"" » ""New..."", ""Guided Mode"".
2. Enter the VM name, e.g. ""Windows 2012"".
3. Press ""Continue"", a directory with the same name is created in the default VM location.
4. __Press ""Back""__, because you realize that you inputted the wrong VM name.
5. Change the VM name to ""Windows 2012 (64)"".
6. You still have a directory named ""Windows 2012"" in the default location.

== Resolution ==
When backing up at step 4, make sure that the newly created empty directory is deleted.



=== Note ===

 I put in 6.0.10 as the version affected, but obviously this goes way, way back...",Socratis
18777,Virtual Box 6 Crashes Windows due to Network device error,other,other,VirtualBox 6.0.10,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
18778,STM32CubeIDE GDB start-up fails in VirtualBox with Ubuntu guests,Linux,Linux,VirtualBox 6.0.6,2019-07-21T19:39:47Z,2019-07-21T19:39:47Z,"
I have tested all supported Ubuntu versions listed in UM2563 when installed as a VirtualBox guest
and STM32CubeIDE is installed in the guest operating system (Ubuntu 14.04, 16.04, 18.04).
Also Linux Mint Mate 19.1 and 19 are tested with similar results as VirtualBox guests.

VirtualBox versions is:

VirtualBox 6.0
VirtualBox Graphical User Interface
Version 6.0.6 r130049 (Qt5.9.5)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

VirtualBoxGuestAdditions VBox_GAs_6.0.6 is installed.
Oracle VM VirtualBox Extension Pack 6.0.8r130620 is installed in Oracle VM VirtualBox Manager.

THE ISSUE IS:
============

Only an unmodified code generated as a STM32Project.
All have the same behaviour where installation and compilation succeed but GDB start-up fails with the message:

Could not determine GDB version using command: /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --version

This is consistent in all Ubuntu versions and same with IDE versions 1.0.1 and 1.0.2.

When running the same command in a terminal session the response is as follows:

xxxxx@ubuntu1604base:~$ /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --versionGNU gdb (GNU Tools for STM32 7-2018-q2-update.20190328-1800) 8.1.0.20180315-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""--host=x86_64-linux-gnu --target=arm-none-eabi"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word"".

When installed without virtualisation (in Linux Mint 19.1 Mate only) everything works as expected (no errors).

",mnu
18624,Vbox 6.0.6 build failure on Linux with gcc 9.1.0,Linux,other,VirtualBox 6.0.6,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
17842,VirtualBox crashes while shutting down guest VM,Mac OS X,all,VirtualBox 5.2.12,2019-07-24T00:11:16Z,2019-07-24T00:11:16Z,VirtualBox 5.2.12 crashes every time while shutting down any guest VM.,QA
18780,VirtualBox-6.0.10-132072-Win  BSOD,Windows,Windows,VirtualBox 6.0.10,2019-07-25T05:16:39Z,2019-07-25T05:16:39Z,"Steps to reproduce:
-create or use an existing Windows7 VM
-download VNC viewer standalone
-run it inside the VM => BSOD

No BSOD with VirtualBox-5.2.30-130521",jcstaquet
18783,Patch VirtualBox 6.0.10 for Linux kernel 5.3.y,Linux,all,VirtualBox 6.0.10,2019-07-25T06:09:10Z,2019-07-25T06:09:10Z,"
Patch VirtualBox 6.0.10 for Linux kernel 5.3.y


{{{
diff -ruN ./virtualbox-6.0.10.orig/r0drv/linux/mp-r0drv-linux.c ./virtualbox-6.0.10/r0drv/linux/mp-r0drv-linux.c
--- ./virtualbox-6.0.10.orig/r0drv/linux/mp-r0drv-linux.c       2019-07-12 11:38:58.000000000 +0300
+++ ./virtualbox-6.0.10/r0drv/linux/mp-r0drv-linux.c    2019-07-22 21:03:06.993331834 +0300
@@ -283,12 +283,7 @@
     if (RTCpuSetCount(&OnlineSet) > 1)
     {
         /* Fire the function on all other CPUs without waiting for completion. */
-# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 27)
-        int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */);
-# else
-        int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* retry */, 0 /* wait */);
-# endif
-        Assert(!rc); NOREF(rc);
+        NOREF(smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */));
     }
 #endif
 
@@ -326,7 +321,6 @@
 {
 #ifdef CONFIG_SMP
     IPRT_LINUX_SAVE_EFL_AC();
-    int rc;
     RTMPARGS Args;
 
     RTTHREADPREEMPTSTATE PreemptState = RTTHREADPREEMPTSTATE_INITIALIZER;
@@ -337,14 +331,11 @@
     Args.cHits = 0;
 
     RTThreadPreemptDisable(&PreemptState);
-# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 27)
-    rc = smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */);
-# else /* older kernels */
-    rc = smp_call_function(rtmpLinuxWrapper, &Args, 0 /* retry */, 1 /* wait */);
-# endif /* older kernels */
+
+    NOREF(smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */));
+
     RTThreadPreemptRestore(&PreemptState);
 
-    Assert(rc == 0); NOREF(rc);
     IPRT_LINUX_RESTORE_EFL_AC();
 #else
     RT_NOREF(pfnWorker, pvUser1, pvUser2);
diff -ruN ./virtualbox-6.0.10.orig/vboxnetflt/linux/VBoxNetFlt-linux.c ./virtualbox-6.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c
--- ./virtualbox-6.0.10.orig/vboxnetflt/linux/VBoxNetFlt-linux.c        2019-07-22 21:05:55.545025085 +0300
+++ ./virtualbox-6.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c     2019-07-22 21:06:08.743978844 +0300
@@ -2107,6 +2107,8 @@
     struct in_device *in_dev;
     struct inet6_dev *in6_dev;
 
+    const struct in_ifaddr *ifa;
+
     if (ulEventType != NETDEV_REGISTER)
         return NOTIFY_OK;
 
@@ -2123,7 +2125,8 @@
 #endif
     if (in_dev != NULL)
     {
-        for_ifa(in_dev) {
+        rcu_read_lock();
+        in_dev_for_each_ifa_rcu(ifa, in_dev) {
             if (VBOX_IPV4_IS_LOOPBACK(ifa->ifa_address))
                 return NOTIFY_OK;
 
@@ -2137,7 +2140,8 @@
 
             pThis->pSwitchPort->pfnNotifyHostAddress(pThis->pSwitchPort,
                 /* :fAdded */ true, kIntNetAddrType_IPv4, &ifa->ifa_address);
-        } endfor_ifa(in_dev);
+        }
+     rcu_read_unlock();
     }
 
     /*


}}}



Best regards, Andy Lavr.
",Andy Lavr
18785,Host Bluetooth Stops Working,other,other,VirtualBox 6.0.10,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
18782,Host machine crashes when booting guest for installation,Windows,all,VirtualBox 6.0.10,2019-07-25T08:29:22Z,2019-07-25T08:29:22Z,"I posted a couple of threads seeking help for my issue, someone suggested I post a bug report.

https://superuser.com/questions/1462614/oracle-virtualbox-host-machine-crashes-when-booting-guest-for-installation

https://forums.virtualbox.org/viewtopic.php?f=6&t=93933&sid=4632274c1fd7c536357bd0c7c7877e99
",diamondpumpkin
18788,Für die virtuelle Maschine WindowsXP konnte keine neue Sitzung eröffnet werden.,Windows,Windows,VirtualBox 6.0.10,2019-07-25T09:10:23Z,2019-07-25T09:10:23Z,"Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",burghard007
18767,VirtualBox 6.0.10 segfaults at startup on CentOS 7.6,Linux,other,VirtualBox 6.0.10,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
18794,"VM stopped scaling correctly ater update to 6.0.10 from 6,0,08",Windows,Linux,VirtualBox 6.0.10,2019-07-26T17:57:20Z,2019-07-26T17:57:20Z,"Hi there 
I updated VMBox vom 6.0.8 to 6.0.10
this went well.- 
Then I started the Guest Cd 6.0.10 , after that the scaling of the desktop in the VM stoppend working. 
the size is set and is not changeable. 
I counter checked via a recent clone of the VM and there the scaling of the screen still works.-  
I am not sure what else I can give. please let me know.
cheers
   Me",Baros
18554,systemd startup script not updated during guest additions install,Windows,Linux,VirtualBox 6.0.4,2019-07-29T12:30:00Z,2019-07-29T12:30:00Z,"Environment:[[BR]]
Host: Windows 10 Enterprise[[BR]]
Guest: Linux Mint 19.1[[BR]]

I upgraded my host Virtualbox install from version 5.2.26 to 6.0.4[[BR]]
 
After booting the Linux Mint guest I was prompted to update the virtualbox guest additions.

This appears to install correctly, however when rebooting the guest, vbox shared folders don't appear to mount.

I eventually traced the issue down to the systemd startup script located in /etc/systemd/system/vboxadd-service.service 

When querying the status of the service startup after updating to guest additions version 6.0.4 this error is shown:

Apr 09 14:06:21 Mint-19 systemd[4423]: vboxadd-service.service: Failed at step EXEC spawning /opt/VBoxGuestAdditions-5.2.26/init/vboxadd-service: No such file or directory


I then manually edited the /etc/systemd/system/vboxadd-service.service service file and changed all entries for the path /opt/VBoxGuestAdditions-5.2.26/ to the path /opt/VBoxGuestAdditions-6.0.4/

I then reloaded systemd and started up the vboxadd-service successfully, with host shared folders mounting on the guest as expected",Chuck Donahue
18746,Live snaphot cloning (VBoxManage clonevm) fails when basefolder is SMB share,Linux,all,VirtualBox 6.0.8,2019-07-29T18:17:19Z,2019-07-29T18:17:19Z,"When the `--basefolder` is specified to point to a Samba share, the clonevm process fails for a previously-created live snapshot.

Interesting note: the issue does NOT occur when the snapshot was taken from a VM that was powered off (not live). Live snapshot clones do succeed, however, when the basefolder is on the local ext4 filesystem.

Host is Ubuntu 16.04 amd64 running kernel 4.15.

{{{
$ VBoxManage snapshot ""{7a81c085-7fd5-49c6-a698-c64eda275119}"" take backup.tmp --live
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: d53e1bfb-2111-4945-ac1a-d1b10206c5f3

$ VBoxManage clonevm ""{7a81c085-7fd5-49c6-a698-c64eda275119}"" --snapshot backup.tmp --options keepallmacs,keepdisknames --basefolder /vmdata/_backups/tmp --name ""iot-manager.bak""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
}}}

/vmdata/_backups is a Samba mountpoint on a Synology box. Relevant info from `mount`:
{{{
//mynas/NAS/VM stuff/backups on /vmdata/_backups type cifs (rw,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=nasuser,domain=,uid=1000,forceuid,gid=0,noforcegid,addr=mynas,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
}}}
",Aleksandr Kotlyar
14053,separate caps-lock state between host & guest,all,all,VirtualBox 4.3.26,2019-07-30T19:56:24Z,2019-07-30T19:56:24Z,"I'd like to suggest that each VM settings page have an additional setting for linking and unlinking the caps-lock state from the host to the guest (might as well include num-lock and scroll-lock states too).

The setting could be: ['''''linked to host'''''] or ['''''unlinked to host''''']. Unlinked would permit completely different states between the host and guest. But the default would be [linked to host].

I'm thinking that having it as an automatic switch (like with mouse cursor capture and release) would be easiest for the user. Each VM would have to keep track of its own caps-lock state. When the user returns to that VM, caps-lock is in the same state as when they left it.

A minor convenience? Yes.

More trouble than it's worth? Quite possibly.

Thanks for reading.

''':)'''",RandomName123
18800,vmR3HaltGlobal1Halt hogs host CPU,all,Windows,VirtualBox 6.0.10,2019-07-31T19:11:19Z,2019-07-31T19:11:19Z,"Running a single CPU VM Windows 10 1803/1809/1903 64 bit or 32 bit (default VirtualBox VM settings for Windows 10 32 or 64 bit guest), the VM host process hogs the CPU, while the guest idles.
If I start a 2nd VM (no OS, no boot medium, single CPU), it's enough to lower the CPU usage of the Windows 10 VM. On Windows, the CPU usage is lower if I start the VM while the PC is playing a video

To reproduce, just start the Windows 10 VM (no other VMs running or suspended), booting the Windows 10 1803/1809/1903 installation ISO, until it has completely loaded the setup and you are shown the first window. To check the CPU load in the guest, press Shift+F10 and type in Command Prompt: wmic cpu get loadpercentage[[br]]
Booting Windows 10 1709 installation ISO is a very different experience. The host CPU is idling while the guest is idling[[br]]

I am able to build VirtualBox OSE on Windows and I have observed that it spends a most of time in vmR3HaltGlobal1Halt. I can also record an ETL log with the official VirtualBox release build, if needed.[[br]]
I can reproduce this issue on Windows 10 1803/1903 64 bit host OS and Debian 64 bit host OS.
I first mentioned about this issue on #12851[[br]]
There's also a forum thread, where some of the users reported similar issues [[https://forums.virtualbox.org/viewtopic.php?f=6&t=87991|link]][[br]]
",Mihai Hanor
18381,Certain sounds seem to crash OS/2 guest,Windows,other,VirtualBox 6.0.4,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
18770,can't use VirtualBox under debian-live-10.0.0-amd64-kde,Linux,all,VirtualBox 6.0.10,2019-08-01T17:26:01Z,2019-08-01T17:26:01Z,"hello,
i just made a fresh installation of [https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ debian-live-10.0.0-amd64-kde.iso] to my harddisk and i tried to install virtualbox.

i followed the instruction on [https://www.virtualbox.org/wiki/Linux_Downloads Debian-based Linux distributions]


{{{
:~$ echo ""deb https://download.virtualbox.org/virtualbox/debian buster contrib"" | sudo tee -a /etc/apt/sources.list.d/virtualbox.list
:~$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -

:~$ sudo apt update -y
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 https://download.virtualbox.org/virtualbox/debian buster InRelease                          
Hit:3 http://deb.debian.org/debian buster InRelease                
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.


:~$ apt search virtualbox
...
virtualbox-5.2/unknown 5.2.32-132073~Ubuntu~bionic amd64
  Oracle VM VirtualBox

virtualbox-6.0/unknown 6.0.10-132072~Ubuntu~bionic amd64
  Oracle VM VirtualBox
...


:~$ sudo apt install virtualbox-6.0
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libcurl4 libsdl-ttf2.0-0 linux-headers-amd64
Recommended packages:
  linux-image
The following NEW packages will be installed:
  libcurl4 libsdl-ttf2.0-0 linux-headers-amd64 virtualbox-6.0
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 103 MB of archives.
After this operation, 228 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian buster/main amd64 libcurl4 amd64 7.64.0-4 [332 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 libsdl-ttf2.0-0 amd64 2.0.11-6 [18,6 kB]
Get:3 http://deb.debian.org/debian buster/main amd64 linux-headers-amd64 amd64 4.19+105 [6.652 B]
Get:4 https://download.virtualbox.org/virtualbox/debian buster/contrib amd64 virtualbox-6.0 amd64 6.0.10-132072~Ubuntu~bionic [102 MB]                                                                                                                                        
Fetched 103 MB in 30s (3.424 kB/s)                                                                                                                                                                                                                                            
...

}}}

i was wondering that during installation the virtualbox packet it was shown ""6.0.10-132072~Ubuntu~bionic"", but i am on an debian environment at that moment

ok, so far so good... virtualbox starts as normal as i expected.[[BR]]

but when i create a new virtual machine and start it, i get an error message.

{{{
Failed to open a session for the virtual machine Test.

The virtual machine 'Test' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

}}}

the same error message i get, when i add an existing virtual machine i created and used earlier under Ubuntu19.04.


the current installed version under Debian Buster (KDE) shows:
Version 6.0.10 r132072 (Qt5.11.3)
",beta_tester
18804,VirtualBox Manager terminating without notice after start,Windows,Linux,VirtualBox 6.0.10,2019-08-02T08:58:57Z,2019-08-02T08:58:57Z,"When I start the VirtualBox Manager, it briefly shows the selector window, then terminates without any notice. I have a single Linux VM in the list.",sgiesecke
18806,Wrong GUI scaling on very large screen resolution ultrawidescreen triple monitors,Linux,all,VirtualBox 6.0.10,2019-08-02T23:41:59Z,2019-08-02T23:41:59Z,"Hello,

I have a 3x1280x1024 screen.
I upgraded from 5.2.30 to 6.0.10 and now some part of the GUI are too large.

Prior to the upgrade, I could resize the main virtualbox window to 1280x1024 so that it fits one of my triple-monitors.
With 6.0.10, the main window can't be reduced horizontally to less than approximately 1600x1024. I think this is because the GUI elements are already collapsed to the non-overlapping minimum but they are still too large.

The guest window is too big too.
I used to set the guest screen to 1152x864 and I had space left around it.
Now with 6.0.10, the UI elements around the window are so big that it the same 1152x864 guest window is too tall for the screen and it even has to add (large) scrollbars to it.

The issue is prominent in the menus.
Also, the larger the monitor resolution, the more pixelated the guest preview.

If I set my screen resolution to a lower single monitor resolution (1280x1024) the issue is not present.
The issue is proportional to the wideness of the screen.
See the attached screenshots for comparison between different resolutions.

Host is Debian 8 Jessie 64bit.
Guest is irrelevant.

Regards.",www.olivierdierick.be
18808,VirtualBox 6.0.10 Segmentation fault in openSUSE 13.2,Linux,other,VirtualBox 6.0.10,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
15268,Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10,Windows,Windows,VirtualBox 5.0.16,2019-08-04T09:26:22Z,2019-08-04T09:26:22Z,"==== How to Reproduce ====

While trying to restart a VM with a saved state computer turns off and a blue screen shows the 
SYSTEM_SERVICE_EXCEPTION message then it restarts.

==== System Information ====

I am running:
VirtualBox VM 5.0.17 r106155 win.amd64 
Windows 10
DMI Product Name: Dell Precision M3800
Host RAM: 16286MB total, 12942MB available
Package type: WINDOWS_64BITS_GENERIC

==== Enabled Plugins ====
No plugins installed
",Nayz
18809,Version 6.0 - Scale,other,Windows,VirtualBox 6.0.10,2019-08-04T14:57:59Z,2019-08-04T14:57:59Z,"The view mode is all messed up.  No matter what I change to, all of the icons either grow or shrink into a water mess when moving the mouse cursor.  The windows taskbar is no where to be seen.  No changes have been done to my VMs other than installing the new 6.0 version.

Guest system is a Windows machine
Host is the latest MAC OS.

",Mordy
18812,Ubuntu virtual machine fails to start,Linux,Linux,VirtualBox 6.0.10,2019-08-05T05:11:06Z,2019-08-05T05:11:06Z,,bobocc
18810,Linux Host: High CPU usage with idle Windows 10 guest,Linux,Windows,VirtualBox 6.0.6,2019-08-05T06:46:47Z,2019-08-05T06:46:47Z,"When Windows 10 is in idle mode, there still high CPU usage in host.
Host is Kubuntu 18.04.

---
{{{
rfried@rfried-mobl1 ~/dev/vim-bitwise master $ top
top - 16:34:02 up 6 days, 55 min,  8 users,  load average: 1.49, 1.84, 1.89
Tasks: 357 total,   1 running, 356 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.0 us,  7.1 sy,  0.0 ni, 90.5 id,  0.0 wa,  0.0 hi,  0.4 si,  0.0 st
MiB Mem :  32001.6 total,   1579.0 free,  13931.3 used,  16491.3 buff/cache
MiB Swap:   2048.0 total,   2036.5 free,     11.5 used.  17438.4 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                                                 
27416 rfried    20   0   11.1g   8.5g   8.3g S 138.1  27.2 681:52.72 VirtualBoxVM  
}}}",rfried
18817,Mini toolbar display corruption,Linux,Windows,VirtualBox 6.0.10,2019-08-07T07:49:07Z,2019-08-07T07:49:07Z,"Using a Dell XPS13 (2018) with a second full HD monitor (1920x1080) the mini toolbar display becomes corrupted (see attached image).
The menu items do not line up with the display although they all work by a trial-and-error method.
",Smot
10275,Horizontal tilting (in certain Guests) behaves like Vertical Scrolling,other,other,,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
18212,Windows 10 Host - Hardening error - VMs do not start,Windows,Linux,VirtualBox 6.0.0,2019-08-07T13:56:10Z,2019-08-07T13:56:10Z,"Windows 10 Host - Hardening error - VMs do not start

Steps (on latest Windows Release build - Windows 10 x64 Version 1809 Build 17763.195):

- Install and use !VirtualBox v6.0.0
- Start with a Linux VM that has a restored snapshot from v5.2.23 (mine was from !VirtualBox v5.2.23 Test Build 127495)
- Start the VM - it starts successfully
- Take an online snapshot
- While the VM is running, delete the old v5.2.23 snapshot
- Power off the VM
- Restore the online snapshot
- Attempt to Start the VM
- BUG: Progress gets to 97% and hangs. It does not start. Later, a secondary progress dialog appears on the VM Manager window, and also hangs.
- NOTE: The following lines in VBoxHardening.log may indicate a problem with ""wintab32.dll"":
{{{
2658.2dec: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\WINDOWS\system32\wintab32.dll': 0 (NtPath=\??\C:\WINDOWS\system32\wintab32.dll; Input=C:\WINDOWS\system32\wintab32.dll; rcNtGetDll=0x0
2658.2dec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000034 'C:\WINDOWS\system32\wintab32.dll'
}}}
Attached are:
- .vbox files (multiple versions), showing the progression of the steps
- .log files (VBox.log, VBoxHardening.log)
- Image showing failure

This worked properly using !VirtualBox v5.2.23 Test Build 127495.

Let me know if you require the actual VM itself.",Jacob Klein
18819,3D Acceleration not working in 6.0,Windows,Windows,VirtualBox 6.0.10,2019-08-08T01:05:53Z,2019-08-08T01:05:53Z,"Reference forum post:
https://forums.virtualbox.org/viewtopic.php?f=2&t=94052

Seems there are at least three people voicing this complaint.

I was using VB 5.2.22 on Win7 host with Win10 guests for a long time. I set the guests to use 3D and 2D acceleration and never noticed an issue.

I rebuilt my host to Win10 v1709, same hardware including the NVIDIA Quadro GPU. I installed VB 6.0.10, created new VMs, and then quickly ran into the shared folder crash, so backed down to 6.0.8.

When I set the Win10 guest to use 2D and 3D (256MB), I have graphics issues. The most notable is that videos won't play in WMP or VLC (audio only, no image shown). There is also a lot of flickering and choppiness in the OS UI. If I toggle off 3D, then videos will play and other OS UI animations are smooth again.
",Justinh
18821,VirtualBox (VirtualVM.exe) crashes on Xubuntu 18.04 guest shutdown,Windows,Linux,VirtualBox 6.0.10,2019-08-08T11:18:44Z,2019-08-08T11:18:44Z,"More often than not, my Xubuntu 18.04 guest OS does not shutdown cleanly. The host OS is running the latest version of Windows 10. A crash is raised in VirtualVM.exe. An example screenshot of the 'Application Error' is attached.

Attached are the following files:
* VBox Manager log
* Link (not actual attachment) to compressed, '''full''' crash dump (generated via Task Manager) - [https://drive.google.com/file/d/1CiOAs_8KejRZzMYjGd3UtA71kUOobv5a/view?usp=sharing Google Drive].
* Screenshot of application error raised by Windows. For the record, this screenshot does not (unfortunately) correspond to the attached crashdump.

I initially suspected the issue was related to Graphics acceleration, but I have disabled both 2d/3d but it has not changed the resulting behaviour.",zerodefect
18822,VMs with name lengths greater than 64 characters abort on start when using Pulseaudio. Have root cause and fix option <Regression>,Linux,all,VirtualBox 5.2.26,2019-08-08T15:35:59Z,2019-08-08T15:35:59Z,"If a VM has a name length greater than 64 characters, and is using Pulseaudio, it will abort on startup with ""VERR_CFGM_NOT_ENOUGH_SPACE"" being thrown.

The root cause is:
Inside ""src/VBox/Devices/Audio/DrvHostPulseAudio.cpp"", in ""struct DRVHOSTPULSEAUDIO"", there is ""char                  szStreamName[64];"".

This ""szStreamName"" only appears to be used by Pulseaudio for display purposes, such as when running ""pavucontrol"". The comments above ""szStreamName"" read:
     * The stream (base) name; needed for distinguishing
     *  streams in the PulseAudio mixer controls if multiple
     *  VMs are running at the same time. */

So, when ""int rc2 = CFGMR3QueryString(pCfg, ""StreamName"", pThis->szStreamName, sizeof(pThis->szStreamName));"" is called inside of the ""drvHostPulseAudioConstruct"" function in that file, ""CFGMR3QueryString"" throws the above error, as String.cb is greater than 64 characters.

I have a local patch which is a hacky solution and not good enough for you guys -- it checks if ""StreamName"" is passed in in each call to ""CFGMR3QueryString"", and then does the following if it is too long -- but I got it to work just fine by ellpisizing (""..."") at the middle of the string like so, creating a 64 character string like Pulseaudio requires, which shows up correctly in ""pavcontrol"":
     * First 30 chracters of the VM name
     * 3 chracters for ""...""
     * Last 30 chracters of the VM name
     * 1 byte for '\0'
This is 64 characters total. In my patch, I simply change the contents of String.psz and String.cb, which is probably not the correct way to do it.

I would strongly suggest ellipsizing in the middle like this, since the first 64 characters of multiple VM clones could easily be the same, usually the last few characters/words are what is different when there are many clones/different versions of a VM running.
Another option could be the number them, but ellipsizing is probably better for the user.

This limitation did not exist when using Ubuntu 18.04/16.04, so I have marked it as a regression. I looked at the latest 6.0 source code, and it looks like this bug will still be present there.

I have many VMs with long and descriptive names past 64 characters, and I know others do too, that is a very useful feature to tell them apart at a glance (especially when using many clones, where checking each description is not realistic).
Please fix this for us users who let our VM names get out of control! It really helps workflow to be able to use such long names.

Reproducible: Always",J_F
18592,OpenGL has performance and drawing issues after 6.0.6 update.,Windows,Windows,VirtualBox 6.0.6,2019-08-12T05:35:00Z,2019-08-12T05:35:00Z,"After update to the aforementioned version my Windows 10 1809 host and guest got some problems. First of all the startup time is now double or triple as much as before. One can see the system starting as one would moved back from SSD to plain old HDD. Even if one see something there is a slow reaction on the keyboard and mouse events. So it takes more time from the start of the VM till the moment where you can do something with it.

The other one: as soon as host try to dime the display or turn it off, the content of the VM turns black. The programs work fine and you can hear the sound, but you can’t see anything, just black square. The mouse cursor changes itself in case you move it over some places (like border of the program’s window or the link in the browser). I could blindly shutdown the VM through keyboard commands directly in VM. There are some topics ([https://forums.virtualbox.org/viewtopic.php?f=6&t=92756 92756],[https://forums.virtualbox.org/viewtopic.php?f=2&t=92757 92757]) in the forum describing the same behavior. Some other tickets (#18564, #18582) are probably depends on this issue.

I tested with 5.2.28, current 5.2.29 and 6.0.7 with the same result. Going back to the 6.0.4, 5.2.26 or 5.2.22 solves this. I saw some changes in the OpenGL using code in the last to weeks, maybe this causing this behavior? I put my logs here, I could see some OpenGL warnings and errors here just 12 minutes after the VM start.

Funny enough this not happens on my older Windows 7 guest — Windows 8.1 host system. The Windows 10 systems are all Core i5 3xxx with build-in graphics, also not the youngest ones, but not as old as Windows 8.1 system.",boxer01
18830,Problem with Version 6.0.10 Guest Additions,Windows,Windows,VirtualBox 6.0.10,2019-08-12T07:29:36Z,2019-08-12T07:29:36Z,"I'm running VirtualBox 5.2.32 with a Windows XP virtual machine. Everything works fine. However, when I installed 6.0.10, it reports ""Disk is full"" when a program tries to write to a file on a FAT16 (yes, FAT16) shared partition. This only happens if I install the 6.0.10 guest additions. If I stay with the 5.2.32 guest additions, it doesn't occur. (I don't know if it would occur with a FAT32 or NTFS partition, because the program only works with FAT16, which is why I have a FAT16 partition).",cdgoldin
18811,6.0.10 snaphot fails on NFS share with savestate,Linux,all,VirtualBox 6.0.10,2019-08-14T03:50:42Z,2019-08-14T03:50:42Z,"This all works with 5.2.X. A fresh install of 6.0.10 yields the following bug:

With a VM located on an NFS share, if that VM is put into ""savestate"", and we try to clone that VM, the clone fails with the following error:
{{{
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
}}}

If the VM was shutdown using poweroff or acpipowerbutton, the clone works as expected.
[[BR]]
Note: If the VM is located on a local ext4 filesystem, cloning of a savestate VM works as expected. The issue only happens if the VM is on an NFS share AND the vm was put into ""savestate"".

Some traces below:
VMinfo:
{{{
[vbox@scvm001 ]$ vm showvminfo dtest
Name:                        dtest
Groups:                      /
Guest OS:                    Ubuntu (64-bit)
UUID:                        7ff40ac1-6ebb-4d3f-9726-148f9f700e41
Config file:                 /home/vbox/vms/dtest/dtest.vbox
Snapshot folder:             /home/vbox/vms/dtest/Snapshots
Log folder:                  /home/vbox/vms/dtest/Logs
Hardware UUID:               7ff40ac1-6ebb-4d3f-9726-148f9f700e41
Memory size                  2048MB
Page Fusion:                 disabled
VRAM size:                   16MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              2
PAE:                         disabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      enabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               DVD
Boot Device 2:               HardDisk
Boot Device 3:               Not Assigned
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         UTC
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 disabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   KVM
State:                       powered off (since 2019-07-25T18:24:07.000000000)
Monitor count:               1
3D Acceleration:             disabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:          
Teleporter Password:         
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:       
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:            
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      1
Storage Controller Bootable (0):        on
Storage Controller Name (1):            IDE
Storage Controller Type (1):            PIIX4
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  2
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
SATA (0, 0): /home/vbox/vms/dtest/dtest.vmdk (UUID: 2ec6b9b3-1ea9-44e8-b2b2-d752ef938034)
IDE (1, 0): Empty
NIC 1:                       MAC: 080027BDA9CB, Attachment: Bridged Interface 'enp65s0', Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             PS/2 Mouse
Keyboard Device:             PS/2 Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       disabled
Audio playback:              disabled
Audio capture:               disabled
Clipboard Mode:              disabled
Drag and drop Mode:          disabled
VRDE:                        enabled (Address 0.0.0.0, Ports 3400, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
Video redirection:           disabled
VRDE property               : TCP/Ports  = ""3400""
VRDE property               : TCP/Address = <not set>
VRDE property               : VideoChannel/Enabled = <not set>
VRDE property               : VideoChannel/Quality = <not set>
VRDE property               : VideoChannel/DownscaleProtection = <not set>
VRDE property               : Client/DisableDisplay = <not set>
VRDE property               : Client/DisableInput = <not set>
VRDE property               : Client/DisableAudio = <not set>
VRDE property               : Client/DisableUSB = <not set>
VRDE property               : Client/DisableClipboard = <not set>
VRDE property               : Client/DisableUpstreamAudio = <not set>
VRDE property               : Client/DisableRDPDR = <not set>
VRDE property               : H3DRedirect/Enabled = <not set>
VRDE property               : Security/Method = <not set>
VRDE property               : Security/ServerCertificate = <not set>
VRDE property               : Security/ServerPrivateKey = <not set>
VRDE property               : Security/CACertificate = <not set>
VRDE property               : Audio/RateCorrectionMode = <not set>
VRDE property               : Audio/LogPath = <not set>
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                /home/vbox/vms/dtest/dtest.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             

Description:
dtest
Guest:

Configured memory balloon size: 0MB
}}}

Show where the disk is located
{{{
[vbox@scvm001 ]$ vm showvminfo dtest | grep SATA
Storage Controller Name (0):            SATA
SATA (0, 0): /home/vbox/vms/dtest/dtest.vmdk (UUID: 2ec6b9b3-1ea9-44e8-b2b2-d752ef938034)
}}}

Show the disk mount point
{{{
[vbox@scvm001 ]$ df -k /home/vbox/vms/dtest/dtest.vmdk
Filesystem      1K-blocks       Used  Available Use% Mounted on
scqn001:/vbox  3787705600 1550129152 2237035776  41% /mnt/scqn001
}}}

Show the mount type and mount options. This is an NFS mount.
{{{
[vbox@scvm001 ]$ grep /mnt/scqn001 /etc/mtab
scqn001:/vbox /mnt/scqn001 nfs4 rw,relatime,vers=4.2,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.10.31,local_lock=none,addr=192.168.10.29 0 0
}}}

Start the VM
{{{
[vbox@scvm001 ]$ vm startvm --type headless dtest
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone working if VM is set to ""poweroff""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest poweroff
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114608-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""dtest-20190803-114608-vboxbu""
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone working if VM is set to ""acpipowerbutton""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest acpipowerbutton
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114015-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""dtest-20190803-114015-vboxbu""
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Show clone failing is VM is set to ""savestate""
{{{
[vbox@scvm001 ]$ vboxmanage controlvm dtest savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[vbox@scvm001 ]$ vboxmanage clonevm dtest --mode all --basefolder /mnt/lv001-r0/backup/vms --name dtest-20190803-114359-vboxbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 609 of file VBoxManageMisc.cpp
[vbox@scvm001 ]$ vboxmanage startvm dtest --type headless
Waiting for VM ""dtest"" to power on...
VM ""dtest"" has been successfully started.
}}}

Removing 6.0.10 and installing 5.2.X, everything works as expected.


",guideloom
17168,VB display frame and content are no longer bound in High Sierra (osx 10.13),Mac OS X,all,VirtualBox 5.1.28,2019-08-14T06:43:34Z,2019-08-14T06:43:34Z,"OSX High Sierrra 10.13
Windows 8.1 Guest (and others)

After upgrading to High Sierra, the display frame and display content are no longer bound together. When I drag using the title bar, only the frame moves exposing a black window behind the guest's content which has remained in place.

It is possible to re-sync the two either by minimizing/restoring the window, or the Display icon -> ""Adjust Window Size"" option.",James Moe
18795,Hotmail messages not loaded,other,other,VirtualBox 6.0.10,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
15269,shift + scroll wheel inoperative,Mac OS X,Linux,VirtualBox 5.0.16,2019-08-16T05:48:22Z,2019-08-16T05:48:22Z,"Mouse scroll wheel events do not get passed to the guest if Shift key is being held down. This only seems to happen when the host OS is OS X; same VM works as expected if hosted on a Linux host instead. Very inconvenient, as some applications use Shift-scroll to perform specific actions, e.g. horizontal scrolling of a window.

Misbehavior has been noted in multiple applications which use Shift-scroll to perform UI actions. Lack of mouse scroll events when Shift is held has also been verified via the xev tool.

Host is OS X 10.11.3 (El Capitan), guest is Debian 8 (Jessie) running KDE, with up-to-date patches and Guest Additions installed.",MikeUatCS
18798,Virtual machine windows 10 auto restart  when click on one folder in shared disk (internal disk host or USB),Linux,Windows,VirtualBox 6.0.10,2019-08-16T06:59:35Z,2019-08-16T06:59:35Z,"* I'm working with a zip compressed file at a shared disk (on host is a USB DIsk 4 TB)
* Try expand, and crash
* Try another, and crash.
* Move to other shared folder (in host is a internal disk 3TB)
* Uncompressed well.
* After click on folder Setup, crash other time.
",Abdelkarim Mateos Sánchez
18843,VirtualBox crashes with Skype and Windows 10 guest,Linux,Windows,VirtualBox 6.0.10,2019-08-16T08:27:29Z,2019-08-16T08:27:29Z,"Ubuntu 18.04 Host

VirtualBox Version 6.0.10 r132072 (Qt5.9.5).

Sound works fine. Can watch Youtube and use ""Sound Recorder"".

Joining a conference call with Skype also works, everyone can hear each other.

Tried to set ICH AC97 driver (uninstall multimedia driver in Device Manager, reinstall guest additions, reboot) but could not get Windows 10 to recognize it.

VirtualBox window invariably disappears after anything from a few seconds up to around 5 minutes.

The issue is easy to reproduce.

The issue was taken up on forum before filing this ticket:

https://forums.virtualbox.org/viewtopic.php?f=7&t=94305

Attached same log here.  It was edited for privacy.",hapless_user
18845,Feature Request: Automatically enable virtualization,other,all,VirtualBox 6.0.10,2019-08-16T15:28:36Z,2019-08-16T15:28:36Z,"Some of us users either do not have the necessary virtualization components for Virtualbox running on our computers, or do not know how to enable them.
Why not have Virtualbox check during install and attempt to enable VT-X or AMD-v as needed from the GUI?

Some manufacturers take advantage of a software way to enable hardware virtualization anyway:
https://stackoverflow.com/questions/31581854/enabling-intel-virtualization-vt-x-without-option-in-bios
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager",JEB
18813,Linux installation fails when machine folder points to non-OS directory | Win 8.1 x64,Windows,Linux,VirtualBox 6.0.10,2019-08-17T02:55:43Z,2019-08-17T02:55:43Z,"Tried to install Ubuntu 16 x VM by selecting ""Machine Folder"" to a non-os directory. Installation always fails at Use entire disk and setup LVM.

ENV:
- Windows 8.1 x64 8GB RAM/500 GB HDD
- VM Conf: Memory: 1024 MB, create vhd now, VDI [dynamic alloc][10 GB]",cheruvattil
18787,Blue screen when try to launch WinSCP-5.15.3.,Windows,Windows,VirtualBox 6.0.10,2019-08-17T04:52:53Z,2019-08-17T04:52:53Z,"Guest machine Windows 7 - Win 6.1 (Build 7601 SP 1)

Host machine Windows 10 Ver 1809 (OS Build 17763.615)

Virtual Box - VirtualBox Graphical User Interface, Version 6.0.10 r132072 (Qt5.6.2)

Guest machine fall with Blue screen when try to launch WinSCP-5.15.3. (WinSCP.exe)

Downloaded from here 
https://winscp.net/download/WinSCP-5.15.3-Portable.zip",dimabol
18826,Starting VirtualBox on Windows 10 gives error,other,other,VirtualBox 6.0.10,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
18833,Virtualbox doesn´t work with new Windows update,Windows,Windows,VirtualBox 6.0.10,2019-08-17T06:26:54Z,2019-08-17T06:26:54Z,"I have updated my OS to the latest Windows 10 version, after that I can´t run open any virtual OS.

The virtual machine 'Pintura WinCC 7.3' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Usuario\VirtualBox VMs\Pintura WinCC 7.3\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976} ",erjefe
18704,Windows-KB890830-x64-V5.73 (current Windows malicious software removal tool) in the shared folder causes crush  of the guest OS,Windows,Windows,VirtualBox 6.0.8,2019-08-17T06:43:06Z,2019-08-17T06:43:06Z,"As I wrote, during the today’s Windows updates I downloaded the current version of t x64 MSRT and put it in the shared folder. As soon as I access the shared folder afterwards, the shared folder is shown empty. Shortly after that, the display (not the window) of the guest resizes to something very small like 640 × 480; couple of seconds later the BSOD happens and guest would be restarted.

I put my logs, directory listing of the shared folders and BSOD numbers in the archive. If something else is needed, just let me know. The logs clearly shows the detection of the critical condition. As soon as this file is removed from the shard folders, everything works as it should. This is Windows 10 1809 x64 guest and host combination.",boxer01
18846,'VBoxManage showvminfo' while VM Settings is open causes VirtualBox to think the VM is running,all,all,VirtualBox 6.0.10,2019-08-17T08:06:06Z,2019-08-17T08:06:06Z,"'''Steps to recreate'''
* Create a new VM, or use an existing one.
* Open the VM Settings for the VM.
* On a Terminal run the command ""`VBoxManage showvminfo <VM>`"".
* !VirtualBox warning complains that the VM is running:\\
 > ''The virtual machine that you are changing has been started. Only certain settings can be changed while a machine is running. All other changes will be lost if you close this window now.''",Socratis
18840,Guest VM with Windows 10 64 bit Pro 1903 is resetting with no reason,Windows,Windows,VirtualBox 6.0.10,2019-08-17T08:29:31Z,2019-08-17T08:29:31Z,,fduenas
18847,win10 guest on opensuse 15.1 host crashes on saving session,Linux,Windows,VirtualBox 6.0.10,2019-08-17T09:19:18Z,2019-08-17T09:19:18Z,"When trying to save a session with a win10 guest vbox 6.0.10 crashes with segmentation fault after about 75% of the progress bar.
After rollback to vbox 6.0.8 everything works nicely.

With other guests (winxp, win7, opensuse) this problem did not occur. It is specific to this one w10 vmachine.
vbox does not provide a proper post mortem report when it crashes and says so.",andreas366
18828,VirtualBox client crash when opening VBox shared folder,Windows,Windows,VirtualBox 6.0.10,2019-08-17T09:28:11Z,2019-08-17T09:28:11Z,"Server-OS: Win-10
VirtualBox 6.0
Client-OS: WIN-7

WHen double-click/open a VBOX shared folder in the client, the client chrashes.
",LarsHes
18837,VB Manager crash silently when maximizing window (Fixed in SVN),Windows,other,VirtualBox 6.0.10,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
18839,Guest VMs will only start headless,Windows,Linux,VirtualBox 6.0.10,2019-08-18T21:17:40Z,2019-08-18T21:17:40Z,"After upgrading from VirtualBox5 to VirtualBox6 none of my existing VMs will start unless I choose the ""Headless Start"" option from the dropdown menu.

Once a VM is running I'm able to bring up the GUI by clicking on the ""Show"" button.",nthexwn
18848,Virtual box crashes MacOS Mojave,Mac OS X,Linux,VirtualBox 6.0.10,2019-08-19T07:01:38Z,2019-08-19T07:01:38Z,"MacOS crash when I start a vm on Virtual Box.

Mac 
  cpu is 2.4 GHz Intel Core i9.
  DDR4
  macOs Mojave  10.14.5

vm Guset OS
  CentOS-7-x86_64-DVD-1810
  installed as  DataServer

",iwweyl
18849,Provide default screenshot directory setting,all,all,VirtualBox 6.0.10,2019-08-19T08:33:56Z,2019-08-19T08:33:56Z,"Hello,

I set the screenshot folder as ""/home/olivier/VirtualBox VMs/WindowsXP/Snapshots"". This setting was made with the menu ""Machine > Settings > General > Advanced > Snapshot folder"".

However, VirtualBox does not take this setting into account. When I hit ""Host+E"", the save dialog insists on proposing ""/home/olivier/VirtualBox VMs/WindowsXP"". I must then change the proposed folder to the folder I really want.

Could you please take the folder choice into account correctly?

Also, and this point is a wish, I would like a shortcut for ""immediate screenshot with no dialog box"" (but into the right directory!).

Olivier (VirtualBox 5.2.22-dfsg-2 on Debian Linux)",OCLC
18796,Virtualbox 6.0.10 Lockup Issue,Windows,Windows,VirtualBox 6.0.10,2019-08-19T12:18:49Z,2019-08-19T12:18:49Z,"I am creating this ticket because my companies Windows 7 64/32 bit virtual machines are randomly locking up.  This issue has been present since 6.0 was first released.  I have not been able to figure out how to recreate the issue so I have attached a 7-zip file that include the virtual machine html file along with the log files from a session that locked up and had to be aborted.

Please let me know if you need anything else from me to resolve this ticket.

Thank you
Chris

",cmccarron
18854,BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver,other,Linux,VirtualBox 6.0.10,2019-08-19T16:22:46Z,2019-08-19T16:22:46Z,"I am using VirtualBox on Windows 10 x64 host.
BSOD of Windows host occured when I using CentOS 7 x64 Linux without GUI (just console mode) installation and trying to install ISPmanager Business https://www.ispsystem.com/software/ispmanager/download to avaluate it:
wget ""http://cdn.ispsystem.com/install.sh""
sh install.sh
, activating the demo version of ISPmanager Business and trying to update packages of it.
The probability of BSOD is approx. 80% in update packages state.
BSOD is in Windows network card driver in ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ndis!ndisCallSendCompleteHandler+0x33
ndis!NdisMSendNetBufferListsComplete+0x1df
e1d65x64+0x133b4
(see Windbg outputs)
Guest network is in bridge mode.
In addition, RusRoute firewall free version http://rusroute.com/ is installed on host system, independed in disabled or enabled state of it (Standard Windows firewall is disalbed in both cases).
Can you tell me what software is the reason os BSOD? Is this the bug in VistualBox or in other third party software, like RusRoute firewall?
The Windows 7, XP guests with the same environment is working fine.
WinDbg of minidump1, minidump2 are attached.

{{{

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-10984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols;cache*c:\MySymbols;srv*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`18200000 PsLoadedModuleList = 0xfffff804`186432f0
Debug session time: Fri Aug  2 20:15:42.372 2019 (UTC + 3:00)
System Uptime: 0 days 0:49:12.083
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff9d8db279f1a0, Virtual address for the attempted execute.
Arg2: 8a000008092008e3, PTE contents.
Arg3: fffff8041db504a0, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys

KEY_VALUES_STRING: 1

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.239 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffff9d8db279f1a0

BUGCHECK_P2: 8a000008092008e3

BUGCHECK_P3: fffff8041db504a0

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:05:14.0379

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

DPC_STACK_BASE:  FFFFF8041DB50FB0

TRAP_FRAME:  fffff8041db504a0 -- (.trap 0xfffff8041db504a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9d8db279f1a0 rbx=0000000000000000 rcx=ffff9d8db2ad9950
rdx=ffff9d8db9a923d0 rsi=0000000000000000 rdi=0000000000000000
rip=ffff9d8db279f1a0 rsp=fffff8041db50638 rbp=fffff8041db506b9
 r8=0000000000000001  r9=0000000000000000 r10=fffff80424425b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff9d8d`b279f1a0 1101            adc     dword ptr [rcx],eax ds:ffff9d8d`b2ad9950=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff804184554bc to fffff804183bc900

STACK_TEXT:  
fffff804`1db50278 fffff804`184554bc : 00000000`000000fc ffff9d8d`b279f1a0 8a000008`092008e3 fffff804`1db504a0 : nt!KeBugCheckEx
fffff804`1db50280 fffff804`1844fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 fffff804`1db503c0 : nt!MiCheckSystemNxFault+0x125330
fffff804`1db502c0 fffff804`1827ac2a : 00000000`00000003 00000000`00000011 fffff804`1db50400 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
fffff804`1db50300 fffff804`183ca920 : ffff9d8d`b279f1a0 ffff9d8d`bb66a950 00000000`00000001 00000000`00000001 : nt!MmAccessFault+0x48a
fffff804`1db504a0 ffff9d8d`b279f1a0 : fffff804`1d18aa51 ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 : nt!KiPageFault+0x360
fffff804`1db50638 fffff804`1d18aa51 : ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 ffff9d8d`b9a923d0 : 0xffff9d8d`b279f1a0
fffff804`1db50640 fffff804`1d18eba3 : 00000000`00000002 00000000`00000000 fffff804`00000001 fffff804`244c2101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
fffff804`1db50720 fffff804`1d18bcdf : 00001e00`00001e01 ffff9d8d`b26073c1 ffff9d8d`b2adbb60 ffff9d8d`b9a923d0 : ndis!ndisCallSendCompleteHandler+0x33
fffff804`1db50760 fffff804`271033b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff804`27100d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
fffff804`1db50850 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 : e1d65x64+0x133b4
fffff804`1db50858 00000001`00000000 : 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 : 0x2
fffff804`1db50860 00000001`00000000 : fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 : 0x00000001`00000000
fffff804`1db50868 fffff804`27100d00 : ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 : 0x00000001`00000000
fffff804`1db50870 ffff9d8d`b2be0c60 : ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 : e1d65x64+0x10d00
fffff804`1db50878 ffff9d8d`b29c9d50 : ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 : 0xffff9d8d`b2be0c60
fffff804`1db50880 ffff9d8d`b281f000 : ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad : 0xffff9d8d`b29c9d50
fffff804`1db50888 ffff9d8d`b281fe40 : 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 : 0xffff9d8d`b281f000
fffff804`1db50890 00000001`b283ad01 : 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 : 0xffff9d8d`b281fe40
fffff804`1db50898 00000000`00000001 : ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 00000000`00000000 : 0x00000001`b283ad01
fffff804`1db508a0 ffff9d8d`000001ad : 00000000`00000000 ffff9d8d`af928350 00000000`00000000 00000000`00000000 : 0x1
fffff804`1db508a8 00000000`00000000 : ffff9d8d`af928350 00000000`00000000 00000000`00000000 ffff9d00`00000000 : 0xffff9d8d`000001ad


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff804`271033b4 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:15:42.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.239

ANALYSIS_SESSION_ELAPSED_TIME:  b5e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}



{{{

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`62c00000 PsLoadedModuleList = 0xfffff803`630432f0
Debug session time: Fri Aug  2 20:37:09.365 2019 (UTC + 3:00)
System Uptime: 0 days 0:11:15.077
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff800803df71a0, Virtual address for the attempted execute.
Arg2: 8a00000809c008e3, PTE contents.
Arg3: ffff908edb1c8340, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: ffff800803df71a0

BUGCHECK_P2: 8a00000809c008e3

BUGCHECK_P3: ffff908edb1c8340

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:08:23.0965

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME:  ffff908edb1c8340 -- (.trap 0xffff908edb1c8340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff800803df71a0 rbx=0000000000000000 rcx=ffff8008042dab50
rdx=ffff80080ae10600 rsi=0000000000000000 rdi=0000000000000000
rip=ffff800803df71a0 rsp=ffff908edb1c84d8 rbp=ffff908edb1c8559
 r8=0000000000000001  r9=0000000000000000 r10=fffff8036e9c5b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff8008`03df71a0 1101            adc     dword ptr [rcx],eax ds:ffff8008`042dab50=03da7ef0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80362e554bc to fffff80362dbc900

STACK_TEXT:  
ffff908e`db1c8118 fffff803`62e554bc : 00000000`000000fc ffff8008`03df71a0 8a000008`09c008e3 ffff908e`db1c8340 : nt!KeBugCheckEx
ffff908e`db1c8120 fffff803`62e4fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 ffff908e`db1c8260 : nt!MiCheckSystemNxFault+0x125330
ffff908e`db1c8160 fffff803`62c7ac2a : 00000000`00000006 00000000`00000011 ffff908e`db1c82a0 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
ffff908e`db1c81a0 fffff803`62dca920 : 00000000`00000000 fffff803`b2503711 00000000`00000002 00000000`00000036 : nt!MmAccessFault+0x48a
ffff908e`db1c8340 ffff8008`03df71a0 : fffff803`6778aa51 ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 : nt!KiPageFault+0x360
ffff908e`db1c84d8 fffff803`6778aa51 : ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 ffff8008`0ae10600 : 0xffff8008`03df71a0
ffff908e`db1c84e0 fffff803`6778eba3 : 00000000`00000002 00000000`00000000 fffff803`00000001 fffff803`6ea62101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ffff908e`db1c85c0 fffff803`6778bcdf : fffff803`60367101 ffff8008`03afb9a1 ffff8008`043198c0 ffff8008`0ae10600 : ndis!ndisCallSendCompleteHandler+0x33
ffff908e`db1c8600 fffff803`70ed33b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff803`70ed0d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
ffff908e`db1c86f0 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff803`70ed0d00 00000000`00000000 : e1d65x64+0x133b4
ffff908e`db1c86f8 00000001`00000000 : 00000001`00000000 fffff803`70ed0d00 00000000`00000000 00000000`00000000 : 0x2
ffff908e`db1c8700 00000001`00000000 : fffff803`70ed0d00 00000000`00000000 00000000`00000000 ffff8008`03e23000 : 0x00000001`00000000
ffff908e`db1c8708 fffff803`70ed0d00 : 00000000`00000000 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 : 0x00000001`00000000
ffff908e`db1c8710 00000000`00000000 : 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 00000001`03e3ed01 : e1d65x64+0x10d00


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff803`70ed33b4 448b7dcb        mov     r15d,dword ptr [rbp-35h]

FAULT_INSTR_CODE:  cb7d8b44

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:37:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  10b20

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}
",MaaSoftware
18856,Windows 10 hangs with High CPU Usage after changing number of Cores,Linux,Windows,VirtualBox 6.0.10,2019-08-20T04:35:43Z,2019-08-20T04:35:43Z,"A Guest Windows 10 (Latest patches Aug 2019) built with a single core fails after initial startup when the CPU cores are changed to anything above 1. The machine usually stops with a black screen and the twirling dots and almost never reaches the login screen. The CPU usage sits at 100%

Building a new machine with multiple cores works fine. This appears to be a similar bug to one reported with Version 5.X of Virtual Box.

Host is Linux (OpenSUSE). Tried on two hosts, XEON and Desktop I4. Both systems are successfully running many other VirtualBox hosts, both Windows and Linux.
",Eric Belcher
18855,please add much better sound support for DOS VMs,Windows,other,VirtualBox 6.0.10,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
18390,'memory could not be read' crash in Linux guest / Windows host 6.02 and 6.04,Windows,Linux,VirtualBox 6.0.4,2019-08-21T13:09:11Z,2019-08-21T13:09:11Z,"I am running a Linux guest (Mint Virtualbox image downloaded from www.osboxes.org) in a Windows 10 host.

I started running this guest under VirtualBox 6.0.2 and experienced this crash. A couple of days later I noticed 6.0.4 was available and tried updating to that to see whether it had been fixed, but the crash is still occurring and has happened 3x today, so it is fairly regular.

The guest isn't running too much - it's being used as a dev box with Docker (postgres / pgAdmin) and VS Code. There doesn't seem to be a particular pattern in what I'm doing before a crash. The VM doesn't have many modifications to base settings - 2 CPU, bidir clipboard and 2 networks (NAT and Host Only).

The error message is:
'The instruction at 0x00007FFC612061E3 referenced memory at 0x00000000000010. The memory could not be read'

I have attached the output from VBoxBugReport",MattA
18860,Error opening,other,other,VirtualBox 5.2.6,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
18859,"Guest randomly crashes with ""The memory could not be read""",Windows,Linux,VirtualBox 6.0.10,2019-08-21T19:15:03Z,2019-08-21T19:15:03Z,"I am running a Windows 10 1903 host and a Ubuntu 19.04 guest. The Ubuntu guest crashes fairly often with the attached dialog (see attached PNG file), warning of ""The memory could not be read.""

Both host and guest are using the latest patches. The guest has the current VMWare Extensions installed. The guest has 3D acceleration enabled.

Almost all of this guest OS's usage is for using Chromium browser to browse everyday sites, like Gmail, Facebook, CNN, etc. I feel it's fairly vanilla other than installing a few commodity apps like Chromium, GIMP, and Visual Studio Code.

The crash can happen when I am using nothing other than Chromium. In fact, just today, the crash happened less than 15 minutes after starting the VM. I attached log files from that crash.

Sometimes right-click context menus in Chromium go black. That is, you right-click on something, and the context menu that pops up is just a black rectangle. You can still click on things in that menu, but . I ''loosely'' correlate this to ""the VM is going to crash sooner than later"", but I am not sure there is a correlation. This morning, I did not notice the black context menus, although I do not think I invoked one.",Aren Cambre
18861,The virtual machine has terminated unexpectedly during startup,Windows,Windows,VirtualBox 6.0.10,2019-08-22T09:13:58Z,2019-08-22T09:13:58Z,"Не удалось открыть сессию для виртуальной машины МЗНП_10.

The virtual machine 'МЗНП_10' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\bxz\VirtualBox VMs\МЗНП_10\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

",bxz
18862,The Guest window will flicker with the package virtualbox-guest-additions,Mac OS X,Linux,VirtualBox 6.0.10,2019-08-23T05:43:46Z,2019-08-23T05:43:46Z,"Since version 28 of Fedora, the package comes with the distribution but with VirtualBox 6; when using Fedora 30 the package Guest Additions is having issues with the VBoxSVGA graphics card, as it start to wake up the guest window (it turns white and then goes back to normal), but if I use the VMSVGA controller it does not do it.  However the screen does not dinamically resizes, whereas with the VBoxSVGA it does it but then it fails.  I have had to remove the package and install the Guest Additions CD Image.

My OS: MacOS as Host. 
Guest: Fedora 30
Package: virtualbox-guest-additions",luispautt
18536,VERR_NEM_VM_CREATE_FAILED with Win10 10.0.18362,all,all,VirtualBox 6.0.4,2019-08-25T01:21:31Z,2019-08-25T01:21:31Z,"dear oracle team,

no matter which bios settings or windows settings (hyper-v on off, virtualization on off, sandbox on off, all windows additional functions on (normal) or off) I think I get this error: VERR_NEM_VM_CREATE_FAILED

I do not know any more and hope for your support. here is an inserted log to my normal settings.

Yours sincerely
roman prosek

sehr geehrtes oracle team, 

egal welche bios einstellungen oder windows einstellungen (hyper-v an aus, virtualisation an aus, sandbox an aus, alle windows zusatz funktionen an (normal) oder aus) ich vornehme ich bekomme diesen fehler: VERR_NEM_VM_CREATE_FAILED 

ich weis nicht mehr weiter und hoffe auf ihre unterstützung. hier noch ein eingefügter log zu meinen normalen einstellungen.

mit freundlichen grüßen 
roman prosek
",supra
18841,enhancement: merge title bar and menu bar,other,other,VirtualBox 6.0.10,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
18815,No guest DHCP through host WiFi in bridged mode,Linux,Linux,VirtualBox 6.0.10,2019-08-25T02:48:36Z,2019-08-25T02:48:36Z,"Hi there!

I'm experiencing problems with the combination host wifi, bridged mode and guest DHCP. I'm hoping not to create a duplicate.

- Host OS: Ubuntu 18.04
- Guest OS: Ubuntu 18.04
- Version 6.0.10 r132072 (Qt5.9.5)

The guest VM is sending DHCP Requests with its MAC address but gets no answer.
When debugging on the hosts wlan0 I see 2 DHCP Requests - 1 from the MAC of the guest VM and 1 with the MAC of wlan0 on behalf of the guest VM - but still no answer. I'm using tcpdump to trace packets.

Debugging of the DHCP server shows incoming request and outgoing answers.

Other physical devices get IP addresses.

A friend of mine with Windows 10 for the host OS sees the same problem.

There are hints on the net to change the adapter type from 'Intel PRO 1000 MT Desktop' to '... Server' - unfortunately without success for me.

On cable ethernet it works fine. The same goes for WiFi using manual IP address configuration on the guest OS.

Cheers!

JK
",JKu
18870,vboxwebsrv IPerformanceCollector.queryMetricsData failed.,Linux,other,VirtualBox 6.0.8,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
18871,User Account delete,other,other,VirtualBox 6.0.10,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
18873,"""VBoxManage sharedfolder add"" is missing documentation about the ""--auto-mount-point"" option",all,all,VirtualBox 6.0.10,2019-08-28T09:35:59Z,2019-08-28T09:35:59Z,"The automount point option which is exposed in the GUI, while also available in the CLI via the ""`VBoxManage sharedfolder add`"" command, it's not documented either in the ""`VBoxManageHelp.cpp`"", the ""`SDKRef.xml`"", and the ""`user_VBoxManage.xml`"" (that's all the suspects that I could find).

Also, if it's not too late, you could change that option from ""`--auto-mount-point`"" to ""`--automount-point`"" to be more consistent with the ""`--automount`"" option.",Socratis
18865,Prompt to assign another UUID when already exists.,other,other,VirtualBox 6.0.10,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
18876,Default window size is inscrutably small on macOS,Mac OS X,other,VirtualBox 6.0.10,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
18877,binary in shared folder loses executable permission while running,Windows,Linux,VirtualBox 6.0.10,2019-08-29T07:36:41Z,2019-08-29T07:36:41Z,"After upgrading from virtualbox v5.0 to v6.0.10 I was not able to execute a binary from a shared folder (host Windows, guest Ubuntu) twice in parallel: while executing its permission would change from -rwxrwxrwx to -rw-rw-rw-.

I had mounted it via a line in /etc/fstab:
{{{
FolderName  /home/somewhere vboxsf rw,uid=1000,gid=1000,dmode=755  0  0
}}}

how to reproduce: with that mount:
{{{
cp /bin/cat /home/somewhere/cat2
ls -l /home/somewhere/cat2 # => permissions -rwxrwxrwx, owner me:me
/home/somewhere/cat2 &
ls -l /home/somewhere/cat2 # => permissions -rw-rw-rw-
/home/somewhere/cat2   # => 'permission denied'
}}}
After stopping the running executable the permissions return to -rwxrwxrwx again.

Mounting as an automount instead resolves the problem: cat2 has owner root:vboxsf, and permissions -rwxrwx--- - and that doesn't change while running.

",nijhof
18322,Shared folders hang while R/W access,Linux,Windows,VirtualBox 6.0.2,2019-08-29T07:37:09Z,2019-08-29T07:37:09Z,"Host `lsb_release -a` is 
{{{
Distributor ID: Debian
Description:    Debian GNU/Linux 8.11 (jessie)
Release:        8.11
Codename:       jessie
}}}


I'm using shared folders in Windows 7 x86 guest and Mentor Expedition PCB hangs if I try to open project, placed on shared disk.

This behavior is not observed if I replace guest additions with version 5.2.22. Versions 6.0.0 and 6.0.2 show exactly the same behavior.

Other read/write operations doesn't show any problem (at this time).

I've tried to investigate hanging I/O operation in Expedition PCB and with the Process Monitor (Sysinternals) found, that last unfinished call was '''QueryDirectory'''. This event description from ProcMon is

{{{
Date & Time:	17.01.2019 14:58:38
Event Class:	File System
Operation:	QueryDirectory
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KiberLock-NET\20190115\KibLck-NET_v1p0\PCB\.lck_dir\*.lckreq
TID:	4996
Duration:	
Filter:	*.lckreq
}}}

Call stack (reported by ProcMon) is

{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtQueryDirectoryFile + 0x5b	0xe3444528	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	NtQueryDirectoryFile + 0xc	0x77825acc	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	FindFirstFileExW + 0x276	0x7598b355	C:\Windows\System32\KernelBase.dll
10	KernelBase.dll	FindFirstFileA + 0x4a	0x7599a956	C:\Windows\System32\KernelBase.dll
11	xf_Os.dll	xf_Os.dll + 0x4f3d	0x10004f3d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\lib\xf_Os.dll
}}}

And another similar hang event from ProcMon and another process, tried to call the '''WriteFile''':

{{{
Date & Time:	17.01.2019 16:02:08
Event Class:	File System
Operation:	WriteFile
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KIBERLOCK-NET\20190115\KIBLCK-NET_V1P0\database\cdbsvr\log\2019-01-17 16.02.07-1536\2019.01.17.txt
TID:	2648
Duration:	
Offset:	6,109
Length:	82
Priority:	Normal
}}}

Call stack is very similar to the '''QueryDirectory''' one:
{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtWriteFile + 0x6fe	0xe3480994	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	ZwWriteFile + 0xc	0x7782659c	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	WriteFile + 0x5f	0x759875ad	C:\Windows\System32\KernelBase.dll
10	kernel32.dll	WriteFile + 0x4e	0x768d56e4	C:\Windows\System32\kernel32.dll
11	msvcr90.dll	lseeki64 + 0x56b	0x71cc99ad	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
12	msvcr90.dll	write + 0x9f	0x71cc9d37	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
13	msvcr90.dll	fdopen + 0x1c0	0x71c8fea2	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
14	msvcr90.dll	fflush_nolock + 0x1c	0x71c8fef0	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
15	msvcr90.dll	fflush + 0x30	0x71c90030	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
16	iCDBNetServer.exe	iCDBNetServer.exe + 0x47fe6d	0x87fe6d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\bin\iCDBNetServer.exe

}}}


",makc
17044,Doing network copy from shared folder does not transfer file correctly: wrong md5sum,Linux,other,VirtualBox 5.1.26,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
18881,Guest additions installation fails with: The network operation failed with the following error:  During network request: Unknown reason.,Linux,other,VirtualBox 6.0.10,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
18884,Failed to get a console object,Mac OS X,Linux,VirtualBox 6.0.10,2019-08-30T11:37:17Z,2019-08-30T11:37:17Z,"I develop HA cluster and use VirtualBox to test the system in loop. When I test in loop boot/shutdown and have opened GUI, sometimes I see next error window:

{{{
Failed to open a session for the virtual machine witness.

Failed to get a console object from the direct session (VBOX_E_INVALID_OBJECT_STATE).

Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
}}}

But this does not stop the running test script or virtualbox itself. I hope I'll can attach screenshot and logs. As far as I see the error is risen on massive (I use 9 VM) simultaneous  shutdown by command

{{{
VBoxManage controlvm ""$h"" acpipowerbutton
}}}

",Olleg
18823,Failed to create the VirtualBox object!,Mac OS X,Linux,VirtualBox 6.0.10,2019-08-30T12:23:03Z,2019-08-30T12:23:03Z,"Version 6.0.10 r132072 (Qt5.6.3)

I created a test bed on VirtualBox of HA cluster. And I simulate hardware failures in loop. And with very rare probability (I got it on 424 iteration) I get VirtualBox error.


{{{
+ VBoxManage snapshot tuchanka0a restore install
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

}}}
",Olleg
18886,"Virtual screen 2 crashes after update to virtualbox 6.0.10, but only when running ubuntu",Windows,Linux,VirtualBox 6.0.10,2019-08-31T16:08:46Z,2019-08-31T16:08:46Z,"I usually run ubuntu 18.04 in a virtual box on a Windows 10 host and use two virtual screens, i.e. virtual screen 1 and virtual screen 2. Today I updated my virtualbox to 6.0.10. When I restarted the virtual machine with ubuntu, virtual screen 1 and virtual screen 2 opens as usual, see screen shot here: https://imgur.com/a/owwjNnL

Furthermore, I can move the windows with virtual screen 1 and virtual screen 2 around. However, when I try to go to full screen or to resize the windows, screen 2 closes/crashes. It is then impossible to restart it by choosing view->virtual screen 2 -> enable. 

To see where the problem lies I also installed ubuntu 19.04 and windows 10 in virtual machines. With ubuntu 19.04 I still got the same problem. But with the windows 10 virtual machine everything worked, even if the graphics of window is flickering a couple of seconds before adapting to the new size. What can I do?
",haggle
18887,I´ll try to initiate de sesion for install a windows XP and fail,other,other,VirtualBox 6.0.10,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
18889,Detect elementaryOS as Ubuntu 64-Bit,other,other,VirtualBox 6.0.10,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
18890,"VirtualBox 6.0.10, VM window - black color gets transparent with Xwayland",Linux,all,VirtualBox 6.0.10,2019-09-01T18:55:38Z,2019-09-01T18:55:38Z,"Hello,

I'm running VirtualBox 6.0.10 on Gentoo Linux with Xwayland as native Wayland support for VBox is not ready yet. When any VM starts in windowed mode everything that is black in that VM gets transparent (other colors are semi-transparent, if not white). When VM goes full screen the issue mostly disappears - sometimes black fonts get transparent. Changing graphics adapter type in VM settings, toggling 2D/3D acceleration and installing VM guests doesn't change anything.",Hubert Kromer
17898,Can Not Assign More Than 8 Processors to Windows 10 Guest,Linux,Windows,VirtualBox 5.2.16,2019-09-02T08:47:10Z,2019-09-02T08:47:10Z,"I just built a new Linux (Gentoo) system based on a SuperMicro mainboard, C9X299-PG300, and an Intel i9-7940X (14-core, 28 thread) CPU. I copied over my Windows 10 VirtualBox guest VM from the old system (Intel i7 8-core) to the new system. The Virtual Box guest boots without issue using the old settings (8-processors). However, if I shut down the VM and change the settings to a higher processor count (I have tried 12 and 14 cores), the VM does not progress very far into its boot: I see a blue background and the windows icon. None of the VirtualBox activity icons at the bottom of the Guest window are active: all dark. That is it. There is one Virtual Box process that continues to run at 100% cpu usage until I kill the VM. In the VirtualBox log the relevant part is:


{{{
00:00:03.569172 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
00:00:03.570686 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:03.872720 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f2f74000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0
00:00:03.872802 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:03.872885 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:03.872897 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:03.872908 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:04.610473 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:04.610490 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:04.610506 GIM: HyperV: Enabled hypercall page at 0x000000000020f000
00:00:04.610778 GIM: HyperV: Unknown/invalid hypercall opcode 0x8001 (32769)
00:00:04.610792 GIM: HyperV: Enabled TSC page at 0x000000000000c000 - u64TscScale=0xd3add100000000 u64TscKHz=0x2f3dc9 (3 096 009) Seq=1
00:00:04.610982 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
00:00:04.611068 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000d000
00:00:04.614818 APIC0: Attempt to read reserved/unknown MSR (0x80e) -> #GP(0)
00:00:04.614825 IEM: rdmsr(0x80e) -> #GP(0)
00:00:04.614859 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000096 P2=0xfffff80360406fd9 P3=0x0 P4=0x0
00:05:36.462561 GUI: Request to close active machine-window.
}}}

The ""HyperV: Guest indicates a fatal condition!"" does not look good.",Jagdpanther
18891,USB support feature make error in silent installation,Windows,Windows,VirtualBox 6.0.10,2019-09-02T12:15:02Z,2019-09-02T12:15:02Z,"Hello,

I tried to make silent install via msiexec.exe and with .msi file. So, when I used command ""msiexec /i [path/to/file.msi] /norestart /qn"" nothing happened. I attach log from one of my tries. 

This problem applies to 6.0.10 and 5.x version.

I discovered when I use command ""msiexec.exe /i [path/to/file.msi /norestart /qn -msiparams ADDLOCAL=VBoxApplication,VBoxNetwork,VBoxPython"" (so I'm not installing USB feature) it works and installation can go on. 

This happen's only on machines which hadn't got VB earlier. Machines with older versions can be updated without any problem.    ",Fangier
18894,Allow deleting running VMs,other,other,VirtualBox 6.0.10,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
18895,"Gray out, don't rearrange, disabled buttons",other,other,VirtualBox 6.0.10,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
18896,Virtual hard disk UI often discards decimal point,Mac OS X,other,VirtualBox 6.0.10,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
18899,Allow VM window to close while VM settings window is open,Mac OS X,other,VirtualBox 6.0.10,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
18903,VirtualBox does not start when docked,other,other,VirtualBox 6.0.10,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
18905,Graphics Issues with VBoxSVGA,Linux,Windows,VirtualBox 6.0.10,2019-09-04T18:45:33Z,2019-09-04T18:45:33Z,"With the upgrade to VirtualBox 6.0.12 I received a warning that in version 6.1.0 VBoxVGA will no longer be supported and I need to migrate my VM to VBoxSVGA.

I attempted to change my Graphics Controller which placed my VM in an unusable state as it kept crashing the Windows GUI.  I put the guest into SafeMode to install the guest additions which allowed me to boot.

Now when using the guest I am unable to view applications as they render as black boxes.  Examples of applications not working: Google Chrome, Microsoft Outlook, just about anything not part of Windows OS.

I have also tested VMSVGA and this is not working either.  My Display configuration is:
Video Memory: 256 MB
Screens: 2
Graphics Controller: VMSVGA
Acceleration: 2D Video, 3D
Remote Desktop Server: Disabled
Recording: Disabled

Happy to provide anything that helps with diagnostics, but the logs were not showing anything of value to me.
",Bryan R Festa
18907,Guest display will not size correctly,Windows,Windows,VirtualBox 6.0.12,2019-09-04T19:33:39Z,2019-09-04T19:33:39Z,"Guest Additions icon does not appear on taskbar
Guest Additions Service is running normally
Seamless Mode and Auto-resize Guest Display are both greyed out

VirtualBox 6.0
Version 6.0.12 r133076 (Qt5.6.2)

Guest Additions Installed
Version 6.0.12.0

Host
Win10 Pro
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Host Graphics
Intel UHD Graphics 620
Driver Version 23.20.16.4849

Guest
Win10 Pro 64
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Guest Graphics
VirtualBox Graphics Adapter (WDDM)
Driver Version 6.0.12.0
",JTC
16978,Windows 10: scan for hardware changes freezes after loading Virtual Box manager,Windows,Linux,VirtualBox 5.1.26,2019-09-04T20:44:46Z,2019-09-04T20:44:46Z,"Windows 10 Pro
Virtual Box  5.1.26 r117224 (Qt5.6.2)

Restart windows 10
Open device manager
Action: Scan for Hardware Changes

The scan completes normally

Open the Virtual Box manager (doesn't matter if we run a session)
Close virtual box manager
Open device manager
Action: Scan for Hardware Changes

The scan never seems to complete.  The ""Scanning plug and play compliant hardware..."" dialog stays on screen.

Plugging in a new device (such as a USB device) does nothing.   It is not recognized by Windows.

Something happens to windows when the virtual box application is loaded.

",K1MGY
4427,active FTP doesn't work with NAT,Solaris,Windows,VirtualBox 3.0.0,2019-09-05T02:54:35Z,2019-09-05T02:54:35Z,"This is with a 64-bit OpenSolaris host (2009.06).  It happens with all tested guests (XP, Ubuntu, OpenSolaris, Solaris 10), both with NAT and bridged networking.  The problem did not exist prior to 3.0.0, and has been confirmed both with pre-existing guests and newly created guests.

When you open an FTP session from the guest to the OpenSolaris host, the host returns an error like this one from a NAT guest:

Jun 21 19:50:21 fnog ftpd[1902]: [ID 227848 daemon.warning] refused PORT 10.0.2.15,60783 from fnog [192.168.99.22]

192.168.99.22 is the host IP.

If you do the same with VB 2.2.4 on the same host, ftpd logs no errors and successfully connects the guest.  This has been tested on two different hosts.  Both tested installations of the host OS use an unmodified default ftp configuration.

With FTP servers on the Internet, VB guests connect, but are unable to list files or directories on the FTP server using either the 'ls' or 'dir' commands.  The same FTP servers interact normally with computers that are not VB guests.  One tested example would be ftp.sunfreeware.com.

Shared folders and SSH/SCP/SFTP exhibit no observed problems from guest to host, but are slower for large transfers and for network testing.

I will be attaching a log file soon.",bqbauer
18908,The access to shared folder hangs the vmachine and makes it to restart itself,Windows,Windows,VirtualBox 6.0.10,2019-09-05T09:07:55Z,2019-09-05T09:07:55Z,"Sometimes when I connect to the shared folder the vmachine W1064bits hangs and 1 or 2 seconds after, restarts itself. I change the host machine, I reinstall a new vmachine but I got the same issue.
I updates the guestaddit from 6.0.10 to 6.0.12 but no change",llazare
17477,Compacting VDI file resulting in corrupt file system on High Sierra (APFS),Mac OS X,Windows,VirtualBox 5.2.6,2019-09-08T01:07:18Z,2019-09-08T01:07:18Z,"I tried to compact a VirtualBox VDI file (Windows 10 Guest) with this commands on High Sierra 10.13.2 (17C205):

 1. VBoxManage modifymedium disk XXX.vdi --compact
 2. VBoxManage modifyhd XXX.vdi --compact

Both commands won´t finish and resulting in an corrupt file system (APFS) on the host.

After that I´m not able to show the VDI file or navigate to the VM folder which contains the VDI file. Finder crashes if I want to do that, Terminal also crahses and Time Machine Backups can´t finish if Time Machine passes that folder for backups...

I had to boot into recovery mode to repair the filesystem of my main Macintosh HD, after that I was able to remove the corrupt VDI file...

This is the second time I had that issue, fortunately I was able to repair my file system this time, the last time with macOS High Sierra 10.13.0 and VirtualBox 5.1.30 I ending with and corrupt file system and was not able to repair it, this means I completely had to restore my Mac...

",DanielH
18921,Received critical error on new VM,Windows,Windows,VirtualBox 6.0.12,2019-09-10T13:15:57Z,2019-09-10T13:15:57Z,Log files attached,broberts160
18923,Bad performance in VBoxSVGA Adapter on retina screens,Mac OS X,Windows,VirtualBox 6.0.12,2019-09-11T18:34:53Z,2019-09-11T18:34:53Z,"Thank you for resolving some of the graphics issues in the VBoxSVGA adapter for the 6.0.12 release. It's getting closer to being usable, but for now I still have to stick with the VBoxVGA adapter to be able to work.

The performance of the VBoxSVGA adapter in scaled (200% autoscale) output on a MacBook Pro with retina display is really bad. When I switch to unscaled 100% output the performance gets better, but then everything becomes unreadable.

The performance issue can easily be seen when having 200% autoscale output on a retina display and then clicking the start menu. The start menu appears slowly with poor performance.

As I switch between multiple monitors (built-in retina and external LoDPI 4k), I would need a working solution for this before you remove the trusty good old VBoxVGA in 6.1.",klas
16032,VirtualBox not compatible with USBPcap and similar,Windows,all,VirtualBox 5.1.6,2019-09-12T00:10:55Z,2019-09-12T00:10:55Z,"Hello,

* Issue:

current versions of VirtualBox are not compatible with USBPcap on Windows (e.g. Windows 8.1 or Windows 10).

* Description

USBPcap provides USB traffic recording functionality by injecting itself into the USB stack (see http://desowin.org/usbpcap/block_diagram.html) in a way currently incompatible with the way VirtualBox does something similar.

* Experienced behavior

Host USB device is unavailable (""busy"") for attachment to Virtual Machine with USBPcap installed and active. USBPcap can be installed as (optional but default) component of WireShark.

* Expected behavior

VirtualBox forwards the USB device in a defined manner, i.e. either with all USB traffic happening inside the VM visible to USBPcap, or with all USB traffic inside the VM circumventing USBPcap

* Why shouldn't this be fixed by USBPcap?

There are multiple software packages providing similar or identical USB sniffing capability in a similar or near identical functionality, addressing this in all of them with special code instead of handling this properly at the virtualization layer (already deeply involving itself with the system) seems odd.",berlincount
17485,"Crash 0xc0000005 after host suspend (Linux guest, Windows 7 host)",Windows,Linux,VirtualBox 5.2.6,2019-09-12T12:38:50Z,2019-09-12T12:38:50Z,"Crash occurred twice for me.
{{{
03:20:07.990450 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001140!!!
03:20:07.990470 
03:20:07.990471 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fefb15be75
03:20:07.990477 ExceptionInformation[0]=0000000000000000
03:20:07.990482 ExceptionInformation[1]=0000000000000070
}}}
!VirtualBox show error message, then virtual machine become turned off.",ukolovda
18919,Cursor doesn't capture,Windows,Windows,VirtualBox 6.0.12,2019-09-12T13:14:40Z,2019-09-12T13:14:40Z,"Hello, I have a problem. The cursor doesn't capture on my Windows 98 guest. I hope there's a solution. It happens, surprise, on the !VirtualBox last version and Windows 98 SE.",SamiVirtualBox
10811,MAC addresses filtered by VBox bridging,Linux,Linux,VirtualBox 4.1.18,2019-09-12T16:25:43Z,2019-09-12T16:25:43Z,"I am attempting to run an OpenVPN server in a Ubuntu 12.04 (server) guest machine running on a Ubuntu 12.04 (server) host via VBoxHeadless.  This OpenVPN server needs to run as a layer 2 VPN (tap) which means it will place clients onto the local LAN with their own MAC addresses visible, and these clients need to be capable of two-way communication at layer 2.  I have been using the bridged network adapter for the VM.

When run from within the VM, I can connect clients to this server and ping/log into the server's IP, (guest machine) but I cannot access the Host's IP or anything else on the LAN from the client.  If I set up the OpenVPN server identically on the host, (Which is the same OS and otherwise identical setup) it works fine.  OpenVPN requires setting up a bridge internally on the server for this kind of layer 2 tap VPN, and putting the ethernet interface into promiscuous mode.  I've tried attaching the VM bridged adapter to the physical eth0 interface of the host and also to a bridged adapter on the host that was then bridged to the eth0 interface while eth0 was in promiscuous mode (similar to the setup on the guest)

I have found two other references to this problem, one with a Linux host, the other with Windows.  The Windows one was ticket #8965.  Both references indicate that this bug was a regression between versions 4.0.4 and 4.0.6.  Since I'm using Ubuntu 12.04 and VBox 4.1.18, downgrading to VBox 4.0.4 to confirm this would be painful.

Looking at the changelog of 4.0.6, I suspect that I've found the culprit:
""Host-Only & Bridged & Internal Networking: fix for processing promiscuous mode requests by VMs, defaulting to switch behaviour ""

Not sure what is meant by ""switch behavior"" but a switch is nothing more than a many-port bridge, which will broadcast frames to all ports but the one it came in on if the MAC is not in the MAC table, will learn the source MAC of any frame and put it in the MAC table for the port it came in on, and will unicast learned MACs to the ports on which the MAC table says they reside.  This may be somewhat inconsistent with being able to specify a MAC for the bridged adapter of the guest (which I have also done in this case)  If the switch portion is not flooding unlearned frames out to the guest machine virtual ports and also learning new MAC entries from frames sent by those ports, then the behavior may be efficient, but it will also be incorrect for Guests with their interfaces in promiscuous mode.

This bug is closely related to #8965 and this version with the Linux host type is also referenced here: https://forums.virtualbox.org/viewtopic.php?f=7&t=42335&p=203067&hilit=openvpn#p203067
",Raltar
18930,VirtualBox-5.2.33-133021-Linux_x86.run hangs on lsmod,Linux,all,VirtualBox 5.2.32,2019-09-16T02:36:25Z,2019-09-16T02:36:25Z,"Two copies of lsmod running in D state.  In 5.2.32 I get 100% cpu on modprobe vboxdrv.

Debian Buster 10, Linux honey14 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) i686 GNU/Linux

Skip to 6:20 to see install still hung, swapping screen(1) to htop(1) and back. https://www.youtube.com/watch?v=ze95E4xIvEk

Thanks!",supaplextor
18932,No DNS from DHCP on NAT connection,Windows,all,VirtualBox 6.0.12,2019-09-17T00:05:17Z,2019-09-17T00:05:17Z,"On VirtualBox 6.0.12, with plain NAT configuration, the domain name resolution does not work anymore on Windows/Linux guests on Windows host.

I've checked quite everything on host and guests configuration and come up to the hypothesis that VirtualBox dhcp ""server"" does not send the DNS address, but it used to do on previous versions.

This is confirmed by DHCP not containing the DNS entry as shown by the following DHCP response:


{{{
$ sudo nmap --script broadcast-dhcp-discover

Starting Nmap 7.60 at 2019-09-12 08:08 CEST
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 10.0.2.16
|     DHCP Message Type: DHCPOFFER
|     Subnet Mask: 255.255.255.0
|     Router: 10.0.2.2
|     IP Address Lease Time: 1d00h00m00s
|_    Server Identifier: 10.0.2.2
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.51 seconds
}}}
",Han Fastolfe
18934,RFE: smart card sharing aka Shared mode,all,all,VirtualBox 6.0.12,2019-09-17T09:08:42Z,2019-09-17T09:08:42Z,"Being used to sharing smart cards between virtual guests in vmWare it seems to be one of the few things that VirtualBox is lacking.


https://pubs.vmware.com/workstation-11/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-6F6D2C78-F28C-4553-8E46-F337599174DB.html

 I found this https://pcsclite.apdu.fr/api/group__API.html they seem to be using the functionality of pcscd to achieve it as the daemon has to be stopped to enable passthrough instead of shared mode https://communities.vmware.com/thread/498792",variona
18936,VirtualBox ignores LIBGL_DRI3_DISABLE=1,Linux,all,VirtualBox 5.2.32,2019-09-17T12:48:02Z,2019-09-17T12:48:02Z,"Hello

Shell environment variable LIBGL_DRI3_DISABLE= is used to disable DRI3 on X Server.
Before VBox switched to libQt5*VBox.so it worked.
Now this envvar is ignored.
Please, fix.

Best regards
",waltk
18410,debian-stretch-netinst does not work with 'VBoxManage unattended install' because of incorrect install menu defaults,all,Linux,VirtualBox 6.0.4,2019-09-17T19:52:27Z,2019-09-17T19:52:27Z,"[attached script: reproduce-bug.sh] # 88 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

The install menu defaults for the stock debian-stretch-netinst ISO is setup to be ""Graphical Install"" rather than just ""Install"".

The files in the ISO that control this are[[BR]]
/isolinux/menu.cfg[[BR]]
/isolinux/gtk.cfg[[BR]]
/isolinux/txt.cfg[[BR]]

VBoxManage already generates a replacement for one of the above files, but flattens its name to ${aux_base_path}isolinux-txt.cfg, so this file is patched after it was generated, but before it was used.[[BR]]
Specifically, this patch was applied after running 'VBoxManage unattended install ...' but before running 'VBoxManage startvm <vm>'.

This works only because the /isolinux/txt.cfg follows /isolinux/gtk.cfg (in /isolinux/menu.cfg) and thus can override its use of 'default label' and 'menu default'. But this order could change in the future so the ideal solution is below.

The ideal solution is[[BR]]
  - Remove 'default installgui' and 'menu default' (within 'label installgui') from /isolinux/gtk.cfg[[BR]]
  - Add 'default install' and 'menu default' (within 'label install') from /isolinux/txt.cfg[[BR]]

Currently, since there is no 'ui' directives used, the 'default installgui' and 'default install' are being ignored.[[BR]]
---[[BR]]
https://www.syslinux.org/wiki/index.php?title=Config

https://www.syslinux.org/wiki/index.php?title=Menu

The function that modifies /isolinux/txt.cfg is:[[BR]]
  src/VBox/Main/src-server/UnattendedInstaller.cpp:[[BR]]
  HRESULT UnattendedDebianInstaller::editDebianTxtCfg(GeneralTextScript *pEditor)[[BR]]

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

It will use the graphical installer, and thus mandates a manual install.[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]
",Robert Nielsen
18941,First keypress are repeated multiple times,Mac OS X,Windows,VirtualBox 6.0.12,2019-09-18T06:56:45Z,2019-09-18T06:56:45Z,"Working with MS Project. When creating a new task and then trying to type in the either the successor or predesessor then the first keypress is repeated multiple times (not less than 5 times, but have been seen up to 15 times). So having a task with id 400 and it's predecessor is 399, then typing 399 results in 333333333333399. It's the first keypress no matter what key, this includes the ""Enter-key"" - this has not happened before in earlier versions. 
I can't use this version.",Jan P DK
18915,Critical structure corruption blue screen,Linux,Windows,VirtualBox 6.0.12,2019-09-18T07:38:00Z,2019-09-18T07:38:00Z,"Hi,
Virtualbox became unusable for me since a few months where the ""CRITICAL_STRUCTURE_CORRUPTION"" blue screens are happening regularly (multiple times per day). I also get screen refreshes all the time where the screen stays black for about 2-3 seconds where nothing can be done until the normal desktop gets back.

Attached is the most recent logfile from today, older logs can be found in my thread in the forum: https://forums.virtualbox.org/viewtopic.php?f=2&t=93939

I am using the VboxVGA driver and I can't use the VboxSVGA driver because the graphical glitches with this driver make working impossible (see my other thread here: https://forums.virtualbox.org/viewtopic.php?f=2&t=94585)",0x00
18215,6.0.0 Windows guest addition installation aborted,Linux,Windows,VirtualBox 6.0.0,2019-09-18T14:03:34Z,2019-09-18T14:03:34Z,"VirtualBox 6.0.0 r127566

Guest: MS Windows 10 EDU build 1803, 64-bit

Host: Linux Mint 19.1 MATE, 64-bit

When trying to install guest additions, the installation in MS Windows 10 will be aborted with error (log files attached). Tried also uninstall old guest additions in first place and then new one but did not help.",Edmund Laugasson
12162,Serial Port output slows down VM,Windows,Linux,VirtualBox 4.2.18,2019-09-18T22:57:01Z,2019-09-18T22:57:01Z,"I have a linux VM, with a kernel command-line saying console=ttyS0,115200 

With no serial port enabled, or a disconnected serial port, there are no problems. As soon as I redirect the serial port to a local file, the guest slows down significantly.

Booting the same guest using VMware Player (with the serial port also redirected to a file) does not show such a large performance penalty.

Alternatively, is there a faster solution to get /dev/console output onto a file on the host?",AxelFontaine
16327,"""Auto Capture keyboard"" option doesn't work",Linux,all,VirtualBox 5.1.12,2019-09-20T04:03:06Z,2019-09-20T04:03:06Z,"Virtualbox captures keyboard even when told to not do so.

Steps to reproduce:

1. Open a VM (e.g. create an empty one).
2. Go to Preferences → Input, and make sure the ""Auto Capture Keyboard"" is disabled.
3. Run the VM.
4. Focus the VM window (e.g. click on it)
5. Try global hotkeys of the host, like switching workspaces, windows, a player — nothing works.

It seem to be a regression to the old [https://www.virtualbox.org/ticket/8596 #8596], but I'm not naming it so because I don't know when it stopped working.

Tested on Archlinux, i3 WM.",Hi-Angel
18929,NS_ERROR_INVALID_ARG (0x80070057),other,other,VirtualBox 6.0.12,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
18928,Error Importing an Appliance (ODI),Linux,Windows,VirtualBox 6.0.12,2019-09-20T05:02:14Z,2019-09-20T05:02:14Z,"Hi

I have Virtual Box installed on my work laptop with a working appliance on it for just Linux.
I am trying to import an appliance for Oracle Data Integrator but I keep getting an error message shown here:

''Failed to import appliance C:\Users\marhamil\Downloads\VBoxApp-ODI12c\ODI 12c Getting Started VM - OTN 122131.ova.
Result Code: E_INVALIDARG (0x80070057)''

Please can someone help?

Thanks,
From Mark",Mark H
18411,ubuntu-bionic-server does not work with 'VBoxManage unattended install' because of preseeding post-install errors,all,Linux,VirtualBox 6.0.4,2019-09-20T06:35:25Z,2019-09-20T06:35:25Z,"[attached script: reproduce-bug.sh] # 111 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

It was reported here (and includes this fix):[[BR]]
https://forums.virtualbox.org/viewtopic.php?f=8&t=86798[[BR]]
I'm WildSAR[[BR]]

This is a single line change in .../UnattendedTemplates/ubuntu_preseed.cfg which is consistent with debian_preseed.cfg in the same directory.

The text of the error is:[[BR]]
---[[BR]]
!! Finish the installation[[BR]]

Failed to run preseeded command[[BR]]
Execution of preseeded command ""cp /cdrom/vboxpostinstall.sh[[BR]]
/target/root/vboxpostinstall.sh && chmod +x /target /root/vboxpostinstall.sh && /bin/bash[[BR]]
/root/vboxpostinstall.sh --preseed-late-command"" failed with exit code 127.[[BR]]
---[[BR]]

This is the patch which fixes ubuntu_preseed.cfg:

{{{
<  && /bin/bash /root/vboxpostinstall.sh --preseed-late-command
---
>  && /bin/sh /target/root/vboxpostinstall.sh --need-target-bash --preseed-late-command
}}}
There are *three* bugs in this single line of code:

/bin/bash should be /bin/sh[[BR]]
/root/vboxpostinstall.sh should be /target/root/vboxpostinstall.sh[[BR]]
--need-target-bash is missing[[BR]]

The above solution is the same as in .../UnattendedTemplates/debian_preseed.cfg (a peer file of ubuntu_preseed.cfg).

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]",Robert Nielsen
18950,clipboard stops working,Windows,Linux,VirtualBox 6.0.12,2019-09-20T07:07:09Z,2019-09-20T07:07:09Z,"As long as I've used VirtualBox this issue has occurred.  It's the same as described in bug #5266.  

> After a period of time the shared clipboard will stop working either in
> one direction or the other and sometime in both directions. A reboot of 
> the guest will bring it back. Logfile included.

Awhile back I found out that I can do this to rectify it sometimes...

killall -9 VBoxClient && /usr/bin/VBoxClient --clipboard && /usr/bin/VBoxClient --display && /usr/bin/VBoxClient --seamless && /usr/bin/VBoxClient --draganddrop

I'm hoping with the extra information regarding killing of the VBoxClient, that it will lead to a fix.  This has been happening for many years, I think more than 10.",Trent
18940,"Smart hide, auto-hide, hot corners and etc.. not working",Windows,Linux,VirtualBox 6.0.10,2019-09-20T16:50:19Z,2019-09-20T16:50:19Z,"Docks, top bars and title bars can be easily hidden by configuring the system from the settings or by downloading extensions. But none of them showing up when pointing/pushing/triggering their hot corners or places....",centaurusa
18946,Screenshot is causing the disk size update to fail,Windows,Linux,VirtualBox 6.0.12,2019-09-23T15:49:09Z,2019-09-23T15:49:09Z,"Hi, 
I am running a host PC Windows 10. Using the virtualbox to launch a Cent OS. 
I was trying to update my disk size on the CentOS as i had reached 100% utilisation. So i used (as recommended by many sites to update this) below command:
{https://stackoverflow.com/questions/8141045/virtualbox-extend-partition
/mnt/c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe modifymedium CentOSVD.vdi --resize 120000}

Idea was to increase the vdi size from 60Gb to 120Gb. 
But after this command, it was not directly reflecting in the Cent OS after restart (also windows restart). The increased volume succeeded on windows side without any errors. But CentOS was not showing this. 
After a lot of debug i found that i had a snapshot stored somewhere on the PC and this was preventing the additional disk to be shown on the CentOS.  {lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 68.3G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part 
}
The sda partition was always showing 68.3G. Even though i increased the VDI to 120G, it was not reflecting here. Then i deleted the snapshot and then i saw the correct results. 
{ lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 117.2G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part }
So somehow the process in the snapshot is preventing the process of disk space update. Please check.
Steps to reproduce:
1. Run Virtual Box on a windows 10 machine. 
2. Install the Cent OS running as guest OS on Virtual Box. 
3. Check the VDI disk size (Virtual and actual size)
4. Take a snapshot (Ctrl + Shift + T). Notice another VDI file is created in another location
5. Increase VDI disk size with above command (VBoxManage.exe modifymedium)
6. Reboot both windows and VBox. 
7. Check the disk space on guest OS (CentOS) it will not show the increase
8. Delete Snapshot. Newly created VDI file is deleted from Step 4.
9. Reboot both windows and VBox. 
10. Check the disk space on guest OS (CentOS) it will show the increase",aanche
18947,usb audio is extremely choppy,Windows,other,VirtualBox 6.0.12,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
18958,virtualbox 6.0.12 update doesn´t allow Fedora 30 VM start,Windows,Linux,VirtualBox 6.0.12,2019-09-25T04:49:39Z,2019-09-25T04:49:39Z,"Vm perfectly running on windows with version from 5.x to ""6.0.10 r132072 (Qt5.6.2)"" after 6.0.12 update was not able to start the vm. On configuration were displayed some problems about ""unsupported hardware acceleration"".

A fast roll-back to previous 6.0.10 fixed the proble,m, but seems that 6.10.12 have some problem.
 
Test environment: Windows 10 pro, notebook fujitsu lifebook i7-8650U, 32Gb ram, sss, lan",Piero Gerletti
18883,Issue with USB joystick SPEEDLINK COMPETITION PRO,Windows,Windows,VirtualBox 6.0.10,2019-09-29T15:23:00Z,2019-09-29T15:23:00Z,"Issue when arcade joystick Speedlink Competition Pro is inserted: when VBox GUI is running ('''don't need to start a VM''') this device switches erroneously from
SPEEDLINK COMPETITION PRO (VID_0738&PID_2217)
into
Game Controller for Android (VID_0079&PID_181C).

The same issue was already fixed by SDL author blacklisting the device from HID enumeration, so I hope you can do the same to solve this problem forcing me to unplug the device every time:
https://hg.libsdl.org/SDL/rev/64d32e614d64 ",hexaae
18638,"Graphics Issues, Machine Crashing on Linux Host and Windows 10 Guest",Linux,Windows,VirtualBox 6.0.6,2019-09-30T12:35:59Z,2019-09-30T12:35:59Z,"So I've been having major trouble getting my Windows 10 Guest to work correctly (From an Ubuntu 18.10 host). I've been having major graphics issues lately, especially when I turn on VBoxSVGA, which I use with 2D and 3D acceleration enabled.

Just now after experiencing some weird issue's I'll go into in a bit and trying to reboot my machine, I got a message box telling me VirtualBox had to abort and to submit a ticket. 

I'm attaching a log file for the ticket, as well as the VM Guest configuration file. As far as I know, everything is up to date and configured correctly.

I'm also attaching the output of lspci (for my host's graphics card) and a partial dump of dmesg as there are some warnings from VB kernel modules.

Some background:
Basically, everything seems to be working intermittently graphics-wise. All the issues seem to be occurring due to crashes inside C:\WINDOWS\system32\VBoxSVGA.dll, including frequent windows in Desktop Window Manager (dwm.exe). 

Additionally, sometimes I am getting the error ""Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver."". When this happens I have no choice but to restart because the guest's screen becomes totally black with a working cursor and a blurred version of the VB bios screen overlayed in white. There is no way to resolve this without a reboot.

When things get really bad, pretty much all apps refuse to launch (though the ones already launch still work) and they fail silently (this is really ironic and frustrating as this includes debugging apps), though for each attempt I see an error relating to VBoxSVGA.dll in the Windows Error Log. I am attaching several days worth of Windows Error Logs (Application Logs) in XML format in the hopes they contain some information. I'm also attaching an HTML export of the Windows Error Reports that were generated. (Unfortunately I didn't have saving minidumps enabled at the time.)

When this whole ""nothing will start"" phenomenon occurs a program that I'm frequently trying to use -- a 3D modeling program called Autodesk Fusion 360 -- actually freaks out because it will keep trying to restart a Chrome WebView process ad infinitum (obviously the ad infinitum bit isn't on VirtualBox). I've included a stack trace from a minidump of one of these crashes as it's one of the few minidumps I have. (I can't attach the minidump itself as the memory contains proprietary content.) 

If anyone could offer any help, it would be greatly appreciated. I'm happy to assist with debugging this in any way I can.
",Mike Vastola
18976,"""screen record"" doesn't work well on Windows 7 virtual machine",Windows,Windows,VirtualBox 6.0.12,2019-10-02T11:56:15Z,2019-10-02T11:56:15Z,"I used ""screen record"" to record the screen of my Windows 7 virtual machine. Everything seems not bad till I stopped the recording by clicking the ""stop"" button on the toolbar. After stooped, all keyboard input seems to be masked(but the mouse is OK). It return to be OK after I quit the ""fullscreen"" mode.I think it might be a BUG.

(I've already installed the guest additions.)",Danyang
18977,"All VM's on VirtualBox  goes to ""Guru Meditation state "" when KVM(virt-manager) VM's are 'power on'",other,other,VirtualBox 6.0.12,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
15478,VBoxTray.exe using excessive CPU,Windows,Windows,VirtualBox 5.0.20,2019-10-03T10:22:20Z,2019-10-03T10:22:20Z,"Windows 10 Host running Widows Guests. Problem started after upgrading to 5.0.18 and installing the GAs. Problem remained after upgrading to 5.0.20.

Symptom is that apps running in the guest get very sluggish. Sometimes slide bars are unresponsive. Menu pull downs always open the first selection. Symptoms appear several minutes after VM is started, but once VBoxTray.exe starts eating the CPU, it does not disappear.

Started thread in forums at: https://forums.virtualbox.org/viewtopic.php?f=2&t=77784

mpack suggested going back to 5.0.16 after just installing 5.0.16 GAs did not fix problem.

Problem does not appear when running 5.0.16 with the 5.0.16 GAs",pansophysr
18973,BSOD (crash) on Windows 10 host with console Linux guest in network driver,Windows,Linux,VirtualBox 6.0.12,2019-10-03T18:04:12Z,2019-10-03T18:04:12Z,"Bug previously opened as #18854 (BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver) is still exist in VirtualBox 6.0.12.
It is releated to active network I/O operations on Windows 10 x64 host with Linix guests (CentOS 7 or Debian 10 x64, for example).
I have reproduce it again when I have created and installed Debian 10 guest and have executed the command
cd /opt && mkdir -p ttt && wget -O - --user UserName --password Password ftp://192.168.0.28/full_backup_29.09.2019 | restore -x -a -T /opt/ttt -f /dev/stdin
where:
192.168.0.28 is IP address of Windows 10 host
192.168.0.91 is IP address of Debian 10 guest
192.168.0.0/24 is a 1 Gbps network on ""Intel(R) Ethernet Connection (2) I219-V"" NIC adapter.",MaaSoftware
18984,failure to install tools,Windows,Windows,VirtualBox 6.0.12,2019-10-05T16:00:05Z,2019-10-05T16:00:05Z,windows 10 host and guest. see screenshot.,DeGarden
18983,Crash Virtualbox guest bcause of segfalut of libc,Linux,Windows,VirtualBox 6.0.12,2019-10-06T18:51:23Z,2019-10-06T18:51:23Z,"Guest Windows10 is crashed suddenly when it is happen segfalut on Debian9 host.

Debian9 syslog is recorded with below messages.
It is seemed that this crash is associated with VBoxDrvLinuxIOCtl control.

{{{
Oct  5 07:45:53 svyomo2 kernel: [172631.378421] EMT-5[6163]: segfault at 7f7cf160ffa0 ip 00007f7d361d80b4 sp 00007f7cf170e918 error 4 in libc-2.24.so[7f7d360af000+195000]
Oct  5 07:45:53 svyomo2 kernel: [172631.378430] Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
Oct  5 07:45:53 svyomo2 kernel: [172631.378561] VBoxDrvLinuxIOCtl: copy_to_user(0x7f7cc00f28e0,,0x18); uCmd=0xc0305698!
Oct  5 07:45:53 svyomo2 kernel: [172631.378636] VBoxDrvLinuxIOCtl: copy_to_user(0x7f7cc10dce10,,0x18); uCmd=0xc0305698!
Oct  5 07:45:56 svyomo2 kernel: [172634.716100] device enxcce1d50dc8db left promiscuous mode
Oct  5 07:45:56 svyomo2 kernel: [172634.740027] vboxnetflt: 0 out of 332085879 packets were not sent (directed to host)
Oct  5 07:46:52 svyomo2 kernel: [172690.335485] vboxdrv: 0000000013086699 VMMR0.r0
Oct  5 07:46:52 svyomo2 kernel: [172690.818663] vboxdrv: 00000000f3fc2f31 VBoxDDR0.r0
Oct  5 07:46:52 svyomo2 kernel: [172691.049999] VBoxNetFlt: attached to 'enxcce1d50dc8db' / cc:e1:d5:0d:c8:db
Oct  5 07:46:53 svyomo2 kernel: [172691.509566] device enxcce1d50dc8db entered promiscuous mode
Oct  5 07:46:53 svyomo2 kernel: [172691.556485] vboxdrv: 0000000094df3d3b VBoxEhciR0.r0
}}}
",Yomo
18968,Installing Guest Additions on Windows does not check for admin rights,Windows,all,VirtualBox 6.0.12,2019-10-07T08:30:14Z,2019-10-07T08:30:14Z,"Host is Windows 10, 64-bit, all latest updates.  As good practise in our corporate environment, our accounts do not have admin rights.  All PCs have the same admin account set up, to which we all know the password, so if we need to install something then we can - but it stops viruses (and incompetence!) from doing major damage.

I've just upgraded VirtualBox from 6.0.10 to 6.0.12.  As expected, running the installer asked me for my admin password, which I entered, and 6.0.12 was installed correctly.  At the time, it also asked me if I wanted to upgrade Guest Additions.  I'd already downloaded the 6.0.12 ""vbox-extpack"" file, so I said no.

When VirtualBox started back up, I went to ""Preferences"" and tried adding the new 6.0.12 Guest Additions.  It failed on installation with just the error message ""E_FAILED"".  Upgrading via the ""Check updates"" option also failed the same way, and so did attempting to remove the 6.0.10 Guest Additions.  Rebooting the PC didn't help.

Looking in the log file, I found the following line:

> 00:11:43.122154 ExtPackUninst ExtPack: enmReason=1 iStatus=1 stderr='VBoxExtPackHelperApp.exe: error: Membership in the Administrators group is required to perform this action

Then I realised.  I ran VirtualBox using ""Run as administrator"", and this time installing the 6.0.12 Guest Additions worked perfectly.

So VirtualBox internally *IS* aware why installation failed - but the UI is not reporting this to the user.  Even if it just passed through that text unchanged, it would still be more meaningful than ""E_FAILED""!

I'm listing this as a defect, because the program is not working to reasonable user expectations for a reasonable user action.  I'm savvy enough to try to interpret a log file, and I know where to find the log file, but most users don't.",GBartlettPrior
18904,Unable to install VirtualBox on Debian 10 Buster,Linux,all,VirtualBox 6.0.10,2019-10-07T14:12:26Z,2019-10-07T14:12:26Z,"Hello.

Today I tried to upgrade my VirtualBox to the latest version.
I powered off my vms and started the update.
Now, all the versions I try to install (testbuilds included) fail on compiling.
The host is older. No Secure Boot, no EFI, just plain old BIOS and MBR.
OS: Debian 10 Buster almost headless (LXDE installed, but it doesn't start on boot and I almost never use it).

Errors on install:
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why

dmesg:
[  360.630491] vboxdrv: loading out-of-tree module taints kernel.
[  360.630672] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[  360.630887] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[  474.533886] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 2230.385340] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4321.446054] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 4468.860093] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4912.527732] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4946.446931] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 5099.180792] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 5657.446078] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab75af
[ 6310.679083] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000751064cb, val ffffffffc0ab792f
[ 7275.790717] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf

I tried the Fedora 29/30 fix, with no luck.

Please help... I'd hate to reinstall and fall back to Stretch.

If you need more details, please let me know.

Thank you.",baltzatu
18975,Resolution screen on the other machine,other,Windows,VirtualBox 6.0.12,2019-10-08T21:34:33Z,2019-10-08T21:34:33Z,"Hi guys, 

I have got problem, with screen resolution. I will describe my issue. On my computer VirtualMachine works good. I made a clone for my first colleague. On his PC works good too. I copied this same clone for third colleague and on his computer is Virtual Machine totaly slow, full of lags and in the end maximum of resolution is 1024X768. We already reinstall guest add. but nothing happen either. Would do you recommend, what to do? 

Thanks a lot. 

Jakub",Jakubco
18988,Wrong time synchronization,Linux,Linux,VirtualBox 6.0.8,2019-10-08T21:37:47Z,2019-10-08T21:37:47Z,"Hello,
I noticed that time is not running right when I'm offline (when I'm online, everything works).
For example: When I start virtual machine at 7:30 and I look to time after 10 minutes, on my host is 7:40, but on guest is 7:38. After next 10 minutes on host is 7:50 and on guest is 7:47...
Sync time settings on VirtualBox are default (I do no changes).

Thank you",max-m
18829,spontaneously causes host to reboot,Mac OS X,Linux,VirtualBox 6.0.10,2019-10-08T21:45:16Z,2019-10-08T21:45:16Z,"This has been an issue I've encountered since VB 6.0.8 and has continued through to VB 6.0.11.  
My host is an iMac running macOS 10.14.6, but issue started when it was on 10.14.5.
I run several linux guest VMs.  
Sometimes when I'm updating one or two, my iMac spontaneously reboots.  Sometimes when I'm booting a guest VM my iMac spontaneously reboots.  Sometimes when I'm shutting down a guest VM my iMac spontaneously reboots.

Here's the latest crash log from my iMac:

Anonymous UUID:       F3719D15-7DCA-7343-A61F-B939BEF8FF8D

Sun Aug 11 09:25:35 2019

*** Panic Report ***
panic(cpu 6 caller 0xffffff80120daadd): Kernel trap at 0xffffffa426926f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007f89184a6000, CR3: 0x00000005a79581a0, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0x00007f88f8423d44, RCX: 0x0000000000000200, RDX: 0x00000000000004dd
RSP: 0xffffffa3e8581c60, RBP: 0xffffffa3e8581d00, RSI: 0x00007f88f83f0000, RDI: 0x00007f89184a6000
R8:  0x00007f88f8423d18, R9:  0x00007f88f8423d78, R10: 0x0000000000000000, R11: 0x00007f88f8423d42
R12: 0x00007f88f8423d40, R13: 0x0000000000023c00, R14: 0x00007f88f8423d38, R15: 0x00007f88f8423d18
RFL: 0x0000000000050246, RIP: 0xffffffa426926f56, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007f89184a6000, Error code: 0x0000000000000002, Fault CPU: 0x6, PL: 1, VF: 5

Backtrace (CPU 6), Frame : Return Address
0xffffffa3e8581730 : 0xffffff8011fad6ed 
0xffffffa3e8581780 : 0xffffff80120e9185 
0xffffffa3e85817c0 : 0xffffff80120da8ba 
0xffffffa3e8581830 : 0xffffff8011f5ab40 
0xffffffa3e8581850 : 0xffffff8011fad107 
0xffffffa3e8581970 : 0xffffff8011facf53 
0xffffffa3e85819e0 : 0xffffff80120daadd 
0xffffffa3e8581b50 : 0xffffff8011f5ab40 
0xffffffa3e8581b70 : 0xffffffa426926f56 
0xffffffa3e8581d00 : 0xffffffa426912735 
0xffffffa3e8581dc0 : 0xffffffa426859da9 
0xffffffa3e8581df0 : 0xffffffa42684ee55 
0xffffffa3e8581e30 : 0xffffffa426843f05 
0xffffffa3e8581fb0 : 0xffffffa42692e168 
0xffffffa3ea993860 : 0xffffffa42685b906 
0xffffffa3ea9939f0 : 0xffffff7f9578342f 
0xffffffa3ea993a00 : 0xffffff7f957961db 
0xffffffa3ea993ac0 : 0xffffff7f95795ac6 
0xffffffa3ea993b40 : 0xffffff801223a163 
0xffffffa3ea993b80 : 0xffffff801222e8df 
0xffffffa3ea993c00 : 0xffffff8012220544 
0xffffffa3ea993e00 : 0xffffff801249b68b 
0xffffffa3ea993e30 : 0xffffff80124f1839 
0xffffffa3ea993f40 : 0xffffff80125b92ad 
0xffffffa3ea993fa0 : 0xffffff8011f5b306 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(6.0.11)[09081CCC-AD27-3F66-A7FB-68A23B0D18F7]@0xffffff7f95781000->0xffffff7f95870fff

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
18G87

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
Kernel slide:     0x0000000011c00000
Kernel text base: 0xffffff8011e00000
__HIB  text base: 0xffffff8011d00000
System model name: iMac18,2 (Mac-77F17D7DA9285301)

System uptime in nanoseconds: 844208412176885
last loaded kext at 750269373847264: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
last unloaded kext at 750399941670990: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
loaded kexts:
com.goldenfrog.VyprVPNMalwareFilter	1
com.goldenfrog.SplitTunnel	1
org.virtualbox.kext.VBoxNetAdp	6.0.11
org.virtualbox.kext.VBoxNetFlt	6.0.11
net.sf.tuntaposx.tun	1
org.virtualbox.kext.VBoxUSB	6.0.11
net.sf.tuntaposx.tap	1
org.virtualbox.kext.VBoxDrv	6.0.11
com.promise.driver.stex	6.2.9
com.apple.filesystems.afpfs	11.1
com.apple.nke.asp-tcp	8.0.2
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AppleTopCaseHIDEventDriver	138.4
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.kext.AMDFramebuffer	2.1.1
com.apple.kext.AMDRadeonX4000	2.1.1
com.apple.driver.AudioAUUC	1.70
com.apple.fileutil	20.036.15
com.apple.driver.AppleGraphicsDevicePolicy	3.50.12
com.apple.filesystems.autofs	3.0
com.apple.AGDCPluginDisplayMetrics	3.50.12
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.14d3
com.apple.driver.AGPM	110.25.11
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.pmtelemetry	1
com.apple.driver.AppleIntelKBLGraphics	12.1.0
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleHDA	282.54
com.apple.kext.AMD9500Controller	2.1.1
com.apple.driver.AppleThunderboltIP	3.1.2
com.apple.driver.AppleMCCSControl	1.5.9
com.apple.iokit.AppleBCM5701Ethernet	10.3.3
com.apple.iokit.BroadcomBluetooth20703USBTransport	6.0.14d3
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.AppleGFXHDA	100.1.414
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AirPort.BrcmNIC	1400.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	12.1.0
com.apple.driver.AppleSMCLMU	212
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleUSBODD	456.260.3
com.apple.iokit.SCSITaskUserClient	408.250.3
com.apple.driver.AppleUSBStorageCoexistentDriver	456.260.3
com.apple.driver.AppleVirtIO	2.1.3
com.apple.filesystems.hfs.kext	407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.filesystems.apfs	945.275.7
com.apple.driver.AppleSDXC	1.7.6
com.apple.driver.AppleAHCIPort	329.260.5
com.apple.private.KextAudit	1.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	201
com.apple.security.TMSafetyNet	8
com.apple.security.SecureRemotePassword	1.0
com.apple.driver.AppleHIDKeyboard	208
com.apple.driver.AppleActuatorDriver	2450.1
com.apple.driver.AppleMultitouchDriver	2450.1
com.apple.driver.AppleInputDeviceSupport	2440.2
com.apple.driver.AppleHSBluetoothDriver	138.4
com.apple.driver.IOBluetoothHIDDriver	6.0.14d3
com.apple.kext.AMDRadeonX4200HWLibs	1.0
com.apple.kext.AMDRadeonX4000HWServices	2.1.1
com.apple.iokit.IOUSBUserClient	900.4.2
com.apple.driver.AppleGraphicsControl	3.50.12
com.apple.kext.triggers	1.0
com.apple.iokit.IOAVBFamily	760.6
com.apple.plugin.IOgPTPPlugin	740.2
com.apple.iokit.IOSkywalkFamily	1
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	282.54
com.apple.kext.OSvKernDSPLib	528
com.apple.AppleGPUWrangler	3.50.12
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.driver.AppleHDAController	282.54
com.apple.iokit.IOHDAFamily	282.54
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.14d3
com.apple.iokit.IOBluetoothFamily	6.0.14d3
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IONDRVSupport	530.51
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.kext.AMDSupport	2.1.1
com.apple.AppleGraphicsDeviceControl	3.50.12
com.apple.iokit.IOAcceleratorFamily2	404.14
com.apple.iokit.IOSurface	255.6.1
com.apple.iokit.IOGraphicsFamily	530.66
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice	408.250.3
com.apple.iokit.IOBDStorageFamily	1.8
com.apple.iokit.IODVDStorageFamily	1.8
com.apple.iokit.IOCDStorageFamily	1.8
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.iokit.IOUSBMassStorageClass	4.0.4
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.iokit.IOSerialFamily	11
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleThunderboltDPInAdapter	5.6.9
com.apple.driver.AppleThunderboltDPOutAdapter	5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily	5.6.9
com.apple.driver.AppleThunderboltPCIUpAdapter	2.1.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.5
com.apple.driver.AppleHPM	3.4.1
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.iokit.IOAHCIFamily	288
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleThunderboltNHI	4.7.9
com.apple.iokit.IOThunderboltFamily	6.8.6
com.apple.iokit.IOSCSIParallelFamily	3.0.0
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.2
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.quarantine	3
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	493.0.0
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	456.260.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice	408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily	408.250.3
com.apple.iokit.IOStorageFamily	2.1
com.apple.kext.CoreTrust	1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOTimeSyncFamily	740.2
com.apple.iokit.IONetworkingFamily	3.4
com.apple.iokit.IOReportFamily	47
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
Model: iMac18,2, BootROM 175.0.0.0.0, 4 processors, Intel Core i7, 3.6 GHz, 32 GB, SMC 2.40f0
Graphics: kHW_AMDRadeonPro560Item, Radeon Pro 560, spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16E), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci105a,8760, RAID Controller, Thunderbolt@133,0,0
USB Device: USB 3.0 Bus
USB Device: Elements 25A2
USB Device: USB3.0 Hub
USB Device: Ultra Fit
USB Device: USB3.0 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB2.0 Hub
USB Device: HL-2040 series
USB Device: USB2.0 Hub
USB Device: EPSON Scanner
USB Device: Amazon Kindle
USB Device: E-USB Bridge for LS-120
USB Device: Apple USB SuperDrive
Thunderbolt Bus: iMac, Apple Inc., 41.1
Thunderbolt Device: Pegasus2-R, Promise Technology, Inc., 1, 19.2
",Jim Kelley
18991,QCOW2: Compressed images,other,other,VirtualBox 6.0.12,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
17962,Display after resize goes black,Windows,Linux,VirtualBox 5.2.18,2019-10-10T01:54:06Z,2019-10-10T01:54:06Z,"Hi,

after resizing display it goes black and VM has to be restarted. VB is running on Win10 enterprise 64bit, guest system is Ubuntu.",Zool0
18935,VirtualBox Crash When Powering Off / Shutting Down Debian VM on macOS Catalina,Mac OS X,Linux,VirtualBox 6.0.12,2019-10-10T04:48:45Z,2019-10-10T04:48:45Z,"When powering off and/or sending the shutdown signal to my Debian VM, VirtualBox crashes and leaves the VM in an 'Aborted' status. I have a Windows VM which I can shutdown/power off without any resulting VirtualBox application crash.

This is the stack trace thrown:
{{{
Process:               VirtualBoxVM [4041]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.12 (6.0.12)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [4019]
Responsible:           VirtualBox [4015]
User ID:               501

Date/Time:             2019-09-17 05:10:40.199 -0400
OS Version:            Mac OS X 10.15 (19A558d)
Report Version:        12
Anonymous UUID:        8CD22061-DD5E-08D6-5768-B3DD7D7C0AC5

Sleep/Wake UUID:       CD3BEF75-0E78-4B26-8AAB-FC908122A280

Time Awake Since Boot: 26000 seconds
Time Since Wake:       390 seconds

System Integrity Protection: enabled

Crashed Thread:        12  VMSVGA FIFO

Exception Type:        EXC_CRASH (SIGKILL)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    LIBSYSTEM, [0x2]

Application Specific Information:
assertion failure: ""((void *)0) == tsd->NSCurrentOpenGLContext"" -> %lld

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.framework.IOKit     	0x00007fff3a8eef34 io_connect_method + 383
3   com.apple.framework.IOKit     	0x00007fff3a8eed47 IOConnectCallMethod + 186
4   com.apple.framework.IOKit     	0x00007fff3a8ef629 IOConnectCallStructMethod + 35
5   com.apple.IOAccelerator       	0x00007fff5bda2d16 IOAccelGLContextClearDrawable + 50
6   libGPUSupportMercury.dylib    	0x00007fff5868f01e gldAttachDrawable + 1587
7   GLEngine                      	0x00007fff4272ce6c gliAttachDrawableWithOptions + 257
8   com.apple.opengl              	0x00007fff4270ed4d CGLClearDrawable + 116
9   com.apple.AppKit              	0x00007fff353a7f56 __32-[NSOpenGLContext clearDrawable]_block_invoke + 34
10  com.apple.AppKit              	0x00007fff34d2b726 NSPerformVisuallyAtomicChange + 132
11  com.apple.AppKit              	0x00007fff3505da9d -[NSOpenGLContext clearDrawable] + 65
12  VBoxSVGA3DObjC.dylib          	0x000000011d102821 0x11d0fe000 + 18465
13  libdispatch.dylib             	0x00007fff6ee924de _dispatch_client_callout + 8
14  libdispatch.dylib             	0x00007fff6ee9dbd3 _dispatch_main_queue_callback_4CF + 1105
15  com.apple.CoreFoundation      	0x00007fff37ac4540 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
16  com.apple.CoreFoundation      	0x00007fff37ac3c8a __CFRunLoopRun + 2370
17  com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
18  com.apple.HIToolbox           	0x00007fff36650f2d RunCurrentEventLoopInMode + 292
19  com.apple.HIToolbox           	0x00007fff36650c6d ReceiveNextEventCommon + 600
20  com.apple.HIToolbox           	0x00007fff366509f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
21  com.apple.AppKit              	0x00007fff34cfaee4 _DPSNextEvent + 990
22  com.apple.AppKit              	0x00007fff34cf9c50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
23  com.apple.AppKit              	0x00007fff34cf4395 -[NSApplication run] + 658
24  libqcocoa.dylib               	0x000000010c487eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
25  org.qt-project.QtCoreVBox     	0x00000001056d2791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
26  org.qt-project.QtCoreVBox     	0x00000001056d6b4a QCoreApplication::exec() + 346
27  VirtualBoxVM.dylib            	0x000000010539ef93 TrustedMain + 1315
28  org.virtualbox.app.VirtualBoxVM	0x0000000104ce4d36 0x104ce1000 + 15670
29  libdyld.dylib                 	0x00007fff6eee22a5 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 2:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff6f0325f6 __select + 10
1   VBoxXPCOM.dylib               	0x0000000108e7c8b0 0x108df2000 + 567472
2   VBoxXPCOM.dylib               	0x0000000108e7e6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000010db72e75 0x10db60000 + 77429
4   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 3:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 4:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dc7f221 0x10db85000 + 1024545
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6571b 0x10db60000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000010db653ed 0x10db60000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x000000010db6a039 0x10db60000 + 41017
7   VBoxXPCOM.dylib               	0x0000000108e652fd 0x108df2000 + 471805
8   VBoxXPCOM.dylib               	0x0000000108e644fb 0x108df2000 + 468219
9   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
10  VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
11  org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 7:: TimerLR
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x0000000104e6fb15 0x104d22000 + 1366805
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 8:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 9:: EMT-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec0974 SUPR3PageFreeEx + 292
4   VBoxVMM.dylib                 	0x0000000108b75df8 PGMR3PhysMMIOExDeregister + 488
5   VBoxVMM.dylib                 	0x0000000108b50aa0 0x108af9000 + 359072
6   VBoxVMM.dylib                 	0x0000000108ba438d 0x108af9000 + 701325
7   VBoxVMM.dylib                 	0x0000000108baa317 0x108af9000 + 725783
8   VBoxVMM.dylib                 	0x0000000108baa828 0x108af9000 + 727080
9   VBoxVMM.dylib                 	0x0000000108ba7623 0x108af9000 + 714275
10  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
11  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff37ac444b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff37ac39e7 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
5   com.apple.AppKit              	0x00007fff34d0251a _NSEventThread + 132
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 11:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 Crashed:: VMSVGA FIFO
0   libsystem_kernel.dylib        	0x00007fff6f031f6e __terminate_with_payload + 10
1   libsystem_kernel.dylib        	0x00007fff6f04c4ba abort_with_payload_wrapper_internal + 119
2   libsystem_kernel.dylib        	0x00007fff6f04c4c5 abort_with_payload + 9
3   libsystem_c.dylib             	0x00007fff6efb8a07 _os_crash_fmt.cold.1 + 55
4   libsystem_c.dylib             	0x00007fff6ef4b876 _os_crash_fmt + 154
5   com.apple.AppKit              	0x00007fff34ebd994 __NSAppKitFinalizeThreadData + 663
6   libsystem_pthread.dylib       	0x00007fff6f0ec413 _pthread_tsd_cleanup + 551
7   libsystem_pthread.dylib       	0x00007fff6f0ef16f _pthread_exit + 70
8   libsystem_pthread.dylib       	0x00007fff6f0ec1cc pthread_exit + 27
9   VBoxRT.dylib                  	0x0000000104ebc14a 0x104d22000 + 1679690
10  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
11  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 13:: AioMgr0-N
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108c8a66b 0x108af9000 + 1644139
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 14:: Port0
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 15:: ATA-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 16:: ATA-1
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 17:: INTNET-RECV
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ebf878 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	0x0000000113d1ad28 0x113cb0000 + 437544
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 18:: INTNET-XMIT
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 19:: AMCP Logging Spool
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 20:
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 21:: EhciFramer
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 22:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 23:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 24:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 25:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 26:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 27:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 28:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 29:
0   libsystem_kernel.dylib        	0x00007fff6f02afca semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff6ee929eb _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff6ee92e12 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff6eea0645 _dispatch_worker_thread + 318
4   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
5   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 30:: VMPwrDwn
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108baa24e VMR3ReqWait + 110
4   VBoxVMM.dylib                 	0x0000000108baa1bf VMR3ReqQueue + 623
5   VBoxVMM.dylib                 	0x0000000108baa00f VMR3ReqQueue + 191
6   VBoxVMM.dylib                 	0x0000000108ba938c VMR3ReqCallVU + 380
7   VBoxVMM.dylib                 	0x0000000108ba91d2 0x108af9000 + 721362
8   VBoxVMM.dylib                 	0x0000000108ba3cc9 VMR3Destroy + 249
9   VBoxC.dylib                   	0x000000010dbf08c3 0x10db85000 + 440515
10  VBoxC.dylib                   	0x000000010dc17047 0x10db85000 + 598087
11  VBoxC.dylib                   	0x000000010dbd510c 0x10db85000 + 327948
12  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
13  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
14  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
15  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000200  rcx: 0x0000700007a7eda8  rdx: 0x0000000000000000
  rdi: 0x0000000000000fc9  rsi: 0x0000000000000012  rbp: 0x0000700007a7edf0  rsp: 0x0000700007a7eda8
   r8: 0x0000000000000054   r9: 0x00007fea858919e0  r10: 0x0000700007a7ee60  r11: 0x0000000000000206
  r12: 0x0000000000000054  r13: 0x0000700007a7ee60  r14: 0x0000000000000002  r15: 0x0000000000000012
  rip: 0x00007fff6f031f6e  rfl: 0x0000000000000206  cr2: 0x00007fff6f0371dd
  
Logical CPU:     0
Error Code:      0x02000208
Trap Number:     133


Binary Images:
       0x104ce1000 -        0x104d02ff7 +org.virtualbox.app.VirtualBoxVM (6.0.12 - 6.0.12) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x104d22000 -        0x105282347 +VBoxRT.dylib (0) <44B42923-83C4-366C-AE1F-813AE54FEE60> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x105397000 -        0x105484ff7 +VirtualBoxVM.dylib (0) <2B18B9FF-A9BA-35AC-94F4-2EF406259714> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1054dd000 -        0x1054e6ff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x1054ef000 -        0x105a16ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x105acc000 -        0x105fa7ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10609b000 -        0x1065a4fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x106707000 -        0x10673bfff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10675f000 -        0x10679efff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x1067c1000 -        0x106814fff +VBoxDDU.dylib (0) <5DCF996A-036C-3DF7-A65F-4FDA755B5DFA> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x106820000 -        0x108956fff +VBoxGlobal.dylib (0) <66B224F5-CBE3-3D76-9DB1-A9D430E041A5> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x108af9000 -        0x108d7bfff +VBoxVMM.dylib (0) <1A356DAB-4305-30E8-84C1-579E86EEF107> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x108df2000 -        0x108ea3ff7 +VBoxXPCOM.dylib (0) <817EE585-D05F-373A-B68D-200A0C997CDF> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10a4e5000 -        0x10a4e9ff7 +VDPluginCrypt.dylib (0) <1D1D34F1-0821-34FB-8998-9888E46D6C5A> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VDPluginCrypt.dylib
       0x10a52b000 -        0x10a5b991f  dyld (732.2) <BAB55B81-E18F-3129-BD61-CC42B9F21198> /usr/lib/dyld
       0x10c465000 -        0x10c5a4fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x10db52000 -        0x10db55047  libobjc-trampolines.dylib (779) <81578FF6-5EE6-3FE5-B69F-31B977F45D58> /usr/lib/libobjc-trampolines.dylib
       0x10db60000 -        0x10db77fff +VBoxXPCOMIPCC.dylib (0) <3F5A7F5F-392A-3855-8091-EAD834051036> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x10db85000 -        0x10df7dfff +VBoxC.dylib (0) <B1A67512-FDC8-38A5-84F2-D8AA9EB23C53> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x10dfc2000 -        0x10dfc5ff7 +VBoxSVCM.dylib (0) <55D3234B-0B5B-3AED-AA2E-3F0528414687> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x10e02f000 -        0x10e031ff7 +VBoxPuelMainVM.dylib (0) <CE286393-79E4-3E6E-8922-4A933C4397E5> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMainVM.dylib
       0x10e2ab000 -        0x10e2bcffb  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <70FBC258-44BF-3C42-A997-3D0EDF27BC59> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x113171000 -        0x113194ff7 +VBoxHostWebcam.dylib (0) <17590F9F-9794-362E-8C62-578DC28C0EEC> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxHostWebcam.dylib
       0x113cb0000 -        0x113ffffff +VBoxDD.dylib (0) <94B8B3E4-5B8D-342A-9E6D-0CEDC6BBC4F5> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x114691000 -        0x1146e8ff7 +VBoxDD2.dylib (0) <8AE831BF-11EF-3DC0-B31E-BC1B6EFC13CF> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x1146ee000 -        0x1146fffff +VBoxEhciR3.dylib (0) <8EBE5D51-1BB4-39F0-99FA-2D9FD22510DD> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxEhciR3.dylib
       0x114704000 -        0x11470fff7 +VBoxNvmeR3.dylib (0) <BE5FF50A-1122-3A61-8504-FC19E2E5F988> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxNvmeR3.dylib
       0x114713000 -        0x11471ffff +VBoxUsbCardReaderR3.dylib (0) <AD3E1939-B325-3A8D-A571-A3179BB0CD32> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbCardReaderR3.dylib
       0x114722000 -        0x11472eff7 +VBoxUsbWebcamR3.dylib (0) <4CC64783-6A10-3ED0-B5C9-B759CFFAE3EB> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbWebcamR3.dylib
       0x11d0bf000 -        0x11d0f2fff +VBoxSVGA3D.dylib (0) <C997472A-A9F8-3F84-B18F-9FDFEEBC2397> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3D.dylib
       0x11d0fe000 -        0x11d104fff +VBoxSVGA3DObjC.dylib (0) <94F57D1A-3216-3E5D-90C9-5C29EAE73BD1> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3DObjC.dylib
       0x14b5f0000 -        0x14b73dff7  com.apple.audio.units.Components (1.14 - 1.14) <0CAF1178-C08B-3A0D-BE03-6D1A376CD37F> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff2b013000 -     0x7fff2b262ff8  com.apple.RawCamera.bundle (9.00.1 - 1200.22) <4E4BD2AA-ABAF-3CC3-B070-D877CA4EBEB9> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff2e758000 -     0x7fff2ec5cff7  com.apple.driver.AppleIntelBDWGraphicsGLDriver (14.0.67 - 14.0.0) <5FF8F09F-EFE6-3D81-8FB8-4DF5843665EF> /System/Library/Extensions/AppleIntelBDWGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsGLDriver
    0x7fff2ec5d000 -     0x7fff2ed5dffd  com.apple.driver.AppleIntelBDWGraphicsMTLDriver (14.0.67 - 14.0.0) <C75B3FE7-984B-3842-A18F-F97778C22FE0> /System/Library/Extensions/AppleIntelBDWGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsMTLDriver
    0x7fff3343b000 -     0x7fff3343fffb  com.apple.agl (3.3.3 - AGL-3.3.3) <EEB8C1EE-479A-3DA6-93D0-B8117D289146> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff33440000 -     0x7fff33698ffa  com.apple.avfoundation (2.0 - 1722.27.4.4) <2EFEF1B1-CDC8-38BA-BA29-0B467ED109D0> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
    0x7fff33699000 -     0x7fff33764ff8  com.apple.audio.AVFAudio (1.0 - ???) <D0AEA054-EC5B-3A92-B672-F9CA22E8EB23> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Frameworks/AVFAudio.framework/Versions/A/AVFAudio
    0x7fff33884000 -     0x7fff33884fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <229BBA70-25E1-363C-9A46-B27BD69269F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff33885000 -     0x7fff3389bff7  libCGInterfaces.dylib (524.2) <7F08322A-4AA0-3677-91CD-9D1588BDBE39> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff3389c000 -     0x7fff33f07fdf  com.apple.vImage (8.1 - 524.2) <45A48EA9-49AA-33A0-B830-AF754BD01009> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff33f08000 -     0x7fff34170fff  libBLAS.dylib (1303) <112B19CC-925A-3E28-8B32-2002D30A37FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff34171000 -     0x7fff34460fdf  libBNNS.dylib (144.11.2) <726C490D-8BDB-3488-9B5A-531F15E42259> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff34462000 -     0x7fff34807fff  libLAPACK.dylib (1303) <5C248B39-F233-3074-A3A5-AF8F436FBF87> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff34808000 -     0x7fff3481dff8  libLinearAlgebra.dylib (1303) <C21931B4-F6BD-324D-A2D9-F13EE8AFB29E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff3481e000 -     0x7fff34823ff3  libQuadrature.dylib (7) <826897ED-B7AD-33DC-B9CB-F9787784F312> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff34824000 -     0x7fff34894fff  libSparse.dylib (103) <55467C29-2096-36AB-8A6D-5231A342809D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff34895000 -     0x7fff348a7fef  libSparseBLAS.dylib (1303) <3244FCAF-A1FE-3248-AF22-BFB3E9D12555> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff348a8000 -     0x7fff34a81ffb  libvDSP.dylib (735) <EE2CBD92-EA9A-3288-B9B4-D61AA08F1114> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff34a82000 -     0x7fff34b3dfd3  libvMisc.dylib (735) <3859618E-D36E-3190-8BC8-7AF170C7A6C8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff34b3e000 -     0x7fff34b3efff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <79C1A1C7-E97A-3B7A-8737-444B402A7AA0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff34b3f000 -     0x7fff34b9dffe  com.apple.Accounts (113 - 113) <57677F31-13F3-3197-B97A-DE57BD03BFC8> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
    0x7fff34ce3000 -     0x7fff35a8eff4  com.apple.AppKit (6.9 - 1877) <9E8E14EA-7B3B-3412-A5C5-B7DC97D5FAD2> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff35ade000 -     0x7fff35adefff  com.apple.ApplicationServices (48 - 50) <981D6A76-AA72-3203-98F5-4989FF2F6058> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff35adf000 -     0x7fff35b4afff  com.apple.ApplicationServices.ATS (377 - 492) <B5739AFF-FF49-3EF7-B123-922300E3E5BE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff35be3000 -     0x7fff35c21ffa  libFontRegistry.dylib (273) <9E8A133C-1DE1-3902-A513-2D474A95CDF0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff35c7c000 -     0x7fff35cabff7  com.apple.ATSUI (1.0 - 1) <9391C527-15CE-3108-8922-CF0C2A50C082> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
    0x7fff35cac000 -     0x7fff35cb0ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <EBA4F56C-3C82-3788-A168-3E77E116724B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff35d4b000 -     0x7fff35da1ff2  com.apple.HIServices (1.22 - 671) <E744DE5F-F775-3BFA-BBCB-4D38ADFCAA2A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff35da2000 -     0x7fff35db0fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <02AE4AE3-1CD9-3193-B5F3-2C1C6D435F18> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff35db1000 -     0x7fff35df6ff2  com.apple.print.framework.PrintCore (15 - 516) <43213BE5-C5E1-3AA8-8AFD-949AFF9FB2C5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff35df7000 -     0x7fff35e01fff  com.apple.QD (4.0 - 413) <EFC01D3C-9012-3FCF-9149-457F530A43F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff35e02000 -     0x7fff35e0fff0  com.apple.speech.synthesis.framework (9.0.20 - 9.0.20) <A5CCADE3-B307-3FAD-A7E8-A77DDFF026CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff35e10000 -     0x7fff35eddff2  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <1961714B-4533-3C6E-836C-1C73511EF4D3> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff35edf000 -     0x7fff35edffff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <4CD694DA-A074-3BC0-BB50-724D16345F18> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff36255000 -     0x7fff365cbffe  com.apple.CFNetwork (1110 - 1110) <EC97BFD7-8745-30F4-9DB4-FD8281C84CC9> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff36641000 -     0x7fff36641fff  com.apple.Carbon (160 - 162) <09CEF7B7-0113-32C3-A3DF-4177A1CFD97C> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff36642000 -     0x7fff36645ffb  com.apple.CommonPanels (1.2.6 - 101) <930A9DD4-B4BF-3D73-8B81-2D46018BB2E4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff36646000 -     0x7fff3693affc  com.apple.HIToolbox (2.1.1 - 987.1) <2AD583EF-7EB9-3EFB-BA74-D230BE62F0CC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff3693b000 -     0x7fff3693eff3  com.apple.help (1.3.8 - 68) <CA52ABA0-636A-39AA-98C0-A1B901A5F4F4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff3693f000 -     0x7fff36944ff7  com.apple.ImageCapture (9.0 - 1600.1) <D4515843-F958-3910-A738-576FD43D3C78> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff36945000 -     0x7fff36945fff  com.apple.ink.framework (10.15 - 227) <BA11FA6C-AEAA-3688-8812-9CA16EA11D03> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff36946000 -     0x7fff36960ff2  com.apple.openscripting (1.7 - 185) <7CFD4E50-FD41-39C7-BA76-6BA260BD91F9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff36981000 -     0x7fff36981fff  com.apple.print.framework.Print (15 - 271) <CB0E6F07-19E3-3207-9B7B-267F04DF6F73> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff36982000 -     0x7fff36984ff7  com.apple.securityhi (9.0 - 55008) <E8AE6A05-5F07-3300-9FEA-8C29C0B45566> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff36985000 -     0x7fff3698bff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <819268CF-2A9D-3321-A826-535CB1F1E694> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff36b25000 -     0x7fff36b25fff  com.apple.Cocoa (6.11 - 23) <F8489AB5-835B-3637-B8A1-64FCF8AB5F7A> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff36b33000 -     0x7fff36d1eff7  com.apple.ColorSync (4.13.0 - 3394.1.4.1) <32A1AEE9-C3AA-3535-9C72-D89955D2DE85> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff3700a000 -     0x7fff37519ffa  com.apple.audio.CoreAudio (5.0 - 5.0) <7A785340-4CE5-3130-94AB-DFA51C69A4E7> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff3756c000 -     0x7fff375a3ff2  com.apple.CoreBluetooth (1.0 - 1) <6767CD70-533B-3114-9F9E-733B9E72C828> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff375a4000 -     0x7fff3797efe8  com.apple.CoreData (120 - 969.2) <BFA70A01-DC83-3A1A-A7DE-8DFEB4269304> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff3797f000 -     0x7fff37a88ffe  com.apple.CoreDisplay (1.0 - 107) <91C74B12-4357-3717-B00B-A21DD0C722CE> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff37a89000 -     0x7fff37f08fff  com.apple.CoreFoundation (6.9 - 1671.12) <6500A498-7434-3C1C-A9EB-1FDB75CB2CC1> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff37f0a000 -     0x7fff38582ff0  com.apple.CoreGraphics (2.0 - 1348.4.4.3) <E16AE614-C7B6-3DC4-904D-B130C7B9CF72> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff38590000 -     0x7fff388ebffe  com.apple.CoreImage (15.0.0 - 900.4) <63DB7953-3DD0-3CA2-9709-68A9A09837B0> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff38caa000 -     0x7fff38e1aff4  com.apple.CoreMedia (1.0 - 2501.27.4.3) <056F96CA-82E5-3DD0-97D8-A700F12D16BB> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff38e1b000 -     0x7fff38e7cff6  com.apple.CoreMediaIO (1000.0 - 5125.1) <70E47B45-B017-3893-97E4-E72729A4F936> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
    0x7fff38f03000 -     0x7fff38f03fff  com.apple.CoreServices (1068.2 - 1068.2) <46CA4F06-5983-3D08-B972-1382381CDAC1> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff38f04000 -     0x7fff38f87ff7  com.apple.AE (836 - 836) <E65EB197-5D66-3EBC-BCA0-A9D8B4F6EC2B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff38f88000 -     0x7fff39269fff  com.apple.CoreServices.CarbonCore (1216 - 1216) <FCE3A1CF-EE79-3FF7-A12F-8AFF74607E8A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff3926a000 -     0x7fff392b7ff1  com.apple.DictionaryServices (1.2 - 321) <648A5391-99DC-3AD1-B68A-9EB26AED62C1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff392b8000 -     0x7fff392c0ff7  com.apple.CoreServices.FSEvents (1268.0.6 - 1268.0.6) <78D2AB1A-9053-3D32-8C18-C1DD31FF9400> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff392c1000 -     0x7fff394f8ffd  com.apple.LaunchServices (1068.2 - 1068.2) <DCB37CF3-15A4-3A97-94B9-7EC6788BAEB7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff394f9000 -     0x7fff39591ff9  com.apple.Metadata (10.7.0 - 2064.1) <A8603546-69B1-39C4-B4D5-83F2E21013D9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff39592000 -     0x7fff395bfff7  com.apple.CoreServices.OSServices (1068.2 - 1068.2) <CB16982C-826A-3444-BCDB-754E48EFEA6E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff395c0000 -     0x7fff39627fff  com.apple.SearchKit (1.4.1 - 1.4.1) <0068BD72-CF2B-34E4-B461-002D5E56C31C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff39628000 -     0x7fff3964cffd  com.apple.coreservices.SharedFileList (130 - 130) <F55A2C27-F648-3608-8B71-43E8EC225F2E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff39972000 -     0x7fff39b25ff6  com.apple.CoreText (643.1 - 643.1) <02D49B30-84A8-32E0-9DD5-06E304B0D498> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff39b26000 -     0x7fff39b6afff  com.apple.CoreVideo (1.8 - 334.0) <54CC4AD8-7F5C-37D5-A26D-9C8C8A72BD41> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff39b6b000 -     0x7fff39bf8ff1  com.apple.framework.CoreWLAN (13.0 - 1448) <2894EC6A-F29E-393F-9105-7436B83C2E57> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff39dc2000 -     0x7fff39dcdff7  com.apple.DirectoryService.Framework (10.15 - 220.11.1) <EADC285E-3166-3474-915B-F905F840D19E> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
    0x7fff39dce000 -     0x7fff39e79ff0  com.apple.DiscRecording (9.0.3 - 9030.4.5) <6F1FE0D6-907E-3309-A53E-B4B01F9355E5> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff39e9e000 -     0x7fff39ea4ff7  com.apple.DiskArbitration (2.7 - 2.7) <23104F29-F120-354B-97BE-4514A675BB14> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff3a097000 -     0x7fff3a1b9ff3  com.apple.FileProvider (252 - 252) <FEF218FA-EAEA-32C5-82DB-5B3843FB7446> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
    0x7fff3a1d1000 -     0x7fff3a598ff3  com.apple.Foundation (6.9 - 1671.12) <D1CCD387-08E0-338D-B93D-C3BA470CE727> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff3a605000 -     0x7fff3a634ff3  com.apple.GSS (4.0 - 2.0) <9520F096-C643-36D7-B8CB-3922B6E6D7EC> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff3a76a000 -     0x7fff3a882ffd  com.apple.Bluetooth (7.0.0 - 7.0.0f4) <D130CB4B-1350-3278-8D3F-A11114A996DC> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff3a8e6000 -     0x7fff3a989ff3  com.apple.framework.IOKit (2.0.2 - 1726.0.14) <E23D2220-479C-3DCC-8CF5-A9A6B497ECE4> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff3a98b000 -     0x7fff3a99bff4  com.apple.IOSurface (269.6 - 269.6) <1E49AD7D-6067-3599-B015-765047D58C13> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff3aa0e000 -     0x7fff3ab69fee  com.apple.ImageIO.framework (3.3.0 - 1972.3.4.2) <9770B095-F95D-328B-A1DE-6978C434ABA0> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff3ab6a000 -     0x7fff3ab6dfff  libGIF.dylib (1972.3.4.2) <F89D4FB5-AFA1-3617-B740-D148B5D635A1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff3ab6e000 -     0x7fff3ac28fe7  libJP2.dylib (1972.3.4.2) <33CC7F2A-1E5A-3302-8A96-0C8EA38E5F90> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff3ac29000 -     0x7fff3ac4dfef  libJPEG.dylib (1972.3.4.2) <FA7B791A-9F06-30B7-917F-94E022A2AE20> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff3aecb000 -     0x7fff3aee5fe7  libPng.dylib (1972.3.4.2) <576BD7D2-FCBF-31AB-BCB3-8935AD9CAD2C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff3aee6000 -     0x7fff3aee7fff  libRadiance.dylib (1972.3.4.2) <06F8438E-10A6-3D6D-BC00-AB49CD5CE602> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff3aee8000 -     0x7fff3af31fef  libTIFF.dylib (1972.3.4.2) <5535A3DB-501F-36B0-830E-108684CFA4DA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff3c34a000 -     0x7fff3c35cff3  com.apple.Kerberos (3.0 - 1) <91DF5D16-E721-39F0-A77B-87DA6032F870> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff3c35d000 -     0x7fff3c35dfff  libHeimdalProxy.dylib (77) <51DB9CFB-808F-32E8-BB34-39F6702DBDED> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
    0x7fff3c35e000 -     0x7fff3c394fff  com.apple.LDAPFramework (2.4.28 - 194.5) <32FAF82F-BA91-366A-83A3-CDFF6CDD1AF9> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff3c6ee000 -     0x7fff3c6f8fff  com.apple.MediaAccessibility (1.0 - 125) <DAF5DD8F-A725-320E-8D7E-2C39CBE33F44> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff3c7c1000 -     0x7fff3d287ffb  com.apple.MediaToolbox (1.0 - 2501.27.4.3) <1BA60E69-C647-3073-850A-BDC3DAD01BC8> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff3d289000 -     0x7fff3d34bff1  com.apple.Metal (211.53 - 211.53) <EA59DEFD-F6DD-3DC5-9E6F-8152CD5F121C> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3d368000 -     0x7fff3d3a4ff3  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <54EC6486-7A3E-39D3-B213-EFCC4110E511> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff3d3a5000 -     0x7fff3d42bfe6  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <144A9994-9AD3-340D-A890-C7F10DDEF489> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3d42c000 -     0x7fff3d451ff0  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <6F07D520-B36C-38D5-810B-A95BA5F79B04> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff3d452000 -     0x7fff3d467ffc  com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <73DBE1D5-89C4-3410-95DA-A384BF9C2C1E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
    0x7fff3d468000 -     0x7fff3d5c7ff4  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <24338B34-481D-3564-917C-CD1DB243FD12> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff3d5c8000 -     0x7fff3d616ff7  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <75ABA9EB-752E-3E7E-BFBA-19806FB65924> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff3d617000 -     0x7fff3d618ff5  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <5EA47648-76E9-37CD-A2FC-A0083A769665> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff3e55e000 -     0x7fff3e56affe  com.apple.NetFS (6.0 - 4.0) <10ECF7E4-98A5-3751-B7AC-0AAAF0050777> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff3e56b000 -     0x7fff3e6aeff6  com.apple.Network (1.0 - 1) <5C29B0D5-3811-32A8-9FF4-CA112F9526F4> /System/Library/Frameworks/Network.framework/Versions/A/Network
    0x7fff410cc000 -     0x7fff410d4fff  libcldcpuengine.dylib (2.12.7) <A9ECDF96-4888-35CB-9BEF-96D8A84E5106> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
    0x7fff410d5000 -     0x7fff4112dff7  com.apple.opencl (3.5 - 3.5) <0F4232DF-854F-3852-8881-D48FF303D4D3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff4112e000 -     0x7fff4114afff  com.apple.CFOpenDirectory (10.15 - 220.11.1) <90901E88-47DC-3DDA-AF53-FD0A0B22078A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff4114b000 -     0x7fff41156fff  com.apple.OpenDirectory (10.15 - 220.11.1) <5AAE71B0-892A-3813-BDCF-C364B61D500B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff41ab1000 -     0x7fff41ab3fff  libCVMSPluginSupport.dylib (17.10.22) <026644DF-3221-3AB0-8DA9-DA9B56A8B38D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff41ab4000 -     0x7fff41ab9fff  libCoreFSCache.dylib (176.7) <A10565BE-6728-3BCA-9A9A-095CC09A5F25> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff41aba000 -     0x7fff41abefff  libCoreVMClient.dylib (176.7) <DF6A2BF6-7775-3ED8-B425-772499BE2BB7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff41abf000 -     0x7fff41ac7ff7  libGFXShared.dylib (17.10.22) <2DBB6DC3-4027-3A0E-AEA7-809399CFFEFA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff41ac8000 -     0x7fff41ad2fff  libGL.dylib (17.10.22) <95746D0C-9347-37C0-88E2-6BA4A3584816> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff41ad3000 -     0x7fff41b08fff  libGLImage.dylib (17.10.22) <B8EE902C-6692-3E32-949B-C193AC944D31> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff41b09000 -     0x7fff41c9bff7  libGLProgrammability.dylib (17.10.22) <02CCAAE9-9B38-352C-A854-026D02ABB7E9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
    0x7fff41c9c000 -     0x7fff41cd8fff  libGLU.dylib (17.10.22) <43DADBAD-9F65-33CE-94DA-654F24817313> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff42708000 -     0x7fff42717ff7  com.apple.opengl (17.10.22 - 17.10.22) <C3E682E0-413B-3134-9107-C45B897E8CDA> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff42718000 -     0x7fff42891ff7  GLEngine (17.10.22) <B67C43C3-77C1-3233-98F5-A5062B14FE70> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine
    0x7fff42892000 -     0x7fff428bafff  GLRendererFloat (17.10.22) <DA488EF2-6318-3376-8616-26CE79640666> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
    0x7fff436c7000 -     0x7fff43944ff7  com.apple.QuartzCore (1.11 - 815.6.4.2) <0459F92C-5C1C-3B32-BCE8-9526AF5BC8D1> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff444cf000 -     0x7fff44812ff1  com.apple.security (7.0 - 59306.11.12) <54D99D96-7E50-3EEA-BCB3-7E73973B131C> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff44813000 -     0x7fff4489bff7  com.apple.securityfoundation (6.0 - 55236) <A1B5CC71-E988-3529-AA03-539C02340DAD> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff448ca000 -     0x7fff448ceff8  com.apple.xpc.ServiceManagement (1.0 - 1) <EF42F840-AF78-38A4-B6E1-FDF445CA3477> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff456bc000 -     0x7fff45726ff7  com.apple.SystemConfiguration (1.19 - 1.19) <C0C089C3-FC64-3107-B23E-4073E800C5D2> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff459a2000 -     0x7fff45d49ff1  com.apple.VideoToolbox (1.0 - 2501.27.4.3) <522DF280-7ADE-3467-B4EE-06B7ED84C1F2> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff494bf000 -     0x7fff49583ff7  com.apple.APFS (1412.11.4 - 1412.11.4) <B66C6042-E929-3A33-83A0-9199E132FE1E> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff49d3c000 -     0x7fff49d44ff6  com.apple.AccessibilityBundles (1.0 - 128) <242ACD03-D41C-38AA-AEB5-D0EC462C548E> /System/Library/PrivateFrameworks/AccessibilityBundles.framework/Versions/A/AccessibilityBundles
    0x7fff4a5b4000 -     0x7fff4a5b5ff1  com.apple.AggregateDictionary (1.0 - 1) <92777CAE-3C90-39A4-A8AE-0273A262F875> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff4a93f000 -     0x7fff4a95bff2  com.apple.AppContainer (4.0 - 448.0.3) <EFE68289-FFE6-3453-89AF-E637CD47A2D0> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
    0x7fff4a9af000 -     0x7fff4a9bdff7  com.apple.AppSandbox (4.0 - 448.0.3) <1E6E9594-4988-32EC-86C2-CDDA7DBB7E66> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
    0x7fff4ae3f000 -     0x7fff4ae63ff3  com.apple.framework.Apple80211 (13.0 - 1453) <C355D394-9489-3C14-856C-A4818B003FE1> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff4af97000 -     0x7fff4afa6fdf  com.apple.AppleFSCompression (119 - 1.0) <725908C4-7585-3AB6-8A1A-691B8A9074B8> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff4b0a5000 -     0x7fff4b0b0ff7  com.apple.AppleIDAuthSupport (1.0 - 1) <6BD125A5-9820-3176-AB79-8B612CCD6956> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff4b0f2000 -     0x7fff4b13afff  com.apple.AppleJPEG (1.0 - 1) <8051B4A3-7658-3003-82D1-41CA5C83CBEC> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff4b50e000 -     0x7fff4b512ff7  com.apple.AppleSRP (5.0 - 1) <B251E119-3F06-3CDB-9559-8CC8BBAF1529> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
    0x7fff4b513000 -     0x7fff4b535ffb  com.apple.applesauce (1.0 - 16.22) <88BFDA72-8D13-3481-B4FA-62215F6E2E43> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff4b5f5000 -     0x7fff4b5f8fff  com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <AF8A3953-4D1A-38C2-B38D-1E21F326B0C7> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
    0x7fff4b5f9000 -     0x7fff4b649ff7  com.apple.AppleVAFramework (6.1.2 - 6.1.2) <282CA618-1F44-3160-9078-B48D70AEDE36> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff4b692000 -     0x7fff4b6a1ffd  com.apple.AssertionServices (1.0 - 223.11.1) <8A45663E-E9C8-3611-BD4C-710700920F14> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff4bbd3000 -     0x7fff4bfd1ff4  com.apple.audio.AudioResourceArbitration (1.0 - 1) <2639564C-1435-3DA2-A0CB-F288617219BC> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration
    0x7fff4c110000 -     0x7fff4c161ffd  com.apple.audio.AudioSession (1.0 - 17) <627167E8-D05D-3851-A5E5-FBA38C8E72D3> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
    0x7fff4c162000 -     0x7fff4c18fff7  libSessionUtility.dylib (17) <28EC4408-4F7C-3C73-A9E2-AD976BE1C1D4> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
    0x7fff4c228000 -     0x7fff4c45dff7  com.apple.audio.AudioToolboxCore (1.0 - 1104.14) <4591B856-C8D0-3FFD-B783-70707D18E91A> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
    0x7fff4c45e000 -     0x7fff4c576ff8  com.apple.AuthKit (1.0 - 1) <2650CED9-1F9F-3C76-A6B9-B0589F986830> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff4c72c000 -     0x7fff4c735ff3  com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <42FAB6B3-D02C-3264-9066-2B81DC62A529> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff4c736000 -     0x7fff4c7d7ff8  com.apple.backup.framework (1.11 - 1296.1) <B6B83178-3F01-3DCB-BC72-70F8F6BCFAD8> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff4c7d8000 -     0x7fff4c857fff  com.apple.BaseBoard (460 - 460) <E2B2C09D-7CA3-3BCF-AE84-E636CBC139CB> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff4c957000 -     0x7fff4c993ff7  com.apple.bom (14.0 - 219) <1AFE57DF-F512-39A7-9C53-1AF0490D38BB> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff4d4fe000 -     0x7fff4d54dfff  com.apple.ChunkingLibrary (302 - 302) <157DF88D-CCA1-3431-AB8F-E8B7A62D652C> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff4e3d2000 -     0x7fff4e3dbff7  com.apple.CommonAuth (4.0 - 2.0) <BDE39131-6389-3243-9C4A-DBA165B8A2F9> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff4e3ef000 -     0x7fff4e406ff1  com.apple.commonutilities (8.0 - 900) <A64C20B3-6860-3CCA-BB89-E8B9B589282A> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
    0x7fff4eae5000 -     0x7fff4eebafc8  com.apple.CoreAUC (280.0.0 - 280.0.0) <4D5184AB-F60A-3C95-82C1-A283FB15C072> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x7fff4eebb000 -     0x7fff4eee9ffb  com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B7C10F1C-B3DE-3F2C-B2B8-1CD37DA7298F> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
    0x7fff4ef0b000 -     0x7fff4ef2aff4  com.apple.analyticsd (1.0 - 1) <A712828F-84FB-302B-BAA8-D2776AB623EB> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
    0x7fff4f1f2000 -     0x7fff4f1fdff7  com.apple.frameworks.CoreDaemon (1.3 - 1.3) <76AC1239-46B1-387E-B053-ED56BDF55DE7> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
    0x7fff4f473000 -     0x7fff4f483ff3  com.apple.CoreEmoji (1.0 - 100) <9AB89183-635C-3859-9DC6-7BCE3A94D15E> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff4facf000 -     0x7fff4fb39ff8  com.apple.CoreNLP (1.0 - 211) <8F08AEF6-A380-3811-BAF0-D80E7C84B5AD> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
    0x7fff4ff9f000 -     0x7fff4ffa7ff8  com.apple.CorePhoneNumbers (1.0 - 1) <0C242322-DB33-3764-9B44-74FA00AA3702> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff506f1000 -     0x7fff50714fff  com.apple.CoreSVG (1.0 - 129) <1716AD1F-A94F-309D-9598-C7B65F5965A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
    0x7fff50715000 -     0x7fff50748ff7  com.apple.CoreServicesInternal (446.1 - 446.1) <D5620418-A66F-300B-BE02-6254206C6B3E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff50749000 -     0x7fff50777ff7  com.apple.CSStore (1068.2 - 1068.2) <C8AEEE68-B040-39B9-9B52-6496497B19A8> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
    0x7fff50c72000 -     0x7fff50cf9fff  com.apple.CoreSymbolication (11.0 - 64509.98.1) <2E90AD17-CEAC-3AE8-A960-DA83D3F3A071> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff50d91000 -     0x7fff50ebdff4  com.apple.coreui (2.1 - 605) <74EF8323-1769-3BF8-A0F3-30A89E5B8454> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff50ebe000 -     0x7fff5105cffd  com.apple.CoreUtils (6.0 - 600.30) <60C366EC-D7C4-300A-B794-12D84952D6B6> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff51190000 -     0x7fff511a3ff1  com.apple.CrashReporterSupport (10.13 - 15010) <94F94549-D6F8-35A5-8FEE-026E079C3B2C> /System/Library/PrivateFrameworks/C",dfuentes
18998,Very laggy performance on MacOSX Mojave host caused display scaling setting,Mac OS X,Windows,VirtualBox 6.0.12,2019-10-10T05:02:50Z,2019-10-10T05:02:50Z,"Host: MacOSX Mojave 10.14.6
Guest: Windows 10 Pro
VirtualBox: 6.0.12 r133076 (Qt5.6.3)

On host if set display scale to smaller font and set scale to 200% or 300% then guest Windows OS going very slow. If I click button h then it printing hhhhh. 
I set host's display setting to biggest font scale and VB scale to 100% then it is working better.",Almas
18999,openSUSE install links broken,Linux,Linux,VirtualBox 6.0.12,2019-10-10T13:29:11Z,2019-10-10T13:29:11Z,"Following the instructions and links on https://www.virtualbox.org/wiki/Linux_Downloads (OpenSUSE) section and it appears the links do not point to the appropriate files on your servers. 

The following terminal output showing errors below:

peter@localhost:~> sudo rpm --import oracle_vbox.asc

[sudo] password for root:
 
peter@localhost:~> wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -
error: -: import read failed(0).

peter@localhost:~> zypper refresh

Root privileges are required to run this command.

peter@localhost:~> sudo zypper refresh

Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.
                                                    
Repository 'openSUSE-Tumbleweed-Oss' is up to date.
                                                        
Repository 'openSUSE-Tumbleweed-Update' is up to date.
                                                     
Retrieving repository 'VirtualBox for openSUSE 20191004 - x86_64' metadata .........................[error]

Repository 'VirtualBox for openSUSE 20191004 - x86_64' is invalid.

[virtualbox|http://download.virtualbox.org/virtualbox/rpm/opensuse/20191004/x86_64] Valid metadata not found at specified URL

Please check if the URIs defined for this repository are pointing to a valid repository.

Skipping repository 'VirtualBox for openSUSE 20191004 - x86_64' because of the above error.

Some of the repositories have not been refreshed because of an error.

peter@localhost:~> ^C

peter@localhost:~>

Another problem for noobs is the error in instruction missing the ""sudo"" root user authority - easy to correct this one as terminal gives the correct advice. (""instruction to run zypper refresh"")

I cannot find any advice on how the following can be implemented ""Users of openSUSE can add  the openSUSE repo file to /etc/zypp/repos.d/."" How is this done and where? This needs more instruction please.



",ozfossil
19014,Imported OVA with SATA controller unbootable in BIOS mode,Linux,Solaris,VirtualBox 6.0.12,2019-10-14T18:21:06Z,2019-10-14T18:21:06Z,"'''Steps to reproduce:'''

1. Import OVA/OVF template with following entry for disk controller:

{{{
<Item>
<rasd:Description>SATA Controller</rasd:Description>
<rasd:Caption>sataController0</rasd:Caption>
<rasd:InstanceID>4</rasd:InstanceID>
<rasd:ResourceType>20</rasd:ResourceType>
<rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
<rasd:Address>0</rasd:Address>
<rasd:BusNumber>0</rasd:BusNumber>
</Item>
}}}

2. Try to boot...

'''Expected:'''

System booted up.

'''Actually'''

Got weird behavior -- on first boot strange error appears,
on second boot system freezes after passing GRUB.
Sometimes after several reboots system is booted.

'''Workaround'''
Seems it's similar to #6984.

SATA controller is created with port count equal to 30.
If port count is set to 1, system boots up flawlessly.

Also when SATA controlled is removed via VirtualBox UI,
and new is one added to the system, it's port count is 0.

Tested with Fedora 30. Screenshot attached.",Roman Valov
19017,Updated to 5.2.34 and now VM constantly crashes,Windows,other,VirtualBox 5.2.34,2019-10-16T03:29:55Z,2019-10-16T03:29:55Z,"See attached log.

This is running Win9x DOS and using dos network support.
",dfatvb
19012,VERR_CFGM_VALUE_NOT_FOUND on boot.,Windows,other,VirtualBox 6.0.12,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
19013,VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2),Windows,Linux,VirtualBox 6.0.12,2019-10-16T03:40:36Z,2019-10-16T03:40:36Z,"I am using VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2)  installed on windows 10 64 bit and my host oracle linux 6.6 x86_64.
here problem is view ( resizing windows is not working in full screen).

kindly ! provide me solution ",gaurav12
19024,Virtualbox Installer launches Virtualbox with non-quoted command line - Windows hosts,Windows,all,VirtualBox 6.0.14,2019-10-16T18:16:34Z,2019-10-16T18:16:34Z,"At the end of the Virtualbox installer, the option is presented by default to start the main Virtualbox window. If there is a program called 'program' or 'program.exe' in the C drive root, that program launches instead of the main Virtualbox window.

This issue is ultimately a Windows issue, but the Virtualbox installer is run with admin privileges (asks for UAC elevate during the install, or is started right-click-run-as-admin), and the subsequent main Virtualbox windows is also launched with admin privileges. (Running the main Virtualbox window with admin privileges is required to install the Extension pack, for example.)

If C:\program or C:\program.exe exists, then 'program' is launched with admin privileges at the end of the Virtualbox installer, instead of the main Virtualbox window.

Is it possible to put double quotes around the command line to launch the main Virtualbox window in the MSI installer? Double-quotes will not launch C:\program or C:\program.exe.

See https://forums.virtualbox.org/viewtopic.php?f=6&t=95156",scottgus1
19027,iSCSI-attached disks of size 0 or which cannot be read lead to VBoxSVC going into a 100% CPU loop,other,BSD,VirtualBox 5.2.34,2019-10-18T15:00:56Z,2019-10-18T15:00:56Z,"Scenario 1:
- FreeBSD 12.0 as iSCSI server (machine A), exporting several block devices
- Misconfiguration results in these devices being exported with size 0 (reason in this case: the blocksize argument in /dev/ctl.conf was missing and needed to reflect the underlying device block size of 4096)
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Scenario 2:
- Linux openSUSE Leap 15.1 as iSCSI server (machine B), exporting a block device
- Firewall misconfiguration leads to read failures when accessing the exported device
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Result (both scenarios):
- On machine C, VBoxSVC goes into a tight loop retrying accesses to these devices
- All running VirtualBox client instances hang, including those not accessing the misconfigured iSCSI exports
- On a multiprocessor system, VBoxSVC uses n x 100% CPU (don't know how n happens, probably the number of concurrently running clients)

Expected result:
- The error should be treated reasonably, probably forwarded to the client (as a read error of the device)

Note:
- The same issue also happened with earlier releases.
",wonko1953
18562,guest screen flickering by 3d acceleration on,Linux,Windows,VirtualBox 6.0.4,2019-10-19T00:31:46Z,2019-10-19T00:31:46Z,"Hello,
My Windows 10 guest screen of apps in Ubuntu-18.04 host shows flickering and/or overlapping.
- Flickering 3~5 times while the tile menu brings up by clicking Start button
- Overlapping top-left area of a window especially graphical apps, e.g. youtube, web browser
I did many googling and reading virtual box forums with similar issues and solutions but no effect for me.
- Turning 3d acceleration off is a solution but drawing is too slow!
- export CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 in /etc/profile.d/my-cr-test.sh - no effect
- replace /usr/lib/virtualbox/VBoxOGLrenderspu.so with compiled one from source codes - no effect
My hardware and software:
  - AMD Ryzen 5 2600 16GB: Ubuntu 18.04.2 LTS
  - NVIDIA GeForce GTX 1050 2GB: nvidia-driver-418  
Please check it.
  ",siriusjt
17509,Add ArcaOS as IBM OS/2 Version Type,other,other,VirtualBox 5.2.6,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
19026,Windows sleep breaks network hotplugging,Windows,Linux,VirtualBox 6.0.12,2019-10-19T00:50:00Z,2019-10-19T00:50:00Z,"I have a windows 10 host system with archlinux as guest. Both operate using virtualbox 6.0.12.

In virtualbox, I have set up two network interfaces
1. Bridge 
2. Host only adapter


The network bridge usually operates either on a USB-C docking station or the laptops own network interface depending on where I am working.
So far, changing the bridges' interface (docking station vs built-in) seems to work fine. However, if I meanwhile put the windows asleep, e.g., through closing its lid it seems to break.

Here is what I mean with break:
The bridge network (when connected to either the docking station or the built-in adapter) obtains an IP from a DHCP which offers IPs in range 172.28.0.0/16.
If the above mentioned problem occurs (putting windows asleep and changing the bridge's interface e.g. from docking station to built-in or the other way around). The linux interface is not able to obtain an IP (it seems to default to an IP starting with 169.xxxx) and also restarting the dhcp client does not change this. The only thing that seems to work is to shutdown and start the VM again.",bomvir
18751,Very low upload throuput in NAT adapter - Windows 10 x64 1903 host/guest,Windows,Windows,VirtualBox 6.0.8,2019-10-20T23:57:16Z,2019-10-20T23:57:16Z,"Virtualbox 6.0.8+Extensions+VBoxGuestAdditions

Upload throuput using NAT is so extremaly bad, as compared to what Bridged provides, that I wonder if a bug could be there.

Full details explained here https://forums.virtualbox.org/viewtopic.php?f=2&t=93707

As workaround I switch on/off one or the other interface in the guest.",caspertone2003
19009,Switching Graphics Controller needs reinstalling Guest Additions,Mac OS X,Windows,VirtualBox 6.0.12,2019-10-21T06:07:06Z,2019-10-21T06:07:06Z,"After switching graphics controller from VBoxVGA to VBoxSVGA, it works but laggy. I found that reinstalling Guest Additions makes it smooth again. Maybe some modules are missing when Guest Additions are installed previously. It would be better to be notified that fact or even not to need to reinstall Guest Additions.",sjchoi
19011,Right screen buttons etc,Windows,other,VirtualBox 6.0.12,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
19032,bad display of IE,other,other,VirtualBox 6.0.14,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
18308,Aero/transparency on Windows Vista no longer working with VirtualBox 6.0.0 r127566,Windows,Windows,VirtualBox 6.0.0,2019-10-21T21:02:58Z,2019-10-21T21:02:58Z,"I performed the following steps:
* On my Windows 10 Professional (version 1809, build 17763.253) host, I upgraded VirtualBox 5.2.22 to 6.0.0 r127566
* In an exisiting Windows Vista Ultimate guest, upgraded VirtualBox Guest Additions from 5.2.22 to 6.0.0. 
* During the Guest Additions upgrade, as before, I selected experimental 3D accelleration and chose ""no"" when asked if I wanted basic Direct3D support.
* Restarted the guest when prompted.

After these steps: 
* Aero/transparency effects no longer work in the Vista guest (and Aero is no longer offered as an option within Windows Vista) where they did with VirtualBox 5.2.22 and earlier 5.2 versions.
* The VBox.log indicates that 3D is enabled and available, and contains no apparent indications of errors.",Rutger van Bergen
19035,Linux client can't use second monitor via Remote Desktop,Windows,Linux,VirtualBox 6.0.14,2019-10-22T11:32:34Z,2019-10-22T11:32:34Z,"I have the following setup, which I give in full here in case it has some influence in the problem:
The physical workstation ""One"" is a Devuan/XFCE based Laptop with two external 1920x1080 monitors connected.
The physical workstation ""Two"" is a Windows 10 box somewhere far away.

On ""One"" I have a virtualbox 6.0.14 with a Windows 10 guest ""v1"" running. ""v1"" uses the two external monitors in full screen display  and connects via VPN and Remote Desktop Connection to ""Two"".

On ""Two"" I have a virtualbox 6.0.14 with a Devuan XFCE MV ""v2"" running. ""v2 is supposed to use both displays of the remote desktop connection, which are rendered on the two external monitors of ""One"".

What happens is that I do have both full screen displays of ""Two"" on the external monitors of ""One"" used by ""v1"", but ""v2"" only ever opens monitor 1. I did manage to get a small window for the second display once or twice by playing around with the view parameters for a long time, but as soon as I try to maximize it the window folds to never appear again. The ""Display"" settings inside ""v2"" only show me ""Virtual1"" monitor available.

I have attached the two screenshots made from ""One"". ""screen1"" shows the display of ""v2"" inside the remote desktop from ""v1"" to ""Two"", so on top there is the menubar from ""v1"" (in Spanish), at the bottom the menu bar from ""v2"" (in German). Please ignore the content of the target desktop. ""screen2"" shows the empty second monitor from ""Two"" via remote desktop from ""v1"", so it only has the ""v1"" menu bar on top and the windows background of ""Two"". What I expected to see there was the second full screen display of ""v2"", because that is the machine I di the actual work on, so I need both displays there.


Log from v2 attached, as soon as I find out how attaching files work.

",nubaltec
19038,"Windows 10 VirtualBox uninstallation required for 6.0.12, or application within VM crashes.",Windows,Windows,VirtualBox 6.0.12,2019-10-22T17:14:21Z,2019-10-22T17:14:21Z,"Submitted for third-party in order to document rare issue encountered by a third party.

Third-party virtualizes a physical classroom disk image with VirtualBox for portability, deployment, and testing, and has done so for years.

A recent upgrade from 6.0.10 to 6.0.12 caused a commercial application within the VM to crash when accessing HTML files. We determined that UNINSTALLING 6.0.10 and then conducting a fresh installation of 6.0.12 solved this application crash, so something is not being uninstalled properly during the upgrade process.

I apologize for the lack of log files. Third party encountered this bug on a production machine and deadlines prevented retrieval of additional troubleshooting assistance. 6.0.12 was already uninstalled and 6.0.14 freshly installed, without issue.",.
19040,ubuntu 16 guest aborted when restoring,Windows,Linux,VirtualBox 6.0.14,2019-10-23T01:03:01Z,2019-10-23T01:03:01Z,"How to produce:
1. Open VirtualBox;
2. select the saved machine ""ubuntu-16"", and click ""start"" button;
3. New vm window comes up and then loading is processing;
4. when the progress bar almost finished the vm disappeared and aborted 

Host OS: Windows 7 SP1
I've been experienced this aborted situation since upgrade my virtualbox was upgraded to version 6, hope the information I've provided is helpful.",buffy
19046,"No Ubuntu 19.10 ""eoan"" packages",Linux,all,VirtualBox 6.0.14,2019-10-23T15:53:58Z,2019-10-23T15:53:58Z,"Thank you for my favorite desktop virtualization software!

I'm using the `disco` packages on `eoan`, because there doesn't seem to be a public eoan APT repo.",mightyiam
19042,DispatchQueue thread taking up close to 100% CPU,Mac OS X,Windows,VirtualBox 6.0.14,2019-10-26T07:28:50Z,2019-10-26T07:28:50Z,"With Windows 10 guest in fullscreen mode, I was typing in a guest text field when the guest seemed to freeze.  Checking on the Mac OSX host side, VirtualBox was using almost 200% on 2-cpu host (guest is only using 1 CPU).  Using the Mac spindump command, I got a dump that showed the DispatchQueue taking up almost all the time, apparently doing Qt updates.

I tried to saved the state of the guest, but VirtualBox crashed.  After rebooting the guest, I was able to reproduce the same freeze.",wullerdewust
18942,Severe UI rendering issues with QT 5.13.1,Linux,Windows,VirtualBox 6.0.12,2019-10-27T21:30:23Z,2019-10-27T21:30:23Z,"After recent upgrade to QT 5.13.1 (probably on or around 15/09/2019) on SuSE Tumbleweed VirtualBox started behaving incorrectly when used on two monitors setup with enabled OS level UI scaling (1.6). Issue happens only on one of the monitors. I am using X11 Plasma with KDE.

When VirtualBox is launched the main window is displayed properly, however when it is resized to full screen (or majority of the screen) severe rendering issues start to show up. The top level menu (File/Machine/Help) disappears, the VM list disappears etc (please refer to the screenshot). 

When a VM is started and is displayed in full screen only part of the screen of the guest is visible (see screenshot).

When VBox windows are moved to the other display and are maximized everything is OK again.

Out of curiosity I tested the latest VBox beta version (VirtualBox-6.0-6.1.0_BETA1_133315_openSUSE150) and the issue is there too.
",karolbe
19050,VirtualBox 6.0 on macOS 10.14 crashes on suspend/resume,Mac OS X,Linux,VirtualBox 6.0.14,2019-10-28T09:05:49Z,2019-10-28T09:05:49Z,"Host: Macbook Pro 2015 retina 13"", macOS 10.14.6, vbox 6.0.14
Guest: Ubuntu 18.04.3 server

When the macbook lid is closed and then reopened:
- the VM says it has ""unexpectedly quit""
- when I click on the VirtualBox icon, that has ""unexpectedly quit"" as well

Possibly related to #16486; however, I never had this problem with vbox 5.x.  It seems to happen every time now, although this is with a freshly-installed 18.04 guest so possibly the guest is different.

Since the laptop has a retina display, with vbox 6.0 I select View > Scaled Mode otherwise the console text is too small.  With vbox 5.x the console size was fine without adjustments.  I don't know if this is related.",bcandler
19052,split of the soapC.cpp file triggers internal GCC 9+ bug,other,other,VirtualBox 6.0.14,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)
19055,Hang in VM after upgrade to 6.0.14,Windows,Linux,VirtualBox 6.0.14,2019-10-31T15:38:58Z,2019-10-31T15:38:58Z,"My Ubuntu VM hangs after detecting the network card. This started after updating to 6.0.14, and has vanished when I stepped back to 6.0.12.
Network setup on the VM is Bridged to Intel Ethernet Connection (4)I219-V with Allow All and cable connected. ",hobson42
19054,No USB Device on Windows 7 guest,Windows,Windows,VirtualBox 6.0.14,2019-10-31T16:15:06Z,2019-10-31T16:15:06Z,"Host Win10 (64bit)
Guest Win7 (64bit)

After upgrading to 6.0.14 there is no USB device shown anymore in USB List. ",cyberoner
19056,Faulty cursor in 32 bit XP VM,Windows,Windows,VirtualBox 6.0.14,2019-10-31T23:58:07Z,2019-10-31T23:58:07Z,"I recently downloaded 6.0.14 for windows clients in hopes that it would fix the cursor problem that I've experienced in updates since 5.2.34. I am running a 32 bit XP VM which I use to run an older drafting program, Drafix CAD. On version 5.2.34 and earlier the cursor displayed properly both on the desktop and within the CAD program. Later updates show an enlarged cursor (regardless of pointer settings in control panel) on both the desktop and within the program. This enlarged cursor is problematic in the CAD program because it creates an offset between where the cursor appears to be and where it actually is which renders the CAD program basically useless. To try to eliminate this problem in 6.0.14 I turned off 3D acceleration, 2D video acceleration, and have tried both VMVGA and VMSVGA modes. Nothing returns the cursor to normal appearance. My workaround is to reinstall 5.2.34. Works fine so I won't be accepting any updates.  ",Woodsaregood
19057,powercfg fail operation,all,Windows,VirtualBox 6.0.8,2019-11-02T09:57:47Z,2019-11-02T09:57:47Z,"When i execute powercfg -h on in root.[[BR]]

C:\Windows\system32>powercfg -h on[[BR]]

La mise en veille prolongée a échoué avec l'erreur suivante : Cette demande n'es
t pas prise en charge.

Les éléments suivants empêchent la mise en veille prolongée de ce système.
        Le microprogramme du système ne prend pas en charge la mise en veille pr
olongée.
[[BR]]

I have this error because function 'hibernation' is not implemented.[[BR]]

I need it[[BR]]

For information i have virtualbox additions 6.0.8 installed[[BR]]


Thank.[[BR]]
",Sizy458
19063,Multiple VBoxSVC processes on Linux host,Linux,other,VirtualBox 5.2.32,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
19064,No animation on Windows 7 start button,Windows,Windows,VirtualBox 6.0.14,2019-11-05T19:51:04Z,2019-11-05T19:51:04Z,"There is no more an animation if the mouse cursor hovers over the start button (only windows 7). 

If then clicked on the start button, the ""hover""-design appears (It should be the ""clicked""-design). 

And if you then leave the start menu (and ""close"" it), the start-button keeps its ""hover""-design.",Timo
19067,No sound from any guest when using ALSA (PulseAudio works),Linux,all,VirtualBox 6.0.14,2019-11-06T13:54:17Z,2019-11-06T13:54:17Z,"When running VirtualBox 6.0.14 on Ubuntu 19.10, neither Windows 10 guest nor latest Debian are able to emit any sounds if I configure the host to use ALSA. PulseAudio does work.

It would seem the problem is somewhere on the host side where it for some reason fails to interact with the sound system. PulseAudio wasn’t running when I tried using ALSA. The configuration is the default, that is, neither /etc/asoundrc nor ~/.asoundrc are present.

The log does not appear to contain anything of relevance, attaching anyway.",rdaysky
19066,Windows guest video driver causes ms office equation render overlapped letters,Linux,Windows,VirtualBox 6.0.12,2019-11-07T06:30:05Z,2019-11-07T06:30:05Z,"I'm using vbox on Linux x86_64. Guest is Windows 7/XP 32bit.

Vbox guest additions' video driver causes Ms office Visio 2010/2007 render equation wrong (non-English version, using equation editor 3.0). While Word has no problem.

Disabling the video driver in Windows hardward management will avoid that issue.

In the log file, I started VM with video driver disabled. Since line 1473 I enabled driver.",BJ6hello
19077,A serious error occurred while running a virtual computer with virtualbox,Linux,Windows,VirtualBox 6.0.10,2019-11-11T01:08:08Z,2019-11-11T01:08:08Z,"Last friday， I use the virtualbox to run an ubuntu virtual machine to build a cross-compilation chain.And then I close the virtual machine.Today when I open it, I get a serious error, and I can't open it success.I have attach the log for this problem",Liyongchun
19078,"NT4 Guest: Weirdness with ""Enable Nested VT-x/AMD-V"" checkbox in guest settings",Windows,Windows,VirtualBox 6.0.14,2019-11-11T06:26:29Z,2019-11-11T06:26:29Z,"I have a good working install of Windows NT4 Server that I toy around with every few months.  I am not sure when this issue began, but I am assuming during 6.x.

From a known good snapshot, I can boot into NT4 successfully and login as the administrator account.  However, when I reboot the guest, the *next* reboot will fail with this error message:

    HAL: MPS MP Structure not found[[BR]]
    HAL: No MPS Table Found.[[BR]]
    
    HAL: This HAL.DLL requires an MPS version 1.1 system[[BR]]
    Replace HAL.DLL with the correct hal for this system[[BR]]
    The system is halting

The solution that I found is to go into the guest's settings, and under System --> Processor, enable OR disable the ""Enable Nested VT-x/AMD-V"" checkbox.  That means, if the checkbox is currently checked, uncheck it.  If it is not currently checked, check it.  Save and then exit the settings dialog.

After this, the next boot will work fine.  But!  The next time you restart the guest, you must toggle the state of that checkbox again before the guest will successfully boot.

Definitely one of the weirder bugs I've ran into.  I'll attach a screenshot of the HAL message, but I'm not sure what else the VBox developers might need to figure this one out.",kumba
19072,VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack unable to install,Windows,all,VirtualBox 6.0.14,2019-11-12T09:09:08Z,2019-11-12T09:09:08Z,"Upgrade of VirtualBox from 6.0.12 to 6.0.14 was successful but an issue happened during the upgrade of Extension Pack.

Fix: Manual removing all files under ''C:\Program Files\Oracle\VirtualBox\ExtensionPacks''

Error
''Failed to install the Extension Pack C:/Users/i314866/Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_DIR_NOT_EMPTY ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

''",Lukáš Viktora
14823,Error messages on a Windows 7 shutdown when VirtualBox is still open,Windows,other,VirtualBox 5.0.10,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
19084,Virtualbox 6.0.12 crash when running Windows guest,Linux,Windows,VirtualBox 6.0.12,2019-11-14T00:43:05Z,2019-11-14T00:43:05Z,"Hi I build Virtualbox from source against custom Linux kernel 4.19.72

	./configure  --build-headless --build-libxml2 --enable-vnc --disable-hardening --disable-docs \
	 --disable-udptunnel --disable-devmapper --disable-dbus --disable-alsa --disable-pulse --disable-java \
	--with-linux=/root/linux-stable

and I got the following crash when running Windows7 VM

00:00:00.199497 SUP: Loaded VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:00.199566 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:00.208481 
00:00:00.208484 !!Assertion Failed!!
00:00:00.208485 Expression: pVM->offVMCPU == RT_UOFFSETOF(VM, aCpus)
00:00:00.208488 Location : /root/trunk/3rd/src/VirtualBox-6.0.12/src/VBox/VMM/VMMR3/VM.cpp(595) int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*)
00:00:00.208528 Stack :
00:00:00.208530 00007f1fc0df12b4 VBoxRT.so + 0x1832b4


Would you please tell me what may be wrong for pVM->offVMCPU == RT_UOFFSETOF(VM, aCpus) ?

thanks
rob",robhuang
19083,Virtualbox Crashes after waking from Sleep macOS High Sierra,Mac OS X,Linux,VirtualBox 6.0.14,2019-11-14T01:17:15Z,2019-11-14T01:17:15Z,"I have an early 2011 15"" MacBook Pro running High Sierra 10.13.6. Virtualbox 6.0.14 is installed and used to run  an Ubuntu Desktop virtual machine.

When waking my computer from sleep, the virtual machine crashes within seconds. At the next occurrence, I'll attach crash report files. I suspect the issue is related to https://www.virtualbox.org/ticket/11425 https://www.virtualbox.org/ticket/11444 and maybe others.

The other tickets mention a change in networking being the cause of the crash. I.e., the computer sleeps on one network and wakes on another. I'll monitor for that and update with further findings. I'm at a university with four different networks and multiple gateway devices for each network. If networking is the cause of these crashes, it may be related to different gateway devices since each wifi network has multiple access points but the same network name.",www139
19079,BSOD после обновления с 5.1.22 до версии 6.0.14,Windows,Windows,VirtualBox 6.0.14,2019-11-14T08:27:10Z,2019-11-14T08:27:10Z,"После обновления VirtualBox с версии 5.1.22 до версии 6.0.14 на Windows 7_x64 не получается запустить ни одну из ранее установленных виртуальных машин, т.к. постоянно выскакивает BSOD. VM установлена не на системном диске.",Назаров Андрей Валерьевич
19085,Error with Windows 10 Enterprise 1903 build 18362.476 and VirtualBox v6.0.14 error,Windows,Windows,VirtualBox 6.0.14,2019-11-15T05:24:01Z,2019-11-15T05:24:01Z,"my MS Windows is in Portuguese-BR!
my user Windows: ""PCuserWin"" -> is a administrator, per default!
Then, all my software are installed in this profile!
My user Administrator, stay disabled, per default!

I use VirtualBox since v5. My pc is:
- CPU Intel i7 4770K
- RAM 8GB Corsair Vengeance
- VGA Gigabyte nVidia GTX650 Ti Boost 2GB
- SSD 120GB Corsair to Operating System MSWindows
- HDD 1TB free to my virtual machines (normally 2 or 3 for test, and later I delete it)

My antivirus Kaspersky Internet Security v2020, never got in the way of installing VirtualBox or virtual machines!

I do not see any changes on my computer so this new error appears!
-------------------

Sometimes i had this problem when try install ""Package"" as normal user (no Admin) as always:
- all my downloads stay (always) in Drive ""D"" (include VirtualBox + Package)
- my Drive ""C"" only MSWindows, Kaspersky, RAD Studio 10.3.2, and other utilities -> normally, only apps to work! No games!

to avoid this error, I try install it using run VirtualBox app ""As Administrator"", or, I copy the file ""Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack"" to into my folder VirtualBox on Disk""C"". then, works! 


----------- Screen error #1: Fail on install Extension Package  -----------
Falha ao instalar o Pacote de Extensões D:/Downloads/__Utils/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1644' -&gt; 'C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Código de Resultado: E_FAIL (0x80004005)
Componente: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
---------------------------------


Now, using same MSWindows 1903 build 18362.476, i had another error when trying create new VM to test new ISO MSWindows 1909 (downloaded from Microsoft directly):

---------- Screen error #2: Fail to the open a session to ... ----------
Falha ao abrir uma sessão para a máquina virtual Windows101909. <-- my VM

 (VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--------------------------------------------------------------

But my ""VIRTUALIZATION"" always is activated on BIOS and MSWindows, since always!  I never had this error before.

I always create my VM with 2GB and 1 (or 2 cpu virtual), and 80GB disk.
I never use 2 VM in same time.
Later test the new system, I delete my VM. Then, i have many disk space!

",Emailx45
19087,"Crash with ExceptionCode=0xc0000005 on ""VMSVGA FIFO""",Windows,Windows,VirtualBox 6.0.14,2019-11-16T02:59:14Z,2019-11-16T02:59:14Z,"Host is windows 10/
2 VMs launched. Virtualbox freezes ""1 VirtualBox GUI is frozen.png"". Correctly completing work in the 1st guest Windows XP. Error ""2 VirtualBoxCrush.png"" pops up and the 2nd guest Windows 10 disappears.
There is also a failure of the keyboard and mouse on the fault of the windows  10 host computer when connected to it via the RDP.

It started this week after updating the virtual box to 6.0.14 r133895 (Qt5.6.2), but the Windows 10 host was also updated.",Дмитро
19081,Display shrinks to 1024x768,Windows,Windows,VirtualBox 6.0.14,2019-11-16T08:39:50Z,2019-11-16T08:39:50Z,"I've been using VirtualBox for several years but recently my Windows 10 guest upgraded from release 1803 to 1903. Since then I've had problems.

Initially I would have random lockups. Suddenly the guest would be unresponsive and after a while it would crash and VirtualBox would report that the guest had aborted. Googling led me to sites that suggested the lockups were usually related to the graphics driver.

I was using VBoxVGA (as I'd originally started on v5.1 of VirtualBox). After lots of reading about the VirtualBox video drivers I discovered I should have been using VBoxSVGA when I upgraded to v6.0 of VirtualBox (currently on v6.0.14).

Since the switch I've not had any lockups but at random times instead my desktop shrinks. I'm using a 4K monitor in Full Screen mode (3840x2160) and when the shrink occurs the Windows 10 desktop has shrunk to 1024x768 and is centred on the screen with a massive black border all around. The guest hasn't crashed and Host+F twice restores the screen to the full size but all my open applications have been squashed too, so I have to resize them.

I asked this question on the forums and it was suggested I log the problem here with logs.

When I originally reported the issue in the forums I was at home using my Windows 7 desktop but it's just occurred while I'm away running the VM on my laptop (Win 10 Home host).

Host: Windows 10 Home (Build 1903)
Guest: Windows 10 Pro (Build 1903)",Iain Waddell
19092,6.0.14 Extensio Pack installation error on Linux Mint Debian Edition 3,Linux,other,VirtualBox 6.0.14,2019-11-17T01:57:01Z,2019-11-17T01:57:01Z,"Система LMDE 3,Ошибка установки VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack.",gri
19097,"""VirtualBox manager has stopped working"" when removing laptop from docking station",Windows,Linux,VirtualBox 6.0.14,2019-11-20T06:49:34Z,2019-11-20T06:49:34Z,"When unddocking/docking my laptop (Fujitsu, Lifebook E Series) from the docking station the VirtualBox manager crashes with a dialog message: ""VirtualBox Manager has stopped working.

I'm running: Windows 10 x64 as host and have one virtual machine running at that time: ""Ubuntu 18.04.3 LTS"". This machine remains working, but the VM Manager is crasing. I followed the instructions to create a coredump which is attached.

My VM also crashes sometimes on dock/undock but here I need to gather more information and will file another ticket.

Expected behavior: Manger should not crash on dock/undock",martg
19098,DR-DOS/Caldera-OpenDOS-7.01 floppy images not recognized,other,other,VirtualBox 6.0.14,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)
18954,VBoxSVGA x64 Vista guest 3D accelerated video broken in VirtualBox 6.0.12,Windows,Windows,VirtualBox 6.0.12,2019-11-20T14:04:41Z,2019-11-20T14:04:41Z,"On a x64 Windows Vista guest, after the installation of VirtualBox 6.0.12, I followed the recommendation to switch to the VBoxSVGA graphics controller in the context of the upcoming deprecation of VBoxVGA. As part of switching to VBoxSVGA I installed the 6.0.12 guest additions with 3D acceleration enabled. 

Following the restart of the guest (eventually multiple times), I consistently get display behavior that effectively makes the VM unusable. What seems to happen is that whatever section of the screen (like an icon, desktop gadget, title bar and occasionally the entire desktop) was updated last is displayed in full screen within the guest.

I will attach a number of screenshots displaying this behavior as I moved my mouse pointer over the guest's screen. Do note that some of those screenshots, being the ones showing the VirtualBox window decorations, were taken in the (Windows 10) host, and some within the guest itself. As you can see, the results are consistent independent of the source of the screenshot.",Rutger van Bergen
19095,Network connection mode couldn't bridge to “VMware Network Adapter” on Windows 10,Windows,all,VirtualBox 6.0.14,2019-11-22T08:51:41Z,2019-11-22T08:51:41Z,"I have a virtual machine that can only run on the vbox，but my primary system is installed on  ""Vmware Workstation Pro""。On MacOS，vbox network can bridge to vmware network adapter such as ""VMnet8""
.But it doesn't  work that way on window 10.",zlgxzswjy
19096,bug keyboard,other,other,VirtualBox 6.0.14,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
19101,Movie Maker with Windows Vista,Linux,Windows,VirtualBox 6.0.14,2019-11-23T00:12:49Z,2019-11-23T00:12:49Z,"Hey!

I need to use the old Windows Movie Maker and therefore I set up a Windows Vista machine.

Issue:
Movie Maker starts fine after some tinkering, but the guest OS crashes if anything is done with the timeline.

Things I did:
- Installed Windows Vista
- Installed all available updates (+ Firefox)
- Installed guest additions 6.0.14 multiple times with different settings, inside and outside of Safe Mode
- Added one shared directory

VM settings:
- 2 GB RAM
- 2 CPU cores
- 3D acceleration enabled
- 2D acceleration enabled
- VBoxSVGA
- 256 MB graphics memory


At first, Movie Maker did not start at all because it needs graphics acceleration. Also, it didn't start when I installed the Guest Additions with regular Direct3D support - dxdiag.exe reported that there was no Direct3D acceleration available.
Installing the Guest Additions with the experimental Aero (WDDM) support failed once in safe mode, but succeeded on the second try.
Movie Maker starts fine now, but as soon as an item is added to the media timeline or moved within it, the Guest OS freezes for a few seconds, then reboots.

Anything I can do to help debug this problem?",jeinzi
19105,Keyboard capture does not work properly under Wayland,Linux,all,VirtualBox 6.0.14,2019-11-23T01:23:30Z,2019-11-23T01:23:30Z,"I am using Virtualbox on Fedora under Wayland (Gnome/Mutter). It generally works correctly apart from being able to capture all keyboard presses.

Key combinations that have meaning to the OS (Alt+Tab, Cmd key, Alt+F4 etc.) are handled by the OS and don't make it to the VM. That '''was''' previously a known issue with Wayland, but has since been fixed by providing the appropriate extension. This has been implemented by Gnome and is in use by the Gnome Boxes app to provide correct keyboard behaviour.

See these two issues for some history and context:
https://bugzilla.redhat.com/show_bug.cgi?id=1285770
https://bugs.freedesktop.org/show_bug.cgi?id=97333

Implementing the same functionality for VirtualBox would greatly improve the usability on Wayland.",WillW
19110,Windows 10 KMODE_EXCEPTION_NOT_HANDLED with mapped shared folder,Mac OS X,Windows,VirtualBox 6.0.14,2019-11-26T21:46:32Z,2019-11-26T21:46:32Z,"Mapped folder:
{{{
              Z:        \\VBoxSvr\Downloads       VirtualBox Shared Folders
}}}

Steps:
1. Turn on win 10 (1809/17763.805) -- this is VM is from modern.ie (it's ~45 days old and updates on its own), it has a persistent mapped shared folder
2. Log in (IEUser...)
3. Open Windows explorer
4. Browse to This PC
5. Browse to Downloads ({{{\\VBoxSvr}}})(Z:)
6. Click the files pane
7. type `zap` (I have ZAP_2_8_0_windows.exe in this shared folder)

Consistently rebooted a couple of times. Since copying the file from the drive to c: using `cmd`, this hasn't happened.

I do have a full kernel dump (4GB).",Garner
18496,'vboxmanage guestcontrol run' stops working after several hours with Linux guests (on MacOS host),Mac OS X,Linux,VirtualBox 6.0.4,2019-11-28T10:11:29Z,2019-11-28T10:11:29Z,"I have a host test script that invokes functionality on Windows and Linux guest VMs using 'vboxmanage guestcontrol run' commands.
After working fine for 3 or 4 hours, the script stops working as the Linux guest VM stops accepting these run commands

At this point, manually issuing a run command shows:
{{{
$ vboxmanage guestcontrol Ubuntu-14.04.5-amd64 run /bin/ls --username xyz --password xyz --verbose

Creating guest session as user 'xyz'...
Waiting for guest session to start...
VBoxManage: error: The specified user was not able to logon on guest
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestSessionWrap, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aSessionWaitFlags), 30 * 1000, &enmWaitResult)"" at line 879 of file VBoxManageGuestCtrl.cpp
Closing guest session ...
}}}

Rebooting the Linux guest VM restores proper functionality.

This is with MacOS 10.13.6 host.

This problem has been repro'ed using VirtualBox 6.0.4 as well as older versions 5.1.38 and 5.0.40

Linux versions tried as the guest VM are: Ubuntu 18.04.1, Ubuntu 14.04.5, and Solus 3.9999
- all exhibit this problem

The test script works fine with Windows7 guest VM, no such failures have been observed with the script running continuously for over 40 hours.
",AlbertDude
19116,When accessing shared folders the WIN10 1903 VM reboots on a WIN10 1903 host,Windows,Windows,VirtualBox 6.0.14,2019-11-30T11:57:21Z,2019-11-30T11:57:21Z,"Similar to ticket 18766, which was resolved in 6.0.14.  When I access shared folders some folders open up hesitantly, most cause a reboot of the VM.
I am new to this, so please let me know what other information would help.  Thanks.",psptconsp
19124,Installing the guest additions on Ubuntu results in no display,Windows,Linux,VirtualBox 6.0.14,2019-12-03T05:07:21Z,2019-12-03T05:07:21Z,"All pre-requisites are installed.Installation gets to the point of generating the boot images and goes to blank screen. Rebooting does not help and the condition is only recoverable if you go into recovery mode and remove the virtual box guest additions.  
Repeated the process on Ubuntu 18.04 and 19.10 same result. 
The end result is a machine that cannot be interacted with graphically. ",RandomDude
19074,"VM Stuck in ""offline snapshotting"" state",Linux,Linux,VirtualBox 6.0.10,2019-12-03T19:22:03Z,2019-12-03T19:22:03Z,"The active problem is that a VM is stuck in ""offline snapshotting"" state and I can't do anything with it.  I need a way to get it out of that state, hopefully without corrupting the VM along the way.

There is no relevant VM-specific log information.  Since it's an offline snapshot, the VM wasn't running at the time, so the most recent log ends with ""Machine state changed to 'PoweredOff'"".

There appears to be no relevant info in the ~/.config/VirtualBox log files either.  Just a bunch of messages about saving config files and the reaper running.

Here's how I got to where I am:
I'm working on a Perl+Curses TUI front-end for a headless !VirtualBox server. It uses the vboxwebsrv webservice via the `SOAP::Lite` package to interact with !VirtualBox. I am following the API documented in the latest SDK from Oracle (6.0.10).

When my scripts initiate a snapshot of a powered-off machine via `IMachine::takeSnapshot`, the VM then becomes stuck in ""offline snapshotting"" state (""stuck"" as in it's been in that state for over 2 months as of the time of this writing). This is what the script does:

1. Get an `ISession` object via `IWebSessionManager::getSessionObject`
2. Lock the session in Shared mode via `IMachine::lockMachine`
3. Get a mutable `IMachine` object with `ISession::getMachine`
4. Initiate the snapshot from the mutable `IMachine` object, getting an `IProgress` object, with `IMachine::takeSnapshot`
5. Start a modal window which periodically queries the `IProgress` interface for its status until `IProgress::complete` returns `true`

As I'm reviewing my code to write this, I note that it's possible that `ISession::unlockMachine` is being called before the `IProgres`s object reports success. Although the documentation implies that a session remains locked as long as it is busy even after a call to `ISession::unlockMachine`, I wonder if this may be causing !VirtualBox to do something bad resulting in the stuck ""offline snapshotting"" state.

Environment info:
* Host OS is Debian Buster 64-bit.
* Guest OS is Windows 7 Ultimate 32-bit.
* VBoxHeadless --version gives 6.0.10r132072.
VBox.log does not get anything written to it.
I'm happy to do whatever data collection is necessary to troubleshoot this; just let me know what I need to do.",Brian of the Pines
19129,Cannot reconize password in Kali Linux 2019.4 VM,other,Linux,VirtualBox 6.0.14,2019-12-04T05:35:54Z,2019-12-04T05:35:54Z,password not reconized by kali Linux software,tommy smith
19128,Kernel bug (vboxdr - VBoxNetFlt) - eth device unintentionally enters promiscuous mode,Linux,Linux,VirtualBox 6.0.14,2019-12-04T06:44:26Z,2019-12-04T06:44:26Z,"Hello, 

When a natnetwork definied. For a while, after some reboots of VM, when VM just started Linux Kernel shows problems.
It is reproducabe: make a new natnetwork eg. like this:

{{{

$ VBoxManage natnetwork add --netname anyad \
--network ""192.168.15.0/24"" --enable --ipv6 on \
--port-forward-4 ""www:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-4 ""ssh:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-4 ""ssl:tcp:[]:10443:[192.168.15.10]:443"" \
--port-forward-6 ""www_ipv6:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-6 ""ssh_ipv6:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-6 ""ssl_ipv6:tcp:[]:10443:[192.168.15.10]:443
}}}
""


{{{
$ VBoxManage dhcpserver modify --ip 192.168.15.3 --netmask 255.255.255.0 \
--netname anyad --lowerip 192.168.15.10 --upperip 192.168.15.100
}}}


Then you select natnetwork definied above for VM. After some rebootings of VM there will be Kernel messages just when you start the affected VM like this:


{{{
[ 6693.723692] vboxdrv: 0000000000000000 VMMR0.r0
[ 6693.850079] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 6693.896097] VBoxNetFlt: attached to 'enp3s0' / xx:zz:xx:zz:xx:zz
[ 6693.901656] vboxdrv: 0000000000000000 VBoxEhciR0.r0
}}}

No need VM to start the guest OS totally, as soon as VM begun to run the Kernel messages sign.
When VM will be just stopped, Kernel message will be like this:
{{{

[ 6355.406993] device enp3s0 left promiscuous mode
[ 6356.691870] vboxnetflt: 0 out of 9668 packets were not sent (directed to host)

}}}

Temporary workaround:

{{{
$ VBoxManage natnetwork remove --netname anyad
$ VBoxManage dhcpserver remove --netname anyad
}}}

After re-make a new natnetwork with same option like above I wrote.


Affected VB versions: 6.0.14 and 6.1.0_RC1 r135151[[BR]]

Affected Kernel: Linux 5.0.0-36-generic",petervagyok
19071,W10 Guest crash when watching youtube videos,Linux,Windows,,2019-12-05T09:40:51Z,2019-12-05T09:40:51Z,"Hi,

When I found 6.0.14 crashing, I tested with the latest nightly[1] and Extension[1.5].

My Host O/S is openSUSE Tumbleweed.  I am up to date[2].

The Guest O/S is an up to date W10 VM.

While watching a youtube video (any will do), the VM crashes.

The following errors are logged.  First, in /var/log/messages:

{{{
Nov  7 17:05:08 fuzzy kernel: EMT-1[28979]: segfault at 7fe0ee42d920 ip 00007fe21dd295ff sp 00007fe1ee42d898 error 4 in libc-2.30.so[7fe21dca6000+14d000]
Nov  7 17:05:08 fuzzy kernel: Code: a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
}}}

after, in VBoxSVC.log:

{{{
00:07:50.279667 main     Saving settings file ""/home/xyz/.VirtualBox/load_test/load_test.vbox"" with version ""1.15-linux""
00:07:50.742201 Watcher  Reaper: Pid 28941 (710d) was signalled: 11 (0xb)
00:07:55.284290 main     VirtualBox: object deletion starts
00:07:55.284327 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/w10/w10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284451 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/r-mobile/r-mobile.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284533 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/load_test/load_test.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.743302 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:08:00.315967 main     {00007ff38001ba80} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:08:00.317272 main     VirtualBox: object deleted
}}}

Nothing is placed in VBox.log

Please let me know what other data is needed.  I am sure you need more.  ;)

'''References'''
1 - VirtualBox-6.0.15-134477-Linux_amd64.run
1.5 - Oracle_VM_VirtualBox_Extension_Pack-6.0.15-134477.vbox-extpack
2 - Tumbleweed version 20191104",Pablo Sanchez
17803,Virutalbox fails to install on MacOS 10.13.5,Mac OS X,other,VirtualBox 5.2.12,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
18979,"Port forwarding ""NAT network"" window for IPv4 display issue",Mac OS X,other,VirtualBox 6.0.12,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
13659,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it",Windows,all,VirtualBox 4.3.20,2019-12-07T17:39:42Z,2019-12-07T17:39:42Z,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it.

VirtualBox since 4.3.14 (all builds, including 4.3.20/4.3.21 - the most updated) are incompatible with Outpost Firewall Pro v6.7.x and others, that used ""WL_HOOK.DLL"" module to inject to all processes to get some information in RING3 (usermode).

WL_HOOK.DLL is digitally signed (!) (I can attach this file, if needed), and must be allowed even by hardened rules. But VirtualBox incorrectly recognize a path to it. There is a bug in VirtualBox getting/parsing path information in some cases of modules inject or other (probably, is because of special inject technics, that used). Please see a VBoxStartup.log:

{{{
...
e4.11ec: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\WINDOWS\system32\imm32.dll [lacks WinVerifyTrust]
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=76290000 'E:\WINDOWS\system32\IMM32.DLL'
e4.11ec: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║)
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║: None of the 1 path(s) have a trust anchor.: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║
e4.11ec: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedMonitor_LdrLoadDll: rejecting 'e:\progra~1\outpos~1\wl_hook.dll': rcNt=0xc0000190
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'e:\progra~1\outpos~1\wl_hook.dll'
...
}}}

Please see a lot of garbage (binary garbage like ""ц╜ОцХоц╝атБжцб┤тБетА▒цЕ░ц"" and so on) after ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall"" string, instead of normal dll name path.

The real path to wl_hook.dll is E:\Program Files\Outpost Firewall Pro\wl_hook.dll

So it must be like: ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall\wl_hook.dll""

But you had incorrectly get/parsed data. It seems like buffer contain a garbarge or like string's ending-zero is missed or something, so you are reading garbage memory.

After you are got that garbarge-containing-path you a providing it to a system function WinVerifyTrust to check digital signature of this ""file"". But path is invalid (garbaged/damaged), so Windows function cannot find the file and check digital signature and returns an error.

After getting this error, you are REJECTING to load this .dll.

And after that, we have a problems to use VM. Because Outpost Firewall cannot read information about process without this R3-dll injected to VM's process, so it can't get correct ProcessName and can't allow/create_rule to any network or other activity from VM, so it is UNUSABLE.

Please fix path retreiving/parsing or this inject method allowing and allow WL_HOOK.DLL (digitally signed) to inject to your process.",John Dan
19136,Failed to open a session for the virtual machine (hardening error),Windows,all,VirtualBox 6.0.14,2019-12-08T15:48:53Z,2019-12-08T15:48:53Z,"Hello,

Failed to open a session for the virtual machine Linux 16LTS.

The virtual machine 'Linux 16LTS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\Linux 16LTS\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}


Failed to open a session for the virtual machine WIN10.

The virtual machine 'WIN10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\WIN10\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}




Best Regards,

Adélio Miranda
",Adelio Miranda
19137,Change log rotation scheme from VBox.log[.<number>] to VBox[.<number>].log,all,all,VirtualBox 6.0.14,2019-12-08T16:11:18Z,2019-12-08T16:11:18Z,"== Current situation ==

Not sure why it first got implemented as is, but when there's a log rotation, the rotation algorithm calls for the ""`.<number>`"" to be appended to the ""`VBox.log`"" name, resulting in ""`VBox.log.1`"", ""`VBox.log.2`"", ""`VBox.log.3`"", or more, depending on your rotation settings:
{{{
VBoxManage setproperty loghistorycount
}}}

That naming scheme is not very helpful when trying to open/display the logs, because they have a ""`.<number>`"" extension, which could be ''anything'', with the most common use that the file is a part of a multi-part archive (ZIP and RAR come to mind).


== Proposed solution ==

* Change the naming scheme/logic/altorithm from ""`VBox.log.`'''`<number>`'''"" to ""`VBox.`'''`<number>`'''`.log`"".

That way there are always ""`VBox[.<number>]`'''`.log`'''"" files, which can be associated and opened with your favorite application.

'''NOTE''' \\
The same logic applies to the PNG screen-capture files in case of a Guru Meditation, should be addressed there as well.",Socratis
19125,Crashes with vmsvga,Windows,Linux,VirtualBox 6.0.14,2019-12-09T06:51:32Z,2019-12-09T06:51:32Z,"Vm crashes if more than 128 megabytes of vram is issued to vmsvga graphical controller.
for example 129
I booted from https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/25/Workstation/i386/iso/Fedora-Workstation-netinst-i386-25-1.3.iso",kotenok2000
19126,Hard freeze on Centos Host system with Guest using Shared Folders,Linux,Windows,VirtualBox 6.0.14,2019-12-09T15:33:25Z,2019-12-09T15:33:25Z,"Running Centos 7.7 Host with a Windows 10 Guest using a Shared Folder. I have experienced issues in the past with Shared Folders, but in the past it only seemed to affect the Guest systems. This issue is hard to troubleshoot since the Host system freezes, I can only resolve it by unplugging the power. I have tried using the SysRq keys to no avail. In troubleshooting the issue, I have stopped all other host applications except VirtualBox and disconnected the Shared folder. For a week, I did not experience any freezing of the host the system. If I connect the Shared Folder I will randomly experience a hard freeze in a couple of hours or a couple of days.

The host system has 16GB RAM and 4 cores. I am using 4GB and 2 cores for my Windows 10 1909 guest.

I do not know how to troubleshoot this any further since the Host system hard freezes, I do not get any indications of problems in any of the host logs. It most likely freezes before documenting the problem. I welcome any tests or settings which you want me to implement in order to determine the problem or fixes.
 ",jim.rather
19139,Kali linux VM buggy cursor,Windows,Linux,VirtualBox 6.0.14,2019-12-09T22:23:55Z,2019-12-09T22:23:55Z,"hello,
My problem is that the mouse integration bugs after a while on kali linux so i have to reebot all the time.
I still can move the cursor graphicaly but its position stays the same. I can click but always on the same spot. 
But when i deactivate the mouse integration option the cursor now disapear but moves.",FvckNorris
19109,Host resume and VM does not respond,Windows,Windows,VirtualBox 6.0.14,2019-12-10T10:44:09Z,2019-12-10T10:44:09Z,"Twice today I've resumed my host (after the host has gone to sleep because I've been away from my desk) and the guest has been frozen. The screen display is restored but the mouse isn't active.

After a minute or so the VM crashes and I have to restart the VM.

Logs are attached from after second crash.",Iain Waddell
18874,Slowdown of X11 drawings in VBox 6.0.10 in comparison to 5.2.* series.,Windows,Linux,VirtualBox 6.0.10,2019-12-11T19:14:21Z,2019-12-11T19:14:21Z,"First the environment:

Host OS: Windows 10 64bit
Guest OS: Debian GNU/Linux 64-bit.
         Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-6 (2019-07-18) x86_64
Memory: 16 GB memory is assigned to VBox out of 32GB real memory.
CPU: Ryzen 2700, 6 out of 16 (8 real core + 8 hyper-thread) are
     assigned to the VBox guest.

Real Display used: 3840x2160 (60Hz) Dell 
Real Display Adaptor on the host: NVidia GeForce GT 1030

Background and Symptom:

I am using VBox under Windows 10 host on a few PC's.
I have used VBox for at least several years now.

On a home PC, I switched from 5.2 series to the latest 6.0.10 about a
couple of weeks ago, and experienced a visible slowdown of X11 drawing
inside the guest Linux. (Say, when I move terminal windows around the
screen. The move is not smooth and very jaggy).

Fast operation with VBox 5.2 series

The slowdown is so much so that I switched back to the 5.2.32 VBox
today, and verified that the moving of terminal window inside the
Linux guest that runs inside 5.2.32 VBox is fast and much
smoother. With 6.0.10 VBox, moving windows shows the wiggling of
window frame if you know what I mean.

I have duly installed the guest tool in both versions.

BTW, when I downgraded from 6.0.10, I had to reinstall/downgrade VBox
extension so that proper USB3.0 support is available.  Funny thing is
that downgraded VBox 5.2.32 resulted in the fast X11 drawing within
the guest OS when I moved the terminal window around EVEN BEFORE I
installed the guest tool. (Does the old guest tool remain in the
system? I don't think so...)

Observation: High Xorg CPU utilization with VBox 6.0.10

With VBox 6.0.10, the linux command ""top"" shows the Xorg x11 server
consuming almost 20% of CPU time CONSTANTLY. This is definitely the
symtom ofslowdown of drawing. The CPU utilization goes up near 25% if
heavy drawing is involved: I felt that other operation became also
slow from time to time. Xorg was slowing down everything, I think.

OTOH, with VBox 5.2.32, Xorg server in the linux guest OS spends
only 2.3% of CPU time when there is not much X11 drawing and the
utilization goes up to 5-6% or so when I move the terminal window, etc..
There is a clear difference of drawing efficiency here between the linux guest in Vbox 6.0.10 and 5.2.32.

Display Setting of VBox

Naturally I checked the display setting of the VBox.

Memory for the graphics display is set to 128MB (maximum) in both
versions of VBox. (BTW, is this memory size relevant in the days of 4K
color display? Or does the guest tool tries to access the native
graphics adaptor memory directly???) 

With VBox 5.2.32, 2D/3D acceleration is set to 3D acceleration only.

With VBox 6.0.10, there are choices of VGA, ..., SVGA. I checked the
both setting of VGA and SVGA and their choice did not make much
difference:Still slow drawing in both cases.
With 6.0.10., 3D setting does not seem to offer much improvement. I
mean disabling (not marking it) does not change much. (I wonder if the
guest graphics module is working or not ...)

When I tried to set 2D under 6.0.10, VBox says it is an illegal
setting and ignored stating that the virtual machine is set to use
video streaming (?) acceleration and it is only supported for Windows
guest and thus ignored. (Sorry, I am using a Japanese-locale Windows
and and the message shown is in Japanese and the above is my best
attempt to translate the gist of the message for this report.)

Well, I can use this 5.2.32 or subsequent 5.2 series until June 2020
when the support of 5.2 series will be terminated.

But I certainly hope to see this issue resolved on this PC before 
5.2 series will become unsupported so that I can use 6.0.x series
comfortably without X11 drawing slowdown..

Strange thing is that I don't think I see similar slowdown problem on another
PC that I use at the office. That machine uses Intel CPU with built-in
graphics co-processor and so it does not use separate graphics
adaptor. It also runs Windows 10 64-bit and runs Debian GNU/Linux.
It runs VBox 6.0.8 or 6.0.10 (I need to re-check.) but the speed of X11
redrawing in the guest linux OS is just fine there.
That VBox 6.0 series runs fine on that office PC was the reason I wanted to
switch to 6.0 series on my home PC in the first place.

Does anyone see similar X11 slow down inside the linux guest under
Windows?

TIA





",ci-zephyurus
19150,Seamless mode hides mini ToolBar,Linux,Windows,VirtualBox 6.1.0,2019-12-12T21:02:11Z,2019-12-12T21:02:11Z,"This bug goes back to VB 5.2, if memory serves.  It was fixed in 6.1 RC1, so I thought ""great!"", but in the 6.1 release, the problem has returned.

On Solaris, Linux, and FreeBSD (BSD using the OSE release) hosts, when a VMs is in seamless mode (like Win 7 and these same Linux/UNIX variants), the VB mini ToolBar is hidden behind the guest's toolbar if they are on the same edge of the screen.  There is no way to bring it forward, even if you set your guest to auto-hide its toolbar.

Attached log is from Windows 7, but it also happens with other guests that have a desktop that works well with seamless mode, like MATE or Gnome2.

This also happens if I use 6.1.0 with the 6.1.0RC1 guest additions.",bq
19089,Kernel Panic when running Ubuntu 18.04.03 inside VirtualBox 6.0.14 on macOS 10.14.6 host,Mac OS X,Linux,VirtualBox 6.0.14,2019-12-14T15:31:10Z,2019-12-14T15:31:10Z,"While the installation of Ubuntu 18.04.03 went fine, a subsequent boot of this VM resulted in a kernel panic. See attached files.",Lars Sonchocky-Helldorf
19159,3 Crashes of VirtualBoxVM running Ubuntu 18.04 guest on macOS 10.14.6 host,Mac OS X,Linux,VirtualBox 6.1.0,2019-12-14T16:51:13Z,2019-12-14T16:51:13Z,"I am running VirtualBox Version 6.1.0 r135406 (Qt5.6.3) on a macOS Mojave 10.14.6 host. Guest OS is Ubuntu 18.04.3 (that's what I installed) but ""uname -a"" says:

Linux Ubuntu-1804-VirtualBox 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I think this is the case because I have the 6.1 guest additions installed.",Lars Sonchocky-Helldorf
19143,usb busy with previous request,other,other,VirtualBox 6.0.14,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
11517,VBoxSDL error before launching VM,Windows,all,VirtualBox 4.2.6,2019-12-15T12:32:47Z,2019-12-15T12:32:47Z,"In version 4.2.6 under Windows 7 SP1 x64, when trying to start a VM using VBoxSDL, I get the following error (regardless of the VM) :
{{{
SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
[[BR]]
It also happens from a freshly created VM :

{{{
C:\Program Files\Oracle\VirtualBox>vboxmanage createvm --name test --ostype Debian_64 --register
Virtual machine 'test' is created and registered.
UUID: 2cbfe35a-fd26-44e3-90a3-9a6e31f406f3
Settings file: 'D:\VMs\VirtualBox\test\test.vbox'

C:\Program Files\Oracle\VirtualBox>vboxsdl --startvm test
Oracle VM VirtualBox SDL GUI version 4.2.6
(C) 2005-2012 Oracle Corporation
All rights reserved.

SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
No VBox.log is generated and nothing appears in the VBoxSVC.log.",Max D
19161,The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1),other,other,VirtualBox 6.0.14,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
19162,The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1),other,other,VirtualBox 6.0.14,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
19164,WindowsXP guest 3D acceleration,other,other,VirtualBox 6.1.0,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
18879,Sound issues since 5.2.20 - Win98+Fifa98,Linux,Windows,VirtualBox 6.0.10,2019-12-17T00:03:47Z,2019-12-17T00:03:47Z,"Hi,
I used to use a Virtualbox for quite some time on a private system to emulate Windows 98 SE with Fifa98 RTWC [2].
That was going fine but somewhen throughout last year I list sound.
First I thought it would be my messing with the system, but whatever I did it did not return.
After a while I did full re-install my system back to the last perfectly working virtualbox version (and a new OS install of the older Ubuntu 16.04).

Then I used the upstream downloads [3] to essentially do a version bisect when it was broken and found it.
6.0.10 (known bad)
5.2_5.2.32-132073 - fail
5.2_5.2.28-130011 - fail
5.2_5.2.20-125813 - fail
5.2_5.2.18-124319 - ok
5.2_5.2.16-123759 - ok
5.2_5.2.14-123301 - ok
5.2_5.2.4-119785 - dkms error on install
5.5.2_2.0-118431 - dkms error on install
5.1_5.1.38-122592 - ok (known good)

It is not that sound would be broken totally, e.g. windows startup sound works and playing wav files. But when starting the game sound fails (no error message). Back out of the game Windows sound works still.

I think this uses DX5 for sound, but I'm not sure.

I tried to replace the (virtual) sound card from soundblaster to AC97 but that didn't help either.

I wonder what debug data I could collect for you to get this understood and fixed at the head of 6.x series so that I can upgrade again?

P.S. I started this in the Ubuntu tracker at [1], but after the debugging we did I guess it is time to reach out here.

[1]: https://en.wikipedia.org/wiki/FIFA:_Road_to_World_Cup_98
[2]: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1840749
[3]: https://www.virtualbox.org/wiki/Downloads",cpaelzer
18784,Windows guests hang exactly once after each host reboot,Windows,Windows,VirtualBox 5.2.32,2019-12-17T01:21:03Z,2019-12-17T01:21:03Z,"At some point during the 5.2.x series (I don't remember exactly which version), I started consistently experiencing the following problem with VirtualBox on my (64-bit) Windows 10 host.  It occurs only with my Windows (10) guests, not with my (Manjaro) Linux guest.

Whenever I reboot the host, after restarting VirtualBox and my VMs, each Windows guest (but not the Linux one) will freeze exactly once, very soon after its first startup.  When it freezes, if I try to close the window, which causes the ""power off / send reset / etc."" dialog box to come up, then whatever I choose, nothing happens; instead, that dialog box also freezes.  If I choose ""power off"", for example, the guest window does not close.  Then I click the 'x' to close either the dialog box or the host window, and it simply disappears (leaving the guest in the aborted state).

After I restart the guest, it remains up for a very long time.  It never freezes again on the second or ensuing startups, until after I reboot the host again.

This has been happening on all 5.2.x versions since the first one on which it happened (alas I don't remember which one that was).  I'm unable to use 6.0.x because of ticket #14366, so I'm not sure whether the bug also exists there or not.  I think I have had at least one VM freeze on 6.0.10 while checking to see whether ticket #14366 still existed there (it does), so perhaps this bug does still exist on 6.0.x, but I didn't run long enough (because of ticket #14366) to confirm that it was the same behavior (i.e. successful long-term operation on the second and ensuing guest reboots, with the problem recurring only after the next host reboot).",rokopt
11606,Poor graphics performance on retina display with VirtualBox 4.2.x,Mac OS X,all,VirtualBox 4.2.10,2019-12-17T17:29:29Z,2019-12-17T17:29:29Z,"I'm happily using VirtualBox on a MacBook Pro with Retina display. However, ever since the release of VirtualBox 4.2 moving windows in a guest OS is very slow, i.e. the movement of the window is considerably lagging behind the pointer movement up to a degree where it gets unusable. This happens on both, a Gentoo Linux VM with a XFCE4 desktop and on a Windows Vista VM. The problem also occurs no matter which resolution the MacBook's retina display is configured to use. Moving windows works fine, however, when I move the VM window to a secondary (non-retina) display.

I tried several 4.2.x releases of VirtualBox including 4.2.10 which all showed the same behaviour. I'm currently using 4.1.24 which seems to be the last version not to have this problem.",cmil
17369,3D Acceleration and Unscaled HiDPI Output bug,Mac OS X,Windows,VirtualBox 5.2.2,2019-12-17T18:43:55Z,2019-12-17T18:43:55Z,"I have three problems.

[1] ""Enabling 3D Acceleration"" causes screen detach. 
      See ""3D Acc.png"".
      Steps to reproduce:
           1) Install a Windows 10 guest on a Mac host.
           2) Enabling 3D Acceleration in Settings > Display > Screen.
           3) Boot the Windows guest.

[2] ""Enable 3D Acceleration"" and ""Use Unscaled HiDPI Output"" causes screen detach and distortion. 
      See ""3D Acc & Unscaled HiDPI.png"".
      Steps to reproduce:
           1) Install a Windows 10 guest on a Mac host.
           2) Enabling 3D Acceleration and Use Unscaled HiDPI Output in Settings > Display > Screen.
           3) Boot the Windows guest.

[3] Using Unscaled HiDPI Output in Integrated Graphics is very slow.
      Steps to reproduce:
           1) Install a Windows 10 guest on a Mac host.
           2) Use Unscaled HiDPI Output in Settings > Display > Screen. 
           3) Uncheck 3D Acc to use Internal Graphics.
           4) Boot the Windows guest.
           5) Set ""Custom Scaling"" to 200% in Settings > System > Display > Scale and layout in Windows.
           6) Log out and in to apply.

      In this state, the virtual machine is very slow and laggy. Can there be any optimizations so that I can use a retina Win 10 guest without any lag?

           7) It goes well if disable ""Custom Scaling"" in the guest and set ""VirtualBoxVM.app"" as ""Open in Low Resolution"" in the host. See ""Low Res.png"".


*** Info ***
Host Device
      MacBook Pro (15-inch, 2017) aka MacBookPro14,3
Host GPU
      Radeon Pro 560 4 GB
      Intel HD Graphics 630 1536 MB
Host OS
      High Sierra 10.13.2 (17C88)
Guest Addition and Extension Pack installed",sjchoi
19174,Guest List disappears abruptly if dragged too far left,Windows,all,,2019-12-19T16:03:35Z,2019-12-19T16:03:35Z,"There is a join between the guest list and the settings where the mouse cursor changes to indicate that the join can be dragged. Dragging this to the left causes the guest list to shrink in width. Eventually the guest list stops shrinking as the mouse continues dragging left. Continue dragging left more than half the width of the now-non-shrinking guest list, and the whole guest list disappears, with no visible indication of any possible way to restore it, or any column to show there's something that can be dragged to the right. 

In Virtualbox.xml, this is shown:

{{{<ExtraDataItem name=""GUI/SplitterSizes"" value=""0,###""/>}}}
('###' being the actual width of the GUI window)

It is still possible to show the list by dragging right from the far left, or issuing this commmand:

{{{VBoxManage setextradata global GUI/SplitterSizes}}}

I don't know if the hard disappearing snap or having no visible sign something is draggable there is by design, but a slightly showing guest list (~20 pixels?) might mitigate the forum users wondering where their guest list has gone.

The hard disappearing snap occurs in 5.2.28, 6.0.14, and 6.1.0. 
5.2.28 does show a thin vertical drag bar.",scottgus1
19175,Getting blank screen while running virtual box session in windows 10 pro,Windows,Windows,VirtualBox 6.1.0,2019-12-20T04:08:42Z,2019-12-20T04:08:42Z,"My VM session is getting stuck at blank screen during startup in windows 10. I can able to run it windows 7 with out any issues but not in windows 10.  

Can someone help me on this.

",amars404
17104,5.1.28 Guest Additions Install fails with gnome-terminal 3.24.2,Windows,Linux,VirtualBox 5.1.28,2019-12-21T13:49:49Z,2019-12-21T13:49:49Z,"The installation of guest additions fails with gnome-terminal version do to deprecated commands in install command.


{{{
localhost ~]$ /bin/gnome-terminal --version
GNOME Terminal 3.24.2 Using VTE version 0.48.3 +GNUTLS
}}}




{{{
localhost ~]$ sudo sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/autorun.sh
}}}
 
Here is the command that fails in the shell script:

{{{
+ BINARY='/run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run'
+ exec /bin/gnome-terminal --title 'VirtualBox Guest Additions installation' -x /bin/sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/runasroot.sh --has-terminal 'VirtualBox Guest Additions installation' '/bin/sh /run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run --xwin' 'Please try running ""/run/media/djohnson/VBOXADDITIONS_5.1.28_117968/VBoxLinuxAdditions.run"" manually.'
Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
Use “-- ” to terminate the options and put the command line to execute after it.
Option “--title” is deprecated and might be removed in a later version of gnome-terminal.
No protocol specified
Unable to init server: Could not connect: Connection refused
Failed to parse arguments: Cannot open display: 
}}}

",septer012
19179,VirtualBox Application Error,Windows,Linux,VirtualBox 6.1.0,2019-12-22T10:01:39Z,2019-12-22T10:01:39Z,"When I try to enable the 3D acceleration on VMSVGA the VM would be instable and eventually crashes with Application Error. 

Example Error message: 

{{{
The instruction at 0x00007FF9A50C019A referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program
}}}

When I disabled the 3D acceleration, the VM works fine.
It would be great if I could enable 3D support, so the UI would render much faster. 
",vboxfan66
19182,Enabling 3D-acceleration hangs boot,Linux,Linux,VirtualBox 6.1.0,2019-12-23T12:49:13Z,2019-12-23T12:49:13Z,"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA, 3D enabled; Guest Additions 6.1.0

Box freezes at boot after boot menu and short appearance of bootup messages. This occurs with bith Chipsets, PIIX3 and ICH9.

Problem disappears when disabling 3D in VM settings.

Possibly a duplicate of Ticket #18914, as under 6.0.10 the problem did not appear and 18914 is for VB 6.0.12.",phaidros
18820,No sound on 5.2.32 Linux guest on Linux host,Linux,Linux,VirtualBox 5.2.32,2019-12-25T08:55:48Z,2019-12-25T08:55:48Z,"I first reported this issue on July 18 here:
https://forums.virtualbox.org/viewtopic.php?f=7&t=93940

For the following weeks I tried playing with various configurations including .asoundrc and asoundrc.conf, the VB audio settings and tools like alsamixer and not a peep. It was extremely frustrating

Sound worked just fine on a quick boot up in qemu. I was about to give up on VB when someone with the identical problem replied to the above thread reporting that reverting to 5.2.18 corrected it. Doing so corrected the issue for me also.

There are logs attached to the above-mentioned thread.  I was also emailing various logs and command output to someone for assistance so may have something else useful in history.

Here are my system specs:

Host: Devuan Jessie 32 bit

Guests: Devuan ascii and Devuan Beowulf also 32 bit, of course.

I was using these VMs for package testing and had not previously tested audio.

Thanks you and hope that you can find the bug and correct it.

",nauved
19119,Windows 3.11 SB16 MPU-41/DMA/386Port/32bit_FileRequest,other,Windows,VirtualBox 6.0.14,2019-12-25T20:00:50Z,2019-12-25T20:00:50Z,"Windows 3.11 SB16 MPU-401 Error
Windows 3.11 SB16 Low-DMA Error
Windows 3.11 386Port Missing Error
Windows 3.11 32bit_File-Request Error

Is there or will there be a solution?

:-)",Ferletyák Károly
19049,Guest resolution changes when moving window between built in Retina and external displays,Mac OS X,all,VirtualBox 6.0.12,2019-12-27T07:54:01Z,2019-12-27T07:54:01Z,"Virtualbox 6 on Mac OSX host with Retina display brings native resolution to guests disregarding user scaling setting in host display properties. This brings a benefit over previous versions of Virtualbox.

Unfortunately, the window dimensions remain linked to the system settings, resulting in all kinds of strange outcomes in common situations with multiple physical or virtual displays.

VM window can have a scaling factor, moving a VM window between Retina and non retina display always triggers display resolution change in the guest. Host OS keeps apparent window size equal, but Virtualbox does not apply different scaling. Things become tricky when the window is on two screens, although this is not very useful use case.

Similar situation occurs when the external display is disconnected and all windows move to the built in display by the system. Or when the host display is closed and all windows move to external screen. Common user expectation is that the virtual screen dimensions would change only if the VM window does not fit the physical screen.

Some improvement can be achieved by deactivation of ""Auto-resize guest display"" but still one needs to manually adjust scaling factor of every window after moving them around.

VM global properties allow to configure scaling factor per monitor. It can be configured only with the monitor is physically attached, so not really useful in a portable environment. With the connection to the reported issue, it is not applied to the window size while moved between host screens.

Another challenging situation is with guest using multiple screens, here the global scaling settings per monitor and guest specific scaling setting per screen require continuous updates when host monitors are connected and disconnected.

Bottom line: When window gets moved between monitors with different scaling factor, this should be transparent (undetectable) by the guest, even with GA installed. Either the window size should get scaled in the same ratio, or the window scaling should change automatically to compensate for the system change of physical window size.

The latter approach was used in versions prior to 6, it would be very useful to enable some kind of a compatibility mode rather than suggesting users to stay with Virtualbox version 5, as seen at https://forums.virtualbox.org/viewtopic.php?f=8&t=91223#p445545
",amk
5732,Many executables refuse to run fom Shared Folders,Windows,Windows,VirtualBox 3.1.0,2019-12-27T16:03:57Z,2019-12-27T16:03:57Z,"About 50% of all Windows executables refuse to run from Shared Folders (vboxsf).

The same executable work perfectly from mounted SMB shares.

Host: Windows XP, Core 2 Q6600, VBox 3.1.0

Guest: Windows 7, 64-bit.

-Technologov, 12.12.2009.",Technologov
19189,"Mouse not captured by Windows 7 guest with VB 6.1.0, 6.0.14 or 5.2.10 on macOS Sierra host",Mac OS X,Windows,VirtualBox 6.1.0,2019-12-29T20:14:12Z,2019-12-29T20:14:12Z,"After migrating from guest Windows 7 to 10 with VB 6.0.14 on host macOS Sierra (which was working fine with guest Windows 7), the full-screen option host F would not work even after installing the guest addition on Windows 10.

So I reverted back to Windows 7 and the full-screen was no longer working.  I tried to uninstall and reinstall the guest addition and it destroyed the mouse integration which is now disabled after starting the VM even though it is enabled on the setting menu. 

Now I can't figure out how to install the guest additions without a working mouse as the it involves clicking on Windows buttons inaccessible from the arrow keys of the mac keyboards which just do not move the cursor from one button to the next. The mouse of the host does not merge with the mouse of the guest. So now I am stuck with a completely unusable VM. I tried to upgrade to VB 6.1.0 and downgrade to 5.2.10 from a backup but still no mouse integration with either of those. 

I tried to change the pointing device from USB tablet to  PS/2 Mouse, the graphic controller to VBoxVGA,  VBoxSVGA and even VMSVGA, the USB controller to 3, 2 and 1, disable my filters, enable and disable 3D and 2D acceleration,  but none of these attempts make neither the mouse integration nor the full screen option work.

Any suggestion?",DamienDeville
734,Guest Additions Deb Packages,other,Linux,VirtualBox 1.5.0,2019-12-30T13:50:53Z,2019-12-30T13:50:53Z,"Could you please consider providing the guest additions as a deb package made available from your repo?

I'd like this because I want to be able to use the features provided by the guest additions in a livecd environment.  The way things are, it's not possible to install the additions in that environment because the installation requires a reboot to take effect.

Or could you address the problem in some other way?",passerby
19183,Auto-resize feature not working,Linux,Linux,VirtualBox 6.1.0,2019-12-31T14:35:14Z,2019-12-31T14:35:14Z,"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA; Guest Additions 6.1.0

Enabling ›auto-resize‹ in guest window (›View‹ – ›Auto-resize Guest Display‹) has no effect. Manual resizing of display works fine.",phaidros
19170,Oracle Linux 6 Fail Window Resize with VMSVGA,Windows,Linux,VirtualBox 6.0.14,2019-12-31T17:45:05Z,2019-12-31T17:45:05Z,"Running Oracle Linux 6 (4.1.12-124.34.1.el6uek.x86_64) with the VMSVGA Graphics Controller selected does not allow the window to be resized keeping it full screen. Using the old VBoxVGA allows the resize of the window without issue.

The machine log is attached to this report.",DonC
19167,Repository metadata broken for Fedora,Linux,other,VirtualBox 6.1.0,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
19193,Opening a photo using Windows Photo app crashes VirtualBox,Windows,Windows,VirtualBox 6.1.0,2020-01-01T20:56:44Z,2020-01-01T20:56:44Z,"If I double click on a .png file in Windows Explorer, VirtualBox crashes. This happens every time I try it, so I switched to using Irfan View to view photos for now.

Host Windows 7 Pro SP1
Guest Windows 10 Pro Build 1909 (18363.535)",Iain Waddell
19194,Cursor Problems,other,Windows,VirtualBox 5.2.32,2020-01-02T11:00:16Z,2020-01-02T11:00:16Z,"Dear Admins,

There is a problem with the cursor where every time I try to use it on the VM it just does not work and the VM is Windows Server 2008. My host operating system is Windows 7",PoppyFamousOfficial
14366,Cursor misscaled in HiDPI mode when using mouse integration,Mac OS X,Linux,VirtualBox 5.0.0,2020-01-02T17:32:33Z,2020-01-02T17:32:33Z,"I am using an OS X 10.10.4 host on a Macbook Pro retina with an archlinux guest, exposing unscaled hidpi output to the guest. When mouse integration is enabled, the cursor is comically oversized -- multiplied by a factor of 2 from the hidpi bug because of my retina display, and another 1.5x from the guest's dpi, giving a 3x size cursor. [https://forums.virtualbox.org/viewtopic.php?f=15&t=68767&p=327418&hilit=retina#p327418 This forum post] suggests it affects other guests too, though I'm not sure about other hosts.

I think the problem is probably that the mouse integration code which implements the hardware cursor is hidpi-unaware and so writes the cursor pixels naively instead of to the underlying device pixels. As a result, the cursor is obviously pixellated and out-of-place with the rest of the guest. Presumably the solution is to simply test whether unscaled mode is on and to then remap the cursor to device pixels.",nitrous
19195,"""Scaled Mode"" makes mouse unusable (lag / slow)",Mac OS X,Windows,VirtualBox 6.1.0,2020-01-03T17:39:10Z,2020-01-03T17:39:10Z,"I am trying to install Windows 98 as a guest in MacOS 10.15.2. The screen is HighDPI, so by default I can't see a thing because the 640x480 virtual screen is way to small (ca. 7 x 5.5 cm).
Full screen mode doesn't change anything, the 7x5.5cm window is just in the center of a large black screen.

""Scaled Mode"" does make the window bigger, so this is ok. However, as soon as the screen is scaled up, the mouse becomes unusable. It lags extremely, and overshoots when stopped.

Obviously, there is no guest support even after Windows 98 is installed. ",T1nue
19196,4K External Monitor greatly distorts GUI,Linux,all,VirtualBox 6.1.0,2020-01-03T18:33:44Z,2020-01-03T18:33:44Z,"I use a 4K TV as an external monitor via HDMI on Ubuntu 18.04. 

When I open VirtualBox, the default window size is huge and doesn't fit on my laptop screen, but the text is a normal size. When I move the window to the external monitor, the font and icon sizes become huge.

In either case, it's extremely difficult and frustrating to use in this condition, so I usually have to unplug the external monitor in order to use VirtualBox. 


*I've been using VirtualBox almost daily for years now; it's the only reason I was able to make the jump to Linux as my daily driver. Thank You.",awsoonn
19197,vmdk not visible after shutdown,Linux,Linux,VirtualBox 5.2.34,2020-01-04T14:29:46Z,2020-01-04T14:29:46Z,"Hi,

I have come acros a problem.
I downloaded mininet-vm from [1].
I opened virtualbox
I selected file
I selected import appliance
The vm booted
I shut down the vm
I closed virtualbox
I opened virtualbox again
I clicked on the ""Mininet-VM"" virtual machine
the prompt with initramfs appeared.
I closed the virtual machine by pressing x from the window
I right clicked the virtual machine
I selected properties
I went to storage
I reselected the vmdk for the VM which came with the mininet-vm from mininet download folder
it worked.

Thanks",cric
17812,VRDEAuth seqfault,other,Windows,VirtualBox 5.2.12,2020-01-06T20:45:29Z,2020-01-06T20:45:29Z,"Here is the message I get in dmesg on a Fedora 28 updated system:

VRDEAuth[40662]: segfault at 7fabb53016c0 ip 00007fabb53016c0 sp 00007fabb5506a08 error 15

Fedora 28 ""uname -a"":

Linux cn4-vcl4 4.16.14-300.fc28.x86_64 #1 SMP Tue Jun 5 16:23:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

It happens regardless of the guest OS (Fedora, Windows 2012 R2, or Windows 10).

The VRDP session freezes or drops after some amount of time, and the only thing we can do is power-cycle the VM to get back the session for a short time.

VBox.log attached

",Stephen Rondeau
19201,"VM changes from good to ""inaccessible"" after about a minute",other,Linux,VirtualBox 6.1.0,2020-01-06T20:54:29Z,2020-01-06T20:54:29Z,"With VirtualBox 6.1 on Fedora 30 and all updates applied, I create a VM and attach an existing virtual disk (Centos 7.6 is the guest operating system) as ""immutable"". I snapshot it twice afterwards, first to make a differencing disk image and next to allow students to roll back their changes. I have been doing this for nearly a decade across many VirtualBox releases, and it usually works. I can list the VMs associated with a user account:

VBoxManage list vms

and it will show the correct name of the VM for a minute or two of repeated ""list vms"", then it will change to ""inaccessible"".

When I revert to 5.2.34, this behavior goes away and the VM remains accessible and usable.",Stephen Rondeau
18296,mtype multiattach does not work,other,other,VirtualBox 6.0.0,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
19206,Crash of VirtualBoxVM running ReactOS 0.4.12 guest on macOS 10.14.6 host,other,other,VirtualBox 6.1.0,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
19207,3d acecleration breaks VMSVGA,other,Linux,VirtualBox 6.0.14,2020-01-08T11:19:43Z,2020-01-08T11:19:43Z,The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).,VincentX
19214,VM is aborted on normal shutdown,Mac OS X,Linux,VirtualBox 6.1.0,2020-01-09T03:36:33Z,2020-01-09T03:36:33Z,"VM is aborted on normal shutdown. The state changes to ""Powered Off"" and then to ""Aborted"".

Last few lines from VBox.log:

02:31:14.797187 E1000#0: TX frames up to 1514: 107844
02:31:14.797197 E1000#0: TX frames up to 2962: 682
02:31:14.797207 E1000#0: TX frames up to 4410: 0
02:31:14.797216 E1000#0: TX frames up to 5858: 0
02:31:14.797226 E1000#0: TX frames up to 7306: 0
02:31:14.797234 E1000#0: TX frames up to 8754: 0
02:31:14.797252 E1000#0: TX frames up to 16384: 0
02:31:14.797276 E1000#0: TX frames up to 32768: 0
02:31:14.797292 E1000#0: Larger TX frames    : 0
02:31:14.797302 E1000#0: Max TX Delay        : 0
02:31:14.799059 GIM: KVM: Resetting MSRs
02:31:14.804435 Changing the VM state from 'DESTROYING' to 'TERMINATED'
02:31:14.811282 Console: Machine state changed to 'PoweredOff'
02:31:14.812640 GUI: Request to close Runtime UI because VM is powered off already.
02:31:14.812665 GUI: Passing request to close Runtime UI from machine-logic to UI session. 
",crvi
19216,"When installing Ubuntu with finnish language, can no see continue tab",Windows,Linux,VirtualBox 6.0.14,2020-01-10T09:49:10Z,2020-01-10T09:49:10Z,"Problem description:
When installing ubuntu-18.04.3-desktop-amd64 with language set to Finnish (Suomi) then next setup windows don't show ""continue"" button. I can continue using Tab button, so it means that continue button is there but it is not visible

Enviroment
Windows machine with 8G mem 250Gb SSDdisk and i5 Intel
Virtual machine has 2G memory and 15Gb disk allocated",Fugit185
10844,Failed to attach the USB device to virtual machine,Windows,Linux,VirtualBox 4.1.18,2020-01-10T14:18:26Z,2020-01-10T14:18:26Z,"64bit Windows 7 host, various 32 and 64 bit Linux guest distributions, 4.1.18r78361 extensions package installed.

Cannot get USB device to be recognized by guest (check via lsusb). Sometimes, selecting the device in the Devices->USB Devices menu just has no effect (entry doesn't get checked), and sometimes I get the following:


Failed to attach the USB device Yubico Yubikey II [0224] to the virtual machine pws-deb6.

USB device 'Yubico Yubico Yubikey II' with UUID {3c66074d-0580-47fd-921e-81da094dd391} is busy with a previous request. Please try again later.

Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
---

Notes:
- Other USB devices can be successfully attached.
- Playing with the USB filter settings has no effect.
- On another 64bit Windows 7 host, running the same versions of VirtualBox and guest, the same (physical) device is successfully passed through to the guest. (Unfortunately, I need this working on the machine that fails...).

Please advise.

P.S. The device vendor has offered to provide assistance, including device samples.",Rony Shapiro
19217,Mouse integration setting is not persistent,Windows,Linux,VirtualBox 6.1.0,2020-01-11T16:14:00Z,2020-01-11T16:14:00Z,"Mouse integration is re-enabled at every VM boot. The setting is not persistent and can not be disabled by default.

Host is Windows 10 Professional
Guest is Ubuntu 18.04 LTS

Oracle VM VirtualBox Extension Pack is installed on host.
Guest Additions Pack is installed on guest.

To reproduce:
  1. Boot Ubuntu 18.04 LTS guest.
  2. Disable mouse integration through view menu.
  3. Reboot guest.

Expected: Mouse integration remains disabled.

Actual: Mouse integration is enabled.

I do not know of a workaround. Mouse integration must be manually disabled every time the VM is started.",XK
19218,The driver detected an internal driver error on \Device\VBoxNetLwf.,Windows,other,VirtualBox 6.1.0,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
18545,Can't enter vdisk size with keyboard,Mac OS X,all,VirtualBox 5.2.26,2020-01-12T20:19:35Z,2020-01-12T20:19:35Z,"I can't enter the vdi disk size with the keyboard. I select the proposed value with the mouse and start to type the desired value. Only the first character appears and the bell rings for any other character I try to enter. I was creating a new Open Media Vault virtual machine (Debian x86_64). This happens also with CentOS guests. I can use the slider.

VirtualBox Version 5.2.26 r128414 (Qt5.6.3)
Mac OS X High Sierra 10.13.6 (17G6030)
Apple Wireless keyboard (bluetooth) (no numeric keypad, batteries at 100%)
Apple Wireless trackpad (bluetooth) (batteries at 10%)",Patrick Timmons
19187,"USB crashes VBox 6.0, 6.1",Windows,Windows,VirtualBox 6.1.0,2020-01-13T12:15:06Z,2020-01-13T12:15:06Z,"When enabling USB filter for:
 Busch-Jaeger Elektro GmbH KNX-USB Interface (Flush mounted) [0101]
 vendor id 145c
 product id 1330
 revision 0101
on host W7 home premium sp1, guest W7 home premium sp1, with vbox 6.0, and latest 6.1. Vbox 6.1 at least sends application error message: ""the guest machine crashes with instruction at 0xdd0069fe referenced memory at 0x00000146. The memory could not be read."" whereas vbox 6.0 was simply aborting the guest machine without message.

It worked in Vbox 5.2.2 with same host, guest Windows XP.

",Yves P
18591,USBIP from/to NAS Sinology not working any more,Linux,Windows,VirtualBox 5.2.28,2020-01-13T12:17:10Z,2020-01-13T12:17:10Z,"Hi,
I've using Oracle VirtualBox on Linux Mint 18.04 host for over a year, to run a Windows XP printing through USBIP on a 3D printer plugged onto a Synology 216j with VirtualHere USBIP server.

Everything worked fine until Version 5.2.26 r128414 (Qt5.6.1).

After upgrading to 5.2.28, my XP could still see USBIP ports but the Up! 3D application under XP could not see the printer as connected.

After upgrading to virtualbox 6.0, the VM could not see the USBIP port.

Coming back to 5.2.26 make it work again.

Best regards,
Jean-Marc",Jean-Marc au Boulot
19204,Virtualbox Manager Crashes when moved to 2nd monitor on Linux Host.,other,other,VirtualBox 6.1.0,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
19219,Serial port access via USB dropping lots of data...,Windows,Linux,VirtualBox 6.1.0,2020-01-15T04:44:08Z,2020-01-15T04:44:08Z,"Receiving data from a serial uart device seems to drop lots of data.

* Host: Windows 10 with VirtualBox 6.1 with extension pack
* Guest: Xubuntu 18.04 with guest additions
* FTDI serial USB module connected to USB port and passed through to Xubuntu
* FPGA connected to the FTDI module sending serial data at 115200 baud. The data is sent in 64-byte chunks, one chunk per second (it's a test project and that's just what I've selected for testing).

I'm finding that:

* Xubuntu on a real machine - works fine.
* Xubuntu in a VirtualBox VM - fails.

Under VirtualBox, I get maybe 16 bytes out of every 64 byte chunk and occasional data corruption (as in bytes that I know aren't being transmitted showing up).

The commands I'm using the dump the serial port are:

$ sudo ssty -F /dev/ttyACM1 115200 raw -echo
$ sudo xxd /dev/ttyACM1

Attached screen shot shows correct serial dump (under windows), on the right, the messed up data via VirtualBox.

VirtualBox Log also attached",toptensoftware
19224,get_Machines not working in 6.1 API,Windows,all,VirtualBox 6.1.0,2020-01-15T04:55:23Z,2020-01-15T04:55:23Z,"Originally posted to forum (here: https://forums.virtualbox.org/viewtopic.php?f=34&t=96233), lodging as a bug report since not resolved....

---

I'm the developer of VBoxHeadlessTray (see here: https://www.toptensoftware.com/vboxheadlesstray). I'm trying to get it working with the latest 6.1 SDK but I'm finding that after calling get_Machines and going through the returned array, the IUnknown for the objects are returned correctly from SafeArrayGetElement, however calling QueryInterface for IMachine fails with E_NOINTERFACE.

The IID_IMachine I'm using is {85632C68-B5BB-4316-A900-5EB28D3413DF}

Running on Windows 10, guest OS is not applicable.
",toptensoftware
19205,Mouse loses focus when enabling second virtual screen,Linux,Windows,VirtualBox 6.1.0,2020-01-15T14:59:28Z,2020-01-15T14:59:28Z,"I have created a Windows 10 1909 guest running Virtualbox 6.1.0 r135406 guest additions with two virtual screens on an Ubuntu 18.04 (4.15.0-74-generic) host running Virtualbox 6.1.0 r135406. The mouse loses focus when you enable the second virtual screen: if you choose 'Extend these displays' from Display settings you cannot click on 'Keep changes'. The mouse pointer seems to get offset, you can click on the Start Menu in the first virtual screen but when you hover over the Start menu items the mouse pointer is offset: the Calculator gets highlighted but the mouse pointer is shown above it. When you 'click on' the Calculator while it is highlighted it launches. You can move the mouse to the second virtual screen but nothing happens when you click anywhere.

Regards,
GW",gwiesenekker
19115,"Guest Windows 7 Aero don't working since v.6.0.14 (VboxSVGA, 3D, 2D active)",Linux,Windows,VirtualBox 6.0.14,2020-01-15T19:15:25Z,2020-01-15T19:15:25Z,"Hi, after Update to Virtualbox 6.0.14 witch Extensions, my Guest Windows 7 Aero don't working, the Startmenu and Taskbar are blur, I can't see the items. The same in two different W7-guests. Guest-Tolls are installed v.6.0.14 with 3d-experimental driver. If I switch to VBoxVGA, all functioning perfect. My Host is Ubuntu 18.04. With Virtualbox v.6.0.12 were all W7-guests OK.

Please help
Best regards
Peter",user324
19234,VBoxClient --clipboard terminates silently,Windows,Linux,VirtualBox 6.1.2,2020-01-16T10:06:59Z,2020-01-16T10:06:59Z,"VBoxClient --clipboard no longer runs on my Debian VM. If I run it by hand:


{{{
$ VBoxClient -v --clipboard -f 
Shared Clipboard: Starting X11 event thread
Shared Clipboard: Stopping X11 event thread ...
Shared Clipboard: X11 event thread terminated successfully
Error connecting to host service, rc=VERR_NOT_IMPLEMENTED
Service terminated abnormally with VERR_NOT_IMPLEMENTED
Running service failed: VERR_NOT_IMPLEMENTED
}}}



Previously reported at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946843> and <https://forums.virtualbox.org/viewtopic.php?f=3&t=96309>",Sam Morris
19208,3d acecleration breaks VMSVGA,Windows,Linux,VirtualBox 6.0.14,2020-01-16T10:33:20Z,2020-01-16T10:33:20Z,The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).,VincentX
18893,Enhancement: CLI flag to sleep host for N seconds,all,other,VirtualBox 6.0.10,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
19221,"VBox ""crashes"" on restart",Mac OS X,Linux,VirtualBox 6.1.0,2020-01-17T09:25:52Z,2020-01-17T09:25:52Z,"After a big Kali VM Update VBox crashed when restarting

{{{VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)}}}
(around line 1417 in the attached log file)

running on macOS High Sierra 10.13.6. VBox asked me to report the crash :-)

Restarting worked and the guest now runs.

VBox 6.1.0 seems to be pretty unstable. I had a handful of freezes the last two days (hadn't used it for some time). 
Especially when I resized the guest window
The image was previously an VMWare image which I converted to OVA and imported in VBox. The Graphics Controller was initially set to VBoxSVGA which lead to an Invalid Setting Detected warning (therefore I changed it)
",C.L
19239,After updating from VB 6.1.0 to 6.1.2. start of guests fails with NS_ERROR_FAILURE (0x80004005)created,Linux,Windows,VirtualBox 6.1.2,2020-01-17T13:03:20Z,2020-01-17T13:03:20Z,"Hi,
my host ist Debian bullseye (5.4.0-2-amd64), the guests are Windows 10 (actual version). When I start a guest, I get the error NS_ERROR_FAILURE (0x80004005). The VBOX.Log is attached. Going back to 6.1.0 everything works fine - I have attached the corresponding VBOX.Log.1.

The VBOX.log.1 from version 6.1.0 continues after

""00:00:01.161562 PGM: pgmR3PoolInit: cMaxPages=0x500 cMaxUsers=0xa00 cMaxPhysExts=0xa00 fCacheEnable=true"" 

with 
 
00:00:01.815025 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=62 u32UpdateIntervalNS=16000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x1b cCpus=4
00:00:01.815087 TM: GIP - u64CpuHz=2 659 999 145 (0x9e8c5da9)  SUPGetCpuHzFromGip => 2 659 999 145
00:00:01.815102 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815110 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815116 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
00:00:01.815124 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x5 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2659999145(*) cErrors=0
",Dr. Michael Hälsig
19240,"windows CE handheld will not connect VirtualBox 6.1, MacOS X host, Windows 7 SP1 guest",Mac OS X,Windows,VirtualBox 6.1.2,2020-01-17T19:28:06Z,2020-01-17T19:28:06Z,"This is identical to bug report #12489 that has been closed as obsolete.

I've been using Parallels but didn't  want to continue to upgrade to keep up with MacOS so thought I'd try virtualBox.  This all works fine on Parallels up to and including their current version.  

when I try to connect my Windows CE handheld to the system I get an error that the Microsoft USBSync did not install properly and that the device is not connected.  Also an error from the driver status that the ""device cannot start (code 10)""


Same install of Windows 7 from the same CD and the same downloaded Microsoft Windows Mobile Device Center/drivers on Parallels works fine.
",billj
13380,When I try to look for updates I get Wrong SSL certificate format,Linux,other,VirtualBox 4.3.14,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
19123,VM Aborts On Laptop Suspend OR Machine Pause,Windows,Linux,VirtualBox 6.0.14,2020-01-18T16:29:41Z,2020-01-18T16:29:41Z,"Hello,

Recently updated to 6.0.14 on Windows 10, hosting a Centos guest.

Two scenarios trigger a VM abort, maybe 50% of the time:
[1] pause VM (Machine -> Pause)
]2] send laptop to sleep

A dialog will pop up (immediately for [1]  and on resume for [2]).

Attaching logs and a screenshot of the dialog.

Cheers,
yato
",yato
19223,VirtualBox Extension Pack 6.0.16 installation failure,Windows,Linux,VirtualBox 6.0.14,2020-01-19T21:32:23Z,2020-01-19T21:32:23Z,"Following 100% download of the Extension Pack for version 6.0.16, and during the verifying VirtualBox Extension Pack... the error message is displayed: ""The network operation failed with the following error: During network request: Url not found on the server."" I have attached the screenshot of this. Despite many repeated attempts, the error persists.",NickD
18789,serial port problems with VB 6.0.10,other,Windows,VirtualBox 6.0.10,2020-01-20T08:52:20Z,2020-01-20T08:52:20Z,"I had to set COM1 to raw file to get the windows guests to completely boot. It's like the boot up is in a boot loop if I set COM1 for Host device. Also, I have the second comport set to user defined but it works OK when set for Host device but there are occasional crashes where the guest can't see the comport. I don't have this problem with VB 5.2.x. see attached files",eelstrebor
18539,Serial Interface doesn´t work correctly,Windows,Windows,VirtualBox 6.0.4,2020-01-20T08:53:09Z,2020-01-20T08:53:09Z,"Hi,

I installed VB 6.0.4 (Host W10 17763.379) and I use an old equiqment to transfer data to a virtual XP using the serial interface. I am using Port 1, COM1, Host-Interface, Pipe/Socket aktivated, Adresse COM1.
The transfer starts but after a fewsecond it terminats.
If I downgrad to VB 5.2.26 it work correctly.

Sorry about my bad enlish.

Best regards
Jürgen",motog
19212,Unexpected exception: std::bad_alloc [St9bad_alloc],Mac OS X,other,VirtualBox 6.1.0,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
15810,VirtualBox Manager has stopped working when adding USB hard disk in Storage,Windows,Windows,VirtualBox 5.1.4,2020-01-20T13:43:17Z,2020-01-20T13:43:17Z,"I stumbled upon a bug in the GUI.

To reproduce, go to VM Settings.
1) I start with no controllers in the Storage Tree.
2) Add USB Controller.
3) Right click the new controller -> Add Hard Disk

Crash.

",danf84
19215,Fedora 31 Workstation - Hang and Crash,Windows,Linux,VirtualBox 6.1.0,2020-01-20T13:46:23Z,2020-01-20T13:46:23Z,"The  laptop lid was closed but the PC was still running and when I opened up the lid and tried to access the Fedora 31 Workstation VM, the UI didnt response to keyboard/mouse.   I tried to select from the menu ACPI Shutdown and there was no reponse and finally tried Input->Keyboard->Insert CTRL+ALT+DEL.  The VM started shutting down and crashed either coming back up.",Aquis7
14231,"Unscaled HighDPI Output Graphics Corruption (OSX Host, Win10 Guest, VB5RC2)",Mac OS X,Windows,,2020-01-20T14:25:17Z,2020-01-20T14:25:17Z,"When ""Use Unscaled HighDPI Output"" is enabled on a Windows 10 Guest graphics corruption occurs. It jumps between rendering the native resolution (2560x1600) and scaling/cropping it to 1/4 that. Mouse movement affects the graphical glitches. Guest additions are installed, Paravirt interface is Hyper-V and 2d+3d acceleration are enabled.

Guest: Windows 10
Host: Mac OSX 10.10.4
Virtualbox: 5RC2 (occurred in RC1 too)

",Benjamin Roberts
19242,vdi file destroyed,Windows,Linux,VirtualBox 6.0.14,2020-01-20T15:47:06Z,2020-01-20T15:47:06Z,"
So my .vdi has become empty - 0B size, checked with hex viewer. There is E_ACCESSDENIED entry at the very end of log from last proper run of my machine (previous log does not have this). Also modification date on the vdi file matches that of said log.

I understand that this error may be not reproducible but seems to me like a possible very major flaw. I have never tampered with disk file in any way and didn't notice any similar incidents on my hardware. 

I'm on windows 8.1, client was Linux Manjaro.

Thank you
",pk6610
19238,Boot time for linux guest is about 50% slower on 6.1.2  compared to 5.2.34,Windows,Linux,VirtualBox 6.1.2,2020-01-20T18:33:01Z,2020-01-20T18:33:01Z,"Host : Windows 10 1903 (10.0.18362.535)

I have been using linux mint 19.2 installed on Virtualbox 5.2.34 for a while.
I just recently upgraded virtualbox to the latest version 6.1.2.

The boot time on 5.2.34 is in average : 1.26  (1 minute and 26 seconds )
The boot time on 6.1.2  is in average : 2.13  (2 minutes and 13 seconds )",DanMc01
19246,Critical error immediately on startup,Mac OS X,Windows,VirtualBox 6.1.2,2020-01-21T11:01:12Z,2020-01-21T11:01:12Z,"Start button fails within seconds. Failed on R 6.0 so I tried installing 6.1 with same result. As far as I'm aware nothing changed on my system between the last day it worked and the day it failed. 
Please help.",aj_m
19247,Accessability Bug: Certain user interface elements are not accessible with the keyboard.,other,other,VirtualBox 6.0.14,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
19248,Accessability Bug: Certain text does not meet the minimum color contrast ratio,Windows,all,VirtualBox 6.0.14,2020-01-21T14:10:35Z,2020-01-21T14:10:35Z,"Defect:  Certain text does not meet the minimum color contrast ratio. 
Description:  Please see example below for details.
Notes: 
•	Testing was performed using the Color Contrast Analyzer v2.2a.
•	This defect may exist elsewhere within the application.

Expected result:  The minimum contrast ratio for the visual presentation of text and image of text is expected to be at least 4.5:1, or 3:1 for text that is 18 points or larger, or 14 points bolded.
Reference: This defect is a failure against Section 508, 1.4.3 – Contrast (Minimum).
For more information, visit: http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html.
Steps to reproduce: 
1.	Open “Virtual Box”.
2.	Check the contrast ratio for the “Tools” text. (Highlighted below)

Notice that the contrast ratio for the Tools Menu is 2:4:1. Instead, the minimum contrast ratio for the visual presentation of text is expected to be at least 4.5:1, or 3:1 for text that is 18 points or larger or 14 points’ bolded.
 ",moshekaplan
19250,processor execution cap is broken for single cpu vms,Windows,other,VirtualBox 6.0.16,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
11857,"medium type ""dvddrive"" cannot be used via a readonly iscsi target",Linux,all,VirtualBox 4.2.12,2020-01-21T21:23:06Z,2020-01-21T21:23:06Z,"ISO mediums exposed in a {{{dvddrive}}} cannot be used over iSCSI when the target is readonly.

According to [http://www.virtualbox.org/manual/ch05.html#hdimagewrites documentation], CD/DVD images are created read-only, but this doesn't seem to be the case, at least with iSCSI.  I need access to a series of readonly iscsi targets that are exposing ISOs, but this does not seem possible unless I start snapshotting guests after the medium is added, and before it is turned on.


A sample target I am trying to connect to
{{{
ryan@TehDualLinux:~$ sudo tgtadm --lld iscsi --mode target --op show
Target 2: iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00020000
            SCSI SN: beaf20
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags: 
        LUN: 1
            Type: disk
            SCSI ID: IET     00020001
            SCSI SN: beaf21
            Size: 1013 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: Yes
            Backing store type: rdwr
            Backing store path: /usr/local/storage/linuxmint-14.1-mate-dvd32bit.iso
            Backing store flags: 
    Account information:
    ACL information:
        ALL

}}}



Adding the above target to VirtualBox
{{{
VBoxManage storageattach ""NewPasswordWindowsReadOnly2"" --storagectl ""MyController"" --port 1 --device 0 --type dvddrive --medium iscsi --server localhost --target ""iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b"" --lun 1 --tport 3260
}}}



It was added successfully.
{{{
vboxmanage list hdds

...
UUID:        2d4790e0-678b-4fc0-b529-32aebfec6f97
Parent UUID: base
Format:      iSCSI
Location:    localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1
State:       created
Type:        normal
Usage:       NewPasswordWindowsReadOnly2 (UUID: e86ffe75-2412-4aa6-9b36-3a0c0f3e4780)
...

}}}


After we try and turn the machine on, it fails with:
{{{
Failed to open a session for the virtual machine NewPasswordWindowsReadOnly2.
VD: error VERR_VD_IMAGE_READ_ONLY opening image file 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' (VERR_VD_IMAGE_READ_ONLY).
Failed to open image 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' in read-write mode rc=VERR_VD_IMAGE_READ_ONLY (VERR_VD_IMAGE_READ_ONLY).
Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY).
AHCI: Failed to attach drive to Port1 (VERR_VD_IMAGE_READ_ONLY).
}}}

Steps to replicate:

1.  Make an iSCSI target with any iSCSI software and make it readonly
2.  Add the target to your guest via vboxmanage stoargeattach and do not take snapshots
3.  Turn on the guest.

Summary:

- If you remove the readonly flag on the iscsi target everything works perfectly (even through VirutalBox does not need write on this medium)
- If you take a snapshot (thus a differencing medium is created), everything works perfectly
- If you add the DVD as multiattach instead of ""normal"", it creates a differencing medium, and everything works perfectly.
- If you add the medium normally, even though VirtualBox's documentation claims it is readonly, it tries to access the medium as read/write.",rshaw
19252,host Win10 crashes when guest Win10 reboots after update,Windows,Windows,VirtualBox 6.0.14,2020-01-22T03:06:49Z,2020-01-22T03:06:49Z,"BSOD
DRIVER_IRQL_NOT_LESS_OR_EQUAL
VBoxDDR0.r0 

Happens only on guest restarts after it installed windows updates",EugeneK
19253,Guest Additions not installing on Win 10 Pro 1903,other,other,VirtualBox 6.1.2,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
19233,No recent-items jumplist on windows10,Windows,Linux,VirtualBox 6.1.2,2020-01-22T09:33:23Z,2020-01-22T09:33:23Z,"I am using virtualbox on Windows. On windows7, when I ""pinned"" it to start menu, it was shown at the top of unfolded start menu, and when hovered by mouse cursor, a sub-menu unfolded with recent virtual-machines. Same as recent documents for MS word or simillar. AFAIK theese are called ""jump-lists"".

After migrating on Windows10, I can see that mechanics are changed a bit - I can of course pin an item to start menu, and most of those pinned items also support some ""recent items"" thingies, but it now requires a right-click on the pinned item.. 
Unfortunately, for virtualbox it doesnt work - when right-clicking on the pinned icon I, a menu unfolds with only below options:
* unpin
* resize
* more
* uninstall
",michal.mulawa
19236,6.0.16 Update delivers 6.0.15 and then breaks the Extension installs,Mac OS X,Windows,VirtualBox 6.0.16,2020-01-22T13:25:08Z,2020-01-22T13:25:08Z,"Was prompted to download 6.0.16 which I did and installed...
After install tried to install the extensions.. extension installer reported requires 6.0.16 but installed is 16.0.15...

After various attempts to remove or downgrade resorted to deleting the Mac VirtualBox app from Applications and downloading and reinstalling 6.0.14 and then the 6.0.14 extensions...

",Serenak
19258,import of freshly exported appliance fails,Mac OS X,Windows,VirtualBox 6.1.2,2020-01-22T19:24:02Z,2020-01-22T19:24:02Z,"i am migrating from one host to another.
on OLD machine, I export using standard/default settings in 6.0 (Mac OS 10.15)
i transfer to NEW machine via usb-Disk
i call import with default settings.
a popup appears declaring that appliance <somename>.ova could not be imported. Error Code  NS_ERROR_INVALID_ARG (0x80070057)

There seems to be a size dependency:
i was able to import one appliance with size 5,62GB, several others larger than 10GB all fail.

There is of course no space problem on the NEW machine, there are more than 500GB free.
FWIW, i detect nothing of interest in the system logs.

 ",MatsWolpers
18943,High DPI support,Windows,Linux,VirtualBox 6.0.12,2020-01-23T22:17:10Z,2020-01-23T22:17:10Z,"High DPI support has always been a little wonky, but after upgrading to 6.0, it has gotten worse.

I use my high DPI laptop with a normal external monitor.  My laptop is set to 250% zoom and the external monitor is set to 100% zoom.  When I start Virtualbox Manager with this set up, it looks okay for my laptop, but if I drag it to the external monitor, everything is too small.  If I set my laptop to 100% zoom, start Virtualbox Manager, and then change the zoom back to 250%, it looks great on my external monitor, but everything is too big on my laptop.",morriw
19260,Macbook doesnot open virtual machine,Mac OS X,Windows,VirtualBox 6.0.16,2020-01-24T00:08:59Z,2020-01-24T00:08:59Z,"I have got the following error always on my Macbook.   Headless is OK, and other mac(MacPRO) can open the same virtual machine.

-----------------------------------------------------
仮想マシン""Windows 10 Pro""のセッションを開けませんでした。

The virtual machine 'Windows 10 Pro' has terminated unexpectedly during startup because of signal 11.

終了コード : NS_ERROR_FAILURE (0x80004005)
コンポーネント: MachineWrap
インターフェース: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
-----------------------------------------------------

Process:               VirtualBoxVM [13245]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.15 (6.0.15)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [12917]
Responsible:           VirtualBoxVM [13245]
User ID:               501

Date/Time:             2020-01-24 09:05:22.750 +0900
OS Version:            Mac OS X 10.13.6 (17G11008)
Report Version:        12
Anonymous UUID:        7C4097BE-7489-5B43-4421-C7BC46185EEE


Time Awake Since Boot: 38000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0:
--> 
    __TEXT                 000000010372d000-000000010374f000 [  136K] r-x/rwx SM=COW  ~2 [/Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           	000000000000000000 0 + 0
1   com.apple.CoreImage           	0x00007fff48219d81 -[CIKernel _initWithFirstKernelFromString:withCruftCompatibility:] + 108
2   com.apple.CoreImage           	0x00007fff48033699 +[CIColorKernel kernelWithString:] + 45
3   com.apple.CoreImage           	0x00007fff48033651 __31-[CIBlendWithAlphaMask _kernel]_block_invoke + 36
4   libdispatch.dylib             	0x00007fff6f502db8 _dispatch_client_callout + 8
5   libdispatch.dylib             	0x00007fff6f502d6b dispatch_once_f + 41
6   com.apple.CoreImage           	0x00007fff4803362b -[CIBlendWithAlphaMask _kernel] + 105
7   com.apple.CoreImage           	0x00007fff481eaa67 -[CIBlendWithMask outputImage] + 989
8   com.apple.Foundation          	0x00007fff4971986c -[NSObject(NSKeyValueCoding) valueForKey:] + 284
9   com.apple.coreui              	0x00007fff5b579fe5 -[CUIShapeEffectStack standardEffectCompositeWithShapeImage:] + 2348
10  com.apple.coreui              	0x00007fff5b5a6f51 CUIRenderer::CreateImageByApplyingEffectsToImage(CUIDescriptor const*, long, __CFArray const*, CGImage*, double, unsigned char, unsigned char, CGBlendMode&) const + 7841
11  com.apple.coreui              	0x00007fff5b5ab965 CUIRenderer::CreateImage(CGRect, long, CUIDescriptor const*, unsigned char, CGImage**, long long*, unsigned char*, CGBlendMode*) const + 11137
12  com.apple.coreui              	0x00007fff5b563eac CUIRenderer::DrawImage(CGRect, long, CUIDescriptor const*) const + 160
13  com.apple.coreui              	0x00007fff5b56353f CUICoreThemeRenderer::DrawMenuTitle(CUIDescriptor const*, CUIReturnInfo&) + 837
14  com.apple.coreui              	0x00007fff5b56257e CUIRenderer::Draw(CGRect, CGContext*, __CFDictionary const*, __CFDictionary const**) + 1824
15  com.apple.coreui              	0x00007fff5b561e2e CUIDraw + 278
16  com.apple.HIToolbox           	0x00007fff468de402 _HIThemeCUIDrawWithOptions + 81
17  com.apple.HIToolbox           	0x00007fff468de396 _HIThemeCUIDrawWithRenderer + 174
18  com.apple.HIToolbox           	0x00007fff468dd7e7 _HIThemeDrawAppleMenuTitle + 506
19  com.apple.HIToolbox           	0x00007fff468d9fbe HIMenuBarView::DrawOnce(CGRect, CGRect, bool, bool, CGContext*) + 1150
20  com.apple.HIToolbox           	0x00007fff468d9a46 HIMenuBarView::DrawSelf(short, __HIShape const*, CGContext*) + 582
21  com.apple.HIToolbox           	0x00007fff468d9482 HIMenuBarView::DrawWithoutCustomization(short, __HIShape const*, CGContext*) + 82
22  com.apple.HIToolbox           	0x00007fff468d941a HIMenuBarView::DrawingDelegateHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 236
23  com.apple.HIToolbox           	0x00007fff468bd904 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1541
24  com.apple.HIToolbox           	0x00007fff468bcc4d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 374
25  com.apple.HIToolbox           	0x00007fff468bcac3 SendEventToEventTargetWithOptions + 45
26  com.apple.HIToolbox           	0x00007fff468d8fbb HIView::SendDraw(short, OpaqueGrafPtr*, __HIShape const*, CGContext*) + 337
27  com.apple.HIToolbox           	0x00007fff468d89d7 HIView::RecursiveDrawComposited(__HIShape const*, __HIShape const*, unsigned int, HIView*, CGContext*, unsigned char, double) + 571
28  com.apple.HIToolbox           	0x00007fff468d8c57 HIView::RecursiveDrawComposited(__HIShape const*, __HIShape const*, unsigned int, HIView*, CGContext*, unsigned char, double) + 1211
29  com.apple.HIToolbox           	0x00007fff468d842c HIView::DrawComposited(short, OpaqueGrafPtr*, __HIShape const*, unsigned int, HIView*, CGContext*) + 874
30  com.apple.HIToolbox           	0x00007fff468d80b0 HIView::Render(unsigned int, CGContext*) + 54
31  com.apple.HIToolbox           	0x00007fff468d776b WindowData::PrepareForVisibility() + 153
32  com.apple.HIToolbox           	0x00007fff468d6eab _ShowHideWindows + 275
33  com.apple.HIToolbox           	0x00007fff468d6d92 ShowHide + 35
34  com.apple.HIToolbox           	0x00007fff468c6af9 MBWindows::GetWindowOnDisplay(unsigned int, unsigned char) + 299
35  com.apple.HIToolbox           	0x00007fff468c6893 MenuBarInstance::ForEachWindowDo(unsigned char, bool (OpaqueWindowPtr*, unsigned int) block_pointer) + 167
36  com.apple.HIToolbox           	0x00007fff46a571bc MenuBarInstance::Hide(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char*, unsigned char) + 260
37  com.apple.HIToolbox           	0x00007fff468c6248 MenuBarInstance::UpdateAggregateUIMode(MenuBarAnimationStyle, unsigned char, unsigned char, unsigned char) + 800
38  com.apple.HIToolbox           	0x00007fff468c5e63 MenuBarInstance::ForEachMenuBarDo(void (MenuBarInstance*) block_pointer) + 47
39  com.apple.HIToolbox           	0x00007fff468c5df9 UpdateAllAggregateUIModes(MenuBarAnimationStyle, unsigned char) + 131
40  com.apple.HIToolbox           	0x00007fff468c5d50 SetSystemUIMode + 169
41  com.apple.AppKit              	0x00007fff44e69e4d -[NSApplication _setPresentationOptions:instance:flags:] + 1406
42  libqcocoa.dylib               	0x000000010a1c5ab9 QCocoaIntegration::QCocoaIntegration(QStringList const&) + 1433
43  libqcocoa.dylib               	0x000000010a1c416e QCocoaIntegrationPlugin::create(QString const&, QStringList const&) + 78
44  org.qt-project.QtGuiVBox      	0x000000010453afd6 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) + 198
45  org.qt-project.QtGuiVBox      	0x00000001045484f5 QGuiApplicationPrivate::createPlatformIntegration() + 2549
46  org.qt-project.QtGuiVBox      	0x00000001045494bb QGuiApplicationPrivate::createEventDispatcher() + 27
47  org.qt-project.QtCoreVBox     	0x000000010412c82e QCoreApplicationPrivate::init() + 1790
48  org.qt-project.QtGuiVBox      	0x0000000104544f71 QGuiApplicationPrivate::init() + 49
49  org.qt-project.QtWidgetsVBox  	0x0000000104afdd4e QApplicationPrivate::init() + 14
50  VirtualBoxVM.dylib            	0x0000000103df577b TrustedMain + 923
51  org.virtualbox.app.VirtualBoxVM	0x0000000103730d36 0x10372d000 + 15670
52  libdyld.dylib                 	0x00007fff6f53c015 start + 1

Thread 1:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 2:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f85420e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 5:
0   libsystem_kernel.dylib        	0x00007fff6f68d28a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff6f854009 _pthread_wqthread + 1035
2   libsystem_pthread.dylib       	0x00007fff6f853be9 start_wqthread + 13

Thread 6:
0   libsystem_pthread.dylib       	0x00007fff6f853bdc start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x00007fca1d749490  rbx: 0x00007fffa187fc78  rcx: 0x0000000000000001  rdx: 0x0000000000000307
  rdi: 0x00007fffa7f6aad0  rsi: 0x0000000000000304  rbp: 0x00007ffeec4cea20  rsp: 0x00007ffeec4ce918
   r8: 0x000000000000000d   r9: 0x00000000fffffff3  r10: 0x00007ffeec4d2b88  r11: 0xffffffffffffff56
  r12: 0x00007fca1d744c30  r13: 0x00007fca1d748d10  r14: 0x0000000000000000  r15: 0x00007fff6e910e80
  rip: 0x0000000000000000  rfl: 0x0000000000010202  cr2: 0x0000000000000000
  
Logical CPU:     2
Error Code:      0x00000014
Trap Number:     14


Binary Images:
       0x10372d000 -        0x10374eff7 +org.virtualbox.app.VirtualBoxVM (6.0.15 - 6.0.15) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10376a000 -        0x103ccb5e7 +VBoxRT.dylib (0) <444F2BE4-CFE1-30FC-AD97-143570F6FCB2> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x103dee000 -        0x103edbff7 +VirtualBoxVM.dylib (0) <AEDB7533-264F-3FC3-B470-25ACCDDB8EDD> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x103f34000 -        0x103f3dff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x103f46000 -        0x10446dff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x104523000 -        0x1049feff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x104af2000 -        0x104ffbfff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x10515e000 -        0x105192fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x1051b6000 -        0x1051f5fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x105218000 -        0x10526bfff +VBoxDDU.dylib (0) <E4AAEA3D-1208-36E2-9A3C-B66067285187> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x105277000 -        0x1054f9fff +VBoxVMM.dylib (0) <DAA0ACC4-A8AE-38A5-922F-2336A21B876E> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x10561e000 -        0x105668adf  dyld (551.5) <ACC6AC7F-EAD9-340E-B2A8-AD26FE5B387B> /usr/lib/dyld
       0x1056bc000 -        0x1077f2fff +VBoxGlobal.dylib (0) <7290F7C1-254E-3EED-9C62-2BB5B0AB7D92> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x107995000 -        0x107a46ff7 +VBoxXPCOM.dylib (0) <8FAAE730-B275-3930-8FE9-C0BDBCDD83A4> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10a1bd000 -        0x10a2fcfff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
    0x7fff3faa6000 -     0x7fff3fac2ffb  libJapaneseConverter.dylib (70) <8E3CD8A2-3F6F-317D-BCA2-5E340217F225> /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
    0x7fff43745000 -     0x7fff43749ffb  com.apple.agl (3.3.1 - AGL-3.3.1) <3741CDE0-4030-32F2-A7B4-ACE7D2E92214> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff43aea000 -     0x7fff43aeafff  com.apple.Accelerate (1.11 - Accelerate 1.11) <8632A9C5-19EA-3FD7-A44D-80765CC9C540> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff43aeb000 -     0x7fff43b01fef  libCGInterfaces.dylib (417.2) <E08ADB62-DF87-3BC8-81C6-60438991D4E1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff43b02000 -     0x7fff44000fc3  com.apple.vImage (8.1 - ???) <A243A7EF-0C8E-3A9A-AA38-44AFD7507F00> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff44001000 -     0x7fff4415bfe3  libBLAS.dylib (1211.50.2) <62C659EB-3E32-3B5F-83BF-79F5DF30D5CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff4415c000 -     0x7fff4418afef  libBNNS.dylib (38.1) <7BAEFDCA-3227-3E07-80D8-59B6370B89C6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff4418b000 -     0x7fff4454aff7  libLAPACK.dylib (1211.50.2) <40ADBA5F-8B2D-30AC-A7AD-7B17C37EE52D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff4454b000 -     0x7fff44560ff7  libLinearAlgebra.dylib (1211.50.2) <E8E0B7FD-A0B7-31E5-AF01-81781F71EBBE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff44561000 -     0x7fff44566ff3  libQuadrature.dylib (3) <3D6BF66A-55B2-3692-BAC7-DEB0C676ED29> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff44567000 -     0x7fff445e7fff  libSparse.dylib (79.50.2) <0DC25CDD-F8C1-3D6E-B472-8B060708424F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff445e8000 -     0x7fff445fbfff  libSparseBLAS.dylib (1211.50.2) <722573CC-31CC-34B2-9032-E4F652A9CCFE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff445fc000 -     0x7fff447a9fc3  libvDSP.dylib (622.50.5) <40690941-CF89-3F90-A0AC-A4D200744A5D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff447aa000 -     0x7fff4485bfff  libvMisc.dylib (622.50.5) <BA2532DF-2D68-3DD0-9B59-D434BF702AA4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff4485c000 -     0x7fff4485cfff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <54FF3B43-E66C-3F36-B34B-A2B3B0A36502> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff44b50000 -     0x7fff459aefff  com.apple.AppKit (6.9 - 1561.61.100) <44C1CF67-764C-39CD-B025-5D8EE6E62591> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff45a00000 -     0x7fff45a00fff  com.apple.ApplicationServices (48 - 50) <0E4AA883-7EFC-36EE-8B8E-E226E2C37965> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff45a01000 -     0x7fff45a67fff  com.apple.ApplicationServices.ATS (377 - 445.5) <703CE7E4-426A-35C0-A229-F140F30F5340> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff45b00000 -     0x7fff45c22fff  libFontParser.dylib (222.1.7) <9C4CEFB4-0F08-3B60-BD50-0120A37F6EA2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff45c23000 -     0x7fff45c6eff7  libFontRegistry.dylib (221.6) <30C6D1DE-C0E3-3447-A0EF-829443D95F0E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff45d13000 -     0x7fff45d46ff7  libTrueTypeScaler.dylib (222.1.7) <E401BD38-5F0E-382F-B4CB-AC6063871C0F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
    0x7fff45db0000 -     0x7fff45db4ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <A5FB2694-1559-34A8-A3D3-2029F68A63CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff45e54000 -     0x7fff45ea6ffb  com.apple.HIServices (1.22 - 625) <78A1FB4F-A39C-3159-B285-600C997335FB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff45ea7000 -     0x7fff45eb5fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <B65FF7E6-E9B5-34D8-8CA7-63D415A8A9A6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff45eb6000 -     0x7fff45f02fff  com.apple.print.framework.PrintCore (13.4 - 503.2) <B90C67C1-0292-3CEC-885D-F1882CD104BE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff45f03000 -     0x7fff45f3dfff  com.apple.QD (3.12 - 404.2) <38B20AFF-9D54-3B52-A6DC-C0D71380AA5F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff45f3e000 -     0x7fff45f4afff  com.apple.speech.synthesis.framework (7.8.1 - 7.8.1) <A08DE016-C8F2-3B0E-BD34-15959D13DBF0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff45f4b000 -     0x7fff461d9ff7  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <BAAB5625-A263-3ADD-9026-3F5F07E9171E> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff461db000 -     0x7fff461dbfff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <294802B9-E24D-34EB-973F-6D2B8E2E86CB> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff464fe000 -     0x7fff4689bfff  com.apple.CFNetwork (902.5 - 902.5) <2D37E75A-42FD-3CDE-BAE3-D4228EF813F0> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff468b0000 -     0x7fff468b0fff  com.apple.Carbon (158 - 158) <F8B370D9-2103-3276-821D-ACC756167F86> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff468b1000 -     0x7fff468b4ffb  com.apple.CommonPanels (1.2.6 - 98) <2391761C-5CAA-3F68-86B7-50B37927B104> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff468b5000 -     0x7fff46bbafff  com.apple.HIToolbox (2.1.1 - 911.10) <BF7F9C0E-C732-3FB2-9BBC-362888BDA57B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff46bbb000 -     0x7fff46bbeffb  com.apple.help (1.3.8 - 66) <DEBADFA8-C189-3195-B0D6-A1F2DE95882A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff46bbf000 -     0x7fff46bc4fff  com.apple.ImageCapture (9.0 - 9.0) <23B4916F-3B43-3DFF-B956-FC390EECA284> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff46bc5000 -     0x7fff46c5affb  com.apple.ink.framework (10.9 - 221) <5206C8B0-22DA-36C9-998E-846EDB626D5B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff46c5b000 -     0x7fff46c75ff7  com.apple.openscripting (1.7 - 174) <1B2A1F9E-5534-3D61-83CA-9199B39E8708> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff46c96000 -     0x7fff46c97fff  com.apple.print.framework.Print (12 - 267) <3682ABFB-2561-3419-847D-02C247F4800D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff46c98000 -     0x7fff46c9aff7  com.apple.securityhi (9.0 - 55006) <C1406B8D-7D05-3959-808F-9C82189CF57F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff46c9b000 -     0x7fff46ca1fff  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <2ED8643D-B0C3-3F17-82A2-BBF13E6CBABC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff46dc2000 -     0x7fff46dc2fff  com.apple.Cocoa (6.11 - 22) <17A98C08-64CF-3232-80EE-E10BAF68778F> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff46dd0000 -     0x7fff46e89fff  com.apple.ColorSync (4.13.0 - 3325) <D283C285-447D-3258-A7E4-59532123B8FF> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff47016000 -     0x7fff470a9ff7  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <EB35D3EC-56EA-33E6-98DC-BDC3A5FA8ACE> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff47110000 -     0x7fff47139ffb  com.apple.CoreBluetooth (1.0 - 1) <E1335074-9D07-370E-8440-61C4874BAC56> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff4713a000 -     0x7fff47490fef  com.apple.CoreData (120 - 851) <A2B59780-FB16-36A3-8EE0-E0EF072454E0> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff47491000 -     0x7fff47574fff  com.apple.CoreDisplay (99.14 - 99.14) <A1B91ADD-828D-33A0-8A92-CC3F83DF89D0> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff47575000 -     0x7fff47a18fef  com.apple.CoreFoundation (6.9 - 1455.12) <DE73A96B-3187-3CAC-99BB-3AA2100CD755> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff47a1a000 -     0x7fff4802afef  com.apple.CoreGraphics (2.0 - 1161.21.3) <60EFD404-B50C-3B77-90CD-D610BC590E7C> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff4802c000 -     0x7fff4831bfff  com.apple.CoreImage (13.0.0 - 579.5) <AAE2DFD0-9B0A-3D56-8A3E-C460BAF70394> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff486f0000 -     0x7fff486f0fff  com.apple.CoreServices (822.37 - 822.37) <7B04988B-C0D4-314E-8B3B-AE446B4A38CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff486f1000 -     0x7fff48765ffb  com.apple.AE (735.2 - 735.2) <690A6F47-1306-371F-B257-783D8F83EA9E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff48766000 -     0x7fff48a3dfff  com.apple.CoreServices.CarbonCore (1178.4.2 - 1178.4.2) <08AF7B7B-219B-3957-86CE-C96B423C823C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff48a3e000 -     0x7fff48a72fff  com.apple.DictionaryServices (1.2 - 284.2) <6505B075-41C3-3C62-A4C3-85CE3F6825CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff48a73000 -     0x7fff48a7bffb  com.apple.CoreServices.FSEvents (1239.50.2 - 1239.50.2) <FE465894-4235-3CE2-9A97-32D6C6C7D9AD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff48a7c000 -     0x7fff48c3aff7  com.apple.LaunchServices (822.37 - 822.37) <6AA93307-220A-3417-BBC2-FE1C0DE0B652> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff48c3b000 -     0x7fff48cebfff  com.apple.Metadata (10.7.0 - 1191.7) <3DD530A7-E104-3469-98BB-20449834B2FE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff48cec000 -     0x7fff48d4cfff  com.apple.CoreServices.OSServices (822.37 - 822.37) <4AD2FC98-C6CB-392A-A22F-196A723D7FAE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff48d4d000 -     0x7fff48dbbfff  com.apple.SearchKit (1.4.0 - 1.4.0) <3662545A-B1CF-3079-BDCD-C83855CEFEEE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff48dbc000 -     0x7fff48de0ffb  com.apple.coreservices.SharedFileList (71.21 - 71.21) <1B5228EF-D869-3A50-A373-7F4B0289FADD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff49081000 -     0x7fff491d1fff  com.apple.CoreText (352.0 - 578.22) <6129F39D-284D-3BBF-8999-7854AB61C01C> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff491d2000 -     0x7fff4920cfff  com.apple.CoreVideo (1.8 - 0.0) <86CCC036-51BB-3DD1-9601-D93798BCCD0F> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff4920d000 -     0x7fff49298ff3  com.apple.framework.CoreWLAN (13.0 - 1350.2) <DC9E1B0B-FD96-38A7-A6E0-820CA414AA94> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff49513000 -     0x7fff49518fff  com.apple.DiskArbitration (2.7 - 2.7) <2F628584-8177-3894-92CE-9CA6089B61C6> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff496d9000 -     0x7fff49aa0ffb  com.apple.Foundation (6.9 - 1455.12) <3B5567E0-775C-36D2-8052-DA42CA319EEA> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff49b11000 -     0x7fff49b41ff3  com.apple.GSS (4.0 - 2.0) <FC69A120-3C19-3802-87B4-C29217758143> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff49c53000 -     0x7fff49d57ffb  com.apple.Bluetooth (6.0.7 - 6.0.7f16) <74EC61E7-20E8-324C-8B5C-1D3129EEE675> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff49db7000 -     0x7fff49e52fff  com.apple.framework.IOKit (2.0.2 - 1445.71.6) <C68CE7ED-85CA-3D1F-BAA0-908327BEC0DE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff49e54000 -     0x7fff49e5bfff  com.apple.IOSurface (211.15 - 211.15) <9FD406F1-6BF2-35B0-8339-DF83A1A661EB> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff49eb2000 -     0x7fff4a02cfef  com.apple.ImageIO.framework (3.3.0 - 1739.3.2) <604D4447-1D29-3B29-A2D0-FED25E1FC6B5> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff4a02d000 -     0x7fff4a031ffb  libGIF.dylib (1739.3.2) <4C4B82AB-2F5A-3B98-9A6A-4D8D6B79DA75> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff4a032000 -     0x7fff4a119fe7  libJP2.dylib (1739.3.2) <A64CEB2C-3E18-3FFE-80B2-4F87233F3DF2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff4a11a000 -     0x7fff4a13dff7  libJPEG.dylib (1739.3.2) <48E918B8-2621-3002-9626-E89C10063104> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff4a419000 -     0x7fff4a43ffeb  libPng.dylib (1739.3.2) <3708AFF8-776C-3EE5-A197-70A30A4FFD9E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff4a440000 -     0x7fff4a442ffb  libRadiance.dylib (1739.3.2) <A5585B3A-0A75-3401-B29F-24FA1A7B0977> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff4a443000 -     0x7fff4a491fef  libTIFF.dylib (1739.3.2) <5F6ADFFB-0072-3176-9BA5-2313F2E2D99E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff4b34b000 -     0x7fff4b364ff7  com.apple.Kerberos (3.0 - 1) <F86DCCDF-93C1-38B3-82C2-477C12E8EE6D> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff4bd46000 -     0x7fff4bdc7fff  com.apple.Metal (125.30 - 125.30) <6B9EBDEE-C64C-3C1C-922A-0363B642C9BC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff4bde4000 -     0x7fff4bdfffff  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <AD754E8F-CA00-3878-9AF3-208C224A230B> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff4be00000 -     0x7fff4be6ffef  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <338B7779-E608-3D68-8A07-2ACC11299744> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff4be70000 -     0x7fff4be94fff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <9CE072D7-853B-3939-9645-7EB951376B87> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff4be95000 -     0x7fff4bf7cff7  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <0DE891AD-27E5-38FF-AEC8-4A95356C4357> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff4bf7d000 -     0x7fff4bf7dff7  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <2D2D261C-50B0-32F9-BF9A-5C01382BB528> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff4cf7c000 -     0x7fff4cf88ffb  com.apple.NetFS (6.0 - 4.0) <471DD96F-FA2E-3FE9-9746-2519A6780D1A> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff4fd7a000 -     0x7fff4fdd4ff7  com.apple.opencl (2.8.24 - 2.8.24) <CF922AFD-CBA4-3B23-A0C1-E3E5362BB6C7> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff4fdd5000 -     0x7fff4fdf1ffb  com.apple.CFOpenDirectory (10.13 - 207.50.1) <29F55F7B-379F-3053-8FF3-5C6675A3DD4D> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff4fdf2000 -     0x7fff4fdfdfff  com.apple.OpenDirectory (10.13 - 207.50.1) <F895547D-4915-353F-9C1E-E95172BA803B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff50f7c000 -     0x7fff50f7efff  libCVMSPluginSupport.dylib (16.7.4) <6846D939-478C-3AE3-9DCD-CD4F4CD05409> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff50f7f000 -     0x7fff50f84ffb  libCoreFSCache.dylib (162.9) <DD9DD721-2957-3D05-B361-70AF9EBFB280> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff50f85000 -     0x7fff50f89fff  libCoreVMClient.dylib (162.9) <4E4F3EA2-5B53-31A3-8256-54EFAA94E4D6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff50f8a000 -     0x7fff50f93ff3  libGFXShared.dylib (16.7.4) <6187AD8B-1CD2-3775-84CD-76A0EA8BCDD4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff50f94000 -     0x7fff50f9ffff  libGL.dylib (16.7.4) <2BB333D3-5C61-33DF-8545-06DF2D08B83D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff50fa0000 -     0x7fff50fdbfe7  libGLImage.dylib (16.7.4) <4DA003CE-0B74-3FE4-808C-B2FBCE517EB4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff5114a000 -     0x7fff51188ffb  libGLU.dylib (16.7.4) <BCB09CD8-EB0E-38FA-8B5A-9E29532EE364> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff51b00000 -     0x7fff51b0fff3  com.apple.opengl (16.7.4 - 16.7.4) <7B71A596-B6D8-335A-B7CA-8684D83B9C0E> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff52963000 -     0x7fff52bafff7  com.apple.QuartzCore (1.11 - 584.64.2) <DDA39332-DE09-3737-A332-0002AE05DD39> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff533e7000 -     0x7fff53712fff  com.apple.security (7.0 - 58286.70.15) <1481D55E-75C7-304D-AA12-D18A5197E508> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff53713000 -     0x7fff5379fff7  com.apple.securityfoundation (6.0 - 55185.50.5) <EB62490A-AA77-3F51-86B3-03669C3897B3> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff537d1000 -     0x7fff537d5ffb  com.apple.xpc.ServiceManagement (1.0 - 1) <E3146BBE-7F32-3605-AD2B-54C0E70759DC> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff53b7a000 -     0x7fff53beaff3  com.apple.SystemConfiguration (1.17 - 1.17) <CD4A4C66-7886-3323-A3B9-0C8952500856> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff56ae7000 -     0x7fff56b7aff3  com.apple.APFS (1.0 - 1) <70133D37-FDD3-3B2C-B295-00BECEA7EDA8> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff577a7000 -     0x7fff577cffff  com.apple.framework.Apple80211 (13.0 - 1370.4) <B37A91A0-5823-3F97-B575-9BB804FCEB00> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff577d1000 -     0x7fff577e0fef  com.apple.AppleFSCompression (96.60.1 - 1.0) <A7C875C4-F5EE-3272-AFB6-57C9FD5352B3> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff578df000 -     0x7fff578eaff7  com.apple.AppleIDAuthSupport (1.0 - 1) <2FAF5567-CDB3-33EF-AB71-05D37F2248B7> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff57924000 -     0x7fff5796cff3  com.apple.AppleJPEG (1.0 - 1) <8DD410CB-76A1-3F22-9A9F-0491FA0CEB4A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff579a7000 -     0x7fff579cffff  com.apple.applesauce (1.0 - ???) <CCA8B094-1BCE-3AE3-A0A7-D544C818DE36> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff57e22000 -     0x7fff580bbffb  com.apple.AuthKit (1.0 - 1) <6CA71A11-91C5-307C-B933-9FCDEDCB580A> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff581f2000 -     0x7fff581f9ff7  com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <51A41CA3-DB1D-3380-993E-99C54AEE518E> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff581fa000 -     0x7fff58281ff7  com.apple.backup.framework (1.9.6 - 1.9.6) <3C96FD26-C7F2-3F37-885A-5A71372FA8F4> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff59c3b000 -     0x7fff59c44ff3  com.apple.CommonAuth (4.0 - 2.0) <21AF4AC2-E650-35F9-AB33-3EBA2769FBC0> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff5a758000 -     0x7fff5a768ff7  com.apple.CoreEmoji (1.0 - 69.3) <A4357F5C-0C38-3A61-B456-D7321EB2CEE5> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff5aefc000 -     0x7fff5af04ff3  com.apple.CorePhoneNumbers (1.0 - 1) <A5D41251-9F38-3AB9-9DE7-F77023FAAA44> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff5b08f000 -     0x7fff5b0c0ff3  com.apple.CoreServicesInternal (309.1 - 309.1) <4ECD14EA-A493-3B84-A32F-CF928474A405> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff5b43a000 -     0x7fff5b4cbfff  com.apple.CoreSymbolication (9.3 - 64026.2) <A8D4315F-5DD5-3164-8672-ECDAF2766644> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff5b54e000 -     0x7fff5b683fff  com.apple.coreui (2.1 - 494.1) <B2C515C3-FCE8-3B28-A225-05AD917F509B> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff5b684000 -     0x7fff5b7b5fff  com.apple.CoreUtils (5.6 - 560.11) <1A02D6F0-8C65-3FAE-AD63-56477EDE4773> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff5b80a000 -     0x7fff5b86efff  com.apple.framework.CoreWiFi (13.0 - 1350.2) <50E8598A-0611-323D-B9A8-72A336424090> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
    0x7fff5b86f000 -     0x7fff5b87fff7  com.apple.CrashReporterSupport (10.13 - 1) <A909F468-0648-3F51-A77E-3F9ADBC9A941> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
    0x7fff5b8fe000 -     0x7fff5b90dff7  com.apple.framework.DFRFoundation (1.0 - 191.7) <9BBCCA62-F7BA-3B44-B044-E7C12ACC49F2> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
    0x7fff5b910000 -     0x7fff5b914ffb  com.apple.DSExternalDisplay (3.1 - 380) <901B7F6D-376A-3848-99D0-170C4D00F776> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
    0x7fff5b996000 -     0x7fff5ba0cfff  com.apple.datadetectorscore (7.0 - 590.3) <B4706195-CBE6-320D-A0E1-A9D4BDF52791> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff5ba5a000 -     0x7fff5ba9aff7  com.apple.DebugSymbols (181.0 - 181.0) <299A0238-ED78-3676-B131-274D972824AA> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
    0x7fff5ba9b000 -     0x7fff5bbcafff  com.apple.desktopservices (1.12.5 - 1.12.5) <7739C9A5-64D9-31A5-899B-5FFA242AD70D> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
    0x7fff5c9df000 -     0x7fff5ce0dfff  com.apple.vision.FaceCore (3.3.2 - 3.3.2) <B574FE33-4A41-3611-9738-388EBAF03E37> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
    0x7fff600d5000 -     0x7fff600dafff  com.apple.GPUWrangler (3.20.17 - 3.20.17) <BEA59DDE-A95A-3408-8FCE-6A74520E74AD> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
    0x7fff60e50000 -     0x7fff60e5ffff  com.apple.GraphVisualizer (1.0 - 5) <B993B8A2-5700-3DFC-9EB7-4CCEE8F959F1> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
    0x7fff60ee2000 -     0x7fff60f56fff  com.apple.Heimdal (4.0 - 2.0) <BAE3D978-2285-35DF-907E-02BC37986D02> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff61869000 -     0x7fff61870ff7  com.apple.IOAccelerator (378.28 - 378.28) <BE5CBEAA-314E-348B-BE85-7E4B2E4C42FF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
    0x7fff61874000 -     0x7fff6188bfff  com.apple.IOPresentment (1.0 - 35.1) <53B47F2A-9A9A-33F5-ADCB-FF766292B93A> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
    0x7fff61c56000 -     0x7fff61c7cffb  com.apple.IconServices (97.6 - 97.6) <A56D826D-20D2-34BE-AACC-A80CFCB4E915> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
    0x7fff61f01000 -     0x7fff61f14ff3  com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <3A6D6354-9CD6-3EE5-B0AB-D25B02D4847D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
    0x7fff61f15000 -     0x7fff6200aff7  com.apple.LanguageModeling (1.0 - 159.5.3) <7F0AC200-E3DD-39FB-8A95-00DD70B66A9F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
    0x7fff6200b000 -     0x7fff6204dfff  com.apple.Lexicon-framework (1.0 - 33.5) <DC94CF9E-1EB4-3C0E-B298-CA1190885276> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
    0x7fff62051000 -     0x7fff62058ff7  com.apple.LinguisticData (1.0 - 238.3) <49A54649-1021-3DBD-99B8-1B2EDFFA5378> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
    0x7fff62d6b000 -     0x7fff62dd4ff7  com.apple.gpusw.MetalTools (1.0 - 1) <B4217182-B2AA-3AA3-80E8-F4C80B71BDDC> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
    0x7fff62f64000 -     0x7fff62f7dfff  com.apple.MobileKeyBag (2.0 - 1.0) <7D657BC6-B779-3E51-B50D-07C95791DD04> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
    0x7fff63009000 -     0x7fff63033ffb  com.apple.MultitouchSupport.framework (1614.1 - 1614.1) <A0709B43-FA9E-3617-8E7A-D68CDFAB2167> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff6329a000 -     0x7fff632a5fff  com.apple.NetAuth (6.2 - 6.2) <2CFA1228-61A1-3708-988D-30499A1D6A9F> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff64b3e000 -     0x7fff64b4effb  com.apple.PerformanceAnalysis (1.194 - 194) <8022ED1F-CE70-388E-B37B-6FB1E5F90CF2> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff6690d000 -     0x7fff6692bfff  com.apple.ProtocolBuffer (1 - 260) <40704740-4A53-3010-A49B-08D1D69D1D5E> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
    0x7fff66b06000 -     0x7fff66b29ffb  com.apple.RemoteViewServices (2.0 - 125) <592323D1-CB44-35F1-9921-4C2AB8D920A0> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff6844f000 -     0x7fff68564ff7  com.apple.Sharing (1050.22.6 - 1050.22.6) <4AACAE2C-C003-39B8-AE6F-28566E6B7598> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
    0x7fff6858f000 -     0x7fff68590ff7  com.apple.performance.SignpostNotification (1.2.6 - 2.6) <8F04800F-3570-3392-A24D-B229FF03F7F9> /System/Library/PrivateFrameworks/SignpostNotification.framework/Versions/A/SignpostNotification
    0x7fff692ee000 -     0x7fff6958afff  com.apple.SkyLight (1.600.0 - 312.103.11) <A4D01EC8-6CED-3AA3-98EA-CD89E2B6559B> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
    0x7fff69d53000 -     0x7fff69d60fff  com.apple.SpeechRecognitionCore (4.6.1 - 4.6.1) <87EE7AB5-6925-3D21-BE00-F155CB457699> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
    0x7fff6a906000 -     0x7fff6a98ffc7  com.apple.Symbolication (9.3 - 64033) <FAA17252-6378-34A4-BBBB-22DF54EC1626> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
    0x7fff6aeff000 -     0x7fff6af07ff7  com.apple.TCC (1.0 - 1) <E1EB7272-FE6F-39AB-83CA-B2B5F2A88D9B> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff6b114000 -     0x7fff6b1d1ff7  com.apple.TextureIO (3.7 - 3.7) <F8BAC954-405D-3CC3-AB7B-048C866EF980> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
    0x7fff6b282000 -     0x7fff6b432fff  com.apple.UIFoundation (1.0 - 547.9) <24E3999C-F515-3389-9A82-A13E624F8B89> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
    0x7fff6cbae000 -     0x7fff6cbb0ffb  com.apple.loginsupport (1.0 - 1) <D1232C1B-80EA-3DF8-9466-013695D0846E> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
    0x7fff6cd17000 -     0x7fff6cd4aff7  libclosured.dylib (551.5) <112BC241-6626-3848-8DD8-B34B5B6F7ABC> /usr/lib/closure/libclosured.dylib
    0x7fff6ce04000 -     0x7fff6ce3dff7  libCRFSuite.dylib (41) <FE5EDB68-2593-3C2E-BBAF-1C52D206F296> /usr/lib/libCRFSuite.dylib
    0x7fff6ce3e000 -     0x7fff6ce49fff  libChineseTokenizer.dylib (28) <53633C9B-A3A8-36F7-A53C-432D802F4BB8> /usr/lib/libChineseTokenizer.dylib
    0x7fff6cedb000 -     0x7fff6cedcff3  libDiagnosticMessagesClient.dylib (104) <9712E980-76EE-3A89-AEA6-DF4BAF5C0574> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff6cf13000 -     0x7fff6d0ddff3  libFosl_dynamic.dylib (17.8) <C58ED77A-4986-31C2-994C-34DDFB8106F0> /usr/lib/libFosl_dynamic.dylib
    0x7fff6d115000 -     0x7fff6d115fff  libOpenScriptingUtil.dylib (174) <610F0242-7CE5-3C86-951B-B646562694AF> /usr/lib/libOpenScriptingUtil.dylib
    0x7fff6d24c000 -     0x7fff6d250ffb  libScreenReader.dylib (562.18.5) <0FEFDAC8-0FDF-38A0-AB88-A84E0DBA058F> /usr/lib/libScreenReader.dylib
    0x7fff6d251000 -     0x7fff6d252ffb  libSystem.B.dylib (1252.50.4) <B01E90C7-20B7-3CB1-8AB8-881827B5544A> /usr/lib/libSystem.B.dylib
    0x7fff6d2e5000 -     0x7fff6d2e5fff  libapple_crypto.dylib (109.50.15) <A8DEA8E9-5769-3C78-824D-969A98B94086> /usr/lib/libapple_crypto.dylib
    0x7fff6d2e6000 -     0x7fff6d2fcff7  libapple_nghttp2.dylib (1.24) <01402BC4-4822-3676-9C80-50D83F816424> /usr/lib/libapple_nghttp2.dylib
    0x7fff6d2fd000 -     0x7fff6d327ff3  libarchive.2.dylib (54) <8FC28DD8-E315-3C3E-95FE-D1D2CBE49888> /usr/lib/libarchive.2.dylib
    0x7fff6d328000 -     0x7fff6d3a9fdf  libate.dylib (1.13.1) <178ACDAD-DE7E-346C-A613-1CBF7929AC07> /usr/lib/libate.dylib
    0x7fff6d3ad000 -     0x7fff6d3adff3  libauto.dylib (187) <A05C7900-F8C7-3E75-8D3F-909B40C19717> /usr/lib/libauto.dylib
    0x7fff6d3ae000 -     0x7fff6d467ffb  libboringssl.dylib (109.50.15) <416CBB92-632F-33C2-A774-86ECB4BE46AE> /usr/lib/libboringssl.dylib
    0x7fff6d468000 -     0x7fff6d478ff3  libbsm.0.dylib (39) <6BC96A72-AFBE-34FD-91B1-748A530D8AE6> /usr/lib/libbsm.0.dylib
    0x7fff6d479000 -     0x7fff6d486ffb  libbz2.1.0.dylib (38) <0A5086BB-4724-3C14-979D-5AD4F26B5B45> /usr/lib/libbz2.1.0.dylib
    0x7fff6d487000 -     0x7fff6d4ddfff  libc++.1.dylib (400.9) <7D3DACCC-3804-393C-ABC1-1A580FD00CB6> /usr/lib/libc++.1.dylib
    0x7fff6d4de000 -     0x7fff6d502ff7  libc++abi.dylib (400.8.2) <EF5E37D7-11D9-3530-BE45-B986612D13E2> /usr/lib/libc++abi.dylib
    0x7fff6d504000 -     0x7fff6d514fff  libcmph.dylib (6) <890DEC4C-4334-393C-8B56-7C8560BBED9D> /usr/lib/libcmph.dylib
    0x7fff6d515000 -     0x7fff6d52cfcf  libcompression.dylib (47.60.2) <543F07BF-2F2F-37D5-9866-E84BF659885B> /usr/lib/libcompression.dylib
    0x7fff6d7d7000 -     0x7fff6d7efff7  libcoretls.dylib (155.50.1) <D350052E-DC4D-3185-ADBA-BA48EDCEE955> /usr/lib/libcoretls.dylib
    0x7fff6d7f0000 -     0x7fff6d7f1ff3  libcoretls_cfhelpers.dylib (155.50.1) <B297F5D8-F2FE-3566-A752-E9D998B9C039> /usr/lib/libcoretls_cfhelpers.dylib
    0x7fff6dcc2000 -     0x7fff6dd17ff3  libcups.2.dylib (462.2.9) <749D90AB-0F1E-308C-81B6-EA1167F7F5CA> /usr/lib/libcups.2.dylib
    0x7fff6de57000 -     0x7fff6de57fff  libenergytrace.dylib (16) <A92AB8B8-B986-3CE6-980D-D55090FEF387> /usr/lib/libenergytrace.dylib
    0x7fff6de8e000 -     0x7fff6de93ff3  libheimdal-asn1.dylib (520.50.9) <EF65C17E-31CD-31DC-876C-BF3EF393099C> /usr/lib/libheimdal-asn1.dylib
    0x7fff6debf000 -     0x7fff6dfb0ff7  libiconv.2.dylib (51.50.1) <2FEC9707-3FAF-3828-A50D-8605086D060F> /usr/lib/libiconv.2.dylib
    0x7fff6dfb1000 -     0x7fff6e1d8ffb  libicucore.A.dylib (59181.0.1) <2CE6205F-D375-3BF5-AA0A-3254BC4773D0> /usr/lib/libicucore.A.dylib
    0x7fff6e225000 -     0x7fff6e226fff  liblangid.dylib (128) <39C39393-0D05-301D-93B2-F224FC4949AA> /usr/lib/liblangid.dylib
    0x7fff6e227000 -     0x7fff6e240ffb  liblzma.5.dylib (10) <3D419A50-961F-37D2-8A01-3DC7AB7B8D18> /usr/lib/liblzma.5.dylib
    0x7fff6e241000 -     0x7fff6e257ff7  libmarisa.dylib (9) <D6D2D55D-1D2E-3442-B152-B18803C0ABB4> /usr/lib/libmarisa.dylib
    0x7fff6e308000 -     0x7fff6e530ff7  libmecabra.dylib (779.7.6) <F462F170-E872-3D09-B219-973D5E99C09F> /usr/lib/libmecabra.dylib
    0x7fff6e708000 -     0x7fff6e883fff  libnetwork.dylib (1229.70.2) <E185D902-AC7F-3044-87C0-AE2887C59CE7> /usr/lib/libnetwork.dylib
    0x7fff6e90a000 -     0x7fff6ecf87e7  libobjc.A.dylib (723) <DD9E5EC5-B507-3249-B700-93433E2D5EDF> /usr/lib/libobjc.A.dylib
    0x7fff6ed0b000 -     0x7fff6ed0ffff  libpam.2.dylib (22) <7B4D2CE2-1438-387A-9802-5CEEFBF26F86> /usr/lib/libpam.2.dylib
    0x7fff6ed12000 -     0x7fff6ed4aff7  libpcap.A.dylib (79.20.3) <6A9D27FA-2780-3E96-8B2E-645638AC13AC> /usr/lib/libpcap.A.dylib
    0x7fff6edc9000 -     0x7fff6ede5ffb  libresolv.9.dylib (65.1) <D9BB6307-71E4-3A94-A745-1FCA114C6894> /usr/lib/libresolv.9.dylib
    0x7fff6ee36000 -     0x7fff6efc9ff7  libsqlite3.dylib (274.8.1) <FCAD6A57-829E-3701-B16E-1833D620E0E8> /usr/lib/libsqlite3.dylib
    0x7fff6f19d000 -     0x7fff6f1fdff3  libusrtcp.dylib (1229.70.2) <1E065228-D0E3-3808-9405-894056C6BEC0> /usr/lib/libusrtcp.dylib
    0x7fff6f1fe000 -     0x7fff6f201ffb  libutil.dylib (51.20.1) <216D18E5-0BAF-3EAF-A38E-F6AC37CBABD9> /usr/lib/libutil.dylib
    0x7fff6f202000 -     0x7fff6f20fff3  libxar.1.dylib (417.1) <351781D5-3CCF-320F-BB5A-4DFCC1CCD31D> /usr/lib/libxar.1.dylib
    0x7fff6f213000 -     0x7fff6f2faff7  libxml2.2.dylib (31.17) <84B491F5-35D4-384A-B224-9B5BF69E8CB7> /usr/lib/libxml2.2.dylib
    0x7fff6f2fb000 -     0x7fff6f323fff  libxslt.1.dylib (15.16) <57D56366-1E7B-356C-B2B8-F4688FF666E6> /usr/lib/libxslt.1.dylib
    0x7fff6f324000 -     0x7fff6f336ffb  libz.1.dylib (70) <48C67CFC-940D-3857-8DAD-857774605352> /usr/lib/libz.1.dylib
    0x7fff6f3d2000 -     0x7fff6f3d6ff7  libcache.dylib (80) <092479CB-1008-3A83-BECF-E115F24D13C1> /usr/lib/system/libcache.dylib
    0x7fff6f3d7000 -     0x7fff6f3e1ff3  libcommonCrypto.dylib (60118.50.1) <029F5985-9B6E-3DCB-9B96-FD007678C6A7> /usr/lib/system/libcommonCrypto.dylib
    0x7fff6f3e2000 -     0x7fff6f3e9fff  libcompiler_rt.dylib (62) <968B8E3F-3681-3230-9D78-BB8732024F6E> /usr/lib/system/libcompiler_rt.dylib
    0x7fff6f3ea000 -     0x7fff6f3f3ffb  libcopyfile.dylib (146.50.5) <3885083D-50D8-3EEC-B481-B2E605180D7F> /usr/lib/system/libcopyfile.dylib
    0x7fff6f3f4000 -     0x7fff6f479ffb  libcorecrypto.dylib (562.70.3) <37AF8EC6-BF34-3D15-BC3A-A9B98F2427D4> /usr/lib/system/libcorecrypto.dylib
    0x7fff6f501000 -     0x7fff6f53aff7  libdispatch.dylib (913.60.3) <BF368549-2DFB-3530-B4CB-31D5EDAC4F2F> /usr/lib/system/libdispatch.dylib
    0x7fff6f53b000 -     0x7fff6f558ff7  libdyld.dylib (551.5) <49BF9E96-8297-30CF-8AA6-128CC14054B2> /usr/lib/system/libdyld.dylib
    0x7fff6f559000 -     0x7fff6f559ffb  libkeymgr.dylib (28) <E34E283E-90FA-3C59-B48E-1277CDB9CDCE> /usr/lib/system/libkeymgr.dylib
    0x7fff6f55a000 -     0x7fff6f566ff3  libkxld.dylib (4570.71.64) <720D7429-BBC0-3ABC-81C5-EB3357802F13> /usr/lib/system/libkxld.dylib
    0x7fff6f567000 -     0x7fff6f567ff7  liblaunch.dylib (1205.70.12) <4950A0B3-5EE1-3F9A-8B1A-94FB85FCCA2C> /usr/lib/system/liblaunch.dylib
    0x7fff6f568000 -     0x7fff6f56cffb  libmacho.dylib (906) <1902A611-081A-3452-B11E-EBD1B166E831> /usr/lib/system/libmacho.dylib
    0x7fff6f56d000 -     0x7fff6f56ffff  libquarantine.dylib (86.70.1) <C8252924-BCB2-35D3-BBA3-CEFE4FCB506C> /usr/lib/system/libquarantine.dylib
    0x7fff6f570000 -     0x7fff6f571ff3  libremovefile.dylib (45) <711E18B2-5BBE-3211-A916-56740C27D17A> /usr/lib/system/libremovefile.dylib
    0x7fff6f572000 -     0x7fff6f589fff  libsystem_asl.dylib (356.70.1) <39E46A6F-B228-3E78-B83E-1779F9707A39> /usr/lib/system/libsystem_asl.dylib
    0x7fff6f58a000 -     0x7fff6f58afff  libsystem_blocks.dylib (67) <17303FDF-0D2D-3963-B05E-B4DF63052D47> /usr/lib/system/libsystem_blocks.dylib
    0x7fff6f58b000 -     0x7fff6f614ff7  libsystem_c.dylib (1244.50.9) <1187BFE8-4576-3247-8177-481554E1F9E7> /usr/lib/system/libsystem_c.dylib
    0x7fff6f615000 -     0x7fff6f618ffb  libsystem_configuration.dylib (963.50.9) <A5DC1AFC-2C3E-3113-BE20-48F96064DB0F> /usr/lib/system/libsystem_configuration.dylib
    0x7fff6f619000 -     0x7fff6f61cffb  libsystem_coreservices.dylib (51) <486000D3-D8CB-3BE7-8EE5-8BF380DE6DF7> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff6f61d000 -     0x7fff6f61efff  libsystem_darwin.dylib (1244.50.9) <09C21A4A-9EE0-388B-A9D9-DFF8F6758791> /usr/lib/system/libsystem_darwin.dylib
    0x7fff6f61f000 -     0x7fff6f625ffb  libsystem_dnssd.dylib (878.70.4) <A94265A1-309C-3A13-B1FC-ED928FD50C3D> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff6f626000 -     0x7fff6f66fff7  libsystem_info.dylib (517.30.1) <AB634A98-B8AA-3804-8436-38261FC8EC4D> /usr/lib/system/libsystem_info.dylib
    0x7fff6f670000 -     0x7fff6f696ff7  libsystem_kernel.dylib (4570.71.64) <6D7159C8-F724-3C47-B8BF-4AB9BF475944> /usr/lib/system/libsystem_kernel.dylib
    0x7fff6f697000 -     0x7fff6f6e2fcb  libsystem_m.dylib (3147.50.1) <17570F46-566C-39FC-BEF6-635A355DD549> /usr/lib/system/libsystem_m.dylib
    0x7fff6f6e3000 -     0x7fff6f702ff7  libsystem_malloc.dylib (140.50.7) <A45A484C-3BDE-3BC4-A219-726E3CB332D9> /usr/lib/system/libsystem_malloc.dylib
    0x7fff6f703000 -     0x7fff6f833ff7  libsystem_network.dylib (1229.70.2) <5E86B2DE-9E15-3354-8714-4094ED5F698D> /usr/lib/system/libsystem_network.dylib
    0x7fff6f834000 -     0x7fff6f83effb  libsystem_networkextension.dylib (767.70.2) <9DC03712-552D-3AEE-9519-B5ED70980B70> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff6f83f000 -     0x7fff6f848ff3  libsystem_notify.dylib (172) <08012EC0-2CD2-34BE-BF93-E7F56491299A> /usr/lib/system/libsystem_notify.dylib
    0x7fff6f849000 -     0x7fff6f850ff7  libsystem_platform.dylib (161.50.1) <6355EE2D-5456-3CA8-A227-B96E8F1E2AF8> /usr/lib/system/libsystem_platform.dylib
    0x7fff6f851000 -     0x7fff6f85cfff  libsystem_pthread.dylib (301.50.1) <0E51CCBA-91F2-34E1-BF2A-FEEFD3D321E4> /usr/lib/system/libsystem_pthread.dylib
    0x7fff6f85d000 -     0x7fff6f860fff  libsystem_sandbox.dylib (765.70.1) <553DFCC6-9D31-3B9C-AB7C-30F6F265786D> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff6f861000 -     0x7fff6f862ff3  libsystem_secinit.dylib (30) <DE8D14E8-A276-3FF8-AE13-77F7040F33C1> /usr/lib/system/libsystem_secinit.dylib
    0x7fff6f863000 -     0x7fff6f86aff7  libsystem_symptoms.dylib (820.60.3) <441C6CA0-5711-3BB1-8420-DDAC3D5272E1> /usr/lib/system/libsystem_symptoms.dylib
    0x7fff6f86b000 -     0x7fff6f87fff7  libsystem_trace.dylib (829.70.2) <EEDE7900-3FDB-3841-A47D-2BED9FFBBF5D> /usr/lib/system/libsystem_trace.dylib
    0x7fff6f881000 -     0x7fff6f886ff7  libunwind.dylib (35.3) <BEF3FB49-5604-3B5F-82B5-332B80023AC3> /usr/lib/system/libunwind.dylib
    0x7fff6f887000 -     0x7fff6f8b4ff7  libxpc.dylib (1205.70.12) <7B82608D-ED82-35C1-B13F-99855E25D6DC> /usr/lib/system/libxpc.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 26549
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=395.2M resident=0K(0%) swapped_out_or_unallocated=395.2M(100%)
Writable regions: Total=62.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=62.9M(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Activity Tracing                   256K        2 
CG backing stores                  440K        2 
CG image                             8K        2 
CoreUI image data                  184K        3 
CoreUI image file                  280K        4 
Dispatch continuations            8192K        2 
Kernel Alloc Once                    8K        2 
MALLOC                            42.6M       15 
MALLOC guard page                   32K        9 
STACK GUARD                       56.0M        8 
Stack                             11.0M        8 
VM_ALLOCATE                         52K        5 
__DATA                            23.2M      243 
__FONT_DATA                          4K        2 
__LINKEDIT                       198.8M       17 
__TEXT                           196.5M      247 
__UNICODE                          560K        2 
mapped file                       64.1M       13 
shared memory                      868K       10 
===========                     =======  ======= 
TOTAL                            602.8M      577 

Model: MacBook10,1, BootROM 183.0.0.0.0, 2 processors, Intel Core i5, 1.3 GHz, 8 GB, SMC 2.42f10
Graphics: Intel HD Graphics 615, Intel HD Graphics 615, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80CE, 0x4B33514634463430424D2D41474346202020
Memory Module: BANK 1/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80CE, 0x4B33514634463430424D2D41474346202020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x168), Broadcom BCM43xx 1.0 (7.77.37.33.1a1)
Bluetooth: Version 6.0.7f16, 3 services, 27 devices, 1 incoming serial ports
Network Service: USB 10/100/1000 LAN, Ethernet, en3
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: USB3.0 Hub
USB Device: USB 10/100/1000 LAN
USB Device: USB3.0 Hub
USB Device: USB2.0 Hub
USB Device: USB 2.0 BILLBOARD
USB Device: USB2.0 Hub
USB Device: ACR1251 CL Reader PICC
Thunderbolt Bus: 
",chitentai
18964,storageattach --hotpluggable while running makes disk unremovable,Linux,other,VirtualBox 5.2.32,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
19261,"Win10/64 on macOS: Display Driver, screen resolution & speed",Mac OS X,Windows,VirtualBox 6.1.2,2020-01-24T10:40:16Z,2020-01-24T10:40:16Z,"running an iMac 2019 27'' with a Radeon Pro 570X, macOS Catalina. 
Issue with Oracle VirtualBox 6.1.2 and a Win10/64 guest system.

Here the screen resolution does not work properly, and speed to display and even show simple mouse movements is not good at all.
Windows 10 telling me, that is using the standard windows display driver. Tried using your radeon-software-adrenalin-2020-20.1.3-minimalsetup-200120_web.exe to resolve, however that does not detect any Radeon/AMD hardware.",Hofbor
19262,2D graphics performance issue when increasing the number of cores,Linux,Windows,VirtualBox 6.1.2,2020-01-24T12:13:58Z,2020-01-24T12:13:58Z,"Hi,

to increase the performances of Adobe Lightroom in a Windows 7 VM, I tried recently to increase the number of cores in my Windows 7 VM and I noticed a serious drop in 2D graphics performances.

I first believed it was due to some regression in recent versions of VirtualBox, so I did some benchmarks (using PassMark 9) in the VM with VirtualBox 5.2.x and 6.1.x, and I got the same performance drop for 2D graphics, whatever the VirtualBox version, when I increased the number of cores in the VM. So, it's not a regression.

I have a very powerful machine, with 16 physical cores and 128 GB RAM, so I was able to plot the PassMark 2D score vs the number of cores (2, 4, 8 or 16) in the VM. Then I exported my VM to VMware Player, and I did the same benchmark. The attached image 'figure_2D.png' shows the results (higher score is better). As you can see, the 2D graphics score for VirtualBox linearly decreases as the number of cores increases. The 2D score is divided by ~4 between 2 cores and 16.

However, this is not the same for VMware, where one can see a small decrease of 15% between 2 cores and 16.

I also plotted the CPU score of PassMark vs the number of cores in the VM (image 'figure_CPU.png', higher score is better). For this benchmark, VirtualBox and VMware perform the same until 8 cores, but VMware gives a much better result for 16 cores.

I tried many parameter tweaks in VirtualBox but I was not able to improve the situation. I also tried with another PC that has less cores, and I saw the same performance drop...

Note that the performance drop I see in PassMark scores (in a Windows 7 VM) reflects what I see as a user in the windows 7 VM. This is not an artefact of using PassMark in a VM. For example, with 16 cores in a VirtualBox VM, moving a window is painfully slow. The CPU load is very high even when I do nothing, the fans are at maximum speeds, etc. Those problems do not arise in VMware player: the CPOU load is low, and the VM is very snappy, whatever the number of cores.

To me, there should be no interaction between increasing the number of cores and the 2D graphics performance. It's clearly a bug or perhaps a side effect of the way multicore processing is done in VirtualBox...


My hardware: HP Z820 Workstation with two Intel Xeon CPU E5-2687W 0 @ 3.10GHz, 16 cores, 32 threads and 128 GB RAM, graphic card id an Nvidia Quadro K2000

Host system: Ubuntu Linux 18.04, 64 bits

Guest system: Windows 7 Professional SP1, 64 bits, 4GB RAM in the VM, guest additions installed, 256 MB video RAM


",roland651
19264,Crash when 'un-pausing' paused VM on Win10 host,Windows,all,VirtualBox 6.1.2,2020-01-24T22:01:25Z,2020-01-24T22:01:25Z,"I usually have 1 or 2 guests open on a Win10 host. When I'm not using the host system, I suspend or hibernate it. In addition, I manually pause a VM when not using it, in order to save host resources.

Sometimes I get crashes:
- I manually want to resume a paused VM. Crash! I then do a normal shutdown of the other VM as guest user (start button). The second VM crashes too. Conclusion: It's probably not a problem of a single VM instance, but rather of some component common to all guests.

- I suspend/resume the Windows host. On resume, I immediately get a VM crash, presumable because vbox does an implicit pause/resume of a VM.

These things happen with some probability. I can't reproduce it reliably. On vbox 6.0.12 the probability was so low that I didn't really mind. With 6.0.14 and 6.0.16 the probability seemed much higher, so I didn't use them. Now I have switched to 6.1.2 r135662 (Qt5.6.2) and I get it quite often.

I have already described my problems in https://forums.virtualbox.org/viewtopic.php?f=6&t=96538

I'm reporting now a case that seems to be typical. Here is what I did:


------------------------------------
1. Start Ubuntu guest.
2. Start WinXP guest.
3. Manually pause the Ubuntu, while WinXP keeps running.
4. Put host (Win 10) asleep.
5. Wake up the host. On wakeup, I immediately get a message notifying me of a VM crash. It turns out that the WinXP guest is gone, the paused Ubuntu guest is still there.
6. I try to manually resume the paused Ubuntu, but it crashes immediately.
------------------------------------

I attach logs of both VMs.
The following lines in the logs may be of interest:

20:58:02.032649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000163c!!! (Log of Ubuntu guest)

18:34:20.151649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002e00!!! (Log of WinXP guest)
",ueli
19266,Shared Clipboard not working bi-directionally,Windows,Windows,VirtualBox 6.0.16,2020-01-25T09:17:59Z,2020-01-25T09:17:59Z,"Hi, I am running a Windows XP SP3 VM on a Windows 10 64bit Host machine and. I am struggling to make the shared clipboard functionality work. The actual shared clipboard function doesn't work at all but i can drag and drop files from the host machine to the guest machine. The other way round this doesn't work. Am attaching a log file. Would really appreciate any advice on this.",alexKite
19268,VirtualBox Extension Pack 6.0.16 installation failure,Mac OS X,other,VirtualBox 6.0.16,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
18645,Install of kernel drivers fails with osx 10.14.5,Mac OS X,Windows,VirtualBox 6.0.8,2020-01-26T03:27:50Z,2020-01-26T03:27:50Z,"During installation of VBOX the OSX system show a message to contact Oracle because the software is not compatible with the last upgrade of OSX and the installation fails.

This problem appears after upgrading OSX to 10.14.5 version.

The same error also trying installing previous versions of VBOX.

",Tunesi Edoardo Fabio
14645,Shared Clipboard some time stop working,Windows,Windows,VirtualBox 5.0.4,2020-01-27T12:17:44Z,2020-01-27T12:17:44Z,"Sometimes the shared clipboard stops working and I need to reboot the machine or stop and restart VBoxTray.exe.
I do not have details on why it happens so I can not put the steps to reproduce the anomaly.",bmn
19273,WindowsHost CloneVM Incorrect VM Filename generated,Windows,all,VirtualBox 6.0.16,2020-01-28T12:17:46Z,2020-01-28T12:17:46Z,"When Cloning a VM from the Windows GUI, (i.e. select a VM, right-click... Clone), it prompts you to enter a new name for the cloned VM. After generating the new clone VM inspection of the files produced show the VM file is based on the filename of the cloned VM and not that of the 'new' VMs name entered previously. This can lead to confusion about which file goes with which VM (only the containing folders differentiate them). This feature has been present in previous releases.",SolidDude
19274,WindowsHost - GUI - Incorrect VM deleted,Windows,all,VirtualBox 6.0.16,2020-01-28T12:35:12Z,2020-01-28T12:35:12Z,"When removing a VM (by selecting a VM in the list, right clicking... Remove), sometimes the wrong VM is deleted resulting in the VM list getting out of sync. e.g. I removed a Linux VM, but discovered it actually destroyed a Windows VM (the Windows VM was listed above the Linux VM in the GUI list). The resulting visible VM list was actually correct (i.e. the Linux one disappeared off the screen list) but the Windows VM folder was corrupted ending up as a Linux VM). i.e. double clicking the Windows VM entry launched Linux. This fault has been in previous releases.",SolidDude
6579,Cannot get a bridged network connection on guest OSes via a WPA2 wireless network with MSCHAPv2/PEAP authentication,Windows,other,VirtualBox 3.1.6,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
19278,"Vboxmanage.exe fails when using ""quoted\folder\path\to""vboxmanage.exe",Windows,all,VirtualBox 6.0.16,2020-01-29T13:51:09Z,2020-01-29T13:51:09Z,"On a Windows 7 host running 5.2.28, and Windows 10 hosts running 6.0.14, and 6.1.2, this vboxmanage command line:


{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""
}}}


finishes correctly.

This command line:


{{{
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""
}}}


errors out with the vboxmanage full help printout and this error:


{{{
Syntax error: Invalid command '\vboxmanage.exe'
}}}


Note the difference in the command lines:

{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""  <-- good
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""  <-- bad
}}}

The difference is in where the double-quotes are put after the space-named folder path.
The second command line was made by drag-n-dropping the Virtualbox install folder onto the command window, then adding the backslash and vboxmanage.exe.

These Windows command lines all work: (""calc.exe was copied to the ""test dir"" folder, ""InSpectre.exe"" is a stand-alone 3rd-party exe.)


{{{
""c:\users\snc\test dir\calc.exe""
""c:\users\snc\test dir""\calc.exe
""c:\users\snc\test dir\inspectre.exe""
""c:\users\snc\test dir""\inspectre.exe
}}}


Note that either with the ""\ or \..."", the command lines work.

It appears that Vboxmanage.exe does not parse the command line correctly. ",scottgus1
19279,BSOD (DRIVER_OVERRAN_STACK_BUFFER ) in guest when trying to run nested virtual machine,Windows,Windows,VirtualBox 6.1.2,2020-01-29T18:41:17Z,2020-01-29T18:41:17Z,"I am unable to make any 64 bit virtual machine to work in guest using nested virtualization provided by Virtualbox. I am using Vbox version 6.1.2 in both Host and Guest (guest have the vbox additions installed). As soon as I try to run any 64 bit VM in guest the guest OS crashes with BSOD (but Host is stable). I am using latest Windows 10 64 bit 1909 in both host and guest. Host is running AMD Ryzen 7 3700X CPU in ASUS x570 TUF Gaming PLUS motherboard.
I have attached logs of the Guest machine and the kernel memory dump from the guest OS that crashed.
The BSOD from guest is related to VMMR0.r0 driver with memory_corruption message. The bug check code is DRIVER_OVERRAN_STACK_BUFFER ",proboszcz
18901,Using serial host device make guest boot hang,Linux,Windows,VirtualBox 6.0.10,2020-01-30T16:05:48Z,2020-01-30T16:05:48Z,"I'm using the serial host device since a long time.
Using Fedora (from 20 now 30) host and XP host (because of sortware only running on Windows XP using serial device)
Until VB 5.12, everything worked thing.
But now, after update to Fedora 30, I had to update to the last VirtuaBox release (6.0.10).
My guest does not boot anymore (it hangs)
If i uncheck serial port, it boots.
If I keep serial port and disable it, My guest Boots, serial COM is visible but unsuable (which is normal).

VBox.log is showing this : (see file attached)
 Failed to change parameters to 9600,EVEN,7,1 -> VERR_DEV_IO_ERROR
 Failed to change parameters to 1200,EVEN,7,1 -> VERR_DEV_IO_ERROR

",cderenne
19281,VB issue with multiple cores for Xeon 5450,Windows,all,VirtualBox 6.1.2,2020-01-30T17:10:23Z,2020-01-30T17:10:23Z,"I have an ""older"" server running a motherboard with two Xeon 5450 (4 cores each) with 16 Gb of ram running W2016. I have installed the current version of VB and installed W7, W10 and Ubuntu (all latest versions) in respective VMs. All settings in VB work OK (as expected), except when I add more than 2 CPU cores to any VM. When that happens, CPU utilization (for the VM) goes to 100% (all cores - after a little while) the VM slows down to a crawl and/or freezes. This is most certainly not the expected behavior.",globus999
19283,VirtualBox stuck zoomed in on Windows 10,Windows,Linux,VirtualBox 6.0.16,2020-01-31T20:37:42Z,2020-01-31T20:37:42Z,"Hello, 
I am running virtual box through vagrant on Windows 10. I cannot perform many functions on VirtualBox that I need to for school and work projects because the screen is zoomed in and I can't click or see many of the things I need to. I have tried some of the recommended fixes mentioned online at stackexchange and others but none have worked. Please let me know what I can do to make this work.

Thank you!",BallsMahoney
19282,Virtual Box Machine fails on startup,Windows,Linux,VirtualBox 6.1.2,2020-02-01T00:03:17Z,2020-02-01T00:03:17Z,"When attempting to start a machine, on the newly upgraded Virtual Box, it does not start. It gives an error saying - 
Error launching Virtual Box VM Process 5
Please try reinstalling Virtual Box
(screenshot attached)
When I click on Ok, it then displays another dialog box with the following message - 

The virtual machine 'orarac1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\*******\VirtualBox VMs\orarac1\Logs\VBoxHardening.log'.
Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}



I tried reinstalling virtualbox, but it still gives an error.
I tried looking at the hardening log. I have attached it in the ticket too.
I have already done an scf /scannow on the entire desktop computer c: drive and it has not returned any errors.
",FireExit
19284,Error when opening vscode file menu,Windows,Linux,VirtualBox 6.1.2,2020-02-03T08:46:38Z,2020-02-03T08:46:38Z,"
The instruction 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click OK to terminate the program""",china_liu
19276,Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).,Linux,Windows,VirtualBox 5.2.36,2020-02-03T15:37:05Z,2020-02-03T15:37:05Z,"Failed to open a session for the virtual machine Windows 7 Test.

Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",DHDurgee
19249,aclocal (and probably other tools) not working in shared folder,other,Linux,VirtualBox 6.1.2,2020-02-04T14:08:24Z,2020-02-04T14:08:24Z,"How to reproduce using Vagrant:

* Use a minimal `Vagrantfile`:
{{{
$script = <<SCRIPT
    yum install -y epel-release
    yum install -y automake libtool
SCRIPT

Vagrant.configure('2') do |config|
    config.vm.box = 'allenta/bento.centos-7.4'
    config.vm.box_version = '=201803.24.0'
    config.vm.synced_folder '.', '/vagrant', :nfs => false
    config.vm.provision :shell, :privileged => true, :inline => $script
end
}}}
* Create a minimal `configure.ac` file in `/vagrant/` (i.e. shared folder):
{{{
AC_INIT([helloworld], [0.1], [hello@example.com])
AM_INIT_AUTOMAKE
AC_PROG_CC
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
}}}
* Try to run `aclocal`:
{{{
$ cd /vagrant

$ aclocal
/usr/bin/m4:/tmp/am4tHcrP6s/traces.m4:320: ERROR: end of file in string
Use of uninitialized value $msg in concatenation (.) or string at /usr/bin/autom4te line 1026.
Use of uninitialized value $stacktrace in pattern match (m//) at /usr/bin/autom4te line 1026.
unknown channel X])])])dnl
])
igure.ac:1: -1- m4_pattern_allow(^mandir$)
 at /usr/share/autoconf/Autom4te/Channels.pm line 638.
    Autom4te::Channels::msg('X])])])dnl\x{a}])\x{a}igure.ac:1: -1- m4_pattern_allow(^mandir$)\x{a}', undef, 'warning: ', 'partial', 0) called at /usr/bin/autom4te line 1026
aclocal: error: echo failed with exit status: 1
}}}

* Try same thing moving `/vagrant/configure.ac` to a different non-shared location (e.g. `/tmp`). The command will work as expected (i.e. not output and some files generated).

This has been tested in the following combinations. It only worked when using Ubuntu 19.10:
* macOS Catalina 10.15.2 + VirtualBox 6.0.16 + Vagrant 2.2.6
* macOS Catalina 10.15.2 + VirtualBox 6.1.2 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662
* Ubuntu 18.04 + VirtualBox 6.0.14 + Vagrant 2.2.6
* Ubuntu 18.04 + VirtualBox 6.1.2 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662
* Ubuntu 19.10 + VirtualBox 6.1.0 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662

In the past this worked fine.",carlos.abalde
18030,EXC_BAD_ACCESS (SIGSEGV) on macOS 10.14 (Mojave) if trying to start Windows 10 Guest,other,other,VirtualBox 5.2.18,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
19292,Critical Error: Guru Meditation,Mac OS X,Linux,VirtualBox 6.1.2,2020-02-05T23:37:45Z,2020-02-05T23:37:45Z,"I set up an Ubuntu 18.04 guest on my Macbook Pro 2019 earlier today, and everything was going ok and I was able to use it. I set up port forwarding with VBoxManage modifyvm ""vmname"" --natpf1 ""ssh,tcp,127.0.0.1,3022,10.0.2.15,22"" and was able to ssh into my vm. I was also able to use VBoxHeadless successfully. I then opened the VirtualBox GUI, right clicked on my virtual machine name and opened settings, and changed the name of the guest slightly (there was an uppercase by mistake). I then checked to see if my port forwarding rule had been updated and it had. Upon trying to use VBoxHeadless to start the vm it produced a lot of errors in the command line, so I stopped it and tried to open it with the VirtualBox GUI. This was when I receive the Critical Error message and was directed here. I have attached the log file and png from the log folder as requested in the pop up box.",josh6
19293,IMedium::getEncryptionSettings() variables are backwards when called via web service,all,all,VirtualBox 6.1.0,2020-02-06T05:39:08Z,2020-02-06T05:39:08Z,"To start: this is a very minor issue and is really just for your awareness. SDKRef for API v6.1.0 page 268 shows IMedium::getEncryptionSettings() taking a variable reference for the cipher and returning the disk ID. When calling this method using the web service, however, it takes a variable reference for the disk ID and returns the cipher. I've confirmed the documentation matches the method when using the VirtualBox.VirtualBox COM object. I would imagine this needs to be changed in the WSDL and VBoxWebSrv. For now, I've simply reversed my variables and it works. My VirtualBox version is 6.1.0 and I'm using the 6.1.0 SDK via PowerShell on a Windows 7 host.

I'm creating the web service proxy in PowerShell using ""$global:vbox = New-WebServiceProxy -Uri ""$($env:VBOX_MSI_INSTALL_PATH)sdk\bindings\webservice\vboxwebService.wsdl"" -Namespace ""VirtualBox"" -Class ""VirtualBoxWebSrv"""". My call to getEncryptionSettings() as it works right now is ""$cipher = $global:vbox.IMedium_getEncryptionSettings($disk.Id, [ref]$diskid)"". $disk.Id is the web service reference ID string to that specific IMedium so is unimportant to this.

I'm creating the vbox COM object using ""$global:vbox = New-Object -ComObject VirtualBox.VirtualBox"". When calling getEncryptionSettings() from the COM, my call can be correct to the SDKRef like this: ""$diskid = $global:vbox.HardDisks[$disk.Id].getEncryptionSettings([string]@([ref]$cipher))"". $disk.Id here is the array index to that specific IMedium so is unimportant to this.",SmithersTheOracle
18200,tinytext in UI elements when on different screens,Linux,all,VirtualBox 6.0.0,2020-02-06T10:07:21Z,2020-02-06T10:07:21Z,"I'm on a three monitor setup, one 1920x1080, and two 1900x1200. Gnome on Oracle Linux 7.5. 


When Moving the Virtualbox Manager to the (slightly) higher resolution screen, the font size shrinks drastically.

In addition, the menubar elements attached to guest machines ('File Machine View Input...') also become extremely small.
",ronabop
19288,W2003 32 bit in VM stops responding in 6.0.16,Linux,Windows,VirtualBox 6.0.16,2020-02-07T06:46:36Z,2020-02-07T06:46:36Z,"In the latest upgrade of VirtualBox 6.0 for Ubuntu my W2003 client stops responding after a while. I need to do a hard reset to get it back again. After hard reset it just runs again, mostly for a few hours.

This client has been running for even years I think without any problems. I downgraded to VirtualBox 6.0.14 and that seems to solve the issue.",NickGuus
16110,5.1.x series - Fullscreen and mouse pointer offset in Gnome 3.20+,Linux,Windows,VirtualBox 5.1.8,2020-02-07T12:14:09Z,2020-02-07T12:14:09Z,"Windows 10 guest, Arch Linux host with Gnome 3.20 and 3.22. Been observing this regression since the initial 5.1.x releases and still present in 5.1.8 with 5.1.8 guest additions.

STR:

1) Load guest Win10 in fullscreen mode. 
2) Navigate away to another non-Virtualbox window. 
3) Navigate back to Virtualbox window.

Expected result: Fullscreen display is maintained

Actual result: Entire fullscreen display is shifted down by X pixels equal to the size of the Gnome bar at top of screen. This offset equally applies to the mouse pointer. Notice in attached screenshot that the top bar area from the native display manager is showing the Gnome desktop background. Also notice the position of the pointer relative to the hovered state of the taskbar icon.",tekstryder
19294,Frequent crashing with The Instruction at 0x... referenced memory at 0x... The memory could not be read,Windows,Linux,VirtualBox 6.1.2,2020-02-07T17:27:51Z,2020-02-07T17:27:51Z,"I have read many similar posts and tried the recommended fixes, but I am still having the issue. 

Host: Windows 10 pro, 16Gb ram, updated the video drivers
Guest: Ubuntu, 8Gb, 256Mb video mem

Seems to happen most frequently when I am running VSCode and click on any menu or context menu.

Attaching logs",tdsTPPS
19287,gcc10 problems,other,other,VirtualBox 6.1.2,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)
19297,Attempting to set up virus protection,Linux,Windows,VirtualBox 5.2.34,2020-02-09T07:56:32Z,2020-02-09T07:56:32Z,"After a very long set up process to get windows 7 pro 32 bit running and finally see my usb drive, I encountered a fatal error when attempting to set up bitdefender virus protection within virtualbox running under feren (ubuntu 18.04 variant).  The software tells me to send you these two files for your review.  Hope you can clear up what is going on here as I a now unable to proceed any further with Virtualbox.",Tripleripple
19031,Segfault on Fedora 30.,Linux,all,VirtualBox 6.0.12,2020-02-09T17:18:58Z,2020-02-09T17:18:58Z,"I am running Fedora 30 on a machine with 128 GB RAM and a GeForce RTX 2080 video card. I recently upgraded to a very high resolution and large monitor (49"" 5120x1440). Since then, virtualbox will not start.

When I run on the commandline, I get the following error, before any graphical interface is displayed (i.e., before I can even try to boot a guest OS):


{{{
% virtualbox
(VirtualBox:33239): librsvg-WARNING **: 10:36:43.169: cannot render on a cairo_t with a failure status (status=""invalid value (typically too big) for the size of the input (surface, pattern, etc.)"")
Segmentation fault (core dumped)
}}}

I've used the Fedora package manager to make sure I have the most recent version available through that source (VirtualBox-6.0.12). 

",mopomi
19298,Frequent crash when suspending virtual machine,Windows,Linux,VirtualBox 6.1.2,2020-02-10T13:24:27Z,2020-02-10T13:24:27Z,"Most of the time when I pause (Host+P) my Linux virtual machines, VirtualBox crashes.
This behavior seems to getting worse with every new release.
I can't really remember when this started, but I'm pretty sure that I never had the issue with versions before 6.0.

After every crash, I see exception ""rtR3WinUnhandledXcptFilter caught an exception on thread"" in the log file.
I attached two of them.
",didier.martiny
19140,MacOS / Random network disconnect (Host-only Adapter) - ARP: duplicate use of $IP detected,Mac OS X,Linux,VirtualBox 6.0.14,2020-02-10T17:06:35Z,2020-02-10T17:06:35Z,"Hi VirtualBox Use/Admin/Dev,

We are using VirtualBox in my company to launch Alpine Linux for Docker usage. All developers use it for development and the main application in Docker is Apache, MySQL and PHP. (The network is Host-only Adapter)

It's work really fine since several years but since 6 months peoples on MacOS suffer of random network disconnect. That lasts 2 to 3 minutes and it comes back without any intervention ...(This happens between 2 to 6 times over a period of one hour)


{{{
Jeu 14 nov 2019 13:22:40 EST: 64 bytes from 172.21.21.5: icmp_seq=6644 ttl=64 time=0.439 ms
Jeu 14 nov 2019 13:22:41 EST: 64 bytes from 172.21.21.5: icmp_seq=6645 ttl=64 time=0.296 ms
Jeu 14 nov 2019 13:22:42 EST: 64 bytes from 172.21.21.5: icmp_seq=6646 ttl=64 time=0.369 ms
Jeu 14 nov 2019 13:22:44 EST: Request timeout for icmp_seq 6647
[...]
Jeu 14 nov 2019 13:25:07 EST: Request timeout for icmp_seq 6789
Jeu 14 nov 2019 13:25:07 EST: 64 bytes from 172.21.21.5: icmp_seq=6790 ttl=64 time=0.832 ms
Jeu 14 nov 2019 13:25:08 EST: 64 bytes from 172.21.21.5: icmp_seq=6791 ttl=64 time=0.412 ms
}}}

 
First we check on the Guest host:

- Check network/application logs 
- Update OS and packages
- Allocate more memory
-  ....

After we make somes changes on Host:

- Update MacOS from 10.14 to 10.15
- Disable Bluetooth
- ...


Here the Host IP/vboxnet0:
{{{
MacBook-Pro:platform-website turbulent$ ifconfig vboxnet0
vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	ether 0a:00:27:00:00:00 
	inet 172.21.21.1 netmask 0xffffff00 broadcast 172.21.21.255
}}}


Here the Guest IP/eth1:
{{{
substance@work:~$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 08:00:27:DA:BC:C4  
          inet addr:172.21.21.5  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feda:bcc4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96227 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68725 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:9772660 (9.3 MiB)  TX bytes:280592087 (267.5 MiB)
}}}

After when I check on ""Console"" on the Host, I have all time this error on the disconnect: 

{{{
13:22:43.454970 -0500	lsd	LSExceptions shared instance invalidated for timeout.
13:22:43.479991 -0500	kernel	X86PlatformPlugin result 0
13:22:43.479997 -0500	kernel	X86PlatformPlugin result 0
13:22:43.743794 -0500	locationd	{""msg"":""kCLConnectionMessageWatchdog"", ""event"":""activity"", ""this"":""0x7fdcf0c808d0"", ""registrationRequired"":0, ""registrationReceived"":1}
13:22:43.776090 -0500	kernel	vboxnet0 duplicate IP address 172.21.21.1 sent from address 08:00:27:5a:96:1c
}}}

After I installed  Wireshark to inspect the netwok and you can view the ARP package from this MAC:

[[Image(https://cdn.clarenne.name/virtualbox-network.png)]]

I open this ticket because this mac address start with ""08:00:27:5a"" look to be the DHCPServer assignments.

Can you please have a check on this issue ? 
",TB-Quentin
19280,"6.1.2 Installation failed, could not run required dll",Windows,other,VirtualBox 6.1.2,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
19301,VirtualBox versions of me checked 4.2 / 6.0 has ceased to provide some OpenGL and DeritX functions.,all,Windows,VirtualBox 6.0.16,2020-02-11T14:31:35Z,2020-02-11T14:31:35Z,"My VirtualBox previously ran a Windows 7 guest with Aero support, and Aero worked. Most games and 3D applications also worked. But something happened, and VirtualBox refuses to provide some API functions for processing 3D graphics. Due to Aero not working, most games are not working. Only very old games that are already 17 years old have remained to work, for example Counter Strike 1.6 is still working.
To solve the problem, I tried to flash the laptop BIOS, and run VirtualBox from the Ubuntu host. But the problem has not been solved, and V irtualBo works the same way. To solve the problem, I tried to find out in Everest, the supported versions of OpenGL VirtualBox, and OpenGL 2.0 and 3.0 are 100% supported, 3.1 and 3.2 are partially supported. However, my applications that I want to run, came out earlier than 2006, and support Open GL 2.0.
I suppose this is bookmarking this peacekeeping. I tried to change the date, it does not help. Total VirtualBox was ominor (even with the Internet turned off).",Aertx
18982,Skype for Business in Win10 guest unusable graphical glitches on Linux host with VBoxSVGA,Linux,Windows,VirtualBox 6.0.12,2020-02-11T14:32:25Z,2020-02-11T14:32:25Z,"Hi, I'm running Win10 1903 on an openSUSE Tumbleweed host with VirtualBox 6.0.12 and integrated Intel graphics. I tried both the Xorg Intel driver as well as the X modesetting driver, and they both act the same. When I switch from VBoxVGA to VBoxSVGA due to the deprecation warning, Skype for Business (October 1, 2019, update KB4484102) becomes unusable due to major graphical glitches. Almost the whole window, including the window border and controls is either white or black. I am attaching a screenshot.

I tried updating the guest additions inside Win10, as well as the extension pack on the host, and it makes no difference. I have 2D and 3D acceleration enabled, which I definitely need for my workload in the Win10 guest.

Please do not deprecate VBoxVGA until VBoxSVGA becomes a reliable alternative.

Thanks.",sb56637
16382,Win10: VBoxSVC hangs when thunderbolt-to-USB is disconnected (PC undocked),Windows,Linux,VirtualBox 5.1.12,2020-02-11T20:59:09Z,2020-02-11T20:59:09Z,"USB ports on the HP ZBook Dock with Thunderbolt 3 is unresponsive after undocking/docking when VirtualBox is running.

Hardware: HP ZBook Studio G3 with HP ZBook Dock with Thunderbolt 3

'''To reproduce :'''
1. Start the Oracle VM VirtualBox.
2. Start the Ubuntu VM . 
3. Undock - Unplug the Thunderbolt cable. (ie. disconnect laptop from dock ...)
4. Re-dock - Plug the Thunderbolt cable.
5. The Thunderbolt dock USB ports are non-responsive.

'''Observations:'''
Something in VirtualBox seems to ""block the system from clearing the instance of the USB root hub driver from memory on the Thunderbolt disconnect"".

After the problem has occurred (ie. USB ports on dock is unresponsive), closing all programs, attempting to reboot Windows, the following Window message appears:

""VirtualBox Interface  Has active connections.""

Aborting the Windows reboot and checking ""Task Manager"" shows that the VBoxSVC.exe process is still active.

Manually killing the VBoxSVC.exe process seems to restore the Thunderbolt dock's USB ports.


This may be related to: Ticket #16338 USB Root Hub Shows Yellow Exclamation Mark in Device Manager

Forum thread:
https://forums.virtualbox.org/viewtopic.php?f=6&t=81228&hilit=Thunderbolt&sid=af360a89332f31d27ba3fc2bf64e502e&start=15

",vscheng
19300,VirtualBox 6.1.2 crashes on startup with Mac OS X 10.10.5,Mac OS X,all,VirtualBox 6.1.2,2020-02-12T10:14:41Z,2020-02-12T10:14:41Z,"VirtualBox 6.1.2 crashes on startup with Mac OS X 10.10.5 due to invalid code siganture ""/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox""

VirtualBox 6.0.16 works just fine.

----------------------------------------
LOGS:

Process:               VirtualBox [22213]
Path:                  /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
Identifier:            org.virtualbox.app.VirtualBox
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           VirtualBox [22213]
User ID:               501

Date/Time:             2020-02-11 14:24:34.192 +0100
OS Version:            Mac OS X 10.10.5 (14F2511)
Report Version:        11

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
  Referenced from: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
  Reason: no suitable image found.  Did find:
	/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox: code signature invalid for '/Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox'

Binary Images:
    0x7fff63536000 -     0x7fff6356c92f  dyld (353.2.4) <3C068A0D-69D5-3AD6-86D9-6261D3B1564E> /usr/lib/dyld
...",cdvk
18966,[VBoxSVGA with WDDM] Graphics corruption,Windows,Linux,VirtualBox 6.0.12,2020-02-12T12:55:08Z,2020-02-12T12:55:08Z,"Corrupt display of various elements in GUI / dialog boxes when using VBoxSVGA and Aero in Windows 7 guest on Linux host.

No problem using VBoxVGA / WDDM.",Thomas S.
19303,The instruction at 0x00007..referenced memory at 0x000..The memory could not be read.,other,Windows,VirtualBox 6.0.14,2020-02-12T15:48:53Z,2020-02-12T15:48:53Z,"The instruction at 0x00007..referenced memory at 0x000..The memory could not be read. This statement is happening to me with Virtual Box 6.0.14 version.

And interrupts my work.  ",kingor
19304,MSDOS MODE freezes under 98 SE in VBox on latest version,other,other,VirtualBox 6.1.2,2020-02-12T19:36:19Z,2020-02-12T19:36:19Z,"Example:

https://youtu.be/GWq_it8qLc0",ned33
17500,macOS 10.13.3 - Host Only Networking - Host not accessible,Mac OS X,other,VirtualBox 5.2.6,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
19308,"Networking mode ""NAT Network"" shows very poor throughput",Windows,Linux,VirtualBox 6.0.16,2020-02-13T12:47:40Z,2020-02-13T12:47:40Z,"Information about my environment:

Physical Host: Windows 10
VBox version: 6.0.16

Guest VM: Debian 9 Linux, 64 bit
Guest additions: 6.0.16.
Networking mode: NAT Network



Use case and problem description: 
I have a Linux guest on Win10 host, using vbox 6.0.16 guest additions. The VM rsync files from a vboxsf shared folder to a remote host via SSH. The network is 
plenty fast (modern 802.11n network - not used for anything else) on which I can easily achieve > 50 MiB/s (measured by iperf) from the host to the remote 
server. However, when I go from guest to remote server, it maxes out at about 200kiB/s

I have checked via atop and htop that CPU is not a bottleneck on neither client nor server. And the physical network is obviously not the bottleneck...
I have verified that I can both read and write files from the vboxsf share plenty fast as well.



I just tried plain NAT as networking mode and that works MUCH better. Now it is several MiBs per second. So it must be something to do with NAT network


So I guess there must be a problem in how networking is implemented in NAT Network compared to plain NAT that causes the slowdown.

",tdn
19141,windows 10 guest hangs on linux 5.3.12 host,Linux,Windows,VirtualBox 6.0.14,2020-02-13T20:46:32Z,2020-02-13T20:46:32Z,"I upgrade my linux host, the kernel upgraded from linux-5.1.16 to 5.3.12.
I started VirtualBox and resumed my windows guest.
I started typing in a browser window, and the guest stopped responding.
I saved the guest state and restarted, and got a windows bluescreen.

I restarted the VM, and the guest froze after login.
I restarted the VM, and again the guest froze.

I rebooted the host reverting back to linux 5.1.16.
I started my VM and have not had any issues since.",rc
19256,VBoxManage copyfrom --target-directory fails to copy,Windows,Windows,VirtualBox 5.2.36,2020-02-14T21:34:40Z,2020-02-14T21:34:40Z,"""copyfrom --target-directory"" fails on Windows 7 host with Windows XP/Windows 7 guests in VirtualBox 5.2.34 and 5.2.36.
The fix of #18724 seems to break this.
{{{
>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" guestcontrol vm_win7 copyfrom -v --username User --password 123 --target-directory D:\log C:\Users\User\Desktop\1.txt
Creating guest session as user 'User'...
Waiting for guest session to start...
Successfully started guest session (ID 1)
Copying from guest to host ...
Directory ""D:\log\"" already exists
Source: C:\Users\User\Desktop\1.txt
Copying ""C:\Users\User\Desktop\1.txt"" to ""D:\log\"" ...
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage.exe: error: Opening/creating destination file on host ""D:\log\"" failed: VERR_PATH_NOT_FOUND.
VBoxManage.exe: error: Error processing ""C:\Users\User\Desktop\1.txt"", rc=VERR_GENERAL_FAILURE
Closing guest session ...
}}}

When I try without --target-directory,
{{{
                      copyfrom [common-options]
                      [--dryrun] [--follow] [-R|--recursive]
                      <guest-src0> [guest-src1 [...]] <host-dst>
}}}
<host-dst> is written from start but not replaced. This corrupts <host-dst> if a smaller file is copied.
",robpats
19318,Critical Error,Linux,other,VirtualBox 6.1.2,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
19319,Mouse clicks unresponsive,Mac OS X,Windows,VirtualBox 6.1.2,2020-02-17T20:31:40Z,2020-02-17T20:31:40Z,"I running a Windows 10 VM under a Mac OSX host. Sporadically, the mouse click becomes unresponsive. The mouse is visible and the keyboard still works.  There is an error in the log with entry given below. The only way to resolve this issue is to shut down/restart the system, which I can do using the keyboard.

VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received ## seconds ago",gsdeerfield
17844,shared folders not working correctly on Lubuntu 18.0.4 guest,Mac OS X,Linux,VirtualBox 5.2.12,2020-02-18T09:05:18Z,2020-02-18T09:05:18Z,"Shared folders worked on Lubuntu 16 but failed after I upgraded to 18.0.4 (thankfully I have a backup copy of 16).
The shared folders mount points do not show up on reboot, and I have to re-run the installer script from the additions CD image after each reboot.  The mount points (sf_source) then show up in /media/... but get a permission denied error trying to view them.   This appears to be a permission (or access list) problem in creating the mountpoint directories, and I can view the contents of the directories with ""sudo ls /media/sf_source'.  This sudo workaround, is, of course, not something I can actually live with.
I have tried reinstalling/rebuilding the guest additions multiple times, without a change in behavior.
",ccox
18957,Frequent freezes in display output since 6.0,other,Windows,VirtualBox 6.0.12,2020-02-18T14:44:02Z,2020-02-18T14:44:02Z,"Since I updated from 5.2.x to 6.0.x I have problems with my Windows 10 guest. The problems manifest as freezes/pauses/hangs in the UI. The whole display output freezes and a bit later suddenly jumps to the desired output. This is especially visible in continuus animations, but annoying everywhere, especially while typing text.

This happens at least with:
* VBoxVGA without 3D acceleration
* VBoxSVGA without 3D acceleration
* VBoxSVGA with 3D acceleration

I didn't test VMSVGA. 2D-video acceleration settings don't seem to have an effect on the problem.

When I downgrade to 5.2.x (last I tried was 5.2.22) the problem is gone.

With 6.0.2 and 6.0.4 it was very easy to reproduce the problem, nearly every start of the guest showed it. With later versions (6.0.10 and especially 6.0.12) it got better (harder to reproduce). Now the problem only shows up every ~10 starts of the guest.

To get or ""fix"" the problem it is not enough to do a restart of the guest. A full shutdown and cold start is requried.
Additionally the problem can also start when you resume the guest from a saved state. But it seems like a resume can not ""fix"" it.

More information and multiple log files from older VirtualBox versions can be found in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=91836

Configuration details:

* VirtualBox 6.0.12 (I could also reproduce it with 6.0.2, 6.0.4 and 6.0.10)
* No extension pack installed
* Guest Additions 6.0.12
* Host OS: Windows 10 x64 1809 (I could also reproduce it with 1803)
* GPU: Intel HD Graphics 530 with driver 26.20.100.6912 (I could also reproduce it with 25.20.100.6519)
* 2 monitors with 1920x1080 resolution (I could also reproduce it with just 1 monitor)
* All monitors (both host and VM) at 100% scaling
* Guest OS: Windows 10 x64 1809 (I could also reproduce it with 1709)
* Guest is running in full screen mode
* Guest settings:
  * 3 of 4 CPU cores (I could also reproduce it with just 2 cores assigned)
  * 10 of 16 GB RAM
  * VRAM at maximum (128/256 MB)
  * All other settings are at their default for a Windows 10 x64 VM",cremor
18882,OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.,Windows,BSD,VirtualBox 6.0.10,2020-02-18T22:35:57Z,2020-02-18T22:35:57Z,"(This looks like a repeat of the Bug #9889, but is probably unrelated.)

I'm using VirtualBox on a Windows 10 host to run a FreeBSD and some Linux VMs (guests). The FreeBSD VM is my main desktop -- and the only guest with GUI (X11) configured.

My access to the Windows host itself is through Remote Desktop -- from a ""dumb"" terminal capable of running only the Remote Desktop client.

Things were working fine until the recent upgrade of the hardware -- the same disk was moved into a new machine, with faster CPUs and bigger RAM. There were no software configuration-changes.

VMs also came up Ok, but, upon starting X11 session in the FreeBSD guest, I started getting the error in subject from various X11-clients.

Since then I tried the following changes, to no avail:
 1. Upgrade the host software (including the extras pack) from 5.x to 6.0.10
 2. Change the ""Graphics Controller"" to ""VBoxSVGA"" in the VM's definition.
 3. Upgrade the virtualbox-ose-additions inside the VM from 5.x to 6.0.10

Nothing helped -- the machine comes up fine, simpler X11-clients (like xterm) work, but many (including Qt5-using programs) fail with the same message about 3D-acceleration...

I'm attaching the X-server's log from inside the VM, and VM's log from the host.

At the very least, the error should be more detailed. At best, it should not happen :)",mi
19091,Seamless Mode inactive with VMSVGA adapter,all,Linux,VirtualBox 6.0.14,2020-02-18T22:52:04Z,2020-02-18T22:52:04Z,"With VirtualBox 6.0+, VMSVGA is the default video adapter type for newely created Linux guests. But ""Seamless Mode"" does not work with VMSVGA - menu item ""Seamless Mode"" is inactive. If switch to VBoxVGA or VBoxSVGA, then Seamless Mode does work.",mikhailnov
19320,Allow exporting & importing of VMs with NVMe storage devices,all,all,VirtualBox 6.1.2,2020-02-19T03:13:25Z,2020-02-19T03:13:25Z,"VirtualBox errors when exporting a VM with an NVMe controller:

{{{
VBoxManage error: VBoxManage: error: Cannot handle medium attachment: storageBus is 7, channel is 0, device is 0
VBoxManage: error: Details: code VBOX_E_NOT_SUPPORTED (0x80bb0009), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""ExportTo(pAppliance, Bstr(pszAbsFilePath).raw(), pVSD.asOutParam())"" at line 1534 of file VBoxManageAppliance.cpp
}}}


There is no support for StorageBus_PCIe in src/VBox/Main/src-server/ApplianceImplExport.cpp nor ApplianceImplImport.cpp",davecardwell
12038,bridged interface  one way VLAN traffic,Mac OS X,Linux,VirtualBox 4.2.16,2020-02-19T09:41:37Z,2020-02-19T09:41:37Z,"A trunk port which is connected to the host adapter, is defined as a bridged interface.
On the guest host (Debian 3.2.32-1 x86_64)vlan support is enabled and the subinterfaces are up.
The host OS version is MAC OS 10.8.4.
The packet sniffer traces of the host physical interface and the virtualbox adapter interface shows that the packets ( pppoe padi ) send by the guest, will be send with the right vlan tag to the destination (seen on adapter and host interface level).
The request packet (pppoe pado) is seen only in the packet dump of the host interface (also with the expected vlan tag) but not seen in the virtualbox adapter dump ( result packet will not be send to guest os).
I have seen the same behavior when using a tagged vlan as a source interface for a guest network adapter.
I have tested this with the virtio-net and 82540EM network adapter types (same behavior).

Kind regards
Sven",svschmid
19322,Unable to use text instalation of linux operating system with accessibility turned on in virtual box.,Windows,Linux,VirtualBox 6.1.2,2020-02-19T21:10:10Z,2020-02-19T21:10:10Z,"When using the text installation of debian with accessibility features turned on it is impossible to use keyboard to perform any actions in a virtual machine after turning the speech on in the guest operating system. To reproduce these steps do the following steps: Run a debian64 bit full dvd installation iOs file in a virtual machine. You can find this file here: https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-10.3.0-amd64-DVD-1.iso
When you run a virtual machine, press the following keys: ""s"" and then press enter. You will turn on the speech support and the text installer. Then you will here speech synthesiser saying ""Select a language"". Try to press any keys on a keyboard, for example: numpad 7 and 9, 4 and 6, arrows up and down, any keys. You will notice that the virtual machine doesn't respond and you don't hear anything. That makes fully impossible to install debian for blind users to a virtual box. Blind people can only use text installer of debian with the speech support and now it is impossible to do in a virtual box. Please fix that issue! Thank you!",Vsevolod Popov
19155,When shutting down guest. rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003b2c,Windows,Linux,VirtualBox 6.0.14,2020-02-19T22:29:25Z,2020-02-19T22:29:25Z,"From Log file.

17:44:49.275875 
17:44:49.275877 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003b2c!!!
17:44:49.275893 
17:44:49.275894 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffcc8078561
17:44:49.275899 ExceptionInformation[0]=0000000000000001
17:44:49.275904 ExceptionInformation[1]=0000000000000021
17:44:49.275908 
17:44:49.275908 cs:rip=0033:00007ffcc8078561
17:44:49.275913 ss:rsp=002b:00000000099ef490 rbp=000000000c6e3cb0
17:44:49.275918 rax=0000000000000000 rcx=e8906b5e61f10000 rdx=0000000000000000 rbx=00000000087dc1e8
17:44:49.275923 rsi=0000000000000001 rdi=0000000000000021 rsp=00000000099ef490 rbp=000000000c6e3cb0
17:44:49.275927 r8 =00000000099ef148 r9 =000000000c6e3cb0 r10=0000000000000000 r11=00000000099ef420
17:44:49.275932 r12=0000000000000002 r13=000000000665cb40 r14=0000000000000000 r15=00000000fffffb83
17:44:49.275936 ds=002b es=002b fs=0053 gs=002b eflags=00010206
17:44:49.275941 p1home=00000000043b8c10 p2home=00000000043b8c10 pe3home=00000000087dc1e8
17:44:49.275945 p4home=00000000043b8c10 p5home=00000000099ef348 pe6home=0000000000000000
17:44:49.275949    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
17:44:49.275954 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
17:44:49.275961 
17:44:49.275962 Stack 00000000099ee370, dumping 0x1c90 bytes (low=00000000098f0000, high=00000000099f0000)
17:44:49.275970 00000000099ee370 0000: 70 e3 9e 09 00 00 00 00-73 74 61 63 6b 6d 61 72 p.......stackmar
17:44:49.275977 00000000099ee380 0010: 6b 65 72 00 fc 7f 00 00-80 00 00 00 00 00 00 01 ker.............
17:44:49.275979 00000000099ee390 0020: 00 20 5e 00 00 00 00 00-01 00 00 00 00 00 00 00 . ^.............
17:44:49.275980 00000000099ee3a0 0030: 80 eb 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.275981 00000000099ee3b0 0040: f0 f1 9e 09 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.275982 00000000099ee3c0 0050: 60 e5 9e 09 00 00 00 00-f0 f9 9e 09 00 00 00 00 `...............
17:44:49.275984 00000000099ee3d0 0060: 00 7f 89 80 fc 7f 00 00-6c 6c d5 f6 fc 7f 00 00 ........ll......
17:44:49.275985 00000000099ee3e0 0070: 60 e5 9e 09 00 00 00 00-61 85 07 c8 fc 7f 00 00 `.......a.......
17:44:49.275986 00000000099ee3f0 0080: 00 00 9f 09 00 00 00 00-00 00 8f 09 00 00 00 00 ................
17:44:49.275988 00000000099ee400 0090: 40 00 00 00 00 00 00 00-03 00 00 00 fc 7f 00 00 @...............
17:44:49.275989 00000000099ee410 00a0: 06 00 00 00 04 00 00 00-08 00 00 00 01 00 00 00 ................
17:44:49.275990 00000000099ee420 00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.275991 00000000099ee430 00c0: 00 00 00 00 00 00 00 00-bd b4 f9 f9 fc 7f 00 00 ................
17:44:49.275992 00000000099ee440 00d0: 60 e5 9e 09 00 00 00 00-80 98 f9 f9 fc 7f 00 00 `...............
17:44:49.275994 00000000099ee450 00e0: 00 00 00 00 00 00 00 00-80 e5 9e 09 00 00 00 00 ................
17:44:49.275995 00000000099ee460 00f0: 00 00 00 00 00 00 00 00-b0 e6 9e 09 00 00 00 00 ................
17:44:49.275996 00000000099ee470 0100: 00 00 00 00 00 00 00 00-bd b4 f9 f9 fc 7f 00 00 ................
17:44:49.275998 00000000099ee480 0110: fc 8c 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.275999 00000000099ee490 0120: 00 00 00 00 28 a0 00 00-da 20 77 55 00 00 00 00 ....(.... wU....
17:44:49.276000 00000000099ee4a0 0130: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276001 00000000099ee4b0 0140: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276003 00000000099ee4c0 0150: 11 82 c0 62 90 e8 00 00-7e 1d 7c 55 00 00 00 00 ...b....~.|U....
17:44:49.276004 00000000099ee4d0 0160: 00 00 f4 f9 fc 7f 00 00-f0 f9 9e 09 00 00 00 00 ................
17:44:49.276005 00000000099ee4e0 0170: f0 f1 9e 09 00 00 00 00-cb 81 fe f9 fc 7f 00 00 ................
17:44:49.276007 00000000099ee4f0 0180: 54 fc 7e 55 00 00 00 00-d4 33 08 fa fc 7f 00 00 T.~U.....3......
17:44:49.276008 00000000099ee500 0190: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276009 00000000099ee510 01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276010 00000000099ee520 01b0: 71 a2 06 00 00 00 00 00-56 fd fc f9 fc 7f 00 00 q.......V.......
17:44:49.276012 00000000099ee530 01c0: 30 00 00 00 00 00 00 00-00 00 00 00 06 00 00 00 0...............
17:44:49.276013 00000000099ee540 01d0: f0 f1 9e 09 00 00 00 00-28 eb 9e 09 00 00 00 00 ........(.......
17:44:49.276014 00000000099ee550 01e0: 10 e6 9e 09 00 00 00 00-74 79 6b f9 fc 7f 00 00 ........tyk.....
17:44:49.276015 00000000099ee560 01f0: f0 f1 9e 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276017 00000000099ee570 0200: f0 f1 9e 09 00 00 00 00-f0 f9 9e 09 00 00 00 00 ................
17:44:49.276018 00000000099ee580 0210: 10 e6 9e 09 00 00 00 00-71 a2 fa f9 fc 7f 00 00 ........q.......
17:44:49.276019 00000000099ee590 0220: 00 00 f4 f9 fc 7f 00 00-7f 47 fe f9 fc 7f 00 00 .........G......
17:44:49.276020 00000000099ee5a0 0230: 00 00 00 00 00 00 00 00-10 eb 9e 09 00 00 00 00 ................
17:44:49.276022 00000000099ee5b0 0240: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276023 00000000099ee5c0 0250: 80 eb 9e 09 00 00 00 00-ef 4b f4 f9 fc 7f 00 00 .........K......
17:44:49.276024 00000000099ee5d0 0260: 10 eb 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276025 00000000099ee5e0 0270: 3c bc 74 f9 fc 7f 00 00-00 00 6a f9 fc 7f 00 00 <.t.......j.....
17:44:49.276027 00000000099ee5f0 0280: 00 00 00 00 28 a0 00 00-40 e8 9e 09 00 00 00 00 ....(...@.......
17:44:49.276028 00000000099ee600 0290: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276029 00000000099ee610 02a0: c0 e7 3f 03 00 00 00 00-00 00 00 00 00 00 00 00 ..?.............
17:44:49.276030 00000000099ee620 02b0: de de de de ab ab ab ab-04 00 00 00 00 00 00 00 ................
17:44:49.276031 00000000099ee630 02c0: 07 00 01 11 04 02 01 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.276033 00000000099ee640 02d0: 0f 00 10 00 a0 1f 00 00-33 00 20 12 e3 12 82 48 ........3. ....H
17:44:49.276034 00000000099ee650 02e0: 30 51 2b 00 06 02 01 00-bd b4 f9 f9 fc 7f 00 00 0Q+.............
17:44:49.276035 00000000099ee660 02f0: 40 e8 9e 09 00 00 00 00-00 00 4e 04 00 00 00 00 @.........N.....
17:44:49.276037 00000000099ee670 0300: 00 00 64 03 00 00 00 00-00 00 00 00 00 00 00 00 ..d.............
17:44:49.276038 00000000099ee680 0310: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276039 00000000099ee690 0320: 00 00 00 00 00 00 00 00-00 00 40 01 00 00 00 00 ..........@.....
17:44:49.276040 00000000099ee6a0 0330: 00 00 00 00 00 00 00 00-70 fa 9e 09 00 00 00 00 ........p.......
17:44:49.276041 00000000099ee6b0 0340: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276043 00000000099ee6c0 0350: 00 00 00 00 00 00 00 00-80 49 40 01 00 00 00 00 .........I@.....
17:44:49.276044 00000000099ee6d0 0360: 50 0d 40 01 00 00 00 00-04 00 00 00 00 00 00 00 P.@.............
17:44:49.276045 00000000099ee6e0 0370: 30 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0...............
17:44:49.276046 00000000099ee6f0 0380: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276048 00000000099ee700 0390: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276049 00000000099ee710 03a0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276050 00000000099ee720 03b0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
17:44:49.276051 00000000099ee730 03c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276053 **************** ****  <ditto x 7>
17:44:49.276053 00000000099ee7b0 0440: 00 00 00 00 00 00 00 00-00 ea 9e 09 00 00 00 00 ................
17:44:49.276054 00000000099ee7c0 0450: 00 00 00 00 00 00 00 00-00 00 40 01 00 00 00 00 ..........@.....
17:44:49.276056 00000000099ee7d0 0460: 50 0d 40 01 00 00 00 00-04 00 00 00 00 00 00 00 P.@.............
17:44:49.276057 00000000099ee7e0 0470: 00 00 00 00 00 00 00 00-30 ea 9e 09 00 00 00 00 ........0.......
17:44:49.276058 00000000099ee7f0 0480: 00 00 00 00 00 00 00 00-80 49 40 01 00 00 00 00 .........I@.....
17:44:49.276059 00000000099ee800 0490: 50 0d 40 01 00 00 00 00-0a 00 00 00 73 1f c5 4c P.@.........s..L
17:44:49.276061 00000000099ee810 04a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276062 **************** ****  <ditto x 9>
17:44:49.276062 00000000099ee8b0 0540: a6 13 b1 d6 d7 c6 8d 3e-00 eb 00 00 06 00 00 00 .......>........
17:44:49.276064 00000000099ee8c0 0550: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276065 00000000099ee8d0 0560: 00 00 00 00 28 a0 00 00-20 eb 9e 09 00 00 00 00 ....(... .......
17:44:49.276066 00000000099ee8e0 0570: 00 00 00 00 00 00 00 00-30 eb 9e 09 00 00 00 00 ........0.......
17:44:49.276067 00000000099ee8f0 0580: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276068 00000000099ee900 0590: 00 00 00 00 28 a0 00 00-50 eb 9e 09 00 00 00 00 ....(...P.......
17:44:49.276070 00000000099ee910 05a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276071 00000000099ee920 05b0: c0 e7 3f 03 00 00 00 00-00 00 00 00 00 00 00 00 ..?.............
17:44:49.276072 00000000099ee930 05c0: de de de de ab ab ab ab-04 00 00 00 00 00 00 00 ................
17:44:49.276073 00000000099ee940 05d0: 07 00 01 11 04 02 01 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.276075 00000000099ee950 05e0: 61 ea 9e 09 00 00 00 00-a8 44 6c 27 cd ba 06 49 a........Dl'...I
17:44:49.276076 00000000099ee960 05f0: a6 13 b1 d6 d7 c6 8d 3e-00 00 00 00 02 00 00 00 .......>........
17:44:49.276077 00000000099ee970 0600: 50 eb 9e 09 00 00 00 00-00 00 4e 04 00 00 00 00 P.........N.....
17:44:49.276078 00000000099ee980 0610: 00 00 64 03 00 00 00 00-00 00 00 00 00 00 00 00 ..d.............
17:44:49.276079 00000000099ee990 0620: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276081 00000000099ee9a0 0630: 30 ea 9e 09 00 00 00 00-0c 00 00 00 00 00 00 00 0...............
17:44:49.276082 00000000099ee9b0 0640: 00 00 00 00 00 00 00 00-39 94 ec f8 fc 7f 00 00 ........9.......
17:44:49.276083 00000000099ee9c0 0650: 00 00 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276084 00000000099ee9d0 0660: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276085 00000000099ee9e0 0670: 06 00 00 00 00 00 00 00-30 ea 9e 09 00 00 00 00 ........0.......
17:44:49.276087 00000000099ee9f0 0680: 2c 80 43 da 28 a0 00 00-6b 97 ec f8 fc 7f 00 00 ,.C.(...k.......
17:44:49.276088 00000000099eea00 0690: 00 00 00 00 00 00 00 00-f0 ee 9e 09 00 00 00 00 ................
17:44:49.276089 00000000099eea10 06a0: f0 ee 9e 09 00 00 00 00-30 ed 9e 09 00 00 00 00 ........0.......
17:44:49.276090 00000000099eea20 06b0: 1c 80 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.276092 00000000099eea30 06c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276093 00000000099eea40 06d0: 48 f3 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276094 00000000099eea50 06e0: de de de de ab ab ab ab-30 ed 9e 09 00 00 00 00 ........0.......
17:44:49.276095 00000000099eea60 06f0: 02 00 00 00 fc 7f 00 00-00 30 cf 00 00 00 00 00 .........0......
17:44:49.276097 00000000099eea70 0700: d0 ef 9e 09 00 00 00 00-b9 b3 f9 f9 fc 7f 00 00 ................
17:44:49.276098 00000000099eea80 0710: e0 ea 9e 09 00 00 00 00-f0 f1 9e 09 00 00 00 00 ................
17:44:49.276099 00000000099eea90 0720: 00 ed 9e 09 00 00 00 00-40 cb 65 06 00 00 00 00 ........@.e.....
17:44:49.276100 00000000099eeaa0 0730: 02 00 00 00 00 00 00 00-21 00 00 00 00 00 00 00 ........!.......
17:44:49.276102 00000000099eeab0 0740: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276103 00000000099eeac0 0750: 00 00 00 00 00 00 00 00-d9 48 f4 f9 fc 7f 00 00 .........H......
17:44:49.276104 00000000099eead0 0760: f0 f1 9e 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276105 00000000099eeae0 0770: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
17:44:49.276107 00000000099eeaf0 0780: 19 00 00 00 00 00 00 00-fc 46 e7 f8 fc 7f 00 00 .........F......
17:44:49.276108 00000000099eeb00 0790: 02 00 00 00 00 00 00 00-50 eb 9e 09 00 00 00 00 ........P.......
17:44:49.276109 00000000099eeb10 07a0: 00 00 3b 04 00 00 00 00-64 d5 0a fa fc 7f 00 00 ..;.....d.......
17:44:49.276110 00000000099eeb20 07b0: 00 00 00 00 00 00 00 00-00 00 f4 f9 fc 7f 00 00 ................
17:44:49.276112 00000000099eeb30 07c0: f0 f1 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276113 00000000099eeb40 07d0: d4 33 08 fa fc 7f 00 00-f0 f9 9e 09 00 00 00 00 .3..............
17:44:49.276114 00000000099eeb50 07e0: 00 00 00 00 00 00 00 00-d0 eb 9e 09 00 00 00 00 ................
17:44:49.276115 00000000099eeb60 07f0: 71 a2 fa f9 fc 7f 00 00-00 00 8f 09 00 00 00 00 q...............
17:44:49.276117 00000000099eeb70 0800: 00 00 9f 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276118 00000000099eeb80 0810: 71 a2 fa f9 fc 7f 00 00-00 00 f4 f9 fc 7f 00 00 q...............
17:44:49.276119 00000000099eeb90 0820: 64 d5 0a fa fc 7f 00 00-f0 f9 9e 09 00 00 00 00 d...............
17:44:49.276120 00000000099eeba0 0830: 00 00 00 00 00 00 00 00-10 e6 9e 09 00 00 00 00 ................
17:44:49.276122 00000000099eebb0 0840: c0 fc fc f9 fc 7f 00 00-d4 33 08 fa fc 7f 00 00 .........3......
17:44:49.276123 00000000099eebc0 0850: d0 eb 9e 09 00 00 00 00-00 00 00 00 ab ab ab ab ................
17:44:49.276124 00000000099eebd0 0860: 0c 00 00 00 00 00 00 00-70 85 83 7f fc 7f 00 00 ........p.......
17:44:49.276125 00000000099eebe0 0870: bd 85 07 c8 fc 7f 00 00-00 00 05 c8 fc 7f 00 00 ................
17:44:49.276127 00000000099eebf0 0880: 98 08 0e c8 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276128 00000000099eec00 0890: 24 e6 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 $.........u.....
17:44:49.276129 00000000099eec10 08a0: 9c e6 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276130 00000000099eec20 08b0: 0c d7 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276132 00000000099eec30 08c0: 0c dd 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276133 00000000099eec40 08d0: bc de 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276134 00000000099eec50 08e0: 20 d5 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00  .........u.....
17:44:49.276135 00000000099eec60 08f0: f8 ba 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276137 00000000099eec70 0900: dc bb 11 80 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276138 00000000099eec80 0910: 54 ef 3b b6 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 T.;.............
17:44:49.276139 00000000099eec90 0920: 58 07 3b b6 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 X.;.............
17:44:49.276141 00000000099eeca0 0930: 70 f8 3a b6 fc 7f 00 00-c0 ee 9e 09 00 00 00 00 p.:.............
17:44:49.276142 00000000099eecb0 0940: bc 83 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.276143 00000000099eecc0 0950: 83 fb ff ff 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276144 00000000099eecd0 0960: 40 cb 65 06 00 00 00 00-02 00 00 00 00 00 00 00 @.e.............
17:44:49.276145 00000000099eece0 0970: 21 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 !...............
17:44:49.276147 00000000099eecf0 0980: b0 3c 6e 0c 00 00 00 00-ee 34 fe f9 fc 7f 00 00 .<n......4......
17:44:49.276148 00000000099eed00 0990: 10 8c 3b 04 00 00 00 00-10 8c 3b 04 00 00 00 00 ..;.......;.....
17:44:49.276149 00000000099eed10 09a0: e8 c1 7d 08 00 00 00 00-10 8c 3b 04 00 00 00 00 ..}.......;.....
17:44:49.276150 00000000099eed20 09b0: 48 f3 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276152 00000000099eed30 09c0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
17:44:49.276153 00000000099eed40 09d0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
17:44:49.276154 00000000099eed50 09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276155 **************** ****  <ditto x 2>
17:44:49.276156 00000000099eed80 0a10: 00 00 f1 61 5e 6b 90 e8-00 00 00 00 00 00 00 00 ...a^k..........
17:44:49.276157 00000000099eed90 0a20: e8 c1 7d 08 00 00 00 00-90 f4 9e 09 00 00 00 00 ..}.............
17:44:49.276158 00000000099eeda0 0a30: b0 3c 6e 0c 00 00 00 00-01 00 00 00 00 00 00 00 .<n.............
17:44:49.276159 00000000099eedb0 0a40: 21 00 00 00 00 00 00 00-48 f1 9e 09 00 00 00 00 !.......H.......
17:44:49.276161 00000000099eedc0 0a50: b0 3c 6e 0c 00 00 00 00-00 00 00 00 00 00 00 00 .<n.............
17:44:49.276162 00000000099eedd0 0a60: 20 f4 9e 09 00 00 00 00-02 00 00 00 00 00 00 00  ...............
17:44:49.276163 00000000099eede0 0a70: 40 cb 65 06 00 00 00 00-00 00 00 00 00 00 00 00 @.e.............
17:44:49.276164 00000000099eedf0 0a80: 83 fb ff ff 00 00 00 00-61 85 07 c8 fc 7f 00 00 ........a.......
17:44:49.276166 00000000099eee00 0a90: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276167 00000000099eee10 0aa0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
17:44:49.276168 00000000099eee20 0ab0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276169 **************** ****  <ditto x 23>
17:44:49.276170 00000000099eefa0 0c30: 00 00 00 00 00 00 00 00-00 00 8f 03 00 00 00 00 ................
17:44:49.276171 00000000099eefb0 0c40: 40 00 00 00 00 00 00 00-05 00 00 00 00 00 00 00 @...............
17:44:49.276172 00000000099eefc0 0c50: a0 9f bc 06 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276173 00000000099eefd0 0c60: 00 00 00 00 00 00 00 00-c0 51 8f 03 00 00 00 00 .........Q......
17:44:49.276175 00000000099eefe0 0c70: b0 0d 8f 03 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276176 00000000099eeff0 0c80: 10 00 00 00 00 00 00 00-c0 48 8f 03 00 00 00 00 .........H......
17:44:49.276177 00000000099ef000 0c90: 00 00 00 00 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276178 00000000099ef010 0ca0: 00 00 00 00 00 00 00 00-02 00 00 00 00 00 00 00 ................
17:44:49.276180 00000000099ef020 0cb0: 10 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276181 00000000099ef030 0cc0: 00 00 9a 03 00 00 00 00-d9 f0 9e 09 00 00 00 00 ................
17:44:49.276182 00000000099ef040 0cd0: 01 00 00 00 00 00 00 00-97 d9 f4 f9 fc 7f 00 00 ................
17:44:49.276183 00000000099ef050 0ce0: 40 00 00 00 00 00 00 00-05 00 00 00 00 00 00 00 @...............
17:44:49.276185 00000000099ef060 0cf0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276186 00000000099ef070 0d00: 00 21 4f 07 00 00 00 00-e0 20 4f 07 00 00 00 00 .!O...... O.....
17:44:49.276187 00000000099ef080 0d10: 02 00 00 00 00 00 00 00-98 3a cc 06 00 00 00 00 .........:......
17:44:49.276188 00000000099ef090 0d20: 40 f2 9e 09 00 00 00 00-c0 48 8f 03 00 00 00 00 @........H......
17:44:49.276189 00000000099ef0a0 0d30: 00 00 00 00 00 00 00 00-02 00 00 00 00 00 00 00 ................
17:44:49.276191 00000000099ef0b0 0d40: 30 00 00 00 00 00 00 00-00 00 cc 06 00 00 00 00 0...............
17:44:49.276192 00000000099ef0c0 0d50: 01 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276193 00000000099ef0d0 0d60: 00 00 00 00 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276194 00000000099ef0e0 0d70: 30 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0...............
17:44:49.276196 00000000099ef0f0 0d80: 00 00 9a 03 00 00 00 00-78 e0 84 80 fc 7f 00 00 ........x.......
17:44:49.276197 00000000099ef100 0d90: d0 3e 41 05 00 00 00 00-f8 be 13 c7 fc 7f 00 00 .>A.............
17:44:49.276198 00000000099ef110 0da0: 00 21 4f 07 00 00 00 00-e0 20 4f 07 00 00 00 00 .!O...... O.....
17:44:49.276200 00000000099ef120 0db0: c0 e2 bb 06 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276201 00000000099ef130 0dc0: ff ff ff ff 00 00 00 00-70 cb 65 06 00 00 00 00 ........p.e.....
17:44:49.276202 00000000099ef140 0dd0: f0 3c 6e 0c 00 00 00 00-e5 c7 d2 f6 fc 7f 00 00 .<n.............
17:44:49.276203 00000000099ef150 0de0: 60 b8 6e 0c 00 00 00 00-78 e0 84 80 fc 7f 00 00 `.n.....x.......
17:44:49.276204 00000000099ef160 0df0: 00 04 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276206 00000000099ef170 0e00: 00 00 00 00 00 00 00 00-77 db 84 7f fc 7f 00 00 ........w.......
17:44:49.276207 00000000099ef180 0e10: 40 ca 65 06 00 00 00 00-00 30 cf 00 00 00 00 00 @.e......0......
17:44:49.276208 00000000099ef190 0e20: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276209 00000000099ef1a0 0e30: 00 e8 bb 06 00 00 00 00-70 cb 65 06 00 00 00 00 ........p.e.....
17:44:49.276211 00000000099ef1b0 0e40: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276212 00000000099ef1c0 0e50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276213 00000000099ef1d0 0e60: 30 fb ff ff 90 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
17:44:49.276214 00000000099ef1e0 0e70: f0 00 00 00 d0 01 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276215 00000000099ef1f0 0e80: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276217 00000000099ef200 0e90: 61 85 07 c8 fc 7f 00 00-02 00 00 00 00 00 00 00 a...............
17:44:49.276218 00000000099ef210 0ea0: 01 00 00 00 00 00 00 00-21 00 00 00 00 00 00 00 ........!.......
17:44:49.276219 00000000099ef220 0eb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276220 **************** ****  <ditto x 6>
17:44:49.276221 00000000099ef290 0f20: 61 85 07 c8 fc 7f 00 00-00 00 00 00 00 00 00 00 a...............
17:44:49.276222 00000000099ef2a0 0f30: 00 00 00 00 00 00 00 00-90 f4 9e 09 00 00 00 00 ................
17:44:49.276223 00000000099ef2b0 0f40: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276224 00000000099ef2c0 0f50: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
17:44:49.276226 00000000099ef2d0 0f60: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276227 **************** ****  <ditto x 19>
17:44:49.276227 00000000099ef410 10a0: a1 90 c0 62 90 e8 00 00-00 00 00 00 00 00 00 00 ...b............
17:44:49.276229 00000000099ef420 10b0: 83 fb ff ff 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276230 00000000099ef430 10c0: 40 cb 65 06 00 00 00 00-02 00 00 00 00 00 00 00 @.e.............
17:44:49.276231 00000000099ef440 10d0: 21 00 00 00 00 00 00 00-0e c6 d2 f6 fc 7f 00 00 !...............
17:44:49.276232 00000000099ef450 10e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276234 00000000099ef460 10f0: e8 c1 7d 08 00 00 00 00-01 00 00 00 00 00 00 00 ..}.............
17:44:49.276235 00000000099ef470 1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276236 00000000099ef480 1110: 00 00 00 00 00 00 00 00-5c 85 07 c8 fc 7f 00 00 ........\.......
17:44:49.276256 00000000099ef490 1120: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276257 **************** ****  <ditto x 2>
17:44:49.276258 00000000099ef4c0 1150: a0 bc e3 0c 00 00 00 00-3a 9b 85 7f fc 7f 00 00 ........:.......
17:44:49.276259 00000000099ef4d0 1160: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
17:44:49.276260 00000000099ef4e0 1170: 48 11 00 00 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276262 00000000099ef4f0 1180: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276263 00000000099ef500 1190: 00 00 00 00 00 00 00 00-76 a4 85 7f fc 7f 00 00 ........v.......
17:44:49.276264 00000000099ef510 11a0: a0 bc e3 0c 00 00 00 00-00 e8 bb 06 00 00 00 00 ................
17:44:49.276266 00000000099ef520 11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276267 00000000099ef530 11c0: 00 00 00 00 00 00 00 00-65 00 85 7f fc 7f 00 00 ........e.......
17:44:49.276268 00000000099ef540 11d0: 00 00 00 00 00 00 00 00-8e 08 20 b6 fc 7f 00 00 .......... .....
17:44:49.276269 00000000099ef550 11e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276271 00000000099ef560 11f0: 00 00 00 00 00 00 00 00-b0 06 20 b6 fc 7f 00 00 .......... .....
17:44:49.276272 00000000099ef570 1200: 00 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276273 00000000099ef580 1210: 02 00 00 00 00 00 00 00-e5 30 85 7f fc 7f 00 00 .........0......
17:44:49.276274 00000000099ef590 1220: 00 00 00 00 00 00 00 00-00 e8 bb 06 00 00 00 00 ................
17:44:49.276276 00000000099ef5a0 1230: b0 3c 6e 0c 00 00 00 00-00 00 00 00 00 00 00 00 .<n.............
17:44:49.276277 00000000099ef5b0 1240: 68 36 d3 0d 00 00 00 00-18 0e d3 0d 00 00 00 00 h6..............
17:44:49.276278 00000000099ef5c0 1250: bb 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276280 00000000099ef5d0 1260: b0 3c 6e 0c 00 00 00 00-3a 42 85 7f fc 7f 00 00 .<n.....:B......
17:44:49.276281 00000000099ef5e0 1270: 00 e8 bb 06 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276282 00000000099ef5f0 1280: 02 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276283 00000000099ef600 1290: 02 00 00 00 00 00 00 00-81 f4 84 7f fc 7f 00 00 ................
17:44:49.276285 00000000099ef610 12a0: 00 00 00 00 00 00 00 00-10 fc e3 0c 00 00 00 00 ................
17:44:49.276286 00000000099ef620 12b0: 40 ca 65 06 00 00 00 00-78 e0 84 80 fc 7f 00 00 @.e.....x.......
17:44:49.276287 00000000099ef630 12c0: 83 fb ff ff 00 00 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276289 00000000099ef640 12d0: 01 00 00 00 00 00 00 00-50 de e0 09 00 00 00 00 ........P.......
17:44:49.276290 00000000099ef650 12e0: d0 e2 e0 09 00 00 00 00-1e 86 83 7f fc 7f 00 00 ................
17:44:49.276291 00000000099ef660 12f0: d8 e2 e0 09 00 00 00 00-0b 00 00 00 00 00 00 00 ................
17:44:49.276292 00000000099ef670 1300: 00 00 00 00 00 00 00 00-79 ac 17 b6 fc 7f 00 00 ........y.......
17:44:49.276294 00000000099ef680 1310: d0 e2 e0 09 00 00 00 00-c0 8f 83 7f fc 7f 00 00 ................
17:44:49.276295 00000000099ef690 1320: d8 e2 e0 09 00 00 00 00-0b 00 00 00 00 00 00 00 ................
17:44:49.276296 00000000099ef6a0 1330: 00 00 00 00 00 00 00 00-50 de e0 09 00 00 00 00 ........P.......
17:44:49.276297 00000000099ef6b0 1340: ae 85 fe 65 34 86 05 00-00 00 9f 09 00 00 00 00 ...e4...........
17:44:49.276299 00000000099ef6c0 1350: 83 fb ff ff 00 00 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276300 00000000099ef6d0 1360: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276301 00000000099ef6e0 1370: 0b d2 00 00 00 00 00 00-26 de 1f b6 fc 7f 00 00 ........&.......
17:44:49.276303 00000000099ef6f0 1380: 60 7c 9f 09 00 00 00 00-50 8d 83 7f fc 7f 00 00 `|......P.......
17:44:49.276304 00000000099ef700 1390: 50 dd e0 09 00 00 00 00-dc d7 10 b6 fc 7f 00 00 P...............
17:44:49.276305 00000000099ef710 13a0: 01 00 00 00 00 00 00 00-07 83 22 00 00 00 00 00 .........."".....
17:44:49.276306 00000000099ef720 13b0: 00 00 00 00 00 00 00 00-00 c0 a0 09 00 00 00 00 ................
17:44:49.276308 00000000099ef730 13c0: 00 00 9f 09 00 00 00 00-0a 2e 0f b6 fc 7f 00 00 ................
17:44:49.276309 00000000099ef740 13d0: 00 00 00 00 00 00 00 00-3e 0a 00 00 00 00 00 00 ........>.......
17:44:49.276310 00000000099ef750 13e0: 00 00 00 00 00 00 00 00-46 b6 15 b6 fc 7f 00 00 ........F.......
17:44:49.276311 00000000099ef760 13f0: 01 00 00 00 00 00 00 00-99 3e 0e b6 fc 7f 00 00 .........>......
17:44:49.276326 00000000099ef770 1400: 3e 0a 00 00 00 00 00 00-b8 39 0e b6 fc 7f 00 00 >........9......
17:44:49.276328 00000000099ef780 1410: 00 c0 a0 09 00 00 00 00-20 f8 9e 09 00 00 00 00 ........ .......
17:44:49.276329 00000000099ef790 1420: 00 00 9f 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276330 00000000099ef7a0 1430: 00 00 9f 09 00 00 00 00-19 98 0e b6 fc 7f 00 00 ................
17:44:49.276331 00000000099ef7b0 1440: 00 c0 a0 09 00 00 00 00-01 00 00 00 00 00 00 00 ................
17:44:49.276333 00000000099ef7c0 1450: 01 00 00 00 00 00 00 00-20 f8 9e 09 00 00 00 00 ........ .......
17:44:49.276334 00000000099ef7d0 1460: 00 00 9f 09 00 00 00 00-a8 63 0e b6 fc 7f 00 00 .........c......
17:44:49.276335 00000000099ef7e0 1470: 00 c0 a0 09 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276336 00000000099ef7f0 1480: 01 00 00 00 00 00 00 00-5c 04 00 00 00 00 00 00 ........\.......
17:44:49.276338 00000000099ef800 1490: 00 00 00 00 00 00 00 00-00 00 9f 09 00 00 00 00 ................
17:44:49.276339 00000000099ef810 14a0: 00 c0 a0 09 00 00 00 00-00 20 53 07 00 00 00 00 ......... S.....
17:44:49.276340 00000000099ef820 14b0: 00 3f 53 07 00 00 00 00-c3 2e 15 b6 fc 7f 00 00 .?S.............
17:44:49.276341 00000000099ef830 14c0: 30 06 31 b6 fc 7f 00 00-50 01 31 b6 fc 7f 00 00 0.1.....P.1.....
17:44:49.276343 00000000099ef840 14d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276344 00000000099ef850 14e0: 00 00 00 00 00 00 00 00-00 00 9f 09 00 00 00 00 ................
17:44:49.276345 00000000099ef860 14f0: a0 3f 53 07 00 00 00 00-d8 3c 15 b6 fc 7f 00 00 .?S......<......
17:44:49.276346 00000000099ef870 1500: 00 00 9f 09 00 00 00 00-00 c0 a0 09 00 00 00 00 ................
17:44:49.276348 00000000099ef880 1510: 00 20 53 07 00 00 00 00-00 00 00 00 00 00 00 00 . S.............
17:44:49.276349 00000000099ef890 1520: c0 69 9a 03 00 00 00 00-32 b2 88 80 fc 7f 00 00 .i......2.......
17:44:49.276350 00000000099ef8a0 1530: 00 00 00 00 00 00 00 00-2c 3b 00 00 00 00 00 00 ........,;......
17:44:49.276351 00000000099ef8b0 1540: 50 e6 19 07 00 00 00 00-00 00 00 00 00 00 00 00 P...............
17:44:49.276353 00000000099ef8c0 1550: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276354 00000000099ef8d0 1560: 00 00 00 00 00 00 00 00-50 e6 19 07 00 00 00 00 ........P.......
17:44:49.276355 00000000099ef8e0 1570: 2c 3b 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ,;..............
17:44:49.276356 00000000099ef8f0 1580: 50 e6 19 07 00 00 00 00-3f c6 7f 80 fc 7f 00 00 P.......?.......
17:44:49.276358 00000000099ef900 1590: 00 00 00 00 00 00 00 00-a0 3f 53 07 00 00 00 00 .........?S.....
17:44:49.276359 00000000099ef910 15a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276360 00000000099ef920 15b0: 50 e6 19 07 00 00 00 00-52 63 8a 80 fc 7f 00 00 P.......Rc......
17:44:49.276361 00000000099ef930 15c0: 00 6b 31 07 00 00 00 00-00 6b 31 07 00 00 00 00 .k1......k1.....
17:44:49.276362 00000000099ef940 15d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276364 00000000099ef950 15e0: 00 00 00 00 00 00 00 00-9f 1d 77 55 00 00 00 00 ..........wU....
17:44:49.276365 00000000099ef960 15f0: 00 6b 31 07 00 00 00 00-00 00 00 00 00 00 00 00 .k1.............
17:44:49.276366 00000000099ef970 1600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276367 00000000099ef980 1610: 00 00 00 00 00 00 00 00-3b 1e 77 55 00 00 00 00 ........;.wU....
17:44:49.276369 00000000099ef990 1620: c0 2a 80 55 00 00 00 00-00 6b 31 07 00 00 00 00 .*.U.....k1.....
17:44:49.276370 00000000099ef9a0 1630: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276371 00000000099ef9b0 1640: 00 00 00 00 00 00 00 00-74 79 6b f9 fc 7f 00 00 ........tyk.....
17:44:49.276372 00000000099ef9c0 1650: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276373 00000000099ef9d0 1660: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276375 00000000099ef9e0 1670: 00 00 00 00 00 00 00 00-71 a2 fa f9 fc 7f 00 00 ........q.......
17:44:49.276376 00000000099ef9f0 1680: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276377 **************** ****  <ditto x 2>
17:44:49.276378 00000000099efa20 16b0: 00 00 00 00 5d c0 13 47-00 00 00 00 00 00 00 00 ....]..G........
17:44:49.276379 00000000099efa30 16c0: b0 6a d5 f6 fc 7f 00 00-60 e5 9e 09 00 00 00 00 .j......`.......
17:44:49.276380 00000000099efa40 16d0: e5 ff 03 00 68 57 35 8e-ed aa c6 b1 fc 7f 00 00 ....hW5.........
17:44:49.276381 00000000099efa50 16e0: b0 6a d5 f6 fc 7f 00 00-60 e5 9e 09 00 00 00 00 .j......`.......
17:44:49.276383 00000000099efa60 16f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276384 **************** ****  <ditto x 88>
17:44:49.276385 00000000099efff0 1c80: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276399 Thread ID:   0000000000003b2c
17:44:49.276404 Thread name: EMT
17:44:49.276408 Thread IPRT: 000000000719e650
17:44:49.276412 
17:44:49.276412 Loaded Modules:
17:44:49.276412 Address range                    [*] Timestamp Path
17:44:49.276417 00007ff69d790000..00007ff69d8a4fff   5d9f7c37  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
17:44:49.276423 00007ffcf9f40000..00007ffcfa12cfff   1f1a0210  C:\WINDOWS\SYSTEM32\ntdll.dll
17:44:49.276428 00007ffcf96a0000..00007ffcf9752fff   250a0626  C:\WINDOWS\System32\KERNEL32.DLL
17:44:49.276433 00007ffcf6cd0000..00007ffcf6f62fff   fc217636  C:\WINDOWS\System32\KERNELBASE.dll
17:44:49.276438 0000000068000000..0000000068065fff   5b060941  C:\WINDOWS\System32\QIPCAP64.dll
17:44:49.276442 00007ffcf9890000..00007ffcf9932fff   b12069f9  C:\WINDOWS\System32\ADVAPI32.dll
17:44:49.276448 00007ffcf97f0000..00007ffcf988dfff   f362c2f9  C:\WINDOWS\System32\msvcrt.dll
17:44:49.276453 00007ffcf74e0000..00007ffcf757dfff   7d59184a  C:\WINDOWS\System32\sechost.dll
17:44:49.276458 00007ffcf8e20000..00007ffcf8f41fff   755dd37f  C:\WINDOWS\System32\RPCRT4.dll
17:44:49.276463 00007ffcf75c0000..00007ffcf8ab3fff   8126cd3a  C:\WINDOWS\System32\SHELL32.dll
17:44:49.276467 00007ffcf6f70000..00007ffcf6fb9fff   ca7e64ca  C:\WINDOWS\System32\cfgmgr32.dll
17:44:49.276472 00007ffcf6000000..00007ffcf60f9fff   15f8b9b3  C:\WINDOWS\System32\ucrtbase.dll
17:44:49.276477 00007ffcf8ac0000..00007ffcf8b67fff   9a0e77eb  C:\WINDOWS\System32\shcore.dll
17:44:49.276482 00007ffcf9120000..00007ffcf944bfff   c366780e  C:\WINDOWS\System32\combase.dll
17:44:49.276487 00007ffcf6160000..00007ffcf61ddfff   94fbdec9  C:\WINDOWS\System32\bcryptPrimitives.dll
17:44:49.276491 00007ffcf6490000..00007ffcf6bdcfff   9a536081  C:\WINDOWS\System32\windows.storage.dll
17:44:49.276496 00007ffcf6c10000..00007ffcf6caffff   448f33c2  C:\WINDOWS\System32\msvcp_win.dll
17:44:49.276501 00007ffcf5fb0000..00007ffcf5fd3fff   36191177  C:\WINDOWS\System32\profapi.dll
17:44:49.276506 00007ffcf5f50000..00007ffcf5facfff   8941f3e3  C:\WINDOWS\System32\powrprof.dll
17:44:49.276511 00007ffcf7160000..00007ffcf71b1fff   4392c932  C:\WINDOWS\System32\shlwapi.dll
17:44:49.276516 00007ffcf7590000..00007ffcf75b8fff   f945b633  C:\WINDOWS\System32\GDI32.dll
17:44:49.276520 00007ffcf6fc0000..00007ffcf7158fff   99521ac9  C:\WINDOWS\System32\gdi32full.dll
17:44:49.276525 00007ffcf9500000..00007ffcf9696fff   9d4422cf  C:\WINDOWS\System32\USER32.dll
17:44:49.276530 00007ffcf61e0000..00007ffcf61fffff   ff141dbb  C:\WINDOWS\System32\win32u.dll
17:44:49.276534 00007ffcf5f30000..00007ffcf5f40fff   be88784d  C:\WINDOWS\System32\kernel.appcore.dll
17:44:49.276539 00007ffcf6cb0000..00007ffcf6cc6fff   fe800ac7  C:\WINDOWS\System32\cryptsp.dll
17:44:49.276544 00007ffcf5500000..00007ffcf55c5fff   e8b181dc  C:\WINDOWS\SYSTEM32\DNSAPI.dll
17:44:49.276549 00007ffcf99c0000..00007ffcf9a2cfff   19b2d7cc  C:\WINDOWS\System32\WS2_32.dll
17:44:49.276554 00007ffcf8ca0000..00007ffcf8ca7fff   d06e5a23  C:\WINDOWS\System32\NSI.dll
17:44:49.276558 00007ffcf97c0000..00007ffcf97edfff   789dcfe1  C:\WINDOWS\System32\IMM32.DLL
17:44:49.276563 00007ffcf54c0000..00007ffcf54fcfff   1ee25965  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
17:44:49.276568 00007ffcf3bb0000..00007ffcf3bb4fff   5d9f7bec  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
17:44:49.276573 00007ffcf6100000..00007ffcf6158fff   d51e499a  C:\WINDOWS\System32\Wintrust.dll
17:44:49.276578 00007ffcf5fe0000..00007ffcf5ff1fff   ac91a4b2  C:\WINDOWS\System32\MSASN1.dll
17:44:49.276583 00007ffcf62b0000..00007ffcf648afff   b2fbbe58  C:\WINDOWS\System32\CRYPT32.dll
17:44:49.276587 0000000001010000..0000000001035fff   4d019572  C:\WINDOWS\System32\bcrypt.dll
17:44:49.276592 00007ffcf50c0000..00007ffcf50f2fff   eb037b86  C:\WINDOWS\system32\rsaenh.dll
17:44:49.276597 00007ffcf5970000..00007ffcf597bfff   210d2d73  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
17:44:49.276601 00007ffcf9100000..00007ffcf911cfff   00e30045  C:\WINDOWS\System32\imagehlp.dll
17:44:49.276606 00007ffcf4900000..00007ffcf4921fff   7f4edceb  C:\WINDOWS\SYSTEM32\gpapi.dll
17:44:49.276611 00007ffcd8d90000..00007ffcd8dbefff   1a60e9ce  C:\WINDOWS\System32\cryptnet.dll
17:44:49.276616 00007ffc80730000..00007ffc80d11fff   5d9f7c37  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.276621 0000000055750000..0000000055821fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.276626 0000000056070000..0000000056107fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
17:44:49.276630 00007ffcc7b40000..00007ffcc7cc7fff   5d9f7c48  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
17:44:49.276635 00007ffcf8cb0000..00007ffcf8e04fff   197cc46a  C:\WINDOWS\System32\ole32.dll
17:44:49.276640 00007ffcf8f50000..00007ffcf9013fff   bcde805b  C:\WINDOWS\System32\OLEAUT32.dll
17:44:49.276645 00007ffcda970000..00007ffcdaa96fff   9747484e  C:\WINDOWS\SYSTEM32\OPENGL32.dll
17:44:49.276650 00007ffc80d20000..00007ffc830a6fff   5d9f7c41  C:\Program Files\Oracle\VirtualBox\VBoxGlobal.dll
17:44:49.276656 0000000053f20000..0000000054484fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
17:44:49.276661 00007ffc80130000..00007ffc80726fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
17:44:49.276665 00000000539b0000..0000000053f10fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
17:44:49.276670 00000000556f0000..0000000055743fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
17:44:49.276675 00007ffcebbe0000..00007ffcebc03fff   01dd0441  C:\WINDOWS\SYSTEM32\WINMM.dll
17:44:49.276680 00007ffcda930000..00007ffcda95bfff   80b792c5  C:\WINDOWS\SYSTEM32\GLU32.dll
17:44:49.276685 00007ffcddd70000..00007ffcddd8afff   696e6b80  C:\WINDOWS\SYSTEM32\MPR.dll
17:44:49.276690 00007ffcebbb0000..00007ffcebbdcfff   61c36296  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
17:44:49.276694 00007ffcced10000..00007ffccee3dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
17:44:49.276699 00007ffcf2600000..00007ffcf269bfff   607fb06a  C:\WINDOWS\system32\uxtheme.dll
17:44:49.276704 00007ffcbf400000..00007ffcbf613fff   5c94072c  C:\Program Files\NVIDIA Corporation\nview\nViewH64.dll
17:44:49.276709 00007ffcf42c0000..00007ffcf42edfff   674bb59c  C:\WINDOWS\SYSTEM32\dwmapi.dll
17:44:49.276714 00007ffcef9e0000..00007ffcef9e9fff   b11b88e5  C:\WINDOWS\System32\VERSION.dll
17:44:49.276719 00007ffcf4c80000..00007ffcf4cb0fff   376a9861  C:\WINDOWS\SYSTEM32\ntmarta.dll
17:44:49.276724 00007ffcf5e30000..00007ffcf5e57fff   153decdb  C:\WINDOWS\system32\userenv.dll
17:44:49.276729 0000000004bb0000..0000000004c51fff   aaba4fa9  C:\WINDOWS\System32\clbcatq.dll
17:44:49.276734 00007ffcc6ee0000..00007ffcc7283fff   5d9f7c45  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
17:44:49.276739 00007ffcc80f0000..00007ffcc81c4fff   5d9f7c3c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
17:44:49.276743 0000000008580000..00000000086ebfff   3243efc5  C:\WINDOWS\System32\MSCTF.dll
17:44:49.276748 00007ffceb370000..00007ffceb3c5fff   28590552  C:\WINDOWS\system32\dataexchange.dll
17:44:49.276753 00007ffcf3320000..00007ffcf359dfff   13a31007  C:\WINDOWS\system32\d3d11.dll
17:44:49.276758 00007ffced1f0000..00007ffced3b2fff   517b0b92  C:\WINDOWS\system32\dcomp.dll
17:44:49.276763 00007ffcf49d0000..00007ffcf4a91fff   8bbb106a  C:\WINDOWS\system32\dxgi.dll
17:44:49.276767 00007ffcf3f80000..00007ffcf418cfff   270a22eb  C:\WINDOWS\system32\twinapi.appcore.dll
17:44:49.276772 00007ffcf4190000..00007ffcf41b7fff   fd3b8fed  C:\WINDOWS\system32\RMCLIENT.dll
17:44:49.276777 00007ffcc4640000..00007ffcc46d9fff   14ab50a3  C:\Windows\System32\ActXPrxy.dll
17:44:49.276782 00007ffce2d50000..00007ffce348efff   038397d3  C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
17:44:49.276787 00007ffcea490000..00007ffcea524fff   1163b0af  C:\WINDOWS\System32\TextInputFramework.dll
17:44:49.276792 00007ffce9d80000..00007ffcea0a1fff   0ef1f94b  C:\WINDOWS\System32\CoreUIComponents.dll
17:44:49.276797 00007ffced7c0000..00007ffced8a1fff   57021383  C:\WINDOWS\System32\CoreMessaging.dll
17:44:49.276801 00007ffcf14c0000..00007ffcf1612fff   57f8d9f0  C:\WINDOWS\SYSTEM32\wintypes.dll
17:44:49.276806 00007ffce5900000..00007ffce596bfff   2b9a3a00  C:\WINDOWS\system32\Oleacc.dll
17:44:49.276811 00007ffceb3d0000..00007ffceb3e0fff   80ed95b9  C:\WINDOWS\system32\wbem\wbemprox.dll
17:44:49.276816 00007ffcec520000..00007ffcec5a4fff   264de62a  C:\WINDOWS\SYSTEM32\wbemcomn.dll
17:44:49.276821 00007ffcea450000..00007ffcea463fff   42167f4e  C:\WINDOWS\system32\wbem\wbemsvc.dll
17:44:49.276826 00007ffcea920000..00007ffceaa10fff   c27bfeee  C:\WINDOWS\system32\wbem\fastprox.dll
17:44:49.276830 00007ffcb60a0000..00007ffcb63d0fff   5d9f7c3d  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.276835 00000000555e0000..00000000556eafff   5d9f7c48  C:\Program Files\Oracle\VirtualBox\VBoxREM.dll
17:44:49.276841 00007ffcd0a10000..00007ffcd0a90fff   c42656ba  C:\Windows\System32\NetSetupShim.dll
17:44:49.276846 00007ffcf9a30000..00007ffcf9ea5fff   cc9bc0eb  C:\WINDOWS\System32\setupapi.dll
17:44:49.276851 00007ffcebeb0000..00007ffcebed4fff   567de38b  C:\Windows\System32\NetSetupApi.dll
17:44:49.276856 00007ffcee450000..00007ffcee462fff   415b279a  C:\Windows\System32\DEVRTL.dll
17:44:49.276860 00007ffceda80000..00007ffcedb4cfff   b7ea870e  C:\Windows\System32\NetSetupEngine.dll
17:44:49.276865 00007ffcf18c0000..00007ffcf18cafff   4eee05dd  C:\WINDOWS\SYSTEM32\WINNSI.DLL
17:44:49.276870 00007ffcf3b10000..00007ffcf3b1afff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
17:44:49.276876 00007ffcf3920000..00007ffcf392cfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
17:44:49.276881 00007ffc7f750000..00007ffc80129fff   5d9f7c45  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.276885 00007ffceff10000..00007ffceff73fff   5d9f7c3c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
17:44:49.276890 00007ffceb580000..00007ffceb5dbfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
17:44:49.276895 00007ffcf21d0000..00007ffcf21e3fff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
17:44:49.276901 00007ffcf36e0000..00007ffcf36ebfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
17:44:49.276906 00007ffcf1e00000..00007ffcf1e0cfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
17:44:49.276911 00007ffcf26e0000..00007ffcf26f5fff   94c6e95c  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
17:44:49.276934 00007ffcf26c0000..00007ffcf26dbfff   3a6169db  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
17:44:49.276941 00007ffcf10c0000..00007ffcf112ffff   2aab5430  C:\WINDOWS\System32\MMDevApi.dll
17:44:49.276946 00007ffcf5d60000..00007ffcf5d88fff   3306001c  C:\WINDOWS\System32\DEVOBJ.dll
17:44:49.276953 00007ffcf3080000..00007ffcf3228fff   296f9bb4  C:\WINDOWS\System32\PROPSYS.dll
17:44:49.276962 00007ffcc8050000..00007ffcc80e5fff*  807cb1be  C:\WINDOWS\System32\dsound.dll
17:44:49.276970 00007ffcf0af0000..00007ffcf0c37fff   6716b91a  C:\WINDOWS\System32\AUDIOSES.DLL
17:44:49.276978 00007ffcf1270000..00007ffcf1279fff   e8464c59  C:\WINDOWS\SYSTEM32\AVRT.dll
17:44:49.276998 00007ffcf41c0000..00007ffcf41d3fff   dfd6e84b  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
17:44:49.277006 00007ffce5f60000..00007ffce5fa3fff   96f675cf  C:\WINDOWS\System32\wdmaud.drv
17:44:49.277011 00007ffcf3c70000..00007ffcf3c78fff   26b922dc  C:\WINDOWS\SYSTEM32\ksuser.dll
17:44:49.277016 00007ffcf3a30000..00007ffcf3a3cfff   d0ebc7cc  C:\WINDOWS\System32\msacm32.drv
17:44:49.277020 00007ffcf3a10000..00007ffcf3a2bfff   a416f17e  C:\WINDOWS\SYSTEM32\MSACM32.dll
17:44:49.277025 00007ffcf0d80000..00007ffcf0d89fff   240f6209  C:\WINDOWS\System32\midimap.dll
17:44:49.277030 00007ffcf57a0000..00007ffcf5806fff   9cffe601  C:\WINDOWS\system32\mswsock.dll
17:44:49.277035 00007ffcea5d0000..00007ffcea709fff   951b586c  C:\Windows\System32\Windows.UI.dll
17:44:49.277040 00007ffcea0e0000..00007ffcea1abfff   d5eb338f  C:\Windows\System32\InputHost.dll
17:44:49.277044 00007ffcf2710000..00007ffcf2ccdfff   9370a562  C:\Windows\System32\d2d1.dll
17:44:49.277049 
17:44:49.277049 Potential code addresses on the stack:
17:44:49.277053 Xcpt PC         : 00007ffcc8078561 - 0x00028561 bytes into C:\WINDOWS\System32\dsound.dll
17:44:49.277060 00000000099ef4c8: 00007ffc7f859b3a - 0x00109b3a bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277066 00000000099ef508: 00007ffc7f85a476 - 0x0010a476 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277072 00000000099ef538: 00007ffc7f850065 - 0x00100065 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277077 00000000099ef548: 00007ffcb620088e - 0x0016088e bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277082 00000000099ef568: 00007ffcb62006b0 - 0x001606b0 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277087 00000000099ef578: 00007ffc808a675a - 0x0017675a bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277093 00000000099ef588: 00007ffc7f8530e5 - 0x001030e5 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277100 00000000099ef5d8: 00007ffc7f85423a - 0x0010423a bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277105 00000000099ef5f8: 00007ffc808a675a - 0x0017675a bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277110 00000000099ef608: 00007ffc7f84f481 - 0x000ff481 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277116 00000000099ef628: 00007ffc8084e078 - 0x0011e078 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277122 00000000099ef638: 00007ffcb60a0000 - 0x00000000 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277127 00000000099ef658: 00007ffc7f83861e - 0x000e861e bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277133 00000000099ef678: 00007ffcb617ac79 - 0x000dac79 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277138 00000000099ef688: 00007ffc7f838fc0 - 0x000e8fc0 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277144 00000000099ef6c8: 00007ffcb60a0000 - 0x00000000 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277150 00000000099ef6e8: 00007ffcb61fde26 - 0x0015de26 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277155 00000000099ef6f8: 00007ffc7f838d50 - 0x000e8d50 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277160 00000000099ef708: 00007ffcb610d7dc - 0x0006d7dc bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277166 00000000099ef738: 00007ffcb60f2e0a - 0x00052e0a bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277171 00000000099ef758: 00007ffcb615b646 - 0x000bb646 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277176 00000000099ef768: 00007ffcb60e3e99 - 0x00043e99 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277181 00000000099ef778: 00007ffcb60e39b8 - 0x000439b8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277187 00000000099ef7a8: 00007ffcb60e9819 - 0x00049819 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277193 00000000099ef7d8: 00007ffcb60e63a8 - 0x000463a8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277199 00000000099ef828: 00007ffcb6152ec3 - 0x000b2ec3 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277204 00000000099ef830: 00007ffcb6310630 - 0x00270630 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277210 00000000099ef838: 00007ffcb6310150 - 0x00270150 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277215 00000000099ef868: 00007ffcb6153cd8 - 0x000b3cd8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277221 00000000099ef898: 00007ffc8088b232 - 0x0015b232 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277227 00000000099ef8f8: 00007ffc807fc63f - 0x000cc63f bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277233 00000000099ef928: 00007ffc808a6352 - 0x00176352 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277238 00000000099ef958: 0000000055771d9f - 0x00021d9f bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277244 00000000099ef988: 0000000055771e3b - 0x00021e3b bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277248 00000000099ef990: 0000000055802ac0 - 0x000b2ac0 bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277254 00000000099ef9b8: 00007ffcf96b7974 - 0x00017974 bytes into C:\WINDOWS\System32\KERNEL32.DLL
17:44:49.277258 00000000099ef9e8: 00007ffcf9faa271 - 0x0006a271 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
17:44:49.277263 00000000099efa30: 00007ffcf6d56ab0 - 0x00086ab0 bytes into C:\WINDOWS\System32\KERNELBASE.dll
17:44:49.277268 00000000099efa50: 00007ffcf6d56ab0 - 0x00086ab0 bytes into C:\WINDOWS\System32\KERNELBASE.dll
17:46:15.060205 GUI: UIMediumEnumerator: Medium-enumeration finished!
",garypx
19323,"VirtualBox show me error when i click on ""Start"" button (it was working perfectly 3 month ago)",Mac OS X,other,VirtualBox 6.1.0,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
18653,"VBox fails to download ""VirtualBox Guest Additions"" disk image since 6.0.0",Linux,Windows,VirtualBox 6.0.8,2020-02-20T09:12:01Z,2020-02-20T09:12:01Z,"Hi
Since around upgrading to VirtualBox 6.0.0 (valid up to 6.0.8), VBox fails to download ""VirtualBox Guest Additions"" disk image since 6.0.0.
When clicking over ""Insert Guest Additions CD Image..."" in the ""Device"" menu, it always ends with the following:
""The network operation failed with the following error: 
During network request: Unknown reason.""

(BTW when it was working, this meant clicking too many times on ""OK"" just to get through, once should be enough)",vtt
19325,6.1.4_136177_fedora31-1 : Checksum mismatch,Linux,other,VirtualBox 6.1.2,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
19327,Linux host vlan interface cannot be bridged to guest,Linux,all,VirtualBox 6.1.4,2020-02-20T16:56:07Z,2020-02-20T16:56:07Z,Linux host vlan interface cannot be bridged to guest.,tulipb
19328,Critical error pop up when starting machine,Windows,Linux,VirtualBox 6.1.2,2020-02-20T22:31:08Z,2020-02-20T22:31:08Z,"When I try to load virtual machine after rebooting I get a pop up stating critical error and suggesting I post here with the logs. If it is relevant, Ubuntu had just performed updates.",tdsTPPS
19330,Can't push Next button when VirtualBox Manager Import Virtual Appliance in  large zoom display setting,Windows,all,VirtualBox 6.1.4,2020-02-21T06:42:01Z,2020-02-21T06:42:01Z,"I am using surface pro 7 with display 300% scale setting.
When Virtualbox Manager -> ""Import Virtual Appliance"", I can't push ""Next"" button because ""Import Virtual Appliance"" window is very large and some buttons appear out of display(attached virualbox6.1.4-scale300%.PNG).

This problem occurs with version 6.1.X, not occurs with version 6.0.X(attached virtual6.0.16-scale300%.PNG).

Of course, I don't always want to use 300%. I wanted to show that this problem occurs even on a famous PC(surface pro 7).
I usually use Fujitsu LIFEBOOK UH75/C3. In this Laptop PC, this problem occurs in its default scale(150%) and not occurs in 125% or less.

Fujits LIFEBOOK UH75/C3: 13.3in(1920 x 1080)
Surface Pro 7 12.3in(2736 x 1824)
Windows 10(1903)
",TT
19331,Any guest crashes with Linux 5.5 as host and VBox > 6.0.0,Linux,all,VirtualBox 6.1.4,2020-02-21T15:13:24Z,2020-02-21T15:13:24Z,"Ever since going from VBox 5.x to 6.x, guests are practically unusable because they crash or have other severe problems (corruption of data passed from host to guest, e.g. network data, file data, ...).
Log is attached of one of the cases with a Windows 10 Guest.",Thermi
19332,keyboard mapping problem on international MacBook Pro keyboard,Mac OS X,all,VirtualBox 6.1.4,2020-02-21T18:22:34Z,2020-02-21T18:22:34Z,"Keyboard mapping is complex. There are tons of components that have an opinion about what code needs to be mapped to what other code. But when using VirtualBox on MacBook Pro host with an Apple international ISO-like keyboard, something strange happens. The keys labeled ""§/±"" and ""`/~"" are not mapped correctly. It do not seem a problem of the guest operating system, it even shows when 'booting' a test virtual machine just into GRUB.

My keyboard layout on the host machine is correctly configured (Dutch) and working. 

The key labeled ""§/±"" (directly below the esc-key in the upper-right corner) assumingly produces the USB HID code 0x64 (""non US\|""). This  produces an macos key event with the apple key code 0x0a (and indeed leads to a ""§"" or ""±"" when typing on the host OS). The key labeled ""`/~"" (directly right to the left shift key) assumingly produces the the USB HID code 0x64 (""grave-tilde""). This produces an macos key event with apple key code 0x32 and indeed leeds to a '`' or '~' when typing on the host OS.

When typing these keys in a guest, I get '</>' for the '`/~' key and '`/~' when typing the ""§/±"" key.

Confusing indeed. The US ANSI-like MacBook Pro keyboard has no ""§/±"" key and the ""`/~"" is where the ""§/±"" is on an international MacBook Pro.

The problem is not caused by a mapping problem in Linux and/or X running inside the virtual machine. As said, the incorrect mapping is already visible in the GRUB console.

It can be _worked around_, of course, by fiddling with the Linux and/or X mappings, of course. But still I think there is a problem mapping the 'grave\tilde' key on a host MacBook Pro with international keyboard to the proper key in the guest.",duco
19334,VirtualBox version 6.1.2.,Windows,all,VirtualBox 6.1.2,2020-02-21T21:50:16Z,2020-02-21T21:50:16Z,"Hello Oracle,

I have 2 complaints that I consider bugs in the new version of Virtual box.

but first I like to thank you so much for VirtualBox, I use it since 10 years and cannot live with out it, and this even I am specialized on Microsoft products since 1982!

Complaint/Problem-1: on the front page of ""Oracle VM VirtualBox Manager"" the virtual machine was showing the path including the drive where the VirtualBox guest is located, however with the new version it was taken away, which means that I have to press settings and then press storage and then press the *.vdi file to see where the file is located, and that is more than ammoying and delaying me, because4 I use over 30 Virtual Machines and cannot remember where is what and always need to know where it is located. Can you please place the full path back in the front page of the manager?

Complaint/Problem2: also on the front page of ""Oracle VM VirtualBox Manager"", they scrollbar is very annoying because I cannot see it and have a tough time to make it visible enable I can scroll up and down to see where is the Virtual Machine that I want to use. Can you please make the scroll bar always visible and therewith make my life easier as well as the lives of hundreds of thousands of others users?

I thank you for your understanding and I really hope you make these changes.

Should you require more information then please do not hesitate to contact me at M@Najar.eu.

Thank you and I wish you a very pleasant and most successful year 2020.

With my sincere regards,

Michael Najar
M@Najar.eu
0031-6-8442 6363
Erasmusplein 80
2532 RE The Hague",Najar
9812,VB v 4.1.4 Splitter Drag Handle Not Available,Mac OS X,other,VirtualBox 4.1.4,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
19338,Virtualbox randomly overwrote current state.,Windows,Linux,VirtualBox 6.0.4,2020-02-23T15:28:32Z,2020-02-23T15:28:32Z,"I have a 'working' snapshot on my CentOS vm only.
When I just closed the window, it asked whether to turn off, save the state, or restore.
As soon as I selected 'save the current state', it immediately overwrote the current state with the snapshot and I lost a lot (a LOT) of work and data.
Please fix this before other people lose information.",K.W.555
19324,"VM abort with error message, log has rtR3WinUnhandledXcptFilter",Windows,Windows,VirtualBox 6.1.2,2020-02-23T22:44:02Z,2020-02-23T22:44:02Z,"At seemingly random times, my VM aborts with an error dialog:

VirtualBoxVM.exe - Application Error : The instruction at 0x00007FFD9D2E8201 referenced memory at 0x0000000000000021. The memory could not be written.

Log shows that the VM had started recording audio (no idea why), then shortly after aborted.",Mark Cranness
18285,Cannot paste copied Chromium URL into Windows,Windows,Linux,VirtualBox 6.0.0,2020-02-24T09:48:32Z,2020-02-24T09:48:32Z,"If I copy the URL in Chromium's address bar on the Linux VM, I cannot paste it into any app on my Windows host. So far, all other uses of the bidirectional clipboard, either direction and with any application, works fine. Also, I can paste a copied Chromium URL into any other app on the same VM.

I have a Ubuntu 18.10 VM on VirtualBox 6.0 running on Windows 10 Pro x64 host. Running the release of Extension Pack that is for VirtalBox 6.0.0. In case it matters, I created this app on a 5.2 release of VirtualBox.

This seems like a VirtualBox bug because it only happens with a specific use of VirtualBox's bidirectional clipboard feature.",Aren Cambre
19341,VirtualBox 6.1.4 on Win 10 critical error on start,Windows,all,VirtualBox 6.1.4,2020-02-24T11:29:34Z,2020-02-24T11:29:34Z,"----------------------------------------------------------
Failed to acquire the VirtualBox COM object.

The application will now terminate.

Error in C:\Users\<username>\.VirtualBox\VirtualBox.xml (line 33) -- UUID &quot;{00000000-0000-0000-0000-000000000000}&quot; has zero format.

F:\tinderbox\win-rel\src\VBox\Main\src-server\VirtualBoxImpl.cpp[740] (long __cdecl VirtualBox::init(void)).

Result Code: E_FAIL (0x80004005)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}
--------------------------------------------------------------------
Not sure where the reference to the F:\drive is coming from since I have no F: drive. 

Also, Line 33 or the referenced XML file has no resemblance to the error message about UUID 0000... zero format, but instead reads 

""  <ExtraDataItem name=""HostOnly/{69874491-c60a-44dc-a52d-f9e8b3f35315}/Name"" value=""VirtualBox Host-Only Ethernet Adapter""/>
    </ExtraData>""

Cannot provide log in usual manner since UI won't run. ",tjod
19350,Radio box behavior on close window,Windows,Windows,VirtualBox 6.1.4,2020-02-25T21:44:38Z,2020-02-25T21:44:38Z,"Hi I have noticed a behavior in the UI which may not be intended. When the Close Virtual Machine window appears, double clicking on any of the radio buttons will cause that option to be accepted. Would it be safer to instead only accept with the OK button?",mike_coreit
19351,Ubunutu 18.04 kernel 5.4.0 suplibOsInit VERR_VM_DRIVER_NOT_INSTALLED ENOENT,Linux,Linux,VirtualBox 6.1.4,2020-02-26T21:29:56Z,2020-02-26T21:29:56Z,"Failure to start vm, error seems to be independend on the image
Bug is reproducible with 
'''host info'''
❯ uname --a  
Linux incbook 5.4.0-050400rc7-generic #201911102031 SMP Mon Nov 11 01:34:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

''secure boot disabled''

'''virtalbox install'''
https://www.virtualbox.org/wiki/Linux_Downloads
version for bionic, 
VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.9.5)

'''image independent'''
reproducible with latest dsl image from https://sourceforge.net/projects/virtualboximage/files/Damn Small/4.4.10/dsl-4.4.10-x86.7z/download?use_mirror=netcologne

'''Error message'''

Failed to open a session for the virtual machine dsl-4.4.10-x86.

The virtual machine 'dsl-4.4.10-x86' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}



Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

'''attempts to fix/reinstall don't help'''

❯ sudo /sbin/vboxconfig          
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

",rtychko
19353,Bad installiation on Windows XP 32 bits.,Windows,all,VirtualBox 5.2.38,2020-02-27T08:04:22Z,2020-02-27T08:04:22Z,"Hello. I had the installed version of Virtualbox 5.2.36 r135684. I tried installing update 5.2.38. It did not install, the program did not reach the end of the installation process. I don’t know if there were driver updates. Just in case, I inform you that there were no dialog boxes offering to install drivers. I saw only the green line of the installation indicator for a long time (more than an hour) and the button to stop the installation.",hellodearfriends
19354,Problems accessing lots of items with nvda screenreader in virtualbox,Windows,other,VirtualBox 6.1.4,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
12680,Unable to restore saved state after sleeping host,Windows,Windows,VirtualBox 4.3.6,2020-02-28T11:06:37Z,2020-02-28T11:06:37Z,"Windows 7 x64 host, Windows 7 x64 guest, VirtualBox 4.3.6 r91406

If I save the state of the guest, and then put the host PC to sleep, when I wake it back up and attempt to resume the guest, I get:

Failed to open a session for the virtual machine Win7.
Failed to load unit 'pgm'
(Verr_SSM_INTEGRITY_REC_TERM_CRC).

The details are:

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

If I shut down the host and reboot, I can then resume the guest from it's saved state.

This is repeatable every time.  I saw another ticket from months (years?) ago with the same issue; it's how I knew to reboot in order to be able to resume the saved state.",Kiran Otter
18420,'Solid State Disk' setting after snapshot not detected by Linux 4.15.0 guest,Linux,Linux,VirtualBox 5.2.26,2020-02-28T14:58:57Z,2020-02-28T14:58:57Z,"Same symptom as with https://www.virtualbox.org/ticket/12025 :
""Solid State Disk"" is checked in VBoxManage but the guest does not recognize that, and `cat /sys/block/sda/queue/rotational` in the guest gives ""0""

Host: Ubuntu 18.04;   Guest: Ubuntu 18.04 (kernel 4.15.0)

NOTE: ""Solid State Disk"" was checked only after taking a snapshot. There is only one snapshot.

Possibly relevant: VBox.log (attached) mentions both the snapshot and original vdi, and ""NonRotatingMedium"" is set for the snapshot.  Here's an extract:

[/Devices/ahci/0/LUN#0/Config/] (level 5)
   Mountable           <integer> = 0
   NonRotationalMedium <integer> = 1
   Path                <string>  = "".../Snapshots/{d5ad9312-a011-4939-b281-a71f223ae696}.vdi"" (cb=93)
   
 [/Devices/ahci/0/LUN#0/Config/Parent/] (level 6)
   Path   <string>  = "".../disk1.vdi"" (cb=64)


",Jim Avera
19362,VirtualBox crash on start ReactOS with BTRFS,Windows,other,VirtualBox 6.1.4,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
19007,VERR_PGM_HANDLER_NOT_FOUND,Linux,Windows,VirtualBox 6.0.12,2020-02-29T06:30:29Z,2020-02-29T06:30:29Z,"Running 4 VirtualBox (Version 6.0.12 r133076 (Qt5.6.1)) instances on Fedora host with 40Gb RAM.
2 Windows Server 2016 instances were doing updates.
Both crashed with VERR_PGM_HANDLER_NOT_FOUND",YoungJules
19344,VirtualBox 6.1.14 install fails on RedHat family,Linux,other,VirtualBox 6.1.4,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
19366,virtualbox does not work,other,Linux,VirtualBox 6.1.4,2020-03-01T12:59:02Z,2020-03-01T12:59:02Z,"OS: Astra Linux

The virtual machine '1' has terminated unexpectedly during startup with exit code 1 (0x1).

Код ошибки: NS_ERROR_FAILURE (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",Yuriy Davidenko
19200,"Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU",Windows,Windows,VirtualBox 6.1.0,2020-03-02T04:57:12Z,2020-03-02T04:57:12Z,"==============================================[[BR]]
Problem:

Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU.[[BR]]
Windows 8.1 Guest does not waste a full CPU core on the Host.[[BR]]

==============================================[[BR]]
VMs: [https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/][[BR]]

==============================================[[BR]]
Problem Behavior:[[BR]][[BR]]
Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> Guest used CPU non-stop for ~30 mins (mscorsvw, ngen, wsappx, Windows Update, Antimalware Service Executable)[[BR]]
-> Host showed VirtualBox.exe/VirtualBoxVM.exe using a full core non-stop[[BR]]
-> Even after ~30 mins, when Guest stopped using CPU, host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Guest - Went to Windows Update and clicked Restart, which updated to: v1809 Build 17763.379[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Repeated for another Windows Update, updating to v1809 Build 17763.914[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Tried Shutdown then Start -> Normal Start[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]

For all tests:[[BR]]
Paravirtualization Interface: Hyper-V[[BR]]

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)
",Jacob Klein
19295,"VM reset (""HeartbeatFlatlinedTimer"") under load",Linux,Linux,VirtualBox 6.0.16,2020-03-02T16:10:23Z,2020-03-02T16:10:23Z,"Since upgrading to 6.1.2, I'm seeing reboots during guest backup runs.

The guest is Linux 2.6.22.14-100 #1 SMP Wed Apr 8 18:07:54 EDT 2015 i686 i686 i386 GNU/Linux

Prior to the upgrade, this was never seen.

The backup is tar (some excludes) -czpf (NFS mountpoint) |tee (log) | grep -v (noise)

A full backup is about 75GB; the crashes generate between 3 and 40GB before the crash.

Log file attached.

The relevant log lines appear to be:

{{{
90:00:58.137957 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
90:01:56.653151 Reset initiated by keyboard controller
90:01:56.682588 Changing the VM state from 'RUNNING' to 'RESETTING'

}}}

Let me know if you need more info.

Is there a way to disable either the detection or the reset action until a fix is available?

I'd like to be able to complete a backup!

",Timothe Litt
19272,crashes very much when i right click in winscp,Linux,Windows,VirtualBox 6.1.2,2020-03-02T16:17:39Z,2020-03-02T16:17:39Z,"Peace, Host mint Mate 19.3, guest win 10 (1909) with high contrast theme
file:///home/zouhairy/VirtualBox%20VMs/Win/Logs/VBox.log
",majed17
19220,Edit Machine Settings - Error in UI,Windows,all,VirtualBox 6.1.0,2020-03-02T18:32:53Z,2020-03-02T18:32:53Z,"PROBLEM:

I've imported some VBoxes from an older PC.  It had a saved state at the time and I cleared it.
I still can not start because of the system acceleration message.  
Clearing the SYSTEM->ACCELERATION->Hardware Virtualization check box does not clear the message and I can not click ""OK"" at the bottom to save the change.


MESSGE: 

System: Acceleration page:
The hardware virtualization is enabled in the Acceleration section of the System page although it is not supported by the host system.  It should be disabled in order to start the virtual system.

",Gereral.2018
19372,a crash on resume machine,Linux,Windows,VirtualBox 6.1.4,2020-03-02T20:39:12Z,2020-03-02T20:39:12Z,"Video mode VBOXSvga dualscreen.[[BR]]
On resume machine i have error loading 'VGA' [[BR]]

link on complete log :[[BR]]

[http://s000.tinyupload.com/index.php?file_id=35541543786314765463]

I join log part.[[BR]]

Information i'am not used opengl application.[[BR]]


thank",Sizy458
18748,bsod after installing alcohol 52% and rebooting in windows xp sp3 guest,Windows,Windows,VirtualBox 5.2.30,2020-03-03T13:03:57Z,2020-03-03T13:03:57Z,"bsod after installing alcohol 52% and rebooting in windows xp sp3 guest
This problem seems to be in Virtualbox 6 also",nikitastepanov
19321,"VM crashes often on USB unplug/replug, also out of blue sky",Linux,Windows,VirtualBox 6.1.2,2020-03-03T13:35:46Z,2020-03-03T13:35:46Z,"Hi,
this looks like a regression in 6.1.2 and 6.0.16 since I cannot duplicate with 6.0.14.
The VM simply disappears from the screen. Sometimes with no visible reason, but every few USB unplug/replug cycles. I found the USB part since I write some code that communicates to a USB device (CDC-ACM aka ComPort emulation). One of the actions does cause the device to reboot (on purpose).

Other times it sits in the background and when I want to open the VM window again, it is gone. Then sometimes it crashes immediately at start or shortly after. A host reboot brings it back to work (until it crashes randomly again).
Host and guest are running with latest updates.
H: Ubuntu 18.04, 5.3.0-40-generic
G: Win10-64, 19H2 (but also showed at 19h1)

I have not seen a crash with Linux guests, but do not use them often right now.

In the logs I did not find useful hints, I hope you do. Let me know when I can help with debugging.

There is a thread in the forum:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=96829&p=470373#p470373]
",ucrasher2
11160,".ova image created with Virtual Box, failed to import in VMware",other,other,VirtualBox 4.2.4,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
19375,Crash bsod on guest machine,other,other,VirtualBox 6.1.4,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
5036,Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS) when running warcraft 1's setup,other,other,VirtualBox 6.0.12,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
17612,Unable to create RAWDISK vmdk which includes extended partition,Linux,other,VirtualBox 5.2.8,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
477,Hardware breakpoints don't work in Virtualbox (software virtualization only),other,other,VirtualBox 3.1.6,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
19376,[Win 7 64 Host] Sound not working in any VM,Windows,all,VirtualBox 6.1.4,2020-03-04T12:26:52Z,2020-03-04T12:26:52Z,"Hallo there, 

My sound works since some versions (i think 5.x it started) when my sound didnt worked anymore in any VM. Its only in the VMs! Host sound works in any situation.
In this post, i already covered most of my Problem. [https://forums.virtualbox.org/viewtopic.php?f=6&t=96994&p=471320#p471320]",helgo1506
19377,Add additional diagnostic information for the VERR_SUP_VP_THREAD_NOT_ALONE error,Windows,all,VirtualBox 6.1.4,2020-03-04T14:49:22Z,2020-03-04T14:49:22Z,"Would it be possible to add additional information to the hardening log when this happens, to make it easier for users to identify the application that is causing the conflict?

For example, when VirtualBox detects an extra thread running that shouldn't be there, can you print a stacktrace to the hardening log that includes the DLL names for the code that is currently executing in that other thread?",rwreed
19378,VirtualBox crashes with VMSVGA and 3D,Windows,Windows,VirtualBox 6.0.18,2020-03-04T20:30:47Z,2020-03-04T20:30:47Z,"I'm using '''Win10''' host with newly installed '''Ubuntu 20.00''' guest on. 
[[BR]]

After login open ''Brave'' browser, open some tabs and close it. It will crash in 90% of cases. It also occurs with ''Chrome'' browser, but less often and predictable. They are both based on ''Chromium/V8''.
[[BR]]

Crash happens only with the new '''VMSVGA''' driver and enabled '''3D acceleration'''.
[[BR]]

I was having issues also with 6.1.2 and 6.1.4 builds, but have downgraded because 3D is not supported in VBoxSVGA mode. 
[[BR]]",mihaur
19379,Ubuntu 18.04 guest Vbox 6.1.4 crash on macOS 10.14.6 / MacBook Pro 15'' 2018 host,Mac OS X,Linux,VirtualBox 6.1.4,2020-03-04T22:28:35Z,2020-03-04T22:28:35Z,I've got a crash of a Vbox 6.1.4 while rebooting an Ubuntu 18.04 guest after a system update. See attached log files,Lars Sonchocky-Helldorf
12279,Memory leak: VBoxService.exe slowly eats up RAM,Linux,Windows,VirtualBox 4.3.0,2020-03-05T12:48:08Z,2020-03-05T12:48:08Z,"version 4.3
host: Ubuntu 10.04 x64
guest: windows xp sp3 with VB addition ver 4.3, running in headless

the VBoxService.exe  starts leaking memory once the VM is login through remote desktop (mstsc, not vrdp). If the VM is not running in headless mode, no leaking.

the fixed in https://www.virtualbox.org/ticket/12072 seems not working here
this ticket is  https://www.virtualbox.org/ticket/10970 , however, seems yet to be fixed.



",maxchen
19382,Multiple Virtual Screen closes when changing a display,Windows,Linux,VirtualBox 6.1.2,2020-03-06T17:06:26Z,2020-03-06T17:06:26Z,"I'm running Fedora 31 on Windows 10 with three monitors.
1. Dell XPS 15 (3840x2160 at 250% scaling which is recommended on Windows)
2. Dell Monitor (1920x1200 at 100% scaling)
3. Dell Monitor (1920x1200 at 100% scaling)
#2 and #3 are connected to XPS 15 via usb hub and daisy chained between #2 and #3.

These monitors are layout from left in above order.

I'm running the Fedora 31 using #2 and #3 monitors (so two virtual screens).

When I turn on the Auto-resize Guest Display option the second virtual screen crashes in a few operations.

Issue #1: When I drag and drop the second virtual screen window around above three monitors.  When I start the vm, the second virtual screen window appears in the monitor #1 (Dell XPS 15) and the first virtual screen windows appears in the monitor #2 (that is because I previously started in it).  I drag and drop the second virtual screen window to the monitor #3.  Then, the window blinks and planed in the monitor #1 and the windows is all grayed out.  Sometimes the window closes.  The first virtual screen window remains functional.

I can turn off the Auto-resize Guest Display options, and above issue does not happen.  After moving the second virtual screen window, I can turn on the option and use screens in the full screen mode.

Issue #2: After getting two virtual screens in the monitor #2 and #3 in the full screen mode.  The second virtual screen window closes if I getting out of the full screen mode.

There is the way around so not blocking issue, but this problem is annoying.",Takahiro
19383,List virtual machines in specific group,all,all,VirtualBox 6.1.4,2020-03-06T20:09:16Z,2020-03-06T20:09:16Z,"Please, implement command line option to list VMs from specific group.

Something like this:
VBoxManage list [--long|-l] [--sorted|-s] vms --group ""my_vm_group""",1ns
19384,Get/set clipboard content for guest OS,all,all,VirtualBox 6.1.4,2020-03-06T20:16:48Z,2020-03-06T20:16:48Z,"Please, implement command to get/set guest clipboard without using shared clipboard.

Something like:
VBoxManage guestcontrol <uuid|vmname> getclipboard
VBoxManage guestcontrol <uuid|vmname> setclipboard ""some text to set as clipboard""

",1ns
18115,VBoxSVC segfault when ending Windows guest,Linux,Windows,VirtualBox 5.2.20,2020-03-08T20:03:39Z,2020-03-08T20:03:39Z,"When cleanly shutting down Windows guests (on a CentOS Host), which were started with:
 VBoxManage startvm MACHINENAME -type vrdp

I see afterwards in the Linux syslog this kind of crash:
 VBoxSVC[5805]: segfault at 0 ip           (null) sp 00007ffc9097f068 error 14 in VBoxSVC[400000+4de000]

The crash is reproducible, and has been there since a long time (all of 5.2.x VirtualBox versions).",Helge Deller
19387,Install of VirtualBox 6.1.4 crashes Sudoers on Ubuntu 18.4.4,Linux,other,VirtualBox 6.1.4,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
19388,crashes during win updates,Mac OS X,other,VirtualBox 6.1.4,2020-03-09T14:09:13Z,2020-03-09T14:09:13Z,VB crashed during 1909 install as well as 1909 update,andyknas
19389,win 7 problemes,Windows,other,VirtualBox 6.1.4,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
19390,Unable to restart VM after loading it from a saved state,Windows,all,VirtualBox 6.1.4,2020-03-09T19:53:06Z,2020-03-09T19:53:06Z,"This is occurring on multiple systems. Windows 7 & 10 hosts, Windows 7,8,10 & Linux guests

'''Recreation:'''
1) Boot up a Windows 7, Windows 8, Windows 10, or Linux VM.
2) Once loaded to the desktop, close the VM with the ""Save machine state"" option.
3) Start up the VM from the saved state.
4) Restart the VM. (ex: Start -> Power -> Restart)

 '''Problem:''' Soon after the VM begins to reload, a Guru Meditation error results. 
Log files are attached. The last recorded error is VERR_PGM_HANDLER_NOT_FOUND.

Point of interest: For Windows guests, a Windows Vista style boot screen (black w/ just a bar) is shown, instead of the usual Windows logo. So ''something'' is set a couple of seconds prior to the failure that is causing it.",JMH1
19393,Virtualbox Linux Guest crashes when opening Eclipse IDE,Windows,Linux,VirtualBox 6.1.4,2020-03-11T08:18:17Z,2020-03-11T08:18:17Z,"Hi,

if I open the Eclipse IDE under my Linux guest, then the guest crashes.

The guest is ArchLinux 64bit and the host Windows 10. I use the official Virtualbox guest extensions and kernel modules. The Linux Kernel of the guest is 5.5.8

I will attach the Logfiles",JMeier12
19394,"After anydesk disconnects, mouse use is corrupted",Linux,Windows,VirtualBox 6.1.4,2020-03-11T17:24:23Z,2020-03-11T17:24:23Z,"On Ubuntu20 using vbox 6.21.4.r136177, running a win10 box, when an AnyDesk user is controlling the box, while they are using it and after they disconnect, the local user of the win10box can't properly use the mouse or enter informaiton via keyboard.  Unable to highlight test or enter information.  Should be able to highlight and enter information.",phelix
19396,Latest version (6.0.18) causes issues with DNS and VPN,Windows,Windows,VirtualBox 6.0.18,2020-03-12T12:55:44Z,2020-03-12T12:55:44Z,"After I upgraded from 6.0.16 to 6.0.18 I started having network issues. After some futzing around and help from a friend I found a work around that forced me to be doing ipconfig /renew after connecting or disconnecting from our company's VPN. Just this morning I went back to 6.0.16 and the problem is gone which pretty much proves the latest version has broken something.

My host is Win 10 and my guest is Win 7.",WayneB64
19352,Guru Meditation when using more than 1 CPU + EFI (VINF_EM_TRIPLE_FAULT),Windows,Windows,VirtualBox 6.1.4,2020-03-13T17:35:01Z,2020-03-13T17:35:01Z,"When I use EFI + CPU greater than 1 the client crashes with Guru Meditation (VINF_EM_TRIPLE_FAULT). From version 6.1.0 the issue starts to occur and is still present in version 6.1.4. In version 6.0.18- the error didnt't occur once. 

'''I made a lot of tests so I claim the trigger for this error is EFI enabled + vCPU > 1.'''

This is also discussed in forum where I attached log files directly after crash in version 6.1.0. Do you need log files for 6.0.18 (latest working version) and 6.1.4 (latest failing version)?

https://forums.virtualbox.org/viewtopic.php?f=6&t=96937",Tommy Parker
19028,Bad 3D display in Virtualbox 6.0.14,Linux,all,VirtualBox 6.0.14,2020-03-13T23:21:36Z,2020-03-13T23:21:36Z,"I have a terrible 3D display in some of my VMs on my Ryzen 3 2200G with Host Ubuntu 19.10/Linux 5.3.0-18 using Virtualbox 6.0.14. I did not have those problems with Ubuntu 19.04/Linux 5.0 and Virtualbox 6.0.12.
- Windows 7, half the time the screen is unreadable after booting, the screen is black with say 2"" of horizontal display of a part of the screen.
- Ubuntu 16.04, the top bar and unity dock are completely garbled.
- Ubuntu 19.10, the wall paper is covered by a strange pattern of blocks. 
All other VM are correct, Xubuntu 18.04, Windows XP, Ubuntu Mate 19.04, Xubuntu 19.10, Ubuntu Mate 19.10, Linux Mint, Peppermint and Windows 10.

Currently I had to switch of the 3D acceleration for those 3 VMs.",BertiN45
19399,Guest Locks Up Then Crashes,Mac OS X,Windows,VirtualBox 6.1.4,2020-03-14T00:04:08Z,2020-03-14T00:04:08Z,"Fresh install of windows 10 x64. All updates installed.

Using Virtualbox 6.1.4 on macos 10.15.3

Installed java 8u241, oracle version.

After opening java control panel, VM locks up. After a bit it crashes. OS reports it as EXC_BAD_ACCESS",rj45
19400,VM Locks Up When Running x64dbg,Mac OS X,Windows,VirtualBox 6.1.4,2020-03-14T00:13:21Z,2020-03-14T00:13:21Z,"If one runs x64dbg https://github.com/x64dbg/x64dbg in a windows 10 VM and opens any PE executable to debug, after stepping through a few instructions the VM locks up.

virtualbox 6.1.4 and macos 10.15.3 and most recent x64dbg from the github releases.",rj45
19401,Virtualbox host Windows 10 - CRASH,other,other,VirtualBox 6.1.4,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
19402,GuruMeditation in a simple hobby operating system,other,other,VirtualBox 6.1.0,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
19403,Why??? if i deactivated why can't i save ???,other,other,VirtualBox 6.1.4,2020-03-15T06:58:32Z,2020-03-15T06:58:32Z,https://imgur.com/d7BYRWu,Fe-lipelinux
19409,Windows 98: Arbitrary corruption of files in guest OS,Windows,Windows,VirtualBox 5.2.38,2020-03-17T00:01:31Z,2020-03-17T00:01:31Z,"1. Create a VM for Win98 and install Windows 98SE there.
2. Inside this VM, install Total Commander 9.51rc3 (the exact version is important!).
3. Make a backup copy of the TC installation folder.
4. Start TC, then exit it (if you're lucky enough that it does not crash).
5. Compare the TOTALCMD.EXE file contents with the one from the backup copy (for example, you can have another version of TC installed into another directory; there is a built-in function for comparing files).

Result: The file contents is different from what it was initially.

Expected result: The file should not change, because Total Commander does not modify its own executable. This was confirmed by the author of TotalCmd, but just in case I also monitored the situation with Sysinternals FileMon. During the whole period from launching Total Commander to its exit, FileMon showed absolutely NONE write operations to the totalcmd.exe file by any process in the system. And still, the file ended up being modified.

The corruption always happens on cluster-level; that is, the changes always consist of one or more cluster-sized chunks (4096 bytes on my guest file system). The exact position and contents of the corrupted data may vary in different experiments.

The issue can be reproduced in VirtualBox 5.2.36 and 5.2.38. With 5.2.34 I could not reproduce it. For some reason, I could reproduce this issue only with that particular version of Total Commander; neither rc2 nor rc4 seem to trigger the corruption scenario. If the version 9.51rc3 is no longer available at the official web site at some later time, it can still be downloaded from here: http://totalcmd.net/beta/tc951x32_rc3.exe (the authenticity can be validated by the digital signature).

I understand that Win98 is completely outdated, but it's a really serious bug causing data loss! And since I don't know what causes it, I cannot be sure if it does not affect any other guest OS.

I've looked at the log files, but they contain nothing at all at the moment of the experiment. Just in case, I'll attach the log file, but you can see it's empty between 13.5 seconds (when the OS started) and 26-something minutes, when I shut down the guest OS after performing the experiments.",Konstantin Vlasov
19410,"Remove, and delete files of the VMs will close the Virtualbox",Windows,Windows,VirtualBox 6.1.4,2020-03-17T10:57:18Z,2020-03-17T10:57:18Z,"I just upgraded the application to 6.1.4.r136177(Qt5.6.2), the first thing I did to remove old VMs which was migrated from the old version.

I have around 7 VMs and deleted them one by one and to be specific , the problem occurred only when I removed and deleted files of Linux OS.

attached is the Event viewer event.",Mahmood.Shehab
19412,Verr_io_gen_failure in Windows XP Pro and Win 7 Pro,Windows,Windows,VirtualBox 6.1.4,2020-03-17T13:50:20Z,2020-03-17T13:50:20Z,"Hello,

i get this Verr_io_gen_failure when i connect a Telenot comXline 3516-1 to the usb port. This happened in Windows XP Pro and Windows 7 Pro.
I see no possiibility to connect the Telenot to the guest systems.

I tried all i can, the usb filter is set right. I tried different settings in the filter.

The usb filter generally works perfect, exept the Telenot conection :(",alsk1
19413,Silent fail of inotify_add_watch,Linux,all,VirtualBox 6.1.4,2020-03-18T10:13:21Z,2020-03-18T10:13:21Z,"To watch new USB devices, ''VBoxSVC'' use ''inotify_add_watch'' on ''/dev/vboxusb''. If ''inotify_add_watch'' fails, USB redirection will silently fail (no log nor warnings).

''inotify_add_watch'' may fail if the limit of watches is already reached. The limit is quite low on a default stable debian install (8192) and several modern text editors use a lot of watches to... watch directories and subdirectories.

Step to reproduce the problem:
1] make sure that VBoxSVC isn't running
2] check that the limit is not too high ''cat /proc/sys/fs/inotify/max_user_watches'', if it is, just temporarily decrease it: ''echo 1000 | sudo tee /proc/sys/fs/inotify/max_user_watches''
3] drain all the watches (for example by executing ''inotifywatch -r'' on a folder with a lot of subfolders.
4] run ''VBoxSVC'', you may ''strace'' it to make sure that ''inotify_add_watch'' fails
5] run ''VBoxManage list usbhost''
6] observe that ''inotify_add_watch'' fails in ''VBoxSVC'' and that ''VBoxManage list usbhost'' returns nothing.
7] [optionnal] use this script to check who's using all the watches: https://raw.githubusercontent.com/fatso83/dotfiles/master/utils/scripts/inotify-consumers

''VBoxSVC'' should return an error that ''VBoxManage list usbhost'' and VirtualBox gui client could display to easily diagnose the problem and maybe hint on a solution (kill the process using all the watches or increase the limit).

There may be other use of ''inotify_add_watch'' in the VBox codebase and there may be other code path to check (for example, there is also a restriction on the number of inotify **instances**, cf. ''/proc/sys/fs/inotify/max_user_instances'', that may cause ''inotify_init'' to fail). ",elvanderb
18866,XNA Framework 4.0 unsupported by Windows XP Guest on Linux Host,Linux,Windows,VirtualBox 6.0.10,2020-03-18T17:14:22Z,2020-03-18T17:14:22Z,"I was hoping that Vbox 6 would work with this. I knew that older versions of Vbox did not support it. I have been using VMware Player 12.1 for several years to achieve my requirement but that application is now too difficult for me to maintain through kernel changes and later versions of ""Player"" are no good to me for other reasons. So I went back to the latest VirtualBox and tried a couple of the graphics adapter settings and I have the Guest additions correctly installed etc.

The VM otherwise works fine and I can run ""dxdiag"" and see the spinning cube on the 3D tests so I know DirectX is working (well 8 & 9 are anyway - doesn't like 7). The ""repair"" option of the XNA installation program appears to work OK (installs DirectX 9.0c components) but the application wanting to use XNA will not start (it reports XNA is not fully supported).

The annoying thing is that the application I want to run is not a game and doesn't really need XNA for what it does but the program writers chose to use it anyway :-(

Can anyone help?",Spiralgalaxy
19415,Gust Additions fails to install correctly on Windows 10 when Graphics Controller set to null,Linux,Windows,VirtualBox 6.1.4,2020-03-19T07:19:41Z,2020-03-19T07:19:41Z,"If you
 - disable the graphics controller (by setting it to null)
 - install the Guest Additions on Windows 10 Guest
It will
 - look like it finished
   - the untrained eye will not notice
     - gives an error message about missing hardware in the detailed output
After install
 - the tray icon will be there
   - making you think it worked
 - most (if not all) features enabled by guest additions will not work",Cameron Tacklind
19416,random file system corrruption on Windows 10,Windows,Linux,VirtualBox 6.1.4,2020-03-20T16:15:32Z,2020-03-20T16:15:32Z,"My system info:



{{{
Host Name:                 PENTIUM
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          vagiz
Registered Organization:
Product ID:                00330-80000-00000-AA650
Original Install Date:     2/29/2020, 8:24:00 AM
System Boot Time:          3/19/2020, 1:14:52 AM
System Manufacturer:       Micro-Star International Co., Ltd.
System Model:              MS-7B98
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~3696 Mhz
BIOS Version:              American Megatrends Inc. 1.80, 12/25/2019
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume5
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     16,248 MB
Available Physical Memory: 5,630 MB
Virtual Memory: Max Size:  16,248 MB
Virtual Memory: Available: 1,731 MB
Virtual Memory: In Use:    14,517 MB
Page File Location(s):     N/A
Domain:                    WORKGROUP
Logon Server:              \\PENTIUM
Hotfix(s):                 8 Hotfix(s) Installed.
                           [01]: KB4534132
                           [02]: KB4497727
                           [03]: KB4500109
                           [04]: KB4503308
                           [05]: KB4537759
                           [06]: KB4538674
                           [07]: KB4541338
                           [08]: KB4551762
Network Card(s):           3 NIC(s) Installed.
                           [01]: Intel(R) Ethernet Connection (7) I219-V
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.30
                                 [02]: fe80::2525:f387:2d51:482c
                                 [03]: fdaa:bbcc:ddee:0:d549:d972:f087:7aea
                                 [04]: fdaa:bbcc:ddee:0:98a1:602:e24a:c661
                                 [05]: fdaa:bbcc:ddee:0:2525:f387:2d51:482c
                           [02]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::c0ff:26ea:bebe:8ea6
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.18.26.193
                                 [02]: fe80::1819:a7d9:5836:496b

}}}
Vagrant file:

{{{
Vagrant.configure(""2"") do |config|
  # The most common configuration options
  # https://docs.vagrantup.com.

  # boxes at https://vagrantcloud.com/search.
  # https://app.vagrantup.com/bento
  config.vm.box = ""bento/centos-7""

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  config.vm.network :forwarded_port, guest: 22, host: 12022
  config.vm.network :forwarded_port, guest: 12080, host: 12080
  config.vm.network :forwarded_port, guest: 12443, host: 12443
  #config.vm.synced_folder ""."", ""/vagrant"", :mount_options => [""dmode=777"",""fmode=666""]
  config.ssh.username = 'vagrant'
  config.ssh.password = 'vagrant'
  config.ssh.insert_key = false
  config.vm.provider ""virtualbox"" do |vb|
        vb.memory = ""1600""
        vb.cpus = ""2""
        end
end
}}}

Random file corruption, e.g. wget https://files.phpmyadmin.net/phpMyAdmin/4.9.4/phpMyAdmin-4.9.4-english.tar.gz

I have tried Hyper-V on/off multiple times with different disks: SSD, NVMe, SATA and disable/enable windows/Vagrant caching.
sometimes cannot even boot from the beginning (system displays emergency mode). tried to reinstall VirtualBox multiple times, use different install image version. nothing changed, random corruption especially with heavy write.

as an example, internal MariaDB output when importing:

{{{
Mar 20 14:22:37 localhost systemd: Starting MariaDB 10.4.12 database server...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] /usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 8606 ...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using Linux native AIO
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Uses event mutexes
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Number of pools: 1
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Completed initialization of buffer pool
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Waiting for purge to start
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 10.4.12 started; log sequence number 60496037333; transaction id 79440
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] Plugin 'FEEDBACK' is disabled.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] 'proxies_priv' entry '@% root@localhost.localdomain' ignored in --skip-name-resolve mode.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] InnoDB: Buffer pool(s) load completed at 200320 14:22:41
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Reading of all Master_info entries succeeded
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Added new Master_info '' to hash table
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=localhost-relay-bin' to avoid this problem.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] /usr/sbin/mysqld: ready for connections.
Mar 20 14:22:41 localhost mysqld: Version: '10.4.12-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 0  MariaDB Server
Mar 20 14:22:41 localhost systemd: Started MariaDB 10.4.12 database server.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=256128, page number=2147483648], should be [page id: space=1511, page number=3530]
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace hpci/articles page [page id: space=1511, page number=3530]. You may have to recover from a backup.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
Mar 20 14:46:44 localhost mysqld: len 16384; hex 00000000800000000000000000003c000000a2998f692000998f692efb00000137000003e8800102000258003780000000003420a6000000000000800000000000000000003c000000a3998f693000998f693efb00000137000003e8800102000260003780000000003420a7000000000000800000000000000000003c000000a4998f694000998f694efb00000137000003e8800102040268003780000000003420a8000000000000800000000000000000003c000000a5998f695000998f695efb00000137000003e8800102000270003780000000003420a9000000000000800000000000000000003c000000a6998f696000998f696efb00000137000003e8800102000278003780000000003420aa000000000000800000000000000000003c000000a7998f697000998f697efb00000137000003e8800102000280003780000000003420ab000000000000800000000000000000003c00000000998f6a0000998f6a0efb00000137000003e8800102040288003780000000003420ac000000000000800000000000000000003c00000001998f6a1000998f6a1efb00000137000003e8800102000290003780000000003420ad000000000000800000000000000000003c00000002998f6a2000998f6a2efb00000137000003e8800102000298003780000000003420ae000000000000800000000000000000003c00000003998f6a3000998f6a3efb00000137000003e88001020002a0003780000000003420af000000000000800000000000000000003c00000004998f6a4000998f6a4efb00000137000003e88001020402a8003780000000003420b0000000000000800000000000000000003c00000005998f6a5000998f6a5efb00000137000003e88001020002b0003780000000003420b1000000000000800000000000000000003c00000006998f6a6000998f6a6efb00000137000003e88001020002b8003780000000003420b2000000000000800000000000000000003c00000007998f6a7000998f6a7efb00000137000003e88001020002c0003780000000003420b3000000000000800000000000000000003c00000008998f6a8000998f6a8efb00000137000003e88001020402c8003780000000003420b4000000000000800000000000000000003c00000009998f6a9000998f6a9efb00000137000003e88001020002d0003780000000003420b5000000000000800000000000000000003c0000000a998f6aa000998f6aaefb00000137000003e88001020002d8003780000000003420b6000000000000800000000000000000003c0000000b998f6ab000998f6abefb00000137000003e88001020002e0003780000000003420b7000000000000800000000000000000003c0000000c998f6ac000998f6acefb00000137000003e88001020402e8003780000000003420b8000000000000800000000000000000003c0000000d998f6ad000998f6adefb00000137000003e88001020002f0003780000000003420b9000000000000800000000000000000003c0000000e998f6ae000998f6aeefb00000137000003e88001020002f8003780000000003420ba000000000000800000000000000000003c0000000f998f6af000998f6afefb00000137000003e8800102000300003780000000003420bb000000000000800000000000000000003c00000010998f6b0000998f6b0efb00000137000003e8800102040308003780000000003420bc000000000000800000000000000000003c00000011998f6b1000998f6b1efb00000137000003e8800102000310003780000000003420bd000000000000800000000000000000003c00000012998f6b2000998f6b2efb00000137000003e8800102000318003780000000003420be000000000000800000000000000000003c00000013998f6b3000998f6b3efb00000137000003e8800102000320003780000000003420bf000000000000800000000000000000003c00000014998f6b4000998f6b4efb00000137000003e8800102040328003780000000003420c0000000000000800000000000000000003c00000015998f6b5000998f6b5efb00000137000003e8800102000330003780000000003420c1000000000000800000000000000000003c00000016998f6b6000998f6b6efb00000137000003e8800102000338003780000000003420c2000000000000800000000000000000003c00000017998f6b7000998f6b7efb00000137000003e8800102000340003780000000003420c3000000000000800000000000000000003c00000018998f6c0000998f6c0efb00000137000003e8800102040348003780000000003420c4000000000000800000000000000000003c00000019998f6c1000998f6c1efb00000137000003e8800102000350003780000000003420c5000000000000800000000000000000003c0000001a998f6c2000998f6c2efb00000137000003e8800102000358003780000000003420c6000000000000800000000000000000003c0000001b998f6c3000998f6c3efb00000137000003e8800102000360003780000000003420c7000000000000800000000000000000003c0000001c998f6c4000998f6c4efb00000137000003e8800102040368003780000000003420c8000000000000800000000000000000003c0000001d998f6c5000998f6c5efb00000137000003e8800102000370003780000000003420c9000000000000800000000000000000003c0000001e998f6c6000998f6c6efb00000137000003e8800102000378003780000000003420ca000000000000800000000000000000003c0000001f998f6c7000998f6c7efb00000137000003e8800102000380003780000000003420cb000000000000800000000000000000003c00000020998f6c8000998f6c8efb00000137000003e8800102040388003780000000003420cc000000000000800000000000000000003c00000021998f6c9000998f6c9efb00000137000003e8800102000390003780000000003420cd000000000000800000000000000000003c00000022998f6ca000998f6caefb00000137000003e8800102000398003780000000003420ce000000000000800000000000000000003c00000081998f669000998f669efb00000138000003e88001020003a0003780000000003420cf000000000000800000000000000000003c00000082998f66a000998f66aefb00000138000003e88001020403a8003780000000003420d0000000000000800000000000000000003c00000083998f66b000998f66befb00000138000003e88001020003b0003780000000003420d1000000000000800000000000000000003c00000084998f66c000998f66cefb00000138000003e88001020003b8003780000000003420d2000000000000800000000000000000003c00000085998f66d000998f66defb00000138000003e88001020003c0003780000000003420d3000000000000800000000000000000003c00000086998f66e000998f66eefb00000138000003e88001020403c8003780000000003420d4000000000000800000000000000000003c00000087998f66f000998f66fefb00000138000003e88001020003d0003780000000003420d5000000000000800000000000000000003c00000088998f670000998f670efb00000138000003e88001020003d8003780000000003420d6000000000000800000000000000000003c00000089998f671000998f671efb00000138000003e88001020003e0003780000000003420d7000000000000800000000000000000003c0000008a998f672000998f672efb00000138000003e88001020403e8003780000000003420d8000000000000800000000000000000003c0000008b998f673000998f673efb00000138000003e88001020003f0003780000000003420d9000000000000800000000000000000003c0000008c998f674000998f674efb00000138000003e88001020003f8003780000000003420da000000000000800000000000000000003c0000008d998f675000998f675efb00000138000003e8800102000400003780000000003420db000000000000800000000000000000003c0000008e998f676000998f676efb00000138000003e8800102040408003780000000003420dc000000000000800000000000000000003c0000008f998f677000998f677efb00000138000003e8800102000410003780000000003420dd000000000000800000000000000000003c00000090998f680000998f680efb00000138000003e8800102000418003780000000003420de000000000000800000000000000000003c00000091998f681000998f681efb00000138000003e8800102000420003780000000003420df000000000000800000000000000000003c00000092998f682000998f682efb00000138000003e8800102040428003780000000003420e0000000000000800000000000000000003c00000093998f683000998f683efb00000138000003e8800102000430003780000000003420e1000000000000800000000000000000003c00000094998f684000998f684efb00000138000003e8800102000438003780000000003420e2000000000000800000000000000000003c00000095998f685000998f685efb00000138000003e8800102000440003780000000003420e3000000000000800000000000000000003c00000096998f686000998f686efb00000138000003e8800102040448003780000000003420e4000000000000800000000000000000003c00000097998f687000998f687efb00000138000003e8800102000450003780000000003420e5000000000000800000000000000000003c00000098998f688000998f688efb00000138000003e8800102000458003780000000003420e6000000000000800000000000000000003c00000099998f689000998f689efb00000138000003e8800102000460003780000000003420e7000000000000800000000000000000003c0000009a998f68a000998f68aefb00000138000003e8800102040468003780000000003420e8000000000000800000000000000000003c0000009b998f68b000998f68befb00000138000003e8800102000470003780000000003420e9000000000000800000000000000000003c0000009c998f68c000998f68cefb00000138000003e8800102000478003780000000003420ea000000000000800000000000000000003c0000009d998f68d000998f68defb00000138000003e8800102000480003780000000003420eb000000000000800000000000000000003c0000009e998f68e000998f68eefb00000138000003e8800102040488003780000000003420ec000000000000800000000000000000003c0000009f998f68f000998f68fefb00000138000003e8800102000490003780000000003420ed000000000000800000000000000000003c000000a0998f690000998f690efb00000138000003e8800102000498003780000000003420ee000000000000800000000000000000003c000000a1998f691000998f691efb00000138000003e88001020004a0003780000000003420ef000000000000800000000000000000003c000000a2998f692000998f6974732061637469766573206120677265656e206c6561662067726164652061732077656c6c20617320696e6469636174696e67207768696368206172652045636f6365727420617070726f7665642c20776869636820617265207072657365727661746976652d6672656520616e64207768696368207061726162656e2d667265652e203c2f703e3c703e43726f64612068617320616c736f20676f6e6520646f776e2074686520677265656e20726f7574652c206c61756e6368696e6720557020436c6f736520616e6420477265656e2c2061206e657720677265656e20677569646520746f20697473207370656369616c69747920726177206d6174657269616c732e2054686520677569646520656e61626c657320666f726d756c61746f727320746f2064657465726d696e6520686f7720677265656e20612070726f647563742069732c2077697468207265666572656e636520746f206f726967696e2028706c616e742c20616e696d616c206f72206d696e6572616c292c20706574726f6368656d6963616c732c2073696c69636f6e65732c207072657365727661746976657320616e642062696f6465677261646162696c69747920616d6f6e677374206f74686572732e2054686520677569646520616c736f206665617475726573206120477265656e2043726974657269612074686174206d61726b7320612064656c69626572617465206d6f766520617761792066726f6d207468652063757272656e742063657274696669636174696f6e207374616e646172647320617661696c61626c652e20556e6465722074686520637269746572696120616c6c2070726f647563747320696e20746865206775696465206172652066726565206f6620657468796c656e65206f7869646520616e642070726f70796c656e65206f786964652d626173656420636f6d706f6e656e74732c20636f6e7461696e206e6f20706574726f6c65756d2064697374696c6c617465732c206e6f2070687468616c617465732c206e6f207061726162656e732c206e6f20666f726d616c6465687964652d72656c656173696e67207072657365727661746976657320616e642068617665206e6f74206265656e20746573746564206f6e20616e696d616c732e3c2f703e3c703ee2809c54686572652061726520736f206d616e792064697363726570616e63696573206265747765656e20656163682063657274696669657220746861742077652068617665206c65667420746865206f7074696f6e206f66207768696368207374616e6461726420746f20666f6c6c6f7720746f206f757220637573746f6d6572732ce2809d206578706c61696e6564205361726168204d696c6c6e732c206d61726b6574696e6720636f6d6d756e69636174696f6e7320636f6f7264696e61746f722c20706572736f6e616c2026206865616c746820636172652c2043726f64612e20e2809c57652061726520616c736f2077616974696e6720666f7220746865204575726f7065616e2063657274696669636174696f6e207374616e6461726420746f206c61756e63682c207768696368206d6179206368616e676520736f6d652063726974657269612ee2809d3c2f703e3c703e466f6c6c6f77696e6720746869732073656e74696d656e742c2074686520636f6d70616e792068617320646576656c6f7065642074776f206e65772073756e20636172652070726f64756374732c20536f6c617665696c2043542d33303020616e6420536f6c617669656c20435a2d3330302c20616e642074776f20687964726174696e672070657074696465732066726f6d206f7267616e696320736f75726365732e20487964726f6176656e612048704f20616e6420487964726f657863656c73612048704f20617265206d6f69737475726973696e67206167656e747320646572697665642062792067656e746c6520656e7a796d6174696320687964726f6c79736973206f6620636572746966696564206f7267616e69632063726f70732e3c2f703e3c703e53796d72697365206861732062726f6164656e656420697473206f7267616e696320706f7274666f6c696f2c20616464696e67206e65772070726f647563747320746f20697473204578747261706f6e65204f7267616e69632072616e67652c207768696368206973206261736564206f6e20636f6e74726f6c6c65642068617276657374696e672e204e65772070726f647563747320696e636c756465204e656f2041637469706f6e6520536f6170204e75747368656c6c2c20612031303025206e61747572616c2073757266616374616e74207375697461626c6520666f722075736520696e20706572736f6e616c2063617265206170706c69636174696f6e732073756368206173207368616d706f6f7320616e6420626f6479207761736865732e3c2f703e3c703ee2809c426f74616e6963616c73206172652070726f76656e20696e2073637265656e696e67206d6574686f647320746f20686176652072656c6576616e742065666665637473207375636820617320616e74692d6972726974616e7420616e6420616e74696f786964616e7420666f7220636f736d65746963206170706c69636174696f6e732ce2809d204d69636861656c205363687572696368742c20726567696f6e616c20627573696e657373206d616e616765722c2053796d726973652c20746f6c64205350432e3c2f703e3c703e54686520636f6d70616e792068617320616c736f2072656e616d65642069747320636f736d657469637320627573696e65737320756e69742c2077686963682077696c6c206e6f77206265206b6e6f776e206173204c69666520457373656e7469616c732c20627574206973207374696c6c20612070617274206f662053796d72697365e2809973205363656e7420262043617265206469766973696f6e2e3c2f703e3c703e53696c61622068617320616c736f20656e746572656420746865206f7267616e6963206172656e612c206c61756e6368696e672061206e65772045636f6365727420636572746966696564206f7267616e69632072616e67652c2077686963682077696c6c20696e697469616c6c7920636f6d7072697365207468726565206163746976652070726f6475637473202d204f73696c6966742042696f2c205374727563747572696e652042696f20616e6420566974616e6f6c2042696f2e20203c2f703e3c703e416e64204c69706f20686173206c61756e636865642061206e6577206c696e65206f66206e61747572616c20656d6f6c6c69656e74732c20646572697665642066726f6d2031303025206e61747572616c20706c616e7420736f75726365732e20546865204c69706f6275747465722072616e676520636f6d707269736573203131207661726965746965732c206569676874206f66207768696368206172652076616c6964617465642062792045636f636572742c207768696c652074686520726566696e6564206f7267616e696320736865612076617269616e7420697320636572746966696564206f7267616e69632062792045636f636572742e2056617269657469657320696e636c7564652061707269636f742c20726566696e656420636f636f612c206f6c6976652c206a6f6a6f62612c20726566696e6564206d616e676f20616e6420706561636820616e64206170706c69636174696f6e2073756767657374696f6e7320696e636c75646520736b696e2c2073756e20616e64206861697220636172652070726f64756374732c2066696e6520736f61707320616e6420626f647920627574746572732e3c2f703e3c2f703e3c703e5a656e6974656368e2809973206e6577204d6561646f77666f616d20616e64204f72616e6765206275747465727320616c736f20676976652061206e6f6420746f206e61747572616c2c20776974682045636f636572742076616c69646174696f6e2e205468652070726f647563747320617265207361696420746f206265207375697461626c6520666f7220612076617269657479206f66206170706c69636174696f6e7320696e636c7564696e6720736b696e20636172652c206861697220636172652c20636f6c6f757220636f736d657469637320616e64206e61696c20636172652e203c2f703e3c703ee2809c54686572652069732061206c6f74206f66206e6f6e73656e736520676f696e67206f6e2077697468206e61747572616c20616e64206f7267616e69637320617420746865206d6f6d656e742ce2809d207361696420436172746572204c61205661792c20707265736964656e742c205a656e69746563682e20e2809c54686520696e647573747279206e6565647320746f206368616e6765202d206974e28099732074696d6520776520776f6b6520757020616e64207265616c697365642074686520776f726c64206973206368616e67696e672e204920616d2070757474696e672045636f63657274206f6e2065766572797468696e6720492063616e206265636175736520492062656c6965766520696e20697420736f207374726f6e676c79202d206974e2809973207468652077617920666f72776172642ee2809d3c2f703e3c703e546865206f6e63652066616d696c696172206e616d65206f662046696e6574657820686173206e6f77206265656e2066756c6c79206162736f7262656420696e746f20496e6e6f737065632e205468652066616d696c6961722046696e736f6c7620656d6f6c6c69656e747320617265207374696c6c20617661696c61626c652c20616c74686f7567682070726f64756374696f6e2077617320726563656e746c7920657870616e6465642066726f6d2074686520555320746f204575726f70652028456c6c65736d65726520506f72742c20554b292c2062757420617420746869732079656172e280997320696e2d636f736d65746963732074686520636f6d70616e79207761732070726f6d6f74696e67204e6174726c71756573742045333020696e20706172746963756c61722c20612072656164696c792062696f64656772616461626c65206368656c6174696e67206167656e74207468617420726573706f6e647320746f2063757272656e7420726571756972656d656e74732e20e2809c50656f706c6520617265207265616c6c79207374617274696e6720746f2070617920617474656e74696f6e20746f20677265656e20616e6420677265656e20696e6772656469656e74732ce2809d2073616964205068696c204d6174656e612c20496e6e6f7370656320767020616e642067656e6572616c206d616e616765722e20e2809c5765e280997265207265696e76656e74696e67206f757273656c7665732061732061207370656369616c697479206368656d6963616c7320636f6d70616e7920616e64207765e28099766520676f742061206772656174206e65772070726f64756374206c696e652e204f75722073747261746567792069732067726f777468202d206f7267616e696320616e64207468726f756768206163717569736974696f6e2c2077686572652069742066697473206f75722073747261746567792ee2809d3c2f703e3c703e50726573657276617469766573207765726520616e6f7468657220617265612077686572652074686520677265656e207468656d652070726f647563656420736f6d6520696e746572657374696e67206e65772070726f64756374732e204472205374726165746d616e7320696e74726f64756365642061206e65772045636f636572742d6c697374656420616e74696d6963726f6269616c20696e6772656469656e74207468617420697320636c61696d656420746f2070726f766964652061206e61747572616c20616c7465726e617469766520746f2074686520636f6e76656e74696f6e616c207072657365727661746976657320746861742068617665206265656e20676976656e206120686172642074696d6520627920736f6d65207061727473206f6620746865206d6564696120726563656e746c792e3c2f703e3c703e4465726d61736f6674203638382045636f206973206120706c616e742d62617365642066756e6769636964616c20696e6772656469656e742c20646572697665642066726f6d20626173696c20616e64206973207361696420746f20706f7373657373207375706572696f7220616e74696d6963726f6269616c20636861726163746572697374696373207468616e206f7468657220706c616e74206465726976656420616c7465726e6174697665732063757272656e746c7920617661696c61626c652ee2809c54686572652068617320646566696e6974656c79206265656e206d6f72652064656d616e6420666f7220677265656e2070726f64756374732074686973207965617220616e64206f7572206e65772070726f6475637420686173206265656e206d65742077697468207665727920676f6f6420726573706f6e73652ce2809d20736169642044722e205374726165746d616e73e2809920537573616e6e65204ac3a46e696368656e2e20e2809c576520686176652045636f63657274206c697374696e6720616e6420617265206177616974696e6720536f696c204173736f63696174696f6e2063657274696669636174696f6e2ee2809d203c2f703e3c703e5769746820657665722067726561746572207365676d656e746174696f6e20696e2074686520736b696e206361726520736563746f722c2074686520636f6d7065746974696f6e20746f20646576656c6f7020696e6772656469656e74732074686174206f6666657220616476616e63656420736b696e20636172652062656e656669747320697320617420616e20616c6c2074696d6520686967682e204265696e67206120e28098677265656ee28099206272616e64206973206f6e65207468696e67206275742074686520696e6772656469656e7473206861766520746f2064656c6976657220736f706869737469636174656420726573756c74732e3c2f703e3c703e4761747465666f7373c3a920756e7665696c656420697473206c6174657374206c61756e63682c204379746f62696f6c204c756d696e2d4579652c20616e2061637469766520696e6772656469656e742077697468207374726f6e672076617363756c6f2d70726f746563746976652070726f70657274696573207468617420697320636c61696d656420746f20726564756365206461726b20636972636c657320616e6420707566667920736b696e2061726f756e64207468652065796520617265612e205468652061637469766520636f6e7461696e7320617368206261726b20657874726163742c206f7267616e69632073696c69636f6e20616e6420766974616d696e2042332c20776869636820616374206f6e2074686520736b696ee280997320637574616e656f7573206d6963726f63697263756c6174696f6e2e2056697369626c6520726573756c74732061726520636c61696d6564206166746572203238206461797320616e6420737567676573746564206170706c69636174696f6e7320696e636c7564652065796520636f6e746f75722074726561746d656e74732c207072652d20616e6420706f73742d737572676572792074726561746d656e74732c20616e74692d616765696e67206361726520616e6420666c6173682072616469616e63652074726561746d656e74732e3c2f703e3c703e4d6962656c6c65206d65616e7768696c65206c61756e636865642074776f206e657720616e74692d616765696e6720736b696e206361726520696e6772656469656e7473206261736564206f6e20706c616e7420736369656e63652e20506879746f43656c6c546563204d616c757320446f6d65737469636120697320616e20616374697665206261736564206f6e206170706c65207374656d2063656c6c732074686174207573657320706174656e742070656e64696e6720706c616e742063656c6c2063756c7475726520746563686e6f6c6f677920616e64206973207361696420746f2070726f7465637420736b696e207374656d2063656c6c7320616761696e737420616765696e672061732077656c6c2061732064656c6179696e67207468652073656e657363656e6365206f66206861697220666f6c6c69636c65732c2068656c70696e6720746f2070726573657276652074686520766974616c69747920616e6420796f75746866756c6e657373206f662074686520736b696e2e3c2f703e3c703e416c736f206d616b696e67206974732064656275742066726f6d204d6962656c6c6520776173204173747261466f7263652c20616e20616e74692d616765696e672070726f6475637420646576656c6f70656420666f7220626c656d697368656420736b696e2e2044656d616e6420666f7220616e74692d626c656d6973682070726f647563747320666f72206d6f7265206d61747572652c206e6f6e2d7465656e61676520736b696e2069732067726f77696e672072617069646c7920627574206163636f7264696e6720746f204d6962656c6c652c207468657265206172652076657279206665772070726f647563747320617661696c61626c6520746f207472656174207468697320636f6e646974696f6e2e2054686520696e6772656469656e7420636f6e7461696e7320417374726167616c7573206d656d6272616e61636575732c206120706c616e74207573656420696e20547261646974696f6e616c204368696e657365204d65646963696e652c20616e6420697320636c61696d656420746f206669726d20616e6420736d6f6f746820736b696e2c2072656475636520696d70657266656374696f6e732c2062616c616e636520736562756d2070726f64756374696f6e2c2070726576656e7420627265616b6f75747320616e64206c656176652074686520736b696ee280997320636f6d706c6578696f6e20636c65617220616e6420726566696e65642e3c2f703e3c703e446f7720416d657263686f6c2070726573656e7465642061206e65772c20706174656e742d70656e64696e6720656e63617073756c6174696f6e20616e642064656c69766572792073797374656d2c20536174696e46582c20776869636820656e61626c657320626f746820687964726f70686f62696320616e6420687964726f7068696c6963206163746976657320746f20626520656e63617073756c6174656420696e20612076617269657479206f6620736b696e20636172652070726f64756374732e204974206973207361696420746f2062652076657279206561737920746f206d69782062792073696d706c6520736865617220746f2063726561746520656e63617073756c6174696f6e20616e6420746f207369676e69666963616e746c7920696d70726f7665207468652073746162696c69736174696f6e206f662073656e73697469766520616374697665732061732077656c6c2061732067726561746572206566666963616379206f7665722074696d652e20566974616d696e73204120616e64204320616e64204448412077657265207374756469656420616e6420696d70726f7665642073746162696c697479207761732061636869657665642e20e2809c4974206365727461696e6c7920656e61626c6573207468652064656c6976657279206f66206e61747572616c206163746976657320736f2063616e206265207573656420696e20737570706f7274206f66206e61747572616c20636c61696d732ce2809d20636f6d6d656e746564204a656e6e696665722053696773776f7274682c20627573696e65737320636f6d6d756e69636174696f6e73207370656369616c697374207769746820446f7720416d657263686f6c2e20e2809c416e64207769746820746865206f6e676f696e672064656d616e6420666f72206d756c746966756e6374696f6e616c6974792c20706f74656e7469616c6c7920696e636f6d70617469626c6520696e6772656469656e7473206c696b652044484120616e6420616d696e6f20616369647320666f722073756e6c6573732074616e6e696e6720616e6420616e74692d616765696e672063616e20626520656e63617073756c6174656420746f6765746865722ee2809d20427920656e63617073756c6174696e6720706f74656e7469616c6c792069727269746174696e6720616374697665732c2074686520706f74656e7469616c20666f722069727269746174696f6e20697320726564756365642e20536174696e465820697320616c736f207361696420746f20696d70726f766520746865206165737468657469632070726f70657274696573206f66206661636520637265616d732c206579652067656c2c20736572756d20616e6420626f6479206c6f74696f6e20666f726d756c6174696f6e732e203c2f703e3c703e4c69676874657220616e642062726967687465723c2f703e3c703e5261686e20666f6375736564206f6e20736b696e206c69676874656e696e67206c61756e6368696e672043656c6c4163746976652057686974652c2061206e657720696e6772656469656e7420646576656c6f70656420666f722067656e746c6520736b696e206c69676874656e696e672c20616e6420636f6e7461696e696e67206120636f6d62696e6174696f6e206f6620766974616d696e2042332c2073756c706875726f75732065787472616374206f6620776174657263726573732c2062696f2d617661696c61626c65207a696e6320616e6420616e20457373656e7469616c2043656c6c20426f6f737420466163746f722e20496e20766974726f207465737473206f6e20334420736b696e206d6f64656c732073686f77656420757020746f2035302520726564756374696f6e20696e206d656c616e696e2070726f64756374696f6e20616e6420616e2031312520736b696e206c69676874656e696e67206f6620417369616e20736b696e2e20e2809c546865207461726765742077617320746f20646576656c6f7020616e2061637469766520666f722077686974656e696e67207468617420776173207361666520746f20736b696e2ce2809d206578706c61696e65642044616e69656c61204775696c646d616e6e2c2068656164206f66206d61726b6574696e672c205261686e2e3c2f703e3c703e4c69706f746563206c61756e63686564204368726f6d616272696768742c2061206e657720627269676874656e696e6720616374697665207468617420697320636c61696d656420746f20696e647563652061207369676e69666963616e74206c69676874656e696e67206566666963616379206f6e2074686520736b696e20616e642068656c707320746f20756e69667920736b696e20746f6e652e204368726f6d6f62726967687420646f6573206e6f742073686f7720616e79206379746f746f78696320656666656374732c206f7220616e792069727269746174696f6e206f722073656e73697469736174696f6e207265616374696f6e206163636f7264696e6720746f2074686520636f6d70616e792e3c2f703e3c703e456c656d656e74616c2070726f74656374696f6e3c2f703e3c703ee28098456c656d656e7473206f6620626561757479e280992077617320746865206e657720736c6f67616e20666f722043696261206174207468652073686f772e20e2809c49742064657363726962657320646966666572656e7420656c656d656e7473206f6620746563686e6f6c6f677920756e646572206f6e6520756d6272656c6c61202d207765e2809972652074616b696e672061206d6f726520686f6c697374696320617070726f61636820616e6420636f6d62696e696e6720636f6e6365707473206f66206265617574792c2077656c6c2d6265696e6720616e64206865616c74682ce2809d2073616964204d69636861656c2057696c6b6f702c20627573696e65737320686561642055562070726f74656374696f6e20262061637469766520627573696e657373206c696e6520686f6d65202620706572736f6e616c20636172652c20436962612e2054686520636f6d70616e79207761732070726f6d6f74696e6720e2809c62657474657220616765696e67e2809d2061732061206d6f726520706f73697469766520776179206f66206c6f6f6b696e6720617420616765696e672c206965206865616c746869657220616765696e67207468726f75676820616e20616e74692d616765696e6720617070726f61636820617320756e666f7274756e6174656c792061676520726576657273616c206973206e6f7420706f737369626c652e205468652069646561206973207468617420746869732063616e206265206163686965766564207468726f75676820757365206f662043696261e28099732054696e6f736f72622055562066696c746572732c2054696e6f6465726d206d6f6973747572697365727320616e642054696e6f6465726d20656e63617073756c6174656420616374697665733b2043696261207361696420697420657870656374732054696e6f736f7262205320616e642054696e6f736f7262204d20746f206761696e20616363657074616e636520696e207468652055532074686973207965617220736f20706c616e7320746f20626520726561647920666f7220746865206d6174657269616c7320746f20626520696e636c7564656420696e2066696e69736865642070726f6475637473206e65787420796561722e20e2809c57652077616e7420746f20657874656e64207468652073636f7065206f66206f75722061637469766974696573202d206974e2809973206e6f74206f6e6c7920612062656175747920746f7069632c206974e28099732061206865616c74682069737375652ee2809d20556c69204f7374657277616c6465722c20676c6f62616c206d61726b6574696e67206d616e616765722055562070726f74656374696f6e20616e642061637469766520656666656374732061646465643a20e2809c436962612077617320616e206561726c7920706c6179657220696e2055564120736f207765e2809972652061206d61726b6574206c65616465722e205765206e6f772077616e7420746f20776f726b207769746820637573746f6d65727320746f20636f6e76657920746865206d65737361676520746f2074686520756c74696d61746520636f6e73756d65722ee2809d2054686520636f6d70616e7920616c736f2077616e747320746f20776f726b2077697468206465726d61746f6c6f676973747320746f20696d70726f76652074686520756e6465727374616e64696e67206f662073756e2070726f74656374696f6e2074686572652e20e2809c5468657920646f6ee280997420616c6c20756e6465727374616e642053504620616e64206974e2809973207665727920696d706f7274616e742074686174207468657920646f2ce2809d2073616964204f7374657277616c6465722e20e2809c4974e280997320696d706f7274616e7420746f20776f726b206f6e2074686520696d616765206f662073756e73637265656e7320627574207765e28099726520636f756e74696e67206f6e20746865206661637420746861742070656f706c652077696c6c20616c776179732077616e7420746f206578706f7365207468656d73656c76657320746f2073756e2e20416e6420766974616d696e204420646566696369656e6379206973206e6f77206265696e67207365656e206173206265696e6720726573706f6e7369626c6520666f722061206c6f74206f662063616e636572732c207768696c6520766974616d696e2044207265717569726573205556422e204275742070726f74656374696f6e20636f6d65732066697273742ee2809d203c2f703e3c703e4e657874206d6f6e7468205350432077696c6c207265706f7274206f6e206d616e79206d6f7265206c61756e6368657320616e64206576656e74732066726f6d207468652073686f772c20696e636c7564696e6720746869732079656172e280997320696e737069726174696f6e616c20696e2d666f63757320666561747572652c2055746f7069612c20616e6420746865206576657220706f70756c6172207472656e64732070726573656e746174696f6e732e203c2f703e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000772915fce46b8b1f; asc               <      i    i.    7         X 7     4                  <      i0   i>    7         ` 7     4                  <      i@   iN    7         h 7     4                  <      iP   i^    7         p 7     4                  <      i`   in    7         x 7     4                  <      ip   i~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j.    7           7     4                  <      j0   j>    7           7     4                  <      j@   jN    7           7     4                  <      jP   j^    7           7     4                  <      j`   jn    7           7     4                  <      jp   j~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      k    k     7           7     4                  <      k    k     7           7     4                  <      k    k.    7           7     4                  <      k0   k>    7           7     4                  <      k@   kN    7         ( 7     4                  <      kP   k^    7         0 7     4                  <      k`   kn    7         8 7     4                  <      kp   k~    7         @ 7     4                  <      l    l     7         H 7     4                  <      l    l     7         P 7     4                  <      l    l.    7         X 7     4                  <      l0   l>    7         ` 7     4                  <      l@   lN    7         h 7     4                  <      lP   l^    7         p 7     4                  <      l`   ln    7         x 7     4                  <      lp   l~    7           7     4                  <      l    l     7           7     4                  <   !  l    l     7           7     4                  <   ""  l    l     7           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      g    g     8           7     4                  <      g    g     8           7     4                  <      g    g.    8           7     4                  <      g0   g>    8           7     4                  <      g@   gN    8           7     4                  <      gP   g^    8           7     4                  <      g`   gn    8           7     4                  <      gp   g~    8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h.    8         ( 7     4                  <      h0   h>    8         0 7     4                  <      h@   hN    8         8 7     4                  <      hP   h^    8         @ 7     4                  <      h`   hn    8         H 7     4                  <      hp   h~    8         P 7     4                  <      h    h     8         X 7     4                  <      h    h     8         ` 7     4                  <      h    h     8         h 7     4                  <      h    h     8         p 7     4                  <      h    h     8         x 7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      i    i     8           7     4                  <      i    i     8           7     4                  <      i    its actives a green leaf grade as well as indicating which are Ecocert approved, which are preservative-free and which paraben-free. </p><p>Croda has also gone down the green route, launching Up Close and Green, a new green guide to its speciality raw materials. The guide enables formulators to determine how green a product is, with reference to origin (plant, animal or mineral), petrochemicals, silicones, preservatives and biodegradability amongst others. The guide also features a Green Criteria that marks a deliberate move away from the current certification standards available. Under the criteria all products in the guide are free of ethylene oxide and propylene oxide-based components, contain no petroleum distillates, no phthalates, no parabens, no formaldehyde-releasing preservatives and have not been tested on animals.</p><p>   There are so many discrepancies between each certifier that we have left the option of which standard to follow to our customers,    explained Sarah Millns, marketing communications coordinator, personal & health care, Croda.    We are also waiting for the European certification standard to launch, which may change some criteria.   </p><p>Following this sentiment, the company has developed two new sun care products, Solaveil CT-300 and Solaviel CZ-300, and two hydrating peptides from organic sources. Hydroavena HpO and Hydroexcelsa HpO are moisturising agents derived by gentle enzymatic hydrolysis of certified organic crops.</p><p>Symrise has broadened its organic portfolio, adding new products to its Extrapone Organic range, which is based on controlled harvesting. New products include Neo Actipone Soap Nutshell, a 100% natural surfactant suitable for use in personal care applications such as shampoos and body washes.</p><p>   Botanicals are proven in screening methods to have relevant effects such as anti-irritant and antioxidant for cosmetic applications,    Michael Schuricht, regional business manager, Symrise, told SPC.</p><p>The company has also renamed its cosmetics business unit, which will now be known as Life Essentials, but is still a part of Symrise   s Scent & Care division.</p><p>Silab has also entered the organic arena, launching a new Ecocert certified organic range, which will initially comprise three active products - Osilift Bio, Structurine Bio and Vitanol Bio.  </p><p>And Lipo has launched a new line of natural emollients, derived from 100% natural plant sources. The Lipobutter range comprises 11 varieties, eight of which are validated by Ecocert, while the refined organic shea variant is certified organic by Ecocert. Varieties include apricot, refined cocoa, olive, jojoba, refined mango and peach and application suggestions include skin, sun and hair care products, fine soaps and body butters.</p></p><p>Zenitech   s new Meadowfoam and Orange butters also give a nod to natural, with Ecocert validation. The products are said to be suitable for a variety of applications including skin care, hair care, colour cosmetics and nail care. </p><p>   There is a lot of nonsense going on with natural and organics at the moment,    said Carter La Vay, president, Zenitech.    The industry needs to change - it   s time we woke up and realised the world is changing. I am putting Ecocert on everything I can because I believe in it so strongly - it   s the way forward.   </p><p>The once familiar name of Finetex has now been fully absorbed into Innospec. The familiar Finsolv emollients are still available, although production was recently expanded from the US to Europe (Ellesmere Port, UK), but at this year   s in-cosmetics the company was promoting Natrlquest E30 in particular, a readily biodegradable chelating agent that responds to current requirements.    People are really starting to pay attention to green and green ingredients,    said Phil Matena, Innospec vp and general manager.    We   re reinventing ourselves as a speciality chemicals company and we   ve got a great new product line. Our strategy is growth - organic and through acquisition, where it fits our strategy.   </p><p>Preservatives were another area where the green theme produced some interesting new products. Dr Straetmans introduced a new Ecocert-listed antimicrobial ingredient that is claimed to provide a natural alternative to the conventional preservatives that have been given a hard time by some parts of the media recently.</p><p>Dermasoft 688 Eco is a plant-based fungicidal ingredient, derived from basil and is said to possess superior antimicrobial characteristics than other plant derived alternatives currently available.   There has definitely been more demand for green products this year and our new product has been met with very good response,    said Dr. Straetmans    Susanne J  nichen.    We have Ecocert listing and are awaiting Soil Association certification.    </p><p>With ever greater segmentation in the skin care sector, the competition to develop ingredients that offer advanced skin care benefits is at an all time high. Being a    green    brand is one thing but the ingredients have to deliver sophisticated results.</p><p>Gattefoss   unveiled its latest launch, Cytobiol Lumin-Eye, an active ingredient with strong vasculo-protective properties that is claimed to reduce dark circles and puffy skin around the eye area. The active contains ash bark extract, organic silicon and vitamin B3, which act on the skin   s cutaneous microcirculation. Visible results are claimed after 28 days and suggested applications include eye contour treatments, pre- and post-surgery treatments, anti-ageing care and flash radiance treatments.</p><p>Mibelle meanwhile launched two new anti-ageing skin care ingredients based on plant science. PhytoCellTec Malus Domestica is an active based on apple stem cells that uses patent pending plant cell culture technology and is said to protect skin stem cells against ageing as well as delaying the senescence of hair follicles, helping to preserve the vitality and youthfulness of the skin.</p><p>Also making its debut from Mibelle was AstraForce, an anti-ageing product developed for blemished skin. Demand for anti-blemish products for more mature, non-teenage skin is growing rapidly but according to Mibelle, there are very few products available to treat this condition. The ingredient contains Astragalus membranaceus, a plant used in Traditional Chinese Medicine, and is claimed to firm and smooth skin, reduce imperfections, balance sebum production, prevent breakouts and leave the skin   s complexion clear and refined.</p><p>Dow Amerchol presented a new, patent-pending encapsulation and delivery system, SatinFX, which enables both hydrophobic and hydrophilic actives to be encapsulated in a variety of skin care products. It is said to be very easy to mix by simple shear to create encapsulation and to significantly improve the stabilisation of sensitive actives as well as greater efficacy over time. Vitamins A and C and DHA were studied and improved stability was achieved.    It certainly enables the delivery of natural actives so can be used in support of natural claims,    commented Jennifer Sigsworth, business communications specialist with Dow Amerchol.    And with the ongoing demand for multifunctionality, potentially incompatible ingredients like DHA and amino acids for sunless tanning and anti-ageing can be encapsulated together.    By encapsulating potentially irritating actives, the potential for irritation is reduced. SatinFX is also said to improve the aesthetic properties of face creams, eye gel, serum and body lotion formulations. </p><p>Lighter and brighter</p><p>Rahn focused on skin lightening launching CellActive White, a new ingredient developed for gentle skin lightening, and containing a combination of vitamin B3, sulphurous extract of watercress, bio-available zinc and an Essential Cell Boost Factor. In vitro tests on 3D skin models showed up to 50% reduction in melanin production and an 11% skin lightening of Asian skin.    The target was to develop an active for whitening that was safe to skin,    explained Daniela Guildmann, head of marketing, Rahn.</p><p>Lipotec launched Chromabright, a new brightening active that is claimed to induce a significant lightening efficacy on the skin and helps to unify skin tone. Chromobright does not show any cytotoxic effects, or any irritation or sensitisation reaction according to the company.</p><p>Elemental protection</p><p>   Elements of beauty    was the new slogan for Ciba at the show.    It describes different elements of technology under one umbrella - we   re taking a more holistic approach and combining concepts of beauty, well-being and health,    said Michael Wilkop, business head UV protection & active business line home & personal care, Ciba. The company was promoting    better ageing    as a more positive way of looking at ageing, ie healthier ageing through an anti-ageing approach as unfortunately age reversal is not possible. The idea is that this can be achieved through use of Ciba   s Tinosorb UV filters, Tinoderm moisturisers and Tinoderm encapsulated actives; Ciba said it expects Tinosorb S and Tinosorb M to gain acceptance in the US this year so plans to be ready for the materials to be included in finished products next year.    We want to extend the scope of our activities - it   s not only a beauty topic, it   s a health issue.    Uli Osterwalder, global marketing manager UV protection and active effects added:    Ciba was an early player in UVA so we   re a market leader. We now want to work with customers to convey the message to the ultimate consumer.    The company also wants to work with dermatologists to improve the understanding of sun protection there.    They don   t all understand SPF and it   s very important that they do,    said Osterwalder.    It   s important to work on the image of sunscreens but we   re counting on the fact that people will always want to expose themselves to sun. And vitamin D deficiency is now being seen as being responsible for a lot of cancers, while vitamin D requires UVB. But protection comes first.    </p><p>Next month SPC will report on many more launches and events from the show, including this year   s inspirational in-focus feature, Utopia, and the ever popular trends presentations. </p>
Mar 20 14:46:44 localhost mysqld: w)   k  ;
Mar 20 14:46:44 localhost mysqld: InnoDB: End of page dump
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 1274019770, innodb 28570114,  page type 39311 == PAGE TYPE CORRUPTED.none 3735928559, stored checksum in field2 1999181308, calculated checksums for field2: crc32 1274019770, innodb 3035797051, none 3735928559,  page LSN 41625 2406031360, low 4 bytes of LSN at page end 3832253215, page number (if stored to page already) 2147483648, space id (if created with >= MySQL-4.1.1 and stored already) 256128
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

}}}


I tried to use Windows 7 with the same version of VirtualBox - no problems at all.



",vagiz
19417,incorrect power off handling with background vms,Windows,other,VirtualBox 6.1.4,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
19419,"Guru Mediation - Cent Os 7, when i start a local ant build",Windows,Linux,VirtualBox 6.1.4,2020-03-21T10:33:31Z,2020-03-21T10:33:31Z,Guru Meditation is coming very frequently. Please help me to resolve the issue,mariswamy
19367,a crash on resume machine,Linux,Windows,VirtualBox 6.1.4,2020-03-21T14:19:51Z,2020-03-21T14:19:51Z,"When i resume machine , i have crash on load 'vga'.[[BR]]
I had executed a opengl application.[[BR]]
Thank.[[BR]]

",Sizy458
16450,VM locks up when setting --discard and --nonrotational and using fstrim,Linux,Linux,VirtualBox 5.1.14,2020-03-21T16:49:41Z,2020-03-21T16:49:41Z,"I changed the settings of my Xubuntu VM to emulate an SSD:

{{{
VBoxManage storageattach Xubuntu --storagectl SATA --port 0 --discard on --nonrotational on
}}}

After that started the VM. Everything runs fine until running fstrim in the VM. First the VDI file is shrinked a bit, then VirtualBox starts continuously reading from host filesystem (I guess from the VDI file). After some time the VM guest OS reports storage problems (timeouts) in dmesg output. No access to emulated storage is possible after that, but VM continues to run (e.g. scrolling in windows, moving mouse, ...). See attached VM screenshots and VBox.log for details.

I already observed the same behavior with a Windows 10 VM which locked up in the same way, but then I did not record any logs or error information.

Problem seems to be similar to ticket #15509.

Host info: Kubuntu 16.10 64 Bit, VirtualBox 5.1.6 (installed from Kubuntu repository)

Guest info: Xubuntu 16.10 64 Bit, 1 SATA controller, 1 VDA file with dynamic size

Please tell if any more information is needed.",Motlib
19345,Oracle_VM_VirtualBox_Extension_Pack-6.1.4 Signature invalid (Mac OS X 10.10.5 Yosemite),Mac OS X,all,VirtualBox 6.1.4,2020-03-22T00:50:11Z,2020-03-22T00:50:11Z,"Install ran smoothly without signature errors (as appeared in VB 6.1.2).

Now the signature error comes up with the Extension Pack:

Failed to load the main module ('/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'): VERR_FILE_NOT_FOUND - dlopen(/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib, 6): no suitable image found. Did find:
/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib: code signature invalid for '/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'
.


Fehlercode: 
NS_ERROR_FAILURE (0x80004005)
Komponente: 
ExtPackManagerWrap
Interface: 
IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
",cdvk
19421,Virtual machine is inaccessible,Mac OS X,Windows,VirtualBox 6.0.18,2020-03-22T20:19:42Z,2020-03-22T20:19:42Z,"After updating VirtualBox to version 6.0.18 I used the program for a few hours, I updated the extension packs without being able to use the iMac camera in the guest system. I turned off the virtual machine first and then the VirtualBox program without problems. A day later when I restarted the program, a message warned me that the WIN-10 virtual machine is inaccessible.
Looking forward to your reply, best regards. Giovanni DV

PS: I am attaching the messages received when the program was turned on, and the request to open the file.

",giovanniDV
19423,full crash of host machine,Linux,Linux,VirtualBox 6.1.4,2020-03-23T02:23:17Z,2020-03-23T02:23:17Z,"This report is going to be very incomplete for now.  I'll update it, if I can get some instruction on what and how to collect some better detail.  I am getting this crash half a dozen times a day when working in the environment

Environment:
Host Fedora 31 workstations 5.5.10-200.fc31.x86_64
dual monitors
16GB memory, 4 cores
Guest Fedora 31 workstations 5.5.10-200.fc31.x86_64
single monitor
6GB memory, 2 cores
Large window, slightly extending past the physical monitor size
scaled mode
Running guest application: qtcreator, debugging an application

The symptoms, just before the hard (black screen) crash of the host:

Attempt some operation in qtcreator, like clicking to create a new breakpoint.  The application freezes, the VM freezes, and all other applications windows except shells freeze.  Freeze might not be quite right.  Clicking on an application window on the host (2nd monitor) that is occluding a shell window activates the shell not the application window.  So the application might already be dead, and just a ghost of the window left on the desktop.  The shell window seems active, but not much time to look around.  In a few seconds, the host goes into full black screen crash, with a blinking text cursor.  Sometimes, in a few more seconds, the host login windows appears without any additional user actions.  Sometimes, ctrl+alt+del will initiate a reboot.

So, is there anything I can enable ahead of time, to get a log that might be useful for tracking this down?  What data can I collect after host reboot to include here?

I have other fc31 guest vms that are not crashing, so there is some interaction with the running applications.  But a misbehaving application should not crash the VM, and definitely should not crash the host machine.",mMerlin
19418,Guest Additions: Debian 10 Auto resize display problem,Mac OS X,Linux,VirtualBox 6.0.18,2020-03-23T07:57:13Z,2020-03-23T07:57:13Z,"v6.0.18 r136238

Oracle_VM_VirtualBox_Extension_Pack-6.0.18

Guest additions installed on Debian 10, however there is an issue with view ""automatic resize guest display"".  When this option is checked, the display of the Debian 10 session maximized or a Full Screen session is invoked, then the display shows a black blank screen with mouse pointer.  I'm using a MacBook 12"" with 2304 x 1440 Retina display.  I had a similar problem in the past for this display and virtual box maintainers fixed it.  I suspect something may be going on with the resolution scaling code.

",npapadon
19426,USB-to-Ethernet crash with Ubuntu guest and Windows 10 host,Windows,Linux,VirtualBox 6.1.4,2020-03-24T01:41:52Z,2020-03-24T01:41:52Z,"Hi,

I'm passing a USB 3.0 USB-to-Ethernet adapter to a Ubuntu 18.04 VM running on a Windows 10 host. After a few seconds of high bandwidth data transfer, the xhci driver in the guest crashes with the following output in dmesg:

{{{
[ 2556.648728] xhci_hcd 0000:00:0c.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 2556.648734] xhci_hcd 0000:00:0c.0: Looking for event-dma 00000000381ff450 trb-start 00000000381ff300 trb-end 00000000381ff300 seg-start 00000000381ff000 seg-end 00000000381ffff0
}}}

The bug happens whether or not I have the guest additions installed. I've tested that this bug does NOT occur when using the same adapter on either a native Windows 10 or Ubuntu machine. I also tried updating the kernel and drivers in the guest VM to the latest version but the bug still occurs. The bug also seems to happen with a variety of USB 3.0 USB-to-Ethernet adapters.

Notably the bug seems to happen on several Dell laptops (Dell Precision 5520). I tested the same setup on an HP laptop with an Ubuntu host but the issue did not appear.",xynith
19428,XP VM unexpected error,Linux,Windows,VirtualBox 5.2.34,2020-03-24T17:55:20Z,2020-03-24T17:55:20Z,"Hello!
I just create a VM for Windows XP. Then i installed dotNET framework version 4.0 and the KB2836939 update (needed to install Daemontools lite).
You could see the attached log file.
Thanks for help!

NB: i'm french and have a very bad english...",Hugo
14176,Failed to open a session for the virtual machine,other,other,VirtualBox 4.3.28,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
19434,some characters are not rendered in QML Application,Mac OS X,other,VirtualBox 6.1.4,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
19435,Critical error on boot of KISS linux - enters Guru meditation,other,other,VirtualBox 6.1.4,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
19436,"Unstable Guest- win 10, 7 , Fedora 29, Ubuntu 19.04",Windows,all,VirtualBox 6.1.4,2020-03-27T12:18:04Z,2020-03-27T12:18:04Z,"I have found win 10, 7 , Fedora 29, Ubuntu 19.04 having issues with 6.1.4 (unresponsive, apps crashing, guest reboot),(tested on different hardware)
it is looks like a bug, log attched",war357
19437,A critical error has occurred while running the virtual machine and the machine execution has been stopped.,Windows,Linux,VirtualBox 6.1.4,2020-03-27T13:11:03Z,2020-03-27T13:11:03Z,"I am using windows10 64bit on UEFI pc desktop this error occured to me trying to use kali linux on virtual box i will attach my vbox.log and vbox.png 
i enabled virtualization , and installed the ext pack same version as the program and still can't make up what's is even the problem! , 
i can't figure any thing from the vbox.log so , any suggestions? ",DEV
19439,Resize Screen crashes Everything,Windows,Linux,VirtualBox 6.1.4,2020-03-27T13:53:09Z,2020-03-27T13:53:09Z,"I am using Windows 10, VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.6.2)
 with an Ubuntu 18.04 LTS guest. Once the guest is installed and rebooted, resizing the screen in windows can lock the VM, and eventually the whole PC. 

Steps to reproduce resize the screen and before the guest is refreshed add a little more screen. Different kinds of hangs but the VM guest is always hung. Sometimes VBox host hangs also.",jerry ely
19440,OVF import fails due to incorrect validation of SHA256 digests,Linux,all,VirtualBox 6.1.4,2020-03-27T15:38:37Z,2020-03-27T15:38:37Z,"
When importing a virtual machine (VM) from .ovf file that is accompanied by a
.mf file that specifies file integrity hashes using SHA256, the importer (both
fom the GUI or using VBoxManage) check the integrity of the files as part of
the import process.

Specifically, the file I am seeing the issues is the hard drive of the VM,
provided in VMDK format. The importer exits with an error indicating that the
digest of the VMDK file does not match the one in the .mf file, but using tools
such as sha256 sum I see that the hash does match (see output below).

{{{
$ VBoxManage import ~/vms/testvm0146.ovf

(...snip...)

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): Attribute 'SHA256' on
'testvm0146-0.vmdk' does not match
('03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9' vs.
'19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d')
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component
ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at
line 1118 of file VBoxManageAppliance.cpp
}}}

However, sha256sum gives the following output:

{{{
$ sha256sum ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

Additionally, sha246deep also provides the same hash:

{{{
$ sha256deep ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

The contents of the testvm0146.mf file are:

{{{
$ cat ~/vms/testvm0146.mf
SHA256(testvm0146-0.vmdk)=
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
SHA256(testvm0146-1.nvram)=
4615577454b8ea7c464f4aee064936e48db52ddb08f23e9ea74ade5e12fce8ce
SHA256(testvm0146.ovf)=
7cbaf2f6dc9ada576ae99ba0f5ef001432650581ad401d4312f297d2737ced49
}}}

As can be seen, the output of sha256sum and the .mf file match
(`03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9`), but for
some reason virtualbox determines the SHA256 hash to be
`19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d`, and thus the
comparison fails.

This has been seen both in Oracle Virtualbox packages (in Ubuntu) as well as Debian-packaged virtualbox (in Debian), which suggests the issue is probably upstream in virtualbox.
",radnaj
19441,Feature request: Menu to switch among running machines (and host),all,all,VirtualBox 6.0.18,2020-03-27T16:07:40Z,2020-03-27T16:07:40Z,"The menu bar of a running virtual machine displays its name. This could be (optionally) replaced by a menu with an option for each of the various running machines (and possibly one for the host). Choosing an option from this menu could switch the display to the window of the corresponding machine (or to the desktop of the host). When running multiple virtual machines in full-screen mode, this change would make it more convenient to switch among those machines.",xphileprof
19433,VM's Constantly going into Guru Mediation state,Mac OS X,Linux,VirtualBox 6.1.4,2020-03-27T19:56:51Z,2020-03-27T19:56:51Z,"Im trying configure a Virtual environment for testing but whenever I start my vis up they all starts dropping into guru mediation state and im getting frustrated. I have a MacBook Pro running Catalina and the box versions is 6.14

",gazza2217
19422,VirtualBox Host-Only Ethernet Adapter DHCP settings proper apply need restart of VB,Windows,BSD,VirtualBox 6.1.4,2020-03-28T13:29:46Z,2020-03-28T13:29:46Z,"Changing DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H) need restart of the whole VB to be applied properly. If not, settings VB was started with are applied (whatsoever user changes them), after just guest is restarted.


It should work in other way: user stops guest, changes DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H), starts guest and changes are properly applied.


Now it needs to stop all guests, main window of VB should be closed, VB should be started again.",MikhailRokhin
19443,Bridge Adapter Name List displays not existed NIC on Windows,Windows,all,VirtualBox 6.1.4,2020-03-29T10:11:04Z,2020-03-29T10:11:04Z,Some removed NICs are still displayed in the Name List if VMs set to Bridged Adapter mode.,ohnoithappens
19446,Virtualbox 6.1.4 r136177. -under MacOS Catalina - Host Only Does not work,other,other,VirtualBox 6.1.4,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
19447,Getting error when trying to install the virtualbox extension pack,other,other,VirtualBox 6.0.18,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
19445,Clipboard broken,Linux,other,VirtualBox 6.1.4,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
18073,Regression: Tails shuts down after snapshot restore (on SATA optical drive),all,Linux,VirtualBox 5.2.20,2020-03-30T08:36:19Z,2020-03-30T08:36:19Z,"Tails thinks that the medium has been removed/changed and does it's emergency shutdown after restoring from a snapshot.

""cat /dev/sr0"" errors out and there are errors about failing to access sr0 in dmesg.

Steps:

1.: Configure the VM to have the ISO in a SATA/AHCI optical drive.

2.: Boot it and make a snapshot when it's done.

3.: Restore from the snapshot. The Guest VM will shut down.

Regression in r64134. Not fixed in trunk yet.

Caveat: Triggering the bug on e.g. 5.2.20 might require to set the Base Memory size to anything larger than 1024 MiB and the Video Memory size to anything larger than 16 MiB. (e.g. set the Base Memory size to 4096 MiB and the Video Memory size to 32 MiB.)

Affected: trunk, 5.2.x

Unaffected: 5.1.x. Older versions should be unaffected.",Christian Inci
19448,VBoxManager (CLI) startvm fails for aborted images,Mac OS X,Linux,VirtualBox 6.1.4,2020-03-30T17:18:45Z,2020-03-30T17:18:45Z,"CLI version:
    Oracle VM VirtualBox Command Line Management Interface Version 6.1.4

Steps:
    With an image that is in the ""aborted"" state do:
    VBoxManage startvm ${MY_IMAGE_GUID} --type headless

Expected:
    Start proceeds as if the vm was in the ""powered off"" state.

Actual:
    VBoxManage: error: The VM session was aborted
    VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession",thirtytwobits
18953,guest additions fail to install,Windows,Windows,VirtualBox 6.0.12,2020-03-31T11:59:06Z,2020-03-31T11:59:06Z,"fails to install see log

https://pastebin.com/sw74ba1C",DeGarden
19454,Transfer of large files from guest to host causes hang,Linux,Windows,VirtualBox 6.1.4,2020-04-01T18:48:28Z,2020-04-01T18:48:28Z,"Host: Windows 10, Guest: Debian
Mount shared folder on from host.
Write large (>10GB) file.
Processes on guest will begin to hang.
Attempt to reboot may hang as well.",eng3
19456,VINF_EM_TRIPLE_FAULT when starting Ubuntu 16.04 on Win10 2004,Windows,Linux,VirtualBox 6.1.4,2020-04-02T12:50:53Z,2020-04-02T12:50:53Z,"Win 10 2004 host, with Hyper-V enabled
VBox 6.1.4
Fresh Ubuntu Server 160406 64-bit install
Ubuntu boots and then ""hangs"" during the boot process
Intermittently, not always, it will throw a VINF_EM_TRIPLE_FAULT when this happens
Played around with various system / processor settings, no change. Reverted to defaults.",yorickdowne
19459,VERR_PROC_ELEVATION_REQUIRED when running file with mandatory UAC elevation,all,Windows,VirtualBox 6.1.4,2020-04-02T20:52:57Z,2020-04-02T20:52:57Z,"Hello.

I am trying to execute file, which requires UAC elevation with VBoxManage, and keep getting 'VERR_PROC_ELEVATION_REQUIRED' with both 'vboxmanage guestcontrol start' and  'vboxmanage guestcontrol run'. 
Disabling UAC on guest OS does not help either.

{{{
$ vboxmanage guestcontrol w10 --username user --password password start C:\\Users\\user\\Desktop\\rufus-3.9.exe
VBoxManage: error: VERR_PROC_ELEVATION_REQUIRED
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestProcessWrap, interface IGuestProcess, callee nsISupports
VBoxManage: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aWaitStartFlags), gctlRunGetRemainingTime(msStart, cMsTimeout), &waitResult)"" at line 1469 of file VBoxManageGuestCtrl.cpp
}}}
",1ns
19460,Can't show Top Menu bar in Windows XP,Mac OS X,Windows,VirtualBox 6.1.4,2020-04-03T00:00:11Z,2020-04-03T00:00:11Z,"My rig: MacBookPro 15-inch (early 2012)
MacOs 10.14.6 (Mojave)
16gb ram
Virtual Box 6.1.4
Installed Windows XP. I want to install XP Guest Additions, but the desktop menu at top is not visible.
Went to vBox to check the flag  in the interface settings. There is no flag for the top menu visible.
See Link:
https://www.dropbox.com/s/2jkpfsql7hcs0nc/Screenshot%202020-04-02%2016.17.25.png?dl=0

BTW, former Apple QA test engineer here. (left just before Jobs came back)",zenmasterb
19381,Virtual box keeps crashin during startup of virtual OS,Mac OS X,Linux,VirtualBox 6.1.4,2020-04-05T10:10:55Z,2020-04-05T10:10:55Z,"I have a fedora OS (tried with fedora 29,30,and 31). I have been using mac Os Mojave throughout. However, recently the OS can't be started and I get the following crash report with the erro reading '''Failed to open a session for the virtual machine fedora'''

'''Failed to open a session for the virtual machine fedora.

The virtual machine 'fedora' has terminated unexpectedly during startup because of signal 11.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

'''",Anky
18388,"""The instruction at 0x000000006BC88A90 referenced memory at 0x0000000000000008. The memory could not be read."" when trying to open Devices > Optical Drives",Windows,Linux,VirtualBox 5.2.26,2020-04-05T11:30:06Z,2020-04-05T11:30:06Z,"Im using
Host: Windows 10 Pro 64 bit v1803
VB: VirtualBox 5.2.26r128414
Guest: Ubuntu 18.04

Getting the error consistently.",custard130
18629,Failed to open a session for the virtual machine vm1.,Windows,other,VirtualBox 6.0.6,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
19420,mount -t vboxsf Operation not supported by device,Windows,BSD,VirtualBox 6.1.4,2020-04-06T17:10:27Z,2020-04-06T17:10:27Z,"When use `mount -t vboxsf ...`as suggested by VB-host SharedFolders hint, it fails, but writes nothing in dmesg. And there is mistake in the hint - it should be vboxVFS not vboxSF. Because vboxSF triggers nothing and vboxVFS triggers kldload of /boot/modules/vboxvfs.ko . [[BR]][[BR]]

When use `mount -t vboxvfs ...` and `mount_vboxvfs ...` it shows:[[BR]]

link_elf_obj: symbol bcmp undefined[[BR]]
linker_load_file: /boot/modules/vboxvfs.ko - unsupported file type  [[BR]][[BR]]

FreeBSD 13-Current[[BR]]
Additions: 5.2.34_2 (installed via pkg, not compiled) [[BR]][[BR]]
",MikhailRokhin
19363,Bidirectional support not working after 6.1.4 update in Linux Mint 19.1 or Ubuntu 14.04,Windows,Linux,VirtualBox 6.1.4,2020-04-06T18:17:13Z,2020-04-06T18:17:13Z,"I did an update yesterday to VB 6.1.4, installed the latest extension pack 6.1.4r136177, and updated the vbox guest additions to 6.1.4. I lost the ability to automatically mount my shared folder, I solved this by editing the following

sudo systemctl edit --full vboxadd-service

removed ""systemd-timesync.service"" from ""Conflicts="" line in [Unit] section. 
change from -->
Conflicts=shutdown.target systemd-timesync.service

To -->
Conflicts=shutdown.target

Then rebooted
Solved the automount issue, but did not solve the bidirectional copy and paste not working. What can I try next?

Having same problem with bidirectional copy and paste in my Ubuntu guest as well.  Id say, since I have the same issue in both this may be a bug.  ",DStair
16172,"""One or more disk image files are not currently accessible (...)"" error, but the file is there and the VM starts",Linux,Windows,VirtualBox 5.1.8,2020-04-07T04:52:25Z,2020-04-07T04:52:25Z,"Hi All,
I've upgraded to version 5.1.8 r111374 using the Fedora 24 packages. I only have one Windows 10 VM that I've been using without issues for many months.

Since upgrading, every time I start VirtualBox (not the VM) I get the error saying: ""One or more disk image files are not currently accessible. As a result, you will not be able to operate virtual machines that use these files until they become accessible later. Press Check to open the Virtual Media Manager window and see which files are inaccessible, or press Ignore to ignore this message."".

The file is the VM's sole vdi file, but it is not missing, and if I click on Ignore the VM starts without any issues. Stopping and restarting the VM does not show the error again. Shutting down VirtualBox and restarting it shows the error again.

It is just an annoyance for now but perhaps it can develop in something worse.
",giacecco
19464,Windows 10 64bit Not Available In The Guest Templates,Windows,Windows,VirtualBox 6.1.4,2020-04-08T11:06:27Z,2020-04-08T11:06:27Z,"I am facing an issue with version 6.1.4 r136177 (Qt5.6.2). I installed it, enabled the virtualization in BIOS then Windows 64bit guest became available in the OS list. I installed it, but after restart my host Machine the option to create a new Windows 64bit guest is not available anymore. I tried to uninstall, removed registers, path, etc but nothing is working. I tried all the suggestions of the VirutalBox forum but nothing is working. 

Please find below my current configuration:

Host Information:

-> Lenovo T440
-> Windows 10 Enterprise Version 1703 OS Build 15063.2108
-> Virtual Box Version 6.1.4 r136177 (Qt5.6.2)
-> Windows Hyper-V is disabled
-> Virtualization BIOS is enabled (VT-X)
-> CPU virtualization is enabled
-> Containers is disabled
-> Windows Subsystem for Linux is disabled",Naua
19466,VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not display sub compartments,other,Linux,VirtualBox 6.1.4,2020-04-08T13:30:31Z,2020-04-08T13:30:31Z,"I want to launch a cloud VM in a sub compartment of a compartment of a tenancy.

Your wizard only goes down 1 level to the compartment level and does NOT show the sub compartments (or beyond).

Please e-mail me for more info: bernie.doehner@oracle.com. 
Thanks,
Bernie
",BernieD
19467,VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not handle errors gracefully,other,other,VirtualBox 6.1.4,2020-04-08T13:36:01Z,2020-04-08T13:36:01Z,"At first, I attempted to launch a new cloud VM without creating a profile first.
I made several errors entering key value pairs, but the wizard also shortened my private key filename so that it subsequently couldn't find it. The New Cloud VM wizard just kept erroring out when I attempted to fix my errors instead of actually accepting my corrections.

I had to delete my profile and enter it into the cloud profile directly and correctly (to avoid erroring out).",BernieD
19468,VirtualBox 6.1.4 New Cloud VM (OCI) wizard public network radio button doesn't work,other,other,VirtualBox 6.1.4,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
19469,VirtualBox 6.1.4 New Cloud VM (OCI) wizard  - missing options,all,all,VirtualBox 6.1.4,2020-04-08T15:32:38Z,2020-04-08T15:32:38Z,"I'd like to deploy a VM to OCI and have the same controls in VirtualBox as I have on the OCI Console or Python SDK:
Options that are missing in VirtualBox 6.1.4:
Availability Domain
custom images
VM shape

",BernieD
19472,Update from VirtualBox 5.2 to 6.1.4 errors,other,other,VirtualBox 6.1.4,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
19474,Incorrect checksum for freed object,Mac OS X,other,VirtualBox 6.1.4,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
19475,Problems in guest settings with too many CPUs present at the host.,Linux,all,VirtualBox 6.1.4,2020-04-10T21:14:10Z,2020-04-10T21:14:10Z,"If there are more than 32 CPU cores present at the host computer, the guest settings CPU-slider-bar shows only red, but the slider is slidable anyway.

After limiting the number of available cores of the host to 32 or less, the guest settings seem to act normal.

As the host (IBM System X3850) has four 10-core-XEON 8870 CPUs, there are 40 cores (80 threads) altogether, which I would like to use entirely.",Orbiter
19477,Virtualbox fatal error while using DisplayLink,Linux,all,VirtualBox 6.1.4,2020-04-11T16:10:54Z,2020-04-11T16:10:54Z,"Hi,

I hope you are well in this unprecedented situation and thank you for all your hard works in this crisis.

I recently started using Wavlink Universal USB 3.0 and install the driver from https://www.displaylink.com/downloads/ubuntu

Whenever I plug it to the laptop and run the Virtualbox with a normal user, it shows the error below:


{{{
Gdk-Message: 16:26:10.843: VirtualBox: Fatal IO error 0 (Success) on X server :0
}}}

and when I run it with root access:


{{{
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server "":0""
      after 681 requests (681 known processed) with 0 events remaining.
}}}

But when I disconnect the DisplayLink, it shows the UI and it works.

Here are the details of ubuntu:


{{{
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic
Linux 5.3.0-46-generic #38~18.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
}}}",navid_gh
19478,NAT limitations,Windows,Windows,VirtualBox 6.1.4,2020-04-11T19:11:12Z,2020-04-11T19:11:12Z,"Current version NAT limitations are well documented in https://www.virtualbox.org/manual/UserManual.html#nat-limitations

Some of them, such as ICMP, have been there over ten years, as this bugtrack documents: https://www.virtualbox.org/ticket/181

So, back in march 2007, ""Frank"" decided that is was ""wontfix"".

I am trying to use VoIP solutions (SIP), asterisk, etc but I would prefer to use a VM box and use NAT for this. I am experiencing dificulties that I believe are due to those sw using inside ICMP, so, no ICMP no working...

TIA",caspertone2003
19479,Unable to create Host-Only Network on Virtual Box,Windows,other,VirtualBox 6.1.4,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
19480,VirtualBox freezes when Windows 7/10 guests reboot/reset after restoring online snapshots if GA is installed,Linux,Windows,VirtualBox 6.1.4,2020-04-12T07:20:54Z,2020-04-12T07:20:54Z,"Host information:

- Arch Linux
- linux 5.6.3.arch1-1
- virtualbox 6.1.4-6
- virtualbox-guest-iso 6.1.4-1

Guest Information (both are reproducible)

- Windows 7 SP1
- Windows 10 LTSC 2019, Build Number 17763.1131

Steps to reproduce:

1. Cold boot the guest VM;
2. Take a online snapshot ""Snapshot 1"";
3. Shutdown the machine and restore to ""Snapshot 1"";
4. Boot the guest VM from ""Snapshot 1"" (directly into the Windows desktop);
5. Reboot/Reset the guest VM;
6. The VM resets, and shows a brief Windows Vista-style loading progress bar, and the VirtualBox (on host machine) freezes before crashing.

Notes:

- I have tried Windows 7 and Windows 10 guests (as decribed above), both are reproducible.
- If Guest Addition is not installed / uninstalled, the bug does not occur.
- If guest VM is cold booted (e.g. after step 4, instead of resetting/rebooting it, just shutdown and boot it), the bug does not occur.

Side note (may not relate to this bug):

After VB freezes/crashes, the RAM for guest VM is simply ""taken away"" from the host and cannot be recovered without a reboot of the host -- My host has 32 GB RAM, and each time a guest with 4 GB RAM crashes, there are 4 GB of RAM taken away from the host. After 7 crashes, 28 GB RAM are taken away from the host. I tried to shutdown Xorg server and there are only a few running processes left (none of them are VirtualBox), the host system still reports there are ~30 GB RAM used (top, htop, free... not cache/buffer, just ""used""). I have to reboot the host system to recover the RAM.",wzyboy
19429,VirtualBox 6.1 + Whonix 15 = Aborted,Linux,Linux,VirtualBox 6.1.4,2020-04-12T14:15:03Z,2020-04-12T14:15:03Z,"Hello everyone! I have been using Whonix 14 for a long time and everything have been working fine but unfortunately I need some soft as libreoffice which I can't download there because Whonix 14 isn't supported. I had to upgrade it. I should note that I used VirtualBox 5.3 with Whonix 14. I decided to make new one from scratch. Downloaded Whonix 15 and import it. I faced with the problem that clipboard didn't work. I decided download new version of VirtulBox = 6.1 This is solved the problem with clipboard but I faced with the bigger problem instead . Now after some time (different time ) VM just close without any reason and in main window of virtulbox I see the title ""Aborted"" . I have several VMs (Whonix 15, Whonix 15, Whonix 14) which usually work together (multiply workstation) and what is strange that one of them work normal (whonix 15) but the other two often crash together in one time. The difference between two whonix 15 is that in one installed psi+ v0.16 . I paid attention to version on psi+ special because it's the version for jessie, some plugins in it work better than in new one. Maybe is that the reason? One more thing I want to note is that I am not cloned first Workstation 15 when I made second Workstation 15 , I just imported all machines again from OVA and then delete second gateway which I didn't need , leaving the second workstation 15.

Info about host

System:    Host: user Kernel: 4.15.0-91-generic x86_64 bits: 64 gcc: 7.4.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) dm: lightdm Distro: Linux Mint 19 Tara
CPU:       Quad core Intel Core i7-8550U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15936
           clock speeds: min/max: 400/4000 MHz 1: 1900 MHz 2: 1900 MHz 3: 1900 MHz 4: 1900 MHz
           5: 1900 MHz 6: 1900 MHz 7: 1900 MHz 8: 1900 MHz
Graphics:  Card-1: Intel UHD Graphics 620 bus-ID: 00:02.0 chip-ID: 8086:5917
           Card-2: NVIDIA GP108M [GeForce MX150] bus-ID: 01:00.0 chip-ID: 10de:1d12
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nouveau (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.05hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
           version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d71
           Sound: Advanced Linux Sound Architecture v: k4.15.0-91-generic
Partition: ID-1: / size: 901G used: 452G (53%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 705M used: 368M (57%) fs: ext4 dev: /dev/nvme0n1p2
           ID-3: swap-1 size: 17.02GB used: 0.70GB (4%) fs: swap dev: /dev/dm-3",CatJump
19483,[CRITICAL] Windows XP VM Won’t Start,Windows,Windows,VirtualBox 6.1.4,2020-04-13T04:49:42Z,2020-04-13T04:49:42Z,"I was not able to attach a log file for this; the log is empty. Let me describe the issue.
When I make a new VM with Windows XP on it, with sufficient RAM, CPU, Disk, and the correct ISO, it says invalid settings detected. I hover over it and it leads me to System/Acceleration and it tells me to uncheck Hardware Virtualisation. Fair enough, I toggle it off. The invalid settings error persists at the same place. Here are my specs:

Windows 7 Home Premium SP 1 Build 7601
Lenovo Ideapad 2010 (x64 based)
Intel Core i5 CPU, M480 @ 2.67 GHz, 2667 MHz, 2 Cores
BIOS Version LENOVO 29CN35WW(V2.12), 8/12/2010
SMBIOS Version 2.6
8 GB RAM

I am also on the latest stable version, 6.1.4r136177 (Qt5.6.2)


",Asquenn
13884,Keys repeat in guest VM (Windows 7 Pro 32 bit OS),Windows,other,VirtualBox 4.3.22,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
19484,Reacting to host shutdown,Windows,Windows,VirtualBox 6.1.4,2020-04-13T16:39:11Z,2020-04-13T16:39:11Z,"1. run Windows 10x64 virtual machine in Windows 10x64 host
2. in host Windows session, start Notepad and type something
3. in host Windows session, initiate shutdown
4. observe the message ""these applications prevent shutdown"" - showing Notepad
5. press ""cancel"" thus terminating the shutdown of the host
6. observe what happens to the virtual machine:

- error message ""failed to pause the execution of the virtual machine""
Callee RC: 
RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
- the console of the virtual machine remains connected and showing the desktop, but it's not working anymore

open VirtualBox Manager, and check the status of the virtual machine - it's ""aborted""

What was expected: if virtual machine was reacting to the host shutdown, it probably should have either shut down itself, or gracefully terminated; there should be no attempt to pause (which failed); the GUI probably should disappear -  rather than stayed on the screen while being non-operational.


",vad
19486,virtual disk name extention is added to perious extension,Linux,Windows,VirtualBox 6.1.4,2020-04-14T09:47:24Z,2020-04-14T09:47:24Z,"VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.9.5)

Ubuntu 18.04.4 LTS

1. Start to create new virtual machine in expert mode.
2. Reach the step of creation virtual disk.
3. Change multiple times file type of the disk. And notice to its extension.

Expected: replacement of current extension to new extension.
Real behavior: new file extension is added to the end of full file name. We have multiply exensions.",Marat-sh
19487,macOS 10.15.4 - VM hang if allocated more than 6 CPU or > 32Gb of memory,Mac OS X,OSX Server,VirtualBox 6.1.4,2020-04-14T13:57:49Z,2020-04-14T13:57:49Z,Installed VirtualBox 6.1.4 and extensions on MacOS Catalina 10.15.4. Created VM through vagrant (macinbox) or via ISO and VM will hang if 32Gb or more memory allocated to VM or if 6 logical cores (out of 12 on a 6 physical core MacMini 2018) are allocated to VM. Never starts boot of machine past initial EFI startup. Reducing to 32700Mb or 6 cores and the machine starts up successfully.,nycnewman
19488,Trying to start a new instance of Ubuntu Server,Linux,Linux,VirtualBox 6.1.4,2020-04-14T16:31:10Z,2020-04-14T16:31:10Z,"00:00:34.744960 GIM: KVM: Resetting MSRs
00:00:34.748351 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:34.756082 Console: Machine state changed to 'PoweredOff'
00:00:35.281071 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:00:35.757520 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:35.757592 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:35.757701 GUI: Aborting startup due to invalid machine state detected: 1",larka06
19489,UI garbled when run through SSH,Linux,other,VirtualBox 6.1.4,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
17086,Webcam crash in Ubuntu 16.0.4 and VirtualBox 5.1.28 running Android-x86,other,Linux,VirtualBox 5.1.28,2020-04-15T15:10:37Z,2020-04-15T15:10:37Z,"I've created a VM with Android 6.0-r3 from www.android-x86.org using VirtualBox 5.1.28 and Ubuntu 16.04 LTS. The VM works great, but every time I try to use a fake webcam it crashes.

Basically if in the host I perform:

# After installing v4l2loopback-dkms
modprobe v4l2loopback
# Init the video stream (/tmp/i.png can be any image and /dev/video0 is the loopback device that can have a different number if you have other connected webcams)
while [ 42 ]; do cat /tmp/i.png ; done | ffmpeg -y -i - -f image2pipe -r 15 -s 1920x1080 -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0

=> Run the VM and manually stop at the GRUB boot loader
=> Assign the webcam to the machine (Devices => Webcams => Dummy Video Device)
=> Continue to boot the machine

(the steps above are important, otherwise Android will not recognize the webcam)

=> Run some camera app, I use Open Camera from https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en

=> The APP should show the image
=> Just try to leave the APP

=> The VM will crash and if you run the 'dmesg' command, it will appear something like

[202894.416980] HWCMONITOR[14932]: segfault at 7f5554b17800 ip 00007f55dc0beb35 sp 00007f55b017bb80 error 4 in VBoxHostWebcam.so[7f55dc0b8000+3a000]",aliedis87.rhyta
19461,App Error - Instruction at ... referenced memory at...,Windows,Linux,VirtualBox 6.1.4,2020-04-15T20:03:18Z,2020-04-15T20:03:18Z,"I am using Linux guest on Windows 10 host. Inside of my guest when I use some Chrome based apps: Chrome, Vivaldi, Electron apps like VSCode, after few minutes of using them I get such an error:  Instruction at ... referenced memory at.... The memory could not be written. VBox then crashes. I'm attaching screenshot and VBox log file.
",Macio
19497,Feture request: minimize the virtualbox machine window when the guest OS powers off its virtual screen,Linux,Linux,VirtualBox 6.0.14,2020-04-16T01:53:18Z,2020-04-16T01:53:18Z,"Hello,

my guest ubuntu OS always keeps saying (in the background) that it's unable to lock screen while I have a virtualbox machine in the foreground. Well in a way that is a feature I understand, but also as it hinders security (host OS is not locking when there's no keyboard and no mouse activity and a virtualbox guest is in the foreground) it is an antifeature as well. As a solution which would make this a feature without any drawbacks I suggest you to minimize the guest OS window (or otherwise prevent it preventing the host OS to lock) when the guest OS blanks or powers off its virtual screen. Maybe you can add a configuration option for this as well, but maybe as until today there were no use to powering off/blanking the virtual screen this feature might be OK without any configuration option as well.

Thank you in advance.

Imre",Imre84
19491,have errors showing up trying to get into macOS Catalina,Windows,OSX Server,VirtualBox 6.1.4,2020-04-16T09:49:23Z,2020-04-16T09:49:23Z,This is the first time I am trying to get into Catalina from my windows 10-64 bit environment.  I have tried several times but I am getting error codes.as shown.  ,esams2
19498,vbox 6.1.2 vboxnetdhcp process blocks the update to vbox 6.1.6,Windows,all,VirtualBox 6.1.6,2020-04-16T11:01:53Z,2020-04-16T11:01:53Z,you need to close vbox 6.1.2 and REBOOT your (windows 10) pc before installing / updating to vbox 6.1.6,clive darra
19500,VirtualBox should now prohibit assigning all physical CPUs to a VM and/or fix VirtualBox CPU assignment manual,all,other,,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
19501,"Hello, good mornning from Mexico",Windows,Windows,VirtualBox 6.1.6,2020-04-16T16:10:30Z,2020-04-16T16:10:30Z,"I tryed to start a virtual machine and a message error, into that mesage apears a note:try reinstalling the software, I tryed with versions, 5,2, 5,5, 6.1 and it is the same case
message:
The virtual machine 'RTCW' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\mgocc\VirtualBox VMs\RTCW\Logs\VBoxHardening.log'.",Pipen13
19502,VM cannot start if network adapter has a trailing space(s) in FriendlyName,Windows,all,VirtualBox 6.1.6,2020-04-16T22:51:34Z,2020-04-16T22:51:34Z,"For some reasons my VM's with all kind of guest OS (Ubuntu, Windows, FreeBSD) suddenly refused to start with error ""Cannot start a VM because Network adapter <...> not found. You can shutdown or ..."". Name of adapter in dropdown list matched those in Windows network adapter properties.[[BR]]

After digging in debug logs I mentioned this -[[BR]]
 
@log Vbox.log.2:[[BR]]
============================[[BR]]
00:00:16.458034 AssertLogRel F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5274) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): <NULL>[[BR]]
00:00:16.458076 NetworkAttachmentType_Bridged: FindByName failed, rc=E_INVALIDARG (0x80070057)VMSetError: F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5275) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool); rc=VERR_INTERNAL_ERROR[[BR]]
00:00:16.458174 VMSetError: Nonexistent host networking interface, name ''''NVIDIA nForce 10/100 Mbps Ethernet''''[[BR]]
00:00:16.459027 Constructor failed with rc=VERR_INTERNAL_ERROR pfnCFGMConstructor=000007fef02e0b00[[BR]]
00:00:16.459846 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Nonexistent host networking interface, name 'NVIDIA nForce 10/100 Mbps Ethernet' (VERR_INTERNAL_ERROR)}, preserve=false aResultDetail=-225[[BR]]
00:00:16.460104 Console: Machine state changed to 'PoweredOff'[[BR]]
=============================[[BR]]
@Vbox.log[[BR]]
00:00:03.619271 [/Devices/e1000/1/LUN#0/Config/] (level 5)[[BR]]
00:00:03.619273   IfPolicyPromisc      <string>  = ""deny"" (cb=5)[[BR]]
00:00:03.619274   IgnoreConnectFailure <integer> = 0x0000000000000000 (0)[[BR]]
00:00:03.619275   Network              <string>  = '''""HostInterfaceNetworking-NVIDIA nForce 10/100 Mbps Ethernet ""''' (cb=60)[[BR]]
00:00:03.619276   Trunk                <string>  = ""\DEVICE\{77FEAE02-6B93-4633-B53D-9B670059780A}"" (cb=47)[[BR]]
00:00:03.619277   TrunkType            <integer> = 0x0000000000000003 (3)[[BR]]
=============================[[BR]]
Registry key at[[BR]]
""\\\Registry\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_03EF&SUBSYS_03EF1849&REV_A2\3&267a616a&0&38\FriendlyName"" was '''""NVIDIA nForce 10/100 Mbps Ethernet ""'''[[BR]]
=============================[[BR]]
So I suggest that somewhere in VBox's code trailing (and maybe leading) spaces in  the adapter's name are trimmed, causing further mismatch.[[BR]]
After I changed registry key (deleted trailing space character) all my VM's started perfectly, as before.

",Dyno_bel
17828,Can't move media due to out of memory errors,other,other,VirtualBox 5.2.12,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
17524,Various VBox binaries use a SHA1-timestamped SHA2 signature,other,other,VirtualBox 5.2.6,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
19504,I'm not able to start a headless virtualmachine,Mac OS X,other,VirtualBox 6.1.6,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
19507,Shared folders in Guest OS (Windows 10) also occupy unused drive letters,Windows,Windows,VirtualBox 6.1.6,2020-04-17T17:11:36Z,2020-04-17T17:11:36Z,"Drive letters are occupied even if they are not assigned in Windows 20 Guest OS! The Shared Folder are correctly connected to the designated drive letters in the Guest OS. Unfortunately, the other drive letters are also occupied. This leads for example to problems with other NAS SHARES that should be connected to drive letters. (Letters are occupied!!). 
The problem does not exist in the same environment with Virtualbox 5.2.40.

Shared Folder - Host OS Windows 10 (Build 1909) - Guest OS Windows 10 (Build 1909).  ",RonaldMcDonald
19385,Start Menu on Windows 10 LTSC becomes broken after some time,Windows,Windows,VirtualBox 6.1.4,2020-04-20T07:49:47Z,2020-04-20T07:49:47Z,"I am using Microsoft Windows 10 1809 LTSC MSDN version, and after some time, the start menu becomes broken, as in the screenshot, it blinks and does not show the headers",astverskoy
19517,Support Sparkle application update framework on macOS,Mac OS X,other,VirtualBox 6.1.6,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
19519,Add CloneVDI features to VirtualBox itself,other,other,VirtualBox 6.1.6,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
8970,Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION),Windows,Windows,VirtualBox 4.0.8,2020-04-20T18:13:29Z,2020-04-20T18:13:29Z,"Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION)

occurs in v4.08

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

thank you,
art",art
19520,Can’t boot Windows VM on macOS 10.15.3,Mac OS X,Windows,VirtualBox 6.1.6,2020-04-21T09:11:48Z,2020-04-21T09:11:48Z,"Hello,

Recently upgraded my Hackintosh from Mojave to Catalina, and now I can’t boot a Windows VM (Linux ones may have problems too but I haven’t tested extensively). Parallels Desktop works fine

When booting the latest live CD downloaded from Microsoft’s website, I first get this error (on a brand new VM):
“File: \windows\System32\drivers\nvraid.sys
Error code: 0xc0000098”
Then I press enter and get this one:
“File: \windows\System32\drivers\iaStorV.sys
Error code: 0xc0000221”

It seems that a few weeks ago when I tried (VirtualBox 6.1.4), it did the same thing with same error codes but with different file names. I attach the screenshots and log file.

Thanks!",GilDev
19514,Win 10 x64 guest setup hangs on Win 7 x64 host if CPU count > 1,Windows,Windows,VirtualBox 5.2.40,2020-04-21T14:19:46Z,2020-04-21T14:19:46Z,"If CPU count is more than one Windows 10 x64 guest hangs during setup on Windows 7 x64 host, while Windows 10 x32 and Windows 7 x64 guests are running fine. If CPU count is one Windows 10 x64 guest is running fine too. Problem exists regardless of chipset is ICH9 or PIIX3, EFI is enabled or disabled. Versions 5.2.38.136252, 6.0.18.136238 and 6.1.4.136177 are also affected.

Related tickets: #19352 (?), #18856, #15529.",Researcher
19522,VirtualBox does not recognize Windows 10 taskbar on the side,Windows,Linux,VirtualBox 6.1.6,2020-04-22T10:11:56Z,2020-04-22T10:11:56Z,"I am using VirtualBox 6.1.6 on a Windows 10 host with Ubuntu 18.04.4 LTS as guest OS. I have installed the latest guest additions and am using the VMSVGA gfx driver. I am using a side-by-side dual monitor setup which is extended in Windows.

My windows taskbar is placed on the left, respectively right side for each monitor, effectively reducing the available width for maximized windows.

Since switching from 6.0.x I have the following issue:
My guest OS windows will show scrollbars to view the full screen rather than scaling the viewport down to fit into the window. I am using maximized guest os windows with the ""auto-resize gust display"" function enabled. I have switched off the display of menu or statusbars.

When moving the windows taskbar to the bottom of my host system, all scrollbars disappear.



",chross
4605,Ubuntu Linux guest audio output slow and distorted,Windows,Linux,VirtualBox 3.0.2,2020-04-22T17:03:35Z,2020-04-22T17:03:35Z,"There's some discussion in community forums related to this, but it doesn't go very far.  Couldn't find any similar report in Bugtracker.  Sorry if I overlooked.

This is an Ubuntu Linux 9.0.4 guest in Virtualbox 3.0.2 r49928 on a Vista SP1 host, a Presario C751 notebook.  Following initial installation of the guest, sound playback works well.  Only after shutting down the VM completely and then restarting will sound playback slow down with a commensurate lowering of pitch as though the clock is running slow.  Sound distortion such as ""chirping"" and stuttering may be evident as well.  The problem is temporarily repaired by reinstalling the Guest Additions and rebooting the VM (reboot only, don't shut it down!).  Having done that, audio playback is restored to normal and will remain normal between reboots of the VM.  Only after the VM is shut down will the problem recur.  The same problem occurred in V 2.2.4 r47978.  FWIW Video output seems to be affected as well.

A Windows XP SP3 guest does not seem to exhibit the same problem.

Using a VM for multimedia apps is silly, but what's amazing is how well it works when it works.  It's not the way to go, but even if you don't, Ubuntu, for example, makes sounds like the drumbeat figure when GDM is ready for login, the Ubuntu ""theme"" as GNOME comes up and other sounds such as error notifications and the like and it is irritating for them to be slow, off pitch and distorted.  More importantly, the fact that it sometimes works and sometimes doesn't implies an underlying problem that may be more significant.

If I can, I will dissect the Guest Additions installation and try to determine what seems to ""fix"" the problem.",Larry Shurr
18640,xoBV tag memory leak,other,other,VirtualBox 6.0.6,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
16466,VB 5.1.14 (linux host / win7 guest) fails concurrent audio/video input from integrated USB device (Logitech C920 webcam); separate devices work OK,Linux,Windows,VirtualBox 5.1.14,2020-04-23T20:46:18Z,2020-04-23T20:46:18Z,"I've a desktop with VB 5.1.14 installed
{{{
	VBoxManage --version
		5.1.14r112924
}}}
and running
{{{
	VBoxManage list runningvms
		""Win7_64"" {71...e9}
}}}
on linux/64 host
{{{
	VBoxManage list hostinfo
		Host Information:

		Host time: 2017-02-08T15:13:41.459000000Z
		Processor online count: 4
		Processor count: 4
		Processor online core count: 4
		Processor core count: 4
		Processor supports HW virtualization: yes
		Processor supports PAE: yes
		Processor supports long mode: yes
		Processor supports nested paging: yes
		Processor#0 speed: 3010 MHz
		Processor#0 description: AMD Phenom(tm) II X4 945 Processor
		Processor#1 speed: 3010 MHz
		Processor#1 description: AMD Phenom(tm) II X4 945 Processor
		Processor#2 speed: 3010 MHz
		Processor#2 description: AMD Phenom(tm) II X4 945 Processor
		Processor#3 speed: 3010 MHz
		Processor#3 description: AMD Phenom(tm) II X4 945 Processor
		Memory size: 16030 MByte
		Memory available: 2423 MByte
		Operating system: Linux
		Operating system version: 4.9.8-2.gaf90696-default
}}}
with up-to-date extpack installed
{{{
	VBoxManage list extpacks
		Extension Packs: 1
		Pack no. 0:   Oracle VM VirtualBox Extension Pack
		Version:      5.1.14
		Revision:     112924
		Edition:
		Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk
		VRDE Module:  VBoxVRDP
		Usable:       true
		Why unusable:
}}}
The host runs PulseAudio.

I have two devices attached and functional in the host, an integrated (audio + video) webcam, and a standalone microphone
{{{
	lsusb | egrep -i ""Logitech|Telex""
		Bus 001 Device 011: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
		Bus 001 Device 010: ID 0562:0002 Telex Communications, Inc. Telex Microphone

	hwinfo --usb
		...
		11: USB 00.1: 0000 Unclassified device
		  [Created at usb.122]
		  Unique ID: xnLL.dxozCEIXKDA
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4/1-4:1.1
		  SysFS BusID: 1-4:1.1
		  Hardware Class: unknown
		  Model: ""Logitech HD Pro Webcam C920""
		  Hotplug: USB
		  Vendor: usb 0x046d ""Logitech, Inc.""
		  Device: usb 0x082d ""HD Pro Webcam C920""
		  Revision: ""0.11""
		  Serial ID: ""60F274DF""
		  Driver: ""uvcvideo""
		  Driver Modules: ""uvcvideo""
		  Speed: 480 Mbps
		  Module Alias: ""usb:v046Dp082Dd0011dcEFdsc02dp01ic0Eisc02ip00in01""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)

		12: USB 00.0: 0401 Multimedia audio controller
		  [Created at usb.122]
		  Unique ID: cLrx.qTkEoUPZciD
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2/1-2:1.0
		  SysFS BusID: 1-2:1.0
		  Hardware Class: sound
		  Model: ""Telex Microphone""
		  Hotplug: USB
		  Vendor: usb 0x0562 ""Telex Communications, Inc.""
		  Device: usb 0x0002 ""Telex Microphone""
		  Revision: ""1.00""
		  Serial ID: ""XXXXX""
		  Driver: ""snd-usb-audio""
		  Driver Modules: ""snd_usb_audio""
		  Speed: 12 Mbps
		  Module Alias: ""usb:v0562p0002d0100dc00dsc00dp00ic01isc01ip00in00""
		  Driver Info #0:
		    Driver Status: snd_usb_audio is active
		    Driver Activation Cmd: ""modprobe snd_usb_audio""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)
		...
}}}
In the host, under PulseAudio routing, the webcam &/or the standalone mic can be used by linux native apps separately &/or concurrently.  No issues.

In VB, Audio settings are set to
{{{
	Audio
		HostDriver: PulseAudio
		Constroller: Intel HD Audio
}}}
The VM sees the mic & webcam on the host as
{{{
	VBoxManage list usbhost
		...
		UUID:               24651a23-221b-45e4-bddf-00bbfc1ce03a
		VendorId:           0x0562 (0562)
		ProductId:          0x0002 (0002)
		Revision:           1.0 (0100)
		Port:               1
		USB version/speed:  1/Full
		Manufacturer:       Telex Communications, Inc.
		Product:            Telex USB microphone
		SerialNumber:       XXXXX
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2//device:/dev/vboxusb/001/010
		Current State:      Captured
		...
		UUID:               272cd013-38e7-4515-af01-9c8f2aebbbd0
		VendorId:           0x046d (046D)
		ProductId:          0x082d (082D)
		Revision:           0.17 (0017)
		Port:               3
		USB version/speed:  2/High
		Manufacturer:       Logitech, Inc.
		Product:            HD Pro Webcam C920
		SerialNumber:       60F274DF
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4//device:/dev/vboxusb/001/011
		Current State:      Busy
}}}
The VM runs Win7/64 with SP1 + latest ConvenienceRollup & all updates.


I'm attempting to get the VM to use ONLY the Logitech C920, for BOTH audio / video input source.

'''[CASE_1]'''

device selection state @ VM 'Devices'
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
@ Microsoft Setup Wizard

there is NO detected audio input at all.


'''[CASE_2]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[X] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the Telex.

and, testing further, 'separate device' audio & video work
{{{
	WebCam video INPUT from the C920      ---> WORKS
	MIC    audio INPUT from the Telex     ---> WORKS
}}}
So, this is a working config for , e.g., WebEx use in the VM

'''[CASE_3]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[X] Logitech, Inc. HD Pro Webcam C920 [0011]
}}}
automatically forces the change
{{{
		Webcams
			No WebCams detected
}}}
In this config

MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the C920.

but there is NO detected/usable video input.",PGNd
19526,'vboxmanage list runningvms' FAILs to list running VMs,Linux,Linux,VirtualBox 6.1.6,2020-04-25T10:58:06Z,2020-04-25T10:58:06Z,"noting this similar symptom, from a still open issue

	""vboxmanage list runningvms does not list anything""
	https://www.virtualbox.org/ticket/6808#propertyform
		Opened 10 years ago[[BR]]
		Last modified 4 years ago

has that been fixed/addressed elsewhere?

here, running latest VB release
{{{
	VBoxManage --version
		6.1.6r137129
}}}

on host,
{{{
	lsb_release -rd
		Description:    openSUSE Leap 15.1
		Release:        15.1
}}}

checking available vms, correctly returns
{{{
	> VBoxManage list vms
		""Debian_Stable"" {...}
		""Win10_Pro"" {...}
		""openSUSE_Leap"" {...}
	>
}}}

if i launch a guest, e.g.
{{{
	""openSUSE_Leap""
}}}

is, atm, up & running ... and accessible,
{{{
	ps ax | grep vir
		24799 ?        Sl     0:16 /usr/lib/virtualbox/VirtualBox
		24816 ?        S      0:08 /usr/lib/virtualbox/VBoxXPCOMIPCD
		24822 ?        Sl     0:19 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
		40167 ?        Sl     0:27 /usr/lib/virtualbox/VirtualBoxVM --comment openSUSE_Leap --startvm ... --no-startvm-errormsgbox
		40176 ?        S      0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
		40182 ?        Sl     0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

but checking RUNNING vms, still (again?) returns blank
{{{
	> VBoxManage list runningvms
	> 
}}}",pgnd
19438,Resize Screen crashes Everything,Windows,Linux,VirtualBox 6.1.4,2020-04-25T14:41:27Z,2020-04-25T14:41:27Z,"I am using Windows 10, VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.6.2)
 with an Ubuntu 18.04 LTS guest. Once the guest is installed and rebooted, resizing the screen in windows can lock the VM, and eventually the whole PC. 

Steps to reproduce resize the screen and before the guest is refreshed add a little more screen. Different kinds of hangs but the VM guest is always hung. Sometimes VBox host hangs also.",jerry ely
19534,Adding USB devices has useless serial number,other,other,VirtualBox 6.1.6,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
19536,"Problems when switching from ""NAT"" to ""Bridge"" and vice versa. VM is not assigned an IP address via DHCP when using ""Bridge"".",Windows,Windows,VirtualBox 5.2.40,2020-04-26T14:19:17Z,2020-04-26T14:19:17Z,"Host is a Windows 10 (Build 1909). If you change in Virtualbox 5.2.40 with a VM (Windows 10 (Build 1909) in the network area from ""NAT"" to ""Bridge"" the VM does not get a new IP address via DHCP within the VM. 
With Virtualbox 5.2.38 it works with the same host and with the same VMs without problems online. You can switch between ""NAT"" and ""Bridge"" and the VM gets an IP address internally via its DHCP service. This can also be observed in the DHCP server of the network.  

The error is reproducible and occurs immediately after installing Virtualbox 5.2.40 and disappears as soon as Virtualbox 5.2.38 is installed again.",RonaldMcDonald
19529,[feature-request] Making linux setup of shared folder more user-friendly,all,Linux,VirtualBox 6.1.6,2020-04-27T11:03:18Z,2020-04-27T11:03:18Z,"To use VB shared folders, the user in the guest Linux OS needs to be a member of the vboxsf group.

This makes configuration cumbersome, especially for not too tech savvy people who use VB to discover Linux.

It would be much easier if the VBoxLinux.run script would offer to add the current user to that group (thanks to the SUDO_USER environment variable) and hint that a logout/login cycle is needed for it to take effect.",YannSalmon
4290,Can't create hard links on a shared folder (= can't use zsh if home directory is shared folder),all,Linux,VirtualBox 2.2.4,2020-04-28T09:59:37Z,2020-04-28T09:59:37Z,"It seems the shared folders do not allow hard links to be created (link() system call). The result is always EPERM, Operation not permitted. A simple ""touch foo; ln foo bar"" on a shared folder will demonstrate the problem. This is with VirtualBox 2.2.4 on Mac OS X 10.4.11 host, Linux 64-bit client (tried both Ubuntu 8.04 LTS Server x86-64 and Scientific Linux 4.8 x86-64 (a RHEL4 variant)).

The way I actually noticed was that the zsh delivered with scientific linux (zsh 4.2.0) tries to create a history lock file with link() and fails - and goes into an infinite loop. There's no such problem with the ubuntu version though (zsh 4.3.4). This makes it rather more difficult to use zsh as a login shell :-) I'll see if I can coax it to not use that way of locking.

However, hard linking support would be nice.",lat
19541,Poor disk write performance for fully allocated sparse-extent VMDKs,all,other,VirtualBox 6.1.6,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
19540,CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host),Mac OS X,Linux,VirtualBox 6.1.6,2020-04-29T02:07:12Z,2020-04-29T02:07:12Z,"Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.",dmnorth
19542,WinVerifyTrust failed to start virtualbox 5.x.x,other,other,VirtualBox 5.2.40,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
19543,WinVerifyTrust failed to start virtualbox 5.x.x,other,other,VirtualBox 5.2.40,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
19392,VMSVGA and FHD on 6.1.4,other,Linux,VirtualBox 6.1.4,2020-04-30T08:21:25Z,2020-04-30T08:21:25Z,"Since 6.1 I switched from VboxSVGA to VMSVGA.[[BR]]My guest display, as the host, was set to 1920x1080.[[BR]]

After the switch I've lost the ability to use that resolution but I've found these commands as workaround:[[BR]]
''
VBoxManage.exe setextradata <VMName> CustomVideoMode1 1920x1080x32[[BR]]
VBoxManage controlvm <VMName> setvideomodehint 1920 1080 32''

After upgrading to 6.1.4 the resolution was still available, __but after installing the guest addition at the same version__ and rebooting it disappeared from the available resolutions.[[BR]]I tried using the same commands as above but with no success. 

Only after downgrading to 6.1.2, reinstalling guest additions 6.1.2 and rebooting my desktop loaded at 1920x1080 and the resolution was available again.

Host: Windows 10[[BR]]Guest: Oracle Linux Server release 6.10 (running 4.1.12-124.37.1.el6uek.x86_64 and fully updated)
",alealeale
19544,Inability to run 6.0-6.1.7 upgrading to 6.1.6,Windows,all,VirtualBox 6.1.6,2020-05-01T01:31:45Z,2020-05-01T01:31:45Z,"After upgrading recently I am unable to launch vbox. The following error occurs on 6.1.6 and 6.1.7 (test). I tried rolling back versions and can successfully run 5.2.40 and lower. As soon as I cross  into 6.0+ the error occurs. The VBoxSDS doesn't seem to want to run and no files are written to the .VirtualBox directory on 6.0+. I did have 6.1.x installed and running before upgrading to 6.1.6 but I do not remember which version specifically. 


'''Failed to acquire the VirtualBox COM object.'''

The application will now terminate.

Completely failed to instantiate CLSID_VirtualBox: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D.

Result Code: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D (0x8007041D)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}


I have tried:
1. Admin rights
2. Removing .VirtualBox directory
3. Cleaning registry
4. Comparability modes: Admin and older windows versions
5. Recover .VirtualBox files from backup
6. Update and verify all drivers
7. Remove all antivirus including defender
8. Hyper-V and VMware can run and have been removed
9. Extend service timeout length despite this being an immediate failure
10. Run bug report: WARNING: Failed to create the VirtualBox object (hr=0x8007041d)


Can provide bug report info if needed.",IamUSER
19539,CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host),Mac OS X,Linux,VirtualBox 6.1.6,2020-05-01T17:05:04Z,2020-05-01T17:05:04Z,"Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.",dmnorth
19547,Three crashes of VirtualBoxVM in a row when trying to boot an Ubuntu 18.04 guest on a macOS 10.14.6 host,Mac OS X,Linux,VirtualBox 6.1.6,2020-05-02T11:29:01Z,2020-05-02T11:29:01Z,"Hi,

I've got three crashes of VirtualBoxVM in a row when trying to boot an Ubuntu 18.04 guest on a macOS 10.14.6 host. See attached crash logs and VBox.logs",Lars Sonchocky-Helldorf
19548,VirtualBox freeze guest Ubuntu 18.04 if i add bridge or vlan,Windows,Linux,VirtualBox 6.1.6,2020-05-02T14:49:17Z,2020-05-02T14:49:17Z,"host VirtualBox 6.1.6 r137129 (on windows 8 x64), guest Ubuntu 18.04 LTS HWE kernel 5.3.0-51-104generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 GNU/Linux, host have 1 ethernet interface directly connected to standalone d-link router with cable, guest have 3 nic's, 1 nat, 2 internal network, 3 brdiged-adapter. 

problem with manage bridge or vlan on guest, if i add manualy interface to bridge or configure vlan, after execute command - guest(ubuntu) freeze, do manual reboot.. example:

#bridge  
modprobe bridge
brctl addbr br0 #(all is ok)
brctl addif br0 bond0 #(all is ok)
brctl addif enp0s3 #(freeze) (tests enp0s3 as NAT, enp0s8 as Lan and enp0s9 as Bridged-adapter)

doesn't matter enp0s3/8/9 up or down before add to bridge, with IP address or without it..

#vlan
apt install vlan
modprobe 8021q
vconfig add enp0s3 100 
added VLAN with VID == 100 to IF -:enp0s3:-
(freeze)

maybe this a problem with my ubuntu in wrong network configuration or with kernel, I ask your help to make it all work :)",Deloris
19549,Problems in restoring VM window size from saved states,Windows,Windows,VirtualBox 6.1.6,2020-05-02T15:56:59Z,2020-05-02T15:56:59Z,"Since upgrading to VBox 6.1.x (Win10 64)I noticed that the program frequently fails in correctly restoring the VM window size (especially if non maximized) when starting a VM from a saved state.

The VM starts normally (although with much less precision in the progress indicator, also since VBox 6.1x) but the VM window, after flashing for a moment at the saved size, shrinks to 640x480 and has to be manually resized, while obviously all the guest's desktop icons get rearranged and any open program windows gets shrunk as well.
This doesn't happen always but often (on an apparently random basis) and never happened, as far as I remember, with previous releases. I couldn't yet spot any clear and reproducible cause.

This is not a major problem, obviously.
However it actually IS some kind of malfunction.
At first I thought it could be just a momentary little regression in the new major update, but since it's still there in the latest 6.1.6 I thought I'd report it here too.",Armando
19552,NAT Network is not working when I try to create or edit  a different IP other than (10.0.2.0)),Windows,Windows,VirtualBox 6.1.6,2020-05-04T09:19:43Z,2020-05-04T09:19:43Z,"Virtualbox  version 6.1.6

This version has issues when trying to ping internet using NAT network.
there is no pin and cannot access the internet.

the problem is not in the default NAT network created by virtualbox 10.0.2.0/24.

the problem appears when i configure a new NAT network or edit the default one, like for example 192.168.0.0/24 in this case it will not work and can not access the internet.

I tested the following versions 6.0.20, 6.0.18, 6.0.12 and all of them work fine with no problems. 

 ",hassanmonji
19563,A critical error has been occurred while running virtual machine and the machine execution has stopped,other,other,VirtualBox 6.1.6,2020-05-06T01:53:56Z,2020-05-06T01:53:56Z,"I have the following error:
""A critical error has occurred while running the virtual machine and the machine execution has been stopped"".

After running Kali Linux 2020.1 a couple of minutes after installation, I restarted the machine and then this error keeps popping up.

Please see the attachment please and also the log.

VBox.log.2[https://gofile.io/?c=rbENBU]

[[Image(https://i.ibb.co/88z8QL4/kali.png)]]


",Ehsanul
19566,A critical error has occurred while running a virtual Machine,other,Windows,VirtualBox 6.1.4,2020-05-06T12:01:07Z,2020-05-06T12:01:07Z,,Kathir
19569,The virtual machine 'XXX has terminated unexpectedly during startup with exit code 1,Windows,all,,2020-05-07T07:52:54Z,2020-05-07T07:52:54Z,"I upgraded to VirtualBox 6.1.7r137622 to escape the bug https://www.virtualbox.org/ticket/19496.
Now, all my VM doesn't start : I have the message bellow.
[[Image(https://i.postimg.cc/nVwkVjK4/supR3.png)]]
",Vbox43532
19533,wacom clicks not registered in virtualbox manager window,Linux,Linux,VirtualBox 6.1.6,2020-05-07T16:12:20Z,2020-05-07T16:12:20Z,"Tested with virtualbox 6.1.6 on Ubuntu 20.04 and separately, by a different person, with virtualbox 6.0.14 on Ubuntu 19.10.

Both of us are unable to click within the virtualbox manager window, like create a new VM or import or export or access preferences, using wacom tablet (in my case Wacom Intuos Pen Tablet). 

For me up to a few days ago, when I was still running virtualbox 5.2.40 on Ubuntu 19.04 (and before on Ubuntu 18.04), this was not a problem. Upgrading to Ubuntu 20.04 means that python2 is no longer supported (which makes total sense) but now it looks like virtualbox manager has become unusable because it does not seem to register the mouse clicks. 

To clarify, when I hover over items in the virtualbox manager window the buttons seem to respond to the hovering, but when I click nothing happens. Clicking in any other program so far has not resulted into issues like this. Also interestingly I discovered today that when I import (using a regular mouse temporarily plugged in) several VMs that I am able to change the order of the VMs in the virtualbox manager window (sort/group them) but again not able to click them.

This may be similar or related to: https://www.virtualbox.org/ticket/11939
If so, this may be a regression bug.

And I also posted it here without reply so far:
https://forums.virtualbox.org/viewtopic.php?f=7&t=97881",Jackg
16318,Not Signed with the Build Certificate error after installing 5.1.12 r112440,Windows,Windows,VirtualBox 5.1.12,2020-05-07T22:15:45Z,2020-05-07T22:15:45Z,"I have just installed !VirtualBox 5.1.12 !r112440 on a Windows host running Windows 10 Professional, and when trying to run a VB image for the first time I get this error:

''!VirtualBox - Error In supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\!VirtualBox\!VirtualBox.exe (rc=-5657)
Make sure the kernel module has been loaded successfully.''

VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT (-5657) - The image is required to be signed with the same certificate as the rest of !VirtualBox.

Previous to installing this version, all !VirtualBox images have worked perfectly fine, with the only change to my machine between last night and this morning being that I've installed the new version of !VirtualBox.",Shaun Collier
19573,Can not install Ubuntu 18.04 or 20.04 only 16.04,Windows,Linux,VirtualBox 6.1.6,2020-05-08T11:40:55Z,2020-05-08T11:40:55Z,"I tried to install Ubuntu 20.04 but it freezes during installation, then I tried 18.04 and same result, then I tried 16.04 and that installed normally.

I have windows 10, MSI Prestige laptop with 256GB SSD and 8GB memory
Version	10.0.18363 Build 18363


",Fugit185
19575,Failed to open a session for virtual machine,other,Linux,VirtualBox 6.1.6,2020-05-09T10:11:04Z,2020-05-09T10:11:04Z,"I'm getting this error message:
""
''Failed to open a session for the virtual machine Ubuntu.

The virtual machine 'Ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Machines\Ubuntu\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}''
""
I've tried everything. I tried downloading other versions of VB (6.1 and 5.2). I don't have an anti-virus. I also tried both graphics cards (built-in and dedicated) and i still get the same message.
I have attached the VBoxHardening.log (zipped)",asabbagh4
18754,Cannot capture mouse pointer in video recording of Ubuntu 18.04 LiveCD guest,Linux,Linux,VirtualBox 6.0.8,2020-05-09T14:32:41Z,2020-05-09T14:32:41Z,"This is on Ubuntu 18.04 host, VirtualBox 6.0.8 r130520, and Ubuntu 18.04 LiveCD (installer) guest.

Please see this video: https://i.imgur.com/KTiGSCJ.mp4

The video starts with Ubuntu 18.04 as guest in VirtualBox, controlled by rdesktop.

While mouse integration is active in VirtualBox, even if the actual mouse is controlling rdesktop, there is no mouse pointer rendered in the VirtualBox Ubuntu LiveCD guest.

If I turn off mouse integration in VirtualBox, then: when we have the actual host mouse pointer controlling via rdesktop - a mouse pointer appears rendered in the VirtualBox Ubuntu LiveCD guest. So this looks promising.

But if I do a Recording video capture in VirtualBox in this state - there is still no mouse pointer in the video recording, even if the host mouse was controlling via rdesktop, and the VirtualBox Ubuntu LiveCD appeared to be rendering the mouse pointer's ""clone""!

Maybe this is a bug in VirtualBox?

Attached is the .webm recorded by VirtualBox in the test run shown in the video above.",sdaau
18444,Cannot use microphone. Applications that try to record audio hang,Linux,Linux,VirtualBox 6.0.4,2020-05-10T16:39:50Z,2020-05-10T16:39:50Z,"After I upgraded VirtualBox from 5.x to 6.0.4, I can no longer use microphone from within the VirtualBox VM. I run Debian on both the host and the guest system.

Steps to reproduce:
* Create a new VM. Set guest OS to Debian 64-bit, don't change any other settings.
* Boot the VM using a Debian live CD.
* Enable audio input for the VM.
* Inside the VM, try to use a program that tries to record audio, such as SOX (run these commands: apt-get install sox; rec -n).
* Observe that the program hangs. On the host system, the same program works fine.",abacabadabacaba
19576,AssertLogRel F:\tinderbox\win-rel\src\VBox\Runtime\win\RTErrConvertFromWin32.cpp(448) int __cdecl RTErrConvertFromWin32(unsigned int): <NULL>  Unhandled error 1453,Windows,Linux,VirtualBox 6.1.4,2020-05-11T00:36:11Z,2020-05-11T00:36:11Z,"VirtualBox 6.1.4 under host windows10, running linux guest crashed due to an assertion failure.
Unhandled error 1453.

VirtualBox was running while I was tinkering with the programs on the Windows 10 site when suddenly the PC froze [I think Windows 10 was executing binary dump of the virtualbox image for debugging.] then about a minute or so later, I got an error dialog about memory reference error or something, but I failed to capture the screen, but rely on the log file(s) instead.",ci-zephyurus
16939,"""Text Select"" mouse cursor corrupted when mouse integration is enabled",Windows,Windows,VirtualBox 5.1.24,2020-05-12T16:10:16Z,2020-05-12T16:10:16Z,"Host:  Windows 10

Guest:  Windows 7

When mouse integration is disabled, [[http://i.imgur.com/WbeIunC.jpg|it looks normal]]

When mouse integration is enabled, [[http://i.imgur.com/SwNYZfy.jpg|it looks messed-up]]

",dfiugh
19360,[Win7 64 Host] Clipboard not working after update,Windows,Windows,VirtualBox 6.1.4,2020-05-13T16:22:06Z,2020-05-13T16:22:06Z,"After i updated VB 6.1.2 and same guest additions, the clipboard on Windows 2000 didnt worked anymore. After VB 6.1.4 came out, i tested it again and still didnt worked. With the GA 5.2.38 and VB 6.1.4, the clipboard worked but not the drag & drop, that did work with GA 6.1.4. On other Windows (tested XP,Win7 so far) it works with GA 6.1.4, so it seems only a Bug for Windows 2000. I hope you still support Windows 2000 Guest.",helgo1506
19581,Ubuntu 20.04 guest VirtualBoxVM 6.1.6 crash on macOS 10.14.6 host,Mac OS X,Linux,VirtualBox 6.1.6,2020-05-14T01:10:53Z,2020-05-14T01:10:53Z,"I got a crash of an Ubuntu 20.04 guest VirtualBoxVM 6.1.6 running on macOS 10.14.6 host when trying to remove the guest additions image after a reboot after installing the 6.1.6 guest additions.

See attached log files",Lars Sonchocky-Helldorf
19578,VirtualBox startup failure under win10,Windows,Windows,VirtualBox 6.1.6,2020-05-14T05:44:48Z,2020-05-14T05:44:48Z,"VirtualBox startup failure under win10

I have checked BIOS virtual settings
I have set Hyper-V off
I have stopped all Hyper-V services
",oracle-lover
19584,Need for Speed Underground 2 causes Virtualbox.exe application error,Windows,Windows,VirtualBox 5.2.40,2020-05-14T14:15:34Z,2020-05-14T14:15:34Z,"When I run Need for Speed Underground 2, window VirtualBox.exe application error appears",Nikita Stepanov
19585,Mouse buttons freezes when using remote desktop,Windows,Linux,VirtualBox 6.1.6,2020-05-14T23:13:16Z,2020-05-14T23:13:16Z,"The mouse buttons stop working (no response) when running Ubuntu (any version). The pointer still moves, but no clicking has no effect.

THis is very repeatable - it occurs every 2 or 3 minutes. The only workaround, is to close RDT, then start again.

Note: this issue does not happen when running windows application on the remote machine. Only when running Ubuntu on VirtualBox (6.1.X , i.e. any version of VBox).",2020Newbie
18127,"Kernel Panic (""a freed zone element has been modified in zone kalloc.16) with 5.2.22 on Mac OSx",Mac OS X,Linux,VirtualBox 5.2.22,2020-05-15T08:54:30Z,2020-05-15T08:54:30Z,"Hello,
after upgrading VirtualBox (including extensions) to 5.2.22 my MacBook runs into kernel panics as soon as I deleted some files in my VM Guest (OEL 6.7) and tried to recreate them.

Kernel panic looks like this (no additional messages in VBox.log) - just copied and pasted two of them.

{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 11:07:05 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff80058b8ff7): ""a freed zone element has been modified in zone kalloc.16: expected 0xc0ffee0af45053f8 but found 0x10000c0ec035, bits changed 0xc0fffe0af85e93cd, at offset 0 of 16 in element 0xffffff804b1e5140, cookies 0x3f00118abf4e05f8 0x53521ec3d6d4d23""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 0), Frame : Return Address
0xffffff81fdf7b980 : 0xffffff800586b1c6 
0xffffff81fdf7b9d0 : 0xffffff8005993a74 
0xffffff81fdf7ba10 : 0xffffff8005985d44 
0xffffff81fdf7ba80 : 0xffffff800581d1e0 
0xffffff81fdf7baa0 : 0xffffff800586ac3c 
0xffffff81fdf7bbd0 : 0xffffff800586a9fc 
0xffffff81fdf7bc30 : 0xffffff80058b8ff7 
0xffffff81fdf7bc90 : 0xffffff80058b8910 
0xffffff81fdf7bce0 : 0xffffff80058b7313 
0xffffff81fdf7be10 : 0xffffff8005876c44 
0xffffff81fdf7be80 : 0xffffff8005ce5ba3 
0xffffff81fdf7bed0 : 0xffffff8005ce5a50 
0xffffff81fdf7bf40 : 0xffffff8005e03008 
0xffffff81fdf7bfa0 : 0xffffff800581d9c6 

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000005600000
Kernel text base: 0xffffff8005800000
__HIB  text base: 0xffffff8005700000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 519699934001
last loaded kext at 248994916223: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f868a3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AudioAUUC	1.70
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.AppleHDAHardwareConfigDriver	281.52
com.apple.driver.AppleHDA	281.52
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.ACPI_SMC_PlatformPlugin	1.0.0
com.apple.driver.eficheck	1
com.apple.driver.AppleFIVRDriver	4.1.0
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AGDCBacklightControl	3.20.0
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.iokit.SCSITaskUserClient	404.30.2
com.apple.filesystems.apfs	748.51.0
com.apple.driver.AppleFileSystemDriver	3.0.1
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.driver.usb.cdc.acm	5.0.0
com.apple.kext.triggers	1.0
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.AppleGPUWrangler	3.20.0
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.driver.IOPlatformPluginLegacy	1.0.0
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.AppleThunderboltEDMSink	4.1.4
com.apple.driver.AppleThunderboltDPOutAdapter	5.5.5
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.AppleUSBMergeNub	900.4.1
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.driver.AppleXsanScheme	3
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}


{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 10:58:16 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff8001cb903d): ""a freed zone element has been modified in zone kalloc.16: expected 0xe4988e3ed03a8352 but found 0xdeadbeef00000001, bits changed 0x3a3530d1d03a8353, at offset 0 of 16 in element 0xffffff8048db0cf0, cookies 0x3f00113912711a2e 0x53521e81ce62793""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 2), Frame : Return Address
0xffffff91ffcbb750 : 0xffffff8001c6b1c6 
0xffffff91ffcbb7a0 : 0xffffff8001d93a74 
0xffffff91ffcbb7e0 : 0xffffff8001d85d44 
0xffffff91ffcbb850 : 0xffffff8001c1d1e0 
0xffffff91ffcbb870 : 0xffffff8001c6ac3c 
0xffffff91ffcbb9a0 : 0xffffff8001c6a9fc 
0xffffff91ffcbba00 : 0xffffff8001cb903d 
0xffffff91ffcbba60 : 0xffffff8001cb8910 
0xffffff91ffcbbab0 : 0xffffff8001cb7313 
0xffffff91ffcbbbe0 : 0xffffff8001c76c44 
0xffffff91ffcbbc50 : 0xffffff8002215d8c 
0xffffff91ffcbbc70 : 0xffffff8002215df2 
0xffffff91ffcbbc90 : 0xffffff800226779d 
0xffffff91ffcbbcb0 : 0xffffff800226780c 
0xffffff91ffcbbcd0 : 0xffffff80022638fc 
0xffffff91ffcbbd10 : 0xffffff80022c842f 
0xffffff91ffcbbd70 : 0xffffff8001d42b7b 
0xffffff91ffcbbdc0 : 0xffffff8001c706e0 
0xffffff91ffcbbe10 : 0xffffff8001c4da3d 
0xffffff91ffcbbe60 : 0xffffff8001c6054b 
0xffffff91ffcbbef0 : 0xffffff8001d6ff1d 
0xffffff91ffcbbfa0 : 0xffffff8001c1d9e6 

BSD process name corresponding to current thread: VBoxSVC

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000001a00000
Kernel text base: 0xffffff8001c00000
__HIB  text base: 0xffffff8001b00000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 6013699815144
last loaded kext at 245870616385: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f82ca3000, size 69632)
last unloaded kext at 403105650360: com.apple.driver.AppleFileSystemDriver	3.0.1 (addr 0xffffff7f82804000, size 8192)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.driver.AudioAUUC	1.70
com.apple.filesystems.autofs	3.0
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleHDA	281.52
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.filesystems.apfs	748.51.0
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.kext.triggers	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.AppleSSE	1.0
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.AppleGPUWrangler	3.20.0
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}

Mac OSx is 10.13.6 (17G3025).",OracleSK
19587,Awful Linux Guest Performance,Linux,Linux,VirtualBox 6.1.6,2020-05-15T11:02:43Z,2020-05-15T11:02:43Z,"I just tested 64bit VBox 6.0.20 and 6.1.6 with a 64bit Linux guest on a 64bit Linux host (updating Guest Additions each time). Started at 6.0.20, performance was fine. Upgraded to 6.1.6, performance was so bad that the VM is unusable. Downgraded back to 6.0.20, performance is normal. So, VBox 6.1 is broken for Linux guests because of the awful performance.

Host: Intel Core i7 (1st gen) 28G RAM
Guest: 2 cores, 4G RAM

Logs for both the broken 6.1.6 guest and the working 6.0.20 guest are attached.

I ran this test because a user on a FB group had perf issues with a 64bit Linux guest. After I suggested that he downgrade to 6.0.20, his perf is back to normal.
",Tom3.14159
15152,Cannot unsubscribe from notifications for a single issue,other,other,VirtualBox 5.0.14,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
19560,Segfault on vm start when 3d acceleration is enabled,Linux,all,VirtualBox 6.1.6,2020-05-17T15:36:07Z,2020-05-17T15:36:07Z,"Host: Fedora 32 x86_64
VirtualBox 6.1.6 rpmfusion

VirtualBoxVM segfaults on start if 3d acceleration is enabled (Windows guest with VBoxSVGA driver or Linux guest with VMSVGA). I managed to get some backtrace:
#0  0x00007f0afb2f7bb7 in ShaderInitLib () at /usr/lib64/virtualbox/VBoxSVGA3D.so
#1  0x00007f0b185e8abd in vmsvga3dPowerOn(PDMDEVINSR3*, VGAState*, VGASTATER3*) () at /usr/lib64/virtualbox/VBoxDD.so
#2  0x00007f0b185d5ae9 in vmsvgaR3PowerOn(PDMDEVINSR3*) () at /usr/lib64/virtualbox/VBoxDD.so
#3  0x00007f0b185603d4 in vgaR3PowerOn(PDMDEVINSR3*) () at /usr/lib64/virtualbox/VBoxDD.so
#4  0x00007f0b48d4a387 in PDMR3PowerOn () at /usr/lib64/virtualbox/components/VBoxVMM.so
#5  0x00007f0b48d96e68 in vmR3PowerOn(VM*, VMCPU*, void*) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#6  0x00007f0b48da0814 in vmmR3EmtRendezvousCommon(VM*, VMCPU*, bool, unsigned int, int (*)(VM*, VMCPU*, void*), void*) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#7  0x00007f0b48da441e in VMMR3EmtRendezvousFF () at /usr/lib64/virtualbox/components/VBoxVMM.so
#8  0x00007f0b48d9c33d in vmR3EmulationThreadWithId(RTTHREADINT*, UVMCPU*, unsigned int) () at /usr/lib64/virtualbox/components/VBoxVMM.so
#9  0x00007f0b6b9d8044 in rtThreadMain () at /usr/lib64/virtualbox/VBoxRT.so
#10 0x00007f0b6ba8e66e in rtThreadNativeMain(void*) () at /usr/lib64/virtualbox/VBoxRT.so
#11 0x00007f0b6bd7a432 in start_thread () at /app/lib64/libpthread.so.0
#12 0x00007f0b6bca19d3 in clone () at /app/lib64/libc.so.6

VBoxTestOGL shows success
",Max Fedotov
19582,"VirtualBox host, memory management issue, unable to release unused memory of guest",Linux,Linux,VirtualBox 6.1.6,2020-05-18T15:23:13Z,2020-05-18T15:23:13Z,"I have a workstation with 32 GB installed memory.

I create a new Debian virtual machine, and allocate 16 GB to it. When I boot the machine, it only take less than 800 MB memory. As the virtual machine running, especially for heavy tasks. The memory occupation increase. But when I end those tasks, the memory usage of guest machine's OS suddenly reduce, but the memory occupation of virtual machine on host RAM, still keep as the memory upper bound. 

I believe that it is the problem of VirtualBox, because even if I reboot (not same as power off and boot) the virtual machine, the RAM usage still keep as Maximum.

I hope VirtualBox can add ability to automatically release unused guest memory.",stl0hello
19599,[VM Crash] Cannot access memory at 0x00000...,Windows,Linux,VirtualBox 6.1.8,2020-05-18T17:05:29Z,2020-05-18T17:05:29Z,"My Ubuntu VM will randomly decide to access an inaccessible memory address causing a panic and crash.

I haven't been able to nail this down to a specific event, it seems to happen randomly. If I can identify a reproducible event I'll update the report.",Chris Doherty
19601,virtio-scsi issue feedback,other,other,VirtualBox 6.1.8,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
19604,Win XP Crash during AVG Install,Windows,Windows,VirtualBox 6.1.8,2020-05-20T00:07:06Z,2020-05-20T00:07:06Z,"Hi,
I was installing AVG AV in Win XP Box, which is running on a Win 8.1 machine. It resulted in a critical error which stopped the VM. The program prompted me to log a ticket and post the log and image.  How do I correct this?  I have been retrieving data from old FDDs in the VM.  Now my data is trapped in the VM.

Thanks,
JC-bnm ",JC-bnm
19608,"[Patch] Fixed BIOS int 13h, ah=48h",Linux,all,VirtualBox 6.1.8,2020-05-21T13:31:13Z,2020-05-21T13:31:13Z,"Patch for VirtualBox 6.1.8. Fixes an impossible condition in «edd_fill_dpt» function, which implements the function 48h of the BIOS interrupt 13h.

{{{
diff -ruN ./VirtualBox-6.1.8{.orig,}/src/VBox/Devices/PC/BIOS/disk.c
--- ./VirtualBox-6.1.8.orig/src/VBox/Devices/PC/BIOS/disk.c	2020-05-14 20:39:11.000000000 +0200
+++ ./VirtualBox-6.1.8/src/VBox/Devices/PC/BIOS/disk.c	2020-05-21 14:53:18.672394097 +0200
@@ -140,6 +140,7 @@
 int edd_fill_dpt(dpt_t __far *dpt, bio_dsk_t __far *bios_dsk, uint8_t device)
 {
     uint16_t    ebda_seg = read_word(0x0040,0x000E);
+    uint16_t    new_dpt_size;
 
     /* Check if buffer is large enough. */
     if (dpt->size < 0x1a)
@@ -149,7 +150,7 @@
     if (dpt->size >= 0x1a) {
         uint64_t    lba;
 
-        dpt->size      = 0x1a;
+        new_dpt_size   = 0x1a;
         dpt->blksize   = bios_dsk->devices[device].blksize;
 
         if (bios_dsk->devices[device].device == DSK_DEVICE_CDROM) {
@@ -175,7 +176,7 @@
         uint8_t     channel, irq, mode, checksum, i, xlation;
         uint16_t    iobase1, iobase2, options;
 
-        dpt->size = 0x1e;
+        new_dpt_size      = 0x1e;
         dpt->dpte_segment = ebda_seg;
         dpt->dpte_offset  = (uint16_t)&EbdaData->bdisk.dpte;
 
@@ -227,7 +228,7 @@
         iface   = bios_dsk->channels[channel].iface;
         iobase1 = bios_dsk->channels[channel].iobase1;
 
-        dpt->size       = 0x42;
+        new_dpt_size    = 0x42;
         dpt->key        = 0xbedd;
         dpt->dpi_length = 0x24;
         dpt->reserved1  = 0;
@@ -269,6 +270,8 @@
         checksum = -checksum;
         dpt->checksum = checksum;
     }
+
+    dpt->size = new_dpt_size;
     return 0;
 }
 
}}}
",jlxip
19611,"Cannot install Debian on 3 ISOs, after installing from 2 other discs constantly prompts to insert disc 1, even if it is already inserted",Windows,Linux,VirtualBox 6.1.8,2020-05-22T06:57:11Z,2020-05-22T06:57:11Z,"I was installing Debian from 3 ISO images. 
Debian installer scanned all the discs, and at some point, it told me to insert 2 other discs. 
Then it prompted to insert disc 1 again, and that's where the problems began. 
I inserted disc 1, and it prompted me to insert it over and over again, even though the disc was in the virtual drive.  
It didn't recognize the disc. 
When I pressed return button, it said ""Cannot read from disc"" when I continued to installing GRUB. 
When the installation ended, I tried to boot Debian, and it didn't boot.
I have checked the ISO images, and there was nothing wrong with them.",anonymous7002
19592,dnf upgrade of virtual box sequence,Linux,Linux,VirtualBox 6.1.8,2020-05-22T12:20:53Z,2020-05-22T12:20:53Z,"The update sequence seems wrong, taking steps to apply 6.1.6 after 6.1.8 

Output to screen:

# dnf upgrade
Last metadata expiration check: 1:17:10 ago on Sat 16 May 2020 03:43:57 PM EDT.
Dependencies resolved.
=========================================================================================================================
 Package                      Architecture         Version                                Repository                Size
=========================================================================================================================
Upgrading:
 VirtualBox-6.1               x86_64               6.1.8_137981_fedora31-1                virtualbox                94 M

Transaction Summary
=========================================================================================================================
Upgrade  1 Package

Total download size: 94 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64.rpm                                        3.8 MB/s |  94 MB     00:24    
-------------------------------------------------------------------------------------------------------------------------
Total                                                                                    3.8 MB/s |  94 MB     00:24     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                 1/1 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Upgrading        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 

Creating group 'vboxusers'. VM users must be member of that group!


  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Cleanup          : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Verifying        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Verifying        : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 

Upgraded:
  VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                                          

Complete!

",Wheaties
19607,Very high energy consumption by 6.1.8 on Mac OS X,Mac OS X,Linux,VirtualBox 6.1.8,2020-05-22T14:52:01Z,2020-05-22T14:52:01Z,"With 6.1.8 on MacOS I'm was seeing very high energy consumption, so much so that my battery level was dropping despite being plugged in. I had to downgrade to 6.1.6.
",tg7747
19612,Windows 10 with and without Hyper-V installed.,Windows,Windows,VirtualBox 6.1.8,2020-05-22T14:54:43Z,2020-05-22T14:54:43Z,"Option:  VT-x/AMD-V Unchecked (not disabled)
Hyper-V: not installed, VT-x/AMD-V shows as Acceleration (shouldn't)
Hyper-V: installed, VT-x/AMD-V shows as Acceleration (shouldn't)

With Hyper-V installed (only once, even after removed), emulation fails to start due to missing VT-x/AMD-V support.

VT-x/AMD-V should follow the requirements of the checkbox, if not wanted, it shouldn't ""auto on"", instead the Acceleration should list ""None"".",BBISOFT
19613,Windows Guest on Windows 7+ loses focus during mouse capture.,Windows,Windows,VirtualBox 6.1.8,2020-05-22T15:09:04Z,2020-05-22T15:09:04Z,"Mouse capture on Windows Guest (actually Android x86 also has issues):

If the start menu is hidden and is brought up during mouse movement, causes mouse capture to break free of the window, using the mouse after that causes odd behavior (wrong mouse click, etc).

High mouse acceleration also causes mouse capture to break free.

P/S2 Mouse, USB Tablet, USB Multi-Touch Tablet produce the same results.

To test:  Use the Windows 98 SE from Archives.org, mouse will refuse to stay in window after the start menu appears after hidden and will continue to become unusable after the initial break free.",BBISOFT
19614,Enabling Page Fusion cause Windows 10 guests to hang random time after booting,Linux,Windows,VirtualBox 6.1.8,2020-05-23T00:41:37Z,2020-05-23T00:41:37Z,"I first posted in the [https://forums.virtualbox.org/viewtopic.php?f=2&t=98123&sid=51fc9f959284400beaac6aadba19f088 forums] and didn't get much direction.

Sometime after upgrading to 6.1.x (don't remember the exact version - .2 or .3 or maybe .4 I think) my Windows 10 guests would randomly freeze shortly after booting.  I built a new from DVD/ISO Windows 10 1909 VM and it didn't/wouldn't freeze.  In comparing the output of ""VBoxManage showvminfo"" I noticed that I had different settings for [https://www.virtualbox.org/manual/UserManual.html#guestadd-balloon Memory Balloning] and [https://www.virtualbox.org/manual/UserManual.html#guestadd-pagefusion Page Fusion].

The freezing behavior didn't change with adjustments to the memory balloning settings, but did for page fusion.  If page fusion was enabled on the ""old"" Windows or the ""new"" Windows guest they would freeze.  Disabling page fusion on the guests and they wouldn't freeze.  I could repeat this Page Fusion '''Enabled''' = Freeze, Page Fusion '''Disabled''' = No Freeze.

The guest additions version of the guest matched the host (6.1.8) when I did the final set of testing.

VirtualBox: 6.1.8 with guest additions[[BR]]
Host: Linux Mint 18.3 Cinnamon 64-bit[[BR]]
Kernel: 4.15.0.n[[BR]]
Memory: 48GB (was 16GB when I initially set up memory balloning and page fusion back in 5.2 days)[[BR]]



",DerekD
19596,0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot,Windows,Linux,VirtualBox 6.1.8,2020-05-23T23:21:57Z,2020-05-23T23:21:57Z,"Have a virtual machine called ""manjaro-kde"". When I start Virtualbox 6.1.8 a different vm is selected, but as soon as I choose ""manjaro-kde"", Virtualbox just freezes and can't be closed. The GUI X button is greyed out. I have to use Process Explorer to kill it, and after that can't be relaunched until I reboot. At least UI should provide several ways to fix it, not freeze and forcing a reboot.

{{{
Oracle VM Virtualbox Manager
manjaro-kde: Inaccessible
Could not find an open hard disk with UUID {68875579-5923-4090-b612-f672cb93c5ff}
Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80bb0001)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
}}}
Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=98232",DeGarden
19618,No hardware acceleration on Ryzen7 4800HS,other,other,VirtualBox 6.1.8,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
19609,Windows 10 Pro failed to work inside Ubuntu 20 VirtualBox,Linux,Windows,VirtualBox 6.1.6,2020-05-24T23:07:02Z,2020-05-24T23:07:02Z,"I have a couple of Windows 10 Pro VMs that used to run perfectly on Ubuntu 18, at the time i upgrade they started to get BSOD always, some times before login screen, some time after... the error seems to be in some part of the Windows Kernel 
Host:
AMD® A6-4400m apu with radeon(tm) hd graphics × 2 
AMD® Aruba
RAM 5.1 GiB
HD: 500.1 GB
Ubuntu 20.04 LTS
64 bits
GNOME Version: 3.36.2

Virtual Box version: Versión 6.1.6_Ubuntu r137129

GuestOS:
Windows 10 PRO
VM Type: Windows 10 64 bit
Chipset: PIIX3
I/O APIC Enabled
1 CPU
Execution limit: 100%
Network Bridge adaptor over wireless LAN interface

",Charlymoon
19621,vboxwebsrv is not connected to port 18083,Linux,other,VirtualBox 6.1.8,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
15050,Can not connect USB Stick to VM,Windows,Linux,VirtualBox 5.0.14,2020-05-25T18:09:52Z,2020-05-25T18:09:52Z,"How to reproduce:
Starting VM. Plugging in USB Stick. After this the following message appears:

Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",Uti
19451,Guest crash after some hours working,Windows,Windows,VirtualBox 6.1.4,2020-05-26T08:19:05Z,2020-05-26T08:19:05Z,On 6.x versions of VBox crashes are stable :-(,Дмитро
19624,Scroll bars missing in VirtualBox 6,Windows,all,VirtualBox 6.1.6,2020-05-26T18:24:52Z,2020-05-26T18:24:52Z,"Hi,

I use scroll bars.  So it sucks when they constantly disappear.

There should be an option to permanently enable them.

Thanks.

Windows 8.1 64-bit
VirtualBox 6.1
",veganaiZe
19562,VBoxClient on Linux : leaves defunct xrandr zombies,all,Linux,VirtualBox 6.1.6,2020-05-27T00:24:18Z,2020-05-27T00:24:18Z,"In this new version the VBox guest additions for Linux have un-desirable working effect in that it leaves many defunct or zombies, somewhere along the chain of xrandr invocation.

Below is snippets from pstree and ps.

{{{
 ├─2*[VBoxClient───VBoxClient───2*[{VBoxClient}]]
        ├─VBoxClient───VBoxClient───3*[{VBoxClient}]
        ├─VBoxClient───VBoxClient─┬─29*[cvt]
        │                         ├─30*[sh]
        │                         ├─17*[xrandr]
        │                         └─2*[{VBoxClient}]

}}}


{{{
1535 ?        00:00:00 VBoxClient
 1536 ?        00:00:05 VBoxClient
 1544 ?        00:00:00 VBoxClient
 1545 ?        00:00:00 VBoxClient
 1550 ?        00:00:00 VBoxClient
 1551 ?        00:00:22 VBoxClient
 1557 ?        00:00:00 VBoxClient
 1558 ?        00:00:00 VBoxClient
 1559 ?        00:00:00 xrandr <defunct>
 1562 ?        00:00:00 sh <defunct>
 1564 ?        00:00:00 cvt <defunct>

 1601 ?        00:00:00 xrandr <defunct>

 1631 ?        00:00:00 sh <defunct>
 1634 ?        00:00:00 cvt <defunct>
 1638 ?        00:00:00 lxclipboard

 1665 ?        00:00:00 xrandr <defunct>

 2651 ?        00:00:00 sh <defunct>
 2653 ?        00:00:00 cvt <defunct>
 2663 ?        00:00:00 sh <defunct>
 2666 ?        00:00:00 xrandr <defunct>
 2683 ?        00:00:00 sh <defunct>
 2685 ?        00:00:00 cvt <defunct>
 2695 ?        00:00:00 sh <defunct>
 2697 ?        00:00:00 cvt <defunct>
 2708 ?        00:00:00 xrandr <defunct>
 2725 ?        00:00:00 sh <defunct>
 2727 ?        00:00:00 cvt <defunct>
 2737 ?        00:00:00 sh <defunct>
 2739 ?        00:00:00 cvt <defunct>
 2750 ?        00:00:00 xrandr <defunct>
 2783 ?        00:00:00 sh <defunct>
 2785 ?        00:00:00 cvt <defunct>
 2795 ?        00:00:00 sh <defunct>
 2797 ?        00:00:00 cvt <defunct>
 2808 ?        00:00:00 xrandr <defunct>

 5735 ?        00:00:00 sh <defunct>
 5737 ?        00:00:00 cvt <defunct>
 5747 ?        00:00:00 sh <defunct>
 5749 ?        00:00:00 cvt <defunct>
 5760 ?        00:00:00 xrandr <defunct>
 5793 ?        00:00:00 sh <defunct>
 5795 ?        00:00:00 cvt <defunct>
 5805 ?        00:00:00 sh <defunct>
 5807 ?        00:00:00 cvt <defunct>
 5818 ?        00:00:00 xrandr <defunct>
 5842 ?        00:00:00 dhclient
 5853 ?        00:00:00 sh <defunct>
 5855 ?        00:00:00 cvt <defunct>
 5865 ?        00:00:00 sh <defunct>
 5867 ?        00:00:00 cvt <defunct>
 5879 ?        00:00:00 xrandr <defunct>
 5912 ?        00:00:00 sh <defunct>
 5914 ?        00:00:00 cvt <defunct>
 5924 ?        00:00:00 sh <defunct>
 5926 ?        00:00:00 cvt <defunct>
 5937 ?        00:00:00 xrandr <defunct>
 5964 ?        00:00:00 sh <defunct>
 5966 ?        00:00:00 cvt <defunct>
 5976 ?        00:00:00 sh <defunct>
 5978 ?        00:00:00 cvt <defunct>
 5989 ?        00:00:00 xrandr <defunct>
 6022 ?        00:00:00 sh <defunct>
 6024 ?        00:00:00 cvt <defunct>
 6034 ?        00:00:00 sh <defunct>
 6036 ?        00:00:00 cvt <defunct>
 6047 ?        00:00:00 xrandr <defunct>
 6074 ?        00:00:00 sh <defunct>
 6076 ?        00:00:00 cvt <defunct>
 6086 ?        00:00:00 sh <defunct>
 6088 ?        00:00:00 cvt <defunct>
 6099 ?        00:00:00 xrandr <defunct>
 6132 ?        00:00:00 sh <defunct>
 6134 ?        00:00:00 cvt <defunct>
 6144 ?        00:00:00 sh <defunct>
 6146 ?        00:00:00 cvt <defunct>
 6157 ?        00:00:00 xrandr <defunct>
 6176 ?        00:00:00 sh <defunct>
 6178 ?        00:00:00 cvt <defunct>
 6188 ?        00:00:00 sh <defunct>
 6190 ?        00:00:00 cvt <defunct>
 6201 ?        00:00:00 xrandr <defunct>
 6234 ?        00:00:00 sh <defunct>
 6236 ?        00:00:00 cvt <defunct>
 6246 ?        00:00:00 sh <defunct>
 6248 ?        00:00:00 cvt <defunct>
 6259 ?        00:00:00 xrandr <defunct>

}}}

Seems it's 'trying to do something..', when I do something -  I haven't spent time checking exactly what, but could be the enabling and/or moving the virtual monitor. However, from memory at least one defunct group appears straight after boot and with first & only one virtual monitor is on. It grows in number of traces from there.

This was not the case for older VBox, quite likely from v 6.1.4 and higher.

My guest is Linux Fedora 30 64bit.",dry
10085,making a symlink fails on a shared folder with EROFS,all,Linux,VirtualBox 4.1.8,2020-05-27T16:34:18Z,2020-05-27T16:34:18Z,"it is impossible to create a symlink within a shared folder from guest OS.

guest shell output:

----------------------

[user@centos sf_sources]$ mount

/dev/sda1 on / type ext4 (rw)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

tmpfs on /dev/shm type tmpfs (rw,rootcontext=""system_u:object_r:tmpfs_t:s0"")

/dev/sda3 on /home type ext4 (rw)

none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

sources on /media/sf_sources type vboxsf (gid=501,rw)

[user@centos sf_sources]$ ln ./test ./test2

ln: creating hard link `./test2' => `./test': Operation not permitted

[user@centos sf_sources]$ ln -s ./test ./test2

ln: creating symbolic link `./test2': Read-only file system

[user@centos sf_sources]$ touch test2

[user@centos sf_sources]$ ls test*

test  test2

-------------------

host FS for the shared folder is ext4.

same operation worked fine in ver. 4.1.6",Vlad Bespalov
19627,Gnome Terminal does not open on Linux guest after installing 6.1.8 GA,Windows,Linux,VirtualBox 6.1.8,2020-05-28T09:32:48Z,2020-05-28T09:32:48Z,"This seems to be related to the other x.11 issues reported with 6.1.8.

If I uninstall GA, I can open a gnome-terminal just fine.

However once I install GA, the terminal fails to launch (the mouse pointer turns to animated wait icon but ultimately no terminal window is opened).

I'm running Windows Host on Windows 10, Centos 8 (up-to-date) guest.

My Centos installation has both Wayland and xorg X.11 display servers installed for some reason (not sure if that's standard on Centos) but it's possible to select which one to use at logon.

When selecting Wayland I get the ""Parent seems to be non-X.11"" error message popup, but that error doesn't come up when I select the xorg server, so that's just the x.11 detection that's new in this release.

The problem is that gnome-terminal doesn't launch at all regardless of which x.11 server I select.

If I connect to the Linux guest from a Windows ssh client, that's fine, but running gnome-terminal from that bash shell doesn't work. Other x.11 programs (eg firefox) work fine from both the guest desktop and a remote ssh shell.

This should be easy to replicate.

Let me know if I can help diagnose further.
",qdev
19628,"Segmentation fault KERN_INVALID_ADDRESS, MacOS host",Mac OS X,Linux,VirtualBox 6.1.8,2020-05-28T09:36:45Z,2020-05-28T09:36:45Z,"MacOS host, Linux (OpenSUSE Tumbleweed) guest.
VM starts up, but segfaults when GUI startup happens. Crashes both VBox 6.1.6 and 6.1.8.

Part of the crashreport for easier searching:

{{{
Process:               VirtualBoxVM [867]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.8 (6.1.8)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [796]
Responsible:           VirtualBox [785]
User ID:               501

Date/Time:             2020-05-28 12:29:59.960 +0300
OS Version:            Mac OS X 10.15.5 (19F96)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        7F0F4F94-AA59-F9D4-DA55-099371894FD2


Time Awake Since Boot: 140 seconds

System Integrity Protection: enabled

Crashed Thread:        11  EMT-1

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [867]
}}}",Richlv
19626,"VirtualBox host-only adapter keeps getting set to an invalid configuration, which breaks multicast.",Windows,other,VirtualBox 6.1.8,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
19629,VBox Fedora Linux Guest Additions 6.1.8 Client failed to get display change,Windows,Linux,VirtualBox 6.1.8,2020-05-28T17:53:40Z,2020-05-28T17:53:40Z,"An error is displayed after updating VirtualBox to version 6.1.8 with the guest Additions into the Fedora Linux 31 operating system running KDE desktop.
Even when you have rebooted everything (having windows as the host OS) and logged on to Linux using a normal user account the desktop displays an error box bottom right-hand corner which is as follows: ""VBoxClient failed to get display change. rc=Verr_Access_Denied""",Clivewi
19524,6.1.6 performance dreadful on VMSVGA and LinuxMint 18.2 VM on Windows 10 host,Windows,Linux,VirtualBox 6.1.6,2020-05-28T20:13:00Z,2020-05-28T20:13:00Z,"I require VBoxSVGA with LinuxMint 18.2 running on a Windows 10 host.  Selection of VMSVGA causes a slow down of the entire VM, including disk access.  That's so weird.

",Trent
18927,VBoxClient clipboard fails to copy rich text from guest to host,Mac OS X,Linux,VirtualBox 6.0.12,2020-05-28T22:20:49Z,2020-05-28T22:20:49Z,"A variant of this bug is back in 6.0 (I tested 6.0.10 and 6.0.12):

  https://www.virtualbox.org/ticket/15782

  https://www.virtualbox.org/ticket/16242

Rich text (e.g., something from a web page) does not copy from guest to host; but plain text does. Expected behavior is for it to copy as plain text.

The workaround is to paste rich text into a simple text file within the guest, re-select said (what is now) plain text, then copy that to the host.

The silver lining here is copying rich text does not completely break clipboard functionality as it did in the previous bugs (thus requiring killing VBoxClient).
",philip
19570,Ubuntu 18.04 guest crashes regularly,Linux,Linux,VirtualBox 6.1.6,2020-05-29T14:58:22Z,2020-05-29T14:58:22Z,"Guest: Ubuntu 18.04
Host: Ubuntu 18.04

This guest is actively (7 days a week) used since VirtualBox 5.x, no crashes were observed. After upgrading VirtualBox to 6.1.6 guest gets terminated with 'Aborted' state at least once a week, usually during text editing.",Andriy
19574,"Ubuntu 20.04 LTS, VM ICONS INVISIBLE",Linux,all,VirtualBox 6.1.6,2020-05-30T09:20:52Z,2020-05-30T09:20:52Z,"I am using a Linux Ubuntu 20.04 LTS host, and when I start a VM, the icon is invisible in the ubuntu dock, the only way to make it visible is by moving the program to another workspace, or locking and unlocking the host.",saikotwolf
19625,Super key and Alt-tab get captured by Ubuntu 20.04 Host not Windows 10 guest on 6.1.8,Linux,Windows,VirtualBox 6.1.8,2020-06-02T02:29:21Z,2020-06-02T02:29:21Z,"Similar to the closed #10842 I am seeing the Ubuntu 20.04 host capture both the Super/Windows key (always) as well as Alt-tab.

I am seeing this on Ubuntu 20.04 immediately after upgrading from 18.04.

I have this version of Virtualbox installed  https://download.virtualbox.org/virtualbox/6.1.8/virtualbox-6.1_6.1.8-137981~Ubuntu~eoan_amd64.deb.

I am using a Windows 10 Virtualbox guest. When I press the ""Windows/Super"" key the Ubuntu unity menu responds when the Windows 10 virtualbox should respond. The unity desktop also seems to capture ""Alt-Tab"" but other ""Alt"" commands do respond in the Windows virtualbox.",kendonb
19637,QT 5.15 breaks VirtualBox (6.1.8),Linux,other,VirtualBox 6.1.8,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
19638,no network connection with virtio-net after some time,Linux,Linux,VirtualBox 6.0.22,2020-06-03T17:57:42Z,2020-06-03T17:57:42Z,"Hi,

I'm running an Ubuntu 18.04 guest on a ubuntu 18.04 host. The guest uses virtio-net for the network adapter.

After some uptime, you can use the interface anymore. The syslog is flodded with

{{{
net eth0: Unexpected TXQ (0) queue failure: -5
}}}

I have to reboot the VM to get it working again.

If you need any information, please don't hesitate to ask for.

Regards,
meiser",Peter Meiser
19639,host freezes when network load is high,Windows,Windows,VirtualBox 6.1.8,2020-06-03T20:49:20Z,2020-06-03T20:49:20Z,"Hello, my friends.

I use a virtual machine to work while I stay in quarantine.
Periodically I faced with heisenbug when my host machine freezes.
I had no idea why this was happening.
But today I was able to reproduce the steps that lead to freezing.

So, what I have.
VBox: 6.1.8
Host: win 7 x64
Motherboard: ASUS AC97 rev.2 
Host disk: SSD Plextor PX-128M6S
Host network card: Realtek PCIe GBE (pci\ven_10ec&dev_8168&subsys_85051043&rev_09)

Guest: win 7 x64
Guest virtual network: Bridge / Intel pro 1000MT Desktop
Virtual disk: VHD / AHCI / i/o caching enabled
Virtual chipset: ICH9 / i/o apic enabled


What I do.
When I try to download a large file (e.g. 1 GB) 
then after a while the guest and the host system freezes.. absolutely )))

What could be the real cause of freezing
- bridged network adapter,
- i/o caching, scaling virtual disk,
- or chipset ...
I don't know,
but I tried a dozen variants of parameters,
and all the same, periodically it happens..
",Aleksey_Popov_1988
19509,Windows 10 VM crashes after copy/paste text coming from Ubuntu 18.04 browser window,Linux,Windows,VirtualBox 6.1.6,2020-06-03T22:59:02Z,2020-06-03T22:59:02Z,"It happened twice: I copied some text in a browser and intended to paste it in a Windows application. The whole VM disappeared and the VBox Manager indicated  ""Aborted"" (or similar). It might be Vbox, it might also be the Guest Additions, I can't tell.",D.Bugger
16801,Running a Virtual Machine when Windows Hyper-V is enabled should NOT Crash Windows,Windows,all,VirtualBox 5.1.22,2020-06-04T16:28:57Z,2020-06-04T16:28:57Z,"VirtualBox can not run on Windows 10 when Hyper-V mode is ACTIVE (ON).  However the existing behaviour is pathological and must be corrected.  

Running a VM when Hyper-V is ON causes the BSOD!



Conditions:

 1. Windows boots with Hyper-V enabled
 2. Start-up VirtualBox Manager GUI
 3. START an existing VM

Outcome:

 1. VM begins to load
 2. The dread Windows BSOD (Blue Screen of Death) appears
 3. Windows dies -- generates crash log, etc.
 4. Windows reboots
 5. NOTE: Hyper-V is still active and must be deactivated manually.


Resolution Sought:

 1. Check for Hyper-V mode is: OFF, at start-up for all VirtualBox tools; especially:
     * VirtualBox Manager GUI and 
     * VM shell  itself

 2. Issue a WARNING pop-up or error message for command line
    Reporting that Hyper-V mode is active and VirtualBox cannot
    run while there is another hypervisor active.  Or some such.

 3. Exit the VirtualMachine (shell) once the Hyper-V Active 
    status is reported.  
      * Thus Avoiding the BSOD


Optional / suggestion:

 * It would be useful for the warning to tell users how to 
   disable/enable Hyper-V as part of the warning message(s).

 * Another helpful feature is for the VirtualBox management 
   GUI to turn Hyper-V off or on from a menu.


Related / supplementary notes:

There seem to be several issues that mention Hyper-V troubles.  Some are real bugs and some look like misunderstandings.

In my opinion no software should cause a system crash-dump when it can be prevented by checking some system configuration attributes.

See also:

 * https://www.virtualbox.org/ticket/16675
 * https://www.virtualbox.org/ticket/15780


",Will
19645,Win7 VM (from p2v) freezes at random intervals,Windows,Windows,VirtualBox 6.1.10,2020-06-08T12:46:06Z,2020-06-08T12:46:06Z,"I have a Win7 VM which is a P2V result from a laptop (i used VMWare Converter Standalone for the task). I then created a new VBox VM and used the .VMDK as a HDD.

I turned on the VM, let it discover all the drivers it wanted, restarted, etc. Finally i installed VBox drivers from the VM, restarted and everything seemed to work OK. Also performed several old drivers cleanup (uninstallations and removals from device driver), to minimize possible issues.

The VM works fine, except that after some time (randomly, usually 10-20 minutes), it just freezes. VBox's window is responsive but the guest OS is completely frozen. Trying to close the VM from the VBox's close window button, i select ""Send the shutdown signal"" and then press OK. It waits a few seconds and then it just closes the window.

Of course, the next time i start it, Windows report they had not been shutdown properly the last time. Also, the original laptop works just fine.",Wand
19651,DNS not working with NAT on some networks.,Windows,Linux,VirtualBox 6.1.10,2020-06-09T12:39:59Z,2020-06-09T12:39:59Z,"Host is Win10, Guest is Debian 10.  Network set to NAT with TCP port 22 forwarded (though ssh will not work either)

Internet access worked fine until I changed WIFI networks. DNS does not seem to work. I can ping the DNS server, but DNS resolving does not work.  I've noticed some strange patterns.  At home it works fine. When I connect to my cellphone hotspot while at home everything worked too. At my hotel, at first it would not work. Then trying at my remote office guest wifi network, it also would not work. Then trying my cellphone hotspot mode, it also would not work. However, upon returning back to my hotel, it suddenly worked. I have the exact same pattern with trying to connect my wireguard vpn. Note back at the hotel, once I connect the vpn, dns stops working, it is unable to contact the dns server on my vpn, eventhough the host is able to.  Virtualbox sees the network changes, debian updates the network configuration, I can ping addresses outside, but dns fails with the ICMP issue. I've noticed that the DNS issue is ok if I switch to a bridged network. Unfortunately, some networks will only give me one IP so getting it to work with NAT is preferred.


In the VM log, I see:
{{{
00:00:18.130180 NAT: Link up
00:00:19.424766 NAT: DHCP offered IP address 10.0.2.15
}}}
On the guest, in network manager, it has a 10.0.2.15 IP address and is able to get DNS servers matching what I have on the host. /etc/resolv.conf has the correct servers
I have tried rebooting the VM. I've tried turning off the firewall on the host.


/etc/resolv.conf:
{{{
nameserver 1.1.1.1
}}}
ping 1.1.1.1 works
{{{
11:38:39.397764 IP 10.0.2.15 > 1.1.1.1: ICMP echo request, id 2960, seq 2, length 64
11:38:39.436573 IP 1.1.1.1 > 10.0.2.15: ICMP echo reply, id 2960, seq 2, length 64
}}}
dig @1.1.1.1 google.com does not work
{{{
11:38:43.814134 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:43.814861 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
11:38:45.697058 IP 10.0.2.15.50263 > 172.30.0.27.53: 32978+ AAAA? clients3.google.com. (37)
11:38:45.697650 IP 10.0.2.15.46410 > 172.30.0.27.53: 56459+ A? clients3.google.com. (37)
11:38:45.698116 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:45.698446 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:48.814785 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:48.816463 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
}}}",eng3
19647,Fedora: Removing suid root bit from VBoxDRMClient,all,Linux,VirtualBox 6.1.10,2020-06-09T13:25:57Z,2020-06-09T13:25:57Z,"From: ""Hans de Goede"" <>
To: vbox-dev@virtualbox.org
Subject: [vbox-dev] Removing suid root bit from VBoxDRMClient
Date: Mon, 08 Jun 2020 17:46:58 +0200

While looking into upgrading the Fedora virtualbox-guest-additions  
packages to 6.0.10
I noticed that the  ""VBoxClient --vmsvga-x11"" call in VBoxClient-all has been replaced
with ""VBoxClient --vmsvga"" and that that one will either behave as the old --vmsvga-x11
version (when running under a X11 session) or it will start  
/usr/bin/VBoxDRMClient.

I added /usr/bin/VBoxDRMClient to the Fedora packages, but after that  
resizing of a GNOME3 as Wayland-compositor session inside the guest still did not work.

The issue seems to be that /usr/bin/VBoxDRMClient needs more rights, I  
guess that the upstream version of the guest-additions installs it suid root ?

That is not necessary and since Fedora ships virtualbox-guest-additions as  part of the default workstation install we would like to avoid adding another suid root binary
to the default install.

Instead I've written a udev rule + systemd service to replace the  
""VBoxClient --vmsvga"" call inside VBoxClient-all. These config files will start  /usr/bin/VBoxDRMClient
when running inside a VBox VM with VMSVGA graphics. Note this will now run  independent
of the type of session (X11 or Wayland) running inside the VM. This means that X11
sessions now also use VBoxDRMClient rather then VBoxClient --vmsvga-x11  
for resizing.

This works fine and if upstream adopts this, then the VBoxClient  
--vmsvga-x11 can be dropped.

The udev rule and systemd file can be found here. Feel free to use these under the MIT license:

[https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/VirtualBox-60-vboxguest.rules][[BR]]
[https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/vboxclient.service][[BR]]

",Frank Batschulat (Oracle)
19652,Segfault in vmsvgaR3PortReportMonitorPositions (vboxvga),Linux,Linux,VirtualBox 6.1.10,2020-06-10T07:31:31Z,2020-06-10T07:31:31Z,"Linux with 4.2.0 kernel (Astra Linux 1.5) crashes VM upon login with legacy vboxvga controller. Host: Fedora 32, guest: Astra Linux 1.5

{{{
#0  0x00007f0aeb03ad7e in vmsvgaR3PortReportMonitorPositions(PDMIDISPLAYPORT*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#1  0x00007f0b325a79b8 in Display::i_handleUpdateMonitorPositions(unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#2  0x00007f0b325ca018 in vmmdevUpdateMonitorPositions(PDMIVMMDEVCONNECTOR*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#3  0x00007f0aeaffe7b1 in vmmdevRequestHandler(PDMDEVINSR3*, void*, unsigned short, unsigned int, unsigned int) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#4  0x00007f0b38310922 in IOMIOPortWrite () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#5  0x00007f0b38208be2 in IOMR3ProcessForceFlag () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#6  0x00007f0b381ff4e5 in emR3HighPriorityPostForcedActions () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#7  0x00007f0b38202ef2 in emR3HmExecute () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#8  0x00007f0b38200c4e in EMR3ExecuteVM () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#9  0x00007f0b382635f0 in vmR3EmulationThreadWithId(RTTHREADINT*, UVMCPU*, unsigned int) () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#10 0x00007f0b54e17f14 in rtThreadMain () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#11 0x00007f0b54ece55e in rtThreadNativeMain(void*) () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#12 0x00007f0b551b9432 in start_thread () from /app/lib64/libpthread.so.0
No symbol table info available.
#13 0x00007f0b550e09d3 in clone () from /app/lib64/libc.so.6
No symbol table info available.
}}}
",Max Fedotov
19648,VirtualBox mounts the same ISO in multiple virtual CD/DVD drives.,other,other,VirtualBox 6.1.10,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
15374,Virtual HDD becomes unavailable for guest : with AHCI#0: Port x reset,Linux,Linux,VirtualBox 5.0.14,2020-06-10T12:34:49Z,2020-06-10T12:34:49Z,"It looks a like #9975 in symptoms but with linux/linux host/guest and no windows involved. Also errors logs are not as much verbose.

The guest runs find for a (what looks like) random duration ranging from a few weeks to one year then without clear causes one virtual disk becomes unavailable and creates sda i/o errors on guest with one only line in the Vbox.log file :

{{{
1900:51:41.454153 AHCI#0: Port 2 reset
}}}

A kill $pid + VboxManage startvm restores every thing to normal until next time.

I have seen this behavior on virtualbox version back to 4.3.6r91406 and up to 5.0.14.
When the crash occurs, system load on host isn't particularly high, i/o aren't particularly high neither on host or guest.
I've seen it on SATA rotative disks in RAID 1 and 5, SATA SSD disks raid 1

Guests linux kernels ranges from 2.6.18 up to 3.2.x
Guest hosts are Linux debian 6.0 7.0 or 8.0
All vdi files are used as SATA controled drives


I keep a log of crashed VMs to try discovering common criteria to narrow it down, but nothing really jump to the eye beside :

- low load/low i/o VMs don't seam to crash
- On some host server  with different hardware I never had any crash

I know my report is quite poor in details, but I'll try to keep it updated. During the mean time is there a way to make those ""virtual disk reset"" more verbose ?



",sylvain Gplservice
18089,Host CPU load 100% for idle guest,Mac OS X,Linux,VirtualBox 5.2.20,2020-06-10T16:51:40Z,2020-06-10T16:51:40Z,"Host: macOS 10.12.6
Guest: Linux (Ubuntu 16.04)

After upgrading Virtualbox to 5.2.20, I ran a single guest which I'd used many times before.  The guest decided to do an auto-update, which is fine.

However even after the update had finished, on the *host*, CPU used by the VirtualBox process remained stuck at 100%, as shown by Activity Monitor and (here) ""top -o cpu"":

{{{
Processes: 326 total, 3 running, 323 sleeping, 1550 threads                                                         08:15:02
Load Avg: 2.34, 2.50, 2.10  CPU usage: 31.47% user, 7.26% sys, 61.25% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 65898 total, 7787M resident, 147M private, 1418M shared.
PhysMem: 14G used (4448M wired), 2268M unused. VM: 879G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 197313/179M in, 123489/30M out. Disks: 385658/8849M read, 161264/4111M written.

PID   COMMAND      %CPU  TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS         %CPU_ME %CPU_OTHRS
1810  VirtualBoxVM 105.5 17:19.54 44/1  5    392   2193M  8048K  0B     1810 1805 running  *1[5]          0.00000 0.00000
335   iTerm2       14.6  01:56.18 11    5    281-  164M-  34M-   0B     335  1    sleeping *0[305]        0.04101 1.50065
}}}

But inside the *guest*, CPU was ~99% idle.  Again, here with ""top"" but inside the guest:

{{{
top - 08:16:00 up 44 min,  1 user,  load average: 0.00, 0.07, 0.11
Tasks: 583 total,   1 running, 582 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.3 us,  0.3 sy,  0.0 ni, 99.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  2048156 total,   238796 free,  1136680 used,   672680 buff/cache
KiB Swap:   786428 total,   747596 free,    38832 used.   554244 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
 4441 101001    20   0 2552704  62904  14900 S  0.3  3.1   0:05.32 java
 7579 brian     20   0   42240   4268   3172 R  0.3  0.2   0:00.02 top
    1 root      20   0   38320   6280   4016 S  0.0  0.3   0:02.16 systemd
}}}

After shutting down and restarting the guest, the problem went away. This again on the host:

{{{
Processes: 325 total, 3 running, 322 sleeping, 1501 threads                                                         08:18:39
Load Avg: 1.90, 2.28, 2.10  CPU usage: 2.68% user, 6.34% sys, 90.97% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 66300 total, 7793M resident, 150M private, 1428M shared.
PhysMem: 14G used (4458M wired), 2178M unused. VM: 876G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 201757/182M in, 127536/32M out. Disks: 419879/9460M read, 166954/4317M written.

PID   COMMAND      %CPU TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS          %CPU_ME %CPU_OTHRS
6140  VirtualBoxVM 7.8  00:49.13 41    4    396   2144M  18M    0B     6140 1805 sleeping *1[4]           0.00000 0.00000
0     kernel_task  7.1  07:13.29 134/4 0    2     1199M  0B     0B     0    0    running   0[0]           0.00000 0.00000
}}}
",bcandler
19653,Clipboard sharing suddenly stops working in reccent release,Linux,all,VirtualBox 6.1.10,2020-06-10T19:17:19Z,2020-06-10T19:17:19Z,"VB 6.1.10 r138449 the host is Ubuntu 18.04.04. Shared clipboard periodically stops working on guests after many hours of working. There is no new lines in the virtual machine log file after the event. If two guests are running it may stop working only for one of them and still works fine on another one. I've observed this on different guests Win10, Linux, WinXP, so this is probably a bug on the host side. Interestingly restart of the guests brings feature back into operational state. 

It seams you are changing the code of the shared clipboard infrastructure due to multiple crash reports #19226 and I would say that the most stable release so far was VB 6.1.8. It didn't crash on copy&paste (not as often as previous releases) and the shared clipboard is again broken in the current VB 6.1.10.",GnomeUser
19654,Clipboard sharing suddenly stops working in reccent release,Linux,all,VirtualBox 6.1.10,2020-06-10T19:17:26Z,2020-06-10T19:17:26Z,"VB 6.1.10 r138449 the host is Ubuntu 18.04.04. Shared clipboard periodically stops working on guests after many hours of working. There is no new lines in the virtual machine log file after the event. If two guests are running it may stop working only for one of them and still works fine on another one. I've observed this on different guests Win10, Linux, WinXP, so this is probably a bug on the host side. Interestingly restart of the guests brings feature back into operational state. 

It seams you are changing the code of the shared clipboard infrastructure due to multiple crash reports #19226 and I would say that the most stable release so far was VB 6.1.8. It didn't crash on copy&paste (not as often as previous releases) and the shared clipboard is again broken in the current VB 6.1.10.",GnomeUser
19656,Error when starting VBoxSVC on alpine linux (MUSL),Linux,Linux,VirtualBox 6.1.8,2020-06-11T07:20:05Z,2020-06-11T07:20:05Z,"Hello

I have compiled the virtualbox in alpine linux (MUSL), but when I run it, I get a failure of XPCOM

this is the mistake

VBoxSVC: error: Failed to initialize XPCOM! 
(rc=NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
VBoxSVC: error: Failed to shutdown XPCOM! (rc=Unknown Status 0x80460016)
XPCOM server has shutdown.",Sodomon
19643,Shift key status leaking from Guest to Host,Windows,Windows,VirtualBox 6.1.10,2020-06-11T10:28:15Z,2020-06-11T10:28:15Z,"If a VBox session is running and has focus, and an app in that guest session has focus, e.g. TextPad, and the shift key is pushed, you can push say a and TextPad displays A, so it has responded to the shift. 

An app running in the host that is monitoring for the shift using the standard GetAsyncKeyState function receives notification that the shift key is down and thus will respond to it.

I believed the keybard, when captured, should act on all keyboard actions, and not be left for the host (I guess certain reserved keystrokes would be exempt).

This same scenario works fine on VMWare, which is what I am changing from - has worked for many years.

I cannot provide a workaround.

I can provide a program if required to monitor the shift status on the host.",Ken S
18912,VBOXSvga : lots of flickering with Windows Guests on Linux Hosts,Linux,Windows,VirtualBox 6.0.12,2020-06-11T11:34:16Z,2020-06-11T11:34:16Z,"Hi,

I tried the VBOXSvga driver with 3D support for the following guests :
- Windows VISTA
- Windows 7
- Windows 8
- Windows 10

I notice a lot of bugs, like Skype displaying a black window and more importantly transparency bugs and flickering. If I disable 3D support Skype remains buggy but flickering disappears. Now if I revert to VBoxVGA w/ 3D support enabled all is fine.

My host is as follows :
- Intel Core i7 4790
- 32 GB RAM
- NVidia GeForce 2070 SUPER w/ driver 430.40
- Debian Buster AMD64

I enabled the following environment variable as a workaround to the flickering bug we had w/ NVidia driver :
CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0

Perhaps is it the culprit, or is it something else ?",gojul
19594,Mouse behaves badly with two screens Guest Additions 6.1.8,Linux,Linux,VirtualBox 6.1.8,2020-06-11T15:04:39Z,2020-06-11T15:04:39Z,"My configuration is 
Host: Debian Stretch
Guests: Debian Buster (two screens), Debian Buster (one screen), Ubuntu Focal Fossa Server
Desktop: Gnome classic on host and guests (including Ubuntu server)

When I upgraded from 6.1.6 to 6.1.8 (including an upgrade of the guest additions) the mouse did not behave correctly on the guests with two screens and the secondary screen stays black even though the window for the second screen opens. When I move the mouse over a widget and click, it sometimes does nothing and sometimes activates a different window. Downgrading to VBox 6.0 and installing the 6.0 guest additions fixed the problem.

I recall having a similar or perhaps exactly the same problem with my two screen guests in an earlier upgrade of VBox (I don't remember the versions involved). I think there was a bug report in that previous case as well.",linux_user_1
19660,Guest Crashes with in a minutes,Windows,Windows,VirtualBox 6.0.20,2020-06-11T18:27:12Z,2020-06-11T18:27:12Z,After just started the virtual box manager. if we wait like 2 or 3 minutes  the mouse becomes unresponsive and eventually i cant open anything. The only thing i can do is close the virtual box directly and restart it and its happening often.,k00000
19270,Window not expanding under Guest Additions 6.1.2,other,Windows,VirtualBox 6.1.2,2020-06-13T02:02:41Z,2020-06-13T02:02:41Z,"In VirtualBox Guest Additions 6.1.2, the Windows version does not auto-expand VM windows.",Dman 028
19666,I tried to install Latest Kali linux on Latest Virtual Box. i am not able to get installed on to my Windows laptop,Windows,Linux,VirtualBox 6.1.10,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,,Universal007
19222,Guest OS Windows 7 have 0x116 BSOD,other,other,VirtualBox 6.1.0,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
19655,Linux guest crashes if VboxAdditions are installed,Windows,Linux,VirtualBox 6.1.10,2020-06-15T07:31:06Z,2020-06-15T07:31:06Z,"Installing guest additions on LinuxMint 19.3 and Debian 10 results in a crash on startup of the VM.
The vboxadd.service will not start.
If the guest additions are removed the guest starts successfully.",S.Pendl
19661,virtual sanal makine hatası önemlid,other,other,VirtualBox 6.1.10,2020-06-15T07:49:32Z,2020-06-15T07:49:32Z,"Merhaba, görsel ektedir.",ferittrn
17811,VirtualBox (vboxdrv) installation FAILED on some Windows 7 PCs,Windows,other,VirtualBox 5.2.12,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
19668,Result Code: E_INVALIDARG (0x80070507),Windows,other,VirtualBox 6.1.10,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
19669,"Windows 10 Guest just crshed, no idea why",Linux,Windows,VirtualBox 6.1.10,2020-06-16T09:24:58Z,2020-06-16T09:24:58Z,"Starting VirtualBox 6.1.6, then 6.1.8, and now 6.1.10, on a Ubuntu host, my Windows 10 Guest VM started crashing for some unknown reason. It happened once when I copied/pasted some text from the guest to the host, but this morning I didn't do anything special. Just editing something...

Sorry that I can't give more info.

I think I'll revert to 6.1.4 for the time being.",D.Bugger
19671,"VirtualBoxVM crash, rtR3WinUnhandledXcptFilter caught an exception",Windows,Linux,VirtualBox 6.1.10,2020-06-19T08:48:49Z,2020-06-19T08:48:49Z,"At time VirtualBoxVM.exe crashes with a pop-up, ""The instruction at '0xXX' referenced memory at '0xXX'. The memory could not be read.

And this issue can be easily reproduced if I use Google chrome within VM.

Vbox is installed in Window 10 & Ubuntu 18.04 is installed Vbox.

Hereby I'm attaching the log file as well.",pearleye
19672,Single step emulation bug,Mac OS X,all,VirtualBox 6.1.10,2020-06-19T08:52:30Z,2020-06-19T08:52:30Z,"Single stepping code in a guest VM doesn't work correctly with I/O instructions.

I first noticed the problem in the built in kernel debugger in my OS. By further examination I also noted that the problem could be reproduced in Windows XP with both the 16-bit command line debugger and an a free 32-bit version of the same. Thus the problem is general.

The problem was detected with single stepping the out instruction. The instruction following the out instruction will also be single stepped, causing the guest VMs exception #1 to point to the wrong instruction.

out 80,al
call Foo

will point to first instruction in Foo instead of the call Foo line.

As RDTSC instruction has been fixed in a similar situation, I assume you have not applied the fix on all privileged instructions like IN, OUT, INT nn etc. The VM emulator should check the TF flag in the instruction emulator and emulate exception #1 in addition if it's set.

I have included the VBOXBUG.COM file that reproduce the problem in Windows XP debug command.

debug VBOXBUG.COM will load the program.

Write U for disassembling and you see what it does. For every out instruction we trace into the subroutine that is called after the OUT instruction instead of stopping at the CALL instruction following it.

You use the T (TRACE INTO)command for single stepping. Perhaps P (TRACE OVER) generates the same problem.

Best regards,

B-O Bergman
PQURE Technology",B-O
19673,"offering, downloading and installing new versions not supported by host",Mac OS X,other,VirtualBox 6.1.10,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
19675,DHCP server mac address conflicts with nat-host mac-address,Windows,Linux,VirtualBox 6.1.10,2020-06-19T19:56:40Z,2020-06-19T19:56:40Z,"
https://gitlab.alpinelinux.org/alpine/aports/-/issues/11669

When the two mac-addresses of the dhcp server and the emulated-host interface in NatNetwork are different, the arp cache may end up with the mac address of host entered as that from the dhcp. WHen that happens further communcation with host (CIFS/ssh) fails.

The eesolution was to set the dhcp server from the default 10.1.x.2 to 10.1.x.5. Then mac addresses don't clash

There should be a vboxmanage setting to set the mac address of the 
host-ip and of the dhcp-server-ip ",gkamathh
19676,Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel,Windows,Linux,VirtualBox 6.1.10,2020-06-20T12:35:32Z,2020-06-20T12:35:32Z,"Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel
Video: https://youtu.be/MdocMGLR2_M
Restarting W/O crashes on Windows 95.
Bliss OS (Linux Android) Restarting Crashes.
Bottom Panel crashes on all systems and many Virtual Box versions (6.X.X) (MS-DOS,Linux,OS/2 e.t.c)",Danik2343
18613,Oracle account got not merged with the correct VirtualBox account,other,other,,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
12456,Failed to Delete Snapshot,other,other,VirtualBox 4.3.4,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
19670,"Automatic VM name-based configuration assumes ""32"" means ""32-bit""",Mac OS X,Linux,VirtualBox 6.1.10,2020-06-23T11:42:20Z,2020-06-23T11:42:20Z,"Fedora 32 is not 32-bit Fedora

I attempted to set up a VM today for version 32 of Fedora x64. When I tried to create a VM named ""Fedora 32"" the creation tool assumed I meant 32-bit Fedora. This lead to several minutes of confusion as I tried to figure out why booting up the Fedora Workstation 32 x64 ISO kept telling me it couldn't run on a 32-bit processor.

I eventually figured out what had happened, and tried to manually change the VM's CPU from 32-bit to x64. However, the ISO still kept insisting that I had a 32-bit processor. Eventually, I had to destroy the VM and create one from scratch.

Not completely sure this is actually a bug, but the algorithm could be fine-tuned to work better, or perhaps provide more noticeable feedback when it changes the ""bit-ness"" of the VM.",imrazor
18969,VirtualBox manager sometimes crashes on start,Windows,other,VirtualBox 6.0.12,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
19683,Window guest display glitch in VBoxSVGA with 3D acceleration mode,Windows,Windows,VirtualBox 6.1.10,2020-06-26T01:28:25Z,2020-06-26T01:28:25Z,"Win7 host, nvidia gtx1650, Win7 guest, vbox v6.1.10 r138449, guest additions updated, VBoxSVGA with 3D acceleration mode on

The desktop of the VM is glitched, and the GUI some software don't work too.

https://youtu.be/GBEkxST6t-g

{{{
00:00:01.554556 VirtualBox VM 6.1.10 r138449 win.amd64 (Jun  4 2020 17:22:00) release log
00:00:01.554559 Log opened 2020-06-26T00:57:08.016600100Z
00:00:01.554560 Build Type: release
00:00:01.554562 OS Product: Windows 7
00:00:01.554563 OS Release: 6.1.7601
00:00:01.554564 OS Service Pack: 1
00:00:01.589427 DMI Product Name: To Be Filled By O.E.M.
00:00:01.598490 DMI Product Version: To Be Filled By O.E.M.
00:00:01.598834 Firmware type: BIOS
00:00:01.598838 Host RAM: 16313MB (15.9GB) total, 10592MB (10.3GB) available
00:00:01.598840 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:01.598840 Process ID: 5640
00:00:01.598841 Package type: WINDOWS_64BITS_GENERIC
00:00:01.602253 Installed Extension Packs:
00:00:01.602291   Oracle VM VirtualBox Extension Pack (Version: 6.1.10 r138449; VRDE Module: VBoxVRDP)
00:00:01.603077 Console: Machine state changed to 'Starting'
00:00:01.630079 Qt version: 5.6.2
00:00:01.632115 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.681454 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:01.681465 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:01.681466 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:01.682637 Guest OS type: 'Windows7_64'
00:00:01.683918 fHMForced=true - No raw-mode support in this build!
00:00:01.689061 File system of 'V:\VBox\Asteroid-7\Snapshots' (snapshots) is ntfs
00:00:01.689066 File system of 'V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi' is ntfs
00:00:01.694215 File system of 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (DVD) is ntfs
00:00:01.706365 Shared Clipboard: Service loaded
00:00:01.706371 Shared Clipboard: Mode: Bidirectional
00:00:01.706520 Shared Clipboard: Service running in normal mode
00:00:01.711359 Drag and drop service loaded
00:00:01.711364 Drag and drop mode: Host to Guest
00:00:01.718761 ************************* CFGM dump *************************
00:00:01.718763 [/] (level 0)
00:00:01.718765   CpuExecutionCap   <integer> = 0x0000000000000064 (100)
00:00:01.718767   EnablePAE         <integer> = 0x0000000000000001 (1)
00:00:01.718768   HMEnabled         <integer> = 0x0000000000000001 (1)
00:00:01.718768   MemBalloonSize    <integer> = 0x0000000000000000 (0)
00:00:01.718769   Name              <string>  = ""Asteroid-7"" (cb=11)
00:00:01.718770   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:01.718770   PageFusionAllowed <integer> = 0x0000000000000000 (0)
00:00:01.718771   RamHoleSize       <integer> = 0x0000000020000000 (536 870 912, 512 MB)
00:00:01.718772   RamSize           <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:01.718773   TimerMillies      <integer> = 0x000000000000000a (10)
00:00:01.718774   UUID              <bytes>   = ""39 73 89 c4 c7 e4 e2 45 9e 93 b0 52 54 ca 40 84"" (cb=16)
00:00:01.718779 
00:00:01.718780 [/CPUM/] (level 1)
00:00:01.718780   GuestCpuName       <string>  = ""host"" (cb=5)
00:00:01.718781   NestedHWVirt       <integer> = 0x0000000000000000 (0)
00:00:01.718781   PortableCpuIdLevel <integer> = 0x0000000000000000 (0)
00:00:01.718782   SpecCtrl           <integer> = 0x0000000000000000 (0)
00:00:01.718783 
00:00:01.718783 [/CPUM/IsaExts/] (level 2)
00:00:01.718783 
00:00:01.718784 [/DBGC/] (level 1)
00:00:01.718784   GlobalInitScript <string>  = ""C:\Users\Mercury\.VirtualBox/dbgc-init"" (cb=39)
00:00:01.718785   HistoryFile      <string>  = ""C:\Users\Mercury\.VirtualBox/dbgc-history"" (cb=42)
00:00:01.718786   LocalInitScript  <string>  = ""V:\VBox\Asteroid-7/dbgc-init"" (cb=29)
00:00:01.718786 
00:00:01.718787 [/DBGF/] (level 1)
00:00:01.718787   Path <string>  = ""V:\VBox\Asteroid-7/debug/;V:\VBox\Asteroid-7/;cache*V:\VBox\Asteroid-7/dbgcache/;C:\Users\Mercury\"" (cb=99)
00:00:01.718788 
00:00:01.718788 [/Devices/] (level 1)
00:00:01.718788 
00:00:01.718789 [/Devices/8237A/] (level 2)
00:00:01.718789 
00:00:01.718789 [/Devices/8237A/0/] (level 3)
00:00:01.718790   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718791 
00:00:01.718791 [/Devices/GIMDev/] (level 2)
00:00:01.718791 
00:00:01.718791 [/Devices/GIMDev/0/] (level 3)
00:00:01.718792   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718792 
00:00:01.718792 [/Devices/VMMDev/] (level 2)
00:00:01.718793 
00:00:01.718793 [/Devices/VMMDev/0/] (level 3)
00:00:01.718794   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718795   PCIDeviceNo   <integer> = 0x0000000000000004 (4)
00:00:01.718795   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718796   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718796 
00:00:01.718796 [/Devices/VMMDev/0/Config/] (level 4)
00:00:01.718797   GuestCoreDumpDir <string>  = ""V:\VBox\Asteroid-7\Snapshots"" (cb=29)
00:00:01.718798 
00:00:01.718798 [/Devices/VMMDev/0/LUN#0/] (level 4)
00:00:01.718798   Driver <string>  = ""HGCM"" (cb=5)
00:00:01.718799 
00:00:01.718799 [/Devices/VMMDev/0/LUN#0/Config/] (level 5)
00:00:01.718800   Object <integer> = 0x0000000006f1e190 (116 515 216)
00:00:01.718801 
00:00:01.718801 [/Devices/VMMDev/0/LUN#999/] (level 4)
00:00:01.718801   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718802 
00:00:01.718802 [/Devices/VMMDev/0/LUN#999/Config/] (level 5)
00:00:01.718803   First   <integer> = 0x0000000000000000 (0)
00:00:01.718803   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718804   papLeds <integer> = 0x0000000003bf5250 (62 870 096)
00:00:01.718804 
00:00:01.718805 [/Devices/acpi/] (level 2)
00:00:01.718805 
00:00:01.718805 [/Devices/acpi/0/] (level 3)
00:00:01.718806   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718806   PCIDeviceNo   <integer> = 0x0000000000000007 (7)
00:00:01.718807   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718807   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718808 
00:00:01.718808 [/Devices/acpi/0/Config/] (level 4)
00:00:01.718808   CpuHotPlug          <integer> = 0x0000000000000000 (0)
00:00:01.718809   FdcEnabled          <integer> = 0x0000000000000000 (0)
00:00:01.718809   HostBusPciAddress   <integer> = 0x0000000000000000 (0)
00:00:01.718810   HpetEnabled         <integer> = 0x0000000000000000 (0)
00:00:01.718810   IOAPIC              <integer> = 0x0000000000000001 (1)
00:00:01.718811   IocPciAddress       <integer> = 0x0000000000010000 (65 536)
00:00:01.718812   NumCPUs             <integer> = 0x0000000000000002 (2)
00:00:01.718812   Parallel0IoPortBase <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel0Irq        <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel1IoPortBase <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel1Irq        <integer> = 0x0000000000000000 (0)
00:00:01.718814   Serial0IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:01.718814   Serial0Irq          <integer> = 0x0000000000000000 (0)
00:00:01.718815   Serial1IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:01.718815   Serial1Irq          <integer> = 0x0000000000000000 (0)
00:00:01.718816   ShowCpu             <integer> = 0x0000000000000001 (1)
00:00:01.718816   ShowRtc             <integer> = 0x0000000000000000 (0)
00:00:01.718817   SmcEnabled          <integer> = 0x0000000000000000 (0)
00:00:01.718817 
00:00:01.718817 [/Devices/acpi/0/LUN#0/] (level 4)
00:00:01.718818   Driver <string>  = ""ACPIHost"" (cb=9)
00:00:01.718818 
00:00:01.718819 [/Devices/acpi/0/LUN#0/Config/] (level 5)
00:00:01.718819 
00:00:01.718819 [/Devices/acpi/0/LUN#1/] (level 4)
00:00:01.718820   Driver <string>  = ""ACPICpu"" (cb=8)
00:00:01.718820 
00:00:01.718821 [/Devices/acpi/0/LUN#1/Config/] (level 5)
00:00:01.718821 
00:00:01.718821 [/Devices/ahci/] (level 2)
00:00:01.718822 
00:00:01.718822 [/Devices/ahci/0/] (level 3)
00:00:01.718823   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718823   PCIDeviceNo   <integer> = 0x000000000000000d (13)
00:00:01.718824   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718824   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718825 
00:00:01.718825 [/Devices/ahci/0/Config/] (level 4)
00:00:01.718825   Bootable  <integer> = 0x0000000000000001 (1)
00:00:01.718826   PortCount <integer> = 0x0000000000000002 (2)
00:00:01.718826 
00:00:01.718826 [/Devices/ahci/0/Config/Port0/] (level 5)
00:00:01.718827   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:01.718827 
00:00:01.718828 [/Devices/ahci/0/Config/Port1/] (level 5)
00:00:01.718828   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:01.718829 
00:00:01.718829 [/Devices/ahci/0/LUN#0/] (level 4)
00:00:01.718829   Driver <string>  = ""VD"" (cb=3)
00:00:01.718830 
00:00:01.718830 [/Devices/ahci/0/LUN#0/Config/] (level 5)
00:00:01.718831   BlockCache <integer> = 0x0000000000000001 (1)
00:00:01.718831   Format     <string>  = ""VDI"" (cb=4)
00:00:01.718832   Mountable  <integer> = 0x0000000000000000 (0)
00:00:01.718832   Path       <string>  = ""V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi"" (cb=72)
00:00:01.718833   Type       <string>  = ""HardDisk"" (cb=9)
00:00:01.718834   UseNewIo   <integer> = 0x0000000000000001 (1)
00:00:01.718834 
00:00:01.718834 [/Devices/ahci/0/LUN#0/Config/Parent/] (level 6)
00:00:01.718835   Format <string>  = ""VDI"" (cb=4)
00:00:01.718835   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{13d95ad9-6645-4a1a-a124-92c2acdf50aa}.vdi"" (cb=72)
00:00:01.718836 
00:00:01.718836 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/] (level 7)
00:00:01.718837   Format <string>  = ""VDI"" (cb=4)
00:00:01.718837   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{7d214b65-fb63-4e15-8517-9a4917deb9f7}.vdi"" (cb=72)
00:00:01.718838 
00:00:01.718838 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/] (level 8)
00:00:01.718839   Format <string>  = ""VDI"" (cb=4)
00:00:01.718839   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{3476a280-0799-4492-b80a-3f49e19328d1}.vdi"" (cb=72)
00:00:01.718840 
00:00:01.718840 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/] (level 9)
00:00:01.718841   Format <string>  = ""VDI"" (cb=4)
00:00:01.718842   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{5e7c1acb-8345-4fd8-8230-07cc65b4a7c1}.vdi"" (cb=72)
00:00:01.718842 
00:00:01.718842 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/] (level 10)
00:00:01.718843   Format <string>  = ""VDI"" (cb=4)
00:00:01.718844   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{d06b5feb-30d7-4c80-86f1-089b0159c660}.vdi"" (cb=72)
00:00:01.718844 
00:00:01.718844 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/] (level 11)
00:00:01.718845   Format <string>  = ""VDI"" (cb=4)
00:00:01.718846   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{00d317fd-75eb-4e52-bc4c-cd16a0cd44c6}.vdi"" (cb=72)
00:00:01.718846 
00:00:01.718846 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 12)
00:00:01.718847   Format <string>  = ""VDI"" (cb=4)
00:00:01.718848   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{702c5788-4b07-4854-afaa-11069398a139}.vdi"" (cb=72)
00:00:01.718848 
00:00:01.718848 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 13)
00:00:01.718850   Format <string>  = ""VDI"" (cb=4)
00:00:01.718850   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{bd5df2b9-1b74-4058-b5dc-de9c354c23c5}.vdi"" (cb=72)
00:00:01.718850 
00:00:01.718851 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 14)
00:00:01.718852   Format <string>  = ""VDI"" (cb=4)
00:00:01.718852   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{e14a6301-e7ab-4f38-919a-474ba2d2224f}.vdi"" (cb=72)
00:00:01.718853 
00:00:01.718853 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 15)
00:00:01.718854   Format <string>  = ""VDI"" (cb=4)
00:00:01.718854   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{bbae5348-a1c8-4eb7-801e-5a75b173af2f}.vdi"" (cb=72)
00:00:01.718855 
00:00:01.718855 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 16)
00:00:01.718857   Format <string>  = ""VDI"" (cb=4)
00:00:01.718857   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{281e38e5-ff1b-4d6c-9523-3794348b861e}.vdi"" (cb=72)
00:00:01.718857 
00:00:01.718858 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 17)
00:00:01.718859   Format <string>  = ""VDI"" (cb=4)
00:00:01.718859   Path   <string>  = ""V:\VBox\Asteroid-7\Asteroid-7.vdi"" (cb=34)
00:00:01.718860 
00:00:01.718860 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 18)
00:00:01.718862   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718862 
00:00:01.718862 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 17)
00:00:01.718864   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718864 
00:00:01.718864 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 16)
00:00:01.718865   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718866 
00:00:01.718866 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 15)
00:00:01.718867   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718868 
00:00:01.718868 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 14)
00:00:01.718869   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718869 
00:00:01.718870 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 13)
00:00:01.718871   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718871 
00:00:01.718871 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 12)
00:00:01.718872   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718873 
00:00:01.718873 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 11)
00:00:01.718874   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718874 
00:00:01.718875 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/VDConfig/] (level 10)
00:00:01.718876   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718876 
00:00:01.718876 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/VDConfig/] (level 9)
00:00:01.718877   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718877 
00:00:01.718878 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/VDConfig/] (level 8)
00:00:01.718878   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718879 
00:00:01.718879 [/Devices/ahci/0/LUN#0/Config/Parent/VDConfig/] (level 7)
00:00:01.718880   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718880 
00:00:01.718880 [/Devices/ahci/0/LUN#0/Config/Plugins/] (level 6)
00:00:01.718881 
00:00:01.718881 [/Devices/ahci/0/LUN#0/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:01.718882   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:01.718883 
00:00:01.718883 [/Devices/ahci/0/LUN#0/Config/VDConfig/] (level 6)
00:00:01.718883   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718884 
00:00:01.718884 [/Devices/ahci/0/LUN#1/] (level 4)
00:00:01.718885   Driver <string>  = ""SCSI"" (cb=5)
00:00:01.718885 
00:00:01.718885 [/Devices/ahci/0/LUN#1/AttachedDriver/] (level 5)
00:00:01.718886   Driver <string>  = ""VD"" (cb=3)
00:00:01.718886 
00:00:01.718886 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:01.718887   Format    <string>  = ""RAW"" (cb=4)
00:00:01.718888   Mountable <integer> = 0x0000000000000001 (1)
00:00:01.718888   Path      <string>  = ""C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso"" (cb=58)
00:00:01.718889   ReadOnly  <integer> = 0x0000000000000001 (1)
00:00:01.718889   Type      <string>  = ""DVD"" (cb=4)
00:00:01.718889   UseNewIo  <integer> = 0x0000000000000001 (1)
00:00:01.718890 
00:00:01.718890 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/Plugins/] (level 7)
00:00:01.718891 
00:00:01.718891 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/Plugins/VDPluginCrypt/] (level 8)
00:00:01.718892   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:01.718892 
00:00:01.718893 [/Devices/ahci/0/LUN#999/] (level 4)
00:00:01.718893   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718894 
00:00:01.718894 [/Devices/ahci/0/LUN#999/Config/] (level 5)
00:00:01.718894   DeviceInstance        <string>  = ""ahci/0"" (cb=7)
00:00:01.718895   First                 <integer> = 0x0000000000000000 (0)
00:00:01.718895   Last                  <integer> = 0x0000000000000001 (1)
00:00:01.718896   pConsole              <integer> = 0x0000000003bf4990 (62 867 856)
00:00:01.718897   papLeds               <integer> = 0x0000000003bf4dd0 (62 868 944)
00:00:01.718898   pmapMediumAttachments <integer> = 0x0000000003bf5270 (62 870 128)
00:00:01.718898 
00:00:01.718899 [/Devices/apic/] (level 2)
00:00:01.718899 
00:00:01.718899 [/Devices/apic/0/] (level 3)
00:00:01.718900   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718900 
00:00:01.718900 [/Devices/apic/0/Config/] (level 4)
00:00:01.718901   IOAPIC  <integer> = 0x0000000000000001 (1)
00:00:01.718901   Mode    <integer> = 0x0000000000000002 (2)
00:00:01.718902   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.718902 
00:00:01.718902 [/Devices/e1000/] (level 2)
00:00:01.718903 
00:00:01.718903 [/Devices/e1000/0/] (level 3)
00:00:01.718904   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718904   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:01.718905   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718905   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718905 
00:00:01.718906 [/Devices/e1000/0/Config/] (level 4)
00:00:01.718906   AdapterType    <integer> = 0x0000000000000000 (0)
00:00:01.718907   CableConnected <integer> = 0x0000000000000001 (1)
00:00:01.718907   LineSpeed      <integer> = 0x0000000000000000 (0)
00:00:01.718907   MAC            <bytes>   = ""08 00 27 07 bb b0"" (cb=6)
00:00:01.718908 
00:00:01.718909 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:01.718909   Driver <string>  = ""NAT"" (cb=4)
00:00:01.718910 
00:00:01.718910 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:01.718911   AliasMode       <integer> = 0x0000000000000000 (0)
00:00:01.718911   BootFile        <string>  = ""Asteroid-7.pxe"" (cb=15)
00:00:01.718912   DNSProxy        <integer> = 0x0000000000000000 (0)
00:00:01.718912   Network         <string>  = ""10.0.2.0/24"" (cb=12)
00:00:01.718913   PassDomain      <integer> = 0x0000000000000001 (1)
00:00:01.718913   TFTPPrefix      <string>  = ""C:\Users\Mercury\.VirtualBox\TFTP"" (cb=34)
00:00:01.718914   UseHostResolver <integer> = 0x0000000000000000 (0)
00:00:01.718914 
00:00:01.718914 [/Devices/e1000/0/LUN#999/] (level 4)
00:00:01.718915   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718915 
00:00:01.718915 [/Devices/e1000/0/LUN#999/Config/] (level 5)
00:00:01.718916   First   <integer> = 0x0000000000000000 (0)
00:00:01.718917   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718917   papLeds <integer> = 0x0000000003bf5130 (62 869 808)
00:00:01.718918 
00:00:01.718918 [/Devices/hda/] (level 2)
00:00:01.718918 
00:00:01.718918 [/Devices/hda/0/] (level 3)
00:00:01.718919   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718919   PCIDeviceNo   <integer> = 0x0000000000000005 (5)
00:00:01.718920   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718920   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718921 
00:00:01.718921 [/Devices/hda/0/AudioConfig/] (level 4)
00:00:01.718922 
00:00:01.718922 [/Devices/hda/0/Config/] (level 4)
00:00:01.718922   DebugEnabled <integer> = 0x0000000000000000 (0)
00:00:01.718923 
00:00:01.718923 [/Devices/hda/0/LUN#0/] (level 4)
00:00:01.718923   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718924 
00:00:01.718924 [/Devices/hda/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.718925   Driver <string>  = ""DSoundAudio"" (cb=12)
00:00:01.718925 
00:00:01.718925 [/Devices/hda/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.718926   StreamName <string>  = ""Asteroid-7"" (cb=11)
00:00:01.718926 
00:00:01.718927 [/Devices/hda/0/LUN#0/Config/] (level 5)
00:00:01.718927   BufferSizeMs    <integer> = 0x0000000000000000 (0)
00:00:01.718928   DriverName      <string>  = ""DSoundAudio"" (cb=12)
00:00:01.718928   InputEnabled    <integer> = 0x0000000000000000 (0)
00:00:01.718929   OutputEnabled   <integer> = 0x0000000000000001 (1)
00:00:01.718929   PeriodSizeMs    <integer> = 0x0000000000000000 (0)
00:00:01.718930   PreBufferSizeMs <integer> = 0x00000000ffffffff (4 294 967 295)
00:00:01.718930 
00:00:01.718931 [/Devices/hda/0/LUN#1/] (level 4)
00:00:01.718931   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718932 
00:00:01.718932 [/Devices/hda/0/LUN#2/] (level 4)
00:00:01.718932   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718933 
00:00:01.718933 [/Devices/i8254/] (level 2)
00:00:01.718933 
00:00:01.718934 [/Devices/i8254/0/] (level 3)
00:00:01.718934 
00:00:01.718935 [/Devices/i8254/0/Config/] (level 4)
00:00:01.718935 
00:00:01.718935 [/Devices/i8259/] (level 2)
00:00:01.718936 
00:00:01.718936 [/Devices/i8259/0/] (level 3)
00:00:01.718937   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718937 
00:00:01.718937 [/Devices/i8259/0/Config/] (level 4)
00:00:01.718938 
00:00:01.718938 [/Devices/ioapic/] (level 2)
00:00:01.718938 
00:00:01.718938 [/Devices/ioapic/0/] (level 3)
00:00:01.718939   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718939 
00:00:01.718940 [/Devices/ioapic/0/Config/] (level 4)
00:00:01.718940   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.718941 
00:00:01.718941 [/Devices/mc146818/] (level 2)
00:00:01.718941 
00:00:01.718941 [/Devices/mc146818/0/] (level 3)
00:00:01.718942 
00:00:01.718942 [/Devices/mc146818/0/Config/] (level 4)
00:00:01.718943   UseUTC <integer> = 0x0000000000000000 (0)
00:00:01.718943 
00:00:01.718943 [/Devices/parallel/] (level 2)
00:00:01.718944 
00:00:01.718944 [/Devices/pcarch/] (level 2)
00:00:01.718944 
00:00:01.718944 [/Devices/pcarch/0/] (level 3)
00:00:01.718945   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718945 
00:00:01.718946 [/Devices/pcarch/0/Config/] (level 4)
00:00:01.718946 
00:00:01.718946 [/Devices/pcbios/] (level 2)
00:00:01.718947 
00:00:01.718947 [/Devices/pcbios/0/] (level 3)
00:00:01.718948   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718948 
00:00:01.718948 [/Devices/pcbios/0/Config/] (level 4)
00:00:01.718950   APIC               <integer> = 0x0000000000000001 (1)
00:00:01.718950   BootDevice0        <string>  = ""IDE"" (cb=4)
00:00:01.718951   BootDevice1        <string>  = ""DVD"" (cb=4)
00:00:01.718951   BootDevice2        <string>  = ""NONE"" (cb=5)
00:00:01.718951   BootDevice3        <string>  = ""NONE"" (cb=5)
00:00:01.718952   FloppyDevice       <string>  = ""i82078"" (cb=7)
00:00:01.718952   HardDiskDevice     <string>  = ""piix3ide"" (cb=9)
00:00:01.718953   IOAPIC             <integer> = 0x0000000000000001 (1)
00:00:01.718953   LanBootRom         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom"" (cb=100)
00:00:01.718954   McfgBase           <integer> = 0x0000000000000000 (0)
00:00:01.718954   McfgLength         <integer> = 0x0000000000000000 (0)
00:00:01.718955   NumCPUs            <integer> = 0x0000000000000002 (2)
00:00:01.718955   PXEDebug           <integer> = 0x0000000000000000 (0)
00:00:01.718956   SataHardDiskDevice <string>  = ""ahci"" (cb=5)
00:00:01.718956   SataLUN1           <integer> = 0x0000000000000000 (0)
00:00:01.718957   UUID               <bytes>   = ""39 73 89 c4 c7 e4 e2 45 9e 93 b0 52 54 ca 40 84"" (cb=16)
00:00:01.718958   UuidLe             <integer> = 0x0000000000000000 (0)
00:00:01.718958 
00:00:01.718959 [/Devices/pcbios/0/Config/NetBoot/] (level 5)
00:00:01.718960 
00:00:01.718960 [/Devices/pcbios/0/Config/NetBoot/0/] (level 6)
00:00:01.718961   NIC           <integer> = 0x0000000000000000 (0)
00:00:01.718961   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718961   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:01.718962   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718962 
00:00:01.718963 [/Devices/pci/] (level 2)
00:00:01.718963 
00:00:01.718963 [/Devices/pci/0/] (level 3)
00:00:01.718964   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718964 
00:00:01.718964 [/Devices/pci/0/Config/] (level 4)
00:00:01.718965   IOAPIC <integer> = 0x0000000000000001 (1)
00:00:01.718965 
00:00:01.718965 [/Devices/pcibridge/] (level 2)
00:00:01.718966 
00:00:01.718966 [/Devices/pckbd/] (level 2)
00:00:01.718967 
00:00:01.718967 [/Devices/pckbd/0/] (level 3)
00:00:01.718967   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718968 
00:00:01.718968 [/Devices/pckbd/0/Config/] (level 4)
00:00:01.718968 
00:00:01.718969 [/Devices/pckbd/0/LUN#0/] (level 4)
00:00:01.718969   Driver <string>  = ""KeyboardQueue"" (cb=14)
00:00:01.718970 
00:00:01.718970 [/Devices/pckbd/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.718971   Driver <string>  = ""MainKeyboard"" (cb=13)
00:00:01.718971 
00:00:01.718971 [/Devices/pckbd/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.718972   Object <integer> = 0x0000000003b869e0 (62 417 376)
00:00:01.718973 
00:00:01.718973 [/Devices/pckbd/0/LUN#0/Config/] (level 5)
00:00:01.718974   QueueSize <integer> = 0x0000000000000040 (64)
00:00:01.718974 
00:00:01.718975 [/Devices/pckbd/0/LUN#1/] (level 4)
00:00:01.718975   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:01.718976 
00:00:01.718976 [/Devices/pckbd/0/LUN#1/AttachedDriver/] (level 5)
00:00:01.718977   Driver <string>  = ""MainMouse"" (cb=10)
00:00:01.718977 
00:00:01.718977 [/Devices/pckbd/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:01.718978   Object <integer> = 0x0000000003c5bed0 (63 291 088)
00:00:01.718978 
00:00:01.718979 [/Devices/pckbd/0/LUN#1/Config/] (level 5)
00:00:01.718979   QueueSize <integer> = 0x0000000000000080 (128)
00:00:01.718980 
00:00:01.718980 [/Devices/pcnet/] (level 2)
00:00:01.718981 
00:00:01.718981 [/Devices/serial/] (level 2)
00:00:01.718981 
00:00:01.718981 [/Devices/usb-ohci/] (level 2)
00:00:01.718982 
00:00:01.718982 [/Devices/usb-ohci/0/] (level 3)
00:00:01.718983   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718983   PCIDeviceNo   <integer> = 0x0000000000000006 (6)
00:00:01.718984   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718984   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718985 
00:00:01.718985 [/Devices/usb-ohci/0/Config/] (level 4)
00:00:01.718985 
00:00:01.718985 [/Devices/usb-ohci/0/LUN#0/] (level 4)
00:00:01.718986   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:01.718986 
00:00:01.718987 [/Devices/usb-ohci/0/LUN#0/Config/] (level 5)
00:00:01.718987 
00:00:01.718987 [/Devices/usb-ohci/0/LUN#999/] (level 4)
00:00:01.718988   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718988 
00:00:01.718989 [/Devices/usb-ohci/0/LUN#999/Config/] (level 5)
00:00:01.718989   First   <integer> = 0x0000000000000000 (0)
00:00:01.718990   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718990   papLeds <integer> = 0x0000000003bf5258 (62 870 104)
00:00:01.718991 
00:00:01.718991 [/Devices/vga/] (level 2)
00:00:01.718991 
00:00:01.718992 [/Devices/vga/0/] (level 3)
00:00:01.718992   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718993   PCIDeviceNo   <integer> = 0x0000000000000002 (2)
00:00:01.718993   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718993   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718994 
00:00:01.718994 [/Devices/vga/0/Config/] (level 4)
00:00:01.718995   3DEnabled        <integer> = 0x0000000000000001 (1)
00:00:01.718995   CustomVideoModes <integer> = 0x0000000000000000 (0)
00:00:01.718996   FadeIn           <integer> = 0x0000000000000001 (1)
00:00:01.718996   FadeOut          <integer> = 0x0000000000000001 (1)
00:00:01.718997   HeightReduction  <integer> = 0x0000000000000000 (0)
00:00:01.718997   LogoFile         <string>  = """" (cb=1)
00:00:01.718998   LogoTime         <integer> = 0x0000000000000000 (0)
00:00:01.718998   MonitorCount     <integer> = 0x0000000000000001 (1)
00:00:01.718998   ShowBootMenu     <integer> = 0x0000000000000002 (2)
00:00:01.718999   VMSVGA3dEnabled  <integer> = 0x0000000000000001 (1)
00:00:01.718999   VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:01.719000   VRamSize         <integer> = 0x0000000010000000 (268 435 456, 256 MB)
00:00:01.719001 
00:00:01.719001 [/Devices/vga/0/LUN#0/] (level 4)
00:00:01.719002   Driver <string>  = ""MainDisplay"" (cb=12)
00:00:01.719002 
00:00:01.719002 [/Devices/vga/0/LUN#0/Config/] (level 5)
00:00:01.719003   Object <integer> = 0x0000000003c397b0 (63 150 000)
00:00:01.719003 
00:00:01.719004 [/Devices/vga/0/LUN#999/] (level 4)
00:00:01.719004   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.719005 
00:00:01.719005 [/Devices/vga/0/LUN#999/Config/] (level 5)
00:00:01.719006   First   <integer> = 0x0000000000000000 (0)
00:00:01.719006   Last    <integer> = 0x0000000000000000 (0)
00:00:01.719006   papLeds <integer> = 0x0000000003bf5268 (62 870 120)
00:00:01.719007 
00:00:01.719007 [/Devices/virtio-net/] (level 2)
00:00:01.719008 
00:00:01.719008 [/EM/] (level 1)
00:00:01.719008   TripleFaultReset <integer> = 0x0000000000000000 (0)
00:00:01.719009 
00:00:01.719009 [/GIM/] (level 1)
00:00:01.719009   Provider <string>  = ""HyperV"" (cb=7)
00:00:01.719010 
00:00:01.719010 [/HM/] (level 1)
00:00:01.719011   64bitEnabled       <integer> = 0x0000000000000001 (1)
00:00:01.719011   EnableLargePages   <integer> = 0x0000000000000001 (1)
00:00:01.719012   EnableNestedPaging <integer> = 0x0000000000000001 (1)
00:00:01.719012   EnableUX           <integer> = 0x0000000000000001 (1)
00:00:01.719013   EnableVPID         <integer> = 0x0000000000000001 (1)
00:00:01.719013   Exclusive          <integer> = 0x0000000000000000 (0)
00:00:01.719013   HMForced           <integer> = 0x0000000000000001 (1)
00:00:01.719014   IBPBOnVMEntry      <integer> = 0x0000000000000000 (0)
00:00:01.719014   IBPBOnVMExit       <integer> = 0x0000000000000000 (0)
00:00:01.719015   L1DFlushOnSched    <integer> = 0x0000000000000001 (1)
00:00:01.719015   L1DFlushOnVMEntry  <integer> = 0x0000000000000000 (0)
00:00:01.719016   MDSClearOnSched    <integer> = 0x0000000000000001 (1)
00:00:01.719016   MDSClearOnVMEntry  <integer> = 0x0000000000000000 (0)
00:00:01.719017   SpecCtrlByHost     <integer> = 0x0000000000000000 (0)
00:00:01.719017   UseNEMInstead      <integer> = 0x0000000000000000 (0)
00:00:01.719017 
00:00:01.719018 [/MM/] (level 1)
00:00:01.719018   CanUseLargerHeap <integer> = 0x0000000000000000 (0)
00:00:01.719018 
00:00:01.719019 [/NEM/] (level 1)
00:00:01.719019   Allow64BitGuests <integer> = 0x0000000000000001 (1)
00:00:01.719019 
00:00:01.719020 [/PDM/] (level 1)
00:00:01.719020 
00:00:01.719020 [/PDM/AsyncCompletion/] (level 2)
00:00:01.719021 
00:00:01.719021 [/PDM/AsyncCompletion/File/] (level 3)
00:00:01.719022 
00:00:01.719022 [/PDM/AsyncCompletion/File/BwGroups/] (level 4)
00:00:01.719022 
00:00:01.719022 [/PDM/BlkCache/] (level 2)
00:00:01.719023   CacheSize <integer> = 0x0000000000500000 (5 242 880, 5 MB)
00:00:01.719024 
00:00:01.719024 [/PDM/Devices/] (level 2)
00:00:01.719024 
00:00:01.719025 [/PDM/Devices/VBoxEhci/] (level 3)
00:00:01.719025   Path         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR3.DLL"" (cb=111)
00:00:01.719026   R0SearchPath <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:01.719027 
00:00:01.719027 [/PDM/Devices/VBoxNvme/] (level 3)
00:00:01.719027   Path         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxNvmeR3.DLL"" (cb=111)
00:00:01.719028   R0SearchPath <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:01.719029 
00:00:01.719029 [/PDM/Drivers/] (level 2)
00:00:01.719029 
00:00:01.719030 [/PDM/Drivers/DrvHostWebcam/] (level 3)
00:00:01.719030   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL"" (cb=115)
00:00:01.719031 
00:00:01.719031 [/PDM/Drivers/VBoxC/] (level 3)
00:00:01.719031   Path <string>  = ""VBoxC"" (cb=6)
00:00:01.719032 
00:00:01.719032 [/PDM/NetworkShaper/] (level 2)
00:00:01.719032 
00:00:01.719033 [/PDM/NetworkShaper/BwGroups/] (level 3)
00:00:01.719033 
00:00:01.719033 [/PDM/USB/] (level 2)
00:00:01.719034 
00:00:01.719034 [/PDM/USB/VBoxUsbCardReader/] (level 3)
00:00:01.719035   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbCardReaderR3.DLL"" (cb=120)
00:00:01.719035 
00:00:01.719035 [/PDM/USB/VBoxUsbWebcam/] (level 3)
00:00:01.719036   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbWebcamR3.DLL"" (cb=116)
00:00:01.719036 
00:00:01.719036 [/TM/] (level 1)
00:00:01.719037   UTCOffset <integer> = 0x0000000000000000 (0)
00:00:01.719037 
00:00:01.719037 [/USB/] (level 1)
00:00:01.719038 
00:00:01.719038 [/USB/HidMouse/] (level 2)
00:00:01.719038 
00:00:01.719039 [/USB/HidMouse/0/] (level 3)
00:00:01.719039 
00:00:01.719039 [/USB/HidMouse/0/Config/] (level 4)
00:00:01.719040   Mode <string>  = ""absolute"" (cb=9)
00:00:01.719040 
00:00:01.719041 [/USB/HidMouse/0/LUN#0/] (level 4)
00:00:01.719041   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:01.719042 
00:00:01.719042 [/USB/HidMouse/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.719043   Driver <string>  = ""MainMouse"" (cb=10)
00:00:01.719043 
00:00:01.719043 [/USB/HidMouse/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.719044   Object <integer> = 0x0000000003c5bed0 (63 291 088)
00:00:01.719045 
00:00:01.719045 [/USB/HidMouse/0/LUN#0/Config/] (level 5)
00:00:01.719046   QueueSize <integer> = 0x0000000000000080 (128)
00:00:01.719046 
00:00:01.719046 [/USB/USBProxy/] (level 2)
00:00:01.719047 
00:00:01.719047 [/USB/USBProxy/GlobalConfig/] (level 3)
00:00:01.719048 
00:00:01.719048 ********************* End of CFGM dump **********************
00:00:01.719154 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:01.719199 MM: cbHyperHeap=0x240000 (2359296)
00:00:01.720617 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:01.721430 CPUM: Matched host CPU INTEL 0x6/0x9e/0xd Intel_Core7_WhiskeyLake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:01.721460 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:01.721467 CPUM: Microcode revision 0x000000B4
00:00:01.721473 CPUM: Changing leaf 13[0]: EBX=0x340 -> 0x340, ECX=0x440 -> 0x340
00:00:01.721480 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD
00:00:01.721483 CPUM: MSR/CPUID reconciliation insert: 0x0000010a IA32_ARCH_CAPABILITIES
00:00:01.721487 CPUM: MSR fudge: 0x00000122 IA32_TSX_CTRL
00:00:01.721498 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:01.721588 PGM: Host paging mode: AMD64+PGE+NX
00:00:01.721592 PGM: PGMPool: cMaxPages=2304 (u64MaxPages=2084)
00:00:01.721594 PGM: pgmR3PoolInit: cMaxPages=0x900 cMaxUsers=0x1200 cMaxPhysExts=0x1200 fCacheEnable=true 
00:00:01.726617 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=100 u32UpdateIntervalNS=10000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x11 cCpus=6
00:00:01.726632 TM: GIP - u64CpuHz=2 904 021 402 (0xad17d99a)  SUPGetCpuHzFromGip => 2 904 021 402
00:00:01.726635 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2905911935(*) cErrors=0
00:00:01.726684 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x2 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2904184923(*) cErrors=0
00:00:01.726687 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2904021402(*) cErrors=0
00:00:01.726689 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x6 iGipCpu=0x5 i64TSCDelta=0 enmState=3 u64CpuHz=2904065034(*) cErrors=0
00:00:01.726691 TM: GIP - CPU: iCpuSet=0x4 idCpu=0x4 idApic=0x8 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2904574105(*) cErrors=0
00:00:01.726692 TM: GIP - CPU: iCpuSet=0x5 idCpu=0x5 idApic=0xa iGipCpu=0x4 i64TSCDelta=0 enmState=3 u64CpuHz=2904101058(*) cErrors=0
00:00:01.726723 TM: cTSCTicksPerSecond=2 904 021 402 (0xad17d99a) enmTSCMode=1 (VirtTscEmulated)
00:00:01.726724 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:01.727183 EMR3Init: fIemExecutesAll=false fGuruOnTripleFault=true 
00:00:01.727347 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_WhiskeyLake
00:00:01.727410 GIM: Using provider 'HyperV' (Implementation version: 0)
00:00:01.727415 GIM: HyperV: Reporting vendor as 'VBoxVBoxVBox'
00:00:01.727418 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:01.727522 AIOMgr: Default manager type is 'Async'
00:00:01.727525 AIOMgr: Default file backend is 'NonBuffered'
00:00:01.727685 BlkCache: Cache successfully initialized. Cache size is 5242880 bytes
00:00:01.727688 BlkCache: Cache commit interval is 10000 ms
00:00:01.727690 BlkCache: Cache commit threshold is 2621440 bytes
00:00:01.961806 PcBios: [SMP] BIOS with 2 CPUs
00:00:01.961820 PcBios: Using the 386+ BIOS image.
00:00:01.961866 PcBios: MPS table at 000e1300
00:00:01.962692 PcBios: Using LAN ROM 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom' with a size of 0xc000 bytes
00:00:01.962730 PcBios: fCheckShutdownStatusForSoftReset=true   fClearShutdownStatusOnHardReset=true 
00:00:01.970013 SUP: Loaded VBoxDDR0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:01.970018 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xXXXXXXXXXXXXXXXX
00:00:01.970163 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:01.970312 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:01.970344 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:01.977390 Shared Folders service loaded
00:00:01.982206 Guest Control service loaded
00:00:02.018512 VGA: Using the 386+ BIOS image.
00:00:02.019790 VD: VDInit finished with VINF_SUCCESS
00:00:02.028356 DrvVD: Flushes will be ignored
00:00:02.028360 DrvVD: Async flushes will be passed to the disk
00:00:02.045804 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Asteroid-7.vdi' (flags 000c0781) created successfully
00:00:02.066049 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{281e38e5-ff1b-4d6c-9523-3794348b861e}.vdi' (flags 000c0781) created successfully
00:00:02.083186 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{bbae5348-a1c8-4eb7-801e-5a75b173af2f}.vdi' (flags 000c0781) created successfully
00:00:02.087823 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{e14a6301-e7ab-4f38-919a-474ba2d2224f}.vdi' (flags 000c0781) created successfully
00:00:02.090770 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{bd5df2b9-1b74-4058-b5dc-de9c354c23c5}.vdi' (flags 000c0781) created successfully
00:00:02.096234 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{702c5788-4b07-4854-afaa-11069398a139}.vdi' (flags 000c0781) created successfully
00:00:02.099833 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{00d317fd-75eb-4e52-bc4c-cd16a0cd44c6}.vdi' (flags 000c0781) created successfully
00:00:02.104616 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{d06b5feb-30d7-4c80-86f1-089b0159c660}.vdi' (flags 000c0781) created successfully
00:00:02.167689 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{5e7c1acb-8345-4fd8-8230-07cc65b4a7c1}.vdi' (flags 000c0781) created successfully
00:00:02.174179 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{3476a280-0799-4492-b80a-3f49e19328d1}.vdi' (flags 000c0781) created successfully
00:00:02.178266 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{7d214b65-fb63-4e15-8517-9a4917deb9f7}.vdi' (flags 000c0781) created successfully
00:00:02.183277 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{13d95ad9-6645-4a1a-a124-92c2acdf50aa}.vdi' (flags 000c0781) created successfully
00:00:02.189513 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi' (flags 000c0723) created successfully
00:00:02.191429 VD: Opening the disk took 161860523 ns
00:00:02.191492 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 211812352
00:00:02.191693 DrvVD: Flushes will be ignored
00:00:02.191698 DrvVD: Async flushes will be passed to the disk
00:00:02.193048 AIOMgr: Endpoint for file 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (flags 000c0781) created successfully
00:00:02.193059 VD: Opening the disk took 104171 ns
00:00:02.193101 AHCI: LUN#1: CD/DVD
00:00:02.193244 AHCI#0: Reset the HBA
00:00:02.193248 VD#0: Cancelling all active requests
00:00:02.193287 E1000#0: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled RC=disabled
00:00:02.199074 NAT: Guest address guess set to 10.0.2.15 by initialization
00:00:02.207129 NAT: DNS#0: 119.29.29.29
00:00:02.207136 NAT: DNS#1: 223.6.6.6
00:00:02.207683 HDA: Asynchronous I/O enabled
00:00:02.207702 Audio: Initializing DirectSound audio driver
00:00:02.276547 DSound: Capture device currently is unavailable
00:00:02.276554 DSound: Error enumeration capture device '主声音捕获驱动程序', rc=VERR_GENERAL_FAILURE
00:00:02.290582 DSound: Capture device currently is unavailable
00:00:02.290589 DSound: Error enumeration capture device '主声音捕获驱动程序', rc=VERR_GENERAL_FAILURE
00:00:02.290594 Audio: Found 3 devices for driver 'DSoundAudio'
00:00:02.290597 Audio: Device '主声音驱动程序':
00:00:02.290599 Audio: 	Usage           = Output
00:00:02.290600 Audio: 	Flags           = DEFAULT
00:00:02.290602 Audio: 	Input channels  = 0
00:00:02.290603 Audio: 	Output channels = 2
00:00:02.290604 Audio: Device '扬声器 (Realtek High Definition Audio)':
00:00:02.290605 Audio: 	Usage           = Output
00:00:02.290606 Audio: 	Flags           = NONE
00:00:02.290608 Audio: 	Input channels  = 0
00:00:02.290609 Audio: 	Output channels = 2
00:00:02.290610 Audio: Device 'EB243Y A (NVIDIA High Definition Audio)':
00:00:02.290612 Audio: 	Usage           = Output
00:00:02.290613 Audio: 	Flags           = NONE
00:00:02.290614 Audio: 	Input channels  = 0
00:00:02.290615 Audio: 	Output channels = 2
00:00:02.290659 HDA: Codec reset
00:00:02.290665 HDA: Reset
00:00:02.290863 GIMDev: Registered Hyper-V hypercall page
00:00:02.290870 GIMDev: Registered Hyper-V TSC page
00:00:02.291047 VUSB: Attached 'HidMouse' to port 1 on RootHub#0 (FullSpeed)
00:00:02.291065 PGM: The CPU physical address width is 39 bits
00:00:02.291068 PGM: PGMR3InitFinalize: 4 MB PSE mask 0000007fffffffff -> VINF_SUCCESS
00:00:02.291190 TM: TMR3InitFinalize: fTSCModeSwitchAllowed=true 
00:00:02.291294 VMM: Thread-context hooks unavailable
00:00:02.291297 VMM: Warning! RTThreadPreemptIsPending() cannot be trusted!  Need to update kernel info?
00:00:02.291298 VMM: Kernel preemption is possible
00:00:02.291978 HM: fWorldSwitcher=0x0 (fIbpbOnVmExit=false fIbpbOnVmEntry=false fL1dFlushOnVmEntry=false); fL1dFlushOnSched=false fMdsClearOnVmEntry=false
00:00:02.291982 HM: Using VT-x implementation 3.0
00:00:02.291984 HM: Max resume loops                  = 1024
00:00:02.291984 HM: Host CR4                          = 0x506f8
00:00:02.291985 HM: Host EFER                         = 0xd01
00:00:02.291986 HM: MSR_IA32_SMM_MONITOR_CTL          = 0x0
00:00:02.291986 HM: MSR_IA32_FEATURE_CONTROL          = 0x5
00:00:02.291986 HM:   LOCK
00:00:02.291987 HM:   VMXON
00:00:02.291988 HM: MSR_IA32_VMX_BASIC                = 0xda040000000004
00:00:02.291988 HM:   VMCS id                           = 0x4
00:00:02.291989 HM:   VMCS size                         = 1024 bytes
00:00:02.291989 HM:   VMCS physical address limit       = None
00:00:02.291990 HM:   VMCS memory type                  = Write Back (WB)
00:00:02.291990 HM:   Dual-monitor treatment support    = true 
00:00:02.291991 HM:   OUTS & INS instruction-info       = true 
00:00:02.291991 HM:   Supports true-capability MSRs     = true 
00:00:02.291991 HM:   VM-entry Xcpt error-code optional = false
00:00:02.291992 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x7f00000016
00:00:02.291992 HM:   EXT_INT_EXIT
00:00:02.291992 HM:   NMI_EXIT
00:00:02.291993 HM:   VIRTUAL_NMI
00:00:02.291993 HM:   PREEMPT_TIMER
00:00:02.291993 HM:   POSTED_INT (must be cleared)
00:00:02.291994 HM: MSR_IA32_VMX_PROCBASED_CTLS       = 0xfff9fffe0401e172
00:00:02.291995 HM:   INT_WINDOW_EXIT
00:00:02.291995 HM:   USE_TSC_OFFSETTING
00:00:02.291995 HM:   HLT_EXIT
00:00:02.291996 HM:   INVLPG_EXIT
00:00:02.291996 HM:   MWAIT_EXIT
00:00:02.291996 HM:   RDPMC_EXIT
00:00:02.291997 HM:   RDTSC_EXIT
00:00:02.291997 HM:   CR3_LOAD_EXIT (must be set)
00:00:02.291997 HM:   CR3_STORE_EXIT (must be set)
00:00:02.291997 HM:   CR8_LOAD_EXIT
00:00:02.291998 HM:   CR8_STORE_EXIT
00:00:02.291998 HM:   USE_TPR_SHADOW
00:00:02.291998 HM:   NMI_WINDOW_EXIT
00:00:02.291998 HM:   MOV_DR_EXIT
00:00:02.291999 HM:   UNCOND_IO_EXIT
00:00:02.291999 HM:   USE_IO_BITMAPS
00:00:02.291999 HM:   MONITOR_TRAP_FLAG
00:00:02.291999 HM:   USE_MSR_BITMAPS
00:00:02.292000 HM:   MONITOR_EXIT
00:00:02.292000 HM:   PAUSE_EXIT
00:00:02.292000 HM:   USE_SECONDARY_CTLS
00:00:02.292000 HM: MSR_IA32_VMX_PROCBASED_CTLS2      = 0x5ffcff00000000
00:00:02.292001 HM:   VIRT_APIC_ACCESS
00:00:02.292001 HM:   EPT
00:00:02.292002 HM:   DESC_TABLE_EXIT
00:00:02.292002 HM:   RDTSCP
00:00:02.292002 HM:   VIRT_X2APIC_MODE
00:00:02.292002 HM:   VPID
00:00:02.292003 HM:   WBINVD_EXIT
00:00:02.292003 HM:   UNRESTRICTED_GUEST
00:00:02.292003 HM:   APIC_REG_VIRT (must be cleared)
00:00:02.292004 HM:   VIRT_INT_DELIVERY (must be cleared)
00:00:02.292005 HM:   PAUSE_LOOP_EXIT
00:00:02.292005 HM:   RDRAND_EXIT
00:00:02.292005 HM:   INVPCID
00:00:02.292005 HM:   VMFUNC
00:00:02.292006 HM:   VMCS_SHADOWING
00:00:02.292006 HM:   ENCLS_EXIT
00:00:02.292006 HM:   RDSEED_EXIT
00:00:02.292006 HM:   PML
00:00:02.292007 HM:   EPT_VE
00:00:02.292007 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292007 HM:   XSAVES_XRSTORS
00:00:02.292008 HM:   MODE_BASED_EPT_PERM
00:00:02.292008 HM:   SPPTP_EPT (must be cleared)
00:00:02.292008 HM:   PT_EPT (must be cleared)
00:00:02.292008 HM:   TSC_SCALING (must be cleared)
00:00:02.292009 HM:   USER_WAIT_PAUSE (must be cleared)
00:00:02.292009 HM:   ENCLV_EXIT (must be cleared)
00:00:02.292009 HM: MSR_IA32_VMX_ENTRY_CTLS           = 0x3ffff000011ff
00:00:02.292010 HM:   LOAD_DEBUG (must be set)
00:00:02.292010 HM:   IA32E_MODE_GUEST
00:00:02.292010 HM:   ENTRY_TO_SMM
00:00:02.292010 HM:   DEACTIVATE_DUAL_MON
00:00:02.292011 HM:   LOAD_PERF_MSR
00:00:02.292011 HM:   LOAD_PAT_MSR
00:00:02.292011 HM:   LOAD_EFER_MSR
00:00:02.292011 HM:   LOAD_BNDCFGS_MSR
00:00:02.292011 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292012 HM:   LOAD_RTIT_CTL_MSR (must be cleared)
00:00:02.292012 HM: MSR_IA32_VMX_EXIT_CTLS            = 0x1ffffff00036dff
00:00:02.292013 HM:   SAVE_DEBUG (must be set)
00:00:02.292013 HM:   HOST_ADDR_SPACE_SIZE
00:00:02.292013 HM:   LOAD_PERF_MSR
00:00:02.292013 HM:   ACK_EXT_INT
00:00:02.292014 HM:   SAVE_PAT_MSR
00:00:02.292014 HM:   LOAD_PAT_MSR
00:00:02.292014 HM:   SAVE_EFER_MSR
00:00:02.292014 HM:   LOAD_EFER_MSR
00:00:02.292015 HM:   SAVE_PREEMPT_TIMER
00:00:02.292015 HM:   CLEAR_BNDCFGS_MSR
00:00:02.292015 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292015 HM:   CLEAR_RTIT_CTL_MSR (must be cleared)
00:00:02.292016 HM: MSR_IA32_VMX_TRUE_PINBASED_CTLS   = 0x7f00000016
00:00:02.292016 HM: MSR_IA32_VMX_TRUE_PROCBASED_CTLS  = 0xfff9fffe04006172
00:00:02.292017 HM: MSR_IA32_VMX_TRUE_ENTRY_CTLS      = 0x3ffff000011fb
00:00:02.292018 HM: MSR_IA32_VMX_TRUE_EXIT_CTLS       = 0x1ffffff00036dfb
00:00:02.292019 HM: MSR_IA32_VMX_MISC                 = 0x7004c1e7
00:00:02.292020 HM:   PREEMPT_TIMER_TSC                 = 0x7
00:00:02.292020 HM:   EXIT_SAVE_EFER_LMA                = true 
00:00:02.292020 HM:   ACTIVITY_STATES                   = 0x7 ( HLT SHUTDOWN SIPI_WAIT )
00:00:02.292021 HM:   INTEL_PT                          = true 
00:00:02.292021 HM:   SMM_READ_SMBASE_MSR               = true 
00:00:02.292021 HM:   CR3_TARGET                        = 0x4
00:00:02.292022 HM:   MAX_MSR                           = 0x0 ( 512 )
00:00:02.292022 HM:   VMXOFF_BLOCK_SMI                  = true 
00:00:02.292023 HM:   VMWRITE_ALL                       = true 
00:00:02.292023 HM:   ENTRY_INJECT_SOFT_INT             = 0x1
00:00:02.292023 HM:   MSEG_ID                           = 0x0
00:00:02.292023 HM: MSR_IA32_VMX_VMCS_ENUM            = 0x2e
00:00:02.292024 HM:   HIGHEST_IDX                       = 0x17
00:00:02.292024 HM: MSR_IA32_VMX_EPT_VPID_CAP         = 0xf0106734141
00:00:02.292025 HM:   RWX_X_ONLY
00:00:02.292025 HM:   PAGE_WALK_LENGTH_4
00:00:02.292025 HM:   EMT_UC
00:00:02.292025 HM:   EMT_WB
00:00:02.292026 HM:   PDE_2M
00:00:02.292026 HM:   PDPTE_1G
00:00:02.292026 HM:   INVEPT
00:00:02.292026 HM:   EPT_ACCESS_DIRTY
00:00:02.292026 HM:   ADVEXITINFO_EPT
00:00:02.292027 HM:   INVEPT_SINGLE_CONTEXT
00:00:02.292027 HM:   INVEPT_ALL_CONTEXTS
00:00:02.292027 HM:   INVVPID
00:00:02.292027 HM:   INVVPID_INDIV_ADDR
00:00:02.292028 HM:   INVVPID_SINGLE_CONTEXT
00:00:02.292028 HM:   INVVPID_ALL_CONTEXTS
00:00:02.292028 HM:   INVVPID_SINGLE_CONTEXT_RETAIN_GLOBALS
00:00:02.292028 HM: MSR_IA32_VMX_VMFUNC               = 0x1
00:00:02.292029 HM:   EPTP_SWITCHING
00:00:02.292029 HM: MSR_IA32_VMX_CR0_FIXED0           = 0x80000021
00:00:02.292029 HM: MSR_IA32_VMX_CR0_FIXED1           = 0xffffffff
00:00:02.292030 HM: MSR_IA32_VMX_CR4_FIXED0           = 0x2000
00:00:02.292030 HM: MSR_IA32_VMX_CR4_FIXED1           = 0x3727ff
00:00:02.292031 HM: APIC-access page physaddr         = 0x0000000026f73000
00:00:02.292031 HM: VCPU  0: MSR bitmap physaddr      = 0x00000004682e6000
00:00:02.292032 HM: VCPU  0: VMCS physaddr            = 0x00000004682e3000
00:00:02.292033 HM: VCPU  1: MSR bitmap physaddr      = 0x00000004682ea000
00:00:02.292033 HM: VCPU  1: VMCS physaddr            = 0x00000004682e7000
00:00:02.292034 HM: Guest support: 32-bit and 64-bit
00:00:02.292038 HM: Supports VMCS EFER fields         = true 
00:00:02.292038 HM: Enabled VMX
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:02.292044 HM: Enabled nested paging
00:00:02.292044 HM:   EPT flush type                  = Single context
00:00:02.292044 HM: Enabled unrestricted guest execution
00:00:02.292045 HM: Enabled large page support
00:00:02.292045 HM: Enabled VPID
00:00:02.292045 HM:   VPID flush type                 = Single context
00:00:02.292045 HM: Enabled VMX-preemption timer (cPreemptTimerShift=7)
00:00:02.292046 HM: VT-x/AMD-V init method: Local
00:00:02.292046 EM: Exit history optimizations: enabled=true  enabled-r0=true  enabled-r0-no-preemption=false
00:00:02.292088 PcBios: SATA LUN#0 LCHS=1024/255/63
00:00:02.292096 APIC: fPostedIntrsEnabled=false fVirtApicRegsEnabled=false fSupportsTscDeadline=false
00:00:02.292099 TMR3UtcNow: nsNow=1 593 133 028 754 100 100 nsPrev=0 -> cNsDelta=1 593 133 028 754 100 100 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 593 133 028 754 100 100)
00:00:02.292105 VMM: fUsePeriodicPreemptionTimers=false
00:00:02.292112 APIC: Enabling Hyper-V x2APIC compatibility mode
00:00:02.292177 CPUM: Logical host processors: 6 present, 6 max, 6 online, online mask: 000000000000003f
00:00:02.292178 CPUM: Physical host cores: 6
00:00:02.292178 ************************* CPUID dump ************************
00:00:02.292182          Raw Standard CPUID Leaves
00:00:02.292182      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:02.292183 Gst: 00000000/0000  00000016 756e6547 6c65746e 49656e69
00:00:02.292185 Hst:                00000016 756e6547 6c65746e 49656e69
00:00:02.292185 Gst: 00000001/0000  000906ed 00020800 d6da2203 178bfbff
00:00:02.292186 Hst:                000906ed 04100800 7ffafbbf bfebfbff
00:00:02.292187 Gst: 00000002/0000  76036301 00f0b6ff 00000000 00c30000
00:00:02.292188 Hst:                76036301 00f0b6ff 00000000 00c30000
00:00:02.292188 Gst: 00000003/0000  00000000 00000000 00000000 00000000
00:00:02.292189 Hst:                00000000 00000000 00000000 00000000
00:00:02.292189 Gst: 00000004/0000  04000121 01c0003f 0000003f 00000000
00:00:02.292190 Hst:                1c004121 01c0003f 0000003f 00000000
00:00:02.292191 Gst: 00000004/0001  04000122 01c0003f 0000003f 00000000
00:00:02.292191 Hst:                1c004122 01c0003f 0000003f 00000000
00:00:02.292192 Gst: 00000004/0002  04000143 00c0003f 000003ff 00000000
00:00:02.292193 Hst:                1c004143 00c0003f 000003ff 00000000
00:00:02.292193 Gst: 00000004/0003  04000163 02c0003f 00002fff 00000006
00:00:02.292194 Hst:                1c03c163 02c0003f 00002fff 00000006
00:00:02.292195 Gst: 00000004/0004  04000000 00000000 00000000 00000000
00:00:02.292195 Hst:                00000000 00000000 00000000 00000000
00:00:02.292196 Gst: 00000005/0000  00000000 00000000 00000000 00000000
00:00:02.292196 Hst:                00000040 00000040 00000003 11142120
00:00:02.292197 Gst: 00000006/0000  00000000 00000000 00000000 00000000
00:00:02.292198 Hst:                000027f7 00000002 00000009 00000000
00:00:02.292198 Gst: 00000007/0000  00000000 00842421 00000000 30000400
00:00:02.292199 Hst:                00000000 029c67af 40000000 bc000400
00:00:02.292199 Gst: 00000007/0001  00000000 00000000 00000000 00000000
00:00:02.292200 Hst:                00000000 00000000 00000000 00000000
00:00:02.292200 Gst: 00000008/0000  00000000 00000000 00000000 00000000
00:00:02.292201 Hst:                00000000 00000000 00000000 00000000
00:00:02.292201 Gst: 00000009/0000  00000000 00000000 00000000 00000000
00:00:02.292202 Hst:                00000000 00000000 00000000 00000000
00:00:02.292202 Gst: 0000000a/0000  00000000 00000000 00000000 00000000
00:00:02.292203 Hst:                07300804 00000000 00000000 00000603
00:00:02.292203 Gst: 0000000b/0000  00000000 00000001 00000100 00000000
00:00:02.292204 Hst:                00000001 00000001 00000100 00000004
00:00:02.292204 Gst: 0000000b/0001  00000001 00000002 00000201 00000000
00:00:02.292205 Hst:                00000004 00000006 00000201 00000004
00:00:02.292205 Gst: 0000000b/0002  00000000 00000000 00000002 00000000
00:00:02.292205 Hst:                00000000 00000000 00000002 00000004
00:00:02.292206 Gst: 0000000c/0000  00000000 00000000 00000000 00000000
00:00:02.292206 Hst:                00000000 00000000 00000000 00000000
00:00:02.292207 Gst: 0000000d/0000  00000007 00000340 00000340 00000000
00:00:02.292207 Hst:                0000001f 00000340 00000440 00000000
00:00:02.292208 Gst: 0000000d/0001  00000000 00000340 00000000 00000000
00:00:02.292208 Hst:                0000000f 00000340 00000100 00000000
00:00:02.292209 Gst: 0000000d/0002  00000100 00000240 00000000 00000000
00:00:02.292209 Hst:                00000100 00000240 00000000 00000000
00:00:02.292210 Gst: 0000000d/0003  00000000 00000000 00000000 00000000
00:00:02.292210 Hst:                00000040 000003c0 00000000 00000000
00:00:02.292211 Gst: 0000000d/0004  00000000 00000000 00000000 00000000
00:00:02.292211 Hst:                00000040 00000400 00000000 00000000
00:00:02.292212 Gst: 0000000d/0005  00000000 00000000 00000000 00000000
00:00:02.292212 Hst:                00000000 00000000 00000000 00000000
00:00:02.292212 Gst: 0000000d/0006  00000000 00000000 00000000 00000000
00:00:02.292213 Hst:                00000000 00000000 00000000 00000000
00:00:02.292213 Gst: 0000000d/0007  00000000 00000000 00000000 00000000
00:00:02.292214 Hst:                00000000 00000000 00000000 00000000
00:00:02.292214 Gst: 0000000d/0008  00000000 00000000 00000000 00000000
00:00:02.292215 Hst:                00000080 00000000 00000001 00000000
00:00:02.292215 Gst: 0000000d/0009  00000000 00000000 00000000 00000000
00:00:02.292216 Hst:                00000000 00000000 00000000 00000000
00:00:02.292230 Gst: 0000000e/0000  00000000 00000000 00000000 00000000
00:00:02.292231 Hst:                00000000 00000000 00000000 00000000
00:00:02.292231 Gst: 0000000f/0000  00000000 00000000 00000000 00000000
00:00:02.292232 Hst:                00000000 00000000 00000000 00000000
00:00:02.292232 Gst: 00000010/0000  00000000 00000000 00000000 00000000
00:00:02.292233 Hst:                00000000 00000000 00000000 00000000
00:00:02.292233 Gst: 00000011/0000  00000000 00000000 00000000 00000000
00:00:02.292234 Hst:                00000000 00000000 00000000 00000000
00:00:02.292234 Gst: 00000012/0000  00000000 00000000 00000000 00000000
00:00:02.292234 Hst:                00000000 00000000 00000000 00000000
00:00:02.292235 Gst: 00000013/0000  00000000 00000000 00000000 00000000
00:00:02.292235 Hst:                00000000 00000000 00000000 00000000
00:00:02.292236 Gst: 00000014/0000  00000000 00000000 00000000 00000000
00:00:02.292236 Hst:                00000001 0000000f 00000007 00000000
00:00:02.292237 Hst: 00000015/0000  00000002 000000f2 00000000 00000000
00:00:02.292237 Hst: 00000016/0000  00000b54 00001004 00000064 00000000
00:00:02.292238                                Name: GenuineIntel
00:00:02.292239                            Supports: 0x00000000-0x00000016
00:00:02.292241                              Family:  6 	Extended: 0 	Effective: 6
00:00:02.292241                               Model: 14 	Extended: 9 	Effective: 158
00:00:02.292242                            Stepping: 13
00:00:02.292243                                Type: 0 (primary)
00:00:02.292243                             APIC ID: 0x00
00:00:02.292244                        Logical CPUs: 2
00:00:02.292244                        CLFLUSH Size: 8
00:00:02.292245                            Brand ID: 0x00
00:00:02.292245 Features
00:00:02.292246   Mnemonic - Description                                  = guest (host)
00:00:02.292247   FPU - x87 FPU on Chip                                   = 1 (1)
00:00:02.292248   VME - Virtual 8086 Mode Enhancements                    = 1 (1)
00:00:02.292248   DE - Debugging extensions                               = 1 (1)
00:00:02.292249   PSE - Page Size Extension                               = 1 (1)
00:00:02.292250   TSC - Time Stamp Counter                                = 1 (1)
00:00:02.292250   MSR - Model Specific Registers                          = 1 (1)
00:00:02.292251   PAE - Physical Address Extension                        = 1 (1)
00:00:02.292252   MCE - Machine Check Exception                           = 1 (1)
00:00:02.292252   CX8 - CMPXCHG8B instruction                             = 1 (1)
00:00:02.292253   APIC - APIC On-Chip                                     = 1 (1)
00:00:02.292253   SEP - SYSENTER and SYSEXIT Present                      = 1 (1)
00:00:02.292254   MTRR - Memory Type Range Registers                      = 1 (1)
00:00:02.292255   PGE - PTE Global Bit                                    = 1 (1)
00:00:02.292255   MCA - Machine Check Architecture                        = 1 (1)
00:00:02.292256   CMOV - Conditional Move instructions                    = 1 (1)
00:00:02.292256   PAT - Page Attribute Table                              = 1 (1)
00:00:02.292257   PSE-36 - 36-bit Page Size Extension                     = 1 (1)
00:00:02.292258   PSN - Processor Serial Number                           = 0 (0)
00:00:02.292258   CLFSH - CLFLUSH instruction                             = 1 (1)
00:00:02.292259   DS - Debug Store                                        = 0 (1)
00:00:02.292259   ACPI - Thermal Mon. & Soft. Clock Ctrl.                 = 0 (1)
00:00:02.292260   MMX - Intel MMX Technology                              = 1 (1)
00:00:02.292261   FXSR - FXSAVE and FXRSTOR instructions                  = 1 (1)
00:00:02.292261   SSE - SSE support                                       = 1 (1)
00:00:02.292262   SSE2 - SSE2 support                                     = 1 (1)
00:00:02.292262   SS - Self Snoop                                         = 0 (1)
00:00:02.292263   HTT - Hyper-Threading Technology                        = 1 (1)
00:00:02.292264   TM - Therm. Monitor                                     = 0 (1)
00:00:02.292264   PBE - Pending Break Enabled                             = 0 (1)
00:00:02.292265   SSE3 - SSE3 support                                     = 1 (1)
00:00:02.292265   PCLMUL - PCLMULQDQ support (for AES-GCM)                = 1 (1)
00:00:02.292266   DTES64 - DS Area 64-bit Layout                          = 0 (1)
00:00:02.292267   MONITOR - MONITOR/MWAIT instructions                    = 0 (1)
00:00:02.292267   CPL-DS - CPL Qualified Debug Store                      = 0 (1)
00:00:02.292268   VMX - Virtual Machine Extensions                        = 0 (1)
00:00:02.292268   SMX - Safer Mode Extensions                             = 0 (0)
00:00:02.292269   EST - Enhanced SpeedStep Technology                     = 0 (1)
00:00:02.292269   TM2 - Terminal Monitor 2                                = 0 (1)
00:00:02.292270   SSSE3 - Supplemental Streaming SIMD Extensions 3        = 1 (1)
00:00:02.292271   CNTX-ID - L1 Context ID                                 = 0 (0)
00:00:02.292271   SDBG - Silicon Debug interface                          = 0 (1)
00:00:02.292272   FMA - Fused Multiply Add extensions                     = 0 (1)
00:00:02.292272   CX16 - CMPXCHG16B instruction                           = 1 (1)
00:00:02.292273   TPRUPDATE - xTPR Update Control                         = 0 (1)
00:00:02.292274   PDCM - Perf/Debug Capability MSR                        = 0 (1)
00:00:02.292274   PCID - Process Context Identifiers                      = 1 (1)
00:00:02.292275   DCA - Direct Cache Access                               = 0 (0)
00:00:02.292275   SSE4_1 - SSE4_1 support                                 = 1 (1)
00:00:02.292276   SSE4_2 - SSE4_2 support                                 = 1 (1)
00:00:02.292276   X2APIC - x2APIC support                                 = 0 (1)
00:00:02.292277   MOVBE - MOVBE instruction                               = 1 (1)
00:00:02.292278   POPCNT - POPCNT instruction                             = 1 (1)
00:00:02.292278   TSCDEADL - Time Stamp Counter Deadline                  = 0 (1)
00:00:02.292279   AES - AES instructions                                  = 1 (1)
00:00:02.292279   XSAVE - XSAVE instruction                               = 1 (1)
00:00:02.292280   OSXSAVE - OSXSAVE instruction                           = 0 (1)
00:00:02.292281   AVX - AVX support                                       = 1 (1)
00:00:02.292281   F16C - 16-bit floating point conversion instructions    = 0 (1)
00:00:02.292282   RDRAND - RDRAND instruction                             = 1 (1)
00:00:02.292282   HVP - Hypervisor Present (we're a guest)                = 1 (0)
00:00:02.292283 Structured Extended Feature Flags Enumeration (leaf 7):
00:00:02.292283   Mnemonic - Description                                  = guest (host)
00:00:02.292284   FSGSBASE - RDFSBASE/RDGSBASE/WRFSBASE/WRGSBASE instr.   = 1 (1)
00:00:02.292284   TSCADJUST - ",Mercury233
19684,Frequent IO Read overload freezing the OpenSUSE VM,Linux,Linux,VirtualBox 6.1.10,2020-06-26T10:02:40Z,2020-06-26T10:02:40Z,"My OpenSUSE VM frequently freezes and the Read IO is constantly maximum. It seemed to always happen when browser the internet, regardless of which browser used. The VM is used for browsing a few websites, connecting to a vpn and ssh tocompany hosts. The CPU also spikes to high load.

I've installed OpenSUSE 15.1 KDE and 15.2 multiple times and have set it up mostly in the same way. This is the setup:

EFI
LUKS > LVM > btrfs
HOST IO cache ON (also tried off)
SSD drive on for storage container
4GB RAM (2GB in use)
4 vCPU
VMDK storage format
guest additions installed

I installed the same setup, except for EFI that is replaces with BIOS (I think I tried that with VB as well), and this issue never happens. Same resources given to VM.

Unfortunately I don't have the logs anymore.",lmmmm
19665,OpenWRT locks up early in the kernel sequence on 6.1,Windows,Linux,VirtualBox 6.1.10,2020-06-27T15:31:19Z,2020-06-27T15:31:19Z,"Tried in latest(r128535) build same thing. Something to do with # of CPUs - console log from kernel looks different between 2 vCPU and 1, but locks up regardless.
I'll attach the log and vdi, as it's reasonably small. Just in case something is wrong there, the vdi was built via ""convertfromraw"" of sourced from https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/openwrt-19.07.3-x86-64-combined-ext4.img.gz, which is the latest released openwrt distro.

The image boots fine on hyper-V, vmware and physical.
",novitk
19685,Failed to create a snapshot of the virtual machine: Win Server 2019 guest,Linux,Windows,VirtualBox 6.1.10,2020-06-27T16:25:05Z,2020-06-27T16:25:05Z,"I cannot snapshot any Win Server 2019 guest.

I can snapshot a guest before the OS is installed, but after, it refuses to snapshot or export.
Guests are stopped when I attempt. I have created multiple guests to attempt snapshoting, all fail.
Dispite the error message, the NVRAM file is copieed to the destination directory, but vbox fails anyway.
I have checked permissions and selinux.
I have tried temporarily changing the value for the ""Guest OS"" selector, and the ""Graphics Controller""

Version  VirtualBox 6.1.10
Host  CentOS linux kernel 3.10.0-1127.13.1.el7.x86_64


{{{

Failed to create a snapshot of the virtual machine melbourne.

Could not copy NVRAM file '/home/vmadmin/VirtualBox_VMs/melbourne/melbourne.nvram' to '/home/vmadmin/vbox_vms/melbourne/snapshots/2020-06-26T20-32-43-296493000Z.nvram' (VERR_NOT_SUPPORTED).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: SessionMachine
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

",Charlweed
13653,VBox > 4.3.14 has flicker / slow redrawing of UI elements (regression),Linux,Windows,VirtualBox 4.3.20,2020-06-27T22:29:48Z,2020-06-27T22:29:48Z,"Host: Fedora 20 x86_64
Host video card: NVIDIA 9500 (driver 340.58)
Guest: Windows 7 x86_64

Any VirtualBox newer than 4.3.14 causes UI elements to flicker or slow / not redraw when the mouse hovers over them when 3D support is enabled and the 3D driver is installed.

VBox guest additions version does not matter. I can have 4.3.20 guest additions installed on 4.3.14 and no flickering occurs, but upgrading the host binaries to 4.3.16, 4.3.18, or 4.3.20 will induce UI flickering. It causes 3D / Aero to be unusable.

Also see: https://forums.virtualbox.org/viewtopic.php?f=7&t=64424&p=305456",Michael
8698,VirtualBox Host-Only Network Adapter prevents multicast traffic,Windows,other,VirtualBox 4.0.4,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
19687,Kali problem,Linux,other,VirtualBox 6.1.10,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
19691,Virtualbox crashes when not used,Linux,Windows,VirtualBox 6.1.10,2020-06-30T09:26:45Z,2020-06-30T09:26:45Z,"I got several crashes, at seemlingly random time, but alwys when I was not working on gest, but on host.

Log is the same :
ShClipboard[95831]: segfault at 4 ip 00007f6cc00252c0 sp 00007f6cb2818d00 error 4 in VBoxSharedClipboard.so[7f6cc001e000+8000]
(same ip, sp and address in VBoxSharedClipboard for all crashes).
",erwan
19681,Linux Mint 32-bit Guest will not fully restart on Mac OS X Catalina host after installed Guest Additions,Mac OS X,Linux,VirtualBox 6.1.10,2020-06-30T14:37:01Z,2020-06-30T14:37:01Z,"After I installed the Guest Additions on my 32-bit Linux Mint virtual machine, the VM Guest will not restart properly. I can enter my user password, but then the operating system won't finish booting to the desktop, and it appears to hang on a blank screen. I left the Guest machine sitting for ~ 20 minutes on the blank screen before I give up and force it to stop.

Approximate steps
- Create a blank virtual machine: Ubuntu 32-bit, ~3.5GB Memory, 30GB hard drive (VDI, dynamic)
- Start the virtual machine, when prompted insert the Linux ISO
- Complete the operating system installation
- When prompted, remove the ISO from Optical drive and restart VM 
- Install operating system updates in Synaptic and restart VM
- Insert the Guest Additions CD and run the installer
- After Guest Additions finishes installation, restart the VM
- Enter the user password & Wait for the machine to finish boot

Observed; the Guest machine just appears to hang on blank black screen. Eventually give up waiting, and click the red dot to close Guest window and force shut down.

In case I made a mistake, I tried deleting & recreating the virtual machine guest again, but same issue occurs again after install Guest Additions.

Additional machine details:
- Host is Mac OS X Catalina 10.15.5
- VirtualBox Version 6.1.10 r138449 (Qt5.6.3)
- Oracle VM VirtualBox Extension Pack v6.1.10r138449 previously installed
- Guest installed with Linux Mint 19.3 Cinnamon 32-bit",keffie
19680,Clipboard doesn't work for 6.1.10-138449 and Solaris 11.4,Windows,Solaris,VirtualBox 6.1.10,2020-06-30T15:18:30Z,2020-06-30T15:18:30Z,"I've installed multiple times and the clipboard never works despite having enabled bidirectional. I have installed successfully before on a different laptop, earlier vbox and Linux Guest and the clipboard worked.
I don't know if it matters, but I get signature errors when installing the guest additions. See attached.",J_Nicholas
19694,Failure reading data from .iso (optical drive) at random locations,Mac OS X,other,VirtualBox 6.1.10,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
15193,"Errors when I start a virtual machine (Virtual Box Version 5.0.14 r105127, Windows 8 - 64 bit)",Windows,all,VirtualBox 5.0.14,2020-07-02T11:48:06Z,2020-07-02T11:48:06Z,"I installed Virtual Box Version 5.0.14 r105127 on Windows 8 - 64 bit

An error dialog appears when I start a virtual machine.
The error message is:


{{{
Failed to open a session for the virtual machine MacOSXYO.

The virtual machine 'MacOSXYO' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\haipv87\VirtualBox VMs\New group\MacOSXYO\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
}}}


The error log is with content:

{{{
f18.940: supR3HardNtViCallWinVerifyTrustCatFile: WinVerifyTrust => 0x0; cat='C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-SKU-Foundation-Package-avcore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat'; file='\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: supR3HardNtViCallWinVerifyTrustCatFile -> 0 (org 22900)
f18.940: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 22900) fWinVerifyTrust=1 for '\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: Fatal error:
f18.940: supR3HardenedMainGetTrustedMain: LoadLibrary ""C:\Program Files\Oracle\VirtualBox/VirtualBox.dll"" failed, rc=1790
618.c3c: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 984 ms, the end);
fb0.f10: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1350 ms, the end);
}}}


I found some people has the similar problem, but all suggestion not work with my case.

Best Reguard.
",haiphungvan
19696,VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate,Linux,Linux,VirtualBox 6.1.10,2020-07-02T18:24:28Z,2020-07-02T18:24:28Z,"Cloning a VM that is in ""savestate"" can issue a VBOX_E_IPRT_ERROR 0x80BB0005 error.
{{{
[vbox@vm001 vms]$ vboxmanage --version
6.1.10r138449
}}}
Change machine to ""savestate""
{{{
[vbox@vm001 vms]$ vboxmanage controlvm t1 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
Try to clone the machine (note this is all on local disk. No NFS/SMB mounts)
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 610 of file VBoxManageMisc.cpp
}}}
As you can see, the clone fails with ""VBOX_E_IPRT_ERROR (0x80BB0005)"".

Now we do the same thing, but poweroff the vm before doing the clone.
Let's resume the VM from the savestate above.
{{{
[vbox@vm001 vms]$ vboxmanage startvm t1 --type headless
Waiting for VM ""t1"" to power on...
VM ""t1"" has been successfully started.
}}}
Poweroff the VM
{{{
[1803 vbox@scvm001 vms]$ vboxmanage controlvm t1 poweroff       
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
and rerun the clone...
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""t1-20200702-112825-vbbu""
}}}
The clone runs sucessfully to completion.

Virtualbox user forum thread for reference: https://forums.virtualbox.org/viewtopic.php?f=7&t=98881",guideloom
19593,VM window movement broken with Linux-Mate distros and Auto capture keyboard enabled,Linux,Windows,VirtualBox 6.1.8,2020-07-02T19:59:57Z,2020-07-02T19:59:57Z,"Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8

Data:
ubuntu 20.04 LTS
Virtualbox Versión 6.1.8 r137981 (Qt5.12.8)
VirtualBox_Extension_Pack-6.1.8
Tested in Desktop Mate
kernel 5.4.0-29-generic
OpenGL version string: 4.6 
Mesa 20.2.0-devel",maravento
19697,Running VM crashes on macOS 10.13.6 with VirtualBox 6.1.10 r138449,Mac OS X,other,VirtualBox 6.1.10,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
19698,System Boot,other,other,VirtualBox 6.1.10,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
19699,Error opening virtual box after upgrade to 6.1,Windows,Windows,VirtualBox 6.1.10,2020-07-03T14:48:01Z,2020-07-03T14:48:01Z,"Hello,

After upgrade to 6.1 i can no longer open my virtual box image that was working perfectly before this version. How can i make my Virtual box working again with the new version ? 

I will add the logfilesthat were created. 

Thanks",Johan1974
19700,Impossible d'installer le systeme de base,other,Linux,VirtualBox 6.1.10,2020-07-03T20:17:57Z,2020-07-03T20:17:57Z,"Je tente de créer une machine virtuelle sous Kali Linux depuis quelques semaines,A chaque tentative un message d'erreur s'Affiche disant: une erreur s'est produite lors de l'installation du noyau vers le système cible. ",Violon
19701,Cannot list raw disk partition table when sector size != 512 bytes,Mac OS X,Linux,VirtualBox 6.1.10,2020-07-04T07:04:52Z,2020-07-04T07:04:52Z,"VBoxManage returns an empty partition table when the disk has a sector size of 4096 bytes. I think this may be the root cause of the problems reported in tickets

https://www.virtualbox.org/ticket/16705

https://www.virtualbox.org/ticket/16498

{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
}}}
fdisk (on linux) return the following information about the drive.
{{{
Disk model: Expansion Desk  
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 268431360 bytes
Disklabel type: gpt
Disk identifier: C3BE927E-B799-4B59-A37F-8927D38FA8BF

Device         Start       End   Sectors   Size Type
/dev/sdf1          6     76805     76800   300M EFI System
/dev/sdf2      76806  61110489  61033684 232.8G Apple APFS
/dev/sdf3   61143258 482519263 421376006   1.6T Linux filesystem
/dev/sdf4  482552032 488345871   5793840  22.1G Linux swap
}}}

Using a disk with a sector size of 512 bytes is successful.
{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x00  0   /0  /0   0   /0  /0            200           40
2       0x00  0   /0  /0   0   /0  /0         238546       409640
3       0x00  0   /0  /0   0   /0  /0        1648981    488953032
4       0x00  0   /0  /0   0   /0  /0          20001   3866066944
}}}
fdisk for this drive shows
{{{
Disk model: 006-2DM164      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 0F3513DC-A778-4280-BB61-5399F44E1135

Device          Start        End    Sectors  Size Type
/dev/sdf1          40     409639     409600  200M EFI System
/dev/sdf2      409640  488953031  488543392  233G Apple APFS
/dev/sdf3   488953032 3866066943 3377113912  1.6T Linux filesystem
/dev/sdf4  3866066944 3907028991   40962048 19.5G Linux swap
}}}",granada29
19702,在开启了  Hyper-V  的  Windows 10 上运行  VirtualBox  虚拟机，会发生崩溃,Windows,Linux,VirtualBox 6.1.10,2020-07-04T12:39:53Z,2020-07-04T12:39:53Z,"我在  VirtualBox  上运行  Arch  Linux  操作系统时，虚拟机出现错误，导致我无法安装  Arch  Linux  操作系统。  

具体现象：虚拟机能够成功启动，但是尝试运行位于  Live  CD  的操作系统时，会发生崩溃

镜像源：  https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-10.4.0-amd64-DVD-3.iso

",FANminiworld
19688,Linux 5.7.x + VBox 6.1.10 driver install failure,Linux,other,VirtualBox 6.1.10,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
19703,VBoxManage and VirtualBox Manager lock up,Linux,all,VirtualBox 6.0.22,2020-07-06T10:26:57Z,2020-07-06T10:26:57Z,"On 4.15.0-108-generic my VirtualBox works fine. Upgrading to 4.15.0-109-generic seems to be a problem for managing Virtual Machines on Virtualbox 6.022 r137980.

VBoxManage as well as VirtualBox Manager seem to lock up when using that version. Virtual Machines just run, until you try to shut them down.

VirtualBox Manager doesn't update the screen anymore. VBoxManage just hangs. Only reboot seems to solve the issue.

I reverted back from 108 to 109 and everything seems to be okay again.

Not 100% sure if it is this upgrade, but it appears so. Thought I better report.",NickGuus
19690,Update for Microsoft Windows KB4560960 creates issues with VBox Guest,Windows,Windows,VirtualBox 6.1.10,2020-07-06T14:11:29Z,2020-07-06T14:11:29Z,"Host: Windows 10
Guest: Windows 7 

After installing recent windows update on host, VBox guests started malfunctioning and could boot.

We then troubleshooted the issue and found that one of the windows update is creating issue which we uninstalled and now guests working smoothly

Here is the update created the issue.
Update for Microsoft Windows KB4560960

I request to test and release the fix for the same.

Thank you
Harsh",hsparekh
19705,E_FAIL (0x80004005)-IMachine {85632c68-b5bb-4316-a900-5eb28d3413df},Windows,all,VirtualBox 6.1.10,2020-07-07T14:23:19Z,2020-07-07T14:23:19Z,"Dear all,

Host : Windows 7 Enterprise 64bit,
Laptop Toshiba Satellite L645
Virtual box Version 6.1.10 r138449 (Qt5.6.2)
Avast AV already uninstall
Firewall already setup to allow this virtualbox
VT-X already disable (when the VT-X was enabled,that still error found on virtualbox)


when I was going running  the Windows 7 or Linux , error


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}.



I was forgot what is old version of Virtual box that installed before.
and with old version, virtual box is normal and not found error


Please fix it and help me....Thanks

",n3wkid2019
19707,Add ability to sort and group virtual computers with tags,other,other,VirtualBox 6.1.10,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
19708,Memory Reference Error,Windows,Linux,VirtualBox 6.1.10,2020-07-08T21:04:33Z,2020-07-08T21:04:33Z,"When running Ubuntu 20 (Linux Mint AND Budgie) I get a memory reference error.  Seems something is trying to write to 0x0000.

I've reproduced this in 6.1.9 and 6.1.10.  Host os is Windows 10.  HW is HP ZBook G5, 48GB RAM and 800+ GB disk.  ",grpark
19692,not compatible with dual display with different dpi scaling,Windows,OSX Server,VirtualBox 6.1.10,2020-07-09T03:26:34Z,2020-07-09T03:26:34Z,"I launched virtualbox in display 1 with 200% dpi scaling, when I drag the window to second screen with 100% dpi scaling the title of the window become very large.
instead, when drag from 100% to 200% every thing in 200% become very small.",liurunliang
19704,VirtualBox 6.1.8 machine restart crash,Windows,Windows,VirtualBox 6.1.8,2020-07-09T08:15:09Z,2020-07-09T08:15:09Z,"Hello.
VirtualBox 6.1.8-137981 works fine, but randomly when restarting crash the machine being only possible close the machine window and start an new machine window.
LOG are here added.
Excuse not is possible for me in moment test current version, but perhaps has the same issue because that crash when restart is since more of 2 previous versions.
Have an nice day.",Augusto
19169,"CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with ""IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)""",Windows,Windows,VirtualBox 6.0.8,2020-07-09T13:03:59Z,2020-07-09T13:03:59Z,"When applying the [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135 CVE-2019-11135] microcode update via Microsoft's [https://support.microsoft.com/en-us/help/4524570/windows-10-update-kb4524570 2019-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4524570)], a Win10 (64-bit) guest will not boot completely, but will rather get stuck with:
{{{
00:00:07.800331 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)
}}}
Intel CPUs that have been affected so far are all Q2'19:
* [https://ark.intel.com/content/www/us/en/ark/products/193563/intel-core-i7-8665u-processor-8m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192987/intel-core-i9-9880h-processor-16m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192993/intel-xeon-e-2286m-processor-16m-cache-2-40-ghz.html Intel(R) Xeon(R) E-2286M  CPU @ 2.40GHz]

This affects all !VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=95783",Socratis
19712,Repeatedly adding file extensions in disk creation,all,all,VirtualBox 6.1.10,2020-07-09T21:31:27Z,2020-07-09T21:31:27Z,"In the ""Create Virtual Hard Disk"" dialog during the creation of a new virtual machine in expert mode, selecting any of the hard disk file type options adds an extra extension to the name of the file. For example, if ""VDI (Virtual Disk Image)"" is selected and the file location displays ""C:/Users/user/VirtualBox VMs/os/disk.vdi"", and the user then selects ""VHD (Virtual Hard Disk)"" then the file location is changed to ""C:/Users/user/VirtualBox VMs/os/disk.vdi.vhd"" instead of ""C:/Users/user/VirtualBox VMs/os/disk.vhd"". Repeated switching back and forth between the two will yield ""C:/Users/user/VirtualBox VMs/os/disk.vdi.vhd.vdi.vhd.vdi.vhd"". Note that the bug also occurs while switching between the other options.

This error occurs during hard disk creation during the creation of a new VM, or by creating a new hard disk in the settings dialogue of an existing VM. This only occurs in expert mode in both cases.

Steps to reproduce:
1. Open VirtualBox click the ""New"" button to create a new VM.
2. Ensure that Expert Mode is selected.
3. Select ""Create a virtual hard disk now""
4. Name the VM.
5. Select any operating system type and version, the bug occurs for any of them.
6. Click create.
7. Select a hard disk file type other than the one currently selected e.g. ""HDD (Parallels Hard Disk)""
8. Observe that an additional file extension was added to the ""File Location"" text field.

This bug initially occurred hosted on Windows 10 Version 2004 using a fresh installation of VirtualBox 6.1.10. I was also able to reproduce the error on Xubuntu 18.04 with VirtualBox 6.1.10 following the exact same steps.",tarix29
19713,Virtual Box Booting Issue,Linux,Linux,VirtualBox 5.2.34,2020-07-10T10:30:32Z,2020-07-10T10:30:32Z,"
I am Using using Ubuntu version :  Ubuntu 18.04.4 LTS
                Virtual Box Version : 5.2.34

While start using iso file from my local after Windows logo system got hanged everytime
Could you suggest and help to resolve the issue.",Ujjal
16707,Add port #'s to USB Filters,all,all,,2020-07-10T22:01:34Z,2020-07-10T22:01:34Z,"The ""port"" space of the USB filter is not showing anything, making usage of USB devices with same vendorid, productid, and revision numbers, etc. difficult to sort and use.

If multiple USB devices containing different data but having identical Virtualbox USB filter information need to be reliably distributed to specific guests, the VB USB filter can't distinguish which USB device to use and sends all of them into the first guest available. Inserting another dongle into the host immediately sends the new dongle into the first guest, requiring further finagling to get the dongle into the next desired guest. Or if by chance the second guest was started first, it would not be known which of the dongles was in the guest, if not all of them at once. In either case further manual manipulation is needed after the guests are started to figure out which donlge to put in which guest.

If the port space showed which USB port the desired device was plugged into, and was filterable, then as long as the device is continually used in the same port, the VB USB filter will be able to distinguish them and filter them into the desired guests automatically.

A company called KernelPro (http://www.kernelpro.com/usb-over-ethernet.html) has a USB-over-ethernet server program that casn differentiate USB devices with the same vendorid, productid, revision, etc. by the port number the USB device is plugged into. Please see the attached screenshot. I have five license dongles attached to this USBoE server. Notice that four of the five have the same vendorid, productid, and revision numbers, even though they contain different license data in each dongle, so they are not swappable. The server can distinguish them and send them reliably, because it keeps track by port number.
",scottgus1bug
19715,VRDP/VBoxAuth not accepting MSTSC connection,Windows,Windows,VirtualBox 6.1.8,2020-07-10T22:29:45Z,2020-07-10T22:29:45Z,"I've been trying to do this off and on for several years and on many versions of VB without success.  I've been through the documentation many times and asked for help on the forums.  Nobody has been able to find a solution and others have reported that this happens for them as well, including on Mac OS and Windows 7 and 10 hosts.

Host OS = Win 8.1[[br]]
Guest OS = Win XP[[br]]
VB version = 6.1.8, with matching extension pack[[br]]
VRDP Authentication = External/default (VBoxAuth)[[br]]
VRDP Port = 5003[[br]]

This process works fine if Authentication = Null, but when set to External I cannot make a connection from my local host (or any other Windows host) to the guest machine via VRDP. MSTSC tells me ""This computer can't connect to the remote computer"" before it even asks for a login.

I have been trying this on many different versions of VB, going back to the early days of v4.x.  Considering how widespread it seems to be in VB releases and across various hosts, I would think this is a problem that is part of the basic functionality.

A log is attached, but the important message from it seems to be
 ""AUTH: external authentication module returned 'access denied'""
",Davin
12646,XP Guest GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6 => Fixed in SVN,Windows,Windows,VirtualBox 4.3.4,2020-07-11T19:27:22Z,2020-07-11T19:27:22Z,"When running 16 bit Apps in XP, there is an occasional GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6.  Same app sometimes works OK.
For me, this problem did not exist through many version of VB through 4.2.18 and started with 4.3.4.

The only web research I have was from a VMWare post that may or may not apply here (quoted from cwsault original post):

""There are a few applications which may fail with this error when executed in a VM. The problem is that the library tries to read the instruction bytes of the last FPU instruction executed based on the code segment and instruction pointer saved in the FPU environment. Unfortunately, the code segment saved in the FPU environment may be NULL.

When we switch between the virtual machine monitor and the host operating system, we use the primitive hardware instructions to save and restore the FPU state. These instructions were not really designed for an environment that mixes 32-bit and 64-bit execution. When the instructions are executed in 64-bit mode, they don't keep track of the code segment, since segments have little meaning in 64-bit mode. The virtual machine monitor, which saves and restores the FPU state for the guest VM, executes in 64-bit mode. Hence, the FPU code segment is lost.

Fortunately, there is a workaround for this issue. If you add the following option to your configuration file, we will make sure that the FPU code segment is properly saved and restored when switching between the virtual machine monitor and the host operating system (at some small performance penalty):
    
monitor_control.enable_rigorous_fpu_save_restore = TRUE""
",SteveDeveloper
19693,Failed to open a session the virtual machine in Win 7 Enterprise SP 1 64 Bit,Windows,Linux,VirtualBox 6.1.10,2020-07-13T14:52:43Z,2020-07-13T14:52:43Z,"Dear all,

My windows:

Win 7 Enterprise 64 bit, SP1
Ram 8Gb
Virtualbox Latest ( 6.1.10 r138449 Qt5.6.2 )

when running to install Linux Mint, error show is below :

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


please fix this is.

note: All my virtual already installed, error same.. could not run and failed session.


Thanks
",n3wkid2019
19714,USB Port filter should use Linux USB bus id instead of a random number,Linux,all,VirtualBox 6.1.10,2020-07-14T09:15:33Z,2020-07-14T09:15:33Z,"On Linux the ""port"" field in the ""USB Filter"" should ideally use the physical bus id instead of a random number.[[BR]]
In my use case I'd like to create an USB filter limited to a specific physical USB port. If the user e.g. puts some random USB memory stick into this specific physical USB port, it should show up in the VM. For that it would be necessary to have a USB filter which can refer to a unique ""port"", which the current implementation can not guarantee.[[BR]]
[[BR]]
E.g. currently I see this on my machine:[[BR]]
{{{
UUID:               9b7430c2-c602-49d8-84e9-ffbb3a22bce0
VendorId:           0x04d9 (04D9)
ProductId:          0x1133 (1133)
Revision:           2.16 (0216)
Port:               1
USB version/speed:  1/Low
Manufacturer:       Holtek Semiconductor, Inc.
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               191cbe8f-442d-4f5e-9552-c0b0cd7bf119
VendorId:           0x046a (046A)
ProductId:          0x0023 (0023)
Revision:           0.50 (0050)
Port:               1
USB version/speed:  2/Low
Manufacturer:       Cherry GmbH
Product:            CyMotion Master Linux Keyboard G230
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2//device:/dev/vboxusb/002/002
Current State:      Busy
}}}

As you can see in the example above, both USB ports have ""Port: 1"" and thus they are not uniquely identifyable. So it would be more useful to instead refer the ""Port"" field to ""3-2"" for the first entry, and to ""2-2"" in the second entry (see the ""Address"" field).
",Helge Deller
19720,Rebooting causes colored stripes in the VM and a Guru meditation,Windows,all,VirtualBox 6.1.10,2020-07-15T02:15:48Z,2020-07-15T02:15:48Z,"Every time I reboot my guest it has colored stripes on the top of the VM's screen then goes into guru meditation, this happens less on BIOS VMs, mostly happens on linux but also happens on Windows (Mostly 7,8,8.1)",OakBricks
19718,Failed to start VirtualBox hub service,Linux,other,VirtualBox 6.1.10,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
19722,Windows server 2019 Seamless Graphical problem,Windows,Windows,VirtualBox 6.1.10,2020-07-15T07:30:28Z,2020-07-15T07:30:28Z,"Hello, There is annoying bug in Virtualbox 6.1.12
Steps to reproduce :

1-Install a clean Windows server 2019 x64 DataCenter With Desktop Experience (Personally tested 1809 and 1903)
2-Install VirtualBox Guest Additions 6.1.12, reboot pc.
3-Enter seamless mode.
4-Click on virtual machine Start Menu.
5-there is no start menu from guest on host.

[[Image(https://img.techpowerup.org/200715/annotation-2020-06-12-174715.png)]]

[[Image(https://img.techpowerup.org/200715/annotation-2020-06-12-174740.png)]]

problem exist in all UWP apps.
tested with VBOXVGA and VBOXSVGA.",VBuser1
19725,my VM Centos 8 starting kicking me out,Windows,Linux,VirtualBox 6.1.10,2020-07-15T18:49:56Z,2020-07-15T18:49:56Z,"This morning I  had a pop up to reboot my Window server for updates.

Before I rebooted Windows,  I went over to my Linux CentOS 8 VM and gracefully shut it down.

After it was completely down, I rebooted Windows.

After windows came backup, I started my Centos 8 VM,  it took a very long time to start, but eventually my sing on GUI was up, I was able to login and open a terminal and ran a few commands,  suddenly  it closed my terminal and went back to the sing on GUI.

I went to Oracle VM VirtualBox Manager, clicked on File, then clicked on Check for updates,  I received ""You are already running the most recent version..."". Since the version number did not show, I looked at Help - About VirtualBox - I was running 6.1.8.

I starting googling and found that the latest version is 6.1.12, so I downloaded and installed it.  I also install the latest extpack and the latest guest additions.

After the CentOS 8 reboot, I was able to login and work for about 15 minutes before it kicked me out again, back to the sign on GUI.

",Saca
19727,Cannot connect to OCI Cloud: VERR_CR_KEY_UNSUPPORTED_CIPHER,Linux,other,VirtualBox 6.1.10,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
19719,Virtualbox 6.1.12 r139181 Win7 Guest Crash VboxVGA,Windows,Windows,,2020-07-17T04:36:02Z,2020-07-17T04:36:02Z,"Just installed the VBox 6.1.12 update and updated the Guest Additions. Windows 7 x64 (newest updates) does not start anymore, it crashes with a blue screen.
Graphics Adapter is VBoxVGA. It works with other graphics adapters configured in settings.",JayEm1
19679,Crash of VirtualBoxVM 6.1.10 Ubuntu 18.04 guest on macOS 10.15.5 host after installing 6.1.10 guest additions,Mac OS X,Linux,VirtualBox 6.1.10,2020-07-18T01:38:24Z,2020-07-18T01:38:24Z,"Hi,

I've got a crash of VirtualBoxVM 6.1.10 Ubuntu 18.04 guest on macOS 10.15.5 host after installing 6.1.10 guest additions. This crash occurs every time I try to boot up this VM right after entering the Login credentials into the guest. See attached log files",Lars Sonchocky-Helldorf
19735,headless start failed with vmsvga display,Linux,Linux,VirtualBox 6.1.10,2020-07-19T17:00:05Z,2020-07-19T17:00:05Z,"Host - fedora 31 workstation

Guest - Ubuntu 18.04.4 LTS

VirtualBox 6.1.12

1. I set up VMSVGA (as recommended for linux guests) with 3D driver in VM settings
2. I logon to host with ssh
3. I have started VM by command: VBoxManage startvm ""vmname"" --type headless
4. VM started
5. Shortly VM stoped with status ""interrupted""

6. I set up old VBoxVGA driver without 3D in VM settings
7. I have repeated steps 2-3
8. All is OK!

9. I have repeated step 1
10. I logon to host with ssh BUT with -X option
11. I have repeated step 3
12. All is OK
13. BUT when I have closed session (which started at step 10) then my VM stopped!

I would like to use steps 1-4 but without step 5 :)
At this time I use my VM with old VBoxVGA driver.
May be step 5 - result of some bug with VMSVGA driver...",tol2000
19738,Virtualbox aborting on resume,Windows,Linux,VirtualBox 6.1.10,2020-07-20T04:28:10Z,2020-07-20T04:28:10Z,"Windows 10 2004 19041.388
Virtualbox 6.1.12

This happens in three ways
1) save-state -> resume vm
2) running -> pause -> resume vm
3) start as hidden -> show -> close-window and continue running in the background

a popup box appears
VBoxHeadless.exe - Application Error
The instruction at 0x... referenced memory at 0x0000..000C. The memory could no be read
Click OK to terminate the program

00:00:25.871086 VMMDev: Guest Additions capability report: (0x0 -> 0x4) seamless: no, hostWindowMapping: no, graphics: yes
00:00:26.335303 VMMDev: Guest Log: 22:32:02.516677 main     VBoxService 6.1.10_Fedora r138449 (verbosity: 0) linux.amd64 (Jun  8 2020 00:00:00) release log
00:00:26.335670 VMMDev: Guest Log: 22:32:22:32:02.517571 main     OS Product: Linux
00:00:26.337367 VMMDev: Guest Log: 22:32:02.519165 main     OS Release: 5.7.8-200.fc32.x86_64
00:00:26.338250 VMMDev: Guest Log: 22:32:02.519954 main     OS Version: #1 SMP Thu Jul 9 14:34:51 UTC 2020
00:00:26.339013 VMMDev: Guest Log: 22:32:02.520828 main     Executable: /usr/sbin/VBoxService
00:00:26.339255 VMMDev: Guest Log: 22:32:02.520828 main     Process ID: 421
00:00:26.342033 VMMDev: Guest Log: 22:32:02.520829 main     Pa22:32:02.523773 main     6.1.10_Fedora r138449 started. Verbose level = 0
00:00:26.344597 VMMDev: Guest Log: 22:32:02.526267 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:26.345107 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:00:37.138464 IEM: rdmsr(0x122) -> #GP(0)
00:49:57.970214 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:49:57.970344 PDMR3Suspend: after     0 ms, 1 loops: 1 async tasks - virtio-scsi/0
00:49:59.069354 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0781) created successfully
00:49:59.426309 AIOMgr: Async flushes not supported
00:49:59.505913 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0781) created successfully
00:49:59.541990 PDMR3Suspend: 1 571 708 931 ns run time
00:49:59.542009 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:49:59.542021 Console: Machine state changed to 'Paused'
00:50:04.490337 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:50:04.490657 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0723) created successfully
00:50:04.495647 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0723) created successfully
00:50:04.500963 Changing the VM state from 'RESUMING' to 'RUNNING'
00:50:04.500977 Console: Machine state changed to 'Running'
00:50:04.501069 
00:50:04.501070 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002f58!!!
00:50:04.501075 
00:50:04.501075 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501079 ExceptionInformation[0]=0000000000000000
00:50:04.501082 ExceptionInformation[1]=000000000000000c
00:50:04.501085 
00:50:04.501085 cs:rip=0033:00007ffa18bb0023
00:50:04.501089 ss:rsp=002b:0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501093 rax=00000000000022e0 rcx=00000000064b0000 rdx=00000000064b3340 rbx=00000000064b0000
00:50:04.501096 rsi=00000000064b3340 rdi=0000000000000000 rsp=0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501102 r8 =00000000064b0140 r9 =0000000000000004 r10=0000000008f4fb10 r11=0000000008f4fb10
00:50:04.501107 r12=00000000064b3340 r13=0000000000000000 r14=0000000000000020 r15=0000000000000060
00:50:04.501110 ds=002b es=002b fs=0053 gs=002b eflags=00010287
00:50:04.501113 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000064b0000
00:50:04.501117 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:50:04.501126 
00:50:04.501126 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000456c!!!
00:50:04.501137    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:50:04.501147 
00:50:04.501148 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501176 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:50:04.501190 ExceptionInformation[0]=0000000000000000
00:50:04.501202 
00:50:04.501203 Stack 0000000008f4c740, dumping 0x38c0 bytes (low=0000000008e50000, high=0000000008f50000)
00:50:04.501215 ExceptionInformation[1]=000000000000000c

Though VMSVGA display adapter is configured, it does not matter which display-adapter is configured, same effect for each.
No sound device is enabled.
I have ensured that hyper-V hypervisor is not enabled

There is a intel haxm type-2 hypervisor, which occasionally is run with android-emulator/qemu. My understanding is that it should not interfere. The joint installtion has worked before. Plus no qemu-VM is running. 

Save/Resume/Show/Hide has worked before.  


",gkamathh
19739,Menu opens on wron place,Windows,Windows,VirtualBox 6.1.10,2020-07-20T08:26:15Z,2020-07-20T08:26:15Z,"VirtualBox 6.1.12 r139181 (Qt5.6.2)

When I click on a menu the menu opens on the wrong place.",Eistee
19041,Debian Buster guest aborted after host resumes from sleep,Mac OS X,Linux,VirtualBox 6.0.14,2020-07-21T11:15:11Z,2020-07-21T11:15:11Z,"1. Start Debian Buster guest either headless or normal
1. Put host to sleep (in my case my shutting laptop)
1. Resume host
1. Guest is aborted

This happens with or without guest additions.

This could well be the same as #13874

",planck_length
19744,Critical Error,Windows,Linux,VirtualBox 6.1.10,2020-07-21T19:42:00Z,2020-07-21T19:42:00Z,Critical error ocurs while compiling with GCC. All my woes seems to have started after upgrading windows 10 (the host) to version 2004 and virtualbox to 6.1.12 r139181 (Qt5.6.2). I often also get program referenced illeegal memory at 0x000000 warra warra warra.,Tiaan
19745,"Add emulation for x86, ARM guests",other,other,VirtualBox 6.1.10,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
19746,while installing os it stucks at black screen,Windows,all,VirtualBox 6.1.10,2020-07-22T06:20:18Z,2020-07-22T06:20:18Z,"I checked off Hyper-V and 3D acceleration but still, it's stuck at the black screen I waited for half-hour its shows running and stuck at the black screen",promethius
19580,Crash on switch from guest(Win10) to host(Catalina) window,Mac OS X,Windows,VirtualBox 6.0.20,2020-07-22T09:43:50Z,2020-07-22T09:43:50Z,"VBox crashes periodically after mouse click outside guest window.
",Yauheni
19748,VirtualBox 6.1.12 allows to create a fixed disk bigger than free space,Windows,Windows,,2020-07-22T12:35:44Z,2020-07-22T12:35:44Z,"Good afternoon,

Creating a virtual machine allows you to also add a new disk. In my opinion, if you choose fixed size, the program shouldn't allow to create disks bigger than the free space.

You can see it in [https://streamable.com/fr8dyj this video].

Regards.",Antonio López Fernández
19750,Changing from guided to expert mode deletes,Windows,Windows,VirtualBox 6.1.10,2020-07-22T12:48:02Z,2020-07-22T12:48:02Z,"Good afternoon,

By the time you add a new machine, the program detects the operating system when you type VM's name. If you change from guided to expert mode, it deletes VM's name and detected OS.

You can see it in [https://streamable.com/cd8btm this video].

Regards.",Antonio López Fernández
11211,Feature request: add auto update functionality,Mac OS X,other,VirtualBox 4.2.4,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
19752,Linux VMs are not running with MS Defender Application Guard,Windows,Linux,VirtualBox 6.1.10,2020-07-22T18:57:43Z,2020-07-22T18:57:43Z,"If you install/activate this Microsoft feature, all Linux VMs will stay stuck with a black screen.
I was just able to start without issue a Win 7 VM.

After removing the MS feature, all Linux VMs (and Windows)are running fine.

Regards,",Cruzzy54
19558,Clipboard failure,Mac OS X,other,VirtualBox 6.1.6,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
19755,VirtualBox crashed with EXC_CRASH (SIGABRT) after resuming on macOS 10.14.6 - malloc: Incorrect checksum for freed object,Mac OS X,Windows,VirtualBox 6.1.10,2020-07-23T20:16:23Z,2020-07-23T20:16:23Z,"Running two Windows VMs simultaneously, with internal networking, VirtualBox crashed on sleep and resume (reopening lid) of macOS 10.14.6

abort() called
VirtualBoxVM(14390,0x70000d07f000) malloc: Incorrect checksum for freed object 0x7fe3f2011800: probably modified after being freed.
Corrupt value: 0x0

#19050 ? 

{{{
Process:               VirtualBoxVM [14390]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.10 (6.1.10)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [13937]
Responsible:           VirtualBoxVM [14390]
User ID:               501

Date/Time:             2020-07-23 10:08:50.261 -0400
OS Version:            Mac OS X 10.14.6 (18G6020)
Report Version:        12
Bridge OS Version:     4.6 (17P6065)
Anonymous UUID:        

Sleep/Wake UUID:       

Time Awake Since Boot: 31000 seconds
Time Since Wake:       10 seconds

System Integrity Protection: enabled

Crashed Thread:        8  EMT-0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
VirtualBoxVM(14390,0x70000d07f000) malloc: Incorrect checksum for freed object 0x7fe3f2011800: probably modified after being freed.
Corrupt value: 0x0
 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   com.apple.HIToolbox           	0x00007fff2d7b91ab RunCurrentEventLoopInMode + 292
6   com.apple.HIToolbox           	0x00007fff2d7b8ee5 ReceiveNextEventCommon + 603
7   com.apple.HIToolbox           	0x00007fff2d7b8c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8   com.apple.AppKit              	0x00007fff2bb5077d _DPSNextEvent + 1135
9   com.apple.AppKit              	0x00007fff2bb4f46b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
10  com.apple.AppKit              	0x00007fff2bb49588 -[NSApplication run] + 699
11  libqcocoa.dylib               	0x0000000115808eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
12  org.qt-project.QtCoreVBox     	0x000000010ea34791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
13  org.qt-project.QtCoreVBox     	0x000000010ea38b4a QCoreApplication::exec() + 346
14  VirtualBoxVM.dylib            	0x000000010e6ccd4e TrustedMain + 1502
15  org.virtualbox.app.VirtualBoxVM	0x000000010de05951 0x10de02000 + 14673
16  libdyld.dylib                 	0x00007fff5a4d93d5 start + 1

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff5a615616 __select + 10
1   VBoxXPCOM.dylib               	0x00000001121b18a0 0x112127000 + 567456
2   VBoxXPCOM.dylib               	0x00000001121b36e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000011827be75 0x118269000 + 77429
4   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x00000001182747b8 0x118269000 + 47032
5   VBoxXPCOM.dylib               	0x000000011218b1f9 0x112127000 + 410105
6   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x0000000118388711 0x118291000 + 1013521
4   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
5   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000011826e71b 0x118269000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000011826e3ed 0x118269000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x0000000118273039 0x118269000 + 41017
7   VBoxXPCOM.dylib               	0x000000011219a2ed 0x112127000 + 471789
8   VBoxXPCOM.dylib               	0x00000001121994eb 0x112127000 + 468203
9   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
11  org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
12  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
13  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
14  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x00000001182d52f0 0x118291000 + 279280
4   VBoxC.dylib                   	0x00000001182d651d 0x118291000 + 283933
5   VBoxC.dylib                   	0x000000011845e90a 0x118291000 + 1890570
6   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
8   org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxC.dylib                   	0x00000001182d52f0 0x118291000 + 279280
4   VBoxC.dylib                   	0x00000001182d651d 0x118291000 + 283933
5   VBoxC.dylib                   	0x000000011845e90a 0x118291000 + 1890570
6   UICommon.dylib                	0x000000010fdca172 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	0x000000010fbde2f7 0x10faf8000 + 942839
8   org.qt-project.QtCoreVBox     	0x000000010e87a96b 0x10e851000 + 170347
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 7:: MainHGCMthread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x00000001184293eb 0x118291000 + 1672171
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 8 Crashed:: EMT-0
0   libsystem_kernel.dylib        	0x00007fff5a6142c2 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff5a6cfbf1 pthread_kill + 284
2   libsystem_c.dylib             	0x00007fff5a57e6a6 abort + 127
3   libsystem_malloc.dylib        	0x00007fff5a68d077 malloc_vreport + 545
4   libsystem_malloc.dylib        	0x00007fff5a6a5e0d malloc_zone_error + 183
5   libsystem_malloc.dylib        	0x00007fff5a6895c8 small_free_list_remove_ptr_no_clear + 1177
6   libsystem_malloc.dylib        	0x00007fff5a6881db small_malloc_from_free_list + 152
7   libsystem_malloc.dylib        	0x00007fff5a687afc small_malloc_should_clear + 284
8   libsystem_malloc.dylib        	0x00007fff5a685245 szone_malloc_should_clear + 120
9   libsystem_malloc.dylib        	0x00007fff5a686444 malloc_zone_calloc + 99
10  libsystem_malloc.dylib        	0x00007fff5a6863c4 calloc + 30
11  VBoxDD.dylib                  	0x000000011fe387b6 0x11fde1000 + 358326
12  VBoxDD.dylib                  	0x000000011fe37d3e 0x11fde1000 + 355646
13  VBoxDD.dylib                  	0x000000011fe348d9 0x11fde1000 + 342233
14  VBoxVMM.dylib                 	0x0000000111f03798 IOMIOPortWrite + 312
15  VBoxVMM.dylib                 	0x0000000111df000d 0x111da1000 + 323597
16  VBoxVMM.dylib                 	0x0000000111de69fc 0x111da1000 + 285180
17  VBoxVMM.dylib                 	0x0000000111dea70a 0x111da1000 + 300810
18  VBoxVMM.dylib                 	0x0000000111de808c 0x111da1000 + 290956
19  VBoxVMM.dylib                 	0x0000000111e4d2ee 0x111da1000 + 705262
20  VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
21  VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
22  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
23  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
24  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 9:: EMT-1
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff11c6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	0x0000000111e4eb32 0x111da1000 + 711474
5   VBoxVMM.dylib                 	0x0000000111e4db01 0x111da1000 + 707329
6   VBoxVMM.dylib                 	0x0000000111de847b 0x111da1000 + 291963
7   VBoxVMM.dylib                 	0x0000000111e4d2ee 0x111da1000 + 705262
8   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
9   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
10  libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
11  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
12  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 10:: ShClipboard
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 11:: SHCLIP
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeb526 0x10de4b000 + 1705254
3   VBoxRT.dylib                  	0x000000010df351d9 RTThreadUserWait + 73
4   VBoxSharedClipboard.dylib     	0x0000000117921bd7 0x11791a000 + 31703
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 12:: DragAndDropSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 13:: Timer
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeaa9c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x000000010dfdbd4d 0x10de4b000 + 1641805
4   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
5   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 14:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff5a611f2e __semwait_signal + 10
1   libsystem_c.dylib             	0x00007fff5a59d914 nanosleep + 199
2   VBoxRT.dylib                  	0x000000010dfeea33 RTThreadSleep + 67
3   VBoxVMM.dylib                 	0x0000000111f3c35a 0x111da1000 + 1684314
4   VBoxVMM.dylib                 	0x0000000111e0e49f 0x111da1000 + 447647
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 15:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   com.apple.AppKit              	0x00007fff2bb584a2 _NSEventThread + 175
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 16:: ShFolders
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 17:: GuestControlSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 18:: GuestPropSvc
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxC.dylib                   	0x0000000118424ef5 0x118291000 + 1654517
4   VBoxC.dylib                   	0x00000001184255e6 0x118291000 + 1656294
5   VBoxC.dylib                   	0x000000011842613d 0x118291000 + 1659197
6   VBoxC.dylib                   	0x0000000118424ccf 0x118291000 + 1653967
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 19:: GstPropNtfy
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010df325e2 RTReqQueueProcess + 146
4   VBoxGuestPropSvc.dylib        	0x0000000122093081 0x12208d000 + 24705
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 20:: VMSVGA FIFO
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe759bf 0x11fde1000 + 608703
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 21:: ATA-0
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe0e3f9 0x11fde1000 + 185337
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 22:: ATA-1
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe0e3f9 0x11fde1000 + 185337
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 23:: TaskSet0
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxVMM.dylib                 	0x0000000111e0d067 0x111da1000 + 442471
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 24:: NATRX
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011ff1a63a 0x11fde1000 + 1283642
4   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 25:: NATURGRX
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxDD.dylib                  	0x000000011ff1a69a 0x11fde1000 + 1283738
4   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 26:: HOSTRES
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeab4b RTSemEventWait + 539
3   VBoxRT.dylib                  	0x000000010df325e2 RTReqQueueProcess + 146
4   VBoxDD.dylib                  	0x000000011ff1a701 0x11fde1000 + 1283841
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 27:: NAT
0   libsystem_kernel.dylib        	0x00007fff5a61636a poll + 10
1   VBoxDD.dylib                  	0x000000011ff1a83b 0x11fde1000 + 1284155
2   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
3   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
4   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
5   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 28:: INTNET-RECV
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff1148 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	0x000000011fe52638 0x11fde1000 + 464440
5   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
6   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 29:: INTNET-XMIT
0   libsystem_kernel.dylib        	0x00007fff5a60eb56 __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff5a60eb40 ioctl + 151
2   VBoxRT.dylib                  	0x000000010dff88ed 0x10de4b000 + 1759469
3   VBoxRT.dylib                  	0x000000010dff56f7 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x000000011fe53400 0x11fde1000 + 467968
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 30:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x00000001121b6dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x00000001121b72ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x00000001182747b8 0x118269000 + 47032
5   VBoxXPCOM.dylib               	0x000000011218b1f9 0x112127000 + 410105
6   VBoxXPCOM.dylib               	0x00000001121b8a96 0x112127000 + 596630
7   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
8   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
9   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 31:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x000000010dfeb661 0x10de4b000 + 1705569
3   VBoxRT.dylib                  	0x000000010dfeb3e3 0x10de4b000 + 1704931
4   VBoxDD.dylib                  	0x000000011fea1f22 0x11fde1000 + 790306
5   VBoxVMM.dylib                 	0x0000000111e0e493 0x111da1000 + 447635
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 32:: CAQUEUE
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   VBoxDD.dylib                  	0x000000011ff17fb5 0x11fde1000 + 1273781
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 33:: AQConverterThread
0   libsystem_kernel.dylib        	0x00007fff5a611866 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5a6d056e _pthread_cond_wait + 722
2   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce821ca CAGuard::Wait() + 72
3   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce7e575 AQConverterManager::AQConverterThread::Run() + 375
4   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce7e3f3 AQConverterManager::AQConverterThread::ConverterThreadEntry(void*) + 9
5   com.apple.audio.toolbox.AudioToolbox	0x00007fff2ce5b741 CAPThread::Entry(CAPThread*) + 77
6   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 34:: CAQUEUE
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2e55b882 __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2e55adf0 __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2e55a552 CFRunLoopRunSpecific + 455
5   VBoxDD.dylib                  	0x000000011ff17fb5 0x11fde1000 + 1273781
6   VBoxRT.dylib                  	0x000000010df349cc 0x10de4b000 + 956876
7   VBoxRT.dylib                  	0x000000010dfee9b2 0x10de4b000 + 1718706
8   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 35:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 36:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 37:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 38:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 39:
0   libsystem_kernel.dylib        	0x00007fff5a60e26e semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff5a48cc99 _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff5a48d377 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff5a49a1fd _dispatch_worker_thread + 317
4   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 40:: com.apple.audio.IOThread.client
0   libsystem_kernel.dylib        	0x00007fff5a60e21a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5a60e768 mach_msg + 60
2   com.apple.audio.CoreAudio     	0x00007fff2dfcaeda HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 122
3   com.apple.audio.CoreAudio     	0x00007fff2dfcae4f HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 45
4   com.apple.audio.CoreAudio     	0x00007fff2dfc739f HALC_ProxyIOContext::IOWorkLoop() + 1017
5   com.apple.audio.CoreAudio     	0x00007fff2dfc6df4 HALC_ProxyIOContext::IOThreadEntry(void*) + 122
6   com.apple.audio.CoreAudio     	0x00007fff2dfc6956 HALB_IOThread::Entry(void*) + 72
7   libsystem_pthread.dylib       	0x00007fff5a6cd2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5a6d0249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5a6cc40d thread_start + 13

Thread 41:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 42:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 43:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 44:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 45:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 46:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 47:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 48:
0   libsystem_pthread.dylib       	0x00007fff5a6cc3f0 start_wqthread + 0

Thread 8 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x000070000d07f000  rcx: 0x000070000d07b6f8  rdx: 0x0000000000000000
  rdi: 0x000000000000b707  rsi: 0x0000000000000006  rbp: 0x000070000d07b730  rsp: 0x000070000d07b6f8
   r8: 0x0000000000000000   r9: 0x000070000d07b650  r10: 0x0000000000000000  r11: 0x0000000000000206
  r12: 0x000000000000b707  r13: 0x0000000115b29000  r14: 0x0000000000000006  r15: 0x000000000000002d
  rip: 0x00007fff5a6142c2  rfl: 0x0000000000000206  cr2: 0x00007ffecbc7f570
  
Logical CPU:     0
Error Code:      0x02000036
Trap Number:     133


Binary Images:
       0x10de02000 -        0x10de23ff7 +org.virtualbox.app.VirtualBoxVM (6.1.10 - 6.1.10) <E16212EC-8D76-3B0C-814C-7BFCC94C0A11> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10de4b000 -        0x10e3a151f +VBoxRT.dylib (0) <62894218-58E3-3537-8ED0-A5D0BAA9580E> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x10e4c7000 -        0x10e4d0ff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x10e4dc000 -        0x10e510fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10e537000 -        0x10e576fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x10e5fa000 -        0x10e66470f  dyld (655.1.1) <91A01B2E-622F-3FBC-8D67-AC6D5D1C0023> /usr/lib/dyld
       0x10e6c5000 -        0x10e7e8fff +VirtualBoxVM.dylib (0) <D8B020D2-66AF-3BBC-88E1-E4DBB2812AD9> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x10e851000 -        0x10ed78ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10ee3c000 -        0x10f317ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10f418000 -        0x10f921fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x10fa93000 -        0x10fae8ff7 +VBoxDDU.dylib (0) <936C11CF-0353-3300-AA7B-3A5DC55F5D0A> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x10faf8000 -        0x111b9ffff +UICommon.dylib (0) <1C0A76C2-1EAE-33E9-81AA-9A2DD1A3FE73> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x111da1000 -        0x1120a6fff +VBoxVMM.dylib (0) <84DD54C0-07CC-39A1-AF76-DEF4D6AE9771> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x112127000 -        0x1121d8ff7 +VBoxXPCOM.dylib (0) <F1D3A14D-4D3A-3FB0-823E-4E2798EF4CEF> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x1157e6000 -        0x115925fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x11791a000 -        0x117923ff7 +VBoxSharedClipboard.dylib (0) <83275893-F5C7-34FE-94FB-DBBFC51DFA78> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedClipboard.dylib
       0x11792b000 -        0x117932fff +VBoxDragAndDropSvc.dylib (0) <0A99CD2D-48E3-3D18-8484-A8DF8929E939> /Applications/VirtualBox.app/Contents/MacOS/VBoxDragAndDropSvc.dylib
       0x117958000 -        0x11795b047  libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib
       0x118269000 -        0x118280fff +VBoxXPCOMIPCC.dylib (0) <4EC687AC-51DB-3E34-BD49-3AAE70D51BA5> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x118291000 -        0x11868eff7 +VBoxC.dylib (0) <81E94F5F-830A-3D42-B77A-A9970A794448> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x1186dd000 -        0x1186e0ff7 +VBoxSVCM.dylib (0) <BF1D7EBF-3313-3963-A66A-C5A4D3FF9453> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x11989b000 -        0x1198a3ff7  com.apple.iokit.IOUSBLib (900.4.2 - 900.4.2) <A4432BC7-3694-3666-A3B2-B338CDB5A5B6> /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Contents/MacOS/IOUSBLib
       0x119975000 -        0x119982fff  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <E77B604A-8C73-382E-AC8A-62E9ADE73E9D> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x119ea9000 -        0x119eb6ff7 +VBoxSharedFolders.dylib (0) <919BF239-5930-3A63-9E8F-603AE9394A6C> /Applications/VirtualBox.app/Contents/MacOS/VBoxSharedFolders.dylib
       0x119ec0000 -        0x119ec5ff7 +VBoxGuestControlSvc.dylib (0) <BEEAA3B8-91CB-3B2E-A597-70D43A8CC8DF> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestControlSvc.dylib
       0x11fde1000 -        0x120143fff +VBoxDD.dylib (0) <EEB6BA71-4040-30C1-825F-FB907F5900A7> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x1207e0000 -        0x120837ff7 +VBoxDD2.dylib (0) <481FD166-F49E-3A8D-B4C1-703F21AA6C95> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x12208d000 -        0x122094fff +VBoxGuestPropSvc.dylib (0) <3E171A9E-4125-3C1A-AECE-B47ABD39EAF3> /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestPropSvc.dylib
       0x20d1cd000 -        0x20d362fff  com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff22c82000 -     0x7fff22fdbfff  com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff22fde000 -     0x7fff230eafff  com.apple.AMDMTLBronzeDriver (2.11.22 - 2.1.1) <E84F9A71-99A7-3879-A943-0B39816B7649> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
    0x7fff27ac5000 -     0x7fff27df5ff7  com.apple.driver.AppleIntelKBLGraphicsMTLDriver (12.10.22 - 12.1.0) <9F5D7B3C-027F-3E8D-A808-F212DDA36314> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver
    0x7fff2a553000 -     0x7fff2a557fff  com.apple.agl (3.3.2 - AGL-3.3.2) <A5954DED-265B-395D-B907-3CEC000B10B6> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff2a902000 -     0x7fff2a902fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff2a903000 -     0x7fff2a919ff7  libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff2a91a000 -     0x7fff2afb3fef  com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff2afb4000 -     0x7fff2b22dff3  libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff2b22e000 -     0x7fff2b2a0ffb  libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff2b2a1000 -     0x7fff2b64aff3  libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff2b64b000 -     0x7fff2b660feb  libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff2b661000 -     0x7fff2b666ff3  libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff2b667000 -     0x7fff2b6e3ff3  libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff2b6e4000 -     0x7fff2b6f7fe3  libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff2b6f8000 -     0x7fff2b8dfff7  libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff2b8e0000 -     0x7fff2b993ff7  libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff2b994000 -     0x7fff2b994fff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff2bb36000 -     0x7fff2c8ebffb  com.apple.AppKit (6.9 - 1671.60.109) <942F1512-A819-347B-90B4-075F2367950C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff2c93d000 -     0x7fff2c93dfff  com.apple.ApplicationServices (50.1 - 50.1) <FBE56E8E-9B8A-3B04-A0C6-20CBA0E6CED6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff2c93e000 -     0x7fff2c9a9fff  com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff2ca42000 -     0x7fff2cb59ff7  libFontParser.dylib (228.6.2.5) <CEDF1D5A-8897-3621-A1DC-558301F8BE05> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff2cb5a000 -     0x7fff2cb9cfff  libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff2cbf6000 -     0x7fff2cc28fff  libTrueTypeScaler.dylib (228.6.2.5) <E17ABF05-EC1E-3042-BBE2-C2E2909D3875> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
    0x7fff2cc8d000 -     0x7fff2cc91ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff2cd2c000 -     0x7fff2cd7eff7  com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff2cd7f000 -     0x7fff2cd8efff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff2cd8f000 -     0x7fff2cdd8ff7  com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff2cdd9000 -     0x7fff2ce12ff7  com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff2ce13000 -     0x7fff2ce1ffff  com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff2ce20000 -     0x7fff2d097fff  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff2d099000 -     0x7fff2d099fff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff2d3f2000 -     0x7fff2d794fff  com.apple.CFNetwork (978.4 - 978.4) <2D4EEB80-0C17-34E0-B2B5-E24308CF9359> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff2d7a9000 -     0x7fff2d7a9fff  com.apple.Carbon (158 - 158) <BE5FB24D-510F-3AE6-A455-79BFDEB99AEC> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff2d7aa000 -     0x7fff2d7adffb  com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff2d7ae000 -     0x7fff2daa5fff  com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff2daa6000 -     0x7fff2daa9ff3  com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff2daaa000 -     0x7fff2daafff7  com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff2dab0000 -     0x7fff2db45ff3  com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff2db46000 -     0x7fff2db5eff7  com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff2db7e000 -     0x7fff2db7fff7  com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff2db80000 -     0x7fff2db82ff7  com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff2db83000 -     0x7fff2db89ff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff2dcab000 -     0x7fff2dcabfff  com.apple.Cocoa (6.11 - 23) <F6FA8C4A-40B6-30CB-ABD2-FDD165F3ECC4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff2dcb9000 -     0x7fff2de08ff7  com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff2df94000 -     0x7fff2e01afff  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <1E8E64E6-0E58-375A-97F7-07CB4EE181AC> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff2e07e000 -     0x7fff2e0a8ffb  com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff2e0a9000 -     0x7fff2e42efef  com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff2e42f000 -     0x7fff2e51fff7  com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff2e520000 -     0x7fff2e965fff  com.apple.CoreFoundation (6.9 - 1575.300) <2ABD4A7D-6C28-3594-8584-4D7445911EAA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff2e967000 -     0x7fff2eff7fe7  com.apple.CoreGraphics (2.0 - 1265.11) <B433DE85-643A-3A48-AE01-2BE1F4E888D1> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff2eff9000 -     0x7fff2f319fff  com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff2f616000 -     0x7fff2f71afff  com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff2f777000 -     0x7fff2f777fff  com.apple.CoreServices (946 - 946) <FA85ED71-4375-319B-BDC8-AD6231653280> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff2f778000 -     0x7fff2f7f4ff7  com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff2f7f5000 -     0x7fff2faccfff  com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff2facd000 -     0x7fff2fb15ff7  com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff2fb16000 -     0x7fff2fb1effb  com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff2fb1f000 -     0x7fff2fcd0ff7  com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff2fcd1000 -     0x7fff2fd6fff7  com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff2fd70000 -     0x7fff2fdbaff7  com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff2fdbb000 -     0x7fff2fe22ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff2fe23000 -     0x7fff2fe44ff3  com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff3014f000 -     0x7fff302b1ff3  com.apple.CoreText (352.0 - 584.26.3.4) <7247EA49-9F90-3258-AABF-932C6343BD6A> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff302b2000 -     0x7fff302f2ff3  com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff302f3000 -     0x7fff30382fff  com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff305d9000 -     0x7fff305deffb  com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff307a5000 -     0x7fff30b52ffb  com.apple.Foundation (6.9 - 1575.300) <CA3584DA-A8AF-3931-9B53-3B1EA240575C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff30bc1000 -     0x7fff30bf0ffb  com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff30cf0000 -     0x7fff30dfafff  com.apple.Bluetooth (6.0.14 - 6.0.14d11) <C2CE7A31-E7A1-3058-AA32-F80297C04FFC> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff30e5d000 -     0x7fff30eecfff  com.apple.framework.IOKit (2.0.2 - 1483.260.4) <8A90F547-86EF-3DFB-92FE-0E2C0376DD84> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff30eee000 -     0x7fff30efdffb  com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff30f51000 -     0x7fff310ddfef  com.apple.ImageIO.framework (3.3.0 - 1850.2.7) <9C059297-033F-3441-BDC1-46CC1139DBCB> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff310de000 -     0x7fff310e2ffb  libGIF.dylib (1850.2.7) <1F60E131-3255-324F-A73D-87B8B66A51F9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff310e3000 -     0x7fff311bffe7  libJP2.dylib (1850.2.7) <209FEE0C-319C-3B13-90BF-D36C9A8D621C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff311c0000 -     0x7fff311e5feb  libJPEG.dylib (1850.2.7) <AB1D6EDF-FB59-34F9-81D4-ED01B965BD1B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff314bb000 -     0x7fff314e1feb  libPng.dylib (1850.2.7) <85AFD5DD-D842-3F6C-A6D6-147A283B97EE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff314e2000 -     0x7fff314e4ffb  libRadiance.dylib (1850.2.7) <3C77681E-A94B-314B-BD85-95067016E204> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff314e5000 -     0x7fff31532fff  libTIFF.dylib (1850.2.7) <7D9DC37B-7855-3344-A12C-DFF588B78BDA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff326a5000 -     0x7fff326befff  com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff32978000 -     0x7fff32982fff  com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff32a32000 -     0x7fff330d8fff  com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff330da000 -     0x7fff33182ff7  com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3319e000 -     0x7fff331bdff7  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff331be000 -     0x7fff3323afe7  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3323b000 -     0x7fff33262fff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff33263000 -     0x7fff3338eff7  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff3338f000 -     0x7fff333a9fff  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff333aa000 -     0x7fff333abff7  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff341a4000 -     0x7fff341b0ff7  com.apple.NetFS (6.0 - 4.0) <E917806F-0607-3292-B2D6-A15404D61B99> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff36c4e000 -     0x7fff36ca5ff7  com.apple.opencl (2.15.3 - 2.15.3) <3F72F3B0-F607-39E5-BDF6-5C37C9B67430> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff36ca6000 -     0x7fff36cc1ff7  com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff36cc2000 -     0x7fff36ccdffb  com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff3761d000 -     0x7fff3761ffff  libCVMSPluginSupport.dylib (17.7.3) <83C36A70-5F35-37D1-A124-A2CD497F1915> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff37620000 -     0x7fff37625ff3  libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff37626000 -     0x7fff3762afff  libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff3762b000 -     0x7fff37633ff7  libGFXShared.dylib (17.7.3) <09F50639-F0CB-3312-8BAC-5AA8083350F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff37634000 -     0x7fff3763ffff  libGL.dylib (17.7.3) <4EEC82D4-A3C6-336D-9F90-67F1D24ED35B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff37640000 -     0x7fff3767afef  libGLImage.dylib (17.7.3) <B175F261-69D1-3366-A009-DF75CB32E2F9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff377ee000 -     0x7fff3782cfff  libGLU.dylib (17.7.3) <5BB2F84A-4D96-35A1-8A5B-99AE39CD9E59> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff381c9000 -     0x7fff381d8ffb  com.apple.opengl (17.7.3 - 17.7.3) <9C1FCE6E-FED6-3A09-9FDC-4C81F8CDB2A6> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff38fe2000 -     0x7fff39239ff7  com.apple.QuartzCore (1.11 - 701.14) <1E82D0E6-EB06-3CC6-AEB5-06E3365887D0> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff39a6f000 -     0x7fff39d6fff7  com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff39d70000 -     0x7fff39dfcfff  com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff39e2e000 -     0x7fff39e32fff  com.apple.xpc.ServiceManagement (1.0 - 1) <B0B6F84E-2892-346B-A7D3-BAEE726DA4BF> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff3a1cb000 -     0x7fff3a238fff  com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff3a497000 -     0x7fff3a7f8fff  com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff3d474000 -     0x7fff3d519fff  com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff3df2e000 -     0x7fff3df2fff7  com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff3e530000 -     0x7fff3e55cff7  com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff3e684000 -     0x7fff3e693fc7  com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff3e78f000 -     0x7fff3e79afff  com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff3e7db000 -     0x7fff3e824ff3  com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
  ",wesinator
19754,Cannot use VM due to Guru Meditation Error,Windows,Linux,VirtualBox 6.1.10,2020-07-24T07:48:08Z,2020-07-24T07:48:08Z,"when starting a VM it asks me to choose from four options: ubuntu, advances options for ubuntu and two memtests. In the logs the error shows as "" VCPU0: Guru Meditation -1149 (VERR_EM_INTERNAL_ERROR)"".
updated the version from 6.1.10 to 6.1.12 but the problem remains 

after creating new VMs also has the same error

",virgo
19763,Calculation of required video memory for VBoxSVGA / VMSVGA,all,all,VirtualBox 6.1.10,2020-07-25T09:04:56Z,2020-07-25T09:04:56Z,"VirtualBox calculates the required video memory in UICommon::requiredVideoMemory(). Basically, it calculates memory for 1 surface for Linux guests, and for 2 or 3 surfaces for Windows guests (plus some extra). Is this calculation still correct for the new graphics controllers (VBoxSVGA, VMSVGA)?

I'm asking because a forum user seemed to have problems with a Linux guest switching to 1920x1080 and the VirtualBox default of 16 MB VRAM would IMHO be enough memory, if the factor of 1 was still valid (~ 9 MB). Because this was one of multiple cases in the previous years, it made me wonder if the calculation is still correct. ",fth0
19770,impossible to start restored machine,other,other,VirtualBox 6.1.10,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
19771,Windows 7 Guest Goes BSOD upon rebooting after install of Guest Additions for 6.1.12,Windows,Windows,VirtualBox 6.1.10,2020-07-27T04:46:05Z,2020-07-27T04:46:05Z,"Windows 7 Client runs fine under version 6.1.10,  I performed the upgrade to 6.1.12.  After rebooting I installed the guest additions and rebooted as requested.  I could no longer successfully reboot.  I could reboot into safe mode only.  I kept getting the BSOD message.  I rolled back to version 6.1.10 and everything is working again.",Yogi2
19773,Cannot see Host Only Adapter in Windows 10 adapters,Windows,Linux,VirtualBox 6.1.10,2020-07-28T08:51:40Z,2020-07-28T08:51:40Z,"After some wailing and gnashing of teeth, I got host only networking to work with Uvuntu 20.04. I was expecting to see the adapter in the Control Panel\Network and Internet\Network Connections but it doesn't show up. It does appear in the Device Manager.
",d0325mgray
19774,RDP connection fails with error code 0xd06 with MS Android client,Mac OS X,Linux,VirtualBox 6.1.10,2020-07-28T10:43:58Z,2020-07-28T10:43:58Z,"I'm trying to connect to my VMs via RDP.

I use the MS Remote Desktop Android client (https://play.google.com/store/apps/details?id=com.microsoft.rdc.androidx).

The connection fails with error code 0xd06.

Don't know if it's related or not, xRDP server is already fixed by using painter by default, see https://github.com/neutrinolabs/xrdp/issues/246

",Peter Meiser
19757,Referenced memory at 0x000000... yadayadayada,other,other,VirtualBox 6.1.10,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
19776,Linux Mint 20 Vir Box 6.1 cant turn off Hardware Virtualization,other,other,VirtualBox 6.1.10,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
19764,paravirtualized adapter doesn't receive packets until a ping6 of the gateway,Mac OS X,BSD,VirtualBox 6.1.10,2020-07-28T20:00:10Z,2020-07-28T20:00:10Z,"OpenBSD 6.7 guest on macOS Catalina, where the guest is configured for IPv6-only and a paravirtualized network bridged adapter. After booting the OpenBSD guest, and obtaining the IPv6 address by autoconfiguration, the Internet seems unreachable. Simultaneous packet captures on the guest and the host show, for example, a DNS request egress the guest and the host, and the DNS response ingress the macOS host but not the OpenBSD guest. A workaround is to ping6 the IPv6 gateway public address, then suddenly packets for the guest will start showing up in the guest packet capture.

However, the ping6 also inserts the neighbor entry for the IPv6 gateway public address. Otherwise, because of autoconfiguration, the Internet6 default route is the IPv6 gateway link-local address and there is only the gateway's link-local address in the neighbor mapping table.",jasonmader
19775,Bluetooth device failed to pass through VM - MacOS,Mac OS X,all,VirtualBox 6.1.10,2020-07-29T22:10:39Z,2020-07-29T22:10:39Z,"When I want to use my internal bluetooth in the VM, VBox reports that it failed to attach. However, in VBoxManage, it reports that the device is available. I have requested help in the [https://forums.virtualbox.org/viewtopic.php?f=8&t=99203 Forum], but the issue was not solved. Also, when attempting to connect the device, this error shows in the console (but not the logs):

{{{
014435.208921 VBoxSVC@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.bluetooth.control
}}}

Steps Taken:
1. Start VBox
2. Launch VM.
3. Try to connect to Bluetooth on the fly.

or 
1. Start VBox
2. Set USB filter.
3. Launch VM.
",JP3
19710,Problem to start VM Virtual Box,other,other,VirtualBox 6.1.10,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
19780,Issue with guest additions on Windows 10 vm,Linux,Windows,VirtualBox 6.1.10,2020-07-30T09:45:15Z,2020-07-30T09:45:15Z,"I got an issue with full screen (impossible to get) and with the graphics, almost impossible to use like that, transparent window, strange layout, window who doesnt appear, everything is up to date (windows iso, vb, guest additions, extention vb)",toolhelp
19781,DMI Handle is not unique,Windows,Linux,VirtualBox 6.1.8,2020-07-30T13:42:09Z,2020-07-30T13:42:09Z,"I have been having issues with the DMI on VirtualBox.

When I run dmidecode on Ubuntu 18.04, there are 2 entries for Handle 0x0008.
When python's py-dmidecode runs, it loops through the DMI and the contents of the second entry for Handle 0x0008 replace the previous entry, causing it's output to be invalid.

I think the Handle entries should be unique.

I have attached a copy of my dmi output with the above issue (0x0008 listed twice).",MattRobinson
19753,Guest Additions 6.1.12 don't support screen autosizing anymore on Windows 7 guests,Windows,Windows,,2020-07-30T19:13:09Z,2020-07-30T19:13:09Z,"After upgrading VirtualBox to version 6.1.12, I upgraded '''Guest Additions''' (GA) on my virtual machines (VMs), all Windows 10 guests except one, which is Windows 7. I use screen autosizing to get full-screen display on all my VMs.

The upgrade worked properly for all Windows 10 VMs. However, after upgrading GA to version 6.1.12 on the Windows 7 guest, I ran into repeated blue screens. After changing the graphics driver to VBoxSVGA, I could properly start the VM again, but I couldn't get the screen to autosize anymore.

Actually, the behaviour I observed looks like GA are not working at all anymore on Windows 7 guests.

The only way I could get back this feature (and GA to work properly) was to rollback GA to version 6.1.10.

Bottom line: This looks like a '''compatibility issue between Guest Additions 6.1.12 and Windows 7 hosts'''.",jfmorin
19783,Guest Windows Desktop load fails if Guest Additions Direct3D installed,Linux,Windows,VirtualBox 6.1.10,2020-07-30T20:59:28Z,2020-07-30T20:59:28Z,"Host: Ubuntu 18.04 kernel 4.15.0-112
VBox: 6.1.12
Guests:
(a) Windows Server 2008 64bit
(b) Windows Vista 64bit
(c) Windows Vista 32bit

Problem:
When, during the install of the VBox Guest Additions 6.1.12, the Direct3D support is selected (default=selected), on the subsequent reboot, after the user credentials have been entered and the login succeeds, the desktop fails to load. The VM either performs a reset after a few seconds (a) or hangs indefinitely ((b) and (c)).

The problem is reproducible.

The problem disappears when the Direct3D support is disabled during installation of the VBox Guest Additions.

The problem does NOT show with a Windows Server 2008 32bit version.

The problem is independent of the setting of the 3D Acceleration in the VM Display Settings.


[P.S.: The 'Create New Ticket' webpage does not allow the selection of 'VirtualBox 6.1.12' in the Version dropdown selector. 6.1.12 is not present there. So I chose 6.1.10.]",sunrider
19784,Win10 Quick Assist screen-share shows corrupted desktop,other,other,VirtualBox 6.1.4,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
19761,VirtualBox guest OpenWrt OS crashed when using the nmap to scan the wireless network through the USB port,Windows,Linux,VirtualBox 6.1.10,2020-07-31T02:05:45Z,2020-07-31T02:05:45Z,"Guest OpenWrt OS crashed with the following configuration and operation
Host is the Lenovo ThinkCentre M920t desktop PC, WIN 10 professional OS.
The VirtualBox v6.1.12 with extension pack 6.1.12 is installed. 
The Guest OS is Linux 64bit(OpenWrt Lede 17.01). Using the MediaTek USB wifi dongle MT7601U to act as a AP(AccessPoint). It works well, I can connct it by my mobile phone and surf the Internet without problem, but it will be crashed once I use the nmap(v7.31) to scan the wifi network. I have the exactly same configuration with my HP laptop and the sympton won't happen in it, don't why it's crashed with my Lenovo desktop PC.",MercyLin
19785,machine is restarted but with the last working snapshoot,Mac OS X,Windows,VirtualBox 5.2.42,2020-07-31T06:00:51Z,2020-07-31T06:00:51Z,"Gent.mi,

ho avuto un problema con una macchina virtuale Windows 7 64bit con host Imac, in pratica ha smesso di funzionare non si avviava più l'errore riportava alla disabilitazione della scheda di rete.

Al riavvio la macchina è ripartita ma con l'ultimo snapshoot funzionante del 2016, ho perso 4 anni di lavoro sul desktop, c'è un modo per recuperare i dati.

In attesa di un vostro cortese riscontro saluto cordialmente.

Federico Ales

----------------

Hi

I have a problem with a Windows 7 64bit virtual machine with Imac host, in practice it stopped working it did not start anymore the error reported disabling the network card.

At restart the machine is restarted but with the last working snapshoot of 2016, I lost 4 years of work on the desktop, there is a way to recover the data.

Looking forward to your kind reply.

Best Regards

Federico Ales ",Fred74
19786,VMs won't run after testbuild 6.1.13-139554: driver version mismatch kernel 5.7.12,Linux,Windows,VirtualBox 6.1.10,2020-08-02T21:13:49Z,2020-08-02T21:13:49Z,"All  builds from VB 6.1.12 through  test builds until 139554 work fine.  After 139554 VB test builds compile but VMs crash on startup with a kernel module message, give SVC log errors (no errs in the vmlogs).

Both 139683 and 139683 give the same errors.


VBoxSVC.log

00:00:05.638966 nspr-4   Support driver version mismatch: DriverVersion=0x2d0001 ClientVersion=0x2e0000 rc=VERR_VERSION_MISMATCH
00:00:06.113750 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'win7dpg' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0


I've tried removing and reinstalling the host modules,  building the VirtualBox...run, unloading and reloading the modules to no avail.

Not a big deal for me, but maybe important for developers to know (if not, my apologies).

Host: manjaro Linux updated daily, kernel 5.7.12 linux57-virtualbox-host-modules 6.1.12-4",matthewls
19787,Virtual Machine goes into error after few days,Windows,Windows,VirtualBox 6.1.10,2020-08-03T11:25:34Z,2020-08-03T11:25:34Z,"Hi,
I am using Virtual Box 6.1.12 on Windows 10 as a host. I am facing a issue of error on my VB which is attached. This is happening after few days and to overcome this I have to uninstall it, delete the .exe file from PC and then restart the PC and download again the new Vbox from Website. I don't know what to call this error. I have attached couple of pics and the Log.
Can anyone help me in this ti resolve the issue. By the way, it doesn't matter which version of Vbox I have installed. This error occurs after few days 

Thanks
Manoj",Montu
19664,Guest Additions prevent Lubuntu desktop from starting,Linux,Linux,VirtualBox 6.1.10,2020-08-04T10:21:05Z,2020-08-04T10:21:05Z,"The guest is a 32 bit Lubuntu 18.04 Linux machine. The host is a 64 bit Ubuntu 18.04 Linux machine.

The guest works great as long as I do not install Guest Additions. After installing Guest Additions, I get the login / greeter screen, but after logging in, the desktop does not start.

To test this, I created the virtual machine and restarted it many times, logging in successfully. After one of these logins, I took a snapshot and installed Guest Additions. After that and a restart, the desktop did not start.

To confirm that the snapshot was not the problem, I restored the snapshot and did not install Guest Additions. I was able to restart and have the desktop start.

I would be happy to provide additional information but I do not know what would be helpful.",Organic_Marble
19790,virtual machine startup error (0x80004005),Windows,other,VirtualBox 5.2.40,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
19794,Windows 10 Blue Screen when USB device is disconectec runnning only VBox application,all,Windows,VirtualBox 6.1.10,2020-08-05T15:21:34Z,2020-08-05T15:21:34Z,"Hi all,

The issue happens all the time, the only that you need is open virtualbox, is not necessary to run a guest virtual machine:

Open Virtual box
Disconnect a USB keyboard or Mouse (some times blue screen come here), if not,
Connect a USB keyboard or Mouse, here comes the blue screen.

If you open the VirtualBox application and close and disconnect and connect a USB Keyboard or mouse, the doesn't happens.

I'm ussing the VirtualBox 6.1.12-139181, I uninstall and install 6.1.0-135406 and the issue is there, also on 6.1.10-138449",Andres Marin
19796,Server 2019 Virtualbox host - Guest with any type of GUI causing Windows RDP to crash forcing reboot,Windows,all,VirtualBox 6.1.10,2020-08-06T01:23:16Z,2020-08-06T01:23:16Z,"When RDP'ing to a server 2019 Host with virtualbox installed, attempting to run a guest with a GUI (EG: Ubuntu Desktop, Windows 7 /10) causes RDP to crash and unable to reconnect. Appears to take down whole server as unable to connect to other services either. 

Have been unable to find any details of crash in windows event log. 

Last crash occurred when trying to run windows7 installer ISO. ",ranvens
19797,installed virtualbox 6.1.12 on centos 7 but vboxweb-service is not started,Linux,Linux,VirtualBox 6.1.10,2020-08-06T11:52:45Z,2020-08-06T11:52:45Z,"installed virtualbox 6.1.12 but vboxweb-service is not started.
i tried to start ------>
systemctl start vboxweb-service

""Job for vboxweb-service.service failed because the control process exited with error code. See ""systemctl status vboxweb-service.service"" and ""journalctl -xe"" for details.""

systemctl status vboxweb-service -l
● vboxweb-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-08-06 17:19:28 IST; 1min 17s ago
  Process: 5801 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=1/FAILURE)

Aug 06 17:19:28 localhost.localdomain systemd[1]: Starting vboxweb-service.service...
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 06 17:19:28 localhost.localdomain su[5807]: (to admin) root on none
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: failed: VirtualBox web service failed to start.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service: control process exited, code=exited status=1
Aug 06 17:19:28 localhost.localdomain systemd[1]: Failed to start vboxweb-service.service.
Aug 06 17:19:28 localhost.localdomain systemd[1]: Unit vboxweb-service.service entered failed state.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service failed.",pmssy
19798,Can't load my document,other,other,VirtualBox 6.1.10,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
19799,Incorrect DHCP lease command output,Windows,Linux,VirtualBox 6.1.10,2020-08-07T07:18:51Z,2020-08-07T07:18:51Z,"VirtualBox 6.1.12r139181

Please, take a look at leases file fragment below:

{{{#!xml
<?xml version=""1.0""?>
<Leases version=""1.0"">
  <Lease mac=""08:00:27:6a:51:e9"" id=""010800276a51e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.254""/>
    <Time issued=""1596783415"" expiration=""600""/>
  </Lease>
  <Lease mac=""08:00:27:6a:51:e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.252""/>
    <Time issued=""1596783702"" expiration=""600""/>
  </Lease>
}}}

Command output:

{{{#!python
C:\Users\User>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       acked
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 10 sec left
}}}

Should return the latest lease, not the first one I assume.

And it didn't return the correct lease even when first one expired:

{{{#!python
C:\Users\user>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       expired
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 0 sec left
}}}

Expected behaviour: return the last lease for MAC address.",imort
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,other,VirtualBox 6.1.10,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
19803,Add support for SATA attached read-only (RO/RDONLY) vmdk disks,all,all,,2020-08-09T12:03:10Z,2020-08-09T12:03:10Z,"Currently you cannot attach a full raw real harddisk with the RDONLY (read-only) flag set as the VM execution runs into an error:


'''The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_INVALID_HANDLE). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.'''

{{{
Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error

[Copy] [OK]
}}}

Pressing OK doesn't allow to continue the execution.

Please fix.

Here's an example VMDK image:

{{{
# Disk DescriptorFile
version=1
CID=abcdedfg
parentCID=ffffffff
createType=""fullDevice""

# Extent description
RDONLY 800000000 FLAT ""/dev/sda"" 0

# The disk Data Base
#DDB

ddb.virtualHWVersion = ""4""
ddb.adapterType=""ide""
ddb.geometry.cylinders=""16383""
ddb.geometry.heads=""16""
ddb.geometry.sectors=""63""
ddb.uuid.image=""xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx""
ddb.uuid.parent=""00000000-0000-0000-0000-000000000000""
ddb.uuid.modification=""xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx""
ddb.uuid.parentmodification=""00000000-0000-0000-0000-000000000000""
ddb.geometry.biosCylinders=""1024""
ddb.geometry.biosHeads=""255""
ddb.geometry.biosSectors=""63""
}}}",Artem S. Tashkinov
19805,VirtualBox Manager hijacks Linux desktop,Linux,all,VirtualBox 6.1.10,2020-08-10T11:55:23Z,2020-08-10T11:55:23Z,"If I remove or rename the virtual disk file of a virtual machine and then start VirtualBox Manager it goes into an endless loop redisplaying an error message box ""Failed to open the medium with the following ID: ...""

The message box redisplays itself in a loop and cannot be closed. Besides that it steals the desktop focus so it is impossible to do anything else. Cannot even kill the process or close down the host machine in a proper way! Have to push power button to reboot!

It is OK to display the error message ONCE! It is unacceptable to hijack the desktop!

VirtualBox 6.1.12
Ubuntu 18.04 host
Guest is Windows 10 but it probably does not matter(?).
",ele
19370,On power off error at line 580 in VBoxManageControlVM.cpp in 6.0.18,Mac OS X,Linux,VirtualBox 6.0.18,2020-08-10T12:19:29Z,2020-08-10T12:19:29Z,"I have automatic test system based on VirtualBox, which in infinite loop test VMs, for instance for power off. And now I see some rare error when power off VM. The error may be rare, but in the night run I got it twice. Looked like error at line 580 in VBoxManageControlVM.cpp. I didn't saw such error in 6.0.16. Screenshots are attached.",Olleg
19806,[Guest OS windows 7] VirtualboxVM process memory increases while launch app in guest OS,Linux,Windows,VirtualBox 6.1.10,2020-08-11T06:39:55Z,2020-08-11T06:39:55Z,"Host OS : ubuntu 20.04
VirtualBox: 6.1.12.r139181
Guest OS: windows 7 ultimate x64 7601
test app: mBlock

VM config: Memory 2G.

How to reproduce:
1. Use top to monitor memory usage.
2. Open VirtualBox, boot windows 7 guest os to desktop.
3. Install and launch app named mblock.exe.
4. While mblock launch completely. then close it.
5. Repeat launch mblock.exe and close scene several times.
6. Check memory status. ==> We find it increse to 3.3G, But i only allocate 2G.",ramboliu
19356,Copy and paste and drag and drop doesn't work,Windows,Linux,VirtualBox 6.1.4,2020-08-11T11:36:22Z,2020-08-11T11:36:22Z,"this was the error for Windows to Linux(Kali Linux):
Drag and drop operation from host to guest failed.
Drag and drop error from host (VERR_NET_PATH_NOT_FOUND).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

This error is Linux to Windows:
Specified format 'text/plain;charset=utf-8' is not supported.
Result Code: 
E_INVALIDARG (0x80070057)
Component: 
GuestDnDSourceWrap
Interface: 
IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: 
IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
",Coder2005
18985,Appdata folder contents copied to host drives when dragging and dropping files from kali linux vm,Windows,Linux,VirtualBox 6.0.12,2020-08-11T11:45:33Z,2020-08-11T11:45:33Z,"I have attached a video of the bug or whatsoever and managed to reproduce it like 3 times and as its mentioned in the summary it happened when i tried to drag and drop from vm to host, and after the copying started after calculating the files(110 GB the second time I tried), i cancelled copying and some files from appdata folder and the screenshots i wanted were copied to the host drive. thank you.",hasa
19034,Drag drop from guest to host leads to full AppData drop,Windows,Windows,VirtualBox 6.0.14,2020-08-11T11:46:00Z,2020-08-11T11:46:00Z,"Hi,

As said in title I'm facing a verry strange file drag/drop from VM to host.

Wherever I drag from (in term of folder), if the file is named ""006_remplissage_pieces_test_pause"" and whatever is the extension Virtualbox '''try to drop all the AppData folder content to my host.'''

Exactly the same if the file is named ""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" plus ANY extension.
Even in ""small path length"" conditions.
The same with 1 character removed. Works with 2 removed...

The same with 1, 2 or 3 characters added.

The ""uge drop file name length"" seems to be from 32 to 35 char, without ""."" and extension.

{{{

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   - 36 char / OK
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    - 35 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx     - 34 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx      - 33 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx       - 32 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx        - 31 char / OK
}}}


Host is Windows 7x64, latest updates[[BR]]
Guest is Windows 7x64, latest updates[[BR]]
Virtual box is 6.0.14 r133895[[BR]]
Guest additions are up to date (6.0.14).
",wkoenig_ngbe
19801,add redhat8_ks.cfg kickstart config to unattended templates,all,Linux,VirtualBox 6.1.10,2020-08-12T12:33:42Z,2020-08-12T12:33:42Z,"From: ""Timothy Tacker"" <>
To: vbox-dev@virtualbox.org
Subject: [vbox-dev] [PATCH] add redhat8_ks.cfg kickstart
Date: Tue, 21 Jul 2020 14:49:04 +0200

Due to changes in RHEL 8, the redhat67_ks.cfg Kickstart script included in the UnattendedTemplates directory does not work with CentOS 8. The patch below adds a Kickstart script for RHEL 8 and CentOS 8, and makes other changes to integrate the new script into VirtualBox. Following the pattern for redhat67_ks.cfg, the new script is named redhat8_ks.cfg. All comments in the new script are worded to mirror language and terms used in the RHEL 8 documentation; and all sections, commands, and options appear in the same order in both the new script and the documentation.

The install command has been deprecated in RHEL 8. In regard to the install command, the documentation states, ""Use its methods as separate commands.""
The cdrom command was retained and now serves to specify that installation should occur from the first optical drive. The install command was removed from the new script.

The auth command has been deprecated in RHEL 8. Passwords are shadowed by default with sha512. The following auth command was removed from the new script:
auth  --useshadow  --passalgo=sha512

The default SELinux policy is enforcing. The following selinux command was removed from the new script:
selinux --enforcing

The documentation states, ""Either the --vckeymap= or the --xlayouts= option must be used"" for the required keyboard command, suggesting an OR rather than an AND. Nonetheless, both --vckeymap=us and --xlayouts='us' are used
in the new script. Many examples of this usage can be found, and it does not appear to cause issues. The value ""us"" was specified to maintain consistency with the value that was specified in the redhat67_ks.cfg script.

In order to comply with the order demonstrated in the syntax shown in the documentation, the timezone command was changed as follows:
timezone@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@@VBOX_COND_END@@
@@VBOX_INSERT_TIME_ZONE_UX@@
timezone @@VBOX_INSERT_TIME_ZONE_UX@@@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@
@VBOX_COND_END@@

For the --plaintext option to the user command, the documentation states, ""If this option is present, the password argument is assumed to be in plain text""; but it does not explicitly indicate plaintext is the default. The --plaintext option was added to the user command as follows:
user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@
user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@ --plaintext

For the network command, DHCP is the bootproto method used by default. In addition, due to a change in how network devices are named in RHEL 8, eth0 is not a valid device name by default; but the link keyword can be used to specify the first interface with its link in the up state. The network command was changed as follows:
network  --bootproto=dhcp --device=eth0 --onboot=on
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@@
network --device=link --onboot=on  
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@
@

For the bootloader command, mbr is the default value for the location
option. The bootloader command was changed as follows:
bootloader --location=mbr --append=""nomodeset crashkernel=auto rhgb quiet""
bootloader --append=""nomodeset crashkernel=auto rhgb quiet""

The autopart command automatically creates partitions in accordance with Red Hat recommendations. The value plain for the type option specifies ""Regular partitions with no LVM."" The following two part commands were changed to the single autopart command on the third line immediately below:
part / --fstype ext4 --size 6000 --grow --asprimary
part swap --size 1024
autopart --type=plain

Without the elfutils-libelf-devel package installed, post install scripting failed to compile kernel modules for VirtualBox Guest Additions, resulting in their failure to install. The elfutils-libelf-devel package was added to the %packages section in order to resolve this issue.

Only the new Kickstart script has been tested, and it has only been tested with CentOS 8. OS and Guest Additions both install. Full testing with RHEL 8 should be completed prior to integration.

I'm licensing this patch under the MIT license. Please review. Feedback is welcome. Thanks!

Timothy Tacker
{{{
---
  src/VBox/Installer/Config.kmk                 |   1 +
  .../Main/UnattendedTemplates/Makefile.kmk     |   1 +
  .../Main/UnattendedTemplates/redhat8_ks.cfg   | 116 ++++++++++++++++++
  src/VBox/Main/include/UnattendedInstaller.h   |  11 ++
  4 files changed, 129 insertions(+)
  create mode 100644 src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg

diff --git a/src/VBox/Installer/Config.kmk b/src/VBox/Installer/Config.kmk
index 077d6af6..0cbcfe8d 100644
--- a/src/VBox/Installer/Config.kmk
+++ b/src/VBox/Installer/Config.kmk
@@ -66,6 +66,7 @@ ifdef VBOX_WITH_UNATTENDED
   rhel4_ks.cfg \
   rhel5_ks.cfg \
   redhat67_ks.cfg \
+ redhat8_ks.cfg \
   win_nt5_unattended.sif \
   win_nt6_unattended.xml \
         \
diff --git a/src/VBox/Main/UnattendedTemplates/Makefile.kmk
b/src/VBox/Main/UnattendedTemplates/Makefile.kmk
index c8baeaf5..cd15ffb4 100644
--- a/src/VBox/Main/UnattendedTemplates/Makefile.kmk
+++ b/src/VBox/Main/UnattendedTemplates/Makefile.kmk
@@ -32,6 +32,7 @@ ifdef VBOX_WITH_UNATTENDED
   rhel4_ks.cfg \
   rhel5_ks.cfg \
   redhat67_ks.cfg \
+ redhat8_ks.cfg \
   ol_ks.cfg \
   fedora_ks.cfg \
   suse_autoinstall.xml \
diff --git a/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
b/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
new file mode 100644
index 00000000..d37f8baa
--- /dev/null
+++ b/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
@@ -0,0 +1,116 @@
+#platform=x86, AMD64, or Intel EM64T
+#version=DEVEL
+
+
+## Installation program configuration and flow control commands:
+
+# Install from first optical drive.
+cdrom
+
+# Specify info as minimum log level on tty3 in Anaconda during
installation.
+logging --level=info
+
+# Attempt to eject bootable media and reboot after installation.
+reboot --eject
+
+# Perform installation in text mode.
+text
+
+
+## System configuration commands:
+
+# Do not configure iptables rules.
+firewall --disabled
+
+# Set available keyboard layouts for system.
+keyboard --vckeymap=us --xlayouts='us'
+
+# Set language to use during installation and default to use on installed
system.
+lang @@VBOX_INSERT_LOCALE@@
+
+# Set system root password using supplied plaintext.
+rootpw --plaintext @@VBOX_INSERT_ROOT_PASSWORD_SH@@
+
+# Set system time zone and indicate if hardware clock is UTC (Greenwich
Mean) time.
+timezone @@VBOX_INSERT_TIME_ZONE_UX@@@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@
@VBOX_COND_END@@
+
+# Create new user on system and set password using supplied plaintext.
+user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@ --plaintext
+
+
+## Network configuration commands:
+
+# Configure network device and activate in Anaconda installation
environment.
+#  Device specified in first network command activated automatically.
+#  DHCP method used by default.
+#  Device: Link keyword specifies first interface with link in up state.
+#  Onboot: Enable device at boot time.
+#  Hostname: Specify host name for installed system.
+network --device=link --onboot=on
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@@
+
+
+## Storage handling commands:
+
+# Specifify how boot loader installed.
+#  Location boot record written dependent on drive usage of MBR or GPT
scheme.
+#  Append: Specifies additional kernel parameters.
+bootloader --append=""nomodeset crashkernel=auto rhgb quiet""
+
+# Remove partitions from system prior to creation of new partitions.
+#  All: Erase all partitions on disks reachable by installation program,
including attached network storage.
+#  Initlabel: Initialize disk(s) by creating default labels in respective
architectures designated for formatting.
+clearpart --all --initlabel
+
+# Automatically create partitions.
+#  Type: Plain keyword specifies regular partitioning scheme with no LVM.
+#  Default file system is xfs.
+autopart --type=plain
+
+# Initialize invalid partition tables and destroy contents of disks with
invalid partition tables.
+zerombr
+
+
+# Packages.  We currently ignore missing packages/groups here to keep
things simpler.
+%packages --ignoremissing
+@base
+@core
+@@VBOX_COND_IS_NOT_MINIMAL_INSTALLATION@@
+@development
+@basic-desktop
+@desktop-debugging
+@desktop-platform
+@fonts
+@general-desktop
+@graphical-admin-tools
+@remote-desktop-clients
+@x11
+@@VBOX_COND_END@@
+
+# Prepare building the additions kernel module, try get what we can from
the cdrom as it may be impossible
+# to install anything from the post script:
+kernel-headers
+kernel-devel
+glibc-devel
+glibc-headers
+gcc
+dkms
+make
+bzip2
+perl
+elfutils-libelf-devel
+
+%end
+
+
+# Post install happens in a different script.
+# Note! We mount the CDROM explictily here since the location differs
between fedora 26 to rhel5
+#       and apparently there isn't any way to be certain that anaconda
didn't unmount it already.
+%post --nochroot --log=/mnt/sysimage/root/ks-post.log
+df -h
+mkdir -p /tmp/vboxcdrom
+mount /dev/cdrom /tmp/vboxcdrom
+cp /tmp/vboxcdrom/vboxpostinstall.sh /mnt/sysimage/root/vboxpostinstall.sh
+chmod a+x /mnt/sysimage/root/vboxpostinstall.sh
+/bin/bash /mnt/sysimage/root/vboxpostinstall.sh --rhel
+umount /tmp/vboxcdrom
+%end
diff --git a/src/VBox/Main/include/UnattendedInstaller.h
b/src/VBox/Main/include/UnattendedInstaller.h
index 5003613d..09988815 100644
--- a/src/VBox/Main/include/UnattendedInstaller.h
+++ b/src/VBox/Main/include/UnattendedInstaller.h
@@ -518,6 +518,17 @@ protected:
  };


+/**
+ * RHEL 8 installer (same as RHEL 6 & 7, except for the kickstart
template).
+ */
+class UnattendedRhel5Installer : public UnattendedRhel6And7Installer
+{
+public:
+    UnattendedRhel5Installer(Unattended *pParent) :
UnattendedRhel6And7Installer(pParent, ""redhat8_ks.cfg"") {}
+    ~UnattendedRhel5Installer() {}
+};
+
+
  /**
   * RHEL 5 installer (same as RHEL 6 & 7, except for the kickstart
template).
   */
--
}}}

https://www.virtualbox.org/pipermail/vbox-dev/2020-July/015524.html
",Frank Batschulat (Oracle)
17849,Error Relaunching VirtualBox VM Process:5,other,other,VirtualBox 5.2.14,2020-08-13T00:54:53Z,2020-08-13T00:54:53Z,Cannot start any VM of Virtual Box,Andres0910
19810,"Can not run any VM's ""Error relaunching VirtualBox VM process: 5""",other,other,VirtualBox 6.0.14,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
19809,Very bad latency numbers with more than 1 vCPU,Windows,Linux,VirtualBox 6.1.10,2020-08-13T22:11:28Z,2020-08-13T22:11:28Z,"VirtualBox 6.1.12 verified on Win10 host (or openSUSE TW host), with Linux guests Ubuntu 16/18 or openSUSE TW.

Basically, I have distilled this down to a small perl script, that sleeps for 1ms for 1000 times.  Ideally, this would be 1000ms total -- but on real hardware, the script takes just a shade under 1100ms per iteration (perl overhead, etc), and when VirtualBox is behaving, about 1350-1425ms per iteration.

On real hardware, 100% of 1ms sleeps are <2ms.  When VirtualBox is behaving, 99% of 1ms sleeps are <2ms, and the upper bound is around 10-15ms for a few outliers.

The problem is when vCPU is 2+ ... the more added, the worse latency gets.  1ms sleeps start taking 100ms, 300ms, 500ms, occasionally even 900ms to return.",JasonM
19814,I can't install Windows 2019 in a virtualbox machine,Windows,Windows,VirtualBox 6.1.10,2020-08-14T15:50:11Z,2020-08-14T15:50:11Z,"When I try to add a virtualbox machine and start the instalation from The ISO image, I get ERROR

The Host where it runs virtualbox is Windows 2008R2 64bits with lasts updates",LluisG
19813,Instalation Windows2019,Windows,Windows,VirtualBox 6.1.10,2020-08-14T15:52:02Z,2020-08-14T15:52:02Z,"When I try to install Windows2019 I get Error

Versión 6.1.12.r

The host is Windows 2008R2 Server 64 bits",LluisG
19815,Extremely low performance and high CPU consumption on Ryzen 3600X,Windows,Windows,VirtualBox 6.1.10,2020-08-15T21:29:08Z,2020-08-15T21:29:08Z,"I started having this problem after migrating my VMs to the new hardware - i.e. Ryzen 3600X and Asus B550 motherboard. Simply booting a VM takes about 6 minutes with 30-40% CPU utilization, and running a VM in idle mode consumes about 10-20% CPU.
Host and guest - Windows 10 both.
See the logs.",fandrei
19414,ljmp (mem48) fails,other,other,VirtualBox 6.1.4,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
16350,VERR_SSM_LOADED_TOO_MUCH when restoring snapshot,Windows,Windows,VirtualBox 5.1.12,2020-08-18T14:23:48Z,2020-08-18T14:23:48Z,"I cannot resume VM state from existing snapshot, getting following error:

Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).


E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Host: Windows10
Guest: Windows10

",mammoth
14275,Error with USB 3.0 devices on VirtualBox 5.0,Windows,all,VirtualBox 5.0.0,2020-08-19T09:10:11Z,2020-08-19T09:10:11Z,"When I try to attach a device (USB 3.0) I got this message:

VirtualBox Error
Failed to attach the USB device Ralink 802.11 n WAN [0101] to the virtual machine ...
Details
USB device 'Ralink 802.11 n WLAN' with UUID ... Is busy with a previous request. Please try again later.


Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDeviceWrap
Interface: 
IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Then I try changing to USB 2.0, but the error continue.

My HOST is DELL Inspiron 17r i7 with OS Windows 8.1 64 bits with 16 GB RAM, 1 TB HD (400 GB free).

I got the same error using with Existents VMs, one OS Win XP SP3 and  the second with Debian. ",Xopxe
19527,"The guest OS has access to the host microphone despite the ""Enable Audio Input"" setting being disabled.",all,all,VirtualBox 6.1.6,2020-08-19T10:49:58Z,2020-08-19T10:49:58Z,"The guest OS has access to the host microphone despite the ""Enable Audio Input"" setting being disabled.

My host OS is Ubuntu 18.04
Host Audio Driver: PulseAudio
Audio Controller: ICH AC97
VirtualBox 6.1.6

For the guest OS I have tested several Linux guests, I have not tested non-linux guests.

Steps to reproduce this bug:

1. Create a new VM using an Ubuntu host and a Linux guest. (I don't know if this bug effects other hosts)
2. Open the settings for the VM, click the audio tab and uncheck the ""Enable Audio Input"" setting.
3. Start the VM.
4. Use some application inside the VM to record audio or just look at the microphones sound levels from the guest OS's audio input settings.",eqkb
19751,clarify license of VBoxGuestAdditions ISO OSE or PUEL (free vs nonfree),all,all,VirtualBox 6.1.10,2020-08-19T12:08:49Z,2020-08-19T12:08:49Z,"VBoxGuestAdditions iso was PUEL (nonfree, proprietary) in 2009 as per [https://forums.virtualbox.org/viewtopic.php?f=10&t=21374 this forum discussion]. Therefore the Debian package [https://packages.debian.org/buster/virtualbox-guest-additions-iso virtualbox-guest-additions-iso] is still in Debian nonfree (meaning: Debian is saying that package is proprietary, not Open Source / Free / Libre Software). The [https://metadata.ftp-master.debian.org/changelogs//non-free/v/virtualbox-guest-additions-iso/virtualbox-guest-additions-iso_6.0.4-1_copyright Debian license file for virtualbox-guest-additions-iso] still says so.

A lot has happened since 2009.

The VirtualBox licensing FAQ `[2]` does not mention the VBoxGuestAdditions ISO. It only mentions the VirtualBox Extension Pack being under nonfree license Extension Pack Personal Use and Evaluation License (PUEL) `[3]`.

Editions page `[4]` stating:

> Before version 4.0, there were two editions of VirtualBox: a full binary containing all features and an ""Open Source Edition"" (OSE) with source code. With version 4.0, there is only one version any more, which is open source, and the closed-source components have been moved to a separate extension pack.

When installing from guest using guest additions ISO, there is no PUEL license prompt either.

Source code organization page `[5]` mentions:

> src/VBox/Additions/: The ""Guest Additions"" for Windows and Linux (and possibly more in the future); this is code that must be installed within a guest to optimize its performance and usability. The build system compiles this code into an ISO file that can be mounted as a VM's virtual CD-ROM drive, as described in the user manual.

The VirtualBox guest additions source tree is apparently part of OSE. Therefore the build result should also be under OSE.

VirtualBox extension pack source code was as far as I know never visible to the general public. Therefore reviewing the situation with today's knowledge, I wouldn't know why virtualbox-guest-additions-iso should be considered being under non-free PUEL license.

The licensing state (libre vs non-libre) was never in public, specifically mentioned, clarified according to my elaborate web research. It seems quite likely that guest additions ISO is nowadays under a libre license (OSE).

Asked about this in [https://forums.virtualbox.org/viewtopic.php?f=10&t=21374&p=477656#p477656 virtualbox forums] and Debian issue tracker [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962311 move virtualbox-guest-additions-iso from non-free to contrib] but haven't received any answer after more than 1 months therefore I guess there won't be an answer. Therefore now asking here.

I speculate it could be that the Debian maintainers of the package are waiting for the VirtualBox representatives to make any statement regarding the license.

It would be good if this could be clarified. A short reply ""VBoxGuestAdditions iso is OSE."" would suffice.

`[1]` -

`[2]` https://www.virtualbox.org/wiki/Licensing_FAQ

`[3]` https://www.virtualbox.org/wiki/VirtualBox_PUEL

`[4]` https://www.virtualbox.org/wiki/Editions

`[5]` https://www.virtualbox.org/wiki/Source_code_organization
",adrelanos
19808,Cannot get my VM to run with,other,other,VirtualBox 6.1.10,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
19822,Constant and varied problems installing ubuntu VM from Windows host,other,other,VirtualBox 6.1.10,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
17515,VBoxManager gets into a bad state,Windows,Linux,VirtualBox 5.2.4,2020-08-19T18:56:17Z,2020-08-19T18:56:17Z,"
simple repro on windows, foo.bat:


    set VBOX=""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe""

    :loop
    %VBOX% controlvm ""%1"" poweroff
    %VBOX% snapshot ""%1"" restorecurrent
    %VBOX% startvm ""%1""

    goto loop


this results in a bunch off issues, including:


VBoxManage.exe: error: The machine 'box' is already locked by a session (or being locked or unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp


VBoxManage.exe: error: Invalid machine state: PoweredOff (must be Running, Paused or Stuck)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: ""PowerDown(progress.asOutParam())"" at line 578 of file VBoxManageControlVM.cpp


and eventually it dies:

Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Snapshot operation failed
VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleSnapshot(struct HandlerArg *)"" at line 539 of file VBoxManageSnapshot.cpp
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp

at this point a full restart of all VBox processes is required.
",spongman
19823,Windows 10 Audio VRDE Driver Bug,other,Linux,VirtualBox 6.1.10,2020-08-20T04:05:12Z,2020-08-20T04:05:12Z,"VirtualBox VMs freeze on boot up due to a Audio driver issue.  See clip from v.log below 

00:00:24.165034 Audio: Enabling input for driver 'AudioVRDE'
00:00:24.165105 Mixer: Setting recording source of sink '[Recording] Line In' to 'Line-In'
00:00:24.208146 Audio: Disabling input for driver 'AudioVRDE'
00:00:24.208218 Mixer: Setting recording source of sink '[Recording] Line In' to '<None>'
00:00:24.515883 Audio: Enabling input for driver 'DSoundAudio'
00:00:24.516780 Mixer: Setting recording source of sink '[Recording] Line In' to 'Line-In'
00:00:24.517068 Audio: Disabling input for driver 'DSoundAudio'
00:00:24.530419 Audio: Enabling input for driver 'AudioVRDE'

Can be fixed by disabling audio.  Once audio is disabled, VMs boot fine. ",JackieWin10
19818,Use portable sched_yield() rather than pthread_yield(),Linux,Linux,VirtualBox 6.1.10,2020-08-20T18:20:12Z,2020-08-20T18:20:12Z,"The sched_yield() call is the standard and portable routine.  Current calls to pthread_yield() in Virtualbox sources (host and guests) should be replaced by calls to sched_yield().  If sched_yield() is not available on a platform, then the build tools (including those for the Guest Additions) could arrange to use a shim routine that calls pthread_yield().  

This would be helpful in supporting platforms that do provide support for non-portable libraries and routines.",Harry M
19827,Display problem using Python-IDE,Windows,Windows,VirtualBox 6.1.6,2020-08-21T17:31:16Z,2020-08-21T17:31:16Z,"I tried the Eric IDE for Python on a Win10 VM.
The text on various window tabs was distorted.
The effect occured with VBoxSVGA and activated 3D acceleration.
It vanished with 3D acceleration deactivated.",dornech2
19828,Bug virtualización por hardware,Windows,Windows,VirtualBox 6.1.10,2020-08-21T22:41:54Z,2020-08-21T22:41:54Z,"en maquinas donde la virtualización no es compatible, aunque no este activada no te deja guardar la configuración",MaurOwO
19826,Can only attach USB Scanner 1st Time Virtual Machine started,other,other,VirtualBox 6.1.10,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
19602,VirtualBox 6.1.6 and 6.1.8 failled to start virtual machines,Solaris,Windows,VirtualBox 6.1.8,2020-08-23T06:17:42Z,2020-08-23T06:17:42Z,"Hello,

I have used VirtualBox successfully under Illumos/OpenIndiana (the open version of Solaris). However, today I upgraded my system and I
cannot run VirtualBox version 6.1.6 r137129. My system has ab AMD FX-6300 Six-core processor and AMD-V is enable. When the I try to run
either Windows XP or Windows 7 I get the following message:

Failed to open a session for the virtual machine Win7.

VirtualBox can't enable the AMD-V extension. Please close all other virtualization programs. (VERR_SVM_IN_USE).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

KVM is not installed in my system:

$ pkg list kvm

pkg list: no packages matching the following patterns are installed:
kvm

Also bhyve is not installed inthis system:

$ pkg list bhyve

pkg list: no packages matching the following patterns are installed:
bhyve

Since I have no idea what is going I thouggt someone here might be able to help fixing this problem.

Regards,

Apostolos

PS Setting export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on a terminal and running VBox from there does not solve the problem...

PSS I have also used a build of VBox 6.1.8 and I see exactly the same behavior",asyropoulos
19829,Hard to move VirtualBox guest windows,Linux,all,VirtualBox 6.1.10,2020-08-23T21:52:32Z,2020-08-23T21:52:32Z,"On Ubuntu Mate 20.04.1 folal (but not on 18.04.5 bionic) VirtualBox guest windows won't move unless
1) The focus is starts on a different window.
2) Press the Host key (Right Control)

This worked correctly on Ubuntu Mate 18.04.5 but is broken on 20.04.1

Both systems have VirtualBox 6.1.12 r139181",Howad
19830,VB 6.1.12 Windows 10 host BSOD NDU.SYS,Windows,Linux,VirtualBox 6.1.10,2020-08-24T19:53:03Z,2020-08-24T19:53:03Z,"No issues with previous VB version. After install BSOD  usually within an hour after Win10 host boot. VB does not have to be running though if so the BSOD seems quicker to result. The minidump indicates NDU.SYS faulting with KMODE_UNHANDLED.

Uninstalling VB 6.1.12 results with NO host BSOD for 4 days. Reinstalling results in BSOD within 1 hour of host boot. Currently uninstalled with no host BSOD since.

2 decyphered minidumps below:

==================================================
Dump File         : 082220-8750-01.dmp
Crash Time        : 8/22/2020 9:41:05 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff802`317b4540
Parameter 3       : ffff9d89`fb53d4a8
Parameter 4       : ffff8d80`e29df930
Caused By Driver  : Ndu.sys
Caused By Address : Ndu.sys+4540
File Description  : Windows Network Data Usage Monitoring Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.18362.1 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+1c23c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\082220-8750-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 742,612
Dump File Time    : 8/22/2020 9:42:40 PM
==================================================

==================================================
Dump File         : 082020-10078-01.dmp
Crash Time        : 8/20/2020 9:46:39 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff805`7a723df9
Parameter 3       : 00000000`00000001
Parameter 4       : ffff8b0d`b5deb9c0
Caused By Driver  : Ndu.sys
Caused By Address : Ndu.sys+3df9
File Description  : Windows Network Data Usage Monitoring Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.18362.1 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+1c23c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\082020-10078-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 1,545,378
Dump File Time    : 8/20/2020 9:47:24 PM
==================================================

",psionprime
19831,VB Virtual Monitor Setting,Windows,Windows,VirtualBox 6.1.10,2020-08-25T09:08:20Z,2020-08-25T09:08:20Z,"I am using high resolution screen (3840 x 2560).
When I start my VM I can use the virtual monitor to force the guest to switch the resoution to up to 1600x900. The pull down menu however offers also 1920x1080 and 1920 x 1200. Nothing happens if select them from a lower current guest resultion. 
When expand the guest to maxumum from the host window (auto resizing) I can use the full screen resolution (Great !).
If I click now on in the virtual monitor menu on 1920 x1200 the guest resizes (virtualbox window however remanis maximize).
So there are some issues here on handling the virtual monitor I guess. 
Would be greast offer higher ressultions in the virtual monitor menu for up to the maximum host physical screen resolution (maximizing the host window proofs that the resultions are achievable) but at least that the offered screen resultions in the virtual screen resoltion work properly.",Andreas S
19833,virtualbox showing : The VM session was aborted.   Result Code:  E_FAIL (0x80004005) Component:  SessionMachine Interface:  ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7},Windows,all,,2020-08-26T06:27:01Z,2020-08-26T06:27:01Z,The VM session was aborted,TGT
19834,VM slow down when video recording enabled,all,Linux,VirtualBox 6.1.10,2020-08-26T20:15:19Z,2020-08-26T20:15:19Z,"To reproduce bug you can try create VM with one core and start it with and without video recording. With video recording enabled you must see some slow down of working VM.

This happens because of slow working vpx_codec_encode call under lock inside RecordingStream::Process:

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L373

{{{
int RecordingStream::Process(RecordingBlockMap &mapBlocksCommon)
{
    LogFlowFuncEnter();

    lock();

    ...
                    rc2 = writeVideoVPX(msTimestamp, pVideoFrame);
    ...

    unlock();

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}

And writeVideoVPX calls vpx_codec_encode:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L1161

{{{
vpx_codec_err_t rcv = vpx_codec_encode(&pCodec->VPX.Ctx,
                                           &pCodec->VPX.RawImage,
                                           pts                          /* Timestamp */,
                                           this->Video.uDelayMs         /* How long to show this frame */,
                                           0                            /* Flags */,
                                           pCodec->VPX.uEncoderDeadline /* Quality setting */);
}}}

In fact vpx_codec_encode working slow beacuse of last parameter ""deadline"" by default is zero (which means infinite deadline for encoding)

Interesting part is that in 5.x virtualbox branch there was a code which fill the default value of uEncoderDeadline but this code not present in 6.0/6.1  branches...


{{{
/**
 * Invalidates the video recording configuration.
 */
void Display::i_videoRecInvalidate(void)
{
    AssertPtr(mParent);
    ComPtr<IMachine> pMachine = mParent->i_machine();
    Assert(pMachine.isNotNull());

    mVideoRecCfg.enmDst = VIDEORECDEST_FILE; /** @todo Make this configurable once we have more variations. */

    /*
     * Cache parameters from API.
     */
    com::SafeArray<BOOL> aScreens;
    HRESULT hrc = pMachine->COMGETTER(VideoCaptureScreens)(ComSafeArrayAsOutParam(aScreens));
    AssertComRCReturnVoid(hrc);

    mVideoRecCfg.aScreens.resize(aScreens.size());
    for (size_t i = 0; i < aScreens.size(); ++i)
        mVideoRecCfg.aScreens[i] = aScreens[i];

    hrc = pMachine->COMGETTER(VideoCaptureWidth)((ULONG *)&mVideoRecCfg.Video.uWidth);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureHeight)((ULONG *)&mVideoRecCfg.Video.uHeight);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureRate)((ULONG *)&mVideoRecCfg.Video.uRate);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFPS)((ULONG *)&mVideoRecCfg.Video.uFPS);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFile)(mVideoRecCfg.File.strName.asOutParam());
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxFileSize)((ULONG *)&mVideoRecCfg.File.uMaxSizeMB);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxTime)((ULONG *)&mVideoRecCfg.uMaxTimeS);
    AssertComRCReturnVoid(hrc);
    BSTR bstrOptions;
    hrc = pMachine->COMGETTER(VideoCaptureOptions)(&bstrOptions);
    AssertComRCReturnVoid(hrc);

    /*
     * Set sensible defaults.
     */
    mVideoRecCfg.Video.fEnabled = true; /* Enabled by default. */

    if (!mVideoRecCfg.Video.uFPS) /* Prevent division by zero. */
        mVideoRecCfg.Video.uFPS = 15;

#ifdef VBOX_WITH_LIBVPX
    mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
#endif

#ifdef VBOX_WITH_AUDIO_VIDEOREC
    mVideoRecCfg.Audio.fEnabled  = false; /* Disabled by default, unless set otherwise below. */
    /* By default we use 48kHz, 16-bit, stereo for the audio track. */
    mVideoRecCfg.Audio.uHz       = 48000;
    mVideoRecCfg.Audio.cBits     = 16;
    mVideoRecCfg.Audio.cChannels = 2;
#endif

}}}


Here is:
>mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
",gim
19837,Forwarded ports are blocked,Windows,Linux,VirtualBox 6.1.10,2020-08-27T13:42:17Z,2020-08-27T13:42:17Z,"It can happen that ports which are forwarded to the guest are blocked on the host and therefore you are unable to open those ports on the host. Then you have to remove the forwarding, open the ports and then re-add the forwarding.

Expected behaviour:
Forwarded ports should not be blocked.",jnevada
19589,Black screen after GUI login on Ubuntu with tools installed.,Windows,Linux,VirtualBox 6.1.6,2020-08-28T12:50:31Z,2020-08-28T12:50:31Z,"Hi 

I'm running on virutalbox (6.1.6r137129) on Windows 10 and I have installed an Ubuntu 20.04 guest on the host. I have then installed the virtualbox guest additions on the guest. 

The problem I have is that after bootup, the login window is displayed and I log in but then the screen goes totally black. If I then resize the window, the desktop appears

I'm not sure if this is a bug in virtualbox / guest additions or some sort of conflict with Ubuntu. I have tried this multiple times installing new version of Ubuntu and each time the problem re-occurs so for me it is repeatable. 

Steps to reproduce:

1. Install Ubuntu 20.04 Guest OS (I gave it 128MB video memory, VMSVGA video, 3D acceleration enabled 

2. Boot guest OS 

3. Install guest additions (you'll need ""build-essential"" package installed too) 

4. Reboot 

5. Set guest to start up in full screen mode. 

6. Login 

<black screen> 

7. Re-size guest window. 

<image appears>

",MattF
19642,Virtualbox UI freezes after clicking VM in list and corresponding VM is not properly booting,Windows,Linux,VirtualBox 6.1.10,2020-08-28T14:35:15Z,2020-08-28T14:35:15Z,"Observed behaviour:
--------------------

When I start the VM with ""vagrant up"" (while having Virtualbox GUI open), the VM is created and booted in Virtualbox. Then vagrant hangs at the point, when it tries to access the VM via SSH in order to configure the VM. At the same time in Virtualbox, when I click on the VM in the list, the GUI of Virtualbox freezes and does not unfreeze anymore. I need to end the Virtualbox Manager Process in Windows Task manager in order to make Virtualbox work again.
The Problem occurs with several Vagrant Boxes with recent Ubuntu versions (e.g. ubuntu/focal64, ubuntu/eoan64). It seems to work (at least most of the time) with older Ubuntu versions (e.g. ubuntu/trusty64).

I have the feeling that I experience problems with Virtualbox since upgrading Windows to 2004 (Spring 2020 Update) and/or enabling WSL2, but I cannot prove since I haven't used Virtualbox immediately before the upgrade / WSL 2 enabling.

Expected bahaviour:
-------------------

The Virtualbox GUI does not freeze when I click on the VM in the list of VMs and Vagrant is able to finish the prozess of configuring the VM.


Additional Information:
-----------------------

- Windows 10 Pro (2004, Spring 2020 Update)
- Windows Subsystem for Linux (WSL) 2 enabled 
- Virtualbox 6.1.10 r138449 (Qt5.6.2)
- Vagrant 2.2.9
- Vagrant Box: ubuntu/focal64, 20200605.1.0",chrizzzt
1633,Windows XP cannot boot natively after installation of Guest Additions (BSOD during boot),other,Windows,VirtualBox 4.0.6,2020-08-28T20:29:11Z,2020-08-28T20:29:11Z,"I have successfully managed to run Windows XP Home / SP3 from a raw partition within Virtual Box on an OpenSUSE 10.3 Linux host. Without Guest Additions installed, the windows installation can be booted both natively as well as in a virtual machine.

Once the Guest Additions are installed, booting natively fails. Immediately after showing the initial Windows splash screen, the mouse pointer appears in the center of the black screen, and the machine locks up completely. The keyboard doesn't react at all; doing a CTRL-ALT-DEL, for example, doesn't work.

I have further managed to reproduce the problem by simply installing the Guest Additions into the natively running Windows (from a CD-Rom that contains the Guest Additions). Installation apparently proceeds without problems (no warnings or error messages), but the machine freezes up at the next native boot as described above. Booting into the virtual machine is fine (and the Guest Additions work properly).

In both cases, the windows Windows installation boots natively again after the Guest Additions have been uninstalled, e.g. from within a virtual machine. On the first native boot of the Windows installation, some device drivers are apparently reinstalled (Graphics and Mouse, I think).

If a native boot has failed with the Guest Additions installed, all Linux partitions (extfs3) are checked during the next Linux boot because of not being unmounted properly, although the previous Linux shutdown proceeded without problems. The NTFS partition holding the Windows install is also flagged as being not clean (an ntfs-3g mount has to be forced, for example, and during a boot into a virtual machine the Windows installation starts up with offering to boot into previous configurations or a safe mode).

Hardware: Samsung X20 laptop with an Intel i915 Graphics chip set, a single SATA drive holding several partitions, the first one being used for the Windows installation.",Christian Marquardt
19841,WarpDrive doesn't work on VirtualBox 6.x anymore,Linux,Windows,VirtualBox 6.1.10,2020-08-28T20:57:13Z,2020-08-28T20:57:13Z,"So in VirtualBox 5.x warp drive was working fine. When you make:

{{{
VBoxManage setextradata VM-name ""VBoxInternal/TM/WarpDrivePercentage"" 200
}}}

the time inside VM was going faster. But in VirtualBox 6.x it  doesn't work at all...

This happens because of this change:

{{{
    rc = CFGMR3QueryU32(pCfgHandle, ""TimerMillies"", &u32Millies);
    if (rc == VERR_CFGM_VALUE_NOT_FOUND)
        u32Millies = VM_IS_HM_ENABLED(pVM) ? 1000 : 10;
}}}

In 5.x default value of TimerMillies was 10 ms always (not 1 sec). But it is not the root of the problem.
The root lies near semaphore timeout calculation which trigger return from HLT. When WarpDrive is enabled this semaphore timeout calculated in wrong way.",gim
19842,Settings' 'OK' button not working.,Windows,other,VirtualBox 6.1.10,2020-08-29T06:53:59Z,2020-08-29T06:53:59Z,The 'OK' button in settings is not working for the Virtual Box Manager,H3
15839,Attempting to output audio causes processes in guest to hang,Windows,Linux,VirtualBox 5.1.4,2020-08-31T06:50:49Z,2020-08-31T06:50:49Z,"Since upgrading to 5.1.4 audio output in the guest has become unreliable. A process that attempts to play sound freezes. Sometimes, if I kill off all processes trying to play sounds, I can run aplay or speaker-test a couple of times, but a few moments later they still stop working again.

Guest is running 64-bit Linux 4.6.0, host is 64-bit Windows 10 Home. The sound card is ICH AC97.",Sam Morris
19846,VIRTUALBOX 6.1.6,other,other,VirtualBox 6.1.6,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
19847,/opt/VirtualBox/vboxwebsrv: no process found,Linux,all,VirtualBox 6.1.10,2020-08-31T14:09:46Z,2020-08-31T14:09:46Z,"VirtualBox-6.1.13-140124-Linux_amd64.run

running Leap 15.1 with kernel 5.5.0-1.g3f183bf-default

VirtualBox has been installed successfully.

giga-151:/home/hmi/import # service vboxweb-service status
* vboxweb-service.service
   Loaded: loaded (/opt/VirtualBox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2020-08-31 15:19:05 CEST; 3min 30s ago
  Process: 7724 ExecStart=/opt/VirtualBox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)
    Tasks: 0
   CGroup: /system.slice/vboxweb-service.service

Aug 31 15:19:05 giga-151 vboxweb-service.sh[7724]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 31 15:19:05 giga-151 su[7730]: (to vbox) root on none
Aug 31 15:19:04 giga-151 systemd[1]: Starting vboxweb-service.service...
Aug 31 15:19:05 giga-151 vboxweb-service.sh[7781]: VirtualBox web service started.
Aug 31 15:19:05 giga-151 systemd[1]: Started vboxweb-service.service.

giga-151:/home/hmi/import # service vboxweb-service stop

giga-151:/home/hmi/import # service vboxweb-service status
* vboxweb-service.service
   Loaded: loaded (/opt/VirtualBox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2020-08-31 15:23:11 CEST; 5s ago
  Process: 7897 ExecStop=/opt/VirtualBox/vboxweb-service.sh stop (code=exited, status=0/SUCCESS)
  Process: 7724 ExecStart=/opt/VirtualBox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)

Aug 31 15:19:05 giga-151 vboxweb-service.sh[7724]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 31 15:19:05 giga-151 su[7730]: (to vbox) root on none
Aug 31 15:19:04 giga-151 systemd[1]: Starting vboxweb-service.service...
Aug 31 15:19:05 giga-151 vboxweb-service.sh[7781]: VirtualBox web service started.
Aug 31 15:19:05 giga-151 systemd[1]: Started vboxweb-service.service.
Aug 31 15:23:10 giga-151 systemd[1]: Stopping vboxweb-service.service...
Aug 31 15:23:10 giga-151 vboxweb-service.sh[7897]: vboxweb-service.sh: Stopping VirtualBox web service.
Aug 31 15:23:10 giga-151 vboxweb-service.sh[7897]: 
'''/opt/VirtualBox/vboxwebsrv: no process found'''
Aug 31 15:23:11 giga-151 vboxweb-service.sh[7906]: VirtualBox web service stopped.",hgf_m
19848,Ubuntu new installation not booting,Windows,Linux,VirtualBox 6.1.10,2020-08-31T20:18:24Z,2020-08-31T20:18:24Z,Ubuntu 20.04.1 new installation not booting sometimes. Logs attached for two incidents.,009
19408,Linux panic with a 'not-present page' when rebooting resumed VM,Linux,all,VirtualBox 6.1.4,2020-08-31T21:03:37Z,2020-08-31T21:03:37Z,"After I suspended/resumed Windows 10 guest (Fedora 31 host, kernel 5.5.9), the rebooted it, VM caused kernel oops and virtual box froze (all windows, including manager). Attaching kernel oops report.",Max Fedotov
19849,VirtualBox 6.1.10/12  VRDP Feature Mouse Lag cause user experience,other,Windows,VirtualBox 6.1.10,2020-09-03T03:25:26Z,2020-09-03T03:25:26Z,"When VRDP feature is used and mouse is lagging by 2 seconds, but using console virtual box is ok

-Virtualbox guest addition has been installed
-3D has been enabled
-256mb assigned to memory display
-MSTSC set to realtime in task manager
-mouse is set to usb table
-mouse properties in control panel has been change from none to windows standard large scheme etc, all modes tested and still got issue
-mouse pointer change from slow to fast , still got the issue
-We have assigned 4-8 GB of ram as well to virtual box but does not resolve the issue
-We have assigned 6 cpu to virtual box but still does not resolve the issue
-We have change mstsc settings to slowest mbps link still have the same issue
-We have change the display settings from 100 to 125 still got issue , incase related to a DPI
-usb extension is set from 2.0 as well as 3.0 nothing changed
-extension package is also latest version
-Issue is not happening when access via virtual box console
-Issue only happens when VRDP feature is used
-Seems the issue is with VRDP feature interprocess communication with the mstsc and virtualbox cause a drawing of mouse movement to be lagged
-Anything can be done to improve user experience?

Thanks",EdgarMoreno
19853,Linux instalation during boot instalation ISO,Windows,Linux,VirtualBox 6.1.10,2020-09-03T11:01:37Z,2020-09-03T11:01:37Z,critical error occured while running the virtual machine. The issue is probably related to windows ,jtach
7187,VirtualBox huge log file harvesting disk,Linux,Windows,VirtualBox 3.2.6,2020-09-03T22:36:03Z,2020-09-03T22:36:03Z,"Using VirtualBox 3.2.6 r633112, Ubuntu 10.04 as host and Windows XP Professional as guest, I had problems starting a program (Mach3) inside Windows, I didn't open after three attempts but continued working with Firefox and other programs, after some time, I received an Ubuntu system message indicating my hard disk had very few available space, this surprised me since I was supposed to be using just 20 GB (for both Ubuntu and virtual WinXP) from my 160 GB disk. I forced VBox down and searched for the problem, I found four VBox log files in the Logs directory for my VM, two had sizes of 30 GB and 90 GB!

I'm not sure whether such a huge log file should be useful for debugging, but guess VBox could emit an alert when these logs grow too much so that the user can pay attention and take some actions before the host system becomes unresponsive.
",José Jorge
19858,Unable to resize guest window with multi-monitor,other,other,VirtualBox 6.1.10,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
19551,Virtual Machine can not start,Windows,all,VirtualBox 6.1.6,2020-09-04T14:39:12Z,2020-09-04T14:39:12Z,"Hi,

After Virtual Box upgrade to 6.1.6 r137129 (Qt5.6.2) many machines stop to work. Virtual BOX and Guest Aditional upgrade were performed fine. But after few days, in some VMachine the screen stay black after the power on. The issue happened in some WINDOWS10 and FEDORA Virtual Machine, but not on all.

I tried to uninstall and install VIRTUAL BOX but the black screen issue is still present. The only solution is delete and create the Machine from scratch.

Could some one help me to debug the issue to understand why it is happen?",Ivan_70
19859,After executing a tutorial virtualbox is becoming super slow to run a Windows 10 instance,Windows,other,VirtualBox 6.1.10,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
19860,VirtualBox 6.1.13 (testbuild) tiggers BLUE SCREEN on Windows when UAC Required,Linux,Windows,VirtualBox 6.1.10,2020-09-04T16:21:32Z,2020-09-04T16:21:32Z,"Host: Archlinux with Linux 5.8.5
VirtualBox: 6.1.13 testbuild (build=139989, sdkbuild=139990)
Guest: Windows 7 32-bit (run headless, accessed via rdesktop)
Guest Additions: version=6.1.13-139990

Blue Screen is triggered each time User Account Control Activated to allow changes to windows.

This problem seems to be triggered by Windows 7 User Account Control (UAC). I can't even install simple updates to PuTTY, etc. without 6.1 causing a BLUE screen and reboot. This is triggered any time you are prompted to allow a change to your computer with UAC. The UAC dialog is displayed and the remainder of the screen is darkened. After choosing ""Yes"" to allow the change, the darken background is not removed from any open windows and about 5 seconds later BLUE SCREEN, and the Virtualbox 6.1 reboot screen is shown. 

This will occur if you simply attempt to start the command prompt with ""Run As Administrator"". I have 3 Minidumps collected if needed and the Event Viewer reports the critical error as ""Kernel Power"" (which doesn't look very useful)

As a test, I disabled UAC completely and attempted the updates to PuTTY again. With UAC disable, there is no problem. I can update software as normal without the Blue Screen on 6.1. So the bug in 6.1 causing the BLUE SCREEN crash is triggered any time elevated privileges are needed and UAC is activated. 

I have run this same VM for 5+ years and never had any problem with the 5.1 or 5.2 Virtualbox branches. There is something new in 6.1 that triggers a crash when Windows UAC is activated. 

Let me know if the Minidumps will be of any use or if there is other documentation I can provide and I'm happy to attach them.
",drankinatty
19861,Windows XP 32bit does not start,other,other,VirtualBox 6.1.10,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
19597,Mouse pointer doesn't work properly in Windows guests when scaling is on,other,Windows,VirtualBox 6.1.8,2020-09-06T21:36:08Z,2020-09-06T21:36:08Z,"This problem started happening when I've got a 4k monitor and set scaling >= 150% in the guest OSes (as VBs built-in scaling makes the picture very blurry).

When I have mouse integration enabled, certain types of mouse pointers look messed up (see the attached video for an example). When mouse integration is disabled, the mouse pointer freezes in place when moving over certain locations on the screen (it seems that these locations are same as in the first case).
Guests I tried so far - Windows 7 and Windows 10, both have this bug. This problem doesn't happen for Ubuntu.
Hosts - Windows 7 and 10, and Ubuntu 20. All have this bug.
",fandrei
19864,OVERHEATING AND HIGH RISK TO DAMAGE MACHINE - MacBook Pro 2018 CATALINA OS,other,OSX Server,VirtualBox 6.1.14,2020-09-07T10:22:59Z,2020-09-07T10:22:59Z,"THE VIRTUALBOX WITH CATALINA AND MACBOOK PRO 2018 CREATES OVERHEATING PROBLEMS. THE PROCESSOR COMES TO WORK AT 80 90 CELSIUS DEGREES, THE PROCESS AS YOU CAN SEE WORKS AT> 160% OF THE CPU, WE ARE NOT THERE, SOMETHING IS NOT WORKING WITH THE SOURCE FOR MACOS CHECK THANK YOU CAN DAMAGE THE MACHINE!",nickslay@…
19835,Wrong guest screen resolution with host using 1920x1080,Linux,Windows,VirtualBox 6.1.10,2020-09-07T10:28:26Z,2020-09-07T10:28:26Z,"Hello. I'm using VirtualBox 6.1.12 on a ArchLinux host (Kernel: x86_64 Linux 5.8.3-arch1-1, Resolution: 1920x1080), running an Windows 7 guest with the guest additions installed from the ISO, also in version 6.1.12. 

But in guest OS, the screen resolution  unable to identify the host's screen resolution 1920x1080.

Similar issue as https://www.virtualbox.org/ticket/19499",zeno
19867,Unable to run Windows 7 64 Bit OS Virtual Machine,Windows,Windows,VirtualBox 6.1.14,2020-09-07T10:29:53Z,2020-09-07T10:29:53Z,Unable to run Windows 7 64 Bit OS Virtual Machine,rdua
19634,vboxweb.cpp fails to compile with gSoap 2.8.103,all,other,VirtualBox 5.2.34,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
17636,"After minimising full screen VM, on restoring only quarter of screen shown",Linux,all,VirtualBox 5.2.8,2020-09-07T14:16:14Z,2020-09-07T14:16:14Z,"On a Kubuntu host, when running a VM full screen, if I minimise the VM and then restore it, the VM stays in full screen mode but only about a quarter of it is shown.

In the attached screen shot you can see a Xubuntu guest part showing top left on a Kubuntu host.

The problem occurs both with Windows and Linux guest.

The problem has only occurred since the host upgraded to Kubuntu 17.10.

If I alternately minimise/maximise/minimise/maximise/.... on the maximise it alternately fails/works.

Bug originally reported on Launchpad  #1731495

",ximera
19868,Divide by zero crashes VM,Mac OS X,Windows,,2020-09-07T15:22:41Z,2020-09-07T15:22:41Z,"I have multiple, reproducible crashes on macOS host with Windows 10 guest.

Will attach 4 example crash reports.

Note that I run 6.1.12, not 6.1.14, and the update checker thinks this is the latest release.

--- 1 ---

Crashed Thread:        23  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [63034]

--- 2 ---

Crashed Thread:        25  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [5393]

--- 3 ---

Crashed Thread:        23  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [23291]

--- 4 ---

Crashed Thread:        26  TaskSet0

Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [66175]
",jonashaag
19778,Guest additions screen resize detection code fails,other,Linux,VirtualBox 6.1.8,2020-09-07T22:29:10Z,2020-09-07T22:29:10Z,"Although I have now upgraded to 6.1.12 for Virtualbox itself and the extensions, I am maintaining the VMs at guest additions 6.1.6 because 6.1.8 introduced an error where the screen resize instruction fails (on Linux machines) when using the 3D facility, e.g. Cinnamon. Making it impossible to run them headless and the issue has been carried over into 6.1.10 & 6.1.12 too. A Debian/Cinnamon VM actually reports the failure to the user.
",Sysop
14291,Lots of error entries in VBoxSVC.log,Windows,other,VirtualBox 5.0.0,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
16221,After upgrading to 5.1.10 Network interface is not working enp0s3: Detected Tx Unit Hang,Windows,Linux,VirtualBox 5.1.10,2020-09-08T16:49:04Z,2020-09-08T16:49:04Z,"After upgrading to virtualbox 5.1.10  Network interface is not working after boot unless its manually reset after boot.Downgrading to virtualbox 5.1.8 fixes the problem.However, upgrading to 5.1.11 is mostly working but not 100% of the time. During the testing it didn't work a few times.
Linux arch 4.8.10-1-ARCH guest on windows 10 Host. 

journalctl -b
kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang",vdv
19816,VirtualBox not able to power-off any (currently-running) machines,Linux,Windows,VirtualBox 5.2.42,2020-09-08T17:20:25Z,2020-09-08T17:20:25Z,"I am using cuckoo sandbox (version 2.0.7) to perform batch dynamic analysis on windows malware. My host system is Ubuntu 18.04 and I am running 10 Windows 7 VMs on parallel (headless).

The Cuckoo Sandbox application will stop a VM when it is done analysing a binary and will restore the specified snapshot. It will then power up the machine to start a new analysis.

After prolonged usage (around 4+ hours), one or more of the running VMs will become unresponsive and will not poweroff. The only solution I have is to restart the computer, as the virtualbox services will fail to reload.
(If I quit the cuckoo sandbox when one of the machines deadlocks, then all of the running machines will become unresponsive and keep running endlessly).

I am attaching the log of the VM that caused the issue most recently",soutsos
19870,virtio-nic has been removed?,Linux,all,VirtualBox 6.1.14,2020-09-08T18:53:36Z,2020-09-08T18:53:36Z,"There is no more virtio-nic option in the gui on Linux (Fedora 32) and machines with a virtio-nic error out on startup:
{{{
Invalid network adapter type '6' for slot '0' (VERR_INVALID_PARAMETER).

Codice di uscita:
NS_ERROR_FAILURE (0x80004005)
Componente: 
ConsoleWrap
Interfaccia: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

}}}
",_ReD_
19871,virtio-nic has been removed?,Linux,all,VirtualBox 6.1.14,2020-09-08T18:54:04Z,2020-09-08T18:54:04Z,"There is no more virtio-nic option in the gui of the open source version on Fedora Linux 32 and existing machines with a virtio-nic do error out on startup:
{{{
Invalid network adapter type '6' for slot '0' (VERR_INVALID_PARAMETER).

Codice di uscita:
NS_ERROR_FAILURE (0x80004005)
Componente: 
ConsoleWrap
Interfaccia: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

}}}
",_ReD_
19872,Partial or Blank VBox UI in Cinnamon 4.6,Linux,all,VirtualBox 6.1.14,2020-09-09T03:50:59Z,2020-09-09T03:50:59Z,"Host: Ubuntu 20.04 (focal) also verified on Linux Mint 20 Ulyana[[BR]]
Kernel: 5.4.0-47-generic[[BR]]
Guest: N/A as it is the main UI[[BR]]
GPU: Nvidia GTX 1060[[BR]]
GPU Driver: nvidia-driver-440-server Xorg[[BR]]
GPU Driver Source: graphics-drivers-ubuntu-ppa-focal[[BR]]
Display Manager: Cinnamon 4.6[[BR]]
Failure is on the host level[[BR]]
[[BR]]
After installing VirtualBox via both apt (virtualbox 6.1.10), downloaded (virtualbox 6.1.14), and through added virtualbox repo (virtualbox 6.1.14) on both Linux Mint 20 and Ubuntu 20.04 running Cinnamon 4.6 (on Ubuntu 20.04 using the UbuntuRemix repo) the UI is either blank or shows up partially.  The cli functionality is all there and working, it is just the UI.  Sometimes I can guess my way around and launch a VM, but for any guest I am using the screen does not refresh.[[BR]]
[[BR]]
Attached are the VBoxBugReport and a screenshot of the partial UI.[[BR]][[BR]]
I would love to take the time to troubleshoot more, but I just don't have it as this is my main system and I need it up and running for work.  I am wiping it and reinstalling Ubuntu 20.04 with Cinnamon 4.4 in which Virtualbox works just fine.",Jared Grange
19874,Failed to create a host network interface,other,other,VirtualBox 6.1.14,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
19876,guest language change changes host,Windows,Windows,VirtualBox 6.1.14,2020-09-10T00:24:37Z,2020-09-10T00:24:37Z,"i am learning german, and though useing a computer in german would help, but when i setup a windows 10 guest on a windows 10 host, and install a new language, it also installs on the host, and changed my time, and language, on top of adding it to the host. when i delete the forein language from the host, it dissapears on the guest as well",devsch
5515,Builtin DHCP server does not pick up setting update once started,Windows,Linux,VirtualBox 3.0.12,2020-09-10T08:52:41Z,2020-09-10T08:52:41Z,"I have several hosts that I want to connect with each other without access to the outside world. So all hosts use host-only networking. One of the hosts provides PXE and DHCP, so I went to File -> Preferences -> Network and edited the settings for the host-only networking. In the tab of the DHCP Server I disabled the DHCP server. Then I started my management server (fixed IP address in the proper range), configured DHCP with a range outside the default range for host-only and started one of the client hosts. PXE went well and the OS was installed. When the client host requested an IP-address, it was served with an address from the builtin DHCP server although I disabled this server. Stopping all clients and restarting VirtualBox did not solve this. After a reboot of the host system, the DHCP server was truly disabled and the client was served with an address from my management server.",SiemKorteweg
19850,Error Cloudera Virtual Box,Linux,other,VirtualBox 6.1.10,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
19881,AltGr not working most of the time,Windows,Linux,VirtualBox 6.1.14,2020-09-11T07:33:32Z,2020-09-11T07:33:32Z,"Setup is a Linux (nixos 20.03) VM on a Windows 10 laptop, usually with 2 screens attached. The VM gets 3 virtual screens.
Both host and guest use a german (qwertz) keyboard layout.

Most of the time, the AltGr key and with it many symbols are not working on the guest. According to xev pressing the key does not trigger anything at all.

Often, but not always, changing from one virtual display to another will make the AltGr key work for a few times before falling back to not doing anything at all.

Sometimes, when changing to another screen and beginning to type, the first letter will be greek and I don't even know how to type those deliberately (it's not AltGr+something).

There have been days where it worked the whole time but those are rare.

Turning automatic keyboard capturing off as some related incidents suggested as solution does not help.

Suspending (save execution state) and restarting does also not help reliably.


To me it seems as if somehow the modifier gets stuck or a wrong keycode is sent or it gets out of sync between host and guest or between the virtual screens?
I can't really find any 100% reliable way to trigger or fix this behaviour.


I'll gladly provide any additional info or perform tests that could help this issue.",Nervengift
12851,High cpu-load (up to 100%) on idle,Linux,Windows,VirtualBox 4.3.6,2020-09-12T21:09:13Z,2020-09-12T21:09:13Z,"My host is Linux 3.13.6 x86_64 and the guest is Windows XP SP3 32 bit with all current updates installed. The guest additions with experimental 3D support are installed too.

If the Windows XP guest is booted up and reached the idle state (0-1% cpu-load in the task manager) I'm noticing that on my Linux host the cpu-load is constantly at ~15% of one core (AMD Phenom II X6 1045T). If I'm booting up the Windows XP guest into the safe mode and it reached the idle state the cpu-load on my Linux guest goes even up to the maximum (~600%/600%).",Sworddragon
19887,frequently the app(VM VirtualBox) does not respond,Windows,Linux,VirtualBox 6.1.10,2020-09-16T12:59:25Z,2020-09-16T12:59:25Z,"Whenever I open the app, it hangs for sure and also when I open any virtual OS it does the same kind of thing.
I am doubtful that it is causing my system to slow down
Help me asap",jishu
19499,Wrong guest screen resolution with host using 1366x768,Windows,Linux,VirtualBox 6.1.6,2020-09-16T13:30:33Z,2020-09-16T13:30:33Z,"Hello. I'm using VirtualBox 6.1.6 on a Windows 10 host, running an ArchLinux guest with the guest additions installed from the ISO, also in version 6.1.6.

When I maximize the screen, or use full screen, the guest resolution is wrong. It seems that VirtualBox is trying to round to the closest multiple of 8, so a few extra pixels are inserted. In maximized mode, scroll bars (horizontal and vertical) are shown. In full screen, a few pixels get off-screen.

It's a minor issue, and I could solve it by using the 1360x768 resolution on my laptop. It's not the recommended resolution, but solves the VirtualBox issue.",luisgbm
19844,hangul keyboard problem,Windows,Windows,VirtualBox 6.1.10,2020-09-17T12:22:33Z,2020-09-17T12:22:33Z,"Hi.

In VB 6.0, Hangul & Hanja key is working.(guest Windows, Ubuntu, etc.)

In VB 6.1, Hangul & Hanja key is not working. (guest Winwods, Ubuntu, etc.)

In both, VB SoftKeyboard is working.

Please correct it.",test2020
19892,macOS 10.15.6 Default Machine Folder Path Cannot be Updated,Mac OS X,all,VirtualBox 6.1.14,2020-09-18T04:11:32Z,2020-09-18T04:11:32Z,"I recently changed my username on my macOS host, and noticed this screen when starting VBox:

[[Image(https://imgur.com/a/anxePYT)]]

I then opened Preferences, and found the ""Default Machine Folder"" option, then changed the path to my new location, shown here:

[[Image(https://imgur.com/nOrw2Ey)]]


However, after confirming this multiple times, quitting and opening VirtualBox back up, completely reinstalling, and rebooting, VirtualBox seems to not take the Default Machine Folder into account at all. 

As a temporary workaround, I've remade my old home folder under my permissions and copied the VirtualBox VMs folder there. I'm not sure if this is only a macOS issue or not, but for those that don't have the know-how to work around this, it can completely break VBox for them.

",lossdev
19893,Plantage de la VM : Code d’arrêt : CRITICAL STRUCTURE CORRUPTION,Windows,Windows,VirtualBox 6.1.14,2020-09-18T09:18:27Z,2020-09-18T09:18:27Z,"Depuis le passage en 6.1.14 sur en un hôte en Windows 10 2004 et de l'invité en Windows 10 2004, plantage régulier de l'invité avec l'erreur -> Code d’arrêt : CRITICAL STRUCTURE CORRUPTION",LFX_LFX
19899,Virtualbox 6.1.14 shared paper press and drag and drop don't work,Windows,Linux,VirtualBox 6.1.14,2020-09-18T19:04:32Z,2020-09-18T19:04:32Z,"Hello,
With the latest version of virtualbox (6.1.14) on a type of Windows10
host and a type of Linux ubuntu v 19.10 guest 
I have a problem with the shared paper press and the drag and drop 
(In Bi-directionnel position)that don't work.
VBox Guest Additions Linux v 6.1.14 installed

Can you help me solve this problem?
Thanks.Regards.
KAT",KAT66
19901,Reopen #6650 closed on 08/14/2016,Linux,Linux,VirtualBox 6.1.14,2020-09-18T23:49:19Z,2020-09-18T23:49:19Z,"vbox-img --help documentation allows the `convert` command to output to stdout. This has been requested by forum users a few times in several forums. Mentioned 2010 ticket is just one user case. But this usage fails, as seen in log attached.
There seems to be an unjustified regression in the code, in `vbox-img.cpp`:797. The following line of code was withdrawn at changeset 33235 with commit message ""Storage/vbox-img: implement stdout handling"".

     {{{ AssertFailedReturn(VERR_NOT_SUPPORTED); }}}

However for some reason this line has been reintroduced later on.
I tested a custom build of vbox-img with the attached patch and the requested stdout handling worked well. Attached proposed patch against 6.1.14a code.
Alternatively, if this capability is still immature, revise the `--help` output and reopen #6650


",fabnicol
19905,"GUI glitches on Wayland running ""sudo virtualbox""",Linux,other,VirtualBox 6.1.14,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
19896,virtualbox 6.1.14 X Debian guest X keyboard X webcam X fullscreen VM,Linux,Linux,VirtualBox 6.1.14,2020-09-22T14:57:56Z,2020-09-22T14:57:56Z,"Hello

I found a very strange issue on Virtualbox 6.1.14 running on Ubuntu 18.04 host, Debian GNU/Linux bullseye (testing) guest using Gnome 3.30 desktop (or KDE Plasma 5.17) and a Logitech HD webcam C270 on fullscreen VM.

If enable webcam device on virtualbox toolbar, the keyboard is lost.

It also happens with Debian GNU/Linux 10.5 buster VM.

BUT this problem does not happen when using windowed VM.

What additional info should I collect?

Regards.

Andre Felipe",afmachado
19646,Windows XP Machine freeze,Windows,Windows,VirtualBox 6.1.10,2020-09-22T16:35:58Z,2020-09-22T16:35:58Z,"My XP machine always freezes without any visible reason. I tried a few things but don't know what to do now....

Please can you help me?

Best regards
Herbert",Herby_ITS
19793,VM Guest Windows-7 Freezes after loading Operating System,Windows,Windows,VirtualBox 6.1.10,2020-09-22T16:36:38Z,2020-09-22T16:36:38Z,"I have Laptop with this configuration AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx, 2100 Mhz, 4 Core(s), 8 Logical Processor(s) Installed Windows-10 on  it. Installed latest Virtual Box 6.1.12r Installed Windows-7 as VM guest frequently operating system crashes with in 2-3 days and need to get a new copy of it and observed that after load operating system VM freezes with no activity for 20-30 Min than starts responds. If I reboot laptop same issue reports. More issue in setting up Display settings adjustments. Can any one help me out it. 2 CPU's and 4 GB memory allocated.",Madhava
19911,Fresh VM always crashing due to RAM issue,Windows,Linux,VirtualBox 6.1.14,2020-09-23T08:31:44Z,2020-09-23T08:31:44Z,"Hey,

recently I built a new computer with 16 GB of DDR4 ram, a Ryzen 7 3700X and a Nvidia RTX 2060 Super. On my old one I never experienced any problems with Virtualbox but now any new VM I create crashes right after I reboot it after installation (Every driver I can think of is up-to-date). 

Of course I will supply more information if you need any. Maybe the log files can already help a lot with this problem.

Thanks in advance

PT400C",PT400C
19912,Host gnome topleft hot-corner doesn't work when VM is running and focused.,Linux,Windows,VirtualBox 6.1.14,2020-09-23T23:47:19Z,2020-09-23T23:47:19Z,"I use Virtualbox 6.1.14 r140239 on Debian 10.5 with an Nvidia driver and an Nvidia proprietary driver.When I opened a Win10 VM and had it focused,I am unable to use the topleft hot-corner action of Gnome desktop. 
In gnome,when moving cursor to the topleft corner,it works as if you clicked the 'Activities' button on the topleft.While when focusing on a Virtualbox Win10 VM,moving cursor to the topleft corner doesn't cause any reactive.
This bug does not only exist on Debian,but also on Arch.
There is another spotter of this bug:
https://www.reddit.com/r/gnome/comments/dhqxbg/topleft_hotcorner_not_working_when_virtualbox/",TyamaAROU
19913,linux guest processes terminated after win10 host sleep,Windows,Linux,VirtualBox 6.1.14,2020-09-24T14:48:43Z,2020-09-24T14:48:43Z,"(similar to https://www.virtualbox.org/ticket/19131)

Windows 10 1904 host
Ubuntu 20.04-LTS guest (created with 6.1.10 IIRC)
virtualbox-6.1.14 with 6.1.14 extension pack

situation occurs when host goes into sleep on its own (my power settings are set never to hibernate when on line power)

result:
- running apps and windows in guest are all exited
- docker containers are exited
- system uptime seems to be correct

in attached log, the situation likely occurred starting at ""07:39:12.135290"" as this delta from the log opened time corresponds to the time docker reports my container exited
",DanielH_
19914,guest display reacts very slowly,Mac OS X,Linux,VirtualBox 6.1.14,2020-09-24T21:01:35Z,2020-09-24T21:01:35Z,"Hello I want to run Debian Buster as guest on Mac OS X as host. Installation worked, but the guest display reacts very slowly and randers it unusable. When doing a SSH to the guest, I see that CPU usage is almost zero. Why is the display part broken?",kouros
19916,Android x_86 ISO have bugs and don't supprt persian hardware keyboards,all,all,VirtualBox 6.1.14,2020-09-25T13:47:14Z,2020-09-25T13:47:14Z,"Hi Innotek team,
This is the only way I can reach oy guys. The Android ISO project has some bugs related to language settings. In Android ISO the hardware and software keyboard for persian does not write Persian characters althought the Arabic keyboard does. Instead for writing text with Persian characters it still uses English characters. Please fix this bug in future releases. 
If this email is not relevant please tell me how to notify the related guys about this issue. 
Thanks",pakanangel
19099,openSUSE Leap 42.3 - cannot compile vboxsf module,all,Linux,VirtualBox 6.0.14,2020-09-25T18:24:02Z,2020-09-25T18:24:02Z,"Using the current 6.0.14 we cannot compile the shared folder module from the guest additions in the guest with a compile error and as such no shared folder functionality is available:

openSUSE Leap 42.3
Linux linux-ntkd 4.4.180-102-default #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a) x86_64 x86_64 x86_64 GNU/Linux

cat vboxadd-install.log
{{{
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 4.4.180-102-default.

VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what
went wrong
VirtualBox Guest Additions: modprobe vboxsf failed

cat vboxadd-setup.log
Installing X.Org Server 1.18 modules
}}}

### the service in general worked:
{{{
 systemctl status vboxadd-service.service
● vboxadd-service.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.0.14/init/vboxadd-service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2019-11-20 09:22:25 CET; 13min ago
    Tasks: 8 (limit: 512)
   CGroup: /system.slice/vboxadd-service.service
           └─1457 /usr/sbin/VBoxService --pidfile /var/run/vboxadd-service.sh
}}}

XXX but shared folder support does not work:
{{{
fbatschu@linux-ntkd:~> lsmod|grep vbox
vboxguest             368640  6

[    4.253318] vboxguest: misc device minor 57, IRQ 20, I/O port d040, MMIO at 00000000f2400000 (size 0x400000)
[    4.253319] vboxguest: Successfully loaded version 6.0.14 (interface 0x00010004)
[    4.258614] XFS (sda3): Ending clean mount
[    4.296429] systemd-journald[403]: Received request to flush runtime journal from PID 1
[    4.553802] snd_intel8x0 0000:00:05.0: white list rate for 1028:0177 is 48000
[    5.217573] No iBFT detected.
[    5.243033] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.353076] 08:22:25.818744 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
               08:22:25.818746 main     Log opened 2019-11-20T08:22:25.818741000Z
[    6.353107] 08:22:25.818807 main     OS Product: Linux
[    6.353121] 08:22:25.818824 main     OS Release: 4.4.180-102-default
[    6.353134] 08:22:25.818838 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
[    6.353157] 08:22:25.818855 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
               08:22:25.818855 main     Process ID: 1452
               08:22:25.818856 main     Package type: LINUX_64BITS_GENERIC
[    6.353791] 08:22:25.819485 main     6.0.14 r133895 started. Verbose level = 0
[    6.354534] 08:22:25.820219 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[    6.361318] 08:22:25.826993 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Downloads' on '/media/sf_Downloads': No such device (-1,19)
[    6.362301] 08:22:25.827991 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Music' on '/media/sf_Music': No such device (-1,19)
[    7.249769] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[    7.250592] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    7.371502] 08:22:26.837466 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Downloads' on '/media/sf_Downloads': No such device (-1,19)
[    7.381974] 08:22:26.847947 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Music' on '/media/sf_Music': No such device (-1,19)
[    7.643712] NET: Registered protocol family 17
[   23.841175] fuse init (API version 7.23)
[  529.556954] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  530.941517] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  548.804519] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  550.120040] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
}}}

### try to test this manually:
{{{
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin # VBoxControl sharedfolder list
Oracle VM VirtualBox Guest Additions Command Line Management Interface Version 6.0.14
(C) 2008-2019 Oracle Corporation
All rights reserved.

Shared Folder mappings (2):

01 - Downloads [idRoot=0 writable auto-mount host-icase]
02 - Music [idRoot=1 writable auto-mount host-icase]

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/sbin # ./VBoxService --enable-automount
08:44:57.202537 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
08:44:57.202545 main     Log opened 2019-11-20T08:44:57.202521000Z
08:44:57.202777 main     OS Product: Linux
08:44:57.202865 main     OS Release: 4.4.180-102-default
08:44:57.202935 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
08:44:57.203002 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
08:44:57.203004 main     Process ID: 3724
08:44:57.203006 main     Package type: LINUX_64BITS_GENERIC
08:44:57.209167 main     6.0.14 r133895 started. Verbose level = 0

[ 1356.851990] 08:44:57.202537 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
               08:44:57.202545 main     Log opened 2019-11-20T08:44:57.202521000Z
[ 1356.852141] 08:44:57.202777 main     OS Product: Linux
[ 1356.852213] 08:44:57.202865 main     OS Release: 4.4.180-102-default
[ 1356.852282] 08:44:57.202935 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
[ 1356.852371] 08:44:57.203002 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
               08:44:57.203004 main     Process ID: 3724
               08:44:57.203006 main     Package type: LINUX_64BITS_GENERIC
[ 1356.858567] 08:44:57.209167 main     6.0.14 r133895 started. Verbose level = 0
[ 1356.881822] 08:44:57.232459 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 1356.882025] 08:44:57.232708 main     Error: Failed to become guest control master: VERR_RESOURCE_BUSY
[ 1356.882273] 08:44:57.232954 main     Error: Service 'control' failed to initialize: VERR_RESOURCE_BUSY
[ 1356.882528] 08:44:57.233216 main     Session 0 is about to close ...
[ 1356.882548] 08:44:57.233241 main     Stopping all guest processes ...
[ 1356.882579] 08:44:57.233272 main     Closing all guest files ...
[ 1356.882631] 08:44:57.233292 main     Ended.

fbatschu@linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin> mount -v|grep vbox
fbatschu@linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin>

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/other # ./mount.vboxsf Downloads /mnt
./mount.vboxsf: mounting failed with the error: No such device
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/other # echo $?
1

mount(""Downloads"", ""/mnt"", ""vboxsf"", MS_NODEV, """") = -1 ENODEV (No such device)
write(2, ""./mount.vboxsf: mounting failed ""..., 46./mount.vboxsf: mounting failed with the error) = 46
write(2, "": No such device\n"", 17: No such device
)      = 17

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14 # find / -name vboxguest -ls
  1066    0 drwxr-xr-x   1 root     root          656 Oct 10 20:44 /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxguest
 13625    0 crw-rw----   1 vboxadd  root      10,  57 Nov 20 09:22 /dev/vboxguest
4026532203    0 dr-xr-xr-x   2 root     root            0 Nov 20 09:52 /proc/irq/20/vboxguest
 11526    0 drwxr-xr-x   2 root     root            0 Nov 20 09:22 /sys/bus/pci/drivers/vboxguest
 12374    0 drwxr-xr-x   3 root     root            0 Nov 20 09:22 /sys/devices/virtual/misc/vboxguest
 12377    0 lrwxrwxrwx   1 root     root            0 Nov 20 09:52 /sys/class/misc/vboxguest -> ../../devices/virtual/misc/vboxguest
 11450    0 drwxr-xr-x   7 root     root            0 Nov 20 09:22 /sys/module/vboxguest

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14 # find / -name vboxsf -ls
  1268    0 drwxr-xr-x   1 root     root          850 Oct 10 20:44 /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf
}}}

XXX see how the compilation of the vboxsf module fails:
{{{
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf # make
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.4.180-102-default/build M=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf SRCROOT=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -j2 modules
make[1]: Entering directory '/usr/src/linux-4.4.180-102-obj/x86_64/default'
make -C ../../../linux-4.4.180-102 O=/usr/src/linux-4.4.180-102-obj/x86_64/default/. modules
make -C /usr/src/linux-4.4.180-102-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.4.180-102 \
-f /usr/src/linux-4.4.180-102/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_versions ; rm -f /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_versions/*
make -f /usr/src/linux-4.4.180-102/scripts/Makefile.build obj=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.vfsmod.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(vfsmod)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_vfsmod.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.c
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.dirops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(dirops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_dirops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.c
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.o""; fi; fi;
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.lnkops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(lnkops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_lnkops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.c
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.o""; fi; fi;
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.regops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(regops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_regops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c: In function ‘vbsf_lock_user_pages’:
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 1 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct task_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 2 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 3 of ‘get_user_pages_unlocked’ makes pointer from integer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘struct page **’ but argument is of type ‘uintptr_t’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: declared here
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c: At top level:
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:3780:5: warning: initialization from incompatible pointer type [enabled by default]
     .direct_IO      = vbsf_direct_IO,
     ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:3780:5: warning: (near initialization for ‘vbsf_reg_aops.direct_IO’) [enabled by default]
/usr/src/linux-4.4.180-102/scripts/Makefile.build:278: recipe for target '/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.o' failed
make[4]: *** [/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.o""; fi; fi;
/usr/src/linux-4.4.180-102/Makefile:1462: recipe for target '_module_/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf' failed
make[3]: *** [_module_/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf] Error 2
Makefile:152: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-4.4.180-102-obj/x86_64/default'
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/Makefile-footer.gmk:111: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 2
}}}

XXX the error is around the usage of get_user_pages_unlocked()
{{{
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 2 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 3 of ‘get_user_pages_unlocked’ makes pointer from integer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);

In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘struct page **’ but argument is of type ‘uintptr_t’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
}}}
",Frank Batschulat (Oracle)
19920,/bin/ls: reading directory : Protocol error for asian fonts,Windows,Linux,VirtualBox 6.1.14,2020-09-26T09:37:26Z,2020-09-26T09:37:26Z,"On my Windows 10 host I am not able to 'ls' a directory with these Asian characters: 

HID_Miniport_Device_￿࿘낖彴.hid

These characters appear in the ProtableApps version of Mixxx.
This is my error message.

neo:~/PortableApps/MixxxPortable/Data/MixxxSettings$ ls controller
/bin/ls: reading directory 'controller': Protocol error

After I delete such files 'ls' works well again.",Frank Breitling
19922,Fedora 32 Workstation official ISO fails to install stating integrity problems,Windows,Linux,VirtualBox 6.1.14,2020-09-27T19:29:36Z,2020-09-27T19:29:36Z,"I download https://torrent.fedoraproject.org/torrents/Fedora-Workstation-Live-x86_64-32.torrent from https://torrent.fedoraproject.org/ . While torrent guarantees file isn't corrupt, I also check the file per vendor instructions.

 sha256sum -c Fedora-Workstation-32-1.6-x86_64-CHECKSUM
Fedora-Workstation-Live-x86_64-32-1.6.iso: OK

When I try to install this specific image, its media check stops at exactly 4.8% and suggests not to use this image. If you ignore (e.g. disable check), it doesn't succeed booting anyway.

Today, I installed VMWare Workstation Player 16 and amazingly, very same ISO passed every test and installed fine. I think I may have triggered a Virtualbox (or windows?) bug.",Ilgaz
19921,VirtualBox Version 6.1.14 r140239 (Qt5.6.2) will not work with Windows Preview,Windows,Windows,VirtualBox 6.1.14,2020-09-29T08:32:15Z,2020-09-29T08:32:15Z,"Edition	Windows 10 Pro Insider Preview
Version	2004
Installiert am	‎24.‎09.‎2020
Betriebssystembuild	20221.1000
Leistung	Windows Feature Experience Pack 120.22800.0.0
",DKKABG
19923,Mouse Middle-Scroll Click aborts Linux guest,Linux,Linux,VirtualBox 6.1.10,2020-09-30T06:32:13Z,2020-09-30T06:32:13Z,"On Linux host 20.04.1, using linux guest 20.04 
At random occurrence when I middle click or scrollwheel click (to open multiple tabs in firefox) the guest machine immediately aborts. Shows (Aborted) within Vbox machine list window

I think this has occured before years ago and needed some upgrade. I am unable to search the bugs or forum as I kept getting error mesages ""Unable to search at this time. Please check back in several minutes""
",FleddyFlinty
19925,"RTEXITCODE handleControlVM(HandlerArg *)"" at line 622 of file VBoxManageControlVM.cpp",other,other,VirtualBox 6.1.14,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
19933,Issues due to lost USB packets (control and bulk type transfers),Linux,Linux,VirtualBox 6.1.14,2020-10-02T23:48:14Z,2020-10-02T23:48:14Z,"Hi all,

I'm using the latest VirtualBox version under Kubuntu 18.04 LTS. I'm having errors when testing a software I've made in a VM running the same OS, but it makes no difference on other VMs running other Linux distributions. However, my software doesn't have issues when it is running on my native machine, no VMs involved. I even tested this on a different machine, and no issues whatsoever even after a few hours.

The history here is that this software controls a USB switcher, monitoring it continuously, ever 200ms (but that can be changed in the options). The USB switcher itself is based on the CP2130 from Silicon Labs. The software has all the kinks ironed, but it fails on a VirtualBox VM, which should not happen. This also happens, seemingly, irregardless of the version of VBox I have installed. I've recently updated to the latest version from the VirtualBox repository, but saw no differences. In fact, I've seen it fail catastrophically and even causing the device to reset (the software forces a reset if more than 10 errors occur) quite rapidly. More frequently, errors are due to lost control transfers, but can happen with bulk transfers as well.

To sort this out, I've decided to run traces with Wireshark, simultaneoulsy inside and outside the VM, monitoring the same connections essentially. I can conclude that there were some lost packets because I've seen errors reporting inside the VM pertaining to packets that simply were not matched to any packets caught outside the VM, which might mean that the request packet never went outside the VM to the USB host, and due to timeout, it generated a ENOENT response inside the VM, but not outside. I must add that responses that exceed 100ms are ruled out the the application.

I have the images proving the issue, the screenshots highlighting some of the packets and the traces taken inside and outside the VM.

Kind regards, Samuel Lourenço",bloguetronica
18583,building virtualbox without opengl on server without X11,Linux,other,VirtualBox 6.0.6,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
19934,Cannot create 64-bit VM with VirtualBox,other,Linux,VirtualBox 6.1.14,2020-10-03T22:04:20Z,2020-10-03T22:04:20Z,"I just got a brand-new computer, running Windows 10 Education. I try to create an Ubuntu 64-bit VM on VirtualBox 6.1.14, but only 32-bit options are available. I checked the BIOS to make sure SVM was enabled, and it already was. I made sure that Hyper-V was disabled, so there weren't two virtualization options available at the same time, but it already was. I've checked Google and Stack Exchange but I couldn't find anything else. Any help would be appreciated.",rochat
19928,VirtualBox hangs on shutdown,other,other,VirtualBox 6.1.14,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
19927,"Audio: garbled and hanging audio is caused by a ""bug"" in VirtualBox 5.x and up",Windows,other,VirtualBox 6.1.14,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
19545,"Regression related to shared folders, npm install",Mac OS X,Linux,VirtualBox 6.1.6,2020-10-05T09:04:34Z,2020-10-05T09:04:34Z,"After upgrading from 5.x to 6.x, I get the following error related to a shared filesystem when running npm install:

npm ERR! enoent ENOENT: no such file or directory, open '/home/kyle/share/devel/test/node_modules/argparse/node_modules/sprintf-js/package.json.226652263'
npm ERR! enoent This is related to npm not being able to find a file.

Steps to reproduce:

On the linux guest, in a shared folder:
  mkdir test
  cd test
  npm init -y
  npm install grunt --save-dev

On 5.x VB, I would see an error like this when I did not have guest symlinks properly enabled so I think it might be related to a problem with symlinks.  But I can create symlinks in 6.x from within the guest manually and they seem to work, at least from the command line.

I revert to VB 5.x and the problem goes away.  Unfortunately VB 5.x doesn't work on MacOS Catalina so trying to get this working under 6.x now.
",keb
19940,Nested Virtualization makes guest os freeze,Windows,Linux,VirtualBox 6.1.14,2020-10-05T13:57:58Z,2020-10-05T13:57:58Z,"I have the last version of virtualbox and I have Kali Linux virtual machine and I want to start android virtual machine on it and I have done the setup for everything and enabled Nested virtualization in virtualbox and installed kvm on guest os for acceleration but every time I try to start the emulator, It appears with the message:-


""Emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.""


and the guest os suddenly freezes totally and no longer responds.

My PC's CPU is Intel core I7-8750H (6 cores) and 16GB ram.
What is the problem? How can I solve it?",MINE
19554,Virtual machine closes unexpectingly,other,Linux,VirtualBox 6.1.6,2020-10-05T15:45:46Z,2020-10-05T15:45:46Z,"I use BirtualBox 6.1.6 r137129 (Qt5.6.1) under Linux Sabayon 64 bit (up to date) with KDE:

Operating System: Gentoo Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.4.0-sabayon
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7 CPU 920 @ 2.67GHz
Memory: 23,5 GiB of RAM

The guest is KDE Neon also up to date, for KDE development.

When I switch to KRDC, after an undetermined time, the guest is closed unexpectingly.

",----------
14269,Error relaunching VirtualBox VM process: 5,Windows,Linux,VirtualBox 5.1.8,2020-10-05T21:05:38Z,2020-10-05T21:05:38Z,Unable to run guest VM using latest OVM 5.0 release. See attached screenshot for details.,sombra
19941,virtualbox 6.1.14 on Ubuntu 20.04 (5.4.0-48-generic),other,other,VirtualBox 6.1.14,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
19943,"""Invalid Settings Detected"" System : Acceleration page",Windows,Linux,VirtualBox 6.1.14,2020-10-06T10:43:35Z,2020-10-06T10:43:35Z,"I tried to use ""old"" machine (created in previous versions of virtualbox) with the actual Virtualbox 6.1.14. But I got a problem described by other people

https://www.reddit.com/r/virtualbox/comments/efffap/i_have_a_problem_invalid_settings_detected/

https://www.reddit.com/r/virtualbox/comments/eig7f4/invalid_settings_detected/


It looks like there was a checkbox ""Enable VT-x|AMD-V"" in Settings>System>Acceleration in 6.0.x linked to the ""Invalid Settings Detected"" alert.

And it looks like in 6.1.x the checkbox was removed but the requirement to unset it was left somehow. 
",jekka
19944,SIGSEGV on poweron,other,other,VirtualBox 6.1.14,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
19947,Full Screen does not come up when using the latest version of Guest Additions,Windows,Linux,VirtualBox 6.1.14,2020-10-08T09:52:02Z,2020-10-08T09:52:02Z,"Hello! 

I am working with the https://images.apertis.org/release/v2021dev3/v2021dev3.0/amd64/sdk/apertis_v2021dev3-sdk-amd64-sdk_v2021dev3.0.vdi.gz SDK which is based on the Debian 10 Buster distribution. I tried to enable the full screen mode on the same SDK by installing the v6.1.14 guest additions from Oracle [https://download.virtualbox.org/virtualbox/6.1.14/]

After installing the same and on rebooting the SDK, it does not boot in the Full screen mode and instead the window shrinks. 

I also performed the same operations on the Debian_10.1.0_VirtualBox_Image_LinuxVMImages.ova image [https://www.linuxvmimages.com/images/debian-10/] 

The Debian VM starts with 6.0.14r133895 GA and fullscreen worked, then after upgrading to 6.1.14r140239 GA it is no more going to fullscreen
and it boots with a smaller screen.

I will attach the log files for the same. ",sagar123
17420,"Regression: Cannot compile VirtualBox 5.2.4 on Ubuntu 16.04, Qt5 not found",Linux,Linux,VirtualBox 5.2.4,2020-10-08T16:13:01Z,2020-10-08T16:13:01Z,"Even with the qt5 package installed on Ubuntu 16.04, the VirtualBox 5.2.4 configure script does not find Qt5. This is a regression since VirtualBox 5.1.",core-it-admin
19949,Some VirtualBox EFI Boot Menu entries do nothing when booting from ISO,Linux,Linux,VirtualBox 6.1.14,2020-10-08T19:51:51Z,2020-10-08T19:51:51Z,"Description:

With the exception of EFI Shell entry, none of the other choices in the EFI Boot Menu actually launch an EFI binary.  I've tried this with several different ISO images with the same result.  Usually, however, I can navigate using the EFI shell to the EFI binary and launch it manually.

Steps to reproduce (example):

(Using VirtualBox 6.1 on Devuan Ascii 2.1)
Download recent copy of Devuan ISO (devuan.org)
Create brand new EFI VM (with appropriate bitness)
""Insert"" the downloaded copy of Devuan ISO in the CD drive
Start the VM -- the EFI shell will appear
Exit the EFI Shell
Select the Boot Menu option in the EFI UI
Try to launch the entries in the Boot Menu (the EFI Shell entry will work; try others)

Expected Outcome:   Grub menu appears

Actual Outcome:  Nothing happens; the user is left in the EFI UI

Additional Information:

Adelie Linux (adelielinux.org) and Devuan experience this issue, regardless of 32 or 64 bitness, and regardless of which variation of these distros are used.  Other distros have not been tested for EFI install extensively.
",Harry M
19906,Black Screen after trying to log onto to Kali Linux,Linux,Linux,VirtualBox 6.1.14,2020-10-09T13:06:33Z,2020-10-09T13:06:33Z,"So recently I have been trying to log back into my Kali Linux virtual machine in virtual box. But so far, after I sign in to with my username and password , it cuts to a black screen. How do I fix this? I have screenshots inside that kali linux that I desperately need... 

Please help.. I tried to use some ways to fix it but I can't.. I desperately need that information before something happens to it.",MrFrank
19951,Can't boot from bootable USB and install window on freshly created Windows VM,Linux,Windows,VirtualBox 6.1.14,2020-10-09T17:22:31Z,2020-10-09T17:22:31Z,"1. I wasted an hour of my life downloading and creating an installable USB drive with Windows 10, using Microsoft's official tool.
2. In Virtual Box on a Linux host, I created a VM, chose Windows as the machine type, enabled the USB controller,
3. Then I plugged the physical Windows bootable USB drive into the host's physical USB port, and added that device to the VM
4. I powered on the VM and I was asked to choose whether to boot from a physical optical drive on the host, an ISO image simulating an optical drive, and I don't remember what other options, but there was no option to boot from the USB drive.

I should have that option. Now I have to start over and download a DVD ISO image and use that.",php4fan
19954,"after DISabling timesync in VB linux guest's GuestAdditions, boot errors: ""timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED"" ?",Linux,Linux,VirtualBox 6.1.14,2020-10-10T03:37:13Z,2020-10-10T03:37:13Z,"I run
{{{
rpm -qa | grep -i virtualbox
	VirtualBox-6.1-6.1.14_140239_fedora32-1.x86_64

uname -rm
	5.8.13-200.fc32.x86_64 x86_64
}}}

for both host & guests.

I've been having lots of time-sync issues in guests -- large drifts, time jumping forward & backwards, etc.

That's despite running chrony time sync clients in each guest.

After some digging, found this

	https://docs.oracle.com/en/virtualization/virtualbox/6.1/admin/fine-tune-timers.html#disabletimesync

and disabled timesync in clients' GuestAdditions, with
{{{
VBoxManage setextradata ""<vm name>"" ""VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled"" 1
}}}

Now, on guest reboot, I'm seeing these errors in guest dmesg log,
{{{
dmesg | egrep -i ""timesync|virtualbox""
	[    0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[    2.123518] usb 2-1: Manufacturer: VirtualBox
	[    2.134288] input: VirtualBox USB Tablet as /devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input5
	[    2.134476] hid-generic 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-0000:00:06.0-1/input0
	[   27.809171] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   27.809255] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   57.418443] 02:19:39.352350 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   66.602300] 02:19:49.375515 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   75.767563] 02:19:59.378440 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   84.932750] 02:20:09.381252 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   94.098285] 02:20:19.384482 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  103.264664] 02:20:29.388593 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  112.496162] 02:20:39.463769 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  121.658906] 02:20:49.463953 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  130.822255] 02:20:59.464766 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  139.985037] 02:21:09.464959 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
}}}

Clearly 'errors', not warnings ...

Either a bug, or add'l config is needed to fix/silence that^ ...",pgnd
19955,VirtualBox Manager crashes when opening,Windows,other,VirtualBox 6.1.14,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
17553,Une erreur critique est survenue pendant l'execution de la machine virtuelle,Windows,Windows,,2020-10-11T12:57:45Z,2020-10-11T12:57:45Z,"Hi!
after an update of the version ubuntu 17.04 and restart my virtual machine is not accessible anymore and a window appear containing this words "" Une erreur critique est survenue pendant l'execution de la machine virtuelle et cette derniere a été suspendue"" .
thanks",mohamed degaci
19958,I double click on Virtual Box and it does not open,other,other,VirtualBox 6.1.14,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
19960,Screen distorted Windows7 guest on Kubuntu 18.04 host,Linux,Windows,VirtualBox 6.1.14,2020-10-12T04:10:31Z,2020-10-12T04:10:31Z,"After upgrading to 6.1.12 found guest display distorted. Had to downgrade back to 6.1.10.
However, have now also found the same problem in 6.1.14 and 6.1.15.  --> see attached screenshots.
This is on Lenovo T430s running Kubuntu 18.04 as the host.
Guest: Windows7 Home Premium

The interesting thing is even after downgrading back to 6.1.10 the problem still appeared until Extension pack 6.1.10 was re-installed. - During installation screen flickered and reverted back to normal operation.",KarlS
19946,interrupt transfers stop working,Linux,Windows,VirtualBox 6.1.10,2020-10-12T06:01:20Z,2020-10-12T06:01:20Z,"After forwarding a SCM Microsystems, Inc. SCR331 SmartCard Reader USB device to the guest, it can at first be used normally. If it isn't used for a few seconds (no cards are inserted or removed, no interrupt responses are sent), interrupt handling stops working for the device. The reader can still be accessed (for example, if a card is inserted certutil can still read it), but further interrupts don't reach the guest (if no card was inserted, newly inserted cards are not noticed).

Running wireshark on both host and guest shows that on both host and guest an interrupt in request is sent out and after 5 seconds a response from the device is received. After that, the guest has no further traffic, but on the host, a SET FEATURE request is sent and a response received.

I have also seen this problem on an older modified virtualbox verion 5.1.38. I was unable to use wireshark in this configuration, but observed that in qemu-usb in file hcd-xhci.c, in function xhci_process_comands, in a switch on TBRType type, it falls into CR_STOP_ENDPOINT.",Cochimetl
19961,"Screen partially (upper portion) garbled after going to full screen (host: win10, guest: linux )",other,Linux,VirtualBox 6.1.14,2020-10-12T17:57:25Z,2020-10-12T17:57:25Z,"Maybe for half a year or so, I experience the partial garbling of 
upper portion of the screen when I go to full screen mode to a small er size. (I am attaching a screen capture.)

Problem here is
- sometimes (and quite often) no input is recognized in this state, but
- once I resize the window and going back to full screen size, the garbled area disappears, and I can continue operating the guest. So the VM did not crash.

My video card is NVIDIA GT 1030 if that matters, and I am using nvidia's latest driver.

I have come to experience this maybe for the last six months or something and not before. I have been using 6.0.12 and it seems the problem still persists with 6.0.14. The capture was taken 6.0.14.
",ci-zephyurus
19962,"Screen partially (upper portion) garbled after going to full screen (host: win10, guest: linux )",other,Linux,VirtualBox 6.1.14,2020-10-12T17:59:27Z,2020-10-12T17:59:27Z,"Maybe for half a year or so, I experience the partial garbling of 
upper portion of the screen when I go to full screen mode to a small er size. (I am attaching a screen capture.)

Problem here is
- sometimes (and quite often) no input is recognized in this state, but
- once I resize the window and going back to full screen size, the garbled area disappears, and I can continue operating the guest. So the VM did not crash.

My video card is NVIDIA GT 1030 if that matters, and I am using nvidia's latest driver.

I have come to experience this maybe for the last six months or something and not before. I have been using 6.0.12 and it seems the problem still persists with 6.0.14. The capture was taken 6.0.14.
",ci-zephyurus
19964,Address violation crash,other,other,VirtualBox 6.1.10,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
19965,Windows7 virtual machine stops,Windows,Windows,VirtualBox 6.1.14,2020-10-14T07:12:21Z,2020-10-14T07:12:21Z,"I tried to start Beckhoff plc in run mode, it has been running earlier in this VM. But now in this version i onlny come to this stop mode of the VM.",GoranP
19966,"OSx host, Swedish keyboard, win 10 guest wakes up with VK_LWIN depressed on resume",Mac OS X,Windows,VirtualBox 6.1.14,2020-10-14T07:41:35Z,2020-10-14T07:41:35Z,"For a while I have noticed that my Windows 10 guest wakes up after a resume with the keyboard in a weird state.

Today I installed KeyboardStateView.exe on the guest to see what the keyboard state is after a resume, and it seems that the guest wakes up with the left window key depressed. Pressing the left Command key will get it in sync again.

It behaves the same on both my MacBook Pro keyboard and an external Apple USB keyboard, both with Swedish layout.

I have suffered from this for several versions and I can't remember when I first noticed it.

After a reboot of the client the keyboard is not in this weird state, only after a suspend/resume cycle.

After some more experimenting it appears to be caused by pressing the left Command key+Q to suspend the client and quit VBox. The left Command key appears to be mapped as the left Windows key. If I instead use the right Command key+Q, which seems dead in the client, then this does not happen.

Not sure if this is a bug or not",Tipo
19970,memory could not be written error,other,other,VirtualBox 6.1.14,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
19968,File transfers to / from guest corrupted,Windows,Linux,VirtualBox 6.1.14,2020-10-15T18:02:39Z,2020-10-15T18:02:39Z,I have a Centos guest OS running on Win10 host. I am unable to reliably transfer files or perform a Yum update on the guest OS. With Yum update the checksums consistently fail - but always different values for the downloaded file. Mozilla FTP and WinSCP to the guest also fail. Makes no difference whether using bridged network or local host. Seems to occur on all VM's I have running. What can be causing this? Seems everything else runs ok.,VicK
19977,USB3 UASP SATA SSD support,Windows,Windows,VirtualBox 6.1.14,2020-10-17T17:43:27Z,2020-10-17T17:43:27Z,"Hi,

I connected my Usb 3 Sata Ssd Mx500 to the host. I can see UASP is supported and enabled in CrystalDisk Info, in Windows 10. However, it is not in the guest (same OS). I have of course installed Virtualbox extension pack.

The difference in speed is high: with CrystalDiskMark, I have around 320MB/s in guest and 450MB/s in host.

Workaround:
Mount the drive in guest. The benchmark shows similar result that in host.

This is a good improvement I think, but no a priority.

Env: Windows 10 in host/guest
Virtualbox 6.1.14 with guest additions in guest + extension pack.",myroad
19743,Hardening rejects DLL because of expired certificate nvldumdx.dll,Windows,Linux,VirtualBox 6.1.10,2020-10-18T10:05:42Z,2020-10-18T10:05:42Z,"Im using a Nvidia GTX960 video card and it seems like the driver loader dll gets rejected because of an expired certificate.

The thing is that nvldumdx.dll is signed 2 times:
1. by Nvidia SHA1  (expired cert, was valid from 2018-2019)
2. by Microsoft SHA256  (valid cert)

Since Nvidia releases the file like that, I assume it's ok that only one of the signatures is valid, which is the case. But VirtualBox complains about the expired cert in the hardening log and rejects the file.

(VBox and video drivers are both the most recent releases)

{{{
2bc0.d1c: supHardenedWinVerifyImageByHandle: -> -23033 (\Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll) WinVerifyTrust
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll: Certificate is not valid (ValidTime=2020-07-05T18:39:56.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll): rcNt=0xc0000190
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll'
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23033 (0xffffa607)) on \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):

}}}
",Peter B
19979,"Virtualbox 6.1.14 crashes on Windows 10 Home, 6.1.4 does not",Windows,Linux,VirtualBox 6.1.14,2020-10-18T17:04:31Z,2020-10-18T17:04:31Z,"I've been using 6.1.4 about 10 hours a day for 6 months on my Windows 10 Pro laptop, without *any* crashes (ok maybe once once but I'm not going to complain, awesome software). Recently I got a new laptop with Windows 10 Home and installed VirtualBox 6.1.14. VM crashed several times and behaved strangely, like Firefox in the VM would crash, or after being in ""screensave"" mode then login would crash and once re-logged in my apps would be gone I would have to restart them, that kind of stuff. I tried a few things, like upgrading Windows 10 to Pro, turning off audio etc. But the only that worked was to rollback to VirtualBox 6.1.4. I did not try 6.1.6, 8, 10 or 12, but clearly a bug got introduced in one of those or in 6.1.14.  ",schollii
19978,Crash reboot VM UEFI Windows Server,Windows,Windows,VirtualBox 6.1.14,2020-10-19T10:54:03Z,2020-10-19T10:54:03Z,"A VM configured for Windows Server 2019 UEFI with VM VirtualBox Extension Pack 6.1.14, hangs on reboot (random). Windows 10 2004 host. This problem has occurred since the first version 6.0.",tiagocoelho2
19919,6.1.14 BSOD when VM starts,other,other,VirtualBox 6.1.14,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
19976,Any types of VM cannot be started by hardenedwinrespawn,Windows,Windows,VirtualBox 6.1.14,2020-10-19T21:39:58Z,2020-10-19T21:39:58Z,"I was trying to create vms on my machine, I also enabled virtualization through bios, installed hyper-v (Just in case) on windows 10 home and also I did modified the owner of every hardrive to be my user, it seems it has problem with permission but i used administrator mode and gave all the acording permissions.",Valkiria
19981,"GNOME issue, Suspected but unsure",Windows,Linux,VirtualBox 6.1.14,2020-10-20T15:08:11Z,2020-10-20T15:08:11Z,the vm will start but not get past the command line.,eryktyler26
19982,Crash when using vscode on linux guest,Windows,Linux,VirtualBox 6.1.14,2020-10-20T17:19:14Z,2020-10-20T17:19:14Z,"Hello,

VB crashes when I use vscode on a linux ( Ubuntu ) guest. It crashes when I right click to display a menu.
I join the crash  logs and a copy of the error message ( ""memory state cannot be written"" ). Is this enough to start to debug or do you need more information ? 

Thanks !

Crash logs : 

151:19:24.402862 AIOMgr: Async flushes not supported
152:49:24.051989 
152:49:24.051991 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000004184!!!
152:49:24.053107 
152:49:24.053108 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffc189728c2
152:49:24.053118 ExceptionInformation[0]=0000000000000001
152:49:24.053124 ExceptionInformation[1]=0000000000000000
152:49:24.053128 
152:49:24.053129 cs:rip=0033:00007ffc189728c2
152:49:24.053149 ss:rsp=002b:00000000cacbf560 rbp=00000000cacbf610
152:49:24.053154 rax=00000000cdeb87c0 rcx=0000000000000000 rdx=0000000082751090 rbx=0000000082751070
152:49:24.053159 rsi=0000000219a24c00 rdi=0000000219a24c00 rsp=00000000cacbf560 rbp=00000000cacbf610
152:49:24.053165 r8 =0000000000000000 r9 =0000000082751450 r10=0000000000000000 r11=00000000cacbf6a0
152:49:24.053170 r12=000000026a000770 r13=0000000000000000 r14=000000026a000080 r15=00000000cd680f40
152:49:24.053175 ds=002b es=002b fs=0053 gs=002b eflags=00010206
152:49:24.053180 p1home=0000000000000000 p2home=0000000000000000 pe3home=0000000082751070
152:49:24.053185 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
152:49:24.053189    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
152:49:24.053194 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
152:49:24.053202 
152:49:24.053203 Stack 00000000cacbe440, dumping 0x1bc0 bytes (low=00000000cabc0000, high=00000000cacc0000)
152:49:24.054088 00000000cacbe440/0000: 40 e4 cb ca 00 00 00 00-73 74 61 63 6b 6d 61 72 @.......stackmar
152:49:24.054818 00000000cacbe450/0010: 6b 65 72 00 00 00 00 00-00 10 02 00 00 00 00 00 ker.............
152:49:24.054825 00000000cacbe460/0020: 00 00 00 00 00 00 00 00-80 d7 75 54 fc 7f 00 00 ..........uT....
152:49:24.054831 00000000cacbe470/0030: 01 00 00 00 00 00 00 00-ff ff ff ff ff ff ff ff ................
152:49:24.054839 00000000cacbe480/0040: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054845 00000000cacbe490/0050: d0 59 c2 fa fb 7f 00 00-50 f8 cb ca 00 00 00 00 .Y......P.......
152:49:24.054848 00000000cacbe4a0/0060: 00 00 00 00 00 00 00 00-aa 08 5f 54 fc 7f 00 00 .........._T....
152:49:24.054849 00000000cacbe4b0/0070: 40 e6 cb ca 00 00 00 00-c2 28 97 18 fc 7f 00 00 @........(......
152:49:24.054851 00000000cacbe4c0/0080: 00 00 cc ca 00 00 00 00-00 00 bc ca 00 00 00 00 ................
152:49:24.054852 00000000cacbe4d0/0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054854 00000000cacbe4e0/00a0: 06 00 00 00 04 00 00 00-00 00 00 00 01 00 00 00 ................
152:49:24.054855 00000000cacbe4f0/00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054857 00000000cacbe500/00c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054858 00000000cacbe510/00d0: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054860 00000000cacbe520/00e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054862 **************** ****  <ditto x 6>
152:49:24.054862 00000000cacbe590/0150: 25 f0 25 10 04 1a 00 00-00 00 00 00 00 00 00 00 %.%.............
152:49:24.054864 00000000cacbe5a0/0160: 00 00 b4 56 fc 7f 00 00-40 ec cb ca 00 00 00 00 ...V....@.......
152:49:24.054866 00000000cacbe5b0/0170: 50 f8 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 P...............
152:49:24.054868 00000000cacbe5c0/0180: 00 00 00 00 00 00 00 00-b2 4a be 56 fc 7f 00 00 .........J.V....
152:49:24.054869 00000000cacbe5d0/0190: 00 00 00 00 00 00 00 00-20 44 c8 56 fc 7f 00 00 ........ D.V....
152:49:24.054871 00000000cacbe5e0/01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054872 00000000cacbe5f0/01b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054882 00000000cacbe600/01c0: 51 ce 06 00 00 00 00 00-56 c6 bc 56 fc 7f 00 00 Q.......V..V....
152:49:24.054883 00000000cacbe610/01d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054885 00000000cacbe620/01e0: 08 ec cb ca 00 00 00 00-90 ec cb ca 00 00 00 00 ................
152:49:24.054886 00000000cacbe630/01f0: a4 0e c0 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054902 00000000cacbe640/0200: b0 f2 cb ca 00 00 00 00-c0 ed cb ca 00 00 00 00 ................
152:49:24.054903 00000000cacbe650/0210: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.054905 00000000cacbe660/0220: c0 ed cb ca 00 00 00 00-c0 c5 bc 56 fc 7f 00 00 ...........V....
152:49:24.054906 00000000cacbe670/0230: 00 00 00 00 00 00 00 00-cf 11 be 56 fc 7f 00 00 ...........V....
152:49:24.054908 00000000cacbe680/0240: 00 00 00 00 00 00 00 00-f0 eb cb ca 00 00 00 00 ................
152:49:24.054909 00000000cacbe690/0250: b0 f2 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.054924 00000000cacbe6a0/0260: 40 ec cb ca 00 00 00 00-09 a2 ba 56 fc 7f 00 00 @..........V....
152:49:24.054926 00000000cacbe6b0/0270: 01 00 00 00 00 00 00 00-00 00 b4 56 fc 7f 00 00 ...........V....
152:49:24.054928 00000000cacbe6c0/0280: 00 00 00 00 00 00 00 00-f0 e9 ca 56 fc 7f 00 00 ...........V....
152:49:24.054929 00000000cacbe6d0/0290: f0 e6 cb ca 00 00 00 00-10 ec cb ca 00 00 00 00 ................
152:49:24.054931 00000000cacbe6e0/02a0: 00 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054932 00000000cacbe6f0/02b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055264 **************** ****  <ditto x 2>
152:49:24.055266 00000000cacbe720/02e0: 0f 00 10 00 a0 1f 00 00-33 00 00 00 00 00 00 00 ........3.......
152:49:24.055268 00000000cacbe730/02f0: 00 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 ..+.............
152:49:24.055270 00000000cacbe740/0300: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055272 **************** ****  <ditto x 3>
152:49:24.055273 00000000cacbe780/0340: 00 00 00 00 00 00 00 00-d0 f8 cb ca 00 00 00 00 ................
152:49:24.055275 00000000cacbe790/0350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055276 **************** ****  <ditto x 5>
152:49:24.055277 00000000cacbe7f0/03b0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055279 00000000cacbe800/03c0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055280 00000000cacbe810/03d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055282 **************** ****  <ditto x 23>
152:49:24.055283 00000000cacbe990/0550: c0 ed cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055284 00000000cacbe9a0/0560: ff ff ff ff ff ff ff ff-00 00 00 00 00 00 00 00 ................
152:49:24.055286 00000000cacbe9b0/0570: 80 ea cb ca 00 00 00 00-2b 2e f3 15 f7 7f 00 00 ........+.......
152:49:24.055288 00000000cacbe9c0/0580: 40 94 fa 15 f7 7f 00 00-c0 eb cb ca 00 00 00 00 @...............
152:49:24.055290 00000000cacbe9d0/0590: c0 87 eb cd 00 00 00 00-70 10 75 82 00 00 00 00 ........p.u.....
152:49:24.055291 00000000cacbe9e0/05a0: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055293 00000000cacbe9f0/05b0: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055295 00000000cacbea00/05c0: 00 00 00 00 00 00 00 00-50 14 75 82 00 00 00 00 ........P.u.....
152:49:24.055296 00000000cacbea10/05d0: 00 00 00 00 00 00 00 00-a0 f6 cb ca 00 00 00 00 ................
152:49:24.055298 00000000cacbea20/05e0: 70 07 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 p..j............
152:49:24.055300 00000000cacbea30/05f0: 80 00 00 6a 02 00 00 00-40 0f 68 cd 00 00 00 00 ...j....@.h.....
152:49:24.055301 00000000cacbea40/0600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055303 00000000cacbea50/0610: c2 28 97 18 fc 7f 00 00-60 f5 cb ca 00 00 00 00 .(......`.......
152:49:24.055305 00000000cacbea60/0620: 10 f6 cb ca 00 00 00 00-5f 00 10 00 00 00 00 00 ........_.......
152:49:24.055306 00000000cacbea70/0630: 33 00 00 00 00 00 00 00-2b 00 00 00 00 00 00 00 3.......+.......
152:49:24.055308 00000000cacbea80/0640: 2b 00 00 00 37 66 66 63-2b 00 00 00 32 38 63 32 +...7ffc+...28c2
152:49:24.055310 00000000cacbea90/0650: 53 00 00 00 00 00 00 00-2b 00 00 00 fc 7f 00 00 S.......+.......
152:49:24.055311 00000000cacbeaa0/0660: 06 02 01 00 00 00 00 00-a0 1f 00 00 02 00 00 00 ................
152:49:24.055313 00000000cacbeab0/0670: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055314 **************** ****  <ditto x 7>
152:49:24.055315 00000000cacbeb30/06f0: 00 4c a2 19 02 00 00 00-d6 2f f3 15 f7 7f 00 00 .L......./......
152:49:24.055317 00000000cacbeb40/0700: 02 00 00 00 00 00 00 00-00 70 cf 00 00 00 00 00 .........p......
152:49:24.055318 00000000cacbeb50/0710: 20 97 fa 15 f7 7f 00 00-05 00 00 c0 00 00 00 00  ...............
152:49:24.055320 00000000cacbeb60/0720: 01 00 00 00 00 00 00 00-40 0f 68 cd 00 00 00 00 ........@.h.....
152:49:24.055322 00000000cacbeb70/0730: 80 00 00 6a 02 00 00 00-f2 ec b5 56 fc 7f 00 00 ...j.......V....
152:49:24.055323 00000000cacbeb80/0740: 70 07 00 6a 02 00 00 00-00 4c a2 19 02 00 00 00 p..j.....L......
152:49:24.055325 00000000cacbeb90/0750: b0 f2 cb ca 00 00 00 00-0b 00 10 00 00 00 00 00 ................
152:49:24.055327 00000000cacbeba0/0760: 10 00 00 00 00 00 00 00-dc a0 ba 56 fc 7f 00 00 ...........V....
152:49:24.055329 00000000cacbebb0/0770: 00 00 00 00 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.055330 00000000cacbebc0/0780: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055335 00000000cacbebd0/0790: 19 00 00 00 00 00 00 00-72 3a 20 30 78 63 30 30 ........r: 0xc00
152:49:24.055336 00000000cacbebe0/07a0: 30 30 30 30 35 20 28 30-30 30 30 30 30 30 30 30 00005 (000000000
152:49:24.055338 00000000cacbebf0/07b0: 00 30 30 30 30 30 31 2c-90 ec cb ca 00 00 00 00 .000001,........
152:49:24.055339 00000000cacbec00/07c0: 50 f8 cb ca 00 00 00 00-00 00 b4 56 fc 7f 00 00 P..........V....
152:49:24.055341 00000000cacbec10/07d0: 20 44 c8 56 fc 7f 00 00-00 00 00 00 00 00 00 00  D.V............
152:49:24.055343 00000000cacbec20/07e0: 00 00 cc ca 00 00 00 00-00 d0 cb ca 00 00 00 00 ................
152:49:24.055344 00000000cacbec30/07f0: c0 ed cb ca 00 00 00 00-80 51 9d 18 fc 7f 00 00 .........Q......
152:49:24.055346 00000000cacbec40/0800: 51 ce ba 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 Q..V.......V....
152:49:24.055348 00000000cacbec50/0810: f0 e9 ca 56 fc 7f 00 00-50 f8 cb ca 00 00 00 00 ...V....P.......
152:49:24.055349 00000000cacbec60/0820: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.055351 00000000cacbec70/0830: c0 c5 bc 56 fc 7f 00 00-20 44 c8 56 fc 7f 00 00 ...V.... D.V....
152:49:24.055352 00000000cacbec80/0840: 90 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055354 00000000cacbec90/0850: 0a 00 00 00 00 00 00 00-80 38 8f 18 fc 7f 00 00 .........8......
152:49:24.055355 00000000cacbeca0/0860: 78 ce ba 56 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x..V............
152:49:24.055357 00000000cacbecb0/0870: 80 4b a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .K..............
152:49:24.055358 00000000cacbecc0/0880: b0 48 a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .H..............
152:49:24.055360 00000000cacbecd0/0890: a4 0f a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055362 00000000cacbece0/08a0: 78 fc a2 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x...............
152:49:24.055363 00000000cacbecf0/08b0: b4 1d a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055365 00000000cacbed00/08c0: b8 1c a3 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055366 00000000cacbed10/08d0: d4 0e c0 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055368 00000000cacbed20/08e0: a4 0e c0 18 fc 7f 00 00-00 00 31 56 fc 7f 00 00 ..........1V....
152:49:24.055369 00000000cacbed30/08f0: d8 ac 3b 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 ..;V.......V....
152:49:24.055371 00000000cacbed40/0900: f0 e9 ca 56 fc 7f 00 00-08 c0 f3 15 f7 7f 00 00 ...V............
152:49:24.055373 00000000cacbed50/0910: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055374 00000000cacbed60/0920: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055376 00000000cacbed70/0930: e0 41 c3 4b 97 74 00 00-a0 f6 cb ca 00 00 00 00 .A.K.t..........
152:49:24.055377 00000000cacbed80/0940: 40 0f 68 cd 00 00 00 00-80 00 00 6a 02 00 00 00 @.h........j....
152:49:24.055379 00000000cacbed90/0950: 00 00 00 00 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055380 00000000cacbeda0/0960: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055382 00000000cacbedb0/0970: 10 f6 cb ca 00 00 00 00-3e fe bd 56 fc 7f 00 00 ........>..V....
152:49:24.055384 00000000cacbedc0/0980: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055385 00000000cacbedd0/0990: 70 10 75 82 00 00 00 00-00 00 00 00 00 00 00 00 p.u.............
152:49:24.055387 00000000cacbede0/09a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055388 00000000cacbedf0/09b0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
152:49:24.055390 00000000cacbee00/09c0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
152:49:24.055391 00000000cacbee10/09d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055393 00000000cacbee20/09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055396 00000000cacbee30/09f0: 00 00 00 00 00 00 00 00-c0 87 eb cd 00 00 00 00 ................
152:49:24.055398 00000000cacbee40/0a00: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055399 00000000cacbee50/0a10: 70 10 75 82 00 00 00 00-60 f5 cb ca 00 00 00 00 p.u.....`.......
152:49:24.055401 00000000cacbee60/0a20: 10 f6 cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055403 00000000cacbee70/0a30: 00 4c a2 19 02 00 00 00-00 00 00 00 00 00 00 00 .L..............
152:49:24.055404 00000000cacbee80/0a40: 50 14 75 82 00 00 00 00-00 00 00 00 00 00 00 00 P.u.............
152:49:24.055406 00000000cacbee90/0a50: a0 f6 cb ca 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055407 00000000cacbeea0/0a60: 00 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055409 00000000cacbeeb0/0a70: 40 0f 68 cd 00 00 00 00-c2 28 97 18 fc 7f 00 00 @.h......(......
152:49:24.055410 00000000cacbeec0/0a80: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055412 00000000cacbeed0/0a90: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055413 00000000cacbeee0/0aa0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055415 **************** ****  <ditto x 58>
152:49:24.055416 00000000cacbf290/0e50: 30 fb ff ff a0 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055417 00000000cacbf2a0/0e60: f0 00 00 00 e0 01 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055419 00000000cacbf2b0/0e70: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055421 00000000cacbf2c0/0e80: c2 28 97 18 fc 7f 00 00-02 00 00 00 00 00 00 00 .(..............
152:49:24.055422 00000000cacbf2d0/0e90: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055438 00000000cacbf2e0/0ea0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055440 **************** ****  <ditto x 5>
152:49:24.055440 00000000cacbf340/0f00: 00 00 00 00 00 00 00 00-c6 2b 97 18 fc 7f 00 00 .........+......
152:49:24.055442 00000000cacbf350/0f10: c2 28 97 18 fc 7f 00 00-00 00 00 00 00 00 00 00 .(..............
152:49:24.055443 00000000cacbf360/0f20: 00 00 00 00 00 00 00 00-60 f5 cb ca 00 00 00 00 ........`.......
152:49:24.055445 00000000cacbf370/0f30: f8 37 00 6a 02 00 00 00-87 c9 9a 18 fc 7f 00 00 .7.j............
152:49:24.055446 00000000cacbf380/0f40: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
152:49:24.055448 00000000cacbf390/0f50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055449 **************** ****  <ditto x 2>
152:49:24.055450 00000000cacbf3c0/0f80: 00 82 2f 7c 00 00 00 00-00 00 00 00 02 00 00 00 ../|............
152:49:24.055451 00000000cacbf3d0/0f90: 00 01 00 00 00 00 00 00-c0 81 2f 7c 00 00 00 00 ........../|....
152:49:24.055453 00000000cacbf3e0/0fa0: 17 03 00 00 00 00 00 00-1e 00 00 00 e0 01 00 00 ................
152:49:24.055455 00000000cacbf3f0/0fb0: 17 03 00 00 00 00 00 00-00 00 00 00 17 03 00 00 ................
152:49:24.055456 00000000cacbf400/0fc0: 17 03 00 00 00 00 00 00-00 02 00 00 00 00 00 00 ................
152:49:24.055458 00000000cacbf410/0fd0: 80 79 72 64 02 00 00 00-80 00 00 6a 02 00 00 00 .yrd.......j....
152:49:24.055459 00000000cacbf420/0fe0: 00 00 00 00 01 00 00 00-00 00 00 00 00 02 00 00 ................
152:49:24.055461 00000000cacbf430/0ff0: 00 00 00 00 00 00 00 00-b0 50 3e 44 02 00 00 00 .........P>D....
152:49:24.055462 00000000cacbf440/1000: 50 b2 49 6a 02 00 00 00-a9 57 92 18 fc 7f 00 00 P.Ij.....W......
152:49:24.055464 00000000cacbf450/1010: 10 f6 cb ca 00 00 00 00-b0 f5 cb ca 00 00 00 00 ................
152:49:24.055465 00000000cacbf460/1020: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055467 00000000cacbf470/1030: 00 00 f0 41 00 c0 45 44-00 00 80 3f 00 00 80 3f ...A..ED...?...?
152:49:24.055469 00000000cacbf480/1040: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055473 00000000cacbf490/1050: 28 31 00 6a 02 00 00 00-00 00 80 3f 00 00 80 3f (1.j.......?...?
152:49:24.055488 00000000cacbf4a0/1060: 00 00 00 00 00 c0 45 44-00 00 00 00 00 00 00 00 ......ED........
152:49:24.055490 00000000cacbf4b0/1070: 00 00 00 00 00 00 00 00-00 00 80 3f 00 00 80 3f ...........?...?
152:49:24.055491 00000000cacbf4c0/1080: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055493 00000000cacbf4d0/1090: 32 ac a9 1f bb e0 00 00-00 00 00 00 00 00 00 00 2...............
152:49:24.055497 00000000cacbf4e0/10a0: d2 ab a9 1f bb e0 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055500 00000000cacbf4f0/10b0: 00 00 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055504 00000000cacbf500/10c0: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055509 00000000cacbf510/10d0: 04 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055512 00000000cacbf520/10e0: 30 f6 cb ca 00 00 00 00-00 da 9a 18 fc 7f 00 00 0...............
152:49:24.055519 00000000cacbf530/10f0: 80 00 00 6a 02 00 00 00-28 f7 cb ca 00 00 00 00 ...j....(.......
152:49:24.055523 00000000cacbf540/1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055526 00000000cacbf550/1110: 00 00 00 00 00 00 00 00-40 f8 95 18 fc 7f 00 00 ........@.......
152:49:24.055529 00000000cacbf560/1120: 00 00 00 00 00 00 00 00-68 95 d0 cb 00 00 00 00 ........h.......
152:49:24.055533 00000000cacbf570/1130: 01 00 00 00 01 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055536 00000000cacbf580/1140: 80 00 00 6a 02 00 00 00-df 06 97 18 fc 7f 00 00 ...j............
152:49:24.055540 00000000cacbf590/1150: 00 00 00 00 02 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055543 00000000cacbf5a0/1160: 80 4b 6c 64 02 00 00 00-b0 50 3e 44 02 00 00 00 .Kld.....P>D....
152:49:24.055546 00000000cacbf5b0/1170: b0 50 3e 44 02 00 00 00-00 00 00 00 00 00 00 00 .P>D............
152:49:24.055549 00000000cacbf5c0/1180: 00 00 00 00 00 00 00 00-00 f6 cb ca 00 00 00 00 ................
152:49:24.055553 00000000cacbf5d0/1190: 80 4b 6c 64 02 00 00 00-00 00 00 00 00 00 00 00 .Kld............
152:49:24.055556 00000000cacbf5e0/11a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055560 00000000cacbf5f0/11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055563 00000000cacbf600/11c0: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055564 00000000cacbf610/11d0: 00 00 00 00 00 00 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055566 00000000cacbf620/11e0: 70 07 00 6a 02 00 00 00-03 00 00 00 00 00 00 00 p..j............
152:49:24.055568 00000000cacbf630/11f0: 00 00 00 00 00 00 00 00-b0 4b ef 7b 00 00 00 00 .........K.{....
152:49:24.055569 00000000cacbf640/1200: b8 0b 00 00 00 00 00 00-ed 1b 91 18 fc 7f 00 00 ................
152:49:24.055571 00000000cacbf650/1210: b0 4b ef 7b 00 00 00 00-00 00 00 00 00 00 00 00 .K.{............
152:49:24.055573 00000000cacbf660/1220: 04 00 00 7a 00 00 00 01-01 00 00 00 00 00 00 00 ...z............
152:49:24.055574 00000000cacbf670/1230: 00 00 00 00 00 00 00 00-04 00 00 7a 98 04 00 01 ...........z....
152:49:24.055576 00000000cacbf680/1240: 60 00 00 00 00 00 00 00-5c 99 dc cb 00 00 00 00 `.......\.......
152:49:24.055577 00000000cacbf690/1250: 00 00 8e 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055579 00000000cacbf6a0/1260: 80 00 00 6a 02 00 00 00-79 3a 8f 18 fc 7f 00 00 ...j....y:......
152:49:24.055580 00000000cacbf6b0/1270: b0 4b ef 7b 00 00 00 00-04 00 00 00 00 00 00 00 .K.{............
152:49:24.055582 00000000cacbf6c0/1280: d8 65 91 26 02 00 00 00-38 cf 8a 19 02 00 00 00 .e.&....8.......
152:49:24.055583 00000000cacbf6d0/1290: a0 f7 cb ca 00 00 00 00-7c 91 92 18 fc 7f 00 00 ........|.......
152:49:24.055585 00000000cacbf6e0/12a0: 04 00 00 00 00 00 00 00-04 00 00 00 00 00 00 00 ................
152:49:24.055586 00000000cacbf6f0/12b0: 80 00 00 6a 02 00 00 00-17 53 90 18 fc 7f 00 00 ...j.....S......
152:49:24.055591 00000000cacbf700/12c0: 88 14 00 6a 02 00 00 00-6f 7e 92 18 fc 7f 00 00 ...j....o~......
152:49:24.055593 00000000cacbf710/12d0: 80 00 00 6a 02 00 00 00-80 00 00 6a 02 00 00 00 ...j.......j....
152:49:24.055594 00000000cacbf720/12e0: 98 14 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055596 00000000cacbf730/12f0: f0 43 3e 44 02 00 00 00-88 14 00 6a 02 00 00 00 .C>D.......j....
152:49:24.055598 00000000cacbf740/1300: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055599 00000000cacbf750/1310: 5c 99 dc cb 00 00 00 00-d0 95 dc cb 00 00 00 00 \...............
152:49:24.055601 00000000cacbf760/1320: 01 00 00 00 00 00 00 00-60 90 d0 cb 00 00 00 00 ........`.......
152:49:24.055602 00000000cacbf770/1330: 8c 03 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055604 00000000cacbf780/1340: 00 00 00 00 00 00 00 00-c6 53 b7 18 fc 7f 00 00 .........S......
152:49:24.055605 00000000cacbf790/1350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055607 00000000cacbf7a0/1360: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055608 00000000cacbf7b0/1370: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055610 **************** ****  <ditto x 2>
152:49:24.055610 00000000cacbf7e0/13a0: 01 00 00 00 00 00 00 00-a3 4f b7 18 fc 7f 00 00 .........O......
152:49:24.055612 00000000cacbf7f0/13b0: 60 90 d0 cb 00 00 00 00-00 00 00 00 00 00 00 00 `...............
152:49:24.055614 00000000cacbf800/13c0: 00 00 a4 18 fc 7f 00 00-1c 19 00 00 00 00 00 00 ................
152:49:24.055615 00000000cacbf810/13d0: 00 00 00 00 00 00 00 00-d4 7b 32 56 fc 7f 00 00 .........{2V....
152:49:24.055617 00000000cacbf820/13e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055618 00000000cacbf830/13f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055620 00000000cacbf840/1400: 00 00 00 00 00 00 00 00-51 ce ba 56 fc 7f 00 00 ........Q..V....
152:49:24.055621 00000000cacbf850/1410: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055623 **************** ****  <ditto x 2>
152:49:24.055623 00000000cacbf880/1440: 00 00 00 00 1e 91 8b 62-00 00 00 00 00 00 00 00 .......b........
152:49:24.055625 00000000cacbf890/1450: 00 00 00 00 00 00 00 00-c0 06 5f 54 fc 7f 00 00 .........._T....
152:49:24.055626 00000000cacbf8a0/1460: 40 e6 cb ca 00 00 00 00-f0 ff 01 00 78 5f 52 db @...........x_R.
152:49:24.055628 00000000cacbf8b0/1470: de 97 d4 36 fc 7f 00 00-40 e6 cb ca 00 00 00 00 ...6....@.......
152:49:24.055629 00000000cacbf8c0/1480: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055632 **************** ****  <ditto x 114>
152:49:24.055632 00000000cacbfff0/1bb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055881 Thread ID:   0000000000004184
152:49:24.055891 Thread name: <NULL>
152:49:24.055896 Thread IPRT: 0000000000000000
152:49:24.055901 
152:49:24.055901 Loaded Modules:
152:49:24.055901 Address range                    [*] Timestamp Path
152:49:24.055907 00007ff715f30000..00007ff716045fff   5f51ed66  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
152:49:24.055914 00007ffc56b40000..00007ffc56d2ffff   b5beef21  C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.055920 00007ffc56310000..00007ffc563c1fff   53a32b86  C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.055926 00007ffc544f0000..00007ffc54794fff   1b835a75  C:\WINDOWS\System32\KERNELBASE.dll
152:49:24.055932 00007ffc2f520000..00007ffc2f524fff   5f51ecdc  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
152:49:24.055937 00007ffc54410000..00007ffc5446bfff   ad0f5fb3  C:\WINDOWS\System32\Wintrust.dll
152:49:24.055943 00007ffc56560000..00007ffc565fdfff   f5bdefd7  C:\WINDOWS\System32\msvcrt.dll
152:49:24.055949 00007ffc53a90000..00007ffc53aa1fff   e4c2641f  C:\WINDOWS\System32\MSASN1.dll
152:49:24.055954 00007ffc548d0000..00007ffc54a18fff   0e128cc8  C:\WINDOWS\System32\CRYPT32.dll
152:49:24.055960 00007ffc547d0000..00007ffc548c9fff   32a6df9a  C:\WINDOWS\System32\ucrtbase.dll
152:49:24.055966 00007ffc55970000..00007ffc55a8ffff   ee94cb53  C:\WINDOWS\System32\RPCRT4.dll
152:49:24.055971 00007ffc547a0000..00007ffc547c5fff   b59ada57  C:\WINDOWS\System32\bcrypt.dll
152:49:24.055984 00007ffc54470000..00007ffc544effff   bf9ade76  C:\WINDOWS\System32\bcryptprimitives.dll
152:49:24.055990 00007ffc543f0000..00007ffc54406fff   a51023f1  C:\WINDOWS\System32\CRYPTSP.dll
152:49:24.055996 00007ffc526e0000..00007ffc52712fff   fa3c3542  C:\WINDOWS\system32\rsaenh.dll
152:49:24.056001 00007ffc52d40000..00007ffc52d4bfff   fef011a6  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
152:49:24.056007 00007ffc56540000..00007ffc5655cfff   13bffc39  C:\WINDOWS\System32\imagehlp.dll
152:49:24.056013 00007ffc54ce0000..00007ffc54d76fff   f222d51c  C:\WINDOWS\System32\sechost.dll
152:49:24.056018 00007ffc51900000..00007ffc51921fff   0ab6ed3a  C:\WINDOWS\SYSTEM32\gpapi.dll
152:49:24.056024 00007ffc53a60000..00007ffc53a82fff   ca538c5d  C:\WINDOWS\System32\profapi.dll
152:49:24.056030 00007ffc52240000..00007ffc5226efff   b35f039c  C:\WINDOWS\System32\cryptnet.dll
152:49:24.056049 00007ffc54d80000..00007ffc54e22fff   502aaa11  C:\WINDOWS\System32\advapi32.dll
152:49:24.056055 00007ffbfaab0000..00007ffbfb08ffff   5f51ed67  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
152:49:24.056061 00007ffc55880000..00007ffc558eefff   50866107  C:\WINDOWS\System32\WS2_32.dll
152:49:24.056066 00000000502b0000..0000000050381fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
152:49:24.056072 0000000050210000..00000000502a7fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
152:49:24.056077 00007ffbf6a50000..00007ffbf6c17fff   5f51ed81  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
152:49:24.056083 00007ffc550b0000..00007ffc55244fff   57629574  C:\WINDOWS\System32\USER32.dll
152:49:24.056088 00007ffc54bc0000..00007ffc54be0fff   5343f4fb  C:\WINDOWS\System32\win32u.dll
152:49:24.056093 00007ffc563d0000..00007ffc563f5fff   90b22122  C:\WINDOWS\System32\GDI32.dll
152:49:24.056098 00007ffc53ad0000..00007ffc53c65fff   7ea30dec  C:\WINDOWS\System32\gdi32full.dll
152:49:24.056104 00007ffc54a20000..00007ffc54abdfff   2085286c  C:\WINDOWS\System32\msvcp_win.dll
152:49:24.056109 00007ffc56600000..00007ffc56756fff   3340c819  C:\WINDOWS\System32\ole32.dll
152:49:24.056114 00007ffc567c0000..00007ffc56af4fff   8349657a  C:\WINDOWS\System32\combase.dll
152:49:24.056119 00007ffc557b0000..00007ffc55874fff   6ac977e7  C:\WINDOWS\System32\OLEAUT32.dll
152:49:24.056126 00007ffc25480000..00007ffc255d5fff   c7cf39ed  C:\WINDOWS\SYSTEM32\OPENGL32.dll
152:49:24.056132 00007ffbf8790000..00007ffbfaaa6fff   5f51ed79  C:\Program Files\Oracle\VirtualBox\UICommon.dll
152:49:24.056137 0000000077a90000..0000000077ff4fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
152:49:24.056142 00007ffc55a90000..00007ffc56176fff   37e737cc  C:\WINDOWS\System32\SHELL32.dll
152:49:24.056148 00007ffc54ac0000..00007ffc54b09fff   afaaabaa  C:\WINDOWS\System32\cfgmgr32.dll
152:49:24.056153 00007ffc54bf0000..00007ffc54c98fff   bd8b0e7d  C:\WINDOWS\System32\shcore.dll
152:49:24.056158 00007ffc53c70000..00007ffc543effff   a8db3b62  C:\WINDOWS\System32\windows.storage.dll
152:49:24.056163 00007ffc53a10000..00007ffc53a59fff   fdc4588a  C:\WINDOWS\System32\powrprof.dll
152:49:24.056169 00007ffc53a00000..00007ffc53a0ffff   a2ccd413  C:\WINDOWS\System32\UMPDC.dll
152:49:24.056174 00007ffc562b0000..00007ffc56301fff   f8807ba1  C:\WINDOWS\System32\shlwapi.dll
152:49:24.056179 00007ffc53ab0000..00007ffc53ac0fff   05bef372  C:\WINDOWS\System32\kernel.appcore.dll
152:49:24.056184 00007ffbf8190000..00007ffbf8786fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
152:49:24.056190 0000000077520000..0000000077a80fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
152:49:24.056195 00000000501b0000..0000000050203fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
152:49:24.056200 00007ffc4d690000..00007ffc4d6b3fff   d238be3c  C:\WINDOWS\SYSTEM32\WINMM.dll
152:49:24.056205 00007ffc25450000..00007ffc2547bfff   f93070ee  C:\WINDOWS\SYSTEM32\GLU32.dll
152:49:24.056211 00007ffc2ba80000..00007ffc2ba9afff   57b24d2b  C:\WINDOWS\SYSTEM32\MPR.dll
152:49:24.056216 00007ffc4d660000..00007ffc4d68cfff   d6bb9be2  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
152:49:24.056221 00007ffc51950000..00007ffc5196ffff   bc0e8e8e  C:\WINDOWS\SYSTEM32\dxcore.dll
152:49:24.056227 00007ffc54cb0000..00007ffc54cddfff   4be57136  C:\WINDOWS\System32\IMM32.DLL
152:49:24.056232 00007ffbf8060000..00007ffbf818dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
152:49:24.056237 00007ffc509e0000..00007ffc50a78fff   6eb90ac0  C:\WINDOWS\system32\uxtheme.dll
152:49:24.056242 00007ffc538e0000..00007ffc53904fff   dbb466d6  C:\WINDOWS\system32\userenv.dll
152:49:24.056248 00007ffc56200000..00007ffc562a1fff   9506208f  C:\WINDOWS\System32\clbcatq.dll
152:49:24.056253 00007ffbf7bb0000..00007ffbf7f6ffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
152:49:24.056258 00007ffbf7f70000..00007ffbf805efff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
152:49:24.056264 00007ffc56400000..00007ffc56534fff   8776e62f  C:\WINDOWS\System32\MSCTF.dll
152:49:24.056269 00007ffc26a40000..00007ffc26a79fff   5c8c75fa  C:\WINDOWS\system32\dataexchange.dll
152:49:24.056274 00007ffc4ca70000..00007ffc4cccafff   7e72d1cb  C:\WINDOWS\system32\d3d11.dll
152:49:24.056280 00007ffc4ccd0000..00007ffc4ceacfff   2ba0a53f  C:\WINDOWS\system32\dcomp.dll
152:49:24.056285 00007ffc51a10000..00007ffc51afafff   4029f10d  C:\WINDOWS\system32\dxgi.dll
152:49:24.056290 00007ffc50ad0000..00007ffc50d31fff   eeb9f7a6  C:\WINDOWS\system32\twinapi.appcore.dll
152:49:24.056296 00007ffc50f10000..00007ffc50f38fff   5be0eb17  C:\WINDOWS\system32\RMCLIENT.dll
152:49:24.056301 00007ffc41fd0000..00007ffc4206dfff   66a372e8  C:\WINDOWS\System32\TextInputFramework.dll
152:49:24.056306 00007ffc4a6f0000..00007ffc4aa19fff   d02b205d  C:\WINDOWS\System32\CoreUIComponents.dll
152:49:24.056312 00007ffc4ceb0000..00007ffc4cf83fff   99046ad7  C:\WINDOWS\System32\CoreMessaging.dll
152:49:24.056317 00007ffc53450000..00007ffc53480fff   d95e6299  C:\WINDOWS\SYSTEM32\ntmarta.dll
152:49:24.056322 00007ffc4b1d0000..00007ffc4b322fff   571c81a7  C:\WINDOWS\SYSTEM32\wintypes.dll
152:49:24.056327 00007ffc40a70000..00007ffc40d15fff   156c7509  C:\WINDOWS\System32\iertutil.dll
152:49:24.056333 00007ffc3e0f0000..00007ffc3e100fff   6e82a406  C:\WINDOWS\system32\wbem\wbemprox.dll
152:49:24.056339 00007ffc3eb30000..00007ffc3ebb3fff   6af5c06d  C:\WINDOWS\SYSTEM32\wbemcomn.dll
152:49:24.056345 00007ffc3d770000..00007ffc3d783fff   f9651a38  C:\WINDOWS\system32\wbem\wbemsvc.dll
152:49:24.056350 00007ffc3d890000..00007ffc3d990fff   65ead981  C:\WINDOWS\system32\wbem\fastprox.dll
152:49:24.056356 00007ffc33850000..00007ffc33864fff   b26a0aaf  C:\WINDOWS\System32\amsi.dll
152:49:24.056361 00007ffc31bd0000..00007ffc31c48fff   c930d9ac  C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2009.7-0\MpOav.dll
152:49:24.056367 00007ffc47f20000..00007ffc47f29fff   927b71e6  C:\WINDOWS\system32\version.dll
152:49:24.056372 00007ffbf66d0000..00007ffbf6a4dfff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
152:49:24.056378 00007ffc534b0000..00007ffc534bffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
152:49:24.056383 00007ffc534a0000..00007ffc534acfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
152:49:24.056389 00007ffbf5ce0000..00007ffbf66c5fff   5f51ef9a  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
152:49:24.056394 00007ffc55340000..00007ffc557affff   a7d94c0a  C:\WINDOWS\System32\SETUPAPI.dll
152:49:24.056400 00007ffbf7b40000..00007ffbf7ba6fff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
152:49:24.056405 00007ffbf5480000..00007ffbf5cdbfff   5f51ef98  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
152:49:24.056411 00007ffc52880000..00007ffc528b9fff   50afe730  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
152:49:24.056416 00007ffc2f500000..00007ffc2f513fff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
152:49:24.056421 00007ffc53490000..00007ffc5349bfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
152:49:24.056427 00007ffc14a70000..00007ffc14a7cfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
152:49:24.056433 00007ffc4b100000..00007ffc4b10afff   3f83c149  C:\WINDOWS\SYSTEM32\WINNSI.DLL
152:49:24.056438 00007ffc55960000..00007ffc55967fff   76a581c8  C:\WINDOWS\System32\NSI.dll
152:49:24.056443 00007ffc4ab20000..00007ffc4ab35fff   1c3a0614  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
152:49:24.056448 00007ffc4ab00000..00007ffc4ab1bfff   3c1facb4  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
152:49:24.056454 00007ffc528c0000..00007ffc5298afff   6d09021f  C:\WINDOWS\SYSTEM32\DNSAPI.dll
152:49:24.056459 00007ffc426e0000..00007ffc42751fff   1626851d  C:\WINDOWS\System32\MMDevApi.dll
152:49:24.056464 00007ffc537f0000..00007ffc53819fff   73cca382  C:\WINDOWS\System32\DEVOBJ.dll
152:49:24.056470 00007ffc1fa50000..00007ffc1fae8fff   0f4dfe70  C:\WINDOWS\System32\dsound.dll
152:49:24.056509 00007ffc3ff90000..00007ffc400ecfff   7e935799  C:\WINDOWS\System32\AUDIOSES.DLL
152:49:24.056523 00007ffc18d80000..00007ffc18dc3fff   2c6931f6  C:\WINDOWS\System32\wdmaud.drv
152:49:24.056536 00007ffc2f8c0000..00007ffc2f8c8fff   9b72df6f  C:\WINDOWS\SYSTEM32\ksuser.dll
152:49:24.056546 00007ffc4ad50000..00007ffc4ad59fff   f97bfee2  C:\WINDOWS\SYSTEM32\AVRT.dll
152:49:24.056555 00007ffc2e910000..00007ffc2e91cfff   4d3c7e92  C:\WINDOWS\System32\msacm32.drv
152:49:24.056564 00007ffc2ded0000..00007ffc2deebfff   6a4add8d  C:\WINDOWS\SYSTEM32\MSACM32.dll
152:49:24.056574 00007ffc2e730000..00007ffc2e739fff   5a70c191  C:\WINDOWS\System32\midimap.dll
152:49:24.056583 00007ffc18a40000..00007ffc18c06fff   c808fce5  C:\WINDOWS\system32\d3d9.dll
152:49:24.056592 00007ffc50e30000..00007ffc50e5cfff   7cd7bb0f  C:\WINDOWS\SYSTEM32\dwmapi.dll
152:49:24.056602 00007ffc188e0000..00007ffc18a3cfff*  5eb1b78e  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056615 00007ffc14fd0000..00007ffc188d8fff   5eb1b648  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igd9dxva64.dll
152:49:24.056630 00007ffc451c0000..00007ffc45363fff   5eb1b356  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdgmm64.dll
152:49:24.056643 00007ffc51e70000..00007ffc51e95fff   5eb1b301  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdinfo64.dll
152:49:24.056659 00007ffc42bb0000..00007ffc451b3fff   5eb1b815  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igc64.dll
152:49:24.056677 00007ffc4bba0000..00007ffc4bc8ffff   e593a459  C:\Windows\System32\PROPSYS.dll
152:49:24.056688 00007ffc52b70000..00007ffc52bd6fff   65b356bc  C:\WINDOWS\system32\mswsock.dll
152:49:24.056702 00007ffc50d40000..00007ffc50d53fff   c19b74f1  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
152:49:24.056713 
152:49:24.056713 Potential code addresses on the stack:
152:49:24.056719 Xcpt PC         : 00007ffc189728c2 - 0x000928c2 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056740 00000000cacbf588: 00007ffc189706df - 0x000906df bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056759 00000000cacbf618: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056770 00000000cacbf648: 00007ffc18911bed - 0x00031bed bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056777 00000000cacbf690: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056784 00000000cacbf6a8: 00007ffc188f3a79 - 0x00013a79 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056791 00000000cacbf6d8: 00007ffc1892917c - 0x0004917c bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056798 00000000cacbf6f8: 00007ffc18905317 - 0x00025317 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056804 00000000cacbf708: 00007ffc18927e6f - 0x00047e6f bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056813 00000000cacbf788: 00007ffc18b753c6 - 0x001353c6 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056820 00000000cacbf7e8: 00007ffc18b74fa3 - 0x00134fa3 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056829 00000000cacbf800: 00007ffc18a40000 - 0x00000000 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056836 00000000cacbf818: 00007ffc56327bd4 - 0x00017bd4 bytes into C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.056841 00000000cacbf848: 00007ffc56bace51 - 0x0006ce51 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.056860 00000000cacbf898: 00007ffc545f06c0 - 0x001006c0 bytes into C:\WINDOWS\System32\KERNELBASE.dll",paulcad
19983,critical eror occured while runing vm and vm stopped,other,other,VirtualBox 6.1.16,2020-10-20T17:22:00Z,2020-10-20T17:22:00Z,,sebibala
19991,It is not possible to drag and drop files.,Windows,Windows,VirtualBox 6.1.16,2020-10-22T13:25:10Z,2020-10-22T13:25:10Z,"Attached to the log file, Guets is windows 1064Bits and Host also windows 10 64Bits.

This feature is very important and does not work it would be interesting to implement a Ctrl + C and Ctrl + V feature I think it would be more and would not give so much problems because with each version that I update in the Virtual box to stop drag and drop even then marked as bidirectional",luciano_f
19993,USB MIDI on Windows 2000 SP4,Linux,Windows,VirtualBox 6.1.14,2020-10-22T18:20:52Z,2020-10-22T18:20:52Z,"Hello All,

when I connect YAMAHA MIDI Keyboard to Windows 2000 host via USB the system crashes during the PnP phase. When it enters the:

""Found New Hardware - USB Audio Device"" the BSOD appears with:

STOP 0x0000001E ...
KMODE_EXCEPTION_NOT_HANDLED
Address BCEA7A90 base at BCEA3000, DateStamp 3803cad4 - usbaudio.sys
... etc.

I tried almost everything from switching to USB 1.0, changing the Sound Card to SoundBlaster etc.
The Host is Debian 10 (buster) the version of VirtualBox is 6.1.14.

I updated the VirtualBox Guest Add-ons to latest version. Turned off VT-x all leads to BSOD.

Thanks in advance",unun
19873,VMSVGA: 1920x1080 resolution not available at boot (?),Windows,Linux,VirtualBox 6.1.14,2020-10-23T01:45:38Z,2020-10-23T01:45:38Z,"As I've reported in some other tickets, I have a ''Oracle Linux Server release 7.8'' VM running on ''Windows 10''.[[br]]
The ''Video Memory'' is set to ''128MB'' and the ''Graphics Controller'' to ''VMSVGA''.[[br]]
The VM starts in ''Full-screen Mode'' on my second display which is set to 1920x1080.

After upgrading from ''6.1.6'' to ''6.1.10'' (I've skipped ''6.1.8'') I have the following problem: the greeter (lightdm) doesn't span the whole maximized VM window because the resolution is lower, but that should not be the problem, as far as I can remember this always happened on the first display of the greeter after boot.[[br]]
But after logging in the screen remains black with a visible mouse cursor instead of displaying my desktop at 1920x1080.

The workaround I'm using is sending the guest into runlevel 3 and then again into runlevel 5 so Xorg gets restarted and after doing that I can login successfully into my desktop at the desired resolution.[[br]]
So I tool a look at Xorg.0.log soon after boot and then after the telinit workaround.[[br]]
I think that the relevant differences are:
{{{
94c94
<  (II) vmware(0): Modeline ""800x600""x60.0   42.75  800 850 900 950  600 650 700 750 -hsync +vsync (45.0 kHz eP)
---
>  (II) vmware(0): Modeline ""1920x1080""x60.0  152.77  1920 1970 2020 2070  1080 1130 1180 1230 -hsync +vsync (73.8 kHz eP)
129c129
<  (II) vmware(0): Output Virtual1 using initial mode 800x600 +0+0
---
>  (II) vmware(0): Output Virtual1 using initial mode 1920x1080 +0+0
}}}

So it seems that 800x600 is available soon after boot while 1920x1080 is not and, after restarting Xorg, the other way around.[[br]]
I've tried with Acceleration enabled and disabiled with the same result.

I also tried with VBOXSVGA but it has far more Modeline than VMSVGA, including 1920x1080, so there is no such problem with in this case.[[br]]


P.S.[[br]]
I don't know if it's something related to the problem, since I moved to 6.1 and switched to VMSVGA if missing with the following two commands (see also Ticket #19392), but it seems they aren't working anymore:
{{{
VBoxManage.exe setextradata ''<vmname>'' CustomVideoMode1 1920x1080x32
VBoxManage controlvm ''<vmname>'' setvideomodehint 1920 1080 32
}}}
anyway the screen was set to the higher resolution available after login and not black.",alealeale
19897,Virtualbox depends on deprecated pyhton version,Linux,Windows,VirtualBox 6.1.14,2020-10-23T09:35:53Z,2020-10-23T09:35:53Z,"Debian testing can't install the current python version 2.7.18 without deinstall Virtualbox.
The installed virtualbox packet is 6.1.14-140239~Ubuntu~eoan.
It is planned to update the python dependancies to the current versions?

--------------- snip -------------------------------------
axel@graf-zahl:~$ apt-get -s dist-upgrade
HINWEIS: Dies ist nur eine Simulation!
         apt-get benötigt root-Privilegien für die reale Ausführung.
         Behalten Sie ebenfalls in Hinterkopf, dass die Sperren deaktiviert
         sind, verlassen Sie sich also bezüglich des reellen aktuellen
         Status der Sperre nicht darauf!
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libpython-stdlib libsdl-ttf2.0-0 python-minimal
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
  python virtualbox-6.1
Die folgenden Pakete sind zurückgehalten worden:
  libpython2-stdlib python2 python2-minimal
0 aktualisiert, 0 neu installiert, 2 zu entfernen und 3 nicht aktualisiert.
Remv virtualbox-6.1 [6.1.14-140239~Ubuntu~eoan]
Remv python [2.7.16-1]
axel@graf-zahl:~$ 
--------------- snap -------------------------------------
",DanielDuesentrieb
19994,Network Status Bar Icon always displays connect,Windows,Windows,VirtualBox 6.1.16,2020-10-23T17:00:16Z,2020-10-23T17:00:16Z,Network Status Bar Icon always displays connect regardless of connected or disconnected.,irondude
19995,Error occurs when attempting to delete a virtualbox nic if it is disabled in the operating system,all,Windows,VirtualBox 6.1.16,2020-10-23T20:54:34Z,2020-10-23T20:54:34Z,"Not particularly a huge issue, but I have found that, when one attempts to delete a virtualbox virtual network adapter from within virtualbox and the virtual nic has been disabled in the actual operating system, you get this error:

[[Image(https://i.imgur.com/KZwaezQ.png)]]

However, as you may have guessed, if I re-enable the virtual network adapter in the operating system and try to delete the nic in virtualbox, it works.",coolbeans
19996,Black Screen of Death,Windows,Linux,VirtualBox 6.1.16,2020-10-24T18:59:43Z,2020-10-24T18:59:43Z,"I'm trying to get virtualbox running on a windows 10 pro (2004) machine and create a linuxmint vm.  When I start the VM I get the linux screen that says ""start linux"" and then after 10 seconds the screen goes black.  I have disabled hyper-v, i have unchecked 3d acceleration.  I was able to get VMWARE to work but not having any luck with virtualbox.  I've attached the log file",rsail
19030,guest window position not restored,Windows,all,VirtualBox 6.0.14,2020-10-25T12:01:33Z,2020-10-25T12:01:33Z,"The guest window positions (guest with more than one monitor) are not restored.
In 5.0.40 it works well. In 5.1.Y it started not to work.

See also here: https://forums.virtualbox.org/viewtopic.php?f=6&t=95117",artelogic
19997,"Nested virtualization, Windows 8.1 64bit, multiple CPUs lead to crash",Windows,Windows,VirtualBox 6.1.14,2020-10-25T14:03:56Z,2020-10-25T14:03:56Z,"Forum topic:[https://forums.virtualbox.org/viewtopic.php?f=6&t=100373]
Host Machie: Windows 10 64bit (i9 9900K 8core)
Guest Machine1: Debian 10 64bit (4core allocated)
Guest Machine2: Windows 8.1 64bit

Host Machie contains Guest Machine1, and Guest Machine1 contains Guest Machine2, it's nested virtualization.

When I run Windows 8.1 64bit in Host Machie with multiple CPUs, no crash, everything is fine.
But when I run Windows 8.1 64bit in Guest Machine1, I can only allocate 1 cpu, if more then 1 cpu are allocated, it will crash after I click start.",larisa_serova
19984,PulseAudio not working on Fedora 33,Linux,other,,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
19999,no me deja aceptar las configuraciones que deseo aplicar en mi virtual box,Windows,Linux,VirtualBox 6.1.16,2020-10-26T04:21:42Z,2020-10-26T04:21:42Z,,roldan0314
20001,i can not start 64bit installation,other,other,VirtualBox 6.1.16,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
20002,Crash when restoring machine state and launching or selecting program from favorites,Windows,Linux,VirtualBox 6.1.16,2020-10-27T14:38:16Z,2020-10-27T14:38:16Z,"Windows 10 host and Ubuntu Desktop guest.

Whenever I save machine state with something running, I get a crash when I restore (the crash comes when I select a favorite, whether it was running or not). I have seen this in various scenarios (basically any other than shutting down with nothing running at all). I have attached logs for the following scenario.

1. Launch Ubuntu VM.
2. Start LibreOffice Writer (really can be anything, Visual Studio Code will do the same thing).
3. Click the 'X' in the far upper right to close VB. Select 'Save the machine state'.
4. In VB with the Ubuntu machine selected, click 'Start'.
5. The machine is restored, with the LibreOffice Writer document open.
6. Click on Chrome in the Favorites panel, trying to launch it (again, I'm not sure it matters what program you try to launch here).
7. The crash window immediately comes up (the one with the OK and IGNORE buttons telling me I have to shut down and where the logs are, etc.)

This behavior is consistent. It basically makes the program unusable because I have to shut down the machine whenever I close VB.
",mark6139
19992,VirtualBox does not install on Fedora 32,Linux,all,VirtualBox 6.1.16,2020-10-28T14:36:49Z,2020-10-28T14:36:49Z,"uname -a: Linux master-1.fios-router.home 5.8.15-201.fc32.x86_64 #1 SMP Thu Oct 15 15:56:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Installed: kernel-devel.x86_64 ver 5.8.15-201.fc32
           kernel-headers.x86_64 ver 5.8.11-200.fc32
           VirtualBox-6.1.x86_64 ver 6.1.16_140961_fedora32-1
           gcc.x66_64 ver 10.2.1-5.fc32
All packages installed via dnf from the appropriate repositories.

vboxconfig fails. Log:
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.
Error building the module:
make: *** No rule to make target 'install'.  Stop.

I suspect that the underlying cause is that the version of kernel-headers doesn't match the exact version of the kernel. However, the fedora-32 repositories don't contain a package named kernel-headers-5.8.15; kernel-headers-5.8.11 is the most recent. Any other info you need? Any suggestions?",rws
19957,Virtualbox can't co-exist with python3 on Ubuntu 20.10 (even though python2 is also installed),Linux,other,VirtualBox 6.1.14,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
20007,virtual screen can not ne resized over rdp,Windows,Windows,VirtualBox 6.1.16,2020-10-29T09:47:01Z,2020-10-29T09:47:01Z,"I have a vm that i use on my home computer and a copy in the company over rdp.

At home it is no problem to change the virtual Monitor to my 1080p screen (windows 10 20h2) Nvidia 2060.
But when i remotely access the same(copy) vm i can not resize the screen. the only option i can access and change, is the screen is the scaling option (100 % 125 % and so on).

The remote Monitor has a screen size (1600x900) with an Intel(R) UHD Graphics 630

It is more an annoyance, to scroll the hole time, but as i need the hle screen, i have to do that fairly often.",nbk
14832,Unable to use Host-Only adapters on Windows 10 Threshold 2,Windows,all,VirtualBox 5.0.10,2020-10-30T19:55:25Z,2020-10-30T19:55:25Z,"I installed the new Windows 10 update ""threshold 2"" via Windows Update, and VirtualBox is no longer able to use Host Only adapters.  While it creates them, changes their IPs, and deletes them with no trouble, the following error message comes up when I try to run any VM with a Host Only interface attached:

{{{
Failed to open a session for the virtual machine Ubuntu Test.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

This worked with no trouble before the Windows Update, and all other adapter types still work perfectly.

I originally had this issue with VirtualBox 5.0.1, so I uninstalled that one and installed 5.0.10, and I still have the issue.

Log file attached.",kohenkatz
20010,Update to Qt 5.15.1,Windows,all,VirtualBox 6.1.16,2020-10-31T05:07:43Z,2020-10-31T05:07:43Z,subj,necros
20011,Use Host I/O Cache as default option,Windows,all,VirtualBox 6.1.16,2020-10-31T05:15:53Z,2020-10-31T05:15:53Z,subj,necros
20012,Externally zero null free space before compacting,Windows,all,VirtualBox 6.1.16,2020-10-31T05:22:37Z,2020-10-31T05:22:37Z,Any way to apply sdelete function externally from GUI before compacting vdi?,necros
19635,"Option ""Auto-resize Guest Display"" grayed out on Xubuntu/Kubuntu 20.4 Host and Windows 10 Guest",Linux,Windows,VirtualBox 6.1.8,2020-11-01T21:31:34Z,2020-11-01T21:31:34Z,"Option ''""Auto-resize Guest Display""'' is disabled / grayed out. Max. resolution is set to 1920x1200. Guest Add-Ons are installed (most recent ones).

I think problems started when I updated to Kubuntu/Xubuntu 20.04 (not really sure). I was able to reproduce this issue on three (!) machines independently. One with Xubuntu 20.04 and two with Kubuntu 20.04. Different graphics cards as well.

A solution is to set ''""Graphics Controller""'' from ''""VBoxSVGA""'' to ''""VBoxVGA""'' and disable 3D acceleration. Then you have to shut down and restart your VM properly (by OS shutdown functionality).

However, ''VBoxVGA'' is not recommended and 3D Acceleration is not available. Should be considered as a bug!


'''Laptop 1:'''

Lenovo Thinkpad P1 2nd Gen

Kubuntu 20.04

VirtualBox 6.1.8

NVIDIA Quadro T2000

Switchable graphics are disabled => Intel graphics card not used

nvidia-driver-440


'''Laptop 2:'''

Lenovo Thinkpad T430

Xubuntu 20.04

VirtualBox 6.1.8

Switchable Graphics active

NVIDIA NVS 5400M

nvidia-driver-390


'''Laptop 3''':

Lenovo Thinkpad T570

Kubuntu 20.04

VirtualBox 6.1.6_Ubuntu r137129

Intel Corporation HD Graphics 620 (rev 02)

Kernel driver",openminded
20013,VirtualBox locks up when host resumes from sleep,Windows,Windows,VirtualBox 6.1.16,2020-11-02T11:36:16Z,2020-11-02T11:36:16Z,"I have had an issue with VirtualBox locking up on Host resume from sleep for years, but it seemed to be a bit random. However I did notice that in v6.1.14 it hardly occurred any more, perhaps once a fortnight.

Once I upgraded to v6.1.16, VirtualBox was locking up almost every time the Host resumed from sleep.

After a few days of these lockups I decided to revert to v6.1.14 (29th October) and since then I've not had a single lock up and I've probably resumed the Host from sleep a dozen times.

I've attached the logs from v6.1.16 but from my quick look, I don't think anything gets logged after the sleep as it locks up before that can happen.

The Host is Windows 10 Home 1909 Build 18363.1139
The Guest is Windows 10 Pro 1909 Build 18363.1139",Iain Waddell
20014,VirtualBox GUI broken after update from 5.2.44 to 6.1.14,Linux,Linux,VirtualBox 6.1.14,2020-11-02T15:56:52Z,2020-11-02T15:56:52Z,"After struggling all day trying to keep 5.2.44 working with VVV, I decided to try updating to 6.1.14.  As a result, when I open up the VirtualBox Manager GUI, I get this broken display.  The contents are in the incorrect location and aren't clickable.  If I expand the window, all of the content disappears.  Luckily, I don't need to use the configuration tools there at the moment but this will be a problem for me quite soon.",artlytic_dave
18404,No Audio on Linux Guest with Windows 10 x64 host when changing output device in host,Windows,Linux,VirtualBox 6.0.4,2020-11-03T00:15:01Z,2020-11-03T00:15:01Z,"Audio in the linux guest completely hangs, after changing output audio device in the windows host (plugging in/out headphones)
Tried with both AC97 and HDAudio device under Manjaro.
Started with 6.0.4 comming from 6.0.2
",BartHandels
17225,Audio distortion/skipping/stutter in Windows 7 Guest,Windows,Windows,VirtualBox 5.2.0,2020-11-03T00:15:38Z,2020-11-03T00:15:38Z,"Both my host and guest are Windows 7 Professional.  If I use the HD Audio driver for the guest, the audio lags behind the video a few frames for any streaming video such as news or YouTube.  Also, there is distortion, popping, crackling, skipping, etc. of the audio.  After switching to AC97 ICH in the guest, the LAGGING problem goes away.  However, the distortion persists.

I followed the steps for Audio Debugging in the Wiki.  The WAV file also exhibits some distortion when played on the host, though perhaps not quite as noticeable as the distortion in the guest.  I am attaching the VBox.log file.

Finally, it may be worth noting that NONE of these issues existed for me when I was using VBox version 5.0.26.  Every version of 5.1 I have tried as well as the newest 5.2 has this problem.",LittleJeff1970
19158,VirtualBox and bluetooth earbuds,Windows,Windows,VirtualBox 6.1.0,2020-11-03T00:16:08Z,2020-11-03T00:16:08Z,"Host: Windows 10 (all updates)
Guest: Windows 10 (all updates)
Earbuds: Bluetooth Sony wf-1000xm3 (firmware 2.03)

Connected earbuds to host, guests detect and no issues.
Once earbuds disconnected from host and connected again, guest can not detect the audio coming from host via earbuds (sound via speakers and wired earnphones works well)",superme
20015,VBox commands via MS openssh on a windows 10 host system fail CO_E_RUNAS_LOGON_FAILURE,Windows,all,VirtualBox 6.1.16,2020-11-03T13:27:29Z,2020-11-03T13:27:29Z,"Trying to run ""VBoxManage list vms"" on a Windows 10 host, when connected to the host via Microsoft OpenSSH server fails:

VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Completely failed to instantiate CLSID_VirtualBox: CO_E_RUNAS_LOGON_FAILURE
VBoxManage.exe: error: Details: code CO_E_RUNAS_LOGON_FAILURE (0x8000401a), component 
VirtualBoxClientWrap, interface IVirtualBoxClient

This works as soon as any user (it does not need to be the one who tries to run the command) connects via rdp to the system. If a user B is connected to the system and a VBox is started from user A, the VBoxHeadless process is running as user B...

Is it possible to avoid this behaviour and run VBoxManage commands and even start headless VMs connected via openssh?
What is the reason for this behaviour?


",mih
19907,"Starting VM causes 100% load on one cpu in NT-Kernel, even after VM exit",Windows,all,VirtualBox 6.1.14,2020-11-03T21:15:43Z,2020-11-03T21:15:43Z,"Observe in Host task manager, that ""System"" process works normally. Everything idle.

Simply start some VM (tested Fedora 32 and Windows 10 1909 guest). Wait until its booted and logged in (Guest additions installed and loaded).

Observe in Host task manager, that ""System"" (ntoskrnl.exe) process fully loads 1 core. This is in addition to the VM process itself.

Shutdown VM.

High load can still be observed and is persistent until host is rebooted.

I tried to reproduce this with same VMs imported to another host, but failed. Seemingly its somehow connected to specific host configuration/hardware. host hardware also is relatively new.
However it is 100% reproducible on this host and always triggered by staring some VM.",theRman
20018,BSOD when plugging (any) USB device to Windows 10 computer even when no VM is on,Windows,all,VirtualBox 6.1.16,2020-11-05T07:36:22Z,2020-11-05T07:36:22Z,"For my windows laptop this issue occurs for at least couple of newest builds of VirtualBox 6.1.x versions. The issue haven't occurred on version 6.0.24 for me.

Every time I connect any USB device to my laptop AFTER starting VBox (but not necessarily any VMs) BSOD occurs.

VBoxUSBMon.sys seems to cause PNP_DETECTED_FATAL_ERROR.

Some of my colleagues are suffering from same issue.


Windows 10 Enterprise, 2004, 19041.572",SamuelH
20019,Hosted VM is restarting unexpectedly which contains VirtualBox,Windows,Linux,VirtualBox 6.1.16,2020-11-05T08:16:49Z,2020-11-05T08:16:49Z,"We've a Windows 10 Azure VM  which we have installed latest VirtualBox on it. After starting image on VB, everything is fine. But, when we try to login to guest vm via filezilla/putty from hosted vm, it's restarting hosted VM suddenly. 

Please check log that belongs to guest vm that we having problem.",alpercelerce
20021,AMD Ryzen 9 3900XT - Slackware Current64 - kernel 5.9.3-burdi64 - VM's fail to start,Linux,Linux,VirtualBox 6.1.16,2020-11-05T16:24:25Z,2020-11-05T16:24:25Z,"Some weeks ago my multi-boot Intel i7-6700 system died on me. From backups I was able to clone things on the AMD Ryzen 9 3900XT replacement. Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.

The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. Sometimes I can start another user session via <Alt+Fx>. Very often a hard restart is required.
The Slackware instance initially ran my own kernel 5.8.14-burdi64, the Xubuntu one kernel 5.4.0-48-generic. During the testing these kernels were upped. At the moment they are 5.9.3-burdi64 and 5.4.0-52-generic respectively. The symptoms however stayed the same.[[BR]]
I started out with VB 6.1.14-140239. Nowadays I test with VB 6.1.16-140961, a preliminary test with VB 6.1.17-141128 shows no discernable effects.[[BR]]
It should be noted that both the Slackware and Xubuntu instances via symlinks refer to the same VM's.

The Slackware ""error"" VBox.log ends with:[[BR]]

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}

while the Xubuntu ""ok"" one contains:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


The i7-6700 had embedded video, so used the i915 driver. My Ryzen has a discrete video card -- an ASUS Radeon RX 550 PH-RX550-2G-EVO one:
-- lspci: [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7).
supported by the amdgpu driver.

To isolate the problem I did the following tests:[[BR]]
-- I cloned the Slackware instance to an i5 laptop with embedded video: the VM's there started and ran without problems;[[BR]]
-- Back on the AMD box I replaced my 5.9.3-burdi64 kernel with Slackware's stock 5.4.74 one: the VM's started and ran without problems;[[BR]]
-- I upped the Xubuntu kernel to the 5.9.2-050902-generic one from the kernel PPA: the VM's started and ran without problems;[[BR]]
-- I replaced the Xubuntu VB 6.1.16-140961 .deb implementation with the .run one: the VM's started and ran without problems;[[BR]]
-- Back on my Slackware instance I replaced the 5.4.74 kernel with the Xubuntu 5.9.2-050902-generic one: the VM's started and ran without problems.

As said when the problem occurs one often cannot do much more than hard resetting the system. By formally repeating these tests and collecting as much info as possible I found that for the ""error"" case the syslog reports an oops ""unable to handle page fault for address"", the call trace of which starts within vboxdrv.

The Slackware the VBox.logs and the /var/log/messages file as collected are:[[BR]]
-- VBox-59S.log: the ""error"" with my 5.9.3-burdi64 kernel;[[BR]]
-- VBox-54S.log: the ""ok"" with Slackware's stock 5.4.74 kernel;[[BR]]
-- VBox-59U.log: the ""ok"" with the Xubuntu 5.9.2-050902-generic kernel;[[BR]]
-- messages: searching for ""========="" will give you the ""error"" and ""ok"" sections.

It is likely that something in the configuration of my 5.9.3-burdi64 kernel triggers the problem. But which setting is the culprit? My config is 187.4 kB and the Xubuntu one is 248.8 kB. So comparing the two is an almost hopeless endevour ...

Any hints would be appreciated.[[BR]]
:D
",burdi01
19950,UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: 0x0 1920x1173,Linux,Linux,VirtualBox 6.1.14,2020-11-05T16:34:20Z,2020-11-05T16:34:20Z,"Recently I migrated my multi-boot system from an i7-6700 to a Ryzen 9 3900XT.[[BR]]
Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.[[BR]]
The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. A hard restart is required.[[BR]]

From the VBox.log's it seems that the Slackware problem is:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}


whereas the Xubuntu VBox.log reads:


{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


Note the ""0x0"" versus ""0x25"".[[BR]]

As via symlinks the VB settings and VM definitions are shared between the sundry Linux instances an error like a ""leftover"" file definition is highly unlikely.[[BR]]

Some other differences beween the VBox.logs are:[[BR]]
-- Xubuntu kernel 5.4.0-48-generic, Slackware 5.8.14-burdi64;[[BR]]
-- Xubuntu VB QT version 5.12.6, Slackware 5.6.1;[[BR]]
-- Xubuntu X release 12008000, Slackware 12009000;[[BR]]
-- Xubuntu loads a VMMR0.so, Slackware does not.[[BR]]

I started out with VB 6.1.14-140239. For Slackware I then tested VB testbuild 6.1.15-6.1.15-140809 asis with kernel 5.8.14-burdi64 and the same testbuild but patched (see #19845) with kernel 5.9.0-rc8-burdi64.[[BR]]
However the problem persists ...


 ",burdi01
20017,VB installation failing in linux kernel drivers installation,Linux,other,VirtualBox 6.1.16,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
20024,Linux host freezes with bridged adapter and apt,Linux,Linux,VirtualBox 6.1.16,2020-11-08T03:28:46Z,2020-11-08T03:28:46Z,"My Linux (Fedora 33) host freezes whenever I enable bridged adapter and the guest transfers (some) data.

Steps to reproduce:
1. Install an Ubuntu 20.04 server guest
2. Go to Guest settings, Network, Attached to, Bridged Adapter
3. Run an apt install command on it. I was following [these instructions](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart).
4. The host completely freezes, and I'm forced to reboot.

I've installed some server software (Jitsi Meet) and now it freezes even on guest boot.

Some hardware details:

{{{
*-cpu
          product: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
          vendor: Advanced Micro Devices [AMD]
          physical id: 1
          bus info: cpu@0
          size: 1443MHz
          capacity: 2100MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq
}}}



{{{
*-network
                description: Wireless interface
                product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: wlp2s0
                version: 00
                serial: [REMOVED]
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.18-300.fc33.x86_64 firmware=N/A ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
                resources: irq:81 ioport:2000(size=256) memory:c0700000-c070ffff
}}}

I will append a log file in some minutes",gabrc
20025,"DirectSound Device on windows host not found, no sound on host OS, independent of guest OS",Windows,all,VirtualBox 5.2.42,2020-11-08T16:31:33Z,2020-11-08T16:31:33Z,"In VBox.log the following occurs during Direct Sound Initialisation on Windows 7 32-bit host, independent of guest OS, the improvement is applicable to all Windows hosts versions:

00:00:02.768338 Audio: Initializing DirectSound audio driver
00:00:02.796743 DSound: DirectSound not available: REGDB_E_CLASSNOTREG
00:00:02.796782 Audio: Initialization of host driver 'DSoundAudio' failed with VERR_NOT_SUPPORTED
00:00:02.797158 Audio: Initializing NULL driver
00:00:02.797183 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0)
00:00:02.797189 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message=""Host audio backend initialization has failed. Selecting the NULL audio backend with the consequence that no sound is audible""

In DrvHostDSound.cpp, line 2253 the intialisation happens on a fixed audio device interface ID (of what I can see, I am not 100% sure, just looks like it). Rather build an ""enum"" list of sound devices in the computer. These audio devices can have any IDs. Make that list available in the user interface by audio device name (two lists for Sound In and Sound Out). The user can then select the audio device he/she wants to use, one for sound in, and the other for sound out. So then it does not have to be the default audio device. The user can have several audio devices, e.g. Intel HD Audio, Creative audio, NVidia Sound, etc on the Windows host.

The default audio device fails on my machine, since I have a Creative Audio Product, which has a non-standard GUID.

Attached I have the user interface of the audio tab (there is no device selectable, only a default WindowsDirectSound Device. That's no good. Make a list of direct sound audio devices available in the computer, and expose that list to the user interface. That way, the user can select the audio device to use (does not have to be default, then).

The issue is here, /src/VBox/Devices/Audio/DrvHostDSound.cpp, line 2253:

static DECLCALLBACK(int) drvHostDSoundInit(PPDMIHOSTAUDIO pInterface)
{
    PDRVHOSTDSOUND pThis = PDMIHOSTAUDIO_2_DRVHOSTDSOUND(pInterface);
    LogFlowFuncEnter();

    int rc;

    /* Verify that IDirectSound is available. */
    LPDIRECTSOUND pDirectSound = NULL;
    HRESULT hr = CoCreateInstance(CLSID_DirectSound, NULL, CLSCTX_ALL, IID_IDirectSound, (void **)&pDirectSound);
    if (SUCCEEDED(hr))
    {
        IDirectSound_Release(pDirectSound);

        rc = VINF_SUCCESS;

        dsoundUpdateStatusInternal(pThis);
    }
    else
    {
        DSLOGREL((""DSound: DirectSound not available: %Rhrc\n"", hr));
        rc = VERR_NOT_SUPPORTED;
    }

The IID_IDirectSound should be an enum list with all audio devices attached to the host computer, make that list available in the user interface, so the user can select an audio device of his choice by device name.

It would be nice to also get that feature on the Virtual Box 5.2 for 32-bit Windows hosts, which I am currently using.

",Garfield
19640,Linux Fullscreen Guest display broken,Linux,Linux,VirtualBox 6.1.10,2020-11-09T03:22:37Z,2020-11-09T03:22:37Z,"At VirtualBox 6.1.4, the login screen shows fullscreen and once logged in, the desktop is set to fullscreen - in my case 1280 x 1024. 

Since VirtualBox 6.1.6 all my Debian 10 guests that run fullscreen have had
their display go blank once you've logged in. 

The same problem still exists with VirtualBox 6.1.10. The login screen is 
reduced to 800 x 600 and once logged in, the guests screen goes blank.
If you use the View -> Set Fullscreen (or Host+F key), the guests screen
reappears as windowed. Do this again and the guests display is fullscreen
again. However, rebooting the guest results in the same blank screen again. 

Attached are two VBoxLogs, one from 6.1.10 which is taken at the point the guests screen has gone blank and the other when using the GA's from 6.1.4, when everything works as it should.  

The Host is running Debian 10 with the Mate desktop.  
The affected guest(s) are also running Debian 10 with the Mate desktop.",Feline
19948,VirtualBox 6.1.14 Stop responding.,Windows,Windows,VirtualBox 6.1.14,2020-11-09T16:27:35Z,2020-11-09T16:27:35Z,"The program VirtualBox.exe version 6.1.14.40239 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1658
 Start Time: 01d69d5160d6c373
 Termination Time: 31
 Application Path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
 Report Id: ae63b5da-a309-46c2-aad5-d4d1807b745e
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown",sakurayz
19953,Cannot boot Windows 10 guest on OS X El Capitan host.,other,other,VirtualBox 6.1.14,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
20028,Crash when restoring Fedora virtual machine from a Snapshot,Linux,Linux,VirtualBox 6.1.14,2020-11-09T16:45:26Z,2020-11-09T16:45:26Z,"Shortly after restoring from snapshot with virtualbox 6.1.14, the Fedora VM locked up, and a few interesting things happened after I ended the process (the only way to close it as it was totally unresponsive):


The HDD with the OS on became detached.
Virtualbox refused to re-attach the HDD without dropping the saved state (shown in screenshot)
Upon re-attaching the HDD after dropping my saved state, the HDD state had not been restored to the state it was in when I took the snapshot (it was as if I hadn't tried to restore the snapshot).

Attached is the Vbox.log file, and a screenshot of the error I was given as mentioned above.

Please let me know if there's anything I can do to help further debug this. I want to note that VirtualBox 6.1.16 seems generally much more stable than 6.1.14, but I thought the information in this report might still be useful.",Hamish McIntyre-Bhatty
20029,Solaris 10 Guest operating slowly on Windows 10 host running 6.1.16 and other recent releases,Windows,Solaris,VirtualBox 6.1.16,2020-11-09T17:00:04Z,2020-11-09T17:00:04Z,"Running VBManagers earlier than 6.0, my Solaris 10 guest system operated with reasonable speed, but we had some problems with shared folders and creating/transferring data files to shared folders on the Windows 10 host system.
Now with 6.0.XX, the shared data folder problems seem to have been corrected, but the guest Solaris 10 system seems to run significantly slower than it did before.
Not sure if it is network issue - we have tried a variety of machine configuration options to optimize the guest system (more memory, more processors, anything else we could think of.)
Looking for ideas and suggestion, wondering if anyone else has seen this issue??",CJK
19741,Seamless mode is all-or-nothing,Windows,all,VirtualBox 6.1.10,2020-11-10T21:00:39Z,2020-11-10T21:00:39Z,"Bringing //one// guest-window to the foreground in seamless mode, brings //all// guest-windows to the foreground, obscuring the natively-running apps.

For example, if I have:

1. An xterm running in the upper left corner,
1. Another xterm in the lower right corner,
1. Microsoft Outlook in the center,

clicking on the first xterm's titlebar will bring both X11-programs to the foreground, obscuring not only the upper-left portion of Outlook, but also the bottom-right segment...

This is both undesired and unexpected. Though my current VB-version is 6.1.10, the problem is not new -- I've had it since my first encounter with VirtualBox years ago.

My guests are all X11-based (FreeBSD and Linux), but someone else told me, they have the same problem with a Windows guest.",mi
20031,Virtual Ram feature idea,all,all,,2020-11-10T23:04:29Z,2020-11-10T23:04:29Z,"Can you add a feature for Virtual Ram where it does not use the computer's physical ram and instead uses hard drive space on the host computer for ram, also select which drive to use for ram, ex: USB connected to the host computer and the user wants to use 4gb of its space for ram, so the user can go and create a ram disk by creating a virtual hard disk and use it for ram while stored on the USB",BSoD
20032,vboxautostart-service (auto-start) ignores guest settings and blocks guest VMs audio output.,Linux,Windows,VirtualBox 6.1.16,2020-11-11T18:07:00Z,2020-11-11T18:07:00Z,"Spent quite awhile tracking the culprit for this!

Running 6.1.16 (appears in recent older versions as well.)

Using a Linux Mint 20 Host, Windows 7 guest although tested with a Linux Mint 20 guest and it has issue as well. 

Started 2 different VMs using the following command

VBoxManage modifyvm xxxxx --autostart-enabled on --autostop-type acpishutdown --autostart-delay xx

Rebooted Host - everything launches correctly HOWEVER Windows Guest has NO AUDIO even though VM setting has Audio enabled. (With correct selections)

Issuing the following command: 

systemctl disable vboxautostart-service

Thereby disabling Autostart service

And rebooting and starting the VMs via script with the command:

vboxmange startvm xxxxx

Correctly allows guest audio.

There are a couple of annoying assumtions with Autostart as well. It FORCES headless (and audioless) operation of the client. Why? The Autostart feature should have a --type option as with the vboxmange startvm command (enhancement request)

Thank you for an otherwise great product and your attention to these issues.


",Vm User
12570,VM window appears off screen; not accessible,Windows,Linux,VirtualBox 4.3.6,2020-11-14T10:18:07Z,2020-11-14T10:18:07Z,"Virtual box remembers guest window location and uses it at next start-up for a VM.  This is a good thing.  However, what it doesn't do is confirm upon start-up that the remembered location is still valid and will display the window off screen and not viewable.  Worse, it does not respond to the typical Windows move commands in order to move the window back into viewable space.  This leads to not being able to correct the condition and the user is stuck with a window they cannot access.

Specifics:
At home, I have an additional monitor that is positioned vertically above my laptop screen and is oriented that way in Windows ""Screen Resolution"" where one identifies monitors and their relative locations.  At the office, I have three external monitors, all side-by-side, and do not use the laptop screen.

I had worked at home and placed the VM window in the ""top"" monitor in scaled mode.  I shut down the guest and then shut-down the host laptop in that condition and went to the office.  There, I started the host laptop, opened VirtualBox, and started the guest.  Initially, the guest window came up in my main monitor.  I then switched it to scaled mode and the window disappeared.  Attempts to move it via the Windows Move option from the System menu was not successful.

I ended up having to go into ""Screen Resolution"" and orienting my monitors to place one of them ""above"" my main monitor -- thus replicating the condition under which the scaled guest window last appeared.  Doing this, I was able to then access the guest window and drag it ""down"" to the main monitor.  I then reverted the monitor orientation to side-by-side and moved the guest window to the monitor on the side.

Certainly not an insurmountable issue but until I thought about trying the re-orienting of my monitors, I was really stuck.",RodBarnes
20035,Cloned guest poweroff fails and causes complete VM lockup,all,Windows,VirtualBox 6.1.16,2020-11-14T16:57:50Z,2020-11-14T16:57:50Z,"While provisioning a Windows 2016 cloned guest machine using Vagrant, a reboot command is issued that causes the guest to become completely locked up. The vbox.log shows that this appears to be an issue with the state transition table:

00:01:39.652519 Console: Machine state changed to 'Stopping'
00:01:39.652837 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:01:42.828602 AssertLogRel F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\PDMThread.cpp(990) int __cdecl pdmR3ThreadSuspendAll(struct VM *): RT_SUCCESS(rc)
00:01:42.828631 PDMR3ThreadSuspend -> VERR_TIMEOUT for 'HOSTRES'
00:01:42.828642 PDMR3PowerOff: 60 136 616 676 ns run time
00:01:42.828649 Changing the VM state from 'POWERING_OFF' to 'OFF'
00:01:42.828685 VMR3PowerOff:
00:01:42.828693  RUNNING -> POWERING_OFF, SUSPENDED -> POWERING_OFF, DEBUGGING -> POWERING_OFF, LOAD_FAILURE -> POWERING_OFF, GURU_MEDITATION -> POWERING_OFF, FATAL_ERROR -> POWERING_OFF, CREATED -> POWERING_OFF, RUNNING_LS -> POWERING_OFF_LS, DEBUGGING_LS -> POWERING_OFF_LS, GURU_MEDITATION_LS -> POWERING_OFF_LS, FATAL_ERROR_LS -> POWERING_OFF_LS failed, because the VM state is actually OFF
00:01:42.828729 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(3338) int __cdecl vmR3TrySetState(struct VM *,const char *,unsigned int,...); rc=VERR_VM_INVALID_VM_STATE
00:01:42.828857 VMSetError: VMR3PowerOff failed because the current VM state, OFF, was not found in the state transition table (old state FATAL_ERROR_LS)
00:01:42.830483 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Could not power off the machine. (Error: VERR_VM_INVALID_VM_STATE)}, preserve=false aResultDetail=-1907

The only way to recover from this is to kill the VM using task manager.

This issue is reproducible on both MacOS and Windows versions of VirtualBox and more information can be found here: https://github.com/clong/DetectionLab/issues/517",centurion
20039,Snapshot remove from disk but still in logical path,Windows,Windows,VirtualBox 6.1.16,2020-11-15T14:52:24Z,2020-11-15T14:52:24Z,"While the VM is running, I remove a snapshot. The removed snapshot is a parent snapshot of the running state. The snapshot is removed from disk but is still in the virtual media tree. 
In consequence the VM can't be started because the media (deleted) can't be read 

I tried to remove the media from the media manager, but the manager can't removed from the list because this media has 1 child.

How can I solve this problem and rescue the VM (the snapshot removed is a very old one and i need to restore on of his child).
 

 



 ",dingdingdong
20042,VirtualBox.exe crash at start,Windows,Windows,VirtualBox 6.1.16,2020-11-16T06:37:57Z,2020-11-16T06:37:57Z,"Sometimes (not always) VirtualBox GUI crashes at start. In such situation it is possible to successfully start GUI only at 2nd or 3rd attempt.

WinDbg bug analysis:

{{{
 SYMBOL_NAME:  Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e
 MODULE_NAME: Qt5GuiVBox
 IMAGE_NAME:  Qt5GuiVBox.dll
 STACK_COMMAND:  ~0s ; .ecxr ; kb
 FAILURE_BUCKET_ID:  NULL_CLASS_PTR_WRITE_c0000005_Qt5GuiVBox.dll!QRasterPaintEngine::transformChanged
 OS_VERSION:  10.0.19041.1
 BUILDLAB_STR:  vb_release
 OSPLATFORM_TYPE:  x64
 OSNAME:  Windows 10
 IMAGE_VERSION:  5.6.2.0
 FAILURE_ID_HASH:  {c4d15f2c-b524-5704-6c40-ab527e5b6a72}
}}}
",ReapedBrain
19662,Upgrade to 6.1.10 breaks all VMs on Windows 10,Windows,all,VirtualBox 6.1.10,2020-11-16T08:53:58Z,2020-11-16T08:53:58Z,"Just upgraded from to 6.1.10 on Windows 10 and am not unable to start any VM, the error received is:
More specifically, the error is:

{{{
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0xa34e2 and 0xa34ec in #1 (.text), first 8b != b8 (rc=-5600)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification Failure: The memory content does not match the image file.
}}}
",Twisted Lucidity
19890,Guest Windows Slowly Shrink Vertically to 103 pixels  and Jump Around on Resize,Linux,all,VirtualBox 6.1.14,2020-11-16T19:02:58Z,2020-11-16T19:02:58Z,"Hi,

I started a thread on the Community Forums on this on Sept 3rd, and despite some excellent questions from Volunteer fth0 in Germany, I think it's time for a bug report.

The trail on community is at [https://forums.virtualbox.org/viewtopic.php?f=7&t=99659].  It includes a small video of the shrinking guest windows, plus a bunch of Log files.

----
'''SUMMARY'''

I just upgraded to V 6.1.12 r139181 and I'm seeing some very odd behavior in guest windows. A subsequent upgrade to Version 6.1.14 r140239 (Qt5.14.2), including the extpack and Guest Additions, has not changed anything.

'''DETAILS'''

Guest windows jump around randomly at irregular times, and guest windows slowly shrink vertically '''unless maximized''' after a resize. Over a period of 15 - 20 minutes, a guest windows shrinks, vertically only, until it's 103 pixels in height.  It seems to shrink 1 or 2 pixels at a rate that appears dependent on the host machine's loading, but often around every 1 or 2 seconds.  This makes it impossible to do much with the guest OS, because any menu picks get removed by the window redraw before an option can be chosen.

Horizontal size seems to be irrelevant.  Scale factor in Display Setting for all guests is 100%.

If I resize a guest window, it will jump elsewhere randomly - often to another screen or straddling two monitors, and then start shrinking.


This happens on both Windows and Linux guests, with VBoxVGA and VBoxSVGA graphics controllers. It has only started since the update to the 6.1.12 and 6.1.14 versions...all was fine before that.

The host machine is an 8 physical core (16 virtual) AMD Ryzen 7 2700X PowerSpec G162 with an AMD Radeon RX580 GPU, with 48G RAM and 15Tb Storage so it can handle the VBox load.
The machine is running KDE Neon 5.19.4, which is KDE's own distro, based on Plasma 5.19.4 and the 5.14.2 Kernel. I have compositing switched on for full KDE effects.
I have 3 4k Monitors, although I don't think that's relevant.

The Log files contain large numbers of repeats of these lines, with the X size reducing by 1 or 2 pixels each time, until 103 is reached.


{{{
00:04:30.078206 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2245x103 if necessary
00:04:30.182443 VMMDev: SetVideoModeHint: Got a video mode hint (2245x103x32)@(0x0),(1;0) at 0
00:04:30.182825 VMMDev: Guest Log: Got multi resize request 1 displays
00:04:30.182851 VMMDev: Guest Log: [0]: 0 0x39 0,0 2245x103 32
00:04:30.194294 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:04:30.205602 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f9698000000 w=2245 h=103 bpp=32 cbLine=0x2314 flags=0x1 origin=0,0
}}}


At fth0's suggestions, I tried setting extradata to various initial window sizes, to see if that affected the shrinking behaviour, but it hasn't made much difference.





",PHands
20044,IP Duplicate with MacOS 11.0.1 (Big Sur) and VBox 6.1.16,Windows,OSX Server,VirtualBox 6.1.16,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,"After installing MacOS X 11.0.1 and reinstalling VBox 6.1.16 to fix the kernel issue.

Now all Guest OS cannot connect to network (Bridged Adapter), since it detect a conflict IP address.

Looking in Windows Event Viewer and the duplication of 0.0.0.0 is identified with the MAC address of the Host MacOS server

I think we should have a new release to correct this issue in MacOSX Big Sur
Thank you",BDelorme
20045,Install Debian not run,Windows,Linux,VirtualBox 6.1.14,2020-11-17T08:18:35Z,2020-11-17T08:18:35Z,Installation of Debian will not run with VirtualBox 6.1.14r140239,christophedlr34
20046,Host-Only Adapter not migrated during Windows 10 inplace upgrade,Windows,other,VirtualBox 6.1.16,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
18522,Audio transmitted with the VBox Remote Display server sounds chopped and pitched,Windows,Linux,VirtualBox 6.0.4,2020-11-18T11:30:05Z,2020-11-18T11:30:05Z,"Audio generated in a Linux guest on a Windows 7 host can be transmitted via the VBox Remote Display server, and is received with a Windows 10 Remote Desktop client. (This was not possible in earlier versions of VBox, I believe).
However, the sound that is played back on the Remote Desktop client (Windows 10) sounds 'chopped'. Moreover, the sound is seemingly transmitted or played back with a wrong samplerate, i.e. the pitch is considerably higher than of the sound on the Linux guest.
",EsbenS
20047,VirtualBox not compatible with Windows Memory integrity feature,Windows,all,VirtualBox 6.1.16,2020-11-18T12:06:48Z,2020-11-18T12:06:48Z,"https://docs.microsoft.com/windows/security/threat-protection/device-guard/memory-integrity

When Memory integrity is enabled all guest machines will become unusably slow.",fredd
20049,Испорченный образ Guest Addition Addon,other,other,VirtualBox 6.1.16,2020-11-18T21:11:55Z,2020-11-18T21:11:55Z,Отсутствует компонент NTDLL.DLL:NtQueryObject в файле VBoxWindowsAdditions.exe,IBw
14323,Virtualbox 5.0: Blackscreen in fullscreen mode with i3wm host.,Linux,all,VirtualBox 5.1.4,2020-11-19T13:25:26Z,2020-11-19T13:25:26Z,"Hello,

ISSUE:
It seems that VirtualBox update don't handle the fullscreen mode when host is using i3wm as Window manager. When hitting host+F keys, the screen become black and the only way to go back is to click icon on the bottom bar (Host+F was not responding when in fullscreen mode).

INVESTIGATION:
The issue was not present on the last virtualbox update (4.3.24 on ArchLinux). To be sure that the problem came from the window manager, I launched virtualbox on the same machine using XFCE as window manager and everything was fine. 
I have tested it with multiple VMs: Slitaz, Debian 8, Windows server 2012, Windows 7. Each time with updated guest additions tools.
",y0no
15863,Auto-Resize is broken with tiling window managers,Linux,Windows,VirtualBox 5.1.4,2020-11-19T13:26:17Z,2020-11-19T13:26:17Z,"I run Archlinux with i3wm, installed VirtualBox via pacman (virtualbox).  A recent update has caused nasty behavior around window sizing for guests: using the ""auto-resize"" feature is completely broken. The window is now resized to some seemingly arbitrary size, and I cannot override it (it just resizes right back). It also cannot be auto reassigned to a specific workspace.

",amosb
20050,Execution Cap fails in V 6.1.16,Windows,Windows,VirtualBox 6.1.16,2020-11-19T18:51:44Z,2020-11-19T18:51:44Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
20051,Execution Cap fails in V 6.1.16,Windows,Windows,VirtualBox 6.1.16,2020-11-19T18:51:49Z,2020-11-19T18:51:49Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
19929,VMs only start in headless mode on Big Sur,Mac OS X,other,,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
20048,Nested VMs on Intel without VMCS Shadowing,other,Linux,VirtualBox 6.1.16,2020-11-21T04:56:01Z,2020-11-21T04:56:01Z,"Having nested VMs as of 6.0 is great, but the requirement for Intel VMCS Shadowing means that it's only available on a limited set of CPUs.

Is there any chance of adding for support on CPUs that do not have VMCS Shadowing? At least for Linux guests?",Grunthos
20056,no mouse pointer or capture after login,Windows,Linux,VirtualBox 6.1.16,2020-11-21T15:17:33Z,2020-11-21T15:17:33Z,"Until 11/17/20, my VM worked perfectly. Now, the mouse works UNTIL I login. But AFTER login, the capture is no longer working. There is NO mouse pointer on the virtual desktop, just the REAL mouse pointer, which moves anywhere, in or out of the Virtualbox.
The Vbox message (at the top of the window) saying the capture is effective shows and the capture icon indicates the mouse integration is on, but it is NOT being captured.
Using the CNTRL key to get the ""capture"" window and allowing capture, the mouse is NOT captured. 

I am using VBOX 6.1.16. My guest O/S is Ubuntu 20.04.1-AMD64. 
My HOST O/S is Windows 10 Pro 64-bit. I/O APIC was already on and I left it on.
I have tried:
*VMSVGA vs. VBOXSVGA vs VBOXVGA
*increase video memory to 128MB
*1 vs 2 CPUs
*USB tablet vs PS/2 Mouse
*paravirtualization: default vs minimal
*re-install Vbox extensions
* Enable PAE/NX
*3D accel on vs off
None of these make any difference. 
""File>send shutdown signal"" does NOT shut down the VM.

",Dennis Foreman
20057,long loading initial ramdisk virtualbox,other,other,VirtualBox 6.1.16,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
19875,Upgrading Guest Additions on NT4/W2000 can't overwrite VBoxService.exe,all,Windows,VirtualBox 6.1.14,2020-11-21T17:22:26Z,2020-11-21T17:22:26Z,"Host can be anything (though tested only on macOS 10.13 and Windows 10).

Guest: Windows 2000 and Windows NT4 only (no problems on anything newer).

Upgrading the guest additions will always halt with:
Error opening file for writing:
C:\WINNT\system32\VBoxService.exe

Selecting ""Ignore"" will bypass the installation of that file. GA appears to work fine afterwards but is probably still running an older version of that file. Uninstalling GA completely, rebooting and then reinstall GA is how I'm currently getting around this.

This appears to have started from 6.1.x onwards.

",DavidVivaDJ
20020,VirtualBox 6.1.16 Ubuntu 20.04 Guest freezes when windows 10 screensaver or screen lock,Windows,Linux,VirtualBox 6.1.16,2020-11-22T10:54:59Z,2020-11-22T10:54:59Z,When I lock screen on Windows 10 host and then unlock and log back in my VirtualBox Ubuntu 20.04 Guest v6.1.16 freezes (I even have issues closing the main window of VirtualBox guest). Totally unresponsive. Only closing guest (after putting in some effort) main window with quite a few attempts including VirtualBox Manager on host freezing at the same time and restarting gets the VM back to life only to be unusable after host screen lock again...,SamH
20058,Virtual Box encounters error while Ubuntu 20.04 VM is running,Windows,other,VirtualBox 6.1.16,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
20059,error in window vista,Windows,Windows,VirtualBox 6.1.16,2020-11-23T01:29:24Z,2020-11-23T01:29:24Z,error in window vista,lev115
20060,Unable to read complete notification,other,other,VirtualBox 6.1.16,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
20061,"""Permission denied"" error at linux-guest on Windows10-host when execute a file on a shared folders immediately after creation or 'chmod +x'",Windows,Linux,VirtualBox 6.1.14,2020-11-24T10:45:10Z,2020-11-24T10:45:10Z,"
Following script reproduces the error on my virtual linux-machine when working on a share folder (in my case the '/vagrant'):

Script:


{{{

set -x

# switch to shared folder
cd /vagrant/ || exit 1

# create simple script
echo ""echo 'Hello World'"">PrintHelloWorld.sh
cat PrintHelloWorld.sh || exit 1
ls -l PrintHelloWorld.sh || exit 1

echo ""start failing tests...""
touch PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +x PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +r PrintHelloWorld.sh
./PrintHelloWorld.sh
}}}


Output:


{{{
++ cd /vagrant/
++ echo 'echo '\''Hello World'\'''
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ls -l PrintHelloWorld.sh
-rwxrwxrwx 1 vagrant vagrant 19 Nov 24  2020 PrintHelloWorld.sh
++ echo 'start failing tests...'
start failing tests...
++ touch PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 14: ./PrintHelloWorld.sh: Permission denied
++ chmod +x PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 17: ./PrintHelloWorld.sh: Permission denied
++ chmod +r PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 20: ./PrintHelloWorld.sh: Permission denied
}}}


The second part of the script shows some 'workarounds' to the problem:


{{{
echo ""start successful tests...""
touch PrintHelloWorld.sh
sleep 1
./PrintHelloWorld.sh

touch PrintHelloWorld.sh
cat PrintHelloWorld.sh
./PrintHelloWorld.sh

echo ""echo 'Hello World'"">PrintHelloWorld2.sh
./PrintHelloWorld2.sh

echo ""cleanup...""
rm PrintHelloWorld.sh
rm PrintHelloWorld2.sh

}}}


and creates following output:


{{{
++ echo 'start successful tests...'
start successful tests...
++ touch PrintHelloWorld.sh
++ sleep 1
++ ./PrintHelloWorld.sh
Hello World
++ touch PrintHelloWorld.sh
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ./PrintHelloWorld.sh
Hello World
++ echo 'echo '\''Hello World'\'''
++ ./PrintHelloWorld2.sh
Hello World
++ echo cleanup...
cleanup...
++ rm PrintHelloWorld.sh
++ rm PrintHelloWorld2.sh
}}}

The complete repro-environment including script and logs are attached.



",progger98
20038,Linux guest GUI freeze or full VM hang after not being interracted with for some time,Windows,Linux,VirtualBox 6.1.16,2020-11-24T11:17:52Z,2020-11-24T11:17:52Z,"
== Linux guest GUI freeze or full VM hang after not being interacted with for some time ==


'''Terms in use:'''

 - '''GUI Freeze''': The ''GUI inside the VM, XFCE, is not responsive''. ''The VM is still active, as can be seen by the activity indicators'' (disk, network, etc). A console can be brought up (ctl-alt-F2 for example), logged into, and all of my users processes killed with ""pkill -u myusername"". This causes the GUI to become responsive, giving me the fresh login screen. This is not optimal, however, at least it's a clean shutdown of programs. Alternately I can perform an ACPI shutdown and the system will shut down cleanly.
 
 - '''Full VM Hang''': The ''GUI inside the VM, XFCE, is not responsive. The VM is NOT active, as the activity indicators are inactive.'' A console can NOT be brought up (ctl-alt-F2 for example). Using the soft keyboard and trying the same has no effect. Sending ACPI shutdown signals has no effect. At the same time as this, ''sometimes the virtualbox GUI for managing the virtual machines hangs''. This can only be resolved by manually killing off the VM and anything virtualbox related, and rebooting the host.
 

'''VirtualBox information:'''

 - Version 6.1.16
 - Extension pack 6.1.16

'''Host information:'''

 - Windows 10 pro
 - Intel 4GHz corex CPU
 - 128GB RAM
 - Samsung SSD Disks
 - Nvidia GeForce RTX 2080 Ti using Nvidias drivers

'''Guest information:'''

 - Linux Mint 20
 - GUI: XFCE
 - Guest additions: 6.1.16
 - Virtual RAM: 9240 MB
 - Virtual processors: 6
 - Acceleration: default
 - Display: 128MB RAM, VMSVGA, Enable 3D Acceleration
 - Storage: SATA: Disk 1: Linux_Mint_19.vdi | Virtual size: 300GB | Actual size: 91GB
 - Storage: SATA: Disk 2: Linux_Mint_19_swap.vdi | Virtual size: 16GB | Actual size: 9GB
 
===

'''Issue Details:'''

Frequently after being away at least 10 or 15 minutes the guest will either experience a GUI freeze (see above for a description), or a full VM hang. The first situation can be recovered from, however in the second situation nothing can be done. For this reason I take frequent snapshots while the VM is powered on so that I can use them to restore from as setting everything back up again and again and again gets frustrating.

===

'''Solutions attempted:'''

Disable the screen saver / screen lock etc inside of the guest: The prior night I did this and returned in the morning to find that a full VM hang had taken place shortly after I had left to go to sleep. I know when it took place because of the time shown in the GUI (stuck).

Restore the latest snapshot, cleanly shut down, and power the VM on again: The issue still frequently occurs.

Disable 3D Acceleration: The issue still frequently occurs.


===

'''Logs:'''

''Note: For each of the logs, I prefix a string like ""round1"" and then refer to them that way. Please be sure to refer to them that way to me as well.''

The last log in round1 Vbox.log for this VM is: 
{{{
14:38:47.761976 GUI: UIMediumEnumerator: Medium-enumeration finished!
}}}


The full round1 Vbox.log will be attached. In addition I'll attach round1 VBox.log.1 , VBox.log.2 and VBox.log.3 .

round1 VBoxHardening.log doesn't really make sense to me so I'll just attach it.

Windows event log upon shutting down the host for round1, since it was both a full VM hang AND the virtualbox management interface became unresponsive:

{{{winlog.event_data.Caption:
    VirtualBox: VirtualBox.exe - Application Error
message:
    '''Application popup: VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
agent.hostname:
    MY-SYSTEM-NAME
agent.name:
    MY-SYSTEM-NAME
agent.id:
    130ce1c1-0e0a-419c-9b7f-f4bf70a6c377
agent.type:
    winlogbeat
agent.ephemeral_id:
    002ca6d2-1396-44b0-9a31-ec9b95be97bc
agent.version:
    7.9.0
winlog.record_id:
    2,049
winlog.computer_name:
    MY-SYSTEM-NAME
winlog.process.pid:
    16,852
winlog.process.thread.id:
    2,196
winlog.event_id:
    26
winlog.task:
winlog.provider_guid:
    {47bfa2b7-bd54-4fac-b70b-29021084ca8f}
winlog.channel:
    System
winlog.event_data.Message:
    '''The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
winlog.api:
    wineventlog
winlog.provider_name:
    Application Popup
winlog.opcode:
    Info
winlog.user.identifier:
    S-1-5-18
winlog.user.domain:
    NT AUTHORITY
winlog.user.name:
    SYSTEM
winlog.user.type:
    User}}}

===

'''Follow up:'''

What more can I provide to assist?",Fieldy
20062,Guru Meditation Fault,Windows,Linux,VirtualBox 6.1.16,2020-11-24T13:18:39Z,2020-11-24T13:18:39Z,"Received a Guru Meditation fault while running git status from the guest.
The Win 10 host was in the middle of its own startup activity and was quite busy. The Ubuntu 18.04 client had just started and was in the middle of an update when the fault occurred. Please see attachments.",TFR
20063,Resources misuse on Ubuntu 20.04LTS host with a Windows 10 guest,Linux,Windows,VirtualBox 6.1.16,2020-11-24T14:18:52Z,2020-11-24T14:18:52Z,After the '''update''' from 6.1.14 to 6.1.16 I'm observing a resources misuse on Ubuntu 20.04LTS. This means '''high RAM and CPU usage with no activity''' in the Windows 10 guest. Extension pack and guest additions have also been updated.,ProTerm
20064,Vista VM not functioning properly.,Windows,Windows,VirtualBox 6.1.16,2020-11-24T20:19:09Z,2020-11-24T20:19:09Z,"I have my windows Vista VM set up following the instructions of someone who’s been successful with vms, however, I can’t get past the loading screen before the vm gets a BSOD. [[Image()]]",MetaKnightmare
20065,VM Starting with grey screen,other,other,VirtualBox 6.1.16,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
20066,Error on starting 6.1 with windows  on Mac with Big Sur w,Mac OS X,other,VirtualBox 6.1.16,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
20068,Guru Meditation,Windows,Linux,VirtualBox 6.1.16,2020-11-26T06:12:00Z,2020-11-26T06:12:00Z,Guru Meditation Error in windows host and Kali guest,Aqua
20069,Error,Windows,Windows,VirtualBox 6.1.16,2020-11-26T12:27:18Z,2020-11-26T12:27:18Z,"Hey, 
I have got problem with virtual box. It whount start or install system. Only system i can install is windows xp but its very, very slow. I have got Windows 10 Pro 2004.",Daniel_Mandinec
19407,Extension Pack 6.1.4 Failed to install VERR_FILE_NOT_FOUND,Mac OS X,Windows,VirtualBox 6.1.4,2020-11-26T13:35:49Z,2020-11-26T13:35:49Z,"I'm on Mac OS X Yosemite 10.10.5 running VirtualBox 6.1.4

When trying to install Oracle_VM_VirtualBox_Extension_Pack-6.1.4.vbox-extpack , i faced Failed to install the Extension Pack /Users/..../Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.1.4.vbox-extpack.


{{{
﻿Failed to load the main module ('/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'): VERR_FILE_NOT_FOUND - dlopen(/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib, 6): no suitable image found. Did find:
/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib: code signature invalid for '/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'
}}}

Could someone please enlighten where i've gone wrong ? 
",writetokelvin
19510,Webcam Lenovo P50 doesn't work => insufficient information provided,Linux,Windows,VirtualBox 6.1.6,2020-11-27T18:06:02Z,2020-11-27T18:06:02Z,"I have a Lenovo P50, with 64Gb RAM, 1.5TB disk. It runs KDE Neon (so Ubuntu 18.04 LTS under the hood). But I have the same problem on LMDE 3, LMDE 4, since VB 5.1.22.

On all systems, the linux app cheese works properly and displays the video stream from the camera. 

Windows clients have 2 webcams, and I can attach both to a client. The first does not result in a recognised device, the second does, but the video stream shows a blue rectangle. 

The laptop runs intel video and NVidia (MX1000 I think). Makes no difference, same effect. Audio is currently working perfectly, no detectable lag. VM performance is overall good. Windows VM's run with 2 cpu's, 8192MB Ram, virtio NIC and Hyper-V interface. No other issues. 

Under Linux the camera shows as 
{{{
Listing available devices:
  video0   Integrated Camera: Integrated C
    Media controller device: /dev/media0
    Entity 1: Integrated Camera: Integrated C. Type: 65537, Revision: 0, Flags: 1, Group-id: 0, Pads: 1, Links: 0
      Device node
      Entity: 1, Pad 0, Flags: 1
  video1   Integrated Camera: Integrated C
    Media controller device /dev/media1 doesn't exist
ERROR: Unable to list device entities: Invalid device or device cannot be opened. (Code: 5)
}}}

Cheese sees only 1 device. VB sees 2. 

VBManage list usbhost yields this for the camera
{{{
UUID:               ffc18e87-da01-4b0b-a446-71749f1d68e2
VendorId:           0x04f2 (04F2)
ProductId:          0xb52c (B52C)
Revision:           0.41 (0041)
Port:               7
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co.,Ltd.
Product:            Integrated Camera
SerialNumber:       0001
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8//device:/dev/vboxusb/001/003
Current State:      Busy
}}}

VBoxManage list webcams gives me:
{{{
Video Input Devices: 2
.1 ""Integrated Camera: Integrated C""
/dev/video0
.2 ""Integrated Camera: Integrated C""
/dev/video1
}}}

Attaching 1 from the menu doesn't do anything. Attaching 2 does, a webcam is detected, but a blue screen image is all I see.

An external USB webcam works perfectly. I am assuming it is related to the double entry, the client device detection seems to trigger on /dev/video1, rather than /dev/video0. The host seems to be indicating that /dev/video1 is not the one to use. 
",ChrisMW
20072,uninstall option missing from help menu,other,other,VirtualBox 6.1.16,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
20030,linux guests cannot be restored,Linux,Linux,VirtualBox 6.1.16,2020-11-29T22:19:16Z,2020-11-29T22:19:16Z,"Unable to restore linux guest (Ubuntu) in linux host (Fedora Rawhide). Error ""Kernel driver not installed"" (even though the package is). Running akmods as recommended results in error (log attached).

System info - uname -r: 5.10.0-0.rc2.20201105git4ef8451b3326.64.fc34.x86_64
Specific VB packages: 6.1.16_RPMFusion r140961

This makes virtualbox completely unusable. Has persisted for ~a few weeks with diligent system updating on Fedora Rawhide.",xris
20054,network problems under bigsur macOS version,Windows,OSX Server,VirtualBox 6.1.16,2020-12-01T11:59:52Z,2020-12-01T11:59:52Z,"I have problems getting a working network connection when I transferred from Catalina to Bigsur

Sometimes VBOX crashes when I use NAT option for the adapter, normally use bridged option",pbvbox
19766,Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?,Windows,other,VirtualBox 6.1.10,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
20033,"In Windows 10 Host with Hyper-V, setting processor to 2 CPU, installation of Windows 2004 guest stuck at Windows logo",Windows,Windows,VirtualBox 6.1.16,2020-12-01T13:34:33Z,2020-12-01T13:34:33Z,"In Windows 10 Host (Windows 10 Home 20H2 and Windows 10 Home 2004), when setting processor to 2 CPU, installation of Windows 10 2004 guest stuck at Windows logo.

I have Hyper-V enabled, because I need to use WSL2 (which requires Hyper-V) and docker desktop (which requires WSL2).

Default processor is set to 1 CPU, Installation of Windows 2004 guest succeeded under 1 CPU, but it won't work with 2 CPU.

I have tested it in MacBook Pro 2020 Bootcamp and a Lenovo desktop PC, same results.",liuzhiyuan1225
16973,"Thunderbolt 3 Docks, VirtualBox needs new behavior model",Windows,Linux,VirtualBox 5.1.26,2020-12-02T06:19:52Z,2020-12-02T06:19:52Z,"My specific hardware.
* HP zBook 15 G3 Laptop
  * NIC: Intel Dual Band Wireless-AC 8260
  * NIC: Intel Ethernet connection I219-LM
* HP Elite Thunderbolt 3 Dock
  * NIC: Broadcom NetXtreme Gigabit Ethernet
* Host: Windows 7 Enterprise
  * Selected Bridged Adapter Intel PRO/1000 MT Desktop
* Guest: CentOS 7

**Situation**
* Thunderbolt 3 docking stations extend the PCIe such that new devices may appear when docked and disappear when undocked.
* One specific issue is with the NIC. While docked I use the NIC provided by the docking station.
* When undocked I use the Wireless NIC or the NIC on the motherboard.

**Issue**
* VirtualBox is unable to cope went the NIC in the dock completely disappears after undocking.
  * In Windows Device Manager the NIC does not appear
* It is also does not seem to hand gracefully when a Wireless NIC is disconnected from any network.
  * VirtualBox has no wireless bridge adapter option.

I hope this description is through enough.",J.R.
18872,I cannot enable second monitor,Windows,Linux,VirtualBox 6.0.10,2020-12-03T15:09:19Z,2020-12-03T15:09:19Z,"I set 2 displays in preferences. Linux starts with one. When I right click on the screen icon in the status bar, I see the second virtual display. Unfortunately, nothing happens when I click on ""Enable"".

linux xrandr 
{{{
Screen 0: minimum 1 x 1, current 1920 x 975, maximum 8192 x 8192
Virtual1 connected primary 1920x975+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x975      60.00*+
   2560x1600     59.99  
   1920x1440     60.00  
   1856x1392     60.00  
   1792x1344     60.00  
   1920x1200     59.88  
   1600x1200     60.00  
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.81  
   1152x864      75.00  
   1280x768      59.87  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
Virtual2 disconnected (normal left inverted right x axis y axis)
Virtual3 disconnected (normal left inverted right x axis y axis)
Virtual4 disconnected (normal left inverted right x axis y axis)
Virtual5 disconnected (normal left inverted right x axis y axis)
Virtual6 disconnected (normal left inverted right x axis y axis)
Virtual7 disconnected (normal left inverted right x axis y axis)
Virtual8 disconnected (normal left inverted right x axis y axis)
}}}




linux systemctl status vboxadd.service:
{{{
● vboxadd.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.0.11/init/vboxadd; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2019-08-28 10:31:45 CEST; 10min ago
  Process: 737 ExecStart=/opt/VBoxGuestAdditions-6.0.11/init/vboxadd start (code=exited, status=0/SUCCESS)
 Main PID: 737 (code=exited, status=0/SUCCESS)
    Tasks: 2 (limit: 4915)
   Memory: 216.7M
   CGroup: /system.slice/vboxadd.service
           ├─1231 VBoxClient --vmsvga
           └─1232 VBoxClient --vmsvga

Aug 28 10:31:42 ubuntu vboxadd[737]: modules.  This may take a while.
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: or
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Aug 28 10:31:45 ubuntu useradd[1166]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu useradd[1167]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu vboxadd[737]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Aug 28 10:31:45 ubuntu vboxadd[737]: the system is restarted
Aug 28 10:31:45 ubuntu systemd[1]: Started vboxadd.service.
}}}",Benmaxrei
20078,Trend FDE Post Login Fault,Linux,other,VirtualBox 6.1.16,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
20079,VRDP Forwarding Touchscreen Events (scrolling in Webbrowser),Windows,all,VirtualBox 6.1.16,2020-12-04T21:10:24Z,2020-12-04T21:10:24Z,"Hello, I tried to connect via VRDP into two machines (Ubuntu and Windows Server 2019). Both connections are working except of forwarding the touchscreen events form the host system. Both machines are configured as USB-Multitouch-Tablet. This problem only appears via VRDP. If I connect for example to the Windows Server 2019 with RDP (RDP Service form Guest OS), the touch events (for example one finger scrolling) are working as expected. Also if I start the machines normal (with GUI) die touch events are working. 

Is this a known issue?
Can I solve this with some additional config?

Thanks",strgey07
20080,Problem running Ubuntu VM,Windows,Linux,VirtualBox 6.1.16,2020-12-05T00:34:02Z,2020-12-05T00:34:02Z,"I was trying to set up Windows Subsystem for Linux on my laptop running on Windows 10. I switched on WSL options and restarted the machine. After that I started my Ubuntu VM on VirtualBox. It causes some errors and close the VM. I, then switches off the WLS which started the Ubuntu VM but recommended turning it off. Log file is attached herewith.",mshahin
20082,Virtualbox VM crashes with macOS Catalina host and High Sierra guest,Mac OS X,other,VirtualBox 6.1.16,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
19082,"VirtualBox Manager scaled *down*, when a mix of HiDPI and non-HiDPI screens are attached",Linux,all,VirtualBox 6.0.14,2020-12-06T07:48:12Z,2020-12-06T07:48:12Z,"Steps to reproduce:
1. Set up a machine with a mix of HiDPI and non-HiDPI screens
2. Start virtualbox
3. Observe failure

Expected result: The GUI of virtualbox looks normal
Also acceptable: The GUI is scaled up for the HiDPI screen

Observed behavior:
The GUI of virtualbox is scaled *down* by roughly a factor of two. Making the text hard to read even on a low-resolution screen. The virtual machines themselves are not impacted.

My setup:
VirtualBox Version is 6.0.14 r133895 (Qt5.6.1) on Debian 10 Buster. The device is a Lenovo T490 notebook, with an internal 14"" 1920x1080 (HiDPI) screen. The behavior is observed when attaching a low-res 1920*1200 external display, but not when attaching a HiDPI 3840*2160 display. The behavior occurs both with the Debian-Package, and with the distribution-agnostic installation. I am not aware of any custom configuration on my system that might impact this.

Additional notes:
I have posted about this on the forums here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=95297]. There are descriptions of similar behavior (may or may not be the same issue) here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=92965]; and here: [https://forums.virtualbox.org/viewtopic.php?f=7&t=88116]. All of these are recent. I first observed this behavior after installing an update using apt, however I do not know which version I had before that, sorry.

Temporary workaround:
Virtualbox can be forcibly scaled up by setting QT_SCALE_FACTOR=2, however this cannot be set globally, as it will break all other Qt-based applications. Also when this bug is not triggered (b/c only low-res or HiDPI screens are attached) the extra scaling will make everything unusably big.

Is there any log files that I should post to help reproduce this?",Nuvanda
20083,Import VM buttons below screen sized 1280x800,other,other,VirtualBox 6.1.16,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
19935,"When I try to install Windows Server 2019 with ISO, it goes to ""guru meditation state"".",other,other,VirtualBox 6.1.14,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
20085,MachineWrap,Windows,all,VirtualBox 6.1.16,2020-12-07T19:21:45Z,2020-12-07T19:21:45Z,"Hi Team,

For somewhat, I have had an issue with Virtualbox. This message has appeared when I start the VM. 

Here is the message:

'''''The virtual machine 'AppDynamics' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\ferna\VirtualBox VMs\AppDynamics\Logs\VBoxHardening.log'.


Código de Resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}'''''


Could you help me? I attached the logs here.

I already tried to uninstall and install again, but I haven't a success.

Kind Regards,
Fernando",fernandofot
20070,audio only works every other startup,Windows,Windows,VirtualBox 6.1.16,2020-12-09T00:12:07Z,2020-12-09T00:12:07Z,"If I have a VM with Windows 7 and I close and ""save the machine state"", then start it up again later, every other time I do that the audio/sound works. Every other time, it does not work. Occasionally, I can disable the virtual sound card within Windows and reenable it and it will work. Otherwise, I have to close the VM and restart it.
This happens with the current latest version of VirtualBox and has happened with multiple VMs and across several versions of VirtualBox.",RAR
20087,Sending multiple VBoxManage commands can cause VBox GUI to hang,Windows,Linux,VirtualBox 6.1.16,2020-12-09T08:37:53Z,2020-12-09T08:37:53Z,"We have scripts that issue multiple VBoxManage commands to start/stop VMs. Very often if multiple commands are sent and you interact with the UI (mostly with the VM that VBoxManage is acting upon) the GUI will freeze/hang indefinitely and often VBoxManage will as well. Terminating the GUI forcibly and restarting it makes it fine until you again single left-click on the VM in the UI upon which time it freezes again. Rebooting Windows makes VBox usable again but leaves the VMs in state aborted.

Staggering VBoxManage commands seems to be a workaround with at least partial success.",rdghickman
20088,Soft reset from guest does not reliably restart VM,Windows,Linux,VirtualBox 6.1.16,2020-12-09T08:43:00Z,2020-12-09T08:43:00Z,"On a Windows host with a Linux Debian 10 guest, issuing a ""reboot"" command to the guest OS does not seem to reliably restart the VM (although it does most of the time). When this fails, it results in a blank/black screen on the guest VM and nothing further happens. It is required that the user manually power off the VM and restart it from scratch.

For example, at this point the reboot trigger seems to be recognised from the logs:
00:01:48.843711 OHCI: Software reset
However, nothing further happens until 5 minutes later when I forcibly power it off:
00:06:59.972369 Console: Machine state changed to 'Stopping'

Logs are attached.",rdghickman
9223,A running VM is listed as Powered Off,other,other,VirtualBox 4.0.10,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
20086,VM crashed when updating Windows 10 guest,other,other,VirtualBox 6.1.16,2020-12-10T04:38:41Z,2020-12-10T04:38:41Z,See the logs attached.,fandrei
19296,No USB devices available to Win7/Win10 guests on Linux host [VBox 6.0.16],Linux,Windows,VirtualBox 6.0.16,2020-12-10T17:45:16Z,2020-12-10T17:45:16Z,"Under VirtualBox 6.0.14-133895, right-clicking on the USB icon on the VBox window status displays a menu showing a list of the USB interfaces/devices available on the host. Each entry in the list has a checkbox which can be used to assign the USB device to the Guest OS.

However, after upgrading to Version 6.0.16-135674 of VirtualBox, right-clicking on the USB icon does not show the list of USB interfaces/devices - instead it shows a menu list with the only entry of ""USB Settings..."" and a greyed-out entry stating ""No USB Devices Connected""

Although I discovered this issue when running Windows 7 and Windows 10 guest VMs, the same issue also arose when running an Ubuntu 16.04.6 guest VM too.

I have attached the following files:
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.14-133895
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.16-135674
- a zipped copy of the VM log for the Win10 guest, runing under VBox 6.0.16-135674.

My host system is a Lenovo Thinkpad E590 laptop with Intel Core i5-8265U CPU & 8Gb RAM, running Ubuntu 16.04.6.

I originally raised this as an issue on the forum, at [https://forums.virtualbox.org/viewtopic.php?f=7&t=96663&p=469555#p469555]",thoikix
20023,After Update to 6.1.16: Black screen after booting Ubuntu in fullscreen,Windows,Linux,VirtualBox 6.1.16,2020-12-11T08:01:49Z,2020-12-11T08:01:49Z,"I use Ubuntu 18.04.5 LTS (64-bit) as guest and Windows 10 as host and always do all VirtualBox-, Ubuntu and Windows-updates available. 

I boot into fullscreen mode. Since Upgrading to 6.1.16 after booting the screen is black. The boot screen-sequence (purple screen with Ubuntu logo and some text output) appears. But once the desktop should appear the entire display is black. Not the entire: At the bottom the VirtualBox-toolbar is available and accessable. Once I use it to switch to window-mode the screen refreshes and I can see and use the desktop. After that I'm able to re-activate the fullscreen mode and fullscreen works as expected.

If I boot in window-mode then the desktop is shown as expected. I also tried to boot without 3D acc. but the screen is also black without this setting.

Settings:
Mem: 24576 MB (host 32 GB)
CPUs: 12 (host 12)
CPU-limit: 95%
options: VT-x/AMD-V, Nested Paging, PAE/NX, KVM
Graphics: 128 MB, VMSVGA, 3D acc.
Storage: IDE: VBoxGuestAdditions.iso, SATA: mydisk.vdi (SSD enabled)
Audio: disabled
Network: 1 adapter Intel PRO/1000 MT Desktop (NAT)
USB: xHCI
Shared folders: 1

Host-OS: Windows 10
Host-graphics: GeForce RTX 2060, set NVIDIA 3D to use GeForce for virtualboxvm.exe instead of internal graphics of the laptop.",stevep
19952,Virtualbox 6.1.14 breaks compatibility on Mac OSX,Mac OS X,other,VirtualBox 6.1.14,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
20093,ubuntu doesnt starts,other,other,VirtualBox 6.1.16,2020-12-14T05:34:49Z,2020-12-14T05:34:49Z,coming black screen after starting the ubuntu os,mrun
19561,Nested virtualization BUG: soft lockup - CPU#4 stuck for 22s! [CPU 1/KVM:28838],all,Linux,VirtualBox 6.1.6,2020-12-16T07:19:30Z,2020-12-16T07:19:30Z,"I am running a KVM vm inside virtualbox. if the VM is set with 1 CPU, it works well. But if i increase the CPU to 2 or more, i am getting CPU stuck message inside virtualbox.

HOST OS: MAC OSX
Virtualbox Version: 6.1.6
Host have 12 cores and 64gb ram

Guest OS: Ubuntu 18.04
Guest CPU: 4
Guest Ram: 20GB
Nested VT-x/AMD-V and PAE/NX is enabled in processor settings

Nested VM Guest OS: debian
Nested VM Guest CPU: 2
Nested VM Guest Ram: 4GB

Partial syslog message and vbox.log is attached",hamerins
20052,Unable to start any VM since BigSur installation,other,other,VirtualBox 6.1.16,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
15845,e1000 Detected Tx Unit Hang,Windows,Linux,VirtualBox 5.1.2,2020-12-17T12:22:56Z,2020-12-17T12:22:56Z,"Hi,

My Arch Linux desktop (client) is sometimes hanging, seems like the kernel module is detecting a disconnection:
{{{
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: new request (0 scripts)
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: completed: no scripts
aug 22 11:25:08 virtwin chromium.desktop[1507]: [1507:1530:0822/112508:ERROR:connection_factory_impl.cc(369)] Failed 
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.2914] device (enp0s3): link disconnected (deferring 
aug 22 11:25:38 virtwin kernel: e1000 0000:00:03.0 enp0s3: Reset adapter
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3570] device (enp0s3): link connected
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3571] device (enp0s3): DHCPv4 lease renewal requeste
aug 22 11:25:38 virtwin kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): canceled DHCP transaction, DHC
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): state changed bound -> done
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3760] dhcp4 (enp0s3): activation: beginning transact
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3783] dhcp4 (enp0s3): dhclient started with pid 4117
aug 22 11:25:38 virtwin dhclient[4117]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67
aug 22 11:25:41 virtwin kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                                  Tx Queue             <0>
                                  TDH                  <1>
                                  TDT                  <9>
                                  next_to_use          <9>
                                  next_to_clean        <2>
                                buffer_info[next_to_clean]
                                  time_stamp           <10012adce>
                                  next_to_watch        <2>
                                  jiffies              <10012b100>
                                  next_to_watch.status <0>
}}}
I must admit I do all my work in this virtual machine, but I can't recall to have seen disconnects in Windows (the host).

Guest OS: Arch Linux
Kernel: 4.7.1-1-ARCH",LordChaos
20094,VB Blank screen after one day.,Windows,Linux,VirtualBox 6.1.16,2020-12-17T14:52:09Z,2020-12-17T14:52:09Z,"
While running VB version Versie 6.1.16 r140961 (Qt5.6.2) on Windows host computer (windows 10 pro) after one day the VB screen will turn blank.

Only closing the program and restarting it will show the regular screen again.

Is there a fix ?

[img]https://imgur.com/3s39bcD[/img]
",VB-box
10676,mount.vboxsf does not support generic userspace mount options (nofail),other,other,VirtualBox 4.1.16,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
20096,Crash when powering off guest OS,Windows,Linux,VirtualBox 6.1.16,2020-12-19T01:59:57Z,2020-12-19T01:59:57Z,"Host: Windows 10 build 17763 amd64
Guest: Ubuntu 18
1. Start guest OS
2. Sleep/resume host computer (not sure if this is necessary but seems related)
3. From within the guest OS, select the power off setting.
Message box appears: The instruction at 0x0000&FF9E4808561 referenced memory at 0x0000000000000021. The memory could not be written.

This crash is intermittent and happens prior to the screen resizing to the linux text-based shutdown screen (i.e. guest is still running X)",jkriegshauser
20097,VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) error,Linux,Windows,VirtualBox 6.1.16,2020-12-19T06:18:13Z,2020-12-19T06:18:13Z,"The VM-B works properly in Windows 10,
The VM-B is a link-clone VM of another VM-A.
I moved my working space '''from Windows to Linux''' in recently.
[[Image(https://i.loli.net/2020/12/19/UrqvuKlEnOZQbRT.png)]]

I installed newest VirtualBox on my Linux Desktop.
And the '''VM-A is working properly,''' (import from *.vbox file)
But the VM-B give an error message VBOX_E_OBJECT_NOT_FOUND.
[[Image(https://i.loli.net/2020/12/19/vIt5o8ZPUHVFubW.png)]]

And I tried register the seprated disk image for VM-B,
then VM-B works fine!
But the error VBOX_E_OBJECT_NOT_FOUND showns again when I restart VirtualBox.
I need register the seprated disk again to let it works.
[[Image(https://i.loli.net/2020/12/19/ijwGykchT7L4npN.png)]]


Linux OS: UOS V20 [Deepin V20 Commerical Version]
VirtalBox: 6.1.16 r140961 (Qt5.11.3)


i tried:
* remove old vbox file for VM-B and recreate it.
* import vbox file for VM-B again.
but no use.

Regards,
Pekaikon Norckon",dfc643
20100,BSOD caused by VirtualBox and USBNetworkGate,Windows,other,VirtualBox 6.1.16,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
20101,I can't stat my virtual box machine,other,other,VirtualBox 6.1.16,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
20107,VirtualBox crashes with hardened memory allocator Hardened Malloc on the host,Linux,all,VirtualBox 6.1.16,2020-12-29T12:53:04Z,2020-12-29T12:53:04Z,"When using hardened memory allocator [https://github.com/GrapheneOS/hardened_malloc Hardened Malloc] on the host operating system Debian `buster` VBoxSVC crashes after arround 30 minutes even during inactivity.

{{{
A critical error has occurred while running the virtual machine and the machine execution should be stopped.

For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log, which you can find in the virtual machine log directory, as well as a description of what you were doing when this error happened. Note that you can also access the above file by selecting Show Log from the Machine menu of the main VirtualBox window.

Press OK to power off the machine.
}}}

VirtualBox VM log:

{{{
all OK
no more log entries for 30 minutes while VM is working OK
then the only new log additions are these:
00:18:45.237389 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)
00:19:16.904964 VirtualBoxClient: detected working VBoxSVC (rc=NS_OK)
}}}

VBoxSVC.log

{{{
tail -f ~/.config/VirtualBox/VBoxSVC.log
}}}

{{{
all OK
no more log entries for 30 minutes while VM is working OK
no new log entry after crash
The log ends there after crash then becomes
~/.config/VirtualBox/VBoxSVC.log.1
}}}

Will a [https://www.virtualbox.org/wiki/Core_dump VirtualBox core dump] be required? Or something else? Is this a bug you would be interested in fixing or out of scope?

Hardened Malloc installed inside the VM is functional. Hardened Malloc on the host crashes VirtualBox after a while.

Could you please make VirtualBox compatible with Hardened Malloc?

VirtualBox compatibility with [https://github.com/GrapheneOS/hardened_malloc/issues/89#issuecomment-522236117 Hardened Malloc might be usable to reveal some memory corruption bugs] inside VirtualBox.",adrelanos
20004,Windows Server 2012 R2 guest freezes after each resume and some reboots,Windows,Windows,VirtualBox 6.1.14,2020-12-29T15:14:03Z,2020-12-29T15:14:03Z,"I have a Windows Server 2012 R2 guest I have used for several months, within the last month I began experiencing intermittent freeze ups of the guest.  I would have to power it down and restart.  Sometimes it would be stable the rest of the day but freeze after resuming it the next day.  Now it is freezing after every resume and sometime after restart.  I've gone back a few snapshots but not change.  Checking for updates says I am on the latest version.  No 3D acceleration enabled.  Host is Windows 10 Pro fully patched.  Guest if fully patched.  Minidump and log attached.",David Shower
20109,Guest Bridged Networking Stops Working After Host Link Was Down,Windows,Windows,VirtualBox 6.1.16,2020-12-31T00:11:39Z,2020-12-31T00:11:39Z,"I tested bridged networking on a Windows 10 Host with a Windows 7 64-bit Guest and a Windows XP 32-bit Guest.  They both exhibit the same problem with a bridged network adapter.  If the host's bridged link was down when the virtual machine was started, or goes down temporarily after the virtual machine is started, communication is lost through the bridged adapter on the host.  It is still possible to ping the host's address assigned to the real adapter, but no devices connected to the LAN on the real host adapter will communicate.

Virtual Network Adapter
Windows 7 64-bit Intel PRO/1000 MT
Windows XP 32-bit PCnet-FAST III

Host LAN Adapter Intel I219-V (1 Gb) VEN 0x8086 DEV 0x15B8
Host OS Windows 10 64-bit 10.0.19042

The work around for the problem is to temporarily disable and then enable the host LAN adapter using the Network Connections in the Control Panel.  Then disable and enable the virtual network adapter in the devices menu for the virtual machine.  After doing both of those things, the bridged adapter will communicate again.  I have noticed that it sometimes recovers if I just temporarily disable the network adapter for the virtual machine, but that seems to depend on whether the host adapter was up when the virtual machine was started.

I noticed this problem on a LAN port connected to a test network that normally has the switch powered off until I need to run tests.  If I power up the switch after starting the virtual machine then there is no communication to the network switch until I perform the steps that I outlined.",ErikWlfn
20110,Virtualbox looses track of USB SSD,Windows,Linux,VirtualBox 6.1.16,2020-12-31T06:45:36Z,2020-12-31T06:45:36Z,"I've encountered a big glitch. If I create a virtual machine with no virtual drive, and then use a USB filter to attach a USB SSD (WD Passport if it matters) to the virtual machine, then it will find that drive no problem for ONLY the first powercycle. Rebooting without powering down the machine makes no difference. But if you power the machine down (not save state, actually set the machine as turned off), then try to turn it on again, it won't find the SSD. It boots into the EFI shell, and the EFI shell reports no file systems, or it reports the Optical Disc file system if there is one. But it doesn't see the USB drive. The only way I've been able to fix this is to completely delete the machine and re-create from scratch. That's annoying and stupid!
",TheStudent
20111,"Drag and Drop not working: Windows 10(host), Fedora 33(guest)",Windows,Linux,VirtualBox 6.1.16,2020-12-31T15:26:22Z,2020-12-31T15:26:22Z,"Hi there,

I am working with VirtualBox 6.1.16 r140961 with a Windows 10 (1909) host and a Fedora 33 guest. Guest Additions are seemingly installed correctly. The clipboard is working fine bidirectionally.
Files drag and drop doesn't work in any direction.

Attached log files made as described here: https://www.virtualbox.org/wiki/DnDDebug

Thanks in advance and best regards
Pavel",nashoboima
19515,Virtualbox disconnects USB drives without first unmounting them,Mac OS X,all,VirtualBox 6.1.6,2020-12-31T23:22:43Z,2020-12-31T23:22:43Z,"I'm using a macOS 10.15.4 host with Virtualbox 6.1.6 with a Windows 7 guest. If I select a USB drive already mounted on the host to connect to the guest from the machine USB menu the drive gets suddenly disconnected without first unmounting it thus causing filesystem inconsistencies and data loss. The same thing happens with linux guests.

I'd happily attach a log but I'm afraid of losing data on my USB backup hard drive so I hope this is alright.

Thanks in advance.",gio91ber
20114,Crash on guest VM,Linux,Windows,VirtualBox 6.1.14,2021-01-01T13:40:31Z,2021-01-01T13:40:31Z,"I have a crash VM[[BR]]
Please solve bug ![[BR]]
I have installed microsoft net framework 4.0.[[BR]]
Guest : Windows XP[[BR]]


Thank
",Sizy458
20116,Windows 10 VirtualBoxVM guest crashes when updating Windows 10 inside,Mac OS X,Windows,VirtualBox 6.1.16,2021-01-04T17:31:01Z,2021-01-04T17:31:01Z,"My Windows 10 VirtualBoxVM guest crashed when running a Windows 10 update. An attempted boot after this also crashed. Booting in turn after the second crash resulted in a hang.

See attached log files.",Lars Sonchocky-Helldorf
17987,VirtualBox 5.2.18 vulnerable to spectre/meltdown despite microcode being installed,Linux,Linux,VirtualBox 5.2.18,2021-01-04T18:10:22Z,2021-01-04T18:10:22Z,"'''How to reproduce:'''

A host running Debian stretch.
Using VirtualBox version 5.2.18.
A guest running Debian stretch.

Host using stretch-backports with get access to newer microcode. (Old versions are incapable to show spectre/meltdown fixed.)

spectre-meltdown-checker being installed on host and in guest from stretch-backports. (Old versions are incapable to show spectre/meltdown fixed.)

{{{
sudo su -c ""echo -e 'deb http://http.debian.net/debian stretch-backports main contrib non-free' > /etc/apt/sources.list.d/backports.list""
}}}
{{{
sudo apt-get update
}}}
{{{
sudo apt-get -t stretch-backports install spectre-meltdown-checker
}}}

Suppose microcode being installed.

Intel:

{{{
sudo apt-get -t stretch-backports install intel-microcode
}}}

Amd:

{{{
sudo apt-get -t stretch-backports install amd64-microcode
}}}

Suppose running spectre-meltdown-checker on the host looks fine.

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

Suppose using all VirtualBox spectre/meltdown defense options.

{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-entry on
}}}
{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-exit on
}}}
{{{
VBoxManage modifyvm vm-name --spec-ctrl on
}}}
{{{
VBoxManage modifyvm vm-name --l1d-flush-on-sched off
}}}

(These options were introduced in VirtualBox version 5.2.18.)

'''Expected result:'''

spectre-meltdown-checker in guest VM saying ""all fine"".

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

'''Actual result:'''

spectre-meltdown-checker reporting vulnerable.

'''Questions:'''

Can you reproduce the same issue?

Were all necessary steps performed to protect the guest from spectre/meltdown?

Is this a VirtualBox issue or false-positive in spectre-meltdown-checker?

([https://forums.virtualbox.org/viewtopic.php?f=7&t=89395 Previously posted in VirtualBox forum].)",adrelanos
20117,Kernel 5.11 RC2: Error building modules with mainline kernel 5.11 RC2,other,other,VirtualBox 6.1.16,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
20115,Microsoft Office hangs when opening a file in a network share,Linux,Windows,VirtualBox 6.1.16,2021-01-07T07:44:09Z,2021-01-07T07:44:09Z,"Microsoft Office hangs when opening a .docx file in a network share.

Deactivating 3d acceleration does not solve the problem.

May be relate to [https://www.virtualbox.org/ticket/15513 this] although I am able to open the file, it hangs when I scroll it down.

VirtualBox Version 6.1.16 r140961 (Qt5.14.2)

'''HOST:'''

{{{
Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-33-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 15,5 GiB of RAM
Graphics Processor: GeForce GTX 1060/PCIe/SSE2
}}}

'''GUEST:'''

{{{
Edition	Windows 10 Education
Version	20H2
Installed on	‎12/‎6/‎2020
OS build	19042.685
Experience	Windows Feature Experience Pack 120.2212.551.0
}}}
",JohnJane
20075,No VirtualBox packages for Ubutnu 20.10 'Groovy',Linux,all,VirtualBox 6.1.16,2021-01-08T19:31:37Z,2021-01-08T19:31:37Z,"As of 2020-12-01 there are no VirtualBox DEB packages for
newly released (2020-10-22) Ubuntu version 20.10 'Groovy':

http://download.virtualbox.org/virtualbox/debian/dists/

VirtalBox packages for the previous Ubuntu release 20.04 'Focal'
require dependency package 'python-is-python2' to be installed,
but this breaks many other packages in Ubuntu 20.10, e.g. 'dh-python'.
",PHD
20118,Failed to create a proxy device for the USB device.,other,all,VirtualBox 6.1.16,2021-01-08T21:16:33Z,2021-01-08T21:16:33Z,"Hello,

after upgrading to 6.1.16 from 6.0.x USB mounting is not working anymore. The upgrade coincides with Mac OS upgrade to Big Sur version, after which my VirtualBox 6.0 stopped working. Now after upgrade to 6.1.16 I get the following message when trying to connect USB Storage 2.0 and 3.0 to any guest OS:


{{{
00:01:24.433251 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS)}, preserve=false aResultDetail=-2861
}}}

I have also installed Extensions pack matching 6.1.16 version. Do you know what might be causing the issue?

Thanks!
Dragan

",Dragan
20120,Guest container crashes,other,other,VirtualBox 6.1.16,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
20121,[Extension_Pack] Linux downloads the .gz extension file instead of .vbox-extpack,Linux,all,VirtualBox 6.1.16,2021-01-09T19:13:00Z,2021-01-09T19:13:00Z,"Oracle_VM_VirtualBox_Extension_Pack-6.1.16.gz

After manually modifying the file name extension, it was possible to install the package.

Link: https://download.virtualbox.org/virtualbox/6.1.16/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack



OS:
cat /etc/os-release
NAME=""Ubuntu""
VERSION=""20.04.1 LTS (Focal Fossa)""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 20.04.1 LTS""
VERSION_ID=""20.04""
HOME_URL=""https://www.ubuntu.com/""
SUPPORT_URL=""https://help.ubuntu.com/""
BUG_REPORT_URL=""https://bugs.launchpad.net/ubuntu/""
PRIVACY_POLICY_URL=""https://www.ubuntu.com/legal/terms-and-policies/privacy-policy""
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
",rh.silicon@…
20122,Ayuda para mac,other,other,VirtualBox 6.1.16,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
20123,"Please find attachment, VM not started",Linux,Linux,VirtualBox 6.1.16,2021-01-11T14:30:15Z,2021-01-11T14:30:15Z,,vijay.hambir
20124,Unable to add Guest Addition in macOS Big Sur 11.1,Windows,other,VirtualBox 6.1.16,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
20126,Crash when removing  vms from command line,Linux,all,VirtualBox 6.1.16,2021-01-13T11:32:19Z,2021-01-13T11:32:19Z,"When removing a VM from the command line, Virtualbox often crashes with a critical error when *other* VMs are running. The dialog says for those running (one for each window): ""A critical error has occurred while running the virtual machine and the machine execution should be stopped. [...] Press OK to power off the machine.""

The command executed is
$ vboxmanage unregistervm ""${childvm}"" --delete
where the variable ""childvm"" is a valid name of a VM.

The given log is:
--- start of log ---
Log created: 2021-01-13T10:42:27.425692000Z
Process ID:  3619370 (0x373a2a)
Parent PID:  12731 (0x31bb)
Executable:  /usr/lib/virtualbox/VBoxSVC
Arg[0]: /usr/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown
AddRef: illegal refcnt=3221225469 state=2
--- end of log ---

During the crash ""Oracle VM VirtualBox Manager"" always says data is unavailable. Sometimes the manager refreshes the data itself, other times you need to restart the manager.

",Mrpn
16808,Removed network adapters are still showing in bridged networking,Windows,all,VirtualBox 5.1.22,2021-01-13T16:15:05Z,2021-01-13T16:15:05Z,"When I run ""vboxmanage list bridgedifs"", I get a list of adapter that still contains adapters that are not in the system anymore. In my case, I used to have VLANs adapters that were created using the Intel ANS utility. The VLAN were since removed but are still showing in VirtualBox bridged networking. This is annoying.

In the log below, all adapters having a HardwareAddress of 00:00:00:00:00:00 are not in the system anymore but are still listed in all VirtualBox bridged networking list.

I tried removing and reinstalling VB, removing and reinstalling the NDIS6 Bridged Network Driver, nothing works, the old adapters are still showing up in the list. The Windows registry does not contain any references to the GUID of the removed adapters anymore. Why is VB still 

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage list bridgedifs
Name:            Intel(R) Ethernet I210-T1 GbE NIC
GUID:            da04ab21-b3e6-4bad-b6ad-497cfcd15188
DHCP:            Enabled
IPAddress:       192.168.4.170
NetworkMask:     255.255.255.3
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: a0:36:9f:cd:99:ad
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet
GUID:            42ffbcdd-fad9-4a1e-bc7f-de92582df835
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ
GUID:            dbc6c4c8-8e06-4b50-a0ba-b82766724257
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion
GUID:            d59e7f43-fc7f-4830-902a-74881b6354db
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
GUID:            146679e9-63c0-439f-a968-1545520a0e34
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
}}}

",viaujoc
20127,Finalize File System fails,Windows,Linux,VirtualBox 6.1.16,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,"Failed to finalize file system
",MikeTheBike
20133,Unable to delete or add extensions,Linux,all,VirtualBox 6.1.16,2021-01-18T14:54:54Z,2021-01-18T14:54:54Z,"When I try to remove an extension package, I have this error:

Failed to uninstall the Extension Pack Oracle VM VirtualBox Extension Pack.
Result Code: NS_ERROR_FAILURE (0x80004005)

When I want to add an extension package, clicks are inactive in the selection window.
Terminal says:
Qt WARNING: QWidgetWindow(0x558d168d1a20, name=""UIGlobalSettingsExtensionWindow"") must be a top level window.
Qt WARNING: We got some errors while running testparm ""Error loading services.""
Qt WARNING: We got some errors while running 'net usershare info'
Qt WARNING: ""Can't load /etc/samba/smb.conf - run testparm to debug it\n""
Qt WARNING: No node found for item that was just removed: QUrl(""file:///home/redhead/.Xauthority"")
Qt WARNING: QWidgetWindow(0x558d16db92b0, name=""UIGlobalSettingsExtensionWindow"") must be a top level window.

And if I click directly on the extension package, I have this error:
Failed to install the Extension Pack /home/redhead/Téléchargements/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack.
Result Code: NS_ERROR_FAILURE (0x80004005)











",-RedHead-
20134,Guest OS will not boot,Windows,all,VirtualBox 6.1.16,2021-01-18T18:45:00Z,2021-01-18T18:45:00Z,"Whenever I try to boot ''any'' guest OS, it will freeze and enter guru meditation. This happens on MBR and UEFI based guest OS.
",Pupilliam
20135,After installing Centos OS the VM is failing to reboot,Windows,Linux,VirtualBox 6.1.16,2021-01-18T21:52:15Z,2021-01-18T21:52:15Z,"The Host PC is Windows 10, after installing a Centos minimal image using vagrant the image fails to boot. There are obvious errors that in the log file.
I have installed an ubuntu vm and that works fine.

",harryv
20136,"upon resume getting ""VBoxClient: Crtc disable failed 63""",Windows,Linux,VirtualBox 6.1.16,2021-01-19T17:15:10Z,2021-01-19T17:15:10Z,"6.1.16 r140961 (Qt 5.6.2)

Sometime reactivating the ""full screen"" fixes it, sometimes I have to reboot",ralfhauser
19709,Windows 10 guest on Linux host aborts with VMSVGA3d OpenGL error 0x501 if 3D acceleration is enabled,Linux,Windows,VirtualBox 6.1.10,2021-01-19T17:33:39Z,2021-01-19T17:33:39Z,"Host is Ubuntu 20.04 with NVidia 440.100 drivers. Guest is Windows 10 version 1909. I enabled 3D acceleration to reduce high CPU usage on the host even if the guest was showing low CPU usage. After some time (an hour or so) the VM aborted with the error:

1:14:24.245508 VMSVGA3d: OpenGL error 0x501 (idActiveContext=0xffffeeee) on line 2331 glPixelStorei(GL_UNPACK_ALIGNMENT, pSave->iAlignment)
01:14:24.252162 VMSVGA3d: OpenGL error 0x501 (idActiveContext=0xffffeeee) on line 2331 glPixelStorei(GL_UNPACK_ALIGNMENT, pSave->iAlignment)
",gwiesenekker
20137,virtualbox manager does not work properly wit 4k monitors on Ubunto 20.04,Linux,Linux,VirtualBox 6.1.16,2021-01-19T22:11:37Z,2021-01-19T22:11:37Z,"When installed on a Ubuntu 20.04, virtualbox 6.1.16 runs as empty gray window. The method to fix it is to change scaling in displays settings from 200% to 100% or run it using the ""run_scaled"" script.
Also making the window smaller helps to an extent.

the same problem is related to running virtual machine window. With 200% scaling it has numerous graphical artifacts that prevent normal operation.",Lacek
20139,stealing focus while installing extension pack,other,other,VirtualBox 6.1.16,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
20144,Solaris host produce no sound in guest OSes,Solaris,all,VirtualBox 6.1.18,2021-01-20T16:36:58Z,2021-01-20T16:36:58Z,"Since VB v5.2.18 guests in Solaris have no sound, see:
https://forums.virtualbox.org/viewtopic.php?f=11&t=94108&p=490595#p490595

Steps to reproduce this regression :
-Install Solaris 11.4 (or 11.3) on bare metal
-Install latest VB version
-Install any OS, for instance Linux Ubuntu
Problem: Ubuntu guest have no sound. Win7 guest has no sound neither, and probably all other guest OSes?
",Brutalizer
20130,Calling launchVMProcess via vboxwebsrv causes VERR_ENV_INVALID_VAR_NAME,Linux,Linux,VirtualBox 6.1.16,2021-01-21T14:23:58Z,2021-01-21T14:23:58Z,"When Sending the SOAP request:


{{{
<soap-env:Envelope xmlns:soap-env=""http://schemas.xmlsoap.org/soap/envelope/"">
	<soap-env:Body>
		<ns0:IMachine_launchVMProcess xmlns:ns0=""http://www.virtualbox.org/"">
			<_this>692d166c1e430875-0000000000000004</_this>
			<session>692d166c1e430875-0000000000000003</session>
			<name/>
			<environmentChanges/>
		</ns0:IMachine_launchVMProcess>
	</soap-env:Body>
</soap-env:Envelope>
}}}


I get:


{{{
<SOAP-ENV:Envelope xmlns:SOAP-ENV=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:SOAP-ENC=""http://schemas.xmlsoap.org/soap/encoding/"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:vbox=""http://www.virtualbox.org/"">
	<SOAP-ENV:Body>
		<SOAP-ENV:Fault>
			<faultcode>SOAP-ENV:Client</faultcode>
			<faultstring>VirtualBox error: rc=0x80bb0005 Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME) (0x80bb0005)</faultstring>
			<detail>
				<vbox:RuntimeFault>
					<resultCode>-2135228411</resultCode>
					<returnval>692d166c1e430875-0000000000000005</returnval>
				</vbox:RuntimeFault>
			</detail>
		</SOAP-ENV:Fault>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
}}}


I am able to start the VM without messages via the GUI and with 
""vboxmanage startvm myvm01""

It does not look like any messages are added to the VM's log file, and the only thing added to VBoxSVC.log is


{{{
01:40:03.911204 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME)}, preserve=false aResultDetail=-752
}}}


All my soap calls to create the VM, query the power state, and power off the VM function.  My code did work as expected on version 5.1.

I also got the error on 6.1.14 and 6.1.12, I was unable to test prior versions due to compile errors when compiling the kernel modules.  I'm running on Ubuntu 20.04 with the ""virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb"" package downloaded from virtualbox's downloads.

My code can be found at:
https://github.com/T3kton/subcontractor_plugins/tree/master/subcontractor_plugins/virtualbox

the power on function is at:
https://github.com/T3kton/subcontractor_plugins/blob/master/subcontractor_plugins/virtualbox/client.py#L182

Thanks",pnhowe
20145,BSOD when a VM is shut down,Windows,Windows,VirtualBox 6.1.16,2021-01-22T04:38:45Z,2021-01-22T04:38:45Z,"This issue is not new, but finally I'm fed up. I thought that you get crash reports from Microsoft, but perhaps this is not the case. It's been perhaps a year that this been happening and no solution still.
At least 4 out of 5 times when a particular Windows 7 VM is shut down (not when it's restarted only), it causes the BSOD (memory corruption) on the Windows 10 host. It's more likely to happen when the VM has been running at least several hours, but this is not a requirement. The below info is from the debugger, but I don't know how to debug that, only providing this as a proof it's !VirtualBox (VBoxDrv.sys) that causes the crash.

{{{
BugCheck 1A, {1236, ffff8a871b92b000, ffff8a871b92b308, 242513}

* ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxDrv.sys - 
* ERROR: Symbol file could not be found.  Defaulted to export symbols for VMMR0.r0 - 
Probably caused by : memory_corruption


BUGCHECK_STR:  0x1a_1236

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80782747406 to fffff807827f5780

STACK_TEXT:  
fffff98f`33cdf518 fffff807`82747406 : 00000000`0000001a 00000000`00001236 ffff8a87`1b92b000 ffff8a87`1b92b308 : nt!KeBugCheckEx
fffff98f`33cdf520 fffff807`8271fc5b : ffff8a87`1b92b000 ffff87f2`00000000 ffffed80`06c6f390 ffff8a87`00000001 : nt!MiFreePagesFromMdl+0x4c2
fffff98f`33cdf5b0 fffff807`881be341 : ffff8a87`19ae7010 ffff8a87`1b530aa0 ffff8a87`1b931010 01000000`00100000 : nt!MmFreePagesFromMdl+0xb
fffff98f`33cdf5e0 fffff807`8818347b : ffff8a87`1b92d010 ffff8a87`1b530aa0 ffff8a87`1b931010 00000000`0d846602 : VBoxDrv!g_abRTZero4K+0x12bf1
fffff98f`33cdf610 fffff807`7ebd5f15 : ffff8a87`19ae7010 ffff8a87`19ae7010 ffff8a87`19ae7010 fffff807`8270f2b9 : VBoxDrv!RTR0MemObjFree+0xfb
fffff98f`33cdf640 fffff807`7ebd6a8f : ffff8a87`1b931010 ffff8a87`19ae7260 ffff8a87`16625000 fffff807`8818227c : VMMR0!GMMR0Term+0x645
fffff98f`33cdf6c0 fffff807`7ebd856a : 00000000`00002000 ffff8a87`19ae7018 ffff8a87`19e02010 ffff8a87`16625000 : VMMR0!GMMR0CleanupVM+0x25f
fffff98f`33cdf720 fffff807`7ebd8794 : ffff8a87`19e02030 ffff8a87`16625000 ffff8a87`19e02010 ffff8a87`19e02030 : VMMR0!GVMMR0DestroyVM+0x39a
fffff98f`33cdf750 fffff807`88161cc1 : ffff8a87`1100c8d0 00000000`00000055 ffff8a87`19e02030 ffff8a87`09e02000 : VMMR0!GVMMR0DestroyVM+0x5c4
fffff98f`33cdf7a0 fffff807`7ebd8465 : ffff8a87`16625000 00000000`00000003 00000000`00042000 fffff807`826501c1 : VBoxDrv!SUPR0ObjRelease+0x171
fffff98f`33cdf7d0 fffff807`7ebfe2a1 : 00000000`00000000 00000000`00000000 ffff8a87`171e07c0 00000000`00000000 : VMMR0!GVMMR0DestroyVM+0x295
fffff98f`33cdf840 fffff807`7ebff4ff : 00000000`00000021 00000000`00000000 00000000`00000000 fffff807`8266119e : VMMR0!ModuleInit+0x6e1
fffff98f`33cdf8a0 fffff807`88167bfb : ffff8a87`1d9e7010 ffff8a87`0f8331a0 00000000`00000000 ffff8a87`171e07c0 : VMMR0!VMMR0EntryEx+0x9f
fffff98f`33cdf910 fffff807`881760d4 : 00000000`00000030 fffff98f`33cdfcc0 00000000`00000030 ffff8a87`00000000 : VBoxDrv!SUPR0PageFree+0x296b
fffff98f`33cdf980 fffff807`829fcb82 : 00000000`0022821c fffff807`88175df0 00000000`09a3f848 ffff8a87`00000030 : VBoxDrv!SUPR0IoCtlPerform+0x25a4
fffff98f`33cdfa20 fffff807`829fc7e6 : ffff8a87`189897c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
fffff98f`33cdfb60 fffff807`828071b5 : ffff8a87`178f9080 fffff98f`33cdfcc0 00000000`09a3e4f8 fffff98f`33cdfbe8 : nt!NtDeviceIoControlFile+0x56
fffff98f`33cdfbd0 00007ffa`ad14c094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`09a3f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`ad14c094
}}}

I can provide more info (just ask), perhaps even upload the memory dump for analysis, but I don't have the skills to analyze the crash dump myself.
",Rafcio
20102,Unable to compile Guest Additions on Linux Kernel 5.4.80.,Windows,Linux,VirtualBox 6.1.16,2021-01-22T15:47:46Z,2021-01-22T15:47:46Z,"I am trying to install the guest additions for Linux, and I'm encountering a problem. I have Gentoo Linux with the 5.4.80 kernel, and I get MANY missing symbols. They are:

{{{
ERROR: ""ttm_bo_eviction_valuable"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_tt_fini"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_put"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_move_to_lru_tail"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_validate"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_add_to_lru"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_kmap"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_tt_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_dma_acc_size"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_init_mm"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_device_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_del_sub_from_lru"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_kunmap"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_device_release"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_manager_func"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_mmap"" [/tmp/vbox.0/vboxvideo.ko] undefined! 
}}}

Notice that all are in the vboxvideo.ko module.

Any tips are most appreciated.
",TheStudent
20147,Problems when masquerade is enabled on host,Linux,Linux,VirtualBox 6.1.16,2021-01-22T19:27:56Z,2021-01-22T19:27:56Z,"Steps to reproduce issue:

1. Configure host linux with firewalld  + enable masquerade on public zone (or configuration alike with iptables or nftables by hand)
2. Test access to both http and https on guest side
3. Disable masquerade on host and repeat 2

If netfilter masquerading is enabled on host, and guest is in bridge modem, both http and https don't work.

For example:

{{{

curl -I http://www.virtualbox.org
curl: (56) Recv failure: Connection reset by peer
root@techier-glossa:~# curl -I https://www.virtualbox.org
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to www.virtualbox.org:443
}}}


If I disable netfilter masquerading, it works.

In bridge mode it should not concern at all if host is doing that.

This the configuration of firewalld:

[root@munster ~]# firewall-cmd --zone=lxc --list-all   

{{{
lxc (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: lxcbr0
  sources: 
  services: 
  ports: 
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
[root@munster ~]# firewall-cmd --zone=libvirt --list-all
libvirt (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: virbr0
  sources: 
  services: dhcp dhcpv6 dns ssh tftp
  ports: 
  protocols: icmp ipv6-icmp
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule priority=""32767"" reject
[root@munster ~]# firewall-cmd --zone=public --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: wlp108s0
  sources: 
  services: dhcpv6-client kdeconnect mdns ssh
  ports: 
  protocols: 
  masquerade: yes
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

}}}



As far I know, In bridge mode it should not concern at all if host is doing that, should it?

Thanks in advance",sblk
20150,Guest additions VNC screen resize detection code fails,all,all,VirtualBox 6.1.18,2021-01-23T18:38:36Z,2021-01-23T18:38:36Z,"When accessing a client using VNC the code fails to detect a screen resize, meaning that clients can not be run 'headless', as the host has to be used to manually detect the resized screen.

This fault was introduced in 6.1.8, forcing me to continue to use 6.1.6 with the new versions of the other software, i.e. Virtualbox & Extension Pack.

p.s. A Debian client actually reports the error to the user.",Sysop
20081,Installing Linux subsystem on windows 10 caused read/write error inside running linux mint (in virtual box),Windows,Linux,VirtualBox 6.1.16,2021-01-24T12:07:45Z,2021-01-24T12:07:45Z,"I'm not used to write these, but if this is a real but, it's a serious one.

I don't have any log files, because during the search for a solution, things have been purged and reinstall many times.

but I'll try to describe as good as I can.

 Basically, I installed Linux subsystem on my windows 10 2004 machine.

Then I upgraded the wsl1 to wsl2 on windows.

Now after the night, I had some scripts running on my linux, scanning and identifying images /copying/sorting.

on the morning it had crashed, and in the terminal running the script it said something about ""segmentation fault core dumped""

I didn't realize it was so serious so I only restarted it. 

I got a few screenshots from a boot, don't remember what I booted, if it was a rescue disc or linux mint installation disc, but it shows some error info.

I uninstalled linux subsystem and Ubuntu 20 that I had installed on Windows, and tried to install linux mint on a new  virtual box, but after a while updates started to fail, and installation of software resulted in read/write error.

after a while I remembered that I didn't uninstall the wsl2 update from windows.

I uninstalled it, tried to reinstall linux mint, an now everything worked fine, no issues,  no errors, everything worked as it should.

so apparently did the wsl2 update interfere with how virtual box was accessing the .vdi files?

well, that's basically what happened.. sorry I can't give any logs, but this issue might be worth investigating..",Nemesis 77
20151,guru meditation appears when running two VMs,Linux,Windows,VirtualBox 6.1.16,2021-01-24T12:24:52Z,2021-01-24T12:24:52Z,"when running two vitualbox vms or a vitualbox vm and a vmware vm , the guru meditation will appears once in a while. When running only one vitualbox vm the prompt do not appears.
Version 6.1.14 and 6.1.16 reach the same ""guru meditation"" prompt.

Vmare works well no matter how many vms opened.
",rnaa
20095,Virtualbox still resets intel adapters,other,Linux,VirtualBox 6.1.14,2021-01-24T13:34:08Z,2021-01-24T13:34:08Z,"Using virtualbox 6.1.14 on linux host with linux guest makes intel driver to reset adapter.
This maybe duplicate but someone is closing not fixed bugs.
Seems like the bug is present from over 10 years.
I tried virtio but its not usable because after 2-3 days or so it just freez my virtual machines and they need to be power cycled. E1000 driver just makes disconnects way better. Using PCNet drivers are no option for me because i need gigabit connection.
",Sanitariu
20129,Linux kernel version 5.10 - we need changes,Linux,all,VirtualBox 6.1.16,2021-01-25T07:23:02Z,2021-01-25T07:23:02Z,"Linux kernel 5.10 won't work with the latest virtualbox 6.1.16, under Fedora 32/33.


/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjLinuxVMap’:
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:34: error: implicit declaration of function ‘alloc_vm_area’ [-Werror=implicit-function-declaration]
  560 |                 pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */
      |                                  ^~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:32: warning: assignment to ‘struct vm_struct *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
  560 |                 pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */
      |                                ^
   ./tools/objtool/objtool orc generate  --module --no-fp --retpoline --uaccess /tmp/vbox.0/SUPDrvTracer.o
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation


Thank you.


PS:
It seems like a common occurrence, first a new kernel is released, packaged and distributed to update repos, we update and discover that its not working, then wait 3-4 months for a new virtualbox. Maybe it would be possible to test future kernels earlier? 
",VirtualBarista
20106,AC97 possible regression in rev 76862,Linux,other,VirtualBox 6.1.16,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
19243,VMSVGA 3d get Crash while guest try to reboot,Windows,Linux,VirtualBox 6.1.2,2021-01-25T23:31:53Z,2021-01-25T23:31:53Z,"Graphic Controller VMSVGA get Problem while 3d Acceleration Enabled. Error Message show while Guest do reboot procedure. 



",Aridu68
19686,Guest audio loss following Windows host suspend,Windows,Linux,VirtualBox 6.1.10,2021-01-26T00:17:35Z,2021-01-26T00:17:35Z,"(Similar to, but distinct from, https://www.virtualbox.org/ticket/19267)

Background is here: https://forums.virtualbox.org/viewtopic.php?f=6&t=98365 but I'll put everything important in this ticket.

The bug only occurs on Windows hosts (W10 1909 tested) - Linux hosts are fine.

No amount of disabling/re-enabling Audio in the Manager will return the VM to a working state, but suspending the guest via its own mechanism and then resuming it generally effects recovery, so my (ignorant) gut feel is that something has changed in the timing or behavior VBox's handling of suspend/resume that's caused the audio pieces to not quite sync up (i.e. resumed before ready or etc).

I have some potentially-useful endpoints to reduce the bisection, in the 6.0 branch: LKG is 6.0.12, FKB is 6.0.22. (The bug is also in the 6.1 branch since at least 6.1.6, through to 6.1.10, but I don't have any working versions of 6.1 to provide the other end).

I've posted a VBox.log in the forums, which I can duplicate here (or recreate with 6.1.10 if you prefer) - I'm not sure what the preference is for attachments.

Cheers.",arQon
20153,No audio output with Windows 10 host/guest,Windows,Windows,VirtualBox 6.1.18,2021-01-26T10:18:47Z,2021-01-26T10:18:47Z,"Hello,
in the virtual machine no audio output is possible. The device manager doesn't show any missing drivers and everything looks normal.",OTonn
20125,Loggin vboxdrv.sh fills syslog,other,other,VirtualBox 6.1.16,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
20156,Windows BSOD,Windows,Windows,VirtualBox 6.1.18,2021-01-27T09:21:00Z,2021-01-27T09:21:00Z,"Host: Windows 10 v1909, Hyper-V enabled, Intel i7-4790 [[BR]]

Guest Windows 10 v20H2 (newly install), 1 vCPU, 4 GB RAM, Nested Paging disabled[[BR]]

Symptoms: Random BSOD on guest OS, with something like following in Vbox.log


{{{
00:01:06.583527 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0x1 P2=0x2 P3=0x0 P4=0xfffff8002069dfa3
00:01:06.583631 GIMHv: BugCheck a {1, 2, 0, fffff8002069dfa3}
00:01:06.583632 IRQL_NOT_LESS_OR_EQUAL
00:01:06.583633 P1: 0000000000000001 - memory referenced
00:01:06.583633 P2: 0000000000000002 - IRQL
00:01:06.583634 P3: 0000000000000000 - bitfield
00:01:06.583634     b0: 0 - read operation
00:01:06.583634     b3: 0 - execute operation
00:01:06.583634 P4: fffff8002069dfa3 - EIP/RIP
00:01:10.260332 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:10.933294 AHCI#0: Reset the HBA
}}}

",ACH
19235,GDM with (default) Wayland sessions are not usable,Windows,Linux,VirtualBox 6.1.2,2021-01-28T09:09:25Z,2021-01-28T09:09:25Z,"When GDM uses Wayland for its login screen, the screen does not update after it is initially drawn. You can log in 'blind', so the login screen itself is working, it's just that the screen is never updated.

Resizing the VM's window on the host causes the screen to be redrawn once only.

If set `WaylandEnable=false` in GDMs config file then I get a traditional Xorg-based login screen and all is well again. And before GDM starts, the (plymouth-based) splash screen works fine, and after I log in then my (Xorg-based) session works OK.

My VM is using VboxSVGA with 3d disabled.",Sam Morris
20159,Reproducible fatal crash of a Linux Mint 20 XFCE VM (VirtBox running on Win10),Windows,Linux,VirtualBox 6.1.18,2021-01-29T10:47:30Z,2021-01-29T10:47:30Z,"I have configured several virtual machines running the latest Linux Mint 20 XFCE4 edition. The display configuration is VMSVGA + 3D acceleration. After installing g++, make, and 6.1.8 guest additions I rebooted them. Then I installed the Atom editor. On every machine the same error occurred reproducibly: When I tore off a tab to attach it to another pane the vm crashed with an error message: 

The instruction at 0x00007FFE673EE652 referenced memory at 0x0000000000000000. 
The memory could not be written. 
Click OK to terminate the program. 

The error seems not to occur when I use another virtual graphics card, but due to the performance lack this is not solution to the problem. 

As I said: I have set up several machines from scratch, the error occurs everytime, absolutely reproducible within Atom. ",Dude McGee
20161,"VM running Windows 10 20H2 guest, VM one time freeze",Windows,Windows,VirtualBox 6.1.18,2021-01-29T18:39:34Z,2021-01-29T18:39:34Z,"Hi,
This hang occurred once. See attached for logs and minidumps for VirtualBoxVM processes in process tree. Host is Windows 10 20H2 64 bit
The guest was running a Remote Desktop Connection session and the Pulse Secure VPN application, which I left, then came back 50 minutes later to find it unresponsive, with black screen (that may be the last display from the RD client).",Mihai Hanor
20164,Error while trying to use VM for SAS University Studio,Windows,other,VirtualBox 6.0.22,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
19840,stable NS_ERROR_FAILURE on starting vm,Mac OS X,all,VirtualBox 6.1.10,2021-01-30T20:45:52Z,2021-01-30T20:45:52Z,"macos 10.13.6
VB throws stable error on starting of any VM (new or existing):

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

The problem has began after installing the last macos update 10.13.6
Compleete removing and reinstalling VB does't help.


",r5d1
19742,3D acceleration on Windows 10 guests apparently doesn't play nicely with some applications,Linux,Windows,VirtualBox 6.1.8,2021-01-31T18:32:34Z,2021-01-31T18:32:34Z,"Host: Ubuntu 18.04.04 LTS on Dell Precision T7610, Quadro K600
Guest: Windows 10 Pro Version 1909 Build 18363.959

Windows 10 guest machine is started with VBoxSVGA, 3D acceleration enabled. Start Rstudio Windows v1.2.5001. Main window contents appear inverted; see attached screenshot. 

Start Windows 10 guest with 3D acceleration disabled; application appears normal. Seems worth reporting even though I'm not 100% sure this isn't an Rstudio problem. 

",ekoski1
18477,Request for VBox to pass through Speculative Store Bypass (SSB) mitigations to guest => duplicate of #17987,Linux,Linux,VirtualBox 6.0.4,2021-02-01T15:42:31Z,2021-02-01T15:42:31Z,"Hi,

Using Host VirtualBox 6.0.4 on CentOS 7.6.

Guest also CentOS 7.6

On the Host

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp

but inside the Virtual Machine Guest

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable


Kindly check.",Thomas Stephen Lee
19839,Default Windows Unattend Template Requires Product Key,all,Windows,VirtualBox 6.1.10,2021-02-01T22:31:55Z,2021-02-01T22:31:55Z,"'''Problem''':

The default Windows answer file template (i.e., ""<vbox_install_dir>\UnattendedTemplates\win_nt6_unattended.xml"") requires a product key. Failure to provide the key results in Windows throwing the following error and aborting install, even if ""<AcceptEula>true</AcceptEula>"" is provided.

{{{
Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.
}}}

[[BR]]

'''Impact''':

This prevents users from performing unattended installs of Trial / Evaluation copies of Windows without additional (and non-intuitive) configuration. This is very difficult to troubleshoot as the Windows error message refers to licensing rather than product key / activation issues.

[[BR]]

'''Workaround''':

Creating a modified copy of the template, containing: 

{{{
<UserData>
    <AcceptEula>true</AcceptEula>
</UserData>
}}}

rather than the default:

{{{
<UserData>
    <ProductKey>
        <Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key>
        <WillShowUI>OnError</WillShowUI>
    </ProductKey>
    <AcceptEula>true</AcceptEula>
</UserData>
}}}


and referencing this during using --script-template="""" solves the problem.

Example: [[BR]][[BR]]
VBoxManage unattended install Server2019Template --user=Administrator --password=password --country=US --time-zone=MST --hostname=Server2019Template --image-index=2 --install-additions --start-vm=gui --iso=<ISO_PATH> --script-template=""<path_to_modified_template>\win_nt6_unattended.xml""

[[BR]]

'''Recommended Solution''':

Implement template conditional similar to ""@@VBOX_COND_IS_USER_LOGIN_ADMINISTRATOR@@"", that prevents the ""<ProductKey>"" block from appearing in the final XML answer file if no key is specified on the command-line for ""VBoxManage unattended install"".

If this cannot be fixed quickly, please at least update the documentation to mention this requirement and workaround.",breakid
20146,"High CPU Kernel usage for any golang project, Windows 10 Host, Hyper-V turn on",Windows,Linux,VirtualBox 6.1.18,2021-02-01T23:52:00Z,2021-02-01T23:52:00Z,"simple Vagrantfile for reproduce

{{{
# -*- mode: ruby -*-
# vi: set ft=ruby :

def total_cpus
  require 'etc'
  Etc.nprocessors
end


Vagrant.configure(2) do |config|
  config.vm.box = ""ubuntu/focal64""
  config.vm.box_check_update = false
  config.vm.synced_folder ""."", ""/vagrant""

  if Vagrant.has_plugin?(""vagrant-vbguest"")
    config.vbguest.auto_update = false
  end

  if Vagrant.has_plugin?(""vagrant-timezone"")
    config.timezone.value = ""UTC""
  end

  config.vm.provider ""virtualbox"" do |vb|
    vb.gui = false
    vb.cpus = total_cpus
    vb.memory = ""2048""
    vb.default_nic_type = ""virtio""
    vb.customize [""modifyvm"", :id, ""--uartmode1"", ""file"", File::NULL ]
    vb.customize [""modifyvm"", :id, ""--natdnshostresolver1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--natdnsproxy1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--ioapic"", ""on""]
    vb.customize [""guestproperty"", ""set"", :id, ""/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold"", 10000]
  end

  config.vm.provision ""shell"", inline: <<-SHELL
    set -xeuo pipefail
    export DEBIAN_FRONTEND=noninteractive

    # docker
    curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -
    add-apt-repository ""deb https://download.docker.com/linux/ubuntu $(lsb_release -cs) test""
    apt-get install --no-install-recommends -y docker-ce
    apt-get install -y linux-tools-generic linux-tools-$(uname -r) 

    MINIKUBE_VERSION=1.16.0
    wget -c --progress=bar:force:noscroll -O /usr/local/bin/minikube https://github.com/kubernetes/minikube/releases/download/v${MINIKUBE_VERSION}/minikube-linux-amd64
    chmod +x /usr/local/bin/minikube
    # required for k8s 1.18+
    apt-get install -y conntrack

    minikube config set vm-driver none
    minikube config set kubernetes-version ${K8S_VERSION}
    minikube start --download-only=true
    /home/vagrant/.minikube/cache/linux/v${K8S_VERSION}/kubeadm config images pull
    minikube start --wait-timeout=20m
  SHELL
end

}}}

minikube fail with timeouts

during start docker containers  and kubelet systemd service
perf top -F 100 -p <kubelet_pid>
perf top -F 100 -p <dockerd_pid>

show following pictures (see attach)

https://monosnap.com/file/97lWTmuXbD9zVQqBpnFtz1B8YVbz8z
https://monosnap.com/file/iJPQK6YeTjVRsn3xziaY9h6LOS9cFi

any other daemons works fine",Slach
19269,Hard Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Linux,Linux,VirtualBox 6.1.2,2021-02-02T03:03:30Z,2021-02-02T03:03:30Z,"Upgrading a fedora 28 guest to 31, at the reboot I get a guru
meditation fault.

It seems to be reproducible.

Initially, I was running VirtualBox 5.2.20 r125813 linux.amd64 (Oct 15 2018 17:11:04).
The fault is ""VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)""

I removed VirtualBox from the host and installed VirtualBox to 6.1.2 r135662 linux.amd64 (Jan 13 2020 12:43:05) and its extension pack.
I then attempted to boot the guest.

The fault is ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""

The host is Fedora 28 - the details are in your logs, attached.

I did not attach the .PNG files because they consist of (only) a black screen.

However, prior to that, I do see the splash screen, ""Welcome to Grub"",
then the crash.  I use a detachable start - but a ""normal"" start has
the same symptom.

This is a ""hard"" failure - every time I try to start this machine.


Both versions of VirtualBox were installed from download.virtualbox.org/virtualbox/rpm/fedora

I do not plan to revert to VirtualBox 5.*...
",Timothe Litt
20168,Linux guest / Mac host - uid option stopped working,Mac OS X,Linux,VirtualBox 6.1.18,2021-02-02T17:35:41Z,2021-02-02T17:35:41Z,"MacOS Catalina host, OpenSUSE Tumbleweed guest.

With Virtualbox 6.1.14, manually mounting a shared folder worked correctly with the ""uid"" option (owner of directories and files being set to the specified user).

After upgrading VBox, this parameter stopped working - mounted data is now owned by root.
Latest test done with VBox 6.1.18 host and 6.1.18 guest tools.

{{{
> sudo mount -t vboxsf -o uid=$UID,gid=100 macroot ~/files/macroot
> ls -ld /home/rich/files/macroot/Users/
drwxr-xr-x 1 root root 192 sep 22 00:27 /home/rich/files/macroot/Users/
}}}

This was discussed in SUSE bug https://bugzilla.suse.com/show_bug.cgi?id=1180761, with a working fix for Linux host in place - but apparently not working as expected on a Mac host.",Richlv
17604,"VM becomes ""inaccessible"" on re-launching GUI, Sharable VDI removed from media registry",Windows,Windows,VirtualBox 5.2.8,2021-02-03T13:47:07Z,2021-02-03T13:47:07Z,"Hello all,

Running into a ''very'' annoying problem, where my shareable vdi disk gets removed from the the VM (.vbox) xml on shutting down the VirtualBox Manager GUI -- resulting in my guest becoming ""inaccessible"" -- this has been happening for the past few versions (at least as far back as 5.2.6).
I can make the VM ""accessible"" again by manually specifying the shared disk in the .vbox file (or temporarily attaching the shared disk to another guest, to have it show up in the media registry).
As soon as I close/re-open the VirtualBox Manager GUI, my VM becomes ""inaccessible"" again.

Anyhow, here is the message I get:

{{{
A differencing image of snapshot {5912e4a6-b6c8-4ba7-ae4c-51b15512b9f5} could not be found. Could not find an open hard disk with UUID {662e4d2d-9085-4ecb-819e-f1f9875367e2}.
Result Code: 
E_FAIL (0x80004005)
Component: 
SnapshotMachine
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
}}}

When manually editing the .vbox file, this is what I have been adding... but it get's overwritten when cycling the VirtualBox Manager GUI:

{{{
<VirtualBox ...>
  <Machine ...>
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{662e4d2d-9085-4ecb-819e-f1f9875367e2}"" location=""C:\Users\{me}\VirtualBox VMs\Shared\ActivationsDisk.vdi"" format=""VDI"" type=""Shareable""/>
      </HardDisks>
      <.../>
    </MediaRegistry>
    <.../>
  </Machine>
</VirtualBox>
}}}

Any help/fixes would be greatly appreciated.

Thanks!
",pbouill
19989,VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33,Linux,Linux,VirtualBox 6.1.16,2021-02-03T20:19:45Z,2021-02-03T20:19:45Z,"VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33 with following error:

Erreur : 
 Problème: conflicting requests
  - nothing provides python(abi) = 3.8 needed by VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64


Test build VirtualBox-6.1.15-140899-Linux_amd64.run installs and works fine on Fedora 33.",Didier
20170,Highlighting of the active VMs,all,all,VirtualBox 6.1.18,2021-02-04T20:51:41Z,2021-02-04T20:51:41Z,"It would be very helpful for the list of VMs to somehow highlight which VMs are currently running.
Each VM already shows ""Running"", ""Powered Off"", etc, but with many VMs in the list it's easy to miss one, which causes headaches when trying to shut down the host computer.
",refactoror
19058,Main process crash after any client window close,Mac OS X,all,VirtualBox 6.0.14,2021-02-06T04:45:05Z,2021-02-06T04:45:05Z,"After the client window closes (via any way) the main processes crashes with,

Process:               VirtualBox [1185]
Path:                  /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
Identifier:            org.virtualbox.app.VirtualBox
Version:               6.0.14 (6.0.14)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           VirtualBox [1185]
User ID:               502

Date/Time:             2019-11-03 16:09:34.792 -0500
OS Version:            Mac OS X 10.14.5 (18F132)
Report Version:        12
Anonymous UUID:        EFB985F9-0C0F-03DF-3AAA-1C1A8FB9F720


Time Awake Since Boot: 570 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 0x0000729b13f76358
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [1185]

VM Regions Near 0x729b13f76358:
    Stack                  0000700004351000-00007000043d3000 [  520K] rw-/rwx SM=COW  thread 7
--> 
    MALLOC_TINY            00007fe4e0400000-00007fe4e0800000 [ 4096K] rw-/rwx SM=PRV  

Application Specific Information:
objc_msgSend() selector name: setSubmenu:


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib               	0x00007fff659fe69d objc_msgSend + 29
1   libqcocoa.dylib               	0x000000010c6e9c67 -[QCocoaMenuDelegate menu:updateItem:atIndex:shouldCancel:] + 327
2   com.apple.AppKit              	0x00007fff38c532da -[NSMenu _populateFromDelegateWithEventRef:] + 788
3   com.apple.AppKit              	0x00007fff38b386a5 -[NSMenu _populateWithEventRef:] + 81
4   com.apple.AppKit              	0x00007fff38c5236e -[NSCarbonMenuImpl _carbonPopulateEvent:handlerCallRef:] + 466
5   com.apple.AppKit              	0x00007fff38c520e2 NSSLMMenuEventHandler + 1193
6   com.apple.HIToolbox           	0x00007fff3a5999fe DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1422
7   com.apple.HIToolbox           	0x00007fff3a598daf SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 371
8   com.apple.HIToolbox           	0x00007fff3a598c35 SendEventToEventTargetWithOptions + 45
9   com.apple.HIToolbox           	0x00007fff3a5f25e7 SendMenuPopulate(MenuData*, OpaqueEventTargetRef*, unsigned int, double, unsigned int, OpaqueEventRef*, unsigned char, unsigned char*) + 318
10  com.apple.HIToolbox           	0x00007fff3a617e1f SendMenuOpening(MenuSelectData*, MenuData*, double, unsigned int, unsigned int, __CFDictionary*, unsigned char, unsigned char*) + 291
11  com.apple.HIToolbox           	0x00007fff3a73e1f0 _SimulateMenuOpening + 110
12  com.apple.HIToolbox           	0x00007fff3a733ff1 OpenMenuForInspection(MenuData*) + 94
13  com.apple.HIToolbox           	0x00007fff3a734dfb MenuData::HandleGetNamedAccessibleAttribute(unsigned long long, __CFString const*, unsigned int, OpaqueEventRef*) + 157
14  com.apple.HIToolbox           	0x00007fff3a734d48 MenuData::GetNamedAccessibleAttributeSelf(unsigned long long, __CFString const*, unsigned int, OpaqueEventRef*) + 180
15  com.apple.HIToolbox           	0x00007fff3a74dfab HIObject::DispatchAccessibilityEvent(OpaqueEventRef*, unsigned long long, AccessibilityHandlers const*, void*) + 489
16  com.apple.HIToolbox           	0x00007fff3a74dc82 HIObject::HandleClassAccessibilityEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 106
17  com.apple.HIToolbox           	0x00007fff3a599fe9 HIObject::EventHook(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 135
18  com.apple.HIToolbox           	0x00007fff3a5999fe DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1422
19  com.apple.HIToolbox           	0x00007fff3a598daf SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 371
20  com.apple.HIToolbox           	0x00007fff3a62eafc CallNextEventHandler + 105
21  com.apple.AppKit              	0x00007fff38e5cc87 -[NSCarbonMenuImpl _carbonGetAccessibleAttributeEvent:handlerCallRef:axElement:] + 37
22  com.apple.AppKit              	0x00007fff38c52053 NSSLMMenuEventHandler + 1050
23  com.apple.HIToolbox           	0x00007fff3a5999fe DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1422
24  com.apple.HIToolbox           	0x00007fff3a598daf SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 371
25  com.apple.HIToolbox           	0x00007fff3a598c35 SendEventToEventTargetWithOptions + 45
26  com.apple.HIToolbox           	0x00007fff3a645bec Accessible::SendEvent(OpaqueEventRef*, bool) const + 88
27  com.apple.HIToolbox           	0x00007fff3a64513f Accessible::GetNamedAttributeData(__CFString const*, void const*, void const**, unsigned char*) + 151
28  com.apple.HIToolbox           	0x00007fff3a644ee4 HLTBCopyUIElementAttributeValue + 57
29  com.apple.HIToolbox           	0x00007fff3a6474dc CarbonCopyAttributeValueCallback(__CFData const*, unsigned int, __CFString const*, void const**, void*) + 84
30  com.apple.AppKit              	0x00007fff38dd86ad CopyCarbonUIElementAttributeValue + 62
31  com.apple.AppKit              	0x00007fff38dd590a CopyAttributeValue + 126
32  com.apple.HIServices          	0x00007fff39b3635d _AXXMIGCopyAttributeValue + 269
33  com.apple.HIServices          	0x00007fff39b3f890 _XCopyAttributeValue + 424
34  com.apple.HIServices          	0x00007fff39b16c9d mshMIGPerform + 203
35  com.apple.CoreFoundation      	0x00007fff3b2c8597 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
36  com.apple.CoreFoundation      	0x00007fff3b2c84f5 __CFRunLoopDoSource1 + 527
37  com.apple.CoreFoundation      	0x00007fff3b2b04ec __CFRunLoopRun + 2524
38  com.apple.CoreFoundation      	0x00007fff3b2af8be CFRunLoopRunSpecific + 455
39  com.apple.HIToolbox           	0x00007fff3a59b96b RunCurrentEventLoopInMode + 292
40  com.apple.HIToolbox           	0x00007fff3a59b6a5 ReceiveNextEventCommon + 603
41  com.apple.HIToolbox           	0x00007fff3a59b436 _BlockUntilNextEventMatchingListInModeWithFilter + 64
42  com.apple.AppKit              	0x00007fff38935987 _DPSNextEvent + 965
43  com.apple.AppKit              	0x00007fff3893471f -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
44  com.apple.AppKit              	0x00007fff3892e83c -[NSApplication run] + 699
45  libqcocoa.dylib               	0x000000010c6e5eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
46  org.qt-project.QtCoreVBox     	0x0000000106171791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
47  org.qt-project.QtCoreVBox     	0x0000000106175b4a QCoreApplication::exec() + 346
48  org.virtualbox.app.VirtualBox 	0x0000000105db2b12 TrustedMain + 1314
49  org.virtualbox.app.VirtualBox 	0x0000000105db2b97 0x105dac000 + 27543
50  libdyld.dylib                 	0x00007fff671da3d5 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff673cd3f0 start_wqthread + 0

Thread 2:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff6731661a __select + 10
1   VBoxXPCOM.dylib               	0x000000010a0458b0 0x109fbb000 + 567472
2   VBoxXPCOM.dylib               	0x000000010a0476e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000010e4bae75 0x10e4a8000 + 77429
4   VBoxXPCOM.dylib               	0x000000010a04ca96 0x109fbb000 + 596630
5   VBoxRT.dylib                  	0x00000001097166dc 0x10962e000 + 952028
6   VBoxRT.dylib                  	0x00000001097c8162 0x10962e000 + 1679714
7   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 3:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x000000010a04adfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x000000010a04b2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010e4b37b8 0x10e4a8000 + 47032
5   VBoxXPCOM.dylib               	0x000000010a01f209 0x109fbb000 + 410121
6   VBoxXPCOM.dylib               	0x000000010a04ca96 0x109fbb000 + 596630
7   VBoxRT.dylib                  	0x00000001097166dc 0x10962e000 + 952028
8   VBoxRT.dylib                  	0x00000001097c8162 0x10962e000 + 1679714
9   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 4:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x00000001097c4a6c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010e5ca221 0x10e4d0000 + 1024545
4   VBoxRT.dylib                  	0x00000001097166dc 0x10962e000 + 952028
5   VBoxRT.dylib                  	0x00000001097c8162 0x10962e000 + 1679714
6   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   VBoxXPCOM.dylib               	0x000000010a04ade7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x000000010a04b2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010e4ad71b 0x10e4a8000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000010e4ad3ed 0x10e4a8000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x000000010e4b2039 0x10e4a8000 + 41017
7   VBoxXPCOM.dylib               	0x000000010a02e2fd 0x109fbb000 + 471805
8   VBoxXPCOM.dylib               	0x000000010a02d4fb 0x109fbb000 + 468219
9   VBoxGlobal.dylib              	0x000000010759a862 CEventSource::GetEvent(CEventListener const&, int) + 162
10  VBoxGlobal.dylib              	0x00000001073bb3e7 0x107309000 + 730087
11  org.qt-project.QtCoreVBox     	0x0000000105fb796b 0x105f8e000 + 170347
12  libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
13  libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
14  libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   VBoxRT.dylib                  	0x00000001097c4a6c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010e511d90 0x10e4d0000 + 269712
4   VBoxC.dylib                   	0x000000010e512fcd 0x10e4d0000 + 274381
5   VBoxC.dylib                   	0x000000010e6a49aa 0x10e4d0000 + 1919402
6   VBoxGlobal.dylib              	0x000000010759a862 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001073bb3e7 0x107309000 + 730087
8   org.qt-project.QtCoreVBox     	0x0000000105fb796b 0x105f8e000 + 170347
9   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
10  libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
11  libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 7:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff6730f22a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6730f76c mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff3b2b0bee __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff3b2b015c __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff3b2af8be CFRunLoopRunSpecific + 455
5   com.apple.AppKit              	0x00007fff3893d6a6 _NSEventThread + 175
6   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 8:
0   libsystem_pthread.dylib       	0x00007fff673cd3f0 start_wqthread + 0

Thread 9:: Dispatch queue: NSCGSDisableUpdates
0   libsystem_kernel.dylib        	0x00007fff6730f22a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6730f76c mach_msg + 60
2   com.apple.SkyLight            	0x00007fff60462105 CGSUpdateManager::enable_updates_common() + 577
3   com.apple.SkyLight            	0x00007fff604624a2 SLSReenableUpdateToken + 104
4   libdispatch.dylib             	0x00007fff6718c5f8 _dispatch_call_block_and_release + 12
5   libdispatch.dylib             	0x00007fff6718d63d _dispatch_client_callout + 8
6   libdispatch.dylib             	0x00007fff671938e0 _dispatch_lane_serial_drain + 602
7   libdispatch.dylib             	0x00007fff67194396 _dispatch_lane_invoke + 385
8   libdispatch.dylib             	0x00007fff6719c6ed _dispatch_workloop_worker_thread + 598
9   libsystem_pthread.dylib       	0x00007fff673cd611 _pthread_wqthread + 421
10  libsystem_pthread.dylib       	0x00007fff673cd3fd start_wqthread + 13

Thread 10:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   org.qt-project.QtCoreVBox     	0x0000000105fb9170 0x105f8e000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105fb8fab 0x105f8e000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105fb8e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001073e4059 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001073e41c0 0x107309000 + 897472
7   org.qt-project.QtCoreVBox     	0x0000000105fb796b 0x105f8e000 + 170347
8   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 11:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6731286a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff673d156e _pthread_cond_wait + 722
2   org.qt-project.QtCoreVBox     	0x0000000105fb9170 0x105f8e000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105fb8fab 0x105f8e000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105fb8e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001073e4059 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001073e41c0 0x107309000 + 897472
7   org.qt-project.QtCoreVBox     	0x0000000105fb796b 0x105f8e000 + 170347
8   libsystem_pthread.dylib       	0x00007fff673ce2eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff673d1249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff673cd40d thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x00000000ffffffff  rbx: 0x0000600002b32080  rcx: 0x0000000000000002  rdx: 0x0000000000000000
  rdi: 0x0000600002c36340  rsi: 0x00007fff394e2ef0  rbp: 0x00007ffee9e4ea30  rsp: 0x00007ffee9e4e9f8
   r8: 0x000000000000000a   r9: 0x0000000000000000  r10: 0x0000729b13f76340  r11: 0x00007fff394e2ef0
  r12: 0x0000000000000001  r13: 0x0000600003454ed8  r14: 0x0000600002c2cfc0  r15: 0x00006000026e6680
  rip: 0x00007fff659fe69d  rfl: 0x0000000000010202  cr2: 0x0000729b13f76358
  
Logical CPU:     0
Error Code:      0x00000004
Trap Number:     14


Binary Images:
       0x105dac000 -        0x105f04ff7 +org.virtualbox.app.VirtualBox (6.0.14 - 6.0.14) <28B40C01-A33D-3C94-9F33-1B437BC96BBE> /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
       0x105f76000 -        0x105f7fff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x105f8e000 -        0x1064b5ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10657e000 -        0x106a59ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x106b5a000 -        0x107063fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x1071dc000 -        0x107210fff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x107239000 -        0x107278fff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x1072a3000 -        0x1072f6fff +VBoxDDU.dylib (0) <425E29E4-3654-3466-9FA4-74595831D829> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x107309000 -        0x10943ffff +VBoxGlobal.dylib (0) <CC52AD54-E3B4-3B53-9E1A-7A8E944E35FF> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x10962e000 -        0x109b8f5e7 +VBoxRT.dylib (0) <C5B1604B-E6AF-38CF-96B2-97ED25DFBC4A> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x109cb4000 -        0x109f36fff +VBoxVMM.dylib (0) <02F0512A-A779-3AC5-896B-A824F1A0F97B> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x109fbb000 -        0x10a06cff7 +VBoxXPCOM.dylib (0) <4B77E0EB-C98A-38B9-9545-903EDE0007DD> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10c6c3000 -        0x10c802fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x10e220000 -        0x10e223ff7 +VBoxSVCM.dylib (0) <BA39D3BF-CEA7-3321-8615-AE868B2B95C4> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x10e232000 -        0x10e29c6ef  dyld (655.1.1) <CE635DB2-D47E-3C05-A0A3-6BD982E7E750> /usr/lib/dyld
       0x10e4a8000 -        0x10e4bffff +VBoxXPCOMIPCC.dylib (0) <09CCD92F-2AB6-3E5D-B826-A374C8B253D8> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x10e4d0000 -        0x10e8c8fff +VBoxC.dylib (0) <5721F352-F17F-3D3D-A25E-D16DFCDAA945> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x113a01000 -        0x113a04047  libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib
    0x7fff2fa8a000 -     0x7fff2fde3fff  com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <FBDF396C-3751-34C2-B452-F1449C583AE2> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff33a43000 -     0x7fff33ad4ff7  com.apple.driver.AppleIntelHD5000GraphicsMTLDriver (12.9.22 - 12.0.9) <CED88DF5-113F-3E62-9CB4-78847108335E> /System/Library/Extensions/AppleIntelHD5000GraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsMTLDriver
    0x7fff37193000 -     0x7fff37337ff7  com.apple.GeForceMTLDriver (12.0.23 - 12.0.0) <73AECFD0-94CA-3539-A720-B41F792B3E8A> /System/Library/Extensions/GeForceMTLDriver.bundle/Contents/MacOS/GeForceMTLDriver
    0x7fff37338000 -     0x7fff3733cfff  com.apple.agl (3.3.2 - AGL-3.3.2) <D1753A7C-4109-3778-BA57-9ED1BCED8EBC> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff376e7000 -     0x7fff376e7fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff376e8000 -     0x7fff376feff7  libCGInterfaces.dylib (506.22) <09E81708-D0A7-3AB6-9B7C-8245E33E27A3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff376ff000 -     0x7fff37d98fef  com.apple.vImage (8.1 - ???) <EFFD9A9C-5563-3762-91CA-9F50FDB7A547> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff37d99000 -     0x7fff38012ff3  libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff38013000 -     0x7fff38085ffb  libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff38086000 -     0x7fff3842fff3  libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff38430000 -     0x7fff38445feb  libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff38446000 -     0x7fff3844bff3  libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff3844c000 -     0x7fff384c8ff3  libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff384c9000 -     0x7fff384dcfe3  libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff384dd000 -     0x7fff386c4ff7  libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff386c5000 -     0x7fff38778ff7  libvMisc.dylib (671.250.4) <73637194-497A-39F9-90F5-004DA772AC69> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff38779000 -     0x7fff38779fff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff3891b000 -     0x7fff396d0ff3  com.apple.AppKit (6.9 - 1671.50.111) <933155DC-6404-3646-B6AE-087D34F611BE> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff39722000 -     0x7fff39722fff  com.apple.ApplicationServices (50.1 - 50.1) <4A6ACC13-2623-36B8-A196-2300980803CD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff39723000 -     0x7fff3978efff  com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff39827000 -     0x7fff3993efff  libFontParser.dylib (228.6.2.3) <3602D55B-3B9E-3B3A-A814-08C1244A8AE4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff3993f000 -     0x7fff39981fff  libFontRegistry.dylib (228.12.2.3) <2A56347B-2809-3407-A8B4-2AB88E484062> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff399db000 -     0x7fff39a0dfff  libTrueTypeScaler.dylib (228.6.2.3) <7E4C5D9C-51AF-3EC1-8FA5-11CD4BEE477A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
    0x7fff39a72000 -     0x7fff39a76ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <B53D557C-071F-3ED9-826A-847DEB465F62> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff39b11000 -     0x7fff39b63ff7  com.apple.HIServices (1.22 - 628) <26A8B7C0-41CC-3DB4-99D7-BD922866DC77> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff39b64000 -     0x7fff39b73fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff39b74000 -     0x7fff39bbdff7  com.apple.print.framework.PrintCore (14.2 - 503.8) <57C2FE32-0E74-3079-B626-C2D52F2D2717> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff39bbe000 -     0x7fff39bf7ff7  com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff39bf8000 -     0x7fff39c04fff  com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <80FA7439-EC77-3CEC-B5D1-5EFE9E503E11> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff39c05000 -     0x7fff39e7cff7  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <EB71583C-58C9-3CF8-92F9-2D57B24BBD4F> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff39e7e000 -     0x7fff39e7efff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <121176B6-7ABE-3AFB-A252-CCED694D98D4> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff3a1d6000 -     0x7fff3a577fff  com.apple.CFNetwork (978.0.7 - 978.0.7) <9FDEFE50-BE1B-386E-8B3C-AEF251069E52> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff3a58c000 -     0x7fff3a58cfff  com.apple.Carbon (158 - 158) <AC9E8C1E-2566-3C2C-8B6B-B5B4C9A1B8B7> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff3a58d000 -     0x7fff3a590ffb  com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff3a591000 -     0x7fff3a887ff7  com.apple.HIToolbox (2.1.1 - 918.5) <F7DA4F20-123B-30FB-9C27-5AB1746DEF63> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff3a888000 -     0x7fff3a88bff3  com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff3a88c000 -     0x7fff3a891ff7  com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff3a892000 -     0x7fff3a927ff3  com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff3a928000 -     0x7fff3a940ff7  com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff3a960000 -     0x7fff3a961ff7  com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff3a962000 -     0x7fff3a964ff7  com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff3a965000 -     0x7fff3a96bff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff3aa8d000 -     0x7fff3aa8dfff  com.apple.Cocoa (6.11 - 23) <9378783B-65FE-3E78-A7D5-0D11EE9117AE> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff3aa9b000 -     0x7fff3ab67ff7  com.apple.ColorSync (4.13.0 - 3340.7) <74B373AB-42C7-330D-A577-1C43BFA6024F> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff3acf3000 -     0x7fff3ad79fff  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <1E8E64E6-0E58-375A-97F7-07CB4EE181AC> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff3addd000 -     0x7fff3ae07ffb  com.apple.CoreBluetooth (1.0 - 1) <F08FE8C0-DD18-37E0-B707-3EF704A73FD6> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff3ae08000 -     0x7fff3b18cfe3  com.apple.CoreData (120 - 866.5) <37F35F2E-FE57-3E3F-A1E5-AD274A8C1FDE> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff3b18d000 -     0x7fff3b274ff7  com.apple.CoreDisplay (101.3 - 109.19) <B00A19C2-4A6A-388C-8AD6-33A42D10D7F0> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff3b275000 -     0x7fff3b6b9fff  com.apple.CoreFoundation (6.9 - 1575.12) <64C38BF2-1869-33C8-B1B6-DCA9C824C0E4> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff3b6bb000 -     0x7fff3bd4afe7  com.apple.CoreGraphics (2.0 - 1260.2) <23436C9A-7D62-3E9F-867A-798C93B52080> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff3bd4c000 -     0x7fff3c06cfff  com.apple.CoreImage (14.4.0 - 750.0.140) <96FA4D1B-AC88-305C-8F4D-D7D44657B733> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff3c369000 -     0x7fff3c46dff7  com.apple.CoreMedia (1.0 - 2288.40) <9BB054FB-68F1-3F03-A8B3-3E55471A6F9B> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff3c4ca000 -     0x7fff3c4cafff  com.apple.CoreServices (945 - 945) <E937BA69-19D5-3A30-B31E-8A6B94E9D9A0> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff3c4cb000 -     0x7fff3c547ff7  com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff3c548000 -     0x7fff3c81ffff  com.apple.CoreServices.CarbonCore (1178.32 - 1178.32) <52F5484E-94B1-37B7-B1AC-E210DF5721AE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff3c820000 -     0x7fff3c868ff7  com.apple.DictionaryServices (1.2 - 284.16.4) <C3D15FD1-759B-3815-8128-42D8220BC459> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff3c869000 -     0x7fff3c871ffb  com.apple.CoreServices.FSEvents (1239.200.12 - 1239.200.12) <8406D379-8D33-3611-861B-7ABD26DB50D2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff3c872000 -     0x7fff3ca24fff  com.apple.LaunchServices (945 - 945) <05FA145B-75AA-3AE6-BB82-F156B29F4FF1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff3ca25000 -     0x7fff3cac3ff7  com.apple.Metadata (10.7.0 - 1191.57) <BFFAED00-2560-318A-BB8F-4E7E5123EC61> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff3cac4000 -     0x7fff3cb0eff7  com.apple.CoreServices.OSServices (945 - 945) <119C5548-59C3-3F94-B23F-8AF02CA10EAA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff3cb0f000 -     0x7fff3cb76ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff3cb77000 -     0x7fff3cb98ff3  com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff3cea3000 -     0x7fff3d005ff3  com.apple.CoreText (352.0 - 584.26.3.2) <A99FD623-7F6E-3C77-8241-E98F664EC039> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff3d006000 -     0x7fff3d045fff  com.apple.CoreVideo (1.8 - 0.0) <1AD23C58-E68E-329B-A1FA-6BF7DD577687> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff3d046000 -     0x7fff3d0d5fff  com.apple.framework.CoreWLAN (13.0 - 1375.2) <F2EA31D8-53BF-32E8-B537-64B4F2BF4B6E> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff3d32c000 -     0x7fff3d331ffb  com.apple.DiskArbitration (2.7 - 2.7) <F481F2C0-884E-3265-8111-ABBEC93F0920> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff3d4f7000 -     0x7fff3d8a4fff  com.apple.Foundation (6.9 - 1575.12) <AD258ED7-64AE-367C-AE5F-48D45089D9F2> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff3d913000 -     0x7fff3d942ffb  com.apple.GSS (4.0 - 2.0) <E41430E5-713B-3E53-BF7E-A3991A881B62> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff3da42000 -     0x7fff3db4cfff  com.apple.Bluetooth (6.0.12 - 6.0.12f1) <58A607F0-A818-3535-A7BD-858D5BB0A807> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff3dbae000 -     0x7fff3dc3dfff  com.apple.framework.IOKit (2.0.2 - 1483.260.4) <CCA92450-8808-37EC-B68E-2C2846B086CE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff3dc3f000 -     0x7fff3dc4effb  com.apple.IOSurface (255.5.4 - 255.5.4) <83F58E47-0D06-3E78-9D19-D38D3205464B> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff3dca2000 -     0x7fff3de2dfef  com.apple.ImageIO.framework (3.3.0 - 1850.2) <E1CC52A4-1074-3997-849B-42EF20EE1ADC> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff3de2e000 -     0x7fff3de32ffb  libGIF.dylib (1850.2) <FB52622F-2A7D-36D0-B821-35DB2BAF9EE8> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff3de33000 -     0x7fff3df0ffef  libJP2.dylib (1850.2) <7FAC16D8-1144-30A1-BABC-008423C7A851> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff3df10000 -     0x7fff3df35feb  libJPEG.dylib (1850.2) <78401F6E-345B-3179-A82A-01F813F15D95> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff3e1f8000 -     0x7fff3e21efeb  libPng.dylib (1850.2) <FF3ABAE1-43F0-3A76-A284-398397693D46> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff3e21f000 -     0x7fff3e221ffb  libRadiance.dylib (1850.2) <92529333-0935-341B-B271-69C235FEF6B5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff3e222000 -     0x7fff3e26ffe7  libTIFF.dylib (1850.2) <FFC74F3B-16F9-38FE-9D3F-D8DC6DEDB9E9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff3f3e6000 -     0x7fff3f3fffff  com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff3f6b9000 -     0x7fff3f6c3fff  com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff3f773000 -     0x7fff3fe19ff7  com.apple.MediaToolbox (1.0 - 2288.40) <0629E756-3D2A-36A4-B25F-9C050FC859B5> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff3fe1b000 -     0x7fff3fec3ff7  com.apple.Metal (161.9.16 - 161.9.16) <A93AA7FC-B72A-3CBF-9932-81DDDFA1DFCD> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3fedf000 -     0x7fff3fefeff7  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <EE85B6D5-5C12-3CE8-8C33-54A203EDC76E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff3feff000 -     0x7fff3ff7bfe7  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <5A78F2DC-9D2B-37BA-B21F-ECFFCC6F7720> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3ff7c000 -     0x7fff3ffa3fff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <096DB3E6-7DDF-3B47-857A-46A203642ACF> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff3ffa4000 -     0x7fff400cfff7  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <D2128338-F1E8-3BEE-A729-AC13A524DD78> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff400d0000 -     0x7fff400eafff  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <ADA5A93C-F79E-3931-840D-48C6B6B305EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff400eb000 -     0x7fff400ecff7  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <515A92B3-A23B-3AC2-8D1B-85B248595B76> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff40ee3000 -     0x7fff40eefff7  com.apple.NetFS (6.0 - 4.0) <E917806F-0607-3292-B2D6-A15404D61B99> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff4398d000 -     0x7fff439e4ff7  com.apple.opencl (2.15.3 - 2.15.3) <AA9CE8F7-DB7C-35A5-A019-2207D1BBFF38> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff439e5000 -     0x7fff43a00ff7  com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff43a01000 -     0x7fff43a0cffb  com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff4435c000 -     0x7fff4435efff  libCVMSPluginSupport.dylib (17.7.2) <247121BB-626C-318E-B24E-3D436E752DF7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff4435f000 -     0x7fff44364ff3  libCoreFSCache.dylib (166.2) <222C2A4F-7E32-30F6-8459-2FAB98073A3D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff44365000 -     0x7fff44369fff  libCoreVMClient.dylib (166.2) <6789ECD4-91DD-32EF-A1FD-F27D2344CD8B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff4436a000 -     0x7fff44372ff7  libGFXShared.dylib (17.7.2) <B75A6E93-E5BE-32A8-8D46-00D8E909DFD3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff44373000 -     0x7fff4437efff  libGL.dylib (17.7.2) <E88FF023-7E15-3E95-88FD-6C415550F769> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff4437f000 -     0x7fff443b9fe7  libGLImage.dylib (17.7.2) <B4C140F3-AF8C-30C8-A03E-B16A20BB05A7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff4452d000 -     0x7fff4456bfff  libGLU.dylib (17.7.2) <EA69FA36-3F20-337C-A6B3-EC49DC2F12F5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff44f08000 -     0x7fff44f17ffb  com.apple.opengl (17.7.2 - 17.7.2) <8EFFA6F9-ABE8-3131-9D3F-37E9796DDF34> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff45d1a000 -     0x7fff45f70fff  com.apple.QuartzCore (1.11 - 699.27.4.1) <BB3BBD58-84DF-3849-B4ED-5FF8DA4015B8> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff467a5000 -     0x7fff46aa4fff  com.apple.security (7.0 - 58286.260.20) <59B4100E-5A31-3EF4-954A-2A69341995F3> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff46aa5000 -     0x7fff46b31fff  com.apple.securityfoundation (6.0 - 55185.260.1) <DB8EB672-5D3A-3082-A62E-4D75C81D94A4> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff46b63000 -     0x7fff46b67fff  com.apple.xpc.ServiceManagement (1.0 - 1) <4AD0F8EE-884C-3FA7-85D9-27F201BC3C64> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff46eff000 -     0x7fff46f6cfff  com.apple.SystemConfiguration (1.17 - 1.17) <1562078D-3251-31B2-B9C6-2667C567F883> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff471cb000 -     0x7fff4752aff7  com.apple.VideoToolbox (1.0 - 2288.40) <17BD9E7F-3B8E-3B62-BACE-AE04824F4B7B> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff4a1eb000 -     0x7fff4a290feb  com.apple.APFS (1.0 - 1) <C001DCC2-32BE-327A-AE03-281885BD93BF> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff4aca2000 -     0x7fff4aca3ff7  com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff4b2a1000 -     0x7fff4b2cdff7  com.apple.framework.Apple80211 (13.0 - 1380.2) <3850E3A9-E00A-374E-87EA-AB01E503E769> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff4b3f5000 -     0x7fff4b404fc7  com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff4b500000 -     0x7fff4b50bfff  com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff4b54c000 -     0x7fff4b595ff3  com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff4b7e9000 -     0x7fff4b80bfff  com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff4b8cf000 -     0x7fff4b91fff7  com.apple.AppleVAFramework (5.1.4 - 5.1.4) <63EBC1A7-25B5-3FF2-AA73-BB378B5FE8D4> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff4b96a000 -     0x7fff4b97effb  com.apple.AssertionServices (1.0 - 1) <11FC4241-6069-3B3A-9BCE-9B68F3A4D2AB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff4bd4d000 -     0x7fff4be39ff7  com.apple.AuthKit (1.0 - 1) <34496FD5-4BAB-3DF3-BF7F-70F38C66848D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff4bffb000 -     0x7fff4c003fff  com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff4c004000 -     0x7fff4c099fff  com.apple.backup.framework (1.10.5 - ???) <BAFC1D7F-9D75-3C45-AAD4-569D13E445C5> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff4c09a000 -     0x7fff4c107ff3  com.apple.BaseBoard (360.28 - 360.28) <DBE27FB4-3FFD-3E9A-846C-F6E7D797286A> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff4dd71000 -     0x7fff4dd7affb  com.apple.CommonAuth (4.0 - 2.0) <81C987FD-69EB-344B-94D9-B9D93624D257> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff4e213000 -     0x7fff4e5f6fef  com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x7fff4e5f7000 -     0x7fff4e625ff7  com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
    0x7fff4ea52000 -     0x7fff4ea63ff7  com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff4f00c000 -     0x7fff4f072ff7  com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
    0x7fff4f31f000 -     0x7fff4f327ff7  com.apple.CorePhoneNumbers (1.0 - 1) <7A826DA2-4725-39D8-AF27-6F034DC53C4E> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff4f4a3000 -     0x7fff4f4d4ff3  com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff4f89b000 -     0x7fff4f91ffff  com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff4f9af000 -     0x7fff4fadaff7  com.apple.coreui (2.1 - 499.10) <105F61F3-D0AE-332B-A485-8615187BB409> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff4fadb000 -     0x7fff4fc79fff  com.apple.CoreUtils (5.8 - 580.19) <CF9C5677-4946-3328-8CE3-C70F2E8599D8> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff4fccd000 -     0x7fff4fd30ff7  com.apple.framework.CoreWiFi (13.0 - 1375.2) <77E078A7-A34F-333B-B50F-8829537D6E9D> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
    0x7fff4fd31000 -     0x7fff4fd42ff7  com.apple.CrashReporterSupport (10.13 - 938.25) <C7665EC7-9389-3717-B152-A59D7872C63C> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
    0x7fff4fdd2000 -     0x7fff4fde1fff  com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
    0x7fff4fde2000 -     0x7fff4fde6fff  com.apple.DSExternalDisplay (3.1 - 380) <645C719D-05D4-3CD7-84D7-4C5218859E0C> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
    0x7fff4fe67000 -     0x7fff4fedcff3  com.apple.datadetectorscore (7.0 - 590.24) <72F0CBF1-D3E9-36C5-B877-F42E1EC59A0E> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff4ff28000 -     0x7fff4ff65ff7  com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
    0x7fff4ff66000 -     0x7fff500a1ff7  com.apple.desktopservices (1.13.5 - ???) <4AF2E011-2CB0-3588-83CB-882ADDA78CAD> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
    0x7fff50fde000 -     0x7fff513f9fff  com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
    0x7fff54cad000 -     0x7fff54caefff  libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib
    0x7fff5634e000 -     0x7fff56353fff  com.apple.GPUWrangler (3.40.16 - 3.40.16) <B9D4F2DD-5D11-32FF-B5BE-29E137458728> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
    0x7fff5715e000 -     0x7fff5716dfff  com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
    0x7fff572bd000 -     0x7fff57331ffb  com.apple.Heimdal (4.0 - 2.0) <5E8F6B79-960D-3030-B889-D29A4015D205> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff58620000 -     0x7fff58627ffb  com.apple.IOAccelerator (404.9 - 404.9) <F9C604B3-3DF7-3EE7-8A44-7877FAF2E6A4> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
    0x7fff5862b000 -     0x7fff58643fff  com.apple.IOPresentment (1.0 - 42.6) <55CB91EF-90F1-3D0A-A59E-2F75CD2EB4AE> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
    0x7fff589eb000 -     0x7fff58a18ff7  com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
    0x7fff58cac000 -     0x7fff58cbeff3  com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <5AAC527E-D197-39B2-A6C9-E0D0FB9CA9B9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
    0x7fff58cd9000 -     0x7fff58db4ff7  com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
    0x7fff58db5000 -     0x7fff58df1ff7  com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
    0x7fff58df8000 -     0x7fff58dfdfff  com.apple.LinguisticData (1.0 - 238.25) <61910887-D5CE-3567-9A5F-6DFEC942EC1F> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
    0x7fff5961b000 -     0x7fff5961efff  com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove
    0x7fff59af2000 -     0x7fff59b1aff7  com.apple.spotlight.metadata.utilities (1.0 - 1191.57) <38BB1FB7-3336-384C-B71F-4D0D402EB606> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities
    0x7fff59b1b000 -     0x7fff59ba8ff7  com.apple.gpusw.MetalTools (1.0 - 1) <DBC4718E-F588-382D-A415-405D0028804D> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
    0x7fff59bbe000 -     0x7fff59bd7ffb  com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset
    0x7fff59d55000 -     0x7fff59d70ffb  com.apple.MobileKeyBag (2.0 - 1.0) <4678FECE-538B-381C-80F2-27AA4805F160> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
    0x7fff59df9000 -     0x7fff59e23ffb  com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <3BF81F33-89A8-3A2D-84B3-B343020B6D98> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff5a05f000 -     0x7fff5a069fff  com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff5a8ca000 -     0x7fff5a91bff3  com.apple.OTSVG (1.0 - ???) <3976F8CC-1CFB-3E09-9009-FE985550565B> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG
    0x7fff5baa0000 -     0x7fff5baafff7  com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff5d93f000 -     0x7fff5d95dff7  com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
    0x7fff5daf5000 -     0x7fff5db45fff  com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit
    0x7fff5dc94000 -     0x7fff5dcb6fff  com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff5f4bb000 -     0x7fff5f5d9fff  com.apple.Sharing (1288.43 - 1288.43) <B9AB8C05-F2F2-371F-A9AF-1D139E2CE54C> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
    0x7fff603ea000 -     0x7fff60698ffb  com.apple.SkyLight (1.600.0 - 340.26) <CD2A7069-6CEA-3737-9E9D-7AE2FED912AB> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
    0x7fff60e3a000 -     0x7fff60e46fff  com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
    0x7fff614e5000 -     0x7fff61521ff3  com.apple.StreamingZip (1.0 - 1) <AF132752-3532-3BFD-8C32-8BA9D1B3449A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip
    0x7fff61597000 -     0x7fff61622fc7  com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
    0x7fff61b0a000 -     0x7fff61b16ffb  com.apple.TCC (1.0 - 1) <968ECAE1-FBB9-3478-BDCE-85E54B6C422D> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff61d7c000 -     0x7fff61e44ff3  com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
    0x7fff61f01000 -     0x7fff620b7ff7  com.apple.UIFoundation (1.0 - 551) <E9D17DAD-230D-390A-B117-3D100C5AF5F2> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
    0x7fff62d33000 -     0x7fff62e0cfff  com.apple.ViewBridge (401.1 - 401.1) <18144EC1-5DEF-369C-8EBA-2826E7142784> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge
    0x7fff635e3000 -     0x7fff635e6fff  com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap
    0x7fff639e7000 -     0x7fff639e9ffb  com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
    0x7fff639ea000 -     0x7fff639fffff  com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login
    0x7fff63cb3000 -     0x7fff63ce7fff  libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib
    0x7fff63cea000 -     0x7fff63cf4ff7  libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib
    0x7fff63d82000 -     0x7fff63d83ffb  libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff63dba000 -     0x7fff64011ff3  libFosl_dynamic.dylib (18.3.4) <45E50221-1A39-3AB3-8267-C1E4E39ECF83> /usr/lib/libFosl_dynamic.dylib
    0x7fff64062000 -     0x7fff64080fff  libMobileGestalt.dylib (645.260.6) <0232958E-1EF2-3627-B8FF-09C6522594C7> /usr/lib/libMobileGestalt.dylib
    0x7fff64081000 -     0x7fff64081fff  libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib
    0x7fff641c1000 -     0x7fff641c2ffb  libSystem.B.dylib (1252.250.1) <1A13E822-B59C-3A36-A2E4-9968149714F9> /usr/lib/libSystem.B.dylib
    0x7fff6423e000 -     0x7fff6423ffff  libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib
    0x7fff64251000 -     0x7fff64267ffb  libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib
    0x7fff64268000 -     0x7fff64291ffb  libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib
    0x7fff64292000 -     0x7fff64311fff  libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib
    0x7fff64315000 -     0x7fff64315ff3  libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib
    0x7fff643e5000 -     0x7fff643f5ffb  libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib
    0x7fff643f6000 -     0x7fff64403fff  libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib
    0x7fff64404000 -     0x7fff64457ff7  libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib
    0x7fff64458000 -     0x7fff6446dff7  libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib
    0x7fff6446e000 -     0x7fff6446eff3  libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib
    0x7fff6446f000 -     0x7fff6447fffb  libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib
    0x7fff64480000 -     0x7fff64498ffb  libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib
    0x7fff6470d000 -     0x7fff64723fff  libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib
    0x7fff64724000 -     0x7fff64725ff3  libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib
    0x7fff64bd1000 -     0x7fff64c27ff7  libcups.2.dylib (462.10) <2AC7B8C3-0D25-3E0F-A34A-94658A06FF94> /usr/lib/libcups.2.dylib
    0x7fff64d5b000 -     0x7fff64d5bfff  libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib
    0x7fff64d8d000 -     0x7fff64d92ff7  libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib
    0x7fff64d93000 -     0x7fff64d98ff7  libheimdal-asn1.dylib (520.260.1) <DC44D1D1-D3DF-38B3-AFC3-1D50B92BE401> /usr/lib/libheimdal-asn1.dylib
    0x7fff64dc3000 -     0x7fff64eb3fff  libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib
    0x7fff64eb4000 -     0x7fff65115fff  libicucore.A.dylib (62135.0.1) <2B292561-798A-381C-AA41-90EE6549C7CF> /usr/lib/libicucore.A.dylib
    0x7fff65162000 -     0x7fff65163fff  liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib
    0x7fff65164000 -     0x7fff6517cff3  liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib
    0x7fff65194000 -     0x7fff65238ff7  libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib
    0x7fff65239000 -     0x7fff6543dfff  libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib
    0x7fff65615000 -     0x7fff65966ff7  libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib
    0x7fff659f8000 -     0x7fff6617dfdf  libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib
    0x7fff6618f000 -     0x7fff66193ffb  libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib
    0x7fff66196000 -     0x7fff661cbfff  libpcap.A.dylib (79.250.1) <C0893641-7DFF-3A33-BDAE-190FF54837E8> /usr/lib/libpcap.A.dylib
    0x7fff662e4000 -     0x7fff662fcffb  libresolv.9.dylib (65.200.2) <893142A5-F153-3437-A22D-407EE542B5C5> /usr/lib/libresolv.9.dylib
    0x7fff6634d000 -     0x7fff6634eff7  libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib
    0x7fff6634f000 -     0x7fff6652cfe7  libsqlite3.dylib (274.25) <55CE34C4-00C0-3844-B7ED-80FA7F0AF03F> /usr/lib/libsqlite3.dylib
    0x7fff66745000 -     0x7fff66748ff7  libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib
    0x7fff66749000 -     0x7fff66756fff  libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib
    0x7fff6675b000 -     0x7fff6683dff3  libxml2.2.dylib (32.8) <54F896CF-6D83-300B-9CD9-1636BE5375A4> /usr/lib/libxml2.2.dylib
    0x7fff6683e000 -     0x7fff66866ff3  libxslt.1.dylib (16.1) <31F7018B-D8F2-36ED-A13B-1E5A16DFAAA1> /usr/lib/libxslt.1.dylib
    0x7fff66867000 -     0x7fff66879ff7  libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib
    0x7fff6705d000 -     0x7fff67061ff3  libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib
    0x7fff67062000 -     0x7fff6706cff3  libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib
    0x7fff6706d000 -     0x7fff67074ff7  libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib
    0x7fff67075000 -     0x7fff6707eff7  libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib
    0x7fff6707f000 -     0x7fff67103fc3  libcorecrypto.dylib (602.260.2) <BED0F385-D8A2-334A-BD7B-0673B5DABBC5> /usr/lib/system/libcorecrypto.dylib
    0x7fff6718a000 -     0x7fff671c3ff7  libdispatch.dylib (1008.250.7) <26DF5B1E-A388-38EF-B73B-AF0E93FB02DB> /usr/lib/system/libdispatch.dylib
    0x7fff671c4000 -     0x7fff671f0ff7  libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib
    0x7fff671f1000 -     0x7fff671f1ffb  libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib
    0x7fff671f2000 -     0x7fff671feff3  libkxld.dylib (4903.261.4) <71CF1ECD-AC4E-3FDD-BEDF-14933D843EEE> /usr/lib/system/libkxld.dylib
    0x7fff671ff000 -     0x7fff671ffff7  liblaunch.dylib (1336.261.2) <BD5CDB35-2BB4-349A-8D14-78E387563F89> /usr/lib/system/liblaunch.dylib
    0x7fff67200000 -     0x7fff67205fff  libmacho.dylib (927.0.2) <3C5C9024-45FD-38C2-B01A-07A322966063> /usr/lib/system/libmacho.dylib
    0x7fff67206000 -     0x7fff67208ffb  libquarantine.dylib (86.220.1) <6D0BC770-7348-3608-9254-F7FFBD347634> /usr/lib/system/libquarantine.dylib
    0x7fff67209000 -     0x7fff6720aff7  libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib
    0x7fff6720b000 -     0x7fff67222ff3  libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib
    0x7fff67223000 -     0x7fff67223ff7  libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib
    0x7fff67224000 -     0x7fff672abfff  libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib
    0x7fff672ac000 -     0x7fff672afffb  libsystem_configuration.dylib (963.260.1) <C7D2BA09-8D5B-3393-8D84-304D76C55DEF> /usr/lib/system/libsystem_configuration.dylib
    0x7fff672b0000 -     0x7fff672b3ff7  libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff672b4000 -     0x7fff672bafff  libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib
    0x7fff672bb000 -     0x7fff672c1ff7  libsystem_dnssd.dylib (878.260.1) <64B79B01-B1B0-3C7E-87A1-023B71843F1F> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff672c2000 -     0x7fff6730dffb  libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib
    0x7fff6730e000 -     0x7fff67336ff7  libsystem_kernel.dylib (4903.261.4) <7B0F52C4-4CC9-3282-8457-C18C6FE1B99E> /usr/lib/system/libsystem_kernel.dylib
    0x7fff67337000 -     0x7fff67382ff7  libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib
    0x7fff67383000 -     0x7fff673adfff  libsystem_malloc.dylib (166.261.1) <4D1CEF38-DE32-3ECF-9F70-0ADDD5C8775F> /usr/lib/system/libsystem_malloc.dylib
    0x7fff673ae000 -     0x7fff673b8ff7  libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff673b9000 -     0x7fff673c0fff  libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib
    0x7fff673c1000 -     0x7fff673cafef  libsystem_platform.dylib (177.250.1) <16949870-9152-3B0D-9EF0-40FAF84B0F1E> /usr/lib/system/libsystem_platform.dylib
    0x7fff673cb000 -     0x7fff673d5ff7  libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib
    0x7fff673d6000 -     0x7fff673d9ff7  libsystem_sandbox.dylib (851.260.2) <9CACC5F5-3859-3A1F-BCC6-96DDD4A556A8> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff673da000 -     0x7fff673dcff3  libsystem_secinit.dylib (30.260.2) <88F3CE61-5FAD-3CDA-AA13",Dunham
20172,boot issues,other,other,VirtualBox 6.1.18,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
20174,Installation of VMware Workstation Pro (might) have crippled my VirtualBox systems,Windows,Windows,VirtualBox 6.1.18,2021-02-08T14:44:59Z,2021-02-08T14:44:59Z,"I have like 10-12 different VMs under Oracle VM VirtualBox. Have used this for many years now, and is very pleased with functionality and possibilities.
Some month ago I had to install VMware Workstation Pro. After that, none of my VirtualBox machines are working ok. Some hangs until I have to abort them others are so slow, they never get into action. Today I uninstalled the VMware Workstation, but the problem is still present under VirtualBox. Now, I do not know for sure that is was VMware that destroyed my VirtualBox. I uninstalled and reinstalled VirtualBox also today, didn't help. Any idea what I should do to make VirtualBox behave under Win-10 (64b) again ?
Martin",MaP
20179,serial port freeze,Windows,other,VirtualBox 6.1.18,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
20108,Strange freeze in Linux host,Linux,Linux,VirtualBox 6.1.16,2021-02-12T15:41:47Z,2021-02-12T15:41:47Z,"I get a repeatable hang of the VM and the GUI with the following sequence:

1.- get https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.vmdk

2.- Create a new VM, 4G of RAM, the vmdk disk and _2_ vCPUs

3.- Start the VM

At one point in the boot process, the VM will stop producing output and when you try to stop it, the GUI will get blocked.

In parallel, I'm investigating why I can't assign 2 vCPUs to the VM using this image, but I'm worried that I can't just kill the VM and that the GUI gets blocked when I try so.

For the host:

uname -a                                                          
Linux paag-EliteBook 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
",paaguti-u
20184,VirtualBox - Ubuntu (20.04.1) error,other,other,VirtualBox 6.1.18,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
20185,Crush VM and GUI,Windows,Windows,VirtualBox 6.1.18,2021-02-13T16:15:51Z,2021-02-13T16:15:51Z,The program swore many windows about the error on each of the 2 running VMs.,Дмитро
20186,Program need tools for obsfucate logs and send it to developers.,other,other,VirtualBox 6.1.18,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.",Дмитро
20177,NtCreateFile(\Device\VBoxDrvStub) failed,other,other,VirtualBox 6.1.18,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
20188,"Network change cause bridged network broken, no adapters in bridged adapter.",Windows,all,VirtualBox 6.1.16,2021-02-14T15:20:32Z,2021-02-14T15:20:32Z,"OS: Windows 10 1909 18363.1316[[BR]]
VBox version: 6.1.16 r140961
----
Problem: (I guess) network changes might cause bridged network broken, like this:
[[Image(https://i.imgur.com/dtOqgNm.png)]]

All interfaces are gone in the bridged adapter. Only showing ""not selected""

----
How to reproduce:

Install/run/upgrade Nox player(a Android simulator, it's a VM that running android) while running the VirtualBox.

And I recorded a video to reproduce this bug: https://www.youtube.com/watch?v=RzTA-qMp3Uk

----
The only way to get bridged network back is upgrade VirtualBox or reinstall.
If I am using the latest VirtualBox, I have to uninstall it, then install it again. Very annoying.
Repair VirtualBox/reboot PC doesn't work.

I guess the installation/running process of Nox player changed some network setting, cause VirtualBox lost all of the network setting. And repair doesn't reconfigure it.

Is there any other way I can reconfigure network settings without reinstall? 
The only way to reconfigure it that I found is uninstall and install again, which makes me reboot my PC twice and reconfigure all vm again.

And pleasse fix this bug,thank you. The network of VM always crash after I running the Nox player. I can't use VirtualBox at all.",HuJK
20187,"Ubuntu 18.04 guest boots up 1 in 5 times. In other times, a cursor in blank screen blinking with no progress",Windows,Linux,VirtualBox 6.1.18,2021-02-14T19:36:46Z,2021-02-14T19:36:46Z,"Host OS Info:
Windows 10 Pro 64 bit, Version 1909
OS Build 18363.1316

Guest OS Info:
Ubuntu 18.04 64 bit
Attached is VM_Settings.PNG

Steps to reproduce:
1. Start the guest

Expected outcome: (This happens 1 in every 5 trials)
The guest boots up. The guest OS shows its desktop. 

Observed outcome: (This happens 4 times in every 5 trials)
A blank screen with a blinking cursor shows up. After a while, blinking stops, and the guest bootup process wont proceed. The blank screen will show indefinitely. If we see this happening, the only option is to kill the guest OS in Windows and then re-boot the host OS. During shotdown & reboot of the host os, the host OS may say ""Referencing to an illegal memory in VMWare"" or something like that. 






",TeddyTeddy
20190,Temp files not deleted after drog-drop,Windows,Windows,VirtualBox 6.1.18,2021-02-15T15:50:36Z,2021-02-15T15:50:36Z,"During dragging-dropping files from a (windows) VM to a (windows) host, a temporary directory is created in ""C:\Users\[USERNAME]\AppData\Local\Temp\VirtualBox Dropped Files""

After this, the files are copied to the selected destination dir. Unfortunately the temp dir is not being deleted after this action, causing the host drive to fill up (and potentionally crash the host because of a full system drive).

Could this deletion-after-coppying be included?",Gipster
20194,Host-only card cannot be created,Windows,Windows,VirtualBox 6.1.18,2021-02-15T20:02:12Z,2021-02-15T20:02:12Z,"Dear Team,

I should create an internal network for a uni project, but I cannot create host-only server for my debian virtual machine. Anything I do I keep receiving the below error message:

A gazda hálózati kártya létrehozása sikertelen.

Querying NetCfgInstanceId failed (0x00000002).

Eredmény kód: E_FAIL (0x80004005)
Komponens: HostNetworkInterfaceWrap
Interfész: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}


Virtualization is allowed, nothing is blocked.",Volodka91
19442,Autoformat pasted MAC address on adapter configuration dialog,Linux,Linux,VirtualBox 6.1.4,2021-02-16T00:58:27Z,2021-02-16T00:58:27Z,"For my home lab, I usually use the same MAC addresses for creating my VMs after reinstalling the host (bridged adapters)

To set the VMs up faster, I want to be able to copy-paste that information from my static DHCP config file to the MAC address field. The format in the DHCP config file is like AA:BB:CC:DD:EE:FF but VBox does not accept the "":"" character. When pasting such a string with CTRL+V into the MAC address field, it should accept the string and automatically remove the "":"" characters",prischnikov
17897,"Port forwardings can only be added, not deleted with ""VBoxManage natnetwork""",all,all,VirtualBox 5.2.12,2021-02-16T01:32:59Z,2021-02-16T01:32:59Z,"For ""natnetwork"" type network setups, port forwarding rules can be added with e.g.:

{{{
VBoxManage natnetwork modify --netname kommune1 --port-forward-4 ""...""
}}}

but, there is no corresponding way to remove an existing rule.

For ""nat"" type networks, both options exist:

{{{
VBoxManage modifyvm Name --natpf1 ""...""
VBoxManage modifyvm Name --natpf1 delete ""...""
}}}

I would like to see an option added to `VBoxManage natnetwork modify` that allows the deletion of rules by their name.

In the meantime, as a workaround, the documentation should suggest that rules can be manually removed from the configuration file `~/Library/VirtualBox/VirtualBox.xml` (on macOS, not sure about the path on other platforms).",damiano++
20195,error relaunching Virtual Box VM Process,other,other,VirtualBox 6.1.18,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
20196,Error while using VirtioSCSI through vboxwebsrv (Invalid controller type 11 (0x80070057)),Linux,Linux,VirtualBox 6.1.18,2021-02-16T10:52:37Z,2021-02-16T10:52:37Z,"Since the lsilogic SCSI controller intermittently crashes with kernel panic, we've tried switching to the new Virtio SCSI controller. 

However, while attempting to use the Java SDK to select this controller through vboxwebsrv, we get an error. This seems to be related to using vboxwebsrv, as selecting the virtio-scsi controller in the UI of Virtualbox or vboxmanage works as expected.

Since the virtio scsi controller is new in 6.1, we suspect that vboxwebsrv has not been modified to accept/handle the new controller type, but we can't be sure.

The error we get back is
{{{
VirtualBox error: rc=0x80070057 Invalid controller type 11 (0x80070057)
}}}

The Java code is:

{{{
IAppliance ova = vbox.createAppliance();
waitFor(ova.read(ovaName));
ova.interpret();
waitFor(ova.importMachines(List.of(ImportOptions.ImportToVDI)));
machine = vbox.findMachine(ova.getMachines().get(0));
ISession session = manager.getSessionObject();
machine.lockMachine(session, LockType.Write);
IStorageController storage = session.getMachine().getStorageControllers().get(0);
storage.setControllerType(StorageControllerType.VirtioSCSI);
session.getMachine().saveSettings();
}}}

The error happens on the line
{{{
storage.setControllerType(StorageControllerType.VirtioSCSI);
}}}

The vboxwebsrv log says:
{{{
00:00:37.787184 SQW01    -- entering __vbox__IStorageController_USCOREsetControllerType
00:00:37.787195 SQW01       findRefFromId(): looking up objref 97ccd3f131838cc7-0000000000000009
00:00:37.787200 SQW01       findComPtrFromId(): returning original IStorageController*=0x7FE6E8004570 (IUnknown*=0x7FE6E80046C0)
00:00:37.787203 SQW01       calling COM method COMSETTER(ControllerType)
00:00:37.787418 main     Pumping COM event queue
00:00:37.787613 main     Pumping COM event queue
00:00:37.787965 main     Pumping COM event queue
00:00:37.788172 main     Pumping COM event queue
00:00:37.788311 main     Pumping COM event queue
00:00:37.788450 main     Pumping COM event queue
00:00:37.788535 main     Pumping COM event queue
00:00:37.788619 main     Pumping COM event queue
00:00:37.788701 main     Pumping COM event queue
00:00:37.788762 SQW01       error, raising SOAP exception
00:00:37.788766 SQW01    API method name:            IStorageController::COMSETTER(ControllerType)
00:00:37.788767 SQW01    API return code:            0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788776 SQW01    COM error info result code: 0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788777 SQW01    COM error info text:        Invalid controller type 11
00:00:37.788840 main     Pumping COM event queue
00:00:37.788896 main     Pumping COM event queue
00:00:37.788899 SQW01       * ManagedObjectRef: MOR created for IVirtualBoxErrorInfo*=0x007fe6e8005070 (IUnknown*=0x007fe6e8007560; COM refcount now 4/2), new ID is 0xa; now 10 objects total
00:00:37.788906 SQW01    -- leaving __vbox__IStorageController_USCOREsetControllerType, rc: 0x80070057 (-2147024809)
}}}

Installed vboxwebsrv:
{{{
VirtualBox web service 6.1.18 r142142 linux.amd64 (Jan  7 2021 17:47:09) release log
}}}
",haster
20163,"kernel 5.10.11 panic at VM start, when CONFIG_DEBUG_SPINLOCK=y in kernel .config",Linux,X11,VirtualBox 6.1.18,2021-02-16T18:31:10Z,2021-02-16T18:31:10Z,"this is on app-emulation/virtualbox-6.1.18::gentoo

kernel 5.10.11

No panic when CONFIG_DEBUG_SPINLOCK=n (which means CONFIG_DEBUG_LOCK_ALLOC=n also)  

Also panic when using CONFIG_DEBUG_LOCK_ALLOC=y (which forces CONFIG_DEBUG_SPINLOCK=y)  

Still panic when CONFIG_DEBUG_SPINLOCK=y and CONFIG_DEBUG_LOCK_ALLOC=n  


This has been mentioned in a comment(thanks!) in https://www.virtualbox.org/ticket/20055#comment:16

I'm happy to test any patches, or if you think the issue is on the kernel side...

Here are my notes, I'm not sure how useful all this is but I'm happy to do more things if you tell me what:

Using /usr/src/.config.prev18_DEBUGlocks
      KERNEL: /var/crash/vmlinux-5.10.11-gentoo-x86_64-2021-01-29-01_35_09
    DUMPFILE: /var/crash/crashdump-2021-01-29-01_42_27  [PARTIAL DUMP]

Below, the word ""crash"" references https://github.com/crash-utility/crash

///
dmesg seen by crash's 'log' command:
{{{
...
[   27.789537] zram1: detected capacity change from 0 to 206158430208
[   27.792783] zram2: detected capacity change from 0 to 206158430208
[   27.807234] vboxdrv: loading out-of-tree module taints kernel.
[   27.807944] vboxdrv: Found 12 processor cores
[   27.808318] ------------[ cut here ]------------
[   27.808318] DEBUG_LOCKS_WARN_ON(lockdep_hardirqs_enabled())
[   27.808325] WARNING: CPU: 4 PID: 12692 at kernel/locking/lockdep.c:5281 check_flags.part.0+0x157/0x160
[   27.808325] Modules linked in: vboxdrv(O+) pcspkr
[   27.808328] CPU: 4 PID: 12692 Comm: modprobe Tainted: G     U     O      5.10.11-gentoo-x86_64 #1
[   27.808329] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   27.808330] RIP: 0010:check_flags.part.0+0x157/0x160
[   27.808331] Code: c0 0f 84 3f 9c 04 01 44 8b 0d 0d cf 7c 02 45 85 c9 0f 85 2f 9c 04 01 48 c7 c6 2f 22 d3 9a 48 c7 c7 cb e5 d1 9a e8 82 52 04 01 <0f> 0b e9 15 9c 04 01 66 90 41 57 41 56 49 89 fe 41 55 41 89 d5 41
[   27.808332] RSP: 0018:ffffb32948e37a10 EFLAGS: 00010082
[   27.808333] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
[   27.808334] RDX: 0000000000000000 RSI: ffffffff991424fc RDI: ffffffff9b065d40
[   27.808334] RBP: ffffffff9b768300 R08: 0000000000000001 R09: 0000000000000000
[   27.808335] R10: 0000000000000000 R11: fffffffffe02e9f8 R12: 0000000000000001
[   27.808335] R13: 0000000000000000 R14: ffffffff9b76c688 R15: 0000000000000046
[   27.808336] FS:  00007bcdb219fb80(0000) GS:ffff996609800000(0000) knlGS:0000000000000000
[   27.808337] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   27.808338] CR2: 00007bcdb232f445 CR3: 00000002d416e005 CR4: 00000000001706e0
[   27.808338] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   27.808339] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   27.808339] Call Trace:
[   27.808342]  ? lock_is_held_type+0x65/0x110
[   27.808344]  ? rcu_read_lock_sched_held+0x3a/0x70
[   27.808345]  ? lock_acquire+0x39a/0x480
[   27.808347]  ? ktime_get_ts64+0x46/0x280
[   27.808355]  ? VBoxHost_RTTimeSystemNanoTS+0x30/0x60 [vboxdrv]
[   27.808360]  ? VBoxHost_RTTimeSystemNanoTS+0x30/0x60 [vboxdrv]
[   27.808365]  ? supdrvLdrGetExportedSymbol+0x3342/0x3640 [vboxdrv]
[   27.808369]  ? supdrvGipCreate+0x820/0xc50 [vboxdrv]
[   27.808370]  ? rcu_read_lock_sched_held+0x3a/0x70
[   27.808371]  ? lockdep_init_map_waits+0x42/0x200
[   27.808375]  ? supdrvInitDevExt+0x14a/0x310 [vboxdrv]
[   27.808380]  ? init_module+0x91/0x1000 [vboxdrv]
[   27.808380]  ? 0xffffffffc0297000
[   27.808382]  ? do_one_initcall+0x7a/0x2d0
[   27.808383]  ? do_init_module+0x57/0x230
[   27.808384]  ? load_module+0x2445/0x26e0
[   27.808386]  ? __do_sys_finit_module+0xc0/0x100
[   27.808387]  ? do_syscall_64+0x33/0x40
[   27.808388]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   27.808388] irq event stamp: 5085
[   27.808390] hardirqs last  enabled at (5085): [<ffffffff99167cd5>] ktime_get_ts64+0x205/0x280
[   27.808390] hardirqs last disabled at (5084): [<ffffffff99167c9d>] ktime_get_ts64+0x1cd/0x280
[   27.808391] softirqs last  enabled at (5000): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808392] softirqs last disabled at (4995): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808392] ---[ end trace 3f8fdc7480d9e05c ]---
[   27.808393] possible reason: unannotated irqs-off.
[   27.808393] irq event stamp: 5085
[   27.808394] hardirqs last  enabled at (5085): [<ffffffff99167cd5>] ktime_get_ts64+0x205/0x280
[   27.808395] hardirqs last disabled at (5084): [<ffffffff99167c9d>] ktime_get_ts64+0x1cd/0x280
[   27.808395] softirqs last  enabled at (5000): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.808396] softirqs last disabled at (4995): [<ffffffff9a400eff>] asm_call_irq_on_stack+0xf/0x20
[   27.823374] zram3: detected capacity change from 0 to 206158430208
[   27.824878] vboxdrv: TSC mode is Invariant, tentative frequency 3714564013 Hz
[   27.830217] xhci_hcd 0000:00:14.0: Cancel URB 00000000493c99df, dev 14, ep 0x81, starting at offset 0xfff92010
[   27.831594] vboxdrv: Successfully loaded version 6.1.18 (interface 0x00300000)
[   27.833271] xhci_hcd 0000:00:14.0: // Ding dong!
...
[   57.854519] elogind-daemon[13194]: New session 2 of user user.
[   62.295045] i2c i2c-1: NAK from device addr 0x50 msg #0
[   62.298587] i2c i2c-0: NAK from device addr 0x50 msg #0
[   62.302129] i2c i2c-2: NAK from device addr 0x50 msg #0
[   62.331645] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0
[   62.344256] snd_hda_intel 0000:00:1f.3: PME# disabled
[   71.473189] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x0 (reading 0xa2f08086)
[   71.473206] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x4 (reading 0x100406)
[   71.473215] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x8 (reading 0x4030000)
[   71.473223] snd_hda_intel 0000:00:1f.3: saving config space at offset 0xc (reading 0x2010)
[   71.473230] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x10 (reading 0xfff20004)
[   71.473238] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x14 (reading 0x2f)
[   71.473258] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x18 (reading 0x0)
[   71.473260] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x1c (reading 0x0)
[   71.473263] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x20 (reading 0xfff00004)
[   71.473265] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x24 (reading 0x2f)
[   71.473267] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x28 (reading 0x0)
[   71.473270] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x2c (reading 0x87241043)
[   71.473272] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x30 (reading 0x0)
[   71.473274] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x34 (reading 0x50)
[   71.473277] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x38 (reading 0x0)
[   71.473279] snd_hda_intel 0000:00:1f.3: saving config space at offset 0x3c (reading 0x10b)
[   71.473297] snd_hda_intel 0000:00:1f.3: PME# enabled
[   71.485469] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot
[   72.024850] SUPR0GipMap: fGetGipCpu=0x1b
[   73.474107] BUGGY: kernel NULL pointer dereference, address: 0000000000000004
[   73.474120] #PF: supervisor read access in kernel mode
[   73.474126] #PF: error_code(0x0000) - not-present page
[   73.474131] PGD 0 P4D 0 
[   73.474143] Oops: 0000 [#1] SMP NOPTI
[   73.474151] CPU: 2 PID: 14833 Comm: EMT-0 Kdump: loaded Tainted: G     U  W  O      5.10.11-gentoo-x86_64 #1
[   73.474157] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   73.474174] RIP: 0010:do_raw_spin_lock+0x4/0x90
[   73.474181] Code: 48 8d 88 b8 06 00 00 48 c7 c7 58 48 d3 9a e8 79 3a 04 01 e9 5b 3b 06 01 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 53 48 89 fb <8b> 47 04 3d ad 4e ad de 75 46 48 8b 53 10 65 48 8b 04 25 00 6f 01
[   73.474187] RSP: 0018:ffffb3294a0ebd30 EFLAGS: 00010296
[   73.474194] RAX: ffffffff992838a1 RBX: 0000000000000000 RCX: 0000000000000000
[   73.474199] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[   73.474204] RBP: ffffb3294a0ebdf8 R08: 0000000000000001 R09: 0000000000000000
[   73.474209] R10: ffffffffc026f760 R11: 000000000007b438 R12: ffffffffc0240080
[   73.474213] R13: ffffb3294bea1000 R14: 0000000000000001 R15: ffffb3294a0ebde0
[   73.474220] FS:  0000754d3c1f4640(0000) GS:ffff996609600000(0000) knlGS:0000000000000000
[   73.474225] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   73.474230] CR2: 0000000000000004 CR3: 00000002d7102004 CR4: 00000000001706e0
[   73.474234] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   73.474239] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   73.474243] Call Trace:
[   73.474255]  ? __apply_to_page_range+0x2e1/0x6a0
[   73.474286]  ? rtR0TermNative+0xd0/0x220 [vboxdrv]
[   73.474313]  ? rtR0MemObjNativeProtect+0x74/0xa0 [vboxdrv]
[   73.474338]  ? VBoxHost_RTR0MemObjProtect+0x81/0xc0 [vboxdrv]
[   73.474360]  ? supdrvIOCtl+0x3265/0x3800 [vboxdrv]
[   73.474379]  ? SUPR0Printf+0x22f/0x330 [vboxdrv]
[   73.474388]  ? __x64_sys_ioctl+0x7e/0xb0
[   73.474395]  ? do_syscall_64+0x33/0x40
[   73.474402]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   73.474407] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) pcspkr
[   73.474425] CR2: 0000000000000004
}}}
(it ended here)

///
Partial output of crash's ""bt -sFlxg"":
{{{
PID: 14833  TASK: ffff9959886acf80  CPU: 2   COMMAND: ""EMT-0""
 #0 [ffffb3294a0eba68] machine_kexec+0x191 at ffffffff9904d3b1
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
    ffffb3294a0eba70: 0000000000000018 0000ffff99574000 
    ffffb3294a0eba80: ffff995740000000 0000000f0a001000 
    ffffb3294a0eba90: ffff99664a001000 0000000f0a000000 
    ffffb3294a0ebaa0: 0000000000000000 cc4567c5b1908400 
    ffffb3294a0ebab0: ffffb3294a0ebc88 ffffb3294a0ebc88 
    ffffb3294a0ebac0: 0000000000000009 __crash_kexec+225 
 #1 [ffffb3294a0ebac8] __crash_kexec+0xe1 at ffffffff99188a21
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
    ffffb3294a0ebad0: ffffb3294a0ebde0 0000000000000001 
    ffffb3294a0ebae0: ffffb3294bea1000 rtR0TermNative+208 
    ffffb3294a0ebaf0: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebb00: 000000000007b438 __this_module+992 
    ffffb3294a0ebb10: 0000000000000000 0000000000000001 
    ffffb3294a0ebb20: __apply_to_page_range+737 0000000000000000 
    ffffb3294a0ebb30: 0000000000000000 0000000000000000 
    ffffb3294a0ebb40: 0000000000000000 ffffffffffffffff 
    ffffb3294a0ebb50: do_raw_spin_lock+4 0000000000000010 
    ffffb3294a0ebb60: 0000000000010296 ffffb3294a0ebd30 
    ffffb3294a0ebb70: 0000000000000018 cc4567c5b1908400 
    ffffb3294a0ebb80: 0000000000000046 crash_kexec+52   
 #2 [ffffb3294a0ebb88] crash_kexec+0x34 at ffffffff99189954
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
    ffffb3294a0ebb90: ffffb3294a0ebc88 oops_end+132     
 #3 [ffffb3294a0ebb98] oops_end+0x84 at ffffffff99022034
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
    ffffb3294a0ebba0: [task_struct]    ffffb3294a0ebc88 
    ffffb3294a0ebbb0: 0000000000000004 no_context+572   
    ffffb3294a0ebbc0: 0000000000000000 contig_page_data+3600 
    ffffb3294a0ebbd0: 0000000000000004 0000000000000000 
    ffffb3294a0ebbe0: 0000000000000000 0000000000000000 
    ffffb3294a0ebbf0: cc4567c5b1908400 0000000000000000 
    ffffb3294a0ebc00: ffffb3294a0ebc88 0000000000000000 
    ffffb3294a0ebc10: 0000000000000004 0000000000000000 
    ffffb3294a0ebc20: [mm_struct]      exc_page_fault+732 
 #4 [ffffb3294a0ebc28] exc_page_fault+0x2dc at ffffffff9a22a69c
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1320
    ffffb3294a0ebc30: 0000000000000000 0000000000000000 
    ffffb3294a0ebc40: 0000000000000000 00042cc000000000 
    ffffb3294a0ebc50: 0000000000000000 0000000000000000 
    ffffb3294a0ebc60: 0000000000000000 0000000000000000 
    ffffb3294a0ebc70: 0000000000000000 0000000000000000 
    ffffb3294a0ebc80: asm_exc_page_fault+27 
 #5 [ffffb3294a0ebc80] asm_exc_page_fault+0x1b at ffffffff9a400acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
    ffffb3294a0ebc88: ffffb3294a0ebde0 0000000000000001 
    ffffb3294a0ebc98: ffffb3294bea1000 rtR0TermNative+208 
 #6 [ffffb3294a0ebca0] rtR0TermNative+0xd0 at ffffffffc0240080 [vboxdrv]
    ffffb3294a0ebca8: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebcb8: 000000000007b438 __this_module+992 
    ffffb3294a0ebcc8: 0000000000000000 0000000000000001 
    ffffb3294a0ebcd8: __apply_to_page_range+737 
 #7 [ffffb3294a0ebcd8] __apply_to_page_range+0x2e1 at ffffffff992838a1
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
    ffffb3294a0ebce0: 0000000000000000 0000000000000000 
    ffffb3294a0ebcf0: 0000000000000000 0000000000000000 
    ffffb3294a0ebd00: ffffffffffffffff do_raw_spin_lock+4 
    ffffb3294a0ebd10: 0000000000000010 0000000000010296 
    ffffb3294a0ebd20: ffffb3294a0ebd30 0000000000000018 
    ffffb3294a0ebd30: ffffb3294beed000 __apply_to_page_range+737 
    ffffb3294a0ebd40: ffff9958401012f8 ffffb3294beed000 
    ffffb3294a0ebd50: [mm_struct]      ffff995858f00508 
    ffffb3294a0ebd60: 0000000000000000 ffffb3294beecfff 
    ffffb3294a0ebd70: ffffb3294beed000 ffff995840000528 
    ffffb3294a0ebd80: ffffb3294beed000 ffff995a17102b30 
    ffffb3294a0ebd90: ffffb3294beecfff rtR0TermNative+208 
 #8 [ffffb3294a0ebd98] rtR0TermNative+0xd0 at ffffffffc0240080 [vboxdrv]
    ffffb3294a0ebda0: ffffb3294beecfff [kmalloc-8k]     
    ffffb3294a0ebdb0: ffffb3294a0ebdf8 0000000000000000 
    ffffb3294a0ebdc0: 0000000000000000 ffffb3294c609010 
    ffffb3294a0ebdd0: [kmalloc-192]    rtR0MemObjNativeProtect+116 
 #9 [ffffb3294a0ebdd8] rtR0MemObjNativeProtect+0x74 at ffffffffc0241774 [vboxdrv]
    ffffb3294a0ebde0: [kmalloc-8k]     8000000000000161 
    ffffb3294a0ebdf0: cc4567c5b1908400 ffffb3294a0ebe10 
    ffffb3294a0ebe00: VBoxHost_RTR0MemObjProtect+129 
#10 [ffffb3294a0ebe00] VBoxHost_RTR0MemObjProtect+0x81 at ffffffffc023ecd1 [vboxdrv]
    ffffb3294a0ebe08: __this_module+992 ffffb3294a0ebea8 
    ffffb3294a0ebe18: supdrvIOCtl+12901 
#11 [ffffb3294a0ebe18] supdrvIOCtl+0x3265 at ffffffffc02339a5 [vboxdrv]
    ffffb3294a0ebe20: 0000000000000004 [kmalloc-2k]     
    ffffb3294a0ebe30: __this_module+992 00000004001fc060 
    ffffb3294a0ebe40: 00000000000004ff 0000000000205900 
    ffffb3294a0ebe50: __this_module+992 0000000000000000 
    ffffb3294a0ebe60: 0000000000000000 0000000000000000 
    ffffb3294a0ebe70: ffffb3294a0ebea8 cc4567c5b1908400 
    ffffb3294a0ebe80: 0000000000205978 0000000000005684 
    ffffb3294a0ebe90: 0000754d24911010 [kmalloc-2k]     
    ffffb3294a0ebea0: ffffb3294c609010 ffffb3294a0ebf08 
    ffffb3294a0ebeb0: SUPR0Printf+559  
#12 [ffffb3294a0ebeb0] SUPR0Printf+0x22f at ffffffffc022b67f [vboxdrv]
    RIP: 0000754d82eb9e37  RSP: 0000754d3c1f2b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000754d24911010  RCX: 0000754d82eb9e37
    RDX: 0000754d24911010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000754d3c1f2b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000754d6ef3afcf
    R13: 0000000000000000  R14: 0000754d3c1f2e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///
{{{
crash> mod
     MODULE       NAME              BASE          SIZE  OBJECT FILE
ffffffffc0225100  pcspkr      ffffffffc0223000   16384  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc026f380  vboxdrv     ffffffffc022b000  438272  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc02b0040  vboxnetflt  ffffffffc02ab000   28672  (not loaded)  [CONFIG_KALLSYMS]
ffffffffc02b9180  vboxnetadp  ffffffffc02b7000   28672  (not loaded)  [CONFIG_KALLSYMS]
}}}
///
{{{
crash> add-symbol-file /usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug 0xffffffffc022b000
add symbol table from file ""/usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug"" at
        .text_addr = 0xffffffffc022b000
Reading symbols from /usr/lib/debug/lib/modules/5.10.11-gentoo-x86_64/misc/vboxdrv.ko.debug...done.
}}}
///
{{{
crash> info line *rtR0TermNative+0xd0
Line 540 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240080 <rtR0MemObjLinuxApplyPageRange> and ends at 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4>.
crash> info line *rtR0MemObjLinuxApplyPageRange+4
Line 542 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4> and ends at 0xffffffffc0240087 <rtR0MemObjLinuxApplyPageRange+7>.
}}}
{{{
  /**                                                                                                                                    
   * Callback called in apply_to_page_range().                                                                                           
   *                                                                                                                                     
   * @returns Linux status code.                                                                                                         
   * @param   pPte                Pointer to the page table entry for the given address.                                                 
   * @param   uAddr               The address to apply the new protection to.                                                            
   * @param   pvUser              The opaque user data.                                                                                  
   */                                                                                                                                    
  static DECLCALLBACK(int) rtR0MemObjLinuxApplyPageRange(pte_t *pPte, unsigned long uAddr, void *pvUser)                                 
  { //this is line 540                                                                                                                   
      PCLNXAPPLYPGRANGE pArgs = (PCLNXAPPLYPGRANGE)pvUser;                                                                               
      PRTR0MEMOBJLNX pMemLnx = pArgs->pMemLnx;  //this is line 542                                                                                         
      size_t idxPg = (uAddr - (unsigned long)pMemLnx->Core.pv) >> PAGE_SHIFT;                                                            
                                                                                                                                         
      set_pte(pPte, mk_pte(pMemLnx->apPages[idxPg], pArgs->fPg));                                                                        
      return 0;                                                                                                                          
  }                                                                                                                                      
  #endif
}}}
///
{{{
crash> info line *rtR0TermNative+208
Line 540 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc0240080 <rtR0MemObjLinuxApplyPageRange> and ends at 0xffffffffc0240084 <rtR0MemObjLinuxApplyPageRange+4>.
(ok this doesn't seem to be useful?)
}}}
///
{{{
crash> info line *rtR0TermNative
Line 117 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/initterm-r0drv-linux.c"" starts at address 0xffffffffc023ffb0 <rtR0TermNative> and ends at 0xffffffffc023ffb4 <rtR0TermNative+4>.

  DECLHIDDEN(void) rtR0TermNative(void)                                                                                                  
  { //this is line 117                                                                                                                   
      IPRT_LINUX_SAVE_EFL_AC();                                                                                                          
                                                                                                                                         
      rtR0LnxWorkqueueFlush();                                                                                                           
  #if RTLNX_VER_MIN(2,5,41)                                                                                                              
      destroy_workqueue(g_prtR0LnxWorkQueue);                                                                                            
      g_prtR0LnxWorkQueue = NULL;                                                                                                        
  #endif                                                                                                                                 
                                                                                                                                         
      rtR0MemExecCleanup();                                                                                                              
                                                                                                                                         
      IPRT_LINUX_RESTORE_EFL_AC();                                                                                                       
  }
}}}
///
{{{
crash> info line *__apply_to_page_range+0x2e1
No line number information available for address 0xffffffff992838a1
(don't know how to make this work, tho it does work in the output of 'bt -l')
crash> sym 0xffffffff992838a1
ffffffff992838a1 (t) __apply_to_page_range+737 /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
crash> info line *__apply_to_page_range+737
No line number information available for address 0xffffffff992838a1
//ok so 0x2e1 is 737 in decimal
crash> sym 0xffffffff992838a1
ffffffff992838a1 (t) __apply_to_page_range+737 /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354

 #7 [ffffb3294a0ebcd8] __apply_to_page_range+0x2e1 at ffffffff992838a1
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354

  static __always_inline void spin_lock(spinlock_t *lock)                                                                                
  {                                                                                                                                      
    raw_spin_lock(&lock->rlock); // this is line 354                                                                                     
  }
}}}
///
---------------
Another crash, now with the following .config diff (compared to /usr/src/.config.prev18_nondebug):

{{{
-CONFIG_DEBUG_LOCK_ALLOC=y
-CONFIG_LOCKDEP=y
-# CONFIG_DEBUG_LOCKDEP is not set
+# CONFIG_DEBUG_LOCK_ALLOC is not set
}}}
      KERNEL: /var/crash/vmlinux-5.10.11-gentoo-x86_64-2021-01-29-19_54_43

    DUMPFILE: /var/crash/crashdump-2021-01-29-20_22_50  [PARTIAL DUMP]

'log' partial output:
{{{
...
[   14.857357] vboxdrv: loading out-of-tree module taints kernel.
[   14.857929] vboxdrv: Found 12 processor cores
[   14.873771] vboxdrv: TSC mode is Invariant, tentative frequency 3695998457 Hz
[   14.873771] vboxdrv: Successfully loaded version 6.1.18 (interface 0x00300000)
...
[   56.083785] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot
[   61.037910] SUPR0GipMap: fGetGipCpu=0x1b
[   62.739845] BUGGY: kernel NULL pointer dereference, address: 0000000000000004
[   62.739856] #PF: supervisor read access in kernel mode
[   62.739862] #PF: error_code(0x0000) - not-present page
[   62.739866] PGD 0 P4D 0 
[   62.739876] Oops: 0000 [#1] SMP NOPTI
[   62.739883] CPU: 9 PID: 14846 Comm: EMT-0 Kdump: loaded Tainted: G     U     O      5.10.11-gentoo-x86_64 #1
[   62.739887] Hardware name: System manufacturer System Product Name/PRIME Z370-A, BIOS 2401 07/12/2019
[   62.739897] RIP: 0010:do_raw_spin_lock+0x4/0x90
[   62.739904] Code: 48 8d 88 90 06 00 00 48 c7 c7 f0 c7 aa 94 e8 f6 be e4 00 e9 33 b4 e6 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 53 48 89 fb <8b> 47 04 3d ad 4e ad de 75 46 48 8b 53 10 65 48 8b 04 25 40 6d 01
[   62.739909] RSP: 0018:ffffb532498a7d30 EFLAGS: 00010286
[   62.739915] RAX: ffff997800000588 RBX: 0000000000000000 RCX: 0000000000000000
[   62.739920] RDX: 0000000101207067 RSI: 00000000040481c0 RDI: 0000000000000000
[   62.739923] RBP: ffffb532498a7df8 R08: ffff997901207588 R09: 0000000000000001
[   62.739927] R10: ffffffffc0273560 R11: 0000000000061918 R12: ffffffffc0244000
[   62.739931] R13: ffffb532498b1000 R14: 0000000000000001 R15: ffffb532498a7de0
[   62.739937] FS:  0000751ec8366640(0000) GS:ffff99880a480000(0000) knlGS:0000000000000000
[   62.739941] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   62.739945] CR2: 0000000000000004 CR3: 000000032b99c004 CR4: 00000000001706e0
[   62.739949] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   62.739954] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   62.739957] Call Trace:
[   62.739967]  ? __apply_to_page_range+0x2e1/0x6a0
[   62.739999]  ? rtR0TermNative+0xd0/0x220 [vboxdrv]
[   62.740026]  ? rtR0MemObjNativeProtect+0x74/0xa0 [vboxdrv]
[   62.740051]  ? VBoxHost_RTR0MemObjProtect+0x81/0xc0 [vboxdrv]
[   62.740074]  ? supdrvIOCtl+0x3265/0x3800 [vboxdrv]
[   62.740094]  ? SUPR0Printf+0x22f/0x330 [vboxdrv]
[   62.740101]  ? __x64_sys_ioctl+0x7e/0xb0
[   62.740109]  ? do_syscall_64+0x33/0x40
[   62.740117]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   62.740121] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) pcspkr
[   62.740136] CR2: 0000000000000004
}}}
{{{
crash> bt -l
PID: 14846  TASK: ffff99792fa78000  CPU: 9   COMMAND: ""EMT-0""
 #0 [ffffb532498a7a68] machine_kexec at ffffffff93042956
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
 #1 [ffffb532498a7ac8] __crash_kexec at ffffffff9314bee1
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
 #2 [ffffb532498a7b88] crash_kexec at ffffffff9314cdf4
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
 #3 [ffffb532498a7b98] oops_end at ffffffff9301cd84
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
 #4 [ffffb532498a7c28] exc_page_fault at ffffffff94002016
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1346
 #5 [ffffb532498a7c80] asm_exc_page_fault at ffffffff94200acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
 #6 [ffffb532498a7ca0] rtR0TermNative at ffffffffc0244000 [vboxdrv]
 #7 [ffffb532498a7d08] do_raw_spin_lock at ffffffff9310dc54
    /usr/src/linux-5.10.11-gentoo/kernel/locking/spinlock_debug.c: 112
 #8 [ffffb532498a7d38] __apply_to_page_range at ffffffff931feb71
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect at ffffffffc02456f4 [vboxdrv]
#10 [ffffb532498a7e00] VBoxHost_RTR0MemObjProtect at ffffffffc0242c81 [vboxdrv]
#11 [ffffb532498a7e18] supdrvIOCtl at ffffffffc0237955 [vboxdrv]
#12 [ffffb532498a7eb0] SUPR0Printf at ffffffffc022f62f [vboxdrv]
    RIP: 0000751f0b85ae37  RSP: 0000751ec8364b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000751ead314010  RCX: 0000751f0b85ae37
    RDX: 0000751ead314010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000751ec8364b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000751efc3aefcf
    R13: 0000000000000000  R14: 0000751ec8364e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///

{{{
 /*                                                                                                                                     
   * We are now relying on the NMI watchdog to detect lockup instead of doing                                                            
   * the detection here with an unfair lock which can cause problem of its own.                                                          
   */                                                                                                                                    
  void do_raw_spin_lock(raw_spinlock_t *lock)                                                                                            
  {                                                                                                                                      
    debug_spin_lock_before(lock); // this is line 112                                                                                    
    arch_spin_lock(&lock->raw_lock);                                                                                                     
    mmiowb_spin_lock();                                                                                                                  
    debug_spin_lock_after(lock);                                                                                                         
  }
}}}
///
{{{
PID: 14846  TASK: ffff99792fa78000  CPU: 9   COMMAND: ""EMT-0""
 #0 [ffffb532498a7a68] machine_kexec+0x186 at ffffffff93042956
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/mem_encrypt.h: 77
    ffffb532498a7a70: 00000000498a7d30 0000ffff99780000 
    ffffb532498a7a80: ffff997800000000 000000003d001000 
    ffffb532498a7a90: ffff99783d001000 000000003d000000 
    ffffb532498a7aa0: 0000000000000000 c2c563b4d1c59e00 
    ffffb532498a7ab0: ffffb532498a7c88 ffffb532498a7c88 
    ffffb532498a7ac0: 0000000000000009 __crash_kexec+225 
 #1 [ffffb532498a7ac8] __crash_kexec+0xe1 at ffffffff9314bee1
    /usr/src/linux-5.10.11-gentoo/kernel/kexec_core.c: 963
    ffffb532498a7ad0: ffffb532498a7de0 0000000000000001 
    ffffb532498a7ae0: ffffb532498b1000 rtR0TermNative+208 
    ffffb532498a7af0: ffffb532498a7df8 0000000000000000 
    ffffb532498a7b00: 0000000000061918 __this_module+864 
    ffffb532498a7b10: 0000000000000001 ffff997901207588 
    ffffb532498a7b20: ffff997800000588 0000000000000000 
    ffffb532498a7b30: 0000000101207067 00000000040481c0 
    ffffb532498a7b40: 0000000000000000 ffffffffffffffff 
    ffffb532498a7b50: do_raw_spin_lock+4 0000000000000010 
    ffffb532498a7b60: 0000000000010286 ffffb532498a7d30 
    ffffb532498a7b70: 0000000000000018 c2c563b4d1c59e00 
    ffffb532498a7b80: 0000000000000246 crash_kexec+52   
 #2 [ffffb532498a7b88] crash_kexec+0x34 at ffffffff9314cdf4
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/atomic.h: 41
    ffffb532498a7b90: ffffb532498a7c88 oops_end+132     
 #3 [ffffb532498a7b98] oops_end+0x84 at ffffffff9301cd84
    /usr/src/linux-5.10.11-gentoo/arch/x86/kernel/dumpstack.c: 359
    ffffb532498a7ba0: [task_struct]    ffffb532498a7c88 
    ffffb532498a7bb0: 0000000000000004 no_context+572   
    ffffb532498a7bc0: 0000000000000000 0000000000000000 
    ffffb532498a7bd0: 0000000000000000 0000000000000000 
    ffffb532498a7be0: 0000000000000000 0000000000000000 
    ffffb532498a7bf0: c2c563b4d1c59e00 0000000000000214 
    ffffb532498a7c00: 0000000000000000 ffffb532498a7c88 
    ffffb532498a7c10: 0000000000000004 0000000000000000 
    ffffb532498a7c20: [mm_struct]      exc_page_fault+790 
 #4 [ffffb532498a7c28] exc_page_fault+0x316 at ffffffff94002016
    /usr/src/linux-5.10.11-gentoo/arch/x86/mm/fault.c: 1346
    ffffb532498a7c30: [mm_struct]      0000000000000000 
    ffffb532498a7c40: 0000000000000000 00000000000001d0 
    ffffb532498a7c50: 0000000000000000 0000000000000000 
    ffffb532498a7c60: 0000000000000000 0000000000000000 
    ffffb532498a7c70: 0000000000000000 0000000000000000 
    ffffb532498a7c80: asm_exc_page_fault+27 
 #5 [ffffb532498a7c80] asm_exc_page_fault+0x1b at ffffffff94200acb
    /usr/src/linux-5.10.11-gentoo/arch/x86/include/asm/idtentry.h: 583
    ffffb532498a7c88: ffffb532498a7de0 0000000000000001 
    ffffb532498a7c98: ffffb532498b1000 rtR0TermNative+208 
 #6 [ffffb532498a7ca0] rtR0TermNative+0xd0 at ffffffffc0244000 [vboxdrv]
    ffffb532498a7ca8: ffffb532498a7df8 0000000000000000 
    ffffb532498a7cb8: 0000000000061918 __this_module+864 
    ffffb532498a7cc8: 0000000000000001 ffff997901207588 
    ffffb532498a7cd8: ffff997800000588 0000000000000000 
    ffffb532498a7ce8: 0000000101207067 00000000040481c0 
    ffffb532498a7cf8: 0000000000000000 ffffffffffffffff 
    ffffb532498a7d08: do_raw_spin_lock+4 
 #7 [ffffb532498a7d08] do_raw_spin_lock+0x4 at ffffffff9310dc54
    /usr/src/linux-5.10.11-gentoo/kernel/locking/spinlock_debug.c: 112
    ffffb532498a7d10: 0000000000000010 0000000000010286 
    ffffb532498a7d20: ffffb532498a7d30 0000000000000018 
    ffffb532498a7d30: ffffb532498fd000 __apply_to_page_range+737 
 #8 [ffffb532498a7d38] __apply_to_page_range+0x2e1 at ffffffff931feb71
    /usr/src/linux-5.10.11-gentoo/include/linux/spinlock.h: 354
    ffffb532498a7d40: ffff997900067260 ffffb532498fd000 
    ffffb532498a7d50: [mm_struct]      ffff997901207588 
    ffffb532498a7d60: 0000000000000000 ffffb532498fcfff 
    ffffb532498a7d70: ffffb532498fd000 ffff997900000648 
    ffffb532498a7d80: ffffb532498fd000 ffff997b2b99cb50 
    ffffb532498a7d90: ffffb532498fcfff rtR0TermNative+208 
    ffffb532498a7da0: ffffb532498fcfff [kmalloc-8k]     
    ffffb532498a7db0: ffffb532498a7df8 0000000000000000 
    ffffb532498a7dc0: 0000000000000000 ffffb5324a109010 
    ffffb532498a7dd0: [kmalloc-192]    rtR0MemObjNativeProtect+116 
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect+0x74 at ffffffffc02456f4 [vboxdrv]
    ffffb532498a7de0: [kmalloc-8k]     8000000000000161 
    ffffb532498a7df0: c2c563b4d1c59e00 ffffb532498a7e10 
    ffffb532498a7e00: VBoxHost_RTR0MemObjProtect+129 
#10 [ffffb532498a7e00] VBoxHost_RTR0MemObjProtect+0x81 at ffffffffc0242c81 [vboxdrv]
    ffffb532498a7e08: __this_module+864 ffffb532498a7ea8 
    ffffb532498a7e18: supdrvIOCtl+12901 
#11 [ffffb532498a7e18] supdrvIOCtl+0x3265 at ffffffffc0237955 [vboxdrv]
    ffffb532498a7e20: 0000000000000004 [kmalloc-2k]     
    ffffb532498a7e30: __this_module+864 00000004001fc060 
    ffffb532498a7e40: 00000000000004ff 0000000000205900 
    ffffb532498a7e50: __this_module+864 0000000000000000 
    ffffb532498a7e60: 0000000000000000 0000000000000000 
    ffffb532498a7e70: 0000000000205978 c2c563b4d1c59e00 
    ffffb532498a7e80: 0000000000205978 0000000000005684 
    ffffb532498a7e90: 0000751ead314010 [kmalloc-2k]     
    ffffb532498a7ea0: ffffb5324a109010 ffffb532498a7f08 
    ffffb532498a7eb0: SUPR0Printf+559  
#12 [ffffb532498a7eb0] SUPR0Printf+0x22f at ffffffffc022f62f [vboxdrv]
    RIP: 0000751f0b85ae37  RSP: 0000751ec8364b58  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 0000751ead314010  RCX: 0000751f0b85ae37
    RDX: 0000751ead314010  RSI: 0000000000005684  RDI: 000000000000000b
    RBP: 0000751ec8364b70   R8: 0000000000000000   R9: 00000000fffffffc
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000751efc3aefcf
    R13: 0000000000000000  R14: 0000751ec8364e20  R15: 0000000000000004
    ORIG_RAX: 0000000000000010  CS: 0033  SS: 002b
}}}
///
{{{
 #9 [ffffb532498a7dd8] rtR0MemObjNativeProtect+0x74 at ffffffffc02456f4 [vboxdrv]
crash> info line *0xffffffffc02456f4
Line 1919 of ""/usr/src/debug/app-emulation/virtualbox-modules-6.1.18/vboxdrv/r0drv/linux/memobj-r0drv-linux.c"" starts at address 0xffffffffc02456f4 <rtR0MemObjNativeProtect+116> and ends at 0xffffffffc0245720 <rtR0MemObjNativeGetPagePhysAddr>.
  # elif defined(IPRT_USE_APPLY_TO_PAGE_RANGE_FOR_EXEC)                                                                                                    
      PRTR0MEMOBJLNX pMemLnx = (PRTR0MEMOBJLNX)pMem;                                                                                                       
      if (   pMemLnx->fExecutable                                                                                                                          
          && pMemLnx->fMappedToRing0)                                                                                                                      
      {                                                                                                                                                    
          LNXAPPLYPGRANGE Args;                                                                                                                            
          Args.pMemLnx = pMemLnx;                                                                                                                          
          Args.fPg = rtR0MemObjLinuxConvertProt(fProt, true /*fKernel*/);                                                                                  
          int rcLnx = apply_to_page_range(current->active_mm, (unsigned long)pMemLnx->Core.pv + offSub, cbSub,                                             
                                          rtR0MemObjLinuxApplyPageRange, (void *)&Args);                                                                   
          if (rcLnx)  //this is line 1919   !!!!!!!!!!!!!!!!!!!!!!!!!!!  which seems off by one (a normal thing) 
              return VERR_NOT_SUPPORTED;                                                                                                                   
                                                                                                                                                           
          return VINF_SUCCESS;                                                                                                                             
      }                                                                                                                                                    
  # endif                       
}}}
---------
no crash now with the following .config diff (compared to previous):
{{{
-CONFIG_UNINLINE_SPIN_UNLOCK=y
+CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
+CONFIG_INLINE_READ_UNLOCK=y
+CONFIG_INLINE_READ_UNLOCK_IRQ=y
+CONFIG_INLINE_WRITE_UNLOCK=y
+CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
-CONFIG_DEBUG_SPINLOCK=y
+# CONFIG_DEBUG_SPINLOCK is not set
}}}
so to avoid crash, you need(at least):

CONFIG_DEBUG_SPINLOCK=n (which forces CONFIG_DEBUG_LOCK_ALLOC=n)

but doesn't matter if =y on the following:
{{{
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
}}}
-------
nvmTODO: try with:
{{{
+# CONFIG_DEBUG_SPINLOCK is not set
}}}
but with
{{{
CONFIG_DEBUG_LOCK_ALLOC=y
}}}
Can't, because if CONFIG_DEBUG_LOCK_ALLOC=y then it's forced that CONFIG_DEBUG_SPINLOCK=y !
--------
",ozugzug
20099,bridged mode not working in VB on macOS Big Sur for VB windows clients,Mac OS X,Windows,VirtualBox 6.1.16,2021-02-17T03:59:37Z,2021-02-17T03:59:37Z,"As posted in the VB Forum:
Finally got to the bottom of the issue after finding a few hints, pointers and bits of information at various places.

After the upgrade from Catalina to Big Sur, networking caused several issues in VB windows instances.
I've always used bridged mode with no issues for both wired and wireless connections before the upgrade.

My symptoms , In bridge mode DHCP in windows failed to obtain a valid IP address, starting with duplicate found and quickly followed with a 192.168.1 address that would not give a proper connection , I use 192.168.0 subdomain. Could not get neither the wired nor the wireless connection to work.

When setting NAT mode the VB windows instance, VB would fatally crash the VB windows instance, so not windows but VB crashed.

I concluded that the last issue must have been caused by VB drivers being messed up after the Catalina to Big Sur transition.

I downloaded the 6.1.16 VB version and used the uninstall script ( available in the finder window when opening the vb.dmg file) to remove VB from the mac.
Don't worry it only removes the drivers and VB itself, not any of your configs or VB disks and client images.
Then re-installed VB. This got NAT back working.

Bridged mode still had same issues for windows clients, it has something to do with change in behaviour of how big sure handles MAC addresses by the looks of it.
The fix is that you have to give the network adapter in VB that is mapped on your mac network adapter the same MAC address as the MAC address for the adapter on your MAC.
This is not a good permanent fix as you this prevents you to have more than one VB client run on your MAC as all you would get duplicated MAC addresses on your system. Be aware of that. Also if you use DHCP with preset IP addresses, each VB windows client will get the same IP address.",pbvbox
20203,VirtualBox crashing,other,other,VirtualBox 6.1.18,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
20204,"My VBoxManage-code, runned on the host, can not bring a ""windows guest registry value"" into my guestproperty",Linux,Windows,VirtualBox 6.1.14,2021-02-18T22:12:24Z,2021-02-18T22:12:24Z,"I try to get a registry value of the guest with a command that runs in the host. But this does not work.

To get a better idea of the problem, I have checked parts of my code separately.

First I have tested the command in the windows guest.
Result: It works.

Here is the command:
I go into my Windows 7 guest. I open the cmd-window. I type in the cmd-window the following inclusive <""> .

{{{
""%SystemRoot%\system32\cmd.exe"" -- 'cmd' /c start ""run this"" For /F ""EOL=H Tokens=2,*"" %G In ('""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""
}}}

To be sure, that it has worked, I go back to my Linux host and type in a terminal the following:

{{{
VBoxManage guestproperty get ""MyWin7Guest"" /myproperties/myproperty
}}}
 Output:

{{{
Value: Word.Document.12
}}}

After, I now change the guestproperty (so that I can use it later again) with the command:

{{{
VBoxManage guestproperty set ""MyWin7Guest"" /myproperties/myproperty ""deleted""
}}}

Now I create a variable of the code above, (but not of the whole one, please compare them) because I need it later.
I do this in a linux terminal in my Linux host:

{{{
q='For /F ""EOL=H Tokens=2,*"" %G In ('
w=""'""
e='""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""'
r=""'""
t=') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""'
p=$q$w$e$r$t
}}}
So I have the code above in $p. I need this later:

{{{
$ echo $p
For /F ""EOL=H Tokens=2,*"" %G In ('""""%SystemRoot%\System32\reg.exe"" Query ""HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.docx\UserChoice"" /V ""ProgId"" 2> NUL""') Do @""D:\NT3x\VBoxControl.exe"" --nologo guestproperty set /myproperties/myproperty ""%H""
}}}



As the code has worked in my guest-system, I can now go one step further. I'll put the following code in front of it:

{{{
VBoxManage guestcontrol ""MyWin7Guest"" start --username XX  --password YY --exe
}}}

So that I have now the following whole code:

{{{
VBoxManage guestcontrol ""MyWin7Guest"" start --username XX  --password YY --exe ""%SystemRoot%\system32\cmd.exe"" -- 'cmd' /c start ""run this"" $p
}}}


I type this code into a terminal in my Linux host. Done.
What is the output? No output. No error. It looks like this if the code had been executed correctly.

To be sure, that it has worked, I type in my Linux terminal the following:

{{{
VBoxManage guestproperty get ""MyWin7Guest"" /myproperties/myproperty
}}}

Here is the result:

{{{
$ VBoxManage guestproperty get ""Win7NeuFurOfficeVersuch"" /myproperties/myproperty
Value: deleted
}}}

So: Why does this not work? Is this a VirtualBox error?




",wemido
20205,OL8 VM aborted - appears screen resize or USB related,Windows,Linux,VirtualBox 6.1.16,2021-02-19T12:24:44Z,2021-02-19T12:24:44Z,"Two suspects for my VM aborting:

1. USB. I use a USB dongle and regularly attach/detach via the VBox device menu.

2. Screen resize.  I frequently resize my VM window as I shuffle windows around to different displays, snap to one side of the screen, etc.",mocooern
20181,WinVerifyTrust for MMDevAPI.dll,Windows,Linux,VirtualBox 6.1.18,2021-02-19T13:00:07Z,2021-02-19T13:00:07Z,"Microsoft updated this dll on 09/02/2021 and since then all virtualbox guests are falling over unexpectedly during startup with exit code 1 (0x1). the cause in the VBoxHardening.log file is MMDevAPI.dll lacks WinVerifyTrust.
Attached is the VBoxHardening.log for a newly created Fedora Linux host.
Version of Windows is Windows 10 Pro Ver 20H2 OS build 19042.804",Tim_B
20208,vboxmanage clonevm crashes VBoxSVC,Linux,all,VirtualBox 6.1.18,2021-02-19T17:36:18Z,2021-02-19T17:36:18Z,"I'm trying to run a script [1] to clone VirtualBox VMs. I run these three examples given at the link in parallel. They are all started almost simultaneously.

During the run when the first has finished (ubuntu focal mate), the other ones gets warnings of that they need to shutdown. 

If I still run them all to the end the following happens:

1) ""Ubuntu Mate Focal"" finishes. 'vboxmanage clonevm ""${parentvm}"" --name ""${childvm}"" --register' writes the new instance to disk, but does not appear in the Manager list. No errors reported.

2) ""Kali Linux"" and ""Shellter"" still running. They got a log entry saying:

01:57:46.655025 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)

01:58:16.598405 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)

A popup at each of the two instances tells the instance needs to finish. I ignore these messages and let them run to the end.

3) After the remaining scripts are finished, data from them also appears on disk but not in the Manager. All three are written correctly.

4) After killing (both with SIGTERM) the manager and the server, starting the manager again all appears in the list and can be run.

Bug entry message from VBoxSVC is:
---
Log created: 2021-02-19T02:06:16.959798000Z
Process ID:  2620270 (0x27fb6e)
Parent PID:  1 (0x1)
Executable:  /usr/lib/virtualbox/VBoxSVC
Arg[0]: /usr/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown
AddRef: illegal refcnt=3221225469 state=2
---

All logs attached.

[1] https://github.com/nipatriknilsson/vboxcloneimmutable
",Mrpn
20209,Windows 10 host - ubuntu 20.10 guest crush,Windows,Linux,VirtualBox 6.1.18,2021-02-19T21:15:26Z,2021-02-19T21:15:26Z,"When playing minecraft (KLauncher) on a guest ubuntu 20.10, the mouse behavior was tilted down or up, then the mouse stopped working in ubuntu altogether.",Дмитро
20200,Guru Meditation 1155 with v6.1.18 on Windows 10 host running Windows 98 guest,Windows,Windows,VirtualBox 6.1.18,2021-02-20T13:47:30Z,2021-02-20T13:47:30Z,"Hi,

I am running the 64bit Version of VirtualBox 6.1.18 r142142 on Windows 10 Pro (20H2) and installed a fresh Windows 98 Second Edition as Guest VM. I use the default Windows 98 configuration and only modified it to set 256MB RAM and 32MB Video RAM.

The first time everything was running fine (no additional programs installed) but since yesterday I get a Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT). This happens sporadically but only during login. Once the system startup is finished everything is fine. Sporadically means that it sometimes works 2-3 times but then the other 5 times I get the Guru.

Regards,
stauberix",stauberix
20217,Xmodmap needs several executions on Windows 10 host,Windows,Linux,VirtualBox 6.1.16,2021-02-21T23:19:23Z,2021-02-21T23:19:23Z,"This is my .Xmodmap in a GNU/Linux guest:

{{{
! Use Menu as a slash
keycode 135 = slash

! Swap Esc and Alt under VirtualBox guest
remove mod1 = Alt_L
keysym Escape = Alt_L
keysym Alt_L = Escape
add mod1 = Alt_L
}}}

This is an excerpt from my .xinitrc:
{{{
usermodmap=""${HOME}/.Xmodmap""
[[ -r ""${usermodmap}"" ]] && xmodmap ""${usermodmap}""
}}}

After startx my desired key bindings are not active. On average I have to execute the following command twice more in a terminal emulator for it to take effect: xmodmap ~/.Xmodmap 

I created a menu item in the TWM window manager that executes: ""xmodmap ~/.Xmodmap ; xmodmap ~/.Xmodmap ; xmodmap ~/.Xmodmap"". 

But even with this usable workaround it is certainly annoying, and I frequently forget to run it from the menu on boot.


Extra information,

Host: Windows 10 19042 

virtualbox extension pack: 6.1.16r140961


Guest: Arch Linux 

virtualbox-guest-utils: 6.1.16 

xorg-server: 1.20.10 

xf86-input-libinput: 0.30.0 

libinput: 1.16.4

X.org configuration:
{{{
Section ""InputClass""
    Identifier      ""keyboard""
    MatchIsKeyboard ""on""
    Option     ""XkbLayout""   ""hr,us""
    # XkbOptions list: /usr/share/X11/xkb/rules/base.lst
    Option     ""XkbOptions""  ""grp:shifts_toggle,terminate:ctrl_alt_bksp""
EndSection
}}}
",anrxc
20219,VirtualBox starts up OK. Failed to open a session for the virtual machine. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine.,Windows,Linux,VirtualBox 6.1.18,2021-02-22T17:07:19Z,2021-02-22T17:07:19Z,"I am experiencing the same problem as #20191. VirtualBox starts up fine. Existing VM fails to start with same error as this ticket describes. Failed to open a session for the virtual machine C7.
I have attached the log file, in addition to pasting it below.

The virtual machine 'C7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\C7\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

From VboxHardening.log:

16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'combase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'combase.dll' -> '\Device\HarddiskVolume3\Windows\System32\combase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\combase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDEVAPI.DLL (Input=MMDEVAPI.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDEVAPI.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'rpcrt4.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'oleaut32.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'mmdevapi.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\AudioSes.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\AudioSes.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume3\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\oleaut32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp_win.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp_win.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcp_win.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcp_win.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\AUDIOSES.DLL (Input=AUDIOSES.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'rpcrt4.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\powrprof.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\powrprof.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffba0030000 LB 0x0004b000 C:\windows\SYSTEM32\powrprof.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\powrprof.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb99220000 LB 0x00185000 C:\windows\System32\AUDIOSES.DLL [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\umpdc.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\umpdc.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb9ffb0000 LB 0x00012000 C:\windows\SYSTEM32\UMPDC.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\umpdc.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99220000 'C:\windows\System32\AUDIOSES.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'mmdevapi.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'msacm32.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\msacm32.drv) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.drv 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msacm32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msacm32.dll' -> '\Device\HarddiskVolume3\Windows\System32\msacm32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\msacm32.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d650000 LB 0x0001e000 C:\windows\SYSTEM32\MSACM32.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d9c0000 LB 0x0000d000 C:\windows\System32\msacm32.drv [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\midimap.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\midimap.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmmbase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmmbase.dll' -> '\Device\HarddiskVolume3\Windows\System32\winmmbase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d640000 LB 0x0000b000 C:\windows\System32\midimap.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.1aa0: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDevApi.dll' 11a8.438: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 109337 ms, the end);

I have tried some suggestions found using Google and sometimes they help, but next reboot or start of VirtualBox results in same bad behavior. I also have uninstalled VirtualBox 6.1.18 and re-installed. It sometimes seems to let the VM start up and other times the same error appears. Both the install of VirtualBox 6.1.18 and the startup of VirtualBox 6.1.18 were done as administrator. Anti-Virus Used is: EseT Nod32 14.0.22.0 Windows Info: OS Name Microsoft Windows 10 Pro Version 10.0.19041 Build 19041 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-H70PDLJ System Manufacturer HP System Model HP EliteBook 855 G7 Notebook PC System Type x64-based PC System SKU 3E780AV Processor AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1700 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date HP S77 Ver. 01.02.03, 11/27/2020 SMBIOS Version 3.2 Embedded Controller Version 7.44 BIOS Mode UEFI BaseBoard Manufacturer HP BaseBoard Product 8760 BaseBoard Version KBC Version 07.2C.00 Platform Role Mobile Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\windows System Directory C:\windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = ""10.0.19041.488"" User Name DESKTOP-H70PDLJ\willh Time Zone Central Standard Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.3 GB Available Physical Memory 27.9 GB Total Virtual Memory 36.1 GB Available Virtual Memory 32.6 GB Page File Space 4.75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes",WillH
20000,Linux guests lock up with Host I/O cache disabled (NVMe and SATA),Linux,Linux,VirtualBox 6.1.14,2021-02-23T21:37:44Z,2021-02-23T21:37:44Z,"I have been finding that Linux guests seem to lock up when Host I/O cache is disabled when disks are under load (for example when installing system updates). dmesg also shows disk timeouts, and it seems no further disk operations succeed after this point without killing the VM process and restarting.

A log is attached. I'm not sure how to reproduce this reliably, but it seems to happen when I'm installing updates. I have seen this with both Ubuntu and Fedora guests. I will also upload a screenshot shortly with the exact messages, but I seem to have misplaced it for the moment.

I should also note that this is with the VDI nonrotational option turned on and discard=on in the guest Linux OS.

Anything else I can do to help diagnose?",Hamish McIntyre-Bhatty
20220,VirtualBox Aborts/Crashes without message with Shared Clipboard enabled,Mac OS X,Windows,VirtualBox 6.1.18,2021-02-24T16:04:44Z,2021-02-24T16:04:44Z,"Since I started using shared clipboard my VirtualBox has been crashing every day or two.  There is no obvious pattern nor activity (from user, me) at time of crash.  My Virtual Box is running a VB6 data upload program 24-7 to upload PV data to internet. There is no message produced by Virtual Box.  There is an Apple crash report.

I referred to this problem on the forum
https://forums.virtualbox.org/viewtopic.php?f=8&t=101856&sid=fcc584fc50e9ceeae4624f76b923a35a

I have attached the Apple Crash.log and VBox.log files.  I have not attached a core dump.  I don't understand the instructions and am not sure if the core dump has to be initialised before the crash or can be collected after the event.
",MisterWooley
20221,windows 10 unmountable boot volume,Windows,Windows,VirtualBox 6.1.18,2021-02-24T16:48:37Z,2021-02-24T16:48:37Z,"I have an HP Envy 17 that has two disk drives, the original 1TB hard disk, and a second 480GB SSD. I have been running Windows 7 on the SSD with the hard drive as backup.

I just updated the hard disk to Windows 10 which I boot by popping out the SSD (which is in the DVD slot) so that Windows then boots from the second drive. 

I want to be able to run Windows 7 normally and use VirtualBox to boot up Windows 10 to run one application which won't run on Windows 7.

I have created a virtual raw disk for Drive 1 and when I attempt to boot it, I get the error message about the boot volume not being mountable. This happens after I get the windows logo and circle for a while.

Anyone have any suggestions how I can get this to work ? 
",Wewebb14
20223,Linux/64bit host XMM register usage in kernel randomly crashes Linux guest,Linux,Linux,VirtualBox 6.1.16,2021-02-24T18:57:46Z,2021-02-24T18:57:46Z,"'''Synopsis:''' src/VBox/VMM/Makefile.kmk 'knows' flag VBOX_WITH_KERNEL_USING_XMM, which is added for Windows/64bit builds only.
Problem is that Linux kernel DOES MAKE USE of XMM registers, too. Examples include aes-ni kernel module (AES-NI instructions implicitly use XMM0..15) or RAID, respectively).
VMM at ring 0 only implements XMM wrappers for Windows/64bit and does not have conditionals to abort build if VBOX_WITH_KERNEL_USING_XMM is set in src/VBox/VMM/Makefile.kmk for linux.amd64. This yields a kernel panic because Microsoft ABI is completely different from System V ABI (aka gcc ABI).
The 6.1.18 trunk seems to rely on a complete rewrite of src/VBox/VMM/VMMR0/HMR0A.asm but 6.1.13 / 6.1.16 (6.0 also) still have this problem.

'''Solution is:'''

a) Add VBOX_WITH_KERNEL_USING_XMM to src/VBox/VMM/Makefile.kmk for linux.amd64


b) Provide conditional implementation in src/VBox/VMM/VMMR0/HMR0A.asm for gcc/amd64 expecting function parameters in System V ABI registers rdi, rsi, rdx, rcx, r8, and r9. The two wrappers hmR0VMXStartVMWrapXMM and hmR0SVMRunWrapXMM need this.


c) calling CPUMIsGuestFPUStateActive from yasm assembler to C++ requires suffix ""wrt ..plt""

I have patches for this but optimized only for ""my"" Intel CPU. VBox users either have to switch to 6.1.18 or apply the above mentioned modifications.

'''Recommendation:'''

VBOX maintainers should think about making VBOX_WITH_KERNEL_USING_XMM the default for Linux, too (because of possible AES-NI or RAID usage, respectively).",vboxcomapijunkie
20224,"GUI remains white, popup window is empty when call Settings",Linux,Windows,VirtualBox 6.1.18,2021-02-24T23:03:29Z,2021-02-24T23:03:29Z,"Hi, 
When I do call Settings for a VM, the popup window remains white, and no  menue items, I cannot change the settings. 
Linux mint 20.1 with cinnamon, kernel 5.8.0-43 generic. 
when I resize the popup window, remains white. 
Seems to me some problem with java: 
openjdk version ""11.0.10"" 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+9-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.10+9-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)


Please review my screenshots. 
thx. 

",szilike
20225,Voice synthesis software rhvoice doesn't work in VirtualBox,Linux,other,VirtualBox 6.1.18,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
20227,Screen locks up during POST,other,other,VirtualBox 6.1.18,2021-02-25T17:05:36Z,2021-02-25T17:05:36Z,"ID 32
ID 455 
Codes",Miles
20192,Virtual Machine does not start on M1 Mac,Mac OS X,all,VirtualBox 6.1.18,2021-02-27T12:08:53Z,2021-02-27T12:08:53Z,"Device: MacBook Pro 13-inch, 2020, M1

Software: macOs 11.1





Installation of VirtualBox is working. 
Trying to create and start an Ubuntu-Machine with VirtualMachine by using the following command in existing project: 
{{{
vagrant up
}}}

After short time the following message appears: 

{{{
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""hostonlyif"", ""create""]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: ""RTEXITCODE handleCreate(HandlerArg *)"" at line 95 of file VBoxManageHostonly.cpp
}}}

There is no file like /dev/vboxnetctl. When  installing VirtualBox there is no option in the security settings to accept. Related posts recommend reinstalling of VirtualBox. Tried multiple times without success. There is still no possibility to adjust the privacy settings of Big Sur for VirtualBox.

Other way to resolve the problem: 
Trying to restart with:
{{{
sudo ""/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh"" restart 
}}}

This doesn’t work and leads to following error:
{{{
Error Domain=KMErrorDomain Code=71 ""Incompatible architecture: Binary is for x86_64, but needed arch arm64e"" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
}}}


It seems that VirtualBox is not compatible to the newest Mac ARM architecture. Is there a plan to fix that in the upcoming releases?


",mheimqpm
20228,Don't start VM with vagrant instruction,other,Linux,VirtualBox 6.1.18,2021-02-28T08:53:27Z,2021-02-28T08:53:27Z,"Hi,

I would like to use vagrant for initializing a docker environment (just for context).

And the vm does not start because it has a problem at the network level, which configured with nat and bridge adapter.
The nat is ok but the bridge does not start with an error code 0X80004005 (VERR_INTNET_FLT_IF_NOT_FOUND).

I need help solving my problem.

Thank

Thank",FredC
20229,Windows10 will not boot after upgrading to 6.1.18,other,other,VirtualBox 6.1.18,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
20218,"Keep getting ""Kernel driver not installed (rc=-1908)"" error",Mac OS X,Windows,VirtualBox 6.0.16,2021-03-01T19:32:16Z,2021-03-01T19:32:16Z,"I mac a MacBook pro still using the intel processor, BigSur 11.1

At first, when I was installing version 6.1.18, I would get this error after clicking ""add"" to add the .iso file for windows 10. I tried uninstalling and reinstalling with no success. I also tried opening the VM through my applications folder as I've read that opening through the shortcut might also cause issues. Still no success. I also tried installing an older version (6.0.16) and repeated the same steps and still got the error when clicking ""add"" to add the .iso file for windows 10. Now, I get the error after clicking ""start"" for my vm. I am not sure what to do at this point. I've also ran:
{{{
sudo su
csrutil clear
reboot
}}}
 and this also didnt work. I am stuck :( 

here is the link to the screenshot of the full error in my dropbox:
https://www.dropbox.com/s/srfcpmmyf7rlj9y/Screen%20Shot%202021-02-21%20at%203.53.03%20PM.png?dl=0



",imagoat
20230,Windows 10 guest crashed when trying to paste image to guest,Linux,other,VirtualBox 6.1.18,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
20231,Network: it is not possible to set the Guest port in the Port Forwarding section (NAT),Mac OS X,Linux,VirtualBox 6.1.18,2021-03-02T21:37:56Z,2021-03-02T21:37:56Z,"it is not possible to set the Guest port in the Port Forwarding section. it is not even possible to enlarge windows.
",simone-it
20098,VM Selector GUI crash on Mojave,Mac OS X,BSD,VirtualBox 6.1.16,2021-03-03T21:59:18Z,2021-03-03T21:59:18Z,"I am experiencing a crash of the VirtualBox GUI nearly every time I use a FreeBSD, XP, or Linux guest. The guests run fine. It's pretty annoying. It doesn't hinder my use of the VM's themselves - thankfully. This happens in:

VirtualBox 5.2, 6,0, and 6.1 lines: 5.2.44, 6.0.24 and 6.1.16, specifically.

My current setup:
MacOS 10.14.6 w/16GB RAM
VirtualBox 6.1.16
MacBook Pro 15"" mid 2012

I'll attach the crash log from Apple, since it's directly relevant and the VM log from the VM that was running when it crashed (I don't know where to find the GUI log).
",decuser
18356,Guest machines randomly freezing on Windows,Windows,Windows,VirtualBox 6.0.2,2021-03-04T18:04:52Z,2021-03-04T18:04:52Z,"Guest machines are just freezing after an random number of minutes. Initially the missing guest heartbeat is just returning an error and resetting the machine. I changed the HeartbeatInterval in order to get the actual cause of this and the message before freezing is:

00:47:36.160501 AHCI#0: Port 0 reset
00:47:36.161610 VD#0: Cancelling all active requests
00:47:36.165047 AHCI#0: Port 0 reset
00:47:36.166097 VD#0: Cancelling all active requests
00:47:36.171464 AHCI#0: Port 0 reset
00:47:36.172509 VD#0: Cancelling all active requests
00:47:36.178255 AHCI#0: Port 0 reset

Same behavior on some version 5, on version 6.0.2 (latest at the time of bug recording) and 6.0.3 r128259. Logs captured from version 6.0.3.",serbanforyou
20236,The mouse is hide on text fill area on the second monitor.,Windows,Windows,VirtualBox 6.1.18,2021-03-05T14:52:53Z,2021-03-05T14:52:53Z,"Stand:
Host: Windows 10 20H2 (laptop)
Guest: Windows 7 (x64)

The mouse stay invisible when placed on any text fill place (notepad.exe for example). This problem reproduces only on second monitor when mouse in integration mode.

If change mouse mode as hooked, the problem disappears.",Nitron
20239,Breakpoint When Starting 6.1.18,Windows,Windows,VirtualBox 6.1.18,2021-03-07T14:36:12Z,2021-03-07T14:36:12Z,"I was asked to submit this bug report by scottgus1 as a result of my updated version of VirtualBox reaching a ""breakpoint"" when attempting to start it. I had no problems running version 6.1.16.

My original post is at:
https://forums.virtualbox.org/viewtopic.php?f=6&t=101947&p=495568#p495568

",SarcasticWit
20240,Host Freeze Ubuntu 20.04,Linux,other,VirtualBox 6.1.16,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
20233,Unwanted conversion dynamic to fixed disk,Linux,Windows,VirtualBox 6.1.18,2021-03-08T12:40:05Z,2021-03-08T12:40:05Z,"Hello!

I'm unsure about this is a bug or a feature, but I'm very confused about it:

I have a VM with a fixed VDI. This is explicitly what I want to have for some performance issues on Linux host. When I clone this VM via Ctrl-O, I wondering that the clone has an dynamic VDI, I didnt like that behavior. 

But really really bad is: The source VM is also converted to a dynamic VDI. Therefore I must go to the vboxmanage modifyvm twice (for source and target VM) and convert it back to fixed. These steps consumes unneccessarily space on my SSD.

Please make an selection in the GUI which target disk type is wanted. And much more important: Please leave the source VM unchanged!

Thanks and Greets!",Codehunter
16678,Huge font size in VirtualBox GUI,Windows,all,VirtualBox 5.1.20,2021-03-09T10:50:37Z,2021-03-09T10:50:37Z,"Host: Windows 10 x64 Build 1607 (""Anniversary Update"").

I installed VirtualBox without incident a few weeks ago and it worked fine (with multiple host system reboots, etc). I started VirtualBox today (5.1.18 from 2017-03-15 - so this was not after an upgrade) and the text in the UI is huge - though the application is still very readable.

I did an upgrade to 5.1.20 just now, and the issue persists.

Attached are some screenshots.

I do run a particular guest VM at 1024x768 with the window ""Scale factor"" set to 125% or 150% - and I note that a very similar issue described in #14151 seems related to the scale-factor setting: https://www.virtualbox.org/ticket/14151 - though I think he's talking about guest font size, not host font size.

I did ",daiplusplus
20241,Windows 10 Vm always crashes on startup,Windows,Windows,VirtualBox 6.1.18,2021-03-10T00:03:18Z,2021-03-10T00:03:18Z,"I downloaded the 20H2 windows 10 iso from Microsoft, and created a 64-bit Vm with that iso. However, every time the Vm starts up, I am told that a critical error has occurred and my Vm stops. I tried to increase Ram, and redownload the iso among other things, but I am not good at debugging. I would really appreciate if somebody could help me.
Thanks",ceddub
20242,VBox Hangs when trying to create VM with 2 CPUs using a Ubuntu cloud image,other,other,VirtualBox 6.1.18,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
5837,"Ability to swap ""Windows"" and ""Alt"" key mapping",Mac OS X,Windows,VirtualBox 3.1.2,2021-03-11T22:08:35Z,2021-03-11T22:08:35Z,"For a Windows guest on a Mac OS host, VB maps the Windows ""Windows"" key to the Mac ""Command"" key, and the Windows ""Alt"" key to the Mac ""Option"" key.  The problem is that those two keys are in the opposite positions of the keys on a Windows keyboard.

IOW, from left-to-right on a Windows keyboard is Control/Windows/Alt/Spacebar, while left-to-right on a Mac keyboard is Control/Option/Command/Spacebar.  Thus, for a touch typist, the mapping should be Control to Control, Windows to Option, and Alt to Command.  The current mapping forces us to learn a completely set of keystrokes on the VM than we're used to on a Windows keyboard (which we have to use anytime we're no on the VM).

Please consider providing a configuration setting that would allow the mapping of these two keys to be swapped, that is, for the Mac ""Option"" key to be mapped to Windows, and the Mac ""Command"" key to be mapped to Alt.

Thank you.",Vince Rice
20246,vboxmanage modifymedium lock not released immediately,Linux,other,VirtualBox 6.1.18,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
20247,save machine state to disk and when resume the window is the smallest possible,Linux,Windows,VirtualBox 6.1.18,2021-03-11T22:57:46Z,2021-03-11T22:57:46Z,"When you close a virtualbox window you are asked how you want to close it. If I ""save the state"" of the vm to disk and then some time in the future resumes the machine...

Windows guest: ... often when the host cpu is heavily loaded the window becomes the smallest possible (640x480) upon resume. I need manually select the window size I want. The faulty window size is otherwise saved and used during next cold start of the guest.

Linux/Windows guests: The preview in the Virtualbox Manager became strange for the Linux guest. So did the windows preview too, but since the window (for the windows guest) resized this was temporarily.

Mainly a windows' guest type error.


",Mrpn
20244,I was attempting to import VM Appliance files,other,Windows,VirtualBox 6.1.18,2021-03-12T09:29:03Z,2021-03-12T09:29:03Z,"I purchased a class “ OBIEE Developer course” on Udemy.

It requires downloading Virtual Box ( done) and VM Appliance files. No
matter, how many times I tried, it failed. Error message attached.

Kindly help me to overcome this obstacle, so I proceed with learning
the OBIEE Developer course.
 Error message. Result Code: INVALIDARG; 0x80070057
 ",Olechka
20249,When updated virtualbox. EVERY VIRTUAL MACHINE ARE NOT STARTING ANYMORE.,Windows,Windows,VirtualBox 6.1.18,2021-03-12T22:21:14Z,2021-03-12T22:21:14Z,"i Updated virtualbox only too see if they fixed a bug. then.
No virtual machine wants to start!
IDK why but i am MAD that is happening
The thing is that I cant activate hypervisor partition. What do i do??
Here is the error that appears when i open a virtual machine

Fallo al abrir una sesión para la máquina virtual Windows 7 Ultimate.

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).

Código resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Julian Gamer
20253,file system damage on flashUSB,Linux,other,VirtualBox 6.1.18,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
16436,Lagging and long pauses in all guests on recent MacOS hosts,Mac OS X,Linux,VirtualBox 5.1.14,2021-03-14T05:50:44Z,2021-03-14T05:50:44Z,"'''Developer update: this problem needs user investigation.  See comment:108.'''

when using os x (10.12.2) as the host and linux guests, gui performance is ok, except for dragging or resizing windows within the gui. then it takes several seconds for the windows to move or resize following the drag event. drag and resize both seem a little faster horizontally and vertically. horizontal is sometimes almost at normal speed. 

maximized apps (full screen) are not affected by this bug and will resize with the virtualbox window in both directions as fast as can be expected.

the only exception is ubuntu desktop, and only when guest extensions are installed. then performance is fine. gnome-desktop, in ubuntu, debian, or red-hat, still has the bug. all other desktops or window managers ive tried also show this bug, lxde, xfce, fvwm, and kde

windows and linux hosts are not affected.

to see the bug, just run a live installer like fedora, debian, or red hat. open an app window and try to drag it around. you can even run the mouse in loops or circles than sit back and watch the window follow its trail.

with debian and lxde, installing guest additions sometimes temporarily solves the issue, but then it spontaneously comes back.

mac is a late 2013 retina with hybrid intel/nvidia graphics.",pixelfairy
20256,Failed to open a session for the virtual machine Windows 10,Mac OS X,other,VirtualBox 6.1.18,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
20257,Failed to open a session for the virtual machine Windows 10,Mac OS X,other,VirtualBox 6.1.18,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
20258,Trouble shotting with connecting Print (forced reboot),other,other,VirtualBox 6.1.18,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
20259,Trouble shotting with connecting Print (forced reboot),other,other,VirtualBox 6.1.18,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
20260,My virtual machines are running slower,Windows,Windows,VirtualBox 6.1.18,2021-03-17T14:22:53Z,2021-03-17T14:22:53Z,"After a quick update to my computer, my virtual machines started to run slower, not sure why.",Guywithproblem
20261,VBoxManage import without eula acceptance returns exit code zero,Mac OS X,Linux,VirtualBox 6.1.18,2021-03-17T16:03:06Z,2021-03-17T16:03:06Z,"Hello!  I have just noticed, when doing a VBoxManage import, the command exits with exit code zero (success) even when there is a license-acceptance error.

I am running VirtualBox 6.1.18r142142.  To ensure I was up-to-date, I downloaded the 6.1.18 .dmg, used the uninstall script to uninstall, rebooted, and then used the installer to install VirtualBox (including all optional components).

Here are steps to reproduce:

1. Download the [https://www.linuxvmimages.com/images/debian-10/ Debian 10 VirtualBox image] from [https://www.linuxvmimages.com/ linuxvmimages.com] (direct link: https://sourceforge.net/projects/linuxvmimages/files/VirtualBox/D/10/Debian_10.7.0_VB.zip/download).
2. Unzip the .zip file, and get the path to the .ova file.
3. Run the command `VBoxManage import PATH_TO_OVA_FILE`.

Here is the output of what happens:

{{{
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage --version
6.1.18r142142
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage import /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova...
OK.
Disks:
  vmdisk1	549755813888	-1	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk	-1	-1

Virtual system 0:
 0: Suggested OS type: ""Debian_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""Debian_10.7.0_VB_LinuxVMImages.COM""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/Users/akkornel/VirtualBox VMs/Debian_10.7.0_VB_LinuxVMImages.COM/Debian_10.7.0_VB_LinuxVMImages.COM.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/Users/akkornel/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Debian 10.7.0
 6: Vendor (ignored): Debian Community
 7: Version (ignored): 10.7.0
 8: ProductUrl (ignored): https://www.linuxvmimages.com/debian-10
 9: VendorUrl (ignored): https://debian.org
10: Description ""Debian 10.7.0 VirtualBox Image
User Name: debian
Password: debian""
    (change with ""--vsys 0 --description <desc>"")
11: End-user license agreement
    (display with ""--vsys 0 --eula show"";
    accept with ""--vsys 0 --eula accept"")
12: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
13: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
14: Sound card (appliance expects """", can change on import)
    (disable with ""--vsys 0 --unit 14 --ignore"")
15: USB controller
    (disable with ""--vsys 0 --unit 15 --ignore"")
16: Network adapter: orig Bridged, config 3, extra slot=0;type=Bridged
17: CD-ROM
    (disable with ""--vsys 0 --unit 17 --ignore"")
18: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 18 --ignore"")
19: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 19 --ignore"")
20: SATA controller, type AHCI
    (disable with ""--vsys 0 --unit 20 --ignore"")
21: Hard disk image: source image=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, target path=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, controller=20;channel=0
    (change target path with ""--vsys 0 --unit 21 --disk path"";
    disable with ""--vsys 0 --unit 21 --ignore"")
VBoxManage: error: Cannot import until the license agreement listed above is accepted.
ITS-C02C91G0MD6R:~ akkornel(nc)$ echo $?
0
}}}

Notice how VBoxManage returns exit code zero.

I think the problem is in [https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp?rev=73217#L940 VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp around line 940].  It looks like although `RTMsgError` is called to report the problem, `rc` is never set to indicate a problem, so `RTEXITCODE_SUCCESS` ends up bring returned.",akkornel
20250,Guru Meditation on virtualbox,other,other,VirtualBox 6.1.18,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
19729,VM failed to start with enabled EFI,Windows,Linux,VirtualBox 6.1.10,2021-03-18T09:25:50Z,2021-03-18T09:25:50Z,"Approx. every tenth start/boot of the vm failed due to enabled EFI.
Failed means: the vm window opens and not output occurs.
This behavior can be seen on VBox version 6.1.10 r138449 (Qt5.6.2) and on older 
version 6.0.8 r130520 (Qt5.6.2).


",benni
19211,Guest won't boot in EFI mode after deleting/adding main disk file,Linux,Linux,VirtualBox 6.1.0,2021-03-18T09:26:14Z,2021-03-18T09:26:14Z,"Setup:
2 VDI disks.
EFI mode enabled (the main disk can only boot in EFI mode).
Hard disk as first device in System/Boot order VM settings.
Regular rebuild of disk images: regular re-add of those images in the storage settings.

After update to VBox 6.1.0, we encountered a bug where after removing and re-adding the bootable media (VDI disk) from the VM storage settings, it won't be able to boot anymore.

It tries to boot in PXE mode and drops into an EFI shell after some time.
I can boot by running the bootx64.efi executable from the shell.

When entering the bios/uefi menu (after exiting EFI shell), we can see that the disk is not in the boot options anymore, there are only PXE and EFI shell.

Reverting to 6.0.14 make it works as expected (boot correctly after disk change).",vclement
17529,VBoxManage and Guest Additions 5.x.y: Can't communicate with FreeBSD Guests,Linux,BSD,VirtualBox 5.2.6,2021-03-18T09:37:39Z,2021-03-18T09:37:39Z,"I've been trying to get FreeBSD to work with VBoxManage for a while (in fact for several years, since 9.3).

This is the result of testing VirtualBox 5.2.6 on Ubuntu with FreeBSD-11.1-RELEASE-amd64 as guest. 

{{{
$ VBoxManage guestcontrol freebsd-11.1-amd64 --username root --password 2Hard2Crack stat /tmp --verbose
Creating guest session as user 'root'...
Waiting for guest session to start...
VBoxManage: error: The specified user was not able to logon on guest
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestSessionWrap, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aSessionWaitFlags), 30 * 1000, &enmWaitResult)"" at line 938 of file VBoxManageGuestCtrl.cpp
Closing guest session ...
}}}

Guest Additions were installed with pkg:
{{{
[root@freebsd ~]# pkg install -y virtualbox-ose-additions
[root@freebsd ~]# sysrc vboxguest_enable=""YES""
vboxguest_enable: NO -> YES
[root@freebsd ~]# sysrc vboxservice_enable=""YES""
vboxservice_enable: NO -> YES
[root@freebsd ~]# reboot
}}}

Guest Additions kernel module is loaded in Guest:
{{{
[root@freebsd ~]# VBoxService --version
5.2.4r119758
[root@freebsd ~]# kldstat|grep vbox
 3    1 0xffffffff8221f000 2eacb    vboxguest.ko
}}}",Jonas Almroth
18415,Guest time lags behind after an online snapshot deletion,other,BSD,VirtualBox 5.2.26,2021-03-18T09:39:32Z,2021-03-18T09:39:32Z,"I had some mysterious cases of huge clock drifts, and other times it was perfect for days… I think I found the problem: it happens shortly after an online snapshot deletion.

Here's a log of a FreeBSD guest running on a FreeBSD host, being perfectly synchronized for the first 2h44, but then losing 60"" every 8 minutes after the snapshot is deleted.",Lapo Luchini
20238,VM Crashes at kernel loading on DELL Inspiron 7501,Windows,Linux,VirtualBox 6.1.18,2021-03-18T12:46:30Z,2021-03-18T12:46:30Z,"Hi,
I tried to run Debian / Ubuntu 20.04 on the latest stable VM Virtualbox build (Version 6.1.18 r142142) on my brand new Dell Inspiron 7501 but after the grub menu, the VM systematically crashes (black screen with blinking white hyphen). Ubuntu is not really verbose, but the last thing that Debian echoes is ""Loading ram disk..."". It's probably not the reason why it crashes but it could maybe help to delimit the source of the problem.

I tried to generate a minidump but as VirtualBox doesn't crash it is useless...

I tried enabling/disabling Hyper-V but nothing changes

I forgot to say that those two VM used to work on my old HP Omen 15 of course.

Feel free to ask me tot test things out, it would be a pleasure to find why it crashes!",Striker209
20255,Solaris 11.4 gnome continuous restarting - application 'org.gnome.Shell.desktop' killed by signal 11,Linux,Solaris,VirtualBox 6.1.18,2021-03-18T14:18:08Z,2021-03-18T14:18:08Z,Guest created from Oracle Solaris 11.4 VM Template for Oracle VM VirtualBox,Andrew Belousoff
20263,VMSVGA FIFO[350]: segfault at 4 ip 00007f92a1a969a7 sp 00007f923d3ef9a0 error 4 in nouveau_dri.so[7f92a0dc9000+dfa000],other,Windows,VirtualBox 6.1.18,2021-03-19T18:58:01Z,2021-03-19T18:58:01Z,"i have a gentoo with kernel 5.11.7 and mesa version 21.0.0 and virtualbox 6.1.18
when i enable 3D acceleration the windows 10 virtual machine suddenly crash and shuts down

this is the kernel message
[ 1228.206773] VMSVGA FIFO[10733]: segfault at 4 ip 00007f7e7b90f9a7 sp 00007f7e07d329a0 error 4 in nouveau_dri.so[7f7e7ac42000+dfa000]
[ 4207.297884] VMSVGA FIFO[13888]: segfault at 4 ip 00007f9016eb59a7 sp 00007f8fb28269a0 error 4 in nouveau_dri.so[7f90161e8000+dfa000]
[ 8372.489017] VMSVGA FIFO[350]: segfault at 4 ip 00007f92a1a969a7 sp 00007f923d3ef9a0 error 4 in nouveau_dri.so[7f92a0dc9000+dfa000]",custom
20262,"FreeBSD host, EFI guests, 6.1.18: F12 no longer presents the boot manager",other,all,VirtualBox 6.1.18,2021-03-19T19:33:45Z,2021-03-19T19:33:45Z,"With 5.2.44, if I recall correctly: 

* F12 always successfully presented the boot manager. 

With recent https://svnweb.freebsd.org/ports?view=revision&revision=567950 for the ports collection for FreeBSD: 

* 6.⋯ became available (nothing earlier than 6.1.18 was in the collection)
* end of life 5.2.44 became legacy. 

With 6.1.18, it seems: 

* boot management is impossible for guests that use EFI. 

The VirtualBox splash screen appears for no longer than a split-second (with and without keying F12), then there's the shell. 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878#c235 (comment 235) described the symptom but was – in the context of bug 234878 (emulators/virtualbox-ose: Update to 6.1) – ''not'' a show-stopper. ",Graham Perrin
19956,Disk booting no longer works automatically on EFI system after cdrom is removed,Linux,Linux,VirtualBox 6.1.14,2021-03-19T19:45:35Z,2021-03-19T19:45:35Z,"I am able to install devuan 32 bit and 64 bit to respective EFI VMs.  This involves navigating the UI and possibly booting from the EFI shell to coerce vbox to boot the install media.  However, after the install is complete, vbox correctly boots to the grub menu the installation media installed.

A problem arises, however, if I insert any arbitrary CD into the cdrom device.  Any attempt to boot off the CD requires navigating the UI again, and in most cases, requires booting from the EFI shell no matter what combination of options I select (such as deleting all but the Cdrom from the boot options and even changing the boot order).  There does not seem to be any way to get vbox to boot off the hard drive after a cd has been inserted and removed.

This behavior appears to be consistent across 32 and 64 bit EFI VMs.

Steps to reproduce:

* Create new EFI VM
* launch installer CD (most likely from EFI Shell, since vbox won't launch the CD automatically)
* complete the install and reboot from hard drive
* insert any CD into the drive
* attempt reboot
* remove the CD from the drive
* attempt to reboot from hard drive again

Expected Results:

VM will return to booting from the hard drive without needing to do anything; the grub menu will appear as normal.

Actual Results:

If the scenario is reproduced, vbox will not boot off the hard drive by itself.  It will be necessary to launch from navigating and selecting via the UI or by using the EFI shell",Harry M
20207,EFI: Incorrect behavior of ExitBootServices,other,other,VirtualBox 6.1.18,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
17013,CustomTable not present in EFI mode,all,all,VirtualBox 5.1.26,2021-03-19T19:54:09Z,2021-03-19T19:54:09Z,"{{{
VBoxManage setextradata ""VM name"" ""VBoxInternal/Devices/acpi/0/Config/CustomTable"" ""/path/to/table.bin""
}}}
(see UserManual: 9.13 Configuring the custom ACPI table)
doesn't work properly for VMs in EFI mode (but in BIOS mode).

It seems the implementation under [https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/EFI/Firmware/MdeModulePkg/Universal/Acpi/AcpiPlatformDxe/AcpiPlatform.c AcpiPlatform.c] Revision 58975 line 220 isn't present. There is no entry in ""TableInfo[]""

''' * To reproduce *'''

 1. Create a VM with EFI mode
 2. Set extra data using VBoxManage
 3. Configure custom ACPI table
 4. boot linux (like CloneZilla) in shell mode 
 5. `ls -l /sys/firmware/acpi/tables/`

The expected table isn't present. Switch to BIOS mode works correct.",vboooo
14842,Converting OVA-deployed machine to EFI gives Error: No mapping found.,Linux,Linux,VirtualBox 5.0.10,2021-03-19T19:54:16Z,2021-03-19T19:54:16Z,"I'm generating OVA template which is intended to be tested for BIOS and UEFI boot capabilities. There is no problem with regular workflow, deploy machine, turn it on and continue with BIOS boot. But once I've turned on ""Enable EFI"" options in deployed machine settings I've got error from UEFI interactive shell - Error: No mapping found. It seems VirtualBox doesn't generate UEFI default boot entries for OVA-deployed instance. Could it be fixed?",Roman Valov
20214,click close button freez machine,Linux,BSD,VirtualBox 6.1.18,2021-03-19T19:54:28Z,2021-03-19T19:54:28Z,"Halo,

the problem is that click on red cross freezing machine. I believe it is mistake because after this click the menu shows up. So when I click it on VPN server machine, to hide it down (not to shout down) I lost the connection.[[Image()]]

So my suggestion is not to freeze machine until the required action is chosen. Please take a look at enclosed picture.
file:///home/swk/Obrazy/Zrzut%20ekranu%20z%202021-02-21%2015-40-25.png
I'm not sure if it enclosed ",PimCo
19176,VirtualBox 6.1: Can't attach Nvram Storage driver (VERR_PDM_DRIVER_NOT_FOUND),all,all,VirtualBox 6.1.0,2021-03-19T19:55:14Z,2021-03-19T19:55:14Z,"Setting any NVRAM variables (`VBoxInternal/Devices/efi/0/LUN#0/Config/Vars/`) results in the error `Can't attach Nvram Storage driver (VERR_PDM_CFG_MISSING_DRIVER_NAME)`

Setting the driver name as it was in VirtualBox 6.0 and earlier (`VBoxManage setextradata VMname 'VBoxInternal/Devices/efi/0/LUN#0/Driver' 'NvramStorage'`) results in the error `Can't attach Nvram Storage driver (VERR_PDM_DRIVER_NOT_FOUND)`.

VirtualBox 6.0 powers on the VM fine, 6.1 doesn't power on with the above errors.",Jack_Smith
20162,Crash when VM reboots due to null memory reference,Windows,all,VirtualBox 6.1.18,2021-03-20T07:19:24Z,2021-03-20T07:19:24Z,"Hello there,

I've noticed lately that when VirtualBox reboots, either via VirtualBox (HOST+R or similar) or instructed by the guest, this fails entirely and crashes with a null memory reference.

* It impacts any guest VM.
* It doesn't impact ACPI shutdown or hard power off, these seem to close gracefully.
* It doesn't particularly matter what stage the guest is at, it'll occur seconds after powering on, or hours after running.
* This impacts running a VM normally and headlessly.

Specifically the error message is ""The instruction at 0x00007ffab544f3bc referenced memory at 0x0000000000000000. The memory could not be read.""

At this point I can power off the virtual machine and start it up again normally, but I worry if any pending storage writes will have been lost causing corruption. (I did very recently lose a guest due to storage corruption, unsure if this caused it.)

Unfortunately attaching a debugger never seems to succeed, so I'll attach some memory dumps of ""VirtualBoxVM.exe"" and ""VBoxHeadless.exe"" when the fatal error message was present.

I did attempt removing and reinstalling VirtualBox, including a whole reboot between, the only change was the memory address of the instruction. I can replicate this incredibly reliably though if further memory dumps are helpful.",Adam Reece
20272,Windows 10 guest freezes randomly on Windows 10 host when accessing files on shared folders,Windows,Windows,VirtualBox 6.1.18,2021-03-24T12:53:05Z,2021-03-24T12:53:05Z,"Weeks ago, after updating from 6.1.12 to 6.1.16 my VM started freezing when I accessed files from a shared host folder. It mostly happens when I trie to browse the shared folder from an application's open file dialog. Reverting back to 6.1.12 did not resolve the issue. This started to happened more frequently, so that I finally could no longer work with that VM and had to recover an older state from a backup. 
Now that some weeks have passed, the issues start again. I upgraded to 6.1.18 without success. Note that I already had issues with shared folders (e.g. can't start executables because they don't exist, copying several files will only copy some files etc) 
But now the issue completly freezes the client each time with increasing frequency.
",bartislartfass
19908,Mouse not working in Virtualbox 6.1.14 with Arch Linux as Host,Linux,Linux,VirtualBox 6.1.14,2021-03-24T19:25:54Z,2021-03-24T19:25:54Z,"I installed Kali Linux as Guest OS while the Host OS is Arch Linux. Whenever I go to Full-screen mode and return back to normal screen mode, the Mouse/Touchpad click is not working. I can move the cursor, but cannot click/tap or scroll through anything in both Guest OS (Kali) and Host OS (Arch).

Steps to Reproduce:
1. Install Kali Linux as Guest and fully update the Guest OS.
2. Reboot the VM.
3. Switch to full screen mode with Host+F.
4. Again, switch to normal screen mode with Host+F.
5. Now, the mouse/touchpad stops working except moving the cursor in both Host(Arch) and Guest(Kali) OSs

This steps to reproduce fail rarely, but I can assure you it happens randomly each time when you stat up the VM and surf a bit.

When I shutdown my Guest(Kali) VM, then the mouse/touchpad operates normally as before.

My Laptop Specs:
Lenovo L340-15IWL
Intel i5-8265U
8GB DDR4 RAM
Intel UHD Graphics 620",404_vip_not_found
20271,nested virtualisation with kvm cpu hits 100% then L2 guest crashes,Windows,Linux,VirtualBox 6.1.18,2021-03-24T21:41:10Z,2021-03-24T21:41:10Z,"Hi,

It maybe that this is known not to work but in the 6.1 docs it mentions kvm as an L2 hypervisor so I thought I'd give it ago.

I have Intel I7 9th gen chip with 6 cores running windows 10 Enterprise build 18363 as my L0

I tried this originally on vbox 6.1.16 but upgraded to 6.1.18 after reading https://www.virtualbox.org/ticket/19315. This caused https://www.virtualbox.org/ticket/20199 so I'm currently running the 6.1.19 test build which fixes the crash but didnt resolve my problem first observed in 6.1.16 so I'm guessing its something different. 

Redhat mention they support some combinations in tech preview when the L0 is RHEL8.2. They say others eg: VMware, Xen, Amazon AWS, Nutanix AHV, Oracle VM are not. 

My use case for this is purely local lab environments mainly in vagrant so I'm more interested in if it work or not then support.

I'm trying to use packer inside a centos7 L1 VM to build with the qemu builder with kvm accelerator.

Packer is able to launch the VM and it starts the install. Its pretty slow but eventually fails installing this glibc.i686 package

{{{
Installing glibc.i686 (684/694)
[ 1354.721435] double fault: 0000 [#1] SMP
[ 1354.722093] Modules linked in: xfs fcoe libfcoe libfc scsi_transport_fc scsi_tgt zram sg pcspkr joydev i2c_piix4 parport_pc parport ext4 mbcache jbd2 loop nls_utf8 isofs sr_mod cdrom 8021q garp mrp stp llc virtio_net virtio_blk net_failover failover drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ata_generic pata_acpi drm ata_piix libata serio_raw virtio_pci virtio_ring virtio drm_panel_orientation_quirks sunrpc xts lrw gf128mul dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq libcrc32c async_xor xor async_tx raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs cramfs edd
[ 1354.722093] CPU: 0 PID: 17227 Comm: glibc_post_upgr Not tainted 3.10.0-1160.el7.x86_64 #1
[ 1354.722093] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.5.1 01/01/2011
[ 1354.722093] task: ffff9fa564fe8000 ti: ffff9fa562bdc000 task.ti: ffff9fa562bdc000
[ 1354.722093] RIP: 0010:[<00000000b5f97d80>]  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093] RSP: 0018:0000000000000000  EFLAGS: 00010082
[ 1354.722093] RAX: 000000000000007a RBX: 00000000ffcc49ca RCX: 0000000000000000
[ 1354.722093] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
[ 1354.722093] RBP: 00000000ffcc495c R08: 0000000000000000 R09: 0000000000000000
[ 1354.722093] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1354.722093] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1354.722093] FS:  0000000000000000(0000) GS:ffff9fa5bcc00000(0000) knlGS:0000000000000000
[ 1354.722093] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 1354.722093] CR2: 00000000b5f97d80 CR3: 0000000022a7c000 CR4: 00000000000006f0
[ 1354.722093] Call Trace:
[ 1354.722093] Code:  Bad RIP value.
[ 1354.722093] RIP  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093]  RSP <0000000000000000>
[ 1354.722093] ---[ end trace 6fd2b3e5f947f091 ]---
[ 1354.722093] Kernel panic - not syncing: Fatal exception
[ 1354.722093] Kernel Offset: 0x34800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
}}}

I see some people are able to get kvm to run fine in vbox. But I'm wondering if they have AMD chips on the L0 or some other fundamental difference.

Any suggestions on how to try to debug this further?


",aw125
20270,Arch linux guest crash after windows 10 host resume from sleep,Windows,Linux,VirtualBox 6.1.18,2021-03-25T09:27:40Z,2021-03-25T09:27:40Z,"I wrote a topic about this on the virtualbox forum[https://forums.virtualbox.org/viewtopic.php?f=6&t=102250&sid=f398ac48ffa5927918c82d13ef2c7ce8].

Here are how I reproduce the problem:

----
1. start Arch linux guest
2. Windows 10 host sleep
3. resume Windows 10 host
4. Arch linux guest is PAUSED, try to resume it
5. whole virtualbox interface freeze, crash (log ""carsh"")

----
However, if I pause and resume the guest manually once before the host go to sleep, the probelem is gone.

----
1. start Arch linux guest
2. pause guest and resume it immediately
3. Windows 10 host sleep
4. resume Windows 10 host
5. arch linux guest is RUNNING, everything works fine (log ""workfine"")

----

Additionally, I also have a windows 10 guest and a ubuntu 16.04 guest, neither of them have this problem.",lindeshun
20274,VM's do not funtion on Win10,Windows,Linux,VirtualBox 6.1.18,2021-03-26T01:25:30Z,2021-03-26T01:25:30Z,"I am running windows 10 pro on my pc. Two days ago I turned on a VM which I use regularly, but it gets stuck trying to ""Start VM."" The VM never starts, VirtualBox says that it is at 20%, so I kill it in task manager. However, I am not able to kill VBoxSVC.exe. I turned on Hyper-V and cloned that VM to it to make sure that it is not corrupt (I disabled Hyper-V after verifying). 

I downloaded two other VM's to see if they would function. These new VM's can start, but when I try to shut them down they freeze. Oddly enough, this event prevents me from being able to turn off my pc, so I have to unplug it from the wall. 

The logs I am including in this ticket are for the first VM I referenced. I have Virtualbox 6.1.18 installed on my pc (normally). During my troubleshooting I also installed the most recent 5.x.x version to see if it would have any effect (same symptoms).",GeneralKenobi
20243,All Virtual Machine freeze when loading into OS,other,other,VirtualBox 6.1.18,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
20275,VM stops when installation of WinSvr2019 on Windows10 (mac dual boot),other,Windows,VirtualBox 6.1.18,2021-03-26T11:18:58Z,2021-03-26T11:18:58Z,"Hi There,

The VM freeze when I install Windows Server 2019 on windows 10 (dual boot from Mac).  The Error can be found in attached.

Appreciated if you can advice a solution.

Regards,
NelNel",NelNel
20276,Virtualbox6.1.18 don't work with Windows 10 (Failed to load R0 module),Windows,Linux,VirtualBox 6.1.18,2021-03-26T15:14:09Z,2021-03-26T15:14:09Z,"Hello,
When I try to open my Ubunto VM the Virtual machine pop up the following error:

Failed to open a session for the virtual machine UbuntuES.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).

Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


I have already tried to reinstall the VM software with no Success;
I've tried to Disable Windows Hyper-V;

Please advise.",Fpedrosa
19988,VM crashes or restarts during package upgrade on FreeBSD guest,Linux,BSD,VirtualBox 6.1.16,2021-03-26T21:01:07Z,2021-03-26T21:01:07Z,"Hi,

my host machine is Debian GNU/Linux 10.6 latest and up to date (21 Oct 2020). VirtualBox version is 6.1.16.

I have a FreeBSD guest - FreeBSD 12.1-RELEASE-p10 GENERIC.

When I try to upgrade packages on guest (FreeBSD) the virtual machine restarts or vanishes.

I could not reproduce the issue with previous versions of VirtualBox (6.1.x) or with Linux guest including VirtualBox 6.1.16.

There is a video.

https://www.youtube.com/watch?v=dqjWNC7nPX0

Kind regards
Georgi
",Georgi
20076,Warn people about memory corruption in VMs due to Intel Power Gadget run on host macOS,Mac OS X,all,VirtualBox 6.1.16,2021-03-27T09:18:10Z,2021-03-27T09:18:10Z,"When running Intel Power Gadget (IPG) on a macOS host alongside VirtualBox it can cause memory corruption in the VirtualBox guests, causing al kinds of random errors, data corruption and eventually kernel panics in the guests.

However, the memory corruption can stay hidden for a while because it will not always directly lead to observable errors. And because IPG seems like an innocent monitoring tool, many people will be oblivious to this corruption due to IPG.

Some other reports about this:
https://forums.virtualbox.org/viewtopic.php?f=8&t=97929
https://stanislas.blog/2020/02/crashes-virtualbox-macos-intel-power-gadget/

Because of the severity of the problem and the fact that it is far from apparent that this is caused by IPG, I think it is wise to warn people about this.

Maybe just add some text on the download page, or maybe even better add a warning in VirtualBox if it detects com.intel.driver.EnergyDriver is loaded.
",janvenekamp
11903,Add VboxControl guestproperty with vm's name.,all,all,VirtualBox 4.2.14,2021-03-27T18:41:17Z,2021-03-27T18:41:17Z,Please add a property to access virtual machine's name via VboxControl it will be very nice for e.g. automatically set hostname of cloned machines.,Fat-Zer
20279,Long-timeout TCP Sessions,Windows,Linux,VirtualBox 6.1.18,2021-03-28T20:53:11Z,2021-03-28T20:53:11Z,"I have a case with long time-out TCP sessions that come from VirtualBox NAT network mode. When I created half-open TCP sessions from the VM to an external TCP Host (by sending SYN packets but not reply the SYN/ACK with ACK packets). After 10 seconds, the external TCP Host proceeded to close the connections by sending FIN packets. This put the port VirtualBox used for those connections to CLOSE_WAIT state. As I observed, the current VirtualBox's CLOSE_WAIT timeout is about 10 minutes.

I have a theory that, if I can generate enough number (maybe 40,000?) of CLOSE_WAIT state TCP sessions, I can occupy all of the port VirtualBox can use for transmitting, which make the internal VM can not create new connection with external hosts, for 10 minutes. 

I suggest that the CLOSE_WAIT timeout should be lowered to 2 minutes to counter the possible problem.",nds21
20277,VirtualBox 6.1.18 freezes when trying to start a Ubuntu installation from CD image,Linux,Linux,VirtualBox 6.1.18,2021-03-29T05:33:31Z,2021-03-29T05:33:31Z,"Host:

vbox-cloud ➤ uname -a                                                          
Linux paag-EliteBook 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox:

vbox-cloud ➤ vboxmanage --version                                              
6.1.16r140961

How to reproduce the *freeze*:

Define a VM with 4G RAM, 40G HDD (in fact anything that can run Ubuntu 20.04)
Define the VM to run with 2 vcpus (this is the critical stuff)
Attach the Ubuntu 20.04 live image to the CDROM in the VM
Boot the VM and watch it freeze VirtualBox
",paaguti-u
19395,Solaris guest appears to hang for minutes after keyboard bell,other,Solaris,VirtualBox 6.1.4,2021-03-30T22:56:38Z,2021-03-30T22:56:38Z,"There is an apparent misbehavior I noticed when running Solaris 11.4 and Solaris Trunk guest VMs, it appears to hang/freeze for a couple of minutes when you get the Gnome terminal to issue a keyboard bell, eg. when you delete more characters in the command line using the backspace key as there are. Then the keyboard bell rings and then the guests Gnome desktop appaers to
be frozen for a couple of minutes and then returns back to normal.
This is very simple and quick to reproduce.

{{{
Solaris 11.4 latest SRU
fail:
Host Driver: PulseAudio
Controller: ICH AC97

Solaris 11.4.0.15.0 aka 11.4 FCS
fail:
Host Driver: OSS Audio Driver
Controller: ICH AC97

Solaris Trunk 11.5.0.65.0
fail:
Host Driver: PulseAudio
Controller: ICH AC97
}}}

{{{
WORKAROUND:

Disable the audio device in the VM settings.
}}}

It sounds like some problem with audio, but I don't know if anyone runs Solaris on real hardware that has audio and can verify if that
happens as well on bare metal using Gnome.

This happen regardless whether or not one uses the Gnome terminal or just a simple Xterm. Same result.

That might be a bug in our audio emulation or in Solaris.

And when it is hung serial console access works fine so it is just Gnome that is stuck/frozen for a couple of minutes.

The problem does not show up with Solaris 10 or OpenIndiana based guest VMs running their corresponding Gnome desktops.",Frank Batschulat (Oracle)
15144,BSOD - Windows 10 host VBoxNetLwf.sys,Windows,Windows,VirtualBox 5.0.14,2021-03-31T21:56:18Z,2021-03-31T21:56:18Z,"I have had a handful of intermittent Windows 10 'blue screen of death' host crashes of type PAGE FAULT IN NONPAGED AREA which mention VBoxNetLwf.sys over the last few weeks. This has been observed with multiple minor releases of VirtualBox since version 5.0 and multiple releases of Windows 10 Professional. 

I suspect this may not be a VirtualBox bug and more likely an issue with our security software (Symantec Endpoint Protection) or the host Windows OS (as I only noticed this issue since updating from Win 8.1 Pro). 

Happy to provide any more info that might help, attached a screen grab of the crash. ",kpm
20084,Virtual Box issues with kernel 5.9.12-lp152.50-preempt?,Linux,Solaris,VirtualBox 6.1.16,2021-04-02T05:22:04Z,2021-04-02T05:22:04Z,"Hi, folks,

I am encountering problems when using the kernel version described in the summary. I am running opensuse-Linux 15.2 as host and Solaris 11.4 as guest. (an image provided by Oracle) Installation of VirtualBox 6.1.16 goes fine, just booting the Solaris virtual machine doesn´t happen, it just hangs when reaching 20%. Any ideas? 

Yours,

Reinhard",Reinardo
20281,Critical error CentOS 7,Windows,Linux,VirtualBox 5.2.16,2021-04-02T10:18:23Z,2021-04-02T10:18:23Z,"Once a week, a virtual machine running centos 7 crashes with a critical error. Windows server 2008 r2 host - freezes. It is not possible to shutdown virtualbox. Only rebooting the host helps.",Ruby_Ridge
19231,Network interface not found error after upgrading to 6.1.0,Mac OS X,all,VirtualBox 6.1.2,2021-04-02T10:33:02Z,2021-04-02T10:33:02Z,"After upgrading to VB 6.1.0 and still with 6.1.2 I get the following error when trying to start both Windows and Linux VMs: 

Could not start the machine Linux OBI 7.2.64.0 because the following physical network interfaces were not found:
en4: Thunderbolt Ethernet Slot 2 (adapter 1)
You can either change the machine's network settings or stop the machine.

This always worked before. This is a MacOS Catalina host (10.15.2) using a wired ethernet connection off a Thunderport dock. The interface name is ""en4: Thunderbolt Ethernet Slot 2"". I am using this in bridge mode. Switching to NAT works fine.


",Stooxie
20282,virtualbox manager (win) crashes when starting on 2nd screen,other,all,VirtualBox 6.1.18,2021-04-02T12:45:16Z,2021-04-02T12:45:16Z,"The VB Manager app works fine in my current setup (dell latitude 7290 latitude with attached 2nd monitor asus zenscreen via usb-c) if it is started on the main windows screen.
It crashes a few seconds after starting if it is started instead on teh 2nd screen.
In order to reproduce: start the Manager, vmove it to the 2nd screen, then shut it down, so that it will start there.
2nd screen is set at 125% scaling in windows settings.

Windows event manager says Exception code 0xc0000005, fault offset 0xc)...01f0c38 in Qt5GuiVbox.dll",gggeek
20286,máquina demorando para iniciar,Linux,Linux,VirtualBox 6.1.18,2021-04-04T01:58:10Z,2021-04-04T01:58:10Z,"já tentei de varias formas corrigir isso, instalei extensões (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)
 e também pack pra distribuição a qual eu uso (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1).deb)

 E ate agora nada, uso o Linux da ofensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b)
 imagem pronta.
[[BR]]
 Inicio a maquina e deixo o computador ligado, e ela varou  passou 28 horas sem sair da tela preta com a logo do kali ",anjo gelado
20288,absurd delay to start virtualization,Linux,Linux,VirtualBox 6.1.18,2021-04-04T13:41:19Z,2021-04-04T13:41:19Z,"I tried in many ways to correct this, I installed medications (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)

and also a distribution pack that I use (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1) .deb)

And so far nothing, I use the Linux of the offensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b) image ready.


I start the machine and leave the computer on, and it went 28 hours without leaving the black screen with the kali logo
",anjo gelado
20292,Trackpad and mouse failure on using trackpad gestures in Gnome 40,other,other,VirtualBox 6.1.18,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
20296,vbox 6.1.18: virt-install cause vm crash (guru meditation),Linux,Linux,VirtualBox 6.1.18,2021-04-09T12:23:55Z,2021-04-09T12:23:55Z,"I met a critical vbox error that I would like to report.

I reproduced this problem on 2 different vbox hypervisors.

== Facts ==
* hypervisor is running ubuntu 20.04 LTS (up to date) + vbox 6.1.18
* nested vt-x is enabled
* guest is running ubuntu 20.04 LTS (up to date, installed manually from ubuntu-20.04.2.0-desktop-amd64.iso)
* guest is running qemu/kvm (installed from ubuntu distro)

== Reproducer ==
* apt install qemu-kvm virtinst virt-manager libguestfs-tools bridge-utils
* cd /tmp && wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/x86_64/alpine-standard-3.13.4-x86_64.iso
* virt-install --connect qemu:///system --virt-type kvm --name alpine --ram 512  --vcpus 1  --disk path=/dev/vmvg/vm --cdrom=/tmp/alpine-standard-3.13.4-x86_64.iso --network none --graphics none --arch x86_64 --os-type=generic --cpu host --noautoconsole
",Arnaud Veron
20297,VM crashes after starting recording,Windows,Linux,VirtualBox 6.1.18,2021-04-10T09:31:42Z,2021-04-10T09:31:42Z,"VM immediately crashes when starting recording:

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFE918E77E3 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------


Host: Windows 10 x64
Guest: Arch Linux x64 (UEFI boot)

To reproduce:
1. Boot from Arch Linux iso
2. Start recording (View\Recording)

PS. Starting recording via command line works just fine.
",1ns
20298,VBox Additions on Linux = Blackscreen after Boot,Windows,Linux,VirtualBox 6.1.18,2021-04-10T20:06:08Z,2021-04-10T20:06:08Z,"I have a problem with VirtualBox on Windows 10 Professional 20H2. I want to run XFCE, KDE and other desktops on VirtualBox, but when I install the additions and I reboot, i just get a blackscreen. I can't provide logs from Linux (because the blackscreen happens), and in the VirtualBox logs is nothing special.",JeremyStarTM
20299,VM hung at installation,Windows,Windows,VirtualBox 6.1.18,2021-04-11T22:42:31Z,2021-04-11T22:42:31Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20300,VM hung at installation,Windows,Windows,VirtualBox 6.1.18,2021-04-11T22:43:10Z,2021-04-11T22:43:10Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20301,vboxmanage startvm fails if new Linux Kernel is installed,other,other,VirtualBox 6.1.18,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
18776,"Vagrant shared folders unable to install Package Management Plugins (Composer, PHP)",Mac OS X,Linux,VirtualBox 6.0.10,2021-04-15T22:28:48Z,2021-04-15T22:28:48Z,"## Versions

* MacOS: Mojave 10.14.5 (18F132)
* Virtualbox: `6.0.10 r132072 (Qt5.6.3) (And Exentions)`
* Vagrant: 2.2.5
* Vagrant box: bento/ubuntu-18.04 201906.18.0

## Problem

Unable to install Composer (PHP Package Manager) plugins on folders shared via Virtualbox (vboxsf)

## Steps To Reproduce:

Clone: https://github.com/svpernova09/vagrant-test

* Adjust folder share of `~/Code/fresh-laravel` to a fresh [Laravel](https://github.com/laravel/laravel) installation
* Run `vagrant up`
* Run `vagrant ssh`
* Run `cd larvel`
* Run `composer require ocramius/package-versions`
* See ""Could not delete /home/vagrant/laravel/vendor/ocramius/package-versions/src/PackageVersions:""
* Run `cd`
* Run `composer create-project laravel/laravel not-vbox-share`
* Run `cd not-vbox-share`
* Run `composer require ocramius/package-versions`
* See ""Package manifest generated successfully.""

## Logs

Here is a gist of the relevant actions: https://gist.github.com/svpernova09/17f7a2c9aba316e24bb063a25010d6f6",Svpernova09
19086,rm / rmdir  not working correctly in shared folders,Windows,Linux,VirtualBox 6.0.14,2021-04-15T22:30:27Z,2021-04-15T22:30:27Z,"As it seems that comments to existing tickets are not enough, I make a ticket out of my comment to #18569.

Since the beginning of VirtualBox v6.x the ""rm -r"" command is not working correctly in shared folder within a Linux guest.

I attach a screen shot of an example what happens.

Host: Windows 10 1903
Guest: CentOS 6.6, kernel 2.6.32-504.el6.x86_64",Reiner Brodbeck
20278,Hardware Virtualization error on non Hardware Virtualization CPU,other,Windows,VirtualBox 6.1.18,2021-04-15T23:42:57Z,2021-04-15T23:42:57Z,"dad@dad-Inspiron-1545:~$ uname -a

Linux dad-Inspiron-1545 5.4.0-70-lowlatency #78-Ubuntu SMP PREEMPT Fri Mar 19

15:09:48 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

dad@dad-Inspiron-1545:~$ 

========================================================

Failed to open a session for the virtual machine WIN-XP.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: NS_ERROR_FAILURE (0x80004005)

Component: ConsoleWrap

Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

6.1.16_Ubuntu r140961
=======================================================

lshw information

=======================================================

dad-inspiron-1545

    description: Portable Computer

    product: Inspiron 1545

    vendor: Dell Inc.

    serial: HGHYXJ1

    width: 64 bits

    capabilities: smbios-2.4 dmi-2.4 smp vsyscall32

    configuration: boot=normal chassis=portable uuid=44454C4C-4700-1048-8059-
C8C04F584A31

  *-core

       description: Motherboard

       product: 0G848F

       vendor: Dell Inc.

       physical id: 0

       serial: .HGHYXJ1.CN7016699J04EU.

     *-firmware

          description: BIOS

          vendor: Dell Inc.

          physical id: 0

          version: A14

          date: 12/07/2009

          size: 64KiB

          capacity: 16MiB

          capabilities: isa pci pcmcia pnp upgrade shadowing cdboot bootselect 
int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp smartbattery biosbootspecification netboot

     *-cpu

          description: CPU

          product: Pentium(R) Dual-Core CPU       T4300  @ 2.10GHz

          vendor: Intel Corp.

          physical id: 400

          bus info: cpu@0

          slot: Microprocessor

          size: 1995MHz

          capacity: 2100MHz

          width: 64 bits

          clock: 200MHz

          capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm pti dtherm cpufreq

====================================================================

Please note that the newest Dell BIOS (A14) for this laptop will support a hardware virtualization CPU in the same socket as is now holding Intel T4300 CPU but the CPU installed does not support this. Therefore the required option to turn on/off hardware virtualization is not available in the BIOS presented to me. The virtualbox startup file has all hardware virtualization turned off.


",winthrom2
20306,VirtualBox crashes on IO in FreeBSD 13,Windows,BSD,VirtualBox 6.1.18,2021-04-20T10:01:34Z,2021-04-20T10:01:34Z,"I started up a FreeBSD 13 VM that I've had for a little bit on VB 6.1.16, started installing some packages, and suddenly the VM crashed and displayed ""Aborted"" on the management interface.

I upgraded VB to 6.1.18, booted the VM, started installing the same packages again, and lo and behold, it died again.

I've attached the log from the VM dying on 6.1.18.",rincebrain
20308,vboxsf module (GA 6.0.24) fails to compile on latest ubuntu-16.04 kernel,Linux,Linux,VirtualBox 6.0.22,2021-04-20T18:32:33Z,2021-04-20T18:32:33Z,"Attempting to build the vboxsf module for Guest Additions 6.0.24 fails on the latest ubuntu-16.04 kernel (`4.4.0-209-generic #241`).
{{{
vagrant@ubuntu-16:~$ uname -a
Linux ubuntu-16 4.4.0-209-generic #241-Ubuntu SMP Tue Apr 13 01:06:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
}}}

Snipped output from attempting to build the module manually with `build_in_tmp` (full log attached):
{{{
=== Building 'vboxsf' module ===
make[1]: Entering directory '/tmp/vbox.0/vboxsf'
make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/4.4.0-209-generic/build M=/tmp/vbox.0/vboxsf SRCROOT=/tmp/vbox.0/vboxsf -j2 modules
make[2]: Entering directory '/tmp/vbox.0/vboxsf'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /tmp/vbox.0/vboxsf/vfsmod.o
  CC [M]  /tmp/vbox.0/vboxsf/dirops.o
  CC [M]  /tmp/vbox.0/vboxsf/lnkops.o
  CC [M]  /tmp/vbox.0/vboxsf/regops.o
  CC [M]  /tmp/vbox.0/vboxsf/utils.o
/tmp/vbox.0/vboxsf/utils.c: In function 'vbsf_inode_setattr':
/tmp/vbox.0/vboxsf/utils.c:812:10: error: implicit declaration of function 'inode_change_ok' [-Werror=implicit-function-declaration]
     rc = inode_change_ok(pInode, iattr);
          ^
cc1: some warnings being treated as errors
scripts/Makefile.build:288: recipe for target '/tmp/vbox.0/vboxsf/utils.o' failed
make[3]: *** [/tmp/vbox.0/vboxsf/utils.o] Error 1
make[3]: *** Waiting for unfinished jobs....
Makefile:1472: recipe for target '_module_/tmp/vbox.0/vboxsf' failed
make[2]: *** [_module_/tmp/vbox.0/vboxsf] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-209-generic'
/tmp/vbox.0/vboxsf/Makefile-footer.gmk:117: recipe for target 'vboxsf' failed
make[1]: *** [vboxsf] Error 2
make[1]: Leaving directory '/tmp/vbox.0/vboxsf'
Makefile:48: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 1
}}}

It looks like a recent kernel update (https://ubuntu.com/security/notices/USN-4916-1) involving some CVE fixes also backported the migration from `inode_change_ok` to `setattr_prepare`.
That migration has previously broken Guest Addition compilation at least a couple times for other distros (https://www.virtualbox.org/ticket/17299, https://www.virtualbox.org/ticket/18697).
There are some existing IFDEFs in `VBox/Additions/linux/sharedfolders/utils.c` related to those previous issues:
{{{
#if (RTLNX_VER_RANGE(3,16,39,  3,17,0)) || RTLNX_VER_MIN(4,9,0) || (RTLNX_VER_RANGE(4,1,37,  4,2,0))
# if RTLNX_VER_MIN(5,12,0)
    rc = setattr_prepare(ns, dentry, iattr);
# else
    rc = setattr_prepare(dentry, iattr);
# endif
#else
    rc = inode_change_ok(pInode, iattr);
#endif
}}}
but they don't cover this case yet since it's a 4.4.0 series kernel.
",jonahbull
19824,Guru Meditation (tripple fault) while using GNS3,Linux,Linux,VirtualBox 6.1.10,2021-04-21T11:07:18Z,2021-04-21T11:07:18Z,"Hello,

I'm using gns3 VM, which launches QEMU VMs, inside virtualbox 6.1.12 (this bugtracker is still missing that version). Today, I got a VINF_EM_TRIPLE_FAULT

I'll attach VBox.log",Luiz Angelo Daros de Luca
20311,Failed to create a host network interface.,Windows,Linux,VirtualBox 6.1.20,2021-04-21T16:59:18Z,2021-04-21T16:59:18Z,"Failed to create a host network interface.

SetupDiCallClassInstaller (DIF_INSTALLDEVICE) failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

",TH
20312,Machine does not terminate: VBOX_E_INVALID_VM_STATE (0x80BB0002),Linux,Linux,VirtualBox 6.1.20,2021-04-22T05:33:58Z,2021-04-22T05:33:58Z,"Invalid machine state: Stopping.


Fehlercode: 
VBOX_E_INVALID_VM_STATE (0x80BB0002)
Komponente: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Log attached

Issue first occured today, with VirtualBox 6.1.20",Thermi
20314,0x00007FF874BF9B2C address,Windows,other,VirtualBox 6.1.18,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
20302,Client ID prevails over MAC based mapping with the NAT Network DHCP server,Linux,Linux,VirtualBox 6.1.18,2021-04-22T14:00:30Z,2021-04-22T14:00:30Z,"I've got two Ubuntu (though what matters here is Systemd-Network) guest VMs connected to a NAT Service network with the DHCP service enabled.
I have added a static mapping between the guests NIC MAC addresses and their assigned IPs. The NatNetwork-Dhcpd.config file shows what I mean:

    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

The same information is reflected in `VirtualBox.xml` (the global config file) though when using `VBoxManage` to set up the mapping I did use the first NIC of each guest to set the mapping hence the `/0` after the guest VM UUID:


    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

Now it comes the twist: DHCP Client ID in machines running Systemd-Network use /etc/machine-id to construct it but both machines have the same contents (due to cloning, you know) in this file hence the Client ID sent to the DHCP is always the same (as seen in NatService-Dhcpd.log)... and the dhcp server in the Nat Service returns the same IP address for both guests.

Is it a bug, a feature or just RFC compliance?
Thanks in advance.",jcb
10031,High I/O causing filesystem corruption,Linux,Linux,VirtualBox 4.1.4,2021-04-22T15:10:32Z,2021-04-22T15:10:32Z,"Hello,
We are running an Ubuntu 10.04 32bit guest on a RHEL 64 bit host. The guest storage control is SATA AHCI with host I/O caching enabled. 
Host info:
OS Type:	Linux (2.6.18-194.el5)
VirtualBox:	4.1.4 (74291)
Processors:	Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2)
HWVirtEx, PAE, Long Mode (64-bit)

It seems during times of high I/O, like backups and etc, the guest filesystem resets to read-only. We have this issue with both ext3 and ext4 filesystems. Switching to ext3 seemed to lessen the occurrences though.

Here is a snip of syslog around the time of the corruption..


{{{
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:29 vault kernel: [ 2338.011698] ata4.00: exception Emask 0x0 SAct 0xffff SErr 0x0 action 0x6 frozen
Dec 15 08:02:29 vault kernel: [ 2338.011714] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011721] ata4.00: cmd 61/00:00:b7:5c:9d/04:00:09:00:00/40 tag 0 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011723]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011726] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011729] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011736] ata4.00: cmd 61/00:08:77:31:9d/04:00:09:00:00/40 tag 1 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011737]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011740] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011743] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011749] ata4.00: cmd 61/00:10:77:35:9d/04:00:09:00:00/40 tag 2 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011751]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}
And then later on in the file....
{{{
Dec 15 08:02:29 vault kernel: [ 2338.011969] ata4: hard resetting link
Dec 15 08:02:29 vault kernel: [ 2338.332268] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 15 08:02:33 vault kernel: [ 2342.108804] ata4.00: configured for UDMA/133
Dec 15 08:02:33 vault kernel: [ 2342.108811] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108815] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108818] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108820] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108823] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108826] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108829] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108831] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108834] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108837] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108840] ata4.00: device reported invalid CHS sector 0
}}}

At this point the guest needs to be shut down and the drive mounted and fsck, which complains about allot of IO handle stuff.",Indigo42
20316,Mouseclicks doesn't respond when attempting to install Fedora 33,other,Linux,VirtualBox 6.1.18,2021-04-22T21:12:22Z,2021-04-22T21:12:22Z,"Steps to reproduce:

1. Download the Fedora 33 Everything (netinstall) ISO
2. Boot the system
3. The installer won't past the first screen, because the mouseclicks doesn't respond.

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-16-generic
OS Type: 64-bit
Graphics Platform: X11",radulf
20317,Seamless Mode Windows 10,Linux,Windows,VirtualBox 6.1.18,2021-04-23T06:32:08Z,2021-04-23T06:32:08Z,"I am running OpenSuse Leap 15.1 as the host and Windows 10 Pro as a guest. If my guest operating system Windows 10 switches to Seamless Mode Host + L, only windows that are not integrated Windows applications are displayed correctly. The taskbar disappears when, for example, I click Start. Windows windows are only visible if an application that is not provided for Windows is open on the desktop and serves as a background. My VirtualBox version is 6.1.18 r142142 (Qt5.12.7).
Guest additions and the current Extensions Pack are also installed.
As a guest I also have a Windos7 Pro operating system and everything works perfectly!",Compaq
20318,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,Linux,VirtualBox 6.1.20,2021-04-23T07:25:42Z,2021-04-23T07:25:42Z,"Hi,
any help please",olfat
20321,disk vmdk corrupted,Windows,Linux,VirtualBox 5.2.32,2021-04-23T17:36:32Z,2021-04-23T17:36:32Z,"I want to describe my happening:
I have 2 laptops
One with Virtual box 5.2.32 r132073 (Qt5.6.2) version
One with Virtual box 6.1 version

I have first enlarged my vmdk by using VBoxmanage.exe from 10 GB to 100Gb and I have used with my Ubuntu Linux VM for developing. All right.
Then I have moved this vmdk on an external disk (1 Tera) in order to have much more space on my physical disk c:


Any days ago I have thought of create another Vm on second laptop with Virtual Box 6.1 version and use the same virtual disk after lighting my first VM on first laptop off.

So I have corrupted my virtual disk vmdk. In fact now when I use my first laptop and launch my VM I obtain this list of message:

....
...
...
...
...

...

fatal error token exceeds yylmax

  ",masdelmon
20315,6.1.20 Fails to start guest : memory can't be written,Windows,BSD,VirtualBox 6.1.20,2021-04-23T21:36:15Z,2021-04-23T21:36:15Z,As of 6.1.18 it succeeded.,MikhailRokhin
20319,Just installed v6.1.20's guest additions freezes Mac OS X El Capitan v10.11.6 guest VM & then host.,other,other,VirtualBox 6.1.20,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
15722,Number Input in Guest System on Wayland Host,Linux,Windows,VirtualBox 5.1.2,2021-04-24T05:35:14Z,2021-04-24T05:35:14Z,"I run VirtualBox 5.1.2-1 on Arch Linux with Gnome 3.20.2. If Gnome is started with Wayland, I cannot input any numbers in the Guest system.

This does not happen, if I use an X.Org session on the Host system.",Phylu
20283,Network issues on Guest-VM,Mac OS X,Linux,VirtualBox 6.1.18,2021-04-24T18:56:04Z,2021-04-24T18:56:04Z,"Hey,

I am using VirtualBox on macOS Big Sur and seem to have found a problem.
I am running a Linux VM with a NAT-Network or NAT adapter and whenever I run nmap on there I am unable to reach my gateway (host) anymore. 
It's either non-responsive or responding very slowly (700ms-3000ms).

[img]https://imgur.com/a/2HU4Lrk[/img]

Is there any fix for this?",Eagleo0
20226,Windows VBox dev. build 6.1.19 142917 host won't start VMs but 6.1.19 142777 does,Windows,Windows,VirtualBox 6.1.18,2021-04-26T11:55:39Z,2021-04-26T11:55:39Z,"Bug report:

Am running Windows 8.1 Pro x64 fully patched (build 9600.19941).
Symantec Endpoint Protection: Version: 14.0.3929.1200 (14.0.3929.1200.105 to be exact)

With developer build Virtual Box 6.1.19 142917, I receive the following (or similar) when trying to start any VM 
(XP 32 bit, but also same for a 64 bit Windows 10 guest and 32 bit Windows 7 guests)
The previous developer build: 6.1.19 142777 was fine.
The only change is the build of Virtual Box, and indeed reverting back from 142917 to 142777 fixes the problem.

Error messages:

Failed to open a session for the virtual machine XP.

The virtual machine 'XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\VBoxMachines\XP\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Note: The following bug report against 142917 also looks relevant:
https://forums.virtualbox.org/viewtopic.php?f=38&t=101896",MikeDiack
20322,Bug from Red Hat Bugtracker,Linux,other,VirtualBox 6.1.20,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-
20313,"CentOS7 poweroff BUG, Couldn't be written",Windows,Linux,VirtualBox 6.1.18,2021-04-28T02:15:43Z,2021-04-28T02:15:43Z,"* Windows:  Win10 family Chinese version 20H2 19042.928 Mem 16GB
* CentOS: CentOS Linux release 7.9.2009 (Core) 
* Kernel: 3.10.0-1160.el7.x86_64
* Configuration
  * CPU：1cores
  * Mem: 1GB
  * Network Cards: 1 NAT
* Reproduce:

  Actually, every centos7 VM has the same problem, and it seems to have nothing to do with the virtual machine configuration. This problem occurs regardless of poweroff, shutdown, init 0 or ACPI shutdown commands. In addition, win10 1909 also has this problem.
  I wanna know is that a BUG, thank you!

* Error Message


{{{
VirtualBoxVM.exe - Application Error: 
The instruction at 0x00007FFED15D9B2C referenced memory at 0x00007FFED15D9B2C. The memory could not be written. 
Click on OK to terminate the program.
}}}
",Justin-Young
20327,No instala máquina virtual de windows Server,other,other,VirtualBox 6.1.20,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
20326,Server 2019 guest hangs,other,other,VirtualBox 6.1.20,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
20328,"MacOSX 11.2.3 Big Sur host, Linux guest; always getting ""Kernel driver not installed (rc=-1908)"" error popups; no system preferences > security and privacy ""Allow"" popups to date",Mac OS X,Linux,VirtualBox 6.1.20,2021-04-29T15:55:07Z,2021-04-29T15:55:07Z,"On every attempted install, this old error keeps popping up: 

[[br]]

>'''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.'''

[[br]]

Another error message shows up in conjunction with it, which is: 

[[br]]

>'''The virtual machine 'Linux Test' has terminated unexpectedly during startup with exit code 1 (0x1).'''
>'''Result Code: NS_ERROR_FAILURE (0x80004005)'''
>'''Component: MachineWrap'''
>'''Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}'''

[[br]]

My setup is: 

[[br]]

'''Program Version: Virtual Box version 6.1.20
Operating System: macOS Big Sur 11.2.3 (20D91)
Hardware Model: Early 2015 13-inch Macbook Pro
Memory: 16GB 1867 MHz DDR3
Processor: 3.1 GHz Dual-Core Intel Core i7'''

[[br]]

This also happened on Big Sur 11.1, and persisted after upgrading. I also did an online Big Sur reinstallation (i.e. from Apple's servers) and it did not solve the issue. 

[[br]]

The only information I have been able to glean that may help solve this issue is that Intel-based Big Sur installations seem to be missing the ""IOUSBMassStorageClass"" kext, which may be deprecated. Seen at Apple's open source page: https://opensource.apple.com/

[[br]]

This may be relevant, because terminal would mention it when attempting to run VirtualBox with the .sh file. I have included relevant logs, and I hope this information helps!",SlugRightsNow
20329,Connect bluetooth headset causes freeze,Windows,Linux,VirtualBox 6.1.18,2021-04-29T18:06:10Z,2021-04-29T18:06:10Z,"Frequently, when I turn on or turn off my bluetooth headset, the Guest OS will freeze. It will no longer respond to any mouse clicks of keyboard presses.

Generally I am in full screen mode. I was recently in windowed mode when this happened and attempting to open the File menu was also unresponsive. Windows then marked the window as Not Responding.


Virtualbox Version 6.1.18 r142142 (Qt5.6.2)
Host: Windows 10 (10.0.18363 Build 18363)
Guest: Ubuntu 20.04


[This thread](https://forums.virtualbox.org/viewtopic.php?f=6&t=94233) contains other users reporting the same issue with slight different pairings of Virtualbox running on Windows10 host with a Linux Guest OS.",plannigan
19386,FileVault,Mac OS X,other,VirtualBox 6.1.4,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
20331,Error NS_ERROR_FAILURE (0x80004005),Mac OS X,Linux,VirtualBox 6.1.20,2021-04-30T10:45:50Z,2021-04-30T10:45:50Z,"Everytime I tried to open an ISO file error happened. 

OSX Big Sur 11.3 (20E232)

Nothing in log file. Just an error I attached here. ",r0mkan
20232,Cannot exec files on vboxsf on newer kernels,Mac OS X,Linux,VirtualBox 6.1.18,2021-04-30T13:45:08Z,2021-04-30T13:45:08Z,"Reference: https://www.spinics.net/lists/reiserfs-devel/msg06411.html
Patch was introduced on https://lkml.org/lkml/2020/8/17/174 

Trying to execute a shell script from a shared mount fails on newer kernels (i.e. debian testing 5.10) with the error:

""kernel read not supported for file /test-exec""

Older kernels (i.e. 4.19 from stable) work. 

This suggests vboxsf needs patches for the new APIs.

",jisakielkiel
20154,Segmentation fault when running 5.10.x kernel as guest,Linux,Linux,VirtualBox 6.1.18,2021-04-30T15:42:33Z,2021-04-30T15:42:33Z,"Running an up to date Ubuntu 20.04 as a guest upgraded to use the 5.10.9 Linux kernel using the instructions contained here as a guide.

Installed  VBoxGuestAdditions-6.1.18 which installed successfully.

Rebooted. Reboot fails  with segmentation fault.

",Alex Kempshall
20332,Intel i7 2600K CPU,other,other,VirtualBox 6.1.22,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
20333,keep restarting vm windows 10 on linux host,Linux,Windows,VirtualBox 6.1.22,2021-05-01T12:14:58Z,2021-05-01T12:14:58Z,"I report sudden and continuous reboots with windows 10 virtual machine on linux host.
with cpu core i5 and i7 11th generation my machine like those of many users suddenly reboots. ",fantic10
16844,DRIVER_POWER_STATE_FAILURE VirtualBox 5.1.22,Windows,other,VirtualBox 5.1.22,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
20336,Windows 10 guest - VirtualBox Graphics Adapter - Windows has stopped this device.,Windows,Windows,VirtualBox 6.1.22,2021-05-03T17:04:43Z,2021-05-03T17:04:43Z,"Hi,
I've been using VirtualBox since a long time.
I'm using VirtualBox 6.1.22.
Now when I've 3D Acceleration enabled in my Windows 10 VM, Device Manager in Windows 10 reports VirtualBox Graphics Adapter - Windows has stopped this device as it has reported problems.
But when 3D Acceleration is disabled it works fine but the display is glitchy.

My specs:
Host:Windows 10 Home Single Language
CPU:Intel Core i5 10210U 2.11 Ghz
Intel UHD Graphics 620
NVIDIA GeForce MX230 2GB GDDR5(Dedicated Graphics)",asrar.sunge198
20337,Natnetwork loose connectivity after a while,Linux,Linux,VirtualBox 6.1.22,2021-05-04T08:29:04Z,2021-05-04T08:29:04Z,"Hi,
I have created 5 VMs based on Debian 10, with Natnetwork configured (because i need to let the VMs talk to each others and access the Vpn on the host).

Each one has static IP, no specific tunning or special configuration. just Debian Vms and default natnetwork configured.

All Vms are working without any problems, i can access it with port forwarding. and after a while (one minute, 3 minutes...), the IP connectivity is suddenly cut, the ssh connections are stuck !

I must restart the natnetwork with VBoxManage ... Same result with paravirtualized network interface or Intel Pro desktop.
So, it s impossible to work in theses conditions.

it seems that problem exists for years or i missed something ?

Thanks to do something on that issue.
Francois




",Francois94130
14748,nat network hangs intermittantly,Linux,Windows,VirtualBox 5.0.8,2021-05-04T20:17:25Z,2021-05-04T20:17:25Z,"Host: Ubuntu 14.04 64Bit

Virtualbox 5.0.8

Guest: Windows Server 2012, Windows XP - defect present for both guests.

Both guests are headless, used only by RDP.

Sometimes (1-2 times per day) guest network adapter stops to recieve any packets from ""media"", can't ping default gw for this network interface.

The only things that fix issue is nat network restart:

{{{
VBoxManage natnetwork stop --netname nat-int-network-2
VBoxManage natnetwork start --netname nat-int-network-2
}}}

Of course, may be there are another ways... reboot particular guest or perform ""sudo  /etc/init.d/vboxdrv restart"" (requiring all VMs stop)... But the only way I found to fix issue (while not rebooting/stopping guest is restart nat network...
 
I have two nat networks (192.168.1.0/24 and 192.168.2.0/24). They hangs indpendently:

- First one, nat-int-network (192.168.1.0/24), connected to WinXP guest (single network adapter within guest) hangs rarely - 1-2 times per month. 

- Second one, nat-int-network-2 (192.168.2.0/24), connected to Windows Server 2012 Guest (one of two network adapters within guest, second one is openvpn tap0 interface attached to guest as Bridged Adapter) and hangs more often - 1-2 times per day... sometime 1 time per 2-3 days...

Windows Server guest is a loaded by 5-10 simultaneous RDP-sessions, but average load is quite moderate... 

I understand that info provied is not enough.
Please, let me know - what kind of details should I add to?",dtgeorge
20338,The transparent image is only half displayed,other,Windows,VirtualBox 6.1.22,2021-05-05T07:19:12Z,2021-05-05T07:19:12Z,"This happens when I use the aero theme. When I switch to the basic theme, everything is OK. Please check the picture, this is what happened in one of my input method settings window. The same problem occurs when you click the download button and the settings button in the Firefox browser. It occurs in 6.1.16 and 6.1.22. I'm not sure whether it's a problem with windows or with VirtualBox. If it's the former, I'm sorry to delay you.",SmartAsMe
20339,Unpinned toolbar minimized when navigating sub menues,Linux,Windows,VirtualBox 6.1.22,2021-05-05T08:05:42Z,2021-05-05T08:05:42Z,"If the toolbar isn't pinned it disappears few seconds after clicking on a sub menu. This is annoying when searching for an selection that you don't know exactly where it is located or if accidentally clicking the neighboring menu by mistake.

Reproduce:
1) Start a guest (any guest, doesn't matter what OS)
2) Disable pinning on VirtualBox toolbar
3) Click on any Menu, let's take [Help] as an example.
4) Try to highlight (i.e. NOT selecting/clicking) [Help] -> [About VirtualBox...] -> (back to top again) -> [Devices] -> [Audio]  and do this *without* clicking the mouse again.

Result:
Toolbar will disappear approximately one second after [Help] is clicked, making navigating between different top menus impossible without  having to raise the toolbar again (done by clicking somewhere outside the now ""floating"" Help-sub menu and then moving mouse back to toolbar.

Expected result:
Toolbar remains active until any sub menu selection is selection is activated/clicked",utforskaren
20340,Headless mode on Windows requires too high permissions because of COM security,Windows,all,VirtualBox 6.1.22,2021-05-05T16:36:07Z,2021-05-05T16:36:07Z,"I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

> VBoxManage startvm ""[...]"" --type headless

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason can be found in the event viewer of Windows:

> Durch die Berechtigungseinstellungen für ""Anwendungsspezifisch"" wird
> dem Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F}
> und der APPID
> {819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

> Durch die Berechtigungseinstellungen für ""Computerstandard"" wird dem
> Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {74AB5FFE-8726-4435-AA7E-876D705BCBA5}
> und der APPID
> {EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

Virtual Box installs COM servers which by default can only be started by the groups SYSTEM, ADMINISTRATOR or INTERACTIVE. My created user isn't any member of those groups when used by the task scheduler, but when logging in interactively and using the shell.

{{{
VirtualBox Application
{819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
}}}

{{{
VirtualBox System Service
{EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
VBoxSDS
}}}

The security settings to start the necessary COM servers can be changed to include my created user with the necessary permissions and afterwards VBoxManage starts successfully and the COM-related error entries in the event viewer are gone. 

* https://ibb.co/6ysd4FZ
* https://ibb.co/DDsNzKW
* https://ibb.co/MZhwx7n
* https://ibb.co/ctrR7cp

As you already have an installer bringing services, device drivers etc. into the system, you could as well adjust security for those COM servers. Some other software simply creates a group for their own purposes, assigning the necessary permissions and document somewhere that users like the one created by me simply need to be a member of that group. That approach is pretty common, e.g. VMware and OpenVPN create custom groups for special maintenance as well.

I'm considering this a defect instead of an enhancement, because using users with least possible privileges is a recommended security practice and because COM isn't used on non-Windows, that approach works on other platforms. After fixing or working around this problem, VBox will be easier to use with the same concepts and good practices across more OS.

Thanks!",Thorsten Schöning
20341,"HARDENING fails to verify DLLs on Windows for non-interactive, restricted user",Windows,all,VirtualBox 6.1.22,2021-05-06T07:26:09Z,2021-05-06T07:26:09Z,"== Background ==

I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

{{{
VBoxManage startvm ""[...]"" --type headless
}}}

== HARDENING prevents necessary functionality ==

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason is HARDENING, which simply refuses to load necessary and otherwise legitimate Windows-DLLs, resulting in errors like the following. Things heavily depend on the configured VM and the purpose of loading some DLLs, the following error is from a VM using bridged networking.

{{{
supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
NetworkAttachmentType_Bridged: Failed to get NetCfg, hrc=ERROR_TRUST_FAILURE 0x800706FE (0x800706fe)
AssertLogRel F:\tinderbox\win-6.1\src\VBox\Main\src-client\ConsoleImpl2.cpp(5376) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): !FAILED(hrc)
hrc=ERROR_TRUST_FAILURE 0x800706FE
Constructor failed with rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR pfnCFGMConstructor=00007ffc15bd1e60
VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(318) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400
Console: Machine state changed to 'PoweredOff'
Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005))
}}}

== HARDENING fails signature verification ==

While changing bridged networking to NAT makes the VM start, I simply have use cases which require a bridged network and one can't be sure anyway. The problem in all of those cases still is HARDENING not being able to verify some DLLs, which can be seen more detailed in the following logs:

{{{
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffc74d20000 'C:\windows\system32\rsaenh.dll'
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000808 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile -> -22900 (org 22900)
supHardenedWinVerifyImageByHandle: -> -22900 (\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll) WinVerifyTrust
Error (rc=0):
supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
Error (rc=0):
supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\System32\NetSetupShim.dll'
supR3HardenedDllNotificationCallback: Unload 00007ffc2aa90000 LB 0x000ef000 C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc77240000 LB 0x00052000 C:\windows\System32\SHLWAPI.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc15f60000 LB 0x003c0000 C:\Program Files\Oracle\VirtualBox\VBoxC.dll [flags=0x0]
Terminating the normal way: rcExit=0
supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1448 ms, the end);
supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1921 ms, the end);
}}}

The following is the relevant code:

{{{
/* Get the next match. */
HCATINFO hCatInfo = g_pfnCryptCATAdminEnumCatalogFromHash(hCatAdmin, abHash, cbHash, 0, &hCatInfoPrev);
if (!hCatInfo)
{
    if (!fFreshContext)
    {
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> %u; iCat=%#x)\n"", RtlGetLastWin32Error(), iCat));
        if (hCatInfoPrev != NULL)
            g_pfnCryptCATAdminReleaseCatalogContext(hCatAdmin, hCatInfoPrev, 0 /*dwFlags*/);
        g_pfnCryptCATAdminReleaseContext(hCatAdmin, 0 /*dwFlags*/);
        goto l_fresh_context;
    }
    ULONG ulErr = RtlGetLastWin32Error();
    fNoSignedCatalogFound = ulErr == ERROR_NOT_FOUND && fNoSignedCatalogFound != 0;
    if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (%u)\n"", ulErr));
    else if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed %u\n"", ulErr));
    break;
}
}}}

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/Support/win/SUPHardenedVerifyImage-win.cpp#L2703

== Comparing verification results ==

The following is how a successful verification of that same file looks like. Specially look at ""cbHash"" and ""wszDigest"", which seems to be the exact same values like for the first attempt in the former logs. So if this verification succeeds, the catalogs contain the necessary data and the state of the DLL is obviously OK.

{{{
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000930 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
}}}

The following lines are of additional interest because they seem to contain some error code of Windows:

{{{
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
}}}

Which might the following:

{{{
ERROR_SERVICE_NOT_ACTIVE
1062 (0x426)
The service has not been started.
}}}

https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1000-1299-

== dberr.txt ==

A corresponding error code is logged to the file ""C:\Windows\System32\catroot2\dberr.txt"" after adjusting its permissions to allow my executing restricted default user to write to it. For some reason this is not the default, but doesn't make any difference for signature checking itself. These lines repeat multiple times, most like for each attempt to check the signature for each DLL of interest.

{{{
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #352 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #590 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #2479 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #939 encountered error 0x00000426
}}}

== Educated guess: COM permissions problem again? ==

So here's what I think is going on: This signature verification relies on some COM-component again and default security settings of those only allow SYSTEM, ADMINISTRATORS and INTERACTIVE to activate those. I have documented that in the related ticket #20340 already. When using task scheduler with my restricted user it's no member of any of these groups, therefore necessary components are not activated and signature can't be checked. This changes instantly when using the same command line etc. with the same user with an interactive shell.

While that could be argued as a limitation of Windows default settings, the problem in my opinion in this case is that HARDENING is requiring that signature verification, not Windows, while without it things would simply work. So to make HARDENING succeed in this case, I would need to make my restricted user being a member of ADMINISTRATORS, which obviously doesn't make too much sense from a security perspective: Providing far more permissions than absolutely necessary to make an additional security(!) check succeed first. :-)

Like discussed in #20340, this might be worked around by creating an additional group and providing necessary permissions on the COM component of interest to that group. The problem is that I couldn't find the exact component yet... :-/

https://stackoverflow.com/questions/67331016/why-does-cryptcatadminenumcatalogfromhash-return-error-not-found-1062-for-n

https://docs.microsoft.com/en-us/answers/questions/378892/why-does-34cryptcatadminenumcatalogfromhash34-retu.html

Another workaround would be to make HARDENING optionally being disabled, it harms in this case, or at least make it more tolerant and ignore some of those errors under some circumstances. As said, the mentioned DLLs are all Windows default DLLs, unchanged, which otherwise easily pass signature verification.",Thorsten Schöning
20343,instruction 0x00007FFD15769B2C,Windows,other,VirtualBox 6.1.22,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
19104,Ubuntu18.04 NS_ERROR_FAILURE,Linux,other,VirtualBox 6.0.14,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
20347,The error message appear when the virual machine shut down,Windows,Windows,VirtualBox 6.1.22,2021-05-08T06:14:02Z,2021-05-08T06:14:02Z,"It always show error message ""The instruction at 0x00007FFE199F9B2C referenced memory. The memory could not be written."" I try to reinstall the application, but didn't work. I use portable usb to store most of vm and ISO files. I think it wouldn't a problem for the vm, but I am not sure what happened. I hope your teams can look at this problem, I would very appreciate if you could solve this problem I currently facing with. Thank you and have a great day",jetAngel
20352,[Guest - windows 7] Cannot detect Qualcomm MMC Storage USB device,Windows,other,VirtualBox 6.1.22,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
20353,Fallo al abrir una sesión para la máquina virtual Windows XP.,Windows,Windows,VirtualBox 5.1.26,2021-05-10T01:00:27Z,2021-05-10T01:00:27Z,"Fallo al abrir una sesión para la máquina virtual Windows XP.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Alejandro Salcido\Downloads\virtualbox\Windows XP\Logs\VBoxHardening.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

",VASG
20356,Mouse integration click focus gets lost when using (Ultra)vncviewer client inside Windows 10 guest,Windows,Windows,VirtualBox 6.1.22,2021-05-10T14:41:10Z,2021-05-10T14:41:10Z,"I often experience issues with the mouse integration focus getting partially lost inside my Windows 10 guest (running on my windows 10 host) , meaning: i can hove above windows and buttons and you see them respond to the hovering, but clicking the button or area does not get through.

I notice this usually when i have been or am using the Ultravnc viewer inside the the guest client. It seems to disorient mouse capturing features.

To resolve this, i have to click the mouseintegration button on the lower right and then disable the automatic integration, then manually click the Windows 10 guest and confirm catching the mouse. After confirmation, the system is then responding to mouse clicks (right and left).

The behavior turned up since updating to 6.1.22, i did not had any issues like this with my former version (6.1.18!)",lbsl
20280,Memory Leak in vboxdrv,Linux,Linux,VirtualBox 6.1.18,2021-05-11T12:22:45Z,2021-05-11T12:22:45Z,"I detected a small memory leak in the openSUSE version that I maintain. To see if the problem had been fixed, I installed test build revision 143492. It has the same problem.

The kmemleak report is as follows:


{{{

localhost:cat > /sys/kernel/debug/kmemleak
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 94.516s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b600 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b680 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
localhost:~ # 
}}}

To trigger this leak, load the GUI, start and stop a VM, and then close the GUI. Until the final step, the kmemleak scan is clean. Note, this is a real leak. If vboxdrv is unloaded, the backtrace info is lost. The first leaked block is reported as:

{{{
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 1095.172s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] 0xffffffffa0c9fb05
    [<00000000064e6217>] 0xffffffffa0c9d82a
    [<00000000523d21fa>] 0xffffffffa0c9edd7
    [<00000000df0eec39>] 0xffffffffa0ca1067
    [<000000008419dc13>] 0xffffffffa0c9e55d
    [<00000000ec3fe3f7>] 0xffffffffa0c8c1b2

}}}

",Larry Finger
20351,SNMP Issues & Mgmt,other,other,VirtualBox 6.1.22,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
20360,VB launches for two seconds then closes,other,other,VirtualBox 6.1.22,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
20359,VM Windows 7 terminated,Linux,Windows,VirtualBox 6.1.22,2021-05-12T12:58:41Z,2021-05-12T12:58:41Z,"My Windows 7 VM terminated on my Ubuntu 20.04 LTS host.

I attached the log file.",anno
20361,vboxnet0 not working on startup,Mac OS X,other,VirtualBox 6.1.22,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
20362,VirtualBox Error using Ubuntu,Mac OS X,other,VirtualBox 6.1.22,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
20363,building kernel modules on a multiarch host fails,Linux,other,VirtualBox 6.1.22,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
20365,Linux guest won't boot unless hard disk is set as the priority,Linux,Linux,VirtualBox 6.1.22,2021-05-14T10:33:56Z,2021-05-14T10:33:56Z,"After installing the latest CentOS 7.8
The OS refuses to boot unless the boot order for the VM is specifically changed so that the VM boots from the disk first.
If I set the boot order to something else (for example network for IPXE testing),the operating system instead shows an error ""fatal: int18: BOOT FAILURE"".
Most of what I found online talks about installing the disk in GPT vs MBR, but that shouldn't have much bearing since I know I installed the VM as MBR. None the less, I still tried to change the VM to UEFI since that is what the online community instructs.  However, no effect was detected besides the VM booting into the UEFI shell. However, if the boot order for the VM is changed, even though the other boot options are not being used and the option for disk is eventually reached, the boot option for the disk will eventually show the error.

",Rusty_Almighty
20367,VM win10 does not start normale.. Does start Headless - Platform Osx,Mac OS X,all,VirtualBox 6.1.22,2021-05-15T13:47:10Z,2021-05-15T13:47:10Z,"A strange thing is that when I open Virtualbox, that the 'Oracele Virtualbox Manager' is appearing on every separate Desktop of my MacBook Pro.

That was not the case before... ",EttD
19508,VM (not) terminated with exit code 0,Linux,all,VirtualBox 6.1.6,2021-05-16T08:54:04Z,2021-05-16T08:54:04Z,"Host: Ubuntu 18.04 kernel 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Guest: any, predominantly experienced the problem with Windows guests

The problem is not willingly reproducible, but occurs on average in 1 of 20 (estimated) VM startups.

Problem description:

The VM starts correctly without any problems. While it is up and running for a considerable but variable time (experienced between 1 minute and 3 hours), the VBox Manager pops up a child window for the VM: 'Creating process for virtual machine ""[machine name]"" (GUI/Qt) ... (1/2)' with progress bar stuck at 0%. See attachment.

The VM continues to be operable as if nothing happens.

If nothing is done about the popup window: The VM is killed at some point in time further on without any notice. VM status in VBox Manager is ""aborted"" then.

If the guest operating system is shutdown ordinarily, the VM is closed and a VirtualBox Error popup window is opened ""Failed to open a session for the virtual machine [machine name]."" with detail ""The virtual machine [machine name] has terminated unexpectedly during startup with exit code 0 (0x0)."" and ""Result Code: NS_ERROR_FAILURE (0x80004005)"" and ""Component: MachineWrap"" and ""Interface: Machine {[hex codes]}"". See attachment.

VM log shows no obscurities. See attachment.

I suspect that the error appeared with kernel 4.15.0-96 or maybe already with kernel 4.15.0-91.
The error was already present in VBox 6.1.4. I did not see it with 6.1.2 (I believe).",sunrider
19641,Assigning more vCPU (within the physical core limits) causes random freezes on guests,Linux,Linux,VirtualBox 6.1.8,2021-05-19T05:19:07Z,2021-05-19T05:19:07Z,"'''Host Info'''
-------------------
Host: Fedora 32 (64 bit)[[BR]]

CPU: Intel® Core™ i9-9880H CPU @ 2.30GHz × 8 Cores[[BR]]

GPU: Intel UHD-630[[BR]]

HyperThreading: Disabled[[BR]]

Physical Cores: 8[[BR]]

VirtualBox Version: 6.1.8[[BR]]

Display Protocol: X11[[BR]]



'''Guest Info'''
------------------------------
Guest: Debian 10 (Kernel 4.19.0-9-amd64) (Also reproducible in Kubuntu 20.04)[[BR]]

Display Adapter: VMSVGA[[BR]]

3D Acceleration: Enabled[[BR]]

VBox Guest Additions: Installed[[BR]]


----

When I assign 4 cores to the guest, on random starts the guest's animation and scrolling lags. When I checked the Session Information it showed Guest Load about ~0-1% and VMM Load about ~25%. The next restart of the guest doesn't have this behavior. Guest is smooth and doesn't cause pauses.[[BR]]


I tried changing few settings to find the root cause of the issue and surprisingly reducing the CPU count to 1 or 2 fixes the issue. The issue was not reproducible at all.
",LienCaspari
20370,Virtual machine running slow and lagging.,Mac OS X,Linux,VirtualBox 6.1.22,2021-05-19T05:23:25Z,2021-05-19T05:23:25Z,I am experiencing a lot of lag while running my system. Especially when I start the browser in the guest os. I cannot run any other program and my screen freezes. The refresh rate and the response speed are also very slow. And when I start the VM box I need to minimize it first or else the guest os won't load up. I hope you can look into this issue and get to me back with a proper fix for this issue. I also tried seeking help from the forum but those solutions don't seem to work for me. Thank you in advance. ,red66
20294,Virtual disk automatic resize/growth failing.,Linux,Linux,VirtualBox 6.1.18,2021-05-19T16:55:55Z,2021-05-19T16:55:55Z,"Hi,

When the vitual hdd is defined during VM creation, I selected a dynamically allocated VDI. As far as I can tell, the size selected will be the maximum size of the hdd on the host and that less space will be allocated initially and extended as needed during guest operation. Correct?

My situation is a VM with a dynamically allocated hdd of 384GB. Right now it's at 45GB or so but is trying to extend the size. The guest is reporting disk problems and out of space problems and has now changed one partition to read only. What I think is happening is that the guest has a code path which Virtual Box intercepts, does some magic to add space, restart the operation. This is apparently NOT happening. The path through Virtual Box may or may not be trying to handle this situation but then appears to let the error(s) continue through the guest OS (5.12.0-0.rc5.180.fc35.x86_64).

Here's what the host thinks of the partition where the VDI is located:

{{{
Filesystem                         1K-blocks        Used   Available  Really_Available Use% Mount_Point
/dev/sda8                         1735405656   485065980  1250569508        1250339676  28% /export/home
}}}

The guest thinks it's VDI is:

{{{
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2        1992552   164592   1706720   9% /
/dev/sda7       65478188 14001584  48104780  23% /usr
/dev/sda1        1992552   149816   1721496   9% /boot
/dev/sda8      184666464 19495796 155717356  12% /export/home
/dev/sda5       65478188   751092  61355272   2% /var
/dev/sda6       65478188   936844  61169520   2% /opt
}}}

Which is considerably less than 384GB.

Additionally, the guest is throwing numerous messages like these:

{{{
[   23.180382] 06:32:17.603879 main     VBoxService 6.1.18_Fedora r142142 (verbosity: 0) linux.amd64 (Mar  2 2021 00:00:00
) release log
               06:32:
[   23.184678] 06:32:17.610514 main     OS Product: Linux
[   23.189518] 06:32:17.614980 main     OS Release: 5.12.0-0.rc5.180.fc35.x86_64
[   23.192546] 06:32:17.617869 main     OS Version: #1 SMP Mon Mar 29 15:30:36 UTC 2021
[   23.197236] 06:32:17.620938 main     Executable: /usr/sbin/VBoxService
               06:32:17.620942 main     Process ID: 591
               06:32:17.620944 main     Pa
[   23.202542] 06:32:17.628117 main     6.1.18_Fedora r142142 started. Verbose level = 0
[   23.208141] 06:32:17.633605 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[   40.487920] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   40.488885] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
[ 7841.824091] systemd[1]: systemd v248-1.fc35 running in system mode. (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOM
P +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQU
ALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 7841.825374] systemd[1]: Detected virtualization oracle.
[ 7841.825631] systemd[1]: Detected architecture x86-64.
[ 7872.660143] ata1.00: exception Emask 0x0 SAct 0x1ffff800 SErr 0x0 action 0x6 frozen
[ 7872.661528] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.662445] ata1.00: cmd 61/00:58:c8:89:2b/0a:00:12:00:00/40 tag 11 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.664910] ata1.00: status: { DRDY }
[ 7872.665671] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.666963] ata1.00: cmd 61/00:60:c8:93:2b/0a:00:12:00:00/40 tag 12 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}


and:

{{{
[ 7872.721207] ata1.00: status: { DRDY }
[ 7872.721577] ata1.00: failed command: READ FPDMA QUEUED
[ 7872.722023] ata1.00: cmd 60/08:e0:10:7a:0d/00:00:17:00:00/40 tag 28 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.723230] ata1.00: status: { DRDY }
[ 7872.723607] ata1: hard resetting link
[ 7873.036871] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7873.038028] ata1.00: configured for UDMA/133
[ 7873.038418] ata1.00: device reported invalid CHS sector 0
[ 7873.038850] ata1.00: device reported invalid CHS sector 0
[ 7873.039295] ata1.00: device reported invalid CHS sector 0
[ 7873.039725] ata1.00: device reported invalid CHS sector 0
[ 7873.040250] ata1.00: device reported invalid CHS sector 0
[ 7873.040691] ata1.00: device reported invalid CHS sector 0
[ 7873.041133] ata1.00: device reported invalid CHS sector 0
[ 7873.041646] ata1.00: device reported invalid CHS sector 0
}}}


and:

{{{
[49175.522760] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621957, error -30)
[49175.526567] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621958, error -30)
[49175.530010] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621961, error -30)
}}}

Of course there are more of all of these messages available in a file. I'm not sure how I would attach a file to this mailing list though.

Can someone take a look at all this and render some assistance please?

Best regards,

George...



VirtualBox Graphical User Interface

Version 6.1.19 r143581 (Qt5.6.1)",George R. Goffe
20374,Default Start Mode Preference,all,all,VirtualBox 6.1.22,2021-05-20T16:57:35Z,2021-05-20T16:57:35Z,"When I start the virtual machine in VirtualBox Manager, I want the virtual machine to start with my preferred startup mode (normal|headless|detached).

I want to set the default startup mode (normal|headless|detached) as a preference.

Thank you.

",Lynda
20375,Clipboard and drag&drop doesn't work bidirectionally (VB 6.1.22/Guest additions 6.1.22_Host: Ubuntu 20.04 / Guest: Win 8.1),Linux,Windows,VirtualBox 6.1.22,2021-05-23T16:16:07Z,2021-05-23T16:16:07Z,"Clipboard and drag&drop doesn't work properly bidirectionally

VB 6.1.22
Guest additions installed 6.1.22 (tried to downgrade to 6.1.18 with same results)
Host: Ubuntu 20.04
Guest: Win 8.1

Done tests from file manager on both sides:

Drag&Drop from guest to host (file): OK
Drag&Drop from host to guest (file): nothing happens

Copy&Paste from guest to host (file): OK
Copy&Paste from host to guest (file): nothing happens

Copy&Paste from guest to host (text): OK
Copy&Paste from host to guest (text): OK


Done test with a program (Host: WPS Docs / Guest: Word 2013):

Drag&Drop from guest to host (image): nothing happens
Drag&Drop from host to guest (image): nothing happens

Copy&Paste from guest to host (image): OK
Copy&Paste from host to guest (image): OK

PrintScreen from guest to host: OK
PrintScreen from host to guest: nothing happens

Hope the issue is clear enough to understand.
",cimarron
20376,USB Moxa UPort1150l device cannot start Code 10,Windows,Windows,VirtualBox 6.1.22,2021-05-24T11:44:18Z,2021-05-24T11:44:18Z,"Hello!

'''Hardware and hosts:[[BR]]'''

Dell Precision 7520 Windows 10 company based 20H2 (year ago some older version)[[BR]]

Virtual Windows 7 - all updates[[BR]]


I have found that about a year ago my Uport was working fine with Win7. After a update VM and extensions it stopped working. Now I have tested also this with new fresh Win7 installation and same problem exist.

In device manager the device status is ""This device cannot start. (Code 10)"". If I try to use some other driver from Moxa like Uport 1150 then result is same.",Vahelduvool
20378,Virtualbox Extension makes Windows Startmenue unusable,Windows,Windows,VirtualBox 6.1.22,2021-05-25T09:46:30Z,2021-05-25T09:46:30Z,When I install the Guest Additions the Windows Start Menue stopps working correct,Temaktor
20364,VirtualBox guest freezes when chaning host audio interfaces,Windows,Linux,VirtualBox 6.1.20,2021-05-25T13:30:35Z,2021-05-25T13:30:35Z,"The VirtualBox Ubuntu guest may freeze / (GUI hangup) when the audio in a guest is in use and an audio interface changes on the Windows 10 host.

Tested with multiple Ubuntu guest versions 18.04 up to 21.04.

Users reported the same issue when connecting USB audio devices (like bluetooth).

See full detailed logs and 100% reproducible testcase in issue:
https://forums.virtualbox.org/viewtopic.php?f=6&t=94233&p=499715#p499715",Erwin
20380,Suggestions for development for a Mac Host,Mac OS X,other,VirtualBox 6.1.22,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
20354,VirtualBox crashing on Big Sur 11.3.1,Mac OS X,Windows,VirtualBox 6.1.22,2021-05-26T18:29:39Z,2021-05-26T18:29:39Z,"Greetings VirtualBox team.

I just recently applied the latest apple patch to my macbook pro.
The OS version I am running is Big Sur 11.3.1 and after that version was installed, I am unable to run my windows 10 VM.

The error I am getting is the following:

Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 



VirtualBox version: 6.1.22

Any pointers on how to fix this issue would be highly appreciated.
Best.",QuattroXL
20379,6.1.18 to 6.1.20 Intel pro/1000 changes,Windows,other,VirtualBox 6.1.20,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
19689,Microphone does not work when going from version VirtualBox 5 to 6,Linux,Windows,VirtualBox 6.1.10,2021-06-01T08:29:46Z,2021-06-01T08:29:46Z,"The microphone does not work on any of the guest systems.
I have ubuntu 20.04 host, VirtualBox 6.1.10 r138449 (Qt5.12.8). The microphone works in hosts, but it doesn't work on any of the guests: Windows 10 and ubuntu 20.04.

VirtualBox Audio Configuration: 
Host Controller: Pulseaudio
Controller: Audio Intel HD

When I used version 5 of virtualbox everything worked perfectly.",Abate Bus
20384,"VM not staring, was working perfectly two months ago.",other,other,VirtualBox 6.1.22,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
20385,VirtualBox crashes by accessing 0xFFFFFFFFFFFFFFFF when USB dongle is unplugged/plugged.,Windows,Linux,VirtualBox 6.1.22,2021-06-03T04:29:34Z,2021-06-03T04:29:34Z,"I am using virtualbox 6.1.22: 6.1.22 r144080 (Qt5.6.2) to be exact.
Host is Windows 10 Pro 64-bit., 20H2, OS build is 19042.985
Guest is Debian GNU/Linux, 5.10.0-4-amd64 

I have a USB Wi-Fi dongle NEC Aterm WL300NU-AG adaptor.
This works fine under Windows 10.

I tried to use this dongle from within linux to test my Wi-Fi devices at home against fragattacks (recently found Wi-Fi vulnerability).
So I removed the driver under Windows 10 for this USB. 
(It is plugged and no messing from Windoes 10 itself without the driver, I suppose.)
I intend to use the dongle via the native linux driver.

Under guest linux, I could somehow make the dongle recognized initially,
and eventually was able to assign IP address to it (manually, not by DHCP) and ping the interface address from other PCs via Wi-Fi. 
So experimentally it works, but the device went off-line unexpectedly.
The driver seems to have a known issue.
In order to reset the device, I tried unplugging and plugging it a few times. 
Then VBox crashed saying it accessed 0xFFFFFFFFFFFFFFFF address. 
(Actually I did this a lot initially, but at that time VBox did not crash.)

Alright, I saved a log. (The experiment took a couple of hours).

Now, I rebooted the guest linux by restarting VBox and see if I can continue testing the dongle. Nope.
The device was not visible from within guest linux using lsusb anymore(?!).
So I tried unplugging and unplugging only a couple of times when I get the same address violation and VBox crashed. This time I got the capture on the screen to show the address. 

I think there is a problem with USB handling.
I am attaching the first log (crash that occurred after a couple of hours testing. Actually, it was at the tail end of a very long session.)
and the second log along with the screen dump.

",ci-zephyurus
20388,VM aborted while saving state,Windows,Linux,VirtualBox 6.1.22,2021-06-05T10:43:51Z,2021-06-05T10:43:51Z,"I tried to save the state of the VM by selecting File → Close from the popup menu (invoked via a custom Host key shortcut) and, with the “Save state” radio button selected, pressing OK. At first, the VM seemed to save normally, but then the save process appeared to stop prematurely and the VirtualBox interface showed the VM state as “Aborted”.

This occurred after upgrading VirtualBox from 6.0.24 to 6.1.22. Before the incident, the VM had been running for several days and, if I recall correctly, was successfully saved and restored once, and also paused and resumed once.",mgrzegor
18594,Ubuntu 18.04 (guest) audio stops working (stuck) after Windows 10 (host) sleeps,Windows,Linux,VirtualBox 6.0.6,2021-06-05T11:04:24Z,2021-06-05T11:04:24Z,"'''Host:'''  Windows 10 Pro, 1809, 17763.437

'''Guest:''' Ubuntu 18.04

'''VirtualBox:''' 6.0.6

'''Sound card:''' either '''Intel HD''' or '''AC97'''.

All updates are installed. Guest additions are installed.

'''Problem:''' Ubuntu 18.04 (guest) sound works until Windows 10 (host) goes to sleep. For example, you're listening to YouTube music but after suspension the video and sound stucks forever.

'''Quick dirty workaround:''' Shutdown virtual machine, then launch again. ''Hot reboot doesn't work''!

Resetting of pulseaudio and alsa inside the guest ''doesn't work''!
{{{
sudo killall pulseaudio; sudo alsa force-reload;

Unloading ALSA sound driver modules: snd-hda-codec-idt snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer (failed: modules still loaded: snd-hda-codec-idt snd-hda-codec-generic snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer).
Loading ALSA sound driver modules: snd-hda-codec-idt snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer.

}}}

'''Any action inside the guest doesn't work.''' Only kill the guest and start again (not hot reboot!).

If audio has been playing during the getting sleep, then after system wakes up the 1 second of sound will be repeated infinitely from the guest (like a ""cla-cla-cla-cla-cla-cla...."").",James Fade
19716,Total freeze VM after resume PC from sleep with multi-display,Windows,Linux,VirtualBox 6.1.10,2021-06-05T22:35:10Z,2021-06-05T22:35:10Z,"I have notebook with additional display connected. After resume PC from sleep i have grayscaled VM (not resumed). After any manipulation (manual click to resume or power off) i have total freeze VM, any keys and menus do not work, I can stop it only from windows process manager. I see this bug only if I use additional display, and not always. Host - Windows 10 Pro. Guest - Ubuntu 20.04.

Last log messages:
{{{
19:20:59.444238 Pausing VM execution, reason 'host suspend'
19:20:59.445534 Changing the VM state from 'RUNNING' to 'SUSPENDING'
19:20:59.455506 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0781) created successfully
19:20:59.459381 AIOMgr: Async flushes not supported
19:20:59.460061 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0781) created successfully
19:21:00.435103 PDMR3Suspend: 988 580 745 ns run time
19:21:00.435115 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
19:21:00.435665 Console: Machine state changed to 'Paused'
19:21:01.289288 Audio: Device configuration of driver 'DSoundAudio' has changed
35:23:09.706882 Resuming VM execution, reason 'host resume'
35:23:09.706982 Changing the VM state from 'SUSPENDED' to 'RESUMING'
35:23:09.708188 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0723) created successfully
35:23:09.716841 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0723) created successfully
35:23:27.908281 GUI: UIMachineLogic: Host-screen count changed
35:23:28.567910 GUI: UIMachineLogic: Host-screen count changed
35:23:28.921678 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: 0x0 x 1920x1080
35:23:28.921702 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.971593 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 0x0 x 1920x1080
35:23:28.971614 GUI: UIMachineLogic: Host-screen available-area changed
35:23:28.972004 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: -1920x1072 x 1920x1080
35:23:28.972039 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.972572 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1080
35:23:28.972590 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.526775 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 3840x2130
35:23:33.526800 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.527365 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1050
35:23:33.527380 GUI: UIMachineLogic: Host-screen available-area changed
35:23:37.709638 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:41.938981 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:43.170192 GUI: Request for close-action to power VM off.
35:23:43.170209 GUI: Passing request to power VM off from machine-logic to UI session.
35:23:43.170453 GUI: Powering VM down on UI session power off request...
35:23:43.173091 Console: Machine state changed to 'Stopping'
35:23:43.174650 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
}}}

{{{
19:20:59.444238 - I sleep (or hibernate) PC.
35:23:09.706882 - Resume PC - VM is grayscaled, after any manipulation - total freeze.
}}}",PDZ
20389,VBoxSharedClipboardClass-17032: VirtualBoxVM.exe - Application Error,Windows,Linux,VirtualBox 6.1.22,2021-06-07T23:10:51Z,2021-06-07T23:10:51Z,"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

Copying into clipboard from host caused:

{{{
---------------------------
VBoxSharedClipboardClass-17032: VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFC9EBC2B32 referenced memory at 0x0000000000000000. The memory could not be written.

}}}


Only one guest running at the time, remained responsive but without shared clipboard functionality.  Clicking OK caused immediate close of the guest.  Logs attached.

Has been working solidly until recently.",gkcgareth
13500,Windows VirtualBox Process Priority support,Windows,all,VirtualBox 4.3.18,2021-06-08T23:57:02Z,2021-06-08T23:57:02Z,"BOINC runs CPU-instensive tasks (sometimes VirtualBox CPU-intensive tasks), typically at idle priority, but sometimes at below normal priority. The intent is to not interfere with the user's computing experience.

Before the hardened security that was added to VirtualBox for Windows (using VirtualBox 4.3.12 or prior), BOINC could easily manage/set/increase/decrease the process priorities as needed.

After the hardened security was added to VirtualBox for Windows (using VirtualBox 4.3.14+), the process priorities can no-longer be controlled. They run at Normal, with no way to change them (that I know of). This ends up degrading the user experience. I'm considering this a defect, since the hardened security changes broke something that was previously working great.

Please add some way to control the priorities of the VM processes that get instantiated -- Preferably available in the VirtualBox Manager UI, but for BOINC's purposes, VBoxManage command line parameters would work too I believe.

Thanks,
Jacob Klein",Jacob Klein
20391,"With Windows host,Bridged Adapter Oracle VirtualBox (6.1) doesn't work if the VM Opterating system is Ubuntu 16.04",Windows,Linux,VirtualBox 6.1.22,2021-06-09T22:57:39Z,2021-06-09T22:57:39Z,"Here is an outline of the problem:

Parameters:
•	I’m using Windows 7
•	I’m using Oracle VirtualBox 6.1
•	I’m running Ubuntu 16.04 on Oracle VirtualBox VM’s

Outline of the Problem:

•	Can’t connect to the internet if I select “Bridged Adapter” in 
        the Networking Options of an Oracle VirtualBox VM.
•	Can connect to the Internet via the NAT Adapter.
•	When I try to communicate between Oracle VirtualBox VM’s via 
        the Bridged Adapter, I get the error message “Host not Found.
",intelidrift
18914,VBoxSVGA 3D rendering problems,Linux,Windows,VirtualBox 6.0.12,2021-06-10T00:15:31Z,2021-06-10T00:15:31Z,"VBox 6.0.12[[BR]]

Host: {{{Ubuntu 16.04; 4.15.0-60-generic #67~16.04.1-Ubuntu}}}[[BR]]

Guest: Win10(64) Version 19.03 (OS Build 18362.329)[[BR]]

MS Outlook for Office 365 MSO (16.0.11929.20234) 64-bit[[BR]]


Guest: VBoxSVGA, 2D enabled, 3D enabled, Guest Additions 6.0.12

MS Outlook window is rendered with black/white/grey boxes. Window is responsive, e.g. can close the application by clicking at the top right corner, where the 'X' close widget should be.

Problem disappears when disabling 3D in VM settings.",sunrider
20394,Settings issue,Windows,Linux,VirtualBox 6.1.22,2021-06-11T04:38:12Z,2021-06-11T04:38:12Z,"I cant change the VM´s settings, and i cant run it because a AMD-V setting ",Xion18502
20395,Centos 7 i386 causes serious malfunctions when booted with ncpus>1,Windows,Linux,VirtualBox 6.1.22,2021-06-11T10:34:08Z,2021-06-11T10:34:08Z,"I had occasion to try testing something on CentOS 7 i386. So I fetched CentOS-7-i386-NetInstall-2009.iso, and tried booting it on my Win10 host running VB 6.1.22, and strange behavior ensued. So I tried a premade 7 2009 image, which did the same, and a premade 7 2003 image, which did either the same thing or aborted.

First, it flooded with BUG: Bad page state in process swapper. Then, after a bit, the strangest behavior ensued - it started pegging multiple cores on the host, attempting to do anything with the VM window or other VB windows became infeasible (I needed to use Task Manager to kill the VM ultimately, the times it didn't abort and crash on its own) and my Caps Lock light started oscillating furiously, which continues even if it ultimately gets into the graphical login screen.

Running with n=1 cores, it seems to work fine.

Since Debian buster i386 works fine on this host, it's not impossible for it to be a flaw in what CentOS 7 is doing, but if it works on real hardware, then not working in a VM still seems like a flaw in the VM?",rincebrain
20398,Error Guru Meditation,Windows,Windows,VirtualBox 6.1.22,2021-06-14T09:48:51Z,2021-06-14T09:48:51Z,Al intentar cargar el sistema operativo de una nueva máquina virtual me ha dado el mensaje Guru Meditation y no puedo instalarla,Alfonsodearagon
20406,Mouse integration missing,Windows,Windows,VirtualBox 6.1.22,2021-06-15T19:57:49Z,2021-06-15T19:57:49Z,"After update to 6.1.22, the mouse click sometimes not workin proprealy, so i need to disable mouse integration to continuie using VM, current i'm running w10 vm in w10 host",Lmendes.cwb
20392,TCP reset on 50% of http POST,Mac OS X,all,VirtualBox 6.1.22,2021-06-17T01:09:55Z,2021-06-17T01:09:55Z,"Since MacOS Big sur I get about 50% TCP reset's. This can be reproduced with curl:

{{{
$ curl  -d '{""request"": ""query""}' -H ""Content-Type: application/json"" -X POST http://local_network_host:21573/ >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14668    0 14648  100    20   133k    186 --:--:-- --:--:-- --:--:--  133k
$ curl  -d '{""request"": ""query""}' -H ""Content-Type: application/json"" -X POST http://routingtestb:21573/ >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14668    0 14648  100    20   133k    186 --:--:-- --:--:-- --:--:--  133k
curl: (56) Recv failure: Connection reset by peer
}}}


I'm not able to reproduce with a public host yet. I can provide a pcap but prefer not to make it public.

Tried:
- Only NAT network. Did not try bridge.
- Tried various adapter types.
- Multiple hosts have same issue.
- Different guests have the same issue. (Windows / Linux)

",Pieter1234
20423,Oracle VirtualBox SharedClipboard Use After Free Vulnerability,Linux,Linux,VirtualBox 6.1.22,2021-06-17T03:14:59Z,2021-06-17T03:14:59Z,"=  Oracle VirtualBox SharedClipboard Use After Free Vulnerability =



== Affected Software ==

Oracle VM VirtualBox 6.1.22



== Description of Vulnerability ==

This vulnerability allows guest VM to cause denial of service in the context of the host hypervisor. High privileged code on the target guest system is required to exploit this vulnerability. 



== Technical Details ==

VirtualBox provide a HostService named **""VBoxSharedClipboard""** to perform the operation of shared clipboard between Host and Guest. The guest sends the request through **HGCM (Host-Guest Communication Manager)**. The vulnerability is when guest quickly send `VMMDevReq_HGCMDisconnect` and `VMMDevReq_HGCMCall64` to the same service sequentially. That service will operate the `VMMDevReq_HGCMCall64` after the `VMMDevReq_HGCMDisconnect`. So `pvClient` the internal object used in service has been released when it perform disconnect function. But Later **HGCMCall** will use that freed object to operate guest requested function and cause use after free.

In code [1], it free the pCtx and later will be used in **HGCMCall**

`svcDisconnect` -> 
    `ShClSvcImplDisconnect`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
int ShClSvcImplDisconnect(PSHCLCLIENT pClient)
{
    LogFlowFuncEnter();

    PSHCLCONTEXT pCtx = pClient->State.pCtx;
    AssertPtr(pCtx);

    /* Drop the reference to the client, in case it is still there.  This
     * will cause any outstanding clipboard data requests from X11 to fail
     * immediately. */
    pCtx->fShuttingDown = true;

    int rc = ShClX11ThreadStop(&pCtx->X11);
    /** @todo handle this slightly more reasonably, or be really sure
     *        it won't go wrong. */
    AssertRC(rc);

    ShClX11Destroy(&pCtx->X11);
    RTCritSectDelete(&pCtx->CritSect);

    RTMemFree(pCtx); // code [1]

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}
}}}

When the guest send a `VBOX_SHCL_GUEST_FN_REPORT_FORMATS` request and guest's uMode is set to `VBOX_SHCL_MODE_BIDIRECTIONAL` or `VBOX_SHCL_MODE_GUEST_TO_HOST`
which is `not` default setting in code [2], it will perform the following function. In function `XtAppAddTimeOut`, it will get crashed.


{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
static int shClSvcClientReportFormats(PSHCLCLIENT pClient, uint32_t cParms, VBOXHGCMSVCPARM paParms[])
{
    /*
     * Check if the service mode allows this operation and whether the guest is
     * supposed to be reading from the host.
     */
    uint32_t uMode = ShClSvcGetMode();
    if (   uMode == VBOX_SHCL_MODE_BIDIRECTIONAL //code [2]
        || uMode == VBOX_SHCL_MODE_GUEST_TO_HOST)
    { /* likely */ } 
    else
        return VERR_ACCESS_DENIED;
}}}
}}}

`svcCall` -> 
    `shClSvcClientReportFormats` -> 
        `ShClSvcImplFormatAnnounce` ->
            `ShClX11ReportFormatsToX11` ->
                `clipThreadScheduleCall` ->
                    `XtAppAddTimeOut` ->
                        `clipThreadScheduleCall`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C

static int clipThreadScheduleCall(PSHCLX11CTX pCtx,
                                  void (*proc)(void *, void *),
                                  void *client_data)
{
    LogFlowFunc((""proc=%p, client_data=%p\n"", proc, client_data));

#ifndef TESTCASE
    XtAppAddTimeOut(pCtx->pAppContext, 0, (XtTimerCallbackProc)proc,
                    (XtPointer)client_data);
    ssize_t cbWritten = write(pCtx->wakeupPipeWrite, WAKE_UP_STRING, WAKE_UP_STRING_LEN);
    Assert(cbWritten == WAKE_UP_STRING_LEN);

}}}
}}}


== The POC ==

The following are step by step guide for replicating the bug:
1. Upload the file `poc.c` and `internal.h` into the guest
2. Compile the poc by `gcc poc.c -o poc`
3. Run `poc` as root



== Requirements ==

* The Host OS must be Linux
* Attacker must be able to run **high-privileged** code on the guest
* The setting of Shared Clipboard need to be `Guest to Host` or `Bidirectional`",info_starlabs
19210,windows 10 guest crashes when exploring host shared folder,Linux,Windows,VirtualBox 6.0.10,2021-06-17T13:24:14Z,2021-06-17T13:24:14Z,I have shared a folder from my linux host and boot a windows 10 pro (64-bit originally installed from M$ download site) guest vm to use windows explorer to view the files in the share which appears as Z: drive. I choose to change the sort column to view by modified date and I can no longer get a response from the win 10 guest. The next moment I see the vm rebooting. I can reproduce this behaviour each time. Linux 64 bit vbox 6.0.10 r132072 (Qt5.9.5) I have attached the logfile,captain cranium
20426,Pestaña de Aceptar No Activada,other,other,VirtualBox 6.1.22,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
20419,NAT Port Forwarding CONN RESET ISSUES,Windows,Windows,VirtualBox 6.1.22,2021-06-19T04:56:49Z,2021-06-19T04:56:49Z,"Trying to port forward port 10000-10002 between the 
windows 10 pro host OS
windows 10 enterprise guest OS

on those ports the guest contains the microsoft azure storage emulator endpoints.

I am trying to make REST API call to those endpoints from the host OS will no sucess.

So far, I have turned off the windows defender firewall in the Guest OS  and allowed for the TCP,UDP inbound outbound connections on the HOST OS. I also upgraded my VM FROM 6.1.18-142142 TO 6.1.22-144080.This happend for browser, web app API, python and C#. We know this is the case becuase the API call to MySQL on guest 3306 works sucesfully and on turning off the guest OS, the failed call indicated the MySQL server was only on the guest

The results were from a HTTP Requests that hangs to a requests that respond ""CONNECTION RESET"", this happend on both versions of virtual box
",windmillcode
20400,Virtual Machine crashes when dragging link,Windows,Linux,VirtualBox 6.1.22,2021-06-19T12:39:25Z,2021-06-19T12:39:25Z,"Hello, I was using a virtual machine when i accidentally dragged a link inside the virtual machine. The virtual machine got aborted by virtualbox. it also gave a memory read error. I think the reason why it gave that error is because virtualbox is not checking if what the user drags inside of the virtual machine is a file or directory so it tries to read it then because it is not a file it gives a read error. So i would suggest you guys let virtualbox check if what the user drags inside the virtual machine is a file or directory.
So i would like to report this issue to help improve virtualbox.
If i could contribute through code it would a dream.",MemoryJack
10771,VirtualBox Extension Pack installation failed exit code 128 E_FAIL (0x80004005),Windows,other,VirtualBox 4.1.18,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
19622,VINF_EM_TRIPLE_FAULT on Server 2019 initial boot and install,Windows,Windows,VirtualBox 6.1.8,2021-06-19T20:03:18Z,2021-06-19T20:03:18Z,"VT-v enabled in host bios, attempted with guest efi enabled as well as disabled. Host Hyper-V platform disabled. After parsing the logs with an untrained eye, it looks as if it might be an issue with the cpu. Attempted with 1, 4 and 8 threads allocated, and 4gb and 8gb memory allocated. ",moumoku
20427,can't start the virtual machine,Windows,OSX Server,VirtualBox 6.1.22,2021-06-21T16:40:00Z,2021-06-21T16:40:00Z,"when i start virtual machine i have got this error

{{{
Failed to open a session for the virtual machine Mac.

Could not launch the VM process for the machine 'Mac' (VERR_INVALID_UTF16_ENCODING).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

}}}

how can i fix it?

",gihan
20383,Pass-Through Microphone Audio Broken Virtualbox Ver: 6.1.22-144080~Ubuntu~eoan,Linux,Windows,VirtualBox 6.1.22,2021-06-22T09:02:54Z,2021-06-22T09:02:54Z,"Problem Statement:

Unable to pass microphone audio from Windows guest to Linux host.

Verified with both Windows 7x64 & Windows 10x64 using built in recording application

(NOTE: Though not supported, it appears that this is now happening with my Android OS Guest. Microphone audio pass-through was working prior to latest Virtualbox updates)

pavucontrol used in Linux host to control and verify existence of audio in/out



Virtualbox initial Audio settings:

Enabled Audio

Host Audio Driver = Pulse Audio

Audio Controller = Intel HD Audio

Extended Features: Enabled both Audio Input & Output



Additional steps taken:

Verified user permissions attached to vboxuser. Assumed that the newer Kernel and Inten Chipset combination not yet compatible with Virtualbox. Obtained 6305_Vista_PG537 audio driver and installed in both Windows guests, then changed Audio Controller to ICH AC97. I'm still able to pass through Speaker Audio, but Microphone Audio remains elusive in both Windows versions. In addition, did try the Sound Blaster Audio Controller, but as expected, lost all audio without a matching Windows drivers.
Reloaded new Windows guest to re-verify installation, result log attached

Host System:

OS: Ubuntu 20.04 x86_64

Kernel: 5.11.0-7614-generic

Desktop Environment: KDE

CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz

RAM: -14936 MB / 23894 MB

Disk: 157G / 912G

Virtualbox Ver: 6.1.22-144080~Ubuntu~eoan

Virtualbox-ext-pack Ver: 6.1.22



Guest System:

OS: Win10_20H2_v2_English_x64.iso, No Service Pack

Virtualbox VBoxGuestAdditions.iso

Base Memory: 8192

Enable I/O APIC

Use Default and Nested paging for Hardware Virtualization: Enabled Nested Paging

Processors: 2

Extended Features: PAE/NX Enabled

Paravirtualization Interface: Default

(VT-xAMD-V,Nested Paging, PAE/NX, Hyper-V Paravirtualization)

Video Memory: 256Mb

Graphics Controller: VBoxSVGA

Acceleration: Enabled 3D Acceleration",MSterba
20428,Alias,Mac OS X,Windows,VirtualBox 6.1.22,2021-06-24T16:07:46Z,2021-06-24T16:07:46Z,"I just updated my mac to 10.15.7 and now I can't create a desktop alias for my vm box like i could before the update. If i go thru the steps to create an alias, it puts an icon on the desktop but it is invalid. If I go directly to where the vm files are stored and I click on the box name, it asks what application i'd like to use to open the file. I am using vm 6.1.22. How can I get my alias back on my desktop???",Peter Decesare
20429,System crash on Windows 10 host when using vbox network adapter together with Windows 10 networking bridging feature,Windows,all,VirtualBox 6.1.18,2021-06-25T04:36:09Z,2021-06-25T04:36:09Z,"Steps to reproduce the issue:

1) Install vbox on a Windows 10 device
2) Make sure to also enable the vbox network adapter
3) Set physical network adapter within the Windows 10 network settings to bridge mode (Control Panel\Network and Internet\Network Connections -> right click network connection -> bridge connection)
4) Leave device running as normal. In my case, the crashes seemed to happen fairly consistently after roughly 14 hours of system uptime, give or take a few hours.

Unfortunately my system settings were set to full crash dumps and not minidumps, so the full dump is likely too large to upload here. However, I will paste the information the Windows debugger was able to extract from my crash dump here:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8027f4580c3, The address that the exception occurred at
Arg3: fffffe8c1f2a2ab8, Exception Record Address
Arg4: ffffa400c67f5920, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-INRFD0B

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027f4580c3

BUGCHECK_P3: fffffe8c1f2a2ab8

BUGCHECK_P4: ffffa400c67f5920

EXCEPTION_RECORD:  fffffe8c1f2a2ab8 -- (.exr 0xfffffe8c1f2a2ab8)
ExceptionAddress: fffff8027f4580c3 (bridge+0x00000000000080c3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffa400c67f5920 -- (.cxr 0xffffa400c67f5920)
rax=0000000000000000 rbx=0000000000000000 rcx=b2a29e05584ac880
rdx=0000000000000000 rsi=ffffb8880f8ee2c0 rdi=ffffb888098a48e0
rip=fffff8027f4580c3 rsp=fffffe8c1f2a2cf0 rbp=fffffe8c1f2a2e00
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000002
r11=fffffe8c1f2a2b90 r12=0000000000000000 r13=0000000000000000
r14=ffffb8880f8ee4f0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
bridge+0x80c3:
fffff802`7f4580c3 488b4918        mov     rcx,qword ptr [rcx+18h] ds:002b:b2a29e05`584ac898=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS:  ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

BAD_STACK_POINTER:  ffffa400c67f50e8

STACK_TEXT:  
fffffe8c`1f2a2cf0 fffff802`7f458786 : 00000094`00000000 00000000`00000003 fffffe8c`1f2a2e80 00000000`00000003 : bridge+0x80c3
fffffe8c`1f2a2d80 fffff802`674f53b5 : ffffb888`08528040 ffffb888`08528040 fffff802`7f458550 00000000`00000003 : bridge+0x8786
fffffe8c`1f2a3c10 fffff802`675fe278 : ffffa400`c67b3180 ffffb888`08528040 fffff802`674f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe8c`1f2a3c60 00000000`00000000 : fffffe8c`1f2a4000 fffffe8c`1f29e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bridge+80c3

MODULE_NAME: bridge

IMAGE_NAME:  bridge.sys

STACK_COMMAND:  .cxr 0xffffa400c67f5920 ; kb

BUCKET_ID_FUNC_OFFSET:  80c3

FAILURE_BUCKET_ID:  AV_STACKPTR_ERROR_bridge!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}

Followup:     MachineOwner
---------
",Andazeus
20430,VirtualBox does not uninstall correctly under Fedora 34 (dnf/PackageKit),other,other,VirtualBox 6.1.22,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
20273,Troubles with audio in VBox 6.1.19-143492,Windows,Windows,VirtualBox 6.1.18,2021-06-26T11:36:59Z,2021-06-26T11:36:59Z,"After testing the newly appeared version I immediately found a bug. If one stops audio playback, the last half second will still play over and over again, endlessly. This reminds me about an old good tickets with host audio output device change during the playback, like #17225 or [https://www.virtualbox.org/ticket/18594#comment:31 #18594#comment:31]. And some problems after audio backend rewrite back in 5.2. Those issues first appear in the new version and couldn't be found in 6.1.19-143292.

I put my logs and audio dump here. Both my host and my guest are Windows 10 20H2 with patches from March.",boxer01
14461,Raw disk VM gives ahci-0-0 BLKCACHE_IIOERR if block cache turned off on VirtualBox 5.0.1 and later => fixed in SVN/5.0.x,Windows,all,VirtualBox 5.0.2,2021-06-27T12:09:02Z,2021-06-27T12:09:02Z,"VirtualBox builds 5.0.2-102096 and 5.0.1-102010 fail to run correctly a full-raw-disk-based virtual machine that 5.0.0-101573 loads correctly. The failure occurs when the ""Use Host I/O Cache"" option (StorageController: useHostIOCache) is off for the controller of the raw VMDK.

This is the case even though VirtualBox is being run as an administrator, which I've found required for it to work with raw disks at all. Maybe something changed about what process accessed the drive?

The machine doesn't die straight away, but immediately after the initrd system loads up - the ""Root: clean"" line of fsck is printed (there are many things that happen just after that, so I don't want to imply it's part of fsck) - it freezes and a message is printed:

----

An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_ACCESS_DENIED). 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

----

The log also mentions ""Invalid machine state Paused when checking if the guest entered the ACPI mode"".

----
ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
00:00:10.967017 Console: Machine state changed to 'Stopping'
----
Host is Windows Vista 32-bit, guest is Debian 8.x 64-bit (though I figure it probably doesn't matter so I left the type as 'all'). The controller is the LSI logic, listed as ""AHCI"" in the GUI.

Attached are logs from when the files work, and when they don't, and the vmdk and vbox in question.",Laurence 'GreenReaper' Parry
20432,Cannot write to raw disk under Windows 10 21H1 guest in VBox 6.1.22,Windows,Linux,VirtualBox 6.1.22,2021-06-27T14:06:44Z,2021-06-27T14:06:44Z,"Severe bug, results in complete loss of all data written.

Quick description: I have some mechanical Western Digital Purple SATA drives hooked up via a Perc H310 SAS HBA. (SAS can use SATA drives). Windows 10 host, Ubuntu guest. Some of them can be written, but one which is larger and has NTFS on it can't. The ones that can be written to use ext4 and btrfs partitions. This probably isn't relevant, but who knows.

I had been using VBox 6.1.15 on a Windows 10 host (updated to latest non-insider version which is 21H1, build 19043.1081) with a Ubuntu 20.04 guest, with guest additions installed. Recently, I tried using it with a 14 TB WDC WD140PURZ-850A82 (Western Digital Purple 14TB mechanical SATA drive) connected via a Perc H310 SAS HBA. It is completely new and I created a single partition on it spanning the whole disk. I formatted it to NTFS using Windows 10 and put it offline, then created a VMDK using 

{{{
PS C:\WINDOWS\system32> & 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' internalcommands createrawvmdk -filename C:\VirtualBox\SAS-PhysicalDrive5-14tb.vmdk -rawdisk \\.\PhysicalDrive5
}}}

and then set it to write-through under the VBox gui. Finally I hooked it up to a SATA AHCI controller with 16 ports. The ""Use Host I/O Cache"" box was originally empty (unchecked), and I would get this error:

{{{
The I/O cache encountered an error while updating data in medium ""ahci-0-4"" (rc=VERR_WRITE_PROTECT). 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
}}}

If I DO check the ""Use Host I/O Cache"" box, then the data seems to get written and no error is produced - but when I unmount and remount the partition, it's gone.

What's weird is that there are other drives, also from the same drive family (WD Purple) and on the same SAS controller, which don't have the same issue. But they're linux formatted (either ext4 or btrfs) and also smaller (less than 10 TB).

If I turn on ""Use Host I/O Cache"", I am able to write to the disk. However, 3 issues remain still:

1. performance is very, very poor. On the order of 20 MB/sec. These drives are capable of 150 MB/sec when used under the Windows 10 host on the same controller.

2. if I type sync in the guest, it takes > 5 minutes, and meanwhile hangs up all disk IO

3. The data isn't ACTUALLY written to the disk.


Things I tried include:
- formatting the disk again. Didn't help
- I tried whether writing to the disk works when it's hooked up to the host (and not offlined). It works - files written to disk remain after offlining and again onlining the disk (which essentially unmounts and again mounts the disk on Windows 10).
- I updated to VBox 6.1.22 with latest guest additions, no improvement
- In the VM, I created a new LsiLogic SAS controller, and put the drives under that, no improvement

Finally, I am always running VBox GUI as admin, which is required in order for raw disk access to work in the first place, for all drives, even the ones where writing to disk does work.

Also, I've noticed that when I format the disk to a single NTFS partition under Windows 10, it actually creates two partitions: one tiny ~15MB one that's a ""Microsoft reserved partition"" (/dev/sde1 under Linux for me), and one that spans the rest of the disk (/dev/sde2) (which is where the data lives). Under the Windows 10 Disk Management panel, only one partition is shown. When I mount /dev/sde2, I can see the System Volume Information directory and some other files I put on that drive when it was mounted directly on the host, so I know it's the right partition.

P.S. I have previously re-opened #14461 thinking that was the same bug, but it's not - in #14461 you could work around to write data to the disk, in my situation the same workaround results in data being written to a black hole. Could someone please close that ticket?",cheater
20433,Virtualbox freeze,Linux,Windows,VirtualBox 6.1.22,2021-06-28T09:08:44Z,2021-06-28T09:08:44Z,"During working with VirtualBox and Windows 7, the guest freeze. Only by killing the process can solve the problem.

I attached the log.",anno
20434,usbfilter ignore --product flag,all,all,VirtualBox 6.1.22,2021-06-28T13:48:32Z,2021-06-28T13:48:32Z,"Hi!

I noticed that when I create filter using `usbfilter` command the `--product` flag is ignored.

For example, this command:

{{{#!sh
VBoxManage.exe usbfilter add 0 --target ""otus-astra-docker_default_1624884966310_75575"" --name ""Aktiv Rutoken ECP [0100]"" --product ""Rutoken ECP"" --revision ""0100"" --productid ""0030"" --vendorid ""0a89"" --manufacturer ""Aktiv""
}}}

creates this filter:
{{{#!sh
Index:                       0
Active:                      yes
Name:                        Any Rutoken ECP
VendorId:                    0a89
ProductId:                   0030
Revision:                    0100
Manufacturer:                Aktiv
Product:
Remote:
Serial Number:
}}}

I thik that the cause of this because you are forgot to set product field here:
https://github.com/mirror/vbox/blob/b9657cd5351cf17432b664009cc25bb480dc64c1/src/VBox/Frontends/VBoxManage/VBoxManageUSB.cpp#L404-L516",lo1ol
20436,my virtual box has a lot of bugs,Mac OS X,Windows,VirtualBox 6.1.22,2021-06-29T22:53:59Z,2021-06-29T22:53:59Z,the first bug is somany errors saying the hardrive is not detected but my hard drive is connacted to my mac second bug is the virtual drive is unstable but when i restart my mac the virtual drive is normal again ,kenzie
20443,"In macOS Catalina, a virtual machine crashes when it loses focus.",Mac OS X,Windows,VirtualBox 6.1.22,2021-07-01T12:18:05Z,2021-07-01T12:18:05Z,"I am using macOS Catalina 10.15.7 and running a virtual Windows XP on it. If you switch to another application or to the main VirtualBox window, the virtual machine crashes, but not every time, but with some probability. This opens a form for writing a report about the problem. The main VirtualBox window remains open and indicates that the status of the virtual machine: ""Aborted"". This problem has been around for a very long time. Probably more than a year. And since it is not going anywhere , I decided to report it.",dik
20441,Kernel module compilation error - VirtualBox 6.1.22 kernel 5.12.13,Linux,other,VirtualBox 6.1.22,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
20445,debian packages use version number in package name,other,other,VirtualBox 6.1.22,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
20442,XHCI has wrong PCI config space and runtime register settings,Windows,other,VirtualBox 6.1.22,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
20447,NVMe fails in Windows 10/11 guest,Windows,Windows,VirtualBox 6.1.22,2021-07-05T21:20:34Z,2021-07-05T21:20:34Z,It's impossible to start from bootable DVD-iso connected to NVMe and Windows 10/11 setup can't detect hdd attached to NVMe to install it to.,MikhailRokhin
17228,5.2.0 breaks NVMe support on Win10 1703 or later [regression],Windows,Windows,VirtualBox 5.2.0,2021-07-05T21:23:28Z,2021-07-05T21:23:28Z,"NVMe drive stopped working in a Win10 1703 VM after upgrading VB from 5.1.18 to 5.2.0.

In Device Manager, stornvme.sys is shown with yellow exclamation and (the German version of) this error message:
''This device cannot start. (Code 10) An invalid parameter was passed to a service or function.''

With an older 1607 snapshot of same VM, NVMe worked again.
After copying stornvme.sys from 1607 to 1703, NVMe worked again.
Same with a fresh install of 1709 (upgrade install crashed VB 5.2.0): NVMe failed and worked again after downgrading the driver.

Test results after downgrading VB to latest 5.1:

||= stornvme.sys       =||= 5.1.18/30 =||= 5.2.0 =||
|| 10.0.14393.0 (1607)  || OK          || OK      ||
|| 10.0.15063.0 (1703)  || OK          || Error   ||
|| 10.0.16299.15 (1709) || OK          || Error   ||

Possibly related or duplicate: #16078.
",chrfranke
20022,VM is causing Guest OS applications ( Slack/Intelli J ) hung,Windows,Linux,VirtualBox 6.1.16,2021-07-06T07:20:41Z,2021-07-06T07:20:41Z,"I have windows machine with 32 Gigs RAM and core i7 with 8th Gen. I have installed Ubuntu inside my Oracle VM with 2 cores(Out of 8 Cores) and 8 Gigs RAM (Out of 32 Gigs RAM).

Guest OS application slack or IntelliJ works fine without any issues until I start the Ubuntu using Oracle VM 6.1

As soon I start my Ubuntu on my VM, slack and IntelliJ freezes for every 10 minutes and I need to wait for 2 to 3 minutes to respond and do my work, it became a routine for every 15 minutes.

Unfortunately I do not have any logs because I do not see any network/cpu/disk usage spike, when these applications get hung. ",Sandeep Reddy
20448,Virtualbox on Linux host kills keyboard when running Windows 10 virtual machine,Linux,Windows,VirtualBox 6.1.22,2021-07-06T10:25:29Z,2021-07-06T10:25:29Z,"Hi all,

I have a pretty boring problem with virtualbox installed on Kali host and windows 10 as guest. When I use windows 10, after an indefinite time (sometimes immediately, sometimes after a few minutes of use), the touchpad or mouse stops working in both the host system and the guest system. More specifically, the keyboard works correctly, while the click of the touchpad or mouse does not work. The only way to fix this is to shut down the Windows virtual machine.

Does someone have the same issue and found a solution?",fourteenminusone
15827,Error message when starting VMs: Error In supR3HardenedWinReSpawn,Windows,Linux,VirtualBox 5.1.4,2021-07-06T13:05:47Z,2021-07-06T13:05:47Z,"Almost everyday when I start my machine and run Vbox and try to start a vm, a msgbox appears with the following error:


{{{
VirtualBox - Error In supR3HardenedWinReSpawn
(rc=-5640)
Please try reinstalling VirtualBox.
where supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.
}}}

When I click ""ok"", another msgbox appears:

{{{
Failed to open a session for the virtual machine Ubuntu 16.04.

The virtual machine 'Ubuntu 16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jbassi\VirtualBox VMs\Ubuntu 16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

This has been happening for month, with current version, last version, tests versions, etc.
The reason I haven't reported this bug until now is because if I try again a few times (two or three) the VM starts up correctly. So I cannot reproduce everytime. In order to reproduce I need to restart the machine. The first time I try after a reboot almost always fails.

Version: Version 5.1.4 r110228 (Qt5.5.1)
Host: Windows 8.1 Enterprise
CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
",asdfafds
20449,Ubuntu Linux host hissing audio after starting ubuntu server guest.,Linux,Linux,VirtualBox 6.1.22,2021-07-07T00:07:42Z,2021-07-07T00:07:42Z,"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]",Carlos Henrique
20450,Ubuntu Linux host hissing audio after starting ubuntu server guest.,Linux,Linux,VirtualBox 6.1.22,2021-07-07T00:08:14Z,2021-07-07T00:08:14Z,"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]",Carlos Henrique
19133,VM lockup when guest opens a named pipe in a shared folder,all,all,VirtualBox 6.0.14,2021-07-07T11:16:29Z,2021-07-07T11:16:29Z,"I discovered this bug because I was `rsync`ing a shared folder containing a named pipe, and this hung my machine.

Repro steps:
 - Set up a Linux guest on a Mac host. I have Ubuntu 18.04 running on VBox 6.0.14 (latest stable as of now).
 - Set up a shared folder 
 - On the host, `mkfifo TEST_PIPE` in the folder
 - On the guest, `cat TEST_PIPE`

At this point, the guest is (partially) locked up. Specifically:
 - Ctrl-C nor SIGKILL will work for `cat` — it is hung in D state, unkillable
 - Any process touching the shared folder hangs likewise
 - `dmesg` will show the following stack for the hung `cat` https://pastebin.com/WjKQaZys [1]
 - The guest cannot be cleanly rebooted because shutdown requires tearing down the guest additions module, which is blocked on talking to the VM.
 - Powering off the VM (not from the guest, but from the UI!) will hang.

So this is not a hang in guest additions, but in the VM code itself.

My guess is that the thread handling shared folders is locked up trying to read from the named pipe.

What confirms this is that the hang is resolved the moment that I do `echo > TEST_PIPE` on the host.

The reason this is **not** expected behavior is that the guest sees the named pipe as a regular file:

$ ls -l TEST_PIPE 
-rwxrwx--- 1 root vboxsf 0 Dec  6 16:21 TEST_PIPE

Two fixes seem possible:
 - Make named pipes act as true named pipes to the host. If you google ""vboxsf named pipe"", this is actually a feature that was previously requested.
 - Make the `open` syscall fail in this context. This is worse than working pipes, but better than a lockup. At the moment, data does not actually travel down the named pipe, if the host does `echo foo > TEST_PIPE` and the guest does `cat TEST_PIPE`, the guest simply says `cat: TEST_PIPE: Protocol error`.

[1]
{{{
$ sudo cat /proc/7376/stack
[<0>] rtR0SemEventMultiLnxWait.isra.2+0x33d/0x370 [vboxguest]
[<0>] VBoxGuest_RTSemEventMultiWaitEx+0xe/0x10 [vboxguest]
[<0>] VBoxGuest_RTSemEventMultiWait+0x28/0x30 [vboxguest]
[<0>] vgdrvHgcmAsyncWaitCallbackWorker+0x1c3/0x210 [vboxguest]
[<0>] VGDrvCommonIoCtl+0x489/0x18e0 [vboxguest]
[<0>] VBoxGuestIDC+0x149/0x160 [vboxguest]
[<0>] VbglR0IdcCallRaw+0x13/0x20 [vboxsf]
[<0>] VbglR0HGCMFastCall+0x1c/0x20 [vboxsf]
[<0>] vbsf_reg_open+0x291/0x4f0 [vboxsf]
[<0>] do_dentry_open+0x1c2/0x310
[<0>] vfs_open+0x4f/0x80
[<0>] path_openat+0x6bf/0x1900
[<0>] do_filp_open+0x9b/0x110
[<0>] do_sys_open+0x1bb/0x2c0
[<0>] SyS_openat+0x14/0x20
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0xffffffffffffffff
}}}",lesha
9559,Winsat fails with TSC Frequency,Windows,Windows,VirtualBox 4.1.2,2021-07-09T09:34:33Z,2021-07-09T09:34:33Z,"I can not get WinSat to run (Windows System Assessment Tool)

Pretty much every test receives this result:

>winsat formal
> Running the Formal Assessment
Error: Cannot Measure Time Stamp Counter (TSC) Frequency

>winsat cpu
Windows System Assessment Tool
Error: Cannot Measure Time Stamp Counter (TSC) Frequency

The Host machine is a Dell 6510 laptop with i7 q720 win7 x64.
The Guest is win7 x32.
Both are at SP1 and have current windows updates.


I've had no luck running winsat on any version 4 it did run on version 3 except for graphic.

I believe this same issue also leads to long guest OS pauses (for 30 - 90 second) where no activity in the guest happens and then it resumes to normal operations.

I have current guest additions installed,




",steve richards
20451,Bridged adapter list is empty (with NDIS5 drivers),Windows,all,VirtualBox 6.1.22,2021-07-09T10:35:18Z,2021-07-09T10:35:18Z,"As a workaround for #15060 I tried installing VirtualBox using the old NDIS 5 network drivers, by running the installer with the option `-msiparams NETWORKTYPE=NDIS5`

After installation, attempting to configure a bridged network interface is impossible because the list of adapters to bridge to is empty (see attached screenshot).

There are no other error messages from VirtualBox about a the failure to enumerate network adapters. It looks like the NDIS5 drivers are active, given...

{{{
PS > get-windowsdriver -online | Where-Object -property ProviderName -Like *oracle* | format-list

Driver           : oem16.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_a4e9db3f071a0883\vboxnetadp.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem22.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetflt.inf_amd64_1ca009f9c76e42da\vboxnetflt.inf
Inbox            : False
ClassName        : NetService
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem56.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetfltm.inf_amd64_4f271f5e54b849f3\vboxnetfltm.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem9.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxusb.inf_amd64_721cfc8f354e0c0c\vboxusb.inf
Inbox            : False
ClassName        : USB
BootCritical     : True
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080
}}}
",Sam Morris
15378,Not possible to resume VM after host hibernate & resume => Ubuntu bug,Linux,all,VirtualBox 5.0.20,2021-07-10T22:33:05Z,2021-07-10T22:33:05Z,"After hibernating and resuming my Ubuntu 14.04 host with a running VM, the VM is paused. All attempts to resume this VM failed with the error message: ""VM is paused due to host power management"". It tried to resume using the GUI by unchecking the hook at menu item ""Machine/Pause"", and I used the CLI tool with these command lines: ""VBoxManage controlvm $VMNAME resume"" and ""VBoxManage startvm $VMNAME"" and always got the same error message.

Workaround: Close the VM, then start it again. All data in the VM is lost.

{{{
$ VBoxManage --version
5.0.20r106931
}}}

{{{
$ uname -a
Linux $HOSTNAME 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
}}}

{{{
$ cat /etc/os-release
NAME=""Ubuntu""
VERSION=""14.04.4 LTS, Trusty Tahr""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 14.04.4 LTS""
VERSION_ID=""14.04""
HOME_URL=""http://www.ubuntu.com/""
SUPPORT_URL=""http://help.ubuntu.com/""
BUG_REPORT_URL=""http://bugs.launchpad.net/ubuntu/""
}}}",Bohnenzaehler
20453,Windows 10 guest on Ubuntu host is extremely slow if cpu > 1,Linux,Windows,VirtualBox 6.1.22,2021-07-12T11:53:04Z,2021-07-12T11:53:04Z,"I upgraded to Virtualbox 6.1, and I noticed a **great** slowdown on my Windows 10 guest. I tried to play with the settings, and I see that if I put the numbers of cpu to 1, the guest is faster!

So I tried to downgrade to 5.2 and set the number of cores to a number greater of 1. I have no problem at all.",Marco Sulla
20454,Linux cannot Log  user in with visual interface,Windows,other,VirtualBox 6.1.22,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
20393,Linux Guest [vmwgfx] *ERROR* SVGA device lockup,Windows,Linux,VirtualBox 6.1.18,2021-07-12T16:35:51Z,2021-07-12T16:35:51Z,"Hi,

I'm running a Linux guest on a Windows host and every so often the display will lock up. It's happened maybe 3 times in the last month and I haven't been able to correlate it with anything specific.

By lock up, I mean that it appears that the display stops updating. Input (at least mouse events) appear to work, but when it starts to lock-up, the display does not update in response to any input events until a few seconds go by. Pretty quickly, this behavior degrades to the point where it appears completely frozen and no more updates occur.

I can ssh in from my host and interact, so it seems it is just a display driver issue. dmesg shows the following:

[70545.554435] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70548.553727] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70558.765785] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out
[73420.314255] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73423.314445] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73433.384206] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out

Not sure what else to check, but can do whatever is needed to debug next time it happens. Just let me know.

I also see these messages appearing occasionally before hand, but they look to occur fairly regularly in the log without any other symptoms, so I don't know if they are related or not.

[54955.536381] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

I can provide more detailed hardware info (it's a Dell XPS 9500 using an i7-10857H w/ 32GB), os specifics (Win10, Ubuntu 20.04), and system config (I run 2 external displays on which I use my linux guest) or whatever else is needed.

I will attach my VBOX.log

Thanks for any help,
Brian

",brian-vbox
20381,6.1.22 hangs perhaps due to vmsvga/video,Windows,Linux,VirtualBox 6.1.22,2021-07-12T16:38:43Z,2021-07-12T16:38:43Z,"I had to downgrade to 6.1.20, which was stable for me.

I suspect it has something to do with video/vmsvga

Machine: HP Envy Pavilion 17t-j186nr 
Host is windows-10 updated to 19043.985 21H1
Guest is Fedora-Workstation-34 kernel 5.12.6-300, guest additions 6.1.22 is installed

With 6.1.22, If machine is started as hidden, machine can be ssh-ed to and is stable for very long time.

With 6.1.22, If machine is made to be shown, then after GDM login, after starting a terminal app, wezterm, firefox, virtualbox freezes, becomes non-responsive and remains stuck. 

It is possible to get mouse cursor, which in stcuk state is invisible, to the bottom, to hover over and bring up the VM-menu, minimize it and then get to the windows host. Other menu commands like reset do not work.

Outside, in the host windows, taskmgr can be used to kill and Virtualbox processes, helps close all virtualbox windows, and start over. 

reinstall of 6.1.22 did not help
",gkamathh
20459,Error ReLauching VirtualBox VM Process 5,other,all,VirtualBox 6.1.22,2021-07-14T06:54:21Z,2021-07-14T06:54:21Z,"Every time I try to launch my windows iso, the message (Error ReLauching VirtualBox VM Process 5)

Error code : 
E_FAIL (0x80004005)
Component : 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}",William Monette
20460,host freeze in bridge network mode,other,other,VirtualBox 6.1.22,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
20463,Windows 10 guest crashes on startup,Linux,Windows,VirtualBox 6.1.22,2021-07-19T10:35:04Z,2021-07-19T10:35:04Z,"Host is Pop OS 21.04 with kernel 5.13.2-051302-generic from Ubuntus mainline kernels.

Usually this works just fine, my VM started just fine on kernel 5.13.1 but now with the update to .2 it crashes on startup. I did do a `sudo vboxconfig` after a new kernel update, this did not help.

The crash is as follows:

{{{
	Jul 19 07:37:44 pc1 vboxdrv.sh: Stopping VirtualBox services.
	Jul 19 07:37:44 pc1 vboxdrv.sh: VirtualBox services stopped.
	Jul 19 07:37:46 pc1 vboxdrv.sh: Starting VirtualBox services.
	Jul 19 07:37:46 pc1 vboxdrv.sh: Building VirtualBox kernel modules.
	Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox kernel modules built.
	Jul 19 07:37:50 pc1 kernel: [  470.024094] vboxdrv: Found 32 processor cores
	Jul 19 07:37:50 pc1 kernel: [  470.041364] vboxdrv: TSC mode is Invariant, tentative frequency 3399987811 Hz
	Jul 19 07:37:50 pc1 kernel: [  470.041365] vboxdrv: Successfully loaded version 6.1.22 (interface 0x00300000)
	Jul 19 07:37:50 pc1 kernel: [  470.244020] VBoxNetFlt: Successfully started.
	Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox services started.
	Jul 19 07:37:50 pc1 kernel: [  470.245483] VBoxNetAdp: Successfully started.
	Jul 19 07:37:51 pc1 kernel: [  470.914903] SUPR0GipMap: fGetGipCpu=0x3b
	Jul 19 07:37:52 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199cb9d210' has no handler with id '59274'
	Jul 19 07:37:52 pc1 kernel: [  471.454134] vboxdrv: 0000000000000000 VMMR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.555385] vboxdrv: 0000000000000000 VBoxDDR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.609014] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76
	Jul 19 07:37:52 pc1 kernel: [  471.611471] vboxdrv: 0000000000000000 VBoxEhciR0.r0
	Jul 19 07:37:52 pc1 kernel: [  471.611804] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
	Jul 19 07:37:52 pc1 kernel: [  471.643364] device enp7s0 entered promiscuous mode
	Jul 19 07:37:52 pc1 gnome-shell[4732]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x620018a specified for 0x620018c.
	Jul 19 07:38:13 pc1 kernel: [  492.433391] device enp7s0 left promiscuous mode
	Jul 19 07:38:13 pc1 kernel: [  492.458757] 
	Jul 19 07:38:13 pc1 kernel: [  492.458757] !!Assertion Failed!!
	Jul 19 07:38:13 pc1 kernel: [  492.458757] Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf
	Jul 19 07:38:13 pc1 kernel: [  492.458757] Location  : /home/vbox/vbox-6.1.22/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT)
	Jul 19 07:38:13 pc1 kernel: [  492.458764] ffffad525034a000 <R3_STRING>: ffffffffffffffff != 00007f6f9c164640; cLockers=-1 cNestings=1
	Jul 19 07:38:13 pc1 kernel: [  492.489177] vboxnetflt: 0 out of 0 packets were not sent (directed to host)
	Jul 19 07:38:26 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199871a0a0' has no handler with id '61338'
	Jul 19 07:38:26 pc1 kernel: [  506.400406] vboxdrv: 0000000000000000 VMMR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.511297] vboxdrv: 0000000000000000 VBoxDDR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.553575] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76
	Jul 19 07:38:27 pc1 kernel: [  506.556406] vboxdrv: 0000000000000000 VBoxEhciR0.r0
	Jul 19 07:38:27 pc1 kernel: [  506.556838] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
	Jul 19 07:38:27 pc1 kernel: [  506.589360] device enp7s0 entered promiscuous mode

}}}",robert21
20464,Virtualbox 6.1.22 crashes on windows 10 host,Windows,Linux,VirtualBox 6.1.22,2021-07-20T02:50:25Z,2021-07-20T02:50:25Z,"My virtual box crashes after booting as well as after hibernation. It works fine after the first crash, but it surely crashes for the first time. I am using Virtualbox version 6.1.22, my host machine is Windows 10 and the guest machine is Kali.
",jishu
20465,Failure to load signed modules on UEFI secure boot system,Linux,all,VirtualBox 6.1.24,2021-07-21T06:39:00Z,2021-07-21T06:39:00Z,"As in title really. VirtualBox scripts build the modules, put them in right place but they (rightfully) cannot be loaded.

So I sign them.

And the story repeats - /usr/lib/virtualbox/vboxdrv.sh scripts doesn't recognize the drivers as valid ones, rebuilds them (trashing the signature I've just made) and the story repeats.

The problem probably is in line 330 in function module_available():

    [ ""$mod_dir"" != ""misc"" ] || return

which likely should be:

    [ ""$mod_dir"" = ""misc"" ] || return
",Tomek
8761,Silent failure to delete files on Shared Folders,Windows,Linux,VirtualBox 4.0.6,2021-07-21T08:05:07Z,2021-07-21T08:05:07Z,"When running bonnie++ bechmark on Linux guest (Fedora 14) in a shared folder under Windows XP host, the benchmark fails due to ""directory not empty"" at the end. 

The benchmark creates thousands of small files, and then deletes them. The problem is that after all deletions are done (and no error is reported), the benchmark directory is not empty.

Running the same benchmark on the same guest, but on a Linux native folder (VDI disk), the benchmark runs OK. No files left over.

VirtualBox 4.0.6 (the problem also occurred on VirtualBox 4.0.4, I just hadn't reported it yet, sorry)[[BR]]
Host: Windows XP Professional SP3[[BR]]
Guest: Fedora 14 kernel 2.6.35.11-83.fc14.i686[[BR]]
bonnie++-1.96-1.fc13.i686

Terminal session:

{{{
# cd /media/sf_some_shared_folder
# bonnie++ -u root -n 3 -s 0
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
# ls
Bonnie.1733
# ls Bonnie.1733/ | wc -l
1106
# for i in `seq 1 5`; do bonnie++ -u root -n 3 -s 0; done
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
...[snip, cut 4x repeated output]...
# for dir in `ls -d Bonnie*`; do \
    echo -n ""files left over in $dir: ""; \
    ls $dir | wc -l; done
files left over in Bonnie.1733: 1106
files left over in Bonnie.1743: 1111
files left over in Bonnie.1744: 1102
files left over in Bonnie.1745: 1102
files left over in Bonnie.1746: 1102
files left over in Bonnie.1747: 1108
# rm -rf Bonnie.*
# ls
}}}

Notes:[[BR]]
- bonnie++ option [-n 3] creates 3 * 1024 files[[BR]]
- The command [rm -rf Bonnie.*] successfully deletes all left over files. That said, as stated above the benchmark runs OK on native Linux guest disk instead of shared folder, so it seems the problem is not in bonnie++ code.[[BR]]
- There's no error / no message appearing at VBox.log for the running VM right before, during or after the benchmark. See attached file VBox-20110421-1939.log.


// BTM3505 (self reference, please ignore)
",Edmar (Macrovita)
20466,Virtualbox Extension Pack upgrade is unnecessarily convulted on Ubuntu,Linux,all,VirtualBox 6.1.24,2021-07-21T09:31:46Z,2021-07-21T09:31:46Z,"after upgrading the VirtualBox installation I need to follow the the following dialogs/procedure to upgrade the Extension Pack:
1. You have an old version... click Download
2. Are you sure you want to download... click Download
3. Do you wish to install ... click Install
4. An older version is already installed... click Upgrade
5. PUEL license agreement... read license to the bottom, click I Agree
6. Authentication is needed... enter admin pass
7. Successfully installed... click OK
8. Do you want to delete ... click Delete
This is frankly annoying and unnecessary.

This should be reduced to:
1. You have installed a new version of VirtualBox. You need to upgrade the Extension Pack. If you wish to do it, accept the PUEL license by entering the admin password. The package will be downloaded, installed. The old package is unusable, thus will be deleted.

Thanks for considering the change!",OM617
19314,Copy & paste patially broken in 6.1.2,Windows,Linux,VirtualBox 6.1.2,2021-07-21T13:40:05Z,2021-07-21T13:40:05Z,"Host OS is Windows 8
Guest OS is Ubuntu 18.04
Other platforms not tested.

I upgraded from 6.0.14 to 6.1.2. Matching guest additions are also installed.
In Ubuntu the included guest toos are installed:
virtualbox-guest-dkms 5.2.34-dfsg-0~ubuntu18.04.1
Copy & Paste was working fine with 6.0.14 in both directions and I could copy & paste ""larger amounts"" of text characters. A few tens or hundred lines worked fine.
With 6.1.2 I can only copy & paste very view lines, about 4 to 8, depending on their length. This applies to both directions.
When the contents becomes to large, the paste target ""remembers"" the last clipboard content and pastes it instead.

No log currently available.",Megabreit
20377,Can not select extension file for install in host,Linux,other,VirtualBox 6.1.22,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
20468,VM crashes during reboot if EFI is used on Ryzen CPU,Windows,Windows,VirtualBox 6.1.24,2021-07-21T23:58:34Z,2021-07-21T23:58:34Z,"Guru crash dialog during reboot of EFI Windows 10 VM upon the way back up at the EFI screen when more than 1 vCPU is used.  I have a Ryzen 7 3700X CPU on a B550M chipset motherboard.
Reference forum post https://forums.virtualbox.org/viewtopic.php?f=1&t=103398&sid=5b8fb3bf048f3b4fda4d91bcbd9ec0d3.  User fth0 looked at the logs and found that ""vCPU1 (the second vCPU) is in real mode and triple-faults"".

Logs attached.
",Justinh
20469,6.1.24 Memory can't be written,Windows,Windows,VirtualBox 6.1.24,2021-07-22T12:00:47Z,2021-07-22T12:00:47Z,"Windows 11 guest restarted after update normally.[[BR]]

Bootmgr messaged about HDD corruption and couldn't proceed. I closed guest window and it showed message from VirtualBox that memory can't be written.

The error appeared once only and I couldn't reproduce it again.",MikhailRokhin
20470,Enabled VB Host Only Network adapter causes Internet Connection Icon to show No Internet on Windows 10,Windows,other,VirtualBox 6.1.24,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
20472,Can't insall VirtualBox,Windows,Windows,VirtualBox 6.1.24,2021-07-23T20:13:48Z,2021-07-23T20:13:48Z,"Hi :) 

I am on a Surface Pro 5 i5 4gbram, can't install VirtualBox on Windows 11. 

Did it on Windows 10 but not on 11.

It gives an error, Windows it can't run due to performance and it is basically this app can't run on this version of Windows.
",Shawnloveshorses161
20473,Can't insall VirtualBox VM,Windows,Windows,VirtualBox 6.1.24,2021-07-24T01:50:05Z,2021-07-24T01:50:05Z,"Hi,

I cant' seem to run the attached VM to VirtualBox, please help",Shawnloveshorses161
20476,Interpret Host Key combination on keys up instead of down,Windows,Windows,VirtualBox 6.1.24,2021-07-24T22:30:16Z,2021-07-24T22:30:16Z,"I'd like the guest OS to be able to see that Ctrl+Alt are down even though those keys are mapped as the Host Key combination.

Other virtualization software allows the key combination to be seen by the guest by not acting upon said combination until all keys in the combination return up, with no additional keys or mouse clicks preformed between the down/up events of those keys.

The reason for this request is spending an hour tracking down why Ctrl+Alt+Left-Click didn't perform the action I had mapped in Visual Studio. If the above request is not feasible, please consider providing some type of feedback to the user that something special is going on when pressing the Host Key, such as flashing the window or, if the status bar is visible, make the background for the Host Key combination flash a different color a couple times.",OkieDan
17696,Processor ID and MotherBord ID Missing,Windows,other,VirtualBox 5.2.8,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
20477,log spam/constant high cpu usage related to audio,Mac OS X,Linux,VirtualBox 6.1.22,2021-07-26T10:51:34Z,2021-07-26T10:51:34Z,"I can see constant high cpu usage due to logging, in the virtualboxvm and logd processes on the host but possibly a genuine problem with the audio subsystem somewhere.

When I look at the logs, it keeps spamming it with:

 buffer 0 ptr 0x7fe11a313f5c size 0

It's coming from audiotoolboxcore.
",gl
20180,Windows 10 guest OS crashes with STATUS_DATATYPE_MISALIGNMENT exception,Linux,Windows,VirtualBox 6.1.18,2021-07-26T23:09:42Z,2021-07-26T23:09:42Z,"My '''Windows 10 20H2''' guest OS keeps crashing and rebooting after a few minutes of uptime, even when left at idle with no user activity.
The amount of uptime before crash varies, from a couple of minutes to maybe 30'.

This is an extract of the VBox.log file with the exception (full log attached):

{{{
00:04:04.476177 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
00:04:04.476246 GIMHv: BugCheck 1e {ffffffff80000002, fffff80426ae4793, ffffbd0cd2c0237a, 7010008004002001}
00:04:04.476246 KMODE_EXCEPTION_NOT_HANDLED
00:04:04.476246 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:04:04.476246 P2: fffff80426ae4793 - EIP/RIP
00:04:04.476247 P3: ffffbd0cd2c0237a - Xcpt param #0
00:04:04.476247 P4: 7010008004002001 - Xcpt param #1
00:04:07.226307 AHCI#0: Reset the HBA
00:04:07.226322 VD#0: Cancelling all active requests
00:04:07.226560 AHCI#0: Port 0 reset
00:04:07.227608 VD#0: Cancelling all active requests
00:04:07.367081 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:04:09.277149 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
}}}

The VM's guest OS was freshly installed from Microsoft's ISO. No third party AV software nor drivers installed.

My host setup:
* OS: Ubuntu 20.04.1
* Kernel: tested with 5.8.0-41-generic (Ubuntu) and 5.9.16-050916-generic (mainline)
* System: HP ProBook 650 G8
* CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
* VirtualBox: tested with 6.1.16 (Ubuntu's repo) and 6.1.18 r142142 (Oracle's repo)

Conditions that do not cause a crash:
* running the VM in safe mode
* running the VM in a different host with Ubuntu 20.04.1, kernel 5.8, Virtualbox 6.1.18 r142142, CPU AMD Ryzen 9 3900X
* converting the VM's vdi file to qcow2 and running it with KVM

What have been tested without success (VM still crashes):
* running it with a different CPU profile, ""i7-6700K"" instead of ""host""
* uninstalling the VirtualBox Guest Additions
* changing the paravirtualization interface from ""Default"" to ""Legacy""

This issue has been discussed in this forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=101667

Searching the forums for similar problems led to these apparently relevant discussions, all with no solutions nor workarounds:
* https://forums.virtualbox.org/viewtopic.php?f=7&t=101280
* https://forums.virtualbox.org/viewtopic.php?f=7&t=101353
* https://forums.virtualbox.org/viewtopic.php?f=7&t=99789
",hottobar
20478,Virtualbox locks up badly with fstrim on CentOS 8,Windows,Linux,VirtualBox 6.1.24,2021-07-28T16:57:33Z,2021-07-28T16:57:33Z,"I tried using fstrim, with a VM presenting a virtio-scsi ""disk"", and it worked for a while (defined as ""the VDI file backing the FS shrinking on disk""), then eventually most IO hung indefinitely.

Most excitingly, SysRq-B resulted in the VM being stuck with its ""display"" showing a mix of black and occasional green boxes and not rebooting, then if I attempted to do anything to the VM (e.g. ""Reset"", ""Poweroff""), the window became unresponsive, and I had to force-close it, and VB reported ""Aborted"" for the VM status.

When I tried reproducing it just now for this ticket, it instead just blocked indefinitely in the OS - no errors reported, but fstrim wouldn't respond to ^C or kill -9, and trying to close the VM window hung and then reported Aborted.",rincebrain
15092,virtualbox 5.0.14 linux host failed seamless mode with windows 10 guest,Linux,Windows,VirtualBox 5.0.14,2021-07-28T17:04:02Z,2021-07-28T17:04:02Z,"Windows 10.0.10586 guests run perfectly well in windowed and full screen modes but not in seamless mode. The command to enter seamless works, but after the window disappears as if entering seamless mode, it switches to one similar to  full screen with a transparent band at the top showing the Linux desktop.  
Windows 7 works perfectly in all modes. I've observed the same behavior in every release of VB5 and W10 I've tried starting at 5.0.1. I've tried changing compositing between OpenGL and Xrender on the host, enabling and disabling 3D and 2D on the guest, nothing helps.

This may not be a critical bug, but it keeps me using w7 guests for real work--seamless mode is key.

The host runs an AMD-FX-9370 CPU, GeForce GTX 960, 32GB RAM, NVidia 361.18 drivers, Linux kernel 4.4, Mint 17.3 KDE with X server 1.17.1. 

I've attached the latest log showing startup and switches between modes.
",matthewls
20309,Windows guests abort upon shutdown on linux hosts with segfault indicated in /var/log,Linux,Windows,VirtualBox 6.1.18,2021-07-28T22:32:06Z,2021-07-28T22:32:06Z,"I have been seeing windows guests crash during shutdown then listing as ""aborted"" in the main Virtualbox control GUI.

Surveying /var/log/messages indicates segfaults in the shclipboard process.

audit[7775]: ANOM_ABEND auid=xxxx uid=xxxx gid=xxx ses=3 subj=kernel pid=xxxx comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
Apr 10 09:22:13 xwing kernel: ShClipboard[7839]: segfault at 20 ip 00007f5d5d68622a sp 00007f5d900bbd40 error 4 in libXt.so.6.0.0[7f5d5d668000+41000]

Similar segfaults have been observed by others in the forums. As noted by some, the Virtualbox logs do not indicate a problem at the time of the crash.
Shared Clipboard is DISABLED for the guests.  I do not make use of this feature and so turn it off for my guest machines.

Host: Fedora 32 Linux running kernel 5.11
Virtualbox installation via virtualbox.org site: Fedora repo and manually downloaded extension pack.

I've noticed the problem since upgrading from Virtualbox 5.2 to Virtualbox 6.x as part of an upgrade from Fedora 30 to Fedora 32 several months ago.

The problem has persisted through a recent upgrade to Virtualbox 6.20.

If I do not log into the Guest after booting the guest, but shut it down from the Guest login screen, the guest shuts down without crashing.  I'm assuming that this is related to engaging some part of the Guest additions services after logging into the guest.  Again, Shared Clipboard has been turned off in the guest's options within the Virtualbox control GUI.

As I understand it, the shared clipboard will run services on both the host and the guest to manage the data exchange.  It appears that something may trigger a poling of the clipboard from the host side during guest shutdown, independent of whether the service is running on the guest.


",HDCompute
20462,VBoxNetLwf and EventID 12 on Windows,Windows,all,VirtualBox 6.1.22,2021-07-29T11:04:38Z,2021-07-29T11:04:38Z,"I am aware that this has been posted already but I cannot find an open ticket! In reference to:
https://forums.virtualbox.org/viewtopic.php?f=6&t=87971
I would like to mention that all solutions are not working and the issue is permanent:

Randomly, the VBoxNetLwf driver crashes and causes an event log entry with ID 12. Unfortunately this also causes the WiFi connection to disconnect and it takes some time until Windows recovers internet connection.

I've attached two of these log entries in a file.

Is there anything that can be done about it? Is there already any knowledge when this happens and where (in the source code) this issue occurs? I also read it maybe related to energy management. But I doubt that since it happens for me also when I am actively working on the computer e.g. connected to a remote machine via VPN (which gets disconnected in that case, obviously).",Slimfast
20481,Working VM suddenly stop loading in GUI mode (F7) but working  in tty1 to tty6 mode,Windows,Linux,VirtualBox 6.1.24,2021-08-02T12:33:23Z,2021-08-02T12:33:23Z,"Hi,
I ahve few(3) VMS based out of ubuntu 18.04(bionic) which were all functional from at least a year now. But yesterday, one of the 3 VM stops booting up in GUI mode(F7). It ends up ina blinking curson on the screen.
I can login into machine from tty1,ty2 to tty6 '''but not  getting anything on tty7 but a blinking cursor only'''.

Attaching vbox logs for someone to take a look urgently.

Note: I have checked some existing issues:
1. My host(windows 10) hypervisor is disabled.
2. I can  successfully run other 2 VMs
3. My VM has sufficient RAM/Space(from df and free output)
4. Virtualisation is enabled in BIOS settings.
5. Uptodate Vbox version and extension pack.
6. Done apt-get update  from tty1 and rebooted multiple times.
7. 3D acceleration is in disabled mode.

Please check my logs attached. ",vas
20486,When I download an 18GB file,other,other,VirtualBox 6.1.26,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
19267,Guest audio loss on host display suspend,Windows,Windows,VirtualBox 6.1.2,2021-08-04T08:46:40Z,2021-08-04T08:46:40Z,"Windows 7 guest audio ceases to function after host display is suspended if audio input is disabled for guest. 
The display is connected via HDMI interface. Sound in host is working without any issues. 
Issue is present at least since VB version 6.0 but possibly longer.
Workaround is the enable audio input for guest.
Related forum topic [https://forums.virtualbox.org/viewtopic.php?f=6&t=96411&p=468546 here]",Banana James
20489,virtualbox vms are no longer finctioning,other,Windows,VirtualBox 6.1.26,2021-08-05T04:36:11Z,2021-08-05T04:36:11Z,I updated virtualbox when prompted from then onwards the VM's that I made are no longer functional,Adhu
20252,[SVN version] compile error under python 3.9: _Py_NewReference was not declared in this scopt,Linux,other,,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
20491,Support modifiers in user-defined keyboard shortcuts,all,all,VirtualBox 6.1.26,2021-08-06T12:03:01Z,2021-08-06T12:03:01Z,"In File > Preferences... > Input > Virtual Machine (and in the corresponding menu of a virtual machine) one can set keyboard shortcuts for various host key combinations.  While there are some predefined shortcuts that include modifiers, modifiers are not supported in user-defined shortcuts, e.g. entering Ctrl+Shift+Z results in Host+Z.

Please support modifiers in user-defined keyboard shortcuts.",mjf
20492,Debian installer hangs: BUG: unable to handle kernel NULL pointer dereference at 00000004,Windows,Linux,VirtualBox 6.1.26,2021-08-06T22:14:39Z,2021-08-06T22:14:39Z,"I'm trying to install Debian 10 i386 on a Windows 10 (64-bit) host but the installer hangs during ""Select and install software"", specifically ""Configuring man-db (i386)"". Do not modify the default software selection (Debian desktop, print server and standard system utilities). It happens every time, both in the graphical and the non-graphical installer. I'm running an AMD Ryzen 7 3800X and AMD-V appears to be enabled.

This is logged by the kernel once the system hangs:
{{{
[  401.003262] BUG: unable to handle kernel NULL pointer dereference at 00000004
[  401.003775] *pde = 00000000 
[  401.003978] Oops: 0002 [#1] SMP
[  401.004197] CPU: 0 PID: 21003 Comm: mandb Not tainted 4.19.0-17-686 #1 Debian 4.19.194-1
[  401.004767] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[  401.005336] EIP: _raw_spin_lock+0x14/0x30
[  401.005618] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.007152] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.007694] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: ee4efef4
[  401.008228] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.008863] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
[  401.009382] Call Trace:
[  401.009597]  speculation_ctrl_update+0x1aa/0x220
[  401.009976]  speculation_ctrl_update_current+0x18/0x20
[  401.010399]  task_update_spec_tif+0x25/0x30
[  401.010745]  ssb_prctl_set.part.1+0x1d/0x30
[  401.011091]  arch_seccomp_spec_mitigate+0x45/0x50
[  401.011488]  do_seccomp+0x5b0/0x5f0
[  401.011776]  sys_seccomp+0x16/0x20
[  401.012059]  do_fast_syscall_32+0x81/0x1a0
[  401.012400]  entry_SYSENTER_32+0x68/0xbb
[  401.012848] EIP: 0xb7efdd31
[  401.013188] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
[  401.015419] EAX: ffffffda EBX: 00000001 ECX: 00000000 EDX: 0162db20
[  401.016174] ESI: 015b5352 EDI: b7eded4d EBP: b7c7dde9 ESP: bfdab85c
[  401.016929] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
[  401.017753] Modules linked in: fuse battery dm_mod md_mod xfs jfs btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c vfat fat ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb e1000 nls_utf8 isofs usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ohci_pci ehci_pci ohci_hcd ehci_hcd ata_piix snd_intel8x0 snd_ac97_codec ahci libahci ac97_bus evdev libata psmouse snd_pcm snd_timer usbcore usb_common snd soundcore scsi_mod
[  401.022503] CR2: 0000000000000004
[  401.022903] ---[ end trace 8693d9353e91b6c4 ]---
[  401.023448] EIP: _raw_spin_lock+0x14/0x30
[  401.023933] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.026189] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.026947] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: dca193bc
[  401.027704] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.028492] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
}}}

I've attached the full kernel log, as well as the VirtualBox log on the host.",joelpuig
20458,Is kernel 5.14.0-0.rc0.20210709gitf55966571d5e.14.fc35.x86_64 supported?,other,other,VirtualBox 6.1.22,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
20485,"CentOS 7, VirtualBox 6.1: compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’",Linux,other,VirtualBox 6.1.26,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
5747,Bridged Networking on Ethernet and Wireless Bonded interface fails,Linux,Windows,VirtualBox 3.1.0,2021-08-11T16:19:10Z,2021-08-11T16:19:10Z,"I am using bonding to enslave eth0 and wlan0 together on a Debian Linux Host.

if the ethernet interface is operating and is the primary (which is what I have as default) the Guest is able to access the network.  if the the wireless interface if the primary the guest cannot access the network.

using NAT works but I need to use a PPTP VPN from the guest but Virtualbox does not support GRE via NAT setup.

My network interfaces looks like this on the host to setup bonding between the wireless and ethernet.


# The loopback network interface[[BR]]
auto lo[[BR]]
iface lo inet loopback[[BR]]
[[BR]]
# Bonding interface[[BR]]
auto bond0[[BR]]
iface bond0 inet dhcp[[BR]]
  bond_mode active-backup[[BR]]
  bond_primary eth0[[BR]]
  bond_miimon 100[[BR]]
  bond_downdelay 200[[BR]]
  bond_updelay 200[[BR]]
  wpa-ssid wifi[[BR]]
  wpa-ap-scan 1[[BR]]
  wpa-psk password[[BR]]
  wpa-scan-ssid 1[[BR]]
  wpa-iface wlan0[[BR]]
  slaves eth0 wlan0[[BR]]",James Robertson
20500,V6.1.26 with Windows 10 2019 LTSC as guest,Linux,Windows,VirtualBox 6.1.26,2021-08-12T09:45:13Z,2021-08-12T09:45:13Z,"With last version 6.1.26 ""Auto-resize Guest Display"" doesn't work anymore.",-RedHead-
20158,"VirtualBox falsely claims that using hyperthreaded cores is an ""invalid setting""",other,other,VirtualBox 6.1.18,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
14743,X11 guests: Invisible drag-and-drop window blocks mouse interaction,Linux,Linux,VirtualBox 5.1.6,2021-08-13T05:36:14Z,2021-08-13T05:36:14Z,"I first noticed this in v5.0.6, but it just happened to me again in 5.0.8.  After several days of using a guest, all of a sudden mouse clicks no longer work.  Both left and right mouse clicks do nothing, as if the clicks are not making it to the guest.  Moving the mouse works.  Guest additions are installed.

When the clicks stop working, the mouse continues working correctly in the host and in other guests running on this host.

Rebooting the affected guest fixes the problem.

I looked through the log file, though I see nothing obvious.  In this case, the timestamps in the log indicate the guest was only running for 37 hours and 29 minutes.  I'd guess the problem started around 37 hours and 27 minutes.  I rebooted it a minute or so after it happened.",Stéphane Charette
15271,"USB mouse ""dies"" - pointer still moving but no function",Windows,Linux,VirtualBox 5.0.16,2021-08-13T05:38:52Z,2021-08-13T05:38:52Z,"I am using a kubuntu 15.10 64 bit guest on Windows 7 Enterprise SP 1 with Version 5.0.16 r105871.

About every day, the USB mouse kinda dies in the guest - it still works normal on the Windows host and the pointer still moves in the kubuntu guest, but focus follows mouse and clicks don't do anything any more. Keyboard and everything else still works fine.

Logging off from KDE and on again fixes the problem.

In the attached dmesg, there is an issue with IRQ 22 and a stack trace which I am quite sure are related. The relevant VBox.log is also attached.",Torsten Römer
19302,Mouse support fails,Windows,Linux,VirtualBox 6.0.16,2021-08-13T06:17:00Z,2021-08-13T06:17:00Z,"I've come across this really odd bug with my guest Kali Linux (2019.2, 2019.4 and 2020.1; all had the latest guest additions installed), where mouse support randomly fails.

I can move the cursor. The keyboard works perfectly fine but I can't click anything with the mouse. The really odd thing is, that if I use the menu key (or application key) on the keyboard, the targeted application opens the right-click menu. In this menu, the mouse works again as expected. I've captured a short clip showing the issue. Mouse clicks are not shown, but I've clicked on every button/menu in the clip, when I hover over them.",GarlicCheese
20501,Installation start crash of Win10 guest on Win7 host.,Windows,Windows,VirtualBox 6.1.26,2021-08-14T14:45:34Z,2021-08-14T14:45:34Z,"Machine: LENOVO W701 with Win7 ultimate host OS. 
Win10 Iso image is open in BD-ROM virtual DVD drive. After configuration of the VM for Win10 guest OS clicking start. The VM starts running in VB 6.1.26 and the Win10 screen appears with blue window in mids the black screen. Roughly 10 seconds later an error message appears reporting the fatal error crash.
The log file does not make my sly. Anyone an idea what has happened?
A Win7 guest installation on this system works fine.",drghl
20505,Wrong System Time in OS/2 Guest,Windows,other,VirtualBox 6.1.24,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
20506,Attaching Yubikey USB device to VM causes Guest VM to Crash within Seconds,Mac OS X,Linux,VirtualBox 6.1.26,2021-08-19T08:31:39Z,2021-08-19T08:31:39Z,"Host OS: macOS 11.5.1
Guest OS: Ubuntu 20.04.2.0 x64 with Guest Additions installed
VBox: 6.1.26

Within the Guest OS, when accessing a website that uses FIDO/U2F authentication with a Yubikey USB device, I attached the Yubikey to my host machine and then used the Devices | USB menu to pass through the Yubikey USB device to the Guest machine.  The device worked properly and authentication with the website succeeded within the guest.  However within a few seconds (perhaps 5 seconds) the guest VM process crashed and macOS displayed a ""Problem Report for VirtualBox VM"" dump report window with stack traces (see attachment).  I repeated this three times and each time the crash occurred.  On the third time, after successfully passing through and authenticating with the Yubikey USB device, I quickly accessed the Devices menu to detach the Yubikey USB device, which detachment appeared to succeed (the checkmark next to it was removed), however, again, a few seconds later the guest VM process crashed.  ",OtterFlip
20517,Unable to connect 2TB seagate external USB drives to RHEL7 Guest,Windows,Linux,VirtualBox 6.1.26,2021-08-21T23:06:43Z,2021-08-21T23:06:43Z,"Hi Team, 
I'm having issues connecting multiple different 1.7 TB seagate external USB drives to my RHEL7 guest vms. 

The error and a drive properties view from windows is attached for your review. 

Also, I can attach a 1TB external drive just fine, so I'm thinking that it's a driver compatibility issue with the larger drives that's the problem? 

Thanks!",hanch0
20519,ubuntu isn't booting right,Windows,Linux,VirtualBox 6.1.26,2021-08-22T14:10:38Z,2021-08-22T14:10:38Z,"after tweaking and messing around with the guest os, which is ubuntu. instead of 'save the machine state', i used 'send the shutdown signal', and now the virtual machine isn't booting right. is there a way i can restore to previous versions?",Shoham
8311,SATA AHCI Errors: READ FPDMA QUEUED,Windows,Linux,VirtualBox 4.0.2,2021-08-23T04:41:22Z,2021-08-23T04:41:22Z,"My guest OS hangs periodically with a harddrive command error followed by an attempt to reset the HD (reproduced with Ubuntu and !ArcLinux). This issue does not occur in the host OS (Windows 7), only in the Guest OS.

Environment:

 * Ubuntu running in a Virtual Box 4.0.2 running on Windows 7 64bit.
 * Asus G53JW Laptop
 * Intel X25 SSD HD

Log excerpts:
{{{
Jan 17 14:48:32 vm kernel: [ 1513.120252] ata3: hard resetting link
Jan 17 14:48:33 vm kernel: [ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus
123 SControl 300)
Jan 17 14:48:33 vm kernel: [ 1513.471232] ata3.00: configured for UDMA/133
Jan 17 14:48:33 vm kernel: [ 1513.471241] ata3.00: device reported invalid CHS
sector 0
Jan 17 14:48:33 vm kernel: [ 1513.471255] ata3: EH complete
}}}
{{{
[ 1513.120200] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 1513.120210] ata3.00: failed command: READ FPDMA QUEUED
[ 1513.120222] ata3.00: cmd 60/08:00:30:66:4c/00:00:00:00:00/40 tag 0 ncq 4096
in
[ 1513.120224]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 1513.120230] ata3.00: status: { DRDY }
[ 1513.120252] ata3: hard resetting link
[ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1513.471232] ata3.00: configured for UDMA/133
[ 1513.471241] ata3.00: device reported invalid CHS sector 0
[ 1513.471255] ata3: EH complete
}}}",andornaut
20522,hang on windows after update notifier window pops up,Windows,Linux,VirtualBox 6.1.22,2021-08-23T15:54:51Z,2021-08-23T15:54:51Z,"i was using a relatively recent VirtualBox version on Windows 10
and was sending my host machine to sleep (as it works quite nice all the time).
after a wake up VBox brought up the notifyer dialog for a new version
beeing available on the internet for download. (not sure if that dialog is normally modal or not - but it would be better if its not!)
at this point i was no longer able to control the main application and neither the currently running VM window. neither keyboard nor mouse input were able to interact with any of the two main windows and (BAD THING HERE) not even with the update notifier pop up windows.

(closing either of this first with a task manager did not cure the situation for the other window.)",jetpilot
20516,E_FAIL (0x80004005) after host PC hibernation,Windows,all,VirtualBox 6.1.26,2021-08-23T18:40:35Z,2021-08-23T18:40:35Z,"After I woke up the host PC from hibernation, when I try to start a virtual machine I get the following error:

{{{
Failed to open a session for the virtual machine Windows_10_Pro_LV_2018_SP1.
The VM session was aborted.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}

The error occurs before the VirtualBox logo appears in the launch screen of the virtual machine.[[BR]]
The error does not happen if the host PC is shutdown and restarted.[[BR]]
The error has occurred after updating virtualbox to 6.1.26.

VirtualBox Graphical User Interface[[BR]]
Version 6.1.26 r145957 (Qt5.6.2)[[BR]]
Host OS: Windows 7 Pro 64bit[[BR]]
Guest OS: Windows 10 Pro 64bit or Windows 7 Pro 64bit

As highlighted in the forum post [https://forums.virtualbox.org/viewtopic.php?f=6&t=103708], the problem is solved by completely disabling the audio of the virtual machine.

The issue is repeatable, by re-enabling the audio the error appears the same.

The VBox.log file is attached for checking.
",Asper
20461,Can not drag and drop from host to guest,Windows,Windows,VirtualBox 6.1.16,2021-08-24T13:51:59Z,2021-08-24T13:51:59Z,"Host Windows 10
Guest Windows 8.1
VirtualBox 6.1.16-140961
Guest Additions 6.1.16
VirtualBox Extension Pack 6.1.16-140961

Copy and paste bidirectional works fine.
Drag and drop from Guest to Host works fine.

Drag and drop from Host to Guest is not working.",ewsaracco
16795,"TRIM on SSD not stable with Linux, Windows 10, FreeBSD",Windows,all,VirtualBox 5.1.22,2021-08-24T16:07:04Z,2021-08-24T16:07:04Z,"Linux TRIM timeouts sometimes, FreeBSD same, Windows 10 doesn't boot at all

See below and attachments for details:[[BR]]

Linux Fedora 25 latest updates
1. Attach an image:
{{{
VBoxManage storageattach ""Fedora 25"" --storagectl ""SATA"" --port 0 --device 0 --nonrotational on --discard on --medium ""Fedora 25.vdi"" --type hdd
}}}
2. check trim enabled
{{{
hdparm -I /dev/sda | grep TRIM
           *    Data Set Management TRIM supported (limit unknown)
}}}
3. Enable it in the mount options and reboot afterwards
{{{
/dev/mapper/fedora-root /                       ext4    defaults,discard        1 1
}}}
4. run fstrim /
Hangs sometimes with timeouts


FreeBSD 11 latest updates
1. Attach disk as under Linnux
2. Check for TRIM support
{{{
camcontrol identify /dev/ada0 | grep -i trim
Data Set Management (DSM/TRIM) yes
}}}
3. Enable TRIM support on filesystem
{{{
mount | grep -i ufs
/dev/ada0p2 on / (ufs, local, journaled soft-updates)

# Boot into single user mode
tunefs -t enable /dev/ada0p2
tunefs: issue TRIM to the disk set

bash -c 'tunefs -p /dev/ada0p2 2>&1 | grep -i trim'
tunefs: trim: (-t)                                         enabled
}}}",linuxguru
19505,Windows ME guest ICH AC97/Sound Blaster 16 Audio issues,Windows,Windows,VirtualBox 6.1.6,2021-08-24T20:40:43Z,2021-08-24T20:40:43Z,"Whenever Windows ME Host plays audio such as a WAV, MID, or MP3, when the user clicks stop or when the audio file reaches the end, the audio file may or may not it keeps looping the last 1 or 2 seconds infinitely. It will most of the time. It even happens when a user logs in and the startup sound keeps playing until you play another audio file and stop it multiple times until all noise stops. ",RexBuyeo
20480,SSM: Giving up: Too many passes! (1048576),Linux,Windows,VirtualBox 6.1.10,2021-08-27T21:05:58Z,2021-08-27T21:05:58Z,"We use Virtualbox to make crash-consistent backups of VMs. The script does basically:
- Take snapshot
- Clone snapshot to backupfolder
- Delete snapshot

In some cases (we believe it might be 'busy Windows servers running databases') the backup takes longer than normal. The next day it will take even longer, until after a few days the whole snapshot-taking will fail:

VBoxManage: error: Failed to take snapshot
VBoxManage: error: Failed to save the machine state to '/mnt/path/to/file.sav' (VERR_SSM_TOO_MANY_PASSES)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
VBoxManage: error: Context: ""RTEXITCODE handleSnapshot(HandlerArg*)"" at line 483 of file VBoxManageSnapshot.cpp


A subtract of the logfile does show the problem 'building up' over several days. As soon as the problem exists (and the snapshot fails and keeps failing) it will not go away until we reboot the host:

20:58:09.224319 SSM: Step 1 completed after pass 77.
44:58:12.823156 SSM: Step 1 completed after pass 66.
68:58:11.413950 SSM: Step 1 completed after pass 68.
92:58:12.074819 SSM: Step 1 completed after pass 66.
116:58:13.100936 SSM: Step 1 completed after pass 71.
140:58:17.220420 SSM: Step 1 completed after pass 76.
164:58:16.008601 SSM: Step 1 completed after pass 67.
188:58:17.074839 SSM: Step 1 completed after pass 67.
212:58:17.135282 SSM: Step 1 completed after pass 69.
236:58:17.638284 SSM: Step 1 completed after pass 66.
260:58:18.045740 SSM: Step 1 completed after pass 68.
284:58:18.171871 SSM: Step 1 completed after pass 67.
308:58:17.953139 SSM: Step 1 completed after pass 66.
332:58:18.609908 SSM: Step 1 completed after pass 69.
356:58:19.043087 SSM: Step 1 completed after pass 67.
380:58:45.760012 SSM: Step 1 completed after pass 397.
405:00:09.558703 SSM: Step 1 completed after pass 1598.
429:01:14.283550 SSM: Step 1 completed after pass 2457.
453:16:20.819291 SSM: Step 1 completed after pass 14096.
498:30:29.200112 SSM: Step 1 completed after pass 964826.
549:39:38.213154 SSM: Giving up: Too many passes! (1048576)
549:39:47.451837 SSM: Failed to save the VM state to '/mnt/path/to/file.sav' (file deleted): VERR_SSM_TOO_MANY_PASSES
597:35:18.928754 SSM: Giving up: Too many passes! (1048576)
597:35:40.379878 SSM: Failed to save the VM state to '/mnt/path/to/file.sav' (file deleted): VERR_SSM_TOO_MANY_PASSES

We observed that the .sav-file is growing really big before failing.

The whole VBox.log is attached, as well as the relevant commands of our bash-script.",AO
20526,High VMM load on VMs with more than 1 core,Windows,all,VirtualBox 6.1.26,2021-08-28T02:27:31Z,2021-08-28T02:27:31Z,"The VMM load is stuck about 60% when running VMs assigned with more than 1 core although the guest is totally idle.
I'm using 6.1.x revision 146512 but the problem persist on all the recent versions.
I have enabled ioapic,apic,x2apic but no use.
Note that the VM process does not use much cpu actually, but it is a bit more lag than usual.

image
[[Image(https://i.ibb.co/L0jFyJM/image.png)]]",ebk
20528,3d acceleration with VMSVGA sometimes leads to a crash or a hang of VirtualBox,Windows,Linux,VirtualBox 6.1.26,2021-08-30T20:40:34Z,2021-08-30T20:40:34Z,"When using a Linux VM (debian 9/10) and Windows host with VMSVGA video adapter and 3d acceleration, the VM sometimes might crash or hang. The crash/hang happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

When the crash occurs, the error message is ""The instruction at .... referenced memory at 0x0000000000000010...""

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox ""Use hardware acceleration when available"" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser (sometimes the crash only happens when closing the browser).

Attached are 2 logs: one with a crash with Chromium 90 and another one with a hang with Chromium 83. The hang has happened when the ""accept cookies"" window from zoom.us was loading: it turned out to be completely corrupted and the VM hang occurred. The error in the log is VMSVGA related but is different to what I see in case of a crash. In the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

This problem was first reported in https://www.virtualbox.org/ticket/19154. 
I did more tests today trying to reproduce the problem using Nvidia GPU, but couldn't. Today I also couldn't reproduce the problem using Intel GPU and exactly the same setup as I was using previously. So the problem is not 100% reproducible, unfortunately (until today I could reproduce it all the time - ~20-30 times or so). If I see the problem again, I will do tests with NVidia and will update the ticket.",Mikhail Kovalev
20530,Request Ability To Share Smartcard With Host and Guest,other,other,VirtualBox 6.1.26,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
15665,Mouse pointer graphic is messed up,Windows,Solaris,VirtualBox 5.1.2,2021-09-01T17:43:27Z,2021-09-01T17:43:27Z,"Host: Windows 7 Enterprise 64 bit
Guest: Solaris 10

After installing 5.1.2, the graphic for the mouse pointer in my guest OS is messed up. It looks very bizarre. You can kind of see what the pointer should be, but it is heavily obscured by a bunch of dark ""noise"" that surrounds the pointer in a small rectangle. 

I think this only happened when Mouse Integration was enabled. 

Previous to the upgrade, I was using 5.0.16. I have now downgraded to 5.0.26, and the problem is no longer present. I can't imagine anyone who experiences this would consider it acceptable; I know that I won't be using any 5.1 versions unless this can be resolved. ",Gordon M
20514,Networking is not functional under OPENSTEP 4.2/Mach for Intel,other,other,VirtualBox 6.1.26,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
20532,BSOD when un-plugging USB device with Windows 10 Host and Windows 7 Guest (VM On),Windows,Windows,VirtualBox 6.1.26,2021-09-02T15:52:06Z,2021-09-02T15:52:06Z,"Host : Microsoft Windows [version 10.0.19042.1165]
Guest : Windows 7

step 1 : (OK)
- run the guest VM
- plug USB devices

step 2a : (OK)
- switch off the VM
- un-plug USB devices

step 2b : (HOST BSOD and reset)
- un-plug USB devices while VM is still running

",ManWithNoName
20533,Network card error after deleting Virtual Machine,Windows,Linux,VirtualBox 6.1.26,2021-09-03T14:34:08Z,2021-09-03T14:34:08Z,"Hi,

As I wrote in the summary, after removing a VM from VirtualBox I can not change my network properties in the host for all networks cards I have.

I'm hosting from a Windows PC with Windows 10 Pro.

The error appears after removing a Debian VM. Just to notice it did the same issue with a CentOS VM, and to go back to normal it was necessary to execute a factory reset on my PC.

Also it is not possible to desactivate or reactivate the connection.

My computer is my principal tool to work and I frequently use this parameters.

Thanks for any help and solution. ",ddag
20534,Win server 2008 does not autostart after update to 6.1.22_Ubuntur144080,Linux,Windows,VirtualBox 6.1.22,2021-09-06T08:47:03Z,2021-09-06T08:47:03Z,"L.S,

We have updated several Linux hosts and Virtualbox is updated in that proces to 6.1.22_Ubuntur144080. Win 10 vm's autostart, but win 2008 server vm's fail to autostart after the update. This is noted for all the Linux hosts (4) we have updated.

Regards,

August




",AO
20524,VirtualBox crashes with FreeBSD guest,Windows,BSD,VirtualBox 6.1.24,2021-09-06T20:17:55Z,2021-09-06T20:17:55Z,See attached log.,DeGarden
16704,VBox Manager: Make the double click Start action configurable,all,all,VirtualBox 5.1.20,2021-09-06T21:32:35Z,2021-09-06T21:32:35Z,"Upon a double click on a VM, the VM starts in ""normal"" mode. It would be a great enhancement if this default start mode could be configured to be one of
- normal
- detachable
- detached
Currently, this can only be done in the context menu or with a keyboard shortcut.",Martin Binder
20531,The CentOs screen is getting stuck after starting it,Windows,other,VirtualBox 6.1.18,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
20467,Guest freeze after restoring from saved state,Windows,Linux,VirtualBox 6.1.24,2021-09-08T00:29:58Z,2021-09-08T00:29:58Z,"Saved guest state, left it alone over night.  Resumed from saved state the next morning, guest ran for a few minutes then froze.  Required power off to recover.

Version 6.1.22

00:00:41.067179 TM: cTSCTicksPerSecond=0x7de2930c (2 112 000 780) enmTSCMode=1 (VirtTscEmulated) (state load)
00:00:41.067225 GIM: KVM: VCPU  0: Enabled system-time struct. at 0x0000000070e01000 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x3e6641e77 uVirtNanoTS=0x1d8b90e9e TscKHz=2112000
00:00:41.067391 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
00:00:41.067504 GIM: KVM: VCPU  1: Enabled system-time struct. at 0x0000000070e01040 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44d7575f1 uVirtNanoTS=0x209861cac TscKHz=2112000
00:00:41.067524 GIM: KVM: VCPU  2: Enabled system-time struct. at 0x0000000070e01080 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44ddad072 uVirtNanoTS=0x209b619f2 TscKHz=2112000
00:00:41.067536 GIM: KVM: VCPU  3: Enabled system-time struct. at 0x0000000070e010c0 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44e3dffac uVirtNanoTS=0x209e5104d TscKHz=2112000
00:00:41.067695 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) (restore)
00:00:41.067710 RTC: Stopped the periodic timer (restore)
00:00:41.067746 HGCM: Restoring [VBoxGuestPropSvc]
00:00:41.068417 HGCM: Restoring [VBoxGuestControlSvc]
00:00:41.068625 HGCM: Restoring [VBoxSharedFolders]
00:00:41.069102 HGCM: Restoring [VBoxDragAndDropSvc]
00:00:41.069378 HGCM: Restoring [VBoxSharedClipboard]
00:00:41.069740 Shared Clipboard: New Clipboard API enabled
00:00:41.073974 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)
00:00:41.074187 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:00:41.074218 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.074239 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074248 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074260 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:00:41.074269 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.074279 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074287 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074319 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074328 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074339 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074347 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.075353 E1000#0: Interrupt attempts: 0
00:00:41.075369 E1000#0: Interrupts raised : 0
00:00:41.075377 E1000#0: Interrupts lowered: 0
00:00:41.075384 E1000#0: ICR outside ISR   : 0
00:00:41.075391 E1000#0: IMS raised ints   : 0
00:00:41.075398 E1000#0: Interrupts skipped: 0
00:00:41.075405 E1000#0: Masked interrupts : 0
00:00:41.075412 E1000#0: Early interrupts  : 0
00:00:41.075419 E1000#0: Late interrupts   : 0
00:00:41.075426 E1000#0: Lost interrupts   : 0
00:00:41.075432 E1000#0: Interrupts by RX  : 0
00:00:41.075439 E1000#0: Interrupts by TX  : 0
00:00:41.075446 E1000#0: Interrupts by ICS : 0
00:00:41.075453 E1000#0: Interrupts by RDTR: 0
00:00:41.075460 E1000#0: Interrupts by RDMT: 0
00:00:41.075467 E1000#0: Interrupts by TXQE: 0
00:00:41.075474 E1000#0: TX int delay asked: 0
00:00:41.075481 E1000#0: TX delayed:         0
00:00:41.075488 E1000#0: TX delay expired:   0
00:00:41.075495 E1000#0: TX no report asked: 0
00:00:41.075502 E1000#0: TX abs timer expd : 0
00:00:41.075509 E1000#0: TX int timer expd : 0
00:00:41.075516 E1000#0: RX abs timer expd : 0
00:00:41.075523 E1000#0: RX int timer expd : 0
00:00:41.075530 E1000#0: TX CTX descriptors: 0
00:00:41.075536 E1000#0: TX DAT descriptors: 0
00:00:41.075543 E1000#0: TX LEG descriptors: 0
00:00:41.075550 E1000#0: Received frames   : 0
00:00:41.075557 E1000#0: Transmitted frames: 0
00:00:41.075564 E1000#0: TX frames up to 1514: 0
00:00:41.075577 E1000#0: TX frames up to 2962: 0
00:00:41.075586 E1000#0: TX frames up to 4410: 0
00:00:41.075593 E1000#0: TX frames up to 5858: 0
00:00:41.075600 E1000#0: TX frames up to 7306: 0
00:00:41.075607 E1000#0: TX frames up to 8754: 0
00:00:41.075614 E1000#0: TX frames up to 16384: 0
00:00:41.075621 E1000#0: TX frames up to 32768: 0
00:00:41.075628 E1000#0: Larger TX frames    : 0
00:00:41.075635 E1000#0: Max TX Delay        : 0
00:00:41.075646 E1000#1: Interrupt attempts: 0
00:00:41.075653 E1000#1: Interrupts raised : 0
00:00:41.075660 E1000#1: Interrupts lowered: 0
00:00:41.075667 E1000#1: ICR outside ISR   : 0
00:00:41.075674 E1000#1: IMS raised ints   : 0
00:00:41.075681 E1000#1: Interrupts skipped: 0
00:00:41.075688 E1000#1: Masked interrupts : 0
00:00:41.075694 E1000#1: Early interrupts  : 0
00:00:41.075701 E1000#1: Late interrupts   : 0
00:00:41.075708 E1000#1: Lost interrupts   : 0
00:00:41.075715 E1000#1: Interrupts by RX  : 0
00:00:41.075722 E1000#1: Interrupts by TX  : 0
00:00:41.075729 E1000#1: Interrupts by ICS : 0
00:00:41.075736 E1000#1: Interrupts by RDTR: 0
00:00:41.075743 E1000#1: Interrupts by RDMT: 0
00:00:41.075749 E1000#1: Interrupts by TXQE: 0
00:00:41.075756 E1000#1: TX int delay asked: 0
00:00:41.075763 E1000#1: TX delayed:         0
00:00:41.075770 E1000#1: TX delay expired:   0
00:00:41.075777 E1000#1: TX no report asked: 0
00:00:41.075784 E1000#1: TX abs timer expd : 0
00:00:41.075790 E1000#1: TX int timer expd : 0
00:00:41.075797 E1000#1: RX abs timer expd : 0
00:00:41.075804 E1000#1: RX int timer expd : 0
00:00:41.075811 E1000#1: TX CTX descriptors: 0
00:00:41.075818 E1000#1: TX DAT descriptors: 0
00:00:41.075825 E1000#1: TX LEG descriptors: 0
00:00:41.075831 E1000#1: Received frames   : 0
00:00:41.075838 E1000#1: Transmitted frames: 0
00:00:41.075845 E1000#1: TX frames up to 1514: 0
00:00:41.075852 E1000#1: TX frames up to 2962: 0
00:00:41.075859 E1000#1: TX frames up to 4410: 0
00:00:41.075866 E1000#1: TX frames up to 5858: 0
00:00:41.075873 E1000#1: TX frames up to 7306: 0
00:00:41.075879 E1000#1: TX frames up to 8754: 0
00:00:41.075886 E1000#1: TX frames up to 16384: 0
00:00:41.075893 E1000#1: TX frames up to 32768: 0
00:00:41.075900 E1000#1: Larger TX frames    : 0
00:00:41.075907 E1000#1: Max TX Delay        : 0
00:00:41.075917 E1000#2: Interrupt attempts: 0
00:00:41.075924 E1000#2: Interrupts raised : 0
00:00:41.075931 E1000#2: Interrupts lowered: 0
00:00:41.075938 E1000#2: ICR outside ISR   : 0
00:00:41.075945 E1000#2: IMS raised ints   : 0
00:00:41.075952 E1000#2: Interrupts skipped: 0
00:00:41.075959 E1000#2: Masked interrupts : 0
00:00:41.075966 E1000#2: Early interrupts  : 0
00:00:41.075972 E1000#2: Late interrupts   : 0
00:00:41.075979 E1000#2: Lost interrupts   : 0
00:00:41.075986 E1000#2: Interrupts by RX  : 0
00:00:41.075993 E1000#2: Interrupts by TX  : 0
00:00:41.076000 E1000#2: Interrupts by ICS : 0
00:00:41.076007 E1000#2: Interrupts by RDTR: 0
00:00:41.076013 E1000#2: Interrupts by RDMT: 0
00:00:41.076020 E1000#2: Interrupts by TXQE: 0
00:00:41.076027 E1000#2: TX int delay asked: 0
00:00:41.076034 E1000#2: TX delayed:         0
00:00:41.076041 E1000#2: TX delay expired:   0
00:00:41.076047 E1000#2: TX no report asked: 0
00:00:41.076054 E1000#2: TX abs timer expd : 0
00:00:41.076061 E1000#2: TX int timer expd : 0
00:00:41.076068 E1000#2: RX abs timer expd : 0
00:00:41.076075 E1000#2: RX int timer expd : 0
00:00:41.076081 E1000#2: TX CTX descriptors: 0
00:00:41.076088 E1000#2: TX DAT descriptors: 0
00:00:41.076095 E1000#2: TX LEG descriptors: 0
00:00:41.076102 E1000#2: Received frames   : 0
00:00:41.076109 E1000#2: Transmitted frames: 0
00:00:41.076116 E1000#2: TX frames up to 1514: 0
00:00:41.076122 E1000#2: TX frames up to 2962: 0
00:00:41.076129 E1000#2: TX frames up to 4410: 0
00:00:41.076136 E1000#2: TX frames up to 5858: 0
00:00:41.076143 E1000#2: TX frames up to 7306: 0
00:00:41.076150 E1000#2: TX frames up to 8754: 0
00:00:41.076157 E1000#2: TX frames up to 16384: 0
00:00:41.076165 E1000#2: TX frames up to 32768: 0
00:00:41.076172 E1000#2: Larger TX frames    : 0
00:00:41.076179 E1000#2: Max TX Delay        : 0
00:00:41.076189 E1000#3: Interrupt attempts: 0
00:00:41.076197 E1000#3: Interrupts raised : 0
00:00:41.076204 E1000#3: Interrupts lowered: 0
00:00:41.076211 E1000#3: ICR outside ISR   : 0
00:00:41.076218 E1000#3: IMS raised ints   : 0
00:00:41.076225 E1000#3: Interrupts skipped: 0
00:00:41.076231 E1000#3: Masked interrupts : 0
00:00:41.076238 E1000#3: Early interrupts  : 0
00:00:41.076245 E1000#3: Late interrupts   : 0
00:00:41.076252 E1000#3: Lost interrupts   : 0
00:00:41.076259 E1000#3: Interrupts by RX  : 0
00:00:41.076283 E1000#3: Interrupts by TX  : 0
00:00:41.076290 E1000#3: Interrupts by ICS : 0
00:00:41.076297 E1000#3: Interrupts by RDTR: 0
00:00:41.076304 E1000#3: Interrupts by RDMT: 0
00:00:41.076311 E1000#3: Interrupts by TXQE: 0
00:00:41.076318 E1000#3: TX int delay asked: 0
00:00:41.076325 E1000#3: TX delayed:         0
00:00:41.076332 E1000#3: TX delay expired:   0
00:00:41.076339 E1000#3: TX no report asked: 0
00:00:41.076346 E1000#3: TX abs timer expd : 0
00:00:41.076352 E1000#3: TX int timer expd : 0
00:00:41.076359 E1000#3: RX abs timer expd : 0
00:00:41.076366 E1000#3: RX int timer expd : 0
00:00:41.076373 E1000#3: TX CTX descriptors: 0
00:00:41.076380 E1000#3: TX DAT descriptors: 0
00:00:41.076387 E1000#3: TX LEG descriptors: 0
00:00:41.076394 E1000#3: Received frames   : 0
00:00:41.076401 E1000#3: Transmitted frames: 0
00:00:41.076408 E1000#3: TX frames up to 1514: 0
00:00:41.076414 E1000#3: TX frames up to 2962: 0
00:00:41.076421 E1000#3: TX frames up to 4410: 0
00:00:41.076428 E1000#3: TX frames up to 5858: 0
00:00:41.076435 E1000#3: TX frames up to 7306: 0
00:00:41.076442 E1000#3: TX frames up to 8754: 0
00:00:41.076449 E1000#3: TX frames up to 16384: 0
00:00:41.076456 E1000#3: TX frames up to 32768: 0
00:00:41.076462 E1000#3: Larger TX frames    : 0
00:00:41.076469 E1000#3: Max TX Delay        : 0
00:00:41.077169 Changing the VM state from 'LOADING' to 'SUSPENDED'
00:00:41.077264 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:41.077634 NAT: Link down
00:00:41.077688 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:41.077711 Console: Machine state changed to 'Running'
00:00:41.413451 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.468266 VMMDev: Guest Log: 05:23:50.740142 control  Session 0 is about to close ...
00:00:41.496511 VMMDev: Guest Log: 05:23:50.765559 control  Stopping all guest processes ...
00:00:41.520448 VMMDev: Guest Log: 05:23:50.785749 control  Closing all guest files ...
00:00:41.538332 VMMDev: Guest Log: 05:23:50.809370 control  vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:41.553963 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:00:41.562333 VMMDev: Guest Log: 19:58:06.188434 timesync vgsvcTimeSyncWorker: Radical host time change: 52 465 401 000 000ns (HostNow=1 626 897 486 173 000 000 ns HostLast=1 626 845 020 772 000 000 ns)
00:00:41.603543 VD#0: DEK is missing
00:00:41.605905 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
00:00:41.606263 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:00:41.682916 PDMR3Suspend: 76 471 817 ns run time
00:00:41.682942 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:00:41.682963 Console: Machine state changed to 'Paused'
00:00:41.683147 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message=""VD: The DEK for this disk is missing""
00:00:41.901987 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.906646 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.914961 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.924632 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:41.932803 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:55.433857 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:55.437234 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:55.437266 Console: Machine state changed to 'Running'
00:00:55.437702 VUSB: Attached 'HidMouse' to port 1 on RootHub#1 (FullSpeed)
00:00:55.442756 GUI: 2D video acceleration is disabled
00:00:55.442897 GUI: HID LEDs sync is enabled
00:00:55.448377 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:55.454667 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:55.461637 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:56.250340 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000f820000 w=1920 h=1027 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0
00:00:58.156594 NAT: Link up
00:00:58.165917 NAT: DNS#0: 192.168.1.1
00:01:00.002777 NAT: IPv6 not supported
00:01:00.012749 NAT: DHCP offered IP address 10.0.4.15
00:01:05.442153 VMMDev: Guest Log: 19:58:16.316090 timesync vgsvcTimeSyncWorker: Radical guest time change: 52 465 497 062 000ns (GuestNow=1 626 897 496 316 076 000 ns GuestLast=1 626 845 030 819 014 000 ns fSetTimeLastLoop=true )
",gkcgareth
20457,Guest crashes when unpausing,Windows,Linux,VirtualBox 6.1.22,2021-09-08T00:30:33Z,2021-09-08T00:30:33Z,"Guest was paused for a long time (overnight).  When unpaused, it ran for a few seconds then locked up.  Required a hard reset.

Guest logs attached.

VirtualBox Graphical User Interface
Version 6.1.22 r144080 (Qt5.6.2)
Copyright © 2021 Oracle Corporation and/or its affiliates. All rights reserved.",gkcgareth
20537,Guest process stops responding when host suspends and guest is running a docker container,Windows,Linux,VirtualBox 6.1.26,2021-09-08T00:32:05Z,2021-09-08T00:32:05Z,"VirtualBox version 6.1.26
Host OS is Windows 10 Prod 19043.1202
Guest OS is Ubuntu 21.04 (with latest updates applied)

To reproduce:
 - On a windows 10 host, create a Linux guest.
 - Install docker on the guest, and start one or more containers
 - Suspend the host
 - Resume the host - Guest will freeze within seconds

When I suspend the host the guest normally comes back fine, however whenever a docker container is running, it does not.
I've seen it with different docker stacks, but haven't exhaustively if it's any one in particular - seems to be just whenever one is running.",gkcgareth
20390,Guest hung after host resumes from sleep,Windows,Linux,VirtualBox 6.1.22,2021-09-08T00:32:39Z,2021-09-08T00:32:39Z,"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

When I suspend and resume the host, the guest is no longer responsive, requires a forced power off and complete restart of the guest.  Similar to 20270, but the trick of pausing and resuming doesn't work.

Used to work fine, I suspect it started with a host OS update.  Happened under 6.1.17 too.

Logs attached.",gkcgareth
20539,E_FAIL (0x80004005) after Launch,Windows,Linux,VirtualBox 6.1.26,2021-09-08T07:35:16Z,2021-09-08T07:35:16Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
20535,"W64 host, Ubuntu guest: mouse cursor corrupt in Terminal on secondary 4K screen",Windows,Linux,VirtualBox 6.1.26,2021-09-08T09:41:15Z,2021-09-08T09:41:15Z,"System details at the end.

Whether the VB container window is sized very small or large, there is a glitch with the mouse cursor inside Terminal windows in the guest OS.

Note that there are two 4K monitors attached. **This bug only appears if the VB container window is on one of the secondary monitors.** If it is on the laptop's main screen, the cursor simply disappears when typing, which I believe is the desired behaviour.

The specific issue is as follows: once the mouse cursor is moved inside the Terminal window, it is at first correct. However, type as much as one character, and it turns into a block of glitched data, 8-10 characters wide and one character tall. If the cursor is moved even a tiny amount, it returns to normal, until the user types once again.

I've attached images of the before and after effects within a small VB container window.

It appears that when the cursor is being removed, the underlying pixels are being bitblt'ed from the wrong part of video memory.

**System details**

VB 6.1.26 build 145957 (Qt5.6.2)

Host:
* Edition	Windows 10 Pro
* Version	20H2
* Installed on	‎06/‎07/‎2021
* OS build	19042.1165
* Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
* Ubuntu 64 bit Hirsute, all patches current
* VM Additions installed.

PC:
* Processor	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz   2.71 GHz
* Installed RAM	8.00 GB (7.88 GB usable)
System type	64-bit operating system, x64-based processor

Config:
* HP EliteBook 840 G4
* 3 GiB RAM assigned to guest
* Main screen: 1080p inbuilt
* Secondary screens:
 * 2x 28"" 4K
 * full resolution
 * 125% scaling
 * both connected using DisplayPort.",JonAtFS
14374,Network adapters not working after host returns from sleep Win 7 host Linux Mint 17.2 guest,Windows,Linux,VirtualBox 5.0.0,2021-09-09T03:59:02Z,2021-09-09T03:59:02Z,"Host is Dell E7440 laptop running Windows 7 SP1 Enterprise 64 bit. VirtualBox version 5.0.0 r101573. Wireless NIC is Intel Dual Band AC 7260 as a bridged adapter virtualized as Intel PRO 1000 MT desktop. Guest is ""Linux Mint 17.2 Rafaela built on Ubuntu 14.04.2 LTS Trusty Tahr and kernel is 3.13.0-37-generic. The guest additions have been installed

Issue started appearing after the 5.0 update recently. After my host has returned from sleep my network connection is lost on my guest until i completely shutdown. I have tried switching the host adapter to other adapters. Disconnecting and reconnecting the cable in Devices>Network Settings. I have also tried just rebooting. The VM has to be completely powered off and back on for the adapter to work again. The network connection icon in the task bar stays discontented the entire time. No error message is given at any time.",Johnny Kilo
20543,macOS Guest Additions do not include mount.vboxsf,Mac OS X,OSX Server,VirtualBox 6.1.26,2021-09-13T10:47:16Z,2021-09-13T10:47:16Z,"When successfully installing the Darwin guest additions, the mount.vboxsf tool is not included, while there is a source tree available and seemingly being built.

Steps to reproduce:
- Disable all security on macOS Catalina guest
- Insert the Guest Additions ISO
- Install Guest Additions
- `mount -t vboxsf VboxShared /Users/Shared/Host` result in a File Not Found error because /Library/Filesystems/vboxsf.fs does not exist

I also checked the contents of the .pkg and as far as I can tell, it does not contain any tools for mounting file systems. The source tree on the other hand does contain some kind of implementation in src/Vbox/Additions/darwin/VboxSF, which I unfortunately can't seem to manage to build because the build system does not seem to be compatible with Xcode 12.

As for some context:
I am trying to set up a macOS Catalina build system to build Unreal Engine games on a Big Sur (and Windows) host. The VM should have a minimally sized main disk and should share the actual build tree with the host. I already have all this set up, using SMBFS to share the build tree and it is working ok, but network performance is only about 30MB/s, so builds take forever.

Therefore I am trying to mount shared folders in the macOS 10.15 Catalina guest in hopes they will give me better performance, somewhere in the range of the 400MB/s, the virtual disk in the VM provides. I already installed the guest additions successfully, but as far as I can see, they are missing the mount.vboxsf tool to actually mount the shared folders. I also tried to unpack the VboxDarwinAdditions.pkg, contained on the additions iso of multiple VirtualBox version, but the tool simply isn't there and is not being created. As per the source tree, there should be a tool available to mount the shared folders though, so I am guessing this is a bug in the build environment.
",HI_Paul
20544,loosing control of vm with accessing built-in mic on Windows 10 guest,Mac OS X,Windows,VirtualBox 6.1.26,2021-09-13T17:05:15Z,2021-09-13T17:05:15Z,"Case 1:
The VM was freeze at opening settings app and then browsing settings>systems>sound.
Case 2:
The VM was freeze while doing dictation by cortana.

This issue is occurred on Virtualbox 6.1.26 for Mac OS X, only.
This issue is not only audio input failure, but all responses from VM of Windows guest have also stopped from the time in while the apps has been accessing to mic input. 
The logs had been terminated in a moment which this issue was occured.
It's a very serious and urgent issue.
The only way to get out of this state is to kill the VM process from the host OS.",apo2
20546,Guest suspended with DiskFull error when using fixed size VDI,Linux,Linux,VirtualBox 6.1.26,2021-09-14T06:52:48Z,2021-09-14T06:52:48Z,"VirtualBox guest with fixed size VDI file is suspended when the host runs low on disk space.
Fixed size VDI files should never trigger a disk full condition as they are a fixed preallocated size that will never expand.

VirtualBox build 146314
Host: Fedora Linux 33
Guest Fedora Linux 34
Log File Info:
VD#1: Host disk full
VM: Raising runtime error 'DrvVD_DISKFULL' (fFlags=0x6)
Console: VM runtime error: fatal=false, errorID=DrvVD_DISKFULL message=""Host system reported disk full. VM execution is suspended. You can resume after freeing some space""

VBoxManage showmediuminfo disk ...
Storage format: VDI
Format variant: fixed default
Capacity:       66560 MBytes
Size on disk:   66562 MBytes",RP15873
20089,Windows 10 Guest slow down when a screen grabber is active on the host,Linux,Windows,VirtualBox 6.1.16,2021-09-14T07:34:21Z,2021-09-14T07:34:21Z,"When a screen grabber (like Teamviewer, MS Teams screen sharing, Zoom screen sharing etc.) is active on the host machine (Linux Mint 20), the Guest VM will slowing down more and more and finally freeze. 

This is reproduceble in relation with screen grabbing. When a regulary Teamviewer or Teams session is active, the Guest is usable normally. From the moment when I activate any screen sharing, the guest is affected immediately.

At the moment the screen grabbing is ended, the guest is usable normally again.",Codehunter
20550,Failed to save machine state,Windows,other,VirtualBox 6.1.26,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
20549,installing virtual box on Linux  5.10.0-kali9-amd64,Linux,other,VirtualBox 6.1.26,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
20540,E_FAIL (0x80004005) after Launch,Windows,Linux,VirtualBox 6.1.26,2021-09-16T09:34:36Z,2021-09-16T09:34:36Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
20551,Kernel driver not installed (rc=-1908),Linux,Windows,VirtualBox 6.1.26,2021-09-16T15:13:23Z,2021-09-16T15:13:23Z,"after upgrade centos to newest version (and update virtualbox 6.1.26) I had this error when starting virtuals: ""
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 
""
after use ""sudo /sbin/vboxconfig"" 
I have this:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
(log from file attached)
",oszymanski
20547,Promiscuous Mode Does Not Work on macOS 11.5.2,Mac OS X,Linux,VirtualBox 6.1.26,2021-09-16T15:26:56Z,2021-09-16T15:26:56Z,"Regardless of the network adapter type and other settings, selecting Bridge Adapter and either Allow VMs or Allow All for the Promiscuous Mode does not provide the expected result. Linux VMs have no issues passing network traffic normally, but if a bridge is setup incoming packets do not reach the VM. I see the packets generated on the VirtualBox Guest VM and nested VMs on the VM interfaces, the Mac, and my router, but the return traffic does not make it to the VirtualBox Guest VMs. I found the following ticket that has gone ignored for many years with some information that may help isolate the issue.

https://www.virtualbox.org/ticket/10811

This also fails running VirtualBox as root.

I can say that I'm able to enable Promiscuous Mode in other software without issue, so the issue is not macOS or my setup.

Given that this issue is quite old, my guess is we have one of two issues since some change in an old macOS and every release since. It's broken or there are added steps to make it work.

If you're not going to support Promiscuous Mode, then please remove the options so people don't waste time troubleshooting something that is not going to work.

If more setup is required to make this work with VirtualBox, then please provide the documentation necessary.",Myrddyn
20290,"VB Manager GUI ""move"" machine command",Windows,all,VirtualBox 6.1.18,2021-09-17T08:27:38Z,2021-09-17T08:27:38Z,"use VB on my laptop and have numerous machines for projects with engneering software.
I want to keep only the current project VM on my laptop SSD (for speed and disc space reasons) and keep the other ones accessible on an external USB drive .
So I attach 5TB external HD to the laptop and create a ""machines"" folder.

I use the ""move"" command in the GUI (right-click on the VM) and can select slect basically any drive and folder and pont it to my external HD machine folder.

However the results are mixed and the feature is not working.

A folder for the machine is created but only the VM vbox file and the log folder is moved to the destination. The VDI and snapshot folder remain on Original location :cry:

If I move the VM on the same internal HD drive letter to another location it seems to work better and shifts also the VDI and snapshots.

Background why I need the move feature:
My problem is that I want to shift a VM (with it's VDI) which all reside in a folder (.vbox, .VDI, the Snapshot and log subfolders) and move it to another location either on my laptop or to an external HD over the network to a library (NAS). Reason behind it is that I work with many VM and I can't have all of them in my laptops SSD at the same time. I wanted to use the ""move"" feature from the VB GUI to move a complete VM (including its VDI, snapshots) to an external hard drive and keep those VM that I don't need immediately or only for a quick test on another drive (HDD) and easily move them between my internal SSD and an external drive. The GUI behaves inconsistent when it comes to applying the command on the same (internal) drive or on an external USB drive or a network drive. It doesn't make sense to use the ""move"" command when it only moves the VM definition and leaves the VDI in the old location or even worse when it only partially moves the files leaving some in the old location and some in then new location.
What I figured out is that apparently due to the way the move is implemented in the GUI it works (almost(!!) all the time) within the local drive because only the path informations needs to be updatted on the hard drive file system and files are not physically moved (copied and then deleted from old location). By selecting an external drive for the move command it works ""partially"" but mostly some files are not properly moved.
",Andreas S
20483,"Virtubox crashes when the vbox window was resized. Host Windows 10 Pro (64-bit), guest Debian GNU/Linux",Windows,Linux,VirtualBox 6.1.22,2021-09-17T09:49:46Z,2021-09-17T09:49:46Z,"Host: 
Edition	Windows 10 Pro (64-bit)
version	21H1
Installed	‎2020/‎12/‎16
OS build	19043.1110
Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
Debian GNU/Linux 

When I try to resize the VBox window under Windows 10 Pro (64-bit)  by grabbing the right edge and tried to shrink the width, VBox crashed.

It seems it encountered exception.
Funny, I see screen count changed or something to that effect in the attached log.
I only have a single physical display.

TIA
",ci-zephyurus
20167,Mouse pointer in MS Office is not working correctly.,Windows,Windows,VirtualBox 6.1.18,2021-09-18T02:53:27Z,2021-09-18T02:53:27Z,"Microsoft uses special mouse pointers in MS Office (Excel, Word, Access). These mouse pointers don't work since VirtualBox 6.1.x. It has worked in VB 5.2 and maybe in 6.0 (not sure).
I assume it is a problem of the guest additions for Windows.
I am using Windows 10 on the host and Windows XP with Office 2003 in the VB guest with a scale factor of 1.2.",PeterE
20568,6.1.26 Memory can't be written,Windows,Windows,VirtualBox 6.1.26,2021-09-19T15:00:52Z,2021-09-19T15:00:52Z,Can't repeat it. It was sudden during pausing VM.,MikhailRokhin
19153,VM crashes - Virtualbox vm quit unexpectedly,Mac OS X,other,VirtualBox 6.0.14,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
20570,"Key ""accent grave"" not received in guest",Linux,Windows,VirtualBox 6.1.26,2021-09-20T12:10:30Z,2021-09-20T12:10:30Z,"When I run a Windows 10 guest on a Fedora 34 host, the ""accent grave"" key is not received at all in the guest. However, if I run the guest headless and connect over RDP using xfreerdp directly from my Fedora 34 host, the ""accent grave"" key works like normal. So something is wrong with the VirtualBox guest window on this platform.

    > vboxmanage --version
    6.1.26_RPMFusionr145957

    > uname -a
    Linux xxxxx.xxxxx.xxx 5.12.14-300.fc34.x86_64 #1 SMP Wed Jun 30 18:30:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux",Byron
20571,"Pressing ""Maximize"" button causing error, while the state starts saving",Windows,Windows,VirtualBox 6.1.26,2021-09-20T18:01:20Z,2021-09-20T18:01:20Z,"Pressing the ""Maximize"" button (in dropdown panel), when the state starts saving, in full screen mode, causes an error and an abnormal termination of the virtual machine.

Often trying to minimize the virtual machine, when the state starts saving, I mistakenly click the adjacent ""Maximize"" button, and VM crashed.",astverskoy
20405,Virtual Machine crashes when dragging link,Windows,Linux,VirtualBox 6.1.22,2021-09-20T18:21:06Z,2021-09-20T18:21:06Z,"Hello, I was using a virtual machine when i accidentally dragged a link inside the virtual machine. The virtual machine got aborted by virtualbox. it also gave a memory read error. I think the reason why it gave that error is because virtualbox is not checking if what the user drags inside of the virtual machine is a file or directory so it tries to read it then because it is not a file it gives a read error. So i would suggest you guys let virtualbox check if what the user drags inside the virtual machine is a file or directory.
So i would like to report this issue to help improve virtualbox.
If i could contribute through code it would a dream.
[[Image(https://media.discordapp.net/attachments/470253814235136044/854380201428516894/unknown.png?width=722&height=406)]]
[[Image(https://media.discordapp.net/attachments/470253814235136044/854380211632865297/unknown.png?width=722&height=406)]]
If you look above you can see the virtual machine has been terminated or aborted.",MemoryJack
20569,Cannot interact with VM while settings are open,Windows,all,VirtualBox 6.1.26,2021-09-21T19:56:21Z,2021-09-21T19:56:21Z,"Often it is useful to interact with the VM window while configuring settings.

For example, while setting up NAT forwarding, may want to execute ""ifconfig"" in the guest to retrieve guest IP.

Right now, the settings window forces itself on top and prevents interacting with the guest. This means there is a common pattern of navigating to a settings page, realizing one has forgotten the info one needs, then having to close all windows, get the info from the guest, and retrace steps back to the appropriate settings window.",grapereader
20553,VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension,Windows,Linux,VirtualBox 6.1.26,2021-09-22T04:23:30Z,2021-09-22T04:23:30Z,"hi Team,

While importing the OVA file into Virtual box, an error in being popped up with ""VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension""
I already verified, of having the disk with its proper extensions in .ovf file.
But still having the issues whereas when I import the same ova file in VMware, it did worked at its pace and can start the VM.
Please help on this asap ?",Sanchit Gupta
20566,VirtualBoxVM.exe: unknown software exception (0x80000003) on AMD FX-8300,Windows,all,VirtualBox 6.1.26,2021-09-22T05:57:33Z,2021-09-22T05:57:33Z,"My computer CPU is AMD FX-8300.

When I open a VM and press ""Start"" button, the VirtualBoxVM.exe will stop after 2 seconds, and Windows pops up an ""Application Error"" dialog, which wrote:

""The exception unknown software exception (0x80000003) occurred in the application at location 0xac502432.""

VirtualBox is totally unusable on AMD FX-8300.
But same computer, different CPU: AMD Phenom II X4 945, VirtualBox works fine.",VB6
20552,VMSVGA extremely laggy keyboard input for Linux guests,Linux,Linux,VirtualBox 6.1.26,2021-09-24T06:53:29Z,2021-09-24T06:53:29Z,"Pretty much all Linux guests with this video adapter have an extremely laggy and random keyboard input: while you're typing in any graphical terminal sometimes what you're typing instantly shows on the screen, sometimes there's a random delay for up to three seconds.

It's annoying and maddening.

Host OS: Fedora 33, Linux 5.14.3[[BR]]
Environment: XFCE with '''no''' compositing[[BR]]
CPU: Ryzen 7 5800X[[BR]]
Guest OS: any modern Linux OS without 3D acceleration

Changing the amount of video memory from default 16MB to 128MB makes the issue less pronounced but it's still there.

VBoxSVGA is more or less free from this issue. Keyboard input is not perfect (there's quite a considerable input lag) but at least it's not as bad as with VMSVGA.",Artem S. Tashkinov
20575,"Installer must never rely on trash, left by previous version",Windows,other,VirtualBox 6.1.26,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
20576,Installer must be able to update VBoxSDS windows service entry,Windows,other,VirtualBox 6.1.26,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
20578,Error Guest Addiction Windows 7 does not load drivers,Windows,Windows,VirtualBox 6.1.26,2021-09-27T10:57:00Z,2021-09-27T10:57:00Z,"Good morning, recently I have tried to put usb in my virtual machine with windows 7, trs install all the compponentes (guest aditions and others) I get error of drivers in windows 7 I can not find solution on the internet or way to install drivers",Juanraro
20580,Accessibility. Inaccessible shut down virtual machine screen with screen readers enabeled,other,Windows,VirtualBox 6.1.26,2021-09-28T08:54:47Z,2021-09-28T08:54:47Z,"When navigating in the virtual machine shut down screen, 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. For example:
Save button
Shut down button.
Actual result:
Screen reader doesn't announce any elements, it keeps saying ""Unknown"" while tabbing, so it is impossible to shut down the virtual machine using the screen reader.
See standards and guides:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html",Vsevolod Popov
20529,VM crashes on copy text to clipboard,Windows,Windows,VirtualBox 6.1.26,2021-09-28T11:19:56Z,2021-09-28T11:19:56Z,"VM crashes frequently on x64 Windows (Win7 & Win10) guest running on x64 Windows 10 host on copy text to clipboard
x86 guest never crashes.",Alex_Locarus
16604,Plasma 5 screen scaling on 4K monitor causes Windows guest to be 1/4 size of window.,Linux,Windows,VirtualBox 5.1.16,2021-09-28T15:31:23Z,2021-09-28T15:31:23Z,"This is a very specific bug to KDE / Plasma 5.

I have a laptop with a 4K display. KDE / Plasma 5 are not yet suited to the resolution. To help with icon size I selected System Settings => Display and Monitor => Scaled Display (button) and set the scale to 2.0.

This doubled all my icons nicely, but within the Windows 10 VM, the graphics were scaled to half resolution on both axes, but were not scaled back up to fill the screen. Mouse clicking was difficult because they were based on the full size of the window but the graphics were 1/2 size.

This is a small issue as I just turned of the Plasma feature to fix VirtualBox. And since it limits display resolution, it's probably not a good fix for the small icons.
",Raydude
266,Process priority selectable...,other,other,VirtualBox 1.3.8,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
20583,Sudden failure,Windows,Windows,VirtualBox 6.1.26,2021-09-28T22:37:38Z,2021-09-28T22:37:38Z,"Échec de l'ouverture de session pour la machine virtuelle XP Virtuel.

The VM session was closed before any attempt to power it on.

Code d'erreur : E_FAIL (0x80004005)
Composant : SessionMachine
Interface : ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

",osmond
20584,Mutliple CPU's Stalls When Loading,Windows,other,VirtualBox 6.1.26,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
19795,Virtualbox VM (Windows or Linux) crashes on Mac OS Bigsur host,Mac OS X,all,VirtualBox 6.1.10,2021-09-30T04:28:40Z,2021-09-30T04:28:40Z,"When I try to open a VM (does not matter if Windows or Linux), the error occur

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.",hoshikawa2
20581,Accessibility. Inaccessible shut down virtual machine screen with screen readers enabeled.,Windows,other,VirtualBox 6.1.26,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
20586,VirtualBox additions: VMSVGA display is not resizable,other,other,VirtualBox 6.1.26,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
20587,Critical error while running virtual machine,Windows,Windows,VirtualBox 6.1.26,2021-10-01T12:19:57Z,2021-10-01T12:19:57Z,"Error message is appearing on trying to start virtual machine: Critical error has occurred while running the virtual machine and the machine execution has been stopped.
",SUNNY25
20538,Virtualbox 6.1.26 and current 6.1.27 not installable and working on my Windows 11 22249,Windows,all,VirtualBox 6.1.26,2021-10-01T13:34:12Z,2021-10-01T13:34:12Z,"Possibly related: #20536
Since after well awaited and beloved update to 22249 pre_release, is the error with the Host-Only Adaptor (Filter Error Message). And after deinstall no reinstall possible, sadly no message on rollback, but probably same issue.

After update with existing VM: VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Could remove and readd adaptor without error message, but no change.

This is, as you all know, very critical, as VMs running in my fixed Windows 11 for production might have a problem now, as Virtual Box not working on the same computer..",Delphi
20588,Guest OS startup crashes the VM,Windows,Linux,VirtualBox 6.1.26,2021-10-01T17:44:38Z,2021-10-01T17:44:38Z,"When I trying to start VM with RHEL7 it no longer can startup.
It crashing into ""Guru mediation"".
",xor2003
20132,Guest Windows XP x86 Does Not Shutdown with Serial Ports Enabled,Windows,Windows,VirtualBox 6.1.16,2021-10-02T09:33:32Z,2021-10-02T09:33:32Z,"Host is Windows 10 x64. Serial ports COM 1-4 are from PCI-E Moxa CP-144EL Series card running the version 3.00 driver. All COM ports are working properly on host OS.

Guest OS Windows XP x86 recognizes COM ports 1-4 through the Host Device port mode. Port path on !VirtualBox is set to the identical port on host PC. Communication with a connected device is successful.

Upon shutdown of guest OS the shutdown process hangs with:

{{{
00:05:15.665094 HostSerial#0: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665170 HostSerial#1: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665256 HostSerial#2: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665307 HostSerial#3: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
}}}

Host has to be rebooted afterwards or rarely BSOD error happens upon shutdown.",yordan
20590,Guest window size decreases on login (Linux),Linux,Linux,VirtualBox 6.1.26,2021-10-04T19:23:20Z,2021-10-04T19:23:20Z,"I had one OpenSuSE 15.2 guest machine unexpectedly go back to a resolution of 1024X768 after rebooting and logging in. I was able to click and drag the window to increase the display size to fix the issue.

Things that didn't work were:
using the display settings within the OS to set a resolution
Using the View menu to set Auto-resize Guest Display and then use the View menu to set the display size for Virtual Screen 1.
In both cases the screen would resize as expected but, after a reboot and logging in again the screen size would jump back to 2014X768. When 3D acceleration was turned off I could see that the screen size was initially at the selected size before jumping back to 1025X763. With 3D acceleration turned on I cannot see the jump.

3D acceleration was initially turned off. Turning it on didn't change the symptoms.
Using VMSVGA ",Patrick Headley
20589,"NAT TFTP: leading slash in path cause ""Access violation""",Windows,Linux,VirtualBox 6.1.26,2021-10-05T20:34:25Z,2021-10-05T20:34:25Z,"I was trying to boot Grub2 using the built-in NAT TFTP. However, after being successfully loaded by iPXE Grub fails to load the additional files (/boot/grub/i386-pc/normal.mod, etc.) printing: error: Access violation

Same error is returned by NAT TFTP when using a tftp client on a booted Gust OS when the requested path has a leading forward slash.

Workaround: switch to an alternative TFTP server on localhost:
{{{
VBoxManage modifyvm SLESInst --nattftpserver1 10.0.2.2
}}}
Steps to reproduce:

- Generate Grub dir without grub.cfg or vmlinuz/initrd (they're not needed for testing)
{{{
[root@reallin il]# grub-mknetdir --net-directory=/srv/tftp --subdir=/boot/grub -d /usr/lib/grub/i386-pc
Netboot directory for i386-pc created. Configure your DHCP server to point to /srv/tftp/boot/grub/i386-pc/core.0
}}}
- Copy the files to the default TFTPPrefix
{{{
cp -rT /srv/tftp/boot ~/.VirtualBox/TFTP/boot
}}}
- point the VBox DHCP server to the right file
{{{
# If I use leading slash here boot fails sooner
VBoxManage modifyvm MyVM --nattftpfile1=boot/grub/i386-pc/core.0
}}}
- Boot a guest from Network

Expected: Grub loads in ""Normal"" mode

Actual: Grub loads in ""Rescue"" mode.

Additional info:
{{{
[il@reallin ~]$ atftp 10.0.2.4
tftp> get boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp> get /boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp: error received from server <Access violation>
tftp: aborting
tftp> 
}}} 
",lfmeloman
20597,Running VBox in a VM that's running under VBox,other,other,VirtualBox 6.1.26,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
20598,Security & Privacy in MacOS doesn't give Oracle as option,Mac OS X,Windows,VirtualBox 6.1.26,2021-10-07T15:41:51Z,2021-10-07T15:41:51Z,"Attempted to install VBox 6.1.26 on macOS X 11.6 Big Sur. Initial install gave errors due to Security & Privacy. After going into Security & Privacy and uninstalling VBox due to kernel-driver-not-installed-rc-1908-error attempted another install. Oracle does not come up as option in Security & Privacy. Tried re-starting computer and installing 6.1.26, also 6.1.24 but installer says ""Installed Successfully"" even though Oracle won't come up in Security & Privacy during install and kernels are missing.",Rick Szerminski
20602,UI not working when Win10 User resize scale.,Windows,other,VirtualBox 6.1.26,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
20574,VBoxManage 'start --type headless' cannot be correctly closed by 'controlvm acpipowerbutton',Windows,Linux,VirtualBox 6.1.26,2021-10-12T17:41:27Z,2021-10-12T17:41:27Z,"After using: 
{{{
VBoxManage startvm CentOS7-1 CentOS7-2 CentOS7-3 --type headless
}}}
CentOS7-1, 2, 3 are individual vms created by meself and started correctly.

After using:
{{{
VBoxManage controlvm CentOS7-3 acpipowerbutton
}}}
The vm named CentOS7-3 should have been closed correctly.

But after using:
{{{
VBoxManage startvm CentOS7-3 --type headless
}}}
It fails and outputs as below:
{{{
Waiting for VM ""CentOS7-1"" to power on...
VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
}}}

you can find more detail infos in the topic I posted https://forums.virtualbox.org/viewtopic.php?f=3&t=103980

What's more, through log file named VBoxHardening.log.I find log file which is closed incorrectly lack two lines outputs comparing to log file which is closed correctly:
{{{
3fd0.3fd4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 604653 ms, the end);
3f98.3f9c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 605077 ms, the end);
}}}

Hope this additional msg can help pro devs to solve this problems.
Thx for devs attention and contributions!",Q2K3
20603,Accessibility. Audio driver closes when using the console linux screen reader in guest,all,Linux,VirtualBox 6.1.26,2021-10-12T18:34:12Z,2021-10-12T18:34:12Z,"When using a linux console screen reader ""espeakup"", audio driver in virtual machine can close at any time while this screen reader works.
As a result, a totally blind person can leave without speech during using the console mode in linux.
As the great example to demonstrate the issue can be installation of the textbased linux distros such as debian, arch and others.
Steps to reproduce:
1. Download the debian iso.
2. Create the new debian virtual machine.
3. After running the machine, enable the accessibility installation by pressing ""s"" then ""enter"" key. You will hear as espeakup says: ""select a language"".
More information on debian accessibility installation process is listed here:
https://wiki.debian.org/accessibility#Debian_installer_accessibility
4. Move between the listed variants with keys numpad 7 and numpad 9, these are espeakup's screen reader keys.
5. Try to continue the installation by following provided instructions.
Expected result:
The audio driver should not close while the espeakup console screen reader works.
Actual result:
Audio driver can close at absolutely any time. You can not predict this action. As the result, a totally blind user is not able to install the linux text based guest operating system to a virtual machine and he should restart the machine and start the whole process over.
Duplicate issue:
https://www.virtualbox.org/ticket/19322",Vsevolod Popov
20605,3D opengl with vulcan nvidia,Linux,other,VirtualBox 6.1.26,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
20366,Shared clipboard stops working on vm reboot when started headless => Fixed in SVN,Linux,Linux,VirtualBox 6.1.22,2021-10-15T08:49:38Z,2021-10-15T08:49:38Z,"my setup and testing:

Running Virtualbox 6.1.22 on Ubuntu Server 20.04 with extension pack.  Ubuntu is fully patched.  I connect via RDP to VM console.

If I start a VM headless, shared clipboard works without issues.  Once I reboot the VM, shared clipboard stops working.

I have tested a Windows 10 VM and Mint Mate VM and both have the same issue.

I tested the freerdp client (compiled the latest source) and the Microsoft RDP client and get the same results.


I also installed Mint Mate on my test PC, then VirtualBox on that, and get the same result if I start the vm using vboxheadless.

I have attached log file from a test vm.",thedisbo1125
19523,Host audio not working after launching the guest,Mac OS X,Windows,VirtualBox 6.1.6,2021-10-15T08:51:59Z,2021-10-15T08:51:59Z,"I have an issue where the host audio disappears/doesn't work after the guest is launched.

I have tried disabling the guest audio (VM setting no audio), and full audio from the VM settings, but this makes no difference. During the boot, the audio for the host disappears. I've booted with the guest extensions installed and uninstalled, both exhibit the same outcome. Host is macOS Catalina (10.15.4), Touch Bar 2018 MacBook Pro.

After the VM is shutdown, the host audio will return, but it has a slight echo at the end of any audio play, just as the audio ends it stutters.

It was first noticed by me in 6.1.2, but may have been earlier and persists in 6.1.6 and 6.0.20.
Hardware diagnostics return no errors on the host.

I have reduced the RAM allocated, from 4G (50%) to 3G and the audio seems to be ok. From a thread in the forums (https://forums.virtualbox.org/viewtopic.php?f=8&t=96902), a new guest (VDI) built from scratch seems to be ok.

I copied the VM over to a non-touch bar MacBook Pro (late 2016) and it appears to run without breaking the host audio (logs also attached).

",ncj
20604,Crash on application,other,other,VirtualBox 6.1.26,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
20607,VB host kernel drivers fail to build on CentOS 8 Stream kernel 4.18.0-338,Linux,all,VirtualBox 6.1.26,2021-10-15T19:24:24Z,2021-10-15T19:24:24Z,"Building the host kernel drivers succeeds with with CentOS 8 Stream kernel 4.18.0-315.el8.x86_64 and earlier, but fails with kernel 4.18.0-338.el8.x86_64.  The issue appears to be related to issues #19644 (which relates to a newer base kernel version) and #20488 (which relates to the Guest Additions, not the host drivers), both associated with the symbol `map_vm_area` no longer being exported by the kernel.

This was initially observed with VirtualBox 6.0, but it still occurs with VirtualBox 6.1.26, as installed via the official VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 RPM.

The relevant excerpts from /var/log/vbox-setup.log appear to be:
{{{
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/r0drv/.tmp_alloc-r0drv.o"";
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/r0drv/.tmp_initterm-r0drv.o"";
  gcc -Wp,-MD,/tmp/vbox.0/r0drv/linux/.alloc-r0drv-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch
/x86/include/generated   -I./include/drm-backport -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/
generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
 -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-ss
e -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup
 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FX
SAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -
DCONFIG_TPAUSE=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-
delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -
Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -g -gdwarf-4 -pg -mrecord-mcount -mfentry -DCC_U
SING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -fno-merge-al
l-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-poi
nter-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-omit-frame-poin
ter -fno-pie -Wno-declaration-after-statement -I./include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHO
UT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_WITHOUT_EF
LAGS_AC_SET_IN_VBOXDRV -DIPRT_WITHOUT_EFLAGS_AC_PRESERVING -DVBOX_WITH_64_BITS_GUESTS -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENA
ME='""alloc_r0drv_linux""' -DKBUILD_MODNAME='""vboxdrv""' -c -o /tmp/vbox.0/r0drv/linux/.tmp_alloc-r0drv-linux.o /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c
}}}
[...]
{{{
/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtR0MemAllocExecVmArea’:
/tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.c:204:14: error: implicit declaration of function ‘map_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration]
         if (!map_vm_area(pVmArea, PAGE_KERNEL_EXEC,
              ^~~~~~~~~~~
              get_vm_area
}}}
[...]
{{{
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:316: /tmp/vbox.0/r0drv/linux/alloc-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
}}}
[...]
{{{
make[1]: *** [Makefile:1571: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxdrv] Error 2
}}}
",jcbollinger
20609,Poor performance on 4k display with scale factor less than 200%,Windows,Windows,VirtualBox 6.1.26,2021-10-16T10:48:12Z,2021-10-16T10:48:12Z,"I'm experiencing problems with VirtualBox 6.1.26 (tried other versions as well, very end of 5 series, and end of 6.0) and 4k external display. My laptop is Lenovo P53 with i7-9850H and Nvidia T2000 graphics card. 4k display needs scaling and when it's set 200% (effective resolution Full HD) then everything is smooth. If I go lower than 200% the screen gets choppy - even when dragging the explorer window very slow refresh rate is noticeable. When I change to 100% for the scale factor everything is very smooth again. My goal is to use 150% scaling and that will give me QHD resolution - but it's impossible to use due to lag. 

I tried all possible options. Adding more CPUs or enabling 3D acceleration doesn't make any difference.  Changing the scale factor from 200% to 199% like with flick of switch affects performance. 

I can't believe that this powerful laptop can't handle a 4k display with scaling. Something is not right here. 

Host: Windows 10 
Guest: Windows 7 

",VB_User
20614,No Audio output/passthrough from Linux Guest to Windows Host,Windows,Linux,VirtualBox 6.1.26,2021-10-16T17:30:37Z,2021-10-16T17:30:37Z,"I'm running an Ubuntu 18.04 Guest on a Windows 10 Host in VirutalBox 6.1.26.  When I attempt to play sound from the Ubuntu host using ALSA I get no sound passthrough to the host.  This last worked in VirtualBox 6.1.18 with no problem.  Since my upgrade it no longer works.  When I try to start the audio I get the following specific errors in my host log :

00:00:54.313145 VMMDev: Guest Log: 17:15:44.427713 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
00:00:54.313157 VMMDev: Guest Log: 17:15:44.427715 main     Log opened 2021-10-16T17:15:44.427710000Z
00:00:54.313182 VMMDev: Guest Log: 17:15:44.427760 main     OS Product: Linux
00:00:54.313198 VMMDev: Guest Log: 17:15:44.427778 main     OS Release: 4.15.0-159-generic
00:00:54.313212 VMMDev: Guest Log: 17:15:44.427793 main     OS Version: #167-Ubuntu SMP Tue Sep 21 08:55:05 UTC 2021
00:00:54.313227 VMMDev: Guest Log: 17:15:44.427807 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
00:00:54.313230 VMMDev: Guest Log: 17:15:44.427807 main     Process ID: 1890
00:00:54.313232 VMMDev: Guest Log: 17:15:44.427808 main     Package type: LINUX_64BITS_GENERIC
00:00:54.314916 VMMDev: Guest Log: 17:15:44.429498 main     6.1.24 r145751 started. Verbose level = 0
00:00:54.315580 VMMDev: Guest Log: 17:15:44.430155 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:54.315743 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:01:09.441017 HDA: DP base (lower) set: 0x000000003ae32000
00:01:09.441031 HDA: DMA position buffer is enabled
00:01:09.498001 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140707423584279ms) than used period size (0ms)
00:01:09.541955 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:09.541973 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE",kellbrir
20616,[Feature request] Marking about the changed snapshot in group view,other,other,VirtualBox 6.1.26,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
20617,Audio. Sound doesn't work in fedora live-cd with intel hd audio controller selected,Windows,Linux,VirtualBox 6.1.26,2021-10-17T18:12:10Z,2021-10-17T18:12:10Z,"When using intel hd audio controller to install fedora 34 or 35 to a virtual machine, the sound doesn't work in the live cd image.
As the result, we cannot install the system with accessibility enabled.
Steps to reproduce:
1. Download fedora 34 workstation from:
https://download.fedoraproject.org/pub/fedora/linux/releases/34/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-34-1.2.iso
2. Create new virtual machine. After creating virtual machine, choose intel hd audio controller in settings/audio.
3. Run the virtual machine.
4. When it finishes loading into live-cd, press alt+f2. Then type ""orca"" without quoates and press enter.
Expected result:
The audio driver should work and you should hear: ""Screen reader on"". Then you can continue with the installation or exploring live-cd with orca enabled.
Actual result:
After typing ""orca"" in run dialog and pressing enter, there is no sound in live-cd.
Note:
When ICH AC97 controller is selected, the sound works, but it crackles and plays only partially, so the user isn't available to interact normally with the live-cd when orca is on and perform the installation or exploring the system.",Vsevolod Popov
20608,Crash on resume machine . Please fix this bug[[BR]],other,other,VirtualBox 6.1.26,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
20618,VirtualBox installer on Windows 11: This app can't run on this device,Windows,all,VirtualBox 6.1.26,2021-10-19T16:21:30Z,2021-10-19T16:21:30Z,"Disabling core isolation memory integrity is not an option for me.

VMware Workstation Player is confirmed to be working on my device but I am in a position where I need to run a multitude of virtual machines at once.",fredd
20599,my vbox show an error when I try save machine. What is the problem???,other,other,VirtualBox 6.1.26,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
20487,"When the Shared Clipboard is disabled, a copy operation on the host clears the guest's clipboard => Fixed in SVN",all,all,VirtualBox 6.1.26,2021-10-19T20:03:31Z,2021-10-19T20:03:31Z,"On a host OS with a supported clipboard (e.g. Windows 10 21H1, Linux Mint 20), create a VM with a guest OS with a supported clipboard (e.g. Windows 10 21H1, Linux Mint 20), and leave the Shared Clipboard disabled. Open a text editor on the host and in the guest (e.g. Notepad++, xed) and type some text in each editor. Then proceed as follows:

First, select text inside the guest OS, press Ctrl-C, deselect the text and press Ctrl-V to verify that the local clipboard works as expected. Next, select text on the host OS and press Ctrl-C. Finally, press Ctrl-V inside the guest OS to see that the clipboard contents have been cleared.

Conclusion: A copy operation on the host clears the guest's clipboard. This does not happen the other way around, so a copy operation in the guest does not clear the host's clipboard. Is this behavior deliberate or a bug?",fth0
20619,Failed to Restore VM,Windows,Linux,VirtualBox 6.1.26,2021-10-19T20:06:26Z,2021-10-19T20:06:26Z,I am restoring the Virtual Machine and it stops completely.,desteves
20620,Problem moving VM,Mac OS X,Windows,VirtualBox 6.1.28,2021-10-19T22:29:06Z,2021-10-19T22:29:06Z,"Hi, so when I try to move my Windows 10 virtual machine to my SSD, it says
Failed to move the virtual machine Win10.

Can't create a test file test.txt in the /Volumes/SSD/. Check the access rights of the destination folder..

Result Code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Is there a way to fix this? (I did some research and nobody has the same problem) I'm on the latest version on MacOS if that helps.",ethan1
20548,AMD vs Intel CPU big performance difference,Windows,Windows,VirtualBox 6.1.26,2021-10-20T11:43:14Z,2021-10-20T11:43:14Z,"I use single VM on both Intel and AMD hardware. When I moved it from Intel to AMD I noticed the performance is much better. Next I tried to switch to Hyper-V on both machines, converted the VDI file and use it. 

On Intel Core i5 2540M and Intel Core i5-8265U the performance difference was about 50 percent while on AMD Ryzen 5 3600 both VirtualBox and Hyper-V performs almost identical (5 percent difference is as expected). The AMD PC machine has super fast Samsung 980 Pro SSD while the Intel laptop just an ordinary WD SSD. Still the difference is huge.

The guest OS I use for software development. It is Windows 10, Visual Studio, MS SQL Server and so on. I run unit tests of a complex project and recorded how long it takes, see the tests.png attachment. 

There is a long thread [https://forums.virtualbox.org/viewtopic.php?f=2&t=103488] about it with more detailed information.

",Petr Vones
20622,Python wrapper of VirtualBox API under Debian Bullseye doesn't work,Linux,other,VirtualBox 6.1.26,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
7213,USB: failed to create a proxy device (VERR_OUT_OF_RESOURCES),Mac OS X,other,VirtualBox 4.0.8,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
20471,pasting from Linux to windows 7 VM  via shared clipboard still crashes VM VB 6.1.24 6.1.24 r145751,Linux,Windows,VirtualBox 6.1.24,2021-10-20T17:50:46Z,2021-10-20T17:50:46Z,"Copying text in linux host and pasting into a windows 7 VM crashes the VM.The first few pastes work, then they stop working, then the VM crashes without any messages. I've attached the log. This crashing started in a more recent VB version--6.1.20 or .22 and continued with testbuilds including 145697.",matthewls
20515,Ubuntu 20.04 host hangs if I copy/paste clipboard to Win10 guest,Linux,Windows,VirtualBox 6.1.26,2021-10-20T17:55:02Z,2021-10-20T17:55:02Z,"I have a host with Ubuntu 20.04 and standard Gnome (I did not change anything as to  the UI)  and Windows 10 as guest. 

Shared clipboard is set to ""bidirectional"".  

At the beginning everything work fine, but after 10-20 clipboard copy/paste operations, everything starts to hang: I can't click anywhere, first guest OS freezes (so that I can't even restart it), then in a minute or two host OS freezes and becomes non-responsive. This reproduces many times.  

If I switch off the clipboard exchange - everything will be OK for many days long, but as soon as I switch it on - I get that problems. 

Guest additions in the guest VM are aligned with the host - the same version.

At the end of the log I have this - maybe it will help. 
Also I am ready to provide any help for VirtualBox engineers - feel free to contact me to ibobak at gmail dot com and send any custom VirtualBox binaries with additional logging, whatever. 


19:13:53.112366 ************** End of Guest state at power off ***************
19:13:53.204746 PDMR3PowerOff: 92 351 469 ns run time
19:13:53.204759 Changing the VM state from 'POWERING_OFF' to 'OFF'
19:13:53.205148 Console: Machine state changed to 'Stopping'
19:13:53.205558 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
19:14:08.186578 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:14:38.186794 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:15:08.187232 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:15:38.187862 Shared Clipboard: Converting VBox formats 0x1 to 'text/plain;charset=utf-8' for X11 (idxFmtX11=3, fmtX11=3) failed, rc=VERR_TIMEOUT
19:16:08.188045 Shared Clipboard: Converting VBox formats 0x1 to 'text/plain;charset=utf-8' for X11 (idxFmtX11=3, fmtX11=3) failed, rc=VERR_TIMEOUT
19:16:38.188318 Shared Clipboard: Converting VBox formats 0x1 to 'STRING' for X11 (idxFmtX11=4, fmtX11=2) failed, rc=VERR_TIMEOUT
19:17:08.188778 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:17:38.189030 Shared Clipboard: Converting VBox formats 0x1 to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3) failed, rc=VERR_TIMEOUT
19:17:38.189275 Shared Clipboard: Converting VBox formats 0x1 to 'INVALID' for X11 (idxFmtX11=0, fmtX11=0) failed, rc=VERR_NOT_SUPPORTED
19:17:38.189315 Shared Clipboard: Converting VBox formats 0x1 to 'INVALID' for X11 (idxFmtX11=0, fmtX11=0) failed, rc=VERR_NOT_SUPPORTED



",Ihor_Bobak
20498,PATH_SDK_QT5_INC auto-detects to .../QtGui,Linux,other,VirtualBox 6.1.26,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
19606,OS X Virtual machine has async io problems causing iy to fail,Mac OS X,Linux,VirtualBox 6.1.8,2021-10-22T06:38:57Z,2021-10-22T06:38:57Z,"Getting these messages during the install.  It's accessing the ISO installation CD and the VDI disk. I've tried different chip types, and had best success using the same ATA controller for both the CD image and the installation drive.  When using the SATA, it seems to fail, but I haven't looked at the logs.  I assume it's the same problem. Here's a bit of the log file from the VM.

00:52:18.532264 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:20.452002 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:22.372029 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:24.292006 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:26.212237 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:27.112089 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (51722074 usec ago) CmdIf1=0x00 (-1 usec ago)
00:52:28.172301 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:30.091945 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:32.011961 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:33.528271 AsyncCompletion: Task 0x00000113628f00 completed after 141 seconds
00:52:33.528418 PIIX3 ATA: execution time for ATA command 0xca was 141 seconds
00:52:33.528437 PIIX3 ATA: Ctl#0: finished processing RESET
00:52:33.528568 AsyncCompletion: Task 0x00000113628fc0 completed after 58 seconds
00:52:33.528585 PIIX3 ATA: execution time for ATAPI command 0x28 was 58 seconds
00:52:33.528604 PIIX3 ATA: Ctl#1: finished processing RESET

The VM Manager also SEGFAULTed when I powered off the machine, and I'll attach the crash dump output as well.

This is also present in versions 5.2 and 6.0 releases as well.",unixwzrd
20629,6.1.28 kernel trace on 5.15.0-0-rc3,other,other,VirtualBox 6.1.28,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
20634,No sound with pipewire after updating fedora 34 guest system,Windows,Linux,VirtualBox 6.1.28,2021-10-25T09:21:35Z,2021-10-25T09:21:35Z,"After updating the newly installed fedora 34 and restarting the guest system, there is no sound output because of the pipewire activation.
Steps to reproduce:
1. Create a new virtual machine.
2. Install fedora 34 workstation or fedora 34 mate spin on it.
3. After starting the system, try to play any audio. You will notice that it works because pulseaudio is used.
4. Install the new version of virtualbox guest additions.
5. Update the machine with sudo dnf update command in terminal.
6. Restart the guest machine.
Expected result:
After restarting the virtual machine, audio should continue working.
Actual result:
When launching orca screen reader or playing any other audio file, nothing plays and audio output doesn't work.
While testing,  ICH AC97 driver was used.
Also, this issue appears with intel hd audio controller selected.",Vsevolod Popov
20330,Pipewire audio server unusable,Linux,Linux,VirtualBox 6.1.20,2021-10-25T09:43:20Z,2021-10-25T09:43:20Z,"GNOME 40 introduces a new sound server, Pipewire, to replace pulseaudio to control sound under Linux.

Fedora 34 makes Pipewire as default, while it has a pulseaudio module to maintain compatibility, VirtualBox can't play sound with Pipewire, and it affects video playback as well.

Under GNOME settings, there is a testing option under sound preferences, no sound is available in the test.

If there is a video in a web page, like YouTube, sometimes sound can play 2-3 seconds but then the video will be muted, and frames are freezed as well, not only sound is unavailable but the video is affcted as well.

I tried to remove Pipewire and install Pulseaudio, everything is ok and back to normal again.

As Pipewire introduces many new features and better integration in future Linux development, it would be important to fix this issue before pulseaudio is completely phased out (it may take 2-3 years though...).",Promet
20635,The USB device disappears from the host but doesn't appear on the guest,Windows,Windows,VirtualBox 6.0.4,2021-10-25T10:41:25Z,2021-10-25T10:41:25Z,,LAWGR
20606,Ubuntu Guest randomly and frequently aborts.,other,Linux,VirtualBox 6.1.26,2021-10-25T14:52:35Z,2021-10-25T14:52:35Z,"I have a guest virtual machine running Ubuntu Server 20.04.3 LTS
It aborts few times per week apparently at random.
For testing I created a new VM with the same SO and happens the same thing.
The other day this happened twice in one day.
Everything to up to date.
The Host OS is Windows 10 64bit pro.
You can see the rest in the logs.",Miguel Santos
20293,"Message Linux Mint 20.1 Cinnamon - ""Check your Video Drivers""",Windows,Linux,VirtualBox 6.1.18,2021-10-25T14:58:25Z,2021-10-25T14:58:25Z,"Hi
I have used Virtualbox for quite sometime now but consider myself a newbie. I recently got a new Laptop which has NVIDIA GeForce GTX 1660 Ti Graphics Card. I have tried and tried to load Linux Mint Cinnamon 20.1 into Virtualbox but no matter what I do I continually receive ""Check Your Video Drivers - Your system is currently running without Video acceleration"".  
I have followed all the suggestions on the Forums regarding this issue and as you can see followed the suggestion to load a Beta version as it may solve the problem but all to no avail.  
I have loaded Linux Mint MATE 20.1 without any problems.  But more importantly I have installed VMware Workstation and installed Linux Mint 20.1 Cinnamon with no problems what so ever.
Also If I install Linux Mint Cinnamon 20.1 in a separate partition and dual boot it works OK.
So is there a problem with Virtuabox.
Please advise
Kind Regards 
Arthur Howard
",arfa
20631,Panic in 6.1.28 attempting to boot minix3 ISO cdrom image,other,other,VirtualBox 6.1.28,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
20633,VM Crashed,other,other,VirtualBox 6.1.28,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
20638,Windows does not start,Windows,other,VirtualBox 6.1.28,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
20585,"Shared Clipboard, guest win10 aborted, or host ubuntu cliboard hangs",Linux,Windows,VirtualBox 6.1.26,2021-10-27T09:14:57Z,2021-10-27T09:14:57Z,"Host: Ubuntu 20.04
Guest: Windows 10
Shared clipboard: bidirectional

each time I copy text from pdf files opened in acrobat 2017 in the guest win 10, the host clipboard will hang. (VBox.log)

If I copy texts several times, the guest aborted. (VBox.log.2)

This problem starts at least from VB 6.0",MaxChen
20643,Virtualbox crashes on install of Win11,Windows,Windows,VirtualBox 6.1.28,2021-10-27T12:00:20Z,2021-10-27T12:00:20Z,"win11-DVDs starts normaly, copy his files to the disk and after an reboot, the vm crashes. see attached vm-log.",tomec5189
20644,Whonix Workstation is not working,other,other,VirtualBox 6.1.28,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
20646,In the machine settings page system->acceleration hardware virtualization check box not responding.,Windows,Windows,VirtualBox 6.1.28,2021-10-29T19:20:57Z,2021-10-29T19:20:57Z,"For a virtual machine settings, a invalid setting is indicating on the system -> acceleration page , suggested that the hardware acceleration should be off. After uncheck it the OK button is not enabled , not able to save the configurations.",subhajit
20647,Windows 3.11 not working with hardware virtualization,Windows,Windows,VirtualBox 6.1.28,2021-10-30T17:29:23Z,2021-10-30T17:29:23Z,"If you install MSDOS 6.22 and Windows 3.11 in a Virtualbox machine, Windows 3.11 cannot start when hardware virtualization is enabled (mandatory in VB 6.1). The same virtual machine works OK in VB 6.0 with the hardware virtualization disabled. Windows 3.1 is not affected, only Windows 3.11 (Windows for Workgroups). Is there any workaround for this problem?",Iker Rodriguez
20632,6.1.28 Does Not Work at All on Kubuntu 20.04.3 LTS,Linux,all,VirtualBox 6.1.28,2021-10-31T09:23:19Z,2021-10-31T09:23:19Z,"As reported by several people on your [https://forums.virtualbox.org/viewtopic.php?f=7&t=104196 forums]...

Host: Kubuntu 20.04.03
Guests: (2) Kubuntu 20.04.03 and (1) Windows 10
VB: Version 6.1.28 r147628 (Qt5.12.8)
Package: https://download.virtualbox.org/virtualbox/6.1.28/virtualbox-6.1_6.1.28-147628~Ubuntu~eoan_amd64.deb

All is well on 6.1.26. Upgrading to 6.1.28 causes all guests to fail on startup, with the following error message.

{{{
Failed to open a session for the virtual machine | machine name |
}}}

Under ""Details"", the error contains:

{{{
The virtual machine |machine name| has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

I further attempted to export the guests from 6.1.26, and import them into 6.1.28, but that made no difference.

Downgrading back to 6.1.26 restores correct functionality, so luckily, that's easy. This operation also proves that there's nothing amiss with the machines themselves.

Even worse, newly-created VMs exhibit the same error, so to put it bluntly, 6.1.28 does not work at all on this system.

",Hillman
19530,New VM instance can not display icon!,other,all,VirtualBox 6.1.6,2021-11-03T08:41:05Z,2021-11-03T08:41:05Z,"When start new VM,not icon display in task list,like this image:
[[Image(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAP0AAAHcCAYAAAAdsqzbAAAACXBIWXMAAA7EAAAOxAGVKw4bAAAgAElEQVR4nOy9d7hdVZ3//1pr71PvPfemJ6QnQBIglAAJCoEQOkgTsYttsM7oqDPf+Y0z3zbOOMU6MqLjKIqDiiKIIEWBQEBKIAGSkBBIIL2XW0/fe6/1+2P3c869uSDOdzjZ7+fZ2fvsulae+16fvpZYeNR8LYVgKPhXtLcJQCMQ6GGf0ZH94TCS+6LtGOrZxmMVaa1Ax661epePFbvWjqDVCRK8OSFdAgxNep/s7l0CAcMS3n8muheRLzTuo/cd7p2t7nPPi6b36KCdzUOKxh8Q/N9D9z9BgnaDjNPGJ4+IEKmZnq2IOxyihG3cv5b3tMLhBiH/mmr4ioj0RUaeT+ifoN0h41LSJ4KOEKlZSvpnVMPAMJzEjEr7RmqNRNK3ei5sz/BUHWpg8HvZqCEkSNDOkK1PD0XPEHFJrWP7oe7XDfePBFGtYyhKisPQvnFgCDWVhOIJjjxI39UVx/BOuuj+jULcwIgPEEOTM2qXD4/oO4Ij0axxJMNAgnaHDB1eI4FAReRqSyLFfrd+c6MXfaTXhrr3dUPH3xA3QRIkaE9IaJb0zQT2ia5jkncopTqqjh9O7fYx0oHncOG24dszfKsSL36CIwESGiW27/Zq7e0eSgVupkvoIAxdgiMj33CIhwH9kFzjPY3tb+xfvI3hr0S5T9D+kK1o12hHiwaZDCNJ0Gl+ZnhSiWDAOfw9UQznPGztgRgqMtHq3gQJ2g2B9973cB/OAx+N4I8EPo1Dw6C1ZB55ik70mebj1u+OtqdRV3i94cMECd6ckEOlpcSt9/g9rSRyczQ/btu3enerUJ9m+AEi/l6/VTrW1qFj8vEhq7WcT2ifoL1hDnXBz1WPRrcFGm0YHPuWU3jr0sVkMunX9dGDPb0sf+wJFl18MalUath7AwVdwP1P76dvw+/J2H1IaTA4/gz+7KrjAD+11nXIR5V3ARQHijxx/4P0vrwFHCfWx0YkzrwE7Q4RLbiJJ7C0KlARTH/LAn728+8flqyHw85du7n53mVceN11Qzcusu8frHPN5+9j6rp/IWVK6h3TOPNDf8fXPzwXB7A0OBocmskvgMH+fv76uuvpeeFlry/RL4R9hqTgJkF7w7Pph3K0icjmXl9y/tl/MOEBpk6ZTMGuUVcMudUi208e3EnHrmVIAUIaHByzmE9fNh1LR+7XUFXhVlFQVlBSYBS6WXjJBRHTgojCHw9IJkjQzjAhLvVaOemi17PZ1ir9oZ4etNIUugpk0vF7lFIUiyW6ugqx8x3ZDLXDmNACqFZt7n7gRSb2PYs0JFZmHIvPXcK08TlsDXXczVKupPclvm+3a0/PN/L5pvcnJE9wpMFsFQB7LTToHxjgr774d6xZuw6AuXOO4cc33Rhc37J1Gx+5/jNUazW+c8NXOXXBSbHnhyO9r2PcuXwXqe0PY6CR0mDPqDP518tnYmuwcKV6XYOtwcbdO4DSnqoPCO3e475XHzZSkSBBu8JsRfJm214E+0Z8/6ZbePXVLfzge99i/vHz2L//QPgerfnaN7/D+PHj2LFzF07EieajpoZunAAcW3H3bzcwtvcZpCFxUqM44S3ncsKMApaGqnbf4Ut6C4/0Dfa9wLX73f4199Pva4IE7Q55OPX2cNeXPfwYZ565iEq5wspVz1MohCr8Aw8t5+WXN3H9R4d21g1n09cVPPjkbtj8MAY2Ukr2d7+FT10x21XrPcLXNNQcdwDw7fmyZ9NXnNC2twJOxwe1qKMyUfcTtDuGCNk1y/9WZLAdh96+Ph548BGeWrGSUqnMrJkzuPkH36ZWq3HDjf/BB697N2NGjxqyAXUVfjEKiasp3HP/y4zpXYGUBsrsZPJJS3jrcWOwtEd2Har3lg73vrRXkZfbwY+RJfYkSNCOaMq9dzFCe9erUrv8sot44N7b+Z9f/Ate3byFFze8zG23/xrLsllw8ols37kLgO07d6EbKtui3nffY1/3SPzUs/uovbwMU9eRUnKgayEfu+JYbE/CVx2X8LWIt77quFvFu1b1JH0lkPQJyRMc2fC890Olxh7mYdOku6tAqVxGCEGh0AmAYRgc6ulhYGCAj33q88H9X/vGt1m6ZHFM8jsqdLYF44FwHW/33/8yY3ufREoDbWbpPOYcLjptgqvWR1R7X9LXVVzSK1xnnv9ap2EcG2nyb4IE7YRAvX+tXnsfV1/5Nm752W186ctfZfXadRw9eybHzTuW+SfM43984TMArFz1PJ/5/F9zwzf+qUnVdxrIqb3GvLThIIMvLKNTVZFmioOFU/nU5fNQQoSSXXuS3RsEfNLbPumj76SZ9AnhExyJCEj/epXeT378w0yfPpVXXt3MNVddzhWXX4xhGLF7pk2dwvUf+QDTp09tev57/76KSy6bw1FTu9DeACCAh367kbG9TyClBCONnrqYKxdPpq5Ctd3f1zwvfpT0jo5LeWgmfYIERyIaHHmHl/eOisfYhBC87dILh31m0qQJLT34jlJU7/lbvv/42UxdfDEXXTqPoyYX2LK1j0PPPsRkVUKaKXo6TuTdl54AUrreeMf1xgdSXoWqvqXCOL1vLgSSPuI0TCz7BEcqTH8iCvff1rPNRs+uW7/hDfv42rXryFFhas9vqd3zOD98fDHTFl9CqVhnnCflhWFSmnAWl54znX47DMNVPYefH6bziR/12ushJL2fgpt47hMciRhSvffJ3nh+Z0Vxw3d/yHXvuYbRw4TihsOhnl5+8ONf8Nt1JboNE0MqcqrM1J7fUr33CSrZGYxWgximSV/+OJaedyIV06RY95JuPGedT3Tf829555W3+f3woSI/EsInOFJhNs5C62MoSoyfdyJ9p53PX/zsIaxqJTY4COHGAKUAw99w92bkXC6f55jzruSc0edz173P0n3gMUZXX/LIXyJXWQ+miTQM9neczqyZo6k6obfd0W7M3fK2gPQq9No3SnmIDAS6aSLcAInZn6DdYYY1ZyOzdW0F5rjJTL/4WuwIsWQDwU0BKQlpAWkJmciWEmBKeM8UuOCcGfzs3pP4/bJnGd/3e0ZVNyEQCCFAwNF9d3HzV3fywIKlXH3pPE44bjxaufa5o9z22I7nsVehA8/vTxS+jT/M0n2J/E/Q9jB1S0u+GX6lmu2FyXypGgmtY4iQ/KZH7JpHen+fle7eFB45s2nec83xXLh0Fv9ywxSMDT+i296NkG7Vb0YVmda/jNojj/PdZ05l1PzzufTS+Rx/4iQcLVzy63AQaMzCG0q9968lJE9wpCEorfX/+JWOE8GXiv7eVlC3w0krfF++wFXtRUTi+1K/7pE8LaHqSXrpCnLMyHFx9xYmVreiDZOyeRRlcxxjqy8ipSKjahw1+Dj2Uyv4xdpTMY9ZyjkXncz8BVPRQqIV7haJzUeT/zTe9Uh7E8InOBJhQmgr+3b5cHAU1J3QS+4n0yBCIkmPyJKQ/CmP/CkRagH+cUrCfQ++yqiex9FKoQ04UFjEZ66/glvvW0tx03LGVtdhCAupFBNLz+CsWcXyTSfy4LSlnH7eAuYvnIEwzYDxPumjCT9+tV1U4PvX/H4nNn2CdkeT9z4q9Vs5vBw/Fq5CNTqmJgtiTj3D21s++WVI9JS3HyjWeXL5aqaXNkDKpGKM4YLzz+ajl8zi/RfO5DdPnc7371hN30uPMK66FlPVkVoxvrIG9dIaXth2PCvuO5v5SxZy8ltnk8qlXcI3kl+HZkqs3yKuASRI0M6IqfcaMIXg/dNrLBpdp64ED+9Pce/edCAxlQLL9qR8Cw95I/l91d2X+FaDoy8jYfnyzXQeeBwpBVJIDnQs5BNXHotSbmjtojOmcO7pU3hw5QJ+dOca9r/0KBMqqzFFFSU142obGL11Pdv2PMTah85mzllv4ZSzjiZXyIGXqBNIehEOADHpnhj4CY4QuJI+op5/ZGaFq46qBzcc2+lQc+DBA+4UWI7nLfcTXYZSh6P8kcKd0cZX+40I6au2zdPL1zKl9ALClNhmN6edtYRpEzupOGE4ztFwzmmTWXzqZB57fgE/uWste9c/xoTq86ScElJKxlibGbVrEwd+vYxfLD+TGWcs5tSzj6UwphMnqtoP1WgNOiF+gjaHiQYRWbB6yTir6aZzxlsB6ZUOveS0kPSNELiSVkTVfo/0joB1K7aS3fsEhnCQMsWe3AL+15Xz3Jx6L9W2rkLPuxCw8KRJnH7iJJ5dfwo/+806dqxZzqTq86RUEakko+yddO3/OaX7l/PrJ97KxFPPZsE5cxGRgSqQ8hG9PuF7giMBTd77Vn/4QVDPU5FtxytmOYy0D58PIYVLOEeArRXP/349R5WeRxoGysgz69RzmTdrNGUHyra7+RNeCh0OHlLAifMm8M/zzmPdKyfz89+sY+uzy5lYfY6MGkAqRUHtp6P3TiqPPMbvnlnEhC6L0YTSXkc6nRA+wZGCWGktGpYfSHPV5FrspuUHvduEZ8c7kbLVhrDYUPBJ5eASVgt45YXtmLuewKSOFCn2Z0/mL86fzR23/YZDA1XqCgpjullw3kXBJJe+tpACir0HePHppykVyywYJ+icN4l1ryxGWyUm1taSVb1IrelQfeQG78esZAIPvt8mHSH8sKp/ggRtAtM3dP2/9R9tTVNXmkVj7MCR99D+dOjdDoLgLuGD8tURSP2AXMJ90frHX2R8aRVSGmBksFJjuOmr/8iBg32x53buPsRZ174HjUBpKPUc5NFbb2H140/SSkZLNHu6j0PkC0ysrCLnHEJKifS8ir5t37KtichP0OYwo048ABvBj7dn+fG2hjCWr1YDhna9+FHyj0Tq++9BwK5Nu9E7VpDWZZApDtULsO85Js6dwc9v/CInHTcLgOs++xWee/ppTrz8XShhUOzr5fa/+1usUom//ez7+MA15zF2dBdCCJTWbNuxjxt+eBc/+dUyZh53Avlj/5IXVjzBhMpKCvpg3JnnD3iNIbwECdoYsXp6jSfJvb/8gKQ+uQUMHBpkvPbKUn27foRS31fNhYCXnnqRcaVnkFLSZxewZZa/+ey7+POPXuVOnOEhZRpYtTrFqsKRBivuuI1yXz8P3PpPwcDgQwrBrOmT+Ob//QSzZ0ziS9/8KX/zoXfwvqs+zi/vO4ctj93KWJbFohUxlV7EB64ECdoRMiyRa74Y/P2LkBy7Vz/D/Tf/lkrvoJtCq0EowE+DdTzvvgPKcffBplwNYf+2fVhbnibj9CKlQVVl+fSHruDz178dKSWlcjXWDkcpBmsOg3XY9ORy3n/NeQHhX9y0jcs/9L859ZI/5Z9v/EXwzCevexuFzhyPP/I448Z08NkPLeTqy06J9atljkEi6hO0OWRUsjX+vQsImOFf67K307X+33jguz9i06qNpNAu+XG1BK0Bj9yOComvItvGFRsYW1qJNAyElGgkQsC6l7Zy7cf/nlvueCjWDq01pZpmx9pncWyHd1y2OLj2vVvuY9W6TfRULb7+vTvo7S8CkDJNLl26kBdWrqK/4lC2IL6IRzOiTr4ECdoVMirtdNNBHBqQUpIXJWb2/JItv/43Hv75Q9QHSqS0u1yObCH1VWTfv7eH0qaV5O29SCkZTM0gM3oa37rp1yx911/x6IoXmr6rNFTqcGjHNgBOPn52cO2Z1S/TNXU2R1/8bgCefWFTcG3yxLH09/Wzv2jTW4WqHe9LY0ahn62XIEE7Q0o/DOenpXpb9Djq3RdCYpgpzJTJJGs1HWtv4KHv/Zgtaze5BTS4jj7pSXwcV+prxx0IXl35ImPLKz1vumSgsJAbv/MlPnT9+7j82itaNlJrqFpQq7mszeez3nnNq9v2kBk/g46jzwA0a9ZvDp5LpUyUgoNFh4NlXGnvp+LqMGfA7VhC+ARHBrzFLiJo5YTzjF3XCSeQUmIYJqaZolMMMLPn52y5+9/5/e3LcEpld5YcHZoHvs1f7h2g7+XnKFjbkNKgbBzFeRcspru7k3MuvYJFFw5Betxy3nq5QmdHLoz5OwqtNY4wqJJBAJYdivN8NgMIDvZVOFSGih0SPvBPRjOThozjJUjQPjB1kJPqinNFqPNHU1VFRNwL4Q8AhnesmFx/huK6LTy8czMnnH8+k+fODkjk5+lvfc6z5T0p35NbwDsvmovlCKrKoKZbr7KlNdRs0EaaajWsC5DSbaCjBFWreXLPas29t2in0BXXRIgNao0evcSgT3AEwJX0QuPxJ9hDxOZt6eEXCCGR0sAwXalf4BAzD/2UTXd9j2fueRRdqZIWbgmtU65w8MXVdNc3IaVBzRjDwrOXMHZUnqoN5TpUmtP+g3ZYNmgMbMcJlsaSUjJuTDdWaZBa0XXgdXd1BM9ZtrtubbEuGKi6efzRnIRol4JBIJH0Cdoc0ld3m5x4DSqvHoIQrrovMAwD0zRJmzCt/iTptd/h0f+8lQObt5MRsGPNBkYXV7rls1JyIH0y77rkeGo2lOqwbfMWnn34dy0b6Vh1elbej9W3FyAW0jtjwVyqO15k4MUnAMH5i08Jru0/1IeRyVG2JMWaayI0wh/UDjd5SIIE7QLTd2jpiOoeY3fk59BCUATkF0IgpKTb2UP+0H/y0q9fZfcJF7NvyyvMtjYgDYltFDj21HMZN66bgRrcd/svuf/2Xw75drtcYv9jPw9+P/nsBi4651QAzl+8gHuXPcPBR25m3jHTOWbmZLetWnP/wyvJTjuRqm3i1HDre4kQvCFElwj5BEcC4jPn+J63lnG8w8O17yX+ICAchxn15fSu2coY8phSI6XJXmM+V517IvtLrkq//N67ufZti/mHv/owAB25bPDOb33p03z1f30MgH/41q385FfLuOu3Twakf/815yGF4MChfq5/3yXeoAX3P7ySQ70DdB8/F0uZOBYYTrx7MaVGx8a3BAnaFnHPWcSTHYtfv6ZXCqQErQ0EAiUkY9QOtFYIw0QZOQpHn0N+zDh297vTbtWqVaZPnsDY0V1Nbyt05oAcAEdNcAtjb7vnMc5ceALvf/tSpBC8/5rzYs+sXLORz/zv72Dku0nPOgvbMdz0YuUlETV+RIddT7T8BO0Ol/SRWLw/0URU6r1257br3UdKpBAIKTznm8ASHRzYvYsVT7/MwoVzEAi6x01k2ROrMUxj2Lcuf2otMpXFGDuTz/2f7/KTOx5iyVtPCnL1tda89MoO7nnoaUSmg85zP4kyO0EJUGB4pA9bGT9OpHyCIwHi1EknasOfmaKF7R715wkBcvak1/gJ7SX/+C/XWEqwS5xM4ZjzueKqsxg4sI1lP/lXyoODwzfWTJFd9GHSM8+gvmk5tQ33o4oHw1ZqjUhlSB19Npl5F2J0TkSkcvhTA+U23EL6nq/F+tWqv8/sXvMa+5ggwZsHwcw5bn1pa1l3uPTc4REm9fgDgKkVU5xnKG7YxE3bXua0JUu55HM30DtQpm+wTLHqUK5rag5YDjhaoIWBMHPITCfayJCaeynm7HPR9TLKqbk5vkIijDQynUekcmiZQqtQtg9X+ptI+gRHCiI2vVuOEsxO0+ruP9jg9QYAKTEwKdBHrnQHL/1uIxvWXcDp551NftRU7JrGqYOycKfaCRaxkG4rlUBjgGFCrtOrGvLtEvce977413Xkd2Nm3hvSvQQJ3gQwo4kqMWdWQ849vFG15q6jD8JsvknqBSrbt/DYrRuZfOqFTDvxFEzDwPAW1ZA6nMZa6ZC8utXwNEwbY8taNRA+vJRQP0F7I1jhJopoiqpucf0PhxvT19oL7SlBh1Nmdu0eDj69kWdeuZCj37qU9OhJ7gw9ngpiR2frIRyERjoWiXoFn+pR6R4/TpT8BO0N0y8nbSa2S4Gm83Ub0q1z5F8r/Li+u3eTesY7m+g6sIPN971Efu5FTDlpEciUq+J7Krk/E6/SrSR1axj1AbJbHgz61KrPmpY9TpCgrSBOnXSilkIynBMvlqOeNpETuhGZ1BvaEO3Z5VprlHKr5/rFdHTndMbOPBalhbuUVoT0sbXqYEjmG7VecjseQeza5s7ffRi33crEe5+gjWHK6PQ4HmJhOhps37qN3nko8JENr/578frAYyY89Vkg0LEVb6Pwh6DR9ACrYb3XWK8l0SFKe+8aCcJluRMVPsGRi0iuiktvX3IOlYkbV/p9Eg1Fex2vVxfae7eOfLHVU83nBSCFbpLRIvKuxneKhrtErOXEjpICuwRHCmS4kGP4Z394AjRa0lH3V2MdrkZpEajljZrD4d7sH8erAcMBKrxHBO/VNMpzHWlN4/uj+sxIdYYECd68kAgRC2U11ZjHroTQQ0rIqCz3n9RDvrc5M6418fw3iIa7W7WpVeQ9fHdjP/yziRsvwZEB6drIrX33jfRoRcZGNTn8NbTMlA13+ZTzZW1L4mkdMQvibQmV/rj8bo6+N94TagfNPUiQoD0hm61i91g30Tau/jYWq7hEjA8VQ5EpbkgMQ/TYF4bPnhvKBxH/Xvxc6+8m1E/Q3ogWnQW16M00EU2Ss1nu+6ktQ0f9w2eHduDFbe7WvvbmL+sWg1Djb9Hyu4kNn+BIg8R35ImoH77Rfm52z0FrhVo0Hbu/omnwrSzzZps/VP2b6drcviiGzjiIv6FRO2gc2BIkaEdIIRr+yL2Zbn0czp8fEnVotbjZQddoaze/L7yv2c/e2LJWbQpdc41fjL+rORyZIEF7Q2qEN+llgyQUcJi0mxZegKFJ2PwrTt9GcgpPxrfWCRodec3fi6v8oR7R6t7WrUqQoD0h0Rp/Dg0frhQUrtSPSMzm0FwYSvMxNPF1A12HLm0ZKiwX5tOJFt+Jt7OV6RHvX3PYMQnYJTgSEE6ige/sak5taeXeixMzLvPjbr/m6Hz8iTBVt3UYrtFrP5TF3kphj36vlaYQPxdvZYIE7QlTCBFZrdVNm01nUoybOI5sPodpmAwnlYfDG2UjN4bq3khiOrZNtVzlwP6D1Gv1RNYnaHuYUQIpLcjmMkybOc2b6KIxhq8j3vTWGAkpo5K+tTxvvr/V8UjgvzW6j77LME06ujrJd3ayc+t2qpVqq9ckSNA2MP3cez9GP27iWIR0jXx/FqpAynoJ8I2Kf2gSjIygukmd/uP5zVuH5ZohJIydMI6d23b+UdqRIMF/F8jQy+1SIpd355hXKnToB7l4Oqpk+6k4IyFrc4puc2hu5Hg9w8PQQcIQWa/vCRK0M6T2Zqn1J6aQskUmvh++82a4iZ721rNpuj3u/IsaCa3Sd14rDlfS29iasC3DDRlSvt72JEjw5oEUgJAR6kbUd1/pdgW8Nyp4IT5i+kFzSCz6Dp9Kyrsahsdeu8z2PfEj97W3qqFv/d4ECY4ESACtNAIVZOIFWbmCMDtPyPCk1u6cdgyfDtuIkHytnIEjq2V/bUNF64Sc4dqWpOckaHdI307XCI8dHlFCwR5oAH55q5vF1+zQGwqtIufNabGNCbGt39wqgWY4UjdXCyZIcGRDRknUmMkWSHwiA8OQBG9F1KEt78ZzQzn2Gm3/RgqH+X2tvtKa8q0GgaGy9xIkaDe4GXlDzYPt/W4klL+EfTM9Qq/+cNI/k8tx5qWXcdrFl+EoWHnfr1n50EPUKpWme8NsumhEP57Q2+zYa51NOJxpkCj1CY4UNCxr1UCdBoa8NmKErjb/uVHjxrP0Hdcwf/E5ZPNpBgcqZNJpll73QRZdeS0bHl/Oinvvpffg/sgbWo1HzZkCw7eiOasvQYIjFaYff3fT34dXbQPSvEYNeOrRR7P0mmuYd/ppZDIG+/f1cNfdy7nzvt8zduwY3nPNxSxcuICFV1zGSedfwtbnV/L7O+9g19YtTQG3EK3SgRoRl+1DkX14vSRBgvaCGcr3uGSNh8YabGrPHAjI0qQ3CwxDcuqSxZx5yaXMmHM0hoCtW3fx6/se4q4Hn2Lbnj7S6TQvbzvAU89t4OTjZvOuq87n7MVncNzZZzDr9DPYuWE9K++9i41r16Icp6El0ZbTcHYot2Azmgmf0D9Be0OcOukk7S8rpbVmzglzgOFU+6hTr5k0hVHdXPTOazhtyRK6u/MI4IX1G7ntrge5Z/kqDvZVyGSypMzYTF1UaxaOYzNn1mSuvXwpF11wFqPGj6ZYgUPbd7Dmgft5YcVTlEtFb4wZvgYgtP6H9jA0Oyxh4/qNrEpWuEnQxhCnTTpR460nB3Ds8ccCzaQPHiCei++bBFNmTOfS976T4087lc58CtvWPL3qeW654wEeXrGewapNPpfDNKLrxevgPf7vumVTrdaYMWU8V150Fldcdi6TJk+iUoPBnh42PPEYzz28jEP79jbZ6I3Ousbzzcci+DchfYIjBeLUSSdpKbxseAFzDkP6+NOCWXOPYeG557DonLMYO6aTYrHKw48/zY9vf5AVazZTV4J8NoNhSKR0t2gqbxRKqWAdu7plU6lUGT+mi0vOXcg1l5/P0UfPpu5ApVThybtvZ/MLa9izdZvb3samefvhBoDGBwQJ6RO0PwL1niFIHyeJ+0saBjPnHsOcE47j0ne/nbSZ4lBPDw8+uoKf3vUoazbuQsgU2WzKk6Ku+WAYBoZhYJomUsbVe8dxgi1KfkcpKpUanfkM5771ZN5x+XnMmTsHW7kW/fKf/5R927aw89XNKMeKtRSaCR6u6BO/z0+737huI6v2JKRP0L4IJD24iu6cE4aX9Bq44oPv4eIrLyaVMhHCIG0K/vnGn/H33/kVqVSGUV35pueklJimGZDeHwD8VWp9wtu2HRzHvqs1PX2D5DImf/9Xf8Kll17AYMVBCkFaOiz71e08deedQ7Y56HDst/9LIL119jYlpE/Q5pBhFp5XBnMY57UAZs49nh3bezCEoCNnIqTkbz97Hfff/CXeeuocBooVLNsOn2mozgOXxL5Uj73fX6s+cr9l2ZTKFc5eNJ+b/vV/cvHF52E5cNRok5Q9wC9+/Si7BoxY9MFP6fEdjqLhmgjuIOg9kfsTJGhXRJJz3AWgh7blQ0W/2NtLtYusnTQAACAASURBVKp58QWLadNGM2FiN8IQXHTWiSxZdAI337GMb/7wbrbvPkBnPodhhI66KNmjxPadev49QggcR1EqV5gxdQKf+OBVXHnpUgxTYkowlMVDj67nN4++RKWmmFmoBa2MBhvjQTz/SAdqfqPj73CDXoIEb3aY8RTX1sUsUVmpgeLgIOPyYxFasGdnH/19RaZMHUuhK08mJfnEey7k6gsW8fWb7uLHv3qEYqlCZ4c7QYXWOubQ8yMAUTVfKeU+k8/yyQ9dwUc/cAXjx3VhW1BIwdoXd/Cfdz/Hq7v76cxn6ezIUasO4FcA+tlDfq9CuhOjvo+RpPkkSNAuMBtnl/fhk72V4Bs41MPEKbPo6eshm0pTyI5h26t7GDOug/GTxpJKpZg4rpuv/H8f5H1XnsOXv3M7v330OUzTIJfNBCT3nXk+4ZVSVKo1HEdx8dLT+fNPXMv846dTr0OHCQcODfCtu9bwyLNbMTMp8rkUUmikmUFVLARuzb4/SEWlPd654HdDucFwefkJErQTInPFjOxPXgDFYpF8OsX2Xbv42Je/zQNPryZrpin1ltn2yjb6e3oCdf2U42byy3/7S37yjc8xZ9ZkevuL1OtW4LSzLAvbtqnV6vT1F5l39FRu+uYXuOlbX2D+8dNJAR043HX/ej7z5d/x4Mrt5Dvz1Cq9vPj8Y1RKfaQyeZxq3SW5bl01FO1d43G0snBEocoECd7EMIci+1AZbAKoDA4ihWBUoZMDvQN88caf8fCqtfzZtRdxzLTxHNh9gNLgAGMnTCCTcz35V12wiAvOOpl//9nv+PYt97HvYD+FjiwAg6UKk8aP5ot/+k4+/J4LKWTT1IEc8Oy6Pfz7L1fz0tZDdHfl6MjB9s2r2bN7B1JbpHMFzFSaqlVDK1fSSwVCNkp59zg0ZKKaQCLnExw5MOP2/PB/+P5AUBkcBAmZTIqOXJa6I3jg6XWs3LCF669cwnsvWISqOuzdsYOu0d10jRmLYaToyGX4iz+5kndc8lb+5Xt3cutvHkMKyZ+86wL+8mNvZ8ZRY6kDKaCnp8QNv1rNfY9vJZ1OM2FMBwcPbWPb1g2Uy2UMwyRlpkhnOkilUpSVhcKV1NqbtXd4p1zznLwJEhwJ8Lz3Ucs2jlYprMXBIhpNLpMibUosBV0deSrVOl/5z3tZtnI9n3/vRZx50izKfQPUyyW6xowjW+gGYOaU8Xz3Sx/nvVedg5SCxQvmBt8zlOZXD2/gR3e9wMF+i3GjCjhWPy+/tI4DB/cipUEqlUYpjWEYZLJ5UimJU7PQym2lS3pB0+Kc0GTlJ0hwpMEMSd3aey9aHFu1OkJospk0aVNSrDmk02lSqRQp02T1xh187B9v5r0XLeLT157LUbksAwf3UysV6Rw9FjOTRQPnnDYv9q21G/fx3dtW8dxL++nIdzCmK8uBfRvYvmMTlmVhmikMwwBAKQvTMMlkckhDop0aCuEFHj1nRVIzmyBBE4I4fWOh6nClqQP9fTi2TTptkM+mOVQsI6UknU5jGAZSSizb5qa7H2f5cxv5yw9cyNXnngTKZuDAXnKFLrKFUWhvuu3egQo33bmau5ZvwtEGo7q6qZb389KrL9Lf3+uq8ql0kMXnOA4aME2DdDaLFBpl2SgFSJB4y29o4klB3oR/rUJ0iVWf4EiB2RyFj6OVoKyWK5QGByh05OjMZ1GqFGTWpdNphBDIeh1DSnbu6+HPvnIr9z+1jr/5yCXMmzWJcrmIY9foHDueR1ft4Ss3P8W+3jLdhU6ErrNn52r27duO1ppUKo2UMiC8D6002UyGdDoHVgnlWGjhJfno0FnXqjOtpt9OCJ/gSIEZ+yVc9fiy3C5OSPViacEztfE8XpsQt4W1plqrMba7i85cJiiO8TPpTNN9rdaabCaF42h+89hanlq7mc+97zyue9sZSNsGu8r9T21h96Ey40blKfbvYtfODVQqJQwjhZTxIh0g8i1FJpvFSJlYAxWcej0gezBPv784Z2DbtzJWWlYWJUjQtjBjnnsNV+Z2cG5mb3DD9Pw2LC15qj4u9mCpVMaQgkJHFhVJrjEMI6ioM03TS7d16MxlKJZr/MU3bsc0DT71znNAabIZk3w+R3lwL69uWgnCxDQ9bUFKDNMgZaaQUgZJPC6xNZlMFsM0qFaLWLUqWmkMb+ASaBTaLS6I2S3RMruIfA/uSWR+gvaGbDxxWupQ002nZeLnNNC3twcpoLsz702JrwMpHBDWk9K+XW0akkwmRbFcczmmwTDcAcJ2bEAipRE8b5puWM6vygM3Dq9wS2SyuRyGYaBqFayahdKg0F5iUGRmnSADR0eM98i1BAmOILgr3OhI9VmLMFd0llxfIA72DyClpKsjj9YqkkrrBCm2PumjtfNhUUtY1efm4bv3+L9N0ySVCgmvAUdrbO2XzmhyuQ4MQ1IZHKRSquM4OuSy1ujImCaCxosI50WDFvD6/yMTJHizQPpE9//2V9XHNt20qj66yeNdLA4gpaCrMxfLnbcsm1qthm3bsRr65oo67ZvdGDKcyd71CRik0+mQ8F5lnqU1jvsC1zTIdSCEpF4u4yhQiHBVngbzPVpiK4SOkF34NwSDQoIE7YxIco5L599UpmJpyfx0H7aWPFMbx4ra+CYhWC6XUAI6cxnqlo1SKiC6f5zJZALHnl9BFy96cakoRZg95w4UroQXgHIcHKWw/Ik1bBvtOFh2nWyuA5CUBvrDbLyGdmpAaBFU3gVSXhCq+0CwgkfC+QRtjogjz4WN5J7qVH5TmRq7sbHuvDg4SLVaZ8np87n6/J3c99hq8rkMKdMMJDO4ITxf1ffDekqrsLJFawzpK92hLS+0Rtk2tlKuWu84aMfBqdfRjs3Ss89i6ox5OI6iVu4P3heaDxJX9sOQersQ8Wt66FsTJGgXyLhdG68xb12v5t5V6h+g52AvozpyfO2z7+ZvPnYVAkG5Uo1NluE4TuCYi8+eozz1XmOIUB0XgLZt7FoNq17Htiwsy8KxbaqVCh3ZFO98+9UsWnw1jlGgXh6k2N8bf0Gwj77Ub7wOr/mqQeDkS8R8gvaHdG3reBw7OvlEeDY8lkJQLhbZunUbGqhV63z40rdw09/9CbOnTWSg6K5JF/XoB5NmELHpvc2Q4UKTWinsWs3dbBvLcbAsi0q5zLEzpvC+d3+ACVNPZqDiYDsOGx+/h+LBQ0gpkNJtmxACNxFftx4Mot77UDVo7myCBG0I13vfINejZG/l3FZaY1sWd/z0Nh5+chXCMCiV65wyezI/+YeP846LFlEsV7GscJLLYNKMBmkq8NR7P1vOcXAsyyW7UtTqFo5tseTMhVx62btQ5jiqlsJMmWxecTdrHr0PrWxkEJ8PTQfhF9A2qu0xpyKJlE9wREG2SFYdITSGlNz6Hz/lOz/4OUoa1OsOedPkq5+5li//+bsxUybFUiWY4dafWEOpiDddgDRE4FhTWmMDNlCp1Sh0Zrj68suZf/JSilWX1lJa/P7Wf+Wpu28nmy6QNk133jypPUnv59zr4Bsx20THzZhonxIkaHfI4f7Qo6m3jSWpvppf6Mjz9PIVfO4v/oGDpRoIQbVS54MXLeTWf/oUc2dPpqdvEMuyXEeelzjjJsqHpJdeSxRga02lVuPY2dO5+qp3Uhh3LJWqhSE05b6d3HnD/+TFVavIdYwmnUqRlgLTBENKpBRBHkAsAheT9qKFm1833JMgQXtCRjkRhS8ch+OAFJqUoenOZ+nbd4iPfuBzrH55Gx2dnZSqFvNnTuQX//RJ3nvZWxkoVqjX3cUolDvTheuvl+5il76Tz3YclHI458yFLDnvciwKaMeh0NHBzpee4dav/1969vTR0TGaTMoklxJk0oK0FBjC9Q0IIZC+g7LROSGgadndRLNPcAQhSFkTDftWXIkeCy/0LYQgbUJXPk2ho5M//8Rf84/fvRlpptEIsqbB1/78nXzlC+8hnTYpV+v4ATo3ZVdimBIhBfW6RVdnnssvu4RjT3gL5aomYxgUcmnWrriPe378TbTIks4VSJsG2ZQkm5akDTAMPCkvg9bHE3Q87SIi5f2kvOA6wy2JmSBBe8Bb7CL8U2/1R9+o3vubkAJDCkwJubSkK59i9NjxbN5yiG/e9Et2Hewnm8tSqdT44CWL+MW/fJoTjplCsVQD7erzhpQYKQPHsTh65lQuv+IKusbPoFaz6Mp3oOv9LLvr+6x//mmEUSCVypE2THJpg1zKJbxpgCH9JJ/IzAABuf3EmyGyd/y9SIR+gvZHw3RZoUZ8ONU+gNYI6U7Bk01BV05SrBQZP2kaN/7wLq665EzOXjSfUrnM/FmTuONrn2b73h6qdZt8OoM03CSaOcfOpqNwCo5OYyrF6EIXOzat4fFlv0EgGDdpCnu37HBny0kbZExIm5qMKTCl67nHd+IRz7uJ966h+XhjgWg9JiRI0G4w4Q+rORHCVRe00JgSOjIme/Yf4KQT5zBlwgTue3AFW7fv5T1Xn4vSitEdeSYdV6BuW+RwK+9SpiSbH4UCsqkUuVSG5x67m5fWrWHcpJlMnDievft2kBJpMimDrAm5lCSbAlN6IT8ZJXxEbGsvp99PxgH8NW+aPPfi9UYyEiR488CL07uIEv5w5I8m8QlA4nrg06ZEDA6yfe9BFp0+l4svOo8dO/r42o23cWiwQjaXoW47CCHRGq+azsCUks58AWHX+O1t32Pjiy8wa95pTJ0+i8KYMQz2DJDN5MilJfm0JJfWri0vfW+kdmP0jS0Psv10vNHRTkTWzkskfYJ2RxCnb3JwH+bBxgHC/20agjFZk0eWr6Cju5M5c47i/AvOorNzPP/8zZ+xct1m8h15hBc3MAxBJpWiq9DFge2b+fXNN1CpWMw96QzmHj+XyTOmsm/nToq9veSyWTrSglxak0kJDMOt0MOLywtCad/UWN+JF5j7Aq1FxA6IZiYmSNC+MIWn/EJDinrDjUPZ+E33CejMZ9i04jHWvHgFS06f6zr70gsodHfxgx//lo2bd/L+t5/rSfk0nR2drH18GWueepRJU49lyqxjmDV7FvmODE8/+RS7Xn0Fu1hl0thuOrOQS4EpXW+9FJ6nfog2CXCnxPY9Fb6QF5FMvRE7MBIkePMjmAJ7pJK9VVw/6vwDgSElY9Mm3/iHrzHnh19nxvRx7mqzaYN8VyePP7GCzTv28vEPX41tVXnqvtvo2bOH+QvOYtLkKcydeyy2dnj2+dUM9PRzaPsOpk0cz+gOSS6lMU3pkb05n3DojFoRXPTz/4PknbDxCRK0PcSCSSdrEXFgHXvCscBr0HRjHm93Zjpwl5nuL9Uwxk/kX77+fzj+6GnsP9DHvp4+tu86xHPPrWf/wQOUy2W0NpgybTajx4+hI5+jp6+fx1e/TM+Ozex+4QWmjh/L+EKKbMo1B2T049HOjJC4OsjN9x6KrIbz8vpNPLdn9Qg7nyDBmw8x0mtgzghJ3+gHCMrjvTMKd+bagVKNvrrm3X/yIS678EK0FBzq6+FQbx/7DxyiVCxTrdUoVmvUanX27e9l665dHNq9G2vfPo4aM5pRHW6ITkpv3jvfOS9aax6HRYvO+fn5L69LSJ+gvSEWTDpJy0g22khJPxzCZ13y1+oW+w4V0V2jOWXR6YyZMAGRLlCtW1TqdXr7+imXigz09XFg+2as3h4KmQzju7J0pA0MU4RhBl+t/4PVcR3TUvx85I3rN/LsnjV/6MsTJPhvCxM/Yv0G2rUhITUGkM+YTD9qFJZts3P1SjZaNqTSYEqEmcF2JKpWQdVrjMMmP6GbfEp6ZG/OsmlF+JH64kLHpWjKwIso/QkStC3MUNz5dv1rY/9IyWYIMFIGGQ2dKdMtt7U02qojBQhTYKQNDGEGM/L6i1b4avxw3xm5C6I5UuGed/udOPETtDtMtBvSCqXnH1fS+Wq0TDVNue8h4hYUrc6+MWj9voTyCdofXgVqq9XdRobXahUkJesJEvy/hVtw05ie+hrRDiQWf7hnMEGCNwWkn5rz/zo/5XV9e5jRJqFwggSt4RrWkeqzPzaG+sLr0haGae7r1T6SwSJBu0NqHZ9hxl+Q4o+F/86mgFbqjUgASJDgvzWkEILIXDNUy9URP/xfSeD/CipWytX/3qNSggRvAEwilBfAwf0HmZafipBDhdRC/FcQsTHd948FrRQH9x9MBH2CtkfAbD+UVq3U2LZ5O8WBIrZtNz0wkoq8ofB6nvtjC17HtikNFNm2eTvVSi0R9AnaHqY/DX1UotZrFrt37AEixTT+QUQUNhXdRF7slq5GU2hDE0Jp7S095eXBBemwwq2AC5a7iR0GKbQi8o0hRbMO/ol0MGwLfnfwfRr+hxLaJ2hvmNE8eUGzB9/N0A1TVEVwUvvZu/hZfUQGBxE8R2Q08EgrvGq5CNnCGp04+bQmTtLgso4NJNovxmlV+O+1yT0U4eARjEnBSnqJIy9B20Nqb5YoDc1rvkUYJIgksLg/IhNQRM5HJHtgDETmn/OzAoLv+h+NSlitY4NA7FJwPvy8OwBEdYDwpmitvz/G+BNjEvz2S3ASwidof5ixdd4C0sZOMKQrTYdlar4eMKRyrD0tIpDu0Zq2eMVb+Frv38hnReS5KKHDw3gbg56I6LRgvszXgSYRDkgJErQ3ZKBl400UiYiL/MgSVFG48f3wbDx737PNow/5At8X6qKB0J50Dyktwud9tUCIQCY3zYoX1Q68U4EWEqj27gW/rcE7PI2jsckJErQjZJy2EYkec4RFKBNqxe4gEbENAsIGGr1uIr8mLJUNSBwld/SbMYUjlP3RNgcnm2zxiE8gfAlRcyaK0OmY0D5Be8P0ZV4MAlfHjv72Dz1uCF8hEBFmah27N4bA1Pckb+Cci1S4Bx720KtP9FrwrqgyHvPuNZA/bgBo//v+JX+wCMY0kXA+QdtjyAwcjY6QoXlQ0DokbSggRXjssVa0mohehOQKnGcRLoYfoUk0a//56N1R9aNBD/DXqm85sDV3mqYVbRMkaDPIoSRcQNaoaz+m8ocO/EAVb/LeR19ISLToq6IkC6wL4Y0LzQSMCv9mlb6VK85fITdqRkQuN2onCecTtDliVXZRCRxHYKR7El5HJHOEMTGJ6/9uYUQHzzYMEP4g4j0XEryVek9DW3XTsWg8jmoT/kDW0M3Ef5+g3SF9HTjggGhVYOuRN6KJa+1n1oVOPl9C+xjSJvechmIIGzpUKCIuf2gmqW/P+4NVMMgQO+9yOa6hBH2OjgSJlE9wBEBG/W/R7LxgL1qF6yL3aN/+97zlvstMR5aNCp+M2+aRqID73jBrzpfugVD3nHfKjxL4Tjutg2t+QlDr9vruwugAErYVoRPeJzgiYGoNbkFd6IUPSB0JrfnkECmT2QuPY8n5S8hmM6/rowd7enngwUcol8vBuZxjcVbfTsZls2RTEpQD2omw0CO09oktAjLrINyoAYXQGrQCrdBKM6ANHjRH0d9TcV+po70lEopIkKD9IRZMOkmHHnRf3Y7Y5joM6glg9uKTueWW/3jdhPexc9duPnL9ZxgsFplbPMifDm7hhImjyWRMsGpgVdBWHZQGLUOya4nWEqWkR3XptkwohFagHYSyg03ZDspS7NcmfzruZPYfdOcLCJa28uz4YLpt4NlkhZsEbQwzpmF7qnpcy3fVaP/ckvPO/oMJDzB1ymQuvOBcen54I59NDTD5xKMhY0K9CjUNVQdtAY5CO56E98ivlERoiUaiheuLdH0LCqElQuEOFo6DsAEDxtdrLFW93EYWFdj5BBZG7HeCBG0ME1z5FjjQfSdYg7rrS8JspjXhD/X0oJWm0FUgk07HrimlKBZLdHUVYufHjB7F9Z11xhx9DHRkXZXe1CBtMDTCMsDRCFuDq62DFkhtoLQr4bXwfJFowNPdFe7UV45G2xptaLSAnLQjjn/hmgHRvkZs/wQJ2hWmxluAwo+ZD2nftp42s39ggL/64t+xZu06AObOOYYf33RjcH3L1m185PrPUK3V+M4NX+XUBSfFnh8zdzaM6nQbYVVApkE6bq6gnQZHu5sC4bghQ6EEMoj1+2W6jmfH40l5jbIVSioUCkcptBEZ4HynYeCA9BOFElGfoL3hznsfpK/GCR/3rbfIagO+f9MtvPrqFn7wvW8x//h57N9/IHxea772ze8wfvw4duzcheM4zS0YPxpyGXBsdwgyAFNCOgW2AtsBBTjuJnxnu9IIrdGeHQ/a890ptKNRQqNQKKVxhHJdA/68l7F16v2eNvc4QYJ2hIzOGqMDwodVbOGZ8N8olj38GGeeuYhKucLKVc9TKIQq/AMPLefllzdx/UevG7oFo3LQnYfuAnR1QWcBOgpQ6IZCF3R1R7YuKBQQnR3QmYd8GpE3ETkDkRGItABToKUn7OsCpyxQAwJnAHQtDAvGiR4etRrYEiRoJ5hoEDKq3oa5La5XO0qCOCFsx6G3r48HHnyEp1aspFQqM2vmDG7+wbep1WrccON/8MHr3s2Y0aOGbsHoPGQLoCXUalCtus48ywLbBkeFKr6jQSlwbIRtoZWBcOquw89yXM++kqiaRJUlatDAKSnsksCpaFSWoOAnrsO06l2CBO0J15HncyBq0kaidv5BUy2KNyBcftlF/O1ff4H7f7eML335q7y44WWefW41lmWz4OQT2fjKZgC279zF6aedEl9CamwX5EeDTkPdhkoZ6jWX9I7tkdxxN2W7560a1KuIuoAaYCi0tsGS4Eh0XaIrElWROCVX2ts110/YaMuH6TqJap/gyICJX9ii8arRIKrkimg+fkOBi2madHcVKJXLCCEoFDoBMAyDQz09DAwM8LFPfT64/2vf+DZLlyyOS/4xo6BzPIgsWNqT9DWw6+BYoCx379RdstcqUDOgAlRdT7/AcImOK+m1LVGWQFmgHIGjwEbgLuMRidN5fU2Q4EhCEKdvNb8cRLPXWkvCq698G7f87Da+9OWvsnrtOo6ePZPj5h3L/BPm8T++8BkAVq56ns98/q+54Rv/1KzqF7ph1Fgwu8ARriSvV8CuglMN91YFamUoC6hoMG0QFtgG1IXr/deglEZp7dr0CBzpbcL1BwZ5CAHnfZ99NFknQYL2hRlQ2XNlC+JTUcXceS1CeZ/8+IeZPn0qr7y6mWuuupwrLr8YwzBi90ybOoXrP/IBpk+f2tyCTB7SecgUQKZcld6pgV0GuwR1E+pA1cuysYX7G9e2p15HlyvogRJqoIIqW6iqhWM5OErhaI2D+1gwL0gwhZbfO4/waGKThyRI0IZwQ3aEJAiL2uKS3ae707DWnRCCt1164bAfmTRpQksPvqOUG5cXhhdft3Hjct6mbVetd+pg1aFeh1odylUYKEHvABzqg54B9GANVaqjyw6q4qBqNspSOI5LfIUr6UUsDyHqviQsH0yQoI1htjoZ9+fp2Nl16ze8YR8v7tsOYrYrsUXFk8COK+mtCtQ8+75Wg2oNKjUolmBgEPr7obcf3dePGiyiihaqbONUFKqqUDWFqiuUrXEcjROp+mv0WwYz/icZeQmOAEg/hTXwYPtee9Fo5bsXVq56nm/e8O/09va97o8e6unlhn/7DhdMtVyXulWFeglqRagOQrUIFX8ru5K9XIFi2SX9YBH6i6iBQVSxhC6W0ZUqqlpH1y20ZaNtB+Uod9PaT+oL+hEleywbIeF8gjaH2Zh4GkwQ7VXXRZaFCI5+8cs7+cUv7xzxRyb37md0eZBF82ciR3XQMbqDdy6YzFHTJoFdA1l29+B66m3LjdXXK1CtuMQPCF+GAZ/oFXS1iqpbqLpC2xpla5SjUcqN9imP7LYbzRvWV68jg16CBO2KQL2Pkz+kejRD7fXwIV2vctzOVxhTKXLtKaMZM2c8YuJo6M66ebF2PWyB1m5Cjm25Kn2t6oboyhUoVdAll/y6UoVa3ZXojoNSCqUdl+De5uCS3NYu4Q84sFd5YUk/69j3Y8Ry9BJRn6C9IcPyuqjTznNwBdpudDHr1wLNlN59mPUKjoDN6zYjTBMM6Y0yynXS1StQL7tqfbUIZX8rQakEpTK67Kr5ulZD2zZKOW5evXIluS/RHRFKddsQ1AzYaMPTFuyPNc237BsX2UiQoL1humJPuuG6wLEtAlU3lPevrQJtlFXh4v2b6Ny/n111hUzBxr09TFm9icmXnOG+S9luLA3pSXnHjdPX6mFKbqWKrpShXEFVq+i6Z7fXbZTj4ABKuLF4W7phe0e5En63BevL8IqGkt96rT1pP9TKdYl+n6C94an3OpD00Vq6+J//yNJUhdYsPrSVK3q2c3Qmx7p0jr3VEgLoBdY89AzZaeMYc+aJrirvjyzKU+3rHumrVc9jX4FSGVWpoKs1VM1C1y3PQSfcBBwEjhA4noTfbcG6AcWrNhzwWu5P8K+DSsJw/bpQyieET9D+CGz6YPooCGL1r5UCnXaNd+54gQucCpPHuCWzOUqYg6VguNipNOZP7ueEQz0cdeUShDbdD9kOWG6yDdU6VKpQrQbOOl2ro6w6yvKmwFI6SLxxhKCqJdtKio19mldrmr0abFyyR1f0EA1aS5z4rTITEyRoL5gQz0Y3peAD06ucMaZOXQmW7U9z9+7MYeX8uFqRj+9ax7kdJpnOsZDPQTrNeGki9hwM7tPALqWo/+4p+tdu4KiL3kL3Kce5MfKolK/UXLJXqqhaHVWr4dQslGW5ar2jGCg7HOh12NNrs21QsdeB/cpNyR+qva3NFBG7I0GCdoYZJqC6Rx+dWeHtk2vBDXM6K1Qd+N2+zJC15mNrRb649wUWTsgjCh2QyUA2h8ikmTm2G3PdFvwouY8+DS/s62Pvrb9l3N3L6J4xmdzkSaQ7cpjpFIYAXa3h1C3qgxVqxQqlvhKD/WUGBioc7KvRU1f0OnBIwaBnx7eYpqMBLQjvVRDqFlcTJGg3mH7evV82u3Sc1XTTuePrPLAv3ZIQdR8oFAAAIABJREFUacfi8wc3cMbkLijkIZ9DZLKQzSBSGbJpk2NmTmTztj1Nzzoa9jtwYNDCXLeNzLptpPHaoj2HnAJLQVVBRUFZQVHBoOMW5VnaJftrQ1zax2fPSZCgvRFOl+WjxQKO0QSdODRv79nMkkl5xKhOl/D5nCvp02lEJgOmyeJzT2TrLXsZjlh17U6C68fZbe2S3VYesT3y296110tR0TTtV7TIKCF+gvaHhPif+vID6aabHjmYavnwqHqF92bLGGM6EV05ZHcHopBHdOURhTx0ZhGFLOOmj+es80/5o3RgpDg6LZiXahWPH2pAS5CgPdFUcPODLVlqDpwx1sJSggf3pXlgb/NAAJrFpX1MmDYaUchBoQNyWch6WyqNSJnu8jmmYOH5J1FXddY/uf6/oFshxpmCs3KCqRrub6oeTDz1CY48NJHe1vCjbVl+tC3LcLFrreEtmRqiezQU8ojOLDqbhazrtRfpNJiGO7mF1CA0Z11xBhOnj+OZe59yV6/5I2JyRnJah8ExAoy6Qjoao4nk0QrCBAmODLQsrR0JtNbMygvIZxCdWchnEbkcOp1xCZ8ywTC8wL/26vk0x5x+DNOOn8q65avZ8tzLOLb9hnUmZwiO7kgxP2cwAY2sKaTt2uxCgjEkt6PFtgkStDfMuLLb7OQidi2OXGcaurLQkYF8FjIZRDoDqRSYJkHyvtC4a025X8t05jjtbWdw8nkL2L72VXa/vJ39O/dTqzZHDoaDEDApn2ZSNsW0jMHklERaClF3wHICsuP1UYq4LZ847hIciYhIehFxcjWTQcdsYfe6lUkh8hl3sYpcGjJpSKfB8KW8X7GjCdal0t68VQrMTJrZC+Yy+4RjoG7Rv/cQffv7GOwrUi7VKJYqOLbCdjS2o8mbJhLIGgYFKekSAmnb6LrtzqRrOe7SVwjXl6BVdCo8dyUf/NmyGvszsjTjBAne7PAy8hqTU4dC/Op+mWZGLu1K+mwG0hkwU+4mZKRyz5Py/vLTyjuvRODoQwu6J02ge8xYdN1G17yimprl1svX3M2p1t3z1bq7eeE2JTxWS4E2fFXdXfjCnytLynBVm7C+rlGtT6R/gvaGCaCCWLVXUtuUe9d4zqXMC0VYmEtD1ttSKTA8SS+MyJxzmmBNKS1xF5oU7pp1Snk2P+5m4BodSiMUSG/5KuEod0sZKMdBmBJpSpTjklz7ewQIgfYHAX9yPOUJf68HzbPmJEhwZMCMyMQW02b4aJ2A+/g+h/crTSabgkwqIuU90vvEUt56c1K6aXb45bQe8SWuo08K19umJMKQaNM7dqRLcic8Fo5Ee+eUctes19IdPLQ3gGgHb317bxCRIphEIyF7giMVslUZbajwDm3jCgEv5say6vcbXSmfTruZeCnvOJX2BoF0uBkpz95PgzTdzTDcwUBKd3INKRGGR37DJb8whUt0f5+SSFMgUgKZksiUxEhLzJTAiG5pGfstpW/LR0N1jep9YtcnaG+EU2AH0E0DQFytD48daXDTq4oZK19h6rmnuiSXaXf+eu2RSeNJem95KmG7s99qXAms8aS89tR8Tw83JUIJtPKlvcAvmJeORKUkUhmgHATuYKGldC0Hb4Vbd416Eax6K2QjoRt7lmTnJWh/uAU3LbPUdORfYufAc8wLwZquSXz/1y/yUQxmXHY2iDSICOmVR2jlLTDv+Lq3CE1qfwZLQ4GSYCiEFmhPyuMId/lqR7jOPyWQvkqPRAjp3msYbhG9R3Kf/Dju2vTCjEr1Vj1LKJ+g/WH+/+29eZxdRZ02/lTdc+/tPZ1Oujv7nhCWhDAB2WSV1VFQXxx0FFGRcR1mdEadz4zOoL8Z39FZ3EdZBEf0HRcURRARCCib7EsIkLBk37o7SXfS291O/f6oU6e+VafO7dsBRnNvPdp9tjpVdUI/9V2rSrnuJh+ykmvocc5xS9cSiJ89jbes34EVH/tzZFtbEBvXQs2iqUgJr9RpdZ8LIBOdi1AfeZRNU5GqvrTxOVjI5cAgZHSAMQ7BOFg5I52AGWGSPgRECRgYKWJPsQwgF+ccmF/s4/YejQErI8/+o69OAsYYOJdku2X6UmzfsB1v+/AXsPxtZ2H+m85G0JSPonVCqva8hHhfbEV2EWkBPIycepF9z6VNj4xU9SEYmOBybTsRXbMMBAvBWCjrqgggm5EDRQUYPFBG374x7BwsYEAEeL63iXyVK93IE9+j/qHXyDtIMAbwDAcQ4Ikps/FioRPn/ORerL7xdsw59QTMPO0kdB2+DCzISAkNTuz5aHF6nolU+4y26RmXnvaMUuml1z6W8ojyADiX75cFwpLA0L5x7O4fwe49oxgpCjzb1Ikn22dhXdNUBE2tYBhC8pvZpPUcD49DFc7c+3RJ6AIziH+gqQ0/6T4MtxXHcNz967H6N/ejpznA9FVHYfrKI9C5ZD7aZ3WDBZGUV5I+tKS8/RORnwUcAgzlksDoyDhGh8YwuOcABveMYv/+AoYQ4MVcO9Y3d2Pd1E4UMtlII+HI8Iyxy435FR4ejYEg+ceuEnGU7LN9+S4o4mfAmFyZdoRnsCbbjDs75qG7NIJla3di0aPrMaM0hp4s0NI9DU1dHWie0o58R0tk80c/ofwJiyWURscgKiEKw2MoF4ooF0oYPTCOcrGMPZk8dgbN2JVtxs5gKrZPa8HeoCm29TlnCDgH5xyccfAMtxbtovCy3qMxEOiItZmhpr36FNUkf7TjLefIMAbOQ4ScQ4QCe4MMHsy34wERIgxD5MMyesdG0baljLawH+2VUtW6Q8YwzJswwtsxxjMY6wiwJ8ijyIMo01cm3TDGEDAeJeFI84Bb12673ZWt4OFRnwjU5g/2lJqDdWpJ8gFCZMAYB7hAKDIQIoQQAkKEqIgsduSaoms50NSyQ7QiuBpgsjJuGG22ycA4l4MXAyG57pN31Hl4AEpUOpTbpHpfu/LL4jg+ILeAFoIjJreQ5oNaa19dV1ck6D7y0XlEdhikBiF7Lb32k208GgsB4vl1ivxUvUd075XISHMA0BLdlu61OQ2NK4PoyefpddA0XFjXnvge9Y2AWvN07hmia6oBCACiWAbLHeyCO0oi2+eTcaIdvLNNFKNttPQdu8RB1+3hcagg3vGJOdR4cxqqRHnXEERhcivcTAw2iZ+DgxgvobxzSF9bRw+PRoEhst0z7fQTBiAsllHauteagW/DrTbrsvQ51TPSaG3O5pfeAX0vWZvpjjQz65NhSOEo6+FRr4hJn5Tu5n27nKIYXXojXX7afgJduzAomoSrH7YpYg8WaUlFpsvS7r+75x4e9YZ4s4vQknhpEW1aQhLOJdX1HWG9Jyz6MtKaTX46NNj3qOZgDwimocLIue21MIcrn57j0QgwbHpKEZ2K65L1lDTuhadcia6mMq+onG5du4eC9CfJklFoMD63DQXdbnpbHh71Ba7/2G3FXZ2lqepukgpLYU/G/l0LcLpktmmbm9dp++favXTJ+jT4cJ1HY4BraVurO0urydQpZ9vUaRR2kVE9T7bk1h+qJwOn+fnpd9klPOE9GgexTZ/muU/ayCBPbInPHCXS4HoqnLoFhTI46FCTVt7WJpQF7zYD3HqNh0e9gdO/cvlHb7veJpbILjebetc8s0malOXJ9sx3XB4Al9ruIm+aizEtUuHhUY/gpsI7kWvMlPlpHm8XMdWAYkYFzGu3lDW99GaILd22ryWVR8CO0Xvie9Q/uDGRJeFkSyaxmMEuwEWT5CBgxuldA0U1ktZCRGH9pJVJ1q1Cdp7uHo2BOGSXdOXZcKv1aQtNpUn76jW7fP3muYhlfHUV3x1z0AOQ7rt82y9+7dEoCGzO2sS3KZ0+IFClPYmJpLx6Wk1dNwcZkRhY0nzwaQPARG16eNQjOGWgnYlnS1k3qRhUHrwdjqN2sklMKq1Ns4E56tDPzYQeVwzejh4ojz2AeONK+7n5NR4e9Y2E9746aIY9I/JW0TjNP56M4+s6qAdBX7ntc1uTSPMqmFCuPx7tY+fSXGpx/Hl41AO4LZ3TpJ/OtqOec9vnT+1lU6WnJXRiT9osPXf6TFyHMDUElxNP9YxF5eO2mOm0M/vmae9R/+CSBKYKXy3uzSw62448QQYBl2NQ010/0+1SZdx8l+b4xctwJeq3NQ1NdNqWHXugPfb2vUe9IzBpKmGr5SZBhXHf9IIjLmHbzixRVk1rNdtOc8Yh8Z7pibd7rihN25Tr8qlBgL7rqe7ROAhMxd70rlfzpFOkecyp5pA0GWzKmh55uz1KbDrxJm1wsSmtyqmNa00txDRYPDzqGVHuvTvn3SYrlaO10KNamM6eiedakNNVo6InM6if1E5qGZj0oEAn4Hp41Ddi772SeFRSuohky2P3BJYkqFde2+/JZ0mkZwZM5j59rvvg97DzaDwE5l/8ZOapm3Y1BdUQ3FI+KscYTj/jSJx3/p/gyCPnYvr0DgDAwMB+rFu3Fb++7Qncc/cz8VLZdtac7Qy079v9Mculew88POoZ7OjelYIxVjMFXq1ynVNa8Z9feR9WHbOwaj1PPrERn/jr6zE4NALts09fKmsyfUrr4xM7n5ygJg+PQxfs6N6VgpNdbiZ8YYJy2jue/l7X1DZc+92PYsH8HvTtHsL3/vtuPHD/euzYsQ+AwKxZXTj59ctxyXtOR0/vFGza3IfL3vsNDO4bgdIxVDtUitvf4HYgpmsICp70HvWMmPQTEWGiZ5Mp/69fvATnnLsK69ZtxRUfuwb7IjLbpad2tuLr/3U5jjhiLn5z+5P4u0/fAMA9sKRFHKh2UCs86T3qGfHKOQq1UaN6qWohv+XL5+Ccc1dhZHgcf/uJ76YSHgAGB0fwtx//LoaHx3HOuauwfPkcWb9DkzAdj8lV/2hozsOjkRGk6uMK1nOa9AIA5bCMMCxgWq6EtmwFTayCgAFhysBwyUXnAQDW/PIetB7YgMUtqMJFBgz34+5b7sGb33Ee3v32Fbjuy086i3PGURbAeMgxXOLYMxaAsxyCTBbU3Wir98DktBcPj0Md7OielYLxaqRHgpRCAEIIZMR+vHl5K95y6mrMXroMzVO6kG1pA883g2cyUQtxUwAAPrcVLM8Rbh+FGK/AKpQcABgDa+LgM5shiiHC7WOykFUuDCsIi+MojY5gbP8+bH/pBdy05mHc8swQKqINnHPSQHWae/Xeo57BVvasFLwa6VPAxSC+9MaFOPnMsyC2b4Do3wYxOgRRGAfKRUCEJOldJ7+3fP4rYLk8Rq/8G4jiOAwC2+WjZyzfhJZ/+CJEsYDRL/xdok6AAZwD2TxYvgmseQpY92ywGYtx/9134VM/eRYhpiBp4bsHAE96j3pGoLhDtfiJZGGhXMDbFzKctGI5Kr/9EcTYSDpxLXKGO7bJ9grjllnBkkfVt2IBlc0v62c24Vn0AaVxiFIBYmQIGNgCtmktTjr6eLzp6Y34yboi8kEewjBXVKaB3+bCo3HAju5ZKcDc20Zr+90cAgql/bjm7ClY1dsGMbA9VUIb91IGAffx1XuPTZuFJ7YP4oM/24lc0Jb4B7BDf4DAEzufcv1beXjUBTiY7cdjcQacK+NOCKA3X8IMVoAY7EM1Cf2HJjwYgxgawIxsGb2tFfldIpnjr+bnI5Hu4+FRf+Axw8kffFVnPgTaAoHWfAYIxf8KcV/RewjRkgvQEggI4VhXLx70XFOOPDzqD4EAAydZboCb9FT9zfEK8pkMUAlhEg9mBQZh4SYsY2j+m2vAexcY7VW2rsf4f12R/p6rPZeUFgJN2QC5TBh9AY++wst0j8ZEPLUWiLiTwgSqFHMGZDIcr4aEDo48GZmFK8Ba2vVPvhmZ3nnILD1Wlwc9uu6l9yWT4fE8enscMr/Pw6P+wRPrvVf965faAGdqMQpLNahFshvPGfhZlyRbGRuVnTvpLbrwJOq0+yL7ywCW/nFe6ns0CnjaIpEU9n2BMFqnDhNLdtCjeS+z4Ejklq4yK6+UgPI4ACC36CjwWYtfmR9AqAEq1O4LD48GBjdWnU8hRVIKMvKTVnpiCc3PuTT5eiTl4w6ecEHiPbPeGrQMxq1BKIIfBDwaEJySt5rXXoMw5RXY83zGAuRXnGLUPLJ5A0a2vGDcyx55ElhnN0zCH5z/QLnv4i9w+f3SPtvDo06gd7ixZ6Go29Xm2QIHTUB+6kWJUWZgzU8w8MCtZgczGWSOf9Pk20t8jNJpUlb3k8F6D4+6B9eJOMmkFSDilFCTbFwPgck68FhzK3LHnW9UVR45APbkb8CeXoPy6IjxLDj6TCCXJ4PEQZgVAKqu58cYhPfmeTQAOBWgIk2sM4fq/wqSZ/hx54M3txrV9d17MzpRQSerYOCx3xrPMs0t4CvOIJ1J60O1viRhD2RpXgoPj3oC2cCSgTGGgAHvW1DAVX9yAF9fNYwLZhalEzyep+JyptH7VZxt0Y3MyW81eyEECvf+XIbWODD2+1/KWXoEwbHnI06Sp3XWqmUYzcUrbdbox/DwqB8E9EIAuGzBON42uxDfW9Y2hkIF+HVfThoATBCN2cn+lHuSgJllxyI3e7HRiX3rHkb7/h1AIGXtlOHdGHzpWXQuOSouk+2ZjcrClahsfPrgtYyoaGzV+7Q8jwYEV1JP7eZ6ZncxUej0niLizSUEM63/ydrzp/yfRP377/0FmiLCgwH5DMf+R+5IlGOrz510e7YoD4k+zxzJOqkmjodHnSCIN3xgkX3rkHz2inNBLg82ZTqQzasCqEXSsvZpyK80w3Sl4SFktz8HNqXb0B6yO9ajNDqCbIu2/bNLVyOctQRiZLCm9uJ2m9sR5JqiW2QWoWAJ9Z55fd+jzsEFolCVEGAMuLs/lyh0d39AIlpWbG8yDrxVZ4DxjFH3wEN3oCOAQXgA6Mgy7F37oNlZzoHlJ5rtwHzPfU+BzDGIvjdRwkt6jzpHYKvp176cR6ECnDCthGLIcOfuLG7fldeaAEUV1Zp3z0Xuzz6NzLzDAYvoFDPPfx9w/vucz5JLXgAtF/wVcMFfyYtKGZWNT6Fw81cghve6+2L11V4HVJo1EywO6uFRR4gdeSL6VWYM129uwvWbm4yp9gxKQpIbVSR79p2fQWbuYa9t7zMBMktWI3v+h1H8yReqEF7dkNJdmjN6ABCCxREK79nzqHcEALHnIaSjLiZ3BKet73CaqRMeIJizFAAQbn8JGB+xX351kG8Gn7MUmLUsXatPkeDKf6Htey/sPRoDgbEmnvqrN9R45d1PYwRhW6xCVzC86Xm0LTwC3ArPvRY4sPFZ5IEkax2T581knCTTvUnvUe/g+jT51x4n40SE1tdAunovT7dceyX2b3gSolLBa4WwXMK+Zx5E301fdxDeOqpLBig1X9n4IvHcw6N+YSbnqCXvDOmv70vPdm3r4vWO9+Hlf/8wRkoVZN72cWS75xgN777jh+jY9Kh6MfG+vs1wYO5KdJ9wnvF+aXAPwruvR0c+wNwprUiwO5EgoM8ZmCnR488VVTQaD4/6QACYKq172o0CU9E9xExJiY03ZTNY2tUCPmcJms99k1GLKJew/ZYtmDqjw0H0JEn3lXZg5lGH611zIozvewzh7i3pdjxN/zXEOVyKTZXv9vCoH2j1fgK9lkbnheJQCuENIbvyzERde595CO2VMSSksQFdZwcrYujFdckiS0+cmPCMIRQCoRDx4p8C5nigPPfenvdoBHClzmvu6JV0DCLQZBbBEAIg60c7JTSCHHIrT000OvL4PQg4Wc0mdfCQxwxnGHnuoUQ92cXHABmSTJTSlzC6cI0P1G3h4dEI4Eqd11JOO+40EYRRJgwFKmHabBVNOL78eGRazBSb8ugwshufTAr5CWbNBVufRtlaSivT1AS2aGXV98CASihQITnGyj9Bs+/MQc/Do36hHXmRnWtr+baNz8BQqDCMlyrIcg6ElVTC7nvuEaz7zCXG2MDKZRzWnLaKbnpkoD3gWPvtz0JkAqOTs5oEOqrNtuMZjJfKKJSUJaOcdfKDiQ/Pw6MhEKg/eosCUCn5gPLg62fDZYaRUgntTbyqhG4tj2MRp7Y7wPNcKtqTnA/POLAoX0KIkvEBmZDJSfgsUUlc/2ixjOFCRX0WOFOZOcmQndfzPeodckIrs8JyanYadXqTxJ1dwwzbh0Yxo20qUKykEjfIAAFNBTjYBS1Vam+GJzlpL6Fl15kJsHXfIHYfAAKOOFxHv805r8DDo07BtaYsl4yU0TgRe7QhhI7fC4AxhooIcOeLQwiDPKDCaGmSWmEiyZ68mbyXRvi0QSSTQZjJ4c7n+lEOM4htGOu3h0cjgYtIxVWzaeQoEG1PrdQAAwwBz+K2l8bxu00DEN3zwTq7wZra5OKVmawcCFgKcdPuTXbZK4PokuDgGSCbA2tqA5syHWLqHPzuxd349bphZHnWdNbZot3qhodHvYKt6FkhMlyr4NR2t6egKvFfESFCEaIlW8DZS5tx/qpFmDuzG62tLcjn82AZjmyQTRLfUtc10+ilS0uwe22/L1AqVSAQojBewMjoKLbs7MOvH30Jv1k3iLFiHgHLJBfIiHX8+OMgADy1y+9P71G/YCt7Vgqm58yq2yl2rh4QQlFBKATKYRmMldHTItCeF2gOgGyGoRyGyGW4dJopHwGtgelNJxgQLT/NjDJGkI0Jo7xCRTAUyyGCTAalSoixMnBgHNi9PwRjWWRYAM4YOONmrdGpbkMr/J70HvWMILESDknMUVfU2ac2i+AsAyBEwDMQyGBgDBgY0xUnhxH5W1h2NIsplwwOajjX7HFAkzrDVT85OOPEY6Ecksk8A2/hezQCojg9UbOtCSfxUBDl3RKLP5KgWQDCWHCS0sekFiPkZsZuMyIeFuxy6rdWv6neYNevwFW2oEoJoKUYEApdKxJDkYdH/SIwpJ3jL1/JWBar/Ha8C4BgOgygNGfnKptmVkDSsScc5/S53VFGGnQ8o3PnLXOFGWU9PBoHXEo5oWWd7esCUcGVyu8W6nF5kfYQQNJ/kGwtvQd2PUpVd9cmrHkEhmaf2kMPj/oGl79YrG5DaKJQCOOYZl0Lx+vmGzTb3c58r0XJ1otfqHqF8Z5jmEl8hEjtk4dH/YPH5IvDZC5pK+GanqJn5SXVcSeZlG+AUfktiH2vBxQR2/Z2TaZlbxsJ+pzG9ynRU/rm4dEA4LGkFIoKttTUDjWlaGsJ6dII3JqCG5rgzBhwaJtyjz09MNkwow52IdPJJ1Lpnh4R8PCoL3DA7SLT912EU8S2kmQs2Dvj0OFAiOSQYUbircFDxdUTDjsXiZkxYCXbTzdfPDzqHZL09oqwBgUiqgh9rqQ9N1RnGnKjNVHVXZWloKE3UzmPFX5hqe1xqrAJqmWo3oQiqZFU2aXew6PuwQElPV3E1XSxpTCDjHVX8wEwxkDtdhoX18+IlU0GEXOgUHejYxxo0CHAZIBQGIOA+SVerns0Lrgt9eJrpq901pxNmaSKbavwVKEWQGyfC2EPJPKmtSeuflfQWuy2dWqPTXFHsM/+N0h8jYdHPYMnM9ojmRkTVkt26m5TdNIy2XbKmb5+9ROqabuRmaALaYlNhxBb0xDGXdpv5vxtDFFVJ80nNQsPj3pEZNMDtvdbwHaGRUQiC2zoiTSU8G7vveGPZwycaUter1KrbXvavh2SU9l/KqSXLGFGGfQjl2dBOJ2KHh71ioBFzq6klKN58fparS9n5trTeDozBgGQMyXdZXs6IceOz6sa7ag7Z5EfQc/zjVODbY+E6k/cI2FwXmsBQg9kCe3Dw6MOwYUiDgBqJ8eKPLNccUw/p/a+BFW1TfKZLZgTZUxDQOfYmcS1HY7CepnFpbUpoHsXL3dt9JYZkQtPeI9GgFw9w+KPYT3Hqi8jDxmhFuKnlMSm55wi6agzwm+RVz+diorwuhT1M9gl7TyB6u46MYHd7+Fx6IOb5NISVBg0NuUojLumZGYJsmvpTx166g0zqAdDciMuZ8Lla3BrFK43TSej/T2J1XU8POoMPHnLVti1PNXkpHS2o+PuuuwoAW3FtOsFuUeDhfJoUtaFZK/sto33/YaVHg0GbgbCKDlMyWn63xHfM69NuGLuZhhO1UF9AMqFl1xlh4YPJ5Lp5lu22m959Dw8GgiBeWl7281n6Qq3yymnrsUEz+1WaTl7dR27R+mhNtv3n3yq6vCs92gsyDTc+JKmwiS98jqOrkrZyncSprKdVO2pX8CsyY73i/hdewBRG20ak3GErtUE1W3sux4e9Y/AdVPTgirSycQW7ZBzw0UqU19wedtds+/Mq4Q7zgrHxaFFutOuo6b4LumKJ79HvcPhyEuXf0n7XZC76WqylvY0Sp+s32XBJ2tNOuMSZWIxHpVVIUl1TyiNQSf4xP3yrPeoc8SkT7O59VOX243eT4cO5WmvvHpbO/vcQwrtg3LuTaSW081vnGF3axOO2LQwY4YeHnWJmPRmUMtGkth6KStX4C4p/6l6T6MELtWd1kG9DPFTYsMbar3QZcz5BETKO8Ai6T+RxuLhUQ8IAJtcbiTLCNhhNXrtqifNqQYAaMpjzhV/GV9u+9K/JWpW/ZAcpUm2rki8JHAs7YndL/PwrbiBT8rxaBAEAI3A6ysb1MPPGKspXdUO+5nWuNYUZn7kQ8i0tRnvthx+OEafe85qXcjJOtFkgXjwieYHCIa4X5TscRVE7Y+/Rqh71XUdD496QUBtZUVSJVfT4uBCKCnrSpSZOE9PPRcA5nzybywbO3qjUDDa029FZ2QTy3gGnbCfEc1A2NoBnXlHtBOfe+9R5wjcwbNk0C4JSqGka60addRbcz71ydQy45s2yXqUZIecDEMJraW04ay3Fs+MvoC5ZLggqr/WFjw86hkJR546V/I6jbzJLHhXXp3rqRwuZn/qb6t2LKyEMZEFACGipbBJ+E1uV+fyvKswHBmSUhx55jp+Xrn3qH8YcXpz6Ur9241kzF297VLmqd9Rpyc0AAAgAElEQVRg5oc/XLVTY889DxUf0GviRmYF021qjzzJrDFi8qSrTEUAzP6res2MQA+P+oWVnDPZP/ykUVDdDSjQctQKZNrbnKUUBm7+pV5Ak7ams2jAmA4a6jbMIKF25rFIb5c3ZL06cYfRMcPb9B51joj07lh7rah10gpjDF1vPK96oUpF+/WEMtYptQm5mfYpmL5AK96u0nGpkyLWEpQLk3lB79EQiKfWHhzhbRU/DbL22Z+sbscDwM7vXEc4KWLPe+x0E0yf66CdowdqFRwS7WdkgGLKJxC79mlXPTzqFkH16PyrBYHe97+vppLlwcHoFSeNpUyO4vH2Jh21fYXQe+OpdxhibcALe496h2PCzcSYtDDkHNnp0ydRt0jetDLqkj2xesXMo0zb1QMFi7UF03npBb1HvSNB+tdC8s/527+puWxyf3t1TZjPmNobQ2flKFU9zsax7XSSCUjCd6bLwFPeo/6RIP1Epq1lJU/YQNuqVTV3pqm5Ccf/+7+Qqs1wXMzpSGKTZDodqlc9o4MCU/F4Up0aXWi2n0C0rr+HR/3CuYhGVRAduNpyVQqd55xdc9VdvdPR3NKMTC6HsFQiBFXhtSjPntHQmpWDKwAwYZBXlY+ddqp8zHdBtAlv1XvUNyZt08dz1atk6yn0Xvb+SdWdzWYBAKdc800Ayg6n7VLPfUR85X0TxAlvePbVe9bzaFBgjGgTidCfh0f9oSrpJZfS0m2qU14AyE6bNqnOXP9/vxafd608ClR3VyE8al7EKru8iowBpm1+AJzRDTuSaXp6UHG6ED086g5Gco6NmEQRkrZ8OkVmXHrppDsTVir4yTevBwCs+MQVsh2mQ2qK8UyRXxB5Hk2NjTP1RGQGQB55NBDEIb9Ia1D3Eim9Hh51ioj0tWWm6Lw9s7wKh9FBINvbc1Ad2ts3EJ+//ttfjavUnnlArW9nED9W+Zn8Ick5oRovomMooq19rLwckHo8POoVjtx7hbTUXDOarWe7aSnZfNiyV9Spq/7p3wAAQXMzMvkmMqioNk2pbqYBS6Izehl1VNn3LK4j0iR8vr1HA6GKTZ+0gu1nAJyOr2kXXviKOgUAe3b1AQBOufrrOtSmYu+R951NwFWtj6ihIdIPIvNAiXn9pa4kAQ+P+gJPyvZaENHkNeTHjd/67/h80UVvVfIZNLZO976p2ntGt+VgUS6PlYXnTXmPBoE1nx4IOPD+BQVcs/oAvnnMCC6cVUzwwcxnmThWXysyQcZqR9Y8781vTE55NTJz7HNVhFkhPBWm029QM8DLeI9GQEK9v3xBAe+cW8CCFoFlbRV8bPE4zu0tGmWMee3WkND1loNX7TNB1ri+4d/+i7aqmow4XINoZm57X6+XZxWfdI89PA49cPsP/YzuYqLQGT2lxL04wgWTLE1z5x50Z5pamo3rsZHR+HzZe98dS2apjtcql4Vx5qW5R6OD2yRwOeaci2QIk+zKw86bm5Nla8Ty1StTn01ZtiTRfjUSC1LGHpxc7+i6vLz3qG9wO9t8TV82UWhNf/UU/ThGf5B8yeXzaO/swPzDFmPZqqPQ3tmRKFNU8+xVm6ieSsNg2ezkif2eOQh4XcCjvmGwWQjgmo15FCrACdNKKAmOO3ZncfuuXOLF5PJUtXvCZsydidaUdfLOeOv5zvtr/0On6NqbbZjkNlLsdIG4m+ZmXK+eG9LD49AAO6pnhWARUdKkZlpAzFxfXmLupz/lbogzLFq+xPmsVtz34StQHh1DmqIu+6mfCUDPrJO9ICRnMp03dkbqup7e/fQr6qeHxx8zAgiAcZhbQEXQt8iZ0FNVNarn4i86fMmrslfc67/1NYxs2YZHPvv51HbpTj2yv2ZYTxFcbUutrz08GgPc3tY5Jgs5GnPZGB0gdHaciza5phwWH7H0Vd0csnXeHJx2/bdBM+jUmbLVqTZPpwupLazot9Ge++k2Ho2AhPeerkpDSWDmxoh4Ukvs87bS2mbNn425i+a/Jp1mnOP0/74mVTq7nHQMLB7UGLmXjOJ7eNQ3OGWzmjhj7+pKF61IzE0XpFx0MW/xfDS3trzmnT/s/ZfKfiPpk08qF7SEaRaoXXS8pPdoBPB48QjD2a1Xp9GT50w1OnoZYOYKOrPmzUY2n/T2vxaYddrro04CAiEM294IJiglnsUqvSnhk7vpeHjUK2L1njq5GZhTUkqI2NMfRmqAetI0fRqa2157CU9x6nXf1gtgMBaLeK3Cq9/aejccfaQuL+U9GgHcnshiz2tJLpDBZN47NQGi44n/8a+vVT9TwTN6kg41P5RGQm16WPcQP4vedzzz8Kg3BDEJhDn7TJ4Ip0QEE8bgwACc+OUvvqYddUEttoEFy3DYphdA1XjAIjxJzFGgKj+96+FRz+CGxKZ2vUgG4bR5byrCAkC+q6umBsdGRvHAbWtw3613Yv/ewYlfqILeubPSehhfxT2kDsv4Jy1J18OjfsGO6jlKmJ5vwzefiHvTu+r+8svfi5mvP7lqQ1s2vIzbfvBT57MFy5fg3He+9SC6r3H3pZenhOpM56PruygYfEaeR32D61VgzVx2dVcdTbvX1AImIvzvbr49JvzzN30ThYduROGhG/H8TXJ9+03Pv4hr/78vv6IPaZ09M9F/her5gia8cu9R7+Da4e1Si5NgKedpKJfKeO6xp7F8wWwUHroRC2f1AgCefmETFvQGGH/gKixfMBuVchlPPfDIQXyCxOu+8PlESJHCk9nDQ4IDjJi75mYSNlEsHz4AINOUr9rAd/5ZSvCnfvTV+N6B0TEc9+6/xcPrXsZP1zyG9Zt3AAB+f/s9B/URNmx13uWoS9MGPDzqHYHeCdJNhDQJqYjVc+yxEzYydO//GNer/1zuYnvq5drj33/X99D9hvfU1OmDxUTf4+HRCOA6qdadipq8Z9JjyuFLJ2ykKWcuzHH1Zz6SKNPxKiX1pKXSasJ7me7R2HCue19NrU+nf+04/dij8M7zTo2vCw/deJA1TQy3Ey/NgPFDgkf9gwN02olJA3ltprVSMDCgXDmohr/7uStiL/5kUC6WcP0XvoZLZgf4zLG9+D7Z9NKlvrvTbF3x+erqv4dHvaDK4nfSajcn0Np56wKDz2/AzNNPddYAABe8/x3oeP07sf++/0ktAwAdr38ngqD6WnxxBh6A7//qQTDOMDJeMHpMj7rH6pTOwqGlJ95228OjXsDT5Z9b0VUUUYmuux98uGoDM+fPRaFUwnd+fmdqmWtvugOFUgmXffbjqWVuuvoG4/rbP7sH37rxbpzx1jc6+2wuniGctFYbXXl4NBI4YMo5mwK2eqxi+mFiSks6Pvi5T+JjX7wa0854d+LZ1NPehY/+61X44Oc+WbWOt/7FJZjW223cO+qE1Vi26kirt8n0IZlSHG1fTb7GPcHGy3yP+gY7svtIwZjtz7NTXJR8F+DxEEFJT5eWtK+T99JmurmdbdQVZyfV1viR0JNr7Lpd7a7dvXZS9Xt4HErgbvXWdt7Z01I1iZ0z2mATaWKSJjQKcEv1ZoleVUMyD58ZmgpzED5tEo6HRz2BCwi5RJbjIVWRk4RLLoY5EV1MR1v67HWHgm5N8bFjDMlzV80i+qXIbvc/vUceHvUD6chzTKOVSMbktZqcdILR3Pf0AUBTK7mFZLI11Y+JF6l2GwfprQMufcDT3qPeQeL0tYEZA4GbKG7nmKlIqyHDnerDrKMLtqw25wIm36wWwa+1TQ+PQx+8OuXTMtaSJLbLJ89srcCe+JI2AZa+b0/2pdqGSzmnibc2mT25PRoTkdtewE0aCtuFZyvxplc9Pco/EVwqt6ueanWZXv50z4GHR+OBa1lYTdKazrJ095ct320pr9upVqNGteTYahKePrf76dI8/ADg0TgI7LCYifRwXvK6upbAYObEmWkyE9nurnN1XUs4MN1l6OHRaOAuST6xmm9Ldtf7pkStHkyrVn/6oFJDgA5qwNGwNYRq3+LhUX/gbjU3LRmXBuRMKWuaCa6Qnj0IpBN14uCbcs1Rs8FtZtBSZk3uzATv4POod3BhEURCWPI5Gc4ypSyDno8H8iTdhnYlwLp9C+nmR/LK7icdRNzRA9cTD496RmCGsyiVJ7bRbSQHCkps4bi2y9shNv1M6wc0GTg5cCSHCpPcshd0n3rauzSnoYdH/cCaaePKpaO0UD90lr1y0VHVmBllATqjTV+nt6la1NpD0tOg2jXfZ1A7eCQn04r4bjK06Anv0SgIqPyl8+cUlDy0VWAljbWspHZ+Ut4q9V/T1LTDNRVtiW/2yMzIN/ti30/2QZsc9B0B93x7D496RKDIl1xQwqRhkkSKmJq8piSlkp7Kddvpxqz3aPuu9myyp4EGCalGYnvv0xyOHh71CU7JHcayuJbwmJKbtqS2y2ikeQHc902fgNul6HIw2gOKHnj00ETbqOZw9PCoPwSarKZbzHZ0ATDoY1PDdLWlESfN5tfP6B7y9L45Tz8ZJbCDeLaJIKzytHRS+/DwqF9Es+xsLzni62pnrqi2SSBTE4Dxpgt67X2zrOlMdBObDlJJR57yI9hDjFnCw6P+wbVTTYMSlyXuu33fE0lKTTJ7EBCw361eS1KlV2/Zg5Ct9Ku7aTa8l/MejYAAsF1tSFxRinzv8pcwZ3oZQ2MZFHkbKq1LUKhkcWBU4OmXy7j5nr3o259N1JokpO3lT65iZ54nSW1HCtI98LWo766ov4dH/SFaGHNi1VaRoaMpxDfftxVzlrZjytQs2NxLga4TgNb5YNmp2L/rBbx03w9x268exG8eHsXQaM543w6guYYcq4sJ3cDdWz1EKJ+8ujazBe32ku37hTE96hkJ0lfzYSuKNudCXHf5RixZLhDkOCrTzwRf8AGwjsPB8tMQFvdjdN92PH/PD3HVt3+JR17qIHUnE3bpQOCeEWe642xno93vpJaQ9jXJbwMY1u5+2lHew6M+kOlu7bkyWiI2tnbdzjxdplzheGJzM143ez+mdOeA8R0o99+HSmEPhGAQ5VEwVsLUOfMwv1tgaNtabB5oip1psNrQrZqOORoHcOkClOBp1r45CGitwY7a04HnI5/8cOo/mIfHoY4g6SnXZ6aH25yE83JfE+5a1463zAgxtTsPVMZR2XU7in0PQrQfAbQuQshbseDoZThxxa+xsW8UW/fQnWkZqdPdNh0ebN+87dOn921LX1M9abcn/QTeqveob3DbvWVHz9PcXwLAf/+uG7s3j6KIdlR4EwQygCgjHN6AUt+9KPTdi+KeR7Hq7JNx2vI9cGkNroCevEMThezYvXpbDwjMuqfLp3kTaBaia+jx8KhPRNtamXR0h73MOwzASJHhlic60bejgDKXxA9ZEFUrwFABQwVBNoOOjhzyQQlm/D4ZuKN9SLftzTeSgUCTzOl+Cnf7Hh71jJj0Nkz5SgmkAmgAA8dNj3Zh16YBFMJWVFgbQtaEkGUhGAfAwESIDA8x97BFWDh9BMpWp22kp+oomHkDtlpvlqdDADVSdL+TKn0yeu/hUa+IptZqIgIm2TR9dChM28YCpQrDD+6bhk1PvYwib0eZt6LCmhCyHAQyEIwjG3D0LpqHw+eMYHonx6JZOZkVBAY5NFAHn2wzJH2wrXyADkUmXfVAQomv66U5eYIMAl7SezQKuJKD9raU8ofKe2YRXnvd79vQjsefLWLXpj0YLregwltRFnmMlTIQCACWQSgEstk8vnHd/8XVP70Bl79zBbJBWIWkZkhOwXbU6eEo3SwwV8cX5DtsncPDo/7BbUnHLOmnCWPuLsegtquW965e040tT63H+JjA3rEciqwFyDZj/xjD0OAo7vjRg5i15CQMbHgA4/t2ItvSjiW95YRaTYlruvLS1Xu3pW9Cz5mvlqjj4VH/sPeoNqhN3WBuO1gfKxWOb/ymFy+sWYMDm7diuJDF8HgOpUIZt9zwIKbNOxadvbMwpacbO1/4PcYFQ1uujIAr3YG2puW8HUdPKvq0725HpP1NtiHDkK4leHjUG9gR3UcKzpIz0uywHb0PUHKY0jKbCXHeyr1YPmsUFZ7Bjn3t6Jy5AitOWA0hGF5Y+wJ6DluMXTv6MKtnNna8+Cx+cevj2LovhzBMyl537D3ZL3lNtZKUD4Z7AKPwabge9Qx2eER6m1Q2MajqX036U3rOn17CmcfPxJlvfx8Gtz8LlsthNGRY+9BanHbWiZjWOx9d81aif+d23P3j63DTLx/BjqE8qckcAl6pUm4n7Zj+fQ1Peo96Bnelx1Cb2XajaeeXnVFnvy29hIXxAp64fw2Gyq3g05Zj99adOOuNp2Bgx25sen4dimN7MbWrExd/4nP4t6v+HRe9YQaasxWDlGkS3j53J/EkYav87m/18KhPsCOsCTfpqrObdNXAmcCJy8bA8k1oac4D7d344Ic+iJ0bHkHr1KkolQWG9hZwzBlngfEcWrtmYmT/fjxxz6/w5X+9GtsHc2Znjb6496w3tQC3TpAu4yWe8ZLeo47hTM5xJ71Ul4Yu+oSC4YENLXhhUxkbXjqA7PBuPHbnzWidNh+zlh4LjgrmLJqOR+/8DSrlMYzs2YYpU7tw3FkX4MvXfwOnH9OKbCZNert7YlK52vCUHOjSvsPDo56Q6W7tuZIxneJSu4pr0quaZ3+kkMHQaIDWzBimTmnCgYGdKIyOYMGKEzCwZQOmz+rCjk3bkW9ugagU0NzWidb2KTjpnDeirfQy1q/fjEI5SDj4XO3J8/R+1YKPfPIjB/GWh8ehgcz01p4ruUO9p3ATh+5SX23NGv1sz0gG0zP9WLJqNUrFUWzd8AxmLz0GQ7u2oL2jGYXxAkZHxpDPMYTlEprbO7H8uFOwfNEUPPnAAxguZhN9mijMlnRGTgxPeo96RrQwpqm61yodaZZ7ehn9rFRmeGKjwBP3rsG8w1Zh+sx5eOq3tyHT3IW5R5yMsLgP+VwFL659BqIyjrH9u5HP57DqtPPxle9+HccsyZKgXLIvNiajuXi13qNRwF32vCtO7nrOHOVt0Lx6ANh1oAmbtw/iwV/fhMWrjseRJ78Be3Zsw6O/uQk9C6XUn97biuceexwiLGBk73a0tLZg5vyF+OerrsK5J0wFZyHJ2tPt0CMdbmqJzXvPvUejILbpFQIOvH9BER9dPI7zZ5SR5cD6A5n4uSvjbbLoH84hN7oRA5vWoqO9CYedeBbG9g/iud/fg7nLV2Nw50uY1jsNO7fsRFNLM0R5HO1dM8AZcNyZ56Lc9wQ2vLQHFWEmFFLii/i39vnzZAJiAgxevfeob2Smt3bHjjwA+NCiAi6eU8LUHDA9L3B8VwV948CLI4r41Y0AW7LbEABCIYnfUtqOIM8wvncLZiw6DF2zFmL9o/eis2cBskGAbC7EyP5hFApFcJSQb25FkA2w8qQz0FrZgqfWbkJZZJztuPpRa5qtJ71HPYPbm0C/obucKHRmbyU+pxnxOt6tIRz39H39ZqGUwZPb2rD2ocexb88ebH3uIex47gGsPuetGOzbgd1bt2Hm4tVAZRiojGHz+ucxMrgL4wcG0NSUw4WX/TX++sPnozkoxvW7oHrLwch0XVdKj4dHY8DY4SYE4FoNmwlNjDB23dlLTU9sN9slB8fzeHZnCx5a8wAODA0ik89g/QO/xOKjV6OprR33/fwGTJtzBEb37ULntGase/hhGc/ftxPNLc047a1/jk9+/CK0BCUSSaB9kn0MSd/CuCevLKzn4XGogtO95xiAu/qCRKG7+jPEXpbynVtUSZsUEzdEzmk2Xd9IK17uz+G3t96NwT17kclzbFz7Wwzt2oBFK4/FfT+/Aa1d87F36ybMmDsVT93/ACqVMRwY2IIpXZ1YfeY5+OhfnIdmXiBJRGpg0t/FrH6kbdXppb5HvSPTQxx5AsATgxlkGNAWCPQXMvh/W3O4dWfOyMqbaGmpNG95miYwVGxCWCliz5b1mDl3BlqmtCNoymFo92YcfcbbsO6Bu9A5Yx6G+7dj+owubHp+I9qmtKM0fgDTZi/ClGnTkS9swfPrd6As9KCVlmlo98M+9za9Rz0jduQpiR+C4fHBADfvzOGWXVk8fyBTNYQHpJFIxIODHU5T71Ppv7/YDFGpYOClZzBjbi9ap7Qj15THwJb1eN2fXoKXnnwILNuCabMWIsNHsGvrNoQAwtIwZi8+ElO7e1Hc8Tg2bR82iE/Bo0Qh1a7sW3Io8qT3qGdkeqLNLuyklzQpbR/hOKqr6pJeJNo8UGyGECEGXliL3rk9GB0ZgwDD3h0bkGECPNuCnS9vwBEnnIvRwS0YObAf+/r6wVDA1O6Z6Jm3GDsfvxU7D+QgImrbE4WS50mfhCe9Rz2D27Y4UD0V101w1xRceaTZfiohlxlXMKi/baQL24an4Dc/vA3l8REM7NiOZx9/GixbwXD/y5g+ZyHu+p+rMWPRsciyMlraM3jsnjXo2/w0smIIx5/1Bhw1tR9yMS97113z3NZYvEPPoxFgZKtQKtrzzW245trbKbk6QUZL1fRgn5bB20enYdvwFNz+w9sQVkrI8Apu+8HP0TqtAwNbHsfhrzsVd/zgm+iatwKF/YNYumIx7rv11wgxhkVLZmP1ya/DkrZdk/l38PBoGDjWyJNwO+vsxTF17j2V1ubOM0kvv12/KZHl2c7x6dg4MgO/u/kejA2PYMHy+bjxW99DvqMF257/HU664F24/2c3oKNnKfbt2IbVpx+HO350C1qnd+KIY5Zi5dFLMbtpt9Wq2Y/0aUIeHvWLBOmrzZizkZxnX92vrxJ3aq1/X2kKXhhZgCfufxo7Nm/DMaeuxpqf3AqRzeDFR2/B6Rdfhifv+RVaOudh77YtOOXNp+Oen9+OzhnTsfr1R+OIBe3oDAbhWt8nrZd+GPCodxikT/OyU1Lb5ce7xrDlTzdj6xu3IMxVjOfUBFC+AwZguPssbDrme+hf9NdxCNCe1KPORsImPDe8ECOPbMPgd+7D4c0zsf3lHci1tWLdvT/C6RdfhhcefxDZ1lnYu3ULjj/zONz/qzVo6ezA6lNWY3n3CPK84KzdRX0v/T3qHakzUGzvvFbldZBrdOYINr9lIzqPbUPzkXlsO3uL4biDVYeAwN55l6H/iM9j/pGrsH/uxdg3+10pTkDd8rEH9mBefxkzW7uw75aHMaPcCsbbMX3+Ejz7wE04/R0fwI4X14Hnp2H8wDhWHn8Unnn4cbROnYIlK5ZheUcfEDn27IFMax8Ck9FCPDwOVcSkVzlylBbVvNuFjgK2nL0FHzjnMtx3yYP4yoVfQXl+GQPH9MVl7UU3xzqPw77578N//kUbbvk08PG3tWLP4r/EWMcxVsaffmfu+BAWF4ZwwbXX4IK778aqt7wVm666CeW+MbR3zcLMRUfg5Sfuwhve/RHs2bUVw8MltE+dh8OOWoztL29C7+xedE9vw9yWgbh+qnVoRyMz7np41Cu4phiNV9NAXlIChkEFm/50E04/8VR8bNVfYl9xHxZ3LsabTjwfA6sGwMhQIkklUMpPx47l/4hPXNSGUw8HBkeBC1YDq5a1oH/JJ4xOqdZaKwUce2A7zvjYR9G1ciUKfX1Yfvnl6OnswlNfvR47N+1Ga8cM9C48DNuefRDnXvrXCCsVvPj0k1hw1OmYv2gmxsdGMHNhL9rYHmRZOSVm4Inu0TjgVMU1VWsJU/LL833L9yE3PYMPrv4g9hT3oK/Qh/5CP06cfRKClgz2zduHclhGKSyjFFZQCivYN+ciLF/chguOy2BoDPHPuccIlNsXo9CyGFrhlr1YPrwL87unY/6f/imKfX0o9vWhvG8flp55JnJ7x/H//uObWPfwY2hq6kLP3KXoe/lpnPb2D2Bqzxysvf9uHHP2e9E7Yyq6erpQYDlMDQYB2HY7A9VwPP096h3cDquJxJkU26ocywgMHNWPk153IvJBHv3FfgwU+9Ff7Edbrh1zl8zGvj/ZA7o1ZZjJY7jzOFx0ehcKZWB4HDgwDuwfBxb3MsydEWDv/EtJK0A2LKO9OIKjzjoLpT17UOzvRykifueRR6IzCBBsC/GNr/0Pbvnva1EcE5jaMweDO17Ecef9H0yftQBP3HUrjnvTR1DJBOia04OpwV7YlFehO6/YezQKuDlJNvk/HYmXv/cu2IdMJ8eCaQvRX+xHf7FPHkv96C/1Yc6M2ShOLaLcXoobOTDtFCyY24Z53RwjRWC4CIwUgZECMFYCVi7OYWTqCSiwHMphGeWwhBmj/ZgBoH3uXJT6+lDu64uPYv9+LO7twbyxfdhTmIrv3vwS/v6jf4X7bvkFsrk2jPRvw4qTz8aUntm47cYfY+7qt2DpjHYEmSxcw5rScUyfhodHfSIQYGS6qfyt8+gAO9N+/5IhBEs4RjGC/nI/CpUCSmEJhbCAUqUIluUIpmQwPnMcTcNNAIDxGSdgxcrZqISS5OPWT0crR3vzGMbbj0LL4EMAgKnjQ1gkQoSDgygHAUShADE+jrBQAMbH0RIEyACYUhzBnlwr1u/twn9e/Vsc+cs7cPwbzsDCo47GrsEixkUGGNiCoUGB7WPTiKPQnHjrye7RKAgAM4Zu7lSvoagfBhXwJoZnRtdiRssMFCpFFMMiimEBxUoRfeXdYNMYxmeMgb3YJWsSIVqbM+gbAfI5YLwMFMryOF4GygB6ejqwe8oRMenHhUATgJGnnkJmxYqY9FDHwUH0ihBdpRH0ZfOAAA6EHA9tacYT19+Jw+esgZjShbeecyruu+UXePy5fgxWuuOv1XP6dVqRp71HIyCeg5rc5slcEkM9DXkInmfYWNqIR4YfwczcTEl8UcRwaRjby9vBmhnKrWXEFnNYQC7L0DcM5AKgKQsUQ6AUAqNFuZpNRxvHrqbpcaslADkAo488gnwQIGhrA8bHIQoFhHv2gA8Ooh3S9rcjDwW04sltQGbrIDY9fyNGwnaEmAa5vr/ptnNZ+B4e9Qwy8ZxOhQHFA9QAABirSURBVKF3NS0EgGAsQGWoBNbJ8cTYE9hc3IxW3opSWEZ/cTfCIEQ4HiI3kI/rzJSHsH9oEFM6WrBjP9AUABkOFErAcAFobQLC8iiyI5uR4dLuLjKOIVFBR6WCkfvvR276dAT5vJT4AwMIAOwHMJTJIgmpvJdZDkMVtQuuXCgrwzJxieS3e8J71D+iveyY07K1ZT0D0PvoTJQeriBkIUQgcIAdgAgEpjR1YEHbQkxt6kK4RaC5vzmuZ+q23+COX94GxkJkOFCsyLBBRxPQ2wl0tQM7Nm1EfuSluMW+9pn4GeMIAGSFAB8aQsAYmqdPR9vSpWjq7sYzjONA0IwMy4AzDs445CpA8nt49GWcZRDwAJxlLIU+LRPBw6N+wfVaccrWBUwVmEbxgabBJrRvbkfp9gpCCPQ092JOy1wsbF2ExW1LMHd8HnJ78ujY2gHlDmwe2w42sA63/OwXgKhgSgswrRXo7QBmdAAY24vC4Da0Da2FkrqlfDt2Bs34CZOr1Tf19KB53jy0LFmC5sMOw8DSpRhobsWBfHtMeM4yCCKCy58sMjwAZ9RVac71N8OVnvwe9Y9IvXdNdzF9+FQPmPnwHOwu78Do2Cg6zutA7/xezOSzUO4v47l716N7TU9UjX6ne/td6KuM4Xt9fXjHxedhzvI5aM5U0Nc3gHvvfhzt62+w+gEMds7D/fu3YUd5DJd2duKIGTMg5szBViHwg/UvYEO+x1LI0yhrTwc2Zwd4J55HI4Ed3n24UCoxlXtmKm5c3LgennEA4yvHMGvZLORZE/o27kb2rhyyY9lUEg23zAabeyxmLlyGzvYs9mzfhaGHf4ygPJzaHhsfQjcrYPbcGWjO5rC7by82FXKocGXPUwec3XI1B6Ub63Y/U/W5h8ehDHZ49xFC7XCjFV7q3aby002Y5F3lGEvzEdDnLrJSkroIauYOmKhFZtvr95h1edJ71DMiY5dOOzGJqCV+GrVdNKNpPqosMwYSPSBMTFL3Epv66EoihvXEPYNOOMp5eNQ3uCKe6cISVYjmuuMKeQmjBDUXdFs0JcheoEO/n2apuxKFzSmydk69OdAkM+49+T3qH9yWmlTea6RJY3u2GtUK0qaw0AHCJrYma7r81+nBZlyB9tvMr6dRiGSPbO3FE9+jvsH1H7mZgU8XmTCRJhkFhFDlqw0S1H62B4bku0kTILTecpkeaTa/XgvfbivdVPHwqC8YNj2FzMFn0ERRJEmSKVbWmarLJS/pEBJCIERt89qUj4GmEOka7StzQKGtMwiyfaWtkYRIagkeHvWIYOIQFrWVbWef9vbb5e3IeLQnrlULfcetVmsb3SwTGqp6dWNADwucuClNc8Yr9R6NAs4gIIRrESkq9TRBTBuZHvWb7vXmXBKY2vdp9j911dGEGlfJZKhPDVlKinO4BpwQHh6NArmtFXNtSeFSlU17nBn39ZlwDhguuJyF1W38ZPTfLmlvm2n3j2oc6lmaj8HDo/7A06mZZt/qN8LE4JBWlt4hlJ2E+UwHGNOJZ/bJasGoQR2FIdknGmQ8POoLqeveJ2HpAsI1XKSH6Iwr9S5z5QK4Sae20k6Wd6NaHIB5Xns0MIzFqqvDst0Nk2AyAS9qU1cLBybfSx8OJnrXaiEx2Hh4NA54NcW+doFYq90ur/WAYTvVXKFAQa5s+1seaV4erWkiavtEHI9GRKCo8ZGR/j9wV9LgcvDV8o6rfHpo0MDnPjeJtv6A+Kd/+kP3wOMQRMAgCf+64jAeybVOUPxg8tbceQDVIvPVHYi1olpW4AS5CeIQMPp/+1vZzyuv/EP3xOMQQ7xG3iO5NnyztTt+YMvX5Mo6rkj55AwCZtQzsRQWgmb9TWRSTEYzMAezjxwKRPrc5w6Nwcnjjw5c/9mYXnjTJk7fAaaWrDgK0+3mSt5J9iU+YyY5X8mfvHAMax4ejQCHI8+diWeSkschOztXzqwniYnDbtWu7exBV3JPbU5FM7Golnc9POoDjjh9mgPMPDLGCAFZ9MiW3AdDIkeWnyAz8EmoMJlDn+b0q6UfnvAejYF4q+pk2EzbxcK4JldM2/hS864Wd7dbUhLWlRFnpgAzpg0Ocyiha/LLqb3CWZ8qYb4tQJOMfAquR2OAm9NWaWycEEQkreikLW+vvSNIXeSZUL+YRTpVkx2rD40re5iIV/STo5BFeQZTmTHfZlB+goMJC3p4HJoINCklpMBmscbOIlUekASlyWySsCz6vzDksL2efHwVe9+jS8Yd72hyJh1+tE6m32PqroZJb3sqLou+xxzsPO096h1RyM6aE8+SG0G44JKSVG5rSlr0EyIaKBiECBNe+YnCeEl5TTfbtsqqOJ9QfXb1n5GaPDzqG1zGeomKLmwlm2gBCXKaJeWV7Rc3aSTAwBiPyzAjD55Fdrm7bjoU2dN6FWHtJT6V34ExFpPcNCiIFiAEmI99e9Q5eMJCTkxGsexkixPx+rLGfWadkYGFDDLKKy/I+4b2YAxIsjZ7PVvER73JtmtzLpB+uhbbAKRGILx+71Hn4O4JZ+496gFFykhiCjLd1TFfVSnNBm2pca/s+0jd10+id5K6etwuYm99Uu8wF9g2F90wtRVm/Uxs0nh4HOrglDDJwF0aAYRFSkY8/PK5/u2+o5e7VLPuzEEjabO7BiBAMZ8aJQntgtTjaiFZ1sPA+DhwzDHA6tVAsSjvXXcd8OY3A83NwD33/OH6tnkz8NnPAocfDpx++sTlXd/yauC1qvc1QBzPUtaye737iVesVbZzTE9BnjkGD9MiT9ZvWeaRXU499dF9Z3g96Weo1ndqXjQMvvY1oKMj+kdlwNSpwI03usvu3Qs89RTw5JPAvn3yXhgCpZL8Y/9DYudOIJMBnn++tvKub3k18FrV+xog9t5ru9hNEOqbt11zyXv0naSPQB3tja0Sq+MIQDDqXTd3vzNde0pamz4K6qwz3zFjBYIl365rXHEF8KEPAW1tkjQDA/LowqxZwE03AZwDvb3y3gc+ALz4InD77f97fQaAH/8YOPZYYNEieX3CCcCqVbVPh3Z9y6uB16re1wCOrapNGI6wBCuSmoEZj1d1M3JIxvFpfUZbpF47bq9yBpIuOV2/iH0F7m0yaYs0Wt8wyOXkH2kmk054hQsv/N/pUzWMj8uB6sc/1qQ/GLxW3/LH8G9UAxzLZZn2bXVprWWlGUZDrDKb4T7y3NCn9eo3sby21HY7C0AVSDMPpMmhnXnKCdEwkrwe8e1v/9GrzocCUhfGdKnwVHrHk28TBjGzi5LahFFM+82pt11Y71rSXNChgUpquto+HSKic2bfoUMAKd9Qor4G9PXJhTqOPHJiR9m//IvUHBiTWgS1s++8EzjjDOlHmD0beOc7pT1eK/7iL4CPf1yen322bKOzM1numWeASy8FenqA+fOB73+/tm+57z55b+pUWe+xx8qFSmrBRP9Gv/sdcN55wNy50gw4/3zguef0cyHkgHb00bLfc+ZI82nHDl1myxbgM5+R/3ZXXgnccgtw2mlAa6t0ID72WG19BdnWioa/3H50ZhAr9r4zwAz7WVKXuS9iK1yo77Z9/4gGBjN8qENujLwr39ffQJ2JwvIDMNKuMMcrAUeeQoNjcFAS+dlnJy77D/8gCXn55UChACxfLu9/73vA294GfPSjkui33CJJdu65QKVSWz+uvlrWDwB33CH/Aw4OmmUeewz42MekTX3BBZI073uf9D1U+5bNmyURly6V7zz1FFAum8Sshmr/Rj/4gRzsjj4a2LgRWLMG+PWvgXe9S5f50Ifkv82nPy0HkPvuA+6/X/or1MD4y1/Kd3fsAL76VeCaa4CTT5Z1P/kkcMkltfUVtqS3XNjxACAi6z3KtZ9QIkZTbukCmMb02Oi3GjRchDeOQnVNDhVa87eyBYn2QF0JiN8lNTNzwKk1TtFwWLYM+Pu/r63stddKh+DXv64lwb598g/6r/4KuOgiLZkuvRRYuxa4++5Xr69/8icyfPilL8m+/MM/SPLef3/1b1mzBhgelsRvbpYawoUXSqlbC9LqHRwEPvhBYOVK4ItfBIIAaGmRA0Rzs2776quBd78b+PM/l/cWLJD/hlu3yoEAkP+G//iP8vyKK4Bf/AL4whfkAHr88XKA2r27pu4GOrkm+iXUfy+9FVRMHgCxUyyeqKKlcSyDmUlJVbXyvuvc+4h4jMetMaMVmWUn5MhAHHNRCUbHKctHoJyGpFIdG1CjSGQMMKJLeM4fHJ57Tqqd994L5PP6/s03S0L94AdSWimMjEiJTFXYVwpbSzvmGHkcGKj+3tSp8vjZz0ppv2LFq7M46k03ye98y1v0vXnzpDRvb5fXyvygZQDgzDOlKfTTn8pBoalJP7O/c8UK4KGH5HfWEDngiPZrlVJX6upCkIAW1cGpdLQqYmlnkepNRbecWReRkAEQobESjz7TxoR2zOlOiNjjJ+Kkvli9J32WZUU8cNBBizFKfteUHY8JMT4OvOMd8g914ULz2YYN8vjVr0o1VP288AKwaxfwnve8dv1SEYmJkjAuvBC47DKpnq9aJVXlbdteefsvvCCP8+aZ96dNkz4PQJsQ9r8b51Lij45Ke74aav1OVbWSxaaDzHR4OaPXIprnLiLpDQEhkhs+2/Z+LPajTkrNO3L+GPa1iE2K2ESIameMK8+c1jGiscCOIhgOAjjMCaG/WUBEeQEek8K//7uU2N//flJdL5flcfv2//1+1QrGpDlwzz3A614nv+Poo2vzY1SD8leMjtbWh/8l8NhOtkxegGjA0X3aLcZUfryaoYZIS9BSXejboE6zWO1WdVmquao/7oe6raS5MWknFvaW6h85HpkyWUSsYah7yqmghjg1jHgA+OEPgbe/vbayn/mMVN05l46z/fv1s/nz5fHVTOJ5tdMnBwaAAwekN/zBB4F//meZYfe1r72yepcskceHH04vs2yZPL78snk/DIFNm6QPwNYUXiG0917dqfI3r8innGquaTlyCqtWzBP++shcoHF404MuXKeGZz2OGEQ/QpEb2hrRjkPVRzl3ny6pZU4DtvMDGxzPPz+5kNoJJwB/93fSE65Ca4BUnTMZ4LbbtKqvMDAAPPJI7W3w6M+1r6/2d2rBlVcC3/qWvr7iCnlUzraDxQUXSFv8Rz9Kag1KA1Je/JtuMp/fdZccPP/sz0x7/lUAJ85sQ/s2HN6KZOpSOcn0HWtFHUI+EPKqQoZXHcSjh3hscCE2RUAEe9SA8QpxBRjfEXVBWxjmPIGGk/HlspQoLmzcqM9VGTu8pu6r/3b/9E/SeXbdddKrDMi48he+IEN4Z54JXHWVjNl/6UvAEUcA69bV3t+ZM+Xxq18FHn1Uhr5GRnQ/7G9RxKL9TvuWO+4A+vvlt1x7rfS0v+MdtffNVW9vr/zOQkGG1r74RUnuL35RevQB4JxzgPe+V5oUN9wg23/pJRl6nD9flrXbsL9TtVlj+JMbqrdlVpuSGlq9js6Vlk216wT5bH8cqSs+KhtAOero+0b7jtl2kYpO/RDxYBDXL2LtItYAHB5JYV3XNb7xDRmSKpWkzTljhvlzww2y3B13SHICMvR15JHSfn/jG7V0fNe7gO9+F8hmgU99St67+GLgIx+R55/6lEydnTsX+MQnpPR64AFJgPe+t/Y+X3wx8PrXy1DfxRcDt94qE2iUl/6BB4BTTpHn11wj8wUAOeh86EPp33LKKVKdX7ZMJs/89Kc6FFYL0uoFgL/8Synp580DPv95mXTzyCPAd76j37/uOuDLX5YEnzYNOPVUaWr8/vc6bPj5z+vv+drXtDb1nvfoCMCb3pQ+aYqALe8+XHxsVIY0vtnSjWwGeO/8Ek7qKqMYMty+O8DPdwSWxNYHIZR9XxtbYqHOTE4LWiJ2xVsN2nUR09ysw4LeGscs6KpWAM/2TUL6/KGgdrg5FHbj8fijQmAyReCDC8u4aHYpvj6svYjxCvCr3YH5pogc6AyR156MBNFzdU2FvLAlq3ECmItxWKy0LmONA8reF9YoQDpB+8PI+zYaTsf3aDToHW4i8fuG7nKi0Bt6yjGBmCWeDY93zG6y7BZlu23b0+ekmsT9+J5I3o+dgdZoEhvzSRYnfQKOtjw86hQkDVd7xm3Qne30WnbQfIrPlVgntjfx9mspK2I7W2KSzHP5BpKdtvoGi//MtB4a1Znn0XBIzLK7sy85r/rOfvMe5ZDBW5eTLToa3n+jkKWCO3V++pJ22CXKWiZFopwg12bHPds9GgaBbYtf9XIWhQpw0rRK7Mi7bZcuJoU0MZyNEJhb8OrBgcx3i9V/aoTbb8GQwnTkMBOHqONAPhBReSMdVwidYhxnAFpDkFf1Peocge14K4UM12zM4ZqNDjIyeqI94oprmpNCExGUW4y+HVVFXPBOO95+phoibZgVVtEWmGa1YaektO3hUYfgqaI54VVLMaRj25zco+tY2Y+UFKYT+G3Cp6raUWEh4qm0cR+c8XvSH/uhoWl4eDQOOHW4xUeqvccOOhaTS83GY9aLaiYbddIxKolj00A+0M+spBua9QPaHz06hNGgEffBWM2DOAlpKI/a8fYYZjoJPDzqFtqRpwgNGJI3nsNO7F9jmqrhYLM8dopbIrLmGUgoT5ZnUaumcsGMKg17ndEpsGqxjrhn5vsAIELTyUhSgaFCi3a7Hh51DNN7z+iqONSrbkpA5SQD1KBAJWz0juVCZ5FTje6KoybAaE4TrSMRy9e2OPURqOm3gpoZ9vuGFoFYa5HTgc3Hnvce9Q5Nens+O7ktT8g9qtIDZFAwIwFGYg5tRoTECSjiQcGQ8LGKoIhM7XD9XKi0QLjep30ix4j4dGvtGF7D96hzcEM7p8dYGtP7Zvgrtu8p4agqDrKCTaTOG451RTxBxxSHU05pG0pKQw0WpM3YJrc1BLMe0wxQg4nZZw+PeoYVp7dIQ21dOktG6deK/LGWYL0PY84cAO3IYyrkFt9X78d37E6Q+iMTgZoWsc5P+0BtB6te12DmdXuPBoDeKN6eiQZoj3eCXILMZmUOrhKNIJaeWooaraRcCHKmF7GmbYmo25Ytb9dAyc30oGP20fGeh0edQk+4odKakjUleUUYHrAUSZmYGkvCfLFabQ8KTJdjcWni3ScdUeZBQtqbfaFKgNYzSBTBiCt6eNQ3uBZ8SYKanntKclomTSVP8Z4TZ5tO57UGC0bKOWfkuUwQF8gAkma5JOr1Kr5HfSNw3jUEHiW2w2auGcw6T3gOSfvV7HnyTiKbboL+JByGNb7n4VFH4EmltpoHWzvSYJditk/AqsMIE0Sef7ioT95TSUDGXTYpijrrTTgcPTwaB1z/+SdtYYkUgjCWVJEN+9x8BNsHwGirEy8/TSU0s5+4cutpzfaqno5aq9/z8KgfkIy8NFXZGgwsb/vEke3krjF6EKDFbJ2DOc5MDSO+Sp00Y3jvrLI035/a8l7V96hv8CQdBTkzPeuGVkAkNzN+uSRlYsFsmIMJIaNhBoCUsSMArpYY6Smpg1mljfFLDTZ+60qPxgA3mENSYU2Bru+HNC2Wgux/lyBPFFpLt6/TLon0dQ4GqowOuRF/vTWEWQI/ftcKE3p41Dm4IFlx1Hw3XHa2VFf34o0oIznJbOJTKZ6kvHD8UJjTbc13ZfVpbkh7qq5OC9Cv6oEh8fEeHnUMHlPLWlTCpUybRJEqvqEbRIkuDGaOu2kcaOmt5CsznlhOOFJeGNLYihQ4Qv3G28IadKLpfSb1vYLvUf/gQPSH71p9BtTdJQj95XVsKzOO2ANA6qE1MnCQ4YI8t8sKUrfdJzpAme8JMliZg4Uq75DiIjlYeHjUO/hEO+QaBCWrUSppqbaodvm/6UaWcndbSVZJVJaQ24kQIOmBQf2I4MLy2hsDB0v6F5zn1Lmf6oj08KgfuNfIi/74FYlckpkRmWq+Se4lWEbppaivbpjON9sJZ7sX7WgAs58pxz2DXv2HfJ1ZM91/16v4HvUNnv4nLgy5l/Tm20OCSSXbWUdeNp7r5oRVIvk+mSaTsPdpfw33XtwRsmKP1ROG5DMPj3oFtwmWfkYIJahcVOd2LN486vqS0t1lc9t6REx+ywZI+u/V+y4SJ2PxWqvwcXqPxgA3JalEkrwuO3dycW0XoYRa746E48xBKCn9BRHhaQMLfdtlfuh3Ei4/D4+6RzzL7rjSKD4abVkNVI9aq2dpg4Vr8IDjmS2l06R22jNX/9LK2L6JpAZCyn/ucym9+CPCPffIPcw9PCaJAAC+2TIdzNhQsrr0S5OwtoLung8n6VtbHbU/Sy+jZHr1bzOthkNA0T/tNL83vcdBgR02fblgxow3DZdEd0lmegTSJfxkpbpLg7C99i47nfbepZHYpegzAeC5vmdTeubhcegjoBK3mkqfhFm6GuHp/YlkKKWpyzGozqkTMa2maki+OdEXeHjUB/5/hWPBBUTcf5QAAAAASUVORK5CYII=)]]",luo_wenqiang
19616,FullScreen Mode results in all black screen,other,all,VirtualBox 6.1.6,2021-11-03T09:12:02Z,2021-11-03T09:12:02Z,"- Using VirtualBox 6.1.6 in Ubuntu 20.04

- Using XFCE+i3 as a Desktop/WM (setup following: https://feeblenerd.blogspot.com/2015/11/pretty-i3-with-xfce.html)

When I hit Host[RightCtrl]+F running whatever VM (I tested OpenBSD & Win10), I only get a full bloack screen.",liar666
20649,Version 6.1.97 r147979 for Win 11,Windows,Windows,VirtualBox 6.1.28,2021-11-04T20:44:44Z,2021-11-04T20:44:44Z,"Unfortunately, VBoxGuestAdditions.iso cannot be installed. After the installation and restart, Win11 can no longer be started in the VM. Win11 tries to repair itself, but brings up the message that no repair is possible. There is no other option than to delete the VM and set it up again, including reinstalling Win11.
Unfortunately, the screen resolution and other things cannot be set without the GuestAddition. The Win11 installation cannot really be used on the VM.
Can you help me?",icewater
20382,Unable to create a HostOnly network on Windows 10 NetCfgInstanceId failed,Windows,Linux,VirtualBox 6.1.22,2021-11-05T13:24:30Z,2021-11-05T13:24:30Z,"Using the GUI and ctrl+H to show the host network manager, running as administrator in Windows 10 home, I am no longer able to define a HostOnly network. This is the error I receive:

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}

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}

How can I fix this?
",fjb_saper
19373,VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138 => Fixed in SVN,other,Linux,VirtualBox 6.1.4,2021-11-05T13:59:40Z,2021-11-05T13:59:40Z,"Since Vbox version 6.1.4 we find the following error on Linux guests with the 6.1.4 GAs installed when the guest modules get loaded during boot.

[  386.591934] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138[[BR]]
[  390.244395] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138

I've not yet observed whether or not that has implications and indicates a deeper bug.

",Frank Batschulat (Oracle)
20651,Internal Microphone is not detected/doesn't work on Linux - Ubuntu,Windows,Linux,VirtualBox 6.1.28,2021-11-05T15:56:34Z,2021-11-05T15:56:34Z,"Internal Microphone is not detected/doesn't work (e.g. microphone inside notebook) on Ubuntu 20. When I connect USB headphones with a microphone, only this USB microphone is detected. Host Windows 10, guest Ubuntu 20.",Matej
20527,Copy text from host cause VirtualBox 6.1.26 random crash.,Windows,Windows,VirtualBox 6.1.26,2021-11-05T22:29:25Z,2021-11-05T22:29:25Z,"Sorry for my English.

I'm using Virtualbox 6.1.26 on Windows 10 host with Windows 11 guests.

Sometimes, When I copy text from the host web browser, The running guest VM may randomly(rarely) crash, even the ""clipboard sharing"" is disabled.

Here are the logs and my computer configure, If need any info, please feel free to ask.

Host:
CPU: AMD Ryzen 5 5600X
RAM: KLEVV DDR4-2677 16GB x2
Motherboard: MSI MAG B550M BAZOOKA (MS-7C95)
Graphics card: Sapphire Radeon RX560

Guest:
CPU: 2 cores
RAM: 3072 MB
Chipset: ICH9
I/O APIC: Enabled
PAE/NX: Enabled
Hardware acceleration: Default
Graphics memory: 128 MB
",chenshaoju
20131,rcu_sched detected stalls on CPUs/tasks: linux guest and host ?ryzen issue,Linux,Linux,VirtualBox 6.1.16,2021-11-07T13:22:29Z,2021-11-07T13:22:29Z,"Linux debian guest on Debian host Virtualbox 6.1.16

Host: Linux  5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux  Debian 10
AMD Ryzen 9 3900X 12-Core 32Gb ram 

guest 4 cores, 4gb ram
dmesg:

[  225.539622] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  225.540724] rcu:     0-...!: (27 ticks this GP) idle=c50/0/0x0 softirq=2529/2                                                                                        530 fqs=0

[  225.541761] rcu:     1-...!: (0 ticks this GP) idle=ac8/0/0x0 softirq=2101/21                                                                                        01 fqs=0

[  225.542767] rcu:     3-...!: (26 ticks this GP) idle=99c/0/0x0 softirq=2173/2                                                                                        174 fqs=0

[  225.543767]  (detected by 2, t=5271 jiffies, g=2529, q=2)

[  225.543770] Sending NMI from CPU 2 to CPUs 0:

[  225.543825] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.544771] Sending NMI from CPU 2 to CPUs 1:

[  225.544797] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.545769] Sending NMI from CPU 2 to CPUs 3:

[  225.545796] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.546769] rcu: rcu_sched kthread starved for 5272 jiffies! g2529 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=1

[  225.547792] rcu: RCU grace-period kthread stack dump:

[  225.548812] rcu_sched       I    0    11      2 0x80004000

[  225.548816] Call Trace:

[  225.548836]  ? __schedule+0x2d8/0x760

[  225.548838]  ? __switch_to_asm+0x40/0x70

[  225.548840]  ? __switch_to_asm+0x40/0x70

[  225.548842]  schedule+0x4a/0xb0

[  225.548843]  schedule_timeout+0x15e/0x300

[  225.548850]  ? __next_timer_interrupt+0xd0/0xd0

[  225.548853]  rcu_gp_kthread+0x452/0x8d0

[  225.548864]  kthread+0xf9/0x130

[  225.548869]  ? kfree_call_rcu+0x10/0x10

[  225.548870]  ? kthread_park+0x90/0x90

[  225.548872]  ret_from_fork+0x22/0x40

[  285.421645] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  285.422242] rcu:     0-...!: (0 ticks this GP) idle=da0/0/0x0 softirq=2535/25                                                                                        35 fqs=0

[  285.422780] rcu:     1-...!: (37 ticks this GP) idle=d4c/0/0x0 softirq=2103/2                                                                                        103 fqs=0

[  285.423305] rcu:     3-...!: (46 ticks this GP) idle=b84/0/0x0 softirq=2178/2                                                                                        179 fqs=0

[  285.423815]  (detected by 2, t=5268 jiffies, g=2541, q=866)

[  285.423817] Sending NMI from CPU 2 to CPUs 0:

[  285.423858] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.424818] Sending NMI from CPU 2 to CPUs 1:

[  285.424845] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.425817] Sending NMI from CPU 2 to CPUs 3:

[  285.425847] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.426815] rcu: rcu_sched kthread starved for 5268 jiffies! g2541 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=0

[  285.427228] rcu: RCU grace-period kthread stack dump:

[  285.427620] rcu_sched       I    0    11      2 0x80004000

[  285.427623] Call Trace:

[  285.427629]  ? __schedule+0x2d8/0x760

[  285.427630]  ? __switch_to_asm+0x40/0x70

[  285.427631]  ? __switch_to_asm+0x40/0x70

[  285.427633]  schedule+0x4a/0xb0

[  285.427634]  schedule_timeout+0x15e/0x300

[  285.427637]  ? __next_timer_interrupt+0xd0/0xd0

[  285.427640]  rcu_gp_kthread+0x452/0x8d0

[  285.427643]  kthread+0xf9/0x130

[  285.427645]  ? kfree_call_rcu+0x10/0x10

[  285.427647]  ? kthread_park+0x90/0x90

[  285.427648]  ret_from_fork+0x22/0x40

System is unusable.

Guest transferred from Intel i5 core system, were it worked perfectly.
Same error in Debian 9, 10 and bullseye guests.
Tried multiple combination of cores and ram - no effect.

Interestingly Alpine 3.12 guest on same system has no problem. 

Current workaround: install guest additions on guest and error messages go. 

I've attached the virtualbox logs.  host1 - is related to the dmesg output above.
host2 and host3 are logs from the same system, just running longer. 

Many thanks for your help.
",RT_db
20653,VirtualBox 6.1.26 fails to boot FreeBSD 13.0 install ISO in EFI mode,other,other,VirtualBox 6.1.26,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
20665,Shutting down VM crashes all other Hyper-V instances on Windows 11,Windows,all,VirtualBox 6.1.28,2021-11-12T17:49:24Z,2021-11-12T17:49:24Z,"Attempting to shut down any running VM in any fashion (either from within VM or via power off) on Windows 11 with Hyper-V running will result in all other Hyper-V machines crashing.

Attaching logs from VirtualBox 6.1.28, one machine powering off and second crashing. This is not exclusive to Hyper-V machines however - any running Hyper-V VM, either native Hyper-V, WSL2 or VMWare (also using VMP) will crash(!).

I can attach vmware-vmx.exe dumps if necessary too.",eider
20668,"Windows guest startup text mode scrambled, unreadable for all Windows guests",Mac OS X,Windows,VirtualBox 6.1.28,2021-11-14T15:57:20Z,2021-11-14T15:57:20Z,"During startup Windows guests used to show text information between the graphical screens before the login pops up. This was working well up to version 5. When version 6 came along there were a lot of problems, which were gradually fixed, but this one has never been addressed and I assume this has not been even filed here.

The reason for the textual stage is if there is something, which has been scheduled to run and the user will have to see the status of this. Typical example is when a disk check is run or startup optimizations are performed.

When this information is scrambled/garbled/unreadable and this particular screen takes a long time (see attached screen) users are lost and don't know if something is happening and they need to wait or simply reset the guest OS or what...",wellitisspeedy
20666,VirtualBox UI (Qt5GuiVBox.dll) for Windows crashes on start up,other,other,VirtualBox 6.1.28,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
19340,VMSVGA does not allow to resize guest display in GNU/Linux,Linux,Linux,VirtualBox 6.1.4,2021-11-16T18:20:47Z,2021-11-16T18:20:47Z,"In this case the host and guest are same OS: 64-bit Linux Mint 19.3 MATE.

This error has been since VMSVGA came out and it seems that this is still not fixed. So it is not just VirtualBox 6.1.4 issue but much older one and exist in many former VirtualBox versions.

Graphics controller in VirtualBox machine settings
* in case of GNU/Linux by default VMSVGA 
* in case of MS Windows by default VBoxSVGA

'''The truth is that VMSVGA does not allow to resize guest display in GNU/Linux.''' I have to adjust display settings manually in Linux in order to resize display.
When using VBoxSVGA then guest resizing works in GNU/Linux but ''Invalid settings detected'' message is shown in virtual machine (VM) settings that suggest to use VMSVGA unless I have reason to not use. Well - currently I have reason as VMSVGA does not work properly.

Also in case of VBoxSVGA the resizing clutter appears - I need to maximize VM window and back in order to get guest display resizing work properly. This has to be done after every time I wake up my laptop from sleep or start the VM first time.

At the same time in case of MS Windows the VBoxSVGA is chosen by default which works also in case of MS Windows. Actually when to choose VMSVGA in case of MS Windows then you cannot start VM as it is considered invalid setting. Well - no need as VBoxSVGA works.

My proposal: either get VMSVGA to work properly in case of any supported guest OS or remove it permanently from VirtualBox.",Edmund Laugasson
20675,The mouse cursor looks like 5 Framerates per sevond and is with the y axis inverted. (SAW AFTER MAC OS X 10.6 SNOW LEOPARD UPDATE),Mac OS X,Windows,VirtualBox 6.1.28,2021-11-17T16:54:12Z,2021-11-17T16:54:12Z,"As you read the title, the mouse looked like 5 fps and it was inverted with the y axis. before it wasnt like that! i was running on mac os x 10.6 to mess a bit around until ive came to the idea to update because last time i did it with a different iso and it wouldnt open. it worked out pretty well and everything was tip top!... except the mouse.
it maked me shiver of it! i was trying everything to get this thingy fixed, you know the answer: no! it not worked!. so thats why im here, i want to get this thingy fixed. i would appreciate it if i get a answer how to fix it. regards! 
Lefty. :] (original name Arya Jahanshahi)",Lefty. :]
20669,Multicast originating from different subnet does not reach Guest only on Ubuntu(Linux?) Host,Linux,Linux,VirtualBox 6.1.28,2021-11-17T19:07:55Z,2021-11-17T19:07:55Z,"Hello,

I have run into an issue that I now believe is a bug.

Basically, I am receiving status updates from various devices on the network in my VM. They use multicast on 224.0.0.50.
The devices are on a different subnet from the Host and the Guest (the host and the guest are on the same subnet), but everyone can communicate between each other just fine.
This works on Host Windows 10 but not on Host Ubuntu 18.04. 
Using Virtualbox 6.1.28. 

Also, tried:
- 6.1.26
- 6.1.29 revision 148164 test build
- 6.1.97 development revision 148162

All the above w/ extpack

The guest is using bridged networking.
On Windows it's using Intel PRO/1000 MT Desktop (82540EM). 
On the Ubuntu host I've tried them all with no luck.
On Windows promiscuous mode is set to Deny and greyed out, on the Ubuntu host I tried enabling it to Allow-All, no luck.

Both hosts receive the multicast packet (used wireshark on windows and tcpdump on linux to verify on both the hosts and the guests), but only on the Windows 10 host will it manage to be picked up by the Guest.
I'm attaching a screenshot from a packet capture from inside the Guest with Windows 10 as a host. These two packets are the expected behavior. On Ubuntu Host, only the first one (the direct reply) makes it all the way to the Guest. The multicast packet is lost.

It is worth mentioning that it's the exact same VM copied from Windows to Linux to make this test as good as possible.

Multicast packets originating from the same subnet are well-received.
I also tried mimicking network routes on the Ubuntu host as seen on the Windows host but to no avail.
I tried nuking the routes on the windows host to see if it affected the Windows Guest receiving it but it did not.
",idmistir
20671,Unable to import,other,other,VirtualBox 6.1.28,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
20672,During the execution of the docker pull command the VM dies,Windows,Linux,VirtualBox 6.1.28,2021-11-18T19:23:27Z,2021-11-18T19:23:27Z,"I have a VM installed with the operating system Ubuntu 20.04 LTS .
Running the command docker pull from the docker registry of AWS the virtual machine dies ",GriGiu
20670,virtual machine does not start,Windows,Windows,VirtualBox 6.1.28,2021-11-20T08:32:38Z,2021-11-20T08:32:38Z,Version 6.1.28 r147628 (Qt5.6.2),altair_kusanagi
20678,Keep opened and running each Virtual Display in each Monitor when the Guest is left to return to the Host,all,Linux,VirtualBox 6.1.28,2021-11-22T20:13:23Z,2021-11-22T20:13:23Z,"I have in some laptops installed '''VirtualBox 6.1.28 r147628 (Qt5.6.2)''' where:

* The Hosts are MacOS (El Capitan) and Windows (7 and 10)
* The Guest is '''Ubuntu Desktop 20.04''' for each Host.

The ''Guest Additions'' was installed through the '''.iso''' file. Therefore is possible:

* Share directories copy/paste between the Host and Guest
* Copy/paste between the Host and Guest

About the Display (Monitors). For each guest instance the configurations are:

{{{
Video Memory:  64MB
Monitor Count: 2
Scale Factor:  100%
Graphics Controller: VMSVGA
}}}

When Linux is the Guest, should '''VMSVGA''' be used . So I am assuming my current configuration is ok. I am able to get the 2 monitors configured, and based on extend. Furthermore was mandatory do the following:

1. In the login screen do clic in the Settings icon and not use wayland
2. Once logged go to ''Settings -> Displays -> Join Displays'' - the resolutions are based mostly according of the Host - it how reference

'''Problem''': for any '''Host''' - when the '''Guest''' is running and applied the '''Host + F''' combination - I am able to see both monitors in full screen for each one. If I want return to the Host to do anything (I must use '''Host + F''' to return) - does not matter if the Host uses one/multiple desktop(s) - practically the 90% of times the secondary virtual monitor disappears automatically - so is mandatory do the point number 2 mentioned above. - How solve this?

What I expect is that when I left the Guest through '''Host + F''' the Guest still is running '''and''' each ''Virtual Display'' still must be opened in each Monitor where was assigned since the beginning. Then, when I return to the Guest and '''Host + F''' is used then each ''Virtual Display'' gets again the full screen of the Monitor where it was assigned",manueljordan
20677,kernel module isn't loaded because the VBox drive is not installed,Windows,Windows,VirtualBox 5.2.6,2021-11-22T20:15:36Z,2021-11-22T20:15:36Z,"After several months that I used the version 5.2.6 (with Win 7 - 64), one month ago, I had some Windows problems due pc overheating and to the power source. Despite I solved any Windows failure (in particular those related to the desktop windows managing and to explorer block) Since that moment VM has stopped to run and every time I try tro run my virtual machine (Windows XP 32) it show the attached error, as in summary. 
I'm not expert and my attemp to unblock the situation, even by uninstalling and reinstalling VB, have not been successful.
Thanks for all.",marcopro
20652,USB passthrough fails for Linux hosts and Windows VM with 6.1.28,Linux,Windows,VirtualBox 6.1.28,2021-11-23T05:01:03Z,2021-11-23T05:01:03Z,"With version 6.1.28 running on a Linux Host and a Windows 7 or 10 guest, some USB passthrough operations fail.

This was first reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1192338 where the reporter noted that he could not attach an iPhone to iTunes through his Windows 10 VM on an openSUSE Leap 15.3 host. He also notes that when the VM is closed, there is no power on the USB port until he reboots.

I further tested using an RTL8188EUS Wifi dongle passed through to a Windows 7 or 10 guest from an openSUSE Tumbleweed host. In this case, the Windows software creates a network device, but is unable to complete setting it up. This operation worked with 6.1.26.

I tested my setup using the Oracle binary RPM for openSUSE Leap 15. It had the same problem.",Larry Finger
20685,Ubuntu VM crash,Windows,Linux,VirtualBox 6.1.28,2021-11-23T13:57:48Z,2021-11-23T13:57:48Z,My Ubuntu VM crashed for an unknown reason,mediawiz
20687,kernel module isn't loaded because the VBox drive is not installed,Windows,Windows,VirtualBox 6.1.28,2021-11-24T16:26:51Z,2021-11-24T16:26:51Z,"I used without problems for about three years VM VBox 5.6.2 on an host Win 7-64 , but around a months ago the pc has had some malfunctions with fan and power supply that they caused problems in the management of windows on the desktop and the Explorer block. Moreover VM Vb has stop to run, showing the message enclosed.
Now I have fixed any HD or SW issues and updated the VM Vbox version to 6.1.28 but it still doesn't work due of same problem: VBOX Drive don't installed.",marcopro
20688,invalid destination port,Mac OS X,Linux,VirtualBox 6.1.30,2021-11-24T16:38:05Z,2021-11-24T16:38:05Z,"On quitting a Linux guest, I got this problem report from Monterery..

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VirtualBoxVM [983]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.30 (6.1.30)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [945]
Responsible:           VirtualBox [941]
User ID:               502

Date/Time:             2021-11-24 11:33:23.4080 -0500
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Anonymous UUID:        D29E8D31-4B9E-1252-579C-6F6F7174505F


Time Awake Since Boot: 39000 seconds

System Integrity Protection: disabled

Notes:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000002c40000000c
Exception Codes:       0x0000000000000001, 0x000002c40000000c
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [983]

VM Region Info: 0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      CoreServices                190e88000-190ec8000    [  256K] rw-/rwx SM=COW  
--->  GAP OF 0x5ffe6f138000 BYTES
      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-/rwx SM=PRV  

Error Formulating Crash Report:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   IOKit                         	    0x7ff81e78fae0 IOHIDDeviceCopyMatchingElements + 34
1   UICommon.dylib                	       0x10555efa8 0x10522c000 + 3354536
2   UICommon.dylib                	       0x10555ee4e DarwinHidDevicesApplyAndReleaseLedsState + 590
3   VirtualBoxVM.dylib            	       0x100581e92 0x100553000 + 192146
4   VirtualBoxVM.dylib            	       0x1005815ff 0x100553000 + 189951
5   VirtualBoxVM.dylib            	       0x100581575 0x100553000 + 189813
6   QtCoreVBox                    	       0x1018d943b QMetaObject::activate(QObject*, int, int, void**) + 2075
7   QtCoreVBox                    	       0x1018a5b76 QCoreApplication::exec() + 390
8   VirtualBoxVM.dylib            	       0x10055a42e TrustedMain + 1502
9   VirtualBoxVM                  	       0x10027ef01 0x10027b000 + 16129
10  dyld                          	       0x10bd144fe start + 462

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	    0x7ff81be58e4a __select + 10
1   VBoxXPCOM.dylib               	       0x1009198a0 0x10088f000 + 567456
2   VBoxXPCOM.dylib               	       0x10091b6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	       0x101623e75 0x101611000 + 77429
4   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10ab8eda1 0x10aa95000 + 1023393
4   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
5   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091ede7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161671b 0x101611000 + 22299
5   VBoxXPCOMIPCC.dylib           	       0x1016163ed 0x101611000 + 21485
6   VBoxXPCOMIPCC.dylib           	       0x10161b039 0x101611000 + 41017
7   VBoxXPCOM.dylib               	       0x1009022ed 0x10088f000 + 471789
8   VBoxXPCOM.dylib               	       0x1009014eb 0x10088f000 + 468203
9   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
11  QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
12  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
13  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 7:: nspr-3
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 8:: nspr-4
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 9:: EMT
0   libsystem_kernel.dylib        	    0x7ff81be53fda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff81be53fc7 ioctl + 150
2   VBoxRT.dylib                  	       0x100bfc4ad 0x100a47000 + 1791149
3   VBoxRT.dylib                  	       0x100bf46e6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	       0x102332681 0x102285000 + 710273
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	    0x7ff81be50aba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff81be50e2b mach_msg + 59
2   CoreFoundation                	    0x7ff81bf53d51 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff81bf5240f __CFRunLoopRun + 1329
4   CoreFoundation                	    0x7ff81bf51809 CFRunLoopRunSpecific + 567
5   AppKit                        	    0x7ff81ea11cec _NSEventThread + 132
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 11:: AMCP Logging Spool
0   libsystem_kernel.dylib        	    0x7ff81be50af6 semaphore_wait_trap + 10
1   caulk                         	    0x7ff824d4e1c0 caulk::mach::semaphore::wait_or_error() + 16
2   caulk                         	    0x7ff824d3508a caulk::concurrent::details::worker_thread::run() + 36
3   caulk                         	    0x7ff824d34d4e void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41
4   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
5   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 12:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 13:: VMPwrDwn
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bee9c6 0x100a47000 + 1735110
3   VBoxRT.dylib                  	       0x100b36f73 0x100a47000 + 982899
4   VBoxVMM.dylib                 	       0x10232d00e 0x102285000 + 688142
5   VBoxVMM.dylib                 	       0x10232e9be VMR3Destroy + 270
6   VBoxC.dylib                   	       0x10ab02581 0x10aa95000 + 447873
7   VBoxC.dylib                   	       0x10ab285f7 0x10aa95000 + 603639
8   VBoxC.dylib                   	       0x10aae8a9c 0x10aa95000 + 342684
9   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
10  VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
11  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
12  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 14:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 15:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0


No thread state (register information) available

Binary Images:
    0x7ff81e751000 -     0x7ff81e806fff com.apple.framework.IOKit (2.0.2) <7d46c110-4106-3280-9031-f7e035792f22> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
       0x10522c000 -        0x1072dcfff UICommon.dylib (*) <275d65cb-226c-39b5-a840-5143c6007a6b> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x100553000 -        0x100676fff VirtualBoxVM.dylib (*) <3a6f5a29-74ff-313c-9220-82612f2b6fc7> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1016be000 -        0x101be5fff org.qt-project.QtCoreVBox (5.6) <3a7a08e0-9422-393e-bd97-fd15e751434c> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10027b000 -        0x100282fff org.virtualbox.app.VirtualBoxVM (6.1.30) <43e613e0-b296-3de8-92e1-fbee61a51a5e> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10bd0f000 -        0x10bd7afff dyld (*) <1a6ae033-9438-33c0-8077-988fd885250a> /usr/lib/dyld
    0x7ff81be50000 -     0x7ff81be86fff libsystem_kernel.dylib (*) <12bd6f13-c452-35ee-9069-51befef29f1a> /usr/lib/system/libsystem_kernel.dylib
       0x10088f000 -        0x100940fff VBoxXPCOM.dylib (*) <31c4ddec-f9f5-363e-ad9f-b8881543e336> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x101611000 -        0x101628fff VBoxXPCOMIPCC.dylib (*) <4e46eacb-3d27-3668-8e43-a455d494d839> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x100a47000 -        0x100fb1fff VBoxRT.dylib (*) <05fa665b-b1c8-3f62-861e-1b3579be4a9a> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
    0x7ff81be87000 -     0x7ff81be92fff libsystem_pthread.dylib (*) <29a2750e-f31b-3630-8761-242a6bc3e99e> /usr/lib/system/libsystem_pthread.dylib
       0x10aa95000 -        0x10aea3fff VBoxC.dylib (*) <7a8a2b64-5299-3eda-9b9b-85eac8f2d836> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x102285000 -        0x10258cfff VBoxVMM.dylib (*) <b600b9be-060e-373f-8e33-09248dd2c4b7> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
    0x7ff81bed4000 -     0x7ff81c3d4fff com.apple.CoreFoundation (6.9) <afcc752e-074d-340f-890c-263efd2da77f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7ff81e865000 -     0x7ff81f6f1fff com.apple.AppKit (6.9) <dd0028a3-78e3-3a8a-a51b-ddd68123adef> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7ff824d33000 -     0x7ff824d55fff com.apple.audio.caulk (1.0) <c5042b28-9206-337f-bfb2-dc0b37dd8632> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
               0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)
Writable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               256K        2 
Activity Tracing                   256K        1 
CG backing stores                  640K        4 
CG image                            48K        3 
CG raster data                     140K        3 
ColorSync                          224K       25 
CoreAnimation                     3892K       12 
CoreGraphics                        12K        2 
CoreServices                       304K        2 
CoreUI image data                  332K        5 
Foundation                          16K        1 
Kernel Alloc Once                    8K        1 
MALLOC                           381.5M      105 
MALLOC guard page                   48K        9 
MALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.1M       16 
Stack                             16.1M       16 
VM_ALLOCATE                       8312K       17 
__DATA                            35.6M      344 
__DATA_CONST                      14.2M      192 
__DATA_DIRTY                       638K      110 
__FONT_DATA                          4K        1 
__LINKEDIT                       644.7M       30 
__OBJC_RO                         81.6M        1 
__OBJC_RW                         3120K        2 
__TEXT                           326.9M      354 
__UNICODE                          588K        1 
dyld private memory               1024K        1 
mapped file                       90.2M       24 
shared memory                      808K       19 
===========                     =======  ======= 
TOTAL                              3.4G     1316 
TOTAL, minus reserved VM space     1.6G     1316 



-----------
Full Report
-----------

{""app_name"":""VirtualBoxVM"",""timestamp"":""2021-11-24 11:33:27.00 -0500"",""app_version"":""6.1.30"",""slice_uuid"":""43e613e0-b296-3de8-92e1-fbee61a51a5e"",""build_version"":""6.1.30"",""platform"":1,""bundleID"":""org.virtualbox.app.VirtualBoxVM"",""share_with_app_devs"":1,""is_first_party"":0,""bug_type"":""309"",""os_version"":""macOS 12.0.1 (21A559)"",""incident_id"":""BC924093-ADDD-4947-94C1-823F46F11168"",""name"":""VirtualBoxVM""}
{
  ""uptime"" : 39000,
  ""procLaunch"" : ""2021-11-24 00:42:47.3044 -0500"",
  ""procRole"" : ""Background"",
  ""version"" : 2,
  ""userID"" : 502,
  ""deployVersion"" : 210,
  ""modelCode"" : ""MacPro6,1"",
  ""procStartAbsTime"" : 258600882589,
  ""coalitionID"" : 788,
  ""osVersion"" : {
    ""train"" : ""macOS 12.0.1"",
    ""build"" : ""21A559"",
    ""releaseType"" : ""User""
  },
  ""captureTime"" : ""2021-11-24 11:33:23.4080 -0500"",
  ""incident"" : ""BC924093-ADDD-4947-94C1-823F46F11168"",
  ""bug_type"" : ""309"",
  ""pid"" : 983,
  ""procExitAbsTime"" : 39296637478404,
  ""cpuType"" : ""X86-64"",
  ""procName"" : ""VirtualBoxVM"",
  ""procPath"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
  ""bundleInfo"" : {""CFBundleShortVersionString"":""6.1.30"",""CFBundleVersion"":""6.1.30"",""CFBundleIdentifier"":""org.virtualbox.app.VirtualBoxVM""},
  ""storeInfo"" : {""deviceIdentifierForVendor"":""D2CBA99F-71A3-5B29-BC09-3089D1644C8E"",""thirdParty"":true},
  ""parentProc"" : ""VBoxSVC"",
  ""parentPid"" : 945,
  ""coalitionName"" : ""org.virtualbox.app.VirtualBox"",
  ""crashReporterKey"" : ""D29E8D31-4B9E-1252-579C-6F6F7174505F"",
  ""responsiblePid"" : 941,
  ""responsibleProc"" : ""VirtualBox"",
  ""sip"" : ""disabled"",
  ""vmRegionInfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""isCorpse"" : 1,
  ""exception"" : {""codes"":""0x0000000000000001, 0x000002c40000000c"",""rawCodes"":[1,3040836845580],""type"":""EXC_BAD_ACCESS"",""signal"":""SIGSEGV"",""subtype"":""KERN_INVALID_ADDRESS at 0x000002c40000000c""},
  ""termination"" : {""flags"":0,""code"":11,""namespace"":""SIGNAL"",""indicator"":""Segmentation fault: 11"",""byProc"":""exc handler"",""byPid"":983},
  ""vmregioninfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""extMods"" : {""caller"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""system"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""targeted"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""warnings"":0},
  ""faultingThread"" : 0,
  ""threads"" : [{""triggered"":true,""id"":9449,""queue"":""com.apple.main-thread"",""frames"":[{""imageOffset"":256736,""symbol"":""IOHIDDeviceCopyMatchingElements"",""symbolLocation"":34,""imageIndex"":0},{""imageOffset"":3354536,""imageIndex"":1},{""imageOffset"":3354190,""symbol"":""DarwinHidDevicesApplyAndReleaseLedsState"",""symbolLocation"":590,""imageIndex"":1},{""imageOffset"":192146,""imageIndex"":2},{""imageOffset"":189951,""imageIndex"":2},{""imageOffset"":189813,""imageIndex"":2},{""imageOffset"":2208827,""symbol"":""QMetaObject::activate(QObject*, int, int, void**)"",""symbolLocation"":2075,""imageIndex"":3},{""imageOffset"":1997686,""symbol"":""QCoreApplication::exec()"",""symbolLocation"":390,""imageIndex"":3},{""imageOffset"":29742,""symbol"":""TrustedMain"",""symbolLocation"":1502,""imageIndex"":2},{""imageOffset"":16129,""imageIndex"":4},{""imageOffset"":21758,""symbol"":""start"",""symbolLocation"":462,""imageIndex"":5}]},{""id"":9456,""name"":""nspr-1"",""frames"":[{""imageOffset"":36426,""symbol"":""__select"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":567456,""imageIndex"":7},{""imageOffset"":575205,""symbol"":""PR_Poll"",""symbolLocation"":1061,""imageIndex"":7},{""imageOffset"":77429,""imageIndex"":8},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9457,""name"":""nspr-2"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9458,""name"":""VBoxSVCWatcher"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":1023393,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9459,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589287,""symbol"":""PR_WaitCondVar"",""symbolLocation"":231,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":22299,""imageIndex"":8},{""imageOffset"":21485,""imageIndex"":8},{""imageOffset"":41017,""imageIndex"":8},{""imageOffset"":471789,""imageIndex"":7},{""imageOffset"":468203,""imageIndex"":7},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9460,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9557,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9574,""name"":""nspr-3"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9576,""name"":""nspr-4"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9579,""name"":""EMT"",""frames"":[{""imageOffset"":16346,""symbol"":""__ioctl"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":16327,""symbol"":""ioctl"",""symbolLocation"":150,""imageIndex"":6},{""imageOffset"":1791149,""imageIndex"":9},{""imageOffset"":1758950,""symbol"":""SUPR3CallVMMR0Ex"",""symbolLocation"":438,""imageIndex"":9},{""imageOffset"":710273,""imageIndex"":12},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9582,""name"":""com.apple.NSEventThread"",""frames"":[{""imageOffset"":2746,""symbol"":""mach_msg_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":3627,""symbol"":""mach_msg"",""symbolLocation"":59,""imageIndex"":6},{""imageOffset"":523601,""symbol"":""__CFRunLoopServiceMachPort"",""symbolLocation"":319,""imageIndex"":13},{""imageOffset"":517135,""symbol"":""__CFRunLoopRun"",""symbolLocation"":1329,""imageIndex"":13},{""imageOffset"":514057,""symbol"":""CFRunLoopRunSpecific"",""symbolLocation"":567,""imageIndex"":13},{""imageOffset"":1756396,""symbol"":""_NSEventThread"",""symbolLocation"":132,""imageIndex"":14},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9603,""name"":""AMCP Logging Spool"",""frames"":[{""imageOffset"":2806,""symbol"":""semaphore_wait_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":111040,""symbol"":""caulk::mach::semaphore::wait_or_error()"",""symbolLocation"":16,""imageIndex"":15},{""imageOffset"":8330,""symbol"":""caulk::concurrent::details::worker_thread::run()"",""symbolLocation"":36,""imageIndex"":15},{""imageOffset"":7502,""symbol"":""void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)"",""symbolLocation"":41,""imageIndex"":15},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341041,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341261,""name"":""VMPwrDwn"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1735110,""imageIndex"":9},{""imageOffset"":982899,""imageIndex"":9},{""imageOffset"":688142,""imageIndex"":12},{""imageOffset"":694718,""symbol"":""VMR3Destroy"",""symbolLocation"":270,""imageIndex"":12},{""imageOffset"":447873,""imageIndex"":11},{""imageOffset"":603639,""imageIndex"":11},{""imageOffset"":342684,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341263,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341264,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]}],
  ""usedImages"" : [
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703639605248,
    ""CFBundleShortVersionString"" : ""2.0.2"",
    ""CFBundleIdentifier"" : ""com.apple.framework.IOKit"",
    ""size"" : 745472,
    ""uuid"" : ""7d46c110-4106-3280-9031-f7e035792f22"",
    ""path"" : ""\/System\/Library\/Frameworks\/IOKit.framework\/Versions\/A\/IOKit"",
    ""name"" : ""IOKit""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4381130752,
    ""size"" : 34279424,
    ""uuid"" : ""275d65cb-226c-39b5-a840-5143c6007a6b"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/UICommon.dylib"",
    ""name"" : ""UICommon.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4300550144,
    ""size"" : 1196032,
    ""uuid"" : ""3a6f5a29-74ff-313c-9220-82612f2b6fc7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VirtualBoxVM.dylib"",
    ""name"" : ""VirtualBoxVM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318814208,
    ""CFBundleShortVersionString"" : ""5.6"",
    ""CFBundleIdentifier"" : ""org.qt-project.QtCoreVBox"",
    ""size"" : 5406720,
    ""uuid"" : ""3a7a08e0-9422-393e-bd97-fd15e751434c"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Frameworks\/QtCoreVBox.framework\/Versions\/5\/QtCoreVBox"",
    ""name"" : ""QtCoreVBox"",
    ""CFBundleVersion"" : ""5.6.3""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4297568256,
    ""CFBundleShortVersionString"" : ""6.1.30"",
    ""CFBundleIdentifier"" : ""org.virtualbox.app.VirtualBoxVM"",
    ""size"" : 32768,
    ""uuid"" : ""43e613e0-b296-3de8-92e1-fbee61a51a5e"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
    ""name"" : ""VirtualBoxVM"",
    ""CFBundleVersion"" : ""6.1.30""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4493209600,
    ""size"" : 442368,
    ""uuid"" : ""1a6ae033-9438-33c0-8077-988fd885250a"",
    ""path"" : ""\/usr\/lib\/dyld"",
    ""name"" : ""dyld""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596609536,
    ""size"" : 225280,
    ""uuid"" : ""12bd6f13-c452-35ee-9069-51befef29f1a"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_kernel.dylib"",
    ""name"" : ""libsystem_kernel.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4303941632,
    ""size"" : 729088,
    ""uuid"" : ""31c4ddec-f9f5-363e-ad9f-b8881543e336"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxXPCOM.dylib"",
    ""name"" : ""VBoxXPCOM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318105600,
    ""size"" : 98304,
    ""uuid"" : ""4e46eacb-3d27-3668-8e43-a455d494d839"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxXPCOMIPCC.dylib"",
    ""name"" : ""VBoxXPCOMIPCC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4305743872,
    ""size"" : 5681152,
    ""uuid"" : ""05fa665b-b1c8-3f62-861e-1b3579be4a9a"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxRT.dylib"",
    ""name"" : ""VBoxRT.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596834816,
    ""size"" : 49152,
    ""uuid"" : ""29a2750e-f31b-3630-8761-242a6bc3e99e"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_pthread.dylib"",
    ""name"" : ""libsystem_pthread.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4473835520,
    ""size"" : 4255744,
    ""uuid"" : ""7a8a2b64-5299-3eda-9b9b-85eac8f2d836"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxC.dylib"",
    ""name"" : ""VBoxC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4331163648,
    ""size"" : 3178496,
    ""uuid"" : ""b600b9be-060e-373f-8e33-09248dd2c4b7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxVMM.dylib"",
    ""name"" : ""VBoxVMM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703597150208,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.CoreFoundation"",
    ""size"" : 5246976,
    ""uuid"" : ""afcc752e-074d-340f-890c-263efd2da77f"",
    ""path"" : ""\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation"",
    ""name"" : ""CoreFoundation"",
    ""CFBundleVersion"" : ""1855.105""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703640735744,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.AppKit"",
    ""size"" : 15257600,
    ""uuid"" : ""dd0028a3-78e3-3a8a-a51b-ddd68123adef"",
    ""path"" : ""\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit"",
    ""name"" : ""AppKit"",
    ""CFBundleVersion"" : ""2113""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703746437120,
    ""CFBundleShortVersionString"" : ""1.0"",
    ""CFBundleIdentifier"" : ""com.apple.audio.caulk"",
    ""size"" : 143360,
    ""uuid"" : ""c5042b28-9206-337f-bfb2-dc0b37dd8632"",
    ""path"" : ""\/System\/Library\/PrivateFrameworks\/caulk.framework\/Versions\/A\/caulk"",
    ""name"" : ""caulk""
  },
  {
    ""size"" : 0,
    ""source"" : ""A"",
    ""base"" : 0,
    ""uuid"" : ""00000000-0000-0000-0000-000000000000""
  }
],
  ""sharedCache"" : {
  ""base"" : 140703593594880,
  ""size"" : 15215640576,
  ""uuid"" : ""b5084610-afe4-3485-bade-628c4468b057""
},
  ""vmSummary"" : ""ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)\nWritable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nAccelerate framework               256K        2 \nActivity Tracing                   256K        1 \nCG backing stores                  640K        4 \nCG image                            48K        3 \nCG raster data                     140K        3 \nColorSync                          224K       25 \nCoreAnimation                     3892K       12 \nCoreGraphics                        12K        2 \nCoreServices                       304K        2 \nCoreUI image data                  332K        5 \nFoundation                          16K        1 \nKernel Alloc Once                    8K        1 \nMALLOC                           381.5M      105 \nMALLOC guard page                   48K        9 \nMALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)\nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.1M       16 \nStack                             16.1M       16 \nVM_ALLOCATE                       8312K       17 \n__DATA                            35.6M      344 \n__DATA_CONST                      14.2M      192 \n__DATA_DIRTY                       638K      110 \n__FONT_DATA                          4K        1 \n__LINKEDIT                       644.7M       30 \n__OBJC_RO                         81.6M        1 \n__OBJC_RW                         3120K        2 \n__TEXT                           326.9M      354 \n__UNICODE                          588K        1 \ndyld private memory               1024K        1 \nmapped file                       90.2M       24 \nshared memory                      808K       19 \n===========                     =======  ======= \nTOTAL                              3.4G     1316 \nTOTAL, minus reserved VM space     1.6G     1316 \n"",
  ""legacyInfo"" : {
  ""threadTriggered"" : {
    ""queue"" : ""com.apple.main-thread""
  }
},
  ""trialInfo"" : {
  ""rollouts"" : null,
  ""experiments"" : null
},
  ""reportNotes"" : [
  ""thread_get_state(PAGEIN) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(EXCEPTION) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(FLAVOR) returned 0x10000003: (ipc\/send) invalid destination port""
]
}

Model: MacPro6,1, BootROM 429.40.7.0.1, 6 processors, 6-Core Intel Xeon E5, 3.5 GHz, 32 GB, SMC 2.20f18
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Display: DELL E207WFP, 1680 x 1050 (Widescreen Super eXtended Graphics Array Plus), Main, MirrorOff, Online
Memory Module: DIMM1, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM2, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM3, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM4, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.2)
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: AMD FirePro D300, Display Controller, Slot-1
PCI Card: AMD FirePro D300, Display Controller, Slot-2
PCI Card: pci1b4b,9235, AHCI Controller, Thunderbolt@81,0,0
PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@236,0,0
Serial ATA Device: WDC  WDS100T2B0A-00SM50, 1 TB
Serial ATA Device: TEAM T253A3001T, 1.02 TB
Serial ATA Device: HGST HDN726060ALE614, 6 TB
Serial ATA Device: HGST HUH728060ALE600, 6 TB
USB Device: USB30Bus
USB Device: 4-Port USB 3.0 Hub
USB Device: 4-Port USB 3.0 Hub
USB Device: Mercury Pro
USB Device: USB3.0 Hub
USB Device: JMS56x Series
USB Device: Elite Pro U3FW
USB Device: Elements 25A3
USB Device: 4-Port USB 2.0 Hub
USB Device: 4-Port USB 2.0 Hub
USB Device: USB2.0 Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: MFC-J450DW
USB Device: hub_device
USB Device: hub_device
USB Device: Flash Card Reader
USB Device: USB Camera
USB Device: USB20Bus
USB Device: hub_device
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: RocketStor 5212, HighPoint Technologies, Inc., 1, 7.1
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: Drive Dock, Other World Computing, 1, 25.1
",mauricev
20689,Audio output switching no longer works reliably.,Windows,Windows,VirtualBox 6.1.28,2021-11-24T18:23:28Z,2021-11-24T18:23:28Z,"Audio output switching no longer works reliably.

Windows 10 host, Windows 10 guest.  Swapping audio output (like plugging in to a monitor with speakers), the audio dies.  Not sure if it can be resurrected with some combination of guest and/or host reboots.

It used to transfer seamlessly in 6.1.18.  This is a regression, probably introduced in 6.1.20: ""Audio: Multiple fixes and enhancements"".",Zapados
20690,opengl 3D-rendering malfunction,Linux,Windows,VirtualBox 6.1.30,2021-11-25T18:28:33Z,2021-11-25T18:28:33Z,"I use a Windows10Pro guest within virtualbox on a linux host machine (debian bullseye).
The problem arises running a CAD application within the guest and rendering a 3D-Model.
The model appears top down. It is not possible to rotate it to head up. Also, some textures of faces are not displayed (these structures are displayed like wireframe - front faces missing).
When I use a Mesa (Software) renderer client by the application, opengl rendering works correct, but much slower - as expected.
",woec007
20692,No signature was present in the subject,Windows,other,VirtualBox 6.1.30,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
20686,Turkish translate,other,other,VirtualBox 6.1.30,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
20698,crash vm on share clipboard,other,other,VirtualBox 6.1.30,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
20701,crash vm on share clipboard,other,other,VirtualBox 6.1.30,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
20582,Virtual Machine cannot be started with Linux host kernel 5.14,Linux,Windows,VirtualBox 6.1.26,2021-11-29T09:15:40Z,2021-11-29T09:15:40Z,"""Starting..."" dialog running forever.
{{{
# uname -s -r -v -m -p -i -o
Linux 5.14.0-1-amd64 #1 SMP Debian 5.14.6-3 (2021-09-28) x86_64 unknown unknown GNU/Linux
}}}

Relevant dmesg follows:

{{{
[ 4357.923819] SUPR0GipMap: fGetGipCpu=0x2b
[ 4364.025402] usb 5-2: reset high-speed USB device number 2 using xhci_hcd
[ 4364.754742] BUG: unable to handle page fault for address: ffffb205c8289dc0
[ 4364.754750] #PF: supervisor write access in kernel mode
[ 4364.754754] #PF: error_code(0x0003) - permissions violation
[ 4364.754756] PGD 800100000067 P4D 800100000067 PUD 80010019f067 PMD 80010645d067 PTE 80011b390161
[ 4364.754761] Oops: 0003 [#1] SMP NOPTI
[ 4364.754765] CPU: 11 PID: 18408 Comm: EMT Tainted: P           OE     5.14.0-1-amd64 #1  Debian 5.14.6-3
[ 4364.754769] Hardware name: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING/X470 AORUS ULTRA GAMING-CF, BIOS F41 07/22/2019
[ 4364.754772] RIP: 0010:0xffffb205c8289dc0
[ 4364.754775] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4364.754779] RSP: 0018:ffffb205c39b7e20 EFLAGS: 00010286
[ 4364.754781] RAX: ffffb205c8289dc0 RBX: ffffb205c8407010 RCX: ffffb205c8209000
[ 4364.754784] RDX: ffffb205c8289040 RSI: 0000000000000000 RDI: ffff8df1fb85cfd0
[ 4364.754785] RBP: ffffb205c39b7ea0 R08: 0000000000000001 R09: 0000000000000001
[ 4364.754787] R10: ffffffffc0eba560 R11: 0000000000000070 R12: 0000000000000024
[ 4364.754789] R13: ffffb205c8407010 R14: 0000000000000000 R15: ffff8df1fb85cfd0
[ 4364.754791] FS:  00007ff5c095f640(0000) GS:ffff8df7feac0000(0000) knlGS:0000000000000000
[ 4364.754793] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4364.754795] CR2: ffffb205c8289dc0 CR3: 000080026c12c000 CR4: 00000000003506e0
[ 4364.754798] Call Trace:
[ 4364.754803]  ? supdrvIOCtl+0x3462/0x38b0 [vboxdrv]
[ 4364.754829]  VBoxDrvLinuxIOCtl_6_1_26+0x13c/0x230 [vboxdrv]
[ 4364.754850]  __x64_sys_ioctl+0x83/0xb0
[ 4364.754855]  do_syscall_64+0x3b/0xc0
[ 4364.754861]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 4364.754865] RIP: 0033:0x7ff5e904d957
[ 4364.754868] Code: 3c 1c 48 f7 d8 4c 39 e0 77 b9 e8 24 ff ff ff 85 c0 78 be 4c 89 e0 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e1 94 0c 00 f7 d8 64 89 01 48
[ 4364.754871] RSP: 002b:00007ff5c095dbd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 4364.754874] RAX: ffffffffffffffda RBX: 00007ff5a41e1390 RCX: 00007ff5e904d957
[ 4364.754876] RDX: 00007ff5a41e1390 RSI: 0000000000005684 RDI: 0000000000000007
[ 4364.754877] RBP: 00007ff5c095dbe0 R08: 0000000000000000 R09: 0000000000000000
[ 4364.754879] R10: 00007ff5e8ead220 R11: 0000000000000246 R12: 00007ff5d1260b4f
[ 4364.754881] R13: 00007ff5c095e040 R14: 00007ff5c095dd40 R15: 0000000000000000
[ 4364.754883] Modules linked in: tun(E) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfkill(E) intel_rapl_msr(E) intel_rapl_common(E) nvidia_drm(POE) edac_mce_amd(E) uinput(E) nvidia_modeset(POE) kvm_amd(E) kvm(E) irqbypass(E) uvcvideo(E) videobuf2_vmalloc(E) snd_usb_audio(E) videobuf2_memops(E) snd_hda_codec_realtek(E) videobuf2_v4l2(E) ghash_clmulni_intel(E) nvidia(POE) snd_hda_codec_generic(E) joydev(E) videobuf2_common(E) snd_usbmidi_lib(E) ledtrig_audio(E) aesni_intel(E) snd_rawmidi(E) snd_hda_codec_hdmi(E) videodev(E) snd_seq_device(E) crypto_simd(E) hid_sony(E) snd_hda_intel(E) mc(E) cryptd(E) ff_memless(E) snd_intel_dspcfg(E) snd_intel_sdw_acpi(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) drm_kms_helper(E) snd_pcm(E) rapl(E) cec(E) snd_timer(E) rc_core(E) snd(E) wmi_bmof(E) soundcore(E) ccp(E) pcspkr(E) sp5100_tco(E) sg(E) watchdog(E) rng_core(E) k10temp(E) evdev(E) acpi_cpufreq(E) parport_pc(E) ppdev(E) lp(E) parport(E) drm(E) fuse(E) configfs(E) ip_tables(E) x_tables(E)
[ 4364.754936]  autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) sd_mod(E) hid_lg_g15(E) hid_generic(E) usbhid(E) hid(E) mxm_wmi(E) xhci_pci(E) nvme(E) ahci(E) xhci_hcd(E) libahci(E) nvme_core(E) igb(E) t10_pi(E) crc32_pclmul(E) crc_t10dif(E) dca(E) crc32c_intel(E) crct10dif_generic(E) crct10dif_pclmul(E) ptp(E) libata(E) usbcore(E) pps_core(E) gpio_amdpt(E) i2c_piix4(E) i2c_algo_bit(E) scsi_mod(E) usb_common(E) crct10dif_common(E) wmi(E) gpio_generic(E) button(E)
[ 4364.754968] CR2: ffffb205c8289dc0
[ 4364.754970] ---[ end trace e8bbd62475d00fd4 ]---
[ 4364.754972] RIP: 0010:0xffffb205c8289dc0
[ 4364.754974] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4364.754977] RSP: 0018:ffffb205c39b7e20 EFLAGS: 00010286
[ 4364.754979] RAX: ffffb205c8289dc0 RBX: ffffb205c8407010 RCX: ffffb205c8209000
[ 4364.754981] RDX: ffffb205c8289040 RSI: 0000000000000000 RDI: ffff8df1fb85cfd0
[ 4364.754982] RBP: ffffb205c39b7ea0 R08: 0000000000000001 R09: 0000000000000001
[ 4364.754984] R10: ffffffffc0eba560 R11: 0000000000000070 R12: 0000000000000024
[ 4364.754985] R13: ffffb205c8407010 R14: 0000000000000000 R15: ffff8df1fb85cfd0
[ 4364.754987] FS:  00007ff5c095f640(0000) GS:ffff8df7feac0000(0000) knlGS:0000000000000000
[ 4364.754989] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4364.754991] CR2: ffffb205c8289dc0 CR3: 000080026c12c000 CR4: 00000000003506e0
}}}",deltree
20702,"Execution of "".exe"" fails in shared folders, with Windows 10 or 11",Windows,Windows,VirtualBox 6.1.30,2021-12-01T14:42:25Z,2021-12-01T14:42:25Z,"Host Windows 10. Guest Windows 10 or 11.
(Windows XP x32 and Windows 7 x64, work fine)

When an "".exe"" is run inside a shared folder, it gives the error ""The specified path does not exist"" depending on the number of characters in the path + the file name, and the text entered in ""Folder name"" (sharename).

Examples with mountpoint = ""X:"":

sharename = ""1"":
  OK    X:\1234567.exe

  NOK  X:\12345678.exe
sharename = ""12"":
  OK    X:\12345678.exe

  NOK  X:\123456789.exe
sharename = ""123"":
  OK    X:\123456789.exe

  NOK  X:\1234567890.exe
...
sharename = ""12345678"":
  OK    X:\12345678901234.exe

  NOK  X:\123456789012345.exe

Interestingly, the more characters sharename has, the more characters the "".exe"" file name allows.",FelixG
19365,Graphic anomalies in Windows 10 2004,Windows,Windows,VirtualBox 6.1.4,2021-12-01T14:43:32Z,2021-12-01T14:43:32Z,"I have installed Windows 10 2004 64-Bit as guest under Windows 10 64-Bit 1909 as host system. Graphic adapter is VBOXSVGA with 3D acceleration. Actual guest additions are running.
The Windows start menu and the task bar are completely tranparent and not grey transparent, so the text cannot be read. Furthermore the settings dialog seems to freeze, after minimizing and maximizing the windows changes are visible.
When I disable transparency effects in the settings under personalizing, colors, everything works fine.
I observed this problem first time in Windows 10 2004 as guest, in Windows 10 1909 the graphic output was OK.",awhb
20693,VERR_VERSION_MISMATCH in VBoxExtPackRegister on 6.1.30,Mac OS X,other,VirtualBox 6.1.30,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
20703,OVA import from Windows Explorer (file manager) does not enable Import button,Windows,all,VirtualBox 6.1.30,2021-12-01T18:16:27Z,2021-12-01T18:16:27Z,"Cheers, got an UI bug in Windows edition with 6.1.30, I think it behaved differently with earlier releases: if I take an OVA file from Explorer and double-click it, VB UI opens and shows info from that OVA, but the Import button stays gray.

Now I have to go to file selector on the left and pick the same OVA and then I can Import it. This kinda defeats the purpose of double-clicking ;)

IIRC with earlier 6.1.x versions the import window layout looked different, but import via integration with Explorer ""just worked"".

",Jim Klimov
20696,Port Change Detect (PCD) bit not set on port change interrupt (xHCI),Mac OS X,all,VirtualBox 6.1.30,2021-12-01T20:01:54Z,2021-12-01T20:01:54Z,"The XHCI emulation fails to set the Port Change Detect (PCD) bit (bit 4) in the USB 
Status Register on a port change interrupt as described in the ""eXtensible Host Controller 
Interface for Universal Serial Bus (xHCI) Requirements Specification May 2019 Revision 
1.2"" section 5.4.2.

When real hardware generates a port change interrupt the Port Change Detect (PCD) bit 
is always set. In the VirtualBox VM, when a port change interrupt occurs, the USB Status 
Register only contains the Event Interrupt (EINT) bit set, and not the Port Change Detect 
(PCD) bit. This does not match the way real hardware works.

This (obviously) affects all guest OSes, and is not limited to specific ones.

I have not tested this on other host platforms.",Lewis Rosenthal
20712,VM Cannot Start,other,Windows,VirtualBox 6.1.30,2021-12-02T16:15:00Z,2021-12-02T16:15:00Z,"{{{
virtualbox-6.1:
  Installed: 6.1.30-148432~Debian~buster
  Candidate: 6.1.30-148432~Debian~buster
  Version table:
 *** 6.1.30-148432~Debian~buster 500
        500 http://download.virtualbox.org/virtualbox/debian buster/contrib amd64 Packages
        100 /var/lib/dpkg/status

Linux office-markm 5.10.0-0.bpo.8-rt-amd64 #1 SMP PREEMPT_RT Debian 5.10.46-4~bpo10+1 (2021-08-07) x86_64 GNU/Linux


00:00:00.927460 VirtualBox VM 6.1.30 r148432 linux.amd64 (Nov 22 2021 15:33:42) release log
00:00:00.927462 Log opened 2021-12-02T16:04:38.932286000Z
00:00:00.927463 Build Type: release
00:00:00.927465 OS Product: Linux
00:00:00.927466 OS Release: 5.10.0-0.bpo.8-rt-amd64
00:00:00.927467 OS Version: #1 SMP PREEMPT_RT Debian 5.10.46-4~bpo10+1 (2021-08-07)
00:00:00.927487 DMI Product Name: OptiPlex 9020
00:00:00.927494 DMI Product Version: 00
00:00:00.927503 Firmware type: BIOS
00:00:00.927536 Host RAM: 32054MB (31.3GB) total, 10660MB (10.4GB) available
00:00:00.927539 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:00.927539 Process ID: 20302
00:00:00.927540 Package type: LINUX_64BITS_DEBIAN_10_0
00:00:00.943981 Installed Extension Packs:
00:00:00.943981   Oracle VM VirtualBox Extension Pack (Version: 6.1.30 r148432; VRDE Module: VBoxVRDP)
00:00:00.948269 Console: Machine state changed to 'Starting'
00:00:00.948404 Qt version: 5.11.3
00:00:00.948412 X11 Window Manager code: 0
00:00:01.009079 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.010328 X Server details: vendor: The X.Org Foundation, release: 12004000, protocol version: 11.0, display string: :0
00:00:01.010350 Using XKB for keycode to scan code conversion
00:00:01.049341 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 2 work area is actually resized to: 0x20 x 2558x1398
00:00:01.050343 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 0x20 x 2558x1398
00:00:01.051380 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x20 x 2558x1398
00:00:01.115832 GUI: Machine-window #0 activated
00:00:01.115895 GUI: Machine-view #0 focused, reason=3
00:00:03.056026 GUI: Machine-window #0 deactivated
00:00:03.056026 GUI: Releasing mouse on focus out
00:00:03.056026 GUI: Machine-view #0 unfocused, reason=3
00:00:03.123844 GUI: Machine-window #0 activated
00:00:03.123890 GUI: Machine-view #0 focused, reason=3
00:00:03.659742 GUI: Machine-window #0 deactivated
00:00:03.659774 GUI: Releasing mouse on focus out
00:00:03.660287 GUI: Machine-view #0 unfocused, reason=3
00:00:14.430220 GUI: Machine-window #0 activated
00:00:14.430254 GUI: Machine-view #0 focused, reason=3
00:00:16.189701 GUI: Machine-window #0 deactivated
00:00:16.189731 GUI: Releasing mouse on focus out
00:00:16.190252 GUI: Machine-view #0 unfocused, reason=3

<VirtualBox xmlns=""http://www.virtualbox.org/"" version=""1.15-linux"">
  <Machine uuid=""{1d0f8da1-4e95-471b-b001-632dfe4697cd}"" name=""Windows 10"" OSType=""Windows10_64"" snapshotFolder=""Snapshots"" lastStateChange=""2021-12-02T16:03:48Z"" aborted=""true"">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{8a59a0b2-ab28-4cb8-b4a3-90b34179e741}"" location=""/home/vbox/Win10-64-disk1.vdi"" format=""VDI"" type=""Normal""/>
      </HardDisks>
    </MediaRegistry>
    <Hardware>
      <CPU>
        <PAE enabled=""true""/>
        <LongMode enabled=""true""/>
        <HardwareVirtExLargePages enabled=""false""/>
      </CPU>
      <Memory RAMSize=""6105""/>
      <HID Pointing=""USBTablet""/>
      <Paravirt provider=""Default""/>
      <Display controller=""VBoxSVGA"" VRAMSize=""50""/>
      <VideoCapture file=""."" fps=""25""/>
      <RemoteDisplay enabled=""false""/>
      <BIOS>
        <IOAPIC enabled=""true""/>
        <SmbiosUuidLittleEndian enabled=""true""/>
      </BIOS>
      <USB>
        <Controllers>
          <Controller name=""XHCI"" type=""XHCI""/>
        </Controllers>
      </USB>
      <Network>
        <Adapter slot=""0"" enabled=""true"" MACAddress=""0800274DED3F"" cable=""true"" type=""82540EM"">
          <NAT/>
        </Adapter>
      </Network>
      <AudioAdapter controller=""HDA"" driver=""Pulse"" enabled=""true"" enabledIn=""false""/>
      <Clipboard/>
    </Hardware>
    <StorageControllers>
      <StorageController name=""SATA"" type=""AHCI"" PortCount=""2"" useHostIOCache=""false"" Bootable=""true"" IDE0MasterEmulationPort=""0"" IDE0SlaveEmulationPort=""1"" IDE1MasterEmulationPort=""2"" IDE1SlaveEmulationPort=""3"">
        <AttachedDevice type=""HardDisk"" hotpluggable=""false"" port=""0"" device=""0"">
          <Image uuid=""{8a59a0b2-ab28-4cb8-b4a3-90b34179e741}""/>
        </AttachedDevice>
        <AttachedDevice passthrough=""false"" type=""DVD"" hotpluggable=""false"" port=""1"" device=""0""/>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>



[Thu Dec  2 11:02:12 2021] BUG: kernel NULL pointer dereference, address: 0000000000000018
[Thu Dec  2 11:02:12 2021] #PF: supervisor write access in kernel mode
[Thu Dec  2 11:02:12 2021] #PF: error_code(0x0002) - not-present page
[Thu Dec  2 11:02:12 2021] PGD 0 P4D 0
[Thu Dec  2 11:02:12 2021] Oops: 0002 [#1] PREEMPT_RT SMP PTI
[Thu Dec  2 11:02:12 2021] CPU: 7 PID: 11334 Comm: EMT Tainted: G        W  OE     5.10.0-0.bpo.8-rt-amd64 #1 Debian 5.10.46-4~bpo10+1
[Thu Dec  2 11:02:12 2021] Hardware name: Dell Inc. OptiPlex 9020/0PC5F7, BIOS A25 05/30/2019
[Thu Dec  2 11:02:12 2021] RIP: 0010:rt_spin_lock+0x10/0x30
[Thu Dec  2 11:02:12 2021] Code: 01 00 00 00 f0 0f b1 13 75 02 5b c3 89 c6 48 89 df e8 e4 9a 83 ff 66 90 5b c3 0f 1f 44 00 00 65 48 8b 14 25 40 7c 01 00 31 c0 <f0> 48 0f b1 57 18 48 85 c0 75 0a e8 e0 a8 85 ff e9 9b 7b 80 ff e8
[Thu Dec  2 11:02:12 2021] RSP: 0018:ffffb1c9cdd67d30 EFLAGS: 00010246
[Thu Dec  2 11:02:12 2021] RAX: 0000000000000000 RBX: ffff90b016b63548 RCX: 0000000000000000
[Thu Dec  2 11:02:12 2021] RDX: ffff90af46f80000 RSI: 000fffffffe00000 RDI: 0000000000000000
[Thu Dec  2 11:02:12 2021] RBP: ffffb1c9d3ef6000 R08: ffffb1c9cdd67dd0 R09: 0000000000000001
[Thu Dec  2 11:02:12 2021] R10: 0000000000000001 R11: 0000000000000001 R12: ffff90af4019f4f8
[Thu Dec  2 11:02:12 2021] R13: ffffb1c9d3ef6000 R14: ffffb1c9d3ea9000 R15: ffff90af44a293d0
[Thu Dec  2 11:02:12 2021] FS:  00007f9bc228a700(0000) GS:ffff90b63ddc0000(0000) knlGS:0000000000000000
[Thu Dec  2 11:02:12 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Thu Dec  2 11:02:12 2021] CR2: 0000000000000018 CR3: 0000000219252006 CR4: 00000000001706e0
[Thu Dec  2 11:02:12 2021] Call Trace:
[Thu Dec  2 11:02:12 2021]  __apply_to_page_range+0x2a7/0x680
[Thu Dec  2 11:02:12 2021]  ? rtR0TermNative+0x40/0x40 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  rtR0MemObjNativeProtect+0x74/0xb0 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  VBoxHost_RTR0MemObjProtect+0xad/0xc0 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  supdrvIOCtl+0x335b/0x3810 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  ? _copy_from_user+0x26/0x50
[Thu Dec  2 11:02:12 2021]  VBoxDrvLinuxIOCtl_6_1_30+0x156/0x230 [vboxdrv]
[Thu Dec  2 11:02:12 2021]  __x64_sys_ioctl+0x84/0xc0
[Thu Dec  2 11:02:12 2021]  do_syscall_64+0x33/0x80
[Thu Dec  2 11:02:12 2021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Thu Dec  2 11:02:12 2021] RIP: 0033:0x7f9c0cd99427
[Thu Dec  2 11:02:12 2021] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48
[Thu Dec  2 11:02:12 2021] RSP: 002b:00007f9bc2288c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[Thu Dec  2 11:02:12 2021] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9c0cd99427
[Thu Dec  2 11:02:12 2021] RDX: 00007f9bc1db2010 RSI: 0000000000005684 RDI: 0000000000000008
[Thu Dec  2 11:02:12 2021] RBP: 00007f9bc2288c80 R08: 0000000000000000 R09: 0000000000000000
[Thu Dec  2 11:02:12 2021] R10: 0000000000000010 R11: 0000000000000246 R12: 00007f9bc2288de0
[Thu Dec  2 11:02:12 2021] R13: 00007f9bc22890e0 R14: 00007f9bc1db2010 R15: 0000000000000004
[Thu Dec  2 11:02:12 2021] Modules linked in: cfg80211 vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) fuse ufs qnx4 hfsplus hfs cdrom minix vfat msdos fat jfs xfs ext4 mbcache jbd2 dm_mod c ufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_conservative bnep bluetooth jitterentropy_rng drbg ansi_cprng ecdh_generic rfkill ecc crc16 binfmt_misc uinput nfsd auth_rpcg s nfs_acl nfs lockd grace nfs_ssc fscache sunrpc radeon loop parport_pc ppdev lp parport intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uvcvi eo snd_hda_codec_realtek videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_v4l2 snd_hda_codec_generic videobuf2_common kvm ledtrig_audio snd_hda_codec_hdmi snd_usbmidi_lib vid odev irqbypass snd_hda_intel crc32_pclmul snd_rawmidi snd_intel_dspcfg snd_seq_device soundwire_intel amdgpu ghash_clmulni_intel joydev mc soundwire_generic_allocation snd_soc_core aes i_intel snd_compress soundwire_cadence libaes crypto_simd cryptd dell_wmi evdev mei_wdt
[Thu Dec  2 11:02:12 2021]  mei_hdcp glue_helper snd_hda_codec rapl gpu_sched snd_hda_core intel_cstate ttm snd_hwdep dell_smbios soundwire_bus sg dcdbas drm_kms_helper snd_pcm_oss spa se_keymap dell_wmi_descriptor wmi_bmof intel_uncore cec snd_mixer_oss at24 iTCO_wdt intel_pmc_bxt snd_pcm iTCO_vendor_support drm snd_timer watchdog mei_me i2c_algo_bit snd pcspkr soun core mei button btrfs blake2b_generic xor hid_microsoft ff_memless hid_generic usbhid hid raid6_pq libcrc32c crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic xhci_pci xhci_hcd ehci_pci ahci ehci_hcd libahci libata crct10dif_pclmul e1000e crct10dif_common i2c_i801 usbcore ptp scsi_mod crc32c_intel i2c_smbus lpc_ich pps_core usb_common wmi video
[Thu Dec  2 11:02:12 2021] CR2: 0000000000000018
[Thu Dec  2 11:02:12 2021] ---[ end trace 0000000000000003 ]---
[Thu Dec  2 11:02:12 2021] RIP: 0010:rt_spin_lock+0x10/0x30
[Thu Dec  2 11:02:12 2021] Code: 01 00 00 00 f0 0f b1 13 75 02 5b c3 89 c6 48 89 df e8 e4 9a 83 ff 66 90 5b c3 0f 1f 44 00 00 65 48 8b 14 25 40 7c 01 00 31 c0 <f0> 48 0f b1 57 18 48 85 c0 75 0a e8 e0 a8 85 ff e9 9b 7b 80 ff e8
[Thu Dec  2 11:02:12 2021] RSP: 0018:ffffb1c9cdd67d30 EFLAGS: 00010246
[Thu Dec  2 11:02:12 2021] RAX: 0000000000000000 RBX: ffff90b016b63548 RCX: 0000000000000000
[Thu Dec  2 11:02:12 2021] RDX: ffff90af46f80000 RSI: 000fffffffe00000 RDI: 0000000000000000
[Thu Dec  2 11:02:12 2021] RBP: ffffb1c9d3ef6000 R08: ffffb1c9cdd67dd0 R09: 0000000000000001
[Thu Dec  2 11:02:12 2021] R10: 0000000000000001 R11: 0000000000000001 R12: ffff90af4019f4f8
[Thu Dec  2 11:02:12 2021] R13: ffffb1c9d3ef6000 R14: ffffb1c9d3ea9000 R15: ffff90af44a293d0
[Thu Dec  2 11:02:12 2021] FS:  00007f9bc228a700(0000) GS:ffff90b63ddc0000(0000) knlGS:0000000000000000
[Thu Dec  2 11:02:12 2021] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Thu Dec  2 11:02:12 2021] CR2: 000000de09e0d000 CR3: 0000000219252004 CR4: 00000000001706e0

VirtualBox Guest Freezes while showing 'Starting'
}}}",iMarkM
20713,Serial Port Hangs after xxxx Time,Windows,Windows,VirtualBox 6.1.30,2021-12-02T19:18:50Z,2021-12-02T19:18:50Z,"An old VB6 application runs under Win XP which communicates with a controller via COM port 2.
The application always stops working after a certain period of time.
There was simply no more data sent.
The application was also unable to close the Com Port.
We tried 6.1.30 and 6.1.28 without success.
Now it has been running for several days thanks to version 5.2.44

It is certainly not a problem for the VB6 application, the error could also be reproduced with the HTERM program",mbi
20355,Possible race condition bug in UIMachineView::focusOutEvent / focusInEvent blocks mouse click on host/guest (Qt GUI),Linux,all,VirtualBox 6.1.22,2021-12-03T17:33:29Z,2021-12-03T17:33:29Z,"For more than two years now (so probably since VB version 6.0 or so) from time to time I am affected by a bug which stops mouse click interactions on the host and guest as well.
I can still move the mouse pointer but clicks are not recognized anymore. The only solution then is to shut down *all* running guest instances. Then the mouse clicks starts working again. There will be no entry in the logs, when the bug occurs.


=== How to reproduce ===


It happend very randomly to me but after a while with a screen record I figured out the following steps to reliable reproduce the bug on XFCE:

1) Click on the taskbar to restore VM window from minimized state[[BR]]
2) Press down the mouse button on the taskbar and keep it pressed[[BR]]
3) Release the mouse button and immediately press it again[[BR]]
4) Now no further clicks are registered until VM is shut down[[BR]]


(I agree that this looks like a very special and rare circumstance - however I think that this bug is a race condition and as I often switch between different windows with the taskbar I'm hit by it very often.)

Here is a screencast of the bug as GIF: https://s3.gifyu.com/images/vbox-bug.gif

=== Possible cause === 

From the steps I assume that the bug is kind of a race condition on the minimize respectively focus out / focus in event of the window. So I tried to build VirtualBox from source and try to trace the bug. And indeed I figured out, that the bug does not occure if I comment out the following 3 lines in the file {{{src/VBox/Frontends/VirtualBox/src/runtime/UIMachineView.cpp}}}

{{{
void UIMachineView::focusOutEvent(QFocusEvent *pEvent)
{
    /* If native event filter exists: */
    if (m_pNativeEventFilter)
    {
        /* Uninstall/destroy existing native event filter: */
            
        //qApp->removeNativeEventFilter(m_pNativeEventFilter);
        //delete m_pNativeEventFilter;
        //m_pNativeEventFilter = 0;
    }

    /* Call to base-class: */
    QAbstractScrollArea::focusOutEvent(pEvent);
}
}}}

I tried to dig deeper but I'm kind of stuck. Because I don't know what this native event filter is used for and why it is destroyed on focus out event.",Cryptkeeper
20715,"VirtualBox 6.1.30: ""vboxmanage natnetwork"" lacks of options to set IPv6 prefix and enable/disable router advertisements",other,other,VirtualBox 6.1.30,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
18668,Problem with sharing serial port after upgrade from 5.2.28 to 6.0.X,Windows,other,VirtualBox 6.0.8,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
20716,Impossible to use VirtualBox Guest Addition on Linux Preempt RT Kernel,Windows,Linux,VirtualBox 6.1.30,2021-12-07T11:30:59Z,2021-12-07T11:30:59Z,"I'm using Xubuntu 18.04 LTS as VM Guest (VirtualBox 6.1.28, I've tried with 6.1.30 also, Windows 10 Host).

If I'm using standard Linux kernels (4.x or 5.x), I'm able to install VirtualBox Guest Addition using the sudo ./autorun.sh command from the ISO mounted folder. No issue, working perfectly.

But If I'm using Linux Preempt RT Kernel, impossible to install VirtualBox Guest Addition. I've tried with Kernel 4.16.12-RT5, 5.14-RT19, 5.15.2-RT9. As a result, no shared folder, no mouse...
I've correctly compiled and installed linux-headers and linux-image corresponding to each Preempt RT kernel which are working correctly in standard PC.
The linux distribution is up to date using the sudo apt-get update, sudo apt-get upgrade, sudo apt-get dist-upgrade commands.
I've tried also to install virtualbox-dkms, dkms and virtualbox-guest-utils without any better result

It seems that the Virtualbox Guest Addition is not able to use to dedicated Preempt RT headers, even if they are set in linux kernel installation.

Please see the attached log for explanation.",oartigues
20210,BUG: unable to handle page fault for address: 00007efdf3ddc000,Linux,all,VirtualBox 6.1.18,2021-12-07T20:23:15Z,2021-12-07T20:23:15Z,"Virtualbox panic and freeze VM.
Ubuntu 20.04
5.11.0 mainline kernel",freetestuser
20499,mouse and keyboard stop working after a few seconds,Linux,Windows,VirtualBox 6.1.24,2021-12-08T17:08:17Z,2021-12-08T17:08:17Z,"Host: Debian 10, 64 bit, custom 5.10.x kernel
Guests: Win 7 Pro 32 bit, Win 10 Pro 64 bit, possibly other versions too
Affected VirtualBox versions: 6.1.24 and 6.1.26

After powering on a windows VM the VM stops reacting to mouse clicks or keyboard input. With Guest Additions installed the mouse pointer still moves. The VirtualBox app window won't refresh. I have to destroy the VM window to resume normal operation. When I start the Windows VM in safe mode mouse and keyboard work fine. Another observation is that the Remote Display is affected too (RDP client connects, changes size to VM's resolution, but black window) and works only when VM is started in safe mode. A downgrade of VirtualBox 6.1.22 resolves all issues.",madires
20718,Oracle Linux 8.2 Guest Mouse Pointer Integration Ubuntu 20.10 Host,Linux,Linux,VirtualBox 6.1.30,2021-12-09T15:28:43Z,2021-12-09T15:28:43Z,The mouse does not work right inside Oracle Linux 8.2 guest in VirtualBox 6.1 latest on Ubuntu 20.10 host. The mouse exits before reaching margin of VM console which makes installer GUI buttons inside Oracle Linux 8.2 installer unclickable.,orabuntu
16338,USB Root Hub Shows Yellow Exclamation Mark in Device Manager,Windows,Windows,VirtualBox 5.1.12,2021-12-09T16:58:17Z,2021-12-09T16:58:17Z,"Environment:
    ASMedia USB 3.0 extended host controller with the '''vendor driver'''.[[BR]]Operating system is Windows.

Steps:
    1. Open VM VirtualBox and create virtual machine (Type is Microsoft Windows).
    2. Open Device Manager and disable ASMedia USB Host Controller.
    3. Enable ASMedia USB Host Controller.
    4. USB Root Hub shows yellow exclamation mark.
    5. Device Manager displays the following message in the USB Root Hub Properties dialog box, on the General tab, in the Device Status text box:[[BR]]Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)[[BR]]The driver could not be loaded because a previous version of the driver is still in memory.",Gary_Chen
20691,Can't install virtualbox to other hard drive with msi parameter,other,other,VirtualBox 6.1.30,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
20720,Restart with snapshot,all,all,VirtualBox 6.1.28,2021-12-10T22:13:28Z,2021-12-10T22:13:28Z,"Hi,

A nice feature should whem closing a VM a dialog popup ups wich the three options:
  - Save the machine state
  - Send the shutdown signal
  - Power Off the machine
       + Restore current snapshot xyz
A fourth option should be nice to have.
  - Restart the machine with the current snapshot xyz. 

The machine should then be powered off, snapshot restored and restarted.

Regards,
Luc",viglu
20722,QOpenGLShader::link: error: fragment shader uses too many input components (52 > 40),all,Linux,VirtualBox 6.1.30,2021-12-11T16:09:58Z,2021-12-11T16:09:58Z,"Look at my ticket answer in kde:
https://bugs.kde.org/show_bug.cgi?id=445485

They indicates that you don't respect OpenGL spec.
",Phenom
20723,"Guest can't pick-up/use Host audio device (like BT or USB headset) after the device was physically reconnected/re-plugged (LOGS, STEPS)",Windows,Windows,VirtualBox 6.1.30,2021-12-13T01:16:59Z,2021-12-13T01:16:59Z,"Pls advise on temporary workaround (if any), as it blocks from using some of audio devices with VirtualBox (greate solution, btw, thank you so much!)

Steps:
1 Choose some pluggable audio device on Host. It can be any - USB or Bluetooth/BT headset/headphones, behavior is the same
2 Play audio in Guest
3 Disconnect/unplug audio device physically from Host
4 Audio playback falls back properly to the newly selected Host audio device (like speakers of a laptop)
5 Plug-in/reconnect disconnected USB or BT audio device, ensure it's selected as default in Host and audio plays just fine from Host
6 Try to play audio from Guest
RESULT: silence, nothing audible
I've expected audio to play normally, but it can be done only if I restart Guest

What's interesting is that if after step 6 I switch Host's audio device to 
the fallback device (like laptop's speakers), I start to hear Guest's audio. So the audio itself is not broken in Guest.

What I've tried to do to get it back:
* Disable/enable Audio Out/In in VB's toolbar
* Mute/unmute, ensure that all is unmuted after reconnections
* Stop/Start audiosrv and AudioEndpointBuilder on both Host and Guest
    The only uncertain thing here is that after some sequence of Stop/Starts I think audio started to go out to proper device, but then I couldn't reproduce/restore exact sequence of starts/stops so I'm no longer shure it wasn't a misinterpretation.

Pls note that if to change audio device back and forth without disconnecting/unplugging it, all works fine as expected.
Just in case, speaking of BT device - it's connected to the Host's bluetooth not to the Guest bypassing Host (if to pass-through BT device ""Intel Corp. [0002]"" to Guest)

Please help to solve it and if possible, suggest temporary workaround for the issue (through CLI), so I can restore audio without a need to restart Guest.

I've attached two set of verbose logs, ""Audio issue - NOT OK unplugging"" represents the issue. ""Audio issue - OK changing without unplugging"" is for the simple change without unplugging (just in case).

Logs contains AUDCLNT_E_DEVICE_INVALIDATED and VERR_AUDIO_STREAM_NOT_READY
{{{
00:02:55.763182 WasAPI: GetCurrentPadding failed on '[WasAPI] Front:0': AUDCLNT_E_DEVICE_INVALIDATED
00:02:55.763232 WasAPI: GetCurrentPadding([WasAPI] Front:0) failed during playback: AUDCLNT_E_DEVICE_INVALIDATED (@0x0)
00:02:55.763265 Audio: @0x6fa0: Stream '[WasAPI] Front:0' pre-buffering commit problem: wrote 0x0 out of 0x6fa0 + 0x0 - rc=VERR_AUDIO_STREAM_NOT_READY *pcbWritten=0x20 PREBUF_COMMITTING -> PREBUF_COMMITTING
}}}

VB version is 6.1.30 r148432 (Qt5.6.2) but I've seen it on previous versions as well.

It looks like others experience similar issues, but they were primarily referring to Bluetooth devices, but the issue seems to be more generic and affects all detachable audio devices.
Just in case, other tickets are #20630, #20431

I've seen references to function `drvHostAudioWasHA_StreamPlay()`:
{{{
else
{
    LogRelMax(64, (""WasAPI: GetCurrentPadding(%s) failed during playback: %Rhrc (@%#RX64)\n"",
    pStreamWas->Cfg.szName, hrc, pStreamWas->offInternal));
    /** @todo reinit on AUDCLNT_E_DEVICEINVALIDATED? */
    rc = VERR_AUDIO_STREAM_NOT_READY;
    break;
}
}}}",PavloUnn
20630,Sound disappears after second change from Speaker to Bluetooth Headphones on the host,Windows,Windows,VirtualBox 6.1.28,2021-12-13T01:22:32Z,2021-12-13T01:22:32Z,"This is a duplicate of the ticket #20431. The description and the analysis of the issue is already there. The error is here since 4 versions (was caused by the another refactor of sound backend back in the March 2021). It still here in the version 6.1.28 147628 and 6.1.29 147791, so I opened this duplicate.

Quick description here: after the host output device changes from Speaker to Bluetooth, then back to Speaker and then once again to BT, the sound output from VBox is lost. Other application from the host still can use the BT as output, but VBox can only use the Speaker after that. The only remedy is to restart or to save and restore the VM, but this only gives one single more short for the BT. After that the whole situation repeats itself.
",boxer01
20719,VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm fail to build on Kylin Linux Advanced Server V10,Linux,OSX Server,VirtualBox 6.1.30,2021-12-13T10:08:50Z,2021-12-13T10:08:50Z,"Installing VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm work fine, but sudo /sbin/vboxconfig fails with kernel-4.19.90-25.8.v2101.ky10.x86_64",Nuyoah
20697,Guest Additions 6.1.28 and 6.1.30 cannot install Windows Server 2012 R2,Windows,Windows,VirtualBox 6.1.30,2021-12-13T21:26:41Z,2021-12-13T21:26:41Z,"I've been running Windows Server 2012 R2, along with Windows 7, Windows Server 2016 and Windows Server 2019 guest virtual machines, on my  VirtualBox host, for several months now. 

Up until Guest Additions 6.1.26 (on VirtualBox 6.1.26) there was no serious problems installing those older Guest Additions from the applicable mounted *.ISO files, onto any of those aforementioned operating systems.

However as of Guest Additions 6.1.28 (on VirtualBox 6.1.28) and also now Guest Additions 6.1.30 (on VirtualBox 6.1.30), I am constantly getting an error which prevents Guest Additions to properly install on Windows Server 2012. The error is as follows (FYI I am only showing error for latest Guest Additions version):

-----------------------------------------------
Stopped logging into separate file
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Version: 6.1.30 (Rev 148432)
Previous version: 6.1.26 (Rev 145957)
Detected OS: Windows 8_1 (64-bit)
System Directory: C:\Windows\system32
Checking for installation requirements for Vista / Windows 7 / Windows 8 ...
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: DIFxAPI.dll... 100%
Extract: VBoxDrvInst.exe... 100%
Extract: VBoxVideo.inf... 100%
Extract: VBoxVideo.cat... 100%
Extract: iexplore.ico... 100%
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Stopping VBoxService ...
Stopping VBoxService via SCM ...
Stopping VBoxService done
Stopping VBoxTray ...
Stopping VBoxTray done
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: VBoxVideo.sys... 100%
Extract: vboxdisp.dll... 100%
Extract: VBoxMouse.sys... 100%
Extract: VBoxMouse.inf... 100%
Extract: vboxmouse.cat... 100%
Extract: VBoxGuest.sys... 100%
Extract: VBoxGuest.inf... 100%
Extract: vboxguest.cat... 100%
Extract: VBoxTray.exe... 100%
Extract: VBoxControl.exe... 100%
Extract: VBoxWHQLFake.exe... 100%
Output folder: C:\Windows\system32
Extract: VBoxService.exe... 100%
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: vboxwddm.cat... 100%
Extract: VBoxWddm.sys... 100%
Extract: VBoxWddm.inf... 100%
Extract: vboxdispd3d.dll... 100%
Extract: vboxnine.dll... 100%
Extract: vboxsvga.dll... 100%
Extract: vboxicd.dll... 100%
Extract: vboxgl.dll... 100%
Extract: vboxdispd3d-x86.dll... 100%
Extract: vboxnine-x86.dll... 100%
Extract: vboxsvga-x86.dll... 100%
Extract: vboxicd-x86.dll... 100%
Extract: vboxgl-x86.dll... 100%
Extract: C:\Windows\system32\drivers\VBoxSF.sys... 100%
Skipped: C:\Windows\system32\VBoxMRXNP.dll
Extract: C:\Program Files\Oracle\VirtualBox Guest Additions\nseCA4C.tmp... 100%
Rename on reboot: C:\Program Files\Oracle\VirtualBox Guest Additions\nseCA4C.tmp->C:\Windows\system32\VBoxMRXNP.dll
Extract: C:\Windows\SysWOW64\VBoxMRXNP.dll... 100%
Extract: C:\Windows\system32\VBoxHook.dll... 100%
Installing drivers ...
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Installing guest driver ...
Executing: ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log""
Installing driver ...
INF-File: C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf
(1) ENTER:  DriverPackageInstallW
(1) RETURN: DriverPackageInstallW  (0xE0000244)
ERROR (e0000244): Unknown error!

Execution returned exit code: 2
Error excuting """"C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log"""" (exit code: 2) -- aborting installation
Error excuting """"C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log"""" (exit code: 2) -- aborting installation
-----------------------------------------------

When I then click on the [Cancel] button, an error popup appears as per the attached file ""VBox Guest Additions (6.1.30) - Pop Up Screen (20211128).jpg"". According to that popup there should be a log file named ""install_ui.log"" in the directory shown. However no such log file is written to the drive. I searched the entire guest operating system drive to be sure it was not written to some other location but no such file exists.

I am including ""VBox Guest (6.1.30) - Operating System Version (20211128).jpg"" to show the version of the VirtualBox Guest that I have the bug on.

Although I am showing only the latest 6.1.30 addition error, I was receiving a similar error for Guest Additions 6.1.28. 

I was hoping 6.1.30 Guest Additions would resolve the problem, but it did not.

I have gone to the trouble of installing a brand new VirtualBox Guest OS running Windows Server 2012 R2, and applying all Microsoft security & critical patches applicable to the operating system, before I then tested Guest Additions 6.1.30. Alas I got the same error.

Just to clarify: Guest Additions 6.1.28 and 6.1.30 installed perfectly on Windows 7, Windows 2016 and Windows 2019 without a problem. I am only experiencing the problem with Windows Server 2012 R2.

END",CuriousPaul
18342,Sound totally broken for Windows XP guest under Linux host,Linux,Windows,VirtualBox 6.0.2,2021-12-14T00:11:36Z,2021-12-14T00:11:36Z,"I just updated to VirtualBox v6.0.2 and noticed immediately that audio got totally, utterly broken and non-functional (even going up to crash programs using sounds) for my Windows XP guest under my Linux host.

Sound was working beautifully with v6.0.0 (*) and I reverted to it...

Note that the version of the extpack (6.0.0 or 6.0.2) installed (both in VirtualBox and in the guest OS) does not seem to matter: it's broken at VirtualBox level itself, apparently.

This is a showstopper bug: pretty please, fix it quickly !

Attaching relevant logs to this ticket.


----------
(*) after bad sound lag issues in the late v5.2 releases, akin to what I encountered with even older releases and reported in this ticket: https://www.virtualbox.org/ticket/15924 )",dinosaur0
20724,VB crashed after a while on company computer,Windows,Linux,VirtualBox 6.1.26,2021-12-14T13:21:57Z,2021-12-14T13:21:57Z,"Every time I try to launch my VM with Ubuntu, it's crashes after couple of seconds (sometimes after couples of minutes).
This problem is caused by my company's computer setup. When my administrator has temporarily disabled some Credential Guard, my virtual machine works great.",stefek
20728,VirtualBox Manager UI elements flicker with compositing disabled,Linux,other,VirtualBox 6.1.30,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
20729,High definition audio: cannot control volume with standard pin widgets,Windows,other,VirtualBox 6.1.28,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
20730,issue with Virtual box 6.1.3,Windows,Windows,VirtualBox 6.1.30,2021-12-16T04:02:33Z,2021-12-16T04:02:33Z,"Hi,

After upgrading VBox from 6.1.26 to 6.1.3 and installing VBox guest client on VM server, Audio driver stop working (input & output). Please see below details, I found from VM log. Also, I was trying to revert it back from 6.1.3 to 6.1.26 along with installing the previous VBox guest client. however, still it does not work. Please share your feedback to solve the issue.     

00:01:45.238665 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:45.238766 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:46.147902 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:46.154942 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:46.155013 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:51.688116 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:51.703855 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:51.703903 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:52.830026 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:52.836064 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:52.836369 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:54.355233 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:54.368893 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:54.368967 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:55.936261 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:55.950584 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:55.950695 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:02:14.811520 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:02:14.946336 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:02:14.946384 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE

01:26:10.523556 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:26:22.139051 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
01:26:22.153892 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
01:26:22.153966 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
09:40:53.702393 Audio: Device configuration of driver 'WasAPI' has changed
09:40:53.798489 Audio: Device configuration of driver 'WasAPI' has changed
09:40:54.136774 Audio: Found 6 devices for driver 'WasAPI'
09:40:54.136808 Audio: Device 'Speakers / Headphones (Realtek Audio)':
09:40:54.136808 Audio:   ID              = {0.0.0.00000000}.{8c7e1b82-8bf9-4c4c-92f7-c198b06fdfe7}
09:40:54.136809 Audio:   Usage           = output
09:40:54.136809 Audio:   Flags           = DEFAULT_OUT
09:40:54.136810 Audio:   Input channels  = 0
09:40:54.136810 Audio:   Output channels = 2
09:40:54.136827 Audio: Device 'Speakers / Headphones (Realtek Audio)':
09:40:54.136827 Audio:   ID              = {0.0.0.00000000}.{8c7e1b82-8bf9-4c4c-92f7-c198b06fdfe7}
09:40:54.136827 Audio:   Usage           = output
09:40:54.136828 Audio:   Flags           = NONE
09:40:54.136828 Audio:   Input channels  = 0
09:40:54.136828 Audio:   Output channels = 2


",Reza-DATA-Engineer
17480,Linux boot slows to a crawl when serial port is enabled for serial getty (console).,Mac OS X,Linux,VirtualBox 5.2.6,2021-12-16T21:19:26Z,2021-12-16T21:19:26Z,"This issue first appeared in VirtualBox 5.2.6. This issue does *NOT* exist in VirtualBox 5.1.32 or earlier.

We are using a custom 64 bit Linux OS that uses a serial getty on ttyS0. Prior to VirtualBox 5.2.6, the boot took less than ten seconds. The boot now takes about 20 minutes under VirtualBox 5.2.6.

The UART settings in question are as follows:

{{{ 
UART 1: I/O base: 0x03f8, IRQ: 4, attached to pipe (server) '/tmp/ttyS0'
UART 2: I/O base: 0x02f8, IRQ: 3, attached to pipe (server) '/tmp/ttyS1' 
}}}

The boot returns to normal when using VirtualBox 5.2.6 if UART 1 is turned off. Or, we can leave both UARTs on and revert back to VirtualBox 5.1.32.

I have attached log files from VirtualBox 5.2.6. One log file is with UART 1 turned on (slow boot), and the other is with UART 1 turned off (fast boot).",chuckwolber
20732,Win7 2 screen  boot failure,Windows,Windows,VirtualBox 6.1.30,2021-12-17T08:51:54Z,2021-12-17T08:51:54Z,"virtual  Win7 , 2 screen,The startup failed after KB5008212 was installed.",km Senior electrician
20736,Error when i want use a ubuntu machine,other,Linux,VirtualBox 6.1.30,2021-12-18T20:28:51Z,2021-12-18T20:28:51Z,"Hello, 

I'm on ubuntustudio and I use virtualbox 6.1.30. When I want to virtualize a ubuntu machine, i have an error message (file)
If i try to executing '/sbin/vboxconfig, i have an error , i have the passworf window which open indefinitely. ",moijeux
20737,after using save the machine state vm virtual box is not asking for login for next time,Windows,Linux,VirtualBox 6.1.30,2021-12-19T07:09:26Z,2021-12-19T07:09:26Z,"hello,
i am using Virtual Box 6.1.30 and i am running kali linux in vm my main os or host machine is windows 11 
bug is that when i am selecting 'save the machine state'  before terminating the instance and after closing that machine when i start that machine again it's not asking for login credentials user and password
it's allowing to directly use that machine without login credentials the logged in user is the same before saving the machine state.
 
",AFTAB SAMA
20739,Direct 3D Not Available On Virtualbox Windows 7 Guest,other,other,VirtualBox 6.1.30,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
629,the virtualbox GUI isn't accessible to those using screen readers,other,other,VirtualBox 2.0.4,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
20237,BridgedInterface needs trailing blank,Windows,Linux,VirtualBox 6.1.18,2021-12-22T03:54:56Z,2021-12-22T03:54:56Z,"My network interface card is a ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", host is Windows 10 20H2 build 19042.844. 
When selecting the NIC as bridged interface in the network settings, it is stored to the .vbox file as ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", however when starting the related guest I get an error message that the virtual machine cannot be started as the network interface is not existing.
I can resolve this by adding a trailing blank to the BridgedInterface in the .vbox file as:
<BridgedInterface name=""NVIDIA nForce 10/100/1000 Mbps Ethernet ""/>
before starting VirtualBox.
But whenever I change some settings of the guest, the trailing blank is removed, so I must do this again and again. ",Phantom2398
20005,POPCNT cpu flag not supported in 6.1 Ubuntu 16 guest,other,other,VirtualBox 6.1.16,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
20742,VirtualBox crashes when restoring from saved state,other,other,VirtualBox 6.1.30,2021-12-22T20:15:48Z,2021-12-22T20:15:48Z,"... then hangs when attempted to stop the VM.

",TomerB
20743,VBox 6.1.x does not boot FreeBSD EFI,Windows,BSD,VirtualBox 6.1.30,2021-12-23T00:22:56Z,2021-12-23T00:22:56Z,"Vbox 6.0.24 (or older) boots (FreeBSD) EFI images just fine.
Vbox 6.1.x (I've tried all versions) does not boot EFI but instead goes to network boot even if that's disabled for the VM.",adwsklerjuihgweiop
20744,[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000],Linux,all,VirtualBox 6.1.30,2021-12-23T21:01:06Z,2021-12-23T21:01:06Z,"VirtualBox crashed, with the following dmesg:

[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]

All VMs were forcible shutdown by the crash.

Core files attached.
",keanepgh
20745,[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000],Linux,all,VirtualBox 6.1.30,2021-12-23T21:44:29Z,2021-12-23T21:44:29Z,"VirtualBox crashed, with the following dmesg:

[98915.402109] VirtualBox[21633]: segfault at 289 ip 00007ff0a5e639f8 sp 00007ffd7c5ac148 error 4 in libQt5Gui.so.5.12.8[7ff0a5e0e000+41d000]

All VMs were forcible shutdown by the crash.

Core files attached.
",keanepgh
20746,Memory can't be read,Windows,BSD,VirtualBox 6.1.30,2021-12-23T23:22:14Z,2021-12-23T23:22:14Z,Memory can't be read,MikhailRokhin
20484,On FreeBSD host VMs with pulseaudio audio driver fail to start,other,all,VirtualBox 6.1.24,2021-12-23T23:34:47Z,2021-12-23T23:34:47Z,"I'm testing updating the FreeBSD VirtualBox port.

Starting with 6.1.24, I'm unable to start any VM using pulseaudio as the audio driver. Problem is present in 6.1.26 too.

I'm attaching the log and the vbox file for a test machine.

pulseaudio was working fine in 6.1.22.

If any further information is required please ask and I'll try to provide whatever is needed.",Guido Falsi
20748,6.1.30.148432 Install Results in Extract Path Error,Windows,Linux,VirtualBox 6.1.30,2021-12-24T15:31:48Z,2021-12-24T15:31:48Z,"Upon downloading the latest build and executing it I get the following error on Windows 10.

Failed to create extraction path 'C:\Users\ADMINI~1\AppData\Local\Temp\2\VirtualBox': VERR_PATH_NOT_FOUND

What I found is that the Temp\2 folder does not exist.  I manually created the 2 folder under temp and installation successfully completed after that.",Bruceman1
20749,High cpu usage in guest on several cores causes severe host lagging.,Windows,Linux,VirtualBox 6.1.30,2021-12-24T21:58:52Z,2021-12-24T21:58:52Z,"I have AMD Ryzen 3 3100 4-Core Processor hyperthreaded.
When I run atlas simulation job from lhc@home on virtualbox with 4 cores 
system starts to lag.",kotenok2000
20750,Examples to control VM via COM do not work,Windows,Windows,VirtualBox 6.1.30,2021-12-26T15:17:09Z,2021-12-26T15:17:09Z,"Hi!

I have a VM named Win8.1, running on a Win10 host, which can be controlled manually via the VM manager.

Now, I'd like to control it via COM, but even the examples shipped with the SDK do not work.


== Python  ==

The file SDKRef.pdf lists the following Python code in section 2.3.1.
I just changed the name of the VM  to Win8.1 and added two print commands:


{{{
import win32com.client
vbox = win32com.client.Dispatch(""VirtualBox.VirtualBox"")
session = win32com.client.Dispatch(""VirtualBox.Session"")
mach = vbox.findMachine(""Win8.1"")
print(""Machine.State: "", mach.State) 
print(""Machine SnapshotFolder: "", mach.SnapshotFolder)
progress = mach.launchVMProcess(session, ""gui"", """")
progress.waitForCompletion(-1)
}}}

The output is:
{{{
Machine.State:  1
Machine SnapshotFolder:  C:\VMs\Win8.1\Snapshots
Traceback (most recent call last):
  File ""C:\Users\webers\Desktop\vbox.py\vbox.py"", line 8, in <module>
    progress = mach.launchVMProcess(session, ""gui"", """")
  File ""<COMObject <unknown>>"", line 2, in launchVMProcess
pywintypes.com_error: (-2147352571, 'Typenkonflikt.', None, 3)
}}}

The output of the two print commands is correct, so COM in general works, but launching the VM fails with error ""Typenkonflikt"" (this is german, so it's not a Python error, but comes from my german VM installation or the german Win10 host)

 
== VBS ==

In sdk\bindings\mscom\vbs\sample, there is this listing, where I only inserted my VM name:

{{{
' $Id: vboxinfo.vbs 135976 2020-02-04 10:35:17Z bird $
'' @file
' ???
'

'
' Copyright (C) 2009-2020 Oracle Corporation
'
' This file is part of VirtualBox Open Source Edition (OSE), as
' available from http://www.virtualbox.org. This file is free software;
' you can redistribute it and/or modify it under the terms of the GNU
' General Public License (GPL) as published by the Free Software
' Foundation, in version 2 as it comes in the ""COPYING"" file of the
' VirtualBox OSE distribution. VirtualBox OSE is distributed in the
' hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
'

Sub Print(str)
   Wscript.Echo str
End Sub

Sub StartVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """")
  progress.waitForCompletion(-1)
  session.close()
End Sub


Sub StopVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  vb.openExistingSession session, mach.id
  session.console.powerDown().waitForCompletion(-1)
  session.close()
End Sub


Sub Main
   Dim vb, mach

   set vb = CreateObject(""VirtualBox.VirtualBox"")
   Print ""VirtualBox version "" & vb.version

   ' Safe arrays not fully functional from Visual Basic Script, as we
   ' return real safe arrays, not ones wrapped to VARIANT and VBS engine
   ' gets confused. Until then, explicitly find VM by name.
   ' May wish to use hack like one described in
   ' http://www.tech-archive.net/Archive/Excel/microsoft.public.excel.programming/2006-05/msg02796.html to handle safearrays
   ' if desperate

   Set mach = vb.findMachine(""Win8.1"")
   Print ""Machine: "" & mach.name  & "" ID: "" & mach.id

   StartVm vb, mach
End Sub

Main

}}}

Again, the print commands work correctly. But then, line 26 (Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """") throws an error:

{{{
Line: 26
Column: 3
Error: The object does not support the proberty or method: 'vb.openRemoteSession'
Code: 800A01B6
Source: Run time error in Microsoft VBScript 
}}}
I've also replaced ""openRemoteSesstion"" by ""launchVMProcess"", with the only result that this is replaced in the error message, too.


----

So, is there any functional example on how to control a VM via COM?",sweber
20751,Theme incompatiblity makes fonts invisible,other,other,VirtualBox 6.1.30,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
20752,VirtualBox-6.1.30-SunOS-amd64-r148432.pkg failed on Solaris 10 1/13 s10x_u11wos_24a,Solaris,other,VirtualBox 6.1.30,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
20754,No audio heard in v6.1.24 through v6.1.30,Windows,Windows,VirtualBox 6.1.30,2021-12-31T01:00:23Z,2021-12-31T01:00:23Z,"I'm currently running VirtualBox hosted on Windows 10 Pro 21H1. I have 3 guests with the following audio configurations:

Windows XP Pro 32-bit - Windows Direct Sound / ICH AC97
Windows 7 Pro 64-bit- Windows Direct Sound / Intel HD Audio
Windows 10 Pro 64-bit - Windows Direct Sound / Intel HD Audio

Under v6.1.22 the audio works for all three guests, albeit with the repeating / echoing audio which others have reported.

If I update to any version from v6.1.24 through v6.1.30, the audio in the Windows XP guest works OK, but there is no audio on my Windows 7 and Windows 10 guests.

logs from 6.1.22 and 6.1.30 attached.",doctorx
20757,CANT START ENGINE,Windows,Linux,VirtualBox 6.1.30,2022-01-02T18:44:28Z,2022-01-02T18:44:28Z,"I cannot start it or attach linux installation to apps. i researched everything, but i've found nothing...plz help me",BABBA BOI
9639,v4.1.2 and previous: amplified OpenGL mouse movements,Windows,Windows,VirtualBox 4.1.2,2022-01-04T21:25:37Z,2022-01-04T21:25:37Z,"Host:
System   -- Dell E6510: 8GB, 1.7GHz Core i7 Q720; Win7 Pro SP1 x64
Graphics -- Nvidia NVS 3100M; Forceware v270.61
Mouse -- Microsoft USB IntelliMouse Optical; IntelliPoint v8.20.409.0
VirtualBox v4.1.2

Guests:
Win7 Ultimate SP1 x64 with Guest Additions installed
Win8 Developer Preview x64 with NO Guest Additions installed


Symptoms:

When running the OpenGL program Celestia v1.6.1
which is available at http://sourceforge.net/projects/celestia/files/ 
dragging the mouse in its window with either or both mouse buttons held 
down seems to cause the application to receive many more mouse evemts
than it should or to receive unrealistically large mouse motion values.

When the LMB is dragged, the selected object should move the same amount
of distance that the mouse is dragged. Instead it ""leaps off the screen""

When the RMB is dragged, the selected object should rotate smoothly.
Instead it rotates by unpredictably large amounts.

When both buttons are held down simultaneously, the selected object
should move at a moderate speed toward or away from the viewpoint.
Instead it immediately becomes extremely close or invisibly distant.

Exactly the same symptoms are seen when running Celestia in both guests
and whether or not 2D or 3D graphics acceleration is enabled.

These symptoms are not seen when running on the host.

I am attaching a zip file containing VirtualBox logs recorded while 
running Celestia under Win8.
",Selden Ball
20756,"Picture falling apart until lock up with Wayland, 3D, VMSVGA and Linux guest",Windows,Linux,VirtualBox 6.1.30,2022-01-04T21:50:08Z,2022-01-04T21:50:08Z,"While X.org locks up almost immediately with fractional scaling with 3D enabled Wayland gives some time to work. But scrolling is ultra slow picture start falling apart  more and more until eventual lock up. It does not depend on fractional scaling. Happens with 100% as well.

Both are working without those problems without 3D enabled, except X.org does not change system-wide DPI when changing scaling and Wayland does not remember scaling setting, so resets to 100% on every boot and change of resolution.

It is Windows 10 host, Ubuntu 21.10 guest (been same with 21.04, 20.X etc).

",regs
20759,VBoxTpG: error: Failed to start 'yasm' (assembler): VERR_ACCESS_DENIED,other,other,VirtualBox 6.1.30,2022-01-05T17:05:08Z,2022-01-05T17:05:08Z,build error see log file in attach.,custom
20760,Slow performance since last update,Windows,Linux,VirtualBox 6.1.30,2022-01-06T03:47:51Z,2022-01-06T03:47:51Z,"update to windows 11 slowed things down and since the las vbox update, my VM are unusable

extreme slow speed (response,Latency,Loading)
CPU usage is high for no apparent reason (Firefox use 60% CPU (8cores)

crashes

ive installed vmware to test if it was due to windows 11 but vmware work like vbox when no probleme were existing",dparadis
20761,"VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one",Windows,all,VirtualBox 6.1.30,2022-01-06T14:01:18Z,2022-01-06T14:01:18Z,"As described here: https://forums.virtualbox.org/viewtopic.php?f=6&t=104892&start=15

Currently, i saw that issue on v6.1.97 (testing with TPM support), but i also saw it months ago on older release versions",jmar83
20762,VM crash after KVMS switch,Linux,Linux,VirtualBox 6.1.30,2022-01-07T02:17:10Z,2022-01-07T02:17:10Z,"See [https://forums.virtualbox.org/viewtopic.php?f=7&t=104891&sid=51cd5f0216603e8bec8562fd1da4b3bc] for more information.

Environment:

I have multiple PCs connected by a keyboard-video-mouse-switch (KVMS, to clearly distinguish from kvm, the kernel virtualization subsystem).  The KVMS is a FJGear USB2.0 HDMI KVM model FJ-401HUA.  I will refer to these PCs as A, B, and C.  All 3 boxes are hosting Devuan Beowulf, and all VMs running on all boxes are running Devuan Beowulf Ascii, Beowulf, or Chimaera under virtualbox 6.1.30.  All hosts are running the latest virtualbox extensions, and guests are running the latest virtualbox guest additions.

Description of the Problem:

The problem is that switching between two of these boxes causes a VM running USB 3 to crash.  After an initial switch from A to B and back to A, one VM running USB 3 on A had crashed.  In one instance, switching a second time after this from A to B and back to A, all but one VM running USB 3 had crashed and even a VM running USB 2 had also crashed.  

Detail:

I run virtualbox on PCs A and B.   I use PC A for most of my regular activities; B and C are ""test"" boxes.  However, despite B being a testbox, I do have the VMs on B networked together with some of the VMs on A.  The 3 PCs are networked through an electronic ethernet switch.

The KVMS does work, although there is a bit of a wait for the video to re-sync after a switch.   The KVMS is capable up to 1920x1080, which matches my monitor's resolution.   Normally, I don't notice any peculiar behavior related to using the manual buttons on the face of the unit.  There are some messages logged after each switch, but they have never caused an issue until I changed the VM (the one that crashed) to USB 3.

I have attached the log for the crashed VM (see above link).  These logs were created by saving them from the log dialog box in the virtualbox GUI.  I have not modified them other than to obfuscate private information.  The logs are cut short for some reason, but it is NOT related to the obfuscation script.  I can save the logs again, from the GUI again, and the same results occur.   The line counts of the log files match before and after obfuscation.


",Harry M
20764,Linux host seamless mode with windows 10 guest often don't display anything,Linux,other,VirtualBox 6.1.30,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
20008,VERR_SSM_LOAD_CONFIG_MISMATCH on vagrant snapshot restore,Mac OS X,Linux,VirtualBox 6.1.16,2022-01-12T10:12:54Z,2022-01-12T10:12:54Z,"When restoring a VM snapshot using ''vagrant snapshot restore ..'', I get the following error:

{{{
executing: vagrant snapshot restore 4-st_6_0_0_20-9f29a314b9e1f5626f0f27ebfa8fc0a92dd66e42
==> default: Forcing shutdown of VM...
==> default: Restoring the snapshot '4-st_6_0_0_20-9f29a314b9e1f5626f0f27ebfa8fc0a92dd66e42'...

Progress: 0%

Progress: 90%

==> default: Resuming suspended VM...
==> default: Booting VM...
err: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""startvm"", ""4768f166-7914-4c98-9e81-c4f351614e51"", ""--type"", ""headless""]

Stderr: VBoxManage: error: lsilogicscsi#0: Target 0 config mismatch: config=false state=true  [ver=5 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
}}}

When I try the displayed ''startvm'' command directly, I get the same error (I attached the complete log of that run to this ticket):

{{{
$ VBoxManage startvm ""4768f166-7914-4c98-9e81-c4f351614e51"" --type headless
Waiting for VM ""4768f166-7914-4c98-9e81-c4f351614e51"" to power on...
VBoxManage: error: lsilogicscsi#0: Target 0 config mismatch: config=false state=true  [ver=5 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
$
}}}

Same thing happens in the GUI, when I start the VM or Restore the snapshot.

BUT, when I Discard the saved state, the VM starts up normally. Of course, this doesn't help me, as I cannot use the GUI (see below).

When I try to Restore again, it happens again.

This is VirtualBox 6.1.16, Vagrant 2.2.10 on MacOSX 10.12. But it has happened in this form since at least VirtualBox 6.0.x.

---------------------
Background Info:

We have a script which '''automatically''' provisions a VM to contain our applications, database and everything we need to run our E2E-Tests against.

In order to speed up the provisioning, the script is split into several '''steps'''. As some steps can be quite slow, each step saves a '''VM snapshot''' at the end, so on the next run of the script, if nothing has changed, it can simply '''restore the snapshot''' instead of re-running that step again. (similar idea to the lines in a Dockerfile)

The above error mostly happens on the '''second''' run of the script, when it wants to restore the snapshot it has just taken from the last step on the first run.

The problem seems to be with '''that particular snapshot'''. When I delete it, the script will restore a previous snapshot, which works fine. It will then run the last step again, and snapshot it, and that snapshot usually is also fine.

This is happening for several months now. An interesting pattern I noticed, this only seems to happen when the last step is a '''no-op''' (which means there were two snapshots created in quick succession). It is then always this '''second''' snapshot that is broken. The '''previous''' snapshot is fine. Also when the last step is not a no-op, the error will not occur.

There is nothing peculiar about taking the snapshots, I simply issue ''vagrant snapshot save default <snapshot_name>'' each time.
",Marc Günther
20767,Limit of 2047 bytes when transferring in the clipboard from host to guest.,Windows,Windows,,2022-01-12T11:32:29Z,2022-01-12T11:32:29Z,"In version 6.1.97-148976 there is a bug with a 2kb limitation when transferring to the clipboard, from host (Windows) to guest (Windows). Any size larger than 2047 bytes simply disappears during transfer. In the opposite direction, there is no such behavior.

This does not depend on the installed add-ons in the guest, any installed version of the add-ons in the guest behaves the same with the buffer.

It looks like it only depends on the version installed on the host. Development snapshots 6.1.97-148976 always works with this bug, in release 6.1.30 there is no such behavior. ",megaslowpoke
20770,Guest Additions: Drag and Drop Fails to Work / Register,Windows,all,VirtualBox 6.1.30,2022-01-12T17:13:20Z,2022-01-12T17:13:20Z,"While the copy and paste works just as expected, I can not get drag and drop to work. I have re-installed (right before posting this) virtualbox 6.1.30 along with the appropriate 6.1.30 guest additions to double check.

To ensure I am not messing up installation, I have tried all different ways of installing the guest additions (GUI, terminal, etc).

To give you some visual, it shows a red circle with a slash through it when hovering the file over a virtualbox machine.

",metalfirefox
20766,"Frequest VM crashes, looks like host virtio driver issues",other,other,VirtualBox 6.1.30,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
19154,Using VMSVGA crashes VirtualBoxVM.exe,Windows,Linux,VirtualBox 6.1.0,2022-01-15T23:44:46Z,2022-01-15T23:44:46Z,"Using VirtualBox on a Windows 10 host. Guest is Fedora 31 running Cinnamon UI.

After booting up guest, logging in, things work fine for a few minutes. But eventually, the guest crashes with an alert, title ""VirtualBoxVM.exe - Application Error"". 

Message is: ""The instruction at 0x00007FF95B82489D referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program.""

This is using the suggested VMSVGA Graphics Controller for 3D Acceleration. Backing off to VBoxSVGA causes things to not crash, but I lose 3D.


I have had this problem in the past with previous VirtualBox versions, but it persists in 6.1.0",Paul A Sand
20773,Windows 10 Guest crashes when accessing microphone,Mac OS X,Windows,VirtualBox 6.1.30,2022-01-16T04:53:12Z,2022-01-16T04:53:12Z,"I tested using Skype. Audio playback is working. Testing the microphone causes the Win 10 VM to crash.

This appears to be a permissions problem. In Security&Privacy, VirtualBox is allowed to use the microphone, but VirtualBoxVM does not appear in the list of applications and there is no way to add it.",granada29
20774,CP2102 USB to UART Bridge Ctrl - USB Device Connection Echec (0x80004005),Windows,Windows,VirtualBox 6.1.30,2022-01-16T21:38:14Z,2022-01-16T21:38:14Z,"The Silicon Labs CP2102 USB to UART Bridge Controller doesn't work as expected.

Host : Windows 10
Guest : Windows XP SP3",ManWithNoName
15438,Guest can't access host network after resume from hibernation (hybrid sleep).,Windows,Linux,VirtualBox 5.0.20,2022-01-18T05:02:12Z,2022-01-18T05:02:12Z,"Host : Windows Server 2008 R2 SP1.[[BR]]
Guest : 64-bit Arch Linux with kernel 4.5.4-1-ARCH.[[BR]]
Network : Bridged with host network card (VirtualBox NDIS6 Bridged Networking Driver).[[BR]]

After resume from hibernation, guest can't access host network. No ping packets reach host. Rebooting guest doesn't help. Only totally powering off and then turning it on helps and guest can access host again.

Maybe related to bug ticket [https://www.virtualbox.org/ticket/14457]",hotjava1231
20765,Linux host seamless mode with windows 10 guest Keeps displaying Background the same size the last closed Window was,Linux,Windows,VirtualBox 6.1.30,2022-01-19T09:11:22Z,2022-01-19T09:11:22Z,"I installed windows 10 as a guest and run a few apps using seamless-mode
almost every time I close the last Window seamless-mode will leave me with a part of my Screen occupied by a part of my screen displaying the background of the VM and making that part of the Linux-Desktop inaccessible.

I already tried all Display / Graphics settings on the vm.

the issue happens on both KDE and XFCE. I currently use the version from the ubuntu repos: 6.1.26 but I also tried with 6.1.30 and the same issue occurs.",test111
20650,host-only network is not working on windows 10 pro with 6.1.28,Windows,Linux,VirtualBox 6.1.28,2022-01-19T11:11:01Z,2022-01-19T11:11:01Z,"I have upgraded the virtualbox to 6.1.28, and host-only network is not working.

on the gui of host-only network manager, there is only an empty list, and can't add an adapter. I also try to add an adapter by command line, but get exception as the following:

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 95 of file VBoxManageHostonly.cpp

could you help to solve this problem??",kklin
20673,Machine hang,Windows,Windows,VirtualBox 6.1.28,2022-01-20T01:04:01Z,2022-01-20T01:04:01Z,"I have Windows 11 host and VirtualBox 6.1.28. After install Guest Additions in Windows NT 4.0 Server, the machine go to Guru Meditation.

Please resolve my problem. I was attached log files and the screenshoot.",19Barto89
20781,starting guest with --type headless fails on macOS Mojave host,other,other,VirtualBox 6.1.32,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
20779,drm:vmw_host_printf [vmwgfx]] *ERROR* in version 6.1.30 & 6.1.32,Windows,Linux,VirtualBox 6.1.32,2022-01-20T08:26:05Z,2022-01-20T08:26:05Z,"CentOS 9 Stream VM provisioned with *.vdi|*.vhd|*.vmdk disk and dynamically allocated capacity of 100GB configurations gives the 'drm:vmw_host_printf [vmwgfx]] *ERROR* Failed to send host log message' after OS post installation boot. 

Included are screenshots of the error, device configurations and the host Windows OS configurations occurring on two workstations. A provisioned VM with a *.vdi|*.vhd|*.vmdk disk capacity of 45.6GB dynamically allocated encountered no issues with the post-install boot with the same CentOS 9 Stream OS.

Supporting images are attached. Please let me know if additional technical information about the issue is needed.",BrownFoxx
20782,VirtualBox revert to invalid options automatically,Windows,Linux,VirtualBox 6.1.28,2022-01-20T14:46:50Z,2022-01-20T14:46:50Z,"Hello,
  I have installed a custom Linux guest OS and I wish to keep my video card to VBoxVGA. Unfortunately VirtualBox every time I change the selection or visit the settings page, by default revert this setting to VMsvga without prompt and this driver causes kernel panic to my VM. This is not happening in older versions of VirtualBox.",ssavva
20783,CentOS 9 Stream PXE boot failure,other,Linux,VirtualBox 6.1.30,2022-01-20T16:53:41Z,2022-01-20T16:53:41Z,"Description of problem:
When installing el9 on a VirtualBox guest with an new vmdk files as the storage, the boot will fail with the error:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

A bug was submitted to Red Hat however the response is this is a VirtualBox issue.  For more details, please see/contribute to:
https://bugzilla.redhat.com/show_bug.cgi?id=2041094


How reproducible:
This consistently reproducible with implementing a work around. 

Steps to Reproduce:
1. VirtualBox 6.1.30 (Windows host)
2. Create a new Linux VM.
3. Create a new VMDK file as the disk device.
4. Boot the guest using PXE.

Actual results:
Kernel and initrd loads however the boot fails/stops with:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

Expected results:
Boot succeeds and ANACONDA start the installation.

Additional info:

If I install CentOS 8 on the guest/vmdk file and then reinstall with EL9, the installation succeeds.

I am attaching 2 console logs.  One is the initial attempt that fails.  The second contains the El8 then EL9 work-around for comparison.

",MatthewDva
20784,Dragging a file from mobile phone to guest crashes the machine,Linux,Linux,VirtualBox 6.1.26,2022-01-20T17:42:29Z,2022-01-20T17:42:29Z,"When I drag a file from phone through MTP accessed in KDE directly into an Ubuntu guest running the same operating system, VirtualBox crashes.",miklcct
20785,"VM will not start, Guru Meditation -79 (VERR_INVALID_STATE)",Linux,other,VirtualBox 6.1.22,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
20778,Game crashing when VirtualBox Host-Only Adapter is present and enabled,Windows,other,VirtualBox 6.1.32,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
20772,Catastrophic data loss with Ubuntu 21.04 guest,Mac OS X,Linux,VirtualBox 6.1.30,2022-01-22T17:04:20Z,2022-01-22T17:04:20Z,"See also #20763

Following this:

```Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen
Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED
Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out
Jan 15 21:37:35 ubuntu kernel: [1355482.810786]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY }
Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link
Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link
Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link
```

the filesystem in dmesg reports:
```
[1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.851568] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.852924] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.854644] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.856205] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.857528] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.858951] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.860305] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.862256] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
```

and the filesystem is unbootable, fsck requires run by hand, and probably some files are corrupt.


Linux ubuntu 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
12:34
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.04
Release:	21.04
Codename:	hirsute",AA
13040,VBoxManage storageattach --medium additions bug,all,all,VirtualBox 4.3.12,2022-01-24T22:35:10Z,2022-01-24T22:35:10Z,"VBoxManage storageattach assumes an empty drive when the special case ""--medium additions"" (added by changeset 44131 on 2012-12-14) is used.

In VBoxManageStorageController.cpp:handleStorageAttach, the additions handling code is only executed if GetMediumAttachment was successful.

That means the drive needs to exist (as an emptydrive or with some image already attached) for this special case. If, on the other hand, the user provides the ISO file location, there is no such requirement.

{{{
# this succeeds (path given)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --type dvddrive --medium /path/to/VBoxGuestAdditions.iso --port 3

# this succeeds (emptydrive created before adding additions)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium emptydrive --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium additions --port 3

# this fails (complains about missing ""--type"", but that's misleading)
VBoxManage storageattach base --storagectl ""SATA"" --medium none --port 3
VBoxManage storageattach base --storagectl ""SATA"" --medium additions --port 3
}}}

This behavior has been observed on Linux and Windows hosts before being tracked down in the source code (svn checkout as of 2014-05-17).
",rluethi
20625,After hardware upgrade OS/2 does not boot,Linux,other,VirtualBox 6.1.26,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
20683,PNP DETECTED FATAL ERROR,Windows,other,VirtualBox 6.1.28,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
20798,JMicron Icy Box IB-G1826MF-C31 usb connect,Linux,Windows,VirtualBox 6.1.32,2022-01-30T08:57:57Z,2022-01-30T08:57:57Z,"Hello,


I tried to connect JMicron Icy Box IB-G1826MF-C31 inside with a Crucial P5 Plus 500GB nvme m.2 ssd through USB to the guest system but I get only notification to the device connection but no drive assigned to it. If I add the drive letter manually in the disk manager of the guest system then I can browse the files on it, but only read only. The host system is a Fedora 35, the guest system which I tried was Windows 10 and Windows 7 fully updated. Any other USB devices are working, for ex. Kingston 128GB stick, or webcam, etc. If I connect this USB kit to the host system I can read and write files and folders, its the same when I use it on windows based host system. I need to use it like an usb device because the Rekordbox software (shared folders way not a solution).
Here is some info from the host system:

[924180.551542] usb 4-1: new SuperSpeed USB device number 24 using xhci_hcd
[924180.564117] usb 4-1: New USB device found, idVendor=152d, idProduct=0583, bcdDevice=83.03
[924180.564126] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[924180.564130] usb 4-1: Product: ICY  BOX
[924180.564133] usb 4-1: Manufacturer: JMicron
[924180.564136] usb 4-1: SerialNumber: DD564198838E6
[924180.567996] scsi host5: uas
[924180.568513] scsi 5:0:0:0: Direct-Access     CT500P5P SSD8             8303 PQ: 0 ANSI: 6
[924180.569234] sd 5:0:0:0: Attached scsi generic sg3 type 0
[924182.546281] sd 5:0:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[924182.546285] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[924182.546366] sd 5:0:0:0: [sdd] Write Protect is off
[924182.546367] sd 5:0:0:0: [sdd] Mode Sense: 5f 00 00 08
[924182.546562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[924182.546790] sd 5:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[924182.560170]  sdd: sdd1
[924182.584089] sd 5:0:0:0: [sdd] Attached SCSI disk

",RGeri77
19226,VM segfaults on copy with shared clipboard,Linux,Linux,VirtualBox 6.1.2,2022-01-31T10:33:36Z,2022-01-31T10:33:36Z,"When using the shared clipboard, all running VMs in certain states crash whenever some input it copied on the host.

Steps to reproduce:
1. Start VM and login
2. Open libreoffice calc on host
3. Select and copy some cells
   => VM crashes

No messages are in the VBox log of the VM, but there are some in the journal of the host.
{{{
ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
ShClipboard[1599]: segfault at 4 ip 00007fe97c14a1ae sp 00007fe95c199cf0 error 4 in VBoxSharedClipboard.so[7fe97c143000+8000]
Code: 89 c4 85 c0 78 50 48 8d 4d c0 ba 30 75 00 00 44 89 f6 4c 89 ff 67 e8 b1 c9 ff ff 41 89 c4 85 c0 78 34 48 8b 45 c0 48 8b 7b 08 <8b> 50 04 39 53 04 0f 46 53 04 48 8b 70 08 89 d2 ff 15 84 5c 00 00
audit: type=1701 audit(1579083656.742:64): auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
}}}

The issue also occurs when copying from the guest, but I currently don't have a reproducer for that. Journal message on host:
{{{
SHCLX11[3662]: segfault at 8 ip 00007efc7073d3ea sp 00007efc71b6c8a0 error 4 in VBoxSharedClipboard.so[7efc70736000+8000]
}}}

Version used is 6.0.12, but the issue was also present in at least 6.1.0.
Host is running Arch Linux, guest is Kali Linux (haven't tested with other combinations).",udine
20800,Virtual Box Machine fails on startup,Windows,Windows,VirtualBox 6.1.32,2022-01-31T16:52:10Z,2022-01-31T16:52:10Z,"Exactly as Ticket #19282

message:
------------------------------------------------
Échec de l'ouverture de session pour la machine virtuelle W10-V.

The virtual machine 'W10-V' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Administrateur\VirtualBox VMs\W10-V\Logs\VBoxHardening.log'.

Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
-----------------------------------------------------------

To solve the problem, I had to uninstall '''Trusteer Endpoint Protection by IBM''' as suggested in the aforementioned ticket",Malbec
20799,Duplicate packages in the guest OS when bridging to the LACP adapter in Windows,Windows,other,VirtualBox 6.1.32,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
20802,Interface Bug macOS Monterey and VirtualBOX 6.1.32 r149290,Mac OS X,other,VirtualBox 6.1.32,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
20790,vboxnetx adapters are having a wrong broadcast address,Linux,Linux,VirtualBox 6.1.32,2022-02-01T13:11:49Z,2022-02-01T13:11:49Z,"If I create a hostonly adapter (e.g. vboxnet2) having the following IPV4 parameters:

Address: 10.10.10.1
Netmask: '''255.255.252.0'''

I expect the following result in my host:
# ip addr
6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.11.255''' scope global vboxnet2

and NOT (see brd value)

6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.10.255''' scope global vboxnet2

It seems that there is an error creating the broadcast value on the HOST.",gabrymark26
20803,Using Greenshot for screenshot management on Host crash VirtualBox,Windows,Linux,VirtualBox 6.1.32,2022-02-01T19:13:32Z,2022-02-01T19:13:32Z,"Hello,

I use greenshot on my computer and also open Virtualbox with an Ubuntu Guest

I launch virtual box and my guest is running.

I use Greenshot to do a screenshot and open in image editor

I go on the greenshot software and copy the image to the clickboard button

Then my virtualbox software is killed When I copy this 
Environment

I use 

Windows 10 

Greenshot 1.2.10 Build 6

Virtualbox 6.1.32 r149290

Greenshot support is saying :
https://greenshot.atlassian.net/browse/BUG-2892
Greenshot places an image to the clipboard, which to our knowledge is according to the specifications from Microsoft itself.
",Greggreg
20795,Critical error occurred while running VM after Fedora 29 -> 31 upgrade,Mac OS X,Linux,VirtualBox 6.1.32,2022-02-01T22:46:14Z,2022-02-01T22:46:14Z,"
Had an older version of Fedora 29 running on VirtualBox 6.1.32.  Used the upgrade instructions from this page to upgrade from Fedora 29 to 31, https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/.  The plan was to upgrade from 29 -> 31 -> 33 -> 35.

Fedora 29 was running with no problems on VirtualBox 6.1.32.  After using the upgrade instructions with no apparent errors and the upgrade verification was successful the VM tried to restart with the new installation of Fedora 31.  At that point I got the ""A critical error occurred while running the Virtual Machine.""  The log file and  .png file are attached.  There were no changes to the VirtualBox configuration, the Fedora upgrade process is automatic and after it completes it relaunches the new version.

Note that I tried upgrading to the 6.1.33 build and got the exact same problem, the attached logs are from the 6.1.32 and 6.1.33.
",dbhinz
20804,Some keystrokes dont get recognized in vm [Windows-Host],other,other,VirtualBox 6.1.32,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
20801,trying to start video recording of a new VM makes the entire application crash,other,Windows,VirtualBox 6.1.32,2022-02-03T00:01:31Z,2022-02-03T00:01:31Z,"recording can be pre-set in the settings, so the machine will start recording as soon as it starts, which in this case crashes immediately.
or recording can be done manually by using the provided menu item, in which case it crashes in that instant.

=-=-=

Failed to get a console object from the direct session (RPC_S_SERVER_UNAVAILABLE 0x800706BA)

Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: MachineWrap
Interface: IMachine {85632c68-b555bb-4316-a900-555eb28d3413df}

=-=-=

there are various combination I have checked, 
and non seems to matter for that.

but it is a (completely empty before any installation) Windows 10 based machine.
nothing unusual other than that it is set to UEFI, and 
and I have also set modifyvm (machine name) --nested-hw-virt on

",Elad Karako
20806,GUI | Invalid use of symbol convention to express digital sizes,all,all,VirtualBox 6.1.32,2022-02-03T11:25:16Z,2022-02-03T11:25:16Z,"''Observed on OS hosts'': Linux, Windows.

Hello. Digital sizes exhibited in GUIs are by default expressed in '''byte''' (''B'') unit with their unit prefixes invariably referring to '''power of 10³ multiples'''. However a verification of any size expressed in byte unit alone in regard to those VM files having been created by this application, will indicate that they are according to '''power of 2¹⁰ multiples''' and therefore systematically faulty exhibited in GUIs, by omitting the mention ''i'', which is part of a valid symbol abbreviation in regard of size; e.g. a correct exhibition to express '''1024 bytes''' would be ''1 KiB'', not ''1 KB''.",Ricky Tigg
20808,shared clipboard does not work with Wayland,Linux,Windows,VirtualBox 6.1.32,2022-02-03T15:47:13Z,2022-02-03T15:47:13Z,"On Fedora 35 host with Win10Guest the shared clipboard works with X11, but not with Wayland.",JoKalliauer
20807,echec de l'ouverture de session pour la machine virtuelle XP,other,other,VirtualBox 6.1.32,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
20810,Can't use gpu to increase vram,Windows,Linux,VirtualBox 6.1.32,2022-02-04T09:38:45Z,2022-02-04T09:38:45Z,"Hello i have wanted to up vram, so i have set exec of virtualbox in gpu0 (nvidia graphic card) but when i launch vbox and/or virtual machine he doesn't use my gpu0 have you an idea of why ?

[[Image(https://i.imgur.com/1r4ecp6.png)]]

i have set virtualbox.exe and virtualboxvm.exe to use gpu0",Ludovic BERTHET
19851,Drag and Drop not working: VERR_ACCESS_DENIED,Windows,Linux,VirtualBox 6.1.10,2022-02-04T10:34:54Z,2022-02-04T10:34:54Z,"Hi there,

I am working with VirtualBox 6.1.12 with a Windows 10 (1909) host and a Debian 10.5 guest.
Guest Additions are seemingly installed correctly (incl. perl, etc.). Clipboard is working fine bidirectionally.
Drag and drop is not working in any direction.

I try to d&d files from Debian GNOME Files application (3.30.5-stable) to Windows Explorer and vise versa.

I am working through this:
https://www.virtualbox.org/wiki/DnDDebug

..and thus generated the two following logfile sets for 6.1.12 (originally used version) and also for 6.1.10, after I did not find 6.1.12 in the bug ticket version list and thought: 
Might not harm to test the previous version, too.

In none of the logs I could identify helpful DnD-debug msgs except in the guest log of the 6.1.12 tests:

{{{
06:03:11.674153 00007f9c03e84640 main     New guest source window 0x200005 ('<No name>')
06:03:11.777268 00007f9c03e84640 main     Error reporting pending drag and drop operation status to host: VERR_ACCESS_DENIED
06:03:11.777307 00007f9c03e84640 main     Processing message 101 failed with VERR_ACCESS_DENIED
06:03:11.790000 00007f9c03e84640 main     New guest source window 0x200005 ('<No name>')
}}}

I tried to find suitable solutions here and in the www, but was not successful.

This bug ticket is configured to 6.1.10 but was originally intended to be assigned to 6.1.12, which seems not to be possible.


Thanks in advance and best regards
Claus",ClausG
18563,Drag and drop fails from guest to host,Windows,Linux,VirtualBox 6.0.4,2022-02-04T10:49:50Z,2022-02-04T10:49:50Z,"Hello,

Drag and drop from guest (Ubuntu 18.04) to host (Windows 10) fails : the file is not created on host and following message box appears on guest : ""Dropping data...0%"" but stays at 0% undefinitely.
(drag and drop is working perfectly from host to guest).

Please find attached host and guest log files.

Thank you very much for your help.

Damien KLOTZ",damienklotz
17563,Drag and Drop does not work: Host Windows 10 and guest Linux XUbuntu 14.04,Windows,Linux,VirtualBox 5.2.6,2022-02-04T10:52:07Z,2022-02-04T10:52:07Z,"
The context: Host: Windows 10 Guest: XUbuntu 14.04 with Kernel(3.13.0-139-generic and 4.12-generic and ... does not work) linux Guest Additions 5.2.6 installed and update new Linux Kernel bidirectional clipboard  does not work

The problem: Drag and Drop between guest and host does not work in either direction after update of virtual box and linux update from 22.2.17. 

Error message: vboxvideo, vboxguest: version magic should be ""4.4.0-116-generic SMP mod_unload modversions retpolin"" ?

",m.k.IOSB
19277,Drag and Drop from Windows 8.1 to Ubuntu 18.04,Linux,Windows,VirtualBox 6.1.2,2022-02-04T10:56:17Z,2022-02-04T10:56:17Z,"Hello.
Virtualbox 6.1.2 
The latest extension pack 6.1.2
Host system is Ubuntu 18.04
Guest System is Windows 8.1
Drug and drop files or directories from host system to guest works well.
If I drag and drop a file from guest system to host everything also works fine.
But when I drag and drop directory (directory name 123456) from guest system to host system, it writes error:
Error getting information about the file «/tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456»: No such file or directory

I went to the directory /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/
There I see my files with a false slash:
123456\Hello.txt
123456\Hello2.txt
This is a file names.

But it must be /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456/Hello.txt
and etc.

Please fix a bug.
And in my home directory it create Directory with name /tmp/VirtualBox Dropped Files/2020-01-29T09:12:18.533778000Z/123456

I attach screenshots",dotmitsu
17512,"Drag-n-Drop error, Linux host, Windows 7 client",Linux,Windows,VirtualBox 5.2.6,2022-02-04T10:57:46Z,2022-02-04T10:57:46Z,"When attempting to drag a PDF attachment from Thunderbird on Linux and dropping on a Windows 7 VM desktop, I get the error:

Drag and drop operation from host to guest failed.

Drag and drop error from host (VERR_INVALID_PARAMETER).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

I have attached files per the website https://www.virtualbox.org/wiki/DnDDebug.",mfoley
20811,Test build release not installing on Linux,Linux,all,,2022-02-04T16:50:57Z,2022-02-04T16:50:57Z,"''Test build v.'': 6.1.33 r149712 (Qt5.6.1)
''Host'' Fedora 35; Gnome 41 on X.org

''Note'': Previous installation v. 6.1.32, whose source repository was RPMfusion,  did work as intended. All components related to Virtualbox were dully removed as instructed before the installation of that test build release.

Installation not operational; What follows' won't fix it.


{{{
# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system
}}}
",Ricky Tigg
19967,VirtualBox fails to boot Ubuntu 20.10 beta ISO in EFI mode,other,other,VirtualBox 6.1.14,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
19237,VBoxSVGA OpenGL upsidedown,other,other,VirtualBox 6.0.16,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
20812,VirtualBox GUI doesn't work well with dark themes,Linux,other,VirtualBox 6.1.32,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
20813,Gnome desktop icons not clickable,Linux,Windows,VirtualBox 6.1.32,2022-02-07T11:51:03Z,2022-02-07T11:51:03Z,"There is an issue with gnome desktop icons on CentOS Stream 8 host. After switch any virtualbox guest to seamless mode a linux window ""under guest"" or desktop icons cannot be clicked. Even if guest machine is minimalized. Also virtualbox menu is not clickable. This problem apears on X11 or Wayland GUI mode on host.
The same set up on CentOS 7.x works as intented.",Liwiusz
20814,Upgrade from 6.1.3 to 6.1.32 causes VT-x detection to fail,Windows,Linux,VirtualBox 6.1.32,2022-02-07T15:03:39Z,2022-02-07T15:03:39Z,"I have virtualbox running on windows 10

I have a VM that requires nested virtualization.

It ran fine under 6.1.30 but since upgrading to 6.1.32 it fails saying:

not in hypervisor partition
VT-x is disabled in the BIOS for all CPU modes

Downgrade to 6.1.30 cured the problem
I have replicated the symptoms on two different devices:

Intel Core i3-2350M 2.3GHz running Windows 10 Pro 21H2
Intel core i3-2370M 2.4 GHz Running Windows 10 Pro 21H2

",Pcrossley
20747,Memory can't be read after resuming VM from pause,Windows,BSD,VirtualBox 6.1.30,2022-02-07T18:27:06Z,2022-02-07T18:27:06Z,Memory can't be read after resuming VM from pause,MikhailRokhin
17528,vbox always aborts KDE sesssion shutdown when machine is running,Linux,Windows,VirtualBox 5.2.6,2022-02-07T21:32:30Z,2022-02-07T21:32:30Z,"This is the same as ticket 12195 which was marked closed without resolution. That ticket suggest reopening with a more recent version of VirtualBox if still relevant.

I'm using VirtualBox 5.2.6r120293 on a Linux Slackware64 14.2 host and Windows 7 guest. When I log out (KDE) I run a script shutting down the VM. Despite this, I get a message, ""KDE Workspace / Logout canceled by '/opt/VirtualBox/VirtualBox' and I have to re-logout to actually log out.

If I shutdown the VM manually, then logout, it works OK.",mfoley
20816,Installing VirtualBox Guest Additions Causes All Mouse/Pointer Drivers to Experience a Code 52 Error,Windows,all,VirtualBox 6.1.32,2022-02-08T16:13:12Z,2022-02-08T16:13:12Z,"After installing VirtualBox Guest Additions on both Windows 10 and Windows 11, the mouse/pointer immediately disappears from the screen (even before the reboot) and displays error code 52 in the device manager for all mouse/pointer drivers currently installed on the host. Currently, the only workaround to this is to disable device driver signature checks in Windows.",1Poseidon3
20695,Audio Crackling and Distorted - New,Windows,Windows,VirtualBox 6.1.30,2022-02-08T17:29:40Z,2022-02-08T17:29:40Z,"I've been getting audio crackling and distorted since the latest update (Nov 26)

Running Windows 10 with a Windows 11 VM. It was fine until the latest update of VB. I would forget I was in the VM when I watched a movie in it --- until now.

Version 6.1.30 r148432 (Qt5.6.2)",Photoman15
20817,"Monterey Guest is unstable, reboots every few minutes",Mac OS X,other,VirtualBox 6.1.32,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
20818,Cannot build module virtualbox on Ubuntu server 20.04,other,Linux,VirtualBox 6.1.26,2022-02-09T11:56:52Z,2022-02-09T11:56:52Z,"Hi,

I cannot install virtualbox ( or VMware ) on an ubuntu server 20.04.3 LTS running on Dell server PowerEdge T620 with virtualisation enable / UEFI on.
I get an error when the module is compiling. 
I 

{{{

▶ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal
}}}

▶ uname -r

{{{
5.4.0-99-generic

}}}

Linux-headers files are installed:
sudo apt-get install dkms build-essential linux-headers-`uname -r`
 

I get the following error : 

{{{
Done.
Loading new virtualbox-6.1.26 DKMS files...
Building for 5.4.0-99-generic
Building initial module for 5.4.0-99-generic
Error! Bad return status for module build on kernel: 5.4.0-99-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.26/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of virtualbox:
 virtualbox depends on virtualbox-dkms (>= 6.1.26-dfsg-3~ubuntu1.20.04.2) | virtualbox-source (>= 6.1.26-dfsg-3~ubuntu1.20.04.2) | virtualbox-modules; however:
  Package virtualbox-dkms is not configured yet.
  Package virtualbox-source is not installed.
  Package virtualbox-modules is not installed.
  Package virtualbox-dkms which provides virtualbox-modules is not configured yet.

}}}

Here is my compilation log : 

{{{
DKMS make.log for virtualbox-6.1.26 for kernel 5.4.0-99-generic (x86_64)
Wed Feb  9 12:57:40 CET 2022
make: Entering directory '/usr/src/linux-headers-5.4.0-99-generic'
  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
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/mpnotification-r0drv.o
gcc: malloc.c:2379: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
double free or corruption (!prev)
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o
Aborted
make[2]: *** [scripts/Makefile.build:270: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/SUPDrvTracer.o] Error 134
make[2]: *** Waiting for unfinished jobs....
Aborted
make[2]: *** [scripts/Makefile.build:270: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/mpnotification-r0drv.o] Error 134
/var/lib/dkms/virtualbox/6.1.26/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o: warning: objtool: rtR0MemKernelCopyLnxWorker.part.0()+0xe: redundant CLD
make[1]: *** [scripts/Makefile.build:519: /var/lib/dkms/virtualbox/6.1.26/build/vboxdrv] Error 2
make: *** [Makefile:1762: /var/lib/dkms/virtualbox/6.1.26/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.4.0-99-generic'
}}}

This is my gcc version 

{{{
gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
}}}

Any idea ? 

",dridk
20819,Upgrading to 6.1.32 Failed due to USB permissions...,Windows,all,VirtualBox 6.1.32,2022-02-09T20:30:28Z,2022-02-09T20:30:28Z,"Going trough the regular standard VirtualBox upgrade noticed upgrade to 6.1.32 failed and succeed in two different computers.

My work computer which is secured and by AD blocked the usage of USB due to Data Security requirements, failed to start after install the upgrade to 6.1.32.

However at home computer doing the exactly same upgrade, succeed because there was not constrain about the USB Security at home and not ruled by Windows AD Group Policy filtering USB.

Just like to report, being more agnostic and less intrusive will allow the usage and embracement of VirtualBox more widely.

Thank you for this fantastic product. please keep doing the great work.

Best Regards Dinooz ",Dinooz
20825,copy/paste failure from Win 10 host to Linux guest with VirtualBox 6.1.32,Windows,Linux,VirtualBox 6.1.32,2022-02-13T04:08:02Z,2022-02-13T04:08:02Z,"I am running the latest (fully patched) version of Windows 10 For Workstations as my host OS.

On that host OS, I have recently installed the latest VirtualBox 6.1.32 and its Guest Additions.

Running that VirtualBox, I have created a virtual machine and installed the latest Xubuntu 21.10 as a guest OS.

I have observed a bizarre shared clipboard problem: if I copy something from TextPad (a Windows text editor program, running on the host OS) and paste it into the guest (Xubuntu) OS, the first time I do this the paste works.  But if I try it a second time (copy some different text in TextPad, try to paste it into Xubuntu), what gets pasted is the contents of the first copy from TextPad.  It is as if the 2nd copy is not seen by Xubuntu.  But that 2nd copy is seen by other Windows applications: I can do a paste into many other applications and they see the 2nd copied text just fine.

Another weird fact: if I then copy something from Xubuntu and paste it back into TextPad, and then do a copy of something new in TextPad (besides what I copied before), then it now successfully pastes into Xubuntu.

I have only seen this issue between TextPad and Xubuntu.  If, instead, I copy from, say, Notepad++ and paste into Xubuntu, every copy and paste works just fine.

I have been running both TextPad and VirtualBox for many years, and this copy paste bug did NOT exist before ~14 months ago.

I first noticed this issue ~14 months ago, when my Win 10 box was running VirtualBox 6.1.16, and made this forum posting: https://forums.virtualbox.org/viewtopic.php?f=6&t=101174.

Several people replied because others are seeing similar problems.

When I recently updated to the latest VirtualBox 6.1.32 and installed the latest Xubuntu, I decided to revisit this bug once more.  I made this recent posting to that forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=101174&start=30#p513218

Forum user fth0, a very helpful responder, looked at my log files and did not seem to see any issue.  (His suggestions about OneDrive and ScanSnap I have a very hard time imagining how they could be the culprit.)

He suggested that I add a bug report, so here I am.  I am attaching all the files associated with my last forum posting.
",HaroldFinch
20827,VBox Guest Additions to prompt Linux users to install development modules,all,Linux,VirtualBox 6.1.32,2022-02-14T09:25:31Z,2022-02-14T09:25:31Z,"Note : Below is not a bug, but a user experience enhancement.

'''Scenario :'''
- During Oracle Linux 8 (OL8) VM creation, only 'Server with GUI' selected in installation software selection
- Post OL installation, Insert guest addition image, which will in most cases automatically popup an installation 
- Installation fails with error 'Kernel headers not found' or 'Kernel driver not installed (rc=-1908)'

'''Available Solutions :''' 
It's already well documented in [https://www.virtualbox.org/manual/ch04.html#additions-linux-install ch04] and [https://www.virtualbox.org/manual/ch02.html#externalkernelmodules ch02] of Virtualbox manuals that : Required packages may include GNU compiler (GCC), GNU Make (make), Kernel header files. So incase of OL with UEK, running below and installing vbox extension works perfectly:
{{{
sudo dnf install kernel-uek-devel-$(uname -r)
}}} 


'''Practical Scenario :'''
For users (which may include non-technical users), after a successful Linux installation, generally vbox extensions is next step. The installation of extension fails with below characteristics
- The 'Kernel headers not found' is logged between other info logs and is not necessarily the final text in the console output.
- Many first time users, including tech folks, may not spot the error initially or may not understand them at all
- The log copy-paste function cannot be enabled until the extensions are installed successfully
Users may eventually get it working by searching amongst several other fixes around the web with same generic message, but let's say it does not do that out of the box. 

'''Sample solution :'''
I'll leave the solution part to the experts, but typically for a seamless installation, perhaps something like below should be fine?[[BR]]

If kernel headers not found, then vbox extension scripts (src/VBox/Additions/linux/installer/vboxadd.sh) can prompt users : [[BR]]
`Your system is not configured for building modules needed by vbox. You may run <$install_kernel_headers> as a super user. Alternately, if you would like vbox-extensions to do this for you, press 'y' now`.

where : $install_kernel_headers = 

* `IF (UEK) THEN $install_kernel_headers = dnf install kernel-uek-devel-$(uname -r)`
* `IF (Non-UEK/RHEL/Fedora) THEN $install_kernel_headers = dnf install kernel-devel-$(uname -r)`
* `IF (UBUNTU/DEBIAN) THEN $install_kernel_headers = apt install linux-headers-$(uname -r)`
* `IF (SUSE) Install kernel-source and kernel-syms?`

and so on.. 

I also understand making a standardized approach for all distros may not be possible. But if most major ones are handled that should make one last tiny step closer to a seamless experience.

'''Error log 1:'''

{{{
VirtualBox Guest Additions: Starting
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:  /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:  /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel
5.4.17-2136.302.7.2.el8uek.x86_64. Please install them and execute
  /sbin/rcvboxadd setup
ValueError: File context for /opt/VBoxGuestAdditions-6.1.32/other/mount.vboxsf already defined
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.
}}}


'''Error log 2: ''' Secure boot turned off. (The aspect of why official vbox modules are unsigned is not being highlighted here, since this also gets solved just by installing kernel-headers)

{{{
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
'/sbin/vboxconfig'
as root.
If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
}}}

",Rajeev Sreedharan
19588,Crash - referenced memory at 0x0000000000000000,Windows,Linux,VirtualBox 6.1.6,2022-02-14T21:08:06Z,2022-02-14T21:08:06Z,"Host: Windows 10, 1803

Guest: Linux Mint, 18.3 Cinnamon 64-bit, 3.6.7

Guest Browser: Pale Moon, 28.9.3 (64-bit)

Web Site: 'https://coronavirus.jhu.edu/map.html'

Crash: ""VirtualBoxVM.exe - Application Error""

""The instruction at 0x00007FFA7B9075AD referenced memory at 0x0000000000000000. The memory could not be read.""

Status: Hard, reproducible.

Attached: C:\VMs\Mint18\Mint18-2020-05-15-12-12-36.log
",Mark Filipak
20717,networking is dropped on Linux guests under Monterey,Mac OS X,Linux,VirtualBox 6.1.30,2022-02-16T04:17:42Z,2022-02-16T04:17:42Z,"Under Monterey, I'm seeing this behavior where when starting a virtual Linux guest in bridged mode some of the time, the system can't talk to the Ethernet to obtain a DHCP address. 

Windows guests don't appear to be affected. NAT mode is not affected at all. ",mauricev1
20829,cannot assign static IP in host only adapter - other than 192.168.56.0/21,other,other,VirtualBox 6.1.32,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
20833,Linux Guest VM Crashes If Bridged Network Is Selected,Windows,Linux,VirtualBox 6.1.32,2022-02-18T04:15:58Z,2022-02-18T04:15:58Z,"I just installed VB onto my Windows 10 PC and tried to install Oracle Linux 8 onto it.  If Bridged Network is selected, the VM crashes.",jawale
20835,I cannot do normal start it only start as uncoupled start,Windows,Linux,VirtualBox 6.1.30,2022-02-21T21:56:18Z,2022-02-21T21:56:18Z,"The virtual machine 'android32bvb_7_1_int11' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\Virtual Machines\android32bvb_7_1_int11\Logs\VBoxHardening.log'.


Código resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
",Jose Nunez
20704,VirtualBox Guest Additions 6.1.30 error during install,Linux,Windows,VirtualBox 6.1.30,2022-02-21T22:16:51Z,2022-02-21T22:16:51Z,"Hello
I got an error during the install of the VirtualBox Guest Additions.
Host = Linux Mageia 64 bits
Guest = windows XP 32 bits
The error is:
2148081673 - Failed to calculate strong name from 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.cat'. Check if catalog is valid and if file is in the same directory as the INF.

It occurs since the 6.1.28 release.
6.1.26 is ok

Attached is the install_drivers.log

",courgette
20836,Time Machine won't back up VirtualBox VMs folder on Mac Monterey,Mac OS X,Windows,VirtualBox 6.1.32,2022-02-21T23:02:57Z,2022-02-21T23:02:57Z,"I have a MacBook Pro running VirtualBox 6.1.32 with a Windows 10 VM. If I try to use Time Machine to back up the 'VirtualBox VMs' directory, Time Machine hangs after transferring a trivial amount of data. The backup drive is an external drive mounted on a networked 2021 Mac mini M1 machine. If I exclude the directory from the backup list, the backup proceeds normally. Specifically, the .vdi file must be excluded for the backup to work.

Both Macs are running MacOS 12.2.1. Backup disk drive is formatted using APFS to be 3 Volumes within one Container.",LarryW-PDX
20837,Unable to get Virtualbox to run,Windows,other,VirtualBox 6.1.32,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
20822,Not able to import an OVA and converting the virtual disk to VDI,Linux,Linux,VirtualBox 6.1.32,2022-02-23T18:01:18Z,2022-02-23T18:01:18Z,"

I'm using the official Ubuntu focal cloud image in ova format downloaded from

https://cloud-images.ubuntu.com/focal/current

I try to import it with the command:
{{{
VBoxManage import focal-server-cloudimg-amd64.ova
  --options importtovdi   --vsys 0 --vmname focal-osm11
           --memory 8192 --cpus 2 --eula accept
           --unit 9 --ignore
}}}
Note: I use the importtovdi to be able to resize the disk

I get the following error
{{{           
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/paag/virt/vbox-cloud/focal-server-cloudimg-amd64.ova...
OK.
Disks:
  vmdisk1	10737418240	0	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	ubuntu-focal-20.04-cloudimg.vmdk	565177344	-1	

Virtual system 0:
 0: Suggested OS type: ""Ubuntu_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: VM name specified with --vmname: ""focal-osm11""
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: VM settings file name specified with --settingsfile: ""/home/paag/VirtualBox VMs/focal-osm11/focal-osm11.vbox""
 4: Suggested VM base folder ""/home/paag/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Ubuntu 20.04 Server (20220208)
 6: No. of CPUs specified with --cpus: 2
 7: Guest memory specified with --memory: 8192 MB
 8: Network adapter: orig VM Network, config 3, extra type=Bridged
 9: Floppy -- disabled
10: CD-ROM
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: SCSI controller, type LsiLogic
    (change with ""--vsys 0 --unit 11 --scsitype {BusLogic|LsiLogic}"";
    disable with ""--vsys 0 --unit 11 --ignore"")
12: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 12 --ignore"")
13: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 13 --ignore"")
14: Hard disk image: source image=ubuntu-focal-20.04-cloudimg.vmdk, target path=ubuntu-focal-20.04-cloudimg.vdi, controller=11;channel=0
    (change target path with ""--vsys 0 --unit 14 --disk path"";
    disable with ""--vsys 0 --unit 14 --ignore"")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_INVALID_OBJECT_STATE
VBoxManage: error: Appliance import failed
VBoxManage: error: Storage for the medium '/home/paag/VirtualBox VMs/focal-osm11/ubuntu-focal-20.04-cloudimg.vdi' is not created
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 1119 of file VBoxManageAppliance.cpp
}}}
",paaguti-u
20838,Discovered 2 vulnerabilities in VirtualBox,other,other,VirtualBox 6.1.32,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
20839,Vmbox is running too slow,Windows,all,VirtualBox 6.1.32,2022-02-24T06:58:15Z,2022-02-24T06:58:15Z,After recent update vm box running too slow . I am not able to install any iso file. ,sudip234
20840,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:01Z,2022-02-24T07:20:01Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20841,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:20Z,2022-02-24T07:20:20Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20842,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:22Z,2022-02-24T07:20:22Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20843,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:22Z,2022-02-24T07:20:22Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20844,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:23Z,2022-02-24T07:20:23Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20845,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:23Z,2022-02-24T07:20:23Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20846,Vmbox is running too slow,other,all,VirtualBox 6.1.32,2022-02-24T07:20:23Z,2022-02-24T07:20:23Z,After latest update vm box is running too slow. Even it is not installing iso file properly. After installing it get stucked.,sudip234
20847,Vbox 6.1 guest crashes when monitor powers off,other,other,VirtualBox 6.1.32,2022-02-24T14:42:54Z,2022-02-24T14:42:54Z,"Also happens if monitor input is switched to a different computer!

",mark4th
20848,Time-consuming Guest Addition installation on Windows XP Pro SP3 32-bit.,other,other,VirtualBox 6.1.32,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
20852,Machine guest freeze on the host,other,other,VirtualBox 6.0.22,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
20853,Memory can't be read after resuming VM from pause after few resumes,Windows,Windows,VirtualBox 6.1.32,2022-02-25T17:09:56Z,2022-02-25T17:09:56Z,Memory can't be read after resuming VM from pause: this time after few successful resumes.,MikhailRokhin
20831,Windows 2008 R2 issues.,Windows,Windows,VirtualBox 6.1.32,2022-03-02T07:28:34Z,2022-03-02T07:28:34Z,"Good day.
We have windows 2008 R2 enterprise as a host running on dual Xeon Silver 4210 processor mounted on ASUS motherboard Z11PR-D16 with 392 Gb of memory.
All guest machines are Windows 7 x64 with 6 Gb memory.
We faced this issue: we can run 23 VMs concurrently, but when we start 24-th VM an error appears: 
""The virtual machine 'xxx' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\VMs\XXX\Logs\VBoxHardening.log'.
E_FAIL (0x80004005)
MachineWrap
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}""
There are two logs attached, with successful start and failed one.
VirtualBox version: 6.1.32.
Successful start log
https://www.mediafire.com/file/t38s7g1r0bt4j1j/Logs-success.zip/file
Failed start log
https://www.mediafire.com/file/2v2yrjyna8toyrl/Logs-error.zip/file
",ZMKS
20446,VM intermittently freezing,Windows,Windows,VirtualBox 6.1.22,2022-03-03T03:31:57Z,2022-03-03T03:31:57Z,"Virtual Box Version 6.1.22 r144080 (Qt5.6.2)

Operating System = Windows 10 (OS Build 19042.1052)
                   VM simulating operating system = XP

Works fine for a while then freezes when repeating the same action that had worked fine just before.  

Only way to get it to unfreeze is to Close down application completely.  

Had been working on Lotus spreadsheet when it freezes.  Have had 6 freezes in 2 days.


All worked perfectly 2 versions ago, but see no way to go back to an earlier version.  Started having the problem previous version and updated to this version since it was causing the same problem.
",Sooz C
20854,Oracle VM not booting,Windows,other,VirtualBox 6.1.32,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
20855,Windows Vista Ultimate 64 Bit Guest Additions not working,Windows,Windows,VirtualBox 6.1.32,2022-03-05T13:20:20Z,2022-03-05T13:20:20Z,I am using Windows Vista Ultimate 64 Bit and I wanted to install Guest Additions so I can use Windows Aero Theme but I get an error when installing Guest Additions.,Aremon
20858,6.1.32 Ubuntu package lacks the VirtualBox.chm manual file,Linux,Linux,VirtualBox 6.1.32,2022-03-06T07:12:07Z,2022-03-06T07:12:07Z,"Help > Contents will reveal an error dialog saying ""Unable to load the chm file /usr/share/doc/virtualbox-6.1/VirtualBox.chm""

```
$ tree /usr/share/doc/virtualbox-6.1/
virtualbox-6.1/
├── changelog.Debian.gz
├── LICENSE
└── UserManual.pdf

0 directories, 3 files
```

I've extracted the package https://download.virtualbox.org/virtualbox/6.1.32/virtualbox-6.1_6.1.32-149290~Ubuntu~eoan_amd64.deb and can also verify that the file is indeed missing.","林博仁(Buo-Ren, Lin)"
20474,[vmwgfx]] *ERROR* Failed to open channel,Windows,Linux,VirtualBox 6.1.24,2022-03-06T08:22:30Z,2022-03-06T08:22:30Z,"I am running VirtualBox 6.1.24 on Win10 x64, Hyper-V is paravirtualization interface. Ubuntu 20.04 is guest OS.VM is configured to use VMSVGA with 3D enabled.

During boot up, dmesg log has many following records:

[  107.916494] 10:21:10.493550 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
               10:21:10.493575 main     Log opened 2021-07-24T10:21:10.493522000Z
[  107.916494] 10:21:10.493713 main     OS Product: Linux
[  107.916494] 10:21:10.493841 main     OS Release: 5.8.0-63-generic
[  107.916494] 10:21:10.493933 main     OS Version: #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021
[  107.916494] 10:21:10.494012 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
               10:21:10.494034 main     Process ID: 1337
               10:21:10.494057 main     Package type: LINUX_64BITS_GENERIC
[  107.920318] 10:21:10.501490 main     6.1.24 r145751 started. Verbose level = 0
[  107.927561] 10:21:10.508214 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  133.960208] rfkill: input handler disabled
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  174.892246] rfkill: input handler enabled
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.


Detailed logs are attached.",tysonite
20753,VirtualBox exe failed to install on Windows 11,Windows,Windows,VirtualBox 6.1.30,2022-03-07T12:39:31Z,2022-03-07T12:39:31Z,"Hello,

I am facing a serious problem when installing virtualbox.exe
I tried multiple versions and all didn't install knowing that before I had vbox installed normally. But when I uninstalled it to update to the new version I got this problem.

I am using Windows 11.

Proof Of Concept:
1. Open `VirtualBox-6.1.30-148432-Win.exe` and proceed with the steps.
2. I get this error while installing
Error:
The Windows Installer Service could not be accessible. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
3. And after I hit `OK`. I get the following message.
Installation failed! Error: Fatal error during installation.

Please notice that any exe files are being installed normally without any errors. I am facing this problem when just installing virtual box.

I hope you can find a solution for this problem.

Kind Regards.",ahmad_halabi
20862,PAUSEから再開した場合、オーディオが出力されない,Windows,Windows,VirtualBox 6.1.32,2022-03-09T07:32:57Z,2022-03-09T07:32:57Z,"WindowsXPでVirtualBoxをPauseにしてPauseを解除した場合、Audioが出力されません。
",aokadak@…
20777,Very slow guest VMs in 64-bit Windows (10 & 11) hosts after upgrading VirtualBox v6.1.30 to v6.1.32.,other,all,VirtualBox 6.1.32,2022-03-09T15:47:55Z,2022-03-09T15:47:55Z,"https://forums.virtualbox.org/viewtopic.php?f=6&t=104993&p=512044 for my forum thread with our details, logs, etc. Basically, our guest VMs are unusable due to being very slow.  We had to downgrade back to v6.1.30 to reuse them. :(",Ant
20234,Kernel driver not installed launching VM on Version 6.1.18 r142142 (Qt5.6.3),other,other,VirtualBox 6.1.18,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
20863,Critical error,Windows,Windows,VirtualBox 6.1.32,2022-03-09T23:44:02Z,2022-03-09T23:44:02Z,"A critical error has occurred while running the virtual machine and the machine has been stopped.

",fabio sordi
20864,"If Pause is set and Pause is canceled, Audio will not be output.",other,Windows,VirtualBox 6.1.32,2022-03-10T07:39:12Z,2022-03-10T07:39:12Z,"If the guest OS is Windows XP and VirtualBox is set to Pause and Pause is canceled, Audio will not be output.
Thank you.",aokadak@…
20865,"ause is set and Pause is canceled, Audio will not be output. (continuation)",Windows,Windows,VirtualBox 6.1.32,2022-03-11T08:54:25Z,2022-03-11T08:54:25Z,"When the guest OS does PAUSE on windows xp and cancels PAUSE, Audio is not output in VirtualBox v6.1.30, Audio is output in 6.1.32, but Audio is output after the 3rd, 4th or 2 hours. It disappears.
Thank you.",aokadak@…
20866,nao abre a sessao e consta esse erro,other,Linux,VirtualBox 6.1.32,2022-03-13T23:38:14Z,2022-03-13T23:38:14Z,"Falha ao abrir uma sessão para a máquina virtual debian2.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",YuRi25
20867,Kernel modules not re-built on updating guest additions on Linux,Windows,Linux,VirtualBox 6.1.32,2022-03-14T15:49:43Z,2022-03-14T15:49:43Z,"Calling ./VBoxLinuxAdditions.run to install a new version of guest additions (here: 6.1.32) installs everything but does not re-build kernel-modules like vboxguest, vboxsf - and neither does rcvboxadd setup. The reason is that in the latter, specifically in the function setup_modules, a check is made whether vboxguest.*o* exists for the current kernel and gives up if it does - without checking the module-version. I worked around this by deleting vboxguest.ko ... ",MAnantharaman
20868,Automated login not working on Arch Linux guest of a Windows host,Windows,Linux,VirtualBox 6.1.32,2022-03-14T16:14:42Z,2022-03-14T16:14:42Z,"I followed instructions in https://www.virtualbox.org/manual/ch09.html#autologon
to be able to login automatically on my Arch Linux host under a Windows 10 host, providing credentials as explained for Windows guests (not described for Linux guests), which shows in syslog on the Linux guest as ...
{{{
pam_vbox_setcred called, iFlags=0x4
pam_vbox_setcred: argv[0] = debug
}}}
but pam_vbox is unable to subsequently retrieve the credentials leaving the following error in syslog:
{{{
pam_vbox: 6.1.32r149290, running on amd64
pam_vbox_init: runtime initialized
pam_vbox_init: guest lib initialized
pam_vbox_init: rhost=<none>, tty=:0, prompt=<none>
her	dbus-daemon[2156]: Successfully activated service 'org.a11y.atspi.Registry'
her	SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait""=""1""
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait"" with rc=VINF_SUCCESS
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWaitTimeout"" with rc=VERR_NOT_FOUND
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsMsgWaiting"" with rc=VERR_NOT_FOUND
Showing message ""Waiting for credentials ..."" (type 4)
pam_vbox_check_creds: could not query for credentials! rc=VERR_PERMISSION_DENIED. Aborting
pam_vbox_authenticate: overall result rc=VERR_PERMISSION_DENIED
}}}
",MAnantharaman
20874,Failed to create cloud machine,other,other,VirtualBox 6.1.32,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
20857,Windows 10 21H2 - Menu Start Issue,Windows,Windows,VirtualBox 6.1.32,2022-03-18T07:41:03Z,2022-03-18T07:41:03Z,"After installing the latest VM VBox Extension Pack version 6.1.32 and checking 3d acceleration (Screen -> Acceleration -> Mark enable 3d acceleration) on a guest system (windows 10 21H2) the windows 10 start menu is unusable. 
It becomes transparent, does not scale and crashes the whole system. 
After disabling 3D acceleration - everything works fine. 

The error remains regardless of the screen parameters i.e. Video memory, number of monitors etc.



",ReconX2
20876,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,Windows,VirtualBox 6.1.32,2022-03-18T13:53:57Z,2022-03-18T13:53:57Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output. The procedure is shown below.
1.Start up Windows XP
2. Windows XP is set to PAUSE
3. 1 hour and 10 minutes elapse
4. Release PAUSE
5. AUDIO is not output
Thank you very much for your cooperation.",aokadak@…
20861,Guest Additions do not build on Centos Stream 8,Linux,Linux,VirtualBox 6.1.32,2022-03-22T16:11:33Z,2022-03-22T16:11:33Z,"Updated to the latest kernel on CentosStream 8: 4.18.0-365.el8.x86_64 and the Guest Additions does not compile anymore.
Tried the 6.1.32, then the latest 6.1.33-149980 and the result is the same: the vbox_drv.h tries to include drm/ttm/ttm_memory.h which is not available anymore in this kernel release (apparently the ttm subtree was restrustured).",piters
15925,Crackling sound with Windows 10 anniversary update,Linux,Windows,VirtualBox 5.1.6,2022-03-23T19:55:58Z,2022-03-23T19:55:58Z,"Since latest Windows 10 update (""anniversary update"") on my guest VM, sound is very crackling.

This seems to be pretty common with people having updated their Windows 10 guest: https://forums.virtualbox.org/viewtopic.php?f=7&t=79129

I was using VirtualBox 5.0.26, I've update to VirtualBox 5.1.6 with no change.

I'm using Linux host (Fedora), but in the forum thread, one user was using Windows host.",olem
20881,Guest additions on Linux(Artix) with dinit init system,Windows,Linux,VirtualBox 6.1.32,2022-03-25T13:35:55Z,2022-03-25T13:35:55Z,"
Tried to install Guest Additions by runnung ""VBoxLinuxAdditions.run"".

Install fails due to an error in ""routines.sh"".

{{{
./routines.sh: Zeile 236: systemctl: Kommando nicht gefunden
}}}

Artix Linux guest (artix-plasma-dinit-20220123-x86_64.iso) on Win10 host.
",JAMxWA
20882,SATA Controller Option Cause jbd2 blocking the disk access,other,other,VirtualBox 6.1.30,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
20883,System doesn't boot up,Linux,all,VirtualBox 6.1.32,2022-03-26T17:19:26Z,2022-03-26T17:19:26Z,When I try to launch a guest the system doesn't boot up and I get a black screen.,ar1234a
20887,Problème de démarrage de la machine,other,other,VirtualBox 6.1.32,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
20888,Windows guest hangs completely (possible cause: Split lock detected),Linux,Windows,VirtualBox 6.1.32,2022-03-28T14:19:10Z,2022-03-28T14:19:10Z,"I have a situation where a Windows 10 Professional guest reliably hangs when executing a particular program, the Office 365 installer. The host is VirtualBox 6.1.32_Debian r149290 on, well, Debian 11.3.

The kernel log shows the following:

{{{
[ 3898.986978] SUPR0GipMap: fGetGipCpu=0x1b
[ 3899.552857] vboxdrv: 00000000aeb9f67b VMMR0.r0
[ 3899.656486] vboxdrv: 00000000afb38562 VBoxDDR0.r0
[ 3899.740741] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[ 3916.929613] x86/split lock detection: #AC: ShFolders/7532 took a split_lock trap at address: 0x7efcbf042eaf
[ 6651.842406] tun: Universal TUN/TAP device driver, 1.6
[ 6815.856879] vboxdrv: 00000000bb3fe004 VMMR0.r0
[ 6815.948801] vboxdrv: 000000007f68d4c7 VBoxDDR0.r0
[ 6815.989381] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[ 6938.723256] Split lock detected
               : 0000 [#1] SMP NOPTI
[ 6938.723260] CPU: 4 PID: 9098 Comm: EMT Tainted: G           OE     5.10.0-13-amd64 #1 Debian 5.10.106-1
[ 6938.723261] Hardware name: Dell Inc. XPS 13 9310/0DMPXV, BIOS 3.4.0 12/14/2021
[ 6938.723266] RIP: 0010:0xffffc2e90460e770
[ 6938.723268] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
[ 6938.723269] RSP: 0018:ffffc2e903b879b8 EFLAGS: 00010206
[ 6938.723270] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 6938.723271] RDX: 0000000000000000 RSI: ffffc2e903b879d8 RDI: ffff9ff67a3fccfc
[ 6938.723271] RBP: ffffc2e904238000 R08: ffffc2e903b878c8 R09: ffffc2e903b87980
[ 6938.723272] R10: ffffc2e903b879cc R11: ffffc2e903b879e8 R12: ffffc2e904238000
[ 6938.723273] R13: ffffc2e903b87ba8 R14: 0000000000000000 R15: ffffc2e904227000
[ 6938.723274] FS:  00007fc0682c3700(0000) GS:ffff9ffc2f700000(0000) knlGS:fffff800534ed000
[ 6938.723275] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6938.723275] CR2: 0000000007a4b110 CR3: 000000075f4bc005 CR4: 0000000000772ee0
[ 6938.723276] PKRU: 55555554
[ 6938.723276] Call Trace:
[ 6938.723282]  ? update_load_avg+0x7a/0x5d0
[ 6938.723284]  ? dequeue_entity+0xc6/0x450
[ 6938.723285]  ? check_preempt_curr+0x29/0x60
[ 6938.723286]  ? ttwu_do_wakeup+0x17/0x130
[ 6938.723287]  ? try_to_wake_up+0x1d1/0x4f0
[ 6938.723289]  ? copy_from_kernel_nofault+0x1d/0xf0
[ 6938.723291]  ? process_fetch_insn+0x102/0x690
[ 6938.723294]  ? tomoyo_init_request_info+0x8f/0xb0
[ 6938.723296]  ? tomoyo_path_number_perm+0x66/0x1d0
[ 6938.723308]  ? VBoxHost_RTThreadCtxHookEnable+0x33/0x50 [vboxdrv]
[ 6938.723313]  ? supdrvIOCtlFast+0x66/0xb0 [vboxdrv]
[ 6938.723316]  ? VBoxDrvLinuxIOCtl_6_1_32+0x56/0x230 [vboxdrv]
[ 6938.723319]  ? __x64_sys_ioctl+0x83/0xb0
[ 6938.723321]  ? do_syscall_64+0x33/0x80
[ 6938.723322]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 6938.723323] Modules linked in: tun ctr ccm michael_mic hid_jabra usbhid uhid rfcomm cmac algif_hash algif_skcipher af_alg typec_displayport snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc bnep cdc_ether usbnet r8152 hid_sensor_als hid_sensor_trigger hid_sensor_iio_common mii industrialio_triggered_buffer kfifo_buf industrialio hid_sensor_hub snd_soc_skl_hda_dsp snd_soc_hdac_hdmi iTCO_wdt rtsx_pci_sdmmc qrtr_mhi intel_pmc_bxt iTCO_vendor_support hid_multitouch intel_ishtp_hid snd_soc_dmic mmc_core hid_generic watchdog mei_hdcp intel_rapl_msr dell_laptop dell_wmi dell_smbios dell_wmi_descriptor wmi_bmof dcdbas dell_smm_hwmon x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi irqbypass crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic ghash_clmulni_intel intel_cstate intel_uncore joydev snd_sof_pci snd_sof_intel_byt
[ 6938.723355]  snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp qrtr pcspkr snd_sof ns snd_sof_intel_hda ath11k_pci snd_soc_hdac_hda snd_hda_ext_core mhi snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio efi_pstore ath11k snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation qmi_helpers snd_soc_core mac80211 snd_compress soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_pcm snd_timer snd i2c_i801 i2c_smbus soundcore cfg80211 rtsx_pci libarc4 mei_me mei xhci_pci xhci_hcd hci_uart btqca nls_ascii btrtl nls_cp437 btbcm intel_lpss_pci btintel vfat intel_lpss fat bluetooth idma64 usbcore thunderbolt intel_ish_ipc tpm_crb intel_ishtp usb_common processor_thermal_device tpm_tis ucsi_acpi intel_rapl_common tpm_tis_core intel_soc_dts_iosf typec_ucsi tpm jitterentropy_rng typec rng_core drbg ansi_cprng wmi i2c_hid battery button ecdh_generic rfkill hid ecc int3403_thermal int340x_thermal_zone intel_pmc_core intel_hid int3400_thermal
[ 6938.723391]  sparse_keymap acpi_thermal_rel acpi_tad ac acpi_pad msr parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod i915 i2c_algo_bit drm_kms_helper cec crc32c_intel drm aesni_intel nvme psmouse glue_helper nvme_core libaes crypto_simd cryptd evdev serio_raw t10_pi crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common video
[ 6938.723410] ---[ end trace 595db24fab13b167 ]---
[ 6938.939179] RIP: 0010:0xffffc2e90460e770
[ 6938.939185] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
[ 6938.939187] RSP: 0018:ffffc2e903b879b8 EFLAGS: 00010206
[ 6938.939189] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 6938.939190] RDX: 0000000000000000 RSI: ffffc2e903b879d8 RDI: ffff9ff67a3fccfc
[ 6938.939191] RBP: ffffc2e904238000 R08: ffffc2e903b878c8 R09: ffffc2e903b87980
[ 6938.939192] R10: ffffc2e903b879cc R11: ffffc2e903b879e8 R12: ffffc2e904238000
[ 6938.939193] R13: ffffc2e903b87ba8 R14: 0000000000000000 R15: ffffc2e904227000
[ 6938.939195] FS:  00007fc0682c3700(0000) GS:ffff9ffc2f700000(0000) knlGS:fffff800534ed000
[ 6938.939196] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6938.939197] CR2: 0000000007a4b110 CR3: 000000075f4bc005 CR4: 0000000000772ee0
[ 6938.939198] PKRU: 55555554
}}}

As this is reproducible, I can supply you with more logs if needed (and if you tell me what informaton you need).",Andreas Sewe
20828,Virtualbox test build 7 Gest addition didn't install for W11 Linux host,Linux,Windows,VirtualBox 6.1.32,2022-03-30T16:37:06Z,2022-03-30T16:37:06Z,"It follows this tread : https://forums.virtualbox.org/viewtopic.php?f=2&t=105264&p=513634#p513634
I had to install 6.1.32's Guest Additions instead the one included in Virtualbox Version 6.1.97 r149824 (Qt5.15.2)
How to debug it ?",Alberto789
20890,cannot run any linux VM on ThinkPad X1 Extreme gen 4 with Windows 11 host OS,Windows,Linux,VirtualBox 6.1.32,2022-03-31T15:06:13Z,2022-03-31T15:06:13Z,"hello, I'm using VirtualBox 6.1.32 r149290 (Qt5.6.2) and i have a lot of problems running any virtual machines with linux OS. below problems:

- the system from the ISO image takes a long time to install
- after installation and selecting the ""restart"" button, the machine freezes and cannot restart
- after a reset, and trying to start the virtual machine, I get a system loading screen (the host CPU load increases), but the system does not start.
- sometimes (less than 1 of 10) system boots but runs very slowly, keeps very high activity of CPU on the host


I'm using Lenovo ThinkPad X1 Extreme gen 4 (20Y5CTO1WW): 11850H, 64GB RAM, 4TB 4th gen SSD.",krak
18680,Create symbolic links in shared folders without administrator priviledges using new Windows 10 Developer Mode,Windows,Linux,VirtualBox 6.0.8,2022-04-02T12:16:40Z,2022-04-02T12:16:40Z,"Starting with [https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/#jiIm1mzyjuXxAFXr.97 Windows 10 Insiders build 14972] symlinks can be created without needing to elevate the console as administrator. The prerequisite is to enable ''Developer Mode'', and after that any user on the machine can
1. Run the `mklink` command without elevating a command-line console
2. Use CreateSymbolicLink API '''if''' additional ''dwFlags'' option `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` is set to `0x2`.

Since even after enabling the ''Developer Mode'' VirtualBox has to be run as Administrator in order to create symlinks in shard folders, I assume the method 2 i.e. API calls are used to create them.

My enhancement request: Please add the `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` to the API call when creating symlinks to shared folders under Windows 10 so Administrator priviledges are not required when ''Developer Mode'' is enabled.",asmala
19457,Guest Addition not working with Windows NT 4.0 Guest,Windows,Windows,VirtualBox 6.1.4,2022-04-03T15:49:06Z,2022-04-03T15:49:06Z,"Steps to reproduce the issue:

Install VirtualBox 6.1.4

Install Extension_Pack-6.1.4.vbox-extpack

Create a VM and install Win NT 4.0 on the guest. I used a german OEM iso from here: https://archive.org/download/WinNTWKS40DEU/NTWKS40D.iso

Install Service Pack 6a on the guest.

Install Guest Additions on guest. The installation completes without any errors. After installing it requests a reboot.

Now, whenever I boot the VM and login a user, the system freezes for around a minute and then displays an error message.
Translated to english:
""The start of at least one service failed, which should be started at system boot. Check the Event Viewer.""

There are no information in the Event Viewer. But when I look at the services, the only service with automatic start, which is not running is ""VirtualBox Guest Additions Service"". When I manually try to start this service, the following error appears (free translation to english):
""The VirtualBox Guest Additions Service on HOSTNAME could not be started.
Error 2186: The service does not respond to the control function.""

Some functions of the guest additions are working fine, like higher resolutions and True Color mode. But Shared folders or mouse integration are not working at all. When I try the exact same procedure with VirtualBox 5.2.38, I do not get any errors.",Sbf93
20889,VM fails during starting,Windows,Windows,VirtualBox 6.1.32,2022-04-03T17:01:20Z,2022-04-03T17:01:20Z,"During starting or after a few minutes of running an error appers.
Yesterday it run without any problem, nothing new was installed to the PC.",Jirka
20892,VirtualBox critical errors occur since VirtualBox 6.1.32,all,all,VirtualBox 6.1.32,2022-04-04T11:31:18Z,2022-04-04T11:31:18Z,"VirtualBox critical errors occur since 6.1.32 from both Windows and Linux guests on both Windows and Linux hosts. When a critical error occurs, VirtualBox displays a popup asking whether I want to ignore the error for debugging or stop the VM. I had to downgrade to 6.1.30 to keep my VMs safe from those errors.",a587730
20891,Critical Error starting VM Machine,Windows,Windows,VirtualBox 6.1.32,2022-04-04T11:54:50Z,2022-04-04T11:54:50Z,"After some minutes of run, the VM go in a critical error.
Sometimes during the boot of VM I have a critical error and the VM stops.

The VM Machine has Windows 10 OS.
The host machine is Windows 7

Some days ago there was no trouble running this VM. Now I have this trouble.
I have tried to update VirtualBox (now is 6.1.32 r 149290 (Qt5.6.2)) but I have the same error.

In attach: VBox.log,  VBox.png, ""screen-shot of error""",Bebuccio
20878,Building kernel module fails on CentOS8 and Kernel 5.17,Linux,all,VirtualBox 6.1.32,2022-04-06T06:49:22Z,2022-04-06T06:49:22Z,"Had running VB6.1.32 under kernel 5.16. Reboot triggered after installing kernel 5.17. Build kernel driver failed with error.


{{{
Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.17.0-1.el8.elrepo.x86_64/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j16 modules
make[1]: warning: -j16 forced in submake: resetting jobserver mode.
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `if [ ""gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10)"" != """"gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"""" ]; then \'
make[1]: *** [Makefile:1717: prepare] Error 1
make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxdrv] Error 2

}}}
",HRZ d. Universität Bielefeld
20725,VirtualBox OHCI-controller randomly skips sending URBs to the host,all,Linux,VirtualBox 6.1.30,2022-04-06T09:23:41Z,2022-04-06T09:23:41Z,"Hello!

I have noticed some problems with USB 1.1 devices under VirtualBox.

First, I noticed that when I work with smart cards on VMs, sending some random APDU commands fails. For the test, I generate and destroy key pairs in a loop. I looked at the libccidand libusb log and found that at some point sending of the command gets stuck and fails when send operation timeout exceeds:
{{{
00000003 sending: 00 40 05 80 71 00 00 00 B4
00000005 -> 000000 6F 09 00 00 00 00 8E 00 00 00 00 40 05 80 71 00 00 00 B4
[133.818293] [00029ac3] libusb: debug [libusb_submit_transfer] transfer 0x7f04880010d8
[133.818297] [00029ac3] libusb: debug [add_to_flying_list] arm timer for timeout in 5000ms (first in line)
[133.818302] [00029ac3] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 19
[133.818479] [00029ac3] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[133.818486] [00029ac3] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[138.818506] [00029ac3] libusb: debug [usbi_wait_for_events] poll() returned 1
[138.818545] [00029ac3] libusb: debug [libusb_cancel_transfer] transfer 0x7f04880010d8
[138.835720] [00029ac3] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[138.835771] [00029ac3] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[138.835775] [00029ac3] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[138.835781] [00029ac3] libusb: debug [usbi_wait_for_events] poll() returned 1
[138.835787] [00029ac3] libusb: debug [reap_for_handle] urb type=3 status=-2 transferred=0
[138.835790] [00029ac3] libusb: debug [handle_bulk_completion] handling completion status -2 of bulk urb 1/1
[138.835792] [00029ac3] libusb: debug [handle_bulk_completion] abnormal reap: urb status -2
[138.835794] [00029ac3] libusb: debug [handle_bulk_completion] abnormal reap: last URB handled, reporting
[138.835797] [00029ac3] libusb: debug [usbi_handle_transfer_cancellation] detected timeout cancellation
[138.835799] [00029ac3] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[138.835802] [00029ac3] libusb: debug [usbi_handle_transfer_completion] transfer 0x7f04880010d8 has callback 0x7f049c94c850
[138.835804] [00029ac3] libusb: debug [sync_transfer_cb] actual_length=0
[138.835807] [00029ac3] libusb: debug [libusb_free_transfer] transfer 0x7f04880010d8
05017523 ccid_usb.c:857:WriteUSB() write failed (2/17): -7 LIBUSB_ERROR_TIMEOUT
00000004 openct/proto-t1.c:215:t1_transceive() fatal: transmit/receive failed
00000012 ifdhandler.c:1821:IFDHICCPresence() usb:072f/90cc:libudev:0:/dev/bus/usb/002/017 (lun: 0)
00000027 -> 000000 65 00 00 00 00 00 8F 00 00 00
[138.835862] [000299fb] libusb: debug [libusb_submit_transfer] transfer 0x7f04900013f8
[138.835865] [000299fb] libusb: debug [add_to_flying_list] arm timer for timeout in 5000ms (first in line)
[138.835870] [000299fb] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 10
[138.835901] [000299fb] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[138.835904] [000299fb] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
00000057 SW:
00000002 ifdwrapper.c:543:IFDTransmit() Card not transacted: 612
00000002 winscard.c:1620:SCardTransmit() Card not transacted: 0x80100016
}}}

After, I decided to look at the usbmon log (at the virtual machine) and found that sending of some URBs fail with -2 callback status:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
ffff9e538d484e40 2827180820 S Bo:2:017:2 -115 19 = 6f090000 00008e00 00000040 05807100 0000b4
ffff9e538d484e40 2832198155 C Bo:2:017:2 -2 0
ffff9e538d484e40 2832198387 S Bo:2:017:2 -115 10 = 65000000 00008f00 0000
ffff9e538d484e40 2832219064 C Bo:2:017:2 0 10 >
ffff9e538d484e40 2832219163 S Bi:2:017:2 -115 10 <
}}}

To make sure that the problem is not caused by a small timeout (libccid uses 5 second timeout), I disabled it. After that sending failed URBs gets stuck forever and usbmon log looks like this:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
ffff9e538d484e40 2827180820 S Bo:2:017:2 -115 19 = 6f090000 00008e00 00000040 05807100 0000b4
}}}

I decided to look at usbmon log of the host machine and found that the failed URBs aren't sent at all, and the log looks like this:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
}}}

Also, I found how to get usbmon log of an emulated root hub controller. Failed commands don't appear there too.

I decided that maybe there is a problem with OHCI controller emulation. During debugging I noticed that after failure HeadP and TailP of Bulk List ED (Endpoint Description) are set and aren't equal, but the OHCI controller doesn't process it, because BLF (Bulk List Filled) status is not set.

After discovering the problem, I found there is some problem with cache. To prove it I added logging of bulk_head, status at the beginning of the StartFrame function and before calling the ServiceBulkList function. I also added logging of cached and real values of TailP and HeadP at the ServiceBulkList function.

Extra log patch:
{{{
diff --git a/src/VBox/Devices/USB/DevOHCI.cpp b/src/VBox/Devices/USB/DevOHCI.cpp
index 45b23dd9..713a84a5 100644                                                                                                                                                                               	 
--- a/src/VBox/Devices/USB/DevOHCI.cpp
+++ b/src/VBox/Devices/USB/DevOHCI.cpp
@@ -1564,6 +1564,14 @@ DECLINLINE(void) ohciR3ReadEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
 #endif
 }
 
+/**
+ * Reads an OHCIED without caching.
+ */
+DECLINLINE(void) ohciR3ReadEdWithoutCaching(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+{
+	ohciR3GetDWords(pDevIns, EdAddr, (uint32_t *)pEd, sizeof(*pEd) >> 2);
+}
+
 /**
  * Reads an OHCITD.
  */
@@ -3746,12 +3754,18 @@ static void ohciR3ServiceBulkList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	&& (cIterations-- > 0))
 	{
     	OHCIED Ed;
+    	OHCIED RealEd;
 
     	/* Bail if previous processing ended up in the unrecoverable error state. */
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
+
     	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	ohciR3ReadEdWithoutCaching(pDevIns, EdAddr, &RealEd);
+   	if (Ed.TailP != RealEd.TailP || Ed.HeadP != RealEd.HeadP)
+       	Log((""Cached and real Ed mismatch: EdAddr: 0x%x. Ed.HeadP: cached=0x%x real=0x%x. Ed.TailP: cached=0x%x real=0x%x\n"", EdAddr, Ed.HeadP, RealEd.HeadP, Ed.TailP, RealEd.TailP));
+
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
     	if (ohciR3IsEdReady(&Ed))
     	{
@@ -4286,6 +4300,8 @@ static void ohciR3StartOfFrame(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThisCC)
 	/*
  	* Bulk EPs.
  	*/
+
+	Log((""StartOfFrame: Bulk head: 0x%x. Status: 0x%x\n"", pThis->bulk_head, pThis->status));
 	if (	(pThis->ctl & OHCI_CTL_BLE)
     	&&  (pThis->status & OHCI_STATUS_BLF))
     	ohciR3ServiceBulkList(pDevIns, pThis, pThisCC);
@@ -4350,6 +4366,8 @@ static DECLCALLBACK(bool) ohciR3StartFrame(PVUSBIROOTHUBPORT pInterface, uint32_
 
 	ohciR3Lock(pThisCC);
 
+	Log((""StartFrame: Bulk head: 0x%x. Status: 0x%x\n"", pThis->bulk_head, pThis->status));
+
 	/* Reset idle detection flag */
 	pThis->fIdle = true;
}}}

I got the following logs:
1. usbmon_token.log -- usbmon log on the VM
2. vb_token.log -- VirtualBox log with enabled dev_ohci (lvl 2, 3, 4) logging

As you can see cached and real value of TailP are mismatched before data interchange stuck. Also, BLF status is set before reading mismatched cache:
{{{
StartFrame: Bulk head: 0x349d1150. Status: 0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohci: Updating HCCA on frame 0x3c4d
StartOfFrame: Bulk head: 0x349d1150. Status: 0x4
Cached and real Ed mismatch: EdAddr: 0x349d1150. Ed.HeadP: cached=0x349d31e0 real=0x349d31e0. Ed.TailP: cached=0x349d31e0 real=0x349d3300
ohciR3StartOfFrame: HcCommandStatus=0x00000000: HCR=0 CLF=0 *BLF=0 OCR=0 SOC=0
*FLUSH*
HcBulkHeadED_w(0x349d1150) - old=0x349d11c0 new=0x349d1150
HcBulkCurrentED_w(0x00000000) - old=0x00000000 new=0x00000000
HcControl_w(0x000002af) => CBSR=3 PLE=1 IE=1 CLE=0 *BLE=1 HCFS=0x2 IR=0 RWC=1 RWE=0
HcCommandStatus_w(0x00000004) => HCR=0 CLF=0 *BLF=1 OCR=0 SOC=0
*END*
}}}

I tried to describe the condition which leads to stuck. I think the following happens:
1. HC enters the StartFrame function;
2. HC updates cache;
3. HCD fills TD list and sets HeadP and TailP for Bulk List;
4. HCD sets Bulk List pointer via registers;
5. HCD set BLF status;
6. HC sees that BLF status is set and enters the ServiceBulkList function;
7. HC reads old cached values of HeadP and TailP functions and sees that the TD list is not ready. Therefore it unchecks BLF status.
8. HC enters the StartFrame again at the next iteration. It sees that BLF status is unchecked and doesn't process the Bulk List (but cached values of TailP and TailP are already equal).
9. HCD waits for the Bulk List will be serviced.


I think about some solutions for this problem:
1. Set the invalidate cache flag inside some register setter functions and invalidate cache inside R3 if it's set. But it may lead to a decrease in performance.
2. Disable caching at all. It decreases performance too, but helps to avoid headaches.
3. Avoid some symptoms of the problem. If cached EDs are not ready, but the corresponding status is set, then check ED directly from memory. It's probably a bad solution, because there are some cases where cached ED is ready, but real is not. Nevertheless, it may be better for performance.

I wrote a patch for the last solution and it helped me (it's draft):
{{{
diff --git a/src/VBox/Devices/USB/DevOHCI.cpp b/src/VBox/Devices/USB/DevOHCI.cpp
index 45b23dd9..e34c0ebb 100644
--- a/src/VBox/Devices/USB/DevOHCI.cpp
+++ b/src/VBox/Devices/USB/DevOHCI.cpp
@@ -1550,20 +1550,25 @@ DECLINLINE(void) ohciR3CacheTdUpdate(POHCICC pThisCC, RTGCPHYS32 TdAddr, PCOHCIT
 /**
  * Reads an OHCIED.
  */
-DECLINLINE(void) ohciR3ReadEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+DECLINLINE(void) ohciR3ReadEdEx(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd, bool cached)
 {
 # ifdef VBOX_WITH_OHCI_PHYS_READ_STATS
 	physReadStatsUpdateDesc(&g_PhysReadState.ed, EdAddr);
 	physReadStatsUpdateDesc(&g_PhysReadState.all, EdAddr);
 # endif
 #ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
-	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
-	ohciR3PhysReadCacheRead(pDevIns, &pThisCC->CacheED, EdAddr, pEd, sizeof(*pEd));
+	if (cached) {
+    	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
+    	ohciR3PhysReadCacheRead(pDevIns, &pThisCC->CacheED, EdAddr, pEd, sizeof(*pEd));
+	}
 #else
 	ohciR3GetDWords(pDevIns, EdAddr, (uint32_t *)pEd, sizeof(*pEd) >> 2);
 #endif
 }
 
+#define ohciR3ReadEd(pDevIns, EdAddr, pEd) \
+ 	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 1)
+
 /**
  * Reads an OHCITD.
  */
@@ -3701,6 +3706,31 @@ DECLINLINE(bool) ohciR3IsEdReady(PCOHCIED pEd)
      	&& !(pEd->hwinfo & ED_HWINFO_SKIP);
 }
 
+/**
+ * Tries to get ready an OHCIED from cache and on fail dirrectly from memory.
+ */
+DECLINLINE(bool) ohciR3TryReadReadyEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+{
+#ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
+	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 1);
+	if (ohciR3IsEdReady(pEd))
+    	return true;
+#endif
+
+	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 0);
+	if (ohciR3IsEdReady(pEd)) {
+#ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
+    // Cache contains old page. Invalidate it.
+    	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
+    	ohciR3PhysReadCacheInvalidate(&pThisCC->CacheED);
+    	ohciR3PhysReadCacheInvalidate(&pThisCC->CacheTD);
+#endif
+    return true;
+	}
+
+	return false;
+}
+
 
 /**
  * Checks if an endpoint has TDs queued (not necessarily ready to have them processed).
@@ -3751,9 +3781,9 @@ static void ohciR3ServiceBulkList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	bool ready = ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed);
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ready)
     	{
         	pThis->status |= OHCI_STATUS_BLF;
         	pThis->fBulkNeedsCleaning = true;
@@ -3909,9 +3939,9 @@ static void ohciR3ServiceCtrlList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	bool ready = ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed);
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ready)
     	{
 # if 1
         	/*
@@ -3928,8 +3958,7 @@ static void ohciR3ServiceCtrlList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
                 	pThis->status |= OHCI_STATUS_CLF;
                 	break;
             	}
-            	ohciR3ReadEd(pDevIns, EdAddr, &Ed); /* It might have been updated on URB completion. */
-        	} while (ohciR3IsEdReady(&Ed));
+        	} while (ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed));
 # else
         	/* Simplistic, for debugging. */
         	ohciR3ServiceHeadTd(pThis, VUSBXFERTYPE_CTRL, &Ed, EdAddr, ""Control"");
@@ -3991,8 +4020,7 @@ static void ohciR3ServicePeriodicList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC p
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed))
     	{
         	/*
          	* ""There is no separate head pointer of isochronous transfers. The first
}}}

I admit that you may have no USB 1.1 smart card to reproduce the bug. So, I found how to reproduce the bug via USB 1.1 flash drive (or via any other flash drive connected via USB 1.1 hub).

I wrote a test thatmounts and unmounts a flash drive in a loop, and noticed that sometimes the execution of these operations takes a lot of time.

test.sh:
{{{
i=0
while true
do
    i=$(($i+1))
    echo ""Iteration $i""
    date +""%T""
    mount /dev/sdb1 /media/kek || break
    umount /dev/sdb1 || break
done
}}}

output:
{{{
Iteration 1
18:06:49
Iteration 2
18:06:51
Iteration 3
18:07:26
Iteration 4
18:07:28
Iteration 5
18:07:30
}}}

Inside the OHCI log I found the same problem as for a smart card:
usbmon_falsh.log -- usbmon log for looped mount and unmount
vb_flash.log -- VirtualBox output

What do you think about that? May you confirm the bug? Will it be fixed?

Also, I found some problems with EHCI controller emulation, but will write about that in another bug.

Waiting for your response!
Thanks!",lo1ol
20893,Guest Windows XP 32 bit does not start anymore after network crash,Windows,Windows,VirtualBox 6.1.32,2022-04-06T13:29:35Z,2022-04-06T13:29:35Z,"Host: Windows 10 64 bit (12 Gb installed RAM, 8 CPU's)
Guest: Windows XP 32 bit (1 Gb allowed RAM, 1 CPU allowed)
Network: Windows Server 2008 R2

Yesterday there was a problem in the server (hung), while that happened I had an old program running locally within the VM. In spite of that, I still closed everything apparently in a normal way.
Today I cannot launch the host, when I try I get the message in the image [[Image()]]
My system is in Spanish but it informs that there was a critical error during the execution of the VM and has been stopped; it supplies the option to continue (Ignore button), I tried it to no avail.
All I get when I try to launch the host is a black screen and, sometimes, the message in the attached image, other times it just stays there and I have to shut it down using the X button.
By the way, I've been using VM for years and this is the very first time that I have a problem I cannot solve easily, in fact I don't remember ever having problems before. Thanks in advance.",Mamá Cora
20894,VirtualBox 6.1.30 & 6.1.32 VM terminated returning from hibernate,Windows,Linux,VirtualBox 6.1.32,2022-04-08T18:27:43Z,2022-04-08T18:27:43Z,"Hello,

I have a Ubuntu VM on a Windows 10 Host on a laptop.
When returning from hibernate status while powered on battery, the VM cannot be resumed and a VirtualBox error window states a critical error has occurred and the VM must be terminated.

I get the same result with both VirtualBox 6.1.30 and 6.1.32.
VirtualBox log is only showing ""emR3Debug: rc=VERR_VMX_INVALID_VMXON_PTR"" as last info before the PC goes to hibernate state.
All rest of the log file does not exhibit any meaningful message.

Any help is very appreciated as I suspect more a VM setting issue than a bug but I am not certain and I do not know what kind of VM setting has to be tuned.

Thanks

Laurent",Laurentzed
20895,Better error messages when starting Linux image on Windows 11,Windows,Linux,VirtualBox 6.1.32,2022-04-10T20:03:41Z,2022-04-10T20:03:41Z,"I need better error messages when starting a new Ubuntu image on Windows 11 Home edition. Please so some basic checks in VirtualBox that everything is in order before starting the Ubuntu image. 

Host: Windows 11 Home edition
Guest os: Ubuntu 

For example, is there some Windows Hyper-V settings that needs to be changed? Do I need to uninstall Hyper-V?

Running Vagrant with VirtualBox from this Vagrantfile:
https://github.com/freeciv/freeciv-web/blob/develop/Vagrantfile

The last messages in the VirtualBox log is this:
00:00:07.916785 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored
00:00:08.794811 GIM: KVM: Enabled wall-clock struct. at 0x00000000bfc00000 - u32Sec=1649620734 u32Nano=685699103 uVersion=2
00:00:09.850407 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:10.164896 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)",AndreasRosdal
20897,VBoximg-mount : error in documentation,all,all,VirtualBox 6.1.32,2022-04-11T08:28:11Z,2022-04-11T08:28:11Z,"Hi,

In the VBox User Manual.pdf as in the web pages, regarding vboximg-mount, the string 
{{{
-i=afile.vdi
}}}

 is WRONG ! '''Must be''' 

{{{
-i afile.vdi
}}}

Same problem with 
{{{
--image
}}}
, of course.


Regards,[[BR]]
--[[BR]]
jpt",jpt
19199,Mouse Integration Not working,Windows,Windows,VirtualBox 6.1.0,2022-04-11T10:28:29Z,2022-04-11T10:28:29Z,Updated to VirtualBox 6.1 this morning and mouse integration is no longer working.  The Mouse Integration option is checked and grayed out.  Mouse integration is not working at all.,cmccarron
17264,Virtualbox 5.1.30 Error,Windows,Windows,VirtualBox 5.1.30,2022-04-11T10:30:15Z,2022-04-11T10:30:15Z,"After installing a program in the virtual machine when I reboot the virtual machine I get the following error:

Failed to get a console object from the direct session (RPC_E_DISCONNECTED).


Result Code: 
VBOX_E_VM_ERROR (0x80BB0003)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
",cmccarron
15351,Oracle VM VirtualBox Manager Crashes on Shutdown,Windows,Windows,VirtualBox 5.0.18,2022-04-11T10:31:23Z,2022-04-11T10:31:23Z,"I know there are quite a bit of ticket dealing with Virtualbox crashing during shutdown.  This is not a problem with a guest but with the Oracle VirtualBox Manager.  This has been present since 5.0.0 was released.  I have tested every release since 5.0.0 including 5.0.18.

Host OS:  Windows 7 64bit
Guest OS:  Windows 7 32bit

How to Reproduce

1.  Open Oracle VM VirtualBox Manager, do not start a guest.
2.  Shutdown the Windows 7 Host computer.
3.  This should generate the errors attached.
",cmccarron
20898,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) during Windows 11 update,Windows,Windows,VirtualBox 6.1.32,2022-04-11T15:58:00Z,2022-04-11T15:58:00Z,Just got a guru meditation during the update of the Windows 11 in VM. Here are the logs and the picture.,boxer01
20820,Hardening Issue since 6.1.32,Windows,Windows,VirtualBox 6.1.32,2022-04-11T18:42:29Z,2022-04-11T18:42:29Z,"Since 6.1.32-149290 I have a hardening error. The last version without this issue was 6.1.31-148916. 

I get an error ""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)"" when I try to start a VM. The nonworking versions are also 6.1.33-149396, 6.1.33-149686, 6.1.33-149825. The logs from the version 
6.1.33-149686 are attached. 

This is Windows 10 21H2 VM on Windows 10 21H2 machine.
",boxer01
20899,show the VM logs from the running machine window,other,other,VirtualBox 6.1.30,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
19869,USB audio interface Scarlett 4i4 3GEN no output sound,Linux,Windows,VirtualBox 6.1.14,2022-04-12T11:56:35Z,2022-04-12T11:56:35Z,"First of all i have a question: if you have a linux host with windows 10 guest, where should i post for bugs/problems in the forum of linux hosts or in the windows guests ?
Said this, i have an scarlet4i4 focusrite 3gen audio interface, after several tries and problems i get it to setup and make it work.... but i have no output sound in my speakers.

Seems that the setup is correct and in windows works, but some kind the sound gets lost from output of the guest 



",edufissure
20431,Sound lost after a couple of changes of host audio output device,Windows,Windows,VirtualBox 6.1.22,2022-04-12T16:23:36Z,2022-04-12T16:23:36Z,"I have found another bug, which looks similar to an old one from #17225: if I change the host output from speaker to the Bluetooth headphones, the sound of VBox goes to the headphones. Then I change back and the VBox sounds also goes to the speakers. But the next time I repeat the change to Bluetooth, the VBox ignores it. The sound form the host and programs, running on the host played in the Bluetooth headphones, but the sound from VBox is lost. If I turn the BT headphones off, the VBox sound returns to the speakers, but I can't get the VBox sound to the Bluetooth anymore. The only way is to save and restore the VM state or to turn the VM off and then on (restart).

All information about how I test the sound in VBox is in other ticket.  I'm on 6.1.23 version 145326 now.",boxer01
20900,VirtualBox crashes on startup: Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.,Windows,all,VirtualBox 6.1.32,2022-04-14T06:08:29Z,2022-04-14T06:08:29Z,"When I start VirtualBox it crashes immediate.
Message is:
Het is niet gelukt het VirtualBox COM-object te verkrijgen.
Het programma wordt nu afgesloten.

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.
Resultaatcode: REGDB_E_CLASSNOTREG (0x80040154)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Un- and reinstalled VB, but still same problem.
I added a bugreport file

",A3aan
16819,Mouse Pointer Issue - Constant left click,Windows,Windows,VirtualBox 5.1.22,2022-04-16T03:23:16Z,2022-04-16T03:23:16Z,"After running Virtualbox 5.1 for a period of time (time varies) the mouse pointer will end up in a constant left click.  If I hover over anything it will try to open/click. If I open the start menu the first thing hovered over is what gets opened. Restarting the VM will temporarily fix the issue however it consistently recurs. I did not see the problem pre version 5.1.

Host: Windows 7 64bit pro
Guest:Windows 7 64bit pro",surreal_life
16237,VirtualBox can't find Virtual adapters for vlans on Windows 7,other,other,VirtualBox 5.1.10,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
17215,"Guest additions command line updating fails (Linux host, Windows guest) => Obsolete",Linux,Windows,VirtualBox 5.2.0,2022-04-19T14:54:50Z,2022-04-19T14:54:50Z,"I have a Linux host (Ubuntu 16.04, 64 bits) and a Windows guest (Windows 7 professional, 64 bits). I try to update the guest additions using the command line.

So I issue the command (from the Linux host, with the VM guest powered on):
{{{
VBoxManage guestcontrol ""win7""  updateadditions --source /usr/share/virtualbox/VBoxGuestAdditions.iso --verbose
}}}
The command fails and I get the following output:
{{{
Updating Guest Additions ...
Using source: /usr/share/virtualbox/VBoxGuestAdditions.iso
VBoxManage: error: Could not open guest session: VERR_TIMEOUT
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestWrap, interface IGuest, callee nsISupports
VBoxManage: error: Context: ""UpdateGuestAdditions(Bstr(strSource).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aUpdateFlags), pProgress.asOutParam())"" at line 3667 of file VBoxManageGuestCtrl.cpp
}}}
I tried with Virtualbox 5.1.30 and 5.2.0 and I get the same result.

Manually updating the guest additions (withon the guest) works as expected.

And I was also able to start a program within the guest, using commands like:
{{{
VBoxManage guestcontrol ""win7"" --username my_account run --exe ""C:\Windows\System32\notepad.exe""
}}}
So, I think this issue is clearly a bug...",roland651
20906,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,Windows,VirtualBox 6.1.34,2022-04-22T00:50:34Z,2022-04-22T00:50:34Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
20775,Mouse click doesn't work in window for choice iso,Linux,other,VirtualBox 6.1.32,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
20911,Virtual box unable to start VM failing with error (rc=-5640),Windows,Linux,VirtualBox 6.1.32,2022-04-23T09:11:32Z,2022-04-23T09:11:32Z,"(rc=-5640)
Please try reinstalling VirtualBox.
where: supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.",Prateek DA
20915,SessionState never unlocked,other,other,VirtualBox 6.1.32,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
20908,Cannot install or delete VirtualBox,Windows,Windows,VirtualBox 6.1.34,2022-04-26T12:47:42Z,2022-04-26T12:47:42Z,I migrated VitualBox from my Windows 10 computer to my Windows 11 computer. VirtualBox won't start; trying to Repair it is unsuccessful; trying to Reinstall it is unsuccessful; trying to Delete it is unsuccessful. Please help!,HorseyBob
20880,No Sound,Windows,Linux,VirtualBox 6.1.32,2022-04-26T17:50:26Z,2022-04-26T17:50:26Z,"6.0.18 Kali 2022.1 vm.  No sound.  6.0.24 Kali 2022.2. No sound.  6.1.32 r149290 (Qt5.6.2) Kali 2022.1.  No sound.  Tried removing vbox and reinstall. Tried Ubuntu desktop latest distro.  No sound.  

Any advice would be great and thank you.  I love vbox.

Log:
{{{

00:00:04.300986 VirtualBox VM 6.1.32 r149290 win.amd64 (Jan 17 2022 11:29:30) release log
00:00:04.300991 Log opened 2022-03-24T05:10:51.555341700Z
00:00:04.300992 Build Type: release
00:00:04.300996 OS Product: Windows 7
00:00:04.300997 OS Release: 6.1.7601
00:00:04.300998 OS Service Pack: 1
00:00:04.555010 DMI Product Name: 0914                            
00:00:04.562185 DMI Product Version: Ideapad Z560                    
00:00:04.563273 Firmware type: BIOS
00:00:04.563288 Host RAM: 7990MB (7.8GB) total, 5148MB (5.0GB) available
00:00:04.563294 Executable: E:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:04.563296 Process ID: 4100
00:00:04.563297 Package type: WINDOWS_64BITS_GENERIC
00:00:04.565222 Installed Extension Packs:
00:00:04.565361   Oracle VM VirtualBox Extension Pack (Version: 6.1.32 r149290; VRDE Module: VBoxVRDP)
00:00:04.567121 Console: Machine state changed to 'Starting'
00:00:04.567375 Qt version: 5.6.2
00:00:04.571103 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:04.773997 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:04.774024 SUP: seg #1: R X 0x00001000 LB 0x00109000
00:00:04.774027 SUP: seg #2: R   0x0010a000 LB 0x0004a000
00:00:04.774031 SUP: seg #3: RW  0x00154000 LB 0x00013000
00:00:04.774048 SUP: seg #4: R   0x00167000 LB 0x0000e000
00:00:04.774051 SUP: seg #5: RW  0x00175000 LB 0x00003000
00:00:04.774054 SUP: seg #6: R   0x00178000 LB 0x0000b000
00:00:04.774057 SUP: seg #7: RWX 0x00183000 LB 0x00002000
00:00:04.774060 SUP: seg #8: R   0x00185000 LB 0x00007000
00:00:04.775744 SUP: Loaded VMMR0.r0 (E:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:04.775804 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:04.775807 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:04.777776 Guest OS type: 'Debian_64'
00:00:04.778741 fHMForced=true - No raw-mode support in this build!
00:00:04.782637 File system of 'C:\Users\Home\Downloads\kali-linux-2022.1-installer-amd64.iso' (DVD) is ntfs
00:00:04.786993 File system of 'E:\Users\Home\VirtualBox VMs\Kali\Snapshots' (snapshots) is unknown
00:00:04.787013 File system of 'E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi' is ntfs
00:00:04.824560 Shared Clipboard: Service loaded
00:00:04.824585 Shared Clipboard: Mode: Bidirectional
00:00:04.824698 Shared Clipboard: Service running in normal mode
00:00:04.845565 Drag and drop service loaded
00:00:04.845590 Drag and drop mode: Bidirectional
00:00:04.869561 ************************* CFGM dump *************************
00:00:04.869566 [/] (level 0)
00:00:04.869572   CpuExecutionCap   <integer> = 0x0000000000000064 (100)
00:00:04.869576   EnablePAE         <integer> = 0x0000000000000000 (0)
00:00:04.869580   HMEnabled         <integer> = 0x0000000000000001 (1)
00:00:04.869582   MemBalloonSize    <integer> = 0x0000000000000000 (0)
00:00:04.869584   Name              <string>  = ""Kali"" (cb=5)
00:00:04.869586   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:04.869589   PageFusionAllowed <integer> = 0x0000000000000000 (0)
00:00:04.869591   RamHoleSize       <integer> = 0x0000000020000000 (536 870 912, 512 MB)
00:00:04.869595   RamSize           <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:04.869601   TimerMillies      <integer> = 0x000000000000000a (10)
00:00:04.869603   UUID              <bytes>   = ""c6 81 a3 0c 11 15 18 46 a8 9b 22 69 d5 9b 31 1f"" (cb=16)
00:00:04.869680 
00:00:04.869682 [/CPUM/] (level 1)
00:00:04.869685   GuestCpuName       <string>  = ""host"" (cb=5)
00:00:04.869687   NestedHWVirt       <integer> = 0x0000000000000000 (0)
00:00:04.869689   PortableCpuIdLevel <integer> = 0x0000000000000000 (0)
00:00:04.869691   SpecCtrl           <integer> = 0x0000000000000000 (0)
00:00:04.869694 
00:00:04.869694 [/CPUM/IsaExts/] (level 2)
00:00:04.869700 
00:00:04.869700 [/DBGC/] (level 1)
00:00:04.869701   GlobalInitScript <string>  = ""C:\Users\Home\.VirtualBox/dbgc-init"" (cb=36)
00:00:04.869702   HistoryFile      <string>  = ""C:\Users\Home\.VirtualBox/dbgc-history"" (cb=39)
00:00:04.869703   LocalInitScript  <string>  = ""E:\Users\Home\VirtualBox VMs\Kali/dbgc-init"" (cb=44)
00:00:04.869704 
00:00:04.869704 [/DBGF/] (level 1)
00:00:04.869705   Path <string>  = ""E:\Users\Home\VirtualBox VMs\Kali/debug/;E:\Users\Home\VirtualBox VMs\Kali/;cache*E:\Users\Home\VirtualBox VMs\Kali/dbgcache/;C:\Users\Home\"" (cb=141)
00:00:04.869706 
00:00:04.869706 [/Devices/] (level 1)
00:00:04.869707 
00:00:04.869707 [/Devices/8237A/] (level 2)
00:00:04.869708 
00:00:04.869708 [/Devices/8237A/0/] (level 3)
00:00:04.869709   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869710 
00:00:04.869710 [/Devices/GIMDev/] (level 2)
00:00:04.869711 
00:00:04.869711 [/Devices/GIMDev/0/] (level 3)
00:00:04.869713   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869713 
00:00:04.869713 [/Devices/VMMDev/] (level 2)
00:00:04.869714 
00:00:04.869715 [/Devices/VMMDev/0/] (level 3)
00:00:04.869716   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869717   PCIDeviceNo   <integer> = 0x0000000000000004 (4)
00:00:04.869718   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869718   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869719 
00:00:04.869719 [/Devices/VMMDev/0/Config/] (level 4)
00:00:04.869720   GuestCoreDumpDir <string>  = ""E:\Users\Home\VirtualBox VMs\Kali\Snapshots"" (cb=44)
00:00:04.869722 
00:00:04.869722 [/Devices/VMMDev/0/LUN#0/] (level 4)
00:00:04.869723   Driver <string>  = ""HGCM"" (cb=5)
00:00:04.869724 
00:00:04.869724 [/Devices/VMMDev/0/LUN#0/Config/] (level 5)
00:00:04.869725   Object <integer> = 0x0000000008ae67f0 (145 647 600)
00:00:04.869726 
00:00:04.869726 [/Devices/VMMDev/0/LUN#999/] (level 4)
00:00:04.869728   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869728 
00:00:04.869728 [/Devices/VMMDev/0/LUN#999/Config/] (level 5)
00:00:04.869730   First   <integer> = 0x0000000000000000 (0)
00:00:04.869730   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869731   papLeds <integer> = 0x0000000003eef1c8 (65 991 112)
00:00:04.869732 
00:00:04.869732 [/Devices/acpi/] (level 2)
00:00:04.869733 
00:00:04.869734 [/Devices/acpi/0/] (level 3)
00:00:04.869735   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869736   PCIDeviceNo   <integer> = 0x0000000000000007 (7)
00:00:04.869736   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869737   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869738 
00:00:04.869738 [/Devices/acpi/0/Config/] (level 4)
00:00:04.869740   CpuHotPlug          <integer> = 0x0000000000000000 (0)
00:00:04.869741   FdcEnabled          <integer> = 0x0000000000000000 (0)
00:00:04.869742   HostBusPciAddress   <integer> = 0x0000000000000000 (0)
00:00:04.869743   HpetEnabled         <integer> = 0x0000000000000000 (0)
00:00:04.869743   IOAPIC              <integer> = 0x0000000000000001 (1)
00:00:04.869744   IocPciAddress       <integer> = 0x0000000000010000 (65 536)
00:00:04.869745   NumCPUs             <integer> = 0x0000000000000002 (2)
00:00:04.869746   Parallel0IoPortBase <integer> = 0x0000000000000000 (0)
00:00:04.869747   Parallel0Irq        <integer> = 0x0000000000000000 (0)
00:00:04.869747   Parallel1IoPortBase <integer> = 0x0000000000000000 (0)
00:00:04.869748   Parallel1Irq        <integer> = 0x0000000000000000 (0)
00:00:04.869749   Serial0IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:04.869749   Serial0Irq          <integer> = 0x0000000000000000 (0)
00:00:04.869750   Serial1IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:04.869751   Serial1Irq          <integer> = 0x0000000000000000 (0)
00:00:04.869752   ShowCpu             <integer> = 0x0000000000000001 (1)
00:00:04.869752   ShowRtc             <integer> = 0x0000000000000000 (0)
00:00:04.869753   SmcEnabled          <integer> = 0x0000000000000000 (0)
00:00:04.869754 
00:00:04.869754 [/Devices/acpi/0/LUN#0/] (level 4)
00:00:04.869755   Driver <string>  = ""ACPIHost"" (cb=9)
00:00:04.869756 
00:00:04.869756 [/Devices/acpi/0/LUN#0/Config/] (level 5)
00:00:04.869758 
00:00:04.869758 [/Devices/acpi/0/LUN#1/] (level 4)
00:00:04.869759   Driver <string>  = ""ACPICpu"" (cb=8)
00:00:04.869759 
00:00:04.869760 [/Devices/acpi/0/LUN#1/Config/] (level 5)
00:00:04.869761 
00:00:04.869761 [/Devices/ahci/] (level 2)
00:00:04.869762 
00:00:04.869762 [/Devices/ahci/0/] (level 3)
00:00:04.869764   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869765   PCIDeviceNo   <integer> = 0x000000000000000d (13)
00:00:04.869766   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869766   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869767 
00:00:04.869767 [/Devices/ahci/0/Config/] (level 4)
00:00:04.869768   Bootable  <integer> = 0x0000000000000001 (1)
00:00:04.869769   PortCount <integer> = 0x0000000000000001 (1)
00:00:04.869770 
00:00:04.869770 [/Devices/ahci/0/Config/Port0/] (level 5)
00:00:04.869771   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:04.869772 
00:00:04.869772 [/Devices/ahci/0/LUN#0/] (level 4)
00:00:04.869773   Driver <string>  = ""VD"" (cb=3)
00:00:04.869774 
00:00:04.869774 [/Devices/ahci/0/LUN#0/Config/] (level 5)
00:00:04.869776   BlockCache <integer> = 0x0000000000000001 (1)
00:00:04.869777   Format     <string>  = ""VDI"" (cb=4)
00:00:04.869778   Mountable  <integer> = 0x0000000000000000 (0)
00:00:04.869778   Path       <string>  = ""E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi"" (cb=43)
00:00:04.869779   Type       <string>  = ""HardDisk"" (cb=9)
00:00:04.869780   UseNewIo   <integer> = 0x0000000000000001 (1)
00:00:04.869781 
00:00:04.869781 [/Devices/ahci/0/LUN#0/Config/Plugins/] (level 6)
00:00:04.869782 
00:00:04.869783 [/Devices/ahci/0/LUN#0/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:04.869784   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:04.869785 
00:00:04.869785 [/Devices/ahci/0/LUN#0/Config/VDConfig/] (level 6)
00:00:04.869787   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:04.869787 
00:00:04.869788 [/Devices/ahci/0/LUN#999/] (level 4)
00:00:04.869789   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869790 
00:00:04.869790 [/Devices/ahci/0/LUN#999/Config/] (level 5)
00:00:04.869791   DeviceInstance        <string>  = ""ahci/0"" (cb=7)
00:00:04.869792   First                 <integer> = 0x0000000000000000 (0)
00:00:04.869793   Last                  <integer> = 0x0000000000000000 (0)
00:00:04.869794   pConsole              <integer> = 0x0000000003eeddd0 (65 986 000)
00:00:04.869795   papLeds               <integer> = 0x0000000003eee5d0 (65 988 048)
00:00:04.869796   pmapMediumAttachments <integer> = 0x0000000003eef1e8 (65 991 144)
00:00:04.869797 
00:00:04.869797 [/Devices/apic/] (level 2)
00:00:04.869798 
00:00:04.869799 [/Devices/apic/0/] (level 3)
00:00:04.869800   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869800 
00:00:04.869801 [/Devices/apic/0/Config/] (level 4)
00:00:04.869802   IOAPIC  <integer> = 0x0000000000000001 (1)
00:00:04.869803   Mode    <integer> = 0x0000000000000003 (3)
00:00:04.869803   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:04.869804 
00:00:04.869804 [/Devices/e1000/] (level 2)
00:00:04.869805 
00:00:04.869805 [/Devices/e1000/0/] (level 3)
00:00:04.869806   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869807   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:04.869808   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869808   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869809 
00:00:04.869809 [/Devices/e1000/0/Config/] (level 4)
00:00:04.869810   AdapterType    <integer> = 0x0000000000000000 (0)
00:00:04.869811   CableConnected <integer> = 0x0000000000000001 (1)
00:00:04.869812   LineSpeed      <integer> = 0x0000000000000000 (0)
00:00:04.869813   MAC            <bytes>   = ""08 00 27 79 fa 01"" (cb=6)
00:00:04.869814 
00:00:04.869814 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:04.869815   Driver <string>  = ""NAT"" (cb=4)
00:00:04.869816 
00:00:04.869816 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:04.869818   AliasMode       <integer> = 0x0000000000000000 (0)
00:00:04.869819   BootFile        <string>  = ""Kali.pxe"" (cb=9)
00:00:04.869819   DNSProxy        <integer> = 0x0000000000000000 (0)
00:00:04.869820   Network         <string>  = ""10.0.2.0/24"" (cb=12)
00:00:04.869821   PassDomain      <integer> = 0x0000000000000001 (1)
00:00:04.869822   TFTPPrefix      <string>  = ""C:\Users\Home\.VirtualBox\TFTP"" (cb=31)
00:00:04.869823   UseHostResolver <integer> = 0x0000000000000000 (0)
00:00:04.869823 
00:00:04.869823 [/Devices/e1000/0/LUN#999/] (level 4)
00:00:04.869825   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869825 
00:00:04.869826 [/Devices/e1000/0/LUN#999/Config/] (level 5)
00:00:04.869827   First   <integer> = 0x0000000000000000 (0)
00:00:04.869828   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869828   papLeds <integer> = 0x0000000003eef0a8 (65 990 824)
00:00:04.869829 
00:00:04.869829 [/Devices/i8254/] (level 2)
00:00:04.869830 
00:00:04.869831 [/Devices/i8254/0/] (level 3)
00:00:04.869832 
00:00:04.869832 [/Devices/i8254/0/Config/] (level 4)
00:00:04.869833 
00:00:04.869833 [/Devices/i8259/] (level 2)
00:00:04.869834 
00:00:04.869834 [/Devices/i8259/0/] (level 3)
00:00:04.869835   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869836 
00:00:04.869836 [/Devices/i8259/0/Config/] (level 4)
00:00:04.869837 
00:00:04.869837 [/Devices/ichac97/] (level 2)
00:00:04.869838 
00:00:04.869838 [/Devices/ichac97/0/] (level 3)
00:00:04.869839   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869840   PCIDeviceNo   <integer> = 0x0000000000000005 (5)
00:00:04.869841   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869841   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869842 
00:00:04.869842 [/Devices/ichac97/0/AudioConfig/] (level 4)
00:00:04.869843 
00:00:04.869844 [/Devices/ichac97/0/Config/] (level 4)
00:00:04.869845   Codec        <string>  = ""AD1980"" (cb=7)
00:00:04.869846   DebugEnabled <integer> = 0x0000000000000000 (0)
00:00:04.869846 
00:00:04.869847 [/Devices/ichac97/0/LUN#0/] (level 4)
00:00:04.869848   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869848 
00:00:04.869849 [/Devices/ichac97/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.869850   Driver <string>  = ""HostAudioWas"" (cb=13)
00:00:04.869851 
00:00:04.869851 [/Devices/ichac97/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.869852   VmName <string>  = ""Kali"" (cb=5)
00:00:04.869853   VmUuid <string>  = ""0ca381c6-1511-4618-a89b-2269d59b311f"" (cb=37)
00:00:04.869853 
00:00:04.869854 [/Devices/ichac97/0/LUN#0/Config/] (level 5)
00:00:04.869855   DriverName    <string>  = ""HostAudioWas"" (cb=13)
00:00:04.869856   InputEnabled  <integer> = 0x0000000000000000 (0)
00:00:04.869857   OutputEnabled <integer> = 0x0000000000000001 (1)
00:00:04.869857 
00:00:04.869857 [/Devices/ichac97/0/LUN#1/] (level 4)
00:00:04.869859   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869859 
00:00:04.869860 [/Devices/ichac97/0/LUN#2/] (level 4)
00:00:04.869861   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869861 
00:00:04.869861 [/Devices/ioapic/] (level 2)
00:00:04.869862 
00:00:04.869863 [/Devices/ioapic/0/] (level 3)
00:00:04.869864   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869864 
00:00:04.869864 [/Devices/ioapic/0/Config/] (level 4)
00:00:04.869865   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:04.869866 
00:00:04.869866 [/Devices/mc146818/] (level 2)
00:00:04.869867 
00:00:04.869868 [/Devices/mc146818/0/] (level 3)
00:00:04.869869 
00:00:04.869869 [/Devices/mc146818/0/Config/] (level 4)
00:00:04.869870   UseUTC <integer> = 0x0000000000000001 (1)
00:00:04.869871 
00:00:04.869871 [/Devices/parallel/] (level 2)
00:00:04.869871 
00:00:04.869872 [/Devices/pcarch/] (level 2)
00:00:04.869873 
00:00:04.869873 [/Devices/pcarch/0/] (level 3)
00:00:04.869874   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869874 
00:00:04.869875 [/Devices/pcarch/0/Config/] (level 4)
00:00:04.869876 
00:00:04.869876 [/Devices/pcbios/] (level 2)
00:00:04.869877 
00:00:04.869877 [/Devices/pcbios/0/] (level 3)
00:00:04.869878   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869879 
00:00:04.869879 [/Devices/pcbios/0/Config/] (level 4)
00:00:04.869881   APIC               <integer> = 0x0000000000000001 (1)
00:00:04.869882   BootDevice0        <string>  = ""FLOPPY"" (cb=7)
00:00:04.869883   BootDevice1        <string>  = ""DVD"" (cb=4)
00:00:04.869884   BootDevice2        <string>  = ""IDE"" (cb=4)
00:00:04.869885   BootDevice3        <string>  = ""NONE"" (cb=5)
00:00:04.869885   FloppyDevice       <string>  = ""i82078"" (cb=7)
00:00:04.869886   HardDiskDevice     <string>  = ""piix3ide"" (cb=9)
00:00:04.869887   IOAPIC             <integer> = 0x0000000000000001 (1)
00:00:04.869888   LanBootRom         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom"" (cb=100)
00:00:04.869889   McfgBase           <integer> = 0x0000000000000000 (0)
00:00:04.869890   McfgLength         <integer> = 0x0000000000000000 (0)
00:00:04.869890   NumCPUs            <integer> = 0x0000000000000002 (2)
00:00:04.869891   PXEDebug           <integer> = 0x0000000000000000 (0)
00:00:04.869892   SataHardDiskDevice <string>  = ""ahci"" (cb=5)
00:00:04.869893   SataLUN1           <integer> = 0x0000000000000000 (0)
00:00:04.869894   UUID               <bytes>   = ""c6 81 a3 0c 11 15 18 46 a8 9b 22 69 d5 9b 31 1f"" (cb=16)
00:00:04.869896   UuidLe             <integer> = 0x0000000000000001 (1)
00:00:04.869897 
00:00:04.869897 [/Devices/pcbios/0/Config/NetBoot/] (level 5)
00:00:04.869898 
00:00:04.869898 [/Devices/pcbios/0/Config/NetBoot/0/] (level 6)
00:00:04.869899   NIC           <integer> = 0x0000000000000000 (0)
00:00:04.869900   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869901   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:04.869902   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869902 
00:00:04.869902 [/Devices/pci/] (level 2)
00:00:04.869903 
00:00:04.869904 [/Devices/pci/0/] (level 3)
00:00:04.869904   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869905 
00:00:04.869905 [/Devices/pci/0/Config/] (level 4)
00:00:04.869906   IOAPIC <integer> = 0x0000000000000001 (1)
00:00:04.869907 
00:00:04.869907 [/Devices/pcibridge/] (level 2)
00:00:04.869908 
00:00:04.869909 [/Devices/pckbd/] (level 2)
00:00:04.869909 
00:00:04.869910 [/Devices/pckbd/0/] (level 3)
00:00:04.869911   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869911 
00:00:04.869912 [/Devices/pckbd/0/Config/] (level 4)
00:00:04.869913 
00:00:04.869913 [/Devices/pckbd/0/LUN#0/] (level 4)
00:00:04.869914   Driver <string>  = ""KeyboardQueue"" (cb=14)
00:00:04.869915 
00:00:04.869915 [/Devices/pckbd/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.869916   Driver <string>  = ""MainKeyboard"" (cb=13)
00:00:04.869917 
00:00:04.869917 [/Devices/pckbd/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.869918   Object <integer> = 0x0000000003e3efe0 (65 269 728)
00:00:04.869919 
00:00:04.869919 [/Devices/pckbd/0/LUN#0/Config/] (level 5)
00:00:04.869920   QueueSize <integer> = 0x0000000000000040 (64)
00:00:04.869921 
00:00:04.869921 [/Devices/pckbd/0/LUN#1/] (level 4)
00:00:04.869922   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:04.869923 
00:00:04.869923 [/Devices/pckbd/0/LUN#1/AttachedDriver/] (level 5)
00:00:04.869924   Driver <string>  = ""MainMouse"" (cb=10)
00:00:04.869925 
00:00:04.869925 [/Devices/pckbd/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:04.869927   Object <integer> = 0x0000000003ec5b30 (65 821 488)
00:00:04.869927 
00:00:04.869928 [/Devices/pckbd/0/LUN#1/Config/] (level 5)
00:00:04.869929   QueueSize <integer> = 0x0000000000000080 (128)
00:00:04.869929 
00:00:04.869930 [/Devices/pcnet/] (level 2)
00:00:04.869930 
00:00:04.869931 [/Devices/piix3ide/] (level 2)
00:00:04.869932 
00:00:04.869932 [/Devices/piix3ide/0/] (level 3)
00:00:04.869933   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869934   PCIDeviceNo   <integer> = 0x0000000000000001 (1)
00:00:04.869935   PCIFunctionNo <integer> = 0x0000000000000001 (1)
00:00:04.869936   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869936 
00:00:04.869937 [/Devices/piix3ide/0/Config/] (level 4)
00:00:04.869938   Type <string>  = ""PIIX4"" (cb=6)
00:00:04.869938 
00:00:04.869939 [/Devices/piix3ide/0/LUN#2/] (level 4)
00:00:04.869940   Driver <string>  = ""VD"" (cb=3)
00:00:04.869941 
00:00:04.869941 [/Devices/piix3ide/0/LUN#2/Config/] (level 5)
00:00:04.869943   Format    <string>  = ""RAW"" (cb=4)
00:00:04.869943   Mountable <integer> = 0x0000000000000001 (1)
00:00:04.869944   Path      <string>  = ""C:\Users\Home\Downloads\kali-linux-2022.1-installer-amd64.iso"" (cb=62)
00:00:04.869945   ReadOnly  <integer> = 0x0000000000000001 (1)
00:00:04.869945   Type      <string>  = ""DVD"" (cb=4)
00:00:04.869946 
00:00:04.869946 [/Devices/piix3ide/0/LUN#2/Config/Plugins/] (level 6)
00:00:04.869947 
00:00:04.869948 [/Devices/piix3ide/0/LUN#2/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:04.869949   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:04.869950 
00:00:04.869950 [/Devices/piix3ide/0/LUN#999/] (level 4)
00:00:04.869952   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869952 
00:00:04.869952 [/Devices/piix3ide/0/LUN#999/Config/] (level 5)
00:00:04.869954   DeviceInstance        <string>  = ""piix3ide/0"" (cb=11)
00:00:04.869955   First                 <integer> = 0x0000000000000000 (0)
00:00:04.869956   Last                  <integer> = 0x0000000000000003 (3)
00:00:04.869957   pConsole              <integer> = 0x0000000003eeddd0 (65 986 000)
00:00:04.869958   papLeds               <integer> = 0x0000000003eee5b0 (65 988 016)
00:00:04.869959   pmapMediumAttachments <integer> = 0x0000000003eef1e8 (65 991 144)
00:00:04.869960 
00:00:04.869960 [/Devices/serial/] (level 2)
00:00:04.869961 
00:00:04.869961 [/Devices/usb-ehci/] (level 2)
00:00:04.869962 
00:00:04.869962 [/Devices/usb-ehci/0/] (level 3)
00:00:04.869964   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869964   PCIDeviceNo   <integer> = 0x000000000000000b (11)
00:00:04.869965   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869966   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869967 
00:00:04.869967 [/Devices/usb-ehci/0/Config/] (level 4)
00:00:04.869968 
00:00:04.869968 [/Devices/usb-ehci/0/LUN#0/] (level 4)
00:00:04.869969   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:04.869970 
00:00:04.869970 [/Devices/usb-ehci/0/LUN#0/Config/] (level 5)
00:00:04.869971 
00:00:04.869971 [/Devices/usb-ehci/0/LUN#999/] (level 4)
00:00:04.869972   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869973 
00:00:04.869973 [/Devices/usb-ehci/0/LUN#999/Config/] (level 5)
00:00:04.869974   First   <integer> = 0x0000000000000000 (0)
00:00:04.869975   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869976   papLeds <integer> = 0x0000000003eef1d8 (65 991 128)
00:00:04.869977 
00:00:04.869977 [/Devices/usb-ohci/] (level 2)
00:00:04.869978 
00:00:04.869978 [/Devices/usb-ohci/0/] (level 3)
00:00:04.869979   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869980   PCIDeviceNo   <integer> = 0x0000000000000006 (6)
00:00:04.869980   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869981   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869982 
00:00:04.869982 [/Devices/usb-ohci/0/Config/] (level 4)
00:00:04.869983 
00:00:04.869983 [/Devices/usb-ohci/0/LUN#0/] (level 4)
00:00:04.869984   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:04.869985 
00:00:04.869985 [/Devices/usb-ohci/0/LUN#0/Config/] (level 5)
00:00:04.869986 
00:00:04.869986 [/Devices/usb-ohci/0/LUN#999/] (level 4)
00:00:04.869987   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869988 
00:00:04.869988 [/Devices/usb-ohci/0/LUN#999/Config/] (level 5)
00:00:04.869989   First   <integer> = 0x0000000000000000 (0)
00:00:04.869990   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869990   papLeds <integer> = 0x0000000003eef1d0 (65 991 120)
00:00:04.869991 
00:00:04.869991 [/Devices/vga/] (level 2)
00:00:04.869992 
00:00:04.869993 [/Devices/vga/0/] (level 3)
00:00:04.869994   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869995   PCIDeviceNo   <integer> = 0x0000000000000002 (2)
00:00:04.869995   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869996   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869997 
00:00:04.869997 [/Devices/vga/0/Config/] (level 4)
00:00:04.869999   3DEnabled          <integer> = 0x0000000000000001 (1)
00:00:04.870000   CustomVideoModes   <integer> = 0x0000000000000000 (0)
00:00:04.870001   FadeIn             <integer> = 0x0000000000000001 (1)
00:00:04.870001   FadeOut            <integer> = 0x0000000000000001 (1)
00:00:04.870002   HeightReduction    <integer> = 0x0000000000000000 (0)
00:00:04.870003   LogoFile           <string>  = """" (cb=1)
00:00:04.870004   LogoTime           <integer> = 0x0000000000000000 (0)
00:00:04.870005   MonitorCount       <integer> = 0x0000000000000002 (2)
00:00:04.870005   ShowBootMenu       <integer> = 0x0000000000000002 (2)
00:00:04.870006   VMSVGA3dEnabled    <integer> = 0x0000000000000001 (1)
00:00:04.870007   VMSVGAEnabled      <integer> = 0x0000000000000001 (1)
00:00:04.870007   VMSVGAPciBarLayout <integer> = 0x0000000000000001 (1)
00:00:04.870008   VMSVGAPciId        <integer> = 0x0000000000000001 (1)
00:00:04.870009   VRamSize           <integer> = 0x0000000008000000 (134 217 728, 128 MB)
00:00:04.870010 
00:00:04.870011 [/Devices/vga/0/LUN#0/] (level 4)
00:00:04.870012   Driver <string>  = ""MainDisplay"" (cb=12)
00:00:04.870012 
00:00:04.870013 [/Devices/vga/0/LUN#0/Config/] (level 5)
00:00:04.870014   Object <integer> = 0x0000000003ea2a80 (65 677 952)
00:00:04.870015 
00:00:04.870015 [/Devices/vga/0/LUN#999/] (level 4)
00:00:04.870016   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.870016 
00:00:04.870017 [/Devices/vga/0/LUN#999/Config/] (level 5)
00:00:04.870018   First   <integer> = 0x0000000000000000 (0)
00:00:04.870019   Last    <integer> = 0x0000000000000000 (0)
00:00:04.870019   papLeds <integer> = 0x0000000003eef1e0 (65 991 136)
00:00:04.870020 
00:00:04.870021 [/Devices/virtio-net/] (level 2)
00:00:04.870022 
00:00:04.870022 [/EM/] (level 1)
00:00:04.870023   TripleFaultReset <integer> = 0x0000000000000000 (0)
00:00:04.870023 
00:00:04.870024 [/GIM/] (level 1)
00:00:04.870024   Provider <string>  = ""KVM"" (cb=4)
00:00:04.870025 
00:00:04.870025 [/HM/] (level 1)
00:00:04.870027   64bitEnabled            <integer> = 0x0000000000000001 (1)
00:00:04.870028   EnableLargePages        <integer> = 0x0000000000000001 (1)
00:00:04.870063   EnableNestedPaging      <integer> = 0x0000000000000001 (1)
00:00:04.870064   EnableUX                <integer> = 0x0000000000000001 (1)
00:00:04.870065   EnableVPID              <integer> = 0x0000000000000001 (1)
00:00:04.870065   Exclusive               <integer> = 0x0000000000000000 (0)
00:00:04.870066   HMForced                <integer> = 0x0000000000000001 (1)
00:00:04.870067   IBPBOnVMEntry           <integer> = 0x0000000000000000 (0)
00:00:04.870068   IBPBOnVMExit            <integer> = 0x0000000000000000 (0)
00:00:04.870069   L1DFlushOnSched         <integer> = 0x0000000000000001 (1)
00:00:04.870070   L1DFlushOnVMEntry       <integer> = 0x0000000000000000 (0)
00:00:04.870070   LovelyMesaDrvWorkaround <integer> = 0x0000000000000001 (1)
00:00:04.870071   MDSClearOnSched         <integer> = 0x0000000000000001 (1)
00:00:04.870072   MDSClearOnVMEntry       <integer> = 0x0000000000000000 (0)
00:00:04.870073   SpecCtrlByHost          <integer> = 0x0000000000000000 (0)
00:00:04.870074   UseNEMInstead           <integer> = 0x0000000000000000 (0)
00:00:04.870074 
00:00:04.870075 [/MM/] (level 1)
00:00:04.870075   CanUseLargerHeap <integer> = 0x0000000000000000 (0)
00:00:04.870076 
00:00:04.870076 [/NEM/] (level 1)
00:00:04.870077   Allow64BitGuests        <integer> = 0x0000000000000001 (1)
00:00:04.870078   LovelyMesaDrvWorkaround <integer> = 0x0000000000000001 (1)
00:00:04.870079 
00:00:04.870079 [/PDM/] (level 1)
00:00:04.870080 
00:00:04.870080 [/PDM/AsyncCompletion/] (level 2)
00:00:04.870081 
00:00:04.870081 [/PDM/AsyncCompletion/File/] (level 3)
00:00:04.870082 
00:00:04.870082 [/PDM/AsyncCompletion/File/BwGroups/] (level 4)
00:00:04.870084 
00:00:04.870084 [/PDM/BlkCache/] (level 2)
00:00:04.870085   CacheSize <integer> = 0x0000000000500000 (5 242 880, 5 MB)
00:00:04.870086 
00:00:04.870086 [/PDM/Devices/] (level 2)
00:00:04.870087 
00:00:04.870087 [/PDM/Devices/VBoxEhci/] (level 3)
00:00:04.870089   Path         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR3.DLL"" (cb=111)
00:00:04.870090   R0SearchPath <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:04.870091 
00:00:04.870091 [/PDM/Devices/VBoxNvme/] (level 3)
00:00:04.870095   Path         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxNvmeR3.DLL"" (cb=111)
00:00:04.870097   R0SearchPath <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:04.870098 
00:00:04.870098 [/PDM/Drivers/] (level 2)
00:00:04.870099 
00:00:04.870099 [/PDM/Drivers/DrvHostWebcam/] (level 3)
00:00:04.870100   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL"" (cb=115)
00:00:04.870101 
00:00:04.870101 [/PDM/Drivers/VBoxC/] (level 3)
00:00:04.870102   Path <string>  = ""VBoxC"" (cb=6)
00:00:04.870102 
00:00:04.870102 [/PDM/NetworkShaper/] (level 2)
00:00:04.870103 
00:00:04.870103 [/PDM/NetworkShaper/BwGroups/] (level 3)
00:00:04.870104 
00:00:04.870105 [/PDM/USB/] (level 2)
00:00:04.870105 
00:00:04.870106 [/PDM/USB/VBoxUsbCardReader/] (level 3)
00:00:04.870106   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbCardReaderR3.DLL"" (cb=120)
00:00:04.870107 
00:00:04.870107 [/PDM/USB/VBoxUsbWebcam/] (level 3)
00:00:04.870108   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbWebcamR3.DLL"" (cb=116)
00:00:04.870109 
00:00:04.870109 [/TM/] (level 1)
00:00:04.870110   UTCOffset <integer> = 0x0000000000000000 (0)
00:00:04.870111 
00:00:04.870111 [/USB/] (level 1)
00:00:04.870112 
00:00:04.870112 [/USB/HidMouse/] (level 2)
00:00:04.870113 
00:00:04.870113 [/USB/HidMouse/0/] (level 3)
00:00:04.870114 
00:00:04.870114 [/USB/HidMouse/0/Config/] (level 4)
00:00:04.870115   Mode <string>  = ""absolute"" (cb=9)
00:00:04.870115 
00:00:04.870116 [/USB/HidMouse/0/LUN#0/] (level 4)
00:00:04.870117   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:04.870117 
00:00:04.870118 [/USB/HidMouse/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.870119   Driver <string>  = ""MainMouse"" (cb=10)
00:00:04.870120 
00:00:04.870120 [/USB/HidMouse/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.870121   Object <integer> = 0x0000000003ec5b30 (65 821 488)
00:00:04.870122 
00:00:04.870122 [/USB/HidMouse/0/LUN#0/Config/] (level 5)
00:00:04.870123   QueueSize <integer> = 0x0000000000000080 (128)
00:00:04.870124 
00:00:04.870124 [/USB/USBProxy/] (level 2)
00:00:04.870125 
00:00:04.870125 [/USB/USBProxy/GlobalConfig/] (level 3)
00:00:04.870126 
00:00:04.870127 ********************* End of CFGM dump **********************
00:00:04.870379 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:04.870466 MM: cbHyperHeap=0x240000 (2359296)
00:00:04.872611 CPUM: fXStateHostMask=0x0; initial: 0x0; host XCR0=0x0
00:00:04.873840 CPUM: Matched host CPU INTEL 0x6/0x25/0x5 Intel_Core7_Westmere with CPU DB entry 'Intel Core i7-3960X' (INTEL 0x6/0x2d/0x6 Intel_Core7_SandyBridge)
00:00:04.874032 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:04.874058 CPUM: Disabled PCID without FSGSBASE to workaround buggy guests
00:00:04.874066 CPUM: Microcode revision 0x00000004
00:00:04.874402 PGM: Host paging mode: AMD64+PGE+NX
00:00:04.874442 PGM: PGMPool: cMaxPages=2304 (u64MaxPages=2084)
00:00:04.874462 PGM: pgmR3PoolInit: cMaxPages=0x900 cMaxUsers=0x1200 cMaxPhysExts=0x1200 fCacheEnable=true 
00:00:04.885544 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=100 u32UpdateIntervalNS=10000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x11 cCpus=4
00:00:04.885592 TM: GIP - u64CpuHz=2 793 001 012 (0xa679d034)  SUPGetCpuHzFromGip => 2 793 001 012
00:00:04.885598 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2793108784(*) cErrors=0
00:00:04.885603 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2793001012(*) cErrors=0
00:00:04.885607 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2793843206(*) cErrors=0
00:00:04.885611 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x5 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2793826954(*) cErrors=0
00:00:04.885714 TM: cTSCTicksPerSecond=2 793 001 012 (0xa679d034) enmTSCMode=1 (VirtTscEmulated)
00:00:04.885732 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:04.886591 EMR3Init: fIemExecutesAll=false fGuruOnTripleFault=true 
00:00:04.886887 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_Westmere
00:00:04.887105 GIM: Using provider 'KVM' (Implementation version: 0)
00:00:04.887136 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:04.887272 AIOMgr: Default manager type is 'Async'
00:00:04.887280 AIOMgr: Default file backend is 'NonBuffered'
00:00:04.887515 BlkCache: Cache successfully initialized. Cache size is 5242880 bytes
00:00:04.887526 BlkCache: Cache commit interval is 10000 ms
00:00:04.887532 BlkCache: Cache commit threshold is 2621440 bytes
00:00:05.836511 PcBios: [SMP] BIOS with 2 CPUs
00:00:05.836574 PcBios: Using the 386+ BIOS image.
00:00:05.836909 PcBios: MPS table at 000e1300
00:00:05.838457 PcBios: Using LAN ROM 'E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom' with a size of 0xc000 bytes
00:00:05.838565 PcBios: fCheckShutdownStatusForSoftReset=true   fClearShutdownStatusOnHardReset=true 
00:00:05.888309 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:05.888329 SUP: seg #1: R X 0x00001000 LB 0x0001e000
00:00:05.888333 SUP: seg #2: R   0x0001f000 LB 0x0000c000
00:00:05.888336 SUP: seg #3: RW  0x0002b000 LB 0x00001000
00:00:05.888339 SUP: seg #4: R   0x0002c000 LB 0x00002000
00:00:05.888342 SUP: seg #5: RW  0x0002e000 LB 0x00001000
00:00:05.888345 SUP: seg #6: R   0x0002f000 LB 0x00001000
00:00:05.888348 SUP: seg #7: RWX 0x00030000 LB 0x00001000
00:00:05.888351 SUP: seg #8: R   0x00031000 LB 0x00002000
00:00:05.888453 SUP: Loaded VBoxDDR0.r0 (E:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:05.888463 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xXXXXXXXXXXXXXXXX
00:00:05.888997 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:05.889007 CPUM: SetGuestCpuIdFeature: Enabled x2APIC
00:00:05.889381 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:05.889500 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:05.889796 VMMDev: cbDefaultBudget: 130 922 048 (7cdb640)
00:00:05.912902 Shared Folders service loaded
00:00:05.931191 Guest Control service loaded
00:00:05.985616 VGA: Using the 386+ BIOS image.
00:00:05.989092 VD: VDInit finished with VINF_SUCCESS
00:00:06.017422 DrvVD: Flushes will be ignored
00:00:06.017450 DrvVD: Async flushes will be passed to the disk
00:00:06.019989 AIOMgr: Endpoint for file 'E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi' (flags 000c0723) created successfully
00:00:06.064638 VD: Opening the disk took 45257236 ns
00:00:06.064829 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 218103808
00:00:06.065215 AHCI#0: Reset the HBA
00:00:06.065226 VD#0: Cancelling all active requests
00:00:06.066942 PIIX3 ATA: LUN#0: no unit
00:00:06.066967 PIIX3 ATA: LUN#1: no unit
00:00:06.067102 DrvVD: Flushes will be ignored
00:00:06.067112 DrvVD: Async flushes will be passed to the disk
00:00:06.067349 VD: Opening the disk took 223712 ns
00:00:06.067388 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 1462072, passthrough disabled
00:00:06.067444 PIIX3 ATA: LUN#3: no unit
00:00:06.067465 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:06.067484 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:06.067610 E1000#0: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled RC=disabled
00:00:06.073801 NAT: Guest address guess set to 10.0.2.15 by initialization
00:00:06.123047 NAT: DNS#0: 10.154.1.1
00:00:06.124538 AC97: Using codec 'AD1980'
00:00:06.218937 Audio: Found 5 devices for driver 'WasAPI'
00:00:06.218954 Audio: Device 'Speakers (Conexant CX20671 SmartAudio HD)':
00:00:06.218955 Audio:   ID              = {0.0.0.00000000}.{5aee2f46-7a75-40b4-966e-d7a1df957f8a}
00:00:06.218956 Audio:   Usage           = output
00:00:06.218956 Audio:   Flags           = DEFAULT_OUT
00:00:06.218957 Audio:   Input channels  = 0
00:00:06.218957 Audio:   Output channels = 2
00:00:06.218960 Audio: Device 'Speakers (Conexant CX20671 SmartAudio HD)':
00:00:06.218961 Audio:   ID              = {0.0.0.00000000}.{5aee2f46-7a75-40b4-966e-d7a1df957f8a}
00:00:06.218961 Audio:   Usage           = output
00:00:06.218962 Audio:   Flags           = NONE
00:00:06.218962 Audio:   Input channels  = 0
00:00:06.218962 Audio:   Output channels = 2
00:00:06.218965 Audio: Device 'Microphone (Conexant CX20671 SmartAudio HD)':
00:00:06.218965 Audio:   ID              = {0.0.1.00000000}.{032a30e1-a128-4e17-8f6b-da2a069a099e}
00:00:06.218966 Audio:   Usage           = input
00:00:06.218966 Audio:   Flags           = DEFAULT_IN
00:00:06.218967 Audio:   Input channels  = 2
00:00:06.218967 Audio:   Output channels = 0
00:00:06.218969 Audio: Device 'Microphone (Conexant CX20671 SmartAudio HD)':
00:00:06.218970 Audio:   ID              = {0.0.1.00000000}.{032a30e1-a128-4e17-8f6b-da2a069a099e}
00:00:06.218970 Audio:   Usage           = input
00:00:06.218970 Audio:   Flags           = NONE
00:00:06.218971 Audio:   Input channels  = 2
00:00:06.218971 Audio:   Output channels = 0
00:00:06.218974 Audio: Device 'Stereo Mix (Conexant CX20671 SmartAudio HD)':
00:00:06.218974 Audio:   ID              = {0.0.1.00000000}.{51d473a9-ba14-4ba3-a007-f776ebc945b9}
00:00:06.218974 Audio:   Usage           = input
00:00:06.218975 Audio:   Flags           = NONE
00:00:06.218975 Audio:   Input channels  = 2
00:00:06.218975 Audio:   Output channels = 0
00:00:06.219358 AC97: Reset
00:00:06.219385 AC97: Mixer reset (EAID=0x809, EACS=0x9)
00:00:06.219390 AC97: Record select to left=mic, right=mic
00:00:06.260679 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:06.260697 SUP: seg #1: R X 0x00001000 LB 0x00002000
00:00:06.260701 SUP: seg #2: R   0x00003000 LB 0x00001000
00:00:06.260704 SUP: seg #3: RW  0x00004000 LB 0x00001000
00:00:06.260707 SUP: seg #4: R   0x00005000 LB 0x00002000
00:00:06.260710 SUP: seg #5: RWX 0x00007000 LB 0x00001000
00:00:06.260713 SUP: seg #6: R   0x00008000 LB 0x00002000
00:00:06.260743 SUP: Loaded VBoxEhciR0.r0 (E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:06.260752 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR0.r0=0xXXXXXXXXXXXXXXXX
00:00:06.262034 VUSB: Attached 'HidMouse' to port 1 on RootHub#1 (FullSpeed)
00:00:06.262069 PGM: The CPU physical address width is 36 bits
00:00:06.262136 PGM: PGMR3InitFinalize: 4 MB PSE mask 0000000fffffffff -> VINF_SUCCESS
00:00:06.262300 TM: TMR3InitFinalize: fTSCModeSwitchAllowed=true 
00:00:06.262494 VMM: Thread-context hooks unavailable
00:00:06.262503 VMM: Warning! RTThreadPreemptIsPending() cannot be trusted!  Need to update kernel info?
00:00:06.262505 VMM: Kernel preemption is possible
00:00:06.264747 HM: fWorldSwitcher=0x0 (fIbpbOnVmExit=false fIbpbOnVmEntry=false fL1dFlushOnVmEntry=false); fL1dFlushOnSched=false fMdsClearOnVmEntry=false
00:00:06.264759 HM: Using VT-x implementation 3.0
00:00:06.264786 HM: Max resume loops                  = 1024
00:00:06.264787 HM: Host CR4                          = 0x6f8
00:00:06.264788 HM: Host EFER                         = 0xd01
00:00:06.264789 HM: MSR_IA32_SMM_MONITOR_CTL          = 0x0
00:00:06.264789 HM: MSR_IA32_FEATURE_CONTROL          = 0x5
00:00:06.264790 HM:   LOCK
00:00:06.264790 HM:   VMXON
00:00:06.264791 HM: MSR_IA32_VMX_BASIC                = 0xda04000000000f
00:00:06.264792 HM:   VMCS id                           = 0xf
00:00:06.264792 HM:   VMCS size                         = 1024 bytes
00:00:06.264793 HM:   VMCS physical address limit       = None
00:00:06.264793 HM:   VMCS memory type                  = Write Back (WB)
00:00:06.264794 HM:   Dual-monitor treatment support    = true 
00:00:06.264794 HM:   OUTS & INS instruction-info       = true 
00:00:06.264795 HM:   Supports true-capability MSRs     = true 
00:00:06.264795 HM:   VM-entry Xcpt error-code optional = false
00:00:06.264795 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x7f00000016
00:00:06.264796 HM:   EXT_INT_EXIT
00:00:06.264796 HM:   NMI_EXIT
00:00:06.264797 HM:   VIRTUAL_NMI
00:00:06.264797 HM:   PREEMPT_TIMER
00:00:06.264797 HM:   POSTED_INT (must be cleared)
00:00:06.264813 HM: MSR_IA32_VMX_PROCBASED_CTLS       = 0xfff9fffe0401e172
00:00:06.264814 HM:   INT_WINDOW_EXIT
00:00:06.264814 HM:   USE_TSC_OFFSETTING
00:00:06.264814 HM:   HLT_EXIT
00:00:06.264814 HM:   INVLPG_EXIT
00:00:06.264815 HM:   MWAIT_EXIT
00:00:06.264815 HM:   RDPMC_EXIT
00:00:06.264815 HM:   RDTSC_EXIT
00:00:06.264816 HM:   CR3_LOAD_EXIT (must be set)
00:00:06.264816 HM:   CR3_STORE_EXIT (must be set)
00:00:06.264816 HM:   CR8_LOAD_EXIT
00:00:06.264816 HM:   CR8_STORE_EXIT
00:00:06.264817 HM:   USE_TPR_SHADOW
00:00:06.264817 HM:   NMI_WINDOW_EXIT
00:00:06.264817 HM:   MOV_DR_EXIT
00:00:06.264818 HM:   UNCOND_IO_EXIT
00:00:06.264818 HM:   USE_IO_BITMAPS
00:00:06.264818 HM:   MONITOR_TRAP_FLAG
00:00:06.264819 HM:   USE_MSR_BITMAPS
00:00:06.264819 HM:   MONITOR_EXIT
00:00:06.264819 HM:   PAUSE_EXIT
00:00:06.264819 HM:   USE_SECONDARY_CTLS
00:00:06.264849 HM: MSR_IA32_VMX_PROCBASED_CTLS2      = 0xff00000000
00:00:06.264850 HM:   VIRT_APIC_ACCESS
00:00:06.264850 HM:   EPT
00:00:06.264850 HM:   DESC_TABLE_EXIT
00:00:06.264851 HM:   RDTSCP
00:00:06.264851 HM:   VIRT_X2APIC_MODE
00:00:06.264851 HM:   VPID
00:00:06.264851 HM:   WBINVD_EXIT
00:00:06.264852 HM:   UNRESTRICTED_GUEST
00:00:06.264852 HM:   APIC_REG_VIRT (must be cleared)
00:00:06.264852 HM:   VIRT_INT_DELIVERY (must be cleared)
00:00:06.264853 HM:   PAUSE_LOOP_EXIT (must be cleared)
00:00:06.264853 HM:   RDRAND_EXIT (must be cleared)
00:00:06.264853 HM:   INVPCID (must be cleared)
00:00:06.264854 HM:   VMFUNC (must be cleared)
00:00:06.264854 HM:   VMCS_SHADOWING (must be cleared)
00:00:06.264854 HM:   ENCLS_EXIT (must be cleared)
00:00:06.264855 HM:   RDSEED_EXIT (must be cleared)
00:00:06.264855 HM:   PML (must be cleared)
00:00:06.264855 HM:   EPT_VE (must be cleared)
00:00:06.264856 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264856 HM:   XSAVES_XRSTORS (must be cleared)
00:00:06.264856 HM:   MODE_BASED_EPT_PERM (must be cleared)
00:00:06.264857 HM:   SPPTP_EPT (must be cleared)
00:00:06.264857 HM:   PT_EPT (must be cleared)
00:00:06.264857 HM:   TSC_SCALING (must be cleared)
00:00:06.264858 HM:   USER_WAIT_PAUSE (must be cleared)
00:00:06.264858 HM:   ENCLV_EXIT (must be cleared)
00:00:06.264858 HM: MSR_IA32_VMX_ENTRY_CTLS           = 0xffff000011ff
00:00:06.264859 HM:   LOAD_DEBUG (must be set)
00:00:06.264859 HM:   IA32E_MODE_GUEST
00:00:06.264860 HM:   ENTRY_TO_SMM
00:00:06.264860 HM:   DEACTIVATE_DUAL_MON
00:00:06.264860 HM:   LOAD_PERF_MSR
00:00:06.264860 HM:   LOAD_PAT_MSR
00:00:06.264861 HM:   LOAD_EFER_MSR
00:00:06.264861 HM:   LOAD_BNDCFGS_MSR (must be cleared)
00:00:06.264861 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264862 HM:   LOAD_RTIT_CTL_MSR (must be cleared)
00:00:06.264862 HM: MSR_IA32_VMX_EXIT_CTLS            = 0x7fffff00036dff
00:00:06.264863 HM:   SAVE_DEBUG (must be set)
00:00:06.264863 HM:   HOST_ADDR_SPACE_SIZE
00:00:06.264863 HM:   LOAD_PERF_MSR
00:00:06.264864 HM:   ACK_EXT_INT
00:00:06.264864 HM:   SAVE_PAT_MSR
00:00:06.264864 HM:   LOAD_PAT_MSR
00:00:06.264865 HM:   SAVE_EFER_MSR
00:00:06.264865 HM:   LOAD_EFER_MSR
00:00:06.264865 HM:   SAVE_PREEMPT_TIMER
00:00:06.264880 HM:   CLEAR_BNDCFGS_MSR (must be cleared)
00:00:06.264880 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264881 HM:   CLEAR_RTIT_CTL_MSR (must be cleared)
00:00:06.264881 HM: MSR_IA32_VMX_TRUE_PINBASED_CTLS   = 0x7f00000016
00:00:06.264882 HM: MSR_IA32_VMX_TRUE_PROCBASED_CTLS  = 0xfff9fffe04006172
00:00:06.264883 HM: MSR_IA32_VMX_TRUE_ENTRY_CTLS      = 0xffff000011fb
00:00:06.264884 HM: MSR_IA32_VMX_TRUE_EXIT_CTLS       = 0x7fffff00036dfb
00:00:06.264884 HM: MSR_IA32_VMX_MISC                 = 0x401e7
00:00:06.264885 HM:   PREEMPT_TIMER_TSC                 = 0x7 - erratum detected, using 0x0 instead
00:00:06.264886 HM:   EXIT_SAVE_EFER_LMA                = true 
00:00:06.264886 HM:   ACTIVITY_STATES                   = 0x7 ( HLT SHUTDOWN SIPI_WAIT )
00:00:06.264887 HM:   INTEL_PT                          = false
00:00:06.264887 HM:   SMM_READ_SMBASE_MSR               = false
00:00:06.264887 HM:   CR3_TARGET                        = 0x4
00:00:06.264888 HM:   MAX_MSR                           = 0x0 ( 512 )
00:00:06.264888 HM:   VMXOFF_BLOCK_SMI                  = false
00:00:06.264889 HM:   VMWRITE_ALL                       = false
00:00:06.264889 HM:   ENTRY_INJECT_SOFT_INT             = 0x0
00:00:06.264890 HM:   MSEG_ID                           = 0x0
00:00:06.264890 HM: MSR_IA32_VMX_VMCS_ENUM            = 0x2a
00:00:06.264891 HM:   HIGHEST_IDX                       = 0x15
00:00:06.264891 HM: MSR_IA32_VMX_EPT_VPID_CAP         = 0xf0106114141
00:00:06.264892 HM:   RWX_X_ONLY
00:00:06.264892 HM:   PAGE_WALK_LENGTH_4
00:00:06.264892 HM:   EMT_UC
00:00:06.264893 HM:   EMT_WB
00:00:06.264893 HM:   PDE_2M
00:00:06.264893 HM:   INVEPT
00:00:06.264893 HM:   INVEPT_SINGLE_CONTEXT
00:00:06.264894 HM:   INVEPT_ALL_CONTEXTS
00:00:06.264894 HM:   INVVPID
00:00:06.264894 HM:   INVVPID_INDIV_ADDR
00:00:06.264895 HM:   INVVPID_SINGLE_CONTEXT
00:00:06.264895 HM:   INVVPID_ALL_CONTEXTS
00:00:06.264895 HM:   INVVPID_SINGLE_CONTEXT_RETAIN_GLOBALS
00:00:06.264896 HM: MSR_IA32_VMX_CR0_FIXED0           = 0x80000021
00:00:06.264896 HM: MSR_IA32_VMX_CR0_FIXED1           = 0xffffffff
00:00:06.264897 HM: MSR_IA32_VMX_CR4_FIXED0           = 0x2000
00:00:06.264897 HM: MSR_IA32_VMX_CR4_FIXED1           = 0x267ff
00:00:06.264898 HM: APIC-access page physaddr         = 0x000000023417e000
00:00:06.264899 HM: VCPU  0: MSR bitmap physaddr      = 0x0000000233eb9000
00:00:06.264900 HM: VCPU  0: VMCS physaddr            = 0x0000000233eb6000
00:00:06.264901 HM: VCPU  1: MSR bitmap physaddr      = 0x0000000233ebd000
00:00:06.264901 HM: VCPU  1: VMCS physaddr            = 0x0000000233eba000
00:00:06.264902 HM: Guest support: 32-bit and 64-bit
00:00:06.264910 HM: Supports VMCS EFER fields         = true 
00:00:06.264911 HM: Enabled VMX
00:00:06.264915 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:06.264916 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:06.264917 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:06.264917 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:06.264918 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:06.264918 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:06.264919 HM: Enabled nested paging
00:00:06.264919 HM:   EPT flush type                  = Single context
00:00:06.264919 HM: Enabled unrestricted guest execution
00:00:06.264920 HM: Enabled large page support
00:00:06.264920 HM: Enabled VPID
00:00:06.264921 HM:   VPID flush type                 = Single context
00:00:06.264921 HM: Enabled VMX-preemption timer (cPreemptTimerShift=0)
00:00:06.264922 HM: VT-x/AMD-V init method: Local
00:00:06.264923 EM: Exit history optimizations: enabled=true  enabled-r0=true  enabled-r0-no-preemption=false
00:00:06.267403 AIOMgr: Async flushes not supported
00:00:06.267422 PcBios: SATA LUN#0 LCHS=1024/255/63
00:00:06.267440 APIC: fPostedIntrsEnabled=false fVirtApicRegsEnabled=false fSupportsTscDeadline=false
00:00:06.267445 TMR3UtcNow: nsNow=1 648 098 653 521 591 300 nsPrev=0 -> cNsDelta=1 648 098 653 521 591 300 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 648 098 653 521 591 300)
00:00:06.267455 VMM: fUsePeriodicPreemptionTimers=false
00:00:06.267462 CPUM: Logical host processors: 4 present, 4 max, 4 online, online mask: 000000000000000f
00:00:06.267466 CPUM: Physical host cores: 2
00:00:06.267467 ************************* CPUID dump ************************
00:00:06.267504          Raw Standard CPUID Leaves
00:00:06.267504      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267506 Gst: 00000000/0000  0000000b 756e6547 6c65746e 49656e69
00:00:06.267508 Hst:                0000000b 756e6547 6c65746e 49656e69
00:00:06.267509 Gst: 00000001/0000  00020655 00020800 82b82203 178bfbff
00:00:06.267510 Hst:                00020655 00100800 029ae3ff bfebfbff
00:00:06.267511 Gst: 00000002/0000  55035a01 00f0b2e3 00000000 09ca212c
00:00:06.267512 Hst:                55035a01 00f0b2e3 00000000 09ca212c
00:00:06.267513 Gst: 00000003/0000  00000000 00000000 00000000 00000000
00:00:06.267513 Hst:                00000000 00000000 00000000 00000000
00:00:06.267514 Gst: 00000004/0000  04000121 01c0003f 0000003f 00000000
00:00:06.267515 Hst:                1c004121 01c0003f 0000003f 00000000
00:00:06.267516 Gst: 00000004/0001  04000122 00c0003f 0000007f 00000000
00:00:06.267517 Hst:                1c004122 00c0003f 0000007f 00000000
00:00:06.267517 Gst: 00000004/0002  04000143 01c0003f 000001ff 00000000
00:00:06.267518 Hst:                1c004143 01c0003f 000001ff 00000000
00:00:06.267519 Gst: 00000004/0003  04000163 03c0003f 00000fff 00000002
00:00:06.267520 Hst:                1c03c163 03c0003f 00000fff 00000002
00:00:06.267521 Gst: 00000004/0004  04000000 00000000 00000000 00000000
00:00:06.267521 Hst:                00000000 00000000 00000000 00000000
00:00:06.267522 Gst: 00000005/0000  00000000 00000000 00000000 00000000
00:00:06.267523 Hst:                00000040 00000040 00000003 00001120
00:00:06.267524 Gst: 00000006/0000  00000000 00000000 00000000 00000000
00:00:06.267524 Hst:                00000007 00000002 00000001 00000000
00:00:06.267525 Gst: 00000007/0000  00000000 00000000 00000000 00000000
00:00:06.267526 Hst:                00000000 00000000 00000000 00000000
00:00:06.267526 Gst: 00000008/0000  00000000 00000000 00000000 00000000
00:00:06.267527 Hst:                00000000 00000000 00000000 00000000
00:00:06.267528 Gst: 00000009/0000  00000000 00000000 00000000 00000000
00:00:06.267528 Hst:                00000000 00000000 00000000 00000000
00:00:06.267529 Gst: 0000000a/0000  00000000 00000000 00000000 00000000
00:00:06.267530 Hst:                07300403 00000004 00000000 00000603
00:00:06.267531 Gst: 0000000b/0000  00000000 00000001 00000100 00000000
00:00:06.267531 Hst:                00000001 00000002 00000100 00000000
00:00:06.267532 Gst: 0000000b/0001  00000001 00000002 00000201 00000000
00:00:06.267533 Hst:                00000004 00000004 00000201 00000000
00:00:06.267534 Gst: 0000000b/0002  00000000 00000000 00000002 00000000
00:00:06.267534 Hst:                00000000 00000000 00000002 00000000
00:00:06.267535                                Name: GenuineIntel
00:00:06.267536                            Supports: 0x00000000-0x0000000b
00:00:06.267552                              Family:  6 	Extended: 0 	Effective: 6
00:00:06.267553                               Model:  5 	Extended: 2 	Effective: 37
00:00:06.267554                            Stepping: 5
00:00:06.267555                                Type: 0 (primary)
00:00:06.267556                             APIC ID: 0x00
00:00:06.267557                        Logical CPUs: 2
00:00:06.267557                        CLFLUSH Size: 8
00:00:06.267558                            Brand ID: 0x00
00:00:06.267559 Features
00:00:06.267559   Mnemonic - Description                                  = guest (host)
00:00:06.267576   FPU - x87 FPU on Chip                                   = 1 (1)
00:00:06.267578   VME - Virtual 8086 Mode Enhancements                    = 1 (1)
00:00:06.267579   DE - Debugging extensions                               = 1 (1)
00:00:06.267580   PSE - Page Size Extension                               = 1 (1)
00:00:06.267581   TSC - Time Stamp Counter                                = 1 (1)
00:00:06.267582   MSR - Model Specific Registers                          = 1 (1)
00:00:06.267583   PAE - Physical Address Extension                        = 1 (1)
00:00:06.267584   MCE - Machine Check Exception                           = 1 (1)
00:00:06.267585   CX8 - CMPXCHG8B instruction                             = 1 (1)
00:00:06.267586   APIC - APIC On-Chip                                     = 1 (1)
00:00:06.267587   SEP - SYSENTER and SYSEXIT Present                      = 1 (1)
00:00:06.267588   MTRR - Memory Type Range Registers                      = 1 (1)
00:00:06.267589   PGE - PTE Global Bit                                    = 1 (1)
00:00:06.267590   MCA - Machine Check Architecture                        = 1 (1)
00:00:06.267591   CMOV - Conditional Move instructions                    = 1 (1)
00:00:06.267592   PAT - Page Attribute Table                              = 1 (1)
00:00:06.267593   PSE-36 - 36-bit Page Size Extension                     = 1 (1)
00:00:06.267594   PSN - Processor Serial Number                           = 0 (0)
00:00:06.267595   CLFSH - CLFLUSH instruction                             = 1 (1)
00:00:06.267596   DS - Debug Store                                        = 0 (1)
00:00:06.267597   ACPI - Thermal Mon. & Soft. Clock Ctrl.                 = 0 (1)
00:00:06.267598   MMX - Intel MMX Technology                              = 1 (1)
00:00:06.267599   FXSR - FXSAVE and FXRSTOR instructions                  = 1 (1)
00:00:06.267600   SSE - SSE support                                       = 1 (1)
00:00:06.267601   SSE2 - SSE2 support                                     = 1 (1)
00:00:06.267602   SS - Self Snoop                                         = 0 (1)
00:00:06.267603   HTT - Hyper-Threading Technology                        = 1 (1)
00:00:06.267604   TM - Therm. Monitor                                     = 0 (1)
00:00:06.267605   PBE - Pending Break Enabled                             = 0 (1)
00:00:06.267606   SSE3 - SSE3 support                                     = 1 (1)
00:00:06.267607   PCLMUL - PCLMULQDQ support (for AES-GCM)                = 1 (1)
00:00:06.267608   DTES64 - DS Area 64-bit Layout                          = 0 (1)
00:00:06.267609   MONITOR - MONITOR/MWAIT instructions                    = 0 (1)
00:00:06.267609   CPL-DS - CPL Qualified Debug Store                      = 0 (1)
00:00:06.267610   VMX - Virtual Machine Extensions                        = 0 (1)
00:00:06.267611   SMX - Safer Mode Extensions                             = 0 (1)
00:00:06.267612   EST - Enhanced SpeedStep Technology                     = 0 (1)
00:00:06.267613   TM2 - Terminal Monitor 2                                = 0 (1)
00:00:06.267614   SSSE3 - Supplemental Streaming SIMD Extensions 3        = 1 (1)
00:00:06.267615   CNTX-ID - L1 Context ID                                 = 0 (0)
00:00:06.267616   SDBG - Silicon Debug interface                          = 0 (0)
00:00:06.267617   FMA - Fused Multiply Add extensions                     = 0 (0)
00:00:06.267618   CX16 - CMPXCHG16B instruction                           = 1 (1)
00:00:06.267619   TPRUPDATE - xTPR Update Control                         = 0 (1)
00:00:06.267620   PDCM - Perf/Debug Capability MSR                        = 0 (1)
00:00:06.267620   PCID - Process Context Identifiers                      = 0 (1)
00:00:06.267621   DCA - Direct Cache Access                               = 0 (0)
00:00:06.267622   SSE4_1 - SSE4_1 support                                 = 1 (1)
00:00:06.267623   SSE4_2 - SSE4_2 support                                 = 1 (1)
00:00:06.267624   X2APIC - x2APIC support                                 = 1 (0)
00:00:06.267625   MOVBE - MOVBE instruction                               = 0 (0)
00:00:06.267626   POPCNT - POPCNT instruction                             = 1 (1)
00:00:06.267627   TSCDEADL - Time Stamp Counter Deadline                  = 0 (0)
00:00:06.267628   AES - AES instructions                                  = 1 (1)
00:00:06.267629   XSAVE - XSAVE instruction                               = 0 (0)
00:00:06.267630   OSXSAVE - OSXSAVE instruction                           = 0 (0)
00:00:06.267631   AVX - AVX support                                       = 0 (0)
00:00:06.267632   F16C - 16-bit floating point conversion instructions    = 0 (0)
00:00:06.267633   RDRAND - RDRAND instruction                             = 0 (0)
00:00:06.267634   HVP - Hypervisor Present (we're a guest)                = 1 (0)
00:00:06.267635 Structured Extended Feature Flags Enumeration (leaf 7):
00:00:06.267635   Mnemonic - Description                                  = guest (host)
00:00:06.267636   FSGSBASE - RDFSBASE/RDGSBASE/WRFSBASE/WRGSBASE instr.   = 0 (0)
00:00:06.267636   TSCADJUST - Supports MSR_IA32_TSC_ADJUST                = 0 (0)
00:00:06.267637   SGX - Supports Software Guard Extensions                = 0 (0)
00:00:06.267638   BMI1 - Advanced Bit Manipulation extension 1            = 0 (0)
00:00:06.267639   HLE - Hardware Lock Elision                             = 0 (0)
00:00:06.267640   AVX2 - Advanced Vector Extensions 2                     = 0 (0)
00:00:06.267641   FDP_EXCPTN_ONLY - FPU DP only updated on exceptions     = 0 (0)
00:00:06.267641   SMEP - Supervisor Mode Execution Prevention             = 0 (0)
00:00:06.267642   BMI2 - Advanced Bit Manipulation extension 2            = 0 (0)
00:00:06.267643   ERMS - Enhanced REP MOVSB/STOSB instructions            = 0 (0)
00:00:06.267644   INVPCID - INVPCID instruction                           = 0 (0)
00:00:06.267645   RTM - Restricted Transactional Memory                   = 0 (0)
00:00:06.267645   PQM - Platform Quality of Service Monitoring            = 0 (0)
00:00:06.267646   DEPFPU_CS_DS - Deprecates FPU CS, FPU DS values if set  = 0 (0)
00:00:06.267647   MPE - Intel Memory Protection Extensions                = 0 (0)
00:00:06.267648   PQE - Platform Quality of Service Enforcement           = 0 (0)
00:00:06.267648   AVX512F - AVX512 Foundation instructions                = 0 (0)
00:00:06.267649   RDSEED - RDSEED instruction                             = 0 (0)
00:00:06.267650   ADX - ADCX/ADOX instructions                            = 0 (0)
00:00:06.267651   SMAP - Supervisor Mode Access Prevention                = 0 (0)
00:00:06.267652   CLFLUSHOPT - CLFLUSHOPT (Cache Line Flush) instruction  = 0 (0)
00:00:06.267653   INTEL_PT - Intel Processor Trace                        = 0 (0)
00:00:06.267654   AVX512PF - AVX512 Prefetch instructions                 = 0 (0)
00:00:06.267655   AVX512ER - AVX512 Exponential & Reciprocal instructions = 0 (0)
00:00:06.267655   AVX512CD - AVX512 Conflict Detection instructions       = 0 (0)
00:00:06.267656   SHA - Secure Hash Algorithm extensions                  = 0 (0)
00:00:06.267657   PREFETCHWT1 - PREFETCHWT1 instruction                   = 0 (0)
00:00:06.267658   UMIP - User mode insturction prevention                 = 0 (0)
00:00:06.267659   PKU - Protection Key for Usermode pages                 = 0 (0)
00:00:06.267659   OSPKE - CR4.PKU mirror                                  = 0 (0)
00:00:06.267660   MAWAU - Value used by BNDLDX & BNDSTX                   = 0x0 (0x0)
00:00:06.267661   RDPID - Read processor ID support                       = 0 (0)
00:00:06.267662   SGX_LC - Supports SGX Launch Configuration              = 0 (0)
00:00:06.267664          Raw Hypervisor CPUID Leaves
00:00:06.267664      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267665 Gst: 40000000/0000  40000001 4b4d564b 564b4d56 0000004d
00:00:06.267666 Hst:                00000001 00000002 00000100 00000000
00:00:06.267667 Gst: 40000001/0000  01000089 00000000 00000000 00000000
00:00:06.267668 Hst:                00000001 00000002 00000100 00000000
00:00:06.267669          Raw Extended CPUID Leaves
00:00:06.267669      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267669 Gst: 80000000/0000  80000008 00000000 00000000 00000000
00:00:06.267670 Hst:                80000008 00000000 00000000 00000000
00:00:06.267671 Gst: 80000001/0000  00000000 00000000 00000001 28100800
00:00:06.267672 Hst:                00000000 00000000 00000001 28100800
00:00:06.267672 Gst: 80000002/0000  65746e49 2952286c 726f4320 4d542865
00:00:06.267674 Hst:                65746e49 2952286c 726f4320 4d542865
00:00:06.267674 Gst: 80000003/0000  37692029 55504320 20202020 4d202020
00:00:06.267675 Hst:                37692029 55504320 20202020 4d202020
00:00:06.267677 Gst: 80000004/0000  30343620 20402020 30382e32 007a4847
00:00:06.267678 Hst:                30343620 20402020 30382e32 007a4847
00:00:06.267678 Gst: 80000005/0000  00000000 00000000 00000000 00000000
00:00:06.267679 Hst:                00000000 00000000 00000000 00000000
00:00:06.267680 Gst: 80000006/0000  00000000 00000000 01006040 00000000
00:00:06.267681 Hst:                00000000 00000000 01006040 00000000
00:00:06.267682 Gst: 80000007/0000  00000000 00000000 00000000 00000100
00:00:06.267682 Hst:                00000000 00000000 00000000 00000100
00:00:06.267683 Gst: 80000008/0000  00003024 00000000 00000000 00000000
00:00:06.267684 Hst:                00003024 00000000 00000000 00000000
00:00:06.267685 Ext Name:                        
00:00:06.267685 Ext Supports:                    0x80000000-0x80000008
00:00:06.267686 Family:                          0  	Extended: 0 	Effective: 0
00:00:06.267686 Model:                           0  	Extended: 0 	Effective: 0
00:00:06.267687 Stepping:                        0
00:00:06.267687 Brand ID:                        0x000
00:00:06.267688 Ext Features
00:00:06.267688   Mnemonic - Description                                  = guest (host)
00:00:06.267708   FPU - x87 FPU on Chip                                   = 0 (0)
00:00:06.267709   VME - Virtual 8086 Mode Enhancements                    = 0 (0)
00:00:06.267710   DE - Debugging extensions                               = 0 (0)
00:00:06.267711   PSE - Page Size Extension                               = 0 (0)
00:00:06.267712   TSC - Time Stamp Counter                                = 0 (0)
00:00:06.267713   MSR - K86 Model Specific Registers                      = 0 (0)
00:00:06.267714   PAE - Physical Address Extension                        = 0 (0)
00:00:06.267715   MCE - Machine Check Exception                           = 0 (0)
00:00:06.267716   CX8 - CMPXCHG8B instruction                             = 0 (0)
00:00:06.267717   APIC - APIC On-Chip                                     = 0 (0)
00:00:06.267718   SEP - SYSCALL/SYSRET                                    = 1 (1)
00:00:06.267737   MTRR - Memory Type Range Registers                      = 0 (0)
00:00:06.267740   PGE - PTE Global Bi",Capt Obvious
20917,Ubuntu 22.04 Server unattended install fails with error isolinux.cfg not found,Mac OS X,Linux,VirtualBox 6.1.34,2022-04-27T07:14:03Z,2022-04-27T07:14:03Z,"Trying to perform an unattended install of Ubuntu 22.04 Server AMD64 on an Intel CPU MacBook Pro 2011 and I am getting the error message below.

Setup:
    - macOS 12.3.1 on MacBook Pro 2018 (with Intel CPU)
    - VirtualBox 6.1.34
    - Ubuntu Live Server 20.04 AMD64: ubuntu-22.04-live-server-amd64.iso

Serving up user-data and meta-data with a python server on port 3003, based on a Ubuntu Server doc called autoinstall-quickstart.

Getting the following error message:

VBoxManage: info: Preparing unattended installation of Ubuntu_64 in machine 'axxxxx' (b7e7ff1a-1f41-4320-8e9f-c84a2cxxxxxx).[[br]]
VBoxManage: error: Failed to open '/isolinux/isolinux.cfg' on the ISO '/Users/sxxxxx/dev/vm/iso/ubuntu-22.04-live-server-amd64.iso' (VERR_PATH_NOT_FOUND)[[br]]
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component UnattendedWrap, interface IUnattended, callee nsISupports[[br]]
VBoxManage: error: Context: ""ConstructMedia()"" at line 1859 of file VBoxManageMisc.cpp[[br]]

The files in the isolinux folder are no longer needed, because the server autoinstall is no longer based on the debian-installer (aka d-i), but rather it is based on Subiquity. Therefore, the VBoxManage unattended installer should not be looking for these. I'm afraid that this might require a VBoxManage upgrade or patch to support the new 'cloud-init' and 'curtin' with 'subiquity' based installer, unless someone can come up with a neat workaround or maybe a new unattended install template.

From browsing the source code under UnattendedTemplates/ubuntu_preseed.cfg that the template is entirely based on the debian-installer (ubiquity) and seems to have no knowledge of the new installer (subiquity).

See the source code under: /browser/vbox/trunk/src/VBox/Main/UnattendedTemplates/ubuntu_preseed.cfg on VirtualBox dot org.

Thanks in advance!",stcp
20907,VirtualBox window doesn't move or resize,Linux,Linux,VirtualBox 6.1.32,2022-04-27T13:38:30Z,2022-04-27T13:38:30Z,"Versión 6.1.34 r150636 (Qt5.12.8)
host: Ubuntu Mate 20.04.4 x64
vm: Ubuntu Mate 22.04 x64

VirtualBox window doesn't move or resize. this is an old bug, which was fixed by checking the box ""Machine Windows: Raise Windows Under Mouse""

Currently this option, despite the fact that it still solves the problem, does so partially, that is, it works intermittently",mrvst
20786,Strange audio related VM lockups,Linux,all,VirtualBox 6.1.32,2022-04-28T20:50:24Z,2022-04-28T20:50:24Z,"I am experiencing lockups related to audio playback in VirtualBox. To clarify, lockup means that Virtualbox locks up, not the guest; pressing the reset button in virtualbox does nothing. The window will not close unless I issue a ""killall VirtualBoxVM"", but the UI remains mostly responsive. This has been happening since around 6.1.24. 6.1.22 is the latest version that works fine. On the host, I am using ALSA without pulseaudio. I normally use a very customized asoundrc file, but even without my special ALSA configs, the issue still occurs. 

On a WinXP guest, I am experiencing a complete freeze when attempting to move the volume slider and sometimes audio playback causes a freeze. 

On a Ubuntu 16.04 guest (kernel 4.4), audio playback happens too fast/slow sporadically. When this happens, I see lines like these in dmesg on the guest.
[    9.025442] snd_intel8x0 0000:00:05.0: intel8x0_measure_ac97_clock: measured 55894 usecs (2880 samples)
[    9.025446] snd_intel8x0 0000:00:05.0: clocking to 44715
When that value (44715) is below 48k, audio is slow. When above, it's fast. Rebooting the VM seems to randomly change this ""clocking to ..."" value. Also, occasionally, after a long audio playback session with google chrome + youtube the VirtualBox instance will hang on shutdown (VM guest shuts down, but window remains open).",li200
20922,No Ethernet Ubuntu/Windows guest after computer wake host from sleep,Windows,all,VirtualBox 6.1.30,2022-04-30T13:37:42Z,2022-04-30T13:37:42Z,"'''Problem'''
- Broken Ethernet TX/RX in Ubuntu/Windows guest after computer wake from sleep.
- Wireshark in the guest shows TX packets, but no incoming packets.
- Wireshark in the host does not show any network traffic from/to the guest.

'''Setup'''
- VirtualBox v6.1.30 or v6.1.32
- Windows 10 20H2 host (updates installed of today)
- Ubuntu 21.04 guest or Windows 10 guest (updates + guest additions installed)
- VM Intel (R) i211 Gigabit Network connection (default)
- VM Bridge network

'''Reproducible testcase'''
1. Make sure Ethernet works on the host and guest.
2. Set computer in sleep mode.
3. Wake computer.
4. Network on host works.
5. Network in guest broken: TX and RX failed according to WireShark logs.

'''Additional info'''
- Reproducible on AMD Ryzen 7/9 and Intel Core I7 laptops/desktops.
- Hyper-V on host not enabled.
- Disabling/enabling network in guest does not work.
- Ethernet cable disconnect/reconnect host does not work.
- Virtual Ethernet link down/up guest does not work.
- Set guest in paused mode before sleep/wake host does not work.
- Disconnect Ethernet before sleep/wake host does not work.

See forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105781",Erwin
20921,After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work,Windows,Linux,VirtualBox 6.1.32,2022-04-30T19:42:55Z,2022-04-30T19:42:55Z,"After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work

See please video: https://drive.google.com/file/d/1C0IOJlqY-n71PDoVgYfVfrsuHKaUMnvD/view?usp=sharing",Ilia Poliakov
20925,"When scaling a Windows Guest, the mouse pointer is not displayed correctly in the guest",Windows,Windows,VirtualBox 6.1.34,2022-05-03T08:06:36Z,2022-05-03T08:06:36Z,"Hello, I need a scaled display in the guest system (Host→4k, Guest→FullHD). The host system (Windows, VirtualBox 6.1.34) is equipped with 2x 4k monitors (laptop + monitor connected via HDMI). In the guest (Windows) I need a Full HD resolution (1 monitor). For this I use the function VirtualBox→Display→Virtual Monitor 1→Scale to 200%. When changing the width of columns (e.g. in Windows Explorer), the mouse pointer is not displayed correctly in the guest.
see picture_01.png
In contrast, if the guest is running at a 4k resolution (scale to 100%)
see picture_02.png
the mouse pointer is displayed correctly. The behavior is independent of the operating system (Guest). The behavior is independent of the program (Guest). Changing the graphics controller on the guest (VBoxVGA, VBoxSVGA) does not change the behavior. For help, i thank you in advance ",reine667
20926,"2 screens in a guest (extended), the mouse pointer is not displayed correctly on the 2nd screen",Windows,Windows,VirtualBox 6.1.34,2022-05-03T08:31:35Z,2022-05-03T08:31:35Z,"Hello, I need 2 screens in a Windows guest system. The host system (Windows, VirtualBox 6.1.34) is equipped with 2x 4k monitors (laptop + monitor connected via HDMI). In the guest (Windows) I need 2x Full HD resolution. For this I use the function VirtualBox→Display→Virtual Monitor 1 or Virtual Monitor 2→To 200%. The display is expanded to monitor 2 (monitor 1 is the main monitor). When moving the window in Monitor 2 (e.g. Notepad), the mouse pointer is not displayed correctly in the guest
see picture_01.png
The behavior also occurs when the mouse is moved over the control elements of a window (e.g. vertical scroll bar of Notepad). The behavior is independent of the operating system (guest). The behavior is independent of the program (guest). The behavior also occurs when the guest is operated with 2x 4k resolution (scale to 100%). The behavior does not occur on monitor 1 (main Monitor).
see picture_02.png
For help, i thank you in advance",reine667
20927,Some nested qemu VM crashes at grub if launched in dozens,other,Linux,VirtualBox 6.1.32,2022-05-04T18:28:04Z,2022-05-04T18:28:04Z,"Hello,

I'm using gns3 inside vbox with multiple virtual nodes (openwrt running as qemu vms). If I start all nodes at the same time, some of them crashes during the grub countdown (or a even little bit before) with:

{{{
KVM: entry failed, hardware error 0x80000021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX=00000010 EBX=0000c866 ECX=00040000 EDX=0ff8f7c0
ESI=0ff8f760 EDI=00000005 EBP=00001ff0 ESP=00001ff0
EIP=000082fd EFL=00010006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     00008280 00000027
IDT=     00000000 000003ff
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=ef 82 00 00 08 00 66 b8 10 00 8e d8 8e c0 8e e0 8e e8 8e d0 <8b> 04 24 a3 f0 1f 00 00 a1 64 82 00 00 89 c4 89 c5 a1 f0 1f 00 00 89 04 24 31 c0 0f 01 0d
}}}

If I restart that nested VM, it should work as expected.

I didn't test 6.1.34 but this bug has been happening at least since 2020. 

I also opened an issue with gns3, but it is more likely to be a virtualbox issue:
https://github.com/GNS3/gns3-gui/issues/3330",Luiz Angelo Daros de Luca
20928,"Wrong IPC socket being deleted when VirtualBox is run via su on Linux, leading to possible disk corruption in VMs",Linux,all,VirtualBox 6.1.34,2022-05-05T13:10:54Z,2022-05-05T13:10:54Z,"This is related to ticket #17029 which has the same symptoms, but I'm not sure if it is caused by the same issue.

!VirtualBox, via src/VBox/Installer/linux/VBox.sh, checks for the presence of a VBoxSVC process owned by the current user and will delete a user-specific directory in /tmp if no process is found. But the process check uses the ""whoami"" command to get the current username and the deletion uses the environment variables $LOGNAME or $USER. Certain implementations of su, such as the one from util-linux, does not update $LOGNAME or $USER when switching to the root user, but whoami will return ""root"". Thus, if a user named ""vmuser"" runs !VirtualBox through su, it will search for processes owned by root but delete the socket belonging to vmuser.

The removal of these files will then lead to bad side effects for VMs that were previously running, as future calls to !VirtualBox will create a new IPC socket in /tmp. When using this new socket, all VMs will be shown as being powered off when they might still be running. It is also possible to start another instance of a running VM, which leads to disk corruption when both instances attempt to write to the same disk image.

Not all implementations of su seem to behave in this way, and using sudo or ""sudo su"" can sometimes cause $LOGNAME and $USER to be changed to ""root"", mitigating the issue. Using su by itself seems to have the highest chance of triggering this bug.

Replication steps:
1. Start any VM using ""{{{vboxmanage startvm <VM_NAME> --type headless}}}"" (take a snapshot beforehand in case of disk corruption).
2. Check that two files called ""ipcd"" and ""lock"" are present using ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"".
3. Try to start the same VM again, this should fail with a message that the VM is already locked by a session.
4. Switch to the root account using ""{{{su}}}"" and run ""{{{vboxmanage list vms}}}"".
5. Exit the root shell and run ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"" again to see that the files from step !#2 are now missing.
6. Try to start the VM with the same command as in step !#1, this should now succeed.
7. Run ""{{{ps aux | grep -i vboxheadless}}}"" and see that there are now two processes started for the same VM.

The expected behavior would be that the files in /tmp/.vbox-$USER-ipc/ remain untouched and that step !#6 should refuse to start another VM instance.

While this issue only seems to occur when su does not update $LOGNAME and $USER, I'd argue that either whoami or $LOGNAME/$USER should be used instead of having a mix of both. While running !VirtualBox as root is not recommended, it would be nice if accidentally running ""{{{vboxmanage list vms}}}"" as root did not immediately break existing IPC sessions. I have attached a small patch to replace the use of whoami with $LOGNAME/$USER, and hereby make this modification available under the MIT license.

The !VirtualBox log files are unlikely to contain any relevant information about this bug since it occurs in the initial shell wrapper script, but I can attach them if needed. Here are the results of running the replication steps on an unpatched installation (tested on Ubuntu 22.04 using !VirtualBox 6.1.34):

{{{
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ls -l /tmp/.vbox-$USER-ipc
total 4
srwx------ 1 vmuser vmuser 0 May  5 11:21 ipcd
-rw------- 1 vmuser vmuser 6 May  5 11:21 lock
$ vboxmanage startvm test_VM --type headless
VBoxManage: error: The machine 'test_VM' is already locked by a session (or being locked or unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())"" at line 726 of file VBoxManageMisc.cpp
$ su
Password: 
# vboxmanage list vms
""<inaccessible>"" {7abbc342-2595-4b5d-b13b-4f57b7d4d367}
""<inaccessible>"" {26b6e251-e3c9-4004-a23e-30e5dd55f652}
""<inaccessible>"" {ed047e7d-83db-46b6-8d09-cd99f05f7362}
""<inaccessible>"" {2256db63-2e33-40fd-9182-7631a68a9e64}
""<inaccessible>"" {bf2390e8-3978-4363-9792-e370986ce5fc}
# exit
$ ls -l /tmp/.vbox-$USER-ipc
/usr/bin/ls: cannot access '/tmp/.vbox-vmuser-ipc': No such file or directory
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ps aux | grep -i vboxheadless
vmuser     46799  2.2  0.6 1757468 431480 ?      Sl   11:38   0:01 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
vmuser     47353 59.8  0.2 1482004 157324 ?      Sl   11:39   0:03 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
}}}
",Busan15
19535,Black screen after logon,other,Windows,VirtualBox 6.1.6,2022-05-05T23:43:18Z,2022-05-05T23:43:18Z,"I'm trying to work on Oracle DB Developer VM, but it simply goes into black screen after the logon. I have checked all the requirements for this VM and verified if some settings are well, but I couldn't find anything wrong.
I have attached the log file and a screen.

Any advice or suggestion would be very helpful.

Thanks and have a nice day!",george2123
20929,"""vboxmanage showvminfo"" creates warning when editing guest settings",Linux,Windows,VirtualBox 6.1.30,2022-05-10T15:38:13Z,2022-05-10T15:38:13Z,"I have a bash script running in the background that checks every few seconds if a VM is running on my second workspace of Mint20. When i am in Virtualbox Manager and want to edit a setting of a VM that is NOT running, i get a warning that the VM is running and not all settings are stored or changed.. every time that script is called. The exact warning is in Dutch, but from the forum is got this in English:

'''""The virtual machine you are changing has been started. Only certain settings can be changed while a machine is running. All other changes will be lost if you close this window now""'''

The line in the bash script is:
'''""vboxmanage showvminfo ""W7_64"" | grep -c ""running (since"" ""'''

So calling ""vboxmanage showvminfo"" creates a warning that the VM is running when you try to edit guest settings.

To create this situation, open vbox manager, click on usb settings an leave that open, then go to the terminal and start ""vbmanage showvminfo"". The warning pops up that the VM is running.

",RemonK17
19043,XWayland breaks mouse behavior on Linux/Wayland Hosts,Linux,other,VirtualBox 6.0.14,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
20943,Latest Win 11 updates causing total fault of Virtualbox ver.6.1.34,Windows,Linux,VirtualBox 6.1.34,2022-05-15T06:06:30Z,2022-05-15T06:06:30Z,"Environment: PC HP EliteDesk 800 G8 Tower PC
Processor	11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz   2.50 GHz
Installed RAM	16,0 GB (15,7 GB usable)
System type	64-bit operating system, x64-based processor

OS Windows 11 (upgrade from Win 10 on day of first installation 11-04-2022)
Edition	Windows 11 Pro
Version	21H2
Installed on	‎11/‎04/‎2022
OS build	22000.593
Experience	Windows Feature Experience Pack 1000.22000.593.0

Network private IP 192.168.0.x
Network Adapter Intel Ethernet Connection (14) I219-LM

VirtualBox Oracle ver.6.1.34
with Bridged Adapter attached to Intel Ethernet Connection (14) I219-LM
Adapter Type Intel PRO/1000 MT Desktop (82540EM)

Total fault description:

After start of VM (Debian10 iso image) in early starting phase entire process stoped with VM total failure. 
Until 26-04-2022 (before Win11 update) was this VM running without any problem as well as several other Debian 8, 9, 10 VMs.
After updates on 26-04-2022 with:
Cumulative Update for Windows 11 for x64-based Systems (KB5012643)
Cumulative Update for Windows 11 for x64-based Systems (KB5012592)
total fault appears as
collision in net drivers - VirtualBox Host-Only Ethernet Adapter) Cumulative Update for Windows 11 for x64-based Systems (KB5012643) 

After uninstall of updates the VM is working without any problem.

Supposed fault source:
VirtualBox driver 'Host-Only Ethernet Adapter' is unable to run with newest Win 11 updates.

Remarks: 
When fault occurs I done plenty of tests with different VirtualBox Network settings (NAT,..) and Intel drivers but no solution found. Only uninstall of latest Win updates allowed fault-free run. 
New updates of Win11 published in May 2022 are causing the same problem with VirtualBox.",jotcomponents
20945,Corner dragging second dual monitor screen causes monitor close without warning,Windows,Linux,VirtualBox 6.1.32,2022-05-17T00:46:57Z,2022-05-17T00:46:57Z,"Using the cursor and left clicking the double arrow to expand/contract monitor 2 will cause the monitor to suddenly close with no warning.

You have to go back to the View menu and click on ""Enable"" Virtual Screen 2 to reopen it.

Using Minimize/Maximize buttons on Virtual Screen work as normal.  The sudden close only happens when dragging the corner to resize it.

System: Unbuntu 20.4
Virtual Box: Oracle VM Virtual Box 6.1
    In VBox Settings assigned Video settings 40MB


It's a minor issue, just thought engineering might want to know it exists, should be duplicable.",Tony C
20931,"VBoxSVGA-3d,host gpu memory leak",Linux,Windows,VirtualBox 6.1.34,2022-05-17T18:07:12Z,2022-05-17T18:07:12Z,"I use VBoxSVGA device and open 3D accelerate.
I tried to open and close the chrome browser repeatedly, then I use nvidia-smi to see host gpu memory,I found that the gpu memory leaked.
I print pState->papSurfaces ,Lots of host surface are not released.

host
ubuntu-18.04 kernel-5.4.0-107-generic
virtualbox-6.1.34

guest
windows7x64,windows10x64
chrome-100.0.4896.127",lumory
20946,No audio Pop!OS 22.04 guest / Virtualbox 6.1.34,Windows,Linux,VirtualBox 6.1.34,2022-05-18T07:22:07Z,2022-05-18T07:22:07Z,"Hello Community,

I've got no in&out audio anymore since upgrading my vm to release Pop!OS 22.04. Maybe because the audio subsystem is now using Pipewire ? 

More precisely, for Windows DirectSound + Intel HD Audio. Only ICH AC97 does produce sound. But it's heavily garbled. 

Since this is an Ubuntu based distribution I presume this happens to all Ubuntu 22.04 releases. 

Rebuilding the kernel with the guest additions didn't help.

Is there anything I can try or help with to resolve this issue ?",JLC
15043,VMSetError for ACPI tables < 64k,Linux,other,VirtualBox 5.0.12,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
20947,VirtualBox and VirtualBoxVM segfault when focus changes,Mac OS X,other,VirtualBox 6.1.34,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
20948,Host CPU very high when guest is idle,Mac OS X,Windows,VirtualBox 6.1.32,2022-05-19T17:11:07Z,2022-05-19T17:11:07Z,"Hi,
running Virtualbox on MAC OS X Monterrey (12.4) virtualbox gets very high CPU even when windows guest is completely idle, 1%-3% approx.

Right now I´ve set up Execution Tap to 50%, but nothing changes virtualbox process on running above 98%, when Execution Tap is 100%, cpu on host is above 200% and my mac sounds like an helicopter!

Logs here: https://logpaste.com/6c57FdSg

Note: All guest additions are installed on guest",Raul
20950,Network interface names in the GUI are unsorted,Linux,all,VirtualBox 6.1.32,2022-05-20T10:14:25Z,2022-05-20T10:14:25Z,"The network interface names in the GUI are unsorted. When configuring a bridged adapter to be mapped to one of many test VLAN interfaces on a host machine, it is necessary to go linearly through the whole list to find the right interface. The list should be alphabetically sorted.",Thomas Dreibholz
20951,"Después de desconectar segundo monitor, la máquina virtual sigue intentando mostrarse allí",Windows,Windows,VirtualBox 6.1.32,2022-05-20T16:44:03Z,2022-05-20T16:44:03Z,"Ayer trabajé con un monitor adicional a mi computadora.  Abrí una máquina virtual y la desplegué en el monitor externo.
Hoy ya no tengo ese monitor.  Abrí VirtualBox, abro la misma máquina virtual de ayer, pero no se despliega en la pantalla del computador, el problema es que se está desplegando en el monitor externo que ya no tengo conectado.
Bajé todas las ventanas (Win+D) para intentar ver la máquina virtual, pero no hay forma.",renezito
20955,Debian Jessie not booting on VBox 6.0.24,Windows,Linux,,2022-05-23T16:45:03Z,2022-05-23T16:45:03Z,"Hello,

Recently downloaded VirtualBox under Windows, and I'm struggling to run Debian 8.11.1 ('''Jessie''') as my ''guest'' OS.

At the moment, I've tried to boot it from a ''DVD'' iso (after successful installation), but as soon as it's meant to login the screen prompts a message like ""Something went wrong, and the system can't recover""...

I've read this might be due to VBox graphical settings, and that a VBoxSVGA controller was suggested in place of VMSVGA.

Almost nothing changed by enabling or disabling 3D acceleration...

Please, can you help?

Mine was the first installer from here: [https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-dvd/]

Thanks",Antonin
18705,Icon error,Linux,Linux,VirtualBox 6.0.8,2022-05-30T22:25:28Z,2022-05-30T22:25:28Z,"i am using ubuntu as host and when i launch some virtual machine, the icon does not appears. It looks like a lost item.",betoherrera82
20963,Window decorations do not scale correctly when moved across monitors,Windows,Linux,VirtualBox 6.1.34,2022-05-31T21:25:43Z,2022-05-31T21:25:43Z,"I have a multi monitor setup on my windows 10 host.  One of the screens has a much higher DPI than the others so I ran it at native resolution and use scaling to keep the same visual appearance as the other.  This is the microsoft recommended approach, and is the default configuration for this device.

Under this setup, any virtual box window always has the scaling for that first monitor applied - when I move any VB window to the other display, the title bar is twice as big as it should be, and windows that open there are sized twice as big as you'd expect.  Window contents appear to scale fine.

This doesn't happen with any other application that I've found so far.  All other apps scale correctly depending which monitor they on.

An easy test is to have a common edge between the monitors and move a window so it's half on each  monitor, then move and back and forth so the majority falls on different monitors - you will see the scaling take affect as you do, and notice that VB windows behave differently to other applications.

To reproduce:
1. Set up two monitors, and configure the main monitor with a scale factor of 200%
2. Open up the main VirtualBox window, and move it between the monitors - observe the size of the title bar as you do so.  Slowly move until 50% of the window is on the other monitor, and observe changes.  Repeat these steps with a non VB window (e.g. notepad, explorer) to see the difference",gkcgareth
11577,Secure Boot doesn't allow 'vboxdrv' module to load (now works for Ubuntu and Debian 10+ hosts),Linux,all,VirtualBox 4.2.8,2022-06-01T09:54:37Z,2022-06-01T09:54:37Z,"Host - Fedora 18 64 bit
Bios has Secure Boot enabled.

When I try to start any machine it says:


{{{
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
}}}


{{{
[user@localhost ~]$ sudo /etc/init.d/vboxdrv setup
[sudo] password for user: 
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS[  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

}}}


{{{
[user@localhost ~]$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
}}}
",Quickbooks Office
20959,Unable To Insert Guest Additional CD Image,Windows,Windows,VirtualBox 6.1.34,2022-06-03T13:38:45Z,2022-06-03T13:38:45Z,"I Can't Insert Guest Additional CD Image I Need To Do It '''Manually'''
From The Folder, I'm Windows 10 64 Bit Virtualbox 6.1.34 Please Fix It",Miniblox Gaming
20966,Ova/Ovf Signature Verification Issue,Windows,other,VirtualBox 6.1.34,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
20967,"Sometimes mouse works only in part of the screen, 6.1.34 with Ubuntu 22.04 guest",Windows,Linux,VirtualBox 6.1.34,2022-06-03T14:52:12Z,2022-06-03T14:52:12Z,"Host: Windows 10, Guest: Ubuntu 22.04

When booting the Guest OS, occasionally mouse support works only partially:
* Mouse clicks work in the left-side of the dock, but not with rest of the desktop
* Mouse cursor is correctly set and shows everywhere
* After right-clicking a dock item the context menu can be properly clicked
* In full-screen mode additionally the small top-right triple icon menu works as well (but not in windowed mode)
* Keyboard support seems to work properly, and if I e.g. open Terminal from the dock, keyboard input for the terminal works although mouse input doesn't work.
* Switching between PS/2 or Tablet as VM Pointing Device setting doesn't seem to affect the issue.

Additional details:
CPU type core i7-8700K, VT-x, Nested VT-x and Nested Paging enabled. (Probably not relevant)

WORKAROUND:
The issue seems to go away if Wayland is disabled by editing /etc/gdm3/custom.conf

Forum thread:
https://forums.virtualbox.org/viewtopic.php?f=3&t=106184",jlauha
17345,"Display showing at 1/4 size, mouse input area normal (Windows host / Linux guest)",Windows,Linux,VirtualBox 5.2.0,2022-06-03T16:02:23Z,2022-06-03T16:02:23Z,"The guest displays over 1/2 x 1/2 (a quarter) of the top left of the total screen area, while the mouse responds over the whole area. If I want to click the system menu in the top right of the screen, for example, I have to click at the top right of the black space, and the menu responds as shown.


This is definitely a HiDPI issue. As you can also see in the picture, the title bar is half the size it should be, the menu bar is twice the size it should be (like the scaling was applied twice), and the icons at the bottom are also twice as large. Scaling is at 200%, so I think the title bar is at 100% and the title bar is at 400%. However, some of this is probably confounded with having a HiDPI and a normal screen on different monitors.

Changing resolution on the guest or scaling on the host doesn't fix the problem; it makes the overall window change as expected but the visible area is still a quarter of the size.

Disabling 3D acceleration fixes the issue, but it just makes everything a whole lot laggier to use as compositing is not available.

I ran into this issue after updating from 5.1.22. Several versions I tried from 5.1.24 to 5.2.2 have the same problem, so I think some change in 5.1.24 broke it.

Related thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=83223 . In that thread someone with an Ubuntu host / Win 8 guest claims to have the same problem.",mizzao
20968,Crash virtualbox guest,Linux,Windows,VirtualBox 6.1.32,2022-06-06T15:47:17Z,2022-06-06T15:47:17Z,"I have a crash on virtualbox ""AVORTED""[[BR]]
Thank.[[BR]]

 ",Sizy458
20969,Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.  The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.  Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df},Windows,Linux,VirtualBox 6.1.34,2022-06-07T18:21:22Z,2022-06-07T18:21:22Z,"Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.

The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

'''VBoxHardening.log:'''
{{{
1c58.1e4c: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000084 g_uNtVerCombined=0xa04a6300
1c58.1e4c: \SystemRoot\System32\ntdll.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:24.962297600Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.242392000Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1eeb38
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x1f5000 (2052096)
1c58.1e4c:     Resource Dir:    0x184000 LB 0x6fff8
1c58.1e4c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1682
1c58.1e4c:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: NT Layer DLL
1c58.1e4c: \SystemRoot\System32\kernel32.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:16.157371700Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.008042100Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0xbb058
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0xbd000 (774144)
1c58.1e4c:     Resource Dir:    0xbb000 LB 0x520
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\KernelBase.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:25.904947200Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.226771300Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x2cf640
1c58.1e4c:     NT Headers:      0xf0
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x2cd000 (2936832)
1c58.1e4c:     Resource Dir:    0x2a4000 LB 0x548
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\apisetschema.dll:
1c58.1e4c:     CreationTime:    2019-12-07T09:08:13.518339400Z
1c58.1e4c:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
1c58.1e4c:     ChangeTime:      2022-05-13T09:38:12.902031600Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1f538
1c58.1e4c:     NT Headers:      0xd0
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x20000 (131072)
1c58.1e4c:     Resource Dir:    0x1f000 LB 0x408
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1
1c58.1e4c:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: ApiSet Schema DLL
1c58.1e4c: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1c58.1e4c: supR3HardenedWinFindAdversaries: 0x800
1c58.1e4c: \SystemRoot\System32\drivers\cfrmd.sys:
1c58.1e4c:     CreationTime:    2014-06-26T05:33:42.000000000Z
1c58.1e4c:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
1c58.1e4c:     ChangeTime:      2020-10-11T11:10:28.369648400Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x9d20
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Image Version:   6.1
1c58.1e4c:     SizeOfImage:     0xe000 (57344)
1c58.1e4c:     Resource Dir:    0xc000 LB 0x3e0
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Windows (R) Win 7 DDK driver
1c58.1e4c:     ProductVersion:  6.1.7600.16385
1c58.1e4c:     FileVersion:     6.1.7600.16385 built by: WinDDK
1c58.1e4c:     FileDescription: Safe Deletion Driver
1c58.1e4c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: Calling main()
1c58.1e4c: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
1c58.1e4c: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: SUPR3HardenedMain: Respawn #1
1c58.1e4c: System32:  \Device\HarddiskVolume4\Windows\System32
1c58.1e4c: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1c58.1e4c: KnownDllPath: C:\WINDOWS\System32
1c58.1e4c: supR3HardenedWinInit: Performing a limited self purification...
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=SELF_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000042ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000430000-000000000043ffff 0x0004/0x0004 0x0040000
1c58.1e4c:   0000000000440000-000000000044ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000450000-000000000046cfff 0x0002/0x0002 0x0040000
1c58.1e4c:   000000000046d000-000000000046ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000470000-0000000000520fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000521000-0000000000523fff 0x0104/0x0004 0x0020000
1c58.1e4c:   0000000000524000-000000000056ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *0000000000570000-0000000000573fff 0x0002/0x0002 0x0040000
1c58.1e4c:   0000000000574000-000000000057ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000580000-0000000000581fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000582000-000000000058ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000590000-0000000000591fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000592000-00000000005a9fff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000005aa000-00000000005fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000600000-00000000006affff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000006b0000-00000000006b2fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000006b3000-00000000007fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000800000-00000000008c8fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008c9000-00000000008dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008e0000-00000000008e5fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000008e6000-00000000009dffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00000000009e0000-0000000000a06fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a07000-0000000000adffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000ae0000-0000000000b0ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000b10000-0000000000b1efff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000b1f000-0000000000b1ffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000b20000-0000000000b2afff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000b2b000-0000000000d20fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000d21000-0000000000d21fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000d22000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff4407dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff4407e0000-00007ff4407e4fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff4407e5000-00007ff4408dffff 0x0000/0x0002 0x0040000
1c58.1e4c:  *00007ff4408e0000-00007ff5408fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00007ff540900000-00007ff5428fffff 0x0000/0x0004 0x0020000
1c58.1e4c:   00007ff542900000-00007ff542900fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00007ff542901000-00007ff54290ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542910000-00007ff542910fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542911000-00007ff54291ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542920000-00007ff542942fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542943000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc14fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc15000-00007ff7afc17fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc18000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1bfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1c000-00007ff7afc1dfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1e000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe210ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe2110000-00007ffbe2110fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2111000-00007ffbe2225fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2226000-00007ffbe239efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe239f000-00007ffbe23a2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a3000-00007ffbe23a3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a4000-00007ffbe23dcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23dd000-00007ffbe3f1ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe3f20000-00007ffbe3f20fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f21000-00007ffbe3f9efff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f9f000-00007ffbe3fd1fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd2000-00007ffbe3fd2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd3000-00007ffbe3fd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd4000-00007ffbe3fdcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fdd000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe4694fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4695000-00007ffbe4696fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4697000-00007ffbe469ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
1c58.1e4c: kernelbase.dll: timestamp 0x458acb5b (rc=VINF_SUCCESS)
1c58.1e4c: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1c58.1e4c: supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=0
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
1c58.1e4c: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardenedWinDoReSpawn(1): New child 284c.3ce4 [kernel32].
1c58.1e4c: supR3HardNtChildGatherData: PebBaseAddress=0000000000a24000 cbPeb=0x388
1c58.1e4c: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
1c58.1e4c: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
1c58.1e4c: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000a24000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=00000000009bfe78 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
1c58.1e4c: supR3HardenedWinSetupChildInit: Start child.
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1c58.1e4c: supR3HardNtChildPurify: Startup delay kludge #1/0: 523 ms, 34 sleeps
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000087ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000880000-000000000089ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000008a0000-00000000008bcfff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008bd000-00000000008bffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008c0000-00000000009bafff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000009bb000-00000000009bdfff 0x0104/0x0004 0x0020000
1c58.1e4c:   00000000009be000-00000000009bffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000009c0000-00000000009c3fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000009c4000-00000000009cffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000009d0000-00000000009d1fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000009d2000-00000000009fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000a00000-0000000000a23fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000a24000-0000000000a26fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a27000-0000000000bfffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000c00000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff5ee77ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee780000-00007ff5ee780fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee781000-00007ff5ee78ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee790000-00007ff5ee7b2fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee7b3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: supR3HardNtChildPurify: Done after 526 ms and 0 fixes (loop #0).
284c.3ce4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
284c.3ce4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~00000000009bf908)
284c.3ce4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
284c.3ce4: New simple heap: #1 0000000000d00000 LB 0x400000 (for 2052096 allocation)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: System32:  \Device\HarddiskVolume4\Windows\System32
284c.3ce4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
284c.3ce4: KnownDllPath: C:\WINDOWS\System32
284c.3ce4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
284c.3ce4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
284c.3ce4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
284c.3ce4: Registered Dll notification callback with NTDLL.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
284c.3ce4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 107 ms.
284c.3ce4: \SystemRoot\System32\ntdll.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:24.962297600Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1eeb38
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x1f5000 (2052096)
284c.3ce4:     Resource Dir:    0x184000 LB 0x6fff8
284c.3ce4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1682
284c.3ce4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: NT Layer DLL
284c.3ce4: \SystemRoot\System32\kernel32.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:16.157371700Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0xbb058
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0xbd000 (774144)
284c.3ce4:     Resource Dir:    0xbb000 LB 0x520
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\KernelBase.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:25.904947200Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x2cf640
284c.3ce4:     NT Headers:      0xf0
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x2cd000 (2936832)
284c.3ce4:     Resource Dir:    0x2a4000 LB 0x548
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\apisetschema.dll:
284c.3ce4:     CreationTime:    2019-12-07T09:08:13.518339400Z
284c.3ce4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
284c.3ce4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1f538
284c.3ce4:     NT Headers:      0xd0
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x20000 (131072)
284c.3ce4:     Resource Dir:    0x1f000 LB 0x408
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1
284c.3ce4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: ApiSet Schema DLL
284c.3ce4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
284c.3ce4: supR3HardenedWinFindAdversaries: 0x800
284c.3ce4: \SystemRoot\System32\drivers\cfrmd.sys:
284c.3ce4:     CreationTime:    2014-06-26T05:33:42.000000000Z
284c.3ce4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
284c.3ce4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x9d20
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Image Version:   6.1
284c.3ce4:     SizeOfImage:     0xe000 (57344)
284c.3ce4:     Resource Dir:    0xc000 LB 0x3e0
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Windows (R) Win 7 DDK driver
284c.3ce4:     ProductVersion:  6.1.7600.16385
284c.3ce4:     FileVersion:     6.1.7600.16385 built by: WinDDK
284c.3ce4:     FileDescription: Safe Deletion Driver
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: Calling main()
284c.3ce4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
284c.3ce4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: SUPR3HardenedMain: Respawn #2
284c.3ce4: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
284c.3ce4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ntdll.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
284c.3ce4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe4530000 'C:\WINDOWS\System32\ntdll.dll'
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardenedWinDoReSpawn(2): New child 255c.41c4 [kernel32].
284c.3ce4: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
284c.3ce4: supR3HardNtChildGatherData: PebBaseAddress=0000000000ccf000 cbPeb=0x388
284c.3ce4: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
284c.3ce4: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
284c.3ce4: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000ccf000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=0000000000b9fad8 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
284c.3ce4: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
284c.3ce4: supR3HardenedWinSetupChildInit: Start child.
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
284c.3ce4: supR3HardNtChildPurify: Startup delay kludge #1/0: 524 ms, 34 sleeps
284c.3ce4: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
284c.3ce4:  *0000000000000000-0000000000a5ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000a60000-0000000000a7ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000a80000-0000000000a9cfff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000a9d000-0000000000a9ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000aa0000-0000000000b9afff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000b9b000-0000000000b9dfff 0x0104/0x0004 0x0020000
284c.3ce4:   0000000000b9e000-0000000000b9ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000ba0000-0000000000ba3fff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000ba4000-0000000000baffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000bb0000-0000000000bb1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000bb2000-0000000000bfffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000c00000-0000000000ccefff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000ccf000-0000000000cd1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000cd2000-0000000000dfffff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000e00000-000000007ffdffff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe4000-00007ff55706ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557070000-00007ff557070fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff557071000-00007ff55707ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557080000-00007ff5570a2fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff5570a3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
284c.3ce4: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supR3HardNtChildPurify: Done after 566 ms and 0 fixes (loop #0).
284c.3ce4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000d00000 LB 0x400000)
255c.41c4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
255c.41c4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~0000000000b9f568)
284c.3ce4: supR3HardNtEnableThreadCreationEx:
255c.41c4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
255c.41c4: New simple heap: #1 0000000000f00000 LB 0x400000 (for 2052096 allocation)
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: System32:  \Device\HarddiskVolume4\Windows\System32
255c.41c4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
255c.41c4: KnownDllPath: C:\WINDOWS\System32
255c.41c4: supR3HardenedVmProcessInit: Opening vboxdrv...
255c.41c4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
255c.41c4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
255c.41c4: Registered Dll notification callback with NTDLL.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
255c.41c4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 125 ms.
255c.41c4: \SystemRoot\System32\ntdll.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:24.962297600Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1eeb38
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x1f5000 (2052096)
255c.41c4:     Resource Dir:    0x184000 LB 0x6fff8
255c.41c4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1682
255c.41c4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
255c.41c4:     FileDescription: NT Layer DLL
255c.41c4: \SystemRoot\System32\kernel32.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:16.157371700Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0xbb058
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0xbd000 (774144)
255c.41c4:     Resource Dir:    0xbb000 LB 0x520
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\KernelBase.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:25.904947200Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x2cf640
255c.41c4:     NT Headers:      0xf0
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x2cd000 (2936832)
255c.41c4:     Resource Dir:    0x2a4000 LB 0x548
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\apisetschema.dll:
255c.41c4:     CreationTime:    2019-12-07T09:08:13.518339400Z
255c.41c4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
255c.41c4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1f538
255c.41c4:     NT Headers:      0xd0
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x20000 (131072)
255c.41c4:     Resource Dir:    0x1f000 LB 0x408
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1
255c.41c4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
255c.41c4:     FileDescription: ApiSet Schema DLL
255c.41c4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
255c.41c4: supR3HardenedWinFindAdversaries: 0x800
255c.41c4: \SystemRoot\System32\drivers\cfrmd.sys:
255c.41c4:     CreationTime:    2014-06-26T05:33:42.000000000Z
255c.41c4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
255c.41c4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x9d20
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Image Version:   6.1
255c.41c4:     SizeOfImage:     0xe000 (57344)
255c.41c4:     Resource Dir:    0xc000 LB 0x3e0
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Windows (R) Win 7 DDK driver
255c.41c4:     ProductVersion:  6.1.7600.16385
255c.41c4:     FileVersion:     6.1.7600.16385 built by: WinDDK
255c.41c4:     FileDescription: Safe Deletion Driver
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: Calling main()
255c.41c4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
255c.41c4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: SUPR3HardenedMain: Final process, opening VBoxDrv...
255c.41c4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000f00000 LB 0x400000)
255c.41c4: supR3HardNtEnableThreadCreationEx:
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll: Signature #1/2: info status: 24202
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbdcfb0000 LB 0x00005000 C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\wintrust.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\wintrust.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume4\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msvcrt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msvcrt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe26a0000 LB 0x0009e000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2510000 LB 0x00068000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c70000 LB 0x00100000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ucrtbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ucrtbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1d70000 LB 0x00156000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\crypt32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\crypt32.dll
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-localization-l1-2-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-localization-l1-2-1'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msasn1.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msasn1.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1830000 LB 0x00012000 C:\WINDOWS\SYSTEM32\MSASN1.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\system32\Wintrust.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcrypt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcrypt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcrypt.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c40000 LB 0x00027000 C:\WINDOWS\System32\bcrypt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1c40000 'C:\WINDOWS\system32\bcrypt.dll'
255c.41c4: bcrypt.dll loaded at 00007ffbe1c40000, BCryptOpenAlgorithmProvider at 00007ffbe1c451e0, preloading providers:
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcryptprimitives.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe23e0000 LB 0x00082000 C:\WINDOWS\System32\bcryptprimitives.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe23e0000 'C:\WINDOWS\system32\bcryptprimitives.dll'
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD2',0,0) -> 0x0 (hAlgo=00000000014417e0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD4',0,0) -> 0x0 (hAlgo=0000000001441e60)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD5',0,0) -> 0x0 (hAlgo=0000000001442180)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA1',0,0) -> 0x0 (hAlgo=00000000014434b0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA256',0,0) -> 0x0 (hAlgo=00000000014437d0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA512',0,0) -> 0x0 (hAlgo=0000000001443af0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'RSA',0,0) -> 0x0 (hAlgo=0000000001443e10)
255c.41c4:     BCryptOpenAlgorithmProvider(,'DSA',0,0) -> 0x0 (hAlgo=0000000001444130)
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptsp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptsp.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe15f0000 LB 0x00018000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rsaenh.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rsaenh.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume4\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0cb0000 LB 0x00034000 C:\WINDOWS\system32\rsaenh.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1610000 LB 0x0000c000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptbase.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\kernel32.dll'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\WINTRUST.DLL (Input=WINTRUST.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\System32\WINTRUST.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\CRYPT32.dll (rcNtResolve=0xc0150008) *pfFlags=0x2 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1d70000 'C:\WINDOWS\System32\CRYPT32.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe4280000 LB 0x0001d000 C:\WINDOWS\System32\imagehlp.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\imagehlp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\imagehlp.dll
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\gpapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\gpapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0510000 LB 0x00023000 C:\WINDOWS\SYSTEM32\gpapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\gpapi.dll [lacks WinVerifyTrust]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\profapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\profapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1b80000 LB 0x0001f000 C:\WINDOWS\SYSTEM32\profapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\profapi.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'crypt32.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptnet.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptnet.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume4\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWin",Murdoch
20971,Linux guest VM hangs after upgrading VirtualBox to 6.1.34,Windows,Linux,VirtualBox 6.1.34,2022-06-07T18:32:33Z,2022-06-07T18:32:33Z,"I'm running VirtualBox on Windows 10.
I've recently updated VirtualBox from 6.1.30 to 6.1.34.
My Ubuntu 20.04 VM has hung during an upgrade to Ubuntu 22.04.
I had to force close the VM. This has caused the system to become unbootable, so I've installed Ubuntu 22.04 from scratch.
After installation the system started hanging during boot or just after fresh login. The hanging was so hard that the guest system became unusable - I had to force close it.
I've downgraded VirtualBox to 6.1.32, but the problem persisted.
The problem went away after a second downgrade to version 6.1.30.

I'm using a default hypervisor in the VM so it's probably Hyper-V.",Przemysław Kulczycki
20940,Unable to boot any VM (Ubuntu): kernel panic - not syncing attempted to kill the idle task,Windows,Linux,VirtualBox 6.1.32,2022-06-08T08:42:34Z,2022-06-08T08:42:34Z,"Hello everyone.

I can't boot any of my VMs in Virtualbox. I have several VMs with different versions of Ubuntu, specifically Ubuntu 12 and Ubuntu 20. The same problem occurs in all of them when starting, getting on the screen: ""kernel panic - not syncing attempted to kill the idle task "". Attached log. I have tried to generate a new VM with Ubuntu 12, but I get the same problem. Thanks for your help.",pmartinezOracle
20973,guru meditation,Windows,Windows,VirtualBox 6.1.32,2022-06-08T15:15:08Z,2022-06-08T15:15:08Z,"Hello.

With the last update of the VirtualBox, I have a problem with the Virtual Machines.

The host is in Windows 7 - 64 bits.

When the Virtual Machine starts, sometimes show the guru meditation.

I attach the files if somebody can help me.

Thanks for all.",Ino
20974,Critical Error while installing windows 10 in virtualbox,Windows,Windows,VirtualBox 6.1.34,2022-06-08T17:00:27Z,2022-06-08T17:00:27Z,Critical Error while installing windows 10 in virtualbox. At the beginning of the install of windows 10 a popup window alerted me that an error occurred. It did not specify the error but gave an option to ignore or power down.,Tony_Z
20975,VERR_VMX_VMXON_FAILED during install of CentOS 7,Windows,Linux,VirtualBox 6.1.34,2022-06-08T23:22:16Z,2022-06-08T23:22:16Z,While installing CentOS 7 VM failed with VERR_VMX_VMXON_FAILED and  NtOpenDirectoryObject failed on \Driver: 0xc0000022. Unable to restart VM. ,Tony_Z
20962,machine guest freeze on emit audio,Linux,Windows,VirtualBox 6.0.22,2022-06-10T14:43:03Z,2022-06-10T14:43:03Z,"Hello [[BR]]

Virtualbox 6.0.24[[BR]]


I play audio mp3 MCI windows, then the machine guest random freeze[[BR]]
Thank.[[BR]]
",Sizy458
20978,pop critical error,Windows,Windows,VirtualBox 6.1.34,2022-06-10T15:42:38Z,2022-06-10T15:42:38Z,"when I open the virtual machine it tells me ""critical error"". I tried to uninstall and install virtualbox but the same thing always happens.
I attach log",luzzillo
20979,machine folder share corrupts data,Linux,Linux,VirtualBox 6.1.34,2022-06-11T01:27:45Z,2022-06-11T01:27:45Z,"After upgrading to 6.1.32, machine folder shares started showing corruption when being written to. Also happens in 6.1.34. Happens on new install of ubuntu 22.04 as guest on ubuntu 22.04 host.",illk
20980,"VM launch failed when ""Virtual Machine Platform"" (WSL2/WSA) is enabled",Windows,Windows,VirtualBox 6.1.34,2022-06-12T15:33:50Z,2022-06-12T15:33:50Z,"In VirtualBox version before 6.1.28, there is a problem that once a feature of Windows named ""Virtual Machine Platform"" is enabled, VMs will get stuck when launching without showing anyting. And then in version 6.1.30, this problem has been soved. There is an entry in the changelog: ""Fixed 6.1.28 regression preventing VMs starting when using Hyper-V mode on Windows 10"". But now in Version 6.1.32 and 6.1.34, this problem appears again. In other words, any Windows features relies on ""Virtual Machine Platform"", such as WSL2 or WSA, can't work together with VirtualBox version 6.1.32 or later.",SolAbc
20983,Will crash everytime after WIFI router rebooted.,Windows,Windows,VirtualBox 6.1.32,2022-06-13T20:29:27Z,2022-06-13T20:29:27Z,"VBOX will always crash and exit with ""Application Error"" after WIFI router rebooted, don't know why still, hope you can fix it soon, thanks.",gvvice
20984,Windows 10 remote desktop connection problem,Windows,Windows,VirtualBox 6.1.34,2022-06-13T23:08:39Z,2022-06-13T23:08:39Z,"After installing Windows 10 in a virtual machine
with VBoxWindowsAdditions installed, the remote desktop client in Windows does not want to establish a connection

when VBoxWindowsAdditions is removed from the system in the virtual machine, it connects to the remote desktop


Tested on 2 Windows PCs and both Windows 10 PCs


The problem is with VBoxWindowsAdditions on windows 10 in a virtual machine",Mateusz Woźniakowski
20987,Drag and Drop not working windows host and windows guest,Windows,Windows,VirtualBox 6.1.34,2022-06-14T17:02:47Z,2022-06-14T17:02:47Z,"Drag and drop isn't working. Checked for Guest Addition installed, DnD is enabled. Looks like it wants to work from guest to host but file isn't transferred. DnD isn't even attempted or allowed from Host to Guest.",Lost_Developer
20202,"Win10 6.1.18 host hanging during guest startup / pausing / shutdown, excessive disk read seen",Windows,all,VirtualBox 6.1.18,2022-06-16T01:16:21Z,2022-06-16T01:16:21Z,"When I upgrade from 6.1.16 on win10 to 6.1.18, 6.1.19-142777, or 6.1.97-142300 then my Linux and Win10 guests stop responding for a while during startup, shutdown and every time the VM is Paused.

During the entirity of the time the VM is not responding, Task Manager on the host shows Disk reads for the VirtualBox process jump to 600MBytes/sec. Writes stay at close to zero.   The duration of the non-responsiveness when Pausing both tested VMs corresponds with the size of the VM.  

IE every time I Pause the Ubuntu Linux guest, it take 15 seconds of reading @ 600MB/sec to Puase, while the VM size is ~=9GB.   Likewise it takes ~50 seconds to Pause my ~30GB Win10 VM.

From observing the Disk status on Task Manager, whatever triggers the hang/reads seems to happen 2-3 times during VM start up and 1-2 times during shutdown.

vbox.log on 6.1.18 (see attached) shows entries like:

- AsyncCompletion: Task 0x0000000762df00 completed after 16 seconds

- VD#0: Aborted read (0 bytes left) returned rc=VERR_PDM_MEDIAEX_IOREQ_CANCELED

However, during pausing of the VM no errors are seen in the log file - just that PDMR3Suspend took 15 seconds instead of 50 milliseconds.

The Ubuntu guest sometimes has a console message about disk that I couldn't capture.  One boot it came up with / readonly due to needing fs check.

I don't see the same issue occur using 6.1.18 on Win8.1.  It pauses (in well under 1 second), boots and shuts down swiftly as expected with minimum disk reads.
",Grrrrrrr
20991,Unable To Insert Guest Additional CD Image,Mac OS X,Windows,VirtualBox 6.1.34,2022-06-16T20:28:48Z,2022-06-16T20:28:48Z,"1. I have checked the ""Bidirectional"" for clipboard and drag, but neither of them work.
2. Unable To Insert Guest Additional CD Image
3. When I checked the ""share folder settings"" , it comes to this:
""The Virtua Box Guest Additions do not appear to be available on this virtual machine, and
shared folders cannot be used without them. To use shared folders inside the virtual
machine, please install the Guest Additions if they are not installed, or re-install them if
they are not working correctly, by selecting Insert Guest Additions CD image from the
Devices menu. If they are installed but the machine is not yet fully started then shared
folders will be available once it is.""",HerrHuang
20994,PXE UNDI driver transmit seems to be mapping existing transmit buffer instead of making a copy,Linux,other,VirtualBox 6.1.34,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
20997,Scancode returned by int15h call in BIOS keyboard handler(int09h) is ignored.,Linux,other,VirtualBox 5.2.34,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
20909,Clipboard exchange between Devua host and Windows guest stopped working,Linux,Windows,VirtualBox 6.1.32,2022-06-21T14:56:39Z,2022-06-21T14:56:39Z,"For unknown reasons, the exchange of data via '''clipboard''' stopped working some time ago.

The host is (uname -a):  
''Linux Archimedes 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux''

The guest is (MS Windows 10):  
''Windows 10 pro 64bit''

",Joerg Schiermeier
21001,la instalacion viene rota,Windows,other,VirtualBox 6.1.32,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
21002,Better synchronisation between VboxManage CLI and GUI,other,other,VirtualBox 6.1.32,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
19663,VBox on Windows 10 Pro: Dialog boxes too big for screen,Windows,all,VirtualBox 6.1.10,2022-06-22T08:34:13Z,2022-06-22T08:34:13Z,"The dialog windows for VBox running on Windows 10 Pro (Lenovo T480 ThinkPad) overflow the screen and cannot be resized because the lower corners for resizing cannot be accessed.

Windows 10 Pro is set with defaults:
Display resolution: 1920 x 1080 (recommended)
Scale and layout: 150% (recommended)

Temporary solution to the problem is to change scale and layout to 125%; however, at that point the dialog box text becomes virtual unreadable.

Ideally, VBox should set a size limit on the dialog windows or allow resize from the upper corners as well as the lower.

Attachments are screen shots showing the original problem and the dialog window after adjusting windows screen setting.
",husbear
21003,Dialogs don't fit in 1366x768 screen,Linux,all,VirtualBox 6.1.32,2022-06-22T08:38:02Z,2022-06-22T08:38:02Z,Dialogs don't fit in my laptop's screen and I don't see the buttons.,paaguti-u
21005,Only reserve needed RAM,Windows,Windows,VirtualBox 6.1.34,2022-06-23T09:57:38Z,2022-06-23T09:57:38Z,"When VirtualBox 6.1.34 is configured On Windows 10 host, the amount of memory reserved is specified in the settings. And this amount of memory is reserved on the host by the VM when launched.

Would it be possible change the way this setting works, to define a MAX amount of memory available to the VM, and only reserve on-the-fly onto the host the real needed memory when the VM is running ?

In the way, you can launch without trouble on a 64 Gb system 10 (for example) VM that could use each one MAX 16 Gb of memory, if all of these VM only use less than 64 Gb (or better 32 Gb) of RAM in total.",Shine
21006,DHCP provides wrong DNS server address if DNS server address is not requested,other,other,VirtualBox 6.1.34,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
21007,Linux Guest / No Audio in VBox >= 6.1.24,Windows,Linux,VirtualBox 6.1.24,2022-06-24T15:12:55Z,2022-06-24T15:12:55Z,"When using VirtualBox >= 6.1.24 (Windows 10 host, Linux Mint Mate 20.2 guest), audio output does not work. It works with VirtualBox <= 6.1.22.

Audio players, video players, browsers, all seemingly work as intended (e.g., video is shown), just no sound.

I tried the following fix: added the line ""options snd-intel8x0 ac97_clock=48000"" to the file ""/etc/modprobe.d/alsa-base.conf"" .

This brought partial improvements: Video is now played with sound -- no matter whether from the internet or my own local .mp4 files. The test ""aplay /usr/share/sounds/alsa/Front_Center.wav"" works. However, my own .mp3 and .wav files, ripped from CD, still don't produce any output.

I also noticed that when I do ""aplay /usr/share/sounds/alsa/Front_Center.wav"" and immediately interrupt it with ctrl-z, audio output ''does'' work. So it seems this aplay provides some initializations that normally are missing.


Attached two log files: One before applying the above-mentioned fix, one after. There are Audio errors in there; however, I have no idea what can be done about them.",aabb
20996,No guest connection with bridged adapter,Mac OS X,Linux,VirtualBox 6.1.34,2022-06-24T17:02:33Z,2022-06-24T17:02:33Z,"I recently upgraded my iMac to Monterey 12.4 and updated VBox to 6.1.14.

I've noticed that I'm not able to connect a Linux guest I had running in Catalina with a bridged adapter. It seems to try to connect but it doesn't work at all. (I tried to change the adapter too and MAC address but no success so far.)

NAT with port-forwarding works well.",rpijoan_lsw
20626,VboxManage Error: Code E_ACCESSDENIED (0x80070005) - Access denied,Mac OS X,all,VirtualBox 6.1.28,2022-06-26T06:16:22Z,2022-06-26T06:16:22Z,"Hi

When I attempt to run the following command:

VBoxManage hostonlyif ipconfig vboxnet0 --ip 172.28.128.1 --netmask 255.255.255.0

I got the message:

""VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)""

I downgraded to 6.1.26 version and it is working fine, as it is expected.

My host operative system is MacOS Big Sur

Thanks
",hesevo
21009,macos 6.1.34 cannot change a static IP address in host-only mode,other,other,VirtualBox 6.1.32,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
21008,"""Enable nested virtualization"" button is bugged",Windows,all,VirtualBox 6.1.34,2022-06-26T16:48:34Z,2022-06-26T16:48:34Z,"I downloaded and installed last VirtualBox version for Windows: 6.1.34 r150636 (Qt5.6.2). 
I ran a VM. Then I wanted to turn on nested virtualization in CPU's options, but the button was disabled (see screenshot attached).
I have AMD Ryzen 5600x CPU and SMV is enabled in UEFI options.

I managed to figure out the problem spending some time on this: I used the console tool.
This command works correctly:
''VBoxManage.exe modifyvm ""test"" --nested-hw-virt on''
The checkbox becomes being checked after that and nested virt is turned on.
If I uncheck the checkbox again, it becomes inactive again.

Please, fix the checkbox.
I didn't notice the issue with the other checkboxes.
",IL
21010,mouse sluggish,Windows,Windows,VirtualBox 6.1.32,2022-06-26T23:03:10Z,2022-06-26T23:03:10Z,I have windows 10 on my main pc and windows 7 on vb. When I click on something my mouse gets sluggish and you can actually see where the arrow is through out the movement. I haven't been able to find a work around. ,novalore40
21011,guestcontrol in terminated state right after using it on a just restored online snapshot,Windows,Windows,VirtualBox 6.1.32,2022-06-28T12:33:40Z,2022-06-28T12:33:40Z,"It seems that the guestcontrol interface goes into terminating state, right after an online snapshot has been restored of a VM (windows 10 image).

This is a problem I detected on a VM with 6.1.32 vbox guest additions installed. This problem is not present on a VM with 6.0.4 vbox guest additions installed.

Steps to reproduce:
{{{
1) load OVA (win10 OVA in my case)
2) start VM and create online snapshot
3) poweroff VM
4) restore online snapshot taken in step 2
5) start VM, now the VM will jumpstart into the (online) machine state as saved in step 2
6) execute a guestcontrol command from the host immediately after step 5
}}}

After step 6, the guestcontrol command returns with this kind of error:
""VBoxManage.exe: error: Error starting guest session (current status is: terminated)""

The best way to reproduce the error is to automate the steps as it seems some race condition being the rootcause here. These were the simple steps I had in my batch script to reproduce the issue:

{{{
@echo off

set VM_NAME=win10_10.0.17_clean

echo restore snapshot on %VM_NAME%
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" snapshot %VM_NAME% restore ""online_snapshot""

echo start VM %VM_NAME%
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" startvm %VM_NAME%

rem echo zzzzz
rem sleep 1

echo execute command via guest control interface
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" guestcontrol %VM_NAME% run --putenv ""USERNAME=user"" --username user --password user  --wait-stdout --wait-stderr --timeout 600000 cmd.exe -- /C ipconfig
}}}

Executing this sequence on a VM with 6.1.32 vbox guest additions results in the mentioned 'terminated' state of the guestcontrol interface. There is not other way to get out of that, by just rebooting the VM. Otherwise, the guestcontrol interface remains in 'terminated' state.

If there is tiny sleep between step 5 & 6 (as can also be seen in the script) the issue is not there, and the command is executed succesfully.

So it seems some sort of race condition.

I have attached some logging. You will see that whenever the issue is there the logs show 'VERR_NOT_FOUND' errors:

NOK -->
{{{
00:00:09.268742 VMMDev: Guest Log: 14:01:20.520064 main     VBoxService 6.1.32 r149290 (verbosity: 0) win.amd64 (Jan 13 2022 19:13:21) release log
00:00:09.268766 VMMDev: Guest Log: 14:01:20.520064 main     Log opened 2022-06-27T14:01:20.520064800Z
00:00:09.268834 VMMDev: Guest Log: 14:01:20.522599 main     OS Product: Windows 10
00:00:09.268864 VMMDev: Guest Log: 14:01:20.522599 main     OS Release: 10.0.17763
00:00:09.268919 VMMDev: Guest Log: 14:01:20.522696 main     OS Service Pack: 
00:00:09.268946 VMMDev: Guest Log: 14:01:20.522696 main     Executable: C:\Windows\System32\VBoxService.exe
00:00:09.268953 VMMDev: Guest Log: 14:01:20.522696 main     Process ID: 5272
00:00:09.268957 VMMDev: Guest Log: 14:01:20.522696 main     Package type: WINDOWS_64BITS_GENERIC
00:00:09.268983 VMMDev: Guest Log: 14:01:20.522696 main     Hi, this is guest session ID=1
00:00:09.269316 VMMDev: Guest Log: 14:01:20.523084 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:09.269585 VMMDev: Guest Log: 14:01:20.523084 main     Error: Failed to accept session 57 (client ID 1): VERR_NOT_FOUND
00:00:09.269628 VMMDev: Guest Log: 14:01:20.523084 main     Error: Setting message filterAdd=0x1 failed with rc=VERR_NOT_FOUND
}}}

In the VM with guest additions 6.0.4 these errors do not pop up and the logs look like this:
{{{
00:00:10.154777 VMMDev: Guest Log: 11:24:33.124468 main     VBoxService 6.0.4 r128413 (verbosity: 0) win.amd64 (Jan 25 2019 18:38:16) release log
00:00:10.154798 VMMDev: Guest Log: 11:24:33.124468 main     Log opened 2022-06-28T11:24:33.124468000Z
00:00:10.154834 VMMDev: Guest Log: 11:24:33.124468 main     OS Product: Windows 10
00:00:10.154862 VMMDev: Guest Log: 11:24:33.124468 main     OS Release: 10.0.17763
00:00:10.154888 VMMDev: Guest Log: 11:24:33.124468 main     OS Service Pack: 
00:00:10.154915 VMMDev: Guest Log: 11:24:33.124468 main     Executable: C:\Windows\System32\VBoxService.exe
00:00:10.154923 VMMDev: Guest Log: 11:24:33.124468 main     Process ID: 5212
00:00:10.154928 VMMDev: Guest Log: 11:24:33.124468 main     Package type: WINDOWS_64BITS_GENERIC
00:00:10.154957 VMMDev: Guest Log: 11:24:33.124468 main     Hi, this is guest session ID=1
00:00:10.155536 RTC: period=0x10 (16) 2048 Hz
00:00:10.155670 VMMDev: Guest Log: 11:24:33.140222 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:10.171222 RTC: period=0x10 (16) 2048 Hz
00:00:10.186838 RTC: period=0x10 (16) 2048 Hz
00:00:10.188166 VMMDev: Guest Log: 11:24:33.171524 main     Session 1 is about to close ...
00:00:10.188261 VMMDev: Guest Log: 11:24:33.171524 main     Stopping all guest processes ...
00:00:10.188293 VMMDev: Guest Log: 11:24:33.171524 main     Closing all guest files ...
00:00:10.188324 VMMDev: Guest Log: 11:24:33.171524 main     Session 1 ended

}}}

For reproduction of the issue I am using Vbox version 6.1.32 with a VM using guest additions 6.1.32.",Mayhem
20986,Windows Guest Additions cause Linux host to crash,Linux,Windows,VirtualBox 6.1.34,2022-06-28T19:47:36Z,2022-06-28T19:47:36Z,"When I install Guest Additions on my clean-build Windows 10 guest, the host crashes when the guest boots (approx. 5s after the windows logon screen appears).

Host OS: Oracle Linux 8.5, kernel: 5.4.17-2136.306.1.3.el8uek.x86_64
Guest OS: Windows 10 Pro 21H2 (19044.1708)

The guest is stable without GA installed and the host also runs a number of Linux guests with GA installed with no issue. Neither the host nor Linux guests have X installed.

I have tried the following config changes for the Windows guest but these do not resolve the problem:
* Use graphicscontroller VBoxVGA
* Use graphicscontroller VBoxSVGA
* Use mouse ps2
* Use BIOS firmware
* Disable USB
* Disable audio
* Disable hpet
* Disable vrde

Configuration below, log of post-install boot attached:

{{{
#!div style=""font-size: 80%""
Code highlighting:
  {{{#!python
  Name:                        WindowsTest
  Groups:                      /Test
  Guest OS:                    Windows 10 (64-bit)
  UUID:                        86d3768a-e344-4edd-b21c-3fb816ebe87d
  Config file:                 /vm/Test/WindowsTest/WindowsTest.vbox
  Snapshot folder:             /vm/Test/WindowsTest/Snapshots
  Log folder:                  /vm/Test/WindowsTest/Logs
  Hardware UUID:               86d3768a-e344-4edd-b21c-3fb816ebe87d
  Memory size:                 8192MB
  Page Fusion:                 enabled
  VRAM size:                   128MB
  CPU exec cap:                100%
  HPET:                        enabled
  CPUProfile:                  host
  Chipset:                     piix3
  Firmware:                    EFI
  Number of CPUs:              2
  PAE:                         enabled
  Long Mode:                   enabled
  Triple Fault Reset:          disabled
  APIC:                        enabled
  X2APIC:                      enabled
  Nested VT-x/AMD-V:           disabled
  CPUID Portability Level:     0
  CPUID overrides:             None
  Boot menu mode:              message and menu
  Boot Device 1:               HardDisk
  Boot Device 2:               DVD
  Boot Device 3:               Not Assigned
  Boot Device 4:               Not Assigned
  ACPI:                        enabled
  IOAPIC:                      enabled
  BIOS APIC mode:              APIC
  Time offset:                 0ms
  BIOS NVRAM File:             /vm/Test/WindowsTest/WindowsTest.nvram
  RTC:                         local time
  Hardware Virtualization:     enabled
  Nested Paging:               enabled
  Large Pages:                 enabled
  VT-x VPID:                   enabled
  VT-x Unrestricted Exec.:     enabled
  Paravirt. Provider:          Default
  Effective Paravirt. Prov.:   HyperV
  State:                       running (since 2022-06-14T10:49:28.498000000)
  Graphics Controller:         VBoxSVGA
  Monitor count:               1
  3D Acceleration:             disabled
  2D Video Acceleration:       disabled
  Teleporter Enabled:          disabled
  Teleporter Port:             0
  Teleporter Address:
  Teleporter Password:
  Tracing Enabled:             disabled
  Allow Tracing to Access VM:  disabled
  Tracing Configuration:
  Autostart Enabled:           disabled
  Autostart Delay:             0
  Default Frontend:            headless
  VM process priority:         default
  Storage Controller Name (0):            SATA
  Storage Controller Type (0):            IntelAhci
  Storage Controller Instance Number (0): 0
  Storage Controller Max Port Count (0):  30
  Storage Controller Port Count (0):      4
  Storage Controller Bootable (0):        on
  SATA (0, 0): /vm/Test/WindowsTest/Snapshots/{3169be53-ec9e-418e-b4bc-dca229bb8816}.vdi (UUID: 3169be53-ec9e-418e-b4bc-dca229bb8816)
  SATA (3, 0): Empty
  NIC 1:                       MAC: 08002727E34F, Attachment: Bridged Interface 'enp10s0f0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
  NIC 2:                       disabled
  NIC 3:                       disabled
  NIC 4:                       disabled
  NIC 5:                       disabled
  NIC 6:                       disabled
  NIC 7:                       disabled
  NIC 8:                       disabled
  Pointing Device:             USB Tablet
  Keyboard Device:             PS/2 Keyboard
  UART 1:                      disabled
  UART 2:                      disabled
  UART 3:                      disabled
  UART 4:                      disabled
  LPT 1:                       disabled
  LPT 2:                       disabled
  Audio:                       enabled (Driver: ALSA, Controller: HDA, Codec: STAC9221)
  Audio playback:              enabled
  Audio capture:               disabled
  Clipboard Mode:              disabled
  Drag and drop Mode:          disabled
  Session name:                headless
  Video mode:                  1024x768x32 at 0,0 enabled
  VRDE:                        enabled (Address 192.168.1.1, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
  VRDE port:                   3389
  Video redirection:           disabled
  VRDE property               : TCP/Ports  = ""3389""
  VRDE property               : TCP/Address = ""192.168.1.1""
  VRDE property               : VideoChannel/Enabled = <not set>
  VRDE property               : VideoChannel/Quality = <not set>
  VRDE property               : VideoChannel/DownscaleProtection = <not set>
  VRDE property               : Client/DisableDisplay = <not set>
  VRDE property               : Client/DisableInput = <not set>
  VRDE property               : Client/DisableAudio = <not set>
  VRDE property               : Client/DisableUSB = <not set>
  VRDE property               : Client/DisableClipboard = <not set>
  VRDE property               : Client/DisableUpstreamAudio = <not set>
  VRDE property               : Client/DisableRDPDR = <not set>
  VRDE property               : H3DRedirect/Enabled = <not set>
  VRDE property               : Security/Method = <not set>
  VRDE property               : Security/ServerCertificate = <not set>
  VRDE property               : Security/ServerPrivateKey = <not set>
  VRDE property               : Security/CACertificate = <not set>
  VRDE property               : Audio/RateCorrectionMode = <not set>
  VRDE property               : Audio/LogPath = <not set>
  OHCI USB:                    disabled
  EHCI USB:                    disabled
  xHCI USB:                    enabled

  USB Device Filters:

  <none>

  Available remote USB devices:

  <none>

  Currently Attached USB Devices:

  <none>

  Bandwidth groups:  <none>

  Shared folders:<none>

  VRDE Connection:             not active
  Clients so far:              0

  Capturing:                   not active
  Capture audio:               not active
  Capture screens:             0
  Capture file:                /vm/Test/WindowsTest/WindowsTest.webm
  Capture dimensions:          1024x768
  Capture rate:                512kbps
  Capture FPS:                 25kbps
  Capture options:             ac_enabled=false

  Guest:

  Configured memory balloon size: 0MB
  OS type:                     Windows10_64
  Additions run level:         0

  Guest Facilities:

  No active facilities.

  Snapshots:

   Name: 220613 Clean (UUID: 0f5525d8-e007-47f4-8669-1925a2d396ac) *
  }}}
}}}",techpost
20628,Windows: Guest Additions installation might fail due to missing certificate,all,Windows,VirtualBox 6.1.28,2022-07-01T18:35:31Z,2022-07-01T18:35:31Z,"When I tried to install the Guest Additions on a Windows Server 2022 guest that couldn’t reach the Internet, the installation failed with the following messages in the ”Oracle VM VirtualBox Guest Additions 6.1.28 Setup” window:

{{{
Installing guest driver ...
Executing: ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" dri...
Installing driver ...
INF-File: C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf
(1) ENTER:  DriverPackageInstallW
(1) RETURN: DriverPackageInstallW  (0xE0000247)
ERROR: Adding driver to the driver store failed!!
Execution returned exit code:  2
Error excuting """"C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe...
}}}

I found that the Oracle certificate that had been used to sign the Guest Additions device drivers, security catalog files, and so on, has a certification path for which the only trusted root certificate, in a new installation of Windows Server 2022, is a DigiCert Assured ID Root CA certificate signed by Microsoft. That root certificate expired on April 15, 2021, as described in this Microsoft document:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates

If the guest had been able to reach the Internet, I think the Automatic Root Certificates Update feature of Windows would have installed a better root certificate automatically. This guest had to remain offline, so I worked around the problem by installing an unexpired version of the DigiCert CA certificate into the Local Machine/Trusted Root Certification Authorities store, as I described in the forum:

https://forums.virtualbox.org/viewtopic.php?f=1&t=104204

The certificate I installed is:

https://cacerts.digicert.com/DigiCertAssuredIDRootCA.crt

After this, when I ran the Guest Additions installation again, it was successful.

For reference, I installed Windows Server 2022 from the following image, published on visualstudio.com: en-us_windows_server_version_2022_updated_october_2021_x64_dvd_b6e25591.iso

If it’s not feasible to fix this problem by signing the Guest Additions using a certificate for which a trusted, unexpired root certificate exists by default in all Windows installations, then I’d suggest including a copy of the DigiCert certificate with the Guest Additions and prompting the user to install it, if needed.

This shouldn’t be done silently, by the way: I’ve used VirtualBox to investigate other certificate-related problems like this one, and having any non-default certificate appear on its own would be unfortunate.",w16r
20794,Mouse (in both guest and host) behaves strangely when captured.,Windows,Windows,VirtualBox 6.1.32,2022-07-02T07:27:42Z,2022-07-02T07:27:42Z,"This bug is new to version 6.x (not sure the exact version it started in, as I just upgraded to 6.1.32 from a 5.x version a few days ago). Also, this bug only happens when using mouse capture (not when using mouse integration). I don't think it's dependent on the guest OS, as it has an impact on the host mouse cursor as well as the guest, but it may be dependent on the host OS (not sure if Linux version of VBox has this bug, as my PC only has Windows on it). It also doesn't matter if it's using capture instead of integration due to Guest Additions not being installed, or due to the mouse integration part of Guest Additions being manually disabled.

The bug causes the the host mouse cursor to be locked into a rectangular region of the screen, which is located in the upper-left hand corner of the host computer screen. It doesn't matter where the guest window is. The locked in rectangle is always in the upper-left corner of the host screen. If you use the mouse to try scroll the cursor out it wraps around.

On the guest side, the moment you move the mouse after capturing the mouse, the guest mouse cursor completely disappears. This aspect of the bug may be dependent on the guest OS, but I haven't tried it in any guest OS other than Windows, so I can't verify this.

As I don't have technical knowledge of the internals of VirtualBox, I don't know what component is responsible for this bug, so I have left that set to ""other"" on this bug report form.

I've attached a video I recorded of my screen using my cellphone camera showing this issue. It shows how it only has an impact when mouse capture is being used, by running an OS with Guest Additions with mouse integration, and then I disable the integration and let the mouse get captured, where the bug then becomes immediately obvious.",Ben321
21015,virtualbox does not load audio driver in guest win 10,Linux,Windows,VirtualBox 6.1.34,2022-07-02T21:34:19Z,2022-07-02T21:34:19Z,"virtualbox does not load audio driver in guest win 10

Host: Ubuntu Mate 22.04 x64
Guest: Windows 10 Pro x64 21H2 19044.1766

",mrvst
20903,[feature request][Windows] embedding a manifest into the exe/dll,Windows,all,VirtualBox 6.1.32,2022-07-05T20:13:43Z,2022-07-05T20:13:43Z,"Windows Host:  
none of the binaries (exe/dll) include any manifest.

I've done some testing, with a generic manifest I've suited for all of the files,  
with 'compatibility' for running the app outside of Windows 10 vista virtualization, 'DPI awareness' and the text rendering was amazingly crispy, and 'segmented heap' which seems to improve the program stack handling. I even through in 'long-path awareness' just because I've could.

normally I would patched the embedded (resource-24),  
but it seems that Windows Defender don't like me to do that on signed programs, 

so I've just placed a copy of a '.manifest' for each of the files in c:\Program Files\Oracle\VirtualBox (for example 'VirtualBox.exe.manifest') using 
https://github.com/eladkarako/manifest/blob/master/example_manifests/generic.manifest  

and it seems to do the job. 

I did had to apply this registry patch to make it work,  

{{{
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
""PreferExternalManifest""=dword:00000001
}}}

still, runs fine.


I'm still testing the overall performances,  
but I can say the GUI is super clear and sharp,  
I'm using a 150% DPI on my screen, which always seems to show things a bit blurry. and that fixed it completely, the controls seems to keep their place correctly (sometimes DPI awareness makes controls leak their position).

using the new Windows 10 segmented heap seems to help with memory allocation somewhat, but I'm still stress testing.

as for long-path awareness,  
I do have a registry patch to opt-in the feature as explained in:  

https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd#enable-long-paths-in-windows-10-version-1607-and-later

but I don't have any machines on an especially long paths.

however, I know it might help with machines placed on quirky remote locations as well. 


I strongly suggest applying this nice and easy (no actual code modification is required) fix, the results are amazing (at least as for memory consumption with the segmented heap and GUI crispiness).
",Elad Karako
20999,Ubuntu 22.04 freezes - Windows 11,Windows,Linux,VirtualBox 6.1.32,2022-07-09T23:40:51Z,2022-07-09T23:40:51Z,"I have windows 11, and I downloaded virtualbox 6.1 and installed Ubuntu 22 04. I followd this tutorial (https://www.youtube.com/watch?v=EQy9AUVuyF0&t=1s) step by step.

Ubuntu finished installation without any issues, but when I try to run it, it seems to get stuck. A snapshot is visible at (https://askubuntu.com/questions/1415045/ubuntu-22-04-seems-to-freeze-in-virtualbox-6-1-on-windows-11)

I have tried restarting my computer, but nothing seems to work. Can anyone help with the solution? Thanks in advance.

",user17302
21019,VirtualBox 6.1.34a causing BSOD when plugging in ST-LINK/V2,Windows,Linux,VirtualBox 6.1.34,2022-07-10T03:06:11Z,2022-07-10T03:06:11Z,"Hello, I am attempting to connect an LPC1114 to an Ubuntu 18.04.6 VM running on VirtualBox 6.1.34a via an ST-LINK/V2. Shortly after connecting the device and adding it to the Ubuntu VM, my personal machine experienced a BSOD which threw PNP_DETECTED_FATAL_ERROR (ca). 

This BSOD recurred 2 more times, only when VirtualBox was running and the device was plugged in simultaneously, the BSOD did not occur when either event happened individually.

Taking a look at the minidump, it seems IoGetDevicePropertyData and VBoxUSBMon have something to do with it. Attached are the relevant minidump and VM log.",camcom
21021,VBoxTray *crash* on virtual screen resize.,Windows,Windows,VirtualBox 6.1.34,2022-07-10T18:00:15Z,2022-07-10T18:00:15Z,"'''Error:''' VBoxTray.exe access violation (0xc0000005), Address: 0x004123aa

'''Guest:''' Windows NT 4.0 SP6a

'''Configuration:'''
* virtual screen: 1152×864, true color
* VM: View | Auto-resize guest display = disabled

'''Steps to reproduce:'''
* VM: View | Virtual screen 1 | Resize to 800×600",drwtsn32
20958,No Solaris desktop keyboard or mouse with mounted ISO,Windows,Solaris,VirtualBox 6.1.34,2022-07-11T11:27:43Z,2022-07-11T11:27:43Z,"'''Successfully replicated in Windows 10 and Oracle Linux 7.9 hosts.'''
If an ISO is mounted before starting a Solaris 11 VM in desktop mode the keyboard and mouse are not usable. This occurs regardless of whether the ISO is VirtualBoxGuest, boot, repo, or other. If the ISO is disconnected and then the VM started it can be attached an used. This appears to only occur with Solaris 11, currently using the CBE. Have tried multiple rebuilds using both the release repository and the repo created from the downloadable zip files. May somehow be related to the guest extensions not remaining active. Had to re-install extension on both Windows and Linux hosts after OS updates.",spbarrett
4087,Multimedia keys not passed through to guest,Windows,Linux,VirtualBox 2.2.2,2022-07-15T10:43:12Z,2022-07-15T10:43:12Z,"I have a Cherry eVolution STREAM keyboard. The following buttons are not passed through to the guest when pressed:

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

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

The host is Vista Home Basic x64. The guest is Debian using Linux 2.6.26.",Sam Morris
21023,Trying to run bluestacks in  vbox - cant increase cpu cores inside my bluestacks,Windows,other,VirtualBox 6.1.14,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
21022,unable paste screenshot to windows guest,Linux,Windows,VirtualBox 6.1.32,2022-07-18T08:50:47Z,2022-07-18T08:50:47Z,"host: ubuntu22.04
guest: windows10

unable to paste screenshot to windows, which is all good on ubuntu21.10 host and windows10 guest, I tried all the solutions I can find in google, 
still not working

sometimes, can't paste plain text too",walkerjun
21025,Screen lock in Windows 10 Host makes the Linux Guest unresponsive (regression),Windows,Linux,VirtualBox 6.1.36,2022-07-20T10:59:23Z,2022-07-20T10:59:23Z,"After upgrading from 6.1.30 to 6.1.34, I've started to notice that my Centos 7.8 Guest goes unresponsive on regular basis.

I've been able to pinpoint it to the screen lock in the Windows 10 21H2 Host. Whenever I unlock the screen the VBoxHeadless.exe process uses 100% of all of the cores available to the Guest machine. Guest is unreachable neither by ssh nor by GUI.

This happens regardless of the graphic display used, and also in the headless start. Also changing hypervisor between the Hyper-V and KVM does not make a difference.

VirtualBox 6.1.36 behaves the same as 6.1.34, however downgrading to the 6.1.30 solves the issue.

Logs do not contain anything except repeating pattern of:
00:02:22.924401 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:24.627881 VMMDev: GuestHeartBeat: Guest is alive (gone 5 713 045 344 ns)
00:03:09.694062 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:15.648850 VMMDev: GuestHeartBeat: Guest is alive (gone 9 990 252 305 ns)
00:03:30.642448 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:30.792413 VMMDev: GuestHeartBeat: Guest is alive (gone 4 159 194 451 ns)
00:03:47.088470 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:52.836984 VMMDev: GuestHeartBeat: Guest is alive (gone 9 762 953 270 ns)
00:03:56.874575 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:57.771949 VMMDev: GuestHeartBeat: Guest is alive (gone 4 934 966 056 ns)
00:04:01.784622 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
",MichalBrz
21026,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,Windows,VirtualBox 6.1.36,2022-07-20T12:29:17Z,2022-07-20T12:29:17Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
20932,Loss of audio-input in Windows10 guests after rebooting guest (from 6.1.28),all,Windows,VirtualBox 6.1.34,2022-07-20T13:29:42Z,2022-07-20T13:29:42Z,"Hello;

Starting with virtualbox 6.1.28 (tested as well on 6.1.30, 32, 34 so far) there is no audio input after rebooting a Windows 10 guest VM. The audio interface is present, but only silence as audio ""in"" after a reboot (audio was present at first boot). Everything was working well with virtualbox 6.1.26 or before.

The problem is easily reproduced at first try on any machine I have (tested several hardware, different sound cards, different CPU architecture amd or intel, different host os : debian 11 or windows). The problem always apear after the first (and any subsequent) reboot of the machine (either user induced, or due to and update or a VM crash).  

Also tested several Windows 10 versions (LTSC ; entreprise ; home), all have the same problem.
Depending on the host, I have tested several drivers (Alsa and PulseAudio on Linux and ""Windows Direct Sound"" on Windows).
The problem is the same if the Guest Additions are installed or Not (therefore, not a problem with the GA).

Please see attached some logs taken with extended audio logs using options ""VBOX_RELEASE_LOG=drv_host_audio.e.l.l2.l3.f+drv_audio.e.l.l2.l3.f+audio_mixer.e.l.l2.l3.f+dev_hda_codec.e.l.l2.l3.f+dev_hda.e.l.l2.l3.f+dev_ac97.e.l.l2.l3.f"" :

File 6.1.30-Win10-NotOK-extended.log showing the problem :
- First test OK at 0:06s line 1445 ""fMuted=true""
- Reboot at 0:41s line 1531
- Second test Not OK after reboot at 0:45s line 1729 ""fMuted=true""

File ""6.1.26-Win10-OK-extended.log"" when everything is working fine with 6.1.26 for reference :
- First test OK at 0:08s. See logs line 1479 ""fMuted=false""
- Reboot at 0:58 line 1559
- Second test OK after reboot at 1:02 line 1794 ""fMuted=false""

Any help would be greatly appreciated :)

Thank you very much in advance !",Nicolas@…
21013,Linux guest additions use 0.06 Hz refresh rate for custom display resolutions,all,Linux,VirtualBox 6.1.34,2022-07-20T15:27:23Z,2022-07-20T15:27:23Z,"This can be reliably be reproduced on any Linux guest:

- Install the guest additions onto a Linux guest (tested with Debian & Fedora guests).
- Make sure the package corresponding to the xf86-video-vmware driver is removed, so that the driver doesn't add the resolutions before VBoxClient itself can (see notes below for more details). (On Debian & derivatives, this can be done via `sudo dpkg -r --force-depends xserver-xorg-video-vmware`.)
- Make sure you've rebooted after doing the above.
- Resize the VBox guest window.
- Run xrandr.
- Observe that any new resolutions added by the guest additions (ending in _vbox) all have a refresh rate of 0.06 Hz:

{{{
$ xrandr
Screen 0: minimum 320 x 200, current 1900 x 1920, maximum 8192 x 8192
Virtual-1 connected primary 1900x1920+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   preferred     60.00 +
   2560x1600     59.99  
   1920x1440     60.00  
[...]
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
   1990x1920_vbox   0.06  
   1860x1920_vbox   0.06  
   1940x1920_vbox   0.06  
   1900x1920_vbox   0.06*
[...]
}}}

This completely breaks the ability to use recent versions of Electron applications w/o xf86-video-vmware, which seem to respect this refresh rate when rendering.

Notes:

- This doesn't occur if xf86-video-vmware is installed because then VBox doesn't add the new resolutions itself: since both VBox & VMware use SVGA, xf86-video-vmware picks up the resize first and adds the resolutions it wants, after which the `VBoxClient --smsvga` sees a matching resolution is already present and does nothing.
- This has been reproduced on multiple different host systems.",refi64
21027,Guru Meditation on installation,Linux,all,VirtualBox 6.1.36,2022-07-21T09:50:16Z,2022-07-21T09:50:16Z,"Hi,

i tried version 6.0, 6.1 from repository and the latest testing 152223 Version. With each i get a error, when i try to install Windows 10 or Kubuntu. See both logs.

Can someone give me a hint, where to search?
",murrcoss
18343,Unable to import OVA with error NS_ERROR_INVALID_ARG,Linux,Linux,VirtualBox 6.0.2,2022-07-23T07:02:26Z,2022-07-23T07:02:26Z,"$ vboxmanage import packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova
{{{
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /var/lib/jenkins/tsenay/packer-core-os-builder/packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova...
OK.
Disks:
  vmdisk1       41943040000     -1      http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized       rhel-75-x86_64-core-os-disk001.vmdk     -1      -1

Virtual system 0:
 0: Suggested OS type: ""RedHat_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""rhel-75-x86_64-core-os""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/home/ldapccs/tsenay/VirtualBox VMs/rhel-75-x86_64-core-os/rhel-75-x86_64-core-os.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/home/ldapccs/tsenay/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Description ""packer-core-os-image Virtual Machine""
    (change with ""--vsys 0 --description <desc>"")
 6: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
 7: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
 8: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 9: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 9 --ignore"")
10: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: Hard disk image: source image=rhel-75-x86_64-core-os-disk001.vmdk, target path=rhel-75-x86_64-core-os-disk001.vmdk, controller=9;channel=0
    (change target path with ""--vsys 0 --unit 11 --disk path"";
    disable with ""--vsys 0 --unit 11 --ignore"")
0%...10%...20%...30%...40%...50%...
Progress state: NS_ERROR_INVALID_ARG
VBoxManage: error: Appliance import failed
VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 957 of file VBoxManageAppliance.cpp
}}}",tsenay
21029,no bidirectional clipboard in windows 11 host / ubuntu 18.04 guest,Windows,Linux,VirtualBox 6.1.36,2022-07-25T15:03:11Z,2022-07-25T15:03:11Z,"Hi, 

I can't remember when this stopped working, just recently upgraded virtualbox and the vbox guest additions, and now I realize this is not working:

 * bidirectional clipboard

Guest Additions:

{{{
systemctl status vboxadd.service
● vboxadd.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.1.36/init/vboxadd; enabled; vendor preset: enabled)
   Active: active (exited) since Fri 2022-07-22 14:47:29 -03; 37min ago
  Process: 643 ExecStart=/opt/VBoxGuestAdditions-6.1.36/init/vboxadd start (code=exited, status=0/SUCCESS)
 Main PID: 643 (code=exited, status=0/SUCCESS)

jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: Starting.
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: VirtualBox Guest Additions kernel modules 6.1.36
jul 22 14:47:28 x1buntu vboxadd[643]: r152435 are
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: already available for kernel 5.4.0-122-generic and
jul 22 14:47:28 x1buntu vboxadd[643]: do not require to be rebuilt.
jul 22 14:47:28 x1buntu useradd[924]: failed adding user 'vboxadd', data deleted
jul 22 14:47:28 x1buntu useradd[925]: failed adding user 'vboxadd', data deleted
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
jul 22 14:47:28 x1buntu vboxadd[643]: the system is restarted
jul 22 14:47:29 x1buntu systemd[1]: Started vboxadd.service.
}}}

Guest OS:

{{{
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic
}}}

Host OS: Windows 11 Pro 21H2 (22000.795), x64",arfe
21035,Upgrading from VirtualBox 6.1.34 to 6.1.36 on Windows results in incorrect drivers,Windows,other,VirtualBox 6.1.36,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
21036,VB Startup after Host Shutdown without VB Guest Shutdown,Windows,Windows,VirtualBox 6.1.36,2022-07-26T15:22:24Z,2022-07-26T15:22:24Z,"VirtualBox doesn't show up after a host shutdown (Start/Shutdown) without VB guest shutdown (VB was running and killed by windows shutdown)

The Windows 11 VM was perfectly running prior to this accidently caused shutdown. 

Host:
  Windows 10 Enterprise / 21H2 / 19044.1826[[BR]]
  AMD Ryzen 9 3950X 16-Core Processor[[BR]]
  RAM 64,0 GB[[BR]]
 
Guest:
  Winwows 11 Professional / latest updates (yesterday)

VB Processes running:
 VBoxSDS.exe: ~ 1.8 MB

 VBoxSVC.exe: continously increasing -> >100GB

 VirtualBox.exe: 6.6 MB 

In task manager one can see continuously increasing memory consumption of VBoxSVC.exe which results in a host crash (in my case at over 100GB (64GB RAM installed)  

",Pigo
21038,6.1.36 regression. Recording VMs audio not working,all,Linux,VirtualBox 6.1.36,2022-07-27T00:17:11Z,2022-07-27T00:17:11Z,"In setting select Display->Recording, audio only and highest quality.
The .webm file is created during run (opening the file is logged correctly).
Once the VM is powered down, the file is erased. Tested on windows and debian host (debian guest).
The webm file length never exceeds a few hundred bytes.
Install .34 again, and all was well again.",KurtMielke
18564,"Graphics performance is absolutely dismal, to the point of unusability",Mac OS X,Linux,VirtualBox 6.0.6,2022-07-27T15:13:06Z,2022-07-27T15:13:06Z,"I use Fedora 29 with the Cinnamon desktop (runs in X, requires 3D acceleration).  I have been having pretty dismal graphics performance, to the point where I have to stop typing and let the application catch up with me so that I can spot stuck keys and dropped keystrokes.  It appears numerous X events get dropped in some fashion; often, my shift key gets stuck, as if the key_release event was missed, but that's not the only key that'll get stuck.  I have the same issue with mouse clicks, too, which makes it a bit difficult to cut and paste text or select options in menus.  For the record, this is a freshly created VM utilizing the VMSVGA driver, scaled by 175%, with 3D acceleration activated; resolution is 1920x1200.  When I upgraded from a 6.0.5 pre-release and updated the guest tools, Cinnamon started complaining about using software rendering, although I can see the vmwgfx and vboxvideo drivers loaded.  If I run glxinfo, I see ""OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)"" in the output.  I've also started to node, with the 6.0.6 release, that the Menu is getting randomly activated, as if I hit the Windows key.

(Host is osX.)",Kevin L Mitchell
20525,High VMM Load on Intel CPUs introduced in 6.1.20,Windows,Windows,VirtualBox 6.1.20,2022-07-27T19:24:30Z,2022-07-27T19:24:30Z,"Beginning in version 6.1.20, and also happening in .22, and .24, there is a significant increased VMM Load reported in the Session Information dialog with hosts running Intel processors when using 2 or more vCPUs, getting progressively worse as the vCPU count is increased up to the recommended threshold shown in the VM Settings dialog.

I reverted to 6.1.18 and confirmed the issue is not present in this version, with low to minimal VMM Load.

I tested and am not seeing the issue on a Ryzen 5 3400G host at this time. I have performed the same test with multiple vCPUs with 6.1.20, and 6.1.24 and the VMM Load is low in all these cases on a Ryzen host.

All hosts tested are running Windows 10 x64. Tested and confirmed issue with Windows 10 x64 and Debian x86-64 guests on Intel 3rd gen Core i5, Core i7 5820K, Xeon E5-1620 v2, and Xeon E5-2620 v4 CPUs.",lbgaus
20957,Latest 6.1.35 Guest additions can not be installed in Windows 7 vms. Cause Bluescreen,Windows,Windows,VirtualBox 6.1.34,2022-07-27T22:23:32Z,2022-07-27T22:23:32Z,Title says it all. If you mount the 6.1.35 revision 151572 iso or the one provided with the 6.1.35 revision 151573 the Windows 7 vm will get a bluescreen. Tested with x86 x64 and Server 2008 R2. Same if you you copy the files to a shared folder any try to install them from there. The exe files seem to trigger it. Installing the 6.1.34 version works.,frg
14253,Default VM Start Method,other,other,VirtualBox 5.0.0,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
20371,Video recording settings not saved,Windows,Linux,VirtualBox 6.1.22,2022-07-28T19:33:56Z,2022-07-28T19:33:56Z,"It seems that video recording settings of VMs are not saved. At least this is true for file path and frame size. Leaving VirtualBox Manager and restarting it, video recording settings are back to default.

In the .vbox file of the VM, I found the entry VideoCapture never reflecting these settings.

Maybe this is related to [ticket:20297], because depending on the modification history of video recording settings I experience the same crash. ",Reiner Brodbeck
20357,VM launch fail on Windows 10 when WSL2 and Docker is enabled,Windows,Linux,VirtualBox 6.1.22,2022-08-01T18:37:28Z,2022-08-01T18:37:28Z,"We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

''WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
''

""Windows Hypervisor Platform"" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM ""Settings - System - Acceleration"" too - OK button remain disabled.

To get VirtualBox VMs running again either ""hypervisorlaunchtype"" must be disabled through Windows Command Prompt with command
{{{
bcdedit /set hypervisorlaunchtype off
}}}
or Docker Desktop must be uninstalled together with ""Windows Hypervisor Platform"", ""Virtual Machine Platform"" and ""Windows Subsystem for Linux"" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:
{{{
Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
}}}",Janis Baumanis
21042,I can't open the app,Windows,Windows,VirtualBox 6.1.36,2022-08-01T19:06:00Z,2022-08-01T19:06:00Z,"So I just tried to install the app but when I try to launch it after installing it it just keeps on the background and it doesnt start up, I tried everything I found on google but noyhing works",ZenZen
21040,VM blocked on humongus amounts of disk read,Windows,Linux,VirtualBox 6.1.36,2022-08-02T12:01:44Z,2022-08-02T12:01:44Z,"Problem occurring since updating to 6.1.36 from 6.1.34

running condition tested for reproduction:
  - on a old windows 10 host install, run old or new Linux guests (both EFI, and non EFI) that were working on 6.1.34
  - on a fresh windows 10 host install (21H2), with the same scenarios.

steps to reproduce:
  - from a system without VirtualBox installed, or with VirtualBox 6.1.34 installed:
    - install or update to 6.1.36,
    - try to run any linux guest

observed behavior:
  - at startup a 19GB vdi guest generates a 100 second read @ 600+ MB/s (so about 60GB read) blocking the guest execution for the whole time,
  - after logging in, a second wave of read is triggered (about 30s, so 20GB), 
  - and on shutdown the read is also triggered for about 90 seconds rendering the whole process very cumbersome and sluggish.
  - note: using the menu to insert guest additions CD also triggers a read freeze.",os19000
20386,Mouse click stops working on host/guest due to window focusOutEvent problem in Qt GUI,Linux,Windows,VirtualBox 6.1.22,2022-08-03T03:01:09Z,2022-08-03T03:01:09Z,"https://forums.virtualbox.org/viewtopic.php?f=7&t=102798

Here's a cut & paste of problem description:

Mouse click stops working on host/guest due to window focusOutEvent problem in Qt GUI

Postby Cryptkeeper » 7. May 2021, 17:37
Hi,

for more than two years now (so probably since VB version 6.0 or so) from time to time I am affected by a very anoying bug. Then mouse clicks stops working on the host and the guest as well. I can still move the mouse pointer but clicks are not recognized anymore. The only solution then is to shut down *all* running guest instances. Then the mouse clicks starts working again.

I am sure it is not a drag and drop problem like in https://www.virtualbox.org/ticket/14743

There will be no entry in the logs, when the bug occurs. It happend very randomly to me but after a while with a screen record I figured out the following steps to reliable reproduce the bug:

1) Click on the taskbar to restore VM window from minimized state
2) Press down the mouse button on the taskbar and keep it pressed
3) Release the mouse button and immediatly press it again
4) Now no further clicks are registered until VM is shut down

(I agree that this looks like a very special and rare circumstance - however I think that this bug is a race condition and as I often switch between different windows with the taskbar I'm hit by it very often.)

Here is a screencast of the bug as GIF: https://s3.gifyu.com/images/vbox-bug.gif

When the bug occurs *xprop* on the hosts exits with the error ""xprop: error: Can't grab the mouse"" - on the guest it just hangs as no click is registered. Also the bug only occurs with the Qt front end of VirtualBox - with the SDL front end I couldn't reproduce the error.

From the steps I assume that the bug is kind of a race condition on the minimize respectively focus out / focus in event of the window. So I tried to build VirtualBox from source and try to trace the bug. And indeed I figured out, that the bug does not occure if I comment out the following 3 lines in the file src/VBox/Frontends/VirtualBox/src/runtime/UIMachineView.cpp.

Code: Select all   Expand view
    void UIMachineView::focusOutEvent(QFocusEvent *pEvent)
    {
        /* If native event filter exists: */
        if (m_pNativeEventFilter)
        {
            /* Uninstall/destroy existing native event filter: */
               
            //qApp->removeNativeEventFilter(m_pNativeEventFilter);
            //delete m_pNativeEventFilter;
            //m_pNativeEventFilter = 0;
        }

        /* Call to base-class: */
        QAbstractScrollArea::focusOutEvent(pEvent);
    }



I tried to dig deeper but I'm kind of stuck. Because I don't know what this native event filter is used for and why it is destroyed on focus out event.

Can anyone help me to debug this further?

Thanks a lot!",Seann
21048,"Honor Windows' ""Automatically hide scroll bars"" setting",Windows,all,VirtualBox 6.1.36,2022-08-04T11:51:50Z,2022-08-04T11:51:50Z,"VirtualBox Manager automatically hides the scroll bar of the VM list and it seems you can't turn this behavior off in preferences. It would be nice if VirtualBox would always show the scroll bar if the user disabled ''Ease of Access'' -> ''Display'' -> ''Automatically hide scroll bars in Windows'' in Windows settings. The corresponding registry value is 
{{{
HKCU\Control Panel\Accessibility\DynamicScrollbars
}}}",hqngl
20939,VBox on Windows 11 kernel panic - unable to sync on every VM,other,other,VirtualBox 6.1.32,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
20504,vboxdrv: linux kernel errors on debug kernel and vbox modules built by akmods,other,other,VirtualBox 6.1.26,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
20879,Error creating a new Host Network Manager,Windows,other,VirtualBox 6.1.32,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
21053,Accidental shutdown click if click on `Machine` guest main menu,other,other,VirtualBox 6.1.36,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
21054,Ability for the guest to write on a online-for-the-host partition,Windows,Linux,VirtualBox 6.1.36,2022-08-08T07:55:31Z,2022-08-08T07:55:31Z,"because as I saw it's read-only .

On my PC's hard disk with Windows 10 Home :

Host : Windows 10 Home

Guests :

firmware-testing-amd64-netinst.iso ( a Debian installer ) : installing  Debian physically on my PC's hard disk dual-boot with Windows 10 Home , everything works except GRUB isn't installed on the original ESP ( EFI system partition ) with EFI\Microsoft\Boot etc .

debian-live-11.4.0-amd64-xfce+nonfree.iso ( a Debian live ) : cannot write e.g. a file on a PC's hard disk partition ( original ESP , C: , D: , Debian partition ( me on ext2 ) ) .

See https://forums.virtualbox.org/viewtopic.php?f=6&t=106689 .

Is it a regression related to https://www.virtualbox.org/ticket/14425 ?",ecccc3
20942,"VirtualBox v6.1.34 shows ""Make sure the kernel module has been loaded successfully"" and VM wont start",other,Windows,VirtualBox 6.1.32,2022-08-08T11:48:52Z,2022-08-08T11:48:52Z,"VM no longer starts after:
- a VirtualBox upgrade
- then a Windows Update

- had VirtualBox-6.1.32-149290-Win.exe installed since 01/31/2022
- On 05/09/2022, I upgraded it with VirtualBox-6.1.34-150636-Win.exe
- VM working perfectly. Saved, or closed and reopened...
- on 05/12/2022, I rebooted windows, and a Windows Update took place.
- Then, VM no longer starts with message:

{{{
VirtualBox - Error In supR1HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3 VERR_OPEN_FAILED (-101) - File/ Device open failed. driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
}}}


I rebooted windows. Same issue.

- I just discovered that downgrading fixed the problem.
I looked in windows update history and saw:
- on 05/11/2022, (one day before my ""Update and restart"" though this one http://support.microsoft.com/kb/890830. Others are too old

Also, working on a professional laptop, with windows administration by our IT team, I saw this notification after the ""update and restart"" of windows (did not have time to screenshot it), it was saying something like ""an administrator has changed the rights on some path...""
Don't know if it helps.

Hardware:
Intel(R) Core(TM) i7-10750H CPU @ 2.60Ghz
64Go
Windows 11 professional
Version 21H2
Build 22000.675
Experience 1000.22000 675.0",Syl20
21044,Virtual Machine does not open VMDK-file from VMWare,other,other,VirtualBox 6.1.36,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
21049,Windows 10 Guest login on Fedora 36 crashes after mouse movement,other,other,VirtualBox 6.1.36,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
21056,[CRITICAL] Network driver causing system crashes on windows 11,Windows,all,VirtualBox 6.1.36,2022-08-08T20:53:39Z,2022-08-08T20:53:39Z,"I'd seen this bug reported in other places, but no currently open tickets mention hard, system-wide crashes. One of them mentions being disconnected from the wifi for a brief time, but this is way worse than just that.

I hadn't even used VirtualBox at all since my computer started up, but any time I try to load more intensive websites on my host operating system (completely independent from VB I might add), it has about a 1 in 10 chance of crashing my entire OS. Straight to black screen, computer shuts off and reboots.

I only use virtualbox once in a while, so imagine my surprise when I started investigating why my computer keeps crashing only to find that this event was found before every crash. Initially I thought that was a bug in this version of the software and updated to 6.1.36, but nothing changed on that front. 

I love open source projects, but honestly if this isn't fixed soon I may have to switch to a proprietary VM software, simply because I can't leave this installed on my computer if it's going to cause crashes every other day. It didn't used to happen before I updated to the most recent version of windows, but the fact remains that this driver is still the cause of those crashes.

The problem always correlates with an event ""The driver detected an internal driver error on \Device\VBoxNetLwf."" The event has ID 12 and is listed under the keyword ""classic"".",pizzamonkey
21057,Snapshots restore files on Writetrough Disk,Windows,Windows,VirtualBox 6.1.36,2022-08-09T18:50:57Z,2022-08-09T18:50:57Z,"Hello dear support team. My snapshots restore files on Writetrough Disk.
Here my thread on forum https://forums.virtualbox.org/viewtopic.php?f=6&t=106742

I use two VDI on my VM. First VDI: Normal type. Created for system using (OS, applications, system configuration). I want to take snapshots only from Normal disk type.
Second VDI: Write-through type. Created for file storage. I don't want to take snapshot from Write-through disk.
But files are restored on Write-through disk... I do not understand anything.
Please check me step by step. I will try to be as detailed as possible.
1. I created new VM with new VDI (Normal type for system using). Capacity 30GB. Screenshot https://www.dropbox.com/s/gy764nib8kljrdc/Screenshot_8.png?dl=0
2. I created new VDI (Write-through type for file storage). Capacity 50GB. https://www.dropbox.com/s/2g2cfr621yuqo93/Screenshot_12.png?dl=0
3. Check attached to VM disks. https://www.dropbox.com/s/8ospntq1fx4w9l5/Screenshot_16.png?dl=0 second https://www.dropbox.com/s/8zr79tm9zp6a2ny/Screenshot_17.png?dl=0
4. Now I'm install Windows 10 on 30GB disk (Normal type) https://www.dropbox.com/s/g0uk8bkozy51scy/Screenshot_18.png?dl=0
5. Initialization wright-trough disk after Windows installation https://www.dropbox.com/s/0dnlszujxk5akcw/Screenshot_19.png?dl=0
6. Now I have 2 local disk in Windows Explorer https://www.dropbox.com/s/tw8vf0c14dcf18j/Screenshot_22.png?dl=0
Now it will be interesting
7. Create test folders https://www.dropbox.com/s/fhv3vg2x9z4gnhv/Screenshot_23.png?dl=0
8. Take snapshot https://www.dropbox.com/s/ce1x0r39d34ebfy/Screenshot_25.png?dl=0
9. Test folders deleted using SHIFT+DEL https://www.dropbox.com/s/icjf5t3wyjmz4qh/Screenshot_28.png?dl=0
10. Shutting down VM and restore Test 1 snapshot https://www.dropbox.com/s/orv5cr5ijt29v65/Screenshot_31.png?dl=0
I expect to restore test folder on only drive C:\ (Normal type)
11. Why test folder restored on Write-trough disk (E:\)? https://www.dropbox.com/s/edqmh7ojn7ngmbx/Screenshot_33.png?dl=0",CyanCetus
21058,Erro ao inicializar maquina virtual,Windows,Windows,VirtualBox 6.1.36,2022-08-10T13:55:48Z,2022-08-10T13:55:48Z,"Bom dia,

O seguinte erro aparece ao inicializar a maquina virtual.
Falha ao abrir uma sessão para a máquina virtual:
The virtual machine 'VIRT' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)

Já fiz vários testes para sanar o erro, mas sem sucesso, incluindo:
Desinstalar e instalar novamente, atualizar para a ultima versão, desativar Hyper-V do Windows e entre outros básicos. O mais estranho que o erro começou ""do nada"". Podem me ajudar?
",Gugu Aquino
21059,Virtualbox VM crashed while installing Virtualbox Guest Additions in win8.1 guests,Windows,Windows,VirtualBox 6.1.36,2022-08-12T03:48:32Z,2022-08-12T03:48:32Z,"I was installing VB Guest Additions in a Windows 8.1 guest. After a few seconds, when I was prompted to install a video driver in the guest and I clicked ""Yes"", the virtual machine stopped responding and the host prompted a memory error.  Then,I could never again boot the VM using the hard disk because the same error pops up every time.

'''Reproduce'''
1. Create a win8.1 VM
2. Install win8.1.
3. Try to install VBAdditions.

'''Environment'''
Version: VB 6.1.36
Host OS: Windows 11 22H2
Guest OS: Windows 8.1

",fyc
21062,BUG in updating Nat Network configuration: parameter Network CIDR,Linux,Windows,VirtualBox 6.1.36,2022-08-14T19:28:06Z,2022-08-14T19:28:06Z,"Changing the parameter Network CIDR does not affect the correct configuration of the DHCP server active on the NAT network.
The IP address of the DHCP server and the range of addresses served are not updated.

For the walkthrough see my post on Forum

https://forums.virtualbox.org/viewtopic.php?f=7&t=106799 ",sagypt
21063,Windows 98 not running on windows 11,other,other,VirtualBox 6.1.36,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
21064,My virtual machine half screen blank,Windows,other,VirtualBox 6.1.36,2022-08-15T16:03:08Z,2022-08-15T16:03:08Z,"[[Image(https://i.postimg.cc/vTfcBVHY/IMG-20220815-211452.jpg)]]

",Saikat
21068,VM crashes after a while when pressing Tab/Return in terminal,Mac OS X,Linux,VirtualBox 6.1.36,2022-08-16T16:21:56Z,2022-08-16T16:21:56Z,"Hi,

VirtualBox: 6.1.36 r152435 (Qt5.6.3)

I am on an Ubuntu 20.04 VM (running on a macOS host). I turn it on and open up its terminal (bash). After ~10-15 minutes of playing around, I press the tab key (for autocompletion). I've notices this also sometimes happens with the return key in a Find/Replace dialogue in CLion.

The VM freezes so I have to manually shut down.

The same happens when I am in zsh, so it's not the terminal itself.

Could you please help,
Thanks,
Mihai",mihai_mc
21016,"KUbuntu 22.04 jammy host, Virtualbox 6.1.32 Windows guest: copy and paste causes GUI to freeze",Linux,Windows,VirtualBox 6.1.34,2022-08-17T07:26:38Z,2022-08-17T07:26:38Z,"I am running a windows guest in Virtual Box on Kubuntu 22.04 jammy with kernel 5.15.0-27-generic. From time to time I experience different kinds of freezes. Sometimes, when I am in the VM I can contiue to work in the VM, but can't select another window from the host. Sometimes, when I am outside of the VM I can continue to work in all windows of the host, but can't switch back to the guest. In all cases so far I was able to switch to the console (Ctrl-Alt-F2) and back to the GUI. The mouse continues to work.

Often the system went back to normal after waiting for a couple of seconds. But some times, even waiting for 10 minutes, does not solve the problem and the poweroff via the CLI from the console helps: ""VBoxManage controlvm poweroff"".

I had this problem also seldomly on KUbuntu 18.04. It was so rare that I did not bother. Now it is happening more often and I already tried to find a solution via Google.

By now I am quite certain that it is caused by copy-and-paste in the Windows VM and keeping things selected. Especially when working with Excel. This forum post seems to describe the same issue: https://forums.virtualbox.org/viewtopic.php?t=99685

I've also asked on askubuntu: https://askubuntu.com/questions/1406257/kubuntu-22-04-jammy-host-virtualbox-6-1-32-windows-guest-gui-freezes-in-both-d
At the time I thought it might be related to using shared folders, but by now I am quite certain that copy and pasting from Windows to Linux causes the problem.
",cs224
2942,Save state -> Start/resume does not restore window size,other,Windows,VirtualBox 2.1.0,2022-08-17T21:24:04Z,2022-08-17T21:24:04Z,"Problem: When ""auto-resize guest display"" is enabled, a save state -> start/resume 
will not restore the window size but instead use a too small window. 

This is a regression from 1.x to 2.1. 

How to reproduce:

1. Start VM

2. Enable ""auto-resize guest display""

3. Close VM window choosing ""save machine state""

4. Start the VM again

5. While restoring, the VM window has a certain small size (640x480 or so)

6. When the VM is fully restored, the VM window HEIGHT is restored but the 
WIDTH is unchanged from restore operation. In the next moment, the guest 
OS changes its screen size to adopt to the new size. 

Result: Saving the state at a window size of 1600x1200 results in a restored 
window of 640x1200. 

WM is fvwm2. 
WM is unlikely to cause the problem because when ""auto-resize guest display"" is not active, restoring the vM will resize the window corretly to the same size it had when saving the state. ",joseph_
21069,VM crash diuring install lazarus or anower big packageset,Windows,Linux,VirtualBox 6.1.36,2022-08-18T14:01:39Z,2022-08-18T14:01:39Z,"Hello.

BEFORE, latest activity:
I maked before crushes disk shrunked: VBoxManage modifyhd /path/to/VDI/VM.vdi --compact  (path are different, instructions https://askubuntu.com/questions/1092812/zerofree-on-ubuntu-18-04)

then i see excelent resul: VDI file set to 21GB from 500GB 

After somes reboot i try to launth TLauncher und try to install java 8 -- VM crush.
Then i try to install new lazarus - VM crush.  

",Дмитро
20856,Windows Vista Ultimate 64 Bit Guest Additions not working,Windows,Windows,VirtualBox 6.1.32,2022-08-19T03:55:41Z,2022-08-19T03:55:41Z,"I am using Windows Vista Ultimate 64 Bit and I wanted to install Guest Additions so I can use Windows Aero Theme but I get an error when installing Guest Additions. The error says Error excuting (Yes spelled exactly like dat) C:\Program Files\Oracle\VirtualBox Guest Additions\VboxDrvInst.exe 
And I allowed whatever prompt I got.",Aremon
20335,export VM disk image format: vdi instead of vmdk (ova or different VM container format),other,other,VirtualBox 6.1.22,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
21032,Crash on start up,Windows,other,VirtualBox 6.1.36,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
21070,"Linux VMs hang on boot when ""Host Pipe"" Serial Port is enabled and the OS has console=tty[x] set",all,Linux,VirtualBox 6.1.34,2022-08-22T13:19:56Z,2022-08-22T13:19:56Z,"On Linux and Mac Host I'm seeing that Linux VMs hang on boot when a Host Pipe Serial Port is enabled and I have the Linux bootloader set with the console=tty[x] option. The VM hangs until I use a program to connect to this host port at which time the VM will start loading.

However when I tried to replicate this on a Windows host the VM would boot up immediately.",Joshua_VES
16547,Full screen mode only displays on 1 screen,Windows,Windows,VirtualBox 5.1.16,2022-08-22T13:21:46Z,2022-08-22T13:21:46Z,"I've just upgraded to 5.1.16 hoping this problem will be resolved. When running my guest in full screen, it only displays on one of my screens (Screen 2). Does not matter if I select a different screen under View -> Virtual screen 1 -> Host host screen 1/2

If I plug screen 2 out, then it works, but the moment I plug it in, it goes back to screen 2",Jaques
15649,Can no longer switch screens using mini toolbar,Windows,Windows,VirtualBox 5.1.0,2022-08-22T13:55:20Z,2022-08-22T13:55:20Z,"I just upgraded to v5.1 and can no longer switch screens using the mini-toolbar command '''View | Virtual Screen 1 | Use Host Screen X'''. I am running the VM in full screen mode. When I choose ""Use Host Screen 2"" nothing happens. No errors.

I can switch out of full screen mode, I can drag the VM to my second monitor and reenter full screen mode. But moving the VM to another monitor via. the mini toolbar menu no longer works for me.

Windows 8.1 host with multiple monitors

Windows 7 VM, with a single monitor

",s23ayers
21060,Getting memory reference error after upgraded to Virtualbox 6.1,Windows,Windows,VirtualBox 6.1.36,2022-08-22T21:48:09Z,2022-08-22T21:48:09Z,I am getting the memory reference error after upgrading to Virtualbox 6.1. Can you please help solving the issue?,Natarajan Arumugam
21074,launchVMProcess via MSCOM -- environment changes parameter type mismatch ambiguity,Windows,all,VirtualBox 6.1.30,2022-08-24T04:28:06Z,2022-08-24T04:28:06Z,"
When calling launchVMProcess() through MSCOM by VBScript, JScript, Python, etc.. they all end up with a ""type mismatch"" error. After some process of limitation, it might be the third and final parameter the cause of it: the list of environment changes.

According to the source in c++, it supposed to accept a string array, but the source wants a specific type of array: a string (utf-8) array. It doesn't like variant arrays (I believe they're called safearrays?). Unfortunately, because the samples or examples provided in the SDK doc is too outdated -- i.e. using openRemoteSession rather than launchVMprocess -- I'm lost as to how to pass something to that third parameter that'll satisfy VirtualBox MSCOM.

I was referring to the definition of launchVMProcess() here:
//trunk/src/VBox/Main/src-server/MachineImpl.cpp#L7814

If there are new steps that weren't documented, they should be updated accordingly; especially the SDK doc.

It's worth mentioning that the issue from Ticket #20750 might be related to what was mentioned here.",jprogman
21075,Bridged network doesn't work on WiFi interface on Ubuntu jammy with kernel 5.15.0-46,Linux,Windows,VirtualBox 6.1.36,2022-08-24T08:30:11Z,2022-08-24T08:30:11Z,"Upon upgrading to jammy and using latest kernel 5.15.0-46 the bridged networking on WiFi interface stopped working - host (Windows 10 ENT 64bit). It works fine if I manually switch to 5.13.0-52 kernel.

The difference I spotted is when I list interfaces is that the WiFi is listed as not WiFi:

{{{
vboxmanage list bridgedifs
Name:            wlp3s0
GUID:            33706c77-3073-4000-8000-340286543f76
DHCP:            Disabled
IPAddress:       192.168.1.9
NetworkMask:     255.255.255.0
IPV6Address:     fe80::2421:bd44:a0a3:b042
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 34:02:86:54:3f:76
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-wlp3s0

Name:            enp0s25
GUID:            30706e65-3273-4035-8000-68f7289e3ac5
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 68:f7:28:9e:3a:c5
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-enp0s25
}}}
",rskolnik
21076,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,Windows,Linux,VirtualBox 6.1.34,2022-08-25T14:16:03Z,2022-08-25T14:16:03Z,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,ignasi
21073,Windows 10 VM on Mac 10.15.7 Catalina crashes when clipboard enabled,Mac OS X,Windows,VirtualBox 6.1.36,2022-08-25T14:47:57Z,2022-08-25T14:47:57Z,"Something broke starting about one year ago - having the clipboard enabled leads to crashes within 24 hours of starting the VMs.  Disabling the clipboard makes the VM completely stable.  Upgrading to latest OS and VB releases did not change the behavior.

Process:               VirtualBoxVM [1449]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            VirtualBoxVM
Version:               6.1.36 (6.1.36)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [1443]
Responsible:           VirtualBox [1439]
User ID:               502

Date/Time:             2022-08-22 22:57:21.383 -0400
OS Version:            Mac OS X 10.15.7 (19H2026)
Report Version:        12
Bridge OS Version:     6.6 (19P6064)
Anonymous UUID:        A811DB67-BC10-7168-DD2A-D1DFFC1A784E


Time Awake Since Boot: 46000 seconds

System Integrity Protection: enabled

Crashed Thread:        10  SHCLIP

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
",nfjanette
21080,'NS_ERROR_FAILURE' and '/sbin/rcvboxdrv' and similar commands produce a 'not found' error,other,other,VirtualBox 6.1.36,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
21081,The mouse crashes with VirtualBox 6.1 and Debian 11 with kernel 5.18,Linux,Windows,VirtualBox 6.1.36,2022-08-28T16:41:02Z,2022-08-28T16:41:02Z,"Hi, I'm using Linux Debian 11 (Bullseye) with Kernel 5.18 for compatibility with my new laptop, it doesn't work with a kernel < 5.18.
I have virtualized a windows 10 image with VirtualBox 6.1.36 r152435 (Qt5.15.2)
My problem is when I run a Banco de Sabadell application inside windows 10 to generate bank receipts, the mouse crashes.
I run this application on another laptop with another kernel 5.10 and it works.

The virtualbox error message is as follows:
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={10cd08d0-e8b8-4838-b10c-45ba193734c1} aComponent={MouseWrap} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)}, preserve=false aResultDetail=-2807

Thanks!",capi
21083,EFI shell fails to detect non-ESP partitions,Windows,all,VirtualBox 6.1.36,2022-08-29T19:29:32Z,2022-08-29T19:29:32Z,"Starting with 6.1.34, EFI (both shell and ""GUI"") fails to detect non-ESP partitions in optical media.  Booting from the media using the included boot loader works.  However, it's no longer possible to bypass the boot loader and boot directly from the non-ESP partitions.

I've tested a Windows 10 host with VirtualBox 6.1.34 and 6.1.36.  I've observed the problem with debian-11.2.0-amd64-netinst.iso, ubuntu-22.04-live-server-amd64.iso, and FreeBSD-13.0-RELEASE-amd64-disc1.iso.

This worked in 6.1.32.",ov2k
20995,Failed to open a session for the virtual machine #VMName#.,Windows,Windows,VirtualBox 6.1.34,2022-08-30T07:12:41Z,2022-08-30T07:12:41Z,"VirtualBox-6.1.32-149290 works 100% and all VM's start.

From version 6.1.33 get the following error on ALL VM's:

Failed to open a session for the virtual machine #VMName#.

The virtual machine '#VMName#' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\#UserName#\VirtualBox VMs\#VM_And_LogFolder#\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Tried Installing 6.1.33 with and without Extension Packs - Error as Above
Tried installing 6.1.34 with and without Extension Packs - Error as Above
Tried installing 6.1.34a with and without Extension Packs - Error as Above

Please note: I don't think it is the Extension packs because running v6.1.34a with Extension Pack 6.1.32 gives same error.

Included is the LOG files for:
Successful start and shutdown of a VM (v6.1.32)
1.VBox_20220620_6.1.32.log
2.VBoxHardening_20220620_6.1.32.log
Unsuccessful start of same VM (v6.1.34a)
1.VBoxHardening_20220620_6.1.34a.log",Hercules Oberholzer
21085,mp bios bug 8254,Windows,Linux,VirtualBox 6.1.36,2022-08-31T11:47:09Z,2022-08-31T11:47:09Z,bende bios bug 8254  noapic hatası veriyor bana yardımcı olun tıkandım kaldım,seafflyy
21094,Guru Meditation Error,Windows,Linux,VirtualBox 6.1.38,2022-09-02T18:44:21Z,2022-09-02T18:44:21Z,"I have downloaded the Quickstart Cloudera Vm 5.13.0-0- virtual box with Red Hat for VirtualBox 6.1.38 and when I ""start"" the iteration I get a Guru Meditation critical error. I do not have any chance of interaction. ",fhqwhgads
21096,Tab text do not shown at macOS Monterey,Mac OS X,other,VirtualBox 6.1.38,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
19427,windows 10 virtualbox 6.1.2 wierd cant copy / move webm files,Windows,other,VirtualBox 6.1.2,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
21098,Can't create VDI file from external hard drive,other,other,VirtualBox 6.1.38,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
20667,The keyboard not working after the complete installation of Linux Mint 20.2.,Windows,Linux,VirtualBox 6.1.28,2022-09-07T08:31:06Z,2022-09-07T08:31:06Z,The keyboard not working after the complete installation of Linux Mint 20.2. When the installation is completed & said press enter keys I pressed but not working please solve this problem this is a bug!,Cannon1000
21099,Windows 10 doen's work well with 3D acceleration enabled,Linux,Windows,VirtualBox 6.1.36,2022-09-08T13:41:56Z,2022-09-08T13:41:56Z,"With Windows 10, if 3D acceleration is enabled I have big graphic bugs and the VM can even reboot without a reason.",-RedHead-
21100,Microphone is too silent in the VM with Windows 10 or 11,Windows,Windows,VirtualBox 6.1.38,2022-09-08T23:10:29Z,2022-09-08T23:10:29Z,"I have an old problem with microphone: even with the maximum level on the host, it is nearly silent in the guest. If I test it on the host, I can see the level goes to 100%, but the same test in the guest gives only 10% volume.

I searched the tickets and forum. All I could find is the suggestion to use Line-in in pre-Windows 10 versions, but there is no Line-in in my Windows 10 or Windows 11 VM. My host is Windows 10 by the way.

So, my question is: are there any other possibilities to bring the microphone volume to the right level in the guest?",boxer01
21101,installation folder is not remembered when upgraded,Windows,other,VirtualBox 6.1.38,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
21104,VirtualBox.chm index missing?,Windows,Windows,VirtualBox 6.1.36,2022-09-09T17:17:52Z,2022-09-09T17:17:52Z,"I am unable to search the help file.
It appears there is no index to search.
Can I add/build one (I do not know if the User can add/create an index) or can you update the help file to be searchable?

Please advise.
Thanks, Tracey
Searching for USB results in ""No Topics Found"" ",Tracey
21105,Getting a Guru Meditation - Critical error during CentOS user settings configuration,other,other,VirtualBox 6.1.38,2022-09-10T23:49:24Z,2022-09-10T23:49:24Z,,ktapodac
19131,linux guest os does not recover from host sleep - Win 10 host,Windows,Linux,VirtualBox 6.0.14,2022-09-15T08:26:09Z,2022-09-15T08:26:09Z,"Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min. 

If I send the host OS to sleep and immediately (within 5 min), everything is fine.

After a longer sleep, say 20 min, I get varying results:

1) the guest OS seems to have rebooted and I arrive at the login window.  My prior running apps and consoles are gone from the desktop.

2) the OS hangs, showing the login screen.  Mouse and keyboard are not working.  Software reboot (send a shutdown signal) does not work.  Must reboot the guest os. 


My computer is recovering from sleep mode and not hibernate mode.

This seems to have started since 16.x.  I created the guest OS in 15.x.
",eyn
20972,Black screen,Windows,Windows,VirtualBox 6.1.34,2022-09-19T06:18:08Z,2022-09-19T06:18:08Z,Black screen in opened virtual OS,jjjj jjjj
19496,Virtualbox 6.1.6 guest screen resize broken,Linux,Linux,VirtualBox 6.1.6,2022-09-20T20:23:32Z,2022-09-20T20:23:32Z,"
The virtualbox 6.1.6 update seems to be okay, but if the matching guest additions is applied to the guest, the auto-resize or resize to any resolution is unavailable.  I applied guest additions to several hosts before discovering this issue, including Centos-6, Centos-7, Centos-8, kali linux, and OracleLinux-8.  Guests that have not gotten the update seem to be working fine.

Matt",Wheaties
19677,VM window size not restored after exiting save state,other,other,VirtualBox 6.1.10,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
15060,Can't start virtual machine with bridged interfaces,Windows,all,VirtualBox 5.0.14,2022-09-28T19:15:41Z,2022-09-28T19:15:41Z,"When resuming a saved virtual machine, I get the message:

{{{
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

This is on Windows 10.0.10586, but didn't start when upgrading to this version... I've been using Virtualbox fine for the last couple of weeks until this morning.

I did some searching and it seems that others were able to resolve the same issue by enabling the 'VirtualBox NDIS6 Bridged Networking Driver' for their network adapters, but I checked each adapter and it's already enabled for them all.

The virtual machine logs contain:

{{{
00:00:03.187772 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.187821 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187846 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:03.187879 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187883 VMSetError: Failed to attach the network LUN
00:00:03.187893 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:03.190010 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.197890 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.204536 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.211773 GIM: KVM: Resetting MSRs
00:00:03.341518 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:03.341550 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:03.341693 Console: Machine state changed to 'PoweredOff'
00:00:03.352282 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
}}}",Sam Morris
20937,"Multi monitor operation not working as expected, regression to 5.2",Windows,Linux,VirtualBox 6.1.34,2022-09-29T07:28:20Z,2022-09-29T07:28:20Z,"Host: Windows 10, 64 bit
Guest: Ubuntu 22.02 64 bit, Linux Mint 64 bit,... - Linux guest additions installed from VirtualBox's image as provided by the host

Situation: in version 5.2.x one could setup a VBox with two monitors, start the VBox and switch it to fullscreen mode - immediately on both monitors. That setting was persisent, so starting the VBox later would bring it up on two monitors in fullscreen mode without any manual action.

After upgrading to VirtualBox 6.1.34, the VBox settings were changed to ""VMSVGA"" graphics controller.

In version 6.1.34 it is not possible to activate the second monitor if the VBox is already in fullscreen mode - the menu option is not shown at all.
And in window mode one has to activate the second virtual monitor by hand each time the guest was started.

If one chooses ""VBoxVGA"" graphics controller, then the VBox apppears on two monitors in fullscreen mode immediately as it did in version 5.2. But there's then a really ugly bug with wrong mouse coordinates, that makes the VBOx unusable.

I have attached a log file of the following process:
1. starting the VBox (Xubuntu 22.04)
2. logging in
3. trying to activate the second virtual monitor - that FAILED (the window pops up and disappears immediatly)
4. once again trying to activate the second virtual monitor - worked now
5. shutting down the guest

I have tried both, a VBox that was already present and used with version 5.2.44 in the past and a brand new VBox created with version 6.1.34. There's no difference.

So IMHO that's a regression in version 6.1 compared to version 5.2 - it used to work pretty fine in version 5.2.
",Feuerfloh
21114,Critical error. The memory could not be read.,Windows,Windows,VirtualBox 6.1.38,2022-09-29T13:24:38Z,2022-09-29T13:24:38Z,"Unfortunately, I don't have a log file or a reproduction step for the error.",Eugene
21103,guest resolution defaults to 640x480 waking from sleep state,Windows,Windows,VirtualBox 6.1.38,2022-09-29T13:28:38Z,2022-09-29T13:28:38Z,"every time i start a guest with win10 from saved state 
it defaults to 640x480 even though its saved with a resolution
1600x900",sphinxios
17679,Error on trying to run VM in headless mode.,Windows,Windows,VirtualBox 5.2.8,2022-09-29T17:32:06Z,2022-09-29T17:32:06Z,"Host: Windows 10 Pro x64
Quest: Windows XP x32

All going norm. VM works and launches.
Problem is error when attempt to launch VM in headless mode.

Error:
Не удалось открыть сессию для виртуальной машины VWXP.
The virtual machine 'VWXP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\User\VirtualBox VMs\VWXP\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}",UnclWish
21117,Windows 11 host machine's touchscreen stops working while running a Linux guest VM.,Windows,other,VirtualBox 6.1.38,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
21118,USB isochronous transfers cause problems under OS/2 guest,Windows,other,VirtualBox 6.1.38,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
21115,freeze gnome gui ubuntu,Linux,other,VirtualBox 6.1.38,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
19364,EFI boot from ISO does not work in existing VMs,all,all,VirtualBox 6.1.4,2022-10-04T20:24:36Z,2022-10-04T20:24:36Z,"I have installed Windows 10 64 Bit as guest in EFI mode in a VM under Windows 10 64 Bit as host system, it works fine. However when I mount a bootable ISO (e. g. an actual Windows 10 ISO) and set the optical device as first option in the boot priority, the machine still boots the installed Windows 10 from hard disk. Obviously the boot order is without any effect.
When I create a new VM in EFI mode, booting from ISO works one time, when I close the dialog, which asks the boot medium.
In legacy guest mode (without EFI) everything works fine.
I found this bug first time in Virtual Box 6.1.",awhb
21119,Restoring a saved Guest does not restore the saved display size,Windows,Windows,VirtualBox 6.1.38,2022-10-08T15:07:17Z,2022-10-08T15:07:17Z,"To produce the error. Start a Windows 10 Guest and when idle save the guest, noting the screen display size. Restart the guest VM and note the screen size after allowing time for guest to become idle. Note the screen size is NOT the same as the saved guest VM was.
This happens whether the guest VM is Windows 10 or Windows 11.
In some cases, the correct screen display size is created at the beginning of the restore but is changed to 640x480 when the restore is completed.",MacNala2
21121,second network interface cannot talk to network,other,other,VirtualBox 6.1.38,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
20832,"Fedora-35 HOST + Windows 10/11 GUEST: Keyboard entries and Touchpad Taps stop responging, after ~10m",Linux,Windows,VirtualBox 6.1.32,2022-10-10T12:08:30Z,2022-10-10T12:08:30Z,"Dear Friends:

I have a bug that I've been facing for approaching 2-years (19-months, actually). No matter what I do, the bug remains. Let me explain.

The bug, which I describe further below, first appeared in '''August''' of '''2020''' on '''Fedora-32 64-bit''', which is the '''HOST''' O/S. Back then, I had hoped that the bug would be confined to a particular '''Fedora Kernel''' and waited for the next one; but as I upgraded Fedora-32 Kernels, the bug persisted.

Then, I eventually upgraded to '''Fedora-33''' (again, the '''HOST'''), and the bug persisted through that Fedora version and through all of its Kernels, as well. The same occurred with '''Fedora-34'''.

For '''Fedora-35''', I decided to reinstall everything from scratch: I reinstalled '''Fedora-35''' ('''HOST''') from scratch; as well as reinstalled '''Windows-10''' ('''GUEST'''). Without customizing much, except to apply the '''Extension Pack''' and '''Guest Additions''', I launched a Windows-10 VM (with everything fresth). The bug immediately surfaced. It always takes about ~5 to 10 minutes to occur, by the way.

Now, all of this was on a '''Lenovo''' '''Y700-17isk''' Laptop.

So, I decided to do the same procedure on an '''ASUS G750 Rogue''' Laptop: I installed '''Fedora-35''' ('''HOST''') from scratch; as well as installed '''Windows-10''' ('''GUEST''') from scratch. Without customizing much, except to apply the '''Extension Pack''' and '''Guest Additions''', I launched a Windows-10 VM (with everything fresh). The bug immediately surfaced. 

No matter what I do, I cannot get rid of this bug. I think that circa '''August 2020''', either '''Fedora''' and/or '''VirtualBox''' changed something that is causing this long-running bug.

'''THE PROBLEM''':

-- I first reported this problem on '''August 2020''' ('''Lenovo Y700-17isk''' laptop) [https://forums.virtualbox.org/viewtopic.php?f=7&t=99328 here]

-- Then, I reported this problam again yesterday, '''February 2022''' ('''ASUS G750 Rogue''') [https://forums.virtualbox.org/viewtopic.php?f=7&t=105295 here]


Here is a paste of yesterdays description for your convenience:


{{{
VirtualBox Version..................: 6.1.32_rpmfusion
HOST O/S............................: Fedora-35
HOST Kernel.........................: 5.14.10-300.fc35.x86_64
GUEST O/S (with latest updates......: Windows-11 (happens with Windows-10, as well)

}}}


What happens is this: VirtualBox is working perfectly (Network, Audio, Shared Drive, Cut & Paste, Keyboard & Mouse Capture, Mapped USB Devices, etc); but then suddenly, after, say, 5 to 10 minutes, the Keyboard stops responding to Keystrokes, and the Touchpad stops responding to Taps. The only thing that responds is moving the mouse-cursor around by swiping around the Touchpad, but that's it. This happens whether or not the GUEST (Windows 10 / 11) is in Fullscreen mode or Window mode. Except for being able to move the mouse-cursor around, Keystrokes and Touchpad Taps stop working inside the GUEST window, or around it on the HOST. The only option I have to to crash the Laptop by holding the power-button down. Actually, I did try to SSH into the HOST from another server, and while it does initiate the SSH connection, it never can never actually log in. So the HOST is still quote/unquote kind of running, but in a hobbled state.

I should also mention that this issue arises even with more basics setups: USB disabled; Audio disabled; Network with LAN or Bridged; etc.

Please help me. I think this is a real bug. It persists no matter what I do. For the better part of two-years, I haven't been able to use VirtualBox.

I can upload or add more information. Just let me know what you need.

Thank you in advance!",nyceyes
21124,VirtualBox v7's macOS installer should check the host's requirements first.,Mac OS X,all,VirtualBox 7.0.0,2022-10-11T00:28:35Z,2022-10-11T00:28:35Z,"My upgraded VirtualBox (v7) told me that it doesn't run in my old, updated macOS Mojave v10.14.6. It told me this AFTER (install/upgrad)ing VirtualBox v6.1.38-153438 to v7. I had to uninstall v7 and reinstall the older version. It should had told me that BEFORE (install/upgrad)ing. :(",Ant
21127,windows 10 guest crash,other,other,VirtualBox 6.1.38,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
21129,Graphic bug when I enable aero effects on Windows 7,Windows,Windows,VirtualBox 7.0.0,2022-10-11T18:35:27Z,2022-10-11T18:35:27Z,When I enable Aero effects on the latest version of VirtualBox the Aero graphics are poor after installing the VirtualBox Guest Additions,Sorecchione07
21134,Screen capture didn't work on Windows guest,Windows,Windows,VirtualBox 7.0.0,2022-10-12T09:28:58Z,2022-10-12T09:28:58Z,"Screen capture return black or transparent when the Vbox video driver installed into Win 10 21H2 guest. On driver removal screen capture works fine.

STR:
1) Update VirtualBox from 6.1 to 7
2) Update Guest tools in the Wondows guest OS
3) Try using screen capture 

Vbox logs attached
Screen recording on cloud, due to attachments limit

https://disk.yandex.ru/i/JcATChyQcuZl3Q
https://disk.yandex.ru/d/H3jMvKKWw-CxgQ

",vpupkin3
21123,Virtual machine crashes while installing the Guest addons,other,other,VirtualBox 7.0.0,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
21143,with 2 monitor with different display resolution the mouse does't works,Windows,Windows,VirtualBox 7.0.0,2022-10-13T10:23:09Z,2022-10-13T10:23:09Z,"Using the version 7 of Virtualbox, configured with two screens as per the attached images, configured to the maximum occupancy of the video, the mouse moves everywhere but the click is not located in the correct place on the X axis so it becomes impossible to select or open and close windows or interact with the system. The further you move away from the left side of the first screen, the more the error increases. Fortunately, you can select the windows menu and shut down the operating system. Conversely, if I use only one monitor, even on the ultrawide screen I have no problems.",JamesTKirk
21150,"Some programs see no files in shared folders (Host: W10, Guest: XP)",Windows,Windows,VirtualBox 7.0.0,2022-10-14T15:19:57Z,2022-10-14T15:19:57Z,"In order to reproduce, you will need Norton Commander (I have version 3) or Alpha4 (a database manager; I have version 8).

In the guest VM (XP), Windows Explorer and CMD are able to see and list all the files in a shared folder mounted in the guest.

In some cases, alpha4 shows no files at all, and in others, it shows only files with .set extension (it's supposed to show .set and .dbf files always).

Norton Commander shows no files at all in shared folders mounted in the guest.

When issuing a DIR command when Norton Commander is running, I get ""Extended Error 234"" and no files listed at all (the DIR command should list files normally).

Norton Commander 3.0 can be downloaded from here: [https://winworldpc.com/product/norton-commander/3x]",ArneS
21148,VBoxManage: error: Invalid command 'hostonlynet',Linux,other,VirtualBox 7.0.0,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
20924,IPv6 not working out of the box with bridged WiFi and Linux guests,Windows,Linux,VirtualBox 6.1.34,2022-10-16T00:31:25Z,2022-10-16T00:31:25Z,"When using a bridge WiFi interface, IPv6 doesn't work out of the box on Linux guests. IPv6 becomes operational only after issuing ""ip -6 neigh del <gateway-linklocal-ipv6> dev <dev>"" as proposed in this gist: https://gist.github.com/0xquad/6090af4fe2c5b5fc6299 (although I found issuing it one single time suffices. No need to issue it repeatedly as the gist suggests).

This problem occurs only with Linux guests. Windows (10?) guests can use IPv6 just fine without any additional steps. Several WiFi NICs (Intel, Realtek) were tested, as well as several routers (FritzBox, Compal, generic OpenWrt). Confirmed also by different people, with different distros, including at least Ubuntu 20.04, 21.10, 22.04, Linux Mint 19.x, Mint 20.x, ArchLinux, Kali 2021. I don't have a Linux host to test with, but it's at least a bug with Windows hosts.

The bug appears similar to https://www.virtualbox.org/ticket/5503 (supposedly fixed) and https://www.virtualbox.org/ticket/14212. However, the latter mentions broken promiscuous mode as problematic. Since Windows guests aren't affected, I think that this is a different bug. The bug exists at least since VirtualBox 5.x, probably earlier versions affected as well.",treysis
21157,Virtual box 7.0 oversize interface with DPI setup in Host,Windows,other,VirtualBox 7.0.0,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
21165,Turtle != Snail,Windows,other,VirtualBox 7.0.0,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
21164,Virtualbox 7.0.0 - macOS - provisioning profile,Mac OS X,all,VirtualBox 7.0.0,2022-10-18T21:56:08Z,2022-10-18T21:56:08Z,"Hi all,

I and other forum members noticed that the latest VB on macOS adds provisioning profile:

https://forums.virtualbox.org/viewtopic.php?f=8&t=107346

Would it be possible briefly explain what it is for? macOS profiles are very powerful thing usually used by corporate administrators to change behavior of managed computers, e.g. to install new root certs. Long story short it can have potentially security implications some of us care more than others.

Thank you for your clarification in advanced.

Kind Regards

kapitainsky",kapitainsky
21135,Windows 11 guest hangs at startup on Linux host,Linux,Windows,VirtualBox 7.0.0,2022-10-19T11:15:28Z,2022-10-19T11:15:28Z,"- Windows 11 Guest 
- VM was created with Virtual Box 6.38 (I think) set up registry to bypass TPM checks.

Updated Virtual Box to 7.0.

When starting guest OS, I can see Windows progress animation for a while and then it just freezes",vagaus
21173,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,Windows,VirtualBox 7.0.0,2022-10-21T02:38:16Z,2022-10-21T02:38:16Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
21175,Result of sorting VMs isn't saved properly,Windows,all,VirtualBox 7.0.0,2022-10-21T07:16:25Z,2022-10-21T07:16:25Z,"Since 7.0.0 it seems result of sorting VMs isn't saved properly.[[BR]]
If I click right button of mouse on any VM and select ""Sort"", then VMs are listed in alphabetical order.[[BR]]
But if I restarted VirtualBox Manager, then VMs are listed in the order before sorting.[[BR]]
It also happens with 7.0.2.
",Yasu
21176,Switching between Expert & Guided modes resets all the data,Linux,all,VirtualBox-7.0.2,2022-10-21T12:20:48Z,2022-10-21T12:20:48Z,"This is a very annoying bug.

Start creating a VM in guided mode. At the first step switch to Expert Mode. All the data you've entered will be instantly lost. It's the same vice versa.

Please fix.",Artem S. Tashkinov
21178,Unattended install mustn't be enabled by default,all,all,VirtualBox-7.0.2,2022-10-21T12:23:20Z,2022-10-21T12:23:20Z,"I really dislike that VirtualBox enables Unattended Install by default.

I normally test OSes, so I want to do everything manually.

Or at least add a '''global''' option in VirtualBox: [ ] Enable Unattended Install by default.

Thank you.",Artem S. Tashkinov
21179,Disk read/write net in/out icons need to be shown separately,all,all,VirtualBox-7.0.2,2022-10-21T12:24:38Z,2022-10-21T12:24:38Z,"In the VM window status bar there are two icons, one for disks, another one for network.

Whenever there's a simultaneous disk read/write activity or sent/received traffic it's hard to make sense which one prevails.

Please make the busy indicators (they are quite large circles) smaller and shown separately, e.g.

The green read disk circle at the respective icon bottom left, the write red disk circle at the bottom right.

Thank you!",Artem S. Tashkinov
21181,Increase default VRAM for Windows 11 to 256MB,all,Windows,VirtualBox-7.0.2,2022-10-21T12:28:15Z,2022-10-21T12:28:15Z,Video memory for Windows 11 is set to 128MB by default which is too little. I would be great if the defaults were changed to 256MB because it results in the guest having more RAM available.,Artem S. Tashkinov
18219,VERR_NOT_SUPPORTED for a valid ISO image,Linux,Linux,VirtualBox 6.0.0,2022-10-21T12:47:37Z,2022-10-21T12:47:37Z,"Both VirtualBox 6.0 and 5.2.22 don't accept this ISO image:

http://mirror.ppa.trinitydesktop.org/trinity/cdimages/ubuntu/tde-ubuntu-14.04-desktop-latest-amd64.iso

The error is:

Failed to open the disk image file /tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso.

Could not get the storage format of the medium '/tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso' (VERR_NOT_SUPPORTED).


{{{
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}


",Artem S. Tashkinov
20826,tinycore 1.4 crashes VirtualBox,Linux,Linux,VirtualBox 6.1.32,2022-10-21T12:52:40Z,2022-10-21T12:52:40Z,"Steps to reproduce:

DL http://tinycorelinux.net/archive/tinycore_1.4.iso and use it.

Start a VM.",Artem S. Tashkinov
20600,Fedora 35 compatibility / udev rules errors,Linux,other,VirtualBox 6.1.26,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
20342,VirtualBox 6.1.20/6.1.22 breaks audio output on a Fedora 33 system,other,other,VirtualBox 6.1.22,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
19595,memtest86 8.3 freezes,Linux,other,VirtualBox 6.1.8,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
21184,export appliance doesn't remember the destination path,other,all,VirtualBox-7.0.2,2022-10-21T13:41:10Z,2022-10-21T13:41:10Z,"I export an appliance and it suggests c:\Users\myname\Documents\machineName.ova and this is expected behavior  I choose another path and export the machine properly.  I export a second machine and it goes back to the first path listed not the last path used.

It seems that most apps that will remember the last path used especially if it was the last one used if the app has not been closed.  Perhaps it should remember between runs but certainly if the app has not been closed.  This is on a win 10 host.",pguin
19316,Guest additions cannot be installed in Windows Vista,all,Windows,VirtualBox 6.1.2,2022-10-21T13:54:06Z,2022-10-21T13:54:06Z,"VirtualBox 6.1.2 guest additions cannot be installed in a fully updated Windows Vista SP2 x86.

ERROR 800b0010: no signature was present in the subject.

See the attached screenshot.",Artem S. Tashkinov
21185,"After upgrade to 7.0.2, VM will not launch",other,other,VirtualBox-7.0.2,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
21187,Draw issues with 3d acceleration enabled on Windows Server 2016,other,Windows,VirtualBox-7.0.2,2022-10-21T22:28:36Z,2022-10-21T22:28:36Z,"On Windows 2016 Server, with 3D acceleration enabled I'm seeing draw issues with Direct2D.
There are no issues when 3D acceleration is disabled.",euclid
21188,Clarify if clicking to pause a guest releases CPU and/or Memory,all,all,VirtualBox-7.0.2,2022-10-22T00:09:44Z,2022-10-22T00:09:44Z,"[https://www.virtualbox.org/manual/UserManual.html#vboxmanage-controlvm 8.20. VBoxManage controlvm] states the ""pause command temporarily stops the execution of a VM. When paused, the VM's state is not permanently changed.""

Please add there if it means releasing CPU and/or Memory (mention which) from the host, and whether it's completely or partially (if partially then mention how much it should).

Some users seem to assume so and [https://superuser.com/questions/131646/why-does-virtualbox-use-15-20-cpu-when-vm-is-paused then have complaints], so please make it official.",l-w-c
21177,VirtualBox for Linux - Enter doesn't work for Power off,Linux,all,VirtualBox-7.0.2,2022-10-22T10:52:09Z,2022-10-22T10:52:09Z,"Under Linux press right Ctrl + Q, select ""Power Off the machine"", press ""Enter"" (on the keyboard), nothing will happen (the radio button will flash once).

The OK button seems to be bound to the radio list and cannot be activating using the keyboard.

That's a bug.",Artem S. Tashkinov
20873,HDAT2 crashes under SysLinux 6.04 in VirtualBox 6.1.32 r149290 (Qt5.15.2),Linux,other,VirtualBox 6.1.32,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
21193,Update build instruction page,Linux,other,VirtualBox-7.0.2,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
21194,Export creates a defective .ova file (missing disk image) : cannot import itself back.,Windows,Linux,VirtualBox 6.1.36,2022-10-22T19:25:08Z,2022-10-22T19:25:08Z,"I am using VBox 6.1.36 under Windows 10 Pro.

When I exported my VM from VirtualBox so that it will be imported to VMWare player, etc., VMware Player, and VMWare workstation pro  does not read the disks correctly (I think). 
The number of disks recognized by VMWare player was about half the numbers of attached disks used in VirtualBox. So the import basically failed.

So I tried to read the exported description back to VirtualBox to see what happens.

To my surprise, VirtualBox reported the following error, which collaborates my observation of missing disks in VMWare Player, etc.

--- Begin Quote: The following the error I saw. It is under Japanese Windows 10 Pro.

{{{


仮想アプライアンス""J:\NEW-VMWARE-DIR\debian64bit-Rev02-transition.ova""のインポートに失敗しました。

The above says, VBox failed to import the *.ova description.


&lt;vbox:Machine&gt; element in OVF contains a medium attachment for the disk image 10bf7d63-35a5-4f22-87fd-b11a1634da12 but the OVF describes no such image.

終了コード : E_FAIL (0x80004005)
コンポーネント: ApplianceWrap
インターフェース: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}
}}}


---- end quote

The original VM seems to work just fine as far as I use it to develop patches for Thunderbird mail client and other tasks.
",ci-zephyurus
19374,Goldwave freeze guest machine,Linux,Windows,VirtualBox 6.1.4,2022-10-22T21:54:42Z,2022-10-22T21:54:42Z,"On virtualbox 6.1.4[[BR]] with virtualbox addtion 6.1.4 in mode vboxsvga[[BR]]

In software goldwave , in long sound , when i remove by keyboard 'suppr' a lot sample ,[[BR]]

then i have random problem which is graphics sound sample redraw very slow (system freeze temporarily !) [[BR]]
I see the graphics which is drawn very slowly ![[BR]]

I join log I don't know if this will help correct this bug!

Please solve this bug ! please ![[BR]]

OS Guest: Windows Seven [[BR]]

Thank.[[BR]]

",Sizy458
21195,Display issue with Windows 8,Windows,Windows,VirtualBox-7.0.2,2022-10-23T09:32:08Z,2022-10-23T09:32:08Z,"Windows 8 may not render UI properly in VirtualBox 7.0.2 r154219.
Guest OS: Windows 8
Host OS: Windows 10 Pro 21H2
Virtual Graphics Card: VBOXSVGA(192MB VRAM)
Host Graphics Card: Intel HD Graphics 4000 and AMD Radeon HD8570M with dinamic-switching.
[[Image()]]",Shimakaze
21180,Guest resolution without VirtualBox drivers cannot be changed from default 1024x768,all,Windows,VirtualBox-7.0.2,2022-10-23T13:02:30Z,2022-10-23T13:02:30Z,"For a Windows 11 guest, video/monitor/display resolution without VirtualBox guest drivers cannot be changed from default 1024x768.

This used to work for non-EFI earlier Windows releases.

My guest is Windows 11 22H2.",Artem S. Tashkinov
21197,Make Shared Folder accessible by default in at least certain Linux variants,all,Linux,VirtualBox-7.0.2,2022-10-23T22:35:12Z,2022-10-23T22:35:12Z,"As explained [https://forums.virtualbox.org/viewtopic.php?t=103322 here], it takes a running special command line in order to be able to enter shared folders instead of only getting ""permission denied"" messages.

It's explained there it might be different for each flavor of Linux, but how about giving solutions to at least popular packages like Ubuntu and Lubuntu?

As seen [https://unix.stackexchange.com/a/400137 here] in Lubunto the command (that also saved the day for me) is:

{{{
sudo usermod -a -G vboxsf $(whoami)
}}}

If not, then maybe at least produce a message after installing Guest Additions in Linux to invite the user to look up how to make shared folders work.",l-w-c
21136,Unwanted transparency in the Windows 11 guest,Windows,Windows,VirtualBox 7.0.0,2022-10-23T23:16:04Z,2022-10-23T23:16:04Z,"I already described this in the beta [[https://forums.virtualbox.org/viewtopic.php?f=15&t=106990|forum]], with logs and pictures. Some of the elements of Windows itself (like Start menu or volume control) are transparent in the way it shouldn't be. It isn't a transparency effect from the Windows itself, which could be turned off. And this is an annoying bug in the cases when the current background color isn't matching the element content.",boxer01
21198,"VirtualBox 7.0.2, Window 7 64bit guest, Linux host, 3D openGL not working with any video driver in guest additions",Linux,Windows,VirtualBox-7.0.2,2022-10-24T06:50:29Z,2022-10-24T06:50:29Z,"I suppose this is a continuation of the problem that started with the driver re-write after 6.0. In 6.0 it used to work, in 6.1 it stopped, and in 7.0 there was an attempt to fix it but still not working.

3D OpenGL does not work at all in any software package. (Tried VBoxVGA, VMSVGA, all default to VBoxSVGA)

---------------
Host is Ubuntu 20.04 

output of glxinfo | grep 'version':

server glx version string: 1.4

client glx version string: 1.4

GLX version: 1.4

OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03

OpenGL core profile shading language version string: 4.60 NVIDIA

OpenGL version string: 4.6.0 NVIDIA 470.141.03

OpenGL shading language version string: 4.60 NVIDIA

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.141.03

OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

    GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix, 

---------------
DXDIAG output on Windows 7 64 bit guest:


Display Devices

          Card name: VirtualBox Graphics Adapter (WDDM)
       Manufacturer: Oracle Corporation
          Chip type: 
           DAC type: 
         Device Key: Enum\PCI\VEN_80EE&DEV_BEEF&SUBSYS_040515AD&REV_00
     Display Memory: 3583 MB
   Dedicated Memory: 2303 MB
      Shared Memory: 1279 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Generic Non-PnP Monitor
      Monitor Model: unknown
         Monitor Id: 
        Native Mode: unknown
        Output Type: HD15
        Driver Name: VBoxDispD3D.dll,VBoxDX.dll,VBoxDX.dll
Driver File Version: 7.00.0002.4219 (English)
     Driver Version: 7.0.2.4219
        DDI Version: 11
       Driver Model: WDDM 1.0
  Driver Attributes: Final Retail
   Driver Date/Size: 10/19/2022 15:10:54, 411360 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp: 
  Device Identifier: {D7B78E0E-FDAF-11CF-6666-0724AFC2CA35}
          Vendor ID: 0x80EE
          Device ID: 0xBEEF
          SubSys ID: 0x040515AD
        Revision ID: 0x0000
 Driver Strong Name: oem49.inf:Model.NTamd64.6.0:VBoxVideo:7.0.2.4219:pci\ven_80ee&dev_beef
     Rank Of Driver: 00F82001
        Video Accel: 
   Deinterlace Caps: {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,X8R8G8B8) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

---------------

All the 3d CAD legacy programs I am trying to work, either default to software openGL or display nothing.

I tried running the openGL diagnostic program called glview from here https://realtech-vr.com/home/glview, it also displays the same behaviour (does not show anything but garbage).

All the legacy programs run fine on the same Windows 7 natively (non virtualised)

Any suggestions for a fix or a meaningful work around? Tnx.
",tiras_dude_o
21152,Save state and snapshot functionality is broken in version 7.0.0,Windows,Windows,VirtualBox 7.0.0,2022-10-24T17:15:51Z,2022-10-24T17:15:51Z,"As I already wrote in the beta forum, I can't use neither save state nor snapshot functions in the new version.
After saving the state or making a snapshot, the next start of the guest causes an exception in the Vbox.

The saved state also can't be dropped. The drop function gives you ok, but after starting the VM, it tries to start from the saved state. Which is still on the disk.

Here is my original forum [https://forums.virtualbox.org/viewtopic.php?f=15&t=107200 post], and another [https://forums.virtualbox.org/viewtopic.php?f=2&t=107367 post] after release. I also append my logs.",boxer01
19726,Reported memory usage doubled in 6.1.4 on MacOS Mojave and later,Mac OS X,other,VirtualBox 6.1.10,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
21206,Can't start vm after update,Windows,all,VirtualBox-7.0.2,2022-10-26T20:22:32Z,2022-10-26T20:22:32Z,I have an ubuntu virtual machine with an encrypted disk on windows host. After update from 6.1.40 to 7.0.2 it does not start (there is no window where I can print my password for decryption). After downgrading to 6.1.40 I successfully started my vm.,sorsdt
21203,multiple virtual screen issues,other,other,VirtualBox 6.1.40,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
21196,Display issue with Windows System,Windows,Windows,VirtualBox-7.0.2,2022-10-27T21:09:04Z,2022-10-27T21:09:04Z,Display broken after VBOX additions installed.,iRabbit_Jimmy
21209,Insert Guest Additions does not insert CD ISO,Windows,Windows,VirtualBox-7.0.2,2022-10-27T21:12:30Z,2022-10-27T21:12:30Z,"Unlike in previous revisions, ""Insert Guest Additions"" does not do anything. The new notification window will tell me it is working, and the log says it writes files to my guest's ProgramFiles\Oracle\Vbox Guest Additions\update folder, but I cannot run the installer like in previous builds as the guest will not recognize a CD has been inserted. 

Loading other ISOs work fine, and I can install guest additions using the file path provided above (albeit with graphical glitches noted in other tickets). ",T4nkcommander
21146,"Buttons,transparent list background and startmenu are garbaged with 3d acceleration in win10 guest.",Windows,Windows,VirtualBox 7.0.0,2022-10-27T21:16:02Z,2022-10-27T21:16:02Z,"When 3d acceleration is enabled{
Buttons,transparent list background and other UI elements in Win10 Settings are garbaged.
Start Menu sometimes turns white.
}",ebk
21208,7.0.2 r154219 does not play well with Windows 7 3D acceleration,Windows,Windows,VirtualBox-7.0.2,2022-10-27T21:24:22Z,2022-10-27T21:24:22Z,"Using 3d Acceleration on my Windows 7 Professional guest (which worked fine with Vbox6) has all sorts of problems when on Vbox 7.

Most notably, I get a ""mirage"" effect any time I mouse over an item. Additionally, the minimize, maximize, and exit buttons do not appear at any time on any window. ",T4nkcommander
21211,The command wmic memorychip returns no instances available on Windows server 2019 and Windows 10.,all,Windows,VirtualBox-7.0.2,2022-10-27T22:23:40Z,2022-10-27T22:23:40Z,"The following windows command returns ""no instances available"" on Windows server 2019. The command returns the memory card information on Windows 2012 R2.

   wmic memorychip

Issue occurred on v6 and v7 of VirtualBox.
Issue occurred with VirtualBox running on both Linux and Windows hosts.
Issue also occurs on Windows 10 and Server 2022 VMs.
The command returns valid information on VMware VMs.

This breaks apps and scripts that use this to get memory information.",Nick3213
21210,GuestInfo reverts to old data after VM shutdown,Linux,all,VirtualBox-7.0.2,2022-10-28T14:33:25Z,2022-10-28T14:33:25Z,"I'm trying to get information about my guests without having to start them. Here's an example of my '''Debian 11''' VM:

'''System is off'''

{{{
/VirtualBox/GuestAdd/HostVerLastChecked  = '6.1.38'                       @ 2022-10-02T23:48:31.042Z
/VirtualBox/GuestAdd/Revision            = '154048'                       @ 2022-10-24T19:03:35.218Z
/VirtualBox/GuestAdd/Version             = '6.1.40'                       @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestAdd/VersionExt          = '6.1.40'                       @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/Net/0/MAC          = '0800273D1A5F'                 @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/Name         = 'enp0s3'                       @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/Status       = 'Up'                           @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/Broadcast = '10.0.2.255'                   @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/IP        = '10.0.2.111'                   @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/0/V4/Netmask   = '255.255.255.0'                @ 2022-10-24T19:03:35.220Z
/VirtualBox/GuestInfo/Net/Count          = '1'                            @ 2022-10-24T19:03:50.225Z
/VirtualBox/GuestInfo/OS/Product         = 'Linux'                        @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/Release         = '5.10.0-19-amd64'              @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/ServicePack     = ''                             @ 2022-10-24T19:03:35.217Z
/VirtualBox/GuestInfo/OS/Version         = '#1 SMP Debian 5.10.149-1 (2022-10-17)' @ 2022-10-24T19:03:35.217Z
/VirtualBox/HostInfo/GUI/LanguageID      = 'en_US'                        @ 2022-10-24T19:03:53.671Z RDONLYGUEST
}}}

'''System is on, logged in'''
{{{
/VirtualBox/GuestAdd/HostVerLastChecked    = '7.0.2'                        @ 2022-10-27T19:39:15.924Z
/VirtualBox/GuestAdd/Revision              = '154219'                       @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestAdd/Version               = '7.0.2'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestAdd/VersionExt            = '7.0.2'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/Net/0/MAC            = '0800273D1A5F'                 @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/Name           = 'enp0s3'                       @ 2022-10-27T19:38:57.976Z
/VirtualBox/GuestInfo/Net/0/Status         = 'Up'                           @ 2022-10-27T19:38:57.976Z
/VirtualBox/GuestInfo/Net/0/V4/Broadcast   = '10.0.2.255'                   @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/V4/IP          = '10.0.2.111'                   @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/0/V4/Netmask     = '255.255.255.0'                @ 2022-10-27T19:38:57.975Z
/VirtualBox/GuestInfo/Net/Count            = '1'                            @ 2022-10-27T19:39:18.000Z
/VirtualBox/GuestInfo/OS/LoggedInUsers     = '1'                            @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/LoggedInUsersList = 'ajgringo619'                  @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/NoLoggedInUsers   = 'false'                        @ 2022-10-27T19:39:17.999Z TRANSIENT, TRANSRESET
/VirtualBox/GuestInfo/OS/Product           = 'Linux'                        @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/Release           = '5.10.0-19-amd64'              @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/ServicePack       = ''                             @ 2022-10-27T19:38:57.972Z
/VirtualBox/GuestInfo/OS/Version           = '#1 SMP Debian 5.10.149-1 (2022-10-17)' @ 2022-10-27T19:38:57.972Z
/VirtualBox/HostGuest/SysprepArgs          = ''                             @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostGuest/SysprepExec          = ''                             @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/GUI/LanguageID        = 'en_US'                        @ 2022-10-27T19:39:10.318Z RDONLYGUEST
/VirtualBox/HostInfo/VBoxRev               = '154219'                       @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/VBoxVer               = '7.0.2'                        @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/HostInfo/VBoxVerExt            = '7.0.2'                        @ 2022-10-27T19:38:49.151Z TRANSIENT, RDONLYGUEST
/VirtualBox/VMInfo/ResetCounter            = '0'                            @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
/VirtualBox/VMInfo/ResumeCounter           = '0'                            @ 2022-10-27T19:38:49.097Z TRANSIENT, RDONLYGUEST
}}}
As soon as I shut the VM down, the data reverts to the first list (exactly, including timestamps).  This is not consistent; some VMs retain their data, while others don't. All of my systems in question are using the ISO version of Guest Additions.",ajgringo619
21216,Recovery Mode is not Accessible in Newer MacOS Guests,Mac OS X,OSX Server,VirtualBox-7.0.2,2022-10-29T17:34:03Z,2022-10-29T17:34:03Z,"IF you install Monterey on VirtualBox, you're not able to boot into Recovery Mode via the VB BIOS (e.g. ""Boot from file"") because there's no boot.efi file shown under the GUID in the Recovery Mode partition.  This issue appears to have started with BIg Sur.  If you access the filesystem with the UEFI Shell, you'll see that there are a bunch of files names boot.efi.<some string> in that partition, but this new naming system is obviously not recognized by VirtualBox.

This problem reproduces with the latest VirtualBox, VB 7.",ThomasF
21217,Cannot boot from VISO,Windows,Windows,VirtualBox 6.1.40,2022-10-29T19:09:38Z,2022-10-29T19:09:38Z,"I have been struggling to boot an extracted Windows 11 medium using a VISO file without success until I found a comment regarding this topic:
https://www.virtualbox.org/ticket/19910#comment:24

They mention that on 6.1.32 booting from VISO worked fine which I can confirm.
However, I could not get it to work with VB 6.1.38, 6.1.40, 7.0.0 or 7.0.2.",Flubberlutsch
21220,progress bar for exporting appliance is ambiguous,Windows,all,VirtualBox-7.0.2,2022-10-30T15:22:08Z,2022-10-30T15:22:08Z,"The progress bar when exporting an appliance (and possibly other uses of the bar) are uncertain when the task is complete and there is no positive affirmation that the task is finished properly.

Some applications get to 100% and have some clean up tasks to do for 10-60 seconds and then give a positive affirmation.  There was a common dropbox problem where it got to 100% and never actually completed.  Most progress bars display themselves only while progressing and go away once finishing the task.

But here, it's hard to tell 99% from 100% as the default text is small and both have the same color progress bar.  But there is can be a lingering doubt whether it's actually completed without a positive confirmation of ""I'm done""

I don't know the ideal confirmation be it an ""task completed"" box with and ""OK"" button but one can be hesitant to close as it's uncertain it's actually done.",pguin
21213,Loading a saved state stops some graphical apps from rendering until reboot,Windows,Linux,VirtualBox-7.0.2,2022-10-30T22:11:20Z,2022-10-30T22:11:20Z,"It is a simple problem and not critical but I need to make it work because I work with saved states a lot. I should mention that I am somewhat newbie with this guest system archlinux.

I have windows 10 and vbox7.0.2

Basically some GUI applications stop rendering properly if the VM is loaded from a saved state: midori, badwolf, spotify-launcher

I always save the state to resume it and my applications are still there without having to reopen everything, this is something quite common in virtualbox and it never gave me a problem (edited)

Apps like midori, badwolf or spotify-launcher work fine, but they stop rendering if I load a saved state and the only solution is to restart the vm, but other apps like nemo (file explorer) or the terminal (alacritty) don't have that problem.

I think the common detail is that they are gtk applications (however nemo works fine) and my guest distribution is probably not fully prepared for it because I use a very raw install of arch linux:
-i3, picom (i think it could be related), midori, badwold, opera, minbrowser, spotify-launcher. I had also installed arc-gtk-themes

I have tried to log the problem without results or relevant info inside of the VM, reset i3, picom and polybar but none of that corrects the problem.

I already tried reinstalling virtualbox-guest-utils and gtk, I installed gnome but also didn't change anything.

Booted up and midori works:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644709525266503/unknown.png]

Saved state just fine:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644710116659250/unknown.png]

Loading state just right after:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711106510858/unknown.png]

Some apps looks like this, they WORK but dont render properly:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711580475402/unknown.png]

I believe it this most likely a problem on my end, either host or guest, so considering you may not be able to reproduce, I attached some logs.


",mr.satoshi
21191,VirtualBox 7.0.x aborts VM using Windows XP,Windows,Windows,VirtualBox-7.0.2,2022-10-31T02:04:50Z,2022-10-31T02:04:50Z,VM hosting WinXPSP3 created using VBox 6.1 fails to start (aborts systematically) on VBox 7.0 and 7.0.2,Kyle_Katarn
21221,[regression][7.0.2?] Windows XP guest has suddenly stopped working and causes VBox Internal Error,Linux,Windows,VirtualBox-7.0.2,2022-10-31T15:15:10Z,2022-10-31T15:15:10Z,"All of a sudden my Windows XP guest which I've used for almost a decade without any modifications (I always revert to a snapshot I created back then) has stopped working.

It did work with VirtualBox 7.0.
It probably even worked with VirtualBox 7.0.2 with Linux kernel 5.19.16.
I cannot be sure. I will attach a log file.

I can even send this guest in its entirety to VirtualBox developers if necessary. There's nothing private/personal about it.",Artem S. Tashkinov
21227,VM stop on error,Windows,Linux,VirtualBox-7.0.2,2022-10-31T20:56:18Z,2022-10-31T20:56:18Z,Crash during guest OS upgrade.,Дмитро
21169,Deprecation of libIDL on Linux,Linux,other,VirtualBox 7.0.0,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
21215,Mouse scroll not working,other,other,VirtualBox-7.0.2,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
21228,Plenty of sav files in Snapshots without any snapshot,Windows,Linux,VirtualBox-7.0.2,2022-11-02T14:05:48Z,2022-11-02T14:05:48Z,"On Windows 10 host (Ubuntu guest) I have had a plenty of snapshots over period of time I have used VirtualBox 6.1 and now VirtualBox 7.0.2. I created snapshots and deleted them, then creating new ones etc. But today I have deleted all of the snapshots.

Now looking into Snapshots folder and I expect no files are in this folder anymore, but to my surprise there are plenty of files all with SAV file extension (the problem I am reporting).

Command ""dir"" output on Windows host:
19/05/2022  22:08       712.041.461 2022-05-19T21-07-57-214718900Z.sav
31/05/2022  17:56       782.450.690 2022-05-31T16-56-50-903121400Z.sav
07/06/2022  21:46       665.091.925 2022-06-07T20-46-36-299478900Z.sav
22/06/2022  21:55       702.938.444 2022-06-22T20-55-17-961063100Z.sav
14/07/2022  21:12       843.395.181 2022-07-14T20-12-47-010062000Z.sav
06/08/2022  16:09       707.927.057 2022-08-06T15-09-23-494845800Z.sav
30/08/2022  18:16       836.501.505 2022-08-30T17-16-26-777190700Z.sav
02/10/2022  17:44       717.281.998 2022-10-02T16-44-24-007573200Z.sav
07/10/2022  18:45       757.231.318 2022-10-07T17-45-24-466885500Z.sav

From file's date (May, Jun, July and August) I assume this files are from VirtualBox 6.1.x times. From file extension it looks those files are some saved snapshot's states. Why does they still exists? I assume there is/was some bug that does/did not delete saved state when snapshots gets deleted.

I shut down the virtual machine and move those files away from virtual machine Snapshot directory to some directory outside of VirtualBox and I started virtual machine and it starts up successfully and virtual machine works just normally.

I assume those files are not needed anymore, are they? Can I permanently delete them without any harm?",bobJ
21235,Can't run VBox,Windows,Linux,VirtualBox-7.0.2,2022-11-02T17:51:33Z,2022-11-02T17:51:33Z,"I'm first use of vbox . I'm just download vbox and vdi image and run it. And it cause this error
I don't know what type of error it is.",takriz
21236,VERR_CR_KEY_FORMAT_NOT_SUPPORTED,other,other,VirtualBox-7.0.2,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
21186,VM No memory  Result Code:  E_FAIL (0x80004005),Windows,Linux,VirtualBox 6.1.40,2022-11-03T21:42:40Z,2022-11-03T21:42:40Z,"What to do? 

Failed to open a session for the virtual machine Rocky Linux_8x64.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: RTCrStoreConvertToOpenSslCertStore failed: \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_NO_MEMORY).

Failed to load VMMR0.r0 (VERR_NO_MEMORY).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Butterfly011
21225,USB,Linux,Windows,VirtualBox 6.1.38,2022-11-04T12:30:09Z,2022-11-04T12:30:09Z,"USB is shown as working just fine when defining the Guest VM xppro
however, when xppro is run and accessing Devises the USB section is grayed out.

Running Linux Mint 20 Ulyssa",buz
21231,Current State displayed as (changed) just after taking snapshots,all,Windows,VirtualBox-7.0.2,2022-11-05T11:29:47Z,2022-11-05T11:29:47Z,"Running Virtualbox Version 7.0.0 r153978 (Qt5.15.2) on Windows 11.
I powered off 2 virtual machines (one Linux guest and another FreeBSD guest). I wait a couple of minutes after they have been powered off to take a snapshot of current state, but for some reason says ""Current State (changed)"" like if I powered on the virtual machine after that, which did not happen.

I had noticed this to happen to me occasionally with FreeBSD guest, but now is happening to me also with Linux guest.

If I take a second consecutive snapshot without powering on the vm, then it's fixed and now says ""Current State"" without (changed).

Could not test if the issue is reproducible with the Linux or macOS versions of Virtualbox, anybody had the same issue?

Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=107653",DeGarden
21251,Deleting snapshot's still available to Clone,Windows,other,VirtualBox-7.0.2,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
21243,"WIndows 10 screen black, Mac Ventura, VB 7.0.2",Mac OS X,Windows,VirtualBox-7.0.2,2022-11-07T21:03:40Z,2022-11-07T21:03:40Z,"Just installed VB 7.0.2, latest extension pack, upgraded Mac to Ventura 13.0. Windows 10 VM starts but window is black, cursor alternately shows spinning blue circle. Shutting down machine by red button works as expected. ",LarryW-PDX
21241,Almalinux 8.6 aborts (virt-what),Windows,other,VirtualBox-7.0.2,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
21138,7.0.0 doesn't work for a Windows 10 guest with multiple monitors,Windows,Windows,VirtualBox 7.0.0,2022-11-08T19:56:17Z,2022-11-08T19:56:17Z,"After upgrading from 6.1.38 to 7.0.0 on a Windows 10 host, it seems to be working fine with a single-monitor Windows 10 guest VM, but not with a Windows 10 guest VM that has 3 monitors. It gets confused as to which monitor the mouse is clicking in, making it pretty much unusable. For example, I have the Windows task bar on the center monitor only, and when I try to click with the mouse pointer located over the Windows start button there, nothing happens. If I move the mouse pointer to the bottom left corner of the left monitor and click there, then the start menu opens on the middle monitor.

Also, when the mouse is in the main window the pointer looks good and stable (although it doesn't work for clicking in that window), but when I move it to one of the other windows then it gets jumpy and fuzzy.

I tried to disable 2 of the monitors from within Windows, but that was almost impossible with the mouse clicking on the wrong one.

Rolled back to 6.1.38 and all is hunky dory again.

I then disabled 2 of the 3 monitors while running in 6.1.38 before re-installing 7.0.0, and then the VM worked fine with just the one monitor. But when I then tried to re-enable a 2nd one, the issue came back.",Ian Puleston
21257,virtualbox kernal modules do not match,other,Windows,VirtualBox-7.0.2,2022-11-09T14:14:22Z,2022-11-09T14:14:22Z,"upgraded to version 7,error RTR3InitEx failed with rc=-1921 (fRtFlags=0x10000)(rc=1912)

kernel modules do not match extra

uninstalled, reset computer and still the same, strait back to verison 6.1.40 which works straight away",exinsp
19326,VirtualBox Manager 6.1.x causes BSOD when docking into HP Universal dock G2,Windows,other,VirtualBox 6.1.4,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
15471,"F16C, FMA and BMI extensions are not supported.",all,all,VirtualBox 5.0.20,2022-11-10T01:12:57Z,2022-11-10T01:12:57Z,"Programs compiled with the Intel Compiler (C or Fortran) for >= Haswell do not run inside a VirtualBox VM (with AVX2 enabled), and immediately exit with the following error message:

{{{Please verify that both the operating system and the processor support Intel(R) F16C, FMA and BMI instructions.}}}

Of course, you can tell the Intel Compiler to generate fallback code, but then AVX2 instructions aren't used either, and the (scientific) program runs much slower.

The AVX2 support in VirtualBox would be even more useful if it was possible to run AVX2 optimized code produced by the Intel Compiler suite.",KlausErz
21207,Mouse snap behaves sticky on VB via a remote desktop,Windows,Windows,VirtualBox-7.0.2,2022-11-10T11:48:40Z,2022-11-10T11:48:40Z,"Mouse snap behaves sticky on VB via a remote desktop

When I remote login via mstsc on a machine and use the VB on that machine the mouse snap behaves weird. It jumps instead of smooth moves. Sometimes it jumps to totally different places.

Guest Adition for 7.02 are also installed. VM OS is Win 11. Host OS is Win 10.",SecondBox
21261,Microsoft Office 2013 not working if Guest Additions are installed,other,Linux,VirtualBox-7.0.2,2022-11-10T16:57:30Z,2022-11-10T16:57:30Z,"I have Ubuntu Linux 22.10 as a host and VirtualBox version 7.0.2 r154219 (Qt5.15.6).

I craeted a Windows 10 virtual machine. Windows 10 in virtual machine are fully updated. I also have installed Microsoft Office 2013.

When I run MS Word 2013 and have latest Guest Additions installed, this application runs, but the application window is black. I can right-click on the area of the application window and can get some menus open, but that is all. I can not see anything. The same is with MS Excel 2013.

If I uninstall Guest Additions, MS Word opens normally and the content of the application window is normally visible (the same with Excel). So it seems that Guest Additions are somehow affecting those two applications.

I have tested some other applications (Firefox, Chrome, Adobe Reader, Malwarebytes,...) and those work normally.

Also, I thought that the problem is with Microsoft Office 2013, so I run the installer and select Repair installation. Repair was not successful, because installed said that LYNC.LYNCDESKTOPRESOUR.DLL.x64.1033 cannot be installed. I don't know if this is somehow connected, but I believe it is worth mentioning.",MatejKovacic
21262,Cannot run multiple guest VMs of the same type if their *.vbox files are all in the same directory,Windows,all,VirtualBox-7.0.2,2022-11-10T23:24:47Z,2022-11-10T23:24:47Z,"It seems that Virtualbox is using some kind of folder-level locking construct that makes it impossible to run multiple guest VMs if those guest VMs' corresponding *.vbox files are all in the same folder.  Attempting to launch a second VM stored in the same folder when another is running will lock up the window before the BIOS image appears and the VM will crash with this error:


{{{
The VM session was aborted.
Result Code:
E_FAIL (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}


I like organizing all of my guest OSes by their main OS-type.  So, for example, Windows NT, 2000, 2003, and 2019 will all live in the same ""WINDOWS"" folder under a given directory hierarchy.  Ditto for Solaris 10, Solaris 11.4, OmniOS, and OpenIndiana under a ""SOLARIS"" directory.  I do not like using individual subfolders under this hierarchy and I want all of the *.vbox files to be together.

I don't really know why I like it this way, but I do, and I have found it difficult to organize things in a different manner that makes both myself and Virtualbox happy.  It feels like the folder-level locking is a kludge (I mean, why not file-level locking?), or at least, the crash is not being handled terribly well (a helpful error message being returned would be a marked improvement vs just outright crashing).

FWIW, how I got to this condition is every time I create a new guest VM, I set the bare minimum config, then shut VBox down and  any services to make sure all of the XML files are flushed out.  Then I manually move *.vbox and *.vdi files around to where I want them, then edit the XML's to point things to the new locations.  Other than the occasional hiccup from a still-running VBox process holding a lock, this setup has worked well for the past several years.  The inability to run multiple OSes of the same type is not a major blocker, but I had been perplexed for a while why it wasn't possible until I finally did some debugging.

Can someone maybe take a look at whether folder-level locking is still appropriate, or at least put some code in to detect this scenario and return an error message to the user?",Kumba
21264,extremely bad performance- guest:windowsXP host:Mac ventura 13.0.1 (intel),Mac OS X,Windows,VirtualBox-7.0.2,2022-11-11T10:45:25Z,2022-11-11T10:45:25Z,"Host upgraded from Mac(intel chip) Monterey to MacOS 13 Ventura, and virtualBox upgraded from 6.1 to 7.02. WindowsXP worked fine on 6.1, but now on 7.02 
a major speed down has occurred(both 32bit and 64). Every action is in slow motion now(even typing).

",cryingmachine
21234,"upgrade vb from 6.1.40 to 7 or fresh install vb7,vmsvga(3D) conflict with xrdp's dri3 & glamor",all,Linux,VirtualBox-7.0.2,2022-11-13T05:57:24Z,2022-11-13T05:57:24Z,"debian11 guest on virtualbox 6.1.x, xrdp 0.9.12 support dri3 and glamor, works well with vmsvga(3D).
After virtualbox is upgraded to 7.0.2  or fresh install vb7, Windows 10/11 remote desktop cannot access debian11 guest with xrdp 0.9.12. .xorgxrdp.10.log's lastline shows (EE) Server terminated with error (1).closing log file.

Temporary Solution:
Modify /etc/X11/xrdp/xorg.conf
#Option ""DRMDevice"" ""/dev/dri/renderD128""
Option ""DRMDevice"" """"
or
disable vmsvga(3D)
or
cancel the xrdp login user's access permission on /dev/dri/renderD128 (including the impact of uaccess mechanism on /dev/dri/renderD128).",sxd
21268,[virtualbox 7.0.2] doesn't work with a Windows 11 guest on an Arch Linux host,Linux,Windows,VirtualBox-7.0.2,2022-11-13T13:18:33Z,2022-11-13T13:18:33Z,"Hi,

while downgraded guest additions solved a freeze issue with a Windows 11 guest, USB is broken.

There are no issues with a Windows 7 or a Windows 10 guest.
{{{
$ uname -r; pacman -Q virtualbox
4.19.255-rt113-0.1000
virtualbox 7.0.2-2
}}}
Windows 7

guest never updated to guest additions version 7.0.2r154219
now at version 6.1.40r154048
USB 2.0 enabled does work with my iPads connected by USB

Windows 10

guest updated to guest additions version 7.0.2r154219
now at version 7.0.2r154219
USB 2.0 enabled does work with my iPads connected by USB

Windows 11

guest updated to guest additions version 7.0.2r154219 does cause freezes 
downgraded to guest additions version 6.1.40r154048
now at version 6.1.40r154048 no freezes anymore, but
USB 2.0 as well as USB 1.1 enabled do n o t work with my iPads

For more details, see

https://bugs.archlinux.org/task/76531

https://forums.virtualbox.org/viewtopic.php?f=7&t=107757

https://bbs.archlinux.org/viewtopic.php?id=281196

https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/GSDRGWQEULBUM254XGBZLX7NCFWF5FCE/#GSDRGWQEULBUM254XGBZLX7NCFWF5FCE

Regards,

Ralf",Ralf
21267,USB devices are not recognized in the guest machine,Linux,Windows,VirtualBox 6.1.40,2022-11-13T16:10:00Z,2022-11-13T16:10:00Z,"My USB devices are simply not recognized / detected if I connect them to any USB ports. All of them were successfully detected in previous versions of vbox. And yes, all USB devices I am trying to detect are added to USB devices filters in vbox settings. I have also tried to alternatively enable USB Controller 1.1, 2.0 or 3.0 Without success. 
In the host machine (linux Ubuntu 22) all USB devices are successfully detected. So the problem is only with the guest machine (Windows 10) or the vbox 6.1.40 respectively",rsm37turb
21269,Unable to use more than 1 host-only adapter using Virtualbox 7.x,Windows,Windows,VirtualBox-7.0.2,2022-11-13T18:51:17Z,2022-11-13T18:51:17Z,"Updated to VB 7.02.  I had 2 host-only adapters set up.  After upgrading BOTH host-only adapters were invalid. I would get an error stating that the host-only adapter was unable to open/load.  Create a NEW host-only adapter - same issue.

After deleting BOTH host-only adapters, the app created it's OWN host-only adapter.  I can use this one.  However, I am unable to use ANY OTHER host-only adapter.  I can change the config host-only adapter that the app created, and it works.  However, if I try to create my own (doesn't matter the config), I get an error when trying to load the VM. This DOES NOT happen with vitrualbox 6.x

My laptop is running Windows 11 Pro (latest updates).  The VM is Windows 10 ENT EVAL, but it doesn't matter what OS I use for the VM.
",Fenderluvr
21270,VIRTUAL BOX 7.0.2  Bug,Linux,Windows,VirtualBox-7.0.2,2022-11-14T21:16:07Z,2022-11-14T21:16:07Z,In windows 10 Host when you have more than one virtual machines (Linux machines on my case) and you have put them on shell startup in order to boot them automaticaly one of them crashes on boot and blocks the state of this machine (not all the times),Tasos Skarpathakis
21260,shared folder does not work.  modprobe vboxfs fails due to  missing symbol (Debian kernel 6.0.0.2),Windows,Linux,VirtualBox-7.0.2,2022-11-15T06:42:14Z,2022-11-15T06:42:14Z,"Host Windows 10 Pro
22H2 
19045.2251

Guest: Debian GNU Linux
$ uname -a
inux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux

VirtualBox:
7.0.2 r154219 (Qt5.15.2)

---
Problem: Shared folder between host and guest no longer works.

I have noticed that file sharing between the host no longer works.
I *think* this is  related to the local upgrade of the kernel to 6.0.0.2.

I installed the guesttools.
However, after some investigation, I realized vboxsf module is not loaded.
The reason is the missing symbols when vboxsf is loaded.

modprobe vboxsf fails:
{{{
root@ip030:/var/log# modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg)
}}}
dmesg shows:
{{{
[ 1992.940391] Spectre V2 : System may be vulnerable to spectre v2
[ 1992.940396] vboxsf: loading module not compiled with retpoline compiler.
[ 1992.940527] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 1992.940535] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 1992.940541] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 1992.940554] vboxsf: Unknown symbol VBoxGuest_RTStrNLen (err -2)
[ 1992.940589] vboxsf: Unknown symbol VBoxGuest_RTLogBackdoorPrintf (err -2)
[ 1992.940600] vboxsf: Unknown symbol VBoxGuest_rtR0MemObjLinuxVirtToPage (err -2)
[ 1992.940631] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 1992.940637] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 1992.940643] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 1992.940649] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 1992.940655] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 1992.940661] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[ 1992.940667] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 1992.940673] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 1992.940679] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 1992.940685] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRequest (err -2)
[ 1992.940691] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRelease (err -2)
[ 1992.940697] vboxsf: Unknown symbol VBoxGuest_RTSemMutexCreate (err -2)
[ 1992.940702] vboxsf: Unknown symbol VBoxGuest_RTSemMutexDestroy (err -2)
[ 1992.940708] vboxsf: Unknown symbol VBoxGuest_RTMemContAlloc (err -2)
[ 1992.940714] vboxsf: Unknown symbol VBoxGuest_RTMemContFree (err -2)


}}}

It seems that vboxsf is not compiled locally using retpoline compiler?
But I am not sure if it matters or not.

",ci-zephyurus
21274,Incorrect font size use sticks after virtualbox window is moved to the second display,Windows,Linux,VirtualBox-7.0.2,2022-11-15T12:44:41Z,2022-11-15T12:44:41Z,"Host Windows 10 PRO
[[BR]]
VirtualBox 7.0.2[[BR]]
Guest: Debian GNU/Linux [[BR]]
uname -a[[BR]]
Linux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux[[BR]]

I have two monitors attached to the PC.
[[BR]]

I have experienced a very annoying font size problem.

When the VirtualBox window is moved to the second display,
virtualbox suddenly causes the guest linux to use very large font.[[BR]]

The problem is that even after I move the virtual box window back to the original 1st display, the large font size is still used and it is really unusable after this happens.
I think the change of font size on the 2nd display may be related to the
different display resolution and used font size (there is an multiplication factor I set using individual config of the display, etc. I am using the Japanese Window and so I don't know the menu names for these settings in English.)


The only reference related such a font size issue I can find is the comment in 
comment 3 of ticket Ticket #20282.
{{{
but it uses a wrong font size if it is on the 2nd screen. 
}}}

Please note that strange font size usage when the program window is moved from the 1st window to the 2nd window is observed for many applications.
MS EXCEL, MS WORD, Thunderbird mail client to name a few, especially only half the window is shifted to the 2nd window.
However, many programs resume to use the right font size once the program window is reverted to the 1st window, or completely moved to the 2nd window.

VirtualBox is the only program that keeps on using strangely large font size even if I move the window back to the original. And for that matter, it keeps on using the strangely large font and it becomes unusable for my purpose.
Once VBox is retarted, the problem goes away, but it is very undesirable.

I will attach screen captures to explain the problem, but I am not sure if I can get the screen dump when the VBox window is split between the two windows.
I will take a photo in that case.
 

",ci-zephyurus
21275,Login issue,other,other,VirtualBox-7.0.2,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
21276,The drag and drop does not work,Windows,Windows,VirtualBox 6.1.40,2022-11-15T23:48:32Z,2022-11-15T23:48:32Z,I have windows 10 host and windows 10 guest but drag and drop only works from guest to host,Heber
19168,Error [drm:vmw_host_log [vmwgfx]] in version 6.1.0,Windows,Linux,VirtualBox 6.1.0,2022-11-18T13:08:19Z,2022-11-18T13:08:19Z,"When booting my Oracle Linux 7 (4.14.35-1902.8.4.el7uek.x86_64) system I get the message: (Twice)
{{{
 [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log
}}} 

This is when I select VMSVGA as the Graphics Controller. This message does not happen if I use the old VBOXVGA. I am unsure what, if anything, this effects.

I have included the machine log to this report.
",DonC
21282,ACPI ERST support,all,all,VirtualBox-7.0.4,2022-11-18T17:01:28Z,2022-11-18T17:01:28Z,"ACPI ERST supported by almost all modern motherboards/bioses. It allows to write kernel logs, including kernel panic dumps to special storage. Especially useful for catching and writing panic messages, when system is not able to write to generic partitions. Windows also supports writing  to ERST during BSODs.

This is nice and simple way to store kernel panic logs.

Hope VirtualBox will support ERST soon.

According to article from Oracle blog

https://blogs.oracle.com/linux/post/pstore-linux-kernel-persistent-storage-file-system

''Oracle has been working to improve the usability of the Linux kernel pstore feature.''

QEMU already has this feature:

https://www.qemu.org/docs/master/specs/acpi_erst.html",AndrewByte
21287,Unable to Show Windows Side by Side,Windows,other,VirtualBox-7.0.4,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
21289,crash during shutdown,Windows,Windows,VirtualBox 6.1.38,2022-11-20T00:08:27Z,2022-11-20T00:08:27Z,the system crashes when I shutdown it,tiria
21290,nvme error,Windows,Windows,VirtualBox 6.1.38,2022-11-20T15:44:41Z,2022-11-20T15:44:41Z,I am not able to work with a drive nvme. I have a nvme disk Samsung 970Evo Plus but if I try to use a disk connected to the nvme drive it does not work al all.,tiria
19630,"VM window size not restored after save-state (Ubuntu 20.04, VB 6.1.8)",Linux,Windows,VirtualBox 6.1.8,2022-11-21T08:42:46Z,2022-11-21T08:42:46Z,"If the ""x"" close button on a VM is pressed, and ""Save state"" is selected, then when the VM is started up later, the desktop is much smaller (looks like a default small size -- possibly the same as the size of the startup splash window?)

VB Version 6.1.8 r137981 (Qt5.12.8)

Host: Ubuntu 20.04, X11 with gnome-shell 3.36.2, Intel built-in graphics (in i7-8700K cpu)

Guest: Windows 10 64-bit with latest GAs installed

FWIW, these are the same symptoms reported in [https://www.virtualbox.org/ticket/16593] ; that bug says it was fixed in 5.1.22

I'll attach before & after screen shots and VBox.log files.

STEPS TO REPRODUCE:
1.  Boot Win-10 VM, expand the VM window to a large size.
2.  Click the ""X"" window-manager icon to close the VM window
3.  Check ""Save state"", click OK
(VBox.log.1 was from the above)
4. In VB gui, click ""Start"" to restore the VM

Initially an image of the large VM window appears with the ""restoring..."" progress meter.
   
Then the VM window shrinks to a small size


(VBox.log is from step 4.)

",Jim Avera
21294,Windows 11 freezes shortly after startup on VBox7 MacOS,Mac OS X,Windows,VirtualBox-7.0.2,2022-11-22T21:15:42Z,2022-11-22T21:15:42Z,"MacOS Vbox 7 hangs eventually running Windows 11. Downgrading guest additions to v6.x avoids the issue, but can't stay that way.

Details of issue posted here:

https://forums.virtualbox.org/viewtopic.php?f=2&t=107616

Other users can reproduce the issue...also appears to affect linux as well.",h00die
21295,Win 7 32b guest VM craash when installing guest additions 7.0.4,Linux,Windows,VirtualBox-7.0.4,2022-11-22T22:23:21Z,2022-11-22T22:23:21Z,"Host:
Ubuntu 20.04.5 LTS
kernel 5.4.0-132
Wayland, Gnome 3.36.8

Guest:
Windows 7 (32bit)
Guest Additions 7.0.2 previously installed

Procedure:
Start guest VM; boot; login
From VM window menu -> Devices -> Insert Guest Additions CD image...
Start Guest additions installer from Windows Explorer
Install runs through until the graphics driver is installed.
Window resizes shortly to VGA (probably the 'uninstall' of the old driver) then goes back to previous resolution (probably when the new driver is enabled).
This is the moment when the VM crashes.
Reproducible.
This error is new in 7.0.4. It was not there in 7.0.2.
The Windows VM can be restarted normally after the abort and the guest additions appear to be installed, including the graphics driver. Vbox Task Bar App reports v7.0.4 installed.

Maye a duplicate to https://www.virtualbox.org/ticket/21123",sunrider
21296,TPM not working without UEFI/SecureBoot,Linux,Windows,VirtualBox-7.0.4,2022-11-23T10:07:41Z,2022-11-23T10:07:41Z,"When TPM is enabled, Windows cannot start it if not starting from UEFI/SecureBoot, there should be a warning when enabling it to prevent this invalid configuration",DidiKo
21298,Menu Screen -virtual screen - Use creen # does not work no more,Windows,Windows,VirtualBox-7.0.4,2022-11-23T10:45:55Z,2022-11-23T10:45:55Z,"From version 7, it's impossible to move a ""full screen mode"" VM from a screen of my computer to another. It always worked well with version 6.

The VM stays stuck on screen 3 when I ask it to go to screen 2, while taking the size of the screen 2 (!).

See capture.",JLB
21147,Display driver bug causes VM to abort upon start,Mac OS X,other,VirtualBox 7.0.0,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
21232,3d Accerlation causes guest to not start on Ventura => fixed in SVN/next 7.0.x maintenance,Mac OS X,Linux,VirtualBox-7.0.2,2022-11-24T07:10:14Z,2022-11-24T07:10:14Z,"When trying to run a guest, if 3d Acceleration is enabled, the guest will not start.  VB 7.02 MacOS 13.0

To reproduce, create a windows or linux guest on MacOS Ventrua, and enable 3d graphic acceleration, attache an iOS and start.  Gest will not start with error.

To workaround uncheck, 3d Graphics Acceleration and start guest will succeed.",JavaOops
21307,Virtual Box 6.1.40 r154048(Qt5.6.2) freezing,Windows,Linux,VirtualBox 6.1.40,2022-11-24T10:05:03Z,2022-11-24T10:05:03Z,"I recently upgraded VM to the summary version. Subsequently I have had guest system freezes at random times, usually when idle. I am running Linux LinuxMint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. I had on problems with previous versions.  Log should be attached.",Aiki451
21310,Linux/arm64 guest,all,Linux,VirtualBox-7.0.4,2022-11-24T13:20:48Z,2022-11-24T13:20:48Z,"hi,
please add support for guest ARM64 architecture at least with Linux (and maybe Android) as OS.

As so, as example, we can run a RaspberryOS/arm64 as guest.",Valerio Messina
21222,Issue running virtual machines with VT-X enabled,Mac OS X,Linux,VirtualBox-7.0.2,2022-11-24T15:14:44Z,2022-11-24T15:14:44Z,"Hi,

I am running macOS Ventura version 13.0, existing Ubuntu 22.04 virtual machines with nested VT-X enabled (and KVM installed), are failing to start.

Result code: VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession.

",ecer
21293,UI confused by multiple DPI settings,Windows,all,VirtualBox-7.0.4,2022-11-26T03:30:12Z,2022-11-26T03:30:12Z,"Upgrading from 6.1.x to 7.x the UI seems ""doubled in size"".
I have 3 monitors, main set to 150% scale, laterals set to 125% scale.
Seems that the UI gets confused by this (?) and ends up with very large fonts.
",EPinci
21316,"VM GUI does not open, machine visibly starting in preview",Windows,all,VirtualBox-7.0.4,2022-11-26T11:59:04Z,2022-11-26T11:59:04Z,"When clicking on the ""Start"" button for any VM in the VM Manager, it starts, but no VM control window appears. However, the machine is visibly starting in the small preview box.
I know of 2 workarounds:
1. Use RDP.
2. Close VM Manager. Restart the VBoxSDS service. Open VM Manager and wait until it appears. This fixes my problem until the host reboots.
These are the commands I run to restart the VBoxSDS service:

{{{
sc stop VBoxSDS
sc start VBoxSDS
}}}
",AptemCat
21082,"RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!",other,Linux,VirtualBox 6.1.36,2022-11-27T18:44:59Z,2022-11-27T18:44:59Z,"On VirtualBox 6.1.36, Debian, Windows builds, upon starting both exiting Debian and Ubuntu virtual machines, the warning  '''RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! ''' comes up on boot after grub2.  Porting Debian virtual machine to VMWare Workstation Pro 15.5.7, Windows 11 build base contains no such boot errors.  Creation of new Ubuntu virtual machine from latest iso , virtualbox 6.1.36 gives same warning  RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! Creation of a new Ubuntu virtual machine in VMware gives no such warning.

PHY HW is Intel i5 (i5-8250u) and cpuinfo shows no cpu_insecure flag.

Did not test a Windows virtual machine in virtualbox to see if warning occurred.  

Suspect virtualbox code base is not patched against Spectre v2 or warning message not correct in conditional tree.  

Others reporting similar, see https://ubuntuforums.org/showthread.php?t=2477938",stdperson
21317,Mac dark mode makes it impossible to read help,Mac OS X,Linux,VirtualBox-7.0.4,2022-11-28T02:10:54Z,2022-11-28T02:10:54Z,"I was trying to access the help for VB on my mac in which I run dark mode.  However dark mode only seems to apply to text in the help, resulting in white text on white background.",traisjames
21299,VirtualBox-7.0.4 kernel module build fails on RHEL9.1 host => fixed in svn,Linux,all,VirtualBox-7.0.4,2022-11-28T08:13:56Z,2022-11-28T08:13:56Z,"Upon updating from RHEL 9.0 kernel 5.14.0-70.26.1.el9_0.x86_64 (uname -rv = 5.14.0-70.26.1.el9_0.x86_64 #1 SMP PREEMPT) to RHEL9.1 kernel 5.14.0-162.6.1.el9_1.x86_64 (uname -rv = 5.14.0-162.6.1.el9_1.x86_64 #1 SMP PREEMPT_DYNAMIC), the kernel module build failed with the following message:

.....
/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltPortOsXmit’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:2327:23: error: implicit declaration of function ‘netif_rx_ni’; did you mean ‘netif_rx’? [-Werror=implicit-function-declaration]
 2327 |                 err = netif_rx_ni(pBuf);
      |                       ^~~~~~~~~~~
      |                       netif_rx
.....

I have attached vbox-setup.log for the complete build output.

I have attempted to uninstall and reinstall VBox, to no avail. The kernel module builds fine on the previously installed kernel (5.14.0-70.26.1.el9_0.x86_64). Module build fails regardless of whether I update VBox after updating the kernel or vice versa.

I should note that VBox 7.0.2 also fails to build against the new 5.14.0-162.6.1.el9_1.x86_64 kernel with the exact same failure. So does VBox 6.1.40.

",Hosstyle
20851,VBoxDispD3D.dll Crash Trying to run Flutter programs,Linux,Windows,VirtualBox 6.1.26,2022-11-28T14:19:42Z,2022-11-28T14:19:42Z,"I'm trying to build a Flutter app that can run on both Windows and Linux. I'm trying to use my Windows VM to compile the Windows version, but it crashes as it tries to launch even the default program.

I initially thought it was a Flutter problem and opened a ticket here:
https://github.com/flutter/flutter/issues/99101

To reproduce, you need to install Flutter:
https://docs.flutter.dev/get-started/install/windows

I simply created a template program using
flutter create testwin
cd testwin
flutter run

This is the error message I get when I try to debug with Visual Studio:
Unhandled exception at 0x00007FFC63716A3D (VBoxDispD3D.dll) in testwin.exe: 0xC0000094: Integer division by zero.


",Digitaleagle
21300,'Assertion Failed' in PGMHandlerPhysicalDeregister,Linux,Windows,VirtualBox-7.0.4,2022-11-28T19:06:50Z,2022-11-28T19:06:50Z,"3d mode in VirtualBox-7.0.4 works a little worse than in wine.
I tried to figure out what was wrong and installed Virtualbox with the debug flag. 
The first start of the virtual machine ended with 'Assertion Failed'. 
The problem only appears in 3d mode. 

Host: Gentoo linux

Guest: Windows 10

Backtrace:
{{{

!!Assertion Failed!!
Expression: <none>
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp(570) int PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

Didn't find range starting at 0000000136b26000

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0x7f0b504ff6c0 (LWP 613)]
0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister (pVM=0x7f0b6bbde000, GCPhys=5212626944) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
570	        AssertMsgFailed((""Didn't find range starting at %RGp\n"", GCPhys));
(gdb) bt
#0  0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS) (pVM=0x7f0b6bbde000, GCPhys=5212626944) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
#1  0x00007f0b8b839f3a in pdmR3DevHlp_PGMHandlerPhysicalDeregister(PPDMDEVINS, RTGCPHYS) (pDevIns=0x7f0b6b9b4000, GCPhys=5212626944)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMR3/PDMDevHlp.cpp:918
#2  0x00007f0b50ae8179 in PDMDevHlpPGMHandlerPhysicalDeregister(PPDMDEVINS, RTGCPHYS) (pDevIns=0x7f0b6b9b4000, GCPhys=5212626944)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/include/VBox/vmm/pdmdev.h:9514
#3  0x00007f0b50aea1d9 in vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO) (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:629
#4  0x00007f0b50aeafb8 in vmsvgaR3OTableSetOrGrow(PVMSVGAR3STATE, SVGAOTableType, PPN64, uint32_t, uint32, SVGAMobFormat, bool)
    (pSvgaR3State=0x7f0b6447f100, type=SVGA_OTABLE_SURFACE, baseAddress=1482153, sizeInBytes=16384, validSizeInBytes=8192, ptDepth=SVGA3D_MOBFMT_PTDEPTH64_1, fGrow=true)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:833
#5  0x00007f0b50af18b2 in vmsvga3dCmdGrowOTable(PVGASTATECC, SVGA3dCmdGrowOTable const*, uint32_t) (pThisCC=0x7f0b6b9b4180, pCmd=0x7f0b65773c68, cbCmd=24)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:3653
#6  0x00007f0b50afb2b7 in vmsvgaR3Process3dCmd(VGAState*, VGASTATER3*, unsigned int, SVGAFifo3dCmdId, unsigned int, void const*)
    (pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, idDXContext=4294967295, enmCmdId=SVGA_3D_CMD_GROW_OTABLE, cbCmd=24, pvCmd=0x7f0b65773c68)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:5897
#7  0x00007f0b50ad8f11 in vmsvgaR3CmdBufProcessCommands(PPDMDEVINS, PVGASTATE, PVGASTATECC, uint32_t, void const*, uint32_t, uint32_t*, uint32_t*)
    (pDevIns=0x7f0b6b9b4000, pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, idDXContext=4294967295, pvCommands=0x7f0b65773a70, cbCommands=528, poffNextCmd=0x7f0b504feb18, pu32IrqStatus=0x7f0b504feb1c)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:3805
#8  0x00007f0b50ad9423 in vmsvgaR3CmdBufProcessBuffers(PPDMDEVINS, PVGASTATE, PVGASTATECC, PPDMTHREAD) (pDevIns=0x7f0b6b9b4000, pThis=0x7f0b6b9b4840, pThisCC=0x7f0b6b9b4180, pThread=0x7f0b644b0ee0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:3909
#9  0x00007f0b50adc420 in vmsvgaR3FifoLoop(PPDMDEVINS, PPDMTHREAD) (pDevIns=0x7f0b6b9b4000, pThread=0x7f0b644b0ee0)
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA.cpp:4759
#10 0x00007f0b8b8844fd in pdmR3ThreadMain(RTTHREAD, void*) (Thread=0x7f0b644b1100, pvUser=0x7f0b644b0ee0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMR3/PDMThread.cpp:790
#11 0x00007f0be4509d6e in rtThreadMain(PRTTHREADINT, RTNATIVETHREAD, char const*) (pThread=0x7f0b644b1100, NativeThread=139686568785600, pszThreadName=0x7f0b644b19e0 ""VMSVGA FIFO"")
    at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Runtime/common/misc/thread.cpp:759
#12 0x00007f0be4693b84 in rtThreadNativeMain(void*) (pvArgs=0x7f0b644b1100) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Runtime/r3/posix/thread-posix.cpp:430
#13 0x00007f0be48e2d6a in start_thread () at /lib64/libc.so.6
#14 0x00007f0be49620ac in clone3 () at /lib64/libc.so.6
(gdb) c
Continuing.

!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp(630) void vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

VERR_PGM_HANDLER_NOT_FOUND (-1607) - Specified access handler was not found.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b50aea251 in vmsvgaR3GboDestroy (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:630
630	                AssertRC(rc);
(gdb) c
Continuing.

!!Assertion Failed!!
Expression: <none>
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp(570) int PGMHandlerPhysicalDeregister(PVMCC, RTGCPHYS)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

Didn't find range starting at 0000000132627000

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b8bb68403 in PGMHandlerPhysicalDeregister (pVM=0x7f0b6bbde000, GCPhys=5140279296) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/VMM/VMMAll/PGMAllHandler.cpp:570
570	        AssertMsgFailed((""Didn't find range starting at %RGp\n"", GCPhys));
(gdb) c
Continuing.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

!!Assertion Failed!!
Expression: RT_SUCCESS_NP(rc)
Location  : /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp(630) void vmsvgaR3GboDestroy(PVMSVGAR3STATE, PVMSVGAGBO)
Stack     :
00007f0be44cf7d0 VBoxRT.so!RTAssertMsg2V+0x3f7 (rva:0x28e7d0)

VERR_PGM_HANDLER_NOT_FOUND (-1607) - Specified access handler was not found.
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)

Thread 46 ""VMSVGA FIFO"" received signal SIGTRAP, Trace/breakpoint trap.
0x00007f0b50aea251 in vmsvgaR3GboDestroy (pSvgaR3State=0x7f0b6447f100, pGbo=0x7f0b644801f0) at /var/tmp/portage/app-emulation/virtualbox-7.0.4/work/VirtualBox-7.0.4/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp:630
630	                AssertRC(rc);
(gdb) c

}}}


I found and fixed two bugs: 
{{{
--- a/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp	2022-11-17 22:12:54.000000000 +0300
+++ b/src/VBox/Devices/Graphics/DevVGA-SVGA-cmd.cpp	2022-11-23 13:42:19.327889043 +0300
@@ -463,6 +463,8 @@
 
     uint32_t const cPPNsPerPage = X86_PAGE_SIZE / (fGCPhys64 ? sizeof(PPN64) : sizeof(PPN));
 
+    RT_ZERO(*pGbo);
+
     pGbo->cbTotal = sizeInBytes;
     pGbo->cTotalPages = (sizeInBytes + X86_PAGE_SIZE - 1) >> X86_PAGE_SHIFT;
 
@@ -631,7 +633,7 @@
             }
         }
         RTMemFree(pGbo->paDescriptors);
-        RT_ZERO(pGbo);
+        RT_ZERO(*pGbo);
     }
 }
 
}}}

At least now the debug version starts without exceptions.",pv32768
21097,Automatic update of VBox and Failed to open a session for the virtual machine Ubuntu => fixed in SVNsvn,Windows,Linux,VirtualBox 6.1.38,2022-11-29T03:04:01Z,2022-11-29T03:04:01Z,"Few weeks ago, when I had updated VirtualBox, I had faced an error with opening a session for the virtual machine (guest OS is Ubuntu).
Found a suggestion that VBox version 6.1.32 is good and I had downgraded the VBox and everything works fine, I can start a session for the VM.
I had turned off the automatic update of VirtualBox, but few times since then, VirtualBox was updated automatically to the newest version.

For some, unknown to me reason, I can't use the newest VBox version, but my VBox keep upgrading even when automatic update is turned off.
What is the solution? Should I downgrade my VBox every day?",AZidai
21182,"EventID 15, ""The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer""",all,Windows,VirtualBox-7.0.2,2022-11-30T05:22:35Z,2022-11-30T05:22:35Z,"Each Windows 11 22H2 boot generates six of these TPM errors.

Please fix.",Artem S. Tashkinov
20573,Virtio-scsi shows HDD instead of SSD Virtualbox 6.1.97 r146677,other,Windows,VirtualBox 6.1.26,2022-11-30T12:05:42Z,2022-11-30T12:05:42Z,"Issue:
in Virtualbox 6.1.97 r146677 I've set Virtio-scsi as disk and flagged it as Solid State Drive inside Virtualbox, however Windows 10 x64 Enterprise sees it as HDD...
(Yes the latest virtio drivers are installed in Windows 10)

[[Image(https://forums.virtualbox.org/download/file.php?id=44340)]]
[[Image(https://forums.virtualbox.org/download/file.php?id=44341)]]

Operative System:

Host  - Fedora Workstation 34 x64
Guest - Windows 10 x64 Enterprise

Virtio Drivers version: 2021-09-13 05:07
From:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.208-1/


How to reproduce:
create a virtual machine and install Windows 10 x64 using IDE or Sata.
Install the Virtualbox guest additions.
Insert an empty Virtio-scsi disk and install the virtio drivers.
Shut down the Virtual Machine.
Change the IDE or Sata disk to Virtio-scsi and flag ""Solid State Drive"" in the Virtualbox UI.
Boot the Windows 10 x64 VM.
Open the Task Manager Windows and it will show HDD.",FranceBB
21319,Ring Zero Assertion Error on virtual machine after upgrade to 7.0.x,Linux,Windows,VirtualBox-7.0.4,2022-11-30T14:14:53Z,2022-11-30T14:14:53Z,"Not sure about the trigger - sometimes hangs in 30 minutes, sometimes an hour. The machine was created in 6.1.34. The machine will hang in a fresh reboot of devuan (host) with nothing else running on either host or guest (Win7), excepting some autostarted license management servers.

Working on a core dump for you guys now.",nobodyreally
16296,Left half portion of the guest's widescreen desktop becomes unresponsive to left mouse button clicks,Windows,Linux,VirtualBox 5.1.10,2022-11-30T22:57:40Z,2022-11-30T22:57:40Z,"I am not sure what causes this or how to manually reproduce this behavior; otherwise, I would have reported this issue a long time ago.  Almost every day (and after no particular amount of up-time), the left half of my Linux desktop becomes unresponsive to left mouse button clicks.  Left-mouse button clicks do continue to work on the right half portion of the screen.  Actually, it is not the entire left-half portion of the screen that is affected; more like approximately the left two/fifths (left 40%) portion of the entire screen.

This problem is very annoying because smaller windows running in the affected portion of the screen cannot be interacted with or dragged over to the responsive side of the screen.

When this problem occurs, nothing I have tried so far (e.g. restarting the window manager) will correct it.  I am forced to close out (as best as I can) all the running applications in the Linux guest and then reboot the guest OS.

I have no idea what is causing this.  A faulty screensaver timeout process?  Your guess is as good as mine.

Some specific details of my setup:

* Guest OS: 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
* Guest window manager: Openbox 3.5.2
* Host OS: Windows 7 Enterprise 64-bit
* Host configuration: dual identical DELL P2414H widescreen monitors (1920x1080 resolution); VirtualBox is running as a maximized window on my right-side monitor

I believe that this strange behavior has been happening as far back as version 5.0.20 of Virtual Box.",Tony DeFusco
21323,Non-mouse Integration,Windows,all,VirtualBox-7.0.4,2022-12-01T02:00:54Z,2022-12-01T02:00:54Z,"I have noticed that whenever I disable mouse integration on my virtual machines, my mouse would jump to the top left corner of my screen when I captured it. If I re-enable mouse integration it works as expected. Looking through the logs, I don't notice anything unusual, but I've attached them anyway. I've used a Windows 10 virtual machine as my test.",Harvey Walker
21321,Compiling the kernel-modules fails with error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared,Linux,all,VirtualBox-7.0.4,2022-12-01T19:08:04Z,2022-12-01T19:08:04Z,"The compilation fails with:

vboxdrv/include/VBox/vmm/hm_vmx.h:532:29: error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared here (not in a function); did you mean ‘VMX_BF_EPT_PT_READ_MASK’?
  532 | RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,

The line in hm_vmx.h which is causing this:

RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,
                            (READ, WRITE, EXECUTE, MEMTYPE, IGNORE_PAT, IGN_7, ACCESSED, DIRTY, EXECUTE_USER, IGN_59_11,
                            SUPER_SHW_STACK, IGN_62_61, SUPPRESS_VE));

The cause is that the C preprocessor is replacing READ with '0' (and WRITE with '1') due to the linux kernel header file: tools/virtio/linux/kernel.h

which has (line 29):
/* generic data direction definitions */
#define READ                    0
#define WRITE                   1

I would say this is an unintended side effect and a small rename of the variables in hm_vmx.h would fix this

Apparently a workaround (https://bugs.gentoo.org/880229) is to set the Linux kernel config option CONFIG_JUMP_LABEL but I did not test this yet",gentoo-bird
18176,USB resets and hangs during high I/O,Mac OS X,Linux,VirtualBox 5.2.22,2022-12-03T15:52:56Z,2022-12-03T15:52:56Z,"Experiencing USB reset and hangs on Virtualbox 5.2.22 on Macbook Pro 2017 10.13.6, on Oracle Linux 7.5 and Ubuntu 18.04 VMs.  I'm able to replicate the problem, very quickly, by running the following:
{{{
$ sudo dd if=/dev/zero of=./testfile status=progress bs=1024k
639631360 bytes (640 MB) copied, 5.448752 s, 117 MB/s
}}}
It starts out pretty fast, but once the reset occurs, the speeds taper down to < 50MB/s.  The OL system log shows the resets and I/O errors as:
{{{
Dec 10 15:55:28 jdnissen-lobi7 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
Dec 10 15:55:38 jdnissen-lobi7 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
Dec 10 15:55:44 jdnissen-lobi7 systemd: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1858 (cma)
Dec 10 15:55:44 jdnissen-lobi7 systemd: Mounting Arbitrary Executable File Formats File System...
Dec 10 15:55:45 jdnissen-lobi7 systemd: Mounted Arbitrary Executable File Formats File System.
Dec 10 15:55:46 jdnissen-lobi7 kernel: EXT4-fs (dm-3): Delayed block allocation failed for inode 12 at logical offset 546816 with max blocks 2048 with error 5
Dec 10 15:55:46 jdnissen-lobi7 kernel: EXT4-fs (dm-3): This should not happen!! Data will be lost
Dec 10 15:55:46 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:55:51 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:55:57 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:01 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:07 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:12 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:17 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:22 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:27 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:32 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
}}}
I've attempted to workaround this with the new test build 6.0.0 RC1, and it didn't help.  OL and Ubuntu updates don't help, either.

It's happening on two different USB drives:  Seagate 2TB and Western Digital 2TB.  The seagate is formatted as NTFS and the WD is Linux EXT4.  

In addition, I can attach the drives to an old laptop running bare-metal OL7.2, and it works just fine...no resets, hangs, or slow I/Os, during the 'dd' (or file copies).

I work for Oracle, and this problem is preventing me from being able to copy large patch bundles, used during customer installs.


",Jimson
21324,Carbon Black EDR: VirtualBox VMs Fail to Start After Windows Sensor Upgrades to 7.3.0,Windows,all,VirtualBox-7.0.4,2022-12-05T14:00:00Z,2022-12-05T14:00:00Z,"https://community.carbonblack.com/t5/Knowledge-Base/EDR-VirtualBox-VMs-Fail-to-Start-After-Windows-Sensor-Upgrades/ta-p/113625

Environment
EDR Windows Sensor:  7.3.0
Virtual Box: 6.1.34

Symptoms
VirtualBox VMs do not start if the Windows host is running EDR win-7.3.0.

Cause
VirtualBox hardening script may have issues with the updated, secure signed certificate on the CB win-7.3.0 cbedramsi.dll file.

Resolution
Until VirtualBox hardening script permits the new signed certificate, the Windows host should stay on EDR win-7.2.2.
VMs within VMware Workstation or Microsoft HyperV start properly when the Windows host is running EDR win-7.3.0.

Additional Notes
CB win-7.3.0 uses a new more secure certificate; SHA2 384bit Sectigo CA with integrity checks.
If a case is opened with Virtual Box, VMware Carbon Black Support and Engineers could provide additional information.  
 
",neglas
18695,Guest’s audio output is stuck after the host output device was changed.,Windows,Windows,VirtualBox 6.0.8,2022-12-06T02:39:19Z,2022-12-06T02:39:19Z,"This is a new issue caused by some changes in November 2018. Those changes were done because of the issues in ticket #17225. Because the issues of the other ticket are solved and this is just follow-up issues caused by the changes in the other ticket, I open this one just for those issues.

The issue was already described in the old ticket, I also put some logs there, so I kinda link there for further information and logs (see comment 74 and some previous ones in #17225 for example). Some brief description: as soon as one changes the audio output device on the host (speakers to head phone or Bluetooth; or in the other direction), the guest’s audio output is simply stuck forever in the last second on the old device. The solution is always tricky, I described some of the working ones in the comments of ticket #17225. Sometimes only help is the guest’s reboot.",boxer01
21325,Enhancement: enable high refresh rates (frame rates?) in guests,other,Windows,VirtualBox-7.0.4,2022-12-06T02:47:35Z,2022-12-06T02:47:35Z,"From what I understand, VirtualBox caps the refresh rate (or frame rate - not sure which terminology is correct) of the guest's display to 60Hz, and attempting to force any refresh rates higher than that is pointless.

This results in a very noticeable drop in smoothness when using the guest operating system on a host machine with a high refresh rate.

Simple tasks such as dragging or resizing GUI windows are noticeably laggier than on the host OS.

For example, I'm using a Windows host on a monitor which supports 200Hz. The host OS feels far, far more responsive and enjoyable to use than any of the guest machines.

I am not a VirtualBox developer so I don't know the technical details, but it would be great if it was possible to allow VirtualBox guests to output higher refresh/frame rates, up to and including the refresh rate set on the host OS.",Jenkins1
21329,Help doc comes up behind new VM dialog and can't be accessed,Windows,other,VirtualBox-7.0.4,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
21242,Windows 11 screen freeze with CPUs 100% busy,Linux,Windows,VirtualBox-7.0.2,2022-12-09T22:02:55Z,2022-12-09T22:02:55Z,"Linux-Host with Win11 as guest: After an upgrade from the latest Windows 10 to Windows 11 22H2 the screen and with this the complete guest freezes with no further actions possible (except PowerOff/reboot).
This happend twice (= always up to now) within 4 minutes after power on and login.",snoopy2601
21331,"Delete of a VM does not delete unattended files, so can't recreate VM",Windows,other,VirtualBox-7.0.4,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
21330,Switching between Guided and Expert mode clears populated fields,Windows,other,VirtualBox-7.0.4,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
17708,I18N progress 4.0,other,other,,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
21335,can't see guest OS mapped network drives in File Manager - regression,Windows,Windows,VirtualBox-7.0.4,2022-12-12T15:40:17Z,2022-12-12T15:40:17Z,"VB 7.0.4, W10 guest OS.
In the bridged network guest, map a drive to a server on your network - e.g., y:\\myserver\myshare.  (server credentials are different than guest OS credentials)
Start File Mgr, login - observe the Y drive is not shown.  This worked in 6.0.",Justinh
20758,Crash due to uncaught exception 'NSInvalidArgumentException',Mac OS X,other,VirtualBox 6.1.30,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
20520,White screen when 3D Acceleration enabled,Windows,Linux,VirtualBox 6.1.26,2022-12-13T07:38:20Z,2022-12-13T07:38:20Z,"I get a white desktop screen after logging into Linux with 3D Acceleration enabled.

VM was working as expected until the August update to VirtualBox.

VirtualBox Version 6.1.26 r145957 (Qt5.6.2)
Oracle VM VirtualBox Extension Pack (Version: 6.1.26 r145957; VRDE Module: VBoxVRDP)

{{{
00:00:19.820085 VMSVGA3d: cap[9]=failed rc=VERR_INVALID_PARAMETER! {S23E8_TEXTURES}
00:00:19.820088 VMSVGA3d: cap[10]=failed rc=VERR_INVALID_PARAMETER! {S10E5_TEXTURES}
00:00:19.820301 VMSVGA3d: cap[62]=failed rc=VERR_INVALID_PARAMETER! {MISSING62}
00:00:19.820348 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:19.820350 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}

00:00:20.333005 GUI: 2D video acceleration is disabled

00:04:46.441670 VMSVGA: PIXEL shader: Failed to create:
00:04:46.441718 0xFFFF0300, 0x0200001F, 0x80010005, 0x900F0000, 0x05000051, 0xA00F0001, 0x00000000, 0x3F000000,
00:04:46.441828 0xBF800000, 0x3F800000, 0x0200001F, 0x80000000, 0xA00F0800, 0x03000042, 0x800F0003, 0x90E40000,
00:04:46.441939 0xA0E40800, 0x02000001, 0x80080000, 0x80E40003, 0x02000001, 0x80070000, 0xA0000001, 0x03000005,
00:04:46.442043 0x800F0001, 0xA0E40000, 0x80FF0000, 0x02000001, 0x800F0002, 0x80E40001, 0x02000001, 0x800F0800,
00:04:46.442146 0x80E40002, 0x0000FFFF,

}}}",Lynda
21327,macosx M2 Unable to import OVA with error NS_ERROR_INVALID_ARG,other,other,VirtualBox-7.0.4,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
21312,USB Device unknown,Linux,Windows,VirtualBox-7.0.4,2022-12-13T15:33:13Z,2022-12-13T15:33:13Z,"Windows7 x64 is installed on the guest system, after applying the VirtualBox 7.0.x update, there were problems with the USB device enumerator. If the memory on the guest system is less than 2068Mb, then everything works (found out experimentally). If you set more memory (2068Mb or more), then when connecting USB devices (barcode scanner, smartphone, etc.), error Code 43 occurs and the device manager identifies the equipment as USB/Unknown.",CrayZD
21328,Update to 7.0.4 seems to crash after lacking 6.1.38?,Linux,Windows,VirtualBox-7.0.4,2022-12-13T15:53:52Z,2022-12-13T15:53:52Z,"I loved Virtual Box and did neglect updating-problems. My favorite forum does not have a clue why 7.0.4 fails as follows:

{{{
BuschBo:~> VirtualBox 
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: nouveau
Qt WARNING: QObject::connect: No such signal UITabBar::currentChanged(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabMoved(int,int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarClicked(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarDoubleClicked(int)
/usr/bin/VirtualBox: Zeile 70:  9312 Speicherzugriffsfehler  (Speicherabzug geschrieben) LD_LIBRARY_PATH=""/usr/lib/virtualbox${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"" /usr/lib/virtualbox/VirtualBox6 $@

BuschBo:~> systemctl status vboxdrv.service
● vboxdrv.service - VirtualBox Linux kernel module
     Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; disabled; vendor preset: disabled)
     Active: active (exited) since Fri 2022-12-09 18:45:05 CET; 34min ago

BuschBo:~> uname -a
Linux BuschBo 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux

BuschBo:~> zypper se -si virtualbox vbox
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                   | Type  | Version                                   | Arch   | Repository
---+------------------------+-------+-------------------------------------------+--------+-----------------------
i+ | virtualbox             | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 7.0.4_k5.14.21_150400.24.33-lp154.2.20.2  | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 6.1.38_k5.14.21_150400.24.21-lp154.2.15.1 | x86_64 | Main Update Repository
i  | virtualbox-qt          | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository

BuschBo:~> zypper lr -d
#  | Alias                       | Name                                                                                        | Enabled   | GPG Check       | Refresh        | Priority  | Type   | URI                                                                                                                                                                              | Serv->
---+-----------------------------+---------------------------------------------------------------------------------------------+-----------+-----------------+----------------+-----------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------
 1 | openSUSE-Leap-15.4-1        | openSUSE-Leap-15.4-1                                                                        | Nein      | ----            | ----           |   99      | rpm-md | hd:/?device=/dev/disk/by-id/usb-SanDisk_Ultra_05019bbc553237f7fd551958a91e01fe4ded604716e4280b429924ea2772cd6d46f90000000000000000000010702a2300961a10815581071ea825d9-0:0-part2 | 
 2 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/update/leap/15.4/backports_debug/                                                                                                                   | 
 3 | repo-backports-update       | Update repository of openSUSE Backports                                                     | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/                                                                                                                         | 
 4 | repo-debug                  | Debug Repository                                                                            | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/                                                                                                              | 
 5 | repo-debug-non-oss          | Debug Repository (Non-OSS)                                                                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/                                                                                                          | 
 6 | repo-debug-update           | Update Repository (Debug)                                                                   | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/oss/                                                                                                                         | 
 7 | repo-debug-update-non-oss   | Update Repository (Debug, Non-OSS)                                                          | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/non-oss/                                                                                                                     | 
 8 | repo-non-oss                | Non-OSS Repository                                                                          | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/                                                                                                                | 
 9 | repo-oss                    | Main Repository                                                                             | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/                                                                                                                    | 
10 | repo-sle-debug-update       | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/sle/                                                                                                                         | 
11 | repo-sle-update             | Update repository with updates from SUSE Linux Enterprise 15                                | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/                                                                                                                               | 
12 | repo-source                 | Source Repository                                                                           | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/                                                                                                             | 
13 | repo-update                 | Main Update Repository                                                                      | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/oss                                                                                                                                | 
14 | repo-update-non-oss         | Update Repository (Non-Oss)                                                                 | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/                                                                                                                           | 
}}}",Christiann
21336,VirtualBox 7.0.2 interferes with LG Curved UltraWide 40WP95C audio,Windows,Linux,VirtualBox-7.0.2,2022-12-13T18:39:05Z,2022-12-13T18:39:05Z,"I recently bought a LG Curved UltraWide 40WP95C monitor which is hooked up via DisplayPort to an NVidia 1080 graphics card. I use the built-in speakers in the monitor, which appear as 'LG ULTRAWIDE (NVIDIA High Definition Audio)'

System worked fine until I upgraded to VirtualBox 7.0.2 from 6.1.30. After this the audio device above would disappear if the screen blanked. On unblanking, Windows would have selected a different output device. To get the audio device back I had to start the Windows Device Manager and do a 'Scan for hardware changes'. This then found the device which I could then re-select as the output device.

A few seconds after doing the 'Scan for hardware changes' aI would get an error saying 'USB device not recognized', and an 'Unknown USB Device (Port Reset Failed)' would appear in the Device Manager under 'USB controllers'. Looking in the Windows Event Viewer I found an Error, Information and Error at the approx time this occurred. The messages below have a vendor id in them that maps to Virtual Box.


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\Vid_80EE&Pid_CAFE\5&9a1cce4&0&6
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: 
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719

# information

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was configured.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1949
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\5&24955ba6&0&0


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x2B
Problem Status: 0x0


After uninstalling VirtualBox completely the problem disappeared and the 'LG ULTRAWIDE (NVIDIA High Definition Audio)' device has remained available, and selected as the default device, whenever the screen blanks.
",DaveCleland
21337,Guest start aborted every time when bridged network interface name changes,Linux,all,VirtualBox-7.0.4,2022-12-13T20:41:08Z,2022-12-13T20:41:08Z,"Attaching to physical interface via bridge adapter may cause guest to crash at start up. Every time when laptop is connected to docking station the network interface changes under Linux.

The error message displayed with VB 6.1. There one can change the network settings by pressing ""Change Network Settings"" button. With VB 7.0 the VM simply crashed after that button has been pressed.",EmergReanimator
21340,VM crashes while upgrading GuestAdditions to 7.0.4,Windows,Windows,VirtualBox-7.0.4,2022-12-15T09:05:34Z,2022-12-15T09:05:34Z,What the title says. Attaching logs...,Wand
21284,Bridge Adapter not Connecting in Virtualbox 7.x,other,other,VirtualBox-7.0.4,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
21343,Keeps losing linked disk,Windows,other,VirtualBox-7.0.4,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
21344,Machine became unstable after multiple save and restore,Linux,Windows,VirtualBox 6.1.40,2022-12-16T17:04:54Z,2022-12-16T17:04:54Z,"Hello,[[BR]]

My machine work good but when i make many time action stop by save state and resume [[BR]]
state or after some time then my guest machine has problem :[[BR]]

_Flicking mouse cursor[[BR]]

_Click don't respond when i execute more windows processus[[BR]]


I reboot my guest machine then same problem.[[BR]]

I shutdown my guest machine and restart then no problem.[[BR]]

",Sizy458
21233,VirtualBox 7.0.x 3D acceleration produces artifacts with Windows guest,Linux,Windows,VirtualBox-7.0.2,2022-12-18T12:01:25Z,2022-12-18T12:01:25Z,"Using a Linux (manjaro) host with Intel Haswell graphics and X11 (not Wayland).

Just upgraded from 6.1 to 7.0 and tried to use a Windows 11 guest known to work well with 6.1.

- Initially the Windows 11 guest was not even starting;
- Disabling 3D acceleration made it start;
- Updating the Guest Additions allowed to re-enable 3D acceleration without boot failures however, there are all sort of visual artifacts and prominently, characters become unreadable.

I suspect this may be triggered by my specific graphics card or graphics stack.",sercallegar
21345,Deleting running VM snapshot leaves the .sav file on disk,Windows,Windows,VirtualBox-7.0.4,2022-12-18T16:39:15Z,2022-12-18T16:39:15Z,"The snapshot file for running VM (.sav) remains on the disk after deleting the snapshot. Issue appeared with 7.0.4 and was not there in 6.1.xx.

I have multiple running VM snapshots so it takes time and effort to identify the unused .sav files and delete them manually.

Issue is replicated easily as mentioned on the [https://forums.virtualbox.org/viewtopic.php?f=6&t=108066 forum's thread].",AmirPK
21338,Kernel Panic Boot2Docker Distro,Windows,Linux,VirtualBox-7.0.4,2022-12-19T01:57:35Z,2022-12-19T01:57:35Z,Please see this [https://github.com/hashicorp/vagrant/issues/13011 Vagrant bug report]. The comment by phinze suggests this is a VirtualBox issue.,goldfita
21339,"USB Filter PortNumber field formatting for ports higher than 9 => fixed in SVN/next 7.0.x,6.1.x maintenance",Windows,Windows,VirtualBox 6.1.36,2022-12-19T08:54:13Z,2022-12-19T08:54:13Z,"Inability to insert a PortNumber higher than 9, the ""Port"" field of the USB Filter only accepts numeric characters, this makes the insertion of port numbers higher than 9 not possible, considering that this field reads hexadecimal inputs, the insertion of a port number like 13(000d) not possible.
As a workaround, manual input of the hex value in the .vbox file of the guest works.

For further information: https://forums.virtualbox.org/viewtopic.php?f=6&t=108063",fantinel
20824,Reproducible split lock / freeze,Linux,Windows,VirtualBox 6.1.32,2022-12-19T20:44:58Z,2022-12-19T20:44:58Z,"When attempting to install Visual Studio in a Windows 7 x64 or Windows 10 x64 guest with Ubuntu 20.04.1 w/ hwe host, installer freezes during file extraction and VM is unresponsive and cannot be recovered without killing the VM.

The origin of the error is a split lock, for example:

{{{
Feb  9 08:23:09 Laptop2021 kernel: [333455.818444] Split lock detected
Feb  9 08:23:09 Laptop2021 kernel: [333455.818444] : 0000 [#1] SMP NOPTI
Feb  9 08:23:09 Laptop2021 kernel: [333455.818450] CPU: 1 PID: 1510081 Comm: EMT Tainted: P           O      5.13.0-28-generic #31~20.04.1-Ubuntu
Feb  9 08:23:09 Laptop2021 kernel: [333455.818452] Hardware name: Dell Inc. XPS 13 9310 2-in-1/0W6MV0, BIOS 2.7.0 12/11/2021
Feb  9 08:23:09 Laptop2021 kernel: [333455.818453] RIP: 0010:0xffffa4346aa02680
Feb  9 08:23:09 Laptop2021 kernel: [333455.818456] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
Feb  9 08:23:09 Laptop2021 kernel: [333455.818458] RSP: 0018:ffffa43448393928 EFLAGS: 00010206
Feb  9 08:23:09 Laptop2021 kernel: [333455.818460] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818461] RDX: 0000000000000000 RSI: ffffa43448393948 RDI: ffff93cf3a781e7c
Feb  9 08:23:09 Laptop2021 kernel: [333455.818462] RBP: ffffa43448486000 R08: ffffa43448393838 R09: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818463] R10: ffffa4344839393c R11: ffffa43448393958 R12: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818463] R13: ffffa43448393b38 R14: ffffa43448486000 R15: ffffa43448475000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818464] FS:  00007f5e75dfb700(0000) GS:ffff93d27f680000(0000) knlGS:fffff80002a2c000
Feb  9 08:23:09 Laptop2021 kernel: [333455.818466] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb  9 08:23:09 Laptop2021 kernel: [333455.818467] CR2: 000000006e0c096c CR3: 00000003e3316001 CR4: 0000000000772ee0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818468] PKRU: 55555554
Feb  9 08:23:09 Laptop2021 kernel: [333455.818469] Call Trace:
Feb  9 08:23:09 Laptop2021 kernel: [333455.818470]  <TASK>
Feb  9 08:23:09 Laptop2021 kernel: [333455.818472]  ? sched_clock+0x9/0x10
Feb  9 08:23:09 Laptop2021 kernel: [333455.818476]  ? sched_clock_cpu+0x11/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818478]  ? newidle_balance+0x1e9/0x3f0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818481]  ? schedule_hrtimeout_range_clock+0xa0/0x110
Feb  9 08:23:09 Laptop2021 kernel: [333455.818484]  ? hrtimer_init_sleeper+0x80/0x80
Feb  9 08:23:09 Laptop2021 kernel: [333455.818486]  ? finish_wait+0x5c/0x70
Feb  9 08:23:09 Laptop2021 kernel: [333455.818494]  ? rtR0SemEventMultiLnxWait.isra.0+0x283/0x3c0 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818509]  ? wait_woken+0x80/0x80
Feb  9 08:23:09 Laptop2021 kernel: [333455.818512]  ? SUPR0GetCurrentGdtRw+0xe/0x10 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818519]  ? VBoxHost_RTThreadCtxHookEnable+0x31/0x50 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818531]  ? supdrvIOCtlFast+0x66/0xb0 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818539]  ? VBoxDrvLinuxIOCtl_6_1_32+0x56/0x260 [vboxdrv]
Feb  9 08:23:09 Laptop2021 kernel: [333455.818546]  ? __x64_sys_ioctl+0x91/0xc0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818549]  ? do_syscall_64+0x61/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818552]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818553]  ? syscall_exit_to_user_mode+0x27/0x50
Feb  9 08:23:09 Laptop2021 kernel: [333455.818555]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818557]  ? do_syscall_64+0x6e/0xb0
Feb  9 08:23:09 Laptop2021 kernel: [333455.818558]  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
Feb  9 08:23:09 Laptop2021 kernel: [333455.818564]  ? entry_SYSCALL_64_after_hwframe+0x44/0xae
Feb  9 08:23:09 Laptop2021 kernel: [333455.818566]  </TASK>
Feb  9 08:23:09 Laptop2021 kernel: [333455.818567] Modules linked in: snd_usb_audio snd_usbmidi_lib r8153_ecm cdc_ether usbnet r8152 mii vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_hdmi snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg mei_hdcp snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr snd_hda_core snd_hwdep snd_pcm snd_seq_midi uvcvideo snd_seq_midi_event videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_rawmidi mc btusb btrtl dell_laptop snd_seq ledtrig_audio dell_smm_hwmon btbcm btintel intel_tcc_cooling snd_seq_device x86_pkg_temp_thermal snd_timer
Feb  9 08:23:09 Laptop2021 kernel: [333455.818615]  intel_powerclamp coretemp bluetooth kvm_intel snd dell_wmi iwlmvm kvm mac80211 intel_cstate ecdh_generic ecc hid_sensor_magn_3d libarc4 input_leds dell_smbios efi_pstore dcdbas iwlwifi serio_raw dell_wmi_sysman dell_wmi_descriptor wmi_bmof hid_sensor_als hid_sensor_incl_3d hid_sensor_rotation hid_sensor_custom_intel_hinge hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_trigger soundcore industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio cfg80211 intel_pmt_telemetry hid_multitouch processor_thermal_device mei_me mei processor_thermal_rfim joydev processor_thermal_mbox processor_thermal_rapl intel_pmt_class intel_rapl_common cros_ec_ishtp cros_ec intel_soc_dts_iosf ucsi_acpi typec_ucsi typec intel_hid int3403_thermal soc_button_array int340x_thermal_zone sparse_keymap acpi_pad mac_hid acpi_tad int3400_thermal acpi_thermal_rel sch_fq_codel sunrpc msr parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO)
Feb  9 08:23:09 Laptop2021 kernel: [333455.818649]  icp(PO) zcommon(PO) znvpair(PO) spl(O) dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid wacom usbhid hid_generic i915 crct10dif_pclmul crc32_pclmul i2c_algo_bit ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea rtsx_pci_sdmmc sysfillrect crypto_simd nvme sysimgblt i2c_i801 fb_sys_fops cryptd intel_lpss_pci intel_lpss i2c_smbus intel_ish_ipc cec psmouse rc_core nvme_core rtsx_pci idma64 i2c_hid_acpi xhci_pci intel_ishtp drm i2c_hid thunderbolt xhci_pci_renesas intel_pmt wmi hid pinctrl_tigerlake video
Feb  9 08:23:09 Laptop2021 kernel: [333455.818672] ---[ end trace e310c2a1fbafbaa6 ]---
Feb  9 08:23:09 Laptop2021 kernel: [333456.044605] RIP: 0010:0xffffa4346aa02680
Feb  9 08:23:09 Laptop2021 kernel: [333456.044612] Code: 89 02 c3 cc cc cc cc 53 49 89 ca 49 89 d3 41 8b 1b 41 8b 4b 04 9c 41 8b 02 83 24 24 bf 83 e0 40 48 09 04 24 9d 8b 06 8b 56 04 <f0> 0f c7 0f 89 06 89 56 04 9c 41 5b 41 8b 02 83 e0 bf 41 83 e3 40
Feb  9 08:23:09 Laptop2021 kernel: [333456.044614] RSP: 0018:ffffa43448393928 EFLAGS: 00010206
Feb  9 08:23:09 Laptop2021 kernel: [333456.044616] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044617] RDX: 0000000000000000 RSI: ffffa43448393948 RDI: ffff93cf3a781e7c
Feb  9 08:23:09 Laptop2021 kernel: [333456.044618] RBP: ffffa43448486000 R08: ffffa43448393838 R09: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044619] R10: ffffa4344839393c R11: ffffa43448393958 R12: 0000000000000000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044619] R13: ffffa43448393b38 R14: ffffa43448486000 R15: ffffa43448475000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044620] FS:  00007f5e75dfb700(0000) GS:ffff93d27f680000(0000) knlGS:fffff80002a2c000
Feb  9 08:23:09 Laptop2021 kernel: [333456.044621] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb  9 08:23:09 Laptop2021 kernel: [333456.044622] CR2: 000000006e0c096c CR3: 00000003e3316002 CR4: 0000000000772ee0
Feb  9 08:23:09 Laptop2021 kernel: [333456.044623] PKRU: 55555554
}}}

Other split_lock traces have different detailed call stacks, but the reproducer below causes a split_lock 100% of the time.

Steps to reproduce:

Hardware: XPS 9310, Ubuntu 20.04.1 w/ HWE kernel host, Virtualbox 6.1.32

1. Install Windows 10 x64 20H2 in virtualbox (all default options).

2. Download the visual studio tools installer in guest: https://aka.ms/vs/15/release/vs_buildtools.exe

3. Attempt installation:
vs_buildtools.exe --wait --norestart --nocache modify --installPath ""%ProgramFiles%\Microsoft Visual Studio\2017\BuildTools"" --add Microsoft.VisualStudio.Workload.MSBuildTools --add Microsoft.VisualStudio.Workload.VCTools --lang en-US

This occurs independent of video driver (VMSVGA, VBoxSVGA).",tmcqueen
21280,Host Only Network Blocked by VPN,Mac OS X,all,VirtualBox-7.0.2,2022-12-20T01:56:08Z,2022-12-20T01:56:08Z,"Many VPNs, such as Palo Alto GlobalConnect, mask routes in order to avoid split networks. This breaks Host-only Networks on virtual machines.

Once the VPN is connected all of the bridge interfaces used to dynamically mange Host-only Networks are routed through the VPN instead of locally to the virtual machines.

Prior to VirtualBox 7, Host-only Adapters were available, which worked consistently even when a VPN had locked the route table.

Here is an example of what GlobalProtect does to the route tables on Windwos and macOS to avoid split networks.

https://knowledgebase.paloaltonetworks.com/kCSArticleDetail?id=kA10g000000ClTm

This is particularly troublesome for macOS users because upgrading to Ventura (macOS 13) breaks VirtualBox 6.x, so an upgrade to VirtualBox 7 is required.",chuckwolber
21322,VM loses connection to Host,Windows,Windows,VirtualBox-7.0.4,2022-12-20T09:13:49Z,2022-12-20T09:13:49Z,"After some time the guest OS (Windows 11 Pro 22H2 22621.819 Windows Feature Experience Pack 1000.22636.1000.0) loses connection to the host OS (Windows 11 Enterprise 21H2 22000.1219).
Keyboard and mouse are unresponsive, ACPI shutdown doesn't work either, although the guest os seems to work normally.
The log (attached) reports several 'vmmDevHeartbeatFlatlinedTimer'",Matt G
17721,Vbox crashes under heavy disk IO,Linux,other,VirtualBox 5.2.10,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
21350,3d Graphics with windows 10 as a guest,Mac OS X,Windows,VirtualBox-7.0.4,2022-12-21T04:09:43Z,2022-12-21T04:09:43Z,"Setup the guest with 3d graphics on.  Windows 10 using the 22h2 iso image.  Everything is fine until I installed the guest additions.  Once installed, I could not resize the guest windows and eventually turned off 3d graphics setting.  At this point I was able to resize the guest.

Host Mac running Ventura 13.1
Guest:
Windows 10 22H2
8GB ram
64GB Disk
3d Graphics enabled
Guest addition installed",JavaOops
21348,VM with Linux crashes worse than DOS or Windows 95. Your dog can crash it,Windows,other,VirtualBox 6.1.40,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
21352,"VM crash with ""Memory could not be read"" error when usb-c monitors are disconnected",Windows,other,VirtualBox-7.0.4,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
16053,Multi Monitor: Atypical configurations - mouse desync from window dragging,Windows,Windows,VirtualBox 5.0.26,2022-12-22T07:25:35Z,2022-12-22T07:25:35Z,"Host: Windows 10, VBox 5.0.26, 3 monitors

Guest: Windows 10, GA VBox 5.0.27r111132, 3 monitors

Steps to reproduce: In Guest Windows display settings, change monitor order into something atypical or just change order from 1-2-3 to 3-2-1. Or use something atypical like 1-3, then 2 below.

What happens ? You can move Window when dragging but there is no way to move cursor according to guest OS configuration. Basically mouse cursor movement is desynced from window movement (while dragging windows across monitors). This is wrong and a bug.

When Multi monitor is configured in atypical way, like:
{{{
1+3
 2  (below the others)
}}}

-or-

{{{
3-2-1
}}}

Expected behavior: It should behave like host, move cursor where it is allowed to. Move windows where it is allowed to.

-Technologov, 10.10.2016.",Technologov
21303,exception in module VBoxMRXNP.dll => Fixed in SVN,Windows,Windows,VirtualBox-7.0.4,2022-12-23T17:12:29Z,2022-12-23T17:12:29Z,"application running in MS Visual Studio 2019 crashes if it tries to access the file system (retrieve folder structure). In VirtualBox 6.1 it works fine.

windows Event log:
Faulting application name: EstiCon.Client.exe, version: 22.3.4.100, time stamp: 0x637e116c
Faulting module name: VBoxMRXNP.dll, version: 7.0.4.4605, time stamp: 0x6375102d
Exception code: 0x4000001f
Fault offset: 0x000132b0
Faulting process id: 0x448c
Faulting application start time: 0x01d8ff37dd906849
Faulting application path: c:\projekty\EstDevTest\Client\EstiCon.Client\bin\Debug\EstiCon.Client.exe
Faulting module path: C:\WINDOWS\system32\VBoxMRXNP.dll
Report Id: 7eb1303a-fddb-4eb3-a7ef-848370c48846
Faulting package full name: 
Faulting package-relative application ID: ",medved
21353,apic timer does not trigger in time,Windows,Linux,VirtualBox 6.1.40,2022-12-25T01:27:42Z,2022-12-25T01:27:42Z,"Rencently,I found a bug of APIC timer.Since the vbox set the last VCPU thread as the thread to wakeup all the timer and other VCPU threads will sleep 500ms until the Last VCPU thread wakeup them.
If the last VCPU thread sleep a long time firstly,other VCPU thread's apic timer will not able to trigger in timer.This make other VCPU thread sleep at least 500ms.

here is may patch to the funtion apicSetTimerIcr in VMM/VMMALL/APICAll.cpp to fix the bug

{{{
#include ""TMInternal.h""
static VBOXSTRICTRC apicSetTimerIcr(PPDMDEVINS pDevIns, PVMCPUCC pVCpu, int rcBusy, uint32_t uInitialCount)
{
    VMCPU_ASSERT_EMT(pVCpu);

    PAPIC      pApic      = VM_TO_APIC(pVCpu->CTX_SUFF(pVM));
    PAPICCPU   pApicCpu   = VMCPU_TO_APICCPU(pVCpu);
    PXAPICPAGE pXApicPage = VMCPU_TO_XAPICPAGE(pVCpu);

    Log2((""APIC%u: apicSetTimerIcr: uInitialCount=%#RX32\n"", pVCpu->idCpu, uInitialCount));
    STAM_COUNTER_INC(&pApicCpu->StatTimerIcrWrite);

    /* In TSC-deadline mode, timer ICR writes are ignored, see Intel spec. 10.5.4.1 ""TSC-Deadline Mode"". */
    if (   pApic->fSupportsTscDeadline
        && pXApicPage->lvt_timer.u.u2TimerMode == XAPIC_TIMER_MODE_TSC_DEADLINE)
        return VINF_SUCCESS;

    /*
     * The timer CCR may be modified by apicR3TimerCallback() in parallel,
     * so obtain the lock -before- updating it here to be consistent with the
     * timer ICR. We rely on CCR being consistent in apicGetTimerCcr().
     */
    TMTIMERHANDLE hTimer = pApicCpu->hTimer;
    VBOXSTRICTRC rc = PDMDevHlpTimerLockClock(pDevIns, hTimer, rcBusy);
    if (rc == VINF_SUCCESS)
    {
        pXApicPage->timer_icr.u32InitialCount = uInitialCount;
        pXApicPage->timer_ccr.u32CurrentCount = uInitialCount;
        if (uInitialCount)
            apicStartTimer(pVCpu, uInitialCount);
        else
            apicStopTimer(pVCpu);


        PVMCC pVM   = pVCpu->CTX_SUFF(pVM);
        PVMCPUCC pVCpuDst = VMCC_GET_CPU(pVM, pVM->tm.s.idTimerCpu);

        #ifdef IN_RING3
            VMR3NotifyCpuFFU(pVCpuDst->pUVCpu, VMNOTIFYFF_FLAGS_DONE_REM | VMNOTIFYFF_FLAGS_POKE);
        #elif defined(IN_RING0)

           if (VMMGetCpu(pVM) != pVCpuDst)
            {
                switch (VMCPU_GET_STATE(pVCpuDst))
                {
                    case VMCPUSTATE_STARTED_EXEC:
                        GVMMR0SchedPokeNoGVMNoLock(pVM, pVM->tm.s.idTimerCpu);
                        break;

                    case VMCPUSTATE_STARTED_HALTED:
                        GVMMR0SchedWakeUpNoGVMNoLock(pVM, pVM->tm.s.idTimerCpu);
                        break;

                    default:
                        break; /* nothing to do in other states. */
                }
            }
        #endif

        PDMDevHlpTimerUnlockClock(pDevIns, hTimer);
    }
    return rc;
}
}}}
",liowmark
21326,DirectX 9 image wrong offset in win7 guest,all,Windows,VirtualBox-7.0.4,2022-12-26T10:06:37Z,2022-12-26T10:06:37Z,"The few DX-9 applications that still run in a Windows 7 guest look like this:

[[Image(Untitled.png)]]

VirtualBox 7.0.4, 3D Acceleration on

Host: Gentoo Linux

Guest: Windows 7

Application: DirectX 9.0 SDK, Tutorial 02

Fix:

{{{
diff -Naur a/src/VBox/Devices/Graphics/DevVGA-SVGA3d.cpp b/src/VBox/Devices/Graphics/DevVGA-SVGA3d.cpp
--- a/src/VBox/Devices/Graphics/DevVGA-SVGA3d.cpp	2022-11-17 22:12:55.000000000 +0300
+++ b/src/VBox/Devices/Graphics/DevVGA-SVGA3d.cpp	2022-12-05 16:06:25.417632425 +0300
@@ -1093,6 +1093,8 @@
 
     VMSVGASCREENOBJECT *pScreen = &pSvgaR3State->aScreens[idDstScreen];
 
+    uint32_t const  cbScreenPixel = RT_ALIGN(pScreen->cBpp, 8) / 8;
+
     if (   srcRect.right <= srcRect.left
         || srcRect.bottom <= srcRect.top)
         return VINF_SUCCESS; /* Empty src rect. */
@@ -1186,6 +1188,8 @@
                 + ((box.x + pSurface->cxBlock - 1) / pSurface->cxBlock) * pSurface->cxBlock * pSurface->cbBlock
                 + ((box.y + pSurface->cyBlock - 1) / pSurface->cyBlock) * pSurface->cyBlock * srcMap.cbRowPitch;
 
+            uint32_t const offDstBox = (dstBox.x + box.x) * cbScreenPixel + (dstBox.y + box.y) * pScreen->cbPitch;
+
             /* The 'box' is actually in the destination coordinates relative to the top-left corner of destRect.
              * Therefore it is relative to the top-left corner of srcRect as well.
              */
@@ -1198,11 +1202,11 @@
             {
                 AssertContinue(srcDims.cyBlocks > 0);
 
-                ASSERT_GUEST_BREAK(   srcDims.offBox <= cbDst
-                                   && pScreen->cbPitch * (srcDims.cyBlocks - 1) + srcDims.cbRow <= cbDst - srcDims.offBox);
+                ASSERT_GUEST_BREAK(   offDstBox <= cbDst
+                                   && pScreen->cbPitch * (srcDims.cyBlocks - 1) + srcDims.cbRow <= cbDst - offDstBox);
                 RT_UNTRUSTED_VALIDATED_FENCE();
 
-                uint8_t *pu8DstBox = pu8Dst + srcDims.offBox;
+                uint8_t *pu8DstBox = pu8Dst + offDstBox;
 
                 if (   pSurface->format == SVGA3D_R8G8B8A8_UNORM
                     || pSurface->format == SVGA3D_R8G8B8A8_UNORM_SRGB)
}}}
",pv32768
21354,"Blue Screen when I run any virtual machine in ""Normal Start""",all,other,VirtualBox-7.0.4,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
21356,Guest addtions update issue in WIN 7,Windows,other,VirtualBox-7.0.4,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
21357,Guest addtions update issue in WIN 7,Windows,Windows,VirtualBox-7.0.4,2022-12-29T10:06:31Z,2022-12-29T10:06:31Z,"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
20830,Black Screen on VirtualBox,Windows,Linux,VirtualBox 6.1.30,2022-12-31T12:03:49Z,2022-12-31T12:03:49Z,I am using Virtual box and Kali linux version in it. Once i rebooted it prompted for username and password so after entering it the screen was fully black. Even i close the virtual box and opened it but same issue i am facing,sharan312
21388,Cannot alter the aspect ratio of my Windows XP virtual desktop,Mac OS X,Windows,VirtualBox 6.1.16,2023-01-02T18:33:29Z,2023-01-02T18:33:29Z,"Host – Mac 10.14.6	1TB
Guest 6.1.16 – Windows XP SP3. Virtual Desktop Aspect Ratio 3x2.3 (600x460Pixels).

I am unable to adjust aspect ratio of the Guest display although I could with my previous installation of this edition.
Previously I could make the adjustment using the VIEW tab - VIRTUAL SCREEN 1, and select an aspect ratio. Or simply drag the window out to suit

This does not work with the new installation. I have tried:

VIEW – ADJUST WINDOW SIZE (HOST + A) which is followed below by AUTO-RESIZE GUEST DISPLAY which is greyed out and ticked. Because it is greyed-out I cannot make any alterations – i.e. untick it?

VIEW tab - VIRTUAL SCREEN 1 select an aspect ratio from the list. 800x600 is ticked but I cannot select another ratio even though the list of sizes is not greyed-out?

PREFERENCES – DISPLAY – MAXIMUM GUEST SCREEN SIZE. I can carry out the functions offered by this screen and can, using the HINT function, save a new Width & Height. These dimensions remain on this window but do not alter the virtual desktop aspect ratio?

Have read some of the Forum’s pleas for help regarding screen issues, and as a consequence, have uninstalled and reinstalled Windows XP twice.

Reinstalled my original copy of the VM 6.1.16 program.

Downloaded and installed a new copy of the VM 6.1.16 program.

Reinstalled my original copy of the VM 6.1.16 Extension Pack.

Downloaded and installed a new copy of the VM 6.1.16 Extension Pack.

Have tried with & without 3D Acceleration enabled.

Have now spent some hours on this all to no avail.
",Boadiddly
21389,v7.0.0 + v7.0.2 + v7.0.4 hang-up and damages vms of v6.1.38,Windows,Windows,VirtualBox-7.0.4,2023-01-02T19:13:51Z,2023-01-02T19:13:51Z,"My host machine is Windows11Pro with the last updates installed. I use various virtual machines with virtualbox 6.1.38 and they work fine. I tried to update to v7.0.0 + v7.0.2 + v7.0.4 and the old machines not only do not work with the new release but were damaged! I have been complelled to reinstall again v6.1.38 and recover the virtual machines by backups. The guest operating systems are: WindowsXP + Windows7_32 + Windows7_64 + Windows10Pro + Windows11Pro. What happens is that the virtual machine locks during boot, the cpu goes to 100% and the memory load remains the same. It seems that during the startup something goes wrong, the hypervisor hang-up and damage the boot disk. The biggest problem is that of the damage of the virtual machine.",tiria
17730,Support PCI Passthrough for OSX Hosts,Mac OS X,all,VirtualBox 5.2.10,2023-01-02T19:50:31Z,2023-01-02T19:50:31Z,"PCI Passthrough is supported on VirtualBox for Linux hosts, it also works with VMWare Fusion for OSX. Would be nice to see working on OSX hosts.",jimm
16093,Startvm --type headless on detached guest -> show window,other,other,VirtualBox 5.1.8,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
21390,Installation of Additions not finishing on WinXP64 (VB 7.0.4),Linux,Windows,VirtualBox-7.0.4,2023-01-03T10:32:51Z,2023-01-03T10:32:51Z,"I have a WinXP64bit. I installed old guest-additions. Now I migrate to Virtualbox7. I installed the new guest-additions https://download.virtualbox.org/virtualbox/7.0.0/Oracle_VM_VirtualBox_Extension_Pack-7.0.0.vbox-extpack

Then I try to install the guest-additions in the guest-vm. Unfortunately the installation does not finish and remains at coping VBoxControl.exe.",grim
21391,Installation of Additions not finishing on WinXP64 (VB 7.0.4),Linux,Windows,VirtualBox-7.0.4,2023-01-03T10:41:38Z,2023-01-03T10:41:38Z,"I have a WinXP64bit. I installed old guest-additions. Now I migrate to Virtualbox7. I installed the new guest-additions https://download.virtualbox.org/virtualbox/7.0.0/Oracle_VM_VirtualBox_Extension_Pack-7.0.0.vbox-extpack

Then I try to install the guest-additions in the guest-vm. Unfortunately the installation does not finish and remains at coping VBoxControl.exe.",grim
21393,chrash of VM during shutdown,Windows,Windows,VirtualBox 6.1.38,2023-01-03T19:26:43Z,2023-01-03T19:26:43Z,I have frequent crashes during the shutdown of the virtual machine.,tiria
21351,GetFileInformationByHandleExfor VBoxSharedFolderFS  works incorrectly,Linux,other,VirtualBox-7.0.4,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
21387,Windows 11 BSOD,Windows,other,VirtualBox 6.1.28,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
21392,Microsoft Hyper-V Virtual Machine Bus Provider failed with code 37,Windows,Windows,VirtualBox-7.0.4,2023-01-04T12:36:24Z,2023-01-04T12:36:24Z,"- Device driver displays following error:
Windows cannot initialise the device driver for this hardware. (Code 37)
The request is not supported.

- VB VM configuration has :
  [x] Enable PAE/NX
  [x] Enable Nested VT-x/AMD-V
both enabled

also Acceleration is configured:
Paravirtualization Interface: Hyper-V
Hardware Virtualization: [x] Enabled Nested Paging

- VB is installed on the following system:

OS Name	Microsoft Windows 11 Pro
Version	10.0.22621 Build 22621
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	LP11-D5938-5930
System Manufacturer	Dell Inc.
System Model	Latitude 5511
System Type	x64-based PC
System SKU	09C1
Processor	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz, 2712 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date	Dell Inc. 1.18.0, 10/3/2022
SMBIOS Version	3.2
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Dell Inc.
BaseBoard Product	0C33CM
BaseBoard Version	A00
Platform Role	Mobile
Secure Boot State	On
Installed Physical Memory (RAM)	32.0 GB
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, Secure Memory Overwrite, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured	Hypervisor enforced Code Integrity
Virtualization-based security Services Running	Credential Guard, Hypervisor enforced Code Integrity
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	

",kjdro
21277,Ubuntu 22.10 Freeze/Crash,other,Linux,VirtualBox 6.1.40,2023-01-04T12:43:43Z,2023-01-04T12:43:43Z,"I am currently using virtualbox version 6.1.40, and tried to install ubuntu 22.10 from https://ubuntu.com/download/desktop quite a few times, but every time there is a crash which i can reproduce it the easiest way like this:
1)Fire up virtualbox
2)Click ""Try Ubuntu""
3)Let it boot
4)Open Nautilus/File explorer
5)Right click on Music on left pane
6)The context menu starts glitching
7)VM hangs or crashes
8)Trying to close the VM using Close button causes it to stop responding

HOST: windows 10 21H2
GUEST: Ubuntu 22.10",thehardgamer
21395,Mouse cursor buggy with 2 monitor setup,Windows,all,VirtualBox-7.0.4,2023-01-05T21:59:21Z,2023-01-05T21:59:21Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped by the X button on the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  In the video attached, I was only able to record my rightmost screen (with the VM window in it) but the main VirtualBox window was maximized on the display to the left of the one that was recorded.",KernelPanic
21396,Mouse cursor not working properly with 2 monitor setup,Windows,all,VirtualBox-7.0.4,2023-01-05T22:23:15Z,2023-01-05T22:23:15Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped at the top left corner of the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  When the VM window is moved to the same one as the main VirtualBox window the mouse still does not function properly in the VM.  Tried to attach a video but couldn't due to file size restrictions on here.",KernelPanic
20935,Mouse cursor rendered in low resolution,Windows,Windows,VirtualBox 6.1.34,2023-01-06T09:36:53Z,2023-01-06T09:36:53Z,"As described in forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105871

Host: Windows 10 Pro 21H2, Vbox 6.1.34 (the free version, no Extension Pack)[[BR]]
Guest: Windows 7 + Guest Additions v6.1.34

The Pointer scheme selected in the guest Control Panel is ""(None)"".

The pointer inside the VM is very pixelated. See photos below. One is the pointer inside the VM window, very pixelated, the other shows it outside the VM window, not pixelated, smooth.

The DPI scaling in the guest is set to 100%, the host has also 100%.

The photos on imgur:
https://imgur.com/XOqHicD
https://imgur.com/DLEiCpp
",xerces8
21397,NS_ERROR_FAILURE (0X80004005) / signal 9 in VirtualBox 7.0.4 on macOS Ventura 13.1 host,Mac OS X,other,VirtualBox-7.0.4,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
21399,After updating to 7.0.4 r154605 Virtualbox Manager cannot connect to any VM,other,other,VirtualBox-7.0.4,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
4503,NLS/Translation mistakes & suggestions,other,other,VirtualBox 3.0.2,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
21400,E_FAIL when running Kali in VirtualBox 7.0.4,other,other,VirtualBox-7.0.4,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
21401,VirtualBox stops operation. Log attached.,other,other,VirtualBox-7.0.4,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
21402,PXE boot gets stuck and does not hand over to next boot option,other,other,VirtualBox-7.0.4,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
21403,Broken Display Arrangement Configuration w/ VirtualBox Additions 7.0.4.,Windows,Linux,VirtualBox-7.0.4,2023-01-10T19:48:41Z,2023-01-10T19:48:41Z,"Hello, the issue in which I will try to describe occurs when you have more than 1 display associated with the Linux Guest, in my case Ubuntu Mate 22.04 LTS running under a Windows Host.

The issue occurs when you try to switch the default display arrangement so that it matches the physical arrangement of the displays. For example, if your 2 displays need to be switched so that when you move a window from 1 display to the other, it understands that the display is on the left opposed to on the right.

The behavior that occurs when you attempt to switch the arrangement is this:

- The Guest displays a confirmation dialog.
- When you try to click on ""Keep this Configuration"" there is no way to interact with the dialog.
- However if you move the mouse to the display the dialog is not on, and try clicking where the window would be if it was on that display, you can interact with the dialog in a very difficult way.

The Guest moves the window to the correct display but the the window is rendered on the wrong display.

When I downgraded to VirtualBox v6.1.40, the issue still occurred. I then downgraded to the VirtualBox Additions that come with v6.1.40, and once that was complete, the issue no longer occurred worked correctly.

Therefore it is my conclusion that the VirtualBox Additions that are packaged with VirtualBox v7.0.4 are causing this annoying and unfortunate behavior in regards to display arrangement.

I can provide more information if needed however I cannot easily provide a video capture of the behavior I am experiencing.

Thanks,

-
Rick",agilis
21404,SECOND LINUX GUEST CRASHES ON WINDOWS STARTUP - VBOX 7.04 BUG,Windows,Linux,VirtualBox-7.0.4,2023-01-12T10:53:01Z,2023-01-12T10:53:01Z,"When i am trying to automatically start a second Linux guest on windows 10 startup (through shell:startup), i get an error and the second Linux guest crashes.

The error message is ""The exception Breakpoint A Breakpoint has been reached (0x0000sFFCF66B225A. Click OK to terminate the program""

This bug  (or similarwith same results) occurs in all updates after 6.1.34 version, so i can't start e second guest automatically.

Please fix it !!!

Thank you ",Tasos Skarpathakis
21405,Linux guest on Windows 10 host does not start in seamless mode,Windows,Linux,VirtualBox-7.0.4,2023-01-12T14:25:59Z,2023-01-12T14:25:59Z,"When the Linux host is started, it ''always'' starts in windowed mode, not in seamless mode. I must manually switch to seamless. When I shut down the machine in seamless mode and restart it, I expect it to restart in that mode, as it did in former versions of VirtualBox (6.x).

",reibi
21201,FreeBSD 12.3 and pfSense 2.6.0 networking no longer works with upgrade to VB 7.0.2 => fixed in SVN,Linux,BSD,VirtualBox-7.0.2,2023-01-12T15:03:06Z,2023-01-12T15:03:06Z,"Hi,

After a recent upgrade from VirtualBox 6.1.40 to 7.0.2 on Arch Linux, all of my pfSense virtual machines hang at ""Configuring WAN interface"" during the boot process. Reverting VirtualBox back to 6.1.40 fixes it.

The pfSense VM (CE 2.6.0) is configured with EFI enabled and the WAN interface is a NAT virtual network adapter with ""virtio-net"". I've tried changing the adapter to either of the Intel PRO/1000 Server options and it does eventually boot after a 5 minute hang at the same point, but it is unable to get an IP and therefore doesn't work either.

I've also tried to create a brand new pfSense VM using the same settings as our currently running ones and while it installs properly, after the reboot it is stuck on ""Default interfaces not found -- Running interface assignment option."". This also works properly in 6.1.40. I've also tried setting the network interface to bridge mode and no change.

Edit: All other VM work properly, including other FreeBSD 13.1 virtual machines but same behavior with FreeBSD 12.3.

Any suggestions?",rickga
21406,USB devices not being enumerated on 7.0.4,other,other,VirtualBox-7.0.4,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
21408,Windows: High host cpu usage with 7.0.4,Windows,Windows,VirtualBox-7.0.4,2023-01-13T11:25:35Z,2023-01-13T11:25:35Z,"Even though the guest OS is idle the VBoxHeadless process uses up a whole core for running (see attached screenshot).

The VM was running for a whole day and it's also the same if the start the VM normal or headless - it is constantly consuming the whole CPU core.

Both guest and host use the latest Windows 10 version (22H2 19045.2486).

I have also attached the configuration files of my VM, VBox logs and the sys-info of my host system.",IndyJones
21409,enabling capture with usbattach command always fails,other,Windows,VirtualBox-7.0.4,2023-01-13T21:17:22Z,2023-01-13T21:17:22Z,"I was able to reproduce with both virtualbox 6.1.40-154048~Debian~bullseye and 7.0.4-154605~Debian~bullseye.

Host is mostly Debian bullseye with a Gnome from bookworm.
Guest is Windows 7 Ultimate with latest updates installed.

{{{
$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbattach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
$ ls usb*
ls: impossible d'accéder à 'usb*': Aucun fichier ou dossier de ce type
$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbdetach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
VBoxManage: error: USB device with UUID {7d1e5806-5813-4320-b11f-809e116092c5} is not attached to this machine
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component ConsoleWrap, interface IConsole, callee nsISupports
VBoxManage: error: Context: ""DetachUSBDevice(usbId.raw(), dev.asOutParam())"" at line 1451 of file VBoxManageControlVM.cpp

$ VBoxManage controlvm ""Win7 Ultimate Hermes"" usbattach 7d1e5806-5813-4320-b11f-809e116092c5 --capturefile ""usb_astrometa_20230103-1""
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""AttachUSBDevice(usbId.raw(), captureFilename.raw())"" at line 1447 of file VBoxManageControlVM.cpp

}}}


VBox.log extract:
{{{
00:07:37.598240 PDMUsb: Failed to attach USB device 'USBProxy' instance 1 to hub 00007fccb84e93b0: VERR_NOT_FOUND
00:07:37.765443 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_NOT_FOUND)}, preserve=false aResultDetail=-78
00:07:56.597244 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={USB device with UUID {7d1e5806-5813-4320-b11f-809e116092c5} is not attached to this machine}, preserve=false aResultDetail=0
00:08:05.070747 PDMUsb: Failed to attach USB device 'USBProxy' instance 2 to hub 00007fccb84e93b0: VERR_NOT_FOUND
00:08:05.223122 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_NOT_FOUND)}, preserve=false aResultDetail=-78
}}}


This issue seems to have already been asked in the forum in November 2020 https://forums.virtualbox.org/viewtopic.php?f=7&t=100495

My ""VBoxManage list usbhost"":
{{{
Host USB Devices:

UUID:               d6e93f88-6381-4089-96f7-8abba8cd6718
VendorId:           0x17ef (17EF)
ProductId:          0x608d (608D)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/Low
Manufacturer:       PixArt
Product:            Lenovo USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.2//device:/dev/vboxusb/001/007
Current State:      Busy

UUID:               025e451f-eb3f-4e61-a323-5e317182f509
VendorId:           0x17ef (17EF)
ProductId:          0x608c (608C)
Revision:           1.20 (0120)
Port:               0
USB version/speed:  2/Low
Manufacturer:       LiteOn
Product:            Lenovo Calliope USB Keyboard
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.1//device:/dev/vboxusb/001/005
Current State:      Busy

UUID:               1fbaede8-53a9-4d9f-af86-a4708f66cc9b
VendorId:           0x174c (174C)
ProductId:          0x55aa (55AA)
Revision:           1.0 (0100)
Port:               3
USB version/speed:  3/Super
Manufacturer:       Ugreen
Product:            Ugreen Storage Device
SerialNumber:       021912063F24
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4//device:/dev/vboxusb/002/012
Current State:      Busy

UUID:               d3504e3c-c92f-40fa-9107-b63aee699a85
VendorId:           0x174c (174C)
ProductId:          0x55aa (55AA)
Revision:           1.0 (0100)
Port:               2
USB version/speed:  3/Super
Manufacturer:       Ugreen
Product:            Ugreen Storage Device
SerialNumber:       022001030BFA
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3//device:/dev/vboxusb/002/011
Current State:      Busy

UUID:               e04d293c-2d4a-4e0d-b32a-f297a68f75e4
VendorId:           0x10c4 (10C4)
ProductId:          0xea60 (EA60)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/Full
Manufacturer:       Silicon Labs
Product:            CP2104 USB to UART Bridge Controller
SerialNumber:       00DB1A1E
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2//device:/dev/vboxusb/001/013
Current State:      Busy

UUID:               699af1c0-be96-4f48-a254-a50b36888be9
VendorId:           0x0a12 (0A12)
ProductId:          0x0001 (0001)
Revision:           49.100 (49100)
Port:               0
USB version/speed:  2/Full
Manufacturer:       Cambridge Silicon Radio, Ltd
Product:            Bluetooth Dongle (HCI mode)
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1//device:/dev/vboxusb/001/004
Current State:      Busy

UUID:               7d1e5806-5813-4320-b11f-809e116092c5
VendorId:           0x0781 (0781)
ProductId:          0x5581 (5581)
Revision:           1.0 (0100)
Port:               5
USB version/speed:  3/Super
Manufacturer:       SanDisk
Product:            Ultra
SerialNumber:       4C530001030927114111
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6//device:/dev/vboxusb/002/013
Current State:      Available

}}}
",Alban Browaeys
21309,[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out,Linux,Linux,VirtualBox-7.0.4,2023-01-16T13:56:25Z,2023-01-16T13:56:25Z,"Hi,

Seeing this below error after upgrade to VBOX 7.0.4

[Thu Nov 24 06:55:56 2022] CPU: 0 PID: 9189 Comm: kworker/0:1 Kdump: loaded Tainted: G           OE     5.4.17-2136.313.6.el8uek.x86_64 #2
[Thu Nov 24 06:55:56 2022] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[Thu Nov 24 06:55:56 2022] Workqueue: events vmw_fb_dirty_flush [vmwgfx]

Attaching the file with dmesg from VM.

Host: Fedora 
Host Kernel: 6.0.8-300.fc37.x86_64
VM : Oracle Linux Server release 8.7
VM Kernel: 5.4.17-2136.313.6.el8uek.x86_64

Please let me know if you need any further information.
Thanks,
Srini.",Srini8987
21412,Virtualbox + Hyper-V + 1GB Paging doesn't seem to be supported?,Windows,other,VirtualBox-7.0.4,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
21415,"Debian/Ubuntu repositories: remove dependency ""vitualbox-x.y recommends linux-image""",Linux,all,VirtualBox-7.0.6,2023-01-17T23:59:41Z,2023-01-17T23:59:41Z,"vitualbox-x.y packages in Debian/Ubuntu repositories should have their dependency

""vitualbox-x.y recommends linux-image"" removed.

1.

This dependency sometimes makes apt resolve conflicts by installing random ""linux-image-*"" packages (which provide ""linux-image"" virtual package).

This mostly includes Linux kernel images dedicated for cloud:
linux-image-*-azure, linux-image-*-gcp, linux-image-*-oracle, linux-image-*-aws

Automatically installing these makes an annoying mess in host's Linux installation,
and may also result in failed upgrades if /boot partition is too small to fit all these kernel images.

2.

At least 1 package providing ""linux-image"" is obviously most likely installed already in any Linux system, so this dependency is quite useless anyway.
",PHD
20755,No audio heard in v6.1.24 through v6.1.30,Windows,Windows,VirtualBox 6.1.30,2023-01-18T05:23:44Z,2023-01-18T05:23:44Z,"I'm currently running VirtualBox hosted on Windows 10 Pro 21H1. I have 3 guests with the following audio configurations:

Windows XP Pro 32-bit - Windows Direct Sound / ICH AC97
Windows 7 Pro 64-bit- Windows Direct Sound / Intel HD Audio
Windows 10 Pro 64-bit - Windows Direct Sound / Intel HD Audio

Under v6.1.22 the audio works for all three guests, albeit with the repeating / echoing audio which others have reported.

If I update to any version from v6.1.24 through v6.1.30, the audio in the Windows XP guest works OK, but there is no audio on my Windows 7 and Windows 10 guests.

logs from 6.1.22 and 6.1.30 attached.",doctorx
21416,"If you have multiple LVM partitions for example on sda2 on Oracle 9.1 Linux Guest on Windows 10 Host, the cloned or exported VM will not boot properly",Windows,Linux,VirtualBox-7.0.6,2023-01-18T10:09:55Z,2023-01-18T10:09:55Z,"Hello,

You replicate the problem like this:

1. Install a new VM from the Oracle 9.1 iso. 
2. Define just one disk and ensure it is very large e.g. 2TB. 
3. Ensure the default installation creates at least two LVM partitions:
    e.g. ol-root and ol-home on sda2
4. When cloned or exported/imported even to the same host machine, the resulting cloned VM will not boot properly, because only the first of the partitions is retained. In the example above, only ol-root is visible to the machine. ol-home disappears off the face of the earth.

As you can see the steps to replicate the problem is trivial. 

Thanks for your attention.

Cheers!

Yuet
",Yuet
21417,Different IGuestSession::processCreate behavior in v7 from v6,other,other,VirtualBox-7.0.6,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
17961,VMM missing rflags.TF handling when advance rip that abused by virtual machine detection => fixed in SVN,all,all,VirtualBox 5.2.18,2023-01-18T14:08:35Z,2023-01-18T14:08:35Z,"Found a virtual-box detection vector that abused by VMProtect 3.1+ and Safengine, confirmed by using custom hypervisor to monitor CPUID instruction.

see [https://github.com/tandasat/HyperPlatform/issues/26] for more discussion about this.

{{{#!cpp
IEM_STATIC void iemRegAddToRipAndClearRF(PVMCPU pVCpu, uint8_t cbInstr)
{
    pVCpu->cpum.GstCtx.eflags.Bits.u1RF = 0;

    AssertCompile(IEMMODE_16BIT == 0 && IEMMODE_32BIT == 1 && IEMMODE_64BIT == 2);
#if ARCH_BITS >= 64
    static uint64_t const s_aRipMasks[] = { UINT64_C(0xffffffff), UINT64_C(0xffffffff), UINT64_MAX };
    Assert(pVCpu->cpum.GstCtx.rip <= s_aRipMasks[(unsigned)pVCpu->iem.s.enmCpuMode]);
    pVCpu->cpum.GstCtx.rip = (pVCpu->cpum.GstCtx.rip + cbInstr) & s_aRipMasks[(unsigned)pVCpu->iem.s.enmCpuMode];
#else
    if (pVCpu->iem.s.enmCpuMode == IEMMODE_64BIT)
        pVCpu->cpum.GstCtx.rip += cbInstr;
    else
        pVCpu->cpum.GstCtx.eip += cbInstr;
#endif
}
}}}

Here are the test code that you can use to repro ""cpuid in real"" in real machine but ""cpuid run in vmm"" inside any virtualbox guest. (though the code is for Windows)

{{{#!cpp
int filter(EXCEPTION_POINTERS * pException, BOOL *pFound)
{
    auto code = *(BYTE*)pException->ContextRecord->Eip;

    printf(""cpuid exception eip = %p code = %02x\n"", pException->ContextRecord->Eip, code);

    //code != nop, in vmm
    if (code != 0x90)
        *pFound = TRUE;

    return EXCEPTION_EXECUTE_HANDLER;
}

BOOL cpuid_test()
{
    BOOL bFound = FALSE;
    __try
    {
        __asm
        {
            mov eax, 0
            pushfd;
            or DWORD ptr[esp], 0x100;
            popfd;//set TF=1
            cpuid;
            nop;//normal TF
            int 3//in vmm...
        }
    }
    __except (filter(GetExceptionInformation(), &bFound))
    {
        ;
    }
    return bFound;
}
}}}

[[Image(https://user-images.githubusercontent.com/12287588/44799149-d4273580-abe5-11e8-8b06-a2f1230360cc.png)]]
[[Image(https://user-images.githubusercontent.com/12287588/44799388-629bb700-abe6-11e8-8667-fff3f2b1cc8b.png)]]

what cpu do in real os:
execute CPUID->set EIP at nop->raise a single step exception(#DB) with error code 0x80000004->set TF=0->the exception would be handled by SEH->you see EIP at nop

what cpu do in vmm:
execute cpuid->cpuid is handled by vm-exit handler->you advance the EIP by one instrution in the handler (so EIP would be at nop)->execute nop->set EIP at int3->raise a single step exception->set TF=0->the exception would be handled by SEH->you see EIP at int3

the solution is to inject #DB when Guest's TF is set, and adjusting RIP normally, also writing the instruction length of CPUID in the vm entry instruction len which is 2 in the case of cpuid.

NB: You need to do this generically though.",hzqst
21266,good day. The guest additions CD does not work. I think the CD drive is not working.,Linux,other,VirtualBox-7.0.2,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@…
21218,USB drives do not connect to Virtualbox 7.0.2 under macOS host,Mac OS X,Linux,VirtualBox-7.0.2,2023-01-18T18:59:17Z,2023-01-18T18:59:17Z,"Attempting to attach a USB drive from the host os (macOS) to the guest (Lubuntu) fails, even when drives are unmounted on the host, and an appropriate USB filter has been defined. Errors as follows:


{{{
Failed to attach the USB device SanDisk Cruzer [0100] to the virtual machine Lubuntu 2.
Failed to create a proxy device for the USB device. (Error: VERR_SHARING_VIOLATION).
}}}

Log attached.

{{{
Failed to attach the USB device SanDisk Cruzer [0100] to the virtual machine Lubuntu 2.
Could not find a USB device with uuid {}.
Callee RC:
NS_ERROR_FAILURE (0X80004005)
}}}


",ianr77
20155,"""VBoxManage convertfromraw --format=vdi"" silently fails?",Linux,Linux,VirtualBox 6.1.18,2023-01-18T19:33:51Z,2023-01-18T19:33:51Z,"I have a raw image that perfectly runs with qemu-kvm, obtained with a Ubuntu Server headless install.

I'm trying to convert this raw image to VDI using VBoxManage, but it appears to fail while not providing any error message.

More precisely, here is what happens:

1) I run this command :


{{{
$ VBoxManage convertfromraw --format vdi output/mini-ubuntu-base.img output/mini-ubuntu-base.vdi
}}}


2) It prints what follows and appears to be running (and my CPU load does tell it is running):


{{{
Converting from raw image file=""output/mini-ubuntu-base.img"" to file=""output/mini-ubuntu-base.vdi""...
Creating dynamic image with size 21474836480 bytes (20480MB)...
}}}


3) *While* it is running, using a second terminal, I can see that a VDI file is being created :


{{{
$ ls -lah output | grep vdi
-rw-------. 1 ebo ebo 6,5G 26 janv. 10:28 mini-ubuntu-base.vdi
}}}


4) But then, when the 'VBoxManage' command returns… the VDI file has disappeared!


{{{
$ ls -lah output | grep vdi
<nothing>
}}}

Which means something went wrong somewhere I suppose, but I tend to believe that some output should tell so?


Additional note: I have other raw images obtained through a similar process that I manage to convert into VDI using VBoxManage without problem using my current environment.",ebo
21347,VB systemd unit persistently rebuilding kernel modules with secureboot,Linux,all,VirtualBox-7.0.4,2023-01-19T01:49:28Z,2023-01-19T01:49:28Z,"In Debian, the kernel source script `extract-module-sig.pl` is not available in the kernel modules build/scripts directory. The VirtualBox systemd unit script relies on this script to determine whether the VB kernel modules are appropriately signed if it detects that secureboot is enabled. Since it can't find the script, it believes there is something wrong with the modules, and rebuilds them every time the service starts (at least on every boot), regardless of whether they were correctly signed. This means that every time I reboot my machine, VirtualBox refuses to operate until I go back and sign the newly-built kernel modules.

System: Debian Bullseye
VB installed with the deb distributed by the download.virtualbox.org repository.",lxop
21410,RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf],Windows,Linux,VirtualBox-7.0.4,2023-01-19T08:30:56Z,2023-01-19T08:30:56Z,"Hi,

I am seeing below error with kernel 6.1.5-200.fc37.x86_64.
{{{
------------[ cut here ]------------
memcpy: detected field-spanning write (size 14) of single field ""&pReq->StrPath"" at /tmp/vbox.0/utils.c:591 (size 6)
WARNING: CPU: 0 PID: 2470 at /tmp/vbox.0/utils.c:591 vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Modules linked in: vboxsf(OE) snd_seq_dummy snd_hrtimer vboxvideo(OE) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat 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 rfkill nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter ip_tables qrtr sunrpc snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm intel_rapl_msr snd_timer intel_rapl_common pktcdvd pcspkr snd soundcore i2c_piix4 joydev zram crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic virtio_net ghash_clmulni_intel vmwgfx net_failover sha512_ssse3 drm_ttm_helper video serio_raw failover vboxguest(OE) ttm wmi ata_generic pata_acpi scsi_dh_rdac scsi_dh_emc scsi_dh_alua fuse dm_multipath
CPU: 0 PID: 2470 Comm: ls Tainted: G        W  OE      6.1.5-200.fc37.x86_64 #1
Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Code: cf fd ff ff b9 06 00 00 00 4c 89 fe 4c 89 14 24 48 c7 c2 e0 a8 a5 c0 48 c7 c7 90 a8 a5 c0 c6 05 04 a6 00 00 01 e8 42 4c 31 d7 <0f> 0b 4c 8b 14 24 e9 9e fd ff ff 83 f8 98 41 bb b9 ff ff ff b8 fe
RSP: 0018:ffffb046852bbb58 EFLAGS: 00010282
RAX: 0000000000000074 RBX: ffff986681154e00 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff9874a863 RDI: 00000000ffffffff
RBP: ffff9866874a0144 R08: 0000000000000000 R09: ffffb046852bb9f8
R10: 0000000000000003 R11: ffffffff99146488 R12: ffff98667f8b6f00
R13: ffff98668100d6c0 R14: ffff986682574c00 R15: 000000000000000e
FS:  00007f85aafd3c40(0000) GS:ffff98675bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056279ce6f718 CR3: 00000000011ce000 CR4: 00000000000506f0
Call Trace:
 <TASK>
 vbsf_dentry_revalidate+0x4f/0xb0 [vboxsf]
 lookup_fast+0x74/0xe0
 walk_component+0x1f/0x150
 path_lookupat+0x67/0x190
 filename_lookup+0xd3/0x1c0
 vfs_statx+0x8e/0x150
 do_statx+0x50/0x80
 __x64_sys_statx+0x62/0x80
 do_syscall_64+0x5b/0x80
 ? do_syscall_64+0x67/0x80
 ? fpregs_restore_userregs+0x12/0xe0
 ? exit_to_user_mode_prepare+0x18f/0x1f0
 ? syscall_exit_to_user_mode+0x17/0x40
 ? do_syscall_64+0x67/0x80
 ? do_syscall_64+0x67/0x80
 ? exc_page_fault+0x70/0x170
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f85ab16ca5e
Code: 83 0d 00 ba ff ff ff ff 64 c7 00 16 00 00 00 e9 a5 fd ff ff e8 d3 0f 02 00 0f 1f 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 89 c1 85 c0 74 0f 48 8b 05 9d 83 0d 00 64
RSP: 002b:00007ffda585f578 EFLAGS: 00000246 ORIG_RAX: 000000000000014c
RAX: ffffffffffffffda RBX: 000056279ce5fee8 RCX: 00007f85ab16ca5e
RDX: 0000000000000900 RSI: 00007ffda585f6b0 RDI: 00000000ffffff9c
RBP: 000000000000025e R08: 00007ffda585f580 R09: 0000000000000020
R10: 000000000000025e R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 000056279ce5fed0 R15: 0000000000000000
 </TASK>
---[ end trace 0000000000000000 ]---
}}}",Srini8987
21230,VboxManage guestcontrol issue,Windows,Windows,VirtualBox-7.0.2,2023-01-19T10:47:38Z,2023-01-19T10:47:38Z,"Prior to upgrading to VB 7.0, I could use vboxmanage guestcontrol to run a batch script on a windows 10 virtual machine and that script had access to the virtual machines shared folders/drives. I have been using this script for many years and many versions of VirtualBox. Now when the script runs it is reporting the H drive is not found. Everything in the VM_Setup.bat script works except for access to the H drive. The virtual machine has access to the H drive just not the guestcontrol feature.

Share folder section for the virtual machine is below. All of these drives work inside the virtual machine.
<SharedFolders>
<SharedFolder name=""Projects"" hostPath=""F:\"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""Downloads"" hostPath=""H:\Library\Downloads"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""Shared"" hostPath=""H:\"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""ElecWorkFile"" hostPath=""Z:\"" writable=""true"" autoMount=""false""/>
</SharedFolders>

vboxmanage guestcontrol %VMN% run --quiet --unquoted-args --username ""%VMU%"" --password """" --exe ""H:\Scripts\VM_Setup.bat"" -- H:\Scripts\VM_Setup.bat %VM%

VBoxManage.exe: error: Waiting for guest process (flags 0x1) failed: No such file or directory ""H:\Scripts\VM_Setup.bat"" on guest
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestProcessWrap, interface IGuestProcess, callee IUnknown
VBoxManage.exe: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aWaitStartFlags), gctlRunGetRemainingTime(msStart, cMsTimeout), &waitResult)"" at line 1373 of file VBoxManageGuestCtrl.cpp
Waiting for VM Setup to Complete...
Press any key to continue . . .

<------ Test Script (TestQ.bat) Start ---------->
@echo off
cls
setlocal enabledelayedexpansion

SET VM=vm1
SET VMN=""WinX Rockwell""
SET VDI=WinX_Rockwell
SET VMU=alliance
SET VBMP=C:\Program Files\Oracle\VirtualBox
SET VBM=vboxmanage.exe
SET PATH=%PATH%;%VBMP%
SET LINES=0

:WAITFORSETUP
SET VMDONE=0

For /f ""usebackq tokens=*"" %%i IN (`%VBM% guestcontrol %VMN% run --quiet --unquoted-args --username ""%VMU%"" --password """" --exe ""H:\Scripts\VM_Status.bat"" -- H:\Scripts\VM_Status.bat %VM% `) DO (
SET /a LINES+=1
SET RESULTS=%%i
echo %%i
)
echo %VMDONE% %LINES%
IF ""%LINES%"" EQU ""0"" GOTO SKIP
IF ""%LINES%"" NEQ ""4"" GOTO SKIP
IF NOT ""!RESULTS!."" EQU ""!RESULTS:Complete=!."" (
SET VMDONE=1
)

:SKIP
If %VMDONE% EQU 0 (
Echo Waiting for VM Setup to Complete...
) ELSE (
Echo VM Setup to Complete
)
endlocal

pause
<------ Test Script (TestQ.bat) End ---------->
",cmccarron
21413,gdb crashes,other,other,VirtualBox-7.0.4,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
21418,general protection fault in VBoxRT.so on Linux 5.15,Linux,Linux,VirtualBox 6.1.40,2023-01-20T00:47:16Z,2023-01-20T00:47:16Z,"On Linux 5.15.0-58-generic as shipped by Ubuntu, I have been getting repeated general protection faults while trying to run a Linux guest:

[104009.209640] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[104254.184865] traps: CharIo[1979689] general protection fault ip:7fdabb249cec sp:7fda75ab2c88 error:0 in VBoxRT.so[7fdabb0da000+1ca000]
[112313.218922] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[112533.549601] traps: CharIo[2118320] general protection fault ip:7f1e2041bcec sp:7f1deec85c88 error:0 in VBoxRT.so[7f1e202ac000+1ca000]
cfriesen@yow-cfriesen-lx:~/vdm_workspace/iso/wrcp$ 


The VM log file looks like this:

00:00:29.903869 GIM: KVM: VCPU  4: Enabled system-time struct. at 0x0000000501fc6100 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b4fd3719 uVirtNanoTS=0x6e702e07f TscKHz=2999974
00:00:29.910783 APIC5: Switched mode to x2APIC
00:00:29.910795 GIM: KVM: VCPU  5: Enabled system-time struct. at 0x0000000501fc6140 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b636f299 uVirtNanoTS=0x6e76b748e TscKHz=2999974
00:00:29.916720 APIC6: Switched mode to x2APIC
00:00:29.916669 GIM: KVM: VCPU  6: Enabled system-time struct. at 0x0000000501fc6180 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b7460d8d uVirtNanoTS=0x6e7c5d311 TscKHz=2999974
00:00:29.921905 APIC7: Switched mode to x2APIC
00:00:29.921824 GIM: KVM: VCPU  7: Enabled system-time struct. at 0x0000000501fc61c0 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b833dc4c uVirtNanoTS=0x6e8151828 TscKHz=2999974
00:00:29.914199 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.925422 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.919380 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.907340 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.886932 IEM: rdmsr(0x4e) -> #GP(0)
00:00:40.477240 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:40.477303 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:40.481279 AHCI#0: Reset the HBA
00:00:40.481292 VD#0: Cancelling all active requests
00:00:40.481295 VD#1: Cancelling all active requests
00:00:40.481297 VD#2: Cancelling all active requests
00:00:40.590027 AHCI#0: Port 0 reset
00:00:40.591645 VD#0: Cancelling all active requests
00:00:40.933168 AHCI#0: Port 1 reset
00:00:40.934890 VD#1: Cancelling all active requests
00:00:41.261123 AHCI#0: Port 2 reset
00:00:41.262793 VD#2: Cancelling all active requests


",Chris Friesen
21419,"Error ""kmk: glslangValidator: Command not found""while building VirtualBox",Linux,other,VirtualBox-7.0.6,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
21422,Ciao a tutti sono un principiante di Virtualbox. problema: DnD e appunti condivisi non funzionano. Host Win 10 e Guest Ubuntu. Guest installate.,other,Linux,VirtualBox 6.1.40,2023-01-21T17:29:50Z,2023-01-21T17:29:50Z,"Codice di uscita:
VBOX_E_IPRT_ERROR (0x80BB0005)
Componente: GuestWrap
Interfaccia: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}
",Dave78
21424,can't create new vdisks; verr_write_protect returned,Mac OS X,other,VirtualBox-7.0.6,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
21426,Unable to resize screen on Windows 10 guest with 3D acceleration enabled,Linux,Windows,VirtualBox-7.0.6,2023-01-22T15:49:04Z,2023-01-22T15:49:04Z,,Harold Hare
21427,Unable to resize screen on Windows 10 guest with 3D acceleration enabled,Linux,Windows,VirtualBox-7.0.6,2023-01-22T15:58:57Z,2023-01-22T15:58:57Z,"When I use the View menu with 3D acceleration disabled it allows me to choose a different resolution (1600x900) and it changes both the resolution itself and the value in Windows ""Display Settings"", which presumably is the expected behaviour. However, with 3D acceleration enabled it reverts to the previous setting when I try to set it and the resolution is unchanged even after a reboot.",Harold Hare
21428,Signal 9,Mac OS X,Linux,VirtualBox-7.0.6,2023-01-22T22:18:31Z,2023-01-22T22:18:31Z,"I was trying to boot android 9 on macOS Ventura 13.2 beta but this happened 
VM Name: Android 9
The virtual machine
'Android 9° has
terminated unexpectedly during startup because of signal 9.
Result code: NS_ERROR_FAILURE(0X80004005)
Component: MachineWrap
Interface: IMachine
{300763af-5d6b-46e6-aa96-273eac155381}

I dunno what to do And I scoured the inter webs and could not find anything

Also no one has said anything on this before at least not of my knowledge.

Please help",UKNOWN VM
21429,MiniToolbar not showing when in fullscreen,Linux,all,VirtualBox-7.0.6,2023-01-23T04:23:37Z,2023-01-23T04:23:37Z,"When I upgraded from VirtualBox 7.0.4 to 7.0.6, the mini toolbar stopped showing at the top of the screen. It doesn't matter whether I already installed the operating system or just running it, it does not want to show when I start the operating system. The only work around that I know about is to do the host-f to get out of fullscreen and then host-f again to make the mini toolbar show. It does not matter whether it is FreeDOS, A Linux guest OS, or Windows, the mini toolbar will not show when I first start the OS. My host OS is Ubuntu Cinnamon 22.04 LTS. ",soldier4messiah
21425,Unreadable fonts in Windows 11  as guest in Virtualbox,other,other,VirtualBox-7.0.6,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
21430,Ubuntu kernel panic on Windows 11,Windows,Linux,VirtualBox-7.0.6,2023-01-24T13:03:26Z,2023-01-24T13:03:26Z,Trying to get the DVWA (Damn Vulnerable Web App) VM working in the current version of OVB running on a Windows 11 laptop.  Every time I tried to start the DVWA VM (an Ubuntu Linux VM) it crashed with a kernel panic.  When I downgraded from Windows 11 back to Windows 10 it started successfully.  ,Dr John Mc
21420,The create button is not showing when creating a new Virtual Machine.,Windows,Windows,VirtualBox-7.0.6,2023-01-26T09:05:30Z,2023-01-26T09:05:30Z,"[[Image(X:/downloads/Screenshots/ss1.png)]]I have tried re-installing and tried other versions of Virtual box too, But I am not able to create a Virtual Machine :(.

can someone please help me with this

I am running Virtual box on Windows 11",tuglukbaba
21421,Canonical has updated Ubuntu Linux kernel; DEB package from Oracle no longer works,other,other,VirtualBox-7.0.6,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
21434,A critical error has occurred while running the virtual machine,Mac OS X,other,VirtualBox-7.0.6,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
21435,Vboxdrv module triggers IBT protection. VM's fail to start,Linux,all,VirtualBox-7.0.6,2023-01-26T15:14:43Z,2023-01-26T15:14:43Z,"This has been a problem for a while: The vboxdrv triggers IBT (indirect branch tracking) protection on modern Intel cpu's. This causes the VM to refuse to load.

Disabling IBT (booting the kernel with `ibt=off`) will make the problem disappear, but the protections are there for a reason. IBT is enabled by default on Arch Linux, but I believe IBT will be enabled by default in the upcoming 6.2 linux kernel release for Intel CPU's from the 11th generation up to the current (13th) gen. More and more CPU's will be affected.

A full log from trying to start a VM is attached. Though it is very short, nothing more happens. Also attached is dmesg output showing the protection being triggered in the kernel when starting a VM.

A bug report was also made filed with the kernel (https://bugzilla.kernel.org/show_bug.cgi?id=216102) and in Arch (https://bugs.archlinux.org/task/75481), but the latter suggested to file a bug with Virtualbox, which is what I'm doing now. Please let me know if I can provide more information.

Thanks!",bepaald
21436,Coral USB EdgeTPU runs high then disappear from host,Mac OS X,Linux,VirtualBox-6.1.42,2023-01-27T12:34:35Z,2023-01-27T12:34:35Z,"Running on MacPro 4,1 with macOS 10.13.x (High Sierra) and have 3 machines running. Google Coral should be running in the 10-40ms range with 5-6 cameras. 

Machine 1 - Home-assistant runs perfect.
 Tried adding Frigate add-on with Coral TPU USB runs high inference >300ms and then disappears from virtual machine and sometimes disconnects from host. Tried different port and a powered USB hub. Always the same results after a while. Upon advice from Frigate NVR developers, moved to separate machine. 

Machine 2 - runs Ubuntu perfectly. 

Machine 3 - running Frigate NVR stand-alone on Debian guest
Same as above. Runs high at first (100ms) and then goes higher >300ms and disconnects from guest but not from host. 

Why does the Coral run so high and why does it disconnect? 
                  ",Frank61
21437,Drag and Drop no longer works,Windows,Solaris,VirtualBox-7.0.6,2023-01-27T19:40:16Z,2023-01-27T19:40:16Z,"Version 7.0.6 r155176 (Qt5.15.2)

The drag and drop between my widows laptop and Virtual Box no longer works
Pretty sure it work in previous version of 6.0+",pt519
21439,I/O errors with virtio-scsi,Linux,Linux,VirtualBox-7.0.6,2023-01-28T00:22:36Z,2023-01-28T00:22:36Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
21432,Importing Oracle Solaris 10 and 11 appliances fails to set the memory correctly,other,Solaris,VirtualBox-7.0.6,2023-01-28T00:38:46Z,2023-01-28T00:38:46Z,"This looks something like bug 4188 regressed.

Steps:
1. Download the Solaris 10 or 11 Admin VM templates from the Oracle Network.
2. Start VB 7.0.6
3. Select file/Import Appliance.
4. Select the ova file just downloaded and press ""next""
5. Scroll down to change the CPU and memory settings.
6. Observe non-sensical amount of RAM for the system. (see attached)
7. Set it to 4096 MB...
8. Allow the import to complete
9. Check the system settings of the imported VM.
10. Observer 0GB, and on going in, the VM is allocated a mere 4MB. This causes a memory issue on boot.

The issue can be worked around by manually setting RAM post-import... But there is something rotten in Denmark here.",bricowan
21438,"VirtualBox ""forgetting"" that an instance is running -> data corruption",Linux,Linux,VirtualBox-7.0.6,2023-01-28T08:54:30Z,2023-01-28T08:54:30Z,"I have seen this many times.

I'm not sure how to reproduce this, but something must be fundamentally broken if this is can happen, so you should be able to figure this out my looking at the code.

Here is what happens.

I am working with guests.
Suddenly, _something_ happens, which leaves the guest running, but gives VirtualBox the impression that it is not running any more.

So VirtualBox thinks that it's switched off.

This happens with both the GUI and if I use VBoxManager list runningvms.

Since it thinks it's off, clicking on it will start it again.

What happens then is that we get two instances running, with both having read-write access to the same underlying storage devices.

You can how this ends: with tears, blood and of course irrecoverable data corruption. (Two OSs writing to the same file system at the same time...)

This is messed up beyond words.

I am attaching a screenshot, which shows two instances of the UI, running on the same host, with the same user.

One shows the guest on, the other shows it off.

The only difference is that I have launched the other instance of the GUI a bit later, but there was no configuration change. There is no reason why would it show a different status.

You can also see the output of list runningvms on the same screenshot. (Empty.)

Btw the actual guest is only visible on the screen, which is showing another data corruption bug with virtio-scsi, about which I will open a separate bug report.
",csillag
19358,VMs lose bridged network connection after host suspend/resume,Windows,all,VirtualBox 6.1.4,2023-01-29T17:33:29Z,2023-01-29T17:33:29Z,"This doesn't happen every time, but often enough to become frustrating: when I suspend/resume the host, '''all''' of the guests (Windows ''and'' Linux) are unable to communicate over the bridged network.

What does '''not''' work:
 - suspending/resuming the guest
 - restarting the guest OS network services
 - restarting the guest OS
 - disabling/enabling the guest's network adapter
 - disabling/enabling the host's network adapter that is bridged
 - disabling/enabling the vbox bridging driver on the host's network adapter

One thing that did work:
 - connect alternate network adapter on host (eg.: wireless) and set as bridge for VM

Aside from that, the only thing that fully works is to reboot the host, but I have several passwords to enter and dozens of applications to run in order to get my environment setup, which makes frequent rebooting untenable.

This may also provide a clue: when I enabled the host's wireless adapter, the host was not able to receive an IP lease from the router's DHCP server, I had to key in a static IP for the host.

Is there a service or executable I can restart or run to kickstart the bridged networking?",VeHav2GoVeeper
21444,"Drag and Drop Host to Guest works, but not Guest to Host",Windows,Linux,VirtualBox-7.0.6,2023-01-29T22:47:36Z,2023-01-29T22:47:36Z,"VirtualBox 7.0.6
Guest: Linux Mint 21.1 XFCE 64 bit
Host: Windows 11

I just did a fresh install of Linux Mint, but I am having some issues with the drag and drop.
I set the option to bidirectional. Dragging from host to guest works, but dragging from guest to host does not. Whenever I attempt to do the latter, one of two possible logs pops up.


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_IPE_UNINITIALIZED_STATUS).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


",Niobium62
21445,"Drag and Drop Host to Guest works, but not Guest to Host",Windows,Linux,VirtualBox-7.0.6,2023-01-29T22:47:42Z,2023-01-29T22:47:42Z,"VirtualBox 7.0.6
Guest: Linux Mint 21.1 XFCE 64 bit
Host: Windows 11

I just did a fresh install of Linux Mint, but I am having some issues with the drag and drop.
I set the option to bidirectional. Dragging from host to guest works, but dragging from guest to host does not. Whenever I attempt to do the latter, one of two possible logs pops up.


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_IPE_UNINITIALIZED_STATUS).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


",Niobium62
17093,Serial I/O troubles between Guest and Host,Windows,all,VirtualBox 5.1.26,2023-01-30T04:57:12Z,2023-01-30T04:57:12Z,"I've only personally seen this in a Windows 10 Pro (64-bit) host environment. But some others I've been in touch with seem to have this with other configurations too.

Scenario:

Host running Windows 10 Pro (64-bit) on computer with no physical COM ports (Lenovo T470p laptop). Guest can be ""anything"", but I've tested with FreeDOS, Ubuntu Linux 16/17, and Windows XP. Using NetSerial (http://pcmicro.com/netserial/) to emulate a COM port. NetSerial will behave as a COM port and as a ""modem emulator"" to allow ""ATDTfoo.bar"" to establish a Telnet session to foo.bar.

In VB Guest Config, I set up the serial port as needed. When Guest OS is launched, the results vary. But there seems to be flow control issues between the Guest and the Host. I've been talking to the author of NetSerial and have been testing with beta versions of NetSerial as well. He sets the correct flags for flow control, etc. But somwhere between the Guest and the Host, data is lost or delayed indefinitely.

When booting a Linux Guest in this setup, doing ""dmesg |grep tty"" does reveal that Linux has detected a 16550A UART on COM1, which is good thus far. Opening a Linux terminal emulator (any will do) using /dev/ttyS0, data IS being sent to NetSerial on the Windows Host. Using it's ""monitor"", I can see data being received from the Client terminal emulator. I can also see data being sent FROM NetSerial into the COM port. On the Guest, however, nothing is received.

When booting a FreeDOS Guest in this setup, I get similar results to the above. Data missing. Data delayed. Flow control issues, etc. 

Every application that I have tested with is requesting flow control to be CTS/RTS (hardware) and not XON/XOFF.

In almost exactly the same scenario, if I ""move"" NetSerial so that it runs inside the guest (Windows XP), there is no problem whatsoever. In that case, NetSerial is emulating a COM port and using Windows XP Guest Network to reach the Internet. No data being lost. No flow control issues.

So this is definitely related to the ""bridge"" between the COM port emulator running on the Host side of things.

There's still quite a bit of use left for serial device I/O, so I would expect this to work 100% in a product of VirtualBox's maturity. This problem has been present in at least the past 8-10 releases, and I suspect before that.

This is not a case of misconfiguration.",joho68
21441,Drag and drop not working,Windows,Linux,VirtualBox-7.0.6,2023-01-30T12:40:13Z,2023-01-30T12:40:13Z,"DnD not working between host (Win 11) and guest Ubuntu 22.04. 

Operazione di trascinamento e rilascio dal guest all'host non riuscita.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Codice uscita:VBOX_E_DND_ERROR (0X80BB0011)
Componente:GuestDnDSourceWrap
Interfaccia:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Chiamante:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

",Dave78
21411,VBOX 7.0.x  graphic corruption - Intel GPU,Windows,Linux,VirtualBox-7.0.4,2023-01-31T07:48:34Z,2023-01-31T07:48:34Z,"With VBOX 7.0 my Xubuntu 22.04 VM is unusable I have too much graphic corruption (Windows 11 Host / Seamless mode).
When I switch the guest app window to full screen I have no more corruption.

I had no issue with VBOX 6.x

Tested with
* Intel Gen 12 CPU (i7-1265U) / Iris Xe Graphics
* Intel Gen 8 CPU (i7-8550U) / Intel® UHD 620

[[Image(https://forums.virtualbox.org/download/file.php?id=47912)]]

I will try on my Nvidia 2800 GTX

Best regards",M.Poil
21449,vboxautostartsvc config file issue with windows domain account,Windows,Linux,VirtualBox-7.0.6,2023-01-31T08:00:56Z,2023-01-31T08:00:56Z,"Following the directions in documentation 2.21.4 Windows: Starting the Autostart Service, I have run into the issue where it is NOT accepting a domain account in the autostart configuration file.  I keep getting ""Unexpected token, expected '='"" error in the windows event log.  My domain user is ""raptor"" in the ""truck"" domain.  Permutations of domain\user, user@domain do not work.  It only works if default_policy=allow, which may be a huge risk.


Config file contains only the following:

{{{
default_policy=deny
raptor@truck={
allow=true
startup_delay=10
}
}}}


Looking at the code, I believe the issue is in src/vbox/frontends/vboxautostart/vboxautostartcfg.cpp in the static function autostartConfigTokenizerCreateToken where getting complete token is checking for RT_C_IS_ALNUM which does not allow for either the \ or the @ part of user name and domain since those are not in the alphanumeric range defined in vbox/include/iprt/ctype.h.",RobertV
21447,VirtualBox 7.x + | DNS / Name resolution problem,Windows,Linux,VirtualBox-7.0.6,2023-01-31T13:57:24Z,2023-01-31T13:57:24Z,"When trying to install a VM with Linux as guest OS under VirtualBox 7.x, the installation fails at the name resolution of the online repo.
This was tested with Debian and Arch Linux. 
The installation gives an error at the moment when the name resolution to the repo is needed.
To exclude an error in the images, Debian was installed from a full image, for this no online repo is necessary during the installation.
In the freshly started OS, however, the error of the non-existent name resolution occurs again, SSH via port forwarding does not work either.
A ping to ""google.de"" is unsuccessful. 
A ping to ""8.8.8.8"", is successful.
During the installation all default values of the installer were taken over.

'''When performing the same installations on VirtualBox 6.1.42, this error does not occur and the name resolution works, likewise SSH works without problems.'''

'''Host: Windows 10 Pro 22H2'''

'''Guest: Debian Stable Bullseye 11.6.0 (Kernel 5.10)
Arch Linux Rolling (Kernel 6.1)'''",carcap
21334,arcaos hard disks not recognized,Windows,other,VirtualBox-7.0.4,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
21451,Upcoming problem for Fedora 38 rpms,Linux,all,VirtualBox-7.0.6,2023-02-01T02:26:58Z,2023-02-01T02:26:58Z,"Fedora 38 (currently Rawhide - but due to be released in April) has tightened the security on the crypto on the rpm packages. While we until only few day ago could use your released Fedora36 packages on even rawhide, that is no longer possible, because your signing mechanism is now outdated.

This is just a heads up for Fedora 38 release in april - it should not affect current Fedora 35/36/37 releases.

Please read this blogpost from nirik about the changes:
https://www.scrye.com/wordpress/nirik/2023/01/31/error-rpmdbnextiterator-skipping-in-fedora-38/

",Yoda
21452,Please add require for kernel headers in Fedora rpm packages,Linux,other,VirtualBox-7.0.6,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
21318,Freeze on Oracle Linux 9.1 w. UEK Kernel,other,other,VirtualBox-7.0.4,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
21454,Error: vmnet_start_interface returned 1001,Mac OS X,Linux,VirtualBox-7.0.6,2023-02-02T07:49:33Z,2023-02-02T07:49:33Z,"Unable to use host only network with 192.0.2.0/24 network

00:00:01.271232 VMNet: Host network with mask 255.255.255.0 (192.0.2.1 to 192.0.2.200)
00:00:01.271907 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DrvVMNet.m(650) int drvVMNetConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_INVALID_PARAMETER
00:00:01.271911 VMSetError: Error: vmnet_start_interface returned 1001
00:00:01.272118 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DevE1000.cpp(8287) int e1kR3Construct(PPDMDEVINS, int, PCFGMNODE); rc=VERR_INVALID_PARAMETER
00:00:01.272121 VMSetError: Failed to attach the network LUN
00:00:01.272141 PDM: Failed to construct 'e1000'/1! VERR_INVALID_PARAMETER (-2) - Invalid parameter.

% cat /etc/vbox/networks.conf
* 192.0.2.0/24
* 0.0.0.0/0 ::/0",urbanchef
21423,No repo for Fedora 37,Linux,all,VirtualBox-7.0.6,2023-02-02T11:15:50Z,2023-02-02T11:15:50Z,"I just updated my Fedora (x86_64) host to release 37.

The DNF upgrade complained of a 404 for the VirtualBox repo.

Sure enough, http://download.virtualbox.org/virtualbox/rpm/fedora/ does not have a '37' child.

Can this be fixed?

Thanks.",Timothe Litt
21107,VM's keep freezing,Windows,Windows,VirtualBox 6.1.38,2023-02-03T08:53:27Z,2023-02-03T08:53:27Z,"Have several different VM's.  They all keep freezing unless I click the mouse pointer in the VM window.  Even tried pausing VM from menu, then unpausing.  Each time the VM runs for about a second or two before it freezes up.  The VM's boot up okay, and windows desktop runs and initializes, but after a few minutes the VM's keep pausing.

Very repeatable.  LMK if more information is needed.  Attached log here from one VM.
Thank you",ArtZ
7381,Delete all snapshots at once,other,other,VirtualBox 3.2.8,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
21061,Shared folder Automount not working properly Linux Mint 21 Cinnamon,Windows,Linux,VirtualBox 6.1.36,2023-02-04T08:53:42Z,2023-02-04T08:53:42Z,"Automount works perfectly in my older Linux Mint 20.3 Cinnamon VM.
I installed Linux Mint 21 Cinnamon. But automount does not work properly.
It mounts the folder and I gave permissions to my user to vboxsf
But the sub folders or files are randomly locked without permissions to read/write. It seems some files/folder are owned by root, those works and some are unknown owner those don't work.
Rebooting will randomly change which file/folder have root or unknown owner.

Latest VBox and guest additions is installed.

I tried disabling automount and doing a manual mount or adding to /etc/fstab and both work perfectly.
",Munch
21455,Host with v7.0.6 seeing significantly higher cpu usage vs v6.1.40,Windows,Windows,VirtualBox-7.0.6,2023-02-04T20:15:27Z,2023-02-04T20:15:27Z,"I just tested the latest version 7.06 running the same exact vm's. 20 vms in and it's already at 38% cpu.

I tried the same vm's again using v6.1.40 and I can run 40 vm's no problem while only using 18% cpu.

Host system

CPU: Dual EPYC 7742
Ram: 500G
Drive: U.3 SSD's


Windows 7 guest.
I'm running the 32-bit 4 wallets on each vm.
https://www.crypto-city.com/element-hyp/wallet/
https://www.crypto-city.com/truckcoin-trk/info
https://www.crypto-city.com/xra-rate-coin/info
https://www.crypto-city.com/bitflowers/wallet/",VirtualBoxFan
21212,Copying URL from guest to host causes the VM to crash (SharedClipboard),Linux,Windows,VirtualBox-7.0.2,2023-02-05T12:13:10Z,2023-02-05T12:13:10Z,"Host OS: Fedora Linux 36 x64 X11 (Xorg) kernel 5.19.16
Guest OS: Windows XP Professional x86 (with Microsoft Premier Extended Support Updates 'till July 2019)
Bug: Copying URL from guest to host causes the VM to crash

Bug Description:
When Shared Clipboard is enabled, it's possible to copy text from guest to host and vice versa, however when ""particular"" things like URL and other particularly formatted texts are copied (like from Chrome etc) those fail to be converted properly and therefore cannot be pasted to the host. On top of that, this might lead the guest to crash, which of course is bad.

To highlight the relevant portion of the logs, I'd say that this should give a pretty good insight:


{{{
08:37:22.815753 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816014 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816241 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816442 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816727 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:22.816894 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
08:37:52.813496 Shared Clipboard: Requesting data in format 0x1 for X11 host failed with VERR_TIMEOUT
08:37:52.813528 Shared Clipboard: Converting VBox formats 'UNICODETEXT' to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3, atomTarget='UTF8_STRING') failed, rc=VERR_TIMEOUT
08:38:22.814024 Shared Clipboard: Error reading host clipboard data from X11, rc=VERR_TIMEOUT
08:38:22.814071 Shared Clipboard: Reading host clipboard data failed with VERR_TIMEOUT
08:38:22.814101 Shared Clipboard: Requesting data in format 0x1 for X11 host failed with VERR_TIMEOUT
08:38:22.814156 Shared Clipboard: Converting VBox formats 'UNICODETEXT' to 'UTF8_STRING' for X11 (idxFmtX11=1, fmtX11=3, atomTarget='UTF8_STRING') failed, rc=VERR_TIMEOUT
08:38:22.814179 Shared Clipboard: Converting X11 format 'UTF8_STRING' (idxFmtX11=1) to VBox format 0x1 failed, rc=VERR_NO_DATA
}}}

To put this into context, I was trying to copy the following URL from Chrome Canary via an RDP session from a Windows XP VM:

",FranceBB
21461,ver 7.0.6 failed to install,other,other,VirtualBox-7.0.6,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
21153,Programs show garbage output,Windows,Linux,VirtualBox 7.0.0,2023-02-07T11:03:50Z,2023-02-07T11:03:50Z,Both alacritty - which uses the GPU - and emacs do not show characters and display garbage on typing under Wayland in Ubuntu 22 in VirtualBox 7.0. Currently unusable.,palladio
21462,vm crash,Windows,Windows,VirtualBox-7.0.6,2023-02-07T19:19:31Z,2023-02-07T19:19:31Z,"Restoreing Snapshot crashing vm on vbox 7.0.6
image: Atlas 20H2 -> https://atlasos.net/downloads
",okoca
21470,Emulated TPM does not include Endorsement Key (EK) certificate,Mac OS X,Linux,VirtualBox-7.0.6,2023-02-07T21:37:06Z,2023-02-07T21:37:06Z,"The command ""sudo tpm2_nvread 0x1c00002 > ekcert.der"", installed with the tpm2-tools package on Linux, does not return an endorsement key (EK) certificate. On VMware Fusion's emulator, a self-signed dynamic certificate/key pair is dynamically created in the emulated TPM and the above command works fine.",NedRyerson
21474,Global buffer overflow in hdaMmioWrite(),Linux,Linux,VirtualBox-7.0.6,2023-02-08T03:23:02Z,2023-02-08T03:23:02Z,"When issuing mmio_writeb(0x2146, 0xc2), cbBefore[1] can be too large for g_afMasks[2], which only has five elements.

{{{
static DECLCALLBACK(VBOXSTRICTRC) hdaMmioWrite(PPDMDEVINS pDevIns, void *pvUser, RTGCPHYS off, void const *pv, unsigned cb) {
    // ...
    idxRegDsc = hdaR3RegLookupWithin(off);
    if (idxRegDsc != -1)
    {
        uint32_t const cbBefore = (uint32_t)off - g_aHdaRegMap[idxRegDsc].off; // [1]
        Assert(cbBefore > 0 && cbBefore < 4);
        off      -= cbBefore;
        idxRegMem = g_aHdaRegMap[idxRegDsc].idxReg;
        u64Value <<= cbBefore * 8;
        u64Value  |= pThis->au32Regs[idxRegMem] & g_afMasks[cbBefore]; // ------> [2]
}}}",cyruscyliu
21475,TwinCAT conflict,Windows,other,VirtualBox-7.0.6,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
21477,Custom VM icons don't show up in Ubuntu Dock with VirtualBox 7,Linux,other,VirtualBox-7.0.6,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
21476,Virtualbox 7.x wrong Guest Additions info at Runtime Information,Linux,Linux,VirtualBox-7.0.6,2023-02-09T15:34:17Z,2023-02-09T15:34:17Z,"I noticed Virtualbox 7.x wrong Guest Additions info at Runtime Information. It is something i am seeing for a long time now (7.x and back 6.x).

    
{{{
sudo VBoxControl guestproperty enumerate
}}}


reports the right version though, but Machine -> Session Information -> Runtime Information' is reporting 6.0.0 r127566 for a long time now, in all my linux guests on linux hosts; no matter what kernel or linux version of Fedora i use or have used.
My windowsVM does report the right version btw.
There are no other GA files on the guest machines but 7.0.6",Richard E van der Luit
21440,I/O errors with virtio-scsi,Linux,Linux,VirtualBox-7.0.6,2023-02-09T18:44:17Z,2023-02-09T18:44:17Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
21489,VirtualBox Freeze Issue,other,other,VirtualBox-7.0.6,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
18018,'About' box text is unreadable,Linux,other,VirtualBox 5.2.18,2023-02-10T01:08:30Z,2023-02-10T01:08:30Z,"virtual Box 5-2
Linux Mint 19 x64 Cinnamon",JN
21443,VERR_HGCM_SERVICE_NOT_FOUND vbox 7.0.6,Windows,Linux,VirtualBox-7.0.6,2023-02-10T09:58:56Z,2023-02-10T09:58:56Z,"After downloading the update for 7.0.6, installed over the top of my version 6. On completion, booted my Fedora guest.  Got to the login.  Entered credentials.  At this point I can only assume that it was connecting to resources and preparing audio and graphics for the desktop. One or two seconds after entering credentials, got an error message that the guest had crashed. The only options were to click OK to terminate the guest or to debug the guest.

Reverted back to 6.1.42, tweaked audio driver from WAS (not sure how that setting made it into the vbox file) to DirectSound (had to do this since it failed to add the guest due to driver error), booted the guest and was just fine.",Kronos1776
21278,UEFI Linux guest fails to boot in VB 7,other,Linux,VirtualBox-7.0.2,2023-02-10T10:08:12Z,2023-02-10T10:08:12Z,I upgraded to VB 7 on Monterey 12.6 and it fails to boot a Linux-based guest in UEFI mode. Log attached.,mauricev1
21488,Crash when i change network settings in Ubuntu => fixed in SVN next/7.0.x maintenance,other,other,VirtualBox-7.0.6,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
21491,Restore current snapshot checkbox missing when closing down the VM,other,other,VirtualBox-7.0.6,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
21291,Virtualbox 7.04: Windows 11 guest hangs with hyper-V paravirtualization enabled,Linux,Windows,VirtualBox-7.0.4,2023-02-11T00:15:35Z,2023-02-11T00:15:35Z,"Running Virtualbox 7.04 on a linux host (ubuntu 22.04). Machine is a laptop with an Intel Core i7-10510U CPU and Intel integrated graphics.

I am trying to use a Windows 11 guest.

If I set the paravirtualization interface to ""default"" or Hyper-V (which I guess is the default when windows 11 guest type is selected), then the Windows 11 guest hangs quite frequently. In fact, trying to start word is enough to systematically hang the guest OS. If I set the paravirtualization interface to KVM (which I guess is something that Win11 cannot talk to), then I have no hangs.

I do not know if this is relevant, but I have the latest Virtio drivers for paravirtualized SCSI and network interface installed in Windows.

Any clue?",sercallegar
15308,guest does not regain network connectivity if cable unplugged for for 5+ secs,Windows,Linux,VirtualBox 5.0.16,2023-02-11T00:27:22Z,2023-02-11T00:27:22Z,"Host = Windows 10 Version 1151 (Build 10586.164)
Guest = CentOS7.2.1511 x86_64 (Kernel 3.10.0-327.el7.x86_64)

VirtualBox VM has 2 adapters
- 1 = Host-only Adapter (VirtualBox Host-Only Ethernet Adapter)
- 2 = Bridged Adapter (Intel Ethernet Connection I219-LM)

Networking functions 100% between the VM and LAN if I power on the VM with the Ethernet cable plugged in to the bridged interface (Intel Ethernet Connection I219-LM). The VM can communicate with my LAN and vice versa.

If I start a ping from within the Linux VM and disconnect the Ethernet cable from the bridged interface (Intel Ethernet Connection I219-LM) and plug it back in within 5 seconds, the ping picks back up where it left off.

If it takes more than 5 seconds for me to plug the cable back in, the ping does not pick back up and I need to shut down the VM and cold boot it in order to restore networking between the VM and LAN. Restarting the guest Linux networking, a VM reboot, or a disable/enable of all Windows' interfaces does not regain network connectivity to the Linux VM. Only a shutdown and cold boot of the VM.

I've tried the various ""Adapter Types"" in VirtualBox to no avail.

I run static IPs in the guest.

Virtual LAN = 192.168.184.0/24
VirtualBox NIC in PC = 192.168.184.1/24
Linux enp0s8 = 192.168.184.2/24 (default gw 192.168.184.1)

Physical LAN = 10.70.0.0/24
Windows physical NIC = 10.70.8.139/16
Linux enp0s17 = 10.70.8.130/16

Note: If I put the PC to sleep (tested up to 5 mins) and wake it back up, pings pick back up. It's just when I disconnect the cable to more than 5 seconds and plug it back in, the pings do not pick back up.",Tim Riley
21433,[VirtualBox 7.0.x] Graphical artifacts with 3D acceleration enabled | Windows 7/10 guest,Windows,Windows,VirtualBox-7.0.6,2023-02-11T20:22:32Z,2023-02-11T20:22:32Z,"After installing the Guest Additions on guests like Windows 10 or Windows 7 (on Windows 7 you need to additionally enable Aero) and having the 3D acceleration enabled, graphical glitches/artifacts/issues start appearing.

Example steps to reproduce:
1. Create a new Windows 10 VM (enable 3D acceleration in the VM settings)
2. Install Windows 10
3. Install Guest Additions
4. Restart guest system (to complete Guest Additions installation)
5. After restarting, you should start seeing graphical issues, like:
* transparent News and Interests button
* white squares when browsing through the Start Menu (or completely white Start Menu)
* or flickering menu that opens after clicking on “Type here to search” and moving your mouse

Video: https://www.youtube.com/watch?v=QZ0pQqBiykE

Host GPU: Gigabyte GeForce GTX 960 Windforce OC 4GB DDR5/128bit DVI/HDMI/DP[[br]]
Host Driver Version: 528.24

I also would like to add that those issues are exclusive to VirtualBox 7. I didn't encounter them on VirtualBox 6.",przemo20
21492,Host Win11-VM with Win11 works under VB 6.1.x under VB 7.0.x VM freezes after a few minutes,Windows,Windows,VirtualBox-7.0.6,2023-02-11T22:33:27Z,2023-02-11T22:33:27Z,"Problem: 

One of my most important VMs that runs every day and often for several days at a time is a Windows 11 VM (current kernel and driver, updated from Windows 7->Windows 10->Windows 11) and runs without problems and Virtualbox 6.1.x

As soon as the same VM runs under 7.0.x it freezes with the same settings, etc. I hoped that the error would disappear with the later versions and bug fixes in 7.0.x but unfortunately the behaviour is still the same (since 7.0.0 to 7.0.6).

Of course the latest VirtualboxGuestAdditions are always installed (at the moment the 7.0.6 VirtualboxGuestAddoitions runs in the Win 11 VM under Virtuelbox 6.1.42 without problems) in every Virtualbox version in the Win 11 VM.

I have already tried the settings such as ParaVirtualisation Hyper-V or Default and 3D acceleration on or off (normally off). Nothing helped-

Host System: Windows 11
CPU: Intel i7-6820
RAM: 64GB
Graficcards: Intel HD Graphics 530 (Driver Version 31.0.101.2115 (Date: 16.11.2022)) , Nvidia Qua M2000M (Driver Version 31.0.15.2824 (Date: 15.01.2023))


",RonaldMcDonald
21487,3D acceleration causes Linux guest freezes,Linux,Linux,VirtualBox-7.0.6,2023-02-12T01:04:54Z,2023-02-12T01:04:54Z,"Hi,

//Checking the forums, there seems to be several people reporting instances of their '''Windows 11 Guests''' freezing.  I have a situation with '''Linux Guests'''.  Below are some details in case you need a test case.//

I'm experiencing frequent freezes when 3D acceleration is enabled on Linux Guests.  There is no issue with a '''Windows 10 Guest'''.

The current work-around is to disable 3D acceleration.

I captured a core dump of the frozen Guest using '''vboxmanage debugvm dumpvmcore'''.  If there is any value, I can upload it to my G Drive.  It is 460 MB.

== Environment ==

=== Guest

I have tried to create a minimal test case using openSUSE MicroOS (immutable O/S).

Below are some of the highlight settings of the Guest.  However I suspect '''VBox.log''' may only be needed.

* Download latest MicroOS - https://get.opensuse.org/microos/#download
* Set up a new Guest VM:
  * Base memory:  3072 MB (4096 crashes)
  * Processor:  1
  * Storage:  
    * controller > Use Host I/O Cache
    * 30 GB vdi > Solid-state Drive (assuming you're using an SSD)
      * Current allocation is 8.02 GB
  * Display:
    * Video Memory:  128 MB
    * Graphics controller:
      * VMSVGA
      * Enable 3D Acceleration
* Using the MicroOS ISO, create a new Guest
  * Selected local TZ rather than UTC.
  * Select KDE desktop
* On first boot, the Guest will set up bootstrap apps.
* Use '''discover''' to install the '''Brave browser'''.  '''Discover''' is KDE's flatpak manager.  By default, it lives in the systray.  Its icon is a blue shopping bag.  :)
* I did some minor KDE tweaking (e.g. focus-follows-mouse, etc.)  If required, I could upload a tar-ball of the test user's $HOME.

=== Test Case

Using the test case below, the Guest may take upwards of a few hours to freeze.  Sometimes it freezes in a few minutes.

I run it in a '''Virtual Desktop''' and periodically check.

* Run two instances of '''Brave'''
* In each, go to web pages that auto-refresh periodically.  For example:
  * https://edition.cnn.com
  * https://www.theweathernetwork.com/fr/weather/ile-de-france/paris

=== Host

* openSUSE Tumbleweed - rolling distro
* Regularly kept up to date.
* As of this writing, kernel 6.1.8-1
* Using '''Prime offloading'''
  * iGPU - Intel UHD Graphics
  * dGPU - Nvidia GeForce RTX 2060 Max-Q  
",Pablo Sanchez
21493,"DnD: Error: Drag and drop to guest not possible -- either the guest OS does not support this, or the Guest Additions are not installed.",Windows,Linux,VirtualBox-7.0.6,2023-02-12T05:48:02Z,2023-02-12T05:48:02Z,"Drag and drop operation from host to guest failed.

DnD: Error: Drag and drop to guest not possible -- either the guest OS does not support this, or the Guest Additions are not installed.

Código de Resultado: VBOX_E_DND_ERROR (0X80BB0011)
Componente: GuestDnDTargetWrap
Interface: IGuestDnDTarget {50ce4b51-0ff7-46b7-a138-3c6e5ac946b4}
Chamador: IDnDTarget {ff5befc3-4ba3-7903-2aa4-43988ba11554}

",Willian Tetsuo Kaneta
21494,Only crashes and error messages since the update to 7.0.6,Windows,Windows,VirtualBox-7.0.6,2023-02-12T11:33:02Z,2023-02-12T11:33:02Z,"The update has been around for a while, though I've always put it off until now. And as it turns out, for a good reason: since the latest update, I only get error messages. I don't know what the new ""update"" is supposed to bring, except some improvements in the GUI. 

PC was already restarted after the update, just as info. 

So, the problem is that sometimes I can start a new VM and sometimes not. The VM is W10, if relevant. Everything has remained as it is so far, nothing was changed at all after the update. It's even worse when I want to boot/activate a saved state, that doesn't work at all by now since the update. There come then error messages like:

Callee RC:


RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)


or


The instruction at 0x... referenced memory at 0x0000000000. The memory could not be written. Click on OK to terminate the program. Click on CANCEL to debug the program.",FrankKlein
21219,RPC_S_SERVER_UNAVAILABLE when closing down VirtualBox GUI before virtual machine starts (regression),Windows,Linux,VirtualBox-7.0.2,2023-02-12T15:38:45Z,2023-02-12T15:38:45Z,"Problem description:
1. In Oracle VM VirtualBox Manager (GUI tool) click on virtual machine and then Start button.
2. Because I don't need VirtualBox Manager GUI anymore I close it down.
3. Like 2 to 3 seconds later I get error:
Failed to open a session for the virtual machine <vm name>
and Details:
Callee RC: RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)

It looks to me this problem only appears if VirtualBox Manager is closed down before virtual machine is getting started.

If I wait for few seconds and the virtual machine's window appears before I close down VirtualBox Manager, it looks like error never appears.

This problem started to happen now that after using VirtualBox 6.1 for years I upgraded directly to VirtualBox 7.0.2.

I am very used to closing down VirtualBox Manager after I click on Start virtual machine button. It gets supper annoying that I get this error, because I just forget that now for some reason I have to wait before virtualbox machine GUI appears.

It looks like a regression in v7.0 comparing to v6.1.

My host is: Windows 10
My guest is: Ubuntu 22.04",bobJ
21495,A critical error has occurred while running the virtual machine,Windows,other,VirtualBox-7.0.6,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
21496,VirtualBOx 7.0.6 warning for macOS 10.13.x or earlier,Mac OS X,all,VirtualBox-7.0.6,2023-02-12T18:54:14Z,2023-02-12T18:54:14Z,"VirtualBOx 7.0.6 installer should render an error if the host system is macOS High Sierra or earlier. The installer should halt and provide option to quit, and should not proceed with a success then render a popup box that it requires macOS Catalina or higher.",danskoya
21497,Wrong Bus Frequency and DRAM Frequency,Windows,other,VirtualBox-7.0.6,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
21498,"French translation missing for ""System""",other,other,VirtualBox-7.0.6,2023-02-12T19:55:21Z,2023-02-12T19:55:21Z,"French translation missing for ""System""
should be ""Système""",Kyle_Katarn
21499,aRC=VBOX_E_FILE_ERROR (0x80bb0004),Linux,Linux,VirtualBox-7.0.6,2023-02-12T20:12:20Z,2023-02-12T20:12:20Z,"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



",pabel
21500,aRC=VBOX_E_FILE_ERROR (0x80bb0004),Linux,Linux,VirtualBox-7.0.6,2023-02-12T20:21:59Z,2023-02-12T20:21:59Z,"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



",pabel
21501,[GuruMeditation] VirtualBox inside VirtualBox.,Linux,Windows,VirtualBox-7.0.6,2023-02-12T23:47:37Z,2023-02-12T23:47:37Z,"Host: Windows 10 
VM that I am working on: Arch-Linux
VM that I am trying to start inside the Arch-Linux VM: Alpine-Linux

I thought it was a problem about the Arch-VM, or dedicated resources, but no, I also tried to start the Alpine-VM inside a Xubuntu-VM and a Debian-VM, but still get Guru Meditation.
",Nobody
21283,"Windows 11 VM freezes with Windows 11 Host, VirtualBox 7.0.4",Windows,Windows,VirtualBox-7.0.4,2023-02-13T18:04:08Z,2023-02-13T18:04:08Z,"I am running Windows 11 Pro 22621.819 with VirtualBox 7.0.4 and Hyper-V disabled. I was seeing the Windows 11 Guest VM freeze very quickly after boot, often within a few minutes. After the upgrade to 7.0.4 it still freezes, but after running for several hours. So it's better, but not fixed. This VM is a prebuilt developer image from Microsoft (WinDev2210Eval) with all Windows Updates applied to it.

",cmptrgk
21502,PhpStorm is not displayed correctly,Windows,Linux,VirtualBox-7.0.6,2023-02-13T19:22:45Z,2023-02-13T19:22:45Z,"After update to version 7.0.6 windows of PhpStorm displays with black screen. only some icons are visible on the black screen.
VM Log - [https://pastebin.com/HuEXwQXt]
[[Image(https://prnt.sc/JvSroECLwPJT)]]",Dmytro
21490,Bitnami OVA Aborts on M2 Mac Mini Using Virtualbox Developer preview for macOS / Arm64 (M1/M2) hosts,Mac OS X,Linux,VirtualBox-7.0.6,2023-02-13T20:50:05Z,2023-02-13T20:50:05Z,"Using an M1 Mac Mini 2020, I found the new VirtualBox-7.0.6_BETA4-155176-macOSArm64 download at VirtualBox.org. This is the Developer preview for macOS / Arm64 (M1/M2) hosts.

VirtualBox installs fine and opens as usual.

I imported the Bitnami VM OVA for ResourceSpace bitnami-resourcespace-10.0.0-31-r29-linux-vm-debian-11-x86_64-nami.ova

No apparent problem with importing.

When I click Start, the VM starts the Linux boot, gives a little bit of progress: GRUB Booting Debian GNU/LInux and then the boot sequence aborts and VirtualBox displays Aborted for the status of the VM.

Any ideas what might be happening? Do Bitnami VMs work with the Developer version of VirtualBox for M1 and M2 Mac Minis?

The same problem occurs on an M2 Mac Mini Pro new out of the Box (2023).
",Kyosho at ZMM
21503,VirtualBox 6.1.42 failed to install on MacOS 10.13.6 (High Sierra),other,other,VirtualBox-6.1.42,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
21448,VirtualBox 7 VM Freezes or UI glitches,Linux,Windows,VirtualBox-7.0.6,2023-02-14T08:39:15Z,2023-02-14T08:39:15Z,"Using VirtualBox VM 7.0.6 (guest additions installed) with an Ubuntu 22.04 LTS host and Win 11 guest, with an nvidia RTX 3080 Ti (and attaching log).

If I use the above combination I get frequent VM freezes (even if I leave it for hours).  This happens regularly especially  when I launch a browser (both MS edge and firefox exhibited this behaviour). The only way to recover is with a ""power off"" of the VM.

I have read in the forums (second post here: https://forums.virtualbox.org/viewtopic.php?f=2&t=107371) that this happens with VB7 and the solution for it is to enable 3D acceleration in the settings. I do that and the VM stops freezing BUT ...

The UI is almost unusable as it is broken in multiple ways (even when switching transparency off): broken borders, broken backgrounds, flickering, fonts looks rough, buttons disappear, etc etc etc.  For example when I launch MS Office, I get an empty (white) panel and nothing else. This is certainly related to 3D acceleration as when I set a regedit key (DisableHardwareAcceleration to 1) to disable 3D hardware acc. for office 365, this starts working normally.  But the rest of the OS still suffers from the visual glitches.

Let me know if you require any more info.



",Jean-Paul Ebejer
21463,Kali Linux,Linux,Windows,VirtualBox-7.0.6,2023-02-14T11:16:52Z,2023-02-14T11:16:52Z,"My Kali on the VM is not syncing-Kernel Panic, need help as I'm not able to finish my online school project without this
",Sonja
21446,Linux guest additions 7.0.6: vbox_drv.c compile error with (RH)EL 8.7 kernel: implicit declaration of function ‘vgacon_text_force’ => fixed in svn,Windows,Linux,VirtualBox-7.0.6,2023-02-14T11:36:42Z,2023-02-14T11:36:42Z,"Host:
- Microsoft Windows [Version 10.0.19044.2486]
- VirtualBox 7.0.6 r155176 (Qt5.15.2)

Guest (as updated to latest 8.7):
- RockyLinux 8.7
- kernel: 4.18.0-425.10.1.el8_7.x86_64

Guest additions kernel module will fail to build on:

{{{
/tmp/vbox.0/vbox_drv.c: In function ‘vbox_init’:
/tmp/vbox.0/vbox_drv.c:54:34: error: implicit declaration of function ‘vgacon_text_force’ [-Werror=implicit-function-declaration]
 #  define VBOX_VIDEO_NOMODESET() vgacon_text_force() && vbox_modeset == -1
                                  ^~~~~~~~~~~~~~~~~
}}}
(see attached log)

Same build error w/ VBoxGuestAdditions_7.0.7-155247 (latest testing available)

I've seen in RHEL kernel changelog that nomodeset changes might have been backported into -425, not sure if this is the cause though?

{{{
* Fri Dec  9 13:00:00 2022 Jarod Wilson <jarod@redhat.com> [4.18.0-425.9.1.el8_7]
- Documentation/admin-guide: Document nomodeset kernel parameter (Jocelyn Falempe) [2145218 2143952]
- drm: Move nomodeset kernel parameter to the DRM subsystem (Jocelyn Falempe) [2145218 2143952]
}}}


Changing
{{{
#  define VBOX_VIDEO_NOMODESET() vgacon_text_force() && vbox_modeset == -1
}}}
to
{{{
#  define VBOX_VIDEO_NOMODESET() drm_firmware_drivers_only() && vbox_modeset == -1
}}}
seems to fix the build, although I have no idea whether this produces working driver module.",mareks
21450,Cannot build Guest Additions 7.0.6 for CentOS Stream 9 kernel 5.14.0-239.el9.x86_64 => fixed in svn,Windows,Linux,VirtualBox-7.0.6,2023-02-14T11:37:32Z,2023-02-14T11:37:32Z,"{{{
In file included from /tmp/vbox.1/vboxvideo_guest.h:34,
                 from /tmp/vbox.1/modesetting.c:27:
/tmp/vbox.1/vbox_drv.h:378:32: error: field ‘base’ has incomplete type
  378 |         struct drm_framebuffer base;
      |                                ^~~~
In file included from /tmp/vbox.1/hgsmi_base.c:27:
/tmp/vbox.1/vbox_drv.h:378:32: error: field ‘base’ has incomplete type
  378 |         struct drm_framebuffer base;
      |                                ^~~~
make[2]: *** [scripts/Makefile.build:321: /tmp/vbox.1/hgsmi_base.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [scripts/Makefile.build:321: /tmp/vbox.1/modesetting.o] Error 1
make[1]: *** [Makefile:1915: /tmp/vbox.1] Error 2
make: *** [/tmp/vbox.1/Makefile-footer.gmk:133: vboxvideo] Error 2
}}}
",Steven Barre
21505,Black Screen and Blinking Cursor using 3D Accelerator,Windows,Windows,VirtualBox-7.0.6,2023-02-15T11:37:54Z,2023-02-15T11:37:54Z,"I have installed VB-7.0.6 with 7.0.6 Guest Additions on my Windows 7 Pro client.   However, if I turn on 3D Accelerator in Settings, my system then has a black screen and a blinking cursor and is unusable.  

When I reported this issue here:  https://forums.virtualbox.org/viewforum.php?f=2   I was instructed to open a ticket.

Here is the log files and my hardware setup.  ",QB
21504,windows guest on linux host unresponsive with high cpu,other,other,VirtualBox-7.0.6,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
21506,Windows 11 guest is freezing when trying to install an Windows Update,Linux,Windows,VirtualBox-7.0.6,2023-02-15T19:47:09Z,2023-02-15T19:47:09Z,"I experienced permanently that Windows 11 as guest freezes (with 100% CPU load), and I have to shutdown the virtual machine and restart. 

Now I can reproduce the freezing: when Windows installs an update (in my case during installation of Windows 11 22H2, at 24%. The log is attached - I cannot see any indicators. 

How can I narrow down the cause of the freezing?",Dr. Michael Hälsig
21189,"UI usability of VBox 7/on removed ""Restore Snapshot at Power Off""",all,all,VirtualBox-7.0.2,2023-02-16T16:36:54Z,2023-02-16T16:36:54Z,"I know this bug report will fall of deaf years but I don't care. I just want to file it so that you knew that not everyone is happy with what you've done to VBox 7.

---

I hear all the wrong reasons to remove the feature, so let me give all the reasons why it worked before, why it was never an issue and why the current ""Edit a config file manually"" approach is wrong:

1) Absolute most people don't use the VM shutdown feature. They press ""Start -> Shutdown"" in whatever guest OS they are using instead. Using a VM shutdown dialog in just not as convenient.

2) The checkbox is in your face. It's not hidden, it's right there and it's hard not to notice it. People who were burnt by pressing it accidentally maybe did it once in their entire life. I cannot imagine making this mistake more than once.

3) Now instead of a UI feature, I need to edit a config file and then remember the discard feature is enabled. WTF? What if I use it the feature intermittently? I.e. I need it today but I don't need it tomorrow? Go edit the config file again and again? Really?

4) It literally takes a couple of lines of code to hide it by default from all the users and have it enabled only for those who want to use it.

Now, whenever I want to discard the last state of a guest, I need to switch it off, go to snapshot management and hit all the right buttons (an extra ten buttons if you had your guest on any other mode, e.g. Details vs Spapshot management). Multiple actions which were available as a single click of a mouse earlier.

Your UI team is doing all the wrong stuff it seams.

Here's what you could have done [https://forums.virtualbox.org/viewtopic.php?f=15&t=106906 instead]:  - not a single comment from anyone on the team, meanwhile the guest menu is a total incomprehensible illogical mess.

Also the main actions switcher under the main menu (Welcome, Extensions, Media, etc) terribly sucks.
Also the guest actions pop-up menu is terribly inconvenient (Details, Snapshot, Logs, Activity, File Manager). Why is it hidden by default BTW? Why it's only visible on mouse hover on?

People have 1080p, 1440p, dual monitors configurations - you cram everything such a way you need to constantly mouse click, click, click.

The guest actions are all easy to show on the screen simultaneously or make them some sort of tabs. A single click to switch between tabs.

Likewise for the the main actions switcher - why, why, there's a drop-down menu where there's so much space on the screen? VBox is a desktop application and it now looks like the worst UI-wise mobile app.

I presume you have designers/managers on your team who have to make stuff up to get salaries and in the end we get a horrible usability-wise UI where you need to click often while making sure your mouse movements are precise. This is nightmare.

UI in VBox 5 was a [https://news-cdn.softpedia.com/images/news2/oracle-releases-virtualbox-5-0-20-with-fixes-for-linux-kernel-4-5-small-changes-503525-2.jpg ton more] easier, faster and more effective to navigate.

VBox 7 is the absolute worst in terms of UI (I started using VBox around version 3 I guess) and of course user input is not necessary because ""managers"" and ""designers"". Have these people formally run any usability tests? I doubt it. Something was designed as ""cool"" and ""modern"" and poor programmers bent under because they had no choice.


Of course this salty rational logical message will never reach the responsible people. Not the first time. The PC software industry has done everything to destroy usability over the past 15 years, starting with an abomination called Windows 8.

---

And now the linked message:

1) I feel like these three items could/should be moved elsewhere, e.g. to File or Machine as they have nothing to do with ""View"".

2) The Input submenu is so empty I guess it should be best moved to ""Devices"".

3) Speaking of ""File"". This is not a file!

File -> Preferences should be moved to Machine.

File -> Reset All Warnings should be moved to Machine or View.

File -> Close should be moved to Machine or View.

IOW get rid of File altogether.

4) For the main application window - please move ""File -> Tools"" submenu to its own menu item ""Tools"". Will save a lot of fine mouse movements

Thanks!",Artem S. Tashkinov
21431,Win11 guest freezes if VBoxSVGA is used.,Linux,Windows,VirtualBox-7.0.6,2023-02-16T22:08:06Z,2023-02-16T22:08:06Z,"Win11 guest is very unstable if graphics adapter is set VBoxSVGA. It freezes totally very often. I can only see in the logs that guest is unresponsive. Disabling 3d acceleration does not help, only switching to VBoxVGA helps.

Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz
Memory: 15.4 ГиБ of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Driver version: mesa 22.3.3
Manufacturer: Dell Inc.
Product Name: Dell G15 5510

Second graphics card is NVIDIA GeForce RTX 3060 Laptop (optimus) in offload mode
Driver 525.85.05
",MaxF
21507,"Test, please ignore",other,other,VirtualBox-7.0.6,2023-03-28T16:07:15Z,2023-03-28T16:07:15Z,Checking if the notifications work properly.,Klaus Espenlaub
