1. 19 11月, 2011 1 次提交
  2. 18 11月, 2011 5 次提交
  3. 17 11月, 2011 5 次提交
  4. 15 11月, 2011 4 次提交
  5. 14 11月, 2011 5 次提交
  6. 13 11月, 2011 1 次提交
  7. 12 11月, 2011 15 次提交
  8. 11 11月, 2011 4 次提交
    • A
      vl.c: Fail gracefully if no machine is found · d423675c
      Andreas Färber 提交于
      machine defaults to find_default_machine(),
      then gets overridden via -M and machine_parse().
      
      If no -M is specified and find_default_machine() returns NULL
      (when no machine compiled in), exit with an error.
      
      Avoids a segfault when setting machine->max_cpus.
      Signed-off-by: NAndreas Färber <andreas.faerber@web.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      d423675c
    • K
      block: Make cache=unsafe flush to the OS · ca716364
      Kevin Wolf 提交于
      cache=unsafe completely ignored bdrv_flush, because flushing the host disk
      costs a lot of performance. However, this means that qcow2 images (and
      potentially any other format) can lose data even after the guest has issued a
      flush if the qemu process crashes/is killed. In case of a host crash, data loss
      is certainly expected with cache=unsafe, but if just the qemu process dies this
      is a bit too unsafe.
      
      Now that we have two separate flush functions, we can choose to flush
      everythign to the OS, but don't enforce that it's physically written to the
      disk.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      ca716364
    • K
      block: Introduce bdrv_co_flush_to_os · eb489bb1
      Kevin Wolf 提交于
      qcow2 has a writeback metadata cache, so flushing a qcow2 image actually
      consists of writing back that cache to the protocol and only then flushes the
      protocol in order to get everything stable on disk.
      
      This introduces a separate bdrv_co_flush_to_os to reflect the split.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      eb489bb1
    • K
      block: Rename bdrv_co_flush to bdrv_co_flush_to_disk · c68b89ac
      Kevin Wolf 提交于
      There are two different types of flush that you can do: Flushing one level up
      to the OS (i.e. writing data to the host page cache) or flushing it all the way
      down to the disk. The existing functions flush to the disk, reflect this in the
      function name.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      c68b89ac