Re: [Qemu-devel] Minutes of QEMU Summit 2015 (2015-08-18, Seattle)

Am 06.11.2015 um 17:22 schrieb Peter Maydell: > On 6 September 2015 at 07:05, Stefan Weil wrote: >> Part of that infrastructure is the FSF savannah server. >> The FSF infrastructure is still used for our mailing lists. >> >> http://savannah.nongnu.org/projects/qemu/ needs >>

Re: [Qemu-devel] [PATCH] exec: silence hugetlbfs warning under qtest

On Tue, Oct 27, 2015 at 05:29:43PM +0100, marcandre.lur...@redhat.com wrote: > From: Marc-André Lureau > > vhost-user-test prints a warning. A test should not need to run on > hugetlbfs, let's silence the warning under qtest. Unfortunately, the > condition can't

[Qemu-devel] [Bug 1512134] Re: Multiboot v1 memory map offset wrong

Tested today with GRUB 2.0. Indeed, mmap_entry points to the start of the structure, without a fancy offset. I guess we can close this ticket -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1512134

Re: [Qemu-devel] [PATCH V3] hw/virtio: Add PCIe capability to virtio devices

On Thu, Oct 29, 2015 at 01:56:28PM +0200, Marcel Apfelbaum wrote: > The virtio devices are converted to PCI-Express > if they are plugged into a PCI-Express bus and > the 'modern' protocol is enabled. > > Devices plugged directly into the Root Complex as > Integrated Endpoints remain PCI. > >

Re: [Qemu-devel] [PATCH for-2.5 v3 1/3] arm: boot: Add secure_board_setup flag

On Fri, Nov 6, 2015 at 6:45 AM, Peter Maydell wrote: > > On 3 November 2015 at 04:30, Peter Crosthwaite > wrote: > > Add a flag that when set, will cause the primary CPU to start in secure > > mode, even if the overall boot is non-secure.

Re: [Qemu-devel] [PATCH V3] hw/virtio: Add PCIe capability to virtio devices

On 11/08/2015 07:10 PM, Michael S. Tsirkin wrote: On Thu, Oct 29, 2015 at 01:56:28PM +0200, Marcel Apfelbaum wrote: The virtio devices are converted to PCI-Express if they are plugged into a PCI-Express bus and the 'modern' protocol is enabled. Devices plugged directly into the Root Complex as

Re: [Qemu-devel] [PATCH for-2.5 v3 3/3] arm: highbank: Implement PSCI and dummy monitor

On Fri, Nov 6, 2015 at 6:47 AM, Peter Maydell wrote: > On 3 November 2015 at 04:30, Peter Crosthwaite > wrote: >> Firstly, enable monitor mode and PSCI, both are which are features of > > "both of which" > Fixed. >> this board. >> >> In

Re: [Qemu-devel] [PATCH v6 25/33] nvdimm acpi: build ACPI nvdimm devices

On Fri, Oct 30, 2015 at 01:56:19PM +0800, Xiao Guangrong wrote: > NVDIMM devices is defined in ACPI 6.0 9.20 NVDIMM Devices > > There is a root device under \_SB and specified NVDIMM devices are under the > root device. Each NVDIMM device has _ADR which returns its handle used to > associate

Re: [Qemu-devel] [PATCH v6 32/33] nvdimm acpi: support _FIT method

On Fri, Oct 30, 2015 at 01:56:26PM +0800, Xiao Guangrong wrote: > FIT buffer is not completely mapped into guest address space, so a new > function, Read FIT, function index 0x, is reserved by QEMU to > read the piece of FIT buffer. The buffer is concatenated before _FIT > return > >

