Find the answer to your Linux question:
Results 1 to 4 of 4
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    PXE diskless boot fails


    I am trying to setup a server for a diskless boot of a computer class (with ubuntu)
    I followed the guidelines in

    I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine (using VMWare fusion) that does the net boot. I have additional VM on it with ubuntu 10.4 installed on it for other tests. The server runs ubuntu 10.4 server and the client image for network boot is ubuntu 10.4 desktop that I previously prepared as explained in the link above on a VM on my laptop.

    The problem is that after loading the kernel and initrd (and outputting many things that I can't read because it happens too fast) I get the following error:
    IP-Config: eth0 hardware address 00:0c:29:79:86:c1 mtu 1500 DHCP
    [    2.775718] eth0: link up
    IP-Config: no response after 60 secs - giving up
    /init: .: line 3: can't open /tmp/net-eth0.conf
    [   69.073555] Kernel panic- not syncing" Attempted to kill init!
    [   69.073859] Pid: 1, comm: init Not tainted 2.6.32-22-generic #35-Ubuntu
    < call trace - if it can help I can grab a screenshot >
    I thought it means that the NFS is not accessible but I was able to mount it and access its files from the other VM so it is not the problem.

    I have no idea what this error practically means, could not find a good answer in google...

    Anyone can help?


  2. #2
    Linux Guru coopstah13's Avatar
    Join Date
    Nov 2007
    NH, USA
    can you post your config file on the pxe server?

  3. #3
    Which one of them?

    Here is the DHCP config file:
    allow booting;
    allow bootp;
    subnet netmask {
      option broadcast-address;
      option routers;
      option domain-name-servers;
      filename "/pxelinux.0";
    host pxe_client {
      hardware ethernet 00:0C:29:79:86:C1;

  4. $spacer_open
  5. #4
    I've got a tiny progress: found that the system requests DHCP again after initial PXE DHCP step - just before loading NFS. Problem is that the DHCP server, for some reason, does not answer these later requests.
    Requests have the same MAC address but their length is different: the initial (answered) requests are of length 548 and the latter (unanswered) are only 271.

    Any idea why my DHCP server does not like these requests?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts