FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 05-29-2011, 09:50 PM
Nicolai Beuermann
 
Default virtualbox update v4.0.8 trouble

Hi,
after updating to virtualbox-4.0.8 I cannot start a vm anymore.

The following ebuilds are installed:
app-emulation/virtualbox-4.0.8
app-emulation/virtualbox-additions-4.0.8
app-emulation/virtualbox-extpack-oracle-4.0.8
app-emulation/virtualbox-modules-4.0.8

The logs mention that symlinks are not permitted. /usr/lib64 is a
symlink to /usr/lib on my system.

/ filesystem is ext4 on solid-state-drive mounted with default options.

lsmod:
vboxnetadp 4502 0
vboxnetflt 14541 0
vboxdrv 1745860 2 vboxnetadp,vboxnetflt

By the way stable virtualbox-3.2.12-r4 is able to run the vm.

cat VBox.log
00:00:00.676 VirtualBox 4.0.8-Gentoo r71778 linux.amd64 (May 29 2011
16:47:41) release log
00:00:00.676 Log opened 2011-05-29T17:02:39.312737000Z
00:00:00.676 OS Product: Linux
00:00:00.676 OS Release: 2.6.38-gentoo-r6-28.05.2011-01
00:00:00.676 OS Version: #1 SMP PREEMPT Sat May 28 15:37:06 CEST 2011
00:00:00.676 DMI Product Name: MacPro1,1
00:00:00.676 DMI Product Version: 1.0
00:00:00.677 Host RAM: 9997MB RAM, available: 8732MB
00:00:00.677 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.677 Process ID: 5576
00:00:00.677 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.696 pdmR3LoadR0U: pszName="VMMR0.r0"
rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED szErr="Symlinks are not
permitted: '/usr/lib64'"
00:00:00.696 VMSetError:
/var/tmp/portage/portage/app-emulation/virtualbox-4.0.8/work/VirtualBox-4.0.8_OSE/src/VBox/VMM/VMMR3/VM.cpp(583)
int vmR3CreateU(UVM*, uint32_t, int (*)(VM*, void*), void*);
rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED
00:00:00.696 VMSetError: Failed to load VMMR0.r0
00:00:00.696 VMSetError:
/var/tmp/portage/portage/app-emulation/virtualbox-4.0.8/work/VirtualBox-4.0.8_OSE/src/VBox/VMM/VMMR3/VM.cpp(354)
int VMR3Create(uint32_t, const VMM2USERMETHODS*, void (*)(VM*, void*,
int, const char*, unsigned int, const char*, const char*,
__va_list_tag*), void*, int (*)(VM*, void*), void*, VM**);
rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED
00:00:00.696 VMSetError: Unknown error creating VM
00:00:00.698 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console}
aText={Failed to load VMMR0.r0 (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
00:00:00.698 Unknown error creating VM
(VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED)}, preserve=false
00:00:00.707 Power up failed
(vrc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED, rc=NS_ERROR_FAILURE
(0X80004005))
00:00:00.725 Using XKB for keycode to scan code conversion


Please help. I don't have an idea.

Nico
 
Old 05-29-2011, 09:59 PM
Alan McKinnon
 
Default virtualbox update v4.0.8 trouble

Apparently, though unproven, at 23:50 on Sunday 29 May 2011, Nicolai Beuermann
did opine thusly:

> Hi,
> after updating to virtualbox-4.0.8 I cannot start a vm anymore.
>
> The following ebuilds are installed:
> app-emulation/virtualbox-4.0.8
> app-emulation/virtualbox-additions-4.0.8
> app-emulation/virtualbox-extpack-oracle-4.0.8
> app-emulation/virtualbox-modules-4.0.8
>
> The logs mention that symlinks are not permitted. /usr/lib64 is a
> symlink to /usr/lib on my system.

Switch it to be the other way round which is how it should be. It works
perfectly here with the exact same packages:

$ ls -al /usr/
lrwxrwxrwx 1 root root 5 Oct 27 2010 lib -> lib64


The log entry tells you the software will not accept your configuration.



>
> / filesystem is ext4 on solid-state-drive mounted with default options.
>
> lsmod:
> vboxnetadp 4502 0
> vboxnetflt 14541 0
> vboxdrv 1745860 2 vboxnetadp,vboxnetflt
>
> By the way stable virtualbox-3.2.12-r4 is able to run the vm.
>
> cat VBox.log
> 00:00:00.676 VirtualBox 4.0.8-Gentoo r71778 linux.amd64 (May 29 2011
> 16:47:41) release log
> 00:00:00.676 Log opened 2011-05-29T17:02:39.312737000Z
> 00:00:00.676 OS Product: Linux
> 00:00:00.676 OS Release: 2.6.38-gentoo-r6-28.05.2011-01
> 00:00:00.676 OS Version: #1 SMP PREEMPT Sat May 28 15:37:06 CEST 2011
> 00:00:00.676 DMI Product Name: MacPro1,1
> 00:00:00.676 DMI Product Version: 1.0
> 00:00:00.677 Host RAM: 9997MB RAM, available: 8732MB
> 00:00:00.677 Executable: /usr/lib/virtualbox/VirtualBox
> 00:00:00.677 Process ID: 5576
> 00:00:00.677 Package type: LINUX_64BITS_GENERIC (OSE)
> 00:00:00.696 pdmR3LoadR0U: pszName="VMMR0.r0"
> rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED szErr="Symlinks are not
> permitted: '/usr/lib64'"
> 00:00:00.696 VMSetError:
> /var/tmp/portage/portage/app-emulation/virtualbox-4.0.8/work/VirtualBox-4.0
> .8_OSE/src/VBox/VMM/VMMR3/VM.cpp(583) int vmR3CreateU(UVM*, uint32_t, int
> (*)(VM*, void*), void*);
> rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED
> 00:00:00.696 VMSetError: Failed to load VMMR0.r0
> 00:00:00.696 VMSetError:
> /var/tmp/portage/portage/app-emulation/virtualbox-4.0.8/work/VirtualBox-4.0
> .8_OSE/src/VBox/VMM/VMMR3/VM.cpp(354) int VMR3Create(uint32_t, const
> VMM2USERMETHODS*, void (*)(VM*, void*, int, const char*, unsigned int,
> const char*, const char*,
> __va_list_tag*), void*, int (*)(VM*, void*), void*, VM**);
> rc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED
> 00:00:00.696 VMSetError: Unknown error creating VM
> 00:00:00.698 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
> aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console}
> aText={Failed to load VMMR0.r0 (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
> 00:00:00.698 Unknown error creating VM
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED)}, preserve=false
> 00:00:00.707 Power up failed
> (vrc=VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED, rc=NS_ERROR_FAILURE
> (0X80004005))
> 00:00:00.725 Using XKB for keycode to scan code conversion
>
>
> Please help. I don't have an idea.
>
> Nico

