flight 33464 xen-4.4-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33464/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 33292
Tests which are f
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, January 15, 2015 6:06 PM
>
> > The composed reserved region list is then passed to domain builder,
> > which tries to detect and avoid conflicts when populating guest RAM.
> > To avoid breaking lowmem/highmem layout, we can define a
> From: George Dunlap
> Sent: Thursday, January 15, 2015 7:45 PM
>
> >
> > If above high level flow can be agreed, then we can move forward to
> > discuss next level detail e.g. how to pass the rmrr list cross different
> > components. :-)
>
> I think we're definitely ready to move on. There are
flight 33466 linux-3.10 real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33466/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 5 xen-boot fail REGR. vs. 26303
test-amd64-i386-rhel6h
branch xen-unstable
xen branch xen-unstable
job build-i386-libvirt
test libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.
The only use-case of the mem_event_op structure had been in mem_paging,
thus renaming the structure mem_paging_op and relocating its associated
functions clarifies its actual usage.
Signed-off-by: Tamas K Lengyel
---
tools/libxc/xc_mem_event.c | 16
tools/libxc/xc_mem_pagi
This patch series aims to clean up the mem_event subsystem within Xen. The
original use-case for this system was to allow external helper applications
running in privileged domains to control various memory operations performed
by Xen. Amongs these were paging, sharing and access control. The subsy
The name of the ring still implies it is used only for memory accesses,
which is no longer the case. It is also used to deliver variuos HVM events,
thus the name "monitor" is more appropriate in this setting.
Signed-off-by: Tamas K Lengyel
---
tools/libxc/xc_domain_restore.c | 14 +++---
To avoid growing hvm.c these functions can be stored
separately.
Signed-off-by: Tamas K Lengyel
---
xen/arch/x86/hvm/Makefile | 3 +-
xen/arch/x86/hvm/event.c| 195
xen/arch/x86/hvm/hvm.c | 163 +
x
The vm_event subsystem has been artifically tied to the presence of mem_access.
While mem_access does depend on vm_event, vm_event is an entirely independent
subsystem that can be used for arbitrary function-offloading to helper apps in
domains. This patch removes the dependency that mem_access nee
The spin-lock implementation in the xen-access test program is implemented
in a fashion that is actually incomplete. The x86 assembly that guarantees that
the lock is held by only one thread lacks the "lock;" instruction.
However, the spin-lock is not actually necessary in xen-access as it is not
From: Razvan Cojocaru
The public mem_event structures used to communicate with helper applications via
shared rings have been used in different settings. However, the variable names
within this structure have not reflected this fact, resulting in the reuse of
variables to mean different things un
The function names currently imply that these events are to be delivered via
the memory_event subsystem. However, the naming is confusing as these events
have nothing to do with actual memory events. Simply naming these functions
hvm_event_* more accurately describe their usage.
Signed-off-by: Tam
flight 33488 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33488/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-amd64-amd64-xl-pvh-inte
flight 33514 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33514/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 33422
build-armhf-libvirt
flight 33476 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33476/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-debianhvm-amd64 5 xen-bootfail pass in 33450
test-amd64-amd64-xl 9 gu
flight 33480 qemu-mainline real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33480/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 33424
test-amd64-i386-pair
On 2015/1/17 2:13, Konrad Rzeszutek Wilk wrote:
> On Thu, Jan 15, 2015 at 09:04:35PM +0800, Jiang Liu wrote:
>>
>> Note: we need to test this patch on those special AMD systems which
>> override normal SCI GSI (9) with strange GSI (20).
>
> [0.00] DMI: Supermicro X8DTN/X8DTN, BIOS 2.1c
On 2015/1/17 2:13, Konrad Rzeszutek Wilk wrote:
> On Thu, Jan 15, 2015 at 09:04:35PM +0800, Jiang Liu wrote:
>>
>> Note: we need to test this patch on those special AMD systems which
>> override normal SCI GSI (9) with strange GSI (20).
>
> [0.00] DMI: Supermicro X8DTN/X8DTN, BIOS 2.1c
branch xen-unstable
xen branch xen-unstable
job build-armhf-libvirt
test libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is
Xen overrides __acpi_register_gsi and leaves __acpi_unregister_gsi as is.
That means, an IRQ allocated by acpi_register_gsi_xen_hvm() or
acpi_register_gsi_xen() will be freed by acpi_unregister_gsi_ioapic(),
which may cause undesired effects. So override __acpi_unregister_gsi to
NULL for safety.
S
Hi,
anything missing to take these patches?
Juergen
On 12/17/2014 10:50 AM, Juergen Gross wrote:
The Xen hypercalls are defined in include/xen/interface/xen.h. There
are some places where for each hypercall a table element is created.
Instead of manually add each hypercall element to these tab
flight 33485 linux-linus real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33485/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-freebsd10-i386 7 freebsd-install fail like 33426
test-amd64-i386-freebsd10-amd6
flight 33553 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33553/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 5 libvirt-build fail REGR. vs. 33422
build-i386-libvirt
flight 33494 linux-3.14 real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33494/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 5 xen-boot fail REGR. vs. 33341
test-amd64-amd64-xl-pv
25 matches
Mail list logo
