﻿ticket,summary,version,type,created,modified,_changetime,_description,_reporter
21418,general protection fault in VBoxRT.so on Linux 5.15,VirtualBox 6.1.40,defect,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
21347,VB systemd unit persistently rebuilding kernel modules with secureboot,VirtualBox-7.0.4,defect,2022-12-19T09:50:31Z,2023-01-19T01:49:28Z,2023-01-19T01:49:28Z,"In Debian, the kernel source script `extract-module-sig.pl` is not available in the kernel modules build/scripts directory. The VirtualBox systemd unit script relies on this script to determine whether the VB kernel modules are appropriately signed if it detects that secureboot is enabled. Since it can't find the script, it believes there is something wrong with the modules, and rebuilds them every time the service starts (at least on every boot), regardless of whether they were correctly signed. This means that every time I reboot my machine, VirtualBox refuses to operate until I go back and sign the newly-built kernel modules.

System: Debian Bullseye
VB installed with the deb distributed by the download.virtualbox.org repository.",lxop
21321,Compiling the kernel-modules fails with error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared,VirtualBox-7.0.4,defect,2022-11-30T11:30:21Z,2022-12-01T19:08:04Z,2022-12-01T19:08:04Z,"The compilation fails with:

vboxdrv/include/VBox/vmm/hm_vmx.h:532:29: error: ‘VMX_BF_EPT_PT_0_MASK’ undeclared here (not in a function); did you mean ‘VMX_BF_EPT_PT_READ_MASK’?
  532 | RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,

The line in hm_vmx.h which is causing this:

RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX,
                            (READ, WRITE, EXECUTE, MEMTYPE, IGNORE_PAT, IGN_7, ACCESSED, DIRTY, EXECUTE_USER, IGN_59_11,
                            SUPER_SHW_STACK, IGN_62_61, SUPPRESS_VE));

The cause is that the C preprocessor is replacing READ with '0' (and WRITE with '1') due to the linux kernel header file: tools/virtio/linux/kernel.h

which has (line 29):
/* generic data direction definitions */
#define READ                    0
#define WRITE                   1

I would say this is an unintended side effect and a small rename of the variables in hm_vmx.h would fix this

Apparently a workaround (https://bugs.gentoo.org/880229) is to set the Linux kernel config option CONFIG_JUMP_LABEL but I did not test this yet",gentoo-bird
21283,"Windows 11 VM freezes with Windows 11 Host, VirtualBox 7.0.4",VirtualBox-7.0.4,defect,2022-11-18T22:23:49Z,2023-02-13T18:04:08Z,2023-02-13T18:04:08Z,"I am running Windows 11 Pro 22621.819 with VirtualBox 7.0.4 and Hyper-V disabled. I was seeing the Windows 11 Guest VM freeze very quickly after boot, often within a few minutes. After the upgrade to 7.0.4 it still freezes, but after running for several hours. So it's better, but not fixed. This VM is a prebuilt developer image from Microsoft (WinDev2210Eval) with all Windows Updates applied to it.

",cmptrgk
21117,Windows 11 host machine's touchscreen stops working while running a Linux guest VM.,VirtualBox 6.1.38,defect,2022-10-02T19:05:07Z,2022-10-02T19:05:07Z,2022-10-02T19:05:07Z,"I have a HP Windows 11 ""All-in-One"" PC with a touchscreen. When I attempt to run Home Assistant in VirtualBox, the host's touchscreen stops responding, requiring the use of a mouse instead. Is there a fix for this?",WillD
20928,"Wrong IPC socket being deleted when VirtualBox is run via su on Linux, leading to possible disk corruption in VMs",VirtualBox 6.1.34,defect,2022-05-05T13:10:54Z,2022-05-05T13:10:54Z,2022-05-05T13:10:54Z,"This is related to ticket #17029 which has the same symptoms, but I'm not sure if it is caused by the same issue.

!VirtualBox, via src/VBox/Installer/linux/VBox.sh, checks for the presence of a VBoxSVC process owned by the current user and will delete a user-specific directory in /tmp if no process is found. But the process check uses the ""whoami"" command to get the current username and the deletion uses the environment variables $LOGNAME or $USER. Certain implementations of su, such as the one from util-linux, does not update $LOGNAME or $USER when switching to the root user, but whoami will return ""root"". Thus, if a user named ""vmuser"" runs !VirtualBox through su, it will search for processes owned by root but delete the socket belonging to vmuser.

The removal of these files will then lead to bad side effects for VMs that were previously running, as future calls to !VirtualBox will create a new IPC socket in /tmp. When using this new socket, all VMs will be shown as being powered off when they might still be running. It is also possible to start another instance of a running VM, which leads to disk corruption when both instances attempt to write to the same disk image.

Not all implementations of su seem to behave in this way, and using sudo or ""sudo su"" can sometimes cause $LOGNAME and $USER to be changed to ""root"", mitigating the issue. Using su by itself seems to have the highest chance of triggering this bug.

Replication steps:
1. Start any VM using ""{{{vboxmanage startvm <VM_NAME> --type headless}}}"" (take a snapshot beforehand in case of disk corruption).
2. Check that two files called ""ipcd"" and ""lock"" are present using ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"".
3. Try to start the same VM again, this should fail with a message that the VM is already locked by a session.
4. Switch to the root account using ""{{{su}}}"" and run ""{{{vboxmanage list vms}}}"".
5. Exit the root shell and run ""{{{ls -l /tmp/.vbox-$USER-ipc}}}"" again to see that the files from step !#2 are now missing.
6. Try to start the VM with the same command as in step !#1, this should now succeed.
7. Run ""{{{ps aux | grep -i vboxheadless}}}"" and see that there are now two processes started for the same VM.

The expected behavior would be that the files in /tmp/.vbox-$USER-ipc/ remain untouched and that step !#6 should refuse to start another VM instance.

While this issue only seems to occur when su does not update $LOGNAME and $USER, I'd argue that either whoami or $LOGNAME/$USER should be used instead of having a mix of both. While running !VirtualBox as root is not recommended, it would be nice if accidentally running ""{{{vboxmanage list vms}}}"" as root did not immediately break existing IPC sessions. I have attached a small patch to replace the use of whoami with $LOGNAME/$USER, and hereby make this modification available under the MIT license.

The !VirtualBox log files are unlikely to contain any relevant information about this bug since it occurs in the initial shell wrapper script, but I can attach them if needed. Here are the results of running the replication steps on an unpatched installation (tested on Ubuntu 22.04 using !VirtualBox 6.1.34):

{{{
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ls -l /tmp/.vbox-$USER-ipc
total 4
srwx------ 1 vmuser vmuser 0 May  5 11:21 ipcd
-rw------- 1 vmuser vmuser 6 May  5 11:21 lock
$ vboxmanage startvm test_VM --type headless
VBoxManage: error: The machine 'test_VM' is already locked by a session (or being locked or unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())"" at line 726 of file VBoxManageMisc.cpp
$ su
Password: 
# vboxmanage list vms
""<inaccessible>"" {7abbc342-2595-4b5d-b13b-4f57b7d4d367}
""<inaccessible>"" {26b6e251-e3c9-4004-a23e-30e5dd55f652}
""<inaccessible>"" {ed047e7d-83db-46b6-8d09-cd99f05f7362}
""<inaccessible>"" {2256db63-2e33-40fd-9182-7631a68a9e64}
""<inaccessible>"" {bf2390e8-3978-4363-9792-e370986ce5fc}
# exit
$ ls -l /tmp/.vbox-$USER-ipc
/usr/bin/ls: cannot access '/tmp/.vbox-vmuser-ipc': No such file or directory
$ vboxmanage startvm test_VM --type headless
Waiting for VM ""test_VM"" to power on...
VM ""test_VM"" has been successfully started.
$ ps aux | grep -i vboxheadless
vmuser     46799  2.2  0.6 1757468 431480 ?      Sl   11:38   0:01 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
vmuser     47353 59.8  0.2 1482004 157324 ?      Sl   11:39   0:03 /opt/VirtualBox/VBoxHeadless --comment test_VM --startvm a179e065-a0b4-4fc2-a55a-d59b599aad1e --vrde config
}}}
",Busan15
20822,Not able to import an OVA and converting the virtual disk to VDI,VirtualBox 6.1.32,defect,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
20818,Cannot build module virtualbox on Ubuntu server 20.04,VirtualBox 6.1.26,defect,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
20625,After hardware upgrade OS/2 does not boot,VirtualBox 6.1.26,defect,2021-10-22T05:44:13Z,2022-01-25T14:25:45Z,2022-01-25T14:25:45Z,"opensuse tumbleweed 20211012
linux v5.14.9-1-default x86_64
VBox v6.1.26_SUSE r145957

After an hardware upgrade the OS/2 guest has stopped booting. The boot proceeds normally to a point, then simply stops.

Old CPU: AMD Athlon II 4x
New CPU: AMD Ryzen 5 5600x

Mainboard
Old: asus m5a88-m
New: asus tuf gaming b550+
",James Moe
20618,VirtualBox installer on Windows 11: This app can't run on this device,VirtualBox 6.1.26,defect,2021-10-19T16:21:30Z,2021-10-19T16:21:30Z,2021-10-19T16:21:30Z,"Disabling core isolation memory integrity is not an option for me.

VMware Workstation Player is confirmed to be working on my device but I am in a position where I need to run a multitude of virtual machines at once.",fredd
20600,Fedora 35 compatibility / udev rules errors,VirtualBox 6.1.26,defect,2021-10-09T22:50:29Z,2022-10-21T12:53:24Z,2022-10-21T12:53:24Z,"There are some error messages which I guess should be fixed:


{{{
vboxdrv: /etc/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=""vboxdrv"".
vboxdrvu: /etc/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=""vboxdrvu"".
VBoxNetFlt: Successfully started.
VBoxNetAdp: Successfully started.
vboxnetctl: /etc/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=""vboxnetctl"".
}}}

I'm using VirtualBox-6.1-6.1.26_145957_fedora33-1.x86_64.rpm",Artem S. Tashkinov
20597,Running VBox in a VM that's running under VBox,VirtualBox 6.1.26,defect,2021-10-07T00:09:42Z,2021-10-07T07:49:40Z,2021-10-07T07:49:40Z,"Hi,

I have a VM that duplicates the Native Host I'm running; Fedora Core 36 (x86_64, Rawhide.

The only difference is that the VM has the ""latest"" kernel. My objective was to test that VB would support the new kernel.

I was playing with VB under VB and noticed several problems which make me ask if this config is supported.

1) The VM is x86_64 but NO x86_64 systems were listed in the first screen where the system name and system type are listed.

