[Qemu-devel] [Bug 821078] Re: virtio-serial-bus: Unexpected port id

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/821078 Title:

[Qemu-devel] [Bug 988909] Re: Assert failed in arp_table.c

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/988909 Title: Assert

[Qemu-devel] [Bug 989504] Re: assertion failed when attaching USB MSD device

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/989504 Title: assertion

[Qemu-devel] [Bug 966316] Re: Can't load Android VBOX image or even linux test image as well

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/966316 Title: Can't load

Re: [Qemu-devel] [PATCH v3 0/2] block: Quiesce old aio context during bdrv_set_aio_context

On 13/04/2017 15:21, Fam Zheng wrote: > Paolo, maybe you want to submit a formal patch for 2.10? (Sorry for the > confusion, these series of mine went a bit messy.) Yes, will do. Or just submit the alternative fix that is mentioned in the comment. Paolo

Re: [Qemu-devel] QEMU build breakage on ARM against Xen 4.9 caused by libxendevicemodel

On Fri, 14 Apr 2017, Stefano Stabellini wrote: > Hi Paul, > > The following commit in my qemu "next" branch breaks the build on arm > and arm64: > > commit 670271647ad15e9d937ced7a72c892349c709216 > Author: Paul Durrant > Date: Tue Mar 7 10:55:34 2017 + > >

[Qemu-devel] QEMU build breakage on ARM against Xen 4.9 caused by libxendevicemodel

Hi Paul, The following commit in my qemu "next" branch breaks the build on arm and arm64: commit 670271647ad15e9d937ced7a72c892349c709216 Author: Paul Durrant Date: Tue Mar 7 10:55:34 2017 + xen: use libxendevicemodel when available See the appended build

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v9 2/5] virtio-balloon: VIRTIO_BALLOON_F_BALLOON_CHUNKS

On Fri, Apr 14, 2017 at 04:37:52PM +0800, Wei Wang wrote: > On 04/14/2017 12:34 AM, Michael S. Tsirkin wrote: > > On Thu, Apr 13, 2017 at 05:35:05PM +0800, Wei Wang wrote: > > > > So we don't need the bitmap to talk to host, it is just > > a data structure we chose to maintain lists of pages,

Re: [Qemu-devel] [Qemu-devel RFC v2 2/4] msf2: Microsemi Smartfusion2 System Register block.

On Sun, Apr 9, 2017 at 4:19 AM, Subbaraya Sundeep wrote: > Added Sytem register block of Smartfusion2. > This block has PLL registers which are accessed by guest. > > Signed-off-by: Subbaraya Sundeep > --- > hw/misc/Makefile.objs | 1 + >

Re: [Qemu-devel] [Qemu-devel RFC v2 1/4] msf2: Add Smartfusion2 System timer

On Sun, Apr 9, 2017 at 4:19 AM, Subbaraya Sundeep wrote: > Modelled System Timer in Microsemi's Smartfusion2 Soc. > Timer has two 32bit down counters and two interrupts. > > Signed-off-by: Subbaraya Sundeep Hey Sundeep, I have some comments

Re: [Qemu-devel] [Qemu-devel RFC v2 4/4] msf2: Add Emcraft's Smartfusion2 SOM kit.

On Sun, Apr 9, 2017 at 4:19 AM, Subbaraya Sundeep wrote: > Emulated Emcraft's Smartfusion2 System On Module starter > kit. > > Signed-off-by: Subbaraya Sundeep Hey Sundeep, Cool patch, I have some comments below. > --- >

Re: [Qemu-devel] [PATCH v2 1/4] arm: remove remaining cannot_destroy_with_object_finalize_yet

On Fri, Apr 14, 2017 at 1:37 AM, Laurent Vivier wrote: > With commit ce5b1bbf624b ("exec: move cpu_exec_init() calls to > realize functions"), we can now remove all the > remaining cannot_destroy_with_object_finalize_yet as > unsafe references have been moved to

[Qemu-devel] [Bug 986318] Re: [sdl] Mouse grab breaks GNOME 3 screensaver unlock screen

