Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 03 6月, 2015 1 次提交
  3. 01 6月, 2015 1 次提交
  5. 29 5月, 2015 1 次提交
  7. 27 5月, 2015 1 次提交
    • T
      net: Change help text to list -netdev instead of -net by default · 6a8b4a5b
      由 Thomas Huth 提交于 
      Looking at the output of "qemu-system-xxx -help", you easily get
the impression that "-net" is the preferred way instead of "-netdev"
to specify host network interface, since the "-net" option is
omnipresent but the "-netdev" option is only listed as a one-liner
at the end. This is ugly since "-net" is considered as legacy and
even might be removed one day. Thus, this patch switches the output
to explain the host network interfaces with the "-netdev" option
instead, moving the old "-net" option into some few lines at
the end.
Signed-off-by: NThomas Huth <thuth@redhat.com>
Message-id: 1431701904-12230-1-git-send-email-thuth@redhat.com
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      6a8b4a5b
  9. 30 4月, 2015 1 次提交
  11. 19 3月, 2015 2 次提交
  13. 16 3月, 2015 2 次提交
    • A
      migration: Allow to suppress vmdesc submission · 9850c604
      由 Alexander Graf 提交于 
      We now always send a JSON blob describing the migration file format as part
of the migration stream. However, some tools built around QEMU have proven
to stumble over this.

This patch gives the user the chance to disable said self-describing part of
the migration stream. To disable vmdesc submission, just add

  -machine suppress-vmdesc=on

to your QEMU command line.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Signed-off-by: NJuan Quintela <quintela@redhat.com>
      9850c604
    • T
      s390x: CPACF: Handle key wrap machine options · 2eb1cd07
      由 Tony Krowiak 提交于 
      Check for the aes_key_wrap and dea_key_wrap machine options and set the
appropriate KVM device attribute(s) to tell the kernel to enable or disable
the AES/DEA protected key functions for the guest domain.

This patch introduces two new machine options for indicating the state of
AES/DEA key wrapping functions.  This controls whether the guest will
have access to the AES/DEA crypto functions.

aes_key_wrap="on | off" is changed to aes-key-wrap="on | off"
dea_key_wrap="on | off" is changed to dea-key-wrap="on | off"

Check for the aes-key-wrap and dea-key-wrap machine options and set the
appropriate KVM device attribute(s) to tell the kernel to enable or disable
the AES/DEA protected key functions for the guest domain.
Reviewed-by: NDavid Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: NTony Krowiak <akrowiak@linux.vnet.ibm.com>
Signed-off-by: NJens Freimann <jfrei@linux.vnet.ibm.com>
Message-Id: <1426164834-38648-4-git-send-email-jfrei@linux.vnet.ibm.com>
Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      2eb1cd07
  15. 10 3月, 2015 2 次提交
  17. 05 3月, 2015 1 次提交
  19. 22 1月, 2015 1 次提交
  21. 11 12月, 2014 1 次提交
    • L
      Add the "-semihosting-config" option. · a38bb079
      由 Liviu Ionescu 提交于 
      The usual semihosting behaviour is to process the system calls locally and
return; unfortuantelly the initial implementation dinamically changed the
target to GDB during debug sessions, which, for the usual arm-none-eabi-gdb,
is not implemented. The result was that during debug sessions the semihosting
calls were discarded.

This patch adds a configuration variable and an option to set it on the
command line:

    -semihosting-config [enable=on|off,]target=native|gdb|auto

This option enables semihosting and defines where the semihosting calls will
be addressed, to QEMU ('native') or to GDB ('gdb'). The default is auto, which
means 'gdb' during debug sessions and 'native' otherwise.
Signed-off-by: NLiviu Ionescu <ilg@livius.net>
Message-id: 1416341957-9796-1-git-send-email-ilg@livius.net
[PMM: moved declaration and definition of semihosting_target to
 gdbstub.h and gdbstub.c to fix build failure on linux-user]
Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      a38bb079
  23. 10 12月, 2014 1 次提交
  25. 26 11月, 2014 1 次提交
  27. 02 11月, 2014 1 次提交
  29. 31 10月, 2014 1 次提交
  31. 27 10月, 2014 1 次提交
    • M
      aio / timers: De-document -clock · e218052f
      由 Markus Armbruster 提交于 
      Commit 6d327171 "aio / timers: Remove alarm timers" has issues:

1. It silently ignores -clock for backward compatibility.
Incompatible change: -clock help no longer terminates the program.
Tolerable.

2. Failed to update option documentation.  In particular, -help still
advises users to try -clock help for available timers.  Drop all
documentation on -clock.

3. The 'query-alarm-clock' example in docs/writing-commands.txt no
longer works, and needs to be redone.  Can't do that right now, so I
just stick in a FIXME.
Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      e218052f
  33. 04 10月, 2014 1 次提交
  35. 01 9月, 2014 1 次提交
  37. 29 8月, 2014 3 次提交
  39. 16 8月, 2014 1 次提交
  41. 15 8月, 2014 2 次提交
  43. 06 8月, 2014 2 次提交
  45. 26 7月, 2014 1 次提交
  47. 27 6月, 2014 1 次提交
    • A
      net: L2TPv3 transport · 3fb69aa1
      由 Anton Ivanov 提交于 
      This transport allows to connect a QEMU nic to a static Ethernet
over L2TPv3 tunnel. The transport supports all options present
in the Linux kernel implementation. It allows QEMU to connect
to any Linux host running kernel 3.3+, most routers and network
devices as well as other QEMU instances.

[Fixed up net_client_init1() switch statement to support -netdev
--Stefan]
Signed-off-by: NAnton Ivanov <antivano@cisco.com>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      3fb69aa1
  49. 24 6月, 2014 1 次提交
  51. 19 6月, 2014 4 次提交
  53. 25 5月, 2014 1 次提交
  55. 21 5月, 2014 1 次提交
  57. 19 5月, 2014 2 次提交
    • P
      block: optimize zero writes with bdrv_write_zeroes · 465bee1d
      由 Peter Lieven 提交于 
      this patch tries to optimize zero write requests
by automatically using bdrv_write_zeroes if it is
supported by the format.

This significantly speeds up file system initialization and
should speed zero write test used to test backend storage
performance.

I ran the following 2 tests on my internal SSD with a
50G QCOW2 container and on an attached iSCSI storage.

a) mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/vdX

QCOW2         [off]     [on]     [unmap]
-----
runtime:       14secs    1.1secs  1.1secs
filesize:      937M      18M      18M

iSCSI         [off]     [on]     [unmap]
----
runtime:       9.3s      0.9s     0.9s

b) dd if=/dev/zero of=/dev/vdX bs=1M oflag=direct

QCOW2         [off]     [on]     [unmap]
-----
runtime:       246secs   18secs   18secs
filesize:      51G       192K     192K
throughput:    203M/s    2.3G/s   2.3G/s

iSCSI*        [off]     [on]     [unmap]
----
runtime:       8mins     45secs   33secs
throughput:    106M/s    1.2G/s   1.6G/s
allocated:     100%      100%     0%

* The storage was connected via an 1Gbit interface.
  It seems to internally handle writing zeroes
  via WRITESAME16 very fast.
Signed-off-by: NPeter Lieven <pl@kamp.de>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      465bee1d
    • M
      curl: Add usage documentation · 0a86cb73
      由 Matthew Booth 提交于 
      Signed-off-by: NMatthew Booth <mbooth@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      0a86cb73