[Qemu-devel] [PATCH 3/6] intel_iommu: provide AddressSpaceOps.iommu_get instance

From: Peter Xu Provide AddressSpaceOps.iommu_get() in Intel IOMMU emulator. Signed-off-by: Peter Xu Signed-off-by: Liu, Yi L --- hw/i386/intel_iommu.c | 7 +++ include/hw/i386/intel_iommu.h | 2 ++ 2 files changed, 9

[Qemu-devel] [PATCH 5/6] vfio/pci: add notify framework based on IOMMUObject

This patch introduce a notify framework for IOMMUObject.iommu_notifiers. Introduce VFIOGuestIOMMUObject is to link VFIO Container and the new IOMMUObject notififiers. VFIOGuestIOMMUObject instance is allocated when device is assigned and meanwhile vIOMMU is exposed to guest. If there is

[Qemu-devel] [PATCH 2/6] memory: introduce AddressSpaceOps and IOMMUObject

From: Peter Xu AddressSpaceOps is similar to MemoryRegionOps, it's just for address spaces to store arch-specific hooks. The first hook I would like to introduce is iommu_get(). Return an IOMMUObject behind the AddressSpace. For systems that have IOMMUs, we will create a

[Qemu-devel] [PATCH 6/6] vfio/pci: register vfio_iommu_bind_pasidtbl_notify notifier

This is an example to show the usage of IOMMUObject based notifier. For passthru devices, if there is a vIOMMU exposed to guest, guest would issue iommu operation on the devices. And the iommu operations needs to be propagated to host iommu driver. In future, the IOMMUObject notifiers may

[Qemu-devel] [PATCH 0/6] Introduce new iommu notifier framework

This patchset is a follow-up of Peter Xu's patchset as the link below. In brief, Peter's patchset is to introduce a common IOMMU object which is not depending on platform (x86/ppc/...), or bus (PCI/...). And based on it, a iommu object based notifier framework is introduced and also

[Qemu-devel] [PATCH 1/6] memory: rename existing iommu notifier to be iommu mr notifier

From: Peter Xu IOMMU notifiers before are mostly used for [dev-]IOTLB stuffs. It is not suitable for other kind of notifiers (one example would be the future virt-svm support). Considering that current notifiers are targeted for per memory region, renaming the iommu notifier

[Qemu-devel] [PATCH 4/6] vfio: rename GuestIOMMU to be GuestIOMMUMR

Rename GuestIOMMU to GuestIOMMUMR as the existing GuestIOMMU is for MemoryRegion related notifiers. Signed-off-by: Liu, Yi L --- hw/vfio/common.c | 15 --- include/hw/vfio/vfio-common.h | 8 2 files changed, 12 insertions(+), 11

Re: [Qemu-devel] Qemu start VM in huge page without '-mem-prealloc' will get memory leak?

Why could I not find in ovs-dpdk maillist? could some one give the bug number? 2017-10-27 15:08 GMT+08:00 Daniel P. Berrange : > On Fri, Oct 27, 2017 at 11:28:33AM +0800, Sam wrote: > > After restart ovs-dpdk(which is openvswitch with dpdk lib), memory is > > released. > > >

[Qemu-devel] [Bug] virtio-blk: qemu will crash if hotplug virtio-blk device failed

I found that hotplug virtio-blk device will lead to qemu crash. Re-production steps: 1. Run VM named vm001 2. Create a virtio-blk.xml which contains wrong configurations: 3. Run command : virsh attach-device vm001 vm001 Libvirt will return err msg: error: Failed

[Qemu-devel] [Bug 997631] Re: Windows 2008R2 very slow cold boot when 4 CPUs

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

Re: [Qemu-devel] [PATCH v2 1/4] build: allow setting a custom GIT binary for transparent proxying

On 30/10/17 18:52, Daniel P. Berrange wrote: > On Mon, Oct 30, 2017 at 10:49:01AM +1100, Alexey Kardashevskiy wrote: >> On 30/10/17 03:29, Daniel P. Berrange wrote: >>> On Mon, Oct 30, 2017 at 01:08:56AM +1100, Alexey Kardashevskiy wrote: I run ./scripts/git-submodule.sh on a server

Re: [Qemu-devel] [PATCH v2] arm: implement cache/shareability attribute bits for PAR registers

