SOLVED Change Needed for VM to PXE boot to FOG...


  • [QUOTE]Ok. I just figured out that I had the wrong network adapter booting to iPXE. But now, I’m getting errors when trying to load iPXE.

    “Could not configure console: No such file or directory ([url]http://ipxe.org/2d8c203b[/url])”
    “Could not boot: No such file or directory ([url]http://ipxe.org/2d8c203b[/url])”

    Then it just boots to the VHD like normal.[/QUOTE]

    Open your web interface and finish the install…


  • Not to be a pain, but is there any update on this? I’m running FOG 1.1.1 with build 1639 of iPXE. I’m getting this error when trying to boot from my Hyper-V VM. Screenshot below.

    [url="/_imported_xf_attachments/1/1007_Capture.PNG?:"]Capture.PNG[/url]


  • I am also receiving this same error message as Speedy, when attempting to pxe boot a Hyper-V VM with Fog 1.0.1. I downloaded kpxe directly through svn (as suggested above) and have tried booting with multiple kernels. I have not experienced any issues using Fog 1.0.1 to pxe boot to physical machines. Any suggestions would be greatly appreciated.

    FOG Version: 1.0.1
    OS Version: Ubuntu Server 12.04


  • Hi guys, I am experiencing exactly the same issue in an Optiplex 780 and Optiplex 9020. I am running the latest version using bisync. Ver 0.32 worked fine for my Optiplex 780, but not for the 9020 so I decided to give 0.33b a try. I also try downgrading the kernel to 3.8.8 Core and 3.3.3 Core and I get the same error.[IMG]https://www.dropbox.com/s/450k0cceypfcsza/fog.JPG[/IMG]

    [url="/_imported_xf_attachments/0/726_fog.JPG?:"]fog.JPG[/url]

  • Developer

    [quote=“Jason Shoemake, post: 26194, member: 6565”]Running the latest version of fog .33b and I can confirm this is an issue with Hyper-V. Works fine from VirtualBox[/quote]

    In my experiences… HyperV and VMWare don’t work well with fog without alterations.


  • Running the latest version of fog .33b and I can confirm this is an issue with Hyper-V. Works fine from VirtualBox


  • I’m using svn, and I just updated to revision 1310, but i’m still having the same issue.

  • Senior Developer

    I’m assuming you’ve downloaded via svn? What revision are you on?

    It may not have updated the undionly.kpxe file from the last change over.

    A way to ensure you’ve got the right undionly.kpxe file would be to download it directly through svn:
    [code]wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe -O /tftpboot/undionly.kpxe[/code]


  • Ok. I just figured out that I had the wrong network adapter booting to iPXE. But now, I’m getting errors when trying to load iPXE.

    “Could not configure console: No such file or directory ([url]http://ipxe.org/2d8c203b[/url])”
    “Could not boot: No such file or directory ([url]http://ipxe.org/2d8c203b[/url])”

    Then it just boots to the VHD like normal.

    Any ideas?

  • Developer

    I’m not sure I understand what it is you are asking. I am able to image perfectly fine using ipxe and virtual machines.

    I run Oracle VirtualBox machines and as long as I set up the network card as a bridged mode I can communicate with my pxe server.

    I have in the past used ESXi to build virtual images and upload them, and with the previous kernel 3.8.8 and FOG 0.32, I had to add the ability to talk to SCSI drives because of the way ESXi handles the virtual disks. I was unable to solve the issue with EXTREMELY slow upload speeds while using ESXi though, this is why I moved to VirtualBox and recommend using it to set up your virtual images. Speeds aren’t blazing fast but it still only takes ~ 25-30 min to upload a 20+ gb image. If I were to use ESXi to upload the image, it takes upwards for 7 hours -.-

    Hope this helps.

363
Online

8.0k
Users

14.9k
Topics

140.5k
Posts