similar to: XCP boot failure

Hi, XCP is hanging at (or just after) "Setting Hostname" If you keep trying eventually it gets past this point. It might take 5-20 attempts to get XCP to boot. When it does boot all is stable. I have the same problem on 4 different boxes. 2 x INTEL Black Box Dual XEON server. 1 x AMD II x250 1 x Core2Duo NoteBook used for DEV. All 3 boxes are using mdadm raid 1. The

With XCP how do we autostart a VM when a host boots up? In Xen I would have made a symbolic link to the VMs config in /etc/xen/auto/ Also does anyone know why LVM is disabled in the /etc/rc.d/rc.sysinit in XCP 1.1 beta? I uncommented it and when my Host boots it does a vgchange -ay now and the LV gets mounted in the fstab. I can''t think of a reason why this isn''t the default

I really wants to know. When I start "xm create fc3 -c" but always maintenance mode. Is someone kind enough to point whats wrong with me? Configfiles are like this. kernel ="/boot/vmlinuz-2.6.11-1.1177_FC4xenU" memory =128 name = "fc3" nics = 1 disk = [''file:/root/fedora.img,hda2,w''] ip="210.166.211.245"

This is a bit long-winded, but I wanted to share some info .... Regarding my earlier message about a possible race condition with mdadm, I have been doing all sorts of poking around with the boot process. Thanks to a tip from Steven Yellin at Stanford, I found where to add a delay in the rc.sysinit script, which invokes mdadm to assemble the arrays. Unfortunately it didn't help, so it

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

Hello, Is it possible to create a custom template for XCP? Or edit an existing one? I know that I could create a VM and then exported as a template, but I would prefer to create a template like "Debian Lenny 5.0" that install debian from the network but with 64bits instead of the 32bits used by the template. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de

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, on a system RedHat 8.0, only on this, not on other various RedHat8.0, I have see the follow strange error in /var/log/{messages,boot.log} ..... After the boot all it seems to work, the modules is loads.... I have already tried to install other versions of kernel but the problem is always the same one :-(( Someone has some idea of what is happening? Thanks... Dario Lesca

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

I''m still running XCP 0.5 on two servers. I am trying to make a few 10Gig Slackware64 13.1 servers (using the Windows 2003 server template). However, every time I try to start the guests in OpenXenManager, they die with something like: Async VM.start Slack64 13.1 #3[''NO_HOSTS_AVAILABLE''] I tried starting the hosts from the xsconsole and got the same results. I

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important I still am not able to create iSCSI storage repositories using this command xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn> device-config:SCSIid=<my-scsi-id>

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

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-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

Dear All, Currently i am using CentOS 4.4 Linux After i am rebooted the PC and I have getting problem like /etc/rc.d/rc.sysinit: line 126: 442 Segmentation fault /bin/dmesg -n $LOGLEVEL Initialization hardware... /etc/rc.d/rc.sysinit: line 167: 450 Segmentation fault LC_ALL=C fgrep -xq "$1" /etc/hotplug/blacklist >/dev/null /etc/rc.d/rc.sysinit: line 167: 455 Segmentation

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

I just ordered quite a few servers, and, without verifying ahead of time, ordered without hard drives planning to boot over iSCSI using the built-in network cards (NOT an iSCSI HBA). I''m wondering if anyone has tried (and hopefully succeeded) installing XCP to an iSCSI volume using a network card with iSCSI boot support and the software iSCSI initiator in XCP. Obviously I can order HDs

Package: xcp-squeezed Version: 1.3-13 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts piuparts.d.o Hi, during a test with piuparts I noticed your package failed to install due to incorrect dependencies in the init.d LSB header. Some debian notes are available from at http://wiki.debian.org/LSBInitScripts From the attached log (scroll to the bottom...): Selecting

The issue: - raid1 will be in degraded state if one of its components is logical volume (LV) - raid0 will be inoperable at all (inacessible from within appliance) if one of its component is LV - raidN: you can expect the same issue for any raid level depends on how many components are inaccessible at the time mdadm is running and raid redundency. It happens because mdadm is launched prior to lvm

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under