Hello,

I am kinda new to Ubuntu/Linux/Unix so please bare with me. I have purchased a virtual private server and installed Ubuntu 14.10 on the server, afterwards I have Installed VirtualBox on the server and I have created a Windows 7 machine. When I try starting up my box it gives me this error.



I tried using the command '/sbin/rcvboxdrv setup' to reinstall the kernel module but after pressing enter it gave me another error.



When I do uname -r this what comes up:



I tried going on Google to search for the kernel module, but I had no luck in finding the right Linux Header. I would appreciate it if you could help me out, I'm new to Linux and I'm trying to figure out this problem I am having.

Thanks,
Matthew

Just a couple of things:

When posting, instead of using pics use code tags. It will make it easier for people to help you b/c we'll be able to copy/paste instead of having to retype stuff.

I've never bought / rented a server, I always just build them. Normally everything you need is in a disto's repos. Why are you searching Google for the headers instead of just installing them? Does OpenVZ not provide a repo?

The first thing I would do is upgrade your kernel. When researching your kernel the very first thing I found was this:

Download/kernel/rhel6/042stab113.11
Warning: this is an old version of RHEL6 kernel. For the latest version, see Download/kernel/rhel6/042stab116.1.

It appears as if OpevVZ has issues providing complete repos and that others have had header issues as well:

Installation of Linux kernel headers fails in Debian

I would try following the suggestions in that thread:
1) Contact OpenVZ
2) Try to DL and install the headers for the new kernel manually from their resources after updating.

I'll try what OpevVZ has provided. How do I manually Install Linux headers/image? I've got the header on my ubuntu desktop and I'm wondering how do I manually Install them?

Thanks,
Matthew

Just exactly how hard did you hit Google before coming here?

Inquiry: openvz install headers

5th reply: How to compile a kernel module for an openvz virtual machine?

I know you're new and learning, so I won't yell at you. But I'll tell ya now: In the *nix world we expect you to do your own homework.

"Please install the linux-headers-2.6.32-042stab113.11 package"
linux-headers-2.6.32* sure looks like RH/CentOS nomenclature to me.
So how did the OP "installed Ubuntu 14.10 on the server"?
What is this Frankenstein?

OpenVZ do anything but CentOS?

I paid literally $10 for this Ubuntu server. This is so frustrating lol

From a light / quick run around the googles it looks like OpenVZ (never heard of it before) is some kind of nested hosting service. It looks like VZOpen uses CentOS as the base OS for its service. Then it sells / rents you a (also has an open source) VT server solution.

The OP installed Ubuntu 14.04 inside the VZOpen / CentOS instance.

The OP installed Virtualbox inside Ubuntu 14.04

The OP set up a windows VM inside the UB14 container. The nested windows VM will not run b/c the proper headers are not installed to the VZOpen / CentOS instance.

To further "sub-virtualize" (nest) the OpenVZ instance the headers need to be installed to the instance not the nested containers (doze, ubuntu, etc).

It looks like the OP is throwing the run sbin setup error in the UB container b/c the OpenVZ / CentOS instance does not have the headers installed, plus the instance kernel is out of date.

https://openvz.org/Quick_installation

Now the OP does not specify if they used an ISO to install UB14 to the container or if they DL'd one of the VZOpen pre-built UB14 containers.

If after upgrading the instance kernel and installing the instance headers the nested windows container still will not initialize then the next step would be to attempt to install the necessary headers to the UB14 container. I have not played with nested VT much. But I can tell you it's a PITA. From what little I've read about OpenVZ a pre-built container should have everything it needs; including headers. From what I've read directly installing headers to an ISO built container from the normal UB repos may fail. In which case, after the instance kernel is updated and the instance headers are installed, if the issue persists the simplest solution would be to start over with a pre-built VZOpen UB14 container, then install VB in to it then setup a doze VM inside of it.

---
@OP, I see in your cross-posted reply that you "bought this for $10". Then it should come with support. And did you use a pre-built UB server or install UB yourself? If it is a pre-built UB container did it come with virtualbox already installed or did you install it? If you installed it did you get it from source, UB repos or VZOpen repos? If you got if from any place other than VZOpen then A) You may need their version of it and B) The nested solution that you are attempting to build may not be compatible with their technology and you may need to look towards solutions that employ Xen, Docker and / or direct KVM containers.

Hello,

I use a pre-build Ubuntu 14.04 server, I was the one who Installed Virtualbox on the server. I used a tutorial and used UB repos to Install Virtualbox. The host support is really bad, they didn't help me at all. They just told me to go on Ubuntu forums and get support from there....

Thanks,
Matthew

Well, at least you're only out $10. I wouldn't give them any more money. As far as get support @ the UB forums goes: They're full of sh*t. This is either a problem with the container they built or it is simply not capable of doing what you are trying to do.

As I stated above: Update the instance kernel and headers.

Since you got VB from the UB repos then uninstall it immediately. That version of VB has had issue for years. You can try installing the VB binary's from source since you did not get it there in the first place: https://www.virtualbox.org/wiki/Downloads

But, VB may simply not be capable of doing what you're trying to do w/o at least a lot of modifications that are above your skill level (and mine for that matter, I've never heard of VB being nested inside of a container). That's why I said look to see if VZOpen has a version of VB to install inside a container.

Or, go over to the VB forums, and be prepared to roll up your sleeves and spend weeks (months?) becoming an expert on VT nesting.

After installing the instance headers if VB still won't work then another route to try would be to look in to qemu / xen / kvm / docker. Those solutions can be nested to various extents.

