Ok, here are the results. After issuing
LD_LIBRARY_PATH=. ./VBoxSVC&
LD_LIBRARY_PATH=. ./VirtualBox
I have:
# lsmod
Module Size Used by
vboxdrv 26756 1
# cat /proc/misc
62 vboxdrv
So far it seems correct. I've checked the latest logfile again, however, and
found this:
[/Devices/pcbios/0/Config/] (level 4)
00:00:41.618 RamSize <integer> = 0x0000000010000000 (268435456)
00:00:41.618 HardDiskDevice <string> = "piix3ide" (cch=9)
00:00:41.618 FloppyDevice <string> = "i82078" (cch=7)
00:00:41.618 BootDevice0 <string> = "FLOPPY" (cch=7)
00:00:41.618 BootDevice1 <string> = "DVD" (cch=4)
00:00:41.618 BootDevice2 <string> = "IDE" (cch=4)
00:00:41.618 BootDevice3 <string> = "NONE" (cch=5)
00:00:41.618 FadeIn <integer> = 0x0000000000000001 (1)
00:00:41.618 FadeOut <integer> = 0x0000000000000001 (1)
00:00:41.618 LogoTime <integer> = 0x0000000000000000 (0)
00:00:41.618 LogoFile <string> = "" (cch=1)
00:00:41.618 ShowBootMenu <integer> = 0x0000000000000002 (2)
Here the BootDevice1 is "DVD", and while the device I want to install my
guest system from is actually a DVD-ROM drive, I mount the install CD
as /dev/cdrom (which is link to /dev/hdc, the actual device). Could this
have to do anything with the VERR_ACCESS_DENIED thing? And if so: How can
it be fixed?
One question here: Should the CD be mounted or not? Seems the device name is
preceded by an asterisk when a medium is mounted. But should an
installation CD mounted on the host before running the guest, or not?
Thanks again!
Alex
Frank Mehnert wrote:
> On Monday 22 January 2007 21:05, Alex Baer wrote:
>> 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?
>
> Ok. Next things to check: Is the kernel module actually loaded? And in
> 'cat /proc/misc' must be a line
>
> 62 vboxdrv
> ^^
>
> that is the device minor number of your /dev/vboxdrv device node.
>
>> 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
>
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
