No pxe boot on virtual box guests

[Christian Linden]

I found the cute txt.logs =)

root at 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 task_action task main
root at faiserver:/var/log/fai/remote-logs/demohost/install-20160205_164038#


Best,
Chris


> On 05 Feb 2016, at 16:44, Christian Linden <lindomatic at gmail.com> wrote:
> 
> .. as soon as one puts the correct server/IP in /etc/exports even the mount works.
> But here’s the next pain:
> 
> Pls take a look at the attached pdf files.
> 
> Thank you!
> Chris
> 
> 
> <ErrorLog.pdf><FatalError.pdf>
> 
> 
> 
> 
>> On 05 Feb 2016, at 16:23, Christian Linden <lindomatic at gmail.com> wrote:
>> 
>> 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 2016, at 23:56, Thomas Lange <lange at informatik.uni-koeln.de> wrote:
>>> 
>>>>>>>> On Tue, 26 Jan 2016 22:34:34 +0000, Ronald Steele <rsteele at adaptivemethods.com> 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 (in most cases), and using a wired network on your host (on which
>>> the VM's are running) is important.
>>> 
>>> 
>>> P.S.: your dropbox screenshots work for me.
>>> -- 
>>> regards Thomas
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20160205/e8ce2b30/attachment.html>