On 25.06.2020 18:22, Max Reitz wrote:
Parts of the block layer treat BDS.backing_file as if it were whatever
the image header says (i.e., if it is a relative path, it is relative to
the overlay), other parts treat it like a cache for
bs->backing->bs->filename (relative paths are relative to the
27.07.2020 14:23, Dr. David Alan Gilbert wrote:
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
Bitmaps data is not critical, and we should not fail the migration (or
use postcopy recovering) because of dirty-bitmaps migration failure.
Instead we should just lose unfinished
27.07.2020 14:16, Dr. David Alan Gilbert wrote:
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
24.07.2020 20:35, Eric Blake wrote:
On 7/24/20 3:43 AM, Vladimir Sementsov-Ogievskiy wrote:
Bitmaps data is not critical, and we should not fail the migration (or
use postcopy
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> Bitmaps data is not critical, and we should not fail the migration (or
> use postcopy recovering) because of dirty-bitmaps migration failure.
> Instead we should just lose unfinished bitmaps.
>
> Still we have to report io stream
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> 24.07.2020 20:35, Eric Blake wrote:
> > On 7/24/20 3:43 AM, Vladimir Sementsov-Ogievskiy wrote:
> > > Bitmaps data is not critical, and we should not fail the migration (or
> > > use postcopy recovering) because of dirty-bitmaps
On 26.07.20 17:25, Nir Soffer wrote:
> Add test for "qemu-img convert -O qcow2 -c" to NBD target. The use case
> is writing compressed disk content to OVA archive.
>
> Signed-off-by: Nir Soffer
> ---
> tests/qemu-iotests/302 | 83 ++
>
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> No reasons to keep two public init functions.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> Reviewed-by: Andrey Shinkevich
Yes so I think that means the initialisation of that lock is a little
later in startup, but OK
On Jul 20 13:37, Klaus Jensen wrote:
> From: Klaus Jensen
>
> This series consists of patches that refactors dma read/write and adds a
> number of address mapping helper functions.
>
> Based-on: <20200706061303.246057-1-...@irrelevant.dk>
>
> Klaus Jensen (16):
> hw/block/nvme: memset
On Jul 22 07:48, Michael S. Tsirkin wrote:
> On Mon, Jun 29, 2020 at 10:20:52PM +0200, Klaus Jensen wrote:
> > From: Klaus Jensen
> >
> > Some devices might want to know the return value of dma_memory_rw, so
> > pass it along instead of ignoring it.
> >
> > There are no existing users of the
On Jul 23 09:03, Andrzej Jakowski wrote:
> So far it was not possible to have CMB and PMR emulated on the same
> device, because BAR2 was used exclusively either of PMR or CMB. This
> patch places CMB at BAR4 offset so it not conflicts with MSI-X vectors.
>
> Signed-off-by: Andrzej Jakowski
>
On 26.07.20 17:25, Nir Soffer wrote:
> When converting to qcow2 compressed format, the last step is a special
> zero length compressed write, ending in call to bdrv_co_truncate(). This
> call always fail for the nbd driver since it does not implement
> bdrv_co_truncate().
>
> For block devices,
Daniel P. Berrangé writes:
> Currently at startup if using cache=none on a filesystem lacking
> O_DIRECT such as tmpfs, at startup QEMU prints
>
> qemu-system-x86_64: -drive file=/tmp/foo.img,cache=none: file system may not
> support O_DIRECT
> qemu-system-x86_64: -drive
Daniel P. Berrangé writes:
> This introduces two new helper metohds
Typo metohds.
Suggest to be a bit more explicit on why we want to replace qemu_open(),
perhaps like this:
qemu_open_old() works like open(): set errno and return -1 on failure.
It has even more failure modes, though.
101 - 113 of 113 matches
Mail list logo
