﻿ticket	summary	version	created	modified	_changetime	_description	_reporter
767	[documentation] Explain to users how-to run VirtualBox on Windows in background/as a service on PC boot	VirtualBox 1.5.0	2007-10-11T08:54:47Z	2008-07-15T14:16:57Z	2008-07-15T14:16:57Z	"This is easy on Linux and a bit more difficult on Windows, but I wrote a (untested) way of how this is can be possible on Windows 2000/XP hosts.

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

And my answer:

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

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

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

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

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

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

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

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

-Technologov"	Technologov
2578	Update sections 3.4.3 and 3.4.4 to reflect current functionality	VirtualBox 2.0.4	2008-11-06T15:18:54Z	2009-11-15T22:09:43Z	2009-11-15T22:09:43Z	"'''Section 3.4.3'''

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

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

'''Section 3.4.4'''

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

This is sensible and what VBox should do, it is also factually incorrect.  If you try this then VBox raises an error:  
{{{
Cannot take a snapshot when there is a Writethrough hard disk attached ... E_FAIL (0x80004005)
}}}"	Terry Ellison
3593	Fixes for UserManual.pdf	VirtualBox 2.1.4	2009-03-25T23:01:27Z	2011-02-24T21:15:21Z	2011-02-24T21:15:21Z	"I've read portions of UserManual.pdf and have some suggested corrections...

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

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

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

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

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

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

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

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

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

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

page 128
{{{
9.16 Enabling SCSI controllers in the guest 
As said in chapter 5.1
}}}
As mentioned in ..."	timeless
5344	Add Haiku to the list of supported OS	VirtualBox 3.0.10	2009-10-30T11:13:59Z	2009-10-30T11:13:59Z	2009-10-30T11:13:59Z	"Hi,

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

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

The following host platforms were dropped:

Windows 2000 - dropped in VBox 1.6.0

Linux 2.4 - dropped in VBox 2.?.?

Mac OS X 10.4 Tiger - dropped in VBox 3.1.0

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

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

