1. 23 10月, 2014 4 次提交
  2. 21 10月, 2014 1 次提交
  3. 08 9月, 2014 1 次提交
  4. 03 9月, 2014 1 次提交
  5. 01 9月, 2014 1 次提交
  6. 29 8月, 2014 1 次提交
  7. 15 8月, 2014 1 次提交
    • C
      block: Support Archipelago as a QEMU block backend · c9a12e75
      Chrysostomos Nanakos 提交于
      VM Image on Archipelago volume is specified like this:
      
      file.driver=archipelago,file.volume=<volumename>[,file.mport=<mapperd_port>[,
      file.vport=<vlmcd_port>][,file.segment=<segment_name>]]
      
      'archipelago' is the protocol.
      
      'mport' is the port number on which mapperd is listening. This is optional
      and if not specified, QEMU will make Archipelago to use the default port.
      
      'vport' is the port number on which vlmcd is listening. This is optional
      and if not specified, QEMU will make Archipelago to use the default port.
      
      'segment' is the name of the shared memory segment Archipelago stack is using.
      This is optional and if not specified, QEMU will make Archipelago to use the
      default value, 'archipelago'.
      
      Examples:
      
      file.driver=archipelago,file.volume=my_vm_volume
      file.driver=archipelago,file.volume=my_vm_volume,file.mport=123
      file.driver=archipelago,file.volume=my_vm_volume,file.mport=123,
      file.vport=1234
      file.driver=archipelago,file.volume=my_vm_volume,file.mport=123,
      file.vport=1234,file.segment=my_segment
      Signed-off-by: NChrysostomos Nanakos <cnanakos@grnet.gr>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      c9a12e75
  8. 07 7月, 2014 1 次提交
  9. 03 7月, 2014 1 次提交
  10. 18 6月, 2014 1 次提交
  11. 17 6月, 2014 1 次提交
  12. 28 5月, 2014 1 次提交
  13. 08 5月, 2014 1 次提交
    • M
      MAINTAINERS: addresses for responsible disclosure · 62622c11
      Michael S. Tsirkin 提交于
      Adding addresses to MAINTAINERS, as agreed on the last conference call:
      
      http://wiki.qemu.org/SecurityProcess
      
      People sometimes detect security issues in upstream
      QEMU and don't know where to report them in a non-public way.
      Of course whoever just wants full disclosure can just go public,
      but there's nothing specified for non-public - until recently Anthony
      was doing this informally.
      
      As I started doing this recently anyway, I can handle this on the QEMU side
      in a more formal way.
      
      Adding a secalert mailing list as well - they are the ones who is actually
      opening CVEs, communicating issues to all downstreams etc,
      and they are already handling this for upstream, not just Red Hat.
      
      Keeping Anthony's address around in case he wants to be informed.
      
      Peter Maydell said that he prefers not to be on this contact list at
      this point.
      
      A public mailing list has been created - not listing it here yet -
      until we know how to set it up in a secure fashion and
      until there are more people so manually copying everyone
      becomes unwieldy for reporters.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      62622c11
  14. 06 5月, 2014 5 次提交
  15. 28 4月, 2014 1 次提交
  16. 26 4月, 2014 1 次提交
  17. 07 4月, 2014 1 次提交
    • G
      ui: Update MAINTAINERS entry. · 25eccc37
      Gerd Hoffmann 提交于
      With Amazon eating Anthonys time status "Maintained" certainly isn't
      true any more.  Update entry accordingly.
      
      Also add myself, so scripts/get_maintainer.pl will Cc: me, to reduce
      the chance ui patches fall through the cracks on our pretty loaded
      qemu-devel mailing list.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      25eccc37
  18. 03 4月, 2014 1 次提交
  19. 01 4月, 2014 2 次提交
  20. 11 3月, 2014 1 次提交
  21. 10 3月, 2014 1 次提交
  22. 01 3月, 2014 1 次提交
  23. 09 2月, 2014 1 次提交
    • P
      block: add native support for NFS · 6542aa9c
      Peter Lieven 提交于
      This patch adds native support for accessing images on NFS
      shares without the requirement to actually mount the entire
      NFS share on the host.
      
      NFS Images can simply be specified by an url of the form:
      nfs://<host>/<export>/<filename>[?param=value[&param2=value2[&...]]]
      
      For example:
      qemu-img create -f qcow2 nfs://10.0.0.1/qemu-images/test.qcow2
      
      You need LibNFS from Ronnie Sahlberg available at:
         git://github.com/sahlberg/libnfs.git
      for this to work.
      
      During configure it is automatically probed for libnfs and support
      is enabled on-the-fly. You can forbid or enforce libnfs support
      with --disable-libnfs or --enable-libnfs respectively.
      
      Due to NFS restrictions you might need to execute your binaries
      as root, allow them to open priviledged ports (<1024) or specify
      insecure option on the NFS server.
      
      For additional information on ROOT vs. non-ROOT operation and URL
      format + parameters see:
         https://raw.github.com/sahlberg/libnfs/master/README
      
      Supported by qemu are the uid, gid and tcp-syncnt URL parameters.
      
      LibNFS currently support NFS version 3 only.
      Signed-off-by: NPeter Lieven <pl@kamp.de>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      6542aa9c
  24. 26 1月, 2014 1 次提交
  25. 13 1月, 2014 1 次提交
  26. 18 12月, 2013 2 次提交
  27. 10 12月, 2013 1 次提交
  28. 09 12月, 2013 1 次提交
  29. 29 11月, 2013 1 次提交
  30. 15 11月, 2013 1 次提交
  31. 14 11月, 2013 1 次提交