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

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

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

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

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

",xwisdom
2120,Exposé shortcuts don't work,VirtualBox 2.0.0,defect,2008-09-06T09:08:21Z,2011-01-09T16:39:25Z,2011-01-09T16:39:25Z,On OS X 10.5.4 (locale FR-fr) the Exposé shortcuts (screen edges) are not aviable when the focus is on a VirtualBox window.,Simon Delalay
3010,VM control on powerdown/reboot,VirtualBox 2.0.4,enhancement,2009-01-11T06:41:34Z,2009-01-11T06:41:34Z,2009-01-11T06:41:34Z,"It would be nice to control what the VM does when it tries to powerdown/reboot, similar to the control you get when using qemu.

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

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

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

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


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

",andrew.sharpe.7.9
3064,Wanted pre-start post-stop scripts,VirtualBox 2.1.0,enhancement,2009-01-16T22:17:29Z,2009-05-30T19:53:15Z,2009-05-30T19:53:15Z,"It would be very nice to be able to add a script/program so its run before resp after the vm.

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

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

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

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

As far as I can see there are three possible approaches to remove this product vulnerability:
 * '''Renormalise the data models'''.  For example the ''<!MediaRegistry><!HardDisks>'' tree would only contain HDs that are not allocated to VMs.  The complete set of ''<!HardDisks>'' could be obtained by enumerating this tree plus the ''<!HardDisks>'' in each attached machine.  (This node would replace the existing ''<!HardDiskAttachments>'' node).  Such an approach would also mean that a VM is now a self-contained entity that can be exported or imported (a frequent user request).  Yes this would require addition integrity checks to walk the VMs XML files when adding or removing HDs, but this is hardly a frequent occurrence.  This is my recommended option.
 * '''Provide a repair too'''.  This would walk the various XML files, identify inconsistencies and have a set of rules for when to recommend recovery and when to ask the user for a choice.
 * '''Move the meta data to a proper DB'''.  The obvious one to use here is SQLlite: simple, free, and able to handle the transactional issues.  Under this scenario the Machine schema would only be used for importing and exporting machines.
This metadata is critical to the protecting the user content maintained within the various VMs, yet there are no transactional, journalling or recovery mechanisms provided to ensure the integrity of this metadata.  This is unacceptable in product of VBox's maturity.",Terry Ellison
3500,Auto startup and shutdown for VMs,VirtualBox 2.1.4,enhancement,2009-03-05T10:24:05Z,2017-09-19T08:32:39Z,2017-09-19T08:32:39Z,"It would be good to have an option to allow (headless ?) VMs to be started automatically on host boot and gracefully shut down when the host shuts down. I know that scripts exist, but configuring this in an easy and uncomplicated way via the GUI would be a great enhancement.",mark_orion
5594,Keyboard mapping problems using SSH tunneling,VirtualBox 3.0.12,defect,2009-11-30T02:42:13Z,2009-12-01T09:13:33Z,2009-12-01T09:13:33Z,"While using OpenSSH 5.3 to SSH into my Debian 5.3 GNU/Linux and Ubuntu 9.10, I encounter keyboard mapping problems whenever I run X11 applications from the SSH terminal. When I type into any X11 program (such as leafpad, xterm, etc.), the keyboard output is completely jumbled. When I type ""QWERTY"", I get ""-=[reverse tab][forward tab]w"", also caps lock acts as a space and the back space as a comma. 

I'm running all this on Mac OS X Snow Leopard (v 10.6.2)",sm_news
5683,Configurable actions on signals,VirtualBox 3.1.0,enhancement,2009-12-07T08:53:17Z,2015-02-16T05:00:21Z,2015-02-16T05:00:21Z,"Please see my last post in this thread for background:

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

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

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

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

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

I'm more than happy to help out with testing under 10.5/10.6 on my lab machines.  Thanks!
",ae3265
6510,Timed Default Option When Close Is Detected,VirtualBox 3.1.6,enhancement,2010-04-08T17:18:59Z,2014-01-02T22:22:20Z,2014-01-02T22:22:20Z,"Currently, when VirtualBox detects a close request (i.e. the system sends one or the the clicks on the close button) it brings up the Close Virtual Machine dialog box and waits for a response.  It would be useful to have the ability to select one of the three options as a timed default.  IOW, if the user didn't respond within n seconds VirtualBox would execute the default selection.

This would provide a way to gracefully close a VM when the host initiated a logoff or a shutdown while the user was not at the machine.
",Stewart Berman
6957,More network adapters in VirtualBox,VirtualBox 3.2.4,defect,2010-06-10T12:47:49Z,2011-10-26T15:11:53Z,2011-10-26T15:11:53Z,"In VboxManage maximum is 8 network adapters, but in VirtualBox Gui only 4.
I make a simple patch to fix this, but only for OSE edition.
Please use it in feature release of closed source edition.
It's very usable function for testing in virtual environment.",eugene
7036,"""Check for update"" turned on, automatic vm start, when update available, access blocked",VirtualBox 3.2.2,defect,2010-06-21T15:10:59Z,2010-10-17T23:27:46Z,2010-10-17T23:27:46Z,"Hi,

a very strange ""error"". Situation: 

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

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

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

",vlatko
7419,SSH tunnel headless mode,VirtualBox 3.1.8,enhancement,2010-09-02T19:54:43Z,2010-09-04T08:27:30Z,2010-09-04T08:27:30Z,"Emulation of a Headless Virtual Machine through Supression of any standard Drawn Display, where I would perform all operations through an ssh tunnel.",shiny
7461,Cannot delete old and unused VM snapshot.,VirtualBox 3.2.8,defect,2010-09-11T20:30:53Z,2016-01-27T20:27:06Z,2016-01-27T20:27:06Z,"Hi all.

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

I'm getting:

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

Details:


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

}}}

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

Regards,

-- Shlomi Fish",Shlomi Fish
8011,VBoxManage/GUI does not detect VMs started by another user,VirtualBox 4.0.0,defect,2011-01-05T17:02:28Z,2011-01-06T15:58:46Z,2011-01-06T15:58:46Z,"If a VM is started by the Windows Local System account (for example, if started by ""VBoxVMService""), then neither VBoxManage nor the GUI when executed by a regular user or administrator will show the VM as running. The status of a VM should be machine global and visible to all users.
",DavidN
9087,"Linux: Please optimize output of VBoxHeadless in ""top""",VirtualBox 4.0.8,enhancement,2011-06-17T21:05:07Z,2011-06-17T21:05:07Z,2011-06-17T21:05:07Z,"On a Linux host the ""top"" program is a great tool to see how many resources (memory, CPU usage,...) are used by various Linux processes[[BR]]
But when running multiple headless virtual machines on one physical server it's not possible to see which virtual machine is using how many resources. Instead every virtual machine process is  visible as ""VBoxHeadless"" process (which is of course in principle correct).[[BR]]

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

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

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

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

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



",Helge Deller
9223,A running VM is listed as Powered Off,VirtualBox 4.0.10,defect,2011-07-18T10:23:36Z,2020-12-09T21:30:58Z,2020-12-09T21:30:58Z,"I have a VM that has been running for 11 days, but VBoxManage showvminfo and the VirtualBox Manager window both report that is it powered off.

The machine is working perfectly AFAICT (its console is alive and processes are running in it).

# ps -wwo lstart,command 6686
                 STARTED COMMAND
Wed Jul  6 12:45:57 2011 /usr/lib/virtualbox/VirtualBox --comment barker --startvm 91b05e8b-b485-49cb-849c-eb5dfed6dcf6 --no-startvm-errormsgbox

# VBoxManage showvminfo barker | grep State
State:           powered off (since 2011-07-06T10:44:00.000000000)

The log contains thousands of messages like this:

199:10:30.740 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Failed to query the session machine (NS_ERROR_CALL_FAILED)}, preserve=false
",mlw
10092,Error message when using a normal command which should not give this message,VirtualBox 4.1.8,defect,2011-12-27T12:27:01Z,2015-05-29T16:01:19Z,2015-05-29T16:01:19Z,"After giving the command (as root):
{{{
su - vboxuser -c ""/usr/bin/VBoxManage controlvm ""vmname"" acpipowerbutton""
}}}
the following command is given in a loop each second
{{{
su - vboxuser -c ""/usr/bin/VBoxManage -nologo showvminfo ""vmname"" -machinereadable"" | grep -q 'VMState=""poweroff""'
}}}
until this command returns 0 and the loop is ended.
Apparently at the moment the command returns VMState=""poweroff"" the command VBoxManage also gives the following error message:
{{{
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee nsISupports
Context: ""COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))"" at line 1698 of file VBoxManageInfo.cpp
}}}",Freek de Kruijf
10222,Please implement readPhysicalMemory or a raw memory dumper,VirtualBox 4.1.8,enhancement,2012-02-07T01:46:11Z,2012-02-22T12:45:28Z,2012-02-22T12:45:28Z,"Hello,

We are studying the use of VBox in a forensic course. However, the access to VM memory is critical.

I found many references at the forum about people trying to get the VM memory contents. However, no one provided a solution. I still can get the memory, treating it as a real machine, but that would taint the VM memory with the memory dumper. The best solution would be to collect the VM memory using the VM solution resources, specially in a paused state. The best solution would be to have a simple read function that could access a Snapshot.

The VBOX SDK guide describes the function readPhysicalMemory and notes that it is not developed in 4.0.0. We are already in 4.1.8 and it is still not imeplemented. I got this error message when running a python script that calls this function:

 0x80004001 (Method ReadPhysicalMemory is not implemented)

Please, could you please provide the implementation of this function in the next vbox release. Alternatively, this could be implemented in a VBoxManage debugvm option, specially if considering snapshots. The needed function is a raw VM memory dump.

Vmware Server/Workstation, for example, stores the memory in a flat vmem file. Libvirt has the virDomainMemoryPeek API function. Just Vbox lacks at this point.

Thanks,",Luiz Angelo Daros de Luca
10252,Switch to fullscreen with VBoxManage,VirtualBox 4.1.8,enhancement,2012-02-14T16:52:49Z,2012-02-14T16:52:49Z,2012-02-14T16:52:49Z,"It would be of great value to us to be able to use VBoxManage controlvm to switch the VM window between the different display modes, such as scale, fullscreen and so on via VBoxManage. This would be a very important and valuable feature. Also, it would be valuable to as well allow auto resize to be turned on and off via VBoxManage. These would be extremely valuable and important features to us. Thank you very much, it is greatly appreciated.",David
10351,Host-Q and Host-H do not follow host key remapping,VirtualBox 4.1.10,defect,2012-03-19T20:15:25Z,2012-03-19T20:15:25Z,2012-03-19T20:15:25Z,"Steps to reproduce:

1. Change host key from default (command) to left control + left option.
2. Start a guest (I have a Debian Linux guest).
3. Type Command-Q.

Expected behavior:

* Keystroke is passed through to guest.

Actual behavior:

* Keystroke is intercepted by VirtualBox (which offers to quit).
* After cancelling the quit dialog, the Command key is stuck down until it's pressed again.

Misc:

* Basically, this is a user interface bug. Following the principle of least surprise, all host key combinations should be remapped if the host key is changed. Also, these keystrokes are needed in the guest OS (Emacs in particular uses them frequently).
* This forum thread may be relevant: https://forums.virtualbox.org/viewtopic.php?f=6&t=29695

Thanks for your hard work on VirtualBox! It makes my work dramatically easier.",reidpr
11417,User Manual controlvm options,VirtualBox 4.2.6,defect,2013-01-24T16:57:06Z,2013-01-24T16:57:06Z,2013-01-24T16:57:06Z,"In the HTML and PDF versions of the user manual, the description of the VBoxManage controlvm ""extra option"":

nic<1-N> null|nat|bridged|intnet|hostonly|generic

is incomplete, compared to the VBoxManage command's help, which lists:

nic<1-N> null|nat|bridged|intnet|hostonly|generic '''[<devicename>]'''

This was the one I was most concerned with. However, it appears that there are many other options and ""extra options"" that are not documented (i.e., not explicitly listed as options, but may be described elsewhere) in the user manual:

acpipowerbutton|acpisleepbutton

keyboardputscancode <hex> [<hex> ...]

nictrace<1-N> on|off

nictracefile<1-N> <filename>

nicproperty<1-N> name=[value]

natpf<1-N> [<rulename>],tcp|udp,[<hostip>],<hostport>,[<guestip>],<guestport>

natpf<1-N> delete <rulename>

gueststatisticsinterval <seconds>]

clipboard disabled|hosttoguest|guesttohost|bidirectional

draganddrop disabled|hosttoguest

vrdeproperty <name=[value]>

vrdevideochannelquality <percent>

plugcpu <id>
unplugcpu <id>

cpuexecutioncap <1-100>",Stephen Rondeau
11497,"When starting on user login in windows in fullscreen mode, vb loses focus",VirtualBox 4.2.6,enhancement,2013-02-16T15:00:00Z,2013-02-16T15:00:00Z,2013-02-16T15:00:00Z,"I have set up virtualbox to start up when the Windows user logins, By setting up the virtualbox command line tool to be run in a script on Windows user login, to start virtualbox on start up from a script when the windows user logs in. I wish for it to be started in fullscreen mode so the Windows UI is not visible at all, including the Windows taskbar covered up.

The problem is, after virtualbox starts when the user logs in, the Windows taskbar appears at the top of the screen even though virtualbox is in fullscreeen mode, and virtualbox loses focus. Virtualbox needs to add a stayontop option for use from the virtualbox command line tool to tell virtualbox to stay on top and regain focus if virtualbox happens to lose focus and make sure the windows taskbar stays covered up.

I also request a ""screenmode"" vboxclient option for specifying display mode to use, such as ""fullscreen"", when the vboxclient virtualbox command line program is used, to assure that virtualbox is started in fullscreen mode, by supplying this fullscreen option to vboxclient, when started from with vboxclient from my startup script. ",David
11846,Setting the medium description not implemented,VirtualBox 4.2.12,defect,2013-06-06T11:17:12Z,2013-06-07T13:56:08Z,2013-06-07T13:56:08Z,"Setup
Host: Core i5 3gen (quad core), 16GB RAM, Windows 8 Pro 64 bits.
Guest: 4 cores, 4GB RAM, 2 alread, no OS installed.

I created a disk and attached to a VM with vboxmanage. While the attaching was successful, it gave me some errors:

C:\Users\luka\Desktop>vboxmanage createhd --filename ""E:\asm\asm-vol00.vdi"" --size 20480 --variant Fixed
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Disk image created. UUID: 706f7563-882f-4da2-91c5-3a593dcd957a

C:\Users\luka\Desktop>vboxmanage storageattach ""RAC n1"" --storagectl SATA --port 2 --type hdd --medium ""E:\asm\asm-vol00.vdi"" --mtype shareable --comment ""Disco para ASM""
VBoxManage.exe: error: Method Medium::put_Description is not implemented
VBoxManage.exe: error: Details: code E_NOTIMPL (0x80004001), component Medium, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Description)(bstrComment.raw())"" at line 685 of file VBoxManageStorageController.cpp",chesterman
11856,Quick shutdown of all vms wanted,VirtualBox 4.2.12,enhancement,2013-06-12T08:26:00Z,2013-06-12T08:36:25Z,2013-06-12T08:36:25Z,"This is not a bug, but an enhancement-question


I'm running Debian 7.0.
When i'm shutting down the system 
(This can manual or automatic or by powerloss and other causes..)
Init sends the SIGTERM signal and 5 sec later the SIGKILL.

In the /etc/rcx.d  the vbox-services are executed for shutdown/reboot at the beginning of the shutdown/reboot.
K02vboxautostart-service
K02vboxballoonctrl-services
K02vboxweb-services
K03vboxdrv
(after this unmouting nfs takes place)

Because of the shutdown order, i cannot move the proces more to the back. I can only try to shutdown the vm's before vboxservices are going down. This means a K01 for my script.

I did make a script to put the vm's in savestate one by one. (because a powerdown will not work for some machines.)
Saving a machine takes a few seconds.
I want to save 5 or more vm's.

By default i can save one vm.
With some tuning i can save 4 vm's before the host go's down.

The problem is, that the other vm's are just stopped. And could lose data, because the proces is killed, without the change to save the state off the machine.


I have a question.

Is it possible to make a command likje this:

vboxmanage controlvm all savestate

And that this command brings all machines down '''at once'''.
Not one after an other but alltogether. So it go's quicker and can be done in 5-10 sec.

Or an other sollution would be, the possibility to run commands on the background. So i can call all vm's one by one and don't have to wait for finishing before i can call the next one.

something like this:

vboxmanage controlvm <vm> savestate &

Thanks





",ED
12361,Autostart config doesn't allow for shared storage of VM files,VirtualBox 4.3.2,defect,2013-11-14T05:12:53Z,2013-11-14T05:12:53Z,2013-11-14T05:12:53Z,"As others have done I have several virtualbox servers which store the VM definitions on a common NFS share to facilitate rebalancing loads, maintenance, and teleportation.  The current implementation of autostart uses a config entry in the VM definition .vbox file to determine whether the machine should autostart, but that won't work in the case where the machine definition has been registered on multiple machines, it'd try to autostart on all of them.

I believe the autostart config should not be stored in the machine config file, but in the ~/.VirtualBox directory which can still be specific to the server machine even though the VM definition is shared across servers.",Steve Prior
12477,Can't operate any more on a locked VM -- a way to force lock removal is needed,VirtualBox 4.3.4,defect,2013-12-12T09:58:29Z,2016-12-19T13:20:55Z,2016-12-19T13:20:55Z,"Sometimes it happens that a VM stops or hangs for some unknown reason and it becomes impossible to operate on it any more because vbox says it's locked.

For example:
{{{
$ VBoxManage controlvm xyz poweroff
VBoxManage: error: The virtual machine is being powered down
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: ""PowerDown(progress.asOutParam())"" at line 222 of file VBoxManageControlVM.cpp
}}}

and trying to start it gives:
{{{
$ VBoxHeadless -s xyz
Oracle VM VirtualBox Headless Interface 4.3.4
(C) 2008-2013 Oracle Corporation
All rights reserved.

VBoxHeadless: error: The machine 'xyz' is already locked for a session (or being unlocked)
VBoxHeadless: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxHeadless: error: Context: ""LockMachine(session, LockType_VM)"" at line 955 of file VBoxHeadless.cpp
}}}

Now I'm stuck: the only way I know to solve this problem is to completely shutdown vbox and/or restart the server, but this forces to shutdown all the other running vms, and thats not really easy on some situation.

I suppose that a way to force the removal of a lock is much needed.",Alex
12812,*.start and *.stop scripts are not created by VBoxManage modifyvm myvm --autostart-enabled on,VirtualBox 4.3.8,defect,2014-03-12T06:54:47Z,2014-03-12T06:54:47Z,2014-03-12T06:54:47Z,"I have followed the steps in this tutorial: [http://www.vionblog.com/virtualbox-4-3-autostart-debian-wheezy/]

The problem is no *.start or *.stop files are created in /etc/vbox/ (and no errors are shown) after running the command:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled on
}}}

In case it helps, trying to disable auto start for the same VM does give an error:

{{{
$ VBoxManage modifyvm myvm --autostart-enabled off
VBoxManage: error: Removing machine 'myvm' to the autostart database failed with VERR_FILE_NOT_FOUND
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(AutostartEnabled)(ValueUnion.f)"" at line 2616 of file VBoxManageModifyVM.cpp
}}}

Host os: Ubuntu Server 12.04-4 (amd64)

VirtualBox: 4.3.8

This issue was reported on the forum a few weeks ago, but there has been no reply:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=60425&p=282223#p282223]

Thanks!


For reference, here's user/group involved:

{{{
$ whoami 
dan
$ groups
dan adm cdrom sudo dip plugdev lpadmin sambashare vboxusers
}}}
 

The contents of /etc/vbox

{{{
$ ls -al /etc/vbox/
total 12
drwxrwxr-t   2 root vboxusers 4096 Mar 12 00:55 .
drwxr-xr-x 101 root root      4096 Mar 12 02:11 ..
-rw-r--r--   1 root root       239 Mar 12 00:55 autostart.conf
}}}

content of autostart.conf:

{{{
# Default policy is to deny starting a VM, the other option is ""allow"".
default_policy = deny

# user dan is allowed to start virtual machines but starting them
# will be delayed for 10 seconds
dan = {
 allow = true
 startup_delay = 10
}
}}}

uname:

{{{
$ uname -a
Linux ubu-host64 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
}}}",Dan Rollo
13275,VBoxManage does not set hostonly adapter name,VirtualBox 4.3.14,defect,2014-08-11T11:53:49Z,2014-10-18T09:07:02Z,2014-10-18T09:07:02Z,"I've got a script that creates VM's for me and one of the lines is this one:
VBoxManage modifyvm ""$VM"" --nic2 hostonly --hostonlyadapter1 'vboxnet0'

I can see the adapter in the network section in the GUI, however the name is blank. To populate the name I need to use the GUI and enter Settings, Network, applicable adapter and press Ok. I.e. I do not need to change anything, just press Ok for the hostonly adapter to have the name set.",Onkelringnes
13500,Windows VirtualBox Process Priority support,VirtualBox 4.3.18,defect,2014-10-12T18:15:07Z,2021-06-08T23:57:02Z,2021-06-08T23:57:02Z,"BOINC runs CPU-instensive tasks (sometimes VirtualBox CPU-intensive tasks), typically at idle priority, but sometimes at below normal priority. The intent is to not interfere with the user's computing experience.

Before the hardened security that was added to VirtualBox for Windows (using VirtualBox 4.3.12 or prior), BOINC could easily manage/set/increase/decrease the process priorities as needed.

After the hardened security was added to VirtualBox for Windows (using VirtualBox 4.3.14+), the process priorities can no-longer be controlled. They run at Normal, with no way to change them (that I know of). This ends up degrading the user experience. I'm considering this a defect, since the hardened security changes broke something that was previously working great.

Please add some way to control the priorities of the VM processes that get instantiated -- Preferably available in the VirtualBox Manager UI, but for BOINC's purposes, VBoxManage command line parameters would work too I believe.

Thanks,
Jacob Klein",Jacob Klein
13686,VirtualBox + Actual Windows Manager = crash,VirtualBox 4.3.20,defect,2014-12-12T14:14:03Z,2015-07-07T12:02:14Z,2015-07-07T12:02:14Z,"Hello,

