* On Sunday 27 Jul 2008 23:02:06 Farkas Levente wrote: > Greg Kurtzer wrote: > > On Sat, Jul 26, 2008 at 1:12 AM, Avi Kivity <[EMAIL PROTECTED]> wrote: > >> Greg Kurtzer wrote: > >>> Hello, > >>> > >>> I noticed some problems with the e1000 implementation in kvm >= 70. At > >>> first glance it seemed liked a PXE problem as it would not acknowledge > >>> the DHCP offer from the server. I tried several different Etherboot > >>> ROM images and version 5.2.6 seemed to work. That version isn't PXE > >>> compliant so I built an ELF image to boot, and it downloaded it very, > >>> very, very, very slowly (as in about 10 minutes) but it did end up > >>> working. > >>> > >>> This all worked perfectly with version 69 and previous. > >> > >> There are two patches to e1000 in kvm-70; can you try backing them out > >> (patch -Rp1 < test.patch) to see which one is guilty? > >> > >> Candidates attached. > > > > Reverted both of these patches yet the problem remains. :( > > > > This is easy to reproduce (at least on my build). if there is a DHCP > > server on the network, just do a network boot on the e1000. It makes a > > correct DHCPDISCOVER, but never responds to the DHCPOFFER (it should > > do a DHCPREQUEST next). No packets are getting lost according tcpdump > > on the master. > > > > The console is showing: > > > > Probing pci nic... > > [e1000-82540em]Ethernet addr: 00:04:21:DE:99:55 > > Searching for server (DHCP)....No IP address > > .No IP address > > .No IP address > > .No IP address > > .No IP address > > .No IP address > > .No IP address > > ... > > the same happend with us both with e1000 and rtl8139 driver and the rh > guy said it's not a virt-manager problem... > currently we're not able to pxe boot any kind of kvm guest with any > network driver:-(
Is it related to tap? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
