From: Jeff D. <jd...@ka...> - 2002-10-31 20:30:25
|
ba...@sa... said: > I am trying to boot diskless UML clients from a DHCP server using NFS > for the root file system. My network is entirely vitual, using > uml_switch as the connection medium. Do you know how to do this with a physical box? There is nothing UML-specific involved except that you have to give the ethernet devices MACs on the command line. From hazy memory, you have to configure the IP PNP stuff, which you did provide a MAC to eth0, which you did the ip= line has to request dhcp, which you didn't Basically, it looks like you need to read dhcp docs or something. Jeff |
From: Fisher, B. A <ba...@sa...> - 2002-10-31 20:44:16
|
Actually, I have this same client and server working quite well with BOOTP, TFTP, DHCP, and NFS Root through VMWare. I quite well understand how DHCP "typically" works, you'll notice that my "Script 1" has "ip=bootp" which instructs the kernel to query a BOOTP server (nowadays a service provided by DHCP servers) for it's IP information. The problem I see is that IP-Config is trying to hook up to a device to query the BOOTP server, but no devices have been initialized by the UML kernel. While I do provide an ethernet address on the UML command line, it doesn't seem to be initializing this device before IP-Config (ic_open_devs(), net/ipv4/ipconfig.c). -----Original Message----- From: Jeff Dike [mailto:jd...@ka...] Sent: Thursday, October 31, 2002 1:33 PM To: Fisher, Brice A; 'use...@li...' Subject: Re: [uml-user] DHCP and NSF Root in a virtual UML network ba...@sa... said: > I am trying to boot diskless UML clients from a DHCP server using NFS > for the root file system. My network is entirely vitual, using > uml_switch as the connection medium. Do you know how to do this with a physical box? There is nothing UML-specific involved except that you have to give the ethernet devices MACs on the command line. From hazy memory, you have to configure the IP PNP stuff, which you did provide a MAC to eth0, which you did the ip= line has to request dhcp, which you didn't Basically, it looks like you need to read dhcp docs or something. Jeff |
From: Jeff D. <jd...@ka...> - 2002-10-31 22:17:58
|
ba...@sa... said: > you'll notice that my "Script 1" has "ip=bootp" which instructs the > kernel to query a BOOTP server Hmmm, I didn't read that one because I thought I saw an obvious omission. I can't for the life of me remember what it was. So, that looks right, and this bit IP-Config: No network devices available. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Initializing software serial port version 1 Netdevice 0 (00:50:56:7c:9d:ee) : daemon backend (uml_switch version 3) - unix:/tmp/uml.ctl seems to indicate that we have an init ordering problem between the pnp ip code and the UML eth driver. Not sure what to do about it, but the diagnosis seems pretty clear. Jeff |
From: Fisher, B. A <ba...@sa...> - 2002-11-01 19:26:46
|
I got it to work by applying the first part of Chris Wilson's patch (I wasn't interested in the other problems he was addressing). In arch/um/Makefile I separated the LIBS line into a DRIVERS and CORE_FILES line to affect the link order of the build. #LIBS += $(shell [ -e $(ARCH_DIR)/fs/fs.o ] && echo $(ARCH_DIR)/fs/fs.o) \ # $(ARCH_DIR)/kernel/um.o $(ARCH_DIR)/drivers/drivers.o \ # $(ARCH_DIR)/sys-$(SUBARCH)/sys.o $(ARCH_DIR)/os/os.o DRIVERS += $(shell [ -e $(ARCH_DIR)/fs/fs.o ] && echo $(ARCH_DIR)/fs/fs.o) \ $(ARCH_DIR)/drivers/drivers.o CORE_FILES += $(ARCH_DIR)/kernel/um.o $(ARCH_DIR)/sys-$(SUBARCH)/sys.o \ $(ARCH_DIR)/os/os.o I know from Chris' thread that this isn't your preferred solution, but it works. -----Original Message----- From: Jeff Dike [mailto:jd...@ka...] Sent: Thursday, October 31, 2002 3:20 PM To: Fisher, Brice A; 'use...@li...' Subject: Re: [uml-user] DHCP and NSF Root in a virtual UML network ba...@sa... said: > you'll notice that my "Script 1" has "ip=bootp" which instructs the > kernel to query a BOOTP server Hmmm, I didn't read that one because I thought I saw an obvious omission. I can't for the life of me remember what it was. So, that looks right, and this bit IP-Config: No network devices available. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Initializing software serial port version 1 Netdevice 0 (00:50:56:7c:9d:ee) : daemon backend (uml_switch version 3) - unix:/tmp/uml.ctl seems to indicate that we have an init ordering problem between the pnp ip code and the UML eth driver. Not sure what to do about it, but the diagnosis seems pretty clear. Jeff |
From: Jeff D. <jd...@ka...> - 2002-11-01 19:39:02
|
ba...@sa... said: > I know from Chris' thread that this isn't your preferred solution, > but it works. Yup, that fiddles the initcall ordering to come out right. It still sucks though :-) Jeff |
From: Jeff D. <jd...@ka...> - 2002-11-04 04:56:45
|
ba...@sa... said: > In arch/um/Makefile I separated the LIBS line into a DRIVERS and > CORE_FILES line to affect the link order of the build. I still hate this, but I applied it anyway. Sigh. Jeff |