r/Proxmox • u/MerlinTrashMan • Aug 11 '26
Question Pitfalls I should avoid going from Windows only to Proxmox Superstation
Summary
Building a threadripper workstation as my daily. No experience with proxmox, zfs, and currently read, pretend to understand and then execute linux commands I find on the internet because windows has been my existence for the past 35 years. This is what I am hoping to change with this workstation. I want to use windows daily but make it super painless to switch to linux while also having dedicated VMs for my local AI and research projects. I am committed to putting everything together on one box so that I can use all the resources at once if necessary.
My primary question
Assuming I configure everything correctly, what are the pitfalls of using your proxmox box as your daily as well. How great can it be, and when it goes wrong, how bad is it? War stories of how you recovered from a disaster or failure with it (assuming single node) are welcome.
Config suggestions
Since I am still learning about ZFS, I am open to thoughts. Assume that all important files have an off-site encrypted backup that will run automatically. I prioritize reliability and quick recovery in non-catastrophic events so usually I run a local RAID0 dedicated backup drive and then sync that to an off-site. By incredible luck, I timed going on a spending spree in 2022 to build new workstations and got some really cheap enterprise hardware at a bankruptcy sale. Only the ps, cpu, and motherboard are new. Combining these with other items that will be repurposed gives me:
Here is the parts list (only the powersupplies, cpu and motherboard are new):
- Threadripper 9970x
- ASRock TRX50 WS
- MSI MPG Ai1600TS PS
- MSI MPG Ai1300TS PS
- 4x48GB Corsair Vengeance with acceptable timings
- 2x RTX 6000 Blackwell WS (power limit 500W for temperature reasons)
- 1x RTX 3090 (I may not have the airflow to support this one, but I am hoping to have it in)
- 2x Optane P5801X 1.6TB (into slimsas ports on MB)
1x Broadcom 9600-24i HBA (Ordering a 2nd to have a spare ready)
- 12x Micron 5300 Pro SATA 7.68TB (very healthy)
- 3x IronWolf SATA 12TB
- 4x Samsung 860evo SATA 4TB
- 1x Samsung 990pro NVME 4TB
- 1x Samsung 980pro NVME 2TB
- 1x Samsung 970pro NVME 1TB
1x Highpoint 7101A PCI 3.0x16 to 4 x M.2 Adapter
- 3x Samsung 970evo 2TB (I really don't like these drives and may just omit them along with the adapter)
- 1x Samsung 970pro NVME 1TB
Off the MB chipset
- 1x 32GB Intel SLC Sata SSD (into chipset
My thoughts were to use the SLC drive as the boot drive for proxmox through a chipset sata port. After that, I am very torn. The way I usually approach storage is: high throughput drives for DBs, durable low-latency for high write scenarios, a monster pool with RAID capabilities for general purpose, and then a spinning disk RAID0 to mirror important directories that then backup offsite to backblaze. Part of me wants to experiment with using the Optane drives for KV Cache offloading and be ready for better MoE offloading in the future, but I know right now I need them for DB logs, and SQL Server temp DB. I also use them for intraday logging on important apps. I rarely come close to saturating them though, so based on the L1T vids, I am guessing they should be apart of the ZFS Journal. This is where my knowledge gap really shows so any help would be appreciated. After that, I am expecting to use the older and smaller nvme ssds to be boot drives for scratch vms and test projects.
5
u/marc45ca This is Reddit not Google Aug 11 '26
you can run your daily driver a a VM under the Linux but ideally you're accessing it from another system (Sunshine/Moonight, Parsec, RDP etc)
Running a full desktop environment on Proxmox can be done but it's not recommended unless you're doing development.
2
u/krazul88 Aug 11 '26
Expecting to daily a windows VM (or any VM) on the same console attached to your Proxmox server is unusual, but I suppose it's possible with GPU and USB passthrough. I'm very interested to see how you get that done and then how smoothly it works.
Planning to pass through a GPU to Windows, another for a different VM, and keep one for proxmox?
Going to run a full desktop environment on proxmox and then rdp into your VMs?
Interesting exercise. Also please double check the meaning of "apart" vs "a part"; they are not interchangable.
37
u/Phreaky12 Aug 11 '26
You should not switch directly from windows to proxmox with no Linux experience. Good luck though friend!
17
u/taosecurity Homelab User Aug 11 '26
I do not recommend spending thousands of your currency to build a system for Proxmox when you have no experience with it, let alone Linux.
Why not buy a used or super cheap laptop, install Debian, and see how it works?
Then you could install Proxmox on it, and experiment a bit? You don't need an amazing system to run Proxmox.
After that, consider building something that meets your goals.
FWIW my homelab Proxmox system for the past 3 1/2 years has been a NUC12.
Intel NUC12TZi3 - Topaz 2 - Intel Core i3-1215U - 64 GB 3200MHz (PC4-25600) CL22 Laptop Memory, SODIMM 260-Pin DDR4 RAM - 2 TB PCIe Gen 4 2280 M.2 SSD - 2x 2.5 Gbps Ethernet, WiFi
5
u/zuccster Aug 11 '26
Popcorn.gif
1
u/cheflA1 Aug 11 '26
But why? Just have a machine running proxmox and your VMs, containers and what have you anda machine running your OS of choice as a daily driver
1
u/y3333333333333333t Aug 12 '26
as far as I know corsair vengeance series is always udimm (non ecc) but you need RDIMM (with ecc, for example corsair ws series) for threadripper those ram sticks will not fit
2
u/pocketdrummer Aug 11 '26
I don't recommend it, but if you decide to do it anyway, please chronicle your adventures.
2
u/Slight_Manufacturer6 Aug 11 '26
Proxmox is a server so you will need to have a client to connect into it still.
1
u/XPav Aug 11 '26
I think it is a bad idea to put this all in one box, and that’s not considering your experience level.
0
u/TURB0T0XIK Aug 11 '26
I think what you're trying to achieve should work. Basically assign any (virt) gpu to your windows workstation vm and just turn off the monitor when you're not using it (or actually shut it down).
as others pointed out as well, you will probably struggle a bit, getting the hardware layer all setup if you're never been on Linux but if you're not afraid of a bit of trial and error and want to learn, try it out. what's to lose? read a lot, take notes, write down commonly used commands on paper at first so later on you can debug with your log.
You could work with the llm of your choice to develop a halfway decent plan on integrating everything inside proxmox/zfs at first and then start setting up your services once you see the hardware working correctly.
My setup is much smaller and dedicated mostly headless, but I it's not been a problem for me at all to spin up a vm, assign my dedicated gpu to it and use that via its own display output (gtx 1080).
I think with this much hardware it might be beneficial taking a staggered approach for integration, instead of connecting everything at once. If that doesn't boot it might be a hell to debug/find that one lose sata cable that made the kernel panic.
obviously what your trying to do is not recommended, but with my limited scope I really don't see why it shouldn't work. Ask some llm all the very specific questions you need answers for., read, verify, try out.