RE: [Xen-ia64-devel] config files and dom0/domU

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

When I compiled a domU with CONFIG_XEN_PRIVILEGED_GUEST=n,
I got an error message and domU did not get to a shell prompt.
(I don't recall the error message other than it had something
to do with xenstore and console.)  When I recompiled domU
with CONFIG_XEN_PRIVILEGED_GUEST=y, the problem went away.

I looked at the code where there is ifdef CONFIG_XEN_PRIV...
and I didn't see anything that should cause this problem,
but that is the result I saw.

I am OK with any default values, as long as it is possible
to build dom0 and domU without user intervention.  I would
also like to preserve the capability that a single binary
can be used for both dom0 and domU (which is true for
Xen/x86); the only thing that makes this impossible right
now is CONFIG_VT.

Dan

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Tuesday, November 15, 2005 10:11 PM
> To: Magenheimer, Dan (HP Labs Fort Collins); Williamson, Alex 
> (Linux Kernel Dev)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] config files and dom0/domU
> 
> Could you please say more about your finding, like which part 
> of console frontend requiring CONFIG_XEN_PRIVILEGED_GUEST on? 
> I didn't find yet.
> 
> BTW, I'd like to see default value is 'n' as:
> config XEN_PRIVILEGED_GUEST
> -       bool
> +       bool "Privileged Guest"
>         default n     <------------------------
> 
> That can promise no user intervention required when make 
> oldconfig with proper xen0/xenU config file. The reason is 
> absence of explicit symbol to mark an item off in .config 
> file ("XXX is not set" still goes to default option of that 
> item). If default to 'y' here, actually user will always be 
> prompt to choose n/y/m when make oldconfig for xenU and 
> definitely we don't want that. ;-)
> 
> Thanks,
> Kevin
> 
> >-----Original Message-----
> >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Magenheimer,
> >Dan (HP Labs Fort Collins)
> >Sent: 2005å11æ16æ 8:41
> >To: Williamson, Alex (Linux Kernel Dev)
> >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: RE: [Xen-ia64-devel] config files and dom0/domU
> >
> >Oops, typo.  That should read "console" frontend.
> >
> >> -----Original Message-----
> >> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> >> Of Magenheimer, Dan (HP Labs Fort Collins)
> >> Sent: Tuesday, November 15, 2005 5:13 PM
> >> To: Williamson, Alex (Linux Kernel Dev)
> >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> Subject: RE: [Xen-ia64-devel] config files and dom0/domU
> >>
> >> Hmmm... unfortunately it appears that 
> CONFIG_XEN_PRIVILEGED_GUEST is
> >> required in domU for a guest block frontend to communicate
> >> with a privileged guest backend.  This is certainly unexpected.
> >>
> >> > -----Original Message-----
> >> > From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> > [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> >> > Of Magenheimer, Dan (HP Labs Fort Collins)
> >> > Sent: Tuesday, November 15, 2005 2:08 PM
> >> > To: Williamson, Alex (Linux Kernel Dev)
> >> > Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > Subject: RE: [Xen-ia64-devel] config files and dom0/domU
> >> >
> >> > >    Right, XEN_PRIVILEGED_GUEST is always on right now because
> >> > > there's no
> >> > > prompt to change it.  To fix that, do this:
> >> >
> >> > Cool!  That fixes it.  I was unaware that the prompt had
> >> > any use other than in the user interface so was completely
> >> > ignoring it.
> >> >
> >> > Thanks very much!
> >> > Dan
> >> >
> >> > _______________________________________________
> >> > Xen-ia64-devel mailing list
> >> > Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > http://lists.xensource.com/xen-ia64-devel
> >> >
> >>
> >> _______________________________________________
> >> Xen-ia64-devel mailing list
> >> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-ia64-devel
> >>
> >
> >_______________________________________________
> >Xen-ia64-devel mailing list
> >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-ia64-devel
> 

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