similar to: XCP: sr drivers and multipath.conf

hi, i installed xcp build20719. it seems that it failed to configure the gateway address. 1. i told the installer my gateway address. 2. on xvconsole, "Configure Management Interface" shows the correct gateway address. "Ping gateway address" works. 3. however, the address doesn''t seem to be told to the kernel. route(8) doesn''t show the default

Dear list, We observed the following issue in conjunction w/ XCP 1.1 which is a _severe_ problem. Our environment: - Two XCP 1.1 hosts in the same resource pool - Shared LVM based storage repository based on DRBD - VMs running on both systems stored on the shared SR If suddenly one host dies unexpectedly (e.g. hardware defect, power issue) the metadata still assumes the VMs that were running on

Hello I have a problem with VDI already attached RW in the "adding tag" in blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR. Is there any solution to this problem? /var/log/SMlog: [32484] 2013-01-17 14:59:44.200883 vdi_activate {''sr_uuid'': ''e33281eb-ba4c-3829-9b61-7c64764dff9c'', ''subtask_of'':

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

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

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

Hello, I hope to be in the right list. my question is the following. I can''t seem to get multipathing configure on XCP 1.6. In XenCenter I was able to enable "Multipath" however, in the LUN under general tab I see " multipath 1 of 1 active", the the CLI I do the following command xe --m node session it list only one session. Can someone help me please? Thanks in

hi I am having several pools of xcp with NFS shared storage as default SR on each pool and i want to do following in this arrangement -I want to share vdis among all pools, i.e. for example if I want to detach a vdi from a vm in pool-1 to a vm in pool-2. so is this possible to do so? vdi export is one of the solution but i want to do it seamlessly just like it happens within the same pool or

Hi all, I`m evaluating methods for nightly "snapshot" a physical win2003 to xcp vm. I know it would be a lot easier and reliable just to to one convert one time and start to generate real vm snapshots, but at this time I cannot use this method. I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big deal of using this method is that xenconvert does not send

The reason for the behaviour observed below turned out to be that the device entry in /etc/multipath.conf was inadvertently appended *after* the devices section , rather than inside it - so that we had #devices { # device { # blah blah # } (file has a bunch of defaults commented out) # etc #} # # device { our settings } *rather than*

Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being

hi all We have a rh linux server connected to two HP SAN controllers, one an HSV200 (on the way out), the other an HSV400 (on the way in). (Via a Qlogic HBA). /etc/multipath.conf contains this : device { vendor "(COMPAQ|HP)" product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0" getuid_callout "/sbin/scsi_id -g -u -s /block/%n"

Good day. I was tried to find difference between types of VDI in XCP, but found no information. Was is difference between System and User types? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

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

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,

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, attached I have some patches which add support for iSCSI LVMoISCSI to the xcp-storage-managers package. The patches are based on the Debian git repository. I have tested my changes and everything seems to work fine. The tests are done on a three node XCP pool with multipath. I haven't tested the changes without multipath. Maybe someone could take a look on the patches and give me some