<?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[XCP-ng 7.6 RC1 available]]></title><description><![CDATA[<p dir="auto">A new pre-release is ready for XCP-ng 7.6<img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f680.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--rocket" style="height:23px;width:auto;vertical-align:middle" title=":rocket:" alt="🚀" />.</p>
<p dir="auto">This announcement is basically a copy-and-paste from <a href="https://xcp-ng.org/forum/topic/454/xcp-ng-7-6-beta">the announcement of the beta</a>, except the first section and the upgrade instructions.</p>
<h3>What changed since the beta</h3>
<h4>Signed files on our mirror</h4>
<p dir="auto">Until now, our packages and ISO images were not signed. This meant that if someone would have managed to hack our servers, they would have been able to modify the ISO images or packages installed through further updates. This also prevented us from spreading XCP-ng to mirrors outside our own servers, since we had no way of ensuring that the files were not altered by a third party.</p>
<p dir="auto">We have worked on this, so starting with this RC:</p>
<ul>
<li>every RPM package is signed and the signature is checked when you install or update a package from the repositories;</li>
<li>repository metadata are signed and checked by <code>yum</code></li>
<li>for each ISO image, we provide a checksum file called <code>SHA256SUMS</code> and a signature in <code>SHA256SUMS.asc</code> for you to verify the authenticity and integrity of the downloaded file</li>
<li>for each <code>.repo</code> file that we make you download for <code>yum update</code>-style upgrades, we also provide <code>SHA256SUMS</code> and <code>SHA256SUMS.asc</code> for you to verify the authenticity and integrity of the downloaded file</li>
</ul>
<p dir="auto">Details at <a href="https://github.com/xcp-ng/xcp/wiki/How-to-check-the-authenticity-of-files-downloaded-from-XCP-mirrors" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/xcp-ng/xcp/wiki/How-to-check-the-authenticity-of-files-downloaded-from-XCP-mirrors</a></p>
<h4>Other notable changes</h4>
<ul>
<li>Updated XCP-ng Center</li>
<li>As you already know, support for GFS2 is not available because it depends on proprietary software from Citrix. However our license daemon would report the feature as being available, which caused XCP-ng Center to offer the option to users (then failed to make it work). The license daemon now correctly reports the feature as not available.</li>
</ul>
<h3>What changed since XCP-ng 7.5</h3>
<ul>
<li>Based on XenServer 7.6 (see <a href="https://xen-orchestra.com/blog/xenserver-7-6/" target="_blank" rel="noopener noreferrer nofollow ugc">https://xen-orchestra.com/blog/xenserver-7-6/</a>). It's mostly a maintenance update.</li>
<li>New welcome HTML page when you enter the IP address of your server in a web browser. See screenshots in my next comment to this thread.</li>
<li>Experimental packages:
<ul>
<li>We still have the <a href="https://github.com/xcp-ng/xcp/wiki/ZFS-on-XCP-ng-7.5-and-later" target="_blank" rel="noopener noreferrer nofollow ugc">experimental ZFS support</a>  and <code>zfs</code> packages have been updated to 0.7.11.</li>
<li>The modified <code>qemu-dp</code> package for Ceph support is being worked on (<a href="https://github.com/xcp-ng-rpms/qemu-dp/issues/5" target="_blank" rel="noopener noreferrer nofollow ugc">patches need to be updated</a>). Documentation draft still at <a href="https://github.com/xcp-ng/xcp/wiki/Ceph-on-XCP-ng-7.5-or-later" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/xcp-ng/xcp/wiki/Ceph-on-XCP-ng-7.5-or-later</a> but it's incomplete so I repeat here my call for help: this page needs a step-by-step procedure. <em>Anyone with a github account can improve it.</em></li>
</ul>
</li>
<li>Fixed some upgrade bugs in our packages.</li>
<li>In case you missed it: the installer now has <a href="https://xcp-ng.org/2018/09/21/xcp-ng-new-install-features/" target="_blank" rel="noopener noreferrer nofollow ugc">support for software RAID 1</a>.</li>
<li>In case you also missed it, there's a <a href="https://xcp-ng.org/2018/09/21/xcp-ng-new-install-features/" target="_blank" rel="noopener noreferrer nofollow ugc">network installer ISO</a> available too.</li>
<li>Some proprietary packages have been removed because we can't distribute them:
<ul>
<li>Citrix packages, most of them related to their work on improving the storage layer (smapiv3, GFS2...)
<ul>
<li>xapi-clusterd</li>
<li>sm-transport-lib: was LGPL in 7.5, became proprietary in 7.6</li>
<li>xapi-storage-plugins: was LGPL in 7.5, became proprietary in 7.6</li>
<li>livepatch-utils</li>
</ul>
</li>
<li>Emulex management tools. "elxocm" stands for "Emulex One Command Manager". Can probably be downloaded from their site.
<ul>
<li>elxocmcore</li>
<li>elxocmcorelibs</li>
<li>elxocmlibhbaapi</li>
</ul>
</li>
<li>QLogic tools. Available on their website.
<ul>
<li>QConvergeConsoleCLI-Citrix</li>
<li>QCS-CLI</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3>Documentation :</h3>
<p dir="auto">I structured the home page of <strong>our</strong> <a href="https://github.com/xcp-ng/xcp/wiki" target="_blank" rel="noopener noreferrer nofollow ugc">wiki</a> and started a thread for what I called the <a href="https://xcp-ng.org/forum/topic/435/great-projects-have-great-documentation-is-xcp-ng-a-great-project"><strong>"let's improve the documentation together"</strong> campaign</a>.</p>
<ul>
<li>Glass half full: everybody likes the idea and agrees that we need a great documentation, and some have contributed.</li>
<li>Glass half empty: most pages remain empty at the moment.</li>
</ul>
<p dir="auto">We, as a community, really need your help. Can we manage to fill, say, half the empty pages before we release XCP-ng 7.6?</p>
<h3>How to upgrade</h3>
<p dir="auto">There are two different upgrade methods: classical upgrade via installation ISO or upgrade using <code>yum</code>.</p>
<p dir="auto">Before upgrading, remember that it is a pre-release, so the risks are higher than with a final release. But if you can take the risk, please do and tell us how it went and what method you used!</p>
<p dir="auto">Reminder: <strong>always upgrade the master first</strong> (reboot it first, THEN the slaves).<br />
Also <strong>disable HA</strong> before upgrading.</p>
<p dir="auto">Now to the upgrade methods:</p>
<h4>Upgrade via the installation ISO image</h4>
<ul>
<li>Download <code>xcp-ng-7.6.0-RC1.iso</code> from <a href="https://updates.xcp-ng.org/isos/7.6/" target="_blank" rel="noopener noreferrer nofollow ugc">https://updates.xcp-ng.org/isos/7.6/</a></li>
<li><a href="https://github.com/xcp-ng/xcp/wiki/How-to-check-the-authenticity-of-files-downloaded-from-XCP-mirrors#check-an-iso-image" target="_blank" rel="noopener noreferrer nofollow ugc">Check the authenticity and the integrity of the downloaded ISO</a></li>
<li>Copy the ISO (byte to byte copy, such as using <code>dd</code>) to an usb stick and boot it. Or find another way to boot the ISO.</li>
</ul>
<h4>Upgrade via the network installation ISO image</h4>
<p dir="auto"><em><strong>Warning</strong></em>: this method does not verify the authenticity of the files downloaded accross the network yet.</p>
<ul>
<li>Download <code>xcp-ng-7.6.0-RC1-netinstall.iso</code></li>
<li><a href="https://github.com/xcp-ng/xcp/wiki/How-to-check-the-authenticity-of-files-downloaded-from-XCP-mirrors#check-an-iso-image" target="_blank" rel="noopener noreferrer nofollow ugc">Check the authenticity and the integrity of the downloaded ISO</a></li>
<li>Make sure the server has access either to *.xcp-ng.org or to a local mirror</li>
<li>Copy the ISO (byte to byte copy, such as using <code>dd</code>) to an usb stick and boot it. Or find another way to boot the ISO.</li>
<li><strong>Do not use the default repository URL</strong>: it would install the latest stable version instead of the development version.</li>
<li>Use this URL instead: <code>https://updates.xcp-ng.org/netinstall/7.6/</code></li>
</ul>
<h4>Upgrade from 7.5 with <code>yum</code></h4>
<p dir="auto">Follow the <a href="https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto#from-command-line-experimental-to-xcp-ng-76" target="_blank" rel="noopener noreferrer nofollow ugc">Upgrade Howto</a></p>
<h4>Upgrade from 7.6 beta with <code>yum</code></h4>
<p dir="auto">Usually <code>yum update</code> would be enough to go from beta to RC1, but in this specific case, do as if you were upgrading from 7.5 else you will still be using a configuration of <code>yum</code> that does not check the signatures.</p>
<h3>What to test</h3>
<p dir="auto">Mostly that what used to work still works! Report or ask anything as replies to this thread.</p>
<p dir="auto">If you have QLogic or Emulex hardware, please test that they still work properly without the proprietary packages that we removed. From what I know they are only management tools. If you need those tools, then please download and install them from the vendor and write down your steps in the wiki for the other users.</p>
]]></description><link>https://xcp-ng.org/forum/topic/488/xcp-ng-7-6-rc1-available</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 09:09:09 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/488.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 12 Oct 2018 14:21:01 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 05 Mar 2019 11:48:40 GMT]]></title><description><![CDATA[<p dir="auto">Actually, looks like I had already written something about it in the Updates Howto: <a href="https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations</a></p>
]]></description><link>https://xcp-ng.org/forum/post/9521</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/9521</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 05 Mar 2019 11:48:40 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 05 Mar 2019 10:32:19 GMT]]></title><description><![CDATA[<p dir="auto">Then I recommend that you <a href="https://github.com/xcp-ng/xcp/wiki/Updates-Howto" target="_blank" rel="noopener noreferrer nofollow ugc">apply all the other updates</a>, but you may want to wait for one day or two because there are security fixes on their way.</p>
]]></description><link>https://xcp-ng.org/forum/post/9520</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/9520</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 05 Mar 2019 10:32:19 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 05 Mar 2019 10:30:48 GMT]]></title><description><![CDATA[<p dir="auto">There is no such thing as XCP-ng 7.6.3 (but there's XCP-ng <strong>Center</strong> 7.6.3). There's just XCP-ng 7.6 with latest updates applied.</p>
<p dir="auto">The migration issues discussed above have been fixed in an update to the <code>xcp-emu-manager</code> package. That specific update does not require a reboot of the hosts: only a toolstack restart.</p>
<p dir="auto">You can either apply it from Xen Orchestra, or from command line with <code>yum update xcp-emu-manager</code>. Then <code>xe-toolstack-restart</code>.</p>
<p dir="auto">Once all hosts have the update, migration should be smooth.</p>
]]></description><link>https://xcp-ng.org/forum/post/9519</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/9519</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 05 Mar 2019 10:30:48 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 05 Mar 2019 10:26:39 GMT]]></title><description><![CDATA[<p dir="auto">This issue still appears to be present in 7.6.<br />
It it resolved in 7.6.3? I'm reluctant to pull hosts down without being able to move VM's safely without having to stop them.</p>
<p dir="auto">Cheers<br />
Greg</p>
]]></description><link>https://xcp-ng.org/forum/post/9518</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/9518</guid><dc:creator><![CDATA[glipschitz]]></dc:creator><pubDate>Tue, 05 Mar 2019 10:26:39 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 21:19:53 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> said in <a href="/forum/post/5706">XCP-ng 7.6 RC1 available</a>:</p>
<blockquote>
<p dir="auto">e it working if the load is not</p>
</blockquote>
<p dir="auto">I had this happen on VMs even when they had no load, but now they work.  I suspect it's ignoring other progress messages that were the problem in my case.</p>
]]></description><link>https://xcp-ng.org/forum/post/5707</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5707</guid><dc:creator><![CDATA[conradical]]></dc:creator><pubDate>Wed, 14 Nov 2018 21:19:53 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 21:12:05 GMT]]></title><description><![CDATA[<p dir="auto">Yeah, the current patch is able to make it working if the load is not too huge. We are still working to get it fully functional <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://xcp-ng.org/forum/post/5706</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5706</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Wed, 14 Nov 2018 21:12:05 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 15:09: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><br />
I don't have that pool anymore because I just yum updated it.  If I get time i'll deploy 7.5 again.</p>
]]></description><link>https://xcp-ng.org/forum/post/5699</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5699</guid><dc:creator><![CDATA[conradical]]></dc:creator><pubDate>Wed, 14 Nov 2018 15:09:33 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 15:05:39 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/conradical" aria-label="Profile: conradical">@<bdi>conradical</bdi></a> Since you had issues in 7.5 also, would you mind testing <code>xcp-emu-manager-0.0.3-1.2.x86_64.rpm</code> which is still in the <code>updates_testing</code> repository too?</p>
<pre><code>yum install xcp-emu-manager --enablerepo='xcp-ng-updates-testing'
</code></pre>
]]></description><link>https://xcp-ng.org/forum/post/5698</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5698</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Wed, 14 Nov 2018 15:05:39 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 15:04:58 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>  Yes it is!!</p>
]]></description><link>https://xcp-ng.org/forum/post/5697</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5697</guid><dc:creator><![CDATA[conradical]]></dc:creator><pubDate>Wed, 14 Nov 2018 15:04:58 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 15:01:46 GMT]]></title><description><![CDATA[<p dir="auto">Thanks, this is good news!</p>
]]></description><link>https://xcp-ng.org/forum/post/5696</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5696</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Wed, 14 Nov 2018 15:01:46 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 14 Nov 2018 15:00:55 GMT]]></title><description><![CDATA[<p dir="auto">FYI The newly released xcp-emu-manager-0.0.6-2.x86_64.rpm has resolved the migration issues that i could produce.</p>
]]></description><link>https://xcp-ng.org/forum/post/5695</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5695</guid><dc:creator><![CDATA[conradical]]></dc:creator><pubDate>Wed, 14 Nov 2018 15:00:55 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Fri, 09 Nov 2018 10:10:23 GMT]]></title><description><![CDATA[<p dir="auto">That last comment is not intended as criticism of users who'd skip a release. It's just an explanation of why we thought it would not harm to release the 7.6 release as it was.</p>
]]></description><link>https://xcp-ng.org/forum/post/5473</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5473</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Fri, 09 Nov 2018 10:10:23 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Fri, 09 Nov 2018 10:05:09 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/wayne" aria-label="Profile: wayne">@<bdi>wayne</bdi></a> while it was found during the testing phase for 7.6, it was already present in 7.5 and hadn't been detected until late, so it let us assume that only few users were affected and that is was not worse to release 7.6 with it (and fix it fast) than it had been releasing 7.5 with it. We did not foresee that people still in 7.4 would skip 7.5 and discover the bug with 7.6.</p>
]]></description><link>https://xcp-ng.org/forum/post/5472</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5472</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Fri, 09 Nov 2018 10:05:09 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Fri, 09 Nov 2018 09:59:56 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> my problem isn't the bug, there always be bugs.</p>
<p dir="auto">My problem is that there is no proper communication about it still. I think it is a serious issue about which you know <em>before</em> the 7.6 release as it was tested in rc phase apparently.</p>
<p dir="auto">It should have been mentioned when 7.6 was released, so anybody be aware what they're risking with upgrading.</p>
<p dir="auto">Anyhow, I'm glad that the fix is coming.</p>
]]></description><link>https://xcp-ng.org/forum/post/5471</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5471</guid><dc:creator><![CDATA[wayne]]></dc:creator><pubDate>Fri, 09 Nov 2018 09:59:56 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Thu, 08 Nov 2018 10:17:20 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">Aha Ok then I understand <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /><br />
Sorry!!</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/wayne" aria-label="Profile: wayne">@<bdi>wayne</bdi></a><br />
Sorry for that <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/post/5383</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5383</guid><dc:creator><![CDATA[Adde]]></dc:creator><pubDate>Thu, 08 Nov 2018 10:17:20 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Thu, 08 Nov 2018 09:32:21 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/adde" aria-label="Profile: Adde">@<bdi>Adde</bdi></a> Wayne's issues are not related to the update via <code>yum</code>, they're related to a bug in our replacement of the proprietary <code>emu-manager</code> (for which we'll release update candidates today).</p>
]]></description><link>https://xcp-ng.org/forum/post/5382</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5382</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Thu, 08 Nov 2018 09:32:21 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Thu, 08 Nov 2018 09:25:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/wayne" aria-label="Profile: wayne">@<bdi>wayne</bdi></a><br />
<a href="https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto#from-command-line" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto#from-command-line</a><br />
'know you're doing it at <strong>your own risk</strong> and be prepared to fix any issues that would arise, especially unforeseen upgrade issues'</p>
<p dir="auto">//Adde</p>
]]></description><link>https://xcp-ng.org/forum/post/5381</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5381</guid><dc:creator><![CDATA[Adde]]></dc:creator><pubDate>Thu, 08 Nov 2018 09:25:42 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Wed, 07 Nov 2018 16:23:53 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> honestly, my problem is that i was using 7.4 and i upgraded to 7.6, which made a perfectly stable pool pretty unstable.</p>
<p dir="auto">It would have been really helpful to read a warning beforehand about this nasty bug which still exists in 7.6 as you were aware at that point.</p>
]]></description><link>https://xcp-ng.org/forum/post/5369</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5369</guid><dc:creator><![CDATA[wayne]]></dc:creator><pubDate>Wed, 07 Nov 2018 16:23:53 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 06 Nov 2018 15:24:56 GMT]]></title><description><![CDATA[<p dir="auto">I think the tools were built by XS before 7.5 was released and still carry the 7.4 version number, but they are the latest.</p>
]]></description><link>https://xcp-ng.org/forum/post/5325</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5325</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 06 Nov 2018 15:24:56 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 06 Nov 2018 14:26:13 GMT]]></title><description><![CDATA[<p dir="auto">This is what I see, not sure how that correlates to the correct tools build for 7.6</p>
<p dir="auto">xe vm-param-get param-name=PV-drivers-version uuid=3a8a717f-c998-f05f-d096-f486a4990d1<br />
major: 7; minor: 4; micro: 50; build: 1</p>
<p dir="auto">Thx Will</p>
]]></description><link>https://xcp-ng.org/forum/post/5323</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5323</guid><dc:creator><![CDATA[WBA]]></dc:creator><pubDate>Tue, 06 Nov 2018 14:26:13 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Tue, 06 Nov 2018 09:22:58 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/wba" aria-label="Profile: WBA">@<bdi>WBA</bdi></a> said in <a href="/forum/post/5302">XCP-ng 7.6 RC1 available</a>:</p>
<blockquote>
<p dir="auto">This is what I see when I install guest-tools after migrating the VM to the 7.6 host.<br />
root@# /mnt/Linux/install.sh<br />
Detected `Debian GNU/Linux 9.5 (stretch)' (debian version 9).</p>
<p dir="auto">The following changes will be made to this Virtual Machine:</p>
<ul>
<li>packages to be installed/upgraded:
<ul>
<li>xe-guest-utilities_7.10.0-1_amd64.deb</li>
</ul>
</li>
</ul>
</blockquote>
<p dir="auto">This is the correct version of the tools in XCP-ng 7.6 and is the same as in XCP-ng 7.5.  It was 7.9.0 in 7.4.</p>
<p dir="auto">Using yum to upgrade does give you the right version of the guest tools ISO.</p>
<p dir="auto">So we need to find out why XCP-ng Center reports version 7.4.</p>
<p dir="auto">Does anyone know how to check using <code>xe</code> in CLI to see if the wrong version number is reported by <code>xapi</code> directly or is coming from a bug in XCP-ng Center?</p>
]]></description><link>https://xcp-ng.org/forum/post/5313</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5313</guid><dc:creator><![CDATA[stormi]]></dc:creator><pubDate>Tue, 06 Nov 2018 09:22:58 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Mon, 05 Nov 2018 18:34:21 GMT]]></title><description><![CDATA[<p dir="auto">I just upgraded from version 7.5 to 7.6 using yum upgrade, all seemed to go without error.<br />
When I started to migrate our vm's from one of the 7.5 hosts to the new 7.6 host the vm's would be hung and unresponsive on the new host when the migration completed.<br />
A forced stop and a fresh start of the VM brought the VMs back up.<br />
After finding this post and seeing the notes about "xe-guest-utilities" I noticed that when I install the guest-tools the version remains the same, in fact the version remains at 7.4 looking at it in XCP-ng Center.<br />
Optimized (version 7.4 installed)</p>
<p dir="auto">This is what I see when I install guest-tools after migrating the VM to the 7.6 host.<br />
root@# /mnt/Linux/install.sh<br />
Detected `Debian GNU/Linux 9.5 (stretch)' (debian version 9).</p>
<p dir="auto">The following changes will be made to this Virtual Machine:</p>
<ul>
<li>packages to be installed/upgraded:
<ul>
<li>xe-guest-utilities_7.10.0-1_amd64.deb</li>
</ul>
</li>
</ul>
<p dir="auto">Continue? [y/n] y</p>
<p dir="auto">(Reading database ... 42324 files and directories currently installed.)<br />
Preparing to unpack .../xe-guest-utilities_7.10.0-1_amd64.deb ...<br />
Unpacking xe-guest-utilities (7.10.0-1) over (7.10.0-1) ...<br />
Setting up xe-guest-utilities (7.10.0-1) ...<br />
Processing triggers for systemd (232-25+deb9u4) ...</p>
<p dir="auto">You should now reboot this Virtual Machine.<br />
root@#</p>
<p dir="auto">What is the correct version of guest-tools?<br />
Are guest-tools not being updated because I have used yum to upgrade for the last 2 versions?<br />
I should note these are 95% Linux VM's</p>
<p dir="auto">Thanks, Will</p>
]]></description><link>https://xcp-ng.org/forum/post/5302</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5302</guid><dc:creator><![CDATA[WBA]]></dc:creator><pubDate>Mon, 05 Nov 2018 18:34:21 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Mon, 05 Nov 2018 16:12:02 GMT]]></title><description><![CDATA[<p dir="auto">Yeah, that's why we didn't stopped the release anyway. We got some trace and we continue to investigate right now. I hope we can have something this week.</p>
]]></description><link>https://xcp-ng.org/forum/post/5291</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5291</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Mon, 05 Nov 2018 16:12:02 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-ng 7.6 RC1 available on Mon, 05 Nov 2018 16:09:40 GMT]]></title><description><![CDATA[<p dir="auto">just FYI, it is in 7.5 as well. Looking forward to the patch.</p>
]]></description><link>https://xcp-ng.org/forum/post/5290</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/5290</guid><dc:creator><![CDATA[conradical]]></dc:creator><pubDate>Mon, 05 Nov 2018 16:09:40 GMT</pubDate></item></channel></rss>