Search results

Jump to: navigation, search

Page title matches

  • = QMP Introspection = ...that introspection is limited to syntax and does not tell everything about QMP; developers should still read the documentation to learn semantic constrain
    4 KB (528 words) - 12:15, 12 October 2016

Page text matches

  • - QMP: Fix asynchronous events delivery (Luiz Capitulino) - QMP: Emit asynchronous events on all QMP monitors (Adam Litke)
    42 KB (6,720 words) - 12:21, 18 February 2011
  • * Support for network boot, see http://wiki.qemu-project.org/Features/S390xNetworkBoot * blockdev-add: This QMP command is no longer experimental, together with blockdev-del. Notable chan
    13 KB (1,919 words) - 09:03, 19 April 2017
  • * CPU model probing was implemented through the <tt>query-cpu-model-*</tt> QMP commands ...oleted by <tt>query-cpu-model-expansion</tt> QMP commands and <tt>filtered-features</tt> property
    15 KB (2,336 words) - 13:50, 30 October 2017
  • == Write a C QMP library based on QEMU JSON and QMP code == ...mplementing a higher level API based on this code that exposes each of the QMP functions.
    14 KB (2,116 words) - 15:02, 16 February 2016
  • ...nds attached to the monitor interface that are currently inaccessible over QMP (QEMU Machine Protocol). I intend to give continuity to this effort, conver * Status: some patches have been merged into upstream, but no QMP yet. These cleanups are needed before trying to specify the protocol.
    23 KB (3,423 words) - 17:43, 11 August 2010
  • ...col-visible changes as much as possible. Provide a C library interface to QMP such that can be used to write thorough in-tree unit tests. ...tor. This spec describes the types of changes that are needed to decouple QMP from the human monitor and fix the deficiencies that are currently present.
    16 KB (2,377 words) - 18:10, 2 April 2015
  • The first patchset that brings basic tracing features to QEMU. http://wiki.qemu.org/Features/Tracing/Roadmap
    4 KB (631 words) - 14:59, 11 October 2016
  • ** Tracing framework is described at [[Features/Tracing]] and in docs/tracing.txt in the source tree. ...tion/QMP|QMP]]. See also https://www.linux-kvm.org/images/1/17/2010-forum-qmp-status-talk.pp.pdf
    7 KB (1,207 words) - 18:49, 27 February 2017
  • The QEMU Machine Protocol (QMP) is a [http://www.json.org/ JSON]-based protocol which allows applications Features:
    4 KB (574 words) - 18:01, 17 February 2017
  • * QMP command blockdev-add is still a work in progress. It doesn't support all b * qmp: New MIGRATION event to communicate change in the migration state
    13 KB (2,067 words) - 17:11, 2 December 2015
  • * Various bug fixes, no new features. ...U Enhanced Disk (qed) image format. It is a disk image format that forgoes features found in qcow2 in favor of better levels of performance and data integrity.
    16 KB (2,781 words) - 08:34, 12 October 2016
  • ; QEMU user mode emulation (docs/user, [[Features/Documentation/user]]) ; QEMU full-system emulation user's guide (docs/system, [[Features/Documentation/system]])
    6 KB (871 words) - 15:06, 7 July 2017
  • The idea is to be able to issue a command to QEMU via the monitor or QMP, which causes QEMU to create a new snapshot image with the original image a ...QAPI/GuestAgent Guest Agent]. Please check the guest [http://wiki.qemu.org/Features/QAPI/GuestAgent Guest Agent] page for design and implementation details.
    21 KB (3,274 words) - 14:58, 11 October 2016
  • Future qemu is expected to support these features (some already implemented): = Live features =
    21 KB (3,397 words) - 15:04, 11 October 2016
  • ...ture introduces QEMU block layer I/O limits together with command-line and QMP interfaces for configuring limits. This allows I/O limits to be imposed ac * [[Features/DiskIOLimits/Requirements|Requirements]]
    1 KB (211 words) - 14:54, 11 October 2016
  • easy to understand and implement. The fine-grained features are marked == QMP interface ==
    4 KB (631 words) - 15:41, 11 October 2016
  • ...registers mean we can boot more recent Linux kernels that probe for these features * Removed dependency on external kernel headers, all supported KVM features are now built into the binary
    8 KB (1,151 words) - 06:40, 13 October 2011
  • === HMP/QMP/QAPI === * Run kvm-autotest under QMP [LuizCapitulino]
    7 KB (1,052 words) - 16:41, 29 November 2011
  • ...g a pflash drive. This feature is not supported when KVM is enabled. See [[Features/PC System Flash]] for more information. * KVM guests support Hyper-V enlightenments. These are enabled by the -cpu features hv_spinlocks, hv_relaxed and hv_vapic.
    8 KB (1,276 words) - 05:38, 3 June 2012
  • One is Jeff Cody's multiple-device snapshot series, documented [[Features/SnapshotsMultipleDevices|here]]. ...rive-mirror and blockdev-snapshot-sync can be part of a transaction. Other QMP commands are not, and will never be part of a transaction even in future ve
    5 KB (591 words) - 08:39, 12 October 2016
  • === QMP === * The sendkey monitor command is now available via QMP.
    6 KB (951 words) - 16:38, 15 January 2013
  • * The CPU is now a device. Adding CPUs via -device or HMP/QMP device_add is not supported yet. * Various minor bugfixes; no new features in this release.
    4 KB (589 words) - 12:24, 19 February 2013
  • ...cpu-add QMP command. More details [[Features/CPUHotplug#cpu-add_interface|Features/CPUHotplug]]. ...ltered-features" to allow introspection of supported and not supported CPU features.
    7 KB (1,120 words) - 18:28, 27 May 2013
  • ...It should integrate into the existing build system. Currently, we allow features to be specified in for inclusion in a boolean fashion (either 'y' or 'n' to ...mechanism to support third party extensions to QEMU or out of tree drivers/features
    9 KB (1,464 words) - 19:33, 11 August 2016
  • ...ts/qemu-iotests/. It contains test for disk image formats and block layer features. launch QEMU and interact with the QMP monitor (JSON), which is hard to
    2 KB (298 words) - 10:00, 12 October 2016
  • Or, if you're using the QMP (QEMU Machine Protocol), issue this equivalent command: ...like [http://git.qemu.org/?p=qemu.git;a=blob;f=qapi-schema.json;h=8b1a423 qmp-shell] (from QEMU Git source).
    6 KB (885 words) - 12:28, 16 March 2017
  • ...and can be used by firmware directly. This will in the future enable new features without modifications of all firmware components (SeaBIOS, OVMF, CoreBoot) * New command "blockdev-add" provides a QMP interface for block device hotplug.
    4 KB (563 words) - 11:31, 10 December 2013
  • * Initial support for KVM on AArch64 systems (some features such as migration are not yet implemented) ...5420 is needed. In particular hotplug, pvpanic device and other ACPI based features now work for OVMF.
    10 KB (1,572 words) - 19:24, 16 April 2014
  • ...contains block layer and storage features that have been proposed. These features may not be in active development and questions about them should be address *** Enforce that new QMP/QAPI commands and block jobs add themselves to the matrix
    17 KB (2,627 words) - 10:39, 6 September 2017
  • ...than q35 does (e.g. interrupt remapping). As time permits, some additional features could already be added so that q35 could be manually configured to expose t Minimally required VT-d features for q35 are:
    19 KB (3,009 words) - 15:08, 16 February 2016
  • === QMP legacy interface to the QAPI === ...onverted). You can find more details in the [http://wiki.qemu.org/QMP#TODO QMP TODO page].
    8 KB (1,232 words) - 18:25, 23 November 2017
  • * New monitor command "info memdev" (with the QMP counterpart "query-memdev"). * New QMP command "query-acpi-ospm-status" and event "ACPI_DEVICE_OST" provide inform
    10 KB (1,454 words) - 10:42, 29 July 2014
  • ...e. Only x3270 is supported as client. See https://wiki.qemu.org/index.php/Features/3270 for details. ...vfio-ccw (channel device passthrough). See https://wiki.qemu.org/index.php/Features/Channel_I/O_Passthrough for details.
    11 KB (1,614 words) - 18:24, 24 August 2017
  • There are several features still pending: * QEMU currently offers dirty blocks in a "push-only" mechanism via the QMP command drive-backup, which unconditionally sends all dirty blocks over the
    26 KB (4,021 words) - 23:28, 21 February 2017
  • * QMP command blockdev-add is still a work in progress. It doesn't support all b * [[Features/HRandomHypercall | H_RANDOM hypercall]] device for providing good random da
    13 KB (2,001 words) - 11:33, 17 December 2015
  • ...changes that update user-visible interface options (command line options, QMP, etc.). Use the source of this page to populate a new one for the new feat * qmp commands
    4 KB (547 words) - 04:52, 1 December 2015
  • = QMP Introspection = ...that introspection is limited to syntax and does not tell everything about QMP; developers should still read the documentation to learn semantic constrain
    4 KB (528 words) - 12:15, 12 October 2016
  • * QMP command blockdev-add is still a work in progress. It doesn't support all b * Support for the XSAVE/XSAVEOPT, MPX, FSGSBASE and PKE features
    20 KB (2,998 words) - 09:09, 19 July 2016
  • * QMP command blockdev-add is still a work in progress. It doesn't support all b * new 'info hotpluggable-cpus' and corresponding 'query-hotpluggable-cpus' QMP commands<br>to list present/possible CPUs with properties necessary to add
    12 KB (1,746 words) - 15:53, 1 September 2016
  • * QMP command blockdev-add is still a work in progress. It doesn't support all b * Support for several new CPUID features related to AVX-512 instruction set extensions.
    9 KB (1,253 words) - 11:05, 21 December 2016
  • using QEMU's QMP commands. Backup software and management stack developers * [[Features/IncrementalBackup]]
    2 KB (248 words) - 17:18, 23 January 2017
  • ...eprecated Features"] appendix for the full list of historically deprecated features/options. ...necessary to specify "read-only=on" explicitly on the command line and in QMP commands for the setup to keep working; the default "read-only=off" setting
    10 KB (1,450 words) - 11:19, 12 December 2017

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)