After following the instructions there, I was able to add the repository and complete steps 4-6 from this post, allowing me to install the VirtualBox Guest Additions.
Actually, dkms isn’t in the Oracle public yum server, but I don’t think I need it, at least not now. As John pointed out, I could just build it myself, which is what I’ll be doing in that event.
During the install, I did get a warning that:
This system does not seem to have support for OpenGL direct rendering.
Which I cleared up with this tip, but cleared up is a funny way to put it. Basically, the tip explains how to install the additions without an error, but since this version of OEL ships with an older version of Xorg, I won’t be able to use certain features, as clarified by this message:
You appear to be have an old version of the X Window system installed on your guest system. Seamless mode and dynamic resizing will not work in this guest.
It really does say “be have”. See for yourself.
Update: VirtualBox developers have fixed this typo, w00t for intertubes!
Update: This is caused by OEL shipping with an older version of Xorg, not by a VirtualBox issue. Small resolution is not a big deal for a server box, especially when it means resolving dependencies with a newer version of Xorg. So, no biggie really, just a bummer for me and my VM.
Oddly, I actually was able to get dynamic resize sort of working. I resized the window, then restarted, and voila, the VM remembered the new size, but once I shut down the VM, the settings were lost.
I left off at this point last night to continue the journey today.
The journey took a prolonged rest stop today, as I spent most of the day in meetings.
I tried to tackle the mounting of shared folders between meetings, but that turned into an adventure when got this error:
/sbin/mount.vboxsf: mounting failed with the error: Protocol error
This error had mounds of possible workarounds, several of which I tried, but with no success. If you’re wondering, the reason I want to mount shared folders was because I’ve already downloaded and unzipped WebCenter 11g Release 1 Patch Set 1 on my host.
Update: I neglected to clarify that this error is caused by a “quirk” in the mount command, not by a VirtualBox flaw. Thanks for reminding me.
Shared folders seemed like an easy way to avoid moving more bits around the intertubes, but after banging my head against this mounting error, “easy” seemed highly relative.
So, while I’ve been writing this post, the OEL VM has been chugging away, downloading WebCenter. Now it’s finished, and this seems like a good place to end this part.
Stay tuned for more. I did find out today that there are a few VMWare images of WebCenter floating around the development team. So, I feel better knowing that if I completely bork this up and quit it frustrating (been known to happen), I can always fall back on a vmdk.
Good to know.
Before I sign off, I have to say that I’d forgotten what a dark art (h/t Chet) Linux really is. So much time spent searching for errors and tips, the subtle differences between distros, the CLI-fu, the package building and dependencies; it’s designed by masters for masters. Makes me wonder how the Linux community will react to Chrome OS, which seems to take a Mac approach, i.e. designed by masters for dummies.
Keep in mind, I’m also calling myself a dummy. I wonder how Windows fits into this wordplay . . .
Anyway, find the comments.