From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: tutu sky <ooohooo_u@hotmail.com>
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
Meng Xu <xumengpanda@gmail.com>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: xenpm and scheduler
Date: Wed, 13 Apr 2016 05:52:12 -0400 [thread overview]
Message-ID: <20160413095211.GC2133@localhost.localdomain> (raw)
In-Reply-To: <HE1PR05MB1308FDECCBDC13975ECC09AB8D960@HE1PR05MB1308.eurprd05.prod.outlook.com>
On Wed, Apr 13, 2016 at 08:21:46AM +0000, tutu sky wrote:
> Dario, let me try it in real hardware and i'll back reporting here. I know that there are some distros which are suitable to be dom0:
> http://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen
> I think i choose my distro correctly (ubuntu 14.04 LTS) and i can see xen related configurations in its .config file.
>
> i thought as same as you but after reading devel lists and people's problem with this feature, i noticed maybe using xenpm needs make some modification about acpi in dom0's .config file, which leads to kernel building again. I'm not sure now and after running my setup on a real hardware, i'll back to report here.
> those people who encountered problems, used real hardware.
Right, you may just want to use the distro supplied version of Xen
first.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-13 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 8:16 xenpm and scheduler tutu sky
2016-04-11 12:11 ` Meng Xu
2016-04-12 3:52 ` tutu sky
2016-04-12 8:10 ` Dario Faggioli
2016-04-12 11:50 ` tutu sky
2016-04-12 13:41 ` Konrad Rzeszutek Wilk
2016-04-12 17:04 ` tutu sky
2016-04-12 17:08 ` Konrad Rzeszutek Wilk
2016-04-12 17:46 ` tutu sky
2016-04-12 21:05 ` Dario Faggioli
2016-04-13 8:21 ` tutu sky
2016-04-13 9:52 ` Konrad Rzeszutek Wilk [this message]
2016-04-13 10:24 ` Dario Faggioli
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=20160413095211.GC2133@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=Xen-devel@lists.xen.org \
--cc=dario.faggioli@citrix.com \
--cc=ooohooo_u@hotmail.com \
--cc=xumengpanda@gmail.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.