-Technologov, 20.1.2010"	Technologov
6985	"""Configuring the BIOS DMI information"" documentation needs improvement"	VirtualBox 3.2.4	2010-06-14T02:01:36Z	2010-06-14T12:44:22Z	2010-06-14T12:44:22Z	"I am trying to use the ""VBoxManage setextradata"" feature described in that section of the manual to set up the DMI data so that my VM looks like my actual system, in this case an Acer Ferrari 3400 laptop, so that the version of Windows XP that came with it will install.

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

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

I have included the full output of dmidecode for my laptop for you to see what it looks like as an attachment to this report.
"	Mike Riley
7633	Add an example of scan codes for VBoxManage controlvm	VirtualBox 3.2.10	2010-10-22T15:51:32Z	2018-12-16T23:41:29Z	2018-12-16T23:41:29Z	"It is not clear from the documentation how to send Ctrl-Alt-Del to a vm using 'VBoxManage controlvm'. The solution is far from obvious, but the utility is high (as witnessed by the fact that there is a command for it in the GUI console. I propose adding the following bullet to 8.11:

- VBoxManage controlvm keyboardputscancode allows you to send keystrokes to the virtual machine. This is particularly useful for virtual machines that are running headless. The keystrokes are entered as the hex values of the scancodes. To send Ctrl-Alt-Delete, use the sequence ""1d 38 53 b8 9d"".
"	Paul Hoffman
9041	The example python script src/VBox/Frontends/VBoxShell/vboxshell.py	VirtualBox 4.0.4	2011-06-07T12:24:55Z	2011-06-09T09:10:18Z	2011-06-09T09:10:18Z	"The example python script src/VBox/Frontends/VBoxShell/vboxshell.py, has the ability to save screen-shots. When no file-name for a screen-shot the takeScreenshot function writes the screen-shot to ""/tmp/screenshot.png"".
Potentially ""/tmp/screenshot.png"" could be a symbolic link to another file. The other file would be over-written if a user saved a screen-shot without specifying the file-name."	ra
10592	"Documentation for ""Restoring d3d8.dll and d3d9.dll"" is incomplete"	VirtualBox 4.1.16	2012-05-23T19:00:30Z	2014-08-25T11:50:47Z	2014-08-25T11:50:47Z	"A recent version of the Guest Additions installer on Windows implemented a check for ""corrupted"" versions of d3d8.dll and d3d9.dll. When the installer discovers an incorrect version of one of these files, it opens the following URL in the user's web browser:

http://www.virtualbox.org/manual/ch12.html#ts_d3d8-d3d9-restore

The instructions for Windows 7 are to replace the following files from the original Windows media:

{{{
C:\Windows\System32\d3d9.dll
C:\Windows\SYSWOW64\d3d8.dll
C:\Windows\SYSWOW64\d3d9.dll
}}}

The instructions are incomplete, however, as the guest additions installer also checks for incorrect versions of the following files, and fails if they are found:

{{{
C:\Windows\system32\dllcache\d3d9.dll
C:\Windows\SysWOW64\dllcache\d3d8.dll
C:\Windows\system32\msd3d9.dll
}}}

I believe the first two files can simply be deleted as they are merely cached copies. The third, msd3d9.dll, was not present on the Windows media I was using, and I suspect it can be deleted as well. 

The documentation should be updated to include instructions about deleting these files manually. Alternately, the installer could delete these files itself."	Ryan Steele
11922	Document on creating CD/DVD (and installing Guest Additions) do not mention VM must be shut down	VirtualBox 4.2.14	2013-07-03T12:44:00Z	2013-07-04T19:52:51Z	2013-07-04T19:52:51Z	"I'm running a CentOS 6 VM guest on an XUbuntu 13.04 host using virtualbox 4.2.10_Ubuntu r84101

Under Machine -> Settings -> Storage, the menu item to ""Add a CD/DVD Device"" is disabled for both the IDE and SATA controllers.

Neither https://www.virtualbox.org/manual/ch04.html#idp14782496 
nor https://www.virtualbox.org/manual/ch03.html#settings-storage say anything about shutting down in order to use Device -> Storage -> Add CD/DVD Device.

The latter says ""You can modify these media attachments freely.""

Please add text to these manual pages to make it clear how to add a CD or DVD device.
"	David Biesack
12331	The documentation is not entirely up to date regarding the NAT service	VirtualBox 4.3.2	2013-11-08T12:14:06Z	2013-11-08T12:14:06Z	2013-11-08T12:14:06Z	"A part of the documentation hasn't been updated to reflect the newly introduced NAT Service.

Specifically, ""8.8.2. Networking settings"" doesn't include the ""natnetwork"" options and the ""--nat-network""  parameter, while they are correctly enlisted in ""8.2. Commands overview"".
"	sap239048
12540	Link to VirtualBox Manager for Android from website	VirtualBox 4.3.6	2013-12-25T03:11:27Z	2013-12-25T03:11:27Z	2013-12-25T03:11:27Z	"There is a link to phpVirtualBox (not an offical Oracle application) from www.virtualbox.org which is a webservice client UI.  I created a similar app called VirtualBox Manager for Android which is now a robust and open source application which has almost all the same functionality.  I was hoping to see a link to it from the virtualbox.org website.  It is available on the Google Play Store and source is available on github.

[https://play.google.com/store/apps/details?id=com.kedzie.vbox]
[http://www.github.com/kedzie/VBoxManager]"	Mark Kedzierski
13913	Start a VM at boot time on a Windows host	VirtualBox 4.3.24	2015-03-03T09:59:19Z	2015-03-03T15:36:38Z	2015-03-03T15:36:38Z	"Can a VM be started at boot time on a Windows host? 
Documentation (see page https://www.virtualbox.org/manual/ch09.html#autostart ) 
say it is possibile on other hosts (Linux, Solaris, ...).
Does it mean it is not possible on Windows hosts?
If so, can this limitation be inserted in documentation?
If not, can the documentation include instructions to start a guest VM at boot time?

  "	Marius Roma
15152	Cannot unsubscribe from notifications for a single issue	VirtualBox 5.0.14	2016-02-17T16:14:31Z	2020-05-15T12:18:28Z	2020-05-15T12:18:28Z	"The bugtracker needs a mechanism to unsubscribe from a single issue.

EG: If I write a one-line platform-specific issue confirmation, I don't necessarily want ongoing play-by-play notifications five years later when someone reopens the issue.

I am solving this by emptying my email preference for the time being.  I'll re-enter it in the future if I again have specific bugs that I'd like to track."	Justice
15343	Internal networking remark on same UID policy is misleading	VirtualBox 5.0.18	2016-04-24T21:36:00Z	2016-04-24T21:36:00Z	2016-04-24T21:36:00Z	"The User Manual states that ""As a security measure, the Linux implementation of internal networking only allows VMs running under the same user ID to establish an internal network"". This would be correct if the sentence ended with ""(by default)"".

Current wording suggests that if I wanted to create two VMs using two UIDs I would have to use e.g. a host-only interface instead. This requires more work, e.g. configuring a firewall so the traffic is allowed only between those two VMs.

It seems that ""internal networking"" interfaces work the same as ""host-only"" interfaces used to. Anyone who tried to share a vboxnet interface in older versions of VirtualBox had to use RestictAccess=0. Apparently the same works for ""internal networking"" interfaces. Both types are managed by the same parts of code and show up in logs as ""intnet"" interfaces so maybe it's not that surprising.

So even if authors do not want to write about RestrictAccess and AccessPolicy settings the manual should at least suggest there is a possibility of creating a shared ""internal networking"" interface."	wodny
15352	Poor/missing documentation of Balloon parameters	VirtualBox 5.0.18	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	2016-04-25T23:17:39Z	"The parameters involved in the balloon control (in VBoxBalloonCtrl) are very poorly described (section 9.22.1).  I had to read the code to understand how they are being used.

BalloonLowerLimitMB - despite the confusing name, this parameter is the minimum free memory that should be maintain in the Guest. It is not a ""balloon lower limit"", it is a Guest free memory lower limit.

VBOXWATCHDOG_BALLOON_SAFETYMARGIN - this parameter is only visible in the daemon start up script. While I assumed this was the memory safety margin in the Guest, it is not. It is the memory safety margin the Host. The balloon daemon will not reduce the balloon in a Guest if that would cause the Host to not have enough memory.


"	prensing
15953	doc/manual/fr_FR/ missing man_VBoxManage-debugvm.xml and man_VBoxManage-extpack.xml	VirtualBox 5.1.6	2016-09-19T02:26:12Z	2016-09-21T14:57:54Z	2016-09-21T14:57:54Z	"I'm trying build Vbox with VBOX_WITH_DOCS_TRANSLATIONS=1


{{{
kmk: *** No rule to make target `/builddir/build/BUILD/VirtualBox-5.1.6/doc/manual/fr_FR/man_VBoxManage-debugvm.xml', needed by `/builddir/build/BUILD/VirtualBox-5.1.6/obj/obj/manual/fr_FR/user_man_VBoxManage-debugvm.xml'.  Stop.
}}}

in ./doc/manual/Makefile.kmk, user_man_VBoxManage-debugvm.xml should not be add to fr_FR translation .

fyi is not a new bug , search on french contributions seems that doesn't have debugvm

https://www.virtualbox.org/pipermail/vbox-dev/2013-February/011232.html etc "	sergiomb
16091	Update to manual, section 9.31.3:command to enter a password for headless encrypted guests.		2016-10-20T14:31:28Z	2016-10-20T14:31:28Z	2016-10-20T14:31:28Z	"The command listed is:


{{{
VBoxManage controlvm ""uuid|vmname"" addencpassword ""id"" ""password"" [--removeonsuspend ""yes|no""]
}}}


To me and another user or three (https://forums.virtualbox.org/viewtopic.php?f=1&t=69251) the ""password"" seems to imply that one should type the password in the command line.

However the section 8 VboxManage controlvm addencpassword instructions say the command is:


{{{
addencpassword <id> <password file>|- [--removeonsuspend <yes|no>]
}}}


If one wants to type the password one puts the hyphen in the command line, like this:


{{{
addencpassword <id> -
}}}


and the command line asks for the password separately.

I suspect the command in section 9.31.3 should read the same as section 8, like this:


{{{
VBoxManage controlvm ""uuid|vmname"" addencpassword ""id"" <password file>|- [--removeonsuspend ""yes|no""]
}}}
"	scottgus1bug
16092	Update to Manual for Detachable Guest Windows	VirtualBox 5.1.8	2016-10-20T14:39:30Z	2016-10-20T15:55:25Z	2016-10-20T15:55:25Z	"The manual seems light on details on how to use the new Detachable Guest Windows capabilities. There is a mention of the ""Vboxmanage startvm {vmname} --type separate"" command, but there are a lot more nuances. 

Maybe a new section, perhaps under section 1.8, about the Detachable options and how to use the GUI and the command line to turn the window on and off. Perhaps something like this: (editor note, windows-centric info, should be checked for accuracy with other host OS's)

*******************************************************

Guests are usually run with a normal GUI interface window, as shown at the start of section 1.8. 
Starting in Version 5.0, guests can be started with a detachable window, which can be closed while the guest is still running. The guest can also be started headless, without a visible window, but the window can be shown on demand. When the guest runs headless it still calculates its GUI as if there was a window present.

To start a guest with a visible but detachable window, do one of the following:

  * Click the guest then click the dropdown next to the Start button at the top of the manager window, and choose ""Detachable Start""

  * Right-click the guest in the Manager window, and choose ""Start"", then ""Detachable Start""

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type separate"" 
	(see section 8.2 under ""startvm"" and 8.12)

To start a guest without a visible window, do one of the following:

  * Click the guest then click the dropdown next to the Start button at the top, and choose ""Headless Start""

  * Right-click the guest in the Manager window, and choose Start, then ""Headless Start""

  * Hold down Shift on the keyboard, then double-click the guest in the Manager window.

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type headless"" 
	(see section 8.2 under ""startvm"" and 8.12)

To hide the guest's detachable window and leave the guest running:

  * In version 5.0, click the guest window's Close box. Select ""Continue Running in the Background"", then OK.
	(Note that under versions earlier than 5.1, clicking the guest window's Close box pauses the guest. 
	To prevent this pause when hiding the guest's window, upgrade to version 5.1 or later is required.

  * In version 5.1 or later, click the guest window's ""Machine"" menu, then ""Detach GUI"". 
	A custom Host-key combination can be set for ""Detach GUI"" in the Manager window
	under the File menu, Preferences, Input, Virtual Machine tab.

To show the guest's window after it has been hidden:

  * Click the guest then click ""Show"" at the top of the Manager window.

  * Right-click the guest in the Manager window, and choose ""Show""

  * In a command line, run the command ""Vboxmanage startvm ""vmname"" --type separate"" 
	(see section 8.2 under ""startvm"" and 8.12)

See section 9.31.3 on how to start an encrypted guest in Headless mode.

Things to remember:[[BR]]

At present Detachable mode is experimental.[[BR]]

A guest that is started in Detachable or Headless modes does not have 3D acceleration. [[BR]]

When a guest is started in Normal mode the window cannot be detached.[[BR]]

When a guest is running in Detachable mode and the guest's window has been hidden, the guest does not appear in the taskbar."	scottgus1bug
16176	"No documentation exists for GAs' ""VBoxControl"""	VirtualBox 5.1.8	2016-11-10T08:33:02Z	2016-11-11T15:40:24Z	2016-11-11T15:40:24Z	"As the title plainly says, there is no documentation whatsoever for the ""{{{VBoxControl}}}"" program that gets installed with the GAs. No mention of the syntax, parameters, logic, effects. None, except the command line syntax help.

