[Qemu-devel] [Bug 1740364] [NEW] qemu-img: fails to get shared 'write' lock

Public bug reported: Description of problem: Somewhere in F27 (did not see it happening before), I'm getting while running libguestfs (via libvirt or direct), a qemu-img failure. Note: multiple qcow2 snapshots are on the same backing file, and a parallel libguestfs command is running on all.

[Qemu-devel] [PATCH 2/3] chardev: let g_idle_add() be with chardev gcontext

The idle task will be attached to main gcontext even if the chardev backend is running in another gcontext. Fix the only caller by extending the g_idle_add() logic into the more powerful g_source_attach(). It's basically g_idle_add_full() implementation, but with the chardev's gcontext passed

[Qemu-devel] [PATCH 1/3] chardev: use backend chr context when watch for fe

In commit 6bbb6c0644 ("chardev: use per-dev context for io_add_watch_poll", 2017-09-22) all the chardev watches are converted to use per-chardev gcontext to support chardev to be run outside default main thread. However that's still missing one call from the frontend code. Touch that up.

[Qemu-devel] [PATCH 3/3] chardev: introduce qemu_chr_timeout_add() and use

It's a replacement of g_timeout_add[_seconds]() for chardevs. Chardevs now can have dedicated gcontext, we should always bind chardev tasks onto those gcontext rather than the default main context. Since there are quite a few of g_timeout_add[_seconds]() callers, a new function

[Qemu-devel] [PATCH 0/3] chardev: convert leftover glib APIs to use dedicate gcontext

There were existing work that tried to allow chardev to be run in a dedicated gcontext rather than the default main context/thread. Basically that work passed in the correct gcontext during g_source_attach(). However, I found something missing along the way, that some legacy glib APIs are used by

Re: [Qemu-devel] [PATCH v9 13/13] iotests: add dirty bitmap postcopy test

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Test > - start two vms (vm_a, vm_b) > > - in a > - do writes from set A > - do writes from set B > - fix bitmap sha256 > - clear bitmap > - do writes from set A > - start migration > - than, in b > - wait vm

Re: [Qemu-devel] [PATCH v9 12/13] iotests: add dirty bitmap migration test

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > +def inject_test_case(klass, name, method, *args, **kwargs): > +mc = operator.methodcaller(method, *args, **kwargs) > +setattr(klass, 'test_' + name, new.instancemethod(mc, None, klass)) > + > + > +for cmb in

Re: [Qemu-devel] [PATCH v9 11/13] iotests: add default node-name

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > When testing migration, auto-generated by qemu node-names differs in > source and destination qemu and migration fails. After this patch, > auto-generated by iotest nodenames will be the same. > > Signed-off-by: Vladimir

