On 01/17/2018 05:00 AM, Dan wrote:
> 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
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
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
...@prgmr.com>
To: "Discussion about the virtualization on CentOS"
<centos-virt@centos.org>
Sent: 2018-01-05 12:39:21 AM
Subject: [CentOS-virt] Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot
in Xen PV mode
Problems start before any of the kaiser code executes, though it could
s
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
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
