Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 23 6月, 2015 2 次提交
  3. 28 4月, 2015 1 次提交
  5. 10 3月, 2015 1 次提交
  7. 07 2月, 2015 2 次提交
  9. 29 1月, 2015 2 次提交
  11. 27 9月, 2014 2 次提交
  13. 25 4月, 2014 4 次提交
  15. 11 3月, 2014 1 次提交
  17. 01 3月, 2014 1 次提交
  19. 07 1月, 2014 1 次提交
  21. 17 6月, 2013 1 次提交
  23. 19 12月, 2012 2 次提交
  25. 24 10月, 2012 2 次提交
    • P
      qmp: handle stop/cont in INMIGRATE state · 1e998146
      由 Paolo Bonzini 提交于 
      Right now, stop followed by an incoming migration will let the
virtual machine start.  cont before an incoming migration instead
will fail.

This is bad because the actual behavior is not predictable; it is
racy with respect to the start of the incoming migration.  That's
because incoming migration is blocking, and thus will delay the
processing of stop/cont until the end of the migration.

In addition, there's nothing that really prevents the user from
typing the block device's passwords before incoming migration is
done, so returning the DeviceEncrypted error is also helpful in
the QMP case.

Both things can be fixed by just toggling the autostart variable when
stop/cont are called in INMIGRATE state.

Note that libvirt is currently working around the race by looping
if the MigrationExpected answer is returned.  After this patch, the
command will return right away without ever raising an error.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      1e998146
    • P
      block: add block-job-complete · aeae883b
      由 Paolo Bonzini 提交于 
      While streaming can be dropped as soon as it progressed through the whole
image, mirroring needs to be completed manually for two reasons: 1) so that
management knows exactly when the VM switches to the target; 2) because
for other use cases such as replication, we may leave the operation running
for the whole life of the virtual machine.

Add a new block job command that manually completes background operations.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      aeae883b
  27. 23 10月, 2012 1 次提交
  29. 29 9月, 2012 2 次提交
  31. 14 8月, 2012 11 次提交
  33. 05 6月, 2012 1 次提交
  35. 11 5月, 2012 1 次提交
  37. 05 4月, 2012 1 次提交
    • S
      qdev: add blocksize property type · 02fda01c
      由 Stefan Hajnoczi 提交于 
      Storage interfaces like virtio-blk can be configured with block size
information so that the guest can take advantage of efficient I/O
request sizes.

According to the SCSI Block Commands (SBC) standard a device's block
size is "almost always greater than one byte and may be a multiple of
512 bytes".  QEMU currently has a 512 byte minimum block size because
the block layer functions work at that granularity.  Furthermore, the
block size should be a power of 2 because QEMU calculates bitmasks from
the value.

Introduce a "blocksize" property type so devices can enforce these
constraints on block size values.  If the constraints are relaxed in the
future then this property can be updated.

Introduce the new PropertyValueNotPowerOf2 QError so QMP clients know
exactly why a block size value was rejected.
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      02fda01c
  39. 15 3月, 2012 1 次提交