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

[Xen-users] Building kernels *within* a domU


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "john maclean" <jayeola@xxxxxxxxx>
  • Date: Fri, 22 Sep 2006 10:28:30 +0100
  • Delivery-date: Fri, 22 Sep 2006 02:29:17 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=YGPYYPbIftNNHZ8XK4A6Nokpb2aDhIBfqwxd35mtIEbiatJDizDknn+pi18RVx8YhvnNTsPhbny9rYM0nYvbqRV5g7ybmzOLMjmWbusDbkFUf34LHciwCAwF56jPyFOBf9kzGt2cKEKBs1MJmwsfR+BJgyEHyzDJwvHceaXjFm0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hey chaps,

I've been happily building and running images for my domUs and the
following occoured to me:- how does one build a kernel *within* a
domU? How would a domU specify which kernel to use when it's
hard-coded (see 4 below)? In summary:-

1) xen testing, 3.0.2-2
2) Using a single kernel (/boot/{config-2.6.16-xen, xen-3.0.2-2.gz} )
for all domains
3) I'm using file-based images, (created by dd)
4) The kernel for each domU is specified within /etc/xen/foo

--
John Maclean  - 07739 171 531
MSc (DIC)

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


 


Rackspace

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