Re: [Qemu-devel] [PATCH v9 10/13] migration: add postcopy migration of dirty bitmaps

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Postcopy migration of dirty bitmaps. Only named dirty bitmaps, > associated with root nodes and non-root named nodes are migrated. > > If destination qemu is already containing a dirty bitmap with the same name > as a migrated bitmap (for

Re: [Qemu-devel] [PATCH v9 09/13] migration: add is_active_iterate handler

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Only-postcopy savevm states (dirty-bitmap) don't need live iteration, so > to disable them and stop transporting empty sections there is a new > savevm handler. > > Signed-off-by: Vladimir Sementsov-Ogievskiy >

Re: [Qemu-devel] [PATCH v9 08/13] migration/qemu-file: add qemu_put_counted_string()

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Add function opposite to qemu_get_counted_string. > qemu_put_counted_string puts one-byte length of the string (string > should not be longer than 255 characters), and then it puts the string, > without last zero byte. > > Signed-off-by:

Re: [Qemu-devel] [PATCH v9 07/13] migration: include migrate_dirty_bitmaps in migrate_postcopy

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Enable postcopy if dirty bitmap migration is enabled. > > Signed-off-by: Vladimir Sementsov-Ogievskiy > Reviewed-by: Juan Quintela > Reviewed-by: John Snow > --- >

Re: [Qemu-devel] [PATCH v9 06/13] qapi: add dirty-bitmaps migration capability

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Signed-off-by: Vladimir Sementsov-Ogievskiy > Reviewed-by: John Snow > Reviewed-by: Eric Blake > Reviewed-by: Juan Quintela > --- >

[Qemu-devel] [PATCH v14 2/9] ACPI: Add APEI GHES table generation and CPER record support

This implements APEI GHES Table generation and record CPER in runtime via fw_cfg blobs.Now we only support two types of GHESv2, which are GPIO-Signal and ARMv8 SEA. Afterwards, we can extend the supported type if needed. For the CPER section type, currently it is memory section because kernel

[Qemu-devel] [PATCH v14 3/9] docs: APEI GHES generation and CPER record description

Add APEI/GHES detailed design document Signed-off-by: Dongjiu Geng --- Address Igor's comments to add a doc --- docs/specs/acpi_hest_ghes.txt | 97 +++ 1 file changed, 97 insertions(+) create mode 100644

Re: [Qemu-devel] [PATCH v9 04/13] dirty-bitmap: add locked state

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c > index fe27ddfb83..6218740c95 100644 > --- a/block/dirty-bitmap.c > +++ b/block/dirty-bitmap.c > @@ -40,6 +40,8 @@ struct BdrvDirtyBitmap { > QemuMutex *mutex; > HBitmap

[Qemu-devel] [PATCH v14 0/9] Add ARMv8 RAS virtualization support in QEMU

From: gengdongjiu In the ARMv8 platform, the CPU error type are synchronous external abort(SEA) and SError Interrupt (SEI). If exception happens to guest, sometimes guest itself do the recovery is better, because host does not know guest's detailed information. For

[Qemu-devel] [PATCH v14 1/9] ACPI: add some GHES structures and macros definition

Add Generic Error Status Block structures and some macros definitions, which is referred to the ACPI 4.0 or ACPI 6.1. The HEST table generation and CPER record will use them. Signed-off-by: Dongjiu Geng --- Change since v13: 1. Clean the new added structures and macros

[Qemu-devel] [PATCH v14 8/9] hw/arm/virt: Add RAS platform version for migration

Support this feature since version 2.10, disable it by default in the old version. Signed-off-by: Dongjiu Geng --- Address Shannon's comments to add platform version in [1]. [1]: https://lkml.org/lkml/2017/8/25/821 Signed-off-by: Dongjiu Geng

[Qemu-devel] [PATCH v14 6/9] Move related hwpoison page functions to accel/kvm/ folder

kvm_hwpoison_page_add() and kvm_unpoison_all() will be used both by X86 and ARM platforms, so move these functions to a common accel/kvm/ folder to avoid duplicate code. Signed-off-by: Dongjiu Geng --- Address Peter's comments to move related hwpoison page function to

[Qemu-devel] [PATCH v14 5/9] target-arm: kvm64: inject synchronous External Abort

Add synchronous external abort injection logic, setup exception type and syndrome value. When switch to guest, guest will jump to the synchronous external abort vector table entry. The ESR_ELx.DFSC is set to synchronous external abort(0x10), and ESR_ELx.FnV is set to not valid(0x1), which will

[Qemu-devel] [PATCH v14 9/9] target-arm: kvm64: handle SIGBUS signal from kernel or KVM

Add SIGBUS signal handler. In this handler, it checks the SIGBUS type, translates the host VA which is delivered by host to guest PA, then fill this PA to CPER and fill the CPER to guest APEI GHES memory, finally notify guest according to the SIGBUS type. There are two kinds of SIGBUS that QEMU

[Qemu-devel] [PATCH v14 7/9] ARM: ACPI: Add GPIO notification type for hardware RAS error

In ARM platform we implements a notification of error events via a GPIO pin. For this GPIO-signaled events, we choose GPIO pin 4 for hardware error device (PNP0C33), So _E04 should be added to ACPI DSDT table. When GPIO-pin 4 signaled a events, the guest ACPI driver will receive this notification

[Qemu-devel] [PATCH v14 4/9] ACPI: enable APEI GHES in the configure file

Add CONFIG_ACPI_APEI configuration in the arm-softmmu.mak and add build choice in the Makefile.objs. Signed-off-by: Dongjiu Geng --- default-configs/arm-softmmu.mak | 1 + hw/acpi/Makefile.objs | 1 + 2 files changed, 2 insertions(+) diff --git

Re: [Qemu-devel] [PATCH v9 03/13] block/dirty-bitmap: add _locked version of bdrv_reclaim_dirty_bitmap

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Signed-off-by: Vladimir Sementsov-Ogievskiy > --- > include/block/dirty-bitmap.h | 3 +++ > block/dirty-bitmap.c | 25 - > 2 files changed, 19 insertions(+), 9 deletions(-) > >

Re: [Qemu-devel] [PATCH v9 02/13] block/dirty-bitmap: fix locking in bdrv_reclaim_dirty_bitmap

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Like other setters here these functions should take a lock. > > Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Fam Zheng

Re: [Qemu-devel] [PATCH v9 01/13] block/dirty-bitmap: add bdrv_dirty_bitmap_enable_successor()

On Wed, 12/20 18:49, Vladimir Sementsov-Ogievskiy wrote: > Enabling bitmap successor is necessary to enable successors of bitmaps > being migrated before target vm start. > > Signed-off-by: Vladimir Sementsov-Ogievskiy > Reviewed-by: John Snow > --- >

[Qemu-devel] [Bug 1239008] Re: qemu fails to scroll screen on ^Vidmem output

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) 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/1239008

[Qemu-devel] [Bug 1272796] Re: Windows 98 First Edition emulation problems

[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/1272796 Title: Windows 98

[Qemu-devel] [Bug 1276879] Re: lots of dma command 10, 14 not supported

[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/1276879 Title: lots of

[Qemu-devel] [Bug 1292037] Re: Solaris 10 x86 guest crashes qemu with -icount 1 option

[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/1292037 Title: Solaris 10

[Qemu-devel] [Bug 1007490] Re: Missing binfmt string for init script.

[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/1007490 Title: Missing

[Qemu-devel] [Bug 1332297] Re: qemu-img: crash on check of an image with large value in the 'size' header field

[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/1332297 Title: qemu-img:

[Qemu-devel] [Bug 1239008] Re: qemu fails to scroll screen on ^Vidmem output

[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/1239008 Title: qemu fails

[Qemu-devel] [Bug 1336123] Re: bad switch, segfault in hw/pci-host/bonito.c bonito_readl

[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/1336123 Title: bad

[Qemu-devel] [Bug 1279500] Re: system_powerdown causes SMP OpenBSD guest to freeze

[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/1279500 Title:

[Qemu-devel] [Bug 1247478] Re: usb passthrough mass storage write data corruption

[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/1247478 Title: usb

[Qemu-devel] [Bug 1297781] Re: Network device cannot communicate with host machine

[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/1297781 Title: Network

[Qemu-devel] [Bug 1358287] Re: -readconfig file doesn't interpret memory size correctly

[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/1358287 Title:

Re: [Qemu-devel] [PATCH 05/17] timer: generalize Dallas/Maxim RTC i2c devices

On 12/06/2017 05:14 AM, David Gibson wrote: > On Sun, Dec 03, 2017 at 03:15:10PM -0600, Michael Davidsaver wrote: >> On 11/29/2017 11:13 PM, David Gibson wrote: >>> On Sun, Nov 26, 2017 at 03:59:03PM -0600, Michael Davidsaver wrote: Support for: ds1307, ds1337, ds1338, ds1339, ds1340,

Re: [Qemu-devel] [PATCH] migration: fix small leaks

On Wed, Dec 27, 2017 at 03:25:23PM +0300, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > Hmm, looks like leak is not fixed here: I've checked it while running iotest > 181, that > migration_instance_finalize is not called. > > If I understand correct, to call it we need unref

[Qemu-devel] [PATCH v3] Virt: ACPI: fix qemu assert due to re-assigned table data address

From: Zhaoshenglong acpi_data_push uses g_array_set_size to resize the memory size. If there is no enough contiguous memory, the address will be changed. If we use the old value, it will assert. qemu-kvm: hw/acpi/bios-linker-loader.c:214:

[Qemu-devel] [PATCH] Update dtc to fix compilation problem on Mac OS 10.6

Currently QEMU does not build on Mac OS 10.6 because of a missing patch in the dtc subproject. Updating dtc to make the patch available fixes this problem. Signed-off-by: John Arbuckle --- dtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dtc

Re: [Qemu-devel] [PATCH v7 08/26] tcg/i386: Add vector operations

On 12/27/2017 07:31 AM, Kirill Batuzov wrote: > I think something is wrong with instruction encodings here. Looks like > tcg_out_mov(_ctx, TCG_TYPE_I64, TCG_REG_EBP, TCG_REG_XMM0) > produces > vmovq %xmm5, %rax > instead. Bah. The operands are swapped -- ebp == 5 and eax == 0. r~

Re: [Qemu-devel] [PATCH] migration: Guard ram_bytes_remaining against early call

"Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Calling ram_bytes_remaining during the early part of setup is unsafe > because the ram_state isn't yet initialised. > > This can happen in the sequence: >migrate >

Re: [Qemu-devel] qemu 2.9.0 qcow2 file failed to open after hard server reset

2017-12-22 1:58 GMT+03:00 John Snow : > > > On 12/21/2017 05:13 PM, Vasiliy Tolstov wrote: >> Hi! Today my server have forced reboot and one of my vm can't start >> with message: >> qcow2: Marking image as corrupt: L2 table offset 0x3f786d6c207600 >> unaligned (L1 index: 0);

Re: [Qemu-devel] qemu 2.9.0 qcow2 file failed to open after hard server reset

2017-12-22 12:23 GMT+03:00 Daniel P. Berrange : > On Thu, Dec 21, 2017 at 05:58:47PM -0500, John Snow wrote: >> >> >> On 12/21/2017 05:13 PM, Vasiliy Tolstov wrote: >> > Hi! Today my server have forced reboot and one of my vm can't start >> > with message: >> > qcow2: Marking

Re: [Qemu-devel] [PATCH net-next v2 1/3] virtio_net: propagate linkspeed/duplex settings from the hypervisor

From: Jason Baron Date: Fri, 22 Dec 2017 16:54:01 -0500 > The ability to set speed and duplex for virtio_net in useful in various > scenarios as described here: > > 16032be virtio_net: add ethtool support for set and get of settings > > However, it would be nice to be able

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

I found Adam's patch from Fedora Rawhide (https://src.fedoraproject.org/rpms/qemu/c/f81be8f0261cce74799f946e99f23d57f8db7e17?branch=master) when applied to openSUSE's 2.11.0 QEMU effective in openQA as well as manually with vncviewer. -- You received this bug notification because you are a

[Qemu-devel] [PATCH 00/16] target/xtensa updates

-xtensa.git tags/20171227-xtensa for you to fetch changes up to d462b6b6b79f092327927b3fb3ac20505c90a706: target/xtensa: implement disassembler (2017-12-18 21:26:20 -0800) target/xtensa updates: - add libisa to the xtensa target

Re: [Qemu-devel] [PATCH] i386/cpu/kvm: look at PMU's CPUID before setting MSRs

On Wed, Dec 27, 2017 at 05:04:26PM +0300, Jan Dakinevich wrote: > Certain PMU-related MSRs are not supported for CPUs with PMU > architecture below version 2. KVM rejects any access to them (see > intel_is_valid_msr_idx routine in KVM), and QEMU fails on the following > assertion: > >

Re: [Qemu-devel] [PATCH v7 08/26] tcg/i386: Add vector operations

On Mon, 18 Dec 2017, Richard Henderson wrote: > The x86 vector instruction set is extremely irregular. With newer > editions, Intel has filled in some of the blanks. However, we don't > get many 64-bit operations until SSE4.2, introduced in 2009. > > The subsequent edition was for AVX1,

Re: [Qemu-devel] [PATCH v7 02/26] tcg: Add generic vector expanders

On Mon, 18 Dec 2017, Richard Henderson wrote: > Signed-off-by: Richard Henderson > --- > Makefile.target |2 +- > accel/tcg/tcg-runtime.h | 29 ++ > tcg/tcg-gvec-desc.h | 49 ++ > tcg/tcg-op-gvec.h| 152 ++ >

Re: [Qemu-devel] [PATCH v3 00/13] tpm: Extend TPM with state migration support (not 2.11)

On 12/22/2017 11:13 AM, Marc-André Lureau wrote: Hi On Fri, Dec 22, 2017 at 4:59 PM, Stefan Berger wrote: On 12/22/2017 07:49 AM, Marc-André Lureau wrote: Hi On Fri, Nov 10, 2017 at 3:11 PM, Stefan Berger wrote: This set of patches

Re: [Qemu-devel] [PATCH v3 10/13] tpm: Introduce condition in TPM backend for notification

On 11/10/2017 09:11 AM, Stefan Berger wrote: TPM backends will suspend independently of the frontends. Also here we need to be able to wait for the TPM command to have been completely processed. Signed-off-by: Stefan Berger --- backends/tpm.c | 19

Re: [Qemu-devel] [PATCH v3 09/13] tpm: Introduce condition to notify waiters of completed command

On 12/22/2017 08:24 AM, Marc-André Lureau wrote: On Fri, Nov 10, 2017 at 3:11 PM, Stefan Berger wrote: Introduce a lock and a condition to notify anyone waiting for the completion of the execution of a TPM command by the backend (thread). The backend uses the

Re: [Qemu-devel] [PATCH v5 3/7] vhost: Simplify ring verification checks

On Mon, 18 Dec 2017 20:13:36 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > vhost_verify_ring_mappings() were used to verify that > rings are still accessible and related memory hasn't > been moved after flatview is

[Qemu-devel] [PATCH] i386/cpu/kvm: look at PMU's CPUID before setting MSRs

Certain PMU-related MSRs are not supported for CPUs with PMU architecture below version 2. KVM rejects any access to them (see intel_is_valid_msr_idx routine in KVM), and QEMU fails on the following assertion: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. QEMU also could

Re: [Qemu-devel] [PATCH v5 0/7] Rework vhost memory region updates

On Mon, 18 Dec 2017 20:13:33 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Hi, > This patch set reworks the way the vhost code handles changes in > physical address space layout that came from a discussion with

[Qemu-devel] [Bug 1740219] [NEW] static linux-user emulation has several-second startup time

Public bug reported: static linux-user emulation has several-second startup time My problem: I'm a Parabola packager, and I'm updating our qemu-user-static package from 2.8 to 2.11. With my new statically-linked 2.11, running `qemu-arm /my/arm-chroot/bin/true` went from taking 0.006s to 3s!

[Qemu-devel] [Bug 1740219] Re: static linux-user emulation has several-second startup time

Actually, it seems that the `[base+0x, base+0x+page_size]` segment is only mapped on 32-bit ARM. So this is 32-bit ARM-specific. ** Tags added: arm linux-user ** Summary changed: - static linux-user emulation has several-second startup time + static linux-user ARM emulation has

Re: [Qemu-devel] [PATCH v5 7/7] vhost: Merge and delete unused callbacks

On Mon, 18 Dec 2017 20:13:40 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Now that the olf vhost_set_memory code is gone, the _nop and _add > callbacks are identical and can be merged. The _del callback is > no

Re: [Qemu-devel] [PATCH v5 5/7] vhost: Regenerate region list from changed sections list

On Mon, 18 Dec 2017 20:13:38 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Compare the sections list that's just been generated, and if it's > different from the old one regenerate the region list. > > Signed-off-by:

Re: [Qemu-devel] [PATCH v5 4/7] vhost: Merge sections added to temporary list

On Mon, 18 Dec 2017 20:13:37 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > As sections are reported by the listener to the _nop and _add > methods, add them to the temporary section list but now merge them > with the

Re: [Qemu-devel] [PATCH] migration: fix small leaks

Hi all! Hmm, looks like leak is not fixed here: I've checked it while running iotest 181, that migration_instance_finalize is not called. If I understand correct, to call it we need unref current_migration object somewhere. Or, may be I'm missing something.. 01.08.2017 19:04, Marc-André

Re: [Qemu-devel] [PATCH v5 3/7] vhost: Simplify ring verification checks

On Mon, 18 Dec 2017 20:13:36 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > vhost_verify_ring_mappings() were used to verify that > rings are still accessible and related memory hasn't > been moved after flatview is

Re: [Qemu-devel] [PATCH v4 1/6] vhost: Move log_dirty check

On Thu, 14 Dec 2017 15:20:10 + "Dr. David Alan Gilbert" wrote: > * Igor Mammedov (imamm...@redhat.com) wrote: > > On Wed, 13 Dec 2017 18:08:02 + > > "Dr. David Alan Gilbert (git)" wrote: > > > > > From: "Dr. David Alan Gilbert"

Re: [Qemu-devel] [PATCH v5 1/7] vhost: Build temporary section list and deref after commit

On Mon, 18 Dec 2017 20:13:34 + "Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Igor spotted that there's a race, where a region that's unref'd > in a _del callback might be free'd before the set_mem_table call in > the

Re: [Qemu-devel] [RESEND PATCH for-2.12 1/2] ACPI/unit-test: Add a testcase for RAM allocation in numa node

On Thu, 14 Dec 2017 12:08:54 +0800 Dou Liyang wrote: > As QEMU supports the memory-less node, it is possible that there is > no RAM in the first numa node(also be called as node0). eg: > ... \ > -m 128,slots=3,maxmem=1G \ > -numa node -numa node,mem=128M \ > >

Re: [Qemu-devel] [RESEND PATCH for-2.12 2/2] hw/acpi-build: Make next_base easy to follow

On Thu, 14 Dec 2017 12:08:55 +0800 Dou Liyang wrote: > It may be hard to read the assignment statement of "next_base", so > > S/next_base += (1ULL << 32) - pcms->below_4g_mem_size; > /next_base = mem_base + mem_len; > > ... for readability. > > No functionality

Re: [Qemu-devel] [PATCH v3 2/6] tests: migration test deprecated commands

On Wed, Dec 27, 2017 at 10:41:02AM +0100, Juan Quintela wrote: > Peter Xu wrote: > > On Tue, Dec 26, 2017 at 08:51:10PM +0100, Juan Quintela wrote: > >> Peter Xu wrote: > >> > On Fri, Dec 01, 2017 at 01:58:09PM +0100, Juan Quintela wrote: > >> >> We now test

Re: [Qemu-devel] [PATCH v3 2/6] tests: migration test deprecated commands

Peter Xu wrote: > On Tue, Dec 26, 2017 at 08:51:10PM +0100, Juan Quintela wrote: >> Peter Xu wrote: >> > On Fri, Dec 01, 2017 at 01:58:09PM +0100, Juan Quintela wrote: >> >> We now test the deprecated commands everytime that we test the new >> >> commands.

Re: [Qemu-devel] [PATCH v4] Add ability for user to specify mouse ungrab key

Hi, This series failed build test on s390x host. Please find the details below. Type: series Message-id: 20171227011428.40996-1-programmingk...@gmail.com Subject: [Qemu-devel] [PATCH v4] Add ability for user to specify mouse ungrab key === TEST SCRIPT BEGIN === #!/bin/bash # Testing script

Re: [Qemu-devel] [PATCH v4] Add ability for user to specify mouse ungrab key

Hi, This series failed automatic 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: 20171227011428.40996-1-programmingk...@gmail.com Subject: [Qemu-devel] [PATCH v4] Add ability for

Re: [Qemu-devel] [PATCH v2] Virt: ACPI: fix qemu assert due to re-assigned table data address

On Wed, Dec 27, 2017 at 04:16:12PM +0800, Shannon Zhao wrote: > From: Zhaoshenglong > > acpi_data_push uses g_array_set_size to resize the memory size. If there > is no enough contiguous memory, the address will be changed. If we use > the old value, it will assert. >

[Qemu-devel] [PATCH v2] Virt: ACPI: fix qemu assert due to re-assigned table data address

From: Zhaoshenglong acpi_data_push uses g_array_set_size to resize the memory size. If there is no enough contiguous memory, the address will be changed. If we use the old value, it will assert. qemu-kvm: hw/acpi/bios-linker-loader.c:214: