Meat VM bootable in KVM?

Hi there!

Did anyone manage to boot the Meat! VM with KVM?
We’re getting “No bootable devices found” here.

Any help will be appreciated!

—Chris

Hi @chrimm

If you’re using virt-manager, go to Details -> expand Advanced options and set Storage format to qcow2 (see below).

OK, @Kivlov, thank you! But sadly, we still don’t get it running. As I cannot post a screenshot of the error message (due to new user restriction) I’ll copy the message by hand:

Error starting domain: internal error process exited while
connecting to monitor: char device redirected to /dev/pts/5
kvm: -drive file=/var/lib/libvirt/images/
meat.img,if=none,id=drive-ide0-0-0,format=qcow2: could
not open disk image /var/lib/libvirt/images/meat.img: Invalid
argument

The virtual disk is set up according to your screenshot.

Any further ideas?

@chrimm, do as follows:

  1. Unpack the ova:
    tar -xvf Meat 1.0.16.ova

  2. Run:
    qemu-img convert -O qcow2 1.0.16-disk1.vmdk meat.qcow2

  3. Attach meat.qcow2 as disk

  4. Set the storage format to qcow2

Let me know if it worked.

I was able to do this on a CentOS 7 kvm instance, but now I’m stuck looking for the second disk. I’ve added another disk to the VM, but Meat! isn’t detecting it. Is there some special property that the system is looking for to find it?

Hi, I had the exact same problem. I stopped the VM and disconnected both drives. Then I added them both back as ‘virtio scsi’. After rebooting the VM I get past the detecting disk stage. Hope that helps.