similar to: debugging libxc / builders

Hi, I am having problems getting a domain to start using "xm create". I am running unstable, I pulled today and rebuilt, installed and rebooted. (I also have a few loader patches, posted earlier). I am able to start a domain using VM Tools and the following script: dom=`vm-create` vm-memory -m $dom 64m vm-memory -i $dom 64m vm-build.linux $dom /root/9hello noargs

Hi, I''m trying to test some changes of mine to libxc and python/xc.c, does it requires a boot any time I''m trying to test them? What are your development practices? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Thanks. I have already previewed the xenctrl.h. The following is what I understand: libxc is compiled to a file name after 'xc**' endding with '.so', xend communicates with domain0 through xc and domain0 communicates with hypervisor through privcmd. What's the privcmd? ------------------ 原始邮件 ------------------ 发件人: "Wei

The hypervisor side changes for XSA-46 require the tool stack to now always map the guest pIRQ before granting access permission to the underlying host IRQ (GSI). This in particular requires that pciif.py no longer can skip this step (assuming qemu would do it) for HVM guests. This in turn exposes, however, an inconsistency between xend and qemu: The former wants to always establish 1:1 mappings

Doing some janitorial (you cleaning the flooded toilets and such) work today. I have come across this line of code that really I''m not sure what the intent was..in xen/include/sched.h #define hypercall_preempt_check() (unlikely( \ softirq_pending(smp_processor_id()) | \ (!!current->vcpu_info->evtchn_upcall_pending & \

I''m breaking the tidying up into parts. The first is renaming libxc => libxenctl. I''d like to rename tools/libxc to tools/libxenctl but I thought it might be worth waiting until "flag day" so that we can avoid losing revision history. Does that seem reasonable? Rename libxc to libxenctl, xc.h to xenctl.h, and install xenctl.h to /usr/include/xen/xenctl.h

libxc: Use vcpu_guest_context_any_t instead of two pages Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 14a9a1629590 tools/libxc/xc_dom_boot.c --- a/tools/libxc/xc_dom_boot.c wed aug 27 10:26:50 2008 +0100 +++ b/tools/libxc/xc_dom_boot.c wed aug 27 12:07:28 2008 +0100 @@ -187,7 +187,7 @@ int xc_dom_boot_image(struct xc_dom_imag int xc_dom_boot_image(struct

xc_dom_alloc_segment requires start address to be page align. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index ffe575b..366061d 100644 --- a/tools/libxc/xc_dom_arm.c +++ b/tools/libxc/xc_dom_arm.c @@ -290,6 +290,8 @@ int

This is a patch to forward-port a Xend behaviour. Xend writes IO ABI used for all frontends. Blkfront before 2.6.26 relies on this behaviour otherwise guest cannot boot when running in 32-on-64 mode. Blkfront after 2.6.26 writes that node itself, in which case it''s just an overwrite to an existing node which should be OK. In fact Xend writes the ABI for all frontends including console

Hi Mukesh, I was auditing uses of set_xen_guest_handle for correctness when I noticed that gdbsx (specifically tools/debugger/gdbsx/xg/xg_main.c) defines its own _domctl_hcall and associated helpers instead of using libxc. Is there any particular reason for that? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, libxc contains the following function which is used when uncompressing zipped kernel images: /* ------------------------------------------------------------------------ */ /* read files, copy memory blocks, with transparent gunzip */ size_t xc_dom_check_gzip(void *blob, size_t ziplen) { unsigned char *gzlen; size_t unziplen; if ( strncmp(blob,

Here are two patches that let xm create, save and restore extract and preserve elfnotes read by the domain builder. This is handy for a few things. In particular, I''d like it so that xm can decide whether or not guest domains support fast resume (if save fails, or for checkpointing). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

Hi, the attached patch makes Xen tracing work again, after the introduction of the hypercall buffers broke it. Just a missing line. Thanks to Uwe Dannowski for reporting this. Signed-off-by: Andre Przywara <andre.przywara@amd.com> Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448-3567-12

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings.

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu weight value -sets the cpu time ratio to be

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).

Hi! There''s a include path mistake when trying to build tools/libxc on OpenBSD: gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -D__XEN_TOOLS__ -Werror -fno-strict-aliasing -I. -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c In file included from xc_private.h:18, from xg_private.h:16,