<?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[Alternative to memory ballooning]]></title><description><![CDATA[<p dir="auto">Memory ballooning is a good thing, but can lead to issues, especially during migration. Since Citrix seems to have abandoned the technology, I am happy Xcp-ng keeps it.</p>
<p dir="auto">In QEMU/KVM/VirtIO world there is a new thing as an alternative to ballooning, which is memory hot plug. <a href="https://virtio-mem.gitlab.io/" target="_blank" rel="noopener noreferrer nofollow ugc">https://virtio-mem.gitlab.io/</a></p>
<p dir="auto">The basic idea is to emulate memory modules and utilise OS support for memory hot plug, something that has been used on bare metal servers before.</p>
<p dir="auto">Could this be a avenue to develop with xcp-ng to overcome the limitations of the traditional ballooning?</p>
<p dir="auto">One clear benefit is to be able to add more memory than originally allocated a guest without restarting the guest.</p>
]]></description><link>https://xcp-ng.org/forum/topic/7857/alternative-to-memory-ballooning</link><generator>RSS for Node</generator><lastBuildDate>Wed, 14 Oct 2026 03:29:35 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/7857.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 15 Oct 2023 16:55:48 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Alternative to memory ballooning on Sun, 15 Oct 2023 19:00:15 GMT]]></title><description><![CDATA[<p dir="auto">No sure this will be compatible with the level of memory isolation provided in Xen (vs the more "open bar" model in KVM). Worth taking a look though, thanks for the link.</p>
]]></description><link>https://xcp-ng.org/forum/post/66565</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/66565</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Sun, 15 Oct 2023 19:00:15 GMT</pubDate></item></channel></rss>