1. 18 2月, 2013 4 次提交
  2. 14 2月, 2013 1 次提交
  3. 07 2月, 2013 1 次提交
    • M
      qemu-char: Saner naming of memchar stuff & doc fixes · 3949e594
      Markus Armbruster 提交于
      New device, has never been released, so we can still improve things
      without worrying about compatibility.
      
      Naming is a mess.  The code calls the device driver CirMemCharDriver,
      the public API calls it "memory", "memchardev", or "memchar", and the
      special commands are named like "memchar-FOO".  "memory" is a
      particularly unfortunate choice, because there's another character
      device driver called MemoryDriver.  Moreover, the device's distinctive
      property is that it's a ring buffer, not that's in memory.  Therefore:
      
      * Rename CirMemCharDriver to RingBufCharDriver, and call the thing a
        "ringbuf" in the API.
      
      * Rename QMP and HMP commands from memchar-FOO to ringbuf-FOO.
      
      * Rename device parameter from maxcapacity to size (simple words are
        good for you).
      
      * Clearly mark the parameter as optional in documentation.
      
      * Fix error reporting so that chardev-add reports to current monitor,
        not stderr.
      
      * Replace cirmem in C identifiers by ringbuf.
      
      * Rework documentation.  Document the impact of our crappy UTF-8
        handling on reading.
      
      * QMP examples that even work.
      
      I could split this up into multiple commits, but they'd change the
      same documentation lines multiple times.  Not worth it.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3949e594
  4. 25 1月, 2013 1 次提交
  5. 22 1月, 2013 1 次提交
    • T
      vnc: added initial websocket protocol support · 7536ee4b
      Tim Hardeck 提交于
      This patch adds basic Websocket Protocol version 13 - RFC 6455 - support
      to QEMU VNC. Binary encoding support on the client side is mandatory.
      
      Because of the GnuTLS requirement the Websockets implementation is
      optional (--enable-vnc-ws).
      
      To activate Websocket support the VNC option "websocket"is used, for
      example "-vnc :0,websocket".
      The listen port for Websocket connections is (5700 + display) so if
      QEMU VNC is started with :0 the Websocket port would be 5700.
      As an alternative the Websocket port could be manually specified by
      using ",websocket=<port>" instead.
      
      Parts of the implementation base on Anthony Liguori's QEMU Websocket
      patch from 2010 and on Joel Martin's LibVNC Websocket implementation.
      Signed-off-by: NTim Hardeck <thardeck@suse.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      7536ee4b
  6. 16 1月, 2013 2 次提交
  7. 17 12月, 2012 1 次提交
    • M
      spice-qemu-char: add spiceport chardev · 5a49d3e9
      Marc-André Lureau 提交于
      Add a new spice chardev to allow arbitrary communication between the
      host and the Spice client via the spice server.
      
      Examples:
      
      This allows the Spice client to have a special port for the qemu
      monitor:
      
      ... -chardev spiceport,name=org.qemu.monitor,id=monitorport
          -mon chardev=monitorport
      
      v2:
      - remove support for chardev to chardev linking
      - conditionnaly compile with SPICE_SERVER_VERSION
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      5a49d3e9
  8. 07 12月, 2012 1 次提交
  9. 30 11月, 2012 1 次提交
  10. 23 11月, 2012 1 次提交
  11. 16 11月, 2012 1 次提交
  12. 15 11月, 2012 2 次提交
  13. 31 10月, 2012 5 次提交
  14. 24 10月, 2012 1 次提交
    • C
      qemu-config: Add new -add-fd command line option · 587ed6be
      Corey Bryant 提交于
      This option can be used for passing file descriptors on the
      command line.  It mirrors the existing add-fd QMP command which
      allows an fd to be passed to QEMU via SCM_RIGHTS and added to an
      fd set.
      
      This can be combined with commands such as -drive to link file
      descriptors in an fd set to a drive:
      
          qemu-kvm -add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
                   -add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
                   -drive file=/dev/fdset/2,index=0,media=disk
      
      This example adds dups of fds 3 and 4, and the accompanying opaque
      strings to the fd set with ID=2.  qemu_open() already knows how
      to handle a filename of this format.  qemu_open() searches the
      corresponding fd set for an fd and when it finds a match, QEMU
      goes on to use a dup of that fd just like it would have used an
      fd that it opened itself.
      Signed-off-by: NCorey Bryant <coreyb@linux.vnet.ibm.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      587ed6be
  15. 20 10月, 2012 1 次提交
  16. 26 9月, 2012 1 次提交
    • A
      add a boot parameter to set reboot timeout · ac05f349
      Amos Kong 提交于
      Added an option to let qemu transfer a configuration file to bios,
      "etc/boot-fail-wait", which could be specified by command
          -boot reboot-timeout=T
      T have a max value of 0xffff, unit is ms.
      
      With this option, guest will wait for a given time if not find
      bootabled device, then reboot. If reboot-timeout is '-1', guest
      will not reboot, qemu passes '-1' to bios by default.
      
      This feature need the new seabios's support.
      
      Seabios pulls the value from the fwcfg "file" interface, this
      interface is used because SeaBIOS needs a reliable way of
      obtaining a name, value size, and value. It in no way requires
      that there be a real file on the user's host machine.
      Signed-off-by: NAmos Kong <akong@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      ac05f349
  17. 17 9月, 2012 1 次提交
  18. 14 9月, 2012 1 次提交
  19. 05 9月, 2012 2 次提交
  20. 27 8月, 2012 3 次提交
  21. 24 8月, 2012 3 次提交
  22. 17 8月, 2012 2 次提交
  23. 09 8月, 2012 1 次提交
    • R
      iscsi: Pick default initiator-name based on the name of the VM · 31459f46
      Ronnie Sahlberg 提交于
      This patch updates the iscsi layer to automatically pick a 'unique'
      initiator-name based on the name of the vm in case the user has not set
      an explicit iqn-name to use.
      
      Create a new function qemu_get_vm_name() that returns the name of the VM,
      if specified.
      
      This way we can thus create default names to use as the initiator name
      based on the guest session.
      
      If the VM is not named via the '-name' command line argument, the iscsi
      initiator-name used wiull simply be
      
          iqn.2008-11.org.linux-kvm
      
      If a name for the VM was specified with the '-name' option, iscsi will
      use a default initiatorname of
      
          iqn.2008-11.org.linux-kvm:<name>
      
      These names are just the default iscsi initiator name that qemu will
      generate/use only when the user has not set an explicit initiator name
      via the commandlines or config files.
      Signed-off-by: NRonnie Sahlberg <ronniesahlberg@gmail.com>
      31459f46
  24. 04 8月, 2012 1 次提交
    • P
      vnc: disable VNC password authentication (security type 2) when in FIPS mode · 0f66998f
      Paul Moore 提交于
      FIPS 140-2 requires disabling certain ciphers, including DES, which is used
      by VNC to obscure passwords when they are sent over the network.  The
      solution for FIPS users is to disable the use of VNC password auth when the
      host system is operating in FIPS compliance mode and the user has specified
      '-enable-fips' on the QEMU command line.
      
      This patch causes QEMU to emit a message to stderr when the host system is
      running in FIPS mode and a VNC password was specified on the commend line.
      If the system is not running in FIPS mode, or is running in FIPS mode but
      VNC password authentication was not requested, QEMU operates normally.
      Signed-off-by: NPaul Moore <pmoore@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      0f66998f
  25. 03 8月, 2012 1 次提交
    • P
      Support 'help' as a synonym for '?' in command line options · c8057f95
      Peter Maydell 提交于
      For command line options which permit '?' meaning 'please list the
      permitted values', add support for 'help' as a synonym, by abstracting
      the check out into a helper function.
      
      This change means that in some cases where we were being lazy in
      our string parsing, "?junk" will now be rejected as an invalid option
      rather than being (undocumentedly) treated the same way as "?".
      
      Update the documentation to use 'help' rather than '?', since '?'
      is a shell metacharacter and thus prone to fail confusingly if there
      is a single character filename in the current working directory and
      the '?' has not been escaped. It's therefore better to steer users
      towards 'help', though '?' is retained for backwards compatibility.
      
      We do not, however, update the output of the system emulator's -help
      (or any documentation autogenerated from the qemu-options.hx which
      is the source of the -help text) because libvirt parses our -help
      output and will break. At a later date when QEMU provides a better
      interface so libvirt can avoid having to do this, we can update the
      -help text too.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c8057f95