We are using a KVM based setup for research devices and have installed Zotac ZBoxes which have quite some performance but are not as ruggedized as Alix Boards. The good thing about these boxes is that they have hardware virtualization support so they enable us to combine the research device with the connecting community device into one piece of hardware. The setup got tested on Zotac ZBox ID-81E, ID-82 and Zotac ZBox nano ID61.
For our new reasearch devices we want to switch to a newGigabyte GA-J1800N-D2H based system with the Intel Celeron J1800 processor. CPU performance should be sligtly lower than a Zotec Box with Intel i3, but it still support VT-x and is much cheaper.
Make sure you have installed the latest BIOS. general BIOS Update Instructions.
To enable booting without attached display / monitor make sure to set correct Gigabyte Mainboard Bios Settings.
GRUB_TIMEOUTto 2 seconds
$ wget http://build.ffgraz.net/deb/ffgraz-apt.asc -O - | apt-key add -
$ aptitude update
$ aptitude install sudo screen openssh-server dstat htop less psmisc tcpdump nmap lsof mtr-tiny debian-goodies olsrd olsrd-plugins ntp qemu-kvm libvirt-bin vim zsh acpid isc-dhcp-server
$ aptitude install firmware-linux
$ aptitude install -t wheezy-backports linux-image-amd64 firmware-linux firmware-realtek
$ adduser <username> sudo(username which got created by the installer)
1:2345:respawn:/sbin/getty –noclear 38400 tty1
$ sudo init q
This makes sure the update doesn't hang while restarting important services like olsrd
$ sudo mkdir /home/confine
$ cd /home/confine
rd.xmlwith following content rd.xml
wget --user <your controller user> --ask-password --auth-no-challenge --no-check-certificate "<link to the created firmware iamge>"''
zcat confine-firmware-*.img.gz | sudo dd of=/dev/vm/rd bs=4096 conv=fsync
$ sudo virsh
virsh # define rd.xml
virsh # autostart rd
virsh # start rd –console
$ opkg update
$ opkg install kmod-acpi-button
$ opkg install acpid
$ sudo virsh console rd
$ sudo virsh shutdown rd
$ sudo virsh start rd
rebootinside the VM works as expected
haltwill shutdown the virtual machine but not exit KVM, if your VM hangs at
system haltedyou can use the following to exit KVM
$ sudo virsh destroy rd