This run is configured for baseline tests only.
flight 38193 qemu-upstream-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38193/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pygrub 10 guest
This run is configured for baseline tests only.
flight 38192 xen-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38192/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pygrub 20 guest-start/
On Tue, Oct 20, 2015 at 02:26:46PM +0100, Andrew Cooper wrote:
> On 20/10/15 09:21, Shuai Ruan wrote:
> > This patch add basic definitions/helpers which will be used in
> > later patches.
> >
> *this_xss = xss;
>
> Using this_cpu() multiple times cannot be optimised by compiler (because
> of the u
flight 63142 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63142/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail REGR. vs.
62380
test-amd64-
> -Original Message-
> From: Hu, Robert
> Sent: Thursday, October 15, 2015 5:58 PM
> To: Ian Jackson ;
> xen-de...@lists.xenproject.org
> Cc: Ian Campbell
> Subject: RE: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename
> `nodhcp' to `ensurebridge'
>
> > -Original Message-
flight 63145 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63145/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 0f34a051104e2b1b9123d56d48673de4b21bc533
baseline version:
ovmf 47022e82e1e59f59d375dd66847e93cea7b
flight 63117 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63117/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 15 guest-start.2fail blocked in 63086
Tests which did not succeed,
branch xen-4.3-testing
xen branch xen-4.3-testing
job build-armhf
test xen-build
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
B
On 10/15/2015 04:16 PM, Michal Marek wrote:
> Otherwise make tags can't parse them:
>
> ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern "\1"
> ctags: Warning: drivers/xen/events/events_2l.c:41: null expansion of name
> pattern "\1"
> ctags: Warning: drivers/acpi/processo
Dne 21.10.2015 v 21:27 Prarit Bhargava napsal(a):
> On 10/15/2015 04:16 PM, Michal Marek wrote:
>> Otherwise make tags can't parse them:
>>
>> ctags: Warning: arch/ia64/kernel/smp.c:60: null expansion of name pattern
>> "\1"
>> ctags: Warning: drivers/xen/events/events_2l.c:41: null expansion of n
On Wed, May 27, 2015 at 12:03:12AM +0200, Marek Marczykowski-Górecki wrote:
> On Tue, May 26, 2015 at 11:56:00AM +0100, David Vrabel wrote:
> > On 22/05/15 12:49, Marek Marczykowski-Górecki wrote:
> > > Hi all,
> > >
> > > I'm experiencing xen-netfront crash when doing xl network-detach while
> >
branch xen-4.2-testing
xen branch xen-4.2-testing
job build-amd64
test xen-build
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-4.2-testing.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.2-testing.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem chang
branch xen-4.3-testing
xen branch xen-4.3-testing
job build-amd64
test xen-build
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-4.3-testing.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-4.3-testing.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem chang
Hi,
Can somebody please point me to a resource that talks about scheduler
design for VMs , in contrast with a standard scheduler ( I have consulted
Remzi, Operating Systems for this which is pretty easy to understand
conceptually ). I need to understand the working of the credit scheduler.
Thanks
On 21/10/15 18:20, Ferger, Max wrote:
> Hi!
Hello,
> I'm sorry, but that didn't do the trick.
> Neither did trying, whether a compressed or non-compressed dom0 image would
> do.
>
> Also, I tried:
> - 8< -
> /chosen/xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug
> ignore_logle
This run is configured for baseline tests only.
flight 38185 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38185/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-xsm 21 guest-start/debian.repe
On Wed, Oct 21, 2015 at 05:47:06PM +0100, Ian Campbell wrote:
> On Tue, 2015-10-20 at 16:34 +0100, Ian Jackson wrote:
> > Wei Liu writes ("Re: [Xen-devel] [linux-4.1 test] 63030: regressions
> > - FAIL"):
> > > From mere code inspection and document of lwip 1.3.0 I think mini
> > -os
> > > does se
Hi!
I'm sorry, but that didn't do the trick.
Neither did trying, whether a compressed or non-compressed dom0 image would do.
Also, I tried:
- 8< -
/chosen/xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug ignore_loglevel
vmalloc=384M video=HDMI-A-1:1920x1080-32@60
ip=192.168.0.5:1
On Thu, 2015-10-15 at 10:25 +0200, Juergen Gross wrote:
> Maybe it would be a good idea to move setting of per_cpu(cpupool,
> cpu)
> into schedule_cpu_switch(). Originally I didn't do that to avoid
> spreading too much cpupool related actions outside of cpupool.c. But
> with those ASSERT()s added h
On Tue, 2015-10-20 at 16:34 +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [Xen-devel] [linux-4.1 test] 63030: regressions
> - FAIL"):
> > From mere code inspection and document of lwip 1.3.0 I think mini
> -os
> > does send gratuitous ARP.
>
> The guest is using the PVHVM drivers at this point
Hi everyone,
I managed running again the benchmarks I had already showed off here:
[PATCH RFC] xen: if on Xen, "flatten" the scheduling domain hierarchy
https://lkml.org/lkml/2015/8/18/302
Basically, this is about Linux guests using topology information for
scheduling, while they just don't ma
flight 63137 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63137/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
On 21/10/15 17:05, Ferger, Max wrote:
> Hi!
Hello,
> Thanks for both DT fixes, the "add ranges;", and the "complete memory map".
>
> Here are some findings:
>
> * Linus' most recent version of the kernel [1] (configured with a mix of
> Xen/OMAP description [2] and lager_defconfig [3]) needs th
On Mon, Oct 12, 2015 at 12:55 PM, Luis R. Rodriguez
wrote:
> On Mon, Oct 5, 2015 at 10:03 AM, Luis R. Rodriguez
> wrote:
>> On Mon, Oct 5, 2015 at 9:56 AM, Ian Jackson
>> wrote:
>>> Luis R. Rodriguez writes ("Wiki for automatic reports / fixes"):
>>> [...]
While discussing expectations an
On Wed, 2015-10-21 at 16:52 +0100, Ian Campbell wrote:
> On Wed, 2015-10-21 at 17:26 +0200, Olaf Hering wrote:
> > On Wed, Oct 21, Ian Campbell wrote:
> >
> > > http://xenbits.xen.org/gitweb/?p=qemu-xen.git
> >
> > Is the HEAD warning expected?
>
> No it is not.
Apparently it actually is, it's
Hi!
Thanks for both DT fixes, the "add ranges;", and the "complete memory map".
Here are some findings:
* Linus' most recent version of the kernel [1] (configured with a mix of
Xen/OMAP description [2] and lager_defconfig [3]) needs the 'add
"ranges;"'-fixes, but does not access the otherwise
> On 21 Oct 2015, at 17:02, Stefano Stabellini
> wrote:
>
> On Fri, 16 Oct 2015, Lars Kurth wrote:
>> * Blocking Votes
>>
>> We had several cases, where a voter wanted to express disagreement with a
>> proposal, but did not want to block a vote. I wanted to suggest an
>> approach that
flight 63097 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63097/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 15 guest-localmigrate.2 fail REGR. vs. 62811
Regressions whic
On Wed, 2015-10-21 at 17:26 +0200, Olaf Hering wrote:
> On Wed, Oct 21, Ian Campbell wrote:
>
> > http://xenbits.xen.org/gitweb/?p=qemu-xen.git
>
> Is the HEAD warning expected?
No it is not.
Both trees contain a file HEAD containing:
ref: refs/heads/master
which is the same as xen.git does
(Trimming CCs a bit)
On Wed, 2015-10-21 at 16:22 +0100, Ian Campbell wrote:
>
[...]
> Still to come would be libraries for specific out of tree purposes
> (device model, kexec), which would be adding new library at the same
> level as libxc I think, rather than underneath, i.e. also using the
> l
On Wed, 21 Oct 2015, Boris Ostrovsky wrote:
> On 10/21/2015 09:00 AM, Stefano Stabellini wrote:
> > >
> > > diff --git a/arch/x86/include/asm/xen/hypervisor.h
> > > b/arch/x86/include/asm/xen/hypervisor.h
> > > index d866959..8b2d4be 100644
> > > --- a/arch/x86/include/asm/xen/hypervisor.h
> > > +
libxenctrl links against this library
Signed-off-by: Ian Campbell
---
v3: Library moved to tools/libs
---
xen-hooks.mak | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen-hooks.mak b/xen-hooks.mak
index 179a6b7..229d642 100644
--- a/xen-hooks.mak
+++ b/xen-hooks.mak
@@ -25,6 +25,7 @@ LIBS +
On Wed, 21 Oct 2015, Fabio Fantoni wrote:
> Il 21/10/2015 14:45, Laszlo Ersek ha scritto:
> > On 10/21/15 13:39, Stefano Stabellini wrote:
> > > Empty cdroms are not going to connect, avoid waiting for the backend to
> > > switch to state 4, which is never going to happen, and return
> > > error in
On Wed, Oct 21, Ian Campbell wrote:
> http://xenbits.xen.org/gitweb/?p=qemu-xen.git
Is the HEAD warning expected?
$ git clone git://xenbits.xen.org/qemu-xen qemu-xen.git
$ cd $_
$ git remote show origin
* remote origin
Fetch URL: git://xenbits.xen.org/qemu-xen
Push URL: git://xenbits.xen.or
libxenevtchn has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxenevtchn if libxc is enabled.
Signed-off-by: Ian Campbell
---
v2: Adjust for libs/$lib layout.
---
Makefile | 1 +
1 file changed, 1 inse
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxengnttab which provides access to grant
tables.
In preparation for this switch the compatibility layer in xen_common.h
libxenforeignmemory has just been split out from libxc. From mini-os's
point of view we don't care about the distinction, so keep things
simple by just including libxenforeignmemory if libxc is enabled.
Signed-off-by: Ian Campbell
---
v2: Adjust for libs/$lib layout.
---
Makefile | 1 +
1 file c
libxentoollog has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxentoollog if libxc is enabled.
Signed-off-by: Ian Campbell
---
v2: Adjust for libs/$lib layout.
---
Makefile | 1 +
1 file changed, 1 in
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the mini-os part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch se
/dev/xen/gntdev related wrappers have been moved out of libxenctrl
into their own library.
Signed-off-by: Ian Campbell
---
v3: Library moved to tools/libs/
---
hw/xen_backend.c | 4 ++--
hw/xen_backend.h | 2 +-
hw/xen_common.h | 1 +
hw/xen_console.c | 4 ++--
hw/xen_disk.c| 24 +++
libxencall has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxencall if libxc is enabled.
Signed-off-by: Ian Campbell
---
v2: Adjust for libs/$lib layout.
---
Makefile | 1 +
1 file changed, 1 insertio
libxengnttab has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxengnttab if libxc is enabled.
Signed-off-by: Ian Campbell
---
v2: Adjust for libs/$lib layout.
---
Makefile | 1 +
1 file changed, 1 inse
Until the previous patch this relied on xc_fd(), which was only
implemented for Xen 4.0 and earlier.
Given this wasn't working since Xen 4.0 I have marked this as disabled
by default.
Removing this support drops the use of a bunch of symbols from
libxenctrl, specifically:
- xc_domain_create
The alternative backend (a xen-api/xapi shim) is no longer around and
so this stuff is now just baggage which is getting in the way of
refactoring libxenctrl.
Nested virt probably suffices for this use case now.
This was the last component of the osdep infrastructure, so all the
dynamic loading e
In tree libraries which link against other in tree libraries in a way
which is opaque to their callers need special handling, specifically
correct use of -Wl,-rpath-link for the recusively used libraries.
Currently this is rather simple, but up coming changes are going to
introduce transitive depe
libxengnttab will provide a stable API and ABI for accessing the
grant table devices.
The functions are moved into the xengnt{tab,shr} namespace to make a
clean break from libxc and avoid ambiguity regarding which interfaces
are stable.
XXX consider combining into a single namespace (i.e. with
xe
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenevtchn which provides access to event
channels.
In preparation for this switch the compatibility layer in xen_common.
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenforeignmemory which provides access to
privileged foreign mappings and which will provide an interface
equivalent to x
Using the same rune as we use for the Xen public headers, except we do
not need stdint.h here and we use -pedantic too.
Signed-off-by: Ian Campbell
---
.gitignore | 2 ++
tools/Rules.mk | 8
tools/libs/evtchn/Makefile | 4 +++-
tools/libs/toollog/Makefile
libxenctrl links against this library.
Also, request the compat xc_map_foreign API from libxc.
Signed-off-by: Ian Campbell
---
v3: Library moved to tools/libs/
---
xen-hooks.mak | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen-hooks.mak b/xen-hooks.mak
index 229d642..c1ea4be 100644
---
It can trivially be replaced by xc_map_foreign_bulk which is the
interface I want to move to going forward. All in tree users are
trivially converted by supplying the appropriate error array and
adjusting the what error handling exists (which in many cases is not
much).
This reduces the twist maze
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenforeignmemory which provides access to
privileged foreign mappings and which will provide an interface
equivalent to x
The alternative backend (a xen-api/xapi shim) is no longer around and
so this stuff is now just baggage which is getting in the way of
refactoring libxenctrl.
Nested virt probably suffices for this use case now.
It is now necessary to provide explicit versions of things for
platforms which do not
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the qemu-xen-traditional part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the rel
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the qemu-xen part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch s
All of the work in con_disconnect applies to the primary console case
(when xendev->dev is NULL). Therefore remove the early check and bail
and allow it to fall through. All of the existing code is correctly
conditional already.
The ->dev and ->gnttabdev handles are either both set or neither. For
/dev/xen/evtchn related wrappers have been moved out of libxenctrl
into their own library.
Note that i386-dm/helper2.c's xc_interface * was always really an
xc_evtchn *, it's just they used to be typedefs to the same thing...
Signed-off-by: Ian Campbell
---
v3: Library moved to tools/libs/
---
libxencall will provide a stable API and ABI for calling hypercalls
(although those hypercalls themselves may not have a stable API). As
well as the hypercall buffer infrastructure needed in order to safely
provide pointer arguments to hypercalls.
libxenctrl encapsulates a instance of this interfa
The alternative backend (a xen-api/xapi shim) is no longer around and
so this stuff is now just baggage which is getting in the way of
refactoring libxenctrl.
Note that the intention is to move this into a separate library
shortly.
Nested virt probably suffices for this use case now.
One incorre
These were wrong in the context of libxc before this code was
extracted, clean them up.
Also add some emacs magic blocks
Signed-off-by: Ian Campbell
---
tools/libs/call/buffer.c | 4 ++--
tools/libs/call/core.c| 2 +-
tools/libs/call/minios.c | 4 ++-
v4: Config.mk instead of .config
---
Config.mk | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Config.mk b/Config.mk
index 114db9a..a72b671 100644
--- a/Config.mk
+++ b/Config.mk
@@ -242,20 +242,20 @@ endif
ifeq ($(GIT_HTTP),y)
OVMF_UPSTREAM_URL ?= http:/
These are already arch specific, so just use the appropriate
interfaces (as determined by looking at the xc_memalign backend).
Signed-off-by: Ian Campbell
---
tools/libs/call/netbsd.c | 4 ++--
tools/libs/call/solaris.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tool
And require it be used instead of direct munmap.
This will allow e.g. Valgrind hooks to help track incorrect use of
foreign mappings.
Switch all uses of xenforeignmemory_map to use
xenforeignmemory_unmap, not that foreign mappings via the libxc compat
xc_map_foreign_* interface will not take adva
Signed-off-by: Ian Campbell
---
tools/libs/foreignmemory/include/xenforeignmemory.h | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tools/libs/foreignmemory/include/xenforeignmemory.h
b/tools/libs/foreignmemory/include/xenforeignmemory.h
index 99ec883..3f52417 100644
--
This has been split out of libxenctrl, so the build needs to be able
to find the header and the library. QEMU does not use xtl_* itself so
-rpath-link is sufficient to allow linking to libxenctrl.so (which
links against libxentoollog).
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: L
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the xen part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch series
Both Linux and FreeBSD already implemented these functions using
identical helpers based on xc_map_foreign_pages. Make one copy of
these common helpers and switch all OSes to use them, even those which
previously had a specific lower level implementation of this
functionality.
This is makes two fe
On Solaris and NetBSD xc_map_foreign_bulk is implemented by calling
xc_map_foreign_bulk_compat and xc_map_foreign_bulk_compat is exposed
as a symbol by libxenctrl.so.
Remove these wrappers and turn the compat function into the real thing
surrounded by the appropriate ifdef.
As this is a compat fu
Using an existing libxenctrl handle after a fork was never
particularly safe (especially if foreign mappings existed at the time
of the fork) and the xc fd has been unavailable for many releases.
Reopen the handle after fork and therefore do away with xc_fd().
Signed-off-by: Ian Campbell
Acked-b
Signed-off-by: Ian Campbell
---
tools/libs/call/linux.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libs/call/linux.c b/tools/libs/call/linux.c
index 906ca7e..80b505c 100644
--- a/tools/libs/call/linux.c
+++ b/tools/libs/call/linux.c
@@ -88,7 +88,7 @@ void *osdep
Surprisingly it appears no callers need updating.
Signed-off-by: Ian Campbell
---
v4: New patch
---
tools/libs/foreignmemory/compat.c | 2 +-
tools/libs/foreignmemory/freebsd.c | 4 ++--
.../libs/foreignmemory/include/xenforeignmemory.h | 4 ++--
tools/libs/f
This means adding -L for libxen{evtchn,gnttab,foreignmemory} so that
it can link them directly (rather than using the libxenctrl compat
layer exposed via -rpath-link). Also add -I for libxenforeignmemory.
Signed-off-by: Ian Campbell
---
tools/Makefile | 4
1 file changed, 4 insertions(+)
d
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenforeignmemory which provides access to
privileged foreign mappings and which will provide an interface
equivalent to x
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
Specifically libxenevtchn, libxengnttab and libxenforeignmemory.
Previous patches have already laid the groundwork for using these by
switching the
In attempting to disaggregate libxenctrl I found that many of the
pieces were going to want access to this library, so split it out (as
it probably should always have been).
Various build adjustments are needed. In particular things which use
xtl_* themselves now need to explicity link against the
Remove some stray xc references.
While I'm not convinced by javadoc/doxygen cause the existing comments
which appear to use that syntax to have the appropriate /** marker.
Also fix a typo in a code comment.
Signed-off-by: Ian Campbell
---
tools/libs/gnttab/include/xengnttab.h | 21 +++-
libxenforeignmemory will provide a stable API and ABI for mapping
foreign domain memory (subject to appropriate privileges).
The new library exposes an interface equivalent to
xc_map_foreign_memory_bulk, which all the other
xc_map_foreign_memory_* functions (which remain in libxc) are
implemented
Remove the reference to pre-4.1, since this is now a new library.
Fixup references to xc.
Signed-off-by: Ian Campbell
---
tools/libs/evtchn/include/xenevtchn.h | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/tools/libs/evtchn/include/xenevtchn.h
b/tools/libs/evtchn/in
In <1431963008.4944.80.ca...@citrix.com> I proposed stabilising some
parts of the libxenctrl API/ABI by disaggregating into separate
libraries.
This is v4 of that set of series against:
xen
qemu-xen
qemu-xen-traditional
mini-os
NB: Samuel+minios-devel will only get the mini-os sid
flight 63107 linux-linus running [real]
http://logs.test-lab.xenproject.org/osstest/logs/63107/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 59254
build-i386-xsm
flight 63102 xen-unstable running [real]
http://logs.test-lab.xenproject.org/osstest/logs/63102/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-build fail REGR. vs. 63080
build-i386-xsm
On Wed, 2015-10-21 at 14:16 +0100, Ian Campbell wrote:
> I have just completed the switch to use a single qemu tree for each of the
> versions we support (qemu-xen AKA upstream and qemu-xen-traditional AKA our
> historical fork).
Some flights which were active during the transition have been kille
flight 63115 xen-4.3-testing running [real]
http://logs.test-lab.xenproject.org/osstest/logs/63115/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62742
build-amd64
This run is configured for baseline tests only.
flight 38187 linux-4.1 running [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38187/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm 5 xen-build
This run is configured for baseline tests only.
flight 38189 qemu-upstream-unstable running [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38189/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xe
This run is configured for baseline tests only.
flight 38190 xen-4.5-testing running [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38190/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 5 xen-build
On Fri, 16 Oct 2015, Lars Kurth wrote:
> * Blocking Votes
>
>We had several cases, where a voter wanted to express disagreement with a
>proposal, but did not want to block a vote. I wanted to suggest an
>approach that we used very successfully in Event Program Management
>Committee
On Wed, 2015-10-21 at 15:12 +0100, Ian Campbell wrote:
> On Wed, 2015-10-21 at 14:15 +0100, Ian Campbell wrote:
> > > * Remove the old staging/qemu-upstream-* trees, they are not
> > >referenced by anything.
> >
> > Done (by move aside a discussed above).
>
> This was premature and I have pu
On Wed, 2015-10-21 at 14:15 +0100, Ian Campbell wrote:
> > * Remove the old staging/qemu-upstream-* trees, they are not
> >referenced by anything.
>
> Done (by move aside a discussed above).
This was premature and I have put them back.
The reason is that all osstest flights prior to the upd
That directory is used to store guest memory dump which contains
sensitive information.
Signed-off-by: Wei Liu
---
tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/Makefile b/tools/Makefile
index 2618559..820ca40 100644
--- a/tools/Makefile
+++ b/tools/Mak
On Wed, Oct 21, 2015 at 02:46:54PM +0100, Ian Campbell wrote:
> On Wed, 2015-10-21 at 13:10 +0100, Wei Liu wrote:
> > There is no need to explicitly ask for 700.
>
> Is the rationale for 0700 explicitly not that the files in here will
> contain possibly sensitive date from guest memory?
>
> i.e.
flight 63109 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63109/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-build fail REGR. vs. 63081
build-i386-xsm
From: Joe Jin
Date: Mon, 19 Oct 2015 13:37:17 +0800
> Sometimes xennet_create_queues() may failed to created all requested
> queues, we need to update num_queues to real created to avoid NULL
> pointer dereference.
>
> Signed-off-by: Joe Jin
Applied.
__
flight 63110 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63110/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62380
build-amd64
flight 63106 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63106/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-build fail REGR. vs. 63022
build-i386-xsm
Il 21/10/2015 14:45, Laszlo Ersek ha scritto:
On 10/21/15 13:39, Stefano Stabellini wrote:
Empty cdroms are not going to connect, avoid waiting for the backend to
switch to state 4, which is never going to happen, and return
error instead from XenPvBlockFrontInitialization(). Detect an
empty cdr
flight 63105 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/63105/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 60684
build-amd6
On Wed, 2015-10-21 at 13:10 +0100, Wei Liu wrote:
> There is no need to explicitly ask for 700.
Is the rationale for 0700 explicitly not that the files in here will
contain possibly sensitive date from guest memory?
i.e. the use of something other than the default is deliberate.
If you think tha
On Wed, 2015-10-21 at 14:15 +0100, Ian Campbell wrote:
> /home/xen/git qemu-xen.git#staging
> xen-stag...@lists.xensource.com xen-de...@lists.xensource.com
> /home/xen/git qemu-xen.git#staging-4.6
> xen-stag...@lists.xensource.com xen-de...@lists.xensource.co
This run is configured for baseline tests only.
flight 38183 qemu-upstream-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38183/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-midway 16 gu
1 - 100 of 162 matches
Mail list logo
