search for: visrh

...vice (or name that we can use > for the device). If you start the domain, with your configuration > libvirt will create vnetX and plug it into br1. Essentially, target > device is runtime information, thus not present in config XML. ... but *is* in the status xml (i.e. the output of "visrh dumpxml $domain" while the domain is running, and also the xml provided on stdin to the qemu and network hooks when they are called). (also, what Vincent said in his email - names with the prefix "vnet" are assumed to be "leftover" from a previous instance of the domain...

❦ 3 novembre 2016 20:43 +0300, Anton Gorlov <stalker@altlinux.ru> : >> ... but *is* in the status xml (i.e. the output of "visrh dumpxml >> $domain" while the domain is running, and also the xml provided on stdin >> to the qemu and network hooks when they are called). >> >> (also, what Vincent said in his email - names with the prefix "vnet" are >> assumed to be "leftover&qu...

31.10.2016 16:45, Laine Stump пишет: > ... but *is* in the status xml (i.e. the output of "visrh dumpxml > $domain" while the domain is running, and also the xml provided on stdin > to the qemu and network hooks when they are called). > > (also, what Vincent said in his email - names with the prefix "vnet" are > assumed to be "leftover" from a previous...

03.11.2016 21:49, Vincent Bernat пишет: >>> ... but *is* in the status xml (i.e. the output of "visrh dumpxml >>> $domain" while the domain is running, and also the xml provided on stdin >>> to the qemu and network hooks when they are called). >>> (also, what Vincent said in his email - names with the prefix "vnet" are >>> assumed to be "lefto...

28.10.2016 23:32, Michal Privoznik пишет: On my host node i using system created bridge. example brctl show br1 bridge name bridge id STP enabled interfaces br1 8000.0025907925d3 no eth1 vnet0 vnet2