Search results

delete [] randbyte; delete QNG;

...e to Windows by opening QEMU's monitor window and typing "sendkey ctrl-alt-delete". QEMU's monitor window can be accessed by typing control-alt-2.</li>

...hot image cannot be returned to its original state once modified. Instead delete the first snapshot image (''snapshot.img'' in our example), create another ...leaninstall.img'' in our example) will corrupt its snapshots. Make sure to delete any snapshots before running and modifying the original image. Use the ''q

...e to Windows by opening QEMU's monitor window and typing "sendkey ctrl-alt-delete". QEMU's monitor window can be accessed by typing control-alt-2.</li>

7fdc61c75d4064d2e48777172bbe8e0e970de7d9 migration: delete QEMUFile stdio implementation 40946ae40b33b8aa03fa9b56a374f5d4b5f7aab7 migration: delete QEMUFile sockets implementation

delete [] randbyte; delete QNG;

* bitmap delete regression, including crash if transaction involved https://lists.gnu.org/a

=== snapshot-delete === -> {"execute": "snapshot-delete", "arguments": {"name": "vm_before_upgrade"} }

9 delete the internal snapshot. 9 delete the internal snapshot.

.../create/read/write/close/rename/link/unlink/readdir/readlink/statfs/lookup/delete/truncate, acl, mmap, zerocopy,locking, xattr,sync,fragmentation || dbench, .../create/read/write/close/rename/link/unlink/readdir/readlink/statfs/lookup/delete/truncate, acl, mmap, zerocopy,locking, xattr,sync,fragmentation || dbench,

Traditionally an application will merely delete a volume when it is done with it. For file based images this newly created

* delete all the old texinfo build machinery, install runes, etc * I think we should just delete the "QEMU compared to other emulators" section of qemu-tech.texi (and the a

* Managing live snapshots. It should be possible to delete a live snapshot. Upon deletion, writes should go to normal storage.

* control / allocate / delete resources

* New commands "blockdev-snapshot-internal-sync", "blockdev-snapshot-delete-internal-sync" improve support for internal qcow2 snapshot.

: Delete a bitmap that is not currently in-use by a backup operation. <li><p>Delete the failed incremental, and re-create the image.</p>

...drive-reopen'' succeeds on disk 1 then fails on disk 2, then libvirt can't delete the snapshot, but it also can't perform a rollback (doing yet another ''dri

* QMP native snapshot commands -snapshot-{save,load,delete} * The new QMP commands load-snapshot, save-snapshot and delete-snapshot provide a mechanism for managing internal qcow2 snapshots, that wa

...y newly created files have mode <code>0600</code> when daemonizing. Please delete your old files or change their permissions manually when upgrading.

2. Snapshot create and delete [4 days]