* [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs @ 2010-08-01 9:44 Michael Tokarev 2010-08-01 20:27 ` Stefan Hajnoczi 0 siblings, 1 reply; 6+ messages in thread From: Michael Tokarev @ 2010-08-01 9:44 UTC (permalink / raw) To: qemu-devel I wonder why with etherboot ROMs, the network boot happens two times (0.12.x), like this: ----- Starting SeaBIOS (version 0.5.1-20100801_125707-gandalf) Booting from virtio-net.zrom 5.4.4 (GPL) ether... ROM segment 0xc900 length 0x8000 reloc 0x00000000 Etherboot 5.4.4 (GPL) http://etherboot.org Drivers: VIRTIO-NET Images: NBI ELF PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [00087780,0009f310) to [07ee8470,07f00000) Boot from (N)etwork or (Q)uit? Probing pci nic... Probing isa nic... <sleep> Boot from (N)etwork or (Q)uit? Probing pci nic... [virtio-net]I/O address 0x0000c020, IRQ #11 MAC address 52:54:00:12:34:56 Searching for server (DHCP).... ----- The boot ROMs supplied with the source works as expected. What's the difference? Is gpxe behaves differently, or is that a difference in build options? (This applies to both qemu and qemu-kvm). Thanks! /mjt ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs 2010-08-01 9:44 [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs Michael Tokarev @ 2010-08-01 20:27 ` Stefan Hajnoczi 2010-08-02 16:23 ` Gianni Tedesco 0 siblings, 1 reply; 6+ messages in thread From: Stefan Hajnoczi @ 2010-08-01 20:27 UTC (permalink / raw) To: Michael Tokarev; +Cc: qemu-devel, gpxe-devel On Sun, Aug 1, 2010 at 10:44 AM, Michael Tokarev <mjt@tls.msk.ru> wrote: > I wonder why with etherboot ROMs, the network boot > happens two times (0.12.x), like this: > > ----- > Starting SeaBIOS (version 0.5.1-20100801_125707-gandalf) > > Booting from virtio-net.zrom 5.4.4 (GPL) ether... > ROM segment 0xc900 length 0x8000 reloc 0x00000000 > Etherboot 5.4.4 (GPL) http://etherboot.org > Drivers: VIRTIO-NET Images: NBI ELF PXE Exports: PXE > Protocols: DHCP TFTP > Relocating _text from: [00087780,0009f310) to [07ee8470,07f00000) > Boot from (N)etwork or (Q)uit? > > Probing pci nic... > Probing isa nic... > <sleep> > Boot from (N)etwork or (Q)uit? > > Probing pci nic... > [virtio-net]I/O address 0x0000c020, IRQ #11 > MAC address 52:54:00:12:34:56 > Searching for server (DHCP).... > ----- > > The boot ROMs supplied with the source works as expected. > > What's the difference? Is gpxe behaves differently, or > is that a difference in build options? Etherboot and gPXE are different codebases. gPXE was forked from Etherboot around 2005 and is now very different. The Etherboot and gPXE behavior cannot always be compared, they are not meant to work the same. CCed gPXE mailing list. Stefan > (This applies to both qemu and qemu-kvm). > > Thanks! > > /mjt > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs 2010-08-01 20:27 ` Stefan Hajnoczi @ 2010-08-02 16:23 ` Gianni Tedesco 2010-08-02 16:43 ` Michael Tokarev 0 siblings, 1 reply; 6+ messages in thread From: Gianni Tedesco @ 2010-08-02 16:23 UTC (permalink / raw) To: Stefan Hajnoczi; +Cc: Michael Tokarev, qemu-devel, gpxe-devel@etherboot.org On Sun, 2010-08-01 at 21:27 +0100, Stefan Hajnoczi wrote: > On Sun, Aug 1, 2010 at 10:44 AM, Michael Tokarev <mjt@tls.msk.ru> wrote: > > I wonder why with etherboot ROMs, the network boot > > happens two times (0.12.x), like this: > > > > ----- > > Starting SeaBIOS (version 0.5.1-20100801_125707-gandalf) > > > > Booting from virtio-net.zrom 5.4.4 (GPL) ether... > > ROM segment 0xc900 length 0x8000 reloc 0x00000000 > > Etherboot 5.4.4 (GPL) http://etherboot.org > > Drivers: VIRTIO-NET Images: NBI ELF PXE Exports: PXE > > Protocols: DHCP TFTP > > Relocating _text from: [00087780,0009f310) to [07ee8470,07f00000) > > Boot from (N)etwork or (Q)uit? > > > > Probing pci nic... > > Probing isa nic... > > <sleep> > > Boot from (N)etwork or (Q)uit? > > > > Probing pci nic... > > [virtio-net]I/O address 0x0000c020, IRQ #11 > > MAC address 52:54:00:12:34:56 > > Searching for server (DHCP).... > > ----- > > > > The boot ROMs supplied with the source works as expected. > > > > What's the difference? Is gpxe behaves differently, or > > is that a difference in build options? > > Etherboot and gPXE are different codebases. gPXE was forked from > Etherboot around 2005 and is now very different. The Etherboot and > gPXE behavior cannot always be compared, they are not meant to work > the same. The BIOS boot protocol allows to continue from next device if an earlier boot method doesn't work. In the real hardware the ROM typically only supports one type of card. Therefore a ROM ought to be loaded and tried from each NIC until one of the attempts successfully boots or there are no more to try. Anyway, you will need to post more info on your setup: what and how many NIC's, where the ROM binaries came from... Gianni Tedesco ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs 2010-08-02 16:23 ` Gianni Tedesco @ 2010-08-02 16:43 ` Michael Tokarev 2010-08-02 18:14 ` Stefan Hajnoczi 0 siblings, 1 reply; 6+ messages in thread From: Michael Tokarev @ 2010-08-02 16:43 UTC (permalink / raw) To: Gianni Tedesco; +Cc: Stefan Hajnoczi, qemu-devel, gpxe-devel@etherboot.org 02.08.2010 20:23, Gianni Tedesco wrote: > On Sun, 2010-08-01 at 21:27 +0100, Stefan Hajnoczi wrote: >> On Sun, Aug 1, 2010 at 10:44 AM, Michael Tokarev <mjt@tls.msk.ru> wrote: >>> I wonder why with etherboot ROMs, the network boot >>> happens two times (0.12.x), like this: >>> >>> ----- >>> Starting SeaBIOS (version 0.5.1-20100801_125707-gandalf) >>> >>> Booting from virtio-net.zrom 5.4.4 (GPL) ether... >>> ROM segment 0xc900 length 0x8000 reloc 0x00000000 >>> Etherboot 5.4.4 (GPL) http://etherboot.org >>> Drivers: VIRTIO-NET Images: NBI ELF PXE Exports: PXE >>> Protocols: DHCP TFTP >>> Relocating _text from: [00087780,0009f310) to [07ee8470,07f00000) >>> Boot from (N)etwork or (Q)uit? >>> >>> Probing pci nic... >>> Probing isa nic... >>> <sleep> >>> Boot from (N)etwork or (Q)uit? >>> >>> Probing pci nic... >>> [virtio-net]I/O address 0x0000c020, IRQ #11 >>> MAC address 52:54:00:12:34:56 >>> Searching for server (DHCP).... >>> ----- >>> >>> The boot ROMs supplied with the source works as expected. >>> >>> What's the difference? Is gpxe behaves differently, or >>> is that a difference in build options? >> >> Etherboot and gPXE are different codebases. gPXE was forked from >> Etherboot around 2005 and is now very different. The Etherboot and >> gPXE behavior cannot always be compared, they are not meant to work >> the same. I never supposed it should work the same. I wondered why etherboot shows somewhat weird behavour. > The BIOS boot protocol allows to continue from next device if an earlier > boot method doesn't work. In the real hardware the ROM typically only > supports one type of card. Therefore a ROM ought to be loaded and tried > from each NIC until one of the attempts successfully boots or there are > no more to try. That's quite understandable. But I _guess_ it's a bit more than that, like, just from the wild, different paths or busses to the _same_ device (say, PCI and ISA). > Anyway, you will need to post more info on your setup: what and how many > NIC's, where the ROM binaries came from... There's no info to post. Standard qemu-kvm (or qemu) 0.12.[45], and standard etherboot boot rom (from rom-o-matic will do too), without any extra options. Only one NIC in a virtual machine, like this: kvm -net nic,model=rtl8139 -net tap -boot n (no other options; model does not matter as long as the right pxe ROM can be found). The boot ROMs are searched in, depending on the qemu/kvm configuration, /usr/share/kvm/. If I put gpxe ones in there, I see only one, successful, attempt to boot. If I put etherboot rom, there will be two attempts, first unsuccessful. Not that it is a big issue, just... weird, and annoying -- in Debian for example we (re)build boot ROMs during package build instead of using the ones supplied in the source tarball, and currently gpxe isn't packages in debian, but etherboot behaves somewhat erratically (but works in the end), so I wondered what the issue is. Thanks! /mjt ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs 2010-08-02 16:43 ` Michael Tokarev @ 2010-08-02 18:14 ` Stefan Hajnoczi 2010-08-02 20:08 ` [gPXE-devel] " Marty Connor 0 siblings, 1 reply; 6+ messages in thread From: Stefan Hajnoczi @ 2010-08-02 18:14 UTC (permalink / raw) To: Michael Tokarev; +Cc: qemu-devel, Gianni Tedesco, gpxe-devel@etherboot.org On Mon, Aug 2, 2010 at 5:43 PM, Michael Tokarev <mjt@tls.msk.ru> wrote: > Not that it is a big issue, just... weird, and annoying -- > in Debian for example we (re)build boot ROMs during > package build instead of using the ones supplied in > the source tarball, and currently gpxe isn't packages > in debian, but etherboot behaves somewhat erratically > (but works in the end), so I wondered what the issue is. The issue holding back gPXE from Debian is licensing clarification AFAIK. There is nothing there that can't be tackled but the process has stalled unfortunately. It would be great to have gPXE in Debian. Stefan ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gPXE-devel] [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs 2010-08-02 18:14 ` Stefan Hajnoczi @ 2010-08-02 20:08 ` Marty Connor 0 siblings, 0 replies; 6+ messages in thread From: Marty Connor @ 2010-08-02 20:08 UTC (permalink / raw) To: Stefan Hajnoczi Cc: Michael Tokarev, qemu-devel, Gianni Tedesco, gpxe-devel@etherboot.org On 8/2/10 2:14 PM, Stefan Hajnoczi wrote: > On Mon, Aug 2, 2010 at 5:43 PM, Michael Tokarev <mjt@tls.msk.ru> wrote: >> Not that it is a big issue, just... weird, and annoying -- >> in Debian for example we (re)build boot ROMs during >> package build instead of using the ones supplied in >> the source tarball, and currently gpxe isn't packages >> in debian, but etherboot behaves somewhat erratically >> (but works in the end), so I wondered what the issue is. > > The issue holding back gPXE from Debian is licensing clarification > AFAIK. There is nothing there that can't be tackled but the process > has stalled unfortunately. It would be great to have gPXE in Debian. > > Stefan We definitely have not forgotten about Debian licensing issues, and in a few weeks after Google Summer of Code is over we'll go through http://support.etherboot.org/ and deal with licensing as well as some other issues we haven't gotten to yet. Thanks for reminding us about this. / Marty / ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-08-02 20:08 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-08-01 9:44 [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs Michael Tokarev 2010-08-01 20:27 ` Stefan Hajnoczi 2010-08-02 16:23 ` Gianni Tedesco 2010-08-02 16:43 ` Michael Tokarev 2010-08-02 18:14 ` Stefan Hajnoczi 2010-08-02 20:08 ` [gPXE-devel] " Marty Connor
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).