LLM Development System (GPUs Accounted for)

A user testing a multi-GPU LLM development machine reported that the system held up well under sustained load running the Qwen3.8 27B model, despite the machine shipping from 45 Drives with the wrong CPU and only 8 cores initially. The user cited the model's "annoying habit of insane reasoning blocks" and a migration to vLLM as sources of extensive troubleshooting, and is now segmenting services including MCP, Gitea, Turnstone, and vLLM workloads across separate VMs, with plans to integrate a Proxmox MCP server.

I have been testing this machines fairly intensely over the last few weeks. With the release of Qwen3.8 27B, I have been kicking a lot of heat out of this box and it has held up well. The model has an annoying habit of insane reasoning blocks. Between that and my migration to vLLM, I have spend a lot of time troubleshooting. 45 Drives shipped it with the wrong CPU, so I was just working with 8 cores to begin with. Now I have something that gives me more room to stretch. I am still playing around with the right way to segment my different services like MCP, Gitea, Turnstone, the vLLM workloads etc. onto different VMs. Once I smooth out the rough edges on the model and my turnstone instance, I’ll move to integrating a Proxmox MCP server. I am a long way from an infrastructure aid, but I am learning a lot as I go