I recently installed the Actual Windows Manager application (demo available here: http://www.actualtools.com/windowmanager/) to manage my multiple screens.

I noticed that, when this application is installed, all my virtual machines crashes when I try to open them. After 5 seconds, the virtual machine window freezes, and it's not possible to make any action. I noticed that the virtual machine continues to work on the application main interface (the virtual machine is still updated inside the screenshot control), but the virtual machine display window stops to work, and I have no alternative but to kill it.

When this happens, my machines take the Aborted status, and I cannot do nothing to resolve that. If I try to start my machine again, it restarts normally, but after 5 seconds, the problem returns. All my virtual machines are affected by this issue. If I uninstall the Active Windows Manager, all becomes normal.

I'm working on Windows 7 professional 64bit.

Regards",jeanmilost
13692,Vboxmanage Guestproperty Get command - 'laconic' output,VirtualBox 4.3.20,enhancement,2014-12-15T15:41:39Z,2014-12-15T15:41:39Z,2014-12-15T15:41:39Z,"There are presently two modes for the command-line output of ""Vboxmanage guestproperty get"", the default 


{{{
""Value: ____""
}}}
 

and a --verbose, giving this:


{{{
Value: ______
Timestamp: ###################
Flags: ______
}}}

When using ""Vboxmanage guestproperty get"" in a script, the output of the command has to be put through a filter to act on just the contents of the desired property, without acting on the title preceding the property contents. Especially is this so if one want's the timestamp or the flags, and has to hunt through the verbose output to find the desired data.

It would be useful to have a ""laconic"" output mode, giving just the contents of the requested item itself, with no explanatory name in front of the value, so the command output could be inserted into a variable without any filtering needed later in the script.

Suggested switches:

''--justvalue''  only the value without the preceding ""value: ""

''--justtimestamp''   only the timestamp number without the ""timestamp: ""

''--justflags''    only the flags, without the ""flags: """,scottgus1bug
13697,4.3.20 doesn't start virtual machines any more (supHardenedWinVerifyProcess failed),VirtualBox 4.3.20,defect,2014-12-18T07:23:20Z,2017-09-25T14:30:00Z,2017-09-25T14:30:00Z,"Hi,
yesterday I upgraded from 4.3.12 to 4.3.20 r96997 and every virtual machine on my Win7-32bit SP1 Enterprise Host hangs on startup with this messages (see screenshots):

Error in supR3HardNtChildPurify:
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc=-5673)

I executed KB3024777-x86.exe to remove KB3004394 but it doesn't seem to do anything. In system control, programs, ""installed updates"" I can't find KB3004394.

[[Image(http://abload.de/img/1jgahq.png)]]
[[Image(http://abload.de/img/2hpbct.png)]]

It would be great to get some help on this issue!
If you need any further information about it I'll provide it:-)
Thanks in advance.",JackyRyan
13736,Function Keys in VirtualBox are inactive,VirtualBox 4.3.20,defect,2015-01-05T13:45:38Z,2015-01-05T14:09:20Z,2015-01-05T14:09:20Z,"Hallo
My PC is ASUS ZenBook with OS:Win7 Prof (Host).
I have Installed  WM VirtualBox 4.3.20 with Extension package.
My Guest OS is Win98.
In my Application I need the function keys F1 to F12.
I have try all possible, I also search in the community FAQ but without
success. The proposition I have found there are without success. activate
What I have to do for activating the F1 to F12 ??
Thank You in advance
Anton
",akurka
13763,Problem with setextradata GUI/Seamless on,VirtualBox 4.3.20,defect,2015-01-15T13:51:36Z,2015-03-30T16:09:06Z,2015-03-30T16:09:06Z,"Hello.
I develop on c#.
I'm trying to start VirtualBox VM to SeamlessMode via VBoxManage.exe in command line under Windows 7/8/8.1 host. The problem is that it works, but not all the time. If the host computer is powerful then the success rate of starting VM in seamless mode is about 90%. If the host machine is slow then the success rate drops to 50%.
Please see the attached snippet (VM starting in seamless mode) 
	restoreSnapshot();[[BR]]setSeamlessMode();[[BR]]runVM(); 

	public static void restoreSnapshot()
	{
			Process VBoxManage = new Process();
    			VBoxManage.StartInfo.CreateNoWindow = true;
	    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    			VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    			VBoxManage.StartInfo.Arguments = ""snapshot VM restore Snap1"";
	    		VBoxManage.StartInfo.UseShellExecute = false;
	    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    			VBoxManage.Start();[[BR]]String line = """";
		        while (!VBoxManage.StandardOutput.EndOfStream)
		        {	        
		            line = VBoxManage.StandardOutput.ReadToEnd();	            
		        }
	        	VBoxManage.Dispose();
	}

	public static void setSeamlessMode()
	{
		
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    		VBoxManage.StartInfo.Arguments = ""setextradata VM GUI/Seamless on"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    		VBoxManage.Start();[[BR]]String line = """";
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
	        VBoxManage.Dispose();
	        
	}

	public static void runVM()
	{            
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
            	VBoxManage.StartInfo.Arguments = ""--nologo startvm VM -type GUI"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;
    		VBoxManage.Start();            
	        String line = """";[[BR]]
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
                VBoxManage.Dispose();            
        }",batyr
13765,clonevm faster: make use of --reflink,VirtualBox 4.3.20,enhancement,2015-01-16T12:43:06Z,2015-01-16T12:43:06Z,2015-01-16T12:43:06Z,"I'm running vbox machines off a btrfs partition with CoW. When combined with bcache (SSD-backed cache) the fragmentation penalty of fragmented images doesn't hurt much - i.e. I get adequate perfomance of 3-8 VMs on my Lenovo T540p notebook. 

When I clone the vm (separate copy), virtualbox does a full copy of the image - taking considerable time (4 hours for 100GB image) and space. I suggest to utilize the ""cp --reflink=auto"" instead. The copy is made instantly (if possible and falls back to traditional copy) and no additional space is taken until there are changed blocks in the image file.  ",rugubara
13861,Feature Suggestion: usb and other devices controlling of connections admin permissions,VirtualBox 4.3.22,enhancement,2015-02-19T22:51:48Z,2015-02-19T22:51:48Z,2015-02-19T22:51:48Z,"There should be a way to at least hide (as in VMware player)
or preferably disable the usb connections or restrict for 
non admin users, 
the connecting and disconnecting of specific usb and other devices
shared with the host so kids/non admin users can't randomly connect
and disconnect devices. 
One example is the mouse/keyboard -if disconnected instability in host also.
Or if loading a VDI for virtualbox off the external usb
hard drive you don't want this accidentally disconnected from the host, 
as you may have data loss and crash VM.

I am new to using virtual box and have yet to use the usb filters -not sure how this works.",Astrogirl
13874,"On host sleep/resume, guest becomes ""aborted""",VirtualBox 4.3.22,defect,2015-02-21T04:29:41Z,2018-02-07T12:34:47Z,2018-02-07T12:34:47Z,"Ubuntu 12.04 with up-to-date guest additions. Did not happen in 4.1.

{{{
00:00:23.836304 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:24.049241 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:25.603698 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:25.783293 Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:43.873102 Guest Log: VBoxService 4.3.22 r98236 (verbosity: 0) linux.amd64 (Feb 12 2015 16:53:43) release log
00:00:43.873123 Guest Log: 00:00:00.000103 main     Log opened 2015-02-21T04:21:53.707725000Z
00:00:43.873193 Guest Log: 00:00:00.000219 main     OS Product: Linux
00:00:43.873234 Guest Log: 00:00:00.000263 main     OS Release: 3.2.0-23-generic
00:00:43.873273 Guest Log: 00:00:00.000301 main     OS Version: #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
00:00:43.873311 Guest Log: 00:00:00.000337 main     OS Service Pack: #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
00:00:43.873356 Guest Log: 00:00:00.000377 main     Executable: /opt/VBoxGuestAdditions-4.3.22/sbin/VBoxService
00:00:43.873363 Guest Log: 00:00:00.000382 main     Process ID: 2505
00:00:43.873369 Guest Log: 00:00:00.000385 main     Package type: LINUX_64BITS_GENERIC
00:00:43.877150 Guest Log: 00:00:00.004170 main     4.3.22 r98236 started. Verbose level = 0
00:00:43.978632 NAT: DHCP offered IP address 10.0.2.15
00:00:47.310609 Pausing VM execution, reason ""host suspend""
00:00:47.311013 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:00:47.313057 AIOMgr: Endpoint for file '/Users/alex/VirtualBox VMs/t11e-vm1/box-disk1.vmdk' (flags 000c0781) created successfully
00:00:47.372196 PDMR3Suspend: 61 135 737 ns run time
00:00:47.372214 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:00:49.747565 Resuming VM execution, reason ""host resume""
00:00:49.748181 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
00:00:49.748329 AIOMgr: Endpoint for file '/Users/alex/VirtualBox VMs/t11e-vm1/box-disk1.vmdk' (flags 000c0723) created successfully
}}}",atombender
13932,VBoxManage returns success even thow it failes,VirtualBox 4.3.24,defect,2015-03-06T15:14:01Z,2015-03-11T13:38:58Z,2015-03-11T13:38:58Z,"vboxmanage metrics enable --list ""Android 5""
echo $?
0
vboxmanage --version
4.3.24r98716
",Kappen
13949,All guests fail to start,VirtualBox 4.3.24,defect,2015-03-10T13:54:37Z,2015-03-16T08:24:39Z,2015-03-16T08:24:39Z,"All guests fail to start at virtualbox 4.3.24


The virtual machine 'bioLinux' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\libindo\VirtualBox VMs\bioLinux\Logs\VBoxStartup.log'.

Code erorr: E_FAIL (0x80004005)
Компонент: Machine
Интерфейс: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

",buratin
14007,Cannot Insert Linked Cloned Into Group,VirtualBox 4.3.26,defect,2015-03-29T20:05:41Z,2016-01-22T17:50:21Z,2016-01-22T17:50:21Z,"== Failed Scenario ==
Inserted a Base VM into a new Group[[BR]]
Created a snapshot while VM is off[[BR]]
Cloned the snapshot into a new Linked Clone[[BR]]
The linked clone appears on /VBOX main folder, and not under the Group folder[[BR]]
[[BR]]
Extra: Moving out of the group in Vbox UI and in again, or to another group and back, keeps it in the Main Vbox folder


== Workaround ==
Before cloning base VM, move it out of any group to main Vbox folder[[BR]]
Clone base VM[[BR]]
Move Base and Clone VMs into the group",Zvika Dror Zend
14025,The Exception unkown software exception (0xc06d007e),VirtualBox 4.3.26,defect,2015-04-04T23:42:04Z,2015-04-05T06:19:29Z,2015-04-05T06:19:29Z,"After a re-installing windows I am unable to launch virtualbox, it gives me this error: http://i.imgur.com/jtQC0k6.jpg . I have tried uninstalling and re-installing a few times no luck :( . Can see the log file here : http://pastebin.com/raw.php?i=cMfiN8FD

I've tried turning off firewall and sleeping Kaspersky with no luck. I apologize if this is in the wrong thread, please feel free to move it to the correct one if need be. ",n0rbertt
14177,Very slow command line operations on long uptime,VirtualBox 4.3.28,defect,2015-06-05T13:18:01Z,2015-06-06T18:16:06Z,2015-06-06T18:16:06Z,"I've a server where I'm trying to run a lot of virtual machines (25-30), with somewhat long uptime (some weeks) and what I see is a constant increase of the slowness of VBoxManage operations.

For example, on a fresh start the command ""VBoxManage list runningvms"" employs only 0.2 seconds but day after day the execution time rises and after some weeks the same command can employ even 60 seconds to complete.

This in turn gives problem with applications like phpvirtualbox that is unable to even reach the main screen (supposedly) due to various timeouts.

The only way to solve the problem is to shutdown all the machines, stop the vbox service, and restart it.",Alex
14194,VBoxManage VM with same name in different groups,VirtualBox 4.3.28,enhancement,2015-06-14T13:58:28Z,2015-06-14T13:58:28Z,2015-06-14T13:58:28Z,"In VBox GUI I can easily view and manage two different guests with the same name but are located in different groups:

Project-A -> DC

Project-B -> DC

However, when using 'VBoxManage list runningvms' for example, I just have two VMs called 'DC'.  The only way to manage them is to use the UUIDs which is really awkward to use.  In fact, I have to use 'showvminfo' just to work out which group each guest belongs to.


It would be easier if the group could be used as part of the VMNAME so that they can be referred to as follows in command line tools such as VBoxManage:

Project-A/DC

Project-B/DC

I know I could rename the guests to ProjA-DC and ProjB-DC or similar, but that defeats the object somewhat.
",garethwilliams
14207,VBoxManage unregistervm --delete performs only a partial deletion if media file is locked by other process,VirtualBox 4.3.28,defect,2015-06-17T09:12:07Z,2015-06-17T09:12:07Z,2015-06-17T09:12:07Z,"Trying to produce an automatic provisioning script to build VM's on demand and encountering this issue when the machine get above a few GB in size.

Process calls the vboxmanage export command and then immediately calls the unregistervm --delete command to remove the VM leaving just the export file.

However if the VM is above a few GB in size the lock is not released on the media in time resulting in:

{{{
BoxManage.exe: error: Medium 'C:\Users\scobarn\VirtualBox VMs\My_VM\My_VM.vdi' is locked for reading by another task
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium
VBoxManage.exe: error: Context: ""int __cdecl handleUnregisterVM(struct HandlerArg *)"" at line 166 of file VBoxManageMisc.cpp
}}}

Subsequent delete commands fail due to the vboxmanage unregister command executing just the unregistration part but leaves all files and directories behind requiring manual cleanup.

{{{
VBoxManage.exe: error: Could not find a registered machine named 'My_VM'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: ""FindMachine(Bstr(VMName).raw(), machine.asOutParam())"" at line 154 of file VBoxManageMisc.cpp
}}}

Shouldn't vboxmanage unregister --delete be an all or nothing command and if an error occurs perform none of the steps instead of just removing the registration and leaving all files behind to cause issues without manual cleanup?",sbarnden
14375,VM apparently becomes inaccessible after shutdown,VirtualBox 5.0.0,defect,2015-08-02T19:25:40Z,2015-08-02T19:25:40Z,2015-08-02T19:25:40Z,"Steps:[[BR]]

1) Start VM[[BR]]
2) Do some work[[BR]]
3) Shutdown[[BR]]
After that some VMs always show the state ""inaccessible"". It is possible to remove it. Later on it is not possible to add this VM due to an error:[[BR]]
VBoxManage registervm /u00/HDD/W764.2015/W764.2015.vbox
VBoxManage: error: Could not find an open hard disk with UUID {9d2e777b-dc39-40fc-b1b8-8661dd13bd84}[[BR]]
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports[[BR]]
VBoxManage: error: Context: ""OpenMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())"" at line 85 of file VBoxManageMisc.cpp[[BR]]
[[BR]]

Workaround (not always working):[[BR]]
4) Use VBoxManage showhdinfo <virtualdisk vdi name>. (This command may produce no output, in this case registering VM is not possible.)[[BR]]
5) Add VM back if the previous command provided the information about vdi disk.[[BR]]
[[BR]]
After repeating steps 1-3 VM becomes inaccessible again.
",zoman
14514,VM freezes during installation of guest,VirtualBox 5.0.2,defect,2015-08-28T07:09:02Z,2015-08-28T07:09:02Z,2015-08-28T07:09:02Z,"I am trying to install openSUSE 13.2 and in the middle of the installation everything just stalls. I am able to move the mouse around and operate dialog boxes/buttons inside openSUSE but the installation itself completely froze.
Process Explorer confirms it where I/O activity completely stops in the middle of loading files. It never stops in the same spot always. Once it got as far as installing half the applications that come with the OS, most of the time it doesn't even make it to the first one.

On average it's about 10 minutes into the session that this happens. Once it stalls, there is no possible way to terminate the VM. If I manage to close the window, the process will remain in memory (and I cant start the VM again). I cannot even normally restart my host PC. I have to press the button on the computer to force restart. If I try to terminate the VM after the freeze, it interferes with the functioning of my host OS. Some programs I can't open at all such as CMD, other operations will be extremely slow and so on.",Inds
14635,A way to start (or list) all the VMs in a group,VirtualBox 4.3.30,enhancement,2015-09-25T07:48:51Z,2015-09-25T07:48:51Z,2015-09-25T07:48:51Z,"I know it's possible to start all the VM in a group using the GUI, but I can't find an easy way to do it from VBoxManage.

I would suggest to add something like:
{{{
    VBoxManage startvm --group '/groupname'
}}}
Or at least to allow easy scripting with a command that lists all the VMs in a single group, which right now is only possible with some clever scripting like this:
{{{
    VBoxManage list -l vms | awk '/^Groups:/ { groups = $2; } /^UUID:/ { uuid = $2; if (groups == ""/groupname"") print uuid; }'
}}}
(which as is doesn't support VMs in multiple groups)",Lapo Luchini
14715,VM renaming,VirtualBox 4.3.28,defect,2015-10-19T07:21:10Z,2015-10-19T10:22:31Z,2015-10-19T10:22:31Z,"My VM is creating during automatic provisioning with Vagrant. After VM is created I have an error if I start this VM. (The same script uses on Mac OSX, have no issues with it)

VM has 2 network adapters: Nat & Host-Only Adapter. No GUI. No USB

Log file is attached",tuborg
14724,Need way to move virtual-disk files of running VM,VirtualBox 5.0.6,enhancement,2015-10-20T23:35:20Z,2017-03-17T11:01:58Z,2017-03-17T11:01:58Z,"This is an enhancement request to permit virtual disk files to be moved while they are in use by a (paused) VM.

If an out-of-disk condition occurs, VBox very nicely pauses the VM and pops up a message so you can fix the problem and resume.  However, it continues to hold the virtual disk (including snapshot) files open, so even if they are moved and replaced by symlinks, no disk space can be freed up.  If the VM was running in a dedicated partition, i.e., there is nothing else to move or delete besides VM's files, then there is no possible recovery without loosing VM state; VBox won't close the old files until the VM is shut down, and it and it can't save the VM state if disk is full.

Following are a couple of suggestions, one basic and the other fancy:

Method A (Basic): When a VM is ""paused"", close all the VM's files, at least the virtual disks; re-open them only when the VM is resumed.

   This would let you manually relocate a virtual disk and replace it with a symlink while the VM is paused.  Using the symlink would be necessary because the .vbox file still could not be edited while VBox is running.

Method B (Fancy): Provide a comprehensive command to move a virtual disk, updating VirtualBox.xml or the VM's .vbox file as appropriate.  For example

  VBoxManage modifyvm <vmident> --movemedium <uuid|filename> /destination/folder/
  VBoxManage modifyvm <vmident> --movesnap <snapid|filename> /destination/folder/

This would 
  1. pause all VMs using the specified virtual disk *if not already paused*
(and make them close the underlying files, just as in the simpler method above); 
  2. move the file, 
  3. update and rewrite VirtualBox.xml or the VM's .vbox file with the new path; 
  4. resume VMs paused in step 1 (but not VMs which were already paused)

",Jim Avera
15113,VBoxManage controlvm savestate fails on Windows Host,VirtualBox 5.0.14,defect,2016-02-04T21:27:59Z,2016-02-05T09:41:16Z,2016-02-05T09:41:16Z,"'''Execute:'''[[br]]
{{{VBoxManage controlvm <vmname> savestate}}}

'''Displays:'''[[br]]
{{{VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)}}}[[br]]
{{{VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 101 of file VBoxManageControlVM.cpp}}}

The pause option also displays the same error message. Other options may produce the same error message.
This issue seems to have first appeared in Sept 2015, see https://forums.virtualbox.org/viewtopic.php?f=6&t=70975",Tim T ASP
15119,Trust wireless mouse locks up virtual box,VirtualBox 5.0.14,defect,2016-02-05T18:07:29Z,2016-02-05T18:07:29Z,2016-02-05T18:07:29Z,"Using a trust wireless mouse no. 16592, when starting Windows 7 in Virtual box the mouse locks up. Change to Apple wireless mouse and this now works. Then Apple mouse will then lock up and no way of retrieving System. Forces reboot. Loses un-saved work. No problem when starting Windows XP. This is a recent problem and has only just manifested itself since the last upgrade to 5.0.14",mikey
15153,Invalid machine state: GuruMeditation,VirtualBox 5.0.14,defect,2016-02-17T17:43:52Z,2016-02-17T17:51:38Z,2016-02-17T17:51:38Z,"I am running two VMs on OS X El Capitan, one of the vm keeps getting rebooted randomly with error: 
32:16:18.536412 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: GuruMeditation}, preserve=false aResultDetail=0",wei1984
15258,booting issue,VirtualBox 5.0.16,task,2016-03-21T17:53:10Z,2016-03-22T10:29:14Z,2016-03-22T10:29:14Z,"i installed kali as VM 
every time i boot it : i get black screen with Loading , Please wait 

which never goes away ",zee.21
15370,Exception Breakpoint,VirtualBox 5.0.20,task,2016-04-30T12:22:45Z,2016-05-04T06:54:13Z,2016-05-04T06:54:13Z,"Windows XP guest on a Windows 7 Host
In VirtualBox manager, upon restoring from a save state
I get a Breakpoint exception message (see attached image)
The status of the guest then becomes ""Aborted"".
Upon restoring from this state, the guest boots up correctly.
If I then Save the state of the guest,
then the next time I try to restore it I get this Exception Breakpoint message again.",keuk
15378,Not possible to resume VM after host hibernate & resume => Ubuntu bug,VirtualBox 5.0.20,defect,2016-05-02T08:34:21Z,2021-07-10T22:33:05Z,2021-07-10T22:33:05Z,"After hibernating and resuming my Ubuntu 14.04 host with a running VM, the VM is paused. All attempts to resume this VM failed with the error message: ""VM is paused due to host power management"". It tried to resume using the GUI by unchecking the hook at menu item ""Machine/Pause"", and I used the CLI tool with these command lines: ""VBoxManage controlvm $VMNAME resume"" and ""VBoxManage startvm $VMNAME"" and always got the same error message.

Workaround: Close the VM, then start it again. All data in the VM is lost.

{{{
$ VBoxManage --version
5.0.20r106931
}}}

{{{
$ uname -a
Linux $HOSTNAME 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
}}}

