Thanks, Frank, but this is not the problem, as far as I can tell.
My user is a member of group vboxusers, and this is what I get for vboxdrv:
# ls -l /dev/vboxdrv
crw-rw---- 1 root vboxusers 10, 62 2007-01-22 15:55 /dev/vboxdrv
As far as I can tell this is correct.
Any other ideas what we should check?
Alex
Frank Mehnert wrote:
> Ulf, Thomas, Alex,
>
> On Monday 22 January 2007 20:28, Alex Baer wrote:
>> I found some logfile entries for this in
>> ./VirtualBox/Machines/WinMCE/Logs. Maybe they give some helpful expert an
>> indication what the problem is caused by.
>>
>> <LogFile>
>> [...]
>> 00:00:43.537 count_load_time=0000000000000000
>> next_transition_time=0000000000000000
>> 00:00:43.537 u64ReloadTS=0000000000000000
>> u64NextTS=0000000000000000
>> 00:00:43.537 speaker_data_on=0x0 dummy_refresh_clock=0x0
>> 00:00:43.584 ERROR [COM]: rc=0x80004005
>> IID={1dea5c4b-0753-4193-b909-22330f64ec45} component={Console}
>> text={Failed to start VM execution (VERR_ACCESS_DENIED)}
>> 00:00:44.654 ERROR [COM]: rc=0x80004005
>> IID={1dea5c4b-0753-4193-b909-22330f64ec45} component={Console}
>> text={Failed to start VM execution (VERR_ACCESS_DENIED)}
>> 00:00:44.654 Power up failed (vrc=VERR_ACCESS_DENIED, hrc=0x80004005)
>> 00:00:48.374 ERROR [COM]: rc=0x80070005
>> IID={fd443ec1-000a-4f5b-9282-d72760a66916} component={Keyboard} text={The
>> console is not powered up}
>> 00:00:53.732 ERROR [COM]: rc=0x80070005
>> IID={fd443ec1-000a-4f5b-9282-d72760a66916} component={Keyboard} text={The
>> console is not powered up}
>> </LogFile>
>
> please make sure that the user which is trying to start VirtualBox has
> read/write access to /dev/vboxdrv. It should be suitable to be member of
> the group vboxusers. For further information please consult the User
> Manual section 2.2.3.
>
> Kind regards,
>
> Frank
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
