From: sahilsuneja <sahilsuneja@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Issues with Xenpaging in Xen-4.2.1
Date: Wed, 27 Feb 2013 15:46:39 -0800 (PST) [thread overview]
Message-ID: <1362008799652-5714493.post@n5.nabble.com> (raw)
In-Reply-To: <1361840672591-5714431.post@n5.nabble.com>
sahilsuneja wrote
> Hi,
>
> I know Xenpaging is still at an experimental stage, but I still wanted to
> test it out. Sadly, I could not get it to work reliably.
>
> I have an AMD RVI enabled linux 3.2 host, and I am using linux 2.6.35-22
> HVM guests. After booting a few guests normally upto the host RAM limit, I
> do the following to enable paging for a few guests:
/
>>/usr/lib/xen/bin/xenpaging -f /var/lib/xen/xenpaging/pagefile-hvm-guest -d
1 &
>>xenstore-write /local/domain/1/memory/target-tot_pages $((1024*512))
/
>
> (here '1' is the dom_id and pagefile-hvm-guest is the backing paging file
> for the hvm guest)
>
> I am then able to boot more VMs and I can see the corresponding pagefiles
> increase in size for the xenpaging enabled guests.
>
> The problem is when I go back to the guests on which I enabled xenpaging,
> I see the following errors when I run any basic commands like vim, top,
> less /proc/meminfo:
/
> xc: error: Error populating page 100: Internal error
> xc: error: Error loading 100 during page-in (22 = Invalid argument):
> Internal error
/
>
> This happens even when there is paged-out memory from other guests to be
> had, and the system is not out of RAM for paging in guest's memory.
>
> It seems like a page-in error on gfn 100, but that is strange as, from I
> what I gathered from the xenpaging code, policy_default.c starts paging
> only after half of the guest's gfns : current_gfn = max_pages / 2 (inside
> policy_default.c: policy_init())
>
> I was expecting there to be other stability issues rather that this kind
> of an error.
>
> Could someone please help me understand this and let me know if I am doing
> something incorrectly.
>
> Also, there do not seem to be any interesting messages in xm dmesg or in
> /var/log/xen*.
>
> Thanks,
>
> Sahil Suneja
> Ph.D. Student
> University of Toronto
--
View this message in context: http://xen.1045712.n5.nabble.com/Issues-with-Xenpaging-in-Xen-4-2-1-tp5714431p5714493.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-02-27 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 1:04 Issues with Xenpaging in Xen-4.2.1 sahilsuneja
2013-02-26 9:57 ` Olaf Hering
2013-02-27 23:46 ` sahilsuneja [this message]
[not found] <CALOK3vdqwj-ZNOi_0uvarEorsZ1JaB+bfNXkbfGGLFB8gxFUuw@mail.gmail.com>
2013-02-28 0:07 ` Sahil Suneja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1362008799652-5714493.post@n5.nabble.com \
--to=sahilsuneja@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.