Search results

We do not use LXD at all. We never used it, and we will never use it. We use LXC.

You simply specify the VLAN tag in the VM network config (or when you create the VM).

Looks there are no disks inside the VM? (knowing the VM config would give more insights).

GUI is client side only. Try to clear all web caches and reload the GUI.

The backup task generates a summary and sends it using email.

For Ransomware protection, Tape backup is also a good idea..

The problem with many proprietary storage vendor is that they simply say: "We do not support Proxmox". It won't help if we implement a Cinder plugin, because the other endpoint is still on the storage box and controlled by the storage vendor. So we could never debug or fix problem on that side...

Yes, because Proxmox VE does not use libvirt at all (its a different product).

No, that is not possible. PBS does a lot of pre-processing on the client side: - compression - optional data encryption - chunking - checksum generation (SHA256) Only speeding up TLS would not help at all.

Offensichtlich funktioniert dein Netzwerk nicht - zumindest ein DNS Problem

Für größere installationen empfehlen wir CEPH als Storage zu verwenden. Siehe auch: https://ceph.io/en/discover/technology/ Konfiguration und management sind in unser GUI integriert. Success Stories: https://proxmox.com/en/about/stories?f=7

pmxcfs (/etc/pve/) is a cluster wide file system. So you will not get inotify events if content is modified using the cluster stack.

The "cluster/resources" status is a summary of all nodes. There can be a little lag, becaue data need to be sent to all nodes. The "/nodes/vps2/qemu/200/status/current" status is more accurate, because that API call directly connets to the node the VM is running on.

AFAIK there is already such check based on the storage configuration. Of cause this fails if you have a wrong storage configuration. Anyways, I guess this check could be further improved...

First, I want to notice that the recommended way is to use a shared storage for HA, for example Ceph. Please notice that all things you describe above simply cant happen in such (the recommended) setup. It is simply considered to dangerous to auto-cleanup, because it involves deleting volumes.

Yes Yes Yes, you can use PBS to allow simple disaster recovery and migrating. But keep in mind that VM IDs from different hosts may clash if you only use one datastore. To avoid that, you can define more than one datastore, i.e. one datastore for each host (or cluster).

You can configure the DNS settings for the Container using the GUI.

You need to disable HA for VM 103, then test again. You can re-enable HA when it works again.

There is usually a way to to this from inside the VM. For example, the qemu guest agent provides a "--fsfreeze-hook" option.

Its a normal HTTP get request, so you add the pid as query argument: GET /api2/json/nodes/{node}/qemu/{vmid}/agent/exec-status?pid={pid}