On Thu, May 13, 2010 at 07:49:40PM +0300, Avi Kivity wrote:
> On 05/10/2010 06:58 PM, Anthony Liguori wrote:
> >>Isn't this problem unrelated to this patch? I mean if I start qemu with
> >>two ide devices can I specify from qemu command line which one I want to
> >>boot from?
> >
> >That's sort of
On 05/10/2010 06:58 PM, Anthony Liguori wrote:
Isn't this problem unrelated to this patch? I mean if I start qemu with
two ide devices can I specify from qemu command line which one I want to
boot from?
That's sort of what I'm asking. If you compare this approach to
extboot, extboot provided
On Tue, May 11, 2010 at 03:47:40PM +0300, Gleb Natapov wrote:
> On Tue, May 11, 2010 at 08:45:29AM -0400, Kevin O'Connor wrote:
> > On Tue, May 11, 2010 at 10:04:25AM +0100, Stefan Hajnoczi wrote:
> > > From what I can tell SeaBIOS is reading CMOS_BIOS_BOOTFLAG1 and
> > > CMOS_BIOS_BOOTFLAG2 from n
On Tue, May 11, 2010 at 08:45:29AM -0400, Kevin O'Connor wrote:
> On Tue, May 11, 2010 at 10:04:25AM +0100, Stefan Hajnoczi wrote:
> > From what I can tell SeaBIOS is reading CMOS_BIOS_BOOTFLAG1 and
> > CMOS_BIOS_BOOTFLAG2 from non-volatile memory. The values index into
> > bev[], which contains I
On Tue, May 11, 2010 at 10:04:25AM +0100, Stefan Hajnoczi wrote:
> From what I can tell SeaBIOS is reading CMOS_BIOS_BOOTFLAG1 and
> CMOS_BIOS_BOOTFLAG2 from non-volatile memory. The values index into
> bev[], which contains IPL entries (the drives).
>
> Is the order of bev[] entries well-defined
