Changes

From Amahi Wiki
Jump to: navigation, search
no edit summary
Create a New VM, then choose <b>Other install Media Template</b>. Name the machine without spaces, choose to install from DVD drive where you have the Amahi 7.1 express disk located. Place on your XenServer and choose CPU and RAM. A recommended minimum would be 1 CPU, 2048 MB RAM. Now add a virtual disk. For better performance you should have a separate drive or drive pool for each VM you create. To start, create a 500 GB or larger VDI and move on to the network setup. Again, for better performance, choose a dedicated NIC for each VM. For this tutorial, you can just choose the defaults which is a shared NIC on your XenServer.
Switch to the console tab on the newly created VM and install Amahi 7.1 as you would like.
One suggested change from the default Amahi install is to <b>make the boot partition Ext3</b>. While partitioning the hard drive, choose Ext3 rather than Ext4, because ’pygrub’, the XenServer bootloader for the PV mode, can’t read Ext4. If you wish to benefit from Ext4 advantages anyway, then you’ll have to create a /boot partition in Ext3 and the / partition in Ext4. Finish the Amahi install as per regular instructions. (ensure you have your code and that you let it reboot twice before initializing in browser).
If you are happy with a simple setup and not too concerned about performance then you could stop here and skip to the part about installing Xen-Tools below. The guest VM with Amahi installed on it is in <i>HVM mode or hardware assisted virtualization </i> (more information [http://en.wikipedia.org/wiki/Xen here]). If you would like your guest VM to run in <i>paravirtualization mode</i>, which will give better performance and access to more than three drives, you need to complete the next part.
<h3>Convert to PV or Paravitualize</h3>
Tips from: https://www.cetic.be/Paravirtualize-an-Ubuntu-VM-using
You only need to do this for slightly better resource management, like attaching more than three VDI images. This is only possible if your boot partition is EXT3.
Copy First you should copy down the defaults from grub2 on the Amahi VM. Go to /boot/grub2 and read grub.cfg. NeedWhat you are looking for is the line that specifies your default linux boot option. Both the location and all of the kernel options. It might look like this:
linux /boot/vmlinuz-3.10.5-201.fc19.x86_64 root=UUID=42e4c7e4-f260-4462-ad9c-c3f375e3a967 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet
initrd /boot/initramfs-3.10.5-201.fc19.x86_64.img
Then ssh on SSH in to the XenServer host and identify the name of the VM you wish to convert to PV mode.
{|style="width: 95%; margin-left: 10px; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"!style="color:#777; background-color:#dfd;text-align:left"|{{{lang|{{{2|bash}}}}}} code|-|{{#tag:syntaxhighlight|​{{{Code|xe vm-list}}}​|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}|}<!--{{#tag:syntaxhighlight|{{{1}}}}}-->
need the name of the VM (Amahi71, not uuid=c5ab2d09-9669-fcb5-f121-c979092dff91)
download the makepv.sh.
You will need the name of the VM not the UUID. Now download the makepv.sh script. download this [https://www.cetic.be/IMG/zip/makepv.sh.zip makepv.sh] script. {|style="width: 95%; margin-left: 10px; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"!style="color:#777; background-color:#dfd;text-align:left"|{{{lang|{{{2|bash}}}}}} code|-|{{#tag:syntaxhighlight|​{{{Code|wget https://www.cetic.be/IMG/zip/makepv.sh.zipunzip makepv.sh.zip}}}​|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}|}<!--{{#tag:syntaxhighlight|{{{1}}}}}-->
It will:
<hr>
<h2>Links or Sources that helped create this tutorial</h2>
<ul>
<li>XenServer setup:http://www.dbarticles.com/xen-server-6-2-installation-setup-and-setup-first-centos-6-x86_64-virtual-server/ </li>
<li>Paravirtualization: https://www.cetic.be/Paravirtualize-an-Ubuntu-VM-using</li>
<li>OpenXenManager: http://sourceforge.net/projects/openxenmanager/</li>
</ul>
 
 
<i>
Note: if you are having trouble reaching your apps from the dashboard, you may need to run this command on the HDA:
</i>
# yum -y update openssl