qubes-doc/QubesBuilder.md

layout	title	permalink
wiki	QubesBuilder	/wiki/QubesBuilder/

Building Qubes from scratch

We have recently created a fully automated build system for Qubes, that downloads, builds and packages all the Qubes components, and finally should spit out a ready-to-use installation ISO.

In order to use it one should use an rpm-based distro, like Fedora :) and should ensure the following packages are installed:

• git
• createrepo
• rpm-build
• make
• wget
• rpmdevtools
• pandoc

Unusually one can install those packages by just issuing:

sudo yum install git createrepo rpm-build make wget rpmdevtools pandoc

The build system creates build environments in chroots and so no other packages are needed on the host. All files created by the build system are contained within the qubes-builder directory. The full build requires some 25GB of free space, so keep that in mind when deciding where to place this directory.

The build system is configured via builder.conf file -- one should copy the attached builder.conf.default, and modify it as needed, e.g.:

cp builder.conf.default builder.conf 
# edit the builder.conf file and set the following variables: 
# (make sure to leave no spaces around '=' sign!) 
NO_SIGN=1

# As time of writing this, the default for Qubes 2 Dom0 is fc18
# and VMs is fc18 so if you want to build Qubes 2
DIST_DOM0=fc18
DISTS_VM=fc18

One additional useful requirement is that 'sudo root' work without any prompt, which is default on most distros (e.g. 'sudo bash' brings you the root shell without asking for any password). This is important as the builder needs to switch to root and then back to user several times during the build process.

Additionally, if building with signing enabled (so NO_SIGN is not set), one must adjust ~/.rpmmacro file so that it point to the GPG key used for package signing, e.g.:

%_signature gpg
%_gpg_path /home/user/.gnupg
%_gpg_name AC1BF9B3  # <-- Key ID used for signing

It is also recommended to use an empty passphrase for the private key used for signing. Contrary to a popular belief, this doesn't affect your key or sources security -- if somebody compromised your system, then the game is over, whether you use additional passphrase for the key or not.

So, to build Qubes one would do:

# Import the Qubes master key 
gpg --recv-keys 0x36879494 

# Verify its fingerprint, set as 'trusted'. 
# This is described here: 
# https://wiki.qubes-os.org/trac/wiki/VerifyingSignatures 

wget http://keys.qubes-os.org/keys/qubes-developers-keys.asc 
gpg --import qubes-developers-keys.asc 

git clone git://git.qubes-os.org/joanna/qubes-builder.git qubes-builder 
cd qubes-builder 

cp builder.conf.default builder.conf 
# edit the builder.conf file and set the following variables: 
# (make sure to leave no spaces around '=' sign!) 
# NO_SIGN="1"

# And now to build all Qubes rpms (this will take a few hours): 

make qubes 

# ... and then to build the ISO 

make iso 

And this should produce a shiny new ISO.

You can also build selected component separately. Eg. to compile only gui virtualization agent/daemon:

make gui

Full list you can get from make help. For advanced use and preparing sources for use with QubesBuilder take a look at QubesBuilderDetails page.

Making customized build

Manual source modification

If you want to somehow modify sources, you can also do it, here are some basic steps:

1. Download qubes-builder as described above (if you want to use marmarek's branches, you should also download qubes-builder from his repo - replace 'joanna' with 'marmarek' in above git clone command)

2. Edit builder.conf (still the same as above), some useful additions:

   • As time of writing this, the default is fc15, but latest supported is fc17, so switch to newer one

     DISTS_VM="fc17"
     

   • You can also set GIT_SUBDIR="marmarek" to use my repo instead of "mainstream" - it contains newer (but less tested) versions

3. Download unmodified sources

   make get-sources
   

4. Make your modifications here

5. Build the Qubes make qubes actually is just meta target which build all required components in correct order

   grep ^qubes: Makefile
   qubes: get-sources xen core kernel gui addons docs template kde-dom0 installer qubes-manager dom0-updates sign-all
   

get-sources is already done, so continue with the next one. You can skip sign-all if you've disabled signing

make xen core kernel gui addons docs template kde-dom0 installer qubes-manager dom0-updates

1. build iso installation image

   make iso
   

Non-default git branches

Below example values (especially branch names) are outdated, but config options and steps are still valid

You can use above tool to build Qubes with some components modified. Besides manual source modification, it is possible to use non-default git repositories, or just another branches. For example to try (unofficial, not supported) configuration with newer kernel and xorg server, you can add to builder.conf:

GIT_SUBDIR="marmarek"
BRANCH_kernel=devel-3.4
BRANCH_dom0_updates=devel/xserver-1.12

# NO_SIGN=1 can also be useful

before doing "make qubes". If you built anything before this modification, you should remove qubes-src directory first to fetch the sources again (this will also remove packages compiled before). Above devel/xserver-1.12 branch require some modification of Makefile in qubes-builder. Find dom0-updates target and replace it with:

dom0-updates:
        MAKE_TARGET="stage0" ./build.sh $(DIST_DOM0) dom0-updates
        MAKE_TARGET="stage1" ./build.sh $(DIST_DOM0) dom0-updates
        MAKE_TARGET="stage2" ./build.sh $(DIST_DOM0) dom0-updates
        MAKE_TARGET="stage3" ./build.sh $(DIST_DOM0) dom0-updates
        MAKE_TARGET="stage4" ./build.sh $(DIST_DOM0) dom0-updates

Then you can build qubes as usual.

There is one issue with above experimental version: new Xorg server have different cmdline options, so after installation one config file must be edited to reflect this change. At first system startup hit ESC while progress bar is displayed - to switch to detailed boot view. After you set up user account etc, you must fix KDM config file.

1. Switch to tty2 (Alt-F2)

2. Login as just created user

3. Switch to root (sudo -s)

4. Edit /etc/kde/kdm/kdmrc

   • locate "ServerArgsLocal?=-nr -nolisten tcp" line
   • remove "-nr" from it

5. Restart login manager (now it will start and allow you to login graphically): initctl restart prefdm