Windows Wont PXE Boot
-
The internet is full of similar kind of issues (not really a ‘FOG problem’):
[url]http://softwarefromnorth.blogspot.de/2011/04/virtualbox-fatal-could-not-read-from.html[/url]
[url]http://eitwebguru.com/virtualbox-pxe-boot-fatal-could-not-read-from-the-boot-medium-system-halted/[/url]
… -
[quote=“Uncle Frank, post: 42353, member: 28116”]The internet is full of similar kind of issues (not really a ‘FOG problem’):
[url]http://softwarefromnorth.blogspot.de/2011/04/virtualbox-fatal-could-not-read-from.html[/url]
[url]http://eitwebguru.com/virtualbox-pxe-boot-fatal-could-not-read-from-the-boot-medium-system-halted/[/url]
…[/quote]Thanks for this,
Ive come across these articles already, did what they said. It made no difference same problem
-
[url]http://myworldofit.net/?p=975[/url]
Can you see DHCP (or any other) traffic on the virtual network interface within your windows host using wireshark? I don’t have windows with virtualbox installed here but as far as I remember it should be possible to caputre those packets.
-
Actually, Now you say that. I let the WIN7 box boot using the PC-NET adaptor. Once windows logs in the network connection is down. Says the driver failed to install. Did a google around to find one and can’t for the life of me find one to get it working. Even Virtual box forums are just saying to use the Intel Adaptor but we all know that has issues with PXE booting.
If I use the intel adaptor the network status is fine. So looks like I potentially need to get this adaptor working on the PC-net, but can’t find a driver.
-
Ok I tried another solution where by some people have been having issues PXE booting with windows so I made both a Mac and a Linux VM and set them to boot to their network cards.
The linux VM gave me the error FATAL: No Bootable medium found! System Halted
I have remote access enabled to these servers if anyone would be up for remote in and taking a look?
-
Change your network adapters to E1000
-
These are the only options I get, I have the extension pack installed
[url=“/_imported_xf_attachments/1/1694_box.png?:”]box.png[/url]
-
E1000 is any of the Intel pro 1000 nics
-
Thought so,
Ive been using those and im still getting the same errors.
-
And have you tried the troubleshooting instructions?
-
Ive followed everything I can find on Virtualbox and fogforums and the user guide
-
So the TFTP files transfer just fine?
-
I had the same problem, some peoples have problems with pxe boot in virtualbox 4.3
[url]https://forums.virtualbox.org/viewtopic.php?f=6&t=66092#p313130[/url]
Can you install a older version of virtualbox? For example 4.2
[url]https://www.virtualbox.org/wiki/Download_Old_Builds[/url] -
Ok, seemed to have got it working…sort of.
Seems there must of been an issue with the network adaptors or the install on the machine I was running Virtualbox on. I tried to uninstall virtual box and do a reinstall but it would hang when removing the network adaptors. Finally managed to get it to uninstall. Tried another re install but again it would hang on installing the network adaptors and kill my network. So now I can’t install virtual box on the server I wanted it on.
I’ve now installed Virtualbox on my laptop and started again from scratch and the windows VM now boots to FOG
whoop!But I’m now getting the following error when I register the Host - see attached file.
The screen then changes and says its attempting to register the host but nothing happens further
[url=“/_imported_xf_attachments/1/1695_Untitled.png?:”]Untitled.png[/url]
-
personally i prefer vmware player , i think that the networking coding is more solid. but its up to you …
-
Thanks for the Comments Jenesis but im using virtual box as its free. VMware isnt.
Any one got any ideas on my new problem above?
-
This post is deleted! -
Actually VM player is free unless its changed lately.
-
Do you get anything after “Starting network…”???
The above ‘IP-Config’ warnings/errors derive from the linux kernel (see here: [url]http://lxr.free-electrons.com/source/net/ipv4/ipconfig.c#L1469[/url]). To me that sounds like the kernel has trouble to talk to the network and therefore other things like linux dhclient won’t be able to get an address from the DHCP-server either. This is just guessing as I don’t have an insight into what is really going on in your setup.
Can you capture the traffic on that virtual network interface within your windows host using wireshark??
You can try booting any kind of linux live CD (e.g. ubuntu) in that virtualbox container to see if network is alright with that…
-
I am now having a issue with Intel E1000 NIC not working with FOG I am using VM Ware Player 6.0.5 build-2443746 with FOG 1.2.0 and Ubuntu 10.04.4 I am getting a PXE-E32: TFTP open timeout as anyone encountered this issue all the machines I have tried boot no problem just the VM is an issue.
[url=“/_imported_xf_attachments/1/1703_IMG_20150212_103810.jpg?:”]IMG_20150212_103810.jpg[/url]
