Search results

seems to be working fine here: dig +short de3.cdn.proxmox.com @1.1.1.1 45.84.67.184 dig +short fr.cdn.proxmox.com @8.8.8.8 51.91.38.34 Is your DNS setup maybe the cause?

maybe, never tried it. it is definitely more complex and chances are that things go out of sync in the ceph config if you are not careful. or versions might differ a bit between the ceph mons. if things go wrong and you run a unique setup like that, you will be more on your own as not many...

Wie ich schon versucht habe zu erklären, ist der große Unterschied von PVE 8 → 9, dass die Host Sicht des RAM Verbrauchs jetzt deutlich richtiger berechnet wird. Unter PVE 8 war der Wert mitunter deutlich zu niedrig. Das Balloon Device zu aktivieren, macht nichts Böses! Das Ballooning (VM gibt...

Okay. For the initial sync, you could have either used a "Removable Datastore", sync to it, move it to the remote location, add it there as well and then sync from it to the local remote datastore. https://pbs.proxmox.com/docs/storage.html#removable-datastores Or, the harder way, manually copy...

Is it about the first initial sync or about later syncs?

TIL about gdu. Deutlich flotter als ncdu. :) @TErxleben je nachdem wie alt der Host ist und was da abseits von PVE irgendwann mal drauf installiert wurde, kann auch ein apt autoremove und apt purge manchmal ganz gut tun. Auch alte Kernel deinstallieren die schon lange Zeit nur herumliegen...

Can the clusters talk directly to each other?

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, or use the formatting buttons at the top of the...

In the Hardware menu of the VM.

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 berücksichtigt. Mit PVE 9 wird hier besser der...

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, passiert kein Ballooning, aber das Ballooning Device...

No, the VM to be imported needs to be on a storage where the virtual disks will be stored as files (vmdk).

Yes, I am quite sure: $ apt-cache policy pve-edk2-firmware-aarch64 pve-edk2-firmware-aarch64: Installed: 4.2025.05-2 Candidate: 4.2025.05-2 Version table: *** 4.2025.05-2 500 500 https://enterprise.proxmox.com/debian/pve trixie/pve-enterprise amd64 Packages as @leesteken...

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 options at shop.proxmox.com. If you bought 6x...

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 return information like this: # info balloon balloon...

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 that Device without a driver. Try to let Windows find...