Search results

There are so many ways posted in this thread that it's really not clear what works, what doesn't, what is actually needed, what is not. The problem is that those who find this will install based on one post to find that the next says don't do that or they have installed a bunch of stuff they...

Is it safe to change the type after the host was already installed using the default cpu?

Got it, it's more of a personal choice and based on your requirements. Thank you.

I have a cluster with backups configured which stores the backups onto network NFS storage. I was looking at the backup server a while back and now am wondering what the benefit of it is? If I understand correctly, the backup server is built into a cluster but it could also be used stand alone...

Got it. If I test and it goes well, assuming the CPU's don't change, do you feel from then on, I can count on live migration to work properly?

I read this in the documentation. This has a downside though. If you want to do a live migration of VMs between different hosts, your VM might end up on a new system with a different CPU type. If the CPU flags passed to the guest are missing, the qemu process will stop. To remedy this Qemu...

That worked nicely and now have a nice fresh new cluster. Thank you.

Thanks for offering to help but after things getting even stranger, I decided to rebuild the entire cluster. I backed all guests up onto NFS storage then rebuilt all of the hosts one at a time to keep everything running while doing so. Never found what happened but it was ssh related.

No problem, I'll use network storage. Just wondered if there was a way to copy guests directly from one host to another where there isn't a cluster. Thanks for your help.

I guess I should ask one more thing to be sure :). You mentioned no way to migrate from cluster to cluster but I'll have one remaining node/host and one new host before I create another cluster. Is there a way to migrate guests from host to host before I create the new cluster is will the...

Sorry, not asking about automated or live migration, just if there was a way to migrate even with guest shutdown from one host to a cluster. You say no above so that answers that. Yes, I could back the guests up to network storage and move them over. There aren't too many. Thank you. This gives...

Yes, these are production guests that cannot be turned off so I'm already taking chances by having them all on one host for this. That said, they are mainly redundant servers but still part of production as I need a 'real' situation to start using/testing proxmox. That's an interesting idea, to...

Solved using comment #2 suggestion. After upgrading from 7.1.7 to 7.2.x, I started having problems. Whether or not I broke something is not the question, I'm sure I did something wrong or at least will blame myself. However, I'm stuck in a whack-a-mole situation of ssh being broken across...

What ever happened as we've come to conclude is ssh related but something else. This started happening right after I upgraded three of the nodes from 7.1.7 to 7.2 and re-installed one of the nodes, 04. I have nodes 01, 03, 04 and 07. I noticed the problem when I could not move guests between...

From the link shared; This has a downside though. If you want to do a live migration of VMs between different hosts, your VM might end up on a new system with a different CPU type. If the CPU flags passed to the guest are missing, the qemu process will stop. To remedy this Qemu has also its...

So what is the answer since 'host' does allow it to install? Does it mean some guest limitations or something not so obvious initially? It may not be a proxmox issue specifically but an answer could help someone else trying to install these operating systems. I've installed it and it seems to...

UPDATE: Nope, this comment still didn't fix anything. I continue playing whack-a-mole fixing one node, then another breaks, it won't stop. I even ran this on all of the nodes. pvecm updatecerts The solution I thought for a while was as follows. This is done from each node to all the other...

Come on now, I did not hold back on information and I've been polite and professional the entire time. You make it sound like I wanted to mislead and cause more confusion than there already is. First you get your feelings hurt because it sounds like I'm blaming proxmox and then no matter how...

That only fixed the migration it turns out but that's good. At least I can move the guests and rebuild now. I'm sure there's one simple command to fix the rest but I don't have the energy to contracdict or confuse anyone anymore :). Thanks for the help.

Not sure why someone didn't specifically know this but a suggestion could have been this; node07 # pvecm updatecerts Done, everything works now.