Computing/NAS/Software - Revision history

Cricalix: Remove proxmox, use Incus

2026-04-02T17:12:23Z

Remove proxmox, use Incus

@@ Line 1: / Line 1: @@
-=== Proxmox ===
+== Hardware ==
-Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.
+Core is a https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ ([https://web.archive.org/web/20250624104920/https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ archive] link); twin 2.5G network ports, a lot of SATA ports, and lots of compromises.
-<code>iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006</code>
+== Network ==
-Then use iptables-persistent to make that apply every time.
+=== Host ===
-=== Unraid VM ===
+[ethernet]
-Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM
-* q35 machine
+[ethernet]
-SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array. Integrated graphics also isolated for passthrough to the Media Host.
+[bridge-port]
-=== Media host VM ===
+</syntaxhighlight>
-Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381
+=== Incus Bridge ===
-Revert to 440 with PCI passthrough. Had to reinstall for some reason, and switch to SeaBIOS.
+== VMs and Containers ==
-==== Media host Sonarr ====
+=== Unraid VM ===
-<code>podman run --name=sonarr --detach -e PUID=$(id -u media) -e PGUID=$(id -g media) -e TZ=Europe/Dublin -p 8989:8989 -v /services/sonarr:/config -v /vault/video/TV\ Shows:/media --restart always lscr.io/linuxserver/sonarr:latest</code>
+Unraid needs a USB stick to boot from, as it uses the serial number of the stick as a license key. Ended up with plopkexec in the boot path for the qemu-backed VM (pc-q35)<syntaxhighlight lang="yaml">
-Needs host NFS mounted. Avoids trying to do privileged LXCs on Proxmox and working out how to maintain a copy of the configs outside of the container.
+=== HomeAssistant ===

Cricalix at 21:15, 22 December 2024

2024-12-22T21:15:17Z

← Older revision		Revision as of 21:15, 22 December 2024
Line 1:		Line 1:
	Proxmox		=== Proxmox ===

	Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.		Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.

	`iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006`		<code>iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006</code>

	Then use iptables-persistent to make that apply every time.		Then use iptables-persistent to make that apply every time.

	Unraid VM		=== Unraid VM ===

	Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM		Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM

Line 18:		Line 16:
	* PCI passthrough - SATA controller		* PCI passthrough - SATA controller

	SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array.		SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array. Integrated graphics also isolated for passthrough to the Media Host.

	Media ~~host VM~~

			=== Media host VM ===
	Tried q35 with PCI passthrough of the IGP		Tried q35 with PCI passthrough of the IGP

	Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381		Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381

			Revert to 440 with PCI passthrough. Had to reinstall for some reason, and switch to SeaBIOS.

			==== Media host Sonarr ====
			<code>podman run --name=sonarr --detach -e PUID=$(id -u media) -e PGUID=$(id -g media) -e TZ=Europe/Dublin -p 8989:8989 -v /services/sonarr:/config -v /vault/video/TV\ Shows:/media --restart always lscr.io/linuxserver/sonarr:latest</code>

			Needs host NFS mounted. Avoids trying to do privileged LXCs on Proxmox and working out how to maintain a copy of the configs outside of the container.

Cricalix at 12:20, 22 December 2024

2024-12-22T12:20:25Z

← Older revision		Revision as of 12:20, 22 December 2024
Line 19:		Line 19:

	SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array.		SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array.

			Media host VM

			Tried q35 with PCI passthrough of the IGP

			Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381

Cricalix at 12:17, 22 December 2024

2024-12-22T12:17:34Z

← Older revision		Revision as of 12:17, 22 December 2024
Line 1:		Line 1:
	Proxmox		Proxmox

			Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.

			`iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006`

			Then use iptables-persistent to make that apply every time.

	Unraid VM		Unraid VM

Cricalix: Created page with "Proxmox Unraid VM Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM * q35 machine * UEFI/OVMF * '''No''' EFI disk * Some GB of RAM * Host CPU cores, 2 of them (the VM is tied to the USB stick anyway, so may as well tie it to the host cores) * PCI passthrough - SATA controller SATA controller was assigned to a resource mapping at the Datacenter..."

2024-12-21T15:28:58Z

Created page with "Proxmox Unraid VM Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM * q35 machine * UEFI/OVMF * '''No''' EFI disk * Some GB of RAM * Host CPU cores, 2 of them (the VM is tied to the USB stick anyway, so may as well tie it to the host cores) * PCI passthrough - SATA controller SATA controller was assigned to a resource mapping at the Datacenter..."

New page

Proxmox

Unraid VM

Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM

* q35 machine
* UEFI/OVMF
* '''No''' EFI disk
* Some GB of RAM
* Host CPU cores, 2 of them (the VM is tied to the USB stick anyway, so may as well tie it to the host cores)
* PCI passthrough - SATA controller

SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array.