Can't upgrade to Fedora 34
Can't upgrade to Fedora 34
Fedora 33 VM was running perfect for months and did the standard upgrade procedure to Fedora 34 (dnf update/sudo dnf system-upgrade download --releasever=34). When the new machine starts, it goes to a large screen for a second that reverts back to the smaller login screen and hangs forever.
I've tried changing the settings like 3d acceleration as some posts suggested. I've had issues in the past with the number of processors and other settings and nothing happens as well as other settings. Tried an older kernel from the boot screen and even the rescue choice fails. I can install Fedora 34 to a new machine from .iso and it boots just fine but this machine will not update and have tried several times.
log is attached. I have 32gb assigned to the machine but that's not going to be a problem as 128gb is installed.
I've tried changing the settings like 3d acceleration as some posts suggested. I've had issues in the past with the number of processors and other settings and nothing happens as well as other settings. Tried an older kernel from the boot screen and even the rescue choice fails. I can install Fedora 34 to a new machine from .iso and it boots just fine but this machine will not update and have tried several times.
log is attached. I have 32gb assigned to the machine but that's not going to be a problem as 128gb is installed.
- Attachments
-
- f34-2021-04-30-07-10-51.zip
- (30.24 KiB) Downloaded 25 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Can't upgrade to Fedora 34
You don't have Hyper-V problems in the Windows 10 host, good. The VM has only one processor, I see you were changing processor count as a troubleshooting step.
I don't see anything wrong in the VM operation for the 31 seconds the VM was on, and the Virtualbox environment seems to keep running OK. I lean towards this being an in-the-OS problem.
I would suggest troubleshooting this as a bunged-up update rather than a Virtualbox problem. See if the web has anything to say about how to fix Fedora when a version upgrade goes south.
I don't see anything wrong in the VM operation for the 31 seconds the VM was on, and the Virtualbox environment seems to keep running OK. I lean towards this being an in-the-OS problem.
I would suggest troubleshooting this as a bunged-up update rather than a Virtualbox problem. See if the web has anything to say about how to fix Fedora when a version upgrade goes south.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Can't upgrade to Fedora 34
You're using VirtualBox 6.1.18 on the host, and the Fedora 34 installation seems to bring its own version of the VirtualBox Guest Additions (GA) 6.1.20_Fedora. I'd suggest to first upgrade VirtualBox on the host to 6.1.22. If the Fedora 34 guest is working afterwards, uninstall the Fedora GA 6.1.20 and install the VirtualBox GA 6.1.22. Watch for error messages, especially regarding missing kernel headers, to ensure that the GA installation really succeeds.
Re: Can't upgrade to Fedora 34
I'm beginning to think this is a OS problem.
Thanks for pointing out I was running 6.1.18, I've upgraded. I did check that before I upgraded and I must have done it wrong by doing "about virtualbox" rather than "check for updates" Oops! I upgraded to 6.1.22 and tried to update Fedora 24, no luck and then installed 6.1.20 as it was mentioned but no luck.
Thanks for your suggestions and I'm ok sticking with Fedora 33 a while and it might be easier to rebuild the machine from scratch (I can install 34 from on a new, clean VM). Besides, the rebuild will give me another chance to see if my install and config scripts are working correctly.
Thanks for pointing out I was running 6.1.18, I've upgraded. I did check that before I upgraded and I must have done it wrong by doing "about virtualbox" rather than "check for updates" Oops! I upgraded to 6.1.22 and tried to update Fedora 24, no luck and then installed 6.1.20 as it was mentioned but no luck.
Thanks for your suggestions and I'm ok sticking with Fedora 33 a while and it might be easier to rebuild the machine from scratch (I can install 34 from on a new, clean VM). Besides, the rebuild will give me another chance to see if my install and config scripts are working correctly.
Re: Can't upgrade to Fedora 34
I have also upgraded Fedora to 34, and VBox screen is frozen. I started with:
- Fedora 33 updated to the latest
- VBox host on Win10 v.6.1.22 with same extension pack
I downgraded Win10 VBox to 6.1.20 (and extensions), but that didn't help
From Fedora's boot menu, I tried to run Fedora 33, the same problem.
When I run dmesg on that Fedora, I see the VBox guest as 6.1.20. I am not sure if I can upgrade it to 22, as yum tells that this is the latest. Potentially relevant errors / logs are:
[ 12.651406] 01:54:34.192305 main 6.1.20_Fedora r143896 started. Verbose level = 0
[ 12.652716] 01:54:34.193501 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 46.312314] 01:55:09.368145 main VBoxService 6.1.20_Fedora r143896 (verbosity: 0) linux.amd64 (Apr 23 2021 00:00:00) release log
[ 46.329231] 01:55:09.385378 main 6.1.20_Fedora r143896 started. Verbose level = 0
[ 46.330565] 01:55:09.386652 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 46.332123] 01:55:09.388173 main Error: Failed to become guest control master: VERR_RESOURCE_BUSY
[ 46.332830] 01:55:09.388886 main Error: Service 'control' failed to initialize: VERR_RESOURCE_BUSY
[ 46.333266] 01:55:09.389514 main Session 0 is about to close ...
[ 46.333603] 01:55:09.389849 main Stopping all guest processes ...
[ 46.333906] 01:55:09.390170 main Closing all guest files ...
[ 46.334113] 01:55:09.390491 main Ended.
I cannot say that I see any other potential errors in dmesg output, but I am rather far from being an expert. Also, on that first output line there is a "Verbose level = 0." Is there a way to bump up that log level, would that be beneficial?
- Fedora 33 updated to the latest
- VBox host on Win10 v.6.1.22 with same extension pack
I downgraded Win10 VBox to 6.1.20 (and extensions), but that didn't help
From Fedora's boot menu, I tried to run Fedora 33, the same problem.
When I run dmesg on that Fedora, I see the VBox guest as 6.1.20. I am not sure if I can upgrade it to 22, as yum tells that this is the latest. Potentially relevant errors / logs are:
[ 12.651406] 01:54:34.192305 main 6.1.20_Fedora r143896 started. Verbose level = 0
[ 12.652716] 01:54:34.193501 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 46.312314] 01:55:09.368145 main VBoxService 6.1.20_Fedora r143896 (verbosity: 0) linux.amd64 (Apr 23 2021 00:00:00) release log
[ 46.329231] 01:55:09.385378 main 6.1.20_Fedora r143896 started. Verbose level = 0
[ 46.330565] 01:55:09.386652 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 46.332123] 01:55:09.388173 main Error: Failed to become guest control master: VERR_RESOURCE_BUSY
[ 46.332830] 01:55:09.388886 main Error: Service 'control' failed to initialize: VERR_RESOURCE_BUSY
[ 46.333266] 01:55:09.389514 main Session 0 is about to close ...
[ 46.333603] 01:55:09.389849 main Stopping all guest processes ...
[ 46.333906] 01:55:09.390170 main Closing all guest files ...
[ 46.334113] 01:55:09.390491 main Ended.
I cannot say that I see any other potential errors in dmesg output, but I am rather far from being an expert. Also, on that first output line there is a "Verbose level = 0." Is there a way to bump up that log level, would that be beneficial?
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Can't upgrade to Fedora 34
Regarding the version numbers, the VirtualBox Guest Additions (GA) are allowed to be somewhat older, because that happens all the time during the typical VirtualBox update procedure, where you update VirtualBox (and the VirtualBox Extension Pack) on the host first, then start the guest with the apparent version mismatch, and update the GA later on.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Can't upgrade to Fedora 34
I don't know if it would be beneficial, but you'd have to start the VBoxService with "-l <logfilename> -vvv".Jacek_ wrote:Also, on that first output line there is a "Verbose level = 0." Is there a way to bump up that log level, would that be beneficial?
Re: Can't upgrade to Fedora 34
Thank you fth0.
I upgraded GA to v.1.6.22, but that didn't help (actually now mouse is gone, but the screen is stuck in the same place). I also run YUM hoping for some good Fedora updates. I run that service with -vvv and here is the output:
I upgraded GA to v.1.6.22, but that didn't help (actually now mouse is gone, but the screen is stuck in the same place). I also run YUM hoping for some good Fedora updates. I run that service with -vvv and here is the output:
20:50:03.540165 main VBoxService 6.1.22 r144080 (verbosity: 5) linux.amd64 (Apr 28 2021 18:43:39) release log 20:50:03.540167 main Log opened 2021-05-05T20:50:03.540159000Z 20:50:03.540275 main OS Product: Linux 20:50:03.540331 main OS Release: 5.11.17-300.fc34.x86_64 20:50:03.540361 main OS Version: #1 SMP Wed Apr 28 14:21:28 UTC 2021 20:50:03.540389 main Executable: /opt/VBoxGuestAdditions-6.1.22/sbin/VBoxService 20:50:03.540390 main Process ID: 2113 20:50:03.540391 main Package type: LINUX_64BITS_GENERIC 20:50:03.540766 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-interval not found 20:50:03.540816 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-min-adjust not found 20:50:03.540985 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-latency-factor not found 20:50:03.541035 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-max-latency not found 20:50:03.541078 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold not found 20:50:03.541122 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-set-start not found 20:50:03.541183 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-no-set-start not found 20:50:03.541311 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-set-on-restore not found 20:50:03.541372 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-no-set-on-restore not found 20:50:03.541419 main Guest Property: /VirtualBox/GuestAdd/VBoxService/--timesync-verbosity not found 20:50:03.542010 main Guest Property: /VirtualBox/GuestAdd/DRMResize not found 20:50:03.542050 main 6.1.22 r144080 started. Verbose level = 5 20:50:03.542080 main Daemonizing... 20:50:03.542453 main Setting VBoxService status to 30 20:50:03.542570 main Initializing services ... 20:50:03.542775 main Invalidating configuration ... 20:50:03.542914 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1) 20:50:03.543049 main Error: Failed to become guest control master: VERR_RESOURCE_BUSY 20:50:03.543235 main Error: Service 'control' failed to initialize: VERR_RESOURCE_BUSY 20:50:03.543366 main Setting VBoxService status to 800 20:50:03.543512 main Setting VBoxService status to 100 20:50:03.543556 main All stop functions for services called 20:50:03.543593 main Terminating service 'control' (0) ... 20:50:03.543614 main Terminating ... 20:50:03.543635 main Shutting down ... 20:50:03.543656 main Destroying guest session threads ended with VINF_SUCCESS 20:50:03.543678 main Session 0 is about to close ... 20:50:03.543699 main Stopping all guest processes ... 20:50:03.543738 main 0 guest processes were signalled to stop 20:50:03.543759 main Closing all guest files ... 20:50:03.543816 main Shutting down complete 20:50:03.543843 main Disconnecting client ID=0 ... 20:50:03.543867 main Terminating service 'timesync' (1) ... 20:50:03.543898 main Terminating service 'vminfo' (2) ... 20:50:03.543961 main Terminating service 'cpuhotplug' (3) ... 20:50:03.543986 main Terminating service 'memballoon' (4) ... 20:50:03.544010 main Terminating service 'vmstats' (5) ... 20:50:03.544047 main Terminating service 'automount' (6) ... 20:50:03.544084 main vbsvcAutoMountTerm 20:50:03.544108 main Stopping services returning: VINF_SUCCESS 20:50:03.544146 main Setting VBoxService status to 1 20:50:03.544168 main Setting VBoxService status to 101 20:50:03.544189 main Ended. 20:50:03.544231 main End of log file - Log started 2021-05-05T20:50:03.540159000ZNothing really new. Although I am not sure whether those "Guest Property ABC not found" lines are significant or not, as they didn't show without that extra verbose option. Just in case, here is the output from "ps aux|grep VBox"
root 355 0.0 0.0 0 0 ? I< 13:46 0:00 [iprt-VBoxWQueue] root 723 0.0 0.0 509996 4332 ? Ssl 13:47 0:00 /usr/sbin/VBoxService -f jacek 1653 0.0 0.0 233100 344 ? S 13:47 0:00 /usr/bin/VBoxClient --clipboard jacek 1654 0.0 0.0 365372 4264 ? Sl 13:47 0:00 /usr/bin/VBoxClient --clipboard jacek 1677 0.0 0.0 233100 344 ? S 13:47 0:00 /usr/bin/VBoxClient --seamless jacek 1678 0.0 0.0 365336 2724 ? Sl 13:47 0:00 /usr/bin/VBoxClient --seamless jacek 1691 0.0 0.0 233100 344 ? S 13:47 0:00 /usr/bin/VBoxClient --draganddrop jacek 1692 0.1 0.0 365852 2660 ? Sl 13:47 0:00 /usr/bin/VBoxClient --draganddrop jacek 1698 0.0 0.0 233100 1304 ? S 13:47 0:00 /usr/bin/VBoxClient --vmsvga
Re: Can't upgrade to Fedora 34
I got the system working!!
I thought that my problem is exactly the same as PGuin (started this thread), and for that reason, I didn't spend too much time fiddling with VBox settings (nothing was working for him). However, when I exhausted all other possibilities, I went back to VBox settings. I cannot say for sure, but it looks like the problem was due to VBoxSVGA (only that was working for me before, and this time it doesn't work). The Fedora 34 working setup is using VMSVGA (again, also some changes on CPU side, but maybe those were irrelevant).
Thank you for your help. At least my case is closed.
I thought that my problem is exactly the same as PGuin (started this thread), and for that reason, I didn't spend too much time fiddling with VBox settings (nothing was working for him). However, when I exhausted all other possibilities, I went back to VBox settings. I cannot say for sure, but it looks like the problem was due to VBoxSVGA (only that was working for me before, and this time it doesn't work). The Fedora 34 working setup is using VMSVGA (again, also some changes on CPU side, but maybe those were irrelevant).
Thank you for your help. At least my case is closed.
Re: Can't upgrade to Fedora 34
Problem remains here.
Found a constant way here to recreate the hanging forever problem on VirtualBox 6.1.22.
1. Start system and login GNOME desktop.
2. Start a GUI terminal.
3. Use vi to edit a text file, e.g. vi /tmp/hello.txt.
4. Type something and try ESC and then : and then w to save the file.
5. And it hangs.
Both newly installed Fedora 34 and live session of Fedora 34 WS x86_64 installation ISO can constantly recreate.
Both on Windows 7 and Windows 10 2004 as host OS can constantly recreate.
However, if not using the GUI terminal but try TTY by ctrl-alt-F3 (or other function keys) (user root for Live ISO) and vi text editing works normally.
By the way the VirtualBox here, VMSVGA is the only viable option.
Found a constant way here to recreate the hanging forever problem on VirtualBox 6.1.22.
1. Start system and login GNOME desktop.
2. Start a GUI terminal.
3. Use vi to edit a text file, e.g. vi /tmp/hello.txt.
4. Type something and try ESC and then : and then w to save the file.
5. And it hangs.
Both newly installed Fedora 34 and live session of Fedora 34 WS x86_64 installation ISO can constantly recreate.
Both on Windows 7 and Windows 10 2004 as host OS can constantly recreate.
However, if not using the GUI terminal but try TTY by ctrl-alt-F3 (or other function keys) (user root for Live ISO) and vi text editing works normally.
By the way the VirtualBox here, VMSVGA is the only viable option.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Can't upgrade to Fedora 34
This discussion clearly doesn't belong in "Windows Hosts". Moving the topic to "Linux Guests".
Re: Can't upgrade to Fedora 34
Yes, Fedora 34 hangs on vbox.
All you have to do is start installation in troubleshooting mode, then start fedora workstation 34 live with basic graphics mode and it will go just fine.
All you have to do is start installation in troubleshooting mode, then start fedora workstation 34 live with basic graphics mode and it will go just fine.
Re: Can't upgrade to Fedora 34
This also worked for me.Jacek_ wrote:I got the system working!!
I thought that my problem is exactly the same as PGuin (started this thread), and for that reason, I didn't spend too much time fiddling with VBox settings (nothing was working for him). However, when I exhausted all other possibilities, I went back to VBox settings. I cannot say for sure, but it looks like the problem was due to VBoxSVGA (only that was working for me before, and this time it doesn't work). The Fedora 34 working setup is using VMSVGA (again, also some changes on CPU side, but maybe those were irrelevant).
Thank you for your help. At least my case is closed.