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


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Linux 3.0-rc1 - what Xen components went in.
From: Stephan Seitz <stse+xen@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 16 Jun 2011 11:48:20 +0200
Delivery-date: Thu, 16 Jun 2011 02:49:08 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fsing.rootsland.net; s=mail20100714; t=1308217700; bh=80anXqLDaFqw8p7GLMv9pLiUocZ6YoYhkUacO5hrJB0=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=Ot9p354G2XLC6CJppwFuduahnFpryk+131T/zYI1DuKjCXzBw3BBY+BEjkGwXWT2f +y4cMWIqTyEpiwq7OBm1DHjiP5TulsrbQK+NN1QUH9E/1EuEJO0xRaMYG9tEj2lSm1 g7u2rB8qt9QnygitIItOg/KZgpp3x212C/u5+cLU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110531161224.GA1340@xxxxxxxxxxxx>
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>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Organization: Minas Tirith, Gondor
References: <20110531161224.GA1340@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
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 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 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.

Shade and sweet water!


| Stephan Seitz             E-Mail: stse@xxxxxxxxxxxxxxxxxxx |
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |

Attachment: signature.asc
Description: Digital signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>