similar to: xcp : vm installation

Hello Everyone, I am new with XCP. I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter and command console. Each host has two NICs, one (xenbr0) connected to a physical switch for Internet (said sw1), the other (xenbr3) connected to a physical switch for internal network (said sw2). I am trying to setup VMs and VLANs on xenbr3. I created a virtual bridge by

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

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Good day. XCP 0.5 xe host-evacuate uuid=f9458b0b-5e35-4ee0-adcf-c8945a37868c You attempted an operation on a VM which requires a more recent version of the PV drivers. Please upgrade your PV drivers. vm: a84aaf23-8afe-2ccc-0299-83b9dfd08c35 But at really vm uuid with bad PV-drivers is 42e397c7-3d76-02c0-a1f9-c78d79cac6c6 and no uuid a84aaf23... present in pool. I think, it is an error in

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

Good afternoon, The subject practically is saying what I''m trying to ask but... does anyone tried FreeBSD 8.2 or similar under Cytrix Xenserver or XenCloud?. I have been doing some benchmarks and seems to perform pretty nice... and seems to be stable too; the only thing would be nice to be available for FreeBSD at Xenserver/Xencloud would be the Xenserver/Xencloud''s

Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host:

Dear Debian maintainer, The Debian internationalisation team and the Debian English localisation team will soon begin the review of the debconf templates used in xen-api. This review takes place for all packages that use debconf to interact with users and its aims are: - to improve the use of English in all debconf templates; - to make the wording of debconf templates more consistent; - to

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.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

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-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

Hello, I am using XCP 1.0 and am accessing it with XenCenter. I have three NIC''s and I have bonded two of them through the XenCenter frontend. I then create a VLAN using XenCenter and attach it to the bond0. I create a VM and create its NIC to use VLAN 10, which it does and when the VM boots the NIC shows Active inside of XenCenter. When I look at the XCP host it shows VLAN 10 as an

Hi, I''ve installed XCP 0.5 and I''m following these steps: http://xenbits.xen.org/xapi/install.html to install ddk VM. But I can''t get network working. I tried to create a vif under xenbr0 then assigned mannually a IP address and to create a vif under xapi0. But in both cases I can ping only dom0 IP. What am I doing wrong? Thanks in advance. -- Sergio Roberto

Hi everyone! I have 2 hosts + 1 ISCSI device. I want to create a shared storage repository and both hosts use together. I wont use NFS. prepared sr: xe sr-create host-uuid=xxx content-type=user name-label=NAS1 shared=true type=iscsi device-config:target=xxxx device-config:targetIQN=xxxx hosts see the iscsi device: scsi4 : iSCSI Initiator over TCP/IP scsi 4:0:0:0: Direct-Access NAS

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

xe vm-start vm=debian Your license has expired. Please contact your support representative. Network and Management Interface XCP 0.5.900-36486c I was seriously under the impression we fixed this, now all my images are offline is there any way to fix this without reinstalling everything ? _______________________________________________ Xen-users mailing list

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)