Re: [Qemu-devel] [PULL] tftp: fake support for netascii protocol

On 18.11.2016 18:51, Samuel Thibault wrote: > From: Vincent Bernat > > Some network equipments are requesting a file using the netascii > protocol and this is not configurable. Currently, qemu's tftpd only > supports the octet protocol. This commit makes it accept the netascii

Re: [Qemu-devel] [PATCH v2 3/4] xen: create qdev for each backend device

On Wed, 2 Nov 2016, Juergen Gross wrote: > Create a qdev plugged to the xen-sysbus for each new backend device. > This device can be used as a parent for all needed devices of that > backend. The id of the new device will be "xen--" with > being the xen backend type (e.g. "qdisk") and the xen >

Re: [Qemu-devel] [PATCH v2 2/4] qdev: add function qdev_set_id()

On Wed, 2 Nov 2016, Juergen Gross wrote: > In order to have an easy way to add a new qdev with a specific id > carve out the needed functionality from qdev_device_add() into a new > function qdev_set_id(). > > Signed-off-by: Juergen Gross Reviewed-by: Stefano Stabellini

Re: [Qemu-devel] [PATCH v2 4/4] xen: attach pvusb usb bus to backend qdev

On Wed, 2 Nov 2016, Juergen Gross wrote: > Attach the usb bus of a new pvusb controller to the qdev associated > with the Xen backend. Any device connected to that controller can now > specify the bus and port directly via its properties. > > Signed-off-by: Juergen Gross

Re: [Qemu-devel] [PATCH v2 1/4] xen: add an own bus for xen backend devices

On Wed, 2 Nov 2016, Juergen Gross wrote: > Add a bus for Xen backend devices in order to be able to establish a > dedicated device path for pluggable devices. > > Signed-off-by: Juergen Gross Reviewed-by: Stefano Stabellini > hw/xen/xen_backend.c

[Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error

I’m sorry to post as a newbie here. I just want to confirm the bug described above by Kevin Zhao. At least that’s what it sounds like to me. I had a perfectly working VM on Qemu/KVM, with the VirtManager hypervisor, which I have *only* to be able to access an Audigy pci card from Windows XP. After

Re: [Qemu-devel] ARM documentation

On Nov 18, 2016, at 7:31 PM, Programmingkid wrote: > > On Nov 18, 2016, at 4:10 PM, Alistair Francis wrote: > >> On Fri, Nov 11, 2016 at 8:53 AM, G 3 wrote: >>> >>> On Nov 11, 2016, at 11:31 AM, Alex Bennée wrote: >>> G 3

Re: [Qemu-devel] ARM documentation

On Nov 18, 2016, at 4:10 PM, Alistair Francis wrote: > On Fri, Nov 11, 2016 at 8:53 AM, G 3 wrote: >> >> On Nov 11, 2016, at 11:31 AM, Alex Bennée wrote: >> >>> >>> G 3 writes: >>> On Nov 11, 2016, at 8:27 AM, G 3 wrote:

Re: [Qemu-devel] [PATCH v2 7/9] blkdebug: Add pass-through write_zero and discard support

On 11/17/2016 04:47 PM, Max Reitz wrote: > On 17.11.2016 21:14, Eric Blake wrote: >> In order to test the effects of artificial geometry constraints >> on operations like write zero or discard, we first need blkdebug >> to manage these actions. Ideally, it would be nice to let these >> operations

Re: [Qemu-devel] [PATCH v2 4/9] block: Return -ENOTSUP rather than assert on unaligned discards

On 11/17/2016 04:01 PM, Max Reitz wrote: > On 17.11.2016 21:13, Eric Blake wrote: >> Right now, the block layer rounds discard requests, so that >> individual drivers are able to assert that discard requests >> will never be unaligned. But there are some ISCSI devices >> that track and coalesce

[Qemu-devel] [PATCH for-2.8] dma/rc4030: translate memory accesses only when they occur

This simplifies the code a lot, and this fixes big memory leaks introduced in a3d586f704609a45b6037534cb2f34da5dfd8895 Windows NT is now able to boot without using gigabytes of ram on the host. Signed-off-by: Hervé Poussineau --- hw/dma/rc4030.c | 158

[Qemu-devel] [PATCH for-2.8] scsi/esp: do not raise an interrupt when reading the FIFO register

This fixes SCSI adapter self-tests done in MIPS Jazz emulation, broken since ff589551c8e8e9e95e211b9d8daafb4ed39f1aec. Signed-off-by: Hervé Poussineau --- hw/scsi/esp.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/hw/scsi/esp.c b/hw/scsi/esp.c index

Re: [Qemu-devel] ARM documentation

On Fri, Nov 11, 2016 at 8:53 AM, G 3 wrote: > > On Nov 11, 2016, at 11:31 AM, Alex Bennée wrote: > >> >> G 3 writes: >> >>> On Nov 11, 2016, at 8:27 AM, G 3 wrote: >>> On Nov 11, 2016, at 8:08 AM, Stefan Hajnoczi wrote: >

Re: [Qemu-devel] [RFC PATCH 6/8] quorum: Avoid bdrv_aio_writev() for rewrites

On 11/18/2016 06:21 AM, Kevin Wolf wrote: >>> +ret = bdrv_co_pwritev(s->children[co->i], >>> + acb->sector_num * BDRV_SECTOR_SIZE, >>> + acb->nb_sectors * BDRV_SECTOR_SIZE, >>> + acb->qiov, 0); >>> +(void) ret; >>

Re: [Qemu-devel] [PATCH 1/2] compiler: add ignore_value() macro

On 10/25/2016 10:21 AM, Felipe Franciosi wrote: > >> On 12 Oct 2016, at 18:20, Felipe Franciosi wrote: >> >> >>> On 21 Sep 2016, at 19:15, Eric Blake wrote: >>> >>> On 09/21/2016 10:27 AM, Felipe Franciosi wrote: On GCC versions 3.4 and newer, simply

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

Maxime Coquelin writes: > On 11/18/2016 07:15 PM, Aaron Conole wrote: >> Maxime Coquelin writes: >> >>> This series implements Virtio spec update from Aaron Conole which >>> defines a way for the host to expose its max MTU to the guest.

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

On 11/18/2016 07:15 PM, Aaron Conole wrote: Maxime Coquelin writes: This series implements Virtio spec update from Aaron Conole which defines a way for the host to expose its max MTU to the guest. Changes since RFC v1: - - Rebased on top of

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

On 11/18/2016 11:41 AM, Olaf Hering wrote: > On Fri, Nov 18, Eric Blake wrote: > >> On 11/18/2016 04:24 AM, Olaf Hering wrote: >>> +/* Overflowing byte limit? */ >>> +if ((sec_start + sec_count) > ((INT64_MAX + INT_MAX) >> >>> BDRV_SECTOR_BITS)) { >> This is undefined. INT64_MAX +

Re: [Qemu-devel] [RFC v2 2/3] vhost-net: Add new MTU feature support

Maxime Coquelin writes: > If VHOST_USER_F_MTU feature is negociated, vhost-net makes the > advised MTU available to virtio-net through a vhost_net_get_mtu() s/advised/maximum/ > call. > > Cc: Michael S. Tsirkin > Cc: Aaron Conole

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

Maxime Coquelin writes: > This series implements Virtio spec update from Aaron Conole which > defines a way for the host to expose its max MTU to the guest. > > Changes since RFC v1: > - > - Rebased on top of v2.8.0-rc0 (2.7.90) > - Write MTU

Re: [Qemu-devel] [PATCH] ipmi: fix qemu crash while migrating with ipmi

On 11/18/2016 02:22 AM, Zhuangyanying wrote: From: ZhuangYanying Qemu crash in the source side while migrating, after starting ipmi service inside vm. Yeah, I see the issue with that, it won't always work. Reviewed-by: Corey Minyard

Re: [Qemu-devel] [PULL] tftp: fake support for netascii protocol

Hi, Your series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] [PULL] tftp: fake support for netascii protocol Type: series Message-id: 20161118175128.17192-2-samuel.thiba...@ens-lyon.org === TEST SCRIPT BEGIN === #!/bin/bash BASE=base

Re: [Qemu-devel] [PATCH] tftp: fake support for netascii protocol

Hello, Vincent Bernat, on Thu 17 Nov 2016 13:22:32 +0100, wrote: > ❦ 17 novembre 2016 13:20 +0100, Vincent Bernat  : > > > Some network equipments are requesting a file using the netascii > > protocol and this is not configurable. Currently, qemu's tftpd only > >

[Qemu-devel] [PULL] tftp: fake support for netascii protocol

From: Vincent Bernat Some network equipments are requesting a file using the netascii protocol and this is not configurable. Currently, qemu's tftpd only supports the octet protocol. This commit makes it accept the netascii protocol as well but do not perform the requested

[Qemu-devel] [PULL] tftp: fake support for netascii protocol

The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf: Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +) are available in the git repository at: http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault for you to fetch changes up to

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

