1. 12 6月, 2018 1 次提交
  2. 08 6月, 2018 1 次提交
    • M
      conf, schema, docs: Add support for TSEG size setting · 1bd5a08d
      Martin Kletzander 提交于
      TSEG (Top of Memory Segment) is one of many regions that SMM (System Management
      Mode) can occupy.  This one, however is special, because a) most of the SMM code
      lives in TSEG nowadays and b) QEMU just (well, some time ago) added support for
      so called 'extended' TSEG.  The difference to the TSEG implemented in real q35's
      MCH (Memory Controller Hub) is that it can offer one extra size to the guest OS
      apart from the standard TSEG's 1, 2, and 8 MiB and that size can be selected in
      1 MiB increments.  Maximum may vary based on QEMU and is way too big, so we
      don't need to check for the maximum here.  Similarly to the memory size we'll
      leave it to the hypervisor to try satisfying that and giving us an error message
      in case it is not possible.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      Acked-by: NLaszlo Ersek <lersek@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      1bd5a08d
  3. 07 6月, 2018 1 次提交
  4. 06 6月, 2018 2 次提交
  5. 05 6月, 2018 2 次提交
  6. 01 6月, 2018 1 次提交
  7. 29 5月, 2018 1 次提交
  8. 25 5月, 2018 10 次提交
  9. 23 5月, 2018 1 次提交
  10. 16 5月, 2018 2 次提交
  11. 15 5月, 2018 1 次提交
  12. 14 5月, 2018 1 次提交
  13. 11 5月, 2018 1 次提交
  14. 04 5月, 2018 3 次提交
  15. 03 5月, 2018 1 次提交
  16. 02 5月, 2018 1 次提交
  17. 23 4月, 2018 1 次提交
    • A
      conf: Add rom.enabled attribute for PCI devices · c4466179
      Andrea Bolognani 提交于
      The attribute can be used to disable ROM loading completely
      for a device.
      
      This might be needed because, even when the guest is configured
      such that the PCI ROM will not be loaded in the PCI BAR, some
      hypervisors (eg. QEMU) might still make it available to the
      guest in a form (eg. fw_cfg) that some firmwares (eg. SeaBIOS)
      will consume, thus not achieving the desired result.
      Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
      c4466179
  18. 06 4月, 2018 1 次提交
  19. 01 4月, 2018 1 次提交
  20. 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
  21. 26 1月, 2018 2 次提交
  22. 25 1月, 2018 1 次提交
  23. 07 12月, 2017 1 次提交
  24. 30 11月, 2017 2 次提交