This page will document my expirience with Proxmox which you might think as web-based version of vz-tools.

This is somewhat interesting story, because I ended up migrating PVE installation on internal laptop disk to enable dual boot. First, I installed PVE on external USB drive (which wiped out mbr on internal disk, sic!) and than archived all files from it to move it to internal disk.

Installed system had following partitions:

/dev/mapper/pve-root on /mnt/pve type ext3 (rw)
/dev/sdb1 on /mnt/pve/boot type ext3 (rw)
/dev/mapper/pve-data on /mnt/pve/var/lib/vz type ext3 (rw)

So I re-created volume grup pve and logical volumes.

I have following partitions on my laptop:

root@tab:~# fdisk -l /dev/hda

Disk /dev/hda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3b7f0ef5

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        1305    10482381   83  Linux
/dev/hda2            1306        1436     1052257+  83  Linux
/dev/hda3            1437        1567     1052257+  82  Linux swap / Solaris
/dev/hda4            1568       12161    85096305    5  Extended
/dev/hda5            1568        4178    20972826   8e  Linux LVM
/dev/hda6            4179        6789    20972826   83  Linux
/dev/hda7            6790        9400    20972826   83  Linux
/dev/hda8            9401       12161    22177701   83  Linux

create pv

root@tab:~# pvcreate /dev/hda5
  Physical volume "/dev/hda5" successfully created

final df

proxmox:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/pve/root          2064208    556244   1507964  27% /
/dev/sda2              2063536     52640   1906072   3% /boot
/dev/mapper/pve-data  20642428    407420  20235008   2% /var/lib/vz