Search results

If it is a live migration, you should see a task (bottom panel in the UI) that is called "VM <vmid> - Migrate". Double click on it and you should see the logs. That is what would be interesting to see. Not sure I fully understand the overall situation, but in order to migrate a VM without...

Or in other words, do you actually have a "local-lvm" storage? If you installed Proxmox VE with ZFS or BTRFS as root file system, the default local-X storage can be named differently.

Hmm I don't see any problem with the config of the VM. How do you test it in the Windows VM? Have you done some benchmarking on an empty VM disk image directly on the PVE host? This way you will know what you can expect from the ZFS pool itself. fio on the host with an empty disk image as...

How is the VM configured? You can post the output of qm config <vmid> inside tags

In a live migration needs to transfer the state of the running VM. If the VM has a lot of memory or has its memory changing rapidly, it can take a long time or might never finish because the migration might not be able to catch up to the changing RAM of the VM to get the difference small enough...

I know it is the always ongoing discussion, but I am really curious, have you set the brightness and contrast levels of your screen to something normal? Most screens have both set way to high. This usually leads to images having completely blown out colors andmissing nuance due to the high...

Zum besseren Verständnis: beim Starten der VM sollte die geänderte Config angewendet werden. Ein Neustarten der gesamten Node ist dafür nicht notwendig.

Indem du ein Storage hast das als Content auch Backups konfiguriert hast und dann entweder über das <node> -> <vm> -> Backup Panel oder das Datacenter -> Backup Panel. Das kann entweder ein lokales Storage sein, von dem du dann die Backupdateien weg kopierst bevor du neu aufsetzt oder ein...

Soweit ich weiß nicht, bin jetzt aber auch nicht der GlusterFS Experte. Ceph könte für dich als Alternative interessant sein, wenn es mit Hardware und Netzwerk zusammenpasst.

am einfachsten indem du ein backup machst und wieder zurückspielst.

apt install --reinstall pve-manager This should install everything again for the web GUI to work as expected. Consider buying a community subscription if you are that annoyed by that pop up and feel good that you are supporting the project and help to pay the developers' salary as well as for...

If you edit a storage, you can limit it to certain nodes only. In the edit window top right. This way the PVE tooling will know on which node it can expect which storage and the migration should work.

Hmm, I would try to see what happens if you try to install the latest updates: apt update apt full-upgrade full-upgrade is important in order to resolve new and changed dependencies.

Did you install some updates recently? Do you see anything in the browsers Console tab in the developer tools?

Ich glaube da hat sich ein Missverständnis eingeschlichen. PVE setzt auf Debian auf. Man kann dann laut verlinkter Anleitung PVE nachträglich installieren. Abgesehen vom Festplatten / partitionslayout sollte es kaum von einer PVE Installation mit dem PVE eigenem Installer unterscheidbar sein.

AFAIK this should be possible

This is usually caused by repositories not configured correctly. Can you run apt update and show the output? This is the quickest way to determine which repositories are set.

Wenn die Platten wieder erkannt werden sollte ein zpool import den Pool darauf wieder finden.

This can happen if there is too much load on the zpool. IO gets high and the time until the snapshot for the next replication run is taken is too long -> time out. Check the IO delay graph in the node summary if you have peaks that correlate with the timeouts

This is very much a problem! Use different shares so that each cluster has its own and cannot interfere with the other cluster.