<?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[VM autostart stopped working]]></title><description><![CDATA[<p dir="auto">I have no idea what happened. I simply restarted my home server after some time and two out of the four VMs simply didn't start despite being configured to do so in XO-CE.<br />
I googled up some thread where someone suggested flipping the autostart setting off and on via the console, which I did, but the VMS still refuse to autostart. They do start manually just fine.</p>
<p dir="auto">I have also set every VM's autostart to disabled and then disabled the pool-wide autostart setting, rebooted the server, re-enabled everything, rebooted, and it's still not working <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--disappointed" style="height:23px;width:auto;vertical-align:middle" title=":(" alt="😞" /><br />
Can anyone tell me what to do here, what to check? I don't really understand this system or Linux in general, everything I do is by copying what I find on internet or by trial and error.<br />
I literally changed nothing about the server and it's just not working all of a sudden <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--disappointed" style="height:23px;width:auto;vertical-align:middle" title=":(" alt="😞" /></p>
]]></description><link>https://xcp-ng.org/forum/topic/12388/vm-autostart-stopped-working</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Jul 2026 18:01:20 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/12388.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 29 Jul 2026 21:05:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to VM autostart stopped working on Thu, 30 Jul 2026 07:30:06 GMT]]></title><description><![CDATA[<p dir="auto">Glad the start-delay removal got that VM going again. I checked and it's a real, documented XCP-ng parameter, "the delay to wait before a call to start up the VM returns", so that explains the behavior.<br />
I couldn't find <code>auto_poweron_delay</code> documented anywhere in the XCP-ng or XO docs, so I'm not sure if it's something XO's advanced VM settings expose under a different name, or something unrelated you picked up while googling. <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f937.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--shrug" style="height:23px;width:auto;vertical-align:middle" title=":shrug:" alt="🤷" /><br />
If you check the VM's Advanced tab in XO and see what's actually set there, that would help pin down which setting you're really dealing with.<br />
Either way this looks like a gap in the autostart guide, since it doesn't mention that start-delay can interact with autostart at all.</p>
]]></description><link>https://xcp-ng.org/forum/post/107362</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/107362</guid><dc:creator><![CDATA[poddingue]]></dc:creator><pubDate>Thu, 30 Jul 2026 07:30:06 GMT</pubDate></item><item><title><![CDATA[Reply to VM autostart stopped working on Wed, 29 Jul 2026 21:59:43 GMT]]></title><description><![CDATA[<p dir="auto">I removed the start-delay parameter from one of the VMs (only this one has it) and now it works again.<br />
I don't get it.<br />
No idea how to achieve a startup delay for a specific VM though. There's also "auto_poweron_delay" and I don't understand what the difference from "start-delay" is.</p>
]]></description><link>https://xcp-ng.org/forum/post/107356</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/107356</guid><dc:creator><![CDATA[Octopuss]]></dc:creator><pubDate>Wed, 29 Jul 2026 21:59:43 GMT</pubDate></item></channel></rss>