Search results

Great - thanks for the reply. As this will be a 100% new install on the 7.1 machine do I need to create the guests with the same settings manually or is there a restore process that will handle the config as well? Backup & Restore doesn't seem to touch on this and Upgrade from 6 to 7 seems to...

I have a small cluster of three running 6.4. The reason for three was so that one host could receive backups and run lower resource guests and the third (a NUC) was there just to have an odd number to ensure quorum. I'm planning to update to 7.1 and add a proxmox backup server but don't think I...

... I feel like the fact that the "new" node doesn't show an IP from one of the original node's pvecm status reports is odd. What would that mean?

And it get's even spookier - I just loaded the gui management from one of the nodes that was in good standing and suddenly the new pvnBax node isn't there at all and the Cluster Summary page is back to only thinking there are 3 nodes. So I loaded the gui mangment on pvnBax and it shows the...

Does anyone have a suggestion or knowledge of what I am missing? The more I read the more I'm convinced it's something with the corosync setup but the manual shows straight forward vanilla setups which doesn't help with troubleshooting a long lived cluster that has new nodes and has lost...

So this morning, once again I tried to shutdown pvnOne which is the node I intend to remove and I'm monitoring pvnBax the new node. Once again it sees only itself once pvnOne is gone. Looking at it's syslog this is what I see:

Still grasping at straws here... I started looking into the possibility that there's some misconfiguration with corosync and am reviewing those docs but am not 100% sure. Looking at it's config I do see that under the totem heading it's referencing a bindnetaddress of an IP that's not beenin...

Am I missing something that would make one node essential to the quorum?

I followed the directions in the docs for adding a new node and everything worked great. Then as the start of removing one of the old nodes I simply shut it down after all VMs were safely migrated to other nodes. As soon as it is powered off the original other nodes lose the new node and the...

Ok... so in case anyone stumbled here to find a solution after my stumbles above the solution was I had to use the GUI on the destination node and under my local-zfs | VM Disks area REMOVED what it still claimed was there. I had already deleted the files from the destination node but I'm...

In my particular case 'rpool/data/vm-101-disk-0' isn't actually on the target node. On the target node I do see that filename in: /dev/rpool/data and /dev/zvol/rpool/data I'm guessing the second one since the storage is referred to as zvol in the gui? And after removing the "101" files...

What's the solution though? I have this same or very similar problem but when I go to where it says it exits there's only an empty directory. Or maybe I'm looking in the wrong place or on the wrong node? I am assuming this means the replication target file already exists... Where would this...

Well that made the swap file... and it was very easy so thanks. Marking this solved although I guess we'll see if the problem really was swap. I'm stressing the node now with a 24GBram/6 core Win8 guest, and two four core/4GB RAM guest. With 64GB of ram the swap isn't being touched with updates...

Do I even need swap with a system that's full ZFS for all volumes? I mean there is NO WAY I should be running out of RAM so I don't know when swap would even get touched.

So then better bet would be throw in another spinner and put a swap partition on it I suppose?

I recently had to replace one of my nodes and the new server was setup from scratch. It's an 8 core/16 thread Intel with 64GB ram. I noticed today when trying to update it that it was very sluggish and the stats in the gui manager weren't keeping up. After forcing the two very low resource...

And bingo!! That did it. I stopped the migration, moved the disk to local/zfs, cold migrated it to the new server and it starts up.

And I knew this sounded familiar... I had this same problem a couple years back. Different reason this time but I'm pulling on that thread now to see if it'll do: https://forum.proxmox.com/threads/error-while-cold-migrating-after-upgrade.74143/#post-330951

qm start 108 results in: VM is locked (migrate) I feel like this has happened before. Looking at your link now.

Ideas?