Difference between pages "ZFS Install Guide" and "VirtualBox"

From Funtoo
(Difference between pages)
Jump to: navigation, search
m (Add filesystems to /etc/fstab)
 
(Created page with "<code>VirtualBox</code> is an application that allows to run a guest O/S inside a host O/S. == Glossary of Terms == :;Host O/S : system running on computer you are actually ...")
 
Line 1: Line 1:
== Introduction ==
+
<code>VirtualBox</code> is an application that allows to run a guest O/S inside a host O/S.
  
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.
+
== Glossary of Terms ==
  
=== Introduction to ZFS ===
+
:;Host O/S : system running on computer you are actually on;
 +
:;Guest O/S : system indtalled within VirtualBox;
 +
:;Guest Additions : drivers for the Guest O/S.
  
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:
+
== Versions of VirtualBox ==
  
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
+
VirtualBox is available in two versions :
  
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
+
# '''Source based package''' : app-emulation/virtualbox;
 +
# '''Binary package''' : app-emeulation/virtualbox-bin.
  
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
+
Binary package contains extensions which are not available with the source one. When we install the source based package, we must refer to the USE flags list hereafter.
  
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
+
== USE flags ==
  
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
+
{| class="wikitable" style="margin-left: 1em; margin-right: 1em;" width=80%
 +
! width="20%" | Use flag
 +
! width="10%" | Default
 +
! width="10%" | Recommended
 +
! width="60%" | Description
 +
|-
 +
| style="text-align:center;" |additions
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |Yes
 +
| Install Guest System Tools ISO.
 +
|-
 +
| style="text-align:center;" |alsa
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |Yes
 +
| Add support for media-libs/alsa-lib (Advanced Linux Sound Architecture).
 +
|-
 +
| style="text-align:center;" |doc
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |
 +
| Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally.
 +
|-
 +
| style="text-align:center;" |extensions
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |Yes
 +
| Install extension module packages.
 +
|-
 +
| style="text-align:center;" |headless
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |
 +
| Build without any graphic frontend.
 +
|-
 +
| style="text-align:center;" |java
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |No
 +
| Add support for Java.
 +
|-
 +
| style="text-align:center;" |opengl
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Add support for OpenGL (3D graphics).
 +
|-
 +
| style="text-align:center;" |pam
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |Yes
 +
| Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip.
 +
|-
 +
| style="text-align:center;" |pulseaudio
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Add support for PulseAudio sound server.
 +
|-
 +
| style="text-align:center;" |python
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Add optional support/bindings for the Python language.
 +
|-
 +
| style="text-align:center;" |python_single_target_python2_7
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Build for Python 2.7 only.
 +
|-
 +
| style="text-align:center;" |python_targets_python2_7
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Build with Python 2.7
 +
|-
 +
| style="text-align:center;" |qt4
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |Yes
 +
| Add support for the Qt GUI/Application Toolkit version 4.x. No GUI when not set.
 +
|-
 +
| style="text-align:center;" |sdk
 +
| style="text-align:center;" |Yes
 +
| style="text-align:center;" |
 +
| Enable building of SDK.
 +
|-
 +
| style="text-align:center;" |vboxwebsrv
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |No
 +
| Build and install the VirtualBox webservice.
 +
|-
 +
| style="text-align:center;" |vnc
 +
| style="text-align:center;" |No
 +
| style="text-align:center;" |
 +
| Enable VNC (remote desktop viewer) support.
 +
|}
  
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
+
{{fancyimportant|Depending on desktop environment, some USE flags may already be set or unset. Set USE flags as per '''Recommended''' column when unset.}}
  
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
+
== Installation ==
  
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
+
{{fancyimportant|This tutorial deals with installation of source based package.}}
 
+
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
+
 
+
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.
+
 
+
The only area where btrfs is ahead of ZFS is in the area of small file
+
efficiency. btrfs supports a feature called block suballocation, which
+
enables it to store small files far more efficiently than ZFS. It is
+
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol
+
to obtain similar benefits (with arguably better data integrity) when
+
dealing with many small files (e.g. the portage tree).
+
 
+
=== Disclaimers ===
+
 
+
{{fancywarning|This guide is a work in progress. Expect some quirks.}}
+
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}
+
 
+
== Video Tutorial ==
+
 
+
As a companion to the installation instructions below, a YouTube video tutorial is now available:
+
 
