From: Michael Tokarev <1352555@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1352555] Re: iproute2 incompatibility
Date: Tue, 05 Aug 2014 09:35:30 -0000 [thread overview]
Message-ID: <20140805093532.21774.3668.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 20140804210526.23780.8062.malonedeb@wampee.canonical.com
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1352555
Title:
iproute2 incompatibility
Status in QEMU:
Invalid
Bug description:
installed iproute2 which replaced ifupdown, kvm no longer connects to
tap devices and is unable to create spice sockets
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1352555/+subscriptions
next prev parent reply other threads:[~2014-08-05 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 21:05 [Qemu-devel] [Bug 1352555] [NEW] iproute2 incompatibility swestlake
2014-08-05 9:35 ` Michael Tokarev [this message]
2014-08-05 9:44 ` [Qemu-devel] [Bug 1352555] " Michael Tokarev
2014-08-08 6:31 ` swestlake
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=20140805093532.21774.3668.launchpad@soybean.canonical.com \
--to=1352555@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).