[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1186303
Title:
virtual fat
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1186984
Title:
large -init
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329120745.11154-1-be...@igalia.com
Subject: [Qemu-devel] [PATCH for-2.12 v5] iotest
Disregard the above log; that was from a September 2017 build.
On RC1:
Process: qemu-system-x86_64 [6567]
Path: /usr/local/bin/qemu-system-x86_64
Identifier:qemu-system-x86_64
Version: 0
Code Type: X86-64 (Native)
Parent Process
Process: qemu-system-x86_64 [6330]
Path: /Users/USER/*/qemu-system-x86_64
Identifier:qemu-system-x86_64
Version: 0
Code Type: X86-64 (Native)
Parent Process:bash [1558]
Responsible: qemu-system-x86_64 [6330]
User
Le 30/03/2018 à 21:59, Max Filippov a écrit :
> In case of syscall restart request set pc back to the syscall
> instruction.
>
> Signed-off-by: Max Filippov
> ---
> linux-user/main.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/linux-user/main.c b/linux-user/main.c
> index ba09b7
I no longer see the "WARNING: I/O thread spun for 1000 iterations"
message. A bisection showed that it disappeared with the following
commit:
commit e330c118f2a5a5365409b123cd0dd2c7d575bf05
Author: Paolo Bonzini
Date: Fri Mar 3 11:51:07 2017 +0100
main-loop: remove now unnecessary optimiz
Le 31/03/2018 à 19:16, Max Filippov a écrit :
> mq_getsetattr implementation does not set errno correctly in case of
> error. Also in the presence of both 2nd and 3rd arguments it calls both
> mq_getattr and mq_setattr, whereas only the latter call would suffice.
>
> Don't call mq_getattr in the p
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180331171615.21259-1-jcmvb...@gmail.com
Subject: [Qemu-devel] [PATCH v3] linux-user: fix
mq_getsetattr implementation does not set errno correctly in case of
error. Also in the presence of both 2nd and 3rd arguments it calls both
mq_getattr and mq_setattr, whereas only the latter call would suffice.
Don't call mq_getattr in the presence of the 2nd argument. Don't copy
output back to u
mq_getsetattr implementation does not set errno correctly in case of
error. Also in the presence of both 2nd and 3rd arguments it calls both
mq_getattr and mq_setattr, whereas only the latter call would suffice.
Don't call mq_getattr in the presence of the 2nd argument. Don't copy
output back to u
Le 31/03/2018 à 18:57, Laurent Vivier a écrit :
> Le 31/03/2018 à 18:23, Max Filippov a écrit :
>> mq_getsetattr implementation does not set errno correctly in case of
>> error. Also in the presence of both 2nd and 3rd arguments it calls both
>> mq_getattr and mq_setattr, whereas only the latter ca
Le 31/03/2018 à 18:23, Max Filippov a écrit :
> mq_getsetattr implementation does not set errno correctly in case of
> error. Also in the presence of both 2nd and 3rd arguments it calls both
> mq_getattr and mq_setattr, whereas only the latter call would suffice.
>
> Don't call mq_getattr in the p
mq_getsetattr implementation does not set errno correctly in case of
error. Also in the presence of both 2nd and 3rd arguments it calls both
mq_getattr and mq_setattr, whereas only the latter call would suffice.
Don't call mq_getattr in the presence of the 3rd argument. Use get_errno
to set errno
On 03/31/2018 03:45 AM, Lai Jiangshan wrote:
1) What's this
When the migration capability 'bypass-shared-memory'
is set, the shared memory will be bypassed when migration.
It is the key feature to enable several excellent features for
the qemu, such as qemu-local-migration, qemu-live-update,
ex
During implementation of NBD_CMD_BLOCK_STATUS in qemu, it was
discovered that parsing for the colon that separates the namespace
from the leaf-name can get awkward; a slight tweak to the wire
layout produces something a little friendlier to manipulate.
Since NBD strings are capped at 4k each, 16 b
During implementation of NBD_CMD_BLOCK_STATUS, we found that parsing
for the colon that separates namespaces from leaf-names can get
awkward. Simplify things slightly by passing the two as separate
fields, and noting that since strings are capped to 4k, a 16-bit
rather than 32-bit length field is
As mentioned in earlier email threads, I experimented with an
alternative layout to the structs sent across the wire during
NBD_OPT_{LIST,SET}_META_CONTEXT, on the grounds that having the
namespace and leaf-name combined into one string that requires further
parsing on each end is not as nice a
1) What's this
When the migration capability 'bypass-shared-memory'
is set, the shared memory will be bypassed when migration.
It is the key feature to enable several excellent features for
the qemu, such as qemu-local-migration, qemu-live-update,
extremely-fast-save-restore, vm-template, vm-fast
The attached patch is based on v2.11.1. It was pushed on
https://github.com/hyperhq/qemu v2.11.1-template
The updated patch for upstream qemu is on
https://github.com/hyperhq/qemu upstream-template
On Sat, Mar 31, 2018 at 4:45 PM, Lai Jiangshan wrote:
> ---
> migration/migration.c | 13 +
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id:
152246970464.28900.5033274314150943057.malone...@chaenomeles.canonical.com
Subject: [Qe
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330195928.15607-1-jcmvb...@gmail.com
Subject: [Qemu-devel] [PATCH] target/xtensa: l
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329231837.1914680-1-ebl...@redhat.com
Subject: [Qemu-devel] [PATCH for-2.12] nbd/cl
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
N/A. Internal error while reading log file
---
Email generated automatically by Patchew [http://patchew.org/].
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330170209.20627-1-rka...@virtuozzo.com
Subject: [Qemu-devel] [PATCH for-2.12 v3 0/2]
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330195928.15607-1-jcmvb...@gmail.com
Subject: [Qemu-devel] [PATCH] target/xtensa: li
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id:
152246970464.28900.5033274314150943057.malone...@chaenomeles.canonical.com
Subject: [Qemu
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330161040.350271-1-vsement...@virtuozzo.com
Subject: [Qemu-devel] [PATCH] iotests:
On 2018-03-31 09:32, no-re...@patchew.org wrote:
> Hi,
>
> This series failed docker-quick@centos6 build test. Please find the testing
> commands and
> their output below. If you have Docker installed, you can probably reproduce
> it
> locally.
Apparently, this test case is broken. Who is opera
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330133525.10994-1-jcmvb...@gmail.com
Subject: [Qemu-devel] [PATCH] linux-user: call
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522422996-14235-1-git-send-email-vsement...@virtuozzo.com
Subject: [Qemu-devel] [PATCH 0
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180327045646.21112-1-js...@redhat.com
Subject: [Qemu-devel] [PULL 0/2] Ide patches
==
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329151018.15319-1-brog...@suse.com
Subject: [Qemu-devel] [PATCH] sys_membarrier: fi
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522422996-14235-1-git-send-email-vsement...@virtuozzo.com
Subject: [Qemu-devel] [PATCH 0/
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330195928.15607-1-jcmvb...@gmail.com
Subject: [Qemu-devel] [PATCH] target/xtensa: lin
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330170209.20627-1-rka...@virtuozzo.com
Subject: [Qemu-devel] [PATCH for-2.12 v3 0/2]
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330130950.1931229-1-ebl...@redhat.com
Subject: [Qemu-devel] [PATCH for-2.12] nbd: tra
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180330075128.26919-1-xiaoguangr...@tencent.com
Subject: [Qemu-devel] [PATCH v3 00/10] m
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329113320.8053-1-coh...@redhat.com
Subject: [Qemu-devel] [PATCH for-2.13] s390x: in
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329110914.20888-1-f...@redhat.com
Subject: [Qemu-devel] [RFC PATCH 0/8] qemu-img co
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329151018.15319-1-brog...@suse.com
Subject: [Qemu-devel] [PATCH] sys_membarrier: fix
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180328133152.24623-1-lviv...@redhat.com
Subject: [Qemu-devel] [PATCH] tcg: fix 16-byte
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522270761-29646-1-git-send-email-stef...@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATC
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329052537.32163-1-da...@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH for-2.13
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id:
152246970464.28900.5033274314150943057.malone...@chaenomeles.canonical.com
Subject: [Qemu-devel] [Bug 1760262] [NEW] cmsdk-apb-uart doesn't appear to
clear interrupt flags
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180329231837.1914680-1-ebl...@redhat.com
Subject: [Qemu-devel] [PATCH for-2.12] nbd/clie
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180328170207.49512-1-dgilb...@redhat.com
Subject: [Qemu-devel] [PATCH] migration: Don'
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522180547-22956-1-git-send-email-...@sifive.com
Subject: [Qemu-devel] [PATCH v1 0/2] RI
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180327153011.29569-1-marcandre.lur...@redhat.com
Subject: [Qemu-devel] [PATCH] blockjo
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: f6aa6ac8-3c3c-bf90-6273-3d584f470...@web.de
Subject: [Qemu-devel] [PATCH] hw/i386: Fix IV
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180326191603.10217-1-laur...@vivier.eu
Subject: [Qemu-devel] [PATCH for 2.13 00/19] li
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522163370-18544-1-git-send-email-th...@redhat.com
Subject: [Qemu-devel] [PATCH] configu
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 20180327144124.32533-1-stefa...@redhat.com
Subject: [Qemu-devel] [PULL 0/4] Block patche
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1522124046-34596-1-git-send-email-jianjay.z...@huawei.com
Subject: [Qemu-devel] [PATCH R
54 matches
Mail list logo
