On 01/05/2018 05:26 PM, Shaun Reitan wrote:
> 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
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
Broken!
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.10.0-693.11.6.el7.x86_64
(buil...@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-16)
Forgot to post my domU config (xm/xend format):
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
name = 'domU'
bootloader = '/usr/bin/pygrub'
extra = '(hd0,0)/grub/menu.lst'
maxmem = 4096
memory = 1024
vcpus=2
vif = [
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
On 5 January 2018 at 12:53, Chris Olson wrote:
> How does the latest Intel flaw relate to CentOS 6.x systems
> that run under VirtualBox hosted on Windows 7 computers? Given
> the virtual machine degree of separation from the hardware, can
Supposedly a virtual machine
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Chris Olson
Subject: [CentOS] Intel Flaw
>How does the latest Intel flaw relate to CentOS 6.x systems that run under
>VirtualBox
> hosted on Windows 7 computers?
My computer is an much older AMD Athlon
How does the latest Intel flaw relate to CentOS 6.x systems
that run under VirtualBox hosted on Windows 7 computers? Given
the virtual machine degree of separation from the hardware, can
this issue actually be detected and exploited in the operating
systems that run virtually? If there is a slow
> On Jan 5, 2018, at 9:02 AM, Johnny Hughes wrote:
>
> I have released everything for CentOS-6 that has been released upstream
> in RHEL source code.
>
> I will continue to do so when they release new sources.
>
> NOTE: We will NOT be releasing anything for CentOS versions
I have released everything for CentOS-6 that has been released upstream
in RHEL source code.
I will continue to do so when they release new sources.
NOTE: We will NOT be releasing anything for CentOS versions before
CentOS-6 (ie, CentOS-2.1, 3.x, 4.x, 5.x releases in vault that are past
EOL
On Thu, Jan 4, 2018 at 7:12 PM, Sarah Newman wrote:
> On 01/04/2018 10:49 AM, Akemi Yagi wrote:
>> On Thu, Jan 4, 2018 at 9:51 AM, wrote:
>>
>>> Please patch the CentOS-virt Kernel to fix the
>>> Kernel Side-Channel Attacks vulnerabilities.
>>>
>>> The latest
Send CentOS-announce mailing list submissions to
centos-annou...@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
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
13 matches
Mail list logo