On 21.04.2017 23:09, Eric Blake wrote:
> On 04/06/2017 11:40 AM, Eric Blake wrote:
>
>>> === Changes to the on-disk format ===
>>>
>>> The qcow2 on-disk format needs to change so each L2 entry has a bitmap
>>> indicating the allocation status of each subcluster. There are three
>>> possible states
On 21.04.2017 10:01, Kevin Wolf wrote:
> It is unused.
>
> Suggestetd-by: Fam Zheng
*Suggested
And, since it now would be rude not to, with that fixed:
Reviewed-by: Max Reitz
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/common.config | 18 --
> 1 file changed, 18
On 22.04.2017 00:34, Ping Li wrote:
> Currently, qemu-img 'amend' subcommand would fail to adjust image's backing
> file
> which was moved into different path.
> For example, parent.qcow2, the backing file of leaf.qcow2, first is at
> /home/a/,
> then moved into /home/b/. Originally this command,
On 21.04.2017 17:51, Stefan Hajnoczi wrote:
> On Sat, Apr 01, 2017 at 05:57:47PM +0200, Max Reitz wrote:
>> The issues of using C are well understood and nobody likes it. Let's use
>> a better language. C++ is not a better language, Rust is. Everybody
>> loves Rust. Rust is good. Rust is hip. It wi
Hi,
I think the bellow patch can fix your problme.
[PATCH 2/4] qmp-cont: invalidate on RUN_STATE_PRELAUNCH
https://patchwork.kernel.org/patch/9591885/
Actually, we encounter the same problem in our test, we fix it with the follow
patch:
From 0e4d6d706afd9909b5fd71536b45c58af60892f8 Mon Se
I have seen a bunch of reports about this assertion error (on source
QEMU). [At least I recall Greg Kurz mentioning this a week or so ago on
#qemu, OFTC.]
I just noticed this crash in upstream OpenStack CI environment. This
seems to occur (only intermittently, though) during live migration
witho