This run is configured for baseline tests only.
flight 68262 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68262/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install f
flight 68263 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68263/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-armhf-jessie-netboot-pygrub 14 guest-start/debian.repeat fail
REGR. v
On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote:
> On 12/22/2016 11:44 AM, Roger Pau Monne wrote:
> > On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote:
> > On 22.12.16 at 17:17, wrote:
> >>> On 12/22/2016 07:17 AM, Roger Pau Monne wrote:
> Maybe Boris has some i
On Thu, Dec 22, 2016 at 07:44:19AM -0800, Alistair Francis wrote:
> On Thu, Dec 22, 2016 at 2:54 AM, Wei Liu wrote:
> > On Tue, Dec 20, 2016 at 11:47:00AM -0800, Alistair Francis wrote:
> >> To avoid build errors related to missing file 'sys/sysctl.h' by removing
> >> the #include statement.
> >>
flight 103803 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103803/
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 9 debian-hvm-install
fail REGR. vs. 103466
On Fri, Dec 23, 2016 at 11:16:58AM +0800, Zhang Chen wrote:
[...]
> >>+
> >Here, as I understand it, read can return incomplete message. For
> >example, when the buffer is not big enough.
> >
> >And the inner loop in original code handles that by checking if there is
> >"\r\n". If not, it will read
Having them in StdGNU.mk would affect both hypervisor and tools build.
However judging from the commit message of e4cdd74f LTO was only meant
to affect hypvervisor build.
Move the relevant bits to xen/Rules.mk.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc:
Wei Liu (2):
build: move debug{,_symbols} to tools/Rules.mk
build: use debug_symbols to add -g3
Config.mk | 9 -
tools/Rules.mk | 10 +-
2 files changed, 9 insertions(+), 10 deletions(-)
--
2.1.4
___
Xen-devel mailing list
31d41d7b tried to make debug affect tools build only but failed to take
care of debug_symbols (which appends "-g" to CFLAGS).
Move both to tools/Rules.mk at once in this patch.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek
While doing archeology I found 38ce7ce3, we should also make sure
debug_symbols is the responsible for adding "-g" to CFLAGS.
Move adding "-g3" from being guarded by debug to being guarded by
debug_symbols.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ja
On December 22, 2016 4:12 PM, Jan Beulich wrote:
On 21.12.16 at 06:44, wrote:
>> --- a/xen/arch/x86/hvm/vmx/intr.c
>> +++ b/xen/arch/x86/hvm/vmx/intr.c
>> @@ -315,9 +315,13 @@ void vmx_intr_assist(void)
>> * Set eoi_exit_bitmap for periodic timer interrup to cause
>EOI-induced VM
>>
Having them in StdGNU.mk would affect both hypervisor and tools build.
However judging from the commit message of e4cdd74f LTO was only meant
to affect hypvervisor build.
Move the relevant bits to xen/Rules.mk.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc:
On Fri, Dec 23, 2016 at 12:24:17PM +, Wei Liu wrote:
> Having them in StdGNU.mk would affect both hypervisor and tools build.
> However judging from the commit message of e4cdd74f LTO was only meant
> to affect hypvervisor build.
>
> Move the relevant bits to xen/Rules.mk.
>
Ah, git send-ema
Hello,
I've been looking into the STAO specification[0], because I think it would also
be useful for x86 PVHv2 Dom0, but I'm not really sure how is Xen supposed to
use it.
Xen doesn't have an AML parser, so I'm not sure how is it supposed to guess
the name of the devices it wants to hide from Dom
On Thu, Dec 22, 2016 at 05:07:58PM -0300, Ing. Ricardo Brisighelli wrote:
> Hi my name is Richard and i suscribe to this list but dont know if this list
> is for reports bugs.
>
Yes. Please read
https://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen
Wei.
> Tnks
>
> __
Anyone an idea why I have additional stale Xenstore entries each time
I've started a new domU with a stubdom? After 4 such starts I have:
vm = ""
-0100--fd7f-489bdb5a = ""
memory = "6651"
-0100--fc7f-48dbe98a = ""
memory = "6651"
-0100--ff7f-4
flight 103807 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103807/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail like 103767
test-amd64-amd64-xl-rtds
Hello Xen Devel,
We encountered an issue with one of our instances pushing a lot of
(network) data, resulting in incorrect bandwidth reporting. We do poll
interface traffic every 5 minutes for every interface of our instances
(from Dom0) and store those values for reporting/graphing. At some poin
flight 103842 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103842/
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 1
flight 103802 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103802/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 16 guest-start.2 fail in 103790 REGR. vs. 103769
Tests which are
On 12/23/2016 05:27 AM, Roger Pau Monne wrote:
> On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote:
>> On 12/22/2016 11:44 AM, Roger Pau Monne wrote:
>>> On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote:
>>> On 22.12.16 at 17:17, wrote:
> On 12/22/2016 07:17 AM, Ro
On Fri, Dec 23, 2016 at 10:27:46AM +, Roger Pau Monne wrote:
> On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote:
> > On 12/22/2016 11:44 AM, Roger Pau Monne wrote:
> > > On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote:
> > > On 22.12.16 at 17:17, wrote:
> > >>> O
> But this still assumes that dom0 handles ACPI event for a pCPUs as well,
> right? And I am not sure this can work.
>
> Actually, how do we hotplug pCPUs now?
xen-hptool
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-deve
On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote:
>> But this still assumes that dom0 handles ACPI event for a pCPUs as well,
>> right? And I am not sure this can work.
>>
>> Actually, how do we hotplug pCPUs now?
> xen-hptool
Yes, but this has nothing to do with an actual pCPU being hot-plugge
flight 103800 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103800/
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-
On 23/12/16 15:24, Mart van Santen wrote:
> Hello Xen Devel,
>
> We encountered an issue with one of our instances pushing a lot of
> (network) data, resulting in incorrect bandwidth reporting. We do poll
> interface traffic every 5 minutes for every interface of our instances
> (from Dom0) and st
On Fri, Dec 23, 2016 at 10:35:10AM -0500, Boris Ostrovsky wrote:
> On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote:
> >> But this still assumes that dom0 handles ACPI event for a pCPUs as well,
> >> right? And I am not sure this can work.
> >>
> >> Actually, how do we hotplug pCPUs now?
> > xen
Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version have the
same problem.
My cpu is AMD A10-7860K
I run VM as PVlinux, then try migrate to other server (same hardware) and dont
work, same occurs when try restore a saved VM, but this works well (migrate
and restore) if run VM
flight 103805 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103805/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-migrupgrade 3 host-install/src_host(3) broken in 103791 pass
in 103805
test-amd64-amd64-li
On 23/12/16 16:32, Ing. Ricardo Brisighelli wrote:
Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version have the
same problem.
My cpu is AMD A10-7860K
This issue has been reported before ("[Xen-devel] "X86_PV_VCPU_MSRS
record truncated" during domain restore").
I submitted p
On 12/23/2016 11:02 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, Dec 23, 2016 at 10:35:10AM -0500, Boris Ostrovsky wrote:
>> On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote:
But this still assumes that dom0 handles ACPI event for a pCPUs as well,
right? And I am not sure this can work.
Hey,
I was trying ACPI suspend/resume for testing some patches to Xen, on a
box on which I'm 100% sure I've seen it working a few time back.
Right now, suspending seems ok, but upon resuming, this is what I see
(and after that, everything is just locked):
[ 132.790494] smpboot: CPU 15 is now of
On 23/12/16 17:00, Andrew Cooper wrote:
On 23/12/16 16:32, Ing. Ricardo Brisighelli wrote:
Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version
have the
same problem.
My cpu is AMD A10-7860K
This issue has been reported before ("[Xen-devel] "X86_PV_VCPU_MSRS
record truncated
On 12/23/2016 12:16 PM, Dario Faggioli wrote:
> Hey,
>
> I was trying ACPI suspend/resume for testing some patches to Xen, on a
> box on which I'm 100% sure I've seen it working a few time back.
>
> Right now, suspending seems ok, but upon resuming, this is what I see
> (and after that, everything
On Fri, 2016-12-23 at 12:34 -0500, Boris Ostrovsky wrote:
> On 12/23/2016 12:16 PM, Dario Faggioli wrote:
> > [ 132.790494] smpboot: CPU 15 is now offline
> > [ 132.797383] ACPI: Low-level resume complete
> > [ 132.801635] PM: Restoring platform NVS memory
> > [ 142.805036] Kernel panic - not s
Hello Guys,
I've having some trouble on a new system I'm setting up. I'm getting a kernel
BUG message, seems to be related with the use of Xen (when I boot the system
_without_ Xen, I don't get any crash).
Here is configuration :
- 3x Hard Drives running on RAID 5 Software raid created by mdadm
flight 103812 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103812/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail in 103796
pass in 103812
test-amd64-i386-
flight 103818 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103818/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail like 103797
test-amd64-i386-xl-qemuu-w
Hey Wei,
Sorry about the top post but I’m doing this from my phone.
That sounds good to me, you can use that commit message.
Thanks,
Alistair
From: Wei Liu
Sent: Friday, 23 December 2016 6:12 AM
To: Alistair Francis
Cc: Wei Liu; Doug Goldstein; ian.jack...@eu.citrix.com; imhy.y...@gmail.com;
El Vie 23 Dic 2016 17:16:32 Andrew Cooper escribió:
> On 23/12/16 17:00, Andrew Cooper wrote:
> > On 23/12/16 16:32, Ing. Ricardo Brisighelli wrote:
> >> Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version
> >> have the
> >> same problem.
> >>
> >> My cpu is AMD A10-7860K
> >
> >
On 23/12/16 22:56, Ing. Ricardo Brisighelli wrote:
El Vie 23 Dic 2016 17:16:32 Andrew Cooper escribió:
On 23/12/16 17:00, Andrew Cooper wrote:
On 23/12/16 16:32, Ing. Ricardo Brisighelli wrote:
Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version
have the
same problem.
My cpu
flight 103827 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103827/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-checkfail like 103479
test-armhf-armhf-libvirt-qcow2 1
This run is configured for baseline tests only.
flight 68264 xen-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68264/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-i386-pvgrub 6 xen-boot
flight 103840 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103840/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 9 debian-di-installfail REGR. vs. 103394
Regressions which
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-pair
testid xen-boot/src_host
Tree: linux
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional
This run is configured for baseline tests only.
flight 68265 xen-4.4-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68265/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop
flight 103847 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103847/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pygrub 9 debian-di-installfail REGR. vs. 103807
Regressions whi
flight 103832 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103832/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 101737
test-amd64-amd64-xl-m
This run is configured for baseline tests only.
flight 68266 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68266/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pair 11 host-ping-check-x
49 matches
Mail list logo
