flight 159812 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159812/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
It's now safe to enable the build of rombios on Alpine systems, as
hvmloader already builds fine there.
Signed-off-by: Roger Pau Monné
---
automation/scripts/build | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/automation/scripts/build b/automation/scripts/build
index d
Hello,
While the series started as a build fix for Alpine I think they are
interesting on their own for other OSes/distros.
The main risk for patch 1 is breaking the build in some obscure
distro/OS and toolchain combination. We aim to have this mostly covered
by gitlab CI. Patch 2 main risk is br
The current build of the firmware relies on having 32bit compatible
headers installed in order to build some of the 32bit firmware.
Usually this can be solved by using the -ffreestanding compiler option
which drops the usage of the system headers in favor of a private set
of freestanding headers pr
This requires adding some logic in the build script in order to be
able to pass specific Xen Kconfig options.
Setting any CONFIG_* environment variable when executing the build
script will set such variable in the empty .config file before
running the olddefconfig target. The .config file is also
flight 159808 xen-unstable real [real]
flight 159813 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/159808/
http://logs.test-lab.xenproject.org/osstest/logs/159813/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
On Fri, Feb 26, 2021 at 01:47:38PM +0900, Akihiko Odaki wrote:
> 2021年2月25日(木) 20:46 Gerd Hoffmann :
> >
> > Hi,
> >
> > > > Because of the wasted frames I'd like this to be an option you can
> > > > enable when needed. For the majority of use cases this seems to be
> > > > no problem ...
> > >
We get 1 warning when building kernel with W=1:
arch/x86/xen/efi.c:130:13: warning:
no previous prototype for ‘xen_efi_init’ [-Wmissing-prototypes]
void __init xen_efi_init(struct boot_params *boot_params)
In fact, this function is declared as a static inline function
in header file, but is not
On 03.03.21 10:36, maqiang wrote:
We get 1 warning when building kernel with W=1:
arch/x86/xen/efi.c:130:13: warning:
no previous prototype for ‘xen_efi_init’ [-Wmissing-prototypes]
void __init xen_efi_init(struct boot_params *boot_params)
In fact, this function is declared as a static inlin
Nick Rosbrook writes ("[RFC v2 0/7] add function support to IDL"):
> At a Xen Summit design session for the golang bindings (see [1]), we
> agreed that it would be beneficial to expand the libxl IDL with function
> support. In addition to benefiting libxl itself, this would allow other
> language b
Roger Pau Monne writes ("[PATCH v2 for-4.15 2/2] automation: enable rombios
build on Alpine"):
> It's now safe to enable the build of rombios on Alpine systems, as
> hvmloader already builds fine there.
Release-Acked-by: Ian Jackson
flight 159815 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159815/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 4834936549f788378918da8e9bc97df7dd3ee16d
baseline version:
xen c444
A simply qtest that checks for correct number of netdevs in the response
of the query-netdev.
Signed-off-by: Alexey Kirillov
Acked-by: Thomas Huth
---
tests/qtest/meson.build | 3 +
tests/qtest/test-query-netdev.c | 120
2 files changed, 123 insertions
This patch series introduces a new QMP command "query-netdev" to get
information about currently attached backend network devices (netdevs).
Also, since the "info_str" field of "NetClientState" is now deprecated,
we no longer use it for netdevs, only for NIC/hubports.
The HMP command "info networ
Replace usage of legacy field info_str of NetClientState for backend
network devices with QAPI NetdevInfo stored_config that already used
in QMP query-netdev.
This change increases the detail of the "info network" output and takes
a more general approach to composing the output.
NIC and hubports
The query-netdev command is used to get the configuration of the current
network device backends (netdevs).
This is the QMP analog of the HMP command "info network" but only for
netdevs (i.e. excluding NIC and hubports).
The query-netdev command returns an array of objects of the NetdevInfo
type,
The info_str field of the NetClientState structure is static and has a size
of 256 bytes. This amount is often unclaimed, and the field itself is used
exclusively for HMP "info network".
The patch translates info_str to dynamic memory allocation.
This action is also allows us to painlessly discar
As we use QAPI NetClientState->stored_config to store and get information
about backend network devices, we can drop fill of legacy field info_str
for them.
We still use info_str field for NIC and hubports, so we can not completely
remove it.
Signed-off-by: Alexey Kirillov
---
net/l2tpv3.c
On 03/03/2021 08:33, Roger Pau Monne wrote:
> This requires adding some logic in the build script in order to be
> able to pass specific Xen Kconfig options.
>
> Setting any CONFIG_* environment variable when executing the build
> script will set such variable in the empty .config file before
> run
On Wed, Mar 03, 2021 at 11:46:44AM +, Andrew Cooper wrote:
> On 03/03/2021 08:33, Roger Pau Monne wrote:
> > This requires adding some logic in the build script in order to be
> > able to pass specific Xen Kconfig options.
> >
> > Setting any CONFIG_* environment variable when executing the bui
On 03/03/2021 11:57, Roger Pau Monné wrote:
> On Wed, Mar 03, 2021 at 11:46:44AM +, Andrew Cooper wrote:
>> On 03/03/2021 08:33, Roger Pau Monne wrote:
>>> This requires adding some logic in the build script in order to be
>>> able to pass specific Xen Kconfig options.
>>>
>>> Setting any CONFI
flight 159810 qemu-mainline real [real]
flight 159816 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/159810/
http://logs.test-lab.xenproject.org/osstest/logs/159816/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
On Wed, Mar 03, 2021 at 09:48:02AM +, Ian Jackson wrote:
> Nick Rosbrook writes ("[RFC v2 0/7] add function support to IDL"):
> > At a Xen Summit design session for the golang bindings (see [1]), we
> > agreed that it would be beneficial to expand the libxl IDL with function
> > support. In add
For things like randconfig there's no need to do a full Xen build, a
hypervisor build only will be much faster and will achieve the same
level of testing, as randconfig only changes the hypervisor build
options.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
I think it might be good to get t
Roger Pau Monne writes ("[PATCH for-4.15] automation: allow doing hypervisor
only builds"):
> For things like randconfig there's no need to do a full Xen build, a
> hypervisor build only will be much faster and will achieve the same
> level of testing, as randconfig only changes the hypervisor bui
flight 159811 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159811/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
Signed-off-by: Akihiko Odaki
---
hw/display/edid-generate.c | 9 +
include/hw/display/edid.h | 12 +++-
2 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/hw/display/edid-generate.c b/hw/display/edid-generate.c
index 1665b7cbb29..b0ce583d436 100644
--- a/hw/display/
This change adds a new member, refresh_rate to QemuUIInfo in
include/ui/console.h. It represents the refresh rate of the
physical display backend, and it is more appropriate than
GUI update interval as the refresh rate which the emulated device
reports:
- sdl may set GUI update interval shorter tha
On Tue, Mar 02, 2021 at 04:18:59PM +0100, Jan Beulich wrote:
> On 02.03.2021 16:00, Roger Pau Monné wrote:
> > On Tue, Mar 02, 2021 at 12:16:12PM +0100, Jan Beulich wrote:
> >> On 01.03.2021 17:23, Roger Pau Monne wrote:
> >>> RFC because there's still some debate as to how we should solve the
> >>
Norbert Manthey writes ("[PATCH XENSTORE v1 01/10] xenstore: add missing NULL
check"):
> In case of allocation error, we should not dereference the obtained
> NULL pointer. Hence, fail early.
>
> This bug was discovered and resolved using Coverity Static Analysis
> Security Testing (SAST) by Syno
Norbert Manthey writes ("[PATCH XENSTORE v1 02/10] xenstore: fix print format
string"):
> Use the correct format specifier for unsigned values. Additionally, a
> cast was dropped, as the format specifier did not require it anymore.
>
> This was reported by analysis with cppcheck.
>
> Signed-off-
Norbert Manthey writes ("[PATCH XENSTORE v1 03/10] xenstore: check formats of
trace"):
> When passing format strings to the trace function, allow gcc to analyze
> those and warn on issues.
>
> Signed-off-by: Norbert Manthey
> Reviewed-by: Thomas Friebel
> Reviewed-by: Julien Grall
Release-Ack
Norbert Manthey writes ("[PATCH XENSTORE v1 04/10] xenstore_client: handle
memory on error"):
> In case a command fails, also free the memory. As this is for the CLI
> client, currently the leaked memory is freed right after receiving the
> error, as the application terminates next.
>
> Similarly
Norbert Manthey writes ("[PATCH XENSTORE v1 05/10] xenstore: handle daemon
creation errors"):
> In rare cases, the path to the daemon socket cannot be created as it is
> longer than PATH_MAX. Instead of failing with a NULL pointer dereference,
> terminate the application with an error message.
>
Norbert Manthey writes ("[PATCH XENSTORE v1 07/10] xenstore: handle do_mkdir
and do_rm failure"):
> In the out of memory case, we might return a NULL pointer when
> canonicalizing node names. This NULL pointer is not checked when
> creating a directory, or when removing a node. This change handles
Norbert Manthey writes ("[PATCH XENSTORE v1 08/10] xenstore: add missing NULL
check"):
> From: Michael Kurth
>
> In case of allocation error, we should not dereference the obtained
> NULL pointer.
>
> This bug was discovered and resolved using Coverity Static Analysis
> Security Testing (SAST)
Norbert Manthey writes ("[PATCH XENSTORE v1 09/10] xs: handle daemon socket
error"):
> When starting the daemon, we might see a NULL pointer instead of the
> path to the socket.
>
> Only relevant in case we start the process in a very deep directory
> path, with a length close to 4096 so that app
Norbert Manthey writes ("[PATCH XENSTORE v1 10/10] xs: add error handling"):
> In case of a failure deep in the call tree, we might return NULL as the
> value of the domain. In that case, error out instead of dereferencing
> the NULL pointer.
>
> This bug was discovered and resolved using Coverity
From: Julien Grall
As XenStored is single-threaded, conn->ta_start_time will always be
smaller than now. As we substract the latter from the former, it means
a transaction will never be considered long running.
Invert the two operands of the substraction in both lu_reject_reason()
and lu_check_a
This is a mechanical change to make the fdt available through
MachineState.
Signed-off-by: Alex Bennée
Reviewed-by: Alistair Francis
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20210211171945.18313-3-alex.ben...@linaro.org>
---
include/hw/riscv/virt.h | 1 -
hw/riscv/virt.c | 20
Hi,
Trying to get my ducks in a row for a merge of this before softfreeze
so this is my pre-PR posting of the Xen guest-loader support.
Everything apart from the loader itself is reviewed and given it's
been tested in other patches and I'm going to maintain it I don't see
a reason to hold it up fr
The use of FDT's is quite common across our various platforms. To
allow the guest loader to tweak it we need to make it available in
the generic state. This creates the field and migrates the initial
user to use the generic field. Other boards will be updated in later
patches.
Signed-off-by: Alex
Hypervisors, especially type-1 ones, need the firmware/bootcode to put
their initial guest somewhere in memory and pass the information to it
via platform data. The guest-loader is modelled after the generic
loader for exactly this sort of purpose:
$QEMU $ARGS -kernel ~/xen.git/xen/xen \
-a
A string array in device tree is simply a series of \0 terminated
strings next to each other. As libfdt doesn't support that directly
we need to build it ourselves.
Signed-off-by: Alex Bennée
Reviewed-by: Alistair Francis
Message-Id: <20201105175153.30489-4-alex.ben...@linaro.org>
Message-Id: <2
We might as well surface this useful information in the manual so
users can find it easily. It is a fairly simple conversion to rst with
the only textual fixes being QemuOps to QemuOpts.
Signed-off-by: Alex Bennée
Reviewed-by: Alistair Francis
Message-Id: <20201105175153.30489-6-alex.ben...@lina
Signed-off-by: Alex Bennée
Reviewed-by: Alistair Francis
Message-Id: <20201105175153.30489-7-alex.ben...@linaro.org>
Message-Id: <20210211171945.18313-7-alex.ben...@linaro.org>
---
docs/system/guest-loader.rst | 54
docs/system/index.rst| 1 +
MAINTA
These tests make sure we can boot the Xen hypervisor with a Dom0
kernel using the guest-loader. We currently have to use a kernel I
built myself because there are issues using the Debian kernel images.
Signed-off-by: Alex Bennée
Tested-by: Cleber Rosa
Reviewed-by: Philippe Mathieu-Daudé
Reviewe
Julien Grall writes ("[PATCH for-4.15] tools/xenstored: liveupdate: Properly
check long transaction"):
> From: Julien Grall
>
> As XenStored is single-threaded, conn->ta_start_time will always be
> smaller than now. As we substract the latter from the former, it means
> a transaction will never
Hi Ian,
On 03/03/2021 17:41, Ian Jackson wrote:
Julien Grall writes ("[PATCH for-4.15] tools/xenstored: liveupdate: Properly check
long transaction"):
From: Julien Grall
As XenStored is single-threaded, conn->ta_start_time will always be
smaller than now. As we substract the latter from the
Julien Grall writes ("Re: [PATCH for-4.15] tools/xenstored: liveupdate:
Properly check long transaction"):
> On 03/03/2021 17:41, Ian Jackson wrote:
> > AFAICT this only affects live updated which is not security-supported
> > in 4.15 and which won't block our tests.
>
> That's correct.
>
> > S
Hi Stefano,
On 23/02/2021 01:22, Stefano Stabellini wrote:
Thanks! I am thinking to create a branch next again for queuing 4.15+ patches.
Would that be fine with you?
yes good idea
I have created the branch for-next/4.16 on my public tree and push the
patch:
https://xenbits.xen.org/gitweb
On 3/3/21 6:36 PM, Alex Bennée wrote:
> Hypervisors, especially type-1 ones, need the firmware/bootcode to put
> their initial guest somewhere in memory and pass the information to it
> via platform data. The guest-loader is modelled after the generic
> loader for exactly this sort of purpose:
>
>
On 3/3/21 7:37 PM, Philippe Mathieu-Daudé wrote:
> On 3/3/21 6:36 PM, Alex Bennée wrote:
>> Hypervisors, especially type-1 ones, need the firmware/bootcode to put
>> their initial guest somewhere in memory and pass the information to it
>> via platform data. The guest-loader is modelled after the g
Hi Norbert,
Thank you for the patches. Please find below a state for each patches.
On 26/02/2021 14:41, Norbert Manthey wrote:
For the following patches:
xenstore: add missing NULL check
xenstore: fix print format string
>xenstore: check formats of trace
>xenstore: handle do_mk
Hi Jan,
On 01/03/2021 07:57, Jan Beulich wrote:
The upcoming release complains, not entirely unreasonably:
In file included from rijndael.c:33:
.../xen/include/crypto/rijndael.h:55:53: note: previously declared as 'const
unsigned char[]'
55 | voidrijndaelEncrypt(const unsigned int [],
(BCCing xen-users, CCing xen-devel + a few folks)
Hi,
Moving the discussion to xen-devel.
On 22/02/2021 05:02, Charles Chiou wrote:
When trying to boot two zImage using dom0less boot on ARM, we encountered this
problem when xen runs gunzip on second guest:
(XEN) *
flight 159814 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159814/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm 20 guest-start/debianhvm.repeat
fail in 159808 pass in 159814
tes
flight 159819 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159819/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
flight 159817 qemu-mainline real [real]
flight 159821 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/159817/
http://logs.test-lab.xenproject.org/osstest/logs/159821/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
flight 159818 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159818/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
> From: Jan Beulich
> Sent: Monday, March 1, 2021 5:59 PM
>
> On 01.03.2021 09:30, Tian, Kevin wrote:
> >> From: Jan Beulich
> >> Sent: Monday, March 1, 2021 4:16 PM
> >>
> >> On 01.03.2021 03:18, Tian, Kevin wrote:
> From: Roger Pau Monné
> Sent: Thursday, February 11, 2021 8:27 PM
>
flight 159824 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159824/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
62 matches
Mail list logo
