Search results

I highly appreciate your input, Fiona! That means waiting until no more lock is held on the VM should prevent any issues with concurrency in the future, did I get that right? And hopefully, also the qemu start issue I mentioned earlier. So I don't have to perform an additional check if there...

Thank you Fiona, but I might have misunderstood your message. I thought Qemu exited when trying to start the VM because it was unable to get the lock as maybe one of the config requests still had the lock acquired. In this case, I would implement a method to wait until there is no more lock on...

Thank you! So it should be enough to check if the VM still has a lock and wait until it is released to prevent such issues in the future? I'm using ZFS. I did not see the GPT issue again so far

Nope, nothing. Is Proxmox acquiring a lock on the vm when setting the config (hardware/ cloudinit or firewall)? Maybe it was just not ready yet.

I just had exactly the same issue. The VM was created using the API and is started after setting the config (hardware + clouding + firewall). I tried starting the VM manually and that worked without any issues. But I'd like to figure out why this happened in the first place to prevent this...

Ja, das ist nun auch mein präferierter Ansatz

Hi, Ich sehe beispielsweise sporadisch folgenden error im Cluster Log: qmconfig:277: unable to read tail (got 0 bytes) Ich konnte in dem Kontext wenig dazu finden, würde spontan aber vermuten, dass der Config API call zu nah auf den clone vm request folgt. Dann würde ich hier davor noch...

Thank you @fiona for your quick reply! Is there any chance to sponsor development for such a feature?

Hi, Just checking in, has there been any progress? Unfortunately, we rely on this integration as we currently cannot migrate any VMs with snapshots

Leider nein. Nach wie vor das selbe Problem

So ziemlich alle endpoints, clone, power actions, vm config, cloud init, ip set etc. Genau, damit meine ich eine API Call der eine UPID liefert.

Hallo Proxmox Team, Ich nutze Proxmox primär headless über die API und möchte nun das Error Handling verbessern, da wir hier teilweise Probleme hatten. Insbesondere, wenn mehrere Tasks recht zeitnah hintereinander ausgeführt werden. Reicht es hier zu prüfen, ob Proxmox noch einen Lock auf die...

Thank you! https://bugzilla.proxmox.com/show_bug.cgi?id=4820

Replication by default doesnt make any sense for our use case at the moment. But I'd highly appreciate the "one time" replication when running the migration. Any chance you could add that to your roadmap? I'm sure I'm not the only one who would benefit from that. We have a bunch of nodes in a...

root@pve1:~# pveversion -v | grep qemu-server qemu-server: 7.4-3 root@pve2:~# pveversion -v | grep qemu-server qemu-server: 7.4-3

Both systems are using ZFS and have version 7.4.3 installed However I still receive the error message when trying to migrate a VM 2023-06-29 13:59:31 can't migrate local disk 'local-zfs:vm-139-disk-0': online storage migration not possible if non-replicated snapshot exists

Do I need replication or does it work with local storage as well? I have a bunch of VMs I'd like to migrate to a different host however all of them have snapshots.

Hi, Wir nutzen Proxmox komplett headless und haben die grundlegenden Funktionen über die API implementiert. Die Images basieren auf den offiziellen Cloud Templates der Distributionen und nutzen Cloud Init zur kontextualisierung sowie qemu-guest-agent zur Kommunikation mit der VM. Das...

Hallo, Ich betreibe ein Proxmox Cluster welches aus 3 Servern besteht. Ich möchte nun einen dieser Server gegen einen stärkeren tauschen. Auf dem betroffenen Server laufen einige VMs, die anschließend als standalone auf dem Server weiterlaufen sollen, nur eben außerhalb des Clusters. Daher...

Niemand noch eine Idee? Bei jedem erneuten run von Cloudinit nach der initialen config, werden die SSH host keys neu generiert. Leider recht nervig