search for: nodedev

Hi, When I want to use NPIV for a FC HBA in my Linux machine, I got the below error msg in virsh: virsh # nodedev-create /home/kvm/vHBA.xml error: Failed to create node device from /home/kvm/vHBA.xml error: internal error Parent device scsi_host20 is not capable of vport operations I checked the /sys/class folder for my HBA device that I want to use its NPIV feature, it's there: /sys/class/fc_host/host2...

...ase) ?????????????? libvirt-daemon = 4.5.0-10.el7 ?????????? Available: libvirt-daemon-4.5.0-10.el7_6.2.x86_64 (updates) ?????????????? libvirt-daemon = 4.5.0-10.el7_6.2 Error: Package: libvirt-daemon-xen-4.1.0-2.xen48.el7.x86_64 (@centos-virt-xen-48) ?????????? Requires: libvirt-daemon-driver-nodedev = 4.1.0-2.xen48.el7 ?????????? Removing: libvirt-daemon-driver-nodedev-4.1.0-2.xen48.el7.x86_64 (@centos-virt-xen-48) ?????????????? libvirt-daemon-driver-nodedev = 4.1.0-2.xen48.el7 ?????????? Updated By: libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.3.x86_64 (updates) ?????????????? libvirt-...

...de virtual machines access to the physical CAN channels. >> >>I started with the virtual network handling as CAN interface is a network interface, I tried to find analogies, solutions like "traditional" network handling but it did not work. >>I also tried out to define a nodedev device via .xml config file. The interesting thing is, that when I list all the available nodedev devices with 'virsh nodedev-list', I can see 'net_can0' and 'net_can1' on the output as 'net' type device but I cannot attach these devices to the guests, and I do not k...

Hello everyone, Current host build is RHEL 6.2, soon to be upgrading. I'm in the process of mapping out a KVM/RHEV topology. I have questions about the landscape of storage pools and the instantiation of specific scsi_host IDs using virsh nodedev-create and some magic XML definitions. I'm grouping these questions together because the answer to one may impact the other. High-level goals: - fence off I/O by providing NPIV paths to VMs individually - provide each VM with a pair of paths to the same storage for redundancy Problem 1 - St...

...will primarily describe NPIV functionality as of the current libvirt release, 1.1.2. There will be a troubleshooting and prior version considerations section to describe some historical differences. 1) Discovery Discovery of HBA(s) capable of NPIV is provided through the virsh command 'virsh nodedev-list --cap vports'. If no HBA is returned, then the host configuration should be checked. The XML output from the command "virsh nodedev-dumpxml" will list fields <name>, <wwnn>, and <wwpn> to be used in order to create a vHBA. Take care to also note the <max_vpor...

...ibvirt-daemon = 4.5.0-10.el7 > ?????????? Available: libvirt-daemon-4.5.0-10.el7_6.2.x86_64 (updates) > ?????????????? libvirt-daemon = 4.5.0-10.el7_6.2 > Error: Package: libvirt-daemon-xen-4.1.0-2.xen48.el7.x86_64 > (@centos-virt-xen-48) > ?????????? Requires: libvirt-daemon-driver-nodedev = 4.1.0-2.xen48.el7 > ?????????? Removing: > libvirt-daemon-driver-nodedev-4.1.0-2.xen48.el7.x86_64 > (@centos-virt-xen-48) > ?????????????? libvirt-daemon-driver-nodedev = 4.1.0-2.xen48.el7 > ?????????? Updated By: > libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.3.x86_64 (updat...

...will be > updated > --> Processing Dependency: libvirt-daemon-driver-network = 1.3.0-1.el7 for > package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > ---> Package libvirt-daemon-driver-network.x86_64 0:2.0.0-10.el7_3.2 will > be an update > ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 will be > updated > --> Processing Dependency: libvirt-daemon-driver-nodedev = 1.3.0-1.el7 for > package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > ---> Package libvirt-daemon-driver-nodedev.x86_64 0:2.0.0-10.el7_3.2 will > be an update > ---> Package l...

I have a Dell T430 with CentOS 7 kernel release: 3.18.41-20.el7.x86_64 and xen_version : 4.6.3-3.el7 I am doing an update of my server, but it fails:- yum update ================================================================================= Error: Package: libvirt-daemon-driver-libxl-1.3.0-1.el7.x86_64 (@centos-virt-xen) Requires: libvirt-daemon = 1.3.0-1.el7 Removing:

Hi, I'm trying to attach a host FC HBA to VM (NPIV). Running ovirt 3.5 on CentOS 6.7, libvirt-0.10.2-46.el6_6.6.x86_64, I created vHBA using nodedev-create command - see below HBA and vHBA. I wrote a vdsm hook which appends the vHBA xml stanza to the devices xml element but the vm start starts without the vHBA device. Also, when trying to attach the device manually as a live device - I get: 2016-02-01 21:30:24.216+0000: 129764: debug : qemuDom...

.... So here we go. The document tries to summary up the things about NPIV that libvirt supports till now, and the TODO list. Feedback or suggestion is welcomed. 1) How to find out which HBA(s) support vHBA For libvirt newer than "1.0.4", you can find it out simply by: # virsh nodedev-list --cap vports "--cap vports" is to tell "nodedev-list" only outputs the devices which support "vports" capability, i.e. support vHBA. And also since version "1.0.4", you should be able to know the maximum vports the HBA supports and the current vp...

