kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218876] PCIE device crash when trying to pass through USB PCIe Card to virtual machine
Date: Wed, 29 May 2024 11:35:36 +0000	[thread overview]
Message-ID: <bug-218876-28872-BcD5SvU0nn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218876-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218876

--- Comment #11 from Dan Alderman (dan@danalderman.co.uk) ---
Just tried with the new card:

02:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host
Controller

I added it to the VM in virt-manager and I get the same error when I launch it.

[snip]

kernel: pcieport 0000:00:09.0: broken device, retraining non-functional
downstream link at 2.5GT/s

[snip]

vfio-pci 0000:02:00.0: not ready 4095ms after bus reset; waiting

Thanks.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2024-05-29 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 19:31 [Bug 218876] New: PCIE device crash when trying to pass through USB Device to virtual machine bugzilla-daemon
2024-05-22 19:32 ` [Bug 218876] " bugzilla-daemon
2024-05-22 19:34 ` [Bug 218876] PCIE device crash when trying to pass through USB PCIe Card " bugzilla-daemon
2024-05-22 20:38 ` bugzilla-daemon
2024-05-23 14:35 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-24 11:19 ` bugzilla-daemon
2024-05-25 13:49 ` bugzilla-daemon
2024-05-25 14:16 ` bugzilla-daemon
2024-05-25 14:20 ` bugzilla-daemon
2024-05-28 21:16 ` bugzilla-daemon
2024-05-29 10:42 ` bugzilla-daemon
2024-05-29 11:35 ` bugzilla-daemon [this message]

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=bug-218876-28872-BcD5SvU0nn@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).