But why are you trying to bite off such a big chunk to begin with? You're not just taking on *nix in general as a noob, but also VT, nesting, remote/hosted(?) servers, containers, CentOS, Ubuntu, Virtualbox and doze VMs all at one shot.

My advice: Eat the 10 bucks and back up a bit. If you have a good machine at home with sufficient system resources then install VB to it directly and install a nice little *nix distro (like Deb8) in it and learn from there. Or set it up as a dual boot or get a junker from craigslist / yard sale / pawn shop and install there.

You have straight off jumped in to the deep end of the pool. If you insist on staying there do not be surprised if you give up in frustration; which would be your loss. Once you get the hang of it *nix is actually the ultimate way to go.

I agree 100% of everything you said. I contacted the Host saying If it's possible if you could update the kernel. They responded back
"I'm sorry but container based VPS cannot run a newer kernel than is available on the host node." I basically paid $10 for shit service, and a Server I can't even use....

Thanks,
Matthew

Thank you for your help, Do you know what host is good that you recommend for VirtualBox to be Installed without any issues?

Thanks,
Matthew

Do you mean a remote / hosted service? No, not really. You'll always bump up against some kind of limit of what they built, how they set it up and what they think "it should be".

At it's core *nix is ultimate freedom to do as you please with *your* system. But, you need to have "top level" control to be able to exercise that freedom fully; which means it needs to be on your hardware.

The only thing hosted I've ever messed with was a headless virtual VPN server container that I uploaded to a remote hosting company. And even that I built on my metal, before uploading, after reading their specs.

Do you have a windows lap top or a tower at home? If so what are the specs? If it has enough free system resources you can always install virtualbox in to doze and setup a *nix VM. If it does not have a lot of free system resources then you could always set it up as a dual boot. If you have projects that you want to be able to work with under both doze and *nix you could even set up a shared file partition. Or you can get used stuff at good prices if you shop around. I just added a home virtualization lab to my home network. I built it out of a junk SMB circa ~2005 x86_64 server w/ 8 cores, 12GB RAM and two 500GB RAID drives that I picked up off of craigslist for $50.

I would highly recommend that you start out on metal you own. The problem that you've run in to here was created by someone else's choices. They chose to build out a platform where the entire node shared a kernel which is propagated down in to the instance(s) that are hosting the container that you are running and further propagated down in to any containers / VMs that you try to install in to (nest in) that container. But, it does not "have to be" built that way. There are no technical limits that caused the implementation to be setup that way: somebody made a choice to set it up that way. They could have also set it up so that the node runs it's own kernel that is separate from the kernels in the instances and the containers (and even nested containers within containers) can all have their own separate kernels.

If you start out on your own metal then the only limitations that you will run in to are your imagination (free your mind and your ass will follow), your skill level (Google is your friend) and the implicit technological limitations of *nix (which you are fully free to try to change by creating new stuff).

Yeah like a remote hosted service. I have a Dell Laptop, The specs are. 64-bit Operating System, Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz 1.73 GHz. Which is better? VMware Workstation, or VirtualBox? I'm planning on using one of them, and Install Ubuntu 14.04 on it, and basically do what I was planning on doing before with this Host but it didn't work because of the kernel version.

Thanks,
Matthew

How many gigs of RAM do you have? My main terminal is a ~5 yr old lappy w/ one of the first i7's. It is a i7 2720QM EE and I have 8 GB RAM. All at the same time I can run on this terminal: The base OS (which I home rolled out of ubuntu 12.04), two fully virtualized "full" DE/GUI *nix OSes (one OS that I built that has a teamviewer interface to my vista box and the other is deb8), several SSH terminals to various parts of my NT, a phpvitualbox console to my vtlab and a nomachine interface to my dedicated kali box and I still have about 800MB free RAM. Now all of that is *nix / virtualbox based; which does not use anywhere near as much resources as doze and VM ware. When I fire up my W7 VM on my main terminal it is such a resource hog that I lose the ability to do ~70% of that stuff.

As far as how to set things up: It depends on what you want to achieve. If you're looking to get your toes wet make doze the main OS and VT *nix in a VM. If you want to get good and wet set up a dual boot. If you want to take the plunge then make *nix your main OS and VT doze.

As far as a *nix host OS: This is just my personal opinion, but stay very, very far away from ubuntu. I know my system is based on it and when I started to use it in 2011 when I got in to *nix it was OK for beginners. But that has changed for a lot of reasons both technical and political. Google "why ubuntu is bad" and make up your own mind. Personally I'd recommend debian 8. It has it's issues as well. But they mostly center around the devs being militantly FOSS instead of actual tech / privacy / world politics (sleeping w/ the Chinese government) issues. There's nothing you can do in ubuntu that you can't do in deb8. The only dif is that it will take a little more / slightly "deeper" work to get it done. But not so much so as to make it out of reach for beginners. And a lot of the good stuff in UB has actually made it upstream to deb8 w/o the associated BS.

As far as VB vs VMw: Well once again, it depends on what you want to achieve? Employability? VMw, hands down. It is "the" go to enterprise solution. (By no means the only one, but it's a biggy and will get you jobs.) Hackability, freedom, stability, flexibility, FOSS? VB, hands down. I personally prefer VB.

Now if you decide to go with VMw then you will want to use doze as your base OS. VMw will run in a *nix host based environment. But it has been my experience that it will run like sh*t and you'll spend more time kicking it to keep it running than you will actually using it. VB runs like a charm on both doze and *nix hosts; just be sure that you get it from source (DL directly from VB) b/c a lot of distro devs like to "optimize" it (read: F* it up).

1 members found this post helpful.

should install the module, chances are you already have it, you just need to load it, you might have to reboot host after running the command above.