similar to: [Xen-API] 2TB limitation - bug?

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

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

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

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

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. Running xe vm-export on any vm results in the following error: root@squeeze:~# xe vm-export vm=ddf27dce-5851-2ed8-8fc3-8d7dfd64dbef filename=test.vhd Error code: SR_BACKEND_FAILURE_46 Error parameters: , The VDI is not available [opterr=Command [''/usr/sbin/vhd-util'', ''scan'', ''-f'', ''-c'', ''-m'',

I''ve just pushed vdiskadm translate to the 3.3 vdisk repo. You can now translate data from one virtual disk data type to another without creating a virtual disk. This allows the user to use a vmdk file and directly translate the data into a zvol without having to import it first to a vdisk and then export it to the zvol. # vdiskadm help translate translate - translate virtual disk data

I''ve just pushed vdiskadm import/export/convert to the 3.3 vdisk and vbox repos. You can now import a disk image from a block device or file to a vdisk, convert (in place) to a different type of vdisk and export from a vdisk to a block device or file. I''ve also pushed the full vhd support (sparse and fixed) and the ability to import a vmdk 1.1 optimized stream file. An

Hullo Everybody I have taken the steps below and I failed to get a device similar to /dev/xvda in DOM 0 where am I getting it wrong Create VDI, *[root@virtualintranet /]# xe vdi-create sm-config:type=raw sr-uuid=b303be09-6a32-8d94-d248-7551860fbc3f name-label="Centos-Vdi" virtual-size=20GiB type=user* eefa9066-a991-44c3-b537-d20d65f3d10c create VBD *[root@virtualintranet /]# xe

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

Hello, Why LIBVIRT software/libs need to chown "near the root level" (home/blahblah/) when raw/vdi/vhd can contains lots of directories as /home/user/Virtual_HDs/desktop/daddy/private/bedroom/number2/hd.vdi ? on ubuntu, "/media/hostname" can contains all our external HD's without relation with virtualization !!! :-( another sample picked up in the net: WARNING

Hi. Let me know if I should be reporting this elsewhere for reasons that I''m about to detail below. I''m fiddling with Xen 4.1.1 on Debian squeeze running kernel 3.0. I was really exciting about the Kronos project bringing the API to Debian/Ubuntu so I thought I''d give it a try. I''m find myself facing a number of challenges working with a local lvm based SR.

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

On Mon, Aug 07, 2023 at 01:06:55PM +0200, Sebastien WILLEMIJNS wrote: >Hello, > >Why LIBVIRT software/libs need to chown "near the root level" (home/blahblah/) when raw/vdi/vhd can contains lots of directories as /home/user/Virtual_HDs/desktop/daddy/private/bedroom/number2/hd.vdi ? > >on ubuntu, "/media/hostname" can contains all our external HD's without

Hello I have a problem with VDI already attached RW in the "adding tag" in blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR. Is there any solution to this problem? /var/log/SMlog: [32484] 2013-01-17 14:59:44.200883 vdi_activate {''sr_uuid'': ''e33281eb-ba4c-3829-9b61-7c64764dff9c'', ''subtask_of'':

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

I've had another attempt at installing Wheezy 64 bit from a template as PV. I attach my full script below. I've made much more progress this time, but there are still outstanding issues: - neither "xe console" or VNC seems to allow ALT-F[2-6] keystrokes, so I can't get other virtual terminals and therefore can't obtain any useful log/status messages. This issue alone

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

Hello all, Not sure if I am completely missing something but here goes. I have XCP 1.0 running without any issues. I have the mtu set on both the storage network, the corresponding PIF, and the VIF to 9000 and when displayed in ifconfig it shows that this is indeed true. I have several CentOs 5.6 VMs running in HVM mode (i.e. no xen kernel) which attach to the the storage network through these