similar to: xapi on CentOS 6

Hi, I am a masters student at IIIT Hyderabad, India. I am writing a GOSC proposal for CentOS organization. It's about delivering a custom installer ISO which delivers Xen 4.4 stack on CentOS 6. full proposal: http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/gautam_malu/5629499534213120 I want to port xapi on CentOS 6 as part of it. There has been some previous efforts to

Hi everyone, I am a masters student at IIIT- Hyderabad, India. I have submitted my GSOC proposal for Xen in a Box. I would be great to have some suggestions especially about the porting of xapi on CentOS Abstract: My project goal is to deliver set of scripts preferrably in bash, along with all necessay packages to convert standared installers ISOs into customized ISOs which install CentOS 6 +

Thanks Jon, it worked, I was able to build all the packages for xenserver on CentOS 6.6 final version. Here is the package list: https://gist.github.com/gautammaloo/7616cccbe8f5c85c196e I was wondering what packages would be necessary to use Xen with xapi, I already have xen with xl installed. Could we have a package like http://packages.ubuntu.com/precise/xcp-xe with which we can have

Hi, Regarding my gsoc proposal (xen in a box), I have developed a set of scripts to create a custom CentOS ISO which delivers Xen 4.4 stack on CentOS 6.6 with libvirt and fully bridge network settings. I have used xen scripts for networking settings. Waiting for feedback. scripts: https://github.com/gautammaloo/centos-xen proposal:

On Sun, Mar 22, 2015 at 6:23 AM, Gautam Malu <gautam.maloo at gmail.com> wrote: > Hi, > I am a masters student at IIIT Hyderabad, India. I am writing a GOSC > proposal for CentOS organization. It's about delivering a custom installer > ISO which delivers Xen 4.4 stack on CentOS 6. > full proposal: >

Hi, I am Masters student at IIIT Hyderabad, India. I have made a set of scripts to make a customized installer ISO which installs Xen4.4 + CentOS 6.6. I have tested it on a Xen HVM VM. I would be great if anyone can test it out. https://github.com/gautammaloo/centos-xen Best regards, Gautam Malu -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I am doing xen in box gsoc project. The aim of the project is to have custom installer ISO which delivers xen stack running on c7 along with necessary bridge networking configuration. But I am getting confused over how to package bridge networking settings, so that I can deliver that during installation itself. I can use bridge-utils and package ifcfg-* files as differnet package. But for

i am trying to add auto migration feature in XEN. so is anyone has worked related to migration part. i need help regarding files related to migration. -- Regards Gautam _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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-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

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

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 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

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

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}" !=

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.

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-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

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