Displaying 20 results from an estimated 500 matches similar to: "Can't get PCI passthrough working"
2013 Jul 27
1
WARN in drm_crtc.c:1992 on 3.11-rc2
Hello,
I've started seeing the following warning in 3.11-rc2. [In the
interest of full disclosure, I do have a patch applied that tries to
implement drm_planes, which I might have done completely incorrectly,
but looking around it doesn't seem related. I'm definitely not
invoking any of the planes functionality right now. See
http://paste.debian.net/hidden/cf8b3a2, plus a call to the
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 Nov 09
1
[Bug 98654] New: kernel paging request at iowrite32
https://bugs.freedesktop.org/show_bug.cgi?id=98654
Bug ID: 98654
Summary: kernel paging request at iowrite32
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2013 Dec 11
4
[Bug 72599] New: [NVC0] null pointer dereference (nouveau_fence_wait_uevent.isra.5)
https://bugs.freedesktop.org/show_bug.cgi?id=72599
Priority: medium
Bug ID: 72599
Assignee: nouveau at lists.freedesktop.org
Summary: [NVC0] null pointer dereference
(nouveau_fence_wait_uevent.isra.5)
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux
2007 Feb 09
1
USB Problem
So my syslog filled up with this:
Feb 8 06:47:59 mythbox upsd[3836]: Data for UPS [CyberPower] is stale -
check driver
Feb 8 06:47:59 mythbox upsd[3836]: UPS [CyberPower] data is no longer stale
Feb 8 06:48:01 mythbox upsd[3836]: Data for UPS [CyberPower] is stale -
check driver
Feb 8 06:48:01 mythbox upsd[3836]: UPS [CyberPower] data is no longer stale
Feb 8 06:48:03 mythbox upsd[3836]: Data
2014 Aug 17
0
FYI: Nouveau bug exposed in the latest fedora kernel
(1/3)
Linux version 3.15.10-200.fc20.x86_64
(mockbuild at bkernel02.phx2.fedoraproject.org) (gcc version 4.8.3 20140624
(Red Hat 4.8.3-1) (GCC) ) #1 SMP Thu Aug 14 15:39:24 UTC 2014
(2/3)
[ 1.078495] nouveau [ DEVICE][0000:00:05.0] BOOT0 : 0x04e000a2
[ 1.078501] nouveau [ DEVICE][0000:00:05.0] Chipset: C51 (NV4E)
[ 1.078504] nouveau [ DEVICE][0000:00:05.0] Family : NV40
[
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
2020 Oct 15
2
Re: scsi passthrough differs between guests
Greetings Peter,
> Sent: Thursday, October 15, 2020 at 2:01 PM
> 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
>
> [...]
>
> > -drive
2020 Oct 15
0
Re: scsi passthrough differs between guests
On Thu, Oct 15, 2020 at 12:36:08 +0200, daggs wrote:
> 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
2020 Oct 15
0
Re: scsi passthrough differs between guests
On Thu, Oct 15, 2020 at 13:14:56 +0200, daggs wrote:
> Greetings Peter,
>
> > Sent: Thursday, October 15, 2020 at 2:01 PM
> > 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
2016 Mar 29
0
Re: "INTx fd" busy error on VM startup at boot, subsequent startup okay
Hey Mike, did you ever have any success figuring out this issue? I am having the same problem (on CentOS 7) with a custom data acquisition PCI 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
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
2018 Feb 14
2
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
On Wed, 14 Feb 2018 14:53:40 +0000
Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote:
> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
> VFIO_IOMMU_TYPE1 as well.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
> ---
> drivers/vfio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
2018 Feb 14
2
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
On Wed, 14 Feb 2018 14:53:40 +0000
Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote:
> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
> VFIO_IOMMU_TYPE1 as well.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
> ---
> drivers/vfio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
2012 Jul 14
0
PCI passthrough troubles
Hello,
I have been struggling as of late to successfully configure a pci
passthrough using libvirt with kvm. Hoping someone can shed some light on
the problem. Overall my experience with virtualization limited is so please
forgive. The guest runs fine till passthrough is configured. I am using
virt-manager. This has been tried on both a Fedora17 x86_64 and Arch Linux
x86_64 build with pretty much
2016 Feb 22
0
About the vfio error when using SR-IOV
Hi, All
I want to use the SR-IOV of intel 82576 NIC.
I enabled IOMMU and VT-d and SR-IOV in BIOS.
And enabled VT-d in kernel.
The OS information is bellow:
[root@host3 nova]# cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
[root@host3 nova]# uname -an
Linux host3.localdomain 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@host3 nova]#
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 26
2
POOL of SRIOV networks with multiple PFs
We are using an Intel 82599 chip that allows 4 PFs ( eth0..3) per VM. I am able to manually start VMs using the hostdev
definition for the four network connections, but I'd like to start using the pool approach. Ubuntu 12.04 libvirt 1.0.0
Following:
http://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition
I can get a pool working with
2018 Feb 14
0
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
VFIO_IOMMU_TYPE1 as well.
Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
---
drivers/vfio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig
index c84333eb5eb5..65a1e691110c 100644
--- a/drivers/vfio/Kconfig
+++
2018 Feb 14
0
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
On 14/02/18 15:26, Alex Williamson wrote:
> On Wed, 14 Feb 2018 14:53:40 +0000
> Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote:
>
>> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
>> VFIO_IOMMU_TYPE1 as well.
>>
>> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
>> ---
>>