Ive been on vacation for the past 8 days just got home but couldn’t sign in to ipxe before we left for vacation. If there is someone who can help plz reach out and Ill be online again tomorrow. Just checking emails real quick tonight as my phone was lost\stolen while we were gone.
Thank you Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: ipxe-devel-boun...@lists.ipxe.org <ipxe-devel-boun...@lists.ipxe.org> on behalf of Johannes Thoma <johan...@johannesthoma.com> Sent: Wednesday, June 12, 2019 2:23:19 PM To: ipxe-devel@lists.ipxe.org Subject: Re: [ipxe-devel] Testing for sanboot feature on DHCP server Hi Oliver, Thank you for your response. Am 12.06.19 um 20:46 schrieb Oliver Rath: Hi Johannes! I see 3 possibilities: 1. 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 I already did that but I had to type the commands over the keyboard .. what I wanted to do is to automate this via DHCP. In order to do so I need to tell the VirtualBox iPXE (without sanboot) from my iPXE (with sanboot and some other options). Else there is either an error message from the VirtualBox iPXE (because it does not understand sanboot) or an endless boot loop (iPXE loading my self-compiled iPXE in a loop). 1. 2. You could try to replace the ipxe code of virtual box, but there seems to be a size issue I think I will try that. The solution is then specific to VirtualBox, but so is the problem, so I think "it works for me" ;) 1. You can change to qemu (qemu-system-x86_64). Qemu has already an ipxe version on board, which supports http-boot. Good to know. That will make things much easier for those running WinDRBD with a Linux Server. Hth, Yes it did, Best wishes, - Johannes Oliver Am 12.06.19 um 18:31 schrieb Johannes Thoma: Dear iPXE list, I am using VirtualBox in order to boot diskless clients via WinDRBD (www.github.com/LINBIT/WinDRBD<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.github.com%2FLINBIT%2FWinDRBD&data=02%7C01%7C%7Ceaf15caa70d84280f40508d6ef6b6e53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636959642024130209&sdata=bcX5uPXtm7wHsHBZbkw0H2D7I9aFCZ8Wm39PD4WSiLQ%3D&reserved=0>). Virtual box has a built in iPXE variant which does not support sanboot. We need sanboot in order to boot and load Windows drivers until WinDRBD takes over. This is currently done via http and a small cgi script on the server that basically does a dd (disk dump) to stdout. Is there a way to test if a iPXE variant supports sanboot?: what I would like to do is something like (in /etc/dhcpd.conf): if exists ipxe.sanboot-feature { # sanboot enabled iPXE already running filename ""; option root-path "http://192.168.56.102/cgi-bin/drbd.cgi";<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2F192.168.56.102%2Fcgi-bin%2Fdrbd.cgi&data=02%7C01%7C%7Ceaf15caa70d84280f40508d6ef6b6e53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636959642024140221&sdata=ykgBAUc97dx9JRzPctAUBSLqgDJ0kaAaueLEyVQYO5Q%3D&reserved=0>; } else { # sanboot enabled iPXE not running yet, load it via boot command filename "http://192.168.56.102/~johannes/ipxe/ipxework.pxe";<https://nam02.safelinks.protection.outlook.com/?url=http:%2F%2F192.168.56.102%2F~johannes%2Fipxe%2Fipxework.pxe&data=02%7C01%7C%7Ceaf15caa70d84280f40508d6ef6b6e53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636959642024160243&sdata=ktCjt008buE7IeOK2MOqZ%2FnjG3gzvjyzkJ6iLEBxPs8%3D&reserved=0>; } However all features I've tried are either disabled on both iPXE builds or enabled in both iPXE builds, thereby I can't distinguish between them. I am using isc-dhcp-server on Linux. The DHCP server that comes with VirtualBox is disabled. Thanks for any insights, Kind regards, - Johannes _______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org<mailto:ipxe-devel@lists.ipxe.org> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ipxe.org%2Fmailman%2Flistinfo.cgi%2Fipxe-devel&data=02%7C01%7C%7Ceaf15caa70d84280f40508d6ef6b6e53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636959642024180248&sdata=DbbE3CVHQDKvYGSbSD7t4C%2BIEEZ9AZjQFHzzJQLs6tE%3D&reserved=0> _______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org<mailto:ipxe-devel@lists.ipxe.org> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ipxe.org%2Fmailman%2Flistinfo.cgi%2Fipxe-devel&data=02%7C01%7C%7Ceaf15caa70d84280f40508d6ef6b6e53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636959642024190259&sdata=0G2Fqh8RKOfcT89is3rfdhj9l2ZZyRdkwdZDhZHsa4Y%3D&reserved=0>
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
