[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-12-02 Thread Sebastian Herbszt
Gleb Natapov wrote: How can we get to EDD info after device is mapped? Looking at Seabios implementation it builds EDD table on the fly when int_1348 is called and it does it only for internal devices. Can we use "disconnect vector" to connect device temporarily get EDD and then disconnect? Fr

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-12-02 Thread Gleb Natapov
On Thu, Dec 02, 2010 at 04:07:16PM +0100, Peter Stuge wrote: > Gleb Natapov wrote: > > BBS specification is broken since it doesn't provide a way for > > discovered boot method (BCV) to be linked back to a device it will > > boot from. Nothing we can do to fix this except moving to EFI (an > > hope

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-12-02 Thread Peter Stuge
Gleb Natapov wrote: > BBS specification is broken since it doesn't provide a way for > discovered boot method (BCV) to be linked back to a device it will > boot from. Nothing we can do to fix this except moving to EFI (an > hope the problem is fixed there). There is that option, or there could be

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-11-28 Thread Gleb Natapov
On Sun, Nov 28, 2010 at 08:11:45PM +0100, Peter Stuge wrote: > Peter Stuge wrote: > > Specifying boot device using PCI BDF is a great example of using > > common structured data. That BDF exists both in machine and firmware > > data models. > > Gleb Natapov wrote: > > Bus numbers are assigned by a

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-11-28 Thread Gleb Natapov
On Sun, Nov 28, 2010 at 08:00:29PM +0100, Peter Stuge wrote: > Gleb Natapov wrote: > > There is no way for qemu to know about BCVs or BEVs > > This is very much the key point. > > In order to have command line control over the boot process, the > machine and the firmware must agree on things. >

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-11-28 Thread Peter Stuge
Peter Stuge wrote: > Specifying boot device using PCI BDF is a great example of using > common structured data. That BDF exists both in machine and firmware > data models. Gleb Natapov wrote: > Bus numbers are assigned by a guest. Qemu knows nothing about them, > so it specify device path by topol

[Qemu-devel] Re: [SeaBIOS] [PATCHv6 00/16] boot order specification

2010-11-28 Thread Peter Stuge
Gleb Natapov wrote: > There is no way for qemu to know about BCVs or BEVs This is very much the key point. In order to have command line control over the boot process, the machine and the firmware must agree on things. I see two options: 1. QEMU works very very hard to provide a machine that wi