From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Question: why pvops seldom build modules drivers Date: Thu, 08 Jul 2010 11:37:35 -0700 Message-ID: <4C361AEF.30009@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Liu, Jinsong" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 07/08/2010 04:10 AM, Liu, Jinsong wrote: > Recently I install pvops/xen at a new platform, > However, I meet troubles, it need manually enable&install some driver like Lsi scsi controller (to find root device which is a SAS disk connect to Lsi controller) & Intel 82576 nic to access network. > I check pvops .config, it seldom build module driver. > Just curious why pvops does so? it make trouble when install pvops at various platform ..., while at native linux it config most device driver as module. > I usually build modular kernels without problem. The tricky part is making sure all the right drivers end up in your initrd. What distro are you using? J