Message boards : Number crunching : VirtualBox .. , , 6.1.36 , , .. (released July 19 2022)
Message board moderation

To post messages, you must log in.

AuthorMessage
Richie_unstable

Send message
Joined: 26 Oct 18
Posts: 92
Credit: 4,188,598
RAC: 0
Message 47034 - Posted: 20 Jul 2022, 5:59:49 UTC

VirtualBox 6.1.36 (released July 19 2022)
https://www.virtualbox.org/wiki/Changelog-6.1#v36

This is a maintenance release. The following items were fixed and/or added:

VMM: Fixed possible Linux guest kernel crash when configuring Speculative Store Bypass for a single vCPU VM
GUI: In the storage page of the virtual machine settings dialog, fixed a bug which disrupted mouse interaction with the native file selector on KDE
NAT: Prevent issue when host resolver incorrectly returned NXDOMAIN for unsupported queries (bug #20977)
Audio: General improvements in saved state area
Recording: Various fixes for settings handling
VGA: Performance improvements for screen updates when VBE banking is used
USB: Fixed rare crashes when detaching a USB device
ATA: Fixed NT4 guests taking a minute to eject CDs
vboximg-mount: Fixed broken write support (bug #20896)
SDK: Fixed Python bindings incorrectly trying to convert arbitrary byte data into unicode objects with Python 3, causing exceptions (bug #19740)
API: Fixed an issue when virtual USB mass storage devices or virtual USB DVD drives are added while the VM is not running are by default not marked as hot-pluggable
API: Initial support for Python 3.10
API: Solaris OS types cleanup
Windows host: Fixed regression in 6.1.32 leading to guest hangs when Hyper-V is used (bug #20787)
Windows host: Fixed possible issues with saving and restoring VM state when using Hyper-V/NEM mode
Linux and Solaris hosts: Allow to mount shared folder if it is represented as a symlink on a host side (bug #17491)
Linux Host and Guest drivers: Introduced initial support for kernels 5.18, 5.19 and RHEL 9.1 (bugs #20914, #20941)
Linux Host and Guest drivers: Better support for kernels built with clang compiler (bugs #20425 and #20998)
Solaris Guest Additions: General improvements in installer area
Solaris Guest Additions: Fixed guest screen resize in VMSVGA graphics configuration
Linux and Solaris Guest Additions: Fixed multi-screen handling in VBoxVGA and VBoxSVGA graphics configuration
Linux and Solaris Guest Additions: Added support for setting primary screen via VBoxManage
Linux and Solaris Guest Additions: Fixed X11 resources leak when resizing guest screens
Linux and Solaris Guest Additions: Fixed file descriptor leak when starting a process using guest control (bug #20902)
Linux and Solaris Guest Additions: Fixed guest control executing processes as root
Linux Guest Additions: Improved guests booting time by preventing kernel modules from being rebuilt when it is not necessary (bug #20502)
Windows Guest Additions: Fixed VBoxTray crash on startup in NT4 guests on rare circumstances
ID: 47034 · Report as offensive     Reply Quote
rjs5

Send message
Joined: 14 Mar 22
Posts: 4
Credit: 4,533,977
RAC: 22,238
Message 47156 - Posted: 18 Aug 2022, 9:13:37 UTC - in response to Message 47034.  

I upgraded my Windows 11 machine ( 10802580 ) to virtualbox 6.1.36 and I am seeing Atlas errors.
I have EXCLUDED the Boinc Data directory from antivirus scans.
Do you know what i am doing wrong?
Should I uninstall and install 6.1.34 again?
thanks


Stderr output

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 2159738892 (0x80bb000c)</message>
<stderr_txt>
2022-08-17 23:00:57 (16204): Detected: vboxwrapper 26205
2022-08-17 23:00:57 (16204): Detected: BOINC client v7.20.2
2022-08-17 23:00:58 (16204): Detected: VirtualBox VboxManage Interface (Version: 6.1.36)
2022-08-17 23:00:58 (16204): Successfully copied 'init_data.xml' to the shared directory.
2022-08-17 23:00:59 (16204): Create VM. (boinc_42486e46406184d0, slot#23)
2022-08-17 23:00:59 (16204): Setting Memory Size for VM. (6600MB)
2022-08-17 23:01:00 (16204): Setting CPU Count for VM. (4)
2022-08-17 23:01:00 (16204): Setting Chipset Options for VM.
2022-08-17 23:01:00 (16204): Setting Graphics Controller Options for VM.
2022-08-17 23:01:00 (16204): Setting Boot Options for VM.
2022-08-17 23:01:01 (16204): Setting Network Configuration for NAT.
2022-08-17 23:01:01 (16204): Enabling VM Network Access.
2022-08-17 23:01:01 (16204): Disabling USB Support for VM.
2022-08-17 23:01:02 (16204): Disabling COM Port Support for VM.
2022-08-17 23:01:02 (16204): Disabling LPT Port Support for VM.
2022-08-17 23:01:02 (16204): Disabling Audio Support for VM.
2022-08-17 23:01:02 (16204): Disabling Clipboard Support for VM.
2022-08-17 23:01:03 (16204): Disabling Drag and Drop Support for VM.
2022-08-17 23:01:03 (16204): Adding storage controller(s) to VM.
2022-08-17 23:01:03 (16204): Adding virtual disk drive to VM. (ATLAS_vbox_2.02_image.vdi)
2022-08-17 23:01:10 (16204): Error in deregister parent vdi for VM: -2135228404
Command:
VBoxManage -q closemedium "E:\BOINC/projects/lhcathome.cern.ch_lhcathome/ATLAS_vbox_2.02_image.vdi"
Output:
VBoxManage.exe: error: Cannot close medium 'E:\BOINC\projects\lhcathome.cern.ch_lhcathome\ATLAS_vbox_2.02_image.vdi' because it has 1 child media
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "Close()" at line 1736 of file VBoxManageDisk.cpp

2022-08-17 23:01:10 (16204): Could not create VM
2022-08-17 23:01:10 (16204): ERROR: VM failed to start
2022-08-17 23:01:10 (16204): Powering off VM.
2022-08-17 23:01:10 (16204): Deregistering VM. (boinc_42486e46406184d0, slot#23)
2022-08-17 23:01:10 (16204): Removing network bandwidth throttle group from VM.
2022-08-17 23:01:11 (16204): Removing VM from VirtualBox.
ID: 47156 · Report as offensive     Reply Quote
Crystal Pellet
Volunteer moderator
Volunteer tester

Send message
Joined: 14 Jan 10
Posts: 1302
Credit: 8,664,918
RAC: 6,783
Message 47157 - Posted: 18 Aug 2022, 10:10:29 UTC - in response to Message 47156.  

I upgraded my Windows 11 machine ( 10802580 ) to virtualbox 6.1.36 and I am seeing Atlas errors.
I have EXCLUDED the Boinc Data directory from antivirus scans.
Do you know what i am doing wrong?
Should I uninstall and install 6.1.34 again?
Your errors already started with version 6.1.34. See https://lhcathome.cern.ch/lhcathome/result.php?resultid=363355412
I think you have to cleanup your virtualbox environment with VritualBox Virtual Media Manager from the File Menu.
Remove the disks from the media, but keep the vdi's on your computer.
ID: 47157 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2439
Credit: 229,849,865
RAC: 135,095
Message 47158 - Posted: 18 Aug 2022, 10:16:29 UTC - in response to Message 47156.  

I suspect there were suspended tasks during the update and VirtualBox stumbled over a snapshot.

This needs to be cleaned manually.

1. set BOINC to "no new tasks"
2. pause all vbox tasks that are not yet started
3. cancel all ATLAS tasks that are already started (they will not recover)
4. shut down BOINC
5. Check from the vbox GUI "Media Manager" if there are broken disk entries; remove them (but not the vdi file if you are asked about it!)
6. Restart BOINC (should work again)
ID: 47158 · Report as offensive     Reply Quote
rjs5

Send message
Joined: 14 Mar 22
Posts: 4
Credit: 4,533,977
RAC: 22,238
Message 47161 - Posted: 18 Aug 2022, 16:19:19 UTC - in response to Message 47158.  

I suspect there were suspended tasks during the update and VirtualBox stumbled over a snapshot.

This needs to be cleaned manually.

1. set BOINC to "no new tasks"
2. pause all vbox tasks that are not yet started
3. cancel all ATLAS tasks that are already started (they will not recover)
4. shut down BOINC
5. Check from the vbox GUI "Media Manager" if there are broken disk entries; remove them (but not the vdi file if you are asked about it!)
6. Restart BOINC (should work again)


Thanks to you and Crystal Pellet. It is great to have good volunteer support!!!

The only place I got stuck for a moment was deleting the VDI. I didn't notice the ">" on the left which indicated there was something (a disk) attached. I deleted it, the image and LHC is working again.
ID: 47161 · Report as offensive     Reply Quote

Message boards : Number crunching : VirtualBox .. , , 6.1.36 , , .. (released July 19 2022)


©2024 CERN