On current versions (QEMU 2.8, GNOME-Shell 3.22.3 on Wayland), the screensaver will activate. Cursor control is given to the lock screen, everything works properly. After the screen is unlocked, the cursor is given back to QEMU and is still in "mouse grab" mode. ** Changed in: qemu Status:

Re: [Qemu-devel] [PATCH 0/3] move xen related files to corresponding xen directory

On Wed, 5 Apr 2017, Anthony Xu wrote: > > move xen related files to corresponding xen directory > > move xen-common.c to hw/xen/ > move xen-hvm.c to hw/i386/xen/ > move xen-mapcache.c to hw/i386/xen/ > > Signed-off -by: Anthony Xu Reviewed-by: Stefano Stabellini

Re: [Qemu-devel] [Xen-devel] [PATCH] configure: introduce --enable-xen-fb-backend

On Fri, 14 Apr 2017, Juergen Gross wrote: > On 14/04/17 08:06, Oleksandr Andrushchenko wrote: > > On 04/14/2017 03:12 AM, Stefano Stabellini wrote: > >> On Tue, 11 Apr 2017, Oleksandr Andrushchenko wrote: > >>> From: Oleksandr Andrushchenko > >>> > >>> For some

Re: [Qemu-devel] [RFC v2 4/4] spec/vhost-user spec: Add IOMMU support

On 04/14/2017 07:40 PM, Maxime Coquelin wrote: static void slave_read(void *opaque) { struct vhost_dev *dev = opaque; @@ -611,6 +639,8 @@ static void slave_read(void *opaque) } switch (msg.request) { Oops, I missed "case VHOST_USER_SLAVE_IOTLB_MSG:" here.. +ret =

[Qemu-devel] [RFC v2 3/4] vhost-user: add slave-req-fd support

From: Marc-André Lureau Learn to give a socket to the slave to let him make requests to the master. Signed-off-by: Marc-André Lureau Signed-off-by: Maxime Coquelin --- docs/specs/vhost-user.txt | 30

[Qemu-devel] [RFC v2 4/4] spec/vhost-user spec: Add IOMMU support

This patch specifies and implements the master/slave communication to support device IOTLB in slave. The vhost_iotlb_msg structure introduced for kernel backends is re-used, making the design close between the two backends. An exception is the use of the secondary channel to enable the slave to

[Qemu-devel] [RFC v2 0/4] vhost-user: Specify and implement device IOTLB support

This series aims at specifying ans implementing the protocol update required to support device IOTLB with user backends. In this second version, the slave requests channel part is re-used from Marc-André's series submitted last year[0], with main changes from original version being

[Qemu-devel] [RFC v2 2/4] vhost-user: add vhost_user to hold the chr

From: Marc-André Lureau Next patches will add more fields to the structure Signed-off-by: Marc-André Lureau Signed-off-by: Maxime Coquelin --- hw/virtio/vhost-user.c | 19 --- 1 file

[Qemu-devel] [RFC v2 1/4] vhost: propagate errors in vhost_device_iotlb_miss()

Some backends might want to know when things went wrong. Signed-off-by: Maxime Coquelin --- hw/virtio/vhost.c | 15 ++- include/hw/virtio/vhost.h | 2 +- 2 files changed, 11 insertions(+), 6 deletions(-) diff --git a/hw/virtio/vhost.c

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.9-rc5 v2] block: Drain BH in bdrv_drained_begin

On 14/04/2017 16:51, Stefan Hajnoczi wrote: > On Fri, Apr 14, 2017 at 9:02 AM, Fam Zheng wrote: >> @@ -398,11 +399,15 @@ void bdrv_drain_all(void); >> */\ >> assert(!bs_->wakeup); \

Re: [Qemu-devel] [PATCH 2/6] util: introduce glib-helper.c

Hi Alexey, On 04/14/2017 10:17 AM, Alexey Perevalov wrote: There is a lack of g_int_cmp which compares pointers value in glib, xen_disk.c introduced its own, so the same function now requires in migration.c. So logically to move it into common place. Futher: maybe extend glib. Also this commit

Re: [Qemu-devel] [PATCH for-2.10 1/3] qemu-img/convert: Always set ret < 0 on error