--
alan dot mckinnon at gmail dot com
 
Old 06-05-2011, 01:30 PM
Nicolai Beuermann
 
Default virtualbox update v4.0.8 trouble

Am 29.05.2011 23:59, schrieb Alan McKinnon:
> Apparently, though unproven, at 23:50 on Sunday 29 May 2011, Nicolai Beuermann
> did opine thusly:
>
>> Hi,
>> after updating to virtualbox-4.0.8 I cannot start a vm anymore.
>>
>> The following ebuilds are installed:
>> app-emulation/virtualbox-4.0.8
>> app-emulation/virtualbox-additions-4.0.8
>> app-emulation/virtualbox-extpack-oracle-4.0.8
>> app-emulation/virtualbox-modules-4.0.8
>>
>> The logs mention that symlinks are not permitted. /usr/lib64 is a
>> symlink to /usr/lib on my system.
>
> Switch it to be the other way round which is how it should be. It works
> perfectly here with the exact same packages:
>
> $ ls -al /usr/
> lrwxrwxrwx 1 root root 5 Oct 27 2010 lib -> lib64
Now it works.

One question remains unanswered and that is how this wrong symbolic link
was created??? By portage?

>
>> Please help. I don't have an idea.
>>
>> Nico
>
Thank you very much.
Regards
Nico
 

Thread Tools




All times are GMT. The time now is 11:20 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org