search for: c_info

...libxl/libxl.c Tue Jan 11 15:30:48 2011 +0000 +++ b/tools/libxl/libxl.c Tue Jan 11 15:40:45 2011 +0000 @@ -1024,6 +1024,35 @@ int libxl_device_disk_local_detach(libxl } /******************************************************************************/ +int libxl_device_nic_init(libxl_device_nic *nic_info, int devnum) +{ + const uint8_t *r; + libxl_uuid uuid; + + libxl_uuid_generate(&uuid); + r = libxl_uuid_bytearray(&uuid); + memset(nic_info, ''\0'', sizeof(*nic_info)); + + nic_info->backend_domid = 0; + nic_info->domid = 0; + nic_info->devid...

...HD + | PHYSTYPE_AIO + | PHYSTYPE_FILE + | PHYSTYPE_PHY + +type disk_info = +{ + backend_domid : domid; + physpath : string; + phystype : disk_phystype; + virtpath : string; + unpluggable : bool; + readwrite : bool; + is_cdrom : bool; +} + +type nic_type = + | NICTYPE_IOEMU + | NICTYPE_VIF + +type nic_info = +{ + backend_domid : domid; + devid : int; + mtu : int; + model : string; + mac : int array; + bridge : string; + ifname : string; + script : string; + nictype : nic_type; +} + +type console_type = + | CONSOLETYPE_XENCONSOLED + | CONSOLETYPE_IOEMU + +type console_info = +{ + backend_domid : domid...

...eturn libxl__sprintf(gc, "%s-dm", guest_name); +} + void libxl__spawn_stub_dm(libxl__egc *egc, libxl__stub_dm_spawn_state *sdss) { STATE_AO_GC(sdss->dm.spawn.ao); @@ -733,7 +738,7 @@ void libxl__spawn_stub_dm(libxl__egc *eg libxl_domain_create_info_init(&dm_config->c_info); dm_config->c_info.type = LIBXL_DOMAIN_TYPE_PV; - dm_config->c_info.name = libxl__sprintf(gc, "%s-dm", + dm_config->c_info.name = libxl__stub_dm_name(gc, libxl__domid_to_name(gc, guest_domid)); dm_config->c_info.ssidref = g...

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

Anthony PERARD (3): libxl_qmp: Use GC instead of CTX as parameter for _initialize. Provide dm_vnc() as a in libxl helper. libxl: Set VNC password through QMP tools/libxl/libxl_create.c | 2 +- tools/libxl/libxl_dm.c | 32 ++++++++++++++---------- tools/libxl/libxl_internal.h | 7 ++++- tools/libxl/libxl_qmp.c | 55 ++++++++++++++++++++++++++++++----------- 4 files

...00:00:00 1970 +0000 +++ b/tools/ocaml/test/build_domain.ml Tue Nov 20 17:22:21 2012 +0000 @@ -0,0 +1,42 @@ +open Arg +open Printf +open Xentoollog +open Xenlight + +let _ = + let logger = Xentoollog.create_stdio_logger ~level:Xentoollog.Debug () in + let ctx = Xenlight.ctx_alloc logger in + let c_info = { + Xenlight.Domain_create_info.hap = None; + Xenlight.Domain_create_info.oos = None; + Xenlight.Domain_create_info.name = "Test; + } + and b_info = { + Xenlight.Domain_build_info.max_vcpus = 1; + Xenlight.Domain_build_info.avail_vcpus = [| |]; + Xenlight.Domain_build_inf...

..., "-xen-attach"); } + if (b_info->type == LIBXL_DOMAIN_TYPE_HVM && + libxl_defbool_val(b_info->u.hvm.xen_platform_pci)) { + flexarray_append(dm_args, "-device"); + flexarray_append(dm_args, "xen-platform"); + } + if (c_info->name) { flexarray_vappend(dm_args, "-name", c_info->name, NULL); } -- 1.7.10.4

..., LH --- /tmp/xen-init-name.orig 2016-03-14 00:31:40.812230921 +0100 +++ /usr/lib/xen-common/bin/xen-init-name 2016-03-14 00:31:51.776943095 +0100 @@ -39,7 +39,7 @@ class DataJSON(Data): def __init__(self, p): s = json.loads(p) - self.name = s['config']['c_info']['name'] + self.name = s['c_info']['name'] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-...

...=== +--- xen.orig/tools/libxl/xl_cmdimpl.c 2013-07-09 11:46:56.000000000 +0100 ++++ xen/tools/libxl/xl_cmdimpl.c 2013-08-16 14:47:31.040162084 +0100 +@@ -1591,7 +1591,7 @@ + char *corefile; + int rc; + +- if (asprintf(&corefile, "/var/xen/dump/%s", d_config->c_info.name) < 0) { ++ if (asprintf(&corefile, "/var/lib/xen/dump/%s", d_config->c_info.name) < 0) { + LOG("failed to construct core dump path"); + } else { + LOG("dumping core to %s", corefile); +Index: xen/tools/python/xen...

...=== +--- xen.orig/tools/libxl/xl_cmdimpl.c 2013-07-09 11:46:56.000000000 +0100 ++++ xen/tools/libxl/xl_cmdimpl.c 2013-08-16 14:47:31.040162084 +0100 +@@ -1591,7 +1591,7 @@ + char *corefile; + int rc; + +- if (asprintf(&corefile, "/var/xen/dump/%s", d_config->c_info.name) < 0) { ++ if (asprintf(&corefile, "/var/lib/xen/dump/%s", d_config->c_info.name) < 0) { + LOG("failed to construct core dump path"); + } else { + LOG("dumping core to %s", corefile); +Index: xen/tools/python/xen...

Hello, in the last days I switched from Xen 4.2.1 to Xen 4.2.2 (source from git repository tag 4.2.2) commit a125ec6a4a2f028f97f0bdd8946d347a36dbe76b Author: Jan Beulich <jbeulich@suse.com> Date: Tue Apr 23 18:42:55 2013 +0200 update Xen version to 4.2.2 My "base system" is a debian squeeze. For Xen I use the xl toolstack. Since updating to 4.2.2 the autosave and

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

..._Config *config; XLU_ConfigList *cpus, *vbds, *nics, *pcis, *cvfbs, *cpuids; + XLU_ConfigList *ioports, *irqs; + int num_ioports, num_irqs; int pci_power_mgmt = 0; int pci_msitranslate = 0; int pci_permissive = 0; - int e; + int i, e; libxl_domain_create_info *c_info = &d_config->c_info; libxl_domain_build_info *b_info = &d_config->b_info; @@ -919,6 +921,89 @@ static void parse_config_data(const char abort(); } + if (!xlu_cfg_get_list(config, "ioports", &ioports, &num_ioports, 0)) { + b_info->num...

...n Campbell <ian.campbell@citrix.com> diff -r 69dd2d8cfa88 -r d158e101baa1 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Fri Sep 10 13:56:10 2010 +0100 +++ b/tools/libxl/xl_cmdimpl.c Fri Sep 10 14:54:10 2010 +0100 @@ -274,7 +274,7 @@ static void init_build_info(libxl_domain if (c_info->hvm) { b_info->shadow_memkb = 0; /* Set later */ b_info->video_memkb = 8 * 1024; - b_info->kernel.path = "hvmloader"; + b_info->kernel.path = strdup("hvmloader"); b_info->hvm = 1; b_info->u.hvm.pae = 1;...

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

Hi again! More TPM + XEN stuff. have look at the following: ================= "xl list -l centos7.0" ============== [ { "domid": 31, "config": { "c_info": { "type": "hvm", "name": "centos7.0", "uuid": "feef6cac-8148-4040-a7cb-ad1f82d8d68a", "run_hotplug_scripts": "True" }, &quot...

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

...1592 if (child1) { /*it''s in the parent*/ 1593 printf("Daemon running with PID %d\n", child1); /**it''s in the child/ 1643 LOG("Waiting for domain %s (domid %d) to die [pid %ld]", 1644 d_config.c_info.name, domid, (long)getpid()); After input `xl create xp-101.hvm`, you got `Daemon running with PID 26622` following the command line in the screen; but the xl log file lies in /var/log/xen/xl-xp-101.log contains a line `Waiting for domain xp-101 (domid 1) to die [pid 26624]`. Why 26622 != 26624?...