Hi,
This 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 0/6] Introduce new iommu notifier framework
Type: series
Message-id: 1509426425-23890-1-git-send-
From: Peter Xu
Provide AddressSpaceOps.iommu_get() in Intel IOMMU emulator.
Signed-off-by: Peter Xu
Signed-off-by: Liu, Yi L
---
hw/i386/intel_iommu.c | 7 +++
include/hw/i386/intel_iommu.h | 2 ++
2 files changed, 9 insertions(+)
diff --git a/hw/i386/intel_iommu.c b/hw/i386/inte
This patch introduce a notify framework for IOMMUObject.iommu_notifiers.
Introduce VFIOGuestIOMMUObject is to link VFIO Container and the new
IOMMUObject notififiers.
VFIOGuestIOMMUObject instance is allocated when device is assigned and
meanwhile vIOMMU is exposed to guest.
If there is IOMMUObje
From: Peter Xu
AddressSpaceOps is similar to MemoryRegionOps, it's just for address
spaces to store arch-specific hooks.
The first hook I would like to introduce is iommu_get(). Return an
IOMMUObject behind the AddressSpace.
For systems that have IOMMUs, we will create a special address
space p
This is an example to show the usage of IOMMUObject based notifier.
For passthru devices, if there is a vIOMMU exposed to guest, guest
would issue iommu operation on the devices. And the iommu operations
needs to be propagated to host iommu driver.
In future, the IOMMUObject notifiers may include
This patchset is a follow-up of Peter Xu's patchset as the link below.
In brief, Peter's patchset is to introduce a common IOMMU object which
is not depending on platform (x86/ppc/...), or bus (PCI/...). And based
on it, a iommu object based notifier framework is introduced and also
AddressSpaceOps
From: Peter Xu
IOMMU notifiers before are mostly used for [dev-]IOTLB stuffs. It is not
suitable for other kind of notifiers (one example would be the future
virt-svm support). Considering that current notifiers are targeted for
per memory region, renaming the iommu notifier definitions.
* all t
Rename GuestIOMMU to GuestIOMMUMR as the existing GuestIOMMU is
for MemoryRegion related notifiers.
Signed-off-by: Liu, Yi L
---
hw/vfio/common.c | 15 ---
include/hw/vfio/vfio-common.h | 8
2 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/hw/vf
Why could I not find in ovs-dpdk maillist? could some one give the bug
number?
2017-10-27 15:08 GMT+08:00 Daniel P. Berrange :
> On Fri, Oct 27, 2017 at 11:28:33AM +0800, Sam wrote:
> > After restart ovs-dpdk(which is openvswitch with dpdk lib), memory is
> > released.
> >
> > But problem is in p
I found that hotplug virtio-blk device will lead to qemu crash.
Re-production steps:
1. Run VM named vm001
2. Create a virtio-blk.xml which contains wrong configurations:
3. Run command : virsh attach-device vm001 vm001
Libvirt will return err msg:
error: Failed t
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/997631
Title:
Windows 2008
On 30/10/17 18:52, Daniel P. Berrange wrote:
> On Mon, Oct 30, 2017 at 10:49:01AM +1100, Alexey Kardashevskiy wrote:
>> On 30/10/17 03:29, Daniel P. Berrange wrote:
>>> On Mon, Oct 30, 2017 at 01:08:56AM +1100, Alexey Kardashevskiy wrote:
I run ./scripts/git-submodule.sh on a server (wher
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: Tuesday, 31 October 2017 03:25
>
> On 20 October 2017 at 22:49, Andrew Baumann
> wrote:
> > On a successful address translation instruction, PAR is supposed to
> > contain cacheability and shareability attributes determined by the
>
Hi,
I just found out someone managed to get a retrocomputing devroom
accepted at FOSDEM:
https://lists.fosdem.org/pipermail/retrocomputing-devroom/2017-October/00.html
https://www.elpauer.org/2017/10/retrocomputing-devroom-call-for-participation/comment-page-1/
Surely there are a lot of subj
On 10/30/2017 06:29 PM, Daniel Henrique Barboza wrote:
On 10/30/2017 06:12 PM, David Gibson wrote:
On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote:
This series implements a few RTAS hypercalls in tests/libqos
that, used together, implement the DRC state transition de
On Mon, 30 Oct 2017, Peter Maydell wrote:
> On 26 October 2017 at 00:28, Stefano Stabellini
> wrote:
> > extended_addresses_enabled calls arm_el_is_aa64, hardcoding exception
> > level 1. Instead, add an additional "el" argument to
> > extended_addresses_enabled.
> >
> > The caller will pass the
From: Vladimir Sementsov-Ogievskiy
In following patch nbd_receive_reply will be used both for simple
and structured reply header receiving.
NBDReply is altered into union of simple reply header and structured
reply chunk header, simple error translation moved to block/nbd-client
to be consistent
The NBD spec permits including a human-readable error string if
structured replies are in force, so we might as well send the
client the message that we logged on any error.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
Message-Id: <20171027104037.8319-9-ebl...@redhat.com>
When the server is read-only, we were already reporting an error
message for NBD_CMD_WRITE_ZEROES, but failed to set errp for a
similar NBD_CMD_WRITE. This will matter more once structured
replies allow the server to propagate the errp information back
to the client. While at it, use an error mes
From: Vladimir Sementsov-Ogievskiy
Minimal implementation of structured read: one structured reply chunk,
no segmentation.
Minimal structured error implementation: no text message.
Support DF flag, but just ignore it, as there is no segmentation any
way.
Signed-off-by: Vladimir Sementsov-Ogievsk
From: Vladimir Sementsov-Ogievskiy
Minimal implementation: for structured error only error_report error
message.
Note that test 83 is now more verbose, because the implementation
prints more warnings about unexpected communication errors; perhaps
future patches should tone things down by using t
Consolidate the response for a non-zero-length option payload
into a new function, nbd_reject_length(). This check will
also be used when introducing support for structured replies.
Note that STARTTLS response differs based on time: if the connection
is still unencrypted, we set fatal to true (a
Upcoming patches will implement the NBD structured reply
extension [1] for both client and server roles. Declare the
constants, structs, and lookup routines that will be valuable
whether the server or client code is backported in isolation.
This includes moving one constant from an internal heade
An upcoming change to block/nbd-client.c will want to read the
tail of a structured reply chunk directly from the wire. Move
this function to make it easier.
Based on a patch from Vladimir Sementsov-Ogievskiy.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
Message-Id: <201
Instead of making each caller check whether a transmission error
occurred, we can sink a common error check to the end of the loop.
Signed-off-by: Eric Blake
Message-Id: <20171027104037.8319-6-ebl...@redhat.com>
[eblake: squash in compiler warning fix]
Reviewed-by: Vladimir Sementsov-Ogievskiy
-
NBD errors were originally sent over the wire based on Linux errno
values; but not all the world is Linux, and not all platforms share
the same values. Since a number isn't very easy to decipher on all
platforms, update the trace messages to include the name of NBD
errors being sent/received over
This is needed in preparation for structured reply handling,
as we will be performing the translation from NBD error to
system errno value higher in the stack at block/nbd-client.c.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
Message-Id: <20171027104037.8319-3-ebl...@redh
From: Vladimir Sementsov-Ogievskiy
Split out nbd_request_simple_option to be reused for structured reply
option.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Eric Blake
Message-Id: <20171027104037.8319-10-ebl...@redhat.com>
---
nbd/client.c | 70 +
The following changes since commit abf6e752e55b2f5afb48303429dea2db7c3a62de:
Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20171030' into
staging (2017-10-30 13:02:45 +)
are available in the git repository at:
git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2017-
On Mon, Oct 30, 2017 at 12:21:07PM +0100, Juan Quintela wrote:
> For tcp sockets we read back what is the socket/address. So we know
> what is the port that we are listening into.
>
> Looked all callers of the function, and they just create the addr, use
> it, and drop it, so no problem that we a
On 10/30/2017 09:11 PM, Eric Blake wrote:
> On 10/30/2017 06:22 PM, Vladimir Sementsov-Ogievskiy wrote:
>> 27.10.2017 13:40, Eric Blake wrote:
>>> Consolidate the response for a non-zero-length option payload
>>> into a new function, nbd_reject_length(). This check will
>>> also be used when intro
On 10/30/2017 06:12 PM, David Gibson wrote:
On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote:
This series implements a few RTAS hypercalls in tests/libqos
that, used together, implement the DRC state transition described
in PAPR 2.7+, 13.4.
This started as an attempt of
From: ZhiPeng Lu
Use hmp_handle_error instend of error_report_err to set error.
Signed-off-by: ZhiPeng Lu
Reviewed-by: Jiyun Fan
Message-Id: <1508411793-22868-1-git-send-email-lu.zhip...@zte.com.cn>
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Dr. Da
From: Greg Kurz
If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
causes QEMU to exit:
(qemu) device_del cpu1
(qemu) info cpus
qemu:qemu_cpu_kick_thread: No such process
This happens because "cpu" stores the pointer to the selected CPU into
the monitor structure. When t
From: "Dr. David Alan Gilbert"
The following changes since commit abf6e752e55b2f5afb48303429dea2db7c3a62de:
Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20171030' into
staging (2017-10-30 13:02:45 +)
are available in the Git repository at:
gi
* Eric Blake (ebl...@redhat.com) wrote:
> On 10/30/2017 03:32 PM, Dr. David Alan Gilbert wrote:
>
> > Now, the real challenge is how to deal with a filename with a comma in;
> >drive_add 1 "file=foo,bar"
> >Could not open 'foo': No such file or directory
> >
>
> Does HMP use the QemuOpts
On Thu, Oct 26, 2017 at 06:22:47PM -0200, Daniel Henrique Barboza wrote:
> This series implements a few RTAS hypercalls in tests/libqos
> that, used together, implement the DRC state transition described
> in PAPR 2.7+, 13.4.
>
> This started as an attempt of implementing hot unplug qtests for the
On 10/30/2017 06:22 PM, Vladimir Sementsov-Ogievskiy wrote:
> 27.10.2017 13:40, Eric Blake wrote:
>> Consolidate the response for a non-zero-length option payload
>> into a new function, nbd_reject_length(). This check will
>> also be used when introducing support for structured replies.
>>
>> Not
On 10/30/2017 03:32 PM, Dr. David Alan Gilbert wrote:
> Now, the real challenge is how to deal with a filename with a comma in;
>drive_add 1 "file=foo,bar"
>Could not open 'foo': No such file or directory
>
Does HMP use the QemuOpts parser? If so, try:
drive_add 1 "file=foo,,bar"
(tha
On 20 October 2017 at 22:49, Andrew Baumann
wrote:
> On a successful address translation instruction, PAR is supposed to
> contain cacheability and shareability attributes determined by the
> translation. We previously returned 0 for these bits (in line with the
> general strategy of ignoring cach
On Mon, Oct 30, 2017 at 4:00 PM, Mark Cave-Ayland
wrote:
> On 27/10/17 17:42, Philippe Mathieu-Daudé wrote:
[...]
>> If you don't accept my comments (or don't have time) about keeping
>> "hw/sparc/sparc32_dma.h" generic and moving network/scsi parts in
>> "hw/sparc/sun4m.h" you can still add to yo
On 30/10/17 18:45, Philippe Mathieu-Daudé wrote:
>>> +/*
>>> + * QEMU AMD PC-Net II (Am79C970A) emulation
>>
>> Filename says this is Lance ethernet, but the comment says it's PC-Net ?
>
> According to the datasheet for Am79C970A, the original Lance is an
> Am7990 devic
On 10/30/2017 04:57 AM, Christian Borntraeger wrote:
adding qemu devel and add Daniel and Erik from libvirt to keep them in the loop.
On 10/29/2017 12:11 PM, Cornelia Huck wrote:
On Fri, 13 Oct 2017 13:38:45 -0400
Tony Krowiak wrote:
Tony Krowiak (19):
KVM: s390: SIE considerations for AP
On 27/10/17 17:42, Philippe Mathieu-Daudé wrote:
> Hi Mark,
>
> On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote:
>> This patchset aims to tidy-up the sparc32_dma code by improving the
>> modelling of the espdma/ledma devices using both QOM and the memory
>> API which didn't exist when the code was
On 10/30/2017 06:38 PM, Pierre Morel wrote:
> On 30/10/2017 18:08, Christian Borntraeger wrote:
>>
>> On 10/30/2017 05:59 PM, Cornelia Huck wrote:
>>> On Mon, 30 Oct 2017 14:48:23 +0100
>>> Christian Borntraeger wrote:
>>>
>>>
FWIW, I am testing a guest patch that enables zPCI without
On Mon, Oct 30, 2017 at 3:51 PM, Mark Cave-Ayland
wrote:
> On 27/10/17 17:18, Philippe Mathieu-Daudé wrote:
>> On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote:
>>> Create a new SPARC32_DMA container object (including an appropriate
>>> container
>>> memory region) and add instances of the SPARC32_
On 27/10/17 17:18, Philippe Mathieu-Daudé wrote:
> On 10/25/2017 12:59 PM, Mark Cave-Ayland wrote:
>> Create a new SPARC32_DMA container object (including an appropriate container
>> memory region) and add instances of the SPARC32_ESPDMA_DEVICE and
>> SPARC32_LEDMA_DEVICE as child objects. The bene
* Greg Kurz (gr...@kaod.org) wrote:
> If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> causes QEMU to exit:
>
> (qemu) device_del cpu1
> (qemu) info cpus
> qemu:qemu_cpu_kick_thread: No such process
>
> This happens because "cpu" stores the pointer to the selected CPU
Hi Mark,
>> +/*
>> + * QEMU AMD PC-Net II (Am79C970A) emulation
>
> Filename says this is Lance ethernet, but the comment says it's PC-Net ?
According to the datasheet for Am79C970A, the original Lance is an
Am7990 device and the Am79C970A aka PCNet-PCI II as emulate
30.10.2017 19:32, Vladimir Sementsov-Ogievskiy wrote:
Hi all!
There is a new version of dirty bitmap postcopy migration series.
v8
clone: tag postcopy-v8 from https://src.openvz.org/scm/~vsementsov/qemu.git
online: https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=postcopy-v8
comp
On 30/10/17 13:22, Peter Maydell wrote:
> On 30 October 2017 at 13:10, Mark Cave-Ayland
> wrote:
>> On 26/10/17 11:12, Mark Cave-Ayland wrote:
>>> On 25/10/17 18:47, Peter Maydell wrote:
On 25 October 2017 at 16:59, Mark Cave-Ayland wrote:
> --- /dev/null
> +++ b/include/hw/net/lance
examples configuring with '--enable-kvm --disable-tcg'
- before
$ qemu-system-x86_64 -accel help
Possible accelerators: kvm, xen, hax, tcg
$ qemu-system-x86_64 -accel tcg
qemu-system-x86_64: -machine accel=tcg: No accelerator found
# qemu-system-x86_64 -accel hax
qemu-system-x86_64:
There would be savevm states (dirty-bitmap) which can migrate only in
postcopy stage. The corresponding pending is introduced here.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Juan Quintela
---
8.1: add new version for cmma_save_pending too.
include/migration/register.h | 17 +++
Oops this isn't RFC anymore, this one is v1 ... sorry!
On Mon, Oct 30, 2017 at 3:14 PM, Philippe Mathieu-Daudé wrote:
[...]
> ---
> since RFC:
> - use much cleaner object_class_get_list(TYPE_ACCEL, false)
>
> vl.c | 39 ++-
> 1 file changed, 34 insertions(+)
30.10.2017 20:31, Dr. David Alan Gilbert wrote:
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
There would be savevm states (dirty-bitmap) which can migrate only in
postcopy stage. The corresponding pending is introduced here.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Revie
examples configuring with '--enable-kvm --disable-tcg'
- before
$ qemu-system-x86_64 -accel help
Possible accelerators: kvm, xen, hax, tcg
$ qemu-system-x86_64 -accel tcg
qemu-system-x86_64: -machine accel=tcg: No accelerator found
# qemu-system-x86_64 -accel hax
qemu-system-x86_64:
27.10.2017 13:45, Eric Blake wrote:
Commenting these two lines is enough to avoid the change to 083.out
in 12/12. That is evidence that we may want these two lines to be
trace points rather than error messages; or maybe we really do like
the extra verbosity in the case of an unexpected communica
On 26 October 2017 at 00:28, Stefano Stabellini wrote:
> extended_addresses_enabled calls arm_el_is_aa64, hardcoding exception
> level 1. Instead, add an additional "el" argument to
> extended_addresses_enabled.
>
> The caller will pass the right value. In most cases, it will be
> arm_current_el(e
27.10.2017 13:40, Eric Blake wrote:
From: Vladimir Sementsov-Ogievskiy
Minimal implementation: for structured error only error_report error
message.
Note that test 83 is now more verbose, because the implementation
prints more warnings about unexpected communication errors; perhaps
future patc
On 30/10/2017 18:08, Christian Borntraeger wrote:
On 10/30/2017 05:59 PM, Cornelia Huck wrote:
On Mon, 30 Oct 2017 14:48:23 +0100
Christian Borntraeger wrote:
FWIW, I am testing a guest patch that enables zPCI without AIS. Its as simple as
diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/
27.10.2017 13:40, Eric Blake wrote:
From: Vladimir Sementsov-Ogievskiy
Split out nbd_request_simple_option to be reused for structured reply
option.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Eric Blake
ok for me.
---
v6: error message tweak [Vladimir]
v5: only check le
* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> There would be savevm states (dirty-bitmap) which can migrate only in
> postcopy stage. The corresponding pending is introduced here.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> Reviewed-by: Juan Quintela
Note the error pa
27.10.2017 13:40, Eric Blake wrote:
From: Vladimir Sementsov-Ogievskiy
Minimal implementation of structured read: one structured reply chunk,
no segmentation.
Minimal structured error implementation: no text message.
Support DF flag, but just ignore it, as there is no segmentation any
way.
Sig
27.10.2017 13:40, Eric Blake wrote:
Consolidate the response for a non-zero-length option payload
into a new function, nbd_reject_length(). This check will
also be used when introducing support for structured replies.
Note that STARTTLS response differs based on time: if the connection
is still
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728661/+attachment/5000235/+files/test.img_1728661.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728661
Title:
* Ross Lagerwall (ross.lagerw...@citrix.com) wrote:
> Hi,
>
> I have found an issue where QEMU emits the RESUME event during startup when
> it starts VM execution, but it is not possible to receive this event.
>
> To repro this, run:
> qemu-system-i386 -m 256 -trace
> enable=monitor_protocol_even
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728657/+attachment/5000204/+files/test.img_1728657.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728657
Title:
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.img
#
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728660/+attachment/5000223/+files/test.img_1728660.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728660
Title:
On 10/30/2017 05:59 PM, Cornelia Huck wrote:
> On Mon, 30 Oct 2017 14:48:23 +0100
> Christian Borntraeger wrote:
>
>
>> FWIW, I am testing a guest patch that enables zPCI without AIS. Its as
>> simple as
>>
>>
>> diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c
>> index 7b30af5..9b24836
* Programmingkid (programmingk...@gmail.com) wrote:
>
> > On Oct 30, 2017, at 10:32 AM, Dr. David Alan Gilbert
> > wrote:
> >
> > * Programmingkid (programmingk...@gmail.com) wrote:
> >>
> >>> On Oct 29, 2017, at 6:21 AM, Dr. David Alan Gilbert
> >>> wrote:
> >>>
> >>> * Eric Blake (ebl...@
On Mon, 30 Oct 2017 14:48:23 +0100
Christian Borntraeger wrote:
> FWIW, I am testing a guest patch that enables zPCI without AIS. Its as simple
> as
>
>
> diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c
> index 7b30af5..9b24836 100644
> --- a/arch/s390/pci/pci.c
> +++ b/arch/s390/pci/p
Cc'ing Stefan and Trivial
On 10/30/2017 01:07 PM, Doug Gale wrote:
> From 0e27b5dca8f4f32a1b194e1b3544be77dd4f45d9 Mon Sep 17 00:00:00 2001
> From: Doug Gale
> Date: Mon, 30 Oct 2017 09:28:43 -0400
> Subject: [PATCH] nvme: Add tracing
>
^ to remove from commit description, maybe maintainer taki
27.10.2017 13:40, Eric Blake wrote:
Instead of making each caller check whether a transmission error
occurred, we can sink a common error check to the end of the loop.
Signed-off-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
--
Best regards,
Vladimir
There would be savevm states (dirty-bitmap) which can migrate only in
postcopy stage. The corresponding pending is introduced here.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Juan Quintela
---
include/migration/register.h | 17 +++--
migration/savevm.h | 5 +
To just release successor and unfreeze bitmap without any additional
work.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Denis V. Lunev
---
include/block/dirty-bitmap.h | 2 ++
block/dirty-bitmap.c | 14 ++
2 files changed, 16 insertions(+)
diff --git a/includ
It is needed to realize bdrv_dirty_bitmap_release_successor in
the following patch.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/dirty-bitmap.c | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c
inde
Hi all!
There is a new version of dirty bitmap postcopy migration series.
v8
clone: tag postcopy-v8 from https://src.openvz.org/scm/~vsementsov/qemu.git
online: https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=postcopy-v8
- rebased on master
- patches 01-03 from v7 are already merge
Postcopy migration of dirty bitmaps. Only named dirty bitmaps,
associated with root nodes and non-root named nodes are migrated.
If destination qemu is already containing a dirty bitmap with the same name
as a migrated bitmap (for the same node), then, if their granularities are
the same the migra
Only-postcopy savevm states (dirty-bitmap) don't need live iteration, so
to disable them and stop transporting empty sections there is a new
savevm handler.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Juan Quintela
---
include/migration/register.h | 1 +
migration/savevm.c
When testing migration, auto-generated by qemu node-names differs in
source and destination qemu and migration fails. After this patch,
auto-generated by iotest nodenames will be the same.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
tests/qemu-iotests/iotests.py | 2 +
The test starts two vms (vm_a, vm_b), create dirty bitmap in
the first one, do several writes to corresponding device and
then migrate vm_a to vm_b with dirty bitmaps.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
---
tests/qemu-iotests/169 | 86
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: John Snow
Reviewed-by: Eric Blake
Reviewed-by: Juan Quintela
---
qapi/migration.json | 6 +-
migration/migration.h | 1 +
migration/migration.c | 9 +
3 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/qapi/migr
Make it possible to set bitmap 'frozen' without a successor.
This is needed to protect the bitmap during outgoing bitmap postcopy
migration.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/dirty-bitmap.h | 1 +
block/dirty-bitmap.c | 22 --
2 files chan
Enabling bitmap successor is necessary to enable successors of bitmaps
being migrated before target vm start.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/dirty-bitmap.h | 1 +
block/dirty-bitmap.c | 8
2 files changed, 9 insertions(+)
diff --git a/include/bloc
Test that persistent bitmap migrates and its persistance property
migrates too.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/169 | 21 ++---
tests/qemu-iotests/169.out | 4 ++--
2 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/tests/qemu-
Test
- start two vms (vm_a, vm_b)
- in a
- do writes from set A
- do writes from set B
- fix bitmap sha256
- clear bitmap
- do writes from set A
- start migration
- than, in b
- wait vm start (postcopy should start)
- do writes from set B
- check bitmap sha256
Enable postcopy if dirty bitmap migration is endabled.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Juan Quintela
---
migration/migration.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/migration/migration.c b/migration/migration.c
index 1526cd4bff..e973837bfd
Add function opposite to qemu_get_counted_string.
qemu_put_counted_string puts one-byte length of the string (string
should not be longer than 255 characters), and then it puts the string,
without last zero byte.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: John Snow
Reviewed-by: Jua
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728643/+attachment/5000185/+files/test.img_1728643.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728643
Title:
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached files named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# cp test.img copy
On Mon, Oct 30, 2017 at 11:07:20AM +, Hatayama, Daisuke wrote:
> > From: Marc-André Lureau
> >
> > Since qemu 2.9, DMA write operations are allowed. However, usage of this
> > interface from kernel or user-space is strongly discouraged by the
> > maintainers. This patch is meant for experiment
>From 0e27b5dca8f4f32a1b194e1b3544be77dd4f45d9 Mon Sep 17 00:00:00 2001
From: Doug Gale
Date: Mon, 30 Oct 2017 09:28:43 -0400
Subject: [PATCH] nvme: Add tracing
Add trace output for commands, errors, and undefined behavior.
Add guest error log output for undefined behavior.
Report invalid undefin
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached files named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728639/+attachment/5000182/+files/test.img.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728639
Title:
qemu-
On Tue, 17 Oct 2017 10:16:22 +0200
Greg Kurz wrote:
> If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> causes QEMU to exit:
>
> (qemu) device_del cpu1
> (qemu) info cpus
> qemu:qemu_cpu_kick_thread: No such process
>
> This happens because "cpu" stores the pointer to
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728635/+attachment/5000176/+files/test.img.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728635
Title:
qemu-
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# cp test.img copy.
1 - 100 of 184 matches
Mail list logo
