From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
Date: Fri, 30 Mar 2012 11:07:22 GMT [thread overview]
Message-ID: <201203301107.q2UB7ME9024528@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42636-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42636
--- Comment #4 from Klaus Mueller <kmueller@justmail.de> 2012-03-30 11:07:21 ---
Created an attachment (id=72753)
--> (https://bugzilla.kernel.org/attachment.cgi?id=72753)
log of qemu-kvm crash
I tried again with only one pci card inserted (Network controller: RaLink
RT2800 802.11n PCI). The tree is now like this:
+-14.4-[06]----07.0 RaLink RT2800 802.11n PCI
I booted with intel_iommu=on (does this apply to AMD, too?).
If I start the VM now, I'm getting the same error again:
Failed to assign device "hostdev0" : Device or resource busy
qemu-kvm: -device
pci-assign,host=06:07.0,id=hostdev0,configfd=19,bus=pci.0,addr=0x5: Device
'pci-assign' could not be initialized
If I'm additionally putting the bridge to the VM, I'm getting an error telling
me about a missing reset function and another missing thing, too.
If I remove the bridge from the VM xml-file again and start it now, the VM
suddenly starts up fine :-))).
But if the VM is stopped again (with halt in the VM or with virsh shutdown VM,
qemu-kvm crashes and remains as zombie. The output from messages is attached as
iommu-trace.log.
kvm is 0.15.0 and kernel is 3.1.10 (kernel-desktop from openSUSE)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-03-30 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 9:55 [Bug 42636] New: PCI passthrough does not work with AMD iommu for PCI device bugzilla-daemon
2012-01-23 14:56 ` [Bug 42636] " bugzilla-daemon
2012-01-23 16:26 ` bugzilla-daemon
2012-03-30 7:48 ` bugzilla-daemon
2012-03-30 11:07 ` bugzilla-daemon [this message]
2012-03-30 11:29 ` bugzilla-daemon
2012-03-30 11:35 ` bugzilla-daemon
2012-03-30 12:16 ` bugzilla-daemon
2012-04-04 8:22 ` bugzilla-daemon
2012-04-05 8:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201203301107.q2UB7ME9024528@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.