Proxmox Host: Hardware Overview

This article outlines the hardware setup of a Proxmox VE host used for self-hosting and virtualization projects. All system identifiers and sensitive data have been sanitized for security.

---

🧠 CPU

Field	Value
Model	Intel Xeon E5-1650 v3 @ 3.50GHz
Architecture	x86_64
Cores / Threads	6 cores / 12 threads
Virtualization	VT-x supported
Hyper-Threading	Enabled
Max Frequency	3.5 GHz
Min Frequency	1.2 GHz
Caches	192K L1, 1.5M L2, 15M L3

This CPU supports hardware virtualization and modern instruction sets like AVX, AES, and FMA. Security mitigations for vulnerabilities like Spectre/Meltdown are active.

---

💾 RAM

Slot	Size	Type	Speed	Manufacturer	Part Number (Redacted)
DIMM1	16 GB	DDR4	2133 MT/s	Hynix	Redacted
DIMM2	16 GB	DDR4	2400 MT/s	Micron	Redacted
DIMM3	16 GB	DDR4	2133 MT/s	Hynix	Redacted
DIMM4	16 GB	DDR4	2400 MT/s	Micron	Redacted
DIMM6	16 GB	DDR4	2400 MT/s	Micron	Redacted
DIMM8	16 GB	DDR4	2400 MT/s	Micron	Redacted

Total Installed: 96 GB
Empty Slots: 2
Type: ECC Registered DDR4 (RDIMM)

---

💽 Storage Devices

Device	Size	Filesystem	Mountpoint	Notes
Disk A	300 GB	ext4	/mnt/iso_storage	Used for ISO images
Disk B	1.5 TB	ext4	/mnt/vm_storage	Main storage for VMs
SSD	111 GB	ext4 (LVM)	/ and swap	Proxmox system disk
USB A	1.8 TB	ntfs	/mnt/shared_storage	External storage
USB B	465 GB	ntfs	/mnt/backups	Backup disk

⚠️ Sensitive UUIDs and volume labels have been truncated or redacted.

Use nofail or x-systemd.automount in /etc/fstab to avoid boot issues with removable drives.

---

🎮 GPU

Model	NVIDIA GeForce GTX 980
Chipset	GM204
Driver	nouveau (open-source)

Notes

• The system is using the open-source nouveau driver.
• Suitable for VM passthrough or compute acceleration if desired.
• Proprietary NVIDIA drivers may be required for CUDA or VFIO passthrough setups.

---

✅ Summary

This Proxmox host is well-equipped for advanced homelab and self-hosting use, offering:

• ECC RAM for stability
• GPU ready for passthrough
• Sufficient SSD+HDD mix
• Clear upgrade potential

This profile serves as a reference baseline before installing additional services or setting up VMs and containers.