https://bugzilla.kernel.org/show_bug.cgi?id=107561
Paolo Bonzini changed:
What|Removed |Added
Attachment #197081|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #13 from schefis...@gmail.com ---
Sorry for the delay. I couldn't check sooner.
Unfortunately the guest doesn't start with the patch applied. Nothing displayed
(no sync signal from passthrough card). Host dmesg doesn't show any
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #14 from Jasen Borisov ---
Can confirm. I am also hit by this bug, and my virtual machine doesn't start
either.
I tried applying the patch to both 4.3.0 and linux-next, and neither of those
worked.
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #10 from Paolo Bonzini ---
Another test on the 3GB machine: make it fast by nuking
kvm_mtrr_get_guest_memory_type (return MTRR_TYPE_WRBACK), then cat /proc/mtrr
from the guest.
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #11 from Paolo Bonzini ---
Created attachment 197071
--> https://bugzilla.kernel.org/attachment.cgi?id=197071=edit
OVMF log
> 1) providing host dmesg
Of course this makes no sense, you already did. And from the
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #9 from Paolo Bonzini ---
Can you try the following on HostA:
1) providing *host* dmesg
2) disabling each MTRR starting from the first, until things are fast again.
Then reboot and try disabling only the MTRR that
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #12 from Paolo Bonzini ---
Created attachment 197081
--> https://bugzilla.kernel.org/attachment.cgi?id=197081=edit
patch to be tested
The bug happens when the VM is created with a maxphyaddr that doesn't match the
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #8 from schefis...@gmail.com ---
I captured the traces, they take more than half a GB uncompressed. They are
available in xz under
https://drive.google.com/folderview?id=0B8ebX_WjVHnGNlN4eTEzU2xtMEk=sharing
To make things clear: I
https://bugzilla.kernel.org/show_bug.cgi?id=107561
Paolo Bonzini changed:
What|Removed |Added
CC||tajj...@gmail.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=107921
Paolo Bonzini changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=107561
Paolo Bonzini changed:
What|Removed |Added
CC||bonz...@gnu.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=107561
--- Comment #6 from Paolo Bonzini ---
Ah, the traces are huge. You can xz them and send them through private email.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this
t a viable long-term
solution. It seems as the new function (in 4.2 and onward) does not return the
proper cache type in case of pci passthrough configurations.
I would also like to point out, that
https://bugzilla.kernel.org/show_bug.cgi?id=107921 may be related. The other
bug mentions very simila
https://bugzilla.kernel.org/show_bug.cgi?id=107921
Bug ID: 107921
Summary: Regression with KVM virtual machine using VFIO for PCI
passthrough.
Product: Virtualization
Version: unspecified
Kernel Version: 4.2
Hardware
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #2 from Jasen Borisov ---
Created attachment 193061
--> https://bugzilla.kernel.org/attachment.cgi?id=193061=edit
Kernel config for my 4.2.6 test build.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #4 from Jasen Borisov ---
Created attachment 193081
--> https://bugzilla.kernel.org/attachment.cgi?id=193081=edit
`dmesg` output from 4.1.13.
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #1 from Jasen Borisov ---
Created attachment 193051
--> https://bugzilla.kernel.org/attachment.cgi?id=193051=edit
Kernel config for my 4.1.13 test build.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #3 from Jasen Borisov ---
Created attachment 193071
--> https://bugzilla.kernel.org/attachment.cgi?id=193071=edit
Kernel config for my 4.3.0 test build.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #6 from Jasen Borisov ---
Created attachment 193101
--> https://bugzilla.kernel.org/attachment.cgi?id=193101=edit
`dmesg` output from 4.3.0
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #5 from Jasen Borisov ---
Created attachment 193091
--> https://bugzilla.kernel.org/attachment.cgi?id=193091=edit
`dmesg` output from 4.2.6
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #7 from Jasen Borisov ---
Created attachment 193111
--> https://bugzilla.kernel.org/attachment.cgi?id=193111=edit
libvirt virtual machine domain configuration
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=107921
--- Comment #8 from Jasen Borisov ---
Created attachment 193121
--> https://bugzilla.kernel.org/attachment.cgi?id=193121=edit
`lspci -vv` output from the host system
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=107561
bre...@gmail.com changed:
What|Removed |Added
CC||bre...@gmail.com
--- Comment #3 from
ke.com
--- Comment #1 from John Brooks <k...@fastquake.com> ---
I can confirm this bug. As soon as I enabled PCI passthrough on my VM while
using kernel 4.2.2, my VM ran extremely slowly, and increasing the amount of
RAM made the problem worse. Switching to kernel 4.1.12 fixed the probl
https://bugzilla.kernel.org/show_bug.cgi?id=107561
Aaron Campbell changed:
What|Removed |Added
CC||aa...@monkey.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=107561
Bug ID: 107561
Summary: 4.2 breaks PCI passthrough in QEMU/KVM
Product: Virtualization
Version: unspecified
Kernel Version: 4.2
Hardware: All
OS: Linux
Tree
:
> > > > If this isn't the right place to ask, any pointers to the
> > > > correct
> > > > place
> > > > are appreciated...
> > > >
> > > > I'm trying to see if I can get PCI passthrough working for a
> > > > video
On Thu, Oct 1, 2015 at 3:27 AM, Phil (list) <pbpubl...@gmail.com> wrote:
> If this isn't the right place to ask, any pointers to the correct place
> are appreciated...
>
> I'm trying to see if I can get PCI passthrough working for a video
> capture card (Hauppauge Colossus 1x
If this isn't the right place to ask, any pointers to the correct place
are appreciated...
I'm trying to see if I can get PCI passthrough working for a video
capture card (Hauppauge Colossus 1x PCIe) under a Windows XP guest (32
-bit). Things appear to be somewhat working (Windows is seeing
On Thu, 2015-10-01 at 08:32 -0400, Mauricio Tavares wrote:
> On Thu, Oct 1, 2015 at 3:27 AM, Phil (list) <pbpubl...@gmail.com>
> wrote:
> > If this isn't the right place to ask, any pointers to the correct
> > place
> > are appreciated...
> >
> > I'm
ers to the correct
> > > place
> > > are appreciated...
> > >
> > > I'm trying to see if I can get PCI passthrough working for a video
> > > capture card (Hauppauge Colossus 1x PCIe) under a Windows XP guest
> > > (32
> > > -bit). Things appear t
Hi,
I'm just experimenting with KVM because of VGA passthrough (attempted
that previously on xen, failed).
Clean instalation of Centos 6.6 with KVM from repo.
first problem I've stumbled upon is that I din't manage to pass in some
PCI devices. They share IRQ, even if I add them both, it
On Tue, Mar 24, 2015 at 8:04 AM, jacob jacob opstk...@gmail.com wrote:
The issue is running dpdk from within the vm itself. Is it possible
that the igb_uio driver needs additional updates/functionality to be
at parity with 1.2.37 version of i40e driver?
At this point I think you need to work
After update to latest firmware and using version 1.2.37 of i40e
driver, things are looking better with PCI passthrough.
]# ethtool -i eth3
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1930
bus-info: :00:07.0
supports-statistics: yes
supports-test: yes
supports
On Tue, Mar 24, 2015 at 10:53 AM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Tue, Mar 24, 2015 at 7:13 AM, jacob jacob opstk...@gmail.com wrote:
After update to latest firmware and using version 1.2.37 of i40e
driver, things are looking better with PCI passthrough.
]# ethtool -i eth3
On Tue, Mar 24, 2015 at 7:13 AM, jacob jacob opstk...@gmail.com wrote:
After update to latest firmware and using version 1.2.37 of i40e
driver, things are looking better with PCI passthrough.
]# ethtool -i eth3
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1930
bus
On 20.03.2015 21:55, jacob jacob wrote:
On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann sassm...@redhat.com wrote:
On 19.03.2015 15:04, jacob jacob wrote:
Hi Stefan,
have you been able to get PCI passthrough working without any issues
after the upgrade?
My XL710 fails to transfer regular
On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann sassm...@redhat.com wrote:
On 19.03.2015 15:04, jacob jacob wrote:
Hi Stefan,
have you been able to get PCI passthrough working without any issues
after the upgrade?
My XL710 fails to transfer regular TCP traffic (netperf). If that works
On Thu, Mar 19, 2015 at 5:53 PM, jacob jacob opstk...@gmail.com wrote:
On Thu, Mar 19, 2015 at 5:42 PM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob opstk...@gmail.com wrote:
I have updated to latest firmware and still no luck.
[...]
[
On 18.03.2015 23:06, Shannon Nelson wrote:
On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob opstk...@gmail.com wrote:
On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das b...@redhat.com wrote:
Actually, Stefan suggests
I was going to try this on fedora 21...now not very sure if that makes
much sense..
On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann sassm...@redhat.com wrote:
On 18.03.2015 23:06, Shannon Nelson wrote:
On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Wed,
On 19.03.2015 15:04, jacob jacob wrote:
Hi Stefan,
have you been able to get PCI passthrough working without any issues
after the upgrade?
My XL710 fails to transfer regular TCP traffic (netperf). If that works
for you then you're already one step ahead of me. Afraid I can't help
you
Hi Stefan,
have you been able to get PCI passthrough working without any issues
after the upgrade?
Thanks
Jacob
On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann sassm...@redhat.com wrote:
On 18.03.2015 23:06, Shannon Nelson wrote:
On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
shannon.nel
I have updated to latest firmware and still no luck.
]# ethtool -i eth1
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1930
bus-info: :00:05.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob opstk...@gmail.com wrote:
I have updated to latest firmware and still no luck.
[...]
[ 61.554132] i40e :00:06.0 eth2: the driver failed to link
because an unqualified module was detected.
[ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2:
On Thu, Mar 19, 2015 at 5:42 PM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob opstk...@gmail.com wrote:
I have updated to latest firmware and still no luck.
[...]
[ 61.554132] i40e :00:06.0 eth2: the driver failed to link
because an
On Thu, Mar 19, 2015 at 1:15 AM, Stefan Assmann sassm...@redhat.com wrote:
Interesting, the following might explain why my XL710 feels a bit
sketchy then. ;-)
# ethtool -i p4p1
driver: i40e
version: 1.2.37-k
firmware-version: f4.22.26225 a1.1 n4.24 e12ef
Looks like the firmware on this NIC
. Can you please post the output as well ?
[0.097072] acpi PNP0A03:00: fail to add MMCONFIG information,
can't access extended PCI configuration space under this bridge.
Does this indicate any issue related to PCI passthrough?
Would really appreciate any input on how to bebug this further
earlier, i do not see any issues at all when running
tests using either i40e or dpdk on the host itself.
This is the reason why i am suspecting if it is anything to do with
KVM/libvirt.
Both with regular PCI passthrough and VF passthrough i see issues. It
is always pointing to some issue
On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
shannon.nel...@intel.com wrote:
On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob opstk...@gmail.com wrote:
On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das b...@redhat.com wrote:
Actually, Stefan suggests that support for this card is still
Hi.
I'm using Proxmox VE 3.4 with qemu-server 3.3, and I'm trying to pass
two PCI-Express AudioScience soundcards to a KVM virtual machine.
The soundcards are the following:
ve2:/# lspci
03:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200A PCI
Express-to-PCI Bridge (rev 03)
04:00.0
)
[0.097072] acpi PNP0A03:00: fail to add MMCONFIG information,
can't access extended PCI configuration space under this bridge.
Does this indicate any issue related to PCI passthrough?
Would really appreciate any input on how to bebug this further.
On Fri, Mar 13, 2015 at 10:08 AM, jacob jacob
problem. Does dmesg | grep -e DMAR -e IOMMU
give anything useful ?
[0.097072] acpi PNP0A03:00: fail to add MMCONFIG information,
can't access extended PCI configuration space under this bridge.
Does this indicate any issue related to PCI passthrough?
Would really appreciate any input on how
this bridge.
Does this indicate any issue related to PCI passthrough?
Would really appreciate any input on how to bebug this further.
Did you get a chance to try a newer kernel ?
Currently am using 3.18.7-200.fc21.x86_64 which is pretty recent.
Are you suggesting trying the newer kernel just
PNP0A03:00: fail to add MMCONFIG information,
can't access extended PCI configuration space under this bridge.
Does this indicate any issue related to PCI passthrough?
Would really appreciate any input on how to bebug this further.
Did you get a chance to try a newer kernel ?
Currently am using
, i do not see any issues at all when running
tests using either i40e or dpdk on the host itself.
This is the reason why i am suspecting if it is anything to do with
KVM/libvirt.
Both with regular PCI passthrough and VF passthrough i see issues. It
is always pointing to some issue with packet
On Mon, 2015-03-16 at 14:35 +0100, shacky wrote:
Hi.
I'm using Proxmox VE 3.4 with qemu-server 3.3, and I'm trying to pass
two PCI-Express AudioScience soundcards to a KVM virtual machine.
The soundcards are the following:
ve2:/# lspci
03:00.0 PCI bridge: Texas Instruments
-1.8.0) and see the same issue.
As mentioned earlier, i do not see any issues at all when running
tests using either i40e or dpdk on the host itself.
This is the reason why i am suspecting if it is anything to do with KVM/libvirt.
Both with regular PCI passthrough and VF passthrough i see issues
On Thu, 2015-03-12 at 12:17 -0400, jacob jacob wrote:
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm.
How is the device being assigned, pci-assign or vfio-pci? What QEMU
version? What host kernel version? Thanks,
Alex
--
To unsubscribe
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm.
0a:00.1 Ethernet controller: Intel Corporation Ethernet
Controller XL710 for 40GbE QSFP+ (rev 01)
From dmesg on host:
[80326.559674] kvm: zapping shadow pages for mmio generation wraparound
: 2.fc21
Kernel 3.18.7-200.fc21.x86_64
Rgds
Jacob
On Thu, Mar 12, 2015 at 12:26 PM, Alex Williamson
alex.william...@redhat.com wrote:
On Thu, 2015-03-12 at 12:17 -0400, jacob jacob wrote:
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm
jacob jacob opstk...@gmail.com writes:
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm.
0a:00.1 Ethernet controller: Intel Corporation Ethernet
Controller XL710 for 40GbE QSFP+ (rev 01)
You are assigning the PF right ? Does assigning VFs
jacob jacob opstk...@gmail.com writes:
On Thu, Mar 12, 2015 at 3:07 PM, Bandan Das b...@redhat.com wrote:
jacob jacob opstk...@gmail.com writes:
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm.
0a:00.1 Ethernet controller: Intel
On Thu, Mar 12, 2015 at 3:07 PM, Bandan Das b...@redhat.com wrote:
jacob jacob opstk...@gmail.com writes:
Hi,
Seeing failures when trying to do PCI passthrough of Intel XL710 40G
interface to KVM vm.
0a:00.1 Ethernet controller: Intel Corporation Ethernet
Controller XL710 for 40GbE
https://bugzilla.kernel.org/show_bug.cgi?id=88671
--- Comment #5 from Tom Stellard tstel...@gmail.com ---
Thanks for the tip about vfio-pci. I can now sometimes get two working guest
boots per host boot.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To
https://bugzilla.kernel.org/show_bug.cgi?id=88671
Tom Stellard tstel...@gmail.com changed:
What|Removed |Added
Component|kvm |Video(DRI - non Intel)
https://bugzilla.kernel.org/show_bug.cgi?id=88671
--- Comment #1 from Tom Stellard tstel...@gmail.com ---
Created attachment 158391
-- https://bugzilla.kernel.org/attachment.cgi?id=158391action=edit
Backtrace from BUG_ON
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=88671
Bug ID: 88671
Summary: BUG at drivers/pci/ats.c:62! the second time booting a
kvm guest with pci passthrough
Product: Virtualization
Version: unspecified
Kernel Version: 3.17.3
https://bugzilla.kernel.org/show_bug.cgi?id=88671
--- Comment #2 from Tom Stellard tstel...@gmail.com ---
Created attachment 158401
-- https://bugzilla.kernel.org/attachment.cgi?id=158401action=edit
Virtual machine definition
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=88671
--- Comment #3 from Tom Stellard tstel...@gmail.com ---
I should also mention that I have this hook executing when the machine starts
up:
if [ $2 = prepare ]; then
virsh nodedev-detach pci__01_00_1
fi
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=88671
Alex Williamson alex.william...@redhat.com changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Marti Raudsepp ma...@juffo.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #22 from Marti Raudsepp ma...@juffo.org ---
Since I did not get further confirmation from Mr. Schopp, I decided to push it
and submit a patch: https://lkml.org/lkml/2014/10/2/223
The phrases Not sure what is going on here and should
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #19 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #15)
It's not clear to me which devices were being put in the same group.
Hi Joel, any updates on this? I posted my IOMMU groups in comment #17 in case
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #20 from Joel Schopp joel.sch...@amd.com ---
What updates are you looking for? Joerg's fix is now upstream.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #21 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #20)
What updates are you looking for? Joerg's fix is now upstream.
Yes, but there's still the issue with southbridge component isolation. You
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #18 from Joerg Roedel j...@8bytes.org ---
The fix is now upstream and part of Linux v3.17-rc2.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Joerg Roedel j...@8bytes.org changed:
What|Removed |Added
CC||j...@8bytes.org
---
the attachment 146311 patch to
3.16.0 and it fixes the problem. (I verified that unpatched 3.16.0 also
crashes).
I can start shut down the VM multiple times without crashing the host and PCI
passthrough works as expected.
Feel free to add
Tested-by: Marti Raudsepp ma...@juffo.org
(In reply
the VM multiple times without crashing the host and
PCI passthrough works as expected.
Feel free to add
Tested-by: Marti Raudsepp ma...@juffo.org
Thanks for testing the fix, I will send it upstream once the merge window is
over -rc1 is released. I also added a stable tag so it gets
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #15 from Joel Schopp joel.sch...@amd.com ---
(In reply to Joel Schopp from comment #10)
AMD would need to confirm it.
I don't have an answer for you offhand. Let me do some digging and get you
an answer.
I am sorry if I
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #16 from Alex Williamson alex.william...@redhat.com ---
(In reply to Joel Schopp from comment #15)
(In reply to Joel Schopp from comment #10)
AMD would need to confirm it.
I don't have an answer for you offhand. Let me do
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #17 from Marti Raudsepp ma...@juffo.org ---
It's an ASRock FM2A88X Extreme6+ motherboard with the AMD A88X (Bolton-D4)
chipset.
There are 12 IOMMU groups on the system. The problematic group for me is number
9 because the legacy PCI
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #11 from Marti Raudsepp ma...@juffo.org ---
(In reply to Joel Schopp from comment #10)
How would I go about confirming that? What are the chances that they care,
and provide accurate information to a random person?
Are you
On 8/6/14, 2:49 PM, William Tu wrote:
Try vfio-pci instead of pci-assign
Thanks Alex, William. Using vfio worked.
So does that mean pci-assign is being deprecated?
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #1 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145421
-- https://bugzilla.kernel.org/attachment.cgi?id=145421action=edit
crash_netconsole.txt
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Bug ID: 81841
Summary: amd-iommu: kernel BUG lockup after shutting down KVM
guest using PCI passthrough/PCIe bridge
Product: Virtualization
Version: unspecified
Kernel Version
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #2 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145431
-- https://bugzilla.kernel.org/attachment.cgi?id=145431action=edit
startup_dmesg.txt
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #3 from Marti Raudsepp ma...@juffo.org ---
Created attachment 145441
-- https://bugzilla.kernel.org/attachment.cgi?id=145441action=edit
dmidecode.txt
--
You are receiving this mail because:
You are watching the assignee of the bug.
On Wed, 2014-08-06 at 23:12 -0700, Nishank Trivedi wrote:
On 8/6/14, 2:49 PM, William Tu wrote:
Try vfio-pci instead of pci-assign
Thanks Alex, William. Using vfio worked.
So does that mean pci-assign is being deprecated?
Yes, vfio is meant to replace pci-assign with a better device
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Marti Raudsepp ma...@juffo.org changed:
What|Removed |Added
Kernel Version|3.13 (Ubuntu: |3.16.0 (originally Ubuntu
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Alex Williamson alex.william...@redhat.com changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #6 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
vfio: error, group 9 is not viable, please ensure all devices
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #7 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #6)
(In reply to Alex Williamson from comment #5)
What if you use vfio-pci instead of pci-assign?
I run into the dreaded error:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #8 from Marti Raudsepp ma...@juffo.org ---
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the issue.
I see. This page claims so:
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #9 from Alex Williamson alex.william...@redhat.com ---
(In reply to Marti Raudsepp from comment #8)
(In reply to Alex Williamson from comment #7)
There are some proposed workarounds on the web
None of these remotely address the
https://bugzilla.kernel.org/show_bug.cgi?id=81841
Joel Schopp joel.sch...@amd.com changed:
What|Removed |Added
CC||joel.sch...@amd.com
---
Hi
I'm trying to do a pci-passthrough of Intel 82599 10GbE card, with guest
having 8G of memory. I see following error -
intel_iommu_map: iommu width (48) is not sufficient for the mapped
address (fe001000)
kvm_iommu_map_address:iommu failed to map pfn=45800
I checked IOMMU
On Wed, 2014-08-06 at 14:22 -0700, Nishank Trivedi wrote:
Hi
I'm trying to do a pci-passthrough of Intel 82599 10GbE card, with guest
having 8G of memory. I see following error -
intel_iommu_map: iommu width (48) is not sufficient for the mapped
address (fe001000
I encountered the same IOMMU width is not sufficient issue. Using
VFIO works ok for me.
On Wed, Aug 6, 2014 at 2:31 PM, Alex Williamson
alex.william...@redhat.com wrote:
On Wed, 2014-08-06 at 14:22 -0700, Nishank Trivedi wrote:
Hi
I'm trying to do a pci-passthrough of Intel 82599 10GbE card
1 - 100 of 468 matches
Mail list logo