Changeset 34977 in vbox
- Timestamp:
- Dec 13, 2010 8:16:25 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Installation.xml
r34680 r34977 269 269 <title>The VirtualBox kernel module</title> 270 270 271 <para>VirtualBox uses a special kernel module to perform physical memory 271 <para>VirtualBox uses a special kernel module called 272 <computeroutput>vboxdrv</computeroutput> to perform physical memory 272 273 allocation and to gain control of the processor for guest system 273 274 execution. Without this kernel module, you can still use the VirtualBox 274 manager to configure virtual machines, but they will not start.</para> 275 manager to configure virtual machines, but they will not start. In addition, 276 there are the network kernel modules <computeroutput>vboxnetflt</computeroutput> 277 and <computeroutput>vboxnetadp</computeroutput> which are required for 278 the move advanced networking features of VirtualBox.</para> 275 279 276 280 <para>The VirtualBox kernel module is automatically installed on your 277 281 system when you install VirtualBox. To maintain it with future kernel 278 updates, for recent Linux distributions -- for example Fedora Core 5and279 later, Ubuntu 7.10 (Gutsy) and later and Mandriva 2007.1 and later --,282 updates, for most Linux distributions -- for example Fedora Core 11 and 283 later, Ubuntu 8.04 (Hardy) and later and Mandriva 2009.1 and later --, 280 284 generally we recommend installing Dynamic Kernel Module Support 281 285 (DKMS)<footnote> … … 431 435 432 436 <listitem> 433 <para>It builds the VirtualBox kernel module 434 (<computeroutput>vboxdrv</computeroutput>) and installs it.</para> 437 <para>It builds the VirtualBox kernel modules 438 (<computeroutput>vboxdrv</computeroutput>, 439 <computeroutput>vboxnetflt</computeroutput> and 440 <computeroutput>vboxnetadp</computeroutput>) and installs them.</para> 435 441 </listitem> 436 442 … … 447 453 448 454 <listitem> 449 <para>It creates symbolic links to 455 <para>It creates symbolic links in 456 <computeroutput>/usr/bin</computeroutput> to 457 the executables 450 458 <computeroutput>VirtualBox</computeroutput>, 451 459 <computeroutput>VBoxSDL</computeroutput>, 452 460 <computeroutput>VBoxVRDP</computeroutput>, 453 461 <computeroutput>VBoxHeadless</computeroutput> and 454 <computeroutput>VBoxManage</computeroutput> in 455 <computeroutput>/usr/bin</computeroutput>.</para> 462 <computeroutput>VBoxManage</computeroutput></para> 456 463 </listitem> 457 464 458 465 <listitem> 459 466 <para>It creates 460 <computeroutput>/etc/udev/ 60-vboxdrv.rules</computeroutput>, a467 <computeroutput>/etc/udev/10-vboxdrv.rules</computeroutput>, a 461 468 description file for udev, if that is present, which makes the 462 module accessible to anyone in the group463 <computeroutput>vboxusers</computeroutput> .</para>469 USB devices accessible to all users in the 470 <computeroutput>vboxusers</computeroutput> group.</para> 464 471 </listitem> 465 472 … … 641 648 642 649 <para>To configure the installation process of our .deb and .rpm 643 packages, a file644 <computeroutput>/etc/default/virtualbox</computeroutput> is645 interpreted.The automatic generation of the udev rule can be650 packages, you can create a response file named 651 <computeroutput>/etc/default/virtualbox</computeroutput>. 652 The automatic generation of the udev rule can be 646 653 prevented by the following setting: <screen>INSTALL_NO_UDEV=1</screen> 647 654 The creation of the group vboxusers can be prevented by <screen>INSTALL_NO_GROUP=1</screen> … … 649 656 package installer will not try to build the 650 657 <computeroutput>vboxdrv</computeroutput> kernel module if no module 651 according tothe current kernel was found.</para>658 fitting the current kernel was found.</para> 652 659 </sect3> 653 660 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.