Displaying 20 results from an estimated 10000 matches similar to: "changes in libxc"
2012 Jan 02
1
回复: [help] Who's the author of libxc? I don't know howto start with it
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
2007 Feb 26
2
[PATCH 0 of 2] Parse image elfnotes, write them to xenstore, save and load via image sxpr
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
2005 Oct 10
13
[PATCH] 0/2 VCPU creation and allocation
I''ve put together two patches. The first introduces a new dom0_op,
set_max_vcpus, which with an associated variable and a check in the
VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP,
VCPUOP_create, which handles all of the vcpu creation tasks and leaves
initialization and unpausing to VCPUOP_initialize. The separation
allows for build-time allocation of vcpus which
2005 Jun 23
4
debugging libxc / builders
Hi,
I''m playing with the builders in libxc. I am having trouble
debugging the thing. I was wondering what options I have.
- When I run ''xm create'', what process calls down to the
xc_builder stuff? Can I attach to it with gdb?
- Is there any way to spit out debug output (printf?)? Where
would it go?
- If I make changes and do a make install in
2006 Aug 30
3
arch-specific xc.c code?
Hi Ewan/Alistair, I have a patch that looks like this:
diff -r a39ad4c78850 tools/libxc/xenctrl.h
--- a/tools/libxc/xenctrl.h Wed Aug 30 13:51:12 2006 +0100
+++ b/tools/libxc/xenctrl.h Wed Aug 30 15:11:20 2006 -0500
@@ -416,6 +416,10 @@ int xc_domain_memory_populate_physmap(in
unsigned int address_bits,
xen_pfn_t
2005 Aug 22
2
[PATCH] Rename libxc => libxenctl
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
2007 Jun 27
2
xen not working: xmlrpc.sock doesn''t exist
Hi all,
I have some serious problems making Xen run. I have spent a couple of days
looking in Google and trying a lot of different things, but none of them has
worked. I hope you can help me...
First of all: xen was running smoothly on my machine, but suddenly (I think
I haven''t changed any configuration) it doesn''t work anymore.
I am using a Debian 4.0 with Xen 3.
When
2013 May 21
12
[PATCH] fix XSA-46 regression with xend/xm
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
2006 Dec 07
6
problem restarting xenstored
As any other daemon, I''d assume it should be possible to restart xenstored (i.e.
if it crashed or if, during development, a fix was made to it that needs to be
tested). However, as I learned after over a day of digging, things don''t work
anymore after doing so: Since the watches are transient, they''re lost with the
daemon going away.
Right now I specifically need this in
2013 Jan 10
10
[PATCH v2 1/2] xenconsoled: use grant references instead of map_foreign_range
Grant references for the xenstore and xenconsole shared pages exist, but
currently only xenstore uses these references. Change the xenconsole
daemon to prefer using the grant reference over map_foreign_range when
mapping the shared console ring.
This allows xenconsoled to be run in a domain other than dom0 if set up
correctly - for libxl, the xenstore path /tool/xenconsoled/domid
specifies the
2008 Aug 27
2
[PATCH] libxc: Use vcpu_guest_context_any_t instead of two pages
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
2006 Aug 17
4
[PATCH]configuration files(sched-credit)
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
2006 Aug 01
18
[Patch] Enable "sysrq c" handler for domU coredump
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).
2010 Jan 12
53
Xen 4.0.0 first release candidate
Folks,
The first release candidate for Xen 4.0.0 has been tagged and published.
You can grab it from here:
http://xenbits.xensource.com/xen-unstable.hg (tagged ''4.0.0-rc1'')
Please test it!
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2006 Sep 29
4
[PATCH 4/6] xen: export NUMA topology in physinfo hcall
This patch modifies the physinfo hcall to export NUMA CPU and Memory
topology information. The new physinfo hcall is integrated into libxc
and xend (xm info specifically). Included in this patch is a minor
tweak to xm-test''s xm info testcase. The new fields in xm info are:
nr_nodes : 4
mem_chunks : node0:0x0000000000000000-0x0000000190000000
2013 May 31
3
Bug#710650: xen-api: FTBFS: gcc: error: /home/blank/debian/xen/releases/xen/xen-4.2.1/debian/build/build-utils_amd64/tools/ocaml/libs/xc/../../../../tools/libxc/libxenctrl.so: No such file or directory- build ocaml/xapi rrddump.opt
Source: xen-api
Version: 1.3.2-15
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130529 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/?PKGBUILDDIR?'
> omake phase1
> omake: Symbol `FamErrlist' has different size
2005 Sep 30
14
pdb missing files?
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.
2005 Jul 03
11
[PATCH] xm info
This patch makes "xm info" show information on xen version, compile
info, number of socket/core, etc...
In order to do that, it extends physinfo hypercall to return number of
socket, adds few functions to libxc and extends python wrapper
correspondingly.
Here is the output of new "xm info":
--
system : Linux
host : ubuntu
xen_release
2006 May 16
7
Unable to bring up Mini-OS on x86_64
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
2008 Sep 30
31
[PATCH] [Xend] Move some backend configuration
This patch moves some dom0 variables and backend device
configuration from frontend directories to
/local/domain/<backdomid>/backend or /vm.
Also,
- the first console is created as a xend device and moves
from console/0 to device/console/0
- /vm_path/<domid> is introduced, referencing the /vm path
- /vm_path/device/backend holds the backend device location,
rather than storing it