On Fri, Nov 18, Eric Blake wrote: > On 11/18/2016 04:24 AM, Olaf Hering wrote: > > +/* Overflowing byte limit? */ > > +if ((sec_start + sec_count) > ((INT64_MAX + INT_MAX) >> > > BDRV_SECTOR_BITS)) { > This is undefined. INT64_MAX + anything non-negative overflows int64, The expanded

Re: [Qemu-devel] [PATCH v3] ivshmem: Fix 64 bit memory bar configuration

On 18/11/2016 16:27, Michael S. Tsirkin wrote: > On Thu, Nov 17, 2016 at 08:31:03PM +0800, Zhuangyanying wrote: >> From: Zhuang Yanying >> >> Device ivshmem property use64=0 is designed to make the device >> expose a 32 bit shared memory BAR instead of 64

Re: [Qemu-devel] [QEMU PATCH v13 0/4] migration: migrate QTAILQ

ping On 11/16/2016 04:07 PM, Jianjun Duan wrote: > Hi all, > > I addressed some review comments. Comments are welcome. > > v13: - Changed some QTAILQ related macro names to match existing ones. > > Previous versions are: > > v12: - Fixed type for put_qtailq which caused build break.

Re: [Qemu-devel] [PATCH v14 00/22] Add Mediated device support

On Fri, 18 Nov 2016 17:09:59 +0100 Daniel Vetter wrote: > On Fri, Nov 18, 2016 at 4:40 PM, Alex Williamson > wrote: > >> Alex, could you do a pull request of mdev for Daniel's drm-intel tree? > >> We need to send KVMGT mdev support pull base on that.

Re: [Qemu-devel] [PATCH for-2.8 2/3] migration: spapr_drc: defined VMStateDescription struct

Quoting David Gibson (2016-11-18 00:04:33) > On Thu, Nov 17, 2016 at 07:40:26PM -0600, Michael Roth wrote: > > From: Jianjun Duan > > > > To manage hotplug/unplug of dynamic resources such as PCI cards, > > memory, and CPU on sPAPR guests, a firmware abstraction known

Re: [Qemu-devel] [PATCH for-2.8 0/3] spapr: fix breakage of memory unplug after migration

Quoting David Gibson (2016-11-17 23:45:05) > On Thu, Nov 17, 2016 at 07:40:24PM -0600, Michael Roth wrote: > > These patches are based on David's ppc-for-2.8 tree, and are also > > available from: > > > > https://github.com/mdroth/qemu/commits/spapr-cas-migration > > > > Currently, memory

Re: [Qemu-devel] [PATCH for-2.8 3/3] spapr: migration support for CAS-negotiated option vectors

Quoting Michael Roth (2016-11-17 19:40:27) > With the additional of the OV5_HP_EVT option vector, we now have > certain functionality (namely, memory unplug) that checks at run-time > for whether or not the guest negotiated the option via CAS. Because > we don't currently migrate these negotiated

[Qemu-devel] [PATCH 4/5] sheepdog: simplify inflight_aio_head management

Add to the list in add_aio_request and, indirectly, resend_aioreq. Inline free_aio_req in the caller, it does not simply undo alloc_aio_req's job. Cc: jc...@redhat.com Cc: qemu-bl...@nongnu.org Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by:

[Qemu-devel] [PATCH 5/5] sheepdog: reorganize check for overlapping requests

Wrap the code that was copied repeatedly in the two functions, sd_aio_setup and sd_aio_complete. Cc: jc...@redhat.com Cc: qemu-bl...@nongnu.org Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini ---

[Qemu-devel] [PATCH 2/5] sheepdog: reorganize coroutine flow

Delimit co_recv's lifetime clearly in aio_read_response. Do a simple qemu_coroutine_enter in aio_read_response, letting sd_co_writev call sd_write_done. Handle nr_pending in the same way in sd_co_rw_vector, sd_write_done and sd_co_flush_to_disk. Remove sd_co_rw_vector's return value; just leave

[Qemu-devel] [PATCH 3/5] sheepdog: do not use BlockAIOCB

Sheepdog's AIOCB are completely internal entities for a group of requests and do not need dynamic allocation. Cc: jc...@redhat.com Cc: qemu-bl...@nongnu.org Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini ---

[Qemu-devel] [PATCH 1/5] sheepdog: remove unused cancellation support

SheepdogAIOCB is internal to sheepdog.c, hence it is never canceled. Cc: jc...@redhat.com Cc: qemu-bl...@nongnu.org Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini --- block/sheepdog.c | 52

[Qemu-devel] [PATCH for-2.9 v2 0/5] Sheepdog cleanups

Cleaning up the code and removing duplication makes it simpler to later adapt it for the multiqueue work. Tested against sheepdog 1.0. I also tested taking snapshots and reverting to older snapshots, but the latter only worked with "dog vdi rollback". Neither loadvm nor qemu-img worked for me.

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

On 11/18/2016 04:24 AM, Olaf Hering wrote: > The guest sends discard requests as u64 sector/count pairs, but the > block layer operates internally with s64/s32 pairs. The conversion > leads to IO errors in the guest, the discard request is not processed. > > domU.cfg: > 'vdev=xvda,

Re: [Qemu-devel] [PATCH for-2.9 0/5] Sheepdog cleanups

Hi, Your series failed automatic build test. Please find the testing commands and their output below. If you have docker installed, you can probably reproduce it locally. Subject: [Qemu-devel] [PATCH for-2.9 0/5] Sheepdog cleanups Type: series Message-id:

[Qemu-devel] [PATCH 4/5] sheepdog: simplify inflight_aio_head management

Add to the list in add_aio_request and, indirectly, resend_aioreq. Inline free_aio_req in the caller, it does not simply undo alloc_aio_req's job. Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini ---

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On Fri, Nov 18, 2016 at 10:34:54AM +, Ketan Nilangekar wrote: > > > > > > On 11/18/16, 12:56 PM, "Jeff Cody" wrote: > > >On Wed, Nov 16, 2016 at 08:12:41AM +, Stefan Hajnoczi wrote: > >> On Tue, Nov 15, 2016 at 10:38 PM, ashish mittal > >>

[Qemu-devel] [PATCH 3/5] sheepdog: do not use BlockAIOCB

Sheepdog's AIOCB are completely internal entities for a group of requests and do not need dynamic allocation. Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini --- block/sheepdog.c | 95

[Qemu-devel] [PATCH 2/5] sheepdog: reorganize coroutine flow

Delimit co_recv's lifetime clearly in aio_read_response. Do a simple qemu_coroutine_enter in aio_read_response, letting sd_co_writev call sd_write_done. Handle nr_pending in the same way in sd_co_rw_vector, sd_write_done and sd_co_flush_to_disk. Remove sd_co_rw_vector's return value; just leave

[Qemu-devel] [PULL 7/7] acpi: Use apic_id_limit when calculating legacy ACPI table size

From: Eduardo Habkost The code that calculates the legacy ACPI table size for migration compatibility uses max_cpus when calculating legacy_aml_len (the size of the DSDT and SSDT tables). However, the SSDT grows according to APIC ID limit, not max_cpus. The bug is not

[Qemu-devel] [PULL 6/7] ipmi: fix qemu crash while migrating with ipmi

From: ZhuangYanying Qemu crash in the source side while migrating, after starting ipmi service inside vm. ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -smp 4 -m 4096 \ -drive file=/work/suse/suse11_sp3_64_vt,format=raw,if=none,id=drive-virtio-disk0,cache=none

Re: [Qemu-devel] [PATCH v14 00/22] Add Mediated device support

On Fri, Nov 18, 2016 at 4:40 PM, Alex Williamson wrote: >> Alex, could you do a pull request of mdev for Daniel's drm-intel tree? >> We need to send KVMGT mdev support pull base on that. > > No, this is not how I intend or prefer to merge this. This is a large >

[Qemu-devel] [PULL 4/7] virtio: set ISR on dataplane notifications

From: Paolo Bonzini Dataplane has been omitting forever the step of setting ISR when an interrupt is raised. This caused little breakage, because the specification actually says that ISR may not be updated in MSI mode. Some versions of the Windows drivers however didn't

[Qemu-devel] [PULL 5/7] ivshmem: Fix 64 bit memory bar configuration

From: Zhuang Yanying Device ivshmem property use64=0 is designed to make the device expose a 32 bit shared memory BAR instead of 64 bit one. The default is a 64 bit BAR, except pc-1.2 and older retain a 32 bit BAR. A 32 bit BAR can support only up to 1 GiB of

[Qemu-devel] [PATCH 1/5] sheepdog: remove unused cancellation support

SheepdogAIOCB is internal to sheepdog.c, hence it is never canceled. Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini --- block/sheepdog.c | 52 1 file

[Qemu-devel] [PULL 1/7] virtio-crypto: fix virtio_queue_set_notification() race

From: Stefan Hajnoczi We must check for new virtqueue buffers after re-enabling notifications. This prevents the race condition where the guest added buffers just after we stopped popping the virtqueue but before we re-enabled notifications. I think the virtio-crypto code

[Qemu-devel] [PATCH for-2.9 0/5] Sheepdog cleanups

Cleaning up the code and removing duplication makes it simpler to later adapt it for the multiqueue work. Tested against sheepdog 1.0. I also tested taking snapshots and reverting to older snapshots, but the latter only worked with "dog vdi rollback". Neither loadvm nor qemu-img worked for me.

Re: [Qemu-devel] [PATCH] hw/pci: disable pci-bridge's shpc by default

On Fri, Nov 18, 2016 at 04:52:01PM +0100, Andrew Jones wrote: > On Wed, Nov 16, 2016 at 07:05:25PM +0200, Marcel Apfelbaum wrote: > > On 11/16/2016 06:44 PM, Andrew Jones wrote: > > > On Sat, Nov 05, 2016 at 06:46:34PM +0200, Marcel Apfelbaum wrote: > > > > On 11/03/2016 09:40 PM, Michael S.

[Qemu-devel] [PULL 0/7] virtio, vhost, pc: fixes

The following changes since commit 453ac8835b002263a6b7b0843e7c90fa8b19c869: docs: add PCIe devices placement guidelines (2016-11-15 17:20:38 +0200) 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 2/7] virtio: introduce grab/release_ioeventfd to fix vhost

