qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Sam Eiderman <shmuel.eiderman@oracle.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, arbel.moshe@oracle.com,
	seabios@seabios.org, qemu-devel@nongnu.org, mreitz@redhat.com,
	kevin@koconnor.net, liran.alon@oracle.com,
	karl.heubaum@oracle.com
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH v4 0/5] Add Qemu to SeaBIOS LCHS interface
Date: Mon, 1 Jul 2019 09:44:51 +0200	[thread overview]
Message-ID: <20190701074451.apgschleugyxxbwr@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190626123816.8907-1-shmuel.eiderman@oracle.com>

On Wed, Jun 26, 2019 at 03:38:11PM +0300, Sam Eiderman wrote:
> v1:
> 
> Non-standard logical geometries break under QEMU.
> 
> A virtual disk which contains an operating system which depends on
> logical geometries (consistent values being reported from BIOS INT13
> AH=08) will most likely break under QEMU/SeaBIOS if it has non-standard
> logical geometries - for example 56 SPT (sectors per track).
> No matter what QEMU will guess - SeaBIOS, for large enough disks - will
> use LBA translation, which will report 63 SPT instead.
> 
> In addition we can not enforce SeaBIOS to rely on phyiscal geometries at
> all. A virtio-blk-pci virtual disk with 255 phyiscal heads can not
> report more than 16 physical heads when moved to an IDE controller, the
> ATA spec allows a maximum of 16 heads - this is an artifact of
> virtualization.
> 
> By supplying the logical geometies directly we are able to support such
> "exotic" disks.
> 
> We will use fw_cfg to do just that.
> 
> v2:
> 
> Rename bootdevices fw_cfg key to bios-geoemtry
> 
> v3:
> 
> Change fw_cfg interface from mixed binary/textual to textual only
> Squash commit "config: Add toggle for bootdevice information"
> 
> v4:
> 
> * Rename TRANSLATION_MACHINE to TRANSLATION_HOST
> * Rename "overriden" translation name to "host-supplied"
> * Rename overriden_lchs_supplied() to host_lchs_supplied()
> * Move sectors and heads check to host_lchs_supplied()
> * Reuse duplicate code in boot.c

Looks all sane to me.

Usual workflow is to have to qemu bits merged first, so we'll go wait
for that.

cheers,
  Gerd



      parent reply	other threads:[~2019-07-01  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 12:38 [Qemu-devel] [SeaBIOS] [PATCH v4 0/5] Add Qemu to SeaBIOS LCHS interface Sam Eiderman
2019-06-26 12:38 ` [Qemu-devel] [SeaBIOS] [PATCH v4 1/5] geometry: Read LCHS from fw_cfg Sam Eiderman
2019-06-26 12:38 ` [Qemu-devel] [SeaBIOS] [PATCH v4 2/5] boot: Reorder functions in boot.c Sam Eiderman
2019-06-26 12:38 ` [Qemu-devel] [SeaBIOS] [PATCH v4 3/5] boot: Build ata and scsi paths in function Sam Eiderman
2019-06-26 12:38 ` [Qemu-devel] [SeaBIOS] [PATCH v4 4/5] geometry: Add boot_lchs_find_*() utility functions Sam Eiderman
2019-06-26 12:38 ` [Qemu-devel] [SeaBIOS] [PATCH v4 5/5] geometry: Apply LCHS values for boot devices Sam Eiderman
2019-07-01  7:44 ` Gerd Hoffmann [this message]

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=20190701074451.apgschleugyxxbwr@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=arbel.moshe@oracle.com \
    --cc=karl.heubaum@oracle.com \
    --cc=kevin@koconnor.net \
    --cc=kwolf@redhat.com \
    --cc=liran.alon@oracle.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=shmuel.eiderman@oracle.com \
    /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).