> From: Peter Maydell [mailto:peter.mayd...@linaro.org] > Sent: Tuesday, 31 October 2017 03:25 > > On 20 October 2017 at 22:49, Andrew Baumann > wrote: > > On a successful address translation instruction, PAR is supposed to > > contain cacheability and shareability

[Qemu-devel] Retrocomputing devroom at FOSDEM 2018

Hi, I just found out someone managed to get a retrocomputing devroom accepted at FOSDEM: https://lists.fosdem.org/pipermail/retrocomputing-devroom/2017-October/00.html https://www.elpauer.org/2017/10/retrocomputing-devroom-call-for-participation/comment-page-1/ Surely there are a lot of

Re: [Qemu-devel] [Qemu-ppc] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos

On 10/30/2017 06:29 PM, Daniel Henrique Barboza wrote: On 10/30/2017 06:12 PM, David Gibson wrote: On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote: This series implements a few RTAS hypercalls in tests/libqos that, used together, implement the DRC state transition

Re: [Qemu-devel] [PATCH v2] don't hardcode EL1 in extended_addresses_enabled

On Mon, 30 Oct 2017, Peter Maydell wrote: > On 26 October 2017 at 00:28, Stefano Stabellini > wrote: > > extended_addresses_enabled calls arm_el_is_aa64, hardcoding exception > > level 1. Instead, add an additional "el" argument to > > extended_addresses_enabled. > > > >

[Qemu-devel] [PULL 10/12] nbd/client: prepare nbd_receive_reply for structured reply

From: Vladimir Sementsov-Ogievskiy In following patch nbd_receive_reply will be used both for simple and structured reply header receiving. NBDReply is altered into union of simple reply header and structured reply chunk header, simple error translation moved to

[Qemu-devel] [PULL 08/12] nbd/server: Include human-readable message in structured errors

The NBD spec permits including a human-readable error string if structured replies are in force, so we might as well send the client the message that we logged on any error. Signed-off-by: Eric Blake Reviewed-by: Vladimir Sementsov-Ogievskiy

[Qemu-devel] [PULL 04/12] nbd/server: Report error for write to read-only export

When the server is read-only, we were already reporting an error message for NBD_CMD_WRITE_ZEROES, but failed to set errp for a similar NBD_CMD_WRITE. This will matter more once structured replies allow the server to propagate the errp information back to the client. While at it, use an error

[Qemu-devel] [PULL 07/12] nbd: Minimal structured read for server

From: Vladimir Sementsov-Ogievskiy Minimal implementation of structured read: one structured reply chunk, no segmentation. Minimal structured error implementation: no text message. Support DF flag, but just ignore it, as there is no segmentation any way. Signed-off-by:

[Qemu-devel] [PULL 12/12] nbd: Minimal structured read for client

From: Vladimir Sementsov-Ogievskiy Minimal implementation: for structured error only error_report error message. Note that test 83 is now more verbose, because the implementation prints more warnings about unexpected communication errors; perhaps future patches should

[Qemu-devel] [PULL 06/12] nbd/server: Refactor zero-length option check

