From: Jan Kiszka <jan.kiszka@web.de>
To: Erik Brakkee <erik@brakkee.org>
Cc: kvm@vger.kernel.org
Subject: Re: PCI passthrough on Sony Vaio F11 laptop...
Date: Mon, 15 Nov 2010 23:53:48 +0100 [thread overview]
Message-ID: <4CE1B9FC.6050500@web.de> (raw)
In-Reply-To: <4CE1AC5E.4050604@brakkee.org>
[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]
Am 15.11.2010 22:55, Erik Brakkee wrote:
> Jan Kiszka wrote:
>> Am 14.11.2010 14:21, Erik Brakkee wrote:
>>
>>> Jan Kiszka wrote:
>>>
>>>> Strange, should work. I would suggest to post your full kernel log,
>>>> maybe there is some enlightening message hidden.
>>>>
>>>> I don't think it is a problem of your kernel version, but I'm able to
>>>> pass through devices on OpenSUSE 11.3 with
>>>> kernel-desktop-2.6.36-90.1.x86_64 from their kernel repository.
>>>>
>>>> Jan
>>>>
>>>>
>>>>
>>> Exactly what server logs do you need. Is this only /var/log/messages or
>>> more? And do I need to set specific options there?
>>> Any other log files that you need?
>>>
>> dmesg> log-file
>>
>>
>>> Before, generating these logs I will upgrade to a later kernel. As far
>>> as I can tell, that will still be a 2.6.34 kernel. Perhaps I should try
>>> the 2.6.36 kernel as well. Do you have the URL for the kernel repository
>>> I should use? (cannot find an obvious kernel repository in YAST2).
>>>
>> http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3
>>
>> Jan
>>
>>
> I have attached the logs of /var/log/messages, dmesg, and qemu log
> (other.log), as well as the kernel config parameters (/proc/config.gz).
> I did the test with two kernels (see the tar.gz file): one kernel a
> 2.6.34 and the other a 2.6.36 kernel.
Comparing the dmesg with my kernel log, I'm missing messages like
[ 0.023960] DMAR: Host address width 36
[ 0.023962] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.023968] IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c9008020e30272 ecap 1000
[ 0.023970] DMAR: DRHD base: 0x000000fed93000 flags: 0x1
[ 0.023974] IOMMU 1: reg_base_addr fed93000 ver 1:0 cap c9008020630272 ecap 1000
[ 0.023976] DMAR: RMRR base: 0x000000bf6e9000 end: 0x000000bf6fffff
[ 0.023978] DMAR: No ATSR found
about the Intel DMAR (IOMMU) setup.
Are you sure that you have an Intel chipset with the required features?
And have you checked that "VT-d" is enabled in the BIOS (or however it
may be called there)?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-11-15 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:31 PCI passthrough on Sony Vaio F11 laptop Erik Brakkee
2010-11-13 11:20 ` Jan Kiszka
2010-11-13 11:42 ` Erik Brakkee
2010-11-13 19:03 ` Jan Kiszka
2010-11-14 13:21 ` Erik Brakkee
2010-11-14 15:57 ` Jan Kiszka
[not found] ` <4CE1AC5E.4050604@brakkee.org>
2010-11-15 22:53 ` Jan Kiszka [this message]
2010-12-05 21:47 ` Erik Brakkee
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=4CE1B9FC.6050500@web.de \
--to=jan.kiszka@web.de \
--cc=erik@brakkee.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