{{{
$ cat /etc/os-release
NAME=""Ubuntu""
VERSION=""14.04.4 LTS, Trusty Tahr""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 14.04.4 LTS""
VERSION_ID=""14.04""
HOME_URL=""http://www.ubuntu.com/""
SUPPORT_URL=""http://help.ubuntu.com/""
BUG_REPORT_URL=""http://bugs.launchpad.net/ubuntu/""
}}}",Bohnenzaehler
15437,"""VBoxManage list runningvms"" does not work with the windows taskplaner",VirtualBox 5.0.20,defect,2016-05-20T17:05:53Z,2016-05-20T17:05:53Z,2016-05-20T17:05:53Z,"Hello, i set up my system (Windows 6.3.9600) that the guest (Ubuntu) is starting after systemstart under the permissions of the user ""VM-Helper"" If i use the command 'C:\Windows\System32\runas.exe /user:VM-Helper /savecred ""VBoxManage startvm Ubuntu --type headless""' (running in the VB dir) i can see the status in the GUI with the command 'C:\Windows\System32\runas.exe /user:""VM-Helper"" /savecred ""VirtualBox.exe""'.
But if i start the task ""%programfiles%\Oracle\VirtualBox\VBoxManage startvm Ubuntu --type headless"" (running in the VB dir) as VM-Helper the status can't be read out by VirtualBox.exe and VBoxManage.exe list runningvms"".

I was very pleased if you can reconstruct it.
The VM starts in both cases, the permissions/user are/is right (acc. to taskmanager and log). I have tried detours over batch-files ecetera...
If i want to start the VM again over the GUI as VM-Helper with a still running instance, (of course) i'll get the error ""E_FAIL (0x80004005)""",Mike446
15545,Popup menu does not appear,VirtualBox 5.0.22,defect,2016-06-23T12:35:15Z,2016-06-23T16:03:22Z,2016-06-23T16:03:22Z,Popup menu in virtual machine does not appear. I have set various settings but it does not resolve problem,Destructor
15570,VBoxManage showvminfo fails to find machines,VirtualBox 5.0.24,defect,2016-07-04T23:02:09Z,2016-07-04T23:16:24Z,2016-07-04T23:16:24Z,"Created VM ""W7"", then: 

# VBoxManage showvminfo W7
VBoxManage: error: Could not find a registered machine named 'W7'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())"" at line 2719 of file VBoxManageInfo.cpp

Added more VMs and problem persists.",Pierre Fortin
15605,Full screen bug,VirtualBox 5.0.20,defect,2016-07-13T19:10:47Z,2016-07-13T19:10:47Z,2016-07-13T19:10:47Z,"I know there are 2 tickets for this problmen, but still it's an annoying bug. I can't use full screen mode, either I can't uninstall virtual box. 

When I try to unintall it the wizard came up, then it asks that would I install an another software. No mather what I chose it ends in the same way. The files stayed untouched but I still can run the software.",Zoltanka
15641,mouse capture mode problem when scrolling out of window,VirtualBox 5.1.0,defect,2016-07-19T09:46:40Z,2016-07-19T09:46:40Z,2016-07-19T09:46:40Z,"It'a windows 7 in vbox hosted in my windows 7 in native mode.
I've enabled mouse auto capture mode, I dont have to press ctrl-f to release it.
I have 2 monitors, One is for my virtualbox, in 1 monitor mode.
I use eclipse, notepadd, whatever.
I press the mouse button, to select text, and go out of the vbox monitor window.
when I release, the virtualbox begins to be irresponsive, I cannot select some text anymore with the mouse, I have to restart the vbox in reboot mode or keep the state, and when it's restarted the problem has disappeared.",stephane martin
15783,VBoxManage: error: Error starting guest session (current status is: starting),VirtualBox 5.1.2,defect,2016-08-12T09:32:41Z,2016-08-12T09:32:41Z,2016-08-12T09:32:41Z,"After upgrade from 5.0.26 to 5.1.2 we can not use our automated run sequences controlled by several VBoxManage guestcontrol <vm> run commands, because some of them are returned with the error message:

VBoxManage: error: Error starting guest session (current status is: starting)

This seems to occur not at the first launch of a guestcontrol command after starting the VM, but at one of the following. For example one of such sequence is:

{{{
> VBoxManage snapshot ${VM} restore ""${RestoreSnapshot}""
> VBoxManage  sharedfolder add ${VM} --name RunExecution --hostpath ${HostRunExecutionDirectory}/${BID} --automount
> VBoxManage startvm ""${VM}""  --type headless
> VBoxManage guestproperty get ""${VM}"" ""/VirtualBox/GuestInfo/Net/0/V4/IP""
> VBoxManage controlvm ""${VM}"" setvideomodehint 1920 1080 32
> VBoxManage guestcontrol ${VM} run --username ${VmUser} --password ${VmPassword} --wait-stdout -- \
  ""c:\windows\system32\xcopy.exe"" ""${RunExecutionDirectory}\\runtime-uitest"" ""C:\\runtime-uitest\\"" /r /y /s /i
('''failed''') > VBoxManage guestcontrol ${VM} run --no-wait-stdout --no-wait-stderr \
  --username ${VmUser} --password ${VmPassword} -- ""C:\Windows\system32\cmd.exe"" /c \
  ""${RunExecutionDrive} & cd ${RunExecutionDirectory} & ${RunExecutable} /param:dummy=dummy ""
}}}

Host: 
openSUSE 13.2 Linux r06268 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
VirtualBox-5.1-5.1.2_108956_openSUSE132-1.x86_64
Oracle_VM_VirtualBox_Extension_Pack-5.1.2-108956.vbox-extpack


Guests: 
Windows 7 Professional SP1 64 Bit
Windows Server 2012 R2 Standard
Oracle VM VirtualBox Guest Additions 5.1.2

Until solved we downgrade to 5.0.26.

",rklehm
15809,Virtual machine not runing,VirtualBox 5.1.2,defect,2016-08-17T11:19:04Z,2016-08-17T13:23:46Z,2016-08-17T13:23:46Z,(removed pasted VBox.log content),SerhiiNI
15990,VirtualBox 5.x CLI cannot display snapshot list while VM is running,VirtualBox 5.1.6,defect,2016-09-26T19:07:28Z,2016-10-11T12:04:53Z,2016-10-11T12:04:53Z,"The following command produces an error when executed while the targeted VM is running:

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe snapshot MyLinuxVM list
}}}

The error is as follows:
{{{
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 331 of file VBoxManageSnapshot.cpp
}}}

If the command is executed while the VM is stopped (either suspended or powered off) the command is successful.  I do not have any trouble creating snapshots with VBoxManage while the VM is running.

I had this problem in a previous version (5.0.x) and again when I updated to the latest version (5.1.6).",TastyWheat
16044,version problem,VirtualBox 5.1.6,defect,2016-10-07T15:09:34Z,2016-10-07T15:26:31Z,2016-10-07T15:26:31Z,"inicio normal absurdo,en otras versiones no necesitabamos inicio con desacople.
el arranque de las vm´s en modo normal arroja :

The virtual machine 'other windows' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\tard.sebas\VirtualBox VMs\SERVER2003\Logs\VBoxHardening.log'.

y existen problemas con las auto-capturas de teclado y raton..no deja que esteen ambos en modo auto captura



lo unico bueno de estas versiones nuevas es que se puede configurar la vm´s estando encendida ",tard.sebas
16136,VirtualBox not detecting VMs started on boot,VirtualBox 5.1.8,defect,2016-11-02T02:04:21Z,2016-11-02T23:26:02Z,2016-11-02T23:26:02Z,"I have a server using Microsoft Windows Server 2012 R2, and a virtual machine on it (Debian).

However, I'd like for the virtual machine to be started on boot, without user log in.

So, I used Task Scheduler for this (also tryied nssm and pstools), but no success.

The virtual machine DOES START, however, when I log in and open VirtualBox,
it does not detect the virtual machine running, so it's quite troublesome as I am not planning on RDP or SSH to the guest.

If I do start the VM with VBoxManage while logged in, all works ok.
If I do start the VM with Task Scheduler (admin nor non-admin) it does not work.

I've also reinstalled VirtualBox and ran it without success.",Hario
16160,Add option to not return immediately after a contolvm command,VirtualBox 5.1.8,enhancement,2016-11-06T16:27:07Z,2016-11-06T16:27:07Z,2016-11-06T16:27:07Z,"While running VBoxManage from various systemd unit scripts, I found the following problem:

Systemd service commands like ExecStop return immediately, for example:

{{{
ExecStop=/usr/bin/VBoxManage controlvm MyVBoxVM acpipowerbutton
}}}

The above command will send an ACPI power down signal, which will cause the guest OS to start a shutdown procedure (if configured properly).

BUT

Systemd will see that the PID is still alive (since the guest OS is still powering down) and immediately issue a KILL signal to end the VM process. Thus, the guest OS will not have shutdown cleanly.

A temporary solution, is to create a dedicated shutdown script, which waits and constantly checks if the VM has shutdown or not, before returning. A better solution, would be to add a new parameter to VBoxManage that tells VBoxManage not to return immediately, like:

{{{
ExecStop=/usr/bin/VBoxManage controlvm MyVBoxVM acpipowerbutton noImmediateReturn
}}}

This will make VirtualBox more friendly with systemd units.

Thank you.
",VirtualBarista
16177,in linux 64bit plasma 5 virtualbox start only from terminal,VirtualBox 5.1.8,defect,2016-11-10T08:45:33Z,2016-11-21T11:22:12Z,2016-11-21T11:22:12Z,"As the title say: virtualbox, from release 5.1.6 (and included the build 5.1.9) does not start from menu, but only from terminal.",duns
16187,VirtualBox-Error in suplibOsinit,VirtualBox 5.1.8,task,2016-11-15T12:07:04Z,2016-11-15T12:13:04Z,2016-11-15T12:13:04Z,"In Windows 10 Professional when I like to run any virtual machine I got an error.

Does anybody knows something about this error?",VIrtualtest
16226,vbox file is missing after adding port-forwarding config while guest is running and later guest shutdown,VirtualBox 5.1.10,defect,2016-11-24T12:33:46Z,2016-11-24T12:39:23Z,2016-11-24T12:39:23Z,"Steps to reproduce this problem:

- Create a Linux guest (without installing guest tools).
- Create a snapshot of this guest.
- Fully clone the guest (not linked), not including any snapshot (last state only).
- Run the clone guest.
- Add some port-forwarding configurations while guest is running and save.
- Do ""shutdown -h -t 0"" on the guest.
- It's not previsible how many guest restarts could led .vbox file to be deleted. I had the same problem even with just restarting VirtualBox manager itself or rebooting the host.

Additional info:

Host: Windows 10 Pro Anniversary 64-bits (Hyper-V disabled via ""bcdedit /set hypervisorlaunchtype off"").
Guest: Ubuntu Server 16.04 LTS x64, cloned from another guest.",calamann
16235,latest Guest Additions crash linux guests after installation and rebooting the guest,VirtualBox 5.1.10,defect,2016-11-26T18:44:03Z,2016-11-28T11:20:17Z,2016-11-28T11:20:17Z,"I've find out that the new version of guest extensions crashes down newder debian derivates as elementary os and deepin. I can't confirm this for ubuntu but at least for these too. 

T reproduce 

Download an iso  at deepin.org or elementary.io
install the system on windows at usual 
update the system with sudo apt -y full-upgrade
install guest additions from the iso image delivered with virtualbox as root or with sudo
reboot the guest

The expected result is virtual box on windows will hang up and not respond anymore

",horvan
16265,"Virtualbox 5.1.10 on Ubuntu 6.10 running on Mac Pro 3,1 incorrectly assumes hyperthreading",VirtualBox 5.1.10,defect,2016-12-05T01:43:20Z,2016-12-05T11:31:42Z,2016-12-05T11:31:42Z,"When running the Oracle 5.1.10 deb of Virtualbox-5.1 (5.1.10) on Ubuntu 6.10 installed on a MacPro 3,1 running on Harpertown processors, the Processor tab incorrectly assumes that Hyperthreading is available on that processor and shows 16 CPUs being available on a dual quad-core system.

",howarth
16275,Virtual Box crash on more screen,VirtualBox 5.1.10,defect,2016-12-08T15:32:13Z,2016-12-09T06:41:23Z,2016-12-09T06:41:23Z,"I can translate to english.
Программа аварийно завершается с ошибкой sigfault. Эта ошибка у меня была при использовании Windows 8, 8.1, 10 в качестве основной ОС и Ubuntu 14,15,16 в качестве гостевой ОС. На моём компьютере на работе имеется два монитора. Основная система Win10, гостевая Ubuntu. Ubuntu настроена на использование обоих мониторов. Далее, если я подключаюсь с ноутбука с одним дисплеем к своему рабочему компу через RDP то VirtualBox аварийно завершается. Если так-же удаленно включить её заново и запустить Ubuntu, то всё как-бы загружается и работает. Но при этом в Windows в панели задач я вижу только один ""виртуальный дисплей"" гостевой ОС, но Ubuntu считает что их два! Из-за этого я не могу получить доступ к окнам, открытым на невидимом виртуальном дисплее.",StarVld
16285,Crash disconecting host monitor while saving state,VirtualBox 5.1.10,defect,2016-12-13T19:16:33Z,2016-12-13T19:16:33Z,2016-12-13T19:16:33Z,"While I was saving the state of a VM in fullscreen mode, I disconnected a host monitor (physically, by unplugging the video cable). The VM process crashed with the following error (translated):
 Application Error : The instruction at 0x00000000775C4756 referenced the memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.

After that, the VM in the VBox Manager resulted in an ""Interrupted"" status.

Here are some useful details:
* The host screens '''before''' unplugging were:
 1. Notebook native monitor
 2. HDMI external monitor, with fullscreen VM
 3. MiniDP external monitor, ''main host screen''
* The host screen '''after''' unplugging were:
 1. Notebook native monitor, ''main host screen''
 2. HDMI external monitor, with fullscreen VM
* Of course the host screen configurations before and after unplugging are as expected, including the fact that the main host screen switched from the screen no. 3 to the no. 1
* All 3 monitors have the same resolution, 1920x1024
* The VM has 2 guest screens, but only 1 was enabled
* The VBox Manager was open but '''did not''' crash, i.e. only the VM process crashed",FstTesla
16327,"""Auto Capture keyboard"" option doesn't work",VirtualBox 5.1.12,defect,2016-12-25T12:43:41Z,2019-09-20T04:03:06Z,2019-09-20T04:03:06Z,"Virtualbox captures keyboard even when told to not do so.

Steps to reproduce:

1. Open a VM (e.g. create an empty one).
2. Go to Preferences → Input, and make sure the ""Auto Capture Keyboard"" is disabled.
3. Run the VM.
4. Focus the VM window (e.g. click on it)
5. Try global hotkeys of the host, like switching workspaces, windows, a player — nothing works.

It seem to be a regression to the old [https://www.virtualbox.org/ticket/8596 #8596], but I'm not naming it so because I don't know when it stopped working.

Tested on Archlinux, i3 WM.",Hi-Angel
16335,"VirtualBox automatically forces shut down of guest before displaying ""new version available"" dialog",VirtualBox 5.1.12,defect,2016-12-29T19:02:50Z,2017-01-18T10:09:19Z,2017-01-18T10:09:19Z,"VirtualBox version 5.x (any since 5.0) forces a shutdown of a running guest process to display a dialog stating that there is a new version available.

Steps to reproduce:
1. Install and run a guest operating system (Fedora Linux 23/24/25 in this case(s)).
2. Leave the guest operating system running on the host (Win10 in this case) for many weeks without issue.
3. When a new version of VirtualBox is released, the guest is automatically forced to shut down, and then the VirtualBox GUI displays a notice dialog box stating ""VirtualBox - Information: A new version of VirtualBox is has been released!...."".

Expected behavior:
Don't shut down my running guest operating system to display a simple informational dialog.

Notes:
This has happened to me on various VirtualBox versions 5.0.x and 5.1.x for over 10 months now.  VirtualBox guest tools are installed and are always updated with the host update.  Although I list a Windows 10 host and Fedora guest above, I have had the same exact issue happen on a Fedora 23/24 host and Windows 7 guest, with the same 5.x series of VirtualBox (I did run version VirtualBox 4.x on that combination for a while, however I never experienced this issue).

",gats
16350,VERR_SSM_LOADED_TOO_MUCH when restoring snapshot,VirtualBox 5.1.12,defect,2017-01-03T14:07:04Z,2020-08-18T14:23:48Z,2020-08-18T14:23:48Z,"I cannot resume VM state from existing snapshot, getting following error:

Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).


E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Host: Windows10
Guest: Windows10

",mammoth
16359,VBOX XML files are not locked by VBOX Manager instances,VirtualBox 5.1.4,defect,2017-01-05T15:43:42Z,2017-01-05T15:43:42Z,2017-01-05T15:43:42Z,"We have lost snapshots recently because the .vbox XML files are not locked by the Virtualbox Manager. 

Steps to reproduce:
1. Create a new VM in User1 Windows account.
2. Don't quit from the Virtualbox Manager GUI.
3. Switch to Windows user account User2. 
4. Open the same VM in the Virtualbox Manager.
5. Create a new snapshot (Snapshot 1). 
6. Close the Virtualbox Manager in User2 account, logoff from User2.
7. Switch back to User1.  Snapshot 1 is not listed. 
8. Close the Virtualbox Manager.
9. Start the Virtualbox Manager. Snapshot 1 is not listed. 

Expected result: When the User2 opens the VM in the Virtualbox Manager, it should raise an error that this VM is locked by another user. 

These errors never happen intentionally, so it would be great if the Virtualbox Manager could lock the vbox files.

Sometimes we can recover the snapshots by manually recreating the snapshot entries in the vbox XML file, but this is not optimal.

Thank you for your help",Z6543
16400,Mouse loses ability to drag,VirtualBox 5.1.12,defect,2017-01-17T23:51:49Z,2017-01-31T19:05:42Z,2017-01-31T19:05:42Z,"Win-XP VM on OS-X 10.12.2, VB 5.1.12 r112440 (Qt5.6.2)

After a short period (5 to 10 minutes) the mouse loses the ability to click and drag anything in the XP UI. This happens regardless of the pointer device (mouse, trackpad, etc.) The mouse can still select and click event and hoover are processed correctly. It is only drag that does not work. This applies to any draggle object: windows, filed, window position widgets, etc.

It is possible/likely that this is not caused by time, but by some common activity. But, I have  not been able to identify any such activities.",berkinet
16437,VBoxManage controlvm savestate fails with NS_ERROR_FAILURE (0x80004005),VirtualBox 5.1.14,defect,2017-01-31T13:27:07Z,2017-01-31T14:09:22Z,2017-01-31T14:09:22Z,"When I call 
{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
}}}
from a bash script I get the following error:


{{{
VBoxManage controlvm bosh-lite_default_1485866280659_36137 savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to save machine state
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: ""RTEXITCODE handleControlVM(HandlerArg*)"" at line 276 of file VBoxManageControlVM.cpp

}}}

'''Environment:'''

VBoxManage: Oracle VM VirtualBox Command Line Management Interface Version 5.1.14

Host operating system: CentOS Linux release 7.2.1511 (Core)

Guest operating system: Ubuntu 14.04.4 LTS",acho-bacho
16451,GUI Manager crashes when adding existing vdi file,VirtualBox 5.1.14,defect,2017-02-04T12:21:09Z,2017-02-04T12:21:09Z,2017-02-04T12:21:09Z,Creating a new Windows guest under Windows 7 Host.  Trying to attach an existing vdi file.  If you click on the + at the bottom of the screen the manager crashes (see attached screen capture).  Luckily if you click on the + at the top of the screen it all works!  Maybe the easiest fix would be to remove the + and - at the bottom of the screen.  ,JimAttrill
16516,HTTPS request before LaunchVMProcess let sound crash in guest,VirtualBox 5.1.14,defect,2017-02-27T06:49:59Z,2017-02-27T06:49:59Z,2017-02-27T06:49:59Z,"On a Win7 Guest, Host doesn't mind (tested Win 7 and 10), doing 
[[BR]]
{{{
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(""https://www.google.de"");
HttpWebResponse res = (HttpWebResponse)req.GetResponse();
}}}
before
[[BR]]
{{{
VirtualBox.VirtualBox vBox = new VirtualBox.VirtualBox();
IMachine m = vBox.FindMachine(""VM"");
m.LaunchVMProcess(new Session(), ""gui"", """");
}}}
[[BR]]
the sound in the guest system stops working with 
[[BR]][[BR]]
DSound: Starting playback failed with E_ACCESSDENIED
[[BR]][[BR]]
Switching the https to http in above code, everything will work as expected. 
[[BR]][[BR]]
Additionally, starting the VM without a webrequest (from API or VBoxManage), stopping it and letting VBoxSVC not terminate, means starting the guest by above code immediately, then the https request will not interfere with the guest sound.

Thanks in advance.[[BR]]
Kind regard[[BR]]
Ben",Benne
16553,Virtual Machines running very slowly,VirtualBox 5.1.16,defect,2017-03-11T13:47:57Z,2017-03-14T09:18:51Z,2017-03-14T09:18:51Z,"Hi there,

Apologies if this turns out to be something trivial, but I hope you can help - I've been running Kali Linux / Metasploitable / Windows XP virtual machines using virtual box with no issues until a couple of weeks ago they all suddenly started going unusably slowly, taking ages to even log in and even then extremely laggy to use.

I'm running windows 10 on a HP Desktop with Dual core 1.9GHz and 8GB RAM

What I've tried:

Allocating more RAM / Vram to the VMs - Kali 2GB / 128MB Video

switching between 64-bit and 32-bit versions (my OS is 64 bit)

Uninstalling Vbox and removing all VMs, then re-installing them.

changing chipset from PIIX 3 to ICH9

enable I/0 APIC has always been checked
Hardware clock in UTC time always checked
Enable PAE/NX always checked
Video - Enable 3D Acceleration checked, 128MB allocated 
Storage controller SATA, AHCI, Port count 1, Use host I/O cache checked
Network adapter enabled, NATNetwork selected

I noticed that in the system settings, the 'acceleration' tab was suddenly 'greyed' out - this definitely wasn't the case previously. After some digging, I realised this was related to VTx acceleration, so I logged into my BIOS, enabled it and the acceleration tab came back - I checked the box, but unfortunately it has made no difference. Paravirtualization interface set to 'Legacy' (as it has been), Enable VTx/AMD-v checked, Enable nested paging checked.

