Adapters 2-4 are grey/inactive.. I can’t enable/configure them =( Would need any vboxmanage add nic or similar..
> On 26 Jan 2016, at 17:38, Ronald Steele <rste...@adaptivemethods.com> wrote: > > In VB, select your fai server VM, the click on “Network”. VB is weird > because you have to click on the word “Network”, not on the icon. > This brings up the Networking menu. Between the menu bar at the top and the > particulars for the interface below is a line of adapters. > Just select “Adapter 1”, " Adapter 2” and configure away. > Note that you can change the MAC address here also, and for clients it mush > match what is in the dhcpd.conf and the boot config file in > /srv/tftp/fai/pxelinux.cfg > >> On Jan 26, 2016, at 11:30 AM, Christian Linden <lindoma...@gmail.com> wrote: >> >> Thank you all for your replies! =) >> >> I’m running 5.0.10 r104061 on latest OS X on MacBook Pro. >> Everything to see in syslog with -vvvv in the tftp options is nothing, just >> the dhcp info. >> daemon.log is silent as well. >> >> I think as well that there’s any conflict regarding the built in tftp server >> from vbox. >> >> But Ron, you are not fitting in the over all experience =) >> Prob I have is I just can choose one adapter in this box; there’s no add >> option I could see.. any hint? >> Adding it on the faiserver or via vbox? >> >> Thank you! >> >> Chris >> >> >>> On 26 Jan 2016, at 17:12, Ronald Steele <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> 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
