similar to: Re: PCI Passthrough of 2 identical devices

Displaying 20 results from an estimated 6000 matches similar to: "Re: PCI Passthrough of 2 identical devices"

2014 Mar 12
1
PCI Passthrough of 2 identical devices
hi, i have a small trouble with pci-passthrough. i have a working configuration passing a tv card into the guest, all is fine and dandy. as soon as i add my second identical card into the host i cant start the guest anymore, whether i add the second card to the guest or not. error message is identical in both cases. message of virt-manager|virsh|libvirtd.log: > libvirtError: internal error:
2020 Oct 01
0
Logitech C922 webcam
On 9/30/20 8:52 AM, H wrote: > 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller My system has these: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8
2020 Oct 02
2
Logitech C922 webcam
On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell <bferrell at baywinds.org> wrote: >On 9/30/20 8:52 AM, H wrote: >> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >Family USB 3.0 xHCI Controller >My system has these: > >00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB xHCI (rev 05) >00:1a.0 USB controller: Intel
2020 Oct 05
2
PCI Passthrough and Surprise Hotplug
Hi, I'm using QEMU/KVM on RHEL (CentOS) 7.8.2003: # cat /etc/redhat-release CentOS Linux release 7.8.2003 I'm passing an NVMe drive into a Linux KVM virtual machine (<type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>) which has the following 'hostdev' entry: <hostdev mode='subsystem' type='pci' managed='yes'>
2020 Apr 24
2
Not able to add pcie card to guest: Operation not permitted
Let's say I have libvirt [root@vmhost2 ~]# virsh version Compiled against library: libvirt 4.5.0 Using library: libvirt 4.5.0 Using API: QEMU 4.5.0 Running hypervisor: QEMU 2.12.0 [root@vmhost2 ~]# running on centos 8 and then I have this card [root@vmhost2 ~]# virsh nodedev-dumpxml pci_0000_01_00_0 <device> <name>pci_0000_01_00_0</name>
2015 Aug 12
2
PCI passthrough fails in virsh: iommu group is not viable
I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios
2020 Oct 14
2
scsi passthrough differs between guests
Greetings, I have two machines running the same distro, both running qemu 5.1.0, one runs libvirt 6.7.0, the other 6.8.0. I've decided to test the viability of passing through my sata cdrom into a vm, so I went to the libvirt docs, read a bit and added the following to a debian10 uefi vm running on libvirt 6.8.0: <controller type='scsi' index='0'
2013 Nov 15
2
Using hostdev to plug a PCI-E host device into Q35 pcie-root port
Hello, I'm trying to migrate a working qemu command line configuration to libvirt. The part I'm currently failing on is: $ qemu-system-x86_64 -M Q35 ... -device vfio-pci,host=05:00.0,bus=pcie.0 The right way to translate this into libvirt XML seems to be using <hostdev>, but I seem to be unable to plug it into the pcie-root port This is how the interesting part looks like when
2018 Jul 27
2
Trouble passing PCI device in isolated IOMMU group
I'm attempting PCI-passthrough from host to guest on an HP ProLiant 380P, which has an outdated BIOS (2014), but it does support VT-d. I'm running CentOS 7, kernel 3.10.0-862.9.1.el7.x86_64. I have an Intel 82580 NIC installed with 4 ports. Each of these ports is in its own IOMMU group (I enabled SR-IOV at the BIOS, which might be the reason they show up separately) After detaching and
2014 Feb 04
2
SR-IOV: no traffic isolation between VFs with Broadcom 10Gbps cards
Hi all, I'm testing on debian/unstable SR-IOV feature with Broadcom BCM57810 cards and KVM hypervisor: Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 bnx2x -> firmware 7.8.17 -> driver from kernel 3.12.7 8 VFs are created on the first PF. For each VF, a specific mac address is set manually using "ip
2013 Nov 19
1
Re: Using hostdev to plug a PCI-E host device into Q35 pcie-root port
Am 19.11.2013 11:36, schrieb Laine Stump: > On 11/15/2013 03:35 PM, Thomas Kuther wrote: >> Hello, >> >> I'm trying to migrate a working qemu command line configuration to >> libvirt. >> The part I'm currently failing on is: >> >> $ qemu-system-x86_64 -M Q35 ... -device >> vfio-pci,host=05:00.0,bus=pcie.0 >> >> The right
2018 Jan 05
1
Re: Cannot Write xvga=yes in xml file
Yes, I can use guest with this way, But when i hot-add my graphics card , Guest will reboot. So i want to try it with <hostdev>. Somehow , If i use "hostdev" without xvga , my screen will be black. If we have no hostdev, do you have other methods can help me to use hot-plug my graphics card? At 2018-01-04 23:27:52, "Laine Stump" <laine@redhat.com> wrote:
2013 Aug 27
3
SR-IOV Pool Availability
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?
2020 Oct 15
2
Re: scsi passthrough differs between guests
Greetings Peter, > Sent: Thursday, October 15, 2020 at 9:52 AM > From: "Peter Krempa" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > I don't see anything wrong with you configs. There were some changes
2019 Aug 22
2
Re: RLIMIT_MEMLOCK in container environment
On Thu, Aug 22, 2019 at 12:01 PM Laine Stump <laine@redhat.com> wrote: > > On 8/22/19 10:56 AM, Ihar Hrachyshka wrote: > > On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé <berrange@redhat.com> wrote: > >> > >> On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > >>> Hi all, > >>> > >>> KubeVirt uses
2019 Aug 24
1
Re: RLIMIT_MEMLOCK in container environment
On Fri, 23 Aug 2019, 0:27 Laine Stump, <laine@redhat.com> wrote: > (Adding Alex Williamson to Cc so he can correct any mistakes) > > On 8/22/19 4:39 PM, Ihar Hrachyshka wrote: > > On Thu, Aug 22, 2019 at 12:01 PM Laine Stump <laine@redhat.com> wrote: > >> > >> On 8/22/19 10:56 AM, Ihar Hrachyshka wrote: > >>> On Thu, Aug 22, 2019 at 2:24 AM
2017 Apr 24
0
Issues with exposing USB serial dongle to guest VM
Hi. I have Centos 7 (updated) running as my host, and I?m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn?t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though
2020 Feb 03
0
Re: USB devices with same vendor:product id
On Mon, Feb 03, 2020 at 02:20:47PM +0100, Maxime Accadia wrote: >Hi, > >We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM : > >------- >error: Failed to start domain xxx >error: internal error: Did not find USB device 04b9:0300
2019 Sep 24
1
[PATCH V2 2/8] mdev: class id support
On Tue, 24 Sep 2019 21:53:26 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev
2019 Oct 17
3
[PATCH V4 3/6] mdev: introduce device specific ops
On Thu, 17 Oct 2019 18:48:33 +0800 Jason Wang <jasowang at redhat.com> wrote: > Currently, except for the create and remove, the rest of > mdev_parent_ops is designed for vfio-mdev driver only and may not help > for kernel mdev driver. With the help of class id, this patch > introduces device specific callbacks inside mdev_device > structure. This allows different set of