sudo dnf system-upgrade download --refresh --releasever=33
...
Errors during downloading metadata for repository 'virtualbox':
- Status code: 404 for http://download.virtualbox.org/virtualbox/rpm/fedora/33/x86_64/repodata/repomd.xml (IP: 2.23.8.99)
Error: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
...
Error:
Problem: package VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64 requires python(abi) = 3.8, but none of the providers can be installed
- python3-3.8.6-1.fc32.x86_64 does not belong to a distupgrade repository
- problem with installed package VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64
It ought to come soon, though we don't have a timeline. Give the devs a couple months or so. Check this page: https://www.virtualbox.org/wiki/Linux_Downloads. When Fedora 33 shows up, then try the update again.
I just upgraded Fedora guest to 33 from 32 on a Linux host without issue. That is, I have a desktop. I just ran it from the Fedora "new version 33 is available" download and install.
Linux arch-me 5.9.2-arch1-1 #1 SMP PREEMPT Thu, 29 Oct 2020 17:01:28 +0000 x86_64 GNU/Linux
There are a lot of errors in the journal including a gnome-software coredump, and Rythmbox plays music all chopped up. Not sure what else doesn't work. I'm willing to test this Fedora 33 guest if it will be helpful.
Is there any action on official Fedora 33 support? I see a few methods on how to "get it working", but so far no official downloads or repos for it. With Fedora 34 due out in May, and thus the EOL for 32, what is the future for official support?
al609 wrote:Is there any action on official Fedora 33 support? I see a few methods on how to "get it working", but so far no official downloads or repos for it. With Fedora 34 due out in May, and thus the EOL for 32, what is the future for official support?
I suspect there will be a F33 RPM with the next release (6.1.18 or whatever). It's been almost 2 months since 6.1.16, and the last couple 6.1 releases have been about 1.5 months apart, so it should be soon.
Just found that there is trouble getting VB to work with the 5.10 kernel (see https://www.virtualbox.org/ticket/20055 ), and the next F33 kernel will be 5.10, so the delay may be just as well. Don't know if this issue is what's causing it.
Edit: Confirmed by running 5.10.6 which was just submitted for F33 stable that the VBox kernel modules do not build with it, so will have to stay on 5.9.16 to keep VBox running until a new version is released.
FYI, kernel 5.10.7 has been pushed to both F32 and F33 at this point. For me, that translates into no more updates on F32 with 5.9 kernel until the next version is released with these problems fixed. Hopefully this project is still being actively maintained, as we have not seen an update for some time.
al609 wrote:FYI, kernel 5.10.7 has been pushed to both F32 and F33 at this point. For me, that translates into no more updates on F32 with 5.9 kernel until the next version is released with these problems fixed.
An update won't remove the kernel you're currently running, so during the update just make sure you're running the kernel you want to keep (probably 5.9.16).
Edit: In case the 5.9.16 kernel is accidentally removed, the signed packages can be downloaded from
Maybe the title of this thread should be changed, or a new thread should be split off, since the 5.10 kernel issue affects both F32 and F33 now (since both have a stable 5.10.7 kernel).