>>> On 12.11.15 at 23:54, wrote:
> The switch to Kconfig provides variables prefixed with CONFIG_ with
> results in a redefinition of this variable.
So I can't see how this can be a separate patch: Either the
redefinition causes a build failure after the previous patch (if
CONFIG_64BIT gets intro
>>> On 13.11.15 at 06:47, wrote:
> I saw xen hang after
>
> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
> (
>
> The line that's supposed to be there is
>
> (XEN) Brought up 24 CPUs
>
> After power cycling I went into the BIOS. In the BIOS, C-STATE was disabled.
> I changed it to
>
> * Intel(R)
On Fri, Nov 13, 2015 at 10:48 AM, Jan Beulich wrote:
On 12.11.15 at 18:09, wrote:
>> On Thu, 2015-11-12 at 08:44 -0700, Jan Beulich wrote:
>>> > > > On 12.11.15 at 14:41, wrote:
>>> > Hello, all. I'd like to have set of commands that would boot xen on all
>>> > platforms. I thought of follo
On Thu, 2015-11-12 at 10:53 -0700, Jim Fehlig wrote:
> Ian Campbell wrote:
> > On Thu, 2015-11-12 at 08:45 -0700, Jim Fehlig wrote:
> > >
> > > > The commit message doesn't say anything about AHCI. Are AHCI disks
> > > > actually emulated correctly by QEMU with readonly=on?
> > > I just double ch
On Thu, 2015-11-12 at 15:55 +, Wei Liu wrote:
>
> Note that my Wheezy PV installation is using grub2 so pvgrub doesn't
> seem to be able to parse its config file
FYI you can workaround this by installing the "pv-grub-menu" package (in
wheezy-backports and from Jessie onwards) which provides
On Fri, 2015-11-13 at 00:48 -0700, Jan Beulich wrote:
> > > > On 12.11.15 at 18:09, wrote:
> > On Thu, 2015-11-12 at 08:44 -0700, Jan Beulich wrote:
> > > > > > On 12.11.15 at 14:41, wrote:
> > > > Hello, all. I'd like to have set of commands that would boot xen on
> > > > all
> > > > platforms.
On Fri, 2015-11-13 at 12:04 +0300, Andrei Borzenkov wrote:
> > How do you express modules other than kernel+initrd in that
> > scheme, without grub needing to be aware of any new addition we
> > may find necessary going forward?
> >
>
> Are modules used by Xen self-identifying? Is it enough to si
In fact, with 2 cpupools, one (the default) Credit and
one Credit2 (with at least 1 pCPU in the latter), trying
a (e.g., ACPI S3) suspend/resume crashes like this:
(XEN) [ 150.587779] [ Xen-4.7-unstable x86_64 debug=y Not tainted ]
(XEN) [ 150.587783] CPU:6
(XEN) [ 150.587786] RI
On 13/11/15 07:25, Jan Beulich wrote:
On 13.11.15 at 00:00, wrote:
>> Am 12.11.15 um 17:43 schrieb Andrew Cooper:
>>> On 12/11/15 14:29, Atom2 wrote:
Hi Andrew,
thanks for your reply. Answers are inline further down.
Am 12.11.15 um 14:01 schrieb Andrew Cooper:
> On 12/
flight 38274 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38274/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-jessie-netboot-pygrub 12 saverestore-support-check fail
never pass
test-armhf-ar
Hu, Robert writes ("RE: Osstest nested patch v15 (was RE: [OSSTEST PATCH v14
PART 2 10-26/26] Nested HVM testing)"):
> Yes. In last test step, ts-logs-capture host, I can see
>
> 2015-11-12 03:22:06 Z fetching
> /var/log/xen/osstest-serial-l1.guest.osstest.log to
> osstest-host2---var-log-xen-o
flight 64147 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64147/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-xl
On Thu, 12 Nov 2015, Doug Goldstein wrote:
> Handle unknown distros by saying "unknown" instead of an empty string
> and for Gentoo users actually mention it.
>
> Signed-off-by: Doug Goldstein
Acked-by: Stefano Stabellini
and applied
> lib/common-functions.sh | 5 +
> 1 file changed, 5
On Thu, 12 Nov 2015, Jim Fehlig wrote:
> The fix for XSA-142 is quite a big hammer, rejecting readonly
> disk configuration even when the requested backend is known to
> support readonly. While it is true that qemu doesn't support
> readonly for emulated IDE or AHCI disks
>
> $ /usr/lib/xen/bin/qe
On 12/11/15 17:30, Stefano Stabellini wrote:
> Try XENPF_settime64 first, if it is not available fall back to
> XENPF_settime32.
>
> No need to call __current_kernel_time() when all the info needed are
> already passed via the struct timekeeper * argument.
>
> Return NOTIFY_BAD in case of errors.
>>> On 13.11.15 at 11:08, wrote:
> Fix things by properly deallocating scheduler specific
> data of the pCPU's pool scheduler during pCPU teardown,
> and re-allocating them --always for &ops-- during pCPU
> bringup.
Avoiding this was done for a reason iirc: What if one such allocation
fails (e.g.
On Fri, 13 Nov 2015, David Vrabel wrote:
> On 12/11/15 17:30, Stefano Stabellini wrote:
> > Try XENPF_settime64 first, if it is not available fall back to
> > XENPF_settime32.
> >
> > No need to call __current_kernel_time() when all the info needed are
> > already passed via the struct timekeeper
Hello,
Due to the HVMlite patches now x86 always requires a valid arch domain
config. This is currently causing problems to out-of-tree toolstacks that
are based on the Ocaml or the python bindings, since those bindings have lost
the ability to create HVM guests because a zeroed arch domain con
Due to the addition of HVMlite and the requirement to always provide a valid
xc_domain_configuration_t, xc_domain_create now always takes an arch domain
config, which can be NULL in order to mimic previous behaviour.
Signed-off-by: Roger Pau Monné
---
Cc: Stefano Stabellini
Cc: qemu-de...@nongnu
With the addition of HVMlite the hypervisor now always requires a non-null
arch domain config, which is different between HVM and PV guests.
Add a new parameter to xc_domain_create that contains a pointer to an arch
domain config. If the pointer is null, create a default arch domain config
based o
On Fri, 13 Nov 2015, Roger Pau Monne wrote:
> Due to the addition of HVMlite and the requirement to always provide a valid
> xc_domain_configuration_t, xc_domain_create now always takes an arch domain
> config, which can be NULL in order to mimic previous behaviour.
>
> Signed-off-by: Roger Pau Mon
On Fri, Nov 13, 2015 at 09:28:11AM +, Ian Campbell wrote:
> On Thu, 2015-11-12 at 15:55 +, Wei Liu wrote:
> >
> > Note that my Wheezy PV installation is using grub2 so pvgrub doesn't
> > seem to be able to parse its config file
>
> FYI you can workaround this by installing the "pv-grub-m
On Mon, 9 Nov 2015, Julien Grall wrote:
> Each ITARGETSR register are 4-byte wide and the offset is in byte.
>
> The current implementation is computing the end of the range wrongly
> resulting to emulate only ITARGETSR{0,1} read-only. The rest will be
> treated as read-write.
>
> As 8 registers
Hi Doug,
On 12/11/15 22:54, Doug Goldstein wrote:
> Use the Kconfig generated CONFIG_HAS_GICV3 defines in the code base.
>
> CC: Ian Campbell
> CC: Stefano Stabellini
> Signed-off-by: Doug Goldstein
> ---
> xen/arch/arm/Kconfig | 5 +
> xen/arch/arm/Makefile| 2 +-
> xen/a
On Wed, Oct 21, Chunyan Liu wrote:
> Add pvusb APIs, including:
> @@ -635,6 +664,8 @@ libxl_domain_config = Struct("domain_config", [
> ("pcidevs", Array(libxl_device_pci, "num_pcidevs")),
> ("rdms", Array(libxl_device_rdm, "num_rdms")),
> ("dtdevs", Array(libxl_device_dtdev, "num_
Hi Doug,
On 12/11/15 22:54, Doug Goldstein wrote:
> The following series is a follow on to the Kconfig conversion patch series.
> There are still more components to convert however this is the bare minimal
> to get everything working and get the options out of the existing makefiles.
>
> The CONF
Hi all,
The main point of this series is to fix the access to any register when the
user doesn't write at the base offset of the registers.
At the same, I took the opportunity to re-arrange the emulation and dropping
any registers which doesn't exists or not required by the spec.
This series is
Our vGIC emulation have GICD_TYPER.MBIS set to 0 which means that
GICD_*SPI_* registers are reserved. Implement them using the *_reserved
labels.
Also, implement thoses registers for the read part.
Signed-off-by: Julien Grall
---
xen/arch/arm/vgic-v3.c | 24
1 file chan
Signed-off-by: Julien Grall
---
xen/arch/arm/vgic-v3.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/vgic-v3.c
index 98104ba..c68afdb 100644
--- a/xen/arch/arm/vgic-v3.c
+++ b/xen/arch/arm/vgic-v3.c
@@ -248,7 +248,6 @@ static int __vgic_v3_rdistr_rd_mmio
The GICD_ICACTIVER registers are missing in the read emulation of the
distributor.
Call the common emulation for the whole range.
Signed-off-by: Julien Grall
---
xen/arch/arm/vgic-v3.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/vgic-v3.c
index f9d8
The offset is 0x0D00 and not 0x0F80.
Also re-order the definition to keep all the definitions ordered.
Signed-off-by: Julien Grall
---
xen/include/asm-arm/gic_v3_defs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/include/asm-arm/gic_v3_defs.h
b/xen/include/asm-arm/g
A read to a write only register is unknown. Use a memorable value to
differentiate from an actual RAZ register.
Signed-off-by: Julien Grall
---
xen/arch/arm/vgic-v3.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/v
Most of the identification registers space contains implementation
defined registers (see 8.1.13 in ARM IHI 0069A) and only GIC{D,R}_PIDR2
is required to be implemented.
Currently the emulation of those registers mimic the ARM implementation,
but it's untrue to say that we properly emulate a such
It helps to find quickly whether we forgot to emulate a register or not.
At the same time add the missing reserved/implementation defined
registers. All other missing registers will be added in a follow-up if
necessary.
Note that only the distributor register map explicitely say the
size of a reg
The 2 registers are not described in the software spec (ARM IHI 0069A)
and their offsets are marked "implementation defined".
Signed-off-by: Julien Grall
---
Note that I didn't combine the 2 cases because a follow-up patch
will add reserved registers between the 2 cases.
---
xen/arch/arm/vgic-
The offset in the emulation is based on byte. As most of the registers
are 64/32 bits, they will span over multiple bytes.
However, the current emulation only care about the first offset. This
will result to not emulate properly any access on the register with
other offset.
Introduce new macros t
flight 64149 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64149/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 64035
test-armhf-armhf-xl-
Note: just a rebase close to "RELEASE-4.6.0", with no substantial changes
Port vscsi=[] and scsi-{attach,detach,list} commands from xend to libxl.
libvirt uses its existing SCSI support:
http://lists.xenproject.org/archives/html/xen-devel/2015-04/msg02963.html
targetcli/rtslib has to be aware of
Port pvscsi support from xend to libxl:
vscsi=['pdev,vdev{,options}']
xl scsi-attach
xl scsi-detach
xl scsi-list
Signed-off-by: Olaf Hering
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
docs/man/xl.cfg.pod.5| 55 +++
docs/man/xl.pod.1
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
xen/include/public/io/vscsiif.h | 68 +
1 file changed, 68 insertions(+)
diff --git a/xen/include/public/io/vscsiif.
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
docs/misc/xenstore-paths.markdown | 10 ++
1 file changed, 10 insertions(+)
diff --git a/docs/misc/xenstore-paths.markdown
b/docs/misc/xenstore-pat
Just to make them public, not meant for merging:
The scripts used during development to create a bunch of SCSI devices in
dom0 using the Linux target framework. targetcli3 and rtslib3 is used.
A patch is required for python-rtslib:
http://article.gmane.org/gmane.linux.scsi.target.devel/8146
Signe
The pvops kernel expects either "naa.WWN:LUN" or "h:c:t:l" in the p-dev
property. Add the missing :LUN part to the comment.
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
xen/include/public/io/vscsiif.h
Hi Stefano,
On 12/11/15 17:46, Stefano Stabellini wrote:
> Call update_domain_wallclock_time at domain initialization.
> Set time_offset_seconds to the number of seconds between physical boot
> and domain initialization: it is going to be used to get/set the
> wallclock time.
> Add time_offset_sec
Hi Stefano,
On 12/11/15 17:46, Stefano Stabellini wrote:
> This is just a cleanup, not required at the moment.
>
> Signed-off-by: Stefano Stabellini
Reviewed-by: Julien Grall
> ---
> xen/arch/arm/vtimer.c |3 ---
> xen/include/asm-arm/time.h |3 +++
> 2 files changed, 3 insertio
This is safe only if no existing flights would be affected. (That is,
the meaning of no existing sets of runvars would be changed.)
To check whether this would make any difference I did some database
searches. Since any time target_kernkind_check is called it sets a
corresponding `console' runva
From: Robert Ho
Signed-off-by: Robert Ho
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v14: ts-nested-setup command line syntax updated.
v15: (Robert Ho) remove the unnecessary l1 destroy; as it will
implicitly powered off by framework as a nested host.
From: Robert Ho
L1 guests' serial ports are owned by qemu in L0. We can send them
debug keys by writing to the qemu pipe.
(xl debug-key looks like it would be useful but it actually sends
debug keys to the hypervisor of the host it is running on. We want to
send the debug keys to the hyperviso
From: Robert Ho
await_tcp is often invoked after a reboot.
In this situation the target's IP address may change. If this happens
while await_tcp is running, we would continue to poll the old IP address.
Fix this by running target_check_ip on each iteration.
Signed-off-by: Robert Ho
Signed-off
From: Robert Ho
This `guest' power method uses VM create/destroy. It is automatically
used for nested hosts. It would not make much sense to configure it
manually.
For nested host/guest, its power on/off method shall be
its host invoke $(toolstack)->create/destroy method.
Signed-off-by: Rober
From: Robert Ho
* Provide the L1 with some storage for its own guests' disks
* Install some packages in the L1
* Optionally, set a runvar defining the L1 for the rest of the job
The recipe is going to run ts-xen-install etc.
Signed-off-by: longtao.pang
Signed-off-by: Robert Ho
Signed-off-by:
From: Robert Ho
Signed-off-by: longtao.pang
Signed-off-by: Robert Ho
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
---
v17: Use usual_debianhvm_image
v14: Use default gueststorage_size, rather than setting runvar.
Dropped acked from Ian Campbell.
---
make-flight | 28 +++
From: Robert Ho
For nested cases, nested host can inherit its host's property for
dhcp watch setup and ether_prefix property setup.
Signed-off-by: Robert Ho
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v15: New patch
---
Osstest/TestSupport.pm |4 ++--
1 file changed, 2 insertions(+),
This is, I think, a fully-working series to support Nested HVM testing
in osstest. It can be found here:
git://xenbits.xen.org/people/iwj/osstest.git
http://xenbits.xen.org/git-http/people/iwj/osstest.git
in base.nested-hvm.v17..wip.nested-hvm.v17
a 01 cs-adjust-flight: Add some missing doc
Provides nested-layer-descend, which can be called in an individual
test job at the appropriate point (after the L1 has been set up).
The inner host is a guest of the outer host; powering it off means
destroying it. Putting the poweroff at this point in the loop, rather
than in per-host-finish, a
Document the syntax for $ident.
Log the ident as well as the selected hostname.
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v17: Fix typo in doc message.
v14: New patch
---
Osstest/TestSupport.pm | 16 +++-
1 file changed, 15 insertions(+), 1 delet
The sympathy and xenuse serial modules had too much in common. Factor
out the common code, which is now responsible for
- knowledge of the Xen console switch
- splitting strings up into individual keys
- timing decisions
- error trapping and logging
This new class is an abstract base clas
Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
---
v14: New patch
---
cs-adjust-flight |8
1 file changed, 8 insertions(+)
diff --git a/cs-adjust-flight b/cs-adjust-flight
index 4bfef48..d70abf7 100755
--- a/cs-adjust-flight
+++ b/cs-adjust-flight
@@ -24,6 +24,14 @@
# .
This allows cs-adjust-flight to be run by hand to adjust runvars, in a
flight being used with hand-invocation of ./ts-* scripts.
Signed-off-by: Ian Jackson
Tested-by: Ian Jackson
---
v17: Better documentation of running: flight status
v14: New patch
---
cs-adjust-flight |9 +
1 file
From: Robert Ho
Check IpStatic, and if it is not set, provide a dhcp stanza in
/etc/network/interfaces, rather than an `inet static' one.
This is necessary for L1 nested hosts, because they don't have a
static IP address.
In principle this makes matters more correct for physical hosts
without s
We are going to want to reuse this.
lv_create doesn't (want to) take a $gho, but the $vg and $lv names
directly (so that callers can use it when they don't have a suitable
$gho whose $gho->{Lvdev} they want to use).
In the one existing call site we pass $gho->{Vg} and $gho->{Lv} so
that the effec
Modern qemu has the "pipe:/PATH" character driver. This opens
/PATH.in for reading and /PATH.out for writing. In my tests, I found
that:
- contrary to the documentation, they do not need to be pipes
(at least, /PATH.out can be a file)
- but they must both already exist
- qemu will follo
No functional change.
We now call the per-host-ts finish steps unconditionally, rather than
only if !$need_build_host, per-host-ts is (complicated) no-op if
$need_build_host, since in that case $need_xen_hosts is {}.
Signed-off-by: Ian Jackson
Tested by: Robert Ho
Acked-by: Ian Campbell
---
v1
Make this function suitable for running on targets with static IP
addresses. (Ie, on physical hosts.) Accordingly, rename it and
adjust all call sites.
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v14: New patch
---
Osstest/TestSupport.pm | 11 ++-
ts-
No functional change. (Verified for xen-unstable with
standalone-generate-dump-flight-runvars.)
Signed-off-by: Ian Jackson
Tested-by: Ian Jackson
---
v17: New patch.
---
make-flight |2 +-
mfi-common |5 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/make-flight b
This talks about `guest_check_ip', but this code is now factored out
into a method. Use the correct method name in reporting.
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v14: New patch
---
Osstest/DhcpWatch/leases.pm |2 +-
1 file changed, 1 insertion(+), 1
Like sympathy, attaching via xenuse causes xenuse to send output from
the host to its own stdout.
But we don't want the ts-logs-capture stdout to contain this serial
output, interleaved with its own log messages. We'll capture the
whole serial log from the xenuse logfile. So redirect it to /dev/
This function does not (now) always undo the DHCP configuration.
Sometimes it leaves it. Its main function is to ensure that we have
a bridge for use by guests.
So rename the function.
Signed-off-by: Ian Jackson
Tested-by: Robert Ho
Acked-by: Ian Campbell
---
v14: This patch was previously 4/
It is possible that this may work some of the time with xm, so I have
taken no measures to prevent it running then.
Signed-off-by: Ian Jackson
Signed-off-by: Robert Hu
Tested-by: Robert Hu
Acked-by: Ian Campbell
v14: New patch
v15: Fix missing $ho assignment in block-attach method
---
Os
We introduce a new syntax: instead of a hostname (which might appear
in a command line argument to a ts-* script and hence be passed to
selecthost, or which might be in a runvar), we now support
:.
Such `hosts' (let us refer to such a thing as an L1, although in
principle further nesting may be po
On Mon, 9 Nov 2015, Julien Grall wrote:
> During a store, the byte is always in the low part of the register (i.e
> [0:7]).
>
> We are incorrectly masking the register by using a shift of the byte
> offset in the ITARGETSR while the byte is alwasy in r[0:7]. This will
> result in a target list equ
On Fri, 2015-11-13 at 12:03 +, Ian Jackson wrote:
> This allows cs-adjust-flight to be run by hand to adjust runvars, in a
> flight being used with hand-invocation of ./ts-* scripts.
>
> Signed-off-by: Ian Jackson
> Tested-by: Ian Jackson
Acked-by: Ian Campbell
__
On Fri, 2015-11-13 at 12:03 +, Ian Jackson wrote:
> No functional change. (Verified for xen-unstable with
> standalone-generate-dump-flight-runvars.)
>
> Signed-off-by: Ian Jackson
> Tested-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel
On Fri, 2015-11-13 at 12:03 +, Ian Jackson wrote:
> From: Robert Ho
>
> L1 guests' serial ports are owned by qemu in L0. We can send them
> debug keys by writing to the qemu pipe.
>
> (xl debug-key looks like it would be useful but it actually sends
> debug keys to the hypervisor of the hos
On Fri, 2015-11-13 at 12:03 +, Ian Jackson wrote:
> Like sympathy, attaching via xenuse causes xenuse to send output from
> the host to its own stdout.
>
> But we don't want the ts-logs-capture stdout to contain this serial
> output, interleaved with its own log messages. We'll capture the
>
Due to the addition of HVMlite and the requirement to always provide a valid
xc_domain_configuration_t, xc_domain_create now always takes an arch domain
config, which can be NULL in order to mimic previous behaviour.
Add a small stub called xen_domain_create that encapsulates the correct call
to x
On Fri, 2015-11-13 at 03:41 -0700, Jan Beulich wrote:
> > > > On 13.11.15 at 11:08, wrote:
> > Fix things by properly deallocating scheduler specific
> > data of the pCPU's pool scheduler during pCPU teardown,
> > and re-allocating them --always for &ops-- during pCPU
> > bringup.
>
> Avoiding th
On 13/11/15 11:05, Roger Pau Monne wrote:
> With the addition of HVMlite the hypervisor now always requires a non-null
> arch domain config, which is different between HVM and PV guests.
>
> Add a new parameter to xc_domain_create that contains a pointer to an arch
> domain config. If the pointer i
>>> On 13.11.15 at 13:30, wrote:
> On Fri, 2015-11-13 at 03:41 -0700, Jan Beulich wrote:
>> > > > On 13.11.15 at 11:08, wrote:
>> > Fix things by properly deallocating scheduler specific
>> > data of the pCPU's pool scheduler during pCPU teardown,
>> > and re-allocating them --always for &ops-- d
>>> On 13.11.15 at 12:41, wrote:
> 2) make menuconfig doesn't expose any options => No possibility to
> select any UART on ARM.
>
> The latter is because how you define the option in the Kconfig:
>
> config HAS_EXYNOS4210
> bool
>
> Without any text, it's not possible for the user to sele
Introduce support for domainGetJobInfo to get info about the
ongoing job. If the job is active it will update the
timeElapsed which is computed with the "started" field added to
struct libxlDomainJobObj. For now we support just the very basic
info and all jobs have VIR_DOMAIN_JOB_UNBOUNDED (i.e. n
Introduce support for domainMemoryStats API call, which
consequently enables the use of `virsh dommemstat` command to
query for memory statistics of a domain. We support
the following statistics: balloon info, available and currently
in use. swap-in, swap-out, major-faults, minor-faults require
coo
Introduces support for domainGetJobStats which has the same
info as domainGetJobInfo but in a slightly different format.
Another difference is that virDomainGetJobStats can also
retrieve info on the most recently completed job. Though so
far this is only used in the source node to know if the
migra
Introduce support for connectGetAllDomainStats call that
allow us to _all_ domain(s) statistics including network, block,
cpus and memory. Changes are rather mechanical and mostly
take care of the format to export the data.
Signed-off-by: Joao Martins
---
Changes since v1:
- Rework flags checkin
Introduce a new helper function "virDiskNameParse" which extends
virDiskNameToIndex but handling both disk index and partition index.
Also rework virDiskNameToIndex to be based on virDiskNameParse.
A test is also added for this function testing both valid and
invalid disk names.
Signed-off-by: Joa
Hey,
[ Apologies for resending this series before receiving comments, but I
found two issues (namely on patch 3 and 4) and thus I am reposting it
as v3 having those fixed. ]
This series bring support for various statistics about domains
regarding CPU, Memory, Network Interfaces, Block and Job
Introduce support for domainGetCPUStats API call and consequently
allow us to use `virsh cpu-stats`. The latter returns a more brief
output than the one provided by`virsh vcpuinfo`.
Signed-off-by: Joao Martins
---
Changes since v1:
- Remove libxl_vcpuinfo_dispose() in favor or using
libxl_vcpui
Introduce initial support for domainBlockStats API call that
allow us to query block device statistics. openstack nova
uses this API call to query block statistics, alongside
virDomainMemoryStats and virDomainInterfaceStats. Note that
this patch only introduces it for VBD for starters. QDisk
will
Introduce support for domainInterfaceStats API call for querying
network interface statistics. Consequently it also enables the
use of `virsh domifstat ` command.
After succesful guest creation we fill the network
interfaces names based on domain, device id and append suffix
if it's emulated in t
(XEN) [0.00] IRQ limits: 72 GSI, 15304 MSI/MSI-X
(XEN) [0.00] Switched to APIC driver x2apic_cluster.
(XEN) [6.333211] I/O virtualisation enabled
(XEN) [6.339317] - Dom0 mode: Relaxed
(XEN) [6.344720] Interrupt remapping enabled
(XEN) [6.350864] Enabled directed EO
On 13/11/15 12:54, Jan Beulich wrote:
On 13.11.15 at 12:41, wrote:
>> 2) make menuconfig doesn't expose any options => No possibility to
>> select any UART on ARM.
>>
>> The latter is because how you define the option in the Kconfig:
>>
>> config HAS_EXYNOS4210
>> bool
>>
>> Without any
Hi Stefano,
On 12/11/15 17:30, Stefano Stabellini wrote:
> Signed-off-by: Stefano Stabellini
>
> ---
>
> Changes in v2:
> - rename dom0_op to platform_op
> ---
> arch/arm/include/asm/xen/hypercall.h |2 ++
> arch/arm/xen/enlighten.c |1 +
> arch/arm/xen/hypercall.S
Hi Stefano,
On 12/11/15 17:30, Stefano Stabellini wrote:
> The hypervisor actually exposes an additional field to struct
> pvclock_wall_clock, with the high 32 bit seconds.
>
> Signed-off-by: Stefano Stabellini
Reviewed-by: Julien Grall
Regards,
--
Julien Grall
On Fri, 13 Nov 2015, Roger Pau Monne wrote:
> Due to the addition of HVMlite and the requirement to always provide a valid
> xc_domain_configuration_t, xc_domain_create now always takes an arch domain
> config, which can be NULL in order to mimic previous behaviour.
>
> Add a small stub called xen_
On Fri, 2015-11-13 at 13:46 +, Stefano Stabellini wrote:
> On Fri, 13 Nov 2015, Roger Pau Monne wrote:
> > Due to the addition of HVMlite and the requirement to always provide a
> > valid
> > xc_domain_configuration_t, xc_domain_create now always takes an arch
> > domain
> > config, which can b
On 12/11/15 17:30, Stefano Stabellini wrote:
> +static int xen_pvclock_gtod_notify(struct notifier_block *nb,
> +unsigned long was_set, void *priv)
> +{
> + /* Protected by the calling core code serialization */
> + static struct timespec64 next_sync;
> +
> +
On 11/13/15 2:07 AM, Jan Beulich wrote:
On 12.11.15 at 23:54, wrote:
>> The switch to Kconfig provides variables prefixed with CONFIG_ with
>> results in a redefinition of this variable.
>
> So I can't see how this can be a separate patch: Either the
> redefinition causes a build failure aft
On Thu, Nov 12, 2015 at 09:28:36AM -0700, Jan Beulich wrote:
> >>> On 03.11.15 at 19:15, wrote:
> > Signed-off-by: Ross Lagerwall
> > ---
> > v2: Rebased on keyhandler: rework keyhandler infrastructure
> > v3: Fixed XSM.
> > v4: Removed REVERTED state.
> > Split status and error code.
> >
On Fri, 2015-11-13 at 05:52 -0700, Jan Beulich wrote:
>>> On 13.11.15 at 13:30, wrote:
> > cpu_schedule_up() allocates, with the alloc_pdata hook, stuff that
> > was
> > freed by cpu_schedule_down (with the free_pdata hook) already.
>
> If there is no change in the allocation pattern (i.e. inclu
On Mon, 9 Nov 2015, Julien Grall wrote:
> The current implementation ignores the whole write if one of the field is
> 0. Although, based on the spec (4.3.12 IHI 0048B.b), 0 is a valid value
> when:
> - The interrupt is not wired in the distributor. From the Xen
> point of view, it means tha
1 - 100 of 187 matches
Mail list logo
