flight 77209 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77209/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 3 host-install(3) broken REGR. vs. 66879
test-amd64-i386-xl-q
Hi Jan,
On 2016/1/7 15:45, Jan Beulich wrote:
On 07.01.16 at 07:58, wrote:
>> > On 2015/11/17 19:04, Jan Beulich wrote:
>> > On 17.11.15 at 10:40, wrote:
> >>> > --- a/xen/arch/arm/mm.c
> >>> > +++ b/xen/arch/arm/mm.c
> >>> > @@ -1138,6 +1138,10 @@ int xenmem_add_to_phys
On Wed, 2016-01-06 at 06:54 +, Gohar Irfan wrote:
> Hi,
>
> Can anyone guide me on how to compile Xen with Infiniband support?
> (Particularly Mellanox)
> I want to perform some RDMA read/write functionality from within the Xen
> code (it is for a course project) using the Verbs API.
Xen its
On Wed, 2016-01-06 at 17:55 +, Stefano Stabellini wrote:
> Please CC linux-arm for the non-RFC patches
>
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > Replace various stub functions with real functionality, including
> > reestablishing the shared info page and the per-vcpu info pages on
> > re
On Wed, 2016-01-06 at 18:28 +, osstest service owner wrote:
> flight 77180 qemu-upstream-4.2-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/77180/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i
On Wed, 2016-01-06 at 19:29 +0100, Tamas K Lengyel wrote:
>
>
> On Wed, Jan 6, 2016 at 4:48 PM, Ian Campbell
> wrote:
> > On Wed, 2015-12-23 at 15:53 +0100, Tamas K Lengyel wrote:
> > > Introduce new vm_event domctl option which allows an event subscriber
> > > to request all vCPUs not currently
On Thu, 2016-01-07 at 07:15 +0100, Juergen Gross wrote:
> On 06/01/16 17:12, Ian Campbell wrote:
> > On Fri, 2015-12-18 at 14:14 +0100, Juergen Gross wrote:
> > > Move xen-init-dom0 from tools/libxl to tools/helpers, as it is just a
> > > helper program.
> > >
> > > Signed-off-by: Juergen Gross
>
On Thu, 2016-01-07 at 06:37 +0100, Juergen Gross wrote:
> On 06/01/16 16:59, Ian Campbell wrote:
> > On Fri, 2015-12-18 at 15:10 +0100, Juergen Gross wrote:
> > > On 18/12/15 14:53, Andrew Cooper wrote:
> > > > On 18/12/15 13:14, Juergen Gross wrote:
> > > > > Add libxl_xenstore_domid() to obtain t
Thanks a lot for the response.
I am not sure if I asked it right: I already have Infiniband installed on
my kernel and it is working fine in the user space. However, I would like
to use the RDMA Verbs API inside the Xen code, like calling RDMA functions
to send/receive data. That requires Infiniba
On 07/01/16 05:41, Haozhong Zhang wrote:
> Hi Wei,
>
> On 01/04/16 10:15, Wei Liu wrote:
> [...]
>> = Projects =
>>
>> == Hypervisor ==
> [...]
>> === x86 ===
> [...]
>> == Toolstack ==
> * vNVDIMM support
> - Haozhong Zhang
>
> This is another item I'm working on and would like to see
CC George (who does the packaging for CentOS)
BTW this problem is better directed to appropriate mailing list of
CentOS (centos-virt? I can't remember the exact name).
Wei.
On Thu, Jan 07, 2016 at 10:53:00AM +0200, Jānis Andersons | Failiem.lv wrote:
> xen_major : 4
> xen_minor
On Thu, Jan 07, 2016 at 11:21:04AM +0100, Juergen Gross wrote:
> On 06/01/16 16:40, Wei Liu wrote:
> > On Wed, Dec 16, 2015 at 10:24:18AM +0100, Juergen Gross wrote:
> > [...]
> >> @@ -698,21 +868,19 @@ static int normalise_pagetable(struct xc_sr_context
> >> *ctx, const uint64_t *src,
> >>
On Thu, 2016-01-07 at 07:52 +0100, Juergen Gross wrote:
> On 06/01/16 17:33, Ian Campbell wrote:
> > On Fri, 2015-12-18 at 15:53 +0100, Juergen Gross wrote:
> > > On 18/12/15 15:42, Andrew Cooper wrote:
> > > > On 18/12/15 13:14, Juergen Gross wrote:
> > > > > When restarting or shutting down dom0
On 07/01/16 11:33, Wei Liu wrote:
> On Thu, Jan 07, 2016 at 11:21:04AM +0100, Juergen Gross wrote:
>> On 06/01/16 16:40, Wei Liu wrote:
>>> On Wed, Dec 16, 2015 at 10:24:18AM +0100, Juergen Gross wrote:
>>> [...]
@@ -698,21 +868,19 @@ static int normalise_pagetable(struct xc_sr_context
*
>>> On 07.01.16 at 10:11, wrote:
> Hi Jan,
>
> On 2016/1/7 15:45, Jan Beulich wrote:
> On 07.01.16 at 07:58, wrote:
>>> > On 2015/11/17 19:04, Jan Beulich wrote:
>>> > On 17.11.15 at 10:40, wrote:
>> >>> > --- a/xen/arch/arm/mm.c
>> >>> > +++ b/xen/arch/arm/mm.c
>> >>> >
On 07/01/16 10:42, Ian Campbell wrote:
> On Wed, 2016-01-06 at 11:44 +, Andrew Cooper wrote:
>> All console logging is synchronous (to ensure that log messages have
>> escaped the VM before an action occurs) and by default, an HVM test will
>> use the qemu debug port, console_io hypercall, and
On Thu, 2016-01-07 at 11:44 +0100, Juergen Gross wrote:
> > > IMO the generic concept you are asking for should be added in a
> > > separate patch handling stopping (and possibly rebooting) driver
> > > domains in a clean way.
> >
> > Since libxl has a stable API once we add something we need to c
On 07/01/16 11:55, Ian Campbell wrote:
> On Thu, 2016-01-07 at 11:44 +0100, Juergen Gross wrote:
IMO the generic concept you are asking for should be added in a
separate patch handling stopping (and possibly rebooting) driver
domains in a clean way.
>>>
>>> Since libxl has a stable A
So this arose because Stefano was unaware that 4.2 was no longer supported.
Neither am I ever confident about where the cut-off lie, e.g. I always have
to ask if I am doing backports for a security issue.
We should add rows to http://wiki.xen.org/wiki/Xen_Release_Features right
under Initial Relea
flight 38599 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38599/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3864 host-build-prep fail REGR. vs. 38576
Tests w
flight 77218 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77218/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 6 xen-bootfail REGR. vs. 59254
test-amd64-i386-xl-qe
>>> On 07.01.16 at 12:22, wrote:
> So this arose because Stefano was unaware that 4.2 was no longer supported.
> Neither am I ever confident about where the cut-off lie, e.g. I always have
> to ask if I am doing backports for a security issue.
>
> We should add rows to http://wiki.xen.org/wiki/Xe
El 06/01/16 a les 21.03, Boris Ostrovsky ha escrit:
> With commit 8c45adec18e0 ("libxc: create unmapped initrd in domain
> builder if supported") location of ramdisk may not be available to
> HVMlite guests by the time alloc_magic_pages_hvm() is invoked if the
> guest supports unmapped initrd.
>
>
>>> On 07.01.16 at 11:21, wrote:
> On 07/01/16 05:41, Haozhong Zhang wrote:
>> Hi Wei,
>>
>> On 01/04/16 10:15, Wei Liu wrote:
>> [...]
>>> = Projects =
>>>
>>> == Hypervisor ==
>> [...]
>>> === x86 ===
>> [...]
>>> == Toolstack ==
>> * vNVDIMM support
>> - Haozhong Zhang
>>
>> This is
On Thu, 2016-01-07 at 04:45 -0700, Jan Beulich wrote:
> > > > On 07.01.16 at 12:22, wrote:
> > So this arose because Stefano was unaware that 4.2 was no longer
> > supported.
> > Neither am I ever confident about where the cut-off lie, e.g. I always
> > have
> > to ask if I am doing backports for
Set the SIF_VIRT_P2M_4TOOLS flag for pv-domUs in the domain builder
to indicate the Xen tools have full support for the virtual mapped
linear p2m list.
This will enable pv-domUs to drop support of the 3 level p2m tree
and use the linear list only. Without setting this flag some kernels
might limit
On Thu, 2016-01-07 at 12:44 +, Lars Kurth wrote:
> > On 7 Jan 2016, at 11:45, Jan Beulich wrote:
> >
> > > > > On 07.01.16 at 12:22, wrote:
> > > So this arose because Stefano was unaware that 4.2 was no longer
> > > supported.
> > > Neither am I ever confident about where the cut-off lie, e
Currently there is no documented wire format for guest receive-side
packets but the location of the 'wire format' comment block suggests
it is the same as transmit-side. This is almost true but there is a
subtle difference in the use of the 'size' field for the first fragment.
For clarity this pat
>>> On 07.01.16 at 13:00, wrote:
> On Thu, 2016-01-07 at 04:45 -0700, Jan Beulich wrote:
>> > > > On 07.01.16 at 12:22, wrote:
>> > So this arose because Stefano was unaware that 4.2 was no longer
>> > supported.
>> > Neither am I ever confident about where the cut-off lie, e.g. I always
>> > hav
On Thu, Jan 07, 2016 at 11:36:08AM +, Ian Campbell wrote:
> On Thu, 2016-01-07 at 12:21 +0100, Juergen Gross wrote:
> > On 07/01/16 11:55, Ian Campbell wrote:
> > > On Thu, 2016-01-07 at 11:44 +0100, Juergen Gross wrote:
> > > > > > IMO the generic concept you are asking for should be added in
On Thu, 2016-01-07 at 13:36 +0100, Juergen Gross wrote:
> Add support for the virtual mapped linear p2m list of pv-domains in the
> v2 migrate stream. This will allow to migrate domains larger than 512
> GB.
>
> Tested with 32- and 64-bit pv-domains both with and without linear p2m
> list and with
On Thu, 2016-01-07 at 10:36 +, Ian Campbell wrote:
> On Thu, 2016-01-07 at 09:25 +0100, Juergen Gross wrote:
> > The new logging library Makefile doesn't support the distclean target.
> > Add it.
> >
> > Also remove all created shared library versions via the clean target.
> >
> > Signed-off-
On Wed, 2016-01-06 at 17:21 +, 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 kernels to fail to boot on
> Xen.
>
> Igno
flight 77225 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77225/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 63071
test-am
> On January 07, 2016 9:28 PM, wrote:
> >>> On 07.01.16 at 02:39, wrote:
> > On January 06, 2016 7:26 PM, wrote:
> >> > I didn't think about the full logic thoroughly now. But it would
> >> > always be good to not hide device now until a point where all
> >> > related states have been cleaned up
>>> On 30.12.15 at 12:48, wrote:
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -4583,21 +4583,30 @@ void hvm_cpuid(unsigned int input, unsigned int *eax,
> unsigned int *ebx,
> *edx &= ~cpufeat_mask(X86_FEATURE_PSE36);
> break;
> case 0x7:
> -
>>> On 07.01.16 at 15:01, wrote:
> On 07/01/16 13:49, Jan Beulich wrote:
> On 30.12.15 at 12:48, wrote:
>>> --- a/xen/arch/x86/hvm/hvm.c
>>> +++ b/xen/arch/x86/hvm/hvm.c
>>> @@ -4583,21 +4583,30 @@ void hvm_cpuid(unsigned int input, unsigned int
>>> *eax,
> unsigned int *ebx,
>>>
On 07/01/16 13:51, Ian Campbell wrote:
> The map files highlight a number of namespacing inconsistencies
> (particularly with libxenguest using xc_* a significant amount).
>
> It also seems to highlight a bunch of libxenguest.so functionalty
> which appears to want to be exported (xc_*) but is not
>>> On 07.01.16 at 15:01, wrote:
> Ian Campbell writes:
>
>> I don't see this as contrary to your stated goals (e.g. ripping out all the
>> other schedulers), but I consider you to be within the expert camp for
>> wanting to do so (and having the chops to handle whatever pieces you find
>> yours
On 01/07/2016 06:43 AM, Roger Pau Monné wrote:
El 06/01/16 a les 21.03, Boris Ostrovsky ha escrit:
static int bootlate_hvm(struct xc_dom_image *dom)
{
-DOMPRINTF("%s: doing nothing", __func__);
+uint32_t domid = dom->guest_domid;
+xc_interface *xch = dom->xch;
+
+if ( !dom
On 29.12.2015 02:09, Jim Fehlig wrote:
> Both xm and xl config have long supported specifying vif rate
> limiting, e.g.
>
> vif = [ 'mac=00:16:3E:74:3d:76,bridge=br0,rate=10MB/s' ]
>
> Add support for mapping rate to and from in the xenconfig
> parser and formatter. rate is mapped to the require
>>> On 07.01.16 at 14:51, wrote:
> --- /dev/null
> +++ b/tools/libxc/libxenctrl.map
> @@ -0,0 +1,18 @@
> +{
> + global:
No actual version identifier / name space?
Jan
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-dev
c/s 7bf7458 "libxc: support of linear p2m list for migration of
pv-domains" breaks compilation on CentOS 7 because of 'ptes' being
possibly uninitialised after the 'err:' label.
The migration will fail early for conditions which would cause the for()
loop not to run, but the compiler doesn't know
On Thu, 2016-01-07 at 07:37 -0700, Jan Beulich wrote:
> > > > On 07.01.16 at 15:01, wrote:
>
> > Ian Campbell writes:
> >
> > > I don't see this as contrary to your stated goals (e.g. ripping out all
> > > the
> > > other schedulers), but I consider you to be within the expert camp for
> > > wa
On Thu, 2016-01-07 at 14:55 +, Andrew Cooper wrote:
> c/s 7bf7458 "libxc: support of linear p2m list for migration of
> pv-domains" breaks compilation on CentOS 7 because of 'ptes' being
> possibly uninitialised after the 'err:' label.
>
> The migration will fail early for conditions which wou
On 07/01/16 16:06, Ian Campbell wrote:
> On Thu, 2016-01-07 at 14:55 +, Andrew Cooper wrote:
>> c/s 7bf7458 "libxc: support of linear p2m list for migration of
>> pv-domains" breaks compilation on CentOS 7 because of 'ptes' being
>> possibly uninitialised after the 'err:' label.
>>
>> The migra
On 07/01/16 15:06, Ian Campbell wrote:
> On Thu, 2016-01-07 at 14:55 +, Andrew Cooper wrote:
>> c/s 7bf7458 "libxc: support of linear p2m list for migration of
>> pv-domains" breaks compilation on CentOS 7 because of 'ptes' being
>> possibly uninitialised after the 'err:' label.
>>
>> The migra
On Thu, 2016-01-07 at 15:36 +, Ian Jackson wrote:
> endif
> -OVMF_UPSTREAM_REVISION ?= cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd
> +OVMF_UPSTREAM_REVISION ?= af9785a9ed61daea52b47f0bf448f1f228beee1e
This should be:
OVMF_UPSTREAM_REVISION ?= 52a99493cce88a9d4ec8a02d7f1bd1a1001ce60d
You've pic
>>> On 07.01.16 at 16:18, wrote:
> On 1/7/16 9:00 AM, Ian Campbell wrote:
>> If we invert the sense then we could call it e.g. CONFIG_STANDARD_PLATFORM
>> and default it to y, I expect it will be easier to discourage people from
>> turning such an option off than to discourage them from turning so
flight 77267 qemu-upstream-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77267/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62044
build-a
flight 77380 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77380/
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 07.01.16 at 16:30, wrote:
> Some proposed text for discussion:
>
> config STANDARD_PLATFORM
> bool "Standard/Supported Platform"
> default y
> help
> This option enables everything which is part of the standard and
> supported Xen platform. You sho
On Tue, Dec 22, 2015 at 06:44:35PM +, Ian Jackson wrote:
> This is a new version of Stefano Stabellini's series
> [PATCH v5 0/6] libxl: xs_restrict QEMU
>
> I took Stefano's code as a spec for how to interact with qemu, and
> have reworked the whole series. In particular, I have
> - rebase
flight 77229 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77229/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
El 07/01/16 a les 15.47, Boris Ostrovsky ha escrit:
> On 01/07/2016 06:43 AM, Roger Pau Monné wrote:
>> El 06/01/16 a les 21.03, Boris Ostrovsky ha escrit:
>>> static int bootlate_hvm(struct xc_dom_image *dom)
>>> {
>>> -DOMPRINTF("%s: doing nothing", __func__);
>>> +uint32_t domid =
On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
> CC: Stefano Stabellini
Acked-by: Ian Campbell
(could go in now despite RFC-ness of the series as a whole)
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://
On Tue, 2015-12-22 at 18:45 +, Ian Jackson wrote:
> Add a maximum limit of physmap entries to save, so that when the guest
> gets write access to physmap it cannot DOS the toolstack.
>
> Signed-off-by: Stefano Stabellini
> Signed-off-by: Ian Jackson
Can we have a reference for where the num
Add machinery to allow the schedulers to be individually selectable
through the Kconfig interface. The first patch in the series sets up
the CONFIG_EXPERT Kconfig variable that is only enabled by passing an
environment variable to the build. The second patch in the series sets up
the Kconfig option
Add an additional environment variable, defaulting to disabled,
that enables the CONFIG_EXPERT configuration option. The purpose
of the CONFIG_EXPERT configuration option is to make non-standard
Kconfig options visible during the configuration process. The
CONFIG_EXPERT option is not, itself, visib
Allow the schedulers to be independently enabled or disabled at
compile-time. To match existing behavior, all four schedulers are
compiled in by default, although the Credit2, RTDS, and ARINC653 are
marked EXPERIMENTAL to match their not currently supported status.
CC: George Dunlap
CC: Dario Fag
Adds a simple macro to place a pointer to a scheduler into an array
section at compile time. Also, goes ahead and generates the array
entries with each of the schedulers.
CC: George Dunlap
CC: Dario Faggioli
CC: Josh Whitehead
CC: Robert VanVossen
Signed-off-by: Jonathan Creekmore
Acked-by: D
flight 77400 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77400/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 3 host-install(3) broken REGR. vs.
flight 77249 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77249/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xen-build fail REGR. vs. 66433
build-i386
On Thu, 2016-01-07 at 12:33 -0500, Boris Ostrovsky wrote:
> On 01/07/2016 12:06 PM, Ian Campbell wrote:
> > On Thu, 2016-01-07 at 17:54 +0100, Roger Pau Monné wrote:
> > > El 07/01/16 a les 15.47, Boris Ostrovsky ha escrit:
> > > > On 01/07/2016 06:43 AM, Roger Pau Monné wrote:
> > > > > El 06/01/1
This series arranges for the owner daemon to be able to tolerate
database restarts, and is generally much more careful about database
errors in Tcl.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
We are going to make it wrong to use db-execute for SELECT statements.
Convert the two existing violation sites (providing a dummy arrayvar).
Signed-off-by: Ian Jackson
---
sg-execute-flight |2 +-
tcl/JobDB-Executive.tcl |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
di
We would like to be able to retry db transactions. To do this we need
to know why they failed (if they did).
But pg_execute does not set errorCode. (This is clearly a bug.) And
since it immediately discards a failed statement, any error
information has been lost by the time pg_execute returns.
In chan-destroy-stuff, instead of accessing the db directly, add the
dead task(s) to a queue, and arrange to look at that queue.
Errors are handled by setting an `after' handler which we cancel if we
are successful.
The after handler requeues a queue run attempt as the first thing
(which will arr
Use the new errorCode coming out of db-execute* to tell when the error
is that we got a database deadlock, which is the situation in which we
should retry.
This involves combining the two catch blocks, so that there is only
one error handling strategy. Previously errors on COMMIT would be
retried
flight 77413 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77413/
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
flight 77247 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77247/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 62414
test-am
flight 77260 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77260/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 77156
Tests which did not succeed, but a
On 01/07/2016 05:50 AM, Jan Beulich wrote:
On 07.01.16 at 10:11, wrote:
Hi Jan,
On 2016/1/7 15:45, Jan Beulich wrote:
On 07.01.16 at 07:58, wrote:
On 2015/11/17 19:04, Jan Beulich wrote:
On 17.11.15 at 10:40, wrote:
--- a/xen/arch/arm/mm.c
+++ b/xen/arch/arm/mm.c
@@ -1138,6 +1138,10 @@ i
On Thu, Jan 7, 2016 at 6:12 AM, Jan Beulich wrote:
> >>> On 05.01.16 at 02:43, wrote:
> > This introduces a way to have a restricted VPMU, by specifying one of two
> > predefined groups of PMCs to make available. For secure environments,
> this
> > allows the VPMU to be used without needing to e
With commit 8c45adec18e0 ("libxc: create unmapped initrd in domain
builder if supported") location of ramdisk may not be available to
HVMlite guests by the time alloc_magic_pages_hvm() is invoked if the
guest supports unmapped initrd.
So let's move ramdisk info initialization (along with a few oth
With commit 8c45adec18e0 ("libxc: create unmapped initrd in domain
builder if supported") location of ramdisk may not be available to
HVMlite guests by the time alloc_magic_pages_hvm() is invoked if the
guest supports unmapped initrd.
So let's move ramdisk info initialization (along with a few oth
With commit 8c45adec18e0 ("libxc: create unmapped initrd in domain
builder if supported") location of ramdisk may not be available to
HVMlite guests by the time alloc_magic_pages_hvm() is invoked if the
guest supports unmapped initrd.
So let's move ramdisk info initialization (along with a few oth
flight 77259 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77259/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 3 host-install(3) broken in 77154 REGR. vs. 65639
test-amd64-i386-x
On 01/07/2016 01:42 PM, Doug Goldstein wrote:
This is broken from "xen: convert XSM_ENABLE to Kconfig"
6d5293032f5fc1c65f7a73548afaa3caa8e0105a. This hunk was dropped when I
made my v2 for some reason.
Signed-off-by: Doug Goldstein
Acked-by: Daniel De Graaf
_
On January 07, 2016 9:47 PM, wrote:
> Jan,
> Patch 2/3 and Patch 3/3 are based on v3 (Actually they are v3's patch 1/2 and
> patch 2/2).
> We have discussed how to hide a device with pci_hide_device() when
> Device-TLB flush is error.
>
> Now there are 2 concerns:
> 1. Hide the PCI device m
On 01/07/16 06:53, Jan Beulich wrote:
> >>> On 30.12.15 at 12:48, wrote:
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -4605,6 +4605,9 @@ void hvm_cpuid(unsigned int input, unsigned int *eax,
> > unsigned int *ebx,
> >
> > if ( !cpu_has_clwb )
> >
On 2016/1/8 5:40, Daniel De Graaf wrote:
> On 01/07/2016 05:50 AM, Jan Beulich wrote:
> On 07.01.16 at 10:11, wrote:
>>> Hi Jan,
>>>
>>> On 2016/1/7 15:45, Jan Beulich wrote:
>>> On 07.01.16 at 07:58, wrote:
>> On 2015/11/17 19:04, Jan Beulich wrote:
>> On 17.11.15 at 10
If the hypervisor is built with we will display it.
Signed-off-by: Konrad Rzeszutek Wilk
---
v2: Include HAVE_*, use libxl_zalloc, s/rc/ret/
---
tools/libxl/libxl.c | 24
tools/libxl/libxl.h | 5 +
tools/libxl/libxl_types.idl | 1 +
tools/libxl/xl_c
All of XENVER_* have now an XSM check.
The subop for XENVER_commandline is now a priviliged operation.
To not break guests we still return an string - but it is
just '\0'.
The rest: XENVER_[version|extraversion|capabilities|
parameters|get_features|page_size|guest_handle|changeset|
compile_info]
The mechanism to get this is via the XENVER hypercall and
we add a new sub-command to retrieve the binary build-id
called XENVER_build_id. The sub-hypercall parameter
allows an arbitrary size (the buffer and len is provided
to the hypervisor). A NULL parameter will probe the hypervisor
for the leng
Since v2 (http://lists.xen.org/archives/html/xen-devel/2015-11/msg00630.html)
- Made it work under ARM (build_id is part of the hypervisor).
- Only made two sub-ops be 'priv' - commandline and build_id.
- Applied all review comments.
- Autodetect whether ld is able to use --build-id
v1 (http:/
This run is configured for baseline tests only.
flight 38601 seabios real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38601/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-qemuu-nested-intel 13 xen-boot/l1
Convert the bigmem build option to Kconfig.
Signed-off-by: Doug Goldstein
---
The test:
$ grep CONFIG_BIGMEM .config
# CONFIG_BIGMEM is not set
$ pahole xen-syms -C page_info
/* size: 32, cachelines: 1, members: 5 */
$ grep CONFIG_BIGMEM .config
CONFIG_BIGMEM=y
$ pahole xen-syms
flight 77292 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77292/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 62702
test-am
On 07/01/16 23:19, Boris Ostrovsky wrote:
> With commit 8c45adec18e0 ("libxc: create unmapped initrd in domain
> builder if supported") location of ramdisk may not be available to
> HVMlite guests by the time alloc_magic_pages_hvm() is invoked if the
> guest supports unmapped initrd.
>
> So let's
On 01/07/2016 07:48 AM, Michal Privoznik wrote:
> On 29.12.2015 02:09, Jim Fehlig wrote:
>> The libxl_device_nic structure supports specifying an outgoing rate
>> limit based on a time interval and bytes allowed per interval. In xl
>> config a rate limit is specified as "/s@". INTERVAL
>> is option
On 01/07/2016 07:48 AM, Michal Privoznik wrote:
> On 29.12.2015 02:09, Jim Fehlig wrote:
>> Both xm and xl config have long supported specifying vif rate
>> limiting, e.g.
>>
>> vif = [ 'mac=00:16:3E:74:3d:76,bridge=br0,rate=10MB/s' ]
>>
>> Add support for mapping rate to and from in the xenconfig
On 01/04/2016 05:37 AM, Ian Campbell wrote:
> On Mon, 2016-01-04 at 13:31 +0100, Andreas Pflug wrote:
>> Am 04.01.16 um 13:13 schrieb Ian Campbell:
>>> On Mon, 2016-01-04 at 12:47 +0100, Andreas Pflug wrote:
Am 04.01.16 um 12:36 schrieb Ian Campbell:
> Sorry to hijack this thread.
>
>>
For example: if the secondary host is down, and we fail to send the data to
the secondary host. xc_domain_save() returns 0. So in the function
libxl__xc_domain_save_done(), rc is 0(the helper program exits normally),
and retval is 0(it is xc_domain_save()'s return value). In such case, we
just need
Signed-off-by: Wen Congyang
Reviewed-by: Andrew Cooper
---
tools/libxc/xc_sr_save.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libxc/xc_sr_save.c b/tools/libxc/xc_sr_save.c
index 88d85ef..e532168 100644
--- a/tools/libxc/xc_sr_save.c
+++ b/tools/libxc/xc_sr_save.c
Wen Congyang (5):
remus: don't call stream_continue() when doing failover
remus: resume immediately if libxl__xc_domain_save_done() completes
tools/libxc: don't send end record if remus fails
tools/libxc: error handling for the postcopy() callback
tools/libxl: remove unused function libx
stream_continue() is used for migration to read emulator
xenstore data and emulator context. For remus, if we do
failover, we have read it in the checkpoint cycle, and
we only need to complete the stream.
Signed-off-by: Wen Congyang
Reviewed-by: Andrew Cooper
---
tools/libxl/libxl_stream_read.c
Signed-off-by: Wen Congyang
Reviewed-by: Andrew Cooper
---
tools/libxc/xc_sr_save.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tools/libxc/xc_sr_save.c b/tools/libxc/xc_sr_save.c
index e532168..e4ba560 100644
--- a/tools/libxc/xc_sr_save.c
+++ b/tools/libxc/xc_sr_save
After the commit d77570e7, libxl__domain_save_device_model() can
be dropped.
Signed-off-by: Wen Congyang
---
tools/libxl/libxl.c | 4 --
tools/libxl/libxl_dom.c | 91
tools/libxl/libxl_internal.h | 6 ---
3 files changed, 101 deletions
On Thu, Jan 07, Jim Fehlig wrote:
> The 'iscsi:iqn.2006-09.de.suse@0ac47ee2-216e-452a-a341-a12624cd0225' blob was
> passed wholesale to xend, which would eat it and "do the right thing". AFAIK,
> libxl is not that forgiving. I've cc'd Olaf on this thread since we recently
> discussed how libvirt+l
1 - 100 of 104 matches
Mail list logo
