Re: [Xen-devel] SOLVED - domain that won't boot!!!

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

> You are supposed to be able to run driver domains: Those have physical
> access to network and/or block devices and export them to the other
> domains.

That would be a sensible time to use these configuration options in principle.

> These driver domains of course need physical access to the devices while
> they should not be a priviledged guest.

Remember that what you compile into the kernel is independent of the domain's 
privilege.  If you switch on the "privileged guest" option and run it in an 
unprivileged domain then the privileged driver just won't work.

In 2.0, driver domains are actually privileged anyway.  Reducing their 
privilege level will likely be part of later security / robustness work.

Cheers,
Mark

> I worked around the unbootable kernel problem by manually editing the
> .config file to make sure no non-xen consoles are included in the domU
> kernel.
>
> Regards,
> Tobias
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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