From: Stephan Seitz <stse+xen@fsing.rootsland.net>
To: xen-devel@lists.xensource.com
Subject: Re: Linux 3.0-rc1 - what Xen components went in.
Date: Thu, 16 Jun 2011 19:31:43 +0200 [thread overview]
Message-ID: <20110616T190614.GA.1ac46.stse@fsing.rootsland.net> (raw)
In-Reply-To: <20110616150706.GA6275@dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 2540 bytes --]
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 2.6.36.4-DomU 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)
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.
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.
>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?
>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.
>> The DomU kernel is a 2.6.36.4 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 2.6.34.8 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-2.6.38.3-DomU (not working)
http://fsing.rootsland.net/~stse/config-2.6.36.4-DomU (working)
Thanks for your help.
Shade and sweet water!
Stephan
--
| Stephan Seitz E-Mail: stse@fsing.rootsland.net |
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-06-16 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 16:12 Linux 3.0-rc1 - what Xen components went in Konrad Rzeszutek Wilk
2011-06-01 6:15 ` [Xen-devel] " Joseph Glanville
2011-06-16 9:48 ` Stephan Seitz
2011-06-16 15:07 ` Konrad Rzeszutek Wilk
2011-06-16 17:31 ` Stephan Seitz [this message]
2011-06-16 18:00 ` Konrad Rzeszutek Wilk
2011-06-30 11:16 ` Stephan Seitz
2011-07-17 15:28 ` Problem with vfb at Xen 4.1 Dom0 ( 3.0.0-5-generic ) Ubuntu 11.10 (alpha 2) Boris Derzhavets
2011-07-18 11:35 ` [Xen-devel] " Stefano Stabellini
2011-07-18 12:29 ` Boris Derzhavets
2011-07-18 12:40 ` Stefano Stabellini
2011-07-18 13:45 ` Boris Derzhavets
2011-07-18 16:23 ` [Xen-devel] " Stefano Stabellini
2011-07-19 16:12 ` Olaf Hering
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=20110616T190614.GA.1ac46.stse@fsing.rootsland.net \
--to=stse+xen@fsing.rootsland.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).