Hi Sepanta,
memsharing in Xen is fairly rough around the edges. Not being able to
share all pages between VMs is normal though. Last time I checked you
could still share a fairly large chunk of memory between a VM and its
clone created via save/restore. Just keep in mind that the origin VM
can't
On 8/24/18 8:07 AM, sepanta s wrote:
> I debugged the kernel codes and found out the root cause.
> The sharing is not done for some pages causing error -E2BIG which is due
> to reference count being more than one. This prevents hypervor to
> nominate the page. As much as I know about this issue,
Hi again,
I debugged the kernel codes and found out the root cause.
The sharing is not done for some pages causing error -E2BIG which is due to
reference count being more than one. This prevents hypervor to nominate the
page. As much as I know about this issue, the page that I want to nominate
Thanks.
I would be thankful if he can help me ...
On Mon, Jul 23, 2018 at 11:52 AM Razvan Cojocaru
wrote:
> On 07/23/2018 05:37 AM, sepanta s wrote:
> > I have written a program that can share memory pages of two VMs every x
> > milliseconds. To do so, I modified xen and added an unshare event
On 07/23/2018 05:37 AM, sepanta s wrote:
> I have written a program that can share memory pages of two VMs every x
> milliseconds. To do so, I modified xen and added an unshare event to be
> able to capture it. However, for some pages, when I receive the unshare
> event that contains the
Hi all,
I have written a program that can share memory pages of two VMs every x
milliseconds. To do so, I modified xen and added an unshare event to be
able to capture it. However, for some pages, when I receive the unshare
event that contains the information about the pages which was about to
