<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<div>Hi Shawn,</div>
<div><br>
</div>
<div>You need a special setup in your dhcp server to handle network booting. An alternative is to run a bootp server also. Search for 'bootp tftpd' and you'll get plenty of tutorials on both methods.</div>
<div><br>
</div>
<div>cheers,</div>
<div>Georgios</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:100%">Sent from Samsung mobile</div>
</div>
<br>
Shawn Furrow <sfurrow@vt.edu> wrote:<br>
<div>So I am still having trouble booting Barrelfish over tftp using a pxe server. I feel like I must be missing something in my understanding. My current set up is as follows:
<div><br>
</div>
<div>1. I have successfully built Barrelfish and ran 'make install' to create the 'barrelfish directory with all of the binaries</div>
<div>2. I have successfully installed GRUB 0.97 with the patch for my e1000 network card</div>
<div>3. I set up a tftp server on another machine in my lab's network</div>
<div>4. I copied the generated 'barrelfish' directory into my /var/lib/tftpboot directory for my tftp server</div>
<div>5. I created a menu.lst file and placed it in the /var/lib/tftpboot folder alongside the 'barrelfish' directory (I have included this file below)</div>
<div>6. I started the tftp server (which I have tested and can successfully transfer files to and from the /var/lib/tftpboot folder</div>
<div><br>
</div>
<div>When I startup the computer that I want to boot barrelfish on, I tell it to boot from the network. Then, I get a DHCP...., then the PXE53-No boot filename received.</div>
<div><br>
</div>
<div>I'm not sure what is going on. Does anyone know what I could be missing? I keep seeing a lot of guides refer to specifying the boot file name in a DHCP.conf file but I don't really know much about this. Here is my menu.lst file:</div>
<div><br>
</div>
<div><br>
</div>
<div>/--------------------------------------------------------------------------------------------------------------------------------------------------------------------------/</div>
<div>
<div>timeout 0</div>
<div><br>
</div>
<div># spawnd is used to control which cpus are booted</div>
<div>#</div>
<div># "spawnd boot" will use the skb and pci to figure out and</div>
<div># boot all cores in the machine</div>
<div>#</div>
<div># "spawnd boot bootapic-x86_64=1-5" will not use the skb and</div>
<div># boot the list of cores passed as argument.</div>
<div># The APIC id of the cores to boot should be specified.</div>
<div># This list may not include the bsp core id.</div>
<div><br>
</div>
<div>title Barrelfish</div>
<div>ifconfig --address=10.1.1.20 --server=10.1.1.21</div>
<div>root (nd)/tftpboot/barrelfish</div>
<div>kernel /x86_64/sbin/elver loglevel=4</div>
<div>module /x86_64/sbin/cpu loglevel=4</div>
<div>module /x86_64/sbin/init</div>
<div><br>
</div>
<div># Domains spawned by init</div>
<div>module /x86_64/sbin/mem_serv</div>
<div>module /x86_64/sbin/monitor</div>
<div><br>
</div>
<div># Special boot time domains spawned by monitor</div>
<div>module /x86_64/sbin/ramfsd boot</div>
<div>module /x86_64/sbin/skb boot</div>
<div>modulenounzip /skb_ramfs.cpio.gz nospawn</div>
<div>module /x86_64/sbin/kaluga boot</div>
<div>module /x86_64/sbin/acpi boot</div>
<div>module /x86_64/sbin/spawnd boot</div>
<div>#bootapic-x86_64=1-15</div>
<div>module /x86_64/sbin/startd boot</div>
<div>module /x86_64/sbin/routing_setup boot</div>
<div><br>
</div>
<div># Drivers</div>
<div>module /x86_64/sbin/pci auto</div>
<div>module /x86_64/sbin/ahcid auto</div>
<div>module /x86_64/sbin/rtl8029 auto</div>
<div>module /x86_64/sbin/e1000n auto</div>
<div>module /x86_64/sbin/NGD_mng auto</div>
<div>module /x86_64/sbin/netd auto</div>
<div><br>
</div>
<div># General user domains</div>
<div>module /x86_64/sbin/serial</div>
<div>module /x86_64/sbin/fish</div>
</div>
<div>/---------------------------------------------------------------------------------------------------------------------------------------------------------------------------/</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Shawn</div>
<div><br>
<br>
<div class="gmail_quote">On Wed, Jun 6, 2012 at 8:46 AM, Simon Peter <span dir="ltr">
<<a href="mailto:speter@inf.ethz.ch" target="_blank">speter@inf.ethz.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
In fact, if you use elver, no 64-bit patch is necessary. There is a patch for GRUB to support more network cards.<br>
<br>
Simon
<div class="im"><br>
<br>
On 05.06.2012 22:52, Georgios Varisteas wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div class="im">Hey Shawn,<br>
<br>
Actually it is not really a patch. GRUB supports network booting,<br>
although it is not part of its default compile configuration. You need<br>
to run '# configure --netboot' followed by more arguments that enable<br>
support for specific NICs. It is not recommended to just enable them all<br>
though. More on this in the README found in the netboot subfolder of the<br>
GRUB's tree. Also keep in mind that GRUB legacy is rather old code and<br>
wont compile with modern versions of GCC. Version 3.x is recommended but<br>
it might work with some early 4.x.<br>
<br>
Apart from this you do need a patch to enable support for a 64-bit<br>
kernel but it has nothing to do with PXE.<br>
<br>
Hope this helps<br>
<br>
regards,<br>
Georgios<br>
<br>
</div>
------------------------------<u></u>------------------------------<u></u>------------<br>
*From:* Shawn Furrow [<a href="mailto:sfurrow@vt.edu" target="_blank">sfurrow@vt.edu</a>]<br>
*Sent:* Tuesday, June 05, 2012 21:30<br>
*To:* <a href="mailto:barrelfish-users@lists.inf.ethz.ch" target="_blank">barrelfish-users@lists.inf.<u></u>ethz.ch</a><br>
*Subject:* [Barrelfish-users] Booting Barrelfish using TFTP - GRUB issues
<div class="im"><br>
<br>
Hey all,<br>
<br>
I am trying to boot Barrelfish over a TFTP server but I am having<br>
trouble with GRUB. From what I understand, I need GRUB Legacy (0.97)<br>
with a patch for PXE. From here, GRUB would chain-load Elver, and then<br>
Elver would boot Barrelfish. (Correct me if I am mistaken on this)<br>
However, I cannot get a patched version of GRUB 0.97 to install<br>
correctly to my hard drive. Has anyone gotten this method to work? If<br>
so, what was your environment and GRUB patches do you use?<br>
<br>
Thanks,<br>
Shawn<br>
<br>
--<br>
Virginia Tech<br>
Bradley Department of Electrical and Computer Engineering<br>
B.S. Electrical Engineering<br>
B.S. Computer Engineering<br>
<br>
<br>
<br>
</div>
______________________________<u></u>_________________<br>
Barrelfish-users mailing list<br>
<a href="mailto:Barrelfish-users@lists.inf.ethz.ch" target="_blank">Barrelfish-users@lists.inf.<u></u>ethz.ch</a><br>
<a href="https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users" target="_blank">https://lists.inf.ethz.ch/<u></u>mailman/listinfo/barrelfish-<u></u>users</a><br>
</blockquote>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Virginia Tech<br>
Bradley Department of Electrical and Computer Engineering<br>
B.S. Electrical Engineering</div>
<div>B.S. Computer Engineering</div>
<br>
</div>
</div>
</body>
</html>