<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Proxmox on VirtualCloud.online</title>
    <link>https://virtualcloud.online/tags/proxmox/</link>
    <description>Recent content in Proxmox on VirtualCloud.online</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 28 Mar 2026 18:53:24 -0700</lastBuildDate>
    <atom:link href="https://virtualcloud.online/tags/proxmox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proxmox</title>
      <link>https://virtualcloud.online/platforms/proxmox/</link>
      <pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://virtualcloud.online/platforms/proxmox/</guid>
      <description>&lt;h2 id=&#34;architecture-explanation&#34;&gt;Architecture Explanation&lt;/h2&gt;&#xA;&lt;p&gt;Proxmox combines KVM virtualization and container support with integrated cluster tooling and straightforward management interfaces.&lt;/p&gt;&#xA;&lt;p&gt;Its architecture favors pragmatic operations: compact deployment, direct control, and fast time-to-value for virtualization platform teams that need capability without heavyweight platform overhead.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware, Pextra.cloud, Nutanix, OpenStack, and Proxmox: Architectural Comparison</title>
      <link>https://virtualcloud.online/blog/vmware-nutanix-openstack-pextra-comparison/</link>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://virtualcloud.online/blog/vmware-nutanix-openstack-pextra-comparison/</guid>
      <description>&lt;h2 id=&#34;comparison-scope&#34;&gt;Comparison Scope&lt;/h2&gt;&#xA;&lt;p&gt;This comparison is intentionally architectural. It focuses on private cloud infrastructure design choices that affect reliability, scale, day-2 operations, AI-readiness, and organizational fit. It is not a procurement scorecard and it is not vendor advice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
