From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kay, Allen M" Subject: problems I encountered using xen-4.1-testing and xen-unstable Date: Wed, 4 Jan 2012 22:07:29 +0000 Message-ID: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1202393681981804278==" Return-path: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" Cc: Stefano Stabellini , "'keir@xen.org'" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org --===============1202393681981804278== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_003AAFE53969E14CB1F09B6FD68C3CD4019CB9ORSMSX105amrcorpi_" --_000_003AAFE53969E14CB1F09B6FD68C3CD4019CB9ORSMSX105amrcorpi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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. 2) Xen-unstable: I get ext4 file system corruption when booting xen w= ith the latest upstream Linux kernel. Has anyone seen these two problems? Allen --_000_003AAFE53969E14CB1F09B6FD68C3CD4019CB9ORSMSX105amrcorpi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m encountering following problems while usin= g the latest xen-4.1-testing and xen-unstable with the latest Linux 3.2 ker= nel:

 

1)      Xen-4.1-testing: dom0 only sees ~2.6GB on a 4GB sys= tem, using “cat /proc/meminfo”.  This is without dom_mem b= oot parameter and with 64-bit Xen and dom0 Linux.  Native Linux report= s correct memory size.

 

2)      Xen-unstable:  I get ext4 file system corrupti= on when booting xen with the latest upstream Linux kernel.

 

Has anyone seen these two problems?

 

Allen

