similar to: LVM SR-backend, vm-clone - find out dependent logical volumes

Package: xcp-storage-managers Version: 0.1.1-2ubuntu1 Severity: normal This bug prevents CDROM VDIs from being hotplugged into guest VMs. The issue is that the NFS ISO SR configures the ISO VDIs to be 'file' types, which it should configure them to by 'phy' types. This breaks on Debian's Xen because the Debian hotplug scripts are more robuse than the ones on XenServer, and

Dear list, We observed the following issue in conjunction w/ XCP 1.1 which is a _severe_ problem. Our environment: - Two XCP 1.1 hosts in the same resource pool - Shared LVM based storage repository based on DRBD - VMs running on both systems stored on the shared SR If suddenly one host dies unexpectedly (e.g. hardware defect, power issue) the metadata still assumes the VMs that were running on

It seems that in XCP 1.0, VDIs have a size limit of 2TB, even when sm-config:type=raw is set. I understand the 2TB limit when using VHD, but shouldn''t that limit be relaxed for raw? -Dustin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi all, we have followed the very good HOWTO by http://wherethebitsroam.com/blogs/jeffw/drbd-xcp-05 and set up DRBD on XCP 1.1 in primary/primary mode. It works fine, but I am wondering how to squeeze more performance out of the system (we currently use a crossover GB Ethernet connection). When writing a 1 GB file on a guest I get write performance of about 5MB/s (idle). We have disabled all

hi I am having several pools of xcp with NFS shared storage as default SR on each pool and i want to do following in this arrangement -I want to share vdis among all pools, i.e. for example if I want to detach a vdi from a vm in pool-1 to a vm in pool-2. so is this possible to do so? vdi export is one of the solution but i want to do it seamlessly just like it happens within the same pool or

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

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]

Simon, To add on to this question: Is it possible to run a VM (RHEL 5.2) which I had created on XCP 0.5 on XCP 1.0 whenever it is released? Regards, Prateek > > > > ---------- Forwarded message ---------- > From: Simon Hobson <linux@thehobsons.co.uk> > To: xen-users@lists.xensource.com > Date: Wed, 18 Aug 2010 17:10:33 +0100 > Subject: Re: [Xen-users] Cloning VM

Hi All. I am currently using OpenStack Juno on CentOS 7. The problem is that by default OpenStack's Cinder service creates logical volumes of "linear" type. I would like to have them stripped over all physical disks to get better write performance. Is there a way to tell LVM to create by default stripped volumes instead of linear ones? BR, Rafal.

Hi To deploy KVM vms I use a KVM template + script - which is cloned, then cloned again and resized - using virt-resize. i.e ---------------------------------------------------- virt-clone --original debian6template-DONTSTART --name NAME.test -f /dev/vgpool/NAME.test virsh vol-create-as vgpool NAME 8G virt-clone --original NAME.test --name NAME -f /dev/vgpool/NAME virt-resize --expand

(new) blktap-dev_2.0.90-1_amd64.deb extra devel Xen API blktap shared library (development files) The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, delivering the Xen Hypervisor with support for a range of guest operating systems. This package is part of it. It implements the userland part of the blktap driver. . Virtual Hard

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)

Package: xcp-xe Version: 1.3.2-8 Severity: minor XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not. Difference: XCP 1.1 behavior: xe sr-probe type=nfs device-config:[Tab] device-config: device-config:serverpath= device-config:server= xcp-xe behavior: xe sr-probe type=nfs device-config:[Tab] (nothing) Other arguments

Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is

The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed

Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package

Hi, You can simply boot a live system to create your partition layout and copy it over the existing system with rsync. Once your system is copied, you will need to customize all hardware-dependent configuration files such as {crypt,fs}tab, network configurations, bootloader and so on depending on your setup. Don't forget to install the bootloader afterwards! You can also install a minimal

Hi, I could be wrong, but afaik clonezilla makes bit-accurate copies of the file system like dd does. Therefore, no configurations should be adapted. Usually Linux doesn't care where it runs, as long as the underlying 'hardware' (or virtual hardware) architecture matches. However, there are a number of configuration files that need to be modified for such clones, including network

Hi all, I`m evaluating methods for nightly "snapshot" a physical win2003 to xcp vm. I know it would be a lot easier and reliable just to to one convert one time and start to generate real vm snapshots, but at this time I cannot use this method. I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big deal of using this method is that xenconvert does not send

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)