[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image

Thanks for all the tips guys, I finally got it to work on my Rpi2. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status

[Qemu-devel] [PATCH 08/18] armv7m: fix RETTOBASE

The polarity is reversed, and it should include internal exceptions. Should be set when # of active exceptions <= 1. Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git

[Qemu-devel] [PATCH 15/18] arm: gic: Remove references to NVIC

armv7m_nvic.c no longer relies on the GIC. Remove REV_NVIC and conditionals which use it. Signed-off-by: Michael Davidsaver --- hw/intc/arm_gic.c| 14 +++--- hw/intc/arm_gic_common.c | 23 --- hw/intc/gic_internal.h | 7 ++- 3

[Qemu-devel] [PATCH 00/18] Fix exception handling and msr/mrs access

This series grew from a previous incorrect patch attempting to fix some incorrect behavior. After spending some time going through the arch. ref. manual for v7-M I think I understand better how this should work and have made a number of changes which actually improve the situation. These

[Qemu-devel] [PATCH 01/18] armv7m: MRS/MSR handle unprivileged access

The MRS and MSR instruction handling isn't checking the current permission level. Signed-off-by: Michael Davidsaver --- target-arm/helper.c | 79 + 1 file changed, 37 insertions(+), 42 deletions(-) diff --git

Re: [Qemu-devel] [Qemu-block] [PATCH] mirror: Improve zero-write and discard with fragmented image

On Fri, 11/06 19:36, Max Reitz wrote: > > +next_sector = sector_num; > > +next_chunk = sector_num / sectors_per_chunk; > > @next_sector and @next_chunk set here... > > > hbitmap_next_sector = s->sector_num; > > -sector_num = s->sector_num; > > -sectors_per_chunk =

[Qemu-devel] [PATCH v3 7/9] block: Drop BlockDriver.bdrv_ioctl

Now the callback is not used any more, drop the field along with all implementations in block drivers, which are iscsi and raw. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf --- block/iscsi.c | 33 -

[Qemu-devel] [PATCH v3 8/9] block: Introduce BlockDriver.bdrv_drain callback

Drivers can have internal request sources that generate IO, like the need_check_timer in QED. Since we want quiesced periods that contain nested event loops in block layer, we need to have a way to disable such event sources. Block drivers must implement the "bdrv_drain" callback if it has any

[Qemu-devel] [PATCH v3 6/9] block: Emulate bdrv_ioctl with bdrv_aio_ioctl and track both

Currently all drivers that support .bdrv_aio_ioctl also implement .bdrv_ioctl redundantly. To track ioctl requests in block layer it is easier if we unify the two paths, because we'll need to run it in a coroutine, as required by tracked_request_begin. While we're at it, use .bdrv_aio_ioctl plus

[Qemu-devel] [PATCH v3 5/9] block: Add ioctl parameter fields to BlockRequest

The two fields that will be used by ioctl handling code later are added as union, because it's used exclusively by ioctl code which dosn't need the four fields in the other struct of the union. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf ---

Re: [Qemu-devel] [PULL 12/22] vhost: rename VHOST_RESET_OWNER to VHOST_RESET_DEVICE

On Fri, Nov 06, 2015 at 10:01:58AM +, Peter Maydell wrote: > On 6 November 2015 at 01:34, Yuanhan Liu wrote: > > On Thu, Nov 05, 2015 at 11:42:15AM +, Peter Maydell wrote: > >> On 3 October 2015 at 17:33, Michael S. Tsirkin wrote: > >> > On

Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

Also, this occur only with rbd_cache=false or qemu drive cache=none. If I use rbd_cache=true or qemu drive cache=writeback, I don't have this bug. - Mail original - De: "aderumier" À: "ceph-devel" , "qemu-devel"

Re: [Qemu-devel] [PATCH v2 1/1] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO)

On 11/05/2015 10:06 AM, Sukadev Bhattiprolu wrote: Implement RTAS_SYSPARM_PROCESSOR_MODULE_INFO parameter to rtas_get_sysparm() call in qemu. This call returns the processor module (socket), chip and core information as specified in section 7.3.16.18 of PAPR v2.7. We walk the /proc/device-tree

[Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

Hi, with qemu (2.4.1), if I do an internal snapshot of an rbd device, then I pause the vm with vm_stop, the qemu process is hanging forever monitor commands to reproduce: # snapshot_blkdev_internal drive-virtio0 yoursnapname # stop I don't see this with qcow2 or sheepdog block driver for

[Qemu-devel] [PATCH v2] virtio-blk: trivial code optimization

From: Gonglei 1. avoid possible superflous checking 2. make code more robustness Signed-off-by: Gonglei --- v2: address Paolo's comments, thanks. --- hw/block/virtio-blk.c | 27 +-- 1 file changed, 9 insertions(+), 18

[Qemu-devel] [PATCH 04/18] armv7m: Explicit error for bad vector table

Give an explicit error and abort when a load from VECBASE fails. Otherwise would likely jump to 0, which for v7-m holds the reset stack pointer address. Signed-off-by: Michael Davidsaver --- target-arm/helper.c | 12 +++- 1 file changed, 11 insertions(+), 1

[Qemu-devel] [PATCH 03/18] armv7m: Complain about incorrect exception table entries.

For -M These should always be thumb mode. Log a message if this is seen. Signed-off-by: Michael Davidsaver --- target-arm/helper.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/target-arm/helper.c b/target-arm/helper.c index 4408100..4178400

[Qemu-devel] [PATCH 02/18] armv7m: Undo armv7m.hack

Add CPU unassigned access handler in place of special MemoryRegion to catch exception returns. Signed-off-by: Michael Davidsaver --- hw/arm/armv7m.c | 8 target-arm/cpu.c | 18 ++ 2 files changed, 18 insertions(+), 8 deletions(-) diff --git

[Qemu-devel] [PATCH 05/18] armv7m: expand NVIC state

Expand the NVIC to fully support -M priorities and masking. Doesn't use GIC code. Move some state to ARMCPU to allow calculation of exception masking. Add storage for PRIGROUP to configure group/sub-group split. Track group and sub-group in separate fields for quick comparison. Mix in vector #

[Qemu-devel] [PATCH 18/18] armv7m: prevent unprivileged write to STIR

Prevent unprivileged from writing to the Software Triggered Interrupt register Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/hw/intc/armv7m_nvic.c b/hw/intc/armv7m_nvic.c index

[Qemu-devel] [PATCH 07/18] armv7m: Update NVIC registers

Replace use of GIC state/functions with new NVIC. Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 233 -- 1 file changed, 168 insertions(+), 65 deletions(-) diff --git a/hw/intc/armv7m_nvic.c

[Qemu-devel] [PATCH 11/18] armv7m: fix I and F flag handling

Despite having the same notation, these bits have completely different meaning than -AR. Add armv7m_excp_unmasked() to calculate the currently runable exception priority taking into account masks and active handlers. Use this in conjunction with the pending exception priority to determine if the

[Qemu-devel] [PATCH 06/18] armv7m: new NVIC utility functions

Internal functions for operations previously done by GIC internals. nvic_irq_update() recalculates highest pending/active exceptions. armv7m_nvic_set_pending() include exception escalation logic. armv7m_nvic_acknowledge_irq() and nvic_irq_update() update ARMCPU fields. Signed-off-by: Michael

[Qemu-devel] [PATCH 09/18] armv7m: NVIC update vmstate

Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 64 +-- 1 file changed, 62 insertions(+), 2 deletions(-) diff --git a/hw/intc/armv7m_nvic.c b/hw/intc/armv7m_nvic.c index 3b10dee..c860b36 100644 ---

[Qemu-devel] [PATCH 12/18] armv7m: simpler/faster exception start

No need to bounce through EXCP_IRQ handling for non-IRQ exceptions. just update CPU state directly. Signed-off-by: Michael Davidsaver --- target-arm/helper.c | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/target-arm/helper.c

[Qemu-devel] [PATCH v2] mirror: Improve zero-write and discard with fragmented image

The "pnum < nb_sectors" condition in deciding whether to actually copy data is unnecessarily strict, and the qiov initialization is unnecessarily too, for both bdrv_aio_write_zeroes and bdrv_aio_discard branches. Reorganize mirror_iteration flow so that we: 1) Find the contiguous

