Hi,
I'm currently working on my next Linux book, which will be an elementary course about CentOS administration. I'm using VirtualBox for all the installer screenshots.
Since CentOS has recently been upgraded to version 7.6, I thought I might as well base all book references on this version. So I downloaded the 7.6 1810 minimal ISO and started a fresh installation in VirtualBox.
I'm using a Swiss French keyboard layout (ch-fr or fr_CH-latin1), so one of the first things I do in the installer is replace the default French AZERTY keyboard (since I use the french language) by a swiss french QWERTZ layout.
Now when I reach this dialog in the installer and try do define my new layout, the slider in the selection window doesn't appear, and clicking on any of the first layouts doesn't do anything, so I'm basically stuck there.
I'm running OpenSUSE Leap 15.0 KDE on my workstation, so I tried the same thing with the previous CentOS 7.5 1804 minimal ISO, and the keyboard selection dialog works perfectly.
So my intuition would tell me that there's a nasty bug in the CentOS 7.6 installer. Maybe it went unnoticed, since most folks stick to the default keyboard layout selected in their language.
Any suggestions ?
Cheers,
Niki
On Thu, Jan 3, 2019 at 11:53 PM Nicolas Kovacs info@microlinux.fr wrote:
Hi,
I'm currently working on my next Linux book, which will be an elementary course about CentOS administration. I'm using VirtualBox for all the installer screenshots.
Since CentOS has recently been upgraded to version 7.6, I thought I might as well base all book references on this version. So I downloaded the 7.6 1810 minimal ISO and started a fresh installation in VirtualBox.
I'm using a Swiss French keyboard layout (ch-fr or fr_CH-latin1), so one of the first things I do in the installer is replace the default French AZERTY keyboard (since I use the french language) by a swiss french QWERTZ layout.
Now when I reach this dialog in the installer and try do define my new layout, the slider in the selection window doesn't appear, and clicking on any of the first layouts doesn't do anything, so I'm basically stuck there.
I'm running OpenSUSE Leap 15.0 KDE on my workstation, so I tried the same thing with the previous CentOS 7.5 1804 minimal ISO, and the keyboard selection dialog works perfectly.
So my intuition would tell me that there's a nasty bug in the CentOS 7.6 installer. Maybe it went unnoticed, since most folks stick to the default keyboard layout selected in their language.
Any suggestions ?
Cheers,
Niki
There are known issues with VirtualBox and RHEL (therefore CentOS) 7.6.
(1) https://forums.virtualbox.org/viewtopic.php?f=3&t=90103 (2) https://forums.virtualbox.org/viewtopic.php?f=3&t=90267
(1) is about the GuestAdditions, so this should not affect the installation. But you were most likely hit by (2). All the details are in that forum thread. In short, this is caused by a bug in the 7.6 kernel (see also https://bugs.centos.org/view.php?id=15570 ). It is possible that the next update to the kernel has the fix but this remains to be seen.
Akemi
Le 04/01/2019 à 09:14, Akemi Yagi a écrit :
There are known issues with VirtualBox and RHEL (therefore CentOS) 7.6.
(1) https://forums.virtualbox.org/viewtopic.php?f=3&t=90103 (2) https://forums.virtualbox.org/viewtopic.php?f=3&t=90267
(1) is about the GuestAdditions, so this should not affect the installation. But you were most likely hit by (2). All the details are in that forum thread. In short, this is caused by a bug in the 7.6 kernel (see also https://bugs.centos.org/view.php?id=15570 ). It is possible that the next update to the kernel has the fix but this remains to be seen.
OK, thanks for the clarification. Looks like this is it.
<rant> And I'm glad to begin chapter 2 of my Introduction To Linux with something like "Well, folks, unfortunately you can't select a custom keyboard layout in VirtualBox because the enterprise class Linux we talked about in chapter 1 has a bug in the kernel so for now the default keyboard layout will have to be sufficient.</rant>
:o)
Niki
On Fri, Jan 04, 2019 at 09:42:55AM +0100, Nicolas Kovacs wrote:
<rant> And I'm glad to begin chapter 2 of my Introduction To Linux with something like "Well, folks, unfortunately you can't select a custom keyboard layout in VirtualBox because the enterprise class Linux we talked about in chapter 1 has a bug in the kernel so for now the default keyboard layout will have to be sufficient.</rant>
I suppose this shows you how little Red Hat cares about using VirtualBox (product by their competition).
If I were running a VM on a linux system, I'd probably use KVM/qemu/libvirt. I'm sure that was exhaustively tested.
Le 04/01/2019 à 14:42, Jonathan Billings a écrit :
If I were running a VM on a linux system, I'd probably use KVM/qemu/libvirt. I'm sure that was exhaustively tested.
This is what I normally use.
My only use for VirtualBox is making screenshots of the installer, and sometimes for a quick test, because it's easy to make a VM clone in a single click.
Niki
On Fri, Jan 04, 2019 at 03:42:30PM +0100, Nicolas Kovacs wrote:
My only use for VirtualBox is making screenshots of the installer, and sometimes for a quick test, because it's easy to make a VM clone in a single click.
After some thought, it makes sense to use VirtualBox for teaching, since many people will probably start testing Linux using VirtualBox on Windows or macOS. Too bad the kernel bugs will prevent CentOS 7.6.1810 from being useful there.
Le 04/01/2019 à 15:55, Jonathan Billings a écrit :
After some thought, it makes sense to use VirtualBox for teaching, since many people will probably start testing Linux using VirtualBox on Windows or macOS. Too bad the kernel bugs will prevent CentOS 7.6.1810 from being useful there.
It's not that bad a problem. It only causes a problem with the installer when folks use a different keyboard layout than the default one. So the workaround is to use the default keyboard layout during installation, and then define a custom keyboard after the initial reboot using loadkeys and localectl, if folks need this (which is rare).
As for the rest, I'm only running it in multi-user.target mode for my Linux trainings. On the desktop, I'm running OpenSUSE Leap with KDE, and most of my students either have Windows 10 or Mac OS, with the odd Kubuntu or Linux Mint exception.
Cheers,
Niki
On 1/4/19 3:55 PM, Jonathan Billings wrote:
After some thought, it makes sense to use VirtualBox for teaching, since many people will probably start testing Linux using VirtualBox on Windows or macOS. Too bad the kernel bugs will prevent CentOS 7.6.1810 from being useful there.
It makes sense to use Centos on top of VirtualBox.
In fact I deliver a "Software-in-a-box" package consisting of a Centos installation on top of VirtualBox for my 1. semester students in software development.
The package includes all the necessary software for the courses 2 years ahead.
This removes most of my support problems keeping the Eclipse C/C++ environment stable on Windows and Mac, which I do not know very much and therefore does not offer support on.
|<
On Fri, Jan 4, 2019 at 5:43 AM Jonathan Billings billings@negate.org wrote:
On Fri, Jan 04, 2019 at 09:42:55AM +0100, Nicolas Kovacs wrote:
<rant> And I'm glad to begin chapter 2 of my Introduction To Linux with something like "Well, folks, unfortunately you can't select a custom keyboard layout in VirtualBox because the enterprise class Linux we talked about in chapter 1 has a bug in the kernel so for now the default keyboard layout will have to be sufficient.</rant>
I suppose this shows you how little Red Hat cares about using VirtualBox (product by their competition).
If I were running a VM on a linux system, I'd probably use KVM/qemu/libvirt. I'm sure that was exhaustively tested.
You guys are overreacting. :)
The bug was in a patch applied to the upstream (kernel.org) kernel version 4.17. Therefore any distribution running this kernel was affected -- including Fedora and SuSE. Red Hat backports upstream patches and this particular one was one of them.
By the way, there is a nicely written article about VirtualBox at RH:
https://developers.redhat.com/products/rhel/hello-world/#virtualbox
along with other VM technologies.
Akemi
Hallo, has anyone a working Centos 8.1 PXE Installation?
This is my problem http://realtechtalk.com/Centos_PXEBoot_NetInstall_Failure__Pane_is_dead-2012...
These hints and other don t work here.
Thanks Ralf
On 16/01/2020 10:50, Ralf Prengel wrote:
Hallo, has anyone a working Centos 8.1 PXE Installation?
This is my problem http://realtechtalk.com/Centos_PXEBoot_NetInstall_Failure__Pane_is_dead-2012...
All CentOS 8.1.1911 validations were done over PXE (machines reinstalled - physical or VMs). So that article mentions something specific about non distro kernel to have other kmod enabled. Is that what you need ? IF not, just ensure that you (obviously) boot anaconda through pxe with the kernel/initrd.img that *matches* the tree you're installing from (as yes, a kernel/initrd from 8.0.1905 wouldn't work to kick a 8.1.1911 install)
-----Ursprüngliche Nachricht----- Von: CentOS centos-bounces@centos.org Im Auftrag von Fabian Arrotin Gesendet: Freitag, 17. Januar 2020 14:28 An: centos@centos.org Betreff: Re: [CentOS] PXE ValueError: new value non-existent xfs filesystem is not valid as a default fs type
On 16/01/2020 10:50, Ralf Prengel wrote:
Hallo, has anyone a working Centos 8.1 PXE Installation?
This is my problem http://realtechtalk.com/Centos_PXEBoot_NetInstall_Failure__Pane_is_dea d-2012-articles
All CentOS 8.1.1911 validations were done over PXE (machines reinstalled - physical or VMs). So that article mentions something specific about non distro kernel to have other kmod enabled. Is that what you need ? IF not, just ensure that you (obviously) boot anaconda through pxe with the kernel/initrd.img that *matches* the tree you're installing from (as yes, a kernel/initrd from 8.0.1905 wouldn't work to kick a 8.1.1911 install)
Xxx Hallo, problem solved now. Problem obiously caused by a wrong path mixed kernel initrd versions.
Thanks Ralf Ralf Prengel Teamleiter Customer Care Comline AG Hauert 8 D-44227 Dortmund/Germany
Telefon:+49 231 97575 157 Mobil:+49 151 10831 157 Fax:+49 231 97575 257 E-Mail:ralf.prengel@comline.de
www.comline.de Vorstand: Stephan Schilling Aufsichtsratsvorsitzender: Nikolaus Bethlen HR Dortmund B 14570 USt.-ID-Nr. DE 124727422
-
Akemi Yagi -
Fabian Arrotin -
Jonathan Billings -
Klaus Kolle -
Nicolas Kovacs -
Ralf Prengel -
ralf.prengel＠comline.de