Search results

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}

Please update your software. You have version 3.0-1, but you need at least version 3.0-3.

What vulnerabilities do you mean exactly?

Maybe the data on the USB stick is damaged?

PBS uses deduplication for all backups. So there is no need for Incremental or differential backups. You get that automatically.

Seems your network is down: > Sep 04 06:10:50 pve-node-08 corosync[3659]: [KNET ] link: host: 11 link: 0 is down Maybe there are more hints in syslog? I can also imagine a problem with your network switch. Does it help if you restart the switch?

We modify some container sytem files on startup, so we need to know the exact OS version. System updates are required to maintain security. If you do them manually or atomatic is up to you.

There is no such method, because VM names are not unique...

No, currently not. The system is designed for SSDs.

You need to use "https", not "http". In your case: https://192.168.1.252:8006/

I assume you test with different storage types? VMWare file format vs. LVM-thin. Talking about LVM-thin, it is known that first time block allocation is quite slow. My guess is that this is the cause for the bad result of your benchmark.

AFAIK this board is still not available (will ship end of year).