# Rocky Linux Installation Not working properly in VirtualBox

**URL:** <https://forums.rockylinux.org/t/rocky-linux-installation-not-working-properly-in-virtualbox/13347>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [March 27, 2024, 5:49am UTC](https://forums.rockylinux.org/t/rocky-linux-installation-not-working-properly-in-virtualbox/13347 "2024-03-27T05:49:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shalom](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/shalom/32/1686_2.png) [@shalom](https://forums.rockylinux.org/u/shalom)\
**Post date:** [March 27, 2024, 5:49am UTC](https://forums.rockylinux.org/t/rocky-linux-installation-not-working-properly-in-virtualbox/13347/1 "2024-03-27T05:49:55Z")

</div>

I have installed RockyLinux 9.3 on VirtualBox 7.0.14 and use it as base image, My Base OS is windows 11.

My installation worked fine, but whenever i create full clone and try to boot it, the full clone image gave error screen but when i build linked clone and try to boot it , the linked clone image worked fine and booted successfully.

I tried with different Linux distro iso (Fedora and ubuntu ) but all worked as expected with both option (viz full clone and linked clone ) .  
I’m getting same error with VMware workstation , so i think Rocky Linux 9 image behave differently but i am unable to understand why and how to revert its behaviour like fedora and ubuntu ISO.

Error for your Reference:  
Booting ‘Rocky Linux (5.14.0-362.24.1.e19\_3.x86\_64) 9.3 (Blue Onyx)’  
[9.054307] systemdLll: Invalid DMI field header.  
12.983222] Warning: Unmaintained hardware is detected: el000:100E:8086 @ 00 00:00:03.0 14.803051] vmwgfx 0000:00:02.0: Idrmi _ERROR_ vmwgfx seems to be running on n unsupported hypervisor.  
14.803053] vmwgfx 0000:00:02.0: Idrmi _ERROR_ This configuration is likely b oken  
[14.803055] umwgfx 0000:00:02.0: [drm] _ERROR_ Please switch to a supported g laphics device to avoid problems. You are in emergency mode. After logging in, type “journalctl -xb” to view .ystem logs, “systemctl reboot” to reboot, “systemctl default” or “exit” o boot into default mode. live root password for maintenance (or press Control-D to continue):  
 ![Screenshot 2024-03-27 111748](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/0/06395554102957352030f52bf74b050376a757c6.png)

---

<div class="post-metadata">

**Author:** ![guyr](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@guyr](https://forums.rockylinux.org/u/guyr)\
**Post date:** [April 29, 2024, 5:15am UTC](https://forums.rockylinux.org/t/rocky-linux-installation-not-working-properly-in-virtualbox/13347/2 "2024-04-29T05:15:32Z")

</div>

You may have moved on from this issue. I just found it via search. See my report of the same issue and a workaround I found for it:

> [@9.2 system update corrupts running Rocky LInux under VirtualBox 7.0.6](https://forums.rockylinux.org/t/9-2-system-update-corrupts-running-rocky-linux-under-virtualbox-7-0-6/11269):
>
> I installed a prebuilt VM for Rocky Linux I obtained from [Linux VM Images](https://www.linuxvmimages.com/) on VirtualBox 7.0.6 running under Windows 7 64-bit. I’ve had Ubuntu running on this setup for a decade without issue, currently 23.04… The RL VM starts up fine and seems fully functional. I can shut it down and restart it without error. However, if the system detects updates are available, and I allow it to install them, then upon reboot the system appears to be corrupted. Fortunately, I had taken a backup before I up…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [June 28, 2024, 5:16am UTC](https://forums.rockylinux.org/t/rocky-linux-installation-not-working-properly-in-virtualbox/13347/3 "2024-06-28T05:16:02Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
