All,
I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
[ OK ] Reached target Slices. Starting Create Static Device Nodes in /dev... [ OK ] Started iSCSI UserSpace I/O driver. [ OK ] Started Setup Virtual Console. Starting dracut cmdline hook... [ OK ] Started Apply Kernel Variables. [ OK ] Stopped iSCSI UserSpace I/O driver. Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same results.
I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing something wrong?
Config for the install is below:
# Kernel paths for install #kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" kernel = "/vmlinuz" #ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" ramdisk = "/initrd.img" extra="modules=loop,squashfs console=hvc0"
# Path to HDD and iso file disk = [ #'file:/vmdisk0,xvda,w' 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', ]
extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1"
# Network configuration vif = ['bridge=xenbr0']
#DomU Settings memory = 3072 name = "centos-8.2"
Thank you to all.
All,
Just wanted to check one last time before letting this thread die.
I am curious if anyone has gotten CentOS 8 to work in a PV Xen environment.
Thanks.
9f9dcad3f78905b03201@bcirpg.com wrote:
All,
I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
>[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same results.
I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing something wrong?
Config for the install is below:
># Kernel paths for install >#kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" >kernel = "/vmlinuz" >#ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" >ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', > ] > >extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1" > ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2"
Thank you to all. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Hi,
In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled.
I am curious why you are trying PV.
-yoctozepto
On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt centos-virt@centos.org wrote:
All,
Just wanted to check one last time before letting this thread die.
I am curious if anyone has gotten CentOS 8 to work in a PV Xen environment.
Thanks.
9f9dcad3f78905b03201@bcirpg.com wrote:
All,
I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
>[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same results.
I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing something wrong?
Config for the install is below:
># Kernel paths for install >#kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" >kernel = "/vmlinuz" >#ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" >ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', > ] > >extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1" > ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2"
Thank you to all. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
We tried to get CentOS 8 domU working in PV mode as well but did not have any success and ended up deploying it in HVM mode.
The reason OP have was lack of hardware support for HVM. This wasn't our rationale for wanting to run in PV mode. Our rationale was that we prefer to deploy CentOS 7 VMs on LVs which are formatted and deployed from an image on dom0 and don't have any partition table. This makes snapshotting, mounting, backing up and migrating very simple. We have written a number of scripts over the years that needed extensive modification to work with HVM VMs but in the end we ended up doing it because we couldn't get PV mode working. And we accepted that HVM is the future so might as well take the opportunity to adapt our ways.
If anyone manages to get PV mode working I'd still like to know.
Chris
On September 19, 2020 7:08:28 PM GMT+02:00, "Radosław Piliszek" radoslaw.piliszek@gmail.com wrote:
Hi,
In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled.
I am curious why you are trying PV.
-yoctozepto
On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt centos-virt@centos.org wrote:
All,
Just wanted to check one last time before letting this thread die.
I am curious if anyone has gotten CentOS 8 to work in a PV Xen
environment.
Thanks.
9f9dcad3f78905b03201@bcirpg.com wrote:
All,
I have successfully installed CentOS 7 on a PV environment, and have
been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV
environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the
distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk
for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
>[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same
results.
I even tried installing CentOS 7 clean, then upgrading in place (by
unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing
something wrong?
Config for the install is below:
># Kernel paths for install >#kernel =
"/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz"
>kernel = "/vmlinuz" >#ramdisk =
"/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img"
>ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w,
target=/dev/mapper/vg_1-virtualmachine',
> ] > >extra="ksdevice=
inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1"
> ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2"
Thank you to all. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
use the kernel from elrepo, it has xen support build in...
--- ------ Greetz
Am 19.09.2020 19:26, schrieb Chris Wik:
We tried to get CentOS 8 domU working in PV mode as well but did not have any success and ended up deploying it in HVM mode.
The reason OP have was lack of hardware support for HVM. This wasn't our rationale for wanting to run in PV mode. Our rationale was that we prefer to deploy CentOS 7 VMs on LVs which are formatted and deployed from an image on dom0 and don't have any partition table. This makes snapshotting, mounting, backing up and migrating very simple. We have written a number of scripts over the years that needed extensive modification to work with HVM VMs but in the end we ended up doing it because we couldn't get PV mode working. And we accepted that HVM is the future so might as well take the opportunity to adapt our ways.
If anyone manages to get PV mode working I'd still like to know.
Chris
On September 19, 2020 7:08:28 PM GMT+02:00, "Radosław Piliszek" radoslaw.piliszek@gmail.com wrote:
Hi,
In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled.
I am curious why you are trying PV.
-yoctozepto
On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt centos-virt@centos.org wrote:
All,
Just wanted to check one last time before letting this thread die.
I am curious if anyone has gotten CentOS 8 to work in a PV Xen environment.
Thanks.
9f9dcad3f78905b03201@bcirpg.com wrote: All,
I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
>[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same results.
I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing something wrong?
Config for the install is below:
># Kernel paths for install >#kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" >kernel = "/vmlinuz" >#ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" >ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', > ] > >extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1 [1]" > ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2"
Thank you to all.
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
-- Chris Wik Anu Internet Services www.cwik.ch [2] | www.anu.net [3]
Links:
[1] http://1.1.1.1 [2] http://www.cwik.ch [3] http://www.anu.net _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
the fastest/best mode is still pvh... use the kernel from elrepo it supports the mode
--- ------ Greetz
Am 19.09.2020 19:08, schrieb Radosław Piliszek:
Hi,
In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled.
I am curious why you are trying PV.
-yoctozepto
On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt centos-virt@centos.org wrote:
All,
Just wanted to check one last time before letting this thread die.
I am curious if anyone has gotten CentOS 8 to work in a PV Xen environment.
Thanks.
9f9dcad3f78905b03201@bcirpg.com wrote:
All,
I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running.
Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate.
My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel.
I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error:
>[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver...
I have also tried the CentOS 7 kernel Ram Disk with the same results.
I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel.
Is this is a bug, or is PV just not supported? Or am I doing something wrong?
Config for the install is below:
># Kernel paths for install >#kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" >kernel = "/vmlinuz" >#ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" >ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', > ] > >extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1" > ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2"
Thank you to all. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Christoph,
I understand this is the better option if HVM is available.. Im not sure how to make use of this kernel in a non-HVM, PV environment. I'm a little disturbed by the fact that there isnt PV support in CentOS 8, I hope it comes later so at least PVH becomes an option.
As for using this kernel in a PV only environment, the only route would be attempting an in place upgrade and try to install it as part of the upgrade. I am not willing to spend the time to do this and will use Centos 7 or other operating systems instead.
Thanks.
Christoph mangel@gmx.de wrote:
the fastest/best mode is still pvh... use the kernel from elrepo it supports the mode
Greetz
Am 19.09.2020 19:08, schrieb Radosław Piliszek: > Hi, > > In general, PV tends not to be supported in newer distribution > releases. > This is mostly due to HVM performance and flexibility nowadays, which > just was not the case back in the days when PV ruled. > > I am curious why you are trying PV. > > -yoctozepto > > On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via > CentOS-virt <centos-virt@centos.org> wrote: >> >> All, >> >> Just wanted to check one last time before letting this thread die. >> >> I am curious if anyone has gotten CentOS 8 to work in a PV Xen >> environment. >> >> >> Thanks. >> >> >> <9f9dcad3f78905b03201@bcirpg.com> wrote: >> >All, >> > >> >I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running. >> > >> >Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate. >> > >> >My understanding is that PV support is in the kernel, and that the distro of Linux shouldn&#39;t technically matter. But currently when trying to &quot;PXEBoot&quot; using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel. >> > >> >I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error: >> > >> >&gt;[ OK ] Reached target Slices. >> >&gt; Starting Create Static Device Nodes in /dev... >> >&gt;[ OK ] Started iSCSI UserSpace I/O driver. >> >&gt;[ OK ] Started Setup Virtual Console. >> >&gt; Starting dracut cmdline hook... >> >&gt;[ OK ] Started Apply Kernel Variables. >> >&gt;[ OK ] Stopped iSCSI UserSpace I/O driver. >> >&gt; Starting iSCSI UserSpace I/O driver... >> > >> >I have also tried the CentOS 7 kernel Ram Disk with the same results. >> > >> >I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel. >> > >> >Is this is a bug, or is PV just not supported? Or am I doing something wrong? >> > >> >Config for the install is below: >> > >> >&gt;# Kernel paths for install >> >&gt;#kernel = &quot;/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz&quot; >> >&gt;kernel = &quot;/vmlinuz&quot; >> >&gt;#ramdisk = &quot;/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img&quot; >> >&gt;ramdisk = &quot;/initrd.img&quot; >> >&gt;extra=&quot;modules=loop,squashfs console=hvc0&quot; >> >&gt; >> >&gt;# Path to HDD and iso file >> >&gt;disk = [ >> >&gt; #&#39;file:/vmdisk0,xvda,w&#39; >> >&gt; &#39;format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine&#39;, >> >&gt; ] >> >&gt; >> >&gt;extra=&quot;ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1&quot; >> >&gt; >> >&gt;# Network configuration >> >&gt;vif = [&#39;bridge=xenbr0&#39;] >> >&gt; >> >&gt;#DomU Settings >> >&gt;memory = 3072 >> >&gt;name = &quot;centos-8.2&quot; >> > >> >Thank you to all. >> >_______________________________________________ >> >CentOS-virt mailing list >> >CentOS-virt@centos.org >> >https://lists.centos.org/mailman/listinfo/centos-virt >> _______________________________________________ >> CentOS-virt mailing list >> CentOS-virt@centos.org >> https://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt@centos.org > https://lists.centos.org/mailman/listinfo/centos-virt
On 9/27/20 1:23 PM, 9f9dcad3f78905b03201--- via CentOS-virt wrote:
Christoph,
I understand this is the better option if HVM is available.. Im not sure how to make use of this kernel in a non-HVM, PV environment. I'm a little disturbed by the fact that there isnt PV support in CentOS 8, I hope it comes later so at least PVH becomes an option.
It's existentially possible for there to be PVH support without PV support. I don't know about the current implementation.
--Sarah
AFAIK the support for Xen would not be available in CentOS 8 (Red Hat has dropped the support). You can see the differences between the modes here: https://wiki.xen.org/wiki/Xen_Project_Software_Overview#Guest_Types PVH seems still to be the fastest one... You can use the kernel if you add the elrepo kernel repo to the host. You can find the informations how to do it here: https://elrepo.org/tiki/kernel-ml After adding the repo you can install the elrepo kernel like an other rpm package with "dnf install kernel-ml". AFAIK this kernel supports all the modes of xen (HVM, PV, PVH etc)
A short howto without details: 1. Start the DomU in HVM mode 2. Install the repo and the kernel-ml pkg 3. Make the kernel-ml as default kernel 4. Reboot the DomU in PVH mode.
The requirement for this is a xen hypervisor install with a grub for xen what support boot of such a DomU. The CentOS 8 pkgs from Steven repo ("Xen made easy" project) doesnt have such a grub bin. I've build it for me here and can share it with you if you want.
You can of course use CentOS 7 as far as you dont need a newer versions of the services/applications etc...
A simpler solution is to use Citrix XenServer but not all features are for free...
--- ------ Greetz
Am 27.09.2020 22:23, schrieb 9f9dcad3f78905b03201@bcirpg.com:
Christoph,
I understand this is the better option if HVM is available.. Im not sure how to make use of this kernel in a non-HVM, PV environment. I'm a little disturbed by the fact that there isnt PV support in CentOS 8, I hope it comes later so at least PVH becomes an option.
As for using this kernel in a PV only environment, the only route would be attempting an in place upgrade and try to install it as part of the upgrade. I am not willing to spend the time to do this and will use Centos 7 or other operating systems instead.
Thanks.