From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: Multiple priviliged domains Date: Sun, 19 Dec 2004 15:52:33 +0100 Message-ID: <41C595B1.7080903@diku.dk> References: <39CC97884CA19A4D8D6296FE94357BCB01252EBD@swsmsx404> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <39CC97884CA19A4D8D6296FE94357BCB01252EBD@swsmsx404> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Neugebauer, Rolf" , Xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org Neugebauer, Rolf wrote: > Yes, but in 1.3 device drivers are still in Xen. In 2.0 device drivers > are run in a guest OS (which was what the original poster was looking > for). In order to boot dom0 in this model without physical device > drivers it would need a *really big* initrd (as Mark said) because it > would need to create other VMs from it to provide dom0 with virtual > devices. I'm not sure at all if xend supports this sort of setting. Yep, it seems I misunderstood the original poster's intention. I guess that in an ideal world every device would provide a Xen VM driver in its firmware, similar to how Open Firmware provides Forth drivers, if I understand that part correctly. But then there is the issue of how to upgrade drivers etc. Btw. I remember some discussion about wrapping NDIS drivers as Xen driver domains, did anyone every try doing that? Jacob ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/