# Generic cloud or qcow

**URL:** <https://forums.rockylinux.org/t/generic-cloud-or-qcow/2446>\
**Category:** Rocky Linux Help & Support\
**Created:** [May 2, 2021, 11:35am UTC](https://forums.rockylinux.org/t/generic-cloud-or-qcow/2446 "2021-05-02T11:35:00Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [January 25, 2022, 7:08pm UTC](https://forums.rockylinux.org/t/generic-cloud-or-qcow/2446/18 "2022-01-25T19:08:57Z")

</div>

As you’ve posted a duplicate question, I will answer it in your other post. It’s best not to double-post to save people confusion.

> [@Installing a Rocky 8.4 Virtual Box VM as a qcow2 Openstack Image](https://forums.rockylinux.org/t/installing-a-rocky-8-4-virtual-box-vm-as-a-qcow2-openstack-image/5196):
>
> I built a Rocky 8.4 VM on virtualbox (vmdk format) and hardened it using Red Hat Standard Linux profile - this requires a specific disk partitioning to be implemented. I converted the vmdk format to qcow2 using qemu-img tools for Windows successfully. When I install on the Openstack platform, the qcow2 image instead boots into initramfs system and dracut-initqueue timeout is experienced. The timeout throws an error that the root disk cannot be found. When I check for the devices with the blkid …

---

_[View the full topic](https://forums.rockylinux.org/t/generic-cloud-or-qcow/2446)._
