1

A student of mine stuck with a Fedora virtual machine under VirtualBox:

enter image description here

I do not even recognize what is going on here.

Do you have a clue what is going on? (on the left you see another VM that is broadcasted from me, a working instance of this VM)

Does this have anything to do with

https://access.redhat.com/solutions/658783 ?

Gergely
  • 794
  • 1
  • 10
  • 24
  • The kernel is crashing. Can't tell more than that. Does the same problem happen with 1) a current Fedora release like Fedora 33 and 2) the newest VirtualBox, if this isn't already that? – mattdm Feb 08 '21 at 19:31
  • This is the latest VirtualBox and for all the group but this student it works. Could this be a missing VT-x option in the BIOS? – Gergely Feb 09 '21 at 06:25
  • https://bugzilla.redhat.com/show_bug.cgi?id=1652845 search for "enable nesting". They consider this WONTFIX. I gave a Fedora 33 image to my student, I hope it will work. – Gergely Feb 09 '21 at 08:57

1 Answers1

0

http://bugzilla.redhat.com/show_bug.cgi?id=1652845

describes the problem, search for "enable nesting". They say that Red Hat won't fix this problem with Fedora 28.

mattdm's suggestion of creating a fresh Fedora VM, Fedora 33 worked.

Gergely
  • 794
  • 1
  • 10
  • 24
  • Is your student running on a Power system? It looks to be i686 in the screenshots. I'm not sure that's the same bug at all. In any case, I'm glad F33 worked. – mattdm Feb 09 '21 at 16:05
  • What do you mean by Power system? – Gergely Feb 10 '21 at 09:44
  • IBM Power CPU architecture. Note "ppc64le" in the bug descroption. See https://en.wikipedia.org/wiki/IBM_POWER_microprocessors. Not compatible with Intel/AMD systems and a different set of virtualization technologies. – mattdm Feb 10 '21 at 14:46
  • I see. She uses Intel/AMD. – Gergely Feb 11 '21 at 08:04
  • 1
    Yeah, so I think that's a different bug which happens to produce something that looks like similar symptoms. – mattdm Feb 11 '21 at 17:48