On 06/02/2012 17:33, Rick Miller wrote:
2) do you fetch the kernel successfully?
When using tftp, The kernel and kernel modules are fetched before the memory
file system, so do pxeboot fetch the kernel but not the mfsroot?
The reason for these questions is that your problem may be with the kernel
and kernel modules and not pxeboot. Just to be sure.
I see what you are saying. We will have to look at the packet
captures to make that determination.
The target system loads pxeboot.bs and consequently requests the
following files:
/boot/boot.4th (which it does not find)
/boot/loader.rc
/boot/loader.4th
/boot/support.4th
/boot/defaults/loader.conf
/boot/device.hints
/boot/loader.conf
It is at this point where the failure occurs. The contents of loader.conf are:
mfsroot_load="YES"
mfsroot_type="mfs_root"
mfsroot_name="/boot/mfsroot"
Does this seem consistent with what you were theorizing that it's the
kernel that has the problem with vlan tagging and not pxeboot.bs?
See the other mail, the way pxeboot works IIRC, is that first the
pxeboot is fetched using tftp, the pxeboot is given the next server and
will fetch the kernel, modules and other files from /boot/ on that
server, (path respective to the root of the tftp dir).
The kernel loads and will then fetch the mfsroot file. As mentioned, by
default this is done using nfs, and nfs is assumed if the kernel
supports nfs, even if it only fetches one file. This I understand has to
be this way since the network configuration set with dhcp does not
specify the protocol.
So, if your kernel supports nfs it will not use tftp and hence fail.
The details are somewhat distant to me, it's been some time since I
messsed arround with this.
hope this helps.
BR, Erik
--
M: +34 666 334 818
T: +34 915 211 157
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
