New Project – Proxmox

After my VPS fiasco last week, a new interest has been sparked in VPS hosting. I started installing Proxmox on an old desktop – E6700/6GB/750GB – and will play around with it tomorrow. If it shows promise I will re-install on something more robust.

Update – Tuesday, September 26, 2012:

Setting up a KVM VPS is as simple as uploading an ISO to the library and clicking Create VM. You can assign all the parameters in about 6 steps. Creating a OpenVZ from a template is actually even easier, albeit more convuluted. You actually can download templates from the GUI in version 2.1 but they are limited. For a list of templates you can go here. I set up Ubuntu from a template as follows:

  • download template file using wget to corresponding location in your specified store (cache directory /var/lib/vz/template/cache) NOTE: You could probably use the GUI to upload the template as well but I have not tested this
  • Create CT
  • Follow on-screen instructions

This process took less than 3 minutes after the download was complete with network configured during the creation of the VPS. The next step would be to figure out how to enable kernel support for specific functionality.

Update – Thursday, September 27, 2012:

Since Proxmox looks promising, I started installing it on better hardware (i7 2600/32GB RAM/2TB RAID10). Migration however is a serious pain. There is currently no implementation for migrating between disparate servers in the GUI – at least not when uploading the RAW disk image to the corresponding folders. I did however find a workaround.

First, create a new VM with an empty disk. You can remove this disk image later. Note the ID you specify here (i.e 101).

SSH to your Proxmox server as root and locate the configuration file for your VM id under /etc/pve/nodes/proxmox/qemu-server:

[email protected]:/etc/pve/nodes/proxmox/qemu-server# ls

101.conf 200.conf

For me this is 101.conf as 101 was the ID specified in the new VM creation process.

vi 101.conf

boot: c
bootdisk: ide0
cores: 1
ide0: local:101/test.raw
ide2: none,media=cdrom
memory: 256
name: Natux
net0: rtl8139=56:20:38:EB:64:9C,bridge=vmbr0
ostype: l26
sockets: 1
unused0: local:101/vm-101-disk-1.raw

This is what you will eventually see in the configuration file, however, I specified test.raw as unused0 so it would be visible in the GUI and changed it to ide0 there. Test by loading up the console after starting the VM. For whatever reason, you can’t simply use mv to rename the migrated disk image as it won’t detect a boot device.

If you'd like to share this, click below:

Leave a Reply