I've tried to install Fedora 33 Workstation on VirtualBox 6.1.16 installed on a 64-bit Windows 10 Professional 20H2 (10.0.19042.685) host system. Unfortunately the live installer (Anaconda) gets stuck at the very first dialog of choosing language and then crashes. This is what I see when I try to run it manually from a terminal: [liveuser@localhost-live applications]$ /usr/bin/liveinst Starting installer, one moment... anaconda 33.25.4-1.fc33 for Fedora 33 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2) * when reporting a bug add logs from /tmp as separate text/plain attachments Anaconda received signal 11!. /usr/lib64/python3.9/site-packages/pyanaconda/_isys.so(+0x13c7)[0x7f8e713b53c7] /lib64/libc.so.6(+0x3dc50)[0x7f8e803a7c50] /lib64/libc.so.6(+0x1625b5)[0x7f8e804cc5b5] /lib64/libc.so.6(+0x6e4a8)[0x7f8e803d84a8] /lib64/libc.so.6(+0x7efc5)[0x7f8e803e8fc5] /lib64/libglib-2.0.so.0(g_vasprintf+0x1f)[0x7f8e7274f27f] /lib64/libglib-2.0.so.0(g_strdup_vprintf+0x2d)[0x7f8e7272759d] /lib64/libglib-2.0.so.0(g_prefix_error+0xac)[0x7f8e726f40ac] /lib64/libgio-2.0.so.0(g_unix_connection_send_credentials+0x18c)[0x7f8e724b712c] /lib64/libgio-2.0.so.0(+0xf9559)[0x7f8e724e9559] /lib64/libgio-2.0.so.0(g_bus_get_sync+0x9c)[0x7f8e724f47fc] /lib64/libgio-2.0.so.0(+0x10e03e)[0x7f8e724fe03e] /lib64/libgio-2.0.so.0(g_initable_new_valist+0x92)[0x7f8e72463232] /lib64/libgio-2.0.so.0(g_initable_new+0x99)[0x7f8e724632e9] /lib64/libgio-2.0.so.0(g_dbus_proxy_new_for_bus_sync+0xfd)[0x7f8e724fff1d] /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so(+0x26f8)[0x7f8e65dff6f8] /lib64/libglib-2.0.so.0(+0x51117)[0x7f8e72706117] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x167)[0x7f8e72706ff7] /lib64/libglib-2.0.so.0(+0xa2b88)[0x7f8e72757b88] /lib64/libglib-2.0.so.0(g_main_loop_run+0x7b)[0x7f8e727066cb] [New LWP 5659] [New LWP 5660] [New LWP 5744] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f8e80437d0f in wait4 () from /lib64/libc.so.6 Saved corefile /tmp/anaconda.core.5652 [Inferior 1 (process 5652) detached] [liveuser@localhost-live applications]$ In addition to the official ISO of Fedora 33 I’ve also tried the F33-20201201 respin ISO. But it has similar troubles. It can crash even before its window has appeared: [liveuser@localhost-live ~]$ /usr/bin/liveinst Starting installer, one moment... anaconda 33.25.4-1.fc33 for Fedora 33 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2) * when reporting a bug add logs from /tmp as separate text/plain attachments Anaconda received signal 11!. /usr/lib64/python3.9/site-packages/pyanaconda/_isys.so(+0x13c7)[0x7f7af017b3c7] /lib64/libc.so.6(+0x3da60)[0x7f7aff17fa60] /lib64/libc.so.6(+0x1623b5)[0x7f7aff2a43b5] /lib64/libc.so.6(+0x6e2a8)[0x7f7aff1b02a8] /lib64/libc.so.6(+0x7edc5)[0x7f7aff1c0dc5] /lib64/libglib-2.0.so.0(g_vasprintf+0x23)[0x7f7af152bf73] /lib64/libglib-2.0.so.0(g_strdup_vprintf+0x31)[0x7f7af14ff561] /lib64/libglib-2.0.so.0(g_prefix_error+0xb0)[0x7f7af14cb4d0] /lib64/libgio-2.0.so.0(g_unix_connection_send_credentials+0x18c)[0x7f7af128a5ac] /lib64/libgio-2.0.so.0(+0x100839)[0x7f7af12bd839] /lib64/libgio-2.0.so.0(g_bus_get_sync+0xa4)[0x7f7af12c8d84] /lib64/libgio-2.0.so.0(+0x1158be)[0x7f7af12d28be] /lib64/libgio-2.0.so.0(g_initable_new_valist+0x9a)[0x7f7af1234dea] /lib64/libgio-2.0.so.0(g_initable_new+0x9d)[0x7f7af1234e9d] /lib64/libgio-2.0.so.0(g_dbus_proxy_new_for_bus_sync+0x105)[0x7f7af12d47e5] /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so(+0x2a48)[0x7f7ae8ba6a48] /lib64/libglib-2.0.so.0(+0x528ab)[0x7f7af14dd8ab] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x16f)[0x7f7af14de7ef] /lib64/libglib-2.0.so.0(+0xa55d8)[0x7f7af15305d8] /lib64/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7f7af14ddeb3] [New LWP 2486] [New LWP 2487] [New LWP 2587] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f7aff20fb0f in wait4 () from /lib64/libc.so.6 Saved corefile /tmp/anaconda.core.2479 [Inferior 1 (process 2479) detached] [liveuser@localhost-live ~]$
Please also see my discussion of this issue in the Fedora forum: https://ask.fedoraproject.org/t/cant-install-fedora-33-workstation-on-virtualbox-6-1-16/11013
Created attachment 1738806 [details] the /tmp/anaconda.log file Attaching the /tmp/anaconda.log file when trying the official Fedora 33 Workstation ISO. Not respin.
I've also prepared a zx compressed core dump file of the Anaconda but it's a little bit larger than the maximum attachment size allowed here. So I've uploaded it into a 3rd party site: https://dropmefiles.com/MC6qJ It will be available there for a about a week.
Created attachment 1738808 [details] the /tmp/dbus.log file The /tmp/dbus.log file that could be related since it has the same modification time as the a anaconda.log and anaconda.core.2256
Created attachment 1738809 [details] the /tmp/lvm.log file The /tmp/lvm.log file that could be related since it has the same modification time as the a anaconda.log and anaconda.core.2256
Hello Rostislav Krasny, thank you for the report! Two points: Sadly almost all of Anaconda crash reports from within VirtualBox are unresolvable. I do not know the details, but something does not play nice with kernel. Usually this manifests as failures in the rest of the environment, such as Python crashing (this one), D-Bus failing to transmit, random memory corruption in other processes etc. Actually, if you have any details about how you set up the VirtualBox VM, that would be nice to know - there are articles for Fedora in VirtualBox (eg. [1]) that don't complain about crashes, so it might be just some misconfiguration. To let us diagnose what's going on, please attach the logs. You can find them during the installation in /tmp or on the installed system in /var/log/anaconda/. The most interesting one is going to be journal, but grabbing everything with log in file name and making an archive would be even better. [1] https://itsfoss.com/install-fedora-in-virtualbox/
I missed the link to ask fedora, so followed that and did some more digging. On the server (netinstall, boot) image, we appear to have all the VirtualBox kmods available: vboxvideo, vboxguest, vboxsf. So that should be fine, and is not. Ultimately, that's not really an Anaconda thing, so unless the logs appear and something else is apparent from them, there isn't anything to do :(
Created attachment 1739449 [details] Content of /var/log/anaconda/ Content of /var/log/anaconda/ per Vladimír Slávik request. Don't forget that this was taken in another run.
looks like the bug is since fedora 31 at least, but did not receive much attention. https://bugzilla.redhat.com/show_bug.cgi?id=1773919
From the backtrace: /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so(+0x2a48)[0x7f7ae8ba6a48] The libpk-gtk-module.so library belongs to PackageKit. Reassigning.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.