search for: scsi_host6

...as a live device - I get: 2016-02-01 21:30:24.216+0000: 129764: debug : qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none) 2016-02-01 21:30:24.216+0000: 129764: error : virDomainDeviceDefParse:8136 : XML error: unknown device type Could you please help? virsh # nodedev-dumpxml scsi_host6 <device> <name>scsi_host6</name> <parent>pci_0000_08_00_0</parent> <capability type='scsi_host'> <host>6</host> <capability type='fc_host'> <wwnn>20000024ff57d848</wwnn> <wwpn>21000024f...

...21:30:24.216+0000: 129764: debug : > qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none) > 2016-02-01 21:30:24.216+0000: 129764: error : > virDomainDeviceDefParse:8136 : XML error: unknown device type > > Could you please help? > > virsh # nodedev-dumpxml scsi_host6 > <device> > <name>scsi_host6</name> > <parent>pci_0000_08_00_0</parent> > <capability type='scsi_host'> > <host>6</host> > <capability type='fc_host'> > <wwnn>20000024ff57d848</w...

...; 2016-02-01 21:30:24.216+0000: 129764: debug : qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none) > 2016-02-01 21:30:24.216+0000: 129764: error : virDomainDeviceDefParse:8136 : XML error: unknown device type > > Could you please help? > > virsh # nodedev-dumpxml scsi_host6 > <device> > <name>scsi_host6</name> > <parent>pci_0000_08_00_0</parent> > <capability type='scsi_host'> > <host>6</host> > <capability type='fc_host'> > <wwnn>20000024ff57d848</w...

...64: debug : >> qemuDomainObjBeginJobInternal:847 : Starting job: modify (async=none) >> 2016-02-01 21:30:24.216+0000: 129764: error : >> virDomainDeviceDefParse:8136 : XML error: unknown device type >> >> Could you please help? >> >> virsh # nodedev-dumpxml scsi_host6 >> <device> >> <name>scsi_host6</name> >> <parent>pci_0000_08_00_0</parent> >> <capability type='scsi_host'> >> <host>6</host> >> <capability type='fc_host'> >>...

...ype='scsi_host'> <capability type='fc_host'> </capability> </capability> </device> Then create the vHBA with the command "virsh nodedev-create" (assuming above XML file is named "vhba.xml"): # virsh nodedev-create vhba.xml Node device scsi_host6 created from vhba.xml NOTE: If you specify "name" for the vHBA, then it will be ignored. The kernel will automatically pick the next SCSI host name in sequence not already used. The "wwpn" and "wwnn" values will be automatically generated by libvirt. In order to see...

...evice names like the ones in [1]. 2) How to create a vHBA Pick up one HBA which supports vHBA, use it's "node device name" as the "parent" of vHBA, and specify the "wwnn" and "wwpn" in the vHBA's XML. E.g. <device> <name>scsi_host6</name> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> <wwnn>2001001b32a9da5e</wwnn> <wwpn>2101001b32a9da5e</wwpn> </capability>...

...uit... I'm taking an example from a bz that you won't be able to read because it's marked private. Once you have your vHBA and scsi_hostM for that vHBA on the host you can use 'lsscsi' (you may have to yum/dnf install it - it's a very useful tool)... # lsscsi ... //assume scsi_host6 is the new vHBA created as follow [6:0:0:0] disk IBM 1726-4xx FAStT 0617 - [6:0:1:0] disk IBM 1726-4xx FAStT 0617 - [6:0:2:0] disk IBM 1726-4xx FAStT 0617 /dev/sdf [6:0:3:0] disk IBM 1726-4xx FAStT 0617 /dev/sdg You'll need an mpath pool...

...uit... I'm taking an example from a bz that you won't be able to read because it's marked private. Once you have your vHBA and scsi_hostM for that vHBA on the host you can use 'lsscsi' (you may have to yum/dnf install it - it's a very useful tool)... # lsscsi ... //assume scsi_host6 is the new vHBA created as follow [6:0:0:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:1:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:2:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdf [6:0:3:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdg You'll need an mpath pool...

...uit... I'm taking an example from a bz that you won't be able to read because it's marked private. Once you have your vHBA and scsi_hostM for that vHBA on the host you can use 'lsscsi' (you may have to yum/dnf install it - it's a very useful tool)... # lsscsi ... //assume scsi_host6 is the new vHBA created as follow [6:0:0:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:1:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:2:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdf [6:0:3:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdg You'll need an mpath pool...

...uit... I'm taking an example from a bz that you won't be able to read because it's marked private. Once you have your vHBA and scsi_hostM for that vHBA on the host you can use 'lsscsi' (you may have to yum/dnf install it - it's a very useful tool)... # lsscsi ... //assume scsi_host6 is the new vHBA created as follow [6:0:0:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:1:0]    disk    IBM      1726-4xx  FAStT  0617  - [6:0:2:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdf [6:0:3:0]    disk    IBM      1726-4xx  FAStT  0617  /dev/sdg You'll need an mpath pool...

..., you have to specify the address of the device as SCSI address. Consider this case in a VM xml file to attach to the host's tape drive: <hostdev mode='subsystem' type='scsi' managed='no' sgio='unfiltered'> <source> <adapter name='scsi_host6'/> <address bus='0' target='7' unit='0'/> </source> </hostdev> With the current behaviour of the kernel, this will be broken in all setups with multiple controllers. If the host adapter address changes arbitrarily after a reboot, the VM...