From: Paolo Bonzini Following the recent refactoring of virtio notifiers [1], more specifically the patch ed08a2a0b ("virtio: use virtio_bus_set_host_notifier to start/stop ioeventfd") that uses virtio_bus_set_host_notifier [2] by default, core virtio code requires

[Qemu-devel] [PATCH 5/5] sheepdog: reorganize check for overlapping requests

Wrap the code that was copied repeatedly in the two functions, sd_aio_setup and sd_aio_complete. Cc: Hitoshi Mitake Cc: Liu Yuan Signed-off-by: Paolo Bonzini --- block/sheepdog.c | 66

[Qemu-devel] [PULL 3/7] virtio: access ISR atomically

From: Paolo Bonzini This will be needed once dataplane will be able to set it outside the big QEMU lock. Reviewed-by: Stefan Hajnoczi Tested-by: Farhan Ali Tested-by: Alex Williamson

Re: [Qemu-devel] [PATCH] hw/pci: disable pci-bridge's shpc by default

On Wed, Nov 16, 2016 at 07:05:25PM +0200, Marcel Apfelbaum wrote: > On 11/16/2016 06:44 PM, Andrew Jones wrote: > > On Sat, Nov 05, 2016 at 06:46:34PM +0200, Marcel Apfelbaum wrote: > > > On 11/03/2016 09:40 PM, Michael S. Tsirkin wrote: > > > > On Thu, Nov 03, 2016 at 01:05:44PM +0200, Marcel

