﻿ticket,summary,host,version,created,modified,_changetime,_description,_reporter
21450,Cannot build Guest Additions 7.0.6 for CentOS Stream 9 kernel 5.14.0-239.el9.x86_64 => fixed in svn,Windows,VirtualBox-7.0.6,2023-01-31T23:04:39Z,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
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,VirtualBox-7.0.6,2023-01-30T12:57:55Z,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
21502,PhpStorm is not displayed correctly,Windows,VirtualBox-7.0.6,2023-02-13T19:00:54Z,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
21219,RPC_S_SERVER_UNAVAILABLE when closing down VirtualBox GUI before virtual machine starts (regression),Windows,VirtualBox-7.0.2,2022-10-30T13:00:37Z,2023-02-12T15:38:45Z,2023-02-12T15:38:45Z,"Problem description:
1. In Oracle VM VirtualBox Manager (GUI tool) click on virtual machine and then Start button.
2. Because I don't need VirtualBox Manager GUI anymore I close it down.
3. Like 2 to 3 seconds later I get error:
Failed to open a session for the virtual machine <vm name>
and Details:
Callee RC: RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)

It looks to me this problem only appears if VirtualBox Manager is closed down before virtual machine is getting started.

If I wait for few seconds and the virtual machine's window appears before I close down VirtualBox Manager, it looks like error never appears.

This problem started to happen now that after using VirtualBox 6.1 for years I upgraded directly to VirtualBox 7.0.2.

I am very used to closing down VirtualBox Manager after I click on Start virtual machine button. It gets supper annoying that I get this error, because I just forget that now for some reason I have to wait before virtualbox machine GUI appears.

It looks like a regression in v7.0 comparing to v6.1.

My host is: Windows 10
My guest is: Ubuntu 22.04",bobJ
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,VirtualBox-7.0.6,2023-02-12T05:48:02Z,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
15308,guest does not regain network connectivity if cable unplugged for for 5+ secs,Windows,VirtualBox 5.0.16,2016-04-14T10:49:47Z,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
21443,VERR_HGCM_SERVICE_NOT_FOUND vbox 7.0.6,Windows,VirtualBox-7.0.6,2023-01-28T19:57:36Z,2023-02-10T09:58:56Z,2023-02-10T09:58:56Z,"After downloading the update for 7.0.6, installed over the top of my version 6. On completion, booted my Fedora guest.  Got to the login.  Entered credentials.  At this point I can only assume that it was connecting to resources and preparing audio and graphics for the desktop. One or two seconds after entering credentials, got an error message that the guest had crashed. The only options were to click OK to terminate the guest or to debug the guest.

Reverted back to 6.1.42, tweaked audio driver from WAS (not sure how that setting made it into the vbox file) to DirectSound (had to do this since it failed to add the guest due to driver error), booted the guest and was just fine.",Kronos1776
21153,Programs show garbage output,Windows,VirtualBox 7.0.0,2022-10-14T23:22:36Z,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
21061,Shared folder Automount not working properly Linux Mint 21 Cinnamon,Windows,VirtualBox 6.1.36,2022-08-13T09:15:34Z,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
21447,VirtualBox 7.x + | DNS / Name resolution problem,Windows,VirtualBox-7.0.6,2023-01-30T14:20:10Z,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
21449,vboxautostartsvc config file issue with windows domain account,Windows,VirtualBox-7.0.6,2023-01-31T08:00:56Z,2023-01-31T08:00:56Z,2023-01-31T08:00:56Z,"Following the directions in documentation 2.21.4 Windows: Starting the Autostart Service, I have run into the issue where it is NOT accepting a domain account in the autostart configuration file.  I keep getting ""Unexpected token, expected '='"" error in the windows event log.  My domain user is ""raptor"" in the ""truck"" domain.  Permutations of domain\user, user@domain do not work.  It only works if default_policy=allow, which may be a huge risk.


Config file contains only the following:

{{{
default_policy=deny
raptor@truck={
allow=true
startup_delay=10
}
}}}


Looking at the code, I believe the issue is in src/vbox/frontends/vboxautostart/vboxautostartcfg.cpp in the static function autostartConfigTokenizerCreateToken where getting complete token is checking for RT_C_IS_ALNUM which does not allow for either the \ or the @ part of user name and domain since those are not in the alphanumeric range defined in vbox/include/iprt/ctype.h.",RobertV
21411,VBOX 7.0.x  graphic corruption - Intel GPU,Windows,VirtualBox-7.0.4,2023-01-16T13:19:25Z,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
21441,Drag and drop not working,Windows,VirtualBox-7.0.6,2023-01-28T14:49:43Z,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
21445,"Drag and Drop Host to Guest works, but not Guest to Host",Windows,VirtualBox-7.0.6,2023-01-29T22:47:42Z,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
21444,"Drag and Drop Host to Guest works, but not Guest to Host",Windows,VirtualBox-7.0.6,2023-01-29T22:47:36Z,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
21430,Ubuntu kernel panic on Windows 11,Windows,VirtualBox-7.0.6,2023-01-24T13:03:26Z,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
21410,RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf],Windows,VirtualBox-7.0.4,2023-01-16T09:54:46Z,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
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,VirtualBox-7.0.6,2023-01-18T10:09:55Z,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
21405,Linux guest on Windows 10 host does not start in seamless mode,Windows,VirtualBox-7.0.4,2023-01-12T14:25:59Z,2023-01-12T14:25:59Z,2023-01-12T14:25:59Z,"When the Linux host is started, it ''always'' starts in windowed mode, not in seamless mode. I must manually switch to seamless. When I shut down the machine in seamless mode and restart it, I expect it to restart in that mode, as it did in former versions of VirtualBox (6.x).

",reibi
21404,SECOND LINUX GUEST CRASHES ON WINDOWS STARTUP - VBOX 7.04 BUG,Windows,VirtualBox-7.0.4,2023-01-12T10:53:01Z,2023-01-12T10:53:01Z,2023-01-12T10:53:01Z,"When i am trying to automatically start a second Linux guest on windows 10 startup (through shell:startup), i get an error and the second Linux guest crashes.

The error message is ""The exception Breakpoint A Breakpoint has been reached (0x0000sFFCF66B225A. Click OK to terminate the program""

This bug  (or similarwith same results) occurs in all updates after 6.1.34 version, so i can't start e second guest automatically.

Please fix it !!!

Thank you ",Tasos Skarpathakis
21403,Broken Display Arrangement Configuration w/ VirtualBox Additions 7.0.4.,Windows,VirtualBox-7.0.4,2023-01-10T19:48:41Z,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
20830,Black Screen on VirtualBox,Windows,VirtualBox 6.1.30,2022-02-16T14:58:05Z,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
21353,apic timer does not trigger in time,Windows,VirtualBox 6.1.40,2022-12-25T01:27:42Z,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
21338,Kernel Panic Boot2Docker Distro,Windows,VirtualBox-7.0.4,2022-12-14T16:44:28Z,2022-12-19T01:57:35Z,2022-12-19T01:57:35Z,Please see this [https://github.com/hashicorp/vagrant/issues/13011 Vagrant bug report]. The comment by phinze suggests this is a VirtualBox issue.,goldfita
21336,VirtualBox 7.0.2 interferes with LG Curved UltraWide 40WP95C audio,Windows,VirtualBox-7.0.2,2022-12-13T18:39:05Z,2022-12-13T18:39:05Z,2022-12-13T18:39:05Z,"I recently bought a LG Curved UltraWide 40WP95C monitor which is hooked up via DisplayPort to an NVidia 1080 graphics card. I use the built-in speakers in the monitor, which appear as 'LG ULTRAWIDE (NVIDIA High Definition Audio)'

System worked fine until I upgraded to VirtualBox 7.0.2 from 6.1.30. After this the audio device above would disappear if the screen blanked. On unblanking, Windows would have selected a different output device. To get the audio device back I had to start the Windows Device Manager and do a 'Scan for hardware changes'. This then found the device which I could then re-select as the output device.

A few seconds after doing the 'Scan for hardware changes' aI would get an error saying 'USB device not recognized', and an 'Unknown USB Device (Port Reset Failed)' would appear in the Device Manager under 'USB controllers'. Looking in the Windows Event Viewer I found an Error, Information and Error at the approx time this occurred. The messages below have a vendor id in them that maps to Virtual Box.


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\Vid_80EE&Pid_CAFE\5&9a1cce4&0&6
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: 
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719

# information

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was configured.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1949
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\5&24955ba6&0&0


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x2B
Problem Status: 0x0


After uninstalling VirtualBox completely the problem disappeared and the 'LG ULTRAWIDE (NVIDIA High Definition Audio)' device has remained available, and selected as the default device, whenever the screen blanks.
",DaveCleland
20520,White screen when 3D Acceleration enabled,Windows,VirtualBox 6.1.26,2021-08-22T17:17:49Z,2022-12-13T07:38:20Z,2022-12-13T07:38:20Z,"I get a white desktop screen after logging into Linux with 3D Acceleration enabled.

VM was working as expected until the August update to VirtualBox.

VirtualBox Version 6.1.26 r145957 (Qt5.6.2)
Oracle VM VirtualBox Extension Pack (Version: 6.1.26 r145957; VRDE Module: VBoxVRDP)

{{{
00:00:19.820085 VMSVGA3d: cap[9]=failed rc=VERR_INVALID_PARAMETER! {S23E8_TEXTURES}
00:00:19.820088 VMSVGA3d: cap[10]=failed rc=VERR_INVALID_PARAMETER! {S10E5_TEXTURES}
00:00:19.820301 VMSVGA3d: cap[62]=failed rc=VERR_INVALID_PARAMETER! {MISSING62}
00:00:19.820348 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:19.820350 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}

00:00:20.333005 GUI: 2D video acceleration is disabled

00:04:46.441670 VMSVGA: PIXEL shader: Failed to create:
00:04:46.441718 0xFFFF0300, 0x0200001F, 0x80010005, 0x900F0000, 0x05000051, 0xA00F0001, 0x00000000, 0x3F000000,
00:04:46.441828 0xBF800000, 0x3F800000, 0x0200001F, 0x80000000, 0xA00F0800, 0x03000042, 0x800F0003, 0x90E40000,
00:04:46.441939 0xA0E40800, 0x02000001, 0x80080000, 0x80E40003, 0x02000001, 0x80070000, 0xA0000001, 0x03000005,
00:04:46.442043 0x800F0001, 0xA0E40000, 0x80FF0000, 0x02000001, 0x800F0002, 0x80E40001, 0x02000001, 0x800F0800,
00:04:46.442146 0x80E40002, 0x0000FFFF,

}}}",Lynda
16296,Left half portion of the guest's widescreen desktop becomes unresponsive to left mouse button clicks,Windows,VirtualBox 5.1.10,2016-12-16T14:35:44Z,2022-11-30T22:57:40Z,2022-11-30T22:57:40Z,"I am not sure what causes this or how to manually reproduce this behavior; otherwise, I would have reported this issue a long time ago.  Almost every day (and after no particular amount of up-time), the left half of my Linux desktop becomes unresponsive to left mouse button clicks.  Left-mouse button clicks do continue to work on the right half portion of the screen.  Actually, it is not the entire left-half portion of the screen that is affected; more like approximately the left two/fifths (left 40%) portion of the entire screen.

This problem is very annoying because smaller windows running in the affected portion of the screen cannot be interacted with or dragged over to the responsive side of the screen.

When this problem occurs, nothing I have tried so far (e.g. restarting the window manager) will correct it.  I am forced to close out (as best as I can) all the running applications in the Linux guest and then reboot the guest OS.

I have no idea what is causing this.  A faulty screensaver timeout process?  Your guess is as good as mine.

Some specific details of my setup:

* Guest OS: 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
* Guest window manager: Openbox 3.5.2
* Host OS: Windows 7 Enterprise 64-bit
* Host configuration: dual identical DELL P2414H widescreen monitors (1920x1080 resolution); VirtualBox is running as a maximized window on my right-side monitor

I believe that this strange behavior has been happening as far back as version 5.0.20 of Virtual Box.",Tony DeFusco
21097,Automatic update of VBox and Failed to open a session for the virtual machine Ubuntu => fixed in SVNsvn,Windows,VirtualBox 6.1.38,2022-09-05T12:04:39Z,2022-11-29T03:04:01Z,2022-11-29T03:04:01Z,"Few weeks ago, when I had updated VirtualBox, I had faced an error with opening a session for the virtual machine (guest OS is Ubuntu).
Found a suggestion that VBox version 6.1.32 is good and I had downgraded the VBox and everything works fine, I can start a session for the VM.
I had turned off the automatic update of VirtualBox, but few times since then, VirtualBox was updated automatically to the newest version.

For some, unknown to me reason, I can't use the newest VBox version, but my VBox keep upgrading even when automatic update is turned off.
What is the solution? Should I downgrade my VBox every day?",AZidai
21307,Virtual Box 6.1.40 r154048(Qt5.6.2) freezing,Windows,VirtualBox 6.1.40,2022-11-24T00:20:32Z,2022-11-24T10:05:03Z,2022-11-24T10:05:03Z,"I recently upgraded VM to the summary version. Subsequently I have had guest system freezes at random times, usually when idle. I am running Linux LinuxMint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. I had on problems with previous versions.  Log should be attached.",Aiki451
19168,Error [drm:vmw_host_log [vmwgfx]] in version 6.1.0,Windows,VirtualBox 6.1.0,2019-12-17T06:21:18Z,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
21274,Incorrect font size use sticks after virtualbox window is moved to the second display,Windows,VirtualBox-7.0.2,2022-11-15T12:44:41Z,2022-11-15T12:44:41Z,2022-11-15T12:44:41Z,"Host Windows 10 PRO
[[BR]]
VirtualBox 7.0.2[[BR]]
Guest: Debian GNU/Linux [[BR]]
uname -a[[BR]]
Linux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux[[BR]]

I have two monitors attached to the PC.
[[BR]]

I have experienced a very annoying font size problem.

When the VirtualBox window is moved to the second display,
virtualbox suddenly causes the guest linux to use very large font.[[BR]]

The problem is that even after I move the virtual box window back to the original 1st display, the large font size is still used and it is really unusable after this happens.
I think the change of font size on the 2nd display may be related to the
different display resolution and used font size (there is an multiplication factor I set using individual config of the display, etc. I am using the Japanese Window and so I don't know the menu names for these settings in English.)


The only reference related such a font size issue I can find is the comment in 
comment 3 of ticket Ticket #20282.
{{{
but it uses a wrong font size if it is on the 2nd screen. 
}}}

Please note that strange font size usage when the program window is moved from the 1st window to the 2nd window is observed for many applications.
MS EXCEL, MS WORD, Thunderbird mail client to name a few, especially only half the window is shifted to the 2nd window.
However, many programs resume to use the right font size once the program window is reverted to the 1st window, or completely moved to the 2nd window.

VirtualBox is the only program that keeps on using strangely large font size even if I move the window back to the original. And for that matter, it keeps on using the strangely large font and it becomes unusable for my purpose.
Once VBox is retarted, the problem goes away, but it is very undesirable.

I will attach screen captures to explain the problem, but I am not sure if I can get the screen dump when the VBox window is split between the two windows.
I will take a photo in that case.
 

",ci-zephyurus
21260,shared folder does not work.  modprobe vboxfs fails due to  missing symbol (Debian kernel 6.0.0.2),Windows,VirtualBox-7.0.2,2022-11-10T07:32:09Z,2022-11-15T06:42:14Z,2022-11-15T06:42:14Z,"Host Windows 10 Pro
22H2 
19045.2251

Guest: Debian GNU Linux
$ uname -a
inux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux

VirtualBox:
7.0.2 r154219 (Qt5.15.2)

---
Problem: Shared folder between host and guest no longer works.

I have noticed that file sharing between the host no longer works.
I *think* this is  related to the local upgrade of the kernel to 6.0.0.2.

I installed the guesttools.
However, after some investigation, I realized vboxsf module is not loaded.
The reason is the missing symbols when vboxsf is loaded.

modprobe vboxsf fails:
{{{
root@ip030:/var/log# modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg)
}}}
dmesg shows:
{{{
[ 1992.940391] Spectre V2 : System may be vulnerable to spectre v2
[ 1992.940396] vboxsf: loading module not compiled with retpoline compiler.
[ 1992.940527] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 1992.940535] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 1992.940541] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 1992.940554] vboxsf: Unknown symbol VBoxGuest_RTStrNLen (err -2)
[ 1992.940589] vboxsf: Unknown symbol VBoxGuest_RTLogBackdoorPrintf (err -2)
[ 1992.940600] vboxsf: Unknown symbol VBoxGuest_rtR0MemObjLinuxVirtToPage (err -2)
[ 1992.940631] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 1992.940637] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 1992.940643] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 1992.940649] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 1992.940655] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 1992.940661] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[ 1992.940667] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 1992.940673] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 1992.940679] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 1992.940685] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRequest (err -2)
[ 1992.940691] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRelease (err -2)
[ 1992.940697] vboxsf: Unknown symbol VBoxGuest_RTSemMutexCreate (err -2)
[ 1992.940702] vboxsf: Unknown symbol VBoxGuest_RTSemMutexDestroy (err -2)
[ 1992.940708] vboxsf: Unknown symbol VBoxGuest_RTMemContAlloc (err -2)
[ 1992.940714] vboxsf: Unknown symbol VBoxGuest_RTMemContFree (err -2)


}}}

It seems that vboxsf is not compiled locally using retpoline compiler?
But I am not sure if it matters or not.

",ci-zephyurus
21186,VM No memory  Result Code:  E_FAIL (0x80004005),Windows,VirtualBox 6.1.40,2022-10-21T13:45:35Z,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
21235,Can't run VBox,Windows,VirtualBox-7.0.2,2022-11-02T17:51:33Z,2022-11-02T17:51:33Z,2022-11-02T17:51:33Z,"I'm first use of vbox . I'm just download vbox and vdi image and run it. And it cause this error
I don't know what type of error it is.",takriz
21228,Plenty of sav files in Snapshots without any snapshot,Windows,VirtualBox-7.0.2,2022-11-01T08:18:24Z,2022-11-02T14:05:48Z,2022-11-02T14:05:48Z,"On Windows 10 host (Ubuntu guest) I have had a plenty of snapshots over period of time I have used VirtualBox 6.1 and now VirtualBox 7.0.2. I created snapshots and deleted them, then creating new ones etc. But today I have deleted all of the snapshots.

Now looking into Snapshots folder and I expect no files are in this folder anymore, but to my surprise there are plenty of files all with SAV file extension (the problem I am reporting).

Command ""dir"" output on Windows host:
19/05/2022  22:08       712.041.461 2022-05-19T21-07-57-214718900Z.sav
31/05/2022  17:56       782.450.690 2022-05-31T16-56-50-903121400Z.sav
07/06/2022  21:46       665.091.925 2022-06-07T20-46-36-299478900Z.sav
22/06/2022  21:55       702.938.444 2022-06-22T20-55-17-961063100Z.sav
14/07/2022  21:12       843.395.181 2022-07-14T20-12-47-010062000Z.sav
06/08/2022  16:09       707.927.057 2022-08-06T15-09-23-494845800Z.sav
30/08/2022  18:16       836.501.505 2022-08-30T17-16-26-777190700Z.sav
02/10/2022  17:44       717.281.998 2022-10-02T16-44-24-007573200Z.sav
07/10/2022  18:45       757.231.318 2022-10-07T17-45-24-466885500Z.sav

From file's date (May, Jun, July and August) I assume this files are from VirtualBox 6.1.x times. From file extension it looks those files are some saved snapshot's states. Why does they still exists? I assume there is/was some bug that does/did not delete saved state when snapshots gets deleted.

I shut down the virtual machine and move those files away from virtual machine Snapshot directory to some directory outside of VirtualBox and I started virtual machine and it starts up successfully and virtual machine works just normally.

I assume those files are not needed anymore, are they? Can I permanently delete them without any harm?",bobJ
21227,VM stop on error,Windows,VirtualBox-7.0.2,2022-10-31T20:56:18Z,2022-10-31T20:56:18Z,2022-10-31T20:56:18Z,Crash during guest OS upgrade.,Дмитро
21213,Loading a saved state stops some graphical apps from rendering until reboot,Windows,VirtualBox-7.0.2,2022-10-28T21:51:10Z,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
21194,Export creates a defective .ova file (missing disk image) : cannot import itself back.,Windows,VirtualBox 6.1.36,2022-10-22T19:25:08Z,2022-10-22T19:25:08Z,2022-10-22T19:25:08Z,"I am using VBox 6.1.36 under Windows 10 Pro.

When I exported my VM from VirtualBox so that it will be imported to VMWare player, etc., VMware Player, and VMWare workstation pro  does not read the disks correctly (I think). 
The number of disks recognized by VMWare player was about half the numbers of attached disks used in VirtualBox. So the import basically failed.

So I tried to read the exported description back to VirtualBox to see what happens.

To my surprise, VirtualBox reported the following error, which collaborates my observation of missing disks in VMWare Player, etc.

--- Begin Quote: The following the error I saw. It is under Japanese Windows 10 Pro.

{{{


仮想アプライアンス""J:\NEW-VMWARE-DIR\debian64bit-Rev02-transition.ova""のインポートに失敗しました。

The above says, VBox failed to import the *.ova description.


&lt;vbox:Machine&gt; element in OVF contains a medium attachment for the disk image 10bf7d63-35a5-4f22-87fd-b11a1634da12 but the OVF describes no such image.

終了コード : E_FAIL (0x80004005)
コンポーネント: ApplianceWrap
インターフェース: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}
}}}


---- end quote

The original VM seems to work just fine as far as I use it to develop patches for Thunderbird mail client and other tasks.
",ci-zephyurus
20924,IPv6 not working out of the box with bridged WiFi and Linux guests,Windows,VirtualBox 6.1.34,2022-05-02T08:32:36Z,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
20937,"Multi monitor operation not working as expected, regression to 5.2",Windows,VirtualBox 6.1.34,2022-05-11T09:46:12Z,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
19131,linux guest os does not recover from host sleep - Win 10 host,Windows,VirtualBox 6.0.14,2019-12-04T18:18:27Z,2022-09-15T08:26:09Z,2022-09-15T08:26:09Z,"Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min. 

If I send the host OS to sleep and immediately (within 5 min), everything is fine.

After a longer sleep, say 20 min, I get varying results:

1) the guest OS seems to have rebooted and I arrive at the login window.  My prior running apps and consoles are gone from the desktop.

2) the OS hangs, showing the login screen.  Mouse and keyboard are not working.  Software reboot (send a shutdown signal) does not work.  Must reboot the guest os. 


My computer is recovering from sleep mode and not hibernate mode.

This seems to have started since 16.x.  I created the guest OS in 15.x.
",eyn
20667,The keyboard not working after the complete installation of Linux Mint 20.2.,Windows,VirtualBox 6.1.28,2021-11-14T12:42:18Z,2022-09-07T08:31:06Z,2022-09-07T08:31:06Z,The keyboard not working after the complete installation of Linux Mint 20.2. When the installation is completed & said press enter keys I pressed but not working please solve this problem this is a bug!,Cannon1000
21094,Guru Meditation Error,Windows,VirtualBox 6.1.38,2022-09-02T18:44:21Z,2022-09-02T18:44:21Z,2022-09-02T18:44:21Z,"I have downloaded the Quickstart Cloudera Vm 5.13.0-0- virtual box with Red Hat for VirtualBox 6.1.38 and when I ""start"" the iteration I get a Guru Meditation critical error. I do not have any chance of interaction. ",fhqwhgads
21085,mp bios bug 8254,Windows,VirtualBox 6.1.36,2022-08-31T11:47:09Z,2022-08-31T11:47:09Z,2022-08-31T11:47:09Z,bende bios bug 8254  noapic hatası veriyor bana yardımcı olun tıkandım kaldım,seafflyy
21076,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,Windows,VirtualBox 6.1.34,2022-08-25T14:16:03Z,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
21069,VM crash diuring install lazarus or anower big packageset,Windows,VirtualBox 6.1.36,2022-08-18T12:13:01Z,2022-08-18T14:01:39Z,2022-08-18T14:01:39Z,"Hello.

BEFORE, latest activity:
I maked before crushes disk shrunked: VBoxManage modifyhd /path/to/VDI/VM.vdi --compact  (path are different, instructions https://askubuntu.com/questions/1092812/zerofree-on-ubuntu-18-04)

then i see excelent resul: VDI file set to 21GB from 500GB 

After somes reboot i try to launth TLauncher und try to install java 8 -- VM crush.
Then i try to install new lazarus - VM crush.  

",Дмитро
21054,Ability for the guest to write on a online-for-the-host partition,Windows,VirtualBox 6.1.36,2022-08-07T18:00:10Z,2022-08-08T07:55:31Z,2022-08-08T07:55:31Z,"because as I saw it's read-only .

On my PC's hard disk with Windows 10 Home :

Host : Windows 10 Home

Guests :

firmware-testing-amd64-netinst.iso ( a Debian installer ) : installing  Debian physically on my PC's hard disk dual-boot with Windows 10 Home , everything works except GRUB isn't installed on the original ESP ( EFI system partition ) with EFI\Microsoft\Boot etc .

debian-live-11.4.0-amd64-xfce+nonfree.iso ( a Debian live ) : cannot write e.g. a file on a PC's hard disk partition ( original ESP , C: , D: , Debian partition ( me on ext2 ) ) .

See https://forums.virtualbox.org/viewtopic.php?f=6&t=106689 .

Is it a regression related to https://www.virtualbox.org/ticket/14425 ?",ecccc3
21040,VM blocked on humongus amounts of disk read,Windows,VirtualBox 6.1.36,2022-07-28T16:20:26Z,2022-08-02T12:01:44Z,2022-08-02T12:01:44Z,"Problem occurring since updating to 6.1.36 from 6.1.34

running condition tested for reproduction:
  - on a old windows 10 host install, run old or new Linux guests (both EFI, and non EFI) that were working on 6.1.34
  - on a fresh windows 10 host install (21H2), with the same scenarios.

steps to reproduce:
  - from a system without VirtualBox installed, or with VirtualBox 6.1.34 installed:
    - install or update to 6.1.36,
    - try to run any linux guest

observed behavior:
  - at startup a 19GB vdi guest generates a 100 second read @ 600+ MB/s (so about 60GB read) blocking the guest execution for the whole time,
  - after logging in, a second wave of read is triggered (about 30s, so 20GB), 
  - and on shutdown the read is also triggered for about 90 seconds rendering the whole process very cumbersome and sluggish.
  - note: using the menu to insert guest additions CD also triggers a read freeze.",os19000
20357,VM launch fail on Windows 10 when WSL2 and Docker is enabled,Windows,VirtualBox 6.1.22,2021-05-11T10:16:02Z,2022-08-01T18:37:28Z,2022-08-01T18:37:28Z,"We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

''WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
''

""Windows Hypervisor Platform"" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM ""Settings - System - Acceleration"" too - OK button remain disabled.

To get VirtualBox VMs running again either ""hypervisorlaunchtype"" must be disabled through Windows Command Prompt with command
{{{
bcdedit /set hypervisorlaunchtype off
}}}
or Docker Desktop must be uninstalled together with ""Windows Hypervisor Platform"", ""Virtual Machine Platform"" and ""Windows Subsystem for Linux"" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:
{{{
Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
}}}",Janis Baumanis
20371,Video recording settings not saved,Windows,VirtualBox 6.1.22,2021-05-19T09:15:39Z,2022-07-28T19:33:56Z,2022-07-28T19:33:56Z,"It seems that video recording settings of VMs are not saved. At least this is true for file path and frame size. Leaving VirtualBox Manager and restarting it, video recording settings are back to default.

In the .vbox file of the VM, I found the entry VideoCapture never reflecting these settings.

Maybe this is related to [ticket:20297], because depending on the modification history of video recording settings I experience the same crash. ",Reiner Brodbeck
21029,no bidirectional clipboard in windows 11 host / ubuntu 18.04 guest,Windows,VirtualBox 6.1.36,2022-07-22T18:28:54Z,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
21025,Screen lock in Windows 10 Host makes the Linux Guest unresponsive (regression),Windows,VirtualBox 6.1.36,2022-07-20T10:59:23Z,2022-07-20T10:59:23Z,2022-07-20T10:59:23Z,"After upgrading from 6.1.30 to 6.1.34, I've started to notice that my Centos 7.8 Guest goes unresponsive on regular basis.

I've been able to pinpoint it to the screen lock in the Windows 10 21H2 Host. Whenever I unlock the screen the VBoxHeadless.exe process uses 100% of all of the cores available to the Guest machine. Guest is unreachable neither by ssh nor by GUI.

This happens regardless of the graphic display used, and also in the headless start. Also changing hypervisor between the Hyper-V and KVM does not make a difference.

VirtualBox 6.1.36 behaves the same as 6.1.34, however downgrading to the 6.1.30 solves the issue.

Logs do not contain anything except repeating pattern of:
00:02:22.924401 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:24.627881 VMMDev: GuestHeartBeat: Guest is alive (gone 5 713 045 344 ns)
00:03:09.694062 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:15.648850 VMMDev: GuestHeartBeat: Guest is alive (gone 9 990 252 305 ns)
00:03:30.642448 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:30.792413 VMMDev: GuestHeartBeat: Guest is alive (gone 4 159 194 451 ns)
00:03:47.088470 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:52.836984 VMMDev: GuestHeartBeat: Guest is alive (gone 9 762 953 270 ns)
00:03:56.874575 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:57.771949 VMMDev: GuestHeartBeat: Guest is alive (gone 4 934 966 056 ns)
00:04:01.784622 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
",MichalBrz
4087,Multimedia keys not passed through to guest,Windows,VirtualBox 2.2.2,2009-05-24T09:58:47Z,2022-07-15T10:43:12Z,2022-07-15T10:43:12Z,"I have a Cherry eVolution STREAM keyboard. The following buttons are not passed through to the guest when pressed:

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

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

The host is Vista Home Basic x64. The guest is Debian using Linux 2.6.26.",Sam Morris
21019,VirtualBox 6.1.34a causing BSOD when plugging in ST-LINK/V2,Windows,VirtualBox 6.1.34,2022-07-10T02:56:55Z,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
20999,Ubuntu 22.04 freezes - Windows 11,Windows,VirtualBox 6.1.32,2022-06-21T16:26:35Z,2022-07-09T23:40:51Z,2022-07-09T23:40:51Z,"I have windows 11, and I downloaded virtualbox 6.1 and installed Ubuntu 22 04. I followd this tutorial (https://www.youtube.com/watch?v=EQy9AUVuyF0&t=1s) step by step.

Ubuntu finished installation without any issues, but when I try to run it, it seems to get stuck. A snapshot is visible at (https://askubuntu.com/questions/1415045/ubuntu-22-04-seems-to-freeze-in-virtualbox-6-1-on-windows-11)

I have tried restarting my computer, but nothing seems to work. Can anyone help with the solution? Thanks in advance.

",user17302
21007,Linux Guest / No Audio in VBox >= 6.1.24,Windows,VirtualBox 6.1.24,2022-06-24T15:12:55Z,2022-06-24T15:12:55Z,2022-06-24T15:12:55Z,"When using VirtualBox >= 6.1.24 (Windows 10 host, Linux Mint Mate 20.2 guest), audio output does not work. It works with VirtualBox <= 6.1.22.

Audio players, video players, browsers, all seemingly work as intended (e.g., video is shown), just no sound.

I tried the following fix: added the line ""options snd-intel8x0 ac97_clock=48000"" to the file ""/etc/modprobe.d/alsa-base.conf"" .

This brought partial improvements: Video is now played with sound -- no matter whether from the internet or my own local .mp4 files. The test ""aplay /usr/share/sounds/alsa/Front_Center.wav"" works. However, my own .mp3 and .wav files, ripped from CD, still don't produce any output.

I also noticed that when I do ""aplay /usr/share/sounds/alsa/Front_Center.wav"" and immediately interrupt it with ctrl-z, audio output ''does'' work. So it seems this aplay provides some initializations that normally are missing.


Attached two log files: One before applying the above-mentioned fix, one after. There are Audio errors in there; however, I have no idea what can be done about them.",aabb
20975,VERR_VMX_VMXON_FAILED during install of CentOS 7,Windows,VirtualBox 6.1.34,2022-06-08T23:22:16Z,2022-06-08T23:22:16Z,2022-06-08T23:22:16Z,While installing CentOS 7 VM failed with VERR_VMX_VMXON_FAILED and  NtOpenDirectoryObject failed on \Driver: 0xc0000022. Unable to restart VM. ,Tony_Z
20940,Unable to boot any VM (Ubuntu): kernel panic - not syncing attempted to kill the idle task,Windows,VirtualBox 6.1.32,2022-05-13T09:25:19Z,2022-06-08T08:42:34Z,2022-06-08T08:42:34Z,"Hello everyone.

I can't boot any of my VMs in Virtualbox. I have several VMs with different versions of Ubuntu, specifically Ubuntu 12 and Ubuntu 20. The same problem occurs in all of them when starting, getting on the screen: ""kernel panic - not syncing attempted to kill the idle task "". Attached log. I have tried to generate a new VM with Ubuntu 12, but I get the same problem. Thanks for your help.",pmartinezOracle
20971,Linux guest VM hangs after upgrading VirtualBox to 6.1.34,Windows,VirtualBox 6.1.34,2022-06-07T18:32:33Z,2022-06-07T18:32:33Z,2022-06-07T18:32:33Z,"I'm running VirtualBox on Windows 10.
I've recently updated VirtualBox from 6.1.30 to 6.1.34.
My Ubuntu 20.04 VM has hung during an upgrade to Ubuntu 22.04.
I had to force close the VM. This has caused the system to become unbootable, so I've installed Ubuntu 22.04 from scratch.
After installation the system started hanging during boot or just after fresh login. The hanging was so hard that the guest system became unusable - I had to force close it.
I've downgraded VirtualBox to 6.1.32, but the problem persisted.
The problem went away after a second downgrade to version 6.1.30.

I'm using a default hypervisor in the VM so it's probably Hyper-V.",Przemysław Kulczycki
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,VirtualBox 6.1.34,2022-06-07T18:16:09Z,2022-06-07T18:21:22Z,2022-06-07T18:21:22Z,"Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.

The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

'''VBoxHardening.log:'''
{{{
1c58.1e4c: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000084 g_uNtVerCombined=0xa04a6300
1c58.1e4c: \SystemRoot\System32\ntdll.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:24.962297600Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.242392000Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1eeb38
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x1f5000 (2052096)
1c58.1e4c:     Resource Dir:    0x184000 LB 0x6fff8
1c58.1e4c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1682
1c58.1e4c:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: NT Layer DLL
1c58.1e4c: \SystemRoot\System32\kernel32.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:16.157371700Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.008042100Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0xbb058
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0xbd000 (774144)
1c58.1e4c:     Resource Dir:    0xbb000 LB 0x520
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\KernelBase.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:25.904947200Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.226771300Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x2cf640
1c58.1e4c:     NT Headers:      0xf0
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x2cd000 (2936832)
1c58.1e4c:     Resource Dir:    0x2a4000 LB 0x548
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\apisetschema.dll:
1c58.1e4c:     CreationTime:    2019-12-07T09:08:13.518339400Z
1c58.1e4c:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
1c58.1e4c:     ChangeTime:      2022-05-13T09:38:12.902031600Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1f538
1c58.1e4c:     NT Headers:      0xd0
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x20000 (131072)
1c58.1e4c:     Resource Dir:    0x1f000 LB 0x408
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1
1c58.1e4c:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: ApiSet Schema DLL
1c58.1e4c: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1c58.1e4c: supR3HardenedWinFindAdversaries: 0x800
1c58.1e4c: \SystemRoot\System32\drivers\cfrmd.sys:
1c58.1e4c:     CreationTime:    2014-06-26T05:33:42.000000000Z
1c58.1e4c:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
1c58.1e4c:     ChangeTime:      2020-10-11T11:10:28.369648400Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x9d20
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Image Version:   6.1
1c58.1e4c:     SizeOfImage:     0xe000 (57344)
1c58.1e4c:     Resource Dir:    0xc000 LB 0x3e0
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Windows (R) Win 7 DDK driver
1c58.1e4c:     ProductVersion:  6.1.7600.16385
1c58.1e4c:     FileVersion:     6.1.7600.16385 built by: WinDDK
1c58.1e4c:     FileDescription: Safe Deletion Driver
1c58.1e4c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: Calling main()
1c58.1e4c: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
1c58.1e4c: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: SUPR3HardenedMain: Respawn #1
1c58.1e4c: System32:  \Device\HarddiskVolume4\Windows\System32
1c58.1e4c: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1c58.1e4c: KnownDllPath: C:\WINDOWS\System32
1c58.1e4c: supR3HardenedWinInit: Performing a limited self purification...
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=SELF_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000042ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000430000-000000000043ffff 0x0004/0x0004 0x0040000
1c58.1e4c:   0000000000440000-000000000044ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000450000-000000000046cfff 0x0002/0x0002 0x0040000
1c58.1e4c:   000000000046d000-000000000046ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000470000-0000000000520fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000521000-0000000000523fff 0x0104/0x0004 0x0020000
1c58.1e4c:   0000000000524000-000000000056ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *0000000000570000-0000000000573fff 0x0002/0x0002 0x0040000
1c58.1e4c:   0000000000574000-000000000057ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000580000-0000000000581fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000582000-000000000058ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000590000-0000000000591fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000592000-00000000005a9fff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000005aa000-00000000005fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000600000-00000000006affff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000006b0000-00000000006b2fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000006b3000-00000000007fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000800000-00000000008c8fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008c9000-00000000008dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008e0000-00000000008e5fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000008e6000-00000000009dffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00000000009e0000-0000000000a06fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a07000-0000000000adffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000ae0000-0000000000b0ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000b10000-0000000000b1efff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000b1f000-0000000000b1ffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000b20000-0000000000b2afff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000b2b000-0000000000d20fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000d21000-0000000000d21fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000d22000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff4407dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff4407e0000-00007ff4407e4fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff4407e5000-00007ff4408dffff 0x0000/0x0002 0x0040000
1c58.1e4c:  *00007ff4408e0000-00007ff5408fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00007ff540900000-00007ff5428fffff 0x0000/0x0004 0x0020000
1c58.1e4c:   00007ff542900000-00007ff542900fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00007ff542901000-00007ff54290ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542910000-00007ff542910fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542911000-00007ff54291ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542920000-00007ff542942fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542943000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc14fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc15000-00007ff7afc17fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc18000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1bfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1c000-00007ff7afc1dfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1e000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe210ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe2110000-00007ffbe2110fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2111000-00007ffbe2225fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2226000-00007ffbe239efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe239f000-00007ffbe23a2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a3000-00007ffbe23a3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a4000-00007ffbe23dcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23dd000-00007ffbe3f1ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe3f20000-00007ffbe3f20fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f21000-00007ffbe3f9efff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f9f000-00007ffbe3fd1fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd2000-00007ffbe3fd2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd3000-00007ffbe3fd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd4000-00007ffbe3fdcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fdd000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe4694fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4695000-00007ffbe4696fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4697000-00007ffbe469ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
1c58.1e4c: kernelbase.dll: timestamp 0x458acb5b (rc=VINF_SUCCESS)
1c58.1e4c: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1c58.1e4c: supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=0
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
1c58.1e4c: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardenedWinDoReSpawn(1): New child 284c.3ce4 [kernel32].
1c58.1e4c: supR3HardNtChildGatherData: PebBaseAddress=0000000000a24000 cbPeb=0x388
1c58.1e4c: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
1c58.1e4c: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
1c58.1e4c: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000a24000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=00000000009bfe78 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
1c58.1e4c: supR3HardenedWinSetupChildInit: Start child.
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1c58.1e4c: supR3HardNtChildPurify: Startup delay kludge #1/0: 523 ms, 34 sleeps
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000087ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000880000-000000000089ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000008a0000-00000000008bcfff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008bd000-00000000008bffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008c0000-00000000009bafff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000009bb000-00000000009bdfff 0x0104/0x0004 0x0020000
1c58.1e4c:   00000000009be000-00000000009bffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000009c0000-00000000009c3fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000009c4000-00000000009cffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000009d0000-00000000009d1fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000009d2000-00000000009fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000a00000-0000000000a23fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000a24000-0000000000a26fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a27000-0000000000bfffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000c00000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff5ee77ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee780000-00007ff5ee780fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee781000-00007ff5ee78ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee790000-00007ff5ee7b2fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee7b3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: supR3HardNtChildPurify: Done after 526 ms and 0 fixes (loop #0).
284c.3ce4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
284c.3ce4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~00000000009bf908)
284c.3ce4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
284c.3ce4: New simple heap: #1 0000000000d00000 LB 0x400000 (for 2052096 allocation)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: System32:  \Device\HarddiskVolume4\Windows\System32
284c.3ce4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
284c.3ce4: KnownDllPath: C:\WINDOWS\System32
284c.3ce4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
284c.3ce4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
284c.3ce4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
284c.3ce4: Registered Dll notification callback with NTDLL.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
284c.3ce4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 107 ms.
284c.3ce4: \SystemRoot\System32\ntdll.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:24.962297600Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1eeb38
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x1f5000 (2052096)
284c.3ce4:     Resource Dir:    0x184000 LB 0x6fff8
284c.3ce4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1682
284c.3ce4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: NT Layer DLL
284c.3ce4: \SystemRoot\System32\kernel32.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:16.157371700Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0xbb058
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0xbd000 (774144)
284c.3ce4:     Resource Dir:    0xbb000 LB 0x520
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\KernelBase.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:25.904947200Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x2cf640
284c.3ce4:     NT Headers:      0xf0
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x2cd000 (2936832)
284c.3ce4:     Resource Dir:    0x2a4000 LB 0x548
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\apisetschema.dll:
284c.3ce4:     CreationTime:    2019-12-07T09:08:13.518339400Z
284c.3ce4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
284c.3ce4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1f538
284c.3ce4:     NT Headers:      0xd0
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x20000 (131072)
284c.3ce4:     Resource Dir:    0x1f000 LB 0x408
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1
284c.3ce4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: ApiSet Schema DLL
284c.3ce4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
284c.3ce4: supR3HardenedWinFindAdversaries: 0x800
284c.3ce4: \SystemRoot\System32\drivers\cfrmd.sys:
284c.3ce4:     CreationTime:    2014-06-26T05:33:42.000000000Z
284c.3ce4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
284c.3ce4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x9d20
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Image Version:   6.1
284c.3ce4:     SizeOfImage:     0xe000 (57344)
284c.3ce4:     Resource Dir:    0xc000 LB 0x3e0
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Windows (R) Win 7 DDK driver
284c.3ce4:     ProductVersion:  6.1.7600.16385
284c.3ce4:     FileVersion:     6.1.7600.16385 built by: WinDDK
284c.3ce4:     FileDescription: Safe Deletion Driver
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: Calling main()
284c.3ce4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
284c.3ce4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: SUPR3HardenedMain: Respawn #2
284c.3ce4: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
284c.3ce4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ntdll.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
284c.3ce4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe4530000 'C:\WINDOWS\System32\ntdll.dll'
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardenedWinDoReSpawn(2): New child 255c.41c4 [kernel32].
284c.3ce4: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
284c.3ce4: supR3HardNtChildGatherData: PebBaseAddress=0000000000ccf000 cbPeb=0x388
284c.3ce4: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
284c.3ce4: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
284c.3ce4: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000ccf000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=0000000000b9fad8 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
284c.3ce4: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
284c.3ce4: supR3HardenedWinSetupChildInit: Start child.
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
284c.3ce4: supR3HardNtChildPurify: Startup delay kludge #1/0: 524 ms, 34 sleeps
284c.3ce4: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
284c.3ce4:  *0000000000000000-0000000000a5ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000a60000-0000000000a7ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000a80000-0000000000a9cfff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000a9d000-0000000000a9ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000aa0000-0000000000b9afff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000b9b000-0000000000b9dfff 0x0104/0x0004 0x0020000
284c.3ce4:   0000000000b9e000-0000000000b9ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000ba0000-0000000000ba3fff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000ba4000-0000000000baffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000bb0000-0000000000bb1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000bb2000-0000000000bfffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000c00000-0000000000ccefff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000ccf000-0000000000cd1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000cd2000-0000000000dfffff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000e00000-000000007ffdffff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe4000-00007ff55706ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557070000-00007ff557070fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff557071000-00007ff55707ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557080000-00007ff5570a2fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff5570a3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
284c.3ce4: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supR3HardNtChildPurify: Done after 566 ms and 0 fixes (loop #0).
284c.3ce4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000d00000 LB 0x400000)
255c.41c4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
255c.41c4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~0000000000b9f568)
284c.3ce4: supR3HardNtEnableThreadCreationEx:
255c.41c4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
255c.41c4: New simple heap: #1 0000000000f00000 LB 0x400000 (for 2052096 allocation)
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: System32:  \Device\HarddiskVolume4\Windows\System32
255c.41c4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
255c.41c4: KnownDllPath: C:\WINDOWS\System32
255c.41c4: supR3HardenedVmProcessInit: Opening vboxdrv...
255c.41c4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
255c.41c4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
255c.41c4: Registered Dll notification callback with NTDLL.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
255c.41c4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 125 ms.
255c.41c4: \SystemRoot\System32\ntdll.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:24.962297600Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1eeb38
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x1f5000 (2052096)
255c.41c4:     Resource Dir:    0x184000 LB 0x6fff8
255c.41c4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1682
255c.41c4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
255c.41c4:     FileDescription: NT Layer DLL
255c.41c4: \SystemRoot\System32\kernel32.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:16.157371700Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0xbb058
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0xbd000 (774144)
255c.41c4:     Resource Dir:    0xbb000 LB 0x520
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\KernelBase.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:25.904947200Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x2cf640
255c.41c4:     NT Headers:      0xf0
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x2cd000 (2936832)
255c.41c4:     Resource Dir:    0x2a4000 LB 0x548
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\apisetschema.dll:
255c.41c4:     CreationTime:    2019-12-07T09:08:13.518339400Z
255c.41c4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
255c.41c4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1f538
255c.41c4:     NT Headers:      0xd0
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x20000 (131072)
255c.41c4:     Resource Dir:    0x1f000 LB 0x408
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1
255c.41c4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
255c.41c4:     FileDescription: ApiSet Schema DLL
255c.41c4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
255c.41c4: supR3HardenedWinFindAdversaries: 0x800
255c.41c4: \SystemRoot\System32\drivers\cfrmd.sys:
255c.41c4:     CreationTime:    2014-06-26T05:33:42.000000000Z
255c.41c4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
255c.41c4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x9d20
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Image Version:   6.1
255c.41c4:     SizeOfImage:     0xe000 (57344)
255c.41c4:     Resource Dir:    0xc000 LB 0x3e0
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Windows (R) Win 7 DDK driver
255c.41c4:     ProductVersion:  6.1.7600.16385
255c.41c4:     FileVersion:     6.1.7600.16385 built by: WinDDK
255c.41c4:     FileDescription: Safe Deletion Driver
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: Calling main()
255c.41c4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
255c.41c4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: SUPR3HardenedMain: Final process, opening VBoxDrv...
255c.41c4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000f00000 LB 0x400000)
255c.41c4: supR3HardNtEnableThreadCreationEx:
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll: Signature #1/2: info status: 24202
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbdcfb0000 LB 0x00005000 C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\wintrust.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\wintrust.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume4\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msvcrt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msvcrt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe26a0000 LB 0x0009e000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2510000 LB 0x00068000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c70000 LB 0x00100000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ucrtbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ucrtbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1d70000 LB 0x00156000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\crypt32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\crypt32.dll
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-localization-l1-2-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-localization-l1-2-1'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msasn1.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msasn1.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1830000 LB 0x00012000 C:\WINDOWS\SYSTEM32\MSASN1.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\system32\Wintrust.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcrypt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcrypt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcrypt.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c40000 LB 0x00027000 C:\WINDOWS\System32\bcrypt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1c40000 'C:\WINDOWS\system32\bcrypt.dll'
255c.41c4: bcrypt.dll loaded at 00007ffbe1c40000, BCryptOpenAlgorithmProvider at 00007ffbe1c451e0, preloading providers:
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcryptprimitives.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe23e0000 LB 0x00082000 C:\WINDOWS\System32\bcryptprimitives.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe23e0000 'C:\WINDOWS\system32\bcryptprimitives.dll'
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD2',0,0) -> 0x0 (hAlgo=00000000014417e0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD4',0,0) -> 0x0 (hAlgo=0000000001441e60)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD5',0,0) -> 0x0 (hAlgo=0000000001442180)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA1',0,0) -> 0x0 (hAlgo=00000000014434b0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA256',0,0) -> 0x0 (hAlgo=00000000014437d0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA512',0,0) -> 0x0 (hAlgo=0000000001443af0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'RSA',0,0) -> 0x0 (hAlgo=0000000001443e10)
255c.41c4:     BCryptOpenAlgorithmProvider(,'DSA',0,0) -> 0x0 (hAlgo=0000000001444130)
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptsp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptsp.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe15f0000 LB 0x00018000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rsaenh.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rsaenh.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume4\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0cb0000 LB 0x00034000 C:\WINDOWS\system32\rsaenh.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1610000 LB 0x0000c000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptbase.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\kernel32.dll'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\WINTRUST.DLL (Input=WINTRUST.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\System32\WINTRUST.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\CRYPT32.dll (rcNtResolve=0xc0150008) *pfFlags=0x2 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1d70000 'C:\WINDOWS\System32\CRYPT32.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe4280000 LB 0x0001d000 C:\WINDOWS\System32\imagehlp.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\imagehlp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\imagehlp.dll
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\gpapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\gpapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0510000 LB 0x00023000 C:\WINDOWS\SYSTEM32\gpapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\gpapi.dll [lacks WinVerifyTrust]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\profapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\profapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1b80000 LB 0x0001f000 C:\WINDOWS\SYSTEM32\profapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\profapi.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'crypt32.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptnet.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptnet.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume4\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWin",Murdoch
17345,"Display showing at 1/4 size, mouse input area normal (Windows host / Linux guest)",Windows,VirtualBox 5.2.0,2017-12-04T23:01:51Z,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
20967,"Sometimes mouse works only in part of the screen, 6.1.34 with Ubuntu 22.04 guest",Windows,VirtualBox 6.1.34,2022-06-03T14:52:12Z,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
20963,Window decorations do not scale correctly when moved across monitors,Windows,VirtualBox 6.1.34,2022-05-31T21:25:43Z,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
20955,Debian Jessie not booting on VBox 6.0.24,Windows,,2022-05-23T11:15:00Z,2022-05-23T16:45:03Z,2022-05-23T16:45:03Z,"Hello,

Recently downloaded VirtualBox under Windows, and I'm struggling to run Debian 8.11.1 ('''Jessie''') as my ''guest'' OS.

At the moment, I've tried to boot it from a ''DVD'' iso (after successful installation), but as soon as it's meant to login the screen prompts a message like ""Something went wrong, and the system can't recover""...

I've read this might be due to VBox graphical settings, and that a VBoxSVGA controller was suggested in place of VMSVGA.

Almost nothing changed by enabling or disabling 3D acceleration...

Please, can you help?

Mine was the first installer from here: [https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-dvd/]

Thanks",Antonin
20946,No audio Pop!OS 22.04 guest / Virtualbox 6.1.34,Windows,VirtualBox 6.1.34,2022-05-18T07:22:07Z,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
20945,Corner dragging second dual monitor screen causes monitor close without warning,Windows,VirtualBox 6.1.32,2022-05-17T00:46:57Z,2022-05-17T00:46:57Z,2022-05-17T00:46:57Z,"Using the cursor and left clicking the double arrow to expand/contract monitor 2 will cause the monitor to suddenly close with no warning.

You have to go back to the View menu and click on ""Enable"" Virtual Screen 2 to reopen it.

Using Minimize/Maximize buttons on Virtual Screen work as normal.  The sudden close only happens when dragging the corner to resize it.

System: Unbuntu 20.4
Virtual Box: Oracle VM Virtual Box 6.1
    In VBox Settings assigned Video settings 40MB


It's a minor issue, just thought engineering might want to know it exists, should be duplicable.",Tony C
20943,Latest Win 11 updates causing total fault of Virtualbox ver.6.1.34,Windows,VirtualBox 6.1.34,2022-05-15T06:06:30Z,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
20921,After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work,Windows,VirtualBox 6.1.32,2022-04-29T17:53:51Z,2022-04-30T19:42:55Z,2022-04-30T19:42:55Z,"After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work

See please video: https://drive.google.com/file/d/1C0IOJlqY-n71PDoVgYfVfrsuHKaUMnvD/view?usp=sharing",Ilia Poliakov
20880,No Sound,Windows,VirtualBox 6.1.32,2022-03-24T21:40:57Z,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
20911,Virtual box unable to start VM failing with error (rc=-5640),Windows,VirtualBox 6.1.32,2022-04-23T09:11:32Z,2022-04-23T09:11:32Z,2022-04-23T09:11:32Z,"(rc=-5640)
Please try reinstalling VirtualBox.
where: supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.",Prateek DA
20895,Better error messages when starting Linux image on Windows 11,Windows,VirtualBox 6.1.32,2022-04-10T20:03:41Z,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
20894,VirtualBox 6.1.30 & 6.1.32 VM terminated returning from hibernate,Windows,VirtualBox 6.1.32,2022-04-08T18:27:43Z,2022-04-08T18:27:43Z,2022-04-08T18:27:43Z,"Hello,

I have a Ubuntu VM on a Windows 10 Host on a laptop.
When returning from hibernate status while powered on battery, the VM cannot be resumed and a VirtualBox error window states a critical error has occurred and the VM must be terminated.

I get the same result with both VirtualBox 6.1.30 and 6.1.32.
VirtualBox log is only showing ""emR3Debug: rc=VERR_VMX_INVALID_VMXON_PTR"" as last info before the PC goes to hibernate state.
All rest of the log file does not exhibit any meaningful message.

Any help is very appreciated as I suspect more a VM setting issue than a bug but I am not certain and I do not know what kind of VM setting has to be tuned.

Thanks

Laurent",Laurentzed
18680,Create symbolic links in shared folders without administrator priviledges using new Windows 10 Developer Mode,Windows,VirtualBox 6.0.8,2019-05-29T13:27:20Z,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
20890,cannot run any linux VM on ThinkPad X1 Extreme gen 4 with Windows 11 host OS,Windows,VirtualBox 6.1.32,2022-03-31T15:06:13Z,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
20881,Guest additions on Linux(Artix) with dinit init system,Windows,VirtualBox 6.1.32,2022-03-25T13:35:55Z,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
20868,Automated login not working on Arch Linux guest of a Windows host,Windows,VirtualBox 6.1.32,2022-03-14T16:14:42Z,2022-03-14T16:14:42Z,2022-03-14T16:14:42Z,"I followed instructions in https://www.virtualbox.org/manual/ch09.html#autologon
to be able to login automatically on my Arch Linux host under a Windows 10 host, providing credentials as explained for Windows guests (not described for Linux guests), which shows in syslog on the Linux guest as ...
{{{
pam_vbox_setcred called, iFlags=0x4
pam_vbox_setcred: argv[0] = debug
}}}
but pam_vbox is unable to subsequently retrieve the credentials leaving the following error in syslog:
{{{
pam_vbox: 6.1.32r149290, running on amd64
pam_vbox_init: runtime initialized
pam_vbox_init: guest lib initialized
pam_vbox_init: rhost=<none>, tty=:0, prompt=<none>
her	dbus-daemon[2156]: Successfully activated service 'org.a11y.atspi.Registry'
her	SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait""=""1""
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait"" with rc=VINF_SUCCESS
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWaitTimeout"" with rc=VERR_NOT_FOUND
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsMsgWaiting"" with rc=VERR_NOT_FOUND
Showing message ""Waiting for credentials ..."" (type 4)
pam_vbox_check_creds: could not query for credentials! rc=VERR_PERMISSION_DENIED. Aborting
pam_vbox_authenticate: overall result rc=VERR_PERMISSION_DENIED
}}}
",MAnantharaman
20867,Kernel modules not re-built on updating guest additions on Linux,Windows,VirtualBox 6.1.32,2022-03-14T15:49:43Z,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
20474,[vmwgfx]] *ERROR* Failed to open channel,Windows,VirtualBox 6.1.24,2021-07-24T10:35:44Z,2022-03-06T08:22:30Z,2022-03-06T08:22:30Z,"I am running VirtualBox 6.1.24 on Win10 x64, Hyper-V is paravirtualization interface. Ubuntu 20.04 is guest OS.VM is configured to use VMSVGA with 3D enabled.

During boot up, dmesg log has many following records:

[  107.916494] 10:21:10.493550 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
               10:21:10.493575 main     Log opened 2021-07-24T10:21:10.493522000Z
[  107.916494] 10:21:10.493713 main     OS Product: Linux
[  107.916494] 10:21:10.493841 main     OS Release: 5.8.0-63-generic
[  107.916494] 10:21:10.493933 main     OS Version: #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021
[  107.916494] 10:21:10.494012 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
               10:21:10.494034 main     Process ID: 1337
               10:21:10.494057 main     Package type: LINUX_64BITS_GENERIC
[  107.920318] 10:21:10.501490 main     6.1.24 r145751 started. Verbose level = 0
[  107.927561] 10:21:10.508214 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  133.960208] rfkill: input handler disabled
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  174.892246] rfkill: input handler enabled
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.


Detailed logs are attached.",tysonite
20835,I cannot do normal start it only start as uncoupled start,Windows,VirtualBox 6.1.30,2022-02-21T06:45:18Z,2022-02-21T21:56:18Z,2022-02-21T21:56:18Z,"The virtual machine 'android32bvb_7_1_int11' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\Virtual Machines\android32bvb_7_1_int11\Logs\VBoxHardening.log'.


Código resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
",Jose Nunez
20833,Linux Guest VM Crashes If Bridged Network Is Selected,Windows,VirtualBox 6.1.32,2022-02-18T04:15:58Z,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
19588,Crash - referenced memory at 0x0000000000000000,Windows,VirtualBox 6.1.6,2020-05-15T16:29:56Z,2022-02-14T21:08:06Z,2022-02-14T21:08:06Z,"Host: Windows 10, 1803

Guest: Linux Mint, 18.3 Cinnamon 64-bit, 3.6.7

Guest Browser: Pale Moon, 28.9.3 (64-bit)

Web Site: 'https://coronavirus.jhu.edu/map.html'

Crash: ""VirtualBoxVM.exe - Application Error""

""The instruction at 0x00007FFA7B9075AD referenced memory at 0x0000000000000000. The memory could not be read.""

Status: Hard, reproducible.

Attached: C:\VMs\Mint18\Mint18-2020-05-15-12-12-36.log
",Mark Filipak
20825,copy/paste failure from Win 10 host to Linux guest with VirtualBox 6.1.32,Windows,VirtualBox 6.1.32,2022-02-13T04:08:02Z,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
20814,Upgrade from 6.1.3 to 6.1.32 causes VT-x detection to fail,Windows,VirtualBox 6.1.32,2022-02-07T15:03:39Z,2022-02-07T15:03:39Z,2022-02-07T15:03:39Z,"I have virtualbox running on windows 10

I have a VM that requires nested virtualization.

It ran fine under 6.1.30 but since upgrading to 6.1.32 it fails saying:

not in hypervisor partition
VT-x is disabled in the BIOS for all CPU modes

Downgrade to 6.1.30 cured the problem
I have replicated the symptoms on two different devices:

Intel Core i3-2350M 2.3GHz running Windows 10 Pro 21H2
Intel core i3-2370M 2.4 GHz Running Windows 10 Pro 21H2

",Pcrossley
17563,Drag and Drop does not work: Host Windows 10 and guest Linux XUbuntu 14.04,Windows,VirtualBox 5.2.6,2018-02-23T14:08:34Z,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
18563,Drag and drop fails from guest to host,Windows,VirtualBox 6.0.4,2019-04-16T19:56:48Z,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
19851,Drag and Drop not working: VERR_ACCESS_DENIED,Windows,VirtualBox 6.1.10,2020-09-03T07:29:18Z,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
20810,Can't use gpu to increase vram,Windows,VirtualBox 6.1.32,2022-02-04T09:38:45Z,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
20803,Using Greenshot for screenshot management on Host crash VirtualBox,Windows,VirtualBox 6.1.32,2022-02-01T19:09:35Z,2022-02-01T19:13:32Z,2022-02-01T19:13:32Z,"Hello,

I use greenshot on my computer and also open Virtualbox with an Ubuntu Guest

I launch virtual box and my guest is running.

I use Greenshot to do a screenshot and open in image editor

I go on the greenshot software and copy the image to the clickboard button

Then my virtualbox software is killed When I copy this 
Environment

I use 

Windows 10 

Greenshot 1.2.10 Build 6

Virtualbox 6.1.32 r149290

Greenshot support is saying :
https://greenshot.atlassian.net/browse/BUG-2892
Greenshot places an image to the clipboard, which to our knowledge is according to the specifications from Microsoft itself.
",Greggreg
20782,VirtualBox revert to invalid options automatically,Windows,VirtualBox 6.1.28,2022-01-20T14:46:50Z,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
20779,drm:vmw_host_printf [vmwgfx]] *ERROR* in version 6.1.30 & 6.1.32,Windows,VirtualBox 6.1.32,2022-01-20T05:44:09Z,2022-01-20T08:26:05Z,2022-01-20T08:26:05Z,"CentOS 9 Stream VM provisioned with *.vdi|*.vhd|*.vmdk disk and dynamically allocated capacity of 100GB configurations gives the 'drm:vmw_host_printf [vmwgfx]] *ERROR* Failed to send host log message' after OS post installation boot. 

Included are screenshots of the error, device configurations and the host Windows OS configurations occurring on two workstations. A provisioned VM with a *.vdi|*.vhd|*.vmdk disk capacity of 45.6GB dynamically allocated encountered no issues with the post-install boot with the same CentOS 9 Stream OS.

Supporting images are attached. Please let me know if additional technical information about the issue is needed.",BrownFoxx
20650,host-only network is not working on windows 10 pro with 6.1.28,Windows,VirtualBox 6.1.28,2021-11-05T15:24:45Z,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
15438,Guest can't access host network after resume from hibernation (hybrid sleep).,Windows,VirtualBox 5.0.20,2016-05-23T13:05:56Z,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
19154,Using VMSVGA crashes VirtualBoxVM.exe,Windows,VirtualBox 6.1.0,2019-12-13T12:05:50Z,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
20760,Slow performance since last update,Windows,VirtualBox 6.1.30,2022-01-06T03:47:51Z,2022-01-06T03:47:51Z,2022-01-06T03:47:51Z,"update to windows 11 slowed things down and since the las vbox update, my VM are unusable

extreme slow speed (response,Latency,Loading)
CPU usage is high for no apparent reason (Firefox use 60% CPU (8cores)

crashes

ive installed vmware to test if it was due to windows 11 but vmware work like vbox when no probleme were existing",dparadis
20756,"Picture falling apart until lock up with Wayland, 3D, VMSVGA and Linux guest",Windows,VirtualBox 6.1.30,2022-01-01T19:13:40Z,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
20757,CANT START ENGINE,Windows,VirtualBox 6.1.30,2022-01-02T18:43:10Z,2022-01-02T18:44:28Z,2022-01-02T18:44:28Z,"I cannot start it or attach linux installation to apps. i researched everything, but i've found nothing...plz help me",BABBA BOI
20749,High cpu usage in guest on several cores causes severe host lagging.,Windows,VirtualBox 6.1.30,2021-12-24T18:55:56Z,2021-12-24T21:58:52Z,2021-12-24T21:58:52Z,"I have AMD Ryzen 3 3100 4-Core Processor hyperthreaded.
When I run atlas simulation job from lhc@home on virtualbox with 4 cores 
system starts to lag.",kotenok2000
20748,6.1.30.148432 Install Results in Extract Path Error,Windows,VirtualBox 6.1.30,2021-12-24T15:23:19Z,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
20237,BridgedInterface needs trailing blank,Windows,VirtualBox 6.1.18,2021-03-06T18:41:27Z,2021-12-22T03:54:56Z,2021-12-22T03:54:56Z,"My network interface card is a ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", host is Windows 10 20H2 build 19042.844. 
When selecting the NIC as bridged interface in the network settings, it is stored to the .vbox file as ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", however when starting the related guest I get an error message that the virtual machine cannot be started as the network interface is not existing.
I can resolve this by adding a trailing blank to the BridgedInterface in the .vbox file as:
<BridgedInterface name=""NVIDIA nForce 10/100/1000 Mbps Ethernet ""/>
before starting VirtualBox.
But whenever I change some settings of the guest, the trailing blank is removed, so I must do this again and again. ",Phantom2398
20737,after using save the machine state vm virtual box is not asking for login for next time,Windows,VirtualBox 6.1.30,2021-12-19T07:09:26Z,2021-12-19T07:09:26Z,2021-12-19T07:09:26Z,"hello,
i am using Virtual Box 6.1.30 and i am running kali linux in vm my main os or host machine is windows 11 
bug is that when i am selecting 'save the machine state'  before terminating the instance and after closing that machine when i start that machine again it's not asking for login credentials user and password
it's allowing to directly use that machine without login credentials the logged in user is the same before saving the machine state.
 
",AFTAB SAMA
20724,VB crashed after a while on company computer,Windows,VirtualBox 6.1.26,2021-12-14T13:21:57Z,2021-12-14T13:21:57Z,2021-12-14T13:21:57Z,"Every time I try to launch my VM with Ubuntu, it's crashes after couple of seconds (sometimes after couples of minutes).
This problem is caused by my company's computer setup. When my administrator has temporarily disabled some Credential Guard, my virtual machine works great.",stefek
20716,Impossible to use VirtualBox Guest Addition on Linux Preempt RT Kernel,Windows,VirtualBox 6.1.30,2021-12-07T11:30:59Z,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
20685,Ubuntu VM crash,Windows,VirtualBox 6.1.28,2021-11-23T09:05:01Z,2021-11-23T13:57:48Z,2021-11-23T13:57:48Z,My Ubuntu VM crashed for an unknown reason,mediawiz
20672,During the execution of the docker pull command the VM dies,Windows,VirtualBox 6.1.28,2021-11-17T15:23:26Z,2021-11-18T19:23:27Z,2021-11-18T19:23:27Z,"I have a VM installed with the operating system Ubuntu 20.04 LTS .
Running the command docker pull from the docker registry of AWS the virtual machine dies ",GriGiu
20651,Internal Microphone is not detected/doesn't work on Linux - Ubuntu,Windows,VirtualBox 6.1.28,2021-11-05T15:56:34Z,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
20382,Unable to create a HostOnly network on Windows 10 NetCfgInstanceId failed,Windows,VirtualBox 6.1.22,2021-05-28T18:29:05Z,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
20293,"Message Linux Mint 20.1 Cinnamon - ""Check your Video Drivers""",Windows,VirtualBox 6.1.18,2021-04-08T13:40:18Z,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
20634,No sound with pipewire after updating fedora 34 guest system,Windows,VirtualBox 6.1.28,2021-10-25T09:21:35Z,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
20619,Failed to Restore VM,Windows,VirtualBox 6.1.26,2021-10-19T20:03:53Z,2021-10-19T20:06:26Z,2021-10-19T20:06:26Z,I am restoring the Virtual Machine and it stops completely.,desteves
20617,Audio. Sound doesn't work in fedora live-cd with intel hd audio controller selected,Windows,VirtualBox 6.1.26,2021-10-17T18:12:10Z,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
20614,No Audio output/passthrough from Linux Guest to Windows Host,Windows,VirtualBox 6.1.26,2021-10-16T17:30:37Z,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
20574,VBoxManage 'start --type headless' cannot be correctly closed by 'controlvm acpipowerbutton',Windows,VirtualBox 6.1.26,2021-09-25T09:05:30Z,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
20589,"NAT TFTP: leading slash in path cause ""Access violation""",Windows,VirtualBox 6.1.26,2021-10-01T18:22:50Z,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
20588,Guest OS startup crashes the VM,Windows,VirtualBox 6.1.26,2021-10-01T17:44:38Z,2021-10-01T17:44:38Z,2021-10-01T17:44:38Z,"When I trying to start VM with RHEL7 it no longer can startup.
It crashing into ""Guru mediation"".
",xor2003
20553,VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension,Windows,VirtualBox 6.1.26,2021-09-17T01:25:08Z,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
20405,Virtual Machine crashes when dragging link,Windows,VirtualBox 6.1.22,2021-06-15T15:40:57Z,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
20483,"Virtubox crashes when the vbox window was resized. Host Windows 10 Pro (64-bit), guest Debian GNU/Linux",Windows,VirtualBox 6.1.22,2021-08-01T04:30:39Z,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
20540,E_FAIL (0x80004005) after Launch,Windows,VirtualBox 6.1.26,2021-09-08T07:35:16Z,2021-09-16T09:34:36Z,2021-09-16T09:34:36Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
14374,Network adapters not working after host returns from sleep Win 7 host Linux Mint 17.2 guest,Windows,VirtualBox 5.0.0,2015-08-02T17:02:25Z,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
20535,"W64 host, Ubuntu guest: mouse cursor corrupt in Terminal on secondary 4K screen",Windows,VirtualBox 6.1.26,2021-09-06T11:45:41Z,2021-09-08T09:41:15Z,2021-09-08T09:41:15Z,"System details at the end.

Whether the VB container window is sized very small or large, there is a glitch with the mouse cursor inside Terminal windows in the guest OS.

Note that there are two 4K monitors attached. **This bug only appears if the VB container window is on one of the secondary monitors.** If it is on the laptop's main screen, the cursor simply disappears when typing, which I believe is the desired behaviour.

The specific issue is as follows: once the mouse cursor is moved inside the Terminal window, it is at first correct. However, type as much as one character, and it turns into a block of glitched data, 8-10 characters wide and one character tall. If the cursor is moved even a tiny amount, it returns to normal, until the user types once again.

I've attached images of the before and after effects within a small VB container window.

It appears that when the cursor is being removed, the underlying pixels are being bitblt'ed from the wrong part of video memory.

**System details**

VB 6.1.26 build 145957 (Qt5.6.2)

Host:
* Edition	Windows 10 Pro
* Version	20H2
* Installed on	‎06/‎07/‎2021
* OS build	19042.1165
* Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
* Ubuntu 64 bit Hirsute, all patches current
* VM Additions installed.

PC:
* Processor	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz   2.71 GHz
* Installed RAM	8.00 GB (7.88 GB usable)
System type	64-bit operating system, x64-based processor

Config:
* HP EliteBook 840 G4
* 3 GiB RAM assigned to guest
* Main screen: 1080p inbuilt
* Secondary screens:
 * 2x 28"" 4K
 * full resolution
 * 125% scaling
 * both connected using DisplayPort.",JonAtFS
20539,E_FAIL (0x80004005) after Launch,Windows,VirtualBox 6.1.26,2021-09-08T07:35:16Z,2021-09-08T07:35:16Z,2021-09-08T07:35:16Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
20390,Guest hung after host resumes from sleep,Windows,VirtualBox 6.1.22,2021-06-07T23:17:24Z,2021-09-08T00:32:39Z,2021-09-08T00:32:39Z,"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

When I suspend and resume the host, the guest is no longer responsive, requires a forced power off and complete restart of the guest.  Similar to 20270, but the trick of pausing and resuming doesn't work.

Used to work fine, I suspect it started with a host OS update.  Happened under 6.1.17 too.

Logs attached.",gkcgareth
20537,Guest process stops responding when host suspends and guest is running a docker container,Windows,VirtualBox 6.1.26,2021-09-08T00:25:25Z,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
20457,Guest crashes when unpausing,Windows,VirtualBox 6.1.22,2021-07-13T21:16:15Z,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
20467,Guest freeze after restoring from saved state,Windows,VirtualBox 6.1.24,2021-07-21T21:20:46Z,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
20533,Network card error after deleting Virtual Machine,Windows,VirtualBox 6.1.26,2021-09-03T10:51:19Z,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
20528,3d acceleration with VMSVGA sometimes leads to a crash or a hang of VirtualBox,Windows,VirtualBox 6.1.26,2021-08-30T20:40:34Z,2021-08-30T20:40:34Z,2021-08-30T20:40:34Z,"When using a Linux VM (debian 9/10) and Windows host with VMSVGA video adapter and 3d acceleration, the VM sometimes might crash or hang. The crash/hang happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

When the crash occurs, the error message is ""The instruction at .... referenced memory at 0x0000000000000010...""

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox ""Use hardware acceleration when available"" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser (sometimes the crash only happens when closing the browser).

Attached are 2 logs: one with a crash with Chromium 90 and another one with a hang with Chromium 83. The hang has happened when the ""accept cookies"" window from zoom.us was loading: it turned out to be completely corrupted and the VM hang occurred. The error in the log is VMSVGA related but is different to what I see in case of a crash. In the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

This problem was first reported in https://www.virtualbox.org/ticket/19154. 
I did more tests today trying to reproduce the problem using Nvidia GPU, but couldn't. Today I also couldn't reproduce the problem using Intel GPU and exactly the same setup as I was using previously. So the problem is not 100% reproducible, unfortunately (until today I could reproduce it all the time - ~20-30 times or so). If I see the problem again, I will do tests with NVidia and will update the ticket.",Mikhail Kovalev
20522,hang on windows after update notifier window pops up,Windows,VirtualBox 6.1.22,2021-08-23T15:54:51Z,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
8311,SATA AHCI Errors: READ FPDMA QUEUED,Windows,VirtualBox 4.0.2,2011-02-09T15:53:00Z,2021-08-23T04:41:22Z,2021-08-23T04:41:22Z,"My guest OS hangs periodically with a harddrive command error followed by an attempt to reset the HD (reproduced with Ubuntu and !ArcLinux). This issue does not occur in the host OS (Windows 7), only in the Guest OS.

Environment:

 * Ubuntu running in a Virtual Box 4.0.2 running on Windows 7 64bit.
 * Asus G53JW Laptop
 * Intel X25 SSD HD

Log excerpts:
{{{
Jan 17 14:48:32 vm kernel: [ 1513.120252] ata3: hard resetting link
Jan 17 14:48:33 vm kernel: [ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus
123 SControl 300)
Jan 17 14:48:33 vm kernel: [ 1513.471232] ata3.00: configured for UDMA/133
Jan 17 14:48:33 vm kernel: [ 1513.471241] ata3.00: device reported invalid CHS
sector 0
Jan 17 14:48:33 vm kernel: [ 1513.471255] ata3: EH complete
}}}
{{{
[ 1513.120200] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 1513.120210] ata3.00: failed command: READ FPDMA QUEUED
[ 1513.120222] ata3.00: cmd 60/08:00:30:66:4c/00:00:00:00:00/40 tag 0 ncq 4096
in
[ 1513.120224]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 1513.120230] ata3.00: status: { DRDY }
[ 1513.120252] ata3: hard resetting link
[ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1513.471232] ata3.00: configured for UDMA/133
[ 1513.471241] ata3.00: device reported invalid CHS sector 0
[ 1513.471255] ata3: EH complete
}}}",andornaut
20519,ubuntu isn't booting right,Windows,VirtualBox 6.1.26,2021-08-22T14:10:38Z,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
20517,Unable to connect 2TB seagate external USB drives to RHEL7 Guest,Windows,VirtualBox 6.1.26,2021-08-21T23:06:43Z,2021-08-21T23:06:43Z,2021-08-21T23:06:43Z,"Hi Team, 
I'm having issues connecting multiple different 1.7 TB seagate external USB drives to my RHEL7 guest vms. 

The error and a drive properties view from windows is attached for your review. 

Also, I can attach a 1TB external drive just fine, so I'm thinking that it's a driver compatibility issue with the larger drives that's the problem? 

Thanks!",hanch0
19302,Mouse support fails,Windows,VirtualBox 6.0.16,2020-02-12T13:48:54Z,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
15271,"USB mouse ""dies"" - pointer still moving but no function",Windows,VirtualBox 5.0.16,2016-03-24T11:21:45Z,2021-08-13T05:38:52Z,2021-08-13T05:38:52Z,"I am using a kubuntu 15.10 64 bit guest on Windows 7 Enterprise SP 1 with Version 5.0.16 r105871.

About every day, the USB mouse kinda dies in the guest - it still works normal on the Windows host and the pointer still moves in the kubuntu guest, but focus follows mouse and clicks don't do anything any more. Keyboard and everything else still works fine.

Logging off from KDE and on again fixes the problem.

In the attached dmesg, there is an issue with IRQ 22 and a stack trace which I am quite sure are related. The relevant VBox.log is also attached.",Torsten Römer
20492,Debian installer hangs: BUG: unable to handle kernel NULL pointer dereference at 00000004,Windows,VirtualBox 6.1.26,2021-08-06T22:14:39Z,2021-08-06T22:14:39Z,2021-08-06T22:14:39Z,"I'm trying to install Debian 10 i386 on a Windows 10 (64-bit) host but the installer hangs during ""Select and install software"", specifically ""Configuring man-db (i386)"". Do not modify the default software selection (Debian desktop, print server and standard system utilities). It happens every time, both in the graphical and the non-graphical installer. I'm running an AMD Ryzen 7 3800X and AMD-V appears to be enabled.

This is logged by the kernel once the system hangs:
{{{
[  401.003262] BUG: unable to handle kernel NULL pointer dereference at 00000004
[  401.003775] *pde = 00000000 
[  401.003978] Oops: 0002 [#1] SMP
[  401.004197] CPU: 0 PID: 21003 Comm: mandb Not tainted 4.19.0-17-686 #1 Debian 4.19.194-1
[  401.004767] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[  401.005336] EIP: _raw_spin_lock+0x14/0x30
[  401.005618] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.007152] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.007694] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: ee4efef4
[  401.008228] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.008863] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
[  401.009382] Call Trace:
[  401.009597]  speculation_ctrl_update+0x1aa/0x220
[  401.009976]  speculation_ctrl_update_current+0x18/0x20
[  401.010399]  task_update_spec_tif+0x25/0x30
[  401.010745]  ssb_prctl_set.part.1+0x1d/0x30
[  401.011091]  arch_seccomp_spec_mitigate+0x45/0x50
[  401.011488]  do_seccomp+0x5b0/0x5f0
[  401.011776]  sys_seccomp+0x16/0x20
[  401.012059]  do_fast_syscall_32+0x81/0x1a0
[  401.012400]  entry_SYSENTER_32+0x68/0xbb
[  401.012848] EIP: 0xb7efdd31
[  401.013188] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
[  401.015419] EAX: ffffffda EBX: 00000001 ECX: 00000000 EDX: 0162db20
[  401.016174] ESI: 015b5352 EDI: b7eded4d EBP: b7c7dde9 ESP: bfdab85c
[  401.016929] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
[  401.017753] Modules linked in: fuse battery dm_mod md_mod xfs jfs btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c vfat fat ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb e1000 nls_utf8 isofs usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ohci_pci ehci_pci ohci_hcd ehci_hcd ata_piix snd_intel8x0 snd_ac97_codec ahci libahci ac97_bus evdev libata psmouse snd_pcm snd_timer usbcore usb_common snd soundcore scsi_mod
[  401.022503] CR2: 0000000000000004
[  401.022903] ---[ end trace 8693d9353e91b6c4 ]---
[  401.023448] EIP: _raw_spin_lock+0x14/0x30
[  401.023933] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.026189] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.026947] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: dca193bc
[  401.027704] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.028492] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
}}}

I've attached the full kernel log, as well as the VirtualBox log on the host.",joelpuig
20481,Working VM suddenly stop loading in GUI mode (F7) but working  in tty1 to tty6 mode,Windows,VirtualBox 6.1.24,2021-07-31T13:40:58Z,2021-08-02T12:33:23Z,2021-08-02T12:33:23Z,"Hi,
I ahve few(3) VMS based out of ubuntu 18.04(bionic) which were all functional from at least a year now. But yesterday, one of the 3 VM stops booting up in GUI mode(F7). It ends up ina blinking curson on the screen.
I can login into machine from tty1,ty2 to tty6 '''but not  getting anything on tty7 but a blinking cursor only'''.

Attaching vbox logs for someone to take a look urgently.

Note: I have checked some existing issues:
1. My host(windows 10) hypervisor is disabled.
2. I can  successfully run other 2 VMs
3. My VM has sufficient RAM/Space(from df and free output)
4. Virtualisation is enabled in BIOS settings.
5. Uptodate Vbox version and extension pack.
6. Done apt-get update  from tty1 and rebooted multiple times.
7. 3D acceleration is in disabled mode.

Please check my logs attached. ",vas
20478,Virtualbox locks up badly with fstrim on CentOS 8,Windows,VirtualBox 6.1.24,2021-07-28T16:57:33Z,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
19314,Copy & paste patially broken in 6.1.2,Windows,VirtualBox 6.1.2,2020-02-14T18:26:19Z,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
8761,Silent failure to delete files on Shared Folders,Windows,VirtualBox 4.0.6,2011-04-21T22:50:42Z,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)
20464,Virtualbox 6.1.22 crashes on windows 10 host,Windows,VirtualBox 6.1.22,2021-07-20T02:50:25Z,2021-07-20T02:50:25Z,2021-07-20T02:50:25Z,"My virtual box crashes after booting as well as after hibernation. It works fine after the first crash, but it surely crashes for the first time. I am using Virtualbox version 6.1.22, my host machine is Windows 10 and the guest machine is Kali.
",jishu
20381,6.1.22 hangs perhaps due to vmsvga/video,Windows,VirtualBox 6.1.22,2021-05-27T07:24:51Z,2021-07-12T16:38:43Z,2021-07-12T16:38:43Z,"I had to downgrade to 6.1.20, which was stable for me.

I suspect it has something to do with video/vmsvga

Machine: HP Envy Pavilion 17t-j186nr 
Host is windows-10 updated to 19043.985 21H1
Guest is Fedora-Workstation-34 kernel 5.12.6-300, guest additions 6.1.22 is installed

With 6.1.22, If machine is started as hidden, machine can be ssh-ed to and is stable for very long time.

With 6.1.22, If machine is made to be shown, then after GDM login, after starting a terminal app, wezterm, firefox, virtualbox freezes, becomes non-responsive and remains stuck. 

It is possible to get mouse cursor, which in stcuk state is invisible, to the bottom, to hover over and bring up the VM-menu, minimize it and then get to the windows host. Other menu commands like reset do not work.

Outside, in the host windows, taskmgr can be used to kill and Virtualbox processes, helps close all virtualbox windows, and start over. 

reinstall of 6.1.22 did not help
",gkamathh
20393,Linux Guest [vmwgfx] *ERROR* SVGA device lockup,Windows,VirtualBox 6.1.18,2021-06-10T19:29:19Z,2021-07-12T16:35:51Z,2021-07-12T16:35:51Z,"Hi,

I'm running a Linux guest on a Windows host and every so often the display will lock up. It's happened maybe 3 times in the last month and I haven't been able to correlate it with anything specific.

By lock up, I mean that it appears that the display stops updating. Input (at least mouse events) appear to work, but when it starts to lock-up, the display does not update in response to any input events until a few seconds go by. Pretty quickly, this behavior degrades to the point where it appears completely frozen and no more updates occur.

I can ssh in from my host and interact, so it seems it is just a display driver issue. dmesg shows the following:

[70545.554435] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70548.553727] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70558.765785] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out
[73420.314255] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73423.314445] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73433.384206] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out

Not sure what else to check, but can do whatever is needed to debug next time it happens. Just let me know.

I also see these messages appearing occasionally before hand, but they look to occur fairly regularly in the log without any other symptoms, so I don't know if they are related or not.

[54955.536381] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

I can provide more detailed hardware info (it's a Dell XPS 9500 using an i7-10857H w/ 32GB), os specifics (Win10, Ubuntu 20.04), and system config (I run 2 external displays on which I use my linux guest) or whatever else is needed.

I will attach my VBOX.log

Thanks for any help,
Brian

",brian-vbox
15827,Error message when starting VMs: Error In supR3HardenedWinReSpawn,Windows,VirtualBox 5.1.4,2016-08-19T13:34:14Z,2021-07-06T13:05:47Z,2021-07-06T13:05:47Z,"Almost everyday when I start my machine and run Vbox and try to start a vm, a msgbox appears with the following error:


{{{
VirtualBox - Error In supR3HardenedWinReSpawn
(rc=-5640)
Please try reinstalling VirtualBox.
where supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.
}}}

When I click ""ok"", another msgbox appears:

{{{
Failed to open a session for the virtual machine Ubuntu 16.04.

The virtual machine 'Ubuntu 16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jbassi\VirtualBox VMs\Ubuntu 16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

This has been happening for month, with current version, last version, tests versions, etc.
The reason I haven't reported this bug until now is because if I try again a few times (two or three) the VM starts up correctly. So I cannot reproduce everytime. In order to reproduce I need to restart the machine. The first time I try after a reboot almost always fails.

Version: Version 5.1.4 r110228 (Qt5.5.1)
Host: Windows 8.1 Enterprise
CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
",asdfafds
20022,VM is causing Guest OS applications ( Slack/Intelli J ) hung,Windows,VirtualBox 6.1.16,2020-11-06T05:43:17Z,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
20432,Cannot write to raw disk under Windows 10 21H1 guest in VBox 6.1.22,Windows,VirtualBox 6.1.22,2021-06-27T13:05:56Z,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
20400,Virtual Machine crashes when dragging link,Windows,VirtualBox 6.1.22,2021-06-15T15:35:49Z,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
20395,Centos 7 i386 causes serious malfunctions when booted with ncpus>1,Windows,VirtualBox 6.1.22,2021-06-11T10:34:08Z,2021-06-11T10:34:08Z,2021-06-11T10:34:08Z,"I had occasion to try testing something on CentOS 7 i386. So I fetched CentOS-7-i386-NetInstall-2009.iso, and tried booting it on my Win10 host running VB 6.1.22, and strange behavior ensued. So I tried a premade 7 2009 image, which did the same, and a premade 7 2003 image, which did either the same thing or aborted.

First, it flooded with BUG: Bad page state in process swapper. Then, after a bit, the strangest behavior ensued - it started pegging multiple cores on the host, attempting to do anything with the VM window or other VB windows became infeasible (I needed to use Task Manager to kill the VM ultimately, the times it didn't abort and crash on its own) and my Caps Lock light started oscillating furiously, which continues even if it ultimately gets into the graphical login screen.

Running with n=1 cores, it seems to work fine.

Since Debian buster i386 works fine on this host, it's not impossible for it to be a flaw in what CentOS 7 is doing, but if it works on real hardware, then not working in a VM still seems like a flaw in the VM?",rincebrain
20394,Settings issue,Windows,VirtualBox 6.1.22,2021-06-11T04:38:12Z,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
20391,"With Windows host,Bridged Adapter Oracle VirtualBox (6.1) doesn't work if the VM Opterating system is Ubuntu 16.04",Windows,VirtualBox 6.1.22,2021-06-09T22:57:39Z,2021-06-09T22:57:39Z,2021-06-09T22:57:39Z,"Here is an outline of the problem:

Parameters:
•	I’m using Windows 7
•	I’m using Oracle VirtualBox 6.1
•	I’m running Ubuntu 16.04 on Oracle VirtualBox VM’s

Outline of the Problem:

•	Can’t connect to the internet if I select “Bridged Adapter” in 
        the Networking Options of an Oracle VirtualBox VM.
•	Can connect to the Internet via the NAT Adapter.
•	When I try to communicate between Oracle VirtualBox VM’s via 
        the Bridged Adapter, I get the error message “Host not Found.
",intelidrift
20389,VBoxSharedClipboardClass-17032: VirtualBoxVM.exe - Application Error,Windows,VirtualBox 6.1.22,2021-06-07T23:10:51Z,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
19716,Total freeze VM after resume PC from sleep with multi-display,Windows,VirtualBox 6.1.10,2020-07-11T12:03:15Z,2021-06-05T22:35:10Z,2021-06-05T22:35:10Z,"I have notebook with additional display connected. After resume PC from sleep i have grayscaled VM (not resumed). After any manipulation (manual click to resume or power off) i have total freeze VM, any keys and menus do not work, I can stop it only from windows process manager. I see this bug only if I use additional display, and not always. Host - Windows 10 Pro. Guest - Ubuntu 20.04.

Last log messages:
{{{
19:20:59.444238 Pausing VM execution, reason 'host suspend'
19:20:59.445534 Changing the VM state from 'RUNNING' to 'SUSPENDING'
19:20:59.455506 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0781) created successfully
19:20:59.459381 AIOMgr: Async flushes not supported
19:20:59.460061 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0781) created successfully
19:21:00.435103 PDMR3Suspend: 988 580 745 ns run time
19:21:00.435115 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
19:21:00.435665 Console: Machine state changed to 'Paused'
19:21:01.289288 Audio: Device configuration of driver 'DSoundAudio' has changed
35:23:09.706882 Resuming VM execution, reason 'host resume'
35:23:09.706982 Changing the VM state from 'SUSPENDED' to 'RESUMING'
35:23:09.708188 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0723) created successfully
35:23:09.716841 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0723) created successfully
35:23:27.908281 GUI: UIMachineLogic: Host-screen count changed
35:23:28.567910 GUI: UIMachineLogic: Host-screen count changed
35:23:28.921678 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: 0x0 x 1920x1080
35:23:28.921702 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.971593 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 0x0 x 1920x1080
35:23:28.971614 GUI: UIMachineLogic: Host-screen available-area changed
35:23:28.972004 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: -1920x1072 x 1920x1080
35:23:28.972039 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.972572 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1080
35:23:28.972590 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.526775 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 3840x2130
35:23:33.526800 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.527365 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1050
35:23:33.527380 GUI: UIMachineLogic: Host-screen available-area changed
35:23:37.709638 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:41.938981 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:43.170192 GUI: Request for close-action to power VM off.
35:23:43.170209 GUI: Passing request to power VM off from machine-logic to UI session.
35:23:43.170453 GUI: Powering VM down on UI session power off request...
35:23:43.173091 Console: Machine state changed to 'Stopping'
35:23:43.174650 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
}}}

{{{
19:20:59.444238 - I sleep (or hibernate) PC.
35:23:09.706882 - Resume PC - VM is grayscaled, after any manipulation - total freeze.
}}}",PDZ
18594,Ubuntu 18.04 (guest) audio stops working (stuck) after Windows 10 (host) sleeps,Windows,VirtualBox 6.0.6,2019-04-23T11:32:33Z,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
20388,VM aborted while saving state,Windows,VirtualBox 6.1.22,2021-06-05T10:43:51Z,2021-06-05T10:43:51Z,2021-06-05T10:43:51Z,"I tried to save the state of the VM by selecting File → Close from the popup menu (invoked via a custom Host key shortcut) and, with the “Save state” radio button selected, pressing OK. At first, the VM seemed to save normally, but then the save process appeared to stop prematurely and the VirtualBox interface showed the VM state as “Aborted”.

This occurred after upgrading VirtualBox from 6.0.24 to 6.1.22. Before the incident, the VM had been running for several days and, if I recall correctly, was successfully saved and restored once, and also paused and resumed once.",mgrzegor
20385,VirtualBox crashes by accessing 0xFFFFFFFFFFFFFFFF when USB dongle is unplugged/plugged.,Windows,VirtualBox 6.1.22,2021-06-03T04:19:48Z,2021-06-03T04:29:34Z,2021-06-03T04:29:34Z,"I am using virtualbox 6.1.22: 6.1.22 r144080 (Qt5.6.2) to be exact.
Host is Windows 10 Pro 64-bit., 20H2, OS build is 19042.985
Guest is Debian GNU/Linux, 5.10.0-4-amd64 

I have a USB Wi-Fi dongle NEC Aterm WL300NU-AG adaptor.
This works fine under Windows 10.

I tried to use this dongle from within linux to test my Wi-Fi devices at home against fragattacks (recently found Wi-Fi vulnerability).
So I removed the driver under Windows 10 for this USB. 
(It is plugged and no messing from Windoes 10 itself without the driver, I suppose.)
I intend to use the dongle via the native linux driver.

Under guest linux, I could somehow make the dongle recognized initially,
and eventually was able to assign IP address to it (manually, not by DHCP) and ping the interface address from other PCs via Wi-Fi. 
So experimentally it works, but the device went off-line unexpectedly.
The driver seems to have a known issue.
In order to reset the device, I tried unplugging and plugging it a few times. 
Then VBox crashed saying it accessed 0xFFFFFFFFFFFFFFFF address. 
(Actually I did this a lot initially, but at that time VBox did not crash.)

Alright, I saved a log. (The experiment took a couple of hours).

Now, I rebooted the guest linux by restarting VBox and see if I can continue testing the dongle. Nope.
The device was not visible from within guest linux using lsusb anymore(?!).
So I tried unplugging and unplugging only a couple of times when I get the same address violation and VBox crashed. This time I got the capture on the screen to show the address. 

I think there is a problem with USB handling.
I am attaching the first log (crash that occurred after a couple of hours testing. Actually, it was at the tail end of a very long session.)
and the second log along with the screen dump.

",ci-zephyurus
20364,VirtualBox guest freezes when chaning host audio interfaces,Windows,VirtualBox 6.1.20,2021-05-13T17:27:47Z,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
20329,Connect bluetooth headset causes freeze,Windows,VirtualBox 6.1.18,2021-04-29T18:06:10Z,2021-04-29T18:06:10Z,2021-04-29T18:06:10Z,"Frequently, when I turn on or turn off my bluetooth headset, the Guest OS will freeze. It will no longer respond to any mouse clicks of keyboard presses.

Generally I am in full screen mode. I was recently in windowed mode when this happened and attempting to open the File menu was also unresponsive. Windows then marked the window as Not Responding.


Virtualbox Version 6.1.18 r142142 (Qt5.6.2)
Host: Windows 10 (10.0.18363 Build 18363)
Guest: Ubuntu 20.04


[This thread](https://forums.virtualbox.org/viewtopic.php?f=6&t=94233) contains other users reporting the same issue with slight different pairings of Virtualbox running on Windows10 host with a Linux Guest OS.",plannigan
20313,"CentOS7 poweroff BUG, Couldn't be written",Windows,VirtualBox 6.1.18,2021-04-22T07:17:06Z,2021-04-28T02:15:43Z,2021-04-28T02:15:43Z,"* Windows:  Win10 family Chinese version 20H2 19042.928 Mem 16GB
* CentOS: CentOS Linux release 7.9.2009 (Core) 
* Kernel: 3.10.0-1160.el7.x86_64
* Configuration
  * CPU：1cores
  * Mem: 1GB
  * Network Cards: 1 NAT
* Reproduce:

  Actually, every centos7 VM has the same problem, and it seems to have nothing to do with the virtual machine configuration. This problem occurs regardless of poweroff, shutdown, init 0 or ACPI shutdown commands. In addition, win10 1909 also has this problem.
  I wanna know is that a BUG, thank you!

* Error Message


{{{
VirtualBoxVM.exe - Application Error: 
The instruction at 0x00007FFED15D9B2C referenced memory at 0x00007FFED15D9B2C. The memory could not be written. 
Click on OK to terminate the program.
}}}
",Justin-Young
20321,disk vmdk corrupted,Windows,VirtualBox 5.2.32,2021-04-23T17:36:32Z,2021-04-23T17:36:32Z,2021-04-23T17:36:32Z,"I want to describe my happening:
I have 2 laptops
One with Virtual box 5.2.32 r132073 (Qt5.6.2) version
One with Virtual box 6.1 version

I have first enlarged my vmdk by using VBoxmanage.exe from 10 GB to 100Gb and I have used with my Ubuntu Linux VM for developing. All right.
Then I have moved this vmdk on an external disk (1 Tera) in order to have much more space on my physical disk c:


Any days ago I have thought of create another Vm on second laptop with Virtual Box 6.1 version and use the same virtual disk after lighting my first VM on first laptop off.

So I have corrupted my virtual disk vmdk. In fact now when I use my first laptop and launch my VM I obtain this list of message:

....
...
...
...
...

...

fatal error token exceeds yylmax

  ",masdelmon
20318,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,VirtualBox 6.1.20,2021-04-23T07:25:42Z,2021-04-23T07:25:42Z,2021-04-23T07:25:42Z,"Hi,
any help please",olfat
20311,Failed to create a host network interface.,Windows,VirtualBox 6.1.20,2021-04-21T16:58:04Z,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
19086,rm / rmdir  not working correctly in shared folders,Windows,VirtualBox 6.0.14,2019-11-14T07:22:32Z,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
20298,VBox Additions on Linux = Blackscreen after Boot,Windows,VirtualBox 6.1.18,2021-04-10T20:06:08Z,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
20297,VM crashes after starting recording,Windows,VirtualBox 6.1.18,2021-04-10T09:31:42Z,2021-04-10T09:31:42Z,2021-04-10T09:31:42Z,"VM immediately crashes when starting recording:

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFE918E77E3 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------


Host: Windows 10 x64
Guest: Arch Linux x64 (UEFI boot)

To reproduce:
1. Boot from Arch Linux iso
2. Start recording (View\Recording)

PS. Starting recording via command line works just fine.
",1ns
20281,Critical error CentOS 7,Windows,VirtualBox 5.2.16,2021-04-02T10:18:23Z,2021-04-02T10:18:23Z,2021-04-02T10:18:23Z,"Once a week, a virtual machine running centos 7 crashes with a critical error. Windows server 2008 r2 host - freezes. It is not possible to shutdown virtualbox. Only rebooting the host helps.",Ruby_Ridge
20279,Long-timeout TCP Sessions,Windows,VirtualBox 6.1.18,2021-03-28T20:53:11Z,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
20276,Virtualbox6.1.18 don't work with Windows 10 (Failed to load R0 module),Windows,VirtualBox 6.1.18,2021-03-26T15:04:45Z,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
20274,VM's do not funtion on Win10,Windows,VirtualBox 6.1.18,2021-03-26T01:25:30Z,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
20270,Arch linux guest crash after windows 10 host resume from sleep,Windows,VirtualBox 6.1.18,2021-03-23T03:52:35Z,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
20271,nested virtualisation with kvm cpu hits 100% then L2 guest crashes,Windows,VirtualBox 6.1.18,2021-03-23T13:57:56Z,2021-03-24T21:41:10Z,2021-03-24T21:41:10Z,"Hi,

It maybe that this is known not to work but in the 6.1 docs it mentions kvm as an L2 hypervisor so I thought I'd give it ago.

I have Intel I7 9th gen chip with 6 cores running windows 10 Enterprise build 18363 as my L0

I tried this originally on vbox 6.1.16 but upgraded to 6.1.18 after reading https://www.virtualbox.org/ticket/19315. This caused https://www.virtualbox.org/ticket/20199 so I'm currently running the 6.1.19 test build which fixes the crash but didnt resolve my problem first observed in 6.1.16 so I'm guessing its something different. 

Redhat mention they support some combinations in tech preview when the L0 is RHEL8.2. They say others eg: VMware, Xen, Amazon AWS, Nutanix AHV, Oracle VM are not. 

My use case for this is purely local lab environments mainly in vagrant so I'm more interested in if it work or not then support.

I'm trying to use packer inside a centos7 L1 VM to build with the qemu builder with kvm accelerator.

Packer is able to launch the VM and it starts the install. Its pretty slow but eventually fails installing this glibc.i686 package

{{{
Installing glibc.i686 (684/694)
[ 1354.721435] double fault: 0000 [#1] SMP
[ 1354.722093] Modules linked in: xfs fcoe libfcoe libfc scsi_transport_fc scsi_tgt zram sg pcspkr joydev i2c_piix4 parport_pc parport ext4 mbcache jbd2 loop nls_utf8 isofs sr_mod cdrom 8021q garp mrp stp llc virtio_net virtio_blk net_failover failover drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ata_generic pata_acpi drm ata_piix libata serio_raw virtio_pci virtio_ring virtio drm_panel_orientation_quirks sunrpc xts lrw gf128mul dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq libcrc32c async_xor xor async_tx raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs cramfs edd
[ 1354.722093] CPU: 0 PID: 17227 Comm: glibc_post_upgr Not tainted 3.10.0-1160.el7.x86_64 #1
[ 1354.722093] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.5.1 01/01/2011
[ 1354.722093] task: ffff9fa564fe8000 ti: ffff9fa562bdc000 task.ti: ffff9fa562bdc000
[ 1354.722093] RIP: 0010:[<00000000b5f97d80>]  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093] RSP: 0018:0000000000000000  EFLAGS: 00010082
[ 1354.722093] RAX: 000000000000007a RBX: 00000000ffcc49ca RCX: 0000000000000000
[ 1354.722093] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
[ 1354.722093] RBP: 00000000ffcc495c R08: 0000000000000000 R09: 0000000000000000
[ 1354.722093] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1354.722093] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1354.722093] FS:  0000000000000000(0000) GS:ffff9fa5bcc00000(0000) knlGS:0000000000000000
[ 1354.722093] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 1354.722093] CR2: 00000000b5f97d80 CR3: 0000000022a7c000 CR4: 00000000000006f0
[ 1354.722093] Call Trace:
[ 1354.722093] Code:  Bad RIP value.
[ 1354.722093] RIP  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093]  RSP <0000000000000000>
[ 1354.722093] ---[ end trace 6fd2b3e5f947f091 ]---
[ 1354.722093] Kernel panic - not syncing: Fatal exception
[ 1354.722093] Kernel Offset: 0x34800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
}}}

I see some people are able to get kvm to run fine in vbox. But I'm wondering if they have AMD chips on the L0 or some other fundamental difference.

Any suggestions on how to try to debug this further?


",aw125
20238,VM Crashes at kernel loading on DELL Inspiron 7501,Windows,VirtualBox 6.1.18,2021-03-07T11:51:02Z,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
19729,VM failed to start with enabled EFI,Windows,VirtualBox 6.1.10,2020-07-17T11:44:12Z,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
20219,VirtualBox starts up OK. Failed to open a session for the virtual machine. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine.,Windows,VirtualBox 6.1.18,2021-02-22T17:07:19Z,2021-02-22T17:07:19Z,2021-02-22T17:07:19Z,"I am experiencing the same problem as #20191. VirtualBox starts up fine. Existing VM fails to start with same error as this ticket describes. Failed to open a session for the virtual machine C7.
I have attached the log file, in addition to pasting it below.

The virtual machine 'C7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\C7\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

From VboxHardening.log:

16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'combase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'combase.dll' -> '\Device\HarddiskVolume3\Windows\System32\combase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\combase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDEVAPI.DLL (Input=MMDEVAPI.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDEVAPI.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'rpcrt4.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'oleaut32.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'mmdevapi.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\AudioSes.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\AudioSes.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume3\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\oleaut32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp_win.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp_win.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcp_win.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcp_win.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\AUDIOSES.DLL (Input=AUDIOSES.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'rpcrt4.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\powrprof.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\powrprof.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffba0030000 LB 0x0004b000 C:\windows\SYSTEM32\powrprof.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\powrprof.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb99220000 LB 0x00185000 C:\windows\System32\AUDIOSES.DLL [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\umpdc.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\umpdc.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb9ffb0000 LB 0x00012000 C:\windows\SYSTEM32\UMPDC.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\umpdc.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99220000 'C:\windows\System32\AUDIOSES.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'mmdevapi.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'msacm32.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\msacm32.drv) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.drv 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msacm32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msacm32.dll' -> '\Device\HarddiskVolume3\Windows\System32\msacm32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\msacm32.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d650000 LB 0x0001e000 C:\windows\SYSTEM32\MSACM32.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d9c0000 LB 0x0000d000 C:\windows\System32\msacm32.drv [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\midimap.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\midimap.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmmbase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmmbase.dll' -> '\Device\HarddiskVolume3\Windows\System32\winmmbase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d640000 LB 0x0000b000 C:\windows\System32\midimap.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.1aa0: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDevApi.dll' 11a8.438: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 109337 ms, the end);

I have tried some suggestions found using Google and sometimes they help, but next reboot or start of VirtualBox results in same bad behavior. I also have uninstalled VirtualBox 6.1.18 and re-installed. It sometimes seems to let the VM start up and other times the same error appears. Both the install of VirtualBox 6.1.18 and the startup of VirtualBox 6.1.18 were done as administrator. Anti-Virus Used is: EseT Nod32 14.0.22.0 Windows Info: OS Name Microsoft Windows 10 Pro Version 10.0.19041 Build 19041 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-H70PDLJ System Manufacturer HP System Model HP EliteBook 855 G7 Notebook PC System Type x64-based PC System SKU 3E780AV Processor AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1700 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date HP S77 Ver. 01.02.03, 11/27/2020 SMBIOS Version 3.2 Embedded Controller Version 7.44 BIOS Mode UEFI BaseBoard Manufacturer HP BaseBoard Product 8760 BaseBoard Version KBC Version 07.2C.00 Platform Role Mobile Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\windows System Directory C:\windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = ""10.0.19041.488"" User Name DESKTOP-H70PDLJ\willh Time Zone Central Standard Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.3 GB Available Physical Memory 27.9 GB Total Virtual Memory 36.1 GB Available Virtual Memory 32.6 GB Page File Space 4.75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes",WillH
20217,Xmodmap needs several executions on Windows 10 host,Windows,VirtualBox 6.1.16,2021-02-21T23:19:23Z,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
20209,Windows 10 host - ubuntu 20.10 guest crush,Windows,VirtualBox 6.1.18,2021-02-19T20:23:10Z,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.",Дмитро
20181,WinVerifyTrust for MMDevAPI.dll,Windows,VirtualBox 6.1.18,2021-02-10T16:39:32Z,2021-02-19T13:00:07Z,2021-02-19T13:00:07Z,"Microsoft updated this dll on 09/02/2021 and since then all virtualbox guests are falling over unexpectedly during startup with exit code 1 (0x1). the cause in the VBoxHardening.log file is MMDevAPI.dll lacks WinVerifyTrust.
Attached is the VBoxHardening.log for a newly created Fedora Linux host.
Version of Windows is Windows 10 Pro Ver 20H2 OS build 19042.804",Tim_B
20205,OL8 VM aborted - appears screen resize or USB related,Windows,VirtualBox 6.1.16,2021-02-19T12:24:44Z,2021-02-19T12:24:44Z,2021-02-19T12:24:44Z,"Two suspects for my VM aborting:

1. USB. I use a USB dongle and regularly attach/detach via the VBox device menu.

2. Screen resize.  I frequently resize my VM window as I shuffle windows around to different displays, snap to one side of the screen, etc.",mocooern
20187,"Ubuntu 18.04 guest boots up 1 in 5 times. In other times, a cursor in blank screen blinking with no progress",Windows,VirtualBox 6.1.18,2021-02-14T15:03:42Z,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
20146,"High CPU Kernel usage for any golang project, Windows 10 Host, Hyper-V turn on",Windows,VirtualBox 6.1.18,2021-01-22T05:20:12Z,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
20159,Reproducible fatal crash of a Linux Mint 20 XFCE VM (VirtBox running on Win10),Windows,VirtualBox 6.1.18,2021-01-29T10:47:30Z,2021-01-29T10:47:30Z,2021-01-29T10:47:30Z,"I have configured several virtual machines running the latest Linux Mint 20 XFCE4 edition. The display configuration is VMSVGA + 3D acceleration. After installing g++, make, and 6.1.8 guest additions I rebooted them. Then I installed the Atom editor. On every machine the same error occurred reproducibly: When I tore off a tab to attach it to another pane the vm crashed with an error message: 

The instruction at 0x00007FFE673EE652 referenced memory at 0x0000000000000000. 
The memory could not be written. 
Click OK to terminate the program. 

The error seems not to occur when I use another virtual graphics card, but due to the performance lack this is not solution to the problem. 

As I said: I have set up several machines from scratch, the error occurs everytime, absolutely reproducible within Atom. ",Dude McGee
19235,GDM with (default) Wayland sessions are not usable,Windows,VirtualBox 6.1.2,2020-01-16T10:04:45Z,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
19686,Guest audio loss following Windows host suspend,Windows,VirtualBox 6.1.10,2020-06-27T15:50:21Z,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
19243,VMSVGA 3d get Crash while guest try to reboot,Windows,VirtualBox 6.1.2,2020-01-20T01:15:48Z,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
20081,Installing Linux subsystem on windows 10 caused read/write error inside running linux mint (in virtual box),Windows,VirtualBox 6.1.16,2020-12-05T10:00:50Z,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
20102,Unable to compile Guest Additions on Linux Kernel 5.4.80.,Windows,VirtualBox 6.1.16,2020-12-26T22:21:43Z,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
20136,"upon resume getting ""VBoxClient: Crtc disable failed 63""",Windows,VirtualBox 6.1.16,2021-01-19T17:15:10Z,2021-01-19T17:15:10Z,2021-01-19T17:15:10Z,"6.1.16 r140961 (Qt 5.6.2)

Sometime reactivating the ""full screen"" fixes it, sometimes I have to reboot",ralfhauser
20135,After installing Centos OS the VM is failing to reboot,Windows,VirtualBox 6.1.16,2021-01-18T21:52:15Z,2021-01-18T21:52:15Z,2021-01-18T21:52:15Z,"The Host PC is Windows 10, after installing a Centos minimal image using vagrant the image fails to boot. There are obvious errors that in the log file.
I have installed an ubuntu vm and that works fine.

",harryv
20127,Finalize File System fails,Windows,VirtualBox 6.1.16,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,"Failed to finalize file system
",MikeTheBike
20111,"Drag and Drop not working: Windows 10(host), Fedora 33(guest)",Windows,VirtualBox 6.1.16,2020-12-31T15:26:22Z,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
20110,Virtualbox looses track of USB SSD,Windows,VirtualBox 6.1.16,2020-12-31T06:45:36Z,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
20096,Crash when powering off guest OS,Windows,VirtualBox 6.1.16,2020-12-19T01:59:57Z,2020-12-19T01:59:57Z,2020-12-19T01:59:57Z,"Host: Windows 10 build 17763 amd64
Guest: Ubuntu 18
1. Start guest OS
2. Sleep/resume host computer (not sure if this is necessary but seems related)
3. From within the guest OS, select the power off setting.
Message box appears: The instruction at 0x0000&FF9E4808561 referenced memory at 0x0000000000000021. The memory could not be written.

This crash is intermittent and happens prior to the screen resizing to the linux text-based shutdown screen (i.e. guest is still running X)",jkriegshauser
20094,VB Blank screen after one day.,Windows,VirtualBox 6.1.16,2020-12-16T21:46:23Z,2020-12-17T14:52:09Z,2020-12-17T14:52:09Z,"
While running VB version Versie 6.1.16 r140961 (Qt5.6.2) on Windows host computer (windows 10 pro) after one day the VB screen will turn blank.

Only closing the program and restarting it will show the regular screen again.

Is there a fix ?

[img]https://imgur.com/3s39bcD[/img]
",VB-box
15845,e1000 Detected Tx Unit Hang,Windows,VirtualBox 5.1.2,2016-08-22T09:48:52Z,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
20023,After Update to 6.1.16: Black screen after booting Ubuntu in fullscreen,Windows,VirtualBox 6.1.16,2020-11-06T08:01:30Z,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
20088,Soft reset from guest does not reliably restart VM,Windows,VirtualBox 6.1.16,2020-12-09T08:43:00Z,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
20087,Sending multiple VBoxManage commands can cause VBox GUI to hang,Windows,VirtualBox 6.1.16,2020-12-09T08:37:53Z,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
20080,Problem running Ubuntu VM,Windows,VirtualBox 6.1.16,2020-12-05T00:34:02Z,2020-12-05T00:34:02Z,2020-12-05T00:34:02Z,"I was trying to set up Windows Subsystem for Linux on my laptop running on Windows 10. I switched on WSL options and restarted the machine. After that I started my Ubuntu VM on VirtualBox. It causes some errors and close the VM. I, then switches off the WLS which started the Ubuntu VM but recommended turning it off. Log file is attached herewith.",mshahin
18872,I cannot enable second monitor,Windows,VirtualBox 6.0.10,2019-08-28T08:47:59Z,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
16973,"Thunderbolt 3 Docks, VirtualBox needs new behavior model",Windows,VirtualBox 5.1.26,2017-08-02T18:50:58Z,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.
20068,Guru Meditation,Windows,VirtualBox 6.1.16,2020-11-26T06:12:00Z,2020-11-26T06:12:00Z,2020-11-26T06:12:00Z,Guru Meditation Error in windows host and Kali guest,Aqua
20062,Guru Meditation Fault,Windows,VirtualBox 6.1.16,2020-11-24T13:18:39Z,2020-11-24T13:18:39Z,2020-11-24T13:18:39Z,"Received a Guru Meditation fault while running git status from the guest.
The Win 10 host was in the middle of its own startup activity and was quite busy. The Ubuntu 18.04 client had just started and was in the middle of an update when the fault occurred. Please see attachments.",TFR
20038,Linux guest GUI freeze or full VM hang after not being interracted with for some time,Windows,VirtualBox 6.1.16,2020-11-15T14:48:40Z,2020-11-24T11:17:52Z,2020-11-24T11:17:52Z,"
== Linux guest GUI freeze or full VM hang after not being interacted with for some time ==


'''Terms in use:'''

 - '''GUI Freeze''': The ''GUI inside the VM, XFCE, is not responsive''. ''The VM is still active, as can be seen by the activity indicators'' (disk, network, etc). A console can be brought up (ctl-alt-F2 for example), logged into, and all of my users processes killed with ""pkill -u myusername"". This causes the GUI to become responsive, giving me the fresh login screen. This is not optimal, however, at least it's a clean shutdown of programs. Alternately I can perform an ACPI shutdown and the system will shut down cleanly.
 
 - '''Full VM Hang''': The ''GUI inside the VM, XFCE, is not responsive. The VM is NOT active, as the activity indicators are inactive.'' A console can NOT be brought up (ctl-alt-F2 for example). Using the soft keyboard and trying the same has no effect. Sending ACPI shutdown signals has no effect. At the same time as this, ''sometimes the virtualbox GUI for managing the virtual machines hangs''. This can only be resolved by manually killing off the VM and anything virtualbox related, and rebooting the host.
 

'''VirtualBox information:'''

 - Version 6.1.16
 - Extension pack 6.1.16

'''Host information:'''

 - Windows 10 pro
 - Intel 4GHz corex CPU
 - 128GB RAM
 - Samsung SSD Disks
 - Nvidia GeForce RTX 2080 Ti using Nvidias drivers

'''Guest information:'''

 - Linux Mint 20
 - GUI: XFCE
 - Guest additions: 6.1.16
 - Virtual RAM: 9240 MB
 - Virtual processors: 6
 - Acceleration: default
 - Display: 128MB RAM, VMSVGA, Enable 3D Acceleration
 - Storage: SATA: Disk 1: Linux_Mint_19.vdi | Virtual size: 300GB | Actual size: 91GB
 - Storage: SATA: Disk 2: Linux_Mint_19_swap.vdi | Virtual size: 16GB | Actual size: 9GB
 
===

'''Issue Details:'''

Frequently after being away at least 10 or 15 minutes the guest will either experience a GUI freeze (see above for a description), or a full VM hang. The first situation can be recovered from, however in the second situation nothing can be done. For this reason I take frequent snapshots while the VM is powered on so that I can use them to restore from as setting everything back up again and again and again gets frustrating.

===

'''Solutions attempted:'''

Disable the screen saver / screen lock etc inside of the guest: The prior night I did this and returned in the morning to find that a full VM hang had taken place shortly after I had left to go to sleep. I know when it took place because of the time shown in the GUI (stuck).

Restore the latest snapshot, cleanly shut down, and power the VM on again: The issue still frequently occurs.

Disable 3D Acceleration: The issue still frequently occurs.


===

'''Logs:'''

''Note: For each of the logs, I prefix a string like ""round1"" and then refer to them that way. Please be sure to refer to them that way to me as well.''

The last log in round1 Vbox.log for this VM is: 
{{{
14:38:47.761976 GUI: UIMediumEnumerator: Medium-enumeration finished!
}}}


The full round1 Vbox.log will be attached. In addition I'll attach round1 VBox.log.1 , VBox.log.2 and VBox.log.3 .

round1 VBoxHardening.log doesn't really make sense to me so I'll just attach it.

Windows event log upon shutting down the host for round1, since it was both a full VM hang AND the virtualbox management interface became unresponsive:

{{{winlog.event_data.Caption:
    VirtualBox: VirtualBox.exe - Application Error
message:
    '''Application popup: VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
agent.hostname:
    MY-SYSTEM-NAME
agent.name:
    MY-SYSTEM-NAME
agent.id:
    130ce1c1-0e0a-419c-9b7f-f4bf70a6c377
agent.type:
    winlogbeat
agent.ephemeral_id:
    002ca6d2-1396-44b0-9a31-ec9b95be97bc
agent.version:
    7.9.0
winlog.record_id:
    2,049
winlog.computer_name:
    MY-SYSTEM-NAME
winlog.process.pid:
    16,852
winlog.process.thread.id:
    2,196
winlog.event_id:
    26
winlog.task:
winlog.provider_guid:
    {47bfa2b7-bd54-4fac-b70b-29021084ca8f}
winlog.channel:
    System
winlog.event_data.Message:
    '''The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
winlog.api:
    wineventlog
winlog.provider_name:
    Application Popup
winlog.opcode:
    Info
winlog.user.identifier:
    S-1-5-18
winlog.user.domain:
    NT AUTHORITY
winlog.user.name:
    SYSTEM
winlog.user.type:
    User}}}

===

'''Follow up:'''

What more can I provide to assist?",Fieldy
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,VirtualBox 6.1.14,2020-11-24T10:45:10Z,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
20020,VirtualBox 6.1.16 Ubuntu 20.04 Guest freezes when windows 10 screensaver or screen lock,Windows,VirtualBox 6.1.16,2020-11-05T15:37:23Z,2020-11-22T10:54:59Z,2020-11-22T10:54:59Z,When I lock screen on Windows 10 host and then unlock and log back in my VirtualBox Ubuntu 20.04 Guest v6.1.16 freezes (I even have issues closing the main window of VirtualBox guest). Totally unresponsive. Only closing guest (after putting in some effort) main window with quite a few attempts including VirtualBox Manager on host freezing at the same time and restarting gets the VM back to life only to be unusable after host screen lock again...,SamH
20056,no mouse pointer or capture after login,Windows,VirtualBox 6.1.16,2020-11-21T15:17:33Z,2020-11-21T15:17:33Z,2020-11-21T15:17:33Z,"Until 11/17/20, my VM worked perfectly. Now, the mouse works UNTIL I login. But AFTER login, the capture is no longer working. There is NO mouse pointer on the virtual desktop, just the REAL mouse pointer, which moves anywhere, in or out of the Virtualbox.
The Vbox message (at the top of the window) saying the capture is effective shows and the capture icon indicates the mouse integration is on, but it is NOT being captured.
Using the CNTRL key to get the ""capture"" window and allowing capture, the mouse is NOT captured. 

I am using VBOX 6.1.16. My guest O/S is Ubuntu 20.04.1-AMD64. 
My HOST O/S is Windows 10 Pro 64-bit. I/O APIC was already on and I left it on.
I have tried:
*VMSVGA vs. VBOXSVGA vs VBOXVGA
*increase video memory to 128MB
*1 vs 2 CPUs
*USB tablet vs PS/2 Mouse
*paravirtualization: default vs minimal
*re-install Vbox extensions
* Enable PAE/NX
*3D accel on vs off
None of these make any difference. 
""File>send shutdown signal"" does NOT shut down the VM.

",Dennis Foreman
18522,Audio transmitted with the VBox Remote Display server sounds chopped and pitched,Windows,VirtualBox 6.0.4,2019-03-26T11:03:16Z,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
20045,Install Debian not run,Windows,VirtualBox 6.1.14,2020-11-17T08:18:35Z,2020-11-17T08:18:35Z,2020-11-17T08:18:35Z,Installation of Debian will not run with VirtualBox 6.1.14r140239,christophedlr34
12570,VM window appears off screen; not accessible,Windows,VirtualBox 4.3.6,2014-01-03T15:11:01Z,2020-11-14T10:18:07Z,2020-11-14T10:18:07Z,"Virtual box remembers guest window location and uses it at next start-up for a VM.  This is a good thing.  However, what it doesn't do is confirm upon start-up that the remembered location is still valid and will display the window off screen and not viewable.  Worse, it does not respond to the typical Windows move commands in order to move the window back into viewable space.  This leads to not being able to correct the condition and the user is stuck with a window they cannot access.

Specifics:
At home, I have an additional monitor that is positioned vertically above my laptop screen and is oriented that way in Windows ""Screen Resolution"" where one identifies monitors and their relative locations.  At the office, I have three external monitors, all side-by-side, and do not use the laptop screen.

I had worked at home and placed the VM window in the ""top"" monitor in scaled mode.  I shut down the guest and then shut-down the host laptop in that condition and went to the office.  There, I started the host laptop, opened VirtualBox, and started the guest.  Initially, the guest window came up in my main monitor.  I then switched it to scaled mode and the window disappeared.  Attempts to move it via the Windows Move option from the System menu was not successful.

I ended up having to go into ""Screen Resolution"" and orienting my monitors to place one of them ""above"" my main monitor -- thus replicating the condition under which the scaled guest window last appeared.  Doing this, I was able to then access the guest window and drag it ""down"" to the main monitor.  I then reverted the monitor orientation to side-by-side and moved the guest window to the monitor on the side.

Certainly not an insurmountable issue but until I thought about trying the re-orienting of my monitors, I was really stuck.",RodBarnes
20019,Hosted VM is restarting unexpectedly which contains VirtualBox,Windows,VirtualBox 6.1.16,2020-11-05T08:16:49Z,2020-11-05T08:16:49Z,2020-11-05T08:16:49Z,"We've a Windows 10 Azure VM  which we have installed latest VirtualBox on it. After starting image on VB, everything is fine. But, when we try to login to guest vm via filezilla/putty from hosted vm, it's restarting hosted VM suddenly. 

Please check log that belongs to guest vm that we having problem.",alpercelerce
18404,No Audio on Linux Guest with Windows 10 x64 host when changing output device in host,Windows,VirtualBox 6.0.4,2019-02-01T10:49:39Z,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
20002,Crash when restoring machine state and launching or selecting program from favorites,Windows,VirtualBox 6.1.16,2020-10-27T14:38:16Z,2020-10-27T14:38:16Z,2020-10-27T14:38:16Z,"Windows 10 host and Ubuntu Desktop guest.

Whenever I save machine state with something running, I get a crash when I restore (the crash comes when I select a favorite, whether it was running or not). I have seen this in various scenarios (basically any other than shutting down with nothing running at all). I have attached logs for the following scenario.

1. Launch Ubuntu VM.
2. Start LibreOffice Writer (really can be anything, Visual Studio Code will do the same thing).
3. Click the 'X' in the far upper right to close VB. Select 'Save the machine state'.
4. In VB with the Ubuntu machine selected, click 'Start'.
5. The machine is restored, with the LibreOffice Writer document open.
6. Click on Chrome in the Favorites panel, trying to launch it (again, I'm not sure it matters what program you try to launch here).
7. The crash window immediately comes up (the one with the OK and IGNORE buttons telling me I have to shut down and where the logs are, etc.)

This behavior is consistent. It basically makes the program unusable because I have to shut down the machine whenever I close VB.
",mark6139
19999,no me deja aceptar las configuraciones que deseo aplicar en mi virtual box,Windows,VirtualBox 6.1.16,2020-10-26T04:21:42Z,2020-10-26T04:21:42Z,2020-10-26T04:21:42Z,,roldan0314
19996,Black Screen of Death,Windows,VirtualBox 6.1.16,2020-10-24T18:59:43Z,2020-10-24T18:59:43Z,2020-10-24T18:59:43Z,"I'm trying to get virtualbox running on a windows 10 pro (2004) machine and create a linuxmint vm.  When I start the VM I get the linux screen that says ""start linux"" and then after 10 seconds the screen goes black.  I have disabled hyper-v, i have unchecked 3d acceleration.  I was able to get VMWARE to work but not having any luck with virtualbox.  I've attached the log file",rsail
19873,VMSVGA: 1920x1080 resolution not available at boot (?),Windows,VirtualBox 6.1.14,2020-09-09T12:46:39Z,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
19982,Crash when using vscode on linux guest,Windows,VirtualBox 6.1.14,2020-10-20T17:19:14Z,2020-10-20T17:19:14Z,2020-10-20T17:19:14Z,"Hello,

VB crashes when I use vscode on a linux ( Ubuntu ) guest. It crashes when I right click to display a menu.
I join the crash  logs and a copy of the error message ( ""memory state cannot be written"" ). Is this enough to start to debug or do you need more information ? 

Thanks !

Crash logs : 

151:19:24.402862 AIOMgr: Async flushes not supported
152:49:24.051989 
152:49:24.051991 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000004184!!!
152:49:24.053107 
152:49:24.053108 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffc189728c2
152:49:24.053118 ExceptionInformation[0]=0000000000000001
152:49:24.053124 ExceptionInformation[1]=0000000000000000
152:49:24.053128 
152:49:24.053129 cs:rip=0033:00007ffc189728c2
152:49:24.053149 ss:rsp=002b:00000000cacbf560 rbp=00000000cacbf610
152:49:24.053154 rax=00000000cdeb87c0 rcx=0000000000000000 rdx=0000000082751090 rbx=0000000082751070
152:49:24.053159 rsi=0000000219a24c00 rdi=0000000219a24c00 rsp=00000000cacbf560 rbp=00000000cacbf610
152:49:24.053165 r8 =0000000000000000 r9 =0000000082751450 r10=0000000000000000 r11=00000000cacbf6a0
152:49:24.053170 r12=000000026a000770 r13=0000000000000000 r14=000000026a000080 r15=00000000cd680f40
152:49:24.053175 ds=002b es=002b fs=0053 gs=002b eflags=00010206
152:49:24.053180 p1home=0000000000000000 p2home=0000000000000000 pe3home=0000000082751070
152:49:24.053185 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
152:49:24.053189    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
152:49:24.053194 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
152:49:24.053202 
152:49:24.053203 Stack 00000000cacbe440, dumping 0x1bc0 bytes (low=00000000cabc0000, high=00000000cacc0000)
152:49:24.054088 00000000cacbe440/0000: 40 e4 cb ca 00 00 00 00-73 74 61 63 6b 6d 61 72 @.......stackmar
152:49:24.054818 00000000cacbe450/0010: 6b 65 72 00 00 00 00 00-00 10 02 00 00 00 00 00 ker.............
152:49:24.054825 00000000cacbe460/0020: 00 00 00 00 00 00 00 00-80 d7 75 54 fc 7f 00 00 ..........uT....
152:49:24.054831 00000000cacbe470/0030: 01 00 00 00 00 00 00 00-ff ff ff ff ff ff ff ff ................
152:49:24.054839 00000000cacbe480/0040: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054845 00000000cacbe490/0050: d0 59 c2 fa fb 7f 00 00-50 f8 cb ca 00 00 00 00 .Y......P.......
152:49:24.054848 00000000cacbe4a0/0060: 00 00 00 00 00 00 00 00-aa 08 5f 54 fc 7f 00 00 .........._T....
152:49:24.054849 00000000cacbe4b0/0070: 40 e6 cb ca 00 00 00 00-c2 28 97 18 fc 7f 00 00 @........(......
152:49:24.054851 00000000cacbe4c0/0080: 00 00 cc ca 00 00 00 00-00 00 bc ca 00 00 00 00 ................
152:49:24.054852 00000000cacbe4d0/0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054854 00000000cacbe4e0/00a0: 06 00 00 00 04 00 00 00-00 00 00 00 01 00 00 00 ................
152:49:24.054855 00000000cacbe4f0/00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054857 00000000cacbe500/00c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054858 00000000cacbe510/00d0: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054860 00000000cacbe520/00e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054862 **************** ****  <ditto x 6>
152:49:24.054862 00000000cacbe590/0150: 25 f0 25 10 04 1a 00 00-00 00 00 00 00 00 00 00 %.%.............
152:49:24.054864 00000000cacbe5a0/0160: 00 00 b4 56 fc 7f 00 00-40 ec cb ca 00 00 00 00 ...V....@.......
152:49:24.054866 00000000cacbe5b0/0170: 50 f8 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 P...............
152:49:24.054868 00000000cacbe5c0/0180: 00 00 00 00 00 00 00 00-b2 4a be 56 fc 7f 00 00 .........J.V....
152:49:24.054869 00000000cacbe5d0/0190: 00 00 00 00 00 00 00 00-20 44 c8 56 fc 7f 00 00 ........ D.V....
152:49:24.054871 00000000cacbe5e0/01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054872 00000000cacbe5f0/01b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054882 00000000cacbe600/01c0: 51 ce 06 00 00 00 00 00-56 c6 bc 56 fc 7f 00 00 Q.......V..V....
152:49:24.054883 00000000cacbe610/01d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054885 00000000cacbe620/01e0: 08 ec cb ca 00 00 00 00-90 ec cb ca 00 00 00 00 ................
152:49:24.054886 00000000cacbe630/01f0: a4 0e c0 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054902 00000000cacbe640/0200: b0 f2 cb ca 00 00 00 00-c0 ed cb ca 00 00 00 00 ................
152:49:24.054903 00000000cacbe650/0210: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.054905 00000000cacbe660/0220: c0 ed cb ca 00 00 00 00-c0 c5 bc 56 fc 7f 00 00 ...........V....
152:49:24.054906 00000000cacbe670/0230: 00 00 00 00 00 00 00 00-cf 11 be 56 fc 7f 00 00 ...........V....
152:49:24.054908 00000000cacbe680/0240: 00 00 00 00 00 00 00 00-f0 eb cb ca 00 00 00 00 ................
152:49:24.054909 00000000cacbe690/0250: b0 f2 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.054924 00000000cacbe6a0/0260: 40 ec cb ca 00 00 00 00-09 a2 ba 56 fc 7f 00 00 @..........V....
152:49:24.054926 00000000cacbe6b0/0270: 01 00 00 00 00 00 00 00-00 00 b4 56 fc 7f 00 00 ...........V....
152:49:24.054928 00000000cacbe6c0/0280: 00 00 00 00 00 00 00 00-f0 e9 ca 56 fc 7f 00 00 ...........V....
152:49:24.054929 00000000cacbe6d0/0290: f0 e6 cb ca 00 00 00 00-10 ec cb ca 00 00 00 00 ................
152:49:24.054931 00000000cacbe6e0/02a0: 00 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054932 00000000cacbe6f0/02b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055264 **************** ****  <ditto x 2>
152:49:24.055266 00000000cacbe720/02e0: 0f 00 10 00 a0 1f 00 00-33 00 00 00 00 00 00 00 ........3.......
152:49:24.055268 00000000cacbe730/02f0: 00 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 ..+.............
152:49:24.055270 00000000cacbe740/0300: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055272 **************** ****  <ditto x 3>
152:49:24.055273 00000000cacbe780/0340: 00 00 00 00 00 00 00 00-d0 f8 cb ca 00 00 00 00 ................
152:49:24.055275 00000000cacbe790/0350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055276 **************** ****  <ditto x 5>
152:49:24.055277 00000000cacbe7f0/03b0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055279 00000000cacbe800/03c0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055280 00000000cacbe810/03d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055282 **************** ****  <ditto x 23>
152:49:24.055283 00000000cacbe990/0550: c0 ed cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055284 00000000cacbe9a0/0560: ff ff ff ff ff ff ff ff-00 00 00 00 00 00 00 00 ................
152:49:24.055286 00000000cacbe9b0/0570: 80 ea cb ca 00 00 00 00-2b 2e f3 15 f7 7f 00 00 ........+.......
152:49:24.055288 00000000cacbe9c0/0580: 40 94 fa 15 f7 7f 00 00-c0 eb cb ca 00 00 00 00 @...............
152:49:24.055290 00000000cacbe9d0/0590: c0 87 eb cd 00 00 00 00-70 10 75 82 00 00 00 00 ........p.u.....
152:49:24.055291 00000000cacbe9e0/05a0: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055293 00000000cacbe9f0/05b0: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055295 00000000cacbea00/05c0: 00 00 00 00 00 00 00 00-50 14 75 82 00 00 00 00 ........P.u.....
152:49:24.055296 00000000cacbea10/05d0: 00 00 00 00 00 00 00 00-a0 f6 cb ca 00 00 00 00 ................
152:49:24.055298 00000000cacbea20/05e0: 70 07 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 p..j............
152:49:24.055300 00000000cacbea30/05f0: 80 00 00 6a 02 00 00 00-40 0f 68 cd 00 00 00 00 ...j....@.h.....
152:49:24.055301 00000000cacbea40/0600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055303 00000000cacbea50/0610: c2 28 97 18 fc 7f 00 00-60 f5 cb ca 00 00 00 00 .(......`.......
152:49:24.055305 00000000cacbea60/0620: 10 f6 cb ca 00 00 00 00-5f 00 10 00 00 00 00 00 ........_.......
152:49:24.055306 00000000cacbea70/0630: 33 00 00 00 00 00 00 00-2b 00 00 00 00 00 00 00 3.......+.......
152:49:24.055308 00000000cacbea80/0640: 2b 00 00 00 37 66 66 63-2b 00 00 00 32 38 63 32 +...7ffc+...28c2
152:49:24.055310 00000000cacbea90/0650: 53 00 00 00 00 00 00 00-2b 00 00 00 fc 7f 00 00 S.......+.......
152:49:24.055311 00000000cacbeaa0/0660: 06 02 01 00 00 00 00 00-a0 1f 00 00 02 00 00 00 ................
152:49:24.055313 00000000cacbeab0/0670: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055314 **************** ****  <ditto x 7>
152:49:24.055315 00000000cacbeb30/06f0: 00 4c a2 19 02 00 00 00-d6 2f f3 15 f7 7f 00 00 .L......./......
152:49:24.055317 00000000cacbeb40/0700: 02 00 00 00 00 00 00 00-00 70 cf 00 00 00 00 00 .........p......
152:49:24.055318 00000000cacbeb50/0710: 20 97 fa 15 f7 7f 00 00-05 00 00 c0 00 00 00 00  ...............
152:49:24.055320 00000000cacbeb60/0720: 01 00 00 00 00 00 00 00-40 0f 68 cd 00 00 00 00 ........@.h.....
152:49:24.055322 00000000cacbeb70/0730: 80 00 00 6a 02 00 00 00-f2 ec b5 56 fc 7f 00 00 ...j.......V....
152:49:24.055323 00000000cacbeb80/0740: 70 07 00 6a 02 00 00 00-00 4c a2 19 02 00 00 00 p..j.....L......
152:49:24.055325 00000000cacbeb90/0750: b0 f2 cb ca 00 00 00 00-0b 00 10 00 00 00 00 00 ................
152:49:24.055327 00000000cacbeba0/0760: 10 00 00 00 00 00 00 00-dc a0 ba 56 fc 7f 00 00 ...........V....
152:49:24.055329 00000000cacbebb0/0770: 00 00 00 00 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.055330 00000000cacbebc0/0780: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055335 00000000cacbebd0/0790: 19 00 00 00 00 00 00 00-72 3a 20 30 78 63 30 30 ........r: 0xc00
152:49:24.055336 00000000cacbebe0/07a0: 30 30 30 30 35 20 28 30-30 30 30 30 30 30 30 30 00005 (000000000
152:49:24.055338 00000000cacbebf0/07b0: 00 30 30 30 30 30 31 2c-90 ec cb ca 00 00 00 00 .000001,........
152:49:24.055339 00000000cacbec00/07c0: 50 f8 cb ca 00 00 00 00-00 00 b4 56 fc 7f 00 00 P..........V....
152:49:24.055341 00000000cacbec10/07d0: 20 44 c8 56 fc 7f 00 00-00 00 00 00 00 00 00 00  D.V............
152:49:24.055343 00000000cacbec20/07e0: 00 00 cc ca 00 00 00 00-00 d0 cb ca 00 00 00 00 ................
152:49:24.055344 00000000cacbec30/07f0: c0 ed cb ca 00 00 00 00-80 51 9d 18 fc 7f 00 00 .........Q......
152:49:24.055346 00000000cacbec40/0800: 51 ce ba 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 Q..V.......V....
152:49:24.055348 00000000cacbec50/0810: f0 e9 ca 56 fc 7f 00 00-50 f8 cb ca 00 00 00 00 ...V....P.......
152:49:24.055349 00000000cacbec60/0820: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.055351 00000000cacbec70/0830: c0 c5 bc 56 fc 7f 00 00-20 44 c8 56 fc 7f 00 00 ...V.... D.V....
152:49:24.055352 00000000cacbec80/0840: 90 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055354 00000000cacbec90/0850: 0a 00 00 00 00 00 00 00-80 38 8f 18 fc 7f 00 00 .........8......
152:49:24.055355 00000000cacbeca0/0860: 78 ce ba 56 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x..V............
152:49:24.055357 00000000cacbecb0/0870: 80 4b a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .K..............
152:49:24.055358 00000000cacbecc0/0880: b0 48 a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .H..............
152:49:24.055360 00000000cacbecd0/0890: a4 0f a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055362 00000000cacbece0/08a0: 78 fc a2 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x...............
152:49:24.055363 00000000cacbecf0/08b0: b4 1d a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055365 00000000cacbed00/08c0: b8 1c a3 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055366 00000000cacbed10/08d0: d4 0e c0 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055368 00000000cacbed20/08e0: a4 0e c0 18 fc 7f 00 00-00 00 31 56 fc 7f 00 00 ..........1V....
152:49:24.055369 00000000cacbed30/08f0: d8 ac 3b 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 ..;V.......V....
152:49:24.055371 00000000cacbed40/0900: f0 e9 ca 56 fc 7f 00 00-08 c0 f3 15 f7 7f 00 00 ...V............
152:49:24.055373 00000000cacbed50/0910: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055374 00000000cacbed60/0920: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055376 00000000cacbed70/0930: e0 41 c3 4b 97 74 00 00-a0 f6 cb ca 00 00 00 00 .A.K.t..........
152:49:24.055377 00000000cacbed80/0940: 40 0f 68 cd 00 00 00 00-80 00 00 6a 02 00 00 00 @.h........j....
152:49:24.055379 00000000cacbed90/0950: 00 00 00 00 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055380 00000000cacbeda0/0960: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055382 00000000cacbedb0/0970: 10 f6 cb ca 00 00 00 00-3e fe bd 56 fc 7f 00 00 ........>..V....
152:49:24.055384 00000000cacbedc0/0980: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055385 00000000cacbedd0/0990: 70 10 75 82 00 00 00 00-00 00 00 00 00 00 00 00 p.u.............
152:49:24.055387 00000000cacbede0/09a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055388 00000000cacbedf0/09b0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
152:49:24.055390 00000000cacbee00/09c0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
152:49:24.055391 00000000cacbee10/09d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055393 00000000cacbee20/09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055396 00000000cacbee30/09f0: 00 00 00 00 00 00 00 00-c0 87 eb cd 00 00 00 00 ................
152:49:24.055398 00000000cacbee40/0a00: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055399 00000000cacbee50/0a10: 70 10 75 82 00 00 00 00-60 f5 cb ca 00 00 00 00 p.u.....`.......
152:49:24.055401 00000000cacbee60/0a20: 10 f6 cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055403 00000000cacbee70/0a30: 00 4c a2 19 02 00 00 00-00 00 00 00 00 00 00 00 .L..............
152:49:24.055404 00000000cacbee80/0a40: 50 14 75 82 00 00 00 00-00 00 00 00 00 00 00 00 P.u.............
152:49:24.055406 00000000cacbee90/0a50: a0 f6 cb ca 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055407 00000000cacbeea0/0a60: 00 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055409 00000000cacbeeb0/0a70: 40 0f 68 cd 00 00 00 00-c2 28 97 18 fc 7f 00 00 @.h......(......
152:49:24.055410 00000000cacbeec0/0a80: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055412 00000000cacbeed0/0a90: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055413 00000000cacbeee0/0aa0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055415 **************** ****  <ditto x 58>
152:49:24.055416 00000000cacbf290/0e50: 30 fb ff ff a0 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055417 00000000cacbf2a0/0e60: f0 00 00 00 e0 01 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055419 00000000cacbf2b0/0e70: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055421 00000000cacbf2c0/0e80: c2 28 97 18 fc 7f 00 00-02 00 00 00 00 00 00 00 .(..............
152:49:24.055422 00000000cacbf2d0/0e90: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055438 00000000cacbf2e0/0ea0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055440 **************** ****  <ditto x 5>
152:49:24.055440 00000000cacbf340/0f00: 00 00 00 00 00 00 00 00-c6 2b 97 18 fc 7f 00 00 .........+......
152:49:24.055442 00000000cacbf350/0f10: c2 28 97 18 fc 7f 00 00-00 00 00 00 00 00 00 00 .(..............
152:49:24.055443 00000000cacbf360/0f20: 00 00 00 00 00 00 00 00-60 f5 cb ca 00 00 00 00 ........`.......
152:49:24.055445 00000000cacbf370/0f30: f8 37 00 6a 02 00 00 00-87 c9 9a 18 fc 7f 00 00 .7.j............
152:49:24.055446 00000000cacbf380/0f40: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
152:49:24.055448 00000000cacbf390/0f50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055449 **************** ****  <ditto x 2>
152:49:24.055450 00000000cacbf3c0/0f80: 00 82 2f 7c 00 00 00 00-00 00 00 00 02 00 00 00 ../|............
152:49:24.055451 00000000cacbf3d0/0f90: 00 01 00 00 00 00 00 00-c0 81 2f 7c 00 00 00 00 ........../|....
152:49:24.055453 00000000cacbf3e0/0fa0: 17 03 00 00 00 00 00 00-1e 00 00 00 e0 01 00 00 ................
152:49:24.055455 00000000cacbf3f0/0fb0: 17 03 00 00 00 00 00 00-00 00 00 00 17 03 00 00 ................
152:49:24.055456 00000000cacbf400/0fc0: 17 03 00 00 00 00 00 00-00 02 00 00 00 00 00 00 ................
152:49:24.055458 00000000cacbf410/0fd0: 80 79 72 64 02 00 00 00-80 00 00 6a 02 00 00 00 .yrd.......j....
152:49:24.055459 00000000cacbf420/0fe0: 00 00 00 00 01 00 00 00-00 00 00 00 00 02 00 00 ................
152:49:24.055461 00000000cacbf430/0ff0: 00 00 00 00 00 00 00 00-b0 50 3e 44 02 00 00 00 .........P>D....
152:49:24.055462 00000000cacbf440/1000: 50 b2 49 6a 02 00 00 00-a9 57 92 18 fc 7f 00 00 P.Ij.....W......
152:49:24.055464 00000000cacbf450/1010: 10 f6 cb ca 00 00 00 00-b0 f5 cb ca 00 00 00 00 ................
152:49:24.055465 00000000cacbf460/1020: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055467 00000000cacbf470/1030: 00 00 f0 41 00 c0 45 44-00 00 80 3f 00 00 80 3f ...A..ED...?...?
152:49:24.055469 00000000cacbf480/1040: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055473 00000000cacbf490/1050: 28 31 00 6a 02 00 00 00-00 00 80 3f 00 00 80 3f (1.j.......?...?
152:49:24.055488 00000000cacbf4a0/1060: 00 00 00 00 00 c0 45 44-00 00 00 00 00 00 00 00 ......ED........
152:49:24.055490 00000000cacbf4b0/1070: 00 00 00 00 00 00 00 00-00 00 80 3f 00 00 80 3f ...........?...?
152:49:24.055491 00000000cacbf4c0/1080: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055493 00000000cacbf4d0/1090: 32 ac a9 1f bb e0 00 00-00 00 00 00 00 00 00 00 2...............
152:49:24.055497 00000000cacbf4e0/10a0: d2 ab a9 1f bb e0 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055500 00000000cacbf4f0/10b0: 00 00 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055504 00000000cacbf500/10c0: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055509 00000000cacbf510/10d0: 04 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055512 00000000cacbf520/10e0: 30 f6 cb ca 00 00 00 00-00 da 9a 18 fc 7f 00 00 0...............
152:49:24.055519 00000000cacbf530/10f0: 80 00 00 6a 02 00 00 00-28 f7 cb ca 00 00 00 00 ...j....(.......
152:49:24.055523 00000000cacbf540/1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055526 00000000cacbf550/1110: 00 00 00 00 00 00 00 00-40 f8 95 18 fc 7f 00 00 ........@.......
152:49:24.055529 00000000cacbf560/1120: 00 00 00 00 00 00 00 00-68 95 d0 cb 00 00 00 00 ........h.......
152:49:24.055533 00000000cacbf570/1130: 01 00 00 00 01 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055536 00000000cacbf580/1140: 80 00 00 6a 02 00 00 00-df 06 97 18 fc 7f 00 00 ...j............
152:49:24.055540 00000000cacbf590/1150: 00 00 00 00 02 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055543 00000000cacbf5a0/1160: 80 4b 6c 64 02 00 00 00-b0 50 3e 44 02 00 00 00 .Kld.....P>D....
152:49:24.055546 00000000cacbf5b0/1170: b0 50 3e 44 02 00 00 00-00 00 00 00 00 00 00 00 .P>D............
152:49:24.055549 00000000cacbf5c0/1180: 00 00 00 00 00 00 00 00-00 f6 cb ca 00 00 00 00 ................
152:49:24.055553 00000000cacbf5d0/1190: 80 4b 6c 64 02 00 00 00-00 00 00 00 00 00 00 00 .Kld............
152:49:24.055556 00000000cacbf5e0/11a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055560 00000000cacbf5f0/11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055563 00000000cacbf600/11c0: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055564 00000000cacbf610/11d0: 00 00 00 00 00 00 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055566 00000000cacbf620/11e0: 70 07 00 6a 02 00 00 00-03 00 00 00 00 00 00 00 p..j............
152:49:24.055568 00000000cacbf630/11f0: 00 00 00 00 00 00 00 00-b0 4b ef 7b 00 00 00 00 .........K.{....
152:49:24.055569 00000000cacbf640/1200: b8 0b 00 00 00 00 00 00-ed 1b 91 18 fc 7f 00 00 ................
152:49:24.055571 00000000cacbf650/1210: b0 4b ef 7b 00 00 00 00-00 00 00 00 00 00 00 00 .K.{............
152:49:24.055573 00000000cacbf660/1220: 04 00 00 7a 00 00 00 01-01 00 00 00 00 00 00 00 ...z............
152:49:24.055574 00000000cacbf670/1230: 00 00 00 00 00 00 00 00-04 00 00 7a 98 04 00 01 ...........z....
152:49:24.055576 00000000cacbf680/1240: 60 00 00 00 00 00 00 00-5c 99 dc cb 00 00 00 00 `.......\.......
152:49:24.055577 00000000cacbf690/1250: 00 00 8e 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055579 00000000cacbf6a0/1260: 80 00 00 6a 02 00 00 00-79 3a 8f 18 fc 7f 00 00 ...j....y:......
152:49:24.055580 00000000cacbf6b0/1270: b0 4b ef 7b 00 00 00 00-04 00 00 00 00 00 00 00 .K.{............
152:49:24.055582 00000000cacbf6c0/1280: d8 65 91 26 02 00 00 00-38 cf 8a 19 02 00 00 00 .e.&....8.......
152:49:24.055583 00000000cacbf6d0/1290: a0 f7 cb ca 00 00 00 00-7c 91 92 18 fc 7f 00 00 ........|.......
152:49:24.055585 00000000cacbf6e0/12a0: 04 00 00 00 00 00 00 00-04 00 00 00 00 00 00 00 ................
152:49:24.055586 00000000cacbf6f0/12b0: 80 00 00 6a 02 00 00 00-17 53 90 18 fc 7f 00 00 ...j.....S......
152:49:24.055591 00000000cacbf700/12c0: 88 14 00 6a 02 00 00 00-6f 7e 92 18 fc 7f 00 00 ...j....o~......
152:49:24.055593 00000000cacbf710/12d0: 80 00 00 6a 02 00 00 00-80 00 00 6a 02 00 00 00 ...j.......j....
152:49:24.055594 00000000cacbf720/12e0: 98 14 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055596 00000000cacbf730/12f0: f0 43 3e 44 02 00 00 00-88 14 00 6a 02 00 00 00 .C>D.......j....
152:49:24.055598 00000000cacbf740/1300: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055599 00000000cacbf750/1310: 5c 99 dc cb 00 00 00 00-d0 95 dc cb 00 00 00 00 \...............
152:49:24.055601 00000000cacbf760/1320: 01 00 00 00 00 00 00 00-60 90 d0 cb 00 00 00 00 ........`.......
152:49:24.055602 00000000cacbf770/1330: 8c 03 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055604 00000000cacbf780/1340: 00 00 00 00 00 00 00 00-c6 53 b7 18 fc 7f 00 00 .........S......
152:49:24.055605 00000000cacbf790/1350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055607 00000000cacbf7a0/1360: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055608 00000000cacbf7b0/1370: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055610 **************** ****  <ditto x 2>
152:49:24.055610 00000000cacbf7e0/13a0: 01 00 00 00 00 00 00 00-a3 4f b7 18 fc 7f 00 00 .........O......
152:49:24.055612 00000000cacbf7f0/13b0: 60 90 d0 cb 00 00 00 00-00 00 00 00 00 00 00 00 `...............
152:49:24.055614 00000000cacbf800/13c0: 00 00 a4 18 fc 7f 00 00-1c 19 00 00 00 00 00 00 ................
152:49:24.055615 00000000cacbf810/13d0: 00 00 00 00 00 00 00 00-d4 7b 32 56 fc 7f 00 00 .........{2V....
152:49:24.055617 00000000cacbf820/13e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055618 00000000cacbf830/13f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055620 00000000cacbf840/1400: 00 00 00 00 00 00 00 00-51 ce ba 56 fc 7f 00 00 ........Q..V....
152:49:24.055621 00000000cacbf850/1410: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055623 **************** ****  <ditto x 2>
152:49:24.055623 00000000cacbf880/1440: 00 00 00 00 1e 91 8b 62-00 00 00 00 00 00 00 00 .......b........
152:49:24.055625 00000000cacbf890/1450: 00 00 00 00 00 00 00 00-c0 06 5f 54 fc 7f 00 00 .........._T....
152:49:24.055626 00000000cacbf8a0/1460: 40 e6 cb ca 00 00 00 00-f0 ff 01 00 78 5f 52 db @...........x_R.
152:49:24.055628 00000000cacbf8b0/1470: de 97 d4 36 fc 7f 00 00-40 e6 cb ca 00 00 00 00 ...6....@.......
152:49:24.055629 00000000cacbf8c0/1480: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055632 **************** ****  <ditto x 114>
152:49:24.055632 00000000cacbfff0/1bb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055881 Thread ID:   0000000000004184
152:49:24.055891 Thread name: <NULL>
152:49:24.055896 Thread IPRT: 0000000000000000
152:49:24.055901 
152:49:24.055901 Loaded Modules:
152:49:24.055901 Address range                    [*] Timestamp Path
152:49:24.055907 00007ff715f30000..00007ff716045fff   5f51ed66  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
152:49:24.055914 00007ffc56b40000..00007ffc56d2ffff   b5beef21  C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.055920 00007ffc56310000..00007ffc563c1fff   53a32b86  C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.055926 00007ffc544f0000..00007ffc54794fff   1b835a75  C:\WINDOWS\System32\KERNELBASE.dll
152:49:24.055932 00007ffc2f520000..00007ffc2f524fff   5f51ecdc  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
152:49:24.055937 00007ffc54410000..00007ffc5446bfff   ad0f5fb3  C:\WINDOWS\System32\Wintrust.dll
152:49:24.055943 00007ffc56560000..00007ffc565fdfff   f5bdefd7  C:\WINDOWS\System32\msvcrt.dll
152:49:24.055949 00007ffc53a90000..00007ffc53aa1fff   e4c2641f  C:\WINDOWS\System32\MSASN1.dll
152:49:24.055954 00007ffc548d0000..00007ffc54a18fff   0e128cc8  C:\WINDOWS\System32\CRYPT32.dll
152:49:24.055960 00007ffc547d0000..00007ffc548c9fff   32a6df9a  C:\WINDOWS\System32\ucrtbase.dll
152:49:24.055966 00007ffc55970000..00007ffc55a8ffff   ee94cb53  C:\WINDOWS\System32\RPCRT4.dll
152:49:24.055971 00007ffc547a0000..00007ffc547c5fff   b59ada57  C:\WINDOWS\System32\bcrypt.dll
152:49:24.055984 00007ffc54470000..00007ffc544effff   bf9ade76  C:\WINDOWS\System32\bcryptprimitives.dll
152:49:24.055990 00007ffc543f0000..00007ffc54406fff   a51023f1  C:\WINDOWS\System32\CRYPTSP.dll
152:49:24.055996 00007ffc526e0000..00007ffc52712fff   fa3c3542  C:\WINDOWS\system32\rsaenh.dll
152:49:24.056001 00007ffc52d40000..00007ffc52d4bfff   fef011a6  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
152:49:24.056007 00007ffc56540000..00007ffc5655cfff   13bffc39  C:\WINDOWS\System32\imagehlp.dll
152:49:24.056013 00007ffc54ce0000..00007ffc54d76fff   f222d51c  C:\WINDOWS\System32\sechost.dll
152:49:24.056018 00007ffc51900000..00007ffc51921fff   0ab6ed3a  C:\WINDOWS\SYSTEM32\gpapi.dll
152:49:24.056024 00007ffc53a60000..00007ffc53a82fff   ca538c5d  C:\WINDOWS\System32\profapi.dll
152:49:24.056030 00007ffc52240000..00007ffc5226efff   b35f039c  C:\WINDOWS\System32\cryptnet.dll
152:49:24.056049 00007ffc54d80000..00007ffc54e22fff   502aaa11  C:\WINDOWS\System32\advapi32.dll
152:49:24.056055 00007ffbfaab0000..00007ffbfb08ffff   5f51ed67  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
152:49:24.056061 00007ffc55880000..00007ffc558eefff   50866107  C:\WINDOWS\System32\WS2_32.dll
152:49:24.056066 00000000502b0000..0000000050381fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
152:49:24.056072 0000000050210000..00000000502a7fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
152:49:24.056077 00007ffbf6a50000..00007ffbf6c17fff   5f51ed81  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
152:49:24.056083 00007ffc550b0000..00007ffc55244fff   57629574  C:\WINDOWS\System32\USER32.dll
152:49:24.056088 00007ffc54bc0000..00007ffc54be0fff   5343f4fb  C:\WINDOWS\System32\win32u.dll
152:49:24.056093 00007ffc563d0000..00007ffc563f5fff   90b22122  C:\WINDOWS\System32\GDI32.dll
152:49:24.056098 00007ffc53ad0000..00007ffc53c65fff   7ea30dec  C:\WINDOWS\System32\gdi32full.dll
152:49:24.056104 00007ffc54a20000..00007ffc54abdfff   2085286c  C:\WINDOWS\System32\msvcp_win.dll
152:49:24.056109 00007ffc56600000..00007ffc56756fff   3340c819  C:\WINDOWS\System32\ole32.dll
152:49:24.056114 00007ffc567c0000..00007ffc56af4fff   8349657a  C:\WINDOWS\System32\combase.dll
152:49:24.056119 00007ffc557b0000..00007ffc55874fff   6ac977e7  C:\WINDOWS\System32\OLEAUT32.dll
152:49:24.056126 00007ffc25480000..00007ffc255d5fff   c7cf39ed  C:\WINDOWS\SYSTEM32\OPENGL32.dll
152:49:24.056132 00007ffbf8790000..00007ffbfaaa6fff   5f51ed79  C:\Program Files\Oracle\VirtualBox\UICommon.dll
152:49:24.056137 0000000077a90000..0000000077ff4fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
152:49:24.056142 00007ffc55a90000..00007ffc56176fff   37e737cc  C:\WINDOWS\System32\SHELL32.dll
152:49:24.056148 00007ffc54ac0000..00007ffc54b09fff   afaaabaa  C:\WINDOWS\System32\cfgmgr32.dll
152:49:24.056153 00007ffc54bf0000..00007ffc54c98fff   bd8b0e7d  C:\WINDOWS\System32\shcore.dll
152:49:24.056158 00007ffc53c70000..00007ffc543effff   a8db3b62  C:\WINDOWS\System32\windows.storage.dll
152:49:24.056163 00007ffc53a10000..00007ffc53a59fff   fdc4588a  C:\WINDOWS\System32\powrprof.dll
152:49:24.056169 00007ffc53a00000..00007ffc53a0ffff   a2ccd413  C:\WINDOWS\System32\UMPDC.dll
152:49:24.056174 00007ffc562b0000..00007ffc56301fff   f8807ba1  C:\WINDOWS\System32\shlwapi.dll
152:49:24.056179 00007ffc53ab0000..00007ffc53ac0fff   05bef372  C:\WINDOWS\System32\kernel.appcore.dll
152:49:24.056184 00007ffbf8190000..00007ffbf8786fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
152:49:24.056190 0000000077520000..0000000077a80fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
152:49:24.056195 00000000501b0000..0000000050203fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
152:49:24.056200 00007ffc4d690000..00007ffc4d6b3fff   d238be3c  C:\WINDOWS\SYSTEM32\WINMM.dll
152:49:24.056205 00007ffc25450000..00007ffc2547bfff   f93070ee  C:\WINDOWS\SYSTEM32\GLU32.dll
152:49:24.056211 00007ffc2ba80000..00007ffc2ba9afff   57b24d2b  C:\WINDOWS\SYSTEM32\MPR.dll
152:49:24.056216 00007ffc4d660000..00007ffc4d68cfff   d6bb9be2  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
152:49:24.056221 00007ffc51950000..00007ffc5196ffff   bc0e8e8e  C:\WINDOWS\SYSTEM32\dxcore.dll
152:49:24.056227 00007ffc54cb0000..00007ffc54cddfff   4be57136  C:\WINDOWS\System32\IMM32.DLL
152:49:24.056232 00007ffbf8060000..00007ffbf818dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
152:49:24.056237 00007ffc509e0000..00007ffc50a78fff   6eb90ac0  C:\WINDOWS\system32\uxtheme.dll
152:49:24.056242 00007ffc538e0000..00007ffc53904fff   dbb466d6  C:\WINDOWS\system32\userenv.dll
152:49:24.056248 00007ffc56200000..00007ffc562a1fff   9506208f  C:\WINDOWS\System32\clbcatq.dll
152:49:24.056253 00007ffbf7bb0000..00007ffbf7f6ffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
152:49:24.056258 00007ffbf7f70000..00007ffbf805efff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
152:49:24.056264 00007ffc56400000..00007ffc56534fff   8776e62f  C:\WINDOWS\System32\MSCTF.dll
152:49:24.056269 00007ffc26a40000..00007ffc26a79fff   5c8c75fa  C:\WINDOWS\system32\dataexchange.dll
152:49:24.056274 00007ffc4ca70000..00007ffc4cccafff   7e72d1cb  C:\WINDOWS\system32\d3d11.dll
152:49:24.056280 00007ffc4ccd0000..00007ffc4ceacfff   2ba0a53f  C:\WINDOWS\system32\dcomp.dll
152:49:24.056285 00007ffc51a10000..00007ffc51afafff   4029f10d  C:\WINDOWS\system32\dxgi.dll
152:49:24.056290 00007ffc50ad0000..00007ffc50d31fff   eeb9f7a6  C:\WINDOWS\system32\twinapi.appcore.dll
152:49:24.056296 00007ffc50f10000..00007ffc50f38fff   5be0eb17  C:\WINDOWS\system32\RMCLIENT.dll
152:49:24.056301 00007ffc41fd0000..00007ffc4206dfff   66a372e8  C:\WINDOWS\System32\TextInputFramework.dll
152:49:24.056306 00007ffc4a6f0000..00007ffc4aa19fff   d02b205d  C:\WINDOWS\System32\CoreUIComponents.dll
152:49:24.056312 00007ffc4ceb0000..00007ffc4cf83fff   99046ad7  C:\WINDOWS\System32\CoreMessaging.dll
152:49:24.056317 00007ffc53450000..00007ffc53480fff   d95e6299  C:\WINDOWS\SYSTEM32\ntmarta.dll
152:49:24.056322 00007ffc4b1d0000..00007ffc4b322fff   571c81a7  C:\WINDOWS\SYSTEM32\wintypes.dll
152:49:24.056327 00007ffc40a70000..00007ffc40d15fff   156c7509  C:\WINDOWS\System32\iertutil.dll
152:49:24.056333 00007ffc3e0f0000..00007ffc3e100fff   6e82a406  C:\WINDOWS\system32\wbem\wbemprox.dll
152:49:24.056339 00007ffc3eb30000..00007ffc3ebb3fff   6af5c06d  C:\WINDOWS\SYSTEM32\wbemcomn.dll
152:49:24.056345 00007ffc3d770000..00007ffc3d783fff   f9651a38  C:\WINDOWS\system32\wbem\wbemsvc.dll
152:49:24.056350 00007ffc3d890000..00007ffc3d990fff   65ead981  C:\WINDOWS\system32\wbem\fastprox.dll
152:49:24.056356 00007ffc33850000..00007ffc33864fff   b26a0aaf  C:\WINDOWS\System32\amsi.dll
152:49:24.056361 00007ffc31bd0000..00007ffc31c48fff   c930d9ac  C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2009.7-0\MpOav.dll
152:49:24.056367 00007ffc47f20000..00007ffc47f29fff   927b71e6  C:\WINDOWS\system32\version.dll
152:49:24.056372 00007ffbf66d0000..00007ffbf6a4dfff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
152:49:24.056378 00007ffc534b0000..00007ffc534bffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
152:49:24.056383 00007ffc534a0000..00007ffc534acfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
152:49:24.056389 00007ffbf5ce0000..00007ffbf66c5fff   5f51ef9a  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
152:49:24.056394 00007ffc55340000..00007ffc557affff   a7d94c0a  C:\WINDOWS\System32\SETUPAPI.dll
152:49:24.056400 00007ffbf7b40000..00007ffbf7ba6fff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
152:49:24.056405 00007ffbf5480000..00007ffbf5cdbfff   5f51ef98  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
152:49:24.056411 00007ffc52880000..00007ffc528b9fff   50afe730  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
152:49:24.056416 00007ffc2f500000..00007ffc2f513fff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
152:49:24.056421 00007ffc53490000..00007ffc5349bfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
152:49:24.056427 00007ffc14a70000..00007ffc14a7cfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
152:49:24.056433 00007ffc4b100000..00007ffc4b10afff   3f83c149  C:\WINDOWS\SYSTEM32\WINNSI.DLL
152:49:24.056438 00007ffc55960000..00007ffc55967fff   76a581c8  C:\WINDOWS\System32\NSI.dll
152:49:24.056443 00007ffc4ab20000..00007ffc4ab35fff   1c3a0614  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
152:49:24.056448 00007ffc4ab00000..00007ffc4ab1bfff   3c1facb4  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
152:49:24.056454 00007ffc528c0000..00007ffc5298afff   6d09021f  C:\WINDOWS\SYSTEM32\DNSAPI.dll
152:49:24.056459 00007ffc426e0000..00007ffc42751fff   1626851d  C:\WINDOWS\System32\MMDevApi.dll
152:49:24.056464 00007ffc537f0000..00007ffc53819fff   73cca382  C:\WINDOWS\System32\DEVOBJ.dll
152:49:24.056470 00007ffc1fa50000..00007ffc1fae8fff   0f4dfe70  C:\WINDOWS\System32\dsound.dll
152:49:24.056509 00007ffc3ff90000..00007ffc400ecfff   7e935799  C:\WINDOWS\System32\AUDIOSES.DLL
152:49:24.056523 00007ffc18d80000..00007ffc18dc3fff   2c6931f6  C:\WINDOWS\System32\wdmaud.drv
152:49:24.056536 00007ffc2f8c0000..00007ffc2f8c8fff   9b72df6f  C:\WINDOWS\SYSTEM32\ksuser.dll
152:49:24.056546 00007ffc4ad50000..00007ffc4ad59fff   f97bfee2  C:\WINDOWS\SYSTEM32\AVRT.dll
152:49:24.056555 00007ffc2e910000..00007ffc2e91cfff   4d3c7e92  C:\WINDOWS\System32\msacm32.drv
152:49:24.056564 00007ffc2ded0000..00007ffc2deebfff   6a4add8d  C:\WINDOWS\SYSTEM32\MSACM32.dll
152:49:24.056574 00007ffc2e730000..00007ffc2e739fff   5a70c191  C:\WINDOWS\System32\midimap.dll
152:49:24.056583 00007ffc18a40000..00007ffc18c06fff   c808fce5  C:\WINDOWS\system32\d3d9.dll
152:49:24.056592 00007ffc50e30000..00007ffc50e5cfff   7cd7bb0f  C:\WINDOWS\SYSTEM32\dwmapi.dll
152:49:24.056602 00007ffc188e0000..00007ffc18a3cfff*  5eb1b78e  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056615 00007ffc14fd0000..00007ffc188d8fff   5eb1b648  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igd9dxva64.dll
152:49:24.056630 00007ffc451c0000..00007ffc45363fff   5eb1b356  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdgmm64.dll
152:49:24.056643 00007ffc51e70000..00007ffc51e95fff   5eb1b301  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdinfo64.dll
152:49:24.056659 00007ffc42bb0000..00007ffc451b3fff   5eb1b815  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igc64.dll
152:49:24.056677 00007ffc4bba0000..00007ffc4bc8ffff   e593a459  C:\Windows\System32\PROPSYS.dll
152:49:24.056688 00007ffc52b70000..00007ffc52bd6fff   65b356bc  C:\WINDOWS\system32\mswsock.dll
152:49:24.056702 00007ffc50d40000..00007ffc50d53fff   c19b74f1  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
152:49:24.056713 
152:49:24.056713 Potential code addresses on the stack:
152:49:24.056719 Xcpt PC         : 00007ffc189728c2 - 0x000928c2 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056740 00000000cacbf588: 00007ffc189706df - 0x000906df bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056759 00000000cacbf618: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056770 00000000cacbf648: 00007ffc18911bed - 0x00031bed bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056777 00000000cacbf690: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056784 00000000cacbf6a8: 00007ffc188f3a79 - 0x00013a79 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056791 00000000cacbf6d8: 00007ffc1892917c - 0x0004917c bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056798 00000000cacbf6f8: 00007ffc18905317 - 0x00025317 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056804 00000000cacbf708: 00007ffc18927e6f - 0x00047e6f bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056813 00000000cacbf788: 00007ffc18b753c6 - 0x001353c6 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056820 00000000cacbf7e8: 00007ffc18b74fa3 - 0x00134fa3 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056829 00000000cacbf800: 00007ffc18a40000 - 0x00000000 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056836 00000000cacbf818: 00007ffc56327bd4 - 0x00017bd4 bytes into C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.056841 00000000cacbf848: 00007ffc56bace51 - 0x0006ce51 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.056860 00000000cacbf898: 00007ffc545f06c0 - 0x001006c0 bytes into C:\WINDOWS\System32\KERNELBASE.dll",paulcad
19981,"GNOME issue, Suspected but unsure",Windows,VirtualBox 6.1.14,2020-10-20T15:08:11Z,2020-10-20T15:08:11Z,2020-10-20T15:08:11Z,the vm will start but not get past the command line.,eryktyler26
19979,"Virtualbox 6.1.14 crashes on Windows 10 Home, 6.1.4 does not",Windows,VirtualBox 6.1.14,2020-10-18T16:58:38Z,2020-10-18T17:04:31Z,2020-10-18T17:04:31Z,"I've been using 6.1.4 about 10 hours a day for 6 months on my Windows 10 Pro laptop, without *any* crashes (ok maybe once once but I'm not going to complain, awesome software). Recently I got a new laptop with Windows 10 Home and installed VirtualBox 6.1.14. VM crashed several times and behaved strangely, like Firefox in the VM would crash, or after being in ""screensave"" mode then login would crash and once re-logged in my apps would be gone I would have to restart them, that kind of stuff. I tried a few things, like upgrading Windows 10 to Pro, turning off audio etc. But the only that worked was to rollback to VirtualBox 6.1.4. I did not try 6.1.6, 8, 10 or 12, but clearly a bug got introduced in one of those or in 6.1.14.  ",schollii
19743,Hardening rejects DLL because of expired certificate nvldumdx.dll,Windows,VirtualBox 6.1.10,2020-07-21T13:04:30Z,2020-10-18T10:05:42Z,2020-10-18T10:05:42Z,"Im using a Nvidia GTX960 video card and it seems like the driver loader dll gets rejected because of an expired certificate.

The thing is that nvldumdx.dll is signed 2 times:
1. by Nvidia SHA1  (expired cert, was valid from 2018-2019)
2. by Microsoft SHA256  (valid cert)

Since Nvidia releases the file like that, I assume it's ok that only one of the signatures is valid, which is the case. But VirtualBox complains about the expired cert in the hardening log and rejects the file.

(VBox and video drivers are both the most recent releases)

{{{
2bc0.d1c: supHardenedWinVerifyImageByHandle: -> -23033 (\Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll) WinVerifyTrust
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll: Certificate is not valid (ValidTime=2020-07-05T18:39:56.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll): rcNt=0xc0000190
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll'
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23033 (0xffffa607)) on \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):

}}}
",Peter B
19968,File transfers to / from guest corrupted,Windows,VirtualBox 6.1.14,2020-10-14T16:03:34Z,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
19947,Full Screen does not come up when using the latest version of Guest Additions,Windows,VirtualBox 6.1.14,2020-10-07T13:00:24Z,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
19943,"""Invalid Settings Detected"" System : Acceleration page",Windows,VirtualBox 6.1.14,2020-10-06T10:43:35Z,2020-10-06T10:43:35Z,2020-10-06T10:43:35Z,"I tried to use ""old"" machine (created in previous versions of virtualbox) with the actual Virtualbox 6.1.14. But I got a problem described by other people

https://www.reddit.com/r/virtualbox/comments/efffap/i_have_a_problem_invalid_settings_detected/

https://www.reddit.com/r/virtualbox/comments/eig7f4/invalid_settings_detected/


It looks like there was a checkbox ""Enable VT-x|AMD-V"" in Settings>System>Acceleration in 6.0.x linked to the ""Invalid Settings Detected"" alert.

And it looks like in 6.1.x the checkbox was removed but the requirement to unset it was left somehow. 
",jekka
14269,Error relaunching VirtualBox VM process: 5,Windows,VirtualBox 5.1.8,2015-07-13T18:47:55Z,2020-10-05T21:05:38Z,2020-10-05T21:05:38Z,Unable to run guest VM using latest OVM 5.0 release. See attached screenshot for details.,sombra
19940,Nested Virtualization makes guest os freeze,Windows,VirtualBox 6.1.14,2020-10-05T13:57:58Z,2020-10-05T13:57:58Z,2020-10-05T13:57:58Z,"I have the last version of virtualbox and I have Kali Linux virtual machine and I want to start android virtual machine on it and I have done the setup for everything and enabled Nested virtualization in virtualbox and installed kvm on guest os for acceleration but every time I try to start the emulator, It appears with the message:-


""Emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.""


and the guest os suddenly freezes totally and no longer responds.

My PC's CPU is Intel core I7-8750H (6 cores) and 16GB ram.
What is the problem? How can I solve it?",MINE
19922,Fedora 32 Workstation official ISO fails to install stating integrity problems,Windows,VirtualBox 6.1.14,2020-09-27T19:29:36Z,2020-09-27T19:29:36Z,2020-09-27T19:29:36Z,"I download https://torrent.fedoraproject.org/torrents/Fedora-Workstation-Live-x86_64-32.torrent from https://torrent.fedoraproject.org/ . While torrent guarantees file isn't corrupt, I also check the file per vendor instructions.

 sha256sum -c Fedora-Workstation-32-1.6-x86_64-CHECKSUM
Fedora-Workstation-Live-x86_64-32-1.6.iso: OK

When I try to install this specific image, its media check stops at exactly 4.8% and suggests not to use this image. If you ignore (e.g. disable check), it doesn't succeed booting anyway.

Today, I installed VMWare Workstation Player 16 and amazingly, very same ISO passed every test and installed fine. I think I may have triggered a Virtualbox (or windows?) bug.",Ilgaz
19920,/bin/ls: reading directory : Protocol error for asian fonts,Windows,VirtualBox 6.1.14,2020-09-26T09:37:26Z,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
19913,linux guest processes terminated after win10 host sleep,Windows,VirtualBox 6.1.14,2020-09-24T14:48:43Z,2020-09-24T14:48:43Z,2020-09-24T14:48:43Z,"(similar to https://www.virtualbox.org/ticket/19131)

Windows 10 1904 host
Ubuntu 20.04-LTS guest (created with 6.1.10 IIRC)
virtualbox-6.1.14 with 6.1.14 extension pack

situation occurs when host goes into sleep on its own (my power settings are set never to hibernate when on line power)

result:
- running apps and windows in guest are all exited
- docker containers are exited
- system uptime seems to be correct

in attached log, the situation likely occurred starting at ""07:39:12.135290"" as this delta from the log opened time corresponds to the time docker reports my container exited
",DanielH_
19911,Fresh VM always crashing due to RAM issue,Windows,VirtualBox 6.1.14,2020-09-23T08:31:44Z,2020-09-23T08:31:44Z,2020-09-23T08:31:44Z,"Hey,

recently I built a new computer with 16 GB of DDR4 ram, a Ryzen 7 3700X and a Nvidia RTX 2060 Super. On my old one I never experienced any problems with Virtualbox but now any new VM I create crashes right after I reboot it after installation (Every driver I can think of is up-to-date). 

Of course I will supply more information if you need any. Maybe the log files can already help a lot with this problem.

Thanks in advance

PT400C",PT400C
19899,Virtualbox 6.1.14 shared paper press and drag and drop don't work,Windows,VirtualBox 6.1.14,2020-09-18T19:04:32Z,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
19499,Wrong guest screen resolution with host using 1366x768,Windows,VirtualBox 6.1.6,2020-04-16T11:01:53Z,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
19887,frequently the app(VM VirtualBox) does not respond,Windows,VirtualBox 6.1.10,2020-09-13T04:35:10Z,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
19881,AltGr not working most of the time,Windows,VirtualBox 6.1.14,2020-09-10T16:11:59Z,2020-09-11T07:33:32Z,2020-09-11T07:33:32Z,"Setup is a Linux (nixos 20.03) VM on a Windows 10 laptop, usually with 2 screens attached. The VM gets 3 virtual screens.
Both host and guest use a german (qwertz) keyboard layout.

Most of the time, the AltGr key and with it many symbols are not working on the guest. According to xev pressing the key does not trigger anything at all.

Often, but not always, changing from one virtual display to another will make the AltGr key work for a few times before falling back to not doing anything at all.

Sometimes, when changing to another screen and beginning to type, the first letter will be greek and I don't even know how to type those deliberately (it's not AltGr+something).

There have been days where it worked the whole time but those are rare.

Turning automatic keyboard capturing off as some related incidents suggested as solution does not help.

Suspending (save execution state) and restarting does also not help reliably.


To me it seems as if somehow the modifier gets stuck or a wrong keycode is sent or it gets out of sync between host and guest or between the virtual screens?
I can't really find any 100% reliable way to trigger or fix this behaviour.


I'll gladly provide any additional info or perform tests that could help this issue.",Nervengift
5515,Builtin DHCP server does not pick up setting update once started,Windows,VirtualBox 3.0.12,2009-11-20T10:25:21Z,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
16221,After upgrading to 5.1.10 Network interface is not working enp0s3: Detected Tx Unit Hang,Windows,VirtualBox 5.1.10,2016-11-23T15:56:25Z,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
19853,Linux instalation during boot instalation ISO,Windows,VirtualBox 6.1.10,2020-09-03T11:01:37Z,2020-09-03T11:01:37Z,2020-09-03T11:01:37Z,critical error occured while running the virtual machine. The issue is probably related to windows ,jtach
19848,Ubuntu new installation not booting,Windows,VirtualBox 6.1.10,2020-08-31T20:18:24Z,2020-08-31T20:18:24Z,2020-08-31T20:18:24Z,Ubuntu 20.04.1 new installation not booting sometimes. Logs attached for two incidents.,009
15839,Attempting to output audio causes processes in guest to hang,Windows,VirtualBox 5.1.4,2016-08-21T15:37:52Z,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
19642,Virtualbox UI freezes after clicking VM in list and corresponding VM is not properly booting,Windows,VirtualBox 6.1.10,2020-06-07T10:29:01Z,2020-08-28T14:35:15Z,2020-08-28T14:35:15Z,"Observed behaviour:
--------------------

When I start the VM with ""vagrant up"" (while having Virtualbox GUI open), the VM is created and booted in Virtualbox. Then vagrant hangs at the point, when it tries to access the VM via SSH in order to configure the VM. At the same time in Virtualbox, when I click on the VM in the list, the GUI of Virtualbox freezes and does not unfreeze anymore. I need to end the Virtualbox Manager Process in Windows Task manager in order to make Virtualbox work again.
The Problem occurs with several Vagrant Boxes with recent Ubuntu versions (e.g. ubuntu/focal64, ubuntu/eoan64). It seems to work (at least most of the time) with older Ubuntu versions (e.g. ubuntu/trusty64).

I have the feeling that I experience problems with Virtualbox since upgrading Windows to 2004 (Spring 2020 Update) and/or enabling WSL2, but I cannot prove since I haven't used Virtualbox immediately before the upgrade / WSL 2 enabling.

Expected bahaviour:
-------------------

The Virtualbox GUI does not freeze when I click on the VM in the list of VMs and Vagrant is able to finish the prozess of configuring the VM.


Additional Information:
-----------------------

- Windows 10 Pro (2004, Spring 2020 Update)
- Windows Subsystem for Linux (WSL) 2 enabled 
- Virtualbox 6.1.10 r138449 (Qt5.6.2)
- Vagrant 2.2.9
- Vagrant Box: ubuntu/focal64, 20200605.1.0",chrizzzt
19589,Black screen after GUI login on Ubuntu with tools installed.,Windows,VirtualBox 6.1.6,2020-05-16T13:39:58Z,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
19837,Forwarded ports are blocked,Windows,VirtualBox 6.1.10,2020-08-27T13:42:17Z,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
19830,VB 6.1.12 Windows 10 host BSOD NDU.SYS,Windows,VirtualBox 6.1.10,2020-08-24T19:53:03Z,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
17515,VBoxManager gets into a bad state,Windows,VirtualBox 5.2.4,2018-01-31T21:28:23Z,2020-08-19T18:56:17Z,2020-08-19T18:56:17Z,"
simple repro on windows, foo.bat:


    set VBOX=""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe""

    :loop
    %VBOX% controlvm ""%1"" poweroff
    %VBOX% snapshot ""%1"" restorecurrent
    %VBOX% startvm ""%1""

    goto loop


this results in a bunch off issues, including:


VBoxManage.exe: error: The machine 'box' is already locked by a session (or being locked or unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp


VBoxManage.exe: error: Invalid machine state: PoweredOff (must be Running, Paused or Stuck)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: ""PowerDown(progress.asOutParam())"" at line 578 of file VBoxManageControlVM.cpp


and eventually it dies:

Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Snapshot operation failed
VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleSnapshot(struct HandlerArg *)"" at line 539 of file VBoxManageSnapshot.cpp
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp

at this point a full restart of all VBox processes is required.
",spongman
19809,Very bad latency numbers with more than 1 vCPU,Windows,VirtualBox 6.1.10,2020-08-12T23:22:25Z,2020-08-13T22:11:28Z,2020-08-13T22:11:28Z,"VirtualBox 6.1.12 verified on Win10 host (or openSUSE TW host), with Linux guests Ubuntu 16/18 or openSUSE TW.

Basically, I have distilled this down to a small perl script, that sleeps for 1ms for 1000 times.  Ideally, this would be 1000ms total -- but on real hardware, the script takes just a shade under 1100ms per iteration (perl overhead, etc), and when VirtualBox is behaving, about 1350-1425ms per iteration.

On real hardware, 100% of 1ms sleeps are <2ms.  When VirtualBox is behaving, 99% of 1ms sleeps are <2ms, and the upper bound is around 10-15ms for a few outliers.

The problem is when vCPU is 2+ ... the more added, the worse latency gets.  1ms sleeps start taking 100ms, 300ms, 500ms, occasionally even 900ms to return.",JasonM
18985,Appdata folder contents copied to host drives when dragging and dropping files from kali linux vm,Windows,VirtualBox 6.0.12,2019-10-05T21:58:29Z,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
19356,Copy and paste and drag and drop doesn't work,Windows,VirtualBox 6.1.4,2020-02-28T04:22:49Z,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
19799,Incorrect DHCP lease command output,Windows,VirtualBox 6.1.10,2020-08-07T07:18:51Z,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
19761,VirtualBox guest OpenWrt OS crashed when using the nmap to scan the wireless network through the USB port,Windows,VirtualBox 6.1.10,2020-07-25T06:04:07Z,2020-07-31T02:05:45Z,2020-07-31T02:05:45Z,"Guest OpenWrt OS crashed with the following configuration and operation
Host is the Lenovo ThinkCentre M920t desktop PC, WIN 10 professional OS.
The VirtualBox v6.1.12 with extension pack 6.1.12 is installed. 
The Guest OS is Linux 64bit(OpenWrt Lede 17.01). Using the MediaTek USB wifi dongle MT7601U to act as a AP(AccessPoint). It works well, I can connct it by my mobile phone and surf the Internet without problem, but it will be crashed once I use the nmap(v7.31) to scan the wifi network. I have the exactly same configuration with my HP laptop and the sympton won't happen in it, don't why it's crashed with my Lenovo desktop PC.",MercyLin
19781,DMI Handle is not unique,Windows,VirtualBox 6.1.8,2020-07-30T13:42:09Z,2020-07-30T13:42:09Z,2020-07-30T13:42:09Z,"I have been having issues with the DMI on VirtualBox.

When I run dmidecode on Ubuntu 18.04, there are 2 entries for Handle 0x0008.
When python's py-dmidecode runs, it loops through the DMI and the contents of the second entry for Handle 0x0008 replace the previous entry, causing it's output to be invalid.

I think the Handle entries should be unique.

I have attached a copy of my dmi output with the above issue (0x0008 listed twice).",MattRobinson
19773,Cannot see Host Only Adapter in Windows 10 adapters,Windows,VirtualBox 6.1.10,2020-07-28T08:51:40Z,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
19754,Cannot use VM due to Guru Meditation Error,Windows,VirtualBox 6.1.10,2020-07-23T09:16:33Z,2020-07-24T07:48:08Z,2020-07-24T07:48:08Z,"when starting a VM it asks me to choose from four options: ubuntu, advances options for ubuntu and two memtests. In the logs the error shows as "" VCPU0: Guru Meditation -1149 (VERR_EM_INTERNAL_ERROR)"".
updated the version from 6.1.10 to 6.1.12 but the problem remains 

after creating new VMs also has the same error

",virgo
19752,Linux VMs are not running with MS Defender Application Guard,Windows,VirtualBox 6.1.10,2020-07-22T18:57:43Z,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
19744,Critical Error,Windows,VirtualBox 6.1.10,2020-07-21T19:42:00Z,2020-07-21T19:42:00Z,2020-07-21T19:42:00Z,Critical error ocurs while compiling with GCC. All my woes seems to have started after upgrading windows 10 (the host) to version 2004 and virtualbox to 6.1.12 r139181 (Qt5.6.2). I often also get program referenced illeegal memory at 0x000000 warra warra warra.,Tiaan
19738,Virtualbox aborting on resume,Windows,VirtualBox 6.1.10,2020-07-19T23:33:42Z,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
19725,my VM Centos 8 starting kicking me out,Windows,VirtualBox 6.1.10,2020-07-15T18:35:09Z,2020-07-15T18:49:56Z,2020-07-15T18:49:56Z,"This morning I  had a pop up to reboot my Window server for updates.

Before I rebooted Windows,  I went over to my Linux CentOS 8 VM and gracefully shut it down.

After it was completely down, I rebooted Windows.

After windows came backup, I started my Centos 8 VM,  it took a very long time to start, but eventually my sing on GUI was up, I was able to login and open a terminal and ran a few commands,  suddenly  it closed my terminal and went back to the sing on GUI.

I went to Oracle VM VirtualBox Manager, clicked on File, then clicked on Check for updates,  I received ""You are already running the most recent version..."". Since the version number did not show, I looked at Help - About VirtualBox - I was running 6.1.8.

I starting googling and found that the latest version is 6.1.12, so I downloaded and installed it.  I also install the latest extpack and the latest guest additions.

After the CentOS 8 reboot, I was able to login and work for about 15 minutes before it kicked me out again, back to the sign on GUI.

",Saca
19693,Failed to open a session the virtual machine in Win 7 Enterprise SP 1 64 Bit,Windows,VirtualBox 6.1.10,2020-07-02T04:10:29Z,2020-07-13T14:52:43Z,2020-07-13T14:52:43Z,"Dear all,

My windows:

Win 7 Enterprise 64 bit, SP1
Ram 8Gb
Virtualbox Latest ( 6.1.10 r138449 Qt5.6.2 )

when running to install Linux Mint, error show is below :

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


please fix this is.

note: All my virtual already installed, error same.. could not run and failed session.


Thanks
",n3wkid2019
19708,Memory Reference Error,Windows,VirtualBox 6.1.10,2020-07-08T21:04:33Z,2020-07-08T21:04:33Z,2020-07-08T21:04:33Z,"When running Ubuntu 20 (Linux Mint AND Budgie) I get a memory reference error.  Seems something is trying to write to 0x0000.

I've reproduced this in 6.1.9 and 6.1.10.  Host os is Windows 10.  HW is HP ZBook G5, 48GB RAM and 800+ GB disk.  ",grpark
19702,在开启了  Hyper-V  的  Windows 10 上运行  VirtualBox  虚拟机，会发生崩溃,Windows,VirtualBox 6.1.10,2020-07-04T08:56:06Z,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
19665,OpenWRT locks up early in the kernel sequence on 6.1,Windows,VirtualBox 6.1.10,2020-06-14T18:50:19Z,2020-06-27T15:31:19Z,2020-06-27T15:31:19Z,"Tried in latest(r128535) build same thing. Something to do with # of CPUs - console log from kernel looks different between 2 vCPU and 1, but locks up regardless.
I'll attach the log and vdi, as it's reasonably small. Just in case something is wrong there, the vdi was built via ""convertfromraw"" of sourced from https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/openwrt-19.07.3-x86-64-combined-ext4.img.gz, which is the latest released openwrt distro.

The image boots fine on hyper-V, vmware and physical.
",novitk
19676,Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel,Windows,VirtualBox 6.1.10,2020-06-20T12:35:32Z,2020-06-20T12:35:32Z,2020-06-20T12:35:32Z,"Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel
Video: https://youtu.be/MdocMGLR2_M
Restarting W/O crashes on Windows 95.
Bliss OS (Linux Android) Restarting Crashes.
Bottom Panel crashes on all systems and many Virtual Box versions (6.X.X) (MS-DOS,Linux,OS/2 e.t.c)",Danik2343
19675,DHCP server mac address conflicts with nat-host mac-address,Windows,VirtualBox 6.1.10,2020-06-19T19:56:40Z,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
19671,"VirtualBoxVM crash, rtR3WinUnhandledXcptFilter caught an exception",Windows,VirtualBox 6.1.10,2020-06-19T08:48:49Z,2020-06-19T08:48:49Z,2020-06-19T08:48:49Z,"At time VirtualBoxVM.exe crashes with a pop-up, ""The instruction at '0xXX' referenced memory at '0xXX'. The memory could not be read.

And this issue can be easily reproduced if I use Google chrome within VM.

Vbox is installed in Window 10 & Ubuntu 18.04 is installed Vbox.

Hereby I'm attaching the log file as well.",pearleye
19655,Linux guest crashes if VboxAdditions are installed,Windows,VirtualBox 6.1.10,2020-06-11T03:46:53Z,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
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,VirtualBox 6.1.10,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,,Universal007
19651,DNS not working with NAT on some networks.,Windows,VirtualBox 6.1.10,2020-06-09T12:39:59Z,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
19524,6.1.6 performance dreadful on VMSVGA and LinuxMint 18.2 VM on Windows 10 host,Windows,VirtualBox 6.1.6,2020-04-23T02:38:46Z,2020-05-28T20:13:00Z,2020-05-28T20:13:00Z,"I require VBoxSVGA with LinuxMint 18.2 running on a Windows 10 host.  Selection of VMSVGA causes a slow down of the entire VM, including disk access.  That's so weird.

",Trent
19629,VBox Fedora Linux Guest Additions 6.1.8 Client failed to get display change,Windows,VirtualBox 6.1.8,2020-05-28T17:25:27Z,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
19627,Gnome Terminal does not open on Linux guest after installing 6.1.8 GA,Windows,VirtualBox 6.1.8,2020-05-28T09:21:16Z,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
15050,Can not connect USB Stick to VM,Windows,VirtualBox 5.0.14,2016-01-20T10:45:10Z,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
19596,0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot,Windows,VirtualBox 6.1.8,2020-05-17T20:12:29Z,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
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,VirtualBox 6.1.8,2020-05-22T06:57:11Z,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
19599,[VM Crash] Cannot access memory at 0x00000...,Windows,VirtualBox 6.1.8,2020-05-18T16:02:11Z,2020-05-18T17:05:29Z,2020-05-18T17:05:29Z,"My Ubuntu VM will randomly decide to access an inaccessible memory address causing a panic and crash.

I haven't been able to nail this down to a specific event, it seems to happen randomly. If I can identify a reproducible event I'll update the report.",Chris Doherty
19585,Mouse buttons freezes when using remote desktop,Windows,VirtualBox 6.1.6,2020-05-14T23:13:16Z,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
19576,AssertLogRel F:\tinderbox\win-rel\src\VBox\Runtime\win\RTErrConvertFromWin32.cpp(448) int __cdecl RTErrConvertFromWin32(unsigned int): <NULL>  Unhandled error 1453,Windows,VirtualBox 6.1.4,2020-05-11T00:36:11Z,2020-05-11T00:36:11Z,2020-05-11T00:36:11Z,"VirtualBox 6.1.4 under host windows10, running linux guest crashed due to an assertion failure.
Unhandled error 1453.

VirtualBox was running while I was tinkering with the programs on the Windows 10 site when suddenly the PC froze [I think Windows 10 was executing binary dump of the virtualbox image for debugging.] then about a minute or so later, I got an error dialog about memory reference error or something, but I failed to capture the screen, but rely on the log file(s) instead.",ci-zephyurus
19573,Can not install Ubuntu 18.04 or 20.04 only 16.04,Windows,VirtualBox 6.1.6,2020-05-08T11:40:55Z,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
19548,VirtualBox freeze guest Ubuntu 18.04 if i add bridge or vlan,Windows,VirtualBox 6.1.6,2020-05-02T14:44:47Z,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
19438,Resize Screen crashes Everything,Windows,VirtualBox 6.1.4,2020-03-27T13:53:02Z,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
4605,Ubuntu Linux guest audio output slow and distorted,Windows,VirtualBox 3.0.2,2009-07-22T21:13:53Z,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
19522,VirtualBox does not recognize Windows 10 taskbar on the side,Windows,VirtualBox 6.1.6,2020-04-22T10:07:44Z,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
19461,App Error - Instruction at ... referenced memory at...,Windows,VirtualBox 6.1.4,2020-04-05T14:55:14Z,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
19363,Bidirectional support not working after 6.1.4 update in Linux Mint 19.1 or Ubuntu 14.04,Windows,VirtualBox 6.1.4,2020-02-29T03:21:44Z,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
18388,"""The instruction at 0x000000006BC88A90 referenced memory at 0x0000000000000008. The memory could not be read."" when trying to open Devices > Optical Drives",Windows,VirtualBox 5.2.26,2019-01-30T10:53:05Z,2020-04-05T11:30:06Z,2020-04-05T11:30:06Z,"Im using
Host: Windows 10 Pro 64 bit v1803
VB: VirtualBox 5.2.26r128414
Guest: Ubuntu 18.04

Getting the error consistently.",custard130
19456,VINF_EM_TRIPLE_FAULT when starting Ubuntu 16.04 on Win10 2004,Windows,VirtualBox 6.1.4,2020-04-02T12:00:21Z,2020-04-02T12:50:53Z,2020-04-02T12:50:53Z,"Win 10 2004 host, with Hyper-V enabled
VBox 6.1.4
Fresh Ubuntu Server 160406 64-bit install
Ubuntu boots and then ""hangs"" during the boot process
Intermittently, not always, it will throw a VINF_EM_TRIPLE_FAULT when this happens
Played around with various system / processor settings, no change. Reverted to defaults.",yorickdowne
19439,Resize Screen crashes Everything,Windows,VirtualBox 6.1.4,2020-03-27T13:53:09Z,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
19437,A critical error has occurred while running the virtual machine and the machine execution has been stopped.,Windows,VirtualBox 6.1.4,2020-03-27T13:11:03Z,2020-03-27T13:11:03Z,2020-03-27T13:11:03Z,"I am using windows10 64bit on UEFI pc desktop this error occured to me trying to use kali linux on virtual box i will attach my vbox.log and vbox.png 
i enabled virtualization , and installed the ext pack same version as the program and still can't make up what's is even the problem! , 
i can't figure any thing from the vbox.log so , any suggestions? ",DEV
19426,USB-to-Ethernet crash with Ubuntu guest and Windows 10 host,Windows,VirtualBox 6.1.4,2020-03-23T22:58:21Z,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
19419,"Guru Mediation - Cent Os 7, when i start a local ant build",Windows,VirtualBox 6.1.4,2020-03-21T10:23:48Z,2020-03-21T10:33:31Z,2020-03-21T10:33:31Z,Guru Meditation is coming very frequently. Please help me to resolve the issue,mariswamy
19416,random file system corrruption on Windows 10,Windows,VirtualBox 6.1.4,2020-03-20T15:59:35Z,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
19393,Virtualbox Linux Guest crashes when opening Eclipse IDE,Windows,VirtualBox 6.1.4,2020-03-11T07:57:30Z,2020-03-11T08:18:17Z,2020-03-11T08:18:17Z,"Hi,

if I open the Eclipse IDE under my Linux guest, then the guest crashes.

The guest is ArchLinux 64bit and the host Windows 10. I use the official Virtualbox guest extensions and kernel modules. The Linux Kernel of the guest is 5.5.8

I will attach the Logfiles",JMeier12
19382,Multiple Virtual Screen closes when changing a display,Windows,VirtualBox 6.1.2,2020-03-06T17:03:27Z,2020-03-06T17:06:26Z,2020-03-06T17:06:26Z,"I'm running Fedora 31 on Windows 10 with three monitors.
1. Dell XPS 15 (3840x2160 at 250% scaling which is recommended on Windows)
2. Dell Monitor (1920x1200 at 100% scaling)
3. Dell Monitor (1920x1200 at 100% scaling)
#2 and #3 are connected to XPS 15 via usb hub and daisy chained between #2 and #3.

These monitors are layout from left in above order.

I'm running the Fedora 31 using #2 and #3 monitors (so two virtual screens).

When I turn on the Auto-resize Guest Display option the second virtual screen crashes in a few operations.

Issue #1: When I drag and drop the second virtual screen window around above three monitors.  When I start the vm, the second virtual screen window appears in the monitor #1 (Dell XPS 15) and the first virtual screen windows appears in the monitor #2 (that is because I previously started in it).  I drag and drop the second virtual screen window to the monitor #3.  Then, the window blinks and planed in the monitor #1 and the windows is all grayed out.  Sometimes the window closes.  The first virtual screen window remains functional.

I can turn off the Auto-resize Guest Display options, and above issue does not happen.  After moving the second virtual screen window, I can turn on the option and use screens in the full screen mode.

Issue #2: After getting two virtual screens in the monitor #2 and #3 in the full screen mode.  The second virtual screen window closes if I getting out of the full screen mode.

There is the way around so not blocking issue, but this problem is annoying.",Takahiro
18285,Cannot paste copied Chromium URL into Windows,Windows,VirtualBox 6.0.0,2019-01-07T17:03:12Z,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
19338,Virtualbox randomly overwrote current state.,Windows,VirtualBox 6.0.4,2020-02-23T15:28:32Z,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
19328,Critical error pop up when starting machine,Windows,VirtualBox 6.1.2,2020-02-20T22:31:08Z,2020-02-20T22:31:08Z,2020-02-20T22:31:08Z,"When I try to load virtual machine after rebooting I get a pop up stating critical error and suggesting I post here with the logs. If it is relevant, Ubuntu had just performed updates.",tdsTPPS
19155,When shutting down guest. rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003b2c,Windows,VirtualBox 6.0.14,2019-12-13T12:39:25Z,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
19322,Unable to use text instalation of linux operating system with accessibility turned on in virtual box.,Windows,VirtualBox 6.1.2,2020-02-19T21:10:10Z,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
19308,"Networking mode ""NAT Network"" shows very poor throughput",Windows,VirtualBox 6.0.16,2020-02-13T12:47:40Z,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
18966,[VBoxSVGA with WDDM] Graphics corruption,Windows,VirtualBox 6.0.12,2019-09-26T06:51:59Z,2020-02-12T12:55:08Z,2020-02-12T12:55:08Z,"Corrupt display of various elements in GUI / dialog boxes when using VBoxSVGA and Aero in Windows 7 guest on Linux host.

No problem using VBoxVGA / WDDM.",Thomas S.
16382,Win10: VBoxSVC hangs when thunderbolt-to-USB is disconnected (PC undocked),Windows,VirtualBox 5.1.12,2017-01-12T18:52:03Z,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
19298,Frequent crash when suspending virtual machine,Windows,VirtualBox 6.1.2,2020-02-10T09:36:41Z,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
19294,Frequent crashing with The Instruction at 0x... referenced memory at 0x... The memory could not be read,Windows,VirtualBox 6.1.2,2020-02-06T15:51:02Z,2020-02-07T17:27:51Z,2020-02-07T17:27:51Z,"I have read many similar posts and tried the recommended fixes, but I am still having the issue. 

Host: Windows 10 pro, 16Gb ram, updated the video drivers
Guest: Ubuntu, 8Gb, 256Mb video mem

Seems to happen most frequently when I am running VSCode and click on any menu or context menu.

Attaching logs",tdsTPPS
19284,Error when opening vscode file menu,Windows,VirtualBox 6.1.2,2020-02-03T08:14:44Z,2020-02-03T08:46:38Z,2020-02-03T08:46:38Z,"
The instruction 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click OK to terminate the program""",china_liu
19282,Virtual Box Machine fails on startup,Windows,VirtualBox 6.1.2,2020-01-31T20:03:53Z,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
19283,VirtualBox stuck zoomed in on Windows 10,Windows,VirtualBox 6.0.16,2020-01-31T20:37:42Z,2020-01-31T20:37:42Z,2020-01-31T20:37:42Z,"Hello, 
I am running virtual box through vagrant on Windows 10. I cannot perform many functions on VirtualBox that I need to for school and work projects because the screen is zoomed in and I can't click or see many of the things I need to. I have tried some of the recommended fixes mentioned online at stackexchange and others but none have worked. Please let me know what I can do to make this work.

Thank you!",BallsMahoney
18943,High DPI support,Windows,VirtualBox 6.0.12,2019-09-18T14:13:53Z,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
19233,No recent-items jumplist on windows10,Windows,VirtualBox 6.1.2,2020-01-16T09:38:24Z,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
19238,Boot time for linux guest is about 50% slower on 6.1.2  compared to 5.2.34,Windows,VirtualBox 6.1.2,2020-01-16T19:53:21Z,2020-01-20T18:33:01Z,2020-01-20T18:33:01Z,"Host : Windows 10 1903 (10.0.18362.535)

I have been using linux mint 19.2 installed on Virtualbox 5.2.34 for a while.
I just recently upgraded virtualbox to the latest version 6.1.2.

The boot time on 5.2.34 is in average : 1.26  (1 minute and 26 seconds )
The boot time on 6.1.2  is in average : 2.13  (2 minutes and 13 seconds )",DanMc01
19242,vdi file destroyed,Windows,VirtualBox 6.0.14,2020-01-19T09:55:22Z,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
19215,Fedora 31 Workstation - Hang and Crash,Windows,VirtualBox 6.1.0,2020-01-09T21:43:16Z,2020-01-20T13:46:23Z,2020-01-20T13:46:23Z,"The  laptop lid was closed but the PC was still running and when I opened up the lid and tried to access the Fedora 31 Workstation VM, the UI didnt response to keyboard/mouse.   I tried to select from the menu ACPI Shutdown and there was no reponse and finally tried Input->Keyboard->Insert CTRL+ALT+DEL.  The VM started shutting down and crashed either coming back up.",Aquis7
19223,VirtualBox Extension Pack 6.0.16 installation failure,Windows,VirtualBox 6.0.14,2020-01-14T22:26:29Z,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
19123,VM Aborts On Laptop Suspend OR Machine Pause,Windows,VirtualBox 6.0.14,2019-12-02T12:53:20Z,2020-01-18T16:29:41Z,2020-01-18T16:29:41Z,"Hello,

Recently updated to 6.0.14 on Windows 10, hosting a Centos guest.

Two scenarios trigger a VM abort, maybe 50% of the time:
[1] pause VM (Machine -> Pause)
]2] send laptop to sleep

A dialog will pop up (immediately for [1]  and on resume for [2]).

Attaching logs and a screenshot of the dialog.

Cheers,
yato
",yato
19208,3d acecleration breaks VMSVGA,Windows,VirtualBox 6.0.14,2020-01-08T11:15:09Z,2020-01-16T10:33:20Z,2020-01-16T10:33:20Z,The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).,VincentX
19234,VBoxClient --clipboard terminates silently,Windows,VirtualBox 6.1.2,2020-01-16T09:44:09Z,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
19219,Serial port access via USB dropping lots of data...,Windows,VirtualBox 6.1.0,2020-01-12T12:51:34Z,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
19217,Mouse integration setting is not persistent,Windows,VirtualBox 6.1.0,2020-01-11T16:11:52Z,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
10844,Failed to attach the USB device to virtual machine,Windows,VirtualBox 4.1.18,2012-08-21T03:59:31Z,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
19216,"When installing Ubuntu with finnish language, can no see continue tab",Windows,VirtualBox 6.0.14,2020-01-10T09:49:10Z,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
19170,Oracle Linux 6 Fail Window Resize with VMSVGA,Windows,VirtualBox 6.0.14,2019-12-18T00:39:12Z,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
19179,VirtualBox Application Error,Windows,VirtualBox 6.1.0,2019-12-22T09:22:17Z,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
17104,5.1.28 Guest Additions Install fails with gnome-terminal 3.24.2,Windows,VirtualBox 5.1.28,2017-09-21T19:15:08Z,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
18874,Slowdown of X11 drawings in VBox 6.0.10 in comparison to 5.2.* series.,Windows,VirtualBox 6.0.10,2019-08-28T13:39:39Z,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
19139,Kali linux VM buggy cursor,Windows,VirtualBox 6.0.14,2019-12-09T07:14:33Z,2019-12-09T22:23:55Z,2019-12-09T22:23:55Z,"hello,
My problem is that the mouse integration bugs after a while on kali linux so i have to reebot all the time.
I still can move the cursor graphicaly but its position stays the same. I can click but always on the same spot. 
But when i deactivate the mouse integration option the cursor now disapear but moves.",FvckNorris
19125,Crashes with vmsvga,Windows,VirtualBox 6.0.14,2019-12-02T19:51:45Z,2019-12-09T06:51:32Z,2019-12-09T06:51:32Z,"Vm crashes if more than 128 megabytes of vram is issued to vmsvga graphical controller.
for example 129
I booted from https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/25/Workstation/i386/iso/Fedora-Workstation-netinst-i386-25-1.3.iso",kotenok2000
19124,Installing the guest additions on Ubuntu results in no display,Windows,VirtualBox 6.0.14,2019-12-02T16:25:39Z,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
19097,"""VirtualBox manager has stopped working"" when removing laptop from docking station",Windows,VirtualBox 6.0.14,2019-11-20T06:38:46Z,2019-11-20T06:49:34Z,2019-11-20T06:49:34Z,"When unddocking/docking my laptop (Fujitsu, Lifebook E Series) from the docking station the VirtualBox manager crashes with a dialog message: ""VirtualBox Manager has stopped working.

I'm running: Windows 10 x64 as host and have one virtual machine running at that time: ""Ubuntu 18.04.3 LTS"". This machine remains working, but the VM Manager is crasing. I followed the instructions to create a coredump which is attached.

My VM also crashes sometimes on dock/undock but here I need to gather more information and will file another ticket.

Expected behavior: Manger should not crash on dock/undock",martg
19055,Hang in VM after upgrade to 6.0.14,Windows,VirtualBox 6.0.14,2019-10-31T15:32:43Z,2019-10-31T15:38:58Z,2019-10-31T15:38:58Z,"My Ubuntu VM hangs after detecting the network card. This started after updating to 6.0.14, and has vanished when I stepped back to 6.0.12.
Network setup on the VM is Bridged to Intel Ethernet Connection (4)I219-V with Allow All and cable connected. ",hobson42
19040,ubuntu 16 guest aborted when restoring,Windows,VirtualBox 6.0.14,2019-10-23T01:03:01Z,2019-10-23T01:03:01Z,2019-10-23T01:03:01Z,"How to produce:
1. Open VirtualBox;
2. select the saved machine ""ubuntu-16"", and click ""start"" button;
3. New vm window comes up and then loading is processing;
4. when the progress bar almost finished the vm disappeared and aborted 

Host OS: Windows 7 SP1
I've been experienced this aborted situation since upgrade my virtualbox was upgraded to version 6, hope the information I've provided is helpful.",buffy
19035,Linux client can't use second monitor via Remote Desktop,Windows,VirtualBox 6.0.14,2019-10-21T10:15:07Z,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
19026,Windows sleep breaks network hotplugging,Windows,VirtualBox 6.0.12,2019-10-18T06:31:03Z,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
19013,VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2),Windows,VirtualBox 6.0.12,2019-10-13T21:50:45Z,2019-10-16T03:40:36Z,2019-10-16T03:40:36Z,"I am using VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2)  installed on windows 10 64 bit and my host oracle linux 6.6 x86_64.
here problem is view ( resizing windows is not working in full screen).

kindly ! provide me solution ",gaurav12
17962,Display after resize goes black,Windows,VirtualBox 5.2.18,2018-08-30T13:05:18Z,2019-10-10T01:54:06Z,2019-10-10T01:54:06Z,"Hi,

after resizing display it goes black and VM has to be restarted. VB is running on Win10 enterprise 64bit, guest system is Ubuntu.",Zool0
18973,BSOD (crash) on Windows 10 host with console Linux guest in network driver,Windows,VirtualBox 6.0.12,2019-09-29T08:18:40Z,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
18958,virtualbox 6.0.12 update doesn´t allow Fedora 30 VM start,Windows,VirtualBox 6.0.12,2019-09-23T12:52:01Z,2019-09-25T04:49:39Z,2019-09-25T04:49:39Z,"Vm perfectly running on windows with version from 5.x to ""6.0.10 r132072 (Qt5.6.2)"" after 6.0.12 update was not able to start the vm. On configuration were displayed some problems about ""unsupported hardware acceleration"".

A fast roll-back to previous 6.0.10 fixed the proble,m, but seems that 6.10.12 have some problem.
 
Test environment: Windows 10 pro, notebook fujitsu lifebook i7-8650U, 32Gb ram, sss, lan",Piero Gerletti
18946,Screenshot is causing the disk size update to fail,Windows,VirtualBox 6.0.12,2019-09-19T15:08:23Z,2019-09-23T15:49:09Z,2019-09-23T15:49:09Z,"Hi, 
I am running a host PC Windows 10. Using the virtualbox to launch a Cent OS. 
I was trying to update my disk size on the CentOS as i had reached 100% utilisation. So i used (as recommended by many sites to update this) below command:
{https://stackoverflow.com/questions/8141045/virtualbox-extend-partition
/mnt/c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe modifymedium CentOSVD.vdi --resize 120000}

Idea was to increase the vdi size from 60Gb to 120Gb. 
But after this command, it was not directly reflecting in the Cent OS after restart (also windows restart). The increased volume succeeded on windows side without any errors. But CentOS was not showing this. 
After a lot of debug i found that i had a snapshot stored somewhere on the PC and this was preventing the additional disk to be shown on the CentOS.  {lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 68.3G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part 
}
The sda partition was always showing 68.3G. Even though i increased the VDI to 120G, it was not reflecting here. Then i deleted the snapshot and then i saw the correct results. 
{ lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 117.2G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part }
So somehow the process in the snapshot is preventing the process of disk space update. Please check.
Steps to reproduce:
1. Run Virtual Box on a windows 10 machine. 
2. Install the Cent OS running as guest OS on Virtual Box. 
3. Check the VDI disk size (Virtual and actual size)
4. Take a snapshot (Ctrl + Shift + T). Notice another VDI file is created in another location
5. Increase VDI disk size with above command (VBoxManage.exe modifymedium)
6. Reboot both windows and VBox. 
7. Check the disk space on guest OS (CentOS) it will not show the increase
8. Delete Snapshot. Newly created VDI file is deleted from Step 4.
9. Reboot both windows and VBox. 
10. Check the disk space on guest OS (CentOS) it will show the increase",aanche
18940,"Smart hide, auto-hide, hot corners and etc.. not working",Windows,VirtualBox 6.0.10,2019-09-18T04:26:48Z,2019-09-20T16:50:19Z,2019-09-20T16:50:19Z,"Docks, top bars and title bars can be easily hidden by configuring the system from the settings or by downloading extensions. But none of them showing up when pointing/pushing/triggering their hot corners or places....",centaurusa
18950,clipboard stops working,Windows,VirtualBox 6.0.12,2019-09-20T07:07:09Z,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
12162,Serial Port output slows down VM,Windows,VirtualBox 4.2.18,2013-10-06T13:53:10Z,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
17485,"Crash 0xc0000005 after host suspend (Linux guest, Windows 7 host)",Windows,VirtualBox 5.2.6,2018-01-19T15:58:16Z,2019-09-12T12:38:50Z,2019-09-12T12:38:50Z,"Crash occurred twice for me.
{{{
03:20:07.990450 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001140!!!
03:20:07.990470 
03:20:07.990471 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fefb15be75
03:20:07.990477 ExceptionInformation[0]=0000000000000000
03:20:07.990482 ExceptionInformation[1]=0000000000000070
}}}
!VirtualBox show error message, then virtual machine become turned off.",ukolovda
16978,Windows 10: scan for hardware changes freezes after loading Virtual Box manager,Windows,VirtualBox 5.1.26,2017-08-03T21:53:05Z,2019-09-04T20:44:46Z,2019-09-04T20:44:46Z,"Windows 10 Pro
Virtual Box  5.1.26 r117224 (Qt5.6.2)

Restart windows 10
Open device manager
Action: Scan for Hardware Changes

The scan completes normally

Open the Virtual Box manager (doesn't matter if we run a session)
Close virtual box manager
Open device manager
Action: Scan for Hardware Changes

The scan never seems to complete.  The ""Scanning plug and play compliant hardware..."" dialog stays on screen.

Plugging in a new device (such as a USB device) does nothing.   It is not recognized by Windows.

Something happens to windows when the virtual box application is loaded.

",K1MGY
18886,"Virtual screen 2 crashes after update to virtualbox 6.0.10, but only when running ubuntu",Windows,VirtualBox 6.0.10,2019-08-31T00:10:05Z,2019-08-31T16:08:46Z,2019-08-31T16:08:46Z,"I usually run ubuntu 18.04 in a virtual box on a Windows 10 host and use two virtual screens, i.e. virtual screen 1 and virtual screen 2. Today I updated my virtualbox to 6.0.10. When I restarted the virtual machine with ubuntu, virtual screen 1 and virtual screen 2 opens as usual, see screen shot here: https://imgur.com/a/owwjNnL

Furthermore, I can move the windows with virtual screen 1 and virtual screen 2 around. However, when I try to go to full screen or to resize the windows, screen 2 closes/crashes. It is then impossible to restart it by choosing view->virtual screen 2 -> enable. 

To see where the problem lies I also installed ubuntu 19.04 and windows 10 in virtual machines. With ubuntu 19.04 I still got the same problem. But with the windows 10 virtual machine everything worked, even if the graphics of window is flickering a couple of seconds before adapting to the new size. What can I do?
",haggle
18877,binary in shared folder loses executable permission while running,Windows,VirtualBox 6.0.10,2019-08-29T07:36:41Z,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
18859,"Guest randomly crashes with ""The memory could not be read""",Windows,VirtualBox 6.0.10,2019-08-21T13:07:19Z,2019-08-21T19:15:03Z,2019-08-21T19:15:03Z,"I am running a Windows 10 1903 host and a Ubuntu 19.04 guest. The Ubuntu guest crashes fairly often with the attached dialog (see attached PNG file), warning of ""The memory could not be read.""

Both host and guest are using the latest patches. The guest has the current VMWare Extensions installed. The guest has 3D acceleration enabled.

Almost all of this guest OS's usage is for using Chromium browser to browse everyday sites, like Gmail, Facebook, CNN, etc. I feel it's fairly vanilla other than installing a few commodity apps like Chromium, GIMP, and Visual Studio Code.

The crash can happen when I am using nothing other than Chromium. In fact, just today, the crash happened less than 15 minutes after starting the VM. I attached log files from that crash.

Sometimes right-click context menus in Chromium go black. That is, you right-click on something, and the context menu that pops up is just a black rectangle. You can still click on things in that menu, but . I ''loosely'' correlate this to ""the VM is going to crash sooner than later"", but I am not sure there is a correlation. This morning, I did not notice the black context menus, although I do not think I invoked one.",Aren Cambre
18390,'memory could not be read' crash in Linux guest / Windows host 6.02 and 6.04,Windows,VirtualBox 6.0.4,2019-01-30T17:32:41Z,2019-08-21T13:09:11Z,2019-08-21T13:09:11Z,"I am running a Linux guest (Mint Virtualbox image downloaded from www.osboxes.org) in a Windows 10 host.

I started running this guest under VirtualBox 6.0.2 and experienced this crash. A couple of days later I noticed 6.0.4 was available and tried updating to that to see whether it had been fixed, but the crash is still occurring and has happened 3x today, so it is fairly regular.

The guest isn't running too much - it's being used as a dev box with Docker (postgres / pgAdmin) and VS Code. There doesn't seem to be a particular pattern in what I'm doing before a crash. The VM doesn't have many modifications to base settings - 2 CPU, bidir clipboard and 2 networks (NAT and Host Only).

The error message is:
'The instruction at 0x00007FFC612061E3 referenced memory at 0x00000000000010. The memory could not be read'

I have attached the output from VBoxBugReport",MattA
18839,Guest VMs will only start headless,Windows,VirtualBox 6.0.10,2019-08-15T22:06:46Z,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
18813,Linux installation fails when machine folder points to non-OS directory | Win 8.1 x64,Windows,VirtualBox 6.0.10,2019-08-05T09:20:35Z,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
18821,VirtualBox (VirtualVM.exe) crashes on Xubuntu 18.04 guest shutdown,Windows,VirtualBox 6.0.10,2019-08-08T11:18:44Z,2019-08-08T11:18:44Z,2019-08-08T11:18:44Z,"More often than not, my Xubuntu 18.04 guest OS does not shutdown cleanly. The host OS is running the latest version of Windows 10. A crash is raised in VirtualVM.exe. An example screenshot of the 'Application Error' is attached.

Attached are the following files:
* VBox Manager log
* Link (not actual attachment) to compressed, '''full''' crash dump (generated via Task Manager) - [https://drive.google.com/file/d/1CiOAs_8KejRZzMYjGd3UtA71kUOobv5a/view?usp=sharing Google Drive].
* Screenshot of application error raised by Windows. For the record, this screenshot does not (unfortunately) correspond to the attached crashdump.

I initially suspected the issue was related to Graphics acceleration, but I have disabled both 2d/3d but it has not changed the resulting behaviour.",zerodefect
18212,Windows 10 Host - Hardening error - VMs do not start,Windows,VirtualBox 6.0.0,2018-12-20T15:01:59Z,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
18804,VirtualBox Manager terminating without notice after start,Windows,VirtualBox 6.0.10,2019-08-02T08:58:57Z,2019-08-02T08:58:57Z,2019-08-02T08:58:57Z,"When I start the VirtualBox Manager, it briefly shows the selector window, then terminates without any notice. I have a single Linux VM in the list.",sgiesecke
18554,systemd startup script not updated during guest additions install,Windows,VirtualBox 6.0.4,2019-04-09T21:12:47Z,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
18794,"VM stopped scaling correctly ater update to 6.0.10 from 6,0,08",Windows,VirtualBox 6.0.10,2019-07-26T15:08:10Z,2019-07-26T17:57:20Z,2019-07-26T17:57:20Z,"Hi there 
I updated VMBox vom 6.0.8 to 6.0.10
this went well.- 
Then I started the Guest Cd 6.0.10 , after that the scaling of the desktop in the VM stoppend working. 
the size is set and is not changeable. 
I counter checked via a recent clone of the VM and there the scaling of the screen still works.-  
I am not sure what else I can give. please let me know.
cheers
   Me",Baros
18772,USB flash drive selection / addition causing crash or on removal,Windows,VirtualBox 6.0.10,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,"Intermittent, but fails enough to be extremely troublesome.",xlar54
18749,vbox VERR_BUFFER_OVERFLOW GTX 1650,Windows,VirtualBox 6.0.8,2019-07-09T01:50:10Z,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
18744,Virtualbox causes an abend Windows when it opens a Linux VM,Windows,VirtualBox 6.0.8,2019-07-05T14:24:23Z,2019-07-05T16:51:53Z,2019-07-05T16:51:53Z,"I Use Virtualbox since several years. My host is a Windows seven with 8 Go RAM. I tried several linux with success until some days. 
I had Linux Mint Plasma, Windows 10 as VM. Windows 10 works ithout problem. But when i tried to access Linux Mint, it abends Windows Seven. I get out Linux Mint from Virtualbox, and tried to re-install it. No success. Each try Abends Windows. 
I tried the Virtualbox 6.0.6 .... : same effects.

'''The message in Windows events is :
'''
Nom du journal :System
Source :       VBoxNetLwf
Date :         05/07/2019 16:08:37
ID de l’événement :12
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   Daniel-PC
Description :
Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf.
XML de l’événement :
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""VBoxNetLwf"" />
    <EventID Qualifiers=""49156"">12</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2019-07-05T14:08:37.444012300Z"" />
    <EventRecordID>794248</EventRecordID>
    <Channel>System</Channel>
    <Computer>Daniel-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\VBoxNetLwf</Data>
    <Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000BCAEC55CB4500000</Binary>
  </EventData>
</Event>

I Hope to understand this problem, and resolve it !
Thanks.",Speedycool
18736,attach two similar usb device always fail,Windows,VirtualBox 6.0.8,2019-07-02T10:55:38Z,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
18733,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Windows,VirtualBox 6.0.8,2019-07-01T09:46:33Z,2019-07-05T12:06:57Z,2019-07-05T12:06:57Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
18734,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Windows,VirtualBox 6.0.8,2019-07-01T09:46:42Z,2019-07-01T09:46:42Z,2019-07-01T09:46:42Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
18718,VBox crashes using 32 bit Linux guest on a 64 bit Windows 10 host,Windows,VirtualBox 6.0.8,2019-06-20T14:38:24Z,2019-06-22T17:04:28Z,2019-06-22T17:04:28Z,"I've created a virtual machine with a 32 bit Linux on a Windows 7 64 bit host.
Now I tried to use the same VDI disk file on a Windows 10 64 bit host computer.
But when I created a new virtual machine in the current Version of VirtualBox
using the existing VDI disk Image an exactly the same settings as on the
Windows 7 host the virtual machine crashes (""Guru Meditation"" - Fatal error)
immediately after selecting the GRUB boot options in the guest.

This problem could be fixed by choosing ""Linux 2.6 / 3.x / 4.x ('''64 bit''')"" as
the guest OS in the ""general settings"" for the virtual machine -- although the
Linux guest has only 32 bit (80386 32 bit ELF binaries).
",Martin_G
18715,Resolutions >= 4096px wide break VboxVGA and VboxSVGA,Windows,VirtualBox 6.0.8,2019-06-19T17:22:15Z,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
18707,Windows 1903 - Host Only Adapter - VM not starting,Windows,VirtualBox 6.0.8,2019-06-14T08:08:27Z,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
18696,Host-only interface does not support IPv6 NDP properly?,Windows,VirtualBox 6.0.8,2019-06-07T17:33:12Z,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
18614,Windows clipboard borked (regression),Windows,VirtualBox 6.0.6,2019-05-01T17:26:30Z,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
18623,Kernel modules doesn't build with linux kernel 4.4.176 on openSuse 42.3,Windows,VirtualBox 6.0.6,2019-05-06T08:14:19Z,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
18586,"After 18.04 LTS Ubuntu installation and reboot on VM with Windows7 32bit as host, the guest freezes after 1 min",Windows,VirtualBox 5.2.28,2019-04-20T16:59:40Z,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
18589,I am experiencing an issue starting my Windows 10 virtual machine,Windows,VirtualBox 6.0.6,2019-04-21T12:38:16Z,2019-04-21T12:38:16Z,2019-04-21T12:38:16Z,"I downloaded a windows 10 virtual machine from their website and extracted the VM, I imported the virtual machine using the default settings and I received the error in the picture, I have increased my RAM dedicated to the machine and given it higher processing power, I use many VM's but only experiencing the issue with this virtual machine.",Erynh777
18508,Re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset,Windows,VirtualBox 6.0.4,2019-03-19T17:40:12Z,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
18574,Enhancement Dual Screen Single Click activation,Windows,VirtualBox 6.0.6,2019-04-18T15:56:53Z,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
18565,"Windows 8.1 host, Linux Mint 19 Cinnamon guest, seamless mode: no menu bar, no host key",Windows,VirtualBox 6.0.6,2019-04-16T23:09:09Z,2019-04-17T09:36:27Z,2019-04-17T09:36:27Z,"On the lastest release of Virtual Box (6.0.6), and the one before that, I see the VirtualBox menu bar when booting Mint on my Windows 8.1 machine but, once Mint Cinnamon has finished booting, the menu bar disappears, seemingly never to return. Nor do the host keys (e.g. <host>+a) do anything. Thus, since I have the VM set to run in seamless mode, the only way to move outside the VM is to shut it down.

The version of Mint Cinnamon that I am booting is fairy vanilla: I have not customised it much or installed much software on it. It is running a 4.15 Linux kernel.

I do not seem to have the latest Guest Additions installed. I did, via Windows, download them and run them, but then my guest tells me they are not installed - and, it's the case that, because of the aforementioned problems, I cannot install them from within the guest.",JN
18538,Launching Firefox crashes VM with The memory could not be read.,Windows,VirtualBox 6.0.4,2019-04-02T23:36:48Z,2019-04-03T00:49:12Z,2019-04-03T00:49:12Z,"Installed Virtual Box 6.0.4 on Windows 10 1803 64 bit. Installed Red Hat Linux
6.10 Guest OS. 

After all the updates to Firefox and OS, launching the firefox
gives the message

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFBEA84E889 referenced memory at 0x000000000000001C. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------

Please fix this issue. 
",ketan
18531,Vbox 6.0.4 / HOST - Windows 10 ( 1809 ) / GUEST - Raspbian Stretch Kernal v4.14 / Surface Pro 6,Windows,VirtualBox 6.0.4,2019-03-29T21:38:24Z,2019-03-30T09:25:11Z,2019-03-30T09:25:11Z,"Bug noted regarding Mouse Visibility in reagrds to Virtual Machine Suspend as oposed to Shut Down.

Mouse integration on the Guest is Visible and Function upon Machine Startup.

If the machine is Shut Down ( Power off the machine ) then the mouse is Visible and Functional when restarted.

If the machine is Suspended ( Save the machine state ) then the mouse is Not Visible but Functional when restarted.

The condition is Repeatable and Consistent regardless of any changes in settings ( ie: PS2 Mouse vs Tablet ... )

NOTE: With the machine having been Resumed from a Suspended ( Saved State ) the mouse is visible on the host system and when hovering over the guest window. Once any region of the guest window is clicked on, then the mouse pointer disappears and only the effects of izems on the guest being hovered over is present. Mouse functionality is present, Only the Pointer is Not Visible.",ZAR
17376,unable to start vm: VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH,Windows,,2017-12-18T14:07:49Z,2019-03-28T09:33:28Z,2019-03-28T09:33:28Z,"I'm getting the following error again when trying to restore a saved machine. Same machine worked fine a couple of days ago.
No update or reinstall of VirtualBox in the meantime.

{{{
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)

Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)- Process Verification 
Failure: Executable file name and process image name does not match up.
}}}

After reinstalling VirtualBox by choosing ""repair"" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

VirtualBox: 5.2.3r119650

Host: Windows 10 64bits",rosch
18514,Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).,Windows,VirtualBox 6.0.4,2019-03-22T06:40:12Z,2019-03-24T03:45:44Z,2019-03-24T03:45:44Z,"Failed to open a session for the virtual machine Ubuntu.

Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",SChernolyas
18510,#GP when Windows guest driver tries to write X86_CR4_PCIDE in non-HyperV environment,Windows,VirtualBox 6.0.4,2019-03-21T01:13:34Z,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
18483,Failed to open session,Windows,VirtualBox 6.0.4,2019-03-09T19:56:15Z,2019-03-09T21:02:07Z,2019-03-09T21:02:07Z,"Hi!

I saved state of my virtual machine.
Sometimes I get error:
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
",SChernolyas
8760,VMDK: VERR_SHARING_VIOLATION,Windows,VirtualBox 4.0.6,2011-04-21T21:06:37Z,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
18445,Problem when starting my virtual machin,Windows,VirtualBox 5.2.18,2019-02-21T13:00:54Z,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
17583,VBoxControl guestproperty set fails with error VERR_PERMISSION_DENIED,Windows,VirtualBox 5.2.8,2018-03-02T22:57:29Z,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
18424,Host crashes when using VirtualBox,Windows,VirtualBox 5.2.26,2019-02-11T03:19:50Z,2019-02-11T03:19:50Z,2019-02-11T03:19:50Z,"The problem I have is that sometimes my host (Windows 10 laptop) crashes sometimes when I am using VirtualBox. This only happens if I close the laptop or if it goes to sleep while a VM is still running. 

Whenever the laptop goes to sleep while a VM is running, the host will shut down all applications and restart the computer. Occasionally, there will be a BSOD instead of the host just restarting. I was wondering if this is a common issue when users leave a VM running. The VM was Ubuntu 18 and the host was Windows 10.",mttwh
11758,"""Take Screenshot"" just makes black PNG ==> Fixed in SVN",Windows,VirtualBox 4.2.12,2013-04-26T15:04:10Z,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
18403,Linux Host and Windows guest both consume same input event (windows/action key),Windows,VirtualBox 6.0.4,2019-02-01T07:25:55Z,2019-02-07T09:08:40Z,2019-02-07T09:08:40Z,"Windows 10 Host
Linux Guest (Fedora 29 Workstation) 

Steps to reproduce:
Boot Fedora guest,
Press Windows Key

Observed behavior:
Windows start menu is opened and Gnome Activities is triggered at the same time

Expected behavior:
Only the guest receives the key event and the Gnome Activities is triggered without triggering the Windows start menu

Note:
This Problem did not exist in VirtualBox 5. ",nopaste
18417,USB thumb drive is persistent.  It does not disappear while removed,Windows,VirtualBox 6.0.4,2019-02-06T17:34:03Z,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
18353,Linux Mint 18.x VM Multimedia/Graphics Broken By 6.0.2 Guest Additions Install,Windows,VirtualBox 6.0.2,2019-01-23T14:22:47Z,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
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,VirtualBox 6.0.0,2018-12-22T03:20:08Z,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
18393,USB3 drive not recognized when connected to USB3 port,Windows,VirtualBox 5.1.24,2019-01-30T18:09:24Z,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
18348,VBoxGuestAdditions 6.0.2 failed with OpenArena game (ioquake3/renderer_opengl1_x86_64.so),Windows,VirtualBox 6.0.2,2019-01-22T14:29:14Z,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
17533,USB3.1 USB stick fails to enumerate,Windows,VirtualBox 5.2.6,2018-02-08T12:37:24Z,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
18384,Cursor disappears during Linux installation,Windows,VirtualBox 6.0.4,2019-01-29T10:20:20Z,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
18375,Red Hat Linux 7.6 VM kernel panic running under Windows 10 host,Windows,VirtualBox 6.0.2,2019-01-28T17:28:55Z,2019-01-28T17:28:55Z,2019-01-28T17:28:55Z,"When I try running a Red Hat 7.6 VM under Windows 10 using Oracle VirtualBox 6.0.0 or 6.0.2 I get a Kernel Panic.

If the guest is configured for Enable I/O APIC unchecked and so 1 CPU I get a panic in: __native_set_fixmap
If the guest is configured for 4 CPUs I get a panic in: __lookup_address_in_pgd

I have Hyper-V disabled in Windows Features. I have Windows Hypervisor Platform enabled (as without that I get errors reported in my VirtualBox config and can't even get the VM to start).

Prior to a reboot on Jan 17th 2019 I'd not had a problem. After the reboot Windows Hypervisor Platform was disabled and that stopped the VM running at all. When I enabled that setting I got the kernel panic. I tried reinstalling the Red Hat 7.6 VM, but that also suffered from the kernel panic during the install.

Between the previous reboot and the Jan 17th reboot the only things installed on my machine were:

* Dell SupportAssistAgent 3.1.0.142
* Adobe Acrobat Reader DC (19.101.20069) 

I tried uninstalling the Dell utility. However it did not resolve the issue.


Attached is a log from a startup with 4 CPUs.",David Castell
16936,Snapshot Deletion of Encrypted VM always corrupts filesystem,Windows,VirtualBox 5.1.24,2017-07-22T16:27:41Z,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
15752,Failed to open a session for the virtual machine,Windows,VirtualBox 5.1.2,2016-08-05T15:42:22Z,2019-01-19T21:31:44Z,2019-01-19T21:31:44Z,"Fresh install of Windows 10.
Fresh install of VB 5.1.2
Created a default Ubuntu x64 VM using Ubuntu 16.04 .iso
When I try to start the VM I get the following error:

''Failed to open a session for the virtual machine Xerus.

The virtual machine 'Xerus' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\brad\VirtualBox VMs\Xerus\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
''

I have created a default Win7 VM and get the same result when trying to start it.
",slattdog
18320,Virtual Hard Disk wizard defaults to file size less than recommended for Ubuntu 18,Windows,VirtualBox 6.0.0,2019-01-17T00:28:43Z,2019-01-19T20:51:09Z,2019-01-19T20:51:09Z,"Using VirtualBox 6.0.0 r127566 (Qt5.6.2) on host Windows 7 SP1 amd64.

I am creating a new VM using the GUI wizard. The Create Virtual Machine wizard detects I am intending to install Ubuntu and set the ""Version"" to ""Ubuntu (64-bit)"". The Virtual Hard Disk wizard defaults to a 10GB hard disk.

The download page for Ubuntu 18 (Desktop) at https://www.ubuntu.com/download/desktop suggests 25Gb of free hard drive space.

",Adam Piggott
14102,Kubuntu 15.04 Guest: 3D acceleration broken,Windows,VirtualBox 4.3.26,2015-05-08T16:01:54Z,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
18310,Can't change display settings in an Oracle Linux 6.5 guest,Windows,VirtualBox 6.0.0,2019-01-14T07:42:32Z,2019-01-14T08:37:37Z,2019-01-14T08:37:37Z,"I recently updated to v 6.0.0 r 127566 on Windows 10. All other guests (Debian Linux distros & earlier Windows versions) work fine, except Oracle Linux 6.5. Display becomes garbled when trying to change the resolution after installing the Guest Addition.",whosnick
18302,Can not install VirtualBox Guest Additions in CentOS 6.10,Windows,VirtualBox 6.0.0,2019-01-11T18:10:19Z,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
18253,"Windows10 sleep, wake up, VirtualBox(V6.0.0) display: abnormal exit.",Windows,VirtualBox 6.0.0,2018-12-31T12:14:04Z,2019-01-07T05:10:39Z,2019-01-07T05:10:39Z,"Host Machine System: Windows10 1809
Virtual Machine System: CentOS7.0
Virtual machine running, and then wait 10 minutes not to use Windows system, then Win sleep... Then, wake up Windows, VirtualBox shows: abnormal exit.",solan
18260,Not able to Start VM in Virtual Box when Bridge Adapter Network Setting is Selected After latest update to Windows 10,Windows,VirtualBox 6.0.0,2019-01-01T07:40:50Z,2019-01-05T15:27:30Z,2019-01-05T15:27:30Z,"Hi Team,

I am Not able to start VM on virtual box when Bridge Adapter Network Setting is Selected and This is seen after latest update to Windows 10.

Have tried all the possible solutions listed in google, Nothing Worked.

Have tried 5.2.18, 5.2.22 and also 6.0 versions of VB but observing same Error on all these version.

Below Error is Observed:

Failed to open a session for the virtual machine .

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Linda
18251,Unable to mount shared windows folder to Linux via VirtualBox,Windows,VirtualBox 5.2.20,2018-12-30T17:54:34Z,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
18229,CentOS VM does not start after virtual guest additions 5.2.22 upgradation,Windows,VirtualBox 5.2.22,2018-12-24T07:43:04Z,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
18231,unable to see mouse pointer in guest,Windows,VirtualBox 6.0.0,2018-12-24T21:56:53Z,2018-12-24T21:56:53Z,2018-12-24T21:56:53Z,,kapstone
18209,Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox,Windows,VirtualBox 6.0.0,2018-12-20T11:22:46Z,2018-12-20T11:25:32Z,2018-12-20T11:25:32Z,"Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox, and it does not report to guest system that this CPU supports AVX512 instruction sets. I tried to modify CPUID data for guest, but after doing so Linux guest was not able to boot, so looks that some extra support on VBox side it needed too.

VBoxManage.exe list hostcpuids
Host CPUIDs:

Leaf no.  EAX      EBX      ECX      EDX
00000000  00000016 756e6547 6c65746e 49656e69
00000001  00050654 04100800 7ffefbff bfebfbff
00000002  76036301 00f0b6ff 00000000 00c30000
00000003  00000000 00000000 00000000 00000000
00000004  1c004121 01c0003f 0000003f 00000000
00000005  00000040 00000040 00000003 00002020
00000006  00000ef5 00000002 00000009 00000000
00000007  00000000 d39ffffb 00000000 9c000000
00000008  00000000 00000000 00000000 00000000
00000009  00000000 00000000 00000000 00000000
0000000a  07300804 00000000 00000000 00000603
0000000b  00000001 00000001 00000100 00000004
0000000c  00000000 00000000 00000000 00000000
0000000d  000000ff 00000a80 00000a80 00000000
0000000e  00000000 00000000 00000000 00000000
0000000f  00000000 0000002f 00000000 00000002
00000010  00000000 0000000a 00000000 00000000
00000011  00000000 00000000 00000000 00000000
00000012  00000000 00000000 00000000 00000000
00000013  00000000 00000000 00000000 00000000
00000014  00000001 0000000f 00000007 00000000
00000015  00000002 000000f2 00000000 00000000
00000016  00000b54 00000b54 00000064 00000000
00000017  00000b54 00000b54 00000064 00000000
80000000  80000008 00000000 00000000 00000000
80000001  00000000 00000000 00000121 2c100800
80000002  65746e49 2952286c 6f655820 2952286e
80000003  322d5720 20323031 20555043 2e322040
80000004  48473039 0000007a 00000000 00000000
80000005  00000000 00000000 00000000 00000000
80000006  00000000 00000000 01006040 00000000
80000007  00000000 00000000 00000000 00000100
80000008  0000302e 00000000 00000000 00000000
80000009  00000b54 00000b54 00000064 00000000",SirZooro
18181,"Windows guest, Linux host: copying directories from host to guest copies top-level directories only, not contents",Windows,VirtualBox 5.2.22,2018-12-13T17:36:44Z,2018-12-13T18:25:21Z,2018-12-13T18:25:21Z,"Virtual Box test build 5.2.23
Host: Windows 8.1 x64
Guest: Linux Mint 19.1 x64 beta, Cinnamon.

Guest Additions installed. Bidirectional clipboard enabled.

Copying directory D1, with contents directory D2 and file F1, copies only D1.

The same setup, but with a Linux Mint 19.0 host, does not seem to have the problem.",JN
16075,"VBox ""draganddrop"" CPU Spike on Ubuntu Guest",Windows,VirtualBox 5.0.18,2016-10-17T19:06:54Z,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
18166,Ryzen 1700x - no 64 bit option,Windows,VirtualBox 5.2.22,2018-12-03T00:28:38Z,2018-12-03T05:56:39Z,2018-12-03T05:56:39Z,"Hello,
- I have windows 10
- I have a ryzen 1700X.
- SVM is enabled in the BIOS.
- HyperV is not installed.
VirtualBox won't let me chose a 64 bit option for guestn or even if i try 32bit it won't let me give it more than 1 core.
thanks for the help.",Wolfkiller
18164,FUll screen with VBox 5.2.22 on windows 7,Windows,VirtualBox 5.2.22,2018-12-02T16:15:47Z,2018-12-02T17:50:11Z,2018-12-02T17:50:11Z,"Hi,
I have been using fedora as guest system on windows 7 hosted VBox since years. Yesterday I upgraded from 5.2.18 to 5.2.22 and installed also the vbox additions for it under fedora 29 (linux 4.19).
As a result of this upgrade, suddenly full screen does not work, only normal window mode as well as the adaptive mode (Host-C) are working. Switching to full screen results in the screen freezing - reacting neither to mouse nor to keyboard.",TomKov
18163,Guest property LoggedInUsers does not work with 'wait' in VBoxManage,Windows,VirtualBox 5.2.22,2018-12-02T13:54:57Z,2018-12-02T17:47:06Z,2018-12-02T17:47:06Z,"To wait for a machine to be ready for logins I used

    vboxmanage guestproperty wait <machine> /VirtualBox/GuestProperty/OS/LoggedInUsers

At some point (before 5.2.22) that stopped working. You can still 'get' that property, and it is listed with 'enumerate' for a running <machine>.",thoni56
18160,Virtual Box machines fail to start after migration from Win7 to Win10,Windows,VirtualBox 5.2.22,2018-11-30T12:33:32Z,2018-11-30T14:31:46Z,2018-11-30T14:31:46Z,"I upgraded to Windows 10, turned off hyper-v, rebooted, etc.: I can create new 64bit machines, I can run rescue disk .iso in them but existing machines fail to start.",aivarsk
18130,VBoxGuestAdditions 5.2.22 3d acceleration not working,Windows,VirtualBox 5.2.22,2018-11-13T19:07:55Z,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
14484,Host-only adapter fails after sleep-wake transition,Windows,VirtualBox 5.0.2,2015-08-21T22:57:02Z,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
18029,NAT network UDP port forwarding not working,Windows,VirtualBox 5.2.18,2018-10-04T07:07:04Z,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
18136,Audio canceled strangely with virtualbox grater than 5.2.18.,Windows,VirtualBox 5.2.22,2018-11-18T00:17:29Z,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
18117,vboxsf filesystem doesn't handle no extension file name,Windows,VirtualBox 5.2.20,2018-11-08T20:33:06Z,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
18119,Linux Mint 19 freezes when resizing Window,Windows,VirtualBox 5.2.20,2018-11-10T14:14:49Z,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
17858,VBox Guest Additions make crash VM VB during take VM snapshots,Windows,VirtualBox 5.2.14,2018-07-05T18:46:11Z,2018-11-07T05:58:14Z,2018-11-07T05:58:14Z,"Hi All!

I have a VBox VM with Ubuntu 18.04 as guest on WIndows 10 Host. Before installing the VBox Guest Addition (VB GA) on Ubuntu VM, the VM snapshots all worked very well! But after installing it, all the snapshots that are made cause a crash of the same VM (they interrupt its functioning). In practice, the snapshot process stops and crashes as soon as it reaches 96% of the acquisition of the same. I need the VB GA to implement the shared network folder between guest and host.

In my opinion this is a bug of the VB GA.

  - What's the cause of this crash? Is it possible to fix it?

Thank you.

Greetings,

Lorenzo",Kowa92
18088,guest additions fail to compile against kernel 4.19,Windows,VirtualBox 5.2.20,2018-10-29T14:55:48Z,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
17354,Can't setup Host-Only Network Adapter on Windows 10 Client,Windows,VirtualBox 5.1.30,2017-12-06T18:20:42Z,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
18076,Linux Mint 19 guest using Touch Keyboard in Windows 10 host not working with some keys,Windows,VirtualBox 5.2.20,2018-10-24T13:17:02Z,2018-10-26T00:42:48Z,2018-10-26T00:42:48Z,"I am having problems with Windows 10 the full touch keyboard not the basic one with the arrow keys, Shift and space bar not working and it is in USB Tablet mode. The strange thing is that basic touch keyboard work with space bar, but arrow keys still not working.",Motoko
18082,still doesn't work copying and pasting some words with shift + insert,Windows,VirtualBox 5.1.38,2018-10-25T12:36:28Z,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
16818,VirtualBox Drag and drop failure on Windowd 10,Windows,VirtualBox 5.1.22,2017-06-06T20:09:30Z,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
18062,VirtualBox Application Error - memory could not be read,Windows,VirtualBox 5.2.20,2018-10-18T15:34:24Z,2018-10-18T15:34:24Z,2018-10-18T15:34:24Z,"Updated from 5.2.18 to 5.2.20 last night (with Guest Additions) and left for the day.  Since this morning, two similar crashes - the second is below and attached.  I've updated to Win10 Pro (1809) last week (from previous patch level).  Some additional information that I suspect as relevant ... Dell laptop with Dell D1000 USB3.0 Dock (DisplayLink driver).  Main video, Wired Internet, and USB is run through the dock.

The instruction at 0x00007FFF24DBD680 referenced memory at 0x0000000000000010. The memory could not be read.",Brewsters
18051,My screen is all discombobulated! SOS,Windows,VirtualBox 5.2.18,2018-10-14T03:28:28Z,2018-10-17T08:20:08Z,2018-10-17T08:20:08Z,"When I start my VM for Linux Mint, my laptop cant seem to get
the display right. All I can see is a bunch of lines that seem
to make up my screensaver and I see my mouse divided into approx.
12 different slices along the lines that seem to make up my 
screensaver. I use the VM as a programming environment for my 
CS class and I have project due tomorrow but can't get it to run
so I can add the finishing touches... Please help. I would add a
pic if a knew how
",Diddy
18041,guest suse leap 15.0 could not be started after kernel update openSUSE-2018-1140,Windows,VirtualBox 5.2.18,2018-10-10T09:09:19Z,2018-10-17T08:11:08Z,2018-10-17T08:11:08Z,"With VirtualBox 5.2.18r on a Windows 10 host my Open Suse Leap Linux updated
the kernel with openSUSE-2018-1140 and from then on the suse guest couldn't be
started again.
Attached you'll find a hardcopy of the Startup sequence Messages.

An native Installation of Suse, including the kernel 4.12.14.lp150.12.19, 
works w/o any issues.",guenni
18045,glGetFramebufferAttachmentParameter missing in libGL.so.1,Windows,VirtualBox 5.2.18,2018-10-11T14:00:21Z,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
18002,Heap corruption in VBoxSVC.exe leading to a crash (possibly due to double free),Windows,VirtualBox 5.2.18,2018-09-22T14:47:11Z,2018-10-08T14:28:45Z,2018-10-08T14:28:45Z,"I have encountered a crash of latest VBoxSVC.exe 5.2.18.24319 on a Windows 10 host while running two VMs in parallel (one Windows VM and one Linux VM). The crash happend while I was accessing internet resources from the Linux VM.

I have collected a crash dump which indicates that the crash is caused by a heap corruption in VBoxSVC.exe while calling free function from msvcr100.dll. So, this looks like a double-free issue in VBoxSVC.exe.

I could not find a way to reproduce this crash. Usually, I run 3 or 4 VMs at the same time but VBoxSVC never crashed but this time just with 2 VMs and no extensive CPU load (just internet browsing) and it crashed.

I'm attaching the full log from Linux machine. For the crash dump, I can post it but since it is related to potential double free issue in VBoxSVC which are sometime a security vulnerability I prefer to confirm with you first that it is ok to post here.

",idrassi
16192,Virtualbox Windows clipboard integration causes problems copying in Excel,Windows,VirtualBox 5.1.8,2016-11-17T10:28:15Z,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
17972,vboxsf module crashes guest OS after accessing host-side symlinks in shared folder,Windows,VirtualBox 5.2.18,2018-09-07T16:21:10Z,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
16753,Pen_Tablet.exe takes more and more memory when VM is on.,Windows,VirtualBox 5.1.22,2017-05-12T17:25:50Z,2018-09-06T19:28:55Z,2018-09-06T19:28:55Z,"Tablet is Wacom CTL-470.[[BR]]
Driver version 5.3.5-3 (newest for this tablet).[[BR]]
Memory leak occurs on host while VM is running and tablet is connected. Process name is Pen_Tablet.exe (Tablet service for consumer driver). The process gains around 20K memory every second.[[BR]]
Host is running Windows 10 build 15063.250 (Creators update).[[BR]]
Guest is Arch Linux.[[BR]]

",snow
17967,Shared Folders from Linux Guest VM not accessible,Windows,VirtualBox 5.2.18,2018-09-02T03:45:25Z,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
17953,supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll,Windows,VirtualBox 5.2.18,2018-08-23T21:16:34Z,2018-08-24T14:12:37Z,2018-08-24T14:12:37Z,"VM boot fails with following error in the VBoxHardening.log

768.1808: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Error (rc=0):

768.1808: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Fatal error:

768.1808: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\SHELL32.dll' / '\??\C:\Windows\system32\SHELL32.dll': 0xc0000190

1d50.15d4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1651 ms, the end);

1b18.ac8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2014 ms, the end);
",IvanP2017
17952,5.2.18 - Windows 10 Pro Host 64-bit only supports 32-bit OS.,Windows,VirtualBox 5.2.18,2018-08-23T02:53:36Z,2018-08-23T05:20:54Z,2018-08-23T05:20:54Z,"In Setting-General for Linux virtual machine, Type: Linux Version: only displays 32-bit OS.  Need 64-bit OS as in past.",BigAlKC
17948,Saving a Linux VM (Debian) crashes very often,Windows,VirtualBox 5.2.18,2018-08-22T15:49:52Z,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
16543,High CPU load with MP Linux 4.10 guest,Windows,VirtualBox 5.1.16,2017-03-09T09:21:48Z,2018-08-22T07:53:27Z,2018-08-22T07:53:27Z,"When a Linux 32-bit guest is configured with 2 processors and uses the 4.10 kernel, it loads 100% a host processor core.
It doesn't happen with kernel 4.9 and before.
It doesn't happen with a single guest processor.

During boot the message {{{smpboot: do_boot_cpu failed(-1) to wakeup CPU#1}}} appears.",Urmas
17739,Seamless mode not working with Fedora 28 guest,Windows,VirtualBox 5.2.10,2018-05-06T19:15:33Z,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
17883,Bridge adaptor removed when updating to 5.2.16,Windows,VirtualBox 5.2.16,2018-07-22T16:45:54Z,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
17881,Network in Bridged mode - Guest can't ping host,Windows,VirtualBox 5.2.16,2018-07-21T21:58:53Z,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
17877,RHEL 7.5 Guest Blank Login screen,Windows,VirtualBox 5.2.16,2018-07-20T06:54:19Z,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
17853,Sayign that Virtualisation is disabled when it is definitely enabled,Windows,VirtualBox 5.2.14,2018-07-03T16:54:53Z,2018-07-12T21:59:26Z,2018-07-12T21:59:26Z,"When i try to load a virtual machine i get the following error

    ''Failed to open a session for the virtual machine Linux.
    
    VT-x is not available (VERR_VMX_NO_VMX).
        
    Result Code: E_FAIL (0x80004005)
    Component: ConsoleWrap
    Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
''
This is also happening for my Windows 7 Virtual machine (Both machines are 64-bit)

I have checked all the the things i could think of, and anything that came up after a quick google search and all seems okay to me.

So far i have checked:

Virtualisation Enabled in BIOS - Yes ->(https://imgur.com/gallery/cxYxs7d)

Hyper-V disabled in Windows - Yes -> (https://imgur.com/gallery/rO8u0j9)

Windows sees that Virtualisation is enabled in the Task Manager ->(https://imgur.com/gallery/92A0Ebb)

I have tried enabled and disabling Hyper-V to no avail.
I have also tried with both VT-D enable and disabled - Yet it makes no difference",TheBritishBoi
17860,USB 3.1 support,Windows,VirtualBox 5.2.14,2018-07-09T11:44:14Z,2018-07-09T12:17:10Z,2018-07-09T12:17:10Z,"The usb camera that reports as USB 3.1 will not be recognized by Virtual box while every things working fine with USB 3.0 camera. 

I am not sure if anyone has already reported this. But I did not find any thing in google search.

I am using latest version of Virtual box 5.xx and USB extension package.  ",T1000
17856,Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1) (Hardening Issue while starting an image),Windows,VirtualBox 5.2.6,2018-07-04T12:43:41Z,2018-07-04T18:34:01Z,2018-07-04T18:34:01Z,"I am running Oracle Virtual Box 5.2.6 r120293 (Qt5.6.2) and I am trying to launch CentOS 7 gust image and see the error ""Error (rc=-5640)""

I am on Windows 10 [1709] 64-bit OS and x64-bit Processor.

I have tried most of the options that are mentioned in the link:

https://forums.virtualbox.org/viewtopic.php?f=25&t=82106

Can anyone help us if this is a bug or something that is coming from my environment.

I have attached the VBoXHardening.log",SarmaK
16454,VERR_ACCESS_DENIED when using raw disk on Windows 10 host,Windows,VirtualBox 5.1.14,2017-02-04T18:51:58Z,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
17816,Can't connect to on Linux guest from Windows via host-only network,Windows,VirtualBox 5.2.12,2018-06-12T11:20:47Z,2018-06-12T17:32:08Z,2018-06-12T17:32:08Z,"I have an Ubuntu VM that runs a MySQL server among other things. I connect to it from different host systems - macOS, Windows.

For some unknown reason the host system can no longer connect to the server (mysql says ""connection refused""). I'm connecting through a host-only network via 192.168.56.101. I can ping this IP address without problems.

I have no idea why it stopped working. I did not change any configuration. Deleting and re-creating the host-only network doesn't solve the issue. 

I'm not a networking expert, I have no knowledge of debugging this sort of issues. I was hoping that you could fix this bug.",szx
17815,Failed to save settings - Empty or null bridged interface name is not valid.,Windows,VirtualBox 5.2.12,2018-06-12T09:19:14Z,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
17804,Win10 and 7 host OracleEnterpriseLinux 6.7 guest addition clipboard and window resize does not work,Windows,VirtualBox 5.2.12,2018-06-05T20:46:33Z,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
17807,VM fails to start,Windows,VirtualBox 5.2.12,2018-06-06T18:55:20Z,2018-06-11T16:32:38Z,2018-06-11T16:32:38Z,"Running Version 5.1.14 r112924 (Qt5.6.2) on Windows 7 64bit, suddenly it fails to start with below error:

The virtual machine 'Oracle Linux 6.7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Virtual_Machines\Oracle Linux 6.7\Logs\VBoxHardening.log'.
",Abdelj
17789,Virtual computer failed to start,Windows,VirtualBox 5.2.8,2018-05-30T13:36:22Z,2018-05-30T14:21:39Z,2018-05-30T14:21:39Z,,zhangwei01
17785,Start Kali Linux,Windows,VirtualBox 5.2.12,2018-05-23T14:11:23Z,2018-05-23T16:25:01Z,2018-05-23T16:25:01Z,I installed kali linux virtual machine and the error occurs during startup,LucaFaggiani
17577,Unusable window system on Ubuntu 1204 guest using 5.2.8 or GA 5.2.7,Windows,VirtualBox 5.2.8,2018-02-28T22:51:03Z,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
17780,CentOS 7.5 Guest Additions not installing,Windows,VirtualBox 5.1.38,2018-05-21T15:54:38Z,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
17773,Distorted sound Host: Windows 10 Guest: Ubuntu 18.04,Windows,VirtualBox 5.2.12,2018-05-17T14:03:17Z,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
17729,Current GuestAdditions have problems with resolutions on CentOS 6.2 guests,Windows,VirtualBox 5.2.8,2018-05-04T11:24:12Z,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
17760,"can not start the vm and get the error ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""",Windows,VirtualBox 5.2.12,2018-05-12T22:19:42Z,2018-05-14T14:15:32Z,2018-05-14T14:15:32Z,"Hi,

I created a centos 7.4 virtual machine. After creating, it works ok under virtual box. However it randomly can not start and the log complains below error: 
VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

Attached please find the log file and the screenshot image. 

Thanks,
Shifeng",shzhang
17755,[guest additions] mouse laggy after unlock screen,Windows,VirtualBox 5.2.10,2018-05-11T06:56:04Z,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
17751,"""A critical error has occured while running the virtual machine and the machine execution has been stopped.""",Windows,VirtualBox 5.2.12,2018-05-10T17:19:51Z,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
17723,VirtualBox cannot catch USB devices if RemoteFX USB Redirection enabled,Windows,VirtualBox 5.2.10,2018-05-01T19:59:38Z,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
17734,Error on starting the new machine,Windows,VirtualBox 5.2.10,2018-05-05T01:22:57Z,2018-05-05T22:49:17Z,2018-05-05T22:49:17Z,I installed virtualbox and set all the settings and installed the extension pack. Then created my first vb with vhd and 32 bit linux os.,greybeard74
17731,virtual drive,Windows,VirtualBox 5.2.10,2018-05-04T13:24:06Z,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
17717,DNS resolver does not work,Windows,VirtualBox 5.2.10,2018-04-28T20:27:43Z,2018-04-30T14:56:28Z,2018-04-30T14:56:28Z,"Adapter in NAT mode, network ""192.168.100/24"".

Guest network adapter is called enp0s3, `ip addr` shows the interface is up with ""inet 192.168.100.15/25"".

`ip route` shows ""default via 192.168.100.2 dev enp0s3"".


Now, on the host-side the default DNS is 192.168.1.1.
The guest can ping this IP, but according to the [https://www.virtualbox.org/manual/ch09.html#changenat manual/ch09.html#changenat] the name server should be available at 192.168.100.3.

In the guest: `drill virtualbox.org @192.168.100.3` fails with ""Error: error sending query: Could not send or receive, because of network error"".
`drill virtualbox.org @192.168.1.1` (""directly"" through the DNS in the host's network) works.

I can however ping 192.168.100.3. I can also ping .2 and .4 successfully.",xnoreq
17718,Poor network latency performance / consistency,Windows,VirtualBox 5.2.10,2018-04-28T21:02:15Z,2018-04-28T21:02:15Z,2018-04-28T21:02:15Z,"For VBox.log see the attached log from #17717.

Pinging a computer in the LAN from the host I get constant <1 ms RTT.

Pinging the same computer through from the guest I get ping times that fluctuate from >1 to 10ms. Sometimes it jumps to over 70ms, and even over 160 ms.

This is with both the host and guest essentially idle. Similarly poor performance is observed with TCP and UDP.",xnoreq
17617,guru meditation,Windows,VirtualBox 5.2.6,2018-03-12T16:01:22Z,2018-04-24T20:03:27Z,2018-04-24T20:03:27Z,"Hi,

Please am unable to install my new kali-linux-light-2018.1-i386 on windows 7 host which is giving me a guru meditation error.

Attached are details of error report.
Thank you.",swagalimo
17522,After updating software and kernel of Xubuntu 17.10.1 - critical error on restart,Windows,VirtualBox 5.2.6,2018-02-02T20:44:39Z,2018-04-09T05:43:59Z,2018-04-09T05:43:59Z,"After a good install of Xubuntu, ran software updates, during restart got a critical error:

Installed latest 5.2.7 test build and got same error:

""A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on  https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""",wadesnj
17669,Virtual Box not saving Default Machine Folder after closing app,Windows,VirtualBox 5.2.8,2018-04-06T03:55:38Z,2018-04-06T03:55:38Z,2018-04-06T03:55:38Z,"The version of VBox I have is 5.2.8. I have Windows 10 as my host. I have an SSD as my C drive and a HDD as my D drive. Both internal drives. When I go to file-> Preferences->Default Machine Folder->Other and select a folder on my D drive. It changes. However, when I close the application, all the preferences revert back to the default, and the VMs that were save to the D drive are removed from the main list of VMs.",Joe5232
17635,Linux guest OGL regression in 5.2.8 (LKG 5.1.30),Windows,VirtualBox 5.2.8,2018-03-23T07:20:30Z,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
17624,Files containing only zeroes gets modified after restart,Windows,VirtualBox 5.1.12,2018-03-16T16:49:37Z,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
17620,VERR_VMX_NO_VMX,Windows,VirtualBox 5.2.6,2018-03-13T11:01:44Z,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
15897,Symfony clearing cache fails when done through shared folder (rmdir fails),Windows,VirtualBox 5.1.4,2016-09-07T03:33:41Z,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
17595,Try to attach USB device to VM crashes the VM,Windows,VirtualBox 5.2.8,2018-03-06T14:51:24Z,2018-03-06T14:51:24Z,2018-03-06T14:51:24Z,"When enabling access to intel USB device (Vendor ID: 8087 Product ID: 07dc) the VM gets totally stucked and a reboot of the host is necessary. That is easily reprocible and happens each time.

The logs displays this error message:
ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={c19073dd-cc7b-431b-98b2-951fda8eab89} aComponent={HostUSBDeviceWrap} aText={USB device 'Intel Corp.' with UUID {674944f8-07e8-4224-b303-cb4161d16cb4} is busy (state 'CapturingForVM[Detach]'). Please try again later}, preserve=false aResultDetail=0

Tried with Lubuntu & Debian Guest OS. Of course guest Add-ons have been properly installed.

The bluetooth device works properly on the host.

",jeanbox
17589,No virtual screen repaint when external monitor is connected to laptop.,Windows,VirtualBox 5.2.8,2018-03-05T10:44:33Z,2018-03-05T10:44:33Z,2018-03-05T10:44:33Z,"I have Windows 10 host with Ubuntu 16.04 guest. With enabled 3D acceleration (which is required because without that everything is laggy) and external monitor connected (tested with dvi and mini display port), the drawing on virtual screen freezes when in gnome. It does not matter whether monitor is an extension, clone or primary display. Immediately after monitor disconnection, the virtual screen starts to repaint.

Under the frozen screen the system is running (cursor changes with the windows even after repositioning which is not visible on the frozen screen, ctrl alt fx can be used to display working and visible shell).

When 3D acceleration is disabled, screen repaints fine with external monitor connected. 
I tested also development version 5.97 with the same result.",mvodolan
17585,Audio Output and Input issues on Ubuntu 17.04 with Windows 10 Host,Windows,VirtualBox 5.2.6,2018-03-04T01:01:21Z,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
17581,Vbox Guest Additions support for kernel-4.16.0-rc2,Windows,VirtualBox 5.2.6,2018-03-02T08:24:33Z,2018-03-02T08:24:33Z,2018-03-02T08:24:33Z,"1> Virtual Box version - 5.2.6 r120293

2> Created Virtual Machine  ( CentOS Linux (3.10.0-693.el7.x86_64) 7 ).

3> Default Guest additions image ( which comes when we mount it from devices options ) is working fine.  

4> Downloaded Linux Kernel  ( version - 4.16.0-rc2 )

5> Compiled Linux Kernel ( version - 4.16.0-rc2 ) and booted with it.

6> Guest Additions stopped working, so I debugged around it.

7> And re-installed default guest addition, but its not working ( auto-size guest display is not working  )

8> Downloaded Guest Addition iso image ( VBoxGuestAdditions_5.2.8.iso ) from ""http://download.virtualbox.org/virtualbox/5.2.8/"".

9> Run the Vbox Guest additions agains. I see some compilation errors. Attaching logs.

So I just want to understand if I did something wrong here or is the kernel with which I have booted is still not supported in Virtual Box guest additions 5.2.8.
  

",Zubraj
17569,QtCreator does not work on Linux Ubuntu after new Update,Windows,VirtualBox 5.2.6,2018-02-27T11:42:20Z,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
17527,appcrash virtualbox 5.2.6 on win7 32 bit,Windows,VirtualBox 5.2.6,2018-02-05T14:02:00Z,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
17571,Guest additions will not build using gcc 6,Windows,VirtualBox 5.2.6,2018-02-27T15:36:43Z,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
17474,Black Screen of Death after update to 5.2.6 from 5.2.4,Windows,VirtualBox 5.2.6,2018-01-18T03:00:26Z,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
14747,No sound. Windows 7 host / Arch Linux guest.,Windows,,2015-10-26T09:00:58Z,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
17183,Ubuntu guest on Windows host not properly shut down,Windows,VirtualBox 5.1.28,2017-10-20T08:56:33Z,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
11976,long paths  (>260chars) cannot be created using a host:win + guest:linux setup,Windows,VirtualBox 4.2.16,2013-07-19T17:23:19Z,2018-02-23T21:23:47Z,2018-02-23T21:23:47Z,"From https://github.com/mitchellh/vagrant/issues/1953 and https://github.com/isaacs/npm/issues/3670, VirtualBox on windows cannot generate paths longer than ~260 characters on windows, despite windows supposing UNC paths to allow for ~32k character paths. This means that using things like Vagrant, with a project that uses node/npm, is blocked by VirtualBox because node module dependencies (but also just any deeply nested software project being tested in a virtualbox VM) end up having paths that are longer than the standard 260 character limit.

Somewhere, VirtualBox is not communicating the correct error from host to guest OS; it would be extremely useful if this was solved somehow (allowing UNC paths by default? perhaps something else altogether)",Urrich
17014,Fedora Gnome slow UI performance,Windows,VirtualBox 5.1.26,2017-08-15T10:25:33Z,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
17548,[5.2.6 r120293] Guest linux hangs on boot-up if audio is enabled,Windows,VirtualBox 5.2.6,2018-02-18T08:18:26Z,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
17423,Oracle Linux 6 Booting Error From vboxadd,Windows,VirtualBox 5.2.4,2018-01-05T23:20:07Z,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
17545,"Drag and Drop does not work: Windows 7 host, Fedora linux guest",Windows,VirtualBox 5.2.6,2018-02-14T16:41:17Z,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
17542,VirtualBox 5.2.6 Guru Meditation Error,Windows,VirtualBox 5.2.6,2018-02-13T17:37:21Z,2018-02-13T17:37:21Z,2018-02-13T17:37:21Z,"Since VirtualBox 5.2.6 my VirtualBox keeps crashing with a Guru Meditation Error on Windows 10 Host with Debian guest.
My Log.txt is attached.",Frank Breitling
17541,Input/output error when running ./VBoxLinuxAdditions.run on headless guest,Windows,VirtualBox 5.2.6,2018-02-13T15:32:29Z,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
17539,VirtualBox driver crashes when rebooting with kexec on Ubuntu 16.04,Windows,VirtualBox 5.2.6,2018-02-12T02:54:03Z,2018-02-12T11:33:03Z,2018-02-12T11:33:03Z,"Restarting into another kernel is faster with kexec. There's a crash when I try to reboot into another kernel with kexec. The problem (says the screenshot) is because VirtualBox.

The commands I issued were:

diwou@diwou-VirtualBox:~$ sudo kexec -l /boot/vmlinuz-`uname -r` --reuse-cmdline
[sudo] password for diwou:
diwou@diwou-VirtualBox:~$ sudo systemctl kexec

Then I can see a crash on the GUI screen...

This bug was reported 5 years ago, I read it was marked as obsolete, but I think it's not fixed.",D1W0U
15217,McAFee Agentblocks virtual machine running,Windows,VirtualBox 5.0.16,2016-03-08T09:27:19Z,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@…
17526,Memory exception,Windows,VirtualBox 5.2.6,2018-02-05T14:01:03Z,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
17504,VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,VirtualBox 5.2.6,2018-01-27T10:53:10Z,2018-02-05T11:35:34Z,2018-02-05T11:35:34Z,"Upgraded VB on VirtualBox 5.2.6 version.
Run Guest Ubuntu 16.04 host (has not been running/updated for about a month)
Executed ubuntu updates with:

{{{
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
}}}

Was unable to create a symlinks in my shared directory.
Executed the following command which was supposed to help:


{{{
VBoxManage.exe setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/SHARE_NAME 1
}}}

Then unable to start the Guest machine because of GURU error from the subject.",Faly
12168,Oracle Virtualbox manager has stopped working,Windows,VirtualBox 4.2.18,2013-10-08T05:27:51Z,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
17523,CentOS7 hangs after installing guest additions,Windows,VirtualBox 5.2.6,2018-02-03T12:59:50Z,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
17506,It should be possible to boot a guest with an unconnected hotplug disk,Windows,VirtualBox 5.2.4,2018-01-27T15:18:51Z,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
17501,Ubuntu guest fails after waking from windows 10 host sleep,Windows,VirtualBox 5.2.6,2018-01-26T17:46:47Z,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
17481,VM crashes when allocating memory at MSR_LSTAR address range,Windows,VirtualBox 5.2.6,2018-01-19T10:45:07Z,2018-01-19T22:32:20Z,2018-01-19T22:32:20Z,"Hi,

I'm developing a Linux LKM, and I tried to reserve memory in the same range of MSR_LSTAR (SYSCALL handler), with __vmalloc_node_range().

On the 3rd execution of that function, returning first NULL, second an address and third time NULL, the Guru Mediation spawns.

I'm attaching the source code to reproduce the bug, the log and the screenshot.

Thanks for help.",D1W0U
17268,Guest Addition graphics driver build fails on Debian 9.2 -> fixed,Windows,VirtualBox 5.2.0,2017-11-11T23:56:16Z,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
17206,VBoxLinuxAdditions.run fails in Ubuntu Server 16.04.3 -> module signing problem,Windows,VirtualBox 5.2.0,2017-10-23T22:00:34Z,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
17459,Keyboard/mouse not working after connecting to Dell Docking Station,Windows,VirtualBox 5.2.4,2018-01-16T16:54:46Z,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
17436,[FIXED IN SVN] VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation,Windows,VirtualBox 5.2.4,2018-01-08T20:46:23Z,2018-01-10T23:04:19Z,2018-01-10T23:04:19Z,"I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows:

A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows)

I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out:

00:00:17.401353 !!   VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)

I am attaching a .ZIP file of the VBox.log.



",GregB3
17422,Switching away from guest alters NumLock state of host,Windows,VirtualBox 5.2.4,2018-01-05T09:27:40Z,2018-01-05T18:55:21Z,2018-01-05T18:55:21Z,"Host: Windows 7 Enterprise, initial NumLock state at ""On""
Guest: KDE Neon, initial NumLock state at ""On""

Steps:
Ensure NumLock is on for the host.
Start the guest.
Observe that the host's NumLock remains on.
Enter the guest (e.g. click within the window).
Ensure NumLock remains on.
Return to the host (click the task bar or something that causes VBox to lose focus).

Expected outcome:
Host's NumLock remains on.

Actual outcome:
Host's NumLock turns off.

VBox version first observed: 5.1
Is 5.2.4 affected: Yes

After running a search, I wonder if these bugs are related in some way:
https://www.virtualbox.org/ticket/14614
https://www.virtualbox.org/ticket/14302

I am happy to provide any logs that might be needed.",Twisted Lucidity
16878,VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error on Windows 10,Windows,VirtualBox 5.1.22,2017-07-06T02:31:12Z,2018-01-04T11:44:53Z,2018-01-04T11:44:53Z,"Hello

I keep getting the above mentioned error when I start a guest. I remove and reinstall VirtualBox and the error goes away, but after a few days it comes back again (usually after a restart of my PC). I am attaching the screen shot of error box and VBoxHardening log. A shorter error message is below:


{{{
Failed to open a session for the virtual machine Ubuntu-16.04.

The virtual machine 'Ubuntu-16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\arshad.khan\VirtualBox VMs\Ubuntu-16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}


Any help is greatly appreciated.

Thanks
Arshad",arshad01
17412,Installing Guest Additions 5.2.4 on CentOS 7 fails,Windows,VirtualBox 5.2.4,2018-01-02T17:12:13Z,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
17403,Touchscreen input is not scaled to VM location on screen,Windows,VirtualBox 5.2.4,2017-12-27T06:40:05Z,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
17402,Unexpected input upon minimize/maximize host window,Windows,VirtualBox 5.2.4,2017-12-26T20:13:40Z,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
14978,Error In supR3HardNtChildWaitFor,Windows,VirtualBox 5.0.12,2015-12-26T14:09:49Z,2017-12-22T06:27:04Z,2017-12-22T06:27:04Z,"Hello,
I get this error on startup since 5.0.8 (also on .10 and .12).
Key Host Info:
- Lenovo x250 16GB RAM, 512 SSD
- Host win7 (latest patches some win10 upgrade stuff suppressed)
- guests: debian (but probably irrelevant)
- avira antivir antivirus
- comodo firewall

When I start vbox, after a while I get the following error:
---------------------------
VirtualBox - Error In supR3HardNtChildWaitFor
Timed out after 60001 ms waiting for child request #1 (CloseEvents).
(rc=258)
where: supR3HardNtChildWaitFor
what:  5
Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)
---------------------------

If I do not close it and wait a while (another minute or so) I get it again, and then the guest opens just fine. See this bug description:
https://forums.virtualbox.org/viewtopic.php?t=64111&f=6#p301426 (way back from Oct 2014 and 4.3.18)
...it is essentially this. If I close any of the dialogs, then the guest does not open. Attached are the logs (from 5.0.10, I can recreate with .12 if desired) and a screenshot of the errors. The logs appear normal.

Thanks
Nils
",Nils
17381,virtualbox additional functions are uninstallable,Windows,VirtualBox 5.2.4,2017-12-20T12:19:13Z,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
17387,USB Dongle not recognized correctly,Windows,VirtualBox 5.1.22,2017-12-21T13:56:46Z,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
17384,ElementaryOS Loki not usable with 3D enabled -> unlikely to be fixed in near future,Windows,VirtualBox 5.2.4,2017-12-20T22:37:37Z,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
16771,Qubes install ISO fails to run,Windows,VirtualBox 5.1.22,2017-05-19T14:02:06Z,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
17370,Unknown USB device detected,Windows,VirtualBox 5.1.22,2017-12-14T10:57:05Z,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
17020,dd on USB drive results in Input/output error,Windows,VirtualBox 5.1.26,2017-08-17T22:04:47Z,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
15553,USB 1.1 (OHCI) controller stops working after a period of time,Windows,VirtualBox 5.0.22,2016-06-28T14:52:03Z,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
16449,Flashing ROM on USB device fails,Windows,VirtualBox 5.1.14,2017-02-03T22:55:21Z,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
17235,5.2 causes blue screen of death on windows 10,Windows,VirtualBox 5.2.0,2017-11-04T03:22:51Z,2017-12-11T20:00:20Z,2017-12-11T20:00:20Z,"I upgraded from 5.1.30 to 5.2 to use my ubuntu 17.04 and 17.10 machines. I had multiple BSOD per hour until I reverted to 5.1.30. No BSOD since then.

I have a Surface Pro 4 with the latest Windows 10 updates.

Sorry, I could not capture the error code or QR on the blue screen before the PC rebooted.",silvermangb
17239,Serial port missing characters.,Windows,VirtualBox 5.2.0,2017-11-04T14:38:09Z,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_
17349,VINF_EM_TRIPLE_FAULT,Windows,VirtualBox 5.2.0,2017-12-05T22:41:28Z,2017-12-07T02:13:13Z,2017-12-07T02:13:13Z,"I get guru meditation immediately after the Virtualbox BIOS screen and the log says VINF_EM_TRIPLE_FAULT. This is in a guest machine where I just freshly installed RHEL 7.4 64 bit running on Windows 7 64 bit host. The guest started to boot the first start after I installed RHEL but triple fault occurred before boot finished. Every other boot gets triple fault immediately after the Virtualbox BIOS screen. I see lots of other triple fault bugs but none for Red Hat.

Error occurs on latest stable and latest testing builds

Stable
VirtualBox-5.2.2-119230-Win.exe

Testing
Version 5.2.3 r119405 (Qt5.6.2)",ke
17270,Scrolling with mouse integration,Windows,VirtualBox 5.1.30,2017-11-13T22:18:29Z,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
17330,Ubuntu 17.10 guest freezes when restoring guest windows,Windows,VirtualBox 5.1.30,2017-11-29T17:04:05Z,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
17263,VirtualBox encounters an application error and aborts the guest,Windows,VirtualBox 5.1.28,2017-11-10T15:50:50Z,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
12738,OpenGL windows are always on top of everything else in linux guest,Windows,VirtualBox 4.3.8,2014-02-26T15:32:52Z,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
17245,VBoxGuestAdditions_5.2.1-118918 does not work with Ubuntu 17.10 guest,Windows,VirtualBox 5.2.0,2017-11-05T16:09:16Z,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
17244,CentOS 7 Kernel-ml hangs,Windows,VirtualBox 5.2.0,2017-11-05T13:45:10Z,2017-11-05T13:45:10Z,2017-11-05T13:45:10Z,"Documented here: https://bugs.centos.org/view.php?id=11065

Kernel hangs on CPU making the guest graphics mainly unuseable unless you run all Linux in CLI

I'm using the Virtualbox guest additions as advised on the main site, aware that the latest won't compile properly.

Also doesn't like bridging with an RTL8188EE adapter properly, this could be because of the native drivers.",koolholio
17166,Installing Extension Pack trashes Linux MDM Login options,Windows,VirtualBox 5.1.28,2017-10-15T02:28:38Z,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
16850,No Connection to Mobile Phone with MTP via USB,Windows,VirtualBox 5.1.22,2017-06-21T17:09:56Z,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
17167,Can't install Extensions in WMaker / Linux Mint 17.2,Windows,VirtualBox 5.1.28,2017-10-15T03:10:59Z,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
15084,Scale Factor Causes Malfunction of USB Multi-Touch Tablet in Debian-Based Linux,Windows,VirtualBox 5.0.14,2016-01-28T06:18:18Z,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
17159,vboxsf file timestamp not set properly,Windows,VirtualBox 5.1.28,2017-10-12T15:40:37Z,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
17143,Windows 10 BSOD if Guest OS started,Windows,VirtualBox 5.1.28,2017-10-06T09:47:15Z,2017-10-06T09:47:15Z,2017-10-06T09:47:15Z,"Hello.
If I start guest operation system - I tried FreeBSD, Ubuntu, my laptop got BSOD. Windows 10 Enterpise  1703 (OS Build 15063.384). I made searh about this type of issues - WTx - instructions enabled in BIOS and HYPER-V uninstalled.
",lvesel
16448,VBoxHardening issue (AV software),Windows,VirtualBox 5.1.14,2017-02-03T20:17:44Z,2017-10-04T09:15:23Z,2017-10-04T09:15:23Z,"Windows 7 Enterprise SP1
Virtual Box 5.1.10 was working fine until company pushed an update to my workstation.

I think the issue is related to Cylance Protect as that software seems to have been updated the day VB broke.
It's also possible kernel32.dll was updated by a windows update.

Error starting ALL VMs..

The virtual machine 'DeleteMe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\MyProfile\VirtualBox VMs\DeleteMe\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


The workstation/host has Cylance Protect and Symantec Endpoint Protection enabled (and I can't disable them to test).

I tried test builds.

5.1.10 original had the issue.
5.1.14 - same issue
5.1.15 - test build same issue.
5.1.51 - dev build same issue

",gingleby
17118,virtualbox nataliasmode proxyonly breaks local network connectivity on windows 10,Windows,VirtualBox 5.1.28,2017-09-28T18:09:31Z,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
17115,X of guest freezes with 3D acceleration enabled,Windows,VirtualBox 5.1.28,2017-09-28T11:11:49Z,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.
4656,USB device is busy with a previous request,Windows,VirtualBox 3.0.2,2009-07-30T12:38:29Z,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
15774,VirtualBox incorrectly counts processors on AMD products,Windows,VirtualBox 5.1.2,2016-08-10T01:37:02Z,2017-09-24T05:21:17Z,2017-09-24T05:21:17Z,"VirtualBox incorrectly counts processors on AMD products.  I have an AMD CPU with 8 physical processors.  This processor has 8 full processor cores.  Evidently, VirtualBox assumes this processor is an Intel product with Hyper-Threading, but this assumption is not correct.
",Kriston
17108,Virtualbox 5.1.28 running under Windows 10 corrupts clipboard copy & paste,Windows,VirtualBox 5.1.28,2017-09-22T16:16:06Z,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
17103,Mouse direction locked in opengl programs,Windows,VirtualBox 5.1.28,2017-09-21T04:51:24Z,2017-09-21T04:51:24Z,2017-09-21T04:51:24Z,"Host Win10, Virtual box 5.1.28 with Ubuntu 16.04 installed.
After install the VBoxGuestAdditions, when i start an opengl Application, the mouse lost control, just pointting to the sky.
When I tried to move left/right, the picture just rotate, not looking around.",ffpwserver
17099,Shared clipboard : bidirectional mode causes host clipboard malfunctions,Windows,VirtualBox 5.1.28,2017-09-19T17:33:33Z,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
17000,Cumulative update for Windows 10 1703 broke Virtualbox VT-x recognition,Windows,VirtualBox 5.1.26,2017-08-11T12:37:20Z,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
16901,Non-driver certificates not handled correctly by hardening (OpenText SOCKS),Windows,VirtualBox 5.1.22,2017-07-14T10:03:31Z,2017-09-15T13:22:10Z,2017-09-15T13:22:10Z,"I had originally raised an issue with OpenText socks that theri DLL was not signed and so did not work with VirtualBox. They have now provided a signed version, but it is not signed with a driver certificate. According to OpenText support VirtualBox is not handling the signing check correctly. Some of my correspondance with OpenText support pasted below.

----------------------------------------------------------------------------
---- From OpenText Support -----

Hello Lars,

In regards to ticket #3056978, I received input from Engineering.  This issue appears to be related to the third party application.

According to Engineering: 
If you used signtool, it would show DLL is properly signed.  Note, using the default option, will show a trust error because the default assumes driver signing and this is a not a driver with signed catalog file.  You need to use /pa argument for the signing to show as valid.  Since you use SigCheck (Sysinternals), you do not need to use any parameters to show the DLL is signed

C:\Users\xx>sigcheck64 ""c:\Program Files\Open Text\SOCKS Client\*"" > C:\xx\sigcheck_socks.14.0.16.txt

(Refer to the output in the attached file.)
 

The root issue is that Virtualbox process will have HumSOCKS.dll injected into its process space (this is simply how SOCKS works on Windows).  On startup it does a complicated self-validation on itself and all loaded DLLs in the main process space.  Essentially the rules force that all DLLs need to be signed properly (or a couple of other exceptions for specific location and owner of file).  It appears that their code fails the same way that signtool does without the /pa flag and ultimately will not start up when we are in their process space because of that.  In one sense this is correct behavior because there's no signed catalog file for us at all but it's definitely unwanted because it should not apply that logic for 3rd party dlls that are not drivers.

This appears to be a long standing issue with VirtualBox - check out https://www.virtualbox.org/ticket/13659.  The corrupted path it starts out as is not a problem for us but the exact same issue with failed trust for a correctly signed DLL is the main issue left.

Regards,
OpenText Support



---- From me to OpenText Support ---
To: support@opentext.com
Subject: Re: FW: OTCS Ticket 3056978 Socks 14:  VirtualBox does not work when SocksClient is installed

Hi, I have tried your recommendation of importing the certificate. I also tried disabling the virus scanner. I also tried importing the intermediate certificate and tried loosening some policy settings, but nothing solves the problem. SHA-256 certificates show up fine in Windows and the patch required for support is installed.   The error I'm getting in the VBoxHardening.log is:

{{{
14a4.1a9c: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll) WinVerifyTrust
14a4.1a9c: Error (rc=0):
14a4.1a9c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll: None of the 1 path(s) have a trust anchor.: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll 
14a4.1a9c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll
14a4.1a9c: Error (rc=0): 
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll' (C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll): rcNt=0xc0000190
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll'
}}}",Lars Hupfeldt
17069,Virtual Box cannot create Virutal Machine of 64bits OS on Windows10 Creators Edition.,Windows,VirtualBox 5.1.26,2017-09-10T04:50:13Z,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
17058,Memory protection exception on booting Ubuntu 16.04 VM,Windows,VirtualBox 5.1.26,2017-09-06T20:21:11Z,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
17065,SEGV with plymouth on Ubuntu GNOME 16.04,Windows,VirtualBox 5.1.26,2017-09-08T14:31:53Z,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
17047,"Memory Issue since updated to 5.1.26 - ""Instruction at 0x4336d43 referenced memory at 0x00000018. The memory could not be read.""",Windows,VirtualBox 5.1.26,2017-08-31T06:59:07Z,2017-08-31T06:59:07Z,2017-08-31T06:59:07Z,"Host: Windows 7
Guest: Ubuntu Mate 16.04 LTS

Since I have updated to version 5.1.26, I often get a error message when starting the virtual machine (see attached picture).
After the error message, the virtual machine aborts.
After a few tries it finally starts.",TK87
16903,Windows 10 crashes on VirtualBox session startup,Windows,VirtualBox 5.1.22,2017-07-14T21:03:03Z,2017-08-17T15:27:49Z,2017-08-17T15:27:49Z,"VirtualBox: 5.1.22
Host: Windows 10
Guest: Kali

Windows 10 crashes when starting Kali - the blue screen shows error IRQL_UNEXPECTED_VALUE.

",caveman14
17001,Getting memory Access Violations 5.1.26,Windows,VirtualBox 5.1.26,2017-08-11T13:23:44Z,2017-08-15T18:04:07Z,2017-08-15T18:04:07Z,"Randomly getting Memory Access Violations.  Often at some point during startup, but not always.

I looked in the VBox.log file, but nothing jumped out at me.

Are there other ways to debug this?

The VBox.log is attached.",jhellmers
17016,instruction referenced at 0xe6826d43 referenced memory at 0x00000018 could not be read,Windows,VirtualBox 5.1.26,2017-08-15T16:12:23Z,2017-08-15T16:47:38Z,2017-08-15T16:47:38Z,"windows7 host ubuntu 16.04 guest
moved the vm from a win7 notebook to a win7 workstation
a repeatable crash during vm startup, various instruction address

apparently solved the issue by changing chipset type from PIIX3 to ICH9, all other changes to vm settings had no effect

",devotip
17011,"VBox crashes; Host Win 8.1, Guest Debian Strech; amd64",Windows,VirtualBox 5.1.26,2017-08-13T15:30:16Z,2017-08-15T08:35:23Z,2017-08-15T08:35:23Z,"VBox crashes on my new installation of Debian Stretch amd64 as guest system. My host system is Win 8.1, amd64. The crash happens after the installation of the Virtualbox Guest Additions during booting the guest. It is a permanent fault and happens during every boot.

Appended is the Win error message as image (part of a screen dump).",hwkraus
16992,Linux filesystem through share folder will be data crash,Windows,VirtualBox 5.0.40,2017-08-08T18:53:35Z,2017-08-10T20:44:24Z,2017-08-10T20:44:24Z,"Host Windows 7, Phy 16 GB RAM[[br]]
Guest Linux Centos 6.8, Virtual 3 GB RAM[[br]]
/share is share folder on Windows NTFS.[[br]]
[[br]]
Reproduce command:[[br]]
*---------- Start[[br]]
dd if=/dev/zero of=/share/tmp_fs bs=1M count=300[[br]]
mkreiserfs -f /share/tmp_fs[[br]]
mount -o loop /share/tmp_fs ~/x[[br]]
touch ~/x/mark (or copy anything to there)[[br]]
umount ~/x[[br]]
*---------- End[[br]]
[[br]]
Now, if you re-mount tmp_fs, you will found nothing in filesystem, and if you fsck on it, it will show filesystem broken.[[br]]
[[br]]
On 5.0.28, all thing are fine[[br]]
On 5.0.40 and above 5.1.x (Note: I don't try on 5.0.30 - 5.0.38), you will catch the bug.[[br]]
",C-MIKE
16985,VB Additions incompatible with RAID driver,Windows,VirtualBox 5.1.26,2017-08-06T12:10:13Z,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
16954,"Ubuntu 16.04 VM Win 7 Host; VM worked fine on 5.1.24, crashes on fullscreen in 5.1.26",Windows,VirtualBox 5.1.26,2017-07-28T17:24:04Z,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
16897,NtCreateFile failed: Unknown Status -626,Windows,VirtualBox 5.1.22,2017-07-12T11:53:11Z,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
16925,virtio-net slower than Intel PRO/1000 Desktop,Windows,VirtualBox 5.1.22,2017-07-20T15:07:13Z,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
16907,"Vbox additions 5.1.22 in CentOS 6 cause display adapter to be ""unknown""",Windows,VirtualBox 5.1.22,2017-07-17T15:29:31Z,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
16864,VBox 5.1.22 Does Not Start VM after Upgrade from Win7 to Win10,Windows,VirtualBox 5.1.22,2017-06-29T22:42:33Z,2017-07-06T14:39:40Z,2017-07-06T14:39:40Z,"VM's created with Manager 5.1.22 r115126 were working in Win7.
Upgraded to Win10 Enterprise, ver 1703, build 15063.0.
VMs will not start.
VMs are Ubuntu Xenial 16.04.
Tried running the repair VM Manager from the VBox installer.  Did not work.

On VM ""Start"", I get 2 popups.  
The 1st popup refers to running a cmd 'sc.exe', the results of which are posted.
The 2nd popup refers to a file that I pasted below.
I could not find a button to attach the file.

COMMAND - SC.EXE
{{{
sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.
}}}",jkAB
16877,BSoD CLOCK_WATCHDOG_TIMEOUT,Windows,VirtualBox 5.1.22,2017-07-05T17:30:24Z,2017-07-05T17:30:24Z,2017-07-05T17:30:24Z,"Machine Log: https://pastebin.com/raw/zYqqUp1T
Host OS: Windows 10
There is a dmp file from the bluescreen wich shows VBoxDrv.sys
I'm using Homestead (laravel) with vagrant. Maybe that helps.
Hopefully this is not a duplicate

This bsod just happens randomly when doing something in host system
DMP file can be loaded here: http://www49.zippyshare.com/v/1pxcsU2X/file.html
as to big for the attachmnent page.",keving
16529,Linux guest additions update creates spurious initramfs copies,Windows,VirtualBox 5.1.14,2017-03-03T00:05:53Z,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
16828,Unknown USB device detected,Windows,VirtualBox 5.1.20,2017-06-13T17:43:23Z,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
16811,VBox 5.1.12.12440 immediately crashes - Win10 x64 Home,Windows,VirtualBox 5.1.12,2017-06-04T20:04:30Z,2017-06-05T14:25:59Z,2017-06-05T14:25:59Z,"I cannot run VirtualBox 5.1.12.12440 x64. It crashes immediately when launced. I can't confirm, but I suspect the recent Windows 10 Creators update maybe did something to harm VBox, only becuase VBox worked fine until that Windows update was applied to my computer.

I've attached a crash dump of the most recent launch. I've also attached the most recent logs.",Malchore
16807,Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).,Windows,VirtualBox 5.1.22,2017-06-02T20:37:24Z,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
15975,VBoxManage always shows host only interfaces as disabled,Windows,VirtualBox 5.1.6,2016-09-22T22:41:20Z,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
16738,Cannot Switch Virtualization Off,Windows,VirtualBox 5.1.22,2017-05-08T05:58:12Z,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
16722,Crash on changing optical drive assignment,Windows,VirtualBox 5.1.22,2017-05-03T09:40:19Z,2017-05-03T11:22:00Z,2017-05-03T11:22:00Z,"Hi,
right from clean install of 5.1.22, when I prepared initial config of Debian64 VM, I went to properties, wanted to delete IDE controller (optical disk) and use opt drive under existing SATA there, it crashed - and always crashes.",peterg91
16457,Some menu categories in Linux guest OSes no longer populate,Windows,VirtualBox 5.1.14,2017-02-06T17:20:49Z,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
16681,Virtual core XTEST pointer/keyboard inoperative under X11,Windows,VirtualBox 5.1.20,2017-04-21T10:08:53Z,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
16656,"after command init 6, generate core dump and duplicate UUID",Windows,VirtualBox 5.1.18,2017-04-15T19:51:50Z,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
16492,WebEx screen sharing with Windows 10 host causes guest to crash and out of memory error.,Windows,VirtualBox 5.1.12,2017-02-16T22:35:02Z,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
16638,Don't import appliances if there's not enough space on disk,Windows,VirtualBox 5.1.18,2017-04-05T18:50:26Z,2017-04-06T10:26:05Z,2017-04-06T10:26:05Z,"When importing appliances, it is common that the appliance file is smaller than the actual guest disk size.
Given that, if you are importing an appliance and you don't know the guest disk size, you'll get an error after the host disk is full.
Some import operations may take up to a hour, or more, so if you get the error after the import cannot continue, this is a little frustating to see the time you could save.

E.g.: I have a 20GB appliance the allocates more than 100GB. I was trying to import it on a disk with 80GB free. After 40min importing, I got the allocation error.

So, my suggestion is to show the final size for allocated space in the import dialog, or maybe even check the drive that the user is placing the VM disk and give a message like 'You don't have enough space to import that machine here', or something like that.",tgarcia
16620,Crash when removing USB device,Windows,VirtualBox 5.1.18,2017-03-29T16:07:08Z,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
15417,GUI Artifacts after opening Chrome,Windows,VirtualBox 5.0.20,2016-05-15T00:43:28Z,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
16615,No USB Device Access with NoMachine v5.2.11 Innstalled,Windows,VirtualBox 5.1.18,2017-03-28T06:23:41Z,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
16601,Windows 10 on Surface Book virtualbox install,Windows,VirtualBox 5.1.18,2017-03-24T01:13:41Z,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
16589,Raw mode release assertion,Windows,VirtualBox 5.1.18,2017-03-21T11:05:16Z,2017-03-23T11:00:33Z,2017-03-23T11:00:33Z,"Ubuntu Linux 16.04 server as guest,
Windows 7 as host

Virtualbox version 5.1.18r114002

While updating the Linux kernel (using apt), the following error stopped the virtual machine:

{{{
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0xe555a9ac.

Click OK to terminate the program
Click CANCEL to debug the program
}}}


[[Image(https://i.imgur.com/K0duG4a.png)]]
[[Image(https://i.imgur.com/SRYeDD0.png)]]",Brianetta
16553,Virtual Machines running very slowly,Windows,VirtualBox 5.1.16,2017-03-11T13:47:57Z,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
16559,Mouse pointer misaligned,Windows,VirtualBox 5.1.16,2017-03-14T08:02:22Z,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
16558,missing menu item to enable/disable virtual screen,Windows,VirtualBox 5.1.16,2017-03-13T17:27:08Z,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
16554,"VirtualBox on Windows 10 leaks hostonlyifs, turning them into bridgedifs which cannot be removed",Windows,VirtualBox 5.1.14,2017-03-12T09:34:39Z,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
16526,Google Chrome Stable Crashes Linux Guest,Windows,VirtualBox 5.1.14,2017-03-02T16:29:09Z,2017-03-02T16:40:47Z,2017-03-02T16:40:47Z,"I am not sure about the complete steps, but I can reproduce this each, and every time.  I launch Google Chrome (Version 56.0.2924.87 (64-bit)) under Ubuntu GNOME 16.04.2 Guest.  I visit a Cisco Acano URL to join a meeting (such as https://join.<some domain>.com/invited.sf?secret=QtsgKqo7mTqO2O4pOM0ouB&id=77223344).  When I join the meeting, VirtualBox crashes with an error message, such as:

    The instruction at 0xdc7aa4f2 referenced memory at 0x00000028.  The memory could not be read.  Click on OK to terminate the program.

Host:  Windows 7 Professional SP-1
       16GB RAM
       AMD Radeon R7 M360/Intel HD Graphics 520
       Dual Core i7
       Three monitors (laptop + two external)
Guest: Ubuntu GNOME 16.04.2
       8GB RAM
       128MB VRAM
       2 CPU
       2 Monitors
",JayBofMA
16525,Automatically switching to Seamless mode on start does not use full screen area,Windows,VirtualBox 5.1.14,2017-03-02T13:15:31Z,2017-03-02T13:15:31Z,2017-03-02T13:15:31Z,"If my Arch Linux x64 guest (on Win10 x64 host) is closed with seamless mode running, when I restart the guest there's a popup saying to switch back to seamless mode. If I click okay, seamless mode starts but there's a gap at the top from the vbox guest OS menu. I have to ctrl+L and ctrl+L again to get it to recognize the actual display size.",R
16463,"""Operation not permitted"" on file in shared folder",Windows,VirtualBox 5.0.26,2017-02-07T21:33:01Z,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
4862,"Files in shared folder which open in mode ""w+b""(Linux guest) could not be read(Protocol Error)",Windows,VirtualBox 3.0.4,2009-08-27T02:25:21Z,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
16510,Sound volume not working in guest (winxp x32). Host - kubuntu 16.04.2 LTS x64,Windows,VirtualBox 5.1.14,2017-02-25T08:52:43Z,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
16440,"As a guest, must hold keyboard key a second or more",Windows,VirtualBox 5.1.14,2017-02-01T20:49:13Z,2017-02-24T20:12:44Z,2017-02-24T20:12:44Z,"Previously used Control Panel to uninstall VBox 5.0.4 (was installed through MyDesktop)

Uninstalled VBox 5.1.14 which I'm having keyboard issues with (must hold keys for them to be recognized)

Re-downloaded VirtualBox-5.1.14-112924-Win.exe

Installed VBox 5.1.14, used all defaults

Used Start to bring up Oracle VM VirtualBox

Within VBox Manager, clicked on Start (Oracle Linux Server 6.6), replied with password to ""jhoelsch4.dev"" login.  Information had apparently been retained from a previous install of VBox.  So, looks like there are bits of configuration detail, probably retained in the registry.

Three windows are generated:
- Development [Running] - Oracle VM VirtualBox : 1
- Development [Running] - Oracle VM VirtualBox : 2  (contains icons Computer, jhoelsch's Home, Trash, sf_AutoImage, VBOXADDITIONS_5  1.13_112924)
- Development [Running] - Oracle VM VirtualBox : 3 (identical to window 1 above)
When password was entered in window 1, the same keystrokes were echoed in window 3.

Right-click on jhoelsch's Terminal -> Open In Terminal.  This is where keys must be held extra long to be recognized

Notes: 
sf_AutoImage is residual from a shared folder from a prior VBox install.
",John Hoelscher
16507,Windows 10 freezes when using a KVM switch while VirtualBox is running VMs,Windows,VirtualBox 5.1.14,2017-02-23T18:53:48Z,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
16500,An USB issue only on Linux guest,Windows,VirtualBox 5.1.14,2017-02-21T07:55:44Z,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
16471,TinyCore 7.2 boots on VB 5.0.32 but not on 5.1.14,Windows,VirtualBox 5.1.14,2017-02-09T10:41:13Z,2017-02-09T10:41:13Z,2017-02-09T10:41:13Z,"On a first machine: Win10 - VB 5.1.6, TinyCore-7.2.iso boots fine.

On a second machine: Win8 - VB 5.1.14, CorePlus-7.2.iso or TinyCore-7.2.iso fail with:

{{{
Code:  Bad EIP value.
EIP: [<fefa201c>]  SS:ESP 0068:c703bea4
---[ end trace 91cd7754bf702e09 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

}}}

Full console log attached. The VB log is no more available.

For trial, I uninstalled 5.1.14 and installed 5.0.32, and it worked.",Psam
16467,Unlink of locked file fails on shared folder,Windows,VirtualBox 5.1.14,2017-02-08T16:42:00Z,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
4890,"Linux guest, ""mv -f file1 file2"" fails on shared folder without write permissions on file2 (Windows hosts)",Windows,VirtualBox 3.2.10,2009-09-01T12:28:38Z,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
15603,VirtualBox 5.1 3D acceleration issues,Windows,VirtualBox 5.1.0,2016-07-13T15:15:46Z,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
16439,Clipboard add CR character,Windows,VirtualBox 5.1.8,2017-02-01T15:48:36Z,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
16420,Snapshots present but required Machine/@currentSnapshot attribute is missing.,Windows,VirtualBox 5.1.14,2017-01-24T11:29:01Z,2017-01-30T11:58:24Z,2017-01-30T11:58:24Z,"Hello,

since morning I receive this issue when starting directly into Virtualbox.
Yesterday I used my Ubuntu VM, took a snapshot and closed it.

Everything looked fine.

Please tell me a solution.

Thank you.

Regards

Andreas",Haemma
16433,The installer won't work error 2755 and when I can get it installed another problem happens.,Windows,VirtualBox 5.1.14,2017-01-30T04:26:09Z,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
16383,cannot ping but can ssh and http,Windows,VirtualBox 5.1.12,2017-01-13T06:12:33Z,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
16335,"VirtualBox automatically forces shut down of guest before displaying ""new version available"" dialog",Windows,VirtualBox 5.1.12,2016-12-29T19:02:50Z,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
16392,BSOD SYSTEM_SERVICE_EXCEPTION on Windows 10,Windows,VirtualBox 5.1.12,2017-01-16T13:31:29Z,2017-01-16T13:48:12Z,2017-01-16T13:48:12Z,"I use a VM from MongoDB University course M310.
When I run the VM I get BSOD.",enabokov
16291,Guest SuSe 13.2 freezes on Host Windows 7 when more than 1 processor (core2 quad) is assigned,Windows,VirtualBox 5.1.10,2016-12-15T09:51:04Z,2017-01-06T10:27:29Z,2017-01-06T10:27:29Z,"This issue is similar to that in [https://www.virtualbox.org/ticket/7619 ticket 7619]. However, the issue occurs with a recent VirtualBox version.

When more than 1 processor is assigned to the Guest (Open SuSe 13.2, XFCE Desktop) it freezes after some time and does not react anymore (commonly after below 1 hour). VirtualBox itself still runs. Pausing the VM or Saving it to the Disk (and resuming) works fine but the Guest is still frozen. The Host is Windows 7 SP1.

When I assign 1 processor it works fine (I worked for 2 month with this 1-processor-setup and experienced some performance problems recently, which is way I came back testing a >1 processor setup. But this is not the topic of this ticket).

3D acceleration is not enabled. The issue seems to be correlating with the usage of Mozilla Firefox and/or Thunderbird - but not exclusively. The freezes occured also without Firefox running (but less ofter). 

The host computer has a Core2 Quad Q9400 Processor. It does not support hyper-threading. I could assign up 8 cores in the settings dialog. I mention this because I found some discussion on whether cores or virtual processes are assigned. Idependent whether the processor supports hyper-threading or not, there should be only 4 cores available.

Currently, I am using VirtualBox v5.1.10 but the issue occured also in v5.1.6 and v5.1.8.

Since the number of Core2 processors is declining this issue probably has a quite low priority.",neumannd
15751,"Windows VM host crashes randomly, when using Ubuntu 16.04 LTS and 3D is enabled",Windows,VirtualBox 5.1.2,2016-08-05T12:26:51Z,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
16343,Guest screen corruption with 3D enabled unless mini-toolbar enabled,Windows,VirtualBox 5.1.12,2017-01-01T08:50:41Z,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
16316,Kubuntu guest rendering errors with 3D acceleration enabled,Windows,VirtualBox 5.1.12,2016-12-22T14:15:09Z,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
16313,drag and drop in virtualbox 5.1.12 fail in Centos 7.3,Windows,VirtualBox 5.1.12,2016-12-22T08:36:14Z,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
16222,"dragndrop file fails (Windows 10 host, Ubuntu 64bit guest)",Windows,VirtualBox 5.1.10,2016-11-24T03:05:15Z,2016-12-22T09:26:59Z,2016-12-22T09:26:59Z,"As per instructions, logs enclosed!",robertbaruch
16302,memory usaly error on ubuntu-16.04.1-desktop-amd64,Windows,VirtualBox 5.1.10,2016-12-17T15:18:18Z,2016-12-20T12:29:13Z,2016-12-20T12:29:13Z,"1. run WarZone2100
2. Инструкция по адресу 0х0000000058383А30 обратилась к памяти по адресу 0x0000000000000008. Память не может быть read. ""OK"" — завершение приложения

p.s. https://yadi.sk/i/cDluGr-q33qgq8",fix27
16307,sda_hda_intel 0000:00:05: CORB reset ...,Windows,VirtualBox 5.1.10,2016-12-19T06:57:27Z,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
13580,The Instruction at 0x... referenced memory at 0x... The memory could not be read,Windows,VirtualBox 4.3.18,2014-10-31T15:11:02Z,2016-12-12T17:22:47Z,2016-12-12T17:22:47Z,"As of version 4.3.16 and 4.3.18 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
",Frank Breitling
16024,Win10 host Ubuntu 16.04 guest random crashes,Windows,VirtualBox 5.0.26,2016-10-04T08:05:56Z,2016-12-07T10:02:03Z,2016-12-07T10:02:03Z,"I am using Ubuntu 16.04 with X on Win10 host. It randomly crashes from time to time. I found a remedy. If I select Other 64bit OS from the settings, it does not crash anymore. Below is the Vbox.log file from a crashed machine (after machine was force shut down).
",yurtesen
16123,"Host: Windows 10 x64, Guest: Debian x64. Host gets unusable, kind of freezes.",Windows,VirtualBox 5.1.8,2016-10-27T08:25:31Z,2016-12-07T09:59:30Z,2016-12-07T09:59:30Z,"Hi,

first my Setup:

Host:
CPU: Intel i7-6700K.
GPU: NVIDIA GeForce GTX 1060, Driver: 372.90.
Windows 10 64-Bit. Avira Antivirus.
VirtualBox 5.1.8

Guest:
Debian 8.6.0 amd64.


Basically most functionality works fine. The VM starts and works like a charm. But after a few minutes of using the Debian-Guest the Host begins to act strange. On the Windows 10 Host i can't start new Windows anymore. The Processes start, as seen in the Task-Manager, but no Windows appear. Already before started Programs in already running Windows are still working perfect, except something like System-Monitor Desktop-Widgets, which are freezing. Even the Start-Menu doesn't show up, if i click on the Windows-Banner. Ctrl+Alt+Del brings me a BlackScreen.
From this Point the VM still works great. But if i try to shut it down, VirtualBox freezes completely.
The only Way to get the Host back working from this Point is the Hard-Reset-Button.
Maybe a compatibility Problem between the Virtualization and the Graphics-Driver. I encountered a similiar Problem some time ago with another Virtualization Solution on another Platform, where it caused the NVIDIA Driver to collapse.",DenKr
16262,shared folder not write-able for non-root users for special windows folders,Windows,VirtualBox 5.1.10,2016-12-03T16:01:53Z,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
16250,Display resolution capped at 1024x768,Windows,VirtualBox 5.1.10,2016-11-30T22:58:53Z,2016-12-01T17:28:20Z,2016-12-01T17:28:20Z,Just installed 5.1.10 r112026 Qt5.6.2 and tried to get Lubuntu running on a Win 7/64 workstation with dual 1920x1080 displays. Tried setting everything in sight including preferences but the Lubuntu VM still shows a capped display size. Similar to bugs: 15997  15788  15310,stkvbox
14727,"With Windows 10 host, VirtualBox guest window jumps between monitors",Windows,VirtualBox 5.0.6,2015-10-21T13:25:08Z,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
16235,latest Guest Additions crash linux guests after installation and rebooting the guest,Windows,VirtualBox 5.1.10,2016-11-26T18:44:03Z,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
16226,vbox file is missing after adding port-forwarding config while guest is running and later guest shutdown,Windows,VirtualBox 5.1.10,2016-11-24T12:33:46Z,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
15558,"VBoxDrvStub error: Unknown image file (NtCreateFile, Unknown Status - 5633)",Windows,VirtualBox 5.0.24,2016-06-29T16:06:49Z,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
16218,"Win10 host Ubuntu 16.04 guest, graphics problems",Windows,VirtualBox 5.1.10,2016-11-23T10:09:57Z,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
16214,Blocking delay when switching Guest and Host,Windows,VirtualBox 5.1.4,2016-11-22T14:35:14Z,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
15560,Linux guest on Windows 10 host keeps freezing,Windows,VirtualBox 5.0.24,2016-06-30T07:27:56Z,2016-11-15T22:38:46Z,2016-11-15T22:38:46Z,"I have a current Debian testing VM running on a current Windows 10 host.
It started to freeze very frequently with 5.0.22. 5.0.23 r108298 (and subsequently 5.0.24) reduced the frequency of the freezes, but did not quite eliminate them.

I experienced this freeze while running Knoppix 7.6.1 on 5.0.23 r108298 as well.

The kernel started out as a 4.5 version and was upgraded to 4.6 recently (shortly before VBox 5.0.24 was released but after my switch to 5.0.23 r108298).

It seems likely that this ticket is related to #15529, as the freezes started happening with the same release and the ACPI code change revert seems to have helped (reducing the frequency of the freeze from one every couple of minutes to once or twice a day).

The symptoms for the 5.0.24 freeze were:
* While actively working with the VM, it suddenly stopped responding.
* Most of the video was frozen, with the notable exception of an open but not focused tab in Chromium - the ""page is loading"" animation remained functional.
* The VM stopped responding to SSH login attempts.
* The VM stayed this way for about 15 mins, until I forcibly turned it off.
* I tried to see whether exiting fullscreen mode would make a difference - it did not.
* After the freeze, the VM displayed no apparent disk or CPU activity.

Unfortunately, neither my notebook not my keyboard have status indicator leds, so I cannot tell whether a kernel panic occurred.",ancow
16180,windows host crashes when memory is full,Windows,VirtualBox 5.1.8,2016-11-11T14:08:48Z,2016-11-11T15:03:37Z,2016-11-11T15:03:37Z,"I have recently started to get windows BSODs when the guest VMs are trying to allocate too much memory.

I am running Win 8.1 64bit on a laptop with 16GB of RAM, and have 2 VMs open at the same time with 8GB of memory set to each, so there is obviously some over-provisioning going one.
This works fine until some heavy-duty operation starts in one of the VMs. What happens then is:
- windows slows down to a crawl - I can see screen and cursor refreshes
- I can briefly see the 'vm has been suspended because of lack of memory' dialog box popping up
- the win BSOD kicks in

This did not happen until recently (version 5.1.8) at the moment, but it might be simply due to the fact that I was not using intensively 2 VMs with memory over-provisioning before.

The windows event log says:

L’ordinateur a redémarré après une vérification d’erreur. La vérification d’erreur était : 0x0000007e (0xffffffffc0000005, 0xfffff8015d657f50, 0xffffd0005c195d78, 0xffffd0005c195580)

The guest OS is dDebian 8.6

Note that the VM additions inside the VMs might not correspond exactly to the version of VBox running.",gggeek
16174,HPE Smart Storage Administrator utility lockup error 851,Windows,VirtualBox 5.0.26,2016-11-09T17:01:13Z,2016-11-09T17:01:13Z,2016-11-09T17:01:13Z,"Long time we have curious trouble with virtualbox.
HOST W2012 64 SERVER HP ProLiant ML310e Gen8
When we use smart array gui or utility , this report on Dynamic Smart Array B120i RAID
851 Controller lockup error: Restart the server and run a diagnostic report. Install the latest version of controller firmware. If the condition persists, the controller may need to be replaced or require service 

This error ocurs when virtualbox is run and use direct hardware access with VTx.
Guest os is openSUSE 64 13.1 

Issue not change more as year and last four kernels...

When vbox is off lockup not present, when no hardware direct , too no lockup, but Linux guest system is unstable .

Raid Works ok with or without lockup, but with lockup we cant control raid status. HP utility show nothing in error state.

Dynamic Smart Array B120i RAID controller have latest drv and fw.
Issue tested on 5.0.4 - 5.0.26 i mean next too but not tested now.

Please help.
",mguru
16151,[5.1.6 & 5.1.8] - Failed to open a session for the virtual machine,Windows,VirtualBox 5.1.8,2016-11-04T17:29:21Z,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
16147,Error in supR3HardenedWinReSpawn (System32\ntdll.dll rc=-626),Windows,VirtualBox 5.1.8,2016-11-04T10:49:21Z,2016-11-04T12:47:38Z,2016-11-04T12:47:38Z,"VirtualBox on my machine is failing to start any virtual machine.  I'm sure the log can explain what's going on better than I can, so I've attached the log.

Thanks for any help you can provide,
skippythegoat",skippythegoat
16136,VirtualBox not detecting VMs started on boot,Windows,VirtualBox 5.1.8,2016-11-02T02:04:21Z,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
15666,VirtualBox 5.1.0 and 5.1.2 fails to import digitally signed appliance (OVA file),Windows,VirtualBox 5.1.2,2016-07-22T19:20:52Z,2016-10-30T21:07:22Z,2016-10-30T21:07:22Z,"When attempting to import appliance from ova file, VBoxMAnage.exe fails with:


{{{
C:\Users\...\Downloads>""C:\Program Files\VirtualBox\VBoxManage.exe"" import <path to OVA file>
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Appliance read failed
VBoxManage.exe: error: Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)"" at line 307 of file VBoxManageAppliance.cpp
}}}

Import from GUI ends with error dialog:

{{{
Failed to import appliance <path to OVA file>.

Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed).

Result Code: E_FAIL (0x80004005)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}
}}}

There is no relevant information in logs except:

{{{
00:40:08.764715 ApplRead ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)}, preserve=false aResultDetail=0
}}}


I have seen the same behavior on Windows 7 x64 and Windows 10 x64. On another Windows 7 appliance import finished with information popup stating that certificate cannot be verified. 

The same OVA file can be successfully imported using VirtualBox 5.0.X and software of other vendors. 

Content of ""*.mf"": 

{{{
SHA1(ERA_Appliance-disk1.vmdk)= 44f1d187daa9f6ed129381eec155ece99530bfee
}}}

and content of ""*.cert"":

{{{
SHA1(ERA_Appliance.mf)= 7334b00ada502ae4420c9c01ba5c6baf1809e0539a0ca74da780d00b38c89c8fedc6be81f8d8e2e4626a7e0d1e5c19dae2beaded0abde864584b4b1a8dc80294a42e92960ee40a0065a5dfb06a088b8435690475c14a828256b2137c433f868b0bb284c343e84c55c0bc609ea1269f773cbd24269e98b89a2d98332a0aad49d147f3246d47183ee9bf916a4a0b3a774afa49aa885953e1c4535199c86ac59579d07f02a34a68c466becf471cec3d3de7c46fc859740e3cb7dbc7cf8ece6afecbe2baa4072dbe8e7692e58e8a596f2a76499f7c886ab45281608c22e7e4be47da67800eba89627365febeb40bed86c01b3c1706fffc5685bda2d840c3f1c64169
-----BEGIN CERTIFICATE-----
MIIFTjCCBDagAwIBAgIQHeEN7VQdUec7xIb0kkmINjANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykxMDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAxMCBDQTAeFw0xNjA0MTkw
MDAwMDBaFw0xOTA3MTkyMzU5NTlaMIGvMQswCQYDVQQGEwJTSzERMA8GA1UECBMI
U2xvdmFraWExEzARBgNVBAcTCkJyYXRpc2xhdmExGzAZBgNVBAoUEkVTRVQsIHNw
b2wuIHMgci5vLjE+MDwGA1UECxQ1RGlnaXRhbCBJRCBDbGFzcyAzIC0gTWljcm9z
b2Z0IFNvZnR3YXJlIFZhbGlkYXRpb24gdjIxGzAZBgNVBAMUEkVTRVQsIHNwb2wu
IHMgci5vLjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKW9l/iFn1Y/
BJouXaVLHs6+TlhWgZztdjUWtyuF6FHJaHk8eaU3UbtZJuKzINeg+VLdVCk1O8RN
w2P1XRoDecxb5W2m7rX4sUrBHvYY62G6KDYHxzWYqfCLNkgC8R5gpkKtYHROwg4W
HP0h+OnRBv0ojYoP8q/lNma1pTcABOQVmYVm8Rg7/NaAmqAAquk0n03Y2+y5rfh2
G2FM3xlLzjBocephZeS30ZxkUhm12TnTf9P+0ZB7j0f8V7N9ecZy8NeUaTSWmjkW
czxbwjphePpK9A4xAaca5uoNrvQV4SarnAM1iVJb+zyA/qMRhR78giyfOVQjDGoX
Q2U0XovY/HECAwEAAaOCAV0wggFZMAkGA1UdEwQCMAAwDgYDVR0PAQH/BAQDAgeA
MCsGA1UdHwQkMCIwIKAeoByGGmh0dHA6Ly9zZi5zeW1jYi5jb20vc2YuY3JsMGEG
A1UdIARaMFgwVgYGZ4EMAQQBMEwwIwYIKwYBBQUHAgEWF2h0dHBzOi8vZC5zeW1j
Yi5jb20vY3BzMCUGCCsGAQUFBwICMBkMF2h0dHBzOi8vZC5zeW1jYi5jb20vcnBh
MBMGA1UdJQQMMAoGCCsGAQUFBwMDMFcGCCsGAQUFBwEBBEswSTAfBggrBgEFBQcw
AYYTaHR0cDovL3NmLnN5bWNkLmNvbTAmBggrBgEFBQcwAoYaaHR0cDovL3NmLnN5
bWNiLmNvbS9zZi5jcnQwHwYDVR0jBBgwFoAUz5mp6nsm9EvJjo/X8AUm7+PSp50w
HQYDVR0OBBYEFIKSJNBoZdrPFMTF6cPzFNk4c63aMA0GCSqGSIb3DQEBBQUAA4IB
AQDzz/hCjjc1kc15nqKjnFy/oiRPDhQpM+C5/bputO8q0AE0uUv17DcGuPQgbQsG
7gfDr4x2suxJfxasRBU2OKKWZfpUfuALqIC5oHviD/8UPU3gk8m+LiwgYr13i5sN
ujbBeUaa4WfzrQo+7+GvdfKPw/NpHnmrDSSRadM0AckpyhrLRqMkgVjvIz7t00Yd
AQoBhFvQTaOk/I8iIQqsQcK0qyVbdOJFnO7Wu16XNeSb0TxqFzXCsGoI0qDUCatm
1uDWPzIKL7omFDrKNxxGZhCoJAV4btgZE1Ys6NFWazUa43//lGl11f6pncXv7BQf
sIlwnYi5uqq1MvtD1mV57wWh
-----END CERTIFICATE-----
}}}",koso
16124,Sudden crash of VirtualBox.exe,Windows,VirtualBox 5.1.8,2016-10-27T13:21:29Z,2016-10-29T12:18:35Z,2016-10-29T12:18:35Z,"It happens from time to time that the running Virtual Machine suddenly crashes, without any particular action on the guest system other than using it normally.
For example, last time I was just about to enter a search term into the address bar of the Firefox Browser of my Ubuntu 14.04LTE guest system when it crashed. The moment I clicked on the address bar, VirtualBox crashed. This was only one example of many crashes.

Unfortunately, the appearing error message doesn't say much (see attached screenshot) and from the log file I couldn't find an answer either. It looks like it didn't log anything.
",tacarrie
15901,Copyig files over USB hangs with USB 3 support,Windows,VirtualBox 5.1.4,2016-09-08T05:40:42Z,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
15706,VBoxClient pidfile no copy paste on second running image.,Windows,VirtualBox 5.1.2,2016-07-28T08:34:27Z,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
4088,Noticeable audio latency,Windows,VirtualBox 2.2.2,2009-05-24T10:00:58Z,2016-10-22T15:52:58Z,2016-10-22T15:52:58Z,"There is a noticeable delay between when the guest operating system starts to play a sound, and when it actually becomes audible. Perhaps in the range of 100-200 ms--just a guess though, I'm not sure how to time it.

The host is Vista Home Basic x64 and the guest is Debian running Linux 2.6.26.",Sam Morris
16096,"with a socks proxy set in gnome, guest OS randomly freeze black screen",Windows,VirtualBox 5.1.6,2016-10-20T19:42:29Z,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
16065,Cannot create symlink inside shared folder on Windows host,Windows,VirtualBox 5.1.6,2016-10-12T20:59:18Z,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
15990,VirtualBox 5.x CLI cannot display snapshot list while VM is running,Windows,VirtualBox 5.1.6,2016-09-26T19:07:28Z,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
15754,Sound duplication in headless mode,Windows,VirtualBox 5.1.2,2016-08-05T18:36:13Z,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
16034,Connection lost in guest when restart failed due to lack of memory,Windows,VirtualBox 5.0.26,2016-10-05T14:30:24Z,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
16017,Only one CPU usable Windows 10 Hyper-V Bug,Windows,VirtualBox 5.1.6,2016-10-03T09:23:28Z,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
16006,virutal machine paused with clonezilla,Windows,VirtualBox 5.0.24,2016-09-30T10:32:21Z,2016-09-30T10:32:21Z,2016-09-30T10:32:21Z,"when i'm trying to clone from a vmdk image to a physical disk, the virtual box pause itself with warning when clonezilla has written the partition table to the new disk and ""informing the OS of partition table changes...""

The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Fehler ID: 
BLKCACHE_IOERR
Dringlichkeit:
Normaler Fehler
",mholzer
15992,"Win10 Host, Ubuntu 16 guest, seamless mode, Multiple Virtual Windows",Windows,VirtualBox 5.1.6,2016-09-27T15:18:30Z,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
15814,Virtualbox closes unexpectedly.,Windows,VirtualBox 5.1.4,2016-08-17T23:18:11Z,2016-09-27T12:55:22Z,2016-09-27T12:55:22Z,"100% reproducible on my x86 Win7 host. Open attached VM, then ''vm settings -> Storage -> select any controller -> click on the blue thingy (add new stor. controller) on the window's bottom -> choose optical drive or hard disk''. After that the whole vbox gui closes.",tico-tico
15181,Video Capturing broken within guest systems with 3D enabled,Windows,VirtualBox 5.0.14,2016-02-26T16:55:37Z,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
15960,Copying of HTML from windows host to Firefox on a Linux guest doesn't work,Windows,VirtualBox 5.1.6,2016-09-20T16:57:31Z,2016-09-26T07:18:07Z,2016-09-26T07:18:07Z,"I don't know if it is a problem of Firefox or of VirtualBox itself. Copy-pasting HTML works perfectly fine to e.g. Chrome and LibreOffice Writer. But for some reason it doesn't work if pasting is done to Firefox. Though if you copy HTML directly from the linux guest (e.g. from Chrome, Firefox or LibreOffice) and paste to Firefox on the same guest - it works fine. I've also tried to examine the content of X11 clipboard in the guest and ""text/html"" target seems to be perfectly fine (when obtained with some tools like xclip). I've also tried to write the exact content of ""text/html"" provided by VirtualBox in the guest to the X11 clipboard (with ""xclip -t text/html -selection clipboard"") - and if I do that, then pasting works fine as well. It would be really great, if you could confirm that the problem is in the way how Firefox reads the content and not in the way how VirtualBox is providing this content to Firefox - then I would create a bug ticket on the Firefox bug tracker instead. 

Thnx in advance if you decide to investigate this issue.",mskov
15974,python host.create_host_only_network_interface returns bad object,Windows,VirtualBox 5.1.6,2016-09-22T22:21:10Z,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
15957,"GUI of guest Fedora 24 4.7.3-200.fc24.x86_64 freeze ""blank"" on login screen",Windows,VirtualBox 5.1.6,2016-09-19T20:22:45Z,2016-09-21T22:39:03Z,2016-09-21T22:39:03Z,"I'm using VirtualBox version 5.1.6 r110634 on Windows with Fedora 24 4.7.3-200.fc24.x86_64 as guest, both updated to the last patch.

I have the last version of the Guest Additions installed.

And I operate the Guest full screen.

The guest GUI freeze on the login, leaving a blank screen, only the background color is visible, forbidding any action with the mouse or keyboard, apparently.

To refresh the GUI after a mouse or keyboard typing I have to click on the toolbar of the host, to restore the Windows screen.

When I switch back to the guest, the guest screen is updated.

After the login screen all comes back to normality.

",par7133_2
14348,Video playback freezes in Linux guests with KVM paravirtualization enabled,Windows,VirtualBox 5.0.0,2015-07-30T00:49:30Z,2016-09-15T11:36:18Z,2016-09-15T11:36:18Z,"When KVM paravirtualization is enabled in VirtualBox 5.0.0 Linux guest operating systems fail to playback video. This is apparent with all video tested, including web video using Flash or HTML5. This has been tested on Antergos, Mint 17.2, and Fedora 22. Host Operating systems used to confirm this bug were Windows 8.1 and Windows 10.",Markon101
15876,Some modern application show corrupted graphic in 3D accelerated mode,Windows,VirtualBox 5.1.4,2016-09-02T07:37:41Z,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
15918,"Bad 3D performance, maybe related to: VERR_BAD_EXE_FORMAT atikmdag.sys",Windows,VirtualBox 5.0.26,2016-09-12T09:10:25Z,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
15909,No notification of major new releases,Windows,VirtualBox 5.0.26,2016-09-08T13:06:06Z,2016-09-08T13:06:06Z,2016-09-08T13:06:06Z,"VB 5.0.26 was released on July 18, 2016. It wasn't until I browsed virtualbox.org on Sept. 8, 2016 that I learned that there was a major dot release (x.0 to x.1) available that had two maintenance releases after July 18. It appears that the built in upgrade notification is failing to notify when stable dot releases are available (I am assuming that a second maintenance release of a dot release = stable).",Aren Cambre
15857,Defect: 5.1.4 Shared Folders not showing in Ubuntu Linux Guest from  Win7 Host,Windows,VirtualBox 5.1.4,2016-08-27T07:12:42Z,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
14421,Copy/paste not (always) working from host to guest,Windows,VirtualBox 5.0.0,2015-08-10T07:41:10Z,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
7919,VM VirtualBox Manager GUI crash when deleting snapshot,Windows,VirtualBox 4.0.0,2010-12-27T13:54:39Z,2016-08-26T10:56:07Z,2016-08-26T10:56:07Z,"Host: Win7 x64[[BR]]
Guest: SLES 10 SP3 x64 w/o GA[[BR]]

Manager GUI crashes when trying to delete (merge) snapshot for running machine.[[BR]]
It is reproducible on new machine.[[BR]]
If snapshot has saved state it loses it before crash.
That VM and other ones are not affected and are running.",Alil
15492,Some apps not displaying correctly,Windows,VirtualBox 5.0.20,2016-06-09T12:23:26Z,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
15819,Videos doesn't work,Windows,VirtualBox 5.1.4,2016-08-18T13:16:42Z,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
7492,Need a progress indicator during Snapshot creation,Windows,VirtualBox 3.2.8,2010-09-17T14:38:51Z,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
15755,Windows 7 64bit Host - VirtualBox 5.1.2 r108956 The network operation failed,Windows,VirtualBox 5.1.2,2016-08-05T20:58:06Z,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
15767,"Keyboard capture often escapes to host when using the ""Windows"" key (Windows host, Linux guest)",Windows,VirtualBox 5.1.2,2016-08-08T19:02:54Z,2016-08-08T19:02:54Z,2016-08-08T19:02:54Z,"I'm not quite sure when this started happening, but it happens to me a lot now (VBox 5.1.2).

My guest VM uses xmonad, and I set it so that using Win-1, Win-2, Win-3, switches desktops. Many times, when I am keyboard-captured, and I start switching desktops, one of them will suddenly escape and do stuff in my Windows host...

How to reproduce:
- Run a Linux guest, Windows host.
- Set it so that your keyboard is captured in the guest.
- Start mashing the Windows key with any other key, like 1, 2, 3, Left.

Effect:
- Within a few seconds of mashing, your host's Windows menu will pop-up.

I tested it with three different keyboards and two different machines.",Ptival
15736,Crash in crPackExpandDrawElements () from /usr/lib64/VBoxOGLpackspu.so,Windows,VirtualBox 5.0.24,2016-08-03T11:54:32Z,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
15328,usb mouse does not work after migrating to 5.0.18,Windows,VirtualBox 5.0.18,2016-04-21T07:18:46Z,2016-08-03T09:47:26Z,2016-08-03T09:47:26Z,"if I setup guest 5.0.18 addons in linux guest , mouse seems available but no cursor is displayed.
if I remove completely guest kernel modules addons, mouse is working.
if I setup 5.0.16 guest addons and run 5.0.18 host , the mouse does not work , graphic system runs badly.


",sancelot
15404,Windows 10 - Failed to create the host-only adapter,Windows,VirtualBox 5.0.20,2016-05-11T08:55:23Z,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
15656,"mouse disappears in virtualbox, linux installation menu",Windows,VirtualBox 5.1.0,2016-07-21T15:48:18Z,2016-07-21T15:48:18Z,2016-07-21T15:48:18Z,"First of all, Sorry for my bad English!

my mouse disappears in virtualbox, to be exact in the linux installation menu. I can't choose any of the option system. I mean I can't choose ""Install, or anything"" I've a laptop, I tried to use USB mouse, but it didn't work. I used the insert guest additions, and turned off/on the 3D acceleration. both isn't working. I changed my Pointing device, from USB Multi-Touch tablet to USB Tablet. 

Can anyone help me please? What should I do?",Hisham
15341,Unexpected closure of guest when clicking menubar item in fullscreen,Windows,VirtualBox 5.0.18,2016-04-24T05:43:00Z,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
15605,Full screen bug,Windows,VirtualBox 5.0.20,2016-07-13T19:10:47Z,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
15595,RDP sends scroll wheel events to wrong monitor,Windows,VirtualBox 5.0.24,2016-07-12T16:10:46Z,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
9688,Private host network problem => Fixed in SVN,Windows,VirtualBox 4.1.4,2011-10-04T13:44:08Z,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
14236,Qt5 developed app not displaying correctly in Linux Cinnamon desktop guest,Windows,VirtualBox 4.3.28,2015-07-03T15:53:00Z,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
15540,Can't run Unity Editor due to openGL errors,Windows,VirtualBox 5.0.22,2016-06-21T15:43:03Z,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
15535,Host files with (illegal) colon in filename not visible in shared folder,Windows,VirtualBox 5.0.22,2016-06-20T09:53:47Z,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
15468,drag and drop not bidirectional,Windows,VirtualBox 5.0.20,2016-05-31T16:24:29Z,2016-05-31T16:24:29Z,2016-05-31T16:24:29Z,"Hi, I have a Windows 10 Host, with a Ubuntu 15.10 guest, Virtual Box and Guest addition latest version. When I drag and drop files from guest to host no problem, when I do it from host to guest my files go only in /tmp/VirtualBox dropped files and not where I dropped them.
I attached log files, hope it helps.
Thanks",rok
15318,seamless mode does not work after upgrade to VirtualBox 5.0.18 Oracle VM Guest Additions on Ubuntu Guest,Windows,VirtualBox 5.0.18,2016-04-19T08:28:11Z,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
15460,Windows 10 VB Error Drag N Drop Not Working N Others More,Windows,VirtualBox 5.0.20,2016-05-30T13:00:20Z,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
15442,"Virtualbox doesn't refresh any window, unless you resize it. Can't use any vm at all.",Windows,VirtualBox 5.0.20,2016-05-24T11:01:19Z,2016-05-24T16:35:03Z,2016-05-24T16:35:03Z,"After installing 5.0.18, because 5.0.20 would give a critical error while installing. I tried to load my vm into virtualbox, however, nothing in virtualbox seem to refresh, so when i click on the map to import my vm, it doesn't refresh, i have to resize the window in order to refresh. When i run the vm i get a black screen, while in the preview view of virtual box i see that it works. (using windows 10, virtualization is enabled in bios, 16gb ram, 980m GT video card, should work)",TheCodeKing
15437,"""VBoxManage list runningvms"" does not work with the windows taskplaner",Windows,VirtualBox 5.0.20,2016-05-20T17:05:53Z,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
15434,Host only adapter is not working after host wake up,Windows,VirtualBox 5.0.20,2016-05-19T17:43:05Z,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
15415,Drag and Drop is not working bith direction,Windows,VirtualBox 5.0.20,2016-05-14T01:25:34Z,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
15419,vboxguest: module verification failed: signature and/or required key missing - tainting kernel,Windows,VirtualBox 5.0.20,2016-05-15T13:33:57Z,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
15350,"Cannot use , (comma) as a shortcut key",Windows,VirtualBox 5.0.16,2016-04-25T16:29:00Z,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
15312,Ubuntu doesn't get to desktop when 3D acceleration is enabled,Windows,VirtualBox 5.0.16,2016-04-15T17:20:34Z,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
15291,Linux Gest - Console black in Full Screen,Windows,VirtualBox 5.0.16,2016-04-04T11:55:38Z,2016-04-04T11:55:38Z,2016-04-04T11:55:38Z,When running Debian (current version 8.3) on a Windows host (Windows 8.1 Pro) in fullscreen switching from Gnome desktop to one of the other ttys (e.g. Hostkey-F1 to get tty1) results in a black screen. Doing the same in window mode (but maximized) does work fine.,jeansen
15276,copy&paste alter guest opened file,Windows,VirtualBox 5.0.10,2016-03-26T15:40:26Z,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
15237,random BSOD on Win7 x64,Windows,VirtualBox 5.0.16,2016-03-11T17:12:10Z,2016-03-23T03:51:32Z,2016-03-23T03:51:32Z,"Got several random BSOD on my WIN7 Dell Laptop while having Vbox running.


",theetete
15266,VirtualBox 5.0.16 - Windows 10 Host- Bridged Network,Windows,VirtualBox 5.0.16,2016-03-22T21:05:11Z,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
7968,Protocol error with junctions in shared directory,Windows,VirtualBox 4.0.0,2010-12-31T15:17:31Z,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
14703,shared folders not mounting,Windows,VirtualBox 5.0.6,2015-10-15T07:10:04Z,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
14572,Can't recover the IP when USB2Ethernet adapter is removed and reconnected.,Windows,VirtualBox 5.0.0,2015-09-11T04:27:22Z,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
11980,guest additions should write system time to RTC after adjusting it,Windows,VirtualBox 4.2.16,2013-07-22T13:13:14Z,2016-03-11T12:45:48Z,2016-03-11T12:45:48Z,"When booting a Linux distribution using systemd, the system time is not automatically written to the RTC during shutdown. For further information & rationale, see <http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html>.

As a result, booting my system under VirtualBox results in the following:

{{{
Jul 22 03:46:06 wintermute kernel: rtc_cmos rtc_cmos: setting system clock to 2013-07-22 02:46:03 UTC (1374461163)
...
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: Superblock last write time is in the future.
Jul 22 03:46:07 wintermute systemd-fsck[443]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: clean, 340335/39321600 files, 138917904/157286139 blocks
...
Jul 22 03:46:08 wintermute systemd[1]: Started LSB: VirtualBox Linux Additions.
Jul 22 13:57:43 wintermute systemd[1]: Time has been changed
}}}

After boot, we can observe the RTC is still wrong:

{{{
$ date
Mon 22 Jul 14:10:15 BST 2013

# hwclock -r
Mon 22 Jul 2013 03:58:44 BST  -0.070616 seconds
}}}

After the guest editions have set the system clock from the host clock, they should set the hardware clock to match. That is, perform the equivalent of `hwclock --systohc`.",Sam Morris
15207,Guest kubuntu freezes just after dektop completes loading (more often if loading while virtualbox is not in focus),Windows,VirtualBox 5.0.16,2016-03-05T12:47:27Z,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
14410,"Linux-on-Windows 3D support slow, buggy and generates lots of errors",Windows,VirtualBox 5.0.0,2015-08-06T19:20:44Z,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
13933,VirtualBox 4.3.24 Could Not Initialize GLX,Windows,VirtualBox 4.3.24,2015-03-06T18:14:56Z,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
10759,Can't kill Virtualbox.exe process,Windows,VirtualBox 4.1.18,2012-07-13T20:31:09Z,2016-02-23T02:41:25Z,2016-02-23T02:41:25Z,"Windows 7 64 bit Host.
Ubuntu 11.10. OS will lock when running certain programs and the virtualbox.exe process will keep running at 25% cpu. Can't kill it in the command line or in task Manager. Only option is to reboot the host Windows 7. ",speedkills20
15132,Problems getting native resolution on Windows 10,Windows,VirtualBox 5.0.14,2016-02-09T21:24:04Z,2016-02-16T19:06:25Z,2016-02-16T19:06:25Z,"This ticket concerns how to get native resolution in the Virtualbox graphical frontend when running under a Windows 10 host.

By ""native resolution"", I mean a 1-1 mapping between pixels on the display and pixels in the frontend fullscreen window.

My setup is a laptop with a 2736x1824 screen. Connected to this, I have an external monitor with a 2560x1440 resolution.

The behavior I expect from the frontend is that I always get native resolution when I select a scale factor of 100% in the View menu.

The behavior I get is somewhat complicated. It seems like there are two states: I either get native resolution on the laptop monitor or the external monitor. The switch between these two states goes through Windows display settings:

Assume that we have everything working as expected on the laptop display, with native resolution in the Virtualbox frontend.

Now we connect the external monitor and choose to use only that monitor. When we now select fullscreen in the frontend we only get some scrambled rectangles on the screen. However, if we go from a scale factor of 100% to 125%, we get a screen with proper content, but with a high resolution (higher than the display) from the point of view of the guest, scaled down to fit the display.

Going now to Windows display settings, there is a red sentence saying that we need to sign out in order for all apps to adjust to the new scaling (resolution?). Doing that and restarting the guest and the graphical frontend, we now get (for a 100% frontend scale factor) native resolution.

The same thing happens again when going back to the laptop display.

This is clearly a bug since one shouldn't have to save the machine state, sign out and in again, and restart the vm for every monitor switch. I wish there was a way for Virtualbox to ignore the Windows weirdness and simply have a hard mapping between 100% scale factor and native resolution.

I attach a log from a run where I fail to get native resolution on my laptop display (but do get it on the external monitor).",Mikael Djurfeldt
15151,Ubuntu on VirtualBox crashes when laptop goes to hibernate,Windows,VirtualBox 5.0.14,2016-02-15T13:38:42Z,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
15147,Guest OS cannot see Host in Bridged Mode,Windows,VirtualBox 5.0.14,2016-02-13T05:45:37Z,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
15136,After upgrade Virtual Box 5.0.14 does not recognise USB Key,Windows,VirtualBox 5.0.14,2016-02-10T09:56:47Z,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
15089,Unable to setup base OS using virtual box,Windows,VirtualBox 4.3.28,2016-01-28T23:40:50Z,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
5568,unable to perform some svn operations on shared folders from guest,Windows,VirtualBox 3.0.12,2009-11-26T06:32:34Z,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
14905,Error In supR3HardNtChildWaitFor,Windows,VirtualBox 5.0.10,2015-12-06T21:10:26Z,2016-02-01T09:27:14Z,2016-02-01T09:27:14Z,"Since last week I've been encountering problem with starting Linux virtual machine. It's now starting about 2 minutes and before start it throws an error (in attachment: error-screenshot.jpg).
I've disabled my Avira antivirus real-time protection but it doesn't help, I hadn't installed any additional software before bug started to appear (only Avira Antivirus had made it's update).",DSProgrammer
15083,Win 7 / Linux Guest - Cannot delete backup file on shared folder.,Windows,VirtualBox 5.0.14,2016-01-27T17:29:59Z,2016-01-27T17:29:59Z,2016-01-27T17:29:59Z,"When a backup~ file is created in a directory within a VirtualBox's shared folder, the program that created the backup~ file cannot remove the file preventing the original file from being saved. Trying to remove the backup~ file manually via 'rm' results in an 'Operation not permitted.' message. The only way to remove the backup~ file is navigating to the directory from the Host system and removing the file that way.",agilis
15076,Wifi connections goes off,Windows,VirtualBox 4.3.36,2016-01-25T18:15:47Z,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
13648,VirtualBox 4.3.20 Could Not Initialize GLX,Windows,VirtualBox 4.3.20,2014-11-27T01:15:36Z,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
15044,"WebGL doesn't work, OpenGL shows warnings",Windows,VirtualBox 5.0.12,2016-01-19T21:01:39Z,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
15026,VB Crashes after creating a machine,Windows,VirtualBox 5.0.12,2016-01-11T15:30:08Z,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
15017,I get black screen after log out desktop environment.,Windows,VirtualBox 5.0.12,2016-01-09T04:31:46Z,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
13967,NatNetwork limits mtu,Windows,VirtualBox 4.3.26,2015-03-18T13:43:20Z,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
13946,Unable to Use USB devices on Virtual box,Windows,VirtualBox 4.3.24,2015-03-09T15:09:41Z,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
14939,VM VirtualBox 5.01 on Windows 10 has excessive disk activity when running Debian 7.0.0,Windows,VirtualBox 5.0.10,2015-12-17T14:57:04Z,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
14926,kernel 4.2 incompatible headers structure,Windows,VirtualBox 5.0.10,2015-12-13T01:36:25Z,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
14924,GNU/Linux guest aborts while saving when 3D acceleration is enabled,Windows,VirtualBox 5.0.10,2015-12-12T18:00:46Z,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
14424,Shared folder seems to cache old file content for the guest after editing host files,Windows,VirtualBox 5.0.0,2015-08-10T13:39:45Z,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
14911,Black screen with OpenGL only in full-screen mode,Windows,VirtualBox 5.0.10,2015-12-08T14:52:38Z,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
14597,5.0.4 - Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR,Windows,VirtualBox 5.0.4,2015-09-16T06:44:47Z,2015-11-25T16:09:23Z,2015-11-25T16:09:23Z,"I've been using VirtualBox for a while 4.3.18 - 4.3.30 where i have a VM with a live snapshot.
after upgrading to 5.0.4 i've got a problem on my 4.3.30 created VM: ""Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR""
reverting back 4.3.30 runs the VM fine but not with 5.0.4

Host: Windows 7 x64
guest: Linux based OS

see also: 
[https://forums.virtualbox.org/viewtopic.php?f=6&t=70070]
",talr
10764,VirtualBox 4.1.18r78361 prevents Windows 7 host from sleeping/entering standby,Windows,VirtualBox 4.1.18,2012-07-15T17:20:19Z,2015-11-17T06:22:45Z,2015-11-17T06:22:45Z,"While VirtualBox is running, my Windows 7 host OS will not enter standby/sleep after the time of inactivity specified in my Windows power scheme has elapsed.  When I close VirtualBox, Windows sleeps after the time specified in the power scheme.  This problem started after I upgraded to 4.1.18r78361.  This is very inconvenient because I like to keep my guest OS running, so I have to remember to put my host computer into standby whenever I leave the computer or it will needlessly stay on.",bgx90
14803,E_FAIL (0x80004005) Critical Error on Windows 10 (Build 1240),Windows,VirtualBox 5.0.10,2015-11-11T10:36:24Z,2015-11-11T10:36:24Z,2015-11-11T10:36:24Z,"I can't run VM session with Comodo Internet Security installed on my PC. (CIS 8.2.0.4703). 


{{{
The virtual machine 'name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\name\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

}}}
",netak
14398,webcam on Lenovo T550 with CentOS 7.1 guest,Windows,VirtualBox 5.0.0,2015-08-05T18:53:20Z,2015-11-04T15:32:51Z,2015-11-04T15:32:51Z,"Hi.

I'm running VirtualBox 5.0.0 under Win7 on a Lenovo T550 laptop. 
My guest O/S is CentOS 7.1.
On the Win7 system, the integrated laptop webcam works perfectly.
If I export the webcam to the Linux guest O/S (ie. in the ""Devices"" menu, under Webcams, ""Integrated Camera"" is selected.), then the guest O/S sees the webcam as well (uvcvideo, 04ca:703c).
In the guest O/S, if I start ""cheese"" (a tool to take pictures and video from the webcam), I should see a live preview of the webcam input.  The light on the camera does go on and stays on, but rather than displaying the live preview, I get the first frame that cheese saw when it was started.  That frame doesn't change.  I can click ""take picture"" over and over but it will capture the identical frame.
If I change the video resolution in cheese, then the frame changes one more time.

I tried on an older VirtualBox version 4.3.18, and the problem is identical.
I tried with CentOS 6, under both VirtualBox versions 4.3 and 5.0 (with proper guest extensions), and had the same problem.
I tried with a Lenovo T540p laptop (previous generation of this laptop), and the live preview in cheese worked on both 4.3 and 5.0.

It's important to note that the problem is not explicit to just ""cheese"".  For example, if I visit the following URL in Firefox:

http://mdn-samples.mozilla.org/s/webrtc-capturestill/

This is a WebRTC demo.  In the left box, I should see a live preview of my webcam.  I get the same problem (1 frame).  The same demo works properly on the underlying Linux box, and from the T540p laptop.

I installed a CentOS 7.1 system from scratch with no vbox, and the camera works fine with cheese (and demo above).
I installed VirtualBox 5 on this CentOS 7.1 system, and then installed the same VM that was having the cheese problem, and the video passes through perfectly as well!
I would guess this means that the issue is in the Windows Extension pack.

I'm really really anxious to resolve this issue soon because I really need it for later this month.  If there's any help that I can provide, please let me know.

Jason.",kangaroo
10563,guest addition functions degrade with guest runtime,Windows,VirtualBox 4.1.8,2012-05-14T21:26:15Z,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
14719,OpenGL Warnings,Windows,VirtualBox 5.0.6,2015-10-19T17:54:29Z,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
14704,Windows special folders mount as read only when shared,Windows,VirtualBox 5.0.6,2015-10-15T08:46:37Z,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
14699,"Wrong icon for ""Other Linux (64-bit)""",Windows,VirtualBox 5.0.2,2015-10-14T18:54:55Z,2015-10-14T18:54:55Z,2015-10-14T18:54:55Z,"Choose[[BR]]
Type: '''Linux'''[[BR]]
Version: '''Other Linux (64-bit)'''[[BR]]


Icon the same as for '''Other Linux (32-bit)''' without 64 in left top corner.",bmx666
13705,"Windows 7 Host and Linux guest, BSOD on host",Windows,VirtualBox 4.3.20,2014-12-20T05:41:09Z,2015-10-05T22:30:45Z,2015-10-05T22:30:45Z,"I ran 4.3.12 for quite awhile.  After I jumped to 4.3.20, I am now getting BSOD every now and then.  I've done a memory scan, just to be sure I don't have failing RAM.  Anything else I can do to get more information?

I'm not sure if the windows event viewer files are useful or not, but I'm attaching them.",Trent
14638,VT-x is not available Error while launching Android VM,Windows,VirtualBox 5.0.4,2015-09-25T22:26:28Z,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
14616,Firefox.com Firefox can't completely Download files,Windows,VirtualBox 5.0.4,2015-09-21T13:46:37Z,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
14569,Full screen flicker Linux guests,Windows,VirtualBox 5.0.4,2015-09-10T14:12:23Z,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
14561,Failed to open a session for the VM (0x80004005  Component:  MachineWrap),Windows,VirtualBox 5.0.4,2015-09-09T11:14:15Z,2015-09-09T11:29:06Z,2015-09-09T11:29:06Z,I have a problem. Not start a new VM,SergeyO
14559,"GUI: ""Ungroup"" fails",Windows,VirtualBox 5.0.4,2015-09-09T08:31:38Z,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
14539,Extreme screen flashing and guest unusable,Windows,VirtualBox 5.0.2,2015-09-03T17:58:30Z,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
14537,Linux grsecurity guest kernel will not mount shared folders,Windows,VirtualBox 5.0.2,2015-09-03T15:44:23Z,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
14322,BSOD on Windows 7 upon hibernating while VirtualBox is open,Windows,VirtualBox 4.3.30,2015-07-24T14:06:23Z,2015-09-02T21:52:59Z,2015-09-02T21:52:59Z,"I have a recurring problem where I get a blue screen of death when I hibernate my computer while I have VirtualBox open. I'm running Windows 7 64-bit with a xubuntu on Ubuntu 14.04 (trusty) guest. I'm also using version 4.3.30 of virtualbox and version 4.3.24 of the guest additions. My BSOD provided the following information: the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL, and was attributed to VBoxNetFlt.sys. I ran WinDbg on the MEMORY.DMP (full dump, not minidump) and got the following info:

{{{
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03253890
    Debug session time: Fri Apr 10 15:50:18.376 2015 (UTC - 4:00)
    System Uptime: 3 days 14:35:58.020
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    
    Loading unloaded module list
    ................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {112337, 2, 0, fffff80003076615}
    
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+10634 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000112337, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003076615, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  0000000000112337 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertQueueApc+69
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800bffb710 -- (.trap 0xfffff8800bffb710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80003341a58 rbx=0000000000000000 rcx=000000000011232f
    rdx=fffffa800a6373e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003076615 rsp=fffff8800bffb8a0 rbp=fffff880009e8180
     r8=0000000000000001  r9=000000000011231f r10=fffff880009e8c01
    r11=fffffa800fd26b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KiInsertQueueApc+0x69:
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8] ds:00000000`00112337=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003083469 to fffff80003083ec0
    
    STACK_TEXT:  
    fffff880`0bffb5c8 fffff800`03083469 : 00000000`0000000a 00000000`00112337 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0bffb5d0 fffff800`030820e0 : fffff880`0bffb738 fffff800`03083153 ffffffff`8000297c fffffa80`105c1060 : nt!KiBugCheckDispatch+0x69
    fffff880`0bffb710 fffff800`03076615 : fffff880`00000001 fffffa80`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0bffb8a0 fffff800`030656b0 : fffffa80`105c1060 00000000`00000000 00000000`00000078 fffffa80`0a6373d0 : nt!KiInsertQueueApc+0x69
    fffff880`0bffb8d0 fffff880`04c10634 : 00000000`00000000 00000000`778e7ac0 00000000`00000078 00000000`000007ff : nt!KeInsertQueueApc+0x80
    fffff880`0bffb930 fffff880`04c107b4 : 00000000`0000ed04 fffff880`04c3cf50 ffffffff`8000397c fffffa80`1769b6c0 : avgidsdrivera+0x10634
    fffff880`0bffba10 fffff880`04c10866 : ffffffff`8000397c fffffa80`1769b6c0 fffffa80`168f6520 00000000`000007ff : avgidsdrivera+0x107b4
    fffff880`0bffbac0 fffff880`04c2925c : 00000000`00000001 fffff880`0bffbba8 fffffa80`0fd26b50 fffff880`0bffbba8 : avgidsdrivera+0x10866
    fffff880`0bffbb10 fffff800`0337cb43 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`0fd26b50 : avgidsdrivera+0x2925c
    fffff880`0bffbb40 fffff800`0308da95 : fffff800`03338b00 fffff800`0322b201 fffffa80`0fd26b00 fffffa80`00000000 : nt!IopProcessWorkItem+0x23
    fffff880`0bffbb70 fffff800`03322b8a : fffffa80`105029d0 fffffa80`0fd26b50 00000000`00000080 fffffa80`0698eb30 : nt!ExpWorkerThread+0x111
    fffff880`0bffbc00 fffff800`030758e6 : fffff880`03365180 fffffa80`0fd26b50 fffffa80`06d40290 00000000`07fa1011 : nt!PspSystemThreadStartup+0x5a
    fffff880`0bffbc40 00000000`00000000 : fffff880`0bffc000 fffff880`0bff6000 fffff880`0bffb8a0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    avgidsdrivera+10634
    fffff880`04c10634 84c0            test    al,al
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  avgidsdrivera+10634
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avgidsdrivera
    
    IMAGE_NAME:  avgidsdrivera.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55128c2a
    
    FAILURE_BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    Followup: MachineOwner
    ---------
}}}

Please provide any assistance you can on determining the cause of and solution to this problem.",Anomaly13
13847,vpnc no response from target after upgrade to 4.3.20 and 4.3.22,Windows,VirtualBox 4.3.22,2015-02-17T14:20:10Z,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
13828,Drag-and-drop not working in either direction,Windows,VirtualBox 4.3.22,2015-02-13T14:28:32Z,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
14514,VM freezes during installation of guest,Windows,VirtualBox 5.0.2,2015-08-28T07:09:02Z,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
14513,OpenGL error with 3D acceleration enable with black screen,Windows,VirtualBox 4.3.30,2015-08-27T20:58:30Z,2015-08-27T20:58:30Z,2015-08-27T20:58:30Z,"Hi,

I'm running Ubuntu 14.04 lts trusty 64 bit on 4.3.30 r101610 on Win 7 host 64 bit.
I'm getting too many OpenGL warning and my rendering screen is going black. I'm
running gazebo robotic simulator. However if I do not use hardware acceleration then everything work fine and there are no warning. But then by simulation run very slow.
I've done almost everything regarding this issue as this is not new. I've installed the VBoxGuestAddition_4.3.30.iso. Before installing the guest addition the 3d hardware acceleration work fine and I do not get openGL warning. However I'm not able to go to fullscreen.
I've also installed latest virtual box extension pack.

Please share any suggestion.",AmitUbu
14403,Symlinks are created incorrectly on shared directories,Windows,VirtualBox 5.0.0,2015-08-06T08:59:44Z,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
14463,Symlinks in shared folders don't work after upgrading to 5.0.2,Windows,VirtualBox 5.0.2,2015-08-17T19:39:47Z,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
14470,NAT Network failing to provision gateway,Windows,VirtualBox 5.0.2,2015-08-18T18:56:35Z,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
13748,Java8 GUI Apps not working in Linux guest,Windows,VirtualBox 4.3.20,2015-01-08T07:55:52Z,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
14261,Bridge network,Windows,VirtualBox 5.0.0,2015-07-11T09:53:19Z,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
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,VirtualBox 5.0.0,2015-08-04T09:03:59Z,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
14387,Application Error when Plugging/Unplugging HDMI for second display,Windows,VirtualBox 5.0.0,2015-08-04T13:10:09Z,2015-08-04T13:10:09Z,2015-08-04T13:10:09Z,"When unplugging/plugging in HDMI cable for second display on my laptop, I receive dialog ""VirtualBox.exe - Application Error"", ""The instruction at 0x80165d4a referenced memory at 0x00000018.  The memory could not be read.""

I am running a Windows 8.1 host, with Ubuntu 14.04 as the guest.",cmo
13582,3D fails in Ubuntu 14.10 Guest,Windows,VirtualBox 4.3.18,2014-10-31T16:43:31Z,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
14299,GUI should disable snapshot delete on running VM,Windows,VirtualBox 5.0.0,2015-07-19T12:52:52Z,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
14240,Oracle Linux 6.6 wont start on init 5 after install guest additions,Windows,VirtualBox 4.3.28,2015-07-04T14:12:51Z,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
14212,(ipv6) multicast NS are not delivered to the guest,Windows,VirtualBox 4.3.28,2015-06-19T11:56:51Z,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
14242,3D Accelerate Grayed Out (Can't disable after moving VM),Windows,VirtualBox 4.3.18,2015-07-04T23:28:40Z,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
14230,VirtualBox ISession get_Console returns S_OK but IConsole ptr is NULL,Windows,VirtualBox 4.3.28,2015-06-29T15:52:54Z,2015-06-29T15:52:54Z,2015-06-29T15:52:54Z,"Hi,

I am running into a strange thing here. My (pseudo) code (see below) works fine on Windows 7 SP1 / 64bit with 64bit VirtualBox and 64bit app binary.
But when I compile the stuff not as x64 but Win32 (32bit binary on SysWOW64), the app crashes because get_Session returns S_OK but the delivered pointer IConsole * is NULL !!!
Is this a bug or is it not possible to run a Win32 binary on Win7/64 with VirtualBox/64? I thought that it should be completely transparent using Microsoft COM?
Here is the pseudo code:

{{{
BSTR machineName = SysAllocString(L""VMName"");
IMachine *pMachine = NULL;
if (FAILED(pVBOX->FindMachine(machineName,&pMachine)))
{//do error stuff}
if (FAILED(pMachine->LockMachine(pVBOXSession,LockType_Write)))
{//do error stuff}
pMachine->Release, pMachine = NULL;
if (FAILED(pVBOXSession->get_Machine(&pMachine))) // get mutable one
{// do error stuff}
IConsole *pConsole = NULL;
if (FAILED(pVBOXSession->get_Console(&pConsole)))
{// do error stuff }
}}}

[...]
At this position, pConsole is NULL on Win32 (SysWOW64) and not NULL on Win64 (x64).
Any ideas?

Thank you.




",vboxcomapijunkie
13841,Oracle Vbox crashes on full screen,Windows,VirtualBox 4.3.22,2015-02-16T15:22:58Z,2015-06-29T05:41:28Z,2015-06-29T05:41:28Z,"While trying to view in full screen Vbox crashes with error ""the instruction at 0x000000000 referenced memory at 0x000000000. The memory could not be written."" ",ddfedora21
13526,Memory leak with 3D acceleration with Ubuntu lens,Windows,VirtualBox 4.3.18,2014-10-17T15:24:42Z,2015-06-20T00:47:09Z,2015-06-20T00:47:09Z,"I have a Windows 7 host and Ubuntu 14.04 guest. If I enable 3D acceleration, there is a huge memory leak (about 100 MB per second) when the Ubuntu main system menu (Unity lens) is open. It is apparently related to the blurring effect, since there is no leak if I disable 3D acceleration and Ubuntu just shows a plain colour background. 

The strangest thing is that I can see the memory being eaten away in my host's performance monitor, but the guest's performance monitor doesn't show any problem and the memory use is stable there. I hope this can be a clue as to where the problem lies.

I can work with 3D disabled but the system is totally unusable with it enabled, since the memory leak is so severe.

I attach a log file",rgargente
14213,NAT networking stops responding blocks all I/O on that interface for Ubuntu/Debian x64 guests,Windows,VirtualBox 4.3.28,2015-06-19T18:21:50Z,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
14207,VBoxManage unregistervm --delete performs only a partial deletion if media file is locked by other process,Windows,VirtualBox 4.3.28,2015-06-17T09:12:07Z,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
14180,when trying to open sagemath in oracle vm virtual box in windows 8.1 64 bit Blue screen of death happening,Windows,VirtualBox 4.3.28,2015-06-07T17:57:00Z,2015-06-08T14:12:35Z,2015-06-08T14:12:35Z,"Installation of Oracle VM Virtual Box and importing the sage ova file in it was not a problem. But when I started the sage machine Blue Screen of Death (DRIVER_VERIFIER_DETECTED_VIOLATION) happened. Otherwise my machine works fine. I was using Sage-6.7 ova file and Virtual Box 4.3.28.100309-win in a windows 8.1 64 bit machine. The problem persists for 4.3.12.93733-Win version also. For my machine OS, drivers BIOS everything is up to date. Hard disk health is good. No issue of Virus or malware. I have not installed the guest additions.More than 100 GB space is available in machine. Any help will be appreciated.",amritendu
14169,vboxsf: files with illegal (:) characters truncated on host's NTFS shared folder / results in data loss,Windows,VirtualBox 4.3.28,2015-06-03T06:50:04Z,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
14158,Memory Leak on Windows 7 Host VBox  4.3.28 r100309. Host Mem 45%-90% in 3 Hrs.,Windows,VirtualBox 4.3.28,2015-05-29T17:47:50Z,2015-05-29T17:47:50Z,2015-05-29T17:47:50Z,"Vbox Details
 Version 4.3.28
 Guest Additions 4.3.28.iso
 Operating System: Ubuntu 14.04
 System:
  Base Memory: 3GB
  Processors: 4
  Execution Cap: 95%
  Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX
 Display:
  Video Memory 64 MB
  Screens: 2
  Acceleration: 3D

Host Details:
 Operating System: Windows 7
 RAM: 8GB
 Processors: 8
 
After starting the Virtual Machine VirtualBox.exe Memory(Private Working Set) rises to about 416,416 K. Within 3 hours of working inside the VM It will rise to roughly 2,000,000 K at which point the host alerts me to low memory. If I don't restart the VM eventually it will completely freeze and crash.

Typical Programs running in VM
Firefox
Sublime-Text-2
Terminal
Libre Office Writer/Spreadsheet
File Manager

In the host VirtualBox is typically the only program I'm running. I was wondering if maybe not having Admin permissions on the account I'm using is causing a problem? Although I did give VirtualBox all the rights an admin account has. 
",dduke22
14157,Removing snapshot fails and leave VM in unbootable state,Windows,VirtualBox 4.3.28,2015-05-28T11:24:14Z,2015-05-28T11:24:14Z,2015-05-28T11:24:14Z,"The VM had 2 snapshots and was running. I started the removal of the
first snapshot from the GUI.  This removal aborted with an error, and the running VM was somehow stopped (or killed).
Unfortunately, I don't have the error message any longer.

The bigger problem is that the VM was not bootable any longer; I think this is the error message in VBox.log.2:
{{{
00:00:04.189066 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false
}}}

The next attempt to start the VM resulted in an error messag that a required snapshot file was missing (in VBox.1.log):
{{{
00:00:02.948345 AIOMgr: Endpoint for file 'C:\Users\voelkerb\VirtualBox VMs\opensuse13.2\os13.2.vdi' (flags 000c0781) created successfully
00:00:02.983231 VMSetError: F:\tinderbox\win-4.3\src\VBox\Storage\VD.cpp(6370) int __cdecl VDOpen(struct VBOXHDD *,const char *,const char *,unsigned int,struct VDINTERFACE *); rc=VERR_FILE_NOT_FOUND
}}}

Creating a new snapshot in order to preserve the current state failed
with the same message.

The only way out was to revert to the last snapshot - without taking
a snapshot of the current state and thus loosing the work until that
last snapshot. ;-(

After that, the machine was still not bootable, but the media manager
complained about 2 missing differencing images.
After removing that, the VM could be started again, yet some work was
lost.

I experienced the same already 2-3 times in the past.

Host: Windows 7, guest: openSUSE-13.2",berny
14152,restoring my snapshot made web pages cannot connect to mysql,Windows,VirtualBox 4.3.28,2015-05-25T20:24:18Z,2015-05-26T12:52:01Z,2015-05-26T12:52:01Z,"Restoring snapshot made my webpages connection to Ubuntu guest cannot connect to Ubuntu guest mysql anymore

",virtualguys
13962,"VBoxClient: Failed to set graphics capability, rc=VERR_NOT_SUPPORTED",Windows,VirtualBox 4.3.26,2015-03-16T23:23:10Z,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
14120,unable to startvm with high priority on windows,Windows,VirtualBox 4.3.26,2015-05-15T14:39:58Z,2015-05-15T14:39:58Z,2015-05-15T14:39:58Z,"Reference forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=67715#p320669

I recently upgraded to 4.3.26 and now I'm unable to run my batch file that launched my VM with high priority because it seems that there are now 3 different processes that end up getting run. The parent process has the high priority but the actual VM does not which makes it slow. Here is the batch file, not much to it. Anyone found a workaround for this, or should I report it as a bug? 

Batch File contents:
start ""name"" /high ""C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"" --comment name --startvm 1941c965-3dc5-4326-85ae-4400ea58b90d

Things that I've tried without any success:
- running the batch file as admin
- setting VirtualBox.exe to always run as Admin",p1234
14093,AltGr issue on Windows 8.1 and Windows 7 with Czech keyboard layout,Windows,VirtualBox 4.3.26,2015-05-04T10:52:51Z,2015-05-15T13:18:34Z,2015-05-15T13:18:34Z,"This is weird issue, as I am not able to reproduce it alltime, but I know, after several hours of running guest it results in this weird issue.

Host: MS Windows 8.1 (64 bit) or Windows 7 (64 bit).
Guest: Debian Wheezy (64 bit) or Debian Jessie (64 bit).
Guests addons installed from Debian's contrib repository.

AltGr-a (~) is not working, when host keyboard layout is Czech, but works if keyboard layout is English USA. All other AltGr combinations (I use) work fine.

I have already investigated it using {{{xev}}}, I can see keystroke {{{ISO_Level3_Shift}}}, but no {{{a}}} keystroke, but for example AltGr-q (\) I can see both keystrokes.

Auto capture is disabled. When auto capture is enabled it works as expected, but it is not handy for me.

I see similar fixed issue #13216.

Offtopic: Is it possible to create Extension Pack, that will not capture several key combinations, so for example ctrl-alt-(anything) will not be captured even if auto capture feature is enabled?",xdml
14072,Win 8 host.  Cannot change Linux guest priority using Windows taskmgr.exe,Windows,VirtualBox 4.3.26,2015-04-22T19:11:30Z,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
13620,Inconsistent screen redraw when scrolling in Chromium,Windows,VirtualBox 4.3.18,2014-11-18T13:55:08Z,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
14049,VirtualBox NAT implementation tcp keep-alive problem,Windows,VirtualBox 4.3.10,2015-04-14T21:59:14Z,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
14042,VBoxNetFlt crashing windows 7 on resume,Windows,VirtualBox 4.3.26,2015-04-10T14:58:45Z,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
13968,Can't drag to select text in Google Chrome on Linux Guest,Windows,VirtualBox 4.3.26,2015-03-18T15:57:25Z,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
13949,All guests fail to start,Windows,VirtualBox 4.3.24,2015-03-10T13:54:37Z,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
13931,Excessive processor use,Windows,VirtualBox 4.3.24,2015-03-06T13:17:07Z,2015-03-10T09:47:37Z,2015-03-10T09:47:37Z,"Since 4.3.22 or so I noticed that after a while VBox is starting to use a lot of processor power. Everything is OK when it starts but after few hours its 90-100% of one thread and some minor-medium use on other threads (35%-40% of total processor time, i7 4770K, 4 cores 8 threads).

Host is Windows 8.1
Guest is 64bit Ubuntu 14.04

It was initially installed under 4.3.20 and there was no problem. It only appeared recently.",randomwhitetrash
13928,Change of behavior of Host Only Network,Windows,VirtualBox 4.3.24,2015-03-06T10:52:19Z,2015-03-06T10:52:19Z,2015-03-06T10:52:19Z,From version 4.3.22 you have added a value for *NdisDeviceType register entry. A value for that entry as NDIS_DEVICE_TYPE_ENDPOINT implies that Windows ignores the endpoint device when it identifies networks. I was using a virtual linux firewall connected to the bridged interface to create a network with different OS including the access to internet from the host. After this change in 4.3.22 Windows does not detect the virtual network and there is no connection from most windows applications.,luisds
13925,file timestamp not preserved on tar-extracted files in shared folders on linux guest windows host,Windows,VirtualBox 4.3.24,2015-03-05T17:36:29Z,2015-03-05T17:36:29Z,2015-03-05T17:36:29Z,"There is a strange behavior, that files extracted from TAR package within shared folders on Linux guest/Windows host, does not preserve file timestamp stored in a tarball. The files' timestamp get converted to the extraction time.

I've searched through Virtualbox issues, and saw another ticket regarding timestamp in shared folders, #6473, but that was solved years ago, and does not apply to this particular issue.

Issue is easily reproducable:
- configuration: Windows 7 Host, Linux (Debian, no GUI) Guest
- using tar command from a Linux Guest shell, create a TAR of an older ""test file"", so the timestamp would be evident,
- delete the ""test file""
- extract the ""test file"" from a tar archive
- the timestamp will be wrong, as tar preserves timestamp by default
- to confirm we can do the same procedure within another Linux Guest folder, other than the shared folder, and the timestamp will be preserved.

Here's code sample, presuming we have a file.pdf test file, within /var/www/shared folder, which is a shared folder, both Linux guest and Windows 7 host can see:

{{{
cd /var/www/shared
ls -la
> -rwxrwxrwx 1 root root 11654 Jan 23 08:16 file.pdf
tar -c -f test.tar file.pdf
rm file.pdf
tar -x -f test.tar
ls -la
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 file.pdf
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 test.tar
}}}

I would kindly ask anyone to answer if there is a solution to this problem, or is there anything we can do to preserve original timestamps at tar extraction process within shared folders, so we don't need to extract files in a separate folders and move the files back, as we need those timestamps.

We have both, current Virtualbox and current Guest Additions installed.",sargac
12860,"Linux guest aborts in VRDP, OpenGL mural warning",Windows,VirtualBox 4.3.8,2014-03-25T01:18:02Z,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
13879,Seamless mode tri-head hosts,Windows,VirtualBox 4.3.22,2015-02-22T11:32:48Z,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
12910,respect host-only settings on update / upgrade,Windows,VirtualBox 4.3.10,2014-04-04T08:22:32Z,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
13832,VirtualBox 4.3.22 Breaks Physical Network Card Config,Windows,VirtualBox 4.3.22,2015-02-13T18:11:52Z,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
11995,Saving Ubuntu guest in full-screen mode causes guest X session hang when resuming. Windows 8 host.,Windows,VirtualBox 4.2.16,2013-07-27T04:41:12Z,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
12819,Host fails to read NTFS folder which is mounted to some partition,Windows,VirtualBox 4.3.8,2014-03-13T18:14:42Z,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
13779,vobxsf breaks on long paths (> 260) with Windows host,Windows,VirtualBox 4.3.20,2015-01-22T21:00:44Z,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__
13704,No Window Decorations in Zorin 9 after Guest Additions - VirtualBox 4.3.20,Windows,VirtualBox 4.3.20,2014-12-20T05:00:26Z,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
7736,SATA disks not found after reboot into linux (ICH9 only),Windows,VirtualBox 3.2.10,2010-11-19T10:25:07Z,2015-01-07T22:26:38Z,2015-01-07T22:26:38Z,"Situation:
 * I have a IDE hdd with a linux installation on it, as well as grub.
 * I have a IDE cdrom with an image of windows XP on it.
 * I have a SATA hdd with windows XP on it, or nothing

I want to boot the linux OS, which will determine if the windows XP partition is available and has booted correctly. If this is the case, a grub-reboot is issued to boot into windows XP once, otherwise the image is restored onto the HDD.
If I reboot from windows XP, the linux OS should do the above again.

On an actual machine, the procedure works without a hitch.

However after a reboot from windows XP to linux (Start | Shut Down... | Restart) the linux suddenly can't find the SATA disks.
dmesg has the following lines:
{{{
[    6.166426] ata1.00: qc timeout (cmd 0xec)
[    6.166426] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.516437] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   16.517619] ata1.00: qc timeout (cmd 0xec)
[   16.517619] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   16.517619] ata1: limiting SATA link speed to 1.5 Gbps
[   16.866406] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   46.866424] ata1.00: qc timeout (cmd 0xec)
[   46.866424] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   47.216399] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   47.566424] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   52.566425] ata2.00: qc timeout (cmd 0xec)
[   52.566425] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   52.916425] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   62.916398] ata2.00: qc timeout (cmd 0xec)
[   62.916398] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   62.916398] ata2: limiting SATA link speed to 1.5 Gbps
[   63.266424] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   93.266437] ata2.00: qc timeout (cmd 0xec)
[   93.266437] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   93.616439] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
}}}
Attached is the full vbox.log and the full dmesg as I have it.",Mike Musterd
13731,High CPU load when smooth-scrolling,Windows,VirtualBox 4.3.20,2015-01-04T02:26:32Z,2015-01-04T02:26:32Z,2015-01-04T02:26:32Z,"I have noticed that when smooth-scrolling in either Firefox or Chrome, either by continuously running the mouse wheel, or by mid-click to activate auto-scroll and then moving the cursor slightly to slowly start scrolling, I get very high CPU load. At usual reading pace I can often get 70-80% CPU, slightly less when I scroll slower. This surprises me, since scrolling really shouldn't be a CPU intensive task! Under the Windows host, smooth scrolling never takes any CPU at all. Also, the Linux guest feels a bit more sluggish when scrolling compared to the Windows host. I am running Compiz, and 3D is generally working well (if using the 3D-box desktop, and it rotates nicely).

It is a bit of a bother, since this significantly reduces battery time: When just browsing the web, I scroll while reading, and this usually loads the CPU high enough to spin up the fan. Obviously, all that heat is a battery drain!

I am using a dual-boot Windows 8.1 and Windows 7 host with an Ubuntu 14.04 LTS guest on an ASUS 550JV laptop (Core I7-4700HQ, 16GB RAM and nVidia GT-750M). I have seen this on Virtualbox 4.3.12 (with guest additions 4.3.14) and on 4.3.20 (with guest additions 4.3.20). Virtualbox has one core and 6GB RAM. 3D in general is working well, as mentioned.",00prometheus
13723,Gnome 3 window decoration issue on Debian guest with 3D acceleration enabled,Windows,VirtualBox 4.3.20,2014-12-30T17:19:05Z,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
13721,Machine Shared Folders and Repeatable Serial Numbers (Win),Windows,VirtualBox 4.3.20,2014-12-28T22:47:15Z,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
10955,APC UPS Driver and VirtualBox issue,Windows,VirtualBox 4.2.0,2012-09-18T00:14:30Z,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
13574,VirtualBox keeps resizing the guest to 1 screen,Windows,VirtualBox 4.3.18,2014-10-30T11:15:06Z,2014-12-18T19:39:20Z,2014-12-18T19:39:20Z,"Since updating to VB 4.3.16 and 4.3.18 from 4.3.12 it is impossible to resize the guest operating system to more than 1 screen.

I run Windows 7 and I have 3 screens and I have enabled Auto-Resize Guest Display.

It is possible to drag the bottom right corner of the guest window, but as soon as it is released there are some flickering and the window is resized to be as width as 1 screen.
The guest OS display is internally of the size I resized to, but there is a horizontal scrollbar.

The guest OS is Fedora 19 fully updated.

Guest OS additions are installed.

As soon as I downgradeto 4.3.12 the problem goes away and it is 100% reproducible with 4.3.16 and 4.3.18. I have never tried 4.3.14.

I have a NVIDIA NVS 310 card.

Some other users have reported it here

https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",mariolino
13664,Guest additions failed after upgrading to 4.3.20 on ubuntu 14.04.1 LTS guest / W7 host,Windows,VirtualBox 4.3.20,2014-12-02T13:40:44Z,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
13304,"Generic GL Renderer used, leading to crash when accessing 3D functionality.",Windows,VirtualBox 4.3.14,2014-08-20T09:50:53Z,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
13341,Chipset and problems,Windows,VirtualBox 4.3.14,2014-09-03T12:51:28Z,2014-11-24T12:30:55Z,2014-11-24T12:30:55Z,"Host  - Windows 2003 Std (32 bit)
Guest - Oracle Linux 6.5 (64 bit)

VirtualBox-4.3.14-95030-Win and VirtualBox-4.3.15-95713

If Chipset set to '''PIIX3''':[[br]]

The network is working properly.

# cat /proc/cpuinfo 
> processor	: 0[[br]]
> vendor_id	: GenuineIntel[[br]]
> cpu family	: 6[[br]]
> model		: 23[[br]]
> model name	: Intel(R) Xeon(R) CPU L5420  @ 2.50GHz[[br]]
> stepping	: 6[[br]]
> microcode	: 0x60b[[br]]
>> cpu MHz	: 0.000[[br]]
> cache size	: 6144 KB[[br]]
> physical id	: 0[[br]]
> siblings	: 4[[br]]
> core id		: 0[[br]]
> cpu cores	: 4[[br]]
> apicid		: 0[[br]]
> initial apicid	: 0[[br]]
> fpu		: yes[[br]]
> fpu_exception	: yes[[br]]
> cpuid level	: 5[[br]]
> wp		: yes[[br]]
> flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl pni ssse3 lahf_lm[[br]]
> bogomips	: 4571.13[[br]]
> clflush size	: 64[[br]]
> cache_alignment	: 64[[br]]
> address sizes	: 38 bits physical, 48 bits virtual[[br]]
> power management:[[br]]

[[br]]
[[br]]
If Chipset set to '''ICH9''':[[br]]

# cat /proc/cpuinfo[[br]]
...[[br]]
cpu MHz  : '''2394.048'''[[br]]
...[[br]]

Network interface not work (on guest network interface is up, but there is no network traffic)[[br]]
eth0 - RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)",PepeN
13625,Can't start virtualBox,Windows,VirtualBox 4.2.18,2014-11-19T16:41:16Z,2014-11-20T16:25:38Z,2014-11-20T16:25:38Z,"Échec de l'ouverture de session pour la machine virtuelle Linux Mint 17.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Code d'erreur : E_FAIL (0x80004005)
Composant : Console
Interface : IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

",EricG
13557,Virtualbox 4.3.18 disable logging,Windows,VirtualBox 4.3.18,2014-10-27T08:52:34Z,2014-11-14T11:41:47Z,2014-11-14T11:41:47Z,"I have set system user variables:
{{{
VBOX_RELEASE_LOG_DEST=nofile
VBOXSVC_RELEASE_LOG_DEST=nofile
VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile
}}}

But one file still appears. ""VBoxStartup.log"" under `\VirtualBox VMs\(Machine name)\Logs`. How can I disable all log files?",karlsson
13440,can't share folders after yum update,Windows,VirtualBox 4.3.16,2014-09-27T03:48:08Z,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
11900,Windows host cannot see / follow symlinks in shared folder from Linux guest,Windows,VirtualBox 4.2.12,2013-06-25T15:36:49Z,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
9926,No virtual system boot with grub2 on mbr for raw disk access to specific partitions,Windows,VirtualBox 4.1.6,2011-11-20T18:53:01Z,2013-04-04T06:48:32Z,2013-04-04T06:48:32Z,"Recent Linux systems, such as Fedora 16, use the newer grub2 boot loader.  The usual grub2 setup places the boot code on the mbr and on the unpartitioned sectors immediately follow the mbr partition.  If a virtual guest Linux system is made using raw parition access to Linux code on a partition(s) separate from the host system partition(s), the grub2 boot code is not accessible unless the whole disk is attached rather than just the partitions containing the guest system.

For example, with a Windows 7 64bit host on partition 3 of disk 0 and Fedora 16 on partitions 5 and 6, and with grub2 installed on the mbr of disk0, VirtualBox will not boot a Fedora 16 x86_64 guest unless the vmdk is created with whole disk access to disk0.  If the vmdk is created with access to only partitions 5 and 6, Fedora does not boot and hangs after the boot code in the mbr is executed.  The code in the sectors following the mbr sector is not reached.  Given that it is dangerous for the virtual system to have direct access to the host operating system code, the grub2 boot code should be accessible when only individual partitions are attached.  For Windows hosts, the -relative option is not available for createrawvmdk so this option cannot be tested as a solution with Windows hosts.
",Leo Pilachowski
11640,"vboxsf does not support noatime,nodiratime,discard options",Windows,VirtualBox 4.2.10,2013-03-25T01:30:53Z,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
11514,Time sync: incorrect host time,Windows,VirtualBox 4.2.6,2013-02-22T13:49:40Z,2013-02-26T15:01:24Z,2013-02-26T15:01:24Z,"I have noticed that I do not get the time set correctly on my virtuals machines. They do sync but are always behind the host's time (which is set per ntp correctly) and funnily the times between several VMs running on the same host vary.

When I started to dig for the reason I started VBoxService with -vvv and saw that the Host time displayed there was not the actual time of the host (i.e. the windows machine on which the VMs are running).

I expected the time shown in the log as ""Host:"" would be the host time, e.g:
{{{
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z
}}}
Unfortunately it differs from the hosts time. Even more suspicious: it differs differently on various VMs of the same host.
Could this be the reason why time sync does not work correctly?

Below more debug output.

{{{
root@orpdm-03:~#  /usr/sbin/VBoxService -f -vvv --enable-timesync --timesync-interval 1000
VBoxService 4.2.4 r81684 (verbosity: 3) linux.amd64 (Oct 26 2012 19:49:17) release log
00:00:00.002083 main     Log opened 2013-02-22T13:37:48.290070000Z
00:00:00.002159 main     OS Product: Linux
00:00:00.002180 main     OS Release: 3.2.0-37-generic
00:00:00.002199 main     OS Version: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002388 main     OS Service Pack: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002412 main     Executable: /opt/VBoxGuestAdditions-4.2.4/sbin/VBoxService
00:00:00.002415 main     Process ID: 31071
00:00:00.002418 main     Package type: LINUX_64BITS_GENERIC
00:00:00.002608 main     4.2.4 r81684 started. Verbose level = 3
00:00:00.002766 main     Initializing services ...
00:00:00.003517 main     Service client ID: 0x24
00:00:00.003767 main     VMInfo: Property Service Client ID: 0x25
00:00:00.003810 main     VBoxServiceBalloonInit
00:00:00.003847 main     MemBalloon: VbglR3MemBalloonRefresh failed with VERR_PERMISSION_DENIED
00:00:00.003942 main     Service 'memballoon' was disabled because of missing functionality
00:00:00.003965 main     VBoxServiceVMStatsInit
00:00:00.004058 main     VBoxStatsInit: New statistics interval 0 seconds
00:00:00.004102 main     VBoxServiceAutoMountInit
00:00:00.004353 main     VBoxServiceAutoMountInit: Service Client ID: 0x26
00:00:00.004393 main     Starting services ...
00:00:00.004414 main     Starting service     'control' ...
00:00:00.004706 control  Waiting for host msg ...
00:00:00.004831 main     Starting service     'timesync' ...
00:00:00.005097 main     Starting service     'vminfo' ...
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z    (MinAdjust: 100 ms)
00:00:00.005341 vminfo   Writing guest property ""/VirtualBox/GuestInfo/OS/Product"" = ""Linux""
00:00:00.005413 timesync VBoxServiceTimeSyncWorker: Guest: - 2013-02-22T13:37:48.293063000Z => 119 171 937 000 ns drift
00:00:00.005509 timesync VBoxServiceTimeSyncAdjust: adjtime by 119 171 937 000 ns
}}}",Markus
11497,"When starting on user login in windows in fullscreen mode, vb loses focus",Windows,VirtualBox 4.2.6,2013-02-16T15:00:00Z,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
11397,Clipboard stops working,Windows,VirtualBox 4.2.6,2013-01-16T17:05:09Z,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
10986,Wrong mtime on shared folders,Windows,VirtualBox 4.2.0,2012-09-22T17:45:52Z,2012-09-24T12:07:45Z,2012-09-24T12:07:45Z,"Linux ""vboxsf"" shared folder system does not set correct modification time. It only happens then file is written with some data.
attachment contains repro code (gcc testts.c ; ./a.out)
",ajax16384
8038,Symbolic links in shared folders,Windows,VirtualBox 4.0.0,2011-01-08T19:37:48Z,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
10598,--timesync-set-on-restore syncs time up to 10 seconds after snapshot restore,Windows,VirtualBox 4.0.16,2012-05-24T13:44:54Z,2012-05-25T13:35:49Z,2012-05-25T13:35:49Z,"I have a Linux guest(additions 4.0.16) and a Windows host(vbox 4.0.16). The guest service is started via:
{{{
/usr/sbin/vboxguest-service -f -vvvvv --disable-vminfo --disable-cpuhotplug --disable-vmstats --disable-automount --disable-memballoon --timesync-set-threshold 1000 --timesync-set-on-restore 1
}}}

If I restore a snapshot of this machine, even one that is 7 days old, the time is not synced on restore.
~10 seconds (timesync-interval?) after resuming the VM, the vboxguest-service outputs ""The VM session ID changed, forcing resync."" and time is actually synced.

This causes trouble when working with certificates that are generated after taking the snapshot, so for some use cases this is really annoying.",insecure
10343,"Provide emulated hardware devices for video camera, scanners and video capture",Windows,VirtualBox 4.1.8,2012-03-17T16:47:54Z,2012-04-04T21:02:27Z,2012-04-04T21:02:27Z,"Virtualbox should add a virtual emulated device that a guest OS can use inside the VM to access video input and output devices and imaging devices such as scanners and video cameras, and capture cards, virtualbox would use the  application API of the host OSs to access the hardware through the Host OS driver, the application API for accessing the hardware drivers used by the  host OS as the backend for emulated devices provided to the guest OS. 

This is already what virtualbox does for sound cards, video cards, and network interfaces.

This in many cases is better than attempting to use the USB pass through. USB pass through does not work well when multiple OSs including many VMs need to share the device. Very rarely does pass through work right. It is just asking for trouble to occur to have many different drivers trying to directly cntrol the device. 

This is why it is best to only have one driver directly talk to the device, the Host OS driver, and then provide emulated devices inside the VMs that use the Host OS driver as a backend. The guest Os then only needs to load the driver for the device that virtualbox emulates. Virtualbox should choose to emulate a brand and model of each type of hardware that is particularly common and widely supported by many OSs.

What I suggest is have virtualbox emulate some hardware devices, like a scanner, USB web cam and a happauge video capture card. The emulation would then use the Host OSs application driver APIs as a backend and provide a virtual device in the VM for every real device accessible via the application driver APIs. Guest OSs would load the driver for the scanner, video capture card and camera device that would talk to the emulated hardware device. 

This would provide much smoother operation than  the horrid and buggy USB pass through. This is already done with video cards, network adapters and so on. ",David
10252,Switch to fullscreen with VBoxManage,Windows,VirtualBox 4.1.8,2012-02-14T16:52:49Z,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
10182,Auto capture keyboard shortcut host key not displayed in warning info,Windows,VirtualBox 4.1.8,2012-01-19T16:18:39Z,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
10175,auto mount shared folders immediately and not just after reboot,Windows,VirtualBox 4.1.8,2012-01-16T21:27:12Z,2012-01-16T21:27:12Z,2012-01-16T21:27:12Z,"When creating a shared folder and setting auto mount it will be mounted after reboot.
It will be helpful if the folder will be mounted immediately without requiring a reboot as well.

Tested on ubuntu 11.10 guest under win7 host.

Thanks",pablop
9036,"kernel WARNING ""sysfs: cannot create duplicate filename /devices/virtual/bdi/vboxsf-$SHARENAME""",Windows,VirtualBox 4.0.8,2011-06-06T19:12:45Z,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
9777,"The display panel in Ubuntu only shows the current resolution and 800x600, 640-480 - need better way to set specific resolutions",Windows,VirtualBox 4.1.4,2011-10-17T13:09:03Z,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
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,VirtualBox 4.1.4,2011-10-17T13:05:24Z,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
9706,Big minimizing machine in Full Screen dual monitor mode,Windows,VirtualBox 4.1.4,2011-10-06T19:28:34Z,2011-10-06T19:28:34Z,2011-10-06T19:28:34Z,"I'm running Windows 7 Professional 64 bit as the host and Ubuntu 11.04 as the guest.

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

When in full screen mode running dual monitors, if I click the minimize button on the VM tab with the VirtualBox controls for the machine, it only minimizes the primary monitor window and leaves the secondary monitor window maximized.  This should be fixed since the auto-resize feature in dual monitor mode in running an Ubuntu guest OS is still a little fragile.  Both windows should minimize when clicking the minimize button from the VirtualBox menu bar.",josiah
9472,"Minor regression in past several versions - ""Help...About Virtualbox..."" flashes off-screen before it can be read",Windows,VirtualBox 4.1.2,2011-08-20T07:18:49Z,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
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,VirtualBox 4.0.10,2011-07-02T15:11:58Z,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
9026,Keyboard problem on guest systems in w7 host,Windows,VirtualBox 4.0.8,2011-06-05T18:02:39Z,2011-06-10T04:53:11Z,2011-06-10T04:53:11Z,"I'm running VirtualBox 4.0.8 on 64-bit Windows 7 Home Premium with the latest updates.

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

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

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

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

",smeezekitty
8360,"when using existing ubuntu as a guest, vbox replaces xorg.conf",Windows,VirtualBox 4.0.4,2011-02-17T23:23:52Z,2011-04-13T13:39:34Z,2011-04-13T13:39:34Z,"I have a win7/ubuntu10.10 dual-boot. I installed virtualbox on win7 (host)
I followed these instructions http://chaits.accosted.net/?p=54 and created an instance out of an existing linux partition.
after I installed vb additions and extension, everything worked great in virtualbox. when i tried to boot into linux, the windows manager didn't lunch. xorg.conf was overwritten. 

Currently I have to sitch xorg.conf file manually if i want a graphical interface. 
i documented my experience [http://kirilligum.wordpress.com/2011/02/17/run-existing-linux-ubuntu-10-10-partition-in-virtualbox-under-host-windows-7-system-on-thinkpad-x201t/ here].",kirill
8426,Unable to lock down VBOX COM using DCOMCNFG,Windows,VirtualBox 4.0.4,2011-02-24T19:59:23Z,2011-02-24T19:59:23Z,2011-02-24T19:59:23Z,"I need to install VirtualBox in an environment that permits only a special user (vboxuser) to control virtual box.[[BR]]
[[BR]]
The problem is that on Windows XP, locking down VirtualBox is not working (could be a windows bug), any user can launch with VBOXSVC and then have complete control over VirtualBox (if the set VBOX_USER_HOME properly). Windows 7 works fine (UAC on and off).[[BR]]
[[BR]]
[[BR]]
Here are the steps to lock down the COM service:[[BR]]
1- Install virtualbox under any admin user[[BR]]
2- Create a new user (vboxuser), make it an admin.[[BR]]
3- Login to vboxuser and start DCOMCNFG as admin[[BR]]
4- Select Component Services --> Computers --> My Computer --> DCOM Config[[BR]]
5- Locate VirtualBox then right click on open Properties[[BR]]
6- Select Security Tab[[BR]]
7- Change Launch/Activation to SYSTEM and vboxuser (local launch and activation)[[BR]]
8- Change Access to SELF,SYSTEM and vboxuser (local access)[[BR]]
9- Change Configuration to SYSTEM, vboxuser (full control)[[BR]]
10- Click OK and make sure that virtualbox.exe can start under vboxuser[[BR]]
11- logoff from vboxuser and then log back in to your user.[[BR]]
12- Start virtual box, and it starts! That is the problem.[[BR]]
[[BR]]
On Windows 7 you would get an error (Access Denied) and it would only work if I use runas /user:vboxuser virtualbox.exe.[[BR]]
[[BR]]
The problem happens only on Windows XP SP3 x86 (I haven't tested any x64 versions)[[BR]]
[[BR]]
I tested another COM service, and the permissions seem to work on Windows XP.[[BR]]
Please let me know if you have any questions[[BR]]
[[BR]]
I was able to reproduce this problem using VBOX 4.0.4 and VBOX-OSE 3.2.18 (self compiled/installed)",rbhkamal
8282,Mini Toolbar/Quickbar unavailable if fullscreen changed to other host screen,Windows,VirtualBox 4.0.2,2011-02-05T22:51:59Z,2011-02-05T22:51:59Z,2011-02-05T22:51:59Z,"I am using 4.0.2 on Windows Vista host. (guest should be irrelevant, but is linux in case)

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

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

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

Switching temporarily to window mode, and back to fullscreen fixes the issue (as a work around) until the next host-monitor switch",Martin
8147,Adding devices to virtual SCSI controller will use reserved port 7,Windows,VirtualBox 4.0.2,2011-01-22T15:21:28Z,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
7761,additions install on Xen kernel,Windows,VirtualBox 3.2.10,2010-11-24T21:35:36Z,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
7476,2D Video Acceleration Error Message Should detect platform first,Windows,VirtualBox 3.2.8,2010-09-14T21:32:22Z,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
4754,Suggest a new function to install the VDI file to a real physical hardrive,Windows,VirtualBox 3.0.0,2009-08-12T00:49:45Z,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
6829,"Network Adapter dialog allows to select Bridged Adapter, that is not installed, but actually doesn't set this setting",Windows,VirtualBox 3.2.0,2010-05-28T14:18:53Z,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
5349,traffic get answered on the wrong VLAN,Windows,VirtualBox 3.0.10,2009-10-30T18:44:54Z,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
4961,Mouse wheel scrolling broken in Ubuntu 32 bit guest / Windows 7 host since 3.06,Windows,VirtualBox 3.0.6,2009-09-12T08:47:08Z,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
5076,Keyboard go crazy (miss map) after screen turn off and come back,Windows,VirtualBox 3.0.6,2009-09-25T01:35:08Z,2009-09-25T08:20:58Z,2009-09-25T08:20:58Z,"I just install the latest Virtualbox yesterday and i observed a very strange behavior. Below is the details description:

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

- Basically the problem is causing the host keyboard catching to go crazy. 
- Seem like the window key (special key) is lock up, so no matter what key i pressed, even is a single key (such as ""y"") but in the host window it seem like (window key + y).
- I try using VMware unity, it did not seem to have this problem. So i guess it is a bug. Has this bug being reported?",ntyonline
4057,ER: Simpler way of accessing Windows host printer from Ubuntu guest,Windows,VirtualBox 2.2.2,2009-05-20T08:47:09Z,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
2389,mount.vboxfs does not allow context= option,Windows,VirtualBox 2.0.2,2008-10-07T16:36:55Z,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
18330,Linux Mint 19.1 doesn't display on large monitor,Solaris,VirtualBox 6.0.2,2019-01-18T23:28:29Z,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
16366,Solaris x86 Host - Centos 7 Guest hangs after using all the memory,Solaris,VirtualBox 5.1.12,2017-01-08T11:24:22Z,2017-01-26T22:18:55Z,2017-01-26T22:18:55Z,Solaris x86 Host has 64GB Memory. Centos7 Guest VM given 16GB. After about 3-4 days the VirtualBox process consumes all 16GB and the VM is unavailable. Am able to stop and start the VM and it will stay running for another 3-4 days.,Buster Gonad
21278,UEFI Linux guest fails to boot in VB 7,other,VirtualBox-7.0.2,2022-11-16T20:35:08Z,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
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,VirtualBox 6.1.40,2023-01-21T17:29:50Z,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
21277,Ubuntu 22.10 Freeze/Crash,other,VirtualBox 6.1.40,2022-11-16T08:43:58Z,2023-01-04T12:43:43Z,2023-01-04T12:43:43Z,"I am currently using virtualbox version 6.1.40, and tried to install ubuntu 22.10 from https://ubuntu.com/download/desktop quite a few times, but every time there is a crash which i can reproduce it the easiest way like this:
1)Fire up virtualbox
2)Click ""Try Ubuntu""
3)Let it boot
4)Open Nautilus/File explorer
5)Right click on Music on left pane
6)The context menu starts glitching
7)VM hangs or crashes
8)Trying to close the VM using Close button causes it to stop responding

HOST: windows 10 21H2
GUEST: Ubuntu 22.10",thehardgamer
21082,"RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!",other,VirtualBox 6.1.36,2022-08-28T20:20:24Z,2022-11-27T18:44:59Z,2022-11-27T18:44:59Z,"On VirtualBox 6.1.36, Debian, Windows builds, upon starting both exiting Debian and Ubuntu virtual machines, the warning  '''RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! ''' comes up on boot after grub2.  Porting Debian virtual machine to VMWare Workstation Pro 15.5.7, Windows 11 build base contains no such boot errors.  Creation of new Ubuntu virtual machine from latest iso , virtualbox 6.1.36 gives same warning  RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! Creation of a new Ubuntu virtual machine in VMware gives no such warning.

PHY HW is Intel i5 (i5-8250u) and cpuinfo shows no cpu_insecure flag.

Did not test a Windows virtual machine in virtualbox to see if warning occurred.  

Suspect virtualbox code base is not patched against Spectre v2 or warning message not correct in conditional tree.  

Others reporting similar, see https://ubuntuforums.org/showthread.php?t=2477938",stdperson
21261,Microsoft Office 2013 not working if Guest Additions are installed,other,VirtualBox-7.0.2,2022-11-10T16:57:30Z,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
20927,Some nested qemu VM crashes at grub if launched in dozens,other,VirtualBox 6.1.32,2022-05-04T18:28:04Z,2022-05-04T18:28:04Z,2022-05-04T18:28:04Z,"Hello,

I'm using gns3 inside vbox with multiple virtual nodes (openwrt running as qemu vms). If I start all nodes at the same time, some of them crashes during the grub countdown (or a even little bit before) with:

{{{
KVM: entry failed, hardware error 0x80000021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX=00000010 EBX=0000c866 ECX=00040000 EDX=0ff8f7c0
ESI=0ff8f760 EDI=00000005 EBP=00001ff0 ESP=00001ff0
EIP=000082fd EFL=00010006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     00008280 00000027
IDT=     00000000 000003ff
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=ef 82 00 00 08 00 66 b8 10 00 8e d8 8e c0 8e e0 8e e8 8e d0 <8b> 04 24 a3 f0 1f 00 00 a1 64 82 00 00 89 c4 89 c5 a1 f0 1f 00 00 89 04 24 31 c0 0f 01 0d
}}}

If I restart that nested VM, it should work as expected.

I didn't test 6.1.34 but this bug has been happening at least since 2020. 

I also opened an issue with gns3, but it is more likely to be a virtualbox issue:
https://github.com/GNS3/gns3-gui/issues/3330",Luiz Angelo Daros de Luca
20866,nao abre a sessao e consta esse erro,other,VirtualBox 6.1.32,2022-03-13T23:37:00Z,2022-03-13T23:38:14Z,2022-03-13T23:38:14Z,"Falha ao abrir uma sessão para a máquina virtual debian2.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",YuRi25
20818,Cannot build module virtualbox on Ubuntu server 20.04,other,VirtualBox 6.1.26,2022-02-09T11:02:45Z,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
20783,CentOS 9 Stream PXE boot failure,other,VirtualBox 6.1.30,2022-01-20T16:50:54Z,2022-01-20T16:53:41Z,2022-01-20T16:53:41Z,"Description of problem:
When installing el9 on a VirtualBox guest with an new vmdk files as the storage, the boot will fail with the error:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

A bug was submitted to Red Hat however the response is this is a VirtualBox issue.  For more details, please see/contribute to:
https://bugzilla.redhat.com/show_bug.cgi?id=2041094


How reproducible:
This consistently reproducible with implementing a work around. 

Steps to Reproduce:
1. VirtualBox 6.1.30 (Windows host)
2. Create a new Linux VM.
3. Create a new VMDK file as the disk device.
4. Boot the guest using PXE.

Actual results:
Kernel and initrd loads however the boot fails/stops with:

dracut: FATAL: iscsiroot requested but kernel/initrd does not support iscsi

Expected results:
Boot succeeds and ANACONDA start the installation.

Additional info:

If I install CentOS 8 on the guest/vmdk file and then reinstall with EL9, the installation succeeds.

I am attaching 2 console logs.  One is the initial attempt that fails.  The second contains the El8 then EL9 work-around for comparison.

",MatthewDva
20736,Error when i want use a ubuntu machine,other,VirtualBox 6.1.30,2021-12-18T20:28:51Z,2021-12-18T20:28:51Z,2021-12-18T20:28:51Z,"Hello, 

I'm on ubuntustudio and I use virtualbox 6.1.30. When I want to virtualize a ubuntu machine, i have an error message (file)
If i try to executing '/sbin/vboxconfig, i have an error , i have the passworf window which open indefinitely. ",moijeux
19373,VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138 => Fixed in SVN,other,VirtualBox 6.1.4,2020-03-03T15:10:22Z,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)
20606,Ubuntu Guest randomly and frequently aborts.,other,VirtualBox 6.1.26,2021-10-15T13:01:17Z,2021-10-25T14:52:35Z,2021-10-25T14:52:35Z,"I have a guest virtual machine running Ubuntu Server 20.04.3 LTS
It aborts few times per week apparently at random.
For testing I created a new VM with the same SO and happens the same thing.
The other day this happened twice in one day.
Everything to up to date.
The Host OS is Windows 10 64bit pro.
You can see the rest in the logs.",Miguel Santos
20316,Mouseclicks doesn't respond when attempting to install Fedora 33,other,VirtualBox 6.1.18,2021-04-22T21:10:56Z,2021-04-22T21:12:22Z,2021-04-22T21:12:22Z,"Steps to reproduce:

1. Download the Fedora 33 Everything (netinstall) ISO
2. Boot the system
3. The installer won't past the first screen, because the mouseclicks doesn't respond.

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-16-generic
OS Type: 64-bit
Graphics Platform: X11",radulf
20228,Don't start VM with vagrant instruction,other,VirtualBox 6.1.18,2021-02-28T08:53:27Z,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
20095,Virtualbox still resets intel adapters,other,VirtualBox 6.1.14,2020-12-17T12:31:17Z,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
20048,Nested VMs on Intel without VMCS Shadowing,other,VirtualBox 6.1.16,2020-11-18T14:31:01Z,2020-11-21T04:56:01Z,2020-11-21T04:56:01Z,"Having nested VMs as of 6.0 is great, but the requirement for Intel VMCS Shadowing means that it's only available on a limited set of CPUs.

Is there any chance of adding for support on CPUs that do not have VMCS Shadowing? At least for Linux guests?",Grunthos
19962,"Screen partially (upper portion) garbled after going to full screen (host: win10, guest: linux )",other,VirtualBox 6.1.14,2020-10-12T17:53:02Z,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
19961,"Screen partially (upper portion) garbled after going to full screen (host: win10, guest: linux )",other,VirtualBox 6.1.14,2020-10-12T17:52:46Z,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
19554,Virtual machine closes unexpectingly,other,VirtualBox 6.1.6,2020-05-04T16:09:37Z,2020-10-05T15:45:46Z,2020-10-05T15:45:46Z,"I use BirtualBox 6.1.6 r137129 (Qt5.6.1) under Linux Sabayon 64 bit (up to date) with KDE:

Operating System: Gentoo Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.4.0-sabayon
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7 CPU 920 @ 2.67GHz
Memory: 23,5 GiB of RAM

The guest is KDE Neon also up to date, for KDE development.

When I switch to KRDC, after an undetermined time, the guest is closed unexpectingly.

",----------
19934,Cannot create 64-bit VM with VirtualBox,other,VirtualBox 6.1.14,2020-10-03T22:04:20Z,2020-10-03T22:04:20Z,2020-10-03T22:04:20Z,"I just got a brand-new computer, running Windows 10 Education. I try to create an Ubuntu 64-bit VM on VirtualBox 6.1.14, but only 32-bit options are available. I checked the BIOS to make sure SVM was enabled, and it already was. I made sure that Hyper-V was disabled, so there weren't two virtualization options available at the same time, but it already was. I've checked Google and Stack Exchange but I couldn't find anything else. Any help would be appreciated.",rochat
19778,Guest additions screen resize detection code fails,other,VirtualBox 6.1.8,2020-07-29T16:04:52Z,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
19823,Windows 10 Audio VRDE Driver Bug,other,VirtualBox 6.1.10,2020-08-20T04:05:12Z,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
19700,Impossible d'installer le systeme de base,other,VirtualBox 6.1.10,2020-07-03T19:54:36Z,2020-07-03T20:17:57Z,2020-07-03T20:17:57Z,"Je tente de créer une machine virtuelle sous Kali Linux depuis quelques semaines,A chaque tentative un message d'erreur s'Affiche disant: une erreur s'est produite lors de l'installation du noyau vers le système cible. ",Violon
19575,Failed to open a session for virtual machine,other,VirtualBox 6.1.6,2020-05-09T10:11:04Z,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
19392,VMSVGA and FHD on 6.1.4,other,VirtualBox 6.1.4,2020-03-10T13:00:43Z,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
17086,Webcam crash in Ubuntu 16.0.4 and VirtualBox 5.1.28 running Android-x86,other,VirtualBox 5.1.28,2017-09-16T05:23:17Z,2020-04-15T15:10:37Z,2020-04-15T15:10:37Z,"I've created a VM with Android 6.0-r3 from www.android-x86.org using VirtualBox 5.1.28 and Ubuntu 16.04 LTS. The VM works great, but every time I try to use a fake webcam it crashes.

Basically if in the host I perform:

# After installing v4l2loopback-dkms
modprobe v4l2loopback
# Init the video stream (/tmp/i.png can be any image and /dev/video0 is the loopback device that can have a different number if you have other connected webcams)
while [ 42 ]; do cat /tmp/i.png ; done | ffmpeg -y -i - -f image2pipe -r 15 -s 1920x1080 -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0

=> Run the VM and manually stop at the GRUB boot loader
=> Assign the webcam to the machine (Devices => Webcams => Dummy Video Device)
=> Continue to boot the machine

(the steps above are important, otherwise Android will not recognize the webcam)

=> Run some camera app, I use Open Camera from https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en

=> The APP should show the image
=> Just try to leave the APP

=> The VM will crash and if you run the 'dmesg' command, it will appear something like

[202894.416980] HWCMONITOR[14932]: segfault at 7f5554b17800 ip 00007f55dc0beb35 sp 00007f55b017bb80 error 4 in VBoxHostWebcam.so[7f55dc0b8000+3a000]",aliedis87.rhyta
19466,VirtualBox 6.1.4 New Cloud VM (OCI) wizard does not display sub compartments,other,VirtualBox 6.1.4,2020-04-08T13:30:31Z,2020-04-08T13:30:31Z,2020-04-08T13:30:31Z,"I want to launch a cloud VM in a sub compartment of a compartment of a tenancy.

Your wizard only goes down 1 level to the compartment level and does NOT show the sub compartments (or beyond).

Please e-mail me for more info: bernie.doehner@oracle.com. 
Thanks,
Bernie
",BernieD
19366,virtualbox does not work,other,VirtualBox 6.1.4,2020-03-01T12:59:02Z,2020-03-01T12:59:02Z,2020-03-01T12:59:02Z,"OS: Astra Linux

The virtual machine '1' has terminated unexpectedly during startup with exit code 1 (0x1).

Код ошибки: NS_ERROR_FAILURE (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",Yuriy Davidenko
19249,aclocal (and probably other tools) not working in shared folder,other,VirtualBox 6.1.2,2020-01-21T16:33:17Z,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
19207,3d acecleration breaks VMSVGA,other,VirtualBox 6.0.14,2020-01-08T11:15:00Z,2020-01-08T11:19:43Z,2020-01-08T11:19:43Z,The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).,VincentX
19201,"VM changes from good to ""inaccessible"" after about a minute",other,VirtualBox 6.1.0,2020-01-06T20:54:29Z,2020-01-06T20:54:29Z,2020-01-06T20:54:29Z,"With VirtualBox 6.1 on Fedora 30 and all updates applied, I create a VM and attach an existing virtual disk (Centos 7.6 is the guest operating system) as ""immutable"". I snapshot it twice afterwards, first to make a differencing disk image and next to allow students to roll back their changes. I have been doing this for nearly a decade across many VirtualBox releases, and it usually works. I can list the VMs associated with a user account:

VBoxManage list vms

and it will show the correct name of the VM for a minute or two of repeated ""list vms"", then it will change to ""inaccessible"".

When I revert to 5.2.34, this behavior goes away and the VM remains accessible and usable.",Stephen Rondeau
734,Guest Additions Deb Packages,other,VirtualBox 1.5.0,2007-10-01T11:25:33Z,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
19129,Cannot reconize password in Kali Linux 2019.4 VM,other,VirtualBox 6.0.14,2019-12-04T01:14:30Z,2019-12-04T05:35:54Z,2019-12-04T05:35:54Z,password not reconized by kali Linux software,tommy smith
18854,BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver,other,VirtualBox 6.0.10,2019-08-19T16:22:46Z,2019-08-19T16:22:46Z,2019-08-19T16:22:46Z,"I am using VirtualBox on Windows 10 x64 host.
BSOD of Windows host occured when I using CentOS 7 x64 Linux without GUI (just console mode) installation and trying to install ISPmanager Business https://www.ispsystem.com/software/ispmanager/download to avaluate it:
wget ""http://cdn.ispsystem.com/install.sh""
sh install.sh
, activating the demo version of ISPmanager Business and trying to update packages of it.
The probability of BSOD is approx. 80% in update packages state.
BSOD is in Windows network card driver in ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ndis!ndisCallSendCompleteHandler+0x33
ndis!NdisMSendNetBufferListsComplete+0x1df
e1d65x64+0x133b4
(see Windbg outputs)
Guest network is in bridge mode.
In addition, RusRoute firewall free version http://rusroute.com/ is installed on host system, independed in disabled or enabled state of it (Standard Windows firewall is disalbed in both cases).
Can you tell me what software is the reason os BSOD? Is this the bug in VistualBox or in other third party software, like RusRoute firewall?
The Windows 7, XP guests with the same environment is working fine.
WinDbg of minidump1, minidump2 are attached.

{{{

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-10984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Deferred                                       cache*c:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols;cache*c:\MySymbols;srv*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`18200000 PsLoadedModuleList = 0xfffff804`186432f0
Debug session time: Fri Aug  2 20:15:42.372 2019 (UTC + 3:00)
System Uptime: 0 days 0:49:12.083
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff9d8db279f1a0, Virtual address for the attempted execute.
Arg2: 8a000008092008e3, PTE contents.
Arg3: fffff8041db504a0, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys

KEY_VALUES_STRING: 1

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.239 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: ffff9d8db279f1a0

BUGCHECK_P2: 8a000008092008e3

BUGCHECK_P3: fffff8041db504a0

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:05:14.0379

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

DPC_STACK_BASE:  FFFFF8041DB50FB0

TRAP_FRAME:  fffff8041db504a0 -- (.trap 0xfffff8041db504a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9d8db279f1a0 rbx=0000000000000000 rcx=ffff9d8db2ad9950
rdx=ffff9d8db9a923d0 rsi=0000000000000000 rdi=0000000000000000
rip=ffff9d8db279f1a0 rsp=fffff8041db50638 rbp=fffff8041db506b9
 r8=0000000000000001  r9=0000000000000000 r10=fffff80424425b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff9d8d`b279f1a0 1101            adc     dword ptr [rcx],eax ds:ffff9d8d`b2ad9950=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff804184554bc to fffff804183bc900

STACK_TEXT:  
fffff804`1db50278 fffff804`184554bc : 00000000`000000fc ffff9d8d`b279f1a0 8a000008`092008e3 fffff804`1db504a0 : nt!KeBugCheckEx
fffff804`1db50280 fffff804`1844fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 fffff804`1db503c0 : nt!MiCheckSystemNxFault+0x125330
fffff804`1db502c0 fffff804`1827ac2a : 00000000`00000003 00000000`00000011 fffff804`1db50400 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
fffff804`1db50300 fffff804`183ca920 : ffff9d8d`b279f1a0 ffff9d8d`bb66a950 00000000`00000001 00000000`00000001 : nt!MmAccessFault+0x48a
fffff804`1db504a0 ffff9d8d`b279f1a0 : fffff804`1d18aa51 ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 : nt!KiPageFault+0x360
fffff804`1db50638 fffff804`1d18aa51 : ffff9d8d`b2ae7a20 ffff9d8d`b281a120 fffff804`244f10b0 ffff9d8d`b9a923d0 : 0xffff9d8d`b279f1a0
fffff804`1db50640 fffff804`1d18eba3 : 00000000`00000002 00000000`00000000 fffff804`00000001 fffff804`244c2101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
fffff804`1db50720 fffff804`1d18bcdf : 00001e00`00001e01 ffff9d8d`b26073c1 ffff9d8d`b2adbb60 ffff9d8d`b9a923d0 : ndis!ndisCallSendCompleteHandler+0x33
fffff804`1db50760 fffff804`271033b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff804`27100d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
fffff804`1db50850 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 : e1d65x64+0x133b4
fffff804`1db50858 00000001`00000000 : 00000001`00000000 fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 : 0x2
fffff804`1db50860 00000001`00000000 : fffff804`27100d00 ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 : 0x00000001`00000000
fffff804`1db50868 fffff804`27100d00 : ffff9d8d`b2be0c60 ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 : 0x00000001`00000000
fffff804`1db50870 ffff9d8d`b2be0c60 : ffff9d8d`b29c9d50 ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 : e1d65x64+0x10d00
fffff804`1db50878 ffff9d8d`b29c9d50 : ffff9d8d`b281f000 ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 : 0xffff9d8d`b2be0c60
fffff804`1db50880 ffff9d8d`b281f000 : ffff9d8d`b281fe40 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad : 0xffff9d8d`b29c9d50
fffff804`1db50888 ffff9d8d`b281fe40 : 00000001`b283ad01 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 : 0xffff9d8d`b281f000
fffff804`1db50890 00000001`b283ad01 : 00000000`00000001 ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 : 0xffff9d8d`b281fe40
fffff804`1db50898 00000000`00000001 : ffff9d8d`000001ad 00000000`00000000 ffff9d8d`af928350 00000000`00000000 : 0x00000001`b283ad01
fffff804`1db508a0 ffff9d8d`000001ad : 00000000`00000000 ffff9d8d`af928350 00000000`00000000 00000000`00000000 : 0x1
fffff804`1db508a8 00000000`00000000 : ffff9d8d`af928350 00000000`00000000 00000000`00000000 ffff9d00`00000000 : 0xffff9d8d`000001ad


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff804`271033b4 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:15:42.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.239

ANALYSIS_SESSION_ELAPSED_TIME:  b5e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}



{{{

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\minidump\080219-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\MySymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`62c00000 PsLoadedModuleList = 0xfffff803`630432f0
Debug session time: Fri Aug  2 20:37:09.365 2019 (UTC + 3:00)
System Uptime: 0 days 0:11:15.077
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff800803df71a0, Virtual address for the attempted execute.
Arg2: 8a00000809c008e3, PTE contents.
Arg3: ffff908edb1c8340, (reserved)
Arg4: 0000000000000003, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e1d65x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: ffff800803df71a0

BUGCHECK_P2: 8a00000809c008e3

BUGCHECK_P3: ffff908edb1c8340

BUGCHECK_P4: 3

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  7700K

ANALYSIS_SESSION_TIME:  08-19-2019 19:08:23.0965

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME:  ffff908edb1c8340 -- (.trap 0xffff908edb1c8340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff800803df71a0 rbx=0000000000000000 rcx=ffff8008042dab50
rdx=ffff80080ae10600 rsi=0000000000000000 rdi=0000000000000000
rip=ffff800803df71a0 rsp=ffff908edb1c84d8 rbp=ffff908edb1c8559
 r8=0000000000000001  r9=0000000000000000 r10=fffff8036e9c5b90
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffff8008`03df71a0 1101            adc     dword ptr [rcx],eax ds:ffff8008`042dab50=03da7ef0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80362e554bc to fffff80362dbc900

STACK_TEXT:  
ffff908e`db1c8118 fffff803`62e554bc : 00000000`000000fc ffff8008`03df71a0 8a000008`09c008e3 ffff908e`db1c8340 : nt!KeBugCheckEx
ffff908e`db1c8120 fffff803`62e4fbc1 : 00000000`00000003 00000000`00000001 00000000`00000000 ffff908e`db1c8260 : nt!MiCheckSystemNxFault+0x125330
ffff908e`db1c8160 fffff803`62c7ac2a : 00000000`00000006 00000000`00000011 ffff908e`db1c82a0 00000000`00000000 : nt!MiRaisedIrqlFault+0x12a6e1
ffff908e`db1c81a0 fffff803`62dca920 : 00000000`00000000 fffff803`b2503711 00000000`00000002 00000000`00000036 : nt!MmAccessFault+0x48a
ffff908e`db1c8340 ffff8008`03df71a0 : fffff803`6778aa51 ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 : nt!KiPageFault+0x360
ffff908e`db1c84d8 fffff803`6778aa51 : ffff8008`0451aa20 ffff8008`03e223f0 fffff803`6ea910b0 ffff8008`0ae10600 : 0xffff8008`03df71a0
ffff908e`db1c84e0 fffff803`6778eba3 : 00000000`00000002 00000000`00000000 fffff803`00000001 fffff803`6ea62101 : ndis!ndisMSendCompleteNetBufferListsInternal+0x121
ffff908e`db1c85c0 fffff803`6778bcdf : fffff803`60367101 ffff8008`03afb9a1 ffff8008`043198c0 ffff8008`0ae10600 : ndis!ndisCallSendCompleteHandler+0x33
ffff908e`db1c8600 fffff803`70ed33b4 : 00000000`00000002 00000001`00000000 00000001`00000000 fffff803`70ed0d00 : ndis!NdisMSendNetBufferListsComplete+0x1df
ffff908e`db1c86f0 00000000`00000002 : 00000001`00000000 00000001`00000000 fffff803`70ed0d00 00000000`00000000 : e1d65x64+0x133b4
ffff908e`db1c86f8 00000001`00000000 : 00000001`00000000 fffff803`70ed0d00 00000000`00000000 00000000`00000000 : 0x2
ffff908e`db1c8700 00000001`00000000 : fffff803`70ed0d00 00000000`00000000 00000000`00000000 ffff8008`03e23000 : 0x00000001`00000000
ffff908e`db1c8708 fffff803`70ed0d00 : 00000000`00000000 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 : 0x00000001`00000000
ffff908e`db1c8710 00000000`00000000 : 00000000`00000000 ffff8008`03e23000 ffff8008`03e23e40 00000001`03e3ed01 : e1d65x64+0x10d00


THREAD_SHA1_HASH_MOD_FUNC:  c0ffbf375cd55e1aa93daf3c03427b8881b1e850

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5058410cce10b80427a1f7de155fad955a47b3fb

THREAD_SHA1_HASH_MOD:  f2616a5e3854c666781435d2d0ed7d6384206ea6

FOLLOWUP_IP: 
e1d65x64+133b4
fffff803`70ed33b4 448b7dcb        mov     r15d,dword ptr [rbp-35h]

FAULT_INSTR_CODE:  cb7d8b44

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  e1d65x64+133b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1d65x64

IMAGE_NAME:  e1d65x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57f4c1b3

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  133b4

FAILURE_BUCKET_ID:  0xFC_e1d65x64!unknown_function

BUCKET_ID:  0xFC_e1d65x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xFC_e1d65x64!unknown_function

TARGET_TIME:  2019-08-02T17:37:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 11:33:06

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  10b20

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xfc_e1d65x64!unknown_function

FAILURE_ID_HASH:  {7259990a-ebc1-3d2e-33f5-0c4abf098887}

Followup:     MachineOwner
---------


}}}
",MaaSoftware
18628,Windows 7 crash (blue screen) on start VM,other,VirtualBox 6.0.6,2019-05-08T12:26:26Z,2019-05-08T12:26:26Z,2019-05-08T12:26:26Z,"On start VM, Widows 7 crash (blue screen).",akurgan
18432,Ubuntu is failing to install,other,VirtualBox 6.0.4,2019-02-12T15:45:41Z,2019-02-12T15:45:41Z,2019-02-12T15:45:41Z,"When installing Ubuntu (32x) the installation will hit a large error sending the following text in the attached files. I can sometimes get to the installation page where Ubuntu asks where I am from, and then the installation fails with the same error message. I believe this issue may be unrelated, however, Ubuntu will freeze continually. I managed to reduce the freezing-frequency by changing the video source component to 128MB instead of 12MB. 

I supply roughly 4GBs of RAM to Ubuntu.",ChachiChamp
18150,Extremely sluggish mouse movement on macOS,other,VirtualBox 5.2.22,2018-11-25T01:57:01Z,2018-11-30T00:56:15Z,2018-11-30T00:56:15Z,"Dear fellow developers!

I've been a long-time user of VirtualBox and I've come to appreciate it for it's stable set of features and the fact that it is cross-platform and thus available anywhere. However, with the latest couple of versions, I've run into some real issues. The visual performance is severely degraded. Also, every time I shut down a virtual machine, VirtualBox crashes. I've done a screen recording: https://youtu.be/ndXNDt9kXAY on an example VM running AndroidX86, but I've also observed this on other Linux VMs.

I first noticed this a few months ago when I got a new machine (MacBook Pro 13"" 2017). I initially assumed it was just a bug from a rushed release, but after a couple new releases nothing has changed and unfortunately, VirtualBox is not really usable like this for me.

Could you please look into it? I'm happy to run any kind of diagnostics or try stuff out.

Greetings,
xfbs",xfbs
18056,Linux VM fails to PXE boot on MacOS host,other,VirtualBox 5.2.20,2018-10-17T12:29:26Z,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
17725,Recording audio non detected on Linux,other,VirtualBox 5.2.8,2018-05-02T08:02:13Z,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
17605,VirtualBox does not see 255 char filename,other,VirtualBox 5.2.6,2018-03-08T04:29:47Z,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
16370,Main window showing guest freezes after using virtualdesktop on Win7,other,VirtualBox 5.1.12,2017-01-10T17:09:01Z,2018-02-13T17:28:01Z,2018-02-13T17:28:01Z,"Host: Windows 7, running virtual desktop program Dexpot version 1.6.10, Build 2362. 
Host Video card: NVIDIA GeForce GTX 960
VirtualBox version 5.1.12r112440 (QT5.6.2)

Guest OS: KUbuntu 16.04.1

This behavior started after I just upgraded from VirtualBox version 5.0.?? to version 5.1.12. 

When VB is in fullscreen mode, on the host I switch virtual desktops away from the desktop showing VB guest OS. When I switch back to the host virtual desktop the guest OS screen is frozen. HOWEVER, the VB preview window works. I can see applications switch, and can use a console to tell the machine to reboot. 

The screen does not feeze if the VB guest OS is kept in Windowed mode (not full-screen mode). In fact, switching to windowed mode unfreezes the display. 

The attached log is after the guest screen freezes, then I switch VB to windows mode to unfreeze the display, then switch virtual desktops on the host a couple of times. 
",P-Dog
17424,Old Linux on Virtual Box 5.2.4 gets Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),other,VirtualBox 5.2.4,2018-01-05T23:58:48Z,2018-01-08T21:38:36Z,2018-01-08T21:38:36Z,"Migrating a running (older) Linux guest from Mac OS hosted VirtualBox 5.2.3 to FreeBSD hosted
VirtualBox 5.2.4.

Exported all the machines as an appliance from 5.2.3 and imported them to the 5.2.4.

All virtual machines operate correctly except a rather ancient Linux that fails to boot
with a VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

I will attach the log files.",Dave Rivers
17338,Rename repository name in virtualbox.repo (for Fedora distro),other,VirtualBox 5.2.0,2017-12-01T19:34:59Z,2017-12-01T19:34:59Z,2017-12-01T19:34:59Z,"Repo file provided for Fedora (see link below) defines the repo's name as:


{{{
name=Fedora $releasever - $basearch - VirtualBox
}}}


Example: ''Fedora 26 - x86_64 - VirtualBox''

From a user perspective, in my personal opinion, it would make more sense to print something like

''VirtualBox - Fedora 26 - x86_64''


{{{
name=VirtualBox - Fedora $releasever - $basearch
}}}

This order would be more consistent with other repositories provided for Fedora, first naming the repository, followed by some info about release version and architecture.


Link: http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
",F
17080,"guest additions do not build with 4.14 kernel -> fixed in builds after 1. November 2017, 5.2 and later",other,VirtualBox 5.1.26,2017-09-14T19:13:55Z,2017-10-31T16:46:43Z,2017-10-31T16:46:43Z,"Got an error message while attempting to install guest additions in a Fedora Rawhide guest for the 4.14.0-0.rc0.git5.1.fc28.x86_64 kernel.
{{{
vboxadd.sh: failed: Look at /var/log/vboxadd-install.log to find out what went wrong.
}}}",Andre Robatino
16429,Hard lockup of Linux guests on Mac Host,other,VirtualBox 5.1.14,2017-01-26T13:19:16Z,2017-05-30T23:50:35Z,2017-05-30T23:50:35Z,"I am running an Ubuntu 16.04 guest on a MacOS Sierra host.  In my guest I am running a Yocto project build (https://yoctoproject.org/).  This is a fairly substantial workload and eventually the target apparently locks up.  I've try to get kernel logs out of dmesg, /var/log/syslog and the VT1 console but when the system is hung, there is nothing printed to any of those locations indicating any trouble.

I have seen this happen also on Ubuntu 14 and CentOS 7 targets.

It is reproducible 100% of the time with the Yocto project build.  When it is hung, the GUI is still displayed but nothing updates, not even the clock app.

I tested with both VirtualBox 5.1.14 and 5.0.32 and could reproduce the issue with both versions.  I'm testing now with the 5.1.15 nightly build",drewmoseley
16585,guest additions initscripts should be more flexible,other,VirtualBox 5.1.18,2017-03-20T13:24:28Z,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
15962,Wayland Login Manager Borks Login process in Fedora 24,other,VirtualBox 5.1.6,2016-09-20T18:03:43Z,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
16275,Virtual Box crash on more screen,other,VirtualBox 5.1.10,2016-12-08T15:32:13Z,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
16184,Invisible Mouse Cursor,other,VirtualBox 5.1.8,2016-11-13T10:17:13Z,2016-11-15T02:20:51Z,2016-11-15T02:20:51Z,"Hi there,

I am using VBox 5.1.8 for Windows (also tried test build 5.1.9) but am unable to get the mouse to work on RHEL 7. The cursor is apparently there but its just not showing. When I press left ctrl key and move mouse around the ""show location of pointer"" gets highlighted as I move in different areas. My machine config -

HP Pavillion Laptop / Windows 10 (Home 64bit) / Intel i7-6700HQ / GPUs (Intel HD Graphics 530 & Nividia GeForce GTX 960M)

I will be upfront and open, I am very new to VBox and Linux but nonetheless, I have been reading into forums and bug tickets for the past 3 days but to no avail.

Will appreciate any and all help. Many thanks.",Dan J
11455,"VirtualBox 4.2.6 , Guest freeze / hangs on network load",other,VirtualBox 4.2.6,2013-02-04T15:28:57Z,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
15840,Sound fails with VB 5.1.4 on MacOs 10.11.6(host) and 32 bit Fedora 24 (Guest),other,VirtualBox 5.1.4,2016-08-21T18:01:30Z,2016-09-27T01:14:36Z,2016-09-27T01:14:36Z,On a clean reboot sound is '''sometimes''' briefly available but  quickly fails.,jerrysVB
5295,Shared folders cannot be exported via NFS,other,VirtualBox 3.0.10,2009-10-26T08:56:27Z,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
15697,Linux Additions should still be able to read network config without D-Bus,other,VirtualBox 4.3.36,2016-07-27T10:49:21Z,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
15563,VirtualBox Guest Additions 5.0.24 cannot Auto-resize Guest Display,other,VirtualBox 5.0.24,2016-07-03T02:45:43Z,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
12320,3D acceleration not working with Gnome Ubuntu 13.10 guest (falls back to software rendering),other,VirtualBox 4.3.2,2013-11-06T10:11:31Z,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
15221,VirtualBox 5.0.16 Guest Additions fail to install under RHEL 5.11 64-bit,other,VirtualBox 5.0.16,2016-03-08T16:26:14Z,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
14795,Linux (Centos-6 x64) guest regularly crashes,other,VirtualBox 5.0.6,2015-11-06T08:44:00Z,2015-11-06T09:21:47Z,2015-11-06T09:21:47Z,"Centos-6 x64 guest regularly crashes after several days of uptime. No any problems with adjacent windows VM (Windows Server 2003 x86).

VirtualBox: 5.0.6r103037 (same problem with many previous releases).
Host: Windows Server 2008 x64, with latest updates, 24 GB RAM.
Guest: Centos-6 x64, with latest updates, 2 GB RAM, no guest additions.

Kernel errors examples:

kernel BUG at mm/vmscan.c:1083! [[BR]]

invalid opcode: 0000 [#1] SMP[[BR]]

BUG: soft lockup - CPU#0 stuck for 67s! [updater:31994][[BR]]
",Victor Abramoff
13785,OS X Guest with Bridged Networking cannot obtain DHCP lease - guest actively DHCPDECLINEs due to host activity,other,VirtualBox 4.3.20,2015-01-25T12:38:06Z,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
13891,VNC output scrambled during Ubuntu installation,other,VirtualBox 4.3.22,2015-02-24T22:34:02Z,2015-02-26T09:18:36Z,2015-02-26T09:18:36Z,"I ran VirtualBox headless on a FreeBSD 10.1 server (host) and tried to install Ubuntu 14.10 as a guest from the live iso image. I connect to the VirtualBox VNC server to get the VM output. The Ubuntu VM boots up, my VNC client shows the Ubuntu splash screen but as soon as the Ubuntu desktop gets started I get a scrambled image.
I can confirm the problem on FreeBSD 9.3 / VirtualBox 4.2.16 and FreeBSD 10.1 / VirtualBox 4.2.16 & VirtualBox 4.2.22. I have tried different VNC viewer @ Ubuntu (ssvncviewer) and Windows (RealVNC), no difference.

VM VNC output

[[Image(http://www.directupload.net/file/d/3908/adgfi9ld_png.htm)]]


Steps to create the VM:
- set VM='Ubuntu_14.10'
- VBoxManage createvm --name $VM --ostype ""Ubuntu_64"" --register
- VBoxManage storagectl $VM --name ""SATA Controller"" --add sata --controller IntelAHCI
- VBoxManage storageattach $VM --storagectl ""SATA Controller"" --port 1 --type dvddrive --medium ~/ubuntu-14.10-desktop-amd64.iso
- VBoxManage modifyvm $VM --memory 2048 --vram 128
- VBoxManage modifyvm $VM --vrdeproperty VNCPassword=password
- VBoxHeadless -s $VM


Output from VBoxHeadless
{{{
Oracle VM VirtualBox Headless Interface 4.3.22_OSE
(C) 2008-2015 Oracle Corporation
All rights reserved.

24/02/2015 22:28:30 Listening for VNC connections on TCP port 3389
24/02/2015 22:28:30 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3389.
24/02/2015 22:28:34   other clients:
24/02/2015 22:28:34 Client Protocol Version 3.8
24/02/2015 22:28:34 Protocol version sent 3.8, using 3.8
24/02/2015 22:28:34 rfbProcessClientSecurityType: executing handler for type 2
24/02/2015 22:28:34 Pixel format for client 192.168.0.109:
24/02/2015 22:28:34   32 bpp, depth 24, little endian
24/02/2015 22:28:34   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
24/02/2015 22:28:34 Enabling X-style cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling full-color cursor updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling cursor position updates for client 192.168.0.109
24/02/2015 22:28:34 Enabling KeyboardLedState protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling NewFBSize protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedMessages protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling SupportedEncodings protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling ServerIdentity protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Enabling Xvp protocol extension for client 192.168.0.109
24/02/2015 22:28:34 Using hextile encoding for client 192.168.0.109
24/02/2015 22:28:38 Sending rfbEncodingNewFBSize for resize to (720x400)
24/02/2015 22:29:04 Sending rfbEncodingNewFBSize for resize to (1024x768)
24/02/2015 22:29:06 Sending rfbEncodingNewFBSize for resize to (1152x400)
}}}


Output from ssvncviewer (VNC client)
{{{
Proto: RFB 003.008

Connected to RFB server, using protocol version 3.8

SelectSecurityType:
  sec-type[0]    2  (rfbSecTypeVncAuth)
Security-Type:   2  (rfbSecTypeVncAuth)  Latency: 3.01 ms

Performing standard VNC authentication
VNC Password: 
VNC authentication succeeded

Desktop name ""VBoxVNC""

VNC server default format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 0 green 8 blue 16
Warning: Cannot convert string ""-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*"" to type FontStruct
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
geometry: 720x400+358+238 ycrop: 0
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 720x400
try_create_image: image->bytes_per_line: 2880

guessed: -compresslevel 1
guessed: -qualitylevel  9
enabling 'delay_sync' mode for faster local drawing,
disable via env SSVNC_DELAY_SYNC=0 if there are painting errors.
New Size: 1024x768 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1024x768
try_create_image: image->bytes_per_line: 4096
New Size: 1152x400 at (0, 0)
ReDoDesktop: ycrop: 0
reset_image: destroyed 'image'
create_image()
try_create_image: shm image create fail: image == NULL
try_create_image: created *non-shm* image: 1152x400
try_create_image: image->bytes_per_line: 4608
}}}
",MrSmith
8401,[feature-request] Direct Linux Boot,other,VirtualBox 4.0.4,2011-02-22T15:27:58Z,2013-04-07T20:50:43Z,2013-04-07T20:50:43Z,"Direct Linux Boot means that the user can specify guest kernel and initrd and boot Linux guest directly, either from CD/DVD, or from HDD, bypassing guest's bootloader.

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

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

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

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

-Technologov, 22.02.2011.",Technologov
10094,Valgrind's memcheck hard to use with VirtualBox OpenGL drivers,other,VirtualBox 4.1.8,2011-12-27T19:01:27Z,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
10261,Shared Folder symlnks now broken with Windows Host<-> Linux Guest,other,VirtualBox 4.1.8,2012-02-18T17:47:07Z,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
6525,Develop a Gallium3D Driver for Linux (and Other) Guests,other,VirtualBox 3.1.6,2010-04-14T06:08:45Z,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
10101,"VBoxLinuxAdditions should check for make, perl",other,VirtualBox 4.1.2,2011-12-29T03:03:24Z,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
9307,VBox 4.1.0 GA --  shared folder fails manual mount with sf_read_super_aux err=-22,other,VirtualBox 4.1.0,2011-07-25T23:50:42Z,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
375,Integrating VirtualBox Linux additions upstream (X.org),other,VirtualBox 1.3.8,2007-05-30T21:42:30Z,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
21490,Bitnami OVA Aborts on M2 Mac Mini Using Virtualbox Developer preview for macOS / Arm64 (M1/M2) hosts,Mac OS X,VirtualBox-7.0.6,2023-02-10T16:12:54Z,2023-02-13T20:50:05Z,2023-02-13T20:50:05Z,"Using an M1 Mac Mini 2020, I found the new VirtualBox-7.0.6_BETA4-155176-macOSArm64 download at VirtualBox.org. This is the Developer preview for macOS / Arm64 (M1/M2) hosts.

VirtualBox installs fine and opens as usual.

I imported the Bitnami VM OVA for ResourceSpace bitnami-resourcespace-10.0.0-31-r29-linux-vm-debian-11-x86_64-nami.ova

No apparent problem with importing.

When I click Start, the VM starts the Linux boot, gives a little bit of progress: GRUB Booting Debian GNU/LInux and then the boot sequence aborts and VirtualBox displays Aborted for the status of the VM.

Any ideas what might be happening? Do Bitnami VMs work with the Developer version of VirtualBox for M1 and M2 Mac Minis?

The same problem occurs on an M2 Mac Mini Pro new out of the Box (2023).
",Kyosho at ZMM
21470,Emulated TPM does not include Endorsement Key (EK) certificate,Mac OS X,VirtualBox-7.0.6,2023-02-07T21:37:06Z,2023-02-07T21:37:06Z,2023-02-07T21:37:06Z,"The command ""sudo tpm2_nvread 0x1c00002 > ekcert.der"", installed with the tpm2-tools package on Linux, does not return an endorsement key (EK) certificate. On VMware Fusion's emulator, a self-signed dynamic certificate/key pair is dynamically created in the emulated TPM and the above command works fine.",NedRyerson
21454,Error: vmnet_start_interface returned 1001,Mac OS X,VirtualBox-7.0.6,2023-02-02T07:25:26Z,2023-02-02T07:49:33Z,2023-02-02T07:49:33Z,"Unable to use host only network with 192.0.2.0/24 network

00:00:01.271232 VMNet: Host network with mask 255.255.255.0 (192.0.2.1 to 192.0.2.200)
00:00:01.271907 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DrvVMNet.m(650) int drvVMNetConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_INVALID_PARAMETER
00:00:01.271911 VMSetError: Error: vmnet_start_interface returned 1001
00:00:01.272118 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DevE1000.cpp(8287) int e1kR3Construct(PPDMDEVINS, int, PCFGMNODE); rc=VERR_INVALID_PARAMETER
00:00:01.272121 VMSetError: Failed to attach the network LUN
00:00:01.272141 PDM: Failed to construct 'e1000'/1! VERR_INVALID_PARAMETER (-2) - Invalid parameter.

% cat /etc/vbox/networks.conf
* 192.0.2.0/24
* 0.0.0.0/0 ::/0",urbanchef
21436,Coral USB EdgeTPU runs high then disappear from host,Mac OS X,VirtualBox-6.1.42,2023-01-27T12:34:35Z,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
21428,Signal 9,Mac OS X,VirtualBox-7.0.6,2023-01-22T22:18:31Z,2023-01-22T22:18:31Z,2023-01-22T22:18:31Z,"I was trying to boot android 9 on macOS Ventura 13.2 beta but this happened 
VM Name: Android 9
The virtual machine
'Android 9° has
terminated unexpectedly during startup because of signal 9.
Result code: NS_ERROR_FAILURE(0X80004005)
Component: MachineWrap
Interface: IMachine
{300763af-5d6b-46e6-aa96-273eac155381}

I dunno what to do And I scoured the inter webs and could not find anything

Also no one has said anything on this before at least not of my knowledge.

Please help",UKNOWN VM
21218,USB drives do not connect to Virtualbox 7.0.2 under macOS host,Mac OS X,VirtualBox-7.0.2,2022-10-29T22:53:41Z,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
18176,USB resets and hangs during high I/O,Mac OS X,VirtualBox 5.2.22,2018-12-10T22:06:28Z,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
21317,Mac dark mode makes it impossible to read help,Mac OS X,VirtualBox-7.0.4,2022-11-28T02:10:54Z,2022-11-28T02:10:54Z,2022-11-28T02:10:54Z,"I was trying to access the help for VB on my mac in which I run dark mode.  However dark mode only seems to apply to text in the help, resulting in white text on white background.",traisjames
21222,Issue running virtual machines with VT-X enabled,Mac OS X,VirtualBox-7.0.2,2022-10-30T17:48:26Z,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
21232,3d Accerlation causes guest to not start on Ventura => fixed in SVN/next 7.0.x maintenance,Mac OS X,VirtualBox-7.0.2,2022-11-01T21:17:57Z,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
21068,VM crashes after a while when pressing Tab/Return in terminal,Mac OS X,VirtualBox 6.1.36,2022-08-16T13:05:24Z,2022-08-16T16:21:56Z,2022-08-16T16:21:56Z,"Hi,

VirtualBox: 6.1.36 r152435 (Qt5.6.3)

I am on an Ubuntu 20.04 VM (running on a macOS host). I turn it on and open up its terminal (bash). After ~10-15 minutes of playing around, I press the tab key (for autocompletion). I've notices this also sometimes happens with the return key in a Find/Replace dialogue in CLion.

The VM freezes so I have to manually shut down.

The same happens when I am in zsh, so it's not the terminal itself.

Could you please help,
Thanks,
Mihai",mihai_mc
18564,"Graphics performance is absolutely dismal, to the point of unusability",Mac OS X,VirtualBox 6.0.6,2019-04-16T22:41:16Z,2022-07-27T15:13:06Z,2022-07-27T15:13:06Z,"I use Fedora 29 with the Cinnamon desktop (runs in X, requires 3D acceleration).  I have been having pretty dismal graphics performance, to the point where I have to stop typing and let the application catch up with me so that I can spot stuck keys and dropped keystrokes.  It appears numerous X events get dropped in some fashion; often, my shift key gets stuck, as if the key_release event was missed, but that's not the only key that'll get stuck.  I have the same issue with mouse clicks, too, which makes it a bit difficult to cut and paste text or select options in menus.  For the record, this is a freshly created VM utilizing the VMSVGA driver, scaled by 175%, with 3D acceleration activated; resolution is 1920x1200.  When I upgraded from a 6.0.5 pre-release and updated the guest tools, Cinnamon started complaining about using software rendering, although I can see the vmwgfx and vboxvideo drivers loaded.  If I run glxinfo, I see ""OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)"" in the output.  I've also started to node, with the 6.0.6 release, that the Menu is getting randomly activated, as if I hit the Windows key.

(Host is osX.)",Kevin L Mitchell
20996,No guest connection with bridged adapter,Mac OS X,VirtualBox 6.1.34,2022-06-20T14:41:41Z,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
20917,Ubuntu 22.04 Server unattended install fails with error isolinux.cfg not found,Mac OS X,VirtualBox 6.1.34,2022-04-26T14:13:24Z,2022-04-27T07:14:03Z,2022-04-27T07:14:03Z,"Trying to perform an unattended install of Ubuntu 22.04 Server AMD64 on an Intel CPU MacBook Pro 2011 and I am getting the error message below.

Setup:
    - macOS 12.3.1 on MacBook Pro 2018 (with Intel CPU)
    - VirtualBox 6.1.34
    - Ubuntu Live Server 20.04 AMD64: ubuntu-22.04-live-server-amd64.iso

Serving up user-data and meta-data with a python server on port 3003, based on a Ubuntu Server doc called autoinstall-quickstart.

Getting the following error message:

VBoxManage: info: Preparing unattended installation of Ubuntu_64 in machine 'axxxxx' (b7e7ff1a-1f41-4320-8e9f-c84a2cxxxxxx).[[br]]
VBoxManage: error: Failed to open '/isolinux/isolinux.cfg' on the ISO '/Users/sxxxxx/dev/vm/iso/ubuntu-22.04-live-server-amd64.iso' (VERR_PATH_NOT_FOUND)[[br]]
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component UnattendedWrap, interface IUnattended, callee nsISupports[[br]]
VBoxManage: error: Context: ""ConstructMedia()"" at line 1859 of file VBoxManageMisc.cpp[[br]]

The files in the isolinux folder are no longer needed, because the server autoinstall is no longer based on the debian-installer (aka d-i), but rather it is based on Subiquity. Therefore, the VBoxManage unattended installer should not be looking for these. I'm afraid that this might require a VBoxManage upgrade or patch to support the new 'cloud-init' and 'curtin' with 'subiquity' based installer, unless someone can come up with a neat workaround or maybe a new unattended install template.

From browsing the source code under UnattendedTemplates/ubuntu_preseed.cfg that the template is entirely based on the debian-installer (ubiquity) and seems to have no knowledge of the new installer (subiquity).

See the source code under: /browser/vbox/trunk/src/VBox/Main/UnattendedTemplates/ubuntu_preseed.cfg on VirtualBox dot org.

Thanks in advance!",stcp
20717,networking is dropped on Linux guests under Monterey,Mac OS X,VirtualBox 6.1.30,2021-12-07T17:54:39Z,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
20795,Critical error occurred while running VM after Fedora 29 -> 31 upgrade,Mac OS X,VirtualBox 6.1.32,2022-01-29T06:28:30Z,2022-02-01T22:46:14Z,2022-02-01T22:46:14Z,"
Had an older version of Fedora 29 running on VirtualBox 6.1.32.  Used the upgrade instructions from this page to upgrade from Fedora 29 to 31, https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/.  The plan was to upgrade from 29 -> 31 -> 33 -> 35.

Fedora 29 was running with no problems on VirtualBox 6.1.32.  After using the upgrade instructions with no apparent errors and the upgrade verification was successful the VM tried to restart with the new installation of Fedora 31.  At that point I got the ""A critical error occurred while running the Virtual Machine.""  The log file and  .png file are attached.  There were no changes to the VirtualBox configuration, the Fedora upgrade process is automatic and after it completes it relaunches the new version.

Note that I tried upgrading to the 6.1.33 build and got the exact same problem, the attached logs are from the 6.1.32 and 6.1.33.
",dbhinz
20772,Catastrophic data loss with Ubuntu 21.04 guest,Mac OS X,VirtualBox 6.1.30,2022-01-16T00:30:27Z,2022-01-22T17:04:20Z,2022-01-22T17:04:20Z,"See also #20763

Following this:

```Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen
Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED
Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out
Jan 15 21:37:35 ubuntu kernel: [1355482.810786]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY }
Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link
Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link
Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link
```

the filesystem in dmesg reports:
```
[1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.851568] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.852924] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.854644] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.856205] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.857528] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.858951] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.860305] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.862256] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
```

and the filesystem is unbootable, fsck requires run by hand, and probably some files are corrupt.


Linux ubuntu 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
12:34
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.04
Release:	21.04
Codename:	hirsute",AA
20008,VERR_SSM_LOAD_CONFIG_MISMATCH on vagrant snapshot restore,Mac OS X,VirtualBox 6.1.16,2020-10-29T16:02:24Z,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
17480,Linux boot slows to a crawl when serial port is enabled for serial getty (console).,Mac OS X,VirtualBox 5.2.6,2018-01-19T04:03:55Z,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
20688,invalid destination port,Mac OS X,VirtualBox 6.1.30,2021-11-24T16:38:05Z,2021-11-24T16:38:05Z,2021-11-24T16:38:05Z,"On quitting a Linux guest, I got this problem report from Monterery..

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VirtualBoxVM [983]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.30 (6.1.30)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [945]
Responsible:           VirtualBox [941]
User ID:               502

Date/Time:             2021-11-24 11:33:23.4080 -0500
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Anonymous UUID:        D29E8D31-4B9E-1252-579C-6F6F7174505F


Time Awake Since Boot: 39000 seconds

System Integrity Protection: disabled

Notes:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000002c40000000c
Exception Codes:       0x0000000000000001, 0x000002c40000000c
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [983]

VM Region Info: 0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      CoreServices                190e88000-190ec8000    [  256K] rw-/rwx SM=COW  
--->  GAP OF 0x5ffe6f138000 BYTES
      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-/rwx SM=PRV  

Error Formulating Crash Report:
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   IOKit                         	    0x7ff81e78fae0 IOHIDDeviceCopyMatchingElements + 34
1   UICommon.dylib                	       0x10555efa8 0x10522c000 + 3354536
2   UICommon.dylib                	       0x10555ee4e DarwinHidDevicesApplyAndReleaseLedsState + 590
3   VirtualBoxVM.dylib            	       0x100581e92 0x100553000 + 192146
4   VirtualBoxVM.dylib            	       0x1005815ff 0x100553000 + 189951
5   VirtualBoxVM.dylib            	       0x100581575 0x100553000 + 189813
6   QtCoreVBox                    	       0x1018d943b QMetaObject::activate(QObject*, int, int, void**) + 2075
7   QtCoreVBox                    	       0x1018a5b76 QCoreApplication::exec() + 390
8   VirtualBoxVM.dylib            	       0x10055a42e TrustedMain + 1502
9   VirtualBoxVM                  	       0x10027ef01 0x10027b000 + 16129
10  dyld                          	       0x10bd144fe start + 462

Thread 1:: nspr-1
0   libsystem_kernel.dylib        	    0x7ff81be58e4a __select + 10
1   VBoxXPCOM.dylib               	       0x1009198a0 0x10088f000 + 567456
2   VBoxXPCOM.dylib               	       0x10091b6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	       0x101623e75 0x101611000 + 77429
4   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 2:: nspr-2
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 3:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10ab8eda1 0x10aa95000 + 1023393
4   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
5   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 4:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091ede7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161671b 0x101611000 + 22299
5   VBoxXPCOMIPCC.dylib           	       0x1016163ed 0x101611000 + 21485
6   VBoxXPCOMIPCC.dylib           	       0x10161b039 0x101611000 + 41017
7   VBoxXPCOM.dylib               	       0x1009022ed 0x10088f000 + 471789
8   VBoxXPCOM.dylib               	       0x1009014eb 0x10088f000 + 468203
9   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
10  UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
11  QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
12  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
13  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bedf3c RTSemEventWait + 364
3   VBoxC.dylib                   	       0x10aada0d0 0x10aa95000 + 282832
4   VBoxC.dylib                   	       0x10aadb2fd 0x10aa95000 + 287485
5   VBoxC.dylib                   	       0x10ac7002a 0x10aa95000 + 1945642
6   UICommon.dylib                	       0x1054ff642 CEventSource::GetEvent(CEventListener const&, int) + 162
7   UICommon.dylib                	       0x105312a37 0x10522c000 + 944695
8   QtCoreVBox                    	       0x1016e796b 0x1016be000 + 170347
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 7:: nspr-3
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 8:: nspr-4
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxXPCOM.dylib               	       0x10091edfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	       0x10091f2ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	       0x10161c7b8 0x101611000 + 47032
5   VBoxXPCOM.dylib               	       0x1008f31f9 0x10088f000 + 410105
6   VBoxXPCOM.dylib               	       0x100920a96 0x10088f000 + 596630
7   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
8   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
9   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
10  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 9:: EMT
0   libsystem_kernel.dylib        	    0x7ff81be53fda __ioctl + 10
1   libsystem_kernel.dylib        	    0x7ff81be53fc7 ioctl + 150
2   VBoxRT.dylib                  	       0x100bfc4ad 0x100a47000 + 1791149
3   VBoxRT.dylib                  	       0x100bf46e6 SUPR3CallVMMR0Ex + 438
4   VBoxVMM.dylib                 	       0x102332681 0x102285000 + 710273
5   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
6   VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
7   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
8   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	    0x7ff81be50aba mach_msg_trap + 10
1   libsystem_kernel.dylib        	    0x7ff81be50e2b mach_msg + 59
2   CoreFoundation                	    0x7ff81bf53d51 __CFRunLoopServiceMachPort + 319
3   CoreFoundation                	    0x7ff81bf5240f __CFRunLoopRun + 1329
4   CoreFoundation                	    0x7ff81bf51809 CFRunLoopRunSpecific + 567
5   AppKit                        	    0x7ff81ea11cec _NSEventThread + 132
6   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
7   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 11:: AMCP Logging Spool
0   libsystem_kernel.dylib        	    0x7ff81be50af6 semaphore_wait_trap + 10
1   caulk                         	    0x7ff824d4e1c0 caulk::mach::semaphore::wait_or_error() + 16
2   caulk                         	    0x7ff824d3508a caulk::concurrent::details::worker_thread::run() + 36
3   caulk                         	    0x7ff824d34d4e void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41
4   libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
5   libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 12:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 13:: VMPwrDwn
0   libsystem_kernel.dylib        	    0x7ff81be53506 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	    0x7ff81be8da89 _pthread_cond_wait + 1224
2   VBoxRT.dylib                  	       0x100bee9c6 0x100a47000 + 1735110
3   VBoxRT.dylib                  	       0x100b36f73 0x100a47000 + 982899
4   VBoxVMM.dylib                 	       0x10232d00e 0x102285000 + 688142
5   VBoxVMM.dylib                 	       0x10232e9be VMR3Destroy + 270
6   VBoxC.dylib                   	       0x10ab02581 0x10aa95000 + 447873
7   VBoxC.dylib                   	       0x10ab285f7 0x10aa95000 + 603639
8   VBoxC.dylib                   	       0x10aae8a9c 0x10aa95000 + 342684
9   VBoxRT.dylib                  	       0x100b365ac 0x100a47000 + 980396
10  VBoxRT.dylib                  	       0x100bf1ecc 0x100a47000 + 1748684
11  libsystem_pthread.dylib       	    0x7ff81be8d514 _pthread_start + 125
12  libsystem_pthread.dylib       	    0x7ff81be8902f thread_start + 15

Thread 14:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0

Thread 15:
0   libsystem_pthread.dylib       	    0x7ff81be8900c start_wqthread + 0


No thread state (register information) available

Binary Images:
    0x7ff81e751000 -     0x7ff81e806fff com.apple.framework.IOKit (2.0.2) <7d46c110-4106-3280-9031-f7e035792f22> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
       0x10522c000 -        0x1072dcfff UICommon.dylib (*) <275d65cb-226c-39b5-a840-5143c6007a6b> /Applications/VirtualBox.app/Contents/MacOS/UICommon.dylib
       0x100553000 -        0x100676fff VirtualBoxVM.dylib (*) <3a6f5a29-74ff-313c-9220-82612f2b6fc7> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1016be000 -        0x101be5fff org.qt-project.QtCoreVBox (5.6) <3a7a08e0-9422-393e-bd97-fd15e751434c> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x10027b000 -        0x100282fff org.virtualbox.app.VirtualBoxVM (6.1.30) <43e613e0-b296-3de8-92e1-fbee61a51a5e> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x10bd0f000 -        0x10bd7afff dyld (*) <1a6ae033-9438-33c0-8077-988fd885250a> /usr/lib/dyld
    0x7ff81be50000 -     0x7ff81be86fff libsystem_kernel.dylib (*) <12bd6f13-c452-35ee-9069-51befef29f1a> /usr/lib/system/libsystem_kernel.dylib
       0x10088f000 -        0x100940fff VBoxXPCOM.dylib (*) <31c4ddec-f9f5-363e-ad9f-b8881543e336> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x101611000 -        0x101628fff VBoxXPCOMIPCC.dylib (*) <4e46eacb-3d27-3668-8e43-a455d494d839> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x100a47000 -        0x100fb1fff VBoxRT.dylib (*) <05fa665b-b1c8-3f62-861e-1b3579be4a9a> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
    0x7ff81be87000 -     0x7ff81be92fff libsystem_pthread.dylib (*) <29a2750e-f31b-3630-8761-242a6bc3e99e> /usr/lib/system/libsystem_pthread.dylib
       0x10aa95000 -        0x10aea3fff VBoxC.dylib (*) <7a8a2b64-5299-3eda-9b9b-85eac8f2d836> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x102285000 -        0x10258cfff VBoxVMM.dylib (*) <b600b9be-060e-373f-8e33-09248dd2c4b7> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
    0x7ff81bed4000 -     0x7ff81c3d4fff com.apple.CoreFoundation (6.9) <afcc752e-074d-340f-890c-263efd2da77f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7ff81e865000 -     0x7ff81f6f1fff com.apple.AppKit (6.9) <dd0028a3-78e3-3a8a-a51b-ddd68123adef> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7ff824d33000 -     0x7ff824d55fff com.apple.audio.caulk (1.0) <c5042b28-9206-337f-bfb2-dc0b37dd8632> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
               0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)
Writable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               256K        2 
Activity Tracing                   256K        1 
CG backing stores                  640K        4 
CG image                            48K        3 
CG raster data                     140K        3 
ColorSync                          224K       25 
CoreAnimation                     3892K       12 
CoreGraphics                        12K        2 
CoreServices                       304K        2 
CoreUI image data                  332K        5 
Foundation                          16K        1 
Kernel Alloc Once                    8K        1 
MALLOC                           381.5M      105 
MALLOC guard page                   48K        9 
MALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.1M       16 
Stack                             16.1M       16 
VM_ALLOCATE                       8312K       17 
__DATA                            35.6M      344 
__DATA_CONST                      14.2M      192 
__DATA_DIRTY                       638K      110 
__FONT_DATA                          4K        1 
__LINKEDIT                       644.7M       30 
__OBJC_RO                         81.6M        1 
__OBJC_RW                         3120K        2 
__TEXT                           326.9M      354 
__UNICODE                          588K        1 
dyld private memory               1024K        1 
mapped file                       90.2M       24 
shared memory                      808K       19 
===========                     =======  ======= 
TOTAL                              3.4G     1316 
TOTAL, minus reserved VM space     1.6G     1316 



-----------
Full Report
-----------

{""app_name"":""VirtualBoxVM"",""timestamp"":""2021-11-24 11:33:27.00 -0500"",""app_version"":""6.1.30"",""slice_uuid"":""43e613e0-b296-3de8-92e1-fbee61a51a5e"",""build_version"":""6.1.30"",""platform"":1,""bundleID"":""org.virtualbox.app.VirtualBoxVM"",""share_with_app_devs"":1,""is_first_party"":0,""bug_type"":""309"",""os_version"":""macOS 12.0.1 (21A559)"",""incident_id"":""BC924093-ADDD-4947-94C1-823F46F11168"",""name"":""VirtualBoxVM""}
{
  ""uptime"" : 39000,
  ""procLaunch"" : ""2021-11-24 00:42:47.3044 -0500"",
  ""procRole"" : ""Background"",
  ""version"" : 2,
  ""userID"" : 502,
  ""deployVersion"" : 210,
  ""modelCode"" : ""MacPro6,1"",
  ""procStartAbsTime"" : 258600882589,
  ""coalitionID"" : 788,
  ""osVersion"" : {
    ""train"" : ""macOS 12.0.1"",
    ""build"" : ""21A559"",
    ""releaseType"" : ""User""
  },
  ""captureTime"" : ""2021-11-24 11:33:23.4080 -0500"",
  ""incident"" : ""BC924093-ADDD-4947-94C1-823F46F11168"",
  ""bug_type"" : ""309"",
  ""pid"" : 983,
  ""procExitAbsTime"" : 39296637478404,
  ""cpuType"" : ""X86-64"",
  ""procName"" : ""VirtualBoxVM"",
  ""procPath"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
  ""bundleInfo"" : {""CFBundleShortVersionString"":""6.1.30"",""CFBundleVersion"":""6.1.30"",""CFBundleIdentifier"":""org.virtualbox.app.VirtualBoxVM""},
  ""storeInfo"" : {""deviceIdentifierForVendor"":""D2CBA99F-71A3-5B29-BC09-3089D1644C8E"",""thirdParty"":true},
  ""parentProc"" : ""VBoxSVC"",
  ""parentPid"" : 945,
  ""coalitionName"" : ""org.virtualbox.app.VirtualBox"",
  ""crashReporterKey"" : ""D29E8D31-4B9E-1252-579C-6F6F7174505F"",
  ""responsiblePid"" : 941,
  ""responsibleProc"" : ""VirtualBox"",
  ""sip"" : ""disabled"",
  ""vmRegionInfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""isCorpse"" : 1,
  ""exception"" : {""codes"":""0x0000000000000001, 0x000002c40000000c"",""rawCodes"":[1,3040836845580],""type"":""EXC_BAD_ACCESS"",""signal"":""SIGSEGV"",""subtype"":""KERN_INVALID_ADDRESS at 0x000002c40000000c""},
  ""termination"" : {""flags"":0,""code"":11,""namespace"":""SIGNAL"",""indicator"":""Segmentation fault: 11"",""byProc"":""exc handler"",""byPid"":983},
  ""vmregioninfo"" : ""0x2c40000000c is not in any region.  Bytes after previous region: 3034110459917  Bytes before following region: 102512279420916\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      CoreServices                190e88000-190ec8000    [  256K] rw-\/rwx SM=COW  \n--->  GAP OF 0x5ffe6f138000 BYTES\n      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-\/rwx SM=PRV  "",
  ""extMods"" : {""caller"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""system"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""targeted"":{""thread_create"":0,""thread_set_state"":0,""task_for_pid"":0},""warnings"":0},
  ""faultingThread"" : 0,
  ""threads"" : [{""triggered"":true,""id"":9449,""queue"":""com.apple.main-thread"",""frames"":[{""imageOffset"":256736,""symbol"":""IOHIDDeviceCopyMatchingElements"",""symbolLocation"":34,""imageIndex"":0},{""imageOffset"":3354536,""imageIndex"":1},{""imageOffset"":3354190,""symbol"":""DarwinHidDevicesApplyAndReleaseLedsState"",""symbolLocation"":590,""imageIndex"":1},{""imageOffset"":192146,""imageIndex"":2},{""imageOffset"":189951,""imageIndex"":2},{""imageOffset"":189813,""imageIndex"":2},{""imageOffset"":2208827,""symbol"":""QMetaObject::activate(QObject*, int, int, void**)"",""symbolLocation"":2075,""imageIndex"":3},{""imageOffset"":1997686,""symbol"":""QCoreApplication::exec()"",""symbolLocation"":390,""imageIndex"":3},{""imageOffset"":29742,""symbol"":""TrustedMain"",""symbolLocation"":1502,""imageIndex"":2},{""imageOffset"":16129,""imageIndex"":4},{""imageOffset"":21758,""symbol"":""start"",""symbolLocation"":462,""imageIndex"":5}]},{""id"":9456,""name"":""nspr-1"",""frames"":[{""imageOffset"":36426,""symbol"":""__select"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":567456,""imageIndex"":7},{""imageOffset"":575205,""symbol"":""PR_Poll"",""symbolLocation"":1061,""imageIndex"":7},{""imageOffset"":77429,""imageIndex"":8},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9457,""name"":""nspr-2"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9458,""name"":""VBoxSVCWatcher"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":1023393,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9459,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589287,""symbol"":""PR_WaitCondVar"",""symbolLocation"":231,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":22299,""imageIndex"":8},{""imageOffset"":21485,""imageIndex"":8},{""imageOffset"":41017,""imageIndex"":8},{""imageOffset"":471789,""imageIndex"":7},{""imageOffset"":468203,""imageIndex"":7},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9460,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9557,""name"":""UIMainEventListeningThread"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1732412,""symbol"":""RTSemEventWait"",""symbolLocation"":364,""imageIndex"":9},{""imageOffset"":282832,""imageIndex"":11},{""imageOffset"":287485,""imageIndex"":11},{""imageOffset"":1945642,""imageIndex"":11},{""imageOffset"":2963010,""symbol"":""CEventSource::GetEvent(CEventListener const&, int)"",""symbolLocation"":162,""imageIndex"":1},{""imageOffset"":944695,""imageIndex"":1},{""imageOffset"":170347,""imageIndex"":3},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9574,""name"":""nspr-3"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9576,""name"":""nspr-4"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":589310,""symbol"":""PR_WaitCondVar"",""symbolLocation"":254,""imageIndex"":7},{""imageOffset"":590509,""symbol"":""PR_Wait"",""symbolLocation"":61,""imageIndex"":7},{""imageOffset"":47032,""imageIndex"":8},{""imageOffset"":410105,""imageIndex"":7},{""imageOffset"":596630,""imageIndex"":7},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9579,""name"":""EMT"",""frames"":[{""imageOffset"":16346,""symbol"":""__ioctl"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":16327,""symbol"":""ioctl"",""symbolLocation"":150,""imageIndex"":6},{""imageOffset"":1791149,""imageIndex"":9},{""imageOffset"":1758950,""symbol"":""SUPR3CallVMMR0Ex"",""symbolLocation"":438,""imageIndex"":9},{""imageOffset"":710273,""imageIndex"":12},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9582,""name"":""com.apple.NSEventThread"",""frames"":[{""imageOffset"":2746,""symbol"":""mach_msg_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":3627,""symbol"":""mach_msg"",""symbolLocation"":59,""imageIndex"":6},{""imageOffset"":523601,""symbol"":""__CFRunLoopServiceMachPort"",""symbolLocation"":319,""imageIndex"":13},{""imageOffset"":517135,""symbol"":""__CFRunLoopRun"",""symbolLocation"":1329,""imageIndex"":13},{""imageOffset"":514057,""symbol"":""CFRunLoopRunSpecific"",""symbolLocation"":567,""imageIndex"":13},{""imageOffset"":1756396,""symbol"":""_NSEventThread"",""symbolLocation"":132,""imageIndex"":14},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":9603,""name"":""AMCP Logging Spool"",""frames"":[{""imageOffset"":2806,""symbol"":""semaphore_wait_trap"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":111040,""symbol"":""caulk::mach::semaphore::wait_or_error()"",""symbolLocation"":16,""imageIndex"":15},{""imageOffset"":8330,""symbol"":""caulk::concurrent::details::worker_thread::run()"",""symbolLocation"":36,""imageIndex"":15},{""imageOffset"":7502,""symbol"":""void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)"",""symbolLocation"":41,""imageIndex"":15},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341041,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341261,""name"":""VMPwrDwn"",""frames"":[{""imageOffset"":13574,""symbol"":""__psynch_cvwait"",""symbolLocation"":10,""imageIndex"":6},{""imageOffset"":27273,""symbol"":""_pthread_cond_wait"",""symbolLocation"":1224,""imageIndex"":10},{""imageOffset"":1735110,""imageIndex"":9},{""imageOffset"":982899,""imageIndex"":9},{""imageOffset"":688142,""imageIndex"":12},{""imageOffset"":694718,""symbol"":""VMR3Destroy"",""symbolLocation"":270,""imageIndex"":12},{""imageOffset"":447873,""imageIndex"":11},{""imageOffset"":603639,""imageIndex"":11},{""imageOffset"":342684,""imageIndex"":11},{""imageOffset"":980396,""imageIndex"":9},{""imageOffset"":1748684,""imageIndex"":9},{""imageOffset"":25876,""symbol"":""_pthread_start"",""symbolLocation"":125,""imageIndex"":10},{""imageOffset"":8239,""symbol"":""thread_start"",""symbolLocation"":15,""imageIndex"":10}]},{""id"":341263,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]},{""id"":341264,""frames"":[{""imageOffset"":8204,""symbol"":""start_wqthread"",""symbolLocation"":0,""imageIndex"":10}]}],
  ""usedImages"" : [
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703639605248,
    ""CFBundleShortVersionString"" : ""2.0.2"",
    ""CFBundleIdentifier"" : ""com.apple.framework.IOKit"",
    ""size"" : 745472,
    ""uuid"" : ""7d46c110-4106-3280-9031-f7e035792f22"",
    ""path"" : ""\/System\/Library\/Frameworks\/IOKit.framework\/Versions\/A\/IOKit"",
    ""name"" : ""IOKit""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4381130752,
    ""size"" : 34279424,
    ""uuid"" : ""275d65cb-226c-39b5-a840-5143c6007a6b"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/UICommon.dylib"",
    ""name"" : ""UICommon.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4300550144,
    ""size"" : 1196032,
    ""uuid"" : ""3a6f5a29-74ff-313c-9220-82612f2b6fc7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VirtualBoxVM.dylib"",
    ""name"" : ""VirtualBoxVM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318814208,
    ""CFBundleShortVersionString"" : ""5.6"",
    ""CFBundleIdentifier"" : ""org.qt-project.QtCoreVBox"",
    ""size"" : 5406720,
    ""uuid"" : ""3a7a08e0-9422-393e-bd97-fd15e751434c"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Frameworks\/QtCoreVBox.framework\/Versions\/5\/QtCoreVBox"",
    ""name"" : ""QtCoreVBox"",
    ""CFBundleVersion"" : ""5.6.3""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4297568256,
    ""CFBundleShortVersionString"" : ""6.1.30"",
    ""CFBundleIdentifier"" : ""org.virtualbox.app.VirtualBoxVM"",
    ""size"" : 32768,
    ""uuid"" : ""43e613e0-b296-3de8-92e1-fbee61a51a5e"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/Resources\/VirtualBoxVM.app\/Contents\/MacOS\/VirtualBoxVM"",
    ""name"" : ""VirtualBoxVM"",
    ""CFBundleVersion"" : ""6.1.30""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4493209600,
    ""size"" : 442368,
    ""uuid"" : ""1a6ae033-9438-33c0-8077-988fd885250a"",
    ""path"" : ""\/usr\/lib\/dyld"",
    ""name"" : ""dyld""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596609536,
    ""size"" : 225280,
    ""uuid"" : ""12bd6f13-c452-35ee-9069-51befef29f1a"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_kernel.dylib"",
    ""name"" : ""libsystem_kernel.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4303941632,
    ""size"" : 729088,
    ""uuid"" : ""31c4ddec-f9f5-363e-ad9f-b8881543e336"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxXPCOM.dylib"",
    ""name"" : ""VBoxXPCOM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4318105600,
    ""size"" : 98304,
    ""uuid"" : ""4e46eacb-3d27-3668-8e43-a455d494d839"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxXPCOMIPCC.dylib"",
    ""name"" : ""VBoxXPCOMIPCC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4305743872,
    ""size"" : 5681152,
    ""uuid"" : ""05fa665b-b1c8-3f62-861e-1b3579be4a9a"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxRT.dylib"",
    ""name"" : ""VBoxRT.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703596834816,
    ""size"" : 49152,
    ""uuid"" : ""29a2750e-f31b-3630-8761-242a6bc3e99e"",
    ""path"" : ""\/usr\/lib\/system\/libsystem_pthread.dylib"",
    ""name"" : ""libsystem_pthread.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4473835520,
    ""size"" : 4255744,
    ""uuid"" : ""7a8a2b64-5299-3eda-9b9b-85eac8f2d836"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/components\/VBoxC.dylib"",
    ""name"" : ""VBoxC.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 4331163648,
    ""size"" : 3178496,
    ""uuid"" : ""b600b9be-060e-373f-8e33-09248dd2c4b7"",
    ""path"" : ""\/Applications\/VirtualBox.app\/Contents\/MacOS\/VBoxVMM.dylib"",
    ""name"" : ""VBoxVMM.dylib""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703597150208,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.CoreFoundation"",
    ""size"" : 5246976,
    ""uuid"" : ""afcc752e-074d-340f-890c-263efd2da77f"",
    ""path"" : ""\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation"",
    ""name"" : ""CoreFoundation"",
    ""CFBundleVersion"" : ""1855.105""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703640735744,
    ""CFBundleShortVersionString"" : ""6.9"",
    ""CFBundleIdentifier"" : ""com.apple.AppKit"",
    ""size"" : 15257600,
    ""uuid"" : ""dd0028a3-78e3-3a8a-a51b-ddd68123adef"",
    ""path"" : ""\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit"",
    ""name"" : ""AppKit"",
    ""CFBundleVersion"" : ""2113""
  },
  {
    ""source"" : ""P"",
    ""arch"" : ""x86_64"",
    ""base"" : 140703746437120,
    ""CFBundleShortVersionString"" : ""1.0"",
    ""CFBundleIdentifier"" : ""com.apple.audio.caulk"",
    ""size"" : 143360,
    ""uuid"" : ""c5042b28-9206-337f-bfb2-dc0b37dd8632"",
    ""path"" : ""\/System\/Library\/PrivateFrameworks\/caulk.framework\/Versions\/A\/caulk"",
    ""name"" : ""caulk""
  },
  {
    ""size"" : 0,
    ""source"" : ""A"",
    ""base"" : 0,
    ""uuid"" : ""00000000-0000-0000-0000-000000000000""
  }
],
  ""sharedCache"" : {
  ""base"" : 140703593594880,
  ""size"" : 15215640576,
  ""uuid"" : ""b5084610-afe4-3485-bade-628c4468b057""
},
  ""vmSummary"" : ""ReadOnly portion of Libraries: Total=971.6M resident=0K(0%) swapped_out_or_unallocated=971.6M(100%)\nWritable regions: Total=2.2G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.2G(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nAccelerate framework               256K        2 \nActivity Tracing                   256K        1 \nCG backing stores                  640K        4 \nCG image                            48K        3 \nCG raster data                     140K        3 \nColorSync                          224K       25 \nCoreAnimation                     3892K       12 \nCoreGraphics                        12K        2 \nCoreServices                       304K        2 \nCoreUI image data                  332K        5 \nFoundation                          16K        1 \nKernel Alloc Once                    8K        1 \nMALLOC                           381.5M      105 \nMALLOC guard page                   48K        9 \nMALLOC_MEDIUM (reserved)           1.4G       12         reserved VM address space (unallocated)\nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.1M       16 \nStack                             16.1M       16 \nVM_ALLOCATE                       8312K       17 \n__DATA                            35.6M      344 \n__DATA_CONST                      14.2M      192 \n__DATA_DIRTY                       638K      110 \n__FONT_DATA                          4K        1 \n__LINKEDIT                       644.7M       30 \n__OBJC_RO                         81.6M        1 \n__OBJC_RW                         3120K        2 \n__TEXT                           326.9M      354 \n__UNICODE                          588K        1 \ndyld private memory               1024K        1 \nmapped file                       90.2M       24 \nshared memory                      808K       19 \n===========                     =======  ======= \nTOTAL                              3.4G     1316 \nTOTAL, minus reserved VM space     1.6G     1316 \n"",
  ""legacyInfo"" : {
  ""threadTriggered"" : {
    ""queue"" : ""com.apple.main-thread""
  }
},
  ""trialInfo"" : {
  ""rollouts"" : null,
  ""experiments"" : null
},
  ""reportNotes"" : [
  ""thread_get_state(PAGEIN) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(EXCEPTION) returned 0x10000003: (ipc\/send) invalid destination port"",
  ""thread_get_state(FLAVOR) returned 0x10000003: (ipc\/send) invalid destination port""
]
}

Model: MacPro6,1, BootROM 429.40.7.0.1, 6 processors, 6-Core Intel Xeon E5, 3.5 GHz, 32 GB, SMC 2.20f18
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Graphics: AMD FirePro D300, AMD FirePro D300, PCIe, 2 GB
Display: DELL E207WFP, 1680 x 1050 (Widescreen Super eXtended Graphics Array Plus), Main, MirrorOff, Online
Memory Module: DIMM1, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM2, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM3, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
Memory Module: DIMM4, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.2)
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: AMD FirePro D300, Display Controller, Slot-1
PCI Card: AMD FirePro D300, Display Controller, Slot-2
PCI Card: pci1b4b,9235, AHCI Controller, Thunderbolt@81,0,0
PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@236,0,0
Serial ATA Device: WDC  WDS100T2B0A-00SM50, 1 TB
Serial ATA Device: TEAM T253A3001T, 1.02 TB
Serial ATA Device: HGST HDN726060ALE614, 6 TB
Serial ATA Device: HGST HUH728060ALE600, 6 TB
USB Device: USB30Bus
USB Device: 4-Port USB 3.0 Hub
USB Device: 4-Port USB 3.0 Hub
USB Device: Mercury Pro
USB Device: USB3.0 Hub
USB Device: JMS56x Series
USB Device: Elite Pro U3FW
USB Device: Elements 25A3
USB Device: 4-Port USB 2.0 Hub
USB Device: 4-Port USB 2.0 Hub
USB Device: USB2.0 Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: MFC-J450DW
USB Device: hub_device
USB Device: hub_device
USB Device: Flash Card Reader
USB Device: USB Camera
USB Device: USB20Bus
USB Device: hub_device
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: RocketStor 5212, HighPoint Technologies, Inc., 1, 7.1
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
Thunderbolt Device: Drive Dock, Other World Computing, 1, 25.1
",mauricev
19606,OS X Virtual machine has async io problems causing iy to fail,Mac OS X,VirtualBox 6.1.8,2020-05-20T10:56:29Z,2021-10-22T06:38:57Z,2021-10-22T06:38:57Z,"Getting these messages during the install.  It's accessing the ISO installation CD and the VDI disk. I've tried different chip types, and had best success using the same ATA controller for both the CD image and the installation drive.  When using the SATA, it seems to fail, but I haven't looked at the logs.  I assume it's the same problem. Here's a bit of the log file from the VM.

00:52:18.532264 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:20.452002 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:22.372029 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:24.292006 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:26.212237 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:27.112089 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (51722074 usec ago) CmdIf1=0x00 (-1 usec ago)
00:52:28.172301 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:30.091945 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:32.011961 PIIX3 ATA LUN#2: Async I/O thread probably stuck in operation, interrupting
00:52:33.528271 AsyncCompletion: Task 0x00000113628f00 completed after 141 seconds
00:52:33.528418 PIIX3 ATA: execution time for ATA command 0xca was 141 seconds
00:52:33.528437 PIIX3 ATA: Ctl#0: finished processing RESET
00:52:33.528568 AsyncCompletion: Task 0x00000113628fc0 completed after 58 seconds
00:52:33.528585 PIIX3 ATA: execution time for ATAPI command 0x28 was 58 seconds
00:52:33.528604 PIIX3 ATA: Ctl#1: finished processing RESET

The VM Manager also SEGFAULTed when I powered off the machine, and I'll attach the crash dump output as well.

This is also present in versions 5.2 and 6.0 releases as well.",unixwzrd
20547,Promiscuous Mode Does Not Work on macOS 11.5.2,Mac OS X,VirtualBox 6.1.26,2021-09-14T05:03:41Z,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
20506,Attaching Yubikey USB device to VM causes Guest VM to Crash within Seconds,Mac OS X,VirtualBox 6.1.26,2021-08-18T20:19:16Z,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
20477,log spam/constant high cpu usage related to audio,Mac OS X,VirtualBox 6.1.22,2021-07-25T08:30:05Z,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
20370,Virtual machine running slow and lagging.,Mac OS X,VirtualBox 6.1.22,2021-05-19T05:23:25Z,2021-05-19T05:23:25Z,2021-05-19T05:23:25Z,I am experiencing a lot of lag while running my system. Especially when I start the browser in the guest os. I cannot run any other program and my screen freezes. The refresh rate and the response speed are also very slow. And when I start the VM box I need to minimize it first or else the guest os won't load up. I hope you can look into this issue and get to me back with a proper fix for this issue. I also tried seeking help from the forum but those solutions don't seem to work for me. Thank you in advance. ,red66
20232,Cannot exec files on vboxsf on newer kernels,Mac OS X,VirtualBox 6.1.18,2021-03-04T00:22:23Z,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
20331,Error NS_ERROR_FAILURE (0x80004005),Mac OS X,VirtualBox 6.1.20,2021-04-30T10:45:50Z,2021-04-30T10:45:50Z,2021-04-30T10:45:50Z,"Everytime I tried to open an ISO file error happened. 

OSX Big Sur 11.3 (20E232)

Nothing in log file. Just an error I attached here. ",r0mkan
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,VirtualBox 6.1.20,2021-04-29T15:50:49Z,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
20283,Network issues on Guest-VM,Mac OS X,VirtualBox 6.1.18,2021-04-02T19:41:36Z,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
18776,"Vagrant shared folders unable to install Package Management Plugins (Composer, PHP)",Mac OS X,VirtualBox 6.0.10,2019-07-21T16:22:45Z,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
20261,VBoxManage import without eula acceptance returns exit code zero,Mac OS X,VirtualBox 6.1.18,2021-03-17T16:03:06Z,2021-03-17T16:03:06Z,2021-03-17T16:03:06Z,"Hello!  I have just noticed, when doing a VBoxManage import, the command exits with exit code zero (success) even when there is a license-acceptance error.

I am running VirtualBox 6.1.18r142142.  To ensure I was up-to-date, I downloaded the 6.1.18 .dmg, used the uninstall script to uninstall, rebooted, and then used the installer to install VirtualBox (including all optional components).

Here are steps to reproduce:

1. Download the [https://www.linuxvmimages.com/images/debian-10/ Debian 10 VirtualBox image] from [https://www.linuxvmimages.com/ linuxvmimages.com] (direct link: https://sourceforge.net/projects/linuxvmimages/files/VirtualBox/D/10/Debian_10.7.0_VB.zip/download).
2. Unzip the .zip file, and get the path to the .ova file.
3. Run the command `VBoxManage import PATH_TO_OVA_FILE`.

Here is the output of what happens:

{{{
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage --version
6.1.18r142142
ITS-C02C91G0MD6R:~ akkornel(nc)$ VBoxManage import /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/akkornel/Downloads/Debian_10.7.0_VB/Debian_10.7.0_VB_LinuxVMImages.COM.ova...
OK.
Disks:
  vmdisk1	549755813888	-1	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk	-1	-1

Virtual system 0:
 0: Suggested OS type: ""Debian_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""Debian_10.7.0_VB_LinuxVMImages.COM""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/Users/akkornel/VirtualBox VMs/Debian_10.7.0_VB_LinuxVMImages.COM/Debian_10.7.0_VB_LinuxVMImages.COM.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/Users/akkornel/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Debian 10.7.0
 6: Vendor (ignored): Debian Community
 7: Version (ignored): 10.7.0
 8: ProductUrl (ignored): https://www.linuxvmimages.com/debian-10
 9: VendorUrl (ignored): https://debian.org
10: Description ""Debian 10.7.0 VirtualBox Image
User Name: debian
Password: debian""
    (change with ""--vsys 0 --description <desc>"")
11: End-user license agreement
    (display with ""--vsys 0 --eula show"";
    accept with ""--vsys 0 --eula accept"")
12: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
13: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
14: Sound card (appliance expects """", can change on import)
    (disable with ""--vsys 0 --unit 14 --ignore"")
15: USB controller
    (disable with ""--vsys 0 --unit 15 --ignore"")
16: Network adapter: orig Bridged, config 3, extra slot=0;type=Bridged
17: CD-ROM
    (disable with ""--vsys 0 --unit 17 --ignore"")
18: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 18 --ignore"")
19: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 19 --ignore"")
20: SATA controller, type AHCI
    (disable with ""--vsys 0 --unit 20 --ignore"")
21: Hard disk image: source image=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, target path=Debian_10.7.0_VB_LinuxVMImages.COM-disk001.vmdk, controller=20;channel=0
    (change target path with ""--vsys 0 --unit 21 --disk path"";
    disable with ""--vsys 0 --unit 21 --ignore"")
VBoxManage: error: Cannot import until the license agreement listed above is accepted.
ITS-C02C91G0MD6R:~ akkornel(nc)$ echo $?
0
}}}

Notice how VBoxManage returns exit code zero.

I think the problem is in [https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp?rev=73217#L940 VBox/Frontends/VBoxManage/VBoxManageAppliance.cpp around line 940].  It looks like although `RTMsgError` is called to report the problem, `rc` is never set to indicate a problem, so `RTEXITCODE_SUCCESS` ends up bring returned.",akkornel
16436,Lagging and long pauses in all guests on recent MacOS hosts,Mac OS X,VirtualBox 5.1.14,2017-01-31T01:45:13Z,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
20231,Network: it is not possible to set the Guest port in the Port Forwarding section (NAT),Mac OS X,VirtualBox 6.1.18,2021-03-02T18:36:21Z,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
20168,Linux guest / Mac host - uid option stopped working,Mac OS X,VirtualBox 6.1.18,2021-02-02T17:35:41Z,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
19545,"Regression related to shared folders, npm install",Mac OS X,VirtualBox 6.1.6,2020-05-01T04:53:28Z,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
19914,guest display reacts very slowly,Mac OS X,VirtualBox 6.1.14,2020-09-24T21:01:35Z,2020-09-24T21:01:35Z,2020-09-24T21:01:35Z,"Hello I want to run Debian Buster as guest on Mac OS X as host. Installation worked, but the guest display reacts very slowly and randers it unusable. When doing a SSH to the guest, I see that CPU usage is almost zero. Why is the display part broken?",kouros
19370,On power off error at line 580 in VBoxManageControlVM.cpp in 6.0.18,Mac OS X,VirtualBox 6.0.18,2020-03-02T09:57:22Z,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
19774,RDP connection fails with error code 0xd06 with MS Android client,Mac OS X,VirtualBox 6.1.10,2020-07-28T10:43:58Z,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
19041,Debian Buster guest aborted after host resumes from sleep,Mac OS X,VirtualBox 6.0.14,2019-10-23T02:12:52Z,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
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,VirtualBox 6.1.10,2020-06-25T09:31:23Z,2020-07-18T01:38:24Z,2020-07-18T01:38:24Z,"Hi,

I've got a crash of VirtualBoxVM 6.1.10 Ubuntu 18.04 guest on macOS 10.15.5 host after installing 6.1.10 guest additions. This crash occurs every time I try to boot up this VM right after entering the Login credentials into the guest. See attached log files",Lars Sonchocky-Helldorf
19701,Cannot list raw disk partition table when sector size != 512 bytes,Mac OS X,VirtualBox 6.1.10,2020-07-04T07:03:36Z,2020-07-04T07:04:52Z,2020-07-04T07:04:52Z,"VBoxManage returns an empty partition table when the disk has a sector size of 4096 bytes. I think this may be the root cause of the problems reported in tickets

https://www.virtualbox.org/ticket/16705

https://www.virtualbox.org/ticket/16498

{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
}}}
fdisk (on linux) return the following information about the drive.
{{{
Disk model: Expansion Desk  
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 268431360 bytes
Disklabel type: gpt
Disk identifier: C3BE927E-B799-4B59-A37F-8927D38FA8BF

Device         Start       End   Sectors   Size Type
/dev/sdf1          6     76805     76800   300M EFI System
/dev/sdf2      76806  61110489  61033684 232.8G Apple APFS
/dev/sdf3   61143258 482519263 421376006   1.6T Linux filesystem
/dev/sdf4  482552032 488345871   5793840  22.1G Linux swap
}}}

Using a disk with a sector size of 512 bytes is successful.
{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/disk8
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x00  0   /0  /0   0   /0  /0            200           40
2       0x00  0   /0  /0   0   /0  /0         238546       409640
3       0x00  0   /0  /0   0   /0  /0        1648981    488953032
4       0x00  0   /0  /0   0   /0  /0          20001   3866066944
}}}
fdisk for this drive shows
{{{
Disk model: 006-2DM164      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 0F3513DC-A778-4280-BB61-5399F44E1135

Device          Start        End    Sectors  Size Type
/dev/sdf1          40     409639     409600  200M EFI System
/dev/sdf2      409640  488953031  488543392  233G Apple APFS
/dev/sdf3   488953032 3866066943 3377113912  1.6T Linux filesystem
/dev/sdf4  3866066944 3907028991   40962048 19.5G Linux swap
}}}",granada29
19681,Linux Mint 32-bit Guest will not fully restart on Mac OS X Catalina host after installed Guest Additions,Mac OS X,VirtualBox 6.1.10,2020-06-25T18:25:12Z,2020-06-30T14:37:01Z,2020-06-30T14:37:01Z,"After I installed the Guest Additions on my 32-bit Linux Mint virtual machine, the VM Guest will not restart properly. I can enter my user password, but then the operating system won't finish booting to the desktop, and it appears to hang on a blank screen. I left the Guest machine sitting for ~ 20 minutes on the blank screen before I give up and force it to stop.

Approximate steps
- Create a blank virtual machine: Ubuntu 32-bit, ~3.5GB Memory, 30GB hard drive (VDI, dynamic)
- Start the virtual machine, when prompted insert the Linux ISO
- Complete the operating system installation
- When prompted, remove the ISO from Optical drive and restart VM 
- Install operating system updates in Synaptic and restart VM
- Insert the Guest Additions CD and run the installer
- After Guest Additions finishes installation, restart the VM
- Enter the user password & Wait for the machine to finish boot

Observed; the Guest machine just appears to hang on blank black screen. Eventually give up waiting, and click the red dot to close Guest window and force shut down.

In case I made a mistake, I tried deleting & recreating the virtual machine guest again, but same issue occurs again after install Guest Additions.

Additional machine details:
- Host is Mac OS X Catalina 10.15.5
- VirtualBox Version 6.1.10 r138449 (Qt5.6.3)
- Oracle VM VirtualBox Extension Pack v6.1.10r138449 previously installed
- Guest installed with Linux Mint 19.3 Cinnamon 32-bit",keffie
19670,"Automatic VM name-based configuration assumes ""32"" means ""32-bit""",Mac OS X,VirtualBox 6.1.10,2020-06-17T13:45:31Z,2020-06-23T11:42:20Z,2020-06-23T11:42:20Z,"Fedora 32 is not 32-bit Fedora

I attempted to set up a VM today for version 32 of Fedora x64. When I tried to create a VM named ""Fedora 32"" the creation tool assumed I meant 32-bit Fedora. This lead to several minutes of confusion as I tried to figure out why booting up the Fedora Workstation 32 x64 ISO kept telling me it couldn't run on a 32-bit processor.

I eventually figured out what had happened, and tried to manually change the VM's CPU from 32-bit to x64. However, the ISO still kept insisting that I had a 32-bit processor. Eventually, I had to destroy the VM and create one from scratch.

Not completely sure this is actually a bug, but the algorithm could be fine-tuned to work better, or perhaps provide more noticeable feedback when it changes the ""bit-ness"" of the VM.",imrazor
18089,Host CPU load 100% for idle guest,Mac OS X,VirtualBox 5.2.20,2018-10-30T08:21:29Z,2020-06-10T16:51:40Z,2020-06-10T16:51:40Z,"Host: macOS 10.12.6
Guest: Linux (Ubuntu 16.04)

After upgrading Virtualbox to 5.2.20, I ran a single guest which I'd used many times before.  The guest decided to do an auto-update, which is fine.

However even after the update had finished, on the *host*, CPU used by the VirtualBox process remained stuck at 100%, as shown by Activity Monitor and (here) ""top -o cpu"":

{{{
Processes: 326 total, 3 running, 323 sleeping, 1550 threads                                                         08:15:02
Load Avg: 2.34, 2.50, 2.10  CPU usage: 31.47% user, 7.26% sys, 61.25% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 65898 total, 7787M resident, 147M private, 1418M shared.
PhysMem: 14G used (4448M wired), 2268M unused. VM: 879G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 197313/179M in, 123489/30M out. Disks: 385658/8849M read, 161264/4111M written.

PID   COMMAND      %CPU  TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS         %CPU_ME %CPU_OTHRS
1810  VirtualBoxVM 105.5 17:19.54 44/1  5    392   2193M  8048K  0B     1810 1805 running  *1[5]          0.00000 0.00000
335   iTerm2       14.6  01:56.18 11    5    281-  164M-  34M-   0B     335  1    sleeping *0[305]        0.04101 1.50065
}}}

But inside the *guest*, CPU was ~99% idle.  Again, here with ""top"" but inside the guest:

{{{
top - 08:16:00 up 44 min,  1 user,  load average: 0.00, 0.07, 0.11
Tasks: 583 total,   1 running, 582 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.3 us,  0.3 sy,  0.0 ni, 99.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  2048156 total,   238796 free,  1136680 used,   672680 buff/cache
KiB Swap:   786428 total,   747596 free,    38832 used.   554244 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
 4441 101001    20   0 2552704  62904  14900 S  0.3  3.1   0:05.32 java
 7579 brian     20   0   42240   4268   3172 R  0.3  0.2   0:00.02 top
    1 root      20   0   38320   6280   4016 S  0.0  0.3   0:02.16 systemd
}}}

After shutting down and restarting the guest, the problem went away. This again on the host:

{{{
Processes: 325 total, 3 running, 322 sleeping, 1501 threads                                                         08:18:39
Load Avg: 1.90, 2.28, 2.10  CPU usage: 2.68% user, 6.34% sys, 90.97% idle
SharedLibs: 229M resident, 51M data, 62M linkedit. MemRegions: 66300 total, 7793M resident, 150M private, 1428M shared.
PhysMem: 14G used (4458M wired), 2178M unused. VM: 876G vsize, 627M framework vsize, 0(0) swapins, 0(0) swapouts.
Networks: packets: 201757/182M in, 127536/32M out. Disks: 419879/9460M read, 166954/4317M written.

PID   COMMAND      %CPU TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP PPID STATE    BOOSTS          %CPU_ME %CPU_OTHRS
6140  VirtualBoxVM 7.8  00:49.13 41    4    396   2144M  18M    0B     6140 1805 sleeping *1[4]           0.00000 0.00000
0     kernel_task  7.1  07:13.29 134/4 0    2     1199M  0B     0B     0    0    running   0[0]           0.00000 0.00000
}}}
",bcandler
18927,VBoxClient clipboard fails to copy rich text from guest to host,Mac OS X,VirtualBox 6.0.12,2019-09-12T20:04:52Z,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
19628,"Segmentation fault KERN_INVALID_ADDRESS, MacOS host",Mac OS X,VirtualBox 6.1.8,2020-05-28T09:36:45Z,2020-05-28T09:36:45Z,2020-05-28T09:36:45Z,"MacOS host, Linux (OpenSUSE Tumbleweed) guest.
VM starts up, but segfaults when GUI startup happens. Crashes both VBox 6.1.6 and 6.1.8.

Part of the crashreport for easier searching:

{{{
Process:               VirtualBoxVM [867]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.1.8 (6.1.8)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [796]
Responsible:           VirtualBox [785]
User ID:               501

Date/Time:             2020-05-28 12:29:59.960 +0300
OS Version:            Mac OS X 10.15.5 (19F96)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        7F0F4F94-AA59-F9D4-DA55-099371894FD2


Time Awake Since Boot: 140 seconds

System Integrity Protection: enabled

Crashed Thread:        11  EMT-1

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [867]
}}}",Richlv
19607,Very high energy consumption by 6.1.8 on Mac OS X,Mac OS X,VirtualBox 6.1.8,2020-05-20T17:26:02Z,2020-05-22T14:52:01Z,2020-05-22T14:52:01Z,"With 6.1.8 on MacOS I'm was seeing very high energy consumption, so much so that my battery level was dropping despite being plugged in. I had to downgrade to 6.1.6.
",tg7747
18127,"Kernel Panic (""a freed zone element has been modified in zone kalloc.16) with 5.2.22 on Mac OSx",Mac OS X,VirtualBox 5.2.22,2018-11-13T10:16:51Z,2020-05-15T08:54:30Z,2020-05-15T08:54:30Z,"Hello,
after upgrading VirtualBox (including extensions) to 5.2.22 my MacBook runs into kernel panics as soon as I deleted some files in my VM Guest (OEL 6.7) and tried to recreate them.

Kernel panic looks like this (no additional messages in VBox.log) - just copied and pasted two of them.

{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 11:07:05 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff80058b8ff7): ""a freed zone element has been modified in zone kalloc.16: expected 0xc0ffee0af45053f8 but found 0x10000c0ec035, bits changed 0xc0fffe0af85e93cd, at offset 0 of 16 in element 0xffffff804b1e5140, cookies 0x3f00118abf4e05f8 0x53521ec3d6d4d23""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 0), Frame : Return Address
0xffffff81fdf7b980 : 0xffffff800586b1c6 
0xffffff81fdf7b9d0 : 0xffffff8005993a74 
0xffffff81fdf7ba10 : 0xffffff8005985d44 
0xffffff81fdf7ba80 : 0xffffff800581d1e0 
0xffffff81fdf7baa0 : 0xffffff800586ac3c 
0xffffff81fdf7bbd0 : 0xffffff800586a9fc 
0xffffff81fdf7bc30 : 0xffffff80058b8ff7 
0xffffff81fdf7bc90 : 0xffffff80058b8910 
0xffffff81fdf7bce0 : 0xffffff80058b7313 
0xffffff81fdf7be10 : 0xffffff8005876c44 
0xffffff81fdf7be80 : 0xffffff8005ce5ba3 
0xffffff81fdf7bed0 : 0xffffff8005ce5a50 
0xffffff81fdf7bf40 : 0xffffff8005e03008 
0xffffff81fdf7bfa0 : 0xffffff800581d9c6 

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000005600000
Kernel text base: 0xffffff8005800000
__HIB  text base: 0xffffff8005700000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 519699934001
last loaded kext at 248994916223: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f868a3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AudioAUUC	1.70
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.filesystems.autofs	3.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.AppleHDAHardwareConfigDriver	281.52
com.apple.driver.AppleHDA	281.52
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.ACPI_SMC_PlatformPlugin	1.0.0
com.apple.driver.eficheck	1
com.apple.driver.AppleFIVRDriver	4.1.0
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AGDCBacklightControl	3.20.0
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.iokit.SCSITaskUserClient	404.30.2
com.apple.filesystems.apfs	748.51.0
com.apple.driver.AppleFileSystemDriver	3.0.1
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.driver.usb.cdc.acm	5.0.0
com.apple.kext.triggers	1.0
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.AppleGPUWrangler	3.20.0
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.driver.IOPlatformPluginLegacy	1.0.0
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.AppleThunderboltEDMSink	4.1.4
com.apple.driver.AppleThunderboltDPOutAdapter	5.5.5
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.AppleUSBMergeNub	900.4.1
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.driver.AppleXsanScheme	3
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}


{{{
Anonymous UUID:       82237E1E-63F4-6DBD-263D-F8CCD0BD2352

Tue Nov 13 10:58:16 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff8001cb903d): ""a freed zone element has been modified in zone kalloc.16: expected 0xe4988e3ed03a8352 but found 0xdeadbeef00000001, bits changed 0x3a3530d1d03a8353, at offset 0 of 16 in element 0xffffff8048db0cf0, cookies 0x3f00113912711a2e 0x53521e81ce62793""@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/zalloc.c:1122
Backtrace (CPU 2), Frame : Return Address
0xffffff91ffcbb750 : 0xffffff8001c6b1c6 
0xffffff91ffcbb7a0 : 0xffffff8001d93a74 
0xffffff91ffcbb7e0 : 0xffffff8001d85d44 
0xffffff91ffcbb850 : 0xffffff8001c1d1e0 
0xffffff91ffcbb870 : 0xffffff8001c6ac3c 
0xffffff91ffcbb9a0 : 0xffffff8001c6a9fc 
0xffffff91ffcbba00 : 0xffffff8001cb903d 
0xffffff91ffcbba60 : 0xffffff8001cb8910 
0xffffff91ffcbbab0 : 0xffffff8001cb7313 
0xffffff91ffcbbbe0 : 0xffffff8001c76c44 
0xffffff91ffcbbc50 : 0xffffff8002215d8c 
0xffffff91ffcbbc70 : 0xffffff8002215df2 
0xffffff91ffcbbc90 : 0xffffff800226779d 
0xffffff91ffcbbcb0 : 0xffffff800226780c 
0xffffff91ffcbbcd0 : 0xffffff80022638fc 
0xffffff91ffcbbd10 : 0xffffff80022c842f 
0xffffff91ffcbbd70 : 0xffffff8001d42b7b 
0xffffff91ffcbbdc0 : 0xffffff8001c706e0 
0xffffff91ffcbbe10 : 0xffffff8001c4da3d 
0xffffff91ffcbbe60 : 0xffffff8001c6054b 
0xffffff91ffcbbef0 : 0xffffff8001d6ff1d 
0xffffff91ffcbbfa0 : 0xffffff8001c1d9e6 

BSD process name corresponding to current thread: VBoxSVC

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide:     0x0000000001a00000
Kernel text base: 0xffffff8001c00000
__HIB  text base: 0xffffff8001b00000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 6013699815144
last loaded kext at 245870616385: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f82ca3000, size 69632)
last unloaded kext at 403105650360: com.apple.driver.AppleFileSystemDriver	3.0.1 (addr 0xffffff7f82804000, size 8192)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.22
org.virtualbox.kext.VBoxNetFlt	5.2.22
org.virtualbox.kext.VBoxUSB	5.2.22
org.virtualbox.kext.VBoxDrv	5.2.22
com.apple.driver.AudioAUUC	1.70
com.apple.filesystems.autofs	3.0
com.apple.driver.AGPM	110.23.37
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.driver.AppleHDA	281.52
com.apple.driver.AppleGraphicsDevicePolicy	3.20.14
com.apple.AGDCPluginDisplayMetrics	3.20.0
com.apple.driver.AppleIntelKBLGraphics	10.3.6
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.7f11
com.apple.driver.AppleThunderboltIP	3.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	10.3.6
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AppleSMCLMU	211
com.apple.driver.AppleCameraInterface	6.01.2
com.apple.driver.pmtelemetry	1
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleBacklight	170.12.6
com.apple.driver.AppleMCCSControl	1.5.5
com.apple.driver.usb.AppleUSBHostBillboardDevice	1.0
com.apple.filesystems.apfs	748.51.0
com.apple.filesystems.hfs.kext	407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleTopCaseHIDEventDriver	135
com.apple.driver.AirPort.BrcmNIC	1241.31.1a9
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	183
com.apple.security.TMSafetyNet	8
com.apple.security.quarantine	3
com.apple.driver.usb.cdc.ncm	5.0.0
com.apple.iokit.IOUSBUserClient	900.4.1
com.apple.kext.triggers	1.0
com.apple.driver.DspFuncLib	281.52
com.apple.kext.OSvKernDSPLib	526
com.apple.driver.AppleGraphicsControl	3.20.14
com.apple.iokit.IOAVBFamily	683.1
com.apple.plugin.IOgPTPPlugin	680.15
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport	6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.7f11
com.apple.driver.AppleSSE	1.0
com.apple.iokit.IOAcceleratorFamily2	378.26
com.apple.iokit.IOSurface	211.15
com.apple.driver.AppleHDAController	281.52
com.apple.iokit.IOHDAFamily	281.52
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.driver.AppleIntelLpssUARTv1	3.0.60
com.apple.driver.AppleIntelLpssUARTCommon	3.0.60
com.apple.driver.AppleOnboardSerial	1.0
com.apple.iokit.IOSkywalkFamily	1
com.apple.iokit.IOSerialFamily	11
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.AppleGPUWrangler	3.20.0
com.apple.AppleGraphicsDeviceControl	3.20.14
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	519.21
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.iokit.IOGraphicsFamily	519.21
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc.ecm	5.0.0
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleActuatorDriver	1614.1
com.apple.driver.AppleHIDKeyboard	205.1
com.apple.driver.AppleHSBluetoothDriver	135
com.apple.driver.IOBluetoothHIDDriver	6.0.7f11
com.apple.iokit.IOBluetoothFamily	6.0.7f11
com.apple.driver.AppleMultitouchDriver	1614.1
com.apple.driver.AppleInputDeviceSupport	1614.11
com.apple.driver.AppleHSSPIHIDDriver	53
com.apple.driver.AppleThunderboltDPInAdapter	5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily	5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.3
com.apple.driver.AppleHPM	3.1.3
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleHSSPISupport	53
com.apple.driver.AppleThunderboltNHI	4.7.3
com.apple.iokit.IOThunderboltFamily	6.7.9
com.apple.driver.AppleIntelLpssSpiController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	480.60.1
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	439.70.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice	404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily	404.30.2
com.apple.iokit.IOStorageFamily	2.1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	31
com.apple.iokit.IOTimeSyncFamily	680.15
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
}}}

Mac OSx is 10.13.6 (17G3025).",OracleSK
19581,Ubuntu 20.04 guest VirtualBoxVM 6.1.6 crash on macOS 10.14.6 host,Mac OS X,VirtualBox 6.1.6,2020-05-14T01:10:53Z,2020-05-14T01:10:53Z,2020-05-14T01:10:53Z,"I got a crash of an Ubuntu 20.04 guest VirtualBoxVM 6.1.6 running on macOS 10.14.6 host when trying to remove the guest additions image after a reboot after installing the 6.1.6 guest additions.

See attached log files",Lars Sonchocky-Helldorf
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,VirtualBox 6.1.6,2020-05-02T11:29:01Z,2020-05-02T11:29:01Z,2020-05-02T11:29:01Z,"Hi,

I've got three crashes of VirtualBoxVM in a row when trying to boot an Ubuntu 18.04 guest on a macOS 10.14.6 host. See attached crash logs and VBox.logs",Lars Sonchocky-Helldorf
19539,CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host),Mac OS X,VirtualBox 6.1.6,2020-04-28T18:18:55Z,2020-05-01T17:05:04Z,2020-05-01T17:05:04Z,"Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.",dmnorth
19540,CPU overcranks on Macbook Air i5 early 2020 after sleep (either guest OS or host),Mac OS X,VirtualBox 6.1.6,2020-04-28T18:19:02Z,2020-04-29T02:07:12Z,2020-04-29T02:07:12Z,"Debian and Ubuntu guests operate normally until after waking from sleep -- either suspending the guest while leaving the OS awake, or sleeping the host OS with the guest either awake or asleep. After waking from any of those states, the CPU maxes out to the thermal limit and stays there until the guest is halted, after which CPU behavior reverts to normal and temperatures stabilize at normal levels (40-55 C depending on other operations). This happens even when all other applications are off. Since it includes both guest and host, this may be two separate problems. Occasionally it does not happen with guest suspend, but it is 100% with the host os sleep. This does not happen on my 2018 Mac Mini, so as far as I know it's specific to the new Macbook Air.",dmnorth
19381,Virtual box keeps crashin during startup of virtual OS,Mac OS X,VirtualBox 6.1.4,2020-03-05T10:47:23Z,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
19448,VBoxManager (CLI) startvm fails for aborted images,Mac OS X,VirtualBox 6.1.4,2020-03-30T17:18:45Z,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
19433,VM's Constantly going into Guru Mediation state,Mac OS X,VirtualBox 6.1.4,2020-03-26T14:41:08Z,2020-03-27T19:56:51Z,2020-03-27T19:56:51Z,"Im trying configure a Virtual environment for testing but whenever I start my vis up they all starts dropping into guru mediation state and im getting frustrated. I have a MacBook Pro running Catalina and the box versions is 6.14

",gazza2217
19418,Guest Additions: Debian 10 Auto resize display problem,Mac OS X,VirtualBox 6.0.18,2020-03-20T20:08:25Z,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
19379,Ubuntu 18.04 guest Vbox 6.1.4 crash on macOS 10.14.6 / MacBook Pro 15'' 2018 host,Mac OS X,VirtualBox 6.1.4,2020-03-04T22:28:35Z,2020-03-04T22:28:35Z,2020-03-04T22:28:35Z,I've got a crash of a Vbox 6.1.4 while rebooting an Ubuntu 18.04 guest after a system update. See attached log files,Lars Sonchocky-Helldorf
12038,bridged interface  one way VLAN traffic,Mac OS X,VirtualBox 4.2.16,2013-08-19T13:36:02Z,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
17844,shared folders not working correctly on Lubuntu 18.0.4 guest,Mac OS X,VirtualBox 5.2.12,2018-06-28T23:02:40Z,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
19140,MacOS / Random network disconnect (Host-only Adapter) - ARP: duplicate use of $IP detected,Mac OS X,VirtualBox 6.0.14,2019-12-09T14:43:26Z,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
19292,Critical Error: Guru Meditation,Mac OS X,VirtualBox 6.1.2,2020-02-05T23:37:45Z,2020-02-05T23:37:45Z,2020-02-05T23:37:45Z,"I set up an Ubuntu 18.04 guest on my Macbook Pro 2019 earlier today, and everything was going ok and I was able to use it. I set up port forwarding with VBoxManage modifyvm ""vmname"" --natpf1 ""ssh,tcp,127.0.0.1,3022,10.0.2.15,22"" and was able to ssh into my vm. I was also able to use VBoxHeadless successfully. I then opened the VirtualBox GUI, right clicked on my virtual machine name and opened settings, and changed the name of the guest slightly (there was an uppercase by mistake). I then checked to see if my port forwarding rule had been updated and it had. Upon trying to use VBoxHeadless to start the vm it produced a lot of errors in the command line, so I stopped it and tried to open it with the VirtualBox GUI. This was when I receive the Critical Error message and was directed here. I have attached the log file and png from the log folder as requested in the pop up box.",josh6
19221,"VBox ""crashes"" on restart",Mac OS X,VirtualBox 6.1.0,2020-01-13T22:22:15Z,2020-01-17T09:25:52Z,2020-01-17T09:25:52Z,"After a big Kali VM Update VBox crashed when restarting

{{{VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)}}}
(around line 1417 in the attached log file)

running on macOS High Sierra 10.13.6. VBox asked me to report the crash :-)

Restarting worked and the guest now runs.

VBox 6.1.0 seems to be pretty unstable. I had a handful of freezes the last two days (hadn't used it for some time). 
Especially when I resized the guest window
The image was previously an VMWare image which I converted to OVA and imported in VBox. The Graphics Controller was initially set to VBoxSVGA which lead to an Invalid Setting Detected warning (therefore I changed it)
",C.L
19214,VM is aborted on normal shutdown,Mac OS X,VirtualBox 6.1.0,2020-01-09T03:36:33Z,2020-01-09T03:36:33Z,2020-01-09T03:36:33Z,"VM is aborted on normal shutdown. The state changes to ""Powered Off"" and then to ""Aborted"".

Last few lines from VBox.log:

02:31:14.797187 E1000#0: TX frames up to 1514: 107844
02:31:14.797197 E1000#0: TX frames up to 2962: 682
02:31:14.797207 E1000#0: TX frames up to 4410: 0
02:31:14.797216 E1000#0: TX frames up to 5858: 0
02:31:14.797226 E1000#0: TX frames up to 7306: 0
02:31:14.797234 E1000#0: TX frames up to 8754: 0
02:31:14.797252 E1000#0: TX frames up to 16384: 0
02:31:14.797276 E1000#0: TX frames up to 32768: 0
02:31:14.797292 E1000#0: Larger TX frames    : 0
02:31:14.797302 E1000#0: Max TX Delay        : 0
02:31:14.799059 GIM: KVM: Resetting MSRs
02:31:14.804435 Changing the VM state from 'DESTROYING' to 'TERMINATED'
02:31:14.811282 Console: Machine state changed to 'PoweredOff'
02:31:14.812640 GUI: Request to close Runtime UI because VM is powered off already.
02:31:14.812665 GUI: Passing request to close Runtime UI from machine-logic to UI session. 
",crvi
14366,Cursor misscaled in HiDPI mode when using mouse integration,Mac OS X,VirtualBox 5.0.0,2015-08-02T01:50:42Z,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
19159,3 Crashes of VirtualBoxVM running Ubuntu 18.04 guest on macOS 10.14.6 host,Mac OS X,VirtualBox 6.1.0,2019-12-14T16:51:13Z,2019-12-14T16:51:13Z,2019-12-14T16:51:13Z,"I am running VirtualBox Version 6.1.0 r135406 (Qt5.6.3) on a macOS Mojave 10.14.6 host. Guest OS is Ubuntu 18.04.3 (that's what I installed) but ""uname -a"" says:

Linux Ubuntu-1804-VirtualBox 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I think this is the case because I have the 6.1 guest additions installed.",Lars Sonchocky-Helldorf
19089,Kernel Panic when running Ubuntu 18.04.03 inside VirtualBox 6.0.14 on macOS 10.14.6 host,Mac OS X,VirtualBox 6.0.14,2019-11-16T16:56:27Z,2019-12-14T15:31:10Z,2019-12-14T15:31:10Z,"While the installation of Ubuntu 18.04.03 went fine, a subsequent boot of this VM resulted in a kernel panic. See attached files.",Lars Sonchocky-Helldorf
18496,'vboxmanage guestcontrol run' stops working after several hours with Linux guests (on MacOS host),Mac OS X,VirtualBox 6.0.4,2019-03-15T00:37:50Z,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
19083,Virtualbox Crashes after waking from Sleep macOS High Sierra,Mac OS X,VirtualBox 6.0.14,2019-11-13T19:54:25Z,2019-11-14T01:17:15Z,2019-11-14T01:17:15Z,"I have an early 2011 15"" MacBook Pro running High Sierra 10.13.6. Virtualbox 6.0.14 is installed and used to run  an Ubuntu Desktop virtual machine.

When waking my computer from sleep, the virtual machine crashes within seconds. At the next occurrence, I'll attach crash report files. I suspect the issue is related to https://www.virtualbox.org/ticket/11425 https://www.virtualbox.org/ticket/11444 and maybe others.

The other tickets mention a change in networking being the cause of the crash. I.e., the computer sleeps on one network and wakes on another. I'll monitor for that and update with further findings. I'm at a university with four different networks and multiple gateway devices for each network. If networking is the cause of these crashes, it may be related to different gateway devices since each wifi network has multiple access points but the same network name.",www139
19050,VirtualBox 6.0 on macOS 10.14 crashes on suspend/resume,Mac OS X,VirtualBox 6.0.14,2019-10-26T17:25:02Z,2019-10-28T09:05:49Z,2019-10-28T09:05:49Z,"Host: Macbook Pro 2015 retina 13"", macOS 10.14.6, vbox 6.0.14
Guest: Ubuntu 18.04.3 server

When the macbook lid is closed and then reopened:
- the VM says it has ""unexpectedly quit""
- when I click on the VirtualBox icon, that has ""unexpectedly quit"" as well

Possibly related to #16486; however, I never had this problem with vbox 5.x.  It seems to happen every time now, although this is with a freshly-installed 18.04 guest so possibly the guest is different.

Since the laptop has a retina display, with vbox 6.0 I select View > Scaled Mode otherwise the console text is too small.  With vbox 5.x the console size was fine without adjustments.  I don't know if this is related.",bcandler
18935,VirtualBox Crash When Powering Off / Shutting Down Debian VM on macOS Catalina,Mac OS X,VirtualBox 6.0.12,2019-09-17T09:40:49Z,2019-10-10T04:48:45Z,2019-10-10T04:48:45Z,"When powering off and/or sending the shutdown signal to my Debian VM, VirtualBox crashes and leaves the VM in an 'Aborted' status. I have a Windows VM which I can shutdown/power off without any resulting VirtualBox application crash.

This is the stack trace thrown:
{{{
Process:               VirtualBoxVM [4041]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.12 (6.0.12)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [4019]
Responsible:           VirtualBox [4015]
User ID:               501

Date/Time:             2019-09-17 05:10:40.199 -0400
OS Version:            Mac OS X 10.15 (19A558d)
Report Version:        12
Anonymous UUID:        8CD22061-DD5E-08D6-5768-B3DD7D7C0AC5

Sleep/Wake UUID:       CD3BEF75-0E78-4B26-8AAB-FC908122A280

Time Awake Since Boot: 26000 seconds
Time Since Wake:       390 seconds

System Integrity Protection: enabled

Crashed Thread:        12  VMSVGA FIFO

Exception Type:        EXC_CRASH (SIGKILL)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    LIBSYSTEM, [0x2]

Application Specific Information:
assertion failure: ""((void *)0) == tsd->NSCurrentOpenGLContext"" -> %lld

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.framework.IOKit     	0x00007fff3a8eef34 io_connect_method + 383
3   com.apple.framework.IOKit     	0x00007fff3a8eed47 IOConnectCallMethod + 186
4   com.apple.framework.IOKit     	0x00007fff3a8ef629 IOConnectCallStructMethod + 35
5   com.apple.IOAccelerator       	0x00007fff5bda2d16 IOAccelGLContextClearDrawable + 50
6   libGPUSupportMercury.dylib    	0x00007fff5868f01e gldAttachDrawable + 1587
7   GLEngine                      	0x00007fff4272ce6c gliAttachDrawableWithOptions + 257
8   com.apple.opengl              	0x00007fff4270ed4d CGLClearDrawable + 116
9   com.apple.AppKit              	0x00007fff353a7f56 __32-[NSOpenGLContext clearDrawable]_block_invoke + 34
10  com.apple.AppKit              	0x00007fff34d2b726 NSPerformVisuallyAtomicChange + 132
11  com.apple.AppKit              	0x00007fff3505da9d -[NSOpenGLContext clearDrawable] + 65
12  VBoxSVGA3DObjC.dylib          	0x000000011d102821 0x11d0fe000 + 18465
13  libdispatch.dylib             	0x00007fff6ee924de _dispatch_client_callout + 8
14  libdispatch.dylib             	0x00007fff6ee9dbd3 _dispatch_main_queue_callback_4CF + 1105
15  com.apple.CoreFoundation      	0x00007fff37ac4540 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
16  com.apple.CoreFoundation      	0x00007fff37ac3c8a __CFRunLoopRun + 2370
17  com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
18  com.apple.HIToolbox           	0x00007fff36650f2d RunCurrentEventLoopInMode + 292
19  com.apple.HIToolbox           	0x00007fff36650c6d ReceiveNextEventCommon + 600
20  com.apple.HIToolbox           	0x00007fff366509f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
21  com.apple.AppKit              	0x00007fff34cfaee4 _DPSNextEvent + 990
22  com.apple.AppKit              	0x00007fff34cf9c50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
23  com.apple.AppKit              	0x00007fff34cf4395 -[NSApplication run] + 658
24  libqcocoa.dylib               	0x000000010c487eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
25  org.qt-project.QtCoreVBox     	0x00000001056d2791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
26  org.qt-project.QtCoreVBox     	0x00000001056d6b4a QCoreApplication::exec() + 346
27  VirtualBoxVM.dylib            	0x000000010539ef93 TrustedMain + 1315
28  org.virtualbox.app.VirtualBoxVM	0x0000000104ce4d36 0x104ce1000 + 15670
29  libdyld.dylib                 	0x00007fff6eee22a5 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 2:: nspr-1
0   libsystem_kernel.dylib        	0x00007fff6f0325f6 __select + 10
1   VBoxXPCOM.dylib               	0x0000000108e7c8b0 0x108df2000 + 567472
2   VBoxXPCOM.dylib               	0x0000000108e7e6e5 PR_Poll + 1061
3   VBoxXPCOMIPCC.dylib           	0x000000010db72e75 0x10db60000 + 77429
4   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 3:: nspr-2
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 4:: VBoxSVCWatcher
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dc7f221 0x10db85000 + 1024545
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 5:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81de7 PR_WaitCondVar + 231
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6571b 0x10db60000 + 22299
5   VBoxXPCOMIPCC.dylib           	0x000000010db653ed 0x10db60000 + 21485
6   VBoxXPCOMIPCC.dylib           	0x000000010db6a039 0x10db60000 + 41017
7   VBoxXPCOM.dylib               	0x0000000108e652fd 0x108df2000 + 471805
8   VBoxXPCOM.dylib               	0x0000000108e644fb 0x108df2000 + 468219
9   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
10  VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
11  org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 6:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 7:: TimerLR
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxRT.dylib                  	0x0000000104e6fb15 0x104d22000 + 1366805
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 8:: UIMainEventListeningThread
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8a3c RTSemEventWait + 364
3   VBoxC.dylib                   	0x000000010dbc6d90 0x10db85000 + 269712
4   VBoxC.dylib                   	0x000000010dbc7fcd 0x10db85000 + 274381
5   VBoxC.dylib                   	0x000000010dd599aa 0x10db85000 + 1919402
6   VBoxGlobal.dylib              	0x0000000106ab1842 CEventSource::GetEvent(CEventListener const&, int) + 162
7   VBoxGlobal.dylib              	0x00000001068d23b7 0x106820000 + 730039
8   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 9:: EMT-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec0974 SUPR3PageFreeEx + 292
4   VBoxVMM.dylib                 	0x0000000108b75df8 PGMR3PhysMMIOExDeregister + 488
5   VBoxVMM.dylib                 	0x0000000108b50aa0 0x108af9000 + 359072
6   VBoxVMM.dylib                 	0x0000000108ba438d 0x108af9000 + 701325
7   VBoxVMM.dylib                 	0x0000000108baa317 0x108af9000 + 725783
8   VBoxVMM.dylib                 	0x0000000108baa828 0x108af9000 + 727080
9   VBoxVMM.dylib                 	0x0000000108ba7623 0x108af9000 + 714275
10  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
11  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
12  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
13  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 10:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff6f02af76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b4dc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff37ac444b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff37ac39e7 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff37ac30c3 CFRunLoopRunSpecific + 499
5   com.apple.AppKit              	0x00007fff34d0251a _NSEventThread + 132
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 11:: PDMNsTx
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 Crashed:: VMSVGA FIFO
0   libsystem_kernel.dylib        	0x00007fff6f031f6e __terminate_with_payload + 10
1   libsystem_kernel.dylib        	0x00007fff6f04c4ba abort_with_payload_wrapper_internal + 119
2   libsystem_kernel.dylib        	0x00007fff6f04c4c5 abort_with_payload + 9
3   libsystem_c.dylib             	0x00007fff6efb8a07 _os_crash_fmt.cold.1 + 55
4   libsystem_c.dylib             	0x00007fff6ef4b876 _os_crash_fmt + 154
5   com.apple.AppKit              	0x00007fff34ebd994 __NSAppKitFinalizeThreadData + 663
6   libsystem_pthread.dylib       	0x00007fff6f0ec413 _pthread_tsd_cleanup + 551
7   libsystem_pthread.dylib       	0x00007fff6f0ef16f _pthread_exit + 70
8   libsystem_pthread.dylib       	0x00007fff6f0ec1cc pthread_exit + 27
9   VBoxRT.dylib                  	0x0000000104ebc14a 0x104d22000 + 1679690
10  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
11  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 13:: AioMgr0-N
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108c8a66b 0x108af9000 + 1644139
4   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
5   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
6   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 14:: Port0
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 15:: ATA-0
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 16:: ATA-1
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ec3e27 SUPSemEventWaitNoResume + 135
4   VBoxDD.dylib                  	0x0000000113cdc71a 0x113cb0000 + 182042
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 17:: INTNET-RECV
0   libsystem_kernel.dylib        	0x00007fff6f02b8ea __ioctl + 10
1   libsystem_kernel.dylib        	0x00007fff6f02b8d7 ioctl + 150
2   VBoxRT.dylib                  	0x0000000104ec6d5d 0x104d22000 + 1723741
3   VBoxRT.dylib                  	0x0000000104ebf878 SUPR3CallVMMR0Ex + 312
4   VBoxDD.dylib                  	0x0000000113d1ad28 0x113cb0000 + 437544
5   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
6   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
7   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
8   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 18:: INTNET-XMIT
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 19:: AMCP Logging Spool
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 20:
0   libsystem_kernel.dylib        	0x00007fff6f02afb2 semaphore_wait_trap + 10
1   com.apple.audio.caulk         	0x00007fff6b109ec6 caulk::mach::semaphore::wait() + 16
2   com.apple.audio.caulk         	0x00007fff6b105442 caulk::semaphore::timed_wait(double) + 106
3   com.apple.audio.caulk         	0x00007fff6b108a14 caulk::concurrent::details::worker_thread::run() + 30
4   com.apple.audio.caulk         	0x00007fff6b108b64 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45
5   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
6   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 21:: EhciFramer
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 22:: nspr-3
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxXPCOM.dylib               	0x0000000108e81dfe PR_WaitCondVar + 254
3   VBoxXPCOM.dylib               	0x0000000108e822ad PR_Wait + 61
4   VBoxXPCOMIPCC.dylib           	0x000000010db6b7b8 0x10db60000 + 47032
5   VBoxXPCOM.dylib               	0x0000000108e56209 0x108df2000 + 410121
6   VBoxXPCOM.dylib               	0x0000000108e83a96 0x108df2000 + 596630
7   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
8   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
9   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
10  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 23:: VUsbPeriodFrm
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb9601 0x104d22000 + 1668609
3   VBoxRT.dylib                  	0x0000000104eb9383 0x104d22000 + 1667971
4   VBoxVMM.dylib                 	0x0000000108b6615f PDMR3ThreadIAmSuspending + 79
5   VBoxVMM.dylib                 	0x0000000108b666f8 0x108af9000 + 448248
6   VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
7   VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 24:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 25:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 26:
0   libsystem_pthread.dylib       	0x00007fff6f0eb5b4 start_wqthread + 0

Thread 27:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 28:: UIThreadWorker
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   org.qt-project.QtCoreVBox     	0x000000010551a170 0x1054ef000 + 176496
3   org.qt-project.QtCoreVBox     	0x0000000105519fab 0x1054ef000 + 176043
4   org.qt-project.QtCoreVBox     	0x0000000105519e82 QWaitCondition::wait(QMutex*, unsigned long) + 162
5   VBoxGlobal.dylib              	0x00000001068fb029 UIThreadPool::dequeueTask(UIThreadWorker*) + 121
6   VBoxGlobal.dylib              	0x00000001068fb190 0x106820000 + 897424
7   org.qt-project.QtCoreVBox     	0x000000010551896b 0x1054ef000 + 170347
8   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
9   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 29:
0   libsystem_kernel.dylib        	0x00007fff6f02afca semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff6ee929eb _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff6ee92e12 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff6eea0645 _dispatch_worker_thread + 318
4   libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
5   libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 30:: VMPwrDwn
0   libsystem_kernel.dylib        	0x00007fff6f02e726 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff6f0ef082 _pthread_cond_wait + 701
2   VBoxRT.dylib                  	0x0000000104eb8aeb RTSemEventWait + 539
3   VBoxVMM.dylib                 	0x0000000108baa24e VMR3ReqWait + 110
4   VBoxVMM.dylib                 	0x0000000108baa1bf VMR3ReqQueue + 623
5   VBoxVMM.dylib                 	0x0000000108baa00f VMR3ReqQueue + 191
6   VBoxVMM.dylib                 	0x0000000108ba938c VMR3ReqCallVU + 380
7   VBoxVMM.dylib                 	0x0000000108ba91d2 0x108af9000 + 721362
8   VBoxVMM.dylib                 	0x0000000108ba3cc9 VMR3Destroy + 249
9   VBoxC.dylib                   	0x000000010dbf08c3 0x10db85000 + 440515
10  VBoxC.dylib                   	0x000000010dc17047 0x10db85000 + 598087
11  VBoxC.dylib                   	0x000000010dbd510c 0x10db85000 + 327948
12  VBoxRT.dylib                  	0x0000000104e0a6dc 0x104d22000 + 952028
13  VBoxRT.dylib                  	0x0000000104ebc132 0x104d22000 + 1679666
14  libsystem_pthread.dylib       	0x00007fff6f0eed76 _pthread_start + 125
15  libsystem_pthread.dylib       	0x00007fff6f0eb5d7 thread_start + 15

Thread 12 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000200  rcx: 0x0000700007a7eda8  rdx: 0x0000000000000000
  rdi: 0x0000000000000fc9  rsi: 0x0000000000000012  rbp: 0x0000700007a7edf0  rsp: 0x0000700007a7eda8
   r8: 0x0000000000000054   r9: 0x00007fea858919e0  r10: 0x0000700007a7ee60  r11: 0x0000000000000206
  r12: 0x0000000000000054  r13: 0x0000700007a7ee60  r14: 0x0000000000000002  r15: 0x0000000000000012
  rip: 0x00007fff6f031f6e  rfl: 0x0000000000000206  cr2: 0x00007fff6f0371dd
  
Logical CPU:     0
Error Code:      0x02000208
Trap Number:     133


Binary Images:
       0x104ce1000 -        0x104d02ff7 +org.virtualbox.app.VirtualBoxVM (6.0.12 - 6.0.12) <0ED710D1-15CE-3432-97C3-40B0DD778F9B> /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
       0x104d22000 -        0x105282347 +VBoxRT.dylib (0) <44B42923-83C4-366C-AE1F-813AE54FEE60> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
       0x105397000 -        0x105484ff7 +VirtualBoxVM.dylib (0) <2B18B9FF-A9BA-35AC-94F4-2EF406259714> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM.dylib
       0x1054dd000 -        0x1054e6ff7 +org.qt-project.QtMacExtrasVBox (5.6 - 5.6.3) <AC6F0DC8-BF41-3A20-B803-656B301B8CDF> /Applications/VirtualBox.app/Contents/Frameworks/QtMacExtrasVBox.framework/Versions/5/QtMacExtrasVBox
       0x1054ef000 -        0x105a16ff7 +org.qt-project.QtCoreVBox (5.6 - 5.6.3) <3A7A08E0-9422-393E-BD97-FD15E751434C> /Applications/VirtualBox.app/Contents/Frameworks/QtCoreVBox.framework/Versions/5/QtCoreVBox
       0x105acc000 -        0x105fa7ff7 +org.qt-project.QtGuiVBox (5.6 - 5.6.3) <80F8D761-23D7-381D-B8D5-1C0C130F7876> /Applications/VirtualBox.app/Contents/Frameworks/QtGuiVBox.framework/Versions/5/QtGuiVBox
       0x10609b000 -        0x1065a4fff +org.qt-project.QtWidgetsVBox (5.6 - 5.6.3) <5DFD063A-1901-39D3-90FB-138EFE7C6A9E> /Applications/VirtualBox.app/Contents/Frameworks/QtWidgetsVBox.framework/Versions/5/QtWidgetsVBox
       0x106707000 -        0x10673bfff +org.qt-project.QtPrintSupportVBox (5.6 - 5.6.3) <4C8D48EF-FC21-3BE7-895F-584399F0B308> /Applications/VirtualBox.app/Contents/Frameworks/QtPrintSupportVBox.framework/Versions/5/QtPrintSupportVBox
       0x10675f000 -        0x10679efff +org.qt-project.QtOpenGLVBox (5.6 - 5.6.3) <F75D0235-BFE7-3966-A3C4-CFEA758B9A71> /Applications/VirtualBox.app/Contents/Frameworks/QtOpenGLVBox.framework/Versions/5/QtOpenGLVBox
       0x1067c1000 -        0x106814fff +VBoxDDU.dylib (0) <5DCF996A-036C-3DF7-A65F-4FDA755B5DFA> /Applications/VirtualBox.app/Contents/MacOS/VBoxDDU.dylib
       0x106820000 -        0x108956fff +VBoxGlobal.dylib (0) <66B224F5-CBE3-3D76-9DB1-A9D430E041A5> /Applications/VirtualBox.app/Contents/MacOS/VBoxGlobal.dylib
       0x108af9000 -        0x108d7bfff +VBoxVMM.dylib (0) <1A356DAB-4305-30E8-84C1-579E86EEF107> /Applications/VirtualBox.app/Contents/MacOS/VBoxVMM.dylib
       0x108df2000 -        0x108ea3ff7 +VBoxXPCOM.dylib (0) <817EE585-D05F-373A-B68D-200A0C997CDF> /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOM.dylib
       0x10a4e5000 -        0x10a4e9ff7 +VDPluginCrypt.dylib (0) <1D1D34F1-0821-34FB-8998-9888E46D6C5A> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VDPluginCrypt.dylib
       0x10a52b000 -        0x10a5b991f  dyld (732.2) <BAB55B81-E18F-3129-BD61-CC42B9F21198> /usr/lib/dyld
       0x10c465000 -        0x10c5a4fff +libqcocoa.dylib (0) <FA226E50-20A3-3C6D-B04E-9262D65300BC> /Applications/VirtualBox.app/Contents/plugins/platforms/libqcocoa.dylib
       0x10db52000 -        0x10db55047  libobjc-trampolines.dylib (779) <81578FF6-5EE6-3FE5-B69F-31B977F45D58> /usr/lib/libobjc-trampolines.dylib
       0x10db60000 -        0x10db77fff +VBoxXPCOMIPCC.dylib (0) <3F5A7F5F-392A-3855-8091-EAD834051036> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxXPCOMIPCC.dylib
       0x10db85000 -        0x10df7dfff +VBoxC.dylib (0) <B1A67512-FDC8-38A5-84F2-D8AA9EB23C53> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxC.dylib
       0x10dfc2000 -        0x10dfc5ff7 +VBoxSVCM.dylib (0) <55D3234B-0B5B-3AED-AA2E-3F0528414687> /Applications/VirtualBox.app/Contents/MacOS/components/VBoxSVCM.dylib
       0x10e02f000 -        0x10e031ff7 +VBoxPuelMainVM.dylib (0) <CE286393-79E4-3E6E-8922-4A933C4397E5> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMainVM.dylib
       0x10e2ab000 -        0x10e2bcffb  com.apple.iokit.IOHIDLib (2.0.0 - 2.0.0) <70FBC258-44BF-3C42-A997-3D0EDF27BC59> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
       0x113171000 -        0x113194ff7 +VBoxHostWebcam.dylib (0) <17590F9F-9794-362E-8C62-578DC28C0EEC> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxHostWebcam.dylib
       0x113cb0000 -        0x113ffffff +VBoxDD.dylib (0) <94B8B3E4-5B8D-342A-9E6D-0CEDC6BBC4F5> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD.dylib
       0x114691000 -        0x1146e8ff7 +VBoxDD2.dylib (0) <8AE831BF-11EF-3DC0-B31E-BC1B6EFC13CF> /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2.dylib
       0x1146ee000 -        0x1146fffff +VBoxEhciR3.dylib (0) <8EBE5D51-1BB4-39F0-99FA-2D9FD22510DD> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxEhciR3.dylib
       0x114704000 -        0x11470fff7 +VBoxNvmeR3.dylib (0) <BE5FF50A-1122-3A61-8504-FC19E2E5F988> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxNvmeR3.dylib
       0x114713000 -        0x11471ffff +VBoxUsbCardReaderR3.dylib (0) <AD3E1939-B325-3A8D-A571-A3179BB0CD32> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbCardReaderR3.dylib
       0x114722000 -        0x11472eff7 +VBoxUsbWebcamR3.dylib (0) <4CC64783-6A10-3ED0-B5C9-B759CFFAE3EB> /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxUsbWebcamR3.dylib
       0x11d0bf000 -        0x11d0f2fff +VBoxSVGA3D.dylib (0) <C997472A-A9F8-3F84-B18F-9FDFEEBC2397> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3D.dylib
       0x11d0fe000 -        0x11d104fff +VBoxSVGA3DObjC.dylib (0) <94F57D1A-3216-3E5D-90C9-5C29EAE73BD1> /Applications/VirtualBox.app/Contents/MacOS/VBoxSVGA3DObjC.dylib
       0x14b5f0000 -        0x14b73dff7  com.apple.audio.units.Components (1.14 - 1.14) <0CAF1178-C08B-3A0D-BE03-6D1A376CD37F> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x7fff2b013000 -     0x7fff2b262ff8  com.apple.RawCamera.bundle (9.00.1 - 1200.22) <4E4BD2AA-ABAF-3CC3-B070-D877CA4EBEB9> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x7fff2e758000 -     0x7fff2ec5cff7  com.apple.driver.AppleIntelBDWGraphicsGLDriver (14.0.67 - 14.0.0) <5FF8F09F-EFE6-3D81-8FB8-4DF5843665EF> /System/Library/Extensions/AppleIntelBDWGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsGLDriver
    0x7fff2ec5d000 -     0x7fff2ed5dffd  com.apple.driver.AppleIntelBDWGraphicsMTLDriver (14.0.67 - 14.0.0) <C75B3FE7-984B-3842-A18F-F97778C22FE0> /System/Library/Extensions/AppleIntelBDWGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsMTLDriver
    0x7fff3343b000 -     0x7fff3343fffb  com.apple.agl (3.3.3 - AGL-3.3.3) <EEB8C1EE-479A-3DA6-93D0-B8117D289146> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x7fff33440000 -     0x7fff33698ffa  com.apple.avfoundation (2.0 - 1722.27.4.4) <2EFEF1B1-CDC8-38BA-BA29-0B467ED109D0> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
    0x7fff33699000 -     0x7fff33764ff8  com.apple.audio.AVFAudio (1.0 - ???) <D0AEA054-EC5B-3A92-B672-F9CA22E8EB23> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Frameworks/AVFAudio.framework/Versions/A/AVFAudio
    0x7fff33884000 -     0x7fff33884fff  com.apple.Accelerate (1.11 - Accelerate 1.11) <229BBA70-25E1-363C-9A46-B27BD69269F6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff33885000 -     0x7fff3389bff7  libCGInterfaces.dylib (524.2) <7F08322A-4AA0-3677-91CD-9D1588BDBE39> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
    0x7fff3389c000 -     0x7fff33f07fdf  com.apple.vImage (8.1 - 524.2) <45A48EA9-49AA-33A0-B830-AF754BD01009> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff33f08000 -     0x7fff34170fff  libBLAS.dylib (1303) <112B19CC-925A-3E28-8B32-2002D30A37FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff34171000 -     0x7fff34460fdf  libBNNS.dylib (144.11.2) <726C490D-8BDB-3488-9B5A-531F15E42259> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff34462000 -     0x7fff34807fff  libLAPACK.dylib (1303) <5C248B39-F233-3074-A3A5-AF8F436FBF87> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff34808000 -     0x7fff3481dff8  libLinearAlgebra.dylib (1303) <C21931B4-F6BD-324D-A2D9-F13EE8AFB29E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff3481e000 -     0x7fff34823ff3  libQuadrature.dylib (7) <826897ED-B7AD-33DC-B9CB-F9787784F312> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff34824000 -     0x7fff34894fff  libSparse.dylib (103) <55467C29-2096-36AB-8A6D-5231A342809D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff34895000 -     0x7fff348a7fef  libSparseBLAS.dylib (1303) <3244FCAF-A1FE-3248-AF22-BFB3E9D12555> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff348a8000 -     0x7fff34a81ffb  libvDSP.dylib (735) <EE2CBD92-EA9A-3288-B9B4-D61AA08F1114> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff34a82000 -     0x7fff34b3dfd3  libvMisc.dylib (735) <3859618E-D36E-3190-8BC8-7AF170C7A6C8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff34b3e000 -     0x7fff34b3efff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <79C1A1C7-E97A-3B7A-8737-444B402A7AA0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff34b3f000 -     0x7fff34b9dffe  com.apple.Accounts (113 - 113) <57677F31-13F3-3197-B97A-DE57BD03BFC8> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
    0x7fff34ce3000 -     0x7fff35a8eff4  com.apple.AppKit (6.9 - 1877) <9E8E14EA-7B3B-3412-A5C5-B7DC97D5FAD2> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff35ade000 -     0x7fff35adefff  com.apple.ApplicationServices (48 - 50) <981D6A76-AA72-3203-98F5-4989FF2F6058> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff35adf000 -     0x7fff35b4afff  com.apple.ApplicationServices.ATS (377 - 492) <B5739AFF-FF49-3EF7-B123-922300E3E5BE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff35be3000 -     0x7fff35c21ffa  libFontRegistry.dylib (273) <9E8A133C-1DE1-3902-A513-2D474A95CDF0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff35c7c000 -     0x7fff35cabff7  com.apple.ATSUI (1.0 - 1) <9391C527-15CE-3108-8922-CF0C2A50C082> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
    0x7fff35cac000 -     0x7fff35cb0ff3  com.apple.ColorSyncLegacy (4.13.0 - 1) <EBA4F56C-3C82-3788-A168-3E77E116724B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff35d4b000 -     0x7fff35da1ff2  com.apple.HIServices (1.22 - 671) <E744DE5F-F775-3BFA-BBCB-4D38ADFCAA2A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff35da2000 -     0x7fff35db0fff  com.apple.LangAnalysis (1.7.0 - 1.7.0) <02AE4AE3-1CD9-3193-B5F3-2C1C6D435F18> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff35db1000 -     0x7fff35df6ff2  com.apple.print.framework.PrintCore (15 - 516) <43213BE5-C5E1-3AA8-8AFD-949AFF9FB2C5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff35df7000 -     0x7fff35e01fff  com.apple.QD (4.0 - 413) <EFC01D3C-9012-3FCF-9149-457F530A43F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff35e02000 -     0x7fff35e0fff0  com.apple.speech.synthesis.framework (9.0.20 - 9.0.20) <A5CCADE3-B307-3FAD-A7E8-A77DDFF026CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff35e10000 -     0x7fff35eddff2  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <1961714B-4533-3C6E-836C-1C73511EF4D3> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff35edf000 -     0x7fff35edffff  com.apple.audio.units.AudioUnit (1.14 - 1.14) <4CD694DA-A074-3BC0-BB50-724D16345F18> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff36255000 -     0x7fff365cbffe  com.apple.CFNetwork (1110 - 1110) <EC97BFD7-8745-30F4-9DB4-FD8281C84CC9> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff36641000 -     0x7fff36641fff  com.apple.Carbon (160 - 162) <09CEF7B7-0113-32C3-A3DF-4177A1CFD97C> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff36642000 -     0x7fff36645ffb  com.apple.CommonPanels (1.2.6 - 101) <930A9DD4-B4BF-3D73-8B81-2D46018BB2E4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff36646000 -     0x7fff3693affc  com.apple.HIToolbox (2.1.1 - 987.1) <2AD583EF-7EB9-3EFB-BA74-D230BE62F0CC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff3693b000 -     0x7fff3693eff3  com.apple.help (1.3.8 - 68) <CA52ABA0-636A-39AA-98C0-A1B901A5F4F4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff3693f000 -     0x7fff36944ff7  com.apple.ImageCapture (9.0 - 1600.1) <D4515843-F958-3910-A738-576FD43D3C78> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff36945000 -     0x7fff36945fff  com.apple.ink.framework (10.15 - 227) <BA11FA6C-AEAA-3688-8812-9CA16EA11D03> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff36946000 -     0x7fff36960ff2  com.apple.openscripting (1.7 - 185) <7CFD4E50-FD41-39C7-BA76-6BA260BD91F9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff36981000 -     0x7fff36981fff  com.apple.print.framework.Print (15 - 271) <CB0E6F07-19E3-3207-9B7B-267F04DF6F73> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff36982000 -     0x7fff36984ff7  com.apple.securityhi (9.0 - 55008) <E8AE6A05-5F07-3300-9FEA-8C29C0B45566> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff36985000 -     0x7fff3698bff7  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <819268CF-2A9D-3321-A826-535CB1F1E694> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff36b25000 -     0x7fff36b25fff  com.apple.Cocoa (6.11 - 23) <F8489AB5-835B-3637-B8A1-64FCF8AB5F7A> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff36b33000 -     0x7fff36d1eff7  com.apple.ColorSync (4.13.0 - 3394.1.4.1) <32A1AEE9-C3AA-3535-9C72-D89955D2DE85> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff3700a000 -     0x7fff37519ffa  com.apple.audio.CoreAudio (5.0 - 5.0) <7A785340-4CE5-3130-94AB-DFA51C69A4E7> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff3756c000 -     0x7fff375a3ff2  com.apple.CoreBluetooth (1.0 - 1) <6767CD70-533B-3114-9F9E-733B9E72C828> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff375a4000 -     0x7fff3797efe8  com.apple.CoreData (120 - 969.2) <BFA70A01-DC83-3A1A-A7DE-8DFEB4269304> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff3797f000 -     0x7fff37a88ffe  com.apple.CoreDisplay (1.0 - 107) <91C74B12-4357-3717-B00B-A21DD0C722CE> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff37a89000 -     0x7fff37f08fff  com.apple.CoreFoundation (6.9 - 1671.12) <6500A498-7434-3C1C-A9EB-1FDB75CB2CC1> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff37f0a000 -     0x7fff38582ff0  com.apple.CoreGraphics (2.0 - 1348.4.4.3) <E16AE614-C7B6-3DC4-904D-B130C7B9CF72> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff38590000 -     0x7fff388ebffe  com.apple.CoreImage (15.0.0 - 900.4) <63DB7953-3DD0-3CA2-9709-68A9A09837B0> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff38caa000 -     0x7fff38e1aff4  com.apple.CoreMedia (1.0 - 2501.27.4.3) <056F96CA-82E5-3DD0-97D8-A700F12D16BB> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff38e1b000 -     0x7fff38e7cff6  com.apple.CoreMediaIO (1000.0 - 5125.1) <70E47B45-B017-3893-97E4-E72729A4F936> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
    0x7fff38f03000 -     0x7fff38f03fff  com.apple.CoreServices (1068.2 - 1068.2) <46CA4F06-5983-3D08-B972-1382381CDAC1> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff38f04000 -     0x7fff38f87ff7  com.apple.AE (836 - 836) <E65EB197-5D66-3EBC-BCA0-A9D8B4F6EC2B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff38f88000 -     0x7fff39269fff  com.apple.CoreServices.CarbonCore (1216 - 1216) <FCE3A1CF-EE79-3FF7-A12F-8AFF74607E8A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff3926a000 -     0x7fff392b7ff1  com.apple.DictionaryServices (1.2 - 321) <648A5391-99DC-3AD1-B68A-9EB26AED62C1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff392b8000 -     0x7fff392c0ff7  com.apple.CoreServices.FSEvents (1268.0.6 - 1268.0.6) <78D2AB1A-9053-3D32-8C18-C1DD31FF9400> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff392c1000 -     0x7fff394f8ffd  com.apple.LaunchServices (1068.2 - 1068.2) <DCB37CF3-15A4-3A97-94B9-7EC6788BAEB7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff394f9000 -     0x7fff39591ff9  com.apple.Metadata (10.7.0 - 2064.1) <A8603546-69B1-39C4-B4D5-83F2E21013D9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff39592000 -     0x7fff395bfff7  com.apple.CoreServices.OSServices (1068.2 - 1068.2) <CB16982C-826A-3444-BCDB-754E48EFEA6E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff395c0000 -     0x7fff39627fff  com.apple.SearchKit (1.4.1 - 1.4.1) <0068BD72-CF2B-34E4-B461-002D5E56C31C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff39628000 -     0x7fff3964cffd  com.apple.coreservices.SharedFileList (130 - 130) <F55A2C27-F648-3608-8B71-43E8EC225F2E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff39972000 -     0x7fff39b25ff6  com.apple.CoreText (643.1 - 643.1) <02D49B30-84A8-32E0-9DD5-06E304B0D498> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff39b26000 -     0x7fff39b6afff  com.apple.CoreVideo (1.8 - 334.0) <54CC4AD8-7F5C-37D5-A26D-9C8C8A72BD41> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff39b6b000 -     0x7fff39bf8ff1  com.apple.framework.CoreWLAN (13.0 - 1448) <2894EC6A-F29E-393F-9105-7436B83C2E57> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff39dc2000 -     0x7fff39dcdff7  com.apple.DirectoryService.Framework (10.15 - 220.11.1) <EADC285E-3166-3474-915B-F905F840D19E> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
    0x7fff39dce000 -     0x7fff39e79ff0  com.apple.DiscRecording (9.0.3 - 9030.4.5) <6F1FE0D6-907E-3309-A53E-B4B01F9355E5> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff39e9e000 -     0x7fff39ea4ff7  com.apple.DiskArbitration (2.7 - 2.7) <23104F29-F120-354B-97BE-4514A675BB14> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff3a097000 -     0x7fff3a1b9ff3  com.apple.FileProvider (252 - 252) <FEF218FA-EAEA-32C5-82DB-5B3843FB7446> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider
    0x7fff3a1d1000 -     0x7fff3a598ff3  com.apple.Foundation (6.9 - 1671.12) <D1CCD387-08E0-338D-B93D-C3BA470CE727> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff3a605000 -     0x7fff3a634ff3  com.apple.GSS (4.0 - 2.0) <9520F096-C643-36D7-B8CB-3922B6E6D7EC> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff3a76a000 -     0x7fff3a882ffd  com.apple.Bluetooth (7.0.0 - 7.0.0f4) <D130CB4B-1350-3278-8D3F-A11114A996DC> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff3a8e6000 -     0x7fff3a989ff3  com.apple.framework.IOKit (2.0.2 - 1726.0.14) <E23D2220-479C-3DCC-8CF5-A9A6B497ECE4> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff3a98b000 -     0x7fff3a99bff4  com.apple.IOSurface (269.6 - 269.6) <1E49AD7D-6067-3599-B015-765047D58C13> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff3aa0e000 -     0x7fff3ab69fee  com.apple.ImageIO.framework (3.3.0 - 1972.3.4.2) <9770B095-F95D-328B-A1DE-6978C434ABA0> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff3ab6a000 -     0x7fff3ab6dfff  libGIF.dylib (1972.3.4.2) <F89D4FB5-AFA1-3617-B740-D148B5D635A1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff3ab6e000 -     0x7fff3ac28fe7  libJP2.dylib (1972.3.4.2) <33CC7F2A-1E5A-3302-8A96-0C8EA38E5F90> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff3ac29000 -     0x7fff3ac4dfef  libJPEG.dylib (1972.3.4.2) <FA7B791A-9F06-30B7-917F-94E022A2AE20> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff3aecb000 -     0x7fff3aee5fe7  libPng.dylib (1972.3.4.2) <576BD7D2-FCBF-31AB-BCB3-8935AD9CAD2C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff3aee6000 -     0x7fff3aee7fff  libRadiance.dylib (1972.3.4.2) <06F8438E-10A6-3D6D-BC00-AB49CD5CE602> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff3aee8000 -     0x7fff3af31fef  libTIFF.dylib (1972.3.4.2) <5535A3DB-501F-36B0-830E-108684CFA4DA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff3c34a000 -     0x7fff3c35cff3  com.apple.Kerberos (3.0 - 1) <91DF5D16-E721-39F0-A77B-87DA6032F870> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff3c35d000 -     0x7fff3c35dfff  libHeimdalProxy.dylib (77) <51DB9CFB-808F-32E8-BB34-39F6702DBDED> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
    0x7fff3c35e000 -     0x7fff3c394fff  com.apple.LDAPFramework (2.4.28 - 194.5) <32FAF82F-BA91-366A-83A3-CDFF6CDD1AF9> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff3c6ee000 -     0x7fff3c6f8fff  com.apple.MediaAccessibility (1.0 - 125) <DAF5DD8F-A725-320E-8D7E-2C39CBE33F44> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
    0x7fff3c7c1000 -     0x7fff3d287ffb  com.apple.MediaToolbox (1.0 - 2501.27.4.3) <1BA60E69-C647-3073-850A-BDC3DAD01BC8> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
    0x7fff3d289000 -     0x7fff3d34bff1  com.apple.Metal (211.53 - 211.53) <EA59DEFD-F6DD-3DC5-9E6F-8152CD5F121C> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff3d368000 -     0x7fff3d3a4ff3  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <54EC6486-7A3E-39D3-B213-EFCC4110E511> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff3d3a5000 -     0x7fff3d42bfe6  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <144A9994-9AD3-340D-A890-C7F10DDEF489> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff3d42c000 -     0x7fff3d451ff0  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <6F07D520-B36C-38D5-810B-A95BA5F79B04> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff3d452000 -     0x7fff3d467ffc  com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <73DBE1D5-89C4-3410-95DA-A384BF9C2C1E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
    0x7fff3d468000 -     0x7fff3d5c7ff4  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <24338B34-481D-3564-917C-CD1DB243FD12> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff3d5c8000 -     0x7fff3d616ff7  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <75ABA9EB-752E-3E7E-BFBA-19806FB65924> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff3d617000 -     0x7fff3d618ff5  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <5EA47648-76E9-37CD-A2FC-A0083A769665> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff3e55e000 -     0x7fff3e56affe  com.apple.NetFS (6.0 - 4.0) <10ECF7E4-98A5-3751-B7AC-0AAAF0050777> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff3e56b000 -     0x7fff3e6aeff6  com.apple.Network (1.0 - 1) <5C29B0D5-3811-32A8-9FF4-CA112F9526F4> /System/Library/Frameworks/Network.framework/Versions/A/Network
    0x7fff410cc000 -     0x7fff410d4fff  libcldcpuengine.dylib (2.12.7) <A9ECDF96-4888-35CB-9BEF-96D8A84E5106> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
    0x7fff410d5000 -     0x7fff4112dff7  com.apple.opencl (3.5 - 3.5) <0F4232DF-854F-3852-8881-D48FF303D4D3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff4112e000 -     0x7fff4114afff  com.apple.CFOpenDirectory (10.15 - 220.11.1) <90901E88-47DC-3DDA-AF53-FD0A0B22078A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff4114b000 -     0x7fff41156fff  com.apple.OpenDirectory (10.15 - 220.11.1) <5AAE71B0-892A-3813-BDCF-C364B61D500B> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff41ab1000 -     0x7fff41ab3fff  libCVMSPluginSupport.dylib (17.10.22) <026644DF-3221-3AB0-8DA9-DA9B56A8B38D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff41ab4000 -     0x7fff41ab9fff  libCoreFSCache.dylib (176.7) <A10565BE-6728-3BCA-9A9A-095CC09A5F25> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff41aba000 -     0x7fff41abefff  libCoreVMClient.dylib (176.7) <DF6A2BF6-7775-3ED8-B425-772499BE2BB7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff41abf000 -     0x7fff41ac7ff7  libGFXShared.dylib (17.10.22) <2DBB6DC3-4027-3A0E-AEA7-809399CFFEFA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff41ac8000 -     0x7fff41ad2fff  libGL.dylib (17.10.22) <95746D0C-9347-37C0-88E2-6BA4A3584816> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff41ad3000 -     0x7fff41b08fff  libGLImage.dylib (17.10.22) <B8EE902C-6692-3E32-949B-C193AC944D31> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff41b09000 -     0x7fff41c9bff7  libGLProgrammability.dylib (17.10.22) <02CCAAE9-9B38-352C-A854-026D02ABB7E9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
    0x7fff41c9c000 -     0x7fff41cd8fff  libGLU.dylib (17.10.22) <43DADBAD-9F65-33CE-94DA-654F24817313> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff42708000 -     0x7fff42717ff7  com.apple.opengl (17.10.22 - 17.10.22) <C3E682E0-413B-3134-9107-C45B897E8CDA> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff42718000 -     0x7fff42891ff7  GLEngine (17.10.22) <B67C43C3-77C1-3233-98F5-A5062B14FE70> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine
    0x7fff42892000 -     0x7fff428bafff  GLRendererFloat (17.10.22) <DA488EF2-6318-3376-8616-26CE79640666> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
    0x7fff436c7000 -     0x7fff43944ff7  com.apple.QuartzCore (1.11 - 815.6.4.2) <0459F92C-5C1C-3B32-BCE8-9526AF5BC8D1> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff444cf000 -     0x7fff44812ff1  com.apple.security (7.0 - 59306.11.12) <54D99D96-7E50-3EEA-BCB3-7E73973B131C> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff44813000 -     0x7fff4489bff7  com.apple.securityfoundation (6.0 - 55236) <A1B5CC71-E988-3529-AA03-539C02340DAD> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff448ca000 -     0x7fff448ceff8  com.apple.xpc.ServiceManagement (1.0 - 1) <EF42F840-AF78-38A4-B6E1-FDF445CA3477> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff456bc000 -     0x7fff45726ff7  com.apple.SystemConfiguration (1.19 - 1.19) <C0C089C3-FC64-3107-B23E-4073E800C5D2> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff459a2000 -     0x7fff45d49ff1  com.apple.VideoToolbox (1.0 - 2501.27.4.3) <522DF280-7ADE-3467-B4EE-06B7ED84C1F2> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff494bf000 -     0x7fff49583ff7  com.apple.APFS (1412.11.4 - 1412.11.4) <B66C6042-E929-3A33-83A0-9199E132FE1E> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff49d3c000 -     0x7fff49d44ff6  com.apple.AccessibilityBundles (1.0 - 128) <242ACD03-D41C-38AA-AEB5-D0EC462C548E> /System/Library/PrivateFrameworks/AccessibilityBundles.framework/Versions/A/AccessibilityBundles
    0x7fff4a5b4000 -     0x7fff4a5b5ff1  com.apple.AggregateDictionary (1.0 - 1) <92777CAE-3C90-39A4-A8AE-0273A262F875> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff4a93f000 -     0x7fff4a95bff2  com.apple.AppContainer (4.0 - 448.0.3) <EFE68289-FFE6-3453-89AF-E637CD47A2D0> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
    0x7fff4a9af000 -     0x7fff4a9bdff7  com.apple.AppSandbox (4.0 - 448.0.3) <1E6E9594-4988-32EC-86C2-CDDA7DBB7E66> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
    0x7fff4ae3f000 -     0x7fff4ae63ff3  com.apple.framework.Apple80211 (13.0 - 1453) <C355D394-9489-3C14-856C-A4818B003FE1> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff4af97000 -     0x7fff4afa6fdf  com.apple.AppleFSCompression (119 - 1.0) <725908C4-7585-3AB6-8A1A-691B8A9074B8> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff4b0a5000 -     0x7fff4b0b0ff7  com.apple.AppleIDAuthSupport (1.0 - 1) <6BD125A5-9820-3176-AB79-8B612CCD6956> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
    0x7fff4b0f2000 -     0x7fff4b13afff  com.apple.AppleJPEG (1.0 - 1) <8051B4A3-7658-3003-82D1-41CA5C83CBEC> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff4b50e000 -     0x7fff4b512ff7  com.apple.AppleSRP (5.0 - 1) <B251E119-3F06-3CDB-9559-8CC8BBAF1529> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
    0x7fff4b513000 -     0x7fff4b535ffb  com.apple.applesauce (1.0 - 16.22) <88BFDA72-8D13-3481-B4FA-62215F6E2E43> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff4b5f5000 -     0x7fff4b5f8fff  com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <AF8A3953-4D1A-38C2-B38D-1E21F326B0C7> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
    0x7fff4b5f9000 -     0x7fff4b649ff7  com.apple.AppleVAFramework (6.1.2 - 6.1.2) <282CA618-1F44-3160-9078-B48D70AEDE36> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff4b692000 -     0x7fff4b6a1ffd  com.apple.AssertionServices (1.0 - 223.11.1) <8A45663E-E9C8-3611-BD4C-710700920F14> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff4bbd3000 -     0x7fff4bfd1ff4  com.apple.audio.AudioResourceArbitration (1.0 - 1) <2639564C-1435-3DA2-A0CB-F288617219BC> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration
    0x7fff4c110000 -     0x7fff4c161ffd  com.apple.audio.AudioSession (1.0 - 17) <627167E8-D05D-3851-A5E5-FBA38C8E72D3> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
    0x7fff4c162000 -     0x7fff4c18fff7  libSessionUtility.dylib (17) <28EC4408-4F7C-3C73-A9E2-AD976BE1C1D4> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
    0x7fff4c228000 -     0x7fff4c45dff7  com.apple.audio.AudioToolboxCore (1.0 - 1104.14) <4591B856-C8D0-3FFD-B783-70707D18E91A> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
    0x7fff4c45e000 -     0x7fff4c576ff8  com.apple.AuthKit (1.0 - 1) <2650CED9-1F9F-3C76-A6B9-B0589F986830> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
    0x7fff4c72c000 -     0x7fff4c735ff3  com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <42FAB6B3-D02C-3264-9066-2B81DC62A529> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff4c736000 -     0x7fff4c7d7ff8  com.apple.backup.framework (1.11 - 1296.1) <B6B83178-3F01-3DCB-BC72-70F8F6BCFAD8> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff4c7d8000 -     0x7fff4c857fff  com.apple.BaseBoard (460 - 460) <E2B2C09D-7CA3-3BCF-AE84-E636CBC139CB> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff4c957000 -     0x7fff4c993ff7  com.apple.bom (14.0 - 219) <1AFE57DF-F512-39A7-9C53-1AF0490D38BB> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff4d4fe000 -     0x7fff4d54dfff  com.apple.ChunkingLibrary (302 - 302) <157DF88D-CCA1-3431-AB8F-E8B7A62D652C> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff4e3d2000 -     0x7fff4e3dbff7  com.apple.CommonAuth (4.0 - 2.0) <BDE39131-6389-3243-9C4A-DBA165B8A2F9> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff4e3ef000 -     0x7fff4e406ff1  com.apple.commonutilities (8.0 - 900) <A64C20B3-6860-3CCA-BB89-E8B9B589282A> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
    0x7fff4eae5000 -     0x7fff4eebafc8  com.apple.CoreAUC (280.0.0 - 280.0.0) <4D5184AB-F60A-3C95-82C1-A283FB15C072> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x7fff4eebb000 -     0x7fff4eee9ffb  com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B7C10F1C-B3DE-3F2C-B2B8-1CD37DA7298F> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
    0x7fff4ef0b000 -     0x7fff4ef2aff4  com.apple.analyticsd (1.0 - 1) <A712828F-84FB-302B-BAA8-D2776AB623EB> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
    0x7fff4f1f2000 -     0x7fff4f1fdff7  com.apple.frameworks.CoreDaemon (1.3 - 1.3) <76AC1239-46B1-387E-B053-ED56BDF55DE7> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
    0x7fff4f473000 -     0x7fff4f483ff3  com.apple.CoreEmoji (1.0 - 100) <9AB89183-635C-3859-9DC6-7BCE3A94D15E> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff4facf000 -     0x7fff4fb39ff8  com.apple.CoreNLP (1.0 - 211) <8F08AEF6-A380-3811-BAF0-D80E7C84B5AD> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
    0x7fff4ff9f000 -     0x7fff4ffa7ff8  com.apple.CorePhoneNumbers (1.0 - 1) <0C242322-DB33-3764-9B44-74FA00AA3702> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
    0x7fff506f1000 -     0x7fff50714fff  com.apple.CoreSVG (1.0 - 129) <1716AD1F-A94F-309D-9598-C7B65F5965A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
    0x7fff50715000 -     0x7fff50748ff7  com.apple.CoreServicesInternal (446.1 - 446.1) <D5620418-A66F-300B-BE02-6254206C6B3E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff50749000 -     0x7fff50777ff7  com.apple.CSStore (1068.2 - 1068.2) <C8AEEE68-B040-39B9-9B52-6496497B19A8> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
    0x7fff50c72000 -     0x7fff50cf9fff  com.apple.CoreSymbolication (11.0 - 64509.98.1) <2E90AD17-CEAC-3AE8-A960-DA83D3F3A071> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff50d91000 -     0x7fff50ebdff4  com.apple.coreui (2.1 - 605) <74EF8323-1769-3BF8-A0F3-30A89E5B8454> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff50ebe000 -     0x7fff5105cffd  com.apple.CoreUtils (6.0 - 600.30) <60C366EC-D7C4-300A-B794-12D84952D6B6> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
    0x7fff51190000 -     0x7fff511a3ff1  com.apple.CrashReporterSupport (10.13 - 15010) <94F94549-D6F8-35A5-8FEE-026E079C3B2C> /System/Library/PrivateFrameworks/C",dfuentes
18829,spontaneously causes host to reboot,Mac OS X,VirtualBox 6.0.10,2019-08-11T14:39:22Z,2019-10-08T21:45:16Z,2019-10-08T21:45:16Z,"This has been an issue I've encountered since VB 6.0.8 and has continued through to VB 6.0.11.  
My host is an iMac running macOS 10.14.6, but issue started when it was on 10.14.5.
I run several linux guest VMs.  
Sometimes when I'm updating one or two, my iMac spontaneously reboots.  Sometimes when I'm booting a guest VM my iMac spontaneously reboots.  Sometimes when I'm shutting down a guest VM my iMac spontaneously reboots.

Here's the latest crash log from my iMac:

Anonymous UUID:       F3719D15-7DCA-7343-A61F-B939BEF8FF8D

Sun Aug 11 09:25:35 2019

*** Panic Report ***
panic(cpu 6 caller 0xffffff80120daadd): Kernel trap at 0xffffffa426926f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007f89184a6000, CR3: 0x00000005a79581a0, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0x00007f88f8423d44, RCX: 0x0000000000000200, RDX: 0x00000000000004dd
RSP: 0xffffffa3e8581c60, RBP: 0xffffffa3e8581d00, RSI: 0x00007f88f83f0000, RDI: 0x00007f89184a6000
R8:  0x00007f88f8423d18, R9:  0x00007f88f8423d78, R10: 0x0000000000000000, R11: 0x00007f88f8423d42
R12: 0x00007f88f8423d40, R13: 0x0000000000023c00, R14: 0x00007f88f8423d38, R15: 0x00007f88f8423d18
RFL: 0x0000000000050246, RIP: 0xffffffa426926f56, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007f89184a6000, Error code: 0x0000000000000002, Fault CPU: 0x6, PL: 1, VF: 5

Backtrace (CPU 6), Frame : Return Address
0xffffffa3e8581730 : 0xffffff8011fad6ed 
0xffffffa3e8581780 : 0xffffff80120e9185 
0xffffffa3e85817c0 : 0xffffff80120da8ba 
0xffffffa3e8581830 : 0xffffff8011f5ab40 
0xffffffa3e8581850 : 0xffffff8011fad107 
0xffffffa3e8581970 : 0xffffff8011facf53 
0xffffffa3e85819e0 : 0xffffff80120daadd 
0xffffffa3e8581b50 : 0xffffff8011f5ab40 
0xffffffa3e8581b70 : 0xffffffa426926f56 
0xffffffa3e8581d00 : 0xffffffa426912735 
0xffffffa3e8581dc0 : 0xffffffa426859da9 
0xffffffa3e8581df0 : 0xffffffa42684ee55 
0xffffffa3e8581e30 : 0xffffffa426843f05 
0xffffffa3e8581fb0 : 0xffffffa42692e168 
0xffffffa3ea993860 : 0xffffffa42685b906 
0xffffffa3ea9939f0 : 0xffffff7f9578342f 
0xffffffa3ea993a00 : 0xffffff7f957961db 
0xffffffa3ea993ac0 : 0xffffff7f95795ac6 
0xffffffa3ea993b40 : 0xffffff801223a163 
0xffffffa3ea993b80 : 0xffffff801222e8df 
0xffffffa3ea993c00 : 0xffffff8012220544 
0xffffffa3ea993e00 : 0xffffff801249b68b 
0xffffffa3ea993e30 : 0xffffff80124f1839 
0xffffffa3ea993f40 : 0xffffff80125b92ad 
0xffffffa3ea993fa0 : 0xffffff8011f5b306 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(6.0.11)[09081CCC-AD27-3F66-A7FB-68A23B0D18F7]@0xffffff7f95781000->0xffffff7f95870fff

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
18G87

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
Kernel slide:     0x0000000011c00000
Kernel text base: 0xffffff8011e00000
__HIB  text base: 0xffffff8011d00000
System model name: iMac18,2 (Mac-77F17D7DA9285301)

System uptime in nanoseconds: 844208412176885
last loaded kext at 750269373847264: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
last unloaded kext at 750399941670990: com.apple.driver.AppleXsanScheme	3 (addr 0xffffff7f942a8000, size 32768)
loaded kexts:
com.goldenfrog.VyprVPNMalwareFilter	1
com.goldenfrog.SplitTunnel	1
org.virtualbox.kext.VBoxNetAdp	6.0.11
org.virtualbox.kext.VBoxNetFlt	6.0.11
net.sf.tuntaposx.tun	1
org.virtualbox.kext.VBoxUSB	6.0.11
net.sf.tuntaposx.tap	1
org.virtualbox.kext.VBoxDrv	6.0.11
com.promise.driver.stex	6.2.9
com.apple.filesystems.afpfs	11.1
com.apple.nke.asp-tcp	8.0.2
com.apple.filesystems.msdosfs	1.10
com.apple.driver.AppleTopCaseHIDEventDriver	138.4
com.apple.driver.AppleUpstreamUserClient	3.6.5
com.apple.kext.AMDFramebuffer	2.1.1
com.apple.kext.AMDRadeonX4000	2.1.1
com.apple.driver.AudioAUUC	1.70
com.apple.fileutil	20.036.15
com.apple.driver.AppleGraphicsDevicePolicy	3.50.12
com.apple.filesystems.autofs	3.0
com.apple.AGDCPluginDisplayMetrics	3.50.12
com.apple.driver.AppleHV	1
com.apple.iokit.IOUserEthernet	1.0.1
com.apple.iokit.IOBluetoothSerialManager	6.0.14d3
com.apple.driver.AGPM	110.25.11
com.apple.driver.ApplePlatformEnabler	2.7.0d0
com.apple.driver.X86PlatformShim	1.0.0
com.apple.driver.pmtelemetry	1
com.apple.driver.AppleIntelKBLGraphics	12.1.0
com.apple.Dont_Steal_Mac_OS_X	7.0.0
com.apple.driver.AppleHDA	282.54
com.apple.kext.AMD9500Controller	2.1.1
com.apple.driver.AppleThunderboltIP	3.1.2
com.apple.driver.AppleMCCSControl	1.5.9
com.apple.iokit.AppleBCM5701Ethernet	10.3.3
com.apple.iokit.BroadcomBluetooth20703USBTransport	6.0.14d3
com.apple.driver.eficheck	1
com.apple.driver.AppleIntelPCHPMC	2.0.1
com.apple.driver.AppleGFXHDA	100.1.414
com.apple.driver.AppleOSXWatchdog	1
com.apple.driver.AirPort.BrcmNIC	1400.1.1
com.apple.driver.AppleIntelKBLGraphicsFramebuffer	12.1.0
com.apple.driver.AppleSMCLMU	212
com.apple.driver.AppleIntelSlowAdaptiveClocking	4.0.0
com.apple.driver.AppleUSBODD	456.260.3
com.apple.iokit.SCSITaskUserClient	408.250.3
com.apple.driver.AppleUSBStorageCoexistentDriver	456.260.3
com.apple.driver.AppleVirtIO	2.1.3
com.apple.filesystems.hfs.kext	407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.filesystems.apfs	945.275.7
com.apple.driver.AppleSDXC	1.7.6
com.apple.driver.AppleAHCIPort	329.260.5
com.apple.private.KextAudit	1.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	201
com.apple.security.TMSafetyNet	8
com.apple.security.SecureRemotePassword	1.0
com.apple.driver.AppleHIDKeyboard	208
com.apple.driver.AppleActuatorDriver	2450.1
com.apple.driver.AppleMultitouchDriver	2450.1
com.apple.driver.AppleInputDeviceSupport	2440.2
com.apple.driver.AppleHSBluetoothDriver	138.4
com.apple.driver.IOBluetoothHIDDriver	6.0.14d3
com.apple.kext.AMDRadeonX4200HWLibs	1.0
com.apple.kext.AMDRadeonX4000HWServices	2.1.1
com.apple.iokit.IOUSBUserClient	900.4.2
com.apple.driver.AppleGraphicsControl	3.50.12
com.apple.kext.triggers	1.0
com.apple.iokit.IOAVBFamily	760.6
com.apple.plugin.IOgPTPPlugin	740.2
com.apple.iokit.IOSkywalkFamily	1
com.apple.driver.AppleSSE	1.0
com.apple.driver.DspFuncLib	282.54
com.apple.kext.OSvKernDSPLib	528
com.apple.AppleGPUWrangler	3.50.12
com.apple.driver.X86PlatformPlugin	1.0.0
com.apple.driver.AppleSMBusController	1.0.18d1
com.apple.driver.AppleHDAController	282.54
com.apple.iokit.IOHDAFamily	282.54
com.apple.iokit.IOEthernetAVBController	1.1.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerUSBTransport	6.0.14d3
com.apple.iokit.IOBluetoothHostControllerTransport	6.0.14d3
com.apple.iokit.IOBluetoothFamily	6.0.14d3
com.apple.driver.IOPlatformPluginFamily	6.0.0d8
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IONDRVSupport	530.51
com.apple.driver.AppleSMBusPCI	1.0.14d1
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.kext.AMDSupport	2.1.1
com.apple.AppleGraphicsDeviceControl	3.50.12
com.apple.iokit.IOAcceleratorFamily2	404.14
com.apple.iokit.IOSurface	255.6.1
com.apple.iokit.IOGraphicsFamily	530.66
com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice	408.250.3
com.apple.iokit.IOBDStorageFamily	1.8
com.apple.iokit.IODVDStorageFamily	1.8
com.apple.iokit.IOCDStorageFamily	1.8
com.apple.driver.usb.AppleUSBHub	1.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.iokit.IOUSBMassStorageClass	4.0.4
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.iokit.IOSerialFamily	11
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleThunderboltDPInAdapter	5.6.9
com.apple.driver.AppleThunderboltDPOutAdapter	5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily	5.6.9
com.apple.driver.AppleThunderboltPCIUpAdapter	2.1.5
com.apple.driver.AppleThunderboltPCIDownAdapter	2.1.5
com.apple.driver.AppleHPM	3.4.1
com.apple.driver.AppleIntelLpssI2CController	3.0.60
com.apple.driver.AppleIntelLpssDmac	3.0.60
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.iokit.IOAHCIFamily	288
com.apple.iokit.IONVMeFamily	2.1.0
com.apple.driver.AppleThunderboltNHI	4.7.9
com.apple.iokit.IOThunderboltFamily	6.8.6
com.apple.iokit.IOSCSIParallelFamily	3.0.0
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.2
com.apple.driver.AppleEFINVRAM	2.1
com.apple.driver.AppleEFIRuntime	2.1
com.apple.iokit.IOSMBusFamily	1.1
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.security.quarantine	3
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.driver.DiskImages	493.0.0
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	456.260.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice	408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily	408.250.3
com.apple.iokit.IOStorageFamily	2.1
com.apple.kext.CoreTrust	1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOTimeSyncFamily	740.2
com.apple.iokit.IONetworkingFamily	3.4
com.apple.iokit.IOReportFamily	47
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF
Model: iMac18,2, BootROM 175.0.0.0.0, 4 processors, Intel Core i7, 3.6 GHz, 32 GB, SMC 2.40f0
Graphics: kHW_AMDRadeonPro560Item, Radeon Pro 560, spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2400 MHz, 0x859B, 0x435431364734534644383234412E433136464844
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16E), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci105a,8760, RAID Controller, Thunderbolt@133,0,0
USB Device: USB 3.0 Bus
USB Device: Elements 25A2
USB Device: USB3.0 Hub
USB Device: Ultra Fit
USB Device: USB3.0 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB2.0 Hub
USB Device: HL-2040 series
USB Device: USB2.0 Hub
USB Device: EPSON Scanner
USB Device: Amazon Kindle
USB Device: E-USB Bridge for LS-120
USB Device: Apple USB SuperDrive
Thunderbolt Bus: iMac, Apple Inc., 41.1
Thunderbolt Device: Pegasus2-R, Promise Technology, Inc., 1, 19.2
",Jim Kelley
18823,Failed to create the VirtualBox object!,Mac OS X,VirtualBox 6.0.10,2019-08-09T15:59:24Z,2019-08-30T12:23:03Z,2019-08-30T12:23:03Z,"Version 6.0.10 r132072 (Qt5.6.3)

I created a test bed on VirtualBox of HA cluster. And I simulate hardware failures in loop. And with very rare probability (I got it on 424 iteration) I get VirtualBox error.


{{{
+ VBoxManage snapshot tuchanka0a restore install
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

}}}
",Olleg
18884,Failed to get a console object,Mac OS X,VirtualBox 6.0.10,2019-08-30T11:21:17Z,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
18862,The Guest window will flicker with the package virtualbox-guest-additions,Mac OS X,VirtualBox 6.0.10,2019-08-23T05:15:00Z,2019-08-23T05:43:46Z,2019-08-23T05:43:46Z,"Since version 28 of Fedora, the package comes with the distribution but with VirtualBox 6; when using Fedora 30 the package Guest Additions is having issues with the VBoxSVGA graphics card, as it start to wake up the guest window (it turns white and then goes back to normal), but if I use the VMSVGA controller it does not do it.  However the screen does not dinamically resizes, whereas with the VBoxSVGA it does it but then it fails.  I have had to remove the package and install the Guest Additions CD Image.

My OS: MacOS as Host. 
Guest: Fedora 30
Package: virtualbox-guest-additions",luispautt
18848,Virtual box crashes MacOS Mojave,Mac OS X,VirtualBox 6.0.10,2019-08-17T04:37:57Z,2019-08-19T07:01:38Z,2019-08-19T07:01:38Z,"MacOS crash when I start a vm on Virtual Box.

Mac 
  cpu is 2.4 GHz Intel Core i9.
  DDR4
  macOs Mojave  10.14.5

vm Guset OS
  CentOS-7-x86_64-DVD-1810
  installed as  DataServer

",iwweyl
15269,shift + scroll wheel inoperative,Mac OS X,VirtualBox 5.0.16,2016-03-23T20:58:40Z,2019-08-16T05:48:22Z,2019-08-16T05:48:22Z,"Mouse scroll wheel events do not get passed to the guest if Shift key is being held down. This only seems to happen when the host OS is OS X; same VM works as expected if hosted on a Linux host instead. Very inconvenient, as some applications use Shift-scroll to perform specific actions, e.g. horizontal scrolling of a window.

Misbehavior has been noted in multiple applications which use Shift-scroll to perform UI actions. Lack of mouse scroll events when Shift is held has also been verified via the xev tool.

Host is OS X 10.11.3 (El Capitan), guest is Debian 8 (Jessie) running KDE, with up-to-date patches and Guest Additions installed.",MikeUatCS
18741,VBoxManage see fixed size disk as dynamic,Mac OS X,VirtualBox 6.0.4,2019-07-03T05:27:11Z,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
18656,Cannot boot from .vmdk if 'Use Host I/O Cache' is disabled,Mac OS X,VirtualBox 6.0.8,2019-05-17T19:58:15Z,2019-05-28T14:25:40Z,2019-05-28T14:25:40Z,"Attempting to boot VM from a raw disk fails when 'Use Host I/O Cache' is disabled. When the option is enabled the VMboots normally.

The disk is formatted as GUID with an EFI partition, a macOS HFS+ partition and 2 Linux ext4 partitions (root and swap).
",granada29
18678,macOS app nap: effecting performance of VirtualBox VM,Mac OS X,VirtualBox 6.0.8,2019-05-27T15:50:13Z,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
18603,CentOS 7.6 guest in MacOS host receives spurious input when switching between desktop screens,Mac OS X,VirtualBox 6.0.6,2019-04-26T20:34:19Z,2019-05-17T19:01:07Z,2019-05-17T19:01:07Z,"Host: MacOS 10.13.6 High Sierra
Guest: CentOS 7.6, running KDE

When using the MacOS ""Spaces"" virtual desktop feature, you can use Ctrl-Left arrow/Ctrl-Right arrow to move between desktops. If you make CentOS full screen, then move between virtual desktops, when you switch to the full screen VM, when you first click in the VM it receives some kind of input that causes windows (particularly maximized windows) to come out of maximized state and move locations. Sometimes, a desktop right-click contextual menu to be activated.

After this happens, CentOS gets in a state where it interprets clicks in the wrong location. For example, clicking on a foreground window results in a window behind receiving the click. Clicking on a title bar lets you drag a window, but double clicking on it does not maximize it as expected. However, if you click on the maximize button, the window maximizes.

Another symptom which seems to be related is when the VM is in full screen, moving the mouse pointer down to the bottom to cause the MacOS dock to show itself causes a similar situation to switching desktops.",Glen Kawano
18630,Using dd to write to SD Card in a USB SD Card device results in an error,Mac OS X,VirtualBox 6.0.6,2019-05-08T21:50:53Z,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
6324,Bridging guest on mac os x host vlan cause reception of malformed packets on gest NIC,Mac OS X,VirtualBox 3.1.4,2010-03-04T16:04:59Z,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
18533,Fedora 29 Guest Additions Failure,Mac OS X,VirtualBox 6.0.4,2019-03-31T22:31:49Z,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
18527,Updated MacOS Mojave to 10.14.4 - VirtualBox Crashes,Mac OS X,VirtualBox 5.2.26,2019-03-27T14:27:08Z,2019-03-28T19:54:50Z,2019-03-28T19:54:50Z,"Using VirtualBox 5.2.26 and have extension pack installed.  There was a MacOS for Mojave this past week (10.14.4) and after installing VirtualBox opens but once I login it shows desktop for a brief second and goes back to the login screen.   The VirtualBox is running CentOS 7.

I am attaching the log file which contains a CFGM dump, CPUID dumps.   I don't see anything obvious in the log file ",dduck721
18262,Not enough video memory to restart gnome after loading from save state,Mac OS X,VirtualBox 6.0.0,2019-01-02T12:10:52Z,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
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,VirtualBox 6.0.0,2019-01-02T10:59:01Z,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
15405,Severe time drift with KVM paravirt and Linux guests,Mac OS X,VirtualBox 5.0.20,2016-05-11T09:32:49Z,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
18195,CentOS 7 boot hangs after installing Guest Additions,Mac OS X,VirtualBox 5.2.20,2018-12-18T14:02:58Z,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
18162,Linux guest cannot perform large USB requests,Mac OS X,VirtualBox 5.2.22,2018-12-01T19:30:17Z,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
18139,SIGINT (or Ctrl-C) on Mac Host not passed to Guest,Mac OS X,VirtualBox 5.2.22,2018-11-19T15:53:36Z,2018-11-29T23:59:14Z,2018-11-29T23:59:14Z,"When running a CentOS 7 guest on Max OS X (High Sierra & Mojave), any Ctrl-C command on the terminal is not captured and passed to the guest.

I ran into this issue originally via the terminal app when running the VirtualBox instance with Vagrant. However, i enabled the VBox Gui and then logged in directly. The Ctrl-C command is not being captured correctly and passed to the foreground process. 

You can see in the attached image the keyboard input as i tail a log file. The command should have terminated the tail, instead the key combination is displayed. ",BStopp
17886,VM self-terminates on MacOS,Mac OS X,VirtualBox 5.2.16,2018-07-24T00:59:32Z,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
18097,"Repeatable Kernel Panic OSX Host 10.13.6, 5.2.18/5.2.20",Mac OS X,VirtualBox 5.2.18,2018-11-02T15:13:04Z,2018-11-02T15:20:03Z,2018-11-02T15:20:03Z,"Hi there. I've been contributing to a forum topic about this here: https://forums.virtualbox.org/viewtopic.php?f=8&t=89890&sid=71ba74a8550785a1228b2d0ccdcefa74&p=432426#p432426

I have a Mac Mini (10.13.6, 16GB RAM) which is having regular kernel panics while running three Ubuntu VMs, particularly when under load. The three instances are Ubuntu 16.04 and serve as a three-node Graylog cluster (one master, two additional nodes). Perhaps complicating matters is that the .vdi's being written to are not on the local disk; rather they are saved to a Pegasus R2 RAID-5 array connected over (Apple standard) Thunderbolt cable. This allows them to be 2TB each with battery-backed writes, or believe me I'd be keeping them on the boot disk.

I've tried, to no avail:
* Moving to 5.2.20
* Wild ass guess that the repeated appearance of com.apple.msdosfs as a last-loaded/uloaded kernel extension was somehow the problem, boot into recovery to disable SIP and move aside that kext (when this didn't work, put it back in place again). 
* Altering the paravirtualization settings on the Ubuntu guests (Default, None, KVM) - currently sitting at the recommended KVM option
* Finally, added the ""keepsyms=1"" nvram parameter to at least get the backtrace symbolicated.

I'd be *beyond* happy to take any wild suggestions for additional logging to help diagnose this in any way. The full panic is attached, but this is the top relevant section I believe: 

{{{
Anonymous UUID:       8C247A86-017F-C949-405A-1CFF90AF12B3

Thu Nov  1 15:15:43 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff8006f8776f): Kernel trap at 0xffffff80072d36b0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000100000008, CR3: 0x00000003a8a860ea, CR4: 0x00000000001627e0
RAX: 0xffffff8025937610, RBX: 0x0000000100000000, RCX: 0x0000000009000000, RDX: 0xffffff80076a5128
RSP: 0xffffff91f69dbea0, RBP: 0xffffff91f69dbef0, RSI: 0x0000000000000002, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000000000000400, R10: 0x0000000000000061, R11: 0xffffff91f6b07770
R12: 0xffffff91f69dbea0, R13: 0x0000000000000000, R14: 0xffffff802b6025f0, R15: 0xffffff800782b8d0
RFL: 0x0000000000010206, RIP: 0xffffff80072d36b0, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000100000008, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff91f69db970 : 0xffffff8006e6c1c6 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffff91f69db9c0 : 0xffffff8006f95274 mach_kernel : _kdp_i386_trap + 0x114
0xffffff91f69dba00 : 0xffffff8006f87544 mach_kernel : _kernel_trap + 0x4e4
0xffffff91f69dba70 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dba90 : 0xffffff8006e6bc3c mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffff91f69dbbc0 : 0xffffff8006e6b9fc mach_kernel : _panic + 0x5c
0xffffff91f69dbc20 : 0xffffff8006f8776f mach_kernel : _kernel_trap + 0x70f
0xffffff91f69dbd90 : 0xffffff8006e1e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91f69dbdb0 : 0xffffff80072d36b0 mach_kernel : _audit_mac_free + 0xa0
0xffffff91f69dbef0 : 0xffffff80072c5a65 mach_kernel : _audit_free + 0x115
0xffffff91f69dbf10 : 0xffffff80072c6676 mach_kernel : _audit_syscall_exit + 0x46
0xffffff91f69dbf40 : 0xffffff8007403987 mach_kernel : _unix_syscall64 + 0x287
0xffffff91f69dbfa0 : 0xffffff8006e1e9c6 mach_kernel : _hndl_unix_scall64 + 0x16

BSD process name corresponding to current thread: VBoxHeadless
Boot args: -v keepsyms=1

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide:     0x0000000006c00000
Kernel text base: 0xffffff8006e00000
__HIB  text base: 0xffffff8006d00000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

System uptime in nanoseconds: 2300159388101
last loaded kext at 246145680169: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
last unloaded kext at 306907560558: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8a1c3000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.18
org.virtualbox.kext.VBoxNetFlt	5.2.18
org.virtualbox.kext.VBoxUSB	5.2.18
org.virtualbox.kext.VBoxDrv	5.2.18
com.promise.driver.stex	6.2.9
com.apple.iokit.SCSITaskUserClient	404.30.2
<SNIP>
}}}

Best regards, and much respect: VirtualBox is a wonderful technology.
./scc",Scott Corscadden
5595,Request: built in VDI disk-size optimization routine,Mac OS X,VirtualBox 3.0.12,2009-11-30T02:44:58Z,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
16084,ssl connection incorrectly reset when using NAT,Mac OS X,VirtualBox 5.0.28,2016-10-20T06:19:10Z,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
17889,"VBox 5.2.16: Microphone not working: macOS Host, Linux/Debian Guest",Mac OS X,VirtualBox 5.2.16,2018-07-24T18:05:35Z,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
17857,- Buscador,Mac OS X,VirtualBox 5.2.14,2018-07-05T15:43:32Z,2018-07-09T09:00:19Z,2018-07-09T09:00:19Z,"Hello!

We have 3 MacBook Pro's, all running High Sierra (10.13.5), all with the same error after opening a Buscador ISO 2-3 times. The first time it works fine, it seems to run into the boot error sometime later.

I saw an error in a few of the logs: vmmdev guest log bios cd rom boot failure code 0004

Not sure if this is a generic error, or something more telling. Any help would be appreciated, thanks!

",Kujo
17846,vboxmanage does not work with ubuntu 18.04,Mac OS X,VirtualBox 5.2.12,2018-07-01T20:26:04Z,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
16396,Guest Freeze: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [firefox:3744],Mac OS X,VirtualBox 5.1.12,2017-01-17T08:42:54Z,2018-06-22T15:31:03Z,2018-06-22T15:31:03Z,"I searched a lot for a similar problem and could not find one.
The problem occurs with both 5.1.12 or 5.0.30 and also earlier versions for a few months now.
I tried ubuntu 16.04 64bit VM and also Debian machine 32 bit with jessie and now stretch.
I recompiled the kernel, 4.8.15 same thing.
I am using docker to run the firefox so that is an important information.
The freeze occurs after a while using the firefox. I don't have an idea why it happens or in what situation. Sometimes it can run for a long time, sometimes not. It is sporadic.",Tzahi
17790,Screen resolution limited after Linux guest OS update,Mac OS X,VirtualBox 5.2.12,2018-05-30T18:18:13Z,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
16347,Full screen mode broken on MacOS hosts with Guest additions 5.1.4 and later,Mac OS X,VirtualBox 5.1.12,2017-01-02T11:11:17Z,2018-05-25T19:57:59Z,2018-05-25T19:57:59Z,"I am running VBOX on MacOS. I am tracking both MacOS versions (currently on macOS Sierra (10.12.2), and VirtualBox versions (currently on 5.1.12). I use all my VMs (Linux) in full screen mode

Last september I had upgraded VBOX to 5.1.4. I then upgraded the guest editions to 5.1.4 as well As a result, full screen mode stopped working: the VMs no longer occupied the whole screen, but only part of it. Luckily I was able to go back to the previous guest additions (5.0.20) and got full screen back to working as usual.

Today I upgraded VBOX to 5.1.12 and tried again upgrading the guest additions to 5.1.12. Same effect: full screen broken the same way (full screen no longer occupies the entire screen). Again, downgraded guest additions to 5.0.20.

What seems to happen is that the guest additions somehow no longer automatically match the resolution of the VM screen to the resolution of the host display (1280x800).

I also see differences in the View menu. 
With guest additions 5.0.20, the View menu is like this:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked.
- Scaled Mode (Host+L) is unchecked

With guest additions 5.1.4 and later:
- Full Screen Mode (Host+F) is checked
- Auto Resize Guest Display is checked but greyed out
- Scaled Mode (Host+L) is unchecked but greyed out


",agodfrin
17728,Can't mount shared folder from fstab,Mac OS X,VirtualBox 5.2.10,2018-05-03T19:36:50Z,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
15159,Need bzimage feature in iPXE build for network adapter boot ROM,Mac OS X,VirtualBox 5.0.14,2016-02-18T16:17:05Z,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
17661,iMac High Sierra - host kernel panic when adding load to guest,Mac OS X,VirtualBox 5.2.8,2018-04-03T09:50:43Z,2018-04-03T09:50:43Z,2018-04-03T09:50:43Z,"Steps to reproduce: Create a simple Virtualbox with vagrant:

{{{
Vagrant.configure(""2"") do |config|
  config.vm.box = ""bento/ubuntu-16.04""
  config.ssh.forward_agent = true
  config.vm.network :private_network, ip: ""192.168.91.21""
  config.vm.provider ""virtualbox"" do |v|
    v.name = ""maschinenring test""
    v.customize [""modifyvm"", :id, ""--memory"", ""4096""]
  end
end
}}}

ssh into it and install the stressapptest

{{{
sudo apt-get install stressapptest
}}}

Runn the stressapptest with

{{{
stressapptest -s 9000 -m 8 -C 8 -W --findfiles -i 2 -M 4500
}}}

Wait for one to two hours untill the host system rects with a cernel panic. I have also attached three panic reports. For me they it looks like the vm just create some random errors in the kernel memory space. I reproduced this bug on three iMacs. All software was up to date , the iMacs do not crash in normal usage or with load testing on the host system.

I haven't seen this happening before the upgrade from Sierra to High Sierra.

Softweare Versions:
* High Sierra version: 10.13.3 (17D102)
* Virtualbox: 5.2.8
* Vagrant: 2.0.3

As the test Version of Virtualbox on https://www.virtualbox.org/wiki/Testbuilds is linking to https://www.virtualbox.org/download/testcase/VirtualBox-5.2.9-121224-OSX.dmg and this gives me a 404 I was not able to test it with the latest Test version release.

It looks like this Problem is spcific to the iMac as I was not able to reproduce it on MacBooks.

Some data from my Host OS:
{{{
Hardware-Übersicht:

  Modellname:	iMac
  Modell-Identifizierung:	iMac14,2
  Prozessortyp:	Intel Core i5
  Prozessorgeschwindigkeit:	3,2 GHz
  Anzahl der Prozessoren:	1
  Gesamtanzahl der Kerne:	4
  L2-Cache (pro Kern):	256 KB
  L3-Cache:	6 MB
  Speicher:	16 GB
  Boot-ROM-Version:	IM142.0123.B00
  SMC-Version (System):	2.15f7
  Seriennummer (System):	DGKLQ07LF8J9
  Hardware-UUID:	4328169B-16AA-518C-B249-7CDD6179774A
}}}
",codekunst
17622,MacOS host Debian 9 guest hangs on big load,Mac OS X,VirtualBox 5.2.8,2018-03-14T19:54:59Z,2018-03-22T13:04:46Z,2018-03-22T13:04:46Z,"when I start the guest with vboxmanage --headless, I kick off a build script over ssh to the guest.  eventually, the guest will become unresponsive and use 100% of one cpu.  This does not happen in the dev build (5.2.97) but does happen in the test build (>=5.2.9).  This is not reproducible if I run the same script from a gui login session on the host.

VBox.log is from a run with 5.2.9 which ends with a heartbeat flatline, after which I power the machine off.  VBox.log.2 is from a run with 5.2.97 which finished successfully followed by a power down.",jkordani-lsa2
17552,Invalid SELinux context for /etc/ld.so.cache and/or restorecon,Mac OS X,VirtualBox 5.2.6,2018-02-19T16:53:54Z,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
17547,Facing NS_ERROR_FAILURE on starting all virtual machines,Mac OS X,VirtualBox 5.2.6,2018-02-18T07:16:57Z,2018-02-27T22:22:54Z,2018-02-27T22:22:54Z,"Failed to open a session for the virtual machine Ubuntu.

The virtual machine 'Ubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}



Host OS: 10.13.1 MacOS High Sierra

I couldn't find any related log file anywhere. Please help. This is blocking me. Tried reinstall multiple times

Also. tried all the solutions suggested on this thread https://www.virtualbox.org/ticket/16015

Nothing worked.

",Rakesh Sharma
17544,"VM not responsive after hibernation: Mac OS host, Ubuntu Linux Guest",Mac OS X,VirtualBox 5.2.6,2018-02-13T23:13:30Z,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
13874,"On host sleep/resume, guest becomes ""aborted""",Mac OS X,VirtualBox 4.3.22,2015-02-21T04:29:41Z,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
17519,Phantom Menu Bar in Host Network Manager on macOS High Sierra (Version 10.13.3),Mac OS X,VirtualBox 5.2.6,2018-02-01T21:20:16Z,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
17445,VirtualBox 5.2.4-119785 does not work on High Sierra 10.13.2,Mac OS X,VirtualBox 5.2.4,2018-01-10T14:13:04Z,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
17454,Critical error,Mac OS X,VirtualBox 5.1.30,2018-01-14T22:36:45Z,2018-01-15T19:04:02Z,2018-01-15T19:04:02Z,"On startup of Ubuntu 16.04 virtual machine:

""A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""

",dwhea
15927,USB Wifi Dongle drops connection after short period,Mac OS X,VirtualBox 5.1.6,2016-09-13T23:52:22Z,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
16741,"When installing Guest Additions from CD image, first uninstall packages shipped with client OS",Mac OS X,VirtualBox 5.1.22,2017-05-08T11:10:26Z,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
17180,Unable to get properly into full screen after VM resume,Mac OS X,VirtualBox 5.1.28,2017-10-19T18:47:51Z,2017-11-30T22:15:48Z,2017-11-30T22:15:48Z,"I recently noticed the following issue, after a recent update (version 5.1.28 r117968 (Qt5.6.2) under macOS):
after I resume a VM, it is unable to go to full screen; it also show two windows, one of which shows the state before resume and is frozen.

Steps:
- Run a VM (I had this happen with several Linux Guests)
- Have it work in full screen
- Save the machine
- Resume it; then the first anomaly occurs: two windows show the status of the VM; the first one is not full screen, and reacts to inputs; the other is full screen and does not react to inputs

After that it is sometimes possible to put back to full screen the window that started as non full screen, but the frozen full screen view never goes away.",Merrilin
17126,keyboard mouse not functional on host after dock(or unplug/plug mouse/kb),Mac OS X,VirtualBox 5.1.28,2017-09-30T06:08:18Z,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
4208,Command-Q not passed to client OS,Mac OS X,VirtualBox 2.2.4,2009-06-08T16:32:52Z,2017-09-30T06:44:01Z,2017-09-30T06:44:01Z,"
Certain key combinations are not being passed through to the client OS. 

Usecase: Command-Q (in X11 as Meta-Q) to quit an application in the client OS results in the  ""Close virtual machine"" dialog (and leads to a 'stuck' command key modifier after dismissal, until meta is pressed again).

Also see Command-H for another example of this problem

http://www.virtualbox.org/changeset/1320 describes a fix, but from what I can tell has either not been applied, or does not work.

Partially related to Ticket #1668, but currently the exhibited behaviour is inconsistent with the behaviour of other keyboard combinations (i.e. pass everything to the client) - 1668 describes how passing through these key combos, if _optional_, may still be useful to some.",Gil Pinheiro
16984,Can't enter encryption password  OSX 10.12.5,Mac OS X,VirtualBox 5.1.26,2017-08-06T11:53:17Z,2017-08-30T11:21:23Z,2017-08-30T11:21:23Z,"Hello,

Every machine that using a saved state + virtual encryption, can't be unlocked.  Either no password prompt shows up or the password prompt that appears does not allow any typing in it (can't be clicked).

Only solution for now is to discard the saved state and start up normally.

Another remark:  When pausing a VM, no password has to be entered to unlock/decrypt, ideally behaviour should be the same then we starting/starting from saved state.


",Neekoh
17042,"5.1.26, Mac OS X, VM aborts when external monitor/keyboard/mouse is unplugged",Mac OS X,VirtualBox 5.1.26,2017-08-28T19:21:43Z,2017-08-29T15:35:42Z,2017-08-29T15:35:42Z,"Hello, 

Setup: VirtualBox 5.1.26 on Mac OS X 10.11.6 (El Capitan), guest os is Linux Ubuntu 14.0.4 LTE. Dual monitor. Keyboard, mouse and external monitor are routed from the lightning connector on the mac through an El Gato Thunderbolt2 Dock box. Specifically, the setup looks like:

MAC (lightning connector) -> El Gato Dock (USB + video cables) -> Dell U3415W monitor (USB ports)-> Keyboard, Mouse 

I updated today to 5.1.26 from '24. On the previous version I used to be able to unplug the lightning connector to the dock box from the Mac,  and the VM window would just move to the builtin display and keep going, receiving input from the builtin keyboard and trackpad.

However, on the new version the VM aborts instantly and repeatably as soon as I unplug the connector. 
  ",khomeino
17039,OSX 10.12.6 VB 5.1.26 r117224 reproducible crash /w Kubuntu,Mac OS X,VirtualBox 5.1.26,2017-08-27T19:20:40Z,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
14898,VBox 5.0.10 Aborts Guest session on resume,Mac OS X,VirtualBox 5.0.10,2015-12-04T04:37:18Z,2017-08-23T16:15:41Z,2017-08-23T16:15:41Z,"May be similar to #13874 but that was resolved...
I am running VBox for over a year and never experienced this, until running v5.0.10. All of a sudden now my guest session (Ubuntu 12.04 LTS with kernel 3.2.0-95) aborts when my MacBook Pro awakens (OS Mavericks).
This has happened several times and while I cannot reproduce at will, it is quite frequent.",RobCIQ
16242,"MacOS Sierra host, CentOS 7 guest, VBoxClient clipboard breaks when copying rich text in guest",Mac OS X,VirtualBox 5.1.10,2016-11-28T21:03:18Z,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
17008,VBOX running RHEL aborting,Mac OS X,VirtualBox 5.1.26,2017-08-12T19:37:34Z,2017-08-14T19:17:59Z,2017-08-14T19:17:59Z,"I am running the following version of VBox:

'''VirtualBox VM 5.1.26 r117224 darwin.amd64 (Jul 27 2017 14:04:15) release log''

I am running RHEL guest from a Mac host. This has been working perfectly for almost 2 years now. However, recently I upgraded from a prior version (unfortunately I am not sure what the previous version was) to the current 5.1.26 version and ever since then I the guest OS aborts after a few hours of being up. I am not certain what is causing this, however, I do have a crash dump that I will attach from my Mac OS host.",Garfield-LzLabs
16754,VM config lost after saving state,Mac OS X,VirtualBox 5.1.22,2017-05-12T22:28:17Z,2017-06-12T23:32:35Z,2017-06-12T23:32:35Z,"I've had this issue happen several times recently. I click to save the state of a VM. It saves the state completely and the window closes. I then close out of VirtualBox (UI). 

The next time I open the Vbox UI, the VM looks normal. However, when I attempt to start the VM, I'm greeted with ""Fatal: no boot media"". It seems that the *.vbox file may have been saved incorrectly as a result of the previous shutdown. What I see in the UI is that the entire Storage area is blank (it's lost all of the hard drives, CD, etc). It also has reset the memory and possibly other settings. It's almost like it's overwritten the *.vbox file with a generic template. Or, perhaps a generic template is created because the original *.vbox file has gone missing... not sure which?

I have encountered this bug at least 3 times since 5.1.18. I am still seeing it in the latest version (5.1.22). So, whatever is causing this issue is not fixed. Two of the times, I could easily recreate the VMs. However in this latest one, I need to recover some information for reference.

As an FYI, the *.vdi hard drive files exist. In the snapshot director, I see the *.sav file and the various snapshot files. Unfortunately, trying to hand recreate the working *.vbox file for this VM the way that it was is probably next to impossible.

Note that this VM began its life as a linked clone from another VM. I have not modified the original from which it was cloned, so it shouldn't be related to that. However, for each of these I have encountered, they have all been from linked clones making recreating the *.vbox file more complicated.

It would be great if there were a repair tool included to scan the VM's directory and attempt to repair or recreate the *.vbox file using the files it can find. If such a tool already exists, please let me know. If there's an easy way to recreate this *.vbox file, that would be helpful.

As an FYI, I've also looked at the 'backup' *.vbox file and it also appears to be a generic template. So, I can't even recover from that.",commorancy0
16817,Debugging high CPU usage macOS,Mac OS X,VirtualBox 5.1.22,2017-06-06T15:00:56Z,2017-06-06T20:13:09Z,2017-06-06T20:13:09Z,"I'm using docksal to run a virtual box on macOS 10.12.4. When I view the activity monitor VBoxheadless is consumming 120-140% CPU. I've tried toggling a few things in the settings, but I'm out of my depth in terms of actually debugging the issue.",Claytron
16076,Ubuntu 16.04.1 VM slow after copying data to external USB drive (irq 20: nobody cared),Mac OS X,VirtualBox 5.1.6,2016-10-17T20:49:27Z,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
16742,can connect to virtual usb3 port. can not connect to virtual usb2 port.,Mac OS X,VirtualBox 5.1.22,2017-05-08T12:08:28Z,2017-05-08T12:08:28Z,2017-05-08T12:08:28Z,"Virtualbox-5.1.23-115260-OSX also, 5.1.18 and 5.1.22

when the usb controller is set to usb3, connected a thumb drive works fine. when set to usb2, it cant connect. the error is in the last line of the included log file.

this ticket seems relevant, https://www.virtualbox.org/ticket/15050",pixelfairy
16724,Usb disconnect causes guest USB driver crash,Mac OS X,VirtualBox 5.1.22,2017-05-03T18:25:41Z,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
16523,Multiple Monitors on Full Screen MAC do not work,Mac OS X,VirtualBox 5.0.32,2017-03-01T11:19:50Z,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
16360,vbox guest additions disable gnome graphical login,Mac OS X,VirtualBox 5.1.12,2017-01-05T23:10:07Z,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
16362,Cannot create solid state drives when VM is running,Mac OS X,VirtualBox 5.0.30,2017-01-06T15:38:34Z,2017-01-06T15:38:34Z,2017-01-06T15:38:34Z,"I want to simulate the replacement of a solid state drive while the system is running.

I have a VM (guest OS: ubuntu 14:04), with a SATA controller of 4 hotpluggable disks. The solid-state drive is on port 3.

I first create a new medium to represent the replacement disk:
$ vboxmanage createmedium disk --filename disks/ssd6.vmdk --size 8192 --format VMDK
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Medium created. UUID: 9532c0bc-f14b-4f0c-a4df-b366024ed58d

Then I remove the solid state drive from the VM:
$vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=none

Then I want to replace it with a new virtual Solid-State Drive:
$ vboxmanage storageattach  ""standalone_default_1473423571692_13381"" --storagectl SATAController --port=3 --medium=disks/ssd6.vmdk --type hdd --nonrotational on

I get the following  error:
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""NonRotationalDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 837 of file VBoxManageStorageController.cpp


If I omit the option --nonrotational on, the command succeeds, but it's added as a regular (hotpluggable) hard disk. 






",jkv
16353,Sever Clock Drift,Mac OS X,VirtualBox 5.1.12,2017-01-04T03:11:31Z,2017-01-04T03:11:31Z,2017-01-04T03:11:31Z,"MacOS Sierra Host - Virtualbox Version 5.1.12 r112440 (Qt5.6.2)

Problem on both:

  Guest: ubuntu/xenial64 - 16.04


  Guest: boot2docker (docker-machine create -d virtualbox)

This does not seem to be related to other tickets I found.


Here are some examples:


30 seconds on guest -- 1min40 real time
{{{
ubuntu@ubuntu-xenial:~$ 
while true; do echo $(date -u -Iseconds) == $(curl --silent http://www.timeapi.org/utc/now) ;sleep 10; done
2017-01-04T02:48:35+00:00 == 2017-01-04T03:02:31+00:00
2017-01-04T02:48:46+00:00 == 2017-01-04T03:02:49+00:00
2017-01-04T02:48:56+00:00 == 2017-01-04T03:03:06+00:00
2017-01-04T02:49:06+00:00 == 2017-01-04T03:03:23+00:00
}}}

And here is another: 17 seconds on guest --> 30 seconds on host (real time)
{{{
daniel@darwin:~$ while true; do echo $(docker-machine ssh dev date) == $(date); sleep 10; done
Wed Jan 4 03:01:28 UTC 2017 == Tue 3 Jan 2017 22:06:10 EST
Wed Jan 4 03:01:32 UTC 2017 == Tue 3 Jan 2017 22:06:20 EST
Wed Jan 4 03:01:38 UTC 2017 == Tue 3 Jan 2017 22:06:31 EST
Wed Jan 4 03:01:45 UTC 2017 == Tue 3 Jan 2017 22:06:41 EST
}}}

",daneroo
16280,Shared clipboard is not working in GUI mode,Mac OS X,VirtualBox 5.1.6,2016-12-10T20:28:28Z,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
16117,Kernel Panic on 10.10.1,Mac OS X,VirtualBox 5.1.8,2016-10-26T11:48:24Z,2016-10-28T06:03:57Z,2016-10-28T06:03:57Z,There is kernel panic when using virtualbox.,Majksner
16073,Unity 8 (Ubuntu 16.10) not working,Mac OS X,VirtualBox 5.1.6,2016-10-16T23:49:39Z,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
16072,"5.1.6 messed them up, shortkeys, session information window",Mac OS X,VirtualBox 5.1.6,2016-10-16T21:46:12Z,2016-10-16T22:51:43Z,2016-10-16T22:51:43Z,"Myself is not familiarized with VB's internal architecture, so hard to select proper ""component"".

5.1.6 is the first 5.1 version used with this config.
Host OS X 10.9.5
Guests Ubuntu 64Bits Desktop 16.04 LTS
In prior of this - I guess - 5.0.26 was in use without any probs.
Build 110634 was downloaded and installed few hours ago and still in use this minute.
V.M.s run in full-screen mode.

(A)
Host key combination without effect, short-keys practically not working,
e.g. full-screen shortkey, pause V.M. short key, pop-up menu while in full-screen shortkey
Occasionally host's shortkey for making screenshots on host which doesn't have
anything in common with VB nor with its virtual machines is not working.

(B)
While in full-screen mode opening the Session Information window/dialog works quite differently
as it was before upgrade to 5.1. This dialog gets maximized to full-screen, some other 
white-background window/dialog seems to be opening in its background, closing Session Information dialog leaves some strange screen (grey background) with no function - strange host's workspaces.",Nikc
15996,MacOS 10.12 Bridge sends bad chksum,Mac OS X,VirtualBox 5.1.6,2016-09-28T06:56:21Z,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
15959,Save state crashes when 3D acceleration is enabled,Mac OS X,VirtualBox 5.1.6,2016-09-20T07:16:52Z,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
15950,OS X host UI slowdown during Linux guest usage,Mac OS X,VirtualBox 5.1.6,2016-09-18T08:46:11Z,2016-09-18T08:49:23Z,2016-09-18T08:49:23Z,"I am using VirtualBox on my OS X laptop since VirtualBox version 4.3.

When I updated my OS X to El Capitan I had to update VirtualBox to version 5.0 too (because vbox 4.x didn't support El Capitan when I applied OS X update).

Since my update to VirtualBox 5.0 I noticed that OS X User Interface (UI) slowdown in time during active guest usage.

First few days all looks OK, but after one week of active guest usage (my guest running CentOS 6 x86_64 with X Window System + Gnome, with VirtualBox guest utils) host system UI slowdown to unacceptable level. All OS X graphical effects lagging.

If I have little usage of my Linux guest, host system may slowdown very little - 1-3 weeks host may work before visible slowdown.

If I stop guest or suspend it and start again (without OS X restart), system will go back to normal state and slowdown will begin accumulate again.

One week ago I updated to Virtual Box 5.1, apply all available updates to OS X, update VirtualBox guest utils in hope to have no slowdowns. But it still happened again.

I had installed in my My OS X host: VirtualBox, Skype, Adium and nothing else, I use Safari very active. Linux guest has installed CentOS 6 with Graphical Interface, nothing special - I am using only gnome terminal + ssh.

",osx-user
15942,vm crash on macos upon cmd+c,Mac OS X,VirtualBox 5.0.26,2016-09-16T10:21:42Z,2016-09-16T19:10:50Z,2016-09-16T19:10:50Z,"virtualbox 5.0.26 on macos.
sometimes, the vm crashes (maybe once every two months or so).
last time it specifically happened when (accidentally) pressing cmd+c.

the vm log ends like this :

{{{
92:22:28.521238 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:22:28.521254 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:22:28.521277 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:22:28.521337 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:22:28.521342 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:22:28.521346 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:22:28.521470 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885280 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885336 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x5
92:53:54.885344 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x5
92:53:54.885369 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.885369 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Using fallback buffer since no source bitmap is provided
92:53:54.885610 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885626 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:53:54.885656 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.886947 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.886955 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.886959 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:56:51.703893 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:56:51.703989 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
93:43:17.399764 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received
93:43:17.401758 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.401775 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received.
93:43:17.401778 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to exit, notifying listener...
93:43:17.441045 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillExit: Machine-window #0 will exit native fullscreen
93:43:17.968714 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received
93:43:17.968735 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowDidExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.968740 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received.
93:43:17.968743 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode exited, notifying listener...
93:43:17.970210 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenDidExit: Machine-window #0 exited native fullscreen, changing visual-state to requested...
}}}",Richlv
15940,Failed to open a session while starting a virtual machine,Mac OS X,VirtualBox 5.1.6,2016-09-16T04:48:37Z,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
15498,display size 4096 or more is impossible; guest size is screen size modulo 4096,Mac OS X,VirtualBox 5.0.20,2016-06-10T09:30:21Z,2016-09-08T07:06:31Z,2016-09-08T07:06:31Z,"In ''Auto-resize Guest Display'' mode or also in Fullscreen mode on a very large screen (4096 pixels or more). I see the following wrong behaviour:

The guest's screen size is only ''actual screen size modulo 4096'' rounded down to the next smaller multiple of 8.
If the size is 4096, then 4096 % 4096 = 0, then the default 1024 width is applied. (or 768 for the height)

I tried setting different sizes with `VBoxManage controlvm <VMName> setvideomodehint` command.

I attached the VBox.log file. during that session I had executed the following commands:

{{{
VBoxManage controlvm Kubuntu setvideomodehint 4096 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4095 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 4087 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8191 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 8193 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 9192 2160 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4095 32
VBoxManage controlvm Kubuntu setvideomodehint 1000 4096 32
VBoxManage controlvm Kubuntu setvideomodehint 0 0 32
VBoxManage controlvm Kubuntu setvideomodehint 4088 2160 32
}}}


In the log file one can see, that the resulting guest display size is wrong whenever  w > 4095 or h > 4095

{{{
00:00:15.395987 VMMDev: SetVideoModeHint: Got a video mode hint (4096x2160x32)@(0x0),(1;0) at 0
00:00:15.439417 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:02:15.240295 VMMDev: SetVideoModeHint: Got a video mode hint (4095x2160x32)@(0x0),(1;0) at 0
00:02:17.409141 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:02:56.419179 VMMDev: SetVideoModeHint: Got a video mode hint (4087x2160x32)@(0x0),(1;0) at 0
00:02:58.579637 VBVA: InfoScreen: [0] @0,0 4080x2160, line 0x3fc0, BPP 32, flags 0x1

00:03:19.311747 VMMDev: SetVideoModeHint: Got a video mode hint (8192x2160x32)@(0x0),(1;0) at 0
00:03:20.454025 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1024 h=2160 bpp=32 cbLine=0x1000 flags=0x1

00:03:25.949484 VMMDev: SetVideoModeHint: Got a video mode hint (8191x2160x32)@(0x0),(1;0) at 0
00:03:28.074011 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=4088 h=2160 bpp=32 cbLine=0x3FE0 flags=0x1

00:03:43.210929 VMMDev: SetVideoModeHint: Got a video mode hint (8193x2160x32)@(0x0),(1;0) at 0
00:03:44.349569 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=2560 h=1600 bpp=32 cbLine=0x2800 flags=0x1

00:04:06.325388 VMMDev: SetVideoModeHint: Got a video mode hint (9192x2160x32)@(0x0),(1;0) at 0
00:04:08.445923 VBVA: InfoScreen: [0] @0,0 1000x2160, line 0xfa0, BPP 32, flags 0x1

00:04:43.460792 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4095x32)@(0x0),(1;0) at 0
00:04:45.586547 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=4095 bpp=32 cbLine=0xFA0 flags=0x1

00:04:49.388757 VMMDev: SetVideoModeHint: Got a video mode hint (1000x4096x32)@(0x0),(1;0) at 0
00:04:51.501883 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001266af000 w=1000 h=768 bpp=32 cbLine=0xFA0 flags=0x1

00:05:34.159715 VMMDev: SetVideoModeHint: Got a video mode hint (4088x2160x32)@(0x0),(1;0) at 0
00:05:35.290404 VBVA: InfoScreen: [0] @0,0 4088x2160, line 0x3fe0, BPP 32, flags 0x1

}}}


it looks like the size is only an 8 bit integer.  The lowest 4 bits are always 0 and bits 13 and up are lost.

I tried this with several Linux distributions (Ubuntu, Kubuntu, Mint, Fedora). The behaviour is always the same.

",schnidrig
15097,VBoxHeadless Crashes OSX El Captain on Host Suspend,Mac OS X,VirtualBox 5.0.14,2016-02-02T04:08:53Z,2016-07-06T16:37:25Z,2016-07-06T16:37:25Z,"
",jwaldrip
15456,Wrong screen geometry reported to Linux guest for unscaled HiDPI,Mac OS X,VirtualBox 5.0.20,2016-05-29T16:26:24Z,2016-05-29T16:26:24Z,2016-05-29T16:26:24Z,"I have a MacBook Pro 13"" retina with a resolution of 2560x1600 pixel and a physical screen size of around 286x177 mm.

When activation the ""unscaled HiDPI"" option, the full resolution of 2560x1600 px is reported to the Linux guest (debian jessie).

However, the physical screen size is reported as 677x423 mm, which gives the guest operation system no chance to correctly estimate the DPI resolution.

More over, the reported screen size is not reduced by MacOSX's Menu bar in seamless mode, so the bottom menus inside the linux guest are misplaced below the effective screen area.

I already use guest additions 5.0.21-r107220, because of the cursor displacement issue fixed in this snapshot version compared to the 5.0.20 release of the Linux Guest Additions.",Wolfgang Glas
15310,Auto-resize Guest Display not working,Mac OS X,VirtualBox 5.0.16,2016-04-14T19:26:21Z,2016-04-14T19:26:21Z,2016-04-14T19:26:21Z,"Host: Mac OS 10.10.5 Macbook Pro retina 15 inch with an external auria EQ276W 27"" monitor
Guest: Debian Jessie
Guest using two displays

I have auto-resize guest display enabled

In full screen mode with the primary screen on the Auria and the secondary screen on the macbook it works fine with both.
If you unplug the DP while in full screen mode it still work fine.
However if you exit full screen mode with the two screens on the macbook (external monitor still unplugged), the window for the primary display has a scroll bar on the right and bottom (ei it doesn't resize).
Also if you go back into full screen mode the primary screen no longer fits on the macbook.

Let me know if you need any additional information.

",ranamala
15282,USB subsystem or USB logging is broken,Mac OS X,VirtualBox 5.0.16,2016-03-29T20:19:04Z,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
15248,"""BUG: unable to handle kernel paging request""",Mac OS X,VirtualBox 5.0.16,2016-03-17T07:00:19Z,2016-03-17T07:02:28Z,2016-03-17T07:02:28Z,"VirtualBox 5.1.6. Host is OSX 10.11.3, guest is recent Arch Linux amd64 (4.4.5 kernel). Guest has VM Guest Additions installed.

The kernel periodically BUGs under heavy load (mostly compiling a large C++ project using `make -j 4`; VM is configured to use 4 CPUs).

Attaching dmesg output, as well as VBOX.log",neilc
15229,Can't clone with name of deleted VM / clone,Mac OS X,VirtualBox 5.0.16,2016-03-09T20:35:09Z,2016-03-09T20:35:09Z,2016-03-09T20:35:09Z,"There's something in the Virtualbox internal resources / information that persists when one deletes
the VM files manually (using OS operations), at least on MacOS.
This might have been a mistake, so there should be a way to recover via restoring
the files / directories and re-initializing the VM from recovered files,
but it might have been purposeful / the result of a bug
or failure that you *don't* want to restore (or don't care to) the missing VM.
So, there should be some way to recover by eliminating any knowledge of that VM name,
so that you can re-use it for another clone.
",SteveCat
15204,Soft lockup - CPU stuck for 22s,Mac OS X,VirtualBox 5.0.14,2016-03-04T18:01:29Z,2016-03-04T18:15:53Z,2016-03-04T18:15:53Z,"After running a Virtualbox VM brought up with Vagrant for a long period of time, we are eventually unable to reach the host. We are forced to restart the VM in order to be able to connect to it again. The kernel log contains soft lockup errors.

Host: OS X 10.10.4
Guest: Ubuntu 14.04 3.19.0-51-generic:amd64",mdelillo
15102,Attached USB device filter causes VM to not start/crash,Mac OS X,VirtualBox 5.0.14,2016-02-02T16:54:54Z,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
13033,Gnome Shell Dash Icon-text Drop Shadow Distorted / Skewed,Mac OS X,VirtualBox 4.3.10,2014-05-16T08:41:18Z,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
14427,"Oracle 12.1.0.2 Grid Installation fails to relink VB5 on Oracle Linux 6.7 guest,OSX host",Mac OS X,VirtualBox 5.0.0,2015-08-11T12:40:11Z,2016-01-12T09:18:00Z,2016-01-12T09:18:00Z,"When trying to install 12.1.0.2 Grid Infrastructure on Linux 6.7 guest on OS X (Yosemite) host using !VirtualBox 5 the installer hangs at 59% (after passing all the Oracle pre-requisites) with the error
{{{
error invoking target irman ioracle of makefile /u01/app/gi/12.1.0.2/grid/rdbms/lib/ins_rdbms.mk”
The logs provide further detail.

INFO: /usr/bin/ld: cannot find -ljavavm12
collect2: ld returned 1 exit status

INFO: make: *** [/u01/app/gi/12.1.0.2/grid/rdbms/lib/oracle] Error 1
}}}
It is possible to work around this by copying the libjavavm12.a library located in $ORACLE_HOME/javavm/jdk/jdk7/lib to $ORACLE_HOME/lib directory and retrying the install.

Once the workaround is applied, the installer continues but then the oracle root.sh script fails with a segmentation fault.
{{{
rootconfig.sh: line 131: 4562 Segmentation fault
}}}

A workaround can be applied by reinstalling the Perl binaries under the newly created ORACLE_HOME and the installation can continue.

Both errors and their work arounds are described here:
http://laurent-leturgez.com/2015/05/26/oracle-12c-vmware-fusion-and-the-perl-binarys-segmentation-fault/#comment-7644

Note, this is not my blog but has been very helpful in providing the 2 workarounds for the issue I report here.
It would be great if a permanent fix could be found is it seems this is something specific to Virtual Box 5 rather than an issue with the guest config.",MPMDBA
14922,Accessing Kinect Camera,Mac OS X,VirtualBox 5.0.10,2015-12-11T23:47:48Z,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
14917,Debian guest is aborted when plugging in or unplugging thunderbolt on mac host,Mac OS X,VirtualBox 5.0.10,2015-12-10T16:20:29Z,2015-12-10T16:20:29Z,2015-12-10T16:20:29Z,"Guest:
Debian Jessie
3.16.0-4-amd64
monitor count 2
video memory 50
ram 9000 MB
cpu 4

Host:
MacBook Pro (Retina 15-inch, Late 2013)
Processor: 2.3 GHz Intel Core i7
Memory: 16 GB
Graphics NVIDIA GeForce GT 750M 2048 MB

Unfortunately this issue is intermittent, but sometimes when I plug in or unplug the thunderbolt to an external monitor the guest goes right to aborted.

I would like to attach logs to this ticket, but I see how to.



",ranamala
14886,Virtual Machine crash,Mac OS X,VirtualBox 5.0.10,2015-12-02T15:24:59Z,2015-12-03T11:46:39Z,2015-12-03T11:46:39Z,"After several hours of working on mac os x virtual machine with installed ubuntu 12.04 server crashed.
Crash is stable 2-3 time during working day.",grustem7
14854,regression: failed to open session VD: error VERR_NOT_SUPPORTED opening image file,Mac OS X,VirtualBox 5.0.10,2015-11-21T04:10:57Z,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
14685,Xubuntu 14.04LTS with Virtualbox5 freezes when you drag a window to the border,Mac OS X,VirtualBox 5.0.6,2015-10-09T12:35:18Z,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
12383,Chrome viewport becomes always on top when rendering pages with 3d transforms,Mac OS X,VirtualBox 4.3.2,2013-11-21T18:00:31Z,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
14652,Symbolic links cannot go up file tree on shared folder.,Mac OS X,VirtualBox 5.0.4,2015-10-02T02:14:13Z,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
14592,Can't use unscaled HiDPI with Linux guest if display scaling enabled in OS X Yosemite host,Mac OS X,VirtualBox 5.0.4,2015-09-15T19:20:48Z,2015-09-15T19:20:48Z,2015-09-15T19:20:48Z,"Host is a MacBook Pro running OS X Yosemite 10.10.5, connected to a 3840x2160 display. Guest is Debian 8 with KDE 4.14.2, guest additions installed. I am attempting to run the guest OS in full-screen mode.

Display scaling is enabled in the host, with the scaled resolution set to 2560x1440. If ""Use Unscaled HiDPI Output"" is UNchecked, the guest correctly sees 2560x1440 as a resolution choice, and defaults to it.

If ""Use Unscaled HiDPI Output is checked, then the display does not work properly. The highest resolution reported to the guest appears to be 2560x1600 (not 3840x2160 as it should be), and for some reason the resolution selected by default is 1024x2880 (which isn't even a valid resolution). This results in the entire display being compressed into a narrow vertical strip up the middle of the screen, with everything squeezed to illegibly small size. Manually selecting 2560x1600 in the guest results in a similarly unreadable rectangle in the center of the screen.

Disabling display scaling on the host results in correct guest behavior, allowing guest to access full 3840x2160 native resolution. Unfortunately, this results in UI elements on host OS X desktop being unusably small. So it seems it is impossible to have both a usable host desktop, AND give the guest OS access to the full native display resolution.

To summarize, the functionality of the Use Unscaled HiDPI Output checkbox appears to be broken in 5.0.4, at least for the hardware/software configuration described above.",MikeUatCS
14522,Unity 3D supported: no,Mac OS X,VirtualBox 5.0.2,2015-08-30T21:39:57Z,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
11005,Unable to ping guest from host in host-only network; ping6 works,Mac OS X,VirtualBox 4.2.0,2012-09-30T18:15:27Z,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
8866,Guest network not able to reach beyond host's network when host bridged adaptor is using LACP (bonding),Mac OS X,VirtualBox 4.0.6,2011-05-09T14:33:27Z,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
13022,I/O errors reported by kernel for device backed by VDI,Mac OS X,VirtualBox 4.3.10,2014-05-09T05:28:05Z,2015-07-14T12:15:31Z,2015-07-14T12:15:31Z,"/dev/sda backed by a VDI

/dev/sdb backed by a vmdk, created with the command:
sudo VBoxManage internalcommands createrawvmdk -filename /Users/chris/VirtualBox\ VMs/Fedora\ Rawhide/320g.vmdk -rawdisk /dev/disk2

/media/sf_chris/ is a Shared Folder whose source is HFS+

During sustained copying from /media/sf_chris and writing to /dev/sdb, the kernel reports spurius read and write errors from /dev/sda which is essentially inactive in this process. Long file copies (10 minutes) eventually result in segfaults, the system will no longer respond to commands and I can't even get kernel messages out of the VM to see what's gone wrong other than it looks like the I/O errors are effectively corrupting the OS as it's running.

[  222.202808] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  222.203003] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  222.203287] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  222.203407] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  222.203528] rawhide.localdomain kernel: Write(10): 2a 00 00 58 a1 c8 00 02 00 00
[  222.203644] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 5808584
[  222.203746] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
[  273.598086] rawhide.localdomain kernel: sd 0:0:0:0: [sda] Unhandled error code
[  273.598179] rawhide.localdomain kernel: sd 0:0:0:0: [sda]  
[  273.598255] rawhide.localdomain kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  273.598341] rawhide.localdomain kernel: sd 0:0:0:0: [sda] CDB: 
[  273.598437] rawhide.localdomain kernel: Read(10): 28 00 01 17 73 40 00 00 20 00
[  273.598533] rawhide.localdomain kernel: end_request: I/O error, dev sda, sector 18314048
[  273.598618] rawhide.localdomain kernel: BTRFS: bdev /dev/sda3 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0

The host kernel messages report no IO related errors. But does report other things related to VirtualBox at the time the problem occurs:

May  8 23:04:16 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:44 ming kernel[0]: VirtualBox (map: 0xffffff8050dfec18) triggered DYLD shared region unnest for map: 0xffffff8050dfec18, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VirtualBoxVM (map: 0xffffff803cc1b138) triggered DYLD shared region unnest for map: 0xffffff803cc1b138, region 0x7fff8ba00000->0x7fff8bc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
May  8 23:04:48 ming kernel[0]: VBoxDrv: host_vmxon  -> vmx_use_count=1 rc=0
May  8 23:13:46 ming kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0

The vboxlog reports a lot of issues related to AHCI:

00:43:34.854982 AHCI#0P0: Cancelled task 7
00:43:34.855589 AHCI#0: Port 0 reset
00:43:50.165909 AHCI#0P0: Cancelled task 31
00:43:50.165928 AHCI#0: Port 0 reset
00:44:05.474666 AHCI#0P0: Cancelled task 31
00:44:05.474685 AHCI#0: Port 0 reset
00:44:35.781838 AHCI#0P0: Cancelled task 31
00:44:35.782117 AHCI#0: Port 0 reset
00:44:43.107712 AsyncCompletion: Task 0x00000131801a40 completed after 98 seconds
00:44:43.107728 AsyncCompletion: Task 0x00000131801ac0 completed after 98 seconds
00:44:43.107734 AsyncCompletion: Task 0x00000131801a80 completed after 98 seconds
00:44:43.108556 AsyncCompletion: Task 0x00000131801b40 completed after 98 seconds
00:44:43.108572 AsyncCompletion: Task 0x00000131801b00 completed after 98 seconds
00:44:43.108605 AsyncCompletion: Task 0x00000131801b80 completed after 98 seconds
00:44:43.148090 AHCI#0P0: Flush request was active for 98 seconds
00:44:43.148101 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:43.148108 AsyncCompletion: Task 0x00000131801bc0 completed after 98 seconds
00:44:43.473168 AHCI#0P0: Flush request was active for 68 seconds
00:44:43.473183 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688476 AHCI#0P0: Flush request was active for 54 seconds
00:44:44.688495 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS
00:44:44.688838 AHCI#0P0: Flush request was active for 38 seconds
00:44:44.688850 AHCI#0P0: Canceled flush returned rc=VINF_SUCCESS

Since this is reporting the problem is with sda and not sdb, I don't think it's the physical external drive causing the problem, it's either a guest additions bug or how AHCI is implemented in VBox and interacting with Linux.

kernel-3.15.0-0.rc4.git0.1.fc21.x86_64",Chris Murphy
10860,Full resolution not exposed to Linux guest,Mac OS X,VirtualBox 4.1.20,2012-08-24T08:51:43Z,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
14191,"VBoxSVC crashing, VirtualBox broken in several ways",Mac OS X,VirtualBox 4.3.28,2015-06-12T02:58:18Z,2015-06-17T01:39:10Z,2015-06-17T01:39:10Z,"It's tough to explain what's going on, but here's a post I made on the forum which has screenshots and explanations:

https://forums.virtualbox.org/viewtopic.php?f=8&t=68309

Basically everything is broken. I'm unable to add new guests, and the ones I load up act oddly. It would be great if someone could walk me through some debugging/troubleshooting steps. Something is badly broken here, even after a complete uninstall and fresh install.",CaptSaltyJack
14129,No Internet Connection under Host Only / NAT: DHCP,Mac OS X,VirtualBox 4.3.28,2015-05-17T15:47:11Z,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
14117,One Linux guest crashes on OS X (10.10.3) host in AioMgr0 or Port0 thread,Mac OS X,VirtualBox 4.3.26,2015-05-15T09:23:34Z,2015-05-15T09:23:34Z,2015-05-15T09:23:34Z,"Having two VM on same machine with very similar (but not cloned) setup. 

One crashes frequently. Other one just keep going. 

I am seeing two different crashes. Both are attached. I have seem them both with headless and GUI guests-

",Dennis Schafroth
13104,Network issues on OS X 10.10 Yosemite,Mac OS X,VirtualBox 4.3.12,2014-06-06T15:33:43Z,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
14023,Modifier keys from the virtual keyboard don't get passed through,Mac OS X,VirtualBox 4.3.26,2015-04-02T23:53:33Z,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
13881,Login screen not full screen on Oracle Linux 5,Mac OS X,VirtualBox 4.3.22,2015-02-22T21:35:48Z,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
13844,Ubuntu guest on Mac OS X stops tracking battery status after full charge,Mac OS X,VirtualBox 4.3.22,2015-02-16T16:49:36Z,2015-02-16T16:49:36Z,2015-02-16T16:49:36Z,"As the subject says, an Ubuntu guest tracks the battery status of the Mac host but stops if the host is charged to 100% of the battery. After that point, the Ubuntu guest reports a 100% charged battery regardless of the status of the host (plugged or unplugged).

This issue '''is not present''' with a Windows 7 guest, for example. The Windows client continues to track battery status without problems after a full charge.

Some details about my setup:[[BR]]

'''Guest'''[[BR]]
Ubuntu 14.04 LTS
4 Processors 2GB of memory

'''Host'''[[BR]]
MacBookPro Intel Core i7 4GB of Memory
Mac OS X 10.10.3 (14D72i), but the problem was observed with 10.10.2 public release version as well.",SototaSoft
13718,Write same error when using SAS controller with Arch Linux guest,Mac OS X,VirtualBox 4.3.20,2014-12-27T01:23:00Z,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
9570,MacOSX Menubar appearing in Fullscreen Client,Mac OS X,VirtualBox 4.1.2,2011-09-08T06:50:16Z,2014-11-27T23:30:38Z,2014-11-27T23:30:38Z,"After the Host Screen is locked with the screensaver or the host goes to sleep, and is subsequently woken up, the MacOSX Menubar for VirtualBox appears in a full screen client, when the cursor moves to the very top of the screen. 

A workaround to keep the menubar from appearing again is to switch the guest out of fullscreen, minimize the guest to the dock, have the guest window come back up and switch back to fullscreen. Then the menubar does not reappear, until the next time the host display is locked. 

Host is MacOS X SnowLeopard, Guest is Ubuntu 11.04.
This also happened with VirtualBox 4.0.x.",srd
8057,First mouse click in virtual screen interpreted as drag,Mac OS X,VirtualBox 4.0.0,2011-01-11T06:53:56Z,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
12958,Virtualbox fails to start in headless mode with 3d acceleration enabled.,Mac OS X,VirtualBox 4.3.10,2014-04-18T00:47:53Z,2014-04-18T00:47:53Z,2014-04-18T00:47:53Z,Virtualbox fails with uninformative message when 3d acceleration is enabled and guest OS is started in headless mode using shift+Start.,berkovskyy
12287,VBox 4.3.2 Video Capture without cursor,Mac OS X,VirtualBox 4.3.2,2013-11-02T00:49:33Z,2013-11-18T14:49:39Z,2013-11-18T14:49:39Z,The VBox 4.3.2 Video Capture cannot capture the cursor as well.,Samiux
10351,Host-Q and Host-H do not follow host key remapping,Mac OS X,VirtualBox 4.1.10,2012-03-19T20:15:25Z,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
9757,"MacOS 10.6.8 host, Fedora14-x86-64 guest, Gnome WM, window moves=artifacts",Mac OS X,VirtualBox 4.1.4,2011-10-14T17:20:15Z,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
8888,Unabled to pass Command-Q (Super-Q/Win-Q) to guest machine from OSX host,Mac OS X,VirtualBox 4.0.6,2011-05-13T21:00:09Z,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
9076,After canceling Cmd-Q confirmation dialog keyboard settings are screwed up,Mac OS X,VirtualBox 4.0.8,2011-06-15T05:52:54Z,2011-06-15T05:52:54Z,2011-06-15T05:52:54Z,"I'm using a debian squeeze 64bit guest on my MacOSX 10.6.7 host.

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

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

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

  TIA, Wolfgang",Wolfgang Glas
8731,Cannot use bond0 on Mac OS X 10.6.7 and some other errors...,Mac OS X,VirtualBox 4.0.4,2011-04-16T16:13:51Z,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
8719,Mouse pointer calibration issue in seamless mode,Mac OS X,VirtualBox 4.0.4,2011-04-14T03:08:59Z,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
8460,Mouse events don't come to the guest while snapshot deletion is in progress,Mac OS X,VirtualBox 4.0.4,2011-02-28T18:36:42Z,2011-02-28T18:36:42Z,2011-02-28T18:36:42Z,"Ubuntu guest doesn't get any mouse events while snapshot deletion is running when launched from the main vbox window. Progress dialog is active.

This is unreasonable to affect guest this way since past snapshot deletion has nothing to do with the guest's current state.",yurivict
8144,Dock does not show up anymore after switching between applications,Mac OS X,VirtualBox 4.0.2,2011-01-21T16:51:00Z,2011-01-21T16:51:00Z,2011-01-21T16:51:00Z,"Steps to reproduce:
 * Enable the option ""show dock and menu bar in full screen mode automatically""
 * Switch VM to full screen mode
 * When I move the mouse to the top border, the menu bar shows up. When I move mouse to the left border, the dock shows up. (I have my dock configured to the left side of the screen.) This is the expected behavior.
 * I click on the icon of some other application in the dock. The windows of this application show up.
 * I click on the icon of the VM in the dock or (makes no difference) click in the VM desktop in the background. The windows of the other application and the dock disappear.
 * When I move the mouse now to the left border, nothing happens. The dock does not show up anymore. However the menu bar on the top border still shows up if I move the mouse there.
 
Hiding the VM and the reentering the VM does not change anything, the dock still does not work anymore. What helps is switching off and then on again the full screen mode. Then the dock works again, until the next time.",cmr
7816,"CPU Idle load hi with ""divider=10""",Mac OS X,VirtualBox 3.2.12,2010-12-10T02:57:43Z,2010-12-10T02:57:43Z,2010-12-10T02:57:43Z,"Idle load with CentOs 5.5 client on OSX 10.6.5 host is ~ 75%. I added ""divider=10"" to grub.conf post additions, and have rebooted the client and the application; still idle load is high.

",Dale Douglas
7749,Vboxsf has no read caching on linux,Mac OS X,VirtualBox 3.2.10,2010-11-21T15:20:48Z,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
4789,"""vboxvideo does not export required DRI extension""",Mac OS X,VirtualBox 3.0.4,2009-08-16T16:14:26Z,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
5943,LeftCommand+H cannot be passed to guest on Mac OS X,Mac OS X,VirtualBox 3.1.2,2010-01-08T19:43:02Z,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
5806,Dialog should not include whole status because it doesn't fit,Mac OS X,VirtualBox 3.1.2,2009-12-20T09:45:33Z,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
5594,Keyboard mapping problems using SSH tunneling,Mac OS X,VirtualBox 3.0.12,2009-11-30T02:42:13Z,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
21500,aRC=VBOX_E_FILE_ERROR (0x80bb0004),Linux,VirtualBox-7.0.6,2023-02-12T20:13:33Z,2023-02-12T20:21:59Z,2023-02-12T20:21:59Z,"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



",pabel
21499,aRC=VBOX_E_FILE_ERROR (0x80bb0004),Linux,VirtualBox-7.0.6,2023-02-12T20:12:20Z,2023-02-12T20:12:20Z,2023-02-12T20:12:20Z,"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



",pabel
21487,3D acceleration causes Linux guest freezes,Linux,VirtualBox-7.0.6,2023-02-09T12:20:27Z,2023-02-12T01:04:54Z,2023-02-12T01:04:54Z,"Hi,

//Checking the forums, there seems to be several people reporting instances of their '''Windows 11 Guests''' freezing.  I have a situation with '''Linux Guests'''.  Below are some details in case you need a test case.//

I'm experiencing frequent freezes when 3D acceleration is enabled on Linux Guests.  There is no issue with a '''Windows 10 Guest'''.

The current work-around is to disable 3D acceleration.

I captured a core dump of the frozen Guest using '''vboxmanage debugvm dumpvmcore'''.  If there is any value, I can upload it to my G Drive.  It is 460 MB.

== Environment ==

=== Guest

I have tried to create a minimal test case using openSUSE MicroOS (immutable O/S).

Below are some of the highlight settings of the Guest.  However I suspect '''VBox.log''' may only be needed.

* Download latest MicroOS - https://get.opensuse.org/microos/#download
* Set up a new Guest VM:
  * Base memory:  3072 MB (4096 crashes)
  * Processor:  1
  * Storage:  
    * controller > Use Host I/O Cache
    * 30 GB vdi > Solid-state Drive (assuming you're using an SSD)
      * Current allocation is 8.02 GB
  * Display:
    * Video Memory:  128 MB
    * Graphics controller:
      * VMSVGA
      * Enable 3D Acceleration
* Using the MicroOS ISO, create a new Guest
  * Selected local TZ rather than UTC.
  * Select KDE desktop
* On first boot, the Guest will set up bootstrap apps.
* Use '''discover''' to install the '''Brave browser'''.  '''Discover''' is KDE's flatpak manager.  By default, it lives in the systray.  Its icon is a blue shopping bag.  :)
* I did some minor KDE tweaking (e.g. focus-follows-mouse, etc.)  If required, I could upload a tar-ball of the test user's $HOME.

=== Test Case

Using the test case below, the Guest may take upwards of a few hours to freeze.  Sometimes it freezes in a few minutes.

I run it in a '''Virtual Desktop''' and periodically check.

* Run two instances of '''Brave'''
* In each, go to web pages that auto-refresh periodically.  For example:
  * https://edition.cnn.com
  * https://www.theweathernetwork.com/fr/weather/ile-de-france/paris

=== Host

* openSUSE Tumbleweed - rolling distro
* Regularly kept up to date.
* As of this writing, kernel 6.1.8-1
* Using '''Prime offloading'''
  * iGPU - Intel UHD Graphics
  * dGPU - Nvidia GeForce RTX 2060 Max-Q  
",Pablo Sanchez
21440,I/O errors with virtio-scsi,Linux,VirtualBox-7.0.6,2023-01-28T00:22:38Z,2023-02-09T18:44:17Z,2023-02-09T18:44:17Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
21476,Virtualbox 7.x wrong Guest Additions info at Runtime Information,Linux,VirtualBox-7.0.6,2023-02-08T15:29:10Z,2023-02-09T15:34:17Z,2023-02-09T15:34:17Z,"I noticed Virtualbox 7.x wrong Guest Additions info at Runtime Information. It is something i am seeing for a long time now (7.x and back 6.x).

    
{{{
sudo VBoxControl guestproperty enumerate
}}}


reports the right version though, but Machine -> Session Information -> Runtime Information' is reporting 6.0.0 r127566 for a long time now, in all my linux guests on linux hosts; no matter what kernel or linux version of Fedora i use or have used.
My windowsVM does report the right version btw.
There are no other GA files on the guest machines but 7.0.6",Richard E van der Luit
21474,Global buffer overflow in hdaMmioWrite(),Linux,VirtualBox-7.0.6,2023-02-08T03:23:02Z,2023-02-08T03:23:02Z,2023-02-08T03:23:02Z,"When issuing mmio_writeb(0x2146, 0xc2), cbBefore[1] can be too large for g_afMasks[2], which only has five elements.

{{{
static DECLCALLBACK(VBOXSTRICTRC) hdaMmioWrite(PPDMDEVINS pDevIns, void *pvUser, RTGCPHYS off, void const *pv, unsigned cb) {
    // ...
    idxRegDsc = hdaR3RegLookupWithin(off);
    if (idxRegDsc != -1)
    {
        uint32_t const cbBefore = (uint32_t)off - g_aHdaRegMap[idxRegDsc].off; // [1]
        Assert(cbBefore > 0 && cbBefore < 4);
        off      -= cbBefore;
        idxRegMem = g_aHdaRegMap[idxRegDsc].idxReg;
        u64Value <<= cbBefore * 8;
        u64Value  |= pThis->au32Regs[idxRegMem] & g_afMasks[cbBefore]; // ------> [2]
}}}",cyruscyliu
21438,"VirtualBox ""forgetting"" that an instance is running -> data corruption",Linux,VirtualBox-7.0.6,2023-01-28T00:08:07Z,2023-01-28T08:54:30Z,2023-01-28T08:54:30Z,"I have seen this many times.

I'm not sure how to reproduce this, but something must be fundamentally broken if this is can happen, so you should be able to figure this out my looking at the code.

Here is what happens.

I am working with guests.
Suddenly, _something_ happens, which leaves the guest running, but gives VirtualBox the impression that it is not running any more.

So VirtualBox thinks that it's switched off.

This happens with both the GUI and if I use VBoxManager list runningvms.

Since it thinks it's off, clicking on it will start it again.

What happens then is that we get two instances running, with both having read-write access to the same underlying storage devices.

You can how this ends: with tears, blood and of course irrecoverable data corruption. (Two OSs writing to the same file system at the same time...)

This is messed up beyond words.

I am attaching a screenshot, which shows two instances of the UI, running on the same host, with the same user.

One shows the guest on, the other shows it off.

The only difference is that I have launched the other instance of the GUI a bit later, but there was no configuration change. There is no reason why would it show a different status.

You can also see the output of list runningvms on the same screenshot. (Empty.)

Btw the actual guest is only visible on the screen, which is showing another data corruption bug with virtio-scsi, about which I will open a separate bug report.
",csillag
21439,I/O errors with virtio-scsi,Linux,VirtualBox-7.0.6,2023-01-28T00:22:36Z,2023-01-28T00:22:36Z,2023-01-28T00:22:36Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
21418,general protection fault in VBoxRT.so on Linux 5.15,Linux,VirtualBox 6.1.40,2023-01-20T00:47:16Z,2023-01-20T00:47:16Z,2023-01-20T00:47:16Z,"On Linux 5.15.0-58-generic as shipped by Ubuntu, I have been getting repeated general protection faults while trying to run a Linux guest:

[104009.209640] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[104254.184865] traps: CharIo[1979689] general protection fault ip:7fdabb249cec sp:7fda75ab2c88 error:0 in VBoxRT.so[7fdabb0da000+1ca000]
[112313.218922] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[112533.549601] traps: CharIo[2118320] general protection fault ip:7f1e2041bcec sp:7f1deec85c88 error:0 in VBoxRT.so[7f1e202ac000+1ca000]
cfriesen@yow-cfriesen-lx:~/vdm_workspace/iso/wrcp$ 


The VM log file looks like this:

00:00:29.903869 GIM: KVM: VCPU  4: Enabled system-time struct. at 0x0000000501fc6100 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b4fd3719 uVirtNanoTS=0x6e702e07f TscKHz=2999974
00:00:29.910783 APIC5: Switched mode to x2APIC
00:00:29.910795 GIM: KVM: VCPU  5: Enabled system-time struct. at 0x0000000501fc6140 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b636f299 uVirtNanoTS=0x6e76b748e TscKHz=2999974
00:00:29.916720 APIC6: Switched mode to x2APIC
00:00:29.916669 GIM: KVM: VCPU  6: Enabled system-time struct. at 0x0000000501fc6180 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b7460d8d uVirtNanoTS=0x6e7c5d311 TscKHz=2999974
00:00:29.921905 APIC7: Switched mode to x2APIC
00:00:29.921824 GIM: KVM: VCPU  7: Enabled system-time struct. at 0x0000000501fc61c0 - u32TscScale=0xaaab08c1 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x14b833dc4c uVirtNanoTS=0x6e8151828 TscKHz=2999974
00:00:29.914199 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.925422 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.919380 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.907340 IEM: rdmsr(0x4e) -> #GP(0)
00:00:29.886932 IEM: rdmsr(0x4e) -> #GP(0)
00:00:40.477240 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:40.477303 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:40.481279 AHCI#0: Reset the HBA
00:00:40.481292 VD#0: Cancelling all active requests
00:00:40.481295 VD#1: Cancelling all active requests
00:00:40.481297 VD#2: Cancelling all active requests
00:00:40.590027 AHCI#0: Port 0 reset
00:00:40.591645 VD#0: Cancelling all active requests
00:00:40.933168 AHCI#0: Port 1 reset
00:00:40.934890 VD#1: Cancelling all active requests
00:00:41.261123 AHCI#0: Port 2 reset
00:00:41.262793 VD#2: Cancelling all active requests


",Chris Friesen
20155,"""VBoxManage convertfromraw --format=vdi"" silently fails?",Linux,VirtualBox 6.1.18,2021-01-26T09:35:15Z,2023-01-18T19:33:51Z,2023-01-18T19:33:51Z,"I have a raw image that perfectly runs with qemu-kvm, obtained with a Ubuntu Server headless install.

I'm trying to convert this raw image to VDI using VBoxManage, but it appears to fail while not providing any error message.

More precisely, here is what happens:

1) I run this command :


{{{
$ VBoxManage convertfromraw --format vdi output/mini-ubuntu-base.img output/mini-ubuntu-base.vdi
}}}


2) It prints what follows and appears to be running (and my CPU load does tell it is running):


{{{
Converting from raw image file=""output/mini-ubuntu-base.img"" to file=""output/mini-ubuntu-base.vdi""...
Creating dynamic image with size 21474836480 bytes (20480MB)...
}}}


3) *While* it is running, using a second terminal, I can see that a VDI file is being created :


{{{
$ ls -lah output | grep vdi
-rw-------. 1 ebo ebo 6,5G 26 janv. 10:28 mini-ubuntu-base.vdi
}}}


4) But then, when the 'VBoxManage' command returns… the VDI file has disappeared!


{{{
$ ls -lah output | grep vdi
<nothing>
}}}

Which means something went wrong somewhere I suppose, but I tend to believe that some output should tell so?


Additional note: I have other raw images obtained through a similar process that I manage to convert into VDI using VBoxManage without problem using my current environment.",ebo
21309,[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out,Linux,VirtualBox-7.0.4,2022-11-24T10:14:40Z,2023-01-16T13:56:25Z,2023-01-16T13:56:25Z,"Hi,

Seeing this below error after upgrade to VBOX 7.0.4

[Thu Nov 24 06:55:56 2022] CPU: 0 PID: 9189 Comm: kworker/0:1 Kdump: loaded Tainted: G           OE     5.4.17-2136.313.6.el8uek.x86_64 #2
[Thu Nov 24 06:55:56 2022] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[Thu Nov 24 06:55:56 2022] Workqueue: events vmw_fb_dirty_flush [vmwgfx]

Attaching the file with dmesg from VM.

Host: Fedora 
Host Kernel: 6.0.8-300.fc37.x86_64
VM : Oracle Linux Server release 8.7
VM Kernel: 5.4.17-2136.313.6.el8uek.x86_64

Please let me know if you need any further information.
Thanks,
Srini.",Srini8987
20826,tinycore 1.4 crashes VirtualBox,Linux,VirtualBox 6.1.32,2022-02-13T12:05:01Z,2022-10-21T12:52:40Z,2022-10-21T12:52:40Z,"Steps to reproduce:

DL http://tinycorelinux.net/archive/tinycore_1.4.iso and use it.

Start a VM.",Artem S. Tashkinov
18219,VERR_NOT_SUPPORTED for a valid ISO image,Linux,VirtualBox 6.0.0,2018-12-21T15:17:07Z,2022-10-21T12:47:37Z,2022-10-21T12:47:37Z,"Both VirtualBox 6.0 and 5.2.22 don't accept this ISO image:

http://mirror.ppa.trinitydesktop.org/trinity/cdimages/ubuntu/tde-ubuntu-14.04-desktop-latest-amd64.iso

The error is:

Failed to open the disk image file /tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso.

Could not get the storage format of the medium '/tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso' (VERR_NOT_SUPPORTED).


{{{
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}


",Artem S. Tashkinov
19496,Virtualbox 6.1.6 guest screen resize broken,Linux,VirtualBox 6.1.6,2020-04-15T21:42:27Z,2022-09-20T20:23:32Z,2022-09-20T20:23:32Z,"
The virtualbox 6.1.6 update seems to be okay, but if the matching guest additions is applied to the guest, the auto-resize or resize to any resolution is unavailable.  I applied guest additions to several hosts before discovering this issue, including Centos-6, Centos-7, Centos-8, kali linux, and OracleLinux-8.  Guests that have not gotten the update seem to be working fine.

Matt",Wheaties
18343,Unable to import OVA with error NS_ERROR_INVALID_ARG,Linux,VirtualBox 6.0.2,2019-01-21T15:13:38Z,2022-07-23T07:02:26Z,2022-07-23T07:02:26Z,"$ vboxmanage import packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova
{{{
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /var/lib/jenkins/tsenay/packer-core-os-builder/packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova...
OK.
Disks:
  vmdisk1       41943040000     -1      http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized       rhel-75-x86_64-core-os-disk001.vmdk     -1      -1

Virtual system 0:
 0: Suggested OS type: ""RedHat_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: Suggested VM name ""rhel-75-x86_64-core-os""
    (change with ""--vsys 0 --vmname <name>"")
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: Suggested VM settings file name ""/home/ldapccs/tsenay/VirtualBox VMs/rhel-75-x86_64-core-os/rhel-75-x86_64-core-os.vbox""
    (change with ""--vsys 0 --settingsfile <filename>"")
 4: Suggested VM base folder ""/home/ldapccs/tsenay/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Description ""packer-core-os-image Virtual Machine""
    (change with ""--vsys 0 --description <desc>"")
 6: Number of CPUs: 2
    (change with ""--vsys 0 --cpus <n>"")
 7: Guest memory: 2048 MB
    (change with ""--vsys 0 --memory <MB>"")
 8: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 9: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 9 --ignore"")
10: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: Hard disk image: source image=rhel-75-x86_64-core-os-disk001.vmdk, target path=rhel-75-x86_64-core-os-disk001.vmdk, controller=9;channel=0
    (change target path with ""--vsys 0 --unit 11 --disk path"";
    disable with ""--vsys 0 --unit 11 --ignore"")
0%...10%...20%...30%...40%...50%...
Progress state: NS_ERROR_INVALID_ARG
VBoxManage: error: Appliance import failed
VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 957 of file VBoxManageAppliance.cpp
}}}",tsenay
20979,machine folder share corrupts data,Linux,VirtualBox 6.1.34,2022-06-11T01:27:45Z,2022-06-11T01:27:45Z,2022-06-11T01:27:45Z,"After upgrading to 6.1.32, machine folder shares started showing corruption when being written to. Also happens in 6.1.34. Happens on new install of ubuntu 22.04 as guest on ubuntu 22.04 host.",illk
18705,Icon error,Linux,VirtualBox 6.0.8,2019-06-12T21:32:30Z,2022-05-30T22:25:28Z,2022-05-30T22:25:28Z,"i am using ubuntu as host and when i launch some virtual machine, the icon does not appears. It looks like a lost item.",betoherrera82
20907,VirtualBox window doesn't move or resize,Linux,VirtualBox 6.1.32,2022-04-22T15:58:43Z,2022-04-27T13:38:30Z,2022-04-27T13:38:30Z,"Versión 6.1.34 r150636 (Qt5.12.8)
host: Ubuntu Mate 20.04.4 x64
vm: Ubuntu Mate 22.04 x64

VirtualBox window doesn't move or resize. this is an old bug, which was fixed by checking the box ""Machine Windows: Raise Windows Under Mouse""

Currently this option, despite the fact that it still solves the problem, does so partially, that is, it works intermittently",mrvst
20861,Guest Additions do not build on Centos Stream 8,Linux,VirtualBox 6.1.32,2022-03-07T15:04:04Z,2022-03-22T16:11:33Z,2022-03-22T16:11:33Z,"Updated to the latest kernel on CentosStream 8: 4.18.0-365.el8.x86_64 and the Guest Additions does not compile anymore.
Tried the 6.1.32, then the latest 6.1.33-149980 and the result is the same: the vbox_drv.h tries to include drm/ttm/ttm_memory.h which is not available anymore in this kernel release (apparently the ttm subtree was restrustured).",piters
20858,6.1.32 Ubuntu package lacks the VirtualBox.chm manual file,Linux,VirtualBox 6.1.32,2022-03-06T07:12:07Z,2022-03-06T07:12:07Z,2022-03-06T07:12:07Z,"Help > Contents will reveal an error dialog saying ""Unable to load the chm file /usr/share/doc/virtualbox-6.1/VirtualBox.chm""

```
$ tree /usr/share/doc/virtualbox-6.1/
virtualbox-6.1/
├── changelog.Debian.gz
├── LICENSE
└── UserManual.pdf

0 directories, 3 files
```

I've extracted the package https://download.virtualbox.org/virtualbox/6.1.32/virtualbox-6.1_6.1.32-149290~Ubuntu~eoan_amd64.deb and can also verify that the file is indeed missing.","林博仁(Buo-Ren, Lin)"
20822,Not able to import an OVA and converting the virtual disk to VDI,Linux,VirtualBox 6.1.32,2022-02-10T11:31:42Z,2022-02-23T18:01:18Z,2022-02-23T18:01:18Z,"

I'm using the official Ubuntu focal cloud image in ova format downloaded from

https://cloud-images.ubuntu.com/focal/current

I try to import it with the command:
{{{
VBoxManage import focal-server-cloudimg-amd64.ova
  --options importtovdi   --vsys 0 --vmname focal-osm11
           --memory 8192 --cpus 2 --eula accept
           --unit 9 --ignore
}}}
Note: I use the importtovdi to be able to resize the disk

I get the following error
{{{           
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/paag/virt/vbox-cloud/focal-server-cloudimg-amd64.ova...
OK.
Disks:
  vmdisk1	10737418240	0	http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized	ubuntu-focal-20.04-cloudimg.vmdk	565177344	-1	

Virtual system 0:
 0: Suggested OS type: ""Ubuntu_64""
    (change with ""--vsys 0 --ostype <type>""; use ""list ostypes"" to list all possible values)
 1: VM name specified with --vmname: ""focal-osm11""
 2: Suggested VM group ""/""
    (change with ""--vsys 0 --group <group>"")
 3: VM settings file name specified with --settingsfile: ""/home/paag/VirtualBox VMs/focal-osm11/focal-osm11.vbox""
 4: Suggested VM base folder ""/home/paag/VirtualBox VMs""
    (change with ""--vsys 0 --basefolder <path>"")
 5: Product (ignored): Ubuntu 20.04 Server (20220208)
 6: No. of CPUs specified with --cpus: 2
 7: Guest memory specified with --memory: 8192 MB
 8: Network adapter: orig VM Network, config 3, extra type=Bridged
 9: Floppy -- disabled
10: CD-ROM
    (disable with ""--vsys 0 --unit 10 --ignore"")
11: SCSI controller, type LsiLogic
    (change with ""--vsys 0 --unit 11 --scsitype {BusLogic|LsiLogic}"";
    disable with ""--vsys 0 --unit 11 --ignore"")
12: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 12 --ignore"")
13: IDE controller, type PIIX4
    (disable with ""--vsys 0 --unit 13 --ignore"")
14: Hard disk image: source image=ubuntu-focal-20.04-cloudimg.vmdk, target path=ubuntu-focal-20.04-cloudimg.vdi, controller=11;channel=0
    (change target path with ""--vsys 0 --unit 14 --disk path"";
    disable with ""--vsys 0 --unit 14 --ignore"")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_INVALID_OBJECT_STATE
VBoxManage: error: Appliance import failed
VBoxManage: error: Storage for the medium '/home/paag/VirtualBox VMs/focal-osm11/ubuntu-focal-20.04-cloudimg.vdi' is not created
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 1119 of file VBoxManageAppliance.cpp
}}}
",paaguti-u
20790,vboxnetx adapters are having a wrong broadcast address,Linux,VirtualBox 6.1.32,2022-01-24T18:22:39Z,2022-02-01T13:11:49Z,2022-02-01T13:11:49Z,"If I create a hostonly adapter (e.g. vboxnet2) having the following IPV4 parameters:

Address: 10.10.10.1
Netmask: '''255.255.252.0'''

I expect the following result in my host:
# ip addr
6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.11.255''' scope global vboxnet2

and NOT (see brd value)

6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.10.255''' scope global vboxnet2

It seems that there is an error creating the broadcast value on the HOST.",gabrymark26
19226,VM segfaults on copy with shared clipboard,Linux,VirtualBox 6.1.2,2020-01-15T10:30:50Z,2022-01-31T10:33:36Z,2022-01-31T10:33:36Z,"When using the shared clipboard, all running VMs in certain states crash whenever some input it copied on the host.

Steps to reproduce:
1. Start VM and login
2. Open libreoffice calc on host
3. Select and copy some cells
   => VM crashes

No messages are in the VBox log of the VM, but there are some in the journal of the host.
{{{
ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
ShClipboard[1599]: segfault at 4 ip 00007fe97c14a1ae sp 00007fe95c199cf0 error 4 in VBoxSharedClipboard.so[7fe97c143000+8000]
Code: 89 c4 85 c0 78 50 48 8d 4d c0 ba 30 75 00 00 44 89 f6 4c 89 ff 67 e8 b1 c9 ff ff 41 89 c4 85 c0 78 34 48 8b 45 c0 48 8b 7b 08 <8b> 50 04 39 53 04 0f 46 53 04 48 8b 70 08 89 d2 ff 15 84 5c 00 00
audit: type=1701 audit(1579083656.742:64): auid=1000 uid=1000 gid=1000 ses=2 pid=1559 comm=""ShClipboard"" exe=""/usr/lib/virtualbox/VirtualBoxVM"" sig=11 res=1
}}}

The issue also occurs when copying from the guest, but I currently don't have a reproducer for that. Journal message on host:
{{{
SHCLX11[3662]: segfault at 8 ip 00007efc7073d3ea sp 00007efc71b6c8a0 error 4 in VBoxSharedClipboard.so[7efc70736000+8000]
}}}

Version used is 6.0.12, but the issue was also present in at least 6.1.0.
Host is running Arch Linux, guest is Kali Linux (haven't tested with other combinations).",udine
20784,Dragging a file from mobile phone to guest crashes the machine,Linux,VirtualBox 6.1.26,2022-01-20T17:42:29Z,2022-01-20T17:42:29Z,2022-01-20T17:42:29Z,"When I drag a file from phone through MTP accessed in KDE directly into an Ubuntu guest running the same operating system, VirtualBox crashes.",miklcct
20762,VM crash after KVMS switch,Linux,VirtualBox 6.1.30,2022-01-07T02:17:10Z,2022-01-07T02:17:10Z,2022-01-07T02:17:10Z,"See [https://forums.virtualbox.org/viewtopic.php?f=7&t=104891&sid=51cd5f0216603e8bec8562fd1da4b3bc] for more information.

Environment:

I have multiple PCs connected by a keyboard-video-mouse-switch (KVMS, to clearly distinguish from kvm, the kernel virtualization subsystem).  The KVMS is a FJGear USB2.0 HDMI KVM model FJ-401HUA.  I will refer to these PCs as A, B, and C.  All 3 boxes are hosting Devuan Beowulf, and all VMs running on all boxes are running Devuan Beowulf Ascii, Beowulf, or Chimaera under virtualbox 6.1.30.  All hosts are running the latest virtualbox extensions, and guests are running the latest virtualbox guest additions.

Description of the Problem:

The problem is that switching between two of these boxes causes a VM running USB 3 to crash.  After an initial switch from A to B and back to A, one VM running USB 3 on A had crashed.  In one instance, switching a second time after this from A to B and back to A, all but one VM running USB 3 had crashed and even a VM running USB 2 had also crashed.  

Detail:

I run virtualbox on PCs A and B.   I use PC A for most of my regular activities; B and C are ""test"" boxes.  However, despite B being a testbox, I do have the VMs on B networked together with some of the VMs on A.  The 3 PCs are networked through an electronic ethernet switch.

The KVMS does work, although there is a bit of a wait for the video to re-sync after a switch.   The KVMS is capable up to 1920x1080, which matches my monitor's resolution.   Normally, I don't notice any peculiar behavior related to using the manual buttons on the face of the unit.  There are some messages logged after each switch, but they have never caused an issue until I changed the VM (the one that crashed) to USB 3.

I have attached the log for the crashed VM (see above link).  These logs were created by saving them from the log dialog box in the virtualbox GUI.  I have not modified them other than to obfuscate private information.  The logs are cut short for some reason, but it is NOT related to the obfuscation script.  I can save the logs again, from the GUI again, and the same results occur.   The line counts of the log files match before and after obfuscation.


",Harry M
20718,Oracle Linux 8.2 Guest Mouse Pointer Integration Ubuntu 20.10 Host,Linux,VirtualBox 6.1.30,2021-12-09T15:28:43Z,2021-12-09T15:28:43Z,2021-12-09T15:28:43Z,The mouse does not work right inside Oracle Linux 8.2 guest in VirtualBox 6.1 latest on Ubuntu 20.10 host. The mouse exits before reaching margin of VM console which makes installer GUI buttons inside Oracle Linux 8.2 installer unclickable.,orabuntu
20669,Multicast originating from different subnet does not reach Guest only on Ubuntu(Linux?) Host,Linux,VirtualBox 6.1.28,2021-11-15T17:07:49Z,2021-11-17T19:07:55Z,2021-11-17T19:07:55Z,"Hello,

I have run into an issue that I now believe is a bug.

Basically, I am receiving status updates from various devices on the network in my VM. They use multicast on 224.0.0.50.
The devices are on a different subnet from the Host and the Guest (the host and the guest are on the same subnet), but everyone can communicate between each other just fine.
This works on Host Windows 10 but not on Host Ubuntu 18.04. 
Using Virtualbox 6.1.28. 

Also, tried:
- 6.1.26
- 6.1.29 revision 148164 test build
- 6.1.97 development revision 148162

All the above w/ extpack

The guest is using bridged networking.
On Windows it's using Intel PRO/1000 MT Desktop (82540EM). 
On the Ubuntu host I've tried them all with no luck.
On Windows promiscuous mode is set to Deny and greyed out, on the Ubuntu host I tried enabling it to Allow-All, no luck.

Both hosts receive the multicast packet (used wireshark on windows and tcpdump on linux to verify on both the hosts and the guests), but only on the Windows 10 host will it manage to be picked up by the Guest.
I'm attaching a screenshot from a packet capture from inside the Guest with Windows 10 as a host. These two packets are the expected behavior. On Ubuntu Host, only the first one (the direct reply) makes it all the way to the Guest. The multicast packet is lost.

It is worth mentioning that it's the exact same VM copied from Windows to Linux to make this test as good as possible.

Multicast packets originating from the same subnet are well-received.
I also tried mimicking network routes on the Ubuntu host as seen on the Windows host but to no avail.
I tried nuking the routes on the windows host to see if it affected the Windows Guest receiving it but it did not.
",idmistir
19340,VMSVGA does not allow to resize guest display in GNU/Linux,Linux,VirtualBox 6.1.4,2020-02-23T17:52:24Z,2021-11-16T18:20:47Z,2021-11-16T18:20:47Z,"In this case the host and guest are same OS: 64-bit Linux Mint 19.3 MATE.

This error has been since VMSVGA came out and it seems that this is still not fixed. So it is not just VirtualBox 6.1.4 issue but much older one and exist in many former VirtualBox versions.

Graphics controller in VirtualBox machine settings
* in case of GNU/Linux by default VMSVGA 
* in case of MS Windows by default VBoxSVGA

'''The truth is that VMSVGA does not allow to resize guest display in GNU/Linux.''' I have to adjust display settings manually in Linux in order to resize display.
When using VBoxSVGA then guest resizing works in GNU/Linux but ''Invalid settings detected'' message is shown in virtual machine (VM) settings that suggest to use VMSVGA unless I have reason to not use. Well - currently I have reason as VMSVGA does not work properly.

Also in case of VBoxSVGA the resizing clutter appears - I need to maximize VM window and back in order to get guest display resizing work properly. This has to be done after every time I wake up my laptop from sleep or start the VM first time.

At the same time in case of MS Windows the VBoxSVGA is chosen by default which works also in case of MS Windows. Actually when to choose VMSVGA in case of MS Windows then you cannot start VM as it is considered invalid setting. Well - no need as VBoxSVGA works.

My proposal: either get VMSVGA to work properly in case of any supported guest OS or remove it permanently from VirtualBox.",Edmund Laugasson
20131,rcu_sched detected stalls on CPUs/tasks: linux guest and host ?ryzen issue,Linux,VirtualBox 6.1.16,2021-01-17T18:39:22Z,2021-11-07T13:22:29Z,2021-11-07T13:22:29Z,"Linux debian guest on Debian host Virtualbox 6.1.16

Host: Linux  5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux  Debian 10
AMD Ryzen 9 3900X 12-Core 32Gb ram 

guest 4 cores, 4gb ram
dmesg:

[  225.539622] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  225.540724] rcu:     0-...!: (27 ticks this GP) idle=c50/0/0x0 softirq=2529/2                                                                                        530 fqs=0

[  225.541761] rcu:     1-...!: (0 ticks this GP) idle=ac8/0/0x0 softirq=2101/21                                                                                        01 fqs=0

[  225.542767] rcu:     3-...!: (26 ticks this GP) idle=99c/0/0x0 softirq=2173/2                                                                                        174 fqs=0

[  225.543767]  (detected by 2, t=5271 jiffies, g=2529, q=2)

[  225.543770] Sending NMI from CPU 2 to CPUs 0:

[  225.543825] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.544771] Sending NMI from CPU 2 to CPUs 1:

[  225.544797] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.545769] Sending NMI from CPU 2 to CPUs 3:

[  225.545796] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  225.546769] rcu: rcu_sched kthread starved for 5272 jiffies! g2529 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=1

[  225.547792] rcu: RCU grace-period kthread stack dump:

[  225.548812] rcu_sched       I    0    11      2 0x80004000

[  225.548816] Call Trace:

[  225.548836]  ? __schedule+0x2d8/0x760

[  225.548838]  ? __switch_to_asm+0x40/0x70

[  225.548840]  ? __switch_to_asm+0x40/0x70

[  225.548842]  schedule+0x4a/0xb0

[  225.548843]  schedule_timeout+0x15e/0x300

[  225.548850]  ? __next_timer_interrupt+0xd0/0xd0

[  225.548853]  rcu_gp_kthread+0x452/0x8d0

[  225.548864]  kthread+0xf9/0x130

[  225.548869]  ? kfree_call_rcu+0x10/0x10

[  225.548870]  ? kthread_park+0x90/0x90

[  225.548872]  ret_from_fork+0x22/0x40

[  285.421645] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  285.422242] rcu:     0-...!: (0 ticks this GP) idle=da0/0/0x0 softirq=2535/25                                                                                        35 fqs=0

[  285.422780] rcu:     1-...!: (37 ticks this GP) idle=d4c/0/0x0 softirq=2103/2                                                                                        103 fqs=0

[  285.423305] rcu:     3-...!: (46 ticks this GP) idle=b84/0/0x0 softirq=2178/2                                                                                        179 fqs=0

[  285.423815]  (detected by 2, t=5268 jiffies, g=2541, q=866)

[  285.423817] Sending NMI from CPU 2 to CPUs 0:

[  285.423858] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.424818] Sending NMI from CPU 2 to CPUs 1:

[  285.424845] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.425817] Sending NMI from CPU 2 to CPUs 3:

[  285.425847] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xe/0                                                                                        x10

[  285.426815] rcu: rcu_sched kthread starved for 5268 jiffies! g2541 f0x0 RCU_G                                                                                        P_WAIT_FQS(5) ->state=0x402 ->cpu=0

[  285.427228] rcu: RCU grace-period kthread stack dump:

[  285.427620] rcu_sched       I    0    11      2 0x80004000

[  285.427623] Call Trace:

[  285.427629]  ? __schedule+0x2d8/0x760

[  285.427630]  ? __switch_to_asm+0x40/0x70

[  285.427631]  ? __switch_to_asm+0x40/0x70

[  285.427633]  schedule+0x4a/0xb0

[  285.427634]  schedule_timeout+0x15e/0x300

[  285.427637]  ? __next_timer_interrupt+0xd0/0xd0

[  285.427640]  rcu_gp_kthread+0x452/0x8d0

[  285.427643]  kthread+0xf9/0x130

[  285.427645]  ? kfree_call_rcu+0x10/0x10

[  285.427647]  ? kthread_park+0x90/0x90

[  285.427648]  ret_from_fork+0x22/0x40

System is unusable.

Guest transferred from Intel i5 core system, were it worked perfectly.
Same error in Debian 9, 10 and bullseye guests.
Tried multiple combination of cores and ram - no effect.

Interestingly Alpine 3.12 guest on same system has no problem. 

Current workaround: install guest additions on guest and error messages go. 

I've attached the virtualbox logs.  host1 - is related to the dmesg output above.
host2 and host3 are logs from the same system, just running longer. 

Many thanks for your help.
",RT_db
20330,Pipewire audio server unusable,Linux,VirtualBox 6.1.20,2021-04-30T02:08:34Z,2021-10-25T09:43:20Z,2021-10-25T09:43:20Z,"GNOME 40 introduces a new sound server, Pipewire, to replace pulseaudio to control sound under Linux.

Fedora 34 makes Pipewire as default, while it has a pulseaudio module to maintain compatibility, VirtualBox can't play sound with Pipewire, and it affects video playback as well.

Under GNOME settings, there is a testing option under sound preferences, no sound is available in the test.

If there is a video in a web page, like YouTube, sometimes sound can play 2-3 seconds but then the video will be muted, and frames are freezed as well, not only sound is unavailable but the video is affcted as well.

I tried to remove Pipewire and install Pulseaudio, everything is ok and back to normal again.

As Pipewire introduces many new features and better integration in future Linux development, it would be important to fix this issue before pulseaudio is completely phased out (it may take 2-3 years though...).",Promet
20366,Shared clipboard stops working on vm reboot when started headless => Fixed in SVN,Linux,VirtualBox 6.1.22,2021-05-13T21:37:44Z,2021-10-15T08:49:38Z,2021-10-15T08:49:38Z,"my setup and testing:

Running Virtualbox 6.1.22 on Ubuntu Server 20.04 with extension pack.  Ubuntu is fully patched.  I connect via RDP to VM console.

If I start a VM headless, shared clipboard works without issues.  Once I reboot the VM, shared clipboard stops working.

I have tested a Windows 10 VM and Mint Mate VM and both have the same issue.

I tested the freerdp client (compiled the latest source) and the Microsoft RDP client and get the same results.


I also installed Mint Mate on my test PC, then VirtualBox on that, and get the same result if I start the vm using vboxheadless.

I have attached log file from a test vm.",thedisbo1125
20590,Guest window size decreases on login (Linux),Linux,VirtualBox 6.1.26,2021-10-01T20:18:32Z,2021-10-04T19:23:20Z,2021-10-04T19:23:20Z,"I had one OpenSuSE 15.2 guest machine unexpectedly go back to a resolution of 1024X768 after rebooting and logging in. I was able to click and drag the window to increase the display size to fix the issue.

Things that didn't work were:
using the display settings within the OS to set a resolution
Using the View menu to set Auto-resize Guest Display and then use the View menu to set the display size for Virtual Screen 1.
In both cases the screen would resize as expected but, after a reboot and logging in again the screen size would jump back to 2014X768. When 3D acceleration was turned off I could see that the screen size was initially at the selected size before jumping back to 1025X763. With 3D acceleration turned on I cannot see the jump.

3D acceleration was initially turned off. Turning it on didn't change the symptoms.
Using VMSVGA ",Patrick Headley
20552,VMSVGA extremely laggy keyboard input for Linux guests,Linux,VirtualBox 6.1.26,2021-09-16T11:20:30Z,2021-09-24T06:53:29Z,2021-09-24T06:53:29Z,"Pretty much all Linux guests with this video adapter have an extremely laggy and random keyboard input: while you're typing in any graphical terminal sometimes what you're typing instantly shows on the screen, sometimes there's a random delay for up to three seconds.

It's annoying and maddening.

Host OS: Fedora 33, Linux 5.14.3[[BR]]
Environment: XFCE with '''no''' compositing[[BR]]
CPU: Ryzen 7 5800X[[BR]]
Guest OS: any modern Linux OS without 3D acceleration

Changing the amount of video memory from default 16MB to 128MB makes the issue less pronounced but it's still there.

VBoxSVGA is more or less free from this issue. Keyboard input is not perfect (there's quite a considerable input lag) but at least it's not as bad as with VMSVGA.",Artem S. Tashkinov
20546,Guest suspended with DiskFull error when using fixed size VDI,Linux,VirtualBox 6.1.26,2021-09-13T21:58:24Z,2021-09-14T06:52:48Z,2021-09-14T06:52:48Z,"VirtualBox guest with fixed size VDI file is suspended when the host runs low on disk space.
Fixed size VDI files should never trigger a disk full condition as they are a fixed preallocated size that will never expand.

VirtualBox build 146314
Host: Fedora Linux 33
Guest Fedora Linux 34
Log File Info:
VD#1: Host disk full
VM: Raising runtime error 'DrvVD_DISKFULL' (fFlags=0x6)
Console: VM runtime error: fatal=false, errorID=DrvVD_DISKFULL message=""Host system reported disk full. VM execution is suspended. You can resume after freeing some space""

VBoxManage showmediuminfo disk ...
Storage format: VDI
Format variant: fixed default
Capacity:       66560 MBytes
Size on disk:   66562 MBytes",RP15873
14743,X11 guests: Invisible drag-and-drop window blocks mouse interaction,Linux,VirtualBox 5.1.6,2015-10-25T08:30:04Z,2021-08-13T05:36:14Z,2021-08-13T05:36:14Z,"I first noticed this in v5.0.6, but it just happened to me again in 5.0.8.  After several days of using a guest, all of a sudden mouse clicks no longer work.  Both left and right mouse clicks do nothing, as if the clicks are not making it to the guest.  Moving the mouse works.  Guest additions are installed.

When the clicks stop working, the mouse continues working correctly in the host and in other guests running on this host.

Rebooting the affected guest fixes the problem.

I looked through the log file, though I see nothing obvious.  In this case, the timestamps in the log indicate the guest was only running for 37 hours and 29 minutes.  I'd guess the problem started around 37 hours and 27 minutes.  I rebooted it a minute or so after it happened.",Stéphane Charette
20450,Ubuntu Linux host hissing audio after starting ubuntu server guest.,Linux,VirtualBox 6.1.22,2021-07-07T00:08:14Z,2021-07-07T00:08:14Z,2021-07-07T00:08:14Z,"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]",Carlos Henrique
20449,Ubuntu Linux host hissing audio after starting ubuntu server guest.,Linux,VirtualBox 6.1.22,2021-07-07T00:07:42Z,2021-07-07T00:07:42Z,2021-07-07T00:07:42Z,"Host - Ubuntu Desktop Linux 20.04.2 LTS amd64 
Guest - 20.04.02 Server Linux amd64

To stop the interference in the host machine's audio it is necessary to disable the audio in the guest (virtual machine).

Interferences were observed in Google Chrome and Mozilla Firefox browsers.


[[Image(https://i.stack.imgur.com/geK0R.png)]]",Carlos Henrique
20423,Oracle VirtualBox SharedClipboard Use After Free Vulnerability,Linux,VirtualBox 6.1.22,2021-06-17T03:14:59Z,2021-06-17T03:14:59Z,2021-06-17T03:14:59Z,"=  Oracle VirtualBox SharedClipboard Use After Free Vulnerability =



== Affected Software ==

Oracle VM VirtualBox 6.1.22



== Description of Vulnerability ==

This vulnerability allows guest VM to cause denial of service in the context of the host hypervisor. High privileged code on the target guest system is required to exploit this vulnerability. 



== Technical Details ==

VirtualBox provide a HostService named **""VBoxSharedClipboard""** to perform the operation of shared clipboard between Host and Guest. The guest sends the request through **HGCM (Host-Guest Communication Manager)**. The vulnerability is when guest quickly send `VMMDevReq_HGCMDisconnect` and `VMMDevReq_HGCMCall64` to the same service sequentially. That service will operate the `VMMDevReq_HGCMCall64` after the `VMMDevReq_HGCMDisconnect`. So `pvClient` the internal object used in service has been released when it perform disconnect function. But Later **HGCMCall** will use that freed object to operate guest requested function and cause use after free.

In code [1], it free the pCtx and later will be used in **HGCMCall**

`svcDisconnect` -> 
    `ShClSvcImplDisconnect`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
int ShClSvcImplDisconnect(PSHCLCLIENT pClient)
{
    LogFlowFuncEnter();

    PSHCLCONTEXT pCtx = pClient->State.pCtx;
    AssertPtr(pCtx);

    /* Drop the reference to the client, in case it is still there.  This
     * will cause any outstanding clipboard data requests from X11 to fail
     * immediately. */
    pCtx->fShuttingDown = true;

    int rc = ShClX11ThreadStop(&pCtx->X11);
    /** @todo handle this slightly more reasonably, or be really sure
     *        it won't go wrong. */
    AssertRC(rc);

    ShClX11Destroy(&pCtx->X11);
    RTCritSectDelete(&pCtx->CritSect);

    RTMemFree(pCtx); // code [1]

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}
}}}

When the guest send a `VBOX_SHCL_GUEST_FN_REPORT_FORMATS` request and guest's uMode is set to `VBOX_SHCL_MODE_BIDIRECTIONAL` or `VBOX_SHCL_MODE_GUEST_TO_HOST`
which is `not` default setting in code [2], it will perform the following function. In function `XtAppAddTimeOut`, it will get crashed.


{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C
static int shClSvcClientReportFormats(PSHCLCLIENT pClient, uint32_t cParms, VBOXHGCMSVCPARM paParms[])
{
    /*
     * Check if the service mode allows this operation and whether the guest is
     * supposed to be reading from the host.
     */
    uint32_t uMode = ShClSvcGetMode();
    if (   uMode == VBOX_SHCL_MODE_BIDIRECTIONAL //code [2]
        || uMode == VBOX_SHCL_MODE_GUEST_TO_HOST)
    { /* likely */ } 
    else
        return VERR_ACCESS_DENIED;
}}}
}}}

`svcCall` -> 
    `shClSvcClientReportFormats` -> 
        `ShClSvcImplFormatAnnounce` ->
            `ShClX11ReportFormatsToX11` ->
                `clipThreadScheduleCall` ->
                    `XtAppAddTimeOut` ->
                        `clipThreadScheduleCall`

{{{
#!div style=""font-size: 80%""
Code highlighting:
{{{#!C

static int clipThreadScheduleCall(PSHCLX11CTX pCtx,
                                  void (*proc)(void *, void *),
                                  void *client_data)
{
    LogFlowFunc((""proc=%p, client_data=%p\n"", proc, client_data));

#ifndef TESTCASE
    XtAppAddTimeOut(pCtx->pAppContext, 0, (XtTimerCallbackProc)proc,
                    (XtPointer)client_data);
    ssize_t cbWritten = write(pCtx->wakeupPipeWrite, WAKE_UP_STRING, WAKE_UP_STRING_LEN);
    Assert(cbWritten == WAKE_UP_STRING_LEN);

}}}
}}}


== The POC ==

The following are step by step guide for replicating the bug:
1. Upload the file `poc.c` and `internal.h` into the guest
2. Compile the poc by `gcc poc.c -o poc`
3. Run `poc` as root



== Requirements ==

* The Host OS must be Linux
* Attacker must be able to run **high-privileged** code on the guest
* The setting of Shared Clipboard need to be `Guest to Host` or `Bidirectional`",info_starlabs
20294,Virtual disk automatic resize/growth failing.,Linux,VirtualBox 6.1.18,2021-04-08T18:40:30Z,2021-05-19T16:55:55Z,2021-05-19T16:55:55Z,"Hi,

When the vitual hdd is defined during VM creation, I selected a dynamically allocated VDI. As far as I can tell, the size selected will be the maximum size of the hdd on the host and that less space will be allocated initially and extended as needed during guest operation. Correct?

My situation is a VM with a dynamically allocated hdd of 384GB. Right now it's at 45GB or so but is trying to extend the size. The guest is reporting disk problems and out of space problems and has now changed one partition to read only. What I think is happening is that the guest has a code path which Virtual Box intercepts, does some magic to add space, restart the operation. This is apparently NOT happening. The path through Virtual Box may or may not be trying to handle this situation but then appears to let the error(s) continue through the guest OS (5.12.0-0.rc5.180.fc35.x86_64).

Here's what the host thinks of the partition where the VDI is located:

{{{
Filesystem                         1K-blocks        Used   Available  Really_Available Use% Mount_Point
/dev/sda8                         1735405656   485065980  1250569508        1250339676  28% /export/home
}}}

The guest thinks it's VDI is:

{{{
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2        1992552   164592   1706720   9% /
/dev/sda7       65478188 14001584  48104780  23% /usr
/dev/sda1        1992552   149816   1721496   9% /boot
/dev/sda8      184666464 19495796 155717356  12% /export/home
/dev/sda5       65478188   751092  61355272   2% /var
/dev/sda6       65478188   936844  61169520   2% /opt
}}}

Which is considerably less than 384GB.

Additionally, the guest is throwing numerous messages like these:

{{{
[   23.180382] 06:32:17.603879 main     VBoxService 6.1.18_Fedora r142142 (verbosity: 0) linux.amd64 (Mar  2 2021 00:00:00
) release log
               06:32:
[   23.184678] 06:32:17.610514 main     OS Product: Linux
[   23.189518] 06:32:17.614980 main     OS Release: 5.12.0-0.rc5.180.fc35.x86_64
[   23.192546] 06:32:17.617869 main     OS Version: #1 SMP Mon Mar 29 15:30:36 UTC 2021
[   23.197236] 06:32:17.620938 main     Executable: /usr/sbin/VBoxService
               06:32:17.620942 main     Process ID: 591
               06:32:17.620944 main     Pa
[   23.202542] 06:32:17.628117 main     6.1.18_Fedora r142142 started. Verbose level = 0
[   23.208141] 06:32:17.633605 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[   40.487920] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   40.488885] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
[ 7841.824091] systemd[1]: systemd v248-1.fc35 running in system mode. (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOM
P +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQU
ALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 7841.825374] systemd[1]: Detected virtualization oracle.
[ 7841.825631] systemd[1]: Detected architecture x86-64.
[ 7872.660143] ata1.00: exception Emask 0x0 SAct 0x1ffff800 SErr 0x0 action 0x6 frozen
[ 7872.661528] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.662445] ata1.00: cmd 61/00:58:c8:89:2b/0a:00:12:00:00/40 tag 11 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.664910] ata1.00: status: { DRDY }
[ 7872.665671] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.666963] ata1.00: cmd 61/00:60:c8:93:2b/0a:00:12:00:00/40 tag 12 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}


and:

{{{
[ 7872.721207] ata1.00: status: { DRDY }
[ 7872.721577] ata1.00: failed command: READ FPDMA QUEUED
[ 7872.722023] ata1.00: cmd 60/08:e0:10:7a:0d/00:00:17:00:00/40 tag 28 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.723230] ata1.00: status: { DRDY }
[ 7872.723607] ata1: hard resetting link
[ 7873.036871] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7873.038028] ata1.00: configured for UDMA/133
[ 7873.038418] ata1.00: device reported invalid CHS sector 0
[ 7873.038850] ata1.00: device reported invalid CHS sector 0
[ 7873.039295] ata1.00: device reported invalid CHS sector 0
[ 7873.039725] ata1.00: device reported invalid CHS sector 0
[ 7873.040250] ata1.00: device reported invalid CHS sector 0
[ 7873.040691] ata1.00: device reported invalid CHS sector 0
[ 7873.041133] ata1.00: device reported invalid CHS sector 0
[ 7873.041646] ata1.00: device reported invalid CHS sector 0
}}}


and:

{{{
[49175.522760] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621957, error -30)
[49175.526567] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621958, error -30)
[49175.530010] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621961, error -30)
}}}

Of course there are more of all of these messages available in a file. I'm not sure how I would attach a file to this mailing list though.

Can someone take a look at all this and render some assistance please?

Best regards,

George...



VirtualBox Graphical User Interface

Version 6.1.19 r143581 (Qt5.6.1)",George R. Goffe
19641,Assigning more vCPU (within the physical core limits) causes random freezes on guests,Linux,VirtualBox 6.1.8,2020-06-07T04:04:45Z,2021-05-19T05:19:07Z,2021-05-19T05:19:07Z,"'''Host Info'''
-------------------
Host: Fedora 32 (64 bit)[[BR]]

CPU: Intel® Core™ i9-9880H CPU @ 2.30GHz × 8 Cores[[BR]]

GPU: Intel UHD-630[[BR]]

HyperThreading: Disabled[[BR]]

Physical Cores: 8[[BR]]

VirtualBox Version: 6.1.8[[BR]]

Display Protocol: X11[[BR]]



'''Guest Info'''
------------------------------
Guest: Debian 10 (Kernel 4.19.0-9-amd64) (Also reproducible in Kubuntu 20.04)[[BR]]

Display Adapter: VMSVGA[[BR]]

3D Acceleration: Enabled[[BR]]

VBox Guest Additions: Installed[[BR]]


----

When I assign 4 cores to the guest, on random starts the guest's animation and scrolling lags. When I checked the Session Information it showed Guest Load about ~0-1% and VMM Load about ~25%. The next restart of the guest doesn't have this behavior. Guest is smooth and doesn't cause pauses.[[BR]]


I tried changing few settings to find the root cause of the issue and surprisingly reducing the CPU count to 1 or 2 fixes the issue. The issue was not reproducible at all.
",LienCaspari
20365,Linux guest won't boot unless hard disk is set as the priority,Linux,VirtualBox 6.1.22,2021-05-13T19:11:02Z,2021-05-14T10:33:56Z,2021-05-14T10:33:56Z,"After installing the latest CentOS 7.8
The OS refuses to boot unless the boot order for the VM is specifically changed so that the VM boots from the disk first.
If I set the boot order to something else (for example network for IPXE testing),the operating system instead shows an error ""fatal: int18: BOOT FAILURE"".
Most of what I found online talks about installing the disk in GPT vs MBR, but that shouldn't have much bearing since I know I installed the VM as MBR. None the less, I still tried to change the VM to UEFI since that is what the online community instructs.  However, no effect was detected besides the VM booting into the UEFI shell. However, if the boot order for the VM is changed, even though the other boot options are not being used and the option for disk is eventually reached, the boot option for the disk will eventually show the error.

",Rusty_Almighty
20280,Memory Leak in vboxdrv,Linux,VirtualBox 6.1.18,2021-03-30T17:30:41Z,2021-05-11T12:22:45Z,2021-05-11T12:22:45Z,"I detected a small memory leak in the openSUSE version that I maintain. To see if the problem had been fixed, I installed test build revision 143492. It has the same problem.

The kmemleak report is as follows:


{{{

localhost:cat > /sys/kernel/debug/kmemleak
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 94.516s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b600 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
unreferenced object 0xffff88827c95b680 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918412 (age 94.496s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] rtR0MemAllocEx+0xc5/0x130 [vboxdrv]
    [<00000000064e6217>] VBoxHost_RTMemAllocZTag+0x2a/0x70 [vboxdrv]
    [<00000000523d21fa>] rtR0MemObjNew+0x37/0x70 [vboxdrv]
    [<00000000df0eec39>] rtR0MemObjNativeMapKernel+0x57/0x140 [vboxdrv]
    [<000000008419dc13>] VBoxHost_RTR0MemObjMapKernelExTag+0x12d/0x1f0 [vboxdrv]
    [<00000000ec3fe3f7>] SUPR0PageMapKernel+0x1e2/0x270 [vboxdrv]
localhost:~ # 
}}}

To trigger this leak, load the GUI, start and stop a VM, and then close the GUI. Until the final step, the kmemleak scan is clean. Note, this is a real leak. If vboxdrv is unloaded, the backtrace info is lost. The first leaked block is reported as:

{{{
unreferenced object 0xffff88827c95b380 (size 128):
  comm ""EMT-0"", pid 4550, jiffies 4294918407 (age 1095.172s)
  hex dump (first 32 bytes):
    19 01 09 18 01 00 00 80 58 00 00 00 58 00 00 00  ........X...X...
    10 12 61 19 58 00 00 00 08 00 00 00 00 00 00 00  ..a.X...........
  backtrace:
    [<000000008fe681f2>] 0xffffffffa0c9fb05
    [<00000000064e6217>] 0xffffffffa0c9d82a
    [<00000000523d21fa>] 0xffffffffa0c9edd7
    [<00000000df0eec39>] 0xffffffffa0ca1067
    [<000000008419dc13>] 0xffffffffa0c9e55d
    [<00000000ec3fe3f7>] 0xffffffffa0c8c1b2

}}}

",Larry Finger
20337,Natnetwork loose connectivity after a while,Linux,VirtualBox 6.1.22,2021-05-04T08:29:04Z,2021-05-04T08:29:04Z,2021-05-04T08:29:04Z,"Hi,
I have created 5 VMs based on Debian 10, with Natnetwork configured (because i need to let the VMs talk to each others and access the Vpn on the host).

Each one has static IP, no specific tunning or special configuration. just Debian Vms and default natnetwork configured.

All Vms are working without any problems, i can access it with port forwarding. and after a while (one minute, 3 minutes...), the IP connectivity is suddenly cut, the ssh connections are stuck !

I must restart the natnetwork with VBoxManage ... Same result with paravirtualized network interface or Intel Pro desktop.
So, it s impossible to work in theses conditions.

it seems that problem exists for years or i missed something ?

Thanks to do something on that issue.
Francois




",Francois94130
20154,Segmentation fault when running 5.10.x kernel as guest,Linux,VirtualBox 6.1.18,2021-01-25T14:22:00Z,2021-04-30T15:42:33Z,2021-04-30T15:42:33Z,"Running an up to date Ubuntu 20.04 as a guest upgraded to use the 5.10.9 Linux kernel using the instructions contained here as a guide.

Installed  VBoxGuestAdditions-6.1.18 which installed successfully.

Rebooted. Reboot fails  with segmentation fault.

",Alex Kempshall
10031,High I/O causing filesystem corruption,Linux,VirtualBox 4.1.4,2011-12-15T18:30:45Z,2021-04-22T15:10:32Z,2021-04-22T15:10:32Z,"Hello,
We are running an Ubuntu 10.04 32bit guest on a RHEL 64 bit host. The guest storage control is SATA AHCI with host I/O caching enabled. 
Host info:
OS Type:	Linux (2.6.18-194.el5)
VirtualBox:	4.1.4 (74291)
Processors:	Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2)
HWVirtEx, PAE, Long Mode (64-bit)

It seems during times of high I/O, like backups and etc, the guest filesystem resets to read-only. We have this issue with both ext3 and ext4 filesystems. Switching to ext3 seemed to lessen the occurrences though.

Here is a snip of syslog around the time of the corruption..


{{{
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:29 vault kernel: [ 2338.011698] ata4.00: exception Emask 0x0 SAct 0xffff SErr 0x0 action 0x6 frozen
Dec 15 08:02:29 vault kernel: [ 2338.011714] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011721] ata4.00: cmd 61/00:00:b7:5c:9d/04:00:09:00:00/40 tag 0 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011723]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011726] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011729] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011736] ata4.00: cmd 61/00:08:77:31:9d/04:00:09:00:00/40 tag 1 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011737]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011740] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011743] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011749] ata4.00: cmd 61/00:10:77:35:9d/04:00:09:00:00/40 tag 2 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011751]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}
And then later on in the file....
{{{
Dec 15 08:02:29 vault kernel: [ 2338.011969] ata4: hard resetting link
Dec 15 08:02:29 vault kernel: [ 2338.332268] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 15 08:02:33 vault kernel: [ 2342.108804] ata4.00: configured for UDMA/133
Dec 15 08:02:33 vault kernel: [ 2342.108811] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108815] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108818] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108820] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108823] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108826] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108829] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108831] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108834] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108837] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108840] ata4.00: device reported invalid CHS sector 0
}}}

At this point the guest needs to be shut down and the drive mounted and fsck, which complains about allot of IO handle stuff.",Indigo42
20302,Client ID prevails over MAC based mapping with the NAT Network DHCP server,Linux,VirtualBox 6.1.18,2021-04-13T09:35:05Z,2021-04-22T14:00:30Z,2021-04-22T14:00:30Z,"I've got two Ubuntu (though what matters here is Systemd-Network) guest VMs connected to a NAT Service network with the DHCP service enabled.
I have added a static mapping between the guests NIC MAC addresses and their assigned IPs. The NatNetwork-Dhcpd.config file shows what I mean:

    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

The same information is reflected in `VirtualBox.xml` (the global config file) though when using `VBoxManage` to set up the mapping I did use the first NIC of each guest to set the mapping hence the `/0` after the guest VM UUID:


    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

Now it comes the twist: DHCP Client ID in machines running Systemd-Network use /etc/machine-id to construct it but both machines have the same contents (due to cloning, you know) in this file hence the Client ID sent to the DHCP is always the same (as seen in NatService-Dhcpd.log)... and the dhcp server in the Nat Service returns the same IP address for both guests.

Is it a bug, a feature or just RFC compliance?
Thanks in advance.",jcb
20312,Machine does not terminate: VBOX_E_INVALID_VM_STATE (0x80BB0002),Linux,VirtualBox 6.1.20,2021-04-22T05:33:58Z,2021-04-22T05:33:58Z,2021-04-22T05:33:58Z,"Invalid machine state: Stopping.


Fehlercode: 
VBOX_E_INVALID_VM_STATE (0x80BB0002)
Komponente: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Log attached

Issue first occured today, with VirtualBox 6.1.20",Thermi
19824,Guru Meditation (tripple fault) while using GNS3,Linux,VirtualBox 6.1.10,2020-08-20T17:37:56Z,2021-04-21T11:07:18Z,2021-04-21T11:07:18Z,"Hello,

I'm using gns3 VM, which launches QEMU VMs, inside virtualbox 6.1.12 (this bugtracker is still missing that version). Today, I got a VINF_EM_TRIPLE_FAULT

I'll attach VBox.log",Luiz Angelo Daros de Luca
20308,vboxsf module (GA 6.0.24) fails to compile on latest ubuntu-16.04 kernel,Linux,VirtualBox 6.0.22,2021-04-20T17:48:10Z,2021-04-20T18:32:33Z,2021-04-20T18:32:33Z,"Attempting to build the vboxsf module for Guest Additions 6.0.24 fails on the latest ubuntu-16.04 kernel (`4.4.0-209-generic #241`).
{{{
vagrant@ubuntu-16:~$ uname -a
Linux ubuntu-16 4.4.0-209-generic #241-Ubuntu SMP Tue Apr 13 01:06:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
}}}

Snipped output from attempting to build the module manually with `build_in_tmp` (full log attached):
{{{
=== Building 'vboxsf' module ===
make[1]: Entering directory '/tmp/vbox.0/vboxsf'
make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/4.4.0-209-generic/build M=/tmp/vbox.0/vboxsf SRCROOT=/tmp/vbox.0/vboxsf -j2 modules
make[2]: Entering directory '/tmp/vbox.0/vboxsf'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /tmp/vbox.0/vboxsf/vfsmod.o
  CC [M]  /tmp/vbox.0/vboxsf/dirops.o
  CC [M]  /tmp/vbox.0/vboxsf/lnkops.o
  CC [M]  /tmp/vbox.0/vboxsf/regops.o
  CC [M]  /tmp/vbox.0/vboxsf/utils.o
/tmp/vbox.0/vboxsf/utils.c: In function 'vbsf_inode_setattr':
/tmp/vbox.0/vboxsf/utils.c:812:10: error: implicit declaration of function 'inode_change_ok' [-Werror=implicit-function-declaration]
     rc = inode_change_ok(pInode, iattr);
          ^
cc1: some warnings being treated as errors
scripts/Makefile.build:288: recipe for target '/tmp/vbox.0/vboxsf/utils.o' failed
make[3]: *** [/tmp/vbox.0/vboxsf/utils.o] Error 1
make[3]: *** Waiting for unfinished jobs....
Makefile:1472: recipe for target '_module_/tmp/vbox.0/vboxsf' failed
make[2]: *** [_module_/tmp/vbox.0/vboxsf] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-209-generic'
/tmp/vbox.0/vboxsf/Makefile-footer.gmk:117: recipe for target 'vboxsf' failed
make[1]: *** [vboxsf] Error 2
make[1]: Leaving directory '/tmp/vbox.0/vboxsf'
Makefile:48: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 1
}}}

It looks like a recent kernel update (https://ubuntu.com/security/notices/USN-4916-1) involving some CVE fixes also backported the migration from `inode_change_ok` to `setattr_prepare`.
That migration has previously broken Guest Addition compilation at least a couple times for other distros (https://www.virtualbox.org/ticket/17299, https://www.virtualbox.org/ticket/18697).
There are some existing IFDEFs in `VBox/Additions/linux/sharedfolders/utils.c` related to those previous issues:
{{{
#if (RTLNX_VER_RANGE(3,16,39,  3,17,0)) || RTLNX_VER_MIN(4,9,0) || (RTLNX_VER_RANGE(4,1,37,  4,2,0))
# if RTLNX_VER_MIN(5,12,0)
    rc = setattr_prepare(ns, dentry, iattr);
# else
    rc = setattr_prepare(dentry, iattr);
# endif
#else
    rc = inode_change_ok(pInode, iattr);
#endif
}}}
but they don't cover this case yet since it's a 4.4.0 series kernel.
",jonahbull
20296,vbox 6.1.18: virt-install cause vm crash (guru meditation),Linux,VirtualBox 6.1.18,2021-04-09T10:01:26Z,2021-04-09T12:23:55Z,2021-04-09T12:23:55Z,"I met a critical vbox error that I would like to report.

I reproduced this problem on 2 different vbox hypervisors.

== Facts ==
* hypervisor is running ubuntu 20.04 LTS (up to date) + vbox 6.1.18
* nested vt-x is enabled
* guest is running ubuntu 20.04 LTS (up to date, installed manually from ubuntu-20.04.2.0-desktop-amd64.iso)
* guest is running qemu/kvm (installed from ubuntu distro)

== Reproducer ==
* apt install qemu-kvm virtinst virt-manager libguestfs-tools bridge-utils
* cd /tmp && wget https://dl-cdn.alpinelinux.org/alpine/v3.13/releases/x86_64/alpine-standard-3.13.4-x86_64.iso
* virt-install --connect qemu:///system --virt-type kvm --name alpine --ram 512  --vcpus 1  --disk path=/dev/vmvg/vm --cdrom=/tmp/alpine-standard-3.13.4-x86_64.iso --network none --graphics none --arch x86_64 --os-type=generic --cpu host --noautoconsole
",Arnaud Veron
20288,absurd delay to start virtualization,Linux,VirtualBox 6.1.18,2021-04-04T13:41:19Z,2021-04-04T13:41:19Z,2021-04-04T13:41:19Z,"I tried in many ways to correct this, I installed medications (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)

and also a distribution pack that I use (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1) .deb)

And so far nothing, I use the Linux of the offensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b) image ready.


I start the machine and leave the computer on, and it went 28 hours without leaving the black screen with the kali logo
",anjo gelado
20286,máquina demorando para iniciar,Linux,VirtualBox 6.1.18,2021-04-04T01:18:53Z,2021-04-04T01:58:10Z,2021-04-04T01:58:10Z,"já tentei de varias formas corrigir isso, instalei extensões (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)
 e também pack pra distribuição a qual eu uso (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1).deb)

 E ate agora nada, uso o Linux da ofensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b)
 imagem pronta.
[[BR]]
 Inicio a maquina e deixo o computador ligado, e ela varou  passou 28 horas sem sair da tela preta com a logo do kali ",anjo gelado
20277,VirtualBox 6.1.18 freezes when trying to start a Ubuntu installation from CD image,Linux,VirtualBox 6.1.18,2021-03-27T12:01:51Z,2021-03-29T05:33:31Z,2021-03-29T05:33:31Z,"Host:

vbox-cloud ➤ uname -a                                                          
Linux paag-EliteBook 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox:

vbox-cloud ➤ vboxmanage --version                                              
6.1.16r140961

How to reproduce the *freeze*:

Define a VM with 4G RAM, 40G HDD (in fact anything that can run Ubuntu 20.04)
Define the VM to run with 2 vcpus (this is the critical stuff)
Attach the Ubuntu 20.04 live image to the CDROM in the VM
Boot the VM and watch it freeze VirtualBox
",paaguti-u
19908,Mouse not working in Virtualbox 6.1.14 with Arch Linux as Host,Linux,VirtualBox 6.1.14,2020-09-22T14:38:36Z,2021-03-24T19:25:54Z,2021-03-24T19:25:54Z,"I installed Kali Linux as Guest OS while the Host OS is Arch Linux. Whenever I go to Full-screen mode and return back to normal screen mode, the Mouse/Touchpad click is not working. I can move the cursor, but cannot click/tap or scroll through anything in both Guest OS (Kali) and Host OS (Arch).

Steps to Reproduce:
1. Install Kali Linux as Guest and fully update the Guest OS.
2. Reboot the VM.
3. Switch to full screen mode with Host+F.
4. Again, switch to normal screen mode with Host+F.
5. Now, the mouse/touchpad stops working except moving the cursor in both Host(Arch) and Guest(Kali) OSs

This steps to reproduce fail rarely, but I can assure you it happens randomly each time when you stat up the VM and surf a bit.

When I shutdown my Guest(Kali) VM, then the mouse/touchpad operates normally as before.

My Laptop Specs:
Lenovo L340-15IWL
Intel i5-8265U
8GB DDR4 RAM
Intel UHD Graphics 620",404_vip_not_found
14842,Converting OVA-deployed machine to EFI gives Error: No mapping found.,Linux,VirtualBox 5.0.10,2015-11-18T14:10:02Z,2021-03-19T19:54:16Z,2021-03-19T19:54:16Z,"I'm generating OVA template which is intended to be tested for BIOS and UEFI boot capabilities. There is no problem with regular workflow, deploy machine, turn it on and continue with BIOS boot. But once I've turned on ""Enable EFI"" options in deployed machine settings I've got error from UEFI interactive shell - Error: No mapping found. It seems VirtualBox doesn't generate UEFI default boot entries for OVA-deployed instance. Could it be fixed?",Roman Valov
19956,Disk booting no longer works automatically on EFI system after cdrom is removed,Linux,VirtualBox 6.1.14,2020-10-10T18:31:05Z,2021-03-19T19:45:35Z,2021-03-19T19:45:35Z,"I am able to install devuan 32 bit and 64 bit to respective EFI VMs.  This involves navigating the UI and possibly booting from the EFI shell to coerce vbox to boot the install media.  However, after the install is complete, vbox correctly boots to the grub menu the installation media installed.

A problem arises, however, if I insert any arbitrary CD into the cdrom device.  Any attempt to boot off the CD requires navigating the UI again, and in most cases, requires booting from the EFI shell no matter what combination of options I select (such as deleting all but the Cdrom from the boot options and even changing the boot order).  There does not seem to be any way to get vbox to boot off the hard drive after a cd has been inserted and removed.

This behavior appears to be consistent across 32 and 64 bit EFI VMs.

Steps to reproduce:

* Create new EFI VM
* launch installer CD (most likely from EFI Shell, since vbox won't launch the CD automatically)
* complete the install and reboot from hard drive
* insert any CD into the drive
* attempt reboot
* remove the CD from the drive
* attempt to reboot from hard drive again

Expected Results:

VM will return to booting from the hard drive without needing to do anything; the grub menu will appear as normal.

Actual Results:

If the scenario is reproduced, vbox will not boot off the hard drive by itself.  It will be necessary to launch from navigating and selecting via the UI or by using the EFI shell",Harry M
19211,Guest won't boot in EFI mode after deleting/adding main disk file,Linux,VirtualBox 6.1.0,2020-01-08T16:50:31Z,2021-03-18T09:26:14Z,2021-03-18T09:26:14Z,"Setup:
2 VDI disks.
EFI mode enabled (the main disk can only boot in EFI mode).
Hard disk as first device in System/Boot order VM settings.
Regular rebuild of disk images: regular re-add of those images in the storage settings.

After update to VBox 6.1.0, we encountered a bug where after removing and re-adding the bootable media (VDI disk) from the VM storage settings, it won't be able to boot anymore.

It tries to boot in PXE mode and drops into an EFI shell after some time.
I can boot by running the bootx64.efi executable from the shell.

When entering the bios/uefi menu (after exiting EFI shell), we can see that the disk is not in the boot options anymore, there are only PXE and EFI shell.

Reverting to 6.0.14 make it works as expected (boot correctly after disk change).",vclement
20223,Linux/64bit host XMM register usage in kernel randomly crashes Linux guest,Linux,VirtualBox 6.1.16,2021-02-24T18:57:46Z,2021-02-24T18:57:46Z,2021-02-24T18:57:46Z,"'''Synopsis:''' src/VBox/VMM/Makefile.kmk 'knows' flag VBOX_WITH_KERNEL_USING_XMM, which is added for Windows/64bit builds only.
Problem is that Linux kernel DOES MAKE USE of XMM registers, too. Examples include aes-ni kernel module (AES-NI instructions implicitly use XMM0..15) or RAID, respectively).
VMM at ring 0 only implements XMM wrappers for Windows/64bit and does not have conditionals to abort build if VBOX_WITH_KERNEL_USING_XMM is set in src/VBox/VMM/Makefile.kmk for linux.amd64. This yields a kernel panic because Microsoft ABI is completely different from System V ABI (aka gcc ABI).
The 6.1.18 trunk seems to rely on a complete rewrite of src/VBox/VMM/VMMR0/HMR0A.asm but 6.1.13 / 6.1.16 (6.0 also) still have this problem.

'''Solution is:'''

a) Add VBOX_WITH_KERNEL_USING_XMM to src/VBox/VMM/Makefile.kmk for linux.amd64


b) Provide conditional implementation in src/VBox/VMM/VMMR0/HMR0A.asm for gcc/amd64 expecting function parameters in System V ABI registers rdi, rsi, rdx, rcx, r8, and r9. The two wrappers hmR0VMXStartVMWrapXMM and hmR0SVMRunWrapXMM need this.


c) calling CPUMIsGuestFPUStateActive from yasm assembler to C++ requires suffix ""wrt ..plt""

I have patches for this but optimized only for ""my"" Intel CPU. VBox users either have to switch to 6.1.18 or apply the above mentioned modifications.

'''Recommendation:'''

VBOX maintainers should think about making VBOX_WITH_KERNEL_USING_XMM the default for Linux, too (because of possible AES-NI or RAID usage, respectively).",vboxcomapijunkie
20000,Linux guests lock up with Host I/O cache disabled (NVMe and SATA),Linux,VirtualBox 6.1.14,2020-10-26T15:57:22Z,2021-02-23T21:37:44Z,2021-02-23T21:37:44Z,"I have been finding that Linux guests seem to lock up when Host I/O cache is disabled when disks are under load (for example when installing system updates). dmesg also shows disk timeouts, and it seems no further disk operations succeed after this point without killing the VM process and restarting.

A log is attached. I'm not sure how to reproduce this reliably, but it seems to happen when I'm installing updates. I have seen this with both Ubuntu and Fedora guests. I will also upload a screenshot shortly with the exact messages, but I seem to have misplaced it for the moment.

I should also note that this is with the VDI nonrotational option turned on and discard=on in the guest Linux OS.

Anything else I can do to help diagnose?",Hamish McIntyre-Bhatty
20196,Error while using VirtioSCSI through vboxwebsrv (Invalid controller type 11 (0x80070057)),Linux,VirtualBox 6.1.18,2021-02-16T09:30:51Z,2021-02-16T10:52:37Z,2021-02-16T10:52:37Z,"Since the lsilogic SCSI controller intermittently crashes with kernel panic, we've tried switching to the new Virtio SCSI controller. 

However, while attempting to use the Java SDK to select this controller through vboxwebsrv, we get an error. This seems to be related to using vboxwebsrv, as selecting the virtio-scsi controller in the UI of Virtualbox or vboxmanage works as expected.

Since the virtio scsi controller is new in 6.1, we suspect that vboxwebsrv has not been modified to accept/handle the new controller type, but we can't be sure.

The error we get back is
{{{
VirtualBox error: rc=0x80070057 Invalid controller type 11 (0x80070057)
}}}

The Java code is:

{{{
IAppliance ova = vbox.createAppliance();
waitFor(ova.read(ovaName));
ova.interpret();
waitFor(ova.importMachines(List.of(ImportOptions.ImportToVDI)));
machine = vbox.findMachine(ova.getMachines().get(0));
ISession session = manager.getSessionObject();
machine.lockMachine(session, LockType.Write);
IStorageController storage = session.getMachine().getStorageControllers().get(0);
storage.setControllerType(StorageControllerType.VirtioSCSI);
session.getMachine().saveSettings();
}}}

The error happens on the line
{{{
storage.setControllerType(StorageControllerType.VirtioSCSI);
}}}

The vboxwebsrv log says:
{{{
00:00:37.787184 SQW01    -- entering __vbox__IStorageController_USCOREsetControllerType
00:00:37.787195 SQW01       findRefFromId(): looking up objref 97ccd3f131838cc7-0000000000000009
00:00:37.787200 SQW01       findComPtrFromId(): returning original IStorageController*=0x7FE6E8004570 (IUnknown*=0x7FE6E80046C0)
00:00:37.787203 SQW01       calling COM method COMSETTER(ControllerType)
00:00:37.787418 main     Pumping COM event queue
00:00:37.787613 main     Pumping COM event queue
00:00:37.787965 main     Pumping COM event queue
00:00:37.788172 main     Pumping COM event queue
00:00:37.788311 main     Pumping COM event queue
00:00:37.788450 main     Pumping COM event queue
00:00:37.788535 main     Pumping COM event queue
00:00:37.788619 main     Pumping COM event queue
00:00:37.788701 main     Pumping COM event queue
00:00:37.788762 SQW01       error, raising SOAP exception
00:00:37.788766 SQW01    API method name:            IStorageController::COMSETTER(ControllerType)
00:00:37.788767 SQW01    API return code:            0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788776 SQW01    COM error info result code: 0x80070057 (NS_ERROR_INVALID_ARG)
00:00:37.788777 SQW01    COM error info text:        Invalid controller type 11
00:00:37.788840 main     Pumping COM event queue
00:00:37.788896 main     Pumping COM event queue
00:00:37.788899 SQW01       * ManagedObjectRef: MOR created for IVirtualBoxErrorInfo*=0x007fe6e8005070 (IUnknown*=0x007fe6e8007560; COM refcount now 4/2), new ID is 0xa; now 10 objects total
00:00:37.788906 SQW01    -- leaving __vbox__IStorageController_USCOREsetControllerType, rc: 0x80070057 (-2147024809)
}}}

Installed vboxwebsrv:
{{{
VirtualBox web service 6.1.18 r142142 linux.amd64 (Jan  7 2021 17:47:09) release log
}}}
",haster
19442,Autoformat pasted MAC address on adapter configuration dialog,Linux,VirtualBox 6.1.4,2020-03-28T08:15:33Z,2021-02-16T00:58:27Z,2021-02-16T00:58:27Z,"For my home lab, I usually use the same MAC addresses for creating my VMs after reinstalling the host (bridged adapters)

To set the VMs up faster, I want to be able to copy-paste that information from my static DHCP config file to the MAC address field. The format in the DHCP config file is like AA:BB:CC:DD:EE:FF but VBox does not accept the "":"" character. When pasting such a string with CTRL+V into the MAC address field, it should accept the string and automatically remove the "":"" characters",prischnikov
20108,Strange freeze in Linux host,Linux,VirtualBox 6.1.16,2020-12-30T08:36:15Z,2021-02-12T15:41:47Z,2021-02-12T15:41:47Z,"I get a repeatable hang of the VM and the GUI with the following sequence:

1.- get https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.vmdk

2.- Create a new VM, 4G of RAM, the vmdk disk and _2_ vCPUs

3.- Start the VM

At one point in the boot process, the VM will stop producing output and when you try to stop it, the GUI will get blocked.

In parallel, I'm investigating why I can't assign 2 vCPUs to the VM using this image, but I'm worried that I can't just kill the VM and that the GUI gets blocked when I try so.

For the host:

uname -a                                                          
Linux paag-EliteBook 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
",paaguti-u
19989,VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33,Linux,VirtualBox 6.1.16,2020-10-22T01:16:38Z,2021-02-03T20:19:45Z,2021-02-03T20:19:45Z,"VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33 with following error:

Erreur : 
 Problème: conflicting requests
  - nothing provides python(abi) = 3.8 needed by VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64


Test build VirtualBox-6.1.15-140899-Linux_amd64.run installs and works fine on Fedora 33.",Didier
19269,Hard Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Linux,VirtualBox 6.1.2,2020-01-26T14:09:11Z,2021-02-02T03:03:30Z,2021-02-02T03:03:30Z,"Upgrading a fedora 28 guest to 31, at the reboot I get a guru
meditation fault.

It seems to be reproducible.

Initially, I was running VirtualBox 5.2.20 r125813 linux.amd64 (Oct 15 2018 17:11:04).
The fault is ""VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)""

I removed VirtualBox from the host and installed VirtualBox to 6.1.2 r135662 linux.amd64 (Jan 13 2020 12:43:05) and its extension pack.
I then attempted to boot the guest.

The fault is ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""

The host is Fedora 28 - the details are in your logs, attached.

I did not attach the .PNG files because they consist of (only) a black screen.

However, prior to that, I do see the splash screen, ""Welcome to Grub"",
then the crash.  I use a detachable start - but a ""normal"" start has
the same symptom.

This is a ""hard"" failure - every time I try to start this machine.


Both versions of VirtualBox were installed from download.virtualbox.org/virtualbox/rpm/fedora

I do not plan to revert to VirtualBox 5.*...
",Timothe Litt
18477,Request for VBox to pass through Speculative Store Bypass (SSB) mitigations to guest => duplicate of #17987,Linux,VirtualBox 6.0.4,2019-03-06T08:37:25Z,2021-02-01T15:42:31Z,2021-02-01T15:42:31Z,"Hi,

Using Host VirtualBox 6.0.4 on CentOS 7.6.

Guest also CentOS 7.6

On the Host

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp

but inside the Virtual Machine Guest

$ grep . /sys/devices/system/cpu/vulnerabilities/*

gives

/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable


Kindly check.",Thomas Stephen Lee
20147,Problems when masquerade is enabled on host,Linux,VirtualBox 6.1.16,2021-01-22T19:27:56Z,2021-01-22T19:27:56Z,2021-01-22T19:27:56Z,"Steps to reproduce issue:

1. Configure host linux with firewalld  + enable masquerade on public zone (or configuration alike with iptables or nftables by hand)
2. Test access to both http and https on guest side
3. Disable masquerade on host and repeat 2

If netfilter masquerading is enabled on host, and guest is in bridge modem, both http and https don't work.

For example:

{{{

curl -I http://www.virtualbox.org
curl: (56) Recv failure: Connection reset by peer
root@techier-glossa:~# curl -I https://www.virtualbox.org
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to www.virtualbox.org:443
}}}


If I disable netfilter masquerading, it works.

In bridge mode it should not concern at all if host is doing that.

This the configuration of firewalld:

[root@munster ~]# firewall-cmd --zone=lxc --list-all   

{{{
lxc (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: lxcbr0
  sources: 
  services: 
  ports: 
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
[root@munster ~]# firewall-cmd --zone=libvirt --list-all
libvirt (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: virbr0
  sources: 
  services: dhcp dhcpv6 dns ssh tftp
  ports: 
  protocols: icmp ipv6-icmp
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule priority=""32767"" reject
[root@munster ~]# firewall-cmd --zone=public --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: wlp108s0
  sources: 
  services: dhcpv6-client kdeconnect mdns ssh
  ports: 
  protocols: 
  masquerade: yes
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

}}}



As far I know, In bridge mode it should not concern at all if host is doing that, should it?

Thanks in advance",sblk
20130,Calling launchVMProcess via vboxwebsrv causes VERR_ENV_INVALID_VAR_NAME,Linux,VirtualBox 6.1.16,2021-01-16T23:43:41Z,2021-01-21T14:23:58Z,2021-01-21T14:23:58Z,"When Sending the SOAP request:


{{{
<soap-env:Envelope xmlns:soap-env=""http://schemas.xmlsoap.org/soap/envelope/"">
	<soap-env:Body>
		<ns0:IMachine_launchVMProcess xmlns:ns0=""http://www.virtualbox.org/"">
			<_this>692d166c1e430875-0000000000000004</_this>
			<session>692d166c1e430875-0000000000000003</session>
			<name/>
			<environmentChanges/>
		</ns0:IMachine_launchVMProcess>
	</soap-env:Body>
</soap-env:Envelope>
}}}


I get:


{{{
<SOAP-ENV:Envelope xmlns:SOAP-ENV=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:SOAP-ENC=""http://schemas.xmlsoap.org/soap/encoding/"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:vbox=""http://www.virtualbox.org/"">
	<SOAP-ENV:Body>
		<SOAP-ENV:Fault>
			<faultcode>SOAP-ENV:Client</faultcode>
			<faultstring>VirtualBox error: rc=0x80bb0005 Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME) (0x80bb0005)</faultstring>
			<detail>
				<vbox:RuntimeFault>
					<resultCode>-2135228411</resultCode>
					<returnval>692d166c1e430875-0000000000000005</returnval>
				</vbox:RuntimeFault>
			</detail>
		</SOAP-ENV:Fault>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
}}}


I am able to start the VM without messages via the GUI and with 
""vboxmanage startvm myvm01""

It does not look like any messages are added to the VM's log file, and the only thing added to VBoxSVC.log is


{{{
01:40:03.911204 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME)}, preserve=false aResultDetail=-752
}}}


All my soap calls to create the VM, query the power state, and power off the VM function.  My code did work as expected on version 5.1.

I also got the error on 6.1.14 and 6.1.12, I was unable to test prior versions due to compile errors when compiling the kernel modules.  I'm running on Ubuntu 20.04 with the ""virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb"" package downloaded from virtualbox's downloads.

My code can be found at:
https://github.com/T3kton/subcontractor_plugins/tree/master/subcontractor_plugins/virtualbox

the power on function is at:
https://github.com/T3kton/subcontractor_plugins/blob/master/subcontractor_plugins/virtualbox/client.py#L182

Thanks",pnhowe
20137,virtualbox manager does not work properly wit 4k monitors on Ubunto 20.04,Linux,VirtualBox 6.1.16,2021-01-19T22:08:43Z,2021-01-19T22:11:37Z,2021-01-19T22:11:37Z,"When installed on a Ubuntu 20.04, virtualbox 6.1.16 runs as empty gray window. The method to fix it is to change scaling in displays settings from 200% to 100% or run it using the ""run_scaled"" script.
Also making the window smaller helps to an extent.

the same problem is related to running virtual machine window. With 200% scaling it has numerous graphical artifacts that prevent normal operation.",Lacek
20123,"Please find attachment, VM not started",Linux,VirtualBox 6.1.16,2021-01-11T14:30:15Z,2021-01-11T14:30:15Z,2021-01-11T14:30:15Z,,vijay.hambir
17987,VirtualBox 5.2.18 vulnerable to spectre/meltdown despite microcode being installed,Linux,VirtualBox 5.2.18,2018-09-13T13:30:33Z,2021-01-04T18:10:22Z,2021-01-04T18:10:22Z,"'''How to reproduce:'''

A host running Debian stretch.
Using VirtualBox version 5.2.18.
A guest running Debian stretch.

Host using stretch-backports with get access to newer microcode. (Old versions are incapable to show spectre/meltdown fixed.)

spectre-meltdown-checker being installed on host and in guest from stretch-backports. (Old versions are incapable to show spectre/meltdown fixed.)

{{{
sudo su -c ""echo -e 'deb http://http.debian.net/debian stretch-backports main contrib non-free' > /etc/apt/sources.list.d/backports.list""
}}}
{{{
sudo apt-get update
}}}
{{{
sudo apt-get -t stretch-backports install spectre-meltdown-checker
}}}

Suppose microcode being installed.

Intel:

{{{
sudo apt-get -t stretch-backports install intel-microcode
}}}

Amd:

{{{
sudo apt-get -t stretch-backports install amd64-microcode
}}}

Suppose running spectre-meltdown-checker on the host looks fine.

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

Suppose using all VirtualBox spectre/meltdown defense options.

{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-entry on
}}}
{{{
VBoxManage modifyvm vm-name --ibpb-on-vm-exit on
}}}
{{{
VBoxManage modifyvm vm-name --spec-ctrl on
}}}
{{{
VBoxManage modifyvm vm-name --l1d-flush-on-sched off
}}}

(These options were introduced in VirtualBox version 5.2.18.)

'''Expected result:'''

spectre-meltdown-checker in guest VM saying ""all fine"".

{{{
sudo spectre-meltdown-checker --paranoid ; echo $?
}}}

By fine I mean exit code 0 and not showing ""vulnerable"".

'''Actual result:'''

spectre-meltdown-checker reporting vulnerable.

'''Questions:'''

Can you reproduce the same issue?

Were all necessary steps performed to protect the guest from spectre/meltdown?

Is this a VirtualBox issue or false-positive in spectre-meltdown-checker?

([https://forums.virtualbox.org/viewtopic.php?f=7&t=89395 Previously posted in VirtualBox forum].)",adrelanos
20030,linux guests cannot be restored,Linux,VirtualBox 6.1.16,2020-11-09T19:54:36Z,2020-11-29T22:19:16Z,2020-11-29T22:19:16Z,"Unable to restore linux guest (Ubuntu) in linux host (Fedora Rawhide). Error ""Kernel driver not installed"" (even though the package is). Running akmods as recommended results in error (log attached).

System info - uname -r: 5.10.0-0.rc2.20201105git4ef8451b3326.64.fc34.x86_64
Specific VB packages: 6.1.16_RPMFusion r140961

This makes virtualbox completely unusable. Has persisted for ~a few weeks with diligent system updating on Fedora Rawhide.",xris
20028,Crash when restoring Fedora virtual machine from a Snapshot,Linux,VirtualBox 6.1.14,2020-11-09T16:45:26Z,2020-11-09T16:45:26Z,2020-11-09T16:45:26Z,"Shortly after restoring from snapshot with virtualbox 6.1.14, the Fedora VM locked up, and a few interesting things happened after I ended the process (the only way to close it as it was totally unresponsive):


The HDD with the OS on became detached.
Virtualbox refused to re-attach the HDD without dropping the saved state (shown in screenshot)
Upon re-attaching the HDD after dropping my saved state, the HDD state had not been restored to the state it was in when I took the snapshot (it was as if I hadn't tried to restore the snapshot).

Attached is the Vbox.log file, and a screenshot of the error I was given as mentioned above.

Please let me know if there's anything I can do to help further debug this. I want to note that VirtualBox 6.1.16 seems generally much more stable than 6.1.14, but I thought the information in this report might still be useful.",Hamish McIntyre-Bhatty
19640,Linux Fullscreen Guest display broken,Linux,VirtualBox 6.1.10,2020-06-06T09:37:36Z,2020-11-09T03:22:37Z,2020-11-09T03:22:37Z,"At VirtualBox 6.1.4, the login screen shows fullscreen and once logged in, the desktop is set to fullscreen - in my case 1280 x 1024. 

Since VirtualBox 6.1.6 all my Debian 10 guests that run fullscreen have had
their display go blank once you've logged in. 

The same problem still exists with VirtualBox 6.1.10. The login screen is 
reduced to 800 x 600 and once logged in, the guests screen goes blank.
If you use the View -> Set Fullscreen (or Host+F key), the guests screen
reappears as windowed. Do this again and the guests display is fullscreen
again. However, rebooting the guest results in the same blank screen again. 

Attached are two VBoxLogs, one from 6.1.10 which is taken at the point the guests screen has gone blank and the other when using the GA's from 6.1.4, when everything works as it should.  

The Host is running Debian 10 with the Mate desktop.  
The affected guest(s) are also running Debian 10 with the Mate desktop.",Feline
20024,Linux host freezes with bridged adapter and apt,Linux,VirtualBox 6.1.16,2020-11-08T00:50:16Z,2020-11-08T03:28:46Z,2020-11-08T03:28:46Z,"My Linux (Fedora 33) host freezes whenever I enable bridged adapter and the guest transfers (some) data.

Steps to reproduce:
1. Install an Ubuntu 20.04 server guest
2. Go to Guest settings, Network, Attached to, Bridged Adapter
3. Run an apt install command on it. I was following [these instructions](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart).
4. The host completely freezes, and I'm forced to reboot.

I've installed some server software (Jitsi Meet) and now it freezes even on guest boot.

Some hardware details:

{{{
*-cpu
          product: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
          vendor: Advanced Micro Devices [AMD]
          physical id: 1
          bus info: cpu@0
          size: 1443MHz
          capacity: 2100MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq
}}}



{{{
*-network
                description: Wireless interface
                product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: wlp2s0
                version: 00
                serial: [REMOVED]
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.18-300.fc33.x86_64 firmware=N/A ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
                resources: irq:81 ioport:2000(size=256) memory:c0700000-c070ffff
}}}

I will append a log file in some minutes",gabrc
19950,UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: 0x0 1920x1173,Linux,VirtualBox 6.1.14,2020-10-09T14:43:52Z,2020-11-05T16:34:20Z,2020-11-05T16:34:20Z,"Recently I migrated my multi-boot system from an i7-6700 to a Ryzen 9 3900XT.[[BR]]
Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.[[BR]]
The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. A hard restart is required.[[BR]]

From the VBox.log's it seems that the Slackware problem is:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}


whereas the Xubuntu VBox.log reads:


{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


Note the ""0x0"" versus ""0x25"".[[BR]]

As via symlinks the VB settings and VM definitions are shared between the sundry Linux instances an error like a ""leftover"" file definition is highly unlikely.[[BR]]

Some other differences beween the VBox.logs are:[[BR]]
-- Xubuntu kernel 5.4.0-48-generic, Slackware 5.8.14-burdi64;[[BR]]
-- Xubuntu VB QT version 5.12.6, Slackware 5.6.1;[[BR]]
-- Xubuntu X release 12008000, Slackware 12009000;[[BR]]
-- Xubuntu loads a VMMR0.so, Slackware does not.[[BR]]

I started out with VB 6.1.14-140239. For Slackware I then tested VB testbuild 6.1.15-6.1.15-140809 asis with kernel 5.8.14-burdi64 and the same testbuild but patched (see #19845) with kernel 5.9.0-rc8-burdi64.[[BR]]
However the problem persists ...


 ",burdi01
20021,AMD Ryzen 9 3900XT - Slackware Current64 - kernel 5.9.3-burdi64 - VM's fail to start,Linux,VirtualBox 6.1.16,2020-11-05T16:24:25Z,2020-11-05T16:24:25Z,2020-11-05T16:24:25Z,"Some weeks ago my multi-boot Intel i7-6700 system died on me. From backups I was able to clone things on the AMD Ryzen 9 3900XT replacement. Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.

The failure occurs very early in the start sequence: the big ""starting arrow"" remains shown and the system freezes all over. Sometimes I can start another user session via <Alt+Fx>. Very often a hard restart is required.
The Slackware instance initially ran my own kernel 5.8.14-burdi64, the Xubuntu one kernel 5.4.0-48-generic. During the testing these kernels were upped. At the moment they are 5.9.3-burdi64 and 5.4.0-52-generic respectively. The symptoms however stayed the same.[[BR]]
I started out with VB 6.1.14-140239. Nowadays I test with VB 6.1.16-140961, a preliminary test with VB 6.1.17-141128 shows no discernable effects.[[BR]]
It should be noted that both the Slackware and Xubuntu instances via symlinks refer to the same VM's.

The Slackware ""error"" VBox.log ends with:[[BR]]

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173
}}}

while the Xubuntu ""ok"" one contains:

{{{
GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150
}}}


The i7-6700 had embedded video, so used the i915 driver. My Ryzen has a discrete video card -- an ASUS Radeon RX 550 PH-RX550-2G-EVO one:
-- lspci: [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7).
supported by the amdgpu driver.

To isolate the problem I did the following tests:[[BR]]
-- I cloned the Slackware instance to an i5 laptop with embedded video: the VM's there started and ran without problems;[[BR]]
-- Back on the AMD box I replaced my 5.9.3-burdi64 kernel with Slackware's stock 5.4.74 one: the VM's started and ran without problems;[[BR]]
-- I upped the Xubuntu kernel to the 5.9.2-050902-generic one from the kernel PPA: the VM's started and ran without problems;[[BR]]
-- I replaced the Xubuntu VB 6.1.16-140961 .deb implementation with the .run one: the VM's started and ran without problems;[[BR]]
-- Back on my Slackware instance I replaced the 5.4.74 kernel with the Xubuntu 5.9.2-050902-generic one: the VM's started and ran without problems.

As said when the problem occurs one often cannot do much more than hard resetting the system. By formally repeating these tests and collecting as much info as possible I found that for the ""error"" case the syslog reports an oops ""unable to handle page fault for address"", the call trace of which starts within vboxdrv.

The Slackware the VBox.logs and the /var/log/messages file as collected are:[[BR]]
-- VBox-59S.log: the ""error"" with my 5.9.3-burdi64 kernel;[[BR]]
-- VBox-54S.log: the ""ok"" with Slackware's stock 5.4.74 kernel;[[BR]]
-- VBox-59U.log: the ""ok"" with the Xubuntu 5.9.2-050902-generic kernel;[[BR]]
-- messages: searching for ""========="" will give you the ""error"" and ""ok"" sections.

It is likely that something in the configuration of my 5.9.3-burdi64 kernel triggers the problem. But which setting is the culprit? My config is 187.4 kB and the Xubuntu one is 248.8 kB. So comparing the two is an almost hopeless endevour ...

Any hints would be appreciated.[[BR]]
:D
",burdi01
20014,VirtualBox GUI broken after update from 5.2.44 to 6.1.14,Linux,VirtualBox 6.1.14,2020-11-02T15:50:37Z,2020-11-02T15:56:52Z,2020-11-02T15:56:52Z,"After struggling all day trying to keep 5.2.44 working with VVV, I decided to try updating to 6.1.14.  As a result, when I open up the VirtualBox Manager GUI, I get this broken display.  The contents are in the incorrect location and aren't clickable.  If I expand the window, all of the content disappears.  Luckily, I don't need to use the configuration tools there at the moment but this will be a problem for me quite soon.",artlytic_dave
19954,"after DISabling timesync in VB linux guest's GuestAdditions, boot errors: ""timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED"" ?",Linux,VirtualBox 6.1.14,2020-10-10T03:37:13Z,2020-10-10T03:37:13Z,2020-10-10T03:37:13Z,"I run
{{{
rpm -qa | grep -i virtualbox
	VirtualBox-6.1-6.1.14_140239_fedora32-1.x86_64

uname -rm
	5.8.13-200.fc32.x86_64 x86_64
}}}

for both host & guests.

I've been having lots of time-sync issues in guests -- large drifts, time jumping forward & backwards, etc.

That's despite running chrony time sync clients in each guest.

After some digging, found this

	https://docs.oracle.com/en/virtualization/virtualbox/6.1/admin/fine-tune-timers.html#disabletimesync

and disabled timesync in clients' GuestAdditions, with
{{{
VBoxManage setextradata ""<vm name>"" ""VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled"" 1
}}}

Now, on guest reboot, I'm seeing these errors in guest dmesg log,
{{{
dmesg | egrep -i ""timesync|virtualbox""
	[    0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[    2.123518] usb 2-1: Manufacturer: VirtualBox
	[    2.134288] input: VirtualBox USB Tablet as /devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input5
	[    2.134476] hid-generic 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-0000:00:06.0-1/input0
	[   27.809171] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   27.809255] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
	[   57.418443] 02:19:39.352350 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   66.602300] 02:19:49.375515 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   75.767563] 02:19:59.378440 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   84.932750] 02:20:09.381252 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[   94.098285] 02:20:19.384482 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  103.264664] 02:20:29.388593 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  112.496162] 02:20:39.463769 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  121.658906] 02:20:49.463953 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  130.822255] 02:20:59.464766 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
	[  139.985037] 02:21:09.464959 timesync Error: vgsvcTimeSyncWorker: VbglR3GetHostTime failed; rc2=VERR_NOT_SUPPORTED
}}}

Clearly 'errors', not warnings ...

Either a bug, or add'l config is needed to fix/silence that^ ...",pgnd
19906,Black Screen after trying to log onto to Kali Linux,Linux,VirtualBox 6.1.14,2020-09-21T01:28:21Z,2020-10-09T13:06:33Z,2020-10-09T13:06:33Z,"So recently I have been trying to log back into my Kali Linux virtual machine in virtual box. But so far, after I sign in to with my username and password , it cuts to a black screen. How do I fix this? I have screenshots inside that kali linux that I desperately need... 

Please help.. I tried to use some ways to fix it but I can't.. I desperately need that information before something happens to it.",MrFrank
19949,Some VirtualBox EFI Boot Menu entries do nothing when booting from ISO,Linux,VirtualBox 6.1.14,2020-10-08T19:51:51Z,2020-10-08T19:51:51Z,2020-10-08T19:51:51Z,"Description:

With the exception of EFI Shell entry, none of the other choices in the EFI Boot Menu actually launch an EFI binary.  I've tried this with several different ISO images with the same result.  Usually, however, I can navigate using the EFI shell to the EFI binary and launch it manually.

Steps to reproduce (example):

(Using VirtualBox 6.1 on Devuan Ascii 2.1)
Download recent copy of Devuan ISO (devuan.org)
Create brand new EFI VM (with appropriate bitness)
""Insert"" the downloaded copy of Devuan ISO in the CD drive
Start the VM -- the EFI shell will appear
Exit the EFI Shell
Select the Boot Menu option in the EFI UI
Try to launch the entries in the Boot Menu (the EFI Shell entry will work; try others)

Expected Outcome:   Grub menu appears

Actual Outcome:  Nothing happens; the user is left in the EFI UI

Additional Information:

Adelie Linux (adelielinux.org) and Devuan experience this issue, regardless of 32 or 64 bitness, and regardless of which variation of these distros are used.  Other distros have not been tested for EFI install extensively.
",Harry M
17420,"Regression: Cannot compile VirtualBox 5.2.4 on Ubuntu 16.04, Qt5 not found",Linux,VirtualBox 5.2.4,2018-01-04T21:02:16Z,2020-10-08T16:13:01Z,2020-10-08T16:13:01Z,"Even with the qt5 package installed on Ubuntu 16.04, the VirtualBox 5.2.4 configure script does not find Qt5. This is a regression since VirtualBox 5.1.",core-it-admin
19933,Issues due to lost USB packets (control and bulk type transfers),Linux,VirtualBox 6.1.14,2020-10-02T23:46:30Z,2020-10-02T23:48:14Z,2020-10-02T23:48:14Z,"Hi all,

I'm using the latest VirtualBox version under Kubuntu 18.04 LTS. I'm having errors when testing a software I've made in a VM running the same OS, but it makes no difference on other VMs running other Linux distributions. However, my software doesn't have issues when it is running on my native machine, no VMs involved. I even tested this on a different machine, and no issues whatsoever even after a few hours.

The history here is that this software controls a USB switcher, monitoring it continuously, ever 200ms (but that can be changed in the options). The USB switcher itself is based on the CP2130 from Silicon Labs. The software has all the kinks ironed, but it fails on a VirtualBox VM, which should not happen. This also happens, seemingly, irregardless of the version of VBox I have installed. I've recently updated to the latest version from the VirtualBox repository, but saw no differences. In fact, I've seen it fail catastrophically and even causing the device to reset (the software forces a reset if more than 10 errors occur) quite rapidly. More frequently, errors are due to lost control transfers, but can happen with bulk transfers as well.

To sort this out, I've decided to run traces with Wireshark, simultaneoulsy inside and outside the VM, monitoring the same connections essentially. I can conclude that there were some lost packets because I've seen errors reporting inside the VM pertaining to packets that simply were not matched to any packets caught outside the VM, which might mean that the request packet never went outside the VM to the USB host, and due to timeout, it generated a ENOENT response inside the VM, but not outside. I must add that responses that exceed 100ms are ruled out the the application.

I have the images proving the issue, the screenshots highlighting some of the packets and the traces taken inside and outside the VM.

Kind regards, Samuel Lourenço",bloguetronica
19923,Mouse Middle-Scroll Click aborts Linux guest,Linux,VirtualBox 6.1.10,2020-09-28T00:50:08Z,2020-09-30T06:32:13Z,2020-09-30T06:32:13Z,"On Linux host 20.04.1, using linux guest 20.04 
At random occurrence when I middle click or scrollwheel click (to open multiple tabs in firefox) the guest machine immediately aborts. Shows (Aborted) within Vbox machine list window

I think this has occured before years ago and needed some upgrade. I am unable to search the bugs or forum as I kept getting error mesages ""Unable to search at this time. Please check back in several minutes""
",FleddyFlinty
19896,virtualbox 6.1.14 X Debian guest X keyboard X webcam X fullscreen VM,Linux,VirtualBox 6.1.14,2020-09-18T14:32:37Z,2020-09-22T14:57:56Z,2020-09-22T14:57:56Z,"Hello

I found a very strange issue on Virtualbox 6.1.14 running on Ubuntu 18.04 host, Debian GNU/Linux bullseye (testing) guest using Gnome 3.30 desktop (or KDE Plasma 5.17) and a Logitech HD webcam C270 on fullscreen VM.

If enable webcam device on virtualbox toolbar, the keyboard is lost.

It also happens with Debian GNU/Linux 10.5 buster VM.

BUT this problem does not happen when using windowed VM.

What additional info should I collect?

Regards.

Andre Felipe",afmachado
19901,Reopen #6650 closed on 08/14/2016,Linux,VirtualBox 6.1.14,2020-09-18T23:49:19Z,2020-09-18T23:49:19Z,2020-09-18T23:49:19Z,"vbox-img --help documentation allows the `convert` command to output to stdout. This has been requested by forum users a few times in several forums. Mentioned 2010 ticket is just one user case. But this usage fails, as seen in log attached.
There seems to be an unjustified regression in the code, in `vbox-img.cpp`:797. The following line of code was withdrawn at changeset 33235 with commit message ""Storage/vbox-img: implement stdout handling"".

     {{{ AssertFailedReturn(VERR_NOT_SUPPORTED); }}}

However for some reason this line has been reintroduced later on.
I tested a custom build of vbox-img with the attached patch and the requested stdout handling worked well. Attached proposed patch against 6.1.14a code.
Alternatively, if this capability is still immature, revise the `--help` output and reopen #6650


",fabnicol
19818,Use portable sched_yield() rather than pthread_yield(),Linux,VirtualBox 6.1.10,2020-08-17T18:56:10Z,2020-08-20T18:20:12Z,2020-08-20T18:20:12Z,"The sched_yield() call is the standard and portable routine.  Current calls to pthread_yield() in Virtualbox sources (host and guests) should be replaced by calls to sched_yield().  If sched_yield() is not available on a platform, then the build tools (including those for the Guest Additions) could arrange to use a shim routine that calls pthread_yield().  

This would be helpful in supporting platforms that do provide support for non-portable libraries and routines.",Harry M
19797,installed virtualbox 6.1.12 on centos 7 but vboxweb-service is not started,Linux,VirtualBox 6.1.10,2020-08-06T11:52:45Z,2020-08-06T11:52:45Z,2020-08-06T11:52:45Z,"installed virtualbox 6.1.12 but vboxweb-service is not started.
i tried to start ------>
systemctl start vboxweb-service

""Job for vboxweb-service.service failed because the control process exited with error code. See ""systemctl status vboxweb-service.service"" and ""journalctl -xe"" for details.""

systemctl status vboxweb-service -l
● vboxweb-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-08-06 17:19:28 IST; 1min 17s ago
  Process: 5801 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=1/FAILURE)

Aug 06 17:19:28 localhost.localdomain systemd[1]: Starting vboxweb-service.service...
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 06 17:19:28 localhost.localdomain su[5807]: (to admin) root on none
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: failed: VirtualBox web service failed to start.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service: control process exited, code=exited status=1
Aug 06 17:19:28 localhost.localdomain systemd[1]: Failed to start vboxweb-service.service.
Aug 06 17:19:28 localhost.localdomain systemd[1]: Unit vboxweb-service.service entered failed state.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service failed.",pmssy
19664,Guest Additions prevent Lubuntu desktop from starting,Linux,VirtualBox 6.1.10,2020-06-14T18:23:45Z,2020-08-04T10:21:05Z,2020-08-04T10:21:05Z,"The guest is a 32 bit Lubuntu 18.04 Linux machine. The host is a 64 bit Ubuntu 18.04 Linux machine.

The guest works great as long as I do not install Guest Additions. After installing Guest Additions, I get the login / greeter screen, but after logging in, the desktop does not start.

To test this, I created the virtual machine and restarted it many times, logging in successfully. After one of these logins, I took a snapshot and installed Guest Additions. After that and a restart, the desktop did not start.

To confirm that the snapshot was not the problem, I restored the snapshot and did not install Guest Additions. I was able to restart and have the desktop start.

I would be happy to provide additional information but I do not know what would be helpful.",Organic_Marble
19735,headless start failed with vmsvga display,Linux,VirtualBox 6.1.10,2020-07-19T17:00:05Z,2020-07-19T17:00:05Z,2020-07-19T17:00:05Z,"Host - fedora 31 workstation

Guest - Ubuntu 18.04.4 LTS

VirtualBox 6.1.12

1. I set up VMSVGA (as recommended for linux guests) with 3D driver in VM settings
2. I logon to host with ssh
3. I have started VM by command: VBoxManage startvm ""vmname"" --type headless
4. VM started
5. Shortly VM stoped with status ""interrupted""

6. I set up old VBoxVGA driver without 3D in VM settings
7. I have repeated steps 2-3
8. All is OK!

9. I have repeated step 1
10. I logon to host with ssh BUT with -X option
11. I have repeated step 3
12. All is OK
13. BUT when I have closed session (which started at step 10) then my VM stopped!

I would like to use steps 1-4 but without step 5 :)
At this time I use my VM with old VBoxVGA driver.
May be step 5 - result of some bug with VMSVGA driver...",tol2000
19713,Virtual Box Booting Issue,Linux,VirtualBox 5.2.34,2020-07-10T10:25:01Z,2020-07-10T10:30:32Z,2020-07-10T10:30:32Z,"
I am Using using Ubuntu version :  Ubuntu 18.04.4 LTS
                Virtual Box Version : 5.2.34

While start using iso file from my local after Windows logo system got hanged everytime
Could you suggest and help to resolve the issue.",Ujjal
19696,VBOX_E_IPRT_ERROR 0x80BB0005 when cloning a vm that is in savestate,Linux,VirtualBox 6.1.10,2020-07-02T18:24:28Z,2020-07-02T18:24:28Z,2020-07-02T18:24:28Z,"Cloning a VM that is in ""savestate"" can issue a VBOX_E_IPRT_ERROR 0x80BB0005 error.
{{{
[vbox@vm001 vms]$ vboxmanage --version
6.1.10r138449
}}}
Change machine to ""savestate""
{{{
[vbox@vm001 vms]$ vboxmanage controlvm t1 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
Try to clone the machine (note this is all on local disk. No NFS/SMB mounts)
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Clone VM failed
VBoxManage: error: Code VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleCloneVM(HandlerArg*)"" at line 610 of file VBoxManageMisc.cpp
}}}
As you can see, the clone fails with ""VBOX_E_IPRT_ERROR (0x80BB0005)"".

Now we do the same thing, but poweroff the vm before doing the clone.
Let's resume the VM from the savestate above.
{{{
[vbox@vm001 vms]$ vboxmanage startvm t1 --type headless
Waiting for VM ""t1"" to power on...
VM ""t1"" has been successfully started.
}}}
Poweroff the VM
{{{
[1803 vbox@scvm001 vms]$ vboxmanage controlvm t1 poweroff       
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
}}}
and rerun the clone...
{{{
[vbox@vm001 vms]$ vboxmanage clonevm t1 --mode all --basefolder /mnt/lv001-r0/backup/vms --name t1-20200702-112825-vbbu
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Machine has been successfully cloned as ""t1-20200702-112825-vbbu""
}}}
The clone runs sucessfully to completion.

Virtualbox user forum thread for reference: https://forums.virtualbox.org/viewtopic.php?f=7&t=98881",guideloom
19684,Frequent IO Read overload freezing the OpenSUSE VM,Linux,VirtualBox 6.1.10,2020-06-26T10:02:40Z,2020-06-26T10:02:40Z,2020-06-26T10:02:40Z,"My OpenSUSE VM frequently freezes and the Read IO is constantly maximum. It seemed to always happen when browser the internet, regardless of which browser used. The VM is used for browsing a few websites, connecting to a vpn and ssh tocompany hosts. The CPU also spikes to high load.

I've installed OpenSUSE 15.1 KDE and 15.2 multiple times and have set it up mostly in the same way. This is the setup:

EFI
LUKS > LVM > btrfs
HOST IO cache ON (also tried off)
SSD drive on for storage container
4GB RAM (2GB in use)
4 vCPU
VMDK storage format
guest additions installed

I installed the same setup, except for EFI that is replaces with BIOS (I think I tried that with VB as well), and this issue never happens. Same resources given to VM.

Unfortunately I don't have the logs anymore.",lmmmm
19594,Mouse behaves badly with two screens Guest Additions 6.1.8,Linux,VirtualBox 6.1.8,2020-05-17T17:28:43Z,2020-06-11T15:04:39Z,2020-06-11T15:04:39Z,"My configuration is 
Host: Debian Stretch
Guests: Debian Buster (two screens), Debian Buster (one screen), Ubuntu Focal Fossa Server
Desktop: Gnome classic on host and guests (including Ubuntu server)

When I upgraded from 6.1.6 to 6.1.8 (including an upgrade of the guest additions) the mouse did not behave correctly on the guests with two screens and the secondary screen stays black even though the window for the second screen opens. When I move the mouse over a widget and click, it sometimes does nothing and sometimes activates a different window. Downgrading to VBox 6.0 and installing the 6.0 guest additions fixed the problem.

I recall having a similar or perhaps exactly the same problem with my two screen guests in an earlier upgrade of VBox (I don't remember the versions involved). I think there was a bug report in that previous case as well.",linux_user_1
19656,Error when starting VBoxSVC on alpine linux (MUSL),Linux,VirtualBox 6.1.8,2020-06-11T07:20:05Z,2020-06-11T07:20:05Z,2020-06-11T07:20:05Z,"Hello

I have compiled the virtualbox in alpine linux (MUSL), but when I run it, I get a failure of XPCOM

this is the mistake

VBoxSVC: error: Failed to initialize XPCOM! 
(rc=NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
VBoxSVC: error: Failed to shutdown XPCOM! (rc=Unknown Status 0x80460016)
XPCOM server has shutdown.",Sodomon
15374,Virtual HDD becomes unavailable for guest : with AHCI#0: Port x reset,Linux,VirtualBox 5.0.14,2016-05-01T14:23:43Z,2020-06-10T12:34:49Z,2020-06-10T12:34:49Z,"It looks a like #9975 in symptoms but with linux/linux host/guest and no windows involved. Also errors logs are not as much verbose.

The guest runs find for a (what looks like) random duration ranging from a few weeks to one year then without clear causes one virtual disk becomes unavailable and creates sda i/o errors on guest with one only line in the Vbox.log file :

{{{
1900:51:41.454153 AHCI#0: Port 2 reset
}}}

A kill $pid + VboxManage startvm restores every thing to normal until next time.

I have seen this behavior on virtualbox version back to 4.3.6r91406 and up to 5.0.14.
When the crash occurs, system load on host isn't particularly high, i/o aren't particularly high neither on host or guest.
I've seen it on SATA rotative disks in RAID 1 and 5, SATA SSD disks raid 1

Guests linux kernels ranges from 2.6.18 up to 3.2.x
Guest hosts are Linux debian 6.0 7.0 or 8.0
All vdi files are used as SATA controled drives


I keep a log of crashed VMs to try discovering common criteria to narrow it down, but nothing really jump to the eye beside :

- low load/low i/o VMs don't seam to crash
- On some host server  with different hardware I never had any crash

I know my report is quite poor in details, but I'll try to keep it updated. During the mean time is there a way to make those ""virtual disk reset"" more verbose ?



",sylvain Gplservice
19652,Segfault in vmsvgaR3PortReportMonitorPositions (vboxvga),Linux,VirtualBox 6.1.10,2020-06-10T07:10:01Z,2020-06-10T07:31:31Z,2020-06-10T07:31:31Z,"Linux with 4.2.0 kernel (Astra Linux 1.5) crashes VM upon login with legacy vboxvga controller. Host: Fedora 32, guest: Astra Linux 1.5

{{{
#0  0x00007f0aeb03ad7e in vmsvgaR3PortReportMonitorPositions(PDMIDISPLAYPORT*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#1  0x00007f0b325a79b8 in Display::i_handleUpdateMonitorPositions(unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#2  0x00007f0b325ca018 in vmmdevUpdateMonitorPositions(PDMIVMMDEVCONNECTOR*, unsigned int, RTPOINT*) () from /usr/lib64/virtualbox/components/VBoxC.so
No symbol table info available.
#3  0x00007f0aeaffe7b1 in vmmdevRequestHandler(PDMDEVINSR3*, void*, unsigned short, unsigned int, unsigned int) () from /usr/lib64/virtualbox/VBoxDD.so
No symbol table info available.
#4  0x00007f0b38310922 in IOMIOPortWrite () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#5  0x00007f0b38208be2 in IOMR3ProcessForceFlag () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#6  0x00007f0b381ff4e5 in emR3HighPriorityPostForcedActions () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#7  0x00007f0b38202ef2 in emR3HmExecute () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#8  0x00007f0b38200c4e in EMR3ExecuteVM () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#9  0x00007f0b382635f0 in vmR3EmulationThreadWithId(RTTHREADINT*, UVMCPU*, unsigned int) () from /usr/lib64/virtualbox/components/VBoxVMM.so
No symbol table info available.
#10 0x00007f0b54e17f14 in rtThreadMain () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#11 0x00007f0b54ece55e in rtThreadNativeMain(void*) () from /usr/lib64/virtualbox/VBoxRT.so
No symbol table info available.
#12 0x00007f0b551b9432 in start_thread () from /app/lib64/libpthread.so.0
No symbol table info available.
#13 0x00007f0b550e09d3 in clone () from /app/lib64/libc.so.6
No symbol table info available.
}}}
",Max Fedotov
19638,no network connection with virtio-net after some time,Linux,VirtualBox 6.0.22,2020-06-03T17:54:10Z,2020-06-03T17:57:42Z,2020-06-03T17:57:42Z,"Hi,

I'm running an Ubuntu 18.04 guest on a ubuntu 18.04 host. The guest uses virtio-net for the network adapter.

After some uptime, you can use the interface anymore. The syslog is flodded with

{{{
net eth0: Unexpected TXQ (0) queue failure: -5
}}}

I have to reboot the VM to get it working again.

If you need any information, please don't hesitate to ask for.

Regards,
meiser",Peter Meiser
19570,Ubuntu 18.04 guest crashes regularly,Linux,VirtualBox 6.1.6,2020-05-07T12:48:44Z,2020-05-29T14:58:22Z,2020-05-29T14:58:22Z,"Guest: Ubuntu 18.04
Host: Ubuntu 18.04

This guest is actively (7 days a week) used since VirtualBox 5.x, no crashes were observed. After upgrading VirtualBox to 6.1.6 guest gets terminated with 'Aborted' state at least once a week, usually during text editing.",Andriy
19592,dnf upgrade of virtual box sequence,Linux,VirtualBox 6.1.8,2020-05-16T21:33:02Z,2020-05-22T12:20:53Z,2020-05-22T12:20:53Z,"The update sequence seems wrong, taking steps to apply 6.1.6 after 6.1.8 

Output to screen:

# dnf upgrade
Last metadata expiration check: 1:17:10 ago on Sat 16 May 2020 03:43:57 PM EDT.
Dependencies resolved.
=========================================================================================================================
 Package                      Architecture         Version                                Repository                Size
=========================================================================================================================
Upgrading:
 VirtualBox-6.1               x86_64               6.1.8_137981_fedora31-1                virtualbox                94 M

Transaction Summary
=========================================================================================================================
Upgrade  1 Package

Total download size: 94 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64.rpm                                        3.8 MB/s |  94 MB     00:24    
-------------------------------------------------------------------------------------------------------------------------
Total                                                                                    3.8 MB/s |  94 MB     00:24     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                 1/1 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Upgrading        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 

Creating group 'vboxusers'. VM users must be member of that group!


  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Cleanup          : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Verifying        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Verifying        : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 

Upgraded:
  VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                                          

Complete!

",Wheaties
19582,"VirtualBox host, memory management issue, unable to release unused memory of guest",Linux,VirtualBox 6.1.6,2020-05-14T10:42:00Z,2020-05-18T15:23:13Z,2020-05-18T15:23:13Z,"I have a workstation with 32 GB installed memory.

I create a new Debian virtual machine, and allocate 16 GB to it. When I boot the machine, it only take less than 800 MB memory. As the virtual machine running, especially for heavy tasks. The memory occupation increase. But when I end those tasks, the memory usage of guest machine's OS suddenly reduce, but the memory occupation of virtual machine on host RAM, still keep as the memory upper bound. 

I believe that it is the problem of VirtualBox, because even if I reboot (not same as power off and boot) the virtual machine, the RAM usage still keep as Maximum.

I hope VirtualBox can add ability to automatically release unused guest memory.",stl0hello
19587,Awful Linux Guest Performance,Linux,VirtualBox 6.1.6,2020-05-15T10:45:54Z,2020-05-15T11:02:43Z,2020-05-15T11:02:43Z,"I just tested 64bit VBox 6.0.20 and 6.1.6 with a 64bit Linux guest on a 64bit Linux host (updating Guest Additions each time). Started at 6.0.20, performance was fine. Upgraded to 6.1.6, performance was so bad that the VM is unusable. Downgraded back to 6.0.20, performance is normal. So, VBox 6.1 is broken for Linux guests because of the awful performance.

Host: Intel Core i7 (1st gen) 28G RAM
Guest: 2 cores, 4G RAM

Logs for both the broken 6.1.6 guest and the working 6.0.20 guest are attached.

I ran this test because a user on a FB group had perf issues with a 64bit Linux guest. After I suggested that he downgrade to 6.0.20, his perf is back to normal.
",Tom3.14159
18444,Cannot use microphone. Applications that try to record audio hang,Linux,VirtualBox 6.0.4,2019-02-20T20:30:46Z,2020-05-10T16:39:50Z,2020-05-10T16:39:50Z,"After I upgraded VirtualBox from 5.x to 6.0.4, I can no longer use microphone from within the VirtualBox VM. I run Debian on both the host and the guest system.

Steps to reproduce:
* Create a new VM. Set guest OS to Debian 64-bit, don't change any other settings.
* Boot the VM using a Debian live CD.
* Enable audio input for the VM.
* Inside the VM, try to use a program that tries to record audio, such as SOX (run these commands: apt-get install sox; rec -n).
* Observe that the program hangs. On the host system, the same program works fine.",abacabadabacaba
18754,Cannot capture mouse pointer in video recording of Ubuntu 18.04 LiveCD guest,Linux,VirtualBox 6.0.8,2019-07-15T04:27:15Z,2020-05-09T14:32:41Z,2020-05-09T14:32:41Z,"This is on Ubuntu 18.04 host, VirtualBox 6.0.8 r130520, and Ubuntu 18.04 LiveCD (installer) guest.

Please see this video: https://i.imgur.com/KTiGSCJ.mp4

The video starts with Ubuntu 18.04 as guest in VirtualBox, controlled by rdesktop.

While mouse integration is active in VirtualBox, even if the actual mouse is controlling rdesktop, there is no mouse pointer rendered in the VirtualBox Ubuntu LiveCD guest.

If I turn off mouse integration in VirtualBox, then: when we have the actual host mouse pointer controlling via rdesktop - a mouse pointer appears rendered in the VirtualBox Ubuntu LiveCD guest. So this looks promising.

But if I do a Recording video capture in VirtualBox in this state - there is still no mouse pointer in the video recording, even if the host mouse was controlling via rdesktop, and the VirtualBox Ubuntu LiveCD appeared to be rendering the mouse pointer's ""clone""!

Maybe this is a bug in VirtualBox?

Attached is the .webm recorded by VirtualBox in the test run shown in the video above.",sdaau
19533,wacom clicks not registered in virtualbox manager window,Linux,VirtualBox 6.1.6,2020-04-26T12:20:22Z,2020-05-07T16:12:20Z,2020-05-07T16:12:20Z,"Tested with virtualbox 6.1.6 on Ubuntu 20.04 and separately, by a different person, with virtualbox 6.0.14 on Ubuntu 19.10.

Both of us are unable to click within the virtualbox manager window, like create a new VM or import or export or access preferences, using wacom tablet (in my case Wacom Intuos Pen Tablet). 

For me up to a few days ago, when I was still running virtualbox 5.2.40 on Ubuntu 19.04 (and before on Ubuntu 18.04), this was not a problem. Upgrading to Ubuntu 20.04 means that python2 is no longer supported (which makes total sense) but now it looks like virtualbox manager has become unusable because it does not seem to register the mouse clicks. 

To clarify, when I hover over items in the virtualbox manager window the buttons seem to respond to the hovering, but when I click nothing happens. Clicking in any other program so far has not resulted into issues like this. Also interestingly I discovered today that when I import (using a regular mouse temporarily plugged in) several VMs that I am able to change the order of the VMs in the virtualbox manager window (sort/group them) but again not able to click them.

This may be similar or related to: https://www.virtualbox.org/ticket/11939
If so, this may be a regression bug.

And I also posted it here without reply so far:
https://forums.virtualbox.org/viewtopic.php?f=7&t=97881",Jackg
19526,'vboxmanage list runningvms' FAILs to list running VMs,Linux,VirtualBox 6.1.6,2020-04-23T19:52:03Z,2020-04-25T10:58:06Z,2020-04-25T10:58:06Z,"noting this similar symptom, from a still open issue

	""vboxmanage list runningvms does not list anything""
	https://www.virtualbox.org/ticket/6808#propertyform
		Opened 10 years ago[[BR]]
		Last modified 4 years ago

has that been fixed/addressed elsewhere?

here, running latest VB release
{{{
	VBoxManage --version
		6.1.6r137129
}}}

on host,
{{{
	lsb_release -rd
		Description:    openSUSE Leap 15.1
		Release:        15.1
}}}

checking available vms, correctly returns
{{{
	> VBoxManage list vms
		""Debian_Stable"" {...}
		""Win10_Pro"" {...}
		""openSUSE_Leap"" {...}
	>
}}}

if i launch a guest, e.g.
{{{
	""openSUSE_Leap""
}}}

is, atm, up & running ... and accessible,
{{{
	ps ax | grep vir
		24799 ?        Sl     0:16 /usr/lib/virtualbox/VirtualBox
		24816 ?        S      0:08 /usr/lib/virtualbox/VBoxXPCOMIPCD
		24822 ?        Sl     0:19 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
		40167 ?        Sl     0:27 /usr/lib/virtualbox/VirtualBoxVM --comment openSUSE_Leap --startvm ... --no-startvm-errormsgbox
		40176 ?        S      0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
		40182 ?        Sl     0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

but checking RUNNING vms, still (again?) returns blank
{{{
	> VBoxManage list runningvms
	> 
}}}",pgnd
19497,Feture request: minimize the virtualbox machine window when the guest OS powers off its virtual screen,Linux,VirtualBox 6.0.14,2020-04-15T23:32:38Z,2020-04-16T01:53:18Z,2020-04-16T01:53:18Z,"Hello,

my guest ubuntu OS always keeps saying (in the background) that it's unable to lock screen while I have a virtualbox machine in the foreground. Well in a way that is a feature I understand, but also as it hinders security (host OS is not locking when there's no keyboard and no mouse activity and a virtualbox guest is in the foreground) it is an antifeature as well. As a solution which would make this a feature without any drawbacks I suggest you to minimize the guest OS window (or otherwise prevent it preventing the host OS to lock) when the guest OS blanks or powers off its virtual screen. Maybe you can add a configuration option for this as well, but maybe as until today there were no use to powering off/blanking the virtual screen this feature might be OK without any configuration option as well.

Thank you in advance.

Imre",Imre84
19488,Trying to start a new instance of Ubuntu Server,Linux,VirtualBox 6.1.4,2020-04-14T15:58:38Z,2020-04-14T16:31:10Z,2020-04-14T16:31:10Z,"00:00:34.744960 GIM: KVM: Resetting MSRs
00:00:34.748351 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:34.756082 Console: Machine state changed to 'PoweredOff'
00:00:35.281071 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:00:35.757520 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:35.757592 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:35.757701 GUI: Aborting startup due to invalid machine state detected: 1",larka06
19429,VirtualBox 6.1 + Whonix 15 = Aborted,Linux,VirtualBox 6.1.4,2020-03-24T18:12:00Z,2020-04-12T14:15:03Z,2020-04-12T14:15:03Z,"Hello everyone! I have been using Whonix 14 for a long time and everything have been working fine but unfortunately I need some soft as libreoffice which I can't download there because Whonix 14 isn't supported. I had to upgrade it. I should note that I used VirtualBox 5.3 with Whonix 14. I decided to make new one from scratch. Downloaded Whonix 15 and import it. I faced with the problem that clipboard didn't work. I decided download new version of VirtulBox = 6.1 This is solved the problem with clipboard but I faced with the bigger problem instead . Now after some time (different time ) VM just close without any reason and in main window of virtulbox I see the title ""Aborted"" . I have several VMs (Whonix 15, Whonix 15, Whonix 14) which usually work together (multiply workstation) and what is strange that one of them work normal (whonix 15) but the other two often crash together in one time. The difference between two whonix 15 is that in one installed psi+ v0.16 . I paid attention to version on psi+ special because it's the version for jessie, some plugins in it work better than in new one. Maybe is that the reason? One more thing I want to note is that I am not cloned first Workstation 15 when I made second Workstation 15 , I just imported all machines again from OVA and then delete second gateway which I didn't need , leaving the second workstation 15.

Info about host

System:    Host: user Kernel: 4.15.0-91-generic x86_64 bits: 64 gcc: 7.4.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu4) dm: lightdm Distro: Linux Mint 19 Tara
CPU:       Quad core Intel Core i7-8550U (-MT-MCP-) arch: Kaby Lake rev.10 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15936
           clock speeds: min/max: 400/4000 MHz 1: 1900 MHz 2: 1900 MHz 3: 1900 MHz 4: 1900 MHz
           5: 1900 MHz 6: 1900 MHz 7: 1900 MHz 8: 1900 MHz
Graphics:  Card-1: Intel UHD Graphics 620 bus-ID: 00:02.0 chip-ID: 8086:5917
           Card-2: NVIDIA GP108M [GeForce MX150] bus-ID: 01:00.0 chip-ID: 10de:1d12
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nouveau (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.05hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
           version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d71
           Sound: Advanced Linux Sound Architecture v: k4.15.0-91-generic
Partition: ID-1: / size: 901G used: 452G (53%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 705M used: 368M (57%) fs: ext4 dev: /dev/nvme0n1p2
           ID-3: swap-1 size: 17.02GB used: 0.70GB (4%) fs: swap dev: /dev/dm-3",CatJump
19423,full crash of host machine,Linux,VirtualBox 6.1.4,2020-03-23T02:23:17Z,2020-03-23T02:23:17Z,2020-03-23T02:23:17Z,"This report is going to be very incomplete for now.  I'll update it, if I can get some instruction on what and how to collect some better detail.  I am getting this crash half a dozen times a day when working in the environment

Environment:
Host Fedora 31 workstations 5.5.10-200.fc31.x86_64
dual monitors
16GB memory, 4 cores
Guest Fedora 31 workstations 5.5.10-200.fc31.x86_64
single monitor
6GB memory, 2 cores
Large window, slightly extending past the physical monitor size
scaled mode
Running guest application: qtcreator, debugging an application

The symptoms, just before the hard (black screen) crash of the host:

Attempt some operation in qtcreator, like clicking to create a new breakpoint.  The application freezes, the VM freezes, and all other applications windows except shells freeze.  Freeze might not be quite right.  Clicking on an application window on the host (2nd monitor) that is occluding a shell window activates the shell not the application window.  So the application might already be dead, and just a ghost of the window left on the desktop.  The shell window seems active, but not much time to look around.  In a few seconds, the host goes into full black screen crash, with a blinking text cursor.  Sometimes, in a few more seconds, the host login windows appears without any additional user actions.  Sometimes, ctrl+alt+del will initiate a reboot.

So, is there anything I can enable ahead of time, to get a log that might be useful for tracking this down?  What data can I collect after host reboot to include here?

I have other fc31 guest vms that are not crashing, so there is some interaction with the running applications.  But a misbehaving application should not crash the VM, and definitely should not crash the host machine.",mMerlin
16450,VM locks up when setting --discard and --nonrotational and using fstrim,Linux,VirtualBox 5.1.14,2017-02-04T02:32:50Z,2020-03-21T16:49:41Z,2020-03-21T16:49:41Z,"I changed the settings of my Xubuntu VM to emulate an SSD:

{{{
VBoxManage storageattach Xubuntu --storagectl SATA --port 0 --discard on --nonrotational on
}}}

After that started the VM. Everything runs fine until running fstrim in the VM. First the VDI file is shrinked a bit, then VirtualBox starts continuously reading from host filesystem (I guess from the VDI file). After some time the VM guest OS reports storage problems (timeouts) in dmesg output. No access to emulated storage is possible after that, but VM continues to run (e.g. scrolling in windows, moving mouse, ...). See attached VM screenshots and VBox.log for details.

I already observed the same behavior with a Windows 10 VM which locked up in the same way, but then I did not record any logs or error information.

Problem seems to be similar to ticket #15509.

Host info: Kubuntu 16.10 64 Bit, VirtualBox 5.1.6 (installed from Kubuntu repository)

Guest info: Xubuntu 16.10 64 Bit, 1 SATA controller, 1 VDA file with dynamic size

Please tell if any more information is needed.",Motlib
19295,"VM reset (""HeartbeatFlatlinedTimer"") under load",Linux,VirtualBox 6.0.16,2020-02-07T04:23:25Z,2020-03-02T16:10:23Z,2020-03-02T16:10:23Z,"Since upgrading to 6.1.2, I'm seeing reboots during guest backup runs.

The guest is Linux 2.6.22.14-100 #1 SMP Wed Apr 8 18:07:54 EDT 2015 i686 i686 i386 GNU/Linux

Prior to the upgrade, this was never seen.

The backup is tar (some excludes) -czpf (NFS mountpoint) |tee (log) | grep -v (noise)

A full backup is about 75GB; the crashes generate between 3 and 40GB before the crash.

Log file attached.

The relevant log lines appear to be:

{{{
90:00:58.137957 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
90:01:56.653151 Reset initiated by keyboard controller
90:01:56.682588 Changing the VM state from 'RUNNING' to 'RESETTING'

}}}

Let me know if you need more info.

Is there a way to disable either the detection or the reset action until a fix is available?

I'd like to be able to complete a backup!

",Timothe Litt
18420,'Solid State Disk' setting after snapshot not detected by Linux 4.15.0 guest,Linux,VirtualBox 5.2.26,2019-02-06T22:29:59Z,2020-02-28T14:58:57Z,2020-02-28T14:58:57Z,"Same symptom as with https://www.virtualbox.org/ticket/12025 :
""Solid State Disk"" is checked in VBoxManage but the guest does not recognize that, and `cat /sys/block/sda/queue/rotational` in the guest gives ""0""

Host: Ubuntu 18.04;   Guest: Ubuntu 18.04 (kernel 4.15.0)

NOTE: ""Solid State Disk"" was checked only after taking a snapshot. There is only one snapshot.

Possibly relevant: VBox.log (attached) mentions both the snapshot and original vdi, and ""NonRotatingMedium"" is set for the snapshot.  Here's an extract:

[/Devices/ahci/0/LUN#0/Config/] (level 5)
   Mountable           <integer> = 0
   NonRotationalMedium <integer> = 1
   Path                <string>  = "".../Snapshots/{d5ad9312-a011-4939-b281-a71f223ae696}.vdi"" (cb=93)
   
 [/Devices/ahci/0/LUN#0/Config/Parent/] (level 6)
   Path   <string>  = "".../disk1.vdi"" (cb=64)


",Jim Avera
19351,Ubunutu 18.04 kernel 5.4.0 suplibOsInit VERR_VM_DRIVER_NOT_INSTALLED ENOENT,Linux,VirtualBox 6.1.4,2020-02-26T21:18:23Z,2020-02-26T21:29:56Z,2020-02-26T21:29:56Z,"Failure to start vm, error seems to be independend on the image
Bug is reproducible with 
'''host info'''
❯ uname --a  
Linux incbook 5.4.0-050400rc7-generic #201911102031 SMP Mon Nov 11 01:34:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

''secure boot disabled''

'''virtalbox install'''
https://www.virtualbox.org/wiki/Linux_Downloads
version for bionic, 
VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.9.5)

'''image independent'''
reproducible with latest dsl image from https://sourceforge.net/projects/virtualboximage/files/Damn Small/4.4.10/dsl-4.4.10-x86.7z/download?use_mirror=netcologne

'''Error message'''

Failed to open a session for the virtual machine dsl-4.4.10-x86.

The virtual machine 'dsl-4.4.10-x86' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}



Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

'''attempts to fix/reinstall don't help'''

❯ sudo /sbin/vboxconfig          
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

",rtychko
19197,vmdk not visible after shutdown,Linux,VirtualBox 5.2.34,2020-01-04T10:15:11Z,2020-01-04T14:29:46Z,2020-01-04T14:29:46Z,"Hi,

I have come acros a problem.
I downloaded mininet-vm from [1].
I opened virtualbox
I selected file
I selected import appliance
The vm booted
I shut down the vm
I closed virtualbox
I opened virtualbox again
I clicked on the ""Mininet-VM"" virtual machine
the prompt with initramfs appeared.
I closed the virtual machine by pressing x from the window
I right clicked the virtual machine
I selected properties
I went to storage
I reselected the vmdk for the VM which came with the mininet-vm from mininet download folder
it worked.

Thanks",cric
19183,Auto-resize feature not working,Linux,VirtualBox 6.1.0,2019-12-23T12:53:14Z,2019-12-31T14:35:14Z,2019-12-31T14:35:14Z,"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA; Guest Additions 6.1.0

Enabling ›auto-resize‹ in guest window (›View‹ – ›Auto-resize Guest Display‹) has no effect. Manual resizing of display works fine.",phaidros
18820,No sound on 5.2.32 Linux guest on Linux host,Linux,VirtualBox 5.2.32,2019-08-08T05:31:36Z,2019-12-25T08:55:48Z,2019-12-25T08:55:48Z,"I first reported this issue on July 18 here:
https://forums.virtualbox.org/viewtopic.php?f=7&t=93940

For the following weeks I tried playing with various configurations including .asoundrc and asoundrc.conf, the VB audio settings and tools like alsamixer and not a peep. It was extremely frustrating

Sound worked just fine on a quick boot up in qemu. I was about to give up on VB when someone with the identical problem replied to the above thread reporting that reverting to 5.2.18 corrected it. Doing so corrected the issue for me also.

There are logs attached to the above-mentioned thread.  I was also emailing various logs and command output to someone for assistance so may have something else useful in history.

Here are my system specs:

Host: Devuan Jessie 32 bit

Guests: Devuan ascii and Devuan Beowulf also 32 bit, of course.

I was using these VMs for package testing and had not previously tested audio.

Thanks you and hope that you can find the bug and correct it.

",nauved
19182,Enabling 3D-acceleration hangs boot,Linux,VirtualBox 6.1.0,2019-12-23T12:49:13Z,2019-12-23T12:49:13Z,2019-12-23T12:49:13Z,"VBox 6.1.0 – Version 6.1.0 r135406 (Qt5.9.5)

Host: Ubuntu 18.04; 4.15.0-72-generic #4.15.0.72.81

Guest: Manjaro Linux 18.1.4, 4.19.88-1-MANJARO

Guest: VBoxSVGA, 3D enabled; Guest Additions 6.1.0

Box freezes at boot after boot menu and short appearance of bootup messages. This occurs with bith Chipsets, PIIX3 and ICH9.

Problem disappears when disabling 3D in VM settings.

Possibly a duplicate of Ticket #18914, as under 6.0.10 the problem did not appear and 18914 is for VB 6.0.12.",phaidros
19128,Kernel bug (vboxdr - VBoxNetFlt) - eth device unintentionally enters promiscuous mode,Linux,VirtualBox 6.0.14,2019-12-03T21:42:59Z,2019-12-04T06:44:26Z,2019-12-04T06:44:26Z,"Hello, 

When a natnetwork definied. For a while, after some reboots of VM, when VM just started Linux Kernel shows problems.
It is reproducabe: make a new natnetwork eg. like this:

{{{

$ VBoxManage natnetwork add --netname anyad \
--network ""192.168.15.0/24"" --enable --ipv6 on \
--port-forward-4 ""www:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-4 ""ssh:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-4 ""ssl:tcp:[]:10443:[192.168.15.10]:443"" \
--port-forward-6 ""www_ipv6:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-6 ""ssh_ipv6:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-6 ""ssl_ipv6:tcp:[]:10443:[192.168.15.10]:443
}}}
""


{{{
$ VBoxManage dhcpserver modify --ip 192.168.15.3 --netmask 255.255.255.0 \
--netname anyad --lowerip 192.168.15.10 --upperip 192.168.15.100
}}}


Then you select natnetwork definied above for VM. After some rebootings of VM there will be Kernel messages just when you start the affected VM like this:


{{{
[ 6693.723692] vboxdrv: 0000000000000000 VMMR0.r0
[ 6693.850079] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 6693.896097] VBoxNetFlt: attached to 'enp3s0' / xx:zz:xx:zz:xx:zz
[ 6693.901656] vboxdrv: 0000000000000000 VBoxEhciR0.r0
}}}

No need VM to start the guest OS totally, as soon as VM begun to run the Kernel messages sign.
When VM will be just stopped, Kernel message will be like this:
{{{

[ 6355.406993] device enp3s0 left promiscuous mode
[ 6356.691870] vboxnetflt: 0 out of 9668 packets were not sent (directed to host)

}}}

Temporary workaround:

{{{
$ VBoxManage natnetwork remove --netname anyad
$ VBoxManage dhcpserver remove --netname anyad
}}}

After re-make a new natnetwork with same option like above I wrote.


Affected VB versions: 6.0.14 and 6.1.0_RC1 r135151[[BR]]

Affected Kernel: Linux 5.0.0-36-generic",petervagyok
19074,"VM Stuck in ""offline snapshotting"" state",Linux,VirtualBox 6.0.10,2019-11-08T19:05:39Z,2019-12-03T19:22:03Z,2019-12-03T19:22:03Z,"The active problem is that a VM is stuck in ""offline snapshotting"" state and I can't do anything with it.  I need a way to get it out of that state, hopefully without corrupting the VM along the way.

There is no relevant VM-specific log information.  Since it's an offline snapshot, the VM wasn't running at the time, so the most recent log ends with ""Machine state changed to 'PoweredOff'"".

There appears to be no relevant info in the ~/.config/VirtualBox log files either.  Just a bunch of messages about saving config files and the reaper running.

Here's how I got to where I am:
I'm working on a Perl+Curses TUI front-end for a headless !VirtualBox server. It uses the vboxwebsrv webservice via the `SOAP::Lite` package to interact with !VirtualBox. I am following the API documented in the latest SDK from Oracle (6.0.10).

When my scripts initiate a snapshot of a powered-off machine via `IMachine::takeSnapshot`, the VM then becomes stuck in ""offline snapshotting"" state (""stuck"" as in it's been in that state for over 2 months as of the time of this writing). This is what the script does:

1. Get an `ISession` object via `IWebSessionManager::getSessionObject`
2. Lock the session in Shared mode via `IMachine::lockMachine`
3. Get a mutable `IMachine` object with `ISession::getMachine`
4. Initiate the snapshot from the mutable `IMachine` object, getting an `IProgress` object, with `IMachine::takeSnapshot`
5. Start a modal window which periodically queries the `IProgress` interface for its status until `IProgress::complete` returns `true`

As I'm reviewing my code to write this, I note that it's possible that `ISession::unlockMachine` is being called before the `IProgres`s object reports success. Although the documentation implies that a session remains locked as long as it is busy even after a call to `ISession::unlockMachine`, I wonder if this may be causing !VirtualBox to do something bad resulting in the stuck ""offline snapshotting"" state.

Environment info:
* Host OS is Debian Buster 64-bit.
* Guest OS is Windows 7 Ultimate 32-bit.
* VBoxHeadless --version gives 6.0.10r132072.
VBox.log does not get anything written to it.
I'm happy to do whatever data collection is necessary to troubleshoot this; just let me know what I need to do.",Brian of the Pines
18999,openSUSE install links broken,Linux,VirtualBox 6.0.12,2019-10-10T13:29:11Z,2019-10-10T13:29:11Z,2019-10-10T13:29:11Z,"Following the instructions and links on https://www.virtualbox.org/wiki/Linux_Downloads (OpenSUSE) section and it appears the links do not point to the appropriate files on your servers. 

The following terminal output showing errors below:

peter@localhost:~> sudo rpm --import oracle_vbox.asc

[sudo] password for root:
 
peter@localhost:~> wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -
error: -: import read failed(0).

peter@localhost:~> zypper refresh

Root privileges are required to run this command.

peter@localhost:~> sudo zypper refresh

Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.
                                                    
Repository 'openSUSE-Tumbleweed-Oss' is up to date.
                                                        
Repository 'openSUSE-Tumbleweed-Update' is up to date.
                                                     
Retrieving repository 'VirtualBox for openSUSE 20191004 - x86_64' metadata .........................[error]

Repository 'VirtualBox for openSUSE 20191004 - x86_64' is invalid.

[virtualbox|http://download.virtualbox.org/virtualbox/rpm/opensuse/20191004/x86_64] Valid metadata not found at specified URL

Please check if the URIs defined for this repository are pointing to a valid repository.

Skipping repository 'VirtualBox for openSUSE 20191004 - x86_64' because of the above error.

Some of the repositories have not been refreshed because of an error.

peter@localhost:~> ^C

peter@localhost:~>

Another problem for noobs is the error in instruction missing the ""sudo"" root user authority - easy to correct this one as terminal gives the correct advice. (""instruction to run zypper refresh"")

I cannot find any advice on how the following can be implemented ""Users of openSUSE can add  the openSUSE repo file to /etc/zypp/repos.d/."" How is this done and where? This needs more instruction please.



",ozfossil
18988,Wrong time synchronization,Linux,VirtualBox 6.0.8,2019-10-07T18:06:47Z,2019-10-08T21:37:47Z,2019-10-08T21:37:47Z,"Hello,
I noticed that time is not running right when I'm offline (when I'm online, everything works).
For example: When I start virtual machine at 7:30 and I look to time after 10 minutes, on my host is 7:40, but on guest is 7:38. After next 10 minutes on host is 7:50 and on guest is 7:47...
Sync time settings on VirtualBox are default (I do no changes).

Thank you",max-m
10811,MAC addresses filtered by VBox bridging,Linux,VirtualBox 4.1.18,2012-08-07T02:59:11Z,2019-09-12T16:25:43Z,2019-09-12T16:25:43Z,"I am attempting to run an OpenVPN server in a Ubuntu 12.04 (server) guest machine running on a Ubuntu 12.04 (server) host via VBoxHeadless.  This OpenVPN server needs to run as a layer 2 VPN (tap) which means it will place clients onto the local LAN with their own MAC addresses visible, and these clients need to be capable of two-way communication at layer 2.  I have been using the bridged network adapter for the VM.

When run from within the VM, I can connect clients to this server and ping/log into the server's IP, (guest machine) but I cannot access the Host's IP or anything else on the LAN from the client.  If I set up the OpenVPN server identically on the host, (Which is the same OS and otherwise identical setup) it works fine.  OpenVPN requires setting up a bridge internally on the server for this kind of layer 2 tap VPN, and putting the ethernet interface into promiscuous mode.  I've tried attaching the VM bridged adapter to the physical eth0 interface of the host and also to a bridged adapter on the host that was then bridged to the eth0 interface while eth0 was in promiscuous mode (similar to the setup on the guest)

I have found two other references to this problem, one with a Linux host, the other with Windows.  The Windows one was ticket #8965.  Both references indicate that this bug was a regression between versions 4.0.4 and 4.0.6.  Since I'm using Ubuntu 12.04 and VBox 4.1.18, downgrading to VBox 4.0.4 to confirm this would be painful.

Looking at the changelog of 4.0.6, I suspect that I've found the culprit:
""Host-Only & Bridged & Internal Networking: fix for processing promiscuous mode requests by VMs, defaulting to switch behaviour ""

Not sure what is meant by ""switch behavior"" but a switch is nothing more than a many-port bridge, which will broadcast frames to all ports but the one it came in on if the MAC is not in the MAC table, will learn the source MAC of any frame and put it in the MAC table for the port it came in on, and will unicast learned MACs to the ports on which the MAC table says they reside.  This may be somewhat inconsistent with being able to specify a MAC for the bridged adapter of the guest (which I have also done in this case)  If the switch portion is not flooding unlearned frames out to the guest machine virtual ports and also learning new MAC entries from frames sent by those ports, then the behavior may be efficient, but it will also be incorrect for Guests with their interfaces in promiscuous mode.

This bug is closely related to #8965 and this version with the Linux host type is also referenced here: https://forums.virtualbox.org/viewtopic.php?f=7&t=42335&p=203067&hilit=openvpn#p203067
",Raltar
18815,No guest DHCP through host WiFi in bridged mode,Linux,VirtualBox 6.0.10,2019-08-06T13:32:14Z,2019-08-25T02:48:36Z,2019-08-25T02:48:36Z,"Hi there!

I'm experiencing problems with the combination host wifi, bridged mode and guest DHCP. I'm hoping not to create a duplicate.

- Host OS: Ubuntu 18.04
- Guest OS: Ubuntu 18.04
- Version 6.0.10 r132072 (Qt5.9.5)

The guest VM is sending DHCP Requests with its MAC address but gets no answer.
When debugging on the hosts wlan0 I see 2 DHCP Requests - 1 from the MAC of the guest VM and 1 with the MAC of wlan0 on behalf of the guest VM - but still no answer. I'm using tcpdump to trace packets.

Debugging of the DHCP server shows incoming request and outgoing answers.

Other physical devices get IP addresses.

A friend of mine with Windows 10 for the host OS sees the same problem.

There are hints on the net to change the adapter type from 'Intel PRO 1000 MT Desktop' to '... Server' - unfortunately without success for me.

On cable ethernet it works fine. The same goes for WiFi using manual IP address configuration on the guest OS.

Cheers!

JK
",JKu
18812,Ubuntu virtual machine fails to start,Linux,VirtualBox 6.0.10,2019-08-05T05:11:06Z,2019-08-05T05:11:06Z,2019-08-05T05:11:06Z,,bobocc
18778,STM32CubeIDE GDB start-up fails in VirtualBox with Ubuntu guests,Linux,VirtualBox 6.0.6,2019-07-21T19:39:47Z,2019-07-21T19:39:47Z,2019-07-21T19:39:47Z,"
I have tested all supported Ubuntu versions listed in UM2563 when installed as a VirtualBox guest
and STM32CubeIDE is installed in the guest operating system (Ubuntu 14.04, 16.04, 18.04).
Also Linux Mint Mate 19.1 and 19 are tested with similar results as VirtualBox guests.

VirtualBox versions is:

VirtualBox 6.0
VirtualBox Graphical User Interface
Version 6.0.6 r130049 (Qt5.9.5)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

VirtualBoxGuestAdditions VBox_GAs_6.0.6 is installed.
Oracle VM VirtualBox Extension Pack 6.0.8r130620 is installed in Oracle VM VirtualBox Manager.

THE ISSUE IS:
============

Only an unmodified code generated as a STM32Project.
All have the same behaviour where installation and compilation succeed but GDB start-up fails with the message:

Could not determine GDB version using command: /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --version

This is consistent in all Ubuntu versions and same with IDE versions 1.0.1 and 1.0.2.

When running the same command in a terminal session the response is as follows:

xxxxx@ubuntu1604base:~$ /opt/st/stm32cubeide_1.0.2/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.linux64_1.0.0.201904181610/tools/bin/arm-none-eabi-gdb --versionGNU gdb (GNU Tools for STM32 7-2018-q2-update.20190328-1800) 8.1.0.20180315-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""--host=x86_64-linux-gnu --target=arm-none-eabi"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word"".

When installed without virtualisation (in Linux Mint 19.1 Mate only) everything works as expected (no errors).

",mnu
18669,Virtualbox causes a leak in cursors as reported by xrestop,Linux,VirtualBox 6.0.8,2019-05-23T03:49:50Z,2019-07-17T13:44:52Z,2019-07-17T13:44:52Z,"I am seeing ""cursors"" as reported by xrestop constanly increasing, which I believe is leading to a leak in X11 which slowly but surely eats up all memory, forcing me to restart.

This has been happening for at least all of the 6.0 branch of virtualbox, but maybe earlier.

After searching, I found a similar comment suggesting the same thing:

https://www.virtualbox.org/ticket/15892?cversion=0&cnum_hist=14#comment:14

I graphed it out over a day or so, and I could see that it was constantly increasing whenever I was using the VM, but remained stable otherwise (graph attached).  It never went down.

I've attached a small screenshot video (for whatever reason, it seems gnome screenshot didn't actually capture the cursor... but you can see the link highlighting and the cursors value constantly increasing).

I would note it happens only the cursor switch when *not* in capture mode (i.e., turn off mouse integration and you can switch the cursor as much as you like and it never increases on the host).  Maybe for someone skilled in the art that could help pinpoint which library this is related to?

I am currently running 6.0.8 on Fedora 30, but as mentioned it has been happening before that and the original bug was in the 5.1 series.

I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1713162 too

",iwienand
18735,Certain VM (RedHat) crashing module VBoxNetFlt if launch any other VM,Linux,VirtualBox 6.0.8,2019-07-02T10:01:17Z,2019-07-02T10:01:17Z,2019-07-02T10:01:17Z,"I'm using come vms, but I have one merged from VMware with RedHat inside which crashing module VBoxNetFlt if start together with any other VM. If only ""problem"" VM launched - it's OK.
Crash accompanied with VirtualBox-Guru-Mediatation screen and after that there is no way to launch any VM (just not starting) until perform the full-reboot. 
Instead rebooting I've tried to reload modules VBox*, but module VBoxNetFlt cannot be unloaded with ""it's using"" reason (while it's not actually using).
Logs and dmesg included.",e01
7982,OVA file made with VirtualBox 4.0 can't be read by VMware ovftool,Linux,VirtualBox 4.0.0,2011-01-03T03:16:29Z,2019-07-01T22:52:08Z,2019-07-01T22:52:08Z,"I created a 32-bit openSUSE 11.3 virtual machine using VirtualBox 4.0.0 on a 64-bit openSUSE 11.3 host. The machine works fine. I then exported it to an OVA file using the Export wizard, which did not report any errors. But when I try to read it into VMware using VMware's ""ovftool"" conversion utility, ""ovftool"" reports an error:


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


I've attached the XML 'ovf' file - it is indeed calling this a 'virtualbox-2.2' machine, which the VMware tools apparently do not support. I haven't checked the VMware documents yet to see what they do support, but I can do that if you don't have that filed away somewhere.
",Ed Borasky
18725,WebCam passtrough doesn't properly pass format capabilities to guest GStreamer,Linux,VirtualBox 6.0.8,2019-06-25T07:19:42Z,2019-06-25T07:26:33Z,2019-06-25T07:26:33Z,"When attaching a webcam to a Guest OS using Devices->Webcams menu, resulting device in the Guest system reports following format capabilities to GStreamer:
{{{
...
0:00:00.206792405 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   MJPG
0:00:00.207621489 15881  0x88fee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
image/jpeg, width=(int)1280, height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1, 10/1, 5/1 };
...
}}}
(continues in similar fashion with similar formats)


This results in webcam being incompatible with CameraBin pipeline:

{{{
0:00:00.208131863 15881  0x88fee00 INFO        GST_ELEMENT_PADS gstutils.c:1227:gst_element_get_compatible_pad:<src-crop> Could not find a compatible pad to link to camerasrc-real-src:src
0:00:00.208198762 15881  0x88fee00 INFO                GST_PADS gstutils.c:1035:gst_pad_check_link: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209174846 15881  0x88fee00 INFO                GST_PADS gstpad.c:2378:gst_pad_link_prepare: trying to link camerasrc-real-src:src and src-crop:sink
0:00:00.209487092 15881  0x88fee00 INFO                GST_PADS gstpad.c:2434:gst_pad_link_prepare: caps are incompatible
0:00:00.209526143 15881  0x88fee00 INFO                GST_PADS gstpad.c:2529:gst_pad_link_full: link between camerasrc-real-src:src and src-crop:sink failed: no common format
0:00:00.209583393 15881  0x88fee00 INFO           GST_PARENTAGE gstbin.c:1799:gst_bin_remove_func:<camerasrc> removed child ""src-crop""
0:00:00.209642419 15881  0x88fee00 WARN                 default camerabingeneral.c:87:gst_camerabin_add_element_full:<camerasrc> error: linking src-crop failed
0:00:00.209701572 15881  0x88fee00 INFO        GST_ERROR_SYSTEM gstelement.c:2145:gst_element_message_full_with_details:<camerasrc> posting message: GStreamer error: negotiation problem.
}}}


While on guest system or when attaching as a regular USB device, it reports the following format capabilities:
{{{
...
0:00:00.213225446 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:1202:gst_v4l2_object_fill_format_list:<camerasrc-real-src-actual-src-v4l:src>   YUYV
0:00:00.213341622 15913  0x92dee00 INFO                    v4l2 gstv4l2object.c:4136:gst_v4l2_object_probe_caps:<camerasrc-real-src-actual-src-v4l:src> probed caps:
video/x-raw, format=(string)YUY2, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
video/x-raw, format=(string)YUY2, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 15/1 };
...
}}}

And everything works fine. This makes a webcam incompatible with any application that uses gstreamers' camerabin, for example, a Qt applications.

Attached are exempts from different logs, but there isn't much of interest except for what is provided.

This has been tested on two Host 64-bit machines running Arch Linux and Ubuntu 18.04, with 64-bit Ubuntu 18.04 Guest and another 32-bit Linux-based Guest OS. Results are identical.",SuperPrower
18721,vdi disk got filled up and now VirtualBox refuses to revert to an earlier snapshot,Linux,VirtualBox 5.2.18,2019-06-22T14:31:49Z,2019-06-22T21:39:05Z,2019-06-22T21:39:05Z,"Hello,

I am running VritualBox 5.2.18, host OS being Ubuntu 18.04 and guest being Mint 19. 

In Mint I have a riscv/rocket-chip environment setup in order to simulate behavior of a processor and observe its output waveforms, given the input in the form of c/assembly programs. Once I had installed the Mint OS I created a snapshot, and then again, once I had setup the environment, I created another snapshot and only then moved on to run different simulations.

The output waveform files do tend to get big, so my VDI is 110 GB fixed-size. Nevertheless, yesterday the simulation went on and on, and the output waveform file simply filled the whole VDI, completely. 

That I conclude from this is the message I get when I try turning the VM in its current state:


{{{
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}


So, ok - it makes sense: the file got to big, filled up the disk, the VM can't boot. Ok, no problem there. However, once I tried bringing back the snapshot (either one of them), I get:


{{{
Failed to restore the snapshot intenuser of the virtual machine rockettest.

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
}}}


And this, definitely, is not ok - it brings me into a terrible position, as it completely destroys the work on setting up everything.

I tried increasing size of the VDI, but for some reason - I am not allowed to type in the new size (image attached - 1).

VirtualBox does allow me to enter the new size for a snapshot (image attached - 2), but once I click Apply, that leads to a new error:


{{{
Failed to resize the storage unit of the hard disk /media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi from 100.00 GB to 120.00 GB.

Could not resize medium '/media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi' (VERR_DISK_FULL).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}


Please help.",dndrdm
18720,Host system freezes as soon as the mouse pointer enters the VM on nVidia,Linux,VirtualBox 6.0.8,2019-06-22T10:07:00Z,2019-06-22T16:19:15Z,2019-06-22T16:19:15Z,"Host system freezes immediately when mouse pointer enters the VM when running on nVidia with proprietary drivers. I tried to disable nVidia and run on Intel HD and the issue is not reproducible.
The rest of the system is perfectly stable when running on nVidia.
These are two logs of Virtualbox with different graphics controllers:

https://pastebin.com/azj2dG3v
https://pastebin.com/uCcQ45jL

After the mouse pointer enters the VM, the host freezes, so I cannot control the system anymore, I can only send sysrq and reboot. If I check kernel messages after the boot, this is what I found at the end of the previous session:

https://pastebin.com/n83NqFhA

I do not know where the issue comes from, so I tried to report the issue also to nVidia here:

https://devtalk.nvidia.com/default/topic/1056067/linux/virtualbox-freezes-my-system-when-on-nvidia-but-not-when-on-intel-hd/

but I thought I could also report to Virtualbox and see if together we can find a fix.

Host system is Kubuntu 19.04. Guest system I tried are KDE Neon and Kubuntu 19.04. I tried with official VirtualBox 6.0.8.",Luca Carlon
18711,SCSI port 7 can not be used,Linux,VirtualBox 5.2.30,2019-06-15T08:59:45Z,2019-06-16T13:34:02Z,2019-06-16T13:34:02Z,"[root@rac01-priv ~]# lsscsi -d
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda [8:0]
[2:0:0:0]    disk    VBOX     HARDDISK         1.0   /dev/sdb [8:16]
[2:0:1:0]    disk    VBOX     HARDDISK         1.0   /dev/sdc [8:32]
[2:0:2:0]    disk    VBOX     HARDDISK         1.0   /dev/sdd [8:48]
[2:0:3:0]    disk    VBOX     HARDDISK         1.0   /dev/sde [8:64]
[2:0:4:0]    disk    VBOX     HARDDISK         1.0   /dev/sdf [8:80]
[2:0:5:0]    disk    VBOX     HARDDISK         1.0   /dev/sdg [8:96]
[2:0:6:0]    disk    VBOX     HARDDISK         1.0   /dev/sdh [8:112]
[2:0:8:0]    disk    VBOX     HARDDISK         1.0   /dev/sdi [8:128]
[2:0:9:0]    disk    VBOX     HARDDISK         1.0   /dev/sdj [8:144]
[2:0:10:0]   disk    VBOX     HARDDISK         1.0   /dev/sdk [8:160]

As you can see, when I attach disks to SCSI controller, I can never use the 7th one:  [2:0:7:0]. My OS is oracle linux 7.6",Nil
18693,Memory Leak in VirtualBox 6.0.8,Linux,VirtualBox 6.0.8,2019-06-07T00:05:41Z,2019-06-08T07:34:02Z,2019-06-08T07:34:02Z,"Hello,

It seems like there's a memory leak in VirtualBox 6.0.8.

I'm running with a Linux host (Ubuntu 16.04) and a single Linux guest (Ubuntu 16.04) in headless mode, being accessed by another machine on the network via Virtualbox's RDP server.

What I see is that the ""VBoxHeadless"" process consumes more and more memory as time goes on, at a rate of about 100 MiB every few minutes. This continues indefinitely until the system runs out of memory.

The only thing running on the guest is an instance of Firefox with some web-based FB game.

I've attached the log and vbox file. Please let me know if there's anything else needed.

As of now, the system is up and running, consuming more and more memory.

Thanks,
Jake",unklejoe
18582,Slow startup,Linux,VirtualBox 6.0.6,2019-04-19T10:11:04Z,2019-06-07T06:38:42Z,2019-06-07T06:38:42Z,"Ever since VB 6.x, start up process of the VM is extremely slow. However, if performing multiple mouse clicks in a quick succession (10+) during the process, start up will perform almost in normal speed.

Virtual Machine is Android x86 project, version 8.1-r1",blubber
18650,Ubuntu Issues,Linux,VirtualBox 6.0.8,2019-05-15T22:45:57Z,2019-05-23T08:21:01Z,2019-05-23T08:21:01Z,"Good Evening,

I just wanted to raise an issue I have with Ubuntu on VirtualBox. I have tried increasing the memory, changing from dynamic to fixed memory, changing CPUs as well as changing various advanced settings.

I tried on a different laptop and it worked fine with 18.04, I exported the appliance and importing it onto this laptop failed. The only difference is that Hyper-V is not installed on the other laptop though it is on this. I saw there may be an issue with Hyper-V but I use both VirtualBox and Hyper-V.

I'd just like to raise this as a defect, and also this has been an issue on the current version and the base 6.0.0",MitchB
18616,Shared Folder error when using reposync,Linux,VirtualBox 6.0.6,2019-05-02T02:51:55Z,2019-05-07T05:39:21Z,2019-05-07T05:39:21Z,"I have a couple of VMs (specifically CentOS6 and CentOS7) that I use to sync repositories for a disconnected network. EPEL, Cloudera, MySQL, etc. I keep these VMs pretty lean and but mount Shared Folders to a USB so that I can transfer the files. I download the files in the repos directly to the Shared Folder. For example to update the EPEL6 repository. I cd into a directory on the Shared Folder and use the command, reposync -n -d -r epel6. Since 6.0.6 this causes errors. To test it I tried a created a new directory and here is a sample output from one of the first attempted download:

[jrather@localhost sat]$ reposync -n -d -r epel6
[epel6: 1     of 12532 ] Downloading Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm
Could not retrieve package 2048-cli-0.9.1-1.el6.x86_64. Error was failure: Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm from epel6: [Errno 256] No more mirrors to try.

I get errors on every file. If I try the command within a directory on the VM (for example, /tmp or my user's home directory) everything is fine. It is only with the Shared Folder or trying to write to it. This error occurs with the CentOS7 guest too. I have tried it from both CentOS7 host and Ubuntu 18.04 host both with Guest Additions installed. I have also tried using a physical disk for the Shared Folder instead of USB drive with the same results. This used to work fine with 6.0.4 and previous versions.

I am not sure what else to submit but would be more than happy to if instructed.",jim.rather
18619,VirtualBox 6.0.6 VM guest boot hangs with customized Fedora 30 Remix,Linux,VirtualBox 6.0.6,2019-05-03T20:32:07Z,2019-05-03T21:46:33Z,2019-05-03T21:46:33Z,"I am creating a customized 64bit Fedora 30 Remix called Untochat. It is a Live Linux that allows you to install to harddisk, too. Live image boots fine with VirtualBox and installation to (virtual) VDI disks succeeds as well. But when booting the newly installed Untochat9 from disk, the boot never reaches graphical login screen.

The problem is deterministic, but I am unable to debug this myself. To reproduce the problem, Untochat ISO image (1.4GB) can be downloaded from:

  https://kolttonen.fi/iso/untochat9.iso

My main host is stock Fedora 30, but the same problem occurs on host MacOS Mojave 10.14, too.

Using libvirt + qemu + kvm on Fedora 30 host, everything works fine, so I suspect this could be a bug in VirtualBox 6.0.6. ",KaleviKolttonen
18571,Vboxmanage export / import not working - invalid 'ovf:id' attribute,Linux,VirtualBox 5.2.28,2019-04-18T06:58:57Z,2019-04-19T08:05:40Z,2019-04-19T08:05:40Z,"I'm running am Ubuntu 18.04.2 LTS Server with Virtualbox 5.2.28

Exporting an virtual machine with command line works without any reported error. Result is an *.ova file.

Importing this machine with the command vboxmanage import file.ova ends with this error:

root@nono2018:~# vboxmanage import 20210417_ADC2.ova
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Error reading ""/root/20210417_ADC2.ova"": missing or invalid 'ovf:id' attribute in operating system section element, line 18
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 307 of file VBoxManageAppliance.cpp

If I open the *.ova file with a editor, i can see
<Section xsi:type=""ovf:OperatingSystemSection_Type"" ovf:id=""-1160446143"">

Why is the ovf:id negativ?

Any suggestion to solve the problem?

Regards
Michael",Curval1230
16720,Sound randomly stops working until vm restarted (Fedora vm on Debian host running VirtualBox 5.1.18),Linux,VirtualBox 5.1.18,2017-05-02T19:41:59Z,2019-04-18T20:53:26Z,2019-04-18T20:53:26Z,"It happens very often that the sound stops working after a vm has been running for more than a day.

To clarify: ""Sound stops working"" means just that. For example, an audio file would be played in VLC and no sound would be produced (volume settings have not been changed).

There's a hint that it must have something to do with VirtualBox: After restarting the vm, it works again. It's not even necessary to restart the guest system. The vm can be suspended while VLC is running, it's then immediately resumed and as soon as it's running again, the sound is working again, the music played by VLC will come out.

This is an annoying bug because the vm has to be suspended/resumed all the time and sometimes that's not possible when certain connections should no be disrupted.

Nothing is logged in VBox.log. Host audio driver is PulseAudio, audio controller is ICH AC97 (default settings). Guest OS is Fedora 25. Host OS is Debian 8. VirtualBox 5.1.18.",Philip Seeger
18525,Cannot launch Virtual Machine - Argument aWidth is invalid,Linux,VirtualBox 6.0.4,2019-03-27T11:06:59Z,2019-03-27T11:06:59Z,2019-03-27T11:06:59Z,"I can not launch any of my former created or new created VMs.

VirtualBox Guru Medition Error is showing up. Fatal Error (my translation from german text showing up)

Host: Ubuntu 18.04
Guest: any

Ataching log to investigate error.

Thanks for good work!",Mate
18064,Audio/Video out of sync for Linux guest (since 5.2.20),Linux,VirtualBox 5.2.20,2018-10-20T14:55:24Z,2019-03-26T03:15:54Z,2019-03-26T03:15:54Z,"Host: Ubuntu 16.04
Guest: Ubuntu 16.04

Playing video (e.g. in FF Browser on YouTube) always has audio out of sync (audio lagging behind).
Problem is reproducible.

The problem is NOT present for Windows 10 guests on same host system.

The problem was NOT present on VBox 5.2.18 and has been introduced with VBox 5.2.20.",sunrider
18488,standard tty control sequences ignored in all VM's,Linux,VirtualBox 6.0.4,2019-03-11T19:58:49Z,2019-03-24T00:24:35Z,2019-03-24T00:24:35Z,"Running ubuntu 15.04 Server as well as newer Ubuntu Server VM's as well as RH and Suse within VMs.  When using terminal the typical control sequences (ctrl+c, ctrl+v, ctrl+d, etc) are ignored.  The ctrl portion is eaten/suppressed and the following letter is displayed.   When I run showkey and repeat those the ctrl portion is ignored.  On the host os showkey shows the correct values.  I've even tried a different usb keyboard to make sure it wasn't that.
Trying to run and work on a tty without these controls is extremely frustrating.
I've been researching for almost a week now without any results.   Please address? Thanks",bobmct
18495,VirtualBox NAT alias option use-same-ports (--nataliasmode1=sameports) has no effect on Ubuntu 16.04 host OS,Linux,VirtualBox 6.0.4,2019-03-14T20:53:00Z,2019-03-14T20:53:00Z,2019-03-14T20:53:00Z,"== Steps to reproduce ==

    1. Create a VirtualBox VM as follows, accepting default values for anything not listed here:

        * Name: archlinux-2019.03.01-x86_64
        * Type: Linux
        * Version: Arch Linux (64-bit)

    2. Download archlinux-2019.03.01-x86_64.iso into the VM directory:

    {{{
cd 'VirtualBox VMs'/archlinux-2019.03.01-x86_64
curl -O http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/archlinux-2019.03.01-x86_64.iso
    }}}

    3. Confirm the MD5 checksum. First, display the expected checksum:

    {{{
curl http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/md5sums.txt
    }}}

    Verify on Linux:

    {{{
md5sum archlinux-2019.03.01-x86_64.iso
    }}}

    Verify on macOS:

    {{{
md5 archlinux-2019.03.01-x86_64.iso
    }}}

    4. Start the VM in VirtualBox, click '''Choose a virtual optical disk file''' (represented by a folder icon with an upward-pointing green arrow), and select the archlinux-2019.03.01-x86_64.iso file downloaded in Step 2.

    5. Boot the VM, selecting default options for everything.

    6. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), find two unused privileged (port number less than 1024) ports; for example, the following command will return nothing if both ports 1022 and 1023 are free:

    {{{
netstat -Wa | grep -E '1022|1023'
    }}}

    7. On the guest (64-bit Arch Linux 2019.03.01), confirm that the first free port from Step 6 is also free on the guest:

    {{{
netstat -Wa | grep 1022
    }}}

    If this  command returns any output, repeat Steps 6 and 7 until you have found two free ports.

    8. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), start listening on the second free port, the receiving port:

    {{{
sudo nc -l 1023
    }}}

    9. On the guest (64-bit Arch Linux 2019.03.01), open a connection to the receiving port on the host, originating the connection from the first free port, the sending port:

    {{{
nc -p 1022 ala-michaelk-lx1.corp.ad.wrs.com 1023
    }}}

    Replace `ala-michaelk-lx1.corp.ad.wrs.com` with the fully qualified domain name (FQDN) of the host, as returned by the `hostname -f` command.

    After running both `nc` commands, any text entered on the guest should appear on the host and vice versa.

    10. In another shell on host, look for connections to the receiving port:

    {{{
netstat -W | grep 1023
    }}}

    Initially observe that network address translation (NAT) has replaced the sending port (1022) with a random port (48946), as expected for `--nataliasmode1=default`:

    {{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48946 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48946 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
    }}}

    11. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), close the connection by pressing Ctrl-D (EOF) in the shell running `nc`.

    12. Close the guest console window, select '''Save the machine state''', and click '''OK'''.

    13. On host, switch the VM to `--nataliasmode1=sameports`:

    {{{
VBoxManage modifyvm archlinux-2019.03.01-x86_64 --nataliasmode1=sameports
    }}}

    14. In VirtualBox, click '''Start''' to restore the VM.

    15. Repeat Steps 8–11.

== Expected ==

The port number for the sending port (1022) is preserved, as seen on host macOS Mojave Version 10.14.3:

{{{
inu:~ michael$ netstat -W | grep 1023
tcp4       0      0  inu.corp.ad.wrs.com.1023  inu.corp.ad.wrs.com.1022  ESTABLISHED
tcp4       0      0  inu.corp.ad.wrs.com.exp2  inu.corp.ad.wrs.com.1023  ESTABLISHED
}}}

== Observed ==

The port number for the sending port (1022) is replaced with a random port number, as seen on host 64-bit Ubuntu Xenial Xerus 16.04.6 LTS:

{{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48972 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48972 ESTABLISHED
}}}
",interfrastic
18492,failure to install completely,Linux,VirtualBox 6.0.4,2019-03-12T23:55:27Z,2019-03-13T00:20:57Z,2019-03-13T00:20:57Z,"This is a new Fedora Core system (fc31/rawhide). 

Installation file is: VirtualBox-6.0.5-129304-Linux_amd64.run

Again, the execution of vboxconfig has failed. I know, it's expected. The problem is one that I seem to have seen A LOT. Eventually it gets fixed but it seems to come back (always(?)). Is the fix NOT being propagated to the development tree? Here's the same old message that I've been seeing:

     22    ./tools/objtool/objtool orc generate  --module --no-fp --retpoline /tmp/vbox.0/SUPR0IdcClient.o
     23 /tmp/vbox.0/linux/VBoxPci-linux.c: In function ‘vboxPciFileWrite’:
     24 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
     25   375 |     set_fs(get_ds());
     26       |            ^~~~~~
     27       |            get_fs
     28 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: incompatible type for argument 1 of ‘set_fs’
     29   375 |     set_fs(get_ds());
     30       |            ^~~~~~~~
     31       |            |
     32       |            int

Am I doing something wrong?

Best regards,

Obiewan (George)
",George R. Goffe
18446,Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available),Linux,VirtualBox 6.0.4,2019-02-22T03:34:40Z,2019-02-22T09:28:11Z,2019-02-22T09:28:11Z,"Hi,

I have linux laptop with with ubuntu 18.04 OS.

$lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic


I have virtualBox 6 installed in it. Below is the VBox details -

          Version 6.0.4 r128413 (Qt5.9.5)
          Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.

I have minidcos installed and tried to create virtual machine https://minidcos.readthedocs.io/en/latest/dcos-vagrant-cli.html# .

When I run the command `minidcos vagrant create ./dcos_generate_config.sh --agents 0` I get below error.

Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)

I have below permissions for my `/tmp` folder.

ajkumar@rajkumar:Downloads$sudo ls -ld /tmp
[sudo] password for rajkumar: 
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp
rajkumar@rajkumar:Downloads$ls -ld /tmp
drwxrwxrwx 9 root root 4096 Feb 21 21:14 /tmp






",rajpsgit
18447,libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory,Linux,VirtualBox 6.0.4,2019-02-22T03:47:38Z,2019-02-22T03:57:05Z,2019-02-22T03:57:05Z,"Hi,

I have linux laptop with with ubuntu 18.04 OS.

          $lsb_release -a No LSB modules are available.
            Distributor ID: Ubuntu Description: Ubuntu 18.04.2 
            LTS Release: 18.04
            Codename: bionic

I have virtualBox 6 installed in it. Below is the VBox details -

Version 6.0.4 r128413 (Qt5.9.5) Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.


When I tried to create virtual OS using virtual Box I get below error - 

 libffi-d78936b1.so.6.0.4: cannot open shared object file: No such file or directory

I have attached the completed error trace



",rajpsgit
18429,VirtualBox 5.2.26 fails to build due to VBoxFUSE,Linux,VirtualBox 5.2.26,2019-02-11T16:39:36Z,2019-02-12T10:57:52Z,2019-02-12T10:57:52Z,"Hello,

I'm using a fairly ancient system (Slackware 14.2), but the following is a bug I encountered building VirtualBox, and a patch that enabled me to build it successfully.

While trying to compile, I encountered this error:

{{{
  CXX     VBoxFUSE - {C}/VBoxFUSE.cpp
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:112:5: error: 'PVBOXHDD' does not name a type
     PVBOXHDD                pDisk;
     ^
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp: In function 'bool vboxfuseNodeDestroy(PVBOXFUSENODE, bool)':
/tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp:200:29: error: 'VBOXFUSEFLATIMAGE {aka struct VBOXFUSEFLATIMAGE}' has no member named 'pDisk'
             if (pFlatImage->pDisk)
                             ^
}}}

After searching through the source code, and scouring the internet, I could not find a reference to '''PVBOXHDD''' anywhere.

Finally I found a very old copy of vdfuse ([https://github.com/vasi/vdfuse/blob/7e10fc7aeeffae251042055bc55fb83a09120156/include/VBox/vd.h]) which defined '''PVBOXHDD''' as '''VBOXHDD''', and I found further details that revealed '''VBOXHDD''' could be referenced here as '''PVDISK'''.

I created the following patch:

{{{
--- /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE-old/VBoxFUSE.cpp      2018-10-15 10:31:04.000000000 -0400
+++ /tmp/SBo/VirtualBox-5.2.26/src/VBox/ImageMounter/VBoxFUSE/VBoxFUSE.cpp   2019-02-11 11:31:30.587919884 -0500
@@ -53,6 +53,7 @@
 #include <iprt/initterm.h>
 #include <iprt/stream.h>
 
+#define PVBOXHDD PVDISK
 
 /*********************************************************************************************************************************
 *   Structures and Typedefs                                                                                                      *
}}}

And upon continuing my build, it succeeded.",peterwwillis
18425,Spontanious guest hanging after rollback,Linux,VirtualBox 6.0.4,2019-02-11T08:55:10Z,2019-02-11T08:55:10Z,2019-02-11T08:55:10Z,"After a number of rollbacks to a certain live snapshot the guest (Ubuntu Server 16.04) seems to restore its state but becomes totally unresponsive. It just hangs on the prompt, the video doesn't change at all (even the cursor doesn't blink), and pressing any keyboard keys doesn't have any effect. Htop also shows that one of the cores is loaded 100% with the VBoxHeadless process. You may reboot the guest forcefully and it starts just fine. It's just I have to do a lot of rollbacks to live snapshots automatically that this occasional freeze bugs me big time.

P.S. If that makes any difference - I'm doing headless start instead of normal start

P.S.S. Bug seems to be very occasional - once in a few dozen times maybe
",CIDJEY
18323,Video Memory Expanding to 256 MB Fail,Linux,VirtualBox 6.0.2,2019-01-17T14:21:34Z,2019-01-19T21:27:44Z,2019-01-19T21:27:44Z,"Can no longer extend video memory to 256MB using the command line:

VBoxManange modifyvm ""vm name"" --vram 256

This creates an error upon boot up and stops boot.

Legacy machines created in VirtualBox 5.2 seem to work fine with this mod when installed on VB 6.0.",andrewf
18297,Can't unmount vdi file,Linux,VirtualBox 6.0.0,2019-01-10T22:59:09Z,2019-01-12T21:41:45Z,2019-01-12T21:41:45Z,"I just tried to gparted one of the vdi files and I am getting error unmount it. I have two VM setup both are Ubuntu 18.04 with latest updates

VM1 - is what I am booing into (fresh install)
VM2 - is what is attached as additional IDE or SATA to VM1

VM2 was cloned from VM1

Here is what I did try to do

1. in VM1 attach VM2 vdi file. I did try as IDE and SATA each time
2. Boot to VM1
3. Start gparted
4. Select /dev/sda (VM2)
5. Try to resize ext4 partition (Did checked it is not mounted)
6. Apply changes

It seams that /dev/sdb is VM1 what I booted into.

Resize fails

",oxoocoffee
18149,USB headset disconnection on windows host freezes linux guest,Linux,VirtualBox 5.2.22,2018-11-23T13:11:05Z,2019-01-10T18:02:43Z,2019-01-10T18:02:43Z,"After disconnecting a USB headset (sennheiser mb 660 uc ms) in the host system, the vm freezes (i.e. is no longer responsive to clicks or any other form of interaction including network access). The VirtualBox GUI is no longer responsive either. Repeatedly clicking in the guest window eventually causes it to abort and the VirtualBox GUI becomes responsive again.

Host: Windows 7 x86_64
Guest: Arch linux x86_64

",oksijun
18169,Guest Additions will not install properly in Centos,Linux,VirtualBox 5.2.22,2018-12-04T23:46:36Z,2018-12-14T10:19:53Z,2018-12-14T10:19:53Z,"{{{
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_unpin’:
/tmp/vbox.0/vbox_ttm.c:486:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
/tmp/vbox.0/vbox_ttm.c: In function ‘vbox_bo_push_sysram’:
/tmp/vbox.0/vbox_ttm.c:525:2: error: too many arguments to function ‘ttm_bo_validate’
  ret = ttm_bo_validate(&bo->bo, &bo->placement, false, false);
  ^
In file included from /tmp/vbox.0/vbox_drv.h:92:0,
                 from /tmp/vbox.0/vbox_ttm.c:31:
include/drm/ttm/ttm_bo_api.h:344:5: note: declared here
 int ttm_bo_validate(struct ttm_buffer_object *bo,
     ^
make[2]: *** [/tmp/vbox.0/vbox_ttm.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxvideo] Error 2
}}}",bc
16380,Mouse pointer disappears after VM resume,Linux,VirtualBox 5.1.12,2017-01-12T09:55:03Z,2018-12-11T20:44:10Z,2018-12-11T20:44:10Z,"When I resume my Linux VM, the mouse cursor is never visible when moved into the VM window.

The mouse appears to be working correctly, as I can see icons / menus become ""highlighted"" when I move the mouse around.

And mouse clicks also work as expected.

It's just that the cursor itself is invisible !!

This issue is never present when starting the VM from scratch.[[br]]
It *only* happens when starting from a suspend.

Host : Ubuntu 16.04.1 LTS (64bit)[[br]]
Guest : Ubuntu 16.04.1 LTS (64bit)

Both host and guest are fully up-to-date.",mpfj
18135,Guest network down with version 5.2 and e1000,Linux,VirtualBox 5.2.20,2018-11-17T15:07:25Z,2018-11-17T15:07:25Z,2018-11-17T15:07:25Z,"After an upgrade from 5.1.38-122592 to 5.2.20-125813 the guest network did not automatically come up. The network worked fine after bringing the interface down/up.
Another copy of the same VM running on different hardware with identical software did not have the problem.

Both VMs were using E1000 network adapters in bridged mode. Switching to either of the PCnet adapters fixed the issue on the ""not working"" system.

[Beware: User speculation] The not working system is slower and it looks like there was a recent change to the E1000 LinkUpDelay from 5000ms to 3000ms. I'm suspecting that the shortened delay may be related to the problem. I could not find a configuration setting for the LinkUpDelay.

Host systems: Debian 9 (stable) 64 bit (fully up to date)

Guest systems: Debian 9 32 bit (fully up to date)

About the VirtualBox version. I first noticed the issue on 5.2.20, but did not have a chance to gather logs until after upgrading to 5.2.22. Both versions have the issue.

Not working hardware:
{{{
  AMD Turion(tm) 64 Mobile Technology ML-34 (800 MHz single core)  
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
	Subsystem: Hewlett-Packard Company RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
	Flags: bus master, medium devsel, latency 128, IRQ 22, NUMA node 0
	I/O ports at a000 [size=256]
	Memory at c020a400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
	Kernel driver in use: 8139too
	Kernel modules: 8139cp, 8139too
}}}
Working hardware:
{{{
  Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (dual core, 800 MHz)  
  Ethernet controller: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
	Subsystem: Hewlett-Packard Company 6710b
	Physical Slot: 1
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at e4000000 (64-bit, non-prefetchable) [size=64K]
	Expansion ROM at <ignored> [disabled]
	Capabilities: [48] Power Management version 3
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-1c-c4-ff-fe-c9-02-6d
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: tg3
	Kernel modules: tg3
}}}",FixItDad
18100,Old DHCP leases interfere with changed server configuration,Linux,VirtualBox 5.2.20,2018-11-03T19:31:54Z,2018-11-03T19:35:58Z,2018-11-03T19:35:58Z,"Host: openSUSE Leap 15

virtualbox-host-kmp-default-5.2.20_k4.12.14_lp150.12.22-lp150.4.20.1.x86_64
virtualbox-host-source-5.2.20-lp150.4.20.1.noarch
virtualbox-5.2.20-lp150.4.20.1.x86_64
virtualbox-qt-5.2.20-lp150.4.20.1.x86_64

In short, the lease file for a NAT net must be deleted by hand. Otherwise the DHCP server (with a different IP) hands out the old leases (wrong IPs).",robert spitzenpfeil
18090,Virtualbox crashes on taking a snapshot,Linux,VirtualBox 5.2.20,2018-10-31T12:32:55Z,2018-10-31T23:23:29Z,2018-10-31T23:23:29Z,"I've just installed ubuntu 18.04.1 64bit on VirtualBox 5.2.20.
The installation was the minimal version of ubuntu, everything else at default settings.
My host is Ubuntu 18.04.1 64 bit, too.

After the installation I ran update and upgrade.
I installed gcc, perl, make and build-essential.

Then I ran the guest additions.

The system runs stable and without problems so far. But if I try to make a snapshot, the machine crashes reproducably.
I'm taking the snapshot while the machine is running. The window closes and the state of the machine is changed to ""aborted"".
No snapshot is taken.

Here is the logfile:
https://pastebin.com/f1dqGkxV",lhk
18068,NAT process infinite loop call `poll` function,Linux,VirtualBox 5.2.20,2018-10-22T07:42:56Z,2018-10-22T07:42:56Z,2018-10-22T07:42:56Z,"Host machine: Fedora 28
Guest machine: Windows 10

My guest system is Windows 10 and using NAT network, and Windows 10 system suddenly unable to access the Internet at some point, but my host machine can access the network normally. I using Wireshark capturing some ARP data flow in Windows 10:

{{{
1   0.000000 PcsCompu_7a:1a:df → RealtekU_12:35:02 ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    2   0.207297 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    3   3.718693 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    4   4.500012 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    5   5.500048 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    6   6.719889 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    7  10.721331 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    8  11.499537 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    9  12.500007 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   10  15.499582 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   11  16.721794 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   12  17.500389 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   13  18.500008 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   14  21.499517 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   15  22.725696 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   16  23.499997 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   17  24.499501 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   18  27.499508 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   19  27.982749 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   20  28.500004 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   21  29.500001 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   22  34.985277 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   23  35.500502 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   24  36.500023 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   25  38.248133 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   26  42.249642 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   27  42.999528 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   28  43.999519 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   29  47.235338 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   30  48.000015 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   31  49.000018 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
}}}

IP 10.0.2.2 is NAT's gateway address, as you see, my Windows system send some ARP broadcast packet to find 10.0.2.2's MAC address, but not recive any response packet.

At the same time, in my host machine, the `NAT` process occupies a lot of CPU resources. I using `strace` command tracing `NAT` process:

{{{
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
.......

}}}

as you see, NAT process infinite loop call `poll` function",lu4nx
18028,"Mouse wheel scrolling usually not working, cursor off, hotkeys not sent to vm, after moving to edge of screen",Linux,VirtualBox 5.1.0,2018-10-03T14:20:07Z,2018-10-03T14:20:07Z,2018-10-03T14:20:07Z,"This is not a new issue but I couldn't find a related bug report that's still open.

I believe the following issues may be related.

A) Mouse wheel scrolling usually doesn't work while ""mouse integration"" is not active (input captured). It always works fine at first, right after clicking or hitting Ctrl in the VM window to capture both mouse and keyboard. At some point, it stops working. Hitting Ctrl to release the mouse reveals that the host's mouse cursor is usually about half a screen away from the VM's cursor. After moving the host's cursor back to where the VM's cursor is and then clicking to recapture the input, it works again. But not for long.
This is happening so often that I tend to not use the mouse wheel at all and use the good old scrollbar buttons instead. Unfortunately, some desktop environments (Gnome/GTK) have lost the scrollbar buttons for whatever reason. In that case, the combination of a temporarily broken scroll wheel *and* a broken scrollbar makes it rather difficult to navigate through content (vertically and horizontally).

B) Whenever a VM is started, mouse integration is active by default, which means the VM's cursor is moved together with the host's cursor as long as it's within the VM window without requiring the user to click into the VM window first.
Unfortunately, the cursor is often way off. Sometimes even a third cursor would fit between the host's and the VM's cursor. I'll attach a screenshot.
This is one of the reasons why I usually disable mouse integration after starting a VM. But then, the first issue happens.

C) While mouse integration is active, hotkeys often don't work, i.e., they're not sent to the VM. For example, after starting a VM, you'd hit Alt + Tab while working inside the VM and you get the host's task switcher showing your open Virtualbox windows. What you actually wanted to do is switch windows inside the VM.
You have to first click somewhere inside the VM and then hit Ctrl to temporarily capture the keyboard and send hotkeys to the VM. I say temporarily because at random times, apparently when moving the cursor to the edge of the screen (but strangely not always), it stops working again and the next time Alt + Tab is used, it's sent to the host again.
This is the main reason why I have to disable mouse integration after starting a VM and then only interact with the VM with mouse and keyboard captured and locked inside the VM window.

D) This is just a minor glitch. I don't remember when I first noticed that but it wasn't always like this. The user interface bar at the top of the screen gets stuck, covering that area in the VM. That's particularly annoying if the DE's panel (task bar) is at the top of the screen. This is solved by moving the host's cursor over the user interface panel and back in the VM, then it disappears normally.

E) This is not a glitch, just a note: When mouse integration is disabled but the input controls are *not* captured (e.g., VM on one monitor, host applications on another monitor), most keystrokes are still sent to the guest system (of course no hotkeys) while the VM window is focused. This may be counterintuitive because not having clicked into the VM window means that the user does not want to interact with it. Accidentally moving the host's mouse to the VM window may change the focus and then hitting space may active a button in the guest instead of inserting a whitespace in a host application window.

If it makes a difference, most VM windows are used in full screen mode. There may be a second or third monitor with other VMs or host application windows running.

Again, I am under the impression that the issues described above may be symptoms of one general issue. It appears that the VM window sometimes loses the input controls while the user is working with the VM or they get ""out of sync"" unexpectedly.

This behavior has been seen on different systems, but most recently on Debian, currently running Virtualbox 5.1.38. Some guest systems are running Fedora 28.

",basic6
17934,PulseAudio failed to init context,Linux,VirtualBox 5.2.18,2018-08-16T13:59:13Z,2018-09-09T17:50:51Z,2018-09-09T17:50:51Z,"Host: Ubuntu 16.04[[BR]]
Guest: Ubuntu 16.04

updated VBox from 5.2.16 to 5.2.18;[[BR]]
installed extpack 5.2.18;[[BR]]
rebooted host;[[BR]]
start guest, get error as below;[[BR]]
install guest additions 5.2.18 in guest;[[BR]]
shutdown guest;[[BR]]
restart guest VM, get same error as before (log excerpt):


{{{
00:00:00.801653 Audio: Initializing PulseAudio driver
00:00:30.807983 PulseAudio: Failed to initialize context (state 5)
00:00:30.808320 Audio: Initialization of host backend failed with VERR_AUDIO_BACKEND_INIT_FAILED
00:00:30.808478 Audio: Initializing NULL driver
00:00:30.808523 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0)
00:00:30.808538 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message=""Host audio backend initialization has failed. Selecting the NULL audio backend with the consequence that no sound is audible""
}}}

As the error msg says there is no guest audio playing through the host.

Host audio itself is ok, i.e. all audio functions on host are intact.

",sunrider
17490,VBoxManage and Guest Additions 5.2.x: Can't communicate with Linux Guests,Linux,VirtualBox 5.2.6,2018-01-22T13:41:36Z,2018-08-29T02:14:05Z,2018-08-29T02:14:05Z,"VirtualBox was updated from 5.0.32 (very stable version) to 5.2.4 and later 5.2.6.

All VM:s are provisioned through VBoxManage, but with Guest Additions 5.2.x on Linux guests, the VBoxManage processes just hang. Windows guests work fine, though.

So, with VirtualBox 5.2.6 and Guest Additions Version:

5.2.0-Hangs

5.2.2-Hangs

5.2.4-Hangs

5.2.6-Hangs

5.2.7-120349-Hangs

5.1.30-Works!",Jonas Almroth
16432,Unable to open sqlite database on shared folder,Linux,VirtualBox 5.1.14,2017-01-28T15:32:50Z,2018-08-22T16:43:17Z,2018-08-22T16:43:17Z,"When attempting to open an sqlite database on a shared folder it fails with ""Error: disk I/O error""

If I copy that same database from the shared folder locally to the VM then the open succeeds.
{{{
jlmcgraw@mate1604:~$ sqlite3 /media/sf_Shared_Folder/Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.
 sqlite> .tables
 
 Error: disk I/O error
 sqlite> .q

jlmcgraw@mate1604:~$ cp /media/sf_Shared_Folder/Recordings.db .

jlmcgraw@mate1604:~$ sqlite3 Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.

 sqlite> .tables
 ZDATABASEPROPERTY  ZRECORDING         Z_MODELCACHE     
 ZENTITYREVISION    Z_METADATA         Z_PRIMARYKEY     

 sqlite> .q
}}}",jlm
17746,"Slow I/O when ""Use Host I/O Cache"" is switched on",Linux,VirtualBox 5.2.10,2018-05-09T09:29:56Z,2018-07-29T15:08:38Z,2018-07-29T15:08:38Z,"I installed VirtualBox 5.2 and when I/O cache is switched on, I/O is very slow.

Steps to reproduce:

1. Create a virtual machine with Debian or Ubuntu
2. Switch ""Use Host I/O Cache"" on, on SATA controller.
3. Try to upgrade existing packages or install new in the virtial machine. I have spinning disks on my host computer and they become noisy and IO speed is between 900KB/s and 1.3 MB/s during installation or upgrade of packages. I had no such problem with VirtualBox 5.1.",Georgi
17879,Slow traffic on Bridged network interface when using anything but virtio-net,Linux,VirtualBox 5.2.16,2018-07-20T18:42:15Z,2018-07-20T18:48:38Z,2018-07-20T18:48:38Z,"Hi,

I'm noticing my network interfaces on my VM is very slow 300-400KB/s when using any of these network intefaces:

PCnet-PCI II (Am79C970A)
PCnet-FAST III (Am79C973)
Intel PRO/1000 MT Deesktop (82540EM)
Intel PRO/1000 T Server (82543GC)
Intel PRO/1000 MT Server (82545EM) - couldn't bring network up

When I used:

Paravirtualized Network (virtio-net)

I saw the normal speeds ie 3-4MB/s which is what I should be getting.

The virtual machine is a Debian 9 (Stretch)

Linux virtualmachine 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux


 ii  virtualbox-guest-dkms             5.2.10-dfsg-6~bpo9+1           all          x86 virtualization solution - guest addition module source for dkms
ii  virtualbox-guest-utils            5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - non-X11 guest utilities
ii  virtualbox-guest-x11              5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - X11 guest utilities

The host is Archlinux (latest updates 2018-07-20) ie:

Linux host 4.17.6-1-ARCH #1 SMP PREEMPT Wed Jul 11 19:14:29 UTC 2018 x86_64 GNU/Linux

The virtual machine currently has:

Base Memory: 2048MB
Chipset:     PIIX3
Enable I/O APIC = yes
Proceessor(s) = 4
Execution Cap = 100%
PAE/NX = false
Paravirtulization Interface: Default
VT-x/AMD-V = yes
Nested Paging = yes
Video Memory 128MB

Network:

Bridged Adaptor, on VLAN 2. (VLAN is set inside of the virtual machine).
Has dual stack IPv4 & IPv6 ie NAT IPv6 addressss and IPv6 GLA address.

The version of VirtualBox that ArchLinux has at the moment is 5.2.16 r123745",Tyler A
17820,VERR_INTERRUPTED errors from guest control service during ptrace debugging,Linux,VirtualBox 5.1.38,2018-06-14T12:17:38Z,2018-06-25T09:14:07Z,2018-06-25T09:14:07Z,"VBoxService should cleanly handle interrupted syscalls. When receiving an error with errno=EINTR, the syscall should be retried.

We have a service that performs an anti-virus scan of running processes, which attaches to processes as a debugger to inspect memory to check for injected malware. Every time a scan is performed an error is reported by the Guest control service:

{{{
May 31 09:36:37 rhel74 kernel: 186:39:59.180297 control  Error: Getting host message failed with VERR_INTERRUPTED
}}}


After a few scans (17?) the Guest control service aborts:

{{{
May 31 09:41:10 rhel74 kernel: 186:44:32.414453 control  Error: Getting host message failed with VERR_INTERRUPTED
May 31 09:41:10 rhel74 kernel: 186:44:32.414591 control  Error: Too many failed attempts in a row to get next message, bailing out
May 31 09:41:10 rhel74 kernel: 186:44:32.414636 control  Guest control service stopped
May 31 09:41:10 rhel74 kernel: 186:44:32.414667 control  Guest control worker returned with rc=VERR_INTERRUPTED
}}}

The error can be reproduced with gdb by attaching to the running VBoxService process:


{{{
[root@rhel69 pair]# tail -f /var/log/messages &
[1] 4714
[root@rhel69 pair]# May 31 13:44:00 rhel69 kernel: 00:00:00.000152 main     Log opened 2018-05-31T12:44:00.767090000Z
May 31 13:44:00 rhel69 kernel: 00:00:00.000266 main     OS Product: Linux
May 31 13:44:00 rhel69 kernel: 00:00:00.000307 main     OS Release: 2.6.32-696.3.2.el6.x86_64
May 31 13:44:00 rhel69 kernel: 00:00:00.000355 main     OS Version: #1 SMP Wed Jun 7 11:51:39 EDT 2017
May 31 13:44:00 rhel69 kernel: 00:00:00.000388 main     Executable: /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
May 31 13:44:00 rhel69 kernel: 00:00:00.000390 main     Process ID: 4698
May 31 13:44:00 rhel69 kernel: 00:00:00.000391 main     Package type: LINUX_64BITS_GENERIC
May 31 13:44:00 rhel69 kernel: 00:00:00.001758 main     5.1.38 r122592 started. Verbose level = 0
May 31 13:44:00 rhel69 vboxadd-service.sh: VirtualBox Guest Addition service started.
May 31 13:44:01 rhel69 kernel: 00:02:52.579824 main     Ended.

[root@rhel69 pair]# gdb -p `pidof VBoxService` -batch -ex quit
Missing separate debuginfo for /opt/VBoxGuestAdditions-5.1.38/sbin/VBoxService
[New LWP 4710]
[New LWP 4709]
[New LWP 4708]
[New LWP 4707]
[New LWP 4706]
[New LWP 4705]
[New LWP 4704]
[Thread debugging using libthread_db enabled]
0x0000003f5ca0f585 in sigwait () from /lib64/libpthread.so.0
A debugging session is active.

	Inferior 1 [process 4703] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
May 31 13:45:55 rhel69 kernel: 00:01:54.476487 control  Error: Getting host message failed with VERR_INTERRUPTED
[root@rhel69 pair]# 
[root@rhel69 pair]# kill %1
[root@rhel69 pair]# 
[1]+  Terminated              tail -f /var/log/messages
[root@rhel69 pair]# 
}}}

It looks like VBoxService is failing to handle interrupted system calls correctly.


From http://man7.org/linux/man-pages/man2/ptrace.2.html :
(Programs which do not expect such ""stray"" EINTR errors may behave in an unintended way upon an strace(1) attach.)


I presume VBoxService is waiting on a syscall, such as poll() and receives an EINTR error when the process is interrupted. The error is recoverable, and the call should just be retried in this case, but it looks like the error is being treated as a problem and isn't silently/cleanly recovered.


VBox guest attributes:


{{{

￼
Runtime attributes


Screen Resolution

800x600x32 @0,0
VM Uptime

1d 03:48:55
Clipboard Mode

Disabled
Drag and Drop Mode

Disabled
VT-x/AMD-V

Active
Nested Paging

Active
Unrestricted Execution

Active
Paravirtualization Interface

KVM
Guest Additions

5.1.38 r122592
Guest OS Type

Linux 2.6 / 3.x / 4.x (64-bit)
Remote Desktop Server Port

Not Available
}}}

",Tim@…
17570,vboxmanage cli - Segmentation fault,Linux,VirtualBox 5.2.6,2018-02-27T13:06:22Z,2018-06-14T12:42:52Z,2018-06-14T12:42:52Z,"I'm running CentOS 7 on a dedicated server. And was running a single Linux Guest deployed via VBOX and Vbox-web. Since last year mid Oct I have not been able to use this setup any more. All commands result in segmentation fault.

I have updated Vbox , OS, all packages, rebooted the server. All without any result.
{{{
root@dedi ~ # cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core) 
}}}
{{{
root@dedi ~ # rpm -qa | grep VirtualBox
VirtualBox-5.2-5.2.6_120293_el7-1.x86_64
}}}

dmesg results in the below being logged
{{{
[746521.108089] vboxwebsrv[20856]: segfault at c ip 00007fac8d5fdb65 sp 00007ffe6872ea78 error 6 in libcrypto.so.1.0.2k[7fac8d58d000+234000]
[747035.697541] VBoxManage[23082]: segfault at 9 ip 00007fe6f8fb7b65 sp 00007ffed3c10ec8 error 6 in libcrypto.so.1.0.2k[7fe6f8f47000+234000]
[747292.271164] VBoxManage[24094]: segfault at 9 ip 00007f7eb7d20b65 sp 00007ffe5c8262b8 error 6 in libcrypto.so.1.0.2k[7f7eb7cb0000+234000]
[747329.919469] vboxwebsrv[24204]: segfault at c ip 00007f90a5595b65 sp 00007fff96e61938 error 6 in libcrypto.so.1.0.2k[7f90a5525000+234000]
}}}",ahurjui
15908,XBoxAutostart service starts and completes before NFS and iSCSI start,Linux,VirtualBox 5.1.4,2016-09-08T12:26:16Z,2018-06-14T04:19:55Z,2018-06-14T04:19:55Z,"I have a fresh install of Ubuntu 16.04 Server and VirtualBox 5.1. I have an Ubuntu guest created on an NFS mount with the storage attached to an iSCSI LUN on my NAS. Starting and stopping it manually works fine, but it does not start at boot.

Manually starting the guest works via any one of these commands:
* VBoxHeadless --startvm ""Ubuntu Server""
* sudo service vboxautostart-service restart
* vboxautostart --start --config /etc/vbox/autostart.cfg

The syslog shows the vboxautostart-service starting and completing before the NFS mounting and the iSCSI initiator daemon is ready.  With the help of the forum moderator Perryg, I added 'sleep 10' to the top of the /etc/default/virtualbox and the VM started and working as expected.

The vbox services with my install are started via S02vboxdrv and S03vboxautostart-service in the appropriate rc.d folders.

syslog
{{{
Sep  7 15:12:03 MyHost systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
Sep  7 15:12:03 MyHost vboxdrv.sh[2811]: vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost vboxdrv.sh: Starting VirtualBox services.
...
Sep  7 15:12:03 MyHost kernel: [   14.354340] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Sep  7 15:12:03 MyHost kernel: [   14.359014] vboxdrv: Found 4 processor cores
...
Sep  7 15:12:03 MyHost kernel: [   14.378254] vboxdrv: TSC mode is Invariant, tentative frequency 1596300487 Hz
Sep  7 15:12:03 MyHost kernel: [   14.378258] vboxdrv: Successfully loaded version 5.1.4 (interface 0x00260000)
...
Sep  7 15:12:04 MyHost kernel: [   14.582075] VBoxNetFlt: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.583189] VBoxNetAdp: Successfully started.
Sep  7 15:12:04 MyHost kernel: [   14.584579] VBoxPciLinuxInit
Sep  7 15:12:04 MyHost vboxdrv.sh: VirtualBox services started.
Sep  7 15:12:04 MyHost kernel: [   14.586318] vboxpci: IOMMU not found (not registered)
Sep  7 15:12:04 MyHost systemd[1]: Started VirtualBox Linux kernel module.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxautostart-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxballoonctrl-service.service...
Sep  7 15:12:04 MyHost vboxautostart-service.sh[3023]: vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost vboxautostart-service.sh: Starting VirtualBox VMs configured for autostart.
Sep  7 15:12:04 MyHost systemd[1]: Starting vboxweb-service.service...
Sep  7 15:12:04 MyHost systemd[1]: Started vboxballoonctrl-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxweb-service.service.
Sep  7 15:12:04 MyHost systemd[1]: Started vboxautostart-service.service.
...
Sep  7 15:12:10 MyHost systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Sep  7 15:12:10 MyHost systemd[1]: Starting OpenBSD Secure Shell server...
Sep  7 15:12:10 MyHost systemd[1]: Started /etc/rc.local Compatibility.
Sep  7 15:12:10 MyHost iscsid: iSCSI logger with pid=3172 started!
Sep  7 15:12:10 MyHost systemd[1]: Started iSCSI initiator daemon (iscsid).
Sep  7 15:12:10 MyHost systemd[1]: Starting Login to default iSCSI targets...
Sep  7 15:12:10 MyHost iscsiadm[3180]: iscsiadm: No records found
Sep  7 15:12:10 MyHost systemd[1]: Started OpenBSD Secure Shell server.
Sep  7 15:12:10 MyHost systemd[1]: Started Login to default iSCSI targets.
Sep  7 15:12:10 MyHost systemd[1]: Reached target Remote File Systems (Pre).
Sep  7 15:12:10 MyHost systemd[1]: Mounting /mnt/nfs/myNas...
Sep  7 15:12:10 MyHost kernel: [   21.235486] FS-Cache: Loaded
Sep  7 15:12:10 MyHost kernel: [   21.247575] FS-Cache: Netfs 'nfs' registered for caching
Sep  7 15:12:10 MyHost kernel: [   21.258497] NFS: Registering the id_resolver key type
Sep  7 15:12:10 MyHost kernel: [   21.258505] Key type id_resolver registered
Sep  7 15:12:10 MyHost kernel: [   21.258506] Key type id_legacy registered
Sep  7 15:12:10 MyHost systemd[1]: Mounted /mnt/nfs/myNas.
}}}

Forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=79617",Brian Duguid
17792,vboxmanage guestcontrol run --exe doesn't display any output,Linux,VirtualBox 5.2.12,2018-05-31T00:23:33Z,2018-05-31T09:19:03Z,2018-05-31T09:19:03Z,"Hello,

== 
The vboxmanage guestcontrol run/start doesn't show any information on the standard output. ==
 
I have tried with the --wait-stdout and/or --wait-stderr but nothing change.
Sessions seems to be created but I even obtain acore dumped while watching operation.
Here my details :

What I do :
{{{
[fredmj@Lagrange ~]$ vboxmanage --nologo guestcontrol ""CENTOS7.TMP"" --verbose run --exe ""/bin/ls"" --username fredmj --password dummyPass --wait-stdout

}}}


{{{
[fredmj@Lagrange ~]$ vboxmanage guestcontrol CENTOS7.TMP watch
Session ID=1 ""[12121] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=2 ""[12154] VBoxManage Guest Control [CENTOS7.TMP] - start"" unregistered
Session ID=3 ""[12186] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" registered
Process ""/bin/ls"" registered
Process PID=15554 ""/bin/ls"" changed status to [started]
Process PID=15554 ""/bin/ls"" changed status to [successfully terminated]
Session ID=1 ""[12806] VBoxManage Guest Control [CENTOS7.TMP] - run"" unregistered
Erreur de segmentation (core dumped)

}}}


My configuration:

{{{
[fredmj@Lagrange ~]$ cat /etc/redhat-release 
CentOS Linux release 7.5.1804 (Core)
}}}
 


{{{
[fredmj@Lagrange ~]$ vboxmanage --version
5.2.12r122591
}}}



{{{
[fredmj@Lagrange ~]$ vboxmanage showvminfo CENTOS7.TMP
Name:            CENTOS7.TMP
Groups:          /BuildingBlocksLab
Guest OS:        Red Hat (64-bit)
UUID:            f415d3d3-cc35-488a-82d4-a9dbfd529cca
Config file:     /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vbox
Snapshot folder: /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Snapshots
Log folder:      /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/Logs
Hardware UUID:   f415d3d3-cc35-488a-82d4-a9dbfd529cca
Memory size:     1024MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:           running (since 2018-05-30T23:32:13.661000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.vdi (UUID: 92b5d7ab-8cac-41cf-ae63-98c5d51205c9)
SATA (1, 0): /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: 3cc8e4fb-e56e-4eb6-a214-d1be7ca16272)
NIC 1:           MAC: 080027A06520, Attachment: Bridged Interface 'wlp2s0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: AC97, Codec: AD1980)
Audio playback:  disabled
Audio capture: enabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
Session name:    headless
Video mode:      800x600x32 at 0,0 enabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Capturing:          not active
Capture audio:      not active
Capture screens:    0
Capture file:       /home/fredmj/VirtualBox VMs/BuildingBlocksLab/CENTOS7.TMP/CENTOS7.TMP.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:    ac_enabled=false

Guest:

Configured memory balloon size:      0 MB
OS type:                             Linux26_64
Additions run level:                 2
Additions version:                   5.2.12 r122591


Guest Facilities:

Facility ""VirtualBox Base Driver"": active/running (last update: 2018/05/30 21:35:01 UTC)
Facility ""VirtualBox System Service"": active/running (last update: 2018/05/30 21:35:03 UTC)
Facility ""Seamless Mode"": not active (last update: 2018/05/30 21:35:01 UTC)
Facility ""Graphics Mode"": not active (last update: 2018/05/30 21:35:01 UTC)

}}}

",Frédéric MARIE-JOSEPH
17749,Segmentation fault in libQt5Widgets.so when trying to open preferences,Linux,VirtualBox 5.2.0,2018-05-10T06:31:13Z,2018-05-10T09:31:42Z,2018-05-10T09:31:42Z,"When I open Preferences (File->Preferences) a dialog window appears and then application crashes.

GUI is an package virtualbox-qt (5.1.34-dfsg-0ubuntu1.16.04.2) from Linux Mint's repository. In syslog I see messages like this:

""kernel: [ 6494.722842] VirtualBox[954]: segfault at 28000002c ip 00007fe52d0277b1 sp 00007ffd04fb9380 error 4 in libQt5Widgets.so.5.5.1[7fe52cbfe000+659000]""

I tried reinstall all it but it not helps. Application I have downloaded directly from virtualbox.org works fine. Seems, its GUI doesnt use qt.

My version Linux is Mint 18.3 x64

",akerka
16696,KDE taskbar is not visible,Linux,VirtualBox 5.1.20,2017-04-25T12:35:28Z,2018-05-08T21:46:35Z,2018-05-08T21:46:35Z,The KDE taskbar is not visible on a Linux guest. It disappears as soon as you click on the bar. Screenshots and log attached.,Panos Kavalagios
17644,VBoxHeadless crash,Linux,VirtualBox 5.2.8,2018-03-28T13:02:23Z,2018-04-23T15:29:29Z,2018-04-23T15:29:29Z,"Hi everyone.

Since our VirtualBox upgrade (5.0.40 -> 5.2.8), we started seeing some VBoxHeadless process disappearing. 

Crash file attached.

We'll be glad to help you in any way we can to fix investigate the issue.
",srats
17707,Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10,Linux,VirtualBox 5.2.10,2018-04-23T08:19:03Z,2018-04-23T15:25:29Z,2018-04-23T15:25:29Z,"Ubuntu 16.04 guest fails to start after upgrade to VirtualBox 5.2.10. Please see he video capture: https://drive.google.com/open?id=1aZfyoduWR4IvysM6UQdDePNEVMWjQEHE

One more detail: I was able to start the guest after upgrade to VirtualBox 5.2.10 . I installed guest additions. And the thing is not working any more... Same as last time. Something is broken with guest additions.

I tried to disable 3D acceleration. It does not help...",SamH
17694,Virtualbox choppy sound issue with Genymotion on Linux,Linux,VirtualBox 5.2.10,2018-04-18T04:24:02Z,2018-04-20T08:49:21Z,2018-04-20T08:49:21Z,"There are known sound issues with Genymotion using Virtualbox since Virtualbox version 5.1x and newer, the audio becomes kind of choppy and the virtual machines have performing issues.

In Virtualbox 5.0.26 (up to 5.0.40 in my pc) it worked perfectly. After 5.1 the issue began.

I already tried setting all the audio combinations in Virtualbox (alsa and pulse with all available audio controllers) but the issue remains.

I have done this procedure https://www.virtualbox.org/wiki/AudioDebug and will be attaching a zip file containing the VBox.log file and 3 wav files.",pemartins
17651,A critical error has occurred while running the virtual machine and the machine execution has been stopped,Linux,VirtualBox 5.2.6,2018-03-30T11:53:53Z,2018-04-19T20:14:39Z,2018-04-19T20:14:39Z,"While starting new virtual box and choosing to install Ubuntu 32bit OS I received Guru Meditation box stating that ""A critical error has occurred while running the virtual machine and the machine execution has been stopped"".

Log attached.",H88
17639,synced folder not working  (Ubuntu 16.04 hosting debian/stretch64 9.4.0 ),Linux,VirtualBox 5.2.8,2018-03-26T12:42:23Z,2018-03-29T08:35:23Z,2018-03-29T08:35:23Z,"When setting up a VM via '''Vagrant 2.0.1''' using '''VirtualBox 5.2.8''' and guest additions 5.2.8, touching a file in the default synced folder /vagrant does not make that file appear on the host side.

a similar test works fine for a guest of type ""ubuntu/xenial64 v20180215.0.0"".

how to reproduce: create following Vagrantfile (also attached):


{{{
Vagrant.configure(""2"") do |config|

      config.vm.box = ""debian/stretch64"" # or generic/debian9
      config.vm.box_version = ""9.4.0""
      config.ssh.insert_key = false

      config.vm.network ""private_network"", ip: ""192.168.33.10""
end
}}}

and the run following script from the hos:

{{{
#!/usr/bin/env bash

# to run from tools/vagrant/

set -x
set -e
set -u

GUEST=${1:-""default""} #$1    # name from `vagrant status`

export VERSION=5.2.8   # must be equal to the VirtualBox version!
export URL=""http://download.virtualbox.org/virtualbox/""$VERSION""/VBoxGuestAdditions_""$VERSION"".iso""

time vagrant ssh $GUEST << HERE

set -e
set -x

sudo bash

apt-get update

apt-get install -y dkms build-essential

apt-get install -y linux-headers-amd64 linux-headers-4.9.0-4-amd64

apt-get install -y module-assistant

cd /opt/

wget -c $URL -O vb.iso
mount vb.iso -o loop /mnt

cd /mnt/
sh ./VBoxLinuxAdditions.run --nox11

cd /opt
sudo rm *.iso

lsmod | grep vboxguest || echo ""*** something went wrong while attempting to install the guest additions""

HERE


}}}

touch a file in /vagrant

observe that the file does not appear in the host location.

",axd
17645,Host modules build without dkms patch,Linux,VirtualBox 5.2.6,2018-03-28T14:10:58Z,2018-03-28T14:10:58Z,2018-03-28T14:10:58Z,"Using VirtualBox 5.2.8 I cannot get the host modules to build. The 5.0.x modules build fine. It seems the makefile no longer functions correctly on systems without DKMS. System is LFS, GCC 5.3, QT5.10.1, kernel 4.14.29 

The errors are below. I've created a patch to fix these issues, I'm not sure if this patch is the correct way to fix it though.


{{{
=== Building 'vboxdrv' module ===
make[1]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make V= CONFIG_MODULE_SIG= -C /usr/lib/modules/4.14.29/build SUBDIRS=/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv SRCROOT=/mnt/data/pl/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv -j4 modules
make[2]: Entering directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
  CC [M]  /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o
cc1: fatal error: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/vboxdrv/include/VBox/SUPDrvMangling.h: No such file or directory
compilation terminated.
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:329: /mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/SUPDrv.o] Error 1
make[2]: *** [Makefile:1519: _module_/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv] Error 2
make[2]: Leaving directory '/usr/lib/modules/4.14.29/build'
make[1]: *** [/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv/Makefile.include.footer:101: vboxdrv] Error 2
make[1]: Leaving directory '/mnt/data/packages/virtualbox-host-modules/1/vboxhost-5.2.8_OSE/vboxdrv'
make: *** [Makefile:49: all] Error 2

}}}
",Willie
17607,5.2.8 Has Issues Passing Though USB Devices Consistently,Linux,VirtualBox 5.2.8,2018-03-08T14:27:46Z,2018-03-08T14:27:46Z,2018-03-08T14:27:46Z,"I use USB passthrough often, and after updating to the newest version, the passthrough was working maybe 1 of 10 tries. Currently, I am trying to passthrough USB to Serial cables. Downgrading to 5.2.6 has solved these issues. ",SheepyBloke
17479,Ubuntu host does not start after 5.1.32 Guest Additions installed,Linux,VirtualBox 5.1.32,2018-01-18T16:46:36Z,2018-02-28T15:03:15Z,2018-02-28T15:03:15Z,"The issue is the same as in https://www.virtualbox.org/ticket/17467 in 5.1.32: Ubuntu starts, but then stops at some moment after upgrading VirtualBox from 5.1.30 in 16.04 host to 5.1.32 and the guest additions to 5.1.32. The guest OS is 16.04 as well.
The only way to load the system is to uncheck the option ""Enable 3D Acceleration"".
All features (with unchecked ""Enable 3D Acceleration"") work: buffer, sharing folders etc.
There was a recent update of mesa library from 17.2.2 to 17.2.4 at the same time of 5.1.30->5.1.32, can they be related?",ar123
17561,VBOX_E_FILE_ERROR,Linux,VirtualBox 5.1.28,2018-02-22T19:40:22Z,2018-02-23T18:14:15Z,2018-02-23T18:14:15Z,"VirtualBox-5.1.x86_64 on Red Hat Enterprise Linux Server release 6.6
2.6.32-504.el6.x86_64
/VirtualBox-5.1-5.1.28_117968_el6-1.x86_64

We have a process we have been using for years where we take a Virtual Machine image and convert it to an OVA.  We recently took a new Virtual Machine image for the input because of the Spectre and Meltdown SV's so we need an updated VM image.   The size of the image changed slightly, that is about all I can tell.

I cannot find any documentation or reference that explains what this message means.

/opt/VirtualBox/VBoxManage export VBOX_8_56_07_SHELL --output /ds2/templates/vboxshell.23492/VBOX_8_56_07_SHELL.ova --vsys 0 --product 'XXX VBox Shell Appliance' --vendor XXX --version 8.56.07
0%...10%...20%...30%...40%...50%...60%...70%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance write failed
VBoxManage: error: File not accessible or erroneous file contents
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: ""int handleExportAppliance(HandlerArg*)"" at line 1121 of file VBoxManageAppliance.cpp
",lno184
17549,Themes and UI elements missing after installing Guest Additions,Linux,VirtualBox 5.2.6,2018-02-18T17:43:50Z,2018-02-18T18:12:42Z,2018-02-18T18:12:42Z,"Host: Debian 8 / jessie
Guest: Ubuntu 16.04.3 LTS (Xenial)

After installing Guest Additions on the guest, all of the the theming is gone, all of the icons are blank / x-ed out.  See attachment.",VeHav2GoVeeper
17488,virtualbox freezing the my system linux mint 18.3,Linux,VirtualBox 5.1.20,2018-01-21T23:22:45Z,2018-01-23T10:38:07Z,2018-01-23T10:38:07Z,"i try many time to solve this issue but no way to solve it because that i need your help kindly , i was trying to install Linux Kali in my system guest (Linux mint 18.3) and after i finish form all the setting a start the vm image suddenly the system is freezing 
and the only way to re-start all things is by re-start my guest system 
and i can't provide you with the screen-shoot because the system is freezing 
kindly your support 
my regards 
",astrokinght
17473,GRUB countdown problem,Linux,VirtualBox 5.1.26,2018-01-18T02:46:21Z,2018-01-23T10:14:51Z,2018-01-23T10:14:51Z,"The file /etc/default/grub   contains GRUB_TIMEOUT=5 by default . After starting my Guest OS , it will show a sentence ""The highlighted entry will be executed automatically in 5s"" .
VirtualBox has such a problem that makes GRUB (That's Guest OS ,but not host OS) unable to show this sentence when it's countdowning at 5s . After countdowning at 5s , GRUB shows 4s 3s 2s and 1s very normally . This problem doesn't always appear ,but only sometimes appears ",vbgaofei
14985,Enable 3D acceleration cause black screen or flickering -> obsolete,Linux,VirtualBox 5.0.12,2015-12-29T01:31:41Z,2018-01-19T12:51:38Z,2018-01-19T12:51:38Z,"Ubuntu 14.04.3 X64 + mate 1.82 for both host and guest
Enable 3D acceleration for guest VM
enable hardware acceleration for Chrome in both guest and host
for Chrome, flicking in VM, but works fine in host 

the screen of VM will go black randomly, only can I sent ctrl-alt-backspace to restart X. However, after update both kernel to 4.2 (sudo apt-get install linux-generic-lts-wily). no more black screen in VM. But Chrome still flickering screen when launch if  hardware acceleration is enable in its setings. A 4 seconds screen cast is on https://youtu.be/paVfpClhyj8",maxchen
17467,Ubuntu host does not start after 5.2.6 GUest Additions installed,Linux,VirtualBox 5.2.6,2018-01-17T15:22:13Z,2018-01-18T21:46:15Z,2018-01-18T21:46:15Z,"I upgraded VirtualBox to 5.2.6 on my Ubuntu 16.04 host and also installed Guest Additons 5.2.6 on Ubuntu 16.04 guest. Then I powered off guest. Now, when starting guest it just does not start. I can see Ubuntu starts running but then it gets stuck somewhere...",SamH
17439,Using Intel Realsense SR300 camera causes VM Abort,Linux,VirtualBox 5.2.4,2018-01-09T15:50:27Z,2018-01-09T15:50:27Z,2018-01-09T15:50:27Z,"1- guest
1.1 - Linux vagrant 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1.2 - 
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial

2- install librealsense in vm:

{{{
# if the realsense ubuntu repository was not added add it to ubuntu source list.
if [ ! -f /etc/apt/sources.list.d/realsense-public.list ]; then
    echo 'deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial main' | tee /etc/apt/sources.list.d/realsense-public.list
    apt-key adv --keyserver keys.gnupg.net --recv-key 7DCC6F0F
fi

# make sure you have kernel headers installed, otherwise realsense dkms will not patch the kernel.
apt-get -y install linux-headers-`uname -r`

apt-get -y update
apt-get -y upgrade

apt-get install -y realsense-uvcvideo # kernel patch to support the camera
apt-get install -y librealsense2-utils # demos for the camera 
}}}

3- Plug the camera, and connect to the guest
3.1 - execute the command

{{{
rs-pointcloud
}}}

4- After some seconds the camera vm aborts.

Note: Same setup was tested with VMWare Palyer 14, and vm does not crashes, and the rs-pointcloud application works despite some delays.",mjscosta
17426,Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR),Linux,VirtualBox 5.0.40,2018-01-07T02:07:42Z,2018-01-08T12:07:57Z,2018-01-08T12:07:57Z,Running virtualbox on ubuntu 16.04 host with arch linux as guest after first crash with same error i completelly reinstalled arch so now this error appear on fresh installed system.,Den
17419,Regression: VirtualBox 5.1.30 can not be compiled without kernel build/source directory,Linux,VirtualBox 5.1.30,2018-01-04T20:46:00Z,2018-01-05T17:51:46Z,2018-01-05T17:51:46Z,"In VirtualBox Release 5.1.6 it was possible to compile VBox from Sources without access to the kernel build- and source directory when using --disable-kmods.

When compiling VirtualBox 5.1.30 this gives errors. Not in all environments is the kernel source accessible when compiling a user mode program (or the kernel module build is separated).",core-it-admin
17361,VM Crash on Android USB (debug+tether) unplug,Linux,VirtualBox 5.2.0,2017-12-09T14:56:12Z,2017-12-26T09:35:51Z,2017-12-26T09:35:51Z,"Sometimes, when I unplug my Android device (LineageOS 7.1.2), the VM crashes.
VirtualBox 5.2.2 (it also crashed with VirtualBox 5.1.0).
Host and Guest are Ubuntu Server 17.10.
Host and Guest where rebooted only two days ago.
See crash dump attached.
When plugged, the Android device runs in USB Debug mode, with USB tethering enabled. The linux interface is set with ""allow-hotplug"".",flechaig
17398,Machine remains in aborted state with 3D enabled,Linux,VirtualBox 5.2.4,2017-12-24T10:07:30Z,2017-12-24T10:07:30Z,2017-12-24T10:07:30Z,With guest additions 5.2.4 when I save the state of a VM it starts saving the state but remains in an aborted state. This only happens with 3D enabled. Log has been attached.,mcpudding
17377,VirtualBox 5.2.2 issues on Xubuntu 16.04 x64,Linux,VirtualBox 5.2.2,2017-12-18T18:36:47Z,2017-12-21T09:45:06Z,2017-12-21T09:45:06Z,"Hi,

Last night I uninstalled VirtualBox 5.1.30 from my Xubuntu 16.04 x64 system, deleting all relative files and I did a brand new 5.2.2 installation from scratch. The new installation is facing two issues:

1. It doesn't use the system GTK theme whereas 5.1.30 did. All other GTK, QT4 and QT5 apps do use it, since the system is correctly configured for this.

2. Shared folder auto-mount doesn't work on Xubuntu 16.04 x64 guests whereas it works fine on Windows guests. On Xubuntu guests I have to mount it manually using ""mount -t vboxsf -o uid=1000,gid=1000 shareName /media/sfPublic"". This command mounts it correctly with read/write access.

Thank you.

p.s. The guest additions have been installed of course, using ""sh ./VBoxLinuxAdditions.run"".",StormLord
17378,/sbin/vboxconfig fails during upgrade of Vbox to 5.2.2,Linux,VirtualBox 5.2.2,2017-12-18T19:52:19Z,2017-12-18T19:52:19Z,2017-12-18T19:52:19Z,"Current system is Fedora 28 x86_64 (Rawhide).

Install of VirtualBox released version fails during config. The developer version fails as well... with the same error message (see inclosed install log).",George R. Goffe
17373,vbox driver does not compile with kernel 4.14.5,Linux,VirtualBox 5.1.30,2017-12-15T17:36:32Z,2017-12-15T17:36:32Z,2017-12-15T17:36:32Z,"Hello,

I try a 4.14.5 kernel and the Vbox driver does not compile.
The trace is included.

Regards

JP P",jppo
17341,~30% keyboard strokes reach VM for vbox 5.2.2 only,Linux,,2017-12-02T16:45:06Z,2017-12-02T16:45:06Z,2017-12-02T16:45:06Z,"Host: Debian GNU/Linux 9 amd64, Extension Pack 5.2.2 installed
VM: Debian GNU/Linux 8 amd64

When reverted vbox (and extension pack 5.2.0) to 5.2.0, keyboard strokes reach 100% back again.

(Can't select Version for the ticket, due to lact of 5.2.2 version string in popup menu)",maestro
17317,scaled mode in ubuntu 17.10,Linux,VirtualBox 5.2.0,2017-11-27T15:25:10Z,2017-11-27T15:25:10Z,2017-11-27T15:25:10Z,"Depending on the state (seems scaled first). when going back to normal mode, the VM 
is not responsive to keystrokes.  They appear to buffer, when returning to scaled mode 
they will then show up.

Speculation is on the new WM that comes with 171.0

Saw with with 5.1.28, 5.2.0 and 5.2.2",chad
17246,VirtualBox Guest Additions Fails to start,Linux,VirtualBox 5.2.0,2017-11-05T18:24:07Z,2017-11-05T18:24:07Z,2017-11-05T18:24:07Z,"VirtualBox Guest Additions: Starting.
/etc/rc.d/init.d/vboxadd: line 255: : No such file or directory
",PresidentTrump
17232,/sbin/vboxconfig fails during upgrade of Vbox,Linux,VirtualBox 5.2.0,2017-11-01T05:31:50Z,2017-11-01T16:20:41Z,2017-11-01T16:20:41Z,"I have upgraded kernels on this Fedora 28 (rawhide) system and tried the latest Vbox release (!VirtualBox-5.2-5.2.0_RC1_118201_fedora26-1.x86_64.rpm) as well as the latest developer version (!VirtualBox-5.2.1-118869-Linux_amd64.run) with the same apparent result.

Can someone tell me what I'm doing wrong here please?

George...",George R. Goffe
15853,audio and video out of sync on Ubuntu 16.04.1,Linux,VirtualBox 5.1.4,2016-08-23T18:21:45Z,2017-10-30T10:52:29Z,2017-10-30T10:52:29Z,"Audio and video are out of sync when a youtube video is playing.
Behaviour noticed in a topic of VirtualBox forum: [https://forums.virtualbox.org/viewtopic.php?f=3&t=79360]

My original issue concerned the fact that the Linux guest was unable to reproduce all media contents. In the forum I was suggested to change the Audio Controller, solution that solved the issue.

However @Perryg noticed that audio and video are out of sync and suggested to open this ticket.

My Linux host  is Ubuntu 14.04 LTS, 5,7 GB of total memory
My Linux guest is Ubuntu 16.04.1 LTS, 2 GB of memory and 50 GB of fixed-size file as virtual hard disk.

I attach two log files:

VBox1.log file concerning my original issue posted to the forum
Vbox2.log file recording the reproduction of a youtube video and the reproduction of the same video with videos application.",jrkul
17210,Updated to VB 5.2.0; install failed,Linux,VirtualBox 5.2.0,2017-10-25T22:08:28Z,2017-10-25T22:08:28Z,2017-10-25T22:08:28Z,"I have tried to upgrade VirtualBox to 5.2.0 but the installation failed. Then I tried the ""latest
test (dev?) build (VirtualBox-5.2.1-118468-Linux_amd64.run) but the installation has again failed.

I must be doing something wrong since I am almost continually getting this error (see the enclosed log).

Am I doing something wrong? The error log suggests various versions of ""libelf"" but Fedora 28 (rawhide) doesn't
have any of these packages and as far as I know, never has.

Any help you can give me about this problem would be greatly appreciated.

Regards,

George...
",George R. Goffe
17177,Loss of usb device after live snapshot or snapshot restore,Linux,VirtualBox 5.1.30,2017-10-18T09:32:09Z,2017-10-24T15:20:39Z,2017-10-24T15:20:39Z,"{{{
Host OS: Solus 3 (linux)
Guest OS: Solus 3
Solus kernel: 4.13.5-24.current
VirtualBox Build: 5.1.30r118389
Extension pack installed
USB 2.0 selected
}}}

* USB gamepad shared with the guest.
* Cold boot.
* Play a game using gamepad (e.g. supertux 2)
* Take a live snapshot.
* Gamepad no longer working.
* Restore snapshot.
* Gamepad not working.
* Reboot = gamepad working again.

",romulous75
17199,Virtual appliance of Debian Stretch 32 bit fsails to boot on a native  64 bit,Linux,VirtualBox 5.1.30,2017-10-22T12:19:57Z,2017-10-22T12:22:08Z,2017-10-22T12:22:08Z,"Failed to open a session for the virtual machine Debian 32bit.

Unresolved (unknown) host platform error. (VERR_UNRESOLVED_ERROR).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",flipper88
17155,Running VirtualBox on Ubuntu 17.04 with guest Ubuntu 16.04 crashes VM during apt-get update,Linux,VirtualBox 5.1.28,2017-10-11T09:43:03Z,2017-10-12T12:41:54Z,2017-10-12T12:41:54Z,"I setup a pretty empty VM of Ubuntu 16.04 inside of a host 17.04 running VirtualBox.

When executing the command `sudo apt-get update` the VM crashes and goes into ""aborted"" state.  There appears to be no work-around, and nothing in the apt logs of interest.

Seems similar to this StackOverflow post:
https://stackoverflow.com/questions/30889170/vagrant-enters-aborted-state-during-apt-get-update

The process to create my VM is using Packer, extending a base image from:
https://app.vagrantup.com/box-cutter/boxes/ubuntu1604

and then running a few file copy commands, and then finally ""sudo apt-get update"" and partway through the update the VM vanishes, and is in ""Aborted"" state.

The same VM builds fine on Mac OSX as the host, but fails when Ubuntu is the host.  
",apatrida
16702,Virtual Box in Full screen mode can't switch to other virtual desktop,Linux,VirtualBox 5.1.20,2017-04-26T18:09:37Z,2017-09-22T08:19:46Z,2017-09-22T08:19:46Z,"I am running Linux Mint 18.1 x64 and noticed after upgrading VirtualBox from 5.1.18 to 5.1.20 that when I enter VBOx full screen mode running Ubuntu 16.04 Desktop with fallback installed as guest that I can't switch to other virtual screen using keyboard shortcuts. My short cut was ""Control+Alt+ArrowKeys. This used to work in 5.1.18. When I exit full screen mode and just maximize VBox window it still works. Something I noticed that when in full screen mode when I try to switch virtual screens with above keyboards shortcuts I see for split of a second ""sliding"" like it is trying to do so but then it snaps back to VirtualBox on same screen. So my setup is 3x3 virtual screen setup. So if I enter full screen mode (first row third column) and try to switch to left I see for split of a second 2nd desktop about 5% or it before it snaps back to VirtualBox. I also see Mint 3x3 preview window overlay ed over Virtual box indications all configured screens. But I can switch. I have fairly recent update but this starts happening after Virtual box upgrade. I did reinstall guest tools as well",oxoocoffee
17051,Caps Lock key being remapped in Linux guest can cause the mapping to malfunction,Linux,VirtualBox 5.1.26,2017-09-04T00:45:46Z,2017-09-13T12:53:46Z,2017-09-13T12:53:46Z,"When Colemak is set as the default keyboard layout and Shift+Shift is mapped to serve as a Caps Lock (e.g. with ""setxkbmap -option shift:both_capslock""), Shift+Shift also starts working as Backspace for a little while.",GeneralFailer
17061,NVMe w/o extension pack has too generic of error message,Linux,VirtualBox 5.1.26,2017-09-07T18:12:07Z,2017-09-07T18:12:07Z,2017-09-07T18:12:07Z,"Steps to reproduce:
- Create new Debian 64 VM using defaults for all choices
- Add NVMe controller
- Run VM and note that error message correctly indicates that extpack required but does not mention NVMe even though it does mention USB and RDP.",LNS
17028,ata2.00 exception Emask 0x0 SAct 0x0 SErr action,Linux,VirtualBox 5.1.22,2017-08-21T06:25:54Z,2017-08-21T09:50:55Z,2017-08-21T09:50:55Z,"Hi

Every alternate day on Guest VM running with RHEL 6.5 64bit cpu usage is high and after reboot it shows this error
 
ata2.00 exception Emask 0x0 SAct 0x0 SErr action  on 0x6 is frozen

attached screen shot for more details[[Image()]]",prabhakarraksan
16879,Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS),Linux,VirtualBox 5.1.22,2017-07-06T10:11:57Z,2017-08-14T10:55:08Z,2017-08-14T10:55:08Z,"While using packer tool to automate creation of VM images I face the following errors:
{{{
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Error deleting virtual machine: VBoxManage error: VBoxManage: error: Cannot unregister the machine 'foo' while it is locked
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""Unregister(CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))"" at line 156 of file VBoxManageMisc.cpp
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
}}}
After this happens VM enters ""Guru Meditation"" state.

I searched for more information about the error got and found https://github.com/hashicorp/packer/issues/4309 referring to https://www.virtualbox.org/changeset/64906/vbox that seems to be some attempt to fix this (?).
Anyway, https://www.virtualbox.org/changeset/64906/vbox looks not to be included in VirtualBox-5.1-5.1.22_115126_el7-1.x86_64 RPM I am using in my Centos 7.3 (judging by the lack of VboxManage keyboardputstring/keyboardputfile API added in this changeset).

Steps to reproduce:
{{{
packer build -var vm_name=foo -var no_gui=true centos-vbox.json
Packer version 1.0.0
}}}
Mapping from packer API to VBoxManage calls can be seen in attached packer debug log. ISO image used is just a minimal CentOs 7.3 image. kickstart file should not be relevant for this bug.
The bug is not deterministic, it happens once per ~4 executions.",pstrzelczak
16904,guest OS screen and host OS screen,Linux,VirtualBox 5.1.22,2017-07-16T00:28:49Z,2017-07-28T05:51:21Z,2017-07-28T05:51:21Z,"My host OS is https://parabola.nu  with XFCE desktop .
I downloaded virtualbox latest version, SHA256 is right. And I run 'pacman -S gcc make linux-libre-headers' as root , and then virtualbox successfully installed.
Sometimes I use Ctrl + Alt + F1 to switch to terminal and use Alt + F2 to back to graphical user interface. I installed some guest OSes , one of the guest OSes is parabola too . When the guest OS sleeps, my host OS decreases screen brightness too",vbgaofei
16883,Virtualbox 5.1.22 crashes ethernet card on Ubuntu 16.04 64bit,Linux,VirtualBox 5.1.22,2017-07-07T13:53:10Z,2017-07-26T13:13:51Z,2017-07-26T13:13:51Z,"I have a stock install of Ubuntu 16.04 64bit (Unity desktop) on my laptop.
As an addition there is virtualbox 5.1.22 installed from official Oracle repository and vagrant 1.9.5.

Whenever I start any virtual machine ethernet card just crashes.

Steps to reproduce:

mkdir -pv ~/foo
cd ~/foo
vagrant init bento/ubuntu-16.04
vagrant up

",kiklop74
16417,vboxsf crashes process or VM in case of many file stat operations on shared vboxsf file system in a short time,Linux,VirtualBox 5.1.14,2017-01-23T08:42:05Z,2017-07-20T17:23:49Z,2017-07-20T17:23:49Z,"We use a vagrant based toolchain to automatically generate VMs for executing unit tests. They run on Ubuntu 16.04 LTS 64-bit hosts, and the VMs themselves contain various different older and newer Linux distributions. We use current VirtualBox 5.1.14 and also the 5.1.14 guest tools.

Quite a significant percentage (10-20%) of our VM deployments was not successful. In case of ""default"" paravirtualization using KVM, the whole VM freezes, and the VBox.log file just says:

{{{
00:00:42.027263 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}

If using the ""minimal"" paravirtualization, VM operation continues, just the unit test process itself dies (see log below). This happens consistently at the same place where there are many stat() calls made to get the ctime information of many thousands of (empty) cache files on a shared vboxsf file system, before outdated files are supposed to be cleaned up. If I remove this code part, the error does not occur any more. Therefore my (uneducated) assumption is that it could be related to running many stat operations in a short time. Here's the stack trace as found in /var/log/kern.log in the instance.

{{{
Jan 21 22:23:14 vagrant kernel: [    8.021389] vboxsf: Successfully loaded version 5.1.14 (interface 0x00010004)
Jan 21 22:23:14 vagrant kernel: [    8.328536] VBoxService 5.1.14 r112924 (verbosity: 0) linux.amd64 (Jan 16 2017 17:38:46) release log
Jan 21 22:23:14 vagrant kernel: [    8.328536] 00:00:00.000093 main     Log opened 2017-01-21T22:23:14.323839000Z
Jan 21 22:23:14 vagrant kernel: [    8.328566] 00:00:00.000154 main     OS Product: Linux
Jan 21 22:23:14 vagrant kernel: [    8.328578] 00:00:00.000170 main     OS Release: 3.16.0-4-amd64
Jan 21 22:23:14 vagrant kernel: [    8.328589] 00:00:00.000182 main     OS Version: #1 SMP Debian 3.16.39-1 (2016-12-30)
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000193 main     Executable: /opt/VBoxGuestAdditions-5.1.14/sbin/VBoxService
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000194 main     Process ID: 1028
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000195 main     Package type: LINUX_64BITS_GENERIC
Jan 21 22:23:14 vagrant kernel: [    8.329284] 00:00:00.000860 main     5.1.14 r112924 started. Verbose level = 0
Jan 21 22:27:01 vagrant kernel: [  233.348410] VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-228.
Jan 21 22:27:01 vagrant kernel: [  233.348430] general protection fault: 0000 [#1] SMP 
Jan 21 22:27:01 vagrant kernel: [  233.348461] Modules linked in: vboxsf(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc vboxvideo(O) ttm drm_kms_helper ppdev drm evdev vboxguest(O) crc32_pclmul i2c_piix4 pcspkr i2c_core serio_raw aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd parport_pc battery processor parport video thermal_sys ac button autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic ata_generic crct10dif_pclmul crct10dif_common crc32c_intel e1000 psmouse ata_piix libata scsi_mod
Jan 21 22:27:01 vagrant kernel: [  233.348614] CPU: 1 PID: 1925 Comm: otrs.UnitTest.p Tainted: G           O  3.16.0-4-amd64 #1 Debian 3.16.39-1
Jan 21 22:27:01 vagrant kernel: [  233.348661] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jan 21 22:27:01 vagrant kernel: [  233.348689] task: ffff8800797bcce0 ti: ffff88007bdcc000 task.ti: ffff88007bdcc000
Jan 21 22:27:01 vagrant kernel: [  233.348718] RIP: 0010:[<ffffffffa02666c1>]  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.348763] RSP: 0018:ffff88007bdcfb98  EFLAGS: 00010282
Jan 21 22:27:01 vagrant kernel: [  233.348784] RAX: 00000000ffffff1c RBX: 0000a0007bdcfc84 RCX: 0000000000000001
Jan 21 22:27:01 vagrant kernel: [  233.348813] RDX: 0000000000000000 RSI: 000000000000002f RDI: ffff88007bdcf9a0
Jan 21 22:27:01 vagrant kernel: [  233.348842] RBP: 5f7c81f4149bd010 R08: 000000000000000a R09: 00000000000001c0
Jan 21 22:27:01 vagrant kernel: [  233.348870] R10: 0000000000000000 R11: ffff88007bdcf6be R12: 0000b00000000000
Jan 21 22:27:01 vagrant kernel: [  233.348898] R13: 1b3eed7500000000 R14: 5f7c81f4149bd064 R15: 5f7c81f4149bd010
Jan 21 22:27:01 vagrant kernel: [  233.348927] FS:  00007ff073ca7700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.348958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 22:27:01 vagrant kernel: [  233.348981] CR2: 00007ffec82d3ff8 CR3: 000000007bcd8000 CR4: 00000000000406e0
Jan 21 22:27:01 vagrant kernel: [  233.349008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.349033] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jan 21 22:27:01 vagrant kernel: [  233.349072] Stack:
Jan 21 22:27:01 vagrant kernel: [  233.349082]  001041ed149bd010 000003e900000000 00000002000003e9 013aa00300000902
Jan 21 22:27:01 vagrant kernel: [  233.349114]  0000000000000000 0000000000000000 ffff880023350880 0000006c00000004
Jan 21 22:27:01 vagrant kernel: [  233.349147]  ffff88007bdcfbfc 0000a00000020830 ffff88007b0c6000 ffffffffa03f877c
Jan 21 22:27:01 vagrant kernel: [  233.349178] Call Trace:
Jan 21 22:27:01 vagrant kernel: [  233.349194]  [<ffffffffa03f877c>] ? sf_stat+0x5c/0x110 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349219]  [<ffffffffa03f88b0>] ? sf_inode_revalidate+0x80/0xd0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349246]  [<ffffffff811b5192>] ? __inode_permission+0x22/0xb0
Jan 21 22:27:01 vagrant kernel: [  233.349269]  [<ffffffff811b58e6>] ? link_path_walk+0x256/0x870
Jan 21 22:27:01 vagrant kernel: [  233.349292]  [<ffffffff811c281a>] ? __d_lookup+0x7a/0x150
Jan 21 22:27:01 vagrant kernel: [  233.349979]  [<ffffffffa03f8914>] ? sf_dentry_revalidate+0x14/0x20 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.350641]  [<ffffffff811b47de>] ? lookup_fast+0x25e/0x2b0
Jan 21 22:27:01 vagrant kernel: [  233.351302]  [<ffffffff811b6055>] ? path_lookupat+0x155/0x780
Jan 21 22:27:01 vagrant kernel: [  233.351927]  [<ffffffffa03fa6ee>] ? VbglR0SfCreate+0x7e/0xa0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.352603]  [<ffffffff811b66a6>] ? filename_lookup+0x26/0xc0
Jan 21 22:27:01 vagrant kernel: [  233.353267]  [<ffffffff811ba8e4>] ? user_path_at_empty+0x54/0x90
Jan 21 22:27:01 vagrant kernel: [  233.353855]  [<ffffffff810ed71e>] ? from_kgid_munged+0xe/0x20
Jan 21 22:27:01 vagrant kernel: [  233.354431]  [<ffffffff811af53a>] ? cp_new_stat+0x13a/0x160
Jan 21 22:27:01 vagrant kernel: [  233.354976]  [<ffffffff811af0e6>] ? vfs_fstatat+0x46/0x90
Jan 21 22:27:01 vagrant kernel: [  233.355536]  [<ffffffff811af57a>] ? SYSC_newstat+0x1a/0x40
Jan 21 22:27:01 vagrant kernel: [  233.356067]  [<ffffffff8151adcd>] ? system_call_fast_compare_end+0x10/0x15
Jan 21 22:27:01 vagrant kernel: [  233.356577] Code: 01 b9 ff ff ff ff 48 89 da 4c 89 d6 4c 89 ef e8 b6 df ff ff 41 89 c7 0f 1f 00 48 83 c4 40 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d <c3> 66 0f 1f 44 00 00 49 83 f8 17 0f 86 34 0c 00 00 48 8d 83 00 
Jan 21 22:27:01 vagrant kernel: [  233.358611] RIP  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.359118]  RSP <ffff88007bdcfb98>
Jan 21 22:27:01 vagrant kernel: [  233.359636] ---[ end trace 54b9778e1a5d744b ]---
}}}

For reference, here's the Perl code that is used to cleanup the (empty cache files):

{{{
my $Wanted = sub {

    # Skip nonregular files and directories.
    return if ( !-f $File::Find::name );
    my $Stat = File::stat::stat($File::Find::name);
    if ( $Stat && ( time() - $Stat->ctime() > $CacheTTLSeconds ) ) {    ## no critic
        unlink $File::Find::name;    # Don't die here, this could be removed in the background by another process too.
    }
};
File::Find::find( $Wanted, $CacheDir );
}}}

Less often, a similar error occurs during the vagrant provisioning of the instances, where we copy the source code of our project from the /vagrant shared vboxsf folder into the VM. Here just a simple ""cp -r"" is used during the deployment. It could be the same problem:

{{{
==> default: Copying OTRS code to /opt/otrs
==> default: cp: cannot stat â/vagrant/Sources/otrs/var/httpd/htdocs/js/thirdparty/ckeditor-4.5.6/plugins/mathjax/lang/cy.jsâ: Protocol error
}}}

Please let me know if I should try to provide additional information, and thanks a lot for taking a look at this.",mrtngrnr
16660,VM window freezes and process keeps running after manual savestate,Linux,VirtualBox 5.1.18,2017-04-17T11:47:58Z,2017-06-19T17:19:42Z,2017-06-19T17:19:42Z,"There are several vms on this host, usually running in full screen mode. One vm has been experiencing this issue where the full screen vm window freezes, usually after the vm has been running for one or more days. I haven't noticed that issue with other vms, however, most other vms don't run for weeks.

When it happens, the vm window is not updated anymore. It doesn't show the vm anymore. Instead, it shows whatever was there on the screen earlier. If there was another window above the frozen window and that other window is closed, it's still shown in the frozen vm window. If I switch workspaces back and forth, when I switch back to the workspace with the frozen vm window, the vm window (which is in full screen mode) shows the previous workspace.
For that reason, a screenshot wouldn't be helpful, as it would simply show whatever else was on the screen before the frozen vm window was activated.

This affects the vm window, i.e., the window that shows up when you start a vm in the VirtualBox gui. The affected vm itself is still running and can be accessed via ssh.

It is possible to suspend the vm using ""vboxmanage controlvm [NAME] savestate"", but the frozen vm window won't go away. It visually looks as if nothing had changed.
The vm process keeps running after the vm is suspended:
{{{
user     985 27147 64 00:02 ?        08:10:26 /usr/lib/virtualbox/VirtualBox --comment Fedora-1 --startvm 5c908c7b-bf32-4965-be4d-a11f5abdbf04 --no-startvm-errormsgbox
user    7016     1  0 Apr04 ?        00:38:56 /usr/lib/virtualbox/VBoxXPCOMIPCD
user   27123     1  0 Apr10 ?        00:22:27 /usr/lib/virtualbox/VirtualBox
user   27147     1  0 Apr10 ?        00:47:51 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

If this process (985 in this example) is killed, the frozen window disappears and VirtualBox marks the vm as ""Aborted"". The saved state is lost.
I usually reset the vm to its last healthy state and start it again, which works fine every time. Until the vm window freezes again a few days later.

It's not clear what causes these freezes. I understand that this makes it very difficult to debug this, but I'm hoping this bug report helps someone else out there who is experiencing the same behavior.

Looking at the log (attached), it seems like two log entries are missing. These entries can be found at the end of the log files of other vms that were also suspended (without freeze):
{{{
12:07:58.276482 GUI: UIMediumEnumerator: Medium-enumeration finished!
12:07:58.551772 GUI: Passing request to close Runtime UI from machine-logic to UI session.
}}}




",Philip Seeger
16804,Kernel panic on Arch Linux guest,Linux,VirtualBox 5.1.22,2017-06-01T09:34:49Z,2017-06-01T09:34:49Z,2017-06-01T09:34:49Z,Arch Linux kernel is producing a kernel panic. A screenshot and the log is provided.,Panos Kavalagios
16781,Strange handling of encryption keys in case of encrypted media vs. encrypted VM.,Linux,VirtualBox 5.1.22,2017-05-24T14:48:07Z,2017-05-24T18:11:11Z,2017-05-24T18:11:11Z,"I have created a new medium and encrypted it according the docs[1] WITHOUT attaching it to a VM first. This succeeded and made me wonder where the encryption keys got saved? According to some blog posts and because of tests I made before with encryption on VM level, those should be saved in the XML config of a VM, but in my case I didn't have a VM the media was attached to. I had a look in the global configuration file of the user running the VBoxManage command as well and didn't find any keys.

So where should the keys be saved if only a new medium was created and encrypted, e.g. using VBoxManage, WITHOUT attaching that medium to a VM before encryption?

Afterwards I attached the newly created, encrypted media to some test VM and at some point recognized keys in the XML config of the test VM. Did some testing and stuff and removed the medium from the test VM again to attach it to another VM. But looking at the config of the first test VM, the keys of the re-attached medium is still present there, not in the VM where the medium is currently attached to. Additionally, it is really ONLY attached to the new VM, not the former test VM anymore.

Shouldn't the keys now be part of the one and only VM the medium is attached to? I'm supposed to backup the keys for all media, but how should I do that reliably if I can't be sure where the keys are actually stored? In my case the first VM was for test purposes, the second for production. What happens if I delete the test VM now, still containing the keys of my encrypted medium, even if it's not attached anymore?

I couldn't find any more detailed documentation about where VirtualBox stores the keys when and if/how/when those parts of the config are moved in case of attaching and removing encrypted media from VMs. Looking at how important those keys are, I strongly suggest adding some paragraphs to the docs how to deal with those and what VirtualBox does automatically. Or not at all, because in my case it doesn't seem to move case around as expected...

[1]: https://www.virtualbox.org/manual/ch09.html#diskencryption-encryption",Thorsten Schöning
16765,Virtualbox crashes whit device in DFU mode attached to USB,Linux,VirtualBox 5.1.22,2017-05-17T23:12:20Z,2017-05-17T23:19:19Z,2017-05-17T23:19:19Z,"I work with a device that needs to be rebooted in DFU mode in order to be updated. This device is already connected to the VM with JTAG and UART connections through USB connectors. So far so good, I can see the devices, read data on serial port, list the devices using lsusb, udev rules are properly applied, everything works fine. My problem happens when I reboot the device and remove the jumper that puts the device in DFU mode. As soon as the device boots the VM freezes and goes to an Aborted state. 

I'm using Virtualbox + vagrant but I was also able to reproduce this issue using a pure Virtualbox machine. Issue is also reproducible with older versions of Virtualbox. Host runs on Ubuntu 14.04 and guests are Ubuntu 14.04 and Ubuntu 16.04.

I went through tutorials and forums posts trying to get it to work but I was not able to find a solution and I really need it working as it is a blocker to use virtual machines on my environment. 

Attached are Virtualbox log and core dump.   ",carlosavj
16310,Segmentation fault in VirtualBox,Linux,VirtualBox 5.1.10,2016-12-20T19:14:15Z,2017-05-15T15:18:55Z,2017-05-15T15:18:55Z,"Hi there! My VirtualBox crash and can not use it!

There are the step to reproduce the step:
1) create a new VM
2) start it
3) when prompted for iso click on the browse icon
HERE IT CRASH!

Can you help me, please?
What can I check?
Which logs do you need?

Thanks,
Marco",marco.fortina
16733,Keyboard Layout VirtualBox 5.1 - Ubuntu 16.04 Host - Incorrect keymap,Linux,VirtualBox 5.1.22,2017-05-05T16:00:58Z,2017-05-05T16:00:58Z,2017-05-05T16:00:58Z,"Hi,

When using VirtualBox 5.1 on Ubuntu 16.04 host, the VirtualBox GUI interface does not use the correct keymap.

All other programs on the Host operate without issues.

I tried on 2 hosts and they both display the same problem.

Only solution I found was reinstall VirtualBox 5.036 that is provided by apt-get.

I also installed VirtualBox 5.1 on Centos 7 and the issue does not happen.

I will update this ticket soon when I trie on a Debian 8.7 host...",leo.rudolph
16233,Vbox bridge loses outer QinQ tag,Linux,VirtualBox 5.1.10,2016-11-25T20:03:58Z,2017-04-24T16:13:18Z,2017-04-24T16:13:18Z,"Virtualox bridge loses outer QinQ tag if bridged with Linux TAP interface

Steps to reproduce:

 1. Install OS Linux on PC.
 In my case: Ubuntu 14.04.5
 kernel 4.2.0-42-generic X86_64

 2. Install !VirtualBox (in my case ver. 5.1.10 !r112026 (Qt5.6.1)) from [http://download.virtualbox.org/virtualbox/5.1.10/virtualbox-5.1_5.1.10-112026~Ubuntu~trusty_amd64.deb here]

 3. Download and install guest Linux OS.
 In my case Ubuntu 16.04.01 from [http://releases.ubuntu.com/16.04/ubuntu-16.04.1-server-i386.iso here]

 4. On host system create tap interface:
{{{
ip tuntap add dev tap10 mode tap
ip link set dev tap10 up
}}}
 5. In guest VM netwrok settings set network adapter to ""bridge"" mode to interface tap10
{{{
vboxmanage modifyvm TESTVM --nic2 bridged
vboxmanage modifyvm TESTVM --bridgeadapter2 tap10
}}}
	
 All other network settings may be set to default. I tried to change the ""adapter type"" and ""promiscuous mode"". Their change does not change the result. 
	
 6. Create QINQ subinterface on host interface tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link add link tap10 tap10.100 type vlan proto 802.1q id 100
ip link set up tap10.100
ip link add link tap10.100 tap10.100.2000 type vlan proto 802.1q id 2000
ip link set up tap10.100.2000
ip addr add 10.11.12.1/24 dev tap10.100.2000
}}}
	
 7. Start up guest VM and determine which interface bridged with tap10
	In my case this is a '''enp0s8'''
 8. Create QINQ subinterface on VM interface which bridged with tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link set up enp0s8
ip link add link enp0s8 enp0s8.100 type vlan proto 802.1q id 100
ip link set up enp0s8.100
ip link add link enp0s8.100 enp0s8.100.2000 type vlan proto 802.1q id 2000
ip link set up enp0s8.100.2000
ip addr add 10.11.12.2/24 dev enp0s8.100.2000
}}}
 9. start watch for traffic on host PC on tap10 interface:
{{{
tcpdump -i tap10 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i tap10 -vvv -e -w qinqPC.pcap
}}}
	
 10. start watch for traffic in guest VM on ""physical"" interface:
{{{
tcpdump -i enp0s8 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i enp0s8 -vvv -e -w qinqVM.pcap
}}}
	
 11. Try to ping 10.11.12.2 from 10.11.12.1 (Host PC => Guest VM)
{{{
ping 10.11.12.2
}}}
	
 12. You should get the following results:[[BR]]
 on physical PC (tap10):
{{{
21:22:06.345997 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:07.346093 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:08.346032 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
}}}
 on VM (enp0s8):
{{{
21:30:21.737754 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:22.738035 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:23.737981 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
}}}

As seen, on VM side is missing outer vlan (vlan 100)

If a try to ping from VM to PC the outer vlan in right place only in ARP request. In ARP reply (PC -> VM) the outer vlan is missing.
on physical PC:
{{{
21:35:12.342498 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342501 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342521 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
21:35:13.343489 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343495 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343516 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
}}}

on VM:
{{{
21:35:10.614413 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:10.614556 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:11.615368 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:11.615549 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:12.615063 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
}}}


It does not look as a TAP bug. If a try to bridge two tap interface via linux bridge, and create QINQ subinterfaces for each of them, this problem does not appear.

PCAP-s from VM and PC (qinqVM.pcap and qinqPC.pcap) in attachement.

Thanks in advance!",Arc
16622,Adding an SSD on 2-HD system can confuse drive assignments,Linux,VirtualBox 5.1.18,2017-03-29T18:55:10Z,2017-03-31T15:00:41Z,2017-03-31T15:00:41Z,"Starting with a 2 HD Dell M6800, VB sees the drives as HD1 = sda & HD2 = sdb.

Adding a Samsung EVO 250GB SSD drive caused Linux to assign drives as:
 HD1 = sda, SSD = sdb & HD2 = sdc

My local Mageia Linux install repository resides on HD2p7. This physical source disk was originally defined in DIST[-pt].vmdk as sdb.  After the SSD was installed, VB could not see the installation files because HD2(sdb) was now at sdc.  

Simply editing DIST.vmdk to change the only occurrence of sdb to sdc resolved the problem.

Could this have been overcome by using UUID instead of sdX?
",Pierre Fortin
15179,Severe time drift in guest OS,Linux,VirtualBox 5.0.14,2016-02-25T15:18:02Z,2017-03-27T18:51:09Z,2017-03-27T18:51:09Z,"Installed ubuntu 14 lts guest on centos7 virtualbox Version 5.0.14 r105127

ubuntu guest has latest version: 5.0.14r105127

everything is standard and updated.

Problem is that time drift is so extreme that i run into trouble.

the guest loses about 10 seconds every 15 minutes!

i already tried setting a ntp daemon.. but it does nothing.. also adding a crontab with ntpdate does nothing.

also adding --timesync-set-start --timesync-set-on-restore 1 --timesync-set-threshold 5000 to /etc/init.d/vboxadd-service does not help.


",geegee
16572,shared folders can not be mount,Linux,VirtualBox 5.1.16,2017-03-16T06:32:30Z,2017-03-23T11:14:28Z,2017-03-23T11:14:28Z,"I use Linux Mint LMDE2 (Jessie) as Host with some Linux Guests.

Since VirtualBox 5.1.16 can shared folders not be mounted on the guests.
Until Version 5.1.14 its well done.
(5.1.18 don't work too) 

I gone back to 5.1.14 and it works fine.",Alex175
16586,Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) on Ubuntu 16.04.2 LTS,Linux,VirtualBox 5.0.36,2017-03-20T14:20:03Z,2017-03-20T15:23:34Z,2017-03-20T15:23:34Z,"One of our Production-VMs (the gateway) just crashed with this error after 3.5 days of runtime.

We have no idea how to debug this further.
Googling does not really show up anything helpful either.

* Guest + host have vbox-extensions installed
* host did not run out of ram
* Guest worked fine for weeks prior to getting moved to this Guest-Machine.

Host and Guest are Ubuntu 16.04.2 LTS.",Someone
16527,vbox autostart-enable on deletes the autostart file /etc/vbox/[user].start,Linux,VirtualBox 5.1.14,2017-03-02T17:54:12Z,2017-03-02T18:14:39Z,2017-03-02T18:14:39Z,"it looks like the problems with autostart at ubuntu are somehow logical issues
I wasn't able to bring the vms in autostart mode. all files and folders are fine. But the ...-enabled on reports nothing and the enabled-off showed VERR_FILE_NOT_FOUND

a sudo touch [username].start at /etc/vbox/ followed by sudo chown [user] [user].start changed the the behavior that ..-enabled off doesnt fail.

but after a enabled on the .start script is lost. So something must be wrong there.

Ubuntu 16.04.04 VBOX 5.1.14",bba_fan
14182,Host detects wrong number of cores (half of them),Linux,VirtualBox 4.3.28,2015-06-08T07:11:01Z,2017-02-27T21:55:31Z,2017-02-27T21:55:31Z,"I've a system with 4 Opteron 6174, each of them has 12 cores so the system has a total of 48 cores.

But Vbox seems to detect just half of them, this is the relevant line on one of the client log files:

00:00:00.728345 Physical host cores: 24

I attach the full log for completeness",Alex
16487,Shared Folder /copying an overwriting modified text file causes error on Ubuntu 16 guest,Linux,VirtualBox 5.1.14,2017-02-16T03:10:30Z,2017-02-16T03:10:30Z,2017-02-16T03:10:30Z,"== Summary ==
*copying an overwriting modified text file causes error on Ubuntu 16 guest
after overwriting, file contains invalid characters. (can be check with Ubuntu's gedit) and sometimes missing characters.
One thing I found weird is, if you open the modified file in the shared folder from guest, it doesn't contain any invalid characters. Invalid character problem only rise when the file is overwritten to the folder in guest env.

*copying an overwritten text file steps can be found under 'How to reproduce the problem'

== How to reproduce the problem ==
1. (host OR guest) create a text file from the host shared folder
2. (guest) copy the shared file to any folder
3. (host) modify the file and save (if you modify the file from guest, it won't happen)
4. (guest) copy the modified file and overwrite it

== Attach a (full) log file ==
see the attached log file

Thank you for the great SW!",haku
16446,Virtualbox can only use one core with isolcpus,Linux,VirtualBox 5.1.14,2017-02-03T11:16:19Z,2017-02-06T13:59:27Z,2017-02-06T13:59:27Z,"On our server we installed ''isolcpus'' to dedicate our cpus for special tasks. Unfortunately it is not possible to assign virtualbox for more than one core with 

{{{
taskset -c 4,5,6,7 VBoxManage starvm ""[vm_name]"" --type headless
}}}

If we start the virtual machine only with 

{{{
VBoxManage starvm ""[vm_name]"" --type headless
}}}

the virtual machine runs on core 0-3.

After we uninstalled isolcpus we can use ''taskset'' to assign certain cpus.",seide
16445,VM gets stuck at online snapshotting,Linux,VirtualBox 5.1.12,2017-02-03T11:01:21Z,2017-02-03T11:01:21Z,2017-02-03T11:01:21Z,"In our backup script, we perform online snapshotting of headless VMs to ensure we get a consistent state with the following command:

{{{
vboxmanage snapshot $BCK_VM_UUID take
}}}

One of the VM got stuck in ""online snapshotting"" (as per vboxmanage) for 3h when we took action.

Host is latest update of Debian 8 (Jessie)[[BR]]
Guest is latest update of Ubuntu 16.04 LTS

Core dumps of the vboxheadless process and VBoxSVC are available on request (or via Klaus).",Max D
16437,VBoxManage controlvm savestate fails with NS_ERROR_FAILURE (0x80004005),Linux,VirtualBox 5.1.14,2017-01-31T13:27:07Z,2017-01-31T14:09:22Z,2017-01-31T14:09:22Z,"When I call 
{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
}}}
from a bash script I get the following error:


{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to save machine state
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg*)"" at line 276 of file VBoxManageControlVM.cpp

}}}

'''Environment:'''

VBoxManage: Oracle VM VirtualBox Command Line Management Interface Version 5.1.14

Host operating system: CentOS Linux release 7.2.1511 (Core)

Guest operating system: Ubuntu 14.04.4 LTS",acho-bacho
16423,Unable to boot after converting .vmdk to .vdi,Linux,VirtualBox 5.1.12,2017-01-24T19:17:48Z,2017-01-26T23:06:27Z,2017-01-26T23:06:27Z,"Host: Arch Linux x86_64 with 4.8.13-1-ARCH

After converting a 50GB vmdk file to vdi using the command below, I wasn't able to boot the virtual machine with the newly created vdi file because of a ""fatal error: no bootable medium found"" 

{{{
VBoxManage clonemedium --format VDI actual.vmdk new.vdi
}}}

The conversion went well though. You will find my ''actual.vmdk'' file attached to this post, alongside 2MB of my ''actual-flat.vmdk'', as requested by an IRC user on #vbox.",closingin
16341,With 3D Enabled OpenGL apps fail to work in Stretch Client on Jessie Host,Linux,VirtualBox 5.1.12,2016-12-30T20:26:43Z,2017-01-20T21:03:13Z,2017-01-20T21:03:13Z,"Using the following as OpenGL Test Applications:  KDE Plasma (Stretch), glxgears(Stretch), QT5 Development Tools (Stretch & Download), blender (Stretch).

Toggled Setting: Settings/Display/3D Acceleration (3D_A) in VirtualBox Manager.
* When 3D_A “IS Enabled” VM Guest OpenGL test applications, “Do not work!”.
* When 3D_A “IS Not Enabled” VM Guest OpenGL test applications, “Do work!”.

Note: It would be nice to track this down before Stretch transitions to stable and have it included!

Virtualbox Version:
Jessie sources.list:
deb http://download.virtualbox.org/virtualbox/debian jessie contrib
Virtual Box Version 5.1.12 r112440 (Qt5.3.2)

Virtualbox Guest Additions Version:
VBoxGuestAdditions_5.1.12.iso

NVIDIA Driver Used:
NVIDIA-Linux-x86_64-375.26.run
Both: Titan Black (Kepler) & GTX-1060 (Pascal) showed the same results.

Host Kernel (uname -r):
3.16.0-4-amd64

Guest Kernel (uname -r):
4.8.0-2-amd64

Much work correctly:  In all the test, Jessie (host) neither hung nor needed to be rebooted;   One VM did not effect another;  VM Manager neither hung nor needed to be rebooted do to a failure; sharing worked (within VM KDE Plasma did not mount share correctly when 3D_A was not enalbed.);  copy/paste worked; issues on one VM did not impact other VMs; the base guest Linux kernel did not show instability even when there were failures ongoing; with 3D unchecked OpenGl applications seemed to work.  More testing is needed.

See attachment for more details or the links below where it is also posted to support the stretch alpha8 installation testing process.

Tests were conducted using Stretch Alpha8 Install process.

[https://lists.debian.org/debian-boot/2016/12/msg00275.html Related Post]
See Attachment: hkb_stretch_20161227_1000.pdf
",Hal B.
16385,PCI passthrought works incorrectly with I/O ports,Linux,VirtualBox 5.0.20,2017-01-15T13:18:39Z,2017-01-16T15:45:15Z,2017-01-16T15:45:15Z,"Hello,

I am using virtualBox 5.0.20 OSS with extension pack

# VBoxManage list extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.0.20
Revision:     106931
Edition:      
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption.
VRDE Module:  VBoxVRDP
Usable:       true 
Why unusable:

Host kernel is 3.16.7
Guest kernel is 4.9.0

On the host machine I have the following PCI device:

04:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 19
        Region 1: I/O ports at e080 [size=128]
        Region 2: I/O ports at e100 [size=64]
        Region 3: I/O ports at e140 [size=16]
        Kernel driver in use: pci-stub
        Kernel modules: mxser

When passed into the guest system it looks like the following:

03:00.0 0700: 1393:1320 (rev 02) (prog-if 80)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 17
        Region 1: I/O ports at e000 [size=128]
        Region 2: I/O ports at e080 [size=64]
        Region 3: I/O ports at e0c0 [size=16]

However, access to I/O ports doesn't work in guest system.

To test I/O ports the following simple code snipped is used: https://gist.github.com/matwey/b42f8b9fb50ab8c603d120c54d04c9be

On the host (when accessed to 0xe100) result is the following:

# ./a.out 
64: FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00 FF 00 01 00 00 60 90 00

On the guest (when accessed to 0xe080) result is the following:

# ./a.out 
64: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF",Matwey V. Kornilov
16329,Corruption when accessing files via Shared Folders,Linux,VirtualBox 5.1.12,2016-12-26T01:20:30Z,2016-12-28T19:36:57Z,2016-12-28T19:36:57Z,"I am seeing intermittent file corruption when checking a borgbackup repository via a Shared Folder

Host is Ubuntu x64 16.04 using Virtualbox 5.1.12
Guest is Ubuntu Mint x64 16.10

Here is the output of 5 sequential runs of the same command to verify the repository, you can see that some detect errors and others don't.  The errors that are detected are different between runs as well.


{{{
jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 273, offset 8]
Index object count mismatch. 117954 != 117952
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 155, offset 2726665]
Index object count mismatch. 117954 != 117951
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backup
}}}


I'm unable to recreate the errors when checking the repository from the host machine.

I've also noticed occasional errors in files hosted on the shared folder in other applications as well.  E.g. unzipping a file, errors about duplicity archive errors etc etc so the problem isn't just limited to borg

I will run memory diagnostics again tonight just to be sure, I've run them before and found no errors.

",jlm
15164,"Linux kernel 4.4.0-7.22 (amd64, Ubuntu Xenial) locks up if not using serial output",Linux,,2016-02-21T14:35:14Z,2016-12-25T22:06:53Z,2016-12-25T22:06:53Z,"Hello!

I'm experiencing a rather strange bug. It's perfectly possible that it's a guest kernel bug, and in that case sorry for the noise.

Linux host, Linux strange 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux, 5.0.15r105570 test build

Guest, created by Vagrant, using Ubuntu's linux-image-4.4.0-7-generic_4.4.0-7.22_amd64.deb kernel package.

If I enable a serial port (COM1, raw file output), the guest boots without a problem (but a bit slowly, because it uses a low baud rate by default, I guess). If on the other hand I don't and it doesn't switch to it, the guest kernel basically stops progress after ""no floppy controllers found"" (or work still pending). Eventually initializes the random pool (random: nonblocking pool initialized), and nothing further. I can type, but of course nothing happens, just keys get echoed. Upon sending a SysRq T (tasks?) only the last lines are visible, but it informed me of a pending console_callback.

Any ideas?",Pas
16320,Virtualbox uses 100% of CPU when suspending PC,Linux,VirtualBox 5.0.24,2016-12-23T16:48:45Z,2016-12-23T16:48:45Z,2016-12-23T16:48:45Z,"Hello,
When I suspend the computer while virtualbox is running and then start it again, vboxheadless process use 100% of CPU.

This happens always, every single time.

Ubuntu 16.04

VB log: http://pastebin.com/1PQexHkQ ",Bonomon
16289,Camera access not working,Linux,VirtualBox 5.1.10,2016-12-14T11:37:44Z,2016-12-14T16:14:02Z,2016-12-14T16:14:02Z,"Apps such as Viber and Camera apps aren't able to connect with the host camera on my laptop since updating to the new VBox version. 

Running Android version 4.4 lollipop 32-bit on VBox 5.1 on Ubuntu 16.04 (64-bit)

(see screenshots)",d3m0nking
16253,Starting vm hides itself and all apps on 2 desktops,Linux,VirtualBox 5.1.10,2016-12-01T14:58:40Z,2016-12-02T02:53:25Z,2016-12-02T02:53:25Z,"Host is Dell M6800 running Mageia 5 Linux, KDE4(with 8 desktops).
On desktop 3, running VB, I install/updatee Mageia 6-RC, then reboot to test -- it minimizes ALL apps, as if I clicked host's Show Desktop, on desktop 3 _and_ 4...
Via the taskbar, I can restore (un-minimize) the apps; but when I do this on the started vm, it minimizes all the apps again.  All I can do with this running vm is to power it off which then restores all the minimized apps on both desktops. No idea how this vm could impact 2 desktops on host...

Screenshot of no visible apps would not help...  :)",Pierre Fortin
16128,"Client loses TCP/UDP connectivity, VirtualBox on host uses 100% CPU",Linux,VirtualBox 5.1.8,2016-10-30T08:24:52Z,2016-11-24T08:00:57Z,2016-11-24T08:00:57Z,"I have a guest debian server running on ubuntu host (both 64 bits). Networking mode was set to NAT and port forwarding was set for guest ports 22 and 80 to control and use this server.

It worked fine during low-load testing, but when it come to production with some load (1-2 requests per seconds from around the world), following issue was discovered:

- It's happening after some time, usually after 2-3 days but last time it happens after 7 hours only.
- CPU usage of VBoxHeadless process on host jumps and stay at 100%, although there is no any load on the guest.
- Guest system continues to work but it cannot nor accept nor create new TCP connections (existing TCP connections, e.g. early opened ssh session, continues to work).
- Outgoing TCP connection from the guest (e.g. wget) fails with error code ""Network is unreachable"". This error code is a clear sign that ""bad thing happened"".
- DNS resolving on guest fails so it seems that UDP is affected too.
- PINGs from guest are working! So I consider that network, routing, etc is OK, and the bug is in NAT code.

Of course there are no any messages in any logs when it happens.

I think that symptoms are quite similar to Bug #15223, but don't know could they have common reason or not. First discovering this issue in 4.3.old, I've upgraded to 4.3.40 and then to 5.1.8, but the issue is still here.

",Roman Trunov
16120,VirtualBox 5.1.8r111374 aborts Debian guest after random period - NAT?,Linux,VirtualBox 5.1.8,2016-10-26T21:56:41Z,2016-11-22T08:28:23Z,2016-11-22T08:28:23Z,"I have a Debian Jessie guest running on a Arch host. After a seemingly random period of time, the guest will transition to the ""aborted"" state. I am yet to observe it happening, I normally notice after I find my VirtualBox guest has disappeared after a few hours. 

I think it's possible that this is associated with an older ticket. Sorry if I have not formatted this ticket correctly, this is my first time doing so.

I will provide any information you require, please ask.



",sam.4325224
16164,VirtualBox 5.0 causes lost interrupts / disk stalls on a Linux system,Linux,VirtualBox 5.0.28,2016-11-07T07:11:16Z,2016-11-07T07:11:16Z,2016-11-07T07:11:16Z,"The host system is an 8-core AMD 64-bit system with 32 GB of RAM, a 128 GB SSD drive and a 1 TB regular rotating disk drive. The operating system is Linux Mint 18; kernel is Ubuntu's 

Linux AlgoCompSynth 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox is 5.0.28 r111378 directly from Oracle's download page. I've tried this with 5.1 and it's worse.

In normal use - creating a virtual machine, exporting to an OVA, etc., sometimes the system will freeze for a second or two, then pick up where it left off. It only does this when I'm using VirtualBox.

I dug through kernel ""dmesg"" output and found out what's happening. 


{{{
[  +0.418779] vboxdrv: ffffffffc0835020 VMMR0.r0
[  +0.108599] vboxdrv: ffffffffc0930020 VBoxDDR0.r0
[  +0.003241] vboxdrv: ffffffffc0006020 VBoxDD2R0.r0
[  +0.056406] vboxpci: created IOMMU domain ffff8808170fec20
[Nov 6 22:38] ata1: lost interrupt (Status 0x58)
[  +0.000029] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  +0.000007] ata1.01: failed command: READ DMA
[  +0.000009] ata1.01: cmd c8/00:01:00:e8:d9/00:00:00:00:00/f7 tag 0 dma 512 in
                       res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)
[  +0.000005] ata1.01: status: { DRDY }
[  +0.000023] ata1: soft resetting link
[  +0.184530] ata1.00: configured for UDMA/33
[  +0.007848] ata1.01: configured for UDMA/33
[  +0.000018] ata1: EH complete
[  +0.019241] ata1.00: Enabling discard_zeroes_data
[  +0.156301] ata1.00: Enabling discard_zeroes_data


}}}
I've seen this happen on both the SSD and the rotating disk - whichever VirtualBox is using at the time.",znmebznmeb
16144,"Unhelpful feedback ""DrvVD: Configuration error: keys incorrect at level 0""",Linux,VirtualBox 5.1.8,2016-11-03T17:16:38Z,2016-11-03T17:55:34Z,2016-11-03T17:55:34Z,"Starting a VM which formerly worked fine fails due to
{{{
    DrvVD: Configuration error: keys incorrect at level 0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).
    AHCI: Failed to attach drive to Port0 (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).


    Fehlercode:
    NS_ERROR_FAILURE (0x80004005)
    Komponente:
    ConsoleWrap
    Interface:
    IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
displayed in dialog after start. It'd be helpful to know what failure occurred for what reason and what are useful steps to proceed. It looks like an error in the configuration file, but it's just too useless to guess if you could improve the feedback.

experienced on Ubuntu 16.10 host with Gentoo guest",krichter
16133,Crashes if GUI used with a screen reader,Linux,VirtualBox 5.1.8,2016-11-01T21:25:38Z,2016-11-01T21:25:38Z,2016-11-01T21:25:38Z,"Hi,

On a Debian testing with upstream repo's package:
1. Install qt-at-spi
2. Enable accessibility in the Desktop.
3. Run VirtualBox.
4. Arrow keys, opening dialogs, crash the graphical interface.
5. Run without Orca running.
6. Arrow keys work. Run again screen reader, it crashes as soon as you press an arrow key.

VBoxManage works, VMs as well, but GUI is unusable.

Best regards",texou
16107,Random Freeze of Ubuntu 16.04 guest under 16.04 Host,Linux,VirtualBox 5.1.6,2016-10-23T12:14:23Z,2016-10-25T19:08:40Z,2016-10-25T19:08:40Z,"I encouter random freezes of a 16.04 guest system under a 16.04 host system.

This seems not to be new in the 5.1 versions as I had this problem in previous versions, too. The same guest system was working fine before the update to Ubuntu 16.04 (The box was 14.04 before). 

Unfortunately I do not find a pattern when the box freezes. Sometimes it happens soon after the start of the box, sometimes the box runs stable for 1-2 days. The guest system just freezes. 



",Andreas P
16071,Linux Guest is aborting after some time of inactivity (when afk),Linux,VirtualBox 5.1.6,2016-10-15T23:34:16Z,2016-10-20T07:39:44Z,2016-10-20T07:39:44Z,"I can start up and work with the guest system (Linux mint xcfe 18 64 bit), but after a while (when I am away from keyboard) the VM aborts.



",Klausss
15525,Linux host hangs during compiling,Linux,VirtualBox 5.0.22,2016-06-17T18:15:49Z,2016-10-17T17:48:37Z,2016-10-17T17:48:37Z,I'm compiling LibreOffice on Xubuntu 16.04 guest machine and sometimes (3 freezes - 6 compilings) guest machine freezes. Guest machine is allowed to use 2 cores. I have AMD Phenom II with 4 cores. Host machine - Linux Mint 17.3 (based on ubuntu 14.04),yanp.bugz
15952,virtio slow and have unstable performance when VM have >1 vCPU,Linux,VirtualBox 5.1.6,2016-09-18T19:38:55Z,2016-10-08T10:33:16Z,2016-10-08T10:33:16Z,"
Hi.

I have DL380 G7, with latest CentOS 6. Also, kernel is upgraded to kernel-lt - 3.10.x. Host have 2 NIC's enabled (configured).

I'm using latest VirtualBox 5.1.x.

Test scenario involves two VM's, and both of them are attached to both host NIC's (bridge). In VM's, both vNIC are set as virtio, and vCPU is set to 1. VM's are Centos 6 also.

Everything works ok - i'm getting >140Mbytes/s on all interfaces (eth0<->eth0 and eth1<->eth1 from VM to VM).

Now, on one of those VM's, increase number of vCPU to 2. Things now start to behave erratic.

For a short time, eth0<->eth0 is ok, and then starts to fluctuate widely - from ~100Kb/s to 50Mb/s. At the same time eth1<->eth1 stays >140Mb/s.

In rare occasion, eth0 can work ok, eth1 poorly.

Changing one of interfaces with Intel (so only one vNIC is virtio) makes things work stable - if eth0 was switched to Intel, it is >20Mb/s, while eth1 stays >140Mb/s.

From this, i would conclude that there is some kind of race condition with virtio when VM uses vCPU>1.

Also, i do not know how to debug this furtherer. Please advise.

Regards,

H.",Hrvoje
16043,The guest mouse cursor have big black shadow bellow,Linux,VirtualBox 5.1.6,2016-10-07T09:51:09Z,2016-10-07T09:51:09Z,2016-10-07T09:51:09Z,"The guest mouse cursor have big, fat, black shadow bellow. The problem exists both in Windows XP and Windows 7 guests. If I turn off mouse integration, the problem disappears.",mozo
15913,Installation of guest additions in Fedora 24 32 bits guest hangs => Linux 4.7 bug,Linux,VirtualBox 5.0.24,2016-09-09T10:10:20Z,2016-10-06T11:49:28Z,2016-10-06T11:49:28Z,"I am trying to install the guest additions in a fresh installed Fedora 24 32 bits but the VBoxLinuxAdditions.run script hangs.

The !VirtualBox version I am using is 5.0.24, but I have tried to install guest additions 5.1.4, since the former one doesn't compile under kernel 4.7.2 32 bits.

The exact sequence of commands used are:
{{{
# sudo dnf install install gcc cpp kernel-devel kernel-headers kernel-PAE-devel
# sudo wget http://download.virtualbox.org/virtualbox/5.1.4/VBoxGuestAdditions_5.1.4.iso
# sudo mkdir /tmp/vbox
# sudo mount -o loop /home/vagrant/VBoxGuestAdditions_5.1.4.iso /tmp/vbox
# sudo sh /tmp/vbox/VBoxLinuxAdditions.run
}}}

In the last step it hangs after the following messages are shown:
{{{
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.4 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Building Guest Additions kernel modules.
vboxadd.sh: Starting the VirtualBox Guest Additions.
}}}

I have also tried with the latest test build at https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.1.5-110588.iso but the result is the same.

Exactly the same procedure for a Fedora 24 64 bits guest is working fine and the guest installation finishes without problems.

A pstree command shows the following relevant process tree:
{{{
  │   │           └─sudo,30032 sh -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │               └─sh,30033 -x /tmp/vbox/VBoxLinuxAdditions.run
  │   │                   └─sh,30090 ./install.sh /tmp/vbox/VBoxLinuxAdditions.run
  │   │                       └─vboxadd,30253 /opt/VBoxGuestAdditions-5.1.5/init/vboxadd setup
  │   │                           └─modprobe,32361 vboxsf
}}}

So it looks like it is loading the kernel module where the installation hangs.
This is the list of packages I have installed which are relevant to the kernel:
{{{
$ rpm -qa | grep kernel 
kernel-headers-4.7.2-201.fc24.i686
kernel-PAE-modules-4.7.2-201.fc24.i686
abrt-addon-kerneloops-2.8.2-1.fc24.i686
kernel-devel-4.7.2-201.fc24.i686
kernel-PAE-core-4.7.2-201.fc24.i686
kernel-PAE-devel-4.7.2-201.fc24.i686
libreport-plugin-kerneloops-2.7.2-1.fc24.i686
}}}

I have tried to have a look to the stack of the modprobe command:
{{{
#sudo cat /proc/32361/stack 
[<f8edddfd>] rtR0SemEventMultiLnxWait.isra.2+0x36d/0x3c0 [vboxguest]
[<f8edde73>] VBoxGuest_RTSemEventMultiWaitEx+0x23/0x30 [vboxguest]
[<f8eec5db>] VBoxGuest_RTSemEventMultiWait+0x5b/0x60 [vboxguest]
[<f8ed4361>] vgdrvHgcmAsyncWaitCallbackWorker+0xe1/0x220 [vboxguest]
[<f8ed44be>] vgdrvHgcmAsyncWaitCallback+0x1e/0x20 [vboxguest]
[<f8ed6ff1>] VbglR0HGCMInternalConnect+0x111/0x130 [vboxguest]
[<f8ed60a5>] VGDrvCommonIoCtl+0xad5/0x1550 [vboxguest]
[<f8ed2245>] VBoxGuestIDCCall+0x45/0x70 [vboxguest]
[<f8625b4d>] vbglDriverIOCtl+0x2d/0x40 [vboxsf]
[<f8626780>] VbglHGCMConnect+0x50/0xb0 [vboxsf]
[<f8626a8e>] VbglR0SfConnect+0x5e/0x90 [vboxsf]
[<f840b075>] init+0x75/0x1000 [vboxsf]
[<c0402182>] do_one_initcall+0x42/0x170
[<c056e0af>] do_init_module+0x50/0x1a8
[<c04f4c1a>] load_module+0x213a/0x27a0
[<c04f54b1>] SyS_finit_module+0xb1/0x100
[<c040388d>] do_fast_syscall_32+0x8d/0x140
[<c0b3f932>] sysenter_past_esp+0x47/0x75
[<ffffffff>] 0xffffffff

}}}

I don't know if that's useful.

I attach the output of running the installation script with sh -x, but I am afraid it doesn't give much extra information.

I also attach VBoxSVC.log just in case it is useful.

Regards
",cquike
15994,Guest additions detect GB as KB and claims about too less free space,Linux,VirtualBox 5.1.6,2016-09-27T22:07:04Z,2016-09-27T22:07:04Z,2016-09-27T22:07:04Z,"On installing the guest additions on Android 4.4 I'm getting these errors:

{{{
Uncompressing VirtualBox 5.1.6 Guest Additions for Linux-kP: No such file or directory
mnt/VBoxLinuxAdditions.run[367]: 7.2G: unexpected '.'

Not enough space left in /data/local/tmp (7.2G KB) to decompress mnt/VBoxLinuxAdditions.run (7912 KB)
Consider setting TMPDIR to a directory with more free space.
}}}",Sworddragon
15953,doc/manual/fr_FR/ missing man_VBoxManage-debugvm.xml and man_VBoxManage-extpack.xml,Linux,VirtualBox 5.1.6,2016-09-19T02:26:12Z,2016-09-21T14:57:54Z,2016-09-21T14:57:54Z,"I'm trying build Vbox with VBOX_WITH_DOCS_TRANSLATIONS=1


{{{
kmk: *** No rule to make target `/builddir/build/BUILD/VirtualBox-5.1.6/doc/manual/fr_FR/man_VBoxManage-debugvm.xml', needed by `/builddir/build/BUILD/VirtualBox-5.1.6/obj/obj/manual/fr_FR/user_man_VBoxManage-debugvm.xml'.  Stop.
}}}

in ./doc/manual/Makefile.kmk, user_man_VBoxManage-debugvm.xml should not be add to fr_FR translation .

fyi is not a new bug , search on french contributions seems that doesn't have debugvm

https://www.virtualbox.org/pipermail/vbox-dev/2013-February/011232.html etc ",sergiomb
13073,Video Captures are Blank / Green,Linux,VirtualBox 4.3.12,2014-05-29T03:13:47Z,2016-09-08T21:53:55Z,2016-09-08T21:53:55Z,"When using the Video Capture in Vbox, nothing is recorded. There is only a ""Green Screen"".

Guest Additions are installed

libvpx is installed

This occurs with or without 3D Acceleration enabled.

Host: Ubuntu Gnome 14.04, Virtualbox 4.3.12 r93733
Guest: Lubuntu 14.04",Hashpling
15842,Error with VBoxManage internalcommands createrawvmdk on SAS 4K block size drive.,Linux,VirtualBox 5.1.4,2016-08-21T22:16:56Z,2016-08-21T22:16:56Z,2016-08-21T22:16:56Z,"  - The host (and guests) are under Ubuntu 16.04.1 LTS.
  - My system has 2 X SAMSUNG MZ7KM480 SSD and 6 X SEAGATE  Model: ST1000NX0323. I can create virtual drive on SSD drives without any problem but it does NOT work on SAS drives. The problem is the same with DOS or GPT format.
  - The user is in vboxusers and disk groups.
  - Partitions are readable with the dd command.

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdatah6.vmdk -rawdisk /dev/sdh -partitions 6
VBoxManage: error: Logical partition without magic
VBoxManage: error: Cannot read the partition information from '/dev/sdh'
VBoxManage: error: The raw disk vmdk file was not created
ma@X10DRi:~$ fdisk -l /dev/sdh
Disk /dev/sdh: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x44def683

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdh1            256 244190645 244190390 931,5G  5 Extended
/dev/sdh5            512  52429311  52428800   200G 83 Linux
/dev/sdh6       52429568  55051007   2621440    10G 83 Linux

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdataf6.vmdk -rawdisk /dev/sdf -partitions 6
VBoxManage: error: Cannot read the partition information from '/dev/sdf'
VBoxManage: error: The raw disk vmdk file was not created

ma@X10DRi:~$ fdisk -l /dev/sdf
Disk /dev/sdf: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3D5F9AA3-AA3D-49E4-88B7-1E9CD35FFDF8

Device        Start      End  Sectors  Size Type
/dev/sdf5       512 52429311 52428800  200G Linux LVM
/dev/sdf6  52429568 55051007  2621440   10G Linux filesystem

#
# The behavior is exactly the same with the root user.
#
 - hdparm works well with our SSD drive seems NOT to be working with our ST1000NX0323 drives
 - smartctl works well on our both type of drives
 ",michelparis
15729,keyboard differences in VB 5.1,Linux,VirtualBox 5.1.2,2016-08-03T07:01:19Z,2016-08-03T07:36:49Z,2016-08-03T07:36:49Z,"VB 5.1.2 r108956 on 64-bit Ubuntu 16.04, running 64-bit Ubuntu 16.04 guest with the guest additions.

Something has changed in the way keyboard handling works in VB 5.1.  Two problems that I'm guessing may be related:

'''#1)'''
In the past, the extra ""multimedia"" buttons on my USB keyboard (including the ""calculator"" button) have always worked.  They used to be handled by the host, even when the guest had focus.  In VB 5.1, those buttons don't work anymore when the guest has focus.

'''#2)'''
The other more serious keyboard change in VB 5.1 is that ALT+TAB is no longer always caught by the guest.  Instead of going between the apps in the guest, ALT+TAB is handled by the host, even when the guest has focus.  This doesn't happen 100% of the time.",Stéphane Charette
15547,Virtualbox destroy encrypted discs when delete online snapshots,Linux,VirtualBox 5.0.22,2016-06-26T15:20:55Z,2016-07-14T17:25:07Z,2016-07-14T17:25:07Z,"I tested this on several servers, and the results are 100% reproducible.

I found 3 ways to destroy the encrypted discs:

First:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Remove the snapshot with VM turned on.
 4. Restart the VM
=> The discs are destroyed and the S.O can't start.

Second:
 1. Encrypt the discs of an VM 
 2. Take a offline snapshot
 3. Start the VM
 4. Remove the snapshot with VM turned on.
 5. Restart the VM
=> The discs are destroyed and the S.O can't start.

Third:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Pause the VM
 4. Remove the snapshot with VM paused.
 5. Resume the VM
 6. Restart VM
=> The discs are destroyed and the S.O can't start.

I was tried to find a way to make a automatic backup of an encrypted VM, without need the save the key on the backup script to start vm again, and hard crash the discs off the VM.

The log of the VM on the first case as attached, and a screenshot of it after the restart.

It was tested with the last 5.0.22 VirtualBox Release and I dont found other tickts about this defect.

Thanks for you guys that develop this great program.  ",Law
15534,VBoxManage hostonlyif ipconfig vboxnet1 --dhcp leads to error,Linux,VirtualBox 5.0.22,2016-06-19T20:56:24Z,2016-07-13T19:51:07Z,2016-07-13T19:51:07Z,"Host type: Debian jessie amd64

Trying to configure vboxnet1 to use dhcp after creating it leads to the following error:

{{{
VBoxManage: error: Code NS_ERROR_NOT_IMPLEMENTED (0x80004001) - Not implemented (extended info not available)
VBoxManage: error: Context: ""EnableDynamicIPConfig()"" at line 210 of file VBoxManageHostonly.cpp 
}}}

Steps to reproduce:
* create hostonlyif with ''VBoxManage hostonlyif create''
* call ''VBoxManage hostonlyif ipconfig vboxnet1 --dhcp''  (replace vboxnet1 by the name you get from V''BoxManage list hostonlyifs'' after creating it.

Using the VBoxNetworkName: ( HostInterfaceNetworking-vboxnet1 ) instead of vboxnet1 did not change anything.

",manschenk
15487,Running Linux guest caused udisksd to fail host mounts,Linux,VirtualBox 5.0.20,2016-06-07T14:57:47Z,2016-06-07T15:30:18Z,2016-06-07T15:30:18Z,"Running a Linux guest (freshly installed Mageia 5) to help gather data for a Mageia 5 bug report dealing with installation.  Left the VM running overnight, and this morning was trying to mount some HDs, only to see /var/log/messages such as this:

Jun  7 10:17:39 prf kernel: EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sdc5\040(deleted): No such file or directory
Jun  7 10:05:24 prf udisksd[1666]: Error statting /dev/sde5\040(deleted): No such file or directory
Jun  7 10:05:24 prf systemd[1]: Unit mnt-hd.mount entered failed state.

The mount command on the host appeared to work (no error reported on konsole).

Shut down the guest and host mounts started working again with no other interaction...
Restarting guest to see if this is repeatable...  [not yet]

Looks like I will have to leave guest running for a while to see if this repeats.

",Pierre Fortin
15258,booting issue,Linux,VirtualBox 5.0.16,2016-03-21T17:53:10Z,2016-03-22T10:29:14Z,2016-03-22T10:29:14Z,"i installed kali as VM 
every time i boot it : i get black screen with Loading , Please wait 

which never goes away ",zee.21
7461,Cannot delete old and unused VM snapshot.,Linux,VirtualBox 3.2.8,2010-09-11T20:30:53Z,2016-01-27T20:27:06Z,2016-01-27T20:27:06Z,"Hi all.

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

I'm getting:

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

Details:


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

}}}

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

Regards,

-- Shlomi Fish",Shlomi Fish
3348,Small icons/treeview for guest list,Linux,VirtualBox 2.1.2,2009-02-15T20:56:25Z,2016-01-13T06:34:55Z,2016-01-13T06:34:55Z,"See also http://forums.virtualbox.org/viewtopic.php?t=14385

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

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

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

I think a good idea would be to make the guest list more like Nautilus or Windows Explorer, treating the guests like files/folders.",sej7278
15030,DHCP server on natnetwork doesn't return DNS servers,Linux,VirtualBox 5.0.12,2016-01-12T14:24:23Z,2016-01-12T15:16:39Z,2016-01-12T15:16:39Z,"If I start up a guest VM on old school nat networking I see an option 6 come thru with the DHCP response from the virtualbox DHCP server.

If I do the same on a natnetwork'd guest all but one of the same options arrive in the DHCP response, including 15 for a DNS domain name, but option 6 is consistently missing and obviously this means the DNS server is never configured inside the guest.
If I set it manually in the guest to the IP I configured under ""VBoxManage dhcpserver add"" everything works as expected so networking is certainly working.

This is easily observed with a linux guest by installing and running dhcpdump while running ""dhclient -d""",tommyvn
14912,Microsoft RD Client on iOS - keyboard not working,Linux,VirtualBox 5.0.10,2015-12-09T01:44:02Z,2015-12-09T01:44:02Z,2015-12-09T01:44:02Z,"I am running 5.0.10 Virtualbox on Intel Atom, with 2GBRAM. Latest Guest Extension Pack. I have a Ubuntu 14.4.3LTS guest, latest kernel, 5.0.10 Guest additions. I have configured the guest to share a desktop via VRDE. The gust runs in console mode. When connecting to the guest with Microsoft's official  RD Client software for IOS (either iPad or iPhone), the only key that appears to work on the keyboard is ENTER. That produces a line as expected. Nothing else seems to work. I noticed on log in ""Numlock Enabled"" shows up. I have seen the same problem with a Virtual OpenWRT instance which does not run any guest extensions so it does not seem isolated to just Ubuntu.",Bruksee
14113,Ubuntu guest loses keyboard sporadically,Linux,VirtualBox 4.3.28,2015-05-13T21:23:30Z,2015-12-01T02:14:40Z,2015-12-01T02:14:40Z,"Host: ubuntu 14.04
Guest: ubuntu 12.04

Sporadically guest loses keyboard, xev doesn't show keyboard events, etc. The only way to fix this issue is to restart guest. Save/reload doesn't help.

I'm using the Microsoft Remote Desktop (Win7) as client. If I close it and reconnect to the guest the keyboard still doesn't work.",DO
14251,Ubuntu 14.04 guest additions breaks touchscreen cursor,Linux,VirtualBox 4.3.28,2015-07-09T08:19:47Z,2015-10-05T07:30:04Z,2015-10-05T07:30:04Z,"Hardware: Microsoft surface Pro 3
VirtualBox 4.3.28 
Guest Additions Installed
Host : Ubuntu 14.04
Guest : Ubuntu 14.04

Hello,

After installation of the Guest Additions on the Linux guest, the Touchscreen does not work properly in Guest OS (Ubuntu 14.04).
The mouse works fine I get the cursor but I cannot control the cursor position with Touchscreen, I have already tried to calibrate the Touchscreen (xinput, calibrate Touchscreen…) but it seems like having no effects.

For information, Without the guest addition there is no problem of cursor position, I get the good positions of the Touchscreen cursor but the click doesn’t work, and with the Guest additions installed I lost the positions of the Touchscreen cursor but the click still works.

Can someone help with this issue ?
",drdr_skilled
14605,Date and time on Linux guests is not updated after a session restoration,Linux,VirtualBox 5.0.4,2015-09-18T13:52:48Z,2015-09-30T15:51:24Z,2015-09-30T15:51:24Z,"When you save the machine state and then restoring it on Linux Guest operating systems after some time the date continues to display the last one before saving and not the current date and time. The problem is not reproduced on Windows Guest, where the clock is refreshed automatically.

It might be in the way that Linux system works to retrieve the time from the hardware clock during boot process and then it is maintained by the OS, but if there is any work around would be great to cause the guest to refresh the date like issuing ""hwclock --hctosys"" automatically.",Panos Kavalagios
14368,Connecting Kemper Profiling Amplifier To VM Aborts the VM,Linux,VirtualBox 5.0.0,2015-08-02T03:57:21Z,2015-09-21T15:11:23Z,2015-09-21T15:11:23Z,"Connecting Kemper Profiling Amplifier (KPA) [http://www.kemper-amps.com/] via USB to a virtual machine aborts the VM.

I have tried with both Linux and Windows guests. No problems when connecting KPA to Linux or Windows machine directly.

Nothing is written to VBox.log when KPA is connected to VM. The VM just shuts down and the state in VirtualBox GUI becomes ""Aborted"".

In the attached VBox.log you can see bootup of Kubuntu 14.04 VM. After the VM had booted up, I connected KPA to it (nothing written to VBox.log at this point).

In the lsusb-kpa.txt you can see the output of command lsusb -v -d 133e:0001",Janne Rönkkö
13452,Please add workdir argument to guestcontrol exec,Linux,VirtualBox 4.3.16,2014-10-01T12:52:36Z,2015-09-21T09:42:31Z,2015-09-21T09:42:31Z,"I'm working on virtual build-test factory, based on VirtualBox. VBoxManage guestcontrol helps immensely, but tasks such as 'make' often need concrete folder to run in. Because of that I have to use construct as following, wrapping everything under bash command:

{{{
VBoxManage guestcontrol ""$ARG_VM_NAME"" exec --wait-exit --wait-stderr \
--image ""/bin/bash"" --username $VM_USER_LOGIN --password $VM_USER_PASSWORD \
-- -c ""cd '/mnt/ramdisk/$BUILD/buildroot' && make images""
}}}

It would be very helpful to have --workdir or similar argument to guestcontrol exec, similarly to process spawning libraries in programming languages and libraries.",indifferent
14568,Regression: protocol error if the host folder name differs from share name,Linux,VirtualBox 5.0.4,2015-09-10T13:15:38Z,2015-09-10T13:44:00Z,2015-09-10T13:44:00Z,"I remember many years ago in VBox 2 or 3 there was an issue that name of the folder on host system has to match the name of the share for it to work properly. In 4 it worked properly though. Now on 5.0.4 I've encountered the same issue again:

on host:
1. mkdir ~/vm-shared
2. mkdir ~/test

in VBox UI:
1. add folder ~/vm-shared with name ""shared""
2. add folder ~/test with name ""test""

on guest (under root):
1. mkdir /mnt/shared && mount -t vboxsf -o uid=1000,gid=100 shared /mnt/shared
2. mkdir /mnt/test && mount -t vboxsf -o uid=1000,gid=100 test /mnt/test

now on guest, try to execute following command:
1. mkdir /mnt/shared/somedir
2. mkdir /mnt/test/somedir

Second command executed successfully, but first command fails with protocol error.",indifferent
14414,No DNS server information on DHCP enabled NATNetworks,Linux,VirtualBox 5.0.0,2015-08-07T13:43:58Z,2015-08-17T19:28:16Z,2015-08-17T19:28:16Z,"I've configured a NATNetwork with DHCP enabled:

{{{
NetworkName:    NatNetwork
IP:             10.0.3.1
Network:        10.0.3.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
loopback mappings (ipv4)
        127.0.0.1=2
}}}

It created a DHCP server configuration like this:
{{{
NetworkName:    NatNetwork
IP:             10.0.3.3
NetworkMask:    255.255.255.0
lowerIPAddress: 10.0.3.4
upperIPAddress: 10.0.3.254
Enabled:        Yes
}}}

When the VM is started it requests the IP address to DHCP server. On the DHCP response (DHCP ACK package) there is no DNS information, but there is the Domain Name (DNS suffix).

If I manually configure the DNS in the virtual machine to 10.0.3.1 the name resolution works.
",jacksonfoz
14245,Guest Additions are broken when built with new versions of system Mesa,Linux,VirtualBox 4.3.28,2015-07-06T15:43:24Z,2015-08-01T20:20:57Z,2015-08-01T20:20:57Z,"Most Linux distributions use system versions of Mesa instead of the bundled Mesa 7.2. But with new versions of Mesa Guest Additions are broken. For example, glxinfo reports (null) for ""OpenGL renderer string"" and other glGetString() requests.

This patch from Fedora is used for new Mesa support by various distributions:

http://cvs.rpmfusion.org/viewvc/rpms/VirtualBox/devel/VirtualBox-4.3.10-mesa_guest.patch?revision=1.1&root=free&view=markup

Likely it's incomplete.

Perhaps Virtual Box 5.0+ should support Mesa 10+ because Mesa 7.2 is really old.",Pulfer
10686,Kernel Panic: MONITOR/MWAIT,Linux,VirtualBox 4.1.14,2012-06-20T01:56:16Z,2015-07-25T03:44:42Z,2015-07-25T03:44:42Z,"I'm running Slackware 13.37 x86 host and guest on VirtualBox 4.1.14, this is on a Sony Vaio with a Intel Core i3, and when I try to boot the Slack guest it kernel panics and gives me this message;

kernel panic not syncing: Attempted to kill the idle task!
atkbd serio0: Spurious ACK on isa0060/serio0. Some program may be trying 
to access hardware directly

I'm attaching a screen shot to this bug report you can also see.

I have a desktop running an AMD and the guest will boot and run just fine, it's only on my Vaio with the i3 that it won't boot, so I recompiled the kernel 3.4.3 hoping this would help with no luck.

I've also attached the VB log....

I also noticed that if I try to boot the Slackware 13.37 CD it too won't boot on the Sony and kernel panics and locks up as well.

I read there seems to be an issue here with Slack and i3/i5/i7 cpus?

I hope someone might know a fix for VB OSE 4.1.14 I can apply to get this to bootup?

THANKS

P.S. Since I'm running Slackware and I compiled the OSE version into a slackware package, this is the build script I used;

http://slackbuilds.org/repository/13.37/system/virtualbox/

Until this gets updated, I'm not able to use 4.1.16....

",DasFox
13806,Video capture in Linux does not work (small file with empty green .webm video),Linux,VirtualBox 4.3.20,2015-02-03T13:47:40Z,2015-06-18T12:53:37Z,2015-06-18T12:53:37Z,"I know similar bug reports are made but problem still exist and is not solved like I noticed on some bug report comments.

Host: 64-bit Ubuntu 14.04.1 LTS with 3.18.5 generic kernel.

Using ATI-AMD graphics card HD 7770 series on host:
    $ lspci -vnn | grep VGA
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller])

Also guest additions are installed in guests and 3D acceleration enabled from settings. Did not help. Still I get small .webm file with empty green video.

I tried also classic Gnome fallback - I mean I turned Unity off but still no help. I tried with or without guest additions - no help. Certainly also from settings I turned 3D acceleration on and off.
I am running 64-bit Ubuntu 14.04.1 LTS and guest systems are Kubuntu 14.04.1 LTS, Lubuntu 14.04.1 LTS, Xubuntu 14.04.1 LTS Ubuntu Mate 14.04.1 LTS. I tried both 32-bit and 64-bit guests - same problem.
I also tried different video players - VLC, SMPlayer, Totem, Xine - always blank green video and that's it",Edmund Laugasson
14204,VM screen flickers,Linux,VirtualBox 4.3.28,2015-06-16T20:29:22Z,2015-06-17T23:11:02Z,2015-06-17T23:11:02Z,"Virtual machine is constantly flickering and when I log in grey base coloured squares appear until I press in the higher left corner where dash is. But flickering is making working with VM impossible.

I am using Virtualbox 4.3.26. My host is Ubuntu 15.04 with custom NVIDIA driver (version 346.72) for Geforce GTX 960M. My guest is Ubuntu 14.04.02 LTS.

All details about this annoying regression are described and available here: https://forums.virtualbox.org/viewtopic.php?f=3&t=67823",SamH
14189,Port forwarding silently fails when source ports are privileged,Linux,VirtualBox 4.3.28,2015-06-09T21:21:38Z,2015-06-09T23:38:27Z,2015-06-09T23:38:27Z,"I just spent a really unproductive hour or so trying to work out why I was getting ""Connection refused"" from a test LDAP server in a VM.

Then I resorted to trying to forward the port using SSH. The SSH client reminded me that privileged ports cannot be forwarded unless you're root. (Oh yeah, Unix. Privileged ports. I remember now.)

So my suggestion is:

 - The VirtualBox GUI should warn the user about this.

 - There should be an error displayed if port forwarding fails because the port is privileged.

The documentation at https://www.virtualbox.org/manual/ch06.html mentions the limitation, but it states that the VM will refuse to start in such a situation. That doesn't appear to be true -- I tried restarting the VM and didn't get a useful error message.",meta
10092,Error message when using a normal command which should not give this message,Linux,VirtualBox 4.1.8,2011-12-27T12:27:01Z,2015-05-29T16:01:19Z,2015-05-29T16:01:19Z,"After giving the command (as root):
{{{
su - vboxuser -c ""/usr/bin/VBoxManage controlvm ""vmname"" acpipowerbutton""
}}}
the following command is given in a loop each second
{{{
su - vboxuser -c ""/usr/bin/VBoxManage -nologo showvminfo ""vmname"" -machinereadable"" | grep -q 'VMState=""poweroff""'
}}}
until this command returns 0 and the loop is ended.
Apparently at the moment the command returns VMState=""poweroff"" the command VBoxManage also gives the following error message:
{{{
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee nsISupports
Context: ""COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))"" at line 1698 of file VBoxManageInfo.cpp
}}}",Freek de Kruijf
14045,full screen mode not ok with 2 sceens  under Ubuntu 14.04  64Bit,Linux,VirtualBox 4.3.26,2015-04-11T21:04:09Z,2015-04-13T05:54:53Z,2015-04-13T05:54:53Z,"on full screen mode - the guest appears only half (screen_shot attach to this ticket)

One Screen is Belinea, other one Fujitsu Siemens (different sizes)

On Fujitsu Siemens screen: in full screen mode - onle half display (see screen-shot)

On Belinea (smaler one): display is cut on the right side

",Yupi
13991,NUL character with a value of 0 ^@ Shown In Linux Console,Linux,VirtualBox 4.3.24,2015-03-26T07:46:08Z,2015-03-26T11:12:54Z,2015-03-26T11:12:54Z,"Hi,

My Specs;

Slackware 14.1 x86_64 - Host
screen size 1920x1080
Virtualbox 4.3.24 - (compiled from source)


Slackware 14.1 x86_64 - Guest
screen size 1920x965
Virtualbox 4.3.24 - (Guest Additions installed)

I noticed when I restart or shutdown Slackware, in the console, I am seeing the NUL character with a value of 0 that is represented as `^@` appear next to text on the screen.

I thought at first something in the Slackware system was causing this.

I was running the Guest with the default of 'Auto-resize Guest Display', this causes the console to have a small size, and it seems for some reason Virtualbox doesn't like it and creates the Nul Character, because if I change the Guest to 'Scaled Mode' it never appears.

I tested this several times changing back and forth with the 'Auto-resize Guest Dispaly' and 'Scaled Mode', and everytime it was on 'Auto-resize Guest Display' it appeared, and everytime it was on 'Scaled Mode' it did not appear.

I'm attaching a screen shot, called vb_character.jpg, notice the line with the red dot I marked, to the far left the word; `^@Sending`...",VBoxGrl
13970,Switch desktop defect,Linux,VirtualBox 4.3.26,2015-03-20T09:46:09Z,2015-03-20T09:46:09Z,2015-03-20T09:46:09Z,"On Linux Mint Mate, I have a two-monitor linux VM, and when I boot up, it starts with just one window. The second window is launched a few second later.
If in the meantime, I change desktop (using ctrl-alt right or left, for example), the first window stays in the starting desktop, but the second one is opened in the second desktop.

Would be great if they were opened both in the same desktop.

Thank you.",malarittu
13930,"Shared folders: ""umount -f"" required",Linux,VirtualBox 4.3.24,2015-03-06T12:53:56Z,2015-03-06T12:53:56Z,2015-03-06T12:53:56Z,"Host: openSUSE 13.1 (64bit)
Guest: openSUSE 13.2 (64bit)",robert spitzenpfeil
13834,linked clone - uuid already exists,Linux,VirtualBox 4.3.22,2015-02-14T09:48:11Z,2015-02-14T09:48:11Z,2015-02-14T09:48:11Z,"goodmorning, I have this problem, and I think that all versions from 4.3 are affected, because the problem doesn't .
I created 1 virtualmachine, started, SO installed, closed, everything fine.
I want a (one or more) clone of this machine, type linked-clone, so I use the procedure to create a linked-clone.
If I remove 1 of the 2 machine (remove only) and than I re-add there is the error about ""uuid already exists"" and I can't re-add the machine.
I think the problem is that each machine load all the structure of snapshots for both the machine, so if I re-add the one removed, it sais that already exists.
I have this problem with host Linux and Windows",sigfrido.barb
13720,Virtualbox Crashes in r600_dri.so Mesa Graphics Driver When Running Ubuntu Guest With Guest Additions Installed,Linux,VirtualBox 4.3.20,2014-12-27T22:25:00Z,2015-01-12T22:47:14Z,2015-01-12T22:47:14Z,"On installing guest additions on a Ubuntu 14.10 guest and rebooting, the guest and virtualbox crash immediately _after_ the _login_ screen (i.e. after entering the password and Unity starts setting itself up). Subsequently, every reboot crashes at the same point and only un-installation of the guest additions can work around the problem.

The crash is always reproducible. Debugging details including a coredump, stack trace and register information will be found attached to this bug report.

The system in question is running the 64 bit version of Virtualbox 4.3.20 (4.3.20-96996~Ubuntu~raring) on a 64 bit Ubuntu 14.04 system running kernel 3.8.1.

The system runs the free Radeon drivers. The card is an AMD Radeon Evergreen (REDWOOD) PCI ID: 1002:68c1 (Dell Mobility Radeon HD 5650).

I am using this PPA for the MESA drivers: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers but the crash is reproducible with the stock Ubuntu 14.04 MESA drivers and has been for a while (see the next paragraph).

I have been seeing this problem over the last several (I'd say 3 or 4) iterations of Virtualbox as well as the last 2 iterations of the OS (Currently Ubuntu 14.04 but previously 12.04), and across a wide range of kernels.

Further debugging information (including a Stack Trace e.t.c.) is attached but here are the basics:

- The crash occurs due to Signal 11 in r600_dri.so
- Summary Segv Analysis:
{{{ 
Segfault happened at: 0x7f3ef00ed1bd <_mesa_MultiModeDrawArraysIBM+93>:        
mov    (%r15,%rbx,1),%esi
 PC (0x7f3ef00ed1bd) ok
 source ""(%r15,%rbx,1)"" (0x00000030) not located in a known VMA region (needed r
eadable region)!
 destination ""%esi"" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
}}}
- The kernel has the following traps message in its log after the crash:
{{{
ShCrOpenGL[24186]: segfault at 30 ip 00007ff0902eb1bd sp 00007ff0918afa80 error 4 in r600_dri.so[7ff09016e000+7b8000]
}}}

Exactly the same crash occurs with the most recent Guest Additions ""test build"" (Guest Additions, revision 97191), but with the same (un-updated) version of Virtualbox.

See attached files for further debugging information.",marete
13613,Update vboxadd and vboxadd-service startup scripts for LFS 7.6,Linux,VirtualBox 4.3.18,2014-11-13T06:29:27Z,2014-11-13T06:29:27Z,2014-11-13T06:29:27Z,"Since /etc/rc.d/init.d/functions is removed in LFS 7.6, the existing vboxadd and vboxadd-service startup scripts will not work.
That means those scripts have to be updated.",hykwok
13516,VBoxManage stucks on long operations,Linux,VirtualBox 4.3.18,2014-10-16T12:32:58Z,2014-11-06T16:27:08Z,2014-11-06T16:27:08Z,"Host OS: openSUSE 13.1 or Fedora 20 or RHEL7
Guest OS: any linux I've tried so far.

Steps to reproduce:

1. Import provided OVA file at least 3 times, avoid spaces in VM name. Provided OVA is simple Fedora-20 install, cleaned from garbage, installed openjdk build dependencies and VBox guest additions, nothing special.

2. Change shared folder path to existing writable folder, but leave ""shared"" as name of share.

3. Install mercurial, run following command:
{{{ hg clone 'http://hg.openjdk.java.net/jdk8u/jdk8u/' && cd 'jdk8u' && bash get_source.sh }}}

4. Download jdk-7u67-linux-i586.tar.gz from http://java.sun.com

5. Start all imported VMs, does not matter headless or not.

6. Open number of terminals and run following command in each one of them, change path to jdk8u source, path to jdk-7u67 and name of VM:
{{{
while true; do bash vm-build.sh \
--with-major=8 \
--with-src=/home/user/src/jdk8u \
--with-tag=jdk8u20-b26 \
--with-boot-jdk=/home/user/jdk-7u67-linux-i586.tar.gz \
--with-vm=""Fedora-20-i586-test1"" ; done
}}}
7. Watch the output from time to time, it usually stucks during make pretty soon on at least 1 of the running VMs, usually during first or second iteration.


OVA file and 2 scripts:
https://drive.google.com/folderview?id=0B5Kp-cB1sXJrRDd6RlRwOGxLTTg&usp=sharing",indifferent
13568,"mount vboxsf won't accept option ""user""",Linux,VirtualBox 4.3.18,2014-10-29T12:30:33Z,2014-11-02T20:32:51Z,2014-11-02T20:32:51Z,"Even though the vbox shared folders can be mounted through mount(8) and a usual /etc/fstab entry can be created, some options accepted by mount won't work for vboxsf, e.g. ""user"" and ""group"".

{{{
juanlu@minted ~ $ tail /etc/fstab
# mint shared folder
mint /media/sf_mint vboxsf defaults,user,uid=1000,gid=999 0 0
juanlu@minted ~ $ mount mint
Only root can mount shared folders from the host.
juanlu@minted ~ $ sudo !!
sudo mount mint
unknown mount option `user'
valid options:
  rw         mount read write (default)
  ro         mount read only
  uid       =<arg> default file owner user id
  gid       =<arg> default file owner group id
  ttl       =<arg> time to live for dentry
  iocharset =<arg> i/o charset (default utf8)
  convertcp =<arg> convert share name from given charset to utf8
  dmode     =<arg> mode of all directories
  fmode     =<arg> mode of all regular files
  umask     =<arg> umask of directories and regular files
  dmask     =<arg> umask of directories
  fmask     =<arg> umask of regular files
}}}

This might be just a non-implemented feature in mount.vboxsf.c. If it's not, then probably a clarification is needed in the user manual that not all mount(8) options are allowed for vboxsf, and in that case it would be nice to have a rationale of why is that.
 ",juanlu001
13275,VBoxManage does not set hostonly adapter name,Linux,VirtualBox 4.3.14,2014-08-11T11:53:49Z,2014-10-18T09:07:02Z,2014-10-18T09:07:02Z,"I've got a script that creates VM's for me and one of the lines is this one:
VBoxManage modifyvm ""$VM"" --nic2 hostonly --hostonlyadapter1 'vboxnet0'

I can see the adapter in the network section in the GUI, however the name is blank. To populate the name I need to use the GUI and enter Settings, Network, applicable adapter and press Ok. I.e. I do not need to change anything, just press Ok for the hostonly adapter to have the name set.",Onkelringnes
13416,Add option to allow VM to swap,Linux,VirtualBox 4.3.16,2014-09-18T09:08:41Z,2014-09-18T09:08:41Z,2014-09-18T09:08:41Z,"Test setup is the following:

 * Host machine: Linux, 16GB RAM, 16GB swap.
 * Guest 1: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 2: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 3: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk
 * Guest 4: Linux, 5GB RAM, 2GB swap, 4.5GB ramdisk

Steps to reproduce:
1. Start all 4 VMs.
2. Start growing ramdisk.

When host free RAM is close to zero - VirtualBox will abort one of the VMs. Swap usage on host is still very low.

Please add the option to allow VM to swap, so all of those 4 VMs will be able to work together, even if slower (swap based on SSD disk makes it not so bad).",indifferent
13079,clonevm makes immutable hard disks normal in clone,Linux,VirtualBox 4.3.12,2014-05-31T12:22:05Z,2014-05-31T12:22:05Z,2014-05-31T12:22:05Z,"When cloning a VM, '''ALL''' the cloned new VM's hard disks are of type '''normal''' whereas some of the source VM's hard disks are of type '''immutable'''.  Cloning is not preserving hard disk type and is resetting immutable hard disks to normal.

Both host and guest are Ubuntu Trusty Server.",Senthil Nathan
12812,*.start and *.stop scripts are not created by VBoxManage modifyvm myvm --autostart-enabled on,Linux,VirtualBox 4.3.8,2014-03-12T06:54:47Z,2014-03-12T06:54:47Z,2014-03-12T06:54:47Z,"I have followed the steps in this tutorial: [http://www.vionblog.com/virtualbox-4-3-autostart-debian-wheezy/]

The problem is no *.start or *.stop files are created in /etc/vbox/ (and no errors are shown) after running the command:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled on
}}}

In case it helps, trying to disable auto start for the same VM does give an error:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled off
VBoxManage: error: Removing machine 'myvm' to the autostart database failed with VERR_FILE_NOT_FOUND
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(AutostartEnabled)(ValueUnion.f)"" at line 2616 of file VBoxManageModifyVM.cpp
}}}

Host os: Ubuntu Server 12.04-4 (amd64)

VirtualBox: 4.3.8

This issue was reported on the forum a few weeks ago, but there has been no reply:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=60425&p=282223#p282223]

Thanks!


For reference, here's user/group involved:

{{{
$ whoami 
dan
$ groups
dan adm cdrom sudo dip plugdev lpadmin sambashare vboxusers
}}}
 

The contents of /etc/vbox

{{{
$ ls -al /etc/vbox/
total 12
drwxrwxr-t   2 root vboxusers 4096 Mar 12 00:55 .
drwxr-xr-x 101 root root      4096 Mar 12 02:11 ..
-rw-r--r--   1 root root       239 Mar 12 00:55 autostart.conf
}}}

content of autostart.conf:

{{{
# Default policy is to deny starting a VM, the other option is ""allow"".
default_policy = deny

# user dan is allowed to start virtual machines but starting them
# will be delayed for 10 seconds
dan = {
 allow = true
 startup_delay = 10
}
}}}

uname:

{{{
$ uname -a
Linux ubu-host64 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
}}}",Dan Rollo
11922,Document on creating CD/DVD (and installing Guest Additions) do not mention VM must be shut down,Linux,VirtualBox 4.2.14,2013-07-03T12:44:00Z,2013-07-04T19:52:51Z,2013-07-04T19:52:51Z,"I'm running a CentOS 6 VM guest on an XUbuntu 13.04 host using virtualbox 4.2.10_Ubuntu r84101

Under Machine -> Settings -> Storage, the menu item to ""Add a CD/DVD Device"" is disabled for both the IDE and SATA controllers.

Neither https://www.virtualbox.org/manual/ch04.html#idp14782496 
nor https://www.virtualbox.org/manual/ch03.html#settings-storage say anything about shutting down in order to use Device -> Storage -> Add CD/DVD Device.

The latter says ""You can modify these media attachments freely.""

Please add text to these manual pages to make it clear how to add a CD or DVD device.
",David Biesack
11562,VirtualBox does not honour regular/shareable disks while cloning.,Linux,VirtualBox 4.2.6,2013-03-05T07:35:57Z,2013-03-05T07:35:57Z,2013-03-05T07:35:57Z,"Linked copy doesn't clone any disks. Full copy clones all disks, even when they are shareable. It would be cool to have third clone option, that clones all regular disks and uses shareable disks with the same properties and from the same location, like the source VM.
For example, it would be convenient for Oracle RAC emulation setup.",sknaumov
11462,Problem font with VirtualBox from a terminal in Red Hat 6.2,Linux,VirtualBox 4.2.6,2013-02-06T13:48:27Z,2013-02-22T14:11:53Z,2013-02-22T14:11:53Z,"Hi, 
When we launched !VirtualBox, we had only ""squares"" on the GUI.
{{{
[root# VirtualBox 
Xlib:  extension ""SYNC"" missing on display ""10.102.130.2:32.0"".
}}}
And firstable, we had a failed installation with vboxpci 
{{{
[root@opisidb1 log]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules                         [  OK  ]
Uninstalling old VirtualBox DKMS kernel modulesWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Trying to register the VirtualBox kernel modules using DKMSWARNING: /lib/modules/2.6.32-220.13.1.el6.x86_64/extra/vboxpci.ko needs unknown symbol kmem_cache_alloc_trace
                                                           [  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxpci failed. Please use 'dmesg' to find out why)

root#dmesg
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x51c offMax=0x28308
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x62c offMax=0x2a7f8
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x664 offMax=0x2a8d0
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
vboxdrv: Found 8 processor cores.
vboxdrv: fAsync=0 offMin=0x4fc offMax=0x27658
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.6 (interface 0x001a0004).
vboxpci: Unknown symbol kmem_cache_alloc_trace
}}}",fornesi
2652,Gentoo hardened (grsecurity) hosts not supported,Linux,VirtualBox 4.2.2,2008-11-25T12:59:06Z,2012-10-22T08:45:10Z,2012-10-22T08:45:10Z,"Hello,


I am running VirtualBox 2.0.6 on a Gentoo Hardened Host (2.6.23-r7).

Running normal linux systems as guest works fine, however when I try to boot a Gentoo Hardened _Guest_ system, VirtualBox reports a Guru Mediation Error and the VM freezes on kernel bootup. I tried with various hardened Guest kernels (2.6.23-r7, 2.6.24-r3 and 2.6.25-r9, all hardened-sources from Gentoo) but the error remains. Grsecurity/PAX presetting in the kernel is set to ""high"". The produced log is attached.


I will try to narrow down the search on why the kernel crashes by disabling some of the hardened options but so far I didn't have much success.

Best regards,


Christian Holler",Christian Holler
9054,Add Host CPU/System info to About or other dialog.,Linux,VirtualBox 4.0.4,2011-06-09T21:00:26Z,2012-09-12T09:38:47Z,2012-09-12T09:38:47Z,"Hello, thanks for an awesome project.  I use it for a pre-made LAMP development environment:  http://drupal.org/project/quickstart.

My users are asking me whether they should install the i386 or amd64 version.  

Could you please add a ""System info"" dialog to the Virtualbox host UI?

Basically, CPU info, host OS info, AMD-V/VT-X extensions enabled, etc.  For a  big bonus, ""This system can/can't run a 64-bit guest.""  Other things could be added (3d support, USB, etc) but for now just the 32/64 bit info would be great.

This might seem trivial, but would greatly simplify supporting my users, saving them alot of trouble choosing which guest to download, and helping me help them.

Thanks again for a great project,

Mike
",MIchael Cole
9964,cloned(full) openSUSE12.1 is not able to find it´s harddrive,Linux,VirtualBox 4.1.6,2011-11-28T16:49:27Z,2011-11-28T16:56:50Z,2011-11-28T16:56:50Z,"I´ve made two clones of a working openSUSE12.1 64bit vm(on a openSUSE12.1 64 bit host).

Both have problems to start up correctly.

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

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

I attach a screenshot for the exact error message and the logs.",maninred2
9723,"same disk boots with fullDevice, but not with partitionedDevice",Linux,VirtualBox 4.1.2,2011-10-08T20:53:59Z,2011-10-08T20:53:59Z,2011-10-08T20:53:59Z,"i've recently started to use vbox with debian stable, don't remember which version, and then switched to debian unstabe because of unsupported hw. with that vbox got upgraded to 4.1.2_Debian r38459

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

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

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

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

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

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

Also, the display is configured to never go to sleep in ubuntu.",kihjin
8960,Virtualbox Unity Launcher Integration,Linux,VirtualBox 4.0.4,2011-05-24T23:41:59Z,2011-05-26T15:48:30Z,2011-05-26T15:48:30Z,"Hello,

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

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

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

It's registered under the MIT license.",Daniel
6519,Network bridge does not work with multiple mac addresses on the guest side,Linux,VirtualBox 3.1.6,2010-04-10T00:41:23Z,2011-02-19T18:34:59Z,2011-02-19T18:34:59Z,"The Bridged network mode seems to be unable to deal with multiple MAC addresses being used to send packets from a guest. This situation occurs when a network bridge is configured inside a guest system.

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

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

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

A reasonable alternative to accepting *all* packets would be to enlarge the MAC address buffer, but this would require a far more complex network switch implementation.",Ivo Smits
6323,Can't get IP Forwarding to work with Host-only adapter,Linux,VirtualBox 3.0.6,2010-03-04T07:48:08Z,2011-01-26T12:41:53Z,2011-01-26T12:41:53Z,"Hello, 

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

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

[*]1 bridge br0

[*]2 tun/tap interfaces tap0 and tap1


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

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

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

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

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

Thank you, 

Laurent Sebag",grattemedi
5130,"Bridging eth0 needs ""link"" in order to work",Linux,VirtualBox 3.0.6,2009-10-06T12:30:03Z,2011-01-26T12:41:31Z,2011-01-26T12:41:31Z,"Ran into problem when trying to bridge virtual Ubuntu 9.10 with host Fedora 11 using the distributions VBox-packages. Using NIC eth0 (Thinkpad T61)

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

kernel: 2.6.30.8-64-fc11.i586
VBox 3.0.6

I don't have a problem with the issue as there is a easy workaround, but one have to be aware of it.",Niklas Andersson
7952,gues key mapping problem while host is using XkbOptions,Linux,VirtualBox 4.0.0,2010-12-30T09:23:05Z,2011-01-19T02:02:53Z,2011-01-19T02:02:53Z,"My host is archlinux with xorg 7.6, and i am using XkbOption for some key mapping workaround, like blow:


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


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

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

It seems that virtualbox has ignored the XkbOptions and accesses the keyboard as is.",Zer4tul
7804,"When mounting shared host files with vboxsf, softlinks fail to be copied.",Linux,VirtualBox 3.2.12,2010-12-07T20:23:47Z,2010-12-07T20:23:47Z,2010-12-07T20:23:47Z,"Description:

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

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

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

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

",V
6576,Suggestion for improving the usermanual: Hostonly connection  should mention routing.,Linux,VirtualBox 3.1.6,2010-04-22T15:09:46Z,2010-05-04T14:14:20Z,2010-05-04T14:14:20Z,"I used virtualbox before version 2.0, and now I need it in a production case.

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

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

I tried a random few, and ended up with ""host only"", which I think should mention the option of using routing from the guest to the outside world. This would've made my experience with the new version a lot easier: I could've selected the right option right away. ",Roger Wolff
4939,alt-tab back out of guest doesn't work,Linux,VirtualBox 3.0.6,2009-09-10T13:33:47Z,2010-04-04T02:11:47Z,2010-04-04T02:11:47Z,"Host: Centos 5.3, GNOME 2.16.0
Guest: Ubuntu 9.04, GNOME 2.26.1, guest additions installed

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

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

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

It would be really, really useful to be able to define some hotkeys which are *not* passed through like this... Please! :-)",Andrew Clegg
4924,Change mount behaviour in suse guests (vboxadd),Linux,VirtualBox 3.0.4,2009-09-07T12:45:12Z,2010-03-12T04:06:17Z,2010-03-12T04:06:17Z,"Having vboxsf in the fstab with opensuse is not that good, as suse cannot umount volumes correctly (did not track down this one), however I think the way devices get unmounted is not the best way to do so.

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

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

For all described the attached patch is working.",Michael Kromer
6148,international characters cannot be created on mounted linux guest shared folder,Linux,VirtualBox 3.1.2,2010-02-09T14:16:21Z,2010-02-09T14:16:21Z,2010-02-09T14:16:21Z,"Im using linux ubuntu as guest running on linux host ubuntu. shared folder mount perfectly and I can copy move and delete any files on it, but files with caracters with acentos gives me ""protocol error"" see the command:

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

the above creates the file test.txt

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

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

thanks.",Marcus Leandro
6132,VBoxManage confuses VM names starting with dash character (-) with command line option names,Linux,VirtualBox 3.1.2,2010-02-04T14:22:48Z,2010-02-04T14:22:48Z,2010-02-04T14:22:48Z,"When playing with VBoxManage I created a VM with name ""--ostype"" (by mistake - there was an error in my shell script that invoked VBoxManage)

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

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

Apparently, VBoxManage confuses VM names starting with dash character (-) with command line option names. !VirtualBox GUI does not have such problem.",xlogger
5489,high-bandwidth multicast traffic,Linux,VirtualBox 3.0.10,2009-11-17T16:30:27Z,2009-12-04T11:00:18Z,2009-12-04T11:00:18Z,"Hi!

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

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

I will attach the kernel ring buffer log. ",Stefaan
3645,files in guest shared folders seems not to reflect changes done in host,Linux,VirtualBox 2.1.4,2009-04-06T20:34:53Z,2009-04-15T08:44:17Z,2009-04-15T08:44:17Z,"I have a guest OS (Ubuntu Hardy Heron) with shares a folder (in read/write) with the host OS (Ubuntu Hardy Heron). I use a web editor to edit the files in this folder in the host OS so the modifications should be seen in the guest OS (the shared folder, mounted in the guest, is the root directory of an apache web server installed just in the guest).
The problem is that, when I modify a file in the host side, these changes seem not reflected correctly in guest side. Via a simple cat or less or vi the modified files seem correct but with apache the modifications aren't reflected (I can test this via ""telnet server 80""). In fact often the modifications are seen as strange characters or other times other strange behaviours happen.
I can solve this either:
- umount and then re-mount the shared folder (but I have to do this after every file change)
or
- simply edit the file via vi (guest side) and, with no modifications, save the file",Marco 
21310,Linux/arm64 guest,all,VirtualBox-7.0.4,2022-11-24T13:20:48Z,2022-11-24T13:20:48Z,2022-11-24T13:20:48Z,"hi,
please add support for guest ARM64 architecture at least with Linux (and maybe Android) as OS.

As so, as example, we can run a RaspberryOS/arm64 as guest.",Valerio Messina
21234,"upgrade vb from 6.1.40 to 7 or fresh install vb7,vmsvga(3D) conflict with xrdp's dri3 & glamor",all,VirtualBox-7.0.2,2022-11-02T15:24:37Z,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
21197,Make Shared Folder accessible by default in at least certain Linux variants,all,VirtualBox-7.0.2,2022-10-23T22:35:12Z,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
21070,"Linux VMs hang on boot when ""Host Pipe"" Serial Port is enabled and the OS has console=tty[x] set",all,VirtualBox 6.1.34,2022-08-19T14:26:24Z,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
21038,6.1.36 regression. Recording VMs audio not working,all,VirtualBox 6.1.36,2022-07-27T00:17:11Z,2022-07-27T00:17:11Z,2022-07-27T00:17:11Z,"In setting select Display->Recording, audio only and highest quality.
The .webm file is created during run (opening the file is logged correctly).
Once the VM is powered down, the file is erased. Tested on windows and debian host (debian guest).
The webm file length never exceeds a few hundred bytes.
Install .34 again, and all was well again.",KurtMielke
21013,Linux guest additions use 0.06 Hz refresh rate for custom display resolutions,all,VirtualBox 6.1.34,2022-06-29T14:55:35Z,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
20725,VirtualBox OHCI-controller randomly skips sending URBs to the host,all,VirtualBox 6.1.30,2021-12-14T13:35:43Z,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
20827,VBox Guest Additions to prompt Linux users to install development modules,all,VirtualBox 6.1.32,2022-02-14T09:25:31Z,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
20722,QOpenGLShader::link: error: fragment shader uses too many input components (52 > 40),all,VirtualBox 6.1.30,2021-12-11T16:09:58Z,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
20678,Keep opened and running each Virtual Display in each Monitor when the Guest is left to return to the Host,all,VirtualBox 6.1.28,2021-11-19T21:28:01Z,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
20603,Accessibility. Audio driver closes when using the console linux screen reader in guest,all,VirtualBox 6.1.26,2021-10-12T18:34:12Z,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
19561,Nested virtualization BUG: soft lockup - CPU#4 stuck for 22s! [CPU 1/KVM:28838],all,VirtualBox 6.1.6,2020-05-05T21:23:40Z,2020-12-16T07:19:30Z,2020-12-16T07:19:30Z,"I am running a KVM vm inside virtualbox. if the VM is set with 1 CPU, it works well. But if i increase the CPU to 2 or more, i am getting CPU stuck message inside virtualbox.

HOST OS: MAC OSX
Virtualbox Version: 6.1.6
Host have 12 cores and 64gb ram

Guest OS: Ubuntu 18.04
Guest CPU: 4
Guest Ram: 20GB
Nested VT-x/AMD-V and PAE/NX is enabled in processor settings

Nested VM Guest OS: debian
Nested VM Guest CPU: 2
Nested VM Guest Ram: 4GB

Partial syslog message and vbox.log is attached",hamerins
19099,openSUSE Leap 42.3 - cannot compile vboxsf module,all,VirtualBox 6.0.14,2019-11-20T14:53:44Z,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)
19834,VM slow down when video recording enabled,all,VirtualBox 6.1.10,2020-08-26T20:09:56Z,2020-08-26T20:15:19Z,2020-08-26T20:15:19Z,"To reproduce bug you can try create VM with one core and start it with and without video recording. With video recording enabled you must see some slow down of working VM.

This happens because of slow working vpx_codec_encode call under lock inside RecordingStream::Process:

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L373

{{{
int RecordingStream::Process(RecordingBlockMap &mapBlocksCommon)
{
    LogFlowFuncEnter();

    lock();

    ...
                    rc2 = writeVideoVPX(msTimestamp, pVideoFrame);
    ...

    unlock();

    LogFlowFuncLeaveRC(rc);
    return rc;
}

}}}

And writeVideoVPX calls vpx_codec_encode:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/RecordingStream.cpp#L1161

{{{
vpx_codec_err_t rcv = vpx_codec_encode(&pCodec->VPX.Ctx,
                                           &pCodec->VPX.RawImage,
                                           pts                          /* Timestamp */,
                                           this->Video.uDelayMs         /* How long to show this frame */,
                                           0                            /* Flags */,
                                           pCodec->VPX.uEncoderDeadline /* Quality setting */);
}}}

In fact vpx_codec_encode working slow beacuse of last parameter ""deadline"" by default is zero (which means infinite deadline for encoding)

Interesting part is that in 5.x virtualbox branch there was a code which fill the default value of uEncoderDeadline but this code not present in 6.0/6.1  branches...


{{{
/**
 * Invalidates the video recording configuration.
 */
void Display::i_videoRecInvalidate(void)
{
    AssertPtr(mParent);
    ComPtr<IMachine> pMachine = mParent->i_machine();
    Assert(pMachine.isNotNull());

    mVideoRecCfg.enmDst = VIDEORECDEST_FILE; /** @todo Make this configurable once we have more variations. */

    /*
     * Cache parameters from API.
     */
    com::SafeArray<BOOL> aScreens;
    HRESULT hrc = pMachine->COMGETTER(VideoCaptureScreens)(ComSafeArrayAsOutParam(aScreens));
    AssertComRCReturnVoid(hrc);

    mVideoRecCfg.aScreens.resize(aScreens.size());
    for (size_t i = 0; i < aScreens.size(); ++i)
        mVideoRecCfg.aScreens[i] = aScreens[i];

    hrc = pMachine->COMGETTER(VideoCaptureWidth)((ULONG *)&mVideoRecCfg.Video.uWidth);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureHeight)((ULONG *)&mVideoRecCfg.Video.uHeight);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureRate)((ULONG *)&mVideoRecCfg.Video.uRate);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFPS)((ULONG *)&mVideoRecCfg.Video.uFPS);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureFile)(mVideoRecCfg.File.strName.asOutParam());
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxFileSize)((ULONG *)&mVideoRecCfg.File.uMaxSizeMB);
    AssertComRCReturnVoid(hrc);
    hrc = pMachine->COMGETTER(VideoCaptureMaxTime)((ULONG *)&mVideoRecCfg.uMaxTimeS);
    AssertComRCReturnVoid(hrc);
    BSTR bstrOptions;
    hrc = pMachine->COMGETTER(VideoCaptureOptions)(&bstrOptions);
    AssertComRCReturnVoid(hrc);

    /*
     * Set sensible defaults.
     */
    mVideoRecCfg.Video.fEnabled = true; /* Enabled by default. */

    if (!mVideoRecCfg.Video.uFPS) /* Prevent division by zero. */
        mVideoRecCfg.Video.uFPS = 15;

#ifdef VBOX_WITH_LIBVPX
    mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
#endif

#ifdef VBOX_WITH_AUDIO_VIDEOREC
    mVideoRecCfg.Audio.fEnabled  = false; /* Disabled by default, unless set otherwise below. */
    /* By default we use 48kHz, 16-bit, stereo for the audio track. */
    mVideoRecCfg.Audio.uHz       = 48000;
    mVideoRecCfg.Audio.cBits     = 16;
    mVideoRecCfg.Audio.cChannels = 2;
#endif

}}}


Here is:
>mVideoRecCfg.Video.Codec.VPX.uEncoderDeadline = 1000000 / mVideoRecCfg.Video.uFPS;
",gim
19801,add redhat8_ks.cfg kickstart config to unattended templates,all,VirtualBox 6.1.10,2020-08-07T14:16:55Z,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)
19647,Fedora: Removing suid root bit from VBoxDRMClient,all,VirtualBox 6.1.10,2020-06-09T09:32:47Z,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)
10085,making a symlink fails on a shared folder with EROFS,all,VirtualBox 4.1.8,2011-12-26T14:02:52Z,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
19562,VBoxClient on Linux : leaves defunct xrandr zombies,all,VirtualBox 6.1.6,2020-05-06T00:04:29Z,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
4290,Can't create hard links on a shared folder (= can't use zsh if home directory is shared folder),all,VirtualBox 2.2.4,2009-06-23T19:10:27Z,2020-04-28T09:59:37Z,2020-04-28T09:59:37Z,"It seems the shared folders do not allow hard links to be created (link() system call). The result is always EPERM, Operation not permitted. A simple ""touch foo; ln foo bar"" on a shared folder will demonstrate the problem. This is with VirtualBox 2.2.4 on Mac OS X 10.4.11 host, Linux 64-bit client (tried both Ubuntu 8.04 LTS Server x86-64 and Scientific Linux 4.8 x86-64 (a RHEL4 variant)).

The way I actually noticed was that the zsh delivered with scientific linux (zsh 4.2.0) tries to create a history lock file with link() and fails - and goes into an infinite loop. There's no such problem with the ubuntu version though (zsh 4.3.4). This makes it rather more difficult to use zsh as a login shell :-) I'll see if I can coax it to not use that way of locking.

However, hard linking support would be nice.",lat
19529,[feature-request] Making linux setup of shared folder more user-friendly,all,VirtualBox 6.1.6,2020-04-26T08:14:30Z,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
18073,Regression: Tails shuts down after snapshot restore (on SATA optical drive),all,VirtualBox 5.2.20,2018-10-23T17:42:58Z,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
19091,Seamless Mode inactive with VMSVGA adapter,all,VirtualBox 6.0.14,2019-11-16T22:20:33Z,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
18411,ubuntu-bionic-server does not work with 'VBoxManage unattended install' because of preseeding post-install errors,all,VirtualBox 6.0.4,2019-02-05T09:16:36Z,2019-09-20T06:35:25Z,2019-09-20T06:35:25Z,"[attached script: reproduce-bug.sh] # 111 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

It was reported here (and includes this fix):[[BR]]
https://forums.virtualbox.org/viewtopic.php?f=8&t=86798[[BR]]
I'm WildSAR[[BR]]

This is a single line change in .../UnattendedTemplates/ubuntu_preseed.cfg which is consistent with debian_preseed.cfg in the same directory.

The text of the error is:[[BR]]
---[[BR]]
!! Finish the installation[[BR]]

Failed to run preseeded command[[BR]]
Execution of preseeded command ""cp /cdrom/vboxpostinstall.sh[[BR]]
/target/root/vboxpostinstall.sh && chmod +x /target /root/vboxpostinstall.sh && /bin/bash[[BR]]
/root/vboxpostinstall.sh --preseed-late-command"" failed with exit code 127.[[BR]]
---[[BR]]

This is the patch which fixes ubuntu_preseed.cfg:

{{{
<  && /bin/bash /root/vboxpostinstall.sh --preseed-late-command
---
>  && /bin/sh /target/root/vboxpostinstall.sh --need-target-bash --preseed-late-command
}}}
There are *three* bugs in this single line of code:

/bin/bash should be /bin/sh[[BR]]
/root/vboxpostinstall.sh should be /target/root/vboxpostinstall.sh[[BR]]
--need-target-bash is missing[[BR]]

The above solution is the same as in .../UnattendedTemplates/debian_preseed.cfg (a peer file of ubuntu_preseed.cfg).

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]",Robert Nielsen
18410,debian-stretch-netinst does not work with 'VBoxManage unattended install' because of incorrect install menu defaults,all,VirtualBox 6.0.4,2019-02-05T08:50:00Z,2019-09-17T19:52:27Z,2019-09-17T19:52:27Z,"[attached script: reproduce-bug.sh] # 88 lines[[BR]]
[attached patch: fix.patch] # 4 lines[[BR]]

The install menu defaults for the stock debian-stretch-netinst ISO is setup to be ""Graphical Install"" rather than just ""Install"".

The files in the ISO that control this are[[BR]]
/isolinux/menu.cfg[[BR]]
/isolinux/gtk.cfg[[BR]]
/isolinux/txt.cfg[[BR]]

VBoxManage already generates a replacement for one of the above files, but flattens its name to ${aux_base_path}isolinux-txt.cfg, so this file is patched after it was generated, but before it was used.[[BR]]
Specifically, this patch was applied after running 'VBoxManage unattended install ...' but before running 'VBoxManage startvm <vm>'.

This works only because the /isolinux/txt.cfg follows /isolinux/gtk.cfg (in /isolinux/menu.cfg) and thus can override its use of 'default label' and 'menu default'. But this order could change in the future so the ideal solution is below.

The ideal solution is[[BR]]
  - Remove 'default installgui' and 'menu default' (within 'label installgui') from /isolinux/gtk.cfg[[BR]]
  - Add 'default install' and 'menu default' (within 'label install') from /isolinux/txt.cfg[[BR]]

Currently, since there is no 'ui' directives used, the 'default installgui' and 'default install' are being ignored.[[BR]]
---[[BR]]
https://www.syslinux.org/wiki/index.php?title=Config

https://www.syslinux.org/wiki/index.php?title=Menu

The function that modifies /isolinux/txt.cfg is:[[BR]]
  src/VBox/Main/src-server/UnattendedInstaller.cpp:[[BR]]
  HRESULT UnattendedDebianInstaller::editDebianTxtCfg(GeneralTextScript *pEditor)[[BR]]

# to see the bug, do this[[BR]]
./reproduce-bug.sh[[BR]]

It will use the graphical installer, and thus mandates a manual install.[[BR]]

# to see my fix, do this[[BR]]
fix=1 ./reproduce-bug.sh[[BR]]
",Robert Nielsen
18694,"Add ""minimize"" command to VBoxControl",all,VirtualBox 6.0.8,2019-06-07T03:15:57Z,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
18194,netplan bond not working (ubuntu 18.04),all,VirtualBox 5.2.22,2018-12-18T10:10:24Z,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
18167,"Shared Folders: if disk removed from host, all disks don't auto-mount in guest",all,VirtualBox 5.2.22,2018-12-04T00:30:30Z,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
18015,A forwarded Dectel CI692 doesn't work if the controller is USB 2.0,all,VirtualBox 5.2.18,2018-09-27T14:30:26Z,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
17927,VBoxLinuxAdditions.run --target is dangerous if dir exists (possible data loss),all,VirtualBox 5.2.16,2018-08-14T12:30:53Z,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
17705,Question regarding status of upstream vboxguest module,all,VirtualBox 5.2.10,2018-04-22T20:21:31Z,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
16735,Issue with Linux guest 3D acceleration when logging in -> not likely to be fixed in near future,all,VirtualBox 5.1.22,2017-05-05T20:52:07Z,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
15149,"Files are not deleted when deleting many files, but VM thinks they are",all,VirtualBox 5.0.14,2016-02-14T14:11:57Z,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
17070,vboxvideo does not work with Xorg 1.19,all,VirtualBox 5.1.26,2017-09-10T13:18:10Z,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
17297,critical typo in documentation for installation of Linux Guest Additions,all,VirtualBox 5.1.30,2017-11-20T12:19:39Z,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
16809,PCI MMIO Address Not Listed In Memory Map,all,VirtualBox 5.1.22,2017-06-03T17:14:19Z,2017-06-13T08:01:10Z,2017-06-13T08:01:10Z,"When using the ICH9 chipset, the ""MCFG"" table is added to the ACPI table list, and it has an address of 0xDC000000.  However, this address is not included in the memory map returned by INT 15h AX=E820h.  This causes Linux to ignore the MMIO PCI area, altogether, and it may cause issues if the OS tries to use this area when reassigning addresses to PCI devices.

Please add the PCI MMIO area, and any other chipset specific memory areas to the memory map returned by E820.

Thanks.",SpyderTL
15112,Guest Additions autorun doesn't work with Mate Desktop (doesn't recognize mate-terminal),all,VirtualBox 5.0.14,2016-02-04T16:25:41Z,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
15885,Proposed Memory for openSUSE Linux installs is too small,all,VirtualBox 5.0.26,2016-09-05T01:55:28Z,2016-09-05T09:24:27Z,2016-09-05T09:24:27Z,"Current openSUSE Memory requirements are 1GB of ram while Virtual box currently proposes 768mb so this number should be increased. 

As openSUSE enables its own filesystem snapshots with btrfs users may also run into issues on the 8GB default hard drive size as well.",simotek
15422,New Linux kernel triggers udev hang,all,VirtualBox 5.0.20,2016-05-16T07:01:20Z,2016-05-20T03:32:02Z,2016-05-20T03:32:02Z,"Kernel: linux-image-4.5.0-0.bpo.1-686-pae

This is where it hangs:
http://s.natalian.org/2016-05-15/debug2.png

This is the strace screen capture:
http://s.natalian.org/2016-05-16/strace-usr-lib-systemd-systemd-udevd.png

Able to reproduce on Archlinux & Windows 10.",hendry
14474,start VBoxClient inside virtualbox guest only,all,VirtualBox 5.0.2,2015-08-19T10:44:18Z,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
14882,Windows not shown with Seamless mode if launched headless,all,VirtualBox 5.0.10,2015-12-01T19:49:18Z,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
14644,Feature request: Support self-adapting framebuffer console on GNU/Linux guest,all,VirtualBox 5.0.4,2015-09-29T11:40:05Z,2015-09-29T15:12:33Z,2015-09-29T15:12:33Z,"Currently on GNU/Linux guest vesafb will be used in the TTY console, AFAIK it is possible to manually set custom screen resolutions for VM to use but it will be better if there's a framebuffer driver that can self-adapt the size of the TTY console to the size of VM window(just as on X Window System)

Please consider it if it's possible, thanks in advance!

",林博仁(Buo-Ren Lin)
14331,PXE boot fails on NAT network,all,VirtualBox 5.0.0,2015-07-27T12:01:55Z,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
14061,VBoxManage CLI Support for configuring DNS server settings of the VirtualBox Host-Only Network adapters,all,VirtualBox 4.3.26,2015-04-20T16:47:10Z,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
13932,VBoxManage returns success even thow it failes,all,VirtualBox 4.3.24,2015-03-06T15:14:01Z,2015-03-11T13:38:58Z,2015-03-11T13:38:58Z,"vboxmanage metrics enable --list ""Android 5""
echo $?
0
vboxmanage --version
4.3.24r98716
",Kappen
13948,Host only interfaces in linux host are being deleted after system reboot.,all,VirtualBox 4.2.24,2015-03-10T06:52:39Z,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
10558,Console Mode Mouse Position not moving in Guest,all,VirtualBox 4.1.14,2012-05-12T22:12:06Z,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
