search for: elementshostdev

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:

...018c604f101321</fabric_wwn> > </capability> > </capability> > </device> > > </devices> > This is not how you attach a hostdev to a domain. You need to be looking at <hostdev/>: http://libvirt.org/formatdomain.html#elementsHostDev Michal

...018c604f101321</fabric_wwn> > </capability> > </capability> > </device> > > </devices> > This is not how you attach a hostdev to a domain. You need to be looking at <hostdev/>: http://libvirt.org/formatdomain.html#elementsHostDev Michal

Hello, I encounter a problem, my display is not light when guest running. But it's successful that i check guest with command "ping". Following message is my xml and refer topic from https://libvirt.org/formatdomain.html#elementsHostDev: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio' /> <source> <address domain='0x0000' bus='0x06' slot='0x02' function='0x0'/> </source> </hostdev>

...uce fine-grained pci-assignment in an openstack setup, where > vendor and device id are not enough to pick the right device for a vm. (1) The libvirt domain XML identifies the host PCI device to assign by full PCI address (see the <source> element: <http://libvirt.org/formatdomain.html#elementsHostDev>); it does not filter with vendor/device ID. So, I believe your comment refers to the pci-stub host kernel driver not being flexible enough for binding vs. not binding different instances of the same vendor/device ID. If that's the case, would you be helped by the following host kernel pat...

...gt; </capability> >> </capability> >> </device> >> >> </devices> >> > This is not how you attach a hostdev to a domain. You need to be looking at <hostdev/>: > > http://libvirt.org/formatdomain.html#elementsHostDev > > Michal > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users >

Hey, i am running an unusual setup where i assign pci devices behind the back of libvirt. I have two options to do that: 1. a wrapper script for qemu that takes care of suid-root and appends arguments for pci-assign 2. virsh qemu-monitor-command ... 'device_add pci-assign...' I know i should probably not be doing this, it is a workaround to introduce fine-grained pci-assignment in an