<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vdi on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/vdi/</link>
    <description>Recent content in Vdi on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Wed, 02 Sep 2026 14:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/vdi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Zero Trust VDI Without the Cloud Bill — Proxmox, Intel Arc Pro and Cloudflare Access</title>
      <link>https://blogs.damiendye.uk/en/networking/zero-trust-vdi-cloudflare-access/</link>
      <pubDate>Wed, 02 Sep 2026 14:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/networking/zero-trust-vdi-cloudflare-access/</guid>
      <description>Part one: the architecture and the cost argument for replacing Azure Virtual Desktop with Proxmox, Intel Arc Pro SR-IOV and Cloudflare Access. On-prem OAuth for identity, browser-rendered RDP, a firewalled LXC tunnel on its own VLAN, KSM for memory density, and profiles on Ceph. The next post builds it.</description>
    </item>
    <item>
      <title>Licence-Free Windows VDI on Proxmox with an Intel Arc Pro B50 — and the Firmware Limit That Stopped It</title>
      <link>https://blogs.damiendye.uk/en/proxmox/licence-free-vdi-intel-arc-pro-sriov/</link>
      <pubDate>Fri, 07 Aug 2026 17:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/licence-free-vdi-intel-arc-pro-sriov/</guid>
      <description>Intel&amp;#39;s Arc Pro cards do SR-IOV natively, with no vGPU licence to buy — which makes a licence-free Windows VDI on Proxmox genuinely possible. The whole build on a B50, the Windows-first bootstrap problem, why the firmware caps it at two virtual functions, and how many each card in the B-series gives you.</description>
    </item>
  </channel>
</rss>
