search for: sarraf

...is licensed GPL2 and is a combination of multiple packages. Has the team looked at the feasibility of taking the agent component from XCP and packaging it for Debian. If we can get the agent, and then along with OpenXenCenter, we can have a good management tool for Xen in Debian. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.debian.org/piperma...

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:

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

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

...-1 is not configured yet. dpkg: error processing xen-hypervisor-3.2-1-i386 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: xen-utils-3.2-1 xen-hypervisor-3.2-1-i386 E: Sub-process /usr/bin/dpkg returned an error code (1) Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://list...

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

...STACK value right in its script. Where do we want to fix it? I have filed bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661687 If that is fixed, as part for xcp post-install, just set /etc/default/xen to xcp and we should be good. Okay??? Let's target it for Wheezy -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.d...

...penXenManager has cleared the NEW Queue and is now part of the archive. http://packages.qa.debian.org/o/openxenmanager.html On 10/08/2011 01:06 AM, Cheng Sun wrote: > Ritesh, > >> You can track the packaging efforts over here until it gets >> uploaded: https://github.com/rickysarraf/openxenmanager > Great, cheers. > >>>>> tunnel.py has no license >>> I cannot trace where this code came from. >>> > >> This one is used in window.py for the transport. We'll need a >> license for this. > > I am led to believe that...

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

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}

...kage 'libv8-3.8.9.16' Changed Bug submitter to 'J?r?my Lal <kapouer at melix.org>' from 'J??r??my Lal <kapouer at melix.org>' Warning: Unknown package 'libv8-3.8.9.16' > submitter 668611 Bj?rn Mork <bjorn at mork.no> Bug #668611 {Done: Ritesh Raj Sarraf <rrs at debian.org>} [laptop-mode-tools] /usr/sbin/laptop_mode: append to stdout/stderr to avoid truncating logs when redirected Changed Bug submitter to 'Bj?rn Mork <bjorn at mork.no>' from 'Bj??rn Mork <bjorn at mork.no>' > submitter 668612 Luis Fernando Llana...

Package: blktap-dkms Followup-For: Bug #717157 I picked the commits from upstream. You should consider pushing it to the archive. root at ibmx3650m2-210-147:/usr/src/blktap-2.0.91# diff -Naru ring.c /tmp/ring.c --- ring.c 2013-09-17 11:47:27.468200000 -0400 +++ /tmp/ring.c 2013-09-17 11:47:56.836200000 -0400 @@ -210,7 +210,7 @@ pgoff = 1 + request->usr_idx *