In fact, it would be nice to mention what the rest of the programs installed with the GAs also do. Even briefly."	Socratis
16178	Please fix audio debugging instructions		2016-11-10T15:15:36Z	2016-11-11T17:04:29Z	2016-11-11T17:04:29Z	"The instructions available here https://www.virtualbox.org/wiki/AudioDebug to provide useful log files for audio issues debugging are misleading, at least for Linux.

They suggest to set an environment variable in a shell with elevated privileges, then kill this shell and check in another, non-privileged, shell that the variable is set. I'm quite sure that running VirtualBox with VBOX_RELEASE_LOG set will never happen this way.

My suggestion would be to ask people to close VirtualBox, then run from the command line


{{{
VBOX_RELEASE_LOG=drv_host_audio.e.l.l2.l3.f+drv_audio.e.l.l2.l3.f+audio_mixer.e.l.l2.l3.f+dev_hda_codec.e.l.l2.l3.f+dev_hda.e.l.l2.l3.f+dev_ac97.e.l.l2.l3.f VirtualBox
}}}


then check in the log that ""Audio: Verbose logging enabled"" is there.

I can't test the provided instructions for Windows."	slv
16581	Scaled mode: documentation explains different	VirtualBox 5.1.18	2017-03-19T11:28:38Z	2017-03-19T11:28:38Z	2017-03-19T11:28:38Z	"Previously, the 'Keep Aspect Ratio' feature was present in scale mode but removed since r59335 due to Qt5 migration.[[BR]]
However, the documentation, in chapter 1.8.5 still explains:


