Advanced search

Forums : Technical Support : Can't get VirtualBox task to run correctly
Message board moderation

To post messages, you must log in.

AuthorMessage
Hydrosaure

Send message
Joined: 3 May 17
Posts: 3
Credit: 1,096,315
RAC: 503
Message 21464 - Posted: 2 Jun 2017, 17:59:46 UTC
Last modified: 2 Jun 2017, 18:09:06 UTC

I have several hosts having 100% failure rate on VirtualBox tasks.

Here's one of them:
http://www.cosmologyathome.org/results.php?hostid=310407&offset=0&show_names=0&state=6&appid=

Host is running Voidlinux distribution and all other project/tasks run fine

Logs only show this:
<core_client_version>7.6.3</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
2017-06-02 14:21:53 (8522): vboxwrapper (7.7.26196): starting
SIGSEGV: segmentation violation
Stack trace (8 frames):
../../projects/www.cosmologyathome.org/vboxwrapper_26196_x86_64-pc-linux-gnu(boinc_catch_signal+0x57)[0x487b47]
/usr/lib/libpthread.so.0(+0x11b00)[0x7f440d6c7b00]
/usr/lib/libc.so.6(strlen+0x26)[0x7f440d397b46]
../../projects/www.cosmologyathome.org/vboxwrapper_26196_x86_64-pc-linux-gnu[0x45bcac]
../../projects/www.cosmologyathome.org/vboxwrapper_26196_x86_64-pc-linux-gnu[0x4189f8]
../../projects/www.cosmologyathome.org/vboxwrapper_26196_x86_64-pc-linux-gnu[0x406733]
/usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7f440d3384e1]
../../projects/www.cosmologyathome.org/vboxwrapper_26196_x86_64-pc-linux-gnu[0x404f79]

Exiting...

</stderr_txt>
]]>



Software versions:
# uname -a
Linux boinc-g3258 4.8.17_1 #1 SMP PREEMPT Mon Jan 9 08:32:27 UTC 2017 x86_64 GNU/Linux
# VBoxManage -v
5.1.22r115126



Anything I can do to get more detail logs/feedback and help troubleshoot this issue ?
ID: 21464 · Report as offensive     Reply Quote
Hydrosaure

Send message
Joined: 3 May 17
Posts: 3
Credit: 1,096,315
RAC: 503
Message 21467 - Posted: 12 Jun 2017, 18:07:49 UTC

Trying to figure this out.

I copied a task from another host where it works and tried to run different steps manually.
After making sure links and folder names were correct I ran:

