Search results

Never mind - @JerryLees had it. After reading his post I changed the MTU to 1500, but I'm still new to Proxmox (well, back to it after years) and I forgot to click apply. Working now.

Resolved this - the MTU setting of 9000 on the 10G link was causing ssh to time out.

I'm struggling with this as well on a new cluster. Following the steps y'all took I got migration to work on one interface, but not the 10G interface I'd rather have it using. ssh -o "HostKeyAlias=myhost" root@myhost-10G-network-address doesn't work, and reducing the MTU values on that...

No joy. Went through recreating the certs again, and running pvm updatecerts on both machines and it is still in a state where it will migrate using the slower network, but not the faster network. When I try I get > 2025-06-24 19:47:38 # /usr/bin/ssh -e none -o 'BatchMode=yes' -o...

I preformed some of the steps in this thread on a similar topic. Basically, this: log into pve1 cd .ssh mv id_rsa id_rsa.old mv id_rsa.pub id_rsa.pub.old mv config config.old log into pve2 cd .ssh mv id_rsa id_rsa.old mv id_rsa.pub id_rsa.pub.old mv config config.old pvecm updatecerts back...

Basically what the title says. When I try and migrate a test VM from the original node to the new one I get a status box with no content, and when I choose stop I get this: 2025-06-24 16:40:26 ERROR: migration aborted (duration 00:00:22): Can't connect to destination address using public key...

Well, I can't say I fixed it because I ran into another issue related to permissions - can't ssh from the primary cluster node to the new one. So working on that now. <sigh>

ok, AI to the rescue. Went to datacenter, selected the storage, chose "edit" and made sure both nodes were connected. Testing now...

This is my fault - trying to create a cluster and thought I had the second node configured as the first, but I missed a step: Node 1: local ZFS pool on the boot NVMe: named local-vfs ZFS pool for VM storage: named vm_zfs Added vm_zfs in datacenter view as storage for VMs with the same name...

That confirms my understanding. Thanks!

I'm migrating a cluster from XCP-ng to Proxmox. I'm using Vinchin for this and for the most part it's not too bad, provided I don't need to boot from a Centos CD and reconfigure the start environment to include VirtIO drivers - I've done this twice and am working to not have that happen a third...

Awesome. I don't see that stated in the docs, but now that you've made it clear I don't need to worry about that. :) Part of the goal with my move is to do away with a shared storage backend that I no longer trust. I think this probably gets me there, and will provide the peace of mind to...

Thanks, Alwin. After reading the thread where people document their Ceph performance, I'm not sure I'd be happy with that solution. I can see backups really slowing things down if I were to go that route. So, with storage replication: can it failover automatically? Searching shows some...

I ran a Proxmox cluster for a while a couple of years back and was reasonably happy running on ZFS as local storage for VMs, but wanted native support for Veeam so I moved to Hyper-V. I'm not nearly as happy with Hyper-V, and am at the point where I'll either install reinstall my VMs on bare...

Thanks,Wolfgang. :)

I'm in the process of migrating from Proxmox to another virtualization platform because business needs require Veeam, and Veeam doesn't support Proxmox. To do this I've been pulling a node, configuring it using the other hypervisor, and pushing a restore of my VMs to the new hypervisor. I've...

Yeah, but I didn't want to say that because it's cool. Though I'm happy I didn't need to be that involved. Or at least, not yet. ;) Proxmox occupies a very good niche, with great utility and a very reasonable price. I'm glad I learned it. Business needs change (and businesses change...

Thanks, Thomas. My first trial run with a Centos 7 machine worked once I selected the recovery kernel. I haven't tried the Ubuntu machine yet - I may need to try your solution there. It's innovative though. I dig it. :D

So my business focus has changed a bit, and now I'm selling backups and DR. Which means I'll be running Veeam, which means I need to switch my cluster to Hyper-V or VMWare in order to support the most useful functions that Veeam offers. Is there a solid tutorial on migrating to Hyper-V? Is it...

Thanks, folks. I've always done it on an IP basis in the past, but I'm using an existing QNAP machine now and the ip address permission system was really hard to find. Once I located that backups started to run. Thanks for all your help. :)