The following messages during KVM image creation are...mysterious. I can't quite grasp what they mean, or what I as a user can do about them.
Checking filesystem on first disk .. .. not possible for the first disk
Mounting KVM instance filesystem .. .. failed : None of the partions in the disk image /kvm/ns.cloud.virtualmin.com.img could be mounted and contained the /etc directory
I assume the first is advisory, though it's not clear to me what it means. The second is more confusing. I'm guessing it means something is going to be wrong with the resulting image, but I don't know what, and I'm not sure what I should do about it, based on the message. The creation process continues, and completes without further error.
Maybe that could be more more information? Also, is it a bug that it's failing? The VM we're imaging was created within Cloudmin. It seems like it ought to know how to deal with it's own images.
Comments
Submitted by JamieCameron on Tue, 06/21/2011 - 23:00 Comment #1
I can login and take a look .. which VM are you trying to image?
Also, was it originally created from an image, or by doing an install from a CD into an "empty" VM? In the latter case if the VM is using LVM internally or some partition table format that Cloudmin cannot access externally, then you may get errors like this.
Submitted by JamieCameron on Tue, 06/21/2011 - 23:20 Comment #2
I took a look at the VM, and noticed that it uses LVM internally - this isn't recommended for management by Cloudmin, as there is no way to access the contents of the VM's filesystem externally when it is shut down. If a VM's disks just contain regular partitions, it is possible to mount them on the host and manipulate files. This is needed during the imaging process, and at other times.
OK, cool. I'll make new images without LVM.
It looks like it is possible to mount LVM via loopback: http://www.thegibson.org/blog/archives/467
But, it does sound more complicated than regular filesystems on regular partitions.
Anyway, that error probably ought to be more clear...maybe just mention that it could be caused by LVM on the guest partitions.
Submitted by JamieCameron on Wed, 06/22/2011 - 19:06 Comment #4
Thanks for the link .. that solution looks workable, but may cause problems if the VG on the disk image has the same name as the VG on the host. I think it would be safer to avoid this completely.
I will update the error message to indicate that LVM or RAID on the VM can be the cause.
Submitted by Issues on Wed, 07/06/2011 - 20:21 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.