similar to: Xenstore data not getting updated in running VM

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

Package: xcp-squeezed Version: 1.3.2-11 Followup-For: Bug #682202 ?I found race condtion between xcp-sqeezed and /etc/init.d/xen scripts. If sleep 10 added to xcp-sqeezed host (xcp-sqeezed and xapi) initialize normally, and if not with some probability sqeezed/xapi failed to start with message: Oct 9 16:45:57 xenhost-1 xapi: [ warn|xenhost-1|0 thread_zero|server_init D:1691a70e8b4a|startup]

Hey! I am following the steps at http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM. I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box has 12GB of physical memory and runs Ubuntu 13.04. When I do "xe vm-start", I get the following: The server failed to handle

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

Hi all: I am wondering how to get current VM IP address in XenStore, does it contains such information?? Thanks _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

I''m looking for what I need to write to xenstore from a VM to say whether or not it supports migration and/or suspension. On older versions of NetBSD, suspend/migration isn''t supported and on newer versions it still has issues. Therefore I want to let the XenServer toolstack, etc. not offer the option to the end user. -- Stephen

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

At 09:49 +0100 on 08 May (1336470591), Tim Deegan wrote: > Ccing xen-devel. Actually this time. > At 11:29 -0700 on 07 May (1336390171), Christian Limpach wrote: > > > The current version of Xen allocates the shared page directly > > > in vm memory with other pages (like XenStore page) called > > > special pages. I just begin to hack Xen, so I used the same >

On 09/06/2013 02:42 PM, St?phane Glondu wrote: > Le 05/09/2013 23:18, Julien Cristau a ?crit : >> tracker adjusted. xen-api is currently broken though, so you'll need to >> get that fixed before starting. > > I've just fixed a blocking bug (#713349) which was due to the renaming > of an OCaml library (type-conv -> type_conv). Hi, I had a patch from upstream

Signed-off-by: Matthew Daley <mattjd@gmail.com> --- tools/xenstore/xenstore_client.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/tools/xenstore/xenstore_client.c b/tools/xenstore/xenstore_client.c index 3ac214b..996ee64 100644 --- a/tools/xenstore/xenstore_client.c +++ b/tools/xenstore/xenstore_client.c @@ -134,8 +134,13 @@ static void do_ls(struct

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Hello, I''ve modified tools/xenstore/xenstore_client.c to include a new utility, xenstore-chmod. This utility permits developers and administrators to manually change the permissions on arbitrary locations in XenStore from the command line. This is often helpful if you''re trying to debug an application that relies on XenStore and is encountering difficulties with permissions.

Hi there, I am trying to set up XCP on Ubuntu 12.04. I went through the procedure given in the README file of the xcp-xapi package and reached the point where the hypervisor seems to be running fine. I set up a VM using the Debian Squeeze (64bit) template and started it, giving a Debian mirror URL as install-repository. Running "xe vm-list" reports that the machine is running, but when

tail /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vbd/6/768/node /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected xenstore-read: couldn't read path backend/vbd/6/5632/node xenstore-read: couldn't read path backend/vbd/6/768/node

Hi All , I am using xen 3.2.0 which i have built form source ,I could initially boot Dom 0 and some DomUs. But today when i tried to boot a DomU with birdge enabled it didnt work giving an error .... Error: Device 0 (vif) could not be connected. Hotplug scripts not working. After that I checked my var/log/messages and It gave lots of xenstore-write