1. 14 7月, 2018 8 次提交
  2. 13 7月, 2018 2 次提交
  3. 10 7月, 2018 1 次提交
  4. 04 7月, 2018 1 次提交
    • B
      util:Fix with process number and pid file do not match · d6cfa0cd
      Bobo Du 提交于
      the libvirtd pid file is not match the os process pid number
      which is smaller than before.
      
      this would be exist if the libvirtd process coredump or the os
      process was killed which the next pid number is smaller.
      
      you can be also edit the pid file to write the longer number than
      before,then restart the libvirtd service.
      Signed-off-by: NBobo Du <dubo163@126.com>
      d6cfa0cd
  5. 03 7月, 2018 3 次提交
  6. 27 6月, 2018 1 次提交
  7. 26 6月, 2018 2 次提交
    • D
      nwfilter: export port binding concept in the public API · b57a9aec
      Daniel P. Berrangé 提交于
      When the daemons are split there will need to be a way for the virt
      drivers and/or network driver to create and delete bindings between
      network ports and network filters. This defines a set of public APIs
      that are suitable for managing this facility.
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      b57a9aec
    • J
      util: fix mount issue by moving NULL value to "none" in syscall. · 794b576c
      Julio Faracco 提交于
      After running libvirt daemon with valgrind tools, some errors are
      appearing when you try to start a domain. One example:
      
      ==18012== Syscall param mount(type) points to unaddressable byte(s)
      ==18012==    at 0x6FEE3CA: mount (syscall-template.S:78)
      ==18012==    by 0x531344D: virFileMoveMount (virfile.c:3828)
      ==18012==    by 0x27FE7675: qemuDomainBuildNamespace (qemu_domain.c:11501)
      ==18012==    by 0x2800C44E: qemuProcessHook (qemu_process.c:2870)
      ==18012==    by 0x52F7E1D: virExec (vircommand.c:726)
      ==18012==    by 0x52F7E1D: virCommandRunAsync (vircommand.c:2477)
      ==18012==    by 0x52F4EDD: virCommandRun (vircommand.c:2309)
      ==18012==    by 0x2800A731: qemuProcessLaunch (qemu_process.c:6235)
      ==18012==    by 0x2800D6B4: qemuProcessStart (qemu_process.c:6569)
      ==18012==    by 0x28074876: qemuDomainObjStart (qemu_driver.c:7314)
      ==18012==    by 0x280522EB: qemuDomainCreateWithFlags (qemu_driver.c:7367)
      ==18012==    by 0x55484BF: virDomainCreate (libvirt-domain.c:6531)
      ==18012==    by 0x12CDBD: remoteDispatchDomainCreate (remote_daemon_dispatch_stubs.h:4350)
      ==18012==    by 0x12CDBD: remoteDispatchDomainCreateHelper (remote_daemon_dispatch_stubs.h:4326)
      ==18012==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
      
      Some documentation recommends to use "none" when you don't have a
      filesystem type to use. Specially, for bind and move actions.
      Signed-off-by: NJulio Faracco <jcfaracco@gmail.com>
      794b576c
  8. 14 6月, 2018 1 次提交
  9. 11 6月, 2018 1 次提交
  10. 08 6月, 2018 10 次提交
  11. 07 6月, 2018 2 次提交
  12. 06 6月, 2018 4 次提交
  13. 05 6月, 2018 4 次提交