similar to: OpenXenManager packaging

I just noticed OpenXenCenter (aka OpenXenManager) that is an open source replacement for Citrix's XenCenter. This tool works with XenServer. But as per the blog entry: http://blog.xen.org/index.php/2010/02/09/xen-cloud-platform-installation/ it is also supposed to work with Xen Cloud Platform. XCP is licensed GPL2 and is a combination of multiple packages. Has the team looked at the

Package: xen-utils-3.2-1 Version: 3.2.0-1 Severity: important X-Debbugs-Cc: rrs at researchut.com Hi, xen-utils fails to install. I'm sorry that I couldn't gather other information that reportbug gathers. virtian:~# apt-get install xen-hypervisor-3.2-1-i386 xen-utils-3.2-1 xen-docs-3.2 Reading package lists... Done Building dependency tree Reading state information... Done The

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

http://bugs.freedesktop.org/show_bug.cgi?id=23832 Summary: extended display not working Product: xorg Version: 7.4 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

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

Processing commands for control at bugs.debian.org: > reassign 702338 openxenmanager Bug #702338 [xcp-xe] can't create network from xe command line Bug reassigned from package 'xcp-xe' to 'openxenmanager'. No longer marked as found in versions xen-api/1.3.2-14. Ignoring request to alter fixed versions of bug #702338 to the same values previously set > End of message,

Package: xcp-xapi Version: 1.3-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

Package: xcp-xapi Version: 1.3.2-11 Severity: normal We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

Package: xen-utils-common Version: 4.1.2-3 Severity: important /etc/default/xen, which carries the TOOLSTACK setting, is not honored by xend init script. The xend initscript doesn't check for the value of TOOLSTACK. It just populates it in its initscript. lnx200-39:/etc/init.d# grep TOOLSTACK * xend:TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) xend: if [ -z

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

Package: xcp-xapi Severity: normal Tags: upstream Are there good reasons why xapi by default prefers to bidn to 80 and 443? This will lead to xapi installation/start failure on every server machine that might (and will probably) have apache installed. I know we can remove apache or change its port or change xapi's port (But I've had a hard time to easily find out where to specify the

Package: xen-utils-common Version: 4.1.0~rc6-1 Severity: important Currently xend fails to create a fully virtualized vm because it has a different path hardcoded to it. Unable to complete install: 'POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found")' The correct path to use

Hi, I am trying to install openxencenter to control my VMs I followed the instructions but when I tried to start it I got:  File "window.py", line 44, in <module>     import gtkvnc ImportError: No module named gtkvnc does any one face this problem before. I tried to comment the import line and xencenter started but console tab is not working and it is lookoing for gtkvnc module.

Package: xcp-xapi Version: 1.3-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

Package: xcp-xapi Version: 1.3-15 Severity: normal My packages were initially installed from the deb repository at download.xensource.org. Eventually, I upgraded them to the debian repository ones. Right now, xcp-xapi fails to start with the following messages. lnx200-39:~# /etc/init.d/xcp-xapi start Error: Connection refused (calling connect ) lnx200-39:~# -- System Information: Debian

Package: xcp-xe Version: 1.3.2-14 Severity: important I created an internal network using xe network-create name-label='Private NAT network' Looking with brctl, I could see xapi0 had been created by the tools. However, the network does not appear in openxenmanager. I even restarted openxenmanager, it still didn't appear. Then I deleted the network and created it again from

Package: xcp-networkd Version: 1.3.2-11 Severity: normal Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64

Yes, I am sure because other information pulled are correct. And the same way we have used libvirt APIs to extract other informations at different places. My question is if VM is in shut-off state does it mean running ? IF not, what is the correct state for this VM. I am wondering why the state is 'unsigned char' in virDomainGetInfo, why it could not be 'enum' as it is returning

Hi Libvirt support team, Could you please help me with below query. Regards Ritesh Sharma From: Panday Ritesh Sharma (rpanday) Sent: Tuesday, September 24, 2013 8:22 PM To: 'libvir-list@redhat.com'; 'libvirt-users@redhat.com'; Vinay Shankarkumar (vinays) Cc: Basavaraj Bendigeri (bbendige); q-se-dev(mailer list) Subject: virDomainGetInfo() returns wrong domain state Hi Team, I

Here is the packet trace - ICMP seems to be coming from my SAMBA Server - see frame 3 Does the netstat output look correct in my first request for help? Joel Morrow jiram@aol.com TRACE Frame 1 (92 on wire, 92 captured) Arrival Time: Dec 22, 2001 09:36:08.333676000 Time delta from previous packet: 1.999444000 seconds Time relative to first packet: 2.000088000 seconds Frame