1. 15 11月, 2019 4 次提交
    • J
      qemu: Set capabilities properly for tests · b9647356
      Jonathon Jongsma 提交于
      Several tests were not specifying the necessary qemu capabilities for
      what they were testing. Due to the way that the video devices are
      currently validated, this is not causing any problems. But a change to
      video device validation in a following patch would have exposed this
      issue and resulted in multiple test failures about the domain
      configuration not supporting particular video models.
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      b9647356
    • J
      qemu: use g_autoptr in qemuDomainDeviceDefValidate() · c69e6ede
      Jonathon Jongsma 提交于
      This allows us to simplify the function and avoid jumping to 'cleanup'.
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      c69e6ede
    • J
      qemu: fix domain device validation · ed831437
      Jonathon Jongsma 提交于
      When the virDomainCapsDeviceDefValidate() function returned an error
      status (-1), we were aborting the function early, but returning the
      default return value (0). This patch properly returns an error in that
      case.
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      ed831437
    • J
      libxl: Fix lock manager lock ordering · 2552752f
      Jim Fehlig 提交于
      The ordering of lock manager locks in the libxl driver has a flaw that was
      uncovered by a migration error path. In the perform phase of migration, the
      source host calls virDomainLockProcessPause to release the lock before
      sending the VM to the destination host. If the send fails an attempt is made
      to reacquire the lock with virDomainLockProcessResume, but that too can fail
      if the destination host has not finished cleaning up the failed VM and
      releasing the lock it acquired when starting to receive the VM.
      
      This change delays calling virDomainLockProcessResume in libxlDomainStart
      until the VM is successfully created, but before it is unpaused. A similar
      approach is used by the qemu driver, avoiding the need to release the lock
      if VM creation fails. In the migration perform phase, releasing the lock
      with virDomainLockProcessPause is delayed until the VM is successfully
      sent to the destination, which avoids reacquiring the lock if the send
      fails.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      2552752f
  2. 14 11月, 2019 36 次提交