From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>,
Ian.Campbell@citrix.com, david.vrabel@citrix.com
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"'keir@xen.org'" <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable
Date: Wed, 4 Jan 2012 18:35:24 -0500 [thread overview]
Message-ID: <20120104233524.GA31620@phenom.dumpdata.com> (raw)
In-Reply-To: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com>
On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote:
> I'm encountering following problems while using the latest xen-4.1-testing and xen-unstable with the latest Linux 3.2 kernel:
>
>
> 1) Xen-4.1-testing: dom0 only sees ~2.6GB on a 4GB system, using "cat /proc/meminfo". This is without dom_mem boot parameter and with 64-bit Xen and dom0 Linux. Native Linux reports correct memory size.
Huh. You are right. Hadn't noticed that before since I was using dom0_mem.
Ian, David: any ideas? I get the same problem and it looks as
if the area above 4GB ends up being reserved.
>
>
>
> 2) Xen-unstable: I get ext4 file system corruption when booting xen with the latest upstream Linux kernel.
That I hadn't seen. Is this with dom0 or domU? There is one bug in the 2.6.18 kernel
in blkback if you are using that version.
>
> Has anyone seen these two problems?
>
> Allen
next prev parent reply other threads:[~2012-01-04 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 22:07 problems I encountered using xen-4.1-testing and xen-unstable Kay, Allen M
2012-01-04 23:35 ` Konrad Rzeszutek Wilk [this message]
2012-01-05 8:01 ` Jan Beulich
2012-01-05 21:24 ` Konrad Rzeszutek Wilk
2012-01-06 7:53 ` Jan Beulich
2012-01-06 15:02 ` Konrad Rzeszutek Wilk
2012-01-05 8:05 ` Ian Campbell
2012-01-05 21:25 ` Konrad Rzeszutek Wilk
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=20120104233524.GA31620@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=allen.m.kay@intel.com \
--cc=david.vrabel@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.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.