Re: [PATCH 0/4] nodedev: adjust handling DASDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On 6/19/24 5:10 PM, smitterl(a)redhat.com wrote:
> I am
> not aware of a "storage" option on command nodedev-list. My guess 
> is that your are referring to "nodedev-list --tree".
I meant the '--cap storage' option. But I see the '--tree' also works and it additionally displays the hierarchy that my test usually would traverse by checking dumpxml and there the parents.
> 
> The first three patches do not actually change existing behavior but 
> instead fix the problem described in the referenced issue.
> When the ccw device is configured (online) the relationships are and 
> also should have been as you describe above.
> 
> Theses patches are not modifying SCSI storage device node behavior.
Understood.

I was able to confirm that with the scratch build Jiŕi Denemark provided
a) the device is listed only once
b) the device' parent is correctly set (ccw instead of css)
c) no critical product regression hit in our test suite tp-libvirt for test set 'virsh.nodedev_list,virsh.nodedev_dumpxml'




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux