Re: No pxe boot on virtual box guests

Good checks, Ron. Yes, no grub and the WARNING about removing it from the installation list makes sense. If I just boot the VM I get the hanging terminal window with the cursor in the upper left corner. The int18 error comes up if I go into the boot options on boot (F12) and chose net-boot/LAN.

Re: No pxe boot on virtual box guests

I’ve been playing around with it some more. I mounted the (virtual) disk from the failed install onto FAI server to take a look at it. There is nothing in /boot. I’m guessing grub didn’t get installed either. Oddly, I’m no longer getting the int18 error message. The VM just pops up a terminal

Re: No pxe boot on virtual box guests

Hi Steven, yes I did, I’m on latest Vbox Version 5.0.14 r105127 and ExpPack as mentioned; it’s the same number. PXE works as the FAI installation works. It’s the first reboot after the installation where this problem comes up. Best, Chris > On 09 Feb 2016, at 07:27, Steven Wend wrote: > > H

Re: No pxe boot on virtual box guests

Hi Chris, did you install the Virtual Box's Expansionpack. Virtual Box is not able to handle PXE without the Expansionpack (https://www.virtualbox.org/manual/ch01.html#intro-installing). http://download.virtualbox.org/virtualbox/5.0.14/Oracle_VM_VirtualBox_Extension_Pack-5.0.14-105127.vbox-extpac

Re: No pxe boot on virtual box guests

Jep, too many moving pieces.. Chris > On 08 Feb 2016, at 17:01, Ronald Steele wrote: > > I tried the things listed in the linked page, and more, and couldn’t get it > working. > What is odd is that I have done this before, with FAI 4.xx and a Wheezy > client install. > > i’m currently using

Re: No pxe boot on virtual box guests

jep, checked that twice, with even more controler options and combinations.. no way.. c > On 08 Feb 2016, at 16:24, Thomas Lange wrote: > >> On Mon, 8 Feb 2016 16:04:27 +0100, Christian Linden >> said: > >> Client gets installed fine -> reboot -> blank screen with cursor in the >> u

Re: No pxe boot on virtual box guests

I tried the things listed in the linked page, and more, and couldn’t get it working. What is odd is that I have done this before, with FAI 4.xx and a Wheezy client install. i’m currently using the latest FAI 5.xx and Jessie client. I did try a previous FAI 4.xx and Jessie and it’s not working

Re: No pxe boot on virtual box guests

> On Mon, 8 Feb 2016 16:04:27 +0100, Christian Linden > said: > Client gets installed fine -> reboot -> blank screen with cursor in the upper left corner or if again booting via pxe -> „FATAL: INT18: BOOT FAILURE“. > I assume Vbox doesn’t find GRUB for whatever reason.. I give u

Re: No pxe boot on virtual box guests

I found no way to get the installed fai client bootet. I checked all BIOS settings in VBox, all storage controlers etc.. no way.. Client gets installed fine -> reboot -> blank screen with cursor in the upper left corner or if again booting via pxe -> „FATAL: INT18: BOOT FAILURE“. I assume Vbox doe

Re: No pxe boot on virtual box guests

Thanks for clarifying, Ron. The IP address from the VB-DHCP-Server was put in the /etc/exports.. which is the wrong one for the booting client.. changed that and the installation went through. I’m actually stuck at the same BOOT INT18 error and will continue working on that next week latest and

Re: No pxe boot on virtual box guests

I found the cute txt.logs =) root@faiserver:/var/log/fai/remote-logs/demohost/install-20160205_164038# cat error.log fai.log:primary / 2G-15G ext4 rw,noatime,errors=remount-ro fai.log:Error in task partition. Code: 710 fai.log:Traceback: task_error task_partition task task_install task t

Re: No pxe boot on virtual box guests

To use next-server faiserver, faiserver must be in your /etc/hosts and have the ip address that is accessible to your client (not “localhost”). It used to be that the hostname was usually assigned to the IP address of the first or primary network interface. Somewhere along the line that changed

Re: No pxe boot on virtual box guests

Hi all, after I replaced „next-server faiserver“ with „next-server 192.168.33.250“ the pxe boot starts well. Actually I’m stuck at „mount.nfs: access denied by server while mounting 192.168.33.250:/srv/fai/nfsroot“ But I’m confident getting this resolved as well =P Cheers, Chris > On 26 Jan

Re: No pxe boot on virtual box guests

Hey Ron, I’d be happy to see you /etc/network/interfaces files =) Cheers, Chris > On 26 Jan 2016, at 23:34, Ronald Steele 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

Re: No pxe boot on virtual box guests

Got it from dropbox, thank you, Ron! Sure you are right regarding that ssh’ing on theb box is better.. but from the pure function perspective this network isn’t needed; that’s what I wanted to say. I’ve no time today.. will check that tomorrow and provide feedback. THanks! Chris > On 26 Jan 20

Re: No pxe boot on virtual box guests

> On Tue, 26 Jan 2016 22:34:34 +, Ronald Steele > said: > 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. I just want to emphasis that a bridged network with WLAN does not work

Re: No pxe boot on virtual box guests

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

Re: No pxe boot on virtual box guests

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

Re: No pxe boot on virtual box guests

Oh my god.. what a crap is that.. then they should lock the complete settings.. Cool Frank, thank you! c > On 26 Jan 2016, at 19:13, Frank Thommen wrote: > > Is your VM currently running? stop it and retry. You cannot change settings > while the VM is running > > f. > > > On 01/26/2016 05:

Re: No pxe boot on virtual box guests

Is your VM currently running? stop it and retry. You cannot change settings while the VM is running f. On 01/26/2016 05:47 PM, Christian Linden wrote: 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:3

Re: No pxe boot on virtual box guests

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 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 o

Re: No pxe boot on virtual box guests

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”,

Re: No pxe boot on virtual box guests

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 - 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

Re: No pxe boot on virtual box guests

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-F

Re: No pxe boot on virtual box guests

I'm not sure what a screen shows while a machine PXE boots. (Sorry, I'm blind.) So this may be a dumb suggestion but you can tell what files a machine is asking the tftp server for during a PXE boot by turning on verbose mode on the tftp server. With tftpd-hpa, you add - to the end of the T

Re: No pxe boot on virtual box guests

The other way works as well: Having FAI on a dedicated server (in our case as a KVM host) and the FAI client in VirtualBox. Using FAI 4.2.5 here. Never tried having both server and Client in VirtualBox though. Cheers, Robert Am 26.01.2016 um 16:36 schrieb Frank Thommen: > Hi Chris, > >> Thomas

Re: No pxe boot on virtual box guests

Hi Chris, 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 wi

Re: No pxe boot on virtual box guests

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

No pxe boot on virtual box guests

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