Re: [Qemu-devel] [PULL 0/1] Tracing patches

On Fri, Nov 18, 2016 at 03:01:28PM +, Stefan Hajnoczi wrote: > The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf: > > Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +) > > are available in the git repository at: > >

Re: [Qemu-devel] [PATCH v14 00/22] Add Mediated device support

On Fri, 18 Nov 2016 17:16:32 +0800 Zhenyu Wang wrote: > On 2016.11.17 16:51:45 -0700, Alex Williamson wrote: > > On Thu, 17 Nov 2016 23:29:38 + > > "Tian, Kevin" wrote: > > > > > > From: Alex Williamson [mailto:alex.william...@redhat.com] >

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

Am 18.11.2016 um 15:35 hat Eric Blake geschrieben: > On 11/18/2016 08:19 AM, Olaf Hering wrote: > > Am 18. November 2016 14:43:18 MEZ, schrieb Eric Blake : > >> On 11/18/2016 04:24 AM, Olaf Hering wrote: > >>> The guest sends discard requests as u64 sector/count pairs, but the >

Re: [Qemu-devel] [PATCH v3] ivshmem: Fix 64 bit memory bar configuration

On Fri, Nov 18, 2016 at 05:27:41PM +0200, Michael S. Tsirkin wrote: > On Thu, Nov 17, 2016 at 08:31:03PM +0800, Zhuangyanying wrote: > > From: Zhuang Yanying > > > > Device ivshmem property use64=0 is designed to make the device > > expose a 32 bit shared

Re: [Qemu-devel] [PATCH v3] ivshmem: Fix 64 bit memory bar configuration

On Thu, Nov 17, 2016 at 08:31:03PM +0800, Zhuangyanying wrote: > From: Zhuang Yanying > > Device ivshmem property use64=0 is designed to make the device > expose a 32 bit shared memory BAR instead of 64 bit one. The > default is a 64 bit BAR, except

Re: [Qemu-devel] [PATCH 0/3] virtio: disable notifications in blk and scsi

