Steve Gomez
2019-Feb-14 22:32 UTC
[CentOS] Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
Ran into this rather frustrating bug when working with VBOX on a Windows 10 host. It should come as no surprise that I would hit this bug when installing CentOS, and also with RHEL 7 Server with GUI (since you get the same kernel). Based on information from your bug list, I was fortunately able to workaround the trouble with: wget https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm wget https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm yum -y localinstall kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm yum -y localinstall kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm However, the bug lists seem to refer only to issues with VirtualBox. I have experienced the same symptom when installing on a "hardware" system (no hypervisor). The same commands above also provide a workaround here, but thought the flag should be raised for CentOS and RHEL that it doesn't seem to be just VBOX. Perhaps the priority of this issue should be raised further up the pole since I can't imagine it being a good experience for someone who doesn't know how to dig through a problem like this. The average bear would install something else and move on. In any case, thank you for the patch information. Look forward to a "real" fix soon. Other than that I'm really liking CentOS 7. SG
Akemi Yagi
2019-Feb-14 22:58 UTC
[CentOS] Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
On Thu, Feb 14, 2019 at 2:32 PM Steve Gomez <steve.gomez.sg79 at gmail.com> wrote:> > Ran into this rather frustrating bug when working with VBOX on a Windows 10 > host. It should come as no surprise that I would hit this bug when > installing CentOS, and also with RHEL 7 Server with GUI (since you get the > same kernel). Based on information from your bug list, I was fortunately > able to workaround the trouble with: > > wget > https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > wget > https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > > yum -y localinstall kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > yum -y localinstall kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > > However, the bug lists seem to refer only to issues with VirtualBox. I > have experienced the same symptom when installing on a "hardware" system > (no hypervisor). The same commands above also provide a workaround here, > but thought the flag should be raised for CentOS and RHEL that it doesn't > seem to be just VBOX. > > Perhaps the priority of this issue should be raised further up the pole > since I can't imagine it being a good experience for someone who doesn't > know how to dig through a problem like this. The average bear would > install something else and move on. > > In any case, thank you for the patch information. Look forward to a "real" > fix soon. Other than that I'm really liking CentOS 7. > > SGAs noted in the CentOS bug report you referenced ( https://bugs.centos.org/view.php?id=15570 ), I filed a report upstream ( https://bugzilla.redhat.com/show_bug.cgi?id=1658669, marked private). In that RHBZ, they were able to reproduce it without VirtualBox. Therefore they are aware this is not just a VBox problem. The fix has been added to kernel-3.10.0-984.el7, meaning it will be in the EL 7.7 kernel. Now there is a separate RHBZ for "Z-Stream" for the same issue. This means that the fix will be ported to the current series (EL 7.6). Unfortunately I have no access to this BZ, so cannot tell the progress there. Once it is fixed in RHEL, CentOS will inherit it. Akemi
Akemi Yagi
2019-Feb-14 23:03 UTC
[CentOS] Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
On Thu, Feb 14, 2019 at 2:58 PM Akemi Yagi <amyagi at gmail.com> wrote:> > On Thu, Feb 14, 2019 at 2:32 PM Steve Gomez <steve.gomez.sg79 at gmail.com> wrote: > > > > However, the bug lists seem to refer only to issues with VirtualBox. I > > have experienced the same symptom when installing on a "hardware" system > > (no hypervisor). The same commands above also provide a workaround here, > > but thought the flag should be raised for CentOS and RHEL that it doesn't > > seem to be just VBOX. > > As noted in the CentOS bug report you referenced ( > https://bugs.centos.org/view.php?id=15570 ), I filed a report upstream > ( https://bugzilla.redhat.com/show_bug.cgi?id=1658669, marked > private). In that RHBZ, they were able to reproduce it without > VirtualBox. Therefore they are aware this is not just a VBox problem. > The fix has been added to kernel-3.10.0-984.el7, meaning it will be in > the EL 7.7 kernel. > > Now there is a separate RHBZ for "Z-Stream" for the same issue. This > means that the fix will be ported to the current series (EL 7.6). > Unfortunately I have no access to this BZ, so cannot tell the progress > there. Once it is fixed in RHEL, CentOS will inherit it. > > AkemiI added the following note to bug 15570: "The problem is not unique to VirtualBox. It can be reproduced _without_ VBox." Akemi
Reasonably Related Threads
- Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
- using vbox driver hypervisor support
- how can I use libvirt to connect vbox
- with current libvirt git virsh expects vbox, refuses kvm define
- Cannot obtain CPU freq during vbox machine creation