similar to: XCP: iscsi redundancy

Good day. Which ports are used by xapi? I suddenly found it using tcp/13993 and I''m slightly concern about possible collision between xapi and my own application, running on dom0 on XCP... Thanks. --- wBR, George. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Good day. I found that XCP ignores VCPU-params (weight and cap) after VM live migration, as well, as those parameters ignored if changed on running VM. May I as someone with xcp cloud nearly check this bug? Thank you. -- wBR,George. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

Hi all, we have followed the very good HOWTO by http://wherethebitsroam.com/blogs/jeffw/drbd-xcp-05 and set up DRBD on XCP 1.1 in primary/primary mode. It works fine, but I am wondering how to squeeze more performance out of the system (we currently use a crossover GB Ethernet connection). When writing a 1 GB file on a guest I get write performance of about 5MB/s (idle). We have disabled all

Hi, I'm trying to build a XCP environment based on wheezy and iSCSI storage. When I try to add a iSCSI SR I get the following error: The SR could not be connected because the driver was not recognised. driver: lvmoiscsi As I couldn't find the driver in /usr/lib/xcp/sm I took a look into the package itself and saw that the driver exists in drivers, but is not listed in the Makefile. Is

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

I just ordered quite a few servers, and, without verifying ahead of time, ordered without hard drives planning to boot over iSCSI using the built-in network cards (NOT an iSCSI HBA). I''m wondering if anyone has tried (and hopefully succeeded) installing XCP to an iSCSI volume using a network card with iSCSI boot support and the software iSCSI initiator in XCP. Obviously I can order HDs

Good day. I''m pretty curious, how they work with netinst (debian, suse, ubuntu, centos)... As I understand, at first start they downloads xen-aware kernel and netinst initrd from repository (with one user must point with other-config:install-repository)... But how they do it? I means, this some kind of script, some kind of variables... Really, I''d like to do few more

Hi all, I have experience with XEN, but I just start making tests with XCP. My XEN installation uses iscsi disks in raw mode (i mean using phy:/... for vm definitions where the block device is an iscsi lun managed by the dom0). I''m reading citrix manuals and googling a lot but still i''m not sure about the way to make such a configuration. Any of you has a tutorial for that

Good day. xe-guest-tools for debian adding a repository to aptitude:/etc/apt/sources.list.d/citrix.list deb http://updates.vmd.citrix.com/XCP/0.4.901/debian/ lenny main deb-src http://updates.vmd.citrix.com/XCP/0.4.901/debian/ lenny main But this repository does not work: Err http://updates.vmd.citrix.com lenny/main Packages 404 Not Found Err http://updates.vmd.citrix.com lenny/main

Hello, We''ve been using Xen on several servers with direct-attached storage for a number of years. Now we''re looking to buy more Xen servers and re-purpose two of the older ones as SANs to hold the domU filesystems, in order to achieve redundancy and live migration ability. I''m looking for comments on our proposed design. SAN 1 - existing server w/ 4 GB, 2x

Hi, I've been trying to fix several bugs in XCP, before the Debian 7 release. It's not bug free yet, but it's going into that direction. I would need some help to fix the remaining! 1/ The new 1.3.2-12 release The Debian release team has already accepted an unblock for this new version that I uploaded in Debian SID. Here's the debian/changelog: * Fixes bashism in

Hi All, I apologize in advance if this strays too far from the etiquette on the Xen userlist, however the amount of help, brainpower and experience I''ve received from this list with Xen and "peripheral" related issues (i.e. DRBD) have been worth more than it''s weight on gold and I''m hoping someone will be kind enough to give me a "best practices"

Good day. Found strange behavior in PV-domains. Application like tcpdump or iftop require promiscuous mode for interface. And this feature is disabled by default, as I understand. message from iftop: pcap_open_live(eth0): eth0: You don''t have permission to capture on that device (socket: Address family not supported by protocol) As I understand promiscuous:on in other-config for vif

Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host:

Dear All, I''m totally new to DRBD + XEN over iSCSI but I need to configure this scenario in order to buy the right hardware. Our department will provide us with an iSCSI target which will be replicated in its own to a secondary iSCSI SAN (probably they will use DRBD). This target will be used, in our ideas, to replicate our own iSCSI san, that we are going to buy. We will probably

Package: xcp-xe Version: 1.3.2-11 Severity: minor xe did not prove help in autocomplete for xe console command. Steps to reproduce: xe console[tab] Output (help) does not contains xe console command. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (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

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