I have been running proxmox systems for a while now, and a few features i can think of which would be useful but which don't seem to appear in the roadmap:
Serial console support:
currently i manually configure a serial console on each image, for instance:
args: -serial unix:/var/run/qemu-server/121.serial,server,nowait
and then created minirc.121 in /etc/minicom, so that i can just do:
minicom 121
to connect to the image...
however, it would be useful to have this automatically created (or an option to do so) when adding an image from the gui... i prefer to admin my unix based images this way, as it is more friendly to slow/latent connections than vnc.
Default to KVM in the gui and set other defaults:
currently the gui defaults to openvz containers, even tho i am running the 2.6.32 kernel without openvz support and therefore cannot use containers... An option should be present to turn off openvz support (or do so automatically on a non openvz kernel) or set kvm to be the default...
it would also be useful to be able to set other defaults in the gui, eg default to virtio when creating a new image, or default to 2 cores and 512mb ram etc...
Support for floppy images:
there should to be a facility to attach floppy images, either for installing systems which install from floppy, or for installing virtio disk drivers into windows xp/2003 machines... currently i have to do this manually by editing the config file
Option to change the default cpu type:
again i have to set the default cpu type by manually editing the configs, since i run a cluster of identical machines i would like to use -cpu host.. this may also be beneficial on non clustered systems too.
Shutdown scripts:
when shutting down or rebooting a cluster node or individual system, there should be options regarding how to handle running images... currently they are just killed, it would be beneficial to have the option of suspending them to disk or migrating them to another cluster node (which could be done automatically based on available resources in other cluster nodes if theres 3 or more nodes)
Suspend of images:
an option to suspend to disk running machines would be useful
Serial console support:
currently i manually configure a serial console on each image, for instance:
args: -serial unix:/var/run/qemu-server/121.serial,server,nowait
and then created minirc.121 in /etc/minicom, so that i can just do:
minicom 121
to connect to the image...
however, it would be useful to have this automatically created (or an option to do so) when adding an image from the gui... i prefer to admin my unix based images this way, as it is more friendly to slow/latent connections than vnc.
Default to KVM in the gui and set other defaults:
currently the gui defaults to openvz containers, even tho i am running the 2.6.32 kernel without openvz support and therefore cannot use containers... An option should be present to turn off openvz support (or do so automatically on a non openvz kernel) or set kvm to be the default...
it would also be useful to be able to set other defaults in the gui, eg default to virtio when creating a new image, or default to 2 cores and 512mb ram etc...
Support for floppy images:
there should to be a facility to attach floppy images, either for installing systems which install from floppy, or for installing virtio disk drivers into windows xp/2003 machines... currently i have to do this manually by editing the config file
Option to change the default cpu type:
again i have to set the default cpu type by manually editing the configs, since i run a cluster of identical machines i would like to use -cpu host.. this may also be beneficial on non clustered systems too.
Shutdown scripts:
when shutting down or rebooting a cluster node or individual system, there should be options regarding how to handle running images... currently they are just killed, it would be beneficial to have the option of suspending them to disk or migrating them to another cluster node (which could be done automatically based on available resources in other cluster nodes if theres 3 or more nodes)
Suspend of images:
an option to suspend to disk running machines would be useful
