windows 7 - Setting up VirtualBox guest for PXE boot

21
2014-04
  • Seth Hall

    I'm having an issue getting VirtualBox to boot from the network. I have a Server 2k8 installed and setup and acting as AD DS, DNS, DHCP and WDS. I have two adapter on the server, one of which I have setup as a static IP the one I'm using to hand out IPs to some of the other guest VMs and its setup as a 192.168.2 address.

    I have a couple guest VMs that I'm not sure if I'm setting up the adapters on them right or not. The static IP adapter on the server is adapter #2 and it's set to bridge, Intel PRO/1000 MT Desktop and is set to Allow All. Now on some of the guests I have those adapters setup the same but when I try to boot from LAN it either gives me a No boot medium found. System Halted! message or it will get a 192.168.1 address.

    I have a clonezilla.iso attached to the guest VMs and when I choose to Network Boot from iPXE from the list of options it presents it finds the 192.168.2 server and I'm able to press F12 and my Windows 7 image will load up and I'm able to install it. On the guest VMs I've tried setting the adapters to PCnet II and PCnet III and it will show the DHCP server IP and the guest IP and they're getting a 192.168.2 address but then it says No file found and sticks on the No bootable medium found. System halted!

    Could someone help me out and see where I might be messing up?

  • Answers
  • Seth Hall

    For anyone who runs across this, I had the latest version of VirtualBox and after reading through some of the forum posts on virtualbox.org found there is an extension pack that has updates for PXE that doesn't install when you check for updates. I downloaded it and installed it and am now able to successfully boot PXE like normal without having to go through Clonezilla lol.


  • Related Question

    windows - PXE Boot not working
  • Nishant

    Please explain the error in this screenshot:

    enter image description here

    DHCP Setting:

    enter image description here

    This screenshot was taken after powering off the old comp hence he server interface is shown as the wireless card - it becomes 192.168.0.1 when I connect wires and power up the old laptop to boot via PXE.

    My scenario is simple. An old laptop and a new laptop . A cross over cable ( that I myself made from CAT 6 cable by cutting it and connecting 4 wires as mentioned in some doc). The new laptop ( tftp server ) has a Wirelss Card ( with which I am browsing and writing this ) . And the cable is connected between laptops .

    TFTP server ( new laptop details )

    Windows IP Configuration

    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . :
       Link-local IPv6 Address . . . . . : fe80::f511:3d4a:ca01:122e%16
       IPv4 Address. . . . . . . . . . . : 192.168.0.1
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.2
    
    Wireless LAN adapter Wireless Network Connection:
    
       Connection-specific DNS Suffix  . : Achilles
       Link-local IPv6 Address . . . . . : fe80::99b1:8ae0:9e6c:f300%11
       IPv4 Address. . . . . . . . . . . : 192.168.2.3
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1 
    

  • Related Answers
  • 8088

    I resolved this problem. Things to keep in mind:

    1. Use crossover cable - not the usual LAN wire - router connections use this type of cable
    2. Assign an IP after connecting the computers and make sure the subnet mentioned matches
    3. You need the ISO in an Apache webserver - you can extract the ISO to a folder and provide the folder name during PXE booting to install