Bug 365374 - problems with virtualbox guest tools
Summary: problems with virtualbox guest tools
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Martin Kudlvasr
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-27 21:23 UTC by Wade Berrier
Modified: 2009-10-01 06:15 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wade Berrier 2008-02-27 21:23:48 UTC 
I installed a suse 10.3 guest on a 10.3 host.

I used the packages to install the guest tools, and I had to manually run this command in order to get the xorg vboxmouse driver working:

mknod /dev/vboxadd c 254 0 -m 0666

Shouldn't that be created when the packages are installed?  (By a udev rule or something?)

Also, it would be nice if there was a sax profile to automatically configure the vbox mouse and video, as well as a README to get started with the guest tools.
Comment 1 Stefan Dirsch 2008-02-27 21:32:38 UTC 
>Also, it would be nice if there was a sax profile to automatically configure
>the vbox mouse and video, 
See Bug #358460.
Comment 2 Martin Kudlvasr 2008-03-06 14:43:21 UTC 

*** This bug has been marked as a duplicate of bug 358460 ***
Comment 3 Wade Berrier 2008-03-06 17:08:00 UTC 
This bug is only partially a duplicate of #358460 .

The portion that still needs fixing is the creation of /dev/vboxadd. (I didn't see any reference to fixing this in #358460 )
Comment 4 Martin Kudlvasr 2008-03-06 17:15:47 UTC 
oh, I see ...
Comment 5 Stefan Dirsch 2008-03-12 21:29:20 UTC 
Martin, do you plan to fix this for openSUSE 11.0? Otherwise we would need to revert the changes to SaX2 to use the vboxmouse driver as default.
Comment 6 Martin Kudlvasr 2008-03-13 14:46:01 UTC 
It is fixed in current beta - the init scripts were just not packaged. It is not fixed in factory due to #368571

But i cannot test it as the build does not work right now - problem with includes and makefile and kernel sources ...
Comment 7 Stefan Dirsch 2008-03-13 15:36:40 UTC 
(In reply to comment #6 from Martin Kudlvasr)
> It is fixed in current beta - the init scripts were just not packaged. It is
> not fixed in factory due to #368571

Access denied. :-( Could you add me to Cc of this bugreport?

> But i cannot test it as the build does not work right now - problem with
> includes and makefile and kernel sources ...

init_mm no longer exported. Right?
Comment 8 Martin Kudlvasr 2008-03-13 15:59:40 UTC 
I didn't know what init_mm is :-)
I got to Config.kmk and studying VBOX_LINUX_INCS . Adding the proper dirs should solve the problem right?
Comment 9 Martin Kudlvasr 2008-03-13 16:08:53 UTC 
pity I cannot rollback comment#8 :-)
Comment 15 Stefan Dirsch 2008-03-13 21:04:39 UTC 
(In reply to comment #6 from Martin Kudlvasr)
> It is fixed in current beta - the init scripts were just not packaged. It is
> not fixed in factory due to #368571

Ok. This means, once virtualbox is available again in STABLE, the required
device for vboxmouse will be created by virtualbox' init scripts. That's fine for me.
Comment 16 Michal Seben 2009-10-01 06:15:07 UTC 
closing as fixed