similar to: New 3.10.18 Kernel for Xen4 needs testing

CentOS Errata and Enhancement Advisory 2013:X015 (Xen4CentOS) The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) ----------------------------- X86_64 ----------------------------- c0e393639da8712303ae87a379fbc7584b4a5b20229473c73e640653702da4db e1000e-2.5.4-3.10.20.2.el6.centos.alt.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

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,

Hi list After I install xen4.0 in my debian squeezz,it added the following lines into /boot/grub/grub.cfg ### BEGIN /etc/grub.d/20_linux_xen ### menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set

So... it is theorized that XSA-108 is why amazon is rebooting. Is there any way for me to know when this update hits CentOS5 or xen4centos6? Do we know that it is *not* included in one of the centos patches?

The new process for auto updates of grub upon kernel install is in the xen4centos testing repo. In order to test these as updates to an existing system, you can do this: 1. download the test repo file: http://dev.centos.org/centos/6/xen-c6-RC1/xen-c6-RC1.repo 2. Put it in /etc/yum.repos.d/ 3. Issue this command: yum --disablerepo=Xen4CentOS upgrade xen\* centos-release-xen (that should

On 02/27/2018 07:50 AM, John Vetter wrote: > Hi, > I'm trying to run an arbitrary Xen version (4.7.x) on a recent kernel (say, > 4.13.x) on CentOS 7. > What is the recommended way for doing this? (I am new to Xen and virtualization). > I tried the following: > 1. installed xen4centos. > 2. built linux kernel 4.13.x and installed it (using make install) > 3. built xen

On Tue, Feb 27, 2018 at 3:50 PM, John Vetter <john.vetter at mail.com> wrote: > Hi, > > I'm trying to run an arbitrary Xen version (4.7.x) on a recent kernel (say, > 4.13.x) on CentOS 7. > > What is the recommended way for doing this? (I am new to Xen and > virtualization). > > I tried the following: > 1. installed xen4centos. > 2. built linux kernel

On 12/02/2014 07:36 AM, Bob Ball wrote: >> -----Original Message----- >> From: Johnny Hughes >> On 12/01/2014 04:48 AM, Bob Ball wrote: >>> >>> [<ffffffff81575480>] panic+0xc4/0x1e1 >>> [<ffffffff81054836>] find_new_reaper+0x176/0x180 >>> [<ffffffff81055345>] forget_original_parent+0x45/0x2c0 >>>

> -----Original Message----- > From: Johnny Hughes > On 12/01/2014 04:48 AM, Bob Ball wrote: > > > > [<ffffffff81575480>] panic+0xc4/0x1e1 > > [<ffffffff81054836>] find_new_reaper+0x176/0x180 > > [<ffffffff81055345>] forget_original_parent+0x45/0x2c0 > > [<ffffffff81107214>] ? task_function_call+0x44/0x50 > >

Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself. Xlord -----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt at centos.org Subject: [CentOS-virt] grub-bootxen.sh

On 03/22/2017 09:35 AM, Alvin Starr wrote: > 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

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be

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:

CentOS Errata and Bug Fix Advisory 2013:X006 (Xen4CentOS) The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) ----------------------------- X86_64 ----------------------------- e1000e-2.4.14-3.4.54.1.el6.centos.alt.x86_64.rpm: 42e5a701631d08eca5a62c0f3cb1c9cc527fad358fe74e72f426dd4ce16e384a kernel-3.4.54-8.el6.centos.alt.x86_64.rpm:

On 12/01/2014 04:48 AM, Bob Ball wrote: > Hi all, > > Following instructions at http://wiki.centos.org/QaWiki/Xen4 to setup Xen on CentOS 6.4. Unfortunately after installing Xen and modifying the boot line there is a kernel panic during the boot process causing the host to enter a reboot loop. Console log attached. > > [<ffffffff81575480>] panic+0xc4/0x1e1 >

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

I've also had a few Xen systems grub entry issues. I'm not yet sure what triggers the events, but I do think there *may* be a correlation to the "/boot" part. I've found the Xen servers that have "/boot" before any of the the lines like "/boot/xen.gz" ended up missing complete grub entries. Not sure it's 100% true. Anyone else comment? Thanks PJ On

CentOS Errata and Bugfix Advisory 2013:X016 (Xen4CentOS) The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) ----------------------------- X86_64 ----------------------------- 8d240567c9b4d4a96460664df07e80e84447bd57f44fd495d56f5a73c5a18263 e1000e-2.5.4-3.10.23.2.el6.centos.alt.x86_64.rpm