tags 638574 + moreinfo unreproducible thanks On 20.08.2011 01:18, Michael Tokarev wrote: > On 20.08.2011 01:04, Josh Triplett wrote: >> Package: qemu-kvm >> Version: 0.14.1+dfsg-4 >> Severity: normal >> >> Running "kvm -cdrom some-bootable.iso" now results in a long delay >> waiting for iPXE to time out. OK, fair enough, I didn't specify how to >> boot, and kvm's autodetection now includes iPXE. However, I tried >> specifying "-boot d", and kvm still tried iPXE first. kvm should not >> try iPXE when it has an explicitly specified boot order that does not >> include network booting. > > This has been discussed upstream, the workaround currently is to > explicitly tell qemu to not load any boot roms for the NIC. > http://thread.gmane.org/gmane.comp.emulators.kvm.devel/77851/focus=77929 > for full thread and the solution. I suggested to stop loading the > PXE roms nedlessly - this way it will be possible to not install them, > http://thread.gmane.org/gmane.comp.emulators.kvm.devel/77851/focus=77929
And this is not all. Actually I can't reproduce your problem. Yes I see the iPXE boot _prompt_, but no attempt is made to actually boot from the network, unless you specified a non-bootable CDrom image. The fact that iPXE does prompt is well-known for a long time, it has been this way with etherboot too, see #585170. This is a problem with etherboot and now iPXE configuration, -- the boot pause has to be removed, see #625542 which is mentioned in #585170. Why it is so is a good question which I asked several times but got no answer. both etherboot and ipxe tries to ask for booting twice, first at init time and next at boot time. I can only guess it was done in order to work around some broken bioses. For qemu usage only one place should be used - during boot, not during init time, and no boot pause is intended. With old etherboot package it just failed to ask it all during init time due to a bug, in iPXE it has been now corrected. But I haven't seen that it actually boots from the network this way, if not counting the "explicit network at the end" case as described in the thread mentioned above, -- this actually does not apply to 0.14 version - with -boot d it does not try to boot from anything but cdrom. So tagging as such - unreproducible. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
