1. 20 1月, 2011 1 次提交
  2. 19 1月, 2011 1 次提交
  3. 18 1月, 2011 1 次提交
    • J
      Introduce per-device boot element · 94234fa2
      Jiri Denemark 提交于
      Currently, boot order can be specified per device class but there is no
      way to specify exact disk/NIC device to boot from.
      
      This patch adds <boot order='N'/> element which can be used inside
      <disk/> and <interface/>. This is incompatible with the older os/boot
      element. Since not all hypervisors support per-device boot
      specification, new deviceboot flag is included in capabilities XML for
      hypervisors which understand the new boot element. Presence of the flag
      allows (but doesn't require) users to use the new style boot order
      specification.
      94234fa2
  4. 14 1月, 2011 1 次提交
  5. 13 1月, 2011 1 次提交
  6. 24 12月, 2010 1 次提交
  7. 10 12月, 2010 1 次提交
    • H
      Update documentation of watchdog dump option and add test data for it · e8e9397c
      Hu Tao 提交于
      The xml watchdog dump option is converted to qemu watchdog pause arg
      but it is not reasonable to convert it back from qemu watchdog pause
      arg since there already is a xml watchdog pause option, so a test for
      the dump option to convert it from arg to xml is not added.
      e8e9397c
  8. 09 11月, 2010 4 次提交
    • D
      Support SPICE channel security options · b0ef5c53
      Daniel P. Berrange 提交于
      This extends the SPICE XML to allow channel security options
      
          <graphics type='spice' port='-1' tlsPort='-1' autoport='yes'>
            <channel name='main' mode='secure'/>
            <channel name='record' mode='insecure'/>
          </graphics>
      
      Any non-specified channel uses the default, which allows both
      secure & insecure usage
      
      * src/conf/domain_conf.c, src/conf/domain_conf.h,
        src/libvirt_private.syms: Add XML syntax for specifying per
        channel security options for spice.
      * src/qemu/qemu_conf.c: Configure channel security with spice
      b0ef5c53
    • D
      Define XML syntax for password expiry · 7a696678
      Daniel P. Berrange 提交于
      This extends the XML syntax for <graphics> to allow a password
      expiry time to be set
      
      eg
      
        <graphics type='vnc' port='5900' autoport='yes' keymap='en-us' passwd='12345' passwdValidTo='2010-04-09T15:51:00'/>
      
      The timestamp is in UTC.
      
      * src/conf/domain_conf.h: Pull passwd out into separate struct
        virDomainGraphicsAuthDef to allow sharing between VNC & SPICE
      * src/conf/domain_conf.c: Add parsing/formatting of new passwdValidTo
        argument
      * src/opennebula/one_conf.c, src/qemu/qemu_conf.c, src/qemu/qemu_driver.c,
        src/xen/xend_internal.c, src/xen/xm_internal.c: Update for changed
        struct containing VNC password
      7a696678
    • D
      Add a <graphics> type for SPICE protocol · c909091b
      Daniel P. Berrange 提交于
      This adds an element
      
       <graphics type='spice' port='5903' tlsPort='5904' autoport='yes' listen='127.0.0.1'/>
      
      This is the bare minimum that should be exposed in the guest
      config for SPICE. Other parameters are better handled as per
      host level configuration tunables
      
      * docs/schemas/domain.rng: Define the SPICE <graphics> schema
      * src/domain_conf.h, src/domain_conf.c: Add parsing and formatting
        for SPICE graphics config
      * src/qemu_conf.c: Complain about unsupported graphics types
      c909091b
    • D
      Add a QXL graphics card type to domain XML schema · 3cf5b6f7
      Daniel P. Berrange 提交于
      * src/qemu_conf.c: Add dummy entry in enumeration
      * docs/schemas/domain.rng: Add 'qxl' as a type for the <video> tag
      * src/domain_conf.c, src/domain_conf.h: Add QXL to video type
        enumerations
      3cf5b6f7
  9. 19 10月, 2010 2 次提交
    • E
      vcpu: add current attribute to <vcpu> element · a74f4e44
      Eric Blake 提交于
      Syntax agreed on in
      https://www.redhat.com/archives/libvir-list/2010-September/msg00476.html
      
      <domain ...>
        <vcpu current='x'>y</vcpu>
      ...
      
      can now be used to specify 1 <= x <= y current vcpus, in relation
      to the boot-time max of y vcpus.  If current is omitted, then
      current and max are assumed to be the same value.
      
      * docs/schemas/domain.rng: Add new attribute.
      * docs/formatdomain.html.in: Document it.
      * tests/qemuxml2argvdata/qemuxml2argv-smp.xml: Add to
      domainschematest.
      * tests/xml2sexprdata/xml2sexpr-pv-vcpus.xml: Likewise.
      a74f4e44
    • N
      Update docs for memory parameters and memtune command · 61dfbf8c
      Nikunj A. Dadhania 提交于
      * docs/formatdomain.html.in: Add memtune element details, added min_guarantee
      * src/libvirt.c: Update virDomainGetMemoryParameters api description, make
        it more clear that the user first needs to call the api to get the number
        of parameters supported and then call again to get the values.
      * tools/virsh.pod: Add usage of new command memtune in virsh manpage
      61dfbf8c
  10. 16 10月, 2010 1 次提交
  11. 12 10月, 2010 1 次提交
    • D
      Set sensible defaults for cpu match and feature policy · 95ff6b18
      Daniel P. Berrange 提交于
      To enable the CPU XML from the capabilities to be pasted directly
      into the guest XML with no editing, pick a sensible default for
      match and feature policy. The CPU match will be exact and the
      feature policy will be require. This should ensure safety for
      migration and give DWIM semantics for users
      
      * src/conf/cpu_conf.c: Default to exact match and require policy
      * docs/formatdomain.html.in: Document new defaults
      95ff6b18
  12. 02 10月, 2010 2 次提交
    • M
      esx: Add support for virtual serial device network backing · 02e11b83
      Matthias Bolte 提交于
      Since version 4.1 ESX(i) can expose virtual serial devices over TCP.
      
      Add support in the VMX handling code for this, add test cases to cover
      it and add links to some documentation.
      
      ESX supports two additional protocols: TELNETS and TLS. Add them to
      the list of serial-over-TCP protocols.
      02e11b83
    • E
      vcpu: improve cpuset attribute · 62a50a0b
      Eric Blake 提交于
      The <vcpu cpuset=...> attribute has been available since commit
      e193b5dd, but without documentation or RNG validation.
      
      * docs/schemas/domain.rng (vcpu): Further validate cpuset.
      * docs/formatdomain.html.in: Document it.
      * src/conf/domain_conf.c: Fix typos.
      62a50a0b
  13. 21 8月, 2010 1 次提交
    • J
      Add actions to virDomainLifecycle enum · b9c10268
      Jim Fehlig 提交于
      Xen supports on_crash actions coredump-{destroy,restart}.  libvirt
      cannot parse config returned by xend that contains either of these
      actions
      
      xen52 # xm li -l test | grep on_crash
          (on_crash coredump-restart)
      xen52 # virsh dumpxml test
      error: internal error unknown lifecycle type coredump-restart
      
      This patch adds a new virDomainLifecycleCrash enum and appends
      the new options to existing destroy, restart, preserve, and
      rename-restart options.
      b9c10268
  14. 17 8月, 2010 1 次提交
    • E
      docs: mention domain <clock> improvements · 2ad42978
      Eric Blake 提交于
      Add documentation for features added a while ago.
      
      * docs/formatdomain.html.in (Time keeping): Update documentation
      of <clock> element to match 0.8.0 addition.
      2ad42978
  15. 29 7月, 2010 2 次提交
  16. 28 7月, 2010 1 次提交
    • C
      qemu: Allow setting boot menu on/off · 4f24ca01
      Cole Robinson 提交于
      Add a new element to the <os> block:
      
        <bootmenu enable="yes|no"/>
      
      Which maps to -boot,menu=on|off on the QEMU command line.
      
      I decided to use an explicit 'enable' attribute rather than just make the
      bootmenu element boolean. This allows us to treat lack of a bootmenu element
      as 'use hypervisor default'.
      4f24ca01
  17. 21 7月, 2010 1 次提交
  18. 07 7月, 2010 1 次提交
    • J
      cpu: Add support for CPU vendor · af53714f
      Jiri Denemark 提交于
      By specifying <vendor> element in CPU requirements a guest can be
      restricted to run only on CPUs by a given vendor. Host CPU vendor is
      also specified in capabilities XML.
      
      The vendor is checked when migrating a guest but it's not forced, i.e.,
      guests configured without <vendor> element can be freely migrated.
      af53714f
  19. 27 5月, 2010 1 次提交
  20. 09 4月, 2010 1 次提交
  21. 26 3月, 2010 1 次提交
  22. 05 3月, 2010 1 次提交
  23. 02 3月, 2010 1 次提交
  24. 24 2月, 2010 1 次提交
  25. 23 2月, 2010 1 次提交
  26. 05 2月, 2010 1 次提交
  27. 20 1月, 2010 1 次提交
  28. 12 1月, 2010 1 次提交
  29. 15 12月, 2009 1 次提交
  30. 14 12月, 2009 1 次提交
  31. 20 11月, 2009 1 次提交
  32. 17 11月, 2009 1 次提交
  33. 09 11月, 2009 2 次提交