flight 180360 linux-linus real [real]
flight 180370 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180360/
http://logs.test-lab.xenproject.org/osstest/logs/180370/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
flight 180368 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180368/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 2c2cb235289642775a7c4e6eaeffa6d3828d279c
baseline version:
ovmf
flight 180353 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180353/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 180308
test-armhf-armhf-libvirt-qcow2 15
flight 180352 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180352/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken in 180333
Tests which
flight 180364 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180364/
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
flight 180365 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180365/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf ed2ff315db7e800dd7718b1d1320ea8024d4e8b2
baseline version:
ovmf
On Thu, Apr 20 2023 at 21:10, Thomas Gleixner wrote:
> On Thu, Apr 20 2023 at 18:47, Paul Menzel wrote:
>> Am 20.04.23 um 17:57 schrieb Thomas Gleixner:
>> I quickly applied it on top of your branch, but I am getting:
>
> As I said it was untested. I was traveling and did not have access to a
>
Am 21. April 2023 07:38:10 UTC schrieb "Michael S. Tsirkin" :
>On Mon, Apr 03, 2023 at 09:41:17AM +0200, Bernhard Beschow wrote:
>> There is currently a dedicated PIIX3 device model for use under Xen. By
>> reusing
>> existing PCI API during initialization this device model can be eliminated
On Thu, 2023-04-20 at 16:36 +0200, Jan Beulich wrote:
> On 19.04.2023 17:42, Oleksii Kurochko wrote:
> > --- a/xen/arch/riscv/include/asm/page-bits.h
> > +++ b/xen/arch/riscv/include/asm/page-bits.h
> > @@ -1,6 +1,16 @@
> > #ifndef __RISCV_PAGE_BITS_H__
> > #define __RISCV_PAGE_BITS_H__
> >
>
flight 180349 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180349/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken in 180325
On Thu, 2023-04-20 at 14:58 +0200, Jan Beulich wrote:
> On 19.04.2023 17:42, Oleksii Kurochko wrote:
> > --- a/xen/arch/riscv/include/asm/config.h
> > +++ b/xen/arch/riscv/include/asm/config.h
> > @@ -4,6 +4,37 @@
> > #include
> > #include
> >
> > +/*
> > + * RISC-V64 Layout:
> > + *
> > + *
This protects devices from bh->mmio reentrancy issues.
Thanks: Thomas Huth for diagnosing OS X test failure.
Reviewed-by: Darren Kenny
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Michael S. Tsirkin
Reviewed-by: Paul Durrant
Signed-off-by: Alexander Bulekov
Reviewed-by: Thomas Huth
---
flight 180357 xen-unstable-smoke real [real]
flight 180362 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180357/
http://logs.test-lab.xenproject.org/osstest/logs/180362/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which
Hi Roger,
Roger Pau Monné writes:
> On Fri, Apr 21, 2023 at 11:00:23AM +, Volodymyr Babchuk wrote:
>>
>> Hello Roger,
>>
>> Roger Pau Monné writes:
>>
>> > On Mon, Apr 17, 2023 at 12:34:31PM +0200, Jan Beulich wrote:
>> >> On 17.04.2023 12:17, Roger Pau Monné wrote:
>> >> > On Fri, Apr
Today it is not possible to analyse crash dumps of a system in
hypervisor mode when it had been booted via EFI, as the crash utility
doesn't understand the file format of xen.efi.
This can easily be solved by creating an ELF file from xen.efi via
objcopy. Using that file as name list for crash
On Fri, Apr 21, 2023 at 11:00:23AM +, Volodymyr Babchuk wrote:
>
> Hello Roger,
>
> Roger Pau Monné writes:
>
> > On Mon, Apr 17, 2023 at 12:34:31PM +0200, Jan Beulich wrote:
> >> On 17.04.2023 12:17, Roger Pau Monné wrote:
> >> > On Fri, Apr 14, 2023 at 01:30:39AM +, Volodymyr Babchuk
Hi Jan,
Jan Beulich writes:
> On 21.04.2023 13:00, Volodymyr Babchuk wrote:
>>
>> Hello Roger,
>>
>> Roger Pau Monné writes:
>>
>>> On Mon, Apr 17, 2023 at 12:34:31PM +0200, Jan Beulich wrote:
On 17.04.2023 12:17, Roger Pau Monné wrote:
> On Fri, Apr 14, 2023 at 01:30:39AM +,
Hi Oleg,
On 21/04/2023 14:49, Oleg Nikitenko wrote:
>
>
>
> Hello Michal,
>
> I was not able to enable earlyprintk in the xen for now.
> I decided to choose another way.
> This is a xen's command line that I found out completely.
>
> (XEN) console=dtuart dtuart=serial0
Hello Michal,
I was not able to enable earlyprintk in the xen for now.
I decided to choose another way.
This is a xen's command line that I found out completely.
(XEN) console=dtuart dtuart=serial0 dom0_mem=1600M dom0_max_vcpus=2
dom0_vcpus_pin bootscrub=0 vwfi=native sched=null
On 21.04.2023 13:00, Volodymyr Babchuk wrote:
>
> Hello Roger,
>
> Roger Pau Monné writes:
>
>> On Mon, Apr 17, 2023 at 12:34:31PM +0200, Jan Beulich wrote:
>>> On 17.04.2023 12:17, Roger Pau Monné wrote:
On Fri, Apr 14, 2023 at 01:30:39AM +, Volodymyr Babchuk wrote:
> Above I
Hi Henry,
> On 21 Apr 2023, at 08:33, Henry Wang wrote:
>
> Hi,
>
>> -Original Message-
>> Subject: RE: Xen 4.18 release schedule update and poll (was: RE: Xen 4.18
>> release: Proposed release schedule)
>>
>> Hi Bertrand,
>>
>>> -Original Message-
>>> From: Bertrand Marquis
Hello Roger,
Roger Pau Monné writes:
> On Mon, Apr 17, 2023 at 12:34:31PM +0200, Jan Beulich wrote:
>> On 17.04.2023 12:17, Roger Pau Monné wrote:
>> > On Fri, Apr 14, 2023 at 01:30:39AM +, Volodymyr Babchuk wrote:
>> >> Above I have proposed another view on this. I hope, it will work for
Hello,
Just wanted to add some additional information hoping it will help to start the
discussion and find a correct approach:
My goal is to provide correct buffer for the interfaces, such as
zwp_linux_dmabuf_v1_interface, so zero-copy
feature will work. My suggestion is to give a possibility
flight 180334 qemu-mainline real [real]
flight 180358 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180334/
http://logs.test-lab.xenproject.org/osstest/logs/180358/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 180341 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180341/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qcow2 19 guest-start/debian.repeat fail REGR. vs.
180278
On 21.04.2023 11:23, Henry Wang wrote:
>> -Original Message-
>> From: Jan Beulich
>>
>>> --- a/xen/arch/arm/numa.c
>>> +++ b/xen/arch/arm/numa.c
>>> @@ -28,6 +28,11 @@ enum dt_numa_status {
>>>
>>> static enum dt_numa_status __ro_after_init device_tree_numa =
>> DT_NUMA_DEFAULT;
>>>
>>>
Hi Jan,
> -Original Message-
> From: Jan Beulich
> Subject: Re: [PATCH v3 03/17] xen/arm: implement node distance helpers for
> Arm
> > As both x86 and Arm have implemented __node_distance, so we move
> > its definition from asm/numa.h to xen/numa.h.
>
> Nit: You mean "declaration", not
On 21/04/2023 10:04, Oleg Nikitenko wrote:
>
>
>
> Hello Michal,
>
> Yes, I use yocto.
>
> Yesterday all day long I tried to follow your suggestions.
> I faced a problem.
> Manually in the xen config build file I pasted the strings:
In the .config file or in some Yocto file (listing
Hi Ayan,
On 13/04/2023 19:37, Ayan Kumar Halder wrote:
>
>
> When 32 bit physical addresses are used (ie PHYS_ADDR_T_32=y),
> "va >> ZEROETH_SHIFT" causes an overflow.
> Also, there is no zeroeth level page table on Arm32.
>
> Also took the opportunity to clean up dump_pt_walk(). One could use
Hello Michal,
Yes, I use yocto.
Yesterday all day long I tried to follow your suggestions.
I faced a problem.
Manually in the xen config build file I pasted the strings:
CONFIG_EARLY_PRINTK
CONFIG_EARLY_PRINTK_ZYNQMP
CONFIG_EARLY_UART_CHOICE_CADENCE
Host hangs in build time.
Maybe I did not
Hi Ayan,
On 13/04/2023 19:37, Ayan Kumar Halder wrote:
>
>
> Refer ARM IHI 0062D.c ID070116 (SMMU 2.0 spec), 17-360, 17.3.9,
> SMMU_CBn_TTBR0 is a 64 bit register. Thus, one can use
> writeq_relaxed_non_atomic() to write to it instead of invoking
> writel_relaxed() twice for lower half and
flight 180351 xen-unstable-smoke real [real]
flight 180355 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180351/
http://logs.test-lab.xenproject.org/osstest/logs/180355/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which
Hi Ayan,
On 13/04/2023 19:37, Ayan Kumar Halder wrote:
>
>
> dt_device_get_address() can accept uint64_t only for address and size.
> However, the address/size denotes physical addresses. Thus, they should
> be represented by 'paddr_t'.
> Consequently, we introduce a wrapper for
On Mon, Apr 03, 2023 at 09:41:17AM +0200, Bernhard Beschow wrote:
> There is currently a dedicated PIIX3 device model for use under Xen. By
> reusing
> existing PCI API during initialization this device model can be eliminated and
> the plain PIIX3 device model can be used instead.
>
> Resolving
On Mon, Apr 03, 2023 at 09:41:19AM +0200, Bernhard Beschow wrote:
> When calling pci_bus_irqs() multiple times on the same object without calling
> pci_bus_irqs_cleanup() in between PCIBus::irq_count[] is currently leaked.
> Let's fix this because Xen will do just that in a few commits, and
On Fri, Apr 21, 2023 at 02:26:46AM +, osstest service owner wrote:
> flight 180345 xen-unstable-smoke real [real]
> flight 180348 xen-unstable-smoke real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/180345/
> http://logs.test-lab.xenproject.org/osstest/logs/180348/
>
>
On Thu, Apr 20, 2023 at 04:14:55PM +, Ross Lagerwall wrote:
> > From: Roger Pau Monne
> > Sent: Thursday, April 6, 2023 12:41 PM
> > To: xen-devel@lists.xenproject.org
> > Cc: Roger Pau Monne ; Konrad Rzeszutek Wilk
> > ; Ross Lagerwall
> > Subject: [PATCH v2] livepatch-tools: remove usage
Hi,
> -Original Message-
> Subject: RE: Xen 4.18 release schedule update and poll (was: RE: Xen 4.18
> release: Proposed release schedule)
>
> Hi Bertrand,
>
> > -Original Message-
> > From: Bertrand Marquis
> > Subject: Re: Xen 4.18 release schedule update and poll (was: RE:
Hi Bertrand,
> -Original Message-
> From: Bertrand Marquis
> Subject: Re: Xen 4.18 release schedule update and poll (was: RE: Xen 4.18
> release: Proposed release schedule)
>
> Hi,
>
> > On 21 Apr 2023, at 05:22, Henry Wang wrote:
> >
> > Hi all,
> >
> > Following the discussion in
Hi,
> On 21 Apr 2023, at 05:22, Henry Wang wrote:
>
> Hi all,
>
> Following the discussion in April community call, here comes the two
> updated possible release schedule options that I came up with.
>
> Both of these two options will satisfy the requirements/concerns that
> I've received so
40 matches
Mail list logo
