On Mon, Jan 20, 2014 at 10:23 PM, Alexandre Kandalintsev
s...@messir.net wrote:
I was worried that the amount of changes would
turn the maintainers away from the patch.
Another problem is that I think there is little demand
for this patch.
But let's try to push it once again. Give me a week
Hi William,
I was worried that the amount of changes would
turn the maintainers away from the patch.
Another problem is that I think there is little demand
for this patch.
But let's try to push it once again. Give me a week or
two and I'll submit a new version.
--
best regards,
Alexandre
Hi
Hi Alexandre,
On Mon, Mar 25, 2013 at 10:28 PM, Alexandre Kandalintsev
s...@messir.net wrote:
Ok, lets go this way. We will define patterns in bridge.conf like
~~~
allowifname vm*
~~~
Do you have any news about this patch?
Regards,
--
William
On Thu, Mar 21, 2013 at 07:05:09PM +0100, Alexandre Kandalintsev wrote:
Hi!
Here is the patch that allows us to specify the name of tap interface
when -netdev bridge is used. It's like -netdev tap,ifname=xxx, but for
bridges.
** Motivation **
We've got zillions of VMs and would
By default, custom names should not be allowed. Perhaps the
qemu-bridge-helper configuration file needs an option to specify a
glob pattern, e.g. vm*.
This way the host system administrator can restrict network interface
names while still allowing humand-friendly names.
Ok, lets go this
Hi!
Here is the patch that allows us to specify the name of tap interface
when -netdev bridge is used. It's like -netdev tap,ifname=xxx, but for
bridges.
** Motivation **
We've got zillions of VMs and would like to see meaningful names of tap
interfaces. This is really useful for for, e.g.,
On 03/21/2013 12:05 PM, Alexandre Kandalintsev wrote:
Hi!
Here is the patch that allows us to specify the name of tap interface
when -netdev bridge is used. It's like -netdev tap,ifname=xxx, but for
bridges.
+++ b/qapi-schema.json
@@ -2676,6 +2676,7 @@
{ 'type':
