I have run proxmox on Mac minis 4 cores/8 threads and originally 8gm ram. I upgraded ram heavily and stuffed in an ssd to run as a lvm cache to the 5400 1t drive and it performed well as a home lab server for years. All the rest is use case recommended for a server. Possibly in production. On Sat, Oct 8, 2022, 9:08 PM wrote: > That sounds scary. > > Ok, so I am coming away with a vCPU is = to a thread. RAM is fixed. I > read Proxmox requires 2GB of RAM and I was unable to determine the > number of cores for Proxmox. > > Proxmox says you will need Intel EMT64 or AMD64 with Intel VT/AMD-V CPU > flag. > > They suggest SSD disks, and redundant Gbit NICs. I assume along these > lines you would want redundant power supplies. > > Another Question : > > I have a Cox business connection that allows me to run servers and to be > allocated more than 1 static IP. > > I can see me configuring at least 4 virtual machines for LAMP - PHP > testing and development, and a VM for a real website. Not all of these > VMs would be active at once. > > Since I would be running this out of my home office, to be safe, I would > need enough RAM to allocate 4GB of RAM of reach _active_ VM and 2 vCPUs, > and to be safe maybe 4GB of ram and 2 cores for Proxmox. > > For 4 simultaneously active VMs I would need 8vCPUs (8 threads) and 4GB > of RAM each or 16GB of RAM. Add to that 2 Cores/4 threads and 4GB of > RAM for Proxmox and I would need 12 threads or 6 cores and 20GB of RAM. > > I'm thinking a 500GB SSD would be enough and if I like I could add a > redundant NIC and a redundant power supply. > > Pretty much a consumer grade box? > > Your thoughts? > > > > > > > > > > On 2022-10-07 18:23, Stephen Partington via PLUG-discuss wrote: > > Hit reply too soon. You can share or overprovision ram but you have to > > enable some features and load a couple of os level drivers to make it > > work. > > > > On Fri, Oct 7, 2022, 9:22 PM Stephen Partington > > wrote: > > > >> And you can share ram across containers not vms. > >> > >> On Fri, Oct 7, 2022, 9:21 PM Stephen Partington > >> wrote: > >> > >> i love proxmox.have used it fir years > >> > >> The vcou is socket x cores x2 if you have hyperv/smt > >> > >> So a 4 core ht cpu would be 8vcpu. > >> > >> On Fri, Oct 7, 2022, 7:35 PM Keith Smith via PLUG-discuss > >> wrote: > >> > >> Hi, > >> > >> I just watched a video that covered the Proxmox Hypervisor. Seems > >> simple enough. I've used Oracle's VirtualBox for years. > >> > >> So I did some research on what a vCPU is. I was suppressed. The > >> math > >> given was (Threads x Cores) x Physical CPU = Number vCPU. > >> > >> I have an old laptop that has 1 socket, 2 cores, four threads, and > >> 4GB > >> of RAM. > >> > >> Given the math (4 x 2) x 1 = 8 vCPUS. Is this correct? > >> > >> From my reading it appears that RAM is not shared, so my bottleneck > >> is > >> RAM not cores or threads. > >> > >> I am a PHP developer and a local vps would need 2GB of RAM at a > >> minimum. > >> I have found a LAMP VPS will crash if allocated less than 2GB of > >> RAM, > >> and will run will on 1 vCPU. > >> > >> The good news is I really only need one VPS to be active at any > >> given > >> time. > >> > >> If I wanted to build a box that could run more than one VPS at a > >> time, > >> lets say 4, and I wanted to allocate 2 vCPUs and 4GB of RAM I would > >> need > >> 4 threads x 2 cores to run the 4 VPS configured with 2 vCPUs each. > >> > >> What about RAM. Looks like I would need a minimum of 16GB of ram. > >> > >> How much resources does the Hypervisor need, in this case Proxmox? > >> > >> Thanks!! > >> Keith > >> --------------------------------------------------- > >> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org > >> To subscribe, unsubscribe, or to change your mail settings: > >> https://lists.phxlinux.org/mailman/listinfo/plug-discuss > > --------------------------------------------------- > > PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org > > To subscribe, unsubscribe, or to change your mail settings: > > https://lists.phxlinux.org/mailman/listinfo/plug-discuss >