hey guys,

I have two VMs running inside virtualbox. One is an NFS server that is hosting my kickstart file, and i am trying to kickstart the other VM.

NFS is up and running on the server VM, selinux and iptables are off. I can see the server exports from some other RedHat VM by doing:

where 10.0.1.2 is the IP of the NFS server

in the kickstart file, i specified the NIC eth0 configuration to be statistically assigned an IP address (same subnet, and mask as the server ofcourse). I generated the kickstart file using CentOS kickstart tool, so there's no chance for syntax errors or something.

Now, on the boot prompt of the VM that I wanna kickstart I do:


installation proceeds but a message is displayed.. don't quite remember the exact message but it was trying to contact a DHCP server to get IP!!!

why did that happen? even though I statically configured eth0 in the ks file!

the other weird part, if I set the network configuration on the boot prompt by doing:
all proceeds OK and apparently the network is configured properly but the anaconda complains about not being able to download the kickstart file.. I guess this has something to do with loading nfs module or something but I never investigated.

Can anybody please shed some light on my problems with VirtualBox?

Thanks in advance,

if using static ip's anaconda has to be able to find the kickstart file hence the reason progression is made when you specify an ip on the command line. test the nfs to make sure you can actually mount 10.0.1.2:/kickme from somewhere remote first..

wo wo wo
hang on a second!

this seems like a chicken-egg problem to me! now anaconda needs to mount the remote NFS share first in order to get the ks file which contains network configuration. But, in order to do that, it has to have TCP/IP up and running (interface up and running!).............

hmmmmmmmmmm that's weird! why have a network configuration section in the ks file one can only set network configuration on the boot prompt! (maybe to allow configuration to be written to system files [permenantly])... is this the case???

I am able to mount the remote nfs share from remote machines!! what is wrong?


Please help.

I have a similar problem, not though with a kickstart file, but just mounting a nfs share between my computer and a VM in Virtualbox, for practicing for the Red hat exam. Even though they are on the same subnet and everything, the Error message I get is "No Route to Host", yet they can ping between and no prob.

I know this is not a solution but could also be the error you're experiencing