Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 06 Aug 2011 08:15:22 -0700
From:      Colin Percival <cperciva@freebsd.org>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org>, Sean Bruno <seanbru@yahoo-inc.com>
Subject:   Re: BETA-1 NFS not working, Xen PV i386
Message-ID:  <4E3D5A8A.4070104@freebsd.org>
In-Reply-To: <alpine.BSF.2.00.1108061516510.22650@fledge.watson.org>
References:  <1311986628.2531.15.camel@hitfishpass-lx.corp.yahoo.com> <alpine.BSF.2.00.1108061516510.22650@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08/06/11 07:17, Robert Watson wrote:
> On Fri, 29 Jul 2011, Sean Bruno wrote:
>> Doesn't make a lot of sense here, but building with the i386 XEN
>> kernel config yields the following boot up in PV mode.
>>
>> Odd ... it looks like i386/XEN needs:
>>
>> options         NFSCL                   # New Network Filesystem Client
> 
> Yes -- in general, I consider the existence of a XEN configuration that
> isn't derived from "include GENERIC" to be a mistake.  However, there's
> a somewhat tricky balance in terms of enumerating device drivers, etc. 
> Someone(tm) needs to sync the XEN kernel to GENERIC before we ship to
> make sure it's generally in line, but in the long term it will remain a
> maintenance problem.

I don't think XEN should be derived from GENERIC as it currently exists; there
is an awful lot of stuff in GENERIC which doesn't make any sense to have in a
PV environment.  Maybe if GENERIC was split into separate "physical" and
"logical" sets of options (so that XEN could suck in stuff like nfs without
having drivers for hardware it will never see) the problems would be less?

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E3D5A8A.4070104>