[Qemu-devel] [RFC PATCH V4 2/4] vfio: Add vm status change callback to stop/restart the mdev device

VM status change handler is added to change the vfio pci device status during the migration, write the demanded device status to the DEVICE STATUS subregion to stop the device on the source side before fetch its status and start the deivce on the target side after restore its status.

[Qemu-devel] [RFC PATCH V4 3/4] vfio: Add SaveVMHanlders for VFIO device to support live migration

Instead of using vm state description, add SaveVMHandlers for VFIO device to support live migration. Introduce new Ioctl VFIO_DEVICE_GET_DIRTY_BITMAP to fetch the memory bitmap that dirtied by vfio device during the iterative precopy stage to shorten the system downtime afterward. For vfio pci

[Qemu-devel] [RFC V4 PATCH 0/4] vfio: Introduce live migation capability to

Summary This series RFC would like to resume the discussion about how to introduce the live migration capability to vfio mdev device. A new subtype region VFIO_REGION_SUBTYPE_DEVICE_STATE is introduced for vfio device status migrate, during the initialization it will check if the region is

[Qemu-devel] [RFC PATCH V4 1/4] vfio: introduce a new VFIO subregion for mdev device migration support

New VFIO sub region VFIO_REGION_SUBTYPE_DEVICE_STATE is added to fetch and restore the status of mdev device vGPU during the live migration. Signed-off-by: Yulei Zhang --- hw/vfio/pci.c | 25 - hw/vfio/pci.h | 2 ++

[Qemu-devel] [PATCH] configure: don't warn SDL abi if disabled

SDL has the same problem as GTK that we might get warnings on SDL ABI version even if SDL is disabled. Fix that by only probing SDL if SDL is enabled. Also this should let configure be a little bit faster since we don't really need to probe SDL stuff when it's off. CC: Paolo Bonzini

Re: [Qemu-devel] [PATCH] configure: don't warn GTK if disabled

On Mon, Apr 09, 2018 at 07:37:11PM +0200, Paolo Bonzini wrote: > On 09/04/2018 11:24, Peter Maydell wrote: > > On 9 April 2018 at 09:31, Daniel P. Berrangé wrote: > >> Feels to me that since we've deprecated 2.0, we could just *never* auto > >> detect - just do test -z

Re: [Qemu-devel] [PATCH for-2.12 v2] monitor: bind dispatch bh to iohandler context

On Tue, Apr 10, 2018 at 12:49:42PM +0800, Peter Xu wrote: > Eric Auger reported the problem days ago that OOB broke ARM when running > with libvirt: > > http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html > > The problem was that the monitor dispatcher bottom half was bound to >

[Qemu-devel] [PATCH for-2.12 v2] monitor: bind dispatch bh to iohandler context

Eric Auger reported the problem days ago that OOB broke ARM when running with libvirt: http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html The problem was that the monitor dispatcher bottom half was bound to qemu_aio_context now, which could be polled unexpectedly in block code.

[Qemu-devel] [Bug 1211943] Re: #GP and aligned move instruction

