All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42980] BUG in gfn_to_pfn_prot
Date: Sat, 17 Nov 2012 22:00:40 +0000 (UTC)	[thread overview]
Message-ID: <20121117220040.126E811FB58@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42980-28872@https.bugzilla.kernel.org/>

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


Ian Pilcher <arequipeno@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arequipeno@gmail.com




--- Comment #17 from Ian Pilcher <arequipeno@gmail.com>  2012-11-17 22:00:39 ---
I just hit this.

Host:  Intel DQ67SW, Core i7 2600, 24GB RAM
BIOS:  SWQ6710H.86A.0065.2012.0917.1519

Host OS:  Fedora 17
          kernel-3.6.6-1.fc17.x86_64
          qemu-kvm-1.2.0-20.fc17.x86_64

L1 Guest OS:  RHEL 6.3
              kernel-2.6.32-279.14.1.el6.x86_64
              qemu-kvm-rhev-0.12.1.2-2.295.el6_3.5.x86_64

L2 Guest OS:  RHEL 6.3
              kernel-2.6.32-279.14.1.el6.x86_64

I was running a Pulp sync between a couple of L2 guests when this occurred,
which presumably generated quite a bit of traffic across the virtual bridges. 
I am using Open vSwitch for all of the bridges on the host OS.  The virtualized
RHEV hypervisors use standard Linux bridges.

Please let me know if I can provide any additional information to help track
this down.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-11-17 22:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 21:28 [Bug 42980] New: BUG in gfn_to_pfn_prot bugzilla-daemon
2012-03-28 13:03 ` [Bug 42980] " bugzilla-daemon
2012-03-28 13:37 ` bugzilla-daemon
2012-03-28 13:45 ` bugzilla-daemon
2012-03-28 13:49 ` bugzilla-daemon
2012-03-28 15:07 ` bugzilla-daemon
2012-05-10 10:53 ` bugzilla-daemon
2012-05-10 13:17 ` bugzilla-daemon
2012-05-10 13:30 ` bugzilla-daemon
2012-05-17 20:58 ` bugzilla-daemon
2012-06-16  3:16 ` bugzilla-daemon
2012-07-01  9:46 ` bugzilla-daemon
2012-08-15 21:58 ` bugzilla-daemon
2012-08-15 22:24 ` bugzilla-daemon
2012-08-15 22:34 ` bugzilla-daemon
2012-08-15 22:38 ` bugzilla-daemon
2012-08-15 22:47 ` bugzilla-daemon
2012-08-16  9:32 ` bugzilla-daemon
2012-11-17 22:00 ` bugzilla-daemon [this message]
2012-11-17 22:10 ` bugzilla-daemon
2012-11-18 14:15   ` Avi Kivity
2012-11-18 14:15 ` bugzilla-daemon
2012-11-18 17:06 ` bugzilla-daemon
2012-12-08 20:50 ` bugzilla-daemon
2014-06-25  2:11 ` 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=20121117220040.126E811FB58@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.