[linux-linus test] 150356: tolerable trouble: fail/pass/starved - PUSHED

flight 150356 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/150356/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 150345 test-amd64-amd64-xl-qemut-ws16-amd64

Re: iommu=no-igfx

On Mon, May 25, 2020 at 5:16 AM Tian, Kevin wrote: > > From: Jan Beulich > > Sent: Wednesday, May 20, 2020 7:11 PM > > > > On 11.05.2020 19:43, buy computer wrote: > > > I've been working on a Windows 10 HVM on a Debian 10 dom0. When I > > was first > > > trying to make the VM, I was getting

[seabios test] 150357: regressions - trouble: blocked/fail/pass/starved

flight 150357 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/150357/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 150308 Tests which did not

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

flight 150355 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/150355/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 12 guest-start fail REGR. vs. 150346 Tests which did not

Re: [PATCH v2 for-4.14 1/2] x86/mem_sharing: block interrupt injection for forks

On Sun, May 24, 2020 at 8:33 PM Tian, Kevin wrote: > > > From: Lengyel, Tamas > > Sent: Saturday, May 23, 2020 12:34 AM > > > > When running shallow forks without device models it may be undesirable for > > Xen > > what is shallow forks? and why interrupt injection is not desired without >

[PATCH] SUPPORT: Add linux device model stubdom to Toolstack

Add qemu-xen linux device model stubdomain to the Toolstack section as a Tech Preview. Signed-off-by: Jason Andryuk --- SUPPORT.md | 6 ++ 1 file changed, 6 insertions(+) diff --git a/SUPPORT.md b/SUPPORT.md index e3a366fd56..25becc9192 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -153,6

[PATCH] CHANGELOG: Add qemu-xen linux device model stubdomains

