similar to: XCP Guide Updates

Hi I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu. But I got this error while configuring xcp-xapi: xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed. when I comment the

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

I would like to install XCP. So I started at http://www.xen.org/products/index.html and found the section labeled ''Xen Cloud Platform Project'' This section was a nice overview but no links to docs or downloads. The next section was labeled ''USERS'' which had a download link to ''Xen Cloud Platform 1.5 Beta Download''

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

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

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

On 12/22/2011 01:37 AM, Mike McClurg wrote: > Hi Thomas, Jon, > > I was hoping that you could both comment on this github pull request: > > https://github.com/jonludlam/xen-api/pull/12 > > Mike > In Debian, /etc/default/xen is there to select xm vs xl. So we could do: if ! [ -f /etc/default/xen ] ; then TOOLSTACK=xm else . /etc/default/xen if ! [

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-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

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: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port

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

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

XenServer Installation Guide from  http://www.citrix.com/site/resources/dynamic/salesdocs/XenServer_Quick_Installation_Guide.pdf This is a step by step guide for the installation.  I have some questions as to the content of the guide: p.5 Enable thin provisioning (Optimized storage for XenDesktop). What does this mean? What are the values and consequences? p. 5 One of the choices is not to

I would like to gain some idea of the XCP impact of these two CPU versions: Intel Core i7-2600, 3.4 GHz Core i7-2600K, 3.5 GHz Both have VT-x Differences 2600K does not include: Embedded Opions Available vPro Technology Virtualization Technology for Directed I/O Trusted Execution Technology Is the difference critical? Thanks, ray

The Kronos page: http://wiki.xen.org/wiki/Project_Kronos includes these two entries: A couple of network-related notes + XAPI expects to run in a clean environment, and listens on ports 80 and 443. If you''re running anything else on these ports (typically Apache/Apache2), then you''re likely to have problems. + There is a known bug (which needs to be fixed)

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

Processing commands for control at bugs.debian.org: > reassign #680528 xen-utils-common Bug #680528 [xcp-xapi] xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-8. Ignoring request to alter fixed versions of bug #680528 to the same values previously

Package: xcp-xapi Version: 1.3-15 Severity: normal My packages were initially installed from the deb repository at download.xensource.org. Eventually, I upgraded them to the debian repository ones. Right now, xcp-xapi fails to start with the following messages. lnx200-39:~# /etc/init.d/xcp-xapi start Error: Connection refused (calling connect ) lnx200-39:~# -- System Information: Debian