Hi Jan
> -Original Message-
> From: Jan Beulich
> Sent: Monday, July 19, 2021 4:41 PM
> To: Penny Zheng ; jul...@xen.org
> Cc: Bertrand Marquis ; Wei Chen
> ; nd ; xen-devel@lists.xenproject.org;
> sstabell...@kernel.org
> Subject: Re: [PATCH V3 07/10] xen: re-define assign_pages and
flight 163849 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163849/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 12 debian-hvm-install
fail REGR. vs.
flight 163851 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163851/
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. 162359
RATIONALE: Features in recent versions of Windows now REQUIRE Hyper-V
support to work. In particular, Windows Containers, Sandbox, Docker Desktop
and the Windows Subsystem for Linux version 2 (WSL2). Running Windows in a
VM as a development and test platform is currently a common requirement for
On Tue, Jul 13, 2021 at 09:35:22PM +0200, Uwe Kleine-König wrote:
> The driver core ignores the return value of this callback because there
> is only little it can do when a device disappears.
>
> This is the final bit of a long lasting cleanup quest where several
> buses were converted to also
Hi Jan
> -Original Message-
> From: Jan Beulich
> Sent: Monday, July 19, 2021 4:20 PM
> To: Penny Zheng
> Cc: Bertrand Marquis ; Wei Chen
> ; nd ; xen-devel@lists.xenproject.org;
> sstabell...@kernel.org; jul...@xen.org
> Subject: Re: [PATCH V3 05/10] xen/arm: static memory
flight 163844 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163844/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds18 guest-start/debian.repeat fail REGR. vs. 163800
Tests which did not succeed,
flight 163853 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163853/
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
Hi,
I have a Debian 10 (buster/stable) dom0 running hypervisor 4.14.2.
For almost 2 years it's been using the packaged Debian stable kernel
which is 4.19.x.
Last night I upgraded the kernel to the buster-backports package
which is based on 5.10.40 and about 4 hours later got this:
Jul 20
flight 163841 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163841/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
On Mon, 12 Jul 2021, Michal Orzel wrote:
> AArch64 system registers are 64bit whereas AArch32 ones
> are 32bit or 64bit. MSR/MRS are expecting 64bit values thus
> we should get rid of helpers READ/WRITE_SYSREG32
> in favour of using READ/WRITE_SYSREG.
>
> The last place in code making use of
Re-ping?
On Tue, 13 Jul 2021, Stefano Stabellini wrote:
> Hi all,
>
> This short series adds a minimal ARM32 test based on QEMU. It just runs
> Xen and Dom0 up to a Busybox prompt.
>
> Cheers,
>
> Stefano
>
>
> Stefano Stabellini (2):
> Add qemu-system-arm to the existing
flight 163835 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163835/
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. 162359
This adds an option to the xl domain configuration file syntax for specifying
a kernel command line for device-model stubdomains. It is intended for use with
Linux-based stubdomains.
Signed-off-by: Scott Davis
---
docs/man/xl.cfg.5.pod.in | 4
flight 163834 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163834/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 12 debian-hvm-install
fail REGR. vs.
Andrew Cooper writes ("Re: [PATCH] tests/xs: Check asprintf result"):
> On 20/07/2021 15:31, Ian Jackson wrote:
> > fixed this (with slightly different style, and despite not mentioning
> > this change in the commit message)
>
> ? Literally half of the commit message pertains to this failure.
flight 163832 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163832/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 163458
test-amd64-amd64-qemuu-nested-amd
On Fri, Jul 16, 2021 at 04:41:57PM +0200, Olaf Hering wrote:
> Am Fri, 16 Jul 2021 15:28:43 +0100
> schrieb Anthony PERARD :
>
> > Actually, it's possible to delete the repo.
> > Navigate to the repo you want to delete (
> > https://gitlab.com/xen-project/people/olafhering )
> > then in the
On 20/07/2021 15:31, Ian Jackson wrote:
> Jason Andryuk writes ("[PATCH] tests/xs: Check asprintf result"):
>> Compiling xs-test.c on Ubuntu 21.04 fails with:
> Thanks. However, your patch doesn't apply to staging; the files have
> been reorganised AFAICT. Also, I think
>
>
On 19/07/2021 13:46, Jan Beulich wrote:
> On 19.07.2021 13:14, Andrew Cooper wrote:
>> hvm_load() is currently a mix of -errno and -1 style error handling, which
>> aliases -EPERM. This leads to the following confusing diagnostics:
>>
>> From userspace:
>> xc: info: Restoring domain
>> xc:
On Tue, Jul 20, 2021 at 10:31 AM Ian Jackson wrote:
>
> Jason Andryuk writes ("[PATCH] tests/xs: Check asprintf result"):
> > Compiling xs-test.c on Ubuntu 21.04 fails with:
>
> Thanks. However, your patch doesn't apply to staging; the files have
> been reorganised AFAICT. Also, I think
>
>
Jason Andryuk writes ("[PATCH] tests/xs: Check asprintf result"):
> Compiling xs-test.c on Ubuntu 21.04 fails with:
Thanks. However, your patch doesn't apply to staging; the files have
been reorganised AFAICT. Also, I think
93c9edbef51b31056f93a37a778326c90a83158c
tests/xenstore: Rework
Please split the swiotlb changes into a separate patch from the
consumer.
> }
> +
> +/*
> + * hv_map_memory - map memory to extra space in the AMD SEV-SNP Isolation VM.
> + */
> +unsigned long hv_map_memory(unsigned long addr, unsigned long size)
> +{
> + unsigned long *pfns = kcalloc(size
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-qemuu-debianhvm-amd64
testid debian-hvm-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu
flight 163824 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163824/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
Hi Christoph & Konrad:
Could you review this patch and make sure this is right way to
resolve the memory remap request from AMD SEV-SNP vTOM case?
Thanks.
On 7/7/2021 11:46 PM, Tianyu Lan wrote:
From: Tianyu Lan
In Isolation VM with AMD SEV, bounce buffer needs to be accessed via
flight 163829 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163829/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-armhf-libvirt
flight 163819 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163819/
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. 162359
flight 163811 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163811/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64 12 debian-hvm-install fail REGR. vs.
163321
29 matches
Mail list logo
