VirtualBox

Ticket #3593 (new task)

Opened 5 years ago

Last modified 3 years ago

Fixes for UserManual.pdf

Reported by: timeless Owned by:
Priority: trivial Component: documentation
Version: VirtualBox 2.1.4 Keywords:
Cc: Guest type: Windows
Host type: other

Description

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 prefixed 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 filter drivers were added already with VirtualBox 2.0

were already added in ...

With VirtualBox 2.1, net filter 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 specific “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 ...

Change History

comment:1 Changed 5 years ago by frank

  • Summary changed from various errors in UserManual.pdf to Fixes for UserManual.pdf

Thank you for this report, your fixes are appreciated!

I will leave this ticket open for further reports.

comment:2 Changed 4 years ago by MarkCranness

The manual does not say how to use VirtualBox.exe to directly start a VM; you must instead guess or infer how to use it based on what the manual *does* say about VBoxSDL and VBoxHeadless.

VirtualBox --startvm <uuid|vm>

See:  http://forums.virtualbox.org/viewtopic.php?f=6&t=23641#p104776

comment:3 Changed 4 years ago by frank

  • Host type changed from Mac OS X to other

comment:4 Changed 4 years ago by MarkCranness

The manual does not document the NAT port forwarding GuestIP setting, for e.g.:

VBoxManage setextradata "Guest" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestIP" 10.0.2.29

comment:5 Changed 4 years ago by Technologov

If you keep this ticket open for further reports, maybe convert it from "defect" to "task" ?

-Technologov

comment:6 Changed 4 years ago by frank

  • Type changed from defect to task

MarkCranness, section 6.4.1.

comment:7 Changed 4 years ago by MarkCranness

@Frank: Yes, section 6.4.1 is where documentation for the GuestIP setting should go.

But section 6.4.1 does not currently document the GuestIP setting. It does document Protocol, GuestPort and HostPort, but not GuestIP.

comment:8 Changed 4 years ago by frank

Confirmed.

comment:9 Changed 4 years ago by thrig

Also, in the section '3.4.1 “Motherboard” tab', in the penultimate paragraph:

"It can only be turned off on the command line; e see chapter 8.7, VBoxManage modifyvm,"

The "e see" should be changed to just "see."

comment:10 Changed 4 years ago by klaus

The previous NAT issues should be resolved by the finally redone way to configure forwarding, and the spurious "e" will be gone in 3.2.2 as well.

comment:11 Changed 4 years ago by Technologov

Several major new features missing from 3.2.0 changelog:

*VDE, Virtual Destributed Ethernet (Linux/FreeBSD hosts only)

*Guest Additions: support seamless and dynamic resizing on older X11 guests (bug #5840)

*VNC: OSE version now includes VNC server for headless mode

-"Technologov"

comment:12 Changed 4 years ago by frank

Note that the 3.2.0 changelog is relative to the 3.1.8 changelog.

comment:13 Changed 4 years ago by thrig

"This option makes the NAT engine to use the host’s resolver mechanisms" s/to

comment:14 Changed 4 years ago by Technologov

VBox 3.2.8:

Chapter "2.3.3. USB and advanced networking support"

Please remove or rewrite the networking part. I recommend to remove.

-Technologov

comment:15 Changed 3 years ago by Carsampa

"Chapter 5.5 Differencing images" - Deleting snapshots

Part "In this case, the differencing image of the disk attachment cannot simply be deleted. Instead, VirtualBox needs to look at each sector of the differencing image and needs to copy it back into its parent;" should be

"In this case, that differencing image of the disk attachment can simply be deleted only if it is the last in the chain. Otherwise, VirtualBox needs to look at each sector of the differencing image and needs to copy it forward into its immediate child;"

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use