Re: [Qemu-devel] assert during internal snapshot

> -Original Message- > From: Denis V. Lunev [mailto:d...@openvz.org] > Sent: Saturday, November 07, 2015 11:20 PM > To: Li, Liang Z; Paolo Bonzini; Juan Quintela; Amit Shah > Cc: QEMU > Subject: assert during internal snapshot > > Hello, All! > > This commit > > commit

Re: [Qemu-devel] [PATCH v3 2/3] target-i386: calculate vcpu's TSC rate to be migrated

On 11/06/15 13:12, Eduardo Habkost wrote: > On Fri, Nov 06, 2015 at 10:32:24AM +0800, haozhong.zh...@intel.com wrote: > > On 11/05/15 14:05, Eduardo Habkost wrote: > > > On Thu, Nov 05, 2015 at 09:30:51AM +0800, Haozhong Zhang wrote: > > > > On 11/04/15 19:42, Eduardo Habkost wrote: > [...] > > >

[Qemu-devel] [PATCH 16/18] armv7m: check exception return consistency

Detect use of reserved exception return codes and return to thread mode from nested exception handler. Also check consistency between NVIC and CPU wrt. the active exception. Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 7 +++- target-arm/cpu.h | 2

[Qemu-devel] [PATCH v3 9/9] qed: Implement .bdrv_drain

The "need_check_timer" is used to clear the "NEED_CHECK" flag in the image header after a grace period once metadata update has finished. In compliance to the bdrv_drain semantics we should make sure it remains deleted once .bdrv_drain is called. We cannot reuse qed_need_check_timer_cb because

[Qemu-devel] [PATCH 14/18] armv7m: auto-clear FAULTMASK

on return from all exceptions other than NMI Signed-off-by: Michael Davidsaver --- target-arm/helper.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/target-arm/helper.c b/target-arm/helper.c index 5be09b8..83af528 100644 ---

[Qemu-devel] [PATCH 10/18] armv7m: NVIC initialization

Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 107 -- 1 file changed, 51 insertions(+), 56 deletions(-) diff --git a/hw/intc/armv7m_nvic.c b/hw/intc/armv7m_nvic.c index c860b36..8eaf677 100644 ---

[Qemu-devel] [PATCH 17/18] armv7m: implement CCR

Implement Configuration and Control register. Handle STACKALIGN and USERSETMPEND bits. Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 15 +++ target-arm/cpu.h | 1 + target-arm/helper.c | 8 +++- target-arm/machine.c | 1 + 4

[Qemu-devel] [PATCH 13/18] armv7m: implement CFSR and HFSR

Add the Configurable and Hard Fault Status registers. Note undefined instructions and escalations Signed-off-by: Michael Davidsaver --- hw/intc/armv7m_nvic.c | 10 +++--- target-arm/cpu.h | 2 ++ target-arm/helper.c | 1 + target-arm/machine.c | 6 -- 4

Re: [Qemu-devel] [PULL 0/7] Block patches

On Fri, 11/06 18:07, Peter Maydell wrote: > On 6 November 2015 at 17:52, Stefan Hajnoczi wrote: > > The following changes since commit 4b59f39bc9a03afcc74b2fa28da7c3189fca507c: > > > > Merge remote-tracking branch > > 'remotes/mjt/tags/pull-trivial-patches-2015-11-06' into

Re: [Qemu-devel] assert during internal snapshot

> Hello, All! > > This commit > > commit 94f5a43704129ca4995aa3385303c5ae225bde42 > Author: Liang Li > Date: Mon Nov 2 15:37:00 2015 +0800 > > migration: defer migration_end & blk_mig_cleanup > > Because of the patch 3ea3b7fa9af067982f34b of kvm, which

[Qemu-devel] [PATCH v3 4/9] iscsi: Emulate commands in iscsi_aio_ioctl as iscsi_ioctl

