flight 80616 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80616/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 60684
I've snipped the email. I've taken your reviews in account - and just
responding on some of them that I believe need more comments.
..snip..
> > +However it has severe drawbacks - the safety checks which have to make sure
> > +the function is not on the stack - must also check every caller. For
On 02/05/2016 11:22 PM, Tamas K Lengyel wrote:
> The altp2m subsystem in its current form duplicates much of the existing
> code present in p2m for setting mem_access permissions. In this patch we
> consolidate the two versions but keep the separate MEMOP and HVMOP interfaces.
>
> Signed-off-by:
On Feb 5, 2016 8:30 PM, "Luis R. Rodriguez" wrote:
>
> paravirt_enabled conveys the idea that if this is set or if
> paravirt_enabled() returns true you are in a paravirtualized
> environment. This is not true by any means, and left as-is
> is just causing confusion and is
On 05/02/16 16:42, Boris Ostrovsky wrote:
>
>
> On 02/05/2016 08:21 AM, Juergen Gross wrote:
>> When adding a new frontend to xen-scsiback don't decrement the number
>> of active frontends in case of no error. Not doing so results in a
>
> I think you meant "Doing so".
I think so, too.
>
>
El 5/2/16 a les 17:01, Tim Deegan ha escrit:
> At 18:48 +0100 on 04 Feb (1454611694), Roger Pau Monné wrote:
>> Hello,
>>
>> I've Cced a bunch of people who have expressed interest in the HVMlite
>> design/implementation, both from a Xen or OS point of view. If you
>> would like to be removed,
On Fri, Feb 05, 2016 at 04:12:45PM +, Wei Liu wrote:
> On Fri, Feb 05, 2016 at 01:42:19PM +, Andrew Cooper wrote:
> > Signed-off-by: Andrew Cooper
> > ---
> > CC: Ian Campbell
> > CC: Ian Jackson
> > CC: Wei
flight 80533 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80533/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 66399
build-i386-rumpuserxen
El 5/2/16 a les 15:31, Jan Beulich ha escrit:
On 05.02.16 at 15:27, wrote:
>> El 5/2/16 a les 14:22, Jan Beulich ha escrit:
>> On 05.02.16 at 12:50, wrote:
El 5/2/16 a les 12:45, Jan Beulich ha escrit:
On 05.02.16 at 12:30,
At 14:41 + on 05 Feb (1454683317), Andrew Cooper wrote:
> On 05/02/16 08:01, Jan Beulich wrote:
> > --- a/xen/arch/x86/mm/paging.c
> > +++ b/xen/arch/x86/mm/paging.c
> > @@ -844,6 +844,15 @@ void paging_final_teardown(struct domain
> > * creation. */
> > int paging_enable(struct domain *d,
Hi George,
On Fri, Feb 05, 2016 at 11:05:39AM +, George Dunlap wrote:
> On Fri, Feb 5, 2016 at 3:44 AM, Tian, Kevin wrote:
> >> > So as long as the currently-in-use GTT tree contains no more than
> >> > $LIMIT ranges, you can unshadow and reshadow; this will be slow,
>>> On 14.01.16 at 22:46, wrote:
> +## Patching code
> +
> +The first mechanism to patch that comes in mind is in-place replacement.
> +That is replace the affected code with new code. Unfortunately the x86
> +ISA is variable size which places limits on how much space we
On Fri, Feb 05, 2016 at 09:19:30AM -0600, Doug Goldstein wrote:
> On 2/5/16 9:09 AM, Wei Liu wrote:
> > On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
> >> This is just suppose to do a simple compile test on Travis CI. Currently
> >> due to linux86 (bcc/bin86/dev86) not being
On Fri, Feb 05, 2016 at 01:42:22PM +, Andrew Cooper wrote:
> It is conceptually wrong to base a VM's featureset on the features visible to
> the toolstack which happens to construct it.
>
Agreed.
> Instead, the featureset used is either an explicit one passed by the
> toolstack, or the
On 05/02/16 16:50, Boris Ostrovsky wrote:
>
>
> On 02/05/2016 08:21 AM, Juergen Gross wrote:
>> When adding more than one LUN to a frontend a warning for a failed
>> assignment is issued in dom0 for each already existing LUN. Avoid this
>> warning.
>
> Aren't you just factoring out the check?
On 05/02/16 08:02, Jan Beulich wrote:
> ... as they're being used for PV guests only, which don't use HAP mode.
> This eliminates another pair of NULL callbacks in HAP as well as in 2-
> and 3-guest-level shadow modes.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
>>> On 05.02.16 at 15:41, wrote:
> On 05/02/16 08:01, Jan Beulich wrote:
>> --- a/xen/arch/x86/mm/paging.c
>> +++ b/xen/arch/x86/mm/paging.c
>> @@ -844,6 +844,15 @@ void paging_final_teardown(struct domain
>> * creation. */
>> int paging_enable(struct domain *d, u32
At 00:51 -0700 on 05 Feb (1454633478), Jan Beulich wrote:
> 1: mm: drop guest_{map,get_eff}_l1e() hooks
> 2: mm: make {cmpxchg,write}_guest_entry() hook shadow mode specific
> 3: shadow: remove a few 32-bit hypervisor leftovers
>
> Signed-off-by: Jan Beulich
Reviewed-by: Tim
On 05/02/16 14:28, Jan Beulich wrote:
On 05.02.16 at 14:42, wrote:
>> --- a/tools/libxc/xc_cpuid_x86.c
>> +++ b/tools/libxc/xc_cpuid_x86.c
>> @@ -380,6 +380,11 @@ static void intel_xc_cpuid_policy(xc_interface *xch,
>> }
>> }
>>
>> +#define X86_XCR0_X87
El 5/2/16 a les 16:29, Jan Beulich ha escrit:
On 05.02.16 at 16:00, wrote:
>> El 5/2/16 a les 15:31, Jan Beulich ha escrit:
>> On 05.02.16 at 15:27, wrote:
El 5/2/16 a les 14:22, Jan Beulich ha escrit:
> Also consider e.g. the device
This is just suppose to do a simple compile test on Travis CI. Currently
due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
be built.
Signed-off-by: Doug Goldstein
---
change since v2:
- drop IRC notification
So this will work great if we get a regular
On 02/05/2016 08:21 AM, Juergen Gross wrote:
When adding more than one LUN to a frontend a warning for a failed
assignment is issued in dom0 for each already existing LUN. Avoid this
warning.
Aren't you just factoring out the check? The warning is still printed
for each
On Tue, 2016-02-02 at 14:10 +, Ian Campbell wrote:
>
> When running Jessie userspace the issue only appeared somewhere between
> Linux v3.18 and v3.19, I'm currently looking at bisecting that range in
> case the commit which exposed the issue gives a hint (I fear it wont
> though).
Bisecting
On 02/05/2016 10:50 AM, Boris Ostrovsky wrote:
@@ -962,33 +973,31 @@ static int
scsiback_del_translation_entry(struct vscsibk_info *info,
struct ids_tuple *v)
{
struct v2p_entry *entry;
-struct list_head *head = &(info->v2p_entry_lists);
unsigned
Hi,
I have looked into getting OpenStack been tested on the latest Xen via
osstest.
The ts-openstack-deploy script does prepare a bit more the host, clone
devstack and other OpenStack trees, then run ./stack.sh, which is a bit
like raisin and deploy OpenStack on the host. Once the machine is
This script runs the OpenStack integration test suite, Tempest.
Signed-off-by: Anthony PERARD
Acked-by: Ian Campbell
---
No change in V5
Change in V4:
- use \Q\E for tests names
- write the full name of the tests to skip
- use push
This script installs any necessary packages and clones all of the OpenStack
trees which are used by devstack to deploy OpenStack.
Signed-off-by: Anthony PERARD
Acked-by: Ian Campbell
---
Only change in V5:
- edit stackrc from devstack file to
This patch should create a flight "openstack-nova", with those jobs:
build-amd64
build-amd64-xsm
build-amd64-pvops
build-amd64-libvirt
test-amd64-amd64-devstack
test-amd64-amd64-devstack-xsm
About the runvars revision_* of test-*-*-devstack:
only REVISION_OPENSTACK_NOVA is set, the
On 2/5/16 9:09 AM, Wei Liu wrote:
> On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
>> This is just suppose to do a simple compile test on Travis CI. Currently
>> due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
>> be built.
>>
>> Signed-off-by: Doug
>>> On 05.02.16 at 16:00, wrote:
> El 5/2/16 a les 15:31, Jan Beulich ha escrit:
> On 05.02.16 at 15:27, wrote:
>>> El 5/2/16 a les 14:22, Jan Beulich ha escrit:
Also consider e.g. the device IRQ which the
serial driver may be using: We
On Fri, Feb 05, 2016 at 04:59:43PM +0100, Dario Faggioli wrote:
> On Fri, 2016-02-05 at 14:44 +, Wei Liu wrote:
> > On Thu, Feb 04, 2016 at 04:50:43PM -0600, Chong Li wrote:
> > > Add libxl_vcpu_sched_params_get/set and sched_rtds_vcpu_get/set
> > > functions to support per-VCPU settings.
> >
On Thu, Feb 04, 2016 at 04:50:44PM -0600, Chong Li wrote:
> Change main_sched_rtds and related output functions to support
> per-VCPU settings.
>
> Signed-off-by: Chong Li
> Signed-off-by: Meng Xu
> Signed-off-by: Sisu Xi
>
> ---
>
On 02/05/2016 08:21 AM, Juergen Gross wrote:
When adding a new frontend to xen-scsiback don't decrement the number
of active frontends in case of no error. Not doing so results in a
I think you meant "Doing so".
Reviewed-by: Boris Ostrovsky
failure when
On Fri, 2016-02-05 at 14:44 +, Wei Liu wrote:
> On Thu, Feb 04, 2016 at 04:50:43PM -0600, Chong Li wrote:
> > Add libxl_vcpu_sched_params_get/set and sched_rtds_vcpu_get/set
> > functions to support per-VCPU settings.
> >
>
> I will need Dario or George to review the logic of the code.
>
On Fri, Feb 05, 2016 at 01:42:18PM +, Andrew Cooper wrote:
> Rather than having a different local copy of some of the feature
> definitions.
>
> Modify the xc_cpuid_x86.c cpumask helpers to appropriate truncate the
> new values.
>
> Signed-off-by: Andrew Cooper
On Fri, Feb 05, 2016 at 01:42:16PM +, Andrew Cooper wrote:
> And provide stubs for toolstack use.
>
> Signed-off-by: Andrew Cooper
> ---
> CC: Jan Beulich
> CC: Tim Deegan
> CC: Ian Campbell
> CC: Wei Liu
On Fri, Feb 05, 2016 at 01:42:20PM +, Andrew Cooper wrote:
> It is able to reports the current featuresets; both the static masks and
> dynamic featuresets from Xen, or to decode an arbitrary featureset into
> `/proc/cpuinfo` style strings.
>
> Signed-off-by: Andrew Cooper
At 18:48 +0100 on 04 Feb (1454611694), Roger Pau Monné wrote:
> Hello,
>
> I've Cced a bunch of people who have expressed interest in the HVMlite
> design/implementation, both from a Xen or OS point of view. If you
> would like to be removed, please say so and I will remove you in
> further
On Fri, Feb 05, 2016 at 01:42:19PM +, Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper
> ---
> CC: Ian Campbell
> CC: Ian Jackson
> CC: Wei Liu
>
> New in v2
> ---
>
On 2/5/16 10:33 AM, Ian Campbell wrote:
> On Fri, 2016-02-05 at 08:48 -0600, Doug Goldstein wrote:
>>
>> The goal here is not to replace osstest by any means but to augment it by
>> providing some easy to do build tests on every revision and reporting back.
>> It
>> should be possible in the
Hi everyone,
This, hopefully, simple series aims at making it easier to look at and
interpret hypervisor scheduling related traces.
In fact, it includes improvements for both how xentrace_format and xenalyze
decode and pretty print a trace collected with scheduling events enabled,
either generic
it is enabled for pretty much all of them already.
There were just a few that had it disabled.
When tracing a scheduler, timing information is
really important, so enable it everywhere scheduling
related.
Note that this was not really a problem if looking
at the traces with xenalyze, but it was
when tracing runstate changes, the vcpu and domain IDs
are encoded in the lower and higher, respectively, parts
of a 32 bits integer. When decoding a trace with
xentrace_format, this makes it possible to display
such events like this:
CPU0 833435853624 (+ 768) running_to_runnable [ dom:vcpu
vcpu_wake() and vcpu_sleep() are called before the specific
schedulers wakeup and sleep routines (in fact, it is them
that calls those specific routine).
Make the trace reflect that, by moving the records up. In
fact, it is more natural and easy to find the record of
the event (e.g., the wakeup)
as it is always acts on v->processor of the vcpu because
of which we are tickling.
Getting rid of it makes the code easier to understand
and better looking.
While there, remove a spurious blank line.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
flight 80634 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80634/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 79947
build-amd64
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Meng Xu
Cc: Tianyang Chen
Cc: Ian Jackson
On 05/02/16 16:01, Tim Deegan wrote:
> At 18:48 +0100 on 04 Feb (1454611694), Roger Pau Monné wrote:
>> Hello,
>>
>> I've Cced a bunch of people who have expressed interest in the HVMlite
>> design/implementation, both from a Xen or OS point of view. If you
>> would like to be removed, please say
At 17:14 + on 05 Feb (1454692488), Andrew Cooper wrote:
> On 05/02/16 16:01, Tim Deegan wrote:
> > At 18:48 +0100 on 04 Feb (1454611694), Roger Pau Monné wrote:
> >> Hello,
> >>
> >> I've Cced a bunch of people who have expressed interest in the HVMlite
> >> design/implementation, both from a
Hey,
I applied all your comments..
> >+The `struct xen_xsplice_status` structure contains an status of payload
> >which includes:
> >+
> >+ * `status` - whether it has been:
> >+ * *XSPLICE_STATUS_LOADED* (1) has been loaded.
> >+ * *XSPLICE_STATUS_CHECKED* (2) the ELF payload safety checks
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Meng Xu
Cc: Tianyang Chen
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
On 05/02/16 18:05, Tim Deegan wrote:
> At 17:14 + on 05 Feb (1454692488), Andrew Cooper wrote:
>> On 05/02/16 16:01, Tim Deegan wrote:
>>> At 18:48 +0100 on 04 Feb (1454611694), Roger Pau Monné wrote:
Hello,
I've Cced a bunch of people who have expressed interest in the HVMlite
On 02/05/2016 05:59 PM, osstest service owner wrote:
> flight 80615 libvirt real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/80615/
>
> Regressions :-(
>
FYI, already bisected this a while ago and it's introduced by commit
8cd1d54 ("util: Export remoteSerializeTypedParameters
> >+#define return_(x) { printk(XENLOG_DEBUG "%s:%d rc: %d\n", \
> >+__func__,__LINE__, x); return x; }
> >+
.. snip..
> >+printk(XENLOG_ERR "Could not allocate memory for section table!\n");
>
> Shouldn't this printk be removed if you're using return_?
I
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
tools/xentrace/formats |7
to include the vcpu IDs, in a way that matches
how the "dom:vcpu" couple is displayed in other
events (runstate changes).
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
> >+
> >+ /->\
> >+ \ /
> >+ UNLOAD <--- CHECK ---> REPLACE|APPLY --> REVERT --\
> >+\ |
> >+ \---<-/
>
> This doesn't make much sense to me. The actions need to be represented
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
tools/xentrace/formats | 13
On 02/05/2016 11:59 AM, Juergen Gross wrote:
On 05/02/16 16:50, Boris Ostrovsky wrote:
On 02/05/2016 08:21 AM, Juergen Gross wrote:
When adding more than one LUN to a frontend a warning for a failed
assignment is issued in dom0 for each already existing LUN. Avoid this
warning.
Aren't you
flight 80615 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80615/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 9 debian-di-install fail REGR. vs. 80121
when tracing runstate changes, the vcpu and domain IDs
are encoded in the lower and higher, respectively, parts
of a 32 bits integer. When decoding a trace with
xentrace_format, this makes it possible to display
such events like this:
CPU0 833435853624 (+ 768) running_to_runnable [ dom:vcpu
so that they actually live in the functions that
do the scheduling related domain initialization and
destruction.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
---
xen/common/domain.c |1 -
xen/common/schedule.c |4 ++--
2
>>> On 04.02.16 at 18:12, wrote:
> Two angles on this.
>
> First, assuming that limiting the number of ranges is what we want: I'm
> not really a fan of using HVM_PARAMs for this, but as long as it's not
> considered a public interface (i.e., it could go away or
On 2/4/2016 7:06 PM, George Dunlap wrote:
On Thu, Feb 4, 2016 at 9:38 AM, Yu, Zhang wrote:
On 2/4/2016 5:28 PM, Paul Durrant wrote:
I assume this means that the emulator can 'unshadow' GTTs (I guess on an
LRU basis) so that it can shadow new ones when the limit
On 2/5/2016 1:12 AM, George Dunlap wrote:
On 04/02/16 14:08, Jan Beulich wrote:
On 04.02.16 at 14:33, wrote:
Jan Beulich writes ("Re: [Xen-devel] [PATCH v3 3/3] tools: introduce parameter
max_wp_ram_ranges."):
On 04.02.16 at 10:38,
Hi Bjorn,
On Fri, Feb 5, 2016 at 5:49 AM, Bjorn Helgaas wrote:
> Hi Jayachandran,
>
> On Fri, Jan 29, 2016 at 02:35:40PM +0530, Jayachandran C wrote:
>> Add a simple ACPI based PCI host controller under config option
>> ACPI_PCI_HOST_GENERIC. This is done by providing an
... related to 8-byte cmpxchg having required special precautions
there.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/mm/shadow/common.c
+++ b/xen/arch/x86/mm/shadow/common.c
@@ -259,10 +259,10 @@ hvm_emulate_cmpxchg(enum x86_segment seg
struct sh_emulate_ctxt *sh_ctxt
>>> On 05.02.16 at 04:44, wrote:
> This is why Yu mentioned earlier whether we can just set a default
> limit which is good for majority of use cases, while extending our
> device mode to drop/recreate some shadow tables upon the limitation
> is hit. I think this matches how
Disallow the unmaintained and presumed broken translated-but-not-
external paging mode combination, allowing the respective paging hooks
to go away (which eliminates one pair of NULL callbacks in HAP mode).
As a result of them no longer being generic paging operations, make the
inline functions
... as they're being used for PV guests only, which don't use HAP mode.
This eliminates another pair of NULL callbacks in HAP as well as in 2-
and 3-guest-level shadow modes.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/mm/shadow/multi.c
+++ b/xen/arch/x86/mm/shadow/multi.c
El 4/2/16 a les 21:17, Boris Ostrovsky ha escrit:
> On 02/04/2016 02:21 PM, Roger Pau Monné wrote:
>> El 4/2/16 a les 19:51, Samuel Thibault ha escrit:
>>> Boris Ostrovsky, on Thu 04 Feb 2016 13:38:02 -0500, wrote:
On 02/04/2016 12:48 PM, Roger Pau Monné wrote:
> The format of the boot
On 2/5/2016 12:18 PM, Tian, Kevin wrote:
From: George Dunlap [mailto:george.dun...@citrix.com]
Sent: Friday, February 05, 2016 1:12 AM
On 04/02/16 14:08, Jan Beulich wrote:
On 04.02.16 at 14:33, wrote:
Jan Beulich writes ("Re: [Xen-devel] [PATCH v3 3/3] tools:
On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
> This is just suppose to do a simple compile test on Travis CI. Currently
> due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
> be built.
>
> Signed-off-by: Doug Goldstein
> ---
>
> So this
El 5/2/16 a les 14:13, Jan Beulich ha escrit:
On 05.02.16 at 13:28, wrote:
>> This will prevent alignments from getting in the way. It's not safe to
>> define this memory structures using C anyway, since the ABI depends on the
>> bitness, while our protocol does not.
>>
On Fri, Feb 05, 2016 at 01:42:17PM +, Andrew Cooper wrote:
> The type of the pointer to a bitmap is not interesting; it does not affect the
> representation of the block of bits being pointed to.
>
> Make the libxc functions consistent with those in Xen, so they can work just
> as well with
On Fri, Feb 05, 2016 at 01:42:21PM +, Andrew Cooper wrote:
> Later changes will cause the cpuid generation logic to seed their information
> from a featureset. This patch adds the infrastructure to specify a
> featureset, and will obtain the appropriate default from Xen if omitted.
>
>
On Fri, 2016-02-05 at 08:48 -0600, Doug Goldstein wrote:
>
> The goal here is not to replace osstest by any means but to augment it by
> providing some easy to do build tests on every revision and reporting back. It
> should be possible in the future to potentially tie this into osstest to
>
> >>As far as I can tell, the mechanics of how this works haven't changed, the
> >>code has just been reorganized. Which means the points that Martin raised
> >>about this mechanism are still outstanding.
> >
> >A bit. I added the extra timeout on both of the 'spin-around' and also
> >moved some
On Friday, February 05, 2016 09:47:40 AM Lorenzo Pieralisi wrote:
> On Fri, Feb 05, 2016 at 02:05:37PM +0530, Jayachandran Chandrashekaran Nair
> wrote:
>
> [...]
>
> > pci_host_acpi.c is a generic implementation of these using a sysdata
> > pointing to acpi_pci_root_info, and using a pointer
On Fri, Feb 5, 2016 at 3:13 PM, Zhiyuan Lv wrote:
>> My question is, suppose a single GTT / gpu thread / tree has 9000
>> ranges. It would be trivial for an attacker to break into the
>> operating system and *construct* such a tree, but it's entirely
>> possible that due to
Introduce support for VIR_MIGRATE_PEER2PEER in libvirt migration.
Most of the changes occur at the source and no modifications at
the receiver.
In P2P mode there is only the Perform phase so we must handle the
connection with the destination and actually perform the
migration.
On Wed, Feb 3, 2016 at 3:35 AM, Andrew Cooper
wrote:
> On 03/02/16 01:32, Tamas K Lengyel wrote:
>
>
>
> On Tue, Feb 2, 2016 at 6:00 PM, Andrew Cooper
> wrote:
>
>> On 03/02/2016 00:51, Tamas K Lengyel wrote:
>>
>> Hello all,
>> with the
On Fri, Feb 5, 2016 at 1:38 PM, Konrad Rzeszutek Wilk
wrote:
>> >+#define return_(x) { printk(XENLOG_DEBUG "%s:%d rc: %d\n", \
>> >+__func__,__LINE__, x); return x; }
>> >+
>
> .. snip..
>> >+printk(XENLOG_ERR "Could not allocate memory
When xc_map_foreign_batch got deprecated reinitializing vm_event on a domain
where an event listener was previously active broke as it relied on the flag
XEN_DOMCTL_PFINFO_XTAB to indicate that the magic page is not in the physmap.
Manually check the gpfn type, add it to the physmap if needed, and
On Fri, Feb 5, 2016 at 1:34 PM, Tamas K Lengyel
wrote:
>
>
>
> On Wed, Feb 3, 2016 at 3:35 AM, Andrew Cooper
> wrote:
>
>> On 03/02/16 01:32, Tamas K Lengyel wrote:
>>
>>
>>
>> On Tue, Feb 2, 2016 at 6:00 PM, Andrew Cooper
Only copy the VCPU_PAUSED flag to the response. Copy the entire mem_access
struct which is useful and easily forgotten when also testing the emulate
response flags. Turn off singlestepping on the vCPUs once we are done
processing all events, as we might have turned on singlestep there and leave
The altp2m subsystem in its current form duplicates much of the existing
code present in p2m for setting mem_access permissions. In this patch we
consolidate the two versions but keep the separate MEMOP and HVMOP interfaces.
Signed-off-by: Tamas K Lengyel
Cc: Ian Jackson
Extend the existing get_mem_access memop to allow querying permissions in
altp2m views as well.
Signed-off-by: Tamas K Lengyel
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
On Feb 4, 2016 7:11 PM, "Fengguang Wu" wrote:
>
> Hi Andy,
>
> CC more people on Xen testing -- in case OSStest already (or plans to)
> cover such test case.
>
> On Tue, Feb 02, 2016 at 07:31:30PM -0800, Andy Lutomirski wrote:
> > Hi all-
> >
> > Would it make sense to add
This patch introduces keep alive messages support for P2P migration
and it adds two new configuration entries namely 'keepalive_interval'
'keepalive_count' to control it. Behavior of these entries is the
same as qemu driver thus the description is copied from there
with just a few simplifications.
>>> On 04.02.16 at 19:22, wrote:
> On 04/02/16 17:48, Roger Pau Monné wrote:
>> - HVMlite hardware domain: can we get rid of the PHYSDEV ops and PIRQ
>>event channels?
>> - HVMlite PCI-passthrough: can we get rid of pciback/pcifront?
>
> +1000, for both.
I'm a
On 2/3/2016 2:23 PM, Ian Campbell wrote:
On Wed, 2016-02-03 at 13:54 +0200, Corneliu ZUZU wrote:
I thought this mail was not sent properly (didn't find it any longer on
the web (?)) and I resent it just earlier.
I figured it must've been the fact that I forgot to put a "Changed since
v1"
This primarily consists of ts-coverity-{build,upload} and
make-coverity-flight which constructs the sole job.
The branch is named "xen-unstable-coverity" which matches various xen*
in the cr-* scripts. Places which needed special treatement are
handled by matching xen-*-coverity, which leaves the
I'm going to have a need for it elsewhere.
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
Osstest/BuildSupport.pm | 12
ts-xen-build| 13 +
2 files changed, 13 insertions(+), 12 deletions(-)
diff
On Fri, 2016-02-05 at 00:12 +, Andrew Cooper wrote:
> On 04/02/2016 23:14, Steven Haigh wrote:
> > On 2016-02-05 09:22, Andrew Cooper wrote:
> > > On 04/02/2016 22:06, Alex Braunegg wrote:
> > > Qemu is only used for device emulation when used with Xen, not CPU
> > > emulation.
I answered
I have a patch in Xen which stores some information of VM process. I have
another program running in Dom0 which intercept this information.
i) I want to configure my patch running in Xen to send the alert
notification to program running in Dom0 to read data, probably using event
channels. How to
flight 80434 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80434/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 79422
1 - 100 of 218 matches
Mail list logo