Hey Ron, I’d be happy to see you /etc/network/interfaces files =) Cheers, Chris > On 26 Jan 2016, at 23:34, Ronald Steele <rste...@adaptivemethods.com> wrote: > > I did screen shots of my config and put them on Dropbox so as to not spam the > list with them. I’ve never tried this before, so let me know > if it doesn’t work. > https://www.dropbox.com/sh/lw07igfr4w9tkyn/AABW4e_A10VWc0NtzkWEJLHma?dl=0 > <https://www.dropbox.com/sh/lw07igfr4w9tkyn/AABW4e_A10VWc0NtzkWEJLHma?dl=0> > > I don’t know why you would not want to get to fai sever from the network. It > is much easier to ssh to from a host terminal window than use the dodgy > terminal emulation provided by VB. At any rate, you normally configure a VB > instance with a network interface of some sort and in my very > painful experience trying to get PXE booting to work, you must have a bridged > network connection for the fai server or you won’t be PXE booting. > And the network connection of the host must be wired. I know this doesn’t > seem to make sense, but there are apparently hardware issues at work. > Others may well have a different solution, I don’t claim expertise, I just > know what I got to work. I’d love the hear alternatives as I’m not totally > comfortable > with why this works. > > Good luck and please let me know if you get it to work, or if you can’t get > to my dropbox. > > Ron > > >> On Jan 26, 2016, at 4:18 PM, Christian Linden <lindoma...@gmail.com >> <mailto:lindoma...@gmail.com>> wrote: >> >> Hi Ronald, >> >> doesn’t work here.. for the pxeboot it’s not necessary to get on the >> fai-boxes from the VB host.. hence the internal network should be >> sufficient.. >> But.. for the case VB needs your setup for whatever reason.. could you >> please copy & paste your interface configs pls? >> >> Thank you! >> Chris >> >>> On 26 Jan 2016, at 17:12, Ronald Steele <rste...@adaptivemethods.com >>> <mailto:rste...@adaptivemethods.com>> wrote: >>> >>> I’m working with this setup right now. TFTP seems to be working fine. >>> I’m using “Internal Network” for the installation clients. The fai server >>> has two networks, the same “Internal Network” to boot the clients on and >>> bridged network to get to it from the VB host. >>> You MUST have a wired, not WI-FI network because the bridged network will >>> not work over WI-FI for most if not all WI-FI chips. I’ve never gotten it >>> to work using a NATed network to the host, and I don’t know why. >>> Also, my VB host is a Mac Mini running the latest OSX. >>> Make sure you are running a VB version 5+ as it’s MUCH faster than earlier >>> versions. >>> >>> Host this helps. >>> >>> Ron >>> >>> Now is someone could tell me why the client boot fails on the first boot >>> from the hard drive, that would be great. >>> >>> >>>> On Jan 26, 2016, at 8:22 AM, Sven Schumacher >>>> <schumac...@tfd.uni-hannover.de <mailto:schumac...@tfd.uni-hannover.de>> >>>> wrote: >>>> >>>> You might try to change the type of network card, which is virtually >>>> simulated by Virtualbox... >>>> >>>> Am 26.01.2016 um 14:19 schrieb Christian Linden: >>>>> Hi all, >>>>> >>>>> Thomas went through all steps with me for a couple of days.. and we both >>>>> come the conclusion >>>>> that Virtual Box must be the culprit. >>>>> I’ve a faiserver as guest and want to pxe boot another guest; the client >>>>> gets an IP address but not the pxelinux.0 >>>>> Connecting locally on the faiserver with a tftp client the download >>>>> works, hence the tftp server works. >>>>> >>>>> Does anyone know about this problem with/among VBox guests among each >>>>> other? >>>>> >>>>> I checked all kinds of network VBox offers: Nat, Nat network, Internal >>>>> Network, Bridged.. no way. >>>>> >>>>> Thanks so much! >>>>> >>>>> Best, >>>>> Chris >>>>> >>>> >>>> >>>> -- >>>> Sven Schumacher - Systemadministrator Tel: (0511)762-2753 >>>> Leibniz Universitaet Hannover >>>> Institut für Turbomaschinen und Fluid-Dynamik - TFD >>>> Appelstraße 9 - 30167 Hannover >>>> Institut für Kraftwerkstechnik und Wärmeübertragung - IKW >>>> Callinstraße 36 - 30167 Hannover >>>> >>>> >>> >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