On Fri, Nov 18, 2016 at 04:21:33PM +0200, Michael S. Tsirkin wrote: > On Fri, Nov 18, 2016 at 10:58:47AM +, Stefan Hajnoczi wrote: > > On Thu, Nov 17, 2016 at 07:38:45PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Nov 17, 2016 at 01:27:49PM +, Stefan Hajnoczi wrote: > > > > On Thu, Nov

[Qemu-devel] [Bug 1626972] Re: QEMU memfd_create fallback mechanism change for security drivers

** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1626972 Title: QEMU memfd_create fallback mechanism change for security

Re: [Qemu-devel] [kvm-unit-tests PATCH 0/4] kvm-unit-tests: add first GIC MMIO tests

Hi Andre, I've verified tests you proposed to the lists finish without an issue with the kvm-arm-for-4.9-rc6 kernel. Itaru

[Qemu-devel] [PULL 0/1] Tracing patches

The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf: Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +) are available in the git repository at: git://github.com/stefanha/qemu.git tags/tracing-pull-request for you to fetch changes up to

Re: [Qemu-devel] [RFCv2 01/12] pseries: Always use core objects for CPU construction

On Wed, 16 Nov 2016 09:17:44 +1100 David Gibson wrote: > Currently the pseries machine has two paths for constructing CPUs. On > newer machine type versions, which support cpu hotplug, it constructs > cpu core objects, which in turn construct CPU threads. For older

Re: [Qemu-devel] [PULL 0/1] ivshmem fix for 2.8

Hi On Fri, Nov 18, 2016 at 6:57 PM Stefan Hajnoczi wrote: > On Thu, Nov 17, 2016 at 07:26:12PM +0400, Marc-André Lureau wrote: > > The following changes since commit > b0bcc86d2a87456f5a276f941dc775b265b309cf: > > > > Update version for v2.8.0-rc0 release (2016-11-15

[Qemu-devel] [PULL 1/1] trace: fix generated code build break

From: Greg Kurz If the QEMU source dir is /var/tmp/aaa-qemu-clone and the build dir is /var/tmp/qemu-aio-poll-v2 Then I get an error as: trace/generated-tracers.c:15950:13: error: invalid suffix "_trace_events" on integer constant TraceEvent *2_trace_events[] = {

Re: [Qemu-devel] [PULL 0/1] ivshmem fix for 2.8

On Thu, Nov 17, 2016 at 07:26:12PM +0400, Marc-André Lureau wrote: > The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf: > > Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +) > > are available in the git repository at: > >

Re: [Qemu-devel] [PULL 0/1] ivshmem fix for 2.8

On Thu, Nov 17, 2016 at 07:26:12PM +0400, Marc-André Lureau wrote: > The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf: > > Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +) > > are available in the git repository at: > >

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

Ketan Nilangekar writes: > On 11/18/16, 12:56 PM, "Jeff Cody" wrote: [...] >>* Daniel pointed out that there is no authentication method for taking to a >> remote server. This seems a bit scary. Maybe all that is needed here is >> some

Re: [Qemu-devel] [kvm-unit-tests PATCH 4/4] arm/arm64: GICv3: add TYPER test

On Thu, Nov 17, 2016 at 05:57:52PM +, Andre Przywara wrote: > Add a simple test for the GICv3 TYPER test, which does only one basic > check to ensure we have actually enough interrupt IDs if we support > LPIs. > Allow a GICv3 guest to do the common MMIO checks as well, where the > register

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

On 11/18/2016 08:19 AM, Olaf Hering wrote: > Am 18. November 2016 14:43:18 MEZ, schrieb Eric Blake : >> On 11/18/2016 04:24 AM, Olaf Hering wrote: >>> The guest sends discard requests as u64 sector/count pairs, but the >>> block layer operates internally with s64/s32 pairs. The

Re: [Qemu-devel] [RFC v2 1/3] vhost-user: Add new protocol feature MTU

Maxime Coquelin writes: > This patch adds VHOST_USER_PROTOCOL_F_MTU protocol feature. > > If supported, QEMU sends VHOST_USER_GET_MTU request to the client, > and expects a u64 reply containing the MTU advised for the guest. > > Cc: Michael S. Tsirkin

[Qemu-devel] [PATCH v3 3/3] virtio: set ISR on dataplane notifications

Dataplane has been omitting forever the step of setting ISR when an interrupt is raised. This caused little breakage, because the specification actually says that ISR may not be updated in MSI mode. Some versions of the Windows drivers however didn't clear MSI mode correctly, and proceeded using

[Qemu-devel] [PATCH v3 2/3] virtio: access ISR atomically

This will be needed once dataplane will be able to set it outside the big QEMU lock. Signed-off-by: Paolo Bonzini --- hw/virtio/virtio-mmio.c | 6 +++--- hw/virtio/virtio-pci.c | 9 +++-- hw/virtio/virtio.c | 22 +- 3 files changed, 23