Consolidate the response for a non-zero-length option payload into a new function, nbd_reject_length(). This check will also be used when introducing support for structured replies. Note that STARTTLS response differs based on time: if the connection is still unencrypted, we set fatal to true (a

[Qemu-devel] [PULL 03/12] nbd: Expose constants and structs for structured read

Upcoming patches will implement the NBD structured reply extension [1] for both client and server roles. Declare the constants, structs, and lookup routines that will be valuable whether the server or client code is backported in isolation. This includes moving one constant from an internal

[Qemu-devel] [PULL 11/12] nbd: Move nbd_read() to common header

An upcoming change to block/nbd-client.c will want to read the tail of a structured reply chunk directly from the wire. Move this function to make it easier. Based on a patch from Vladimir Sementsov-Ogievskiy. Signed-off-by: Eric Blake Reviewed-by: Vladimir

[Qemu-devel] [PULL 05/12] nbd/server: Simplify nbd_negotiate_options loop

Instead of making each caller check whether a transmission error occurred, we can sink a common error check to the end of the loop. Signed-off-by: Eric Blake Message-Id: <20171027104037.8319-6-ebl...@redhat.com> [eblake: squash in compiler warning fix] Reviewed-by: Vladimir

[Qemu-devel] [PULL 01/12] nbd: Include error names in trace messages

NBD errors were originally sent over the wire based on Linux errno values; but not all the world is Linux, and not all platforms share the same values. Since a number isn't very easy to decipher on all platforms, update the trace messages to include the name of NBD errors being sent/received over

[Qemu-devel] [PULL 02/12] nbd: Move nbd_errno_to_system_errno() to public header

This is needed in preparation for structured reply handling, as we will be performing the translation from NBD error to system errno value higher in the stack at block/nbd-client.c. Signed-off-by: Eric Blake Reviewed-by: Vladimir Sementsov-Ogievskiy

[Qemu-devel] [PULL 09/12] nbd/client: refactor nbd_receive_starttls

From: Vladimir Sementsov-Ogievskiy Split out nbd_request_simple_option to be reused for structured reply option. Signed-off-by: Vladimir Sementsov-Ogievskiy Signed-off-by: Eric Blake Message-Id:

[Qemu-devel] [PULL 00/12] NBD patches prior to 2.11 soft freeze

The following changes since commit abf6e752e55b2f5afb48303429dea2db7c3a62de: Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20171030' into staging (2017-10-30 13:02:45 +) are available in the git repository at: git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2017-10-30

Re: [Qemu-devel] [PATCH 1/6] qio: Make port 0 work for qio

On Mon, Oct 30, 2017 at 12:21:07PM +0100, Juan Quintela wrote: > For tcp sockets we read back what is the socket/address. So we know > what is the port that we are listening into. > > Looked all callers of the function, and they just create the addr, use > it, and drop it, so no problem that we

Re: [Qemu-devel] [PATCH v6 06/12] nbd/server: Refactor zero-length option check

On 10/30/2017 09:11 PM, Eric Blake wrote: > On 10/30/2017 06:22 PM, Vladimir Sementsov-Ogievskiy wrote: >> 27.10.2017 13:40, Eric Blake wrote: >>> Consolidate the response for a non-zero-length option payload >>> into a new function, nbd_reject_length().  This check will >>> also be used when

Re: [Qemu-devel] [Qemu-ppc] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos

On 10/30/2017 06:12 PM, David Gibson wrote: On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote: This series implements a few RTAS hypercalls in tests/libqos that, used together, implement the DRC state transition described in PAPR 2.7+, 13.4. This started as an attempt

[Qemu-devel] [PULL 1/2] hmp: Replace error_report_err

From: ZhiPeng Lu Use hmp_handle_error instend of error_report_err to set error. Signed-off-by: ZhiPeng Lu Reviewed-by: Jiyun Fan Message-Id: <1508411793-22868-1-git-send-email-lu.zhip...@zte.com.cn> Reviewed-by: Philippe

[Qemu-devel] [PULL 2/2] monitor: fix dangling CPU pointer

From: Greg Kurz If a CPU selected with the "cpu" command is hot-unplugged then "info cpus" causes QEMU to exit: (qemu) device_del cpu1 (qemu) info cpus qemu:qemu_cpu_kick_thread: No such process This happens because "cpu" stores the pointer to the selected CPU into the monitor

[Qemu-devel] [PULL 0/2] hmp queue

From: "Dr. David Alan Gilbert" <dgilb...@redhat.com> The following changes since commit abf6e752e55b2f5afb48303429dea2db7c3a62de: Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20171030' into staging (2017-10-30 13:02:45 +) are available in the Git repos

Re: [Qemu-devel] drive_add: file names with spaces

* Eric Blake (ebl...@redhat.com) wrote: > On 10/30/2017 03:32 PM, Dr. David Alan Gilbert wrote: > > > Now, the real challenge is how to deal with a filename with a comma in; > >drive_add 1 "file=foo,bar" > >Could not open 'foo': No such file or directory > > > > Does HMP use the

Re: [Qemu-devel] [PATCH v1 0/3] ppc: adding some RTAS calls in tests/libqos

On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote: > This series implements a few RTAS hypercalls in tests/libqos > that, used together, implement the DRC state transition described > in PAPR 2.7+, 13.4. > > This started as an attempt of implementing hot unplug qtests for

Re: [Qemu-devel] [PATCH v6 06/12] nbd/server: Refactor zero-length option check

On 10/30/2017 06:22 PM, Vladimir Sementsov-Ogievskiy wrote: > 27.10.2017 13:40, Eric Blake wrote: >> Consolidate the response for a non-zero-length option payload >> into a new function, nbd_reject_length().  This check will >> also be used when introducing support for structured replies. >> >>

Re: [Qemu-devel] drive_add: file names with spaces

On 10/30/2017 03:32 PM, Dr. David Alan Gilbert wrote: > Now, the real challenge is how to deal with a filename with a comma in; >drive_add 1 "file=foo,bar" >Could not open 'foo': No such file or directory > Does HMP use the QemuOpts parser? If so, try: drive_add 1 "file=foo,,bar"

Re: [Qemu-devel] [PATCH v2] arm: implement cache/shareability attribute bits for PAR registers

On 20 October 2017 at 22:49, Andrew Baumann wrote: > On a successful address translation instruction, PAR is supposed to > contain cacheability and shareability attributes determined by the > translation. We previously returned 0 for these bits (in line with the >

Re: [Qemu-devel] [PATCHv4 00/13] sun4m: sparc32_dma tidy-ups

On Mon, Oct 30, 2017 at 4:00 PM, Mark Cave-Ayland wrote: > On 27/10/17 17:42, Philippe Mathieu-Daudé wrote: [...] >> If you don't accept my comments (or don't have time) about keeping >> "hw/sparc/sparc32_dma.h" generic and moving network/scsi parts in >>

Re: [Qemu-devel] [PATCHv4 09/13] lance: move TYPE_LANCE and SysBusPCNetState from lance.c to lance.h

On 30/10/17 18:45, Philippe Mathieu-Daudé wrote: >>> +/* >>> + * QEMU AMD PC-Net II (Am79C970A) emulation >> >> Filename says this is Lance ethernet, but the comment says it's PC-Net ? > > According to the datasheet for Am79C970A, the original Lance is an > Am7990

Re: [Qemu-devel] [RFC 00/19] KVM: s390/crypto/vfio: guest dedicated crypto adapters

On 10/30/2017 04:57 AM, Christian Borntraeger wrote: adding qemu devel and add Daniel and Erik from libvirt to keep them in the loop. On 10/29/2017 12:11 PM, Cornelia Huck wrote: On Fri, 13 Oct 2017 13:38:45 -0400 Tony Krowiak wrote: Tony Krowiak (19): KVM:

Re: [Qemu-devel] [PATCHv4 00/13] sun4m: sparc32_dma tidy-ups

On 27/10/17 17:42, Philippe Mathieu-Daudé wrote: > Hi Mark, > > On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote: >> This patchset aims to tidy-up the sparc32_dma code by improving the >> modelling of the espdma/ledma devices using both QOM and the memory >> API which didn't exist when the code

Re: [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support

On 10/30/2017 06:38 PM, Pierre Morel wrote: > On 30/10/2017 18:08, Christian Borntraeger wrote: >> >> On 10/30/2017 05:59 PM, Cornelia Huck wrote: >>> On Mon, 30 Oct 2017 14:48:23 +0100 >>> Christian Borntraeger wrote: >>> >>> FWIW, I am testing a guest patch

Re: [Qemu-devel] [PATCHv4 11/13] sparc32_dma: introduce new SPARC32_DMA type container object

On Mon, Oct 30, 2017 at 3:51 PM, Mark Cave-Ayland wrote: > On 27/10/17 17:18, Philippe Mathieu-Daudé wrote: >> On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote: >>> Create a new SPARC32_DMA container object (including an appropriate >>> container >>> memory region)

Re: [Qemu-devel] [PATCHv4 11/13] sparc32_dma: introduce new SPARC32_DMA type container object

On 27/10/17 17:18, Philippe Mathieu-Daudé wrote: > On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote: >> Create a new SPARC32_DMA container object (including an appropriate container >> memory region) and add instances of the SPARC32_ESPDMA_DEVICE and >> SPARC32_LEDMA_DEVICE as child objects. The

Re: [Qemu-devel] [PATCH v3] monitor: fix dangling CPU pointer

* Greg Kurz (gr...@kaod.org) wrote: > If a CPU selected with the "cpu" command is hot-unplugged then "info cpus" > causes QEMU to exit: > > (qemu) device_del cpu1 > (qemu) info cpus > qemu:qemu_cpu_kick_thread: No such process > > This happens because "cpu" stores the pointer to the selected CPU

Re: [Qemu-devel] [PATCHv4 09/13] lance: move TYPE_LANCE and SysBusPCNetState from lance.c to lance.h

Hi Mark, >> +/* >> + * QEMU AMD PC-Net II (Am79C970A) emulation > > Filename says this is Lance ethernet, but the comment says it's PC-Net ? According to the datasheet for Am79C970A, the original Lance is an Am7990 device and the Am79C970A aka PCNet-PCI II as

Re: [Qemu-devel] [PATCH v8 00/14] Dirty bitmaps postcopy migration

30.10.2017 19:32, Vladimir Sementsov-Ogievskiy wrote: Hi all! There is a new version of dirty bitmap postcopy migration series. v8 clone: tag postcopy-v8 from https://src.openvz.org/scm/~vsementsov/qemu.git online: https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=postcopy-v8

Re: [Qemu-devel] [PATCHv4 09/13] lance: move TYPE_LANCE and SysBusPCNetState from lance.c to lance.h

On 30/10/17 13:22, Peter Maydell wrote: > On 30 October 2017 at 13:10, Mark Cave-Ayland > wrote: >> On 26/10/17 11:12, Mark Cave-Ayland wrote: >>> On 25/10/17 18:47, Peter Maydell wrote: On 25 October 2017 at 16:59, Mark Cave-Ayland wrote: > --- /dev/null

[Qemu-devel] [PATCH RESEND] vl: only display available accelerators

examples configuring with '--enable-kvm --disable-tcg' - before $ qemu-system-x86_64 -accel help Possible accelerators: kvm, xen, hax, tcg $ qemu-system-x86_64 -accel tcg qemu-system-x86_64: -machine accel=tcg: No accelerator found # qemu-system-x86_64 -accel hax

[Qemu-devel] [PATCH v8.1 05/14] migration: introduce postcopy-only pending

There would be savevm states (dirty-bitmap) which can migrate only in postcopy stage. The corresponding pending is introduced here. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Juan Quintela --- 8.1: add new version for

Re: [Qemu-devel] [RFC PATCH] vl: only display available accelerators

Oops this isn't RFC anymore, this one is v1 ... sorry! On Mon, Oct 30, 2017 at 3:14 PM, Philippe Mathieu-Daudé wrote: [...] > --- > since RFC: > - use much cleaner object_class_get_list(TYPE_ACCEL, false) > > vl.c | 39 ++- > 1 file

Re: [Qemu-devel] [PATCH v8 05/14] migration: introduce postcopy-only pending

30.10.2017 20:31, Dr. David Alan Gilbert wrote: * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: There would be savevm states (dirty-bitmap) which can migrate only in postcopy stage. The corresponding pending is introduced here. Signed-off-by: Vladimir Sementsov-Ogievskiy

[Qemu-devel] [RFC PATCH] vl: only display available accelerators

examples configuring with '--enable-kvm --disable-tcg' - before $ qemu-system-x86_64 -accel help Possible accelerators: kvm, xen, hax, tcg $ qemu-system-x86_64 -accel tcg qemu-system-x86_64: -machine accel=tcg: No accelerator found # qemu-system-x86_64 -accel hax

Re: [Qemu-devel] [RFC PATCH v6 13/12] tweak test 83 verbosity

27.10.2017 13:45, Eric Blake wrote: Commenting these two lines is enough to avoid the change to 083.out in 12/12. That is evidence that we may want these two lines to be trace points rather than error messages; or maybe we really do like the extra verbosity in the case of an unexpected

Re: [Qemu-devel] [PATCH v2] don't hardcode EL1 in extended_addresses_enabled

On 26 October 2017 at 00:28, Stefano Stabellini wrote: > extended_addresses_enabled calls arm_el_is_aa64, hardcoding exception > level 1. Instead, add an additional "el" argument to > extended_addresses_enabled. > > The caller will pass the right value. In most cases, it

Re: [Qemu-devel] [PATCH v6 12/12] nbd: Minimal structured read for client

27.10.2017 13:40, Eric Blake wrote: From: Vladimir Sementsov-Ogievskiy Minimal implementation: for structured error only error_report error message. Note that test 83 is now more verbose, because the implementation prints more warnings about unexpected communication

Re: [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support

On 30/10/2017 18:08, Christian Borntraeger wrote: On 10/30/2017 05:59 PM, Cornelia Huck wrote: On Mon, 30 Oct 2017 14:48:23 +0100 Christian Borntraeger wrote: FWIW, I am testing a guest patch that enables zPCI without AIS. Its as simple as diff --git

Re: [Qemu-devel] [PATCH v6 09/12] nbd/client: refactor nbd_receive_starttls

27.10.2017 13:40, Eric Blake wrote: From: Vladimir Sementsov-Ogievskiy Split out nbd_request_simple_option to be reused for structured reply option. Signed-off-by: Vladimir Sementsov-Ogievskiy Signed-off-by: Eric Blake

Re: [Qemu-devel] [PATCH v8 05/14] migration: introduce postcopy-only pending

* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: > There would be savevm states (dirty-bitmap) which can migrate only in > postcopy stage. The corresponding pending is introduced here. > > Signed-off-by: Vladimir Sementsov-Ogievskiy > Reviewed-by: Juan

Re: [Qemu-devel] [PATCH v6 07/12] nbd: Minimal structured read for server

27.10.2017 13:40, Eric Blake wrote: From: Vladimir Sementsov-Ogievskiy Minimal implementation of structured read: one structured reply chunk, no segmentation. Minimal structured error implementation: no text message. Support DF flag, but just ignore it, as there is no

Re: [Qemu-devel] [PATCH v6 06/12] nbd/server: Refactor zero-length option check

27.10.2017 13:40, Eric Blake wrote: Consolidate the response for a non-zero-length option payload into a new function, nbd_reject_length(). This check will also be used when introducing support for structured replies. Note that STARTTLS response differs based on time: if the connection is

[Qemu-devel] [Bug 1728661] [NEW] qemu-io segfaults at block/qcow2.h:533

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached file named test.img to a directory 2. And customize the following command to point to the above directory and run the same. # mv test.img

[Qemu-devel] [Bug 1728661] Re: qemu-io segfaults at block/qcow2.h:533

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728661/+attachment/5000235/+files/test.img_1728661.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728661

Re: [Qemu-devel] QMP event missed during startup

* Ross Lagerwall (ross.lagerw...@citrix.com) wrote: > Hi, > > I have found an issue where QEMU emits the RESUME event during startup when > it starts VM execution, but it is not possible to receive this event. > > To repro this, run: > qemu-system-i386 -m 256 -trace >

[Qemu-devel] [Bug 1728660] [NEW] qemu-io segfaults at block/io.c:2545

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached file named test.img to a directory 2. And customize the following command to point to the above directory and run the same. # mv test.img

[Qemu-devel] [Bug 1728657] Re: qemu-io: block/qcow2-cluster.c:1109: handle_copied: Assertion failed

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728657/+attachment/5000204/+files/test.img_1728657.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728657

[Qemu-devel] [Bug 1728657] [NEW] qemu-io: block/qcow2-cluster.c:1109: handle_copied: Assertion failed

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached file test.img to a directory 2. And customize the following command to point to the above directory and run the same. # mv test.img copy.img #

[Qemu-devel] [Bug 1728660] Re: qemu-io segfaults at block/io.c:2545

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728660/+attachment/5000223/+files/test.img_1728660.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728660

Re: [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support

On 10/30/2017 05:59 PM, Cornelia Huck wrote: > On Mon, 30 Oct 2017 14:48:23 +0100 > Christian Borntraeger wrote: > > >> FWIW, I am testing a guest patch that enables zPCI without AIS. Its as >> simple as >> >> >> diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c

Re: [Qemu-devel] drive_add: file names with spaces

* Programmingkid (programmingk...@gmail.com) wrote: > > > On Oct 30, 2017, at 10:32 AM, Dr. David Alan Gilbert > > wrote: > > > > * Programmingkid (programmingk...@gmail.com) wrote: > >> > >>> On Oct 29, 2017, at 6:21 AM, Dr. David Alan Gilbert >

Re: [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support

On Mon, 30 Oct 2017 14:48:23 +0100 Christian Borntraeger wrote: > FWIW, I am testing a guest patch that enables zPCI without AIS. Its as simple > as > > > diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c > index 7b30af5..9b24836 100644 > ---

Re: [Qemu-devel] [PATCH v4] nvme: Add tracing

Cc'ing Stefan and Trivial On 10/30/2017 01:07 PM, Doug Gale wrote: > From 0e27b5dca8f4f32a1b194e1b3544be77dd4f45d9 Mon Sep 17 00:00:00 2001 > From: Doug Gale > Date: Mon, 30 Oct 2017 09:28:43 -0400 > Subject: [PATCH] nvme: Add tracing > ^ to remove from commit description,

Re: [Qemu-devel] [PATCH v6 05/12] nbd/server: Simplify nbd_negotiate_options loop

27.10.2017 13:40, Eric Blake wrote: Instead of making each caller check whether a transmission error occurred, we can sink a common error check to the end of the loop. Signed-off-by: Eric Blake Reviewed-by: Vladimir Sementsov-Ogievskiy -- Best

[Qemu-devel] [PATCH v8 05/14] migration: introduce postcopy-only pending

There would be savevm states (dirty-bitmap) which can migrate only in postcopy stage. The corresponding pending is introduced here. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Juan Quintela --- include/migration/register.h | 17

[Qemu-devel] [PATCH v8 03/14] block/dirty-bitmap: add bdrv_dirty_bitmap_release_successor

To just release successor and unfreeze bitmap without any additional work. Signed-off-by: Vladimir Sementsov-Ogievskiy Signed-off-by: Denis V. Lunev --- include/block/dirty-bitmap.h | 2 ++ block/dirty-bitmap.c | 14 ++ 2 files

[Qemu-devel] [PATCH v8 02/14] block/dirty-bitmap: add locked version of bdrv_release_dirty_bitmap

It is needed to realize bdrv_dirty_bitmap_release_successor in the following patch. Signed-off-by: Vladimir Sementsov-Ogievskiy --- block/dirty-bitmap.c | 25 - 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/block/dirty-bitmap.c

[Qemu-devel] [PATCH v8 00/14] Dirty bitmaps postcopy migration

Hi all! There is a new version of dirty bitmap postcopy migration series. v8 clone: tag postcopy-v8 from https://src.openvz.org/scm/~vsementsov/qemu.git online: https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=postcopy-v8 - rebased on master - patches 01-03 from v7 are already

[Qemu-devel] [PATCH v8 10/14] migration: add postcopy migration of dirty bitmaps

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 the same node), then, if their granularities are the same the

[Qemu-devel] [PATCH v8 09/14] migration: add is_active_iterate handler

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 Reviewed-by: Juan Quintela ---

[Qemu-devel] [PATCH v8 11/14] iotests: add default node-name

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 Sementsov-Ogievskiy Reviewed-by: Max Reitz

[Qemu-devel] [PATCH v8 12/14] iotests: add dirty bitmap migration test

The test starts two vms (vm_a, vm_b), create dirty bitmap in the first one, do several writes to corresponding device and then migrate vm_a to vm_b with dirty bitmaps. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Max Reitz ---

[Qemu-devel] [PATCH v8 06/14] qapi: add dirty-bitmaps migration capability

Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow Reviewed-by: Eric Blake Reviewed-by: Juan Quintela --- qapi/migration.json | 6 +- migration/migration.h | 1 + migration/migration.c |

[Qemu-devel] [PATCH v8 04/14] block/dirty-bitmap: add bdrv_dirty_bitmap_set_frozen

Make it possible to set bitmap 'frozen' without a successor. This is needed to protect the bitmap during outgoing bitmap postcopy migration. Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/block/dirty-bitmap.h | 1 + block/dirty-bitmap.c | 22

[Qemu-devel] [PATCH v8 01/14] block/dirty-bitmap: add bdrv_dirty_bitmap_enable_successor()

Enabling bitmap successor is necessary to enable successors of bitmaps being migrated before target vm start. Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/block/dirty-bitmap.h | 1 + block/dirty-bitmap.c | 8 2 files changed, 9 insertions(+)

[Qemu-devel] [PATCH v8 14/14] iotests: add persistent bitmap migration test

Test that persistent bitmap migrates and its persistance property migrates too. Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/169 | 21 ++--- tests/qemu-iotests/169.out | 4 ++-- 2 files changed, 20 insertions(+), 5

[Qemu-devel] [PATCH v8 13/14] iotests: add dirty bitmap postcopy test

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 start (postcopy should start) - do writes from set B - check bitmap sha256

[Qemu-devel] [PATCH v8 07/14] migration: include migrate_dirty_bitmaps in migrate_postcopy

Enable postcopy if dirty bitmap migration is endabled. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Juan Quintela --- migration/migration.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration/migration.c

[Qemu-devel] [PATCH v8 08/14] migration/qemu-file: add qemu_put_counted_string()

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: Vladimir Sementsov-Ogievskiy Reviewed-by:

[Qemu-devel] [Bug 1728643] Re: qemu-io fails with Assertion `*host_offset != 0' failed

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728643/+attachment/5000185/+files/test.img_1728643.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728643

[Qemu-devel] [Bug 1728643] [NEW] qemu-io fails with Assertion `*host_offset != 0' failed

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached files named test.img to a directory 2. And customize the following command to point to the above directory and run the same. # cp test.img

Re: [Qemu-devel] [PATCH v3 5/5] RFC: fw_cfg: add DMA write operation in sysfs

On Mon, Oct 30, 2017 at 11:07:20AM +, Hatayama, Daisuke wrote: > > From: Marc-André Lureau > > > > Since qemu 2.9, DMA write operations are allowed. However, usage of this > > interface from kernel or user-space is strongly discouraged by the > > maintainers. This

[Qemu-devel] [PATCH v4] nvme: Add tracing

>From 0e27b5dca8f4f32a1b194e1b3544be77dd4f45d9 Mon Sep 17 00:00:00 2001 From: Doug Gale Date: Mon, 30 Oct 2017 09:28:43 -0400 Subject: [PATCH] nvme: Add tracing Add trace output for commands, errors, and undefined behavior. Add guest error log output for undefined behavior.

[Qemu-devel] [Bug 1728639] [NEW] qemu-io crashes with SIGSEGV when did -c truncate 320000 on a image_fuzzer image

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached files named test.img to a directory 2. And customize the following command to point to the above directory and run the same. # mv test.img

[Qemu-devel] [Bug 1728639] Re: qemu-io crashes with SIGSEGV when did -c truncate 320000 on a image_fuzzer image

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728639/+attachment/5000182/+files/test.img.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728639 Title:

Re: [Qemu-devel] [PATCH v3] monitor: fix dangling CPU pointer

On Tue, 17 Oct 2017 10:16:22 +0200 Greg Kurz wrote: > If a CPU selected with the "cpu" command is hot-unplugged then "info cpus" > causes QEMU to exit: > > (qemu) device_del cpu1 > (qemu) info cpus > qemu:qemu_cpu_kick_thread: No such process > > This happens because "cpu"

[Qemu-devel] [Bug 1728635] Re: qemu-io crashes with SIGSEGV when did -c aio_write 9233408 28160 on a image_fuzzer image

** Attachment added: "test.img tarred" https://bugs.launchpad.net/qemu/+bug/1728635/+attachment/5000176/+files/test.img.tar.gz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1728635 Title:

[Qemu-devel] [Bug 1728635] [NEW] qemu-io crashes with SIGSEGV when did -c aio_write 9233408 28160 on a image_fuzzer image

Public bug reported: git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4 This is on ppc64le architecture. Re-production steps: 1. Copy the attached file named test.img to a directory 2. And customize the following command to point to the above directory and run the same. # cp test.img

Re: [Qemu-devel] [RFC 00/19] KVM: s390/crypto/vfio: guest dedicated crypto adapters

On 10/30/2017 04:57 AM, Christian Borntraeger wrote: adding qemu devel and add Daniel and Erik from libvirt to keep them in the loop. On 10/29/2017 12:11 PM, Cornelia Huck wrote: On Fri, 13 Oct 2017 13:38:45 -0400 Tony Krowiak wrote: Tony Krowiak (19): KVM:

  1   2   >