Michael DeHaan wrote:
> Pete Eby wrote:
>> Michael DeHaan wrote:
>>
>>> Pete Eby wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> We recently have deployed Cobbler and its working very well for us. I am
>>>> having some trouble getting some images to work correctly with memdisk
>>>> though and was hoping I might be able to get some advice.
>>>>
>>>> For example, I have tried adding the image using the following methods:
>>>>
>>>> cobbler image add --name=UltraPro --file=/tftpboot/hw/ultrapro.img
>>>> --image-type=memdisk
>>>>
>>>> cobbler image add --name=UltraPro --file=/tftpboot/hw/ultrapro.img
>>>> --image-type=direct
>>>>
>>>> cobbler distro add --name=UltraPro --kernel=/tftpboot/memdisk
>>>> --initrd=/tftpboot/hw/ultrapro.img
>>>>
>>>> (I assume this one is incorrect the the above methods are the way to go.)
>>>>
>>>> In all cases, the kernel loads but it appears that right when it goes to
>>>> execute the program, it just hangs at a black screen.
>>>>
>>>> I thought it might be the version of memdisk, so I downloaded
>>>> syslinux-3.73 and compiled a new memdisk - though that did not seem to
>>>> do anything.
>>>>
>>>> I do have memdisk working fine with a memtest.img, but when trying to
>>>> use several other .img files (Such as this UltraPro img of a floppy, and
>>>> various others) I am getting this issue.
>>>>
>>>> Thanks for any input, I appreciate it.
>>>>
>>>> Cheers,
>>>> Pete Eby
>>>> _______________________________________________
>>>> cobbler mailing list
>>>> [email protected]
>>>> https://fedorahosted.org/mailman/listinfo/cobbler
>>>>
>>>>
>>> Hi Pete,
>>>
>>> Sorry for my ignorance here, but what's an ultrapro?
>>>
>>> You might want to try asking this on the syslinux mailing list -- but it
>>> may also not be the right kind of image, don't know.
>>>
>>> I'd be sure to share your options from
>>> /var/lib/tftpboot/pxelinux.cfg/filename to show what you are passing to
>>> it if that is the case.
>>>
>>> Some one else may have some other ideas.
>>>
>>> I have, for what it's worth, only tried it with memtest as well.
>>>
>>> --Michael
>>>
>>>
>>>
>>>
>>>
>>> --Michael
>>>
>>>
>>>
>>> _______________________________________________
>>> cobbler mailing list
>>> [email protected]
>>> https://fedorahosted.org/mailman/listinfo/cobbler
>>>
>>>
>>>
>> Hi Michael,
>>
>> Thanks for the input.
>>
>> UltraPro is a hardware testing environment we use to test servers with.
>> It does an okay job.
>>
>> The weird thing is that this works fine on our generic PXE system with
>> just memdisk and loading the image. I even tried the exact same memdisk
>> file. For some reason this does not work in Cobbler, but works fine on
>> our "normal" PXE server.
>>
>> The Cobbler PXE menu entry is:
>>
>> LABEL UltraPro
>> kernel /memdisk
>> MENU LABEL UltraPro
>> append initrd=/images2/UltraPro ksdevice=eth0 lang= kssendmac
>> syslog=192.168.42.100:25150 text
>>
>> (I tried taking out all the extra options manually and just leaving the
>> kernel and initrd args, but same result)
>>
>
> Yeah cobbler should not be adding those arguments to memdisk images.
> That's a bug.
>
>> Or old PXE system boots in the same way, and it works okay:
>>
>> LABEL ultrapro
>> KERNEL memdisk
>> APPEND initrd=/hw/ultrapro.img
>>
>
> Are you sure they are the same image? Cobbler is basically just using
> TFTP from xinetd.
>> It seems to be related in some way to Cobbler, but I can't zero in on
>> how exactly.
>>
>> I have some other .img files that are the same - the work fine on our
>> old PXE server, but not Cobbler - in all cases they just use memdisk and
>> the img and that is pretty much all.
>>
>> If you or anyone has any other suggestions that would be great.
>>
>
> Strange.
>
> Don't have any ideas at the moment. If you edit the config file on the
> cobbler server to match exactly (don't run sync again as it would
> overwrite it) and use the memdisk
> from your old server you still have problems?
>
> Is the same TFTP server used on each? Is is the same ultrapro image?
>
>
Hi Michael,
Very strange. I copied over the memdisk from the system where this
works, and compiled a new memdisk (latest), but it still hangs just
after loading the image. Its like execution is just stopped or prevented
somehow, which just does not make sense to me.
MD5 shows the files on each server are the same.
[r...@cobbler tftpboot]# md5sum memdisk*
8f18dddf9ddba7760fa6f46802445b46 memdisk
098e9070e47bb1c604f189e4fa7339c0 memdisk-cobbler
[r...@install-gw tftpboot]# md5sum memdisk
8f18dddf9ddba7760fa6f46802445b46 memdisk
[r...@cobbler tftpboot]# md5sum hw/ultrapro.img
023069e46c81d1c1595dfc5807378027 hw/ultrapro.img
[r...@install-gw tftpboot]# md5sum hw/ultrapro.img
023069e46c81d1c1595dfc5807378027 hw/ultrapro.img
I did however notice that cobbler uses SELinux style permissions on the
files, despite SELinux being disabled? Perhaps this is due to my setting
up and ACL for a user - or are these permissions the default?
[r...@cobbler tftpboot]# ls -laZ
drwxrwxr-x+ root root .
drwxr-xr-x root root system_u:object_r:root_t:s0 ..
drwxrwxr-x+ root root acronis
drwxrwxr-x+ root root hw
drwxrwxr-x+ root root images
drwxrwxr-x+ root root images2
-rw-r--r-- root root memdisk
-rw-rwxr--+ root root system_u:object_r:lib_t:s0 memdisk-cobbler
-rw-rw-r--+ root root memdisk-new
-rw-rwxr--+ root root menu.c32
-rw-rwxr--+ root root
-rw-rwxr--+ root root system_u:object_r:lib_t:s0 pxelinux.0
I am certainly not that familiar with ACL permissions, but is it
possible this has something to do with it?
I have also ensured the config in pxelinux.cfg is (essentially)
identical to the working server, it is only:
LABEL ultrapro
KERNEL memdisk
MENU LABEL UltraProOld
APPEND initrd=/hw/ultrapro.img
If you care to try I have temporarily uploaded the image I am using to:
http://www.timelordz.com/scripts/sago/ultrapro.img
(I'll leave it there for a day or so.)
I would like to get this resolved so we can use this and similar images
and so fully migrate to Cobbler and not have to maintain a separate PXE
server just to run a few of these images, this being one of the more
important.
Not that other images such as dban and memtest work fine with Cobbler,
but this one and some others are tricky.
It certainly is strange though as on the one hand I think it can't
really be related to Cobbler, yet on the other hand it just does not
work when it should. Very odd.
Any other hints would be great! Thanks for your time.
Cheers,
Pete
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
