similar to: vga passthroufh fail

Displaying 20 results from an estimated 20000 matches similar to: "vga passthroufh fail"

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 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
2013 Nov 19
0
Re: Using hostdev to plug a PCI-E host device into Q35 pcie-root port
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 way to translate this into libvirt XML seems to be using > <hostdev>, but I seem to be
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'> >
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
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 03
1
multiple devices in the same iommu group in L1 guest
Hi, I have a guest enabled vIOMMU, but on the guest there are several devices in the same iommu group. Could someone help to check if I missed something? Thank you very much! 1. guest xml: # virsh edit q ... <os> <type arch='x86_64' machine='pc-q35-rhel7.5.0'>hvm</type> <loader readonly='yes' secure='yes'
2016 Feb 09
0
Re: Getting "unknown device type" when attaching NPIV (vHBA) to vm
On 02/08/2016 06:01 PM, Vaknin, Rami wrote: > Thank you for your reply, > I'm still getting hard time to attach the hostdev, I couldn't make it work out of the doc. > > I took the address details from: > > # ll /sys/bus/scsi/devices/7:* > lrwxrwxrwx 1 root root 0 Feb 8 12:58 /sys/bus/scsi/devices/7:0:0:0 ->
2016 Feb 03
0
Re: Getting "unknown device type" when attaching NPIV (vHBA) to vm
On 01.02.2016 22:48, Vaknin, Rami wrote: > 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.
2016 Feb 07
1
GPU passthrough failed to find romfile
Hello guys, this drives me insane. I am trying to pass romfile of my GPU for UEFI boot This is an error I am getting : [root@brutus-coreos opt]# virsh start winos1 error: Failed to start domain winos1 error: internal error: early end of file from monitor: possible problem: 2016-02-07T16:56:09.358285Z qemu-system-x86_64: -device
2016 Feb 08
2
Re: Getting "unknown device type" when attaching NPIV (vHBA) to vm
Thank you for your reply, I'm still getting hard time to attach the hostdev, I couldn't make it work out of the doc. I took the address details from: # ll /sys/bus/scsi/devices/7:* lrwxrwxrwx 1 root root 0 Feb 8 12:58 /sys/bus/scsi/devices/7:0:0:0 -> ../../../devices/pci0000:00/0000:00:03.0/0000:08:00.1/host7/rport-7:0-0/target7:0:0/7:0:0:0 lrwxrwxrwx 1 root root 0 Feb 8 12:58
2016 Sep 06
0
My Windows7 VM stopped at loading screen.
Hello. I've been tesing VGA passthrough using libvirt. However, My *Windows7*(64bit) Virtual Machine stopped at loading screen as soon as I installed graphic driver(*AMD Radeon HD 7750*) and then restarted the VM. How Can I use VGA passthrough technology in my *Windows7* VM? I attached my testing information(HW, system environment and settings, qemu log and so on..) Best Regards.
2016 Oct 28
0
Re: [Qemu-devel] pci-assign fails with read error on config-space file
On 10/28/16 13:28, Henning Schild wrote: > 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
2020 Jul 06
0
Re: Could you please help with questions about the net failover feature
On 7/6/20 5:10 AM, Yalan Zhang wrote: > > Hi Laine, > > For the feature testing before, I only test the linux bridge setting as > in 2), it works. > Now I tried 1), to use macvtap bridge mode connected to the PF, it can > not work as the hostdev interface can not get dhcp ip address on the guest. > Check on host, the /var/log/messages and dmesg both says: > >
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
2020 Jul 08
0
Re: Could you please help with questions about the net failover feature
On 7/8/20 1:30 AM, Stefan Assmann wrote: > On 2020-07-06 10:01, Laine Stump wrote: >> On 7/6/20 5:10 AM, Yalan Zhang wrote: >>> Hi Laine, >>> >>> For the feature testing before, I only test the linux bridge setting as >>> in 2), it works. >>> Now I tried 1), to use macvtap bridge mode connected to the PF, it can >>> not work as the
2020 Sep 24
0
Re: [libvirt] SRIOV configuration
On Mon, Sep 21, 2020 at 06:04:36PM +0300, Edward Haas wrote: > The PCI addresses appearing on the domxml are not the same as the ones > mappend/detected in the VM itself. I compared the domxml on the host > and the lspci in the VM while the VM runs. Can you clarify what you are comparing here ? The PCI slot / function in the libvirt XML should match, but the "bus" number in
2020 Mar 21
0
Re: Could you please help with questions about the net failover feature
On 3/21/20 1:08 AM, Yalan Zhang wrote: > In my understanding, the standby and primary hostdev interface may be in > different subnet. There is only one hostdev device in the team pair (that will be the one with <teaming type='transient'.../> since it needs to be unplugged during migration). The other device must be a virtio device (the one with <teaming
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 Feb 04
0
Re: PCI/GPU Passthrough with xen
this config does not work... why? <domain type='xen'> <name>marax.chao5.int</name> <uuid>72f8f7cf-d538-41cd-828a-9945b9157719</uuid> <memory unit='GiB'>32</memory> <currentMemory unit='GiB'>32</currentMemory> <vcpu placement='static'>16</vcpu> <os> <type