All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:48:20 +0200	[thread overview]
Message-ID: <20110616T113336.GA.bd449.stse@fsing.rootsland.net> (raw)
In-Reply-To: <20110531161224.GA1340@dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]

On Tue, May 31, 2011 at 12:12:24PM -0400, Konrad Rzeszutek Wilk wrote:
> - Xen block backend. Yes, it is in!

I tried 3.0-rc2 as a Dom0 kernel, but I have problems with the block 
backend support.
Both Dom0 and DomU are Debian/Testing systems. XEN version is 4.1.0.

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.

Going back to my 2.6.34.8 with xen patches the DomU problems vanished.

Here is the XEN configuration part for the DomU block devices:

disk = [ 'phy:mapper/mroot,xvda1,w', 'phy:mapper/mswap,xvda2,w', 
'phy:mapper/mvar,xvda5,w', 'phy:mapper/msquid,xvda6,w', 
'phy:mapper/musr,xvda7,w', 'phy:mapper/mhome,xvda8,w' ]

Do I have to change something? The devices are LUKS encrypted LVM 
devices.

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.

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

  parent reply	other threads:[~2011-06-16  9:48 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 [this message]
2011-06-16 15:07   ` Konrad Rzeszutek Wilk
2011-06-16 17:31     ` Stephan Seitz
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=20110616T113336.GA.bd449.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 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.