NetBSD-Bugs archive

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

Re: kern/37996: NetBSD does not scan PCI-Express busses for devices

The following reply was made to PR port-xen/37996; it has been noted by GNATS.

From: "Christoph Egger" <>
Subject: Re: kern/37996: NetBSD does not scan PCI-Express busses for devices
Date: Mon, 11 Feb 2008 15:51:40 +0100

 > [cc to Manuel because this is a xen specific problem]
 > said:
 > > The boot messages really look different now: 
 > > [...]
 > > pci9 at hypervisor0 bus 128hypervisor0: added to list as bus 128
 > good -- that's the second primary PCI bus as in your original mail:
 > > mpacpi: found root PCI bus 128 at level 1
 > So it seems to work as expexted.
 > > So can you add "options ACPI_SCANPCI" to
 > > sys/arch/amd64/conf/XEN3_DOM0 and commit, please?
 > I'll leave this to the maintainer.
 Ok. Manuel, please commit :)
 > > Maybe you should also do that for sys/arch/amd64/conf/GENERIC.
 > It is already there.
 > > there is a driver bug:
 > > nfs_boot: trying static
 > > nfs_boot: getfh - no pathname
 > I don't know much about xen, but here I'd suspect the code
 > which compares device names with xen command line arguments, in
 > sys/arch/xen/x86/autoconf.c:device_register().
 That's right. I figured that out before I read your mail:
 On this machine, nfs_bootstatic() does NOT call
 dom0_bootstatic_callback(), while the other does.
 Looking into sys/arch/xen/x86/autoconf.c:device_register(),
 nfs_bootstatic_callback is only set if bootdev matches something.
 And bootdev is set to ex0 to boot on the other machine.
 With bootdev set to bnx1 makes NFS boot actually working.
 So I have to switch forth and back in order to boot a Xen-Dom0
 on my test machines. Sorry for the noise.
 The DHCP does not deliver the nfsroot ip and mount-path information, so I have 
to stick on static nfs boot and having a boot menu entry for each machine... 
only to twiddle with slightly different kernel parameters - very inflexible and 
 Isn't it possible to use something flexible like this:
 bootdev=nfs ip=dhcp nfsroot=<nfs-server-ip>:<path>
 That way, bootdev is independent from the network device,
 NetBSD knows to use nfs as filesystem rather asking me for it
 (or trying autodetection) and
 NetBSD will take nfsroot information via nfs-static and ask
 DHCP for the other required information (ip, gw, netmask).

Home | Main Index | Thread Index | Old Index