search for: awale

...the display is stopped for 2-12 seconds. Then they continue. This happens even on the host OS, at the console. Host system running CentOS 5.2 x86-64: CPU : 2x Xeon E5430 @ 2.66GHz RAM : 24GB Mobo : DSBV-DX HD : 5 x SATA ST3750330AS 750GB in RAID5 There are 5 VMs, detailed at http://www.awale.qc.ca/vmware/stj1.txt to make this mail shorter. Seems to me this system should be more then adequate to handle the load. This is what vmstat on the host looks like when the server is "unhappy" : http://www.awale.qc.ca/vmware/vmstat.txt Spending a lot of time in 'wa', but &...

Hello, I am not only interested in finding out which genes are the most highly up- or down-regulated (which I have done using the linear models and Bayesian statistics in Limma), but I also want to know which genes are consistently highly transcribed (ie. they have a high intensity in the channel of interest eg. Cy5 or Cy3 across the set of experiments). I might have missed a straight forward

[resending, cutting out git pull-request output to make message smaller] Hi all, I have written a COM32 module called "acpioff", that, not surprisingly, powers off a machine using ACPI. I have tested it only using pxelinux.0 with a SeaBIOS/Qemu virtual machine. Since the changeset pulls in a "Linux-ized" version of the open source ACPI Component Architecture, it was too big

Hi all, I have written a COM32 module called "acpioff", that, not surprisingly, powers off a machine using ACPI. I have tested it only using pxelinux.0 with a SeaBIOS/Qemu virtual machine. See the changes since commit c0c25b4826950162517896c5039c6d62d07115be: hdt: Adding postexec= option (2011-12-17 22:27:07 +0100) available in the git repository at:

Hi All, I have a system, that, ~80% of the time, fails to properly boot using pxelinux.0 as provided by RHEL 5.5 (syslinux 3.11, I think). The gripe, before the console messages stop, is a message that comes from the linux kernel complaining the compressed ram drive image is bad: "invalid compressed format (err=[small number])". I have two questions: 1. How should I go about

Update on this problem: I gave up on the "native" h.323 because, like others, I couldn't get audio working. (yes, I tried disabling FastStart in ast_h323.cpp - no change) So I went and got the OH323 code from www.inaccessnetworks.com. Glad to say that everything seems to work so far. Not only does audio work, but even the handshaking is now working in both OpenPhone and even

Hi all, I have written a COM32 module called "acpioff", that, not surprisingly, powers off a machine using ACPI. I have tested it only using pxelinux.0 with a SeaBIOS/Qemu virtual machine. Since the changeset pulls in a "Linux-ized" version of the open source ACPI Component Architecture, it was too big to post as a patches to the list. See the git pull-request output below.

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4

flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4

flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18805 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18844 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18844/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 12557 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail

Hi. I have run across this old problem: http://www.syslinux.org/archives/2010-November/015753.html when compiling 4.05 on an x86_64 RHEL 5.5 systems with nasm v2.10 and GNU ld 2.17.50.0.6-14.el5 20061020. The exact symptom is the linker (ld) improperly loads pxelinux.o, created by nasm, to pxelinux.elf. The pfx_* symbols in the .prefix section end up being filled with 0's in pxelinux.elf.