Seems really strange as it was working perfectly well previously, so obviously something has changed... perhaps some windows update has caused problems, I have no idea.

I have the same setup running on other machines in the school I work at - older apple machines with a lower spec than my own, and it works fine on them!

Any assistance you can offer is greatly appreciated - sorry if I haven't provided enough info, please let me know what you need.

Many thanks,

George



",GMullin
16738,Cannot Switch Virtualization Off,VirtualBox 5.1.22,defect,2017-05-08T05:58:12Z,2017-05-08T05:58:12Z,2017-05-08T05:58:12Z,"If a VM has virtualization switched on, but the BIOS of the physical machine has virtualization switched off, it is impossible to switch virtualization off for the VM.  This is because Virtual Box detects the missing virtualization and grays out the ""Acceleration"" tab under the System Settings.  With this tab missing, it is not possible to deselect hardware virtualization.  Further, Virtual Box does not cascade this detection to actually forcing virtualization off for the VM on execution.  This causes the VM to crash as it starts up (because the virtualization is physically not available).  My suggestion is to always allow the acceleration tab to be accessible.  Alternatively, if virtualization is physically not available, just run the VM with the option deselected, even if it is selected under the acceleration tab (in which case, the acceleration tab can remain grayed out if virtualization is off)",Tim Ellis
16750,VirtualBox GUI Crashed when cloning after upgrading to latest version,VirtualBox 5.1.22,defect,2017-05-11T14:21:19Z,2017-06-02T14:21:45Z,2017-06-02T14:21:45Z,"We upgrade the servers to CentOS Linux 6.9 2.6.32-696.1.1.el6.x86_64 with VirtualBox 5.1.22_115126_el6-1

Now when we try to clone a machine it crashes the GUI.  All machines show ""aborted"" though they are running fine and each states the VirtualBox Critical Error.  I'm attaching the error here.",Tomqwe
16805,darwin kernel crash on starting VM,VirtualBox 5.1.22,defect,2017-06-01T10:53:59Z,2017-06-05T17:29:50Z,2017-06-05T17:29:50Z,"I've got 3 crashes in sequence each time when running Windows VM, either from scratch or saved state.

One of the crash report reads this error:
{{{
panic(cpu 5 caller 0xffffff8003809f4a): ""vmx_on: unexpected return -2 from __vmxon()""@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/i386/vmx/vmx_cpu.c:198
}}}
Another two have:
{{{
panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode, registers:
panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode, registers:
}}}
It happens in 5.1.22 as well as before the upgrade.

Please find crash report details in the attachment.",bronek
16879,Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS),VirtualBox 5.1.22,defect,2017-07-06T10:11:57Z,2017-08-14T10:55:08Z,2017-08-14T10:55:08Z,"While using packer tool to automate creation of VM images I face the following errors:
{{{
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Error deleting virtual machine: VBoxManage error: VBoxManage: error: Cannot unregister the machine 'foo' while it is locked
==> virtualbox-iso: VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
==> virtualbox-iso: VBoxManage: error: Context: ""Unregister(CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))"" at line 156 of file VBoxManageMisc.cpp
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error sending boot command: VBoxManage error: VBoxManage: error: Could not send all scan codes to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component KeyboardWrap, interface IKeyboard, callee nsISupports
VBoxManage: error: Context: ""PutScancodes(ComSafeArrayAsInParam(saScancodes), &codesStored)"" at line 345 of file VBoxManageControlVM.cpp
}}}
After this happens VM enters ""Guru Meditation"" state.

I searched for more information about the error got and found https://github.com/hashicorp/packer/issues/4309 referring to https://www.virtualbox.org/changeset/64906/vbox that seems to be some attempt to fix this (?).
Anyway, https://www.virtualbox.org/changeset/64906/vbox looks not to be included in VirtualBox-5.1-5.1.22_115126_el7-1.x86_64 RPM I am using in my Centos 7.3 (judging by the lack of VboxManage keyboardputstring/keyboardputfile API added in this changeset).

Steps to reproduce:
{{{
packer build -var vm_name=foo -var no_gui=true centos-vbox.json
Packer version 1.0.0
}}}
Mapping from packer API to VBoxManage calls can be seen in attached packer debug log. ISO image used is just a minimal CentOs 7.3 image. kickstart file should not be relevant for this bug.
The bug is not deterministic, it happens once per ~4 executions.",pstrzelczak
16886,4.x -> 5.x crash,VirtualBox 5.1.22,defect,2017-07-07T22:32:30Z,2017-11-15T21:27:54Z,2017-11-15T21:27:54Z,"I updated my virtual box from 4.* to 5.*, now my virtual PCs crash when I start them from any snapshot.

P.S. Can't get log from VM.",Mikha Mikhin
16895,"Host BSOD when starting any VM on Windows 10 host, without Hyper-V",VirtualBox 5.1.22,defect,2017-07-10T16:52:16Z,2017-07-10T16:52:16Z,2017-07-10T16:52:16Z,"I have a largely-clean Windows 10 system with VirtualBox installed. When I attempt to start any VM (including a Centos 7.0 box, and a basic DOS VM), Windows 10 BSODs with `SYSTEM_SERVICE_EXCEPTION`, Bug Check Code `0x0000003b`.

I found multiple references to this being a conflict with Windows 10's own Hyper-V Virtualisation, so I have disabled the Hyper-V services and removed the feature from Windows; the BSOD still happens. I have also updated host graphics and audio drivers (just in case). I have tested VirtualBox versions 5.1.22 (last stable), preview 5.1.23, and 5.0.40 (which is known-good in my department).

Attached are the VBox.log, VBoxHardening.log for both the DOS and Centos systems, and a representative minidump. Analysis of the minidump on Superuser.com (https://superuser.com/a/1228520/82337) suggests that VMMR0.r0 has attempted to execute a Privileged Instruction.

I'm not sure if any further diagnostics would be helpful here, but please ask and I will attempt to get them for you.",Chowlett
16897,NtCreateFile failed: Unknown Status -626,VirtualBox 5.1.22,defect,2017-07-12T11:53:11Z,2017-07-24T10:01:14Z,2017-07-24T10:01:14Z,"Windows 10 Version 1703 Build 15063.413[[BR]]
Virtual Box Version 5.1.22r115126(Qt5.6.2)

The virtual machine 'AHF' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ~\Logs\VBoxHardening.log'.

{{{
Result Code: E_FAIL (0x80004005)
Component:   MachineWrap
Interface:   IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}",TheChris
16906,Unable to start Virtual Machine (exit code 0x01),VirtualBox 5.1.22,defect,2017-07-17T11:36:00Z,2017-07-25T21:57:34Z,2017-07-25T21:57:34Z,"Dear Virtual Box support,

i have a critical problem on my Windows 10 machine (64bit), without any previous advice all the Virtual Machines installed are unable to start. 
I started and used VM succesfully one day and after restarting my toshiba notebook PC i had this problem.


Here is the error reported when starting a Virtual Machine:

------

Apertura di una sessione per la Macchina Virtuale Win 7 (64-bit) non riuscita.

The virtual machine 'Win 7 (64-bit)' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Virtual Box VM\Win 7 (64-bit)\Logs\VBoxHardening.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaccia: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

----

The log of the startup are attached to this message .

Please give me some feedback about this issue.

I used VB for many years and this is first time i encouter souch a big problem.

Best regards,
Massimo Cavagni",MC77
16934,Pause or auto-snapshot on guest restart,VirtualBox 5.1.24,enhancement,2017-07-21T23:36:59Z,2017-07-24T09:16:09Z,2017-07-24T09:16:09Z,"== The Problem ==
There are some cases where it would be advantageous to automatically pause or take a snapshot of a guest that is in the process of restarting.

For example:
* Pausing during OS install to allow device removal, etc.
* Automatic snapshots during OS/software install as clean points to return to or clone.
* Pausing if there is an unexpected restart (to prevent restart loops, etc.)

Trying to do this manually often becomes a test of reflexes. It's necessary to catch the guest in the act of restarting, move focus to that window, and pause it before the guest OS takes over after restarting.

== Implementation ==
Pausing would occur immediately after the restart (on the ""Oracle"" screen).

Taking snapshots would require converting the restart into a shutdown, taking an offline snapshot, and then starting the VM again.

For the GUI, I envision an ""Action on Restart"" menu item, and sub-items to pause during the next restart, or to take snapshots during the next 1-3 restarts (as the current operation may restart the guest multiple times). A CLI implementation of those options is straightforward enough as well.

In most cases, there would seem to be no need for this setting to be stored if the VM isn't running. However, the pause setting being sticky might be useful in cases such as the third example above.",Galactic
16996,Application Error and a crash. The memory could not be read.,VirtualBox 5.1.26,defect,2017-08-10T10:23:28Z,2017-09-06T08:56:58Z,2017-09-06T08:56:58Z,During vm operation message box appears and VirtualBox.exe crashes.,Mik
16998,driver services missing,VirtualBox 5.1.26,defect,2017-08-11T05:14:01Z,2018-02-23T09:31:58Z,2018-02-23T09:31:58Z,"NtCreateFile(\Devie\VBoxDrvStub)failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 RETRIES) (rc=-101)

Make sure the kernel module has been loaded succfully.
where:supR3HardenedWinReSpawn what:3 VERR_OPEN_FAILED (-101) -file/
Device open failed. Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
",amrtin34
17000,Cumulative update for Windows 10 1703 broke Virtualbox VT-x recognition,VirtualBox 5.1.26,defect,2017-08-11T12:37:20Z,2017-09-18T19:17:38Z,2017-09-18T19:17:38Z,"On 2017-0809 around 1700EDT I upgraded my laptop with a security update for Windows 10 (https://support.microsoft.com/en-us/help/4034674/windows-10-update-kb4034674) and a security update for Adobe Flash player for windows 10 (https://support.microsoft.com/en-us/help/4034662/security-update-for-adobe-flash-player-aug-08-2017).

The following morning I attempted to power up my VM that has been running without major hiccups since mid July and got the following failure code:

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Online searches revealed that this type of problem has been encountered before.

1. https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios

I tried 
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and rebooted but problem persisted.

2. https://stackoverflow.com/questions/5482223/vt-x-is-not-available-when-i-start-my-virtual-machine

I reduced my VM's memory footprint below 4096 but when I powered it up I got a Win10 BSOD

3. https://forums.virtualbox.org/viewtopic.php?f=6&t=58820

I ran
c:\Program Files\Oracle\VirtualBox>VBoxManage.exe modifyvm CentOS-Adva-Dev --longmode off

without any noticable effect on this problem.

I confirmed my laptop's virtualization support is enabled in the bios settings.

I attempted to create another VM and noticed that my only VM guest types are 32 bit. 

I attempted to run an installation repair to my VirtualBox 5.1.26 installation without any success.

I have not tried:
1. Uninstall and reinstall VirtualBox application on my host - I have no reason to believe that this will resolve the issue

2. Rolling back the Windows security updates - this action probably carries more risk than reward.

",edwaldner
17039,OSX 10.12.6 VB 5.1.26 r117224 reproducible crash /w Kubuntu,VirtualBox 5.1.26,defect,2017-08-27T19:20:40Z,2017-08-27T19:20:40Z,2017-08-27T19:20:40Z,"
I have a MacBook Pro with OSX 10.12.6 running VB 5.1.26 r117224

The following steps will produce a hard crash/black screen reboot of OSX.

Download Kubuntu 17.04

Install with two gig, two cores, bump graphics memory to 64 meg, otherwise graphical installer won't work

Inside Kubuntu, apt update, then apt upgrade


I've watched it a couple times, seems to be during the *unpacking* of the new kernel, which strikes me as odd. Every time it just completely black screen reboots OSX, which is unusual - the OS normally stops in a graceful fashion with a notification screen.

I also use Lubuntu, which is very similar - no complaints here, just ran an apt upgrade on a fresh install, no problems.

I'm going to see if this also fails on Win8.1, will post a separate ticket if it does.",nrauhauser
17059,Add VM state saving compression level option,VirtualBox 5.1.26,enhancement,2017-09-07T05:26:19Z,2017-09-07T05:26:19Z,2017-09-07T05:26:19Z,"AFAIK, VirtualBox currently uses some default(?) value for libgzip(?) when saving and thus compressing running VM's RAM into disk. Sometimes it's needed to tune (as for me, to lower compression levels to compress VM state faster) the compression level. Peculiarly it's very highly desired feature when using SSD storage, where I/O bandwidth capability is super fast.

I see implementation as some global option for all VMs and custom trigger per VM configuration ""use global compression level when saving to disk"" / ""use X compression level when saving to disk"".
",maestro
17107,"Hello, Today I just upgrade my Vbox, and now I can't open the software. Need Help",VirtualBox 5.1.28,defect,2017-09-22T14:23:00Z,2017-09-22T14:23:00Z,2017-09-22T14:23:00Z,"Fallo al abrir una sesión para la máquina virtual Siemens Win 7 64 bit.

The device helper structure version has changed.

If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH).

Código Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Rocko
17141,"Guests hang in ""restoring snapshot"" or ""deleting snapshot""",VirtualBox 5.1.28,defect,2017-10-05T17:10:57Z,2017-10-05T17:30:02Z,2017-10-05T17:30:02Z,"On an Arch Linux host, after running some VirtualBox-related maintainence scripts that do things such as take and restore snapshots, I observe that several virtual machines are in strange states.  None of the machines are active.

{{{
deb8: ""Restoring Snapshot""
fedora: ""Aborted""
theodore: ""Deleting Snapshot""
ubu12-32: ""Deleting Snapshot""
win10x64: ""Powered off""
}}}

This happens fairly often for me.  I will attach stacktraces.",plujon
17183,Ubuntu guest on Windows host not properly shut down,VirtualBox 5.1.28,defect,2017-10-20T08:56:33Z,2018-02-27T08:03:21Z,2018-02-27T08:03:21Z,"It seems that after installing version 5.1.28, Ubuntu guest (32-bit version 16.04.3 LTS) cannot properly shutdown, and an exception is thrown. State of ubuntu guest is displayed as ""abandoned"" afterwards.",Kanaris
17211,arm64/arm hypervisor add ons,VirtualBox 5.1.30,enhancement,2017-10-26T01:35:27Z,2017-10-26T01:39:43Z,2017-10-26T01:39:43Z,"I have windows /Gentoo  getting arm64 is slightly doable 
however qtemu or aqemu and some hacking backends . 
reliability next to Zilch..  today working tomorrow updates ...s@#$ its broken.. 

say you wish to piddle with Debian 9 arm64 iso well you SOL ... or windows 10 with more Umph than an RPI-3 in 64 mode. 

anyhow , the smooth reliable Virtualbox hypervisor , just add  to Vbox-hyper-arm64 etc.. sub modules.. 

",necrose99
17215,"Guest additions command line updating fails (Linux host, Windows guest) => Obsolete",VirtualBox 5.2.0,defect,2017-10-27T09:13:59Z,2022-04-19T14:54:50Z,2022-04-19T14:54:50Z,"I have a Linux host (Ubuntu 16.04, 64 bits) and a Windows guest (Windows 7 professional, 64 bits). I try to update the guest additions using the command line.

So I issue the command (from the Linux host, with the VM guest powered on):
{{{
VBoxManage guestcontrol ""win7""  updateadditions --source /usr/share/virtualbox/VBoxGuestAdditions.iso --verbose
}}}
The command fails and I get the following output:
{{{
Updating Guest Additions ...
Using source: /usr/share/virtualbox/VBoxGuestAdditions.iso
VBoxManage: error: Could not open guest session: VERR_TIMEOUT
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestWrap, interface IGuest, callee nsISupports
VBoxManage: error: Context: ""UpdateGuestAdditions(Bstr(strSource).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aUpdateFlags), pProgress.asOutParam())"" at line 3667 of file VBoxManageGuestCtrl.cpp
}}}
I tried with Virtualbox 5.1.30 and 5.2.0 and I get the same result.

Manually updating the guest additions (withon the guest) works as expected.

And I was also able to start a program within the guest, using commands like:
{{{
VBoxManage guestcontrol ""win7"" --username my_account run --exe ""C:\Windows\System32\notepad.exe""
}}}
So, I think this issue is clearly a bug...",roland651
17296,Error in supR3HardenendWinReSpawn,VirtualBox 5.1.30,defect,2017-11-20T09:48:24Z,2018-02-27T23:27:20Z,2018-02-27T23:27:20Z,"My virtual box VMs do not start anymore, I get rc=-5640 for all VMs. I have also installed the latest version of docker toolbox (Hyper-V disabled) where the default-VM also stopped working.

Reinstallation and also rollback to version 5.1.14 did not resolve the issue.",danielguenzel
17403,Touchscreen input is not scaled to VM location on screen,VirtualBox 5.2.4,defect,2017-12-27T06:40:05Z,2017-12-27T06:40:05Z,2017-12-27T06:40:05Z,"host: Win 10 on HP Envy 14-k111nr with touchscreen (3200x1800), virtualization enabled.
guest: Android 7.1-rc1 64bit, set as Linux (Version 2.6/3.x/4.x 64 bit)


Problem: When I dont disable mouse-integration i can only control the cursor with touch interactions. Also cursor only moveable by mouse when clicked - otherwise it just wouldnt move. 
When I disable it I can ""use"" the touchscreen ""nativly"". But thats the problem because it seems that it just reads out the coordinates of the touch input rather than the position in the VM-machine. It doesnt bother where the VM-""display"" is located on the desktop. If i push at 3000;1000 the VM will detect the click on 3000;1000 even though it only covers the area until 2000;500.

The solution would be to detect the VM window if not 100% fullscreen and translate the touch input postition to the guest screen. ",FUKU
17415,VirtualBox - Error In supR3HardenedWinReSpawn when the starting the VM,VirtualBox 5.0.40,defect,2018-01-03T16:40:43Z,2018-01-03T18:38:49Z,2018-01-03T18:38:49Z,"I am using VirtualBox 5.0.40 and I have created a VM which has Windows XPMode configured.
When I am starting the VM, I am getting the below exception pop up with the error message:

VirtualBox - Error In supR3HardenedWinReSpawn

(rc=-5640)

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn 
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE
(-5640) - Process Verification Failure: 
The process has more than one thread.

When I click the OK, it brings another exception pop up with the below error message:

VirtualBox - Error

Failed to open a session for the virtual machine 'My Guest Machine'

Details
The virtual machine 'My Guest Machine' has terminated unexpectedly during startup with exit code 1(0x1).
More details may be available in 'C:\Users\myuser\VirtualBox VMs\My Guest Machine\Logs\VBoxHardening.log'. 

I clicked OK to close the window.

But when I start the VM again, it launches successfully with out any error.
But at times when I start again after the above mentioned error, it is not launching and give the same error.
This behavior is inconsistent.

Could you please suggest me any possible fix to avoid this error?",PbuHCL
17432,After upgrade 5.1.30 it never worked again,VirtualBox 5.1.30,defect,2018-01-08T18:48:23Z,2018-01-08T19:03:22Z,2018-01-08T19:03:22Z,"Long time using VirtualBox and after install upgrade 5.1.30 it left working again. I upgrade to 5.2 version and the same result with a different problem. Each time updated Extension Pack, but nothing.",FGGarcia
17448,Python bindings for Python 3.x fail on sys.abiflag() because of module and init name mismatch,VirtualBox 5.2.4,defect,2018-01-10T21:14:13Z,2018-01-10T21:14:13Z,2018-01-10T21:14:13Z,"Reporting an issue where if `sys.abiflags() != ''` you will not be able to import vboxapi on Python 3.x systems because of how the PyInit function is named.

Python requires .so modules to have an exported function with the name `PyInit_[MODULE NAME]` and in this case when the user installed via the .deb
file for Ubuntu 16.04 the .so file was named `VBoxPython3_5m.so` but when examining the exported function names we received only `PyInit_VBoxPython3_5` (note that there is no `m` at the end).

This mismatch makes it tough for users to install vboxapi without having to take additional steps such as renaming their .so file to not include the `m`.

Source file where this PyInit function is generated: https://www.virtualbox.org/svn/vbox/trunk/src/libs/xpcom18a4/python/src/module/_xpcom.cpp

See https://github.com/mjdorma/pyvbox/issues/102 for the original issue reported by another user.",SethMichaelLarson
17477,Compacting VDI file resulting in corrupt file system on High Sierra (APFS),VirtualBox 5.2.6,defect,2018-01-18T14:45:48Z,2019-09-08T01:07:18Z,2019-09-08T01:07:18Z,"I tried to compact a VirtualBox VDI file (Windows 10 Guest) with this commands on High Sierra 10.13.2 (17C205):

 1. VBoxManage modifymedium disk XXX.vdi --compact
 2. VBoxManage modifyhd XXX.vdi --compact

Both commands won´t finish and resulting in an corrupt file system (APFS) on the host.

After that I´m not able to show the VDI file or navigate to the VM folder which contains the VDI file. Finder crashes if I want to do that, Terminal also crahses and Time Machine Backups can´t finish if Time Machine passes that folder for backups...

I had to boot into recovery mode to repair the filesystem of my main Macintosh HD, after that I was able to remove the corrupt VDI file...

This is the second time I had that issue, fortunately I was able to repair my file system this time, the last time with macOS High Sierra 10.13.0 and VirtualBox 5.1.30 I ending with and corrupt file system and was not able to repair it, this means I completely had to restore my Mac...

",DanielH
17501,Ubuntu guest fails after waking from windows 10 host sleep,VirtualBox 5.2.6,defect,2018-01-26T17:46:47Z,2018-01-26T17:46:47Z,2018-01-26T17:46:47Z,"Hi, 
I have the latest version of VirtualBox -- 5.2.6 running on a windows 10 host.   I've tried a couple of different guest OSes, Fedora Core 27 and Ubuntu 16.04.   Both fail to survive a sleep-wake-cycle on the Windows 10 guest.    

I've tried many things from previous bug reports, more memory, more video memory.   Also with and without 3D acceleration and with and without hardware virtuatization, etc.  

Occasionally, the guest will survive one sleep-wake cycle but will slip into  'Guru Mediation' after the second cycle.  

I have also installed the latest guest additions on the host as well. 

I'll attach the virtualbox log file and the virtualbox hardening log file.  


Please advise. 
Thanks,
Jeff
",jmcdonal
17516,Ubuntu Virtual Machine Aborts,VirtualBox 5.2.6,defect,2018-02-01T13:17:38Z,2018-02-01T13:17:38Z,2018-02-01T13:17:38Z,"I have created an Ubuntu virtual machine on my Windows 10 machine using version 5.2.6 with AddOns version 5.2.7.  I use this Ubuntu VM to connect, via vnc, to a headless ubuntu server running x11vnc server.  Prior to the 5.2.6 version, this setup worked flawlessly.  With 5.2.6, it continually aborts.  Prior to doing so, the cursor flickers rapidly, and the display is unresponsive.",kpenrose
17526,Memory exception,VirtualBox 5.2.6,defect,2018-02-05T14:01:03Z,2018-02-05T16:35:56Z,2018-02-05T16:35:56Z,Get an error message that program is trying to access protected memory location 0x0000000000000040 and on click of OK button guest session ends.,kpenrose
17527,appcrash virtualbox 5.2.6 on win7 32 bit,VirtualBox 5.2.6,defect,2018-02-05T14:02:00Z,2018-02-28T16:20:38Z,2018-02-28T16:20:38Z,"Hello kindly help us solve the application crash every time we press on ""New"" to create a new Machine. We are using win 7 32bit..

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	5.2.6.20293
  Application Timestamp:	5a5cc3df
  Fault Module Name:	VirtualBox.dll
  Fault Module Version:	5.2.6.20293
  Fault Module Timestamp:	5a5cc3f2
  Exception Code:	c0000005
  Exception Offset:	001edcd7
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

",reviewsarl
17544,"VM not responsive after hibernation: Mac OS host, Ubuntu Linux Guest",VirtualBox 5.2.6,defect,2018-02-13T23:13:30Z,2018-02-15T08:52:11Z,2018-02-15T08:52:11Z,"This is the version info:

Version 5.2.6 r120293 (Qt5.6.3)

Host OS:  Mac OS, 10.12.6

Guest OS: Ubuntu 16.04 64bit

After a period of hibernation of the host os, the vm becomes not responsive. Though the VM looks like where it is left before hibernation, any actions including clicking and  keyboarding can not make it work.  Power-Off is the only way to kill the VM and start it again.",JayyCee
17551,Error relaunching VirtualBox process : 5,VirtualBox 5.2.6,defect,2018-02-19T13:58:42Z,2018-02-19T15:36:29Z,2018-02-19T15:36:29Z,"VirtualBox crash during Windows 2012 server installation on new VM. Then get an error message when i was trying to restart VM.
",cbr45
17575,macos - virtualbox manager window toolbar,VirtualBox 5.2.6,defect,2018-02-28T16:17:29Z,2018-02-28T16:17:29Z,2018-02-28T16:17:29Z,"Hi all, i have searched about something this but, could not find anything yet.  So i created new, but you are able to merge-join this already open and releated one.

I attached a screenshot.  As far as i remember this problem has been there from the first release of 5.2.

As you can see from the attachment,
- toolbar is there, over the guest vm item
- toolbar's buttons are not visible but functional, so you can click one of it and execute the releated command
- minimize, maximize, window change etc does not fix or affect it
- sometimes it start without toolbar, but when you select and run a command for one guest item then toolbar is comming again with same problematic state.
  ",AOZKESEK
17601,Error when loading VM,VirtualBox 5.2.6,defect,2018-03-07T09:08:09Z,2018-04-17T13:42:01Z,2018-04-17T13:42:01Z,"Hi
i have error on VBOX when i try to run VM 
The error is 
(rc=-5640)
Where supR3HardenedWinReSpawn What :1 VERR_SUP_VP_THREAD_NOT_ALONE(-5640) - Process Verification Failure The Process have more than one thread.

how can i fix this issue it happen to Laptop and Desktop IBM hardware VT enabled 
we try to install the new Ver and try to install old ver 
we try to go back to Windows 10 1607 
Please help 

Thank you for the help",yotama
17618,Use all host threads to compress/decompress VM save state to speedup,VirtualBox 5.2.8,enhancement,2018-03-13T05:29:32Z,2018-03-13T05:29:32Z,2018-03-13T05:29:32Z,"Use all host threads to compress/decompress VM save state to speedup.

It would be N times faster to do the operations.",maestro
17660,Critical Error on Boot,VirtualBox 5.2.8,defect,2018-04-02T21:28:56Z,2018-04-19T20:47:18Z,2018-04-19T20:47:18Z,"can not star my virtual machine, I recceive a critical error and cirtual machine stops.",joaocamara
17679,Error on trying to run VM in headless mode.,VirtualBox 5.2.8,defect,2018-04-12T13:02:55Z,2022-09-29T17:32:06Z,2022-09-29T17:32:06Z,"Host: Windows 10 Pro x64
Quest: Windows XP x32

All going norm. VM works and launches.
Problem is error when attempt to launch VM in headless mode.

Error:
Не удалось открыть сессию для виртуальной машины VWXP.
The virtual machine 'VWXP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\User\VirtualBox VMs\VWXP\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}",UnclWish
17711,VMs no longer start from saved state,VirtualBox 5.2.10,defect,2018-04-25T11:23:17Z,2018-04-26T08:03:43Z,2018-04-26T08:03:43Z,"Since I've upgraded to 5.2.10r122088 (Ubuntu 16 LTS, Kernel: 4.4.0-121-generic), I'm no longer able to start my VMs from saved state:

{{{
Waiting for VM ""VM_W10"" to power on...
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
}}}

The vbox log (attached) doesn't say much.
This happens on all ~150 vms across all 10 vbox hosts I have.",LennyHers
17834,PGM: Failed to procure handy pages; rc=VERR_GMM_HIT_VM_ACCOUNT_LIMIT,VirtualBox 5.2.2,defect,2018-06-22T04:36:45Z,2018-06-22T04:36:45Z,2018-06-22T04:36:45Z,"Bug reproduce:
- Set guest memory balloon to maximum value
- Power on VM and make it crash, Ex: driver failure
- Windows guest will be restarted after crash
- Error will be occurred while VM restart

Error cause:
- When guest crashed, ballooned pages are not cleanup

Suggest fix:
- Cleanup all ballooned pages when VM state change to RESETTING",AnhNN
17845,"Managing groups of VMs will not be synchronized in filesystem, VM stay on their location",VirtualBox 5.2.12,defect,2018-07-01T10:02:34Z,2018-07-01T10:02:34Z,2018-07-01T10:02:34Z,"Managing of groups (new group, move VM to new group, add VM to group) will not synchronized in filesystem.

Steps: 
- VBox running without any Virtual Machines (VM)
- Create on VM: ""vm1""
- ""Group"" this ""vm1"": Group ""New Group"" will created, also in Filesystem (FS) a directory ""New Group"" is created, directroy ""vm1"" is now inside ""New Group""
- Rename ""New Group"" to ""grp1"": ""vm1"" is displayed in group ""grp1"", in FS directory is renamed to ""grp1"", ""vm1"" is inside ""grp1"": OK 
- Clone ""vm1"" to ""vm2"": ""vm2"" is displayed outside ""grp1"", directory ""vm2"" is created outside ""grp1"" (parent directory)
- ""Group"" ""vm2"" to a second group ""grp2"" as before: Group ""grp2"" is displayed with ""vm2"" inside. But no directory for group ""grp2"" is created, ""vm2"" is still outside.
- Move ""vm2"" to ""grp1"" (drag an drop): ""grp2"" is no longer displayed, ""grp1"" has members ""vm1"", ""vm2"". In FS ""vm2"" is still outside of ""grp1""
- ""Add new VM"" in group ""grp1"": Displayed in ""grp1"", but in FS it is created outside of ""grp1"".

Summary:
Only one group will be managed in filesystem. Display and Filesystem are not synchornized.
The first VM of the group will be moved inside group directory.
No further group directories will be created.
Other vms (by clone, by add, by move) will stay outside (in the parent-directory).
",TKinVBOX
17849,Error Relaunching VirtualBox VM Process:5,VirtualBox 5.2.14,defect,2018-07-02T16:22:53Z,2020-08-13T00:54:53Z,2020-08-13T00:54:53Z,Cannot start any VM of Virtual Box,Andres0910
17909,weird time adjustment,VirtualBox 5.1.38,defect,2018-08-02T08:39:40Z,2018-08-02T08:39:40Z,2018-08-02T08:39:40Z,"Hello. I use ""VirtualBox Graphical User Interface Version 5.1.38_Ubuntu r122592 © 2004-2018 Oracle Corporation (Qt5.5.1)"". And using Windows XP on it. I use my own program to track the accuracy of the time, and sometimes I notice that Windows is weirdly tuning the time. For example I attach today's graph of adjustment.

It can be seen that the detuning runs on some kind of sinusoid, and then at some point it goes out on a flat line. Then, when the detuning builds up, it for some reason again goes to the sinusoid of an unacceptably large amplitude, and then again sets the normal time. On the vertical axis - milliseconds. That is, during these sinusoid detuning reaches 15 seconds - it's terrible, I think. 

I tried to disable the vm module on WindowsXP, and the tuning is disabled, but the clipboard between vm and my machine stops working as well - thats not good.

So, I have a couple of questions:

1) Why is there such a strange sinusoid used in the time adjustment (which uses the SetSystemTimeAdjustment) instead of a rapidly decaying exponent?

