1. 17 6月, 2016 16 次提交
    • P
      conf: Remove pre-calculation of initial memory size · a877a163
      Peter Krempa 提交于
      While we need to know the difference between the total memory stored in
      <memory> and the actual size not included in the possible memory modules
      we can't pre-calculate it reliably. This is due to the fact that
      libvirt's XML is copied via formatting and parsing the XML and the
      initial memory size can be reliably calculated only when certain
      conditions are met due to backwards compatibility.
      
      This patch removes the storage of 'initial_memory' and fixes the helpers
      to recalculate the initial memory size all the time from the total
      memory size. This conversion is possible when we also make sure that
      memory hotplug accounts properly for the update of the total memory size
      and thus the helpers for inserting and removing memory devices need to
      be tweaked too.
      
      This fixes a bug where a cold-plug and cold-remove of a memory device
      would increase the size reported in <memory> in the XML by the size of
      the memory device. This would happen as the persistent definition is
      copied before attaching the device and this would lead to the loss of
      data in 'initial_memory'.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1344892
      a877a163
    • P
      conf: Fix perf event parser · 23690e1d
      Peter Krempa 提交于
      The parser was totaly broken. Fix it by rewriting it. Add tests so that
      it doesn't happen.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1346723
      23690e1d
    • P
      qemu: perf: Don't set state of first event for every other event · da8285c4
      Peter Krempa 提交于
      A bug in the code used the value of the first perf event as state for
      all the mentioned one rather than extracting individual ones.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1346730
      da8285c4
    • J
      xenconfig: fix conversion of <driver> to backendtype · e33cd67a
      Jim Fehlig 提交于
      When converting domXML to xen xl.cfg, backendtype should
      not be emitted if <driver> is not specified. Moreover,
      <driver name='file'/> should be converted to backendtype
      qdisk, similar to handling of <driver> in libxlMakeDisk()
      in libxl_conf.c.
      
      Prior to this change, connectDomainXMLToNative would
      produce incorrect xl.cfg when the input domXML contained
      <driver name='file'/>
      
      domXML:
      
        <disk type="file" device="disk">
          <driver name="file"/>
          <source file="/image/file/path"/>
          <target dev="xvda" bus="xen"/>
        </disk>
      
      virsh domxml-to-native xen-xl domXML
      
      disk = [ "format=raw,vdev=xvda,access=rw,backendtype=target=/image/file/path" ]
      
      xl create xl.cfg
      config parsing error in disk specification: unknown value
      for backendtype: near `target=/image/file/path' in
      `format=raw,vdev=xvda,access=rw,backendtype=target=/image/file/path'
      e33cd67a
    • L
      util: fix missing broadcast address in bridge and tap device IP addresses · bf913385
      Laine Stump 提交于
      Commit b3d06987 added peer address setting to the low level
      virNetDevSetIPAddress() function, but ended up causing a segfault in
      cases where the caller passed NULL for peer address.
      
      Commit a3510e33 fixed the segfault, but managed to cause us to
      skip setting the broadcast address when setting an interface's IP
      address. The result is that the broadcast address is 0.0.0.0 for all
      libvirt-created bridges (and interfaces in lxc containers with IP
      addresses set by libvirt).
      
      This was reported on the mailing list:
      
        https://www.redhat.com/archives/libvir-list/2016-June/msg00027.html
      
      but I was too busy to investigate at the time. I found it by accident
      today while refactoring virNetDevSetIPAddress(). Since this regression
      is present in the 1.3.5 release, I'm sending the bugfix as a separate
      patch from my larger refactoring patchset.
      bf913385
    • L
      qemu: don't add pci-bridge to Q35/arm domains unless it's needed · d5fb8f45
      Laine Stump 提交于
      Until now, a Q35 domain (or arm/virt, or any other domain that has a
      pcie-root bus) would always have a pci-bridge added, so that there
      would be a hotpluggable standard PCI slot available to plug in any PCI
      devices that might be added. This patch removes the explicit add,
      instead relying on the pci-bridge being auto-added during PCI address
      assignment (it will add a pci-bridge if there are no free slots).
      
      This doesn't eliminate the dmi-to-pci-bridge controller that is
      explicitly added whether or not a standard PCI slot is required (and
      that is almost never used as anything other than a converter between
      pcie.0's PCIe slots and standard PCI). That will be done separately.
      d5fb8f45
    • L
      qemu: don't be as insistent about adding dmi-to-pci-bridge or pci-bridge · 97b215a4
      Laine Stump 提交于
      Previously there was no way to have a Q35 domain that didn't have
      these two controllers. This patch skips their creation as long as
      there are some other kinds of pci controllers at index 1 and 2
      (e.g. some pcie-root-port controllers).
      
      I'm hoping that soon we won't add them at all, plugging all devices
      into auto-added pcie-*-port ports instead, but in the meantime this
      makes it easier to experiment with alternative bus hierarchies.
      97b215a4
    • C
      util: remove redundant comments · e9df5305
      Chen Hanxiao 提交于
      Signed-off-by: NChen Hanxiao <chenhanxiao@gmail.com>
      e9df5305
    • J
      storage: implement storage lifecycle event APIs · 41b2f108
      Jovanka Gulicoska 提交于
      Implement storage pool event callbacks for START, STOP, DEFINE, UNDEFINED
      and REFRESHED in functions when a storage pool is created/started/stopped
      etc. accordingly
      41b2f108
    • J
      remote: implement storage lifecycle event APIs · 22fb4374
      Jovanka Gulicoska 提交于
      22fb4374
    • J
      test: implement storage lifecycle event APIs · edc1a27a
      Jovanka Gulicoska 提交于
      Also includes unittests for storage pool lifecycle events API
      edc1a27a
    • J
      conf: add storage_event handling · dc7b849a
      Jovanka Gulicoska 提交于
      Add storage event handling infrastructure to storage_event.[ch], following
      the network_event.[ch] pattern.
      dc7b849a
    • J
      Introduce storage lifecycle event APIs · 1328f982
      Jovanka Gulicoska 提交于
      Storage pool lifecycle event API entry points for registering and deregistering
      storage pool events, as well as types of events associated with storage pools.
      These entry points will be used for implementing asynchronous lifecycle events.
      
      Storage pool API:
      virConnectStoragePoolEventRegisterAny
      virConnectStoragePoolEventDeregisterAny
      virStoragePoolEventLifecycleType which has events STARTED, STOPPED, DEFINED,
      UNDEFINED, and REFRESHED
      1328f982
    • M
      qemu: Remove useless block in processWatchdogEvent · bce3d20d
      Martin Kletzander 提交于
      Best viewed with -w since this is mostly just an indentation patch.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      bce3d20d
    • M
      qemu: Follow coding style convention · 0aaeff96
      Martin Kletzander 提交于
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      0aaeff96
    • M
      qemu: Unify automatic coredump filenames · 5e125782
      Martin Kletzander 提交于
      Just create a helper for it and use it.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      5e125782
  2. 16 6月, 2016 7 次提交
  3. 15 6月, 2016 7 次提交
  4. 14 6月, 2016 10 次提交