similar to: Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode

A CentOS 6.9 domU with kernel 2.6.32-696.18.7.el6.x86_64 also fails to boot on a CentOS 6.9 dom0 with kernel 4.9.63-29.el6.x86_64 and xen 4.4.4-34.el6.x86_64 Xen logs lines like these (among others): /var/log/xen/xend.log:[2018-01-05 17:55:45 2357] WARNING (XendDomainInfo:583) Could not unpause blktap disk: ('unpause', '-p11520', '-m4') failed (5632 )

I can confirm the issue with 2.6.32-696.18.7.el6.x86_64, but mine looks alittle different... Maybe because i'm using pvgrub. ============= Init TPM Front ================ Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT Tpmfront:Info Shutting down tpmfront close blk: backend=/local/domain/0/backend/vbd/14/51712 node=device/vbd/51712

Noticed C6 had a kernel update on Friday. 2.6.32-696.18.7.el6.x86_64 What is the flag in /proc/cpuinfo that indicates the KPTI patch for Meltdown CVE-2017-5754 for C6? Some distros are using "kaiser" some like Fedora are using "pti". Also noticed some (like Fedora) are displaying "cpu_insecure" under the bugs: heading of cpuinfo.

CentOS Errata and Security Advisory 2018:0008 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0008 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 68a63bc74c6c079a43edf5e3f967472484e4715259485f768d091b4cc44e232e kernel-2.6.32-696.18.7.el6.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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

Is this now fixed in the latest release by updating the hypervisor, the same as CentOS 7? Or does this require something further? I came across https://access.redhat.com/solutions/3312501 which seems to suggest Redhat are working on resolving the issue, so if that's the case then maybe the solution implemented by CentOS is not the best option? Kind Regards, Dan -------------- next part

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 >

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine