similar to: XCP memory management

Hello! I''m quite new to Xen, and am wondering what is the best way to handle my XCP based server... Eg. video console for installation and maintenance, shutdown, restart, disk and memory config, etc. I read about openxenmanager, but it seems like an abandoned project, and seems extremely nontrivial to use under OSX. What about XenWebManager? I need to install that on the XCP server

Thanks for all the help... XVP seems quite high on requirements. Like it needs an SMTP server set up. I''m not sure I like that. I found a tool called BixData, it''s proprietary but with a free license for a limited number of managed servers. Being a fully fledged cloud management system, it''s true overkill for me and my 3-4 virtual machines, but at least it seems quite

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)

Sorry for posting again, but because the subject.Hi All, I have 5 servers each: Intel Quad Core i7 2.4Gig (8 processors)2 *1TB HDD2*1Gig NIC12G RAM I installed XCP 0.5 on each and all are joining a resource pool.Then I installed 2 Centos 5.5 VM on each XCP host and I used the following command to specify the number of vCPUs for each VM: xe vm-param-set uuid=$VM_UUID VCPUs-max=4xe vm-param-set

Hi David > Hi all, So I have been playing around with XCP and the static/dynamic > memory parameters. I have a few behavioral questions I would like to > pin down: > > -Is the static-max quantity of free memory on the host always > required before the guest vm can be started? I assume so since you > don''t know a-priori if the guest you are booting supports Xen or

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal This was already reported in the archived bug 691805 but I sent an e-mail and I received back permanent delivery failure because this bugs has been archieved. Still the path of "pidof" in the file /usr/lib/xcp/sm/iscsilib.py is wrong on Wheezy. It should be /bin/pidof instead of /sbin/pidof root at xcpcompute2:~# cat

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>

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important The xcp-storage-managers seems to depends on sg3-utils package which contains the 'sginfo' (/usr/bin/sginfo) binary called by /usr/lib/xcp/sm/scsiutil.py script twice (lines 105 and 107). A simple 'apt-get install sg3-utils' solved this issue so I believe that xcp-storage-managers dependency list needs to

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

Xen List After planning for a year to move my Xen 3.4 classrooms to XCP I''m now making an effort. With the old system I wrote many lines of bash scripts around the xm command to group and manage my VMs. I used sudo to grant privileges for each student to start, stop, console into, reboot, and wipe their VMs without any interaction from me. Now with XCP I had the hope of moving to the

Hi all, So I have been playing around with XCP and the static/dynamic memory parameters. I have a few behavioral questions I would like to pin down: -Is the static-max quantity of free memory on the host always required before the guest vm can be started? I assume so since you don''t know a-priori if the guest you are booting supports Xen or not. But if this is true, what is the use of

Package: xcp-storage-managers Version: 0.1.1-3.1 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem tp crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

XCP Users: I received an email from Alberto Gonzalez Rodriguez who created OpenXenCenter/OpenXenManager and is now working on OpenXenWebManager. Info to access the tool is: steps to test are: download from http://bit.ly/bres2U uncompress: tar xvfz xenwebmanager_rev24_full.tar.gz cd xenwebmanager python frontend.py and with a browser open http://localhost:8080 (or http://ip:8080) you need

XCP Users: As many of you are aware, there are several open source products available for everyone to use when working with XCP. I would like to get some feedback on the various tools to get a feeling on how people are using XCP and these tools. Here are the tools that I am aware of (please respond if you are using another tool): * OpenXenManager -

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

Hi, I'm trying to build a XCP environment based on wheezy and iSCSI storage. When I try to add a iSCSI SR I get the following error: The SR could not be connected because the driver was not recognised. driver: lvmoiscsi As I couldn't find the driver in /usr/lib/xcp/sm I took a look into the package itself and saw that the driver exists in drivers, but is not listed in the Makefile. Is

Hi, We found a crash in tp contained in the xcp-storage-managers package. You are being contacted because your are listed as one of the maintainer of xcp-storage-managers. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report

Hi, attached I have some patches which add support for iSCSI LVMoISCSI to the xcp-storage-managers package. The patches are based on the Debian git repository. I have tested my changes and everything seems to work fine. The tests are done on a three node XCP pool with multipath. I haven't tested the changes without multipath. Maybe someone could take a look on the patches and give me some

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)