Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 11 11月, 2014 2 次提交
  3. 03 11月, 2014 1 次提交
  5. 24 10月, 2014 2 次提交
  7. 23 10月, 2014 10 次提交
  9. 21 10月, 2014 1 次提交
  11. 08 9月, 2014 1 次提交
  13. 03 9月, 2014 1 次提交
  15. 01 9月, 2014 1 次提交
  17. 29 8月, 2014 1 次提交
  19. 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
  21. 07 7月, 2014 1 次提交
  23. 03 7月, 2014 1 次提交
  25. 18 6月, 2014 1 次提交
  27. 17 6月, 2014 1 次提交
  29. 28 5月, 2014 1 次提交
  31. 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
  33. 06 5月, 2014 5 次提交
  35. 28 4月, 2014 1 次提交
  37. 26 4月, 2014 1 次提交
  39. 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
  41. 03 4月, 2014 1 次提交
  43. 01 4月, 2014 2 次提交
  45. 11 3月, 2014 1 次提交
  47. 10 3月, 2014 1 次提交