2) The create VM UI complained that acceleration is not supported but I didn't see any way to disable it.

3) The first level VM has only 2G allocated and the second level VM would only allow 2GB to be selected. I tried setting something else but the UI didn't want to forget my first selection.

4) The type of networking would only offer NATed networks.

Thanks,

Obiewan...
",George R. Goffe
20483,"Virtubox crashes when the vbox window was resized. Host Windows 10 Pro (64-bit), guest Debian GNU/Linux",VirtualBox 6.1.22,defect,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
20341,"HARDENING fails to verify DLLs on Windows for non-interactive, restricted user",VirtualBox 6.1.22,defect,2021-05-05T17:22:26Z,2021-05-06T07:26:09Z,2021-05-06T07:26:09Z,"== Background ==

I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

{{{
VBoxManage startvm ""[...]"" --type headless
}}}

== HARDENING prevents necessary functionality ==

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason is HARDENING, which simply refuses to load necessary and otherwise legitimate Windows-DLLs, resulting in errors like the following. Things heavily depend on the configured VM and the purpose of loading some DLLs, the following error is from a VM using bridged networking.

{{{
supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
NetworkAttachmentType_Bridged: Failed to get NetCfg, hrc=ERROR_TRUST_FAILURE 0x800706FE (0x800706fe)
AssertLogRel F:\tinderbox\win-6.1\src\VBox\Main\src-client\ConsoleImpl2.cpp(5376) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): !FAILED(hrc)
hrc=ERROR_TRUST_FAILURE 0x800706FE
Constructor failed with rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR pfnCFGMConstructor=00007ffc15bd1e60
VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(318) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400
Console: Machine state changed to 'PoweredOff'
Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005))
}}}

== HARDENING fails signature verification ==

While changing bridged networking to NAT makes the VM start, I simply have use cases which require a bridged network and one can't be sure anyway. The problem in all of those cases still is HARDENING not being able to verify some DLLs, which can be seen more detailed in the following logs:

{{{
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffc74d20000 'C:\windows\system32\rsaenh.dll'
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000808 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile -> -22900 (org 22900)
supHardenedWinVerifyImageByHandle: -> -22900 (\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll) WinVerifyTrust
Error (rc=0):
supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
Error (rc=0):
supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\System32\NetSetupShim.dll'
supR3HardenedDllNotificationCallback: Unload 00007ffc2aa90000 LB 0x000ef000 C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc77240000 LB 0x00052000 C:\windows\System32\SHLWAPI.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc15f60000 LB 0x003c0000 C:\Program Files\Oracle\VirtualBox\VBoxC.dll [flags=0x0]
Terminating the normal way: rcExit=0
supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1448 ms, the end);
supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1921 ms, the end);
}}}

The following is the relevant code:

{{{
/* Get the next match. */
HCATINFO hCatInfo = g_pfnCryptCATAdminEnumCatalogFromHash(hCatAdmin, abHash, cbHash, 0, &hCatInfoPrev);
if (!hCatInfo)
{
    if (!fFreshContext)
    {
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> %u; iCat=%#x)\n"", RtlGetLastWin32Error(), iCat));
        if (hCatInfoPrev != NULL)
            g_pfnCryptCATAdminReleaseCatalogContext(hCatAdmin, hCatInfoPrev, 0 /*dwFlags*/);
        g_pfnCryptCATAdminReleaseContext(hCatAdmin, 0 /*dwFlags*/);
        goto l_fresh_context;
    }
    ULONG ulErr = RtlGetLastWin32Error();
    fNoSignedCatalogFound = ulErr == ERROR_NOT_FOUND && fNoSignedCatalogFound != 0;
    if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (%u)\n"", ulErr));
    else if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed %u\n"", ulErr));
    break;
}
}}}

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/Support/win/SUPHardenedVerifyImage-win.cpp#L2703

== Comparing verification results ==

The following is how a successful verification of that same file looks like. Specially look at ""cbHash"" and ""wszDigest"", which seems to be the exact same values like for the first attempt in the former logs. So if this verification succeeds, the catalogs contain the necessary data and the state of the DLL is obviously OK.

{{{
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000930 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
}}}

The following lines are of additional interest because they seem to contain some error code of Windows:

{{{
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
}}}

Which might the following:

{{{
ERROR_SERVICE_NOT_ACTIVE
1062 (0x426)
The service has not been started.
}}}

https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1000-1299-

== dberr.txt ==

A corresponding error code is logged to the file ""C:\Windows\System32\catroot2\dberr.txt"" after adjusting its permissions to allow my executing restricted default user to write to it. For some reason this is not the default, but doesn't make any difference for signature checking itself. These lines repeat multiple times, most like for each attempt to check the signature for each DLL of interest.

{{{
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #352 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #590 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #2479 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #939 encountered error 0x00000426
}}}

== Educated guess: COM permissions problem again? ==

So here's what I think is going on: This signature verification relies on some COM-component again and default security settings of those only allow SYSTEM, ADMINISTRATORS and INTERACTIVE to activate those. I have documented that in the related ticket #20340 already. When using task scheduler with my restricted user it's no member of any of these groups, therefore necessary components are not activated and signature can't be checked. This changes instantly when using the same command line etc. with the same user with an interactive shell.

While that could be argued as a limitation of Windows default settings, the problem in my opinion in this case is that HARDENING is requiring that signature verification, not Windows, while without it things would simply work. So to make HARDENING succeed in this case, I would need to make my restricted user being a member of ADMINISTRATORS, which obviously doesn't make too much sense from a security perspective: Providing far more permissions than absolutely necessary to make an additional security(!) check succeed first. :-)

Like discussed in #20340, this might be worked around by creating an additional group and providing necessary permissions on the COM component of interest to that group. The problem is that I couldn't find the exact component yet... :-/

https://stackoverflow.com/questions/67331016/why-does-cryptcatadminenumcatalogfromhash-return-error-not-found-1062-for-n

https://docs.microsoft.com/en-us/answers/questions/378892/why-does-34cryptcatadminenumcatalogfromhash34-retu.html

Another workaround would be to make HARDENING optionally being disabled, it harms in this case, or at least make it more tolerant and ignore some of those errors under some circumstances. As said, the mentioned DLLs are all Windows default DLLs, unchanged, which otherwise easily pass signature verification.",Thorsten Schöning
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",VirtualBox 6.1.20,defect,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
20280,Memory Leak in vboxdrv,VirtualBox 6.1.18,defect,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
20240,Host Freeze Ubuntu 20.04,VirtualBox 6.1.16,defect,2021-03-08T09:47:09Z,2021-03-08T09:47:09Z,2021-03-08T09:47:09Z,"Sometimes i got a freeze of the Host (Ubuntu 20.04.1) after several guest are up. (kernel panic)

Host: Linux 5.8.0-44
Guests are all RHEL 7.8",Chris81
20238,VM Crashes at kernel loading on DELL Inspiron 7501,VirtualBox 6.1.18,defect,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
20146,"High CPU Kernel usage for any golang project, Windows 10 Host, Hyper-V turn on",VirtualBox 6.1.18,defect,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
20022,VM is causing Guest OS applications ( Slack/Intelli J ) hung,VirtualBox 6.1.16,defect,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
19912,Host gnome topleft hot-corner doesn't work when VM is running and focused.,VirtualBox 6.1.14,defect,2020-09-23T23:47:19Z,2020-09-23T23:47:19Z,2020-09-23T23:47:19Z,"I use Virtualbox 6.1.14 r140239 on Debian 10.5 with an Nvidia driver and an Nvidia proprietary driver.When I opened a Win10 VM and had it focused,I am unable to use the topleft hot-corner action of Gnome desktop. 
In gnome,when moving cursor to the topleft corner,it works as if you clicked the 'Activities' button on the topleft.While when focusing on a Virtualbox Win10 VM,moving cursor to the topleft corner doesn't cause any reactive.
This bug does not only exist on Debian,but also on Arch.
There is another spotter of this bug:
https://www.reddit.com/r/gnome/comments/dhqxbg/topleft_hotcorner_not_working_when_virtualbox/",TyamaAROU
19907,"Starting VM causes 100% load on one cpu in NT-Kernel, even after VM exit",VirtualBox 6.1.14,defect,2020-09-21T16:50:07Z,2020-11-03T21:15:43Z,2020-11-03T21:15:43Z,"Observe in Host task manager, that ""System"" process works normally. Everything idle.

Simply start some VM (tested Fedora 32 and Windows 10 1909 guest). Wait until its booted and logged in (Guest additions installed and loaded).

Observe in Host task manager, that ""System"" (ntoskrnl.exe) process fully loads 1 core. This is in addition to the VM process itself.

Shutdown VM.

High load can still be observed and is persistent until host is rebooted.

I tried to reproduce this with same VMs imported to another host, but failed. Seemingly its somehow connected to specific host configuration/hardware. host hardware also is relatively new.
However it is 100% reproducible on this host and always triggered by staring some VM.",theRman
19830,VB 6.1.12 Windows 10 host BSOD NDU.SYS,VirtualBox 6.1.10,defect,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
19786,VMs won't run after testbuild 6.1.13-139554: driver version mismatch kernel 5.7.12,VirtualBox 6.1.10,defect,2020-08-02T21:13:49Z,2020-08-02T21:13:49Z,2020-08-02T21:13:49Z,"All  builds from VB 6.1.12 through  test builds until 139554 work fine.  After 139554 VB test builds compile but VMs crash on startup with a kernel module message, give SVC log errors (no errs in the vmlogs).

