<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Oliver,<br>
<br>
Thank you for your response.<br>
<br>
<div class="moz-cite-prefix">Am 12.06.19 um 20:46 schrieb Oliver
Rath:<br>
</div>
<blockquote type="cite"
cite="mid:2afe991c-1a7b-6d8d-d851-2d1fe0ef96cf@greenunit.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi Johannes!</p>
<p>I see 3 possibilities:</p>
<ol>
<li>You can chainload an ipxe variant, which supports. You can
build an undionly.kpxe or (for uefi) ipxe.efi image with the
needed code. The ipxe code of virtualbox is made as much as
possible to work like pxe, so the dhcp filename option (for
tftp load) should work<br>
</li>
</ol>
</blockquote>
I already did that but I had to type the commands over the keyboard
.. what I<br>
wanted to do is to automate this via DHCP. In order to do so I need
to <br>
tell the VirtualBox iPXE (without sanboot) from my iPXE (with
sanboot and<br>
some other options). Else there is either an error message from the
VirtualBox<br>
iPXE (because it does not understand sanboot) or an endless boot
loop<br>
(iPXE loading my self-compiled iPXE in a loop).<br>
<blockquote type="cite"
cite="mid:2afe991c-1a7b-6d8d-d851-2d1fe0ef96cf@greenunit.de">
<ol>
<li> </li>
<li>You could try to replace the ipxe code of virtual box, but
there seems to be a size issue</li>
</ol>
</blockquote>
I think I will try that. The solution is then specific to
VirtualBox, but so is the problem, <br>
so I think "it works for me" ;)<br>
<blockquote type="cite"
cite="mid:2afe991c-1a7b-6d8d-d851-2d1fe0ef96cf@greenunit.de">
<ol>
<li>You can change to qemu (qemu-system-x86_64). Qemu has
already an ipxe version on board, which supports http-boot.</li>
</ol>
</blockquote>
Good to know. That will make things much easier for those running
WinDRBD<br>
with a Linux Server.<br>
<br>
<blockquote type="cite"
cite="mid:2afe991c-1a7b-6d8d-d851-2d1fe0ef96cf@greenunit.de">
<ol>
</ol>
<p>Hth,</p>
</blockquote>
Yes it did, <br>
<br>
Best wishes, <br>
<br>
- Johannes<br>
<blockquote type="cite"
cite="mid:2afe991c-1a7b-6d8d-d851-2d1fe0ef96cf@greenunit.de">
<p>Oliver</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 12.06.19 um 18:31 schrieb Johannes
Thoma:<br>
</div>
<blockquote type="cite"
cite="mid:c1998c19-4629-0ac5-930d-da59e5a17b26@johannesthoma.com">
Dear iPXE list,<br>
<br>
I am using VirtualBox in order to boot diskless clients via
WinDRBD<br>
(<a class="moz-txt-link-abbreviated"
href="http://www.github.com/LINBIT/WinDRBD"
moz-do-not-send="true">www.github.com/LINBIT/WinDRBD</a>).
Virtual box has a built in iPXE<br>
variant which does not support sanboot. We need sanboot in order<br>
to boot and load Windows drivers until WinDRBD takes over. This<br>
is currently done via http and a small cgi script on the server
that<br>
basically does a dd (disk dump) to stdout.<br>
<br>
Is there a way to test if a iPXE variant supports sanboot?: what
I would<br>
like to do is something like (in /etc/dhcpd.conf):<br>
<br>
if exists ipxe.sanboot-feature {<br>
# sanboot enabled iPXE already running<br>
filename "";<br>
option root-path <a class="moz-txt-link-rfc2396E"
href="http://192.168.56.102/cgi-bin/drbd.cgi"
moz-do-not-send="true">"http://192.168.56.102/cgi-bin/drbd.cgi"</a>;<br>
} else {<br>
# sanboot enabled iPXE not running yet, load it via boot command<br>
filename <a class="moz-txt-link-rfc2396E"
href="http://192.168.56.102/~johannes/ipxe/ipxework.pxe"
moz-do-not-send="true">"http://192.168.56.102/~johannes/ipxe/ipxework.pxe"</a>;<br>
}<br>
<br>
However all features I've tried are either disabled on both iPXE
builds<br>
or enabled in both iPXE builds, thereby I can't distinguish
between<br>
them.<br>
<br>
I am using isc-dhcp-server on Linux. The DHCP server that comes
with<br>
VirtualBox is disabled.<br>
<br>
Thanks for any insights, <br>
<br>
Kind regards, <br>
<br>
- Johannes<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ipxe-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipxe-devel@lists.ipxe.org" moz-do-not-send="true">ipxe-devel@lists.ipxe.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" moz-do-not-send="true">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ipxe-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>