1. 26 9月, 2014 7 次提交
    • D
      Rename tunable event constants · 0778c0be
      Daniel P. Berrange 提交于
      For the new VIR_DOMAIN_EVENT_ID_TUNABLE event we have a bunch of
      constants added
      
         VIR_DOMAIN_EVENT_CPUTUNE_<blah>
         VIR_DOMAIN_EVENT_BLKDEVIOTUNE_<blah>
      
      This naming convention is bad for two reasons
      
        - There is no common prefix unique for the events to both
          relate them, and distinguish them from other event
          constants
      
        - The values associated with the constants were chosen
          to match the names used with virConnectGetAllDomainStats
          so having EVENT in the constant name is not applicable in
          that respect
      
      This patch proposes renaming the constants to
      
          VIR_DOMAIN_TUNABLE_CPU_<blah>
          VIR_DOMAIN_TUNABLE_BLKDEV_<blah>
      
      ie, given them a common VIR_DOMAIN_TUNABLE prefix.
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      0778c0be
    • M
      lxc_monitor_protocol: Redefine xdr_uint64_t if needed · c99f66ac
      Michal Privoznik 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=993411
      
      On some systems (using libtirpc instead of glibc's
      implementation), xdr_uint64_t exists rather under different name:
      xdr_u_int64_t. This makes compilation fail then:
      
      libvirt_lxc-lxc_monitor_protocol.o: In function `xdr_virLXCMonitorInitEventMsg':
      /usr/local/src/libvirt/libvirt-1.1.1/src/./lxc/lxc_monitor_protocol.c:31: undefined reference to `xdr_uint64_t'
      
      Therefore we rather mirror the d707c866 commit and redefine
      xdr_uint64_t if needed.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      c99f66ac
    • M
      qemuPrepareNVRAM: Save domain after NVRAM path generation · 3a3c3780
      Michal Privoznik 提交于
      On a domain startup, the variable store path is generated if needed.
      The path is intended to be generated only once. However, the updated
      domain definition is not saved into config dir rather than state XML
      only. So later, whenever the domain is destroyed and the daemon is
      restarted, the generated path is forgotten and the file may be left
      behind on virDomainUndefine() call.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      3a3c3780
    • M
      remoteNodeGetFreePages: Don't alloc args.pages.pages_val · f2729283
      Michal Privoznik 提交于
      There's no one to free() it anyway. Instead, we can just pass the
      provided array pointer directly.
      
      ==20039== 48 bytes in 4 blocks are definitely lost in loss record 658 of 787
      ==20039==    at 0x4C2A700: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==20039==    by 0x4EA661F: virAllocN (viralloc.c:191)
      ==20039==    by 0x50386EF: remoteNodeGetFreePages (remote_driver.c:7625)
      ==20039==    by 0x5003504: virNodeGetFreePages (libvirt.c:21379)
      ==20039==    by 0x154625: cmdFreepages (virsh-host.c:374)
      ==20039==    by 0x12F718: vshCommandRun (virsh.c:1935)
      ==20039==    by 0x1339FB: main (virsh.c:3747)
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      f2729283
    • T
      nodeinfo: fix version of nodeAllocPages · efafc9c1
      Tomoki Sekiyama 提交于
      Fix comments about the version in which '.nodeAllocPages' are added.
      Signed-off-by: NTomoki Sekiyama <tomoki.sekiyama@hds.com>
      efafc9c1
    • P
      qemu: Always re-detect backing chain · fe7ef7b1
      Peter Krempa 提交于
      Since 363e9a68 we track backing chain metadata when creating snapshots
      the right way even for the inactive configuration. As we did not yet
      update other code paths that modify the backing chain (blockpull) the
      newDef backing chain gets out of sync.
      
      After stopping of a VM the new definition gets copied to the next start
      one. The new VM then has incorrect backing chain info. This patch
      switches the backing chain detector to always purge the existing backing
      chain and forces re-detection to avoid this issue until we'll have full
      backing chain tracking support.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1144922
      fe7ef7b1
    • P
      f06a6257
  2. 25 9月, 2014 15 次提交
  3. 24 9月, 2014 18 次提交