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

[Xen-devel] Configuring kernels...


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Sam Johnston <samjie@xxxxxxxxx>
  • Date: Tue, 21 Jun 2005 19:47:25 +0100
  • Delivery-date: Tue, 21 Jun 2005 18:47:17 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hM3gqRw2PuUUIqc5FsL8YVBZXOLz2IsIcd1ziR7KuDeWATZMooR21qY5/auBtFEA0QALVyFQhmFaUrOgFlc4ts4a+ywdFY2cfXXDzUa0/HHfYw9LsQkjfMjNPPOjK4jsQ8/DYGaf6BpO3WPKRB3/FI/DJQa8bPXczas821mQ3jA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Evening all,

I'd like to configure a dom0 kernel based on the reasonably
comprehensive .config supplied by Debian (/boot/config-2.6.8-2-386).
If I apt-get install kernel-source-2.6.11 and untar it in /usr/src,
then run mkbuildtree on it, when I make xconfig|menuconfig most of the
drivers are unselected, which appears to be because PCI is unselected
(yet PCI *is* selected in the default dom0 config). Presumably I could
just enable PCI and the driver(s) in question (specifically ata_piix)
and go about business as usual, but I thought this behaviour was
curious and was wondering if it was intentional.

Also, I'm hoping to use the box as a workstation so I'd like to get
the bleeding edge i915 chipset up and running if Xen works with
agpgart etc. now.

Incidentally, the motivation for the recompile in the first place was
for root on LVM.

 - samj

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


 


Rackspace

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