similar to: XE VM install

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to XAPI calls being sent from a CloudStack management server. In the past, a simple xe-toolstack-restart would do the trick but the script timed out while restarting the XAPI daemon. I found the process and first tried to use a simple kill command but the process was in a "defunct" state. I tried a kill -9 but no joy.

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Good day. XCP 0.5 xe host-evacuate uuid=f9458b0b-5e35-4ee0-adcf-c8945a37868c You attempted an operation on a VM which requires a more recent version of the PV drivers. Please upgrade your PV drivers. vm: a84aaf23-8afe-2ccc-0299-83b9dfd08c35 But at really vm uuid with bad PV-drivers is 42e397c7-3d76-02c0-a1f9-c78d79cac6c6 and no uuid a84aaf23... present in pool. I think, it is an error in

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

i am trying to add auto migration feature in XEN. so is anyone has worked related to migration part. i need help regarding files related to migration. -- Regards Gautam _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

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-11 Severity: normal xe host-set-hostname-live host-uuid=68878163-7c93-17af-7911-5a2726fefc66 host-name=xapi-xh3 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Subprocess exitted with unexpected code 2; stdout = [ ]; stderr = [ sed: can't read

I''m still running XCP 0.5 on two servers. I am trying to make a few 10Gig Slackware64 13.1 servers (using the Windows 2003 server template). However, every time I try to start the guests in OpenXenManager, they die with something like: Async VM.start Slack64 13.1 #3[''NO_HOSTS_AVAILABLE''] I tried starting the hosts from the xsconsole and got the same results. I

Hi list, I have 3 Citrix Xenserver 5.6  and currently building a a VM backup server. I took the xe client on one of the server and installed it on the backup server (gentoo based) installed the stunnel package to make XE work. now when running, I get this error message : [server ­~ #] ./xe help -debug -s 192.168.111.17 -u user -pw pass Connecting via stunnel to [192.168.111.17] port [443]

Hi, this is the second time I step. After that I filled the dom0 disk, and freed space, xapi stopped working, no xe command works, I can not restart xapi (for the same problem). The first one I could fix it then restart the server, I can not because I have a vm in production. Any ideas on this? Saludos -- nycko _______________________________________________ Xen-users mailing list

Xen Community, I have a team of people frantically creating manpages for the xe command and all of it''s 361 subcommands. The initial source documentation is in asciidoc but also saved as Docbook. From docbook we transform to epub, html, manpage and pdf. This is currently being hosted in a subversion server at a Seattle area college and we''d like to move it to the xen-org

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > "Daniel P. Berrange" <berrange@redhat.com> a écrit : >> If you have new enough libvirt and Xen >= 4.2 then libvirt will >> automatically >> use the libxl APIs instead of XenD. I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the

Package: xcp-xapi Version: 1.3-15 Severity: normal My packages were initially installed from the deb repository at download.xensource.org. Eventually, I upgraded them to the debian repository ones. Right now, xcp-xapi fails to start with the following messages. lnx200-39:~# /etc/init.d/xcp-xapi start Error: Connection refused (calling connect ) lnx200-39:~# -- System Information: Debian

Hi, I''ve trying booting Xen Hypervisor PV with a centos5 template using kernel and initrd from mirror.centos.org/centos/5/os/i386. When i start PV this go to installation mode. However this should boot with template. Please help in this regard what Am i doing wrong. -- Best Regards Asim _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote: > Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > > >According to [1] it seems that libvirt is using Xend daemon to communicate. > > After reading more documentation it seems that Xend is mandatory. As > everything is not up to date I'd like to know if it is still the > case or

Hello Everyone, I am new with XCP. I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter and command console. Each host has two NICs, one (xenbr0) connected to a physical switch for Internet (said sw1), the other (xenbr3) connected to a physical switch for internal network (said sw2). I am trying to setup VMs and VLANs on xenbr3. I created a virtual bridge by