Search results

Jump to: navigation, search

Page title matches

  • ...mat extensions, have been merged back into qcow2 since. The development of QED has been abandoned. ...converting to qcow2 should be considered as today qcow2 provides both more features and better performance, and has an actively maintained code base.
    2 KB (241 words) - 14:42, 16 October 2017
  • ...ation. The following discusses how to implement online defragmentation in QED to attempt to address this over the life time of the VM
    2 KB (384 words) - 14:45, 11 October 2016
  • 57 B (8 words) - 16:50, 8 September 2010
  • ...d clusters. This spec discusses how to implement free cluster tracking in QED. * If we added a compat feature to QED that was a pointer to the first free block, we could chain subsequent block
    2 KB (336 words) - 14:44, 11 October 2016
  • When a request is submitted that is larger than a cluster in size, QED splits the request into multiple cluster sized requests and processes them ...ssion, and then start the processing of the next request. This will cause QED to break a single request into multiple parallel requests.
    777 B (119 words) - 14:45, 11 October 2016
  • 414 B (58 words) - 14:45, 11 October 2016
  • ==Outstanding features== * Block device support (i.e. QED on LVM volumes)
    3 KB (397 words) - 14:45, 11 October 2016
  • uint32_t magic; /* QED\0 */ uint64_t features; /* format feature bits */
    9 KB (1,374 words) - 14:45, 11 October 2016

Page text matches

  • ...mat extensions, have been merged back into qcow2 since. The development of QED has been abandoned. ...converting to qcow2 should be considered as today qcow2 provides both more features and better performance, and has an actively maintained code base.
    2 KB (241 words) - 14:42, 16 October 2017
  • Read [[Features/FVD/WhyFVD | Why FVD]]. Read [[Features/FVD/Design | How FVD Works]].
    2 KB (241 words) - 14:45, 11 October 2016
  • * qed: Fix consistency check on 32-bit hosts {{git|9b33410d3bdd40b6a289c6b79d40a9 * Various bug fixes, no new features.
    16 KB (2,781 words) - 08:34, 12 October 2016
  • ...L2 table cache size to make it happen less often? (Currently 16 * 512 MB, QED uses more) ...lly interesting scenario where you need an image format that provides some features. For qcow2, it's mostly the same as above.
    4 KB (552 words) - 08:57, 12 October 2016
  • ...s possible to make a QCOW2 snapshot of a RAW image, or a QED snapshot of a QED image. ...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
  • ==Outstanding features== * Block device support (i.e. QED on LVM volumes)
    3 KB (397 words) - 14:45, 11 October 2016
  • uint32_t magic; /* QED\0 */ uint64_t features; /* format feature bits */
    9 KB (1,374 words) - 14:45, 11 October 2016
  • == QCOW2 <-> QED image converter == ...image converter that safely and efficiently changes between the QCOW2 and QED image formats.
    15 KB (2,288 words) - 15:07, 16 February 2016
  • ...ages of FVD over QED. The other side of the story, i.e., the advantages of QED over FVD, might be presented separately elsewhere. By design, FVD has the following advantages over QED:
    8 KB (1,278 words) - 14:45, 11 October 2016
  • features that change the format in an incompatible way, so that older increase in order to introduce some incompatible features, however it's
    9 KB (1,281 words) - 10:12, 9 September 2016
  • Future qemu is expected to support these features (some already implemented): = Live features =
    21 KB (3,397 words) - 15:04, 11 October 2016
  • * {{git|4a81ab8}} qed: fix use-after-free during l2 cache commit ...registers mean we can boot more recent Linux kernels that probe for these features
    8 KB (1,151 words) - 06:40, 13 October 2011
  • ...guests use the same NBD image (for example as backing storage for QCOW or QED).
    932 B (132 words) - 14:56, 11 October 2016
  • * No more modifying guest drivers to add simple storage protocol features ====In-place qcow2 <-> qed conversion [Devin, GSoC 2011]:====
    4 KB (580 words) - 08:43, 12 October 2016
  • === QED === * Tested all 9p file system ( security models, features like mmap, locking, posixacl, zerocopy) using the basic fs tests, I/O and s
    7 KB (1,052 words) - 16:41, 29 November 2011
  • ...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. run against, say qcow2, vmdk, and qed. See the actual test code.
    2 KB (298 words) - 10:00, 12 October 2016
  • ...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 # thread-safe drivers [2.10, needs QED conversion to coroutines]
    17 KB (2,627 words) - 10:39, 6 September 2017

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