search for: hostdev0

...a" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > [...] > > > -drive file=/dev/sg5,if=none,format=raw,id=drive-hostdev0,readonly=on \ > > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ > > [...] > > > the bad one: > > /usr/bin/qemu-system-x86_64 \ > > [...] > > > -blockdev '{"driver":"host_device","f...

...en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b \ -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \ -drive file=/dev/sg5,if=none,format=raw,id=drive-hostdev0,readonly=on \ -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 \ -object rng-random,id=objrng0,filename=/dev/urandom \ -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 \ -sandbox on,o...

...make sure you post the latest/actual one. It'll help showing > > whether anything changed between the two or there is a different > > problem. > > > > here is the good cmd: > /usr/bin/qemu-system-x86_64 \ [...] > -drive file=/dev/sg5,if=none,format=raw,id=drive-hostdev0,readonly=on \ > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ [...] > the bad one: > /usr/bin/qemu-system-x86_64 \ [...] > -blockdev '{"driver":"host_device","filename":"/dev/sg0","node-...

...> > To: "daggs" <daggs@gmx.com> > > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > > Subject: Re: scsi passthrough differs between guests > > > > [...] > > > > > -drive file=/dev/sg5,if=none,format=raw,id=drive-hostdev0,readonly=on \ > > > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ > > > > [...] > > > > > the bad one: > > > /usr/bin/qemu-system-x86_64 \ > > > > [...] > > > > > -blockdev '{...

...file. When I attach Virtual Function to VM and I try to poweron the VM, I get the below error: [root@Dell-Rhel7 ~]# virsh start rhel64x64GA error: Failed to start domain rhel64x64GA error: internal error: early end of file from monitor: possible problem: qemu-kvm: -device vfio-pci,host=42:10.2,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to open /dev/vfio/vfio: Permission denied qemu-kvm: -device vfio-pci,host=42:10.2,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to setup container for group 47 qemu-kvm: -device vfio-pci,host=42:10.2,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to get group 47 qemu-k...

...;interface type='network'> <source network='passthrough_eth3'/> </interface> I get this error: "error: Failed to create domain from ./vm0.xml error: internal error Process exited while reading console log output: kvm: -device pci-assign,host=01:10.1,id=hostdev0,configfd=47,bus=pci.0,addr=0x8: Duplicate ID 'hostdev0' for device " Ideas? -- John Fisher

...CI card. It seems like the solution might have something to do with delaying the start of libvirtd in systemd until the PCI card (or vfio?) is ready, but I don’t know how to do that. Can anyone else offer assistance? My output: 2016-03-29T18:29:26.191010Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: Device or resource busy 2016-03-29T18:29:26.289154Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device initialization failed. 2016-03-29T18:29:26.289195Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci...

...sing through a DVB-T TV card to a VM running MythTV. When I assign the PCI devices in virt-manager and attempt to start the VM I get this error: Error starting domain: internal error: process exited while connecting to monitor: 2015-09-06T12:41:09.725990Z qemu-kvm: -device vfio-pci,host=05:02.0,id=hostdev0,bus=pci.0,addr=0x9: vfio: error, group 11 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-09-06T12:41:09.726034Z qemu-kvm: -device vfio-pci,host=05:02.0,id=hostdev0,bus=pci.0,addr=0x9: vfio: failed to get group 11 2015-09-06T12:41:09.726049Z...

...t;52:54:0a:b1:48:07"/> </interface> <interface type="network"> <source network="vnet1"/> <mac address="52:54:0a:b1:48:07"/> </interface> VM can't start because: kvm: -device pci-assign,configfd=24,host=01:10.1,id=hostdev0,bus=pci.0,addr=0x4: Duplicate ID 'hostdev0' for device libvirt version 1.0.5. What i am doing wrong? -- Regards Dominik -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20130516/1905f88f/attac...

...t;john@jpfisher.net > <mailto:john@jpfisher.net>> wrote: > > I get this error: > "error: Failed to create domain from ./vm0.xml > error: internal error Process exited while reading console log > output: kvm: -device > pci-assign,host=01:10.1,id=hostdev0,configfd=47,bus=pci.0,addr=0x8: Duplicate > ID 'hostdev0' for device " > > Ideas? > > > Yes. > > https://bugzilla.redhat.com/show_bug.cgi?id=1001881 > And since it doesn't specifically spell it out in the bug report - the upstream fix was include...

...t; </network> # virsh dumpxml guestbox --- <interface type='network'> <mac address='52:54:00:c0:de:00'/> <source network='em2net'/> <vlan> <tag id='17'/> </vlan> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> --- The networking doesn't work until I run the following command on the host: ip link set em2 vf 0 vlan 17 Then networking in the...

...rface> But the error output when I boot one vm: [root@host3 VTS2.1-demo]# virsh create vtc.demo.xml error: Failed to create domain from vtc.demo.xml error: internal error: early end of file from monitor: possible problem: 2016-02-22T07:38:42.169035Z qemu-kvm: -device vfio-pci,host=10:10.3,id=hostdev0,bus=pci.0,addr=0x3: vfio: error, group 17 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2016-02-22T07:38:42.169215Z qemu-kvm: -device vfio-pci,host=10:10.3,id=hostdev0,bus=pci.0,addr=0x3: vfio: failed to get group 17 2016-02-22T07:38:42.169233Z...

...lt;/controller> <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host0'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <alias name='hostdev0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> but when I boot the vm, I see no cdrom, lspci shows this: 03:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev 01) 07:01.0 SCSI storage c...

