Changes

From Amahi Wiki
Jump to: navigation, search
no edit summary
[https://wiki.amahi.org/index.php/Amahi_Virtualized Back to 'Amahi Virtualized']
<h2>Amahi in Proxmox with Greyhole</h2>
<strong>(work in progress)</strong>
<p>
This tutorial will skip installation of Proxmox, as that is covered by Proxmox documentation.</p>
<ul>
<li>It is not advisable to use Greyhole pooling with drive images (instead of physical drives) due to the added overhead and I/O delay that can be introduced. It will slow down your Proxmox machine and your Amahi file server</li>
<li>This process does work with any Amahi version and installation method, however if Greyhole isn't fully functional with a release of Amahi, it's not advisable to use Greyhole in this case.</li>
<li>The essential concept when using physical drives through the Proxmox machine is that the drive will NOT be mounted on the Proxmox machine, but routed through QEMU/KVM commands to the VM that will use it, much like a hardware pass-thru.</li>
<li>When the physical drive is added to the VM, it will show up in the Proxmox web GUI, but should <strong>NOT</strong> be tampered with from there.</li>
<li>
In its current state, your new VM is off, and also NOT set to start automatically when the Proxmox node boots up. This setting can be changed later, as you see fit.<br />
Congrats! you&#39;ve created the virtual machine that your HDA will use.</li><br /> <li><br /> To accommodate <strong>the Greyhole Landing Zone volume</strong> on this VM, you can add a single drive image to the VM to act as the LZ storage mount, typically known to Amahi users as &#39;/var/hda/files&#39;.<br />
- Under the &#39;hardware&#39; tab, click &quot;add&quot; &gt; &quot;hard disk&quot; &gt; &#39;VIRTIO&#39; &gt; device &#39;1&#39; &gt; storage &#39;local&#39;<br />
- Decide how big this drive is to be. It is limited only by how much &#39;local&#39; storage is available in that Proxmox partition. A good suggestion is 500MB to 1TB because the LZ needs to be big enough to handle your data moving into the storage pool. Once again the remaining options are up to you, but leave cache at &#39;default&#39;. I would suggest to NOT include this LZ drive image in backups and snapshots (There's no need to back this up unless you will have shares NOT marked for pooling. ) Finally, click &quot;Add&quot; and this drive is added to the VM</li><br />
<li>
At this point, with the HDA VM highlighted, click the &quot;Start&quot; button at the top right of the window and it will boot up. Right away, click the &quot;console&quot; button just to the right of the migrate button.&nbsp;<br />
This will launch a window which will be the display for the VM. You will see a normal boot that will boot from the ISO you selected earlier.</li>
<li>
During installation, you can setup the second drive you added to mount &#39;/var/hda/files&#39;, thus creating your shares Landing Zone partition right away at install of Fedora/Ubuntu.</li>
<li>
Installation at this time is just the same as documented by the OS and in the Amahi installation procedures. Please refer to those until your next boot.<br />
*It is suggested that if your HDA is definitely going to be your DNS and DHCP server, that it boots as &#39;0&#39; (first).<br />
&nbsp;</li>
<li>Now that your Amahi VM is installed and created, please check that its main functionality is good. Your OS drive and the second drive acting as LZ, mounted to '/var/hda/files' should be accessible. If all is well, shut down the VM.<br />At this point in time, your physical drives that you wish to use with Greyhole should be inside the Proxmox node and connected. If they are not, please shut down the system, connect the drives, boot it up and then ensure your Amahi VM is shutdown once more. <br />Now use any method you wish to get terminal access to your Proxmox node: either with the 'Console' button in the web GUI, or your favourite SSH client to SSH the Proxmox node.</li><li>This step is where you finally point the physical drive to the VM, through the Proxmox console.<br />This command will add a IDE "abstracted" device to VM101:<pre>qm set vm101 -ide0 /dev/sdb</pre><ul><li>vm101 is the ID of the virtual machine to which you want to point the drive.</li><li>ide0 identifies the drive once mounted, as ide0 and the protocol for it</li><li>/dev/sdb is the installed <strong>but not mounted in Proxmox</strong> drive in the hardware system.</li></ul>Once booting this KVM, now add this drive by manually, permanently mounting it to the VM. This could be via editing the /etc/fstab within the VM or using any other drive mounting tool/method you wish. You should reference the Amahi drive-adding wiki article at this point to ensure the drive is added appropriately: <br />[https://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA Adding a Second Drive to your HDA] <br />For each physical drive you add, you can decide to pool it to Greyhole or not. It helps to understand some commands for managing drives and volumes and partitions in Linux before doing too much moving around.</li></ol><h4>NOTE: Greyhole drives or drive images with data on them can be added to a newly installed Amahi VM and if mapped identically as before, they should function fine once the <pre>greyhole -f</pre> command has run through a couple times. <br />Do reference [https://wiki.amahi.org/index.php/Post-Install_Hardware_Changes Post Install Hardware Changes] for swapping hardware, which is similar to changing from a physical to virtual setup.</h4>
<br />
 
* [http://forum.proxmox.com/threads/2537-quot-qcow2-quot-vs-quot-raw-quot-KVM-Disk-Format forum reading for qcow2 vs raw]
* [http://www.linux-kvm.org/page/Qcow2 KVM reference from Red Hat]
[[Category:Virtualization]]
12,424

edits