On 04/13/2017 05:33 PM, Max Reitz wrote: Otherwise the qemu-img process will exit with EXIT_SUCCESS instead of EXIT_FAILURE. Cc: qemu-stable Signed-off-by: Max Reitz Reviewed-by: Philippe Mathieu-Daudé --- qemu-img.c | 2 ++ 1

Re: [Qemu-devel] [PATCH v9 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

On Fri, Apr 14, 2017 at 02:47:40AM -0700, Matthew Wilcox wrote: > On Fri, Apr 14, 2017 at 04:50:48AM +0300, Michael S. Tsirkin wrote: > > On Thu, Apr 13, 2017 at 01:44:11PM -0700, Matthew Wilcox wrote: > > > On Thu, Apr 13, 2017 at 05:35:03PM +0800, Wei Wang wrote: > > > > 2) transfer the guest

[Qemu-devel] [PATCH 6/6] migration: detailed traces for postcopy

It could help to track down vCPU state during page fault and page fault sources. This patch showes proc's status/stack/syscall file at the moment of pagefault, it's very interesting to know who was page fault initiator. Signed-off-by: Alexey Perevalov ---

[Qemu-devel] [PATCH 5/6] migration: send postcopy downtime back to source

Right now to initiate postcopy live migration need to send request to source machine and specify destination. User could request migration status by query-migrate qmp command on source machine, but postcopy downtime is being evaluated on destination, so it should be transmitted back to source.

[Qemu-devel] [PATCH 2/6] util: introduce glib-helper.c

There is a lack of g_int_cmp which compares pointers value in glib, xen_disk.c introduced its own, so the same function now requires in migration.c. So logically to move it into common place. Futher: maybe extend glib. Also this commit moves existing glib-compat.h into util/glib folder for

[Qemu-devel] [PATCH 4/6] migration: calculate downtime on dst side

This patch provides downtime calculation per vCPU, as a summary and as a overlapped value for all vCPUs. This approach just keeps tree with page fault addr as a key, and t1-t2 interval of pagefault time and page copy time, with affected vCPU bit mask. For more implementation details please see

[Qemu-devel] [PATCH 1/6] userfault: add pid into uffd_msg & update UFFD_FEATURE_*

This commit duplicates header of "userfaultfd: provide pid in userfault msg" into linux kernel. Signed-off-by: Alexey Perevalov --- linux-headers/linux/userfaultfd.h | 5 + 1 file changed, 5 insertions(+) diff --git a/linux-headers/linux/userfaultfd.h

[Qemu-devel] [PATCH 3/6] migration: add UFFD_FEATURE_THREAD_ID feature support

Userfaultfd mechanism is able to provide process thread id, in case when client request it with UFDD_API ioctl. Signed-off-by: Alexey Perevalov --- include/migration/postcopy-ram.h | 2 +- migration/migration.c| 2 +- migration/postcopy-ram.c | 12

[Qemu-devel] [PATCH 0/6] calculate downtime for postcopy live migration

This patch set includes downtime calculation on destination, sending it to source machine for statistics (query-migration). Also additional traceses here for track down who was pagefault initiator. This patch set is based on master branch of git://git.qemu-project.org/qemu.git base commit is

[Qemu-devel] [RFC v5 3/4] hw/intc/arm_gicv3_kvm: Implement pending table save

This patch adds the flush of the LPI pending bits into the redistributor pending tables. This happens on VM stop. There is no explicit restore as the tables are implicitly sync'ed on ITS table restore and on LPI enable at redistributor level. Signed-off-by: Eric Auger

[Qemu-devel] [RFC v5 4/4] hw/intc/arm_gicv3_its: Allow save/restore

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

[Qemu-devel] [RFC v5 2/4] hw/intc/arm_gicv3_its: Implement state save/restore

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 ITS tables on device pre_save() is too late since the

[Qemu-devel] [RFC v5 1/4] linux-headers: Update for vITS save/restore

This is a linux header update against 4.11-rc6 plus the non upstreamed ITS migration series. https://github.com/eauger/linux/tree/v4.11-rc6-its-mig-v5 It aims at enhancing the KVM user API with vITS save/restore capability. Those are new attributes supported in the ITS and GICv3 KVM device

[Qemu-devel] [RFC v5 0/4] vITS save/restore

This series allows ITS save/restore and migration use cases. It relies on not upstreamed kernel series [1]. ITS tables are flushed into guest RAM on VM stop while registers are save on pre_save() callback. Tables and registers are restored on ITS post_load(). Redistributor pending tables also

Re: [Qemu-devel] [Bug 1030666] Re: gdb can't proceed after a breakpoint

Hi, Thank you for your email, I remember this issue. Unfortunately I don’t have the time to try this right now, but I may be able to get to it in the next couple of weeks. Regards, Legorol From: Thomas Huth Sent: 07 April 2017 14:59 To: legorol@gmail.com Subject: [Bug 1030666] Re: gdb can't

Re: [Qemu-devel] [Qemu-block] [RFC] Proposed qcow2 extension: subcluster allocation

On Thu, Apr 13, 2017 at 09:06:19PM -0400, John Snow wrote: > So if we have a 1MB cluster with 64k subclusters as a hypothetical, if > we write just the first subcluster, we'll have a map like: > > X--- > > Whatever actually happens to exist in this space, whether it be a hole > we

Re: [Qemu-devel] [PATCH] char: Fix removing wrong GSource that be found by fd_in_tag

Hi, On 2017/4/14 18:10, Marc-André Lureau wrote: Hi - Original Message - We use fd_in_tag to find a GSource, fd_in_tag is return value of g_source_attach(GSource *source, GMainContext *context), the return value is unique only in the same context, so we may get the same values with

Re: [Qemu-devel] [PATCH] char: Fix removing wrong GSource that be found by fd_in_tag

Hi - Original Message - > We use fd_in_tag to find a GSource, fd_in_tag is return value of > g_source_attach(GSource *source, GMainContext *context), the return > value is unique only in the same context, so we may get the same > values with different 'context' parameters. > > It is no

Re: [Qemu-devel] [PATCH v9 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

On Fri, Apr 14, 2017 at 04:50:48AM +0300, Michael S. Tsirkin wrote: > On Thu, Apr 13, 2017 at 01:44:11PM -0700, Matthew Wilcox wrote: > > On Thu, Apr 13, 2017 at 05:35:03PM +0800, Wei Wang wrote: > > > 2) transfer the guest unused pages to the host so that they > > > can be skipped to migrate in

Re: [Qemu-devel] [PATCH for-2.9 4/5] block: Drain BH in bdrv_drained_begin

On 06/04/2017 23:37, Kevin Wolf wrote: > We used to poll BHs in earlier times. Commit 99723548 ('block: add BDS > field to count in-flight requests') changed this, without an explanation > in the commit message. > > Paolo, is this simply a bug in that commit, or do you rely on it > somewhere? I

Re: [Qemu-devel] [RFC 1/2] spec/vhost-user: Introduce secondary channel for slave initiated requests

Hi On Tue, Apr 11, 2017 at 5:53 PM Maxime Coquelin wrote: > Hi Marc-André, > > On 04/11/2017 03:06 PM, Marc-André Lureau wrote: > > Hi > > > > On Tue, Apr 11, 2017 at 12:10 PM Maxime Coquelin > > > wrote:

Re: [Qemu-devel] [PATCH v9 3/5] mm: function to offer a page block on the free list

On 04/14/2017 10:58 AM, Matthew Wilcox wrote: On Fri, Apr 14, 2017 at 10:30:27AM +0800, Wei Wang wrote: OK. What do you think if we add this: #if defined(CONFIG_VIRTIO_BALLOON) || defined(CONFIG_VIRTIO_BALLOON_MODULE) That's spelled "IS_ENABLED(CONFIG_VIRTIO_BALLOON)", FYI. Right, thanks.

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.9-rc5 v2] block: Drain BH in bdrv_drained_begin

On Fri, Apr 14, 2017 at 9:02 AM, Fam Zheng wrote: > @@ -398,11 +399,15 @@ void bdrv_drain_all(void); > */\ > assert(!bs_->wakeup); \ > bs_->wakeup = true;

Re: [Qemu-devel] [Xen-devel] [PATCH] configure: introduce --enable-xen-fb-backend

On 14/04/17 08:06, Oleksandr Andrushchenko wrote: > On 04/14/2017 03:12 AM, Stefano Stabellini wrote: >> On Tue, 11 Apr 2017, Oleksandr Andrushchenko wrote: >>> From: Oleksandr Andrushchenko >>> >>> For some use cases when Xen framebuffer/input backend >>> is not

[Qemu-devel] [BUG] network : windows os lost ip address of the network card  in some cases

we found this problem for a long time 。For example, if we has three network card in virtual xml file ，such as "network connection 1" / "network connection 2"/"network connection 3" 。 Echo network card has own ip address ，such as 192.168.1.1 / 2.1 /3.1 , when delete the first card ，reboot the

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.9-rc5 v2] block: Drain BH in bdrv_drained_begin

On Fri, Apr 14, 2017 at 9:02 AM, Fam Zheng wrote: > During block job completion, nothing is preventing > block_job_defer_to_main_loop_bh from being called in a nested > aio_poll(), which is a trouble, such as in this code path: > > qmp_block_commit > commit_active_start

[Qemu-devel] [PATCH v2 4/4] qdev: remove cannot_destroy_with_object_finalize_yet

As all users have been removed, we can remove cannot_destroy_with_object_finalize_yet field from the DeviceClass structure. Signed-off-by: Laurent Vivier --- include/hw/qdev-core.h | 13 - qmp.c | 5 - 2 files changed, 18 deletions(-) diff

[Qemu-devel] [PATCH v2 0/4] qdev: remove all remaining cannot_destroy_with_object_finalize_yet

This series removes all the remaining uses of cannot_destroy_with_object_finalize_yet to finally remove the flag itself. The ARM patch has already been sent alone and reviewed by Markus. I have tested the ppc one on ppc64 machine with KVM and using QDM device-list-properties command. For the

[Qemu-devel] [PATCH v2 1/4] arm: remove remaining cannot_destroy_with_object_finalize_yet

With commit ce5b1bbf624b ("exec: move cpu_exec_init() calls to realize functions"), we can now remove all the remaining cannot_destroy_with_object_finalize_yet as unsafe references have been moved to cpu_exec_realizefn(). (tested with QOM command provided by commit 4c315c27). Suggested-by: Markus

[Qemu-devel] [PATCH v2 2/4] ppc: remove cannot_destroy_with_object_finalize_yet

This removes the assert(kvm_enabled()) from kvmppc_host_cpu_initfn() This assert can never be triggered as the function is only registered when KVM is available (see also 4c315c2 "qdev: Protect device-list-properties against broken devices"). So we can remove the

[Qemu-devel] [PATCH v2 3/4] versatile: remove cannot_destroy_with_object_finalize_yet

cannot_destroy_with_object_finalize_yet was added by 4c315c2 ("qdev: Protect device-list-properties against broken devices") because "realview_pci" and "versatile_pci" were hanging during "device-list-properties" cleanup (an infinite loop in bus_unparent()). We have this problem because the child

[Qemu-devel] [PATCH v3 5/5] slirp: add a fake NC-SI backend

NC-SI (Network Controller Sideband Interface) enables a BMC to manage a set of NICs on a system. This model takes the simplest approach and reverses the NC-SI packets to pretend a NIC is present and exercise the Linux driver. The NCSI header file comes from mainline Linux and was untabified.

[Qemu-devel] [PATCH v3 4/5] aspeed: add a FTGMAC100 nic

There is a second NIC but we do not use it for the moment. We use the 'aspeed' property to tune the definition of the end of ring buffer bit for the Aspeed SoCs. Signed-off-by: Cédric Le Goater --- hw/arm/aspeed_soc.c | 21 +

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v9 2/5] virtio-balloon: VIRTIO_BALLOON_F_BALLOON_CHUNKS

On 04/14/2017 12:34 AM, Michael S. Tsirkin wrote: On Thu, Apr 13, 2017 at 05:35:05PM +0800, Wei Wang wrote: So we don't need the bitmap to talk to host, it is just a data structure we chose to maintain lists of pages, right? Right. bitmap is the way to gather pages to chunk. It's only needed

[Qemu-devel] [PATCH v3 2/5] net: add FTGMAC100 support

The FTGMAC100 device is an Ethernet controller with DMA function that can be found on Aspeed SoCs (which include NCSI). It is fully compliant with IEEE 802.3 specification for 10/100 Mbps Ethernet and IEEE 802.3z specification for 1000 Mbps Ethernet and includes Reduced Media Independent

[Qemu-devel] [PATCH v3 3/5] net/ftgmac100: add a 'aspeed' property

The Aspeed SoCs have a different definition of the end of the ring buffer bit. Add a property to specify which set of bits should be used by the NIC. Signed-off-by: Cédric Le Goater --- hw/net/ftgmac100.c | 17 +++-- include/hw/net/ftgmac100.h | 4 2

[Qemu-devel] [PATCH v3 1/5] hw/net: add MII definitions

This adds comments on the Basic mode control and status registers bit definitions. It also adds a couple of bits for 1000BASE-T and the RealTek 8211E PHY for the FTGMAC100 model to use. Signed-off-by: Cédric Le Goater Reviewed-by: Philippe Mathieu-Daudé ---

[Qemu-devel] [PATCH v3 0/5] FTGMAC100 nic model for the Aspeed SoCs

Hi, The Aspeed SoCs AST2400 and AST2500 have two FTGMAC100 ethernet controllers. This series proposes a model for this device and a way to customize the bit definitions which are slightly different from the Faraday definitions. The last patch adds a fake NC-SI (Network Controller Sideband

Re: [Qemu-devel] [PATCH for-2.9-rc5 v2] block: Drain BH in bdrv_drained_begin

On Fri, 04/14 16:02, Fam Zheng wrote: > @@ -167,8 +167,12 @@ static bool bdrv_drain_recurse(BlockDriverState *bs) > bs->drv->bdrv_drain(bs); > } > > -QLIST_FOREACH(child, >children, next) { > -waited |= bdrv_drain_recurse(child->bs); > +QLIST_FOREACH_SAFE(child,

[Qemu-devel] [PATCH for-2.9-rc5 v2] block: Drain BH in bdrv_drained_begin

During block job completion, nothing is preventing block_job_defer_to_main_loop_bh from being called in a nested aio_poll(), which is a trouble, such as in this code path: qmp_block_commit commit_active_start bdrv_reopen bdrv_reopen_multiple

Re: [Qemu-devel] [Qemu-block] [RFC] Proposed qcow2 extension: subcluster allocation

[skipped...] > Hi Denis, > > I've read this entire thread now and I really like Berto's summary which > I think is one of the best recaps of existing qcow2 problems and this > discussion so far. > > I understand your opinion that we should focus on compatible changes > before incompatible ones,

Re: [Qemu-devel] [Qemu-block] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster

On Fri, Apr 14, 2017 at 2:38 PM, Stefan Hajnoczi wrote: > On Fri, Apr 14, 2017 at 7:00 AM, Fam Zheng wrote: >> On Thu, 04/13 10:34, jemmy858...@gmail.com wrote: >>> From: Lidong Chen >>> >>> BLOCK_SIZE is (1 << 20), qcow2 cluster size

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.10] Revert "block/io: Comment out permission assertions"

On Fri, Apr 14, 2017 at 2:10 AM, John Snow wrote: > On 04/13/2017 10:34 AM, Max Reitz wrote: >> On 13.04.2017 15:28, Stefan Hajnoczi wrote: >>> On Tue, Apr 11, 2017 at 05:52:26PM +0200, Max Reitz wrote: This reverts commit e3e0003a8f6570aba1421ef99a0b383a43371a74.

[Qemu-devel] [Bug 1681439] Re: qemu-system-x86_64: hw/ide/core.c:685: ide_cancel_dma_sync: Assertion `s->bus->dma->aiocb == NULL' failed.

> Let's try and see if this doesn't fix your problem: > https://github.com/jnsnow/qemu/commit/57bf2ccdfe8dd35838c1e6642bf9bd76dc9ad1a9 Sadly, no, it still crashes. Same assertion, same canceled command, same time to reproduce. -- You received this bug notification because you are a member of

Re: [Qemu-devel] [PATCH v2 0/5] FTGMAC100 nic model for the Aspeed SoCs

On 04/14/2017 08:26 AM, Jason Wang wrote: > > > On 2017年04月13日 17:41, Cédric Le Goater wrote: >> Hi, >> >> The Aspeed SoCs AST2400 and AST2500 have two FTGMAC100 ethernet >> controllers. This serie proposes a model for this device and a way to >> customize the bit definitions which are slightly

Re: [Qemu-devel] [PATCH 02/15] colo-compare: implement the process of checkpoint

On 2017年04月14日 14:22, Hailiang Zhang wrote: Hi Jason, On 2017/4/14 13:57, Jason Wang wrote: On 2017年02月22日 17:31, Zhang Chen wrote: On 02/22/2017 11:42 AM, zhanghailiang wrote: While do checkpoint, we need to flush all the unhandled packets, By using the filter notifier mechanism, we can

Re: [Qemu-devel] [Qemu-block] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster

On Fri, Apr 14, 2017 at 7:00 AM, Fam Zheng wrote: > On Thu, 04/13 10:34, jemmy858...@gmail.com wrote: >> From: Lidong Chen >> >> BLOCK_SIZE is (1 << 20), qcow2 cluster size is 65536 by default, >> this may cause the qcow2 file size to be bigger after

Re: [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster

On Fri, Apr 14, 2017 at 2:00 PM, Fam Zheng wrote: > On Thu, 04/13 10:34, jemmy858...@gmail.com wrote: >> From: Lidong Chen >> >> BLOCK_SIZE is (1 << 20), qcow2 cluster size is 65536 by default, >> this may cause the qcow2 file size to be bigger after

[Qemu-devel] [PATCH] net/filter-rewriter.c: Fix trace_event print bug

Because of inet_ntoa() return a statically allocated buffer, subsequent calls will overwrite, So we fix this bug. Signed-off-by: Zhang Chen --- net/filter-rewriter.c | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git

Re: [Qemu-devel] [PATCH] progress: Show current progress on SIGINFO

On Thu, 04/13 22:38, Max Reitz wrote: > On 08.02.2017 00:57, Max Reitz wrote: > > Currently we only print progress information on retrieval of SIGUSR1. > > Some systems have a dedicated SIGINFO for this, however, so it should be > > handled appropriately if it is available. > > > > Buglink:

Re: [Qemu-devel] [PATCH v2 0/5] FTGMAC100 nic model for the Aspeed SoCs

On 2017年04月13日 17:41, Cédric Le Goater wrote: Hi, The Aspeed SoCs AST2400 and AST2500 have two FTGMAC100 ethernet controllers. This serie proposes a model for this device and a way to customize the bit definitions which are slightly different from the Faraday definitions. The last patch adds

Re: [Qemu-devel] [PATCH 02/15] colo-compare: implement the process of checkpoint

Hi Jason, On 2017/4/14 13:57, Jason Wang wrote: On 2017年02月22日 17:31, Zhang Chen wrote: On 02/22/2017 11:42 AM, zhanghailiang wrote: While do checkpoint, we need to flush all the unhandled packets, By using the filter notifier mechanism, we can easily to notify every compare object to do

Re: [Qemu-devel] [Xen-devel][PATCH] configure: introduce --enable-xen-fb-backend

On 04/14/2017 03:12 AM, Stefano Stabellini wrote: On Tue, 11 Apr 2017, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko For some use cases when Xen framebuffer/input backend is not a part of Qemu it is required to disable it, because of

Re: [Qemu-devel] [PATCH 0/5] mc146818rtc: fix Windows VM clock faster

On 04/14/2017 01:09 PM, Paolo Bonzini wrote: On 13/04/2017 16:52, Xiao Guangrong wrote: On 04/13/2017 04:39 PM, Xiao Guangrong wrote: On 04/13/2017 02:37 PM, Paolo Bonzini wrote: However, I think that the above should be exactly how the RTC should work. The original RTC circuit had 22

Re: [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster

On Thu, 04/13 10:34, jemmy858...@gmail.com wrote: > From: Lidong Chen > > BLOCK_SIZE is (1 << 20), qcow2 cluster size is 65536 by default, > this may cause the qcow2 file size to be bigger after migration. > This patch checks each cluster, using blk_pwrite_zeroes for each