flight 173220 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173220/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 172133
build-i386-libvirt
Hi Jan and Stewart,
> -Original Message-
> From: Jan Beulich
> Subject: Re: [PATCH] MAINTAINERS: change my email
>
> On 15.09.2022 21:30, Stewart Hildebrand wrote:
> > I am departing DornerWorks. I will still be working with Xen in my next
> > role, and I still have an interest in mainta
I have QubesOS 4.1.1 with Xen 4.14.5 hypervisor system on which I want to
install OpenBSD as a HVM and pass through my NICs to it (Intel Wireless
AC-9560 and Realtek 8168 rev 0x15: RTL8168H/8111H). I tested that when
installing OpenBSD on actual hardware both NICs seems to working properly.
But on
On 15.09.2022 22:04, Neil Sikka wrote:
> Update: I rebuilt the hypervisor binary in debug mode and get the following
> output in xl dmesg after the crash.
>
> (XEN) HVM9 restore: CPU 0
> (XEN) HVM9 restore: PIC 0
> (XEN) HVM9 restore: PIC 1
> (XEN) HVM9 restore: IOAPIC 0
> (XEN) HVM9 restore: LAPI
On 15.09.2022 21:30, Stewart Hildebrand wrote:
> I am departing DornerWorks. I will still be working with Xen in my next
> role, and I still have an interest in maintaining the ARINC 653
> scheduler, so change to my personal email address. Also change status to
> Maintained.
>
> Signed-off-by: Ste
On 15.09.2022 18:48, Tamas K Lengyel wrote:
> On Thu, Sep 15, 2022 at 10:39 AM Jan Beulich wrote:
>>
>> On 15.09.2022 16:16, Tamas K Lengyel wrote:
>>> On Thu, Sep 15, 2022 at 10:10 AM Jan Beulich wrote:
On 15.09.2022 16:05, Tamas K Lengyel wrote:
> On Thu, Sep 15, 2022 at 3:56 AM J
flight 173219 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173219/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
build-i386-libvir
flight 173222 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173222/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
Hi Jan,
> -Original Message-
> Subject: [PATCH for-4.17?] x86: support data operand independent timing
> mode
>
> [1] specifies a long list of instructions which are intended to exhibit
> timing behavior independent of the data they operate on. On certain
> hardware this independence is o
flight 173213 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173213/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172128
build-amd64-libvirt
Roger Pau Monné writes ("Re: [PATCH] libvirt: disable Werror for non-libvirt
flights"):
> I don't mind using -Dwerror=false if that's considered better. Ian, do
> you have an opinion?
No, I don't think I do. I think it depends on what kinds of things
are likely to change, or go wrong, in libvirt
On Thu, 15 Sep 2022, Juergen Gross wrote:
> On 15.09.22 03:18, Stefano Stabellini wrote:
> > On Wed, 14 Sep 2022, Jan Beulich wrote:
> > > On 14.09.2022 01:31, Stefano Stabellini wrote:
> > > > The problem is that drivers/xen/privcmd.c:privcmd_mmap sets VM_IO |
> > > > VM_PFNMAP, and either flag wo
Anthony PERARD writes ("Re: Sorting out osstest"):
> Yes, that plan sound good to me. Just one thing, `git checkout master`
> in testing.git as at the moment "pretest" is the current branch.
Yes.
Here's an overview of what's (supposed) to exist and happen.
There are:
osstest:~osstest/testing
On Thu, 15 Sep 2022, Jan Beulich wrote:
> On 15.09.2022 12:20, Juergen Gross wrote:
> > On 15.09.22 11:32, Jan Beulich wrote:
> >> On 15.09.2022 10:39, Juergen Gross wrote:
> >>> The IOCTL_PRIVCMD_MMAP isn't in use by Xen since at least Xen 4.0.
> >>>
> >>> Remove it from the privcmd driver.
> >>>
flight 173221 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173221/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 173210 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173210/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 172133
build-i386-libvirt
flight 173218 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173218/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
This patch makes the TPM version, for which the ACPI libary probes,
configurable.
If acpi_config.tpm_verison is set to 1, it indicates that 1.2 (TCPA) should be
probed.
I have also added to hvmloader an option to allow setting this new config,
which can
be triggered by setting the platform/tpm_v
This patch introduces an optional TPM 2 interface definition to the ACPI table,
which is to be used as part of a vTPM 2 implementation.
Signed-off-by: Jennifer Herbert
---
tools/firmware/hvmloader/config.h | 1 +
tools/firmware/hvmloader/util.c | 7 ++
tools/libacpi/Makefile|
Update: I rebuilt the hypervisor binary in debug mode and get the following
output in xl dmesg after the crash.
(XEN) HVM9 restore: CPU 0
(XEN) HVM9 restore: PIC 0
(XEN) HVM9 restore: PIC 1
(XEN) HVM9 restore: IOAPIC 0
(XEN) HVM9 restore: LAPIC 0
(XEN) HVM9 restore: LAPIC_REGS 0
(XEN) HVM9 restore
flight 173209 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173209/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
build-i386-libvir
I am departing DornerWorks. I will still be working with Xen in my next
role, and I still have an interest in maintaining the ARINC 653
scheduler, so change to my personal email address. Also change status to
Maintained.
Signed-off-by: Stewart Hildebrand
---
MAINTAINERS | 4 ++--
1 file changed,
flight 173214 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173214/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On Thu, 15 Sep 2022, Jan Beulich wrote:
> Plus an advanced question: In how far does this interoperate with
> static allocation, which again is (for now) an Arm-only feature?
> Your reference to dom0less above doesn't cover this afaict.
I take you are referring to static-mem, the static memory ran
On Thu, Sep 15, 2022 at 10:39 AM Jan Beulich wrote:
>
> On 15.09.2022 16:16, Tamas K Lengyel wrote:
> > On Thu, Sep 15, 2022 at 10:10 AM Jan Beulich wrote:
> >>
> >> On 15.09.2022 16:05, Tamas K Lengyel wrote:
> >>> On Thu, Sep 15, 2022 at 3:56 AM Jan Beulich wrote:
>
> On 15.09.2022 0
Hi All,
I am running a userland debugger in Windows 10 HVM on Xen 4.16 on an Intel
chip. I noticed when I set a hardware breakpoint (which writes to the DR0
register), Windows 10 crashes. This crash reproduces both with and without
viridian enabled in the DomU cfg file.
(XEN) Xen version 4.16.1 (n
On Thu, Sep 15, 2022 at 06:20:52PM +0200, Roger Pau Monne wrote:
> Current usage of Werror=switch-enum by default for libvirt builds out
> of the git tree causes issues when new items are added to libxl public
> API enums if those are used in a switch statement in libvirt code.
> This leads to libv
Current usage of Werror=switch-enum by default for libvirt builds out
of the git tree causes issues when new items are added to libxl public
API enums if those are used in a switch statement in libvirt code.
This leads to libvirt build failures for seemingly unrelated libxl
changes.
In order to pr
flight 173207 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173207/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-raw 1 buil
On Thu, Sep 15, 2022 at 03:10:59PM +0100, Anthony PERARD wrote:
> On Tue, Sep 13, 2022 at 12:03:28PM +0200, Roger Pau Monne wrote:
> > Current usage of Werror=switch-enum by default for libvirt builds out
> > of the git tree causes issues when new items are added to libxl public
> > API enums if th
On Thu, Sep 15, 2022 at 10:01:11AM +0200, Jan Beulich wrote:
> On 14.09.2022 16:23, Roger Pau Monné wrote:
> > On Wed, Sep 14, 2022 at 12:13:49PM +0200, Jan Beulich wrote:
> >> On 14.09.2022 11:13, Roger Pau Monné wrote:
> >>> On Wed, Sep 14, 2022 at 10:31:34AM +0200, Jan Beulich wrote:
> On 1
On Thu, Sep 15, 2022 at 05:24:22PM +0200, Roger Pau Monné wrote:
> Hello,
>
> There was a bit of a mess with osstest, changes have been pushed
> directly into xenbits osstest.git#master. The same changes have also
> been pushed to testing.git#pretest (but it seems that with different
> hashes).
Hello,
There was a bit of a mess with osstest, changes have been pushed
directly into xenbits osstest.git#master. The same changes have also
been pushed to testing.git#pretest (but it seems that with different
hashes). Prestest however is not passing because of libvirt build
issues.
osstest.git
flight 173211 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173211/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On 15.09.22 16:47, Oleksandr Tyshchenko wrote:
On 15.09.22 17:31, Juergen Gross wrote:
Hello Juergen
Commit 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
introduced an error for initialization of multi-page rings.
Cc: sta...@vger.kernel.org
Fixes: 4573240f0764 ("xen/xenbus: elim
Hi Jan,
On Thu, Sep 15, 2022 at 03:29:08PM +0200, Jan Beulich wrote:
> On 26.08.2022 14:50, Carlo Nonato wrote:
> > Shared caches in multi-core CPU architectures represent a problem for
> > predictability of memory access latency. This jeopardizes applicability
> > of many Arm platform in real-tim
On 15.09.22 17:31, Juergen Gross wrote:
Hello Juergen
> Commit 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
> introduced an error for initialization of multi-page rings.
>
> Cc: sta...@vger.kernel.org
> Fixes: 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
> Reported-by
On 15.09.2022 16:31, Juergen Gross wrote:
> Commit 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
> introduced an error for initialization of multi-page rings.
>
> Cc: sta...@vger.kernel.org
> Fixes: 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
> Reported-by: Sander Eikel
flight 173206 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173206/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-rtds broken
build-i386-libvirt6 libvirt-buil
On 15.09.2022 16:16, Tamas K Lengyel wrote:
> On Thu, Sep 15, 2022 at 10:10 AM Jan Beulich wrote:
>>
>> On 15.09.2022 16:05, Tamas K Lengyel wrote:
>>> On Thu, Sep 15, 2022 at 3:56 AM Jan Beulich wrote:
On 15.09.2022 02:41, Tamas K Lengyel wrote:
>>> Do you have any idea what might
Commit 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
introduced an error for initialization of multi-page rings.
Cc: sta...@vger.kernel.org
Fixes: 4573240f0764 ("xen/xenbus: eliminate xenbus_grant_ring()")
Reported-by: Sander Eikelenboom
Signed-off-by: Juergen Gross
---
drivers/xen
On 15/09/2022 15:10, Juergen Gross wrote:
On 15.09.22 14:49, Sander Eikelenboom wrote:
Hi Juergen,
I'm having trouble booting my DomU's when trying to use a linux-5.19 kernel for
both Dom0 and DomU.
A dom0 5.19 kernel with a domU 5.18 kernel boots fine.
I'm using durect kernel boot to boot the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Sep 15, 2022 at 01:56:06PM +0100, Julien Grall wrote:
> Hi Demi,
>
> On 15/09/2022 12:24, Demi Marie Obenour wrote:
> > On Thu, Sep 15, 2022 at 12:04:55PM +0200, Jan Beulich wrote:
> > > [1] specifies a long list of instructions which are in
On Thu, Sep 15, 2022 at 10:10 AM Jan Beulich wrote:
>
> On 15.09.2022 16:05, Tamas K Lengyel wrote:
> > On Thu, Sep 15, 2022 at 3:56 AM Jan Beulich wrote:
> >>
> >> On 15.09.2022 02:41, Tamas K Lengyel wrote:
> > Do you have any idea what might be going on and preventing the output
> > fr
On Tue, Sep 13, 2022 at 12:03:28PM +0200, Roger Pau Monne wrote:
> Current usage of Werror=switch-enum by default for libvirt builds out
> of the git tree causes issues when new items are added to libxl public
> API enums if those are used in a switch statement in libvirt code.
> This leads to libv
On 15.09.2022 16:05, Tamas K Lengyel wrote:
> On Thu, Sep 15, 2022 at 3:56 AM Jan Beulich wrote:
>>
>> On 15.09.2022 02:41, Tamas K Lengyel wrote:
> Do you have any idea what might be going on and preventing the output
> from showing over USB3 afterwards? The /dev/ttyUSB0 device is still
>
On Thu, Sep 15, 2022 at 3:56 AM Jan Beulich wrote:
>
> On 15.09.2022 02:41, Tamas K Lengyel wrote:
> >>> Do you have any idea what might be going on and preventing the output
> >>> from showing over USB3 afterwards? The /dev/ttyUSB0 device is still
> >>> present on the receiving side, just nothing
While experimenting with the vPMU subsystem an ASSERT failure was
observed in vmx_find_msr because the vcpu_runnable state was true.
The root cause of the bug appears to be the fact that the vPMU subsystem
doesn't save its state on context_switch. The vpmu_load function will attempt
to gather the
On 26.08.2022 14:50, Carlo Nonato wrote:
> Shared caches in multi-core CPU architectures represent a problem for
> predictability of memory access latency. This jeopardizes applicability
> of many Arm platform in real-time critical and mixed-criticality
> scenarios. We introduce support for cache p
On 26.08.2022 14:51, Carlo Nonato wrote:
> --- a/xen/common/vmap.c
> +++ b/xen/common/vmap.c
> @@ -8,6 +8,9 @@
> #include
> #include
> #include
> +#ifdef CONFIG_CACHE_COLORING
> +#include
> +#endif
Even independent of my earlier question towards more code becoming common,
I think there will
On 26.08.2022 14:51, Carlo Nonato wrote:
> This commit adds a new memory page allocator that implements the cache
> coloring mechanism. The allocation algorithm follows the given color
> configuration of the domain and maximizes contiguity in the page selection.
>
> Pages are stored in a color-ind
On 15.09.22 14:49, Sander Eikelenboom wrote:
Hi Juergen,
I'm having trouble booting my DomU's when trying to use a linux-5.19 kernel for
both Dom0 and DomU.
A dom0 5.19 kernel with a domU 5.18 kernel boots fine.
I'm using durect kernel boot to boot the domU guest (kernel= and ramdisk=
parame
Hi Demi,
On 15/09/2022 12:24, Demi Marie Obenour wrote:
On Thu, Sep 15, 2022 at 12:04:55PM +0200, Jan Beulich wrote:
[1] specifies a long list of instructions which are intended to exhibit
timing behavior independent of the data they operate on. On certain
hardware this independence is optional
Hi Juergen,
I'm having trouble booting my DomU's when trying to use a linux-5.19 kernel for
both Dom0 and DomU.
A dom0 5.19 kernel with a domU 5.18 kernel boots fine.
I'm using durect kernel boot to boot the domU guest (kernel= and ramdisk=
parameters).
Since both xen-blkback and xen-blkfront
On 15.09.22 13:50, Jan Beulich wrote:
On 13.09.2022 11:32, Juergen Gross wrote:
The size of struct active_grant_entry for 64-bit builds is 40 or 48
bytes today (with or without NDEBUG).
It can easily be reduced by 8 bytes by replacing the trans_domain
pointer with the domid of the related domai
flight 173208 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173208/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Sep 15, 2022 at 12:04:55PM +0200, Jan Beulich wrote:
> [1] specifies a long list of instructions which are intended to exhibit
> timing behavior independent of the data they operate on. On certain
> hardware this independence is optional, con
flight 173201 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173201/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 172133
build-i386-libvirt
On 15.09.22 11:32, Jan Beulich wrote:
On 15.09.2022 10:39, Juergen Gross wrote:
The IOCTL_PRIVCMD_MMAP isn't in use by Xen since at least Xen 4.0.
Remove it from the privcmd driver.
Signed-off-by: Juergen Gross
Can we reasonably remove an IOCTL, without being entirely certain that
no users
flight 173205 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173205/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-i386-libvirt
[1] specifies a long list of instructions which are intended to exhibit
timing behavior independent of the data they operate on. On certain
hardware this independence is optional, controlled by a bit in a new
MSR. Provide a command line option to control the mode Xen and its
guests are to operate i
flight 173200 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173200/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
build-i386-libvir
On 15.09.2022 10:39, Juergen Gross wrote:
> The IOCTL_PRIVCMD_MMAP isn't in use by Xen since at least Xen 4.0.
>
> Remove it from the privcmd driver.
>
> Signed-off-by: Juergen Gross
Can we reasonably remove an IOCTL, without being entirely certain that
no users exist outside of xen.git? Even i
The IOCTL_PRIVCMD_MMAP isn't in use by Xen since at least Xen 4.0.
Remove it from the privcmd driver.
Signed-off-by: Juergen Gross
---
drivers/xen/privcmd.c | 138 +
include/uapi/xen/privcmd.h | 2 -
include/xen/xen-ops.h | 24 ---
3 files ch
On 14.09.2022 16:23, Roger Pau Monné wrote:
> On Wed, Sep 14, 2022 at 12:13:49PM +0200, Jan Beulich wrote:
>> On 14.09.2022 11:13, Roger Pau Monné wrote:
>>> On Wed, Sep 14, 2022 at 10:31:34AM +0200, Jan Beulich wrote:
On 14.09.2022 10:14, Jan Beulich wrote:
> On 13.09.2022 16:50, Roger Pa
On 15.09.2022 02:41, Tamas K Lengyel wrote:
>>> Do you have any idea what might be going on and preventing the output
>>> from showing over USB3 afterwards? The /dev/ttyUSB0 device is still
>>> present on the receiving side, just nothing is being received over it.
>>
>> There are few more patches i
On 15.09.2022 03:18, Stefano Stabellini wrote:
> On Wed, 14 Sep 2022, Jan Beulich wrote:
>> I did look some at the specific use by the TEE subsystem, and it looks
>> to me as if their "shared memory" machinery simply isn't meant to be
>> used with non-local memory.
>
> Any more info?
I guess that
protmode_load_seg() would better adhere to that "feature" of clearing
base (and limit) during NULL selector loads.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/x86_emulate/x86_emulate.c
+++ b/xen/arch/x86/x86_emulate/x86_emulate.c
@@ -1970,6 +1970,7 @@ amd_like(const struct x86_emulate_ctxt *
68 matches
Mail list logo