Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 11 10月, 2013 7 次提交
  3. 03 10月, 2013 1 次提交
  5. 21 9月, 2013 1 次提交
  7. 12 9月, 2013 5 次提交
  9. 06 9月, 2013 5 次提交
  11. 30 8月, 2013 1 次提交
  13. 23 8月, 2013 1 次提交
  15. 22 8月, 2013 1 次提交
  17. 14 8月, 2013 1 次提交
  19. 10 8月, 2013 1 次提交
  21. 03 8月, 2013 1 次提交
  23. 27 7月, 2013 6 次提交
    • S
      misc: Use g_assert_not_reached for code which is expected to be unreachable · dfc6f865
      由 Stefan Weil 提交于 
      The macro g_assert_not_reached is a better self documenting replacement
for assert(0) or assert(false).
Signed-off-by: NStefan Weil <sw@weilnetz.de>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      dfc6f865
    • I
      Implement sync modes for drive-backup. · fc5d3f84
      由 Ian Main 提交于 
      This patch adds sync-modes to the drive-backup interface and
implements the FULL, NONE and TOP modes of synchronization.

FULL performs as before copying the entire contents of the drive
while preserving the point-in-time using CoW.
NONE only copies new writes to the target drive.
TOP copies changes to the topmost drive image and preserves the
point-in-time using CoW.

For sync mode TOP are creating a new target image using the same backing
file as the original disk image.  Then any new data that has been laid
on top of it since creation is copied in the main backup_run() loop.
There is an extra check in the 'TOP' case so that we don't bother to copy
all the data of the backing file as it already exists in the target.
This is where the bdrv_co_is_allocated() is used to determine if the
data exists in the topmost layer or below.

Also any new data being written is intercepted via the write_notifier
hook which ends up calling backup_do_cow() to copy old data out before
it gets overwritten.

For mode 'NONE' we create the new target image and only copy in the
original data from the disk image starting from the time the call was
made.  This preserves the point in time data by only copying the parts
that are *going to change* to the target image.  This way we can
reconstruct the final image by checking to see if the given block exists
in the new target image first, and if it does not, you can get it from
the original image.  This is basically an optimization allowing you to
do point-in-time snapshots with low overhead vs the 'FULL' version.

Since there is no old data to copy out the loop in backup_run() for the
NONE case just calls qemu_coroutine_yield() which only wakes up after
an event (usually cancel in this case).  The rest is handled by the
before_write notifier which again calls backup_do_cow() to write out
the old data so it can be preserved.
Signed-off-by: NIan Main <imain@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      fc5d3f84
    • K
      blockdev: Split up 'cache' option · 29c4e2b5
      由 Kevin Wolf 提交于 
      The old 'cache' option really encodes three different boolean flags into
a cache mode name, without providing all combinations. Make them three
separate options instead and translate the old option to the new ones
for drive_init().

The specific boolean options take precedence if the old cache option is
specified as well, so the following options are equivalent:

-drive file=x,cache=none,cache.no-flush=true
-drive file=x,cache.writeback=true,cache.direct=true,cache.no-flush=true
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      29c4e2b5
    • K
      blockdev: Rename 'readonly' option to 'read-only' · 0f227a94
      由 Kevin Wolf 提交于 
      Option name cleanup before it becomes a QMP API.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      0f227a94
    • K
      blockdev: Rename I/O throttling options for QMP · 57975222
      由 Kevin Wolf 提交于 
      In QMP, we want to use dashes instead of underscores in QMP argument
names, and use nested options for throttling.

The new option names affect the command line as well, but for
compatibility drive_init() will convert the old option names before
calling into the code that will be shared between -drive and
blockdev-add.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      57975222
    • K
      block: Allow "driver" option on the top level · 74fe54f2
      由 Kevin Wolf 提交于 
      This is traditionally -drive format=..., which is now translated into
the new driver option. This gives us a more consistent way to select the
driver of BlockDriverStates that can be used in QMP context, too.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      74fe54f2
  25. 15 7月, 2013 1 次提交
    • S
      blockdev: add sync mode to drive-backup QMP command · b53169ea
      由 Stefan Hajnoczi 提交于 
      The drive-backup command is similar to the drive-mirror command, except
no guest data written after the command executes gets copied.  Add a
sync mode argument which determines whether the entire disk is copied,
just allocated clusters, or only clusters being written to by the guest.

Currently only sync mode 'full' is supported - it copies the entire disk.
For read-only point-in-time snapshots we may only need sync mode 'none'
since the target can be a qcow2 file using the guest's disk as its
backing file (no need to copy the entire disk).  Finally, sync mode
'top' is useful if we wish to preserve the backing chain.

Note that this patch just adds the sync mode argument to drive-backup.
It does not implement sync modes 'top' or 'none'.  This patch is
necessary so we can add a drive-backup HMP command that behaves like the
existing drive-mirror HMP command and takes a sync mode.
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      b53169ea
  27. 28 6月, 2013 7 次提交
  29. 24 6月, 2013 1 次提交