Wrong amount of RAM detected when deployed on ProxmoxVE

Getting Started
1

I’ve deployed the latest OVA (Greenbone-Enterprise-TRIAL-24.10.1-VMware-Workstation.ova) appliance on ProxmoxVE 6.4.1 with 8G RAM allocated to the VM, and vCPU type “host”. Machine type is q35. Host CPU is i7-9700.

After logging in, I am shown a warning that only 3G of RAM has been allocated to the VM:

image
image532×322 18.9 KB

Does anyone know of a solution/workaround for this? I’ve done a cursory search on Google and some older posts suggest a mix of “not supported” and “it worked for me”, and nothing too helpful for my specific situation here.

I am hoping to get it to work on Proxmox as I have moved my environment away from VMWare and I don’t particularly want to run Greenbone on Virtualbox either.

2

Check your virtual machine, this is a typical VM hardware setup issue, PCI Window, etc … At the moment Proxmox is NOT supported at the moment by the VMWare Image.

You can try to run the Image inside QEMU that is the same virtualization technology.

1 Like
3

Thanks for the reply. I’m not sure what you mean by PCI Window. Could you elaborate?

Are you able to definitely confirm that the appliance won’t run (properly) on Proxmox?

I can deploy it on my ESXi instance, but I would prefer to run it on Proxmox if I can. I’m trying to remove ESXi from my environment.

4

The “PCI hole” is a memory gap that prevents access to 512 MB to 1.5 GB of RAM around the 3 GB mark. This is because the memory addresses are required for devices.

If you can run with with QEMU locally you can deploy it with proxmox. Did you choose 64BIT OS with EFI BIOS ? The 3 GB only ram are a typical BIOS, OS configuration issue.

1 Like
5

My VM is configured like this:

image
image510×260 6.11 KB

6

Try to use a different just a simple VGA framebuffer and not QXL as well try Virt-Block and not Virt-SCSI.

7

I’ve tried the default graphics controller instead of SPICE, but no dice.
As for the storage controllers, this is the list of available ones, and I’m not sure which one you’re referring to:

image
image329×259 8.42 KB

EDIT: Moved it onto the Block VirtIO device. This did not help.

8

As i said, try it on QEMU and open a ticket if this is NOT working on Proxmox.
I would suggest to use VirtBlock. I just check it with QEMU and it´s running fine :wink:

9

I got it working in Proxmox.

For anyone else running into the same issue:

The solution was to switch from the q35 machine type to i440fx. This appears to be the only setting that makes a difference.

2 Likes