qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
	qemu-s390x@nongnu.org,  Eric Farman <farman@linux.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] pc-bios/s390-ccw/virtio-blkdev: Simplify/fix virtio_ipl_disk_is_valid()
Date: Fri, 24 Jun 2022 12:00:32 +0200	[thread overview]
Message-ID: <f8f6a5d9-5ec5-8cd3-ccc9-ff06a80e4a74@redhat.com> (raw)
In-Reply-To: <fe1d0e25-b582-0220-db7e-c69df5460f51@linux.ibm.com>

On 24/06/2022 11.20, Christian Borntraeger wrote:
> 
> 
> Am 24.06.22 um 10:50 schrieb Thomas Huth:
>> The s390-ccw bios fails to boot if the boot disk is a virtio-blk
>> disk with a sector size of 4096. For example:
>>
>>   dasdfmt -b 4096 -d cdl -y -p -M quick /dev/dasdX
>>   fdasd -a /dev/dasdX
>>   install a guest onto /dev/dasdX1 using virtio-blk
>>   qemu-system-s390x -nographic -hda /dev/dasdX1
> 
> Interestingly enough a real DASD (dasdX and not dasdX1) did work in the
> past and I also successfully uses an NVMe disk. So I guess the NVMe
> was 512 byte sector size then?

If you're using a full DASD, I think this was working thanks to the 
virtio_disk_is_eckd() function recognizing the geometry.

For NVMe disk - no clue. It either used 512 sectors, or it was at least 
accidentally still able to deal with the 512-byte sector requests after 
virtio_assume_scsi() "fixed" up the geometry. If you've got some spare 
minutes and still have access to those disks, it would be interesting to 
know if the boot still works there with my patches applied.

  Thomas



  reply	other threads:[~2022-06-24 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  8:50 [PATCH 0/2] Fix booting from non-DASD disks with sector size of 4096 Thomas Huth
2022-06-24  8:50 ` [PATCH 1/2] pc-bios/s390-ccw/virtio-blkdev: Simplify/fix virtio_ipl_disk_is_valid() Thomas Huth
2022-06-24  9:20   ` Christian Borntraeger
2022-06-24 10:00     ` Thomas Huth [this message]
2022-06-27  9:44   ` Thomas Huth
2022-06-24  8:50 ` [PATCH 2/2] pc-bios/s390-ccw/virtio-blkdev: Remove virtio_assume_scsi() Thomas Huth

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=f8f6a5d9-5ec5-8cd3-ccc9-ff06a80e4a74@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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).