[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/1211943 Title: #GP and

[Qemu-devel] [Bug 1196498] Re: Failed to create COM port in Windows Guest VM

[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/1196498 Title: Failed to

[Qemu-devel] [Bug 1354167] Re: On VM restart: Could not open 'poppy.qcow2': Could not read snapshots: File too large

[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/1354167 Title: On VM

[Qemu-devel] [Bug 1225187] Re: qemu hangs in windows 7 host with -serial pipe:windbg

[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/1225187 Title: qemu hangs

[Qemu-devel] [Bug 1343827] Re: block.c: multiwrite_merge() truncates overlapping requests

[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/1343827 Title: block.c:

Re: [Qemu-devel] [PATCH for 2.13 1/2] Revert "spapr: Don't allow memory hotplug to memory less nodes"

On Fri, Apr 06, 2018 at 08:48:55AM +0300, Serhii Popovych wrote: > Bharata B Rao wrote: > > On Thu, Apr 05, 2018 at 10:35:22AM -0400, Serhii Popovych wrote: > >> This reverts commit b556854bd8524c26b8be98ab1bfdf0826831e793. > >> > >> Leave change @node type from uint32_t to to int from reverted

Re: [Qemu-devel] [PATCH for 2.13 2/2] spapr: Add ibm, max-associativity-domains property

On Thu, Apr 05, 2018 at 10:35:23AM -0400, Serhii Popovych wrote: > Now recent kernels (i.e. since linux-stable commit a346137e9142 > ("powerpc/numa: Use ibm,max-associativity-domains to discover possible nodes") > support this property to mark initially memory-less NUMA nodes as "possible" > to

Re: [Qemu-devel] [Qemu-ppc] [PATCH for 2.13 0/2] target/ppc: Support adding memory to initially memory-less NUMA nodes

On Fri, Apr 06, 2018 at 10:21:36AM +0200, Greg Kurz wrote: > On Thu, 5 Apr 2018 10:35:21 -0400 > Serhii Popovych wrote: > > > Now PowerPC Linux kernel supports hot-add to NUMA nodes not populated > > initially with memory we can enable such support in qemu. This requires >

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On 04/10/2018 02:11 AM, Emilio G. Cota wrote: > On Mon, Apr 09, 2018 at 16:01:36 +0200, Bastian Koppelmann wrote: >> Thanks for doing this grunt work. Me and a colleague were planning to do >> this as well after converting the RISC-V frontend to decodetree. Do you >> have any plans to do this for

Re: [Qemu-devel] [PATCH v2 14/17] target/openrisc: convert to TranslatorOps

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Notes: > > - Changed the num_insns test in insn_start to check for > dc->base.num_insns > 1, since when tb_start is first > called in a TB, base.num_insns is already set to 1. > > - Removed DISAS_NEXT from the switch in tb_stop; use >

Re: [Qemu-devel] Crash when running hello-world unikernel for ARM

Following is the gdb details : ## ajay@debian:~/rumprun-arm32$ gdb --args qemu-system-arm -machine virt -nographic -kernel helloer.bin GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software

Re: [Qemu-devel] [RFC PATCH v2] spapr: Support ibm, dynamic-memory-v2 property

On Tue, Apr 10, 2018 at 01:02:45PM +1000, David Gibson wrote: > On Mon, Apr 09, 2018 at 11:55:38AM +0530, Bharata B Rao wrote: > > The new property ibm,dynamic-memory-v2 allows memory to be represented > > in a more compact manner in device tree. > > I still need to look at this in more detail,

Re: [Qemu-devel] Crash when running hello-world unikernel for ARM

Thanks Alex for the reply .. > > Can you run under -s -S and gdb step the *guest* and see where it ends > up. The above error is usually indicative of the guest going off into > the weeds somewhere because the hardware isn't what it expects. > So, after your reply that it might be because of the

Re: [Qemu-devel] [PATCH v2 13/17] target/openrisc: convert to DisasContextBase

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > While at it, set is_jmp to DISAS_NORETURN when generating > an exception. > > Cc: Stafford Horne > Signed-off-by: Emilio G. Cota > --- > target/openrisc/translate.c | 93 >

Re: [Qemu-devel] [PATCH v2 12/17] target/s390x: convert to TranslatorOps

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Note: I looked into dropping dc->do_debug. However, I don't see > an easy way to do it given that TOO_MANY is also valid > when we just translate more than max_insns. Thus, the check > for do_debug in "case DISAS_PC_CC_UPDATED" would still need >

Re: [Qemu-devel] [PATCH v2 11/17] target/s390x: convert to DisasContextBase

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Notes: > > - Did not convert {num,max}_insns and is_jmp, since the corresponding > code will go away in the next patch. > > - Avoided a checkpatch error in use_exit_tb. > > - As suggested by David, (1) Drop ctx.pc and use > ctx.base.pc_next

Re: [Qemu-devel] [PULL 1/1] linux-user: fix preadv/pwritev offsets

On 04/10/2018 01:29 PM, Max Filippov wrote: > On Mon, Apr 9, 2018 at 8:20 PM, Richard Henderson > wrote: >> On 04/10/2018 12:17 PM, Max Filippov wrote: >>> +uint64_t off = tlow | >>> +((unsigned long long)thigh << TARGET_LONG_BITS / 2) << >> >> There's a

Re: [Qemu-devel] [PATCH v2 09/17] target/mips: convert to TranslatorOps

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Notes: > > - DISAS_TOO_MANY replaces the former "break" in the translation loop. > However, care must be taken not to overwrite a previous condition > in is_jmp; that's why in translate_insn we first check is_jmp and > return if it's !=

Re: [Qemu-devel] [PATCH v2 08/17] target/mips: use *ctx for DisasContext

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > No changes to the logic here; this is just to make the diff > that follows easier to read. > > While at it, remove the unnecessary 'struct' in > 'struct TranslationBlock'. > > Note that checkpatch complains with a false positive: > ERROR: space

Re: [Qemu-devel] [PATCH v2 07/17] target/mips: convert to DisasContextBase

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Reviewed-by: Philippe Mathieu-Daudé > Cc: Aurelien Jarno > Cc: Yongbok Kim > Signed-off-by: Emilio G. Cota > --- > target/mips/translate.c | 346 >

Re: [Qemu-devel] [PATCH v2 06/17] target/mips: convert to DisasJumpType

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Reviewed-by: Philippe Mathieu-Daudé > Cc: Aurelien Jarno > Cc: Yongbok Kim > Signed-off-by: Emilio G. Cota > --- > target/mips/translate.c | 186 >

Re: [Qemu-devel] [RFC PATCH 0/8] virtio-net 1.1 userspace backend support

On 2018年04月04日 20:53, w...@redhat.com wrote: From: Wei Xu This is a prototype for virtio-net 1.1 support in userspace backend, only minimum part are included in this RFC(roughly synced to v8 as Jason and Tiwei's RFC). Test has been done together with Tiwei's RFC guest

[Qemu-devel] [PULL 4/6] e1000: Migrate props via a temporary structure

From: "Dr. David Alan Gilbert" Swing the tx.props out via a temporary structure, so in future patches we can select what we're going to send. Signed-off-by: Dr. David Alan Gilbert Signed-off-by: Jason Wang --- hw/net/e1000.c | 27

[Qemu-devel] [PULL 3/6] e1000: wire new subsection to property

From: "Dr. David Alan Gilbert" Wire the new subsection from the previous commit to a property so we can turn it off easily. Signed-off-by: Dr. David Alan Gilbert Signed-off-by: Jason Wang --- hw/net/e1000.c | 12 1

[Qemu-devel] [PULL 6/6] e1000: Old machine types, turn new subsection off

From: "Dr. David Alan Gilbert" Turn the newly added subsection off for old machine types Signed-off-by: Dr. David Alan Gilbert Signed-off-by: Jason Wang --- include/hw/compat.h | 4 1 file changed, 4 insertions(+) diff

[Qemu-devel] [PULL 5/6] e1000: Choose which set of props to migrate

From: "Dr. David Alan Gilbert" When we're using the subsection we migrate both the 'props' and 'tso_props' data; when we're not using the subsection (to migrate to 2.11 or old machine types) we've got to choose what to migrate in the main structure. If we're using the

[Qemu-devel] [PULL 1/6] e1000: Convert v3 fields to subsection

From: "Dr. David Alan Gilbert" A bunch of new TSO fields were introduced by d62644b4 and this bumped the VMState version; however it's easier for those trying to keep backwards migration compatibility if these fields are added in a subsection instead. Move the new fields to

[Qemu-devel] [PULL 2/6] e1000: Dupe offload data on reading old stream

From: "Dr. David Alan Gilbert" Old QEMUs only had one set of offload data; when we only receive one lot, dupe the received data - that should give us about the same bug level as the old version. Signed-off-by: Dr. David Alan Gilbert Signed-off-by:

[Qemu-devel] [PULL 0/6] Net patches

The following changes since commit 915d34c5f99b0ab91517c69f54272bfdb6ca2b32: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2018-04-09 17:29:10 +0100) are available in the git repository at: https://github.com/jasowang/qemu.git tags/net-pull-request for you

Re: [Qemu-devel] [RFC PATCH v2] spapr: Support ibm, dynamic-memory-v2 property

On Mon, Apr 09, 2018 at 11:55:38AM +0530, Bharata B Rao wrote: > The new property ibm,dynamic-memory-v2 allows memory to be represented > in a more compact manner in device tree. I still need to look at this in more detail, but to start with: what's the rationale for this new format? It's more

Re: [Qemu-devel] [PULL 1/1] linux-user: fix preadv/pwritev offsets

On Mon, Apr 9, 2018 at 8:20 PM, Richard Henderson wrote: > On 04/10/2018 12:17 PM, Max Filippov wrote: >> +uint64_t off = tlow | >> +((unsigned long long)thigh << TARGET_LONG_BITS / 2) << > > There's a second instance of long long here; needs uint64_t.

Re: [Qemu-devel] [PATCH v2 05/17] target/sparc: convert to TranslatorOps

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Notes: > > - Moved the cross-page check from the end of translate_insn to > init_disas_context. > > Tested-by: Mark Cave-Ayland > Cc: Mark Cave-Ayland > Cc: Artyom Tarasenko

Re: [Qemu-devel] [PATCH v2 04/17] target/sparc: convert to DisasContextBase

On 04/07/2018 04:19 AM, Emilio G. Cota wrote: > Notes: > > - pc and npc are left unmodified, since they can point to out-of-TB > jump targets. > > - Got rid of last_pc in gen_intermediate_code(), using base.pc_next > instead. Only update pc_next (1) on a breakpoint (so that tb->size >

Re: [Qemu-devel] [PULL 1/1] linux-user: fix preadv/pwritev offsets

On 04/10/2018 12:17 PM, Max Filippov wrote: > +uint64_t off = tlow | > +((unsigned long long)thigh << TARGET_LONG_BITS / 2) << There's a second instance of long long here; needs uint64_t. r~

Re: [Qemu-devel] [PATCH for-2.12] monitor: bind dispatch bh to iohandler context

On Tue, Apr 03, 2018 at 01:01:15PM +0800, Peter Xu wrote: I have changed my mind about this: this patch is necessary. It is needed in QEMU 2.12. > Eric Auger reported the problem days ago that OOB broke ARM when running > with libvirt: > >

Re: [Qemu-devel] [PATCH v8 19/23] SiFive RISC-V UART Device

On Sat, 3 Mar 2018 02:51:47 +1300 Michael Clark wrote: > QEMU model of the UART on the SiFive E300 and U500 series SOCs. > BBL supports the SiFive UART for early console access via the SBI > (Supervisor Binary Interface) and the linux kernel SBI console. > > The SiFive UART

[Qemu-devel] [PULL 0/1] linux-user: fix file offset for preadv/pwritev

at: git://github.com/OSLL/qemu-xtensa.git tags/20180409-xtensa for you to fetch changes up to 9ac225171c9d6b2a1cba35a94ae7eeaa0106cf7d: linux-user: fix preadv/pwritev offsets (2018-04-09 18:57:49 -0700) Fix file offset for preadv

[Qemu-devel] [PULL 1/1] linux-user: fix preadv/pwritev offsets

preadv/pwritev accept low and high parts of file offset in two separate parameters. When host bitness doesn't match guest bitness these parts must be appropriately recombined. Introduce target_to_host_low_high that does this recombination and use it in preadv/pwritev syscalls. This fixes glibc

Re: [Qemu-devel] [PATCH] scripts/qemugdb: support coroutine backtrace in coredumps

On Mon, Apr 09, 2018 at 04:01:24PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 04.04.2018 13:34, Stefan Hajnoczi wrote: > > Use the 'select-frame' GDB command to switch stacks instead of manually > > setting the debugged thread's registers (this only works when debugging > > a live process, not

Re: [Qemu-devel] [PATCH for-2.12 v2] iothread: workaround glib bug which hangs qmp-test

On Mon, Apr 09, 2018 at 04:39:56PM +0800, Peter Xu wrote: > Free the AIO context earlier than the GMainContext (if we have) to > workaround a glib2 bug that GSource context pointer is not cleared even > if the context has already been destroyed (while it should). > > The patch itself only changed

Re: [Qemu-devel] [PATCH v4] linux-user: fix preadv/pwritev offsets

On Mon, Apr 9, 2018 at 5:23 PM, Richard Henderson wrote: > On 04/06/2018 11:36 AM, Max Filippov wrote: >> +static void target_to_host_low_high(abi_ulong tlow, >> +abi_ulong thigh, >> +unsigned

Re: [Qemu-devel] [PATCH v2 17/17] target/riscv: convert to TranslatorOps

On 04/07/2018 04:20 AM, Emilio G. Cota wrote: > +next_page = (ctx->base.pc_first & TARGET_PAGE_MASK) + > TARGET_PAGE_SIZE; > +if (ctx->base.pc_next >= next_page) { This fails for the last page of the address space. Better is page_start = ctx->base.pc_first & TARGET_PAGE_MASK;

Re: [Qemu-devel] [PATCH] migration: calculate expected_downtime with ram_bytes_remaining()

On Mon, 9 Apr 2018 19:57:47 +0100 "Dr. David Alan Gilbert" wrote: > * Balamuruhan S (bal...@linux.vnet.ibm.com) wrote: > > On 2018-04-04 13:36, Peter Xu wrote: > > > On Wed, Apr 04, 2018 at 11:55:14AM +0530, Balamuruhan S wrote: [snip] > > > > > - postcopy: that'll let you

[Qemu-devel] [PATCH for-2.12] make-release: add skiboot .version file

This is needed to build skiboot from tarball-distributed sources since the git data the make_release.sh script relies on to generate it is not available. Cc: qemu-sta...@nongnu.org Reported-by: Michael Tokarev Signed-off-by: Michael Roth ---

Re: [Qemu-devel] [PATCH v2] scsi-disk: Don't enlarge min_io_size to max_io_size

On Mon, 9 Apr 2018 11:28:16 +0200 Paolo Bonzini wrote: > On 09/04/2018 03:08, David Gibson wrote: > [...] > [...] > [...] > [...] > [...] > > Hi David, > > it's already included in my pull request from Friday. And I see it in master now. Thanks! -- David

Re: [Qemu-devel] [PATCH] icount: fix cpu_restore_state_from_tb for non-tb-exit cases

On 04/09/2018 07:13 PM, Pavel Dovgalyuk wrote: > In icount mode instructions, that access io memory spaces in the middle > of the translation blocks, invoke TB recompilation. > After recompilation such instructions become last in the TB and are > allowed to access io memory spaces. > When the code

[Qemu-devel] [PATCH for-2.12] tcg: Introduce tcg_set_insn_start_param

The parameters for tcg_gen_insn_start are target_ulong, which may be split into two TCGArg parameters for storage in the opcode on 32-bit hosts. Fixes the ARM target and its direct use of tcg_set_insn_param, which would set the wrong argument in the 64-on-32 case. Cc: qemu-sta...@nongnu.org

Re: [Qemu-devel] [PATCH v4] linux-user: fix preadv/pwritev offsets

On 04/06/2018 11:36 AM, Max Filippov wrote: > +static void target_to_host_low_high(abi_ulong tlow, > +abi_ulong thigh, > +unsigned long *hlow, > +unsigned long *hhigh) > +{ > +unsigned

Re: [Qemu-devel] qom-test on netbsd can be very slow

On 09.04.2018 22:51, Kamil Rytarowski wrote: > On 09.04.2018 19:10, Peter Maydell wrote: >> My NetBSD build system recently seems to have taken a nosedive >> in how long it takes to finish "make check". This seems to be >> because qom-test (and probably other things where the test interacts >>

[Qemu-devel] [Bug 1762179] Re: Record and replay replay fails with: "ERROR:replay/replay-time.c:49:replay_read_clock: assertion failed"

** Description changed: - QEMU master at 08e173f29461396575c85510eb41474b993cb1fb Ubuntu 17.10 + QEMU master at 915d34c5f99b0ab91517c69f54272bfdb6ca2b32 Ubuntu 17.10 host. QEMU commands: ``` #!/usr/bin/env bash cmd="\ time \ ./x86_64-softmmu/qemu-system-x86_64 \ -append

Re: [Qemu-devel] [PATCH for-2.12] target/arm: Don't corrupt insn_start arguments on 32-bit hosts

On 04/10/2018 08:13 AM, Peter Maydell wrote: > On 9 April 2018 at 23:09, Richard Henderson wrote: >> On 04/09/2018 08:38 PM, Peter Maydell wrote: >>> +#if TARGET_LONG_BITS <= TCG_TARGET_REG_BITS >>> tcg_set_insn_param(s->insn_start, 2, syn); >>> +#else >>> +/*

Re: [Qemu-devel] [PATCH for-2.12] linux-user/signal.c: Ensure AArch64 signal frame isn't too small

On 9 April 2018 at 23:05, Richard Henderson wrote: > On 04/10/2018 12:07 AM, Peter Maydell wrote: >> In particular the dash shell >> would segfault if the frame wasn't as big enough. > > Ah, that was the critical difference in my failure to replicate -- the fedora > sysroot

Re: [Qemu-devel] [PATCH for-2.12] target/arm: Don't corrupt insn_start arguments on 32-bit hosts

On 9 April 2018 at 23:09, Richard Henderson wrote: > On 04/09/2018 08:38 PM, Peter Maydell wrote: >> +#if TARGET_LONG_BITS <= TCG_TARGET_REG_BITS >> tcg_set_insn_param(s->insn_start, 2, syn); >> +#else >> +/* tcg_gen_insn_start has split every target_ulong argument to

Re: [Qemu-devel] [PATCH for-2.12] target/arm: Don't corrupt insn_start arguments on 32-bit hosts

On 04/09/2018 08:38 PM, Peter Maydell wrote: > +#if TARGET_LONG_BITS <= TCG_TARGET_REG_BITS > tcg_set_insn_param(s->insn_start, 2, syn); > +#else > +/* tcg_gen_insn_start has split every target_ulong argument to > + * op_insn_start into two 32-bit arguments, so we want the low > +

Re: [Qemu-devel] [PATCH for-2.12] linux-user/signal.c: Ensure AArch64 signal frame isn't too small

On 04/10/2018 12:07 AM, Peter Maydell wrote: > In particular the dash shell > would segfault if the frame wasn't as big enough. Ah, that was the critical difference in my failure to replicate -- the fedora sysroot doesn't have dash. As you say, the patch matches the kernel so, Reviewed-by:

[Qemu-devel] [Bug 1762558] [NEW] Many crashes with "memslot_get_virt: slot_id 170 too big"-type errors in 2.12.0 rc2

Public bug reported: Since qemu 2.12.0 rc2 - qemu-2.12.0-0.6.rc2.fc29 - landed in Fedora Rawhide, just about all of our openQA-automated tests of Rawhide guests which run with qxl / SPICE graphics in the guest have died partway in, always shortly after the test switches from the installer (an X

Re: [Qemu-devel] qom-test on netbsd can be very slow

On 09.04.2018 19:10, Peter Maydell wrote: > My NetBSD build system recently seems to have taken a nosedive > in how long it takes to finish "make check". This seems to be > because qom-test (and probably other things where the test interacts > with the QEMU process) can run very slowly. > >

Re: [Qemu-devel] [PATCH v5 4/9] i386: Add new property to control cache info

On Mon, Apr 09, 2018 at 07:51:24PM +, Moger, Babu wrote: [...] > > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c > > > index 67faa53..f4fbe3a 100644 > > > --- a/target/i386/cpu.c > > > +++ b/target/i386/cpu.c > > > @@ -5132,6 +5132,7 @@ static Property x86_cpu_properties[] = { > > >

Re: [Qemu-devel] [PATCH v5 4/9] i386: Add new property to control cache info

> -Original Message- > From: Alexandr Iarygin > Sent: Monday, April 9, 2018 12:00 PM > To: Moger, Babu ; m...@redhat.com; > mar...@redhat.com; pbonz...@redhat.com; r...@twiddle.net; > ehabk...@redhat.com; mtosa...@redhat.com > Cc:

Re: [Qemu-devel] [PATCH v5 4/9] i386: Add new property to control cache info

Hello, Babu Moger writes: > This will be used to control the cache information. > By default new information will be displayed. If user > passes "-cpu legacy-cache" then older information will > be displayed even if the hardware supports new information. > > Signed-off-by:

Re: [Qemu-devel] [PATCH v3 00/10] migration: improve and cleanup compression

* Paolo Bonzini (pbonz...@redhat.com) wrote: > On 08/04/2018 05:19, Xiao Guangrong wrote: > > > > Hi Paolo, Michael, Stefan and others, > > > > Could anyone merge this patchset if it is okay to you guys? > > Hi Guangrong, > > Dave and Juan will take care of merging it. However, right now QEMU

Re: [Qemu-devel] [PATCH] migration: calculate expected_downtime with ram_bytes_remaining()

* Balamuruhan S (bal...@linux.vnet.ibm.com) wrote: > On 2018-04-04 13:36, Peter Xu wrote: > > On Wed, Apr 04, 2018 at 11:55:14AM +0530, Balamuruhan S wrote: > > > > [...] > > > > > > too. So still I'll put aside the "which one is better" question. > > > > > > > > For your use case, you can have

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

This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu6 --- qemu (1:2.11+dfsg-1ubuntu6) bionic; urgency=medium * Remove LP: 1752026 changes to d/p/ubuntu/define-ubuntu-machine-types.patch. The Kernel fixes are preferred and already committed to the kernel. Therefore

Re: [Qemu-devel] [Qemu-arm] Use of -machine when running via qemu-system-arm

Thanks a ton Peter, that cleared things up a great deal !!! Thanks again for the quick help !! Thanks and Regards, Ajay On Mon, Apr 9, 2018 at 11:17 PM, Peter Maydell wrote: > On 9 April 2018 at 18:41, Ajay Garg wrote: >> Hi Peter. >> >> The

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/09/18 10:49, Daniel P. Berrangé wrote: > On Sat, Apr 07, 2018 at 02:01:17AM +0200, Laszlo Ersek wrote: >> Add a schema that describes the properties of virtual machine firmware. >> >> Each firmware executable installed on a host system should come with a >> JSON file that conforms to this

Re: [Qemu-devel] [Qemu-arm] Use of -machine when running via qemu-system-arm

On 9 April 2018 at 18:41, Ajay Garg wrote: > Hi Peter. > > The link is pretty good, just that I am a complete noob. > > Maybe a more concrete example on the following, clearly specifying why > things work on x86 without the need of -machine flag, will make things > crystal

Re: [Qemu-devel] [PULL v2 00/20] Miscellaneous patches for QEMU 2.12-rc

On 9 April 2018 at 18:38, Paolo Bonzini wrote: > On 09/04/2018 19:21, Peter Maydell wrote: >> On 9 April 2018 at 15:59, Paolo Bonzini wrote: >>> The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d: >>> >>> Update version for

Re: [Qemu-devel] [Qemu-arm] Use of -machine when running via qemu-system-arm

Hi Peter. The link is pretty good, just that I am a complete noob. Maybe a more concrete example on the following, clearly specifying why things work on x86 without the need of -machine flag, will make things crystal clear : Because ARM systems differ so much and in fundamental ways, typically

Re: [Qemu-devel] [PULL v2 00/20] Miscellaneous patches for QEMU 2.12-rc

On 09/04/2018 19:21, Peter Maydell wrote: > On 9 April 2018 at 15:59, Paolo Bonzini wrote: >> The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d: >> >> Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100) >> >> are available in the git

Re: [Qemu-devel] [PATCH] configure: don't warn GTK if disabled

On 09/04/2018 11:24, Peter Maydell wrote: > On 9 April 2018 at 09:31, Daniel P. Berrangé wrote: >> Feels to me that since we've deprecated 2.0, we could just *never* auto >> detect - just do test -z "$gtkabi" && gtkabi=3.0 >> >> Anyone who wants gtk2 should have to use an

Re: [Qemu-devel] [PATCH V4] migration: add capability to bypass the shared memory

Hi, * Lai Jiangshan (jiangshan...@gmail.com) 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-devel] tests/Makefile.include gtester rules defeat attempts to parallelize

I noticed that the rules for gtester in tests/Makefile.include work against attempts to parallelize "make check" with make's -j argument, because from Make's point of view we run a single command which looks like gtester tests/endianness-test tests/fdc-test tests/ide-test tests/ahci-test

Re: [Qemu-devel] [PULL v2 00/20] Miscellaneous patches for QEMU 2.12-rc

On 9 April 2018 at 15:59, Paolo Bonzini wrote: > The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d: > > Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100) > > are available in the git repository at: > >

[Qemu-devel] qom-test on netbsd can be very slow

My NetBSD build system recently seems to have taken a nosedive in how long it takes to finish "make check". This seems to be because qom-test (and probably other things where the test interacts with the QEMU process) can run very slowly. netbsdvm# for i in 1 2 3 4 5 6 7 8 9 10; do

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/09/18 10:26, Gerd Hoffmann wrote: >> +# { >> +# "executable": { >> +# "pathname": "/usr/share/OVMF/OVMF_CODE.secboot.fd", >> +# "description": "OVMF with Secure Boot and SMM-protected varstore", >> +# "tags": [ >> +# "FD_SIZE_4MB", >> +#

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/09/18 10:19, Gerd Hoffmann wrote: >>> +{ 'enum' : 'SystemFirmwareType', >>> + 'data' : [ 'bios', 'slof', 'uboot', 'uefi' ] } >> >> The naming here is quite a bad mixture between firmware interface >> ('bios', 'uefi') and firmware implementations ('slof', 'uboot'). There >> could be other

Re: [Qemu-devel] [PATCH 1/1] mach-virt: Change default cpu and gic-version setting to "max"

On 04/09/2018 10:55 AM, Peter Maydell wrote: > On 9 April 2018 at 16:49, Wei Huang wrote: >> Running mach-virt machine types (i.e. "-M virt") on different systems can >> result in various misleading warnings if -cpu and/or gic-version not >> specified. >> For KVM, this can be

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/09/18 10:08, Thomas Huth wrote: > On 07.04.2018 02:01, Laszlo Ersek wrote: >> Add a schema that describes the properties of virtual machine firmware. > [...] >> +## >> +# @SystemFirmware: >> +# >> +# Describes a system firmware binary and any NVRAM slots that it requires. >> +# >> +#

Re: [Qemu-devel] [qemu RFC] qapi: add "firmware.json"

On 04/09/18 09:26, Thomas Huth wrote: > Hi Laszlo, > > On 07.04.2018 02:01, Laszlo Ersek wrote: >> Add a schema that describes the properties of virtual machine firmware. >> >> Each firmware executable installed on a host system should come with a >> JSON file that conforms to this schema, and

Re: [Qemu-devel] [PATCH 1/1] mach-virt: Change default cpu and gic-version setting to "max"

On 04/09/2018 10:56 AM, Daniel P. Berrangé wrote: > On Mon, Apr 09, 2018 at 10:49:21AM -0500, Wei Huang wrote: >> Running mach-virt machine types (i.e. "-M virt") on different systems can >> result in various misleading warnings if -cpu and/or gic-version not >> specified. >> For KVM, this can

Re: [Qemu-devel] [PULL 0/5] virtio,vhost: fixes

On 9 April 2018 at 15:42, Michael S. Tsirkin wrote: > The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d: > > Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100) > > are available in the git repository at: > >

Re: [Qemu-devel] [PATCH v2 00/17] Translation loop conversion for sh4/sparc/mips/s390x/openrisc/riscv targets

On Mon, Apr 09, 2018 at 16:01:36 +0200, Bastian Koppelmann wrote: > Thanks for doing this grunt work. Me and a colleague were planning to do > this as well after converting the RISC-V frontend to decodetree. Do you > have any plans to do this for the TriCore frontend as well? I have the > same

Re: [Qemu-devel] [PATCH v2 16/17] target/riscv: convert to DisasContextBase

On Mon, Apr 09, 2018 at 16:22:53 +0200, Bastian Koppelmann wrote: > On 04/06/2018 08:19 PM, Emilio G. Cota wrote: > > Notes: > > > > - Did not convert {num,max}_insns, since the corresponding code > > will go away in the next patch. > > > > - ctx->pc becomes ctx->base.pc_next, and ctx->next_pc

Re: [Qemu-devel] [PATCH 1/1] mach-virt: Change default cpu and gic-version setting to "max"

On Mon, Apr 09, 2018 at 10:49:21AM -0500, Wei Huang wrote: > Running mach-virt machine types (i.e. "-M virt") on different systems can > result in various misleading warnings if -cpu and/or gic-version not > specified. > For KVM, this can be solved mostly by using "host" type. But the "host" type

Re: [Qemu-devel] [PATCH 1/1] mach-virt: Change default cpu and gic-version setting to "max"

On 9 April 2018 at 16:49, Wei Huang wrote: > Running mach-virt machine types (i.e. "-M virt") on different systems can > result in various misleading warnings if -cpu and/or gic-version not > specified. > For KVM, this can be solved mostly by using "host" type. But the "host"

[Qemu-devel] [PATCH 1/1] mach-virt: Change default cpu and gic-version setting to "max"

Running mach-virt machine types (i.e. "-M virt") on different systems can result in various misleading warnings if -cpu and/or gic-version not specified. For KVM, this can be solved mostly by using "host" type. But the "host" type doesn't work for TCG. Compared with "host", the "max" type not only

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

* Kevin Wolf (kw...@redhat.com) wrote: > Am 09.04.2018 um 16:04 hat Dr. David Alan Gilbert geschrieben: > > * Kevin Wolf (kw...@redhat.com) wrote: > > > Am 09.04.2018 um 12:27 hat Dr. David Alan Gilbert geschrieben: > > > > * Kevin Wolf (kw...@redhat.com) wrote: > > > > > Am 03.04.2018 um 22:52

Re: [Qemu-devel] [RFC] Defining firmware (OVMF, et al) metadata format & file

On 04/09/18 11:02, Kashyap Chamarthy wrote: > - It also provides a persistent command history in a convenient file: > '~/.qmp-shell_history' I noticed it used readline, but I didn't know about the dedicated history file. Nice! Thanks! Laszlo

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

On Wed, Apr 04, 2018 at 12:03:03 +0200, Kevin Wolf wrote: > Am 03.04.2018 um 22:52 hat Dr. David Alan Gilbert geschrieben: > > * Kevin Wolf (kw...@redhat.com) wrote: > > > Consider a case where the management tool keeps a mirror job with > > > sync=none running to expose all I/O requests to some

Re: [Qemu-devel] [PATCH for-2.12] gdbstub: fix off-by-one in gdb_handle_packet()

On 9 April 2018 at 10:39, Paolo Bonzini wrote: > On 09/04/2018 07:58, Stefan Hajnoczi wrote: >> On Sun, Apr 08, 2018 at 11:59:33AM -0300, Philippe Mathieu-Daudé wrote: >>> memtohex() adds an extra trailing NUL character. >>> >>> Reported-by: AddressSanitizer >>>

Re: [Qemu-devel] [PATCH] migration: Don't activate block devices if using -S

Am 09.04.2018 um 16:04 hat Dr. David Alan Gilbert geschrieben: > * Kevin Wolf (kw...@redhat.com) wrote: > > Am 09.04.2018 um 12:27 hat Dr. David Alan Gilbert geschrieben: > > > * Kevin Wolf (kw...@redhat.com) wrote: > > > > Am 03.04.2018 um 22:52 hat Dr. David Alan Gilbert geschrieben: > > > > > *

[Qemu-devel] [PULL for-2.12 5/8] pc-bios/s390: update images

Contains the following commits: - s390: Do not pass inofficial IPL type to the guest For s390-netboot.img, this also contains the following commits (update was forgotten last time): - pc-bios/s390-ccw: Move string arrays from bootmap header to .c file - pc-bios/s390-ccw: Increase virtio timeout

  1   2   3   >