From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: Linux 3.0-rc1 - what Xen components went in. Date: Thu, 16 Jun 2011 11:07:06 -0400 Message-ID: <20110616150706.GA6275@dumpdata.com> References: <20110531161224.GA1340@dumpdata.com> <20110616T113336.GA.bd449.stse@fsing.rootsland.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110616T113336.GA.bd449.stse@fsing.rootsland.net> 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, stse+xen@fsing.rootsland.net List-Id: xen-devel@lists.xenproject.org On Thu, Jun 16, 2011 at 11:48:20AM +0200, Stephan Seitz wrote: > On Tue, May 31, 2011 at 12:12:24PM -0400, Konrad Rzeszutek Wilk wrote: > >- Xen block backend. Yes, it is in! >=20 > 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. >=20 > 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. >=20 > Going back to my 2.6.34.8 with xen patches the DomU problems vanished. So using the older Dom0. Are there any errors/warnings reported by the frontend? Is there a difference in the dmesg output from the DomU booted on 2.6.34 vs 3.0? >=20 > Here is the XEN configuration part for the DomU block devices: >=20 > disk =3D [ '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' ] >=20 that is pretty much how I've it too. Well: disk =3D [ 'phy:/dev/vg_guest_1/data-xfs,xvda,w', 'phy:/dev/vg_guest_1/da= ta-ext4,xvdb,w','phy:/dev/vg_guest_1/data-ext3,xvdc,w', 'phy:/dev/vg_gues= t_1/data-swap ,xvdd,w'] I don't try to put disks as partitions. Let me try that. Are the sizes that xne-blkfront report the same? > Do I have to change something? The devices are LUKS encrypted LVM > devices. Ah, hadn't tried LUKS. What happens if they are _not_ on LUKS? Let me set up LUKs on my box in the meantime. >=20 > The DomU kernel is a 2.6.36.4 vanilla kernel. I noticed that I can=E2=80= =99t > use a newer kernel. Every kernel > 2.6.36 crashes the DomU > immediatley (I don=E2=80=99t even get a console). The log said that Dom= U 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=3Dxenboot debug loglevel=3D10' please? Are you using a special version of .config? Is it available somewhere?