From: Valentin Meriel <valentin.meriel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] VFIO bug with Sata controler (AsMedia1061)
Date: Mon, 2 Dec 2013 00:52:16 +0100 [thread overview]
Message-ID: <CABSSjJdh5TB_89nSPyMU-rFjkfQ_X_wMMLwt38f3GKBS-eHo8g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Hello,
I want to report to you a really big bug.
vfio passthrough dont works with Sata controler (an AsMedia 1061) ! When i
try to use vfio with this controler it work only once.
When i use vfio for VGA i can reboot (or shutdown and start again) my VM
with out problem, but for any other PCI card the VM refuse to reboot.
In dmesg i have this error :
[ 404.206866] dmar: DRHD: handling fault status reg 2
[ 404.206870] dmar: DMAR:[DMA Write] Request device [07:00.0] fault addr
2affdf000
[ 404.206870] DMAR:[fault reason 05] PTE Write access is not set
[ 404.206877] dmar: DRHD: handling fault status reg 2
[ 404.206879] dmar: DMAR:[DMA Read] Request device [07:00.0] fault addr
2affda000
[ 404.206879] DMAR:[fault reason 06] PTE Read access is not set
Thanks.
[-- Attachment #2: Type: text/html, Size: 867 bytes --]
reply other threads:[~2013-12-01 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABSSjJdh5TB_89nSPyMU-rFjkfQ_X_wMMLwt38f3GKBS-eHo8g@mail.gmail.com \
--to=valentin.meriel@gmail.com \
--cc=qemu-devel@nongnu.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).