On Fri, 18 May 2012 20:12:39 +0200, "Damien Raude-Morvan" <[email protected]> wrote: > Olivier, > > 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 >
Ah, strange, as it won't complain if no ARCH is specified :-/ Maybe there needs a real check for mandatory attributes ? > 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...) > The controller's arch is of no use, for sure (hopefull, not involved, AFAICT ;-) It's just that I was assuming that by default (without any explicit ARCH setting), the same arch could be assumed by the One for its host/node and guest kvm VMs... but surely if this is explicitely set (mandatory attribute), there won't be any problem (unless autodetection inside the VM image was possible, but I'm not sure this is feasable). So, should be file a bug upstream complaining that mandatory attribues don't seem to be ? 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) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
