[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Kernel drivers on domU

To: "Steffen Heil" <lists@xxxxxxxxxxxxxxx>
From: "Diwaker Gupta" <diwaker.lists@xxxxxxxxx>
Date: Fri, 1 Sep 2006 16:47:26 -0700
Cc: kanour <xen@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Sep 2006 16:48:09 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ShzIEUaiKzaP8EueYsmR9XWEmTi3c73XCRah4gv9hccYKKAzpj6IKYnqlxIihkCOFQSO/vuLIXUmqWppJYisLp9gl7tBGj7KYzYKrmk6hxH683sFXOdh3eM1Ee5Rdyq3Ls5fN2iH3o5c39eLWdjiF+1WxV+ApKtNLUkjSIJUYd4=
List-id: Xen user discussion <xen-users.lists.xensource.com>

Current source tarballs by default build only one kernel anyway, giving you
all drivers anywhere.


Thats not entirely correct. The tarballs will make a single kernel
yes, but most drivers are still compiled as modules. So you need to
make sure that the appropriate /lib/modules/2.6.xx-xen directory is
available in the VM file system as well, otherwise drivers compiled as
modules won't be found.

Diwaker
--
Web/Blog/Gallery: http://floatingsun.net/blog

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

Follow-Ups:
- RE: [Xen-users] Kernel drivers on domU
  - From: Steffen Heil

References:
- [Xen-users] Kernel drivers on domU
  - From: kanour
- RE: [Xen-users] Kernel drivers on domU
  - From: Steffen Heil

Prev by Date: [Xen-users] can't get network access from windows hvm
Next by Date: Re: [Xen-users] CPU intensive VM starves IO intensive VMs
Previous by thread: RE: [Xen-users] Kernel drivers on domU
Next by thread: RE: [Xen-users] Kernel drivers on domU
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.