similar to: [XCP] promiscuous mode for vif

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-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

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

Hi, I thought I'd query this here before opening a bug I installed XCP wheezy and imported a couple of my domU instances I chose to use Open vSwitch (ovs) networking mode I notice that each vif is created (e.g. vif1.0, vif2.0) when the domU boots. However, they are not bridged. As a hack, I just do brctl addif xenbr0 vif1.0 and then my domU is reachable. But I realise I should not

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

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:

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

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.2-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request,

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: xen-api Severity: wishlist Tags: patch l10n Hello, Attached is the Dutch translation of the xen-api debconf templates. Please include it in your next upload. Regards, -- Jeroen Schot -------------- next part -------------- # Dutch translation of xen-api debconf templates. # Copyright (C) 2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the

Good day. Is XCP supports any way to mirror network storages (iscsi, f.e.)? As I understand, XCP does not support DRBD yet, so, which other ways are? --- wBR, George. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

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: xen-api Version: 1.3.2-3 Severity: wishlist Tags: l10n patch Greetings, -- Camale?n -------------- next part -------------- # xen-api po-debconf translation to Spanish # Copyright (C) 2010 Software in the Public Interest # This file is distributed under the same license as the xen-api package. # # Changes: # - Initial translation # Camale?n <noelamac at gmail.com>, 2012 # # -

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

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

Package: xcp-xe Version: 1.3.2-8 Severity: minor XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not. Difference: XCP 1.1 behavior: xe sr-probe type=nfs device-config:[Tab] device-config: device-config:serverpath= device-config:server= xcp-xe behavior: xe sr-probe type=nfs device-config:[Tab] (nothing) Other arguments

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: