1. 07 4月, 2012 1 次提交
  2. 30 3月, 2012 2 次提交
    • A
      qtest: add test framework · c7f0f3b1
      Anthony Liguori 提交于
      The idea behind qtest is pretty simple.  Instead of executing a CPU via TCG or
      KVM, rely on an external process to send events to the device model that the CPU
      would normally generate.
      
      qtest presents itself as an accelerator.  In addition, a new option is added to
      establish a qtest server (-qtest) that takes a character device.  This is what
      allows the external process to send CPU events to the device model.
      
      qtest uses a simple line based protocol to send the events.  Documentation of
      that protocol is in qtest.c.
      
      I considered reusing the monitor for this job.  Adding interrupts would be a bit
      difficult.  In addition, logging would also be difficult.
      
      qtest has extensive logging support.  All protocol commands are logged with
      time stamps using a new command line option (-qtest-log).  Logging is important
      since ultimately, this is a feature for debugging.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c7f0f3b1
    • P
      rtc: add -rtc clock=rt · 78808141
      Paolo Bonzini 提交于
      This will let people use backwards-compatible semantics for devices that
      will be affected by the following patches.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      78808141
  3. 27 3月, 2012 1 次提交
  4. 06 3月, 2012 1 次提交
  5. 02 3月, 2012 1 次提交
  6. 10 2月, 2012 1 次提交
    • G
      vnc: implement shared flag handling. · 8cf36489
      Gerd Hoffmann 提交于
      VNC clients send a shared flag in the client init message.  Up to now
      qemu completely ignores this.  This patch implements shared flag
      handling.  It comes with three policies:  By default qemu behaves as one
      would expect:  Asking for a exclusive access grants exclusive access to
      the client connecting.  There is also a desktop sharing mode which
      disallows exclusive connects (so one forgetting -shared wouldn't drop
      everybody else) and a compatibility mode which mimics the traditional
      (but non-conforming) qemu behavior.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      8cf36489
  7. 09 2月, 2012 2 次提交
    • R
      iSCSI: add configuration variables for iSCSI · f9dadc98
      Ronnie Sahlberg 提交于
      This patch adds configuration variables for iSCSI to set
      initiator-name to use when logging in to the target,
      which type of header-digest to negotiate with the target
      and username and password for CHAP authentication.
      
      This allows specifying a initiator-name either from the command line
      -iscsi initiator-name=iqn.2004-01.com.example:test
      or from a configuration file included with -readconfig
          [iscsi]
            initiator-name = iqn.2004-01.com.example:test
            header-digest = CRC32C|CRC32C-NONE|NONE-CRC32C|NONE
            user = CHAP username
            password = CHAP password
      
      If you use several different targets, you can also configure this on a per
      target basis by using a group name:
          [iscsi "iqn.target.name"]
          ...
      
      The configuration file can be read using -readconfig.
      Example :
      qemu-system-i386 -drive file=iscsi://127.0.0.1/iqn.ronnie.test/1
       -readconfig iscsi.conf
      Signed-off-by: NRonnie Sahlberg <ronniesahlberg@gmail.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      f9dadc98
    • J
      kvm: Allow to set shadow MMU size · 39d6960a
      Jan Kiszka 提交于
      Introduce the KVM-specific machine option kvm_shadow_mem. It allows to
      set a custom shadow MMU size for the virtual machine. This is useful for
      stress testing e.g.
      
      Only x86 supports this for now, but it is in principle a generic
      concept for all targets with shadow MMUs.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NMarcelo Tosatti <mtosatti@redhat.com>
      39d6960a
  8. 02 2月, 2012 1 次提交
    • C
      Add support for net bridge · a7c36ee4
      Corey Bryant 提交于
      The most common use of -net tap is to connect a tap device to a bridge.  This
      requires the use of a script and running qemu as root in order to allocate a
      tap device to pass to the script.
      
      This model is great for portability and flexibility but it's incredibly
      difficult to eliminate the need to run qemu as root.  The only really viable
      mechanism is to use tunctl to create a tap device, attach it to a bridge as
      root, and then hand that tap device to qemu.  The problem with this mechanism
      is that it requires administrator intervention whenever a user wants to create
      a guest.
      
      By essentially writing a helper that implements the most common qemu-ifup
      script that can be safely given cap_net_admin, we can dramatically simplify
      things for non-privileged users.  We still support existing -net tap options
      as a mechanism for advanced users and backwards compatibility.
      
      Currently, this is very Linux centric but there's really no reason why it
      couldn't be extended for other Unixes.
      
      A typical invocation would be similar to one of the following:
      
        qemu linux.img -net bridge -net nic,model=virtio
      
        qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
                       -net nic,model=virtio
      
        qemu linux.img -netdev bridge,id=hn0
                       -device virtio-net-pci,netdev=hn0,id=nic1
      
        qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
                       -device virtio-net-pci,netdev=hn0,id=nic1
      
      The default bridge that we attach to is br0.  The thinking is that a distro
      could preconfigure such an interface to allow out-of-the-box bridged networking.
      
      Alternatively, if a user wants to use a different bridge, a typical invocation
      would be simliar to one of the following:
      
        qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
      
        qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
                       -net nic,model=virtio
      
        qemu linux.img -netdev bridge,br=qemubr0,id=hn0
                       -device virtio-net-pci,netdev=hn0,id=nic1
      
        qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
                       -device virtio-net-pci,netdev=hn0,id=nic1
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NRicha Marwaha <rmarwah@linux.vnet.ibm.com>
      Signed-off-by: NCorey Bryant <coreyb@linux.vnet.ibm.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      a7c36ee4
  9. 19 1月, 2012 2 次提交
  10. 13 1月, 2012 1 次提交
  11. 06 1月, 2012 1 次提交
  12. 04 1月, 2012 2 次提交
  13. 20 12月, 2011 2 次提交
  14. 14 12月, 2011 1 次提交
  15. 05 12月, 2011 2 次提交
  16. 31 10月, 2011 2 次提交
  17. 29 10月, 2011 3 次提交
  18. 15 10月, 2011 2 次提交
  19. 14 10月, 2011 1 次提交
  20. 12 10月, 2011 1 次提交
  21. 11 9月, 2011 1 次提交
  22. 09 9月, 2011 1 次提交
  23. 04 9月, 2011 1 次提交
  24. 01 9月, 2011 4 次提交
  25. 23 8月, 2011 1 次提交
    • S
      block: add cache=directsync parameter to -drive · 92196b2f
      Stefan Hajnoczi 提交于
      This patch adds -drive cache=directsync for O_DIRECT | O_SYNC host file
      I/O with no disk write cache presented to the guest.
      
      This mode is useful when guests may not be sending flushes when
      appropriate and therefore leave data at risk in case of power failure.
      When cache=directsync is used, write operations are only completed to
      the guest when data is safely on disk.
      
      This new mode is like cache=writethrough but it bypasses the host page
      cache.
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      92196b2f
  26. 30 7月, 2011 1 次提交
    • M
      revamp acpitable parsing and allow to specify complete (headerful) table · 104bf02e
      Michael Tokarev 提交于
      This patch almost rewrites acpi_table_add() function
      (but still leaves it using old get_param_value() interface).
      The result is that it's now possible to specify whole table
      (together with a header) in an external file, instead of just
      data portion, with a new file= parameter, but at the same time
      it's still possible to specify header fields as before.
      
      Now with the checkpatch.pl formatting fixes, thanks to
      Stefan Hajnoczi for suggestions, with changes from
      Isaku Yamahata, and with my further refinements.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      Cc: Isaku Yamahata <yamahata@valinux.co.jp>
      Cc: John Baboval <john.baboval@virtualcomputer.com>
      Cc: Blue Swirl <blauwirbel@gmail.com>
      [yamahata@valinux.co.jp: fix compile error, comment fallthrough]
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      104bf02e
  27. 29 7月, 2011 1 次提交
    • W
      showing a splash picture when start · 3d3b8303
      wayne 提交于
          Added options to let qemu transfer two configuration files to bios:
      "bootsplash.bmp" and "etc/boot-menu-wait", which could be specified by command
          -boot splash=P,splash-time=T
      P is jpg/bmp file name or an absolute path, T have a max value of 0xffff, unit
      is ms. With these two options, if user invoke qemu with menu=on option, then
      a splash picture would be showed in a given time. For example:
          qemu -boot menu=on,splash=/root/boot.bmp,splash-time=5000
      would make boot.bmp shown as a brand with 5 seconds in the booting up process.
      This feature need the new seabios's support, which could be got from git.
      Signed-off-by: NWayne Xia <xiawenc@linux.vnet.ibm.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3d3b8303