1. 23 3月, 2016 8 次提交
    • M
      qemuxml2argv: Mock virSCSIDeviceGetSgName · 4b527c1a
      Michal Privoznik 提交于
      When constructing SCSI hostdev command line for qemu, the
      /sys/bus/scsi/devices/... dir is scanned. Unfortunately, even in
      the tests. This is needed to determine the name of SCSI device to
      passthrough to qemu, because in the domain XML we were given its
      address instead. Anyway, we should not be touching live system
      data in our test suite as it produced unpredictable results. The
      test is regressing from 1e9a0837 on.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      4b527c1a
    • V
      autocreate tap device for ethernet network type · 9c17d665
      Vasiliy Tolstov 提交于
      If a user specify network type ethernet, then create it via libvirt and run
      script if it provided. After this commit user does not need to
      run external script to create tap device or add root permissions to qemu
      process.
      Signed-off-by: NVasiliy Tolstov <v.tolstov@selfip.ru>
      9c17d665
    • A
      tests: hostdev: Add more tests · ee07c980
      Andrea Bolognani 提交于
      Ensure the code behaves properly even for situations that were not
      being considered before, such as simply detaching devices from the
      host without attaching them to a guest and attaching devices as
      managed even though they had already been manually detached from
      the host.
      ee07c980
    • A
      hostdev: Use actual device when reattaching · ee4cfb56
      Andrea Bolognani 提交于
      Instead of forcing the values for the unbind_from_stub, remove_slot
      and reprobe properties, look up the actual device and use that when
      calling virPCIDeviceReattach().
      
      This ensures the device is restored to its original state after
      reattach: for example, if it was not bound to any driver before
      detach, it will not be bound forcefully during reattach.
      ee4cfb56
    • A
      hostdev: Save netdev configuration of actual device · c3e2f6e3
      Andrea Bolognani 提交于
      We would be just fine looking up the information in pcidevs most
      of the time; however, some corner cases would not be handled
      properly, so look up the actual device instead.
      c3e2f6e3
    • A
      hostdev: Streamline device ownership tracking · 81128609
      Andrea Bolognani 提交于
      After this patch, ownership of virPCIDevice instances is very easy
      to keep track of: for each host PCI device, the only instance that
      actually matters is the one inside one of the bookkeeping list.
      
      Whenever some operation needs to be performed on a PCI device, the
      actual device is looked up first; when this is not the case, a
      comment explains the reason.
      81128609
    • A
      hostdev: Stop early if unmanaged devices have not been detached · 6da6bf2f
      Andrea Bolognani 提交于
      Unmanaged devices, as the name suggests, are not detached
      automatically from the host by libvirt before being attached to a
      guest: it's the user's responsability to detach them manually
      beforehand. If that preliminary step has not been performed, the
      attach operation can't complete successfully.
      
      Instead of relying on the lower layers to error out with cryptic
      messages such as
      
        error: Failed to attach device from /tmp/hostdev.xml
        error: Path '/dev/vfio/12' is not accessible: No such file or directory
      
      prevent the situation altogether and provide the user with a more
      useful error message.
      6da6bf2f
    • A
      hostdev: Detect untracked inactive devices · df490e7c
      Andrea Bolognani 提交于
      Unmanaged devices are attached to guests in two steps: first,
      the device is detached from the host and marked as inactive;
      subsequently, it is marked as active and attached to the guest.
      
      If the daemon is restarted between these two operations, we lose
      track of the inactive device.
      
      Steps 5 and 6 of virHostdevPreparePCIDevices() already subtly
      take care of this situation, but some planned changes will make
      it so that's no longer the case. Plus, explicit is always better
      than implicit.
      df490e7c
  2. 22 3月, 2016 17 次提交
  3. 21 3月, 2016 15 次提交