<?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[Understanding Auto Power On | Auto Start]]></title><description><![CDATA[<p dir="auto">Hey guys,</p>
<p dir="auto">Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing.<br />
<a href="https://docs.xcp-ng.org/guides/autostart-vm/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.xcp-ng.org/guides/autostart-vm/</a></p>
<p dir="auto">From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level.</p>
<p dir="auto">Just looking for some clarification.</p>
<p dir="auto">In order for auto power on to function, we need to enable it on the pool level, and then per VM correct?</p>
<p dir="auto">If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct?</p>
<p dir="auto">What is actually triggering the power on?<br />
Is it XOA or the host itself?<br />
I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on.</p>
<p dir="auto">What determines the start order for auto power on when you have multiple VMs on a host?</p>
<p dir="auto">Thank you!!</p>
]]></description><link>https://xcp-ng.org/forum/topic/12149/understanding-auto-power-on-auto-start</link><generator>RSS for Node</generator><lastBuildDate>Tue, 05 May 2026 17:15:00 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/12149.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 05 May 2026 15:03:04 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Understanding Auto Power On | Auto Start on Tue, 05 May 2026 16:23:12 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/tsukraw" aria-label="Profile: tsukraw">@<bdi>tsukraw</bdi></a> <a href="/forum/post/105054">said</a>:</p>
<p dir="auto">Hey guys,</p>
<p dir="auto">Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing.<br />
<a href="https://docs.xcp-ng.org/guides/autostart-vm/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.xcp-ng.org/guides/autostart-vm/</a></p>
<p dir="auto">From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level.</p>
<p dir="auto">Just looking for some clarification.</p>
<p dir="auto">In order for auto power on to function, we need to enable it on the pool level, and then per VM correct?</p>
<p dir="auto">If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct?</p>
<p dir="auto">What is actually triggering the power on?<br />
Is it XOA or the host itself?<br />
I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on.</p>
<p dir="auto">What determines the start order for auto power on when you have multiple VMs on a host?</p>
<p dir="auto">Thank you!!</p>
</blockquote>
<p dir="auto">Yes, it needs to be enabled at pool level and at VM level. I tried once at only enabling at the VM level and it didn’t auto power on, as it wasn’t enabled at the pool level, it started auto powering on once it’s enabled at both levels.</p>
<p dir="auto">It’s configuring a XAPI value as this occurs at the Xen level (virtualisation server). Xen Orchestra is just making this value visible with a nice UI interface toggle.</p>
]]></description><link>https://xcp-ng.org/forum/post/105056</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/105056</guid><dc:creator><![CDATA[john.c]]></dc:creator><pubDate>Tue, 05 May 2026 16:23:12 GMT</pubDate></item></channel></rss>