search for: domain_config

...:22:21 2012 +0000 @@ -72,4 +72,6 @@ external send_trigger : domid -> trigger external send_sysrq : domid -> char -> unit = "stub_xl_send_sysrq" external send_debug_keys : ctx -> string -> unit = "stub_xl_send_debug_keys" +external domain_create_new : ctx -> Domain_config.t -> domid = "stub_xl_domain_create_new" + let _ = Callback.register_exception "Xenlight.Error" (Error(Fail, "")) diff -r 41f0137955f4 -r 72376896ba08 tools/ocaml/libs/xl/xenlight.mli.in --- a/tools/ocaml/libs/xl/xenlight.mli.in Tue Nov 20 17:22:21 2012 +0000 +++ b...

...reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin, PA E-Mail:  aravindh.puthiyaparambil@unisys.com xenbox:~/xen/xen-unstable/extras/mini-os # xm create domain_config Using config file "domain_config". Error: <ProtocolError for /RPC2: -1 > Dmesg ----- xenbox kernel: python[12171] general protection rip:2b14fba3776e rsp:427ff7d0 error:0 Xend.log -------- [2006-05-16 13:30:55 xend.XendDomainInfo] DEBUG (XendDomainInfo:186) XendDomainInfo.create([...

Hey guys, having some trouble getting Mini-OS to start up. I have xen 3.1 installed and am running dom0 fine. I make the Mini-OS directory and then do the following: root@localhost mini-os]# xm create domain_config -c Using config file "./domain_config". Error: Kernel image does not exist: /home/mcleanap/l4/project/xen-3.0.4_1-src/extras/mini-os/mini-os.elf The file does exist, and with full read/write permissions (just in case) so I cannot see what the problem is :-( Any help on this would be grea...

Want to load a configuration from a yaml file ala config/database.yml. I am following http://blog.innovativethought.net/2009/01/02/making-configuration-files-with-yaml-revised/ but, I am getting uninitialized constant ActionView::CompiledTemplates::DOMAIN_CONFIG from rails. I''ve documented my code to make this simpler. I''m running Rails 3.0.7 I know isn''t the toughest question but, I would also like to know why isn''t that constant available in the views? Do I have to wrap that constant in a Ruby object of some sor...

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

...+++++++++++++ 4 files changed, 53 insertions(+), 9 deletions(-) diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c index ebf2ed7..ae0d668 100644 --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -619,6 +619,9 @@ static int do_domain_create(libxl__gc *gc, libxl_domain_config *d_config, if (dm_info->device_model_version == LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN) { libxl__qmp_initializations(ctx, domid); + if (dm_info->vncpasswd) { + libxl__qmp_vnc_password(gc, domid, dm_info->vncpasswd); + }...

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 ena...

...case LIBXL_DEVICE_USB_TYPE_HOSTDEV: + rc = libxl__qmp_usb_hostdev_remove(gc, domid, usbdev); + break; + default: + return ERROR_INVAL; + } + return rc; +} + + + int libxl__qmp_initializations(libxl__gc *gc, uint32_t domid, const libxl_domain_config *guest_config) { diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl index fcb1ecd..3c6a709 100644 --- a/tools/libxl/libxl_types.idl +++ b/tools/libxl/libxl_types.idl @@ -408,6 +408,28 @@ libxl_device_vtpm = Struct("device_vtpm", [ ("uuid", l...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before