flight 94457 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94457/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
flight 94448 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94448/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 93989
build-amd64-libvi
flight 94464 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94464/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
flight 94456 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94456/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
Hi Doug,
Do you happen to know if Xen has an existing mechanism to make
/dev/xen/xenbus as a default device for xenstored?
On Sun, May 15, 2016 at 11:30 PM, Dagaen Golomb wrote:
>> > Hi All,
>> >
>> > I'm having an interesting issue. I am working on a project that
>> > requires m
Hi,all:
I also met this problem when passthrough 82599 to domU by SRIOV, and the call
stack as follows:
(XEN) Xen call trace:
(XEN)[] panic+0xc3/0x1a0
(XEN)[] symbols_lookup+0x22/0x2a0
(XEN)[] syscall_enter+0x88/0x8d
(XEN)[] syscall_enter+0x88/0x8d
(XEN)[] __print_symbol+0x8a/
> > Hi All,
> >
> > I'm having an interesting issue. I am working on a project that
> > requires me to share memory between dom0 and domUs. I have this
> > successfully working using the grant table and the XenStore to
> > communicate grefs.
> >
> > My issue is this.
On Sun, May 15, 2016 at 9:41 PM, Dagaen Golomb wrote:
>> On 5/15/16 8:28 PM, Dagaen Golomb wrote:
On 5/15/16 11:40 AM, Dagaen Golomb wrote:
> Hi All,
>
> I'm having an interesting issue. I am working on a project that
> requires me to share memory between dom0 and domUs. I hav
As you suggested, I used xen 4.7.0-rc2 to test it again and the problem
still exists.
$ sudo xl create xen-config/win7
> Parsing config from xen-config/win7
> libxl: error: libxl_device.c:1033:device_backend_callback: unable to add
> device with path /local/domain/0/backend/vbd/1/51712
> libxl: er
flight 94442 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94442/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 94368
test-amd64-i386-qemu
> On 5/15/16 8:28 PM, Dagaen Golomb wrote:
>>> On 5/15/16 11:40 AM, Dagaen Golomb wrote:
Hi All,
I'm having an interesting issue. I am working on a project that
requires me to share memory between dom0 and domUs. I have this
successfully working using the grant table and th
On 5/15/16 8:28 PM, Dagaen Golomb wrote:
>> On 5/15/16 11:40 AM, Dagaen Golomb wrote:
>>> Hi All,
>>>
>>> I'm having an interesting issue. I am working on a project that
>>> requires me to share memory between dom0 and domUs. I have this
>>> successfully working using the grant table and the XenSto
> On 5/15/16 11:40 AM, Dagaen Golomb wrote:
> > Hi All,
> >
> > I'm having an interesting issue. I am working on a project that
> > requires me to share memory between dom0 and domUs. I have this
> > successfully working using the grant table and the XenStore to
> > communicate grefs.
> >
> > My is
On 5/15/16 11:40 AM, Dagaen Golomb wrote:
> Hi All,
>
> I'm having an interesting issue. I am working on a project that
> requires me to share memory between dom0 and domUs. I have this
> successfully working using the grant table and the XenStore to
> communicate grefs.
>
> My issue is this. I h
On 2016-05-12 21:02, Wei Liu wrote:
Hi Steven
On Mon, May 09, 2016 at 02:22:48PM +1000, Steven Haigh wrote:
On 2016-05-05 15:52, Steven Haigh wrote:
>On 2016-05-05 12:32, Steven Haigh wrote:
>>Overview
>>
>>If you're using iSCSI, you can mount a target by multiple Dom0
>>machines on the same ta
branch xen-4.5-testing
xenbranch xen-4.5-testing
job build-armhf-libvirt
testid libvirt-build
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and r
flight 94449 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94449/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
Vcpu flags are checked and cleared atomically. Performance can be
improved with corresponding non-atomic versions since schedule.c
already has spin_locks in place.
Signed-off-by: Tianyang Chen
---
xen/common/sched_rt.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
dif
No functional change:
-Various coding style fix
-Added comments for UPDATE_LIMIT_SHIFT.
Signed-off-by: Tianyang Chen
---
xen/common/sched_rt.c | 106 ++---
1 file changed, 56 insertions(+), 50 deletions(-)
diff --git a/xen/common/sched_rt.c b/xen/c
The first part of this patch series aims at fixing coding syle issue
for control structures. Because locks are grabbed in schedule.c before
hooks are called, underscores in front of function names are removed.
The second part replaces atomic bit-ops with non-atomic ones since locks
are grabbed in
> Hi All,
>
> I'm having an interesting issue. I am working on a project that
> requires me to share memory between dom0 and domUs. I have this
> successfully working using the grant table and the XenStore to
> communicate grefs.
>
> My issue is this. I have one domU
flight 94450 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
Hi All,
I'm having an interesting issue. I am working on a project that
requires me to share memory between dom0 and domUs. I have this
successfully working using the grant table and the XenStore to
communicate grefs.
My issue is this. I have one domU running
flight 94398 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94398/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 93932
build-i386-libvir
On Sun, May 15, 2016 at 3:54 PM, Dagaen Golomb wrote:
>>> Hi All,
>>>
>>> I'm having an interesting issue. I am working on a project that
>>> requires me to share memory between dom0 and domUs. I have this
>>> successfully working using the grant table and the XenStore to
>>> communicate grefs.
>>
flight 94443 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94443/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
flight 94417 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94417/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
>>> I'm having an interesting issue. I am working on a project that
>>> requires me to share memory between dom0 and domUs. I have this
>>> successfully working using the grant table and the XenStore to
>>> communicate grefs.
>>>
>>> My issue is this. I have one domU running Ubuntu 12.04 with a def
>> Hi All,
>>
>> I'm having an interesting issue. I am working on a project that
>> requires me to share memory between dom0 and domUs. I have this
>> successfully working using the grant table and the XenStore to
>> communicate grefs.
>>
>> My issue is this. I have one domU running Ubuntu 12.04 wi
flight 94384 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94384/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 93989
build-amd64-libvi
branch xen-4.6-testing
xenbranch xen-4.6-testing
job build-amd64-libvirt
testid libvirt-build
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.gi
flight 94430 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94430/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
flight 94428 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94428/
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 15/05/16 17:40, Dagaen Golomb wrote:
> Hi All,
>
> I'm having an interesting issue. I am working on a project that
> requires me to share memory between dom0 and domUs. I have this
> successfully working using the grant table and the XenStore to
> communicate grefs.
>
> My issue is this. I have
Hi All,
I'm having an interesting issue. I am working on a project that
requires me to share memory between dom0 and domUs. I have this
successfully working using the grant table and the XenStore to
communicate grefs.
My issue is this. I have one domU running Ubuntu 12.04 with a default
3.8.x ker
flight 94396 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94396/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
flight 94368 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94368/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-pair 4 host-install/dst_host(4) broken in 94281 pass in 94368
test-armhf-armhf-libvirt-raw 3 ho
This run is configured for baseline tests only.
flight 44418 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44418/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm
On Fri, May 13, 2016 at 02:36:18PM -0600, Jim Fehlig wrote:
> On 05/10/2016 04:06 AM, Stefano Stabellini wrote:
> > On Mon, 9 May 2016, Wei Liu wrote:
> >> On Thu, Apr 28, 2016 at 03:20:46PM -0600, Jim Fehlig wrote:
> >>> qemu commit 91a097e7 forbids specifying cache mode for empty
> >>> drives. At
On 15/05/16 15:25, Big Strong wrote:
> Hi,
>
> I've configured xen 4.6.0 with xsm enabled and use the default flask
> policy to boot the dom0.
For issues like this, please always use the latest stable branch, in
this case making that Xen 4.6.1+. It is entirely possible that bugfixes
have been bac
flight 94389 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94389/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 3 host-install(3) broken REG
Hi,
I've configured xen 4.6.0 with xsm enabled and use the default flask policy
to boot the dom0.
However, when I tried to create a domU, it will fail for following reasons:
>
> (XEN) avc: denied { send } for domid=0 scontext=system_u:system_r:dom0_t
> tcontext=system_u:system_r:dom0_t tclass=e
flight 94390 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94390/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen 4f6aea066fe2cf3bf4929d6dac1e558071566f73
baseline version:
xen c79fc6c4bee28b4094
flight 94317 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94317/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 93932
build-i386-libvir
flight 94364 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94364/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 65543
build-amd64
flight 94338 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94338/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 94142
Tests which did not succe
flight 94335 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94335/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 3 host-install(3) broken REG
flight 94290 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94290/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 93989
build-amd64-libvi
48 matches
Mail list logo