--_000_003AAFE53969E14CB1F09B6FD68C3CD4019CB9ORSMSX105amrcorpi_-- --===============1202393681981804278== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1202393681981804278==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Wed, 4 Jan 2012 18:35:24 -0500 Message-ID: <20120104233524.GA31620@phenom.dumpdata.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Kay, Allen M" , Ian.Campbell@citrix.com, david.vrabel@citrix.com Cc: "xen-devel@lists.xensource.com" , "'keir@xen.org'" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Thu, 05 Jan 2012 08:01:22 +0000 Message-ID: <4F0566E2020000780006A89C@nat28.tlf.novell.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120104233524.GA31620@phenom.dumpdata.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , Keir Fraser , Ian.Campbell@citrix.com, Stefano Stabellini , Allen M Kay , david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org >>> On 05.01.12 at 00:35, Konrad Rzeszutek Wilk wrote: > On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote: >> 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. Which one are you referring to? Jan From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Thu, 5 Jan 2012 08:05:26 +0000 Message-ID: <1325750726.29084.3.camel@dagon.hellion.org.uk> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120104233524.GA31620@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "Keir (Xen.org)" , "xen-devel@lists.xensource.com" , "Kay, Allen M" , David Vrabel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 2012-01-04 at 23:35 +0000, Konrad Rzeszutek Wilk wrote: > 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? Nope. It would be nice to see some logs (xen+dom0 and native) though. Ian. > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Thu, 5 Jan 2012 16:24:25 -0500 Message-ID: <20120105212425.GA5180@phenom.dumpdata.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> <4F0566E2020000780006A89C@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4F0566E2020000780006A89C@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: "xen-devel@lists.xensource.com" , Keir Fraser , Ian.Campbell@citrix.com, Stefano Stabellini , Allen M Kay , david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org On Thu, Jan 05, 2012 at 08:01:22AM +0000, Jan Beulich wrote: > >>> On 05.01.12 at 00:35, Konrad Rzeszutek Wilk wrote: > > On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote: > >> 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. > > Which one are you referring to? The fix you posted some time ago. Not all distros have picked it up. # HG changeset patch From: Jan Beulich # Date 1306409621 -3600 # Node ID 876a5aaac0264cf38cae6581e5714b93ec380aaa # Parent aedb712c05cf065e943e15d0f38597c2e80f7982 Subject: xen/blkback: don't fail empty barrier requests The sector number on empty barrier requests may (will?) be uninitialized (neither bio_init() nor rq_init() set the respective fields), which allows for exceeding the actual (virtual) disk's size. Inspired by Konrad's "When writting barriers set the sector number to zero...", but instead of zapping the sector number (which is wrong for non-empty ones) just ignore the sector number when the sector count is zero. While at it also add overflow checking to the math in vbd_translate(). Signed-off-by: Jan Beulich diff -r aedb712c05cf -r 876a5aaac026 drivers/xen/blkback/vbd.c --- a/drivers/xen/blkback/vbd.c Thu May 26 08:09:04 2011 +0100 +++ b/drivers/xen/blkback/vbd.c Thu May 26 12:33:41 2011 +0100 @@ -108,8 +108,14 @@ int vbd_translate(struct phys_req *req, if ((operation != READ) && vbd->readonly) goto out; - if (unlikely((req->sector_number + req->nr_sects) > vbd_sz(vbd))) - goto out; + if (likely(req->nr_sects)) { + blkif_sector_t end = req->sector_number + req->nr_sects; + + if (unlikely(end < req->sector_number)) + goto out; + if (unlikely(end > vbd_sz(vbd))) + goto out; + } req->dev = vbd->pdevice; req->bdev = vbd->bdev; > > Jan From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Thu, 5 Jan 2012 16:25:50 -0500 Message-ID: <20120105212550.GB5180@phenom.dumpdata.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> <1325750726.29084.3.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1325750726.29084.3.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "Keir (Xen.org)" , "xen-devel@lists.xensource.com" , "Kay, Allen M" , David Vrabel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Thu, Jan 05, 2012 at 08:05:26AM +0000, Ian Campbell wrote: > On Wed, 2012-01-04 at 23:35 +0000, Konrad Rzeszutek Wilk wrote: > > 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? > > Nope. It would be nice to see some logs (xen+dom0 and native) though. I tried this last night and it seems that this problem has existed in 3.0 and in 3.1 as well. So not a regression but rather something we had never fixed. Interstingly enough you can experience the same problem with 8GB - you end up having 6GB in dom0. Naturally you can balloon up (hadn't tried to do it under 4GB with 2.68GB but it looks like you can certainly do it). From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Fri, 06 Jan 2012 07:53:05 +0000 Message-ID: <4F06B671020000780006AC26@nat28.tlf.novell.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> <4F0566E2020000780006A89C@nat28.tlf.novell.com> <20120105212425.GA5180@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120105212425.GA5180@phenom.dumpdata.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , Keir Fraser , Ian.Campbell@citrix.com, Stefano Stabellini , Allen M Kay , david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org >>> On 05.01.12 at 22:24, Konrad Rzeszutek Wilk wrote: > On Thu, Jan 05, 2012 at 08:01:22AM +0000, Jan Beulich wrote: >> >>> On 05.01.12 at 00:35, Konrad Rzeszutek Wilk wrote: >> > On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote: >> >> 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. >> >> Which one are you referring to? > > The fix you posted some time ago. Not all distros have picked it up. Ah, okay, an already fixed one - you could have said "was" instead of "is" to not make people like me nervous... Jan From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: problems I encountered using xen-4.1-testing and xen-unstable Date: Fri, 6 Jan 2012 10:02:44 -0500 Message-ID: <20120106150244.GA5855@phenom.dumpdata.com> References: <003AAFE53969E14CB1F09B6FD68C3CD4019CB9@ORSMSX105.amr.corp.intel.com> <20120104233524.GA31620@phenom.dumpdata.com> <4F0566E2020000780006A89C@nat28.tlf.novell.com> <20120105212425.GA5180@phenom.dumpdata.com> <4F06B671020000780006AC26@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4F06B671020000780006AC26@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: "xen-devel@lists.xensource.com" , Keir Fraser , Ian.Campbell@citrix.com, Stefano Stabellini , Allen M Kay , david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org On Fri, Jan 06, 2012 at 07:53:05AM +0000, Jan Beulich wrote: > >>> On 05.01.12 at 22:24, Konrad Rzeszutek Wilk wrote: > > On Thu, Jan 05, 2012 at 08:01:22AM +0000, Jan Beulich wrote: > >> >>> On 05.01.12 at 00:35, Konrad Rzeszutek Wilk wrote: > >> > On Wed, Jan 04, 2012 at 10:07:29PM +0000, Kay, Allen M wrote: > >> >> 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. > >> > >> Which one are you referring to? > > > > The fix you posted some time ago. Not all distros have picked it up. > > Ah, okay, an already fixed one - you could have said "was" instead > of "is" to not make people like me nervous... Sorry - I saw it a couple of months ago with some of the cloudproviders so it was still fresh in my mind.