| Summary: | Can not boot VM from PXE, there display 'connection timed out... No more network device' | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ying Cui <ycui> | ||||||||
| Component: | qemu-kvm | Assignee: | Alex Williamson <alex.williamson> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.2 | CC: | acathrow, apevec, areis, bsarathy, chayang, cshao, dyasny, gouyang, juzhang, knoel, leiwang, mburns, mkenneth, ovirt-maint, rananda, virt-maint | ||||||||
| Target Milestone: | rc | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-05-22 07:25:50 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Ying Cui
2011-10-28 10:43:06 UTC
Created attachment 530637 [details]
connection timed out pic
Created attachment 530638 [details]
vdsm log
I've pxe-booted 4 VMs including multiple at the same time from the same host with no issues. Is it possible there were intermittent networking issues in your environment? Can you also try with 6.2-20111026.2? Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. (In reply to comment #5) > Can you also try with 6.2-20111026.2? I tested this issue with 6.2-20111026.2 build, I can not reproduce this issue on normal machine. Note: I can not test this build on HP CCISS machine, because of https://bugzilla.redhat.com/show_bug.cgi?id=747102#c31 This bug does occur occasionally，we are not sure whether it is possible there were intermittent networking issues in our environment. Try add RHEL6.2-20111117.0 to RHEVM IC155.1, but failed with below error: Installation of 10.66.11.120. Recieved message: <BSTRAP component='VDS PACKAGES' status='OK' result='vdsm' message='vdsm-4.9.6-4.5.x86_64 '/> <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed to import default values'/> <BSTRAP component='RHEV_INSTALL' status='FAIL'/> it should be bug 804618. so I will try this bug on new RHEV-H 6.3 build when new build available and try on RHEL62 after 804618 is fixed. (In reply to comment #14) > Try add RHEL6.2-20111117.0 to RHEVM IC155.1, but failed with below error: > > Installation of 10.66.11.120. Recieved message: <BSTRAP component='VDS > PACKAGES' status='OK' result='vdsm' message='vdsm-4.9.6-4.5.x86_64 '/> > <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration > failed to import default values'/> > <BSTRAP component='RHEV_INSTALL' status='FAIL'/> > Tested again, the error did present and add RHEL62 host to RHEVM IC 155.1 successfully. Added 4 vms by using network "rhevm" but with all type virtio, e1000, rtl8139, all can boot from PXE. Since this bug cannot be always reproduced, QE will test on next RHEV-H 6.3, if still cannot reproduce, will close it. Please test with beta version and close if not valid anymore (In reply to comment #16) > Please test with beta version and close if not valid anymore QE will test this when can register to RHEVM successfully. Close this bug since can seldomly reproduce it. Can you provide tcpdump as well? (In reply to comment #25) > Can you provide tcpdump as well? The machine is used for another testing current, not convenient to move back to test this. If I get it back or can reproduce it on other machine I will give the tcpdump output ASAP. Created attachment 598395 [details]
attachment include "Screenshot of vm console" and "tcpdump.log"
Reproduce this bug on rhevh-6.3-20120710.0 build.
attachment include "Screenshot of vm console" and "tcpdump.log"
I am able to reproduce this on My Dell workstation consistently and able to do a workaround to overcome this issue as well. Please refer the reproduction steps and workaround to overcome this issue Reprodcution Steps: ================== 1. Install Redhat Enterprise Linux Workstation release 6.3 (Santiago) using RHEL6.3-20120613.2-Workstation-x86_64-DVD1.iso. 2. Configure the bridge network on this workstation as mentioned below in Bridge Configuration and do "service network restart" 3. Try to create a new VM using Virtual Machine Manager Bridge Configuration: ===================== #cat /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE=em1 TYPE=Ethernet ONBOOT="yes" BOOTPROTO="dhcp" HWADDR=MAC ADDR OF THE PHYSICAL PORT BRIDGE=br0 #UUID=UUID OF THE MACHINE # cat /etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge BOOTPROTO="dhcp" ONBOOT="yes" NM_CONTROLLED="no" Expected Result: ================= Should be able to connect and install via PXE Actual Result: ============== Throws Connection timed out error. Work Around: ============ I did a work around in this issue and was able to install the VM's successfully. Proceedure: =========== During the initial stage of gPXE initialization or when the gPXE throws timed out exception, Press CTRL+B (when the prompt is displayed for this option). After entering the gPXE prompt type the following two commands and dont worry about the usage error 1. clear 2. exit After doing this, the system will be able to connect to the PXE server automatically and will be able to complete the installation process successfully (In reply to comment #28) > > # cat /etc/sysconfig/network-scripts/ifcfg-br0 > DEVICE=br0 > TYPE=Bridge > BOOTPROTO="dhcp" > ONBOOT="yes" > NM_CONTROLLED="no" Your bridge is misconfigured, try adding: DELAY=0 to set the fowarding delay to zero, otherwise the bridge is still learning the mac addresses and won't forward dhcp replies do your VM. (In reply to comment #29) > (In reply to comment #28) > > > > # cat /etc/sysconfig/network-scripts/ifcfg-br0 > > DEVICE=br0 > > TYPE=Bridge > > BOOTPROTO="dhcp" > > ONBOOT="yes" > > NM_CONTROLLED="no" > > Your bridge is misconfigured, try adding: > > DELAY=0 > > to set the fowarding delay to zero, otherwise the bridge is still learning > the mac addresses and won't forward dhcp replies do your VM. Hi Alex, Thanks for the update, things are working fine now. Is this problem with the NEC uPD720400 bridge and qla3xxx NIC still reproducible on RHEL6.4? If so, can a system be made available to investigate? |