+
{{#widget:YouTube|id=SWyThdxNoP8|width=640|height=360}}
+
 
+
{{fancyimportant|'''The video and guide are currently out of sync. The video has newer instructions. The guide needs to be updated.'''}}
+
 
+
== Downloading the ISO (With ZFS) ==
+
In order for us to install Funtoo on ZFS, you will need an environment that already provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS included.
+
 
+
<pre>
+
Name: sysresccd-4.0.1_zfs_0.6.2.iso  (545 MB)
+
Release Date: 2014-02-25
+
md5sum 01f4e6929247d54db77ab7be4d156d85
+
</pre>
+
 
+
 
+
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
+
 
+
== Creating a bootable USB from ISO (From a Linux Environment) ==
+
After you download the iso, you can do the following steps to create a bootable USB:
+
  
 
<console>
 
<console>
Make a temporary directory
+
###i## echo ">=app-emulation/virtualbox-extpack-oracle-4.3.8 PUEL" >> /etc/portage/package.license/virtualbox
# ##i##mkdir /tmp/loop
+
###i## emerge --ask --verbose app-emulation/virtualbox
 +
</console>
  
Mount the iso
+
Installation of <code>app-emulation/virtualbox</code> implies <code>app-emulation/virtualbox-extpack-oracle</code>. That is why PUEL license must be enabled.
# ##i##mount -o ro,loop /root/sysresccd-4.0.1_zfs_0.6.2.iso /tmp/loop
+
  
Run the usb installer
+
== Guest Additions ==
# ##i##/tmp/loop/usb_inst.sh
+
</console>
+
  
That should be all you need to do to get your flash drive working.
+
Make sure that user running X session belongs to <code>vboxguest</code> group. Create group when it does not exist. Add user to the group. That will enable :
  
== Booting the ISO ==
+
*Shared clipboard;
 
+
*Display resizing;
{{fancywarning|'''When booting into the ISO, Make sure that you select the "Alternate 64 bit kernel (altker64)". The ZFS modules have been built specifically for this kernel rather than the standard kernel. If you select a different kernel, you will get a fail to load module stack error message.'''}}
+
*Seamless mode;
 
+
*Drag & Drop.
== Creating partitions ==
+
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.
+
 
+
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.
+
 
+
==== gdisk (GPT Style) ====
+
 
+
'''A Fresh Start''':
+
 
+
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.
+
We will also assume that <tt>/dev/sda</tt> is the target drive.<br />
+
  
 
<console>
 
<console>
# ##i##sgdisk -Z /dev/sda
+
###i## groupadd vboxguest
 +
###i## gpasswd -a ''user'' vboxguest
 
</console>
 
</console>
  
{{fancywarning|This is a destructive operation and the program will not ask you for confirmation! Make sure you really don't want anything on this disk.}}
+
=== Windows Guests ===
  
Now that we have a clean drive, we will create the new layout.
+
You must enable <code>additions</code> USE flag when you intend to install Windows as a guest O/S. That will also install the ISO image containing all necessary Windows guest drivrers.
  
First open up the application:
+
=== Linux Guests ===
  
<console>
+
If you want to run Funtoo GNU/Linux as a guest O/S, emerge <code>app-emulation/virtualbox-guest-additions</code> in the Funtoo GNU/Linux guest O/S. For other GNU/Linux, please refer to [https://www.virtualbox.org/manual/ch04.html#idp11274368 VirtualBox documentation].
# ##i##gdisk /dev/sda
+
</console>
+
 
+
'''Create Partition 1''' (boot):
+
<console>
+
Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+250M ↵
+
Hex Code: ##i##↵
+
</console>
+
 
+
'''Create Partition 2''' (BIOS Boot Partition):
+
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+32M ↵
+
Hex Code: ##i##EF02 ↵
+
</console>
+
 
+
'''Create Partition 3''' (ZFS):
+
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##↵
+
Hex Code: ##i##bf00 ↵
+
 
+
Command: ##i##p ↵
+
 
+
Number  Start (sector)    End (sector)  Size      Code  Name
+
  1            2048          514047  250.0 MiB  8300  Linux filesystem
+
  2          514048          579583  32.0 MiB    EF02  BIOS boot partition
+
  3          579584      1953525134  931.2 GiB  BF00  Solaris root
+
 
+
Command: ##i##w ↵
+
</console>
+
  
 +
== Post Installation ==
  
=== Format your /boot partition ===
+
You will not be able to run and use VirtualBox as a regular user if you are not a member of the <code>vboxusers</code> group.
  
 
<console>
 
<console>
# ##i##mkfs.ext2 -m 1 /dev/sda1
+
###i## gpasswd -a ''user'' vboxusers
 
</console>
 
</console>
  
=== Encryption (Optional) ===
+
You must re-log so changes take effect.
If you want encryption, then create your encrypted vault(s) now by doing the following:
+
  
<console>
+
=== Loading Modules ===
# ##i##cryptsetup luksFormat /dev/sda3
+
# ##i##cryptsetup luksOpen /dev/sda3 vault_1
+
</console>
+
  
{{fancywarning|On some machines, a combination of ZFS and LUKS has caused instability and system crashes.}}
+
Required and optional modules must be loaded before launching VirtualBox. You can do that as root or upon boot.
  
=== Create the zpool ===
+
{{fancynote|<code>vboxnetadp</code> and <code>vboxnetflt</code> are optional.}}
We will first create the pool. The pool will be named `tank` and the disk will be aligned to 4096 (using ashift=12)
+
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo tank /dev/sda3</console>
+
  
{{fancyimportant|If you are using encrypted root, change '''/dev/sda3 to /dev/mapper/vault_1'''.}}
+
==== As root ====
 
+
{{fancynote| If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''.}}
+
 
+
=== Create the zfs datasets ===
+
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: <tt>/home</tt>, <tt>/var</tt>, <tt>/usr/src</tt>, and <tt>/usr/portage</tt>.
+
  
 
<console>
 
<console>
Create some empty containers for organization purposes, and make the dataset that will hold /
+
###i## modprobe vboxdrv
# ##i##zfs create -p tank/funtoo
+
###i## modprobe vboxnetadp
# ##i##zfs create -o mountpoint=/ tank/funtoo/root
+
###i## modprobe vboxnetflt
 
+
Optional, but recommended datasets: /home
+
# ##i##zfs create -o mountpoint=/home tank/funtoo/home
+
 
+
Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
+
# ##i##zfs create -o mountpoint=/usr/src tank/funtoo/src
+
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off tank/funtoo/portage
+
# ##i##zfs create -o mountpoint=/usr/portage/distfiles tank/funtoo/portage/distfiles
+
# ##i##zfs create -o mountpoint=/usr/portage/packages tank/funtoo/portage/packages
+
 
</console>
 
</console>
  
=== Create your swap zvol ===
+
==== Upon boot OpenRC ====
For modern machines that have greater than 4 GB of RAM, A swap size of 2G should be enough. However if your machine doesn't have a lot of RAM, the rule of thumb is either 2x the RAM or RAM + 1 GB.
+
  
For this tutorial we will assume that it is a newer machine and make a 2 GB swap.
+
Edit <code>/etc/conf.d/modules</code> :
  
<console>
+
<pre>modules="vboxdrv vboxnetadp vboxnetflt"</pre>
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 2G tank/swap
+
</console>
+
  
=== Format your swap zvol ===
+
==== Upon boot systemd ====
<console>
+
# ##i##mkswap -f /dev/zvol/tank/swap
+
# ##i##swapon /dev/zvol/tank/swap
+
</console>
+
 
+
Now we will continue to install funtoo.
+
 
+
== Installing Funtoo ==
+
 
+
=== Pre-Chroot ===
+
  
 
<console>
 
<console>
Go into the directory that you will chroot into
+
###i## echo 'vboxdrv' >> /etc/modules-load.d/virtualbox.conf
# ##i##cd /mnt/funtoo
+
###i## echo 'vboxnetadp' >> /etc/modules-load.d/virtualbox.conf
 
+
###i## echo 'vboxnetflt' >> /etc/modules-load.d/virtualbox.conf
Make a boot folder and mount your boot drive
+
# ##i##mkdir boot
+
# ##i##mount /dev/sda1 boot
+
 
</console>
 
</console>
  
[[Funtoo_Linux_Installation|Now download and extract the Funtoo stage3 ...]]
+
=== Kernel Driver ===
 
+
Once you've extracted the stage3, do a few more preparations and chroot into your new funtoo environment:
+
 
+
<console>
+
Bind the kernel related directories
+
# ##i##mount -t proc none proc
+
# ##i##mount --rbind /dev dev
+
# ##i##mount --rbind /sys sys
+
 
+
Copy network settings
+
# ##i##cp -f /etc/resolv.conf etc
+
 
+
Chroot into Funtoo
+
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l
+
</console>
+
 
+
=== In Chroot ===
+
 
+
<console>
+
Create a symbolic link to your mountpoints
+
# ##i##ln -sf /proc/mounts /etc/mtab
+
 
+
Sync your tree
+
# ##i##emerge --sync
+
</console>
+
 
+
=== Add filesystems to /etc/fstab ===
+
 
+
Before we continue to compile and or install our kernel in the next step, we will edit the <tt>/etc/fstab</tt> file because if we decide to install our kernel through portage, portage will need to know where our <tt>/boot</tt> is, so that it can place the files in there.
+
 
+
Edit <tt>/etc/fstab</tt>:
+
 
+
<pre>
+
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
+
 
+
/dev/sda1              /boot          ext2            defaults        0 2
+
/dev/zvol/tank/swap    none            swap            sw              0 0
+
</pre>
+
 
+
== Kernel Configuration ==
+
To speed up this step, you can install "bliss-kernel" since it's already properly configured for ZFS and a lot of other configurations. The kernel is also compiled and ready to go. To install {{Package|sys-kernel/bliss-kernel}} type the following:
+
 
+
<console>
+
# ##i##emerge bliss-kernel
+
</console>
+
 
+
Now make sure that your <tt>/usr/src/linux symlink</tt> is pointing to this kernel by typing the following:
+
<console>
+
# ##i##eselect kernel list
+
Available kernel symlink targets:
+
[1]  linux-3.10.10-FB.01 *
+
</console>
+
You should see a star next to the bliss-kernel version you installed. In this case it was 3.10.10-FB.01. If it's not set, you can type '''eselect kernel set #'''.
+
 
+
== Installing the ZFS userspace tools and kernel modules ==
+
Emerge {{Package|sys-fs/zfs}}, {{Package|sys-kernel/spl}}, and {{Package|sys-fs/zfs-kmod}}:
+
<console># ##i##emerge zfs </console>
+
Check to make sure that the zfs tools are working, the <code>zpool.cache</code> file that you copied before should be displayed.
+
 
+
{{Fancynote| SPL stands for: Solaris Porting Layer}}
+
<console>
+
# ##i##zpool status
+
# ##i##zfs list
+
</console>
+
 
+
If everything worked, continue.
+
 
+
== Install the bootloader ==
+
=== GRUB 2 ===
+
Before you do this, make sure this checklist is followed:
+
* Installed kernel and kernel modules
+
* Installed zfs package from the tree
+
* <code>/dev</code>, <code>/proc</code>, <code>/sys</code> are mounted in the chroot environment
+
 
+
Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.
+
 
+
<console># ##i##echo "sys-boot/grub libzfs" >> /etc/portage/package.use</console>
+
 
+
Then we will compile grub2:
+
 
+
<console># ##i##emerge grub</console>
+
 
+
Once this is done, you can check that grub is version 2.00 by doing the following command:
+
<console>
+
# ##i##grub-install --version
+
grub-install (GRUB) 2.00
+
</console>
+
 
+
Now try to install {{Package|sys-boot/grub}}:
+
<console>
+
# ##i##grub-install --recheck /dev/sda
+
</console>
+
 
+
You should receive the following message:
+
<console>
+
Installation finished. No error reported.
+
</console>
+
 
+
If not, then go back to the above checklist.
+
 
+
=== LILO ===
+
Before you do this, make sure the following checklist is followed:
+
* <code>/dev</code>, <tt>/proc</tt> and <tt>/sys</tt> are mounted.
+
* Installed the {{Package|sys-fs/zfs}} package from the tree.
+
Once the above requirements are met, LILO can be installed.
+
 
+
Now we will install {{Package|sys-boot/lilo}}.
+
<console># ##i##emerge sys-boot/lilo</console>
+
Once the installation of LILO is complete we will need to edit the <tt>/etc/lilo.conf</tt> file:
+
 
+
 
+
<pre>
+
boot=/dev/sda
+
prompt
+
timeout=4
+
default=Funtoo
+
 
+
image=/boot/bzImage
+
      label=Funtoo
+
      read-only
+
      append="root=tank/os/funtoo/root"
+
      initrd=/boot/initramfs
+
</pre>
+
All that is left now is to install the bootcode to the MBR.
+
 
+
This can be accomplished by running:
+
<console># ##i##/sbin/lilo</console>
+
If it is successful you should see:
+
<console>
+
Warning: LBA32 addressing assumed
+
Added Funtoo + *
+
One warning was issued
+
</console>
+
 
+
== Create the initramfs ==
+
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.
+
 
+
=== genkernel ===
+
<console>
+
# ##i##emerge sys-kernel/genkernel
+
# You only need to add --luks if you used encryption
+
# ##i##genkernel --zfs --luks initramfs
+
</console>
+
 
+
=== Bliss Initramfs Creator ===
+
If you are encrypting your drives, then add the "luks" use flag to your package.use before emerging:
+
 
+
<console>
+
# ##i##echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use
+
</console>
+
 
+
Now install the creator:
+
 
+
<console>
+
# ##i##emerge bliss-initramfs
+
</console>
+
 
+
 
+
Then go into the install directory, run the script as root, and place it into /boot:
+
<console># ##i##cd /opt/bliss-initramfs
+
# ##i##./createInit
+
# ##i##mv initrd-<kernel_name> /boot
+
</console>
+
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.
+
 
+
== Using boot-update ==
+
=== /boot on separate partition ===
+
If you created a separate non-zfs partition for boot then configuring boot-update is almost exactly the same as a normal install except that auto detection for root does not work. You must tell boot-update what your root is.
+
==== Genkernel ====
+
If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
+
Example entry for <tt>/etc/boot.conf</tt>:
+
 
+
<pre>
+
"Funtoo ZFS" {
+
        kernel vmlinuz[-v]
+
        initrd initramfs-genkernel-x86_64[-v]
+
        params real_root=ZFS=tank/os/funtoo/root
+
        params += dozfs=force
+
        # Also add 'params += crypt_root=/dev/sda3' if you used encryption
+
        # Adjust the above setting to your system if needed
+
}
+
</pre>
+
 
+
==== Bliss Initramfs Creator ====
+
If you used the Bliss Initramfs Creator then all you need to do is add 'root=<root>' to your params.
+
Example entry for <tt>/etc/boot.conf</tt>:
+
 
+
<pre>
+
"Funtoo ZFS" {
+
        kernel vmlinuz[-v]
+
        initrd initrd[-v]
+
        params root=tank/os/funtoo/root quiet
+
        # If you have an encrypted device with a regular passphrase,
+
        # you can add the following line
+
        params += enc_root=/dev/sda3 enc_type=pass
+
}
+
</pre>
+
 
+
After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
+
<console>
+
###i## boot-update
+
</console>
+
 
+
=== /boot on ZFS ===
+
TBC - pending update to boot-update to support this
+
 
+
== Final configuration ==
+
=== Add the zfs tools to openrc ===
+
<console># ##i##rc-update add zfs boot</console>
+
 
+
=== Clean up and reboot ===
+
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.
+
 
+
<console>
+
Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
+
# ##i##cd /
+
# ##i##rm stage3-latest.tar.xz
+
 
+
Set your root password
+
# ##i##passwd
+
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!
+
 
+
Get out of the chroot environment
+
# ##i##exit
+
 
+
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
+
# ##i##umount -l proc dev sys boot
+
 
+
Turn off the swap
+
# ##i##swapoff /dev/zvol/tank/swap
+
 
+
Export the zpool
+
# ##i##cd /
+
# ##i##zpool export tank
+
 
+
Reboot
+
# ##i##reboot
+
</console>
+
 
+
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}
+
 
+
and that should be enough to get your system to boot on ZFS.
+
 
+
== After reboot ==
+
=== Create initial ZFS Snapshot ===
+
Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.
+
 
+
To take the snapshot of your system, type the following:
+
<console># ##i##zfs snapshot -r tank@install</console>
+
 
+
To see if your snapshot was taken, type:
+
<console># ##i##zfs list -t snapshot</console>
+
  
If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):
+
Each time a new kernel is installed, <code>vboxdrv</code> kernel module must be recompiled. To ensure Portage knows about that, look at <code>/var/lib/module-rebuild/moduledb</code>. The following record must be present.
<console># ##i##zfs rollback tank/os/funtoo/root@install</console>
+
  
{{fancyimportant|'''For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the [[ZFS_Fun|ZFS Fun]] page.'''}}
+
<pre>a:1:app-emulation/virtualbox-modules-''version''</pre>
  
[[Category:HOWTO]]
+
Running <code>emerge @module-rebuild</code> will recompile VirtualBox driver after installation of new kernel.
[[Category:Filesystems]]
+
[[Category:Featured]]
+
  
__NOTITLE__
+
It is strongly recommended to install <code>sys-kernel<nowiki>/</nowiki>dkms</code>. This package keeps track of Linux kernel changes. It recompiles <code>vboxdrv</code> if necessary.

Revision as of 20:06, 4 March 2014

VirtualBox is an application that allows to run a guest O/S inside a host O/S.

Contents

Glossary of Terms

Host O/S 
system running on computer you are actually on;
Guest O/S 
system indtalled within VirtualBox;
Guest Additions 
drivers for the Guest O/S.

Versions of VirtualBox

VirtualBox is available in two versions :

  1. Source based package : app-emulation/virtualbox;
  2. Binary package : app-emeulation/virtualbox-bin.

Binary package contains extensions which are not available with the source one. When we install the source based package, we must refer to the USE flags list hereafter.

USE flags

Use flag Default Recommended Description
additions Yes Yes Install Guest System Tools ISO.
alsa Yes Yes Add support for media-libs/alsa-lib (Advanced Linux Sound Architecture).
doc No Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally.
extensions No Yes Install extension module packages.
headless No Build without any graphic frontend.
java No No Add support for Java.
opengl Yes Add support for OpenGL (3D graphics).
pam Yes Yes Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip.
pulseaudio Yes Add support for PulseAudio sound server.
python Yes Add optional support/bindings for the Python language.
python_single_target_python2_7 Yes Build for Python 2.7 only.
python_targets_python2_7 Yes Build with Python 2.7
qt4 Yes Yes Add support for the Qt GUI/Application Toolkit version 4.x. No GUI when not set.
sdk Yes Enable building of SDK.
vboxwebsrv No No Build and install the VirtualBox webservice.
vnc No Enable VNC (remote desktop viewer) support.
Important: Depending on desktop environment, some USE flags may already be set or unset. Set USE flags as per Recommended column when unset.

Installation

Important: This tutorial deals with installation of source based package.
# echo ">=app-emulation/virtualbox-extpack-oracle-4.3.8 PUEL" >> /etc/portage/package.license/virtualbox
# emerge --ask --verbose app-emulation/virtualbox

Installation of app-emulation/virtualbox implies app-emulation/virtualbox-extpack-oracle. That is why PUEL license must be enabled.

Guest Additions

Make sure that user running X session belongs to vboxguest group. Create group when it does not exist. Add user to the group. That will enable :

  • Shared clipboard;
  • Display resizing;
  • Seamless mode;
  • Drag & Drop.
# groupadd vboxguest
# gpasswd -a ''user'' vboxguest

Windows Guests

You must enable additions USE flag when you intend to install Windows as a guest O/S. That will also install the ISO image containing all necessary Windows guest drivrers.

Linux Guests

If you want to run Funtoo GNU/Linux as a guest O/S, emerge app-emulation/virtualbox-guest-additions in the Funtoo GNU/Linux guest O/S. For other GNU/Linux, please refer to VirtualBox documentation.

Post Installation

You will not be able to run and use VirtualBox as a regular user if you are not a member of the vboxusers group.

# gpasswd -a ''user'' vboxusers

You must re-log so changes take effect.

Loading Modules

Required and optional modules must be loaded before launching VirtualBox. You can do that as root or upon boot.

Note: vboxnetadp and vboxnetflt are optional.

As root

# modprobe vboxdrv
# modprobe vboxnetadp
# modprobe vboxnetflt

Upon boot OpenRC

Edit /etc/conf.d/modules :

modules="vboxdrv vboxnetadp vboxnetflt"

Upon boot systemd

# echo 'vboxdrv' >> /etc/modules-load.d/virtualbox.conf
# echo 'vboxnetadp' >> /etc/modules-load.d/virtualbox.conf
# echo 'vboxnetflt' >> /etc/modules-load.d/virtualbox.conf

Kernel Driver

Each time a new kernel is installed, vboxdrv kernel module must be recompiled. To ensure Portage knows about that, look at /var/lib/module-rebuild/moduledb. The following record must be present.

a:1:app-emulation/virtualbox-modules-''version''

Running emerge @module-rebuild will recompile VirtualBox driver after installation of new kernel.

It is strongly recommended to install sys-kernel/dkms. This package keeps track of Linux kernel changes. It recompiles vboxdrv if necessary.