similar to: PCI passthrough fails in virsh: iommu group is not viable

Displaying 20 results from an estimated 9000 matches similar to: "PCI passthrough fails in virsh: iommu group is not viable"

2015 Aug 12
0
Re: PCI passthrough fails in virsh: iommu group is not viable
On 08/12/2015 02:34 PM, Alex Holst wrote: > 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
2015 Sep 24
1
Re: PCI passthrough fails in virsh: iommu group is not viable
Quoting Laine Stump (laine@laine.org): > On 08/12/2015 02:34 PM, Alex Holst wrote: > > 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
2018 Apr 30
2
Re: connecting host and guest vm using a dummy nic
Greetings Laine, > Sent: Monday, April 30, 2018 at 8:31 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/27/2018 06:39 PM, daggs wrote: > > Greetings all, > > > > I have a host machine that runs
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'
2018 Apr 27
2
connecting host and guest vm using a dummy nic
Greetings all, I have a host machine that runs a router within a vm. I want to allow a connection between the host and the guest so the host can connect to the lan provided by the router vm. I've created a dummy interface with these commands: $ ip link add ens99-dummy type dummy $ ip link set ens99-dummy address 52:54:00:1f:d0:ff this resulted with this output: $ ifconfig ens99-dummy
2014 Jan 25
2
intel quad gigabit nic and pci passthrough
Hi all I have a very weird case of pci passthrough. I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: root@kybrat (x86_64) ~]$ lspci -nn | grep net 00:19.0 Ethernet controller
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
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 Feb 23
3
machine='pc-q35-2.1' and sata controller
Hello. I'm not able to disable the sata controller on a machine='pc-q35-2.1' type VM. Whenever i delete: <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> it gets added again when i close the editor. The reason i would
2020 Apr 25
1
Re: Not able to add pcie card to guest: Operation not permitted
On Fri, Apr 24, 2020 at 4:35 PM Peter Crowther <peter.crowther@melandra.com> wrote: > > On Fri, 24 Apr 2020 at 21:10, Mauricio Tavares <raubvogel@gmail.com> wrote: >> >> Let's say I have libvirt >> >> [root@vmhost2 ~]# virsh version >> [...] >> >> Running hypervisor: QEMU 2.12.0 >> [root@vmhost2 ~]# >> [...] > > When
2015 Aug 04
2
Re: Cannot boot libvirt guests with OVMF. Raw qemu-kvm works as expected
On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >On 08/03/2015 01:43 PM, Ryan Barry wrote: >> Using: >> >> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >> >> On Fedora 22. >> >> Provisioning a i440FX system in virt-manager and attempting to boot >> results in successful EFI
2020 Apr 07
1
"failed to setup INTx fd: Operation not permitted" error when using PCI passthrough
Hi, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver
2015 Aug 06
2
Re: Cannot boot libvirt guests with OVMF. Raw qemu-kvm works as expected
On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >On 08/03/2015 10:47 PM, Martin Kletzander wrote: >> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>> Using: >>>> >>>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>>>
2014 Mar 12
1
Re: PCI Passthrough of 2 identical devices
hi laine, thx for the fast answer. i tried VFIO as it seems supported and got at least one step further. starting the guest with one of the DVB cards is possible now, even when the other card is in the hosts pci config (not removed soft or hard). adding the second card/device thru ... > <hostdev mode='subsystem' type='pci' managed='yes'> >
2014 Feb 24
1
Rhel7 snap6 -- SR-IOV
Hi, This is regarding SRIOV in Rhel7. I have added intel_iommu=on in grub.cfg 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
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 May 01
0
Re: connecting host and guest vm using a dummy nic
On 04/30/2018 03:16 PM, daggs wrote: > Greetings Laine, > >> Sent: Monday, April 30, 2018 at 8:31 PM >> From: "Laine Stump" <laine@redhat.com> >> To: libvirt-users@redhat.com >> Cc: daggs <daggs@gmx.com> >> Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic >> >> On 04/27/2018 06:39 PM, daggs wrote:
2015 Aug 03
2
Cannot boot libvirt guests with OVMF. Raw qemu-kvm works as expected
Using: edk2.git-0-20150803.b1141.ga0973dc.x86_64 edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch On Fedora 22. Provisioning a i440FX system in virt-manager and attempting to boot results in successful EFI initialization, but the VM exits ungracefully after the bootloader (with F22 and CentOS 7 installer images). There's no really useful information in any of the logs. Using qemu-kvm
2016 Dec 21
1
Re: Audio in Windows 10 VM is distorted. Using ALSA.
Hi, I found the main reason for sound distortions on my system is guest timer configuration. The working one is: <clock offset="localtime"> <timer name="hypervclock" present="yes"/> <timer name="hpet" present="no"/> <timer name="rtc" present="yes" track="guest"
2020 Sep 21
2
[libvirt] SRIOV configuration
Hello, We encountered a problem while testing SRIOV on kubevirt [1]: We are currently using the Device "hostdev" generic options to pass-through the VF to the guest. It is not done through the "interface" (with type hostdev) because that option requires access to the PF which is not available in our case (the VF is moved to the container namespace where libvirt runs, but not