1. 25 9月, 2018 14 次提交
  2. 24 9月, 2018 24 次提交
  3. 22 9月, 2018 2 次提交
    • W
      qemu: Update hostdevs device lists before connecting qemu monitor · 2f754b26
      Wu Zongyong 提交于
      In a following case:
      
          virsh start $domain
          service libvirtd stop
          <shutdown> the guest from within the $domain
          service libvirtd start
      
      Notice that PCI devices which have been assigned to the $domain will
      still be bound to stub drivers instead rebound to host drivers.
      In that case the call stack is like below:
      
          libvirtd start
              qemuProcessReconnect
                  qemuProcessStop (because $domain was shutdown without
                                   libvirtd event to process that)
                      qemuHostdevReAttachDomainDevices
                          qemuHostdevReAttachPCIDevices
                              virHostdevReAttachPCIDevices
      
      However, because qemuHostdevUpdateActiveDomainDevices was called
      after the qemuConnectMonitor, the setup of the tracking of each
      host device in the $domain on either the activePCIHostdevs list
      or inactivePCIHostdev list will not occur in an orderly manner.
      Therefore, virHostdevReAttachPCIDevices just neglects these host PCI
      devices which are bound to stub drivers and doesn't rebind them to
      host drivers.
      
      This patch fixs that by moving qemuHostdevUpdateActiveDomainDevices before
      qemuConnectMonitor during libvirtd reconnection processing.
      Signed-off-by: NWu Zongyong <cordius.wu@huawei.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      2f754b26
    • W
      qemu: Fix deadlock if create qemuProcessReconnect thread failed · fad65432
      Wang Yechao 提交于
      Use the new qemuDomainRemoveInactiveJobLocked to remove the
      @obj during the virDomainObjListForEach call which holds a
      lock on the domain object list.
      Signed-off-by: NWang Yechao <wang.yechao255@zte.com.cn>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      fad65432