branch xen-unstable
xenbranch xen-unstable
job build-armhf-libvirt
testid libvirt-build
Tree: libvirt git://libvirt.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 reproduced
On 2016/6/7 21:42, Julien Grall wrote:
> Hello Shannon,
>
> On 31/05/16 06:02, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> Currently there is only the table header in DSDT table.
>>
>> Signed-off-by: Shannon Zhao
>> ---
>> tools/libxl/libxl_arm.c | 15 +++
>> 1 file changed,
flight 95763 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95763/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm3 host-install(3) broken REGR. vs. 94729
test-amd64-i386-freebsd
flight 95768 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95768/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken
REGR. v
flight 95762 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95762/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 3 host-install(3) broken REGR. vs. 94728
test-amd64-amd64-qemuu
On June 14, 2016 5:03 PM, Jan Beulich wrote:
> -if ( amd_iommu_update_ivrs_mapping_acpi() != 0 )
> +rc = amd_iommu_update_ivrs_mapping_acpi();
> +if ( rc )
> goto error_out;
>
> /* initialize io-apic interrupt remapping entries */
> -if ( iommu_intremap && amd_iommu_
On 15 June 2016 at 21:40, Julien Grall wrote:
> Xen will crash on platform where GICv2m is not available with the
> following error:
>
> (XEN) Can't find ranges property for the gic node
> (XEN) Device tree generation failed (-15).
> (XEN)
> (XEN)
> (XEN) P
flight 95747 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95747/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 86412
test-amd64-amd64-qemuu
flight 95738 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95738/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 95353
test-amd64-amd64-xl-
On 06/15/2016 11:26 AM, Jan Beulich wrote:
> --- a/xen/arch/x86/time.c
> +++ b/xen/arch/x86/time.c
> @@ -1328,21 +1328,51 @@ static void time_calibration(void *unuse
> &r, 1);
> }
>
> +static struct {
> +s_time_t local_stime, master_stime;
> +} ap_bringup_ref;
> +
> +vo
flight 95744 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95744/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 3 host-install(3) broken REGR. vs. 95164
test-amd64-i386-freebs
> On 15 Jun 2016, at 12:15, Wei Liu wrote:
>
> Move default the pid file under XEN_RUN_DIR. Note that it changes the
> location from /var/run to /var/run/xen.
>
> Signed-off-by: Wei Liu
> ---
> Cc: Ian Jackson
> Cc: Dave Scott
> ---
> tools/ocaml/xenstored/xenstored.ml | 2 +-
> 1 file change
branch xen-unstable
xenbranch xen-unstable
job build-amd64-libvirt
testid libvirt-build
Tree: libvirt git://libvirt.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.git
Tree: xe
Add a 4.7 config file, make it the default.
Also update the qemu and qemu_traditional recipies after Ian Cambell's
work to split off separate libraries.
Signed-off-by: George Dunlap
---
Changes in v3:
- Reword comment
- Don't use tabs
Changes in v2:
- Only add the extra #defines when building
v3:
- Only 4.7 patch remaining (other patches acked & committed)
v2:
- Include fixes for config-master as well
- Only include qemu / libxc compatiblity #defines for 4.7 and master
George Dunlap (1):
Update to 4.7, update qemu and qemu_traditional recipes
components/qemu | 32 +
flight 95786 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95786/
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 Wed, Jun 15, 2016 at 10:31:41AM +0100, Wei Liu wrote:
> ... because the available vcpu bitmap can change during domain life time
> due to cpu hotplug and unplug.
>
> For QEMU upstream, we interrogate QEMU for the number of vcpus. For
> others, we look directly into xenstore for information.
>
On 15/06/16 18:13, Stefano Stabellini wrote:
> On Wed, 15 Jun 2016, George Dunlap wrote:
>> Add a 4.7 config file, make it the default.
>>
>> Also update the qemu and qemu_traditional recipies after Ian Cambell's
>> work to split off separate libraries.
>>
>> Signed-off-by: George Dunlap
>> ---
>>
On Wed, 15 Jun 2016, George Dunlap wrote:
> Add a 4.7 config file, make it the default.
>
> Also update the qemu and qemu_traditional recipies after Ian Cambell's
> work to split off separate libraries.
>
> Signed-off-by: George Dunlap
> ---
> Changes in v2:
> - Only add the extra #defines when
On Wed, Jun 15, 2016 at 6:34 PM, Konrad Rzeszutek Wilk <
konrad.w...@oracle.com> wrote:
P.S.
The Git Manual is very solid.
That helped O:-) ... now reading
https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
___
Xen-devel mailing list
Xen
On Wed, 15 Jun 2016, George Dunlap wrote:
> Point xen, qemu, and qemu-trad to stable-4.5 and -4.6 branches.
>
> And point the default libvirt to point to the libvirt 1.3.3
> maintenance branch, rather than xen-tested-master.
>
> Also update OVMF revision for 4.6 to a version that builds with mode
On Wed, Jun 15, 2016 at 10:31:39AM +0100, Wei Liu wrote:
> Factor out the logic to determine device model version to a function. It
> will be used later. Note that code now also checks if the stbudom field
> is actually set before trying to extract a value from it.
>
> No functional change.
>
> S
Introduction of indirect descriptors for qdisk.
Changes in the xen_blkif.h file:
- struct blkif_x86_**_request contains union of
'struct blkif_x86_**_request_direct' (previous struct blkif_x86_**_request)
and 'struct blkif_x86_**_request_indirect'
- new helper functions to rewrite 'struct
In the meantime I tried an implementation for indirect descriptors for qemu.
Described further in the next mail. It is based on current staging branch of
qemu.
From tests I did not observed an improvement. A decrease of bandwith starts
earlier when the block size increase then for staging branc
On Mon, 2016-06-13 at 11:58 +0100, David Vrabel wrote:
> On 13/06/16 11:44, Paulina Szubarczyk wrote:
> > On Mon, 2016-06-13 at 11:15 +0100, David Vrabel wrote:
> >> On 13/06/16 10:43, Paulina Szubarczyk wrote:
> >>> Copy data operated on during request from/to local buffers to/from
> >>> the gran
On Wed, Jun 15, 2016 at 10:31:40AM +0100, Wei Liu wrote:
> It interrogates QEMU for CPUs and update the bitmap accordingly.
>
> Signed-off-by: Wei Liu
Reviewed-by: Anthony PERARD
--
Anthony PERARD
___
Xen-devel mailing list
Xen-devel@lists.xen.org
On 06/15/2016 11:54 AM, Jan Beulich wrote:
>
> Yes, albeit two then isn't enough either if we want to fully address
> the basic issue here: We'd have to latch as many translations as
> there are possibly pages involved in the execution of a single
> instruction.
Re: translations changing under us
On Wed, Jun 15, 2016 at 05:26:52PM +0200, Wim ten Have wrote:
> Running F23 here seemed to go trough good with above URL (making up much
> for my environment).
>
> The only part causing me trouble is page specific direction setting the
> branch:
>
> $ cd xen;
> *git checkout -b staging staging*
flight 95733 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95733/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs.
80927
bu
Hi,
i'm working on the dragonboard trying to install Xen on it, do you have any
documentation to help me and ease my work.
Best regards,
Fadwa Messaoudi.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Wed, Jun 15, 2016 at 12:15:05PM +0100, Wei Liu wrote:
> Store xldevd.pid under XEN_RUN_DIR. Note that the default location would
> change from /var/run to /var/run/xen.
>
> Signed-off-by: Wei Liu
Acked-by: Roger Pau Monné
___
Xen-devel mailing lis
v2:
- Include fixes for config-master as well
- Only include qemu / libxc compatiblity #defines for 4.7 and master
George Dunlap (4):
components/xen: Actually disable rombios
config: Separate config urls into a separate file
Update config-4.6 and config-4.5 to point to stable branches; fi
So that we're not duplicating information.
Signed-off-by: George Dunlap
Acked-by: Stefano Stabellini
---
CC: Stefano Stabellini
---
configs/config-4.5 | 39 ---
configs/config-4.6 | 39 ---
configs/config-master
Point xen, qemu, and qemu-trad to stable-4.5 and -4.6 branches.
And point the default libvirt to point to the libvirt 1.3.3
maintenance branch, rather than xen-tested-master.
Also update OVMF revision for 4.6 to a version that builds with modern
gccs.
Point config-master libvirt to libvirt's "ma
Commit 5fe3855 meant to disable rombios, but didn't. This causes the following
build failure:
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-typedefs
-D__XEN_TOO
Add a 4.7 config file, make it the default.
Also update the qemu and qemu_traditional recipies after Ian Cambell's
work to split off separate libraries.
Signed-off-by: George Dunlap
---
Changes in v2:
- Only add the extra #defines when building 4.7 or master, and add an
explanation of what t
On Wed, Jun 15, 2016 at 12:15:07PM +0100, Wei Liu wrote:
> Store various PID files under XEN_RUN_DIR. Note that this change the
> default location from /var/run to /var/run/xen.
>
> Signed-off-by: Wei Liu
Acked-by: Roger Pau Monné
___
Xen-devel maili
On Wed, Jun 15, 2016 at 12:15:06PM +0100, Wei Liu wrote:
> Store xldevd.pid under XEN_RUN_DIR. Note that this will change the
> default location from /var/run to /var/run/xen.
>
> Signed-off-by: Wei Liu
Acked-by: Roger Pau Monné
___
Xen-devel mailing
>>> On 15.06.16 at 17:46, wrote:
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: 15 June 2016 16:43
>> To: Paul Durrant
>> Cc: Sander Eikelenboom; xen-devel@lists.xen.org; Boris Ostrovsky
>> Subject: RE: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called
On Wed, Jun 15, 2016 at 11:12:08AM -0500, Doug Goldstein wrote:
> On 6/15/16 9:47 AM, Wei Liu wrote:
> > On Wed, Jun 15, 2016 at 09:39:24AM -0500, Doug Goldstein wrote:
> >> On 6/15/16 9:31 AM, Wei Liu wrote:
> > [...]
> >>> -#ifndef NDEBUG
> >>> /* Permit use of the Forced Emulation Prefix in HVM
On 15/06/16 15:02, Stefano Stabellini wrote:
> On Wed, 15 Jun 2016, George Dunlap wrote:
>> On 15/06/16 11:53, Stefano Stabellini wrote:
>>> On Wed, 15 Jun 2016, George Dunlap wrote:
On 15/06/16 11:24, Stefano Stabellini wrote:
> On Tue, 14 Jun 2016, George Dunlap wrote:
>> On 14/06/16
On 6/15/16 9:47 AM, Wei Liu wrote:
> On Wed, Jun 15, 2016 at 09:39:24AM -0500, Doug Goldstein wrote:
>> On 6/15/16 9:31 AM, Wei Liu wrote:
> [...]
>>> -#ifndef NDEBUG
>>> /* Permit use of the Forced Emulation Prefix in HVM guests */
>>> extern bool_t opt_hvm_fep;
>>> -#else
>>> -#define opt_hvm_f
On Wed, Jun 15, 2016 at 05:26:52PM +0200, Wim ten Have wrote:
> Running F23 here seemed to go trough good with above URL (making up much
> for my environment).
>
> The only part causing me trouble is page specific direction setting the
> branch:
>
> $ cd xen;
> *git checkout -b staging staging*
>
flight 95728 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95728/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-xsm 3 host-install(3) broken in 95653 pass in 95728
test-amd64-i386-xl-xsm3
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 15 June 2016 16:43
> To: Paul Durrant
> Cc: Sander Eikelenboom; xen-devel@lists.xen.org; Boris Ostrovsky
> Subject: RE: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from
> emulate.c:144 RIP: c000:[<
>>> On 15.06.16 at 17:29, wrote:
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: 15 June 2016 16:22
>> To: Paul Durrant; Boris Ostrovsky
>> Cc: Sander Eikelenboom; xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called
On Thu, Jun 2, 2016 at 11:22 AM, Safa Hamza wrote:
> hello
> in order to build Xen from the source on my host (Intel x86-x64 running
> Ubuntu mate)
> I downloaded Xen Source Code from
> git clone git://xenbits.xen.org/xen.gitthen
> git checkout -b RELEASE-4.3.1 RELEASE-4.3.1
> I configured i
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 15 June 2016 16:22
> To: Paul Durrant; Boris Ostrovsky
> Cc: Sander Eikelenboom; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] Xen-unstable 4.8: HVM domain_crash called from
> emulate.c:144 RIP: c000:[<
On Tue, Jun 14, 2016 at 12:01 PM, Andrew Cooper
wrote:
>
> On 14/06/16 03:13, Meng Xu wrote:
> > On Mon, Jun 13, 2016 at 6:54 PM, Andrew Cooper
> > wrote:
> >> On 13/06/2016 18:43, Meng Xu wrote:
> >>> Hi,
> >>>
> >>> I have a quick question about using the Linux spin_lock() in Xen
> >>> environm
Running F23 here seemed to go trough good with above URL (making up much
for my environment).
The only part causing me trouble is page specific direction setting the
branch:
$ cd xen;
*git checkout -b staging staging*
Instead I did here (and think it should be)
$ cd xen; *git checkout -b stagi
On 6/14/2016 4:09 AM, Andrew Cooper wrote:
On 14/06/16 10:03, Jan Beulich wrote:
... instead of using -ENODEV for any kind of error. It in particular
addresses Coverity ID 1362694 (introduced by commit eb48587210 ["AMD
IOMMU: introduce support for IVHD block type 11h"]).
Coverity ID: 1362694
S
>>> On 15.06.16 at 16:56, wrote:
> On 06/15/2016 10:39 AM, Jan Beulich wrote:
> On 15.06.16 at 16:32, wrote:
>>> So perhaps we shouldn't latch data for anything over page size.
>> But why? What we latch is the start of the accessed range, so
>> the repeat count shouldn't matter?
>
> Because
On Fri, Jun 10, 2016 at 04:03:30PM +0100, Safa Hamza wrote:
> i'm really confused
> i build xen from the source in pc running ubuntu mate but while trying to
Take a look at
http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source#Build_Dependencies_-_Debian_.2F_Ubuntu
and follow the directions t
flight 95724 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95724/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 3 host-install(3) broken REGR. vs. 94856
test-amd64-i386-xl
On 06/15/2016 10:39 AM, Jan Beulich wrote:
On 15.06.16 at 16:32, wrote:
>> So perhaps we shouldn't latch data for anything over page size.
> But why? What we latch is the start of the accessed range, so
> the repeat count shouldn't matter?
Because otherwise we won't emulate full stos (or mov
>>> On 15.06.16 at 16:31, wrote:
> Signed-off-by: Wei Liu
Acked-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Wed, Jun 15, 2016 at 09:39:24AM -0500, Doug Goldstein wrote:
> On 6/15/16 9:31 AM, Wei Liu wrote:
[...]
> > -#ifndef NDEBUG
> > /* Permit use of the Forced Emulation Prefix in HVM guests */
> > extern bool_t opt_hvm_fep;
> > -#else
> > -#define opt_hvm_fep 0
> > -#endif
>
> Please instead add
On 6/15/16 9:31 AM, Wei Liu wrote:
> Originally hvm_fep was guarded by NDEBUG, which means it was only
> available to debug builds.
>
> However there is value to have it for non-debug builds as well. User can
> use that to run tests in setup that replicates production setup.
>
> Make it clear wit
>>> On 15.06.16 at 16:32, wrote:
> So perhaps we shouldn't latch data for anything over page size.
But why? What we latch is the start of the accessed range, so
the repeat count shouldn't matter?
> Something like this (it seems to work):
I'm rather hesitant to take a change like this without un
>>> On 15.06.16 at 16:20, wrote:
> On 06/15/2016 10:07 AM, Jan Beulich wrote:
> On 15.06.16 at 15:58, wrote:
>>> Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
Apart from that, and just to see whether there are other differences
between your guest(s) and mine, could you post a gue
On 06/15/2016 10:20 AM, Boris Ostrovsky wrote:
> On 06/15/2016 10:07 AM, Jan Beulich wrote:
> On 15.06.16 at 15:58, wrote:
>>> Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
Apart from that, and just to see whether there are other differences
between your guest(s) and mine, could y
Wei Liu (2):
xen/kernel: document 'C' in print_tainted
xen: make available hvm_fep to non-debug build as well
docs/misc/xen-command-line.markdown | 8 ++--
xen/arch/x86/hvm/hvm.c | 31 ---
xen/common/kernel.c | 7 +--
xen/incl
Originally hvm_fep was guarded by NDEBUG, which means it was only
available to debug builds.
However there is value to have it for non-debug builds as well. User can
use that to run tests in setup that replicates production setup.
Make it clear with a sync_console style warning that this option c
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
xen/common/kernel.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/common/kernel.c b/xen/common/kernel.c
On Tue, Jun 14, 2016 at 12:36:09PM +0100, Andrew Cooper wrote:
> On 14/06/16 11:54, Jan Beulich wrote:
> On 14.06.16 at 12:47, wrote:
> >> Andrew and I had a short conversation on IRC about why hvm_fep is only
> >> available to debug build. Here is what he said:
> >>
> >> liuw: because hvm_f
On 06/15/2016 10:07 AM, Jan Beulich wrote:
On 15.06.16 at 15:58, wrote:
>> Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
>>> Apart from that, and just to see whether there are other differences
>>> between your guest(s) and mine, could you post a guest config from
>>> one that's affected?
Heya!
Please put on the 4.6 stable tree these two following patches:
2a6f71a xen-blkfront: fix resume issues after a migration
efd1535 xen-blkfront: don't call talk_to_blkback when already connected to
blkback
And for the 4.5 stable tree:
2a6f71a xen-blkfront: fix resume issues after a migrati
On Wed, Jun 15, 2016 at 09:39:00AM +0100, Ross Lagerwall wrote:
> On 06/08/2016 03:47 PM, Konrad Rzeszutek Wilk wrote:
> >On Wed, Jun 08, 2016 at 02:46:38PM +0800, Bob Liu wrote:
> >>
> >>On 06/07/2016 11:25 PM, Konrad Rzeszutek Wilk wrote:
> >>>On Wed, Jun 01, 2016 at 01:49:23PM +0800, Bob Liu wro
>>> On 15.06.16 at 15:58, wrote:
> Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
>> Apart from that, and just to see whether there are other differences
>> between your guest(s) and mine, could you post a guest config from
>> one that's affected?
>
> Hope you are not too disappointed it's rath
On Wed, 15 Jun 2016, George Dunlap wrote:
> On 15/06/16 11:53, Stefano Stabellini wrote:
> > On Wed, 15 Jun 2016, George Dunlap wrote:
> >> On 15/06/16 11:24, Stefano Stabellini wrote:
> >>> On Tue, 14 Jun 2016, George Dunlap wrote:
> On 14/06/16 11:01, Stefano Stabellini wrote:
> > On Tue
On Wed, Jun 15, 2016 at 02:14:15AM -0600, Jan Beulich wrote:
> >>> On 14.06.16 at 18:33, wrote:
> >> +/* Check for continuation if it's not the last iteration. */
> >> +if ( limit > ++bulk->start && hypercall_preempt_check() )
> >
> > I surprised the compiler didn't complain to yo
On Wed, Jun 15, 2016 at 09:08:46AM +0100, Ross Lagerwall wrote:
> On 06/14/2016 04:35 PM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Jun 10, 2016 at 12:02:44PM +0100, Ross Lagerwall wrote:
> >>Remove the old --xen-debug option, and instead, require the user to pass
> >>a .config file matching the orig
Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
On 15.06.16 at 14:00, wrote:
>> Wednesday, June 15, 2016, 12:12:37 PM, you wrote:
>> On 15.06.16 at 11:38, wrote:
Wednesday, June 15, 2016, 10:57:03 AM, you wrote:
> Wednesday, June 15, 2016, 10:29:37 AM, you wrote:
> On
Xen will crash on platform where GICv2m is not available with the
following error:
(XEN) Can't find ranges property for the gic node
(XEN) Device tree generation failed (-15).
(XEN)
(XEN)
(XEN) Panic on CPU 0:
(XEN) Could not set up DOM0 guest OS
(XEN)
On Wed, Jun 15, 2016 at 03:31:46PM +0200, Dario Faggioli wrote:
> On Wed, 2016-06-15 at 10:31 +0100, Wei Liu wrote:
> > This function is used to return the memory needed for a guest. It's
> > not
> > in a position to modify the b_info passed in (note the _setdefault
> > function).
> >
> > Use a co
On Wed, 2016-06-15 at 10:31 +0100, Wei Liu wrote:
> It interrogates QEMU for CPUs and update the bitmap accordingly.
>
> Signed-off-by: Wei Liu
> ---
> Cc: Ian Jackson
> Cc: Anthony PERARD
>
Reviewed-by: Dario Faggioli
Regards,
Dario
--
<> (Raistlin Majere)
-
On Wed, 2016-06-15 at 10:31 +0100, Wei Liu wrote:
> This function is used to return the memory needed for a guest. It's
> not
> in a position to modify the b_info passed in (note the _setdefault
> function).
>
> Use a copy of b_info to do the calculation. Define a macro to mark
> the
> change in A
On Wed, 2016-06-15 at 10:31 +0100, Wei Liu wrote:
> Factor out the logic to determine device model version to a function.
> It
> will be used later. Note that code now also checks if the stbudom
> field
> is actually set before trying to extract a value from it.
>
> No functional change.
>
> Sign
Drop xen-devel to BCC, add xen-users
This question is more suitable for xen-users.
On Wed, Jun 15, 2016 at 05:45:52PM +0430, sepanta s wrote:
> Hi,
>
> after installing xen 4.7, the output of xl list is empty and
> dom0 is not found. what could be the problem ?
> The dmesg content is attached.
Hi,
after installing xen 4.7, the output of xl list is empty and
dom0 is not found. what could be the problem ?
The dmesg content is attached.
Xen 4.7.0-rc
(XEN) Xen version 4.7.0-rc (root@) (gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4)
debug=y Wed Jun 15 17:30:18 IRDT 2016
(XEN) Latest ChangeSet:
On 15/06/16 13:59, Jan Beulich wrote:
On 15.06.16 at 13:03, wrote:
>> On 15/06/16 08:55, Jan Beulich wrote:
> @@ -570,6 +600,15 @@ void fatal_trap(const struct cpu_user_re
> printk("Faulting linear address: %p\n", _p(cr2));
> show_page_walk(cr2);
>
>>> On 15.06.16 at 12:45, wrote:
> In reply to -
> http://lists.xen.org/archives/html/xen-devel/2016-06/msg00622.html
>
> HI, I am working with Jurgen on the issue, as per Jan's request I tried to
> write explicitly only latency timer to be written -
> bool force_write = false;
> if ((dev_data->
Initialise j to 0 to make some versions of gcc (e.g., gcc4.5/4.3) happy to
avoid compilation error by commit beba3693f7243e68bbe31fe3794da91068eeea5b.
Signed-off-by: Dongli Zhang
---
tools/misc/xen-livepatch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/misc/xen-liv
>>> On 15.06.16 at 13:03, wrote:
> On 15/06/16 08:55, Jan Beulich wrote:
@@ -570,6 +600,15 @@ void fatal_trap(const struct cpu_user_re
printk("Faulting linear address: %p\n", _p(cr2));
show_page_walk(cr2);
}
+else if ( trapnr == T
>>> On 15.06.16 at 14:00, wrote:
> Wednesday, June 15, 2016, 12:12:37 PM, you wrote:
> On 15.06.16 at 11:38, wrote:
>>> Wednesday, June 15, 2016, 10:57:03 AM, you wrote:
Wednesday, June 15, 2016, 10:29:37 AM, you wrote:
On 15.06.16 at 01:49, wrote:
>> Just tested latest xen
>>> On 15.06.16 at 12:52, wrote:
> On 6/14/2016 6:45 PM, Jan Beulich wrote:
> On 19.05.16 at 11:05, wrote:
>>> A new HVMOP - HVMOP_map_mem_type_to_ioreq_server, is added to
>>> let one ioreq server claim/disclaim its responsibility for the
>>> handling of guest pages with p2m type p2m_ioreq_s
Wednesday, June 15, 2016, 12:12:37 PM, you wrote:
On 15.06.16 at 11:38, wrote:
>> Wednesday, June 15, 2016, 10:57:03 AM, you wrote:
>>
>>> Wednesday, June 15, 2016, 10:29:37 AM, you wrote:
>>
>>> On 15.06.16 at 01:49, wrote:
> Just tested latest xen-unstable 4.8 (xen_changeset gi
On Tue, Jun 14, 2016 at 12:32:19PM +0200, Andrea Genuise wrote:
[...]
> libxl: debug: libxl_aoutils.c:88:xswait_timeout_callback: backend
> /local/domain/748/backend/vtpm/749/0/state (hoping for state change to 6):
> xswait timeout (path=/local/domain/748/backend/vtpm/749/0/state)
> libxl: debug: l
On 15/06/16 11:46, Jan Beulich wrote:
On 15.06.16 at 12:30, wrote:
>> On 15/06/16 11:25, Jan Beulich wrote:
>> On 15.06.16 at 12:13, wrote:
On 15/06/16 11:04, Jan Beulich wrote:
On 15.06.16 at 11:35, wrote:
>> The version of qemu-xen that was tagged with 4.6 had been t
A guest mapping vcpu_runstate_info into its memory can't read this
information from another cpu but the one the data is referring to.
Reason is there is no reliable way for the guest to detect a concurrent
data update by the hypervisor.
This patch series adds an update flag to the mapped data whic
Up to now the vm_assist hypercall hasn't been supported on ARM, as
there are only x86 specific features to switch. Add support of
vm_assist on ARM for future use.
Signed-off-by: Juergen Gross
Reviewed-by: Julien Grall
---
V2: readded the #ifdef's as requested by Jan Beulich
---
xen/arch/arm/tra
In order to support reading another vcpu's mapped vcpu_runstate_info
an indicator for an occurring update of the runstate information is
needed.
Add the possibility to activate setting this indicator in the highest
bit of state_entry_time via a vm_assist hypercall. When activated the
update indica
flight 95718 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95718/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-migrupgrade 3 host-install/src_host(3) broken in 95645 pass
in 95718
test-amd64-amd64-xl-qem
On 15/06/16 11:21, Jan Beulich wrote:
>> I think you've tripped over "changing coding styles" in unfamiliar code
>> before too, so you know how frustrating it is to try to follow the
>> existing coding style only to be told that you did it wrong. :-)
>
> Agreed, you caught me on this one. Albeit w
On 06/04/16 16:17, Juergen Gross wrote:
Use smp_call_on_cpu() to raise SMI on cpu 0.
Make call secure by adding get_online_cpus() to avoid e.g. suspend
resume cycles in between.
Signed-off-by: Juergen Gross
Could please some maintainer comment on this patch?
Juergen
---
V4: add call to ge
On 06/04/16 16:17, Juergen Gross wrote:
Add generic virtualization support for pinning the current vcpu to a
specified physical cpu. As this operation isn't performance critical
(a very limited set of operations like BIOS calls and SMIs is expected
to need this) just add a hypervisor specific ind
This series deals with hard-coded /var/run in code.
Wei Liu (7):
xenconsoled: honour XEN_RUN_DIR
tools/helper: honour XEN_RUN_DIR in init-xenstore-domain.c
hotplug/FreeBSD: honour XEN_RUN_DIR
hotplug/NetBSD: honour XEN_RUN_DIR
hotplug/Linux: honour XEN_RUN_DIR
libxenstat: honour XEN_RU
Move default the pid file under XEN_RUN_DIR. Note that it changes the
location from /var/run to /var/run/xen.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Dave Scott
---
tools/ocaml/xenstored/xenstored.ml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/ocaml/xenstor
This is because libxl uses XEN_RUN_DIR to generate the socket path for
libxenstat while libxenstat itself uses hard-coded path, which is not
necessary in sync with libxl.
Generate a _paths.h because it is required to make this change work.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
---
.gitign
Store various PID files under XEN_RUN_DIR. Note that this change the
default location from /var/run to /var/run/xen.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Roger Pau Monné
---
tools/hotplug/Linux/init.d/xencommons.in | 6 +++---
tools/hotplug/Linux/init.d/xendriverdomain.in | 2 +-
1 - 100 of 172 matches
Mail list logo
