From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: kvm developers <kvm@vger.kernel.org>
Subject: PCI device passthrough for FreeDOS guests
Date: Mon, 13 Jul 2009 18:16:20 +0200 [thread overview]
Message-ID: <4A5B5DD4.2060907@gmx.net> (raw)
Hi,
I want to trace the PCI device accesses (config space, I/O ports, memory
BARs) of a DOS application (EEPROM flasher) and it seems KVM can help
with this.
The current plan is to install KVM, use FreeDOS as a guest, activate
passthrough for the PCI device I'm interested in and log the accesses
somehow.
Possible problems I'd have to solve:
- According to
http://www.linux-kvm.org/wiki/images/d/d0/KvmForum2008$kdf2008_14.pdf
PCI device passthrough needs a CPU with VT-d/IOMMU support.
- http://www.linux-kvm.org/page/TODO says passthrough won't work for
conventional PCI devices (I assume a PCI graphics card is such a device).
- http://www.linux-kvm.org/page/TODO says passthrough won't work for
devices without Function Level Reset (FLR).
- http://www.linux-kvm.org/page/TODO says VT support for real mode is
not good, so FreeDOS might be a problem.
- The KVM wiki does not mention how to get PCI passthrough working.
- No idea if logging of PCI accesses is possible with KVM or if I have
to use helper tools for that.
Any insights/hints are appreciated. If KVM is the wrong tool for my
task, please point me in the right direction.
Please CC me as I'm not subscribed to the list. Thanks.
Regards,
Carl-Daniel
P.S. The linux-kvm.org wiki returns zero results if you search the wiki
text for "PCI", but a Google search finds quite a few pages mentioning
PCI. Is there a bug in the seach function?
next reply other threads:[~2009-07-13 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 16:16 Carl-Daniel Hailfinger [this message]
2009-07-14 1:49 ` PCI device passthrough for FreeDOS guests Han, Weidong
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=4A5B5DD4.2060907@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--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