2) can I disable this strange time adjustment without disabling the clipboard?

",daybit
18036,MachineTools toolbar buttons disappear after starting VM from Windows Explorer,VirtualBox 5.2.18,defect,2018-10-07T12:12:30Z,2018-10-09T19:16:36Z,2018-10-09T19:16:36Z,"Normally in the VM VirtualBox Manager (VirtualBox.exe) I have the Machine Tools toolbar showing both Details and Snapshots. However if I run a VM by double-clicking the .vbox file in Windows Explorer when VirtualBox.exe is not running, next time I run VirtualBox.exe those buttons are not showing on the toolbar. In particular, before I have in VirtualBox.xml
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""Details,Snapshots""/>
but after, I have
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""None""/>",mf86a
18110,Unable to save window state,VirtualBox 5.2.20,defect,2018-11-06T03:23:40Z,2018-11-06T07:31:53Z,2018-11-06T07:31:53Z,"On the KALI system, the state of the window could not be saved. Every time you click the close button on the window, after you close the program, you need to right-click the display toolbar.",meiying
18165,Problem to open all VM's,VirtualBox 5.2.22,defect,2018-12-03T00:12:53Z,2018-12-03T05:55:08Z,2018-12-03T05:55:08Z,I have in Virtual box two VM (Linux Ubuntu and Windows 10) but all the VM don't open . I have an error but I can't resolve it. [[Image()]]Can i have one help ??,Cris96
18208,VMs with a PIPE in the name cannot be moved in groups,VirtualBox 6.0.0,defect,2018-12-20T09:58:26Z,2018-12-23T17:46:13Z,2018-12-23T17:46:13Z,"If a machine has a PIPE (|) in its name it cannot be moved in or out a group because the config file of the machine (vbox) cannot be edited.

If I rename the VM and replace the pipe with another character (i.e. a minus or a space) it works perfectly.",KevinW
18287,windows 10 x64 guest crashes (vb restarts the guest windows),VirtualBox 6.0.0,defect,2019-01-08T12:16:53Z,2019-01-08T14:44:24Z,2019-01-08T14:44:24Z,"so I have a windows x64 host and a windows x64 guest, from time to time the os of the guest reboots for no reason (no error shown)",xhums1
18307,VM Hang during installing of Centos,VirtualBox 6.0.0,defect,2019-01-13T08:10:48Z,2019-01-14T08:13:22Z,2019-01-14T08:13:22Z,"Hello Team,
i created new VM and attach the Centos 7 ISO file
the installation screen appears after that it hang 
i tried to change the display settings as i suspect its video card issue 
but its the same issue 
i attached the logs 
thanks for support 
regards

",Alaa
18309,VirtualVox 6.0.0-127566 will not start VMs under latest Windows 10 update,VirtualBox 6.0.0,defect,2019-01-13T23:37:04Z,2019-01-14T00:06:21Z,2019-01-14T00:06:21Z,"When trying to start a VM it fails with:

----------------
The virtual machine 'CentOS 7.5' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\${user}\VirtualBox VMs\CentOS 7.5\Logs\VBoxHardening.log'.
-----------------

Looking in that file I find:

------------------
2598.95c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox'
2598.95c: System32:  \Device\HarddiskVolume3\Windows\System32
2598.95c: WinSxS:    \Device\HarddiskVolume3\Windows\WinSxS
2598.95c: KnownDllPath: C:\WINDOWS\System32
2598.95c: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2598.95c: supR3HardenedWinReadErrorInfoDevice: 'Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)'
2598.95c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3)
2598.95c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
41f8.421c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5633 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
41f8.421c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3)
41f8.421c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff)
VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
------------------

Here is the info from that file about my version of Windows 10. It was updated last Tuesday.

-------------------
41f8.421c: Log file opened: 6.0.0r127566 g_hStartupLog=0000000000000070 g_uNtVerCombined=0xa0456300
41f8.421c: \SystemRoot\System32\ntdll.dll:
41f8.421c:     CreationTime:    2019-01-10T02:36:52.431995500Z
41f8.421c:     LastWriteTime:   2019-01-10T02:36:52.457392000Z
41f8.421c:     ChangeTime:      2019-01-10T03:35:31.327390500Z
41f8.421c:     FileAttributes:  0x20
41f8.421c:     Size:            0x1e7010
41f8.421c:     NT Headers:      0xe0
41f8.421c:     Timestamp:       0xe8b54827
41f8.421c:     Machine:         0x8664 - amd64
41f8.421c:     Timestamp:       0xe8b54827
41f8.421c:     Image Version:   10.0
41f8.421c:     SizeOfImage:     0x1ed000 (2019328)
41f8.421c:     Resource Dir:    0x17d000 LB 0x6ea08
41f8.421c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
41f8.421c:     [Raw version resource data: 0x17d0f0 LB 0x380, codepage 0x0 (reserved 0x0)]
41f8.421c:     ProductName:     Microsoft® Windows® Operating System
41f8.421c:     ProductVersion:  10.0.17763.194
41f8.421c:     FileVersion:     10.0.17763.194 (WinBuild.160101.0800)
41f8.421c:     FileDescription: NT Layer DLL
41f8.421c: \SystemRoot\System32\kernel32.dll:
41f8.421c:     CreationTime:    2018-09-15T07:28:44.342269900Z
41f8.421c:     LastWriteTime:   2018-09-15T07:28:44.342269900Z
41f8.421c:     ChangeTime:      2019-01-10T03:35:31.154027900Z
41f8.421c:     FileAttributes:  0x20
41f8.421c:     Size:            0xb1380
------------------------",Richard Sharpe
18425,Spontanious guest hanging after rollback,VirtualBox 6.0.4,defect,2019-02-11T08:55:10Z,2019-02-11T08:55:10Z,2019-02-11T08:55:10Z,"After a number of rollbacks to a certain live snapshot the guest (Ubuntu Server 16.04) seems to restore its state but becomes totally unresponsive. It just hangs on the prompt, the video doesn't change at all (even the cursor doesn't blink), and pressing any keyboard keys doesn't have any effect. Htop also shows that one of the cores is loaded 100% with the VBoxHeadless process. You may reboot the guest forcefully and it starts just fine. It's just I have to do a lot of rollbacks to live snapshots automatically that this occasional freeze bugs me big time.

P.S. If that makes any difference - I'm doing headless start instead of normal start

P.S.S. Bug seems to be very occasional - once in a few dozen times maybe
",CIDJEY
18445,Problem when starting my virtual machin,VirtualBox 5.2.18,defect,2019-02-21T13:00:54Z,2019-02-21T16:22:15Z,2019-02-21T16:22:15Z,"i've downloaded an i386 version of Kali linux but when i start it in my virtual machin, it doesn't work.
It was giving me this error: this kernel requires the following features not present on the CPU:pae but i've been able to fix it and now when i start my virtual machin it tells me that it find a critical error when executing the virtual machin and the virtual machin has stopped working. ",Elbro
18452,"rc=-1908 , suplibOsInit : 3 ENOENT",VirtualBox 6.0.4,defect,2019-02-25T16:13:35Z,2019-02-25T23:12:08Z,2019-02-25T23:12:08Z,"Version 6.0.4 r128413 (Qt5.6.3)
+
Windows 10 Enterprise (Evaluation - Build 201812) 20 GB download
=

Failed to open a session for the virtual machine WinDev1811Eval.

The virtual machine 'WinDev1811Eval' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

??
",A Denevér
18464,Virtual box 6.x hangs VM,VirtualBox 6.0.4,defect,2019-03-01T08:22:31Z,2019-03-01T11:17:35Z,2019-03-01T11:17:35Z,"Hello.
I'm running VirtualBox 6.0.4 in the following environment:
Host: Ms-Win10_64
Guests: Ms-Win10_64 Ms-Win7_64

After update to 6.x release, VM hangs after a few minutes ! ",Kotekino
18508,Re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset,VirtualBox 6.0.4,defect,2019-03-19T17:40:12Z,2019-04-18T19:06:00Z,2019-04-18T19:06:00Z,"System Information:
 * Host: Windows 10 Enterprise:
 * VirtualBox 6.0.4
 * VirtualBox Extension Pack 6.0.4
 * Guest: Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso)
 * VirtualBox Guest Additions: 6.0.4

Issue:
Upon installation of the VirtualBox Guest Additions 6.0.4 in Ubuntu 18.04.2 whenever you attempt to re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset.

Steps to Reproduce:
I have tested this various times by performing the following:
1. Performing a fresh installation of Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso) in VirtualBox with the following specifications:
 * Base Memory:  2048 MB (2 GB)
 * Processors: 2
 * Disk Space: 25 GB
 * Encryption Enabled: Yes (via the graphical Ubuntu installer prompts)

2. Navigating to “Devices -> Insert Guest Additions CD image”

3. Ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

4. Received the “Please install the gcc make perl packages from your distribution.” error message

5. Ran the “sudo apt-get update” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

6. Ran the “sudo apt-get install build-essential gcc make perl dkms” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

7. Ran the “reboot” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

8. Re-ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

9. Attempted to re-size the VirtualBox Ubuntu Guest Window which created a black Ubuntu Guest screen

10. Navigate to “Machine -> Reset”

If I ever re-attempted to re-size the VirtualBox Ubuntu Guest Window then it would re-create black Ubuntu Guest screen

To resolve this issue I would manual uninstall VirtualBox Guest Additions 6.0.4 from the Ubuntu Guest via the Command Line Interface (CLI) by performing the following steps:
 1) Ensure the “Guest Additions CD image” is still mounted to the Ubuntu Guest
 2) Run the “sudo sh /<USERNAME>/media/<VIRUTALBOXNAME>/VBoxLinuxAdditions.run uninstall” command

Outcome:
This issue needs to be resolved so that one can re-size the a Ubuntu 18.04.2+ Guest window",elyons
18525,Cannot launch Virtual Machine - Argument aWidth is invalid,VirtualBox 6.0.4,defect,2019-03-27T11:06:59Z,2019-03-27T11:06:59Z,2019-03-27T11:06:59Z,"I can not launch any of my former created or new created VMs.

VirtualBox Guru Medition Error is showing up. Fatal Error (my translation from german text showing up)

Host: Ubuntu 18.04
Guest: any

Ataching log to investigate error.

Thanks for good work!",Mate
18526,Error warning at the boot,VirtualBox 6.0.4,defect,2019-03-27T13:37:20Z,2019-03-27T13:37:20Z,2019-03-27T13:37:20Z,"When i start the system, i get a warning about a bug and an option to ignore it  or turn of the machine. If i ignore it i cant capture input on my system and when i press right ctrl to do so it does nothing, just highlights the input capture botton in the bottom left corner.",ceca
18713,Error when going to full screen Windows 10 (Host+F),VirtualBox 6.0.8,defect,2019-06-17T09:43:57Z,2019-06-17T09:43:57Z,2019-06-17T09:43:57Z,"When I go from reduced to full screen I loose the precision of the mouse pointer and sometimes no keyboard.

To get the keyboard again I go to the bottom menu use the menu line full screen line twice (Host+F). Sometimes I get the keyboard response again sometimes I have to do it once more.

The shift of the mouse pointer works immediately when using Host+F. The mouse pointer is shifted from about the size of a menu-bar only vertically.",alainsc11
18728,ntoskrnl.exe+939a0  error when i started virtual machines,VirtualBox 6.0.8,defect,2019-06-26T16:01:36Z,2019-06-26T16:01:36Z,2019-06-26T16:01:36Z,my virtualbox crash my windows7 when i start any virtual machine,luizprogrammer
18788,Für die virtuelle Maschine WindowsXP konnte keine neue Sitzung eröffnet werden.,VirtualBox 6.0.10,defect,2019-07-24T20:42:56Z,2019-07-25T09:10:23Z,2019-07-25T09:10:23Z,"Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",burghard007
18839,Guest VMs will only start headless,VirtualBox 6.0.10,defect,2019-08-15T22:06:46Z,2019-08-18T21:17:40Z,2019-08-18T21:17:40Z,"After upgrading from VirtualBox5 to VirtualBox6 none of my existing VMs will start unless I choose the ""Headless Start"" option from the dropdown menu.

Once a VM is running I'm able to bring up the GUI by clicking on the ""Show"" button.",nthexwn
18847,win10 guest on opensuse 15.1 host crashes on saving session,VirtualBox 6.0.10,defect,2019-08-16T21:32:36Z,2019-08-17T09:19:18Z,2019-08-17T09:19:18Z,"When trying to save a session with a win10 guest vbox 6.0.10 crashes with segmentation fault after about 75% of the progress bar.
After rollback to vbox 6.0.8 everything works nicely.

With other guests (winxp, win7, opensuse) this problem did not occur. It is specific to this one w10 vmachine.
vbox does not provide a proper post mortem report when it crashes and says so.",andreas366
19012,VERR_CFGM_VALUE_NOT_FOUND on boot.,VirtualBox 6.0.12,defect,2019-10-13T20:03:29Z,2019-10-16T03:34:08Z,2019-10-16T03:34:08Z,"Using VirtualBox version 6.1.0_BETA1 r133315. VM crashed on guest shutdown and now won't boot, throws ""Failed to construct 'efi'/0! VERR_CFGM_VALUE_NOT_FOUND (-2103) - Value not found."" on boot.

