Skip to main content

PXE boot Fedora 16

Resolution:  noapic acpi=off for kernel args

Implementation:
[root@blackmesa ~]# cd /var/www/html/isos
[root@blackmesa ~]# wget http://some.server.com/Fedora-16-x86_64-DVD.iso
[root@blackmesa ~]# mkdir /var/www/html/OS/Fedora16-x86_64

[root@blackmesa ~]# echo "/var/www/html/isos/Fedora-16-x86_64-DVD.iso /var/www/html/OS/Fedora16-x86_64 udf,iso9660 user,loop 0 0" >> /etc/fstab
[root@blackmesa ~]# mount /var/www/html/OS/Fedora16-x86_64 


[root@blackmesa ~]# mkdir /var/lib/tftpboot/Fedora16-x86_64
[root@blackmesa ~]# /var/www/html/OS/Fedora16-x86_64/isolinux/initrd.img /var/lib/tftpboot/Fedora16-x86_64
[root@blackmesa ~]# /var/www/html/OS/Fedora16-x86_64/isolinux/vmlinuz /var/lib/tftpboot/Fedora16-x86_64
Add an entry into your pxeboot default files
[root@blackmesa ~]# cat /var/lib/tftpboot/pxelinux.cfg/default
...<trunc'd for brevity>...
label 16
  kernel Fedora16-x86_64/vmlinuz
  append initrd=Fedora16-x86_64/initrd.img ramdisk_size=9216 ksdevice=link autostep repo=http://10.10.31.10/OS/Fedora16-x86_64 ks=http://10.10.31.10/Profiles/Fedora16-x86_64.ks noapic acpi=off 

[root@blackmesa ~]# cat << EOF > /var/www/html/Profiles/Fedora16-x86_64.ks 
install
url --url=http://10.10.31.10/OS/Fedora16-x86_64
lang en_US.UTF-8
keyboard us
EOF

Issue:  I am testing an old Compaq nc6400 and a new Kickstart server and attempting to integrate Fedora into the whole thing.  One additional thing that is noteworthy, the 'eth0' interface is now p2p1 (or some nonsense) in Fedora 16.
Labels:

Comments

  1. IscaApril 30, 2012 at 6:27 PM

    I have a problem using this method. When it starts boot give me a message dracut = no root entry.
    I also try put nfs server and give the parameters to the nfs server and no sucess with this too.
    How can i fix that? Seems something is missing here... What root paramether is in your pxelinux.cfg/default file

    Thanks

    ReplyDelete
  2. UnknownJuly 13, 2012 at 4:08 AM

    that issue with strange eth0 name can be bypassed by appending biosdevname=0 to kernel at instalation

    ReplyDelete

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more