After playing for ~2 weeks with Proxmox VE, I must say - I'm impressed. It's probably the best virtualization solution available for Linux.
Of course, improvements are always good - here is my wishlist for future releases.
Points 1 and 2 can be theoretically made by everybody even now, given a bit (point 1) or a lot (point 2) of manual work.
Point 3 is a small web interface change which gives a lot of improvement from my point of view (I always have to go to SSH to do these changes after creating a guest).
1.
Allow to "pause" emulation of a guest, save its state to the disk, reboot the host (i.e. kernel or hardware upgrade), resume the guest from where it last was - probably network connections will reset, but guest will not have to boot again; will have it's programs, calculations/computations still running; guest's uptime will not be lost too
http://article.gmane.org/gmane.comp.emulators.kvm.devel/28758
To stop the guest and save its state, in Qemu monitor, do:
qm> stop
qm> migrate "exec:dd of=/path/to/<VMID>state.img"
To resume:
kvm -all -parameters -incoming "exec:dd if=/path/to/<VMID>state.img"
Also, upon server restart or shutdown it should be configurable per guest if you want to shutdown the guest via ACPI, or pause it and save its state (Xen does pause and save state by default).
2.
Guest accounting
- bytes sent/received
- CPU time used
- days/hours/minutes enabled
- such statistics should be available for guest's lifetime (stats for a given month, week etc.)
3.
Web management:
- web interface only allows adding/removing devices and interfaces ("Hardware" tab); it would be great if it was possible to edit them as well (i.e. change MAC, bustype, hard disk path)
- when creating guests, allow to point the disk to an existing block device or file
Of course, improvements are always good - here is my wishlist for future releases.
Points 1 and 2 can be theoretically made by everybody even now, given a bit (point 1) or a lot (point 2) of manual work.
Point 3 is a small web interface change which gives a lot of improvement from my point of view (I always have to go to SSH to do these changes after creating a guest).
1.
Allow to "pause" emulation of a guest, save its state to the disk, reboot the host (i.e. kernel or hardware upgrade), resume the guest from where it last was - probably network connections will reset, but guest will not have to boot again; will have it's programs, calculations/computations still running; guest's uptime will not be lost too
http://article.gmane.org/gmane.comp.emulators.kvm.devel/28758
To stop the guest and save its state, in Qemu monitor, do:
qm> stop
qm> migrate "exec:dd of=/path/to/<VMID>state.img"
To resume:
kvm -all -parameters -incoming "exec:dd if=/path/to/<VMID>state.img"
Also, upon server restart or shutdown it should be configurable per guest if you want to shutdown the guest via ACPI, or pause it and save its state (Xen does pause and save state by default).
2.
Guest accounting
- bytes sent/received
- CPU time used
- days/hours/minutes enabled
- such statistics should be available for guest's lifetime (stats for a given month, week etc.)
3.
Web management:
- web interface only allows adding/removing devices and interfaces ("Hardware" tab); it would be great if it was possible to edit them as well (i.e. change MAC, bustype, hard disk path)
- when creating guests, allow to point the disk to an existing block device or file