...ci. When I invoke the same machine with virsh with what I believe are the same addresses, I get: virsh # start foo error: Failed to start domain foo error: internal error: process exited while connecting to monitor: 2015-08-12T18:24:10.651720Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: error, group 18 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-08-12T18:24:10.651752Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: failed to get group 18 2015-08-12T18:24:1...

....2 and libvirt 1.2.16. There is a legacy (5V) PCI card being passed through to the VM, the error seems to relate to that. The error that always appears at boot in `/var/log/libvirt/qemu/test-vm.log` is: > 2016-01-11T05:29:28.487935Z qemu-system-x86_64: -device > vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: Error: > Failed to setup INTx fd: Device or resource busy > 2016-01-11T05:29:28.488148Z qemu-system-x86_64: -device > vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device > initialization failed > 2016-01-11T05:29:28.488169Z qemu-system-x86_64: -d...

...</hostdev> When I try to start the guest I get the following error message: [root@vmhost2 ~]# virsh start testfedora error: Failed to start domain testfedora error: internal error: qemu unexpectedly closed the monitor: 2020-04-24T20:01:35.341020Z qemu-kvm: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.8,addr=0x0: vfio error: 0000:01:00.0: failed to setup INTx fd: Operation not permitted [root@vmhost2 ~]# Why is it telling me that is not permitted?

...;x-vga=on" is, but libvirt doesn't directly support that. If it is necessary, you would need to add it using libvirt's "qemu commandline passthrough": http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html (you can add a "-set", "device.hostdev0.x-vga=on" I think) 5) The libvirt definition you've provided add several other devices that you don't have in your qemu commandline which may get in the way of what you want to do; in particular the tablet, mouse, and keyboard. You'll probably want to trim those out (and if you...

If I'm using the SR-IOV Pool assignment method (from http://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition ), how would I check how many virtual functions are already in use? Is there a method other then looping through all the active guests and determining if they're using the SR-IOV interface?

...llowing error message: >> >> >> [root@vmhost2 ~]# virsh start testfedora >> error: Failed to start domain testfedora >> error: internal error: qemu unexpectedly closed the monitor: >> 2020-04-24T20:01:35.341020Z qemu-kvm: -device >> vfio-pci,host=01:00.0,id=hostdev0,bus=pci.8,addr=0x0: vfio error: >> 0000:01:00.0: failed to setup INTx fd: Operation not permitted >> >> [root@vmhost2 ~]# >> >> Why is it telling me that is not permitted? >> > The guest will be running as qemu on the host. Does qemu have appropriate permissi...

...rial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -usb -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device pci-assign,host=04:07.0,id=hostdev0,configfd=26,bus=pci.0,addr=0x8 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 char device redirected to /dev/pts/1 do_spice_init: starting 0.8.3 spice_server_add_interface: SPICE_INTERFACE_MIGRATION spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_IN...