similar to: Kronos - VPN and Apache

Hi All, I tried again with XAPI on Debian last night and this time things went far smoother... I managed to boot into the Xen kernel, xe is working and the XAPI daemon appears to be running. However, I am having trouble connecting to XAPI from XenCenter... it just says the connection was refused without any meaningful errors and nothing in the logs on either side. I can ping the Xen machine from

I''ve just been playing with XenSource and Kronos packages, but the fast cloning ability from XenServer doesn''t appear to be available. Where does this come from exactly, is it something built into Xen or is there a component of XenServer that''s needed to handle it? I was hoping to use Xen on Debian with my web app controlling it using either XAPI or Libvirt, but I

I have Kronos setup fine. I have installed open-iscsi and setup the system as an initiator. However, I cannot seem to get xapi to allow me to setup the target as an SR. I was trying to use XenCenter but go nowhere. So I tried adding it manually and here is what I got: xe sr-create host-uuid=466aac75-c86a-496f-90e8-2a9925a9e9f7 content-type=user \ > name-label="Shared LVM over iSCSI

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

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

Package: xcp-xapi Version: 1.3-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

Hi there, I am trying to set up XCP on Ubuntu 12.04. I went through the procedure given in the README file of the xcp-xapi package and reached the point where the hypervisor seems to be running fine. I set up a VM using the Debian Squeeze (64bit) template and started it, giving a Debian mirror URL as install-repository. Running "xe vm-list" reports that the machine is running, but when

Hi all, today i tried to enable HA on xcp 1.6 but when i enable it through xencenter I received the following error in xensource.log: Dec 5 17:56:26 xcp1 xapi: [ info|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha] Using statefile: /etc/xensource/static-vdis/0/disk Dec 5 17:56:26 xcp1 xapi: [debug|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha]

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

Hi, I''ve trying booting Xen Hypervisor PV with a centos5 template using kernel and initrd from mirror.centos.org/centos/5/os/i386. When i start PV this go to installation mode. However this should boot with template. Please help in this regard what Am i doing wrong. -- Best Regards Asim _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

Package: xcp-xapi Version: 1.3.2-11 Severity: normal We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

Hi, I am a masters student at IIIT Hyderabad. I have applied for gsoc 2015, for xen in a box proposal. As a part of my proposal,I want to deliver xapi repo which can be used to build a custom installer ISO to install CentOS 6 + xen + xapi. Here is my full proposal http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/gautam_malu/5629499534213120 About building xapi packages for

Hi, Nice to receive your suggestions. Follwing the suggestions, the xapi service does work on a non XCP host and most of the xe interface of get information (such as "xe vm-list ")can work well. However, when I used the "xe sr-create" interface to create a SR, I got a error "The SR could not be connected because the driver was not recognised ". I noted that

Hi, Nice to receive your suggestions. Follwing the suggestions, the xapi service does work on a non XCP host and most of the xe interface of get information (such as "xe vm-list ")can work well. However, when I used the "xe sr-create" interface to create a SR, I got a error "The SR could not be connected because the driver was not recognised ". I noted that

Package: xcp-xapi Severity: normal Tags: upstream Are there good reasons why xapi by default prefers to bidn to 80 and 443? This will lead to xapi installation/start failure on every server machine that might (and will probably) have apache installed. I know we can remove apache or change its port or change xapi's port (But I've had a hard time to easily find out where to specify the

[previously posted to xen-devel@ and xen-api@ but this might be of interest to xen-users@ too] Hi, I''ve refreshed the Xen Cloud Platform (XCP) .isos on xen.org with a new development snapshot (labelled version 0.1.1). XCP is a collaborative effort to build a complete cloud infrastructure platform, complete with a powerful management stack, standards-based APIs, support for multi-tenancy

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

On Fri, Dec 12, 2014 at 02:21:08AM -0500, md at rpzdesign.com wrote: > Oops, I got it to work only after putting the WAN on port 656 so it > did not interfere with port 655 for the LAN. You should not need to have two tinc daemons just because you have a WAN and a LAN interface. By default (ie, if you don't specify BindToAddress and/or BindToInterface), tinc listens on all interfaces,

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to XAPI calls being sent from a CloudStack management server. In the past, a simple xe-toolstack-restart would do the trick but the script timed out while restarting the XAPI daemon. I found the process and first tried to use a simple kill command but the process was in a "defunct" state. I tried a kill -9 but no joy.