Search results

  1. B

    ESXi 8 VM on Proxmox - Memory Usage Question

    You have a problem then. What do you think it should do? More importantly, what do you think it should do after it has been running for a while with the guest allocating memory to its guests? BTW, if you are passing any PCI devices into a VM, then it _must_ allocate and commit all of the...
  2. B

    PVE node RAM consumption

    I didn't write the PVE GUI and so don't know where which numbers come from. But it is presumably because that VM hasn't needed to use some of the memory yet and so it is "free" according to the metric that PVE uses. There are constantly people here asking for the "real" memory usage to be...
  3. B

    PVE node RAM consumption

    In case somebody asks, lazy allocation is usually a win. Lots of programs (talking regular programs here) allocate a lot more RAM than they ever use. Java apps are notorious for this but it is really quite common. And it makes sense a lot of the time. Programs usually allocate lots of small...
  4. B

    PVE node RAM consumption

    To elaborate a little; Linux RAM allocation is "lazy". When you allocate a chunk of memory it is not really committed until something touches it. Until then it is just an entry in the page table. In some cases you do need to have that memory be committed and in RAM rather than, say, in swap...
  5. B

    PVE node RAM consumption

    RAM is not shared between virtual machines.
  6. B

    PVE update removing proxmox-ve kernel

    He also has the Debian kernel installed for some reason. ETA: And firmware-linux-free as well, which probably causes a conflict with the PVE version.
  7. B

    PVE node RAM consumption

    One sure way to get a VM to use less RAM is to allocate less RAM to said VM. I really don't understand "I gave it X GB and something must be wrong because it uses X GB". Really odd. If you didn't want it to use the RAM why did you allocate it?
  8. B

    Proxmox VE rocks, except for this one thing, the memory usage graph.

    That info is from inside the VM in this discussion, not from the hypervisor. As such it is irrelevant to the question of whether there is enough RAM to support another VM. For that you need to know the hypervisor's view of things, which is what the graph on the PVE dashboard shows. The Linux At...
  9. B

    Microcode Updates

    If you say so. I wouldn't trust such generalizations without looking it up. Often the low-power variants lack some features. I don't know anything about that script. But what it appears to be doing is just what I do manually. I don't know where it is getting the list (which is a problem to be...
  10. B

    Microcode Updates

    Sorry, I misunderstood. Are you sure both do in fact support GVT? Microcode doesn't really have anything to do with that. In my experience you never need microcode updates to add a feature, they generally fix bugs in the CPU. What "microcode update " are you "running"? I just apt-install...
  11. B

    Microcode Updates

    Microcode gets loaded into the CPU early in the boot process from the initramfs. This happens on every boot, it is not stored in flash or anything like that. If there is a BIOS update that includes the microcode, then that is more or less permanent. You need to install the microcode package and...
  12. B

    Proxmox VE rocks, except for this one thing, the memory usage graph.

    "From a user standpoint"? What user? A user inside the VM or the person managing PVE? That is what @LnxBil is saying. There are different constituencies that necessarily have different views and the numbers are intended for different purposes. From the point of view of the PVE-manager the 18 GB...
  13. B

    Question about Proxmox and OpenWRT

    Maybe you need to tell us more about how your LAN is set up. You have private IP addresses on both sides of your OpenWRT. Is there another router somewhere? There kind of has to be for anything to get out to the Internet. THAT router is almost certainly doing NAT aka Masquerading, which means...
  14. B

    Question about Proxmox and OpenWRT

    Err...255 would be the broadcast for that subnet.
  15. B

    Unable to reach GUI

    This feels like a problem with your pfsense setup. Do you have any VLAN's configured? Are you other devices on 192.168.55.xx?
  16. B

    SeaBIOS fails to boot with Display=None, and OVMF fails to read data from VirtiO disks?

    The memory use is normal. With pass-thru all memory assigned to the VM has to be pre-allocated in case the device does DMA to it. Don't know about the other problem but i440 is a really old chipset that doesn't support PCIe. Maybe q35 would work better? ETA: Also, you can't just switch between...
  17. B

    new installation unable to update proxmox

    No, it isn't about logging in. You are getting "network unreachable" errors. There is some kind of issue with your network. Please post (in code tags) the output of these commands: cat /etc/network/interfaces ip a I also notice that all the addresses are IPv6. Do you have IPv6 configured on...
  18. B

    Config File Changes During Apt-Upgrade

    I should also probably mention that whichever choice you take nothing will be deleted. Either your old file will be renamed with a different extension, or the new one will be saved with an extension. So either way you can always go back.
  19. B

    Config File Changes During Apt-Upgrade

    This kind of thing only happens when you have made local changes to a config file. So it is on you to know the reason you made the change and whether or not it is still important. There is no one-size-fits-all answer to the question.
  20. B

    Config File Changes During Apt-Upgrade

    There is only one actual change there, the others are commented. And the change is trivial, you added a keepalive interval. So it doesn't really matter much. I would apply the change but maybe you had a reason for adding the keepalive in which case you should keep the old version.