Difference between revisions of "Vnx-rootfsfedora"
(→Configuration) |
|||
Line 92: | Line 92: | ||
and executing: | and executing: | ||
grub2-mkconfig -o /boot/grub2/grub.cfg | grub2-mkconfig -o /boot/grub2/grub.cfg | ||
+ | <li>Disable screensaver if using a GUI</li> | ||
</ul> | </ul> | ||
<li>Create a file /etc/vnx_rootfs_version to store version number and informacion about modification. For example:</li> | <li>Create a file /etc/vnx_rootfs_version to store version number and informacion about modification. For example:</li> |
Revision as of 14:36, 18 April 2013
How to create a KVM Fedora root filesystem for VNX
Follow this procedure to create a KVM Fedora based root filesystem for VNX. The procedure has been tested with Fedora 16 and 14.
Contents
Basic installation
- Create the filesystem disk image:
qemu-img create -f qcow2 vnx_rootfs_kvm_fedora.qcow2 8G
wget ftp://ftp.rediris.es/mirror/fedora/16/Fedora/i386/iso/Fedora-16-i386-DVD.iso cp Fedora-16-i386-DVD.iso /almacen/iso
vnx --create-rootfs vnx_rootfs_kvm_fedora.qcow2 --install-media /almacen/iso/Fedora-16-i386-DVD.iso --mem 768M
Note: add "--arch x86_64" option for 64 bits virtual machines
- Fedora 18:
- Edit /etc/default/grub and add:
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8" GRUB_TERMINAL="serial" GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1"
grub2-mkconfig -o /boot/grub2/grub.cfg
ln -s /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@ttyS0.service
#This service maintains a getty on /dev/ttyS0. start on stopped rc RUNLEVEL=[2345] stop on starting runlevel [016] respawn exec /sbin/agetty /dev/ttyS0 9600 vt100-nav
And add ttyS0 to /etc/securetty file if you want to login root on that console:
echo "ttyS0" >> /etc/securetty
rm /etc/udev/rules.d/70-persistent-net.rules halt -p
Configuration
- Restart the system with the following command:
vnx --modify-rootfs vnx_rootfs_kvm_fedora.qcow2 --update-aced --mem 768M
Note: ignore the errors "timeout waiting for response on VM socket". 768M are needed if you are installing a root filesystem with desktop interface Note: add "--arch x86_64" option for 64 bits virtual machines
virsh console vnx_rootfs_kvm_fedora.qcow2
dhclient eth0
Note: use "ip link show" to know which network interface to use.
yum update yum install perl perl-XML-LibXML acpid udisks
Note: if yum fails, check that the network is working. Maybe you will have to manually execute "dhclient eth0", at least in the case of a minimal installation.
mount /dev/sdb /mnt/ perl /mnt/vnxaced-lf/install_vnxaced
chkconfig --level 3 network on
- Install other services needed, for example, an apache server:
yum install httpd chkconfig httpd off # if you want to avoid automatic start of apache server
yum install telnet wget openssh-clients
AutomaticLoginEnable=true AutomaticLogin=vnx
# Fedora 18 chkconfig firewalld off
# Fedora 16 & 14 chkconfig iptables off chkconfig ip6tables off
GRUB_TIMEOUT=0
and executing:
grub2-mkconfig -o /boot/grub2/grub.cfg
VER=v0.25 OS=Fedora 18 DESC=Basic Fedora 18 root-filesystem without GUI
vnx_haltvnx_halt deletes some caches and log files and optionally lets you write a short message to /etc/vnx_rootfs_version file describing the latest modifications done.
Installing additional software
To install additional software or to modify your root file system, you just have to:
- Start a virtual machine from it:
vnx --modify-rootfs vnx_rootfs_kvm_fedora.qcow2
dhclient eth1
Note: use "ip link show" to know which network interface to use.
vnx_halt
Updating VNXACED
You can automatically update the VNXACE daemon with the following command:
vnx --modify-rootfs vnx_rootfs_kvm_fedora.qcow2 --update-aced -y
If VNXACE daemon is not updated automatically, you can do it manually by accessing the virtual machine console and type:
mount /dev/sdb /mnt/ perl /mnt/vnxaced-lf/install_vnxaced