<li>

Choose the node, VM number (defaults to the next available), name (anything you like such as &#39;HDA&#39;, or &#39;Amahi&#39;), and the resource pool to fall under (will need to be defined beforehand) (resource pool is just a pseudo-logical way of looking at stats for several VMs) .. then click &quot;Next&quot;<br />

<li>

Choose the Linux 2.6/3.x kernel type .. then click &quot;Next&quot;</li>

<li>

Choose the &quot;Use CD/DVD disc image file (iso)&quot; option. Then find the storage area (usually &#39;local&#39;) where your Fedora or Ubuntu ISO resides .. then click &quot;Next&quot;<br />

<li>

In the Hard disk tab, you have several options.<br />

- Start with VIRTIO. This is a abstracted, optimized interface for drive images. As this is the first disk, it will be device &#39;0&#39;.<br />

- Choose the storage volume that will contain this image; typically the &quot;local&quot; unless you have setup something else.<br />

<li>

The following tab is for CPU options<br />

This tab decides how much CPU to give to your Amahi VM. Choose options that meet or exceed the minimum system requirements for your chosen OS (Fedora/ Ubuntu).<br />

- start with 2 core and 1 socket and a &#39;qemu64&#39; CPU type. You can always go back and change it.<br />

<li>

This next network tab decides what kind of networking to give the VM.<br />

- go for &quot;bridged mode&quot; as we want the VM to look like a real device on the LAN<br />

- the default bridge is always vmbr0 and it also shares traffic with the web GUI console. If you have no additional NICs in the physical machine, this will be the only bridge to use.<br />

<li>

After OS installation is complete. You may turn on the auto-boot and even select the order in which this VM boots around other VMs in Proxmox.<br />

*It is suggested that if you HDA is definitely going to be your DNS and DHCP server, that it boots as &#39;0&#39; (first).<br />

&nbsp;</li>