Search results

This is the intended behavior of Proxmox VE's restore utility as you marked the volume cpool-02:vm-107-disk-0 to not be backed up and therefore if you restore the VM from said backup it won't be restored from there. It just so happens if you restore the VM itself, that the volume...

Could you elaborate further on what storage and filesystem you use for your VMs?

Hey there! It seems like that your NIC suffered a hardware unit hang, could you verify that with the output of journalctl -b -g e1000e? It would also be helpful if you can post the name of your NIC, the output of cat /etc/network/interfaces and the syslog when the watchdog complains about your...

The vzdump utility is for creating backups only and the --prune-backups argument is only for overwriting the settings that were configured on the storage-level. It seems like pvesm set <storage> --prune-backups <options> and/or pvesm prune-backups <storage> would be the better fit for you, see...

Good to see the logs for verification! It seems clear to me that you suffer from the same issues as described in the linked threads and I would recommend to you to disable the RDMA feature on either the NIC itself and/or disabling the driver, however you see fit best.

How did you setup your network and did you assign the host a correct IP address in the installation dialog?

I see where you come from, but there are a few intricacies to make the backup format storage-independent, as each storage type does snapshots differently. That is why it's recommended to use backups for disaster recovery in the long term. But you can always rsync the qcow2 files for backup so...

What commands exactly cause a segmentation fault for you? A segmentation fault usually refers to some faulty behavior in code, but since you say they are caused by several programs it usually means that either the binaries themselves were corrupted on disk somehow or that your memory is faulty...

Welcome to the forum Grigori! It seems like your interfaces setup is fine, but threads from other users suggested that there are known issues with your NIC. It would be helpful to know if there were any errors setting up your NICs from the syslog (e.g. journalctl -g bnxt) and what errors were...

Have you tried removing the host key from /root/.ssh/known_hosts? Are there any error messages when you run the following command on the current node (simplicitycorp)? I'm assuming the values from your screenshots (ssh from simplicitycorp to pve). ssh -e none -o "HostKeyAlias=pve"...

FYI, as I just have realized this: You run a Copy-on-write (CoW) filesystem on top of another CoW, in this case qcow2 on top of zfs, even though zfs does provide the same snapshotting functionality for guests. This will usually result in performance issues and wear out SSDs faster.

The "Snapshots" functionality works on the guest-level, so usually they are not transferred by clones or backups. It is possible to create backups of the current state (by default) or specify a specific snapshot you want to make a backup of. The backups done of a VM with vzdump do not contain...

Exactly, it will remove any configurations where the VMID is in use for QEMU VMs (e.g. Backup jobs, Storage replication jobs, HA, ...). This checkbox makes sure that all disks that are owned by this VM are deleted, even though they are not referenced within the configuration file. This means...

Einerseits werden die Microcode Updates auch oft über BIOS/UEFI Updates eingespielt, und andererseits ist das bei Debian standardmäßig auch so, da diese Microcode Updates "non-free" Software sind, sprich der Microcode ist closed source und diese standardmäßig zu inkludieren würde gegen die...

I haven't checked the source code on this, but logically it would make sense that deleting QEMU snapshots is most efficient and as fast as possible when deleting them from oldest to newest, as the snapshots need to be written to the initial snapshot disk image. But it can also very much depend...

Grundsätzlich sind die Kernel Migitations Umgehungen von dem Kernel selbst, um vor Sicherheitslücken in der Hardware zu schützen. Microcode Updates haben verschiedene Gründe, welche sowohl Sicherheitsupdates als auch funktionale Updates (Stabilität, etc.) sein können. Siehe dazu die Release...

Die CPU Microcode Updates werden erst automatisch installiert und aktualisiert, wenn diese auch auf dem Host/den Nodes jeweils richtig aufgesetzt wurden. Siehe dazu in der Dokumentation hier über eine Anleitung wie dies gemacht wird. Es ist auch ratsam BIOS/UEFI Updates zu machen, die oft auch...

You can mount a custom RBD by adding a mount point through the Proxmox Container Toolkit CLI: pct set 297 --mp0 <pool-name>:vm-297-disk-1,mp=<mount-point>,size=16G Note that you might need to map it to a block device first and create a filesystem on it, see here.

Great that it pointed you in the right direction!

Could you try to run a memtest on your host and check your other hardware for fault behaviour? Could you try to reinstall the qemu and the kernel package?