Appliance Resources are not sufficient to install or continue to run plugins

The issue you are facing is that the Dell OpenManage Enterprise (OME) virtual appliance requires at least 400GB of disk space to support the appliance and all installed plugins, but your current VM only has 0GB allocated.Based on the information provided in the search results, here is how you can resolve this problem:

1. Increase the disk size of the OME virtual appliance:
   • You mentioned trying to increase the disk size using KVM Qemu Image Conversion and adding a secondary disk, but those methods did not work.
   • The recommended approach is to directly increase the disk size of the OME virtual appliance. This can be done through the hypervisor management interface (e.g., VMware vSphere, Hyper-V, or KVM) by expanding the virtual disk allocated to the OME VM.
   • Ensure that you allocate at least 400GB of disk space to the OME VM to support the appliance and all plugins.34
2. Scan for disk changes and expand the file system:
   • After increasing the disk size, you need to scan for the disk changes and expand the file system within the OME virtual appliance.
   • The search results mention that there is an option within the OME appliance to "scan for disk changes and increase the disk", but this did not work for you.
   • If the automatic disk expansion does not work, you may need to manually expand the file system within the OME virtual appliance using Linux commands, such as resize2fs or lvextend.34
3. Ensure the OME virtual appliance has sufficient resources:
   • In addition to disk space, the OME virtual appliance also requires sufficient CPU and memory resources to run the appliance and all plugins.
   • Verify that the OME VM is configured with adequate CPU and memory resources, as recommended by Dell for your environment.34

By following these steps, you should be able to resolve the "Appliance resources are not sufficient" error and successfully install the required plugins in your Dell OpenManage Enterprise 4.x.x deployment on your KVM server.

1. https://dell.to/3Ub9HOj

2.https://dell.to/4d52cQL

3.https://dell.to/3QkllEz

4. https://dell.to/4d52bMH

5.https://dell.to/3JeXYYO

@Dell-Martin S​ It seems that even after expanding the disk with Qemu-Img to 900GB and running the appliance expansion option, it doesn't see the drive space.  How do I enable SSH access to the appliance to that I can manually run resize2fs or lvextend at you mentioned in bullet 2?

Hello,

You can add storage to it and use the TUI to detect that expanded storage for use.

@DELL-Charles R​ Tried that and unfortunately it doesn't detect the increased storage.  In my case I went from the 400gb appliance size to 900GB and it doesn't detect it at all.

Hello the advice given is correct. So we need to look into if you're not doing this right or the appliance is broken. In this case you'll need a remote session with the team. SSH is not possible. It is not enabled by design. An scalation is needed to have it enabled. Base on the image, it is saying need 400GB, but you claim you already have 400GB so we definitely need to raise a proper case for a remote seesion. Pleae visit https://dell.to/43S3L09
Respectfully,

@DELL-Young E​ Got it figured out.  The virtual machine must use a SATA or IDE interface controller - not a VIRTIO controller.  Then it repeating the process to find the disk and expand the volume worked after converting the controller to the right type.