iscsi_ioctl emulates SG_GET_VERSION_NUM and SG_GET_SCSI_ID. Now that bdrv_ioctl() will be emulated with .bdrv_aio_ioctl, replicate the logic into iscsi_aio_ioctl to make them consistent. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf --- block/iscsi.c | 40

[Qemu-devel] [PATCH v3 3/9] block: Track discard requests

Both bdrv_discard and bdrv_aio_discard will call into bdrv_co_discard, so add tracked_request_begin/end calls around the loop. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf --- block/io.c | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-)

[Qemu-devel] [PATCH v3 2/9] block: Track flush requests

Both bdrv_flush and bdrv_aio_flush eventually call bdrv_co_flush, add tracked_request_begin and tracked_request_end pair in that function so that all flush requests are now tracked. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf --- block/io.c | 11

Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

Some other infos: I can reproduce it too with manual snapshot with rbd command #rbd --image myrbdvolume snap create --snap snap1 qemu monitor: #stop This is with ceph hammer 0.94.5. in qemu vm_stop, the only thing related to block driver are bdrv_drain_all(); ret =

Re: [Qemu-devel] Qemu: Guest Linux hangs on Mac OS X 10.11

On 18 October 2015 at 21:37, Peter Maydell wrote: > Sometimes it does manage to unwedge itself. Paolo, do you have > any suggestions for how to debug this kind of issue? So the good news is that on mainline this doesn't happen any more. The bad news is that something

Re: [Qemu-devel] [PATCH] virtio-blk: trivial code optimization

