HTML Website BuilderCPU: AMD Threadripper 1950X [16C/32T]
RAM: 64GB DDR4 ~2133/2400Mhz [8x8GB]
SSD: OS, 256GB + VMs, 500GB
HDD: Storage, 8TB (x4) → 16TB (x2) pool, mirrored
GPU: AMD RX470 8GB VRAM
GPU2: Nvidia GTX 1030 2GB
PSU: 1200W, 80+ Platinum
Dedicated MiniPCs for each Game Server
Minimum 8C/16T, Minimum 16GB RAM (expandable)
AMD iGPU, Low TDP
SSD: OS, 500GB (Split Partitioned, 128GB + Remaining)
Backup Drive: 128GB+ Flash Drive (Game Data)
Existing VM Host will be converted to Testing and Data Storage, Network Sharing within cluster.
I've noticed that the VM Host is having an issue properly restarting at 4AM. There are times when it fails to boot into Windows. This is observed to be rare, and only once in a while.
Currently, the exact reason is unknown as of this time, but it is speculated to be caused by a bad power connector, which will be replaced in due time.
As the VM Host can be manually rebooted and loads into the Windows environment successfuly after said reboot, this is not a severe issue, but just an annoying one.
It will be fixed, but please be patient, as this is a "free" service.
VM, or Virtual Machine, is basically a computer. Now, when we think of a 'computer', we normally think of the physical thing, which is the hardware that you buy at a store, or order parts online and assemble yourself.
However, we rarely ever think of the software. The software, or OS (Operating System), is really what drives the hardware and makes things work the way that it does when we interact with a 'computer'. You cannot have one without the other.
So then, what makes a Virtual Machine or VM any different?
The VM is basically a software computer inside another whole computer. With a special note that any resources that are available to the computer that it is running inside of, it can use too. Whatever CPU power or RAM I have, I can tell the main computer to share some of it with the VM computer that is inside of it.
So you can see above that my "host" computer is just a really powerful PC. It wasn't really intended for gaming, but you can probably view it that way if it helps you to visualize what is happening.
The Host has a lot of CPU cores and threads (think lines of thought), a lot of RAM (short term memory), and graphics power (the ability to create images or video). Let's say that this machine has a copy of the Windows OS on it. When I turn it on, it would open Windows, just like any other computer that you find at home or work.
But let's say inside of that computer, there is an imaginary container that runs yet another copy of Windows. And I can have as many containers as I want, running any kind of OS inside of it, that is completely separate from the one that I just logged into. And each one uses threads, RAM, and GPU power that I dedicate to them, based on its indvidual needs or intended work loads.
Wait what?
This is where it can get a bit confusing, but imagine this: You have a drawer for your clothes. It's a bit messy, so you go ahead and got yourself a nice drawer organizer (Google it, it will change your life). Inside of the big drawer, you now have separated spaces for different clothing items. You can use one space for socks, and another for underwear. You can use one for your shirts, and another for your pants. You are free to use the spaces as you please for any purpose.
The clothing drawer that was once one big space, is now multiple spaces, divided up amongst the containers you created for different items.
And that's pretty much what you're getting with VMs. You want to run a copy of Linux inside of a VM Host that is running Windows? Sure, that's neat. Or what if it was the other way around, and you wanted to try Windows as someone who is mainly a Linux user? Yep. Or what if you want to be like me, and run Windows inside of Windows, except now you got infinite Windows inside Windows? So many Windows that you can't see what's happening inside.
Windows 10? Pffffttt. Such a lowly 2 digit number.
Windows INFINITE.
I spent a lot of time thinking about it, actually.
I had a lot of internalized debates with myself about going with a Xeon or Epyc server, which could technically open up more paths to upgrades, but it ultimately came down to available software support and resale value.
1. I read a lot of reviews about individuals who have tried to do what I have, and sometimes it's not fun. As an individual, you can only get so much support. As individuals, we are not companies or corporations which get prioritized support through a vendor. Sometimes the firmware you get is buggy, or you have to follow a predetermined set of guidelines in order for your setup to be valid or eligible for support. That can be frustrating.
As an IT Professional working at a company, I can totally get behind it, but as an individual doing this as a side-hobby, no thanks.
2. My previous server ran with a Ryzen 7 1700X, which could be resold as gaming hardware, or gifted to someone who could use it in their everyday computer.
You can't do that as easily with server-specific hardware.
Granted, Threadripper might not be as easy to repurpose or sell, but it's heck of a lot easier than doing that with an Epyc CPU that runs on server-specific motherboard equipment, and is only rated to run with server-certified RAM.
My friends and family wouldn't be able to enjoy my handmedowns with that, now would they?
HTML Website Builder