[Pkg-opennebula-devel] Bug#673173: Bug#673173: opennebula: Forces -cpu qemu32 even if host (and guest) ar amd64

[Olivier Berger]

On Fri, May 18, 2012 at 08:12:39PM +0200, Damien Raude-Morvan wrote:
> Le mercredi 16 mai 2012 18:26:14, Olivier Berger a écrit :
> > Hi.
> > 
> > I'm running opennebula on a 64 bit host with amd64 kernel.
> > 
> > If no explicit OS is parameterized in the VM conf file, kvm will be run
> > with -cpu qemu32, which will prevent booting an amd64 Debian image.
> > 
> > AFAICT, one needs to specifically set :
> > OS=[
> >   ARCH=x86_64 ]
> > in the conf file for kvm to be run without -cpu, hence allowing the
> > bootable image to boot.
> 
> From http://opennebula.org/documentation:rel3.4:kvmg#mandatory_attributes, OS 
> mandatory attributes are :
> BOOT + ARCH + KERNEL
> 
> I'm not sure to understand what you would expect here ? Setting a default ARCH 
> attribute given current arch of OpenNebula controller node doesn't seems to be 
> valid (for example, I'm using an old server as OpenNebula controller - i386 
> but all my nodes/VM are amd64...)
> 

I have investigated this further (see thread at http://lists.opennebula.org/pipermail/users-opennebula.org/2012-May/008972.html) on upstream's list.

My current feeling is that Debian shouldn't ship a default ARCH in /etc/one/vmm_exec/vmm_exec_kvm.conf (currently there's one i686, as per upstream's default file), letting the user, either change that in that file, or in each VM template.

The missing mandatory attribute setting would be detected by One at deployment file generation and reported as a FAILED VM.

Of course, the docs could then indicate that one such setting should be defined.

Maybe the need for removing such a default setting in vmm_exec_kvm.conf in Debian is even more needed, compared to upstream choices, as Debian is supposed to be very versatile, architecture-wise.

What do you think ?

I have suggested a similar change for upstream (see http://lists.opennebula.org/pipermail/users-opennebula.org/2012-May/009036.html) which may well then be tracked in an upstream ticket too.

In the meantime, I have reflected this issue in http://wiki.debian.org/OpenNebula/PreparingDebianVmTemplate hoping it can help others.

Best regards,

-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)