Just an Idea - Is it possible???

K

kumarullal

Renowned Member
Jun 17, 2009
184
0
81
LA, USA
Just an Idea - Is it possible??? Proxmox on a 32 bit os!!!

Proxmox is extremely versatile product.
The web interface is very user friendly. With all the packages like vzdump etc it is extremely powerful when compared to any commercial product out there. Creating, backing up of VEs, using the web interface using vzdump is extremely easy. No command line needed.
The other impressive thing is bonding of NICs and cluster setup which is fantastic for High availability.
I would rate proxmox as the best virtualization product out there
The only issue is that it comes in a 64 bit OS kernel (to support KVM as well as Openvz).
There are times when it is nessesary to share the kernel with the guest os. Since most development work is done on a 32 bit OS kernel, (I may be wrong) this sharing of kernel for certain modules (Example: Zaptel/Dahdi on a 32 bit guest os with asterisk) can not be done with 32 bit guest OS.
Here is the question.
Is it possible for Proxmox team to come up with another product with the same web based control panel in a 32 bit os kernel, either as an ISO image or as a tarball installation. It could be any distro, preferably Centos. Even Debian should be fine.
This would have the capability to support Openvz only and not KVM !!!!
For KVM, for different OS including windows, the existing product is always available.
There are many control panels for Openvz, Hypervm, Parallels etc to name a few.
But there is nothing out there to beat Proxmox.
If this is possible, then it would be one of the most powerful tools for openvz.
Any thoughts in this direction?
 
Last edited:
kumarullal said:
Proxmox is extremely versatile product.
The web interface is very user friendly. With all the packages like vzdump etc it is extremely powerful when compared to any commercial product out there. Creating, backing up of VEs, using the web interface using vzdump is extremely easy. No command line needed.
The other impressive thing is bonding of NICs and cluster setup which is fantastic for High availability.
I would rate proxmox as the best virtualization product out there
The only issue is that it comes in a 64 bit OS kernel (to support KVM as well as Openvz).
There are times when it is nessesary to share the kernel with the guest os. Since most development work is done on a 32 bit OS kernel, (I may be wrong) this sharing of kernel for certain modules (Example: Zaptel/Dahdi on a 32 bit guest os with asterisk) can not be done with 32 bit guest OS.
Here is the question.
Is it possible for Proxmox team to come up with another product with the same web based control panel in a 32 bit os kernel, either as an ISO image or as a tarball installation. It could be any distro, preferably Centos. Even Debian should be fine.
This would have the capability to support Openvz only and not KVM !!!!
For KVM, for different OS including windows, the existing product is always available.
There are many control panels for Openvz, Hypervm, Parallels etc to name a few.
But there is nothing out there to beat Proxmox.
If this is possible, then it would be one of the most powerful tools for openvz.
Any thoughts in this direction?
Click to expand...

In theory this is possible. But the goal of Proxmox VE is OpenVZ and KVM on 64-bit.
 
Thanks a lot Pille,
I added the line
Code: 
 deb [URL="http://flippy.medialisten.net/%7Epille/pve-1.4-i386"]http://flippy.medialisten.net/~pille/pve-1.4-i386[/URL]
/etc/apt/sources.list
When I run aptitude update,
I get the following error
E: Malformed line 11 in source list /etc/apt/sources.list (dist)
E: Malformed line 11 in source list /etc/apt/sources.list (dist)
E: The list of sources could not be read.

Next question,
Do I also need to add the following line is /etc/apt/sources.list?
Code: 
deb http://ftp.debian.org/debian lenny main

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve

# security updates
deb http://security.debian.org/ lenny/updates main

Should I install the the pve-kernel as per the pxoxmox install guide?

Thanks in advance.
 
kumarullal said:
Thanks a lot Pille,
I added the line
Code: 
 deb [URL="http://flippy.medialisten.net/%7Epille/pve-1.4-i386"]http://flippy.medialisten.net/~pille/pve-1.4-i386[/URL]
/etc/apt/sources.list
When I run aptitude update,
I get the following error
E: Malformed line 11 in source list /etc/apt/sources.list (dist)
E: Malformed line 11 in source list /etc/apt/sources.list (dist)
E: The list of sources could not be read.

Next question,
Do I also need to add the following line is /etc/apt/sources.list?
Code: 
deb http://ftp.debian.org/debian lenny main

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve

