This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: "Stefan Berger" <stefanb@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Experimental PCI Emulation Layer for XEN x86(32)
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
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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. 


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>