|Last Update:||Spring 2015|
|Operating system:||Debian 8.0 Jessie|
|CPU:||2x Intel Xeon E5410 @ 2.33GHz|
|RAM:||16 GB DDR2|
Phoenix has older drives than eevee, but several of them have never been used prior to being installed in Phoenix. Additionally, all 4 drives, which are 1 TB each, have been configured in RAID6 to allow for up to 2 failed drives and provide a total of 2 TB of storage. This is twice the amount of storage as eevee currently has, with twice the tolerance for failure.
Generally, we followed the instructions on the debian wiki.
Things to install
apt-get install htop vim sudo qemu-kvm libvirt-bin virtinst
Network Bridge Setup
In order for the VMs to be on our LAN, a bridge must be set up as follows:
# The loopback network interface auto lo iface lo inet loopback auto br0 iface br0 inet static bridge_ports eth0 address 188.8.131.52 netmask 255.255.255.0 gateway 184.108.40.206 broadcast 220.127.116.11 dns-nameservers 18.104.22.168 22.214.171.124
Manual set up:
1) Create new bridge iterface "brctl addbr <bridge_name>"
2) Add existing interface to bridge "brctl addif <bridge_name> <iterface_name>"
3) Bring bridge up "ifconfig <bridge_name> up"
Bridging interfaces will cause the interfaces used to not have an ip address even if they are up. The bridge interface will contain an ip address.
Migration from eevee
To migrate a VM from eevee:
Put iso in /var/lib/libvirt/isos
Put xml file from dump into /var/lib/libvirt/qemu
(The dump can be had by running virsh dumpxml > vm_name.xml on eevee
(The xml file will need to be edited, see the debian wiki)
Put disk image in /var/lib/libvirt/images
virsh define <Your VM Name>.xml