Search results

This is a screenshot from pre PVE 9, though, right?

Sehr cool! Hast du überlegt, das, in welcher Form auch immer, direkt bei Virtio als Installationsschritt upzustreamen?

Besides the Ballooning Device being enabled, is the BalloonService running in the Windows VM? Does it go down after a bit of waiting? In the screenshot, the VM has an uptime of 36 seconds... chances are that the VM hasn't fully booted yet and therefore the BalloonService might not be running yet.

This looks like something went wrong with the installation medium. Verify that the ISO you downloaded is correct, and that it is copied correctly to the install medium: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#installation_prepare_media

https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher this should answer it :)

You mean booting the OS itself from a multipathed LUN? It might be technically possible to do so, especially when converting a Debian installation to Proxmox VE, but this is not a scenario we test for or have in mind with the Proxmox installer.

You could set the multiqueue for the virtual NIC(s). But not higher than the number for vCPUs the VM has.

? If you use the same encryption key you will get good dedup. For example, in a Proxmox VE cluster, you will use one encryption key per storage config. So if you have a second Proxmox VE cluster that is using the same PBS and datastore (ideally separated by namespace), you could upload the same...

On PBS you have it for file-based backups (host, CT). On PVE you have that as well, if the backup storage is a PBS. Then you can do that even for VM backups (given that the FS is supported)

the patch has just been applied. a newer version is not yet released. But once you have a version newer than the mentioned ones, they will include the fix.

Patches are applied and will be part of the next release of the following packages: qemu-server newer than 9.0.19 pve-container newer than 6.0.9

Ah sorry, didn't look too closely in which forum the post was... In that case, most of my reply is void ;) SSH and the HTTP API port ist what is needed. So port 22 and 8006, TCP.

Is the latency in the single digit ms range? Do you have a stable, redundant connection? Can you provide a 3rd vote? E.g. Qdevice? These questions are especially important if you want to use HA. Otherwise, two single nodes might be the better approach. In case you want to (live) migrate between...

We have customers who do run 5-node full-mesh clusters, for example with 4x 25Gbit NICs. Do not go for a ring topology as that could break in 2 places and then you have problems. The Routed with Fallback method is what you want...

Okay. Just to be sure, the ls output which reported that the pve2-vm directory does not exist, was run on the same node? vm-gravity-2?

Thanks! This is getting more confusing the more infos I get. The `ls` command earlier was also done on the same node (vm-gravity-2) right? Would it be possible to give us remote SSH access so we can try to debug this directly on that host? This would mean giving direct access to port 22 on...

Hey, thanks for the output. Unfortunately I currently can't explain why it ended up doing what it did. Could you please run the following debug build and get the journal? http://download.proxmox.com/temp/pve-cluster-9-rrd-debug-v2/ This one debug prints in a lot more places, which will...

What do you get back if you run info balloon in the "Monitor" submenu of the VM?

If you set the "is_mountpoint" it should be a dataset. Otherwise the path would not be a mountpoint. Using a dedicated dataset is what I would do. Having that separation give you some benefits, for example, should you ever want to use the send/recv feature, it will be easy for the backups alone...

Keep in mind that tihs stems from a time where all we had were HDDs. Given that ZFS is copy on write, the data will fragment over time, and if the HDD is full, it will need more time to find unused space on the disk. With SSDs where the seek time is practically zero, I do not think that the 80%...