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

RE: [Xen-devel] Experimental PCI Emulation Layer for XEN x86(32)


  • To: "Stefan Berger" <stefanb@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 19 Aug 2005 17:47:07 +0100
  • Delivery-date: Fri, 19 Aug 2005 16:45:38 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWk25nzFTgfawquRqiRvYRWFyA77QAAcERg
  • Thread-topic: [Xen-devel] Experimental PCI Emulation Layer for XEN x86(32)

> -  The best: Running a domain 0 kernel as a user domain 
> kernel also works ! The bootup messages (dmesg) can be seen 
> under (**) below
>    - With some further exploration this could be leading to a 
> unified build process and kernel for domain 0 and user 
> domains which I think would be 'good'.

? You can already use a xen0 kernel as a xenU kernel just fine. That's
what al distros do.

Having two kernels is just for developer's convenience.

See the -xen default config which compiles everything as modules. 

Ian

_______________________________________________
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®.