[Qemu-devel] [PATCH v3 1/3] virtio: introduce grab/release_ioeventfd to fix vhost

Following the recent refactoring of virtio notifiers [1], more specifically the patch ed08a2a0b ("virtio: use virtio_bus_set_host_notifier to start/stop ioeventfd") that uses virtio_bus_set_host_notifier [2] by default, core virtio code requires 'ioeventfd_started' to be set to true/false when the

[Qemu-devel] [PATCH v3 for-2.8 0/3] virtio fixes

Patch 1 fixes vhost, patches 2-3 fix Windows hibernation. v3 only adds more comments to patches 2 and 3. Paolo Paolo Bonzini (3): virtio: introduce grab/release_ioeventfd to fix vhost virtio: access ISR atomically virtio: set ISR on dataplane notifications hw/block/dataplane/virtio-blk.c

Re: [Qemu-devel] [PATCH 1/3] virtio: introduce grab/release_ioeventfd to fix vhost

On Fri, Nov 18, 2016 at 09:15:32AM +0100, Christian Borntraeger wrote: > On 11/16/2016 07:05 PM, Paolo Bonzini wrote: > > Following the recent refactoring of virtio notifiers [1], more specifically > > the patch ed08a2a0b ("virtio: use virtio_bus_set_host_notifier to > > start/stop ioeventfd")

Re: [Qemu-devel] [PATCH 0/3] virtio: disable notifications in blk and scsi

On Fri, Nov 18, 2016 at 10:58:47AM +, Stefan Hajnoczi wrote: > On Thu, Nov 17, 2016 at 07:38:45PM +0200, Michael S. Tsirkin wrote: > > On Thu, Nov 17, 2016 at 01:27:49PM +, Stefan Hajnoczi wrote: > > > On Thu, Nov 17, 2016 at 12:17:57AM +0200, Michael S. Tsirkin wrote: > > > > On Wed, Nov

Re: [Qemu-devel] [kvm-unit-tests PATCH 3/4] arm/arm64: GICv2: add GICD_ITARGETSR testing

On Thu, Nov 17, 2016 at 05:57:51PM +, Andre Przywara wrote: > Some tests for the ITARGETS registers. > Bits corresponding to non-existent CPUs must be RAZ/WI. > These registers must be byte-accessible, also check that accesses beyond > the implemented IRQ limit are actually

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

Am 18. November 2016 14:43:18 MEZ, schrieb Eric Blake : >On 11/18/2016 04:24 AM, Olaf Hering wrote: >> The guest sends discard requests as u64 sector/count pairs, but the >> block layer operates internally with s64/s32 pairs. The conversion >> leads to IO errors in the guest,

Re: [Qemu-devel] [PATCH v5 12/17] qapi: rename QAPIExprError/QAPILineError

Marc-André Lureau writes: > - Original Message - >> Make the summary line "qapi: Rename QAPIExprError to QAPILineError". >> > > ok > >> Marc-André Lureau writes: >> >> > There is nothing specific about expressions in this exception, >>

Re: [Qemu-devel] [PATCH v2 1/9] nbd: Allow unmap and fua during write zeroes

On 17/11/2016 22:10, Max Reitz wrote: > On 17.11.2016 21:13, Eric Blake wrote: >> Commit fa778fff wired up support to send the NBD_CMD_WRITE_ZEROES, >> but forgot to inform the block layer that FUA unmapping of zeroes is >> supported. Without BDRV_REQ_MAY_UNMAP listed as a supported flag, >>

Re: [Qemu-devel] [PATCH v3 for-2.9 0/3] q35: add negotiable broadcast SMI

On Fri, Nov 18, 2016 at 11:36:56AM +0100, Laszlo Ersek wrote: > This is v3 of the series, with updates based on the v2 discussion: > . > > I've added feature negotiation via the APM_STS ("scratchpad") register. > A new spec

Re: [Qemu-devel] [PATCH v5 03/17] qga/schema: improve guest-set-vcpus Returns: section

Marc-André Lureau writes: > Hi > > - Original Message - >> Marc-André Lureau writes: >> >> > The documentation parser we are going to add finishes a section after an >> > empty line. >> >> Is this still true? > > No longer true, the

Re: [Qemu-devel] [kvm-unit-tests PATCH 1/4] arm/arm64: GIC: basic GICv2 MMIO tests

Hi Drew, On 18/11/16 13:06, Andrew Jones wrote: > Hi Andre, > > I'm so pleased to see this series. Thank you! > > On Thu, Nov 17, 2016 at 05:57:49PM +, Andre Przywara wrote: >> This adds an MMIO subtest to the GIC test. >> It accesses some generic GICv2 registers and does some sanity tests,

