Search results

I know that you've published a bug tracker portal for requesting new features by the users, but referring to the newest "Import wizard to migrate VMware ESXi guests to Proxmox VE" innovation and taking the opportunity: It also would be nice to get the "import OVA image wizard" option. :)

I won't argue with that ;) I'm not a blind fanatic of VMware, I can see what they are doing wrong ;)

Yes, I can agree with that. I only would like to have the option to declare my memory with two units, MiB and GiB like in VMware: It would be nice to have this option for the disk size also. PS And this is exactly what I wrote about in the Bugzilla comment, why you shouldn't do it like...

Hi, I've created the ticket on Bugzilla, but I don't know if it will be processed. It's only a small feature: I also have another small request. Could you change the way of declaring the RAM for the VM, from MiB to GiB? No one is using megabytes for VMS' now, the standard is dozens of...

I make the changes only on the second node, which I try to join the cluster with. Yes, I have backup's. "Master" node works fine. I'll keep that in the back of my mind. For now, we can skip this part. When I got the message waiting for quorum... I tried to make the quorum via qdevice. But we...

OK. I tried to do this via web, and I'm in the same situation. Web UI on master node hangs on: The joining node hangs on: [edit] After a lot of tries, the joining node hangs on: The master node has the same message as previously. After hours of trying, in my opinion, there is...

Thank you. That procedure rebuilt the damaged node in a single mode. I keep trying.

Thank you for the advice, but I'm using a 10 Gbit network as a storage network, so I'm not worried about this part. No, I have been doing it via CLI due to a "separate network" scenario.

I created the new thread: https://forum.proxmox.com/threads/problems-with-cluster-adding-nodes-and-qdevices.137063/

I'll to do that. Thanks. PS I created the new thread: https://forum.proxmox.com/threads/problems-with-cluster-adding-nodes-and-qdevices.137063/

Hi, As some of you have already noticed in other threads, I have huge problems with the cluster and more precisely with adding a node and qdevice for quorum. Without writing too much, I'll describe my issues. I migrated from VMware to Proxmox, and that part was successful. I have two separate...

OK. For everyone who has the same problem and can't solve it. The solution is to use FQDN instead of hostname or IP for adding the node to the cluster. I don't know why it works like that, don't ask me, but it worked for me at last.

Before adding the node to the cluster, I removed all VMs (I made a backup and wanted to restore after joining a cluster). I'll create a new thread and try to get all of my problems in it. PS It's not my first time creating the Proxmox cluster (I've used it since about 2018). As I wrote in other...

Restore standalone node after failed cluster join.

OK. How to restore this backup from sql file?

I have the same problem while adding the node. But it also broke my pve2 configuration. Why, during the adding the node process you don't create the backup of /etc/pve folder on adding node? What am I supposed to do now if adding the node hung on the "waiting for quorum..." message and deleted...

I have the same issue. I'm using the option 5.4.3. Adding Nodes with Separated Cluster Network. The hosts files are correct on all nodes, I can ping the hosts by hostname, and I can connect between them via SSH. What's wrong? I never had such problems with older versions of PVE. Nodes are...

I'm digging up the topic, is there any progress on that issue?

How did you resolve this error? I have the same issue...

Awesome news!!