Both 139683 and 139683 give the same errors.


VBoxSVC.log

00:00:05.638966 nspr-4   Support driver version mismatch: DriverVersion=0x2d0001 ClientVersion=0x2e0000 rc=VERR_VERSION_MISMATCH
00:00:06.113750 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'win7dpg' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0


I've tried removing and reinstalling the host modules,  building the VirtualBox...run, unloading and reloading the modules to no avail.

Not a big deal for me, but maybe important for developers to know (if not, my apologies).

Host: manjaro Linux updated daily, kernel 5.7.12 linux57-virtualbox-host-modules 6.1.12-4",matthewls
19752,Linux VMs are not running with MS Defender Application Guard,VirtualBox 6.1.10,defect,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
19727,Cannot connect to OCI Cloud: VERR_CR_KEY_UNSUPPORTED_CIPHER,VirtualBox 6.1.10,defect,2020-07-16T07:23:18Z,2020-07-16T07:23:18Z,2020-07-16T07:23:18Z,"VirtualBox running on CentOS Linux release 7.8.2003 (Core)
- Linux 3.10.0-1127.13.1.el7.x86_64

has problem opening the Key from profile because of unsupported cipher
(Works in Windows, exact same profile)

VBoxManage cloud --provider=OCI --profile=oci list instances
Parameter 'compartment' is empty or absent.
Trying to get the compartment from the passed cloud profile 'oci'
Found the compartment 'ocid1.compartment.oc1..xxxxxxxxxxxxxxxxxxxxx':
Reply is in the form 'instance name' = 'instance id'
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Failed to list instances
VBoxManage: error: Failed to read signing key from ""~/.oci/oci_api_key.pem"": VERR_CR_KEY_UNSUPPORTED_CIPHER
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component CloudClientWrap, interface ICloudClient
VBoxManage: error: Context: ""RTEXITCODE listCloudInstances(HandlerArg*, int, PCLOUDCOMMONOPT)"" at line 229 of file VBoxManageCloud.cpp",SpongeTort
19718,Failed to start VirtualBox hub service,VirtualBox 6.1.10,defect,2020-07-14T18:54:01Z,2020-07-15T06:54:19Z,2020-07-15T06:54:19Z,"I'm using VirtualBox 6.1.10_Ubuntu r138449 on Linux Mint MATE 19.3.
When starting Linux, I've got this error message : ""Failed to start VirtualBox hub service"".

I've got another message error when I type this command line :
$sudo dpkg-reconfigure virtualbox
See https://github.com/linuxmint/mintsystem/issues/121",InfoLibre
19690,Update for Microsoft Windows KB4560960 creates issues with VBox Guest,VirtualBox 6.1.10,defect,2020-06-30T06:23:03Z,2020-07-06T14:11:29Z,2020-07-06T14:11:29Z,"Host: Windows 10
Guest: Windows 7 

After installing recent windows update on host, VBox guests started malfunctioning and could boot.

We then troubleshooted the issue and found that one of the windows update is creating issue which we uninstalled and now guests working smoothly

Here is the update created the issue.
Update for Microsoft Windows KB4560960

I request to test and release the fix for the same.

Thank you
Harsh",hsparekh
19261,"Win10/64 on macOS: Display Driver, screen resolution & speed",VirtualBox 6.1.2,defect,2020-01-24T10:40:16Z,2020-01-24T10:40:16Z,2020-01-24T10:40:16Z,"running an iMac 2019 27'' with a Radeon Pro 570X, macOS Catalina. 
Issue with Oracle VirtualBox 6.1.2 and a Win10/64 guest system.

Here the screen resolution does not work properly, and speed to display and even show simple mouse movements is not good at all.
Windows 10 telling me, that is using the standard windows display driver. Tried using your radeon-software-adrenalin-2020-20.1.3-minimalsetup-200120_web.exe to resolve, however that does not detect any Radeon/AMD hardware.",Hofbor
19233,No recent-items jumplist on windows10,VirtualBox 6.1.2,enhancement,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
19105,Keyboard capture does not work properly under Wayland,VirtualBox 6.0.14,defect,2019-11-22T11:09:16Z,2019-11-23T01:23:30Z,2019-11-23T01:23:30Z,"I am using Virtualbox on Fedora under Wayland (Gnome/Mutter). It generally works correctly apart from being able to capture all keyboard presses.

