kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 76621] Bridged networking stopped working after yum update
Date: Wed, 21 May 2014 20:30:40 +0000	[thread overview]
Message-ID: <bug-76621-28872-McL5VuEaGm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-76621-28872@https.bugzilla.kernel.org/>

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

Michael Tokarev <mjt@tls.msk.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mjt@tls.msk.ru

--- Comment #1 from Michael Tokarev <mjt@tls.msk.ru> ---
Please report this to fedora bugzilla.  Not everyone is running fedora, and not
everyone even understand what yum is.  This problem is most likely
qemu-related, not kernel, at least it has very small chance to have anything to
do with kvm part of the kernel.  And you completely failed to even mention the
versions, from and to, of the components you upgraded.

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

  reply	other threads:[~2014-05-21 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 13:50 [Bug 76621] New: Bridged networking stopped working after yum update bugzilla-daemon
2014-05-21 20:30 ` bugzilla-daemon [this message]
2014-05-22 10:04 ` [Bug 76621] " bugzilla-daemon
2014-05-22 10:05 ` bugzilla-daemon
2014-05-22 10:08 ` bugzilla-daemon
2014-05-22 10:08 ` bugzilla-daemon
2014-05-22 10:09 ` bugzilla-daemon
2014-05-22 10:28 ` bugzilla-daemon
2014-05-22 10:30 ` bugzilla-daemon
2014-05-22 10:31 ` 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-76621-28872-McL5VuEaGm@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 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).