On 01/02/2017 09:25 AM, Ján Tomko wrote:
> On Fri, Nov 18, 2016 at 09:26:30AM -0500, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1349696
>>
>> When creating a vHBA, the process is to feed XML to nodeDeviceCreateXML
>> that lists the scsi_hostX to use to create the vHBA.
On Fri, Nov 18, 2016 at 09:26:30AM -0500, John Ferlan wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1349696
When creating a vHBA, the process is to feed XML to nodeDeviceCreateXML
that lists the scsi_hostX to use to create the vHBA. However,
between reboots, it's possible that the
On 12/13/2016 08:30 PM, John Ferlan wrote:
On 12/13/2016 10:58 AM, Boris Fiuczynski wrote:
John,
I have a concern regarding usage of the parent_fabric_name.
As far I have been told there are a lot of fc_host attributes in Linux
that are optional and left to the low-level driver to decide if
On 12/13/2016 10:58 AM, Boris Fiuczynski wrote:
> John,
> I have a concern regarding usage of the parent_fabric_name.
> As far I have been told there are a lot of fc_host attributes in Linux
> that are optional and left to the low-level driver to decide if
> implemented. fabric_name apparently
John,
I have a concern regarding usage of the parent_fabric_name.
As far I have been told there are a lot of fc_host attributes in Linux
that are optional and left to the low-level driver to decide if
implemented. fabric_name apparently happens to be one of these
attributes and I know an
https://bugzilla.redhat.com/show_bug.cgi?id=1349696
When creating a vHBA, the process is to feed XML to nodeDeviceCreateXML
that lists the scsi_hostX to use to create the vHBA. However,
between reboots, it's possible that the changes its scsi_hostX
to scsi_hostY and saved XML to perform the