similar to: xcp 1.1 - target release date?

Hi, I''ve collected together a bunch of XCP-related project suggestions and stuck them on the xen wiki: http://wiki.xensource.com/xenwiki/XAPI_project_suggestions The main idea is that new people who want to work on XCP can use this list for inspiration... each idea has a rough guesstimate of size/ knowledge required/ impact and an initial first contact (who either suggested the idea

I see on the XCP roadmap that ocfs2 is in the plans. Can anyone give a guess on how long that might be? Would I be correct assume that would allow you to use sparse files on XCP when using ocfs2? I looked at XenServer this week and converting my existing sles domU''s from my current sles server is not easy. Since XenServer and XCP seem pretty close, will it be any easier with XCP?

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)

On Sun, Jan 13, 2013 at 7:39 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> > wrote: > >> Good points David, I don't feel qualified to evaluate the differences > >> between those versions though... Perhaps Richard or Doug could comment > here? > > > > Unless

Hi team, I am beginning on R and I try to install Rmpi library and I have problems, I have installed LAM-MPI on Rocks; [rcnavarro at hpc-cip ~]$ laminfo LAM/MPI: 7.1.1 Prefix: /opt/lam/gnu Architecture: x86_64-unknown-linux-gnu Configured by: root Configured on: Wed Oct 19 18:12:25 EDT 2005 Configure host: rocks-156.sdsc.edu Memory

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

Hello all, Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, MSVC and clang. I mostly considered only the latest versions of the proposals where there were several, where not there is a link to a note at the bottom. Furthermore I did not scourge through 3 bug databases and I implicitly trusted the wiki page. I drew up a list of profiles, listing the base

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

On Sun, Jan 13, 2013 at 9:57 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: >> Hello all, >> >> Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, >> MSVC and clang. >> >> I mostly considered only the latest versions of the proposals

El 31 de marzo de 2018 17:58:18 CEST, Rafael Wolf <rfwolf at gmail.com> escribió: >Can you just compile the latest from the git repo on to raspian os? > > > >On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > >> El 29 de marzo de 2018 23:41:24 CEST, Ramses ><ramses.sevilla at gmail.com> >> escribió: >> >Hi

On Sun, Jan 13, 2013 at 7:00 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 9:57 AM, David Blaikie <dblaikie at gmail.com> wrote: > > On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> > wrote: > >> Hello all, > >> > >> Using the Apache Wiki [1] I summed up what can be used

On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: > Hello all, > > Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, > MSVC and clang. > > I mostly considered only the latest versions of the proposals where there were > several, where not there is a link to a note at the bottom. Furthermore I did > not

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:

Hello, I have tried to use VM template of Solaris 10 from XenServer 6 on XCP 1.1. It doesn''t work (details are in attachment). Is there somewhere a collection of proven [PH]VM templates for XCP 1.1 for such OSes like: - ubuntu 11.10 - Solaris 10 / Solaris 11 - CentOS 5.7 / CentOS 6 - RHEL 6 Thank you in advance for any hints. regards, Mark -- ms@it-infrastrukturen.org

As seen on the mailinglist, many have been hit by the issues with the igb driver included in xcp 1.1 and below ( and 5.6 fp* and below as well ), version 2.4.3, which due to a bug prevents VLAN tagging and other features from working correct (sr-iov). This mainly affects systems with Intel 82576 nics. There are work arounds for this, mainly updating the driver from intel, see here:

Hello, When trying to start VM I am getting the following error: # --- [root@xcp-dev01 ~]# xe vm-start uuid=f535e5bd-6540-3745-d494-14f776da85e5 Error code: INVALID_SOURCE Error parameters: Unable to access a required file in the specified repository: file:///tmp/cdrom-repo--2OF-Z/install.amd/xen/vmlinuz., , # --- I have used last xen server documentation to prepare the VM installation from

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

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