'''The aspect ratio of the guest screen is preserved when resizing the window. To ignore the aspect ratio, press Shift during the resize operation.'''"	ddixuike
17297	critical typo in documentation for installation of Linux Guest Additions	VirtualBox 5.1.30	2017-11-20T12:19:39Z	2017-11-20T14:13:12Z	2017-11-20T14:13:12Z	"The last sentence of section 2.3.2 of the VirtualBox documentation reads as follows:

----------------------------------------------------------------
If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running (as root) the following command:

rcvboxdrv setup
------------------------------------------------------------------

The command cited (""rcvboxdrv"") does not exist. I believe that what was intended is as follows:

---------------------------------------------------------------------
If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running (as root) the following command:

rcvboxadd setup
----------------------------------------------------------------------

While this might be obvious to someone with experience with Virtualbox, it is likely that any user who actually needs to read that documentation will find it difficult to correct the error that is returned when s/he tries to follow what is written:

---------------------------------------------------------
-su: rcvboxdrv: command not found



"	sbpetrack
17318	Permanent, human readable anchors in the HTML User Manual	VirtualBox 5.2.0	2017-11-28T00:35:50Z	2019-01-21T12:05:37Z	2019-01-21T12:05:37Z	"The HTML format of the user manual and the links to different chapters/sub-chapters/paragraphs, often complain anchors in a ""non-human"" format. Example the GAs for Windows vs. the GAs for Linux:
* https://www.virtualbox.org/manual/ch04.html#additions-windows
* https://www.virtualbox.org/manual/ch04.html#idm2096
That second ""idm2096"" seems like something that was automatically created. My fear is that it might change down the road, making it difficult to link to specific sections, or even worse make links invalid. Especially if new chapters/paragraphs are inserted into the manual."	Socratis
17566	"""VBoxManage natnetwork list"" output incomplete"	VirtualBox 5.2.6	2018-02-26T15:46:42Z	2018-02-26T15:46:42Z	2018-02-26T15:46:42Z	"The command ""VBoxManage natnetwork list"" does not show as much information about configured networks as ""VBoxManage list natnetworks"" does.

The attached ""output.txt"" shows the output of the two commands for an example natnetwork.

If a network has ports forwarded, this part of the configuration can only be seen with ""VBoxManage list natnetworks"".

It's counter-intuitive that not everything about natnetworks can be observed/managed with ""VBoxManage natnetwork ..."". Technically, this behaviour is documented [https://www.virtualbox.org/manual/ch06.html#network_nat_service] but it's easily overlooked. The documentation should emphasise more clearly that not all natnetwork-related commands can be reached with ""VBoxManage natnetwork ..."". Or, alternatively an additional command-line argument in the spirit of ""VBoxManage natnetwork list --detail"" would print the port forwardings as well."	damiano++
17798	help info of autostart wrong => Fixed in SVN	VirtualBox 5.2.12	2018-06-03T06:14:21Z	2018-06-03T10:10:40Z	2018-06-03T10:10:40Z	"The help says to use --autostart on|off to toggle autostart.
But actually it should be --autostart-enabled on|off.

Another tip: The help is missing message of how to set autostop-type. "	kinlion
18759	documentation error -> fixed as of 17 July 2019 (6.0.x and later)	VirtualBox 6.0.8	2019-07-16T12:16:11Z	2019-07-17T07:53:19Z	2019-07-17T07:53:19Z	"https://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm

""uarttype <1-N> 16450|16550A|16750: Confgures the UART type for a virtual serial port. The default UART type is 16550A.""

Is a seperate setting, should not be a subitem under ""uartmode"".
"	jpnielsen
18873	"""VBoxManage sharedfolder add"" is missing documentation about the ""--auto-mount-point"" option"	VirtualBox 6.0.10	2019-08-28T09:33:10Z	2019-08-28T09:35:59Z	2019-08-28T09:35:59Z	"The automount point option which is exposed in the GUI, while also available in the CLI via the ""`VBoxManage sharedfolder add`"" command, it's not documented either in the ""`VBoxManageHelp.cpp`"", the ""`SDKRef.xml`"", and the ""`user_VBoxManage.xml`"" (that's all the suspects that I could find).

