flight 103980 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103980/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 103894
test-armhf-armhf-libvirt-q
On 12/22/16 18:38, Jan Beulich wrote:
On 19.09.16 at 07:52, wrote:
Suravee Suthikulpanit (9):
x86/HVM: Introduce struct hvm_pi_ops
x86/vLAPIC: Declare vlapic_read_aligned() and vlapic_reg_write() as
non-static
x86/HVM: Call vlapic_destroy after vcpu_destroy
x86/SVM: Modify VMCB fiel
On 12/22/16 18:16, Jan Beulich wrote:
On 19.09.16 at 07:52, wrote:
+int svm_avic_init_vcpu(struct vcpu *v)
+{
+struct vlapic *vlapic = vcpu_vlapic(v);
+struct arch_svm_struct *s = &v->arch.hvm_svm;
+
+if ( svm_avic )
+s->avic_bk_pg = vlapic->regs_page;
Why this copying? C
flight 103976 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103976/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64 6 xen-bootfail REGR. vs. 101675
test-amd64-amd64-xl-
Ensure all reserved fields of xatp are zero before making
hypervisor call to XEN in xen_map_device_mmio().
xenmem_add_to_physmap_one() in XEN fails the mapping request if
extra.res reserved field in xatp is not zero for XENMAPSPACE_dev_mmio
request.
Signed-off-by: Jiandi An
---
Changed zeroing xa
flight 103977 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103977/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR.
vs. 103894
Regres
flight 103974 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103974/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 6 xen-bootfail REGR. vs. 101737
test-amd64-amd64-xl
This run is configured for baseline tests only.
flight 68278 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68278/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop
flight 103975 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103975/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-xsm7 host-ping-check-xen fail in 103971 pass in 103975
test-amd64-amd64-xl-qcow2 16 gue
>>> Dario Faggioli 12/23/16 6:18 PM >>>
>[ 142.852159] Call Trace:
>[ 142.854602] [] ? dump_stack+0x5c/0x77
>[ 142.859980] [] ? panic+0xe4/0x226
>[ 142.865004] [] ? dmar_disable_qi+0x108/0x110
>[ 142.870978] [] ? dmar_reenable_qi+0x1e/0x30
>[ 142.876863] [] ? reenable_irq_remapping+0x2f
On 27/12/16 15:53, Jan Beulich wrote:
"Jan Beulich" 12/27/16 4:42 PM >>>
Alistair Francis 12/22/16 8:14 PM >>>
Everyone seems fairly open to an override. Is a environment variable,
which if set will disable Werror acceptable? Something like NO_ERROR=Y
which will result in no -Werror being appe
On 12/27/16 9:53 AM, Jan Beulich wrote:
"Jan Beulich" 12/27/16 4:42 PM >>>
Alistair Francis 12/22/16 8:14 PM >>>
>>> Everyone seems fairly open to an override. Is a environment variable,
>>> which if set will disable Werror acceptable? Something like NO_ERROR=Y
>>> which will result in
>>> "Jan Beulich" 12/27/16 4:42 PM >>>
>>> Alistair Francis 12/22/16 8:14 PM >>>
>>Everyone seems fairly open to an override. Is a environment variable,
>>which if set will disable Werror acceptable? Something like NO_ERROR=Y
>>which will result in no -Werror being appended.
>
>I dislike environm
>>> "Tian, Kevin" 12/23/16 6:48 AM >>>
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, December 22, 2016 11:37 PM
>> >>> On 22.12.16 at 16:14, wrote:
>> > My argument is that, instead of excluding the hook, the behaviour of the
>> > emulation path should be made to function sen
>>> Alistair Francis 12/22/16 8:14 PM >>>
>On Thu, Dec 22, 2016 at 12:41 AM, Jan Beulich wrote:
> On 20.12.16 at 20:46, wrote:
>>> Signed-off-by: Alistair Francis
>>
>> Without some rationale given I don't think such changes are
>> acceptable at all. And then, as already pointed out others,
flight 103973 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103973/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64 6 xen-bootfail REGR. vs. 101675
test-amd64-amd64-xl-
>>> Ian Jackson 12/22/16 8:00 PM >>>
>Jan Beulich writes ("Re: [PATCH] docs: Clarify scope of reboot= and noreboot
>Xen command line options"):
>> On 22.12.16 at 16:02, wrote:
>> > -Specify the host reboot method.
>> > +Specify the host reboot method,
>> > +used when Xen crashes.
>> > +(This doe
We have searched in the last days more and more for the cause of this
performance issue.
In cooperation with the datacenter, we change some hardware to check, if the
problem already proceeds. We put the RAID Controller included all RAID Arrays
to another Supermicro Mainboard: X10SLM-F with only
flight 68277 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68277/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-weekly-netinst-pygrub 9 debian-di-install fail like
68247
test-armhf-
flight 103971 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103971/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-qcow2 10 guest-startfail in 103960 pass in 103971
test-armhf-armhf-xl-xsm 7
flight 103965 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103965/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 6 xen-bootfail REGR. vs. 101737
test-amd64-amd64-xl
21 matches
Mail list logo
