similar to: CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now also) with centosplus kernel 693.11.6.el7

On Sun, Jan 7, 2018 at 12:07 PM, David Groep <davidg at nikhef.nl> wrote: > Dear all, > > Maybe I'm the only one - so before filing it as a bug: it appears that > the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue > 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" > re-surface *also* with the CentOS PLUS kernel. But

To: CentOS mailing list <centos at centos.org> Thema: Re: [CentOS] Nvidia maximum pixel clock issue in kmod-nvidia-384.98 Dear All, Start BIOS Configuration and go to Graphic Configuration change On Board VGA to PCI Express x16 Automatic is VGA on Board Bis bald Alexander Am 09.01.2018 um 13:00 schrieb centos-request at centos.org: > Send CentOS mailing list submissions to >

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

Today we tried to update machines w/ Core2 Duo E6750 from 3.10.0-693.11.1.el7.centos.plus to 3.10.0-693.11.6.el7.centos.plus and the machines did not boot due to a kernel panic. Before we dig any further I wanted to know if the 11.6 kernel has been tested on old hardware, too, or if the problem is well known but not documented (yet). Thank you in advance! Gerhard Schneider -- Gerhard

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

Linux.file_owner is not used by any other function, so remove it. Linux.is_file_owned is only used when removing kmod-xenpv on old RHEL releases, and so is only required to work for RPM. The old file_owner/is_file_owned functions were completely broken. This replaces them with a simpler, working implementation that only covers the narrow use case of removing kmod-xenpv non-owned directories.

/usr/lib/xen/bin/qemu-system-i386 doesn''t exist on ARM. We need to check if the file exists/is executable and starts it. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/hotplug/Linux/init.d/xencommons | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tools/hotplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons index

In doing an update of centos 5.2 this morning, I observed that the old gecko-libs dependency issue caused yum update to fail because it was required by nspluginwrapper (x64_86), devhelp, yelm and firefox. Also, a firefox (x64_86) showed the red hat splash screen rather than centos. Manual installation of affected rpms using --nodeps (I don't advise this) did not apear to impair the

On Thu, 2015-01-22 at 13:02 +0100, Stefan Bader wrote: > That one modifies xen-init-list to look at domains managed by the xl namespace. > This additionally works around a bug in xl which will report a syntax error when > "xl list -l" is called while domains in a different namespace exist. Which is > the case when libvirt is used to start them. FWIW in 4.5 xl is supposed to

Hi, Me and another sysadmin has independently been researching a problem where DomU randomly locks (Can’t reach it via xl console, no ping / SSH connection, shown as stuck in running-state in xentop) on two of our separate machines (installed completely independently): Dom0: Debian 7.0 with Xen version: 4.1.4 and xen-utils 4.1.4-3+deb7u1 Debian 7.1 with Xen version: 4.1 DomU: 7.0 7.1(.3)

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

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi guys, I hope you can help me on this issue with kvm/libvirt: using this command to install a kvm virtual machine: virt-install --connect qemu:///system \ --name p3k0401 \ --ram 2048 \ --file //dev/VolGroup01/p3k0401logvol \ --accelerate \ -s 10 \ --nographics \ --hvm \ --location='http://10.1.4.80' I get: Starting install... Retrieving file vmlinuz... | 1.8 MB 00:00

Hello, I am running two dom0s, one on CentOS 5 with Xen 4.1.2 (from Gitco) and the other one on CentOS 6 with Xen 4.2.4 (from Xen4CentOS). I host one LVM based domU on both from the same template (CentOS 6 PV) with the same Xen config (see below). However, the domU on Xen 4.1 reports itself as Xen PV while the domU on Xen4CentOS reports itself as Xen HVM. == First domU == virt-what and cPanel

CentOS Errata and Enhancement Advisory 2008:0274 Upstream details at : https://rhn.redhat.com/errata/RHEA-2008-0274.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 478ae0ee8579ef930b92d966f55915f1 kmod-xenpv-0.1-9.el5.i686.rpm e46e1df0f5f1f9ad25db97126e3c6f25 kmod-xenpv-PAE-0.1-9.el5.i686.rpm Source:

26470:acaf29203cf9 "tools+stubdom: install under /usr/local by default" moved more stuff under /usr/local than was desirable. In particular SYSCONFIG_DIR (configuration for initscripts) moved to /usr/local/etc/{sysconfig,defaults} while the initscripts themselves (correctly) remained in /etc/init.d. Moving /etc/xen/scripts breaks the udev bakcned rules file. Lastly stuff under /var was

CentOS Errata and Enhancement Advisory 2008:0274 Upstream details at : https://rhn.redhat.com/errata/RHEA-2008-0274.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: db039012348802382642df92fbadfbf1 kmod-xenpv-0.1-9.el5.x86_64.rpm Source: 4e9d7cad6dd2ad7c1b31669d404df7a9 xenpv-0.1-9.el5.src.rpm -- Karanbir Singh

Red Hat no longer maintains the i386 kernel for RHEL 7.4.? We have been using a modified kernel until this latest meltdown / spectre? release (*kernel-3.10.0-693.11.6.el7*). This latest release does not build on i386/i686 and we can't figure out how to make it work.? Build try: https://buildlogs.centos.org/c7.1708.u.i386/kernel/20180109171431/3.10.0-693.11.6.el7.centos.plus.i386/ SRPM:

Don't remove the Processor and Intelppm nodes since that just breaks the device driver. The only remaining node being removed by the original code was "rhelscsi" (the xenpv-win driver). I changed this so that instead of deleting the whole node, it simply disables that driver. If you look at RHBZ#737600, it's not even clear that deleting nodes was the right fix for anything. I