Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Fix upstream in v0.8.3-23-ge26672f:
commit e26672f78661272274580e0653b21017c7c31d4e
Author: Jiri Denemark <jdenemar>
Date: Wed Aug 11 20:25:09 2010 +0200
bridge: Add --dhcp-no-override option to dnsmasq
--dhcp-no-override description from dnsmasq man page:
Disable re-use of the DHCP servername and filename fields as
extra option space. If it can, dnsmasq moves the boot server and
filename information (from dhcp-boot) out of their dedicated
fields into DHCP options. This make extra space available in the
DHCP packet for options but can, rarely, confuse old or broken
clients. This flag forces "simple and safe" behaviour to avoid
problems in such a case.
It seems some virtual network card ROMs are this old/buggy so let's add
--dhcp-no-override as a workaround for them. We don't use extra DHCP
options so this should be safe. The option was added in dnsmasq-2.41,
which becomes the minimum required version.
Verified it on RHEL6_x86_64 Server and it passed:
libvirt-0.8.6-1.el6.x86_64
kernel-2.6.32-92.el6.x86_64
qemu-kvm-0.12.1.2-2.128.el6.x86_64
The steps are as follows:
1. #yum -y install syslinux
#mkdir /var/lib/tftpboot
#cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot
2, dowload vmlinuz and initrd.img under the /var/lib/tftpboot folder
example: http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.0-Beta1-4.1/6.0/Server/x86_64/os/images/pxeboot/
3, mkdir /var/lib/tftpboot/pxelinux.cfg
4, create a file name default under the pxelinux.cfg folder
5, edit the file with the contents
DISPLAY boot.txt
DEFAULT rhel6
LABEL rhel6
kernel vmlinuz
append initrd=initrd.img
PROMPT 1
TIMEOUT 0
6, create a new virtual network , the xml description is as follows
<network>
<name>netboot</name>
<bridge name="virbr1" stp='off' delay='1'/>
<forward/>
<ip address="192.168.10.1" netmask="255.255.255.0">
<tftp root="/var/lib/tftpboot" />
<dhcp>
<range start="192.168.10.2" end="192.168.10.254" />
<bootp file="pxelinux.0" />
</dhcp>
</ip>
</network>
7, using virt-manager to create a new vm in pxe network install way, and choose netboot virtual network as its network
After step 7, the vm is installed successfully.
retest with libvirt-0.8.7-6.el6.x86_64 PASSED . So could set bug status to VERIFIED
The steps are as follows:
1. #yum -y install syslinux
#mkdir /var/lib/tftpboot
#cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot
2, dowload vmlinuz and initrd.img under the /var/lib/tftpboot folder
example:
http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.0-Beta1-4.1/6.0/Server/x86_64/os/images/pxeboot/
3, mkdir /var/lib/tftpboot/pxelinux.cfg
4, create a file name default under the pxelinux.cfg folder
5, edit the file with the contents
DISPLAY boot.txt
DEFAULT rhel6
LABEL rhel6
kernel vmlinuz
append initrd=initrd.img
PROMPT 1
TIMEOUT 0
6, create a new virtual network , the xml description is as follows
<network>
<name>netboot</name>
<bridge name="virbr1" stp='off' delay='1'/>
<forward/>
<ip address="192.168.10.1" netmask="255.255.255.0">
<tftp root="/var/lib/tftpboot" />
<dhcp>
<range start="192.168.10.2" end="192.168.10.254" />
<bootp file="pxelinux.0" />
</dhcp>
</ip>
</network>
7, using virt-manager to create a new vm in pxe network install way, and choose
netboot virtual network as its network
After step 7, the vm is installed successfully.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html
Fix upstream in v0.8.3-23-ge26672f: commit e26672f78661272274580e0653b21017c7c31d4e Author: Jiri Denemark <jdenemar> Date: Wed Aug 11 20:25:09 2010 +0200 bridge: Add --dhcp-no-override option to dnsmasq --dhcp-no-override description from dnsmasq man page: Disable re-use of the DHCP servername and filename fields as extra option space. If it can, dnsmasq moves the boot server and filename information (from dhcp-boot) out of their dedicated fields into DHCP options. This make extra space available in the DHCP packet for options but can, rarely, confuse old or broken clients. This flag forces "simple and safe" behaviour to avoid problems in such a case. It seems some virtual network card ROMs are this old/buggy so let's add --dhcp-no-override as a workaround for them. We don't use extra DHCP options so this should be safe. The option was added in dnsmasq-2.41, which becomes the minimum required version.