similar to: [PATCH] [Xm-Test] A test case doing local migration 3 times in a loop

Lots of xm-test tests are failing with console timeouts on some machines at the moment. I reproduced the problem and found it was due to some probing activity in the boot process of the -xen kernel. The behaviour of the current xm-test code is to assume that the boot process has finished after performing three one-second waits for input---when the probing activity introduces more than three

__findFirstOctetIP() is expecting min and max available octets according to its code, however the caller getFreeIP() gives it the min octet and (max - min + 1), which is the length instead. Signed-off-by: Zhu Yanhai <gaoyang.zyh@taobao.com> --- tools/xm-test/lib/XmTestLib/NetConfig.py | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

This patch fixes Linux 2.6.18 compilation on x86-64 and also works on i386. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch rewrites the rtc/timeoffset entry so the VM''s record can be retrieved with the Java xmlrpc library. If the entry is ''None'' it upsets the xmlrpc parser. This fixes it, though maybe there''s a better place in xend to place similar code. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel

This patch adds an implementation of the TCG BIOS extensions to the Bochs BIOS and enables logging of boot measurements using the previously implemented support for TCPA ACPI tables. A low-level driver for a TPM TIS device and an Atmel device is provided. The implemented specification is described here:

Previously, I used to run 2.6.18 kernel built from Xen sources. I just tried to run a 2.6.25.1 domU kernel on top of Xen 3.2 - after changing domU''s config file here and there, I successfully booted the guest, but I''m still unable to use xm console. When I start the domain, it displays all kernel and bootup messages, but I don''t get any prompt after the bootup is

On 01/06/2017 12:27 AM, L. A. Walsh wrote: > Stefan Berger wrote: >> The security.evm extended attribute is fully owned by the Linux kernel >> and cannot be directly written from userspace. Therefore, we can always >> skip it. > --- (see below "...")... > > Please put this on a switch or option. > > The security.evm field seems only special on

This patch adds a TPM device model to the qemu dm for fully virtualized VMs. It is enabled in the VM only if the user requests a TPM device in the vm configuration file using the ''vtpm=[...]'' line. It enables the qemu device model command line with a ''vtpm_instance <instance number>'' parameter. Signed-off-by: David Safford <safford@watson.ibm.com>

This patch adds TCG BIOS extensions to the high memory area along with some often-used libc utility functions. The TCG extensions are described here: https://www.trustedcomputinggroup.org/specs/PCClient/TCG_PCClientImplementationforBIOS_1-20_1-00.pdf I have tried to keep the patching with rombios.c to a minimum, but some amount of code needs to be inserted at various locations. The code is

Testing on an 8-node 128-way NUMA machine has exposed a problem with Xen''s nr_cpus calculation. In this case, since Xen cuts off recognized CPUs at 32, the machine appears to have 16 CPUs on the first and second nodes and none on the remaining nodes. Given this asymmetry, the calculation of sockets_per_node (which is later used to calculate nr_cpus) is incorrect:

The latest change to ACM makes it fail to compile. This patch fixes the problem. Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com> $ diffstat acm.patch acm/acm_core.c | 61 --------------------- include/acm/acm_hooks.h | 135 ++++++++++++++++++++++++++++++++++-------------- 2 files changed, 96 insertions(+), 100 deletions(-) _______________________________________________

This enables the usage of a bootloader, i.e., pygrub, when starting a domain using xm in Xen-API mode. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi All; This problem has come about from trying to learn some of the review practices recommend by rOpensci. One of them is to use the package goodpractice. After installing goodpractice, it kept failing on my own packages which are under development, and I was concerned something was funny in my own , so I have a fork of the package rerddap, and I tested goodpractice on that. I get the

This patch: * adds a C-based security policy translation tool to Xen (secpol_xml2bin) and removes the current Java security policy translator (Java dependencies). The C-based tool integrates into the Xen source tree build and install (using gnome libxml2 for XML parsing). See install.txt. * introduces security labels and related tools. Users can now use semantic-rich label names to put

I am running xen 3.2-1 (Debian 3.2.1-2) on Debian Lenny (2.6.26-2-xen-amd64 #1 SMP Wed Mar 10) on two identical production systems. This morning on one of the systems, xentop stopped displaying. Running xentop results in: unable to open xenstore : Connection refused Failed to initialize xenstat library xm list: Error: (9, ''Bad file descriptor'') xm dmseg: Error: Subcommand

- This minor patch implements the missing stub function security_label_to_details in the dummy module. This stub function is necessary to create domains with network interfaces for modules that do not implement the security_label_to_details function. Signed-off-by: George Coker <gscoker@alpha.ncsc.mil> _______________________________________________ Xen-devel mailing list

Hi Xen-users, I am trying to boot of my fist guest domain. The below attached message was thrown on the screen. I am not quite sure that the below information is sufficient to root cause the issue. Where do i look for additional logs to root cause the issue. Appreciate any info that you think might be useful. Thanks, Karthik xm create -c guest1.conf vmid=2 Using config file

withr:::set_makevars() can give that error if the makefile named by the 'old_path' argument (default "~/.R/Makevars) contains more than one definition of a variable of the form 'name=value'. You can see what file it is reading and its contents by using the trace() function: trace(withr:::set_makevars, quote({ cat(old_path, "\n"); writeLines(paste0(" ",

Greetings, As a Google Summer of Code student for the SYSLINUX project, I had the chance to learn many interesting things from hpa regarding the internals of SYSLINUX. So besides my main task of implementing ELF modules loading & linking, I decided to put down in the wiki all the information I found concerning SYSLINUX development. In this regard, I have created a special category on the