Could not install header

[xeniux]

Respected Proxmox Staff and Users,

I'm in the middle of installing VirtualBox on my Ubuntu SS 13.10 (run at OVZ) and i got stuck cause it keeps asking for installing pve header :

trying to install but not found the package

root@SvrVMBackup:~# apt-get install pve-headers-2.6.32-27-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package pve-headers-2.6.32-27-pve
E: Couldn't find any package by regex 'pve-headers-2.6.32-27-pve'

Any one knows how to install and get the file?

Thanks alot in advance

Kind regards

Xen

 

[xeniux]

in addition i got this message at vbox-install.log
DKMS: add completed.
Failed to install using DKMS, attempting to install without
Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.

seems that i need to update the linux kernel? but i wonder that the kernel that i use is the most recent?
I suppose it means Proxmox kernel and not Ubuntu where i put the VBox, cause the Ubuntu had already at 13.10, the most recent one now i suppose.

advice would be greatly appreciated, Thanks alot

kind regards

Xen

 

[xeniux]

[update]

i 'think' i got the header file from ftp://download.proxmox.com/debian/dists/wheezy/pve-no-subscription/binary-amd64/

I put it in /usr/src : pve-headers-2.6.32-27-pve_2.6.32-121_amd64.deb

Got this when try to install in Ubuntu GUI : http://i.imgur.com/TWuPTk8.png

when i run sudo apt-get install pve-headers-2.6.32-27-pve_2.6.32-121_amd64.deb, got this error : http://i.imgur.com/B2apOjD.png

Might need some guidance on :
1. getting the right file
2. put the right file at the right path
3. installing the file

Thanks in advance

Kind regards

Xen

 

[xeniux]

[update]

Trying to use dpkg to install the header , got mismatched architecture : http://i.imgur.com/ijGMNHy.png

Seems that all the kernel header for AMD64, any path/link for i386?

Now i totally stuck and hands up

kind regards

Xen

 

[Mr.Holmes]

Hello xeniux,

The line deb http://download.proxmox.com/debian wheezy pve-no-subscription

is missed in /etc/apt/sources.list


BUT:

VBOX in an OpenVZ container is something special and cannot be done by
simply installing in container, but works ....

You have to do the following:

- install VBOX in your container

- check if the GUI works and a machine can be created

- start the machine - it fails now because of mising kernel module

- install VBOX in PROXMOX server

