On 20/08/14 15:10, Paolo Bonzini wrote:
Il 20/08/2014 11:35, Christian Borntraeger ha scritto:
On 20/08/14 10:19, Paolo Bonzini wrote:
Il 29/07/2014 14:27, Ekaterina Tumanova ha scritto:
The new HDIO_GETGEO logic is required for two use cases:
a) Support for geometries of Direct Attached
Il 29/07/2014 14:27, Ekaterina Tumanova ha scritto:
The new HDIO_GETGEO logic is required for two use cases:
a) Support for geometries of Direct Attached Storage Disks (DASD)
on s390x configured as backing of virtio block devices.
Is this still relevant now that QEMU can emulate 512-byte
On 20/08/14 10:19, Paolo Bonzini wrote:
Il 29/07/2014 14:27, Ekaterina Tumanova ha scritto:
The new HDIO_GETGEO logic is required for two use cases:
a) Support for geometries of Direct Attached Storage Disks (DASD)
on s390x configured as backing of virtio block devices.
Is this still
Il 20/08/2014 11:35, Christian Borntraeger ha scritto:
On 20/08/14 10:19, Paolo Bonzini wrote:
Il 29/07/2014 14:27, Ekaterina Tumanova ha scritto:
The new HDIO_GETGEO logic is required for two use cases:
a) Support for geometries of Direct Attached Storage Disks (DASD)
on s390x configured as
This patch extends the function hd_geometry_guess. It introduces a
target specific hook. The default implementation for this target
specific hook is empty, has therefore no effect and the existing logic
works as before.
For target-s390x, the behaviour is chosen as follows:
If no geo could be