Key combinations that have meaning to the OS (Alt+Tab, Cmd key, Alt+F4 etc.) are handled by the OS and don't make it to the VM. That '''was''' previously a known issue with Wayland, but has since been fixed by providing the appropriate extension. This has been implemented by Gnome and is in use by the Gnome Boxes app to provide correct keyboard behaviour.

See these two issues for some history and context:
https://bugzilla.redhat.com/show_bug.cgi?id=1285770
https://bugs.freedesktop.org/show_bug.cgi?id=97333

Implementing the same functionality for VirtualBox would greatly improve the usability on Wayland.",WillW
19011,Right screen buttons etc,VirtualBox 6.0.12,defect,2019-10-13T17:55:23Z,2019-10-21T06:09:10Z,2019-10-21T06:09:10Z,"Win 10 pro / Chrome / 
Right side - menu ellipses, x out and minimize/maximize, more than 5 tabs -cease working.
VB reinstall was a temporary fix
",Amadeo
18822,VMs with name lengths greater than 64 characters abort on start when using Pulseaudio. Have root cause and fix option <Regression>,VirtualBox 5.2.26,defect,2019-08-08T15:35:59Z,2019-08-08T15:35:59Z,2019-08-08T15:35:59Z,"If a VM has a name length greater than 64 characters, and is using Pulseaudio, it will abort on startup with ""VERR_CFGM_NOT_ENOUGH_SPACE"" being thrown.

The root cause is:
Inside ""src/VBox/Devices/Audio/DrvHostPulseAudio.cpp"", in ""struct DRVHOSTPULSEAUDIO"", there is ""char                  szStreamName[64];"".

This ""szStreamName"" only appears to be used by Pulseaudio for display purposes, such as when running ""pavucontrol"". The comments above ""szStreamName"" read:
     * The stream (base) name; needed for distinguishing
     *  streams in the PulseAudio mixer controls if multiple
     *  VMs are running at the same time. */

So, when ""int rc2 = CFGMR3QueryString(pCfg, ""StreamName"", pThis->szStreamName, sizeof(pThis->szStreamName));"" is called inside of the ""drvHostPulseAudioConstruct"" function in that file, ""CFGMR3QueryString"" throws the above error, as String.cb is greater than 64 characters.

I have a local patch which is a hacky solution and not good enough for you guys -- it checks if ""StreamName"" is passed in in each call to ""CFGMR3QueryString"", and then does the following if it is too long -- but I got it to work just fine by ellpisizing (""..."") at the middle of the string like so, creating a 64 character string like Pulseaudio requires, which shows up correctly in ""pavcontrol"":
     * First 30 chracters of the VM name
     * 3 chracters for ""...""
     * Last 30 chracters of the VM name
     * 1 byte for '\0'
This is 64 characters total. In my patch, I simply change the contents of String.psz and String.cb, which is probably not the correct way to do it.

I would strongly suggest ellipsizing in the middle like this, since the first 64 characters of multiple VM clones could easily be the same, usually the last few characters/words are what is different when there are many clones/different versions of a VM running.
Another option could be the number them, but ellipsizing is probably better for the user.

This limitation did not exist when using Ubuntu 18.04/16.04, so I have marked it as a regression. I looked at the latest 6.0 source code, and it looks like this bug will still be present there.

I have many VMs with long and descriptive names past 64 characters, and I know others do too, that is a very useful feature to tell them apart at a glance (especially when using many clones, where checking each description is not realistic).
Please fix this for us users who let our VM names get out of control! It really helps workflow to be able to use such long names.

Reproducible: Always",J_F
18771,vboxdrv.sh does not attempt to build modules on Fedora if Secure Boot is enabled,VirtualBox 6.0.10,defect,2019-07-18T14:28:35Z,2019-07-18T16:48:12Z,2019-07-18T16:48:12Z,"When running vboxdrv.sh with Secure Boot enabled it exits with the message ""You must sign these kernel modules before using VirtualBox..."" before checking if the modules have been built.",thomasfedb
18678,macOS app nap: effecting performance of VirtualBox VM,VirtualBox 6.0.8,defect,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
18574,Enhancement Dual Screen Single Click activation,VirtualBox 6.0.6,enhancement,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
18558,Shutdown gracefully upon Windows Update reboot,VirtualBox 5.2.26,enhancement,2019-04-11T15:10:48Z,2019-04-11T15:10:48Z,2019-04-11T15:10:48Z,"On Windows 8 and up, it's difficult (at best) for users to prevent Windows from automatically rebooting after some automatic updates have been installed.

Several times, I have had one of my guest OS's running, and lost whatever was going on there when the process was killed during an automatic reboot.

My suggestion is to have options upon reboot to allow...
-- preventing the reboot
-- save guest machine state and exit
-- shut down guest machine and exit
-- power off guest machine and exit
",adaptatron
18510,#GP when Windows guest driver tries to write X86_CR4_PCIDE in non-HyperV environment,VirtualBox 6.0.4,defect,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
18314,"6.0.2 RPM was built for fedora26, while 6.0.0 RPM was built for fedora29. Regression?",VirtualBox 6.0.2,defect,2019-01-16T06:50:53Z,2019-01-16T07:02:14Z,2019-01-16T07:02:14Z,"Summary says it all. 6.0.0 installed fine on Fedora 29, because the RPM had a requires for libvpx.so.5()(64bit) from libvpx-1.7.0.

6.0.2 doesn't upgrade on Fedora 29, because it has a requires for libvpx.so.4 from libvpx-1.6.* which is no longer present on 29.",Valdis Kletnieks
18304,VirtualBox 6.0 crashes on Ubuntu 18.10,VirtualBox 6.0.0,defect,2019-01-11T21:15:19Z,2019-01-12T21:05:58Z,2019-01-12T21:05:58Z,"VirtualBox 6.0 crashes immediately after launching on fresh Ubuntu 18.10 host (ASUS N551JW laptop)

{{{
$ virtualbox
Gdk-Message: 21:32:35.060: VirtualBox: Fatal IO error 2 (No such file or directory) on X server :0.

$ sudo virtualbox
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Qt WARNING: The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server "":0""
      after 612 requests (612 known processed) with 0 events remaining.
}}}

My installation process:

{{{
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
sudo add-apt-repository ""deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian $(lsb_release -cs) contrib""
sudo apt-get update
sudo apt-get install virtualbox-6.0 -y
}}}
",kipc
18261,"VM self-terminates during first boot after install (Virtualbox 6.0 MacOS Mojave 10.14.2 Host, Ubuntu 18.04.1 Guest)",VirtualBox 6.0.0,defect,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
18212,Windows 10 Host - Hardening error - VMs do not start,VirtualBox 6.0.0,defect,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
18030,EXC_BAD_ACCESS (SIGSEGV) on macOS 10.14 (Mojave) if trying to start Windows 10 Guest,VirtualBox 5.2.18,defect,2018-10-04T09:06:30Z,2020-02-05T02:46:25Z,2020-02-05T02:46:25Z,"Process:               VirtualBoxVM [748]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               5.2.18 (5.2.18)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [747]
Responsible:           VirtualBoxVM [748]
User ID:               501

Date/Time:             2018-10-04 10:52:39.613 +0200
OS Version:            Mac OS X 10.14 (18A391)
Report Version:        12
Bridge OS Version:     3.0 (16P375)
Anonymous UUID:        F0AE1762-A39B-8B31-FA72-EBFAC4B9E51B

Sleep/Wake UUID:       1526540A-27B6-482C-8AB3-864E562E4740

Time Awake Since Boot: 4400 seconds
Time Since Wake:       380 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000010
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [748]

VM Regions Near 0x10:
--> 
    __TEXT                 0000000103da3000-0000000103dc5000 [  136K] r-x/rwx SM=COW  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   VirtualBox.dylib              	0x00000001044383e4 0x104338000 + 1049572
1   VirtualBox.dylib              	0x000000010441c3b3 0x104338000 + 934835
2   VirtualBox.dylib              	0x000000010471b8dd 0x104338000 + 4077789
3   org.qt-project.QtCoreVBox     	0x0000000104f36808 QMetaObject::activate(QObject*, int, int, void**) + 3048",rharting
17903,Guru meditation (VERR_VMX_INVALID_GUEST_STATE) on any host with any guest.,VirtualBox 5.2.16,defect,2018-07-28T23:47:08Z,2018-07-29T05:15:35Z,2018-07-29T05:15:35Z,"I have tried numerous BIOS settings and software settings however whenever trying to run a guest on my system (Ubuntu 18.04) I receive (VERR_VMX_INVALID_GUEST_STATE) on both Ubuntu 18.04 and Windows 10 1803 hosts. You can see a list of what I have tried here https://forums.virtualbox.org/viewtopic.php?f=6&t=88833&p=426110#p426110

I have tried downgrading to 5.1.x but I receive hardening issues when doing so. 

Attached are the logs. ",Surgikill
17842,VirtualBox crashes while shutting down guest VM,VirtualBox 5.2.12,defect,2018-06-27T09:42:01Z,2019-07-24T00:11:16Z,2019-07-24T00:11:16Z,VirtualBox 5.2.12 crashes every time while shutting down any guest VM.,QA
17803,Virutalbox fails to install on MacOS 10.13.5,VirtualBox 5.2.12,defect,2018-06-05T16:45:46Z,2019-12-07T02:44:13Z,2019-12-07T02:44:13Z,"Virtualbox fails to install without any obvious explanation except this part of the logs:
{{{
error	18:32:10.563277 +0200	syspolicyd	Kernel Extension BLOCKED: <private>
default	18:32:10.563624 +0200	kextd	Kext rejected due to system policy: <OSKext 0x7f9b8a0dadb0 [0x7fffad793af0]> { URL = ""file:///Library/StagedExtensions/Library/Application%20Support/VirtualBox/VBoxDrv.kext/"", ID = ""org.virtualbox.kext.VBoxDrv"" }
default	18:32:10.563667 +0200	kextd	org.virtualbox.kext.VBoxDrv failed security checks; failing.
}}}
It was also tested with !VirtualBox-5.2.97-122902-OSX",jav
17730,Support PCI Passthrough for OSX Hosts,VirtualBox 5.2.10,enhancement,2018-05-04T12:18:05Z,2023-01-02T19:50:31Z,2023-01-02T19:50:31Z,"PCI Passthrough is supported on VirtualBox for Linux hosts, it also works with VMWare Fusion for OSX. Would be nice to see working on OSX hosts.",jimm
17710,"LsiLogic SCSI BIOS: int13_harddisk: function 02, error 04 ! or  int13_harddisk_ext: function 42, error 04 !",VirtualBox 5.1.22,defect,2018-04-24T13:19:49Z,2018-04-24T20:00:33Z,2018-04-24T20:00:33Z,"while starting winxp32/64 win764 guests(linux guests same controller work fine) using LsiLogic SCSI controller(also SAS) with ""Use Host I/O cache"" active, on debian 8 host i get very often these errors while hang

same guests same setup on win764 host work fine

win xp 32/64: VMMDev: Guest Log: BIOS: int13_harddisk: function 02, error 04 !
win764: VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 42, error 04 !

the bug doesnt appear if ""Use Host I/O cache"" is off
also no data corruption on guests

more detail: https://forums.virtualbox.org/viewtopic.php?f=7&t=87646&p=418668#p418668


'''my setup'''
vbox 5.1.22 r115126 (Qt5.3.2)
guest: Hdd controller LsiLogic SCSI
host: 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux Debian 8.10",justaquiz
17683,vboxdrv.sh: failed: modprobe vboxpci failed with linux 4.15 (centos7) -> fixed after (not in) 5.1.36,VirtualBox 5.1.34,defect,2018-04-13T10:06:03Z,2018-04-18T15:46:01Z,2018-04-18T15:46:01Z,"centos7  update kernel to 4.15.11 elrepo ,and vbox install have some problems with ""vboxpci: 

Unknown symbol vfs_write (err 0)""
{{{
uname -a
Linux crmdev205 4.15.11-1.el7.elrepo.x86_64 #1 SMP Mon Mar 19 11:46:06 EDT 2018 x86_64 x86_64 

x86_64 GNU/Linux


 ./VirtualBox-5.1.34-121010-Linux_amd64.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.1.34 r121010 (2018-02-26T15:29:57Z) installer
Removing previous installation of VirtualBox 5.1.32 r120294 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

[root@crmdev205 soft]# dmesg | tail -f 
[1746570.104013] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1746570.312366] VBoxNetFlt: Successfully started.
[1746570.318263] VBoxNetAdp: Successfully started.
[1746570.321467] vboxpci: Unknown symbol vfs_write (err 0)
[1747176.620175] vboxdrv: Found 32 processor cores
[1747176.635978] vboxdrv: TSC mode is Invariant, tentative frequency 1999998028 Hz
[1747176.635979] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000)
[1747176.840965] VBoxNetFlt: Successfully started.
[1747176.844354] VBoxNetAdp: Successfully started.
[1747176.846577] vboxpci: Unknown symbol vfs_write (err 0)
}}}",zw
17645,Host modules build without dkms patch,VirtualBox 5.2.6,defect,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
17621,USB and LAN error when re-connecting notebook to dock,VirtualBox 5.2.8,defect,2018-03-14T14:54:10Z,2018-06-12T06:55:04Z,2018-06-12T06:55:04Z,"Environment 1:
Hardware: Dell XPS 15 with Dell Dock TB16
Software: Oracle VirtualBox 5.2.6, then updated to 5.2.8 r121009 

Environment 2:
Hardware: Dell Precision 5520 with Dell Dock TB16
Software: Citrix Desktop Player 2.5.0.10 with integrated Oracle VirtualBox 5.1.25 r117057(Qt5.6.2)


Reproducible error:

After disconnecting and reconnecting the notebook to dock:
- LAN and USB devices connected to the dock do not work
- In device manager the device ""ASMedia USB Root Hub"" shows an error:
""Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)""


Workarounds to temporarily fix the issue:

Environment 1:
Close all open VirtualBox windows

Environment 2:
Disable:
- DesktopPlayer Service 
- Citrix DesktopPlayer Mped Service
- VirtualBox Host-Only Network (in network connections)
",ChrisSt
17620,VERR_VMX_NO_VMX,VirtualBox 5.2.6,defect,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
17593,Unable to Rename Screenshot - Keyboard Capture,VirtualBox 5.2.8,defect,2018-03-06T08:28:48Z,2018-03-06T11:43:58Z,2018-03-06T11:43:58Z,"When trying to do a Screenshot it is impossible to create a new named Folder, rename a Folder or rename the Screenshot File in the Popup Filerequester. This is due that the Mouse will be active in the Mac OS Popup but the Keyboard is still captured inside the VM and is not entering anything in the Filerequester. ",tops4u
17588,KB4056448 cause hardening error,VirtualBox 5.1.34,defect,2018-03-05T09:35:46Z,2018-03-20T21:08:14Z,2018-03-20T21:08:14Z,"KB4056448 on Windows Server 2008 x64 SP2 cause hardening error. Same with VBox 5.2.8.
",Victor Abramoff
17402,Unexpected input upon minimize/maximize host window,VirtualBox 5.2.4,defect,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
17358,Guru Meditation when starting Windows 10 VM on Linux after 5.2.2 upgrade,VirtualBox 5.2.0,defect,2017-12-08T12:16:48Z,2017-12-18T17:31:40Z,2017-12-18T17:31:40Z,"After the Upgrade from VirtualBox 5.2.0 to VirtualBox 5.2.2 the vm no longer starts, it fails with a guru meditation. 

Surprisingly only Windows 10 appears to be affected, any Linux, even ReactOS are working as expected.



The requested PNG file only shows a black screen, little helpful so i only attached the logfile. ",Jörg Skottke
17272,My Windows 10 crash when I try to start the install of a linux vm,VirtualBox 5.2.0,defect,2017-11-14T15:55:31Z,2017-11-22T15:48:05Z,2017-11-22T15:48:05Z,"My Windows 10 crash when I try to start the install of a linux vm. It works fine up until I hit start, I can load in the ISO file into storage but once i hit start windows crashes. I have tried the ISO for debian and ubuntu and it works fine with hyper V.",cgarry
17263,VirtualBox encounters an application error and aborts the guest,VirtualBox 5.1.28,defect,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
17229,Please add HP Sure Click as a hardening adversary.,VirtualBox 5.2.0,enhancement,2017-10-31T16:13:39Z,2017-10-31T18:47:23Z,2017-10-31T18:47:23Z,"Please see a forum discussion here: https://forums.virtualbox.org/viewtopic.php?f=6&t=85134.

A log is provided in the forum.

The user was having typical hardening problems, it looked like an AV conflict, but the ""adversaries"" list in VBoxHardening.log was empty. Plus the user said he normally uses Defender on his Win10 host, which we usually consider as not a problem.

Eventually, after tips on what kind of software to consider, the user discovered that removing ""HP Sure Click"" (a browser filter) fixed the problem.

I am drawing attention to the discussion in case you decide that ""HP Sure Click"" should be added to the adversaries that the hardening feature looks for. Had it been listed then we would have come to the correct diagnosis much faster.
",mpack
17224,VM crashes after input switch with KVM switch,VirtualBox 5.2.0,defect,2017-10-29T06:59:38Z,2017-12-06T23:49:33Z,2017-12-06T23:49:33Z,"Simiar to Ticker #8004, but on a Mac OS X host.

To reproduce: 
1. Start VM, wait until it starts an X server. Guest additions don't need to be installed. Make sure VM has captured the mouse.
2. Switch keyboard and mouse input to different computer with KVM switch (I'm using a SeaWit 4 port HDMI KVM switch).
3. Switch input back to VirtualBox host
4. Release the mouse from the VM and click another Window on the host to transfer focus.
5. VM aborts.

I tried to capture a core dump, but for some reason I didn't get one. I followed the instructions here exactly: https://www.virtualbox.org/wiki/Core_dump. The terminal showed ""Segmentation fault: 11"" when the VM aborted.

Host is Mac OS X 10.11.6
",Bernie S
17179,Extension pack upgrade failure (from within VirtualBOX offer to do so),VirtualBox 5.2.0,defect,2017-10-18T18:54:04Z,2017-10-18T18:54:04Z,2017-10-18T18:54:04Z,"Running VirtualBox 5.2.0 on a recent Windows 10 Pro :
   After upgrading the software from version 5.1.28 to 5.2.0 it offered to install new extension pack to match the upgrade.
   Agreed to do so -- it showed the window and appeared as if it was downloading the pack (I believe it did, but I do not know where).
   Then it proceeded to install and failed, saying something about wrong url.
   Then it offers to retry, but the result is the same dialog, where it ""swears"" the same, so I cancel it.
   
   Downloaded the extension pack from the website. Tried to install it -- VirtualBox said I need to log on as administrator :). 
  
   Logged on as administrator, started VirtualBox and received an offer to upgrade the Extension pack to 5.2.0 -- agreed, dowloaded, and same failure trying to install with seemingly unrelated ""wrong url"".
   Downloaded the pack from the website. Fired it to install (this time as Windows administrator) -- it succeeded.
   ",Kestutiss
17064,VM setting for all PC users,VirtualBox 5.0.24,enhancement,2017-09-08T13:00:02Z,2017-09-08T13:00:02Z,2017-09-08T13:00:02Z,"we have '''VM Dos''' running on '''host windows'''.[[BR]]

our case is we need all users loged in this pc have this VM with same setting without call our helpdesk to config it.",NorMal PC
17045,"""vboxmanage list hostinfo"" fails if CPUs have gaps in their processor IDs.",VirtualBox 5.1.26,defect,2017-08-30T15:21:53Z,2017-08-30T17:03:33Z,2017-08-30T17:03:33Z,"I have a server containing two Intel(R) Xeon(R) CPU X5675[1] @ 3.07GHz with 6 physical cores each and hyperthreading enabled, which results in 24 processors in total. Running ""vboxmanage list hostinfo"" results in the following shortened output:

{{{
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""GetProcessorDescription(i, processorDescription.asOutParam())"" at line 241 of file VBoxManageList.cpp
Host Information:

Host time: 2017-08-29T09:42:55.061000000Z
Processor online count: 24
Processor count: 24
Processor online core count: 12
Processor core count: 12
Processor supports HW virtualization: yes
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: yes
Processor#0 speed: 3066 MHz
Processor#0 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#1 speed: 3066 MHz
[...]
Processor#11 speed: 3066 MHz
Processor#11 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Processor#12 speed: unknown
Processor#12 description: 
Processor#13 speed: unknown
Processor#13 description: 
Processor#14 speed: unknown
Processor#14 description: 
Processor#15 speed: unknown
Processor#15 description: 
Processor#16 speed: 3066 MHz
Processor#16 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
[...]
Processor#23 speed: 3066 MHz
Processor#23 description: Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
Memory size: 145055 MByte
Memory available: 143530 MByte
Operating system: Linux
Operating system version: 4.10.0-33-generic
}}}

As you can see, while the overall number of processors is known, the command fails to retrieve the description of some of those. The reason is pretty simple: The implementation uses a loop to iterate all processor IDs and fails, because my IDs have gaps. Look at the following output of lscpu:

{{{
NUMA node0 CPU(s):     0,2,4,6,8,10,16,18,20,22,24,26
NUMA node1 CPU(s):     1,3,5,7,9,11,17,19,21,23,25,27
}}}

The following is the implementation of VBoxManageList.cpp:

{{{
static HRESULT listHostInfo(const ComPtr<IVirtualBox> pVirtualBox)
{
	[...]
	Bstr processorDescription;
	for (ULONG i = 0; i < processorCount; i++)
	{
		CHECK_ERROR(Host, GetProcessorSpeed(i, &processorSpeed));
		if (processorSpeed)
			RTPrintf(""Processor#%u speed: %lu MHz\n"", i, processorSpeed);
		else
			RTPrintf(""Processor#%u speed: unknown\n"", i);
		CHECK_ERROR(Host, GetProcessorDescription(i, processorDescription.asOutParam()));
		RTPrintf(""Processor#%u description: %ls\n"", i, processorDescription.raw());
	}
	[...]
}
}}}

12, 13, 14 and 15 are not used currently and I'm pretty sure that I don't have any influence on those IDs. Have double-checked the BIOS and from what I've researched on the topic on how those IDs are assigned, I have the feeling that this is really some attribute of the CPUs itself and only used by the Linux kernel, not assigned. So gaps in those IDs should be a valid use case:

> The x2APIC id space is not continuously mapped to logical processors however; there can be gaps in the mapping, meaning that some intermediate x2APIC ids don't necessarily correspond to any logical processor.

https://en.wikipedia.org/wiki/CPUID#EAX.3D4_and_EAX.3DBh:_Intel_thread.2Fcore_and_cache_topology

{{{
c->cpu_core_id = apic->phys_pkg_id(c->initial_apicid, index_msb) &
 				       ((1 << core_bits) - 1);
}}}


http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/kernel/cpu/common.c#L546

http://elixir.free-electrons.com/linux/v4.0.9/source/arch/x86/include/asm/processor.h#L114

With 8-core CPUs in mind, the gap of 2 per CPU might even make sense, because it's one additional core with hyperthreading, while the other core might simply be added at the end of the IDs.

So it seems using a loop might be a bit too naive and needs to be reworked to really use the available CPU IDs. I didn't came across any other errors like this one for now and hosting some VMs it looks like all CPUs are used by VirtualBox properly.

[1]: https://ark.intel.com/de/products/52577/Intel-Xeon-Processor-X5675-12M-Cache-3_06-GHz-6_40-GTs-Intel-QPI",Thorsten Schöning
16694,Host fails to resume from suspend when virtualbox installed,VirtualBox 5.1.18,defect,2017-04-25T07:35:52Z,2017-04-25T07:38:26Z,2017-04-25T07:38:26Z,"Since I installed virtualbox my laptop fails to suspend to RAM properly.

Looks like it suspends, but when I open the lid it just reboots.

Laptop is a Dell XPS 13 9350 Developer edition
OS: Ubuntu 16.10 / 17.04
Virtual box does not need to be running, just installed


Steps to reproduce:
- close lid and suspend to ram
- open lid and it will just restarts most of the time

From the logs:
Suspending:

Apr 21 16:55:24 XPS13 systemd[1]: Starting TLP suspend/resume...
Apr 21 16:55:24 XPS13 psensor.desktop[15786]: [2017-04-21T15:55:24] [ERR] lmsensor: Cannot get value of subfeature temp1_input: I/O error.
Apr 21 16:55:24 XPS13 systemd[1]: Started TLP suspend/resume.
Apr 21 16:55:24 XPS13 systemd[1]: Reached target Sleep.
Apr 21 16:55:24 XPS13 systemd[1]: Starting Suspend...
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Apr 21 16:55:24 XPS13 systemd-sleep[26265]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Apr 21 16:55:24 XPS13 systemd-sleep[26264]: Suspending system...
Suspend never finished

And it just reboots:
Apr 21 17:59:10 XPS13 rsyslogd: [origin software=""rsyslogd"" swVersion=""8.16.0"" x-pid=""902"" x-info=""http://www.rsyslog.com""] start

Let me know if more info is needed",silles
16590,extension pack breaks safari and unlock on Mac OSX,VirtualBox 5.1.18,defect,2017-03-21T13:30:21Z,2017-03-22T19:55:54Z,2017-03-22T19:55:54Z,"I installed the extension pack (latest downloaded from the website) and after that I had the following issues on my Mac host:
- Safari stopped working and could not be started again
- when screen was locked I could not unlock it anymore.  Only option was a reboot.

Removed extension pack and functionality is back to normal.",Dave Geysemans
16498,VBoxManage createrawvmdk doesn't work on 2016 MacBook Pro,VirtualBox 5.1.14,defect,2017-02-18T19:22:36Z,2017-04-28T12:07:56Z,2017-04-28T12:07:56Z,"I've had success with this tool on my previous laptops, but no luck on this computer. I'm running macOS Sierra 10.12.3. I've tried Virtual Box versions 5.1.14 and 4.3.40, both fail in the same way:
{{{
marcel@marcel $ sudo VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename win10raw.vmdk -partitions 1,4
VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
}}}

I've confirmed it's not a permissions or locking issue:
{{{
marcel@marcel $ dd if=/dev/disk0s1 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.006011 secs (170354 bytes/sec)

marcel@marcel $ dd if=/dev/disk0s4 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.005971 secs (171497 bytes/sec)

marcel@marcel $ dd if=/dev/disk0 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes transferred in 0.006038 secs (169587 bytes/sec)
}}}

SIP is disabled:
{{{
marcel@marcel $ csrutil status
System Integrity Protection status: disabled.
}}}

I can even confirm with dtruss that the tool is reading the disk just fine, but seems to fail to parse the partition map.
{{{
open(""/dev/disk0\0"", 0x0, 0x180)		 = 6 0
fcntl(0x6, 0x2, 0x1)		 = 0 0
fstat64(0x6, 0x7FFF5FBFE390, 0x1)		 = 0 0
ioctl(0x6, 0x40086419, 0x7FFF5FBFE530)		 = 0 0
ioctl(0x6, 0x40046418, 0x7FFF5FBFE55C)		 = 0 0
lseek(0x6, 0x0, 0x0)		 = 0 0
read(0x6, ""\0"", 0x200)		 = 512 0
lseek(0x6, 0x200, 0x0)		 = 512 0
read(0x6, ""\0"", 0x200)		 = 512 0
write_nocancel(0x2, ""VBoxManage\0"", 0xA)		 = 10 0
write_nocancel(0x2, "": \0"", 0x2)		 = 2 0
write_nocancel(0x2, ""error: \0"", 0x7)		 = 7 0
write_nocancel(0x2, ""Cannot read the partition information from '/dev/disk0'\0"", 0x37)		 = 55 0
}}}

My partition table is pretty standard:
{{{
marcel@marcel $ diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         2.0 TB     disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            1.9 TB     disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                117.8 GB   disk0s4
}}}

Any suggestions for next steps?",marcel.laverdet
16398,Boot up of Windows 7 VM running on Windows 10 post upgrade to v5.0.32 crashed,VirtualBox 5.0.32,defect,2017-01-17T19:46:10Z,2017-01-18T16:58:31Z,2017-01-18T16:58:31Z,"Windows 10 Host
Windows 7 Guest
vBox v5.0.32

Post upgrade to VirtualBox v5.0.32 the Windows 7 Guest crashed during boot up.
",n3kfh
16161,Opening a VBOX file from Win Explorer opens a 2nd instance of VirtualBox Manager,VirtualBox 5.1.8,defect,2016-11-06T16:56:24Z,2016-11-06T16:56:24Z,2016-11-06T16:56:24Z,"== NOTE: This affects BOTH Win & Linux Hosts ==
Launch !VirtualBox Manager. Double-click (or open) a VBOX file from Windows Explorer/File Manager.
* If the VM is already registered and not running, it will run. Good.
* If the VM is already registered and running, it will get the focus. Good.
* If the VM is not registered, a 2nd instance of !VirtualBox Manager opens up just to register the VM, which also appears on the 1st instance as well. __Not good__.
Especially on Windows, if you couple this, with #14988 it makes things not ... optimal.",Socratis
16151,[5.1.6 & 5.1.8] - Failed to open a session for the virtual machine,VirtualBox 5.1.8,defect,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
16130,VirtualBox Manager fonts+colors messed up on Linux host,VirtualBox 5.1.4,defect,2016-10-30T16:52:35Z,2018-03-16T18:35:45Z,2018-03-16T18:35:45Z,"At version 5.1-5.1.4, the UI in VirtualBox Manager seriously degraded in both text clarity and coloring.   At version 5.1-5.1.2, there were no issues but at 5.1-5.1.4 through -5.1.8, the problem is present.  All versions mentioned were tested on a fully updated CentOS 7 install.  Pictures attached of -5.1.2 vs -5.1.4
",ChrisE
16117,Kernel Panic on 10.10.1,VirtualBox 5.1.8,defect,2016-10-26T11:48:24Z,2016-10-28T06:03:57Z,2016-10-28T06:03:57Z,There is kernel panic when using virtualbox.,Majksner
16017,Only one CPU usable Windows 10 Hyper-V Bug,VirtualBox 5.1.6,defect,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
15977,Ubuntu 14.04 crash when open windows 7 guest machine,VirtualBox 5.1.6,defect,2016-09-23T09:05:36Z,2016-09-23T09:05:36Z,2016-09-23T09:05:36Z,"Hi everybody,
my ubuntu 14.04.1 with kernel 4.4.0-38-generic #57 crash when i try to open a windows 7 guest machine. i just installed gcc ver. 5.4.1 20160904
watch in other forum... but the problem persist.
New guest addition installed.

Guest machine was installed with VBox 4.xx, and ubuntu kernel 3.16.xx.

When host crash i can only move the mouse on desktop.
Ubuntu 14.04.1 with KDE  4.13.2

What do i do to resolve?

Sorry for my easy English.",zipp0
15919,No sound when VirtualBox is installed,VirtualBox 5.0.26,defect,2016-09-12T09:10:47Z,2016-09-12T09:42:50Z,2016-09-12T09:42:50Z,"The original report was filed here:
https://github.com/NixOS/nixpkgs/issues/15005

When VirtualBox is installed in NixOS, the kernel emits a backtrace which then results in the host not having any sound. So far it only seems to be happening on the Skylake architecture. We tried multiple Linux versions with always the same result.

None of us have kernel debugging experience, do you mind pointing us to the right direction?",zimbatm
15908,XBoxAutostart service starts and completes before NFS and iSCSI start,VirtualBox 5.1.4,defect,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
15900,Remote Desktop (RDP) into Windows10 (64-bit) Host Crashes Full Screen Guests 5.1.4,VirtualBox 5.1.4,defect,2016-09-07T15:48:55Z,2018-10-11T16:52:46Z,2018-10-11T16:52:46Z,"I've had multiple full-screen VMs crash twice now upon getting connected to my Windows 10 64-bit host via the standard Windows Remote Desktop client. The sequence of events scenario was similar both times: I'll typically leave a few guests running full-screen in the background, remote into the host while away, reconnect to the local host console upon returning, then remote in again next day. On the 1st remote connection, the full-screen guests that were left running flash the hosts Windows taskbar, and switching to them restores the full-screen display. Upon the 2nd or so remote connection, the full-screen guests that were left running again flash the host's Windows taskbar, and clicking then to switch to them causes them to crash with (latest example):

[Running] - Oracle VM VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x000000005B16C025 referenced memory at 0x000000000D41E000. The memory could not be read.

Host: Windows 10.0.10586 (64-bit), Dell Precision T5500 36GB RAM
Displays: (NVIDIA GeForce GTS 240)
Primary (Dell 2408WFP) 1920x1200
Extended (Samsung TV) 1920x1080
Guests (all configured for a single display):
Windows 10
Windows Vista (2 CPUs)
Windows XP
(not sure about Linux/Mint)

In all cases, the Remote Desktop client is set to start full-screen on 1 display. Not sure if this could be the reason or if it could be caused by the host having two different screens (speculation of course). However, simply connecting to a host should not crash guest VMs.
",CM7
15828,Desktop shortcuts (Alias) not working on OSX Host (10.9.5) after updating to 5.1.4.,VirtualBox 5.1.4,defect,2016-08-19T19:00:21Z,2016-09-15T09:22:47Z,2016-09-15T09:22:47Z,"I have two VMs (Win7 and WinXP) that I always start from shortcuts I have on my desktop (properly created from the ""Create Alias on Desktop"" - selected from the Machine Menu of the Virtualbox Manager). These shortcuts no longer work (either with or without Virtualbox running) after updating to 5.1.4.  Even deleted the existing shortcuts and recreated them using 5.1.4 without any luck.

No error messages are generated, the shortcut icons only blink when I double click on them and nothing else happens.

The VMs start o.k. from the Virtualbox Manager and function normally from that point.",Gregg Haines
15581,VirtualBox v5.0 fails on Linux v4.6 kernel host with floppy drive attached,VirtualBox 5.0.24,defect,2016-07-07T12:59:12Z,2016-09-15T07:58:08Z,2016-09-15T07:58:08Z,"When I start VirtualBox (currently v5.0.24) on a Linux v4.6 system running on a computer with a floppy drive fitted (yes, I know, it's becoming rare, but I need floppy for file exchanges with my old computers), VirtualBox fails to start Windows guests if the floppy drive is empty or contains a write-protected floppy disk.

Here are VirtualBox's reports:

1.- No floppy disk in drive:
{{{
The floppy controller cannot attach to the floppy drive (VERR_DEV_IO_ERROR).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}
and in /var/log/messages:

{{{
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0dbe020 VMMR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0071020 VBoxDDR0.r0
Jul  7 14:42:58 localhost klogd: vboxdrv: ffffffffa0002020 VBoxDD2R0.r0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
Jul  7 14:42:58 localhost klogd: blk_update_request: I/O error, dev fd0, sector 0
Jul  7 14:42:58 localhost klogd: floppy: error -5 while reading block 0
}}}


2.- Write-protected floppy disk in drive:

{{{
The floppy controller cannot attach to the floppy drive (VERR_WRITE_PROTECT).

Code d'erreur : 
NS_ERROR_FAILURE (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

I'm also attaching the log for a failed start of a Windows 7 guest session, with no floppy disk in drive.

This issue doesn't happen with older kernels (OK at least up to Linux kernel v4.1).",dinosaur0
15558,"VBoxDrvStub error: Unknown image file (NtCreateFile, Unknown Status - 5633)",VirtualBox 5.0.24,defect,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
15217,McAFee Agentblocks virtual machine running,VirtualBox 5.0.16,defect,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@…
15184,"""reopening"" 14286",VirtualBox 5.0.14,defect,2016-02-28T05:08:25Z,2016-02-29T08:09:37Z,2016-02-29T08:09:37Z,"Attempted to re-open 14286:  Allowed update, but could not change to open/reopened.

Here is my update to the closed/obsolete ticket:

I'm having this same problem. Just started after applying a kernel patch requiring a reboot. So, I tried to find updates/patches and ended up pulling down the latest RPM for SUSE 13.2 64bit.

Here is what I get when I attempt to fire up my W7 Home Premium under VBox (was a working image prior to the kernel patch).

Failed to open a session for the virtual machine W7 Home Premium.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

VBox 5.0.14 r105127 is what is shown with About VirtualBox

Let me know what more you want for diagnosing this.
",Wylbur
15141,Virtualbox and Avira,VirtualBox 5.0.14,defect,2016-02-11T08:37:47Z,2016-02-11T08:37:47Z,2016-02-11T08:37:47Z,"Hi,

I want to report a problem with antiviruses, especially with Avira (that is my case).

VirtualBox (5.0.14 but also previous versions) worked fine until I installed Avira on my host pc (Windows 7 Pro x64).
Then it started to slow down and show this error:

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap

The error appear also if the antivirus is disabled and creating exceptions in the real time protection doesn't work either.

If I uninstall Avira on my host pc, everything works fine again.
",Baboo85
15021,Pressure Sensitivity for USB Multitouch Tablet pointing device,VirtualBox 5.0.12,enhancement,2016-01-10T13:29:04Z,2016-01-10T13:29:04Z,2016-01-10T13:29:04Z,"I would like to run a Linux host on a Wacom Penabled TabletPC (Supporting both a pressure-sensitive pen and capacitive multitouch), and run windows-only, non-wine-compatible programs like Corel Painter in Virtualbox.

Unfortunately, it seems that neither option for emulating a USB tablet reports pressure data from the host tablet device. And, given the nature of the hardware (The digitizer is the primary input device for the whole machine, so the host must still be able to use it), USB passthrough is not an option.",MorningSong
14727,"With Windows 10 host, VirtualBox guest window jumps between monitors",VirtualBox 5.0.6,defect,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
14638,VT-x is not available Error while launching Android VM,VirtualBox 5.0.4,defect,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
14182,Host detects wrong number of cores (half of them),VirtualBox 4.3.28,defect,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
14178,Host Crash reproducible,VirtualBox 4.3.28,defect,2015-06-05T15:33:32Z,2015-06-08T12:40:51Z,2015-06-08T12:40:51Z,"Hi, i finally add it as a BUG here AFTER following all advices ( IRC, testing, reproducing failure, compaing results, check forums, etc. );

[ Sorry for sounding washy, im a bit tired now of all that crap, hopefully you are not and can take a deep look in it ]

Definition of the Bug as far as i can describe:

[HOST-SYSTEM]

[Soft-Ware:OS]

The Host Operating Systems i can reproduce these bugs on ( so far )are:

a) Windows NT 6.3.1 x86 U1 [ Windows 8.1 ( Embedded / Enterprise )Update 1 32-Bit ] NVHD

b) Windows NT 6.1.2 x86 [ Windows 7 ( Embedded Standard / Enterprise ) ] Service Pack 2 32-Bit ] NVHD

[Soft-Ware:VBOX]

VirtualBox 4.3.28 r100309 with ext-pack same version

[same effect/other symptoms in]

VirtualBox 4.3.29 r100811 with ext-pack from released version r100309 AND extpack for testing version [r100811]

HINT: Any version before is running ( not fine, but running )!


[Hard-Ware]

[A:AMD]
- Dell Optiplex 740
- CPU: AMD-Athlon X2 2.7GHz ( AMD-VX )
- NIC:
- onboard lan Marvell yukon GBit
- Wifi 54g D-link (PCI) originally; was exchanged with a firewire-pci
- 100mbit lan(pci with pxe-bios)

SND:
- onboard realtek ac 97

VGA:
- onboard nvidia ? ( unused)
- Ati v5700 Fire-GL (pci-express 16x)

HDD:
- 4x Seagate Barracuda ES 750GB 15k (non-raid use on onboard SATA AHCI )

ODD:
- external LG DVD+-RW whatever USB2
USB:
- 4 RootHubs ( 3 in use ) USB 2

[B:Intel]
- FS Esprimo

CPU:
- Pentium D 945 Presler ( VT-X)

HDD:
- 1x Samsung 160GB ( internal SATA AHCI )
- 1x IDE changeable rack
- 1x ide smart card/Compactflash-boot/SDHC/MS

VGA:
- Intel 945G (EE)

SND:
- onboard intel HD

ODD:
- none

HINT: These machines are in amounts up to 50 available, were in seldom use and bought from local energy provider as sorted-out and should be used in future for kindergarten-network as experimental stations; they are already checked and stress-tested and i interchanged systems with the given setup just to ensure it is not a single-machine that is faulty. Btw.: all these machines ran in energy efficient lowest modes all their lifetime just used for some bureaucracy, so even if cpu-ram-gpu-stresstest weren't reliable, they function normally in any other case ( before and after reproducing the given failure of vbox )


What is the problem ?


In my webchat IRC with MichalN in the #vbox channel i had kind brainstorm of possibilities, because i wouldn't report a bug without further investigations. Whatever, the problem to report a bug is, i can get NO MINIDUMP at all, independent of settings, because due to bugs in the given version, from a given OS in native VHD-Boot there are issues which in most cases, do not lead to a dump. believe me i tried all options. That is why i asked at vbox-channel for possible workarounds, like special logging-modes for vbox or possibilities to sandbox vbox, so the host-system can't crush and can be investigated. Nonen option so far given.

The problem in its symptomatic:

When running 64-Bit guests the host system crushes almost immediately!
Linux live systems run. ( at least in the release version ) in the testing-version they crush also immediately and with a bsod clock_watchdog_timeout for some millisecs of the host - followed by immediate restart and no dump at all ); at least in testing version vbox comes so far to log the usual vm-init inside. in the release version it never got so far.

Tested systems:
- 64-bit guest on 32-bit host is the problem;
- i counterchecked 32-bit ones also

- Fedora
- 17
- 19
- 21
( Workstation, Server, Live, DVD , CD, Netinstall )

- Ubuntu
- all LTS versions plus vivid (15.04) and winy (15.10)

- Windows
- any you can think of

- Debian
- Jessie ( 8 )
- Wheezy ( 7.1 and 7.6 )
- did i forget some, maybe ...

okay to get some more specific things:


side-problem NIC

as MichalN mentioned, due to change from wifi to onboard lan i checked that ones too, it makes a difference in time it takes until crash, but nevertheless changes nothing at all; so forget about it; right now in this moment i am running the stable-version 4.2.30 r100415 with winy werewolf (15.10) besides this ticket-creation without a problem with full install and stress-test inside 64 bit vm on the A-Host, the AMD-one, with all options given and any hardware acceleration and all hardware on the host enabled, soi can say -- It is NOT a HW-problem and not even a host-problem i would say.

I know it is problematic without a dump at all; however let me go on with that:

i tested any old version i could find in my libraries and which i regularly used on all my machines, especially on the given ones.
Btw. i just checked if it is dependent of the generation/featuresets by checking on m HP Elitebooks, too and on a panasonic toughbook; It is not; That ones were Core-duo Core2-Duo Turion X2 i5; Where was I, ah yes: Old versions

Old versions of VBOX tested so far:

- 3.2.8
- 4.0.8-71778
- 4.1.12
- 4.1.14-77440
- 4.1.22-80657
- 4.2.0-80737
- 4.2 ( 4.2.16 + 4.2.4[r81684] )
- 4.3 ( 4.3.6[r91406] + 4.3.8[92456] )
... these ones are counterchecked on linux hosts as well, which have not at all any problem with the 64guests on 32hosts (whereas the mentioned systems above that were used as guests i have also available as hosts )
plus the actual

release:

- 4.3.28-100309

testing:
- 4.3.29-100811

and the actual stable:

- 4.2.30-100415


Here is what i came to as a definitive reproducable point:

When using the actual release or testing:

-ONLY Linux-live systems based on debian run at all;
- UNTIL fully installed, the CRASH follows right after logging in the created user-account first-time.

- Windows-64-Guests ( Setup OR OVA OR prepared vhd's dism/firadisk/grub4dos) crash immediately.

- Linux-64-Guests crash right in the moment a user account is logged in in a graphical system

- Fedora-based linuxes are critically slow

- debian-based run acceptable up to perfect

- ovas with virtualization features in it are crushing in the same manner, comparable to Fedora 21 Workstation, which is the fastest crusher of all tested systems(IMMEDIATE-RIGHT-NOW-TOTAL-RESTART-OF-HOST)

Okay that was long enough - i am tired and have no concentration anymore, please see this as a possibility to make something of it; i am available for further test-scenarios, BUT DO NOT FORGET: the given HOST-OSs can not produce a dump.

I saved the chat-log of my chat with MichalN if it helps and am willed to help out. added also 2 screenshots just for a prove of stable is running ubuntu winy and a short device overview.

Give me reproducable test-case and i follow to my best; If necessary i can make a video of the crash and the none existance of the dump if you wish to. In case you do not believe.
I have visual studio available if it helps and am able to install a set of progs to help narrow the problem, because these ones are not really production systems at the moment. Only thing is you have to explain what it is for if i dont know and i might double check for resulting contents, because i run some more networks chained where these machines are appended to.

To be precise: i am willed to spend my time to check on the HOST-A ( the AMD ) as the Intel-Machines go out for setup and deliverance for a while for other projects.

The other systems are my personal ones and i am not willed to make crucial tests on them anymore as long as crazy shutdowns are not handled.

So whatever: I hope you have an idea of an idea of an idea of what might could eventually maybe happen here and feel able to give some straight questions.

Thanks for your interest.

PAETH CLAUDIUSRAPHAEL
S466531257BOSS

P.s.:

By the way, if you think that it is not necessary to give compatibility to these OLD machines then i need you to tell that clearly and unmisleading and ALSO clarify the tech-specs of your products for the given case. If instead you accept that these kind of machines are right now even in industry-leading nations like germany still in use by MANY private AND business users and organizations, especially those who teach and take care of our children then PLEASE do me and maybe others the chance to make it usable. Your decision. I just ask to be precise about this issue.",PAETH CLAUDIUSRAPHAEL
14072,Win 8 host.  Cannot change Linux guest priority using Windows taskmgr.exe,VirtualBox 4.3.26,defect,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
14042,VBoxNetFlt crashing windows 7 on resume,VirtualBox 4.3.26,defect,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
13953,WinXP guest machines do not start after the update to version 4.3.24 & host system reboott,VirtualBox 4.3.24,defect,2015-03-13T20:58:08Z,2015-03-22T12:52:20Z,2015-03-22T12:52:20Z,"After the update to version 4.3.24 from 4.2.18 I was able to run a win XP guest machine but after the host (Win 7 Home Premium x64, AMD, Acer Aspire) reboot it has been possible no longer. I tried to turn off PC Tools 7 firewall, antivirus AVG 2015 and Iobit Advanced Care 8.1 but without a success. I am enclosing screenshots and the VM guest machine logs. Could you look at the issue?

The error messages are:
""Error relaunching VirtualBox VM process: 5
Command line: '...--starttvm...--no-starttvm-errormsgbox...""

""The virtual machine '...' has terminated unexpectedly during startup with exit code 1(0x1)...
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {...}""
",Kola Wisarionowicz
13676,Guest windows is squeezed to small size if user32.dll has been altered on a host,VirtualBox 4.3.20,defect,2014-12-07T22:22:47Z,2015-04-18T09:30:31Z,2015-04-18T09:30:31Z,"If user32.dll has been altered on a host (some software installation) and is not signed anymore, since 4.3.16 (or 4.3.14) all guests start with a window squeezed to a smallest possible size. VMs start and run normally, just the window always auto-resize to a smallest size. Not happening with 4.3.12 version.

related error in the logs:
00:00:01.122572 supR3HardenedErrorV: supR3HardenedScreenImage/Imports: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=32 \Device\HarddiskVolume7\Windows\System32\user32.dll

discussion on the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",wroot
13659,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it",VirtualBox 4.3.20,defect,2014-11-29T15:14:44Z,2019-12-07T17:39:42Z,2019-12-07T17:39:42Z,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it.

VirtualBox since 4.3.14 (all builds, including 4.3.20/4.3.21 - the most updated) are incompatible with Outpost Firewall Pro v6.7.x and others, that used ""WL_HOOK.DLL"" module to inject to all processes to get some information in RING3 (usermode).

WL_HOOK.DLL is digitally signed (!) (I can attach this file, if needed), and must be allowed even by hardened rules. But VirtualBox incorrectly recognize a path to it. There is a bug in VirtualBox getting/parsing path information in some cases of modules inject or other (probably, is because of special inject technics, that used). Please see a VBoxStartup.log:

{{{
...
e4.11ec: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\WINDOWS\system32\imm32.dll [lacks WinVerifyTrust]
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=76290000 'E:\WINDOWS\system32\IMM32.DLL'
e4.11ec: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║)
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║: None of the 1 path(s) have a trust anchor.: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║
e4.11ec: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedMonitor_LdrLoadDll: rejecting 'e:\progra~1\outpos~1\wl_hook.dll': rcNt=0xc0000190
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'e:\progra~1\outpos~1\wl_hook.dll'
...
}}}

Please see a lot of garbage (binary garbage like ""ц╜ОцХоц╝атБжцб┤тБетА▒цЕ░ц"" and so on) after ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall"" string, instead of normal dll name path.

The real path to wl_hook.dll is E:\Program Files\Outpost Firewall Pro\wl_hook.dll

So it must be like: ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall\wl_hook.dll""

But you had incorrectly get/parsed data. It seems like buffer contain a garbarge or like string's ending-zero is missed or something, so you are reading garbage memory.

After you are got that garbarge-containing-path you a providing it to a system function WinVerifyTrust to check digital signature of this ""file"". But path is invalid (garbaged/damaged), so Windows function cannot find the file and check digital signature and returns an error.

After getting this error, you are REJECTING to load this .dll.

And after that, we have a problems to use VM. Because Outpost Firewall cannot read information about process without this R3-dll injected to VM's process, so it can't get correct ProcessName and can't allow/create_rule to any network or other activity from VM, so it is UNUSABLE.

Please fix path retreiving/parsing or this inject method allowing and allow WL_HOOK.DLL (digitally signed) to inject to your process.",John Dan
13263,RTPathUserHome lookup fails when using API in a windows service,VirtualBox 4.3.14,defect,2014-08-06T11:16:18Z,2014-08-06T11:16:18Z,2014-08-06T11:16:18Z,"RTPathUserHome uses environment variables to determine the user home directory. When accessing the API from a windows service the lookup for the user home directory fails.

Probably a solution would be to use SHGetFolderPathW for the lookup.

http://stackoverflow.com/questions/9542611/how-to-get-the-current-users-home-directory-in-windows",hakito
12669,Mac OSX  VBoxManage: error: Cannot read the partition information from '/dev/disk0',VirtualBox 4.3.6,defect,2014-02-04T06:09:41Z,2014-02-06T03:58:51Z,2014-02-06T03:58:51Z,"I am trying to get !VirtualBox to boot up my Bootcamp Partition. Does anyone know why I'm getting the error ""VBoxManage: error: Cannot read the partition information from '/dev/disk0'""?

What I typed into terminal
{{{
WinXPmbp manila$ chmod 777 /dev/disk0 /dev/disk0s4
WinXPmbp manila$ sudo VBoxManage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename ""/Users/home/VirtualBox/WinXPMBP/bootcamp.vmdk"" -partitions 4
Password:
VBoxManage: error: Cannot read the partition information from '/dev/disk0'
VBoxManage: error: The raw disk vmdk file was not created
}}}",DonyorM
12168,Oracle Virtualbox manager has stopped working,VirtualBox 4.2.18,defect,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
11476,build time dependences not documentend in debian control file,VirtualBox 4.2.6,enhancement,2013-02-09T05:09:56Z,2013-02-09T05:11:26Z,2013-02-09T05:11:26Z,"building from a svn copy (4.2.51~svn-1) in a debian wheezy with vanilla 3.6.7 stable kernel.

packages that are needed to build virtualbox but are not indicated at build environment check time, so dpkg-buildpackage does not complain while they are not installed and build ends up failing later:

libdevmapper-dev
makeself 

also, linux-headers-generic is obsoleted and uninstallable in wheezy so I have benn forced to build vbox with 
dpkg-buildpakage -d",AlejandroAmo
10534,"Virtualbox overrides umask, making it unusable for shared setup",VirtualBox 4.1.14,defect,2012-05-09T04:40:53Z,2019-03-13T11:08:00Z,2019-03-13T11:08:00Z,"I want to setup Virtualbox to use a common directory to be used by any user who sits at the console (using VBOX_USER_HOME and the machinefolder property). Problem: The VirtualBox tools (GUI or command line) ignore umask and use 0600 instead. The next user runs into ""permission denied"" problems.

This makes it impossible for us to deploy VirtualBox as a replacement for VMware.
",Harri
8960,Virtualbox Unity Launcher Integration,VirtualBox 4.0.4,enhancement,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
8324,Windows Host shutdown -any guests running stop windows from shuting down correctly,VirtualBox 4.0.2,enhancement,2011-02-11T11:29:53Z,2017-09-13T19:46:44Z,2017-09-13T19:46:44Z,"Is there a way to improve the shutdown of guests on a windows host which is performing a shutdown / reboot.

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

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

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

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


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

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

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

many thanks",Jimbo
7891,VBox doens't handle the user account correctly on Windows Hosts,VirtualBox 3.2.12,defect,2010-12-23T10:37:26Z,2012-01-10T23:47:17Z,2012-01-10T23:47:17Z,"Host : Windows 7 Pro 64 bits

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

I wrote a little PowerShell script to illustrate the defect:

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

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

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

To me, this is the CORRECT result.

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

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

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

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

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

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

Thanks.",Romuald Tisserand
4949,Need to be able to re-assign keys for Mac,VirtualBox 3.0.6,enhancement,2009-09-10T23:49:05Z,2010-01-14T09:12:25Z,2010-01-14T09:12:25Z,"The main modifier key on Mac is the ""Command"" button - not the ""Control"" button which is used on Windows. It would be really useful to be able to map the Command button to Control inside VirtualBox. This is what you can do in Parallels and it's a very handy feature.

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

Many thanks for a fantastic product,

Simon",Simon Wade
3045,Feature Request: Control HOST os resolution in fullscreen mode (for res switching),VirtualBox 2.1.0,enhancement,2009-01-15T12:05:14Z,2009-10-29T19:35:02Z,2009-10-29T19:35:02Z,"Id like to see a feature that allows virtual box to control the physical monitor on resolution switching 

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

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

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

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

",hyakki
