Recent content by Chris Olive

That’s the thing — this is all NFS v4 and I could not get the mount to work wo opening 892 for the GUI. Mounting to the PVE node at the command line worked fine without 892 open.

Recently upgraded all PVE v8 nodes to PVE v9 nodes. I have one node on an isolated network with holes punched through the firewall to allow NFS mounting on my LAN that worked at one time. Suddenly not working. showmount on the command line hangs. Opened up port 892 (in addition to 111 and 2049...

I’m in the middle of testing and converting some older servers to new servers. Due to various issues and testing I’ve reimaged and re-upgraded a fair amount in the last several days. So I’m in this section a lot. It’s ridiculous. Has nothing to do with a short fuse. It’s just poor design. Zero...

Is there really some overwhelming need, especially when I'm mucking around in Updates and Repositories to pop the No valid subscription "You do not have a valid subscription for this server." pop up EVERY OTHER CLICK?!?! ** I KNOW I DON'T HAVE A VALID SUBSCRIPTION. ** Upon login, "okay," I...

Confirmed this did the trick (as you already knew). Not sure why I read your original directive as to perform on the deleted cluster member.

<Salutes> That's all I need to confirm. Will do.

Ironically, the section above the one you reference speaks to removing a node from a cluster. It states: Take down the node (shutdown) and never bring it back up again. Then issue a pvecm delnode <oldnode> command. That's essentially what happened to me. I took down the node without doing...

Well, this looks like a guide for executing on the node I took down without deleting the node from the cluster while it was still up and running. If it's easier to bring back "construct3" (as per my output in the OP), I can do that as a one-time thing to resolve on this. I'll look into bringing...

Woke up this AM and my PVE Web GUI was down. Wouldn't start with a "can't update certs" issue. "No quorum" Okay, well, I just established a cluster yesterday and then brought a cluster member down -- and it's probably not coming back. I didn't see any way to delete the cluster member, so I just...

But now networking is a pain. I'm totally running into this now: https://forum.proxmox.com/threads/test-environment-virtualized-proxmox-on-esxi-network-problem.37612/ Trying to work through it, but none of this is coming easy.

It would probably run like a dog, going the other way around (nesting ESXi inside of PVE instead of the other way around). I have no idea why in English, the idiom "runs like a dog" is what it is. Dog are actually pretty fast. :cool:

I totally should have gone this way (tested PVE under ESXi). But I was also pressed for time and PVE was still a magnificent discovery. I've learned so much in just a few weeks and there are things I'd like to change where I'm basically entrenched and can't go back, not without a lot of work I...

Holy carp, I never really even thought of that? How does PVE perform when inside a VM itself? I'd probably use it just for containers, yes... Seems simple. I conceive of PVE on bare metal, but I don't see why this wouldn't work? It irks me I have to keep this ESXi server around.

Okay, had a look and you are exactly correct. The .conf files at /etc/pve/nodes/<node>/lxc/<vmid>.conf get handled by the management code at the URL above. I was pleased to see Perl when I visited that link as I still do a lot of coding in Perl. But I can see this is exactly what someone did is...

Might be enough for me. Ima check it out. Totally. Totally agree. Again, it's amazing what I was able to accomplish with LXD for LXC and it's all very simple once set up except the actual container launch settings. I can issue an lxc launch blah/blah/blah then yum -y install mariadb (CentOS 8)...