similar to: Kernel 3.18.21-17 and 3.18.21-18 kernel panics

On 02/21/2016 08:02 PM, Shaun Reitan wrote: > I've seen this issue on about 15 different servers now. Anybody else seeing this? > > Screenshot: http://imgur.com/cBcwr8l > > I also have a video of the boot process if that will be helpful. Are you missing the initrd line in /boot/grub/menu.lst? That's a known bug that I believe has been fixed with 3.18.25-something.

We're using the stock configuration, the dom0 is limited to 1024MB via grub. ------ Original Message ------ From: "Pasi K?rkk?inen" <pasik at iki.fi> To: "Shaun Reitan" <shaun.reitan at ndchost.com>; "Discussion about the virtualization on CentOS" <centos-virt at centos.org> Sent: 6/26/2016 9:30:57 AM Subject: Re: [CentOS-virt] Cannot

On 01/08/2018 02:10 PM, Shaun Reitan wrote: > While installing the experemental kernel on a CentOS 7 PV the following > happened. After a reboot of the PV the kernel looks to be installed but > there is no option for booting it in grub. ?I attempted to run yum > reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but > still no entry in grub. No initramfs existed and

On 01/06/2018 03:16 AM, Dmitry Melekhov wrote: > The same problem with latest centos 6 kernel,i.e. with meltdown fix. > > I can't see console output, because I have it on "cloud" provider > hosting :-) > > > > 06.01.2018 05:13, Shaun Reitan ?????: >> Broken! >> >> For those of you looking for a PV enabled client Kernel for CentOS Linux

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

On 05/31/2016 02:01 AM, Minchan Kim wrote: > Per Vlastimi's review comment. > > Thanks for the detail review, Vlastimi! > If you have another concern, feel free to say. I don't for now :) [...] > Cc: Rik van Riel <riel at redhat.com> > Cc: Vlastimil Babka <vbabka at suse.cz> > Cc: Joonsoo Kim <iamjoonsoo.kim at lge.com> > Cc: Mel Gorman

On 05/31/2016 02:01 AM, Minchan Kim wrote: > Per Vlastimi's review comment. > > Thanks for the detail review, Vlastimi! > If you have another concern, feel free to say. I don't for now :) [...] > Cc: Rik van Riel <riel at redhat.com> > Cc: Vlastimil Babka <vbabka at suse.cz> > Cc: Joonsoo Kim <iamjoonsoo.kim at lge.com> > Cc: Mel Gorman

On 01/05/2018 06:33 AM, George Dunlap wrote: > On Thu, Jan 4, 2018 at 7:12 PM, Sarah Newman <srn at prgmr.com> wrote: >> On 01/04/2018 10:49 AM, Akemi Yagi wrote: >>> On Thu, Jan 4, 2018 at 9:51 AM, <rikske at deds.nl> wrote: >>> >>>> Please patch the CentOS-virt Kernel to fix the >>>> Kernel Side-Channel Attacks vulnerabilities.

On Wed, Jun 22, 2016 at 6:45 PM, Shaun Reitan <shaun.reitan at ndchost.com> wrote: > Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a > guest because of what looks like an issue allocating memory even though xm > info shows like 5x the amount of free memory needed? We are still > unfortunately still using xm... it's on my list, i know.. > >

Broken! [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.0-693.11.6.el7.x86_64 (builder at kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Thu Jan 4 01:06:37 UTC 2018 [ 0.000000] Command line: root=/dev/xvda ro

We need a way to do two things to /usr/bin/grub-bootxen.sh in Xen4CentOS. 1. Automate running it if xen (the package) and the xen kernel are installed. But only if the user WANTS to run it. 2. Allow users to automatically modify the variables passed into the xen.gz line (that is, more or less memory, add console settings, etc.) If you look at the current script,

Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC

While installing the experemental kernel on a CentOS 7 PV the following happened. After a reboot of the PV the kernel looks to be installed but there is no option for booting it in grub. I attempted to run yum reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but still no entry in grub. No initramfs existed and I found kernel-modules did not install properly so I then ran

My /var/log/messages log is being flooded with kernel messages showing the following messages Aug 1 11:22:52 host43 kernel: System RAM resource 48000000 - 4fffffff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17 Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

Hi just a little question. Can I boot FreeBSD over network with pxelinux ?

I actually move the default *.repo files and replace them with "". The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more. I would argue that I should not need to install any *-release-* rpms at all to get all the required software. On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:

I ran "yum update" the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that.

This is not abit issue just a minor annoyance. I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo. I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d. -- Alvin