similar to: Bug#682979: sample logfile

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

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

Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is

The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed

Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package

Hello, It is strange. There is no output and the imported VM (template) is not visible with "xe vm-list" or "xe template-list". The file is an exported template. What do I miss? Thank you in advance for any hints. Regards, mark -- ms@it-infrastrukturen.org # --- [root@xs6db01 ~]# xe vm-import filename=Solaris10-extended-HVM-template [root@xs6db01 ~]# [root@xs6db01 ~]#

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

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

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

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

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

running xen cloud on my ubuntu12.04 box connecting with xencenter - i can create delete and monitor VM''s when i connect to the console i can see the console output but none of my keypresses or mouse clicks are registered in the VM everything i hit a key i get this in my xcp-xapi log [20120721T17:17:20.330Z|debug|xen|509 INET 127.0.0.1:80|Connection to VM console R:73c96b23cdd8|console]

I'm trying add drivers as detailed in chapter 18 (Classical Printing Support) in the Samba-HOWTO-Collection HEAD/3.0. The following command returns the "Printer Driver __________ Successfully Installed" message, but none of the dependent files get moved or associated with the Driver. rpcclient -U PRINT-ADMIN-USER -c 'adddriver "Windows NT x86" "RICOH Aficio 700

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

Hi. Let me know if I should be reporting this elsewhere for reasons that I''m about to detail below. I''m fiddling with Xen 4.1.1 on Debian squeeze running kernel 3.0. I was really exciting about the Kronos project bringing the API to Debian/Ubuntu so I thought I''d give it a try. I''m find myself facing a number of challenges working with a local lvm based SR.

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]

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

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

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME