Search results

Hello all, I tried to find a way in proxmox to "bundle" vms together in a group which can then be addressed with functions like a single vm. Like I want to be able to migrate a pool from one node to another in a cluster. I would like to see it more like a group of vms rather than a "pool" of...

It just came to my mind that the whole issue is quite simple to solve: all needed is somebody having daily snapshots of the proxmox repositories and one would easily be able to update to any given date (version). Is there someone out there having such an archive?

Is there nothing else to update besides the corosync.conf?

... when I have a cluster with 4 nodes, where one is down for some reason. Then I add a new node which runs perfect. Then I restart the node that was down during adding the new node. Does this work, or is it a problem in some way? The same btw might happen if you have to restore some node from a...

Hello all, I recently ran into the problem that an updated proxmox node cannot join a cluster with older version. So I tried to install the node with the same old proxmox version - which works. I can join the cluster. Only I had to find out that installing ifupdown2 the usual way updates...

Thanks for your help. I changed the ICODE, thanks for the hint. Last question: how am I to make updates only taking small steps for old versions? Lets say I start from the 6.0. How do I update to 6.1 ? My understanding so far was that this is only possible as one step to the current last minor...

Is there a possibility that the problem has to do with passwords? When I joined the node to the cluster this node had another password entered during the setup phase. Is there a way to change this password for pve? Or is "passwd root" sufficient?

You're right. The major reason against this idea is the downtime. But there are others as well. We need to use the old servers for some time as a failover resource until all new material is delivered (which is beyond our influence). PS: Whats the right tag to include lists like above? Obviously...

Hello, thank you for coming back to the issue. Here is the requested output (hopefully correctly inlined) # journalctl -u pve-cluster Dec 15 13:31:25 pm-249 systemd[1]: Starting The Proxmox VE cluster filesystem... Dec 15 13:31:25 pm-249 pmxcfs[1631]: [quorum] crit: quorum_initialize failed...

Let me mention that we read the doc you pointed to before and there: Preconditions Upgraded to the latest version of Proxmox VE 6.4 (check correct package repository configuration) So we are in fact at the beginning of your requested upgrade and find out that even the one-by-one upate to 6.4...

The thing is we would like to consolidate the cluster with new nodes and killing old ones. So the idea was to put in one new node (which is large enough to take the whole cluster vhosts) with 6.4, which is needed for update to 7.X anyway. So put in node, migrate everything to it, kill all old...

Hello all, I tried to join a new node today to an existing cluster with version 6.0-4. The new node has version 6.4 (I thought it would be a good idea to use the latest minor version). First everything went well, but after completion it turns out the node is not active in the cluster. It was...

Es ist ein Cluster, aber leider sind mittlerweile sehr viele VMs drauf und eine Migration aller VMs einer Node ist nicht mehr so ohne weiteres drin. Daneben bin ich sehr vorsichtig mit der Idee dass nach einem Update die geupdatete Node so ohne weiteres wieder in dem Cluster funktionieren wird...

Hm, das bedeutet wohl ich muss die Ursache selbst suchen. Es handelt sich um produktive Systeme wo ich nicht einfach mal so updaten kann (wegen der Downtime und wegen der unbekannten Stabilitaet des neuen Systems).

Hallo, vielen Dank fuer die Reaktion! Ich muss dazu zwei Dinge anmerken: 1. Das ist Proxmox 6.0.-4 2. Der Gast ist Linux Kernel 3.18.43 3. Ja, der Gast laeuft bei dem Versuch, das ging bist virtio7 einwandfrei ... Beides koennte Auswirkungen haben. Ich habe im Kernel-Source allerdings keinen...

Hallo zusammen, hat jemand eine Erklaerung dafuer warum ich es nicht schaffe das 9. virtio-blk Device hinzuzufuegen. Da erscheint folgender Fehler: Fehler: 400 Parameter verification failed. virtio8: hotplug problem - VM XXX qmp command 'query-pci' failed - got timeout Eigentlich hatte ich...

I can add this one to the list of possibilities why the error message shows up: # apt-get update Get:1 http://security.debian.org buster/updates InRelease [65.4 kB] Get:2 http://ftp.de.debian.org/debian buster-updates InRelease [51.9 kB] Hit:3 http://download.proxmox.com/debian/pve buster...

Sorry for hijacking this thread, but as the OP seems to use a Mikrotik CHR and solve performance problems I'd like to jump in and ask pretty much in the same direction. We tried some CHRs in our setup and they are aweful in terms of performance. Even with their P-Unlimited license they are not...

Ok, in the meantime I found out that my question probably misled you in the storage direction. But in fact I only searched for a possibility to mount some block device (which can be a zfs vdev) inside a vm. And guess what, striking easy: qm set VMID -scsi0 /dev/someblockdevice and you have a...

Hello, it seems the common config for vm drives in proxmox is file-based. But of course qemu can do more. So how do I tell proxmox to use a zfs vdev as block device inside a vm? -- Regards