From: Jacob Gorm Hansen <jacobg@diku.dk>
To: "Neugebauer, Rolf" <rolf.neugebauer@intel.com>,
Xen-devel@lists.sourceforge.net
Subject: Re: Multiple priviliged domains
Date: Sun, 19 Dec 2004 15:52:33 +0100 [thread overview]
Message-ID: <41C595B1.7080903@diku.dk> (raw)
In-Reply-To: <39CC97884CA19A4D8D6296FE94357BCB01252EBD@swsmsx404>
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/
next prev parent reply other threads:[~2004-12-19 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 21:44 Multiple priviliged domains Neugebauer, Rolf
2004-12-19 14:52 ` Jacob Gorm Hansen [this message]
2004-12-19 22:29 ` Ian Pratt
-- strict thread matches above, loose matches on Subject: below --
2004-12-19 5:52 John L Griffin
2004-12-19 9:22 ` Ian Pratt
2004-12-19 14:02 ` Jan Kundrát
2004-12-19 17:05 ` Bin Ren
2004-12-19 18:25 ` Mark Williamson
2004-12-19 11:52 ` Jacob Gorm Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C595B1.7080903@diku.dk \
--to=jacobg@diku.dk \
--cc=Xen-devel@lists.sourceforge.net \
--cc=rolf.neugebauer@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.