WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Latest pvops dom0 kernel and missing /dev/xen/evtchn, xe

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Latest pvops dom0 kernel and missing /dev/xen/evtchn, xenstored and xend not starting
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sat, 19 Jun 2010 21:04:56 +0300
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 19 Jun 2010 11:05:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C1D0184.4060203@xxxxxxxx>
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>
References: <20100619131801.GF17817@xxxxxxxxxxx> <435854.48558.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100619133702.GH17817@xxxxxxxxxxx> <4C1CE092.8070104@xxxxxxxx> <20100619163830.GP17817@xxxxxxxxxxx> <4C1D0184.4060203@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Jun 19, 2010 at 06:42:28PM +0100, Jeremy Fitzhardinge wrote:
> On 06/19/2010 05:38 PM, Pasi Kärkkäinen wrote:
> > On Sat, Jun 19, 2010 at 04:21:54PM +0100, Jeremy Fitzhardinge wrote:
> >   
> >> On 06/19/2010 02:37 PM, Pasi Kärkkäinen wrote:
> >>     
> >>> On Sat, Jun 19, 2010 at 06:32:21AM -0700, Boris Derzhavets wrote:
> >>>   
> >>>       
> >>>>    > Looks like it's this one in xen-4.0.1-rc2-pre:
> >>>>    [1]> http://xenbits.xen.org/xen-4.0-testing.hg?rev/0e1521f654f2
> >>>>
> >>>>    I believe you are right.
> >>>>
> >>>>    > What was the corresponding changeset/patch in xen/stable-2.6.32.x 
> >>>> that
> >>>>    breaks things > with Xen 4.0.0 ?
> >>>>
> >>>>    If you mean PV network issue after merge netback-tasklets . 
> >>>>
> >>>>     
> >>>>         
> >>> No, I don't mean that.
> >>>
> >>> I mean older xen/stable-2.6.32.x kernels DO work with xen-4.0.0,
> >>> but the latest xen/stable-2.6.32.x does NOT work with xen-4.0.0.
> >>>
> >>> So there is some change/patch in the dom0 kernel that breaks things with 
> >>> xen 4.0.0.
> >>>   
> >>>       
> >> 376d908f52427591cef4acd172db9c3ef28676ec and
> >> 9d85e25edbcb8a684db8470119077475ac4d90b5
> >>
> >>     
> > Ok, thanks.
> >
> > I seem to have these major/minors on my devices:
> >
> > # ls -la /dev/xen
> > total 0
> > drwxr-xr-x  2 root root     80 Jun 19 19:17 .
> > drwxr-xr-x 20 root root   4580 Jun 19 19:33 ..
> > crw-rw----  1 root root 10, 58 Jun 19 19:17 evtchn
> > crw-rw----  1 root root 10, 57 Jun 19 19:17 gntdev
> >
> > Is that correct? They don't seem to match what you pasted earlier..
> >
> > Then again things seem to work.. I can install new guests using 
> > virt-manager etc :)
> >   
> 
> The major/minors are completely dynamic, depending on what else you've
> got in your kernel.  /proc/misc will tell you what they should be.  The
> problem is that (old) libxc has some completely broken code to re-create
> the device which ends up destroying any correctly created device if it
> fails to determine what the major/minor is - and with the change in
> kernel device name, it does fail.
> 

Thanks.

I added info about that to XenParavirtOps wiki page.

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel