setup and control colo proxy on secondary side
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_colo_restore.c | 28 +---
tools/libxl/libxl_internal.h | 3 +++
2 files changed, 28 insertions(+), 3 deletions(-)
diff --git a/tools/libxl/libxl_colo_restore.c b/tools/
implement COLO nic subkind.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
---
tools/hotplug/Linux/Makefile | 1 +
tools/hotplug/Linux/colo-proxy-setup | 131 +++
tools/libxl/Makefile | 1 +
tools/libxl/libxl_colo_nic.c | 317 +++
setup and control colo proxy on primary side
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_colo_save.c | 124 +++---
tools/libxl/libxl_internal.h | 1 +
2 files changed, 117 insertions(+), 8 deletions(-)
diff --git a/tools/libxl/libxl_colo_save.c b/to
From: Wen Congyang
Usage: disk = ['...,colo,colo-params=xxx,active-disk=xxx,hidden-disk=xxx...']
The format of colo-params: host:port:exportname=xx
For QEMU block replication details:
http://wiki.qemu.org/Features/BlockReplication
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
---
d
Send dirty bitmap to primary when checkpoint under colo.
Signed-off-by: Yang Hongyang
---
tools/libxc/xc_sr_common.h | 4 ++
tools/libxc/xc_sr_restore.c | 120 +++-
2 files changed, 123 insertions(+), 1 deletion(-)
diff --git a/tools/libxc/xc_sr_common
add colo readme, refer to
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
Signed-off-by: Yang Hongyang
---
docs/README.colo | 9 +
1 file changed, 9 insertions(+)
create mode 100644 docs/README.colo
diff --git a/docs/README.colo b/docs/README.colo
new file mode 100644
index
From: Wen Congyang
We will call libxl__xc_domain_restore_done() to rebuild secondary vm. But
we need store mfn and console mfn when rebuilding secondary vm. So make
restore_results a function pointer in callback struct and struct
{save,restore}_callbacks, and use this callback to send store mfn a
From: Wen Congyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_internal.h | 4 ++
tools/libxl/libxl_stream_write.c | 92
2 files changed, 96 insertions(+)
diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
index 7f591ee.
setup/teardown of COLO proxy module.
we use netlink to communicate with proxy module.
About colo-proxy module:
https://lkml.org/lkml/2015/6/18/32
How to use:
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
Signed-off-by: Yang Hongyang
---
tools/libxl/Makefile | 1 +
tools/
Add cmdline switches to 'xl migrate-receive' command to specify
a domain-specific hotplug script to setup COLO proxy.
Add a new config var 'colo.default.agentscript' to xl.conf, that
allows the user to override the default global script used to
setup COLO proxy.
Signed-off-by: Yang Hongyang
Sign
This patchset implemented the COLO feature for Xen.
For detail/install/use of COLO feature, refer to:
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
This patchset is based on:
[PATCH v3 COLOPre 00/26] Prerequisite patches for COLO
and on:
http://xenbits.xen.org/gitweb/?p=people/
From: Wen Congyang
Use qemu block replication as our block replication solution.
Note that guest must be paused before starting COLO, otherwise,
the disk won't be consistent between primary and secondary.
Signed-off-by: Wen Congyang
for commit message,
Signed-off-by: Yang Hongyang
---
tools/l
call the callbacks resume/checkpoint/suspend while secondary vm
status is consistent with primary.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Andrew Cooper
---
tools/libxc/xc_sr_common.h | 19 --
tools/libxc/xc_sr_restore.c | 63 ++
From: Wen Congyang
Secondary vm is running in colo mode. So we will do
the following things again and again:
1. Resume secondary vm
a. Send LIBXL_COLO_SVM_READY to master.
b. If it is not the first resume, call libxl__checkpoint_devices_preresume().
c. If it is the first resume(resume ri
From: Wen Congyang
We will do the following things again and again:
1. Suspend primary vm
a. Suspend primary vm
b. do postsuspend
c. Read LIBXL_COLO_SVM_SUSPENDED sent by secondary
2. Resume primary vm
a. Read LIBXL_COLO_SVM_READY from slave
b. Do presume
c. Resume primary vm
After suspend primary vm, get dirty bitmap on secondary vm,
and send pages both dirty on primary/secondary to secondary.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Andrew Cooper
---
tools/libxc/xc_sr_common.h | 2 +
tools/libxc/xc_sr_save.c | 104 +
From: Wen Congyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_internal.h| 3 +++
tools/libxl/libxl_stream_read.c | 51 +
2 files changed, 54 insertions(+)
diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
index 840734d.
From: Wen Congyang
Add a new option -c to the command 'xl remus'. If you want
to use COLO HA instead of Remus HA, please use -c option.
Update man pages to reflect the addition of a new option to
'xl remus' command.
Also add a new option -c to the internal command 'xl migrate-receive'.
Signed-
preresume, postresume and checkpoint
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_colo.h | 3 +++
tools/libxl/libxl_colo_proxy.c | 57 ++
2 files changed, 60 insertions(+)
diff --git a/tools/libxl/libxl_colo.h b/tools/libxl/libxl_colo.h
index
This patch is auto generated by the following commands:
1. git mv tools/libxl/libxl_remus_device.c
tools/libxl/libxl_checkpoint_device.c
2. perl -pi -e 's/libxl_remus_device/libxl_checkpoint_device/g'
tools/libxl/Makefile
3. perl -pi -e 's/\blibxl__remus_devices/libxl__checkpoint_devices/g'
t
read_record() could be used by primary to read dirty bitmap
record sent by secondary under COLO.
When used by save side, we need to pass the backchannel fd
instead of ctx->fd to read_record(), so we added a fd param to
it.
Signed-off-by: Yang Hongyang
CC: Andrew Cooper
---
tools/libxc/xc_sr_com
From: Wen Congyang
Signed-off-by: Wen Congyang
---
docs/specs/libxl-migration-stream.pandoc | 21 -
tools/libxl/libxl_sr_stream_format.h | 11 +++
tools/python/xen/migration/libxl.py | 9 +
3 files changed, 40 insertions(+), 1 deletion(-)
diff --gi
From: Wen Congyang
In colo mode, slave needs to send data to master, but the io_fd
only can be written in master, and only can be read in slave.
Save recv_fd in domain_suspend_state, and send_fd in
domain_create_state.
Extend libxl_domain_create_restore API, add a send_fd param to
it.
Add LIBXL_H
From: Wen Congyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_create.c | 8 +---
tools/libxl/libxl_internal.h| 9 +
tools/libxl/libxl_remus.c | 8 +---
tools/libxl/libxl_stream_read.c | 33 +
4 files changed, 44 insertions
Checkpoint device is an abstract layer to do checkpoint.
COLO can also use it to do checkpoint. But there are
still some codes in checkpoint device which touch remus:
1. remus_ops: we use remus ops directly in checkpoint
device. Store it in checkpoint device state.
2. concrete layer's private me
This is just tidying up after the previous automatic renaming.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
Acked-by: Ian Campbell
---
tools/libxl/libxl_checkpoint_device.c | 21 +++--
tools/libxl/libxl_internal.h | 19 +++
2 files changed,
Used by secondary to send it's dirty bitmap to primary under COLO.
Signed-off-by: Yang Hongyang
---
docs/specs/libxc-migration-stream.pandoc | 23 ++-
tools/libxc/xc_sr_common.c | 1 +
tools/libxc/xc_sr_stream_format.h| 1 +
3 files changed, 24 inserti
From: Wen Congyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_dom_save.c | 7 +--
tools/libxl/libxl_internal.h | 9 +
tools/libxl/libxl_remus.c| 8 +---
tools/libxl/libxl_stream_write.c | 22 ++
4 files changed, 33 insertions(+), 13
Secondary(restore side) is running under COLO, we also need
postcopy/suspend callbacks.
Signed-off-by: Yang Hongyang
---
tools/libxc/include/xenguest.h | 10 ++
tools/libxl/libxl_save_msgs_gen.pl | 4 ++--
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/tools/libxc/i
Secondary vm is running in colo mode. So we will do
the following things again and again:
1. suspend both primay vm and secondary vm
2. sync the state
3. resume both primary vm and secondary vm
We will send qemu's state each time in step2, and
slave's qemu should read it each time before resuming
s
Under COLO, we are doing checkpoint on demand, if this
callback returns 1, we will take another checkpoint.
0 indicates unexpected error.
Signed-off-by: Yang Hongyang
---
tools/libxc/include/xenguest.h | 18 ++
tools/libxl/libxl_save_msgs_gen.pl | 7 ---
2 files changed,
We need to send secondary's dirty page pfns back to primary.
Primary will then send pages that are both dirtied on
primary/secondary to secondary. in this way the secondary's
memory will be consistent with primary.
We do this on libxc side, so we need to introduce back
channel to libxc.
Signed-of
Secondary vm is running in colo mode, we need to send
secondary vm's dirty page information to master at checkpoint,
so we have to enable qemu logdirty on secondary.
libxl__domain_suspend_common_switch_qemu_logdirty() is to enable
qemu logdirty. But it uses domain_save_state, and calls
libxl__xc_d
We need to enable logdirty on secondary, so we export logdirty_init
for internal use. Rename it to libxl__logdirty_init.
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_dom_save.c | 4 ++--
tools/libxl/libxl_internal.h | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/too
Pass checkpointed_stream from libxl to libxc.
It won't affact legacy migration because legacy migration
won't use this param.
Signed-off-by: Yang Hongyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
---
tools/libxc/include/xenguest.h | 9 ++---
tools/libxc/xc_domain
Currently, libxl__domain_unpause() only supports
qemu-xen-traditional. Update it to support qemu-xen.
We use libxl__domain_resume_device_model to unpause guest dm.
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl.c | 15 +--
tools/libxl/libxl_dom_suspend.c | 15
If the err is RECORD_NOT_PROCESSED, and it is an optional record,
restore will still fail. There're two options to fix this,
a, setting rc to 0 when it is an optional record.
b, do the error handling in the caller.
We choose b because:
There will be another error type in COLO, which indicates a
From: Wen Congyang
1. suspend
a. PVHVM and PV: we use the same way to suspend the guest(send the suspend
request to the guest). If the guest doesn't support evtchn, the xenstore
variant will be used, suspending the guest via XenBus control node.
b. pure HVM: we call xc_domain_shutdown(...,
Currently struct libxl__domain_suspend_state contains 2 type of states,
one is save state, another is suspend state. This patch separates those
two out.
The motivation of this is that COLO will need to do suspend/resume
continuously, we need a more common suspend state.
After this change, dss stan
introduce enum type libxl_checkpointed_stream in IDL.
rename the last argument of migrate_receive from "remus" to
"checkpointed" since the semantics of this parameter has
changed.
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_types.idl | 5 +
tools/libxl/xl_cmdimpl.c| 13 +++---
This is purely code motion.
Signed-off-by: Yang Hongyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl_dom.c | 607 -
tools/libxl/libxl_dom_save.c | 634 +++
Do the following things:
- There are 2 checkpoint callbacks, rename them to:
libxl__remus_domain_{save/restore}_checkpoint_callback
- Moving remus callbacks into libxl_remus.c, export following
callbacks for internal use:
* libxl__remus_domain_suspend_callback
* libxl__remus_domain_resume_c
This patchset is Prerequisite for COLO feature. For what COLO is, refer
to http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
This patchse is based on Andrew Cooper's Libxl migration v2:
http://xenbits.xen.org/gitweb/?p=people/andrewcoop/xen.git;a=shortlog;h=refs/heads/libxl-migv2-v1
I
move domain resume code into libxl_dom_suspend.c.
pure code motion except for making
libxl__domain_resume_device_model() static.
Signed-off-by: Yang Hongyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxl/libxl.c | 33 -
tools/libxl/libxl_dom.
Rename libxl__domain_suspend() to libxl__domain_save() since it
actually do the save domain work.
This results in some strangeness in that some functions called *save*
are now passed a struct called *suspend*, this is temporary and is all
fixed up later by the refactoring of the suspend_state.
Si
Move domain suspend code into a separate file libxl_dom_suspend.c.
Add an API libxl__domain_suspend() which wraps the static
function domain_suspend_callback_common() for internal use.
Export the existing API libxl__domain_suspend_callback() used by
libxc to suspend the guest during migration.
Not
My apologize for been to late for subscription confirmation.
Resubmitting.
Env : xen 4.5 + kernel 4.0.5 + xl stack, working dom0/domU.
Level : Quite critical despite integration env as using source distro
(gentoo)
tmem is on xen command line, and reported in xl dmesg.
tmem module in loaded via i
Agree, but I think the document is a bit confused
> It is important that channel names are globally unique.
https://github.com/mirage/xen/blob/master/docs/misc/channel.txt#L94
On Thu, Jun 25, 2015 at 2:29 AM Dave Scott wrote:
> Hi Xu,
>
> > On 24 Jun 2015, at 14:44, Wang Xu wrote:
> >
> > Tha
flight 58861 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58861/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-pair 20 guest-start/debian fail in 58838 pass in 58861
test-amd64-amd64-xl-qemuu-win7-amd64
On 06/16/2015 07:26 PM, Ian Campbell wrote:
On Tue, 2015-06-16 at 12:24 +0100, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:45 +0800, Yang Hongyang wrote:
setup/teardown of COLO proxy module.
we use netlink to communicate with proxy module.
What is a COLO proxy module and where would one ge
flight 58855 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58855/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-i386-i386-xl-credit222 leak-check/check fail REGR. vs. 58411
Regressions which
On 06/16/2015 07:19 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:45 +0800, Yang Hongyang wrote:
From: Wen Congyang
Add a new option -c to the command 'xl remus'. If you want
to use COLO HA instead of Remus HA, please use -c option.
Update man pages to reflect the addition of a new optio
On 06/16/2015 06:53 PM, Ian Campbell wrote:
On Mon, 2015-06-15 at 17:24 +0100, Wei Liu wrote:
On Mon, Jun 15, 2015 at 09:45:54AM +0800, Yang Hongyang wrote:
On 06/12/2015 10:57 PM, Ian Jackson wrote:
Wei Liu writes ("Re: [Xen-devel] [PATCH v2 COLOPre 11/13] tools/libxl: rename remus
devic
On 06/24/2015 03:57 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Jun 24, 2015 at 02:06:02PM +0200, Juergen Gross wrote:
Hi,
my qemu integrated pvUSB backend is now running stable enough to do
some basic performance measurements. I've passed a memory-stick with
about 90MB of data on it to a pv-domU.
flight 58856 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58856/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 58834
test-amd64-i386-xl-qemuu-win7-amd64 1
On Mon, Jun 22, 2015 at 2:56 PM, Ed White wrote:
> Add the remaining routines required to support enabling the alternate
> p2m functionality.
>
> Signed-off-by: Ed White
> ---
> xen/arch/x86/hvm/hvm.c | 60 +-
> xen/arch/x86/mm/hap/Makefile| 1 +
> xen/arch/x86/mm/ha
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as write-combining
From: "Luis R. Rodriguez"
Now that we have pci_iomap_wc() add the respective
devres helpers. These go unexported for now but
note that should they later be exported this
must go with EXPORT_SYMBOL_GPL().
Cc: Toshi Kani
Cc: Andy Lutomirski
Cc: Suresh Siddha
Cc: Ingo Molnar
Cc: Thomas Gleixner
From: "Luis R. Rodriguez"
PCI BARs tell us whether prefetching is safe, but they don't say anything
about write combining (WC). WC changes ordering rules and allows writes to
be collapsed, so it's not safe in general to use it on a prefetchable
region.
Add pci_iomap_wc() and pci_iomap_wc_range(
From: "Luis R. Rodriguez"
The driver doesn't use mtrr_add() or arch_phys_wc_add() but
since we know the framebuffer is isolated already on an
ioremap() we can take advantage of write combining for
performance where possible.
In this case there are a few motivations for this:
a) Take advantage o
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as write-combining
From: "Luis R. Rodriguez"
Convert the driver from using the x86 specific MTRR code to
the architecture agnostic arch_phys_wc_add(). arch_phys_wc_add()
will avoid MTRR if write-combining is available, in order to
take advantage of that also ensure the ioremap'd area is requested
as write-combining
From: "Luis R. Rodriguez"
This lets drivers take advantage of PAT when available. This
should help with the transition of converting video drivers over
to ioremap_wc() to help with the goal of eventually using
_PAGE_CACHE_UC over _PAGE_CACHE_UC_MINUS on x86 on
ioremap_nocache() (de33c442e titled
From: "Luis R. Rodriguez"
Boris,
This patchset is part of the long haul of series that addresses removal of
direct use of MTRR and transforms drivers over to use PAT interfaces when
available [0]. Other than this series there is only one more pending series for
that effort, the other one being t
On Wed, 2015-06-24 at 17:58 -0700, Luis R. Rodriguez wrote:
> On Wed, Jun 24, 2015 at 5:52 PM, Benjamin Herrenschmidt
> wrote:
> > On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
> >>
> >> OK thanks I'll proceed with these patches then.
> >>
> >> > As for user mappings,
> >>
> >> Which
On 06/24/2015 07:49 PM, Andrew Cooper wrote:
On 24/06/2015 22:35, Boris Ostrovsky wrote:
On 06/23/2015 11:18 AM, Jan Beulich wrote:
... as being identical to is_pv_32bit_vcpu() after the x86-32 removal.
In a few cases this includes an additional is_pv_32bit_vcpu() ->
is_pv_32bit_domain() conve
On Wed, Jun 24, 2015 at 5:52 PM, Benjamin Herrenschmidt
wrote:
> On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
>>
>> OK thanks I'll proceed with these patches then.
>>
>> > As for user mappings,
>>
>> Which APIs were you considering in this regard BTW?
>
> mmap of the generic /sys/bu
On Thu, 2015-06-25 at 02:08 +0200, Luis R. Rodriguez wrote:
>
> OK thanks I'll proceed with these patches then.
>
> > As for user mappings,
>
> Which APIs were you considering in this regard BTW?
mmap of the generic /sys/bus/pci/.../resource*
> > maybe the right thing to do is to let us do wha
Windows 8.0 iso can't install in uefi mode,
I have to use windbg to get more debug information,
So using xen in this case
发件人: Razvan Cojocaru [mailto:rcojoc...@bitdefender.com]
发送时间: 2015年6月24日 17:26
收件人: Fanhenglong; xen-devel@lists.xen.org
抄送: Liuqiming (John); Yanqiangjun; Huangpeng (Peter)
On Thu, Jun 25, 2015 at 09:38:01AM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2015-06-24 at 15:29 -0700, Luis R. Rodriguez wrote:
>
> > Nope but at least what made me squint at this being a possible
> > "feature" was that in practice when reviewing all of the kernels
> > pending device drivers
On 24/06/2015 22:35, Boris Ostrovsky wrote:
> On 06/23/2015 11:18 AM, Jan Beulich wrote:
>> ... as being identical to is_pv_32bit_vcpu() after the x86-32 removal.
>>
>> In a few cases this includes an additional is_pv_32bit_vcpu() ->
>> is_pv_32bit_domain() conversion.
>>
>> Signed-off-by: Jan Beul
On Wed, 2015-06-24 at 15:29 -0700, Luis R. Rodriguez wrote:
> Nope but at least what made me squint at this being a possible
> "feature" was that in practice when reviewing all of the kernels
> pending device drivers using MTRR (potential write-combine candidates)
> I encountered a slew of them wh
On 06/24/2015 03:45 PM, Lengyel, Tamas wrote:
> On Wed, Jun 24, 2015 at 6:02 PM, Ed White wrote:
>
>> On 06/24/2015 02:34 PM, Lengyel, Tamas wrote:
>>> Hi Ed,
>>> I tried the system using memsharing and I collected the following crash
>>> log. In this test I ran memsharing on all pages of the dom
On Wed, Jun 24, 2015 at 6:02 PM, Ed White wrote:
> On 06/24/2015 02:34 PM, Lengyel, Tamas wrote:
> > Hi Ed,
> > I tried the system using memsharing and I collected the following crash
> > log. In this test I ran memsharing on all pages of the domain before
> > activating altp2m and creating the v
On Wed, Jun 24, 2015 at 3:05 PM, Benjamin Herrenschmidt
wrote:
> On Wed, 2015-06-24 at 18:38 +0200, Luis R. Rodriguez wrote:
>> On Wed, Jun 24, 2015 at 08:42:23AM +1000, Benjamin Herrenschmidt wrote:
>> > On Fri, 2015-06-19 at 15:08 -0700, Luis R. Rodriguez wrote:
>> > > From: "Luis R. Rodriguez"
flight 58851 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58851/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs.
On Wed, 2015-06-24 at 18:38 +0200, Luis R. Rodriguez wrote:
> On Wed, Jun 24, 2015 at 08:42:23AM +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2015-06-19 at 15:08 -0700, Luis R. Rodriguez wrote:
> > > From: "Luis R. Rodriguez"
> > >
> > > PCI BARs tell us whether prefetching is safe, but they
On 06/24/2015 02:34 PM, Lengyel, Tamas wrote:
> Hi Ed,
> I tried the system using memsharing and I collected the following crash
> log. In this test I ran memsharing on all pages of the domain before
> activating altp2m and creating the view. Afterwards I used my updated
> xen-access to create a co
Thank you Dave, I think I can also get work around for that.
By the way, the document says the name should be global unique, but I can
start 2 domains have channels with a same name, is there some potential
problems?
Cheers
Xu
On Wed, Jun 24, 2015 at 9:03 PM Dave Scott wrote:
> I don’t think
Thanks for the help and support guys. I'll need some time to get a proper
understanding of how it is incorporated in Linux kernel and what all
interfaces are built on top of it. Once I'm comfortable with that and xen's
credit_scheduler, for starting, I'll come up with a design doc and share
with yo
Hello everyone,
I would like to try the vTPM feature, but I'm having some issues. Basically, I
followed the steps explained in
https://mhsamsal.wordpress.com/2013/12/05/configuring-virtual-tpm-vtpm-for-xen-4-3-guest-virtual-machines/
I'm running Ubuntu 14.04 as Dom0 on a Dell optiplex-9020. I
On Wed, 24 Jun 2015 16:26:44 -0400
Elena Ufimtseva wrote:
> On Wed, Jun 24, 2015 at 07:24:18PM +0100, Andrew Cooper wrote:
> > On 24/06/15 08:49, Jan Beulich wrote:
> > On 24.06.15 at 04:34, wrote:
> > >> On 06/23/2015 08:30 AM, Jan Beulich wrote:
> > >> On 22.06.15 at 18:37, wrote:
>
On Wed, Jun 24, 2015 at 12:43 PM, Ed White wrote:
> On 06/24/2015 06:37 AM, Razvan Cojocaru wrote:
> > On 06/24/2015 04:32 PM, Lengyel, Tamas wrote:
> >>
> >>
> >> On Wed, Jun 24, 2015 at 1:39 AM, Razvan Cojocaru
> >> mailto:rcojoc...@bitdefender.com>> wrote:
> >>
> >> On 06/24/2015 12:27 AM,
On 06/23/2015 11:18 AM, Jan Beulich wrote:
... as being identical to is_pv_32bit_vcpu() after the x86-32 removal.
In a few cases this includes an additional is_pv_32bit_vcpu() ->
is_pv_32bit_domain() conversion.
Signed-off-by: Jan Beulich
We have
struct arch_domain
{
...
/* Is a 32-b
On 06/24/2015 05:47 AM, Andrew Cooper wrote:
>> +case EXIT_REASON_VMFUNC:
>> +if ( vmx_vmfunc_intercept(regs) == X86EMUL_OKAY )
>
> This is currently an unconditional failure, and I don't see subsequent
> patches which alter vmx_vmfunc_intercept(). Shouldn't
> vmx_vmfunc_intercept() s
On Wed, Jun 24, 2015 at 07:24:18PM +0100, Andrew Cooper wrote:
> On 24/06/15 08:49, Jan Beulich wrote:
> On 24.06.15 at 04:34, wrote:
> >> On 06/23/2015 08:30 AM, Jan Beulich wrote:
> >> On 22.06.15 at 18:37, wrote:
> --- a/xen/arch/x86/hvm/svm/svm.c
> +++ b/xen/arch/x86/hvm/sv
On Tue, Jun 23, 2015 at 01:02:49PM +0100, Jan Beulich wrote:
> >>> On 22.06.15 at 18:37, wrote:
> > From: Elena Ufimtseva
> >
> > Signed-off-by: Mukesh Rathor
>
> As long as this patch originally cam from Mukesh, From: should
> reflect that imo. Once you made changes, you S-o-b would be
> requ
On Tue, Jun 23, 2015 at 01:02:49PM +0100, Jan Beulich wrote:
> >>> On 22.06.15 at 18:37, wrote:
> > From: Elena Ufimtseva
> >
> > Signed-off-by: Mukesh Rathor
>
> As long as this patch originally cam from Mukesh, From: should
> reflect that imo. Once you made changes, you S-o-b would be
> requ
Hi Jan / Andrew,
I'm having some trouble with a xhci controller passed through with
pci-passthrough to one of my HVM guests.
It uses MSI-X for interrupts, a bisection turned up the following commit:
ad28e42bd1d28d746988ed71654e8aa670629753 is the first bad commit
commit ad28e42bd1d28d746988ed71
>As said by David, Xen will parse "reg" using the #address-cells and
>#size-cells of the parent. So it's normal to see 2GB. Does the same device
>tree reports 3GB on Linux? I suspect no.
I'm not in the office today, so I can't test this, but I believe the answer is
"yes". I have this log from a
On 24/06/15 06:18, Feng Wu wrote:
> This patch adds cmpxchg16b support for x86-64, so software
> can perform 128-bit atomic write/read.
>
> Signed-off-by: Feng Wu
> ---
> v3:
> Newly added.
>
> xen/include/asm-x86/x86_64/system.h | 28
> xen/include/xen/types.h
flight 58848 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58848/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 58440
test-amd64-i386-x
Hi Xu,
> On 24 Jun 2015, at 14:44, Wang Xu wrote:
>
> Thank you Dave, I think I can also get work around for that.
>
> By the way, the document says the name should be global unique, but I can
> start 2 domains have channels with a same name, is there some potential
> problems?
The name need
On 24/06/15 08:49, Jan Beulich wrote:
On 24.06.15 at 04:34, wrote:
>> On 06/23/2015 08:30 AM, Jan Beulich wrote:
>> On 22.06.15 at 18:37, wrote:
--- a/xen/arch/x86/hvm/svm/svm.c
+++ b/xen/arch/x86/hvm/svm/svm.c
@@ -1444,6 +1444,9 @@ const struct hvm_function_table * __init
On 24/06/15 18:47, Ed White wrote:
>> > This looks like some hoop jumping around the assertions in
>> > domain_pause() and vcpu_pause().
>> >
>> > We should probably have some new helpers where the domain needs to be
>> > paused, possibly while in context. The current domain/vcpu_pause() are
>> >
On 24/06/15 18:57, Ed White wrote:
> On 06/24/2015 07:59 AM, Jan Beulich wrote:
> On 22.06.15 at 20:56, wrote:
>>> +case HVM_PARAM_ALTP2MHVM:
>>> +if ( a.value > 1 )
>>> +rc = -EINVAL;
>>> +if ( a.value &&
>>> + d->arch.hvm_domain.params[HVM_PARAM_NE
On 06/24/2015 09:15 AM, Lengyel, Tamas wrote:
>> +bool_t p2m_set_altp2m_mem_access(struct domain *d, uint16_t idx,
>> + unsigned long pfn, xenmem_access_t
>> access)
>> +{
>>
>
> This function IMHO should be merged with p2m_set_mem_access and should be
> triggerable
On 06/24/2015 09:01 AM, Lengyel, Tamas wrote:
> On Mon, Jun 22, 2015 at 2:56 PM, Ed White wrote:
>
>> Add a flag to indicate that a memory event occurred in an alternate p2m
>> and a field containing the p2m index. Allow the response to switch to
>> a different p2m using the same flag and field.
1 - 100 of 322 matches
Mail list logo
