Hello,
So I have several proxmox nodes working fine, hosting several virtual machines. We had to spin up another instance of Server 2022 so I did just that, it's working fine as well. I installed Hyper-V on the virtual machine, as the application may run a nested virtual machine (though I needed to make some tweaks, listed below).
One of the requirements for an application on the server ran the equivalent of the powershell command Get-WmiObject Win32_PhysicalMemory. When it ran, it returned nothing.
I disabled KVM on the node, disabled ballooning, passed the host cpu info to the VM, installed / enabled the QEMU agent on the host/guest vm, still no go. I wonder if the OS doesn't see the RAM (though it appears in system properties)? VirtualBox has a command, vboxmanage, that can expose additional information to the OS. is there a similar command that we can run in proxmox to do the same thing?
TIA
So I have several proxmox nodes working fine, hosting several virtual machines. We had to spin up another instance of Server 2022 so I did just that, it's working fine as well. I installed Hyper-V on the virtual machine, as the application may run a nested virtual machine (though I needed to make some tweaks, listed below).
One of the requirements for an application on the server ran the equivalent of the powershell command Get-WmiObject Win32_PhysicalMemory. When it ran, it returned nothing.
I disabled KVM on the node, disabled ballooning, passed the host cpu info to the VM, installed / enabled the QEMU agent on the host/guest vm, still no go. I wonder if the OS doesn't see the RAM (though it appears in system properties)? VirtualBox has a command, vboxmanage, that can expose additional information to the OS. is there a similar command that we can run in proxmox to do the same thing?
TIA