qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Passing boot order from qemu to seabios
Date: Mon, 11 Oct 2010 12:32:48 +0200	[thread overview]
Message-ID: <4CB2E7D0.1010702@redhat.com> (raw)
In-Reply-To: <20101011101855.GA25030@redhat.com>

Am 11.10.2010 12:18, schrieb Gleb Natapov:
> Currently if VM is started with multiple disks it is almost impossible to
> guess which one of them will be used as boot device especially if there
> is a mix of ATA/virtio/SCSI devices. Essentially BIOS decides the order
> and without looking into the code you can't tell what the order will
> be (and in qemu-kvm if boot=on is used it brings even more havoc). We
> should allow fine-grained control of boot order from qemu command line,
> or as a minimum control what device will be used for booting.
> 
> To do that along with inventing syntax to specify boot order on qemu
> command line we need to communicate boot order to seabios via fw_cfg
> interface. For that we need to have a way to unambiguously specify a
> disk from qemu to seabios.  PCI bus address is not enough since not all
> devices are PCI (do we care about them?) 

Floppy? Yes, I think we do.

> and since one PCI device may
> control more then one disk (ATA slave/master, SCSI LUNs). We can do what
> EDD specification does. Describe disk as:
>     bus type (isa/pci),
>     address on a bus (16 bit base address for isa, b/s/f for pci)
>     device type (ATA/SCSI/VIRTIO)
>     device path (slave/master for ATA, LUN for SCSI, nothing for virtio)

If we had a qdev ID for all devices (which I think we should have
anyway), would this work or is a string not really handy enough?

Kevin

  reply	other threads:[~2010-10-11 10:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 10:18 [Qemu-devel] [RFC] Passing boot order from qemu to seabios Gleb Natapov
2010-10-11 10:32 ` Kevin Wolf [this message]
2010-10-11 10:43   ` Gleb Natapov
2010-10-11 11:01     ` Kevin Wolf
2010-10-11 12:07   ` Gerd Hoffmann
2010-10-11 12:16     ` Gleb Natapov
2010-10-11 19:48       ` [SeaBIOS] " Anthony Liguori
2010-10-11 19:59         ` Gleb Natapov
2010-10-11 20:30           ` Anthony Liguori
2010-10-11 20:36             ` Gleb Natapov
2010-10-11 20:50               ` Anthony Liguori
2010-10-11 21:14                 ` Gleb Natapov
2010-10-11 21:15             ` H. Peter Anvin
2010-10-11 21:41               ` Sebastian Herbszt
2010-10-11 21:51                 ` H. Peter Anvin
2010-10-12  8:01               ` Gleb Natapov
2010-10-12 16:33                 ` H. Peter Anvin
2010-10-12 16:56                   ` Gleb Natapov
2010-10-12 17:35                     ` H. Peter Anvin
2010-10-12 17:41                       ` Gleb Natapov
2010-10-12 17:45                         ` H. Peter Anvin
2010-10-12 19:06                           ` Gleb Natapov
2010-10-13 19:17                             ` H. Peter Anvin
2010-10-13 20:00                               ` H. Peter Anvin
2010-10-13 20:22                                 ` H. Peter Anvin
2010-10-11 19:51     ` Anthony Liguori
2010-10-11 20:02       ` Gleb Natapov
2010-10-11 20:18       ` [SeaBIOS] " H. Peter Anvin
2010-10-11 11:16 ` Bernhard Kohl
2010-10-11 12:08   ` Gleb Natapov
2010-10-11 23:33     ` [SeaBIOS] " Kevin O'Connor
2010-10-11 12:48   ` Stefan Hajnoczi
2010-10-11 14:29     ` Gleb Natapov
2010-10-11 15:52       ` Stefan Hajnoczi
2010-10-11 16:04         ` Gleb Natapov
2010-10-11 17:01         ` Anthony Liguori
2010-10-11 17:04           ` Gleb Natapov
2010-10-11 23:16             ` [SeaBIOS] " Kevin O'Connor
2010-10-12  8:44             ` Stefan Hajnoczi
2010-10-11 15:09 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2010-10-11 15:39   ` Gleb Natapov
2010-10-11 15:42     ` Avi Kivity
2010-10-11 15:52       ` Gleb Natapov
2010-10-12  0:08 ` Kevin O'Connor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB2E7D0.1010702@redhat.com \
    --to=kwolf@redhat.com \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).