Difference between revisions of "Gourd CentOS 6 Migration"
(Notes install on Tomato drive) |
(VM notes) |
||
| Line 2: | Line 2: | ||
The steps to take is to first install a gourd clone on Tomato. Virtualize a Roentgen clone on Tomato. Once everything is all setup we can simply swap the hard drive on Gourd with Tomato's harddrive. | The steps to take is to first install a gourd clone on Tomato. Virtualize a Roentgen clone on Tomato. Once everything is all setup we can simply swap the hard drive on Gourd with Tomato's harddrive. | ||
| + | |||
| + | =VM Specs= | ||
| + | Specs were copied from the information on wiki pages at the time. | ||
| + | |||
| + | ==Base-Clone== | ||
| + | Minimal install of CentOS 7.0-1406 with two network cards, unconfigured hostname. Will be used to clone new VMs. | ||
| + | Steps to cloning: | ||
| + | #Generate a new qcow2 file for the new VM | ||
| + | #Clone base-clone onto the new hard disk file | ||
| + | #Modify memory, start-on-boot, and network card MAC addresses to your liking | ||
| + | #Boot into new VM | ||
| + | #Log in using base-clone root password and change root password | ||
| + | #Modify hostname/domain, network scripts for statically configured IPs | ||
| + | #Have fun | ||
| + | |||
| + | ==Jalapeno== | ||
| + | *Memory: 512MB | ||
| + | *Hard Drive: 8GB | ||
| + | |||
| + | ==Roentgen== | ||
| + | *Memory: 1512MB | ||
| + | *Hard Drive: 50GB | ||
=Logs= | =Logs= | ||
| Line 8: | Line 30: | ||
It was found that Tomato's CPU did not have virtualization support. As an alternative we tried installation on one of the computer clusters but it seems the power supplies died whenever we tried to move them around. This resulted in two dead power supplies with unknown cause of death. Creating Tomato on a VM would work, but I didn't want to deal with any problems that could arise with nested virtual systems. In the end we took Tomato's hard drive and installed Gourd on that. | It was found that Tomato's CPU did not have virtualization support. As an alternative we tried installation on one of the computer clusters but it seems the power supplies died whenever we tried to move them around. This resulted in two dead power supplies with unknown cause of death. Creating Tomato on a VM would work, but I didn't want to deal with any problems that could arise with nested virtual systems. In the end we took Tomato's hard drive and installed Gourd on that. | ||
| − | Installation | + | Installation: |
*Gourd | *Gourd | ||
**Minimal server install | **Minimal server install | ||
**Installed Virtualization Group, libvirtd, dnsmasq, ebtables | **Installed Virtualization Group, libvirtd, dnsmasq, ebtables | ||
| − | |||
| − | |||
| − | |||
Revision as of 09:33, 5 March 2015
Gourd is currently running RHEL 5.11. The goal is to upgrade Gourd to CentOS 6.
The steps to take is to first install a gourd clone on Tomato. Virtualize a Roentgen clone on Tomato. Once everything is all setup we can simply swap the hard drive on Gourd with Tomato's harddrive.
VM Specs
Specs were copied from the information on wiki pages at the time.
Base-Clone
Minimal install of CentOS 7.0-1406 with two network cards, unconfigured hostname. Will be used to clone new VMs. Steps to cloning:
- Generate a new qcow2 file for the new VM
- Clone base-clone onto the new hard disk file
- Modify memory, start-on-boot, and network card MAC addresses to your liking
- Boot into new VM
- Log in using base-clone root password and change root password
- Modify hostname/domain, network scripts for statically configured IPs
- Have fun
Jalapeno
- Memory: 512MB
- Hard Drive: 8GB
Roentgen
- Memory: 1512MB
- Hard Drive: 50GB
Logs
CentOS 6.6 is installed on Tomato. It has gourd's username, no users, no internet-connection, and the expected root password. It is connected to Pumpkin's unused interface and set with a temporary address 172.16.0.3. The interface for Pumpkin is set with a temporary address of 172.16.0.2. For internet access I plugged Tomato into my personal laptop and bridged my wifi with my ethernet connection. Tomato was updated. A list of all packages on Gourd was generated and a yum install was executed for all of those packages. Unavailable packages were logged.
It was found that Tomato's CPU did not have virtualization support. As an alternative we tried installation on one of the computer clusters but it seems the power supplies died whenever we tried to move them around. This resulted in two dead power supplies with unknown cause of death. Creating Tomato on a VM would work, but I didn't want to deal with any problems that could arise with nested virtual systems. In the end we took Tomato's hard drive and installed Gourd on that.
Installation:
- Gourd
- Minimal server install
- Installed Virtualization Group, libvirtd, dnsmasq, ebtables
