Posts made by Jaymes Driver

Side note this stuff may be completely unrelated but…

What format are your drives in? Have you tried switching your Image Type to one if the Mutli Partition selections?

The best way I found is to export the appliance, unfortunately. Unless you only want to make copies in which case cloning would be the best solution.

I use an external drive to store all my Virtual Images on so I don’t actually “export” them I just set up the appliance with the current files at my other locations. This allows me to have the same image and upload to the different servers (I chose stand alone servers instead of Nodes… not really sure why, I was just new at setting FOG up and I never re did the set up I know it’s going to change when I upgrade to 0.33 version but for now I just have multiple servers.)

I am partial to the snapshots feature. That and I use fairly antiquated technology, the ones that are on the phase out, for my imaging so I never had a GOOD server to build ESXi on, so the bad taste left in my mouth may be my own fault, but I never had good luck with VMWare.

I do dynamic just because I want the disk to expand but I still set the max to like 60 gb that way I know that I can image all the hard drives I have in my corporation (we don’t have anything smaller than 80 gb now) and if you need to, you can use gparted live cd to alter your partitions.

ooo… I don’t have that. I only run a vm for FOG if I am testing I have a physical box I install FOG on. The images are the only ones I keep on the VM.

Someone else may need to offer some expertise to get a VM FOG to take a VM image I don’t know if there is anything specific you may need to do. I don’t think it should cause any issues

I use VirtualBox and I set up my images as VDI. Make sure you are setting up the network adapter in a bridged mode under the settings for your virtual machine.

I don’t have any problems with uploading my image, I would try a different kernel. VirtualBox has always just worked, that is why I chose it over VMWare because VMWare uses scsi drivers and they are not included in the kernels.

try this one -> [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]

Tom has informed me that the undionly.kpxe file IS the pxelinux.0 file. So with that being said, we don’t have to rename the pxelinux file and we can use undionly.kpxe in place. I will test and verify/update wiki when I have confirmed this.

Thanks for that Tom, I have adjusted my statement as not to confuse anyone.

Which Revision of Ubuntu?

I can confirm that 13.10 works fine. There are ALWAYS issues to over come when launching FOG in each environment, everyone has different switches and hardware. I know you want to blame Ubuntu, and I will admit that the latest revision of Ubuntu have needed some adjustment to work perfectly with fog. But I can also confirm that each one of my test servers is at the latest revision. So I don’t think this is a problem with Ubuntu.

I also want to note that I am able to boot, and image to my servers on 13.10, but I am using the Beta version of FOG.

THANK YOU FOR THE HELP!!! THAT DID IT!!! It had to be the ipxe.krn in the default file that was where I kept getting stuck! I kept using the undionly.kpxe

So for reference this is how I set it up.

Installed DNSMasq and used the settings recommended in the wiki. I edited some of the information, but I left it to boot pxelinux.0. I added the line dhcp-authoritative to the bottom of the ltsp.conf and saved the file. I will post my set up at the end of my write up.

I then renamed the pxelinux.0.old in the /tftpboot folder to pxelinux.0
[code]
sudo mv /tftpboot/pxelinux.0.old /tftpboot/pxelinux.0
[/code]

Now I created a /pxelinux.cfg/default.

[code]
cd tftpboot
sudo mkdir /pxelinux.cfg
cd pxelinux.cfg
sudo gedit default
[/code]

I used Junkhackers recommendation on the default file information substituting my ip address for the fog server:

[code]
DEFAULT vesamenu.c32
LABEL fog
MENU DEFAULT
kernel ipxe.krn dhcp && chain http://(fog-server-ip-address)/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 01
[/code]

Then test!

as promised my ltsp.conf

[code]

port=0
log-dhcp
tftp-root=/tftpboot

dhcp-boot=/tftpboot/pxelinux.0

dhcp-option=17,/images

dhcp-option=vendor:PXEClient,6,2b

dhcp-no-override

pxe-prompt=“Press F8 for boot menu”, 0

pxe-service=X86PC, “Boot from network”, pxelinux

dhcp-range=10.6.10.1,proxy
dhcp-authoritative

[/code]

I’ve tried both. I’ve been focusing on undionly.kpxe, should I not be?

After supplying either one I just sit at “boot:”

Yes, that is the guide I am working off of.

Also taking information from:
[url]http://etherboot.org/wiki/pxechaining[/url]
[url]http://www.richud.com/wiki/Network_iPXE_dnsmasq_Examples_PXE_BOOT[/url]

As the title says.

I am looking for help in getting the dnsmasq to boot the undionly.kpxe. I have been beating my head against the wall since the 0.33b switched to iPXE. I’ve used a few guides online, but I will spare you the drab, because NONE of them have worked thus far. Most only return that the boot file can not be found. The ONLY boot file I can successfully find is pxelinux.0 and I tried using it to chain load as well.

I have tried editing the current working dnsmasq settings to include the undionly.kpxe. I only get errors returned stating the boot file can not be found.

After attempting to chain load from a pxe file I am greeted with a command prompt stuck at “boot:”

I HAVE to use this service in my environment it is the only way I can talk to my machines properly with all the networking junk. So if someone has ideas or troubleshooting steps, I am all ears!

I don’t keep the kernels up to date, Tom does. I know it is above 3.13.

Tom builds his kernels to be mostly all inclusive, and he does an amazing job. In the past I just made a custom kernel to include the drivers I needed but since Tom started compiling them, I just use his

Back up your old bzImage. located /tftpboot/fog/kernel/bzImage.

Change it to bzImage.OLD or something similar.

Download the new bzImage from [COLOR=#737373][url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]32[/COLOR]

put the new bzImage in the /tftpboot/fog/kernel/ folder.

WireShark, watch the packets and where they get stopped.

There you go! That’s where you need to make your changes, with the Web GUI!

Try installing the proxyDHCP stuff.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

I normally use a Gparted live CD to extend my os to the end of the DISK, with Windows there is a command in the sysprep Unattend.xml file that can extend the OS. I am not familiar with doing this in linux without using a tool.

Try deleting your file KitchenSinkPXE.

When you say you changed the file I assume you did so on the FOG Web GUI is this correct?

I would say the 0.33b is stable. Like Tom said, it is as stable as 0.32

HOWEVER… there are a lot of implementations going on. Tom is working to make the system leaner, and has already changed the cloning solution to SUPPORT uefi so we can make that transition. We are still working on the solid base of required features though so that we can begin to work on the luxuries.

I would say there isn’t really an expected time for a stable release, but I wouldn’t say that the Version of 0.33b is unstable either. Just definitely in the beta test stages. (Which is better than alpha test stage!!!)