All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 107561] 4.2 breaks PCI passthrough in QEMU/KVM
Date: Thu, 10 Dec 2015 21:51:20 +0000	[thread overview]
Message-ID: <bug-107561-28872-RGKAEM1Skk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-107561-28872@https.bugzilla.kernel.org/>

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

--- Comment #11 from Paolo Bonzini <bonzini@gnu.org> ---
Created attachment 197071
  --> https://bugzilla.kernel.org/attachment.cgi?id=197071&action=edit
OVMF log

> 1) providing host dmesg

Of course this makes no sense, you already did.  And from the traces I suspect
that /proc/mtrr is the same on the two guests.  The culprit seems to be this
MTRR:

 qemu-system-x86-2228  [002]   127.763684: kvm_msr: msr_read 201 = 0xff80000800
 qemu-system-x86-2228  [002]   127.763685: kvm_msr: msr_read 200 = 0x80000000

which is set up by OVMF.  I'm attaching the OVMF output for reference (it can
be extracted from the traces with "trace-cmd report trace-3GBmem.dat |grep
0x402 | awk --non-decimal-data '{printf "%c", 0+$NF}' > OVMF.log").

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

  parent reply	other threads:[~2015-12-10 21:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 12:18 [Bug 107561] New: 4.2 breaks PCI passthrough in QEMU/KVM bugzilla-daemon
2015-11-12 22:20 ` [Bug 107561] " bugzilla-daemon
2015-11-13  0:43 ` bugzilla-daemon
2015-11-16  2:12 ` bugzilla-daemon
2015-11-21 10:03 ` bugzilla-daemon
2015-11-22 23:45 ` bugzilla-daemon
2015-11-22 23:49 ` bugzilla-daemon
2015-11-22 23:51 ` bugzilla-daemon
2015-11-23 18:40 ` bugzilla-daemon
2015-12-10 21:22 ` bugzilla-daemon
2015-12-10 21:24 ` bugzilla-daemon
2015-12-10 21:51 ` bugzilla-daemon [this message]
2015-12-10 22:23 ` bugzilla-daemon
2015-12-11 22:01 ` bugzilla-daemon
2015-12-12  5:52 ` bugzilla-daemon
2015-12-14 15:56 ` 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=bug-107561-28872-RGKAEM1Skk@https.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.