search for: bdrv_make_zero

Displaying 5 results from an estimated 5 matches for "bdrv_make_zero".

2020 Feb 18
1
Re: Cross-project NBD extension proposal: NBD_INFO_INIT_STATE
...o ensure that some image is > zero. Knowing whether an image is zero can help with that, but that can > be an implementation detail. > > For qcow2, the idea would be that there is some flag that remains true > as long as the image is guaranteed to be zero. Then we’d have some > bdrv_make_zero function, and qcow2’s implementation would use this > information to gauge whether there’s something to do as all. > > For NBD, we cannot use this idea directly because to implement such a > flag (as you’re describing in this mail), we’d need separate is_zero > infrastructure, and t...
2020 Feb 17
0
Re: Cross-project NBD extension proposal: NBD_INFO_INIT_STATE
...cases involve someone having to ensure that some image is zero. Knowing whether an image is zero can help with that, but that can be an implementation detail. For qcow2, the idea would be that there is some flag that remains true as long as the image is guaranteed to be zero. Then we’d have some bdrv_make_zero function, and qcow2’s implementation would use this information to gauge whether there’s something to do as all. For NBD, we cannot use this idea directly because to implement such a flag (as you’re describing in this mail), we’d need separate is_zero infrastructure, and that kind of makes the poi...
2020 Feb 10
17
Cross-project NBD extension proposal: NBD_INFO_INIT_STATE
I will be following up to this email with four separate threads each addressed to the appropriate single list, with proposed changes to: - the NBD protocol - qemu: both server and client - libnbd: client - nbdkit: server The feature in question adds a new optional NBD_INFO_ packet to the NBD_OPT_GO portion of handshake, adding up to 16 bits of information that the server can advertise to the
2015 Jul 29
3
qemu-kvm-ev with CentOS 7.1
Hello, All! Is it possible to use binary packages build from http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7/SRPMS/qemu-kvm-ev-2.1.2-23.el7_1.3.1.src.rpm with plain CentOS 7.1 and use all other packages from CentOS (libvirt, virt-manager, etc) Is it have reasons, if I not use live migrations and qcow2 snapshots? (instead use zfs, zvols and zfs snapshots for VM disks online backups) Is using
2015 Jul 29
2
CentOS 7.1 + qemu-kvm-ev + SLIC acpitable windows bug workaround
...Version: 2.1.2 Release: 23%{?dist}_1.3.1 # Epoch because we pushed a qemu-1.0 package. AIUI this can't ever be dropped -Epoch: 10 +Epoch: 77 License: GPLv2+ and LGPLv2+ and BSD Group: Development/Tools URL: http://www.qemu.org/ @@ -847,6 +847,8 @@ Patch341: kvm-block-Fix-max-nb_sectors-in-bdrv_make_zero.patch # For bz#1219271 - Patch342: kvm-fdc-force-the-fifo-access-to-be-in-bounds-of-the-all.patch +# copy OEM ACPI parameters from SLIC table to RSDT +Patch999: mjt-set-oem-in-rsdt-like-slic.diff BuildRequires: zlib-devel BuildRequires: SDL-devel @@ -1400,6 +1402,7 @@ %patch340 -p1 %patch...