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

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


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Williamson, Alex \(Linux Kernel Dev\)" <alex.williamson@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 16 Nov 2005 13:11:12 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 16 Nov 2005 05:11:08 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXqIzh/fhjFMu+FQGWj6zX5WUL5WgABRleAAAZ0+vAAAQKgwAAJJMJg
  • Thread-topic: [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


 


Rackspace

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