what is best options proxmox

[sicute]

hi ..

i try using kvm in proxmox i need advice about :
1. image format ( what should i choice ? )
- QCOW2
- RAW
- VMDK
2.disk type ?
- IDE
- SCSI
- virtio

my concern is :
- easy to migrate to another cluster best option online
- perfomance fro write and read real production server (web server , mail server , proxy etc )
- easy to backup and compatibe move to another virtual such as vmware, virtualbox etc
- some compare report

ok that is before and after many thanks

 

[tom]

hi ..

i try using kvm in proxmox i need advice about :
1. image format ( what should i choice ? )
- QCOW2
- RAW
- VMDK

raw, and consider using block devices directly (with LVM).

2.disk type ?
- IDE
- SCSI
- virtio

virtio or IDE, for Linux virtio.

my concern is :
- easy to migrate to another cluster best option online

online migration is only possible inside the same cluster - means from node to node. you need shared storage or DRBD for this.

- perfomance fro write and read real production server (web server , mail server , proxy etc )
- easy to backup and compatibe move to another virtual such as vmware, virtualbox etc
- some compare report

ok that is before and after many thanks

these questions are far to general - read the forum and wiki about recommendations.

 

[oeginc]

hi ..

i try using kvm in proxmox i need advice about :
1. image format ( what should i choice ? )
- QCOW2
- RAW
- VMDK
2.disk type ?
- IDE
- SCSI
- virtio

my concern is :
- easy to migrate to another cluster best option online
- perfomance fro write and read real production server (web server , mail server , proxy etc )
- easy to backup and compatibe move to another virtual such as vmware, virtualbox etc
- some compare report

ok that is before and after many thanks

I just asked (almost) this same question about 10 days ago (CLICK HERE).

The general consensus was:

1. KVM (instead of OpenVZ)
2. RAW (instead of QCOW2, or VMDK)
3. Virtio (instead of IDE, or SCSI)
4. LVM (instead of no LVM)

I started making a spreadsheet of testing under the various configurations and got frustrated 1/2 way thru. and I deferred to the expert knowledge of others. The above assumes a large enough budget to purchase machines capable of handling the task at hand. You will chew up more memory and disk space with KVM vs. OpenVZ...