On Mon, Jun 13, 2016 at 12:59 PM, Wei Liu wrote:
> On Sun, Jun 12, 2016 at 02:37:29PM +0430, sepanta s wrote:
> > Hi,
> >
> > how to does MEM_SHARING_DEBUG works in xen ?
> > This function is located at and its internal structure is
> > xen/arch/x86/mm/mem_sharing.c
> > <
> https://github.com/mir
When trying to use xl cpupool-numa-split and dom0 is limited to less
vcpus than one numa node the operation will fail.
Correct this by allowing this configuration.
Reported-by: Glenn Enright
Signed-off-by: Juergen Gross
---
tools/libxl/xl_cmdimpl.c | 8 ++--
1 file changed, 6 insertions(+)
flight 95631 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95631/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-freebsd10-amd64 3 host-install(3)broken pass in 95557
test-amd64-i386-xl-qemuu-winxps
flight 95638 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95638/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 95460
build-amd64-libvirt
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
>> environment to protect some host-wide shared (memory) resource among
>> VMs.
>>
>> *** The question is as follows ***
>> Supp
On Mon, Jun 13, 2016 at 5:17 PM, Boris Ostrovsky
wrote:
> On 06/13/2016 04:46 PM, Meng Xu wrote:
>> On Mon, Jun 13, 2016 at 2:28 PM, Boris Ostrovsky
>> wrote:
>>> On 06/13/2016 01:43 PM, Meng Xu wrote:
Hi,
I have a quick question about using the Linux spin_lock() in Xen
enviro
flight 95622 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95622/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 94748
test-amd64-amd64-
Hello all,
Sorry to disturb you, but I really want to figure it out.
The xen core of redhat 6 with pod is unable to be used with crash.
I installed a hvm of redhat 6 by xen 4.7.0-rc2.
And the memory is set as below:
memory=1024
maxmem=4096
"xl dump-core" is executed, and the core is produced suc
On 06/12/2016 11:01 PM, osstest service owner wrote:
> flight 95577 libvirt real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/95577/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386-libvirt5 libvir
On 13/06/2016 18:43, Meng Xu wrote:
> Hi,
>
> I have a quick question about using the Linux spin_lock() in Xen
> environment to protect some host-wide shared (memory) resource among
> VMs.
>
> *** The question is as follows ***
> Suppose I have two Linux VMs sharing the same spinlock_t lock (throug
flight 95615 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95615/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-libvirt 3 host-install(3) broken pass in 95550
test-armhf-armhf-xl-arndale 15
On 06/13/2016 04:46 PM, Meng Xu wrote:
> On Mon, Jun 13, 2016 at 2:28 PM, Boris Ostrovsky
> wrote:
>> On 06/13/2016 01:43 PM, Meng Xu wrote:
>>> Hi,
>>>
>>> I have a quick question about using the Linux spin_lock() in Xen
>>> environment to protect some host-wide shared (memory) resource among
>>>
On Mon, Jun 13, 2016 at 2:28 PM, Boris Ostrovsky
wrote:
> On 06/13/2016 01:43 PM, Meng Xu wrote:
>> Hi,
>>
>> I have a quick question about using the Linux spin_lock() in Xen
>> environment to protect some host-wide shared (memory) resource among
>> VMs.
>>
>> *** The question is as follows ***
>>
> On 13 Jun 2016, at 16:22, Wei Liu wrote:
>
> On Mon, Jun 13, 2016 at 04:19:59PM +0100, Ian Jackson wrote:
>> Wei Liu writes ("[PATCH 14/17] ocaml/libxs: generate a paths.ml"):
>>> Signed-off-by: Wei Liu
>>
>> FAOD I don't consider myself qualified to review this.
>>
>
> David gave his ack
On Mon, 13 Jun 2016, Roger Pau Monné wrote:
> On Fri, Jun 10, 2016 at 09:38:59PM +, Marcin Cieslak wrote:
> > "?" does not work - it mostly causes a panic, the console is slow, but I
> > managed
> > to switch it to /dev/ada0p2, dmesg below:
>
> This has now been reverted, so when I import th
flight 95602 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95602/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl 15 guest-start/debian.repeat fail in 95527 pass in 95602
test-armhf-armhf-xl-r
On Wednesday 06 April 2016 16:17:46 Juergen Gross wrote:
> Use the smp_call_on_cpu() function to call system management
> mode 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
> ---
> V4: add call to get_on
3.16.36-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 103f6112f253017d7062cd74d17f4a514ed4485c upstream.
Huge pages are not normally available to PV guests. Not suppressing
hugetlbfs use results in an endless loop of page fault
On 06/13/2016 01:43 PM, Meng Xu wrote:
> Hi,
>
> I have a quick question about using the Linux spin_lock() in Xen
> environment to protect some host-wide shared (memory) resource among
> VMs.
>
> *** The question is as follows ***
> Suppose I have two Linux VMs sharing the same spinlock_t lock (thr
On Mon, Jun 13, 2016 at 06:39:36PM +0100, Anthony PERARD wrote:
> On Wed, Jun 08, 2016 at 03:28:45PM +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 o
On Mon, Jun 13, 2016 at 05:52:14PM +0100, Anthony PERARD wrote:
> On Wed, Jun 08, 2016 at 03:28:44PM +0100, Wei Liu wrote:
> > diff --git a/tools/libxl/libxl_qmp.c b/tools/libxl/libxl_qmp.c
> > index 3eb279a..23eac92 100644
> > --- a/tools/libxl/libxl_qmp.c
> > +++ b/tools/libxl/libxl_qmp.c
> > @@
On Mon, Jun 13, 2016 at 05:57:26PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH 08/17] tools: remove hard-coded /var/lib/xen in
> Makefile"):
> > On Mon, Jun 13, 2016 at 05:07:11PM +0100, Ian Jackson wrote:
> > > Mmmm. So maybe we should just drop this now.
> >
> > Drop what? Drop the
flight 95597 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95597/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 13 xen-boot/l1fail REGR. vs. 94728
Tests which are failin
On Wed, Jun 08, 2016 at 03:28:46PM +0100, Wei Liu wrote:
> Calculate the final bitmap for CPUs to add to avoid having annoying
> error messages complaining those CPUs are already present.
>
> We can also properly handle error from QMP now.
>
> Signed-off-by: Wei Liu
Reviewed-by: Anthony PERARD
On Wed, Jun 08, 2016 at 03:28:45PM +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.
I
Hi,
I have a quick question about using the Linux spin_lock() in Xen
environment to protect some host-wide shared (memory) resource among
VMs.
*** The question is as follows ***
Suppose I have two Linux VMs sharing the same spinlock_t lock (through
the sharing memory) on the same host. Suppose we
On 06/13/2016 05:30 AM, Stefano Stabellini wrote:
On Thu, 9 Jun 2016, Shanker Donthineni wrote:
The Masked interrupt status register (UARTMIS) is not described in ARM
SBSA 2.x document. Anding of two registers UARTMSC and UARTRIS values
gives the same information as register UARTMIS.
UARTRIS,
On 13/06/16 18:19, Shanker Donthineni wrote:
Julien,
Hello,
Please avoid top-posting.
The problem that was reported earlier related to our platform drivers in
domn0 kernel. I have verified your patches and works fine without any
dead-lock.
Good, thank you!
Regards,
--
Julien Grall
_
On Mon, Jun 13, 2016 at 3:28 AM, George Dunlap wrote:
> On 11/06/16 18:55, Tamas K Lengyel wrote:
>> On Thu, May 26, 2016 at 10:17 AM, Tamas K Lengyel
>> wrote:
>>>
>>> On May 26, 2016 04:40, "George Dunlap" wrote:
On 26/05/16 04:55, Tamas K Lengyel wrote:
> Move sharing locks abo
Julien,
The problem that was reported earlier related to our platform drivers in
domn0 kernel. I have verified your patches and works fine without any
dead-lock.
On 06/13/2016 06:42 AM, Julien Grall wrote:
On 08/06/16 13:34, Julien Grall wrote:
On 08/06/16 13:11, Shanker Donthineni wrote
Hi Konrad,
I noticed the warnings below when building Xen x86
with Livepatch enabled.
/local/home/julieng/works/xen/xen/.xen.efi.0s.S: Assembler messages:
/local/home/julieng/works/xen/xen/.xen.efi.0s.S:21: Warning: value
0x7d2f8591 truncated to 0x8591
/local/home/julieng/works/xen/xen/.
Wei Liu writes ("Re: [PATCH 08/17] tools: remove hard-coded /var/lib/xen in
Makefile"):
> On Mon, Jun 13, 2016 at 05:07:11PM +0100, Ian Jackson wrote:
> > Mmmm. So maybe we should just drop this now.
>
> Drop what? Drop the uninstall target all together? Or just the rune in
> this patch?
I mean
On Wed, Jun 08, 2016 at 03:28:44PM +0100, Wei Liu wrote:
> diff --git a/tools/libxl/libxl_qmp.c b/tools/libxl/libxl_qmp.c
> index 3eb279a..23eac92 100644
> --- a/tools/libxl/libxl_qmp.c
> +++ b/tools/libxl/libxl_qmp.c
> @@ -979,6 +979,43 @@ int libxl__qmp_cpu_add(libxl__gc *gc, int domid, int idx)
I'm not sure if this is a bug or my fault, but when I create a domain
with a vTPM attached, detaching it sometimes causes the following error
to be thrown (I post the command sequence):
[root@localhost ~]# xl create /etc/xen/vtpmmgr-stubdom
Parsing config from /etc/xen/vtpmmgr-stubdom
[root@localh
On Mon, Jun 13, 2016 at 4:17 PM, Xu, Quan wrote:
> From: Quan Xu
>
> Propagate the IOMMU Device-TLB flush error up to the ept_set_entry(),
> when VT-d shares EPT page table.
>
> Signed-off-by: Quan Xu
> Acked-by: Kevin Tian
> Reviewed-by: Jan Beulich
Acked-by: George Dunlap
>
> CC: Jun Naka
On Mon, Jun 13, 2016 at 4:17 PM, Xu, Quan wrote:
> From: Quan Xu
>
> When IOMMU mapping is failed, we issue a best effort rollback, stopping
> IOMMU mapping, unmapping the previous IOMMU maps and then reporting the
> error up to the call trees. When rollback is not feasible (in early
> initializa
On Mon, Jun 13, 2016 at 05:07:11PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH 08/17] tools: remove hard-coded /var/lib/xen in
> Makefile"):
> > TBH I think the uninstall target has been broken for a long time. I
> > merely added the rm rune for completeness. Last time I tried it didn
Wei Liu writes ("Re: [PATCH 08/17] tools: remove hard-coded /var/lib/xen in
Makefile"):
> TBH I think the uninstall target has been broken for a long time. I
> merely added the rm rune for completeness. Last time I tried it didn't
> remove things cleanly. For one there is no rune to remove system
>>> "Xu, Quan" 06/13/16 5:22 PM >>>
>From: Quan Xu
>
>The propagation value from IOMMU flush interfaces may be positive, which
>indicates callers need to flush cache, not one of faliures.
>
>when the propagation value is positive, this patch fixes this flush issue
>as follows:
>- call iommu_flush
flight 95662 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95662/
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
>>> "Xu, Quan" 06/13/16 5:22 PM >>>
>From: Quan Xu
>
>When IOMMU mapping is failed, we issue a best effort rollback, stopping
>IOMMU mapping, unmapping the previous IOMMU maps and then reporting the
>error up to the call trees. When rollback is not feasible (in early
>initialization phase or trad
On Mon, Jun 13, 2016 at 04:13:26PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 08/17] tools: remove hard-coded /var/lib/xen in
> Makefile"):
> > Now all conversations are done, remove the hard-coded paths.
>
> Should we not keep these for (most of) a release cycle ?
>
> Otherwise someone
On Mon, Jun 13, 2016 at 04:19:59PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 14/17] ocaml/libxs: generate a paths.ml"):
> > Signed-off-by: Wei Liu
>
> FAOD I don't consider myself qualified to review this.
>
David gave his ack to a similar path so I presume he will be fine with
this,
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
---
xen/drivers/passthrough/arm/smmu.c | 13 -
xen/drivers/passthrough/iommu.c | 8 ++--
xen/driver
From: Quan Xu
Propagate the IOMMU Device-TLB flush error up to the ept_set_entry(),
when VT-d shares EPT page table.
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Jun Nakajima
CC: Kevin Tian
CC: George Dunlap
CC: Jan Beulich
CC: Andrew Cooper
CC: Feng Wu
---
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Acked-by: Suravee Suthikulpanit
CC: Jan Beulich
CC: Liu Jinsong
CC: Keir Fraser
CC: Andrew Cooper
CC: Suravee Suthikulpanit
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
v8: enhance the error check of dev
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
---
xen/drivers/passthrough/vtd/extern.h | 3 ++-
xen/drivers/passthrough/vtd/iommu.c | 8
xen/drivers/passthrough/vtd/quirks.c | 27 +-
From: Quan Xu
This patch set is a prereq patch set for Patch:'VT-d Device-TLB flush issue'.
While IOMMU Device-TLB flush timed out, xen calls panic() at present. However
the existing panic()
is going to be eliminated, so we must propagate the IOMMU Device-TLB flush
error up to the call trees.
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Acked-by: Suravee Suthikulpanit
Acked-by: Julien Grall
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
CC: Jan Beulich
CC: Andrew Cooper
CC: Suravee Suthikulpanit
---
xen/drivers/pa
From: Quan Xu
The propagation value from IOMMU flush interfaces may be positive, which
indicates callers need to flush cache, not one of faliures.
when the propagation value is positive, this patch fixes this flush issue
as follows:
- call iommu_flush_write_buffer() to flush cache.
- return
From: Quan Xu
When IOMMU mapping is failed, we issue a best effort rollback, stopping
IOMMU mapping, unmapping the previous IOMMU maps and then reporting the
error up to the call trees. When rollback is not feasible (in early
initialization phase or trade-off of complexity) for the hardware domai
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
---
xen/drivers/passthrough/vtd/iommu.c | 50 ++--
xen/drivers/passthrough/vtd/iommu.h | 11 +---
xen/drivers/passthrough/vtd
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Acked-by: Suravee Suthikulpanit
Reviewed-by: Jan Beulich
CC: Suravee Suthikulpanit
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
CC: Jan Beulich
CC: Andrew Cooper
v8: use the Linux coding style for arm cod
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Julien Grall
Reviewed-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Kevin Tian
---
xen/arch/arm/p2m.c | 4 +++-
xen/common/memory.c | 12 ++--
x
From: Quan Xu
Treat IOMMU mapping and unmapping failures as a fatal to the DomU
If IOMMU mapping and unmapping failed, crash the DomU and propagate
the error up to the call trees.
No spamming of the log can occur. For DomU, we avoid logging any
message for already dying domains. For Dom0, that'l
Wei Liu writes ("[PATCH 13/17] hotplug/FreeBSD: honour XEN_RUN_STORED"):
> Signed-off-by: Wei Liu
> ---
> Cc: Ian Jackson
> Cc: Roger Pau Monné
Acked-by: Ian Jackson
We should probably get an ack from Roger too.
Ian.
___
Xen-devel mailing list
Xen
Wei Liu writes ("[PATCH 14/17] ocaml/libxs: generate a paths.ml"):
> Signed-off-by: Wei Liu
FAOD I don't consider myself qualified to review this.
Ian.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Wei Liu writes ("[PATCH 11/17] hotplug/Linux: honour XEN_RUN_STORED"):
> Signed-off-by: Wei Liu
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Wei Liu writes ("[PATCH 12/17] libxenstore: honour XEN_RUN_STORED"):
> Signed-off-by: Wei Liu
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Wei Liu writes ("[PATCH 09/17] docs: honour XEN_DUMP_DIR"):
> Use configure to generate xl.cfg and xl manpage. Add the generated files
> to gitignore.
...
> Not entirely sure if this is a good idea. I don't deem this patch
> important so I'm fine with dropping it.
It seems like a lot of effort to
flight 95591 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95591/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-amd64 10 guest-startfail REGR. vs. 94729
Tests which are failing
Wei Liu writes ("[PATCH 08/17] tools: remove hard-coded /var/lib/xen in
Makefile"):
> Now all conversations are done, remove the hard-coded paths.
Should we not keep these for (most of) a release cycle ?
Otherwise someone who tries to use the new feature in 4.8 will find it
doesn't uninstall the
Wei Liu writes ("[PATCH 07/17] libxl: honour XEN_LIB_DIR"):
> Signed-off-by: Wei Liu
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Wei Liu writes ("[PATCH 06/17] hotplug/Linux: honour XEN_LIB_DIR"):
> Use configure to generate sysconfig.xendomains file.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-de
Wei Liu writes ("[PATCH 05/17] tools: install and remove XEN_LIB_DIR in
Makefile"):
> The intention of using wild card in uninstall target is to remove both
> xen and xenstored directories. Change that to two runes that explicitly
> remove each of those directories.
>
> Note that the runes that u
Wei Liu writes ("[PATCH 04/17] build: introduce and export XEN_LIB_DIR"):
> This variable defaults to /var/lib/xen. It will be used to substitute
> various hard-coded paths in tools.
>
> The new variable points to $localstatedir/lib/xen, which defaults to
> /var/lib/xen, so there is no change in d
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.
Singed-off-by: George Dunlap
---
CC: Stefan
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
---
CC: Stefano Stabellini
---
components/qemu | 21 +
components/qemu_tradition
So that we're not duplicating information.
Signed-off-by: George Dunlap
---
CC: Stefano Stabellini
---
configs/config-4.5 | 39 ---
configs/config-4.6 | 39 ---
configs/config-master | 38 ---
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
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
Update to 4.7, update qemu and qemu_traditional recipes
components/qemu | 21
compone
flight 95604 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95604/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3863 host-install(3) broken REG
George Dunlap writes ("Re: [Xen-devel] xenbits "official" repo for XTF (was Re:
[PATCH 0/2] xtf: add launcher (+1 bugfix)"):
> On Mon, Jun 13, 2016 at 11:10 AM, Andrew Cooper
> > I am not completely averse to changing it, but I don't see an
> > alternative which is any better or clearer.
>
> Do y
On Mon, Jun 13, 2016 at 11:10 AM, Andrew Cooper
wrote:
> On 09/06/16 16:04, Ian Jackson wrote:
>> Roger Pau Monne writes ("[Xen-devel] [PATCH 0/2] xtf: add launcher (+1
>> bugfix)"):
>>> This series contains a bugfix for the build infrastructure and a basic
>>> launcher for XTF. Patches can also
On Mon, 13 Jun 2016, Jan Beulich wrote:
> May I ask what the disposition of "xen/blkif: avoid double access to
> any shared ring request fields" is? I don't think I've seen a pull req,
> and it doesn't appear to be in master.
I miscategorized it, sorry. It is going to be in the next pull request.
George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6,
vnc.c, qemu-tradintional issues under ubuntu 16.04"):
> The original report actually had 3 different issues -- the one I'm
> re-raising was the one I'm personally still tripping over. (Don't
> know about the other two.)
Th
> -Original Message-
[snip]
> >
> > No, I meant the guest receive-side copy didn't scale, not grant table v2
> itself. Ok the table is bigger with v2, but to do guest receive-side copy
> required a huge table in dom0 if it was going to scale to 100s of VMs and the
> perf. benefits were neve
flight 95652 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95652/
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 13/06/16 13:45, Paul Durrant wrote:
-Original Message-
From: Julien Grall [mailto:julien.gr...@arm.com]
Sent: 13 June 2016 13:42
To: Paul Durrant; boris.ostrov...@oracle.com; David Vrabel;
jgr...@suse.com; sstabell...@kernel.org; konrad.w...@oracle.com
Cc: Andrew Cooper; xen-devel@li
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 13 June 2016 13:42
> To: Paul Durrant; boris.ostrov...@oracle.com; David Vrabel;
> jgr...@suse.com; sstabell...@kernel.org; konrad.w...@oracle.com
> Cc: Andrew Cooper; xen-devel@lists.xen.org; linux-ker...@vger.
On 13/06/16 13:41, Julien Grall wrote:
Hello Paul,
On 13/06/16 13:12, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 13 June 2016 11:51
To: boris.ostrov...@oracle.com; David Vrabel; jgr...@suse.com;
sstab
Hello Paul,
On 13/06/16 13:12, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 13 June 2016 11:51
To: boris.ostrov...@oracle.com; David Vrabel; jgr...@suse.com;
sstabell...@kernel.org; konrad.w...@oracle.com
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> Julien Grall
> Sent: 13 June 2016 12:10
> To: David Vrabel; boris.ostrov...@oracle.com; jgr...@suse.com;
> sstabell...@kernel.org; konrad.w...@oracle.com
> Cc: Andrew Cooper; steve.cap...@arm.com;
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> Julien Grall
> Sent: 13 June 2016 11:51
> To: boris.ostrov...@oracle.com; David Vrabel; jgr...@suse.com;
> sstabell...@kernel.org; konrad.w...@oracle.com
> Cc: steve.cap...@arm.com; Andrew Cooper;
flight 95585 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95585/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-amd 13 xen-boot/l1 fail REGR. vs. 95164
test-amd64-amd64-qemuu
On 09/06/16 11:14, Euan Harris wrote:
> nvmx_msr_read_intercept() does not check the prerequisites before
> accessing MSR_IA32_VMX_PROCBASED_CTLS2, MSR_IA32_VMX_EPT_VPID_CAP,
> MSR_IA32_VMX_VMFUNC on the host. Accessing these MSRs from a nested
> VMX guest running on a host which does not support
ble in the git repository at:
>
>
> git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-20160613-tag
>
> for you to fetch changes up to 88c16567d2cd23da328787187910b013ee43ebca:
>
> Introduce &q
the git repository at:
>
>
> git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-20160613-tag
>
> for you to fetch changes up to 88c16567d2cd23da328787187910b013ee43ebca:
>
> Introduce "xen-load-devices-state" (2016-06-13 11:50:53 +0100)
>
> ---
On 08/06/16 13:34, Julien Grall wrote:
On 08/06/16 13:11, Shanker Donthineni wrote:
I don't know exactly which of the patch causing the issue. I have
noticed a couple of drivers are not receiving SPI interrupts in DOM0.
I need to digest your patches before tracing/investigate the problem
to ge
flight 95612 xen-unstable running [real]
http://logs.test-lab.xenproject.org/osstest/logs/95612/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 queued
test-amd64-i386-
flight 95625 xen-4.7-testing running [real]
http://logs.test-lab.xenproject.org/osstest/logs/95625/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 queued
test-amd64-amd6
Hello Georg,
first of all thank you for answering.
Am 13.06.2016 um 12:15 schrieb George Dunlap:
> On Fri, Jun 10, 2016 at 4:22 PM, Philipp Hahn wrote:
>> while trying to live migrate some VMs from an xen-4.1.6.1 host "xc_save"
>> crashes with a segmentation fault in tools/libxc/xc_domain_save.c
Hi David,
On 13/06/16 11:57, David Vrabel wrote:
On 13/06/16 11:50, Julien Grall wrote:
The version 1 of the grant-table protocol only supports frame encoded on
32-bit.
When the platform is supporting 48-bit physical address, the frame will
be encoded on 36-bit which will lead a truncation and
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 grant references.
>>>
>>> Before grant copy operation local buffers
On Mon, Jun 13, 2016 at 11:16 AM, Andrew Cooper
wrote:
> On 13/06/16 11:08, George Dunlap wrote:
>> On Fri, Jun 10, 2016 at 12:02 PM, Ross Lagerwall
>> wrote:
>>> When testing and applying patches, set fuzz=0 so that patches must apply
>>> exactly. Also set "-f" to avoid interactive questions, a
From: Anthony PERARD
Since f615f39 (exec: remove ram_addr argument from
qemu_ram_block_from_host), migration under Xen is likely to fail, with a
SEGV of QEMU. But the commit only reveal a bug with the calculation of
the offset value in qemu_ram_block_from_host().
This patch calculates the offset
From: Wen Congyang
Introduce a "xen-load-devices-state" QAPI command that can be used to
load the state of all devices, but not the RAM or the block devices of
the VM.
We only have hmp commands savevm/loadvm, and qmp commands
xen-save-devices-state.
We use this new command for COLO:
1. suspend
On 13/06/16 11:50, Julien Grall wrote:
> The version 1 of the grant-table protocol only supports frame encoded on
> 32-bit.
>
> When the platform is supporting 48-bit physical address, the frame will
> be encoded on 36-bit which will lead a truncation and give access to
> the wrong frame.
>
> On
t tags/xen-20160613-tag
for you to fetch changes up to 88c16567d2cd23da328787187910b013ee43ebca:
Introduce "xen-load-devices-state" (2016-06-13 11:50:53 +0100)
---
The version 1 of the grant-table protocol only supports frame encoded on
32-bit.
When the platform is supporting 48-bit physical address, the frame will
be encoded on 36-bit which will lead a truncation and give access to
the wrong frame.
On ARM Xen will always allow the guest to use all the phys
1 - 100 of 165 matches
Mail list logo