Also, if it's not too late, you could change that option from ""`--auto-mount-point`"" to ""`--automount-point`"" to be more consistent with the ""`--automount`"" option."	Socratis
19751	clarify license of VBoxGuestAdditions ISO OSE or PUEL (free vs nonfree)	VirtualBox 6.1.10	2020-07-22T14:22:40Z	2020-08-19T12:08:49Z	2020-08-19T12:08:49Z	"VBoxGuestAdditions iso was PUEL (nonfree, proprietary) in 2009 as per [https://forums.virtualbox.org/viewtopic.php?f=10&t=21374 this forum discussion]. Therefore the Debian package [https://packages.debian.org/buster/virtualbox-guest-additions-iso virtualbox-guest-additions-iso] is still in Debian nonfree (meaning: Debian is saying that package is proprietary, not Open Source / Free / Libre Software). The [https://metadata.ftp-master.debian.org/changelogs//non-free/v/virtualbox-guest-additions-iso/virtualbox-guest-additions-iso_6.0.4-1_copyright Debian license file for virtualbox-guest-additions-iso] still says so.

A lot has happened since 2009.

The VirtualBox licensing FAQ `[2]` does not mention the VBoxGuestAdditions ISO. It only mentions the VirtualBox Extension Pack being under nonfree license Extension Pack Personal Use and Evaluation License (PUEL) `[3]`.

