1. 20 9月, 2018 2 次提交
  2. 19 9月, 2018 1 次提交
    • J
      qemu: Fix error reporting in qemuDomainSaveImageStartVM · 1468536d
      Jiri Denemark 提交于
      When restoring a domain from a compressed image, we launch an
      intermediate process for decompressing the saved data. If QEMU fails to
      load the data for some reason, we force close the stdin/stdout file
      descriptors of the intermediate process and wait for it to die. However,
      virCommandWait can report various errors which would overwrite the real
      error from QEMU. Thus instead of getting something useful:
      
          internal error: process exited while connecting to monitor:
          2018-09-17T15:17:29.998910Z qemu-system-x86_64: can't apply global
          Skylake-Client-x86_64-cpu.osxsave=off: Property '.osxsave' not found
      
      we could get an irrelevant error message:
      
          internal error: Child process (lzop -dc --ignore-warn) unexpected
          fatal signal 13
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      1468536d
  3. 18 9月, 2018 1 次提交
    • M
      security_manager: Load lock plugin on init · 3e26b476
      Michal Privoznik 提交于
      Now that we know what metadata lock manager user wishes to use we
      can load it when initializing security driver. This is achieved
      by adding new argument to virSecurityManagerNewDriver() and
      subsequently to all functions that end up calling it.
      
      The cfg.mk change is needed in order to allow lock_manager.h
      inclusion in security driver without 'syntax-check' complaining.
      This is safe thing to do as locking APIs will always exist (it's
      only backend implementation that changes). However, instead of
      allowing the include for all other drivers (like cpu, network,
      and so on) allow it only for security driver. This will still
      trigger the error if including from other drivers.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      3e26b476
  4. 17 9月, 2018 2 次提交
  5. 06 9月, 2018 1 次提交
  6. 04 9月, 2018 1 次提交
  7. 28 8月, 2018 1 次提交
  8. 23 8月, 2018 1 次提交
  9. 21 8月, 2018 22 次提交
  10. 13 8月, 2018 1 次提交
  11. 30 7月, 2018 1 次提交
  12. 27 7月, 2018 1 次提交
  13. 25 7月, 2018 2 次提交
    • J
      qemu: Use the correct vm def on cold attach · 55ce6564
      John Ferlan 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=1559867
      
      When attaching a device to the domain we need to be sure
      to use the correct domain definition (vm->def or vm->newDef)
      when calling virDomainDeviceDefParse because the post parse
      processing algorithms that may assign an address for the
      device will use whatever domain definition was passed in.
      
      Additionally, some devices (SCSI hostdev and SCSI disk) use
      algorithms that rely on knowing what already exists of the
      other type when generating the new device's address. Using
      the wrong VM definition could result in duplicated addresses.
      
      In the case of the bz, two hostdev's with no domain address
      provided were added to the running domain's config only.
      However, the parsing algorithm used the live domain in
      order to figure out the host device address resulting in
      the same address being used and a subsequent start failing
      due to duplicate address.
      
      Fix this by separating the checks/code into CONFIG and LIVE
      processing using the correct definition for each block and
      performing cleanup for both options as necessary.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      ACKed-by: NMichal Privoznik <mprivozn@redhat.com>
      55ce6564
    • M
      qemuDomainSaveMemory: Don't enforce dynamicOwnership · 8c8c3233
      Michal Privoznik 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=1589115
      
      When doing a memory snapshot qemuOpenFile() is used. This means
      that the file where memory is saved is firstly attempted to be
      created under root:root (because that's what libvirtd is running
      under) and if this fails the second attempt is done under
      domain's uid:gid. This does not make much sense - qemu is given
      opened FD so it does not need to access the file. Moreover, if
      dynamicOwnership is set in qemu.conf and the file lives on a
      squashed NFS this is deadly combination and very likely to fail.
      
      The fix consists of using:
      
        qemuOpenFileAs(fallback_uid = cfg->user,
                       fallback_gid = cfg->group,
                       dynamicOwnership = false)
      
      In other words, dynamicOwnership is turned off for memory
      snapshot (chown() will still be attempted if the file does not
      live on NFS) and instead of using domain DAC label, configured
      user:group is set as fallback.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      8c8c3233
  14. 20 7月, 2018 3 次提交