Message boards :
ATLAS application :
All Atlas jobs failing on Win11 host
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Dec 19 Posts: 15 Credit: 41,935,605 RAC: 75,079 |
All ATLAS jobs failing. And I can't figure out why. I have reinstalled boinc already few times (7.24.1), Virtualbox is 7.0.12 (and runs happily other virtual machines) and my host is win11 with latest patches. Atlas jobs have been run successfully with this hw earlier so I don't suspect that either. But boinc/vbox combo is new and I don't remember whether that has rund any Atlas job successfully. Example of failing job is here https://lhcathome.cern.ch/lhcathome/result.php?resultid=401842192. Error text in question: 2023-11-17 21:38:57 (9532): Error in deregister parent vdi for VM: -2135228404 Command: VBoxManage -q closemedium "C:\ProgramData\BOINC/projects/lhcathome.cern.ch_lhcathome/ATLAS_vbox_3.01_image.vdi" Output: VBoxManage.exe: error: Cannot close medium 'C:\ProgramData\BOINC\projects\lhcathome.cern.ch_lhcathome\ATLAS_vbox_3.01_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 1875 of file VBoxManageDisk.cpp 2023-11-17 21:38:57 (9532): Could not create VM 2023-11-17 21:38:57 (9532): ERROR: VM failed to start 2023-11-17 21:38:57 (9532): Powering off VM. 2023-11-17 21:38:57 (9532): Deregistering VM. (boinc_98d04b0a3a9f3e97, slot#0) 2023-11-17 21:38:57 (9532): Removing network bandwidth throttle group from VM. 2023-11-17 21:38:57 (9532): Removing VM from VirtualBox. Has anyone else seen similar or am I alone with these issues? Any suggestions on how to triage the problem further are appreciated. Pekka |
Send message Joined: 2 May 07 Posts: 2228 Credit: 173,737,495 RAC: 23,084 |
Take a look into Virtualbox vboxmanager for yellow triangle. Seem so, there are old .vdi's. |
Send message Joined: 23 Dec 19 Posts: 15 Credit: 41,935,605 RAC: 75,079 |
And resolution to the problem was to completely reinstall virtualbox (and boinc). Reinstalling boinc only didn't help. I didn't find the actual cause within virtualbox which was causing the issue though. Pekka |
©2024 CERN