Editions page `[4]` stating:

> Before version 4.0, there were two editions of VirtualBox: a full binary containing all features and an ""Open Source Edition"" (OSE) with source code. With version 4.0, there is only one version any more, which is open source, and the closed-source components have been moved to a separate extension pack.

When installing from guest using guest additions ISO, there is no PUEL license prompt either.

Source code organization page `[5]` mentions:

> src/VBox/Additions/: The ""Guest Additions"" for Windows and Linux (and possibly more in the future); this is code that must be installed within a guest to optimize its performance and usability. The build system compiles this code into an ISO file that can be mounted as a VM's virtual CD-ROM drive, as described in the user manual.

The VirtualBox guest additions source tree is apparently part of OSE. Therefore the build result should also be under OSE.

VirtualBox extension pack source code was as far as I know never visible to the general public. Therefore reviewing the situation with today's knowledge, I wouldn't know why virtualbox-guest-additions-iso should be considered being under non-free PUEL license.

The licensing state (libre vs non-libre) was never in public, specifically mentioned, clarified according to my elaborate web research. It seems quite likely that guest additions ISO is nowadays under a libre license (OSE).

Asked about this in [https://forums.virtualbox.org/viewtopic.php?f=10&t=21374&p=477656#p477656 virtualbox forums] and Debian issue tracker [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962311 move virtualbox-guest-additions-iso from non-free to contrib] but haven't received any answer after more than 1 months therefore I guess there won't be an answer. Therefore now asking here.

I speculate it could be that the Debian maintainers of the package are waiting for the VirtualBox representatives to make any statement regarding the license.

It would be good if this could be clarified. A short reply ""VBoxGuestAdditions iso is OSE."" would suffice.

`[1]` -

`[2]` https://www.virtualbox.org/wiki/Licensing_FAQ

`[3]` https://www.virtualbox.org/wiki/VirtualBox_PUEL

`[4]` https://www.virtualbox.org/wiki/Editions

`[5]` https://www.virtualbox.org/wiki/Source_code_organization
"	adrelanos
20076	Warn people about memory corruption in VMs due to Intel Power Gadget run on host macOS	VirtualBox 6.1.16	2020-12-02T15:48:57Z	2021-03-27T09:18:10Z	2021-03-27T09:18:10Z	"When running Intel Power Gadget (IPG) on a macOS host alongside VirtualBox it can cause memory corruption in the VirtualBox guests, causing al kinds of random errors, data corruption and eventually kernel panics in the guests.

However, the memory corruption can stay hidden for a while because it will not always directly lead to observable errors. And because IPG seems like an innocent monitoring tool, many people will be oblivious to this corruption due to IPG.

Some other reports about this:
https://forums.virtualbox.org/viewtopic.php?f=8&t=97929
https://stanislas.blog/2020/02/crashes-virtualbox-macos-intel-power-gadget/

Because of the severity of the problem and the fact that it is far from apparent that this is caused by IPG, I think it is wise to warn people about this.

Maybe just add some text on the download page, or maybe even better add a warning in VirtualBox if it detects com.intel.driver.EnergyDriver is loaded.
"	janvenekamp
20897	VBoximg-mount : error in documentation	VirtualBox 6.1.32	2022-04-11T08:28:11Z	2022-04-11T08:28:11Z	2022-04-11T08:28:11Z	"Hi,

In the VBox User Manual.pdf as in the web pages, regarding vboximg-mount, the string 
{{{
-i=afile.vdi
}}}

 is WRONG ! '''Must be''' 

{{{
-i afile.vdi
}}}

Same problem with 
{{{
--image
}}}
, of course.


Regards,[[BR]]
--[[BR]]
jpt"	jpt
21104	VirtualBox.chm index missing?	VirtualBox 6.1.36	2022-09-09T17:17:52Z	2022-09-09T17:17:52Z	2022-09-09T17:17:52Z	"I am unable to search the help file.
It appears there is no index to search.
Can I add/build one (I do not know if the User can add/create an index) or can you update the help file to be searchable?

Please advise.
Thanks, Tracey
Searching for USB results in ""No Topics Found"" "	Tracey
21188	Clarify if clicking to pause a guest releases CPU and/or Memory	VirtualBox-7.0.2	2022-10-22T00:09:44Z	2022-10-22T00:09:44Z	2022-10-22T00:09:44Z	"[https://www.virtualbox.org/manual/UserManual.html#vboxmanage-controlvm 8.20. VBoxManage controlvm] states the ""pause command temporarily stops the execution of a VM. When paused, the VM's state is not permanently changed.""

Please add there if it means releasing CPU and/or Memory (mention which) from the host, and whether it's completely or partially (if partially then mention how much it should).

Some users seem to assume so and [https://superuser.com/questions/131646/why-does-virtualbox-use-15-20-cpu-when-vm-is-paused then have complaints], so please make it official."	l-w-c
21193	Update build instruction page	VirtualBox-7.0.2	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	2022-10-22T17:26:27Z	"The wiki page (https://www.virtualbox.org/wiki/Linux%20build%20instructions) containing the build instruction seems to be a bit out of date.

The instructions for a Linux host are missing at least 
the reference to `glslang`, `liblzf` and maybe others.
gcc-3.3.3 might still work, but nowadays, `gcc-12.2.0` is recent.
What about Java versions beyond JDK6, how to use newer JDKs (9, 11, 17 or even newer) than JDK8?
"	Moody