Logs: https://pastebin.com/sBQjAhfY

vbox: https://pastebin.com/HLNQWz4S",DeezNutz
19063,Multiple VBoxSVC processes on Linux host,VirtualBox 5.2.32,defect,2019-11-05T10:01:27Z,2019-11-05T10:01:27Z,2019-11-05T10:01:27Z,"Hello,

I use VirtualBox on headless Linux server.

From time to time I get second VBoxSVC process running:
{{{
#: ps aufx | grep VBoxSVC
jenkins   6445  0.0  0.0  14856  1040 pts/0    S+   09:19   0:00              \_ grep VBoxSVC
jenkins  19100  2.2  0.0 1077660 84388 ?       Sl   Oct17 604:18 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
jenkins  27511  1.7  0.0 875548 28544 ?        Sl   Nov04  15:58 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}
I have to kill processes every time I get this issue.
All VBoxHeadless processes always start by user jenkins.
/tmp permissions: drwxrwxrwt  root root
{{{
#: ls -la /tmp/
drwx------  2 jenkins jenkins  4096 Nov  4 18:14 .vbox-jenkins-ipc

#: ls -l /tmp/.vbox-jenkins-ipc/
srwx------ 1 jenkins jenkins 0 Nov  4 18:14 ipcd
-rw------- 1 jenkins jenkins 6 Nov  4 18:14 lock
}}}

User jenkins is in vboxusers group.

Version: 5.2.32r132073.

Host: Ubuntu 18.04.3 LTS",mgubanov
19194,Cursor Problems,VirtualBox 5.2.32,defect,2020-01-02T11:00:16Z,2020-01-02T11:00:16Z,2020-01-02T11:00:16Z,"Dear Admins,

There is a problem with the cursor where every time I try to use it on the VM it just does not work and the VM is Windows Server 2008. My host operating system is Windows 7",PoppyFamousOfficial
19224,get_Machines not working in 6.1 API,VirtualBox 6.1.0,defect,2020-01-15T04:55:23Z,2020-01-15T04:55:23Z,2020-01-15T04:55:23Z,"Originally posted to forum (here: https://forums.virtualbox.org/viewtopic.php?f=34&t=96233), lodging as a bug report since not resolved....

---

I'm the developer of VBoxHeadlessTray (see here: https://www.toptensoftware.com/vboxheadlesstray). I'm trying to get it working with the latest 6.1 SDK but I'm finding that after calling get_Machines and going through the returned array, the IUnknown for the objects are returned correctly from SafeArrayGetElement, however calling QueryInterface for IMachine fails with E_NOINTERFACE.

The IID_IMachine I'm using is {85632C68-B5BB-4316-A900-5EB28D3413DF}

Running on Windows 10, guest OS is not applicable.
",toptensoftware
19264,Crash when 'un-pausing' paused VM on Win10 host,VirtualBox 6.1.2,defect,2020-01-24T22:01:25Z,2020-01-24T22:01:25Z,2020-01-24T22:01:25Z,"I usually have 1 or 2 guests open on a Win10 host. When I'm not using the host system, I suspend or hibernate it. In addition, I manually pause a VM when not using it, in order to save host resources.

Sometimes I get crashes:
- I manually want to resume a paused VM. Crash! I then do a normal shutdown of the other VM as guest user (start button). The second VM crashes too. Conclusion: It's probably not a problem of a single VM instance, but rather of some component common to all guests.

- I suspend/resume the Windows host. On resume, I immediately get a VM crash, presumable because vbox does an implicit pause/resume of a VM.

These things happen with some probability. I can't reproduce it reliably. On vbox 6.0.12 the probability was so low that I didn't really mind. With 6.0.14 and 6.0.16 the probability seemed much higher, so I didn't use them. Now I have switched to 6.1.2 r135662 (Qt5.6.2) and I get it quite often.

I have already described my problems in https://forums.virtualbox.org/viewtopic.php?f=6&t=96538

I'm reporting now a case that seems to be typical. Here is what I did:


------------------------------------
1. Start Ubuntu guest.
2. Start WinXP guest.
3. Manually pause the Ubuntu, while WinXP keeps running.
4. Put host (Win 10) asleep.
5. Wake up the host. On wakeup, I immediately get a message notifying me of a VM crash. It turns out that the WinXP guest is gone, the paused Ubuntu guest is still there.
6. I try to manually resume the paused Ubuntu, but it crashes immediately.
------------------------------------

I attach logs of both VMs.
The following lines in the logs may be of interest:

20:58:02.032649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000163c!!! (Log of Ubuntu guest)

18:34:20.151649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002e00!!! (Log of WinXP guest)
",ueli
19298,Frequent crash when suspending virtual machine,VirtualBox 6.1.2,defect,2020-02-10T09:36:41Z,2020-02-10T13:24:27Z,2020-02-10T13:24:27Z,"Most of the time when I pause (Host+P) my Linux virtual machines, VirtualBox crashes.
This behavior seems to getting worse with every new release.
I can't really remember when this started, but I'm pretty sure that I never had the issue with versions before 6.0.

After every crash, I see exception ""rtR3WinUnhandledXcptFilter caught an exception on thread"" in the log file.
I attached two of them.
",didier.martiny
19302,Mouse support fails,VirtualBox 6.0.16,defect,2020-02-12T13:48:54Z,2021-08-13T06:17:00Z,2021-08-13T06:17:00Z,"I've come across this really odd bug with my guest Kali Linux (2019.2, 2019.4 and 2020.1; all had the latest guest additions installed), where mouse support randomly fails.

I can move the cursor. The keyboard works perfectly fine but I can't click anything with the mouse. The really odd thing is, that if I use the menu key (or application key) on the keyboard, the targeted application opens the right-click menu. In this menu, the mouse works again as expected. I've captured a short clip showing the issue. Mouse clicks are not shown, but I've clicked on every button/menu in the clip, when I hover over them.",GarlicCheese
19340,VMSVGA does not allow to resize guest display in GNU/Linux,VirtualBox 6.1.4,defect,2020-02-23T17:52:24Z,2021-11-16T18:20:47Z,2021-11-16T18:20:47Z,"In this case the host and guest are same OS: 64-bit Linux Mint 19.3 MATE.

This error has been since VMSVGA came out and it seems that this is still not fixed. So it is not just VirtualBox 6.1.4 issue but much older one and exist in many former VirtualBox versions.

Graphics controller in VirtualBox machine settings
* in case of GNU/Linux by default VMSVGA 
* in case of MS Windows by default VBoxSVGA

'''The truth is that VMSVGA does not allow to resize guest display in GNU/Linux.''' I have to adjust display settings manually in Linux in order to resize display.
When using VBoxSVGA then guest resizing works in GNU/Linux but ''Invalid settings detected'' message is shown in virtual machine (VM) settings that suggest to use VMSVGA unless I have reason to not use. Well - currently I have reason as VMSVGA does not work properly.

Also in case of VBoxSVGA the resizing clutter appears - I need to maximize VM window and back in order to get guest display resizing work properly. This has to be done after every time I wake up my laptop from sleep or start the VM first time.

At the same time in case of MS Windows the VBoxSVGA is chosen by default which works also in case of MS Windows. Actually when to choose VMSVGA in case of MS Windows then you cannot start VM as it is considered invalid setting. Well - no need as VBoxSVGA works.

My proposal: either get VMSVGA to work properly in case of any supported guest OS or remove it permanently from VirtualBox.",Edmund Laugasson
19370,On power off error at line 580 in VBoxManageControlVM.cpp in 6.0.18,VirtualBox 6.0.18,defect,2020-03-02T09:57:22Z,2020-08-10T12:19:29Z,2020-08-10T12:19:29Z,"I have automatic test system based on VirtualBox, which in infinite loop test VMs, for instance for power off. And now I see some rare error when power off VM. The error may be rare, but in the night run I got it twice. Looked like error at line 580 in VBoxManageControlVM.cpp. I didn't saw such error in 6.0.16. Screenshots are attached.",Olleg
19381,Virtual box keeps crashin during startup of virtual OS,VirtualBox 6.1.4,defect,2020-03-05T10:47:23Z,2020-04-05T10:10:55Z,2020-04-05T10:10:55Z,"I have a fedora OS (tried with fedora 29,30,and 31). I have been using mac Os Mojave throughout. However, recently the OS can't be started and I get the following crash report with the erro reading '''Failed to open a session for the virtual machine fedora'''

'''Failed to open a session for the virtual machine fedora.

The virtual machine 'fedora' has terminated unexpectedly during startup because of signal 11.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

'''",Anky
19448,VBoxManager (CLI) startvm fails for aborted images,VirtualBox 6.1.4,defect,2020-03-30T17:18:45Z,2020-03-30T17:18:45Z,2020-03-30T17:18:45Z,"CLI version:
    Oracle VM VirtualBox Command Line Management Interface Version 6.1.4

Steps:
    With an image that is in the ""aborted"" state do:
    VBoxManage startvm ${MY_IMAGE_GUID} --type headless

Expected:
    Start proceeds as if the vm was in the ""powered off"" state.

Actual:
    VBoxManage: error: The VM session was aborted
    VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession",thirtytwobits
19487,macOS 10.15.4 - VM hang if allocated more than 6 CPU or > 32Gb of memory,VirtualBox 6.1.4,defect,2020-04-14T13:57:49Z,2020-04-14T13:57:49Z,2020-04-14T13:57:49Z,Installed VirtualBox 6.1.4 and extensions on MacOS Catalina 10.15.4. Created VM through vagrant (macinbox) or via ISO and VM will hang if 32Gb or more memory allocated to VM or if 6 logical cores (out of 12 on a 6 physical core MacMini 2018) are allocated to VM. Never starts boot of machine past initial EFI startup. Reducing to 32700Mb or 6 cores and the machine starts up successfully.,nycnewman
19497,Feture request: minimize the virtualbox machine window when the guest OS powers off its virtual screen,VirtualBox 6.0.14,enhancement,2020-04-15T23:32:38Z,2020-04-16T01:53:18Z,2020-04-16T01:53:18Z,"Hello,

my guest ubuntu OS always keeps saying (in the background) that it's unable to lock screen while I have a virtualbox machine in the foreground. Well in a way that is a feature I understand, but also as it hinders security (host OS is not locking when there's no keyboard and no mouse activity and a virtualbox guest is in the foreground) it is an antifeature as well. As a solution which would make this a feature without any drawbacks I suggest you to minimize the guest OS window (or otherwise prevent it preventing the host OS to lock) when the guest OS blanks or powers off its virtual screen. Maybe you can add a configuration option for this as well, but maybe as until today there were no use to powering off/blanking the virtual screen this feature might be OK without any configuration option as well.

Thank you in advance.

Imre",Imre84
19501,"Hello, good mornning from Mexico",VirtualBox 6.1.6,defect,2020-04-16T15:19:08Z,2020-04-16T16:10:30Z,2020-04-16T16:10:30Z,"I tryed to start a virtual machine and a message error, into that mesage apears a note:try reinstalling the software, I tryed with versions, 5,2, 5,5, 6.1 and it is the same case
message:
The virtual machine 'RTCW' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\mgocc\VirtualBox VMs\RTCW\Logs\VBoxHardening.log'.",Pipen13
19504,I'm not able to start a headless virtualmachine,VirtualBox 6.1.6,defect,2020-04-17T11:26:11Z,2020-04-17T11:52:32Z,2020-04-17T11:52:32Z,"I'm not able to start the vm in headless mode from my macOS Mojave 10.14.6. I'm not ready to upgrade to Catalina because I have some 32 bits applications that doesn't work in Catalina.

I'm running the last version of VirtualBox 6.1.6r137129

It seems that error only happens when: Display > Screen > Acceleration > Enable 3D Acceleration is enabled,

",arturocandela
19526,'vboxmanage list runningvms' FAILs to list running VMs,VirtualBox 6.1.6,defect,2020-04-23T19:52:03Z,2020-04-25T10:58:06Z,2020-04-25T10:58:06Z,"noting this similar symptom, from a still open issue

	""vboxmanage list runningvms does not list anything""
	https://www.virtualbox.org/ticket/6808#propertyform
		Opened 10 years ago[[BR]]
		Last modified 4 years ago

has that been fixed/addressed elsewhere?

here, running latest VB release
{{{
	VBoxManage --version
		6.1.6r137129
}}}

on host,
{{{
	lsb_release -rd
		Description:    openSUSE Leap 15.1
		Release:        15.1
}}}

checking available vms, correctly returns
{{{
	> VBoxManage list vms
		""Debian_Stable"" {...}
		""Win10_Pro"" {...}
		""openSUSE_Leap"" {...}
	>
}}}

if i launch a guest, e.g.
{{{
	""openSUSE_Leap""
}}}

is, atm, up & running ... and accessible,
{{{
	ps ax | grep vir
		24799 ?        Sl     0:16 /usr/lib/virtualbox/VirtualBox
		24816 ?        S      0:08 /usr/lib/virtualbox/VBoxXPCOMIPCD
		24822 ?        Sl     0:19 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
		40167 ?        Sl     0:27 /usr/lib/virtualbox/VirtualBoxVM --comment openSUSE_Leap --startvm ... --no-startvm-errormsgbox
		40176 ?        S      0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
		40182 ?        Sl     0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
}}}

but checking RUNNING vms, still (again?) returns blank
{{{
	> VBoxManage list runningvms
	> 
}}}",pgnd
19611,"Cannot install Debian on 3 ISOs, after installing from 2 other discs constantly prompts to insert disc 1, even if it is already inserted",VirtualBox 6.1.8,defect,2020-05-22T06:57:11Z,2020-05-22T06:57:11Z,2020-05-22T06:57:11Z,"I was installing Debian from 3 ISO images. 
Debian installer scanned all the discs, and at some point, it told me to insert 2 other discs. 
Then it prompted to insert disc 1 again, and that's where the problems began. 
I inserted disc 1, and it prompted me to insert it over and over again, even though the disc was in the virtual drive.  
It didn't recognize the disc. 
When I pressed return button, it said ""Cannot read from disc"" when I continued to installing GRUB. 
When the installation ended, I tried to boot Debian, and it didn't boot.
I have checked the ISO images, and there was nothing wrong with them.",anonymous7002
19612,Windows 10 with and without Hyper-V installed.,VirtualBox 6.1.8,defect,2020-05-22T14:54:43Z,2020-05-22T14:54:43Z,2020-05-22T14:54:43Z,"Option:  VT-x/AMD-V Unchecked (not disabled)
Hyper-V: not installed, VT-x/AMD-V shows as Acceleration (shouldn't)
Hyper-V: installed, VT-x/AMD-V shows as Acceleration (shouldn't)

With Hyper-V installed (only once, even after removed), emulation fails to start due to missing VT-x/AMD-V support.

VT-x/AMD-V should follow the requirements of the checkbox, if not wanted, it shouldn't ""auto on"", instead the Acceleration should list ""None"".",BBISOFT
19643,Shift key status leaking from Guest to Host,VirtualBox 6.1.10,defect,2020-06-08T02:26:20Z,2020-06-11T10:28:15Z,2020-06-11T10:28:15Z,"If a VBox session is running and has focus, and an app in that guest session has focus, e.g. TextPad, and the shift key is pushed, you can push say a and TextPad displays A, so it has responded to the shift. 

An app running in the host that is monitoring for the shift using the standard GetAsyncKeyState function receives notification that the shift key is down and thus will respond to it.

I believed the keybard, when captured, should act on all keyboard actions, and not be left for the host (I guess certain reserved keystrokes would be exempt).

This same scenario works fine on VMWare, which is what I am changing from - has worked for many years.

I cannot provide a workaround.

I can provide a program if required to monitor the shift status on the host.",Ken S
19703,VBoxManage and VirtualBox Manager lock up,VirtualBox 6.0.22,defect,2020-07-06T10:18:37Z,2020-07-06T10:26:57Z,2020-07-06T10:26:57Z,"On 4.15.0-108-generic my VirtualBox works fine. Upgrading to 4.15.0-109-generic seems to be a problem for managing Virtual Machines on Virtualbox 6.022 r137980.

VBoxManage as well as VirtualBox Manager seem to lock up when using that version. Virtual Machines just run, until you try to shut them down.

VirtualBox Manager doesn't update the screen anymore. VBoxManage just hangs. Only reboot seems to solve the issue.

I reverted back from 108 to 109 and everything seems to be okay again.

Not 100% sure if it is this upgrade, but it appears so. Thought I better report.",NickGuus
19713,Virtual Box Booting Issue,VirtualBox 5.2.34,defect,2020-07-10T10:25:01Z,2020-07-10T10:30:32Z,2020-07-10T10:30:32Z,"
I am Using using Ubuntu version :  Ubuntu 18.04.4 LTS
                Virtual Box Version : 5.2.34

While start using iso file from my local after Windows logo system got hanged everytime
Could you suggest and help to resolve the issue.",Ujjal
19738,Virtualbox aborting on resume,VirtualBox 6.1.10,defect,2020-07-19T23:33:42Z,2020-07-20T04:28:10Z,2020-07-20T04:28:10Z,"Windows 10 2004 19041.388
Virtualbox 6.1.12

This happens in three ways
1) save-state -> resume vm
2) running -> pause -> resume vm
3) start as hidden -> show -> close-window and continue running in the background

a popup box appears
VBoxHeadless.exe - Application Error
The instruction at 0x... referenced memory at 0x0000..000C. The memory could no be read
Click OK to terminate the program

00:00:25.871086 VMMDev: Guest Additions capability report: (0x0 -> 0x4) seamless: no, hostWindowMapping: no, graphics: yes
00:00:26.335303 VMMDev: Guest Log: 22:32:02.516677 main     VBoxService 6.1.10_Fedora r138449 (verbosity: 0) linux.amd64 (Jun  8 2020 00:00:00) release log
00:00:26.335670 VMMDev: Guest Log: 22:32:22:32:02.517571 main     OS Product: Linux
00:00:26.337367 VMMDev: Guest Log: 22:32:02.519165 main     OS Release: 5.7.8-200.fc32.x86_64
00:00:26.338250 VMMDev: Guest Log: 22:32:02.519954 main     OS Version: #1 SMP Thu Jul 9 14:34:51 UTC 2020
00:00:26.339013 VMMDev: Guest Log: 22:32:02.520828 main     Executable: /usr/sbin/VBoxService
00:00:26.339255 VMMDev: Guest Log: 22:32:02.520828 main     Process ID: 421
00:00:26.342033 VMMDev: Guest Log: 22:32:02.520829 main     Pa22:32:02.523773 main     6.1.10_Fedora r138449 started. Verbose level = 0
00:00:26.344597 VMMDev: Guest Log: 22:32:02.526267 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:26.345107 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:00:37.138464 IEM: rdmsr(0x122) -> #GP(0)
00:49:57.970214 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:49:57.970344 PDMR3Suspend: after     0 ms, 1 loops: 1 async tasks - virtio-scsi/0
00:49:59.069354 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0781) created successfully
00:49:59.426309 AIOMgr: Async flushes not supported
00:49:59.505913 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0781) created successfully
00:49:59.541990 PDMR3Suspend: 1 571 708 931 ns run time
00:49:59.542009 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:49:59.542021 Console: Machine state changed to 'Paused'
00:50:04.490337 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:50:04.490657 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0723) created successfully
00:50:04.495647 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0723) created successfully
00:50:04.500963 Changing the VM state from 'RESUMING' to 'RUNNING'
00:50:04.500977 Console: Machine state changed to 'Running'
00:50:04.501069 
00:50:04.501070 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002f58!!!
00:50:04.501075 
00:50:04.501075 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501079 ExceptionInformation[0]=0000000000000000
00:50:04.501082 ExceptionInformation[1]=000000000000000c
00:50:04.501085 
00:50:04.501085 cs:rip=0033:00007ffa18bb0023
00:50:04.501089 ss:rsp=002b:0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501093 rax=00000000000022e0 rcx=00000000064b0000 rdx=00000000064b3340 rbx=00000000064b0000
00:50:04.501096 rsi=00000000064b3340 rdi=0000000000000000 rsp=0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501102 r8 =00000000064b0140 r9 =0000000000000004 r10=0000000008f4fb10 r11=0000000008f4fb10
00:50:04.501107 r12=00000000064b3340 r13=0000000000000000 r14=0000000000000020 r15=0000000000000060
00:50:04.501110 ds=002b es=002b fs=0053 gs=002b eflags=00010287
00:50:04.501113 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000064b0000
00:50:04.501117 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:50:04.501126 
00:50:04.501126 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000456c!!!
00:50:04.501137    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:50:04.501147 
00:50:04.501148 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501176 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:50:04.501190 ExceptionInformation[0]=0000000000000000
00:50:04.501202 
00:50:04.501203 Stack 0000000008f4c740, dumping 0x38c0 bytes (low=0000000008e50000, high=0000000008f50000)
00:50:04.501215 ExceptionInformation[1]=000000000000000c

Though VMSVGA display adapter is configured, it does not matter which display-adapter is configured, same effect for each.
No sound device is enabled.
I have ensured that hyper-V hypervisor is not enabled

There is a intel haxm type-2 hypervisor, which occasionally is run with android-emulator/qemu. My understanding is that it should not interfere. The joint installtion has worked before. Plus no qemu-VM is running. 

Save/Resume/Show/Hide has worked before.  


",gkamathh
19787,Virtual Machine goes into error after few days,VirtualBox 6.1.10,defect,2020-08-03T11:25:34Z,2020-08-03T11:25:34Z,2020-08-03T11:25:34Z,"Hi,
I am using Virtual Box 6.1.12 on Windows 10 as a host. I am facing a issue of error on my VB which is attached. This is happening after few days and to overcome this I have to uninstall it, delete the .exe file from PC and then restart the PC and download again the new Vbox from Website. I don't know what to call this error. I have attached couple of pics and the Log.
Can anyone help me in this ti resolve the issue. By the way, it doesn't matter which version of Vbox I have installed. This error occurs after few days 

Thanks
Manoj",Montu
19796,Server 2019 Virtualbox host - Guest with any type of GUI causing Windows RDP to crash forcing reboot,VirtualBox 6.1.10,defect,2020-08-06T01:23:16Z,2020-08-06T01:23:16Z,2020-08-06T01:23:16Z,"When RDP'ing to a server 2019 Host with virtualbox installed, attempting to run a guest with a GUI (EG: Ubuntu Desktop, Windows 7 /10) causes RDP to crash and unable to reconnect. Appears to take down whole server as unable to connect to other services either. 