[root@boinc-z87 0]# ./vboxwrapper_26196_x86_64-pc-linux-gnu
[root@boinc-z87 0]#
[root@boinc-z87 0]# cat stderr.txt
2017-06-12 19:46:40 (18232): vboxwrapper (7.7.26196): starting
2017-06-12 19:46:40 (18232): Feature: Checkpoint interval offset (213 seconds)
2017-06-12 19:46:40 (18232): Detected: VirtualBox VboxManage Interface (Version: 5.1.22)
2017-06-12 19:46:40 (18232): Detected: Minimum checkpoint interval (600.000000 seconds)
2017-06-12 19:46:40 (18232): ERROR: couldn't create scratch directory: mkdir() failed.
2017-06-12 19:46:40 (18232): Create VM. (boinc_3d41a328df5c7e34, slot#0)
2017-06-12 19:46:40 (18232): Updating drive controller type and model for desired configuration.
2017-06-12 19:46:43 (18232): Setting Memory Size for VM. (2048MB)
2017-06-12 19:46:43 (18232): Setting CPU Count for VM. (2)
2017-06-12 19:46:43 (18232): Setting Chipset Options for VM.
2017-06-12 19:46:43 (18232): Setting Boot Options for VM.
2017-06-12 19:46:43 (18232): Setting Network Configuration for NAT.
2017-06-12 19:46:43 (18232): Enabling VM Network Access.
2017-06-12 19:46:44 (18232): Disabling USB Support for VM.
2017-06-12 19:46:44 (18232): Disabling COM Port Support for VM.
2017-06-12 19:46:44 (18232): Disabling LPT Port Support for VM.
2017-06-12 19:46:44 (18232): Disabling Audio Support for VM.
2017-06-12 19:46:45 (18232): Disabling Clipboard Support for VM.
2017-06-12 19:46:45 (18232): Disabling Drag and Drop Support for VM.
2017-06-12 19:46:45 (18232): Adding storage controller(s) to VM.
2017-06-12 19:46:46 (18232): Adding virtual ISO 9660 disk drive to VM. (vm_isocontext.iso)
2017-06-12 19:46:46 (18232): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2017-06-12 19:46:46 (18232): Enabling shared directory for VM.
2017-06-12 19:46:46 (18232): Starting VM. (boinc_3d41a328df5c7e34, slot#0)
2017-06-12 19:46:48 (18232): Successfully started VM. (PID = '18653')
2017-06-12 19:46:48 (18232): Reporting VM Process ID to BOINC.
2017-06-12 19:46:48 (18232): Guest Log: BIOS: VirtualBox 5.1.22
2017-06-12 19:46:48 (18232): VM state change detected. (old = 'poweroff', new = 'running')
2017-06-12 19:46:48 (18232): Preference change detected
2017-06-12 19:46:48 (18232): Setting CPU throttle for VM. (100%)
2017-06-12 19:46:48 (18232): Setting checkpoint interval to 600 seconds. (Higher value of (Preference: 600 seconds) or (Vbox_job.xml: 600 seconds))
19:46:50 (18232): BOINC client no longer exists - exiting
19:46:50 (18232): timer handler: client dead, exiting
2017-06-12 19:46:50 (18232): Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
2017-06-12 19:46:50 (18232): Guest Log: int13_harddisk: function 02, unmapped device for ELDL=80
2017-06-12 19:46:50 (18232): Guest Log: BIOS: Boot from Hard Disk 0 failed
2017-06-12 19:46:50 (18232): Guest Log: BIOS: Boot : bseqnr=2, bootseq=0003
2017-06-12 19:46:50 (18232): Guest Log: BIOS: Booting from CD-ROM...
2017-06-12 19:46:50 (18232): Guest Log: BIOS: KBD: unsupported int 16h function 03
2017-06-12 19:46:50 (18232): Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
2017-06-12 19:46:50 (18232): Powering off VM.
2017-06-12 19:46:50 (18232): Successfully stopped VM.


it cant talk to boinc so stops immediately, still the VM remains registered:
[root@boinc-z87 ~]# VBoxManage -q list vms
"boinc_3d41a328df5c7e34" {77a01cd0-c852-44e1-80e4-18fd95b0b034}



From the VBox Logs:

00:00:00.320679 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:00.320691 Console: Machine state changed to 'Running'
00:00:00.324126 VMMDev: Guest Log: BIOS: VirtualBox 5.1.22
00:00:00.324951 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:00.350201 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:00.356523 AHCI#0: Reset the HBA
00:00:00.356563 AHCI#0: Port 0 reset
00:00:00.356657 AHCI#0: Port 1 reset
00:00:00.356707 AHCI#0: Port 2 reset
00:00:00.356749 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:00.373681 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007fc080f3f000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0
00:00:02.833670 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:02.835025 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:02.835167 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
00:00:02.835351 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=80
00:00:02.835463 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
00:00:02.835583 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0003
00:00:02.835911 VMMDev: Guest Log: BIOS: Booting from CD-ROM...
00:00:03.468488 VMMDev: Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:03.468643 VMMDev: Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
00:00:03.681362 Console: Machine state changed to 'Stopping'
00:00:03.681522 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:00:03.681530 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=32 cbLine=0x0 flags=0x0
00:00:03.681740 Changing the VM state from 'RUNNING' to 'POWERING_OFF'


So it seems to fail to boot from CDROM for some reason.

Checked file from working and non working system they match sha1sums.

20096bb4b438d184cfc5380b2dcbbad24f21dbb8  /var/lib/boinc-client/projects/www.cosmologyathome.org/vm_isocontext_v1.0.0.iso
20096bb4b438d184cfc5380b2dcbbad24f21dbb8  /root/cosmo/0/vm_isocontext.iso
ID: 21467 · Report as offensive     Reply Quote
Hydrosaure

Send message
Joined: 3 May 17
Posts: 3
Credit: 1,096,315
RAC: 503
Message 21486 - Posted: 19 Jul 2017, 17:50:20 UTC - in response to Message 21467.  

So I thought I was onto something after searching around origin of error message
"ERROR: couldn't create scratch directory: mkdir() failed.",
digging through source code of both vboxwrapper/boinc projects and finding out the /scratch directory was indeed missing on this host.

Still after manually creating it, it doesn't change a thing and I still get the same instant crash :(
ID: 21486 · Report as offensive     Reply Quote

Forums : Technical Support : Can't get VirtualBox task to run correctly