On 05/08/2017 03:00 AM, Christian Borntraeger wrote:
On 05/06/2017 10:24 AM, Paolo Bonzini wrote:
On 05/05/2017 18:12, Eric Farman wrote:
On 05/05/2017 11:13 AM, Paolo Bonzini wrote:
On 05/05/2017 17:03, Eric Farman wrote:
We get a value of x3f when sending that to a scsi-disk fro
On 05/06/2017 10:24 AM, Paolo Bonzini wrote:
>
>
> On 05/05/2017 18:12, Eric Farman wrote:
>>
>>
>> On 05/05/2017 11:13 AM, Paolo Bonzini wrote:
>>>
>>>
>>> On 05/05/2017 17:03, Eric Farman wrote:
We get a value of x3f when sending that to a scsi-disk from bios
code. That's fully e
On 05/05/2017 18:12, Eric Farman wrote:
>
>
> On 05/05/2017 11:13 AM, Paolo Bonzini wrote:
>>
>>
>> On 05/05/2017 17:03, Eric Farman wrote:
>>> We get a value of x3f when sending that to a scsi-disk from bios
>>> code. That's fully emulated though, in scsi_disk_emulate_inquiry. And
>>> th
On 05/05/2017 11:13 AM, Paolo Bonzini wrote:
On 05/05/2017 17:03, Eric Farman wrote:
We get a value of x3f when sending that to a scsi-disk from bios
code. That's fully emulated though, in scsi_disk_emulate_inquiry. And
that's the scenario that already works.
While there is indeed cod
On 05/05/2017 17:03, Eric Farman wrote:
> We get a value of x3f when sending that to a scsi-disk from bios
> code. That's fully emulated though, in scsi_disk_emulate_inquiry. And
> that's the scenario that already works.
>
> While there is indeed code in hw/scsi/scsi-generic.c to wire that
On 05/05/2017 03:41 AM, Fam Zheng wrote:
On Wed, 04/26 16:46, Eric Farman wrote:
The short version of what happens is the host device driver rejects our
requests because the transfer lengths are too long for it to satisfy.
A virtio-scsi disk connected via scsi-generic is fine as a non-boot dev
On Wed, 04/26 16:46, Eric Farman wrote:
> The short version of what happens is the host device driver rejects our
> requests because the transfer lengths are too long for it to satisfy.
> A virtio-scsi disk connected via scsi-generic is fine as a non-boot device
> because the guest kernel is able t
On 04/26/2017 11:48 AM, Christian Borntraeger wrote:
On 04/26/2017 04:46 PM, Eric Farman wrote:
Today, trying to boot a guest from a SCSI LUN on s390x yields the following:
virtio-blk = OK
virtio-scsi and /dev/sdX = OK
virtio-scsi and /dev/sgX = FAIL
Example of the failin
On 04/26/2017 04:46 PM, Eric Farman wrote:
> Today, trying to boot a guest from a SCSI LUN on s390x yields the following:
>
> virtio-blk = OK
> virtio-scsi and /dev/sdX = OK
> virtio-scsi and /dev/sgX = FAIL
>
> Example of the failing scenario:
>
> /usr/bin/qemu-system-s390
Today, trying to boot a guest from a SCSI LUN on s390x yields the following:
virtio-blk = OK
virtio-scsi and /dev/sdX = OK
virtio-scsi and /dev/sgX = FAIL
Example of the failing scenario:
/usr/bin/qemu-system-s390x ...
-device virtio-scsi-ccw,id=scsi0,devno=fe.0.0001
10 matches
Mail list logo