Have been unable to find any details of crash in windows event log. 

Last crash occurred when trying to run windows7 installer ISO. ",ranvens
19816,VirtualBox not able to power-off any (currently-running) machines,VirtualBox 5.2.42,defect,2020-08-16T17:34:33Z,2020-09-08T17:20:25Z,2020-09-08T17:20:25Z,"I am using cuckoo sandbox (version 2.0.7) to perform batch dynamic analysis on windows malware. My host system is Ubuntu 18.04 and I am running 10 Windows 7 VMs on parallel (headless).

The Cuckoo Sandbox application will stop a VM when it is done analysing a binary and will restore the specified snapshot. It will then power up the machine to start a new analysis.

After prolonged usage (around 4+ hours), one or more of the running VMs will become unresponsive and will not poweroff. The only solution I have is to restart the computer, as the virtualbox services will fail to reload.
(If I quit the cuckoo sandbox when one of the machines deadlocks, then all of the running machines will become unresponsive and keep running endlessly).

I am attaching the log of the VM that caused the issue most recently",soutsos
19831,VB Virtual Monitor Setting,VirtualBox 6.1.10,defect,2020-08-25T09:08:20Z,2020-08-25T09:08:20Z,2020-08-25T09:08:20Z,"I am using high resolution screen (3840 x 2560).
When I start my VM I can use the virtual monitor to force the guest to switch the resoution to up to 1600x900. The pull down menu however offers also 1920x1080 and 1920 x 1200. Nothing happens if select them from a lower current guest resultion. 
When expand the guest to maxumum from the host window (auto resizing) I can use the full screen resolution (Great !).
If I click now on in the virtual monitor menu on 1920 x1200 the guest resizes (virtualbox window however remanis maximize).
So there are some issues here on handling the virtual monitor I guess. 
Would be greast offer higher ressultions in the virtual monitor menu for up to the maximum host physical screen resolution (maximizing the host window proofs that the resultions are achievable) but at least that the offered screen resultions in the virtual screen resoltion work properly.",Andreas S
19839,Default Windows Unattend Template Requires Product Key,VirtualBox 6.1.10,defect,2020-08-27T18:33:47Z,2021-02-01T22:31:55Z,2021-02-01T22:31:55Z,"'''Problem''':

The default Windows answer file template (i.e., ""<vbox_install_dir>\UnattendedTemplates\win_nt6_unattended.xml"") requires a product key. Failure to provide the key results in Windows throwing the following error and aborting install, even if ""<AcceptEula>true</AcceptEula>"" is provided.

{{{
Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.
}}}

[[BR]]

'''Impact''':

This prevents users from performing unattended installs of Trial / Evaluation copies of Windows without additional (and non-intuitive) configuration. This is very difficult to troubleshoot as the Windows error message refers to licensing rather than product key / activation issues.

[[BR]]

'''Workaround''':

Creating a modified copy of the template, containing: 

{{{
<UserData>
    <AcceptEula>true</AcceptEula>
</UserData>
}}}

rather than the default:

{{{
<UserData>
    <ProductKey>
        <Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key>
        <WillShowUI>OnError</WillShowUI>
    </ProductKey>
    <AcceptEula>true</AcceptEula>
</UserData>
}}}


and referencing this during using --script-template="""" solves the problem.

Example: [[BR]][[BR]]
VBoxManage unattended install Server2019Template --user=Administrator --password=password --country=US --time-zone=MST --hostname=Server2019Template --image-index=2 --install-additions --start-vm=gui --iso=<ISO_PATH> --script-template=""<path_to_modified_template>\win_nt6_unattended.xml""

[[BR]]

'''Recommended Solution''':

Implement template conditional similar to ""@@VBOX_COND_IS_USER_LOGIN_ADMINISTRATOR@@"", that prevents the ""<ProductKey>"" block from appearing in the final XML answer file if no key is specified on the command-line for ""VBoxManage unattended install"".

If this cannot be fixed quickly, please at least update the documentation to mention this requirement and workaround.",breakid
20008,VERR_SSM_LOAD_CONFIG_MISMATCH on vagrant snapshot restore,VirtualBox 6.1.16,defect,2020-10-29T16:02:24Z,2022-01-12T10:12:54Z,2022-01-12T10:12:54Z,"When restoring a VM snapshot using ''vagrant snapshot restore ..'', I get the following error:

{{{
executing: vagrant snapshot restore 4-st_6_0_0_20-9f29a314b9e1f5626f0f27ebfa8fc0a92dd66e42
==> default: Forcing shutdown of VM...
==> default: Restoring the snapshot '4-st_6_0_0_20-9f29a314b9e1f5626f0f27ebfa8fc0a92dd66e42'...

Progress: 0%

Progress: 90%

==> default: Resuming suspended VM...
==> default: Booting VM...
err: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""startvm"", ""4768f166-7914-4c98-9e81-c4f351614e51"", ""--type"", ""headless""]

Stderr: VBoxManage: error: lsilogicscsi#0: Target 0 config mismatch: config=false state=true  [ver=5 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
}}}

When I try the displayed ''startvm'' command directly, I get the same error (I attached the complete log of that run to this ticket):

{{{
$ VBoxManage startvm ""4768f166-7914-4c98-9e81-c4f351614e51"" --type headless
Waiting for VM ""4768f166-7914-4c98-9e81-c4f351614e51"" to power on...
VBoxManage: error: lsilogicscsi#0: Target 0 config mismatch: config=false state=true  [ver=5 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
$
}}}

Same thing happens in the GUI, when I start the VM or Restore the snapshot.

BUT, when I Discard the saved state, the VM starts up normally. Of course, this doesn't help me, as I cannot use the GUI (see below).

When I try to Restore again, it happens again.

This is VirtualBox 6.1.16, Vagrant 2.2.10 on MacOSX 10.12. But it has happened in this form since at least VirtualBox 6.0.x.

---------------------
Background Info:

We have a script which '''automatically''' provisions a VM to contain our applications, database and everything we need to run our E2E-Tests against.

In order to speed up the provisioning, the script is split into several '''steps'''. As some steps can be quite slow, each step saves a '''VM snapshot''' at the end, so on the next run of the script, if nothing has changed, it can simply '''restore the snapshot''' instead of re-running that step again. (similar idea to the lines in a Dockerfile)

The above error mostly happens on the '''second''' run of the script, when it wants to restore the snapshot it has just taken from the last step on the first run.

The problem seems to be with '''that particular snapshot'''. When I delete it, the script will restore a previous snapshot, which works fine. It will then run the last step again, and snapshot it, and that snapshot usually is also fine.

This is happening for several months now. An interesting pattern I noticed, this only seems to happen when the last step is a '''no-op''' (which means there were two snapshots created in quick succession). It is then always this '''second''' snapshot that is broken. The '''previous''' snapshot is fine. Also when the last step is not a no-op, the error will not occur.

There is nothing peculiar about taking the snapshots, I simply issue ''vagrant snapshot save default <snapshot_name>'' each time.
",Marc Günther
20015,VBox commands via MS openssh on a windows 10 host system fail CO_E_RUNAS_LOGON_FAILURE,VirtualBox 6.1.16,defect,2020-11-03T13:27:29Z,2020-11-03T13:27:29Z,2020-11-03T13:27:29Z,"Trying to run ""VBoxManage list vms"" on a Windows 10 host, when connected to the host via Microsoft OpenSSH server fails:

VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Completely failed to instantiate CLSID_VirtualBox: CO_E_RUNAS_LOGON_FAILURE
VBoxManage.exe: error: Details: code CO_E_RUNAS_LOGON_FAILURE (0x8000401a), component 
VirtualBoxClientWrap, interface IVirtualBoxClient

This works as soon as any user (it does not need to be the one who tries to run the command) connects via rdp to the system. If a user B is connected to the system and a VBox is started from user A, the VBoxHeadless process is running as user B...

Is it possible to avoid this behaviour and run VBoxManage commands and even start headless VMs connected via openssh?
What is the reason for this behaviour?


",mih
20035,Cloned guest poweroff fails and causes complete VM lockup,VirtualBox 6.1.16,defect,2020-11-14T16:57:50Z,2020-11-14T16:57:50Z,2020-11-14T16:57:50Z,"While provisioning a Windows 2016 cloned guest machine using Vagrant, a reboot command is issued that causes the guest to become completely locked up. The vbox.log shows that this appears to be an issue with the state transition table:

00:01:39.652519 Console: Machine state changed to 'Stopping'
00:01:39.652837 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:01:42.828602 AssertLogRel F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\PDMThread.cpp(990) int __cdecl pdmR3ThreadSuspendAll(struct VM *): RT_SUCCESS(rc)
00:01:42.828631 PDMR3ThreadSuspend -> VERR_TIMEOUT for 'HOSTRES'
00:01:42.828642 PDMR3PowerOff: 60 136 616 676 ns run time
00:01:42.828649 Changing the VM state from 'POWERING_OFF' to 'OFF'
00:01:42.828685 VMR3PowerOff:
00:01:42.828693  RUNNING -> POWERING_OFF, SUSPENDED -> POWERING_OFF, DEBUGGING -> POWERING_OFF, LOAD_FAILURE -> POWERING_OFF, GURU_MEDITATION -> POWERING_OFF, FATAL_ERROR -> POWERING_OFF, CREATED -> POWERING_OFF, RUNNING_LS -> POWERING_OFF_LS, DEBUGGING_LS -> POWERING_OFF_LS, GURU_MEDITATION_LS -> POWERING_OFF_LS, FATAL_ERROR_LS -> POWERING_OFF_LS failed, because the VM state is actually OFF
00:01:42.828729 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(3338) int __cdecl vmR3TrySetState(struct VM *,const char *,unsigned int,...); rc=VERR_VM_INVALID_VM_STATE
00:01:42.828857 VMSetError: VMR3PowerOff failed because the current VM state, OFF, was not found in the state transition table (old state FATAL_ERROR_LS)
00:01:42.830483 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Could not power off the machine. (Error: VERR_VM_INVALID_VM_STATE)}, preserve=false aResultDetail=-1907

The only way to recover from this is to kill the VM using task manager.

This issue is reproducible on both MacOS and Windows versions of VirtualBox and more information can be found here: https://github.com/clong/DetectionLab/issues/517",centurion
20050,Execution Cap fails in V 6.1.16,VirtualBox 6.1.16,defect,2020-11-19T18:51:44Z,2020-11-19T18:51:44Z,2020-11-19T18:51:44Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
20051,Execution Cap fails in V 6.1.16,VirtualBox 6.1.16,defect,2020-11-19T18:51:49Z,2020-11-19T18:51:49Z,2020-11-19T18:51:49Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
20088,Soft reset from guest does not reliably restart VM,VirtualBox 6.1.16,defect,2020-12-09T08:43:00Z,2020-12-09T08:43:00Z,2020-12-09T08:43:00Z,"On a Windows host with a Linux Debian 10 guest, issuing a ""reboot"" command to the guest OS does not seem to reliably restart the VM (although it does most of the time). When this fails, it results in a blank/black screen on the guest VM and nothing further happens. It is required that the user manually power off the VM and restart it from scratch.

For example, at this point the reboot trigger seems to be recognised from the logs:
00:01:48.843711 OHCI: Software reset
However, nothing further happens until 5 minutes later when I forcibly power it off:
00:06:59.972369 Console: Machine state changed to 'Stopping'

Logs are attached.",rdghickman
20126,Crash when removing  vms from command line,VirtualBox 6.1.16,defect,2021-01-13T11:32:19Z,2021-01-13T11:32:19Z,2021-01-13T11:32:19Z,"When removing a VM from the command line, Virtualbox often crashes with a critical error when *other* VMs are running. The dialog says for those running (one for each window): ""A critical error has occurred while running the virtual machine and the machine execution should be stopped. [...] Press OK to power off the machine.""

The command executed is
$ vboxmanage unregistervm ""${childvm}"" --delete
where the variable ""childvm"" is a valid name of a VM.

The given log is:
--- start of log ---
Log created: 2021-01-13T10:42:27.425692000Z
Process ID:  3619370 (0x373a2a)
Parent PID:  12731 (0x31bb)
Executable:  /usr/lib/virtualbox/VBoxSVC
Arg[0]: /usr/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown
AddRef: illegal refcnt=3221225469 state=2
--- end of log ---

During the crash ""Oracle VM VirtualBox Manager"" always says data is unavailable. Sometimes the manager refreshes the data itself, other times you need to restart the manager.

",Mrpn
20130,Calling launchVMProcess via vboxwebsrv causes VERR_ENV_INVALID_VAR_NAME,VirtualBox 6.1.16,defect,2021-01-16T23:43:41Z,2021-01-21T14:23:58Z,2021-01-21T14:23:58Z,"When Sending the SOAP request:


{{{
<soap-env:Envelope xmlns:soap-env=""http://schemas.xmlsoap.org/soap/envelope/"">
	<soap-env:Body>
		<ns0:IMachine_launchVMProcess xmlns:ns0=""http://www.virtualbox.org/"">
			<_this>692d166c1e430875-0000000000000004</_this>
			<session>692d166c1e430875-0000000000000003</session>
			<name/>
			<environmentChanges/>
		</ns0:IMachine_launchVMProcess>
	</soap-env:Body>
</soap-env:Envelope>
}}}


I get:


{{{
<SOAP-ENV:Envelope xmlns:SOAP-ENV=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:SOAP-ENC=""http://schemas.xmlsoap.org/soap/encoding/"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:vbox=""http://www.virtualbox.org/"">
	<SOAP-ENV:Body>
		<SOAP-ENV:Fault>
			<faultcode>SOAP-ENV:Client</faultcode>
			<faultstring>VirtualBox error: rc=0x80bb0005 Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME) (0x80bb0005)</faultstring>
			<detail>
				<vbox:RuntimeFault>
					<resultCode>-2135228411</resultCode>
					<returnval>692d166c1e430875-0000000000000005</returnval>
				</vbox:RuntimeFault>
			</detail>
		</SOAP-ENV:Fault>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
}}}


I am able to start the VM without messages via the GUI and with 
""vboxmanage startvm myvm01""

It does not look like any messages are added to the VM's log file, and the only thing added to VBoxSVC.log is


{{{
01:40:03.911204 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={Could not launch the VM process for the machine 'myvm01' (VERR_ENV_INVALID_VAR_NAME)}, preserve=false aResultDetail=-752
}}}


All my soap calls to create the VM, query the power state, and power off the VM function.  My code did work as expected on version 5.1.

I also got the error on 6.1.14 and 6.1.12, I was unable to test prior versions due to compile errors when compiling the kernel modules.  I'm running on Ubuntu 20.04 with the ""virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb"" package downloaded from virtualbox's downloads.

My code can be found at:
https://github.com/T3kton/subcontractor_plugins/tree/master/subcontractor_plugins/virtualbox

the power on function is at:
https://github.com/T3kton/subcontractor_plugins/blob/master/subcontractor_plugins/virtualbox/client.py#L182

Thanks",pnhowe
20174,Installation of VMware Workstation Pro (might) have crippled my VirtualBox systems,VirtualBox 6.1.18,defect,2021-02-08T14:44:59Z,2021-02-08T14:44:59Z,2021-02-08T14:44:59Z,"I have like 10-12 different VMs under Oracle VM VirtualBox. Have used this for many years now, and is very pleased with functionality and possibilities.
Some month ago I had to install VMware Workstation Pro. After that, none of my VirtualBox machines are working ok. Some hangs until I have to abort them others are so slow, they never get into action. Today I uninstalled the VMware Workstation, but the problem is still present under VirtualBox. Now, I do not know for sure that is was VMware that destroyed my VirtualBox. I uninstalled and reinstalled VirtualBox also today, didn't help. Any idea what I should do to make VirtualBox behave under Win-10 (64b) again ?
Martin",MaP
20209,Windows 10 host - ubuntu 20.10 guest crush,VirtualBox 6.1.18,defect,2021-02-19T20:23:10Z,2021-02-19T21:15:26Z,2021-02-19T21:15:26Z,"When playing minecraft (KLauncher) on a guest ubuntu 20.10, the mouse behavior was tilted down or up, then the mouse stopped working in ubuntu altogether.",Дмитро
20227,Screen locks up during POST,VirtualBox 6.1.18,defect,2021-02-25T17:05:36Z,2021-02-25T17:05:36Z,2021-02-25T17:05:36Z,"ID 32
ID 455 
Codes",Miles
20249,When updated virtualbox. EVERY VIRTUAL MACHINE ARE NOT STARTING ANYMORE.,VirtualBox 6.1.18,defect,2021-03-12T01:32:15Z,2021-03-12T22:21:14Z,2021-03-12T22:21:14Z,"i Updated virtualbox only too see if they fixed a bug. then.
No virtual machine wants to start!
IDK why but i am MAD that is happening
The thing is that I cant activate hypervisor partition. What do i do??
Here is the error that appears when i open a virtual machine

Fallo al abrir una sesión para la máquina virtual Windows 7 Ultimate.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Código resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Julian Gamer
20270,Arch linux guest crash after windows 10 host resume from sleep,VirtualBox 6.1.18,defect,2021-03-23T03:52:35Z,2021-03-25T09:27:40Z,2021-03-25T09:27:40Z,"I wrote a topic about this on the virtualbox forum[https://forums.virtualbox.org/viewtopic.php?f=6&t=102250&sid=f398ac48ffa5927918c82d13ef2c7ce8].

Here are how I reproduce the problem:

----
1. start Arch linux guest
2. Windows 10 host sleep
3. resume Windows 10 host
4. Arch linux guest is PAUSED, try to resume it
5. whole virtualbox interface freeze, crash (log ""carsh"")

----
However, if I pause and resume the guest manually once before the host go to sleep, the probelem is gone.

----
1. start Arch linux guest
2. pause guest and resume it immediately
3. Windows 10 host sleep
4. resume Windows 10 host
5. arch linux guest is RUNNING, everything works fine (log ""workfine"")

----

Additionally, I also have a windows 10 guest and a ubuntu 16.04 guest, neither of them have this problem.",lindeshun
20274,VM's do not funtion on Win10,VirtualBox 6.1.18,defect,2021-03-26T01:25:30Z,2021-03-26T01:25:30Z,2021-03-26T01:25:30Z,"I am running windows 10 pro on my pc. Two days ago I turned on a VM which I use regularly, but it gets stuck trying to ""Start VM."" The VM never starts, VirtualBox says that it is at 20%, so I kill it in task manager. However, I am not able to kill VBoxSVC.exe. I turned on Hyper-V and cloned that VM to it to make sure that it is not corrupt (I disabled Hyper-V after verifying). 

I downloaded two other VM's to see if they would function. These new VM's can start, but when I try to shut them down they freeze. Oddly enough, this event prevents me from being able to turn off my pc, so I have to unplug it from the wall. 

The logs I am including in this ticket are for the first VM I referenced. I have Virtualbox 6.1.18 installed on my pc (normally). During my troubleshooting I also installed the most recent 5.x.x version to see if it would have any effect (same symptoms).",GeneralKenobi
20299,VM hung at installation,VirtualBox 6.1.18,defect,2021-04-11T22:42:31Z,2021-04-11T22:42:31Z,2021-04-11T22:42:31Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20300,VM hung at installation,VirtualBox 6.1.18,defect,2021-04-11T22:43:10Z,2021-04-11T22:43:10Z,2021-04-11T22:43:10Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20332,Intel i7 2600K CPU,VirtualBox 6.1.22,defect,2021-05-01T07:06:53Z,2021-05-01T07:06:53Z,2021-05-01T07:06:53Z,"Hello, I am running the latest virtual box (6.1.22) on an old intel i7 2600K CPU. The motherboard is gigabyte p67a-ud7 with virtualization enabled on the bios.  I am using gns3 2.2.20.  Below is the error message when powering up the gns3 VM.  Thanks.

Appreciate your help.


Failed to open a session for the virtual machine GNS3VM.

Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!

 (VERR_CPUM_INVALID_HWVIRT_CONFIG).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Eugene Crujido
20356,Mouse integration click focus gets lost when using (Ultra)vncviewer client inside Windows 10 guest,VirtualBox 6.1.22,defect,2021-05-10T14:41:10Z,2021-05-10T14:41:10Z,2021-05-10T14:41:10Z,"I often experience issues with the mouse integration focus getting partially lost inside my Windows 10 guest (running on my windows 10 host) , meaning: i can hove above windows and buttons and you see them respond to the hovering, but clicking the button or area does not get through.

I notice this usually when i have been or am using the Ultravnc viewer inside the the guest client. It seems to disorient mouse capturing features.

To resolve this, i have to click the mouseintegration button on the lower right and then disable the automatic integration, then manually click the Windows 10 guest and confirm catching the mouse. After confirmation, the system is then responding to mouse clicks (right and left).

The behavior turned up since updating to 6.1.22, i did not had any issues like this with my former version (6.1.18!)",lbsl
20359,VM Windows 7 terminated,VirtualBox 6.1.22,defect,2021-05-11T19:17:39Z,2021-05-12T12:58:41Z,2021-05-12T12:58:41Z,"My Windows 7 VM terminated on my Ubuntu 20.04 LTS host.

I attached the log file.",anno
20367,VM win10 does not start normale.. Does start Headless - Platform Osx,VirtualBox 6.1.22,defect,2021-05-15T13:29:42Z,2021-05-15T13:47:10Z,2021-05-15T13:47:10Z,"A strange thing is that when I open Virtualbox, that the 'Oracele Virtualbox Manager' is appearing on every separate Desktop of my MacBook Pro.

That was not the case before... ",EttD
20394,Settings issue,VirtualBox 6.1.22,defect,2021-06-11T04:38:12Z,2021-06-11T04:38:12Z,2021-06-11T04:38:12Z,"I cant change the VM´s settings, and i cant run it because a AMD-V setting ",Xion18502
20434,usbfilter ignore --product flag,VirtualBox 6.1.22,defect,2021-06-28T13:48:32Z,2021-06-28T13:48:32Z,2021-06-28T13:48:32Z,"Hi!

I noticed that when I create filter using `usbfilter` command the `--product` flag is ignored.

For example, this command:

{{{#!sh
VBoxManage.exe usbfilter add 0 --target ""otus-astra-docker_default_1624884966310_75575"" --name ""Aktiv Rutoken ECP [0100]"" --product ""Rutoken ECP"" --revision ""0100"" --productid ""0030"" --vendorid ""0a89"" --manufacturer ""Aktiv""
}}}

creates this filter:
{{{#!sh
Index:                       0
Active:                      yes
Name:                        Any Rutoken ECP
VendorId:                    0a89
ProductId:                   0030
Revision:                    0100
Manufacturer:                Aktiv
Product:
Remote:
Serial Number:
}}}

I thik that the cause of this because you are forgot to set product field here:
https://github.com/mirror/vbox/blob/b9657cd5351cf17432b664009cc25bb480dc64c1/src/VBox/Frontends/VBoxManage/VBoxManageUSB.cpp#L404-L516",lo1ol
20448,Virtualbox on Linux host kills keyboard when running Windows 10 virtual machine,VirtualBox 6.1.22,defect,2021-07-06T10:25:29Z,2021-07-06T10:25:29Z,2021-07-06T10:25:29Z,"Hi all,

I have a pretty boring problem with virtualbox installed on Kali host and windows 10 as guest. When I use windows 10, after an indefinite time (sometimes immediately, sometimes after a few minutes of use), the touchpad or mouse stops working in both the host system and the guest system. More specifically, the keyboard works correctly, while the click of the touchpad or mouse does not work. The only way to fix this is to shut down the Windows virtual machine.

Does someone have the same issue and found a solution?",fourteenminusone
20485,"CentOS 7, VirtualBox 6.1: compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’",VirtualBox 6.1.26,defect,2021-08-02T14:37:07Z,2021-08-10T10:57:17Z,2021-08-10T10:57:17Z,"CentOS 7, kernel 5.4.137-1.el7.elrepo.x86_64, Virtual Box 6.1

I try to start Virtual machine on Virtual Box 6.1.

''/sbin/vboxconfig''


but I get error:

''vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.''

Here error in file var/log/vbox-setup.log

''In file included from <command-line>:0:0:
./arch/x86/include/asm/page_64.h: In function ‘clear_page’:
././include/linux/compiler_types.h:214:24: error: expected ‘(’ before ‘__inline’
 #define asm_inline asm __inline
                        ^
./arch/x86/include/asm/alternative.h:256:2: note: in expansion of macro ‘asm_inline’
  asm_inline volatile (ALTERNATIVE_2(""call %P[old]"", ""call %P[new1]"", feature1,\
  ^
./arch/x86/include/asm/page_64.h:49:2: note: in expansion of macro ‘alternative_call_2’
  alternative_call_2(clear_page_orig,''


P.S.

''
gcc --version

gcc (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)''
",a_subscriber
20574,VBoxManage 'start --type headless' cannot be correctly closed by 'controlvm acpipowerbutton',VirtualBox 6.1.26,defect,2021-09-25T09:05:30Z,2021-10-12T17:41:27Z,2021-10-12T17:41:27Z,"After using: 
{{{
VBoxManage startvm CentOS7-1 CentOS7-2 CentOS7-3 --type headless
}}}
CentOS7-1, 2, 3 are individual vms created by meself and started correctly.

After using:
{{{
VBoxManage controlvm CentOS7-3 acpipowerbutton
}}}
The vm named CentOS7-3 should have been closed correctly.

But after using:
{{{
VBoxManage startvm CentOS7-3 --type headless
}}}
It fails and outputs as below:
{{{
Waiting for VM ""CentOS7-1"" to power on...
VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
}}}

you can find more detail infos in the topic I posted https://forums.virtualbox.org/viewtopic.php?f=3&t=103980

What's more, through log file named VBoxHardening.log.I find log file which is closed incorrectly lack two lines outputs comparing to log file which is closed correctly:
{{{
3fd0.3fd4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 604653 ms, the end);
3f98.3f9c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 605077 ms, the end);
}}}

Hope this additional msg can help pro devs to solve this problems.
Thx for devs attention and contributions!",Q2K3
20632,6.1.28 Does Not Work at All on Kubuntu 20.04.3 LTS,VirtualBox 6.1.28,defect,2021-10-24T17:10:08Z,2021-10-31T09:23:19Z,2021-10-31T09:23:19Z,"As reported by several people on your [https://forums.virtualbox.org/viewtopic.php?f=7&t=104196 forums]...

Host: Kubuntu 20.04.03
Guests: (2) Kubuntu 20.04.03 and (1) Windows 10
VB: Version 6.1.28 r147628 (Qt5.12.8)
Package: https://download.virtualbox.org/virtualbox/6.1.28/virtualbox-6.1_6.1.28-147628~Ubuntu~eoan_amd64.deb

All is well on 6.1.26. Upgrading to 6.1.28 causes all guests to fail on startup, with the following error message.

{{{
Failed to open a session for the virtual machine | machine name |
}}}

Under ""Details"", the error contains:

{{{
The virtual machine |machine name| has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}

I further attempted to export the guests from 6.1.26, and import them into 6.1.28, but that made no difference.

Downgrading back to 6.1.26 restores correct functionality, so luckily, that's easy. This operation also proves that there's nothing amiss with the machines themselves.

Even worse, newly-created VMs exhibit the same error, so to put it bluntly, 6.1.28 does not work at all on this system.

",Hillman
20653,VirtualBox 6.1.26 fails to boot FreeBSD 13.0 install ISO in EFI mode,VirtualBox 6.1.26,defect,2021-11-09T11:59:11Z,2021-11-09T11:59:11Z,2021-11-09T11:59:11Z,"VirtualBox 6.1.26 fails to boot FreeBSD 13.0 install ISO in EFI mode (https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.0/FreeBSD-13.0-RELEASE-amd64-disc1.iso). However, with old version 6.1.10, I was able to boot this ISO in EFI mode. BIOS boot is working with both versions.",Thomas Dreibholz
20675,The mouse cursor looks like 5 Framerates per sevond and is with the y axis inverted. (SAW AFTER MAC OS X 10.6 SNOW LEOPARD UPDATE),VirtualBox 6.1.28,defect,2021-11-17T16:54:12Z,2021-11-17T16:54:12Z,2021-11-17T16:54:12Z,"As you read the title, the mouse looked like 5 fps and it was inverted with the y axis. before it wasnt like that! i was running on mac os x 10.6 to mess a bit around until ive came to the idea to update because last time i did it with a different iso and it wouldnt open. it worked out pretty well and everything was tip top!... except the mouse.
it maked me shiver of it! i was trying everything to get this thingy fixed, you know the answer: no! it not worked!. so thats why im here, i want to get this thingy fixed. i would appreciate it if i get a answer how to fix it. regards! 
Lefty. :] (original name Arya Jahanshahi)",Lefty. :]
20785,"VM will not start, Guru Meditation -79 (VERR_INVALID_STATE)",VirtualBox 6.1.22,defect,2022-01-20T21:10:17Z,2022-01-21T20:55:33Z,2022-01-21T20:55:33Z,"Virtual machines will not start any more.
Both Windows and Ubuntu guests seem to be having the same project.
I am using VirtualBox 6.1.22_Ubuntu r144080 and I am running Ubuntu 20.04
Linux 5.13.0-27-lowlatency #29~20.04.1-Ubuntu SMP PREEMPT

Yesterday everything works fine and now machines wont start.
When exporting and importing a machine to a different host, the machine does start so it seems the issue is related to the virtual box host.

In the logfile I see:

00:00:04.713444 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:04.713532 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:04.713611 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:04.713634 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:04.713659 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
00:00:10.049433 PIT: mode=3 count=0x4dae (19886) - 60.00 Hz (ch=0)
00:00:10.069842 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:10.069860 Console: Machine state changed to 'GuruMeditation'
00:00:10.070003 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:10.070003 !!
00:00:10.070004 !!         VCPU0: Guru Meditation -1701 (VERR_MM_HYPER_NO_MEMORY)
00:00:10.070037 !!
00:00:10.070063 !!
00:00:10.070063 !! {mappings, <NULL>}
00:00:10.070064 !!


I will attach the logfile to this ticket.

Any help is highly appreciated",DeHouthakker
20889,VM fails during starting,VirtualBox 6.1.32,defect,2022-03-29T22:47:13Z,2022-04-03T17:01:20Z,2022-04-03T17:01:20Z,"During starting or after a few minutes of running an error appers.
Yesterday it run without any problem, nothing new was installed to the PC.",Jirka
20929,"""vboxmanage showvminfo"" creates warning when editing guest settings",VirtualBox 6.1.30,defect,2022-05-05T23:58:31Z,2022-05-10T15:38:13Z,2022-05-10T15:38:13Z,"I have a bash script running in the background that checks every few seconds if a VM is running on my second workspace of Mint20. When i am in Virtualbox Manager and want to edit a setting of a VM that is NOT running, i get a warning that the VM is running and not all settings are stored or changed.. every time that script is called. The exact warning is in Dutch, but from the forum is got this in English:

