Xen 4.0 downloads the latest PV-OPS, which means dev/xen/evtchn and dev/xen/gnttab are not visible for Xen.

Xen 4.0 downloads the latest PV-OPS, which means dev/xen/evtchn and dev/xen/gnttab are not visible for Xen.

[Konrad Rzeszutek Wilk]

If a user gets the 4.0 sources from:

http://www.xen.org/products/xen_source.html

And runs the make process it fetches the latest pv-ops. Which
is a bit of a problem since the latest pv-ops has these two
commits: 9d85e25edbcb8a684db8470119077475ac4d90b5 
(xen/gnttab: use proper device name for gntdev) and
376d908f52427591cef4acd172db9c3ef28676ec
(xen/evtchn: Fix name of Xen event-channel device)

which are incompatible with Xen 4.0.

Any thoughts on how to fix this? Perhaps tagging right before
the those two commits and making the master point to that branch?

Re: Xen 4.0 downloads the latest PV-OPS, which means dev/xen/evtchn and dev/xen/gnttab are not visible for Xen.

[Pasi Kärkkäinen]

On Wed, Jun 30, 2010 at 04:49:33PM -0400, Konrad Rzeszutek Wilk wrote:
> If a user gets the 4.0 sources from:
> 
> http://www.xen.org/products/xen_source.html
> 
> And runs the make process it fetches the latest pv-ops. Which
> is a bit of a problem since the latest pv-ops has these two
> commits: 9d85e25edbcb8a684db8470119077475ac4d90b5 
> (xen/gnttab: use proper device name for gntdev) and
> 376d908f52427591cef4acd172db9c3ef28676ec
> (xen/evtchn: Fix name of Xen event-channel device)
> 
> which are incompatible with Xen 4.0.
> 
> Any thoughts on how to fix this? Perhaps tagging right before
> the those two commits and making the master point to that branch?
> 

Earlier I added a note about that to XenParavirtOps and XenCommonProblems wiki pages.
Now I also added a note about it to Xen4.0 wiki page.

So people should be able to figure it out with some googling :)
Soon though we'll (hopefully) have Xen 4.0.1 and then we don't have the problem anymore..

-- Pasi