1. 08 4月, 2020 1 次提交
  2. 03 4月, 2020 1 次提交
  3. 27 3月, 2020 6 次提交
  4. 20 3月, 2020 1 次提交
  5. 16 3月, 2020 1 次提交
  6. 24 2月, 2020 3 次提交
  7. 11 2月, 2020 9 次提交
  8. 07 2月, 2020 3 次提交
    • D
      gnulib: delete all gnulib integration · 2621d48f
      Daniel P. Berrangé 提交于
      This deletes all trace of gnulib from libvirt. We still
      have the keycodemapdb submodule to deal with. The simple
      solution taken was to update it when running autogen.sh.
      
      Previously gnulib could auto-trigger refresh when running
      'make' too. We could figure out a solution for this, but
      with the pending meson rewrite it isn't worth worrying
      about, given how infrequently keycodemapdb changes.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      2621d48f
    • D
      util: import an event loop impl based on GMainContext · f8ab47cb
      Daniel P. Berrangé 提交于
      The libvirt-glib project has provided a GMainContext based
      event loop impl for applications. This imports it and sets
      it up for use by libvirt as the primary event loop. This
      remains a private impl detail of libvirt.
      
      IOW, applications must *NOT* assume that a call to
      "virEventRegisterDefaultImpl" results in a GLib based
      event loop. They should continue to use the libvirt-glib
      API gvir_event_register() if they explicitly want to
      guarantee a GLib event loop.
      
      This follows the general principle that the libvirt public
      API should not expose the fact that GLib is being used
      internally.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      f8ab47cb
    • D
      src: introduce helper API for creating GSource for socket · 5de317b8
      Daniel P. Berrangé 提交于
      We need to be able to create event loop watches using the
      GSource API for sockets. GIOChannel is able todo this, but
      we don't want to use the GIOChannel APIs for reading/writing,
      and testing shows just using its GSource APIs is unreliable
      on Windows.
      
      This patch thus creates a standalone helper API for creating
      a GSource for a socket file descriptor. This impl is derived
      from code in QEMU's io/channel-watch.c file that was written
      by myself & Paolo Bonzini & thus under Red Hat copyright.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      5de317b8
  9. 29 1月, 2020 2 次提交
  10. 27 1月, 2020 1 次提交
    • D
      qemu: introduce a new "virt-qemu-run" program · d6006672
      Daniel P. Berrangé 提交于
      The previous "QEMU shim" proof of concept was taking an approach of only
      caring about initial spawning of the QEMU process. It was then
      registered with the libvirtd daemon who took over management of it. The
      intent was that later libvirtd would be refactored so that the shim
      retained control over the QEMU monitor and libvirt just forwarded APIs
      to each shim as needed. This forwarding of APIs would require quite alot
      of significant refactoring of libvirtd to achieve.
      
      This impl thus takes a quite different approach, explicitly deciding to
      keep the VMs completely separate from those seen & managed by libvirtd.
      Instead it uses the new "qemu:///embed" URI scheme to embed the entire
      QEMU driver in the shim, running with a custom root directory.
      
      Once the driver is initialization, the shim starts a VM and then waits
      to shutdown automatically when QEMU shuts down, or should kill QEMU if
      it is terminated itself. This ought to use the AUTO_DESTROY feature but
      that is not yet available in embedded mode, so we rely on installing a
      few signal handlers to gracefully kill QEMU. This isn't reliable if
      we crash of course, but you can restart with the same root dir.
      
      Note this program does not expose any way to manage the QEMU process,
      since there's no RPC interface enabled. It merely starts the VM and
      cleans up when the guest shuts down at the end. This program is
      installed to /usr/bin/virt-qemu-run enabling direct use by end users.
      Most use cases will probably want to integrate the concept directly
      into their respective application codebases. This standalone binary
      serves as a nice demo though, and also provides a way to measure
      performance of the startup process quite simply.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      d6006672
  11. 17 1月, 2020 6 次提交
  12. 03 1月, 2020 2 次提交
  13. 20 12月, 2019 1 次提交
  14. 10 12月, 2019 2 次提交
  15. 04 12月, 2019 1 次提交