# security updates
deb http://security.debian.org/ lenny/updates main
Should I install the the pve-kernel as per the pxoxmox install guide?

Thanks in advance.
Click to expand...

go back to the wiki and check the line for the repository (you missed the ./ at the end)
 
Thanks for pointing that out.
Changed it and now it has installed.
Now I am going to test it with some OpenVZ images. I will post my finding here.
Thanks, once again.
 
I am still working on it. However, I have to report 2 problems.
Problem 1)
The "VNC console" does not show any characters. It shows a black screen and the cursor. It moves when I type a command, but does not show any characters.

When I try to enter the container it does not allow me to enter.
This the output:
Code: 
 vzctl enter 201
Warning: too large value for NUMTCPSOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMOTHERSOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for KMEMSIZE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for TCPSNDBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for TCPRCVBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for OTHERSOCKBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for DGRAMRCVBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMFILE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMFLOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for DCACHESIZE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for SHMPAGES=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMIPTENT=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for PHYSPAGES=0:9223372036854775807 was truncated
Unable to fork: Cannot allocate memory
What could be the problem?

Problem 2) vzdump did not work correctly, I had to manually reinstall older version for it to work correctly.
wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_1.1-2_all.deb

Then
dpkg -i vzdump_1.1-2_all.deb


FYI
This is the output:
Code: 
Openvz-prox:/# pveversion -v
pve-manager: 1.4-9 (pve-manager/1.4/4390)
qemu-server: 1.1-6
pve-kernel: not correctly installed
pve-qemu-kvm: not correctly installed
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1dso1
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1


Thanks in advance.
 
Last edited:
try clicking into the black window first. or login on the cmdline to see if that works. all daemons running?
 
Hi Pille,

When I click in to the black window and type any command, the cursor moves, but I cant see any characters.
It allows me to log in using putty. no problem there.
 
actually i'm out of ideas? is the i386 specific? does it work after migrating the machine to official pve installation?
 
pille said:
actually i'm out of ideas? is the i386 specific? does it work after migrating the machine to official pve installation?
Click to expand...

i386 is not a supported architecture so we cannot answer this - no one here uses i386.
 
Re: Just an Idea - Is it possible??? Proxmox on a 32 bit os!!!

Hi Pille,
I have figured out a way to work perfectly with your compilation of proxmox, so please don't ever take it offline. It is a great resource for anyone wanting to load Proxmox on a 32 bit OS!!!!
Here is what I did. But first to answer your question, yes it works just fine when I copied the VE to an official version of proxmox.
Anyways, I found the solution to the VNC terminal problem. I can enter the container from the host node. "vzctl enter xxx". Works fine.
However, there is an issue that needs to be fixed manually every time you build a container form a template. (Even if it is the proxmox approved temples)
I get:
Warning: too large value for NUMTCPSOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMOTHERSOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for KMEMSIZE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for TCPSNDBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for TCPRCVBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for OTHERSOCKBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for DGRAMRCVBUF=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMFILE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMFLOCK=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for DCACHESIZE=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for SHMPAGES=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for NUMIPTENT=9223372036854775807:9223372036854775807 was truncated
Warning: too large value for PHYSPAGES=0:9223372036854775807 was truncated

To solve this problem, I created a config file using vzsplit
vzsplit -n 4 -f ve.4
Then copy everything from the ve.4-sample.conf file (Please leave out CPU fairshare and everything below as it is. Copy everything above it) and replace it in the conf file of any container giving the "Warning: too large" message.
Once I did that, the change reflected on the Proxmox web interface, but with strange values of CPU, RAM and SWAP.
However, Now if I simply changed the values from the web interface to the desired CPU, RAM and Swap, it WORKED just fine. That turned out to be a clean image with no warning error, and any problem!!!!
I could then copy that image using vzdump to the official Proxmox version running on 64 bit, and works just fine!!!
Thanks once again Pille, to provide us with the opportunity to load proxmox on a 32 bit OS. Bravo!!
 
Last edited:
Re: Just an Idea - Is it possible??? Proxmox on a 32 bit os!!!

kumarullal said:
To solve this problem, I created a config file using vzsplit
Click to expand...

You simply need to adjust the maximum integer value, i.e replace '9223372036854775807' with '2147483647'

Code: 
# sed -e 's/9223372036854775807/2147483647/g' -i /etc/vz/conf/<VMID>.conf
 
You must log in or register to reply here.
Top Bottom