From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jia Rao Subject: Re: Problems with xen and linux 2.26.32 kernels for dom0 Date: Wed, 16 Jun 2010 17:06:04 -0400 Message-ID: References: <20100616194310.GB8413@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0603709155==" Return-path: In-Reply-To: <20100616194310.GB8413@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0603709155== Content-Type: multipart/alternative; boundary=0015175caebe03bcd904892c17b4 --0015175caebe03bcd904892c17b4 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jun 16, 2010 at 3:43 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > On Wed, Jun 16, 2010 at 03:00:03PM -0400, Jia Rao wrote: > > Hi all, > > > > I used to use xen 3.4.2 and linux 2.6.18-xen kernels for both dom0 and > domU, > > without any problems. > > > > Recently, I need to try io bandwidth control like dm-ioband in the new > > kernel 2.6.32 (dm-ioband has patches for this kernel). It gave me a lot > of > > problems if I want to upgrade the dom0 to 2.6.32. The following is what I > > tried and the errors. > > > > > > Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run > pvops) > > > > *First approach:* > > I tried to download pvops from the git repository xen/stable-2.6.32.x. > The > > compilation was OK, but the initrd has a lot missing dependencies. I > tried > > to use --builtin to claim those missing modules in kernel. However, with > the > > generated initrd, dom0 can not boot. I got the error: *unable to locate > > IOAPIC for GSIx and mount: could not find filesystem: /dev/root*. > > I enabled : CONFIG_SYSFS_DEPRECATED=y, CONFIG_SYSFS_DEPRECATED_V2=y and > > tried to use root=/dev/sdax or root=LABEL=/. No luck. > > You did follow the the Wiki: > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher > > and made sure you had the right SATA drivers compiled in? They changed > their names from .18 to .31-and-higher > > > I tried the script with the pvops, the dom0 still cannt boot. How can I check if other modules have changed the name besides ata_piix ? > > *Second approach:* > > Then I switched to the forward ported 2.6.32.13 kernel generated from the > > gentoo xen kernel patches. > > > > Still xen 3.4.3. After compilation, dom0 booted successfully. However I > > previous domU which has 2.6.18-xen kernels can not boot. It has the same > > error: *mount: could not find filesystem: /dev/root > > *Do I need to create a initrd for the domU? I didnt need one when dom0 is > > 2.6.18-xen kernel. > > That is perplexing. If you did not change anything in your DomU it > should work as before. > The same domU booted correctly under an old dom0 which has a 2.6.18.8-xen kernel. BTW the domU booted using pygrub, so it should work under the new kernel. It is really strange. > > * > > *BTW. I dont see a PARAVIRT_GUEST config option in the forward ported > 2.6.32 > > kernel*. > > Right. You won't. They are a different type of patches. > --0015175caebe03bcd904892c17b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Wed, Jun 16, 2010 at 3:43 PM, Konrad = Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
On Wed, Jun 16, 2010 at 03:00:03PM -0400, Jia Rao wrote:<= br> > Hi all,
>
> I used to use xen 3.4.2 and linux 2.6.18-xen kernels for both dom0 and= domU,
> without any problems.
>
> Recently, I need to try io bandwidth control like dm-ioband in the new=
> kernel 2.6.32 (dm-ioband has patches for this kernel). It gave me a lo= t of
> problems if I want to upgrade the dom0 to 2.6.32. The following is wha= t I
> tried and the errors.
>
>
> Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run = pvops)
>
> *First approach:*
> I tried to download pvops from the git repository xen/stable-2.6.32.x.= The
> compilation was OK, but the initrd has a lot missing dependencies. I t= ried
> to use --builtin to claim those missing modules in kernel. However, wi= th the
> generated initrd, dom0 can not boot. I got the error: *unable to locat= e
> IOAPIC for GSIx and mount: could not find filesystem: /dev/root*.
> I enabled : CONFIG_SYSFS_DEPRECATED=3Dy, =A0CONFIG_SYSFS_DEPRECATED_V2= =3Dy and
> tried to use root=3D/dev/sdax or root=3DLABEL=3D/. No luck.

You did follow the the Wiki:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-hig= her

and made sure you had the right SATA drivers compiled in? They changed
their names from .18 to .31-and-higher
>
=A0
I tried the script with the pvops, = the dom0 still cannt boot. How can I check if other modules have changed th= e name besides ata_piix ?
=A0
> *Second approach:*
> Then I switched to the forward ported 2.6.32.13 kern= el generated from the
> gentoo xen kernel patches.
>
> Still xen 3.4.3. After compilation, dom0 booted successfully. However = I
> previous domU which has 2.6.18-xen kernels can not boot. It has the sa= me
> error: *mount: could not find filesystem: /dev/root
> *Do I need to create a initrd for the domU? I didnt need one when dom0= is
> 2.6.18-xen kernel.

That is perplexing. If you did not change anything in your DomU it should work as before.

The same domU booted correc= tly under an old dom0 which has a 2.6.18.8-xen kernel. BTW the domU booted = using pygrub, so it should work under the new kernel. It is really strange.=
> *
> *BTW. I dont see a PARAVIRT_GUEST config option in the forward ported = 2.6.32
> kernel*.

Right. You won't. They are a different type of patches.

--0015175caebe03bcd904892c17b4-- --===============0603709155== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0603709155==--