Change Needed for VM to PXE boot to FOG...
-
I recall reading a post about needed to change something in FOG to allow a VM to boot to iPXE.
Currently, I have the VM running on Server 2008 R2 Hyper-V.
-
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.
-
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?
-
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] -
I’m using svn, and I just updated to revision 1310, but i’m still having the same issue.
-
Running the latest version of fog .33b and I can confirm this is an issue with Hyper-V. Works fine from VirtualBox
-
[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.
-
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]
-
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 -
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]
-
[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…
-
[quote=“BigMan99211, post: 24152, member: 21932”]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?[/quote]Has there been any movement on resolving this issue? I am experiencing it also on my Hyper-V 2012. Physical machines have no issue.
Ubuntu Server 14.04 LTS x64
Fog Project 1.1.2Both clean virgin installs.
This is a game stopper for upgrading from 0.32 .
-
And you try and use the files found in SVN trunk
-
I’ve tried:
[CODE]wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe -O /tftpboot/undionly.kpxe[/CODE]
and
[CODE]
cd /var/www/fog/service/ipxe/
rm init.xz init_32.xz
wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init.xz
wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init_32.xz
[/CODE]Plus I’ve tried [url]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/url] . The symbolic link works, but the same error results.
The physical machines I’ve tried so far all work, it is only hanging up with my Hyper-V 2012 VMs with the same two errors as the original poster.
-
It will be ugly, but can you try this:
[url]http://fogproject.org/forum/threads/dell-optiplex-320.10872/#post-31511[/url] -
[quote=“Tom Elliott, post: 32252, member: 7271”]It will be ugly, but can you try this:
[url]http://fogproject.org/forum/threads/dell-optiplex-320.10872/#post-31511[/url][/quote]Editing {fogwebdir}/lib/fog/BootMenu.class.php changing line 600:
[PHP]print “console --picture $this->booturl/ipxe/bg.png --left 100 --right 80\n”;[/PHP]
to
[PHP]// print “console --picture $this->booturl/ipxe/bg.png --left 100 --right 80\n”;[/PHP]
… appears to be working! … oh wait… nvm.
I get to the Control Key prompt to enter, then the username/password page, but then the same error occurs. -
Can you comment out all instances of console within those files? I believe there’s only one but I could be way off.
-
There can be only ONE!
ahem… There is only one instance of “console” in that context. There are two other entries as variables “consoleblank=0”
And now, somehow, I’m back to the original condition without getting to the ControlKey and Username/Password.
I read somewhere else, someone was having an issue where they could only get things to work immediately after rebooting the server. So I tried that.
If I time the PXE boot on my VM to hit the FOG server within the first few seconds of restarting, I can get all the way to the PXE menu. I quickly then tried to do a Quick Host Registration.
/bzImage… ok
/init.xz… ok
tsc: Fast TSC calibration failed
The VM window re-sizes to what looks like 1024x768, then if I’m lucky, I might get to:
piix4_smbus 0000:00:07.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
… otherwise it’s hanging after the screen re-size.
I then disabled the firewall:
[CODE]sudo ufw disable[/CODE]
My VM is showing CPU usage above idle (12%) while I’m stuck.
Meanwhile we’re looking into the SQL server. -
Alrighty… something’s working.
I’ve been stepping up through the kernels and have landed on unofficial 3.15.3 that appears to be working … okay-ish.
I’m grabbing a linux server vm right now and it spitting up errors like watermelon seeds along the likes of:
bug: using smp_processor_id() in preemptible [00000000] code partclone.image/2520
… but it is still working through the upload.
Now to blow it all away back to bare metal and see what fixes are really needed.
-
… but wait! There’s more!
This current configuration with this kernel works but is extremely slow to proceed after “/init.xz… ok” on the physical machines I was using for testing. It eventually pops up a failure to configure the network adapter. (an Intel
82567LM-3 Gigabit Network Connection)
