1. 09 12月, 2014 2 次提交
    • L
      util: functions to manage bridge fdb (forwarding database) · 19a5474d
      Laine Stump 提交于
      These two functions use netlink RTM_NEWNEIGH and RTM_DELNEIGH messages
      to add and delete entries from a bridge's fdb. The bridge itself is
      not referenced in the arguments to the functions, only the name of the
      device that is attached to the bridge (since a device can only be
      attached to one bridge at a time, and must be attached for this
      function to make sense, the kernel easily infers which bridge's fdb is
      being modified by looking at the device name/index).
      19a5474d
    • L
      util: new functions for setting bridge and bridge port attributes · 100b7a72
      Laine Stump 提交于
      These functions all set/get items in the sysfs for a bridge device.
      100b7a72
  2. 01 12月, 2014 1 次提交
  3. 24 11月, 2014 2 次提交
  4. 21 11月, 2014 1 次提交
  5. 19 11月, 2014 1 次提交
  6. 12 11月, 2014 1 次提交
  7. 10 11月, 2014 1 次提交
  8. 06 11月, 2014 2 次提交
  9. 04 11月, 2014 2 次提交
  10. 03 11月, 2014 1 次提交
  11. 29 10月, 2014 3 次提交
  12. 23 10月, 2014 1 次提交
  13. 22 10月, 2014 1 次提交
  14. 15 10月, 2014 4 次提交
  15. 07 10月, 2014 1 次提交
  16. 06 10月, 2014 1 次提交
    • L
      conf: add trustGuestRxFilters attribute to network and domain interface · 07450cd4
      Laine Stump 提交于
      This new attribute will control whether or not libvirt will pay
      attention to guest notifications about changes to network device mac
      addresses and receive filters. The default for this is 'no' (for
      security reasons). If it is set to 'yes' *and* the specified device
      model and connection support it (currently only macvtap+virtio) then
      libvirt will watch for NIC_RX_FILTER_CHANGED events, and when it
      receives one, it will issue a query-rx-filter command, retrieve the
      result, and modify the host-side macvtap interface's mac address and
      unicast/multicast filters accordingly.
      
      The functionality behind this attribute will be in a later patch. This
      patch merely adds the attribute to the top-level of a domain's
      <interface> as well as to <network> and <portgroup>, and adds
      documentation and schema/xml2xml tests. Rather than adding even more
      test files, I've just added the net attribute in various applicable
      places of existing test files.
      07450cd4
  17. 02 10月, 2014 1 次提交
    • G
      qemu: use systemd's TerminateMachine to kill all processes · 4882618e
      Guido Günther 提交于
      If we don't properly clean up all processes in the
      machine-<vmname>.scope systemd won't remove the cgroup and subsequent vm
      starts fail with
      
        'CreateMachine: File exists'
      
      Additional processes can e.g. be added via
      
        echo $PID > /sys/fs/cgroup/systemd/machine.slice/machine-${VMNAME}.scope/tasks
      
      but there are other cases like
      
        http://bugs.debian.org/761521
      
      Invoke TerminateMachine to be on the safe side since systemd tracks the
      cgroup anyway. This is a noop if all processes have terminated already.
      4882618e
  18. 25 9月, 2014 2 次提交
  19. 24 9月, 2014 3 次提交
  20. 16 9月, 2014 1 次提交
  21. 15 9月, 2014 1 次提交
  22. 12 9月, 2014 1 次提交
  23. 10 9月, 2014 1 次提交
    • M
      conf: Extend <loader/> and introduce <nvram/> · 68bf13db
      Michal Privoznik 提交于
      Up to now, users can configure BIOS via the <loader/> element. With
      the upcoming implementation of UEFI this is not enough as BIOS and
      UEFI are conceptually different. For instance, while BIOS is ROM, UEFI
      is programmable flash (although all writes to code section are
      denied). Therefore we need new attribute @type which will
      differentiate the two. Then, new attribute @readonly is introduced to
      reflect the fact that some images are RO.
      
      Moreover, the OVMF (which is going to be used mostly), works in two
      modes:
      1) Code and UEFI variable store is mixed in one file.
      2) Code and UEFI variable store is separated in two files
      
      The latter has advantage of updating the UEFI code without losing the
      configuration. However, in order to represent the latter case we need
      yet another XML element: <nvram/>. Currently, it has no additional
      attributes, it's just a bare element containing path to the variable
      store file.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Acked-by: NLaszlo Ersek <lersek@redhat.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      68bf13db
  24. 09 9月, 2014 1 次提交
    • E
      blockcopy: add a way to parse disk source · 37588b25
      Eric Blake 提交于
      The new blockcopy API wants to reuse only a subset of the disk
      hotplug parser - namely, we only care about the embedded
      virStorageSourcePtr inside a <disk> XML.  Strange as it may
      seem, it was easier to just parse an entire disk definition,
      then throw away everything but the embedded source, than it
      was to disentangle the source parsing code from the rest of
      the overall disk parsing function.  All that I needed was a
      couple of tweaks and a new internal flag that determines
      whether the normally-mandatory target element can be
      gracefully skipped, since everything else was already optional.
      
      * src/conf/domain_conf.h (virDomainDiskSourceParse): New
      prototype.
      * src/conf/domain_conf.c (VIR_DOMAIN_XML_INTERNAL_DISK_SOURCE):
      New flag.
      (virDomainDiskDefParseXML): Honor flag to make target optional.
      (virDomainDiskSourceParse): New function.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      37588b25
  25. 03 9月, 2014 1 次提交
  26. 28 8月, 2014 1 次提交
  27. 25 8月, 2014 1 次提交
    • R
      fdstream: introduce virFDStreamOpenBlockDevice · f5b4c141
      Roman Bogorodskiy 提交于
      virStorageBackendVolDownloadLocal and virStorageBackendVolUploadLocal
      use virFDStreamOpenFile function to work with the volume fd.
      
      virFDStreamOpenFile calls virFDStreamOpenFileInternal that implements
      handling of the non-blocking I/O. If a file is not a character device and
      not a fifo, it uses libvirt_iohelper.
      
      On FreeBSD, it doesn't work as expected because disk devices (including
      ZFS volumes) are exposed as character devices, and ZFS volumes do not
      support open(2) with O_NONBLOCK.
      
      To overcome this, introduce a forceIOHelper flag to
      virFDStreamOpenFileInternal that forces using libvirt_iohelper. And
      introduce virFDStreamOpenBlockDevice that calls
      virFDStreamOpenFileInternal with the forceIOHelper set to true.
      f5b4c141
  28. 22 8月, 2014 1 次提交