On Thu, Jun 15, 2017 at 04:04:56PM +0100, Peter Maydell wrote:
> On 15 June 2017 at 15:57, Edgar E. Iglesias wrote:
> > On Thu, Jun 15, 2017 at 03:40:40PM +0100, Peter Maydell wrote:
> >> Unfortunately we make no guarantees at all about migration order
> >> for devices as far as I'm aware, so devi
Hi,
Peter noticed that there were some hangs in the ahci-test;
I can reproduce them on my laptop as long as the laptop has
some other load on it (a few md5sum /dev/zero's help).
/x86_64/ahci/flush/migrate: qemu-system-x86_64: Failed to get "write" lock
Is another process using the image?
OK
/x86
On 13 June 2017 at 21:26, Richard Henderson wrote:
> Cleanups and fixes from David Hildenbrand.
>
>
> r~
>
>
>
> The following changes since commit 3f0602927b120a480b35dcf58cf6f95435b3ae91:
>
> Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20170613' into staging (2017-06
Le 15/06/2017 à 17:15, Edgar E. Iglesias a écrit :
On Thu, Jun 15, 2017 at 04:04:56PM +0100, Peter Maydell wrote:
On 15 June 2017 at 15:57, Edgar E. Iglesias wrote:
On Thu, Jun 15, 2017 at 03:40:40PM +0100, Peter Maydell wrote:
Unfortunately we make no guarantees at all about migration orde
On Tue, Feb 28, 2017 at 11:03:01AM +0100, fred.kon...@greensocs.com wrote:
> From: KONRAD Frederic
>
> This adds the qemu-clock documentation.
Hi Fred
>
> Signed-off-by: KONRAD Frederic
>
> V1 -> V2:
> * Fixed in accordance with the changes in the previous patches.
> ---
> docs/clock.tx
On 06/15/2017 02:02 AM, Thomas Huth wrote:
On 15.06.2017 07:53, Richard Henderson wrote:
Signed-off-by: Richard Henderson
---
target/s390x/cpu_models.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
index c3a4ce6..703feca 100644
-
On Thu, Jun 15, 2017 at 03:27:28PM +0200, Igor Mammedov wrote:
> On Thu, 15 Jun 2017 15:41:08 +0300
> Roman Kagan wrote:
> > On Wed, Jun 14, 2017 at 03:00:27PM +0200, Igor Mammedov wrote:
> > > On Wed, 14 Jun 2017 13:26:44 +0200
> > > Paolo Bonzini wrote:
> > >
> > > > On 14/06/2017 13:25, Rom
On 06/15/2017 11:28 AM, Dr. David Alan Gilbert wrote:
> Hi,
> Peter noticed that there were some hangs in the ahci-test;
> I can reproduce them on my laptop as long as the laptop has
> some other load on it (a few md5sum /dev/zero's help).
>
> /x86_64/ahci/flush/migrate: qemu-system-x86_64: Fa
Need to mark copied pages as closer as possible to the place where it
tracks down. That will be necessary in futher patch.
Reviewed-by: Juan Quintela
Signed-off-by: Alexey Perevalov
---
migration/postcopy-ram.c | 13 -
migration/postcopy-ram.h | 4 ++--
migration/ram.c |
Just for placing auxilary operations inside helper,
auxilary operations like: track received pages,
notify about copying operation in futher patches.
Signed-off-by: Alexey Perevalov
---
migration/postcopy-ram.c | 35 ++-
1 file changed, 22 insertions(+), 13 deleti
This is second version of
[PATCH v1 0/2] Add bitmap for copied pages in postcopy migration
cover message from there
This is a separate patch set, it derived from
https://www.mail-archive.com/qemu-devel@nongnu.org/msg456004.html
There are several possible use cases:
1. solve issue with postcopy li
This series extends qemu-iotests 068 to also run with iothread enabled. Doing
so was harder than expected because:
1. ioeventfd is disabled without -M accel=kvm even though it should work
2. loadvm still has an iothread bug
Instead of adding a ./check -iothread option I decided to always run the
Avoid duplicating the QEMU command-line.
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/068 | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/tests/qemu-iotests/068 b/tests/qemu-iotests/068
index 9c1687d..653e23c 100755
--- a/tests/qemu-iotests/068
+++ b/te
This patch adds ability to track down already received
pages, it's necessary for calculation vCPU block time in
postcopy migration feature, maybe for restore after
postcopy migration failure.
Also it's necessary to solve shared memory issue in
postcopy livemigration. Information about received page
migration_incoming_state_destroy() uses qemu_fclose() on the vmstate
file. Make sure to call it inside an AioContext acquire/release region.
This fixes an 'qemu: qemu_mutex_unlock: Operation not permitted' abort
in loadvm.
This patch closes the vmstate file before ending the drained region.
Prev
Old kvm.ko versions only supported a tiny number of ioeventfds so
virtio-pci avoids ioeventfds when kvm_has_many_ioeventfds() returns 0.
Do not check kvm_has_many_ioeventfds() when KVM is disabled since it
always returns 0. Since commit 8c56c1a592b5092d91da8d8943c1d6462a6f
("memory: emulate i
The legacy -hda option does not support -drive/-device parameters. They
will be required by the next patch that extends this test case.
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/068 | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/068 b/te
Perform the savevm/loadvm test with both iothread on and off. This
covers the recently found savevm/loadvm hang when iothread is enabled.
Signed-off-by: Stefan Hajnoczi
---
tests/qemu-iotests/068 | 23 ++-
tests/qemu-iotests/068.out | 11 ++-
2 files changed, 24
On Thu, Jun 15, 2017 at 5:38 PM, Stefan Hajnoczi wrote:
> This series extends qemu-iotests 068 to also run with iothread enabled.
I forgot to mention: this series is based on Kevin's 'block' branch:
git://repo.or.cz/qemu/kevin.git block
This is necessary in order to get the "[PATCH v3 0/4] bl
On 14/06/2017 09:55, Peter Xu wrote:
> 0425dc9 is actually v1 of that patch, but it was accidentally
> merged (while there was a v2). That will cause problem when we try to
> migrate to some old QEMUs when return path is not really there. Let's
> fix it, then squashing this patch with 0425dc9 will
On 08/06/2017 07:09, David Gibson wrote:
> This fourth isntallment of cleanups to the DRC code introduces the
> first changes to the fundamental state handling. We change the
> initial states in the reset code and attach code for PCI devices, and
> are able to remove the 'signalled' state variable
Yes, Thomas, this patch fixes the issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1694998
Title:
PPC: msgsnd instruction leads to assertion
Status in QEMU:
New
Bug description:
I tried t
On Mon, Jun 12, 2017 at 17:53:47 +0300, Lluís Vilanova wrote:
> This series proposes a generic (target-agnostic) instruction translation
> framework.
>
> It basically provides a generic main loop for instruction disassembly, which
> calls target-specific functions when necessary. This generalizati
On 06/15/2017 06:15 AM, Peter Maydell wrote:
> On 14 June 2017 at 11:55, Antonio Huete Jiménez
> wrote:
>> According to 2.9 changelog page, DragonFly BSD will be listed as unsupported
>> with the possibility of dropping support completely in the future:
>>
>> http://wiki.qemu.org/ChangeLog/2.9
>
It turns out that SPARC hosts impose a requirement that
if you mmap MAP_SHARED|MAP_FIXED then the address must be
aligned to SHMLBA alignment, which for SPARC is 16K and
larger than the 8K page size:
http://lxr.linux.no/#linux+v4.10.1/arch/sparc/kernel/sys_sparc_64.c#L158
QEMU doesn't really cope
On 15 June 2017 at 19:09, John Snow wrote:
> Peter, do we have a wiki page detailing what it takes to get an
> operating system considered "supported" with hints and tips for
> prospective maintainers?
We don't, but as you say there aren't that many cases where
it will come up in future, and one
On 06/15/17 20:17, Peter Maydell wrote:
> It turns out that SPARC hosts impose a requirement that
> if you mmap MAP_SHARED|MAP_FIXED then the address must be
> aligned to SHMLBA alignment, which for SPARC is 16K and
> larger than the 8K page size:
> http://lxr.linux.no/#linux+v4.10.1/arch/sparc/ke
When attaching the NBD QIOChannel to an AioContext, the TLS channel should
be used, not the underlying socket channel. This is because, trivially,
the TLS channel will be the one that we read/write to and thus the one
that will get the qio_channel_yield() call.
Fixes: ff82911cd3f69f028f2537825c97
When attaching the NBD QIOChannel to an AioContext, the TLS channel should
be used, not the underlying socket channel. This is because, trivially,
the TLS channel will be the one that we read/write to and thus the one
that will get the qio_channel_yield() call.
Fixes: ff82911cd3f69f028f2537825c97
There are no uses in a Linux system with which to test,
but it Looks Right by my reading of the PoO.
Signed-off-by: Richard Henderson
---
target/s390x/helper.h | 1 +
target/s390x/insn-data.def | 2 +
target/s390x/mem_helper.c | 189 +
target
On 2017-06-14 22:53, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> target/s390x/cpu_models.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> index c3a4ce6..703feca 100644
> --- a/target/s390x/cpu_models.c
>
On 06/15/2017 01:48 AM, Alex Bennée wrote:
Richard Henderson writes:
Signed-off-by: Richard Henderson
---
target/alpha/translate.c | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/target/alpha/translate.c b/target/alpha/translate.c
index 7c4
On 2017-06-15 15:10, David Hildenbrand wrote:
>
> >> A "sane" guest (e.g. Linux) will only use an instruction if the
> >> corresponding stfl(e) bit is set. So in my opinion, this should be just
> >> fine. If the bit is not set currently, the guest will not use it == dead
> >> code.
> >
> > Not ne
On 06/15/2017 01:49 PM, Aurelien Jarno wrote:
+S390_FEAT_FLOATING_POINT_SUPPPORT_ENH,
Theoretically the floating-point-support-enhancement facilities include
the DFP rounding facility. Given We don't implement the DFP facility I
guess this can be ignored.
We *do* implement the one ins
On 2017-06-14 12:48, Richard Henderson wrote:
> From: Paolo Bonzini
>
> Exit to cpu loop so we reevaluate cpu_mips_hw_interrupts.
>
> Cc: Aurelien Jarno
> Cc: Yongbok Kim
> Signed-off-by: Richard Henderson
> ---
> target/mips/translate.c | 6 --
> 1 file changed, 4 insertions(+), 2 delet
On 2017-06-15 14:10, Richard Henderson wrote:
> On 06/15/2017 01:49 PM, Aurelien Jarno wrote:
> > > +S390_FEAT_FLOATING_POINT_SUPPPORT_ENH,
> >
> > Theoretically the floating-point-support-enhancement facilities include
> > the DFP rounding facility. Given We don't implement the DFP facili
On 06/15/2017 02:19 PM, Aurelien Jarno wrote:
While the above looks correct, it's not complete. It only fixes the
microMIPS EI instruction. The MIPS one also has to be fixed.
For what I understood, anything that can change the result of
cpu_mips_hw_interrupts_enabled has to stop the translation.
Peter cleaned that and improved the doc on ARM:
https://patchwork.kernel.org/patch/9690993/
(commit b636649f5a2e108413dd171edaf320f781f57942)
$ git grep -- singlestep_enabled target|wc -l
113
still confusing...
On Thu, Jun 15, 2017 at 5:55 PM, Richard Henderson wrote:
> On 06/15/2017 01:48 AM, A
On Mon, Jun 12, 2017 at 17:54:09 +0300, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova
> ---
> include/exec/gen-icount.h |2
> include/exec/translate-all_template.h | 73
> include/qom/cpu.h | 22
> translate-all_template.h
Some minor nits below.
On Mon, Jun 12, 2017 at 17:54:09 +0300, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova
> ---
> +/**
> + * BreakpointHitType:
> + * @BH_MISS: No hit
> + * @BH_HIT_INSN: Hit, but continue translating instruction
> + * @BH_HIT_TB: Hit, stop translating TB
> + *
> + * Ho
We are relying on cpu_env being defined as a global, yet most
targets (i.e. all but arm/a64) have it defined as a local variable.
Luckily all of them use the same "cpu_env" name, but really
compilation shouldn't break if the name of that local variable
changed.
This patch fixes it by explicitly pa
Signed-off-by: Emilio G. Cota
---
include/exec/gen-icount.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/exec/gen-icount.h b/include/exec/gen-icount.h
index 62d462e..547c979 100644
--- a/include/exec/gen-icount.h
+++ b/include/exec/gen-icount.h
@@ -44,7 +44,7 @@ sta
On Thu, Jun 15, 2017 at 18:19:11 -0400, Emilio G. Cota wrote:
> (snip)
> > +/**
> > + * DisasContextBase:
> > + * @tb: Translation block for this disassembly.
> > + * @pc_first: Address of first guest instruction in this TB.
> > + * @pc_next: Address of next guest instruction in this TB (current du
On Thu, 06/08 19:56, Fam Zheng wrote:
> From: Paolo Bonzini
>
> It protects only the list of dirty bitmaps; in the next patch we will
> also protect their content.
>
> Reviewed-by: Stefan Hajnoczi
> Signed-off-by: Paolo Bonzini
> Message-Id: <20170605123908.18777-15-pbonz...@redhat.com>
> Sign
On Mon, Jun 12, 2017 at 17:54:30 +0300, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova
> ---
> target/arm/translate-a64.c | 346 ++---
> target/arm/translate.c | 720
> ++--
> target/arm/translate.h | 46 ++-
> 3 files ch
On Thu, 06/15 11:08, Mao Zhongyi wrote:
> From: Cao jin
>
> The non-blocking connect mechanism is obsolete, and it doesn't
> work well in inet connection, because it will call getaddrinfo
> first and getaddrinfo will blocks on DNS lookups. Since commit
> e65c67e4 & d984464e, the non-blocking conn
On Wed, 06/14 10:29, Stefan Hajnoczi wrote:
> It is hard to analyze trace logs with multiple virtio-blk devices
> because none of the trace events include the VirtIODevice *vdev.
>
> This patch adds vdev so it's clear which device a request is associated
> with.
>
> I considered using VirtIOBlock
The following changes since commit edf8bc98424d62035d5e4c0f39542722d72d7979:
Merge remote-tracking branch 'remotes/rth/tags/pull-s390-20170613' into
staging (2017-06-15 13:45:15 +0100)
are available in the git repository at:
git://github.com/famz/qemu.git tags/docker-and-block-pull-request
From: Paolo Bonzini
It protects only the list of dirty bitmaps; in the next patch we will
also protect their content.
Reviewed-by: Stefan Hajnoczi
Signed-off-by: Paolo Bonzini
Message-Id: <20170605123908.18777-15-pbonz...@redhat.com>
Signed-off-by: Fam Zheng
---
block.c |
On Thu, Jun 15, 2017 at 09:32:38AM +0200, Greg Kurz wrote:
> On Thu, 15 Jun 2017 08:22:44 +0530
> Bharata B Rao wrote:
>
> > ICPState objects were being allocated before CPU thread realization.
> > However commit 9ed656631d73 (xics: setup cpu at realize time) reversed it
> > by allocating ICPStat
On 2017年06月15日 16:10, Zhang Chen wrote:
On 06/15/2017 12:31 PM, Jason Wang wrote:
On 2017年06月14日 16:04, Zhang Chen wrote:
On 06/13/2017 05:14 PM, Jason Wang wrote:
On 2017年06月12日 17:27, Zhang Chen wrote:
+if (nf->direction == NET_FILTER_DIRECTION_RX ||
+nf->dir
On 06/15/2017 04:04 PM, Emilio G. Cota wrote:
We are relying on cpu_env being defined as a global, yet most
targets (i.e. all but arm/a64) have it defined as a local variable.
Luckily all of them use the same "cpu_env" name, but really
compilation shouldn't break if the name of that local variabl
On 06/15/2017 04:04 PM, Emilio G. Cota wrote:
Signed-off-by: Emilio G. Cota
---
include/exec/gen-icount.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Richard Henderson
r~
On 06/15/2017 02:57 PM, Philippe Mathieu-Daudé wrote:
Peter cleaned that and improved the doc on ARM:
https://patchwork.kernel.org/patch/9690993/
(commit b636649f5a2e108413dd171edaf320f781f57942)
$ git grep -- singlestep_enabled target|wc -l
113
still confusing...
This is two of the three sing
On Thu, Jun 15, 2017 at 04:10:17PM +0800, Wei Wang wrote:
> On 06/14/2017 01:56 AM, Michael S. Tsirkin wrote:
> > On Fri, Jun 09, 2017 at 06:41:38PM +0800, Wei Wang wrote:
> > > Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables
> > > the transfer of the ballooned (i.e. inflated/deflate
On Thu, Jun 15, 2017 at 02:52:01PM +0800, Wei Wang wrote:
> On 06/15/2017 12:16 PM, Jason Wang wrote:
> >
> >
> > On 2017年06月14日 23:22, Michael S. Tsirkin wrote:
> > > On Wed, Jun 14, 2017 at 07:26:54PM +0800, Jason Wang wrote:
> > > >
> > > > On 2017年06月13日 18:46, Jason Wang wrote:
> > > > >
>
On Thu, Jun 15, 2017 at 09:07:45AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > To be specific, what I meant is a bit that tells guest that a
> > config space register is available, and lets host find out
> > that guest is going to use it.
> >
> > This to ensure full forward and backward compatibili
On Thu, Jun 15, 2017 at 05:38:09PM +0100, Stefan Hajnoczi wrote:
> Old kvm.ko versions only supported a tiny number of ioeventfds so
> virtio-pci avoids ioeventfds when kvm_has_many_ioeventfds() returns 0.
>
> Do not check kvm_has_many_ioeventfds() when KVM is disabled since it
> always returns 0.
On Thu, Jun 15, 2017 at 07:10:55PM +0200, Laurent Vivier wrote:
> On 08/06/2017 07:09, David Gibson wrote:
> > This fourth isntallment of cleanups to the DRC code introduces the
> > first changes to the fundamental state handling. We change the
> > initial states in the reset code and attach code
Introduce a synthetic feature (type MISC) to handle disabling of
the enforcing of features at translation time.
Signed-off-by: Richard Henderson
---
target/s390x/cpu_features.c | 4 +++-
target/s390x/cpu_features_def.h | 1 +
target/s390x/cpu_models.c | 5 +
target/s390x/translate.
On 06/16/2017 08:21 AM, Fam Zheng wrote:
On Thu, 06/15 11:08, Mao Zhongyi wrote:
From: Cao jin
The non-blocking connect mechanism is obsolete, and it doesn't
work well in inet connection, because it will call getaddrinfo
first and getaddrinfo will blocks on DNS lookups. Since commit
e65c67e4
Hi,
On Wed, Jun 14, 2017 at 11:56 PM, Fernando Casas Schössow
wrote:
> Hi there,
>
> I recently migrated a Hyper-V host to qemu/kvm runing on Alpine Linux 3.6.1
> (kernel 4.9.30 -with grsec patches- and qemu 2.8.1).
>
> Almost on daily basis at least one of the guests is showing the following
>
101 - 162 of 162 matches
Mail list logo
