qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1352555] Re: iproute2 incompatibility


From: Michael Tokarev
Subject: [Qemu-devel] [Bug 1352555] Re: iproute2 incompatibility
Date: Tue, 05 Aug 2014 09:44:41 -0000

This is a Very Useful BugReport (NOT!).

Qemu does not use neither ifupdown nor iproute.  Instead, it runs a
script, /etc/qemu-ifup by default, which should use whatever commands
needed on the given operating system to do whatever configuration of the
tap devices which is necessary.  But qemu itself does not provide such a
script.

So you can't file such a bug against qemu because qemu just does not
HAVE this functionality to start with.

The script is expected to be provided by the user, and it can be as
large as a one line which adds a given (as an argument) tap device to a
user-specifid bridge.  But this script greatly depends on the particular
network details, -- eg, some prefer to have multiple bridges for
different purposes, some prefer not to have any bridges at all (tap
device will work without a bridge just fine), some may use these tap
devices to assign them to lxc containers and so on and so forth.  That's
why you have to provide this script by your own - a script which suits
_your_ needs.

Debian and ubuntu provides such scripts which covers "simple" case where
all guest tap devices are assigned to a bridge wich has a default route
on it, provided such a bridge exists.  Both debian and ubuntu scripts
will work with either ifconfig/route/bridge or with iproute2 package
just fine, will use whatever is avilable/installed on the system.   So
it should not be debian/ubuntu problem either.

And one more thing: ifupdown, at least in ubuntu/debian, is _not_ being
replaced by iproute2.  This is just gross (again, at least on
debian/ubuntu).  Ifupdown package provides network configuration in
/etc/network/, and it uses either iproute2 OR net-tools (which is the
old ifconfig/route/... network toolset).  So it is old ifconfig which is
being "replaced" by iproute2, not ifupdown.  But since you haven't
specified any details at all, it is difficult to say whenever this
comment applies to your distribution (as it isn't even know which
distribution it is).

Closing this bugreport as 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]