flight 58946 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58946/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
flight 58937 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58937/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 9 windows-installfail REGR. vs. 58919
Regressions which are regard
flight 58935 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58935/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are failing
From: Don Slutz
This file: backdoor_def.h comes from:
http://packages.vmware.com/tools/esx/3.5latest/rhel4/SRPMS/index.html
open-vm-tools-kmod-7.4.8-396269.423167.src.rpm
open-vm-tools-kmod-7.4.8.tar.gz
vmhgfs/backdoor_def.h
and is unchanged.
Added the badly named include file includeChe
From: Don Slutz
This is done by adding xen_arch_domainconfig vmware_hw. It is set to
the VMware virtual hardware version.
Currently 0, 3-4, 6-11 are good values. However the
code only checks for == 0 or != 0 or >= 7.
If non-zero then
Return VMware's cpuid leaves. If >= 7 return data, else
This new libxl_domain_create_info field is used to set
XEN_DOMCTL_CONFIG_VMWARE_PORT_MASK in the xc_domain_configuration_t
for x86.
In xen it is is_vmware_port_enabled.
If is_vmware_port_enabled then
enable a limited support of VMware's hyper-call.
VMware's hyper-call is also known as VMware B
Changes v11 to v12:
Rebased on staging.
Jan Beulich (xen: Add ring 3 vmware_port support)
As there don't seem to be enough convincing arguments for this
to be worthwhile, I'm going to drop this...
Dropped the 2 ring3 patches.
Ian Campbell (tools: Add vmware_hwver support):
From: Don Slutz
This includes adding is_vmware_port_enabled
This is a new xen_arch_domainconfig flag,
XEN_DOMCTL_CONFIG_VMWARE_PORT_MASK.
This enables limited support of VMware's hyper-call.
This is both a more complete support then in currently provided by
QEMU and/or KVM and less. The missi
From: Don Slutz
This is used to set xen_arch_domainconfig vmware_hw. It is set to
the emulated VMware virtual hardware version.
Currently 0, 3-4, 6-11 are good values. However the code only
checks for == 0, != 0, or < 7.
Signed-off-by: Don Slutz
CC: Don Slutz
---
v12:
I'm not sure this h
From: Don Slutz
This allows use of QEMU's VMware emulated video card
NOTE: vga=vmware is not supported by device_model_version=qemu-xen-traditional
Signed-off-by: Don Slutz
CC: Don Slutz
---
v12:
Dropped LIBXL_HAVE_LIBXL_VGA_INTERFACE_TYPE_VMWARE
This means that the later patch that defin
From: Don Slutz
This adds synchronization of the 6 vcpu registers (only 32bits of
them) that vmport.c needs between Xen and QEMU.
This is to avoid a 2nd and 3rd exchange between QEMU and Xen to
fetch and put these 6 vcpu registers used by the code in vmport.c
and vmmouse.c
In the tools, enable
From: Don Slutz
Also added missing TRAP_DEBUG & VLAPIC.
Signed-off-by: Don Slutz
Acked-by: Ian Campbell
CC: Don Slutz
---
v12:
Switch VMPORT_IGNORED to port, regs->_eax.
v11:
No change
v10:
Added Acked-by: Ian Campbell
Added back in the trace point calls.
Why is cmd in this pat
flight 58934 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58934/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail like 58904
test-amd64-i386-libvirt-xsm
flight 58933 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58933/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 5
commit 2df1aa01bef7366798248ac6d03cfb42048b003d
Author: Paul Durrant
Date: Tue Jun 23 18:07:49 2015 +0200
x86/hvm: remove hvm_io_pending() check in hvmemul_do_io()
...
-rc = X86EMUL_RETRY;
-if ( !hvm_send_assist_req(s, &p) )
+rc = hvm_send_assist_req(s,
flight 58932 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58932/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 58842
Regressions which are reg
All,
Sorry for the repeated send to the mailing list, I forgot to add some
cc's and wanted to make sure
everyone was included.
This is the new patch that works towards how Dario suggested
structuring the event-driven move.
It uses the previous timer to drive the rt_schedule function, which
enforc
To do this, we create a new list that holds, for each
vcpu, the time least into the future that it may need to be
rescheduled. The scheduler chooses the lowest time off of this
list and waits until the specified time instead of running every
1 ms as it did before.
Signed-off-by: Dagaen Golomb
Sig
To do this, we create a new list that holds, for each
vcpu, the time least into the future that it may need to be
rescheduled. The scheduler chooses the lowest time off of this
list and waits until the specified time instead of running every
1 ms as it did before.
Signed-off-by: Dagaen Golomb
Sig
On 06/26/2015 02:17 PM, Ed White wrote:
> On 06/24/2015 03:29 AM, Andrew Cooper wrote:
>> On 22/06/15 19:56, Ed White wrote:
>>> diff --git a/xen/include/asm-x86/hvm/vcpu.h b/xen/include/asm-x86/hvm/vcpu.h
>>> index 3d8f4dc..a1529c0 100644
>>> --- a/xen/include/asm-x86/hvm/vcpu.h
>>> +++ b/xen/incl
flight 58925 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58925/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail in 58863 REGR.
vs. 58451
Tests
2015-06-25 5:15 GMT-07:00 Dario Faggioli :
> and of (almost every) direct use of cpupool_online_cpumask().
>
> In fact, what we really want for the most of the times,
> is the set of valid pCPUs of the cpupool a certain domain
> is part of. Furthermore, in case it's called with a NULL
> pool as arg
Hi Dario,
A dummy question:
>
> For now, as RTDS is still marked as experimental,
> test failures are allowed, as it is for SEDF.
>
Will I receive the email in cc. list if OSSTest fails?
I want/hope to know when/how the RTDS scheduler fails the test so that
I can also contribute to fix the issu
On 06/23/2015 06:33 PM, Konrad Rzeszutek Wilk wrote:
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.2
in your 'for-4.2/drivers' branch. It is late - for which I am terrible
sorry! The patches have been sitting in
flight 58917 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58917/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
like 58773
test-amd64-i386-x
flight 58919 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58919/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 5
test-amd64-i386-xl-qemuu-win7-amd64 1
I want to use guest's variables on Xen hypervisor.
But I don't know how to do exactly.
First, I was thinking that I could use grant table but grant-table is not
related to this issue(cause grant-table is used inter-domain)
Is there any way to get PV guest's variables? or is there no solution?
flight 58911 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58911/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 58873
Regre
flight 58907 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58907/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are failing
flight 58904 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58904/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail like 58876
test-amd64-i386-libvirt-xsm
flight 58902 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58902/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail REGR. vs. 58793
test-amd64-i386-freebsd10-amd6
flight 58930 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58930/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
32 matches
Mail list logo
