-   Linux - Virtualization and Cloud (
-   -   VirtualBox: NS_ERROR_FAILURE, component Machine, interface IMachine, callee (

catkin 12-10-2010 01:07 PM

VirtualBox: NS_ERROR_FAILURE, component Machine, interface IMachine, callee
Hello :)

After a routine upgrade of Slackware64 13.1, VirtualBox 3.2.8 virtual machines will not start. The error message is (as shown, with nothing after callee)

ERROR: The virtual machine 'WXP' has terminated unexpectedly during startup with exit code 1
Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee

No log is generated in the ~/.VirtualBox/Machines/WXP/Log directory.

Rebuilding the modules using /etc/rc.d/vboxdrv setup goes without an error message either on-screen or in /var/log/vbox-install.log but does not fix the problem.

The packages upgraded include glibc-solibs-2.11.1-x86_64-5_slack13.1, glibc-2.11.1-x86_64-5_slack13.1, glibc-i18n-2.11.1-x86_64-5_slack13.1, glibc-profile-2.11.1-x86_64-5_slack13.1 and glibc-zoneinfo-2.11.1-noarch-5_slack13.1.

Netsearching for the error message does not find any closely related problems except for this from 4oct10 with solution "The problem was caused by incorrect .config file into the linux-source directory"

Three questions:
  1. The running kernel's .config file is not in /usr/src/linux but in /home/c/src/linux- That has not previously been a problem ... ?
  2. Does the VirtualBox module build and/or kernel build use glibc packages? If so, is it worth trying to fix the problem by re-building the kernel?
  3. How to back out the glibc package changes? This with the hope of restoring functionality and analysing the problem.


catkin 12-11-2010 07:56 AM

Fixed by installing VirtualBox 3.2.12 (thanks vdemuth).

All times are GMT -5. The time now is 05:16 PM.