search for: target_memkb

...<stefano.stabellini@eu.citrix.com> diff -r a69965e61ae9 tools/libxl/libxl.c --- a/tools/libxl/libxl.c Mon Jan 31 17:47:24 2011 +0000 +++ b/tools/libxl/libxl.c Tue Feb 01 16:34:43 2011 +0000 @@ -2059,9 +2059,12 @@ retry_transaction: goto out; } - if (relative) - new_target_memkb = current_target_memkb + target_memkb; - else + if (relative) { + if (target_memkb < 0 && abs(target_memkb) > current_target_memkb) + new_target_memkb = 0; + else + new_target_memkb = current_target_memkb + target_memkb; + } else n...

...fo ptr; + char *uuid; videoram_s = libxl_xs_read(ctx, XBT_NULL, libxl_sprintf(ctx, "%s/memory/videoram", dompath)); videoram = videoram_s ? atoi(videoram_s) : 0; libxl_xs_write(ctx, XBT_NULL, libxl_sprintf(ctx, "%s/memory/target", dompath), "%lu", target_memkb); + + rc = xc_domain_getinfolist(ctx->xch, domid, 1, &info); + if (rc != 1 || info.domain != domid) + return rc; + xcinfo2xlinfo(&info, &ptr); + uuid = libxl_uuid2string(ctx, ptr.uuid); + libxl_xs_write(ctx, XBT_NULL, libxl_sprintf(ctx, "/vm/%s/memory"...

...ed, 15 insertions(+), 11 deletions(-) diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c index e63c7bd..e706124 100644 --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -127,15 +127,6 @@ int libxl__domain_build_info_setdefault(libxl__gc *gc, b_info->target_memkb = b_info->max_memkb; libxl_defbool_setdefault(&b_info->localtime, false); - if (libxl_defbool_val(b_info->localtime)) { - time_t t; - struct tm *tm; - - t = time(NULL); - tm = localtime(&t); - - b_info->rtc_timeoffset += tm->tm_gmt...

...bxl__build_pre(libxl__gc *gc, uint libxl_domain_build_info *info, libxl__domain_build_state *state) { libxl_ctx *ctx = libxl__gc_owner(gc); + int tsc_mode; xc_domain_max_vcpus(ctx->xch, domid, info->max_vcpus); xc_domain_setmaxmem(ctx->xch, domid, info->target_memkb + LIBXL_MAXMEM_CONSTANT); if (info->type == LIBXL_DOMAIN_TYPE_PV) xc_domain_set_memmap_limit(ctx->xch, domid, (info->max_memkb + info->u.pv.slack_memkb)); - xc_domain_set_tsc_info(ctx->xch, domid, info->tsc_mode, 0, 0, 0); + switch (info->ts...

...virtualised features (such as devices) diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c index 8417661..d39ecbe 100644 --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -124,6 +124,17 @@ int libxl__domain_build_info_setdefault(libxl__gc *gc, if (b_info->target_memkb == LIBXL_MEMKB_DEFAULT) b_info->target_memkb = b_info->max_memkb; + libxl_defbool_setdefault(&b_info->localtime, false); + if (libxl_defbool_val(b_info->localtime)) { + time_t t; + struct tm *tm; + + t = time(NULL); + tm = localtime(&...

...nfo->ssidref = 0; + c_info->poolid = 0; +} + +void libxl_init_build_info(libxl_domain_build_info *b_info, libxl_domain_create_info *c_info) +{ + memset(b_info, ''\0'', sizeof(*b_info)); + b_info->max_vcpus = 1; + b_info->max_memkb = 32 * 1024; + b_info->target_memkb = b_info->max_memkb; + b_info->disable_migrate = 0; + b_info->cpuid = NULL; + b_info->shadow_memkb = 0; + if (c_info->hvm) { + b_info->video_memkb = 8 * 1024; + b_info->kernel.path = strdup("hvmloader"); + b_info->hvm = 1; +...

...char b_info->cur_vcpus = (1 << l) - 1; } + if (!xlu_cfg_get_long (config, "maxvcpus", &l)) + b_info->max_vcpus = l; + if (!xlu_cfg_get_long (config, "memory", &l)) { b_info->max_memkb = l * 1024; b_info->target_memkb = b_info->max_memkb; _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...1 || info.domain != domid) goto out; xcinfo2xlinfo(&info, &ptr); - uuid = libxl_uuid2string(ctx, ptr.uuid); + uuid = libxl_uuid2string(&gc, ptr.uuid); libxl_xs_write(&gc, XBT_NULL, libxl_sprintf(&gc, "/vm/%s/memory", uuid), "%"PRIu32, target_memkb / 1024); if (enforce || !domid) diff -r dc335ebde3b5 tools/libxl/libxl.h --- a/tools/libxl/libxl.h Thu Aug 12 18:03:23 2010 +0100 +++ b/tools/libxl/libxl.h Fri Aug 13 15:32:31 2010 +0100 @@ -362,7 +362,6 @@ int libxl_run_bootloader(libxl_ctx *ctx, libxl_device_disk...

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

..."b_info": { "max_vcpus": 4, "avail_vcpus": [ 0, 1, 2, 3 ], "max_memkb": 4194304, "target_memkb": 4194304, "video_memkb": 8192, "shadow_memkb": 36864, "localtime": "False", "sched_params": { }, "claim_mode": "True",...

...ight.Domain_build_info.avail_vcpus = [| |]; + Xenlight.Domain_build_info.cpumap = [| |]; + Xenlight.Domain_build_info.numa_placement = None; + Xenlight.Domain_build_info.tsc_mode = Xenlight.TSC_MODE_DEFAULT; + Xenlight.Domain_build_info.max_memkb = 1024L; + Xenlight.Domain_build_info.target_memkb = 1024L; + Xenlight.Domain_build_info.video_memkb = 0L; + Xenlight.Domain_build_info.shadow_memkb = 0L; + Xenlight.Domain_build_info.rtc_timeoffset = 0L; + } in + let d_info = { + Xenlight.Domain_config.b_info = b_info; + Xenlight.Domain_config.c_info = c_info; + Xenlight.Domain...

...rintf(&gc, "%s-dm", _libxl_domid_to_name(&gc, info->domid)); for (i = 0; i < 16; i++) c_info.uuid[i] = info->uuid[i]; @@ -1387,28 +1465,31 @@ static int libxl_create_stubdom(libxl_ct b_info.max_vcpus = 1; b_info.max_memkb = 32 * 1024; b_info.target_memkb = b_info.max_memkb; - b_info.kernel.path = libxl_abs_path(ctx, "ioemu-stubdom.gz", libxl_xenfirmwaredir_path()); - b_info.u.pv.cmdline = libxl_sprintf(ctx, " -d %d", info->domid); + b_info.kernel.path = libxl_abs_path(&gc, "ioemu-stubdom.gz", libxl_xenf...

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

...apic : bool; + acpi : bool; + nx : bool; + viridian : bool; + timeoffset : string; +} + +type build_spec = BuildHVM of build_hvm_info | BuildPV of build_pv_info + +type build_info = +{ + timer_mode : int; + hpet : int; + vpt_align : int; + max_vcpus : int; + cur_vcpus : int; + max_memkb : int64; + target_memkb : int64; + video_memkb : int64; + shadow_memkb : int64; + kernel : string; + priv: build_spec; +} + +type build_state = +{ + store_port : int; + store_mfn : int64; + console_port : int; + console_mfn : int64; +} + +type domid = int + +type disk_phystype = + | PHYSTYPE_QCOW + | PHYSTYPE_QCOW2 + | PH...

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

...6cd -r cdb947baea10 tools/libxl/libxl_dm.c --- a/tools/libxl/libxl_dm.c Thu May 17 16:39:51 2012 +0100 +++ b/tools/libxl/libxl_dm.c Thu May 17 17:51:32 2012 +0100 @@ -715,10 +715,6 @@ void libxl__spawn_stub_dm(libxl__egc *eg dm_config->b_info.max_memkb = 32 * 1024; dm_config->b_info.target_memkb = dm_config->b_info.max_memkb; - dm_config->b_info.u.pv.kernel.path = libxl__abs_path(gc, "ioemu-stubdom.gz", - libxl__xenfirmwaredir_path()); - dm_config->b_info.u.pv.cmdline = libxl__sprintf(gc, " -d %d", guest_domi...

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

...t;uuid":"339a8082-6104-4342-96b5-b7f6000e4972","xsdata":{},"platformdata":{},"poolid":0},"b_info":{"max_vcpus":1,"cur_vcpus":1,"cpumap":[],"tsc_mode":"default","max_memkb":131072,"target_memkb":131072,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"<default>","disable_migrate":"<default>","cpuid":[],"device_model_version":null,"device_model_stubdomain"...

Hi, Here are three small but important libxl/xl memory management patches: - libxl: xl mem-max et consortes must update static-max in xenstore too, - xl: Allow user to configure xl mem-set behavior, - xl: Improve xl documentation in regards to guest memory management. Daniel