Cleanup (non user visible) whitespace issues and rewrap long lines.
This commit is contained in:
Benedict Reuschling
parent
53d308e9ea
commit
b5f16bbdf4
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=52160
1 changed files with 31 additions and 30 deletions
|
|
@ -101,7 +101,7 @@
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Know how to <link linkend="ports">install additional
|
<para>Know how to <link linkend="ports">install additional
|
||||||
third-party software</link>.</para>
|
third-party software</link>.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
@ -921,24 +921,24 @@ perm vboxnetctl 0660</programlisting>
|
||||||
<title>&virtualbox; USB Support</title>
|
<title>&virtualbox; USB Support</title>
|
||||||
|
|
||||||
<para><application>&virtualbox;</application> can be configured
|
<para><application>&virtualbox;</application> can be configured
|
||||||
to pass <acronym>USB</acronym> devices through to the guest
|
to pass <acronym>USB</acronym> devices through to the guest
|
||||||
operating system. The host controller of the OSE version is
|
operating system. The host controller of the OSE version is
|
||||||
limited to emulating <acronym>USB</acronym> 1.1 devices until
|
limited to emulating <acronym>USB</acronym> 1.1 devices until
|
||||||
the extension pack supporting <acronym>USB</acronym> 2.0 and 3.0
|
the extension pack supporting <acronym>USB</acronym> 2.0 and
|
||||||
devices becomes available on &os;.</para>
|
3.0 devices becomes available on &os;.</para>
|
||||||
|
|
||||||
<para>For <application>&virtualbox;</application> to be
|
<para>For <application>&virtualbox;</application> to be aware of
|
||||||
aware of <acronym>USB</acronym> devices attached to the
|
<acronym>USB</acronym> devices attached to the machine, the
|
||||||
machine, the user needs to be a member of the <systemitem
|
user needs to be a member of the <systemitem
|
||||||
class="groupname">operator</systemitem> group.</para>
|
class="groupname">operator</systemitem> group.</para>
|
||||||
|
|
||||||
<screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>yourusername</replaceable></userinput></screen>
|
<screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>yourusername</replaceable></userinput></screen>
|
||||||
|
|
||||||
<para>Restart the login session and
|
<para>Restart the login session and
|
||||||
<application>&virtualbox;</application> for these changes to take
|
<application>&virtualbox;</application> for these changes to
|
||||||
effect, and create <acronym>USB</acronym> filters as
|
take effect, and create <acronym>USB</acronym> filters as
|
||||||
necessary.</para>
|
necessary.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 xml:id="virtualization-virtualbox-host-dvd-cd-access">
|
<sect2 xml:id="virtualization-virtualbox-host-dvd-cd-access">
|
||||||
<title>&virtualbox; Host
|
<title>&virtualbox; Host
|
||||||
|
|
@ -1202,16 +1202,16 @@ grub> <userinput>boot</userinput></screen>
|
||||||
that are not supported by the other loaders.</para>
|
that are not supported by the other loaders.</para>
|
||||||
|
|
||||||
<para>In order to make use of the <acronym>UEFI</acronym>
|
<para>In order to make use of the <acronym>UEFI</acronym>
|
||||||
support in <application>bhyve</application>, first obtain the
|
support in <application>bhyve</application>, first obtain the
|
||||||
<acronym>UEFI</acronym> firmware images. This can be done
|
<acronym>UEFI</acronym> firmware images. This can be done by
|
||||||
by installing <package>sysutils/bhyve-firmware</package>
|
installing <package>sysutils/bhyve-firmware</package> port or
|
||||||
port or package.</para>
|
package.</para>
|
||||||
|
|
||||||
<para>With the firmware in place, add the flags
|
<para>With the firmware in place, add the flags <option>-l
|
||||||
<option>-l bootrom,<replaceable>/path/to/firmware</replaceable></option>
|
bootrom,<replaceable>/path/to/firmware</replaceable></option>
|
||||||
to your <application>bhyve</application> command line.
|
to your <application>bhyve</application> command line. The
|
||||||
The actual <application>bhyve</application> command may look
|
actual <application>bhyve</application> command may look like
|
||||||
like this:</para>
|
this:</para>
|
||||||
|
|
||||||
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
|
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
|
||||||
-s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \
|
-s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \
|
||||||
|
|
@ -1220,8 +1220,8 @@ grub> <userinput>boot</userinput></screen>
|
||||||
<replaceable>guest</replaceable></userinput></screen>
|
<replaceable>guest</replaceable></userinput></screen>
|
||||||
|
|
||||||
<para><package>sysutils/bhyve-firmware</package> also contains a
|
<para><package>sysutils/bhyve-firmware</package> also contains a
|
||||||
<acronym>CSM</acronym>-enabled firmware, to boot guests with no
|
<acronym>CSM</acronym>-enabled firmware, to boot guests with
|
||||||
<acronym>UEFI</acronym> support in legacy
|
no <acronym>UEFI</acronym> support in legacy
|
||||||
<acronym>BIOS</acronym> mode:</para>
|
<acronym>BIOS</acronym> mode:</para>
|
||||||
|
|
||||||
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
|
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
|
||||||
|
|
@ -1235,12 +1235,13 @@ grub> <userinput>boot</userinput></screen>
|
||||||
<title>Graphical <acronym>UEFI</acronym> Framebuffer for
|
<title>Graphical <acronym>UEFI</acronym> Framebuffer for
|
||||||
<application>bhyve</application> Guests</title>
|
<application>bhyve</application> Guests</title>
|
||||||
|
|
||||||
<para>The <acronym>UEFI</acronym> firmware support is particularly
|
<para>The <acronym>UEFI</acronym> firmware support is
|
||||||
useful with predominantly graphical guest operating systems
|
particularly useful with predominantly graphical guest
|
||||||
such as Microsoft &windows;.</para>
|
operating systems such as Microsoft &windows;.</para>
|
||||||
|
|
||||||
<para>Support for the UEFI-GOP framebuffer may also be enabled
|
<para>Support for the UEFI-GOP framebuffer may also be enabled
|
||||||
with the <option>-s 29,fbuf,tcp=<replaceable>0.0.0.0:5900</replaceable></option>
|
with the <option>-s
|
||||||
|
29,fbuf,tcp=<replaceable>0.0.0.0:5900</replaceable></option>
|
||||||
flags. The framebuffer resolution may be configured with
|
flags. The framebuffer resolution may be configured with
|
||||||
<option>w=<replaceable>800</replaceable></option> and
|
<option>w=<replaceable>800</replaceable></option> and
|
||||||
<option>h=<replaceable>600</replaceable></option>, and
|
<option>h=<replaceable>600</replaceable></option>, and
|
||||||
|
|
@ -1251,7 +1252,7 @@ grub> <userinput>boot</userinput></screen>
|
||||||
<acronym>VNC</acronym> protocol.</para>
|
<acronym>VNC</acronym> protocol.</para>
|
||||||
|
|
||||||
<para>The resulting <application>bhyve</application> command
|
<para>The resulting <application>bhyve</application> command
|
||||||
would look like this:</para>
|
would look like this:</para>
|
||||||
|
|
||||||
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc \
|
<screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc \
|
||||||
-s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \
|
-s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue