From: Subbaraya Sundeep
This patch set emulates Ethernet MAC block
present in Microsemi SmartFusion2 SoC.
Testing:
1. Download u-boot.bin, uImage and msf2-devkit.dtb from
https://github.com/Subbaraya-Sundeep/qemu-test-binaries.git
2. Copy uImage and msf2-devkit.dtb to suitable Qemu tftp dire
On 11/21/19 4:28 PM, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
ping?
Did this fall through the cracks?
Certainly =) Thanks for noticing.
This now need a (trivial) rebase.
I'll respin for 5.0.
On 6/26/19 2:20 PM, Philippe Mathieu-Daudé wrote:
Another trivial cleanup series.
Philippe Mathieu-Daudé writes:
> ping?
Did this fall through the cracks?
> On 6/26/19 2:20 PM, Philippe Mathieu-Daudé wrote:
>> Another trivial cleanup series.
>>
>> Philippe Mathieu-Daudé (2):
>> MAINTAINERS: Add missing m48t59 files to the PReP section
>> hw/timer/m48t59: Convert debug p
* Dr. David Alan Gilbert (git) (dgilb...@redhat.com) wrote:
> From: "Dr. David Alan Gilbert"
>
> Hi,
> This fixes a deadlock that can occur on the source after
> a failed RDMA migration and cleans up some warning messages
> that can appear during normal completion.
>
> https://bugzilla.redhat.
On 9/13/19 1:12 AM, Michael Roth wrote:
> Bruce noticed that we cannot build `make efi` target from the v4.1.0
> tarball. This is due to a failure on the part of the make-release script
> to pull in submodules nested under other submodules, as well as
> Makefile.edk2's assumptions about being in a
On Thu, Sep 19, 2019 at 01:54:40PM +0200, Philippe Mathieu-Daudé wrote:
> On 9/19/19 1:41 PM, Daniel P. Berrangé wrote:
> > On Thu, Sep 19, 2019 at 01:18:57PM +0200, Stefan Weil wrote:
> >> Am 19.09.2019 um 12:59 schrieb Philippe Mathieu-Daudé:
> >>> Add a job to cross-build QEMU with WHPX enabled.
On Thu, Sep 19, 2019 at 01:18:57PM +0200, Stefan Weil wrote:
> Am 19.09.2019 um 12:59 schrieb Philippe Mathieu-Daudé:
> > Add a job to cross-build QEMU with WHPX enabled.
> >
> > Use the Win10SDK headers from the Android Project, as commented
> > in https://lists.gnu.org/archive/html/qemu-devel/201
On 9/19/19 1:41 PM, Daniel P. Berrangé wrote:
> On Thu, Sep 19, 2019 at 01:18:57PM +0200, Stefan Weil wrote:
>> Am 19.09.2019 um 12:59 schrieb Philippe Mathieu-Daudé:
>>> Add a job to cross-build QEMU with WHPX enabled.
>>>
>>> Use the Win10SDK headers from the Android Project, as commented
>>> in
On 9/19/19 1:18 PM, Stefan Weil wrote:
> Am 19.09.2019 um 12:59 schrieb Philippe Mathieu-Daudé:
>> Add a job to cross-build QEMU with WHPX enabled.
>>
>> Use the Win10SDK headers from the Android Project, as commented
>> in https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03842.html
>>
>> B
On 9/19/19 1:09 PM, Thomas Huth wrote:
> On 19/09/2019 12.59, Philippe Mathieu-Daudé wrote:
>> Add a job to cross-build QEMU with WHPX enabled.
>>
>> Use the Win10SDK headers from the Android Project, as commented
>> in https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03842.html
>>
>> Based
Am 19.09.2019 um 12:59 schrieb Philippe Mathieu-Daudé:
> Add a job to cross-build QEMU with WHPX enabled.
>
> Use the Win10SDK headers from the Android Project, as commented
> in https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03842.html
>
> Based-on: <20190918121101.30690-1-phi...@redhat.
On 19/09/2019 12.59, Philippe Mathieu-Daudé wrote:
> Add a job to cross-build QEMU with WHPX enabled.
>
> Use the Win10SDK headers from the Android Project, as commented
> in https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03842.html
>
> Based-on: <20190918121101.30690-1-phi...@redhat.co
Add a job to cross-build QEMU with WHPX enabled.
Use the Win10SDK headers from the Android Project, as commented
in https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03842.html
Based-on: <20190918121101.30690-1-phi...@redhat.com>
https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg038
On Wed, Sep 11, 2019 at 04:58:16PM +0200, Stefan Hajnoczi wrote:
> Small fixes to the -audiodev documentation.
>
> Stefan Hajnoczi (2):
> audio: fix buffer-length typo in documentation
> audio: add -audiodev pa,in|out.latency= to documentation
>
> qemu-options.hx | 8 ++--
> 1 file chang
Add 'features' field in the schema for commands and add a feature flag
to advertise that the fix for savevm [1] is present.
[1] https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03487.html
Peter Krempa (2):
qapi: Add feature flags to commands in qapi introspection
qapi: Allow introspec
On Tue, Sep 17, 2019 at 13:04:41 +0200, Kevin Wolf wrote:
> This fixes internal snapshots with separately defined protocol nodes
> (like libvirt will do with -blockdev).
The code change is exactly what I thought would be necessary in this
case. I've tested it with my blockdev code in libvirt enabl
Try #2 using PCI config space of MCH to negotiate/lock SMRAM
at 0x3.
CC: yingwen.c...@intel.com
CC: de...@edk2.groups.io
CC: phillip.go...@oracle.com
CC: alex.william...@redhat.com
CC: jiewen@intel.com
CC: jun.nakaj...@intel.com
CC: michael.d.kin...@intel.com
CC: pbonz...@redhat.com
CC:
This fixes internal snapshots with separately defined protocol nodes
(like libvirt will do with -blockdev).
Kevin Wolf (2):
block/snapshot: Restrict set of snapshot nodes
iotests: Test internal snapshots with -blockdev
block/snapshot.c | 26 +++--
tests/qemu-iotests/267
On Fri, Sep 13, 2019 at 05:35:05PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Hi,
> This fixes a deadlock that can occur on the source after
> a failed RDMA migration and cleans up some warning messages
> that can appear during normal completion.
>
> https:
On 9/13/19 6:17 AM, Sven Schnelle wrote:
> Sven Schnelle (2):
> target/hppa: prevent trashing of temporary in trans_mtctl()
> target/hppa: prevent trashing of temporary in do_depw_sar()
>
> target/hppa/translate.c | 15 ++-
> 1 file changed, 10 insertions(+), 5 deletions(-)
Thank
From: "Dr. David Alan Gilbert"
Hi,
This fixes a deadlock that can occur on the source after
a failed RDMA migration and cleans up some warning messages
that can appear during normal completion.
https://bugzilla.redhat.com/show_bug.cgi?id=1746787
Dr. David Alan Gilbert (2):
migration/rdma: D
Hi Stefan,
I'v been confused by trailing newline in trace reports,
so this series aims to fix this, by cleaning current
formats and add a check to catch new one introduced.
Regards,
Phil.
Philippe Mathieu-Daudé (2):
trace: Remove trailing newline in events
trace: Forbid event format ending
Hi Richard,
here are two patches for HPPA tcg. QEMU was crashing with a tcg assert
because dead temporaries where used. This could be observed at the end·
of a HP-UX 11.11 installation, or by running the STARBASE X11 demos in
HP-UX 10.20.
Thanks,
Sven
Sven Schnelle (2):
target/hppa: prevent tr
Bruce noticed that we cannot build `make efi` target from the v4.1.0
tarball. This is due to a failure on the part of the make-release script
to pull in submodules nested under other submodules, as well as
Makefile.edk2's assumptions about being in a git tree.
Suggestions for more robust solutions
Gerd Hoffmann (2):
vga: move access helpers to separate include file
ati: use vga_read_byte in ati_cursor_define
hw/display/vga-access.h | 49
hw/display/vga-helpers.h | 26 -
hw/display/ati.c | 11 +
hw/display/
Small fixes to the -audiodev documentation.
Stefan Hajnoczi (2):
audio: fix buffer-length typo in documentation
audio: add -audiodev pa,in|out.latency= to documentation
qemu-options.hx | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.21.0
The acceptance tests have been running primarily on x86_64 hosts, and
some tests will fail when run under non-x86 hosts or targets.
This series addresses issues that enables running the acceptance tests
under aarch64 hosts, and on other hosts using arm and aarch64 targets.
Cleber Rosa (2):
Pyth
Le 03/09/2019 à 15:35, Peter Maydell a écrit :
> On Thu, 22 Aug 2019 at 19:59, Richard Henderson
> wrote:
>>
>> This is inspired by the discussion in
>>
>>https://bugs.launchpad.net/qemu/+bug/1840922
>>
>> Previously I suggested a new CPUClass hook, but when I went
>> to implement that seemed
Hi Shu-Chun Weng via Qemu-devel!
We received your email, but were unable to deliver it because it
contains content which has been blacklisted by the list admin. Please
remove your application/pkcs7-signature attachments and send again.
You are also advised to configure your email client to send e
Ping. Patchwork links:
http://patchwork.ozlabs.org/patch/1151884/
http://patchwork.ozlabs.org/patch/1151883/
On Thu, Aug 22, 2019 at 4:14 PM Shu-Chun Weng wrote:
> Shu-Chun Weng (2):
> linux-user: add missing UDP and IPv6 setsockopt options
> linux-user: time stamping options for setsockopt
On Fri, Aug 30, 2019 at 07:07:21AM -0400, Igor Mammedov wrote:
> Fixes bc1fb850a3 (vl.c deprecate incorrect CPUs topology) that introduced
> regression.
Queued on machine-next. Thanks!
--
Eduardo
On Thu, 22 Aug 2019 at 19:59, Richard Henderson
wrote:
>
> This is inspired by the discussion in
>
>https://bugs.launchpad.net/qemu/+bug/1840922
>
> Previously I suggested a new CPUClass hook, but when I went
> to implement that seemed like overkill.
>
>
> r~
>
>
> Richard Henderson (2):
> l
Am 23.08.2019 um 20:47 hat Max Reitz geschrieben:
> Jobs are expected to return 0 on success. .bdrv_co_create() on the
> other hand is a block layer function, and as such returns a
> non-negative value on success.
I don't agree that >= 0 is the block layer way. The block layer uses
0/-errno for t
Am 23.08.2019 um 15:03 hat Max Reitz geschrieben:
> Hi,
>
> As suggested by Paolo, this series drops xfsctl() calls where we have
> working fallocate() alternatives. (And thus replaces “block/file-posix:
> Fix xfs_write_zeroes()”.)
>
> Unfortunately, we also use xfsctl() to inquire the request a
Hi Yuval,
On 8/18/19 4:21 PM, Yuval Shaia wrote:
The virtual address that is provided by the guest in post_send and
post_recv operations is related to the guest address space. This
address
space is unknown to the HCA resides on host so extra step in these
operations is needed to adjust the addre
Fixes bc1fb850a3 (vl.c deprecate incorrect CPUs topology) that introduced
regression.
Igor Mammedov (2):
tests: add qtest_qmp_device_add_qdict() helper
tests: cpu-plug-test: fix device_add for pc/q35 machines
tests/libqtest.h | 12 +
tests/cpu-plug-test.c | 62 ++
On Fri, Aug 02, 2019 at 05:35:56PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> This little series improves linux_ssh_mips_malta.py, both in the sense
> of code organization and in the sense of quantity of executed tests.
Thanks! I'm queueing it on python-next. The changes
28.08.2019. 23.24, "Cleber Rosa" је написао/ла:
>
> On Thu, Aug 22, 2019 at 07:59:07PM +0200, Aleksandar Markovic wrote:
> > 22.08.2019. 05.15, "Aleksandar Markovic"
је
> > написао/ла:
> > >
> > >
> > > 21.08.2019. 23.00, "Eduardo Habkost" је
написао/ла:
> > > >
> > > > On Wed, Aug 21, 2019 at 1
On 8/29/19 6:05 AM, Philippe Mathieu-Daudé wrote:
> This series update the git.orderfile to order Python and shell
> scripts before unordered files.
> This is particularly useful for changes in tests/qemu-iotests.
>
> Regards,
>
> Phil.
>
> Philippe Mathieu-Daudé (2):
> scripts/git.orderfil
Oops Cc'ing qemu-triv...@nongnu.org
On 8/29/19 12:05 PM, Philippe Mathieu-Daudé wrote:
> This series update the git.orderfile to order Python and shell
> scripts before unordered files.
> This is particularly useful for changes in tests/qemu-iotests.
>
> Regards,
>
> Phil.
>
> Philippe Mathieu-
On 8/29/19 5:05 AM, Philippe Mathieu-Daudé wrote:
> This series update the git.orderfile to order Python and shell
> scripts before unordered files.
> This is particularly useful for changes in tests/qemu-iotests.
>
> Regards,
>
> Phil.
>
> Philippe Mathieu-Daudé (2):
> scripts/git.orderfile:
This series update the git.orderfile to order Python and shell
scripts before unordered files.
This is particularly useful for changes in tests/qemu-iotests.
Regards,
Phil.
Philippe Mathieu-Daudé (2):
scripts/git.orderfile: Order Python files before unordered ones
scripts/git.orderfile: Orde
On Thu, Aug 22, 2019 at 07:59:07PM +0200, Aleksandar Markovic wrote:
> 22.08.2019. 05.15, "Aleksandar Markovic" је
> написао/ла:
> >
> >
> > 21.08.2019. 23.00, "Eduardo Habkost" је написао/ла:
> > >
> > > On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> > > > 02.08.2019. 17.
Markus Armbruster writes:
> Markus Armbruster (2):
> contrib/gitdm: filetype interface is not in order, fix
> contrib/gitdm: Add arm...@pond.sub.org to group-map-redhat
Queued to gitdm/next, thanks.
>
> contrib/gitdm/filetypes.txt| 2 +-
> contrib/gitdm/group-map-redhat | 1 +
> 2 fi
On 8/23/19 2:47 PM, Max Reitz wrote:
> Jobs are expected to return 0 on success. .bdrv_co_create() on the
> other hand is a block layer function, and as such returns a non-negative
> value on success.
>
> blockdev_create_run() should translate between the two (patch 1).
>
> Without patch 1, b
On Mon, 26 Aug 2019 at 16:15, Richard Henderson
wrote:
>
> As Laurent pointed out, gen_exception_insn is very different
> between aarch64 and aarch32, so we shouldn't accidentally
> redirect one to the other.
>
>
> r~
>
>
> Richard Henderson (2):
> Revert "target/arm: Use unallocated_encoding fo
On Fri, 16 Aug 2019 06:09:34 PDT (-0700), bmeng...@gmail.com wrote:
Currently when QEMU is given a bios image with only a file name and
its file path passed in "-L", it still reports file not found.
This series fixes the issue. This is especially helpful for creating
distro QEMU packages.
Bin
ping
22.08.2019. 19.59, "Aleksandar Markovic" је
написао/ла:
>
>
> 22.08.2019. 05.15, "Aleksandar Markovic" је
написао/ла:
> >
> >
> > 21.08.2019. 23.00, "Eduardo Habkost" је
написао/ла:
> > >
> > > On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> > > > 02.08.2019. 17.37,
As Laurent pointed out, gen_exception_insn is very different
between aarch64 and aarch32, so we shouldn't accidentally
redirect one to the other.
r~
Richard Henderson (2):
Revert "target/arm: Use unallocated_encoding for aarch32"
target/arm: Factor out unallocated_encoding for aarch32
tar
This is the second part of the patches I prepared
for this driver back when I worked on mdev-nvme.
Best regards,
Maxim Levitsky
Maxim Levitsky (2):
block/nvme: add support for write zeros
block/nvme: add support for discard
block/nvme.c | 155
Jobs are expected to return 0 on success. .bdrv_co_create() on the
other hand is a block layer function, and as such returns a non-negative
value on success.
blockdev_create_run() should translate between the two (patch 1).
Without patch 1, blockdev-create is likely to fail for VPC images.
Hence
Hi,
As suggested by Paolo, this series drops xfsctl() calls where we have
working fallocate() alternatives. (And thus replaces “block/file-posix:
Fix xfs_write_zeroes()”.)
Unfortunately, we also use xfsctl() to inquire the request alignment for
O_DIRECT, and this is the only way we currently hav
On 8/23/19 11:23 AM, Stefan Hajnoczi wrote:
> warn(3), warnx(3), err(3), and errx(3) print to stderr even when the --syslog
> option was given. In this case messages to stderr are likely to be lost and
> this makes troubleshooting hard. Use "fuse_log.h" APIs instead of .
>
> Stefan Hajnoczi (2):
23.08.2019. 01.15, "Shu-Chun Weng via Qemu-devel"
је написао/ла:
>
> Shu-Chun Weng (2):
> linux-user: add missing UDP and IPv6 setsockopt options
> linux-user: time stamping options for setsockopt()
>
> linux-user/generic/sockbits.h | 4
> linux-user/mips/sockbits.h| 4
> linu
warn(3), warnx(3), err(3), and errx(3) print to stderr even when the --syslog
option was given. In this case messages to stderr are likely to be lost and
this makes troubleshooting hard. Use "fuse_log.h" APIs instead of .
Stefan Hajnoczi (2):
virtiofsd: replace warn(3) and warnx(3) with fuse_w
On 22/8/2019 7:26 PM, Max Reitz wrote:
> Lukàš ran over a nasty regression in our xfs_write_zeroes() function
> (sorry, my fault) made apparent by a recent patch from Anton that makes
> qcow2 images heavily exercise the offending code path.
>
> This series fixes the bug and adds a test to prevent
Dne 22. 08. 19 v 19:09 Max Reitz napsal(a):
> On 22.08.19 18:53, Paolo Bonzini wrote:
>> On 22/08/19 18:26, Max Reitz wrote:
>>> Lukàš ran over a nasty regression in our xfs_write_zeroes() function
>>> (sorry, my fault) made apparent by a recent patch from Anton that makes
>>> qcow2 images heavily
Patchew URL: https://patchew.org/QEMU/20190822231443.172099-1-...@google.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH 0/2] Adding some setsockopt() options
Message-id: 20190822231443.172099-1
Shu-Chun Weng (2):
linux-user: add missing UDP and IPv6 setsockopt options
linux-user: time stamping options for setsockopt()
linux-user/generic/sockbits.h | 4
linux-user/mips/sockbits.h| 4
linux-user/syscall.c | 16 +---
3 files changed, 21 insertions(+
This is inspired by the discussion in
https://bugs.launchpad.net/qemu/+bug/1840922
Previously I suggested a new CPUClass hook, but when I went
to implement that seemed like overkill.
r~
Richard Henderson (2):
linux-user: Pass CPUState to MAX_RESERVED_VA
linux-user/arm: Adjust MAX_RESER
22.08.2019. 05.15, "Aleksandar Markovic" је
написао/ла:
>
>
> 21.08.2019. 23.00, "Eduardo Habkost" је написао/ла:
> >
> > On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> > > 02.08.2019. 17.37, "Aleksandar Markovic" <
aleksandar.marko...@rt-rk.com> је
> > > написао/ла:
> > >
On 22.08.19 18:53, Paolo Bonzini wrote:
> On 22/08/19 18:26, Max Reitz wrote:
>> Lukàš ran over a nasty regression in our xfs_write_zeroes() function
>> (sorry, my fault) made apparent by a recent patch from Anton that makes
>> qcow2 images heavily exercise the offending code path.
>>
>> This serie
On 22/08/19 18:26, Max Reitz wrote:
> Lukàš ran over a nasty regression in our xfs_write_zeroes() function
> (sorry, my fault) made apparent by a recent patch from Anton that makes
> qcow2 images heavily exercise the offending code path.
>
> This series fixes the bug and adds a test to prevent it
Lukàš ran over a nasty regression in our xfs_write_zeroes() function
(sorry, my fault) made apparent by a recent patch from Anton that makes
qcow2 images heavily exercise the offending code path.
This series fixes the bug and adds a test to prevent it from
reoccurring.
Max Reitz (2):
block/fil
Hi, this is a SLiRP bug, however as QEMU comsumes the library, it is
directly concerned, so I'm cross-posting both QEMU and SLiRP lists
for a stricter review.
The 2nd patch is a PoC, to give QEMU a chance to shutdown properly
if SLiRP internals get corrupted. Simply sent as RFC.
The vulnerability
Markus Armbruster (2):
contrib/gitdm: filetype interface is not in order, fix
contrib/gitdm: Add arm...@pond.sub.org to group-map-redhat
contrib/gitdm/filetypes.txt| 2 +-
contrib/gitdm/group-map-redhat | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.21.0
21.08.2019. 23.00, "Eduardo Habkost" је написао/ла:
>
> On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> > 02.08.2019. 17.37, "Aleksandar Markovic"
је
> > написао/ла:
> > >
> > > From: Aleksandar Markovic
> > >
> > > This little series improves linux_ssh_mips_malta.py, both
On Wed, Aug 21, 2019 at 10:27:11PM +0200, Aleksandar Markovic wrote:
> 02.08.2019. 17.37, "Aleksandar Markovic" је
> написао/ла:
> >
> > From: Aleksandar Markovic
> >
> > This little series improves linux_ssh_mips_malta.py, both in the sense
> > of code organization and in the sense of quantity o
02.08.2019. 17.37, "Aleksandar Markovic" је
написао/ла:
>
> From: Aleksandar Markovic
>
> This little series improves linux_ssh_mips_malta.py, both in the sense
> of code organization and in the sense of quantity of executed tests.
>
Hello, all.
I am going to send a new version in few days, and
I noticed recently that the exit semihosting call on nios2 was
ignoring its parameter and always returning status 0 instead. It
turns out the handler was retrieving the value of the wrong register.
Since the nios2 semihosting implementation was basically
cut-and-pasted from that for m68k, I checke
Patchew URL:
https://patchew.org/QEMU/20190821092020.17952-1-anthony.per...@citrix.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH 0/2] Fix for the xen-bus driver
Message-id: 20190821092020.17952
Cheers,
Anthony PERARD (2):
xen-bus: Fix backend state transition on device reset
xen-bus: Avoid rewriting identical values to xenstore
hw/xen/xen-bus.c | 41 +++--
1 file changed, 27 insertions(+), 14 deletions(-)
--
Anthony PERARD
On Mon, Aug 19, 2019 at 01:44:37PM +0100, Peter Maydell wrote:
> On Fri, 16 Aug 2019 at 13:58, Peter Maydell wrote:
> >
> > The translation table walk for an ATS instruction can result in
> > various faults. In general these are just reported back via the
> > PAR_EL1 fault status fields, but in s
On Mon, Aug 19, 2019 at 01:44:37PM +0100, Peter Maydell wrote:
> On Fri, 16 Aug 2019 at 13:58, Peter Maydell wrote:
> >
> > The translation table walk for an ATS instruction can result in
> > various faults. In general these are just reported back via the
> > PAR_EL1 fault status fields, but in s
On Fri, 16 Aug 2019 at 13:58, Peter Maydell wrote:
>
> The translation table walk for an ATS instruction can result in
> various faults. In general these are just reported back via the
> PAR_EL1 fault status fields, but in some cases the architecture
> requires that the fault is turned into an ex
On Sat, Aug 17, 2019 at 05:32:35PM +0800, Peter Xu wrote:
> I can easily crash QEMU as long as KVM is used with e1000 and reboot
> many times, then I hit this and QEMU aborts [1]:
>
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28)
Reproducer:
bin=x86_64-softmmu/qem
On Wed, Jul 31, 2019 at 10:42:23PM +0800, Wei Yang wrote:
>Two cleanup:
>
>Patch #1 make code consistent on calling add_to_iovec
>Patch #2 refine the code to handle the case when buf already flushed
>
Ping~
>Wei Yang (2):
> migration/qemu-file: remove check on writev_buffer in
>qemu_put_comp
The virtual address that is provided by the guest in post_send and
post_recv operations is related to the guest address space. This
address
space is unknown to the HCA resides on host so extra step in these
operations is needed to adjust the address to host virtual address.
This step, which is don
I can easily crash QEMU as long as KVM is used with e1000 and reboot
many times, then I hit this and QEMU aborts [1]:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28)
To reproduce this issue and also to avoid rebooting so many times,
simply dump the devcount from KVM
Patchew URL:
https://patchew.org/QEMU/20190816143321.20903-1-dgilb...@redhat.com/
Hi,
This series failed build test on s390x host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit that
Patchew URL:
https://patchew.org/QEMU/20190816125802.25877-1-peter.mayd...@linaro.org/
Hi,
This series failed build test on s390x host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit
From: "Dr. David Alan Gilbert"
Hi,
This pair of patches adds the core of the virtio-fs support to qemu;
it's marked experimental since the kernel patch and spec changes aren't
in yet; but they're bubbling along.
While the spec change is still in progress; the ID number is already
reserved.
Currently when QEMU is given a bios image with only a file name and
its file path passed in "-L", it still reports file not found.
This series fixes the issue. This is especially helpful for creating
distro QEMU packages.
Bin Meng (2):
riscv: Add a helper routine for finding firmware
riscv:
The translation table walk for an ATS instruction can result in
various faults. In general these are just reported back via the
PAR_EL1 fault status fields, but in some cases the architecture
requires that the fault is turned into an exception:
* synchronous stage 2 faults of any kind during AT S
Hi all!
Max's series to fix some problems around filters consists of 42 patches.
I'm sure that we didn't find all bugs around filters, and that filters
would be a constant source of bugs in future, as during developing new
feature nobody will consider all possible cases of dealing with filters
(OK
On 13.08.19 17:03, Kevin Wolf wrote:
> Am 13.08.2019 um 16:53 hat Max Reitz geschrieben:
>> On 13.08.19 16:46, Vladimir Sementsov-Ogievskiy wrote:
>>> 13.08.2019 17:31, Max Reitz wrote:
On 13.08.19 13:51, Kevin Wolf wrote:
[...]
> Hm... This is a mess. :-)
Just out
Am 13.08.2019 um 16:53 hat Max Reitz geschrieben:
> On 13.08.19 16:46, Vladimir Sementsov-Ogievskiy wrote:
> > 13.08.2019 17:31, Max Reitz wrote:
> >> On 13.08.19 13:51, Kevin Wolf wrote:
> >>
> >> [...]
> >>
> >>> Hm... This is a mess. :-)
> >>
> >> Just out of curiosity: Why?
> >>
> >> Aren’t the
On 13.08.19 16:46, Vladimir Sementsov-Ogievskiy wrote:
> 13.08.2019 17:31, Max Reitz wrote:
>> On 13.08.19 13:51, Kevin Wolf wrote:
>>
>> [...]
>>
>>> Hm... This is a mess. :-)
>>
>> Just out of curiosity: Why?
>>
>> Aren’t there only two things we really need from the block_status
>> infrastructur
On 8/13/19 9:31 AM, Max Reitz wrote:
> On 13.08.19 13:51, Kevin Wolf wrote:
>
> [...]
>
>> Hm... This is a mess. :-)
>
> Just out of curiosity: Why?
>
> Aren’t there only two things we really need from the block_status
> infrastructure?
>
> (1) Whether something is allocated in the given layer
13.08.2019 17:31, Max Reitz wrote:
> On 13.08.19 13:51, Kevin Wolf wrote:
>
> [...]
>
>> Hm... This is a mess. :-)
>
> Just out of curiosity: Why?
>
> Aren’t there only two things we really need from the block_status
> infrastructure?
>
> (1) Whether something is allocated in the given layer o
On 13.08.19 11:34, Kevin Wolf wrote:
> Am 12.08.2019 um 21:46 hat Max Reitz geschrieben:
>> On 12.08.19 20:11, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi all!
>>>
>>> I'm not sure, is it a bug or a feature, but using qcow2 under raw is
>>> broken. It should be either fixed like I propose (by Max's
On 13.08.19 13:51, Kevin Wolf wrote:
[...]
> Hm... This is a mess. :-)
Just out of curiosity: Why?
Aren’t there only two things we really need from the block_status
infrastructure?
(1) Whether something is allocated in the given layer of the backing chain,
(2) Whether we know that a given ran
13.08.2019 14:51, Kevin Wolf wrote:
> Am 13.08.2019 um 13:14 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> 13.08.2019 12:33, Vladimir Sementsov-Ogievskiy wrote:
>>> 13.08.2019 12:01, Vladimir Sementsov-Ogievskiy wrote:
13.08.2019 11:39, Vladimir Sementsov-Ogievskiy wrote:
> 12.08.2019 2
On 13/08/19 12:29, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> This fixes a symptom I've seen on vhost-user on aarch64 where the
> daemon would be falsely notified of memory region changes that didn't
> exist.
> The underlying problem was me memcmp'ing MemoryRegionSec
Am 13.08.2019 um 13:14 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 13.08.2019 12:33, Vladimir Sementsov-Ogievskiy wrote:
> > 13.08.2019 12:01, Vladimir Sementsov-Ogievskiy wrote:
> >> 13.08.2019 11:39, Vladimir Sementsov-Ogievskiy wrote:
> >>> 12.08.2019 22:50, Max Reitz wrote:
> On 12.08.
13.08.2019 12:33, Vladimir Sementsov-Ogievskiy wrote:
> 13.08.2019 12:01, Vladimir Sementsov-Ogievskiy wrote:
>> 13.08.2019 11:39, Vladimir Sementsov-Ogievskiy wrote:
>>> 12.08.2019 22:50, Max Reitz wrote:
On 12.08.19 21:46, Max Reitz wrote:
> On 12.08.19 20:11, Vladimir Sementsov-Ogievski
From: "Dr. David Alan Gilbert"
This fixes a symptom I've seen on vhost-user on aarch64 where the
daemon would be falsely notified of memory region changes that didn't
exist.
The underlying problem was me memcmp'ing MemoryRegionSections even
though they had padding in.
(Discovered while getting v
13.08.2019 12:01, Vladimir Sementsov-Ogievskiy wrote:
> 13.08.2019 11:39, Vladimir Sementsov-Ogievskiy wrote:
>> 12.08.2019 22:50, Max Reitz wrote:
>>> On 12.08.19 21:46, Max Reitz wrote:
On 12.08.19 20:11, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> I'm not sure, is it a bug
Am 12.08.2019 um 21:46 hat Max Reitz geschrieben:
> On 12.08.19 20:11, Vladimir Sementsov-Ogievskiy wrote:
> > Hi all!
> >
> > I'm not sure, is it a bug or a feature, but using qcow2 under raw is
> > broken. It should be either fixed like I propose (by Max's suggestion)
> > or somehow forbidden (j
13.08.2019 11:39, Vladimir Sementsov-Ogievskiy wrote:
> 12.08.2019 22:50, Max Reitz wrote:
>> On 12.08.19 21:46, Max Reitz wrote:
>>> On 12.08.19 20:11, Vladimir Sementsov-Ogievskiy wrote:
Hi all!
I'm not sure, is it a bug or a feature, but using qcow2 under raw is
broken. It sh
1 - 100 of 4151 matches
Mail list logo
