<feed xmlns="http://www.w3.org/2005/Atom"> <id>/</id><title>9tec</title><subtitle>Exploring the backend of modern infrastructure — from VMware and Linux to automation, virtualization, and real-world homelab setups.</subtitle> <updated>2026-09-24T23:30:47-03:00</updated> <author> <name>Gustavo Novello</name> <uri>/</uri> </author><link rel="self" type="application/atom+xml" href="/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Gustavo Novello </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>VRMS Connection refused: tracking down an hms.service file descriptor leak</title><link href="/posts/vrms-hms-connection-refused/" rel="alternate" type="text/html" title="VRMS Connection refused: tracking down an hms.service file descriptor leak" /><published>2026-04-20T16:00:00-03:00</published> <updated>2026-04-20T16:00:00-03:00</updated> <id>/posts/vrms-hms-connection-refused/</id> <content type="text/html" src="/posts/vrms-hms-connection-refused/" /> <author> <name>Gustavo Novello</name> </author> <category term="VMware" /> <category term="Troubleshooting" /> <summary>Intermittent VRMS API failures traced through systemd watchdog timeouts, "Too many open files" errors, and a single XML parameter — schedule-health-checks — that was slowly exhausting file descriptors until hms crashed.</summary> </entry> <entry><title>PVSCSI vs LSI on vSphere: does the controller choice actually matter?</title><link href="/posts/pvscsi-vs-lsi-sioc/" rel="alternate" type="text/html" title="PVSCSI vs LSI on vSphere: does the controller choice actually matter?" /><published>2026-04-02T18:00:00-03:00</published> <updated>2026-04-02T18:00:00-03:00</updated> <id>/posts/pvscsi-vs-lsi-sioc/</id> <content type="text/html" src="/posts/pvscsi-vs-lsi-sioc/" /> <author> <name>Gustavo Novello</name> </author> <category term="Storage" /> <category term="VMware" /> <summary>Five VMs, two controllers, SIOC on and off. The numbers show that what you think is a controller problem is usually a storage fairness problem.</summary> </entry> <entry><title>fio_benchmark: A wrapper to stop writing the same fio commands over and over</title><link href="/posts/fio_benchmark/" rel="alternate" type="text/html" title="fio_benchmark: A wrapper to stop writing the same fio commands over and over" /><published>2026-03-20T10:00:00-03:00</published> <updated>2026-03-20T10:00:00-03:00</updated> <id>/posts/fio_benchmark/</id> <content type="text/html" src="/posts/fio_benchmark/" /> <author> <name>Gustavo Novello</name> </author> <category term="Storage" /> <category term="Troubleshooting" /> <summary>A Bash script that compiles the standard fio test profiles sysadmins and storage engineers run manually every time into a single repeatable tool — with structured output and optional sweeps for finding bottlenecks.</summary> </entry> <entry><title>AMD APU Passthrough to a Proxmox LXC for Local AI</title><link href="/posts/AMD_APU_to_LXC/" rel="alternate" type="text/html" title="AMD APU Passthrough to a Proxmox LXC for Local AI" /><published>2026-03-06T14:00:00-03:00</published> <updated>2026-03-06T23:43:16-03:00</updated> <id>/posts/AMD_APU_to_LXC/</id> <content type="text/html" src="/posts/AMD_APU_to_LXC/" /> <author> <name>Gustavo Novello</name> </author> <category term="Homelab" /> <category term="Proxmox" /> <category term="AI" /> <summary>Step-by-step guide to successfully passing your AMD APU through to an LXC container and deploying a hardware-accelerated AI stack with Ollama and Open WebUI.</summary> </entry> <entry><title>Failed tasks in SDDC 5.2</title><link href="/posts/failed-tasks-in-sddc-5-2/" rel="alternate" type="text/html" title="Failed tasks in SDDC 5.2" /><published>2025-08-17T21:00:00-03:00</published> <updated>2025-08-17T21:00:00-03:00</updated> <id>/posts/failed-tasks-in-sddc-5-2/</id> <content type="text/html" src="/posts/failed-tasks-in-sddc-5-2/" /> <author> <name>Gustavo Novello</name> </author> <category term="VMware" /> <category term="SDDC" /> <summary>Notes on failed tasks in SDDC 5.2</summary> </entry> </feed>
