1. 10 4月, 2018 1 次提交
  2. 06 4月, 2018 1 次提交
    • J
      util: introduce virSocketAddrParseAny · 412afdb8
      Jim Fehlig 提交于
      When preparing for migration, the libxl driver creates a new TCP listen
      socket for the incoming migration by calling virNetSocketNewListenTCP,
      passing the destination host name. virNetSocketNewListenTCP calls
      virSocketAddrParse to check if the host name is a wildcard address, in
      which case it avoids adding the AI_ADDRCONFIG flag to the hints passed to
      getaddrinfo. If the host name is not an IP address, virSocketAddrParse
      reports an error
      
      error : virSocketAddrParseInternal:121 : Cannot parse socket address
      'myhost.example.com': Name or service not known
      
      But virNetSocketNewListenTCP succeeds regardless and the overall migration
      operation succeeds.
      
      Introduce virSocketAddrParseAny and use it when simply testing if a host
      name/addr is parsable.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      412afdb8
  3. 05 4月, 2018 1 次提交
  4. 03 4月, 2018 3 次提交
  5. 23 3月, 2018 1 次提交
  6. 15 3月, 2018 2 次提交
  7. 14 3月, 2018 1 次提交
  8. 07 3月, 2018 1 次提交
  9. 22 2月, 2018 1 次提交
  10. 19 2月, 2018 1 次提交
    • D
      driver: allow override of connection for secondary drivers · 70854ea3
      Daniel P. Berrangé 提交于
      When the test suite is running, we don't want to be triggering the
      startup of daemons for the secondary drivers. Thus we must provide a way
      to set a custom connection for the secondary drivers, to override the
      default logic which opens a new connection.
      
      This will also be useful for code where we have a whole set of separate
      functions calls all needing the secret driver. Currently the connection
      to the secret driver is opened & closed many times in quick
      succession. This will allow us to pre-open a connection temporarily,
      improving the performance of startup.
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      70854ea3
  11. 17 2月, 2018 1 次提交
    • Z
      conf: Add support for setting Chassis SMBIOS data fields · c8fec256
      Zhuang Yanying 提交于
      This type of information defines attributes of a system
      chassis, such as SMBIOS Chassis Asset Tag.
      
      access inside VM (for example)
      Linux:   /sys/class/dmi/id/chassis_asset_tag.
      Windows: (Get-WmiObject Win32_SystemEnclosure).SMBIOSAssetTag
                wirhin Windows PowerShell.
      
      As an example, add the following to the guest XML
      
          <chassis>
            <entry name='manufacturer'>Dell Inc.</entry>
            <entry name='version'>2.12</entry>
            <entry name='serial'>65X0XF2</entry>
            <entry name='asset'>40000101</entry>
            <entry name='sku'>Type3Sku1</entry>
          </chassis>
      Signed-off-by: NZhuang Yanying <ann.zhuangyanying@huawei.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      c8fec256
  12. 13 2月, 2018 1 次提交
  13. 09 2月, 2018 6 次提交
  14. 01 2月, 2018 3 次提交
  15. 31 1月, 2018 2 次提交
  16. 29 1月, 2018 7 次提交
  17. 26 1月, 2018 3 次提交
  18. 12 1月, 2018 1 次提交
  19. 04 1月, 2018 2 次提交
  20. 03 1月, 2018 1 次提交