Add qemu-xen linux device model stubdomain. Signed-off-by: Jason Andryuk --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ccb5055c87..52ed470903 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,6 +16,7 @@ The format is based on [Keep a

[PATCH 2/8] vchan-socket-proxy: Check xs_watch return value

Check the return value of xs_watch and error out on failure. This was found by Citrix's Coverity. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/tools/libvchan/vchan-socket-proxy.c

[PATCH 8/8] vchan-socket-proxy: Handle closing shared input/output_fd

input_fd & output_fd may be the same FD. In that case, mark both as -1 when closing one. That avoids a dangling FD reference. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/libvchan/vchan-socket-proxy.c

[PATCH 4/8] vchan-socket-proxy: Use a struct to store state

Use a struct to group the vchan ctrl and FDs. This will facilite tracking the state of open and closed FDs and ctrl in data_loop(). Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 52 + 1 file changed, 30 insertions(+), 22 deletions(-) diff

[PATCH 0/8] Coverity fixes for vchan-socket-proxy

This series addresses some Coverity reports. To handle closing FDs, a state struct is introduced to track FDs closed in both main() and data_loop(). Jason Andryuk (8): vchan-socket-proxy: Ensure UNIX path NUL terminated vchan-socket-proxy: Check xs_watch return value vchan-socket-proxy:

[PATCH 3/8] vchan-socket-proxy: Unify main return value

Introduce 'ret' for main's return value and remove direct returns. This is in preparation for a unified exit path with resource cleanup. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff --git

[PATCH 5/8] vchan-socket-proxy: Switch data_loop() to take state

Switch data_loop to take a pointer to vchan_proxy_state. No functional change. This removes a dead store to input_fd identified by Coverity. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 65 +++-- 1 file changed, 33 insertions(+), 32

[PATCH 7/8] vchan-socket-proxy: Cleanup resources on exit

Close open FDs and close th vchan connection when exiting the program. This addresses some Coverity findings about leaking file descriptors. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 9 + 1 file changed, 9 insertions(+) diff --git

[PATCH 6/8] vchan-socket-proxy: Set closed FDs to -1

These FDs are closed, so set them to -1 so they are no longer valid. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/libvchan/vchan-socket-proxy.c b/tools/libvchan/vchan-socket-proxy.c index 32be410609..f3f6e5ec09

[PATCH 1/8] vchan-socket-proxy: Ensure UNIX path NUL terminated

Check the socket path length to ensure sun_path is NUL terminated. This was spotted by Citrix's Coverity. Signed-off-by: Jason Andryuk --- tools/libvchan/vchan-socket-proxy.c | 12 1 file changed, 12 insertions(+) diff --git a/tools/libvchan/vchan-socket-proxy.c

RE: [PATCH v2 for-4.14 1/2] x86/mem_sharing: block interrupt injection for forks

> From: Lengyel, Tamas > Sent: Saturday, May 23, 2020 12:34 AM > > When running shallow forks without device models it may be undesirable for > Xen what is shallow forks? and why interrupt injection is not desired without device model? If it means just without Qemu thing, you still get local

RE: [PATCH v10 01/12] xen/vmx: let opt_ept_ad always reflect the current setting

> From: Juergen Gross > Sent: Tuesday, May 19, 2020 3:21 PM > > In case opt_ept_ad has not been set explicitly by the user via command > line or runtime parameter, it is treated as "no" on Avoton cpus. > > Change that handling by setting opt_ept_ad to 0 for this cpu type > explicitly if no user

RE: iommu=no-igfx

> From: Jan Beulich > Sent: Wednesday, May 20, 2020 7:11 PM > > On 11.05.2020 19:43, buy computer wrote: > > I've been working on a Windows 10 HVM on a Debian 10 dom0. When I > was first > > trying to make the VM, I was getting IOMMU errors. I had a hard time > > figuring out what to do about

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

flight 150353 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/150353/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-rtds 16 guest-localmigrate fail REGR. vs. 150332 test-armhf-armhf-xl-rtds

[xen-unstable-smoke test] 150354: tolerable all pass - PUSHED

flight 150354 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/150354/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass test-arm64-arm64-xl-xsm

Re: [PATCH 12/12] xen/arm: call iomem_permit_access for passthrough devices

Hi, On 30/04/2020 14:01, Julien Grall wrote: On 29/04/2020 21:47, Stefano Stabellini wrote: On Wed, 15 Apr 2020, Julien Grall wrote: But doesn't it make sense to give domU permission if it is going to get the memory mapped? But admittedly I can't think of something that would break because of

[xen-unstable test] 150346: tolerable FAIL

flight 150346 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/150346/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-rtds 16 guest-localmigrate fail pass in 150341 Tests which did not succeed,

Re: [PATCH] x86/shadow: Reposition sh_remove_write_access_from_sl1p()

At 10:04 +0100 on 21 May (1590055468), Andrew Cooper wrote: > When compiling with SHOPT_OUT_OF_SYNC disabled, the build fails with: > > common.c:41:12: error: ‘sh_remove_write_access_from_sl1p’ declared ‘static’ > but never defined [-Werror=unused-function] >static int

[libvirt bisection] complete build-arm64-libvirt

branch xen-unstable xenbranch xen-unstable job build-arm64-libvirt testid libvirt-build Tree: libvirt git://libvirt.org/libvirt.git Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git Tree: qemuu

[xen-unstable-coverity test] 150349: all pass - PUSHED

flight 150349 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/150349/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen 5e015d48a5ee68ba03addad2698364d8f015afec baseline version: xen

[libvirt bisection] complete build-i386-libvirt

branch xen-unstable xenbranch xen-unstable job build-i386-libvirt testid libvirt-build Tree: libvirt git://libvirt.org/libvirt.git Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git Tree: qemu

[linux-linus test] 150345: tolerable FAIL - PUSHED

flight 150345 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/150345/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 150343 test-amd64-amd64-xl-qemuu-win7-amd64

[libvirt test] 150347: regressions - FAIL

flight 150347 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/150347/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 146182 build-i386-libvirt