Hello, this is a repost from forum:
I've been evaluating cloudmin as a new platform for our VPS business and in requirements for that we are looking for easy way to migrate existing customer (server panel) to cloudmin via "add instance".
Our setup is using Debian Linux with libvirt (which should not be a problem) and LVM based images, presetned to guests as "xvda". Inside the guest servers customers are doing custom partitions and custom filesystems (yes we have jfs/drbd/ocfs users).
What is a stopping us is cloudmin disk naming: all newly created servers are utilizing pygrub/pvgrub (which is just fine), but disk is presented to guest as "sda1" which is the huge stopper for us, because we have already uniform LVM setup with single "xvda" drive and custom partition inside (none of our business as provider). As far as we could see from evaluation of cloudmin everything is a very big go, but that disk naming is preventing us from going further into actual deployment.
Is there any way to point cloudmin to provide xen guests with single "xvda" at creation time thru template without any manual intervention? We could not find a switch for that. Seems like "sda1" is hardcoded somewhere in "xen-type-lib.pl".
And yes, I am aware that this could disable features like automatic backups and disk resize.