...gt; Processing Dependency: libvirt-daemon-driver-network = > > 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > > ---> Package libvirt-daemon-driver-network.x86_64 > > 0:2.0.0-10.el7_3.2 > > will be an update > > ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 > > will > > be updated > > --> Processing Dependency: libvirt-daemon-driver-nodedev = > > 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > > ---> Package libvirt-daemon-driver-nodedev.x86_64 > > 0:2.0.0-10.el7_3.2 >...

...r-network.x86_64 0:1.3.0-1.el7 will be updated --> Processing Dependency: libvirt-daemon-driver-network = 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 ---> Package libvirt-daemon-driver-network.x86_64 0:2.0.0-10.el7_3.2 will be an update ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 will be updated --> Processing Dependency: libvirt-daemon-driver-nodedev = 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 ---> Package libvirt-daemon-driver-nodedev.x86_64 0:2.0.0-10.el7_3.2 will be an update ---> Package libvirt-daemon-driver-nwfilter....

...will > be updated > --> Processing Dependency: libvirt-daemon-driver-network = > 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > ---> Package libvirt-daemon-driver-network.x86_64 0:2.0.0-10.el7_3.2 > will be an update > ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 will > be updated > --> Processing Dependency: libvirt-daemon-driver-nodedev = > 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > ---> Package libvirt-daemon-driver-nodedev.x86_64 0:2.0.0-10.el7_3.2 > will be an update > ---> Package l...

...ine 225, in _reparse_xml     self._xmlobj = self._build_xmlobj(self._get_raw_xml())   File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 228, in _build_xmlobj     return self._parseclass(self.conn.get_backend(), parsexml=xml)   File "/usr/share/virt-manager/virtManager/nodedev.py", line 27, in _parse_convert     return NodeDevice.parse(conn, parsexml)   File "/usr/share/virt-manager/virtinst/nodedev.py", line 95, in parse     tmpdev = NodeDevice(conn, parsexml=xml, allow_node_instantiate=True)   File "/usr/share/virt-manager/virtinst/nodedev.py",...

...n-driver-network = > >>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > >>> ---> Package libvirt-daemon-driver-network.x86_64 > >>> 0:2.0.0-10.el7_3.2 > >>> will be an update > >>> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 > >>> will > >>> be updated > >>> --> Processing Dependency: libvirt-daemon-driver-nodedev = > >>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 > >>> ---> Package libvirt-daemon-driver-nodedev.x...

...Dependency: libvirt-daemon-driver-network = >>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 >>> ---> Package libvirt-daemon-driver-network.x86_64 >>> 0:2.0.0-10.el7_3.2 >>> will be an update >>> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 >>> will >>> be updated >>> --> Processing Dependency: libvirt-daemon-driver-nodedev = >>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 >>> ---> Package libvirt-daemon-driver-nodedev.x86_64 >>> 0:2.0....

...ould like to make a HBA visible through my guest. I stumbled upon a bug that is documented in redhat's bugzilla that attempted creation of NPIV on pci_0000_blah_blah instead on the scsi_hostX device, but I fixed that easily in the xml and although virsh doesn't seem to think I completed the nodedev-create NPIV_for_my_FC.xml the device is seen as a child in nodedev-list and what is more important the WWN are seen on the SAN switch. So this seems to be working OK, however I don't know how to attach this new shiny device that I created to a guest. Could someone give me a hint? What is the pr...

...k = >>>>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 >>>>> ---> Package libvirt-daemon-driver-network.x86_64 >>>>> 0:2.0.0-10.el7_3.2 >>>>> will be an update >>>>> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.3.0-1.el7 >>>>> will >>>>> be updated >>>>> --> Processing Dependency: libvirt-daemon-driver-nodedev = >>>>> 1.3.0-1.el7 for package: libvirt-daemon-xen-1.3.0-1.el7.x86_64 >>>>> ---> Package libvirt-daemon-d...

On 06/20/2013 11:07 AM, Dennis Chen wrote: > Hi, > > When I want to use NPIV for a FC HBA in my Linux machine, I got the below > error msg in virsh: > > virsh # nodedev-create /home/kvm/vHBA.xml > error: Failed to create node device from /home/kvm/vHBA.xml > error: internal error Parent device scsi_host20 is not capable of vport > operations > > I checked the /sys/class folder for my HBA device that I want to use its NPIV > feature, it's the...

Hi, I am using the libvirt 1.0.6 with the patch applied: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=371c155 The problem I encountered is, with virsh comand 'nodedev-create /home/kvm/vHBA.xml', the vHBA can be generated as expected on the host, but error msg will show in the virsh shell: libvirt: Node Device Driver error : Node device not found I try to find the reason with gdb, and found that the 'nodedev-create' command will call virNetClientI...