There seems to be an issue with kvm virtual network interface being connected to a in-kernel bridge implementation.
When you configure networking that way the bridge port comes up when the kvm instance is started. As the time from the kvm start to entering the netboot rom is minimal and the timeout before the bridge starts forwarding on new ports is long this may cause the machine never getting an address. If you are using a bridge try setting the forwarding delay to a small value like: iface vmbridge inet static bridge_ports <probably should put some network interface name here - undocumented> address 10.10.10.1 netmask 255.255.255.0 post-up brctl setfd vmbridge 3 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/588731 Title: PXE boot not working Status in QEMU: Incomplete Bug description: /root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net tap,vlan=0,name=tap.0 -boot n -net nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait -monitor chardev:monitor net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035) No more network devices No bootable device. After doing a system_reset .... net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] DHCP (net0 02:5a:3b:27:00:a1).... ok net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1 Booting from filename "boot.pxe" tftp://x.x.x./boot.pxe.. ok And it magaically works. using HEAD. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/588731/+subscriptions
