On 04.12.2015 at 2:55pm, wrote:
> >>> "Tian, Kevin" 12/04/15 2:49 AM >>>
> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> Sent: Thursday, December 03, 2015 9:16 PM
> >> >>> On 03.12.15 at 09:09, wrote:
> >> > If impacted domain is Dom0 or hardware domain, just throw out a
> warning.
>
flight 65364 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65364/
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. 65329
Reg
> Hardware is a SuperMicro X10SAT motherboard
> (http://www.supermicro.com/products/motherboard/Xeon/C220/X10SAT.cfm),
> with AMI v3 BIOS + "UEFI support"
>
> Two issues exist with the SuperMicro EFI
>
> (1) firmware EFI mis-mapping causing Xen PANIC on restart
> (2) EFI variables not persistent ac
flight 65361 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65361/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-qemut
This run is configured for baseline tests only.
flight 38447 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38447/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 6e3e562c9d3f3737b718b5be9c9a64e98784890b
baseline version:
ovm
I run Xen 4.6 Dom0 on an Opensuse Leap 42.1 server.
Hardware is a SuperMicro X10SAT motherboard
(http://www.supermicro.com/products/motherboard/Xeon/C220/X10SAT.cfm),
with AMI v3 BIOS + "UEFI support"
Two issues exist with the SuperMicro EFI
(1) firmware EFI mis-mapping causing Xen P
On 12/04/15 03:59, Paul Durrant wrote:
>> -Original Message-
>> From: Don Slutz [mailto:don.sl...@gmail.com]
>> Sent: 04 December 2015 00:23
>> To: Paul Durrant; xen-devel@lists.xen.org
>> Cc: Jun Nakajima; Wei Liu; Kevin Tian; Keir (Xen.org); Ian Campbell; George
>> Dunlap; Andrew Cooper;
This run is configured for baseline tests only.
flight 38429 xen-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38429/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 3 host-ins
On Wed, Dec 2, 2015 at 10:41 AM, Jan Beulich wrote:
> >>> On 02.12.15 at 16:37, wrote:
> > On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote:
> >
> > On 02.12.15 at 16:04, wrote:
> >>> I have attached the output from 'xl dmesg' with iommu=debug
> >>> apic_verbosity=debug loglvl=all
> >>
> >>
flight 65359 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65359/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 6e3e562c9d3f3737b718b5be9c9a64e98784890b
baseline version:
ovmf e04671e81a7fe842f640a926171048e5524
Hi,
We're a team of three fourth-year undergraduate software engineering
students at the University of Waterloo in Canada. We're in the process
of planning for our capstone design project, and are interested in
contributing to Xen. Ideally, we'd like to take on a hypervisor/kernel
hacking proje
flight 65355 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65355/
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 15
guest-localmigrate/x10 fail REGR. vs. 6
This run is configured for baseline tests only.
flight 38431 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38431/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
Commit d2e5538b1 changes virDomainDef to include ifnames
that autogenerated by libxl, and that are also cleared
on domain cleanup. One place that's missing is on
migration, when domain xml is sent to dst libvirtd and
would contain ifnames from the source libvirtd. This
would lead to erronous behavi
This allows a user in non-standalone mode to make a whole new test
database, which is largely a clone of the original database.
The new db refers to the same resources (hosts), and more-or-less
safely borrows some of those hosts.
Currently we don't do anything about the queue and owner daemons.
T
This allows us to execute only the first SQL
invocations. The first non-executed one is dumped, instead, by having
get_psql_command print a rune involving ./mg-debug-fail (which the
caller will then execute).
The locking makes things work roughly-correctly if get_psql_cmd is run
in multiple proc
We arrange for the test configuration to look for the daemons on a
different host and port, and we provide a convenient way to run such a
pair of daemons.
Signed-off-by: Ian Jackson
---
mg-schema-test-database | 57 ++-
1 file changed, 56 insertions(
If the socket setup fails, this makes it easier to see what the
program was trying to do.
Signed-off-by: Ian Jackson
---
tcl/daemonlib.tcl |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tcl/daemonlib.tcl b/tcl/daemonlib.tcl
index 972b5e2..b76ff12 100644
--- a/tcl/daemonli
Instead, expect the user to provide ~/.pgpass.
This is a good idea because we don't really want to be handling
passwords ourselves if we can help it. And, we are shortly going to
want to do some exciting mangling of the database access
configuration, which would be complicated by the presence of
Signed-off-by: Ian Jackson
---
mg-debug-fail | 13 +
1 file changed, 13 insertions(+)
create mode 100755 mg-debug-fail
diff --git a/mg-debug-fail b/mg-debug-fail
new file mode 100755
index 000..64fa235
--- /dev/null
+++ b/mg-debug-fail
@@ -0,0 +1,13 @@
+#!/bin/sh
+#
+# This sc
Move this oddity (and the associated comment) from
standalone-generate-dump-flight-runvars to cri-getconfig. We are
going to want it elsewhere.
We put this in cri-getconfig because that is the one library of
generic shell functions which everything includes. Perhaps this file
is misnamed.
No ov
This will makes it available to a wider subset of the script, which is
going to be important in a moment.
No functional change.
Signed-off-by: Ian Jackson
---
mg-schema-test-database | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/mg-schema-test-database b/mg-
This is for (non-standalone-mode) shell scripts which want to access
the postgresql database.
get_psql_command provides `-v ON_ERROR_STOP' because it is not the
default (!) and no sane caller would not want it.
No callers as yet.
Signed-off-by: Ian Jackson
---
cri-getconfig | 31
I'm intending to be able to do database schema updates. But I don't
want to play around with such code on a live database. So I need a
test database.
Thus, a yak: arrangements to make a test database.
I have tested this and it now does the right things in, apparently,
the right order, and seems
When stdin is a tty, do not try to dump it.
Signed-off-by: Ian Jackson
---
mg-debug-fail |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/mg-debug-fail b/mg-debug-fail
index 64fa235..ffe9f50 100755
--- a/mg-debug-fail
+++ b/mg-debug-fail
@@ -3,10 +3,10 @@
# This sc
No functional change; no callers as yet.
Signed-off-by: Ian Jackson
---
Osstest.pm |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Osstest.pm b/Osstest.pm
index 95e4d46..20b8f62 100644
--- a/Osstest.pm
+++ b/Osstest.pm
@@ -30,7 +30,7 @@ BEGIN {
@ISA =
On 12/04/2015 05:28 PM, Joao Martins wrote:
> Commit d2e5538b1 changes virDomainDef to create ifnames
> that are autogenerated by libxl, and also clearing them up
> on domain cleanup. One place that was missing was also
> on migration, when domain xml is sent to dst libvirtd and
> would contain ifn
On 04/12/15 16:31, Jan Beulich wrote:
> I noticed Linux 4.4 doing this universally now, and I think it's a good
> idea to override such anti-security BIOS settings (we certainly have no
> compatibility problem due to NX being enabled).
I had a plan to do the same, so definitely +1.
>
> Secondary
Hi everyone,
I am pleased to inform you that ARM will host the 2016 Hackathon at their site
in Cambridge, UK. The Hackathon will take place April 18 & 19. I will put
together more information (wiki, blog posts, ...) in the new year!
Best Regards
Lars
__
Commit d2e5538b1 changes virDomainDef to create ifnames
that are autogenerated by libxl, and also clearing them up
on domain cleanup. One place that was missing was also
on migration, when domain xml is sent to dst libvirtd and
would contain ifnames from the source libvirtd. This
would lead to erro
On 04/12/15 16:29, Jan Beulich wrote:
> The previous variant didn't work for non-contiguous socket numbers.
>
> Reported-by: Ed Swierk
> Signed-off-by: Jan Beulich
> Tested-by: Ed Swierk
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-deve
flight 65352 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65352/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 5 kernel-build fail REGR. vs. 60684
test-amd64
On 12/03/2015 12:18 PM, Joao Martins wrote:
>
> On 12/02/2015 11:27 PM, Jim Fehlig wrote:
>> On 11/10/2015 08:32 AM, Joao Martins wrote:
>>> Introduce support for VIR_MIGRATE_PEER2PEER in libxl driver
>>> for supporting migration in Openstack. Most of the changes
>>> occur at the source and no modi
>>> On 04.12.15 at 16:55, wrote:
> I'm having a problem with an Xen 4.6.0 install on debian jessie 8.2 with
> kernel 4.1.13.
> Different domU's has been unexpectedly rebooted several times.
> DomU's runs debian squeeze and wheezy with 4.1.13 kernel.
This ...
> [235243.886902] RIP: e030:[] []
>
I noticed Linux 4.4 doing this universally now, and I think it's a good
idea to override such anti-security BIOS settings (we certainly have no
compatibility problem due to NX being enabled).
Secondary changes:
- no need to check supported extended CPUID level for leaves 8000
and 8001 (r
The previous variant didn't work for non-contiguous socket numbers.
Reported-by: Ed Swierk
Signed-off-by: Jan Beulich
Tested-by: Ed Swierk
--- a/xen/arch/x86/mpparse.c
+++ b/xen/arch/x86/mpparse.c
@@ -89,19 +89,14 @@ void __init set_nr_cpu_ids(unsigned int
void __init set_nr_sockets(void)
On 12/04/2015 10:52 AM, Vitaly Kuznetsov wrote:
Boris Ostrovsky writes:
On 12/04/2015 10:24 AM, David Vrabel wrote:
On 04/12/15 14:06, David Vrabel wrote:
On 03/12/15 10:43, David Vrabel wrote:
Adding the rtc platform device when there are no legacy irqs (no
legacy PIC) causes a conflict wi
flight 65353 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65353/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR.
vs. 63340
test-amd64-i386-l
Hi,
I'm having a problem with an Xen 4.6.0 install on debian jessie 8.2 with
kernel 4.1.13.
Different domU's has been unexpectedly rebooted several times.
DomU's runs debian squeeze and wheezy with 4.1.13 kernel.
Then yesterday a domU (debian squeeze) crashed with following trace in
xl dmesg:
On Thu, 3 Dec 2015, Jianzhong,Chang wrote:
> From: jianzhong,Chang
>
> Add pci = [ '$VF_BDF', '$VF_BDF', '$VF_BDF'] in
This is a bit confusing: it is not actually correct to assign the same
device, even an SR_IOV VF, multiple times, so these must be all
different. More like:
pci = [ '$VF_BDF1',
flight 65346 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65346/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail baseline
untested
test-armhf-armhf-xl
Boris Ostrovsky writes:
> On 12/04/2015 10:24 AM, David Vrabel wrote:
>> On 04/12/15 14:06, David Vrabel wrote:
>>> On 03/12/15 10:43, David Vrabel wrote:
Adding the rtc platform device when there are no legacy irqs (no
legacy PIC) causes a conflict with other devices that end up using
On Thu, 3 Dec 2015, Ian Campbell wrote:
> 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
On 12/04/2015 10:24 AM, David Vrabel wrote:
On 04/12/15 14:06, David Vrabel wrote:
On 03/12/15 10:43, David Vrabel wrote:
Adding the rtc platform device when there are no legacy irqs (no
legacy PIC) causes a conflict with other devices that end up using the
same irq number.
An alternative is
Turning on set -x generally in this script is too verbose, so run the
command in a subshell which sets -x.
Signed-off-by: Ian Campbell
---
v2: Use set -x in a sub shell
---
standalone | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/standalone b/standalone
index c804b74..499cb
On Thu, 3 Dec 2015, Ian Campbell wrote:
> 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
On Thu, 3 Dec 2015, Ian Campbell wrote:
> diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h
> index 2cadd4f..8fbaf07 100644
> --- a/include/hw/xen/xen_common.h
> +++ b/include/hw/xen/xen_common.h
> @@ -41,6 +41,7 @@ static inline void *xc_map_foreign_bulk(int xc_handle,
> uint
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/processor_idle.c:64: null expansion of name
pattern "\1"
ctags:
On Fri, 2015-12-04 at 15:14 +, Stefano Stabellini wrote:
> On Fri, 4 Dec 2015, Ian Campbell wrote:
> > On Fri, 2015-12-04 at 14:43 +, Stefano Stabellini wrote:
> > > On Fri, 4 Dec 2015, Ian Campbell wrote:
> > > > Stefano, Anthony: The debian-di-install failure has "error: Unknown
> > > > d
On 04/12/15 14:06, David Vrabel wrote:
> On 03/12/15 10:43, David Vrabel wrote:
>> Adding the rtc platform device when there are no legacy irqs (no
>> legacy PIC) causes a conflict with other devices that end up using the
>> same irq number.
>
> An alternative is to remove the rtc_cmos platform de
On Fri, 4 Dec 2015, Ian Campbell wrote:
> On Fri, 2015-12-04 at 14:43 +, Stefano Stabellini wrote:
> > On Fri, 4 Dec 2015, Ian Campbell wrote:
> > > Stefano, Anthony: The debian-di-install failure has "error: Unknown
> > > driver
> > > 'vhd'" in the qemu-log. It turns out this has previously be
Ian Campbell writes ("[PATCH OSSTEST] cr-try-bisect-adhoc: Set
OSSTEST_PRIORITY=-30"):
> This makes adhoc bisects slightly more important than smoke tests, on
> the basis that a smoke test can choose another host while an adhoc
> bisect cannot.
Acked-by: Ian Jackson
Ian Campbell writes ("Re: [PATCH OSSTEST] standalone: Log things we are running
via with_logging"):
> On Thu, 2015-12-03 at 16:41 +, Ian Jackson wrote:
> > It's not clear to me from the context whether $@ might contain things
> > which would require quoting.
...
> Are you worried about things
Ian Campbell writes ("Re: [libvirt test] 65324: regressions - FAIL"):
> See which went to
> xen-devel + osstest-output but for some reason is in
That message had a complete git log of all the changes being merged,
so was massive. Now there is a length limit.
Ian.
__
On Fri, 2015-12-04 at 14:43 +, Stefano Stabellini wrote:
> On Fri, 4 Dec 2015, Ian Campbell wrote:
> > Stefano, Anthony: The debian-di-install failure has "error: Unknown
> > driver
> > 'vhd'" in the qemu-log. It turns out this has previously been bisected
> > and
> > blamed on:
> >
> > comm
Ian Campbell writes ("Re: [OSSTEST PATCH] production-config-cambridge: Use new
squid proxy"):
> Do you want to go pretest in Cambridge then merge back to colo or do you
> want to push it to the colo and let it flow through in time?
I don't care all that much.
Ian.
__
On 04/12/15 14:01, Ross Lagerwall wrote:
> Commit fc0c3fa2ad5c ("x86/IO-APIC: fix setup of Xen internally used IRQs
> (take 2)") introduced a regression on some hardware where Xen would hang
> during shutdown, repeating the following message:
> APIC error on CPU0: 08(08), Receive accept error
>
> T
>>> On 04.12.15 at 15:07, wrote:
> We need to have at least version 2 since it's the first version to
> support various control and status registers (such as
> MSR_CORE_PERF_GLOBAL_CTRL) that VPMU relies on always having.
>
> We don't fully emulate version 4 but since it's back compatible with
>
On Fri, 4 Dec 2015, Ian Campbell wrote:
> Stefano, Anthony: The debian-di-install failure has "error: Unknown driver
> 'vhd'" in the qemu-log. It turns out this has previously been bisected and
> blamed on:
>
> commit 3fb401edbd8e9741c611bfddf6a2032ca91f55ed
> Merge: a44c280 816609b
> Author:
>>> On 04.12.15 at 15:01, wrote:
> Commit fc0c3fa2ad5c ("x86/IO-APIC: fix setup of Xen internally used IRQs
> (take 2)") introduced a regression on some hardware where Xen would hang
> during shutdown, repeating the following message:
> APIC error on CPU0: 08(08), Receive accept error
>
> This ap
The Xen toolstack uses "vhd" to specify a disk in VHD format, however
the name of the driver in QEMU is "vpc". Replace "vhd" with "vpc", so
that QEMU can find the right driver to use for it.
Signed-off-by: Stefano Stabellini
diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
index 267d8a8..3
On Fri, Dec 04, 2015 at 02:19:33PM +, Ian Campbell wrote:
> On Fri, 2015-12-04 at 10:01 +, Daniel P. Berrange wrote:
> > On Thu, Dec 03, 2015 at 11:13:06PM -0700, Jim Fehlig wrote:
> > > On 11/26/2015 09:59 AM, Ian Campbell wrote:
> > > > libxlConnectDomainXMLFromNative calls both xenParseX
On Fri, 2015-12-04 at 10:01 +, Daniel P. Berrange wrote:
> On Thu, Dec 03, 2015 at 11:13:06PM -0700, Jim Fehlig wrote:
> > On 11/26/2015 09:59 AM, Ian Campbell wrote:
> > > libxlConnectDomainXMLFromNative calls both xenParseXM and xenParseXL
> > > with cfg->verInfo->xen_version_major, however A
We need to have at least version 2 since it's the first version to
support various control and status registers (such as
MSR_CORE_PERF_GLOBAL_CTRL) that VPMU relies on always having.
We don't fully emulate version 4 but since it's back compatible with
earlier versions we can fall back to v3. At th
On Fri, 2015-12-04 at 13:57 +, Ian Jackson wrote:
> Specify both HttpProxy and DebianMirrorProxy. In my tests this seems
> to improve some of the apparently-intercepting-proxy-related failures,
> and it will certainly improve logging.
>
> I set DebianMirrorProxy too so that queries to securit
On 03/12/15 10:43, David Vrabel wrote:
> Adding the rtc platform device when there are no legacy irqs (no
> legacy PIC) causes a conflict with other devices that end up using the
> same irq number.
An alternative is to remove the rtc_cmos platform device in Xen PV
guests.
Any preference on how th
Commit fc0c3fa2ad5c ("x86/IO-APIC: fix setup of Xen internally used IRQs
(take 2)") introduced a regression on some hardware where Xen would hang
during shutdown, repeating the following message:
APIC error on CPU0: 08(08), Receive accept error
This appears to be because an interrupt (in this case
Specify both HttpProxy and DebianMirrorProxy. In my tests this seems
to improve some of the apparently-intercepting-proxy-related failures,
and it will certainly improve logging.
I set DebianMirrorProxy too so that queries to security.d.o go through
the proxy. Ideally we would have a apt cache t
On 04/12/15 11:00, George Dunlap wrote:
> On 03/12/15 16:42, David Vrabel wrote:
>> If a guest allocates a page and the tlbflush_timestamp on the page
>> indicates that a TLB flush of the previous owner is required, only the
>> linear and combined mappings are invalidated. The guest-physical
>> ma
flight 65338 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65338/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 3 host-install(3) broken REGR. vs. 65114
test-amd64-amd64-qem
Hi Stefano:
Can you please add xen/arm in the commit title?
On 04/12/2015 12:36, Stefano Stabellini wrote:
Injecting a fault to the guest just because it is writing to one of the
GICD_ICACTIVER registers, which are part of the GICv2 and GICv3 specs,
is harsh. Additionally it causes recent linux
Injecting a fault to the guest just because it is writing to one of the
GICD_ICACTIVER registers, which are part of the GICv2 and GICv3 specs,
is harsh. Additionally it causes recent linux kernels to fail to boot on
Xen.
Ignore writes to GICD_ICACTIVER ... GICD_ICACTIVERN instead, to solve
the boo
osstest service owner writes ("[xen-4.6-testing test] 65327: regressions -
FAIL"):
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 16
> guest-localmigrate/x10 fail in 65210 REGR. vs. 63449
>
...
>
Jan Beulich writes ("Re: [Xen-devel] [xen-4.6-testing test] 65327: regressions
- FAIL"):
> And indeed I had suggested a force push a number of flights ago,
> but Ian had hoped it would eventually end up running on another
> host, thus allowing a push to happen.
I'm not sure which Ian this is and
This run is configured for baseline tests only.
flight 38427 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38427/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd
On 03/12/15 16:42, David Vrabel wrote:
> From: David Vrabel
>
> Holding the p2m lock while calling ept_sync_domain() is very expensive
> since it does a on_selected_cpus() call. IPIs on many socket machines
> can be very slows and on_selected_cpus() is serialized.
>
> Defer the invalidate until
Dario,
thank you for the feedback.
Does anyone else have any? One item that was raised when I chatted to a few
people was to see whether we can include something like
https://fuzzing-project.org/ or http://lcamtuf.coredump.cx/afl/ into the Xen
Project Test Lab. This may not be quite as easy a
>>> On 04.12.15 at 11:20, wrote:
> On Fri, Dec 04, 2015 at 05:15:28AM +, osstest service owner wrote:
>> flight 65327 xen-4.6-testing real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/65327/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including
On 03/12/15 16:42, David Vrabel wrote:
> If a guest allocates a page and the tlbflush_timestamp on the page
> indicates that a TLB flush of the previous owner is required, only the
> linear and combined mappings are invalidated. The guest-physical
> mappings are not invalidated.
>
> This is curre
On 02/12/15 15:30, Jan Beulich wrote:
On 02.12.15 at 16:09, wrote:
>> On 12/02/2015 02:02 PM, Jan Beulich wrote:
>> On 02.12.15 at 14:46, wrote:
--- a/xen/arch/x86/smp.c
+++ b/xen/arch/x86/smp.c
@@ -286,6 +286,7 @@ void __stop_this_cpu(void)
static void stop_th
On Fri, 2015-12-04 at 09:54 +, Joao Martins wrote:
>
> On 12/04/2015 01:18 AM, osstest service owner wrote:
> > flight 65324 libvirt real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/65324/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > inclu
flight 38428 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38428/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-amd64-jessie-netboot-pygrub 9 debian-di-install fail blocked
in 38362
test-amd
Jim,
FYI, something in 3c7590e0a435..d2e5538b16e3 seems to have broken migrate.
The bisector is working on it at:
http://logs.test-lab.xenproject.org/osstest/results/bisect/libvirt/test-amd64-amd64-libvirt-pair.guest-migrate--src_host--dst_host.html
The build-armhf issue is fixed.
Stefano, Antho
On Fri, Dec 04, 2015 at 05:15:28AM +, osstest service owner wrote:
> flight 65327 xen-4.6-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/65327/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64
Hi,
> btw some questions here:
>
> for non-gl and gl rendering in Qemu, are they based on dma-buf already?
> once we can export guest framebuffer in dma-buf, is there additional work
> required or just straightforward to integrate with SPICE?
Right now we are busy integrating dma-buf support
On 04/12/15 03:21, Carl Patenaude Poulin wrote:
> Hi folks,
>
> On page 12 of "The Definitive Guide to the Xen Hypervisor", it is
> mentioned that "Xen, like Linux, uses the MS-DOS calling convention,
> rather than the UNIX convention used by FreeBSD."
>
> I keep digging online and I can't find any
On Thu, 2015-12-03 at 13:08 -0500, Daniel De Graaf wrote:
> On 03/12/15 06:22, Ian Campbell wrote:
> > In particular around error handling, behaviour on fork and the unmap
> > notification mechanism.
> >
> > Behaviour of xengnttab_map_*grant_refs and xengntshr_share_pages on
> > partial failure ha
On Thu, Dec 03, 2015 at 11:13:06PM -0700, Jim Fehlig wrote:
> On 11/26/2015 09:59 AM, Ian Campbell wrote:
> > libxlConnectDomainXMLFromNative calls both xenParseXM and xenParseXL
> > with cfg->verInfo->xen_version_major, however AFAICT they both (either
> > inherently, or through there use of xenPa
On 12/04/2015 01:18 AM, osstest service owner wrote:
> flight 65324 libvirt real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/65324/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-libvirt-pair 21 g
On Thu, 2015-12-03 at 16:41 +, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST] standalone: Log things we are
> running via with_logging"):
> > Turning on set -x is too verbose, so just echo the command ourselves.
>
> It's not clear to me from the context whether $@ might contain thi
> -Original Message-
> From: Don Slutz [mailto:don.sl...@gmail.com]
> Sent: 04 December 2015 00:23
> To: Paul Durrant; xen-devel@lists.xen.org
> Cc: Jun Nakajima; Wei Liu; Kevin Tian; Keir (Xen.org); Ian Campbell; George
> Dunlap; Andrew Cooper; Stefano Stabellini; Eddie Dong; Don Slutz; Ti
flight 65329 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65329/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-qemut
92 matches
Mail list logo
