On May 17, 2016 10:00 PM, Jan Beulich wrote:
> >>> On 22.04.16 at 12:54, wrote:
> > --- a/xen/drivers/passthrough/vtd/qinval.c
> > +++ b/xen/drivers/passthrough/vtd/qinval.c
> > @@ -206,10 +206,71 @@ static int invalidate_sync(struct iommu *iommu)
> > return 0;
> > }
> >
> > +static void de
On 19/05/16 19:15, Stefano Stabellini wrote:
> On Thu, 19 May 2016, Juergen Gross wrote:
>> The pv_time_ops structure contains a function pointer for the
>> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
>> uses its own mechanism to account for the "stolen" time a thread wa
The pv_time_ops structure contains a function pointer for the
"steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
uses its own mechanism to account for the "stolen" time a thread wasn't
able to run due to hypervisor scheduling.
Add support in Xen arch independent time handling
flight 94594 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94594/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 94588
build-amd64
flight 94592 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94592/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
> My bottom line is the error reporting mechanism needs to be preserved,
> otherwise we risk breaking other users. Libxl currently relies on those
> nodes to report error.
Got it.
Andrii Anisov | Associate Manager, Engineering
GlobalLogic
Kyiv, 03038, Protasov Business Park, M.Grinchenka, 2/1
P +
Oleksandr Dmytryshyn | Product Engineering and Development
GlobalLogic
M +38.067.382.2525
www.globallogic.com
http://www.globallogic.com/email_disclaimer.txt
On Thu, May 19, 2016 at 5:34 PM, Julien Grall wrote:
> Hello Oleksandr,
>
>
> On 19/05/16 14:58, Oleksandr Dmytryshyn wrote:
>>>
>>> Why
On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote:
On 19.05.16 at 15:58, wrote:
>> Case 1: Dom0 is driver domain:
>> There is a Ducati firmware which runs on dedicated M4 core and decodes
>> video. This firmware uses hardcoded physical addresses for graphics
>> buffers. Those addresses shou
On Thu, May 19, Meng Xu wrote:
> Does anyone try to install two version of Xen toolstack on the same machine?
I do that. See the INSTALL file which has examples at the end:
* To build a private copy of tools and xen:
configure --prefix=/odd/path --sysconfdir=/odd/path/etc --enable-rpath
make
sud
flight 94591 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94591/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 guest-saverestorefail never pass
test-armhf-armhf-libvirt 12 migrate-sup
> -Original Message-
> From: Roger Pau Monné [mailto:roger@citrix.com]
> Sent: 19 May 2016 17:28
> To: xen-de...@lists.xenproject.org
> Cc: Wei Liu; David Vrabel; Paul Durrant
> Subject: netif.h clarifications
>
> Hello,
>
> While trying to solve a FreeBSD netfront bug [0] I came acro
When the last assigned device is dettached from the domain, all
the PI related hooks are removed then, however, the vCPU can be
blocked, switched to another pCPU, etc, all without the aware of
PI. After the next time we attach another device to the domain,
which makes the PI realted hooks avaliable
The current VT-d PI related code may operate incorrectly in the following
scenarios:
- When the last assigned device is dettached from the domain, all
the PI related hooks are removed then, however, the vCPU can be
blocked, switched to another pCPU, etc, all without the aware of
PI. After the next
We need to make sure the bocking vcpu is not in any per-cpu blocking list
when the associated domain is going to be destroyed.
Signed-off-by: Feng Wu
---
xen/arch/x86/hvm/vmx/vmx.c | 32
1 file changed, 32 insertions(+)
diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/
Make hook pi_do_resume always available, so when the last
assigned device is dettached from a domain, the blocked
vcpu can be removed from the per-cpu blocking list properly.
Signed-off-by: Feng Wu
---
xen/arch/x86/hvm/vmx/vmx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
flight 94600 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94600/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 66e5133ce0a8940a99451842a804dc5a37b4b687
baseline version:
ovmf 1f1ec99dea4d6d04fed96fa8a2e299212f6
>>> On 20.05.16 at 09:15, wrote:
> On May 17, 2016 10:00 PM, Jan Beulich wrote:
>> >>> On 22.04.16 at 12:54, wrote:
>> > --- a/xen/drivers/passthrough/vtd/qinval.c
>> > +++ b/xen/drivers/passthrough/vtd/qinval.c
>> > @@ -206,10 +206,71 @@ static int invalidate_sync(struct iommu *iommu)
>> >
>>> On 20.05.16 at 10:45, wrote:
> On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote:
> On 19.05.16 at 15:58, wrote:
>>> Case 1: Dom0 is driver domain:
>>> There is a Ducati firmware which runs on dedicated M4 core and decodes
>>> video. This firmware uses hardcoded physical addresses for g
>>> On 19.05.16 at 20:40, wrote:
> Does anyone try to install two version of Xen toolstack on the same machine?
> Is there any documentation about the best practice to install two
> versions of Xen onto the same machine?
Or, as an alternative to Olaf's reply, don't install the tools at all, but
i
>>> On 20.05.16 at 10:53, wrote:
> I still have two opens, which needs comments/sugguestions from you guys.
> - What shoule we do for the per-cpu blocking list during vcpu hotplug?
What do you mean with vcpu hotplug? vcpus never get removed
from a VM (from hypervisor perspective), and all the gue
Hello Andrii,
Thank you for sharing details on your use case.
On 19/05/16 22:28, Andrii Anisov wrote:
See the system details I can reveal below:
* There are two OS in the system Linux(Dom0) and Android(DomU)
* Android provides almost all infotainment functionality. Linux covers
functio
flight 94589 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94589/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-amd64-pvgrub 3 host-install(3)broken REGR. vs. 94580
test-amd64-amd64-xl-
On Fri, May 20, 2016 at 10:09:43AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Roger Pau Monné [mailto:roger@citrix.com]
> > Sent: 19 May 2016 17:28
> > To: xen-de...@lists.xenproject.org
> > Cc: Wei Liu; David Vrabel; Paul Durrant
> > Subject: netif.h clarifications
> >
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, May 20, 2016 6:27 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
> de...@lists.xen.org; konrad.w...@oracle.com; k...@xen.or
> -Original Message-
[snip]
> > > And then I've also seen some issues with TSO/LRO (GSO in Linux
> > > terminology)
> > > when using packet forwarding inside of a FreeBSD DomU. For example in
> the
> > > following scenario:
> > >
> > >+
> > >
On Fri, 20 May 2016, Juergen Gross wrote:
> The pv_time_ops structure contains a function pointer for the
> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> uses its own mechanism to account for the "stolen" time a thread wasn't
> able to run due to hypervisor scheduling.
>
flight 94604 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94604/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
On Fri, May 20, 2016 at 12:55:16PM +0100, Paul Durrant wrote:
> > -Original Message-
> [snip]
> > > > And then I've also seen some issues with TSO/LRO (GSO in Linux
> > > > terminology)
> > > > when using packet forwarding inside of a FreeBSD DomU. For example in
> > the
> > > > following s
> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: 20 May 2016 13:34
> To: Paul Durrant
> Cc: xen-de...@lists.xenproject.org; Wei Liu; David Vrabel
> Subject: Re: netif.h clarifications
>
> On Fri, May 20, 2016 at 12:55:16PM +0100, Paul Durrant wrote:
> > >
On 18/05/16 18:14, Juergen Gross wrote:
> On 18/05/16 18:09, Tony S wrote:
>> On Wed, May 18, 2016 at 8:57 AM, Dario Faggioli
>> wrote:
>>> On Wed, 2016-05-18 at 14:24 +0200, Juergen Gross wrote:
On 17/05/16 11:33, George Dunlap wrote:
>> Looks like CONFIG_PARAVIRT_TIME_ACCOUNTING is used
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
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
---
xen/arch/arm/traps.c | 1 +
xen/common/domain.c | 2 --
xen/common/kernel.c
Since commit 4b25423a "arch/arm: unmap partially-mapped memory regions",
Xen has been undoing the P2M mappings when an error occurred during
insertion or memory allocation.
This is done by calling recursively apply_p2m_changes, however the
second call is done with the p2m lock taken which will res
Since commit 4b25423a "arch/arm: unmap partially-mapped memory regions",
Xen has been undoing the P2M mappings when an error occurred during
insertion or memory allocation.
The function apply_p2m_changes can work with region not-aligned to a
block size (2MB, 1G) or page size (4K). The mapping will
Hello,
This small series fixes potential deadlock and the removal of unrelated
mapping when the P2M code fails to insert/allocate mappings.
This series contains bug fix for Xen 4.7 and candidate for backporting
up to Xen 4.5.
Yours sincerely,
Release-acked-by: Wei Liu
Julien Grall (2):
xen/
On 20/05/16 15:34, Andrew Cooper wrote:
> On 20/05/16 14:22, Juergen Gross wrote:
>> diff --git a/xen/arch/arm/domain.c b/xen/arch/arm/domain.c
>> index 1365b4a..91f256b 100644
>> --- a/xen/arch/arm/domain.c
>> +++ b/xen/arch/arm/domain.c
>> @@ -239,10 +239,32 @@ static void ctxt_switch_to(struct v
On 20/05/16 14:22, Juergen Gross wrote:
> diff --git a/xen/arch/arm/domain.c b/xen/arch/arm/domain.c
> index 1365b4a..91f256b 100644
> --- a/xen/arch/arm/domain.c
> +++ b/xen/arch/arm/domain.c
> @@ -239,10 +239,32 @@ static void ctxt_switch_to(struct vcpu *n)
> /* Update per-VCPU guest runstate sh
Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
ACPI 2.0, Hardware: Add access_width/bit_offset support for
acpi_hw_write()") result in guests issuing 32-bit accesses to IO space.
QEMU needs to be able to handle them.
Signed-off-by: Boris Ostrovsky
---
vl.c | 15
Hi Juergen,
On 20/05/16 14:22, Juergen Gross wrote:
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
Regards,
--
Julien
Hi Juergen,
On 20/05/16 14:22, Juergen Gross wrote:
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 p
On 20/05/16 16:10, Julien Grall wrote:
> Hi Juergen,
>
> On 20/05/16 14:22, Juergen Gross wrote:
>> 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
On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote:
On 20.05.16 at 10:45, wrote:
>> On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote:
>> On 19.05.16 at 15:58, wrote:
Case 1: Dom0 is driver domain:
There is a Ducati firmware which runs on dedicated M4 core and decodes
On 19/05/16 18:31, bharat gohil wrote:
Hello All,
Hello,
I am trying to boot xen on OrangePi PC(based upon Allwinner H3). It is
able to boot on this target board but it hangs when it try to boot
unmodified linux guest(with xen configuration enable).
Please find following log for same.Can any
>>> On 20.05.16 at 15:22, wrote:
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -1408,7 +1408,6 @@ long do_vcpu_op(int cmd, unsigned int vcpuid,
> XEN_GUEST_HANDLE_PARAM(void) arg)
> return rc;
> }
>
> -#ifdef VM_ASSIST_VALID
> long vm_assist(struct domain *p, unsigned int
On 20/05/16 16:34, Jan Beulich wrote:
On 20.05.16 at 15:22, wrote:
>> --- a/xen/common/domain.c
>> +++ b/xen/common/domain.c
>> @@ -1408,7 +1408,6 @@ long do_vcpu_op(int cmd, unsigned int vcpuid,
>> XEN_GUEST_HANDLE_PARAM(void) arg)
>> return rc;
>> }
>>
>> -#ifdef VM_ASSIST_VALID
>>
>>> On 20.05.16 at 15:22, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -1925,13 +1925,37 @@ static void paravirt_ctxt_switch_to(struct vcpu *v)
> bool_t update_runstate_area(struct vcpu *v)
> {
> bool_t rc;
> +bool_t update_flag;
I think this variable is supe
Hello Oleksandr,
On 20/05/16 15:19, Oleksandr Dmytryshyn wrote:
On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote:
On 20.05.16 at 10:45, wrote:
On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote:
On 19.05.16 at 15:58, wrote:
Case 1: Dom0 is driver domain:
There is a Ducati firmware whi
On 20/05/16 16:49, Jan Beulich wrote:
On 20.05.16 at 15:22, wrote:
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86/domain.c
>> @@ -1925,13 +1925,37 @@ static void paravirt_ctxt_switch_to(struct vcpu *v)
>> bool_t update_runstate_area(struct vcpu *v)
>> {
>> bool_t rc;
>> +bool
On 20/05/16 16:51, Jan Beulich wrote:
On 20.05.16 at 16:42, wrote:
>> On 20/05/16 16:34, Jan Beulich wrote:
>> On 20.05.16 at 15:22, wrote:
--- a/xen/common/domain.c
+++ b/xen/common/domain.c
@@ -1408,7 +1408,6 @@ long do_vcpu_op(int cmd, unsigned int vcpuid,
>> XEN_GUEST
>>> On 20.05.16 at 16:42, wrote:
> On 20/05/16 16:34, Jan Beulich wrote:
> On 20.05.16 at 15:22, wrote:
>>> --- a/xen/common/domain.c
>>> +++ b/xen/common/domain.c
>>> @@ -1408,7 +1408,6 @@ long do_vcpu_op(int cmd, unsigned int vcpuid,
> XEN_GUEST_HANDLE_PARAM(void) arg)
>>> return rc;
On Thu, May 19, 2016 at 5:53 PM, Andrii Anisov
wrote:
> Meng,
>
Hi Andrii,
Thank you very much for your explanation about the use case in previous email!
>>> If the board is not supported by Xen, can we say Xen will support the
>>> board with the warkaround?
>
> I would not say boards are suppo
>>> On 20.05.16 at 17:08, wrote:
> On 20/05/16 16:51, Jan Beulich wrote:
> On 20.05.16 at 16:42, wrote:
>>> On 20/05/16 16:34, Jan Beulich wrote:
>>> On 20.05.16 at 15:22, wrote:
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -1408,7 +1408,6 @@ long do_vcpu_op(i
>>> On 20.05.16 at 17:04, wrote:
> On 20/05/16 16:49, Jan Beulich wrote:
> On 20.05.16 at 15:22, wrote:
>>> if ( guest_handle_is_null(runstate_guest(v)) )
>>> return 1;
>>>
>>> +update_flag = VM_ASSIST(v->domain, runstate_update_flag);
>>> +
>>> smap_policy = smap_pol
docs/misc/qemu-deprivilege.txt and libxl suggest that "xen-qemuuser" is
the default prefix, reflect that in the man.
Also add some emphasis.
Signed-off-by: Anthony PERARD
---
docs/man/xl.cfg.pod.5 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/man/xl.cfg.pod.5 b/docs/m
From: "Edgar E. Iglesias"
Avoid looking up the device class multiple times in handle_node().
This optimization should not have any functional change.
Signed-off-by: Edgar E. Iglesias
---
xen/arch/arm/domain_build.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/xen/a
From: "Edgar E. Iglesias"
Create a helper function to map regions as MEMORY with
cached attributes and read-write-execute permissions.
Signed-off-by: Edgar E. Iglesias
---
xen/arch/arm/p2m.c| 26 ++
xen/include/asm-arm/p2m.h | 10 ++
2 files changed, 36
From: "Edgar E. Iglesias"
Add a DEVICE_MEMORY class to be used for things like "mmio-sram"
or memory controllers.
Signed-off-by: Edgar E. Iglesias
---
xen/include/asm-arm/device.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/include/asm-arm/device.h b/xen/include/asm-arm/device.h
in
From: "Edgar E. Iglesias"
Add device_get_desc, a function to lookup the device descriptor
for a DT node. This is in preparation for adding per device
mapping implementations.
Signed-off-by: Edgar E. Iglesias
---
xen/arch/arm/device.c| 15 +++
xen/include/asm-arm/device.h |
From: "Edgar E. Iglesias"
This series adds support for mapping mmio-sram nodes into dom0
as MEMORY, cached and with RWX perms.
Dom0 can then choose to further restrict these mappings if needed.
We only look at the outer mmio-sram region. The sub-area nodes that
describe allocations within the mm
From: "Edgar E. Iglesias"
Add an optional map function to the device descriptor. If
registered, the map function will be called to do custom
device specific mappings of the device. If not registered,
the generic DT version (handle_device) will be used.
This is in preparation for adding support f
From: "Edgar E. Iglesias"
Add an mmio-sram device. This device takes care of mapping
mmio-sram regions as MEMORY as opposed to the generic DT
mappings as DEVICE.
We only map the outer regions as children of mmio-sram nodes
describe allocations within it that really only mean something
to the gue
On 20/05/16 17:36, Jan Beulich wrote:
On 20.05.16 at 17:04, wrote:
>> On 20/05/16 16:49, Jan Beulich wrote:
>> On 20.05.16 at 15:22, wrote:
if ( guest_handle_is_null(runstate_guest(v)) )
return 1;
+update_flag = VM_ASSIST(v->domain, runstate_update
On 20/05/16 17:33, Jan Beulich wrote:
On 20.05.16 at 17:08, wrote:
>> On 20/05/16 16:51, Jan Beulich wrote:
>> On 20.05.16 at 16:42, wrote:
On 20/05/16 16:34, Jan Beulich wrote:
On 20.05.16 at 15:22, wrote:
>> --- a/xen/common/domain.c
>> +++ b/xen/common/domain.c
On Fri, May 20, 2016 at 04:04:43PM +0100, Julien Grall wrote:
> Hello Oleksandr,
>
> On 20/05/16 15:19, Oleksandr Dmytryshyn wrote:
> >On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote:
> >On 20.05.16 at 10:45, wrote:
> >>>On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote:
> >>>On 19
>>> On 20.05.16 at 17:54, wrote:
> On 20/05/16 17:36, Jan Beulich wrote:
> On 20.05.16 at 17:04, wrote:
>>> On 20/05/16 16:49, Jan Beulich wrote:
>>> On 20.05.16 at 15:22, wrote:
> if ( guest_handle_is_null(runstate_guest(v)) )
> return 1;
>
> +update_
flight 94611 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94611/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
> If a malicious user has access to the Android guest (via USB key, wifi,...)
> he would be able to crash the platform using the GPU because there is no
> SMMU protection.
That's why we are shadowing GPU MMU translation tables in xen heap.
And this is leaded us to need of [PATCH RFC 18/18] arm: Add
Hi all
Recently I got a report on xen-users@ about xl network-attach not
working for HVM guest.
I try to use
xl network-attach jessie-hvm 'bridge=xenbr0'
and vif-bridge script complains that it can't add vifXX-emu to bridge.
The underlying issue is that the vif spec provided defaults to
emul
Anthony PERARD writes ("[PATCH] docs: Fix device_model_user description of its
default value"):
> docs/misc/qemu-deprivilege.txt and libxl suggest that "xen-qemuuser" is
> the default prefix, reflect that in the man.
>
> Also add some emphasis.
I'm going to make a perhaps-controversial suggestio
Wei Liu writes ("[RFC] libxl hotplug / unplug emulated devices"):
> Recently I got a report on xen-users@ about xl network-attach not
> working for HVM guest.
>
> I try to use
> xl network-attach jessie-hvm 'bridge=xenbr0'
> and vif-bridge script complains that it can't add vifXX-emu to bridge.
On 20/05/16 17:34, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH] docs: Fix device_model_user description of
> its default value"):
>> docs/misc/qemu-deprivilege.txt and libxl suggest that "xen-qemuuser" is
>> the default prefix, reflect that in the man.
>>
>> Also add some emphasis.
> I'm g
On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[RFC] libxl hotplug / unplug emulated devices"):
> > Recently I got a report on xen-users@ about xl network-attach not
> > working for HVM guest.
> >
> > I try to use
> > xl network-attach jessie-hvm 'bridge=xenbr0'
On 2016-05-18 11:12, Jan Beulich wrote:
On 06.04.16 at 01:38, wrote:
I'm running Xen 4.6.1 with Alpine Linux 3.3.3 in dom0. In a HVM domU
with vga="qxl", Xorg will segfault instantly if tried started.
Multiple
Linux distros have been tested and Xorg segfaults in all.
Attached are a full back
On 20/05/16 17:42, Wei Liu wrote:
> On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
>> Wei Liu writes ("[RFC] libxl hotplug / unplug emulated devices"):
>>> Recently I got a report on xen-users@ about xl network-attach not
>>> working for HVM guest.
>>>
>>> I try to use
>>> xl networ
On Fri, May 20, 2016 at 05:34:10PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH] docs: Fix device_model_user description of
> its default value"):
> > docs/misc/qemu-deprivilege.txt and libxl suggest that "xen-qemuuser" is
> > the default prefix, reflect that in the man.
> >
> > Als
On Fri, May 20, 2016 at 05:45:53PM +0100, Andrew Cooper wrote:
> On 20/05/16 17:42, Wei Liu wrote:
> > On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> >> Wei Liu writes ("[RFC] libxl hotplug / unplug emulated devices"):
> >>> Recently I got a report on xen-users@ about xl network-att
On Fri, May 20, 2016 at 05:48:37PM +0100, Anthony PERARD wrote:
> On Fri, May 20, 2016 at 05:34:10PM +0100, Ian Jackson wrote:
> > Anthony PERARD writes ("[PATCH] docs: Fix device_model_user description of
> > its default value"):
> > > docs/misc/qemu-deprivilege.txt and libxl suggest that "xen-qe
> If I understand correctly, all the initiators but the GPU will be used by
> DOM0 which is already direct mapped. The only issue here is allocating
> memory enough memory below 4GB.
It's not about memory allocation for domain. It is rather about SDRAM
mapping on the bus. J6 has first 2GB for iomem
Meng,
> From my previous experience, the board may not be supported by Xen even though
> the processor it uses has virtualization extension.. :-(
I still insist it depends on SoC ;)
If you are saying about this case:
> Yes. I searched around for the "Jacinto 6" Automotive processor.[1]
> It use
On Fri, May 20, 2016 at 1:23 PM, Andrii Anisov
wrote:
> Meng,
>
>> From my previous experience, the board may not be supported by Xen even
>> though
>> the processor it uses has virtualization extension.. :-(
>
> I still insist it depends on SoC ;)
Ah-ha, I totally agree about this...
>
> If yo
On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[RFC] libxl hotplug / unplug emulated devices"):
> > Recently I got a report on xen-users@ about xl network-attach not
> > working for HVM guest.
> >
> > I try to use
> > xl network-attach jessie-hvm 'bridge=xenbr0'
From: Paul Durrant
Date: Wed, 18 May 2016 08:53:01 +0100
> The length checks on the grant table copy_ops for setting hash key and
> hash mapping are checking the local 'len' value which is correct in
> the case of the former but not the latter. This was picked up by
> static analysis checks.
>
>
On Fri, May 20, 2016 at 4:52 AM, Olaf Hering wrote:
> On Thu, May 19, Meng Xu wrote:
>
>> Does anyone try to install two version of Xen toolstack on the same machine?
>
> I do that. See the INSTALL file which has examples at the end:
>
> * To build a private copy of tools and xen:
> configure --pr
Hi Jan,
On Fri, May 20, 2016 at 6:20 AM, Jan Beulich wrote:
On 19.05.16 at 20:40, wrote:
>> Does anyone try to install two version of Xen toolstack on the same machine?
>> Is there any documentation about the best practice to install two
>> versions of Xen onto the same machine?
>
> Or, as
Wei Liu writes ("Re: [RFC] libxl hotplug / unplug emulated devices"):
> On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> > Maybe the fix should be that xl network-attach should default hotplug
> > nics to pv only.
>
> Here is a patch to do this. :-)
Acked-by: Ian Jackson
Although
On Fri, May 20, 2016 at 06:58:40PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [RFC] libxl hotplug / unplug emulated devices"):
> > On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> > > Maybe the fix should be that xl network-attach should default hotplug
> > > nics to pv only.
>
Wei Liu writes ("Re: [RFC] libxl hotplug / unplug emulated devices"):
> On Fri, May 20, 2016 at 06:58:40PM +0100, Ian Jackson wrote:
> > Although I have a style nit:
> >
> > > if (libxl__device_model_version_running(gc, domid) ==
> > > -LIBXL_DEVICE_MODEL_VERSION_NONE)
On Fri, May 20, 2016 at 07:04:20PM +0100, Wei Liu wrote:
> On Fri, May 20, 2016 at 06:58:40PM +0100, Ian Jackson wrote:
> > Wei Liu writes ("Re: [RFC] libxl hotplug / unplug emulated devices"):
> > > On Fri, May 20, 2016 at 05:38:44PM +0100, Ian Jackson wrote:
> > > > Maybe the fix should be that x
Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
the signature checking paragraph.
/usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
--output pdf/misc/xsplice.pdf
! Undefined control sequence.
l.1085 appended\textasciitilde{}\n
Surrou
On Fri, May 20, 2016 at 07:09:42PM +0100, Andrew Cooper wrote:
> Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
> the signature checking paragraph.
>
> /usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
> --output pdf/misc/xsplice.pdf
>
flight 94610 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94610/
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. 94580
Regressi
flight 94614 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94614/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf edddb945519cf71c048e82a2f009db3e1e7f7d74
baseline version:
ovmf 66e5133ce0a8940a99451842a804dc5a37b
On Fri, Feb 26, 2016 at 03:56:04PM +0100, Heiko Carstens wrote:
> On Sun, Feb 21, 2016 at 06:55:05PM -0800, H. Peter Anvin wrote:
> > On 02/19/16 13:06, Luis R. Rodriguez wrote:
> > >>
> > >> I think the \n\t is unnecessary.
> > >
> > > Super! I wonder if we we can just use this on s390 as well wi
flight 94612 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94612/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 94586
test-amd64-i386-xl-qemuu-win
flight 94613 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94613/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
On 05/20/2016 05:22 PM, Munehisa Kamata wrote:
> Commit ff1e22e7a638 ("xen/events: Mask a moving irq") introduced
> a crash below. This can be triggered after being resumed from suspend
> (e.g. live migration) if there are disabled IRQs with
> IRQD_SETAFFINITY_PENDING set.
A patch just like this
From: Paul Durrant
Date: Wed, 18 May 2016 15:55:42 +0100
> A domain with a frontend that does not implement a control ring has been
> seen to cause a crash during domain save. This was apparently because
> the call to xenvif_deinit_hash() in xenvif_disconnect_ctrl() is made
> regardless of whethe
From: Kővágó, Zoltán
Except qapi-schema.json, this patch was generated by:
find . -name .git -prune -o -type f \! -name '*~' -print0 | \
xargs -0 sed -i \
-e 's/NetClientOptionsKind/NetClientDriver/g' \
-e 's/NET_CLIENT_OPTIONS_KIND_/NET_CLIENT_DRIVER_/g' \
-e 's/netdev->opts/netde
I've encountered two problems booting a Linux 4.4 dom0 on recent
stable xen 4.5 on VMware ESXi 5.5.0.
One has the same "ata_piix: probe of :00:07.1 failed with error
-22" symptom discussed some time ago, and prevents the kernel from
seeing any of the virtual IDE drives exposed by VMware. This
1 - 100 of 108 matches
Mail list logo