- you MUST NOT have a kvm machine active (kvm and VBOX cannot run parallel, see http://www.dedoimedo.com/computers/kvm-virtualbox.html)

- unload the kvm kernel modules

- check if VBOX works

- grant the VBOX kernel module to your container (here 5505 is the container id)
vzctl set 5505 --devnodes vboxdrv:rw --save
vzctl set 5505 --devices c:10:58:rw --save

- now start the machine again in the container - should work!

Let me finally note that I tested it and checked out just if the machine starts with a simple live-cd.
If there is anything else (virtual network etc.) to take care of I cannot say ....

Best regards

Mr.Holmes

 

[xeniux]

Hi Mr Holmes,

Thanks for your response,

"The line deb http://download.proxmox.com/debian wheezy pve-no-subscription
is missed in /etc/apt/sources.list"
>> I had added to the sources, and when i try to install the header it fails.
>> I also had add the linux header file to /usr/src and then run the header installation, but still failed (please see image above that i put)

"- start the machine - it fails now because of mising kernel module"
>> Yes, it said that i had not installing the kernel header (which is one of the factor that makes vbox could not run)
>> I could create VM in VBOX but when i want to start it said that i had to setup the vboxdrv

"- install VBOX in PROXMOX server"
>> Did you mean by installing vbox in the proxmox GUI ("monitor") ?
>> If yes then what code that i need to put there in order to install the vbox?

"- you MUST NOT have a kvm machine active (kvm and VBOX cannot run parallel, see http://www.dedoimedo.com/computers/kvm-virtualbox.html)
- unload the kvm kernel modules "
>> I had KVM running in Proxmox not in my Ubuntu OVZ, does running KVM in proxmox (not in ovz) affect to this issue too? need confirmation.

"- grant the VBOX kernel module to your container (here 5505 is the container id)
vzctl set 5505 --devnodes vboxdrv:rw --save
vzctl set 5505 --devices c:10:58:rw --save"
>> means i put this code in my OVZ host?
>> what is the meaning of : c:10:58:rw ?

Looking forward to hear from you. Thanks again for your precious time. Greatly appreciated.

Kind regards

Xen

 

[Mr.Holmes]

Hello xeniux,

Comments as follows:

>> I had added to the sources, and when i try to install the header it fails.
>> I also had add the linux header file to /usr/src and then run the header installation, but still failed (please see image above that i put)
Forget it - has no relevance, see next paragraph why: OVZ does not have an own kernel.

>> Yes, it said that i had not installing the kernel header (which is one of the factor that makes vbox could not run)
>> I could create VM in VBOX but when i want to start it said that i had to setup the vboxdrv
Means, the installation on OVZ was ok! - But the server preparation is still missed.
Why? OVZ ues the kernel of the (PROXMOX-)server. Therefore you have to load the respective kernel module there.
The easiest way to do so is to install it also tehre (even you will not install VBOX any virtual machine there).

>> Did you mean by installing vbox in the proxmox GUI ("monitor") ?
No- connect to your PROXMOX via ssh and install the VBOX package for debian wheezy
>> If yes then what code that i need to put there in order to install the vbox?
just install it with dpkg - important: the kernel module will be generated and loaded during this process.


>> I had KVM running in Proxmox not in my Ubuntu OVZ, does running KVM in proxmox (not in ovz) affect to this issue too? need confirmation.
Unfortunately, the OVZ has here an effect to the server. You must decide: kvm OR VirtualBox (regardless they are directly in server or in OVZ container)

>> means i put this code in my OVZ host?
No - in the PROXMOX server
>> what is the meaning of : c:10:58:rw ?
parameter corresponding to "mknod" - for further information see linux documentation (man page etc.)

Best regards

Mr.Holmes

 

[xeniux]

Hi,

From what i got from your explanation is :
1. Vbox could not run parallel with KVM and KVM need to be shut down.
2. Vbox need to be installed in proxmox via ssh and then run again the VBox at Ovz (Ubuntu) and the Vbox would run.

Kindly confirm before i install the vbox on proxmox via ssh and also how to check what debian version that i use?

Thank you alot in advance Mr.Holmes.

Kind regards

Xen

 

[xeniux]

Hi,

- grant the VBOX kernel module to your container (here 5505 is the container id)
vzctl set 5505 --devnodes vboxdrv:rw --save
vzctl set 5505 --devices c:10:58:rw --save

In what file should i put that line of code?
(i suppose that the file is in proxmox main server)

Thank you in advance

Kind regards

Xen

 

[Mr.Holmes]

Hello xeniux,

In principle: strongly recommended to make experiments first with a separate installation. All what I mentioned here I have just tested with my environment an worked - but I cannot give any guarantee, it´s not a tutorial, we never know ....

1. Vbox could not run parallel with KVM and KVM need to be shut down.
Xen

Yes, but if already a kvm runs, probably a reboot of PROXMOX is necesarry

2. Vbox need to be installed in proxmox via ssh and then run again the VBox at Ovz (Ubuntu) and the Vbox would run.
Xen

Yes

Debian in PROXMOX 3.0 and higher is wheezy, about older versions I don´t know

Best regards

Mr.Holmes

 

[xeniux]

Hi Mr.Holmes.

I tried to install the deb package of Vbox that i got , got error like this :

root@XenSky:~# ls
virtualbox-4.3_4.3.10-93012~Debian~wheezy_amd64.deb
root@XenSky:~# dpkg -i virtualbox-4.3_4.3.10-93012~Debian~wheezy_amd64.deb
(Reading database ... 36648 files and directories currently installed.)
Preparing to replace virtualbox-4.3 4.3.10-93012~Debian~wheezy (using virtualbox-4.3_4.3.10-93012~Debian~wheezy_amd64.deb) ...
Unpacking replacement virtualbox-4.3 ...
dpkg: dependency problems prevent configuration of virtualbox-4.3:
virtualbox-4.3 depends on libgl1-mesa-glx | libgl1; however:
Package libgl1-mesa-glx is not installed.
Package libgl1 is not installed.
virtualbox-4.3 depends on libpython2.7 (>= 2.7); however:
Package libpython2.7 is not installed.
virtualbox-4.3 depends on libqt4-network (>= 4:4.5.3); however:
Package libqt4-network is not installed.
virtualbox-4.3 depends on libqt4-opengl (>= 4:4.7.2); however:
Package libqt4-opengl is not installed.
virtualbox-4.3 depends on libqtcore4 (>= 4:4.8.0); however:
Package libqtcore4 is not installed.
virtualbox-4.3 depends on libqtgui4 (>= 4:4.8.0); however:
Package libqtgui4 is not installed.
virtualbox-4.3 depends on libvpx1 (>= 1.0.0); however:
Package libvpx1 is not installed.
virtualbox-4.3 depends on libxinerama1; however:
Package libxinerama1 is not installed.

dpkg: error processing virtualbox-4.3 (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
virtualbox-4.3

Kindly advice what steps that i need to do?

Thank you in advance.

Kind regards

Xen

 

[xeniux]

I got this error when i tried to install the suggested package :

root@XenSky:~# apt-get install libgl1-mesa-glx
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
libgl1-mesa-glx : Depends: libdrm2 (>= 2.3.1) but it is not going to be installed
Depends: libglapi-mesa (= 8.0.5-4+deb7u2) but it is not going to be installed
Depends: libxcb-glx0 (>= 1.8) but it is not going to be installed
Depends: libxdamage1 (>= 1:1.1) but it is not going to be installed
Depends: libxxf86vm1 but it is not going to be installed
Recommends: libgl1-mesa-dri (>= 7.2) but it is not going to be installed
virtualbox-4.3 : Depends: libpython2.7 (>= 2.7) but it is not going to be installed
Depends: libqt4-network (>= 4:4.5.3) but it is not going to be installed
Depends: libqt4-opengl (>= 4:4.7.2) but it is not going to be installed
Depends: libqtcore4 (>= 4:4.8.0) but it is not going to be installed
Depends: libqtgui4 (>= 4:4.8.0) but it is not going to be installed
Depends: libvpx1 (>= 1.0.0) but it is not going to be installed
Depends: libxinerama1 but it is not going to be installed
Recommends: libsdl-ttf2.0-0 but it is not going to be installed
Recommends: dkms but it is not going to be installed
Recommends: linux-headers
Recommends: gcc but it is not going to be installed
Recommends: make but it is not going to be installed
Recommends: binutils but it is not going to be installed
Recommends: pdf-viewer
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Kindly advice

Thanks alot

Kind regards

Xen

 

[pirateghost]

I have to ask what you are looking to accomplish by running vbox inside a container?

Sent from my Nexus 5

 

[xeniux]

Hi,

Thanks for your response Pirateghost,

I'm trying to install winsvr2008 in for my client with static IP so he could access through RDP.

Tried to use KVM to install winsvr2008 (could install but stuck with assigning static IP on KVM)
Tried to use OVZ to install winsvr2008 (could assign IP but stuck with installing Vbox)

Any advice on helping to accomplished with one of those 2 method is very appreciated.

Thanks in advance.

Kind regards

Xen

 

[pirateghost]

I run a few different windows 2008 servers in kvm. Not really understanding your problem of assigning it a static IP. Perhaps you should fix that instead of breaking your entire system for vbox

Sent from my Nexus 5

 

[xeniux]

Hi,

Thanks for your response Pirateghost,

May i know could you RDP to your KVM (winsvr2008) ?
Did you assign static failover IP or you use DHCP?

Thank you in advance

Kind regards

Xen

 

[pirateghost]

Hi,

Thanks for your response Pirateghost,

May i know could you RDP to your KVM (winsvr2008) ?
Did you assign static failover IP or you use DHCP?

Thank you in advance

Kind regards

Xen

Of course I can RDP into my winservers.

instead of these vague questions and responses can you give us a proper layout of your network and the server configuration? At this point it sounds like your server should be wiped and reloaded due to all the misconfiguration you have done to it.

A KVM machine will act like ANY other machine on the network if you have your network configurations correct. I don't understand why you would have trouble doing this, or why you would think that VBOX was a good idea to completely trash your proxmox install. You have a good virtualization hypervisor at your fingertips and you tried to install another virtual pseudo-hypervisor on top of it for some strange reason.

Create KVM, install windows server 2008, assign it a static IP from within the VM itself... DONE. All my servers have static IP addresses assigned.

 

[Mr.Holmes]

Hello,

yes indeed, pirateghost is right here: to install VBox in PROXMOX or one of its vitual machines is strange and not a proper solution.

And after such a lot of experiments

your server should be wiped and reloaded due to all the misconfiguration

is really recommended.

@pirateghost:

However: it was an example adding kernel modules to PROXMOX in order to use them in OVZ.

Do you think to add kernel modules or just add packages into PROXMOX server is misconfiguration in principle? Or only in that particular case?

Best regards

Mr. Holmes

 

[pirateghost]

Hello,

yes indeed, pirateghost is right here: to install VBox in PROXMOX or one of its vitual machines is strange and not a proper solution.

And after such a lot of experiments


is really recommended.

@pirateghost:

However: it was an example adding kernel modules to PROXMOX in order to use them in OVZ.

Do you think to add kernel modules or just add packages into PROXMOX server is misconfiguration in principle? Or only in that particular case?

Best regards

Mr. Holmes

Only in this particular case.

If installing the necessary dependencies for vbox breaks all of kvm, then it essentially breaks proxmox. I personally prefer to keep proxmox as close as possible to the way it ships, only adding in what I absolutely need. Adding in vbox is just not necessary. At that point, just convert the physical machine to a standard Linux desktop and load up vbox

Sent from my Nexus 5