# "missing DISK mandatory attributes" when VM starting

**URL:** <https://forum.opennebula.io/t/missing-disk-mandatory-attributes-when-vm-starting/889>\
**Category:** Product Support\
**Created:** [June 19, 2015, 5:27am UTC](https://forum.opennebula.io/t/missing-disk-mandatory-attributes-when-vm-starting/889 "2015-06-19T05:27:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![VURoland](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/vuroland/32/7682_2.png) [@VURoland](https://forum.opennebula.io/u/VURoland)\
**Post date:** [June 19, 2015, 10:33am UTC](https://forum.opennebula.io/t/missing-disk-mandatory-attributes-when-vm-starting/889/2 "2015-06-19T10:33:00Z")

</div>

hi,

when creating a datablock, you end up with a raw image. If you want to use it as a startup disk, you should change the type from “datablock” to “OS”. Under FSTYPE you mention qcow2, but that should be something else, like ext4 or ntfs.

If you want to use qcow2 images, don’t create datablocks, but use qemi-img to create qcow2 images and then import them to the datastore. (and make sure to use the prefix “vd” instead of “sd”, so it uses virtio).

This thread: [RAW vs QCOW2 images; VMs fail](https://forum.opennebula.io/t/raw-vs-qcow2-images-vms-fail/607/6)  
contains ways to create qcow2 images, or convert your existing raw images to qcow2.

hope this helps !

---

_[View the full topic](https://forum.opennebula.io/t/missing-disk-mandatory-attributes-when-vm-starting/889)._