<?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[Wyse 5070 VM won&#x27;t booting after update bios 1.27]]></title><description><![CDATA[<p dir="auto">Wanted to share this with group because this had me thrown for a loop for the better part of three day &amp; I know there are quite a few other homelab aficionados that repurposed these little thinclients because they are just so small &amp; versatile.</p>
<p dir="auto">TLDR: microcode update was to culprit. Hope dell either push an update or it otherwise get resolved or...I'll be unsecure, I guess.</p>
<p dir="auto">Fixed it by rolling back to version 2:2.1-26.xs28.1.xcpng8.2</p>
<p dir="auto">yum downgrade microcode_ctl 2:2.1-26.xs28.1.xcpng8.2</p>
<p dir="auto">yum downgrade microcode_ctl</p>
<p dir="auto">might work as well, but that really depends on your upgrade path.</p>
<p dir="auto">Detail:</p>
<p dir="auto">After a recent update I discovered that none on my virtual machines would boot save for one that would boot sporadically. It was accidentally set to pv drivers...not entirely sure how that happened, but it also could have just loaded that way when I imported the cloud image from Harvester.</p>
<p dir="auto">The symptoms:</p>
<p dir="auto">Not keyboard or mouse input for windows or linux.</p>
<p dir="auto">Windows vms would boot &amp; do one of two thing the screen would "Guest has not initialised the display (yet)" or get to the point where the drive was initialized &amp; hang...they would basically max out what CPU they were allowed.</p>
<p dir="auto">Linux vms would boot &amp; always hang at the same place right after grub loaded initial ramdisk.</p>
<p dir="auto">Try every bios setting I could no joy.</p>
<p dir="auto">Hope you other poor stuck soles stumble of this &amp; save your self's some time.</p>
]]></description><link>https://xcp-ng.org/forum/topic/8736/wyse-5070-vm-won-t-booting-after-update-bios-1-27</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Apr 2026 23:23:06 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/8736.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 01 Apr 2024 00:21:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 28 May 2024 15:02:39 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/andyhhp" aria-label="Profile: andyhhp">@<bdi>andyhhp</bdi></a> giving this a shot now.</p>
]]></description><link>https://xcp-ng.org/forum/post/78047</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/78047</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Tue, 28 May 2024 15:02:39 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 28 May 2024 14:31:49 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain I've got a fix from Intel, and <a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a> has packaged it.</p>
<p dir="auto"><code>yum update microcode_ctl --enablerepo=xcp-ng-testing</code> should get you <code>microcode_ctl-2.1-26.xs29.2.xcpng8.2</code> which has the fixed microcode for this issue in it.</p>
]]></description><link>https://xcp-ng.org/forum/post/78044</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/78044</guid><dc:creator><![CDATA[andyhhp]]></dc:creator><pubDate>Tue, 28 May 2024 14:31:49 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Fri, 05 Apr 2024 07:20:20 GMT]]></title><description><![CDATA[<p dir="auto">Doc about XTF testing: <a href="https://docs.xcp-ng.org/project/development-process/tests/#test-the-xen-hypervisor-itself" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.xcp-ng.org/project/development-process/tests/#test-the-xen-hypervisor-itself</a></p>
]]></description><link>https://xcp-ng.org/forum/post/74929</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74929</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Fri, 05 Apr 2024 07:20:20 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Thu, 04 Apr 2024 22:56:33 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain In addition to the XTF testing, could you also please (with the bad microcode) try booting Xen with <code>spec-ctrl=no-verw</code> on the command line, and seeing whether that changes the behaviour of your regular VMs?  Please capture <code>xl dmesg</code> from this run too.</p>
]]></description><link>https://xcp-ng.org/forum/post/74926</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74926</guid><dc:creator><![CDATA[andyhhp]]></dc:creator><pubDate>Thu, 04 Apr 2024 22:56:33 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Thu, 04 Apr 2024 13:40:46 GMT]]></title><description><![CDATA[<p dir="auto">However, logs from a debug Xen might give more clues.</p>
<p dir="auto">If you can, please follow the instructions given by <a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/andyhhp" aria-label="Profile: andyhhp">@<bdi>andyhhp</bdi></a> - a Xen developer - at <a href="https://xcp-ng.org/forum/post/74855">https://xcp-ng.org/forum/post/74855</a>.</p>
]]></description><link>https://xcp-ng.org/forum/post/74882</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74882</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Thu, 04 Apr 2024 13:40:46 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Thu, 04 Apr 2024 13:31:26 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain No need to, unless you have some doubts. For now the conclusion will be <code>xl dmesg</code> doesn't output anything particular when the VM hangs.</p>
]]></description><link>https://xcp-ng.org/forum/post/74879</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74879</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Thu, 04 Apr 2024 13:31:26 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Thu, 04 Apr 2024 13:28:33 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a> At that point that vm dsk05002 was hung for about 20 minutes. I don't know if it where are like this that an alert event is ever generated.</p>
<p dir="auto">If need be I can boot a vm &amp; just let it go.</p>
]]></description><link>https://xcp-ng.org/forum/post/74878</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74878</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Thu, 04 Apr 2024 13:28:33 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Thu, 04 Apr 2024 10:08:02 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain Was the xl dmesg output produced before, or after the VM hanged?</p>
]]></description><link>https://xcp-ng.org/forum/post/74856</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74856</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Thu, 04 Apr 2024 10:08:02 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Wed, 03 Apr 2024 21:41:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a></p>
<p dir="auto">You can see the vms just kind of hang here.</p>
<p dir="auto"><img src="/forum/assets/uploads/files/1712180481072-374c345a-8aef-4d42-8aaa-d997590415a6-image.png" alt="374c345a-8aef-4d42-8aaa-d997590415a6-image.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://xcp-ng.org/forum/post/74829</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74829</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Wed, 03 Apr 2024 21:41:24 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Wed, 03 Apr 2024 21:39:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a></p>
<p dir="auto">Here is the xl_dmesg output after the microcode update.</p>
<p dir="auto"><a href="/forum/assets/uploads/files/1712180390236-xenserver02.trc.blox_microcode_upd_xl_dmesg.txt">xenserver02.trc.blox_microcode_upd_xl_dmesg.txt</a></p>
]]></description><link>https://xcp-ng.org/forum/post/74828</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74828</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Wed, 03 Apr 2024 21:39:57 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 17:07:44 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain Yes, please. One host, with one failed VM start, would be enough</p>
]]></description><link>https://xcp-ng.org/forum/post/74723</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74723</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 02 Apr 2024 17:07:44 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 16:53:06 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a> Sorry about that only answered part of the question. I did have a vm fail to boot, but it was because of an underlying issues with drbd/xostor &amp; don't believe related to the microcode.</p>
]]></description><link>https://xcp-ng.org/forum/post/74721</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74721</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Tue, 02 Apr 2024 16:53:06 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 16:43:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a></p>
<p dir="auto">Those are the microcode downgraded hosts. I can upgrade the packages &amp; get those outputs as well if need be.</p>
]]></description><link>https://xcp-ng.org/forum/post/74719</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74719</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Tue, 02 Apr 2024 16:43:57 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 16:08:02 GMT]]></title><description><![CDATA[<p dir="auto">@t-chamberlain Is the output of <code>xl dmesg</code> with, or without the bad microcode? Did a VM fail to boot since the hosts were booted?</p>
]]></description><link>https://xcp-ng.org/forum/post/74718</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74718</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 02 Apr 2024 16:08:02 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 15:28:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a> said in <a href="/forum/post/74672">Wyse 5070 VM won't booting after update bios 1.27</a>:</p>
<blockquote>
<p dir="auto">head /proc/cpuinfo</p>
</blockquote>
<p dir="auto">Here info for my 3 nodes.</p>
<p dir="auto"><a href="/forum/assets/uploads/files/1712071258027-xenserver01.trc.blox_cpuinfo.txt">xenserver01.trc.blox_cpuinfo.txt</a><br />
<a href="/forum/assets/uploads/files/1712071258054-xenserver01.trc.blox_xl_dmesg.txt">xenserver01.trc.blox_xl_dmesg.txt</a><br />
<a href="/forum/assets/uploads/files/1712071258055-xenserver02.trc.blox_cpuinfo.txt">xenserver02.trc.blox_cpuinfo.txt</a><br />
<a href="/forum/assets/uploads/files/1712071258057-xenserver02.trc.blox_xl_dmesg.txt">xenserver02.trc.blox_xl_dmesg.txt</a><br />
<a href="/forum/assets/uploads/files/1712071258058-xenserver03.trc.blox_cpuinfo.txt">xenserver03.trc.blox_cpuinfo.txt</a><br />
<a href="/forum/assets/uploads/files/1712071258060-xenserver03.trc.blox_xl_dmesg.txt">xenserver03.trc.blox_xl_dmesg.txt</a></p>
]]></description><link>https://xcp-ng.org/forum/post/74712</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74712</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Tue, 02 Apr 2024 15:28:42 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 10:38:32 GMT]]></title><description><![CDATA[<p dir="auto">So, could you get some logs from the boot failures?</p>
<ul>
<li><code>head /proc/cpuinfo</code></li>
<li>full output of <code>xl dmesg</code> including booting the problem VM with the good and bad ucode in place</li>
</ul>
]]></description><link>https://xcp-ng.org/forum/post/74672</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74672</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 02 Apr 2024 10:38:32 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 10:30:59 GMT]]></title><description><![CDATA[<p dir="auto">My search engine just made me discover this one: <a href="https://xcp-ng.org/forum/topic/8584/dell-wyse-fw-update-breaks-vm-booting-console-frozen-tianocore-edk2-related">https://xcp-ng.org/forum/topic/8584/dell-wyse-fw-update-breaks-vm-booting-console-frozen-tianocore-edk2-related</a></p>
]]></description><link>https://xcp-ng.org/forum/post/74670</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74670</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 02 Apr 2024 10:30:59 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Tue, 02 Apr 2024 10:29:48 GMT]]></title><description><![CDATA[<p dir="auto">Making sure (how?) this topic is indexed by search engines would be a good starting point.</p>
]]></description><link>https://xcp-ng.org/forum/post/74668</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74668</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 02 Apr 2024 10:29:48 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Mon, 01 Apr 2024 14:53:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/olivierlambert" aria-label="Profile: olivierlambert">@<bdi>olivierlambert</bdi></a> Completely agree, years old consumer/non-HCL compliant hardware shouldn't rate in overall development progress &amp; a pin is about the best we should hope for.</p>
<p dir="auto">It might just be time for some home labbers to start shopping &amp; retire come gear!</p>
<p dir="auto">The XCP-NG community &amp; platform are amazing...keep up the great work!</p>
]]></description><link>https://xcp-ng.org/forum/post/74613</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74613</guid><dc:creator><![CDATA[t.chamberlain]]></dc:creator><pubDate>Mon, 01 Apr 2024 14:53:41 GMT</pubDate></item><item><title><![CDATA[Reply to Wyse 5070 VM won&#x27;t booting after update bios 1.27 on Mon, 01 Apr 2024 08:36:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/stormi" aria-label="Profile: stormi">@<bdi>stormi</bdi></a> I'm not sure there's many things we can do about it, maybe a proper/documented way to pin the latest working microcode?</p>
]]></description><link>https://xcp-ng.org/forum/post/74587</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/74587</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Mon, 01 Apr 2024 08:36:35 GMT</pubDate></item></channel></rss>