Submitted by Hal9000 on Fri, 05/18/2012 - 01:17
Hi there! I am running Cloudmin Pro on a server which is going to be replaced soon by another one. So I installed Cloudmin Pro on the new server and added the soon-to-die master as KVM host to it. So far so good, however it fails to find any existing KVM instance on that host. Here is the error message:
Processing KVM command /usr/bin/kvm -name mercury -m 1024 -drive file=/dev/raid/mercury_img,media=disk,index=0,if=virtio,boot=on -drive index=1,media=disk,file=/dev/ssd/mercury_ssd,if=virtio -boot c -net tap,vlan=0,script=/kvm/mercury-eth0.sh -net nic,vlan=0,macaddr=02:54:00:33:05:90,model=virtio -vnc :3,password -usbdevice tablet -monitor tcp:127.0.0.1:40000,server -smp 2 ..
.. primary disk image /dev/raid/mercury_img is not in the raw format
So it complains the disk image is not in the raw format, whatever that means. The image is an LVM volume and I created the KVM instance with Cloudmin. By the way, I also have another host which I added to the new master, and I have the same problem trying to find the instance. What can I do now?
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 05/18/2012 - 16:44 Comment #1
What output do you get if you run :
fdisk -l /dev/raid/mercury_img
and
parted /dev/raid/mercury_img print
on the host system?
Submitted by Hal9000 on Fri, 05/18/2012 - 18:31 Comment #2
Disk /dev/raid/mercury_img: 17.2 GB, 17179869184 bytes
255 heads, 63 sectors/track, 2088 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00053cec
Device Boot Start End Blocks Id System
/dev/raid/mercury_img1 * 1 13 96256 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/raid/mercury_img2 13 2089 16678912 83 Linux
and
Model: Linux device-mapper (linear) (dm)
Disk /dev/dm-1: 17.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 99.6MB 98.6MB primary ext2 boot
2 99.6MB 17.2GB 17.1GB primary ext4
Submitted by JamieCameron on Fri, 05/18/2012 - 23:57 Comment #3
Ok, I see the cause of this now - it will be fixed in the next Cloudmin release.
The work-around till then is to add the VMs one by one, instead of doing a mass import.
Submitted by Issues on Sat, 06/02/2012 - 00:45 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.