similar to: XEN API SDK

Hullo Everybody I have taken the steps below and I failed to get a device similar to /dev/xvda in DOM 0 where am I getting it wrong Create VDI, *[root@virtualintranet /]# xe vdi-create sm-config:type=raw sr-uuid=b303be09-6a32-8d94-d248-7551860fbc3f name-label="Centos-Vdi" virtual-size=20GiB type=user* eefa9066-a991-44c3-b537-d20d65f3d10c create VBD *[root@virtualintranet /]# xe

During some discussions and handwaving, including discussions with some experts on the Xenserver/XCP storage architecture, we came up with what we think might be a plausible proposal for an architecture for communication between toolstack and driver domain, for storage at least. I offered to write it up. The abstract proposal is as I understand the consensus from our conversation. The concrete

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

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

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

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,

hi i have installed xcp and installed xen api sdk using the xcp cd and all the installation is working well , when i have entered into the xen api sdk in the console its asking me the login and the password ... But during the installation i have not given any login and password can u tell me the login and password i need to do program for vm migration and the procedure , i.e. how to write the

hi i need to install the api sdk for xen cloud platform can u pls tell me how to install the api sdk and, the there procedure how to develop my own program using python , can u pls tell me the steps for the sample progam -- R.G.BABUKARTHIK _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

I've had another attempt at installing Wheezy 64 bit from a template as PV. I attach my full script below. I've made much more progress this time, but there are still outstanding issues: - neither "xe console" or VNC seems to allow ALT-F[2-6] keystrokes, so I can't get other virtual terminals and therefore can't obtain any useful log/status messages. This issue alone

I''m rather new to working with puppet so forgive me it these are solved problems. I''ve read through some documentation, but was not able to find the full set of information to answer all my questions. I''m being tasked with finding/configuring/developing an enterprise resource configuration tool. We have several on the table but puppet/chef are the only

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

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

I'm using the the Microsoft Real-Time Communications Client API SDK using Visual Studio 6 and . NET 2003 SE to make SIP calls. Using the examples provided I can make unregistered SIP calls fine, however I am having trouble registering with Asterisk. I have to produce an XML Profile to use when registering with a registrar. The one I use is... <provision

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

How do I resolve this issue? Please help me. ################################################ [root@xenhost2 ~]# xe vm-list uuid=0a0efde9-a92f-3619-478c-64edd8b0adf8 uuid ( RO) : 0a0efde9-a92f-3619-478c-64edd8b0adf8 name-label ( RW): rhel52 power-state ( RO): halted ################################################ [root@xenhost2 ~]# xe vm-start

Hi, I double checked the configuration with xm and the "w!" option seems to be configured :-( I also upgraded to build 123, but also no change in behaviour. Thus is this a RAC 11.2 problem or is there a general problem using zvols as as shared disks for xVM domains ? (device (vbd (protocol x86_64-abi) (uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)

I am running Xen 3.3.0 and am trying to run a XenEnterprise image. The image has a hda directory with files called chunk-000000000.gz - chunk-000000042.gz and a filed called ova.xml with the following: <appliance version="0.1"> <vm name="VM"> <label> Manager </label> <shortdesc> </shortdesc> <config

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under