similar to: Any tips on dealing with a super hung XAPI process?

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

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

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

Hi, this is the second time I step. After that I filled the dom0 disk, and freed space, xapi stopped working, no xe command works, I can not restart xapi (for the same problem). The first one I could fix it then restart the server, I can not because I have a vm in production. Any ideas on this? Saludos -- nycko _______________________________________________ Xen-users mailing list

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

Hi - I''m trying to use the instructions here http://xen.pablolibo.com/doku.php to create a new VM but it''s not clear where the .cfg file should go and what to do next. I was thinking xe needs to install the vm from the /mnt/so_xen mount but i''m not sure. Are the steps on the site reasonable? Is there a way to install a vm from USB instead?  I don''t have an

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-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 all, i meet a big problem, when i finish install xcp-xapi on ubuntu 12.04, i set grub to go into xen 4.1 kernel when startup and set echo ''TOOLSTACK="xapi"'' > /etc/default/xen when i reboot and login to the system , i got a lot out of memory error and all process be killed, seem like kernel crash. can anyone help me about that ? thanks.

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

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-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

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

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :

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

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