>>> On 05.06.15 at 18:42, wrote:
> On 05/06/15 17:11, Jan Beulich wrote:
> On 05.06.15 at 17:55, wrote:
>>> On 05/06/15 15:51, Jan Beulich wrote:
>>> On 02.06.15 at 18:26, wrote:
> +/*
> + * max_maptrack_frames is per domain so each VCPU gets a share of
> + * the
>>> On 08.06.15 at 03:47, wrote:
> On 26/05/2015 21:58, Jan Beulich wrote
>> >>> On 13.05.16 at 09:50, wrote:
>> > +static int byt_get_min_pstate(void)
>> > +{
>> > +u64 value;
>> > +
>> > +rdmsrl(BYT_RATIOS, value);
>> > +return (value >> 8) & 0x7F;
>> > +}
>> > +
>> > +static int by
flight 58157 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58157/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
Hi Andrew,
Thank you for your reply!
I do not know much about migration V2. Was it integrated to Xen? If
integrated, from which version?
Thank you!!
Best Regards,
Yunfang
2015-06-06 3:00 GMT+08:00 Andrew Cooper :
> On 05/06/15 19:45, Konrad Rzeszutek Wilk wrote:
> > On Thu, Jun 04, 2
Hi Konrad,
Thank you for your reply!
It does not matter whether it is 1000 or not. Most of the save &
restore operations will be failed
when there are more than 1000 pages put in the persistent pool. Some of the
operations
will be success when there are not so much pages put in the persiste
On 05/27/2015 07:05 PM, David Vrabel wrote:
On 27/05/15 17:25, David Vrabel wrote:
On 20/04/15 06:23, Juergen Gross wrote:
64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
main reason has been the 3 level p2m tree, which was replaced by the
virtual mapped linear p2m list. Par
flight 58119 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58119/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 11 guest-start fail REGR. vs. 53854
test-amd64-amd64-libvirt
Ping?
Anything missing from my side?
On 04/30/2015 12:53 PM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
instruc
flight 58121 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58121/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 56492
test-amd64-i386-xl-qemuu-win
On 06/05/2015 09:53 PM, wei.l...@citrix.com wrote:
(Note, please trim your quotes when replying, and also trim the CC list if
necessary. You might also consider changing the subject line of your reply to
"Status of (Was: Xen 4.6 Development Update (X months reminder)")
Hi all
We are now four m
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/
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 v2 COLOPre 00/13] Prerequisite patches for COLO
We only support hvm guest now. The codes are also host
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-
From: Wen Congyang
Usage: disk = ['...,colo,colo-params=xxx,active-disk=xxx,hidden-disk=xxx...']
The format of colo-params: host:port:exportname=xx
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
---
docs/man/xl.pod.1 | 2 +-
tools/libxl/libxl.c | 42 ++-
too
From: Wen Congyang
The guest should be paused before doing COLO!!!
Signed-off-by: Wen Congyang
---
tools/libxl/Makefile | 1 +
tools/libxl/libxl_colo_qdisk.c | 209 +++
tools/libxl/libxl_colo_restore.c | 21 +++-
tools/libxl/libxl_colo_save.
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
call callbacks->get_dirty_pfn() after suspend primary vm to
get dirty pages 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_save.c | 49 +++
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
d. Read secondary vm's dirty page information to master(count + pfn list)
2. Get dirty pfn list callback
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 | 11 +--
tools/libxc/xc_sr_restore.c | 63 +
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 is a function pointers in callbacks struct and struct
{save,restore}_callbacks, and use this callback to send store
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
setup/teardown of COLO proxy module.
we use netlink to communicate with proxy module.
Signed-off-by: Yang Hongyang
---
tools/libxl/Makefile | 1 +
tools/libxl/libxl_colo.h | 2 +
tools/libxl/libxl_colo_proxy.c | 210 +
tools/libxl/libxl
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
setup and control colo proxy on primary side
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl_colo_save.c | 125 +++---
tools/libxl/libxl_internal.h | 1 +
2 files changed, 118 insertions(+), 8 deletions(-)
diff --git a/tools/libxl/libxl_colo_save.c b/to
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 +++
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
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
This is just tidying up after the previous automatic renaming.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_checkpoint_device.c | 21 +++--
tools/libxl/libxl_internal.h | 19 +++
2 files changed, 22 insertions(+), 18 del
From: Wen Congyang
Currently, all callbacks return an integer value or void. We cannot
return some data to xc via callback. Update libxl_save_msgs_gen.pl
to support this case.
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_internal.h | 3 ++
tools/libxl/libxl_save_callout.c | 31
When we are under COLO, we will send dirty page bitmap info from
secondary to primary at every checkpoint. So we need to get/test
the dirty page bitmap. We just expose xc_bitops.h for libxl use.
NOTE:
Need to make clean and rerun configure to get it compiled.
Signed-off-by: Yang Hongyang
---
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
ioreq page contains evtchn which will be set when we resume the
secondary vm the first time. The hypervisor will check if the
evtchn is corrupted, so we cannot zero the ioreq page more
than one time.
The ioreq->state is always STATE_IOREQ_NONE after the vm is
suspended, so it is OK if we only zero
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
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.
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
---
tools/libxl/l
From: Wen Congyang
For PVHVM, the hypercall return code is 0, and it can be resumed
in a new domain context.
we suspend PVHVM and resume it is like this:
1. suspend it via evtchn
2. modifty the return code to 1
3. the guest know that the suspend is cancelled, we will use fast path
to resume it
From: Wen Congyang
The guest is paused after libxl_domain_create_restore().
Secondary vm is running in colo mode. So we need to unpause
the guest. The current API libxl_domain_unpause() is
not an internal API. Introduce a new API to support it.
No functional change.
Signed-off-by: Wen Congyang
This patchset is Prerequisite for COLO feature. For what COLO is, refer
to http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
This patchset is based on:
[PATCH v2 0/6] Misc cleanups for libxl
You can also get the patchset from:
https://github.com/macrosheep/xen/tree/colo-v6
v1->v2:
Currently, libxl__domain_unpause() only supports
qemu-xen-traditional. Update it to support qemu-xen.
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
---
tools/libxl/libxl.c | 42 +-
1 file changed, 33 insertions(+), 9 deletions(-)
diff --git a/
If the err is RECORD_NOT_PROCESSED, and it is an optional record,
restore will still fail. The patch fix this.
Signed-off-by: Yang Hongyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
---
tools/libxc/xc_sr_restore.c | 28 ++--
1 file changed, 14 ins
> -Original Message-
> From: wei.l...@citrix.com [mailto:wei.l...@citrix.com]
> Sent: Friday, June 5, 2015 9:54 PM
>
> Hi all
>
> We are now four months into 4.6 development window. This is an email to keep
> track of all the patch series I gathered. It is by no means complete and / or
>
On 2015/6/7 19:20, Wei Liu wrote:
On Wed, Jun 03, 2015 at 10:25:47AM +0800, Chen, Tiejun wrote:
[...]
+static struct xen_reserved_device_memory
+*xc_device_get_rdm(libxl__gc *gc,
+ uint32_t flag,
+ uint16_t seg,
+ uint8_t bus,
+
On 26/05/2015 21:58, Jan Beulich wrote
> >>> On 13.05.16 at 09:50, wrote:
> > +static int byt_get_min_pstate(void)
> > +{
> > +u64 value;
> > +
> > +rdmsrl(BYT_RATIOS, value);
> > +return (value >> 8) & 0x7F;
> > +}
> > +
> > +static int byt_get_max_pstate(void)
> > +{
> > +u64 val
On 2015/6/7 19:06, Wei Liu wrote:
On Wed, Jun 03, 2015 at 09:35:16AM +0800, Chen, Tiejun wrote:
[...]
+reserved regions explicitly. And using "host" to include all reserved regions
+reported on this platform which is good to handle hotplug scenario. In the
+future this parameter may be further
> -Original Message-
> From: wei.l...@citrix.com [mailto:wei.l...@citrix.com]
> Sent: Friday, June 05, 2015 9:54 PM
> To: xen-de...@lists.xenproject.org; White, Edmund H;
> xumengpa...@gmail.com; dgol...@seas.upenn.edu; lichong...@gmail.com;
> jtwea...@hawaii.edu; oleksandr.dmytrys...@glo
flight 58104 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58104/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 3 host-install(3) broken REGR. vs. 57815
test-amd64-amd64-xl
flight 58111 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58111/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail in 58064 REGR. vs. 57312
Tests which are faili
flight 58095 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58095/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 11 guest-start fail REGR. vs. 57903
test-amd64-i386-libvirt
On 05/06/2015 21:14, Chris (Christopher) Brand wrote:
Hi Julien,
Hi Chris,
When the property "clock-frequency" is present in the DT timer node, it means
that the bootloader/firmware didn't correctly configured the
CNTFRQ/CNTFRQ_EL0 on each processor.
I did try this out, and it didn't aff
flight 58087 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58087/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 9 debian-install fail REGR. vs. 52209-bisect
test-amd64-amd64-pair
flight 58060 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58060/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-sedf 17 guest-localmigrate/x10 fail in 57881 pass in 58060
test-amd64-i386-xend-qemut-winx
flight 58057 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58057/
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. 5
flight 58090 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58090/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 56492
test-amd64-i386-xl-qemuu-win
flight 58015 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58015/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 11 guest-start fail REGR. vs. 53854
test-amd64-amd64-libvirt
flight 57955 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57955/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xend-qemut-winxpsp3 16 guest-stop fail in 57895 pass in 57955
test-amd64-i386-xend-winxpsp3 1
flight 58064 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58064/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail REGR. vs. 57312
Tests which are failin
On Mon, Jun 01, 2015 at 09:13:08AM +, Maoming wrote:
> Hi all:
>I encountered a troublesome problem about OVMF.
>I used OVMF.fd as a BIOS of virtual machine(VM).
>
>1、my environment:
>xen_version: 4.6-unstable
>I git clone xen from git://xenb
Hi
Please CC me and Anthony (CC'ed) in the future if you have questions
regarding OVMF on Xen.
On Tue, May 26, 2015 at 12:02:22PM +0200, Laszlo Ersek wrote:
> On 05/25/15 03:50, lidonglin wrote:
> > Hi all:
>
> > Recentlly, I want to use PXE boot on Xen with OVMF as bios. At
> > beginning, I jus
On Fri, Jun 05, 2015 at 08:29:39AM +, Jason Long wrote:
> Hello Experts.What is "Ling" and why Xen choose "Erlang" ? Can you tell me
> about the future of it on Xen? what is the goal?
> Thank you.
Erlang on Xen is not affiliated with Xen project. You should
ask on their mailing list instead.
On Wed, Jun 03, 2015 at 05:07:59PM +, Joao Martins wrote:
[...]
> >
> > How much harder would it be to ref-count inflight grants? Would that
> > simplify or perplex things? I'm just asking, not suggesting you should
> > choose ref-counting over current scheme.
> >
> > In principle I favour si
On Thu, Jun 04, 2015 at 12:28:19PM +0100, Stefano Stabellini wrote:
> Starts a second QEMU to provide PV backends in userspace to HVM guests.
>
> Signed-off-by: Stefano Stabellini
> ---
> tools/libxl/libxl_create.c | 18 ++
> tools/libxl/libxl_dm.c |9 -
> 2 fil
On Sun, Jun 07, 2015 at 12:38:38PM +0100, Wei Liu wrote:
> On Thu, Jun 04, 2015 at 12:27:12PM +0100, Stefano Stabellini wrote:
> > Hi all,
> >
> > this patch series changes libxl to start QEMU as device model with the
> > new xsrestrict option (http://marc.info/?l=xen-devel&m=143341692707358).
> >
On Thu, Jun 04, 2015 at 12:28:15PM +0100, Stefano Stabellini wrote:
> The device model is going to restrict its xenstore connection to $DOMID
> level. Let it access /local/domain/0/device-model/$DOMID, as it is
> required by QEMU to read/write the physmap. It doesn't contain any
> information the g
On Thu, Jun 04, 2015 at 12:27:12PM +0100, Stefano Stabellini wrote:
> Hi all,
>
> this patch series changes libxl to start QEMU as device model with the
> new xsrestrict option (http://marc.info/?l=xen-devel&m=143341692707358).
> It also starts a second QEMU to provide PV backends in userspace (qd
flight 57925 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57925/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 11 guest-saverestore fail REGR.
vs. 57815
test-amd6
On Wed, Jun 03, 2015 at 10:58:31AM +0800, Chen, Tiejun wrote:
> On 2015/6/3 0:36, Wei Liu wrote:
> >On Fri, May 22, 2015 at 05:35:08PM +0800, Tiejun Chen wrote:
> >>This patch passes rdm reservation policy to xc_assign_device() so the policy
> >>is checked when assigning devices to a VM.
> >>
> >>S
On Wed, Jun 03, 2015 at 10:25:47AM +0800, Chen, Tiejun wrote:
[...]
> >>+static struct xen_reserved_device_memory
> >>+*xc_device_get_rdm(libxl__gc *gc,
> >>+ uint32_t flag,
> >>+ uint16_t seg,
> >>+ uint8_t bus,
> >>+ uint8_t
On Wed, Jun 03, 2015 at 09:35:16AM +0800, Chen, Tiejun wrote:
[...]
> >
> >>+reserved regions explicitly. And using "host" to include all reserved
> >>regions
> >>+reported on this platform which is good to handle hotplug scenario. In the
> >>+future this parameter may be further extended to allow
From: Julien Grall
Date: Thu, 4 Jun 2015 16:35:13 +0100
> rx->status is an int16_t, print it using %d rather than %u in order to
> have a meaningful value when the field is negative.
>
> Also use %d rather than %x for rx->offset.
>
> Signed-off-by: Julien Grall
> Reviewed-by: David Vrabel
> C
flight 58008 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58008/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 57
70 matches
Mail list logo
