startup failures (4.0, xen 3.1)

[Greg Troxel <gdt%ir.bbn.com@localhost>]

I have a box that was running older versions of NetBSD/i386 and xen2.  I
just updated it to 4.0_STABLE (build from 9/2), both the dom0 and the
single domU.  Then I updated pkgsrc on both dom0 and domU and rebuilt
with pkg_rolling-replace.  I then switched to xen3 (3.1, using xentools3
and xenkernel3 packages).

I had not updated /etc right - I thought the box was more set up for
etcmanage than it was, but I straightened that out, and also MAKEDEV<
and ran "./MAKEDEV xen".

Things are mostly ok, but xend does not start up correctly on boot.  I
have xend=YES, xenbackendd=YES, and xendomains=domUname.  If I restart
xend after boot, and then start xenbackendd and xendomains, my domU
comes up.

After booting, ps shows:

root    375  0.0  2.7 7124  6980 ?     Ia    7:53PM 0:00.11 
/usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start 
root    377  0.0  1.3 6728  3268 ?     I     7:53PM 0:00.00 
/usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start 

and does not show xenstored or xenconsoled.  In this state, xenbackend
apparently won't start (doing "/etc/rc.d/xenbackendd start" gets a
complaint) and "xm list" fails.

Then, if I "/etc/rc.d/xend restart", I find the missing processes:

root     441  0.0  1.3 6732  3284 ?     S     7:55PM 0:00.00 
/usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start 
root    1016  1.5  0.4 2280  1104 ?     S     7:55PM 0:00.04 xenstored 
--pid-file /var/run/xenstore.pid 
root    1061  0.0  0.3 2084   900 ?     Sa    7:55PM 0:00.00 xenconsoled 
root    1083  5.6  3.2 8060  8460 ?     Sa    7:55PM 0:00.29 
/usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start 

and after "/etc/rc.d/xenbackendd start" and "/etc/rc.d/xendomains start"
all is well:

root      67  0.0  0.4 2076   976 ?     Ssa   7:55PM 0:00.00 
/usr/pkg/sbin/xenbackendd 

Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   256     1     r-----     11.2
domUname                                     1   512     1     -b----      1.1


Any clues?  It almost feels like PATH is not set right on boot, but
surely the rc.d scripts must get this right.