On 2015/11/6 20:54, Paolo Bonzini wrote: > > > On 06/11/2015 11:35, Stefan Hajnoczi wrote: if (niov + req->qiov.niov > IOV_MAX) { merge = false; +goto unmerge; } /* merge would exceed maximum

[Qemu-devel] [PATCH v3 1/9] block: Add more types for tracked request

We'll track more request types besides read and write, change the boolean field to an enum. Signed-off-by: Fam Zheng Reviewed-by: Kevin Wolf --- block/io.c| 9 + include/block/block_int.h | 10 +- 2 files changed, 14

[Qemu-devel] [PATCH v3 0/9] block: Fixes for bdrv_drain

v3: Don't reuse coroutine in bdrv_aio_ioctl. [Stefan] Recursely call .bdrv_drain callback only. [Stefan, Paolo] Added Kevin's reviewed-by in other patches. v2: Add Kevin's reviewed-by in patches 1, 2, 5-7, 9. Address Kevin's reviewing comments which are: - Explicit "ret = 0"

Re: [Qemu-devel] assert during internal snapshot

> migration: defer migration_end & blk_mig_cleanup > > Because of the patch 3ea3b7fa9af067982f34b of kvm, which introduces a > lazy collapsing of small sptes into large sptes mechanism, now > migration_end() is a time consuming operation because it calls >

Re: [Qemu-devel] [PATCH v9 00/56] Postcopy implementation

On Fri, Nov 06, 2015 at 03:48:11PM +, Dr. David Alan Gilbert wrote: > * Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote: > > > > Where we have iterable, but non-postcopiable devices (e.g. htab > > > or block migration), complete them before forming the 'package' > > > but with the CPUs

Re: [Qemu-devel] [PATCH v9 00/56] Postcopy implementation

On Fri, Nov 06, 2015 at 12:22:23PM +, Dr. David Alan Gilbert wrote: > * Bharata B Rao (bharata@gmail.com) wrote: > > On Fri, Nov 6, 2015 at 2:39 PM, Dr. David Alan Gilbert > > wrote: > > > * Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote: > > >> On Thu, Nov 05, 2015

Re: [Qemu-devel] [PATCH for-2.5 1/1] spapr: Handle failure of KVM_PPC_ALLOCATE_HTAB ioctl

On Tue, Nov 03, 2015 at 03:38:19PM +0530, Bharata B Rao wrote: > KVM_PPC_ALLOCATE_HTAB ioctl can return -ENOMEM for KVM guests and QEMU > never handled this correctly. But this didn't cause any problems till > now as KVM_PPC_ALLOCATE_HTAB ioctl returned with smaller than requested > HTAB when

Re: [Qemu-devel] [PATCH v7 12/35] util: let qemu_fd_getlength support block device

On 11/06/2015 11:54 PM, Eduardo Habkost wrote: On Mon, Nov 02, 2015 at 05:13:14PM +0800, Xiao Guangrong wrote: lseek can not work for all block devices as the man page says: | Some devices are incapable of seeking and POSIX does not specify | which devices must support lseek(). This patch

Re: [Qemu-devel] [PATCH v6 25/33] nvdimm acpi: build ACPI nvdimm devices

On 11/09/2015 01:38 AM, Michael S. Tsirkin wrote: On Fri, Oct 30, 2015 at 01:56:19PM +0800, Xiao Guangrong wrote: NVDIMM devices is defined in ACPI 6.0 9.20 NVDIMM Devices There is a root device under \_SB and specified NVDIMM devices are under the root device. Each NVDIMM device has _ADR

Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

On 11/09/2015 08:10 AM, Li, Liang Z wrote: since commit commit 94f5a43704129ca4995aa3385303c5ae225bde42 Author: Liang Li Date: Mon Nov 2 15:37:00 2015 +0800 migration: defer migration_end & blk_mig_cleanup when actual .cleanup callbacks calling was

Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

> On 11/09/2015 08:10 AM, Li, Liang Z wrote: > >> since commit > >> commit 94f5a43704129ca4995aa3385303c5ae225bde42 > >> Author: Liang Li > >> Date: Mon Nov 2 15:37:00 2015 +0800 > >> > >> migration: defer migration_end & blk_mig_cleanup > >> > >> when

Re: [Qemu-devel] [PATCH v2] virtio-blk: trivial code optimization

On Mon, 11/09 11:19, arei.gong...@huawei.com wrote: > From: Gonglei > > 1. avoid possible superflous checking > 2. make code more robustness > > Signed-off-by: Gonglei > --- > v2: address Paolo's comments, thanks. > --- > hw/block/virtio-blk.c

[Qemu-devel] [PATCH qemu] spapr: Add /system-id

Section B.6.2.1 Root Node Properties of PAPR specification defines a set of properties which shall be present in the device tree root, one of these properties is "system-id" which "should be unique across all systems and all manufacturers". Since UUID is meant to be unique, it makes sense to use

[Qemu-devel] [PATCH for 2.5 v2 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

since commit commit 94f5a43704129ca4995aa3385303c5ae225bde42 Author: Liang Li Date: Mon Nov 2 15:37:00 2015 +0800 migration: defer migration_end & blk_mig_cleanup when actual .cleanup callbacks calling was removed from complete operations. The patch

Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

On 11/09/2015 10:19 AM, Denis V. Lunev wrote: On 11/09/2015 06:10 AM, Alexandre DERUMIER wrote: Hi, with qemu (2.4.1), if I do an internal snapshot of an rbd device, then I pause the vm with vm_stop, the qemu process is hanging forever monitor commands to reproduce: #

Re: [Qemu-devel] [PATCH COLO-Frame v10 09/38] COLO: Implement colo checkpoint protocol

On 2015/11/9 14:51, zhanghailiang wrote: On 2015/11/7 2:26, Dr. David Alan Gilbert wrote: * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote: We need communications protocol of user-defined to control the checkpoint process. The new checkpoint request is started by Primary VM, and the

Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

CC'ing Liang Li, author of the patch. On (Sat) 07 Nov 2015 [18:40:12], Denis V. Lunev wrote: > since commit > commit 94f5a43704129ca4995aa3385303c5ae225bde42 > Author: Liang Li > Date: Mon Nov 2 15:37:00 2015 +0800 > > migration: defer migration_end &

Re: [Qemu-devel] [PATCH v7 11/35] util: introduce qemu_file_getlength()

On 11/06/2015 11:50 PM, Eduardo Habkost wrote: As this patch affects raw_getlength(), CCing the raw block driver maintainer and the qemu-block mailing list. Eduardo, thanks for your reminder. I will keep CCing Kevin and qemu-block mail list for future version. On Mon, Nov 02, 2015 at

Re: [Qemu-devel] [PATCH v2 1/1] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO)

On Mon, Nov 09, 2015 at 12:57:48PM +1100, Alexey Kardashevskiy wrote: > On 11/05/2015 10:06 AM, Sukadev Bhattiprolu wrote: > >Implement RTAS_SYSPARM_PROCESSOR_MODULE_INFO parameter to rtas_get_sysparm() > >call in qemu. This call returns the processor module (socket), chip and core > >information

Re: [Qemu-devel] [PATCH v2 1/1] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO)

On Wed, Nov 04, 2015 at 03:06:05PM -0800, Sukadev Bhattiprolu wrote: > Implement RTAS_SYSPARM_PROCESSOR_MODULE_INFO parameter to rtas_get_sysparm() > call in qemu. This call returns the processor module (socket), chip and core > information as specified in section 7.3.16.18 of PAPR v2.7. PAPR

Re: [Qemu-devel] [PATCH COLO-Frame v10 06/38] migration: Integrate COLO checkpoint process into loadvm

On 2015/11/7 1:29, Dr. David Alan Gilbert wrote: * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote: Switch from normal migration loadvm process into COLO checkpoint process if COLO mode is enabled. We add three new members to struct MigrationIncomingState, 'have_colo_incoming_thread' and

Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

On 11/09/2015 09:16 AM, Li, Liang Z wrote: On 11/09/2015 08:10 AM, Li, Liang Z wrote: since commit commit 94f5a43704129ca4995aa3385303c5ae225bde42 Author: Liang Li Date: Mon Nov 2 15:37:00 2015 +0800 migration: defer migration_end &

Re: [Qemu-devel] [PATCH COLO-Frame v10 09/38] COLO: Implement colo checkpoint protocol

On 2015/11/7 2:26, Dr. David Alan Gilbert wrote: * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote: We need communications protocol of user-defined to control the checkpoint process. The new checkpoint request is started by Primary VM, and the interactive process like below: Checkpoint

Re: [Qemu-devel] [PATCH 3/3] block/gluster: add support for multiple gluster servers

On Thu, Nov 05, 2015 at 07:45:50 -0500, Prasanna Kumar Kalever wrote: > On Thursday, November 5, 2015 6:07:06 PM, Prasanna Kumar Kalever wrote: > > This patch adds a way to specify multiple volfile servers to the gluster > > block backend of QEMU with tcp|rdma transport types and their port

[Qemu-devel] [PATCH V5] block/nfs: add support for setting debug level

recent libnfs versions support logging debug messages. Add support for it in qemu through an URL parameter. Example: qemu -cdrom nfs://127.0.0.1/iso/my.iso?debug=2 Signed-off-by: Peter Lieven --- v4->v5: add a comment in the code why we limit the debug level [Stefan] v3->v4:

[Qemu-devel] [PATCH for-2.5 v4 3/3] arm: highbank: Implement PSCI and dummy monitor

Firstly, enable monitor mode and PSCI, both of which are features of this board. In addition to PSCI, this board also uses SMC for cache maintenance ops. This means we need a secure monitor to catch these and nop them. Use the ARM boot board-setup feature to implement this. The SMC trap

[Qemu-devel] [PATCH for-2.5 v4 1/3] arm: boot: Add secure_board_setup flag

Add a flag that when set, will cause the primary CPU to start in secure mode, even if the overall boot is non-secure. This is useful for when there is a board-setup blob that needs to run from secure mode, but device and secondary CPU init should still be done as-normal for a non- secure boot.

[Qemu-devel] [PATCH for-2.5 v4 0/3] ARM: Highbank: Highbank: Add monitor support

Hi, This adds dummy monitor support to the Highbank board. It is needed by the Highbank kernel which expects a monitor to be present. A feature is added to arm/boot's board_setup feature, that allows the board_setup entry point to be entered in secure mode (which is needed to configure a

[Qemu-devel] [PATCH for-2.5 v4 2/3] arm: highbank: Defeature CPU override

This board should not support CPU model override. This allows for easier patching of the board with being able to rely on the CPU type being correct. Reviewed-by: Peter Maydell Signed-off-by: Peter Crosthwaite --- hw/arm/highbank.c | 21

Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

On 11/09/2015 06:10 AM, Alexandre DERUMIER wrote: Hi, with qemu (2.4.1), if I do an internal snapshot of an rbd device, then I pause the vm with vm_stop, the qemu process is hanging forever monitor commands to reproduce: # snapshot_blkdev_internal drive-virtio0 yoursnapname # stop I

Re: [Qemu-devel] [PATCH v7 07/35] util: introduce qemu_file_get_page_size()

On 11/06/2015 11:36 PM, Eduardo Habkost wrote: On Mon, Nov 02, 2015 at 05:13:09PM +0800, Xiao Guangrong wrote: There are three places use the some logic to get the page size on the file path or file fd Windows did not support file hugepage, so it will return normal page for this case. And

Re: [Qemu-devel] [PATCH v6 32/33] nvdimm acpi: support _FIT method

On 11/09/2015 01:50 AM, Michael S. Tsirkin wrote: On Fri, Oct 30, 2015 at 01:56:26PM +0800, Xiao Guangrong wrote: FIT buffer is not completely mapped into guest address space, so a new function, Read FIT, function index 0x, is reserved by QEMU to read the piece of FIT buffer. The

[Qemu-devel] [PATCH for-2.5 v4 1/1] hw/misc: Add support for ADC controller in Xilinx Zynq 7000

From: Guenter Roeck Add support for the Xilinx XADC core used in Zynq 7000. References: - Zynq-7000 All Programmable SoC Technical Reference Manual - 7 Series FPGAs and Zynq-7000 All Programmable SoC XADC Dual 12-Bit 1 MSPS Analog-to-Digital Converter Tested with Linux

Re: [Qemu-devel] [PULL 0/7] Block patches

Fam Zheng writes: > On Fri, 11/06 18:07, Peter Maydell wrote: >> On 6 November 2015 at 17:52, Stefan Hajnoczi wrote: >> > The following changes since commit >> > 4b59f39bc9a03afcc74b2fa28da7c3189fca507c: >> > >> > Merge remote-tracking branch >> >

Re: [Qemu-devel] qemu : rbd block driver internal snapshot and vm_stop is hanging forever

Something is really wrong, because guest is also freezing, with a simple snapshot, with cache=none / rbd_cache=false qemu monitor : snapshot_blkdev_internal drive-virtio0 snap1 or rbd command : rbd --image myrbdvolume snap create --snap snap1 Then the guest can't read/write to disk

Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation

> since commit > commit 94f5a43704129ca4995aa3385303c5ae225bde42 > Author: Liang Li > Date: Mon Nov 2 15:37:00 2015 +0800 > > migration: defer migration_end & blk_mig_cleanup > > when actual .cleanup callbacks calling was removed from complete operations.

Re: [Qemu-devel] [PATCH] hw/arm/virt: error_report cleanups

Peter Maydell writes: > On 7 November 2015 at 15:25, Andrew Jones wrote: >> Signed-off-by: Andrew Jones >> --- >> hw/arm/virt.c | 10 +- >> 1 file changed, 5 insertions(+), 5 deletions(-) >> >> diff --git

Re: [Qemu-devel] [PATCH] exec: silence hugetlbfs warning under qtest

"Michael S. Tsirkin" writes: > On Tue, Oct 27, 2015 at 05:29:43PM +0100, marcandre.lur...@redhat.com wrote: >> From: Marc-André Lureau >> >> vhost-user-test prints a warning. A test should not need to run on >> hugetlbfs, let's silence the warning