Hi Lior, Am 16.05.2013 16:12, schrieb Lior Vernia:
Search for a variable called "fake_nics", it should exist for 3.2. By default it is empty, but you may define a pattern for fake NIC names to be passed to the engine (in your case probably "dummy*"). Restart the vdsm daemon and everything should be fine. Maybe you'll have to move the host to maintenance and then reactivate just to refresh the UI.
IT WORKS! :-) Restarting vdsmd was sufficient. Attaching the network to the dummy NIC worked like a charm and a test VM is able to communicate with the Node's dummy NIC. (I just need to setup routing on the Node to get communication with the outside world running.) --- /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.'), Is there a chance to change it from a hard-coded value to a configurable item in a future release of oVirt? Or maybe have a better default value (dummy*) in a bugfix release? Thanks - Frank