Hey there Michael, Thanks for the response!
As far as I can tell, these drivers are not in the kernel, and will not be in the near future. These drivers are part of the xen hg repository. I expect that I'll need to use DKMS in order to get the drivers built. I've written up a HOWTO for doing it manually: http://wp.colliertech.org/cj/?p=653 Cheers, C.J. On Sat, 2010-04-10 at 01:08 +0400, Michael Tokarev wrote: > 10.04.2010 00:09, C.J. Adams-Collier wrote: > > Package: wnpp > > Severity: wishlist > > Owner: "C.J. Adams-Collier"<c...@colliertech.org> > > Owner: "C.J. Adams-Collier"<c...@colliertech.org> > > > > * Package name : xen-unmodified-drivers > > Version : 3.4.3 > > Upstream Author : Xen developers<xen-de...@lists.xensource.com> > > * URL : http://www.xen.org/ > > * License : GPL > > Programming Lang: C > > Description : Kernel drivers for paravirt-on-hvm devices > > > > Drivers for installation on HVM guests which provide access to the PV > > devices, including netfront, blkfront and scsifront > > Isn't this already included in the stock kernel? > Or maybe it is better to wait for the next kernel > release which - hopefully - will include all the > missing bits? The drivers aren't that problematic > as the pvops dom0, right? I mean, is it worth to > create a separate package when something is already > in kernel and that something will improve to match > the to-be-packaged thing? > > Not that I'm "against" or something, just... asking. > > Thanks! > > /mjt
signature.asc
Description: This is a digitally signed message part
