<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with existing-hosts]]></title><description><![CDATA[A list of topics that have been tagged with existing-hosts]]></description><link>https://xcp-ng.org/forum/tags/existing-hosts</link><generator>RSS for Node</generator><lastBuildDate>Tue, 14 Apr 2026 05:31:36 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/tags/existing-hosts.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 11 Jan 2024 18:44:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Patching and trying to Pool Hosts after they&#x27;ve been in production]]></title><description><![CDATA[@Danp said in Patching and trying to Pool Hosts after they've been in production:

Warm migration should work in this case because the VM is halted then restarted as part of the process. See here for more details.

Sweet, I'll setup something small on the old host for testing and use the Warm Migration process.
]]></description><link>https://xcp-ng.org/forum/topic/8198/patching-and-trying-to-pool-hosts-after-they-ve-been-in-production</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/8198/patching-and-trying-to-pool-hosts-after-they-ve-been-in-production</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Thu, 11 Jan 2024 18:44:24 GMT</pubDate></item></channel></rss>