flight 60822 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60822/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 11 guest-start fail like 60605
Tests which did not
flight 60817 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60817/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 58581
Tests which are failin
Hi,
I'm trying to use a PV guest VM on Xen to help debug Linux.
I was using VirtualBox to help debug Linux kernel by redirecting the output
of the serial port of the VM to a file in the host. I can do it in
VirtualBox.
[Why do I want to achieve this?]
It is much faster to reboot a VM than rebooti
flight 60814 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60814/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 16
guest-start/debianhvm.repeat fail REGR. vs. 60681
flight 60812 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60812/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 3 host-install(3)broken REGR. vs. 60777
flight 60843 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60843/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 5 kernel-build fail REGR. vs. 60684
build-i386
On Sun, Aug 23, 2015 at 06:44:28AM +, osstest service owner wrote:
> flight 60810 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/60810/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-am
flight 60811 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60811/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate
fail REGR. vs
This patch uses HVMOP_IO_RANGE_XXX values rather than the raw ioreq
type to select the ioreq server, therefore the identical relationship
between ioreq type and rangeset type is no longer necessary.
Signed-off-by: Yu Zhang
Reviewed-by: Paul Durrant
---
xen/arch/x86/hvm/hvm.c | 16 +++---
This patch refactors struct rangeset to base it on the red-black
tree structure, instead of on the current doubly linked list. By
now, ioreq leverages rangeset to keep track of the IO/memory
resources to be emulated. Yet when number of ranges inside one
ioreq server is very high, traversing a doubl
XenGT leverages ioreq server to track and forward the accesses to
GPU I/O resources, e.g. the PPGTT(per-process graphic translation
tables). Currently, ioreq server uses rangeset to track the BDF/
PIO/MMIO ranges to be emulated. To select an ioreq server, the
rangeset is searched to see if the I/O
Currently in ioreq server, guest write-protected ram pages are
tracked in the same rangeset with device mmio resources. Yet
unlike device mmio, which can be in big chunks, the guest write-
protected pages may be discrete ranges with 4K bytes each. This
patch uses a seperate rangeset for the guest r
12 matches
Mail list logo
