----- Original Message -----
From: "Frank Wall" <fw(a)moov.de>
Sent: Sunday, August 25, 2013 10:38:30 PM
Subject: Re: [Users] How to add internal networks
just installed oVirt 3.3 and noticed that the suggestion from this
thread was included:
> --- /usr/lib64/python2.7/site-packages/vdsm/config.py.orig 2013-03-14
> 11:32:54.000000000 +0100
> +++ /usr/lib64/python2.7/site-packages/vdsm/config.py 2013-05-16
> 16:34:27.722959670 +0200
> @@ -38,7 +38,7 @@
> ('extra_mem_reserve', '65',
> 'Memory reserved for non-vds-administered programs.'),
> - ('fake_nics', '',
> + ('fake_nics', 'dummy*',
> 'Comma-separated list of fnmatch-patterns for dummy hosts
> nics to '
> 'be shown to vdsm.'),
The suggestion was to include a pattern which makes it possible to use
dummy NICs in oVirt, but I think there is a typo:
--- /usr/lib64/python2.7/site-packages/vdsm/config.py.orig 2013-08-22
+++ /usr/lib64/python2.7/site-packages/vdsm/config.py 2013-08-25
@@ -38,7 +38,7 @@
'Memory reserved for non-vds-administered programs.'),
- ('fake_nics', 'dummy_*',
+ ('fake_nics', 'dummy*',
'Comma-separated list of fnmatch-patterns for dummy hosts
nics to '
'be shown to vdsm.'),
As you can see, the new pattern includes dummy NICs, but expect the
devices to be prefixes with "dummy_". Apparently the underscore does not
work. The pattern should expect "dummy*" instead. I did the modification
locally and dummy NICs are working again.
The new pattern is set as 'dummy_' so that the functional tests use
dummies with a different naming conventions that the default kernel pattern
of dummy*. Note that you can create dummies with any name you want with
ip link add drummy type dummy
So you could potentially create your own dummy_250, for example.
Any chance to get this fixed for 3.3 oder maybe 3.3.1?
Users mailing list