2.7 KiB
| layout | title | permalink | redirect_from |
|---|---|---|---|
| doc | FedoraTemplateUpgrade | /doc/FedoraTemplateUpgrade/ | /wiki/FedoraTemplateUpgrade/ |
Upgrade of Fedora template
This instruction in simplified version of official Fedora instruction. Note that only "yum" method will work in Qubes template VM (if you are curious why: mostly because template VM does not have own bootloader).
Upgrading Fedora 18 to Fedora 20
Commands to run in dom0 console (you can do the same from Qubes Manager):
{% highlight trac-wiki %} qvm-clone fedora-18-x64 fedora-20-x64 qvm-run -a fedora-20-x64 gnome-terminal {% endhighlight %}
Commands to run in new fedora-20-x64 template:
{% highlight trac-wiki %} sudo yum --releasever=20 distro-sync poweroff {% endhighlight %}
If you have installed a lot of software in your template, it may happen that you don't have enough disk space for upgrade. Yum will tell you this just after confirming the operation (before it change anything to your system). In that case you need to provide some "external" place for yum cache (uses about 2GB during upgrade). For example attach virtual disk stored in some file. Prepare the file in dom0:
{% highlight trac-wiki %} truncate -s 5GB /var/tmp/template-upgrade-cache.img qvm-block -A fedora-20-x64 dom0:/var/tmp/template-upgrade-cache.img {% endhighlight %}
Then use it in template:
{% highlight trac-wiki %} sudo mkfs.ext4 /dev/xvdi sudo mount /dev/xvdi /mnt/removable sudo yum --releasever=20 --setopt=cachedir=/mnt/removable distro-sync {% endhighlight %}
After upgrade is finished, you can remove /var/tmp/template-upgrade-cache.img file.
Compacting templates root.img
fstrim, nor "discard" mount option do not work on template root fs, so when some file is removed in the template, space isn't freed in dom0. This means that template will use about twice a space that is really need after upgrade.
If you have at least qubes-core-dom0-2.1.68 installed, you can use qvm-trim-template tool. Otherwise use instructions below.
You can compact root.img in the "old way", you'll need about 15GB (template's max size + really used space there) in dom0 for this operation: Start the template, fill all the free space with zeros, for example with:
{% highlight trac-wiki %} dd if=/dev/zero of=/var/tmp/zero (wait for "No space left on device" error) rm -f /var/tmp/zero {% endhighlight %}
Then shutdown template and all VMs based on it. Go into template directory in dom0 (/var/lib/qubes/vm-templates/fedora-20-x64 or so) and issue:
{% highlight trac-wiki %} cp --sparse=always root.img root.img.new mv root.img.new root.img {% endhighlight %}
Done.