This bug was fixed in the package qemu-kvm - 1.0+noroms-0ubuntu5
---
qemu-kvm (1.0+noroms-0ubuntu5) precise; urgency=low
* define_AT_EMPTY_PATH.patch: Make sure AT_EMPTY_PATH is defined.
(LP: #930181)
* Be smarter about what bridge to attach a TAP device to (LP: #475327):
-
** Package changed: qemu (Ubuntu) => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
qemu -net nic -net tap does not start due to qemu-ifXXX scripts
To manage notifica
** Changed in: qemu (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
qemu -net nic -net tap does not start due to qemu-ifXXX scripts
To manag
I really don't know who "they" are, but chances are good that you know
something I do not, Serge, e.g.: plans, specs, requirements, etc..
Just my $.02 that iproute seems very useful for "digging deeper", but
looks more like an optional package than anything standard. It is
however a dep. of other
Quoting Sean Channel (475...@bugs.launchpad.net):
> I agree with the fix proposed in comment #6, though I question the
> dependency on the "ip" utility (from package "iproute") and using bash-
> specific syntax, vs. the more standard "route" command (from "net-
> tools") e.g.:
>
> switch=`
I agree with the fix proposed in comment #6, though I question the
dependency on the "ip" utility (from package "iproute") and using bash-
specific syntax, vs. the more standard "route" command (from "net-
tools") e.g.:
switch=`route | awk '/^default / { print $8 }'`
Also I would caution
Presumably the occasional desktop user would use virt manager which will
by default attach a veth nic to virbr0?
The reason this bug was raised is that /etc/qemu-ifup assumes the
default route has been bridged.
For the moment, we always create a virbr0, so perhaps qemu-ifup should
attach tap0 to
@Patsev,
you assigned this bug to yourself. Do you intend to push a fix?
If not, I think I'll push the change I detailed in comment #6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
the script is needed to bring up a tap interface. the user would have to
write their own if it does not exist already. perhaps in the interest of
a more user-friendly experience the default script should first start a
bridge if one does not exist.
Requiring a permanant bridge already setup can con
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
qemu -
On 2011-05-03 16:12:53 -, Olivier Mengué <475...@bugs.launchpad.net>
wrote in <20110503161253.22907.24156.mal...@wampee.canonical.com>:
> @dl9sau: if NAT is enough for you, don't use "-net tap": "-net user" is
> much simpler to setup.
This is no option.
It's generally not a good idea to force
@dl9sau: if NAT is enough for you, don't use "-net tap": "-net user" is
much simpler to setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
qemu -net nic -net tap does not start due t
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Patsev Anton (patsev-anton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475327
Title:
qemu -net nic -net tap does not start due to qemu-
Similar problem for me.
I set up the following tap device
$ cat /etc/network/interfaces
# Loopback device:
auto lo
iface lo inet loopback
# device: eth0
auto eth0
iface eth0 inet static
address x.x.x.x
broadcast x.x.x.x
netmask x.x.x.x
gateway x.x.x.x
# default route to acces
14 matches
Mail list logo
