From: Paolo Bonzini
Make hw/vfio configurable and add new CONFIG_VFIO_* to the
default-configs/s390x*-softmmu.mak. This allow a finer-grain
selection of the various VFIO backends.
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/arm-softmmu.mak | 2 ++
Add the new configs to default-configs/riscv*-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Alistair Francis
Reviewed-by: Thomas Huth
---
default-configs/riscv32-softmmu.mak | 7 +++
default-configs/riscv64-softmmu.mak | 7 +++
CONFIG_MOXIE added for moxiesim board.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/moxie-softmmu.mak | 1 +
hw/moxie/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
CONFIG_NIOS2_10M50 added for 10m50 dev board.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/nios2-softmmu.mak | 1 +
hw/nios2/Makefile.objs| 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git
Add the new configs to default-configs/hppa-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Richard Henderson
---
default-configs/hppa-softmmu.mak | 1 +
hw/hppa/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Paolo Bonzini
Create separate variables for these components, they are
used in many boards but not all. This allows finer-grain
selection of the included code with default-configs/*.mak.
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/arm-softmmu.mak
From: Paolo Bonzini
Make hw/s390x configurable and add new CONFIG_* to the
default-configs/s390x*-softmmu.mak. This will be used to
enable/disable vfio-ccw.
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/s390x-softmmu.mak | 1 +
hw/s390x/Makefile.objs|
Add the new configs to default-configs/tricore-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/tricore-softmmu.mak | 1 +
hw/tricore/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
Add the new configs to default-configs/sparc64-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/sparc64-softmmu.mak | 2 ++
hw/sparc64/Makefile.objs| 6 +++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff
Add the new configs to default-configs/cris-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/cris-softmmu.mak | 1 +
hw/cris/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
Add the new configs to default-configs/or1k-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/or1k-softmmu.mak | 1 +
hw/openrisc/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Ákos Kovács
Make hw/sh4 configurable and add new CONFIG_* to the
default-configs/sh4*-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/sh4-softmmu.mak | 2 ++
default-configs/sh4eb-softmmu.mak | 2 ++
From: Ákos Kovács
CONFIG_LM32 and CONFIG_MILKYMIST added for lm32 and milkmyst build.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
hw/lm32/Makefile.objs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/lm32/Makefile.objs
From: Ákos Kovács
Add the new configs to default-configs/mips*-sofmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Signed-off-by: Yang Zhong
Reviewed-by: Thomas Huth
---
default-configs/mips-softmmu-common.mak | 3 +++
hw/mips/Makefile.objs | 5 +++--
2
Add the new configs to default-configs/alpha-sofmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
Reviewed-by: Richard Henderson
---
default-configs/alpha-softmmu.mak | 1 +
hw/alpha/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1
From: Ákos Kovács
CONFIG_PPC405, CONFIG_PPC440, CONFIG_MAC_OLDWORLD, CONFIG_MAX_NEWWORLD
and CONFIG_VIRTEX configuration options created for
default-configs/ppc*-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Signed-off-by: Yang Zhong
Reviewed-by: Thomas Huth
---
From: Ákos Kovács
CONFIG_AN5206, CONFIG_MCF5206 and CONFIG_MCF5208 make
variables created for m68k boards, and added to
default-configs/m86k-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/m68k-softmmu.mak | 2 ++
Make ARM virt code configurable and the new CONFIG_ARM_VIRT
definitions added to the default-configs/arm-softmmu.mak.
Signed-off-by: Yang Zhong
Signed-off-by: Paolo Bonzini
Reviewed-by: Richard Henderson
Reviewed-by: Thomas Huth
---
default-configs/arm-softmmu.mak | 1 +
hw/arm/Makefile.objs
From: Ákos Kovács
Add the new CONFIG_* values to default-config/xtensa*-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
Acked-by: Max Filippov
---
default-configs/xtensa-softmmu.mak | 3 +++
default-configs/xtensaeb-softmmu.mak | 3 +++
From: Ákos Kovács
CONFIG_PETALOGIX_* and CONFIG_XLNX_* configs added to
default-configs/microblaze-softmmu.mak and
default-configs/microblazeel-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/microblaze-softmmu.mak | 3 +++
From: Paolo Bonzini
CONFIG_PIIX and CONFIG_Q35 created for the pc board object files. These
are enabled automatically at default-configs/i386-softmmu.mak and
default-configs/x86_64-softmmu.mak
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
From: Paolo Bonzini
This is not needed on ARM, and brings in ISA bus code which is otherwise not
necessary.
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
hw/ide/Makefile.objs | 4 +--
hw/ide/core.c| 25 -
hw/ide/ioport.c | 66
From: Ákos Kovács
CONFIG_LEON3 added to default-configs/sparc-softmmu.mak.
Signed-off-by: Ákos Kovács
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/sparc-softmmu.mak | 2 ++
hw/sparc/Makefile.objs| 4 +++-
2 files changed, 5 insertions(+), 1
Change the CONFIGs for PCI EXPRESS and make module name more
clear for code files.
Signed-off-by: Yang Zhong
Cc: Michael S. Tsirkin
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
default-configs/arm-softmmu.mak | 4 ++--
default-configs/i386-softmmu.mak | 2 +-
From: Paolo Bonzini
Instead of wrapping the entire Makefile.objs with an ifeq/endif, just
include the directory only for Linux.
Signed-off-by: Paolo Bonzini
Reviewed-by: Thomas Huth
---
hw/Makefile.objs | 2 +-
hw/vfio/Makefile.objs | 2 --
2 files changed, 1 insertion(+), 3
From: Paolo Bonzini
Do not link it unconditionally into all binaries.
Signed-off-by: Paolo Bonzini
Signed-off-by: Yang Zhong
Reviewed-by: Thomas Huth
---
default-configs/i386-softmmu.mak | 1 +
hw/pci-host/Makefile.objs| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff
This patch set is part of Kconfig task, and our target is to make
all platform's code file configurable for Kconfig, which is suitable
for add "config XXX" for all platforms.
As for Kconfig patch set(RFC v5), please ref below thread:
From: Paolo Bonzini
ARM should not have an ISA bus, this device should not be enabled.
Kconfig allows to clean up the dependencies and remove CONFIG_ISA_BUS=y
from ARM, and then catches a contradiction between the hardcoded
CONFIG_SERIAL_ISA=y and CONFIG_ISA_BUS=n.
Signed-off-by: Paolo Bonzini
On Thu, Jan 31, 2019 at 09:48:54AM +0100, Thomas Huth wrote:
> On 2019-01-31 08:32, Yang Zhong wrote:
> > From: Paolo Bonzini
> >
> > Make hw/vfio configurable and add new CONFIG_VFIO_* to the
> > default-configs/s390x*-softmmu.mak. This allow a finer-grain
> > selection of the various VFIO
Patchew URL: https://patchew.org/QEMU/20190128021835.24451-1-jcmvb...@gmail.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
> 在 2019年2月1日，22:13，Markus Armbruster 写道：
>
> Fei Li writes:
>
>> From: Fei Li
>>
>> For qemu_signalfd_compat: set errno, do some cleanup, and return
>
> "For iothread_complete" is redundant, isn't it?
Yep, will remove it. Thanks for pointing this out. :)
>
>> -1 to replace the
> 在 2019年2月1日，22:03，Markus Armbruster 写道：
>
> Fei Li writes:
>
>> From: Fei Li
>>
>> For iothread_complete: utilize the existed errp to propagate the
>
> "For iothread_complete" is redundant, isn't it?
Emm, right. Will remove it in the next version.
>
>> error and do the corresponding
> 在 2019年2月1日，20:33，Markus Armbruster 写道：
>
> Fei Li writes:
>
>> From: Fei Li
>>
>> The callers of qemu_init_vcpu() already passed the **errp to handle
>> errors. In view of this, add a new Error parameter to qemu_init_vcpu()
>> and all qemu_X_start_vcpu() functions called by
> 在 2019年2月1日，20:58，Markus Armbruster 写道：
>
> Fei Li writes:
>
>> From: Fei Li
>>
>> Utilize the existed errp to propagate the error and do the
>> corresponding cleanup to replace the temporary _abort.
>>
>> Cc: Markus Armbruster
>> Cc: Jiri Slaby
>> Signed-off-by: Fei Li
>> ---
>>
Public bug reported:
The ioctl SIOCGIFNAME takes a pointer to a struct ifreq, not an integer.
This leads to if_indextoname() not correctly returning interface names
(well, not if they're longer than 4 characters including the trailing
NULL ;-).
This is observed on v3.1.0.
The following one-line
Just like the previous tests, boots a Linux kernel on a s390x target
using the s390-ccw-virtio machine.
Because it's not possible to have multiple VT220 consoles,
'-nodefaults' is used, so that the one set with set_console() works
correctly.
Reviewed-by: Caio Carrara
Signed-off-by: Cleber Rosa
Just like the previous tests, boots a Linux kernel on an arm target
using the virt machine.
Reviewed-by: Caio Carrara
Signed-off-by: Cleber Rosa
---
.travis.yml| 2 +-
tests/acceptance/boot_linux_console.py | 19 +++
2 files changed, 20
On 1/31/19 3:29 AM, Vladimir Sementsov-Ogievskiy wrote:
>
> About @frozen and @locked, we can also note that they can't be exported
> through NBD.
> We can summarize, that @frozen and @locked means that user can't use them in
> any
> command, and the only option is to list them. However even
Similar to the x86_64 + pc test, it boots a Linux kernel on a Malta
board and verify the serial is working.
If mips64el is a target being built, "make check-acceptance" will
automatically include this test by the use of the "arch:mips64el"
tags.
Alternatively, this test can be run using:
$
The current acceptance tests don't provide any type of architecture
information that can be used to influence the selection of the QEMU
binary used on them[1]. If one is running tests on a x86_64 host, the
default QEMU binary will be "x86_64-softmmu/qemu-system-x86_64".
Given the nature of QEMU,
The meaning of the states has changed subtly over time,
this should bring the understanding more in-line with the
current, actual usages.
Reported-by: Eric Blake
Signed-off-by: John Snow
---
V2: Amended some wordings, though this is a little chatty now.
Hopefully it's clearer, though.
---
Similar to the x86_64 + pc test, it boots a Linux kernel on a Malta
board and verify the serial is working. One extra command added to
the QEMU command line is '-vga std', because the kernel used is
known to crash without it.
If alpha is a target being built, "make check-acceptance" will
On 2/2/19 1:56 AM, Cleber Rosa wrote:
> The 'printk.time=0' option makes it easier to parse the console
> output. Let's set it as a default, and reusable, kernel command line
> options for this and future similar tests.
Thanks!
>
> Signed-off-by: Cleber Rosa
Reviewed-by: Philippe
Given that the test is specific to x86_64 and pc, and new tests are
going to be added to the same class, let's rename it accordingly.
Also, let's make the class documentation not architecture specific.
Reviewed-by: Caio Carrara
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Cleber Rosa
---
Currently, the only test that contains some target architecture
information is "boot_linux_console.py" which test contains a "x86_64"
tag. But that tag is not respected in the default execution, that is,
"make check-acceptance" doesn't do anything with it.
That said, even the target architecture
Just like the previous tests, boots a Linux kernel on a ppc64 target
using the pseries machine.
Reviewed-by: Caio Carrara
Signed-off-by: Cleber Rosa
---
.travis.yml| 2 +-
tests/acceptance/boot_linux_console.py | 19 +++
2 files changed, 20
The set_console() utility function traditionally adds a device either
based on the explicitly given device type, or based on the machine type,
a known good type of device.
But, for a number of machine types, it may be impossible or
inconvenient to add the devices my means of "-device" command
From: Philippe Mathieu-Daudé
Similar to the x86_64 + pc test, it boots a Linux kernel on a Malta
board and verify the serial is working. Also, it relies on the serial
device set by the machine itself.
If mips is a target being built, "make check-acceptance" will
automatically include this test
This introduces a utility method that monitors the console device and
looks for either a message that signals the test success or failure.
Reviewed-by: Caio Carrara
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Cleber Rosa
---
tests/acceptance/boot_linux_console.py | 30
Even when the launch of QEMU succeeds, it's useful to have the command
line recorded.
Reviewed-by: Caio Carrara
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Alex Bennée
Signed-off-by: Cleber Rosa
---
scripts/qemu.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/qemu.py
The 'printk.time=0' option makes it easier to parse the console
output. Let's set it as a default, and reusable, kernel command line
options for this and future similar tests.
Signed-off-by: Cleber Rosa
---
tests/acceptance/boot_linux_console.py | 4 +++-
1 file changed, 3 insertions(+), 1
To the stock Fedora 29 kernel, from the Fedora 28. New tests will be
added using the 29 kernel, so for consistency, let's also update it
here.
Reviewed-by: Caio Carrara
Signed-off-by: Cleber Rosa
---
tests/acceptance/boot_linux_console.py | 4 ++--
1 file changed, 2 insertions(+), 2
The "this directory" reference is misleading and confusing, it's a
leftover from when this text was proposed in a README file inside
the "tests/acceptance/avocado_qemu" directory.
When that text was moved to the top level docs directory, the
reference was not updated.
Reviewed-by: Caio Carrara
When running on very low powered environments, some tests may time out
causing false negatives. As a conservative change, and for
considering that human time (investigating false negatives) is worth
more than some extra machine cycles (and time), let's increase the
overall timeout.
CC: Alex
Just like the previous tests, boots a Linux kernel on a aarch64 target
using the virt machine.
One special option added is the CPU type, given that the kernel
selected fails to boot on the virt machine's default CPU (cortex-a15).
Reviewed-by: Caio Carrara
Signed-off-by: Cleber Rosa
---
It's useful to define the architecture that should be used in
situations such as:
* the intended target of the QEMU binary to be used on tests
* the architecture of code to be run within the QEMU binary, such
as a kernel image or a full blown guest OS image
This commit introduces both a test
The current version of the "check-acceptance" target will only show
one line for execution of all tests. That's probably OK if the tests
to be run are quick enough and they're always the same.
But, there's already one test alone that takes on average ~5 seconds
to run, we intend to adapt the
Making it clear what is returned by this utility function.
Reviewed-by: Caio Carrara
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Cleber Rosa
---
tests/acceptance/avocado_qemu/__init__.py | 4
1 file changed, 4 insertions(+)
diff --git a/tests/acceptance/avocado_qemu/__init__.py
A test can, optionally, be tagged for one or many architectures. If a
test has been tagged for a single architecture, there's a high chance
that the test won't run on other architectures. This changes the
default order of choosing a default target architecture to use based
on the 'arch' tag
Hi Gerd,
On Tue, Nov 06, 2018 at 12:28:29 +0100, Gerd Hoffmann wrote:
> seabios 1.12 release is planned for november.
>
> update seabios to a master branch snapshot so it gets more testing
> and to make the delta smaller when updating to -final during freeze.
I just bisected a performance
On 2/1/19 1:53 PM, Cleber Rosa wrote:
> Getting straight to the point, this is the ppc64 "boot linux console"
> test, running 10 times, on top my latest rebase (e8977901b, that
> includes f7b78602f).
>
> (01/10) boot_linux_console.py:BootLinuxConsole.test_ppc64_pseries: PASS
> (63.07 s)
...
>
Patchew URL:
https://patchew.org/QEMU/20190123225705.28963-1-richard.hender...@linaro.org/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT
On 02/01/19 23:24, Michael S. Tsirkin wrote:
> On Thu, Jan 31, 2019 at 03:23:50PM +0100, Laszlo Ersek wrote:
>> On 01/24/19 21:39, Laszlo Ersek wrote:
>>> Previous version (v1):
>>> http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
>>>
>>> Updates in v2 have been noted on each
On 02/02/19 00:03, Philippe Mathieu-Daudé wrote:
> On 2/1/19 11:35 PM, Laszlo Ersek wrote:
>> On 01/31/19 19:55, Laszlo Ersek wrote:
>>> (1) How *exactly* does it fail for you?
>
> In my mailbox the mail appears with Message-ID:
> cf693646-58c8-8810-58a1-a6e503636...@redhat.com in response to
>
Hi Jonathan,
On 2/1/19 11:06 PM, Jonathan Behrens wrote:
> Public bug reported:
>
> I attempted to run qemu with a ram disk. However, when reading the
> contents of the disk from within the VM I only get back zeros.
>
> I was able to trace the issue to a mismatch of expectations on line 93
> of
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1814343
Title:
Initrd not loaded on riscv32
Status in QEMU:
Confirmed
Bug description:
I
On 2/2/19 12:00 AM, Michael S. Tsirkin wrote:
> Comment near strncpy explains kernel_cmdline does
> not need to be 0-terminated.
>
> Accordingly mark it as QEMU_NONSTRING.
>
> Without this, gcc warns:
> 'strncpy' specified bound 256 equals destination size
>
> Signed-off-by: Michael S.
On 2/1/19 11:35 PM, Laszlo Ersek wrote:
> On 01/31/19 19:55, Laszlo Ersek wrote:
>> On 01/31/19 18:07, Philippe Mathieu-Daudé wrote:
>>> On 1/24/19 9:39 PM, Laszlo Ersek wrote:
>
+# "build.sh" invokes the "build" utility of edk2 BaseTools. In any given
edk2
+# workspace, at most
Comment near strncpy explains kernel_cmdline does
not need to be 0-terminated.
Accordingly mark it as QEMU_NONSTRING.
Without this, gcc warns:
'strncpy' specified bound 256 equals destination size
Signed-off-by: Michael S. Tsirkin
---
hw/sh4/r2d.c | 2 +-
1 file changed, 1 insertion(+), 1
On 1/31/19 3:29 AM, Vladimir Sementsov-Ogievskiy wrote:
> 31.01.2019 4:01, John Snow wrote:
>> The meaning of the states has changed subtly over time,
>> this should bring the understanding more in-line with the
>> current, actual usages.
>>
>> Reported-by: Eric Blake
>> Signed-off-by: John
Thank you for testing this, the last update greatly improved the
situation. libspice-server1 updated, so I rebuilt QEMU. The
libspice-server1 0.14.0-1ubuntu2.4 change log is:
* SECURITY UPDATE: off-by-one error in memslot_get_virt
- debian/patches/CVE-2019-3813.patch: fix checks in
On 01/31/19 19:55, Laszlo Ersek wrote:
> On 01/31/19 18:07, Philippe Mathieu-Daudé wrote:
>> On 1/24/19 9:39 PM, Laszlo Ersek wrote:
>>> +# "build.sh" invokes the "build" utility of edk2 BaseTools. In any given
>>> edk2
>>> +# workspace, at most one "build" instance may be operating at a time.
On Thu, Jan 31, 2019 at 03:23:50PM +0100, Laszlo Ersek wrote:
> On 01/24/19 21:39, Laszlo Ersek wrote:
> > Previous version (v1):
> > http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
> >
> > Updates in v2 have been noted on each patch in the series.
>
> ping
Oh sorry I
On Mon, Jan 28, 2019 at 03:48:57PM -0200, Eduardo Habkost wrote:
> On Fri, Jan 18, 2019 at 01:38:26PM +, Daniel P. Berrangé wrote:
> > A number of virtio devices (gpu, crypto, mouse, keyboard, tablet) only
> > support the virtio-1 (aka modern) mode. Currently if the user launches
> > QEMU,
Public bug reported:
I attempted to run qemu with a ram disk. However, when reading the
contents of the disk from within the VM I only get back zeros.
I was able to trace the issue to a mismatch of expectations on line 93
of hw/riscv/virt.c. Specifically, when running in 32-bit mode the value
of
On Wed, Jan 16, 2019 at 01:31:06PM -0500, w...@redhat.com wrote:
> From: Wei Xu
>
> >From 1.1 spec.
>
> Signed-off-by: Wei Xu
So pls don't open-code this in qemu. These headers should come
from Linux using scripts/update-linux-headers.sh.
> ---
>
While working on the "boot_linux_console.py" tests, after a given
rebase, I noticed that the ppc64 specific test began timing out. The
original timeout set to the test was 60 seconds, and it "always" had
room to spare when running either on my system, or on Travis CI.
Then, Alex mentioned that
On 01/02/19 15:56, Philippe Mathieu-Daudé wrote:
> Now when I disable Xen, exec.o isn't rebuilt, so I get link errors:
>
> /usr/bin/ld: exec.o: in function `reclaim_ramblock':
> qemu/exec.c:2392: undefined reference to `xen_invalidate_map_cache_entry'
> /usr/bin/ld: exec.o: in function
On 2/1/19 7:01 AM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
>
> Here is most of preparatory refactoring for NBD reconnect, rebased
> on master. Let's push it.
Thanks; queued for my next NBD pull request.
>
> Sorry for a long delay in answering on v4 review and for v4 which
> I pinged a
On 2/1/19 7:01 AM, Vladimir Sementsov-Ogievskiy wrote:
> Keep all connection code in one file, to be able to implement reconnect
> in further patches.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
>
> +static QIOChannelSocket *nbd_establish_connection(SocketAddress *saddr,
> +
On 2/1/19 7:01 AM, Vladimir Sementsov-Ogievskiy wrote:
> This coroutine will serve nbd reconnects, so, rename it to be something
> more generic.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> Reviewed-by: Eric Blake
> ---
> block/nbd-client.h | 4 ++--
> block/nbd-client.c | 24
On 01/02/19 16:05, Philippe Mathieu-Daudé wrote:
> This lacks a DISPLAY dependency?
>
> $ i386-softmmu/qemu-system-i386 -M q35
> qemu-system-i386: Unknown device 'VGA' for bus 'PCIE'
> Aborted (core dumped)
If you build --without-default-devices, you pretty much have to do one
of two things: 1)
Hi Cédric,
On 1/21/19 5:00 PM, Cédric Le Goater wrote:
> JEDEC STANDARD JESD216 for Serial Flash Discovery Parameters (SFDP)
> provides a mean to describe the features of a serial flash device
> using a set of internal parameter tables.
>
> This is the initial framework for the RDSFPD command
* Leonardo Soares Müller (leozinho29...@hotmail.com) wrote:
> I can confirm this, KDE Neon using the command line similar to yours
> crashes QEMU to me too. I will test with Mageia 7 later to see if it
> behaves differently.
>
> But this is a completely different crash. This crash is happening
>
On 1/31/19 3:55 AM, Kevin Wolf wrote:
> Am 31.01.2019 um 03:03 hat John Snow geschrieben:
>> On 1/30/19 12:27 PM, Kevin Wolf wrote:
>>> Am 14.01.2019 um 17:25 hat Eric Blake geschrieben:
From: John Snow
New interface, new smoke test.
Signed-off-by: John Snow
On Fri, Feb 01, 2019 at 13:32:34 -0600, Eric Blake wrote:
> Commit 2cade3d wired up new tests, but did not exclude the
> new *.out files produced by running the tests.
>
> Signed-off-by: Eric Blake
Reviewed-by: Emilio G. Cota
E.
Patchew URL:
https://patchew.org/QEMU/1548509635-15776-1-git-send-email-ptsne...@gmail.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST
On 1/28/19 3:06 AM, Alex Bennée wrote:
> We build all tests with:
>
> CFLAGS+=-Wall -O0 -g -fno-strict-aliasing
>
> mainly because the first thing you want to do when they fail is run them
> through gdb to see what went wrong. Do you actually need optimisation on
> for the build to work?
Most of the v1 patch set has been merged.
Changes since v1:
* I've added the missing check against arg3 through arg5.
* I've removed the -O1 I had cribed from the MTE patch set.
r~
Richard Henderson (2):
linux-user: Implement PR_PAC_RESET_KEYS
tests/tcg/aarch64: Add pauth smoke test
On 2/1/19 1:29 PM, Max Reitz wrote:
> Before this patch, bdrv_refresh_filename() is used in a pushing manner:
> Whenever the BDS graph is modified, the parents of the modified edges
> are supposed to be updated (recursively upwards). However, that is
> nonviable, considering that we want child
On 2/1/19 1:29 PM, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/iotests.py | 10 ++
> 1 file changed, 10 insertions(+)
Reviewed-by: Eric Blake
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org |
Commit 2cade3d wired up new tests, but did not exclude the
new *.out files produced by running the tests.
Signed-off-by: Eric Blake
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore
index 72c18aaab04..f2bf85c8c4c 100644
---
Both of the defaults we currently have in the curl driver are named
based on a slightly different schema, let's unify that and call both
CURL_BLOCK_OPT_${NAME}_DEFAULT.
While at it, we can add a macro for the third option for which a default
exists, namely "sslverify".
Signed-off-by: Max Reitz
Instead of having every block driver which implements
bdrv_refresh_filename() copy all of the strong runtime options over to
bs->full_open_options, implement this process generically in
bdrv_refresh_filename().
This patch only adds this new generic implementation, it does not remove
the old
Signed-off-by: Max Reitz
Reviewed-by: Alberto Garcia
---
block/curl.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/block/curl.c b/block/curl.c
index 2c07a694d8..606709fea4 100644
--- a/block/curl.c
+++ b/block/curl.c
@@ -950,6 +950,23 @@ static int64_t
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
v2: Pass all 5 arguments to prctl; remove -O1.
---
tests/tcg/aarch64/pauth-1.c | 23 +++
tests/tcg/aarch64/Makefile.target | 6 +-
2 files changed, 28 insertions(+), 1 deletion(-)
create mode 100644
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
v2: Check arg3-5 are zero.
---
linux-user/aarch64/target_syscall.h | 7 ++
linux-user/syscall.c| 36 +
2 files changed, 43 insertions(+)
diff --git
The generic bdrv_dirname() implementation would be able to generate some
form of directory name for many NBD nodes, but it would be always wrong.
Therefore, we have to explicitly make it an error (until NBD has some
form of specification for export paths, if it ever will).
Signed-off-by: Max
Currently, BlockDriver.bdrv_refresh_filename() is supposed to both
refresh the filename (BDS.exact_filename) and set BDS.full_open_options.
Now that we have generic code in the central bdrv_refresh_filename() for
creating BDS.full_open_options, we can drop the latter part from all
blkverify's BDSs have a file BDS, but we do not want this to be
preferred over the raw node. There is no way to decide between the two
(and not really a reason to, either), so just return NULL in blkverify's
implementation of bdrv_dirname().
Signed-off-by: Max Reitz
Reviewed-by: Eric Blake
1 - 100 of 378 matches
Mail list logo
