Disk image directory option not in Create KVM Instance, create empty system


I’ve succesfuly installed and created a running cloudmin server on a 16 gig usb stick running centos. Of course this does not have space for the VMs so I added in two new drives.

I’ve created two disk image directories for the two drives in “New System > Disk Image Directories”.
However, when i go to “New System > Create KVM Instance”, i can use those in the first tab “Create working system” listed under “Disk image directory” but they are not listed in “Create empty system”.

I’m confused as to why I can’t use them in the empty system, i see some info online about creating the hosts in cli, but then whats the point of the web based create if I have to go and do it in the cli.

Is it a setting or something i’m missing.

Any thoughts or suggestions?


This is a missing feature in Cloudmin - it should be possible to specify the disk images directory when creating an empty VM. I’ll fix this in the 6.5 release.

Thanks for the reply.

After spending a few hours last night back tracking the code, I found that it wasn’t programed in to support specifying the image location.

I started hoping that the code was there in the background and it just needed to be passed a path, not the case I found out. But here are the notes as to what I did and some other issues that came up. Maybe it will help you when you get to the point of working it in to the 6.5 version.

I’m in the path “/usr/libexec/webmin”.

I took the form element code from “server-manager/create.cgi” and added it to “server-manager/empty.cgi” – as far as I can tell with my limited Perl experience it appears to work.

My current problem is that I keep getting told there is not enough disk space.

I traced that error to the “host_free_disk” function in server-manager/server-manager-lib-funcs.pl
This gets the host data from “&get_server_collected($vhost)” which looks ok as far as I can tell.

My problem is that the “host_free_disk” function checks for lvm and if found uses it to determine the drive space, this fails on my current configuration.

I have a USB stick that is my base drive which was configured as an lvm during the install (defaults). I decided since I’m not using raid against expanding the lvm and just to mount my extra drives outside the lvm.

df -ah

File system Size Used Avail Use%
Mounted on
13G 1.8G 11G 15% /
proc 0 0 0 - /proc
sysfs 0 0 0 - /sys
devpts 0 0 0 - /dev/pts
tmpfs 16G 0 16G 0% /dev/shm
/dev/sdc1 485M 52M 409M 12% /boot
/dev/sdb1 2.7T 201M 2.6T 1% /storage_one
/dev/sda1 2.7T 201M 2.6T 1% /storage_two

This causes the “host_free_disk” to fail with not enough disk space.

This problem actually drifts over to the “Create working system” also as I am unable to create those because of the above function not detecting the drive space – even though I’ve specified a location using the “Disk image directory”.

Now all the above still doesn’t cover if the vm disk is created or not or the actually using the “Disk image directory” to make them.

That is as far as I got as it was getting late and I had enough fun for the night.

On side note on the “Create working system”, you might want to work in an error or warning that you need to download a system image in “Couldmin Settings > New System Images” before using the “Create working system” form.

When you don’t have an image downloaded the form does not show the “Cloudmin system image” select option, since there is no system image available. But it also doesn’t tell you until you submit the form.

Then it’s a bit confusing as it say something like no system image specified – but you go back to the form and there wasn’t any place on the form to specify one.

Anyways, hope this helps some.

I’m going to wipe and reinstall without the lvm and see if I can use the system image to create the machine then reinstall over it.

It appears that I cannot create any system images because of the volume group space check. I reinstalled and removed the volume group from the drive, but cloudmin still only reported the default usb stick size, ignoring the other drives - even though i specified a image directory in the create form.

Just thought I’d pass that note along …

That sounds like a bug - I presume your LVM volume group is really small, and that you really want to create VMs in another directory?

If that is the case, you can go to Host Systems -> KVM Host Systems -> your-host and set LVM volume group for disk images to either None, or to a volume group with plenty of space.

Yes, the base drive for the systems is a 16G usb stick running centos 6.2. Only a few small steps to get the installer to work with that version, nothing to major.

I didn’t think about created a second volume group for the secondary data drives.

I’ll give both ways a try on my next machine install, need to get this on up so just using the minimum desktop and using the virt-manager for the time being.

I’ll be rebuilding another box later this month (hopefully) and I’ll try what you’ve mentioned.

Thanks for the reply