Message boards :
Number crunching :
VBox 6.1.2 announced - Ext.Pack giving troubles (solved)
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 Jan 10 Posts: 1268 Credit: 8,421,616 RAC: 2,139 |
Since the 13th of January there is a new VBox version 6.1.2 available and announced in VBox Manager like: You can download it and install, but installing the 6.1.2. Extension Pack gives troubles. Installing procedure is endless. So stay to 6.1.0 (or older) as long as that is not solved. |
Send message Joined: 29 Sep 04 Posts: 281 Credit: 11,859,285 RAC: 1 |
There are a couple of suggestions in their Forum but none worked for me, or for others it seems. Even uninstalling 6.1.0 to install 6.1.2 didn't allow the Extension Pack to upgrade. I only have 2 Windows hosts. Both have been left at 6.1.2 with the 6.1.0 Extension Pack (not recommended but no issues so far) It is probably better to stick with 6.1.0 with the 6.1.0 Extensions until the upgrade issue is resolved in case there are incompatibility issues when not using the VBox and Extensions of the same version number but I couldn't be bothered downgrading both machines to the previous version again. |
Send message Joined: 26 Oct 18 Posts: 90 Credit: 4,188,598 RAC: 0 |
That problem seems to be fixed now on the latest package / build. Extension pack installed fine. |
Send message Joined: 14 Jan 10 Posts: 1268 Credit: 8,421,616 RAC: 2,139 |
Version 6.1.2 with VirtualBox Extension Pack installed OK now. I tested this version on Windows with a running Theory- and ATLAS-task including several suspends (LAIM off), resumes, Theory snapshots, BOINC-restart and BOINC start after reboot. All without issues. Theory task ATLAS task |
Send message Joined: 16 Sep 17 Posts: 100 Credit: 1,618,469 RAC: 0 |
I tested this version on Windows with a running Theory- and ATLAS-task including several suspends (LAIM off), resumes, Theory snapshots, BOINC-restart and BOINC start after reboot. All without issues. I am not so lucky. I repeatedly encounter stuck Atlas tasks that go overtime without ever completing or crashing. Some VMs are completely unresponsive, but most are still active and show a kworker issue. All tasks have in common that their log shows a "timesync vgsvcTimeSyncWorker: Radical guest time change" error. They all have been previously suspended for various reasons, so my assumption is that resuming doesn't work any more reliable than with previous VBox versions. Therefore resuming should still be avoided, if at all possible. (BOINC 7.12.1 and VBox 6.1.2) Edit: VBox is also littered with several inactive (crashed and completed) VMs. |
©2024 CERN