All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farhan Ali <alifm@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-devel@nongnu.org, farman@linux.vnet.ibm.com,
	walling@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] s390-ccw: Fix alignment for CCW1
Date: Tue, 29 Aug 2017 08:39:27 -0400	[thread overview]
Message-ID: <ffe9c512-4238-7456-27d2-cdc8fa39d8e0@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170829140429.08a1731c.cohuck@redhat.com>



On 08/29/2017 08:04 AM, Cornelia Huck wrote:
> On Mon, 28 Aug 2017 10:28:53 -0400
> Farhan Ali <alifm@linux.vnet.ibm.com> wrote:
>
>> On 08/28/2017 10:19 AM, Halil Pasic wrote:
>>>
>>>
>>> On 08/28/2017 04:15 PM, Farhan Ali wrote:
>>>>
>>>>
>>>> On 08/28/2017 10:05 AM, Cornelia Huck wrote:
>>>>>>>> It's the alignment of the CCW which causes the problem.
>>>>>>>>
>>>>>>>> The exact error message when starting the guest was:
>>>>>>>>
>>>>>>>> ! No virtio device found !
>>>>>>>>
>>>>>>>> Since it worked for SCSI and CDL, and failed for LDL disks on that particular system, we are not really sure what caused the failure.
>>>>>>>> Debugging it further showed the CCW for LDL disks were not aligned at double word boundary.
>>>>> This is really, really odd, as the low-level ccw code is the same for
>>>>> any disk type...
>>>>>
>>>> Exactly!
>>>>
>>>>>>>> Trying the test on a different system with LDL disks worked fine, with the aligned(8) fix.
>>>>>>> Do you happen to have an old s390-ccw.img laying around in the test folder? QEMU might pick up
>>>>>>> this one (e.g. when calling it without libvirt from the command line).
>>>>>>>
>>>>>> I explicitly mention the bios to use with '-bios' option and pick up the
>>>>>> latest bios. Without the aligned fix I see the error and with the fix it
>>>>>> works fine.
>>>>> Wait, so the fix fixes it? Or am I confused now?
>>>>>
>>>>
>>>> It fixes in my system and one other system we tried on. But fails on a system where this issue was first noticed.
>>>
>>> This is very confusing. So you have tried -bios on the system
>>> where the issue was first noticed and the issue still persists
>>> despite of the fixed bios is specified?
>>>
>> Yes.
>>
>> The system where the issue was first noticed, applying the fix for the
>> bios, fixes for:
>>
>> 1) CDL disks
>> 2) SCSI disks
>>
>> But fails for LDL disk.
>>
>> On my system and one other system, the fix works for all the disk types,
>> CDL, SCSI and LDL and fixes the issue.
>
> Are you using different toolchains on the failing and the working
> systems? Does it work when you copy the bios from a working system?
>
> (Clutching at straws here...)
>

So yesterday we realized for the failing system, the bios wasn't being 
built on that system rather it was being built on a different system and 
being copied over to the failing system. :/

Building the bios on the failing system with the fix, resolves the issue 
and we did not see anymore failures.
So I think I can safely say this patch fixes the alignment problem.

  reply	other threads:[~2017-08-29 12:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1503667215.git.alifm@linux.vnet.ibm.com>
2017-08-25 13:24 ` [Qemu-devel] [PATCH] s390-ccw: Fix alignment for CCW1 Farhan Ali
2017-08-25 13:55   ` no-reply
2017-08-25 14:04   ` Cornelia Huck
2017-08-25 15:05     ` Farhan Ali
2017-08-28  8:22       ` Cornelia Huck
2017-08-28 12:56         ` Farhan Ali
2017-08-28 13:06           ` Cornelia Huck
2017-08-28 13:18             ` Farhan Ali
2017-08-28 13:24               ` Christian Borntraeger
2017-08-28 13:52                 ` Farhan Ali
2017-08-28 14:05                   ` Cornelia Huck
2017-08-28 14:15                     ` Farhan Ali
2017-08-28 14:19                       ` Halil Pasic
2017-08-28 14:28                         ` Farhan Ali
2017-08-29 12:04                           ` Cornelia Huck
2017-08-29 12:39                             ` Farhan Ali [this message]
2017-08-29 12:45                               ` Cornelia Huck
2017-08-29 18:45                                 ` Eric Farman
2017-08-30  7:27                                   ` Cornelia Huck
2017-08-28 15:04                       ` Philippe Mathieu-Daudé
2017-08-28 18:47                         ` Farhan Ali

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=ffe9c512-4238-7456-27d2-cdc8fa39d8e0@linux.vnet.ibm.com \
    --to=alifm@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=walling@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.