Re: [Qemu-devel] [kvm-unit-tests PATCH 2/4] arm/arm64: GICv2: add GICD_IPRIORITYR testing

On Thu, Nov 17, 2016 at 05:57:50PM +, Andre Przywara wrote: > Some tests for the IPRIORITY registers. The significant number of bits > is IMPLEMENTATION DEFINED, but should be the same for every IRQ. > Also these registers must be byte-accessible. > Check that accesses beyond the implemented

Re: [Qemu-devel] [PATCH] xen_disk: convert discard input to byte ranges

On 11/18/2016 04:24 AM, Olaf Hering wrote: > The guest sends discard requests as u64 sector/count pairs, but the > block layer operates internally with s64/s32 pairs. The conversion > leads to IO errors in the guest, the discard request is not processed. Doesn't the block layer already split

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

On Fri, Nov 18, 2016 at 01:25:43PM +, Ketan Nilangekar wrote: > > > > On Nov 18, 2016, at 5:25 PM, Daniel P. Berrange wrote: > > > >> On Fri, Nov 18, 2016 at 11:36:02AM +, Ketan Nilangekar wrote: > >> > >> > >> > >> > >> > >>> On 11/18/16, 3:32 PM, "Stefan

[Qemu-devel] [RFC Design Doc v2] Enable Shared Virtual Memory feature in pass-through scenarios

What's changed from v1: a) Solution changed: Switch to extend the existing QEMU vIOMMU emulator to support virtual SVM for pass-through devices. Take use of VFIO to do data propagation. b) A SVM Virtualization Architecture diagram is added. Content

Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

> On Nov 18, 2016, at 5:25 PM, Daniel P. Berrange wrote: > >> On Fri, Nov 18, 2016 at 11:36:02AM +, Ketan Nilangekar wrote: >> >> >> >> >> >>> On 11/18/16, 3:32 PM, "Stefan Hajnoczi" wrote: >>> On Fri, Nov 18, 2016 at 02:26:21AM -0500,

Re: [Qemu-devel] [kvm-unit-tests PATCH 1/4] arm/arm64: GIC: basic GICv2 MMIO tests

Hi Andre, I'm so pleased to see this series. Thank you! On Thu, Nov 17, 2016 at 05:57:49PM +, Andre Przywara wrote: > This adds an MMIO subtest to the GIC test. > It accesses some generic GICv2 registers and does some sanity tests, > like checking for some of them being read-only. > >

Re: [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV

On 18/11/2016 13:53, Greg Kurz wrote: > Hi Laurent, Hi Greg, > On Thu, 17 Nov 2016 21:22:33 +0100 > Laurent Vivier wrote: > >> On 16/11/2016 15:17, Greg Kurz wrote: >>> On Wed, 16 Nov 2016 14:17:47 +0100 >>> Thomas Huth wrote: >>> On 16.11.2016

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

Juan, It looks like Lai is waiting for a reply from you on this email :). Alex On 08/30/2016 06:11 AM, Lai Jiangshan wrote: On Wed, Aug 10, 2016 at 5:03 PM, Juan Quintela wrote: Lai Jiangshan wrote: Hi First of all, I like a lot the patchset,

Re: [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV

Hi Laurent, On Thu, 17 Nov 2016 21:22:33 +0100 Laurent Vivier wrote: > On 16/11/2016 15:17, Greg Kurz wrote: > > On Wed, 16 Nov 2016 14:17:47 +0100 > > Thomas Huth wrote: > > > >> On 16.11.2016 13:37, Greg Kurz wrote: > >>> On Wed, 16 Nov 2016

Re: [Qemu-devel] [PATCH v5 16/17] docs: add qemu logo

Marc-André Lureau writes: > The pdf (needed by texi2pdf for vectorized images) was generated thanks > to inkscape, from the pc-bios/qemu_logo.svg file. Since we don't want to build-depend on inkscape, we need to commit the .pdf. Not that bad, as the .svg is

Re: [Qemu-devel] [PATCH 16/25] tcg/i386: Handle ctz and clz opcodes

On 11/18/2016 12:03 AM, Richard Henderson wrote: > On 11/17/2016 11:09 PM, Bastian Koppelmann wrote: >> On 11/17/2016 08:59 PM, Richard Henderson wrote: >>> On 11/17/2016 08:53 PM, Richard Henderson wrote: On 11/17/2016 05:50 PM, Bastian Koppelmann wrote: > On 11/16/2016 08:25 PM, Richard

  1   2   >