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

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

On Saturday, 14. May 2005 12:45, James Harper wrote:
> It seems that if I specify CONFIG_XEN_PHYSDEV_ACCESS without
> CONFIG_XEN_PRIVILEGED_GUEST, I get an unbootable kernel. Is there any
> case where PHYSDEV without PRIV would be useful? Maybe it shouldn't be
> an allowed combination of options.

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.

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

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.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.