search for: kernel1

...bugs have different causes, but if they do then potentially we're > seeing a mix of both since my test has no way to distinguish them. > I just experimented with this, I think it's the issue I suggested at: https://bugzilla.redhat.com/show_bug.cgi?id=1269975#c4 I created two VMs, kernel1 and kernel2, just booting off a kernel in $HOME/session-kernel/vmlinuz. Then I added this patch: diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c index f083f3f..5d9f0fa 100644 --- a/src/qemu/qemu_process.c +++ b/src/qemu/qemu_process.c @@ -4901,6 +4901,13 @@ qemuProcessLaunch(virConn...

As people may know, we frequently encounter errors caused by libvirt when running the libguestfs appliance. I wanted to find out exactly how frequently these happen and classify the errors, so I ran the 'virt-df' tool overnight 1700 times. This tool runs several parallel qemu:///session libvirt connections both creating a short-lived appliance guest. Note that I have added Cole's

----- Oorspronkelijk bericht ----- Van: "Jim Perrin" <jperrin at centos.org> Aan: centos at centos.org Verzonden: Donderdag 22 september 2016 17:19:42 Onderwerp: Re: [CentOS] always boot from Elrepo kernel On 09/22/2016 10:14 AM, johan.vermeulen7 at telenet.be wrote: > Hello All, > > I purchased some Dell Latitude 3570 laptops. They came with Ubuntu preinstalled. (

--- v2v/convert_linux.ml | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index f670812..39a520c 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -49,13 +49,14 @@ type kernel_info = { ki_modules : string list; (* The list of module names. *) ki_supports_virtio : bool; (* Kernel has

...oots from that kernel again. There is no reason to keep the CentOS Kernel on your machines if the elrepo kernel is what you want to use. You should be able to (1) boot from an elrepo kernel then do: rpm -qa | grep kernel | sort then pick out the CentOS kernels and do: rpm -e <kernel> <kernel1> where <kernel> and <kernel1> are the name-version of the kernel you want to remove. Then you should not get updates for the CentOS Kernels, only for elrepo ones. The advice Jim gave you will then allow an update of 'kernel-ml' to actually update the grub. One thing to th...

...e (yn2$reason[i] = 1) } x1 = yn1$deathday / (1*10^3); d1 = yn1$reason; x2 = yn2$deathday / (1* 10^3); d2 = yn2$reason; loglik <- function( theta, param) { sum(d1*log(hazard1(x1, param)) - chazard1(x1, param) + d2*log(hazard2(x2, theta, param)) - chazard2(x2, theta, param))} / 10000 kernel1 <- function(theta, param) { exp(loglik(theta, param)) + log(10000)} kernel2 <- function(theta, param) {( exp(loglik(theta, param)) + log(10000)) * gm(theta, param) } kernel2(theta0, param0) adapt(4, lower = c(0, 0, 0, 0), upper = c(1, 1, 1, 1), functn = kernel2(theta0, param0)) So I...