This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Linux 3.0-rc1 - what Xen components went in.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: Linux 3.0-rc1 - what Xen components went in.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 16 Jun 2011 14:00:35 -0400
Delivery-date: Thu, 16 Jun 2011 11:02:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110616T190614.GA.1ac46.stse@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110531161224.GA1340@xxxxxxxxxxxx> <20110616T113336.GA.bd449.stse@xxxxxxxxxxxxxxxxxxx> <20110616150706.GA6275@xxxxxxxxxxxx> <20110616T190614.GA.1ac46.stse@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Jun 16, 2011 at 07:31:43PM +0200, Stephan Seitz wrote:
> On Thu, Jun 16, 2011 at 11:07:06AM -0400, Konrad Rzeszutek Wilk wrote:
> >On Thu, Jun 16, 2011 at 11:48:20AM +0200, Stephan Seitz wrote:
> >>The 3.0-rc2 compiled and started without problems, even the DomU
> >>started.  But when I looked at the DomU console I noticed that the
> >>system had problems with the filesystems. ext3 and ext4 partitions
> >>produced journal errors and got mounted read only.
> >Hmm, are barriers somehow being turned on? (They shouldn't). It would
> >be helpfull if you included the error logs.
> At least with barriers seems to be enabled:
> blkfront: xvda1: barriers enabled (tag)
> blkfront: xvda2: barriers enabled (tag)
> blkfront: xvda5: barriers enabled (tag)
> blkfront: xvda6: barriers enabled (tag)
> blkfront: xvda7: barriers enabled (tag)
> blkfront: xvda8: barriers enabled (tag)

That is wrong. It should not have turned them on. The 3.0 version
does not export the feature-barrier at all. Looks like a bug
in xen-blkfront in 2.6.36 ..
> xvda1 is ext3 (root fs) with the mount option barrier=1, but this
> doesn’t seem to work (EXT3-fs: barriers not enabled). The other
> filesystems are ext4 without explicit barrier options and don’t have
> log output concerning barriers.

Uh, what? Do you see the errors if the barriers are turned off.  As
in -o barrier=0 or -o writeback=1
> For now I can’t make tests since I’m not at home for the next days.
> Then I will try to get logs as well. Since the filesystems are
> changed to read only, the logs are not written to disk, so I have to
> use other methods.

Uh, you can log the output from the kernel using the 'xl crreate -c'.
You might need to edit the Linux command line options..
> >I don't try to put disks as partitions. Let me try that. Are the sizes
> >that xne-blkfront report the same?
> xen-blkfront? Is this a program or kernel output? Dom0 or DomU?

kernel output.
> >Ah, hadn't tried LUKS. What happens if they are _not_ on LUKS?
> For now I can’t try it. Besides /boot in Dom0 all my partitions are
> LUKS encrypted.

OK? Can you try in a week or so? I am going to try to reproduce LUKS here.
You could just create new partition.

> >>The DomU kernel is a vanilla kernel. I noticed that I can’t
> >>use a newer kernel. Every kernel > 2.6.36 crashes the DomU
> >>immediatley (I don’t even get a console). The log said that DomU was
> >>crashing too fast, so it was disabled to avoid loops. This happens
> >>with as Dom0 kernel and with 3.0-rc2.
> >Can you boot it with 'earlyprintk=xenboot debug loglevel=10' please?
> Is this a boot option I pass to the DomU kernel? I will do the test
> next week.

> >Are you using a special version of .config? Is it available somewhere?
> http://fsing.rootsland.net/~stse/config- (not working)
> http://fsing.rootsland.net/~stse/config- (working)
> Thanks for your help.
> Shade and sweet water!
>       Stephan
> -- 
> | Stephan Seitz             E-Mail: stse@xxxxxxxxxxxxxxxxxxx |
> | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list