Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 896585

Summary: RHEL5.8 kvm pxe fails.
Product: Red Hat Enterprise Linux 5 Reporter: craig <craig.lamparter>
Component: kvmAssignee: Amos Kong <akong>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.8CC: ailan, chayang, juzhang, mkenneth, rhod, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 05:10:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sos report rhel5.8
none
sos report for rhel5.9
none
V2 sosreport log files from HP none

Description craig 2013-01-17 15:06:04 UTC 
Description of problem:
Unable to get dhcp lease in kvm (wrong subnet, can't change).

Version-Release number of selected component (if applicable):
RHEL5.8

How reproducible:
100%

Steps to Reproduce:
Deploy RHEL5.8 KVM on target server. After successful installation os try to create a virtual machine on it.
We can see the craeted vm will fail to boot to pxe.
We tried to Share the physical Network with Both KVM Host and Guest.
We shared the physical network port of Host (Eth0) with bridge (br0) by following the steps mentioned in one of the wiki page.
We followed the steps mentioned in the URL http://wiki.libvirt.org/page/Networking#Host_configuration_2
Created a VM by selecting Shared Physical device for Network.
When VM is booting from PXE we are getting different Error “Searching for Server (DHCP)…. No IP address.
Still VM Guest are not getting discovered in RDP Console.
  
Actual results:
No IP address

Expected results:
DHCP lease

Additional info:
This is not a problem with RHEL6.3KVM x86_64.


proxying this bugrequest for HP RDP business (internal quix# QXCR1001261256).

Initial requestors:  vinodhk hemantha-kumara.y konkumutti.mounika
--craig
Comment 1 Amos Kong 2013-01-20 13:36:56 UTC 
Can you provide the sosreport result? I want to know more detail of configuration. Thanks.
Comment 2 craig 2013-01-25 15:06:55 UTC 
attaching sos report(s), thanks!
-craig
Comment 3 craig 2013-01-25 15:08:08 UTC 
Created attachment 687506 [details]
sos report rhel5.8
Comment 4 craig 2013-01-25 15:08:53 UTC 
Created attachment 687507 [details]
sos report for rhel5.9
Comment 5 Amos Kong 2013-03-08 03:21:23 UTC 
(In reply to comment #2)
> attaching sos report(s), thanks!
> -craig

Hi craig,

Does this problem still exist? Can you help to reproduce this bug and re-collect the sosreport log (make sure problem is reproduced & vm is running)?

I didn't find any log in sosreport/var/log/libvirt/qemu/,
no qemu process in sosreport/ps

Thanks.
Comment 7 Amos Kong 2013-03-19 03:38:57 UTC 
Created attachment 712374 [details]
V2 sosreport log files from HP

I sent mail to (craig.lamparter, vinodhk, hemantha-kumara.y, konkumutti.mounika), Mounika provided me this log files. It's effective :)
Comment 8 Amos Kong 2013-03-19 05:10:41 UTC 
In latest sosreportlog, guest already got the ip address(192.168.122.93) from DHCP service which is provided by dnsmasq. But it failed to find the tftp file (Error: No filename).

TFTP was not configured rightly, there is no tftp options in dnsmasq's cmdline

tftp related options:  --enable-tftp --tftp-root $tftp --dhcp-boot $dhcp

$ grep dnsmasq k.896585-985977/ps
/usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file=  --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253 --dhcp-no-override


$ grep network k.896585-985977/etc/libvirt/qemu/win.xml
    <boot dev='network'/>
      <source network='default'/>

1. guest try to boot from network first
2. guest will use 'default' network

$ grep bridge k.896585-985977/etc/libvirt/qemu/networks/default.xml 
  <bridge name="virbr0" />

Default network uses the private bridge (virbr0, subnet: 192.168.122.*)

You should use public bridge (br0 subnet:172.20.50.*).


So it's a configure problem, I will close this bug.