can you please post the full config of the VM? You get it by running qm config 100 on the CLI
What is the hardware of the host? Mainly, which CPU is used? What is the output if you run lscpu on the CLI?
Please paste the output within CODE tags...
Did you add an EFI disk with Pre-Enrolled keys? Then Secure Boot is enabled and not every Linux Distro can boot with that.
Remove the EFI disk and add a new one with the "Pre-Enrolled keys" checkbox disabled and try again :)
Ist bei Windows der "Balloon Service" von der VirtIO ISO installiert und gestartet? Unter Linux liefert der Linux Kernel direkt die Infos über das Balloon Device.
Das gilt auch für pre PVE 9 ;-)
Das war schon immer so. Auch pre PVE 9 war das Balloon Device nötig, um eine akkurate Gast-Sicht in der VM Summary auf den RAM Verbrauch zu bekommen. Die Host-Sicht auf den Gast RAM war nicht ganz richtig und hat einige Teile des Overheads nicht...
Siehe hier: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher
Wenn der Gast die richtigen Infos via Ballooning Device liefert, stimmt die Anzeige auch wieder. Solange Memory und Minimum Memory gleich sind...
Technically, this surely is possible. How will it perform once it contains quite some data and is under load? No idea. It might be fine for your workload. It might be bad…
You'll have to see how it goes.
The pve-edk2-firmware-aarch64 package should be available in all repositories, test, no-subscription and enterprise from what I can see.
The latest version in the enterprise repo is pve-edk2-firmware-aarch64_4.2025.05-2_all.deb
First of, small but important difference: the primary license of Proxmox products is the AGPLv3. You are buying subscriptions :)
The Subscription for Proxmox VE needs to match the number of physical CPUs in the server. That's why you have a few...
Hi,
have you considered using the auto-install-assistent and provide an answer file with the configuration details, already?
https://pve.proxmox.com/wiki/Automated_Installation
Awesome. This seems to be the step I was missing. Thanks!
Copying virtio.iso:\Balloon\2k8\x86\* to c:\Program Files\Balloon and executing "blnsvr.exe -i" as admin did the trick for me on win2k8/x86. BalloonService now shows as service. Graph in...
PVE 9.1.1 with vm win2008R2 the memory usage show correctly after install balloon service
https://pve.proxmox.com/wiki/Dynamic_Memory_Management#Enable_Auto-Ballooning_on_Windows_2008r2
win2008r2 with virtio version 173
Those will not report detailed memory usage. See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher
The old Win 2008 machine does not report back detailed memory info. What you need is to get the guest to...
Only once you get more detailed infos back via `info balloon` in the Monitor menu, can Proxmox VE itself show the inside view of the VM.
So if the BalloonService is up and running, the Ballooning Device enabled, things should be good. Except...
If that is all you get, then no, it is not working as expected. Is the Balloon Device enabled in the VMs -> Hardware -> Memory settings? Is the "Balloon Service" running in the Windows guest?
Is there no device without a driver in the device...
Hmm, how did you create that ZFS pool? Which version of PVE?
I tried to recreate that in a test VM and even after writing almost 10G into a 10G volume, I get the following result:
root@pvezfstest:~# zfs get all vms/vm-100-disk-0
NAME...