[ovmf test] 175384: regressions - FAIL

flight 175384 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175384/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

[qemu-mainline test] 175377: tolerable FAIL - PUSHED

flight 175377 qemu-mainline real [real] flight 175386 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/175377/ http://logs.test-lab.xenproject.org/osstest/logs/175386/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

[linux-linus test] 175374: regressions - trouble: broken/fail/pass

flight 175374 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/175374/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-dom0pvh-xl-intel broken test-amd64-amd64-dom0pvh-xl-intel 5

[ovmf test] 175382: regressions - FAIL

flight 175382 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175382/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

Re: [Patch v1] Bug fix - Integer overflow when cpu frequency > u32 max value.

On 17/12/2022 5:42 pm, Neowutran wrote: > diff --git a/xen/arch/x86/time.c b/xen/arch/x86/time.c > index b01acd390d..7c77ec8902 100644 > --- a/xen/arch/x86/time.c > +++ b/xen/arch/x86/time.c > @@ -2585,7 +2585,7 @@ int tsc_set_info(struct domain *d, > case TSC_MODE_ALWAYS_EMULATE: >

[xen-unstable test] 175354: tolerable FAIL - PUSHED

flight 175354 xen-unstable real [real] flight 175378 xen-unstable real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/175354/ http://logs.test-lab.xenproject.org/osstest/logs/175378/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

[ovmf test] 175375: regressions - FAIL

flight 175375 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175375/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

[ovmf test] 175372: regressions - FAIL

flight 175372 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175372/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

Re: [Patch v1] Bug fix - Integer overflow when cpu frequency > u32 max value.

On Sat, Dec 17, 2022 at 06:42:05PM +0100, Neowutran wrote: > xen/arch/x86/time.c: Bug fix - Integer overflow when cpu frequency > u32 max > value. > > What is was trying to do: I was trying to install QubesOS on my new computer > (AMD zen4 processor). Guest VM were unusably slow / unusable. > >

[linux-linus test] 175361: regressions - FAIL

flight 175361 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/175361/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-multivcpu 8 xen-bootfail REGR. vs. 173462

[XEN v3] xen/arm: Probe the entry point address of an uImage correctly

Currently, kernel_uimage_probe() does not set info->zimage.start. As a result, it contains the default value (ie 0). This causes, kernel_zimage_place() to treat the binary (contained within uImage) as position independent executable. Thus, it loads it at an incorrect address. The correct approach

[ovmf test] 175369: regressions - FAIL

flight 175369 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175369/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

[xen-unstable bisection] complete test-amd64-amd64-xl-credit1

branch xen-unstable xenbranch xen-unstable job test-amd64-amd64-xl-credit1 testid xen-boot Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git Tree: qemuu

[Patch v1] Bug fix - Integer overflow when cpu frequency > u32 max value.

xen/arch/x86/time.c: Bug fix - Integer overflow when cpu frequency > u32 max value. What is was trying to do: I was trying to install QubesOS on my new computer (AMD zen4 processor). Guest VM were unusably slow / unusable. What is the issue: The cpu frequency reported is wrong for linux guest

[ovmf test] 175367: regressions - FAIL

flight 175367 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175367/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

Re: [PATCH RFC 10/10] common: convert vCPU info area registration

Hi, On 19/10/2022 08:45, Jan Beulich wrote: Switch to using map_guest_area(). Noteworthy differences from map_vcpu_info(): - remote vCPU-s are paused rather than checked for being down (which in principle can change right after the check), - the domain lock is taken for a much smaller

[ovmf test] 175364: regressions - FAIL

flight 175364 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175364/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

Re: [QEMU][PATCH v2 10/11] hw/arm: introduce xenpv machine

Hi, On 02/12/2022 22:36, Stefano Stabellini wrote: Do you know what Xen version your build env has? I think Alex is just building against upstream Xen. GUEST_TPM_BASE is not defined there yet. I think we would need to introduce in xen_common.h something like: #ifndef GUEST_TPM_BASE #define

Re: [PATCH] exec: Rename NEED_CPU_H -> CONFIG_TARGET

On Fri, 16 Dec 2022 at 22:09, Philippe Mathieu-Daudé wrote: > > 'NEED_CPU_H' guard target-specific code; it is defined by meson > altogether with the 'CONFIG_TARGET' definition. Since the latter > name is more meaningful, directly use it. > > Inspired-by: Peter Maydell > Signed-off-by: Philippe

[ovmf test] 175359: regressions - FAIL

flight 175359 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175359/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

[linux-linus test] 175345: regressions - FAIL

flight 175345 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/175345/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-multivcpu 8 xen-bootfail REGR. vs. 173462

[ovmf test] 175349: regressions - FAIL

flight 175349 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/175349/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 175202

Re: [XEN v1 2/9] xen/arm: Define translate_dt_address_size() for the translation between u64 and paddr_t

Hi, On 17/12/2022 00:46, Stefano Stabellini wrote: On Fri, 16 Dec 2022, Julien Grall wrote: Hi Ayan, On 15/12/2022 19:32, Ayan Kumar Halder wrote: paddr_t may be u64 or u32 depending of the type of architecture. Thus, while translating between u64 and paddr_t, one should check that the

[qemu-mainline test] 175344: tolerable FAIL - PUSHED

flight 175344 qemu-mainline real [real] flight 175355 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/175344/ http://logs.test-lab.xenproject.org/osstest/logs/175355/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):