search for: gorlov

❦ 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...

On 10/28/2016 05:30 PM, Michal Privoznik wrote: > On 28.10.2016 14:17, Anton Gorlov wrote: >> 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 n...

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

On 28.10.2016 11:09, Anton Gorlov wrote: > Can i assign static vnet* device for some guests? > What do you mean? vnet* devices are created by libvirt when a domain is being started (or on device hotplug). In general, unless all devices would be statically allocated, it would be impossible to guarantee certain vnet name. H...

On 28.10.2016 14:17, Anton Gorlov wrote: > 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 >...

ut 2.4.1 works with megatec_usb driver. It tries to interact with a device in /dev/bus/usb/X/Y, but there are root:root 664 access rights. When I try to set port /dev/hiddev0 with write access in config file, in strace there are no records about accessing /dev/hiddev, but still only /dev/bus/usb/X/Y How to explain such a behavior? execve("./megatec_usb",

after I starting battery test on my laptop I see in my logs some error and ups (IPPON Smart Power Pro 1400. usb interface) isn't monitoring now [ippon] driver = megatec_usb port = auto desc = "local" Feb 16 23:22:09 f37 upsd[17150]: Instant command: stlk at 127.0.0.1 did test.battery.start on ippon Feb 16 23:22:12 f37 megatec_usb[17249]: ser_get_line: Device detached? (error

I try to add some rules to filtering network, example <filterref filter='clean-traffic'/> or <filterref filter='no-ip-spoofing'/> and vm not starting with message virsh start freebsd8.2 error: Failed to start domain freebsd8.2 error: internal error IP parameter must be given since libvirt was not compiled with IP address learning support what do I do wrong?

I would like to use jumbo frame for local interfaces, but I am not sure in which order to set it up. Should it be set on the physical interface first, then on the bridge and on the guest, or in another way? On some servers there are configurations with vlan on the bridge

Hi all. What right way to protect ip/mac spoofing for guests withnount dhcp and other 1 ip per guest?

Can i assign static vnet* device for some guests?

If I add VG with some other lv-s to libvirt pool then libvirt slow responding. How to fix it? <pool type='logical'> <name>LVM_MAIN</name> <uuid>a2713bed-ad4a-fb79-83b5-65a9e8f1094e</uuid> <capacity>0</capacity> <allocation>0</allocation> <available>0</available> <source>

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

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

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