Search results

So if I want the convenience of the GUI, I need to setup the cluster and in case of (temporary) down time of one node use 'pvecm expected 1' to be sure backupping still works. Or I need to forget the cluster and work with the pve-zsync commandline. Correct?

No problem. The VM's of node 1 will stay online, don't worry. But be sure to have all the prerequisites when you start a cluster and not like I did. I used lvm-thin on both nodes, but that was useless for me. As lvm-thin doesn't support replication for example :D

We have a solution with 2 nodes in a cluster. We won't use HA, we only want to use the replication feature, just to copy VM's to each other to make our solution redundant in a way. We used this also in our old Hyper-V environment, but in Hyper-V we didn't need to setup a cluster. I was just...

For future readers, please try this first, It can save you alot of time: https://forum.proxmox.com/threads/how-to-fix-non-booting-linux-vm-imported-from-a-gen2-vm-hyper-v-source.45070/

The problem An imported Gen2 Hyper-V VM won't boot. You get an EFI Shell or you are just stuck in the boot sequence. When you go into the UEFI BIOS (press ESC during startup of the VM) you are able to make modifications and boot from a file. This works, but you are not able to save changes...

I don't understand the ring1 recommendation on NIC2? @wolfgang In my setup I would attach NIC2 to ring0 and according to your documentation the ring1 adapter should be physically seperated from each other? Did you mean I have to attach ring1 to NIC1? I'm able to add another NIC to this...

I have an easy solution (2 minute) for troubled Hyper-V Gen2 Virtual machines running Linux (and maybe also Windows OSses, but I haven't tested that yet). For future readers, please try this first, It can save you alot of time...

Hi guys, I'm evaluating Proxmox and so far I'm impressed! I have a question: I have two physical machines that will be running Proxmox and I want to setup a Cluster. They are running several NICs and I want to make the Cluster config right. SERVER A NIC1 192.168.150.1 Meant for...

For what's worth it, I have had the same issue and in my case it was this: I recreated a new VM with IDE0 and attached the qcow2 image to it and it was working again. :D Of course you can also detach the hard disk from the VM and retach it as IDE0.