'''""The virtual machine you are changing has been started. Only certain settings can be changed while a machine is running. All other changes will be lost if you close this window now""'''

The line in the bash script is:
'''""vboxmanage showvminfo ""W7_64"" | grep -c ""running (since"" ""'''

So calling ""vboxmanage showvminfo"" creates a warning that the VM is running when you try to edit guest settings.

To create this situation, open vbox manager, click on usb settings an leave that open, then go to the terminal and start ""vbmanage showvminfo"". The warning pops up that the VM is running.

",RemonK17
20995,Failed to open a session for the virtual machine #VMName#.,VirtualBox 6.1.34,defect,2022-06-20T08:30:16Z,2022-08-30T07:12:41Z,2022-08-30T07:12:41Z,"VirtualBox-6.1.32-149290 works 100% and all VM's start.

From version 6.1.33 get the following error on ALL VM's:

Failed to open a session for the virtual machine #VMName#.

The virtual machine '#VMName#' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\#UserName#\VirtualBox VMs\#VM_And_LogFolder#\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Tried Installing 6.1.33 with and without Extension Packs - Error as Above
Tried installing 6.1.34 with and without Extension Packs - Error as Above
Tried installing 6.1.34a with and without Extension Packs - Error as Above

Please note: I don't think it is the Extension packs because running v6.1.34a with Extension Pack 6.1.32 gives same error.

Included is the LOG files for:
Successful start and shutdown of a VM (v6.1.32)
1.VBox_20220620_6.1.32.log
2.VBoxHardening_20220620_6.1.32.log
Unsuccessful start of same VM (v6.1.34a)
1.VBoxHardening_20220620_6.1.34a.log",Hercules Oberholzer
21070,"Linux VMs hang on boot when ""Host Pipe"" Serial Port is enabled and the OS has console=tty[x] set",VirtualBox 6.1.34,defect,2022-08-19T14:26:24Z,2022-08-22T13:19:56Z,2022-08-22T13:19:56Z,"On Linux and Mac Host I'm seeing that Linux VMs hang on boot when a Host Pipe Serial Port is enabled and I have the Linux bootloader set with the console=tty[x] option. The VM hangs until I use a program to connect to this host port at which time the VM will start loading.

However when I tried to replicate this on a Windows host the VM would boot up immediately.",Joshua_VES
21186,VM No memory  Result Code:  E_FAIL (0x80004005),VirtualBox 6.1.40,task,2022-10-21T13:45:35Z,2022-11-03T21:42:40Z,2022-11-03T21:42:40Z,"What to do? 

Failed to open a session for the virtual machine Rocky Linux_8x64.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: RTCrStoreConvertToOpenSslCertStore failed: \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_NO_MEMORY).

Failed to load VMMR0.r0 (VERR_NO_MEMORY).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Butterfly011
21213,Loading a saved state stops some graphical apps from rendering until reboot,VirtualBox-7.0.2,defect,2022-10-28T21:51:10Z,2022-10-30T22:11:20Z,2022-10-30T22:11:20Z,"It is a simple problem and not critical but I need to make it work because I work with saved states a lot. I should mention that I am somewhat newbie with this guest system archlinux.

I have windows 10 and vbox7.0.2

Basically some GUI applications stop rendering properly if the VM is loaded from a saved state: midori, badwolf, spotify-launcher

I always save the state to resume it and my applications are still there without having to reopen everything, this is something quite common in virtualbox and it never gave me a problem (edited)

Apps like midori, badwolf or spotify-launcher work fine, but they stop rendering if I load a saved state and the only solution is to restart the vm, but other apps like nemo (file explorer) or the terminal (alacritty) don't have that problem.

I think the common detail is that they are gtk applications (however nemo works fine) and my guest distribution is probably not fully prepared for it because I use a very raw install of arch linux:
-i3, picom (i think it could be related), midori, badwold, opera, minbrowser, spotify-launcher. I had also installed arc-gtk-themes

I have tried to log the problem without results or relevant info inside of the VM, reset i3, picom and polybar but none of that corrects the problem.

I already tried reinstalling virtualbox-guest-utils and gtk, I installed gnome but also didn't change anything.

Booted up and midori works:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644709525266503/unknown.png]

Saved state just fine:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644710116659250/unknown.png]

Loading state just right after:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711106510858/unknown.png]

Some apps looks like this, they WORK but dont render properly:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711580475402/unknown.png]

I believe it this most likely a problem on my end, either host or guest, so considering you may not be able to reproduce, I attached some logs.


",mr.satoshi
21328,Update to 7.0.4 seems to crash after lacking 6.1.38?,VirtualBox-7.0.4,defect,2022-12-09T18:27:06Z,2022-12-13T15:53:52Z,2022-12-13T15:53:52Z,"I loved Virtual Box and did neglect updating-problems. My favorite forum does not have a clue why 7.0.4 fails as follows:

{{{
BuschBo:~> VirtualBox 
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: nouveau
Qt WARNING: QObject::connect: No such signal UITabBar::currentChanged(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabMoved(int,int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarClicked(int)
Qt WARNING: QObject::connect: No such signal UITabBar::tabBarDoubleClicked(int)
/usr/bin/VirtualBox: Zeile 70:  9312 Speicherzugriffsfehler  (Speicherabzug geschrieben) LD_LIBRARY_PATH=""/usr/lib/virtualbox${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"" /usr/lib/virtualbox/VirtualBox6 $@

BuschBo:~> systemctl status vboxdrv.service
● vboxdrv.service - VirtualBox Linux kernel module
     Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; disabled; vendor preset: disabled)
     Active: active (exited) since Fri 2022-12-09 18:45:05 CET; 34min ago

BuschBo:~> uname -a
Linux BuschBo 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux

BuschBo:~> zypper se -si virtualbox vbox
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                   | Type  | Version                                   | Arch   | Repository
---+------------------------+-------+-------------------------------------------+--------+-----------------------
i+ | virtualbox             | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 7.0.4_k5.14.21_150400.24.33-lp154.2.20.2  | x86_64 | Main Update Repository
i  | virtualbox-kmp-default | Paket | 6.1.38_k5.14.21_150400.24.21-lp154.2.15.1 | x86_64 | Main Update Repository
i  | virtualbox-qt          | Paket | 7.0.4-lp154.2.20.2                        | x86_64 | Main Update Repository

BuschBo:~> zypper lr -d
#  | Alias                       | Name                                                                                        | Enabled   | GPG Check       | Refresh        | Priority  | Type   | URI                                                                                                                                                                              | Serv->
---+-----------------------------+---------------------------------------------------------------------------------------------+-----------+-----------------+----------------+-----------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------
 1 | openSUSE-Leap-15.4-1        | openSUSE-Leap-15.4-1                                                                        | Nein      | ----            | ----           |   99      | rpm-md | hd:/?device=/dev/disk/by-id/usb-SanDisk_Ultra_05019bbc553237f7fd551958a91e01fe4ded604716e4280b429924ea2772cd6d46f90000000000000000000010702a2300961a10815581071ea825d9-0:0-part2 | 
 2 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/update/leap/15.4/backports_debug/                                                                                                                   | 
 3 | repo-backports-update       | Update repository of openSUSE Backports                                                     | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/                                                                                                                         | 
 4 | repo-debug                  | Debug Repository                                                                            | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/                                                                                                              | 
 5 | repo-debug-non-oss          | Debug Repository (Non-OSS)                                                                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/                                                                                                          | 
 6 | repo-debug-update           | Update Repository (Debug)                                                                   | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/oss/                                                                                                                         | 
 7 | repo-debug-update-non-oss   | Update Repository (Debug, Non-OSS)                                                          | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/non-oss/                                                                                                                     | 
 8 | repo-non-oss                | Non-OSS Repository                                                                          | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/                                                                                                                | 
 9 | repo-oss                    | Main Repository                                                                             | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/                                                                                                                    | 
10 | repo-sle-debug-update       | Update repository with debuginfo for updates from SUSE Linux Enterprise 15                  | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/debug/update/leap/15.4/sle/                                                                                                                         | 
11 | repo-sle-update             | Update repository with updates from SUSE Linux Enterprise 15                                | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/                                                                                                                               | 
12 | repo-source                 | Source Repository                                                                           | Nein      | ----            | ----           |   99      | NONE   | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/                                                                                                             | 
13 | repo-update                 | Main Update Repository                                                                      | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/oss                                                                                                                                | 
14 | repo-update-non-oss         | Update Repository (Non-Oss)                                                                 | Ja        | (r ) Ja         | Ja             |   99      | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/                                                                                                                           | 
}}}",Christiann
21392,Microsoft Hyper-V Virtual Machine Bus Provider failed with code 37,VirtualBox-7.0.4,defect,2023-01-03T13:45:05Z,2023-01-04T12:36:24Z,2023-01-04T12:36:24Z,"- Device driver displays following error:
Windows cannot initialise the device driver for this hardware. (Code 37)
The request is not supported.

- VB VM configuration has :
  [x] Enable PAE/NX
  [x] Enable Nested VT-x/AMD-V
both enabled

also Acceleration is configured:
Paravirtualization Interface: Hyper-V
Hardware Virtualization: [x] Enabled Nested Paging

- VB is installed on the following system:

OS Name	Microsoft Windows 11 Pro
Version	10.0.22621 Build 22621
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	LP11-D5938-5930
System Manufacturer	Dell Inc.
System Model	Latitude 5511
System Type	x64-based PC
System SKU	09C1
Processor	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz, 2712 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date	Dell Inc. 1.18.0, 10/3/2022
SMBIOS Version	3.2
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Dell Inc.
BaseBoard Product	0C33CM
BaseBoard Version	A00
Platform Role	Mobile
Secure Boot State	On
Installed Physical Memory (RAM)	32.0 GB
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, Secure Memory Overwrite, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured	Hypervisor enforced Code Integrity
Virtualization-based security Services Running	Credential Guard, Hypervisor enforced Code Integrity
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	

",kjdro
21395,Mouse cursor buggy with 2 monitor setup,VirtualBox-7.0.4,defect,2023-01-05T21:59:21Z,2023-01-05T21:59:21Z,2023-01-05T21:59:21Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped by the X button on the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  In the video attached, I was only able to record my rightmost screen (with the VM window in it) but the main VirtualBox window was maximized on the display to the left of the one that was recorded.",KernelPanic
21396,Mouse cursor not working properly with 2 monitor setup,VirtualBox-7.0.4,defect,2023-01-05T22:03:20Z,2023-01-05T22:23:15Z,2023-01-05T22:23:15Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped at the top left corner of the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  When the VM window is moved to the same one as the main VirtualBox window the mouse still does not function properly in the VM.  Tried to attach a video but couldn't due to file size restrictions on here.",KernelPanic
21400,E_FAIL when running Kali in VirtualBox 7.0.4,VirtualBox-7.0.4,defect,2023-01-08T10:49:55Z,2023-01-08T10:49:55Z,2023-01-08T10:49:55Z,"I was setting up my VirtualBox and I'm having problem when running kali in VirtualBox.

i've tried reinstalling and stepping down to versions and changing bios settings but still shows the same error.

version: vBox-7.4.4

error message shown as below:

The virtual machine 'kali' has terminated unexpectedly during startup with exit code -1073740791 (0xc0000409). More details may be available in 'C:\Users\Razal\VirtualBox VMs\kali\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0X80004005)
Component: MachineWrap
Interface: IMachine {300763af-5d6b-46e6-aa96-273eac15538a}



",razii97
21438,"VirtualBox ""forgetting"" that an instance is running -> data corruption",VirtualBox-7.0.6,defect,2023-01-28T00:08:07Z,2023-01-28T08:54:30Z,2023-01-28T08:54:30Z,"I have seen this many times.

I'm not sure how to reproduce this, but something must be fundamentally broken if this is can happen, so you should be able to figure this out my looking at the code.

Here is what happens.

I am working with guests.
Suddenly, _something_ happens, which leaves the guest running, but gives VirtualBox the impression that it is not running any more.

So VirtualBox thinks that it's switched off.

This happens with both the GUI and if I use VBoxManager list runningvms.

Since it thinks it's off, clicking on it will start it again.

What happens then is that we get two instances running, with both having read-write access to the same underlying storage devices.

You can how this ends: with tears, blood and of course irrecoverable data corruption. (Two OSs writing to the same file system at the same time...)

This is messed up beyond words.

I am attaching a screenshot, which shows two instances of the UI, running on the same host, with the same user.

One shows the guest on, the other shows it off.

The only difference is that I have launched the other instance of the GUI a bit later, but there was no configuration change. There is no reason why would it show a different status.

You can also see the output of list runningvms on the same screenshot. (Empty.)

Btw the actual guest is only visible on the screen, which is showing another data corruption bug with virtio-scsi, about which I will open a separate bug report.
",csillag
21462,vm crash,VirtualBox-7.0.6,defect,2023-02-07T19:19:31Z,2023-02-07T19:19:31Z,2023-02-07T19:19:31Z,"Restoreing Snapshot crashing vm on vbox 7.0.6
image: Atlas 20H2 -> https://atlasos.net/downloads
",okoca
21477,Custom VM icons don't show up in Ubuntu Dock with VirtualBox 7,VirtualBox-7.0.6,defect,2023-02-08T22:05:46Z,2023-02-08T22:05:46Z,2023-02-08T22:05:46Z,"In Virtualbox 6, I modified the iconfile for each vm, and that icon would show up in the Ubuntu dock. 

On upgrading to 7, the custom icons are still shown inside the VBox Manager GUI, but I just get the default icon in the OS dock bar.

Desired capability shown here: https://twitter.com/0xdf_/status/1529429480858697728

Host OS is Ubuntu 22.04.",dfors
