plesk 9.5 + centos 5.6, and "correct"yum repos to use?

[paulie]

Hi,

After extensive testing a 32 bit Virtuozzo container will report a 32 bit kernel be it hosted on a 64-bit or a 32-bit node (obviously I'm lying when I say "extensive", I just built a 32 bit Openvz container on a 64 bit node and it fakes the output to say 32 bit. I think this is because this is where yum pulls its basearch from).

So, if the output from your vps is saying 64 bit then either they've migrated you from a 32-bit to a 64-bit node (which ought not to be possible), or you and your provider are looking at different VPS's.

Whats the output of "yum check-update" in terms of the types of packages the vps wants to update?

Paul.

[scott]

Its going to say 64-bit

[faris]

Yeah, all Viruozzo VPSes will report the same kernel version, no matter whether they are 32bit or 64bit. The kernel is the host nod's kernel, and the host will definitely be 64bit.

When creating a container, the hosting company can choose between 64 and 32bit.

32bit would be preferable over 64bit when: They also have 32bit nodes, as this allows the container to be moved to those nodes as well as64bit nodes OR POSSIBLY to keep things a bit simpler in terms of management for the user (only 32bit libraries to deal with) OR when the container was created it was on a 32bit node in which case there was no choice at the time.

You can tell which your container is for sure by logging in to your Virtuozzo Power Panel.

Look at the OS Template (under container summary). It is says centos5-x86 then it is 32bit. If it says centos5-x86_64 then it is 64bit.

[paulie]

Faris,

Thats not true on OpenVZ so I suspect its not true on Virtuozzo (I'm not at work, just coming to the end of a 3 week holiday) :

Node :

Code: Select all

[root@opennode ~]# uname -a
Linux opennode.pagwag.co.uk 2.6.18-194.17.1.el5.028stab070.7 #1 SMP Fri Oct 1 14:17:14 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@opennode ~]# 

64-bit Container :

Code: Select all

[root@oms /]# uname -a
Linux oms.opennode.pagwag.co.uk 2.6.18-194.17.1.el5.028stab070.7 #1 SMP Fri Oct 1 14:17:14 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@oms /]# 

32-bit Container :

Code: Select all

[root@test /]# uname -a
Linux test.pagwag.co.uk 2.6.18-194.17.1.el5.028stab070.7 #1 SMP Fri Oct 1 14:17:14 MSD 2010 i686 athlon i386 GNU/Linux
[root@test /]# 

And just to prove they're on the same host :

Code: Select all

[root@opennode ~]# vzlist -a
      CTID      NPROC STATUS    IP_ADDR         HOSTNAME
       101         29 running   10.0.0.252      oms.opennode.pagwag.co.uk
<snipped some>
       104         12 running   10.0.0.233      test.pagwag.co.uk
[root@opennode ~]# 

Also we have a Virtuozzo/OpenVZ container with another company that is 32-bit :

Code: Select all

[<snipped> ~]$ uname -a
Linux <snipped> 2.6.18-028stab068.3-ent #1 SMP Wed Feb 17 11:54:49 MSK 2010 i686 i686 i386 GNU/Linux

From memory the -ent indicates that its a PAE kernel, this is missing from humpy's kernel, which in all probability indicates its a 64-bit node surely?

What I find odd about "Virttuozzo the most popular virtualization solution in the world" is the complete lack of any real information on it and how it works, the Parallels virtuozzo forums are virtually and have been for the 2 years I've been working with it.

[scott]

I suspect thats probably really just tricking the uname function, its not really possible to run a different kernel in a container-type virtualization environment.

[paulie]

Hi,

Yes, absolutely, because if it doesn't then yum will install 64 bit versions of software on a 32 bit container hosted on 64 bit hardware : http://www.redhat.com/archives/rhl-list ... 03438.html (Someone claiming that $basearch is pulled from uname).

I can't see the fiddling happening within the container, it must be occurring from the node, so on that basis I can only assume that the Servermasters support are mistaken.

Paul.