Re: [Qemu-devel] Can qemu run on the ARM hardware?

> -Original Message- > From: Qemu-devel > [mailto:qemu-devel-bounces+wangjintang=huawei@nongnu.org] On > Behalf Of liangy...@zhwei.com > Sent: Wednesday, March 29, 2017 10:53 AM > To: qemu-devel > Subject: [Qemu-devel] Can qemu run on the ARM hardware? > > Dear QEMU Community, > > I

Re: [Qemu-devel] [PATCH 1/1] target/ppc: Improve accuracy of guest HTM availability on P8s

On Wed, Mar 29, 2017 at 04:01:28PM +1100, Sam Bobroff wrote: > On Power8 hosts it is currently theoretically possible for QEMU/KVM-HV guests > to receive a ibm,pa-features property indicating that HTM support is available > when it is not. The situation would occur if the platform firmware of > a

Re: [Qemu-devel] [PATCH qemu] spapr_pci: Removed unused include

On Wed, Mar 29, 2017 at 04:09:58PM +1100, Alexey Kardashevskiy wrote: > Signed-off-by: Alexey Kardashevskiy > --- > > This leftover is just confusing :) Applied to ppc-for-2.10. > > > --- > hw/ppc/spapr_pci.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git

Re: [Qemu-devel] [PATCH v4 1/8] xen: import ring.h from xen

On 29/03/17 01:54, Stefano Stabellini wrote: > On Tue, 28 Mar 2017, Juergen Gross wrote: >> On 28/03/17 00:48, Stefano Stabellini wrote: >>> On Mon, 27 Mar 2017, Juergen Gross wrote: On 24/03/17 18:37, Stefano Stabellini wrote: > On Fri, 24 Mar 2017, Juergen Gross wrote: >> On

Re: [Qemu-devel] [PATCH 1/1] target/ppc: Improve accuracy of guest HTM availability on P8s

On 29.03.2017 07:01, Sam Bobroff wrote: > On Power8 hosts it is currently theoretically possible for QEMU/KVM-HV guests > to receive a ibm,pa-features property indicating that HTM support is available > when it is not. The situation would occur if the platform firmware of > a Power8 host cleared

Re: [Qemu-devel] [PATCH v3 7/8] ppc/pnv: link the CPUs to the machine XICSFabric

On Tue, Mar 28, 2017 at 09:32:31AM +0200, Cédric Le Goater wrote: > This assigns the ICPState object to the CPU using the PIR number for > lookups before calling the XICS layer to finish the job. > > Signed-off-by: Cédric Le Goater > Reviewed-by: David Gibson

Re: [Qemu-devel] [PATCH v3 5/8] ppc/pnv: create the ICP and ICS objects under the machine

On Tue, Mar 28, 2017 at 09:32:29AM +0200, Cédric Le Goater wrote: > Like this is done for the sPAPR machine, we use a simple array under > the PowerNV machine to store the Interrupt Control Presenters (ICP) > objects, one for each vCPU. This array is indexed by 'cpu_index' of > the CPUState but

Re: [Qemu-devel] [PATCH qemu] spapr_pci: Warn when RAM page size is not enabled in IOMMU page mask

On Tue, Mar 28, 2017 at 07:13:49PM +1100, Alexey Kardashevskiy wrote: > If a page size used by QEMU is not enabled in the PHB IOMMU page mask, > in-kernel acceleration of TCE handling won't be enabled and performance > might be slower than expected. > > This prints a warning if system page size

[Qemu-devel] [PATCH qemu] spapr_pci: Removed unused include

Signed-off-by: Alexey Kardashevskiy --- This leftover is just confusing :) --- hw/ppc/spapr_pci.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/hw/ppc/spapr_pci.c b/hw/ppc/spapr_pci.c index 097ebdd51d..e7567e2e8f 100644 --- a/hw/ppc/spapr_pci.c +++ b/hw/ppc/spapr_pci.c

Re: [Qemu-devel] [RFC PATCH qemu 1/3] memory: Add get_fd() hook for IOMMU MR

On 29/03/17 14:35, David Gibson wrote: > On Tue, Mar 28, 2017 at 11:48:29AM -0600, Alex Williamson wrote: >> On Tue, 28 Mar 2017 20:05:28 +1100 >> Alexey Kardashevskiy wrote: >> >>> Signed-off-by: Alexey Kardashevskiy >>> --- >>> include/exec/memory.h | 2 ++ >>>

[Qemu-devel] [PATCH 0/1] target/ppc: Improve accuracy of guest HTM availability on P8s

Hi QEMU, See the patch itself for a description of the issue it's fixing. Additionally, I've done some investigation on the effect of the patch on older kernels. The discussion below only refers to the situation in which the existing workaround would have an effect (system is P8, KVM is HV and

[Qemu-devel] [PATCH 1/1] target/ppc: Improve accuracy of guest HTM availability on P8s

On Power8 hosts it is currently theoretically possible for QEMU/KVM-HV guests to receive a ibm,pa-features property indicating that HTM support is available when it is not. The situation would occur if the platform firmware of a Power8 host cleared the HTM bit of the ibm,pa-features property.

Re: [Qemu-devel] [PATCH] e1000: disable debug by default

On 2017年03月22日 11:07, Jason Wang wrote: Disable debug output by default, the information were not needed for release. Cc: Peter Maydell Cc: Stefan Hajnoczi Cc: Leonid Bloch Cc: Dmitry Fleytman

Re: [Qemu-devel] [PATCH for 2.9?] tap-win32: don't abort in tap_enable(); enables -netdev tap

On 2017年03月29日 12:13, Andrew Baumann via Qemu-devel wrote: From: Jason Wang [mailto:jasow...@redhat.com] Sent: Tuesday, 28 March 2017 19:39 On 2017年03月29日 02:55, Andrew Baumann wrote: From: Stefan Weil [mailto:s...@weilnetz.de] Sent: Tuesday, 28 March 2017 11:28 Am 25.03.2017 um 00:46

Re: [Qemu-devel] [RFC for-2.10 3/3] pseries: Allow PCIe virtio and XHCI on pseries machine type

On Wed, Mar 29, 2017 at 01:20:50PM +1100, Alexey Kardashevskiy wrote: > On 28/03/17 13:16, David Gibson wrote: > > pseries now allows PCIe devices (both emulated and VFIO), although its > > PCI bus is in most respects a plain PCI bus - this uses paravirtualized > > access methods to PCIe extended

Re: [Qemu-devel] [PATCH v3 1/8] ppc/xics: introduce an 'icp' backlink under PowerPCCPU

On Tue, Mar 28, 2017 at 09:32:25AM +0200, Cédric Le Goater wrote: > Today, the ICPState array of the sPAPR machine is indexed with > 'cpu_index' of the CPUState. This numbering of CPUs is internal to > QEMU and the guest only knows about what is exposed in the device > tree, that is the

[Qemu-devel] [PATCH] tcg/i386: Display AMD HT warning only for KVM

TCG uses the AMD cpu which warns when we use hyperthreading. Disable the warning for TCG since it is not necessary. Signed-off-by: Pranith Kumar --- target/i386/cpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/i386/cpu.c b/target/i386/cpu.c

Re: [Qemu-devel] [RFC PATCH qemu 3/3] vfio: Enable in-kernel acceleration via VFIO KVM device

On 29/03/17 04:48, Alex Williamson wrote: > On Tue, 28 Mar 2017 20:05:30 +1100 > Alexey Kardashevskiy wrote: > >> This enables in-kernel acceleration of TCE update requests via >> VFIO KVM device. >> >> Signed-off-by: Alexey Kardashevskiy >> --- >>

Re: [Qemu-devel] [PATCH for 2.9?] tap-win32: don't abort in tap_enable(); enables -netdev tap

> From: Jason Wang [mailto:jasow...@redhat.com] > Sent: Tuesday, 28 March 2017 19:39 > > On 2017年03月29日 02:55, Andrew Baumann wrote: > >> From: Stefan Weil [mailto:s...@weilnetz.de] > >> Sent: Tuesday, 28 March 2017 11:28 > >> Am 25.03.2017 um 00:46 schrieb Andrew Baumann: > >>> The docs

[Qemu-devel] [PATCH for 2.9] vhost: generalize iommu memory region

We assumes the iommu_ops were attached to the root region of address space. This may not be true for all kinds of IOMMU implementation and especially after commit 3716d5902d74 ("pci: introduce a bus master container"). So fix this by not assuming as->root has iommu_ops, instead depending on the

Re: [Qemu-devel] [RFC PATCH qemu 3/3] vfio: Enable in-kernel acceleration via VFIO KVM device

On Tue, Mar 28, 2017 at 08:05:30PM +1100, Alexey Kardashevskiy wrote: > This enables in-kernel acceleration of TCE update requests via > VFIO KVM device. > > Signed-off-by: Alexey Kardashevskiy > --- > include/hw/vfio/vfio-common.h | 1 + > target/ppc/kvm_ppc.h | 6

Re: [Qemu-devel] [RFC PATCH qemu 1/3] memory: Add get_fd() hook for IOMMU MR

On Tue, Mar 28, 2017 at 11:48:29AM -0600, Alex Williamson wrote: > On Tue, 28 Mar 2017 20:05:28 +1100 > Alexey Kardashevskiy wrote: > > > Signed-off-by: Alexey Kardashevskiy > > --- > > include/exec/memory.h | 2 ++ > > hw/ppc/spapr_iommu.c | 8 > > 2

Re: [Qemu-devel] [RFC PATCH qemu 2/3] vfio-pci: Reorder group-to-container attaching

On Tue, Mar 28, 2017 at 11:48:36AM -0600, Alex Williamson wrote: > On Tue, 28 Mar 2017 20:05:29 +1100 > Alexey Kardashevskiy wrote: > > > At the moment VFIO PCI device initialization works as follows: > > vfio_realize > > vfio_get_group > > vfio_connect_container

[Qemu-devel] [PULL 1/2] spapr: fix buffer-overflow

From: Marc-André Lureau Running postcopy-test with ASAN produces the following error: QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 tests/postcopy-test ... = ==23641==ERROR: AddressSanitizer:

[Qemu-devel] [PULL 0/2] ppc-for-2.9 queue 20170329

The following changes since commit df9046363220e57d45818312759b954c033c58ab: Update version for v2.9.0-rc2 release (2017-03-28 19:11:16 +0100) are available in the git repository at: git://github.com/dgibson/qemu.git tags/ppc-for-2.9-20170329 for you to fetch changes up to

[Qemu-devel] [PULL 2/2] spapr: fix memory hot-unplugging

From: Laurent Vivier If, once the kernel has booted, we try to remove a memory hotplugged while the kernel was not started, QEMU crashes on an assert: qemu-system-ppc64: hw/virtio/vhost.c:651: vhost_commit: Assertion `r >= 0' failed. ... #4

[Qemu-devel] Can qemu run on the ARM hardware?

Dear QEMU Community, I am a newbie for the QEMU. I have some questions to ask for you, My hardware is an arm board and installed with ubuntu Linux OS. i have some code must run on the x86 platform. so i want to install a vm software like the VMware and VirtualBox on the arm board and

Re: [Qemu-devel] host stalls when qemu-system-aarch64 with kvm and pflash

Hi Radha, On Tue, Mar 28, 2017 at 12:58:24PM -0700, Radha Mohan wrote: > Hi, > I am seeing an issue with qemu-system-aarch64 when using pflash > (booting kernel via UEFI bios). > > Host kernel: 4.11.0-rc3-next-20170323 > Qemu version: v2.9.0-rc1 > > Command used: >

Re: [Qemu-devel] [RFC PATCH qemu 1/3] memory: Add get_fd() hook for IOMMU MR

On Wed, 29 Mar 2017 12:41:01 +1100 Alexey Kardashevskiy wrote: > On 29/03/17 04:48, Alex Williamson wrote: > > On Tue, 28 Mar 2017 20:05:28 +1100 > > Alexey Kardashevskiy wrote: > > > >> Signed-off-by: Alexey Kardashevskiy > >> --- > >>

Re: [Qemu-devel] [PATCH fixup 2/2] vhost: genearlize iommu memory region

On 2017年03月21日 09:39, Peter Xu wrote: On Mon, Mar 20, 2017 at 08:21:44PM -0500, Eric Blake wrote: On 03/20/2017 08:12 PM, Michael S. Tsirkin wrote: Since this patchset depends on vtd vfio series and fixes its breakage to vhost, I'll pick them up for consistency for next post of vtd vfio

Re: [Qemu-devel] [PATCH v3 3/3] vfio-pci: process non fatal error of AER

On Wed, 29 Mar 2017 02:59:34 +0300 "Michael S. Tsirkin" wrote: > On Tue, Mar 28, 2017 at 10:12:25AM -0600, Alex Williamson wrote: > > On Tue, 28 Mar 2017 21:49:17 +0800 > > Cao jin wrote: > > > > > On 03/25/2017 06:12 AM, Alex Williamson wrote: >

Re: [Qemu-devel] [PATCH v6] vfio error recovery: kernel support

On Wed, 29 Mar 2017 03:01:48 +0300 "Michael S. Tsirkin" wrote: > On Tue, Mar 28, 2017 at 10:12:33AM -0600, Alex Williamson wrote: > > On Tue, 28 Mar 2017 21:47:00 +0800 > > Cao jin wrote: > > > > > On 03/25/2017 06:12 AM, Alex Williamson wrote: >

Re: [Qemu-devel] [PATCH for-2.10 05/23] numa: move source of default CPUs to NUMA node mapping into boards

On Tue, Mar 28, 2017 at 12:53:10PM +0200, Igor Mammedov wrote: > On Tue, 28 Mar 2017 15:19:20 +1100 > David Gibson wrote: > > > On Wed, Mar 22, 2017 at 02:32:30PM +0100, Igor Mammedov wrote: > > > Originally CPU threads were by default assigned in > > > round-robin

Re: [Qemu-devel] [PATCH for-2.10 22/23] numa: add '-numa cpu, ...' option for property based node mapping

On Tue, Mar 28, 2017 at 01:09:11PM +0200, Igor Mammedov wrote: > On Tue, 28 Mar 2017 16:16:02 +1100 > David Gibson wrote: > > > On Wed, Mar 22, 2017 at 02:32:47PM +0100, Igor Mammedov wrote: > > > legacy cpu to node mapping is using cpu index values to map > > > VCPU

Re: [Qemu-devel] [PATCH qemu] pci: Add missing drop of bus master AS reference

On 2017年03月27日 12:40, Alexey Kardashevskiy wrote: The recent introduction of a bus master container added memory_region_add_subregion() into the PCI device registering path but missed memory_region_del_subregion() in the unregistering path leaving a reference to the root memory region of the

Re: [Qemu-devel] [PATCH for 2.9?] tap-win32: don't abort in tap_enable(); enables -netdev tap

On 2017年03月29日 02:55, Andrew Baumann wrote: From: Stefan Weil [mailto:s...@weilnetz.de] Sent: Tuesday, 28 March 2017 11:28 Am 25.03.2017 um 00:46 schrieb Andrew Baumann: The docs generally steer users away from using the legacy -net parameter, however on win32 attempting to enable a tap

[Qemu-devel] Python support in Risu

I was wondering if someone wrote a risugen_*.pm file in python and it still worked with risugen, would you accept that patch?

Re: [Qemu-devel] [RFC for-2.10 3/3] pseries: Allow PCIe virtio and XHCI on pseries machine type

On 28/03/17 13:16, David Gibson wrote: > pseries now allows PCIe devices (both emulated and VFIO), although its > PCI bus is in most respects a plain PCI bus - this uses paravirtualized > access methods to PCIe extended config space defined in the PAPR spec. > > However, because the bus is not

Re: [Qemu-devel] [RFC PATCH qemu 1/3] memory: Add get_fd() hook for IOMMU MR

On 29/03/17 04:48, Alex Williamson wrote: > On Tue, 28 Mar 2017 20:05:28 +1100 > Alexey Kardashevskiy wrote: > >> Signed-off-by: Alexey Kardashevskiy >> --- >> include/exec/memory.h | 2 ++ >> hw/ppc/spapr_iommu.c | 8 >> 2 files changed, 10

Re: [Qemu-devel] [PATCH v2] spapr: fix memory hot-unplugging

On Tue, Mar 28, 2017 at 02:09:34PM +0200, Laurent Vivier wrote: > If, once the kernel has booted, we try to remove a memory > hotplugged while the kernel was not started, QEMU crashes on > an assert: > > qemu-system-ppc64: hw/virtio/vhost.c:651: >vhost_commit:

[Qemu-devel] [PULL 2/3] pci: Add missing drop of bus master AS reference

From: Alexey Kardashevskiy The recent introduction of a bus master container added memory_region_add_subregion() into the PCI device registering path but missed memory_region_del_subregion() in the unregistering path leaving a reference to the root memory region of the new

[Qemu-devel] [PULL 3/3] virtio: fix vring_align() on 64-bit windows

From: Andrew Baumann long is 32-bits on 64-bit windows, which caused the top half of the address to be truncated; this patch changes it to use the QEMU_ALIGN_UP macro which does not suffer the same problem Signed-off-by: Andrew Baumann

[Qemu-devel] [PULL 0/3] virtio, pci: fixes

The following changes since commit df9046363220e57d45818312759b954c033c58ab: Update version for v2.9.0-rc2 release (2017-03-28 19:11:16 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream for you to fetch changes up to

[Qemu-devel] [PULL 1/3] event_notifier: prevent accidental use after close

From: Halil Pasic Let's set the handles to the underlying facilities to their extremal value so no accidental misuse can happen, and to make it obvious that the notifier is dysfunctional. E.g. if we just close an fd but do not touch the int holding the fd eventually a

[Qemu-devel] [PATCH v3 0/1] block: pass the right options for BlockDriver.bdrv_open()

Trying to restore rbd image on ceph cluster from snapshot with qemu-img could trigger a calling to raw_open with a NULL @options, and that will lead to a failure of the snapshot applying. [root@s8345007 ~]# gdb --args qemu-img snapshot -a snap1 rbd:test_pool/dj_image ... ... Program received

[Qemu-devel] [PATCH v3 1/1] block: pass the right options for BlockDriver.bdrv_open()

raw_open() expects the caller always passing in the right actual @options parameter. But when trying to applying snapshot on a RBD image, bdrv_snapshot_goto() calls raw_open() (by calling the bdrv_open callback on the BlockDriver) with a NULL @options, and that will result in a Segmentation fault.

Re: [Qemu-devel] [PATCH 3/4] savevm: fix savevm after migration

On 03/28/2017 01:55 PM, Dr. David Alan Gilbert wrote: > * Kevin Wolf (kw...@redhat.com) wrote: >> Am 25.02.2017 um 20:31 hat Vladimir Sementsov-Ogievskiy geschrieben: >>> After migration all drives are inactive and savevm will fail with >>> >>> qemu-kvm: block/io.c:1406: bdrv_co_do_pwritev: >>>

Re: [Qemu-devel] [PATCH for 2.9 1/1] block: add missed aio_context_acquire into release_drive

On Tue, 03/28 19:12, Denis V. Lunev wrote: > Recently we expirience hang with iothreads enabled with the following > call trace: > Thread 1 (Thread 0x7fa95efebc80 (LWP 177117)): > 0 ppoll () from /lib64/libc.so.6 > 2 qemu_poll_ns () at qemu-timer.c:313 > 3 aio_poll () at aio-posix.c:457 > 4

Re: [Qemu-devel] [PATCH v6] vfio error recovery: kernel support

On Tue, Mar 28, 2017 at 10:12:33AM -0600, Alex Williamson wrote: > On Tue, 28 Mar 2017 21:47:00 +0800 > Cao jin wrote: > > > On 03/25/2017 06:12 AM, Alex Williamson wrote: > > > On Thu, 23 Mar 2017 17:07:31 +0800 > > > Cao jin wrote: > > > >

Re: [Qemu-devel] [PATCH v3 3/3] vfio-pci: process non fatal error of AER

On Tue, Mar 28, 2017 at 10:12:25AM -0600, Alex Williamson wrote: > On Tue, 28 Mar 2017 21:49:17 +0800 > Cao jin wrote: > > > On 03/25/2017 06:12 AM, Alex Williamson wrote: > > > On Thu, 23 Mar 2017 17:09:23 +0800 > > > Cao jin wrote: > > >

Re: [Qemu-devel] [PATCH v4 1/8] xen: import ring.h from xen

On Tue, 28 Mar 2017, Juergen Gross wrote: > On 28/03/17 00:48, Stefano Stabellini wrote: > > On Mon, 27 Mar 2017, Juergen Gross wrote: > >> On 24/03/17 18:37, Stefano Stabellini wrote: > >>> On Fri, 24 Mar 2017, Juergen Gross wrote: > On 23/03/17 19:22, Stefano Stabellini wrote: > > On

Re: [Qemu-devel] [PATCH v2] xen: additionally restrict xenforeignmemory operations

On Tue, 28 Mar 2017, Paul Durrant wrote: > Commit f0f272baf3a7 "xen: use libxendevice model to restrict operations" > added a command-line option (-xen-domid-restrict) to limit operations > using the libxendevicemodel API to a specified domid. The commit also > noted that the restriction would be

[Qemu-devel] [PULL 2/3] slirp: Make RA build more flexible

Do not hardcode the RA size at all, use a pl_size variable which accounts the accumulated size, and fill rip->ip_pl at the end. This will allow to make some blocks optional. Signed-off-by: Samuel Thibault Reviewed-by: Philippe Mathieu-Daudé ---

[Qemu-devel] [PULL 1/3] slirp: fix compilation errors with DEBUG set

From: Laurent Vivier slirp/slirp.c: In function 'get_dns_addr_resolv_conf': slirp/slirp.c:202:29: error: initialization discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers] char *res = inet_ntop(af, tmp_addr, s, sizeof(s));

[Qemu-devel] [PULL 3/3] slirp: Send RDNSS in RA only if host has an IPv6 DNS server

Previously we would always send an RDNSS option in the RA, making the guest try to resolve DNS through IPv6, even if the host does not actually have and IPv6 DNS server available. This makes the RDNSS option enabled only when an IPv6 DNS server is available. Signed-off-by: Samuel Thibault

[Qemu-devel] [PULL 0/3] slirp updates

The following changes since commit df9046363220e57d45818312759b954c033c58ab: Update version for v2.9.0-rc2 release (2017-03-28 19:11:16 +0100) are available in the git repository at: http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault for you to fetch changes up to

[Qemu-devel] [ANNOUNCE] QEMU 2.9.0-rc2 is now available

Hello, On behalf of the QEMU Team, I'd like to announce the availability of the third release candidate for the QEMU 2.9 release. This release is meant for testing purposes and should not be used in a production environment. http://download.qemu-project.org/qemu-2.9.0-rc2.tar.xz

Re: [Qemu-devel] [PATCH 1/1] parallels: wrong call to bdrv_truncate

On 03/28/2017 07:26 PM, Kevin Wolf wrote: > [ Cc: qemu-block ] > > Am 27.03.2017 um 16:38 hat Denis V. Lunev geschrieben: >> Parallels driver should not call bdrv_truncate if the image was opened >> in the read-only mode. Without the patch >> qemu-img check harddisk.hds >> asserts with >>

Re: [Qemu-devel] [RFC v3 2/3] hw/intc/arm_gicv3_its: Implement state save/restore

On 28 March 2017 at 20:45, Juan Quintela wrote: > Let me see if I understood this correctly. > > We have an ARM_GICV3_ITS_COMMON. And that has some fields. > In particular: > > struct GICv3ITSState { > /* Registers */ > uint32_t ctlr; > uint64_t cbaser; >

Re: [Qemu-devel] [PATCH v3 for-2.10 0/4] block: Add errp to b{lk, drv}_truncate()

On 28.03.2017 22:51, Max Reitz wrote: > Having an Error parameter for these functions makes sense because we > sometimes want a bit more information than just "Something failed". Some > drivers already use error_report() and the like to emit this additional > information, so it's rather obvious

[Qemu-devel] [PATCH v3 for-2.10 4/4] block: Add .bdrv_truncate() error messages

Add missing error messages for the block driver implementations of .bdrv_truncate(); drop the generic one from block.c's bdrv_truncate(). Since one of these changes touches a mis-indented block in block/file-posix.c, this patch fixes that coding style issue along the way. Signed-off-by: Max

[Qemu-devel] [PATCH v3 for-2.10 3/4] block: Add errp to BD.bdrv_truncate()

Add an Error parameter to the block drivers' bdrv_truncate() interface. If a block driver does not set this in case of an error, the generic bdrv_truncate() implementation will do so. Where it is obvious, this patch also makes some block drivers set this value. Signed-off-by: Max Reitz

[Qemu-devel] [PATCH v3 for-2.10 2/4] block: Add errp to b{lk, drv}_truncate()

For one thing, this allows us to drop the error message generation from qemu-img.c and blockdev.c and instead have it unified in bdrv_truncate(). Signed-off-by: Max Reitz --- include/block/block.h | 2 +- include/sysemu/block-backend.h | 2 +- block.c

[Qemu-devel] [PATCH v3 for-2.10 0/4] block: Add errp to b{lk, drv}_truncate()

Having an Error parameter for these functions makes sense because we sometimes want a bit more information than just "Something failed". Some drivers already use error_report() and the like to emit this additional information, so it's rather obvious that we do want a real error object here. v3:

[Qemu-devel] [PATCH v3 for-2.10 1/4] block/vhdx: Make vhdx_create() always set errp

This patch makes vhdx_create() always set errp in case of an error. It also adds errp parameters to vhdx_create_bat() and vhdx_create_new_region_table() so we can pass on the error object generated by blk_truncate() as of a future commit. Signed-off-by: Max Reitz Reviewed-by:

Re: [Qemu-devel] host stalls when qemu-system-aarch64 with kvm and pflash

On Tue, Mar 28, 2017 at 1:16 PM, Christoffer Dall wrote: > Hi Radha, > > On Tue, Mar 28, 2017 at 12:58:24PM -0700, Radha Mohan wrote: >> Hi, >> I am seeing an issue with qemu-system-aarch64 when using pflash >> (booting kernel via UEFI bios). >> >> Host kernel:

Re: [Qemu-devel] [PATCH v3 for-2.9] virtio: fix vring_align() on 64-bit windows

Am 28.03.2017 um 22:11 schrieb Michael S. Tsirkin: I'm doing a pull request a bit later today - I can pick this one up if you prefer. If yes, pls send your ack. Yes, please. Thanks a lot Stefan

Re: [Qemu-devel] [PATCH v3 for-2.9] virtio: fix vring_align() on 64-bit windows

On Tue, Mar 28, 2017 at 10:02:10PM +0200, Stefan Weil wrote: > Am 28.03.2017 um 20:56 schrieb Andrew Baumann: > > > From: Eric Blake [mailto:ebl...@redhat.com] > > > Sent: Tuesday, 28 March 2017 11:52 > > > > > > On 03/28/2017 01:38 PM, Stefan Weil wrote: > > > > Am 25.03.2017 um 00:19 schrieb

Re: [Qemu-devel] [PATCH v3 for-2.9] virtio: fix vring_align() on 64-bit windows

Am 28.03.2017 um 20:56 schrieb Andrew Baumann: From: Eric Blake [mailto:ebl...@redhat.com] Sent: Tuesday, 28 March 2017 11:52 On 03/28/2017 01:38 PM, Stefan Weil wrote: Am 25.03.2017 um 00:19 schrieb Andrew Baumann: long is 32-bits on 64-bit windows, which caused the top half of the address

Re: [Qemu-devel] [PATCH v3] virtio: fix vring_align() on 64-bit windows

On Fri, Mar 24, 2017 at 04:19:43PM -0700, Andrew Baumann wrote: > long is 32-bits on 64-bit windows, which caused the top half of the > address to be truncated; this patch changes it to use the > QEMU_ALIGN_UP macro which does not suffer the same problem > > Signed-off-by: Andrew Baumann

Re: [Qemu-devel] [PULL for-2.9] block: Declare blockdev-add and blockdev-del supported

On 28.03.2017 20:49, Markus Armbruster wrote: > Paolo Bonzini writes: > >> On 28/03/2017 15:45, Markus Armbruster wrote: >>> It's been a long journey, but here we are. >>> >>> The supported blockdev-add is not compatible to its experimental >>> predecessors; bump all Since:

[Qemu-devel] host stalls when qemu-system-aarch64 with kvm and pflash

Hi, I am seeing an issue with qemu-system-aarch64 when using pflash (booting kernel via UEFI bios). Host kernel: 4.11.0-rc3-next-20170323 Qemu version: v2.9.0-rc1 Command used: ./aarch64-softmmu/qemu-system-aarch64 -cpu host -enable-kvm -M virt,gic_version=3 -nographic -smp 1 -m 2048 -drive

[Qemu-devel] [PULL 2/2] i386: Don't override -cpu options on -cpu host/max

The existing code for "host" and "max" CPU models overrides every single feature in the CPU object at realize time, even the ones that were explicitly enabled or disabled by the user using "feat=on" or "feat=off", while features set using +feat/-feat are kept. This means "-cpu host,+invtsc" works

[Qemu-devel] [PULL 0/2] i386: Fix for "-cpu host,invtsc=on" bug

Last-minute fix for a bug found by Jiri Denemark. Unfortunately not in time for -rc2, but I would like to get this in -rc3. The following changes since commit df9046363220e57d45818312759b954c033c58ab: Update version for v2.9.0-rc2 release (2017-03-28 19:11:16 +0100) are available in the git

[Qemu-devel] [PULL 1/2] i386: Replace uint32_t* with FeatureWord on feature getter/setter

Instead of passing a pointer to the feature property getter and setter functions, pass a FeatureWord enum so they can perform other actions related to the feature flag. This will be used to add a new "user_features" field to keep track of features that were explicitly set by the user.

Re: [Qemu-devel] [RFC v3 3/3] hw/intc/arm_gicv3_its: Allow save/restore

Eric Auger wrote: > We change the restoration priority of both the GICv3 and ITS. The > GICv3 must be restored before the ITS and the ITS needs to be restored > before PCIe devices since it translates their MSI transactions. > > Signed-off-by: Eric Auger

Re: [Qemu-devel] [RFC v3 2/3] hw/intc/arm_gicv3_its: Implement state save/restore

Eric Auger wrote: > We need to handle both registers and ITS tables. While > register handling is standard, ITS table handling is more > challenging since the kernel API is devised so that the > tables are flushed into guest RAM and not in vmstate buffers. > > Flushing the

Re: [Qemu-devel] [PATCH v2 for-2.10 0/4] block: Add errp to b{lk, drv}_truncate()

On 23.03.2017 19:05, Kevin Wolf wrote: > Am 08.03.2017 um 20:14 hat Max Reitz geschrieben: >> Having an Error parameter for these functions makes sense because we >> sometimes want a bit more information than just "Something failed". Some >> drivers already use error_report() and the like to emit

Re: [Qemu-devel] QEMU website (wiki) improvements

Am 23.01.2017 um 11:28 schrieb Stefan Hajnoczi: On Sun, Jan 22, 2017 at 04:19:43PM +0100, Stefan Weil wrote: On 03/02/15 23:12, Stefan Hajnoczi wrote: On Sat, Feb 28, 2015 at 04:29:44PM +0100, Stefan Weil wrote: * It does not support secure access (https), so each login is insecure. Can we

Re: [Qemu-devel] [PATCH v2 for-2.10 3/4] block: Add errp to BD.bdrv_truncate()

On 23.03.2017 19:00, Kevin Wolf wrote: > Am 08.03.2017 um 20:15 hat Max Reitz geschrieben: >> Add an Error parameter to the block drivers' bdrv_truncate() interface. >> If a block driver does not set this in case of an error, the generic >> bdrv_truncate() implementation will do so. >> >> Where it

Re: [Qemu-devel] [PATCH v2 for-2.10 4/4] block: Add some bdrv_truncate() error messages

On 23.03.2017 19:03, Kevin Wolf wrote: > Am 08.03.2017 um 20:15 hat Max Reitz geschrieben: >> Add missing error messages for the drivers I am comfortable to do this >> in. >> >> Since one of these changes touches a mis-indented block in >> block/file-posix.c, this patch fixes that coding style

Re: [Qemu-devel] [PATCH v2 for-2.10 2/4] block: Add errp to b{lk, drv}_truncate()

On 23.03.2017 18:46, Kevin Wolf wrote: > Am 08.03.2017 um 20:14 hat Max Reitz geschrieben: >> For one thing, this allows us to drop the error message generation from >> qemu-img.c and blockdev.c and instead have it unified in >> bdrv_truncate(). >> >> Signed-off-by: Max Reitz >

Re: [Qemu-devel] [PATCH v3 for-2.9?] virtio: fix vring_align() on 64-bit windows

Am 28.03.2017 um 20:56 schrieb Andrew Baumann: From: Eric Blake [mailto:ebl...@redhat.com] Is this needed for 2.9? Yes, it's a correctness bug that avoids miscompilation on 64-bit targets where long is 32 bits (which, at the moment, is really just Windows). I agree, this should be in 2.9. I

Re: [Qemu-devel] [PATCH v3 for-2.9?] virtio: fix vring_align() on 64-bit windows

Hi, I never received Andrew Baumann's mail via the ML... On 03/28/2017 03:38 PM, Stefan Weil wrote: Am 25.03.2017 um 00:19 schrieb QEMU_ALIGN_UP: long is 32-bits on 64-bit windows, which caused the top half of the address to be truncated; this patch changes it to use the QEMU_ALIGN_UP macro

[Qemu-devel] [PATCH v2 1/1] slirp: add SOCKS5 support

When the VM is used behind a firewall, This allows the use of a SOCKS5 proxy server to connect the VM IP stack directly to the Internet. This implementation doesn't manage UDP packets, so they are simply dropped (as with restrict=on), except for the localhost as we need it for DNS.

[Qemu-devel] [PATCH v2 0/1] slirp: add SOCKS5 support

This patch implements the SOCKS5 client part for "-net user" backend. It allows to route all internet traffic of the virtual machine to a SOCKS5 server. But all the local traffic (to the host) is sent to the host. It is needed because this SOCKS5 client doesn't route UDP traffic, and this allows

Re: [Qemu-devel] [RFC] Split migration bitmaps by ramblock

* Juan Quintela (quint...@redhat.com) wrote: > Hi > > This series split the migration and unsent bitmaps by ramblock. This > makes it easier to synchronize in small bits. This is on top of the > RAMState and not-hotplug series. So I think generally this is a good idea; my main reason is I'd

Re: [Qemu-devel] [PATCH] Create libqemutrace.a for all trace.o

> >>> ./trace.o, ./qapi/trace.o and ./util/trace.o are added into > >>> libqemuutil.a to avoid recursive dependencies between > >>> libqemuutil.a and libqemutrace.a. > >> Why would libqemutrace.a depend on libqemuutil.a? > > Each trace.c calls trace_event_register_group to register events, > >

Re: [Qemu-devel] [PATCH v3 for-2.9?] virtio: fix vring_align() on 64-bit windows

> From: Eric Blake [mailto:ebl...@redhat.com] > Sent: Tuesday, 28 March 2017 11:52 > > On 03/28/2017 01:38 PM, Stefan Weil wrote: > > Am 25.03.2017 um 00:19 schrieb Andrew Baumann: > >> long is 32-bits on 64-bit windows, which caused the top half of the > >> address to be truncated; this patch

Re: [Qemu-devel] [PATCH for 2.9?] tap-win32: don't abort in tap_enable(); enables -netdev tap

> From: Stefan Weil [mailto:s...@weilnetz.de] > Sent: Tuesday, 28 March 2017 11:28 > Am 25.03.2017 um 00:46 schrieb Andrew Baumann: > > The docs generally steer users away from using the legacy -net > > parameter, however on win32 attempting to enable a tap device using > > -netdev tap fails at

Re: [Qemu-devel] [PATCH v3 for-2.9?] virtio: fix vring_align() on 64-bit windows

On 03/28/2017 01:38 PM, Stefan Weil wrote: > Am 25.03.2017 um 00:19 schrieb Andrew Baumann: >> long is 32-bits on 64-bit windows, which caused the top half of the >> address to be truncated; this patch changes it to use the >> QEMU_ALIGN_UP macro which does not suffer the same problem >> >>

Re: [Qemu-devel] [RFC] Split migration bitmaps by ramblock

* Yang Hongyang (yanghongy...@huawei.com) wrote: > > > On 2017/3/24 16:34, Juan Quintela wrote: > > Yang Hongyang wrote: > >> Hi Juan, > >> > >> First of all, I like the refactor patchset about RAMState, it makes > >> things clean, great! > > > > Thanks. > > > > The

[Qemu-devel] [PATCH for-2.9?] configure: Remove unused code (found by shellcheck)

smartcard_cflags is no longer needed since commit 0b22ef0f57a8910d849602bef0940edcd0553d2c. Signed-off-by: Stefan Weil --- This is a very old patch which I just found in my patch queue. It's not mandatory for 2.9, but I also think that there is no risk to apply it. Sorry for

Re: [Qemu-devel] [PULL for-2.9] block: Declare blockdev-add and blockdev-del supported

Paolo Bonzini writes: > On 28/03/2017 15:45, Markus Armbruster wrote: >> It's been a long journey, but here we are. >> >> The supported blockdev-add is not compatible to its experimental >> predecessors; bump all Since: tags to 2.9. > > Can you document the differences in

Re: [Qemu-devel] [PATCH 42/51] ram: Pass RAMBlock to bitmap_sync

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> Yang Hongyang wrote: >> > On 2017/3/24 4:45, Juan Quintela wrote: >> >> We change the meaning of start to be the offset from the beggining of >> >> the block. >> >> >>

Re: [Qemu-devel] [PATCH 11/51] ram: Move dup_pages into RAMState

Peter Xu wrote: > On Thu, Mar 23, 2017 at 09:45:04PM +0100, Juan Quintela wrote: >> Once there rename it to its actual meaning, zero_pages. >> >> Signed-off-by: Juan Quintela >> Reviewed-by: Dr. David Alan Gilbert > > Reviewed-by:

Re: [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=reject policy

On 03/28/2017 01:28 PM, Michael S. Tsirkin wrote: >> (2) I could reconfigure mailman to try to not rewrite anything that >> we think is likely to be signed (in particular not the body or the >> subject) >>* this means dropping the [qemu-devel] tag from the subject, which I'm >>

Re: [Qemu-devel] [PATCH v3 for-2.9?] virtio: fix vring_align() on 64-bit windows

Am 25.03.2017 um 00:19 schrieb Andrew Baumann: long is 32-bits on 64-bit windows, which caused the top half of the address to be truncated; this patch changes it to use the QEMU_ALIGN_UP macro which does not suffer the same problem Signed-off-by: Andrew Baumann

Re: [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=reject policy

On 03/28/2017 12:53 PM, Andrew Baumann via Qemu-devel wrote: >> (3) I could set dmarc_moderation_action to Munge From, which means that >> those senders who have a p=reject policy will get their mails >> rewritten to have a From="Whoever (via the list) " >> and

Re: [Qemu-devel] [PATCH 16/51] ram: Move iterations into RAMState

Peter Xu wrote: > On Thu, Mar 23, 2017 at 09:45:09PM +0100, Juan Quintela wrote: >> Signed-off-by: Juan Quintela >> @@ -693,13 +694,13 @@ static void migration_bitmap_sync(RAMState *rs) >> } >> >